Not only is Cluely factually wrong, his argument doesn't make sense. Even if you pretend IIS is the most popular web server, and thus more often targeted by worms, that would still mean it's more often targeted by worms, and thus an unusually vulnerable platform. It being "not Microsoft's fault" won't keep your server secure any more than "not Linux's fault" will help it write NTFS any time soon.
It may or may not still blow (I haven't tried it), but there have been substantial changes. Andrea Arcangeli did a large rewrite in pre11 ("major VM merge.")
If you're looking for a stable VM, I've heard a handful of good things (like this) about 2.4.9-ac10. Alan's been much more cautious than Linus about merging VM changes.
For years, Linux has had it's own C library. The BSD world also uses their own C libraries. There is no reason that Linux has to use glibc, that's a choice that the community has made.
For pretty much everything are non-GNU alternatives: bash can be replaced by zsh, ash or the Korn shell. All the command line tools can be taken from *BSD.
Whups; I hadn't known about Linux libc. Thanks for pointing out my error. I guess I should tone down my rhetoric a bit, or at least make sure of my facts first:-).
The GNU project was founded with the explicit goal of producing a Free operating system. So was Linux. When the Linux kernel got functional, GNU was done, except for the kernel -- and the Linux people bolted GNU tool after GNU tool onto the system. Linux (the cool hack) gradually morphed into GNU/Linux (the full-featured Unix clone), and the name was never "officially" changed, even after the amount of system-essential GNU code had far exceeded the amount of system-essential Linux code.
On a Redhat system (for example),the C library, the compiler toolchain, bash, and all the command-line tools (ls, mv, chgrp, and the like) are all GNU tools, designed originally for use within an operating system called "GNU."
You can, of course, call the OS whatever you like. But one of the reasons RMS is so adamant about "GNU/Linux" is that "Linux" fosters the mistaken impression that all the GNU tools are optional add-ons like Gnome, the Gimp, or Gnumeric. You can try "rpm -e glibc" or "rpm -e libstdc++", or find/write replacements for these, if you still believe that they are.
The lesson here is: Don't buy.biz domains. They already collide with OpenNIC's.biz domain, which means that if OpenNIC gains any popularity, your domain name may not function.
How much are you willing to bet that the internet will still be following a pigheadedly self-serving organization like ICANN five years from now?
Agreed. Here's a bit by Brett in which he lays out his views on the GPL ("The GPL... was designed explicitly to hurt programmers' livelihoods.") and Stallman (who "says that good wages for programmers should be 'banned.'")
This common misunderstanding is part of why RMS is so adamant about "GNU/Linux." A modern Linux system uses the GNU project's system libraries, compiler toolchain, and (mostly) command-line Unix tools (tar, gzip, etc.) Without any one of these, Linux couldn't function as a modern Free OS -- they're not "trivial" add-ons like Perl or Apache.
I personally say "Linux," probably because I'm afraid of looking silly. It is true, though, that there's more GNU code on your machine than Linux (i.e. kernel) code, and it's just as necessary to get your bash prompt to come up. Some people say it's "more necessary" (since GNU has a kinda-sorta-almost-working kernel, but AFAIK gcc and glibc have no existing Free replacements), but that just starts flamewars.
I highly recommend showing people how insecure telnet is -- in a dorm, for example, pop up ethereal on one machine and log in over telnet from a machine in a different room. Follow TCP stream, and point to your real password displayed on the screen. This is more effective than lecturing people about TCP/IP and ethernet, and I've only had one guy start asking dismaying questions about how to sniff other people's passwords.
Change your password after, of course. Now if only there were an equivalent way to get people to use PGP...
My wife is from Europe, where truthfulness in ads seems to be something the governments still care about, and it has taken her YEARS to build up enough skepticism of ads to not believe all the patently fraudulent bullshit that is perpetrated here.
You've hit the nail on the head, I think... if I had my way, we'd have no truth in advertising whatsoever. Car commercials would show the cars going 200mph, then extruding wings and lifting off to shoot down the Soviet invaders, all for just $19.95. Fast-food places would say that their milkshakes cured cancer. Microsoft would say that failure to use their software was a license violation punishable by law. People would have to actually do some research, or talk to their friends, to find out which products were good enough to buy, everyone would get accustomed to the idea that the stuff that comes out of corporate mouthpieces is greed-laced extract of horseshit, and we'd all be a lot better off.
Similar things apply to the laws that keep Las Vegas "fair" by limiting the casinos to removing your money at a fixed, gradual rate, but I digress...
The idea that we need a central authority to dictate nicknames is ludicrous. The idea that if nicknames collide, the internet is "destabolized" is equally silly.
A large problem with this (which is mentioned in the linked articles, but who has time to read those?) is that a lot of existing software assumes that the hostname-to-IP mapping is global to the internet; email handlers, search engines, and transparent web proxies are three examples. There's also the madness that results when non-authoratative DNS records manage to cross over into machines that aren't "loyal" to the agency that defined them.
mp3 files don't reduce album sales, they simply help people avoid bad purchases (and sometimes help them make better ones too).
Yep. Have you noticed that Napster now blocks John Fogerty, Bob Dylan, Steppenwolf, and John Kay, but not N'Sync or Snoop Doggy Dog? Try it; I think the RIAA is smarter than we give them credit for.
Re:Sounds like a good idea, but..
on
The Dot in .mars
·
· Score: 2
For our
deep-space links, we're dealing with many issues that can cause the IP
stack to break down, like a lot of latency, intermittent links and
high bit-error rates because of very low signal strength. We can
encounter latency approaching more than 30 minutes on the link from
the orbiter back to Earth, for example. We borrow a lot of the
concepts of Earth's Internet but come up with protocols that will work
in this deep-space application.
D00D U CAN JUST USE UUCP
UUCP ROKS MY DAD HAS A DIAL UP 4 EMALE
/Q
Slipshod as it is, the following worked quite well for me back in the beta3 days; it assumes all the mp3s have filenames of the form "Artist - Title.mp3". If you want to nuke your mp3s as you go, remove the # from the obvious place (after making sure it works.) It needs mpg123 and vorbis-tools. Change "-b 128" to encode at a different bitrate.
Hack the seds to taste if your mp3s are systematically named; if they aren't, root around in $TEMP for tags or use this (which discards title & artist):
Beyond the 2.4 kernel, Linux developers are asking for the incorporation of a journaling file system,
No comment.
more work on Linux clusters and on the scheduler,
"I asked the engineers I manage what Linux needed, and this is what they told me. I don't know what it means."
additional scalability, high availability, internationalization,
"This is what I think Linux should have. I don't know what it means, either."
printing, and systems management.
"I tried to do these under Linux and I couldn't, so I guess it doesn't have them."
It seems like most of the article was about making an artificial distinction between "lowly consumer-level stuff" and Enterprise Level Computing, with the strong implication that Powerful Businessmen (the people interviewed: a vice president, a CTO, a chairman, a Data Center Manager, and, for some reason, an analyst) need Enterprise Level Computing, which Linux still doesn't do.
Shit, man, it works or it doesn't. Maybe (as the analyst lucidly pointed out near the end) the OEMs and ISVs need to put out ERP and CRM with the SMP and raw I/O that the 2.4 kernels can provide. Or you could just write me a check right now, sir, and I'll see that it gets done.
This is one of the things the FSF is good for. They have lawyers and such, and they have a history of contacting companies infringing on GPLed code and fixing the problem without making it into a public brouhaha.
It may be, for example, that the company (particularly if its Indian developers' grasp of English doesn't extend to legalese) doesn't properly understand the difference between GPLed code and public domain code. In the case that the company doesn't want to cooperate, the subsequent wrangling will go better if the FSF still has the "We'll go public with this" bargaining chip on their side.
To me, it looks like anything but cosmetic -- the only "Look what it can do now!" features are support for needed devices (esp. USB), but there are major changes to the networking code, and/dev can now be a semi-magical filesystem (like/proc) if you're brave enough, which solves a great many problems (see Documentation/filesystems/devfs/*). Enable ipchains compatibility, configure devfs right, and nothing changes from your perspective, but everything under the hood is running much more smoothly -- which is the way it should be.
I patched to the prerelease (tho test12 gave me no problems) because I wanted to help Linus out (however infinitesimally) by making sure everything ran ok on my system before the official release, not because I expected my kernel to start doing anything worthwhile -- kernels don't really have to "do" anything; they just have to stay out the way and not crash.
Here, here. I hate to jump on the "Linux rules
OK" bandwagon, but the article missed a
fundamental point: Linux 2.4 is out. It
just hasn't been judged as officially stable yet.
I'm far from Linux-elite, and I've been using
test12 for more than a week now with no problems
(other than a single, correctible instance of pppd wierdness
that might have been indirectly caused by the
kernel.)
Let's hear it for slow releases. I'd be
very happy if KDE was as paranoid as Linus about
issuing a "stable" release, and as willing to
ignore the cries and complaints of them as do not
help with the coding.
And for those who are even more adventuresome, reactive honey pots can be configured to flood the intruder's IP, denying access not only to your own machine but to all potential victims.
Sounds like a bad idea to me... most attacks are launched from previously 0wned boxes.
It's not an easy question; certainly it should be, but the average user probably doesn't have the time or inclination to keep an up-to-date blocklist... also, most ISPs (I hazard to guess) are making less of a political statement with their blocklists than a pragmatic one -- they don't want their servers brought to their knees by spam, and so they take measures to prevent this happening.
In the end, of course, you can always vote with your wallet, or use a webmail service for your email if you don't like your ISP's terms.
While I agree that MAPS's actions here seem to be out of line, I support their right to recommend that any IPs they see fit be blackholed -- it's not like any ISPs are being legally required to use the RBL, as some places are censorware. MAPS built their trust with the community by being evenhanded and trustworthy; if they start making bad recommendations, people using the RBL will stop listening to them (just as they did, for the most part, to ORBS.)
Personally, I'm hoping Vixie sees the light. What's Media3 gonna do, terminate the account illegally and risk getting sued? Argue "but spam is wrong" in court when it happens? But hell, that's my opinion, and more people seem to want to listen to Vixie than me;-). That is, of course, their right, as it is his to recommend that they blackhole any damn IP that comes into his head to mention.
Slashdot Mirror
Not only is Cluely factually wrong, his argument doesn't make sense. Even if you pretend IIS is the most popular web server, and thus more often targeted by worms, that would still mean it's more often targeted by worms, and thus an unusually vulnerable platform. It being "not Microsoft's fault" won't keep your server secure any more than "not Linux's fault" will help it write NTFS any time soon.
It may or may not still blow (I haven't tried it), but there have been substantial changes. Andrea Arcangeli did a large rewrite in pre11 ("major VM merge.")
If you're looking for a stable VM, I've heard a handful of good things (like this) about 2.4.9-ac10. Alan's been much more cautious than Linus about merging VM changes.
Whups; I hadn't known about Linux libc. Thanks for pointing out my error. I guess I should tone down my rhetoric a bit, or at least make sure of my facts first
The GNU project was founded with the explicit goal of producing a Free operating system. So was Linux. When the Linux kernel got functional, GNU was done, except for the kernel -- and the Linux people bolted GNU tool after GNU tool onto the system. Linux (the cool hack) gradually morphed into GNU/Linux (the full-featured Unix clone), and the name was never "officially" changed, even after the amount of system-essential GNU code had far exceeded the amount of system-essential Linux code.
On a Redhat system (for example),the C library, the compiler toolchain, bash, and all the command-line tools (ls, mv, chgrp, and the like) are all GNU tools, designed originally for use within an operating system called "GNU."
You can, of course, call the OS whatever you like. But one of the reasons RMS is so adamant about "GNU/Linux" is that "Linux" fosters the mistaken impression that all the GNU tools are optional add-ons like Gnome, the Gimp, or Gnumeric. You can try "rpm -e glibc" or "rpm -e libstdc++", or find/write replacements for these, if you still believe that they are.
I asked the guy at the next machine, "If you had to give a date, when would you say the dot-com collapse happened?" He said, "November '99."
According to this, that's within two months of the point at which marketing people got more popular than engineers (with employers.)
Yes, fascinating.
The lesson here is: Don't buy .biz domains. They already collide with OpenNIC's .biz domain, which means that if OpenNIC gains any popularity, your domain name may not function.
How much are you willing to bet that the internet will still be following a pigheadedly self-serving organization like ICANN five years from now?
Agreed. Here's a bit by Brett in which he lays out his views on the GPL ("The GPL ... was designed explicitly to hurt programmers' livelihoods.") and Stallman (who "says that good wages for programmers should be 'banned.'")
This common misunderstanding is part of why RMS is so adamant about "GNU/Linux." A modern Linux system uses the GNU project's system libraries, compiler toolchain, and (mostly) command-line Unix tools (tar, gzip, etc.) Without any one of these, Linux couldn't function as a modern Free OS -- they're not "trivial" add-ons like Perl or Apache.
I personally say "Linux," probably because I'm afraid of looking silly. It is true, though, that there's more GNU code on your machine than Linux (i.e. kernel) code, and it's just as necessary to get your bash prompt to come up. Some people say it's "more necessary" (since GNU has a kinda-sorta-almost-working kernel, but AFAIK gcc and glibc have no existing Free replacements), but that just starts flamewars.
I highly recommend showing people how insecure telnet is -- in a dorm, for example, pop up ethereal on one machine and log in over telnet from a machine in a different room. Follow TCP stream, and point to your real password displayed on the screen. This is more effective than lecturing people about TCP/IP and ethernet, and I've only had one guy start asking dismaying questions about how to sniff other people's passwords.
Change your password after, of course. Now if only there were an equivalent way to get people to use PGP...
You've hit the nail on the head, I think... if I had my way, we'd have no truth in advertising whatsoever. Car commercials would show the cars going 200mph, then extruding wings and lifting off to shoot down the Soviet invaders, all for just $19.95. Fast-food places would say that their milkshakes cured cancer. Microsoft would say that failure to use their software was a license violation punishable by law. People would have to actually do some research, or talk to their friends, to find out which products were good enough to buy, everyone would get accustomed to the idea that the stuff that comes out of corporate mouthpieces is greed-laced extract of horseshit, and we'd all be a lot better off.
Similar things apply to the laws that keep Las Vegas "fair" by limiting the casinos to removing your money at a fixed, gradual rate, but I digress...
A large problem with this (which is mentioned in the linked articles, but who has time to read those?) is that a lot of existing software assumes that the hostname-to-IP mapping is global to the internet; email handlers, search engines, and transparent web proxies are three examples. There's also the madness that results when non-authoratative DNS records manage to cross over into machines that aren't "loyal" to the agency that defined them.
D00D U CAN JUST USE UUCP
UUCP ROKS MY DAD HAS A DIAL UP 4 EMALE
.
Slipshod as it is, the following worked quite well for me back in the beta3 days; it assumes all the mp3s have filenames of the form "Artist - Title.mp3". If you want to nuke your mp3s as you go, remove the # from the obvious place (after making sure it works.) It needs mpg123 and vorbis-tools. Change "-b 128" to encode at a different bitrate.
.*//"`
//"`
#!/bin/bash
RANDOM=$$$(date)
TEMP=/tmp/mp32ogg-tmp.$RAND
while [ "$1" != "" ]; do
NAME=`echo $1 | sed s/.mp3//`
mpg123 -t -n 1 "$NAME.mp3" >& $TEMP
STATS=`grep kbit/s $TEMP`
ARTIST=`echo $NAME | sed "s/ -
TITLE=`echo $NAME | sed "s/.* -
rm -f $TEMP
mpg123 -s -r 44100 --stereo "$NAME.mp3" | \
oggenc -r -o "$NAME.ogg" -b 128 -c \
"Encoded from mp3 ($STATS)" -t "$TITLE" -a \
"$ARTIST" - #&& rm -f "$NAME.mp3"
shift
done
Hack the seds to taste if your mp3s are systematically named; if they aren't, root around in $TEMP for tags or use this (which discards title & artist):
#!/bin/bash
RANDOM=$$$(date)
TEMP=/tmp/mp32ogg-tmp.$RAND
while [ "$1" != "" ]; do
NAME=`echo $1 | sed s/.mp3//`
mpg123 -t -n 1 "$NAME.mp3" >& $TEMP
STATS=`grep kbit/s $TEMP`
rm -f $TEMP
mpg123 -s -r 44100 --stereo "$NAME.mp3" | \
oggenc -r -o "$NAME.ogg" -b 128 -c \
"Encoded from mp3 ($STATS)" - #&& rm -f \
"$NAME.mp3"
shift
done
I haven't checked that it still works in beta 4. Caveat emptor, don't blame me if it hoses your partition table, etc. etc.
Innovation, (n): Anything that does what it's supposed to do. See also "freedom"; both definitions have been recently updated.
It seems like most of the article was about making an artificial distinction between "lowly consumer-level stuff" and Enterprise Level Computing, with the strong implication that Powerful Businessmen (the people interviewed: a vice president, a CTO, a chairman, a Data Center Manager, and, for some reason, an analyst) need Enterprise Level Computing, which Linux still doesn't do.
Shit, man, it works or it doesn't. Maybe (as the analyst lucidly pointed out near the end) the OEMs and ISVs need to put out ERP and CRM with the SMP and raw I/O that the 2.4 kernels can provide. Or you could just write me a check right now, sir, and I'll see that it gets done.
It may be, for example, that the company (particularly if its Indian developers' grasp of English doesn't extend to legalese) doesn't properly understand the difference between GPLed code and public domain code. In the case that the company doesn't want to cooperate, the subsequent wrangling will go better if the FSF still has the "We'll go public with this" bargaining chip on their side.
I patched to the prerelease (tho test12 gave me no problems) because I wanted to help Linus out (however infinitesimally) by making sure everything ran ok on my system before the official release, not because I expected my kernel to start doing anything worthwhile -- kernels don't really have to "do" anything; they just have to stay out the way and not crash.
Let's hear it for slow releases. I'd be very happy if KDE was as paranoid as Linus about issuing a "stable" release, and as willing to ignore the cries and complaints of them as do not help with the coding.
You think you're joking...
In the end, of course, you can always vote with your wallet, or use a webmail service for your email if you don't like your ISP's terms.
works as well.
Problem solved.
Personally, I'm hoping Vixie sees the light. What's Media3 gonna do, terminate the account illegally and risk getting sued? Argue "but spam is wrong" in court when it happens? But hell, that's my opinion, and more people seem to want to listen to Vixie than me ;-). That is, of course, their right, as it is his to recommend that they blackhole any damn IP that comes into his head to mention.