Slashdot Mirror

This guy is one sick man, and sounds like a dirty pedophile (he's obsessed with 14 year old boys masturbating ). Read the Linux sucks part. He's gone though so much trouble compiling this page. But the best part is this piece of irony:


Throughout all of these, it's interesting to note the typical Linux kiddie reaction to proof that their OS sucks ass. It's always something like:

1. The test wasn't "fair"
2. What about new kernel x.y.z?
3. You can't expect
4. The people doing the test must be mean/biased
5. It wasn't tuned properly
6. They didn't look at the latest release of Red Hat x.y!

They really seem like 4-year-olds who have just been denied a pack of gum in a grocery store.


Hmm... thats seems strangely familiar...

Apparently he doesn't realize that Linux has "slowass network code":

http://www.spatula.net/proc/linux/localhost.src

Apparently he doesn't realize that Linux has "slowass network code":

http://www.spatula.net/proc/linux/localhost.src

"[to save Slashdot users' bandwidth, a reply about how Gentoo GNU/Linux does most of this stuff, too, and some of it (like making package repositories) in an easier way has been deleted from this space]"

I know that you're making fun of Gentoo zealots, but in the process, you're in danger of awaking a sleeping giant: The BSD Snob. Because you didn't think before posting, innocent Slashdot readers will be forced to read how the BSDs are better designed, more carefully developed, and are more portable across different platforms. Readers will even be forced to endure accusations that, being Linux users, they wet the bed. Gentoo certainly has its zealots, but BSD users have been looking down their noses at AT&T UNIX since, like, the 1970s. They're the original OS zealots!

See, you've unleashed an Army of Darkness upon us all. Where's Bruce Campbell when you need him?

Steve
Linux and BSD User

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Here's a short list of Linux flaws that make it look silly:

* /usr/include/linux (come on. honestly.) Lame. Nonstandard. (for the clue-deprived, this means that any code written for linux using the linux/ headers will be incompatible with all other Unix flavors.) Guess what: string.h, types.h, malloc.h, signal.h, and so-on don't belong in a platform-specific include directory. Hope you didn't want to port your code...
* Neither the sigaction manpage nor the signal.h includs indicate what the system defaults are. Of course, they've put signal.h in /usr/include/linux...
* "intro" manpages are a joke. Compare the BSD section 2 intro with the one from Linux.
* file systems mount async by default (power outage and your fs dies)
* Most linux users don't have pubes yet and are intolerably lame (3Y3 4m 1337 H4x0r d00d [uz 3y3 h4v3 L1Nux!)
* Too many things in user space that belong in the kernel (nfs)
* Too many things in the kernel that belong in user space (java)
* No standard distribution. Linux people say this is a good thing? Try writing software or software configuration instructions when you never know how the OS is going to be laid out, or try finding the responsible party for a block of OS code, or try fixing security problems when they arise and you'll see that this is NOT a good thing at all.
* no consistant pronunciation the os'es name (line-ucks? lynn-ucks?)
* svr4? bsd? make up your mind?
* Lame NFS & dd
* #linux, #hack, #linuxwarez...
* New kernel every week that breaks half your applications
* Security flaw/Root compromise of the week (see below)
* glibc? libc? libc5? libc6? glibc2?
* /bin/sh != sh; /bin/sh == bash. Lame. Nonstandard. Result: broken shell scripts and nonportable code.
* /usr/bin/make != make; /usr/bin/make == gmake. Lame. Nonstandard. Same result as above: nonportable code.
* ext2fs
* Linux will mount partitions that are not clean
* can't handle partitions > 2GB (i've hear they finally fixed this one)
* e2fsck deliberatly leaves/creates corrupt files (if there is a block that it duplicate between two files, e2fsck will clone the duplicate (while fsck will remove both files. This can also result in a user gaining unauthorized access to another user's data.))
* it swap likes swap to swap swap too swap often swap
* only allows 128M of swap at a time; for a 1G of swap, you need 8 swap partitions
* can't handle more than 1GB of RAM
* To install Joe's program, you need Bob's kernel hack, but for Bob's kernel hack, you've got to have Suzy's patches, but Suzy's patches only work with a year-old kernel, unless you get Mike's patches to Suzy's patches, but even then, those conflict with Jeff's drivers, which can be resolved only by installing Nancy's patches...
* Can't handle the same IP on more than one interface
* Can't handle large files
* Max file size: 2GB. (*BSD: 4 Terabytes)
* Dynamically linked root shell. Doom!
* lilo! any boot loader that needs to have magic block numbers is wrong
* linux icmp.h is *NOT* unix icmp.h - they're totally incompatible.
* flatfile password files make listing large ftp directories impossible due to huge numbers of flatfile searchces.
* password file can be non-shadowed - encrypted passwords visible to all
* shadow.h! hahahahahahaha!
* Slowass network code
* Did I mention slowass network code?
* Oh, also slowass network code
* Miserably pathetic threading implementation doesn't scale for shit: all threads wake up on signals (stampeding process problem).
* L1nux c0d3rz!
* LILO can't cope with kernels > 1Mb, so the kernel has to be gzipped.
* strfry and memfrob
* Can't cope with hard drives > 32GB
* GPL - a license and a virus
* Fundamental design and direction problems. It turns out that Linus is not the smartest man in the world and the saviour of all mankind.
* OS or religion?
* UNABLE TO LOAD INTERPRETER...memory leak much?
* This is a real Linux error message: Uhhh. NMI recieved. Dazed and Confused. Trying to cope ...such professionalism!
*The GNU su manpage actually says this:
This program does not support a "wheel group" that restricts who can su to super-user accounts, because that can help fascist system administrators hold unwarranted power over other users. ...apparently it's better for any user to attack the root password than to offer added security. Ignorance of security is a common Linux thread.
* vi != vi; vi == vim. vim links to X libraries. Wipe X, and now you can't use vi. Retards.
* Still no USB support in 2000, after NetBSD and FreeBSD have had it for nearly 2 years. So much for the "million geeks" theory of rapid software development.
* Always trying to help you hold your weewee when you're going tinkle.
* No version control used to manage the system.

Why Linux Sucks

Nick Johnson wrote a spam quotient program which can detect spam based on word frequencies also.

You can make your own barcodes online here.

It never ceases to amaze me how something stupid can proliferate. Take, for example, the following quote, which you'll find in people's signatures everywhere:

"There are two major products that came from Berkeley: LSD and Unix. We don't believe this to be a coincidence."

"Two things came out of Berkeley: BSD and LSD. We don't believe this to be a coincidence."

The quote is usually attributed to "J.S. Anderson" or "Jeremy S. Anderson".

The problem here is that both quotes are ncorrect. First, LSD did not come from Berkeley. LSD was developed in Sandoz labs in Basel, Switzerland. Second, BSD did come from Berkeley, but it is not "Unix". "Unix" was until recently a trademark of AT&T. I believe the Santa Cruz Operation is the most recent holder of the trademark. BSD is a UNIX flavour but is not Unix.

This is probably a case of false authority syndrome. Did anyone think to question this "J.S. Anderson" or his credentials? Does anyone know who he is now? Do people question the validity of his statement before putting it in their signature files? Who is J.S. Anderson anyway? If you search for the name "Jeremy S. Anderson" on the web, all you will find are quote pages containing the aforementioned misinformed quote. For all we know, Jeremy S. Anderson might not even be a real person.

Knowing all of this, then, what would possess people to put a false statement from someone they don't know at the bottom of all their email or usenet posts without questioning it at all?

source

I wonder why it is that every *BSD coder/user i meet has to slam Linux this way? are they scared thier little OS will get forgotten and trampled by popularity of linux? probably. Personaly I can see a LOT of parallels of the old OS/2 vs. Windows wars in the *BSD vs. Linux wars. I think they also see this and are deathly afraid of being forgotten like OS/2 was. If I were the *BSD guys i would stop being so closed and simple minded and go out and make people aware of thier OS in a productive way. Simply screaming "But MY os is better than yours!" isn't going to win any IT managers. PROOVE IT. And no i'm not talking of places like ht tp://www.spatula.net/proc/linux|0687a4b2bf8e7f720f 6b1bf144e39acb4fd9/index.src that the #FreeBSD kiddies are spreading around. (BTW this page is so out of date and biased it's funny just to read. :) )
Sincerely,
another FreeBSD user.