I know it was meant in humor, but the Macintosh is dead? Guess the Macs at home and the Macs at work didn't know this yet, I'll be sure to clue them in:)
Interesting.. So are you advocating all the rabid Linux advocates who ignore everything not Linux should do the same, and perhaps be a little more open minded about operating systems? Or is this merely a one-way street where BSD users must bow down and acknowledge Linux and Linux may completely ignore BSD? For every Linux driven site you name, I *know* I can name a BSD driven site. Arguing over that is pointless.
khttpd is tied specifically to a kernel. Big deal. I could run khttpd with small modifications to the FreeBSD kernel. Why would I want to burden a kernel with such a specific userland task anyhow? I'm baffled.
Oh yes, one last thing, I'm terribly impressed by your argument. *eye roll*
Let's turn your "articulate" argument around. How about you provide some hard facts and figures pointing out how the Linux TCP/IP stack is better? I constantly see whiners say that there is no evidence that the BSD stack is better (which is a lie, go search Google for statistics if you like) yet they are unwilling to back up their own statements.
The number of errors of logic (among other errors) in your post leads me to believe that you aren't knowledgable enough to make the judgement that "BSD doesn't matter". What is POSTIX? Perhaps you mean POSIX, and no, the Linux kernel cannot be called "POSIX" complient because that in itself has no real meaning. As for the move to ELF, it was motivated by necessity, not by "gee whiz, let's incorporate this new thing".
Oh.. one other thing. I can run 99.99% of the binary-only applications on FreeBSD that were compiled for Linux x86, ELF or otherwise. So perhaps that means BSD (FreeBSD, in this case) can actually do more than Linux because I can run all your binaries *plus* binaries for BSD.
Please stop looking at the world through fiercely over-zealous glasses. "Corporate code" as you call it does not always equate with poor quality code. Not all open source projects are examples of crystal clear coding, either.
Uh, no. One form of autoconfiguration avaliable in IPv6 hosts is to embed the EUI64 (derived from the ethernet address) into the IPv6 address. Other methods are DHCPv6, or just using a number at random. Please don't spread alarm where it isn't necessary.
Umm.. man pkg_add. There's your package management system. FreeBSD has ports, and packages are basically pre-compiled ports. Management is take care of by keeping track of dependancies and such in/var/db/pkg.
Nonsense. Nobody has restricted the code base from which this hypothetical "proprietary" product was produced. This anti-BSDL argument is such a joke and I get tired of enlightening people about it's faulty logic.
I realize the audio is uncompressed when you play, but MP3 is lossy and it just sounds "odd" when copied to MiniDisc. 192 and 256 Kbps MP3 encodings sound fine to my ear, but 128 and even 160 Kbps go "funky". Ah well, I suppose it's mostly a matter of how trained your ear is to pick anomolies up anyways.
Why is it so abhorrent for some people to pay money for good quality drivers, just because they don't give away their source? I didn't feel bad paying my $30 for 4Front drivers.
Ugh. I've been doing this already for a little while, and it's not really worth it. Use uncompressed audio to write to MiniDisc; MP3 just is already compressed, and something "funky" happens to the audio when the ATRAC encoding gets ahold of it.
Hopefully they will *not* be GPL'd so other operating systems can benefit by Aureal's decision. Even the LGPL would be preferable so 4Front could integrate this into their early Vortex support..
What winning? Is this a race? You can't view the programming world as a win/lose game. It doesn't work like that. Unless you want to be viewed as very anti-social, you work with others. There is no harm in working with "proprietary" vendors; there is a place for both kinds of software in this world. Don't narrow your views.
What is ths gibberish about Steve Jobs? The Apple bashers amaze me in their ability to bash Apple in a thread totally unrelated to the MacOS or Apple. Grow up, people.
What's wrong with concentration on code purity? Do you advocate tossing in just any old feature or modification into a large and complex software project? Nothing stops you from grabbing the sources and using your modifications, enhancements, or features. Don't spread FUD. The NetBSD group have found a method that works for them to produce high-quality production code. Who the hell are you to criticize the work they have done?
Does it matter? Use the right tool for the right job; Linux isn't always the right tool.. not everything is a nail when the only tool you insist on using is a hammer.
There should be no more concern about IPv6 addresses than there should be about IPv4 addresses. It's just a number, no tie to any sort of geographical identifier. It's a non-issue in reality.
Slashdot Mirror
If you understand the technical issues behind USB and "FireWire", you would know that they solve two different problems.
I know it was meant in humor, but the Macintosh is dead? Guess the Macs at home and the Macs at work didn't know this yet, I'll be sure to clue them in :)
Interesting.. So are you advocating all the rabid Linux advocates who ignore everything not Linux should do the same, and perhaps be a little more open minded about operating systems? Or is this merely a one-way street where BSD users must bow down and acknowledge Linux and Linux may completely ignore BSD? For every Linux driven site you name, I *know* I can name a BSD driven site. Arguing over that is pointless.
khttpd is tied specifically to a kernel. Big deal. I could run khttpd with small modifications to the FreeBSD kernel. Why would I want to burden a kernel with such a specific userland task anyhow? I'm baffled.
Oh yes, one last thing, I'm terribly impressed by your argument. *eye roll*
Let's turn your "articulate" argument around. How about you provide some hard facts and figures pointing out how the Linux TCP/IP stack is better? I constantly see whiners say that there is no evidence that the BSD stack is better (which is a lie, go search Google for statistics if you like) yet they are unwilling to back up their own statements.
The number of errors of logic (among other errors) in your post leads me to believe that you aren't knowledgable enough to make the judgement that "BSD doesn't matter". What is POSTIX? Perhaps you mean POSIX, and no, the Linux kernel cannot be called "POSIX" complient because that in itself has no real meaning. As for the move to ELF, it was motivated by necessity, not by "gee whiz, let's incorporate this new thing".
Oh.. one other thing. I can run 99.99% of the binary-only applications on FreeBSD that were compiled for Linux x86, ELF or otherwise. So perhaps that means BSD (FreeBSD, in this case) can actually do more than Linux because I can run all your binaries *plus* binaries for BSD.
Please stop looking at the world through fiercely over-zealous glasses. "Corporate code" as you call it does not always equate with poor quality code. Not all open source projects are examples of crystal clear coding, either.
I can't let this slide. Linux did *NOT* originate the ELF binary format.
Uh, no. One form of autoconfiguration avaliable in IPv6 hosts is to embed the EUI64 (derived from the ethernet address) into the IPv6 address. Other methods are DHCPv6, or just using a number at random. Please don't spread alarm where it isn't necessary.
Umm.. man pkg_add. There's your package management system. FreeBSD has ports, and packages are basically pre-compiled ports. Management is take care of by keeping track of dependancies and such in /var/db/pkg.
Show some facts, benchmarks, something to prove your statement. You have nothing to back up your attempt at rabid advocacy.
Stomp on Sun? I hardly think so. Please keep the rabid advocacy to a minimum; this article wasn't about Linux, it was about the BeOS.
Nonsense. Nobody has restricted the code base from which this hypothetical "proprietary" product was produced. This anti-BSDL argument is such a joke and I get tired of enlightening people about it's faulty logic.
True, but did you see "[your OS] supported" on the box when you bought it? If you buy a Ford part but own a Volkswagon, do you get mad?
I realize the audio is uncompressed when you play, but MP3 is lossy and it just sounds "odd" when copied to MiniDisc. 192 and 256 Kbps MP3 encodings sound fine to my ear, but 128 and even 160 Kbps go "funky". Ah well, I suppose it's mostly a matter of how trained your ear is to pick anomolies up anyways.
Why is it so abhorrent for some people to pay money for good quality drivers, just because they don't give away their source? I didn't feel bad paying my $30 for 4Front drivers.
Ugh. I've been doing this already for a little while, and it's not really worth it. Use uncompressed audio to write to MiniDisc; MP3 just is already compressed, and something "funky" happens to the audio when the ATRAC encoding gets ahold of it.
Hopefully they will *not* be GPL'd so other operating systems can benefit by Aureal's decision. Even the LGPL would be preferable so 4Front could integrate this into their early Vortex support..
What winning? Is this a race? You can't view the programming world as a win/lose game. It doesn't work like that. Unless you want to be viewed as very anti-social, you work with others. There is no harm in working with "proprietary" vendors; there is a place for both kinds of software in this world. Don't narrow your views.
Simple, don't buy the extension. Use the non-infected version of AbiWord.
This isn't rocket science, people. Use your heads.
Just a small repair on your posting..
Under *UNIX* the VNC server cna have an independent display for each client connecting.
Linux is not the whole world, bub.
What is ths gibberish about Steve Jobs? The Apple bashers amaze me in their ability to bash Apple in a thread totally unrelated to the MacOS or Apple. Grow up, people.
What's wrong with concentration on code purity? Do you advocate tossing in just any old feature or modification into a large and complex software project? Nothing stops you from grabbing the sources and using your modifications, enhancements, or features. Don't spread FUD. The NetBSD group have found a method that works for them to produce high-quality production code. Who the hell are you to criticize the work they have done?
Does it matter? Use the right tool for the right job; Linux isn't always the right tool.. not everything is a nail when the only tool you insist on using is a hammer.
There should be no more concern about IPv6 addresses than there should be about IPv4 addresses. It's just a number, no tie to any sort of geographical identifier. It's a non-issue in reality.