I have built and used Linux with non-GNU userland. There are alternate C libraries available, along with alternate shells, etc. I even used ICC to build everything. Only GNU product on there was the linker, which is also used by FreeBSD, et al. So by your logic, should FreeBSD be called GNU/FreeBSD?
It's not GNU/Linux you GNU/Twat. The typical Linux system has just as much, if not more, non-GNU software in it than GNU software that insisiting that it's GNU/Linux is idiotic, egotistical, and just plain silly. Typical Linux box has more software from other vendors, such as Apache, KDE, etc, than GNU. So by your moronic logic, should it be Apache/KDE/GNU/X11/Linux?
Part of me thinks that part of the reason for this very short cycle doesn't have to do so much with windows insecurities as the fact that it's so damn old, relatively speaking. The stock copy of Windows XP sold on the shelf right now is vulnerable to attacks patched back in 2001. Apple and Linux don't have this problem simply because the relatively short time to live of their distributions, and the fact that Apple at least seems more willing to provide version updates in with their retail boxes. Maybe it's time that MS looked at their sales practices and started actually slipstreaming patches into their boxes. Surely pressing a new master every couple months can't be that hard for their plants.
Only if the program is crap will it require administrator access. Well-written programs should be able to be installed to the home directory of the user with no problems.
C'mon, people, how can you forget Cyclops from the X-men and his eye beams. And of course, there what disaster film wouldn't be complete with the similarly named, but completely different I-Beams collapsing at just the right time for dramatic purposes?
Depends. A virus that just destroys these drives wouldn't spread very far, but a virus that destroys these drives along with other nasty affects would spread fairly well.
But the original topic was the kernel api, which has, by your own admission even, significant differences. Now if you were discussing userland, you may have had a point, but not kernel API
The problem is that many system utilities are designed to use that default shell, so if one has to diagnose an oddly booting system, then you can run into some problems if you aren't familiar with the scripting language.
They're separate projects. While Darwn may have started out with FreeBSD roots, that was several years ago. Both projects have moved on and changed considerably since then. At this point, having FreeBSD developers discuss Darwin's API is little more relevant than having Steve Ballmer discuss the BSD kernel API in Tiger.
Funny, the most functional Linux desktop setup for me looks nothing like windows at all. Yes, they start out looking like windows for sake of familiarity, but are quickly adaptable in ways windows is incapable of without a raft of 3rd party cpu hogging extensions and replacements.
Ick. More ramblings from a peak oil nutcase. Yes, there are problems, no they're not going to cause the end of civilization like the author of the site is suggesting.
So that by the time you're 65 and have made wise investment choices with your money, you'll be able to buy better medicines with the discoveries created in part by your miniscule investment in running protein folding simulations on an otherwise idle console. I think the prospect of a longer, fuller life is a damn good one, non?
The only reason that Fedex doesn't deliver first class mail is because it's against the law for them to do so. In the interests of universal service, the government decided that no one other than the postal service is allowed to deliver first class mail.
Well, it could be worse, he could have the european mindset of "throw money and bureaucrats at a problem until it goes away". I wouldn't trust them with anything that matters either. Best solution, like nearly everything, probably lies outside of government waste.
Intel's codenames are a bit more complex out of the necessities of a wide market. x86 is a wide market with hundreds of millions of processors. As a result, the players in making chips have to be more diverse in what they offer. Apple was easy because they usually only used one or two cores at a time; the x86 market is just too diverse for that.
I imagine there are still a few people who write apps using the oldschool win16 api. However, the situation is a lot different there as Win16 was obsoleted by newer software. There are still people who port software to the all but dead OS/2 platform as well; if there is a vested interest, say millions of users, there are going to be more than a few developers that keep that market running for a very long time.
The author was trolling the mac community when he said he got the G5 as a gift. He had gotten a case from a mac retailer friend and crafted the story that he got the G5 as a gift. After stating this, the more rabid maclots still bashed him out of some sense of righteous indignation.
I imagine it'll be a non-US developed software product, so not very much. The big distro makers won't bundle it, but people who want it will know where to get it.
Slashdot Mirror
I have built and used Linux with non-GNU userland. There are alternate C libraries available, along with alternate shells, etc. I even used ICC to build everything. Only GNU product on there was the linker, which is also used by FreeBSD, et al. So by your logic, should FreeBSD be called GNU/FreeBSD?
It's not GNU/Linux you GNU/Twat. The typical Linux system has just as much, if not more, non-GNU software in it than GNU software that insisiting that it's GNU/Linux is idiotic, egotistical, and just plain silly. Typical Linux box has more software from other vendors, such as Apache, KDE, etc, than GNU. So by your moronic logic, should it be Apache/KDE/GNU/X11/Linux?
Part of me thinks that part of the reason for this very short cycle doesn't have to do so much with windows insecurities as the fact that it's so damn old, relatively speaking. The stock copy of Windows XP sold on the shelf right now is vulnerable to attacks patched back in 2001. Apple and Linux don't have this problem simply because the relatively short time to live of their distributions, and the fact that Apple at least seems more willing to provide version updates in with their retail boxes. Maybe it's time that MS looked at their sales practices and started actually slipstreaming patches into their boxes. Surely pressing a new master every couple months can't be that hard for their plants.
I was told that duct tape was the force that bound the galaxy together, not gravity. Have I been lied to all this time?
Only if the program is crap will it require administrator access. Well-written programs should be able to be installed to the home directory of the user with no problems.
C'mon, people, how can you forget Cyclops from the X-men and his eye beams. And of course, there what disaster film wouldn't be complete with the similarly named, but completely different I-Beams collapsing at just the right time for dramatic purposes?
Depends. A virus that just destroys these drives wouldn't spread very far, but a virus that destroys these drives along with other nasty affects would spread fairly well.
But the original topic was the kernel api, which has, by your own admission even, significant differences. Now if you were discussing userland, you may have had a point, but not kernel API
The problem is that many system utilities are designed to use that default shell, so if one has to diagnose an oddly booting system, then you can run into some problems if you aren't familiar with the scripting language.
They're separate projects. While Darwn may have started out with FreeBSD roots, that was several years ago. Both projects have moved on and changed considerably since then. At this point, having FreeBSD developers discuss Darwin's API is little more relevant than having Steve Ballmer discuss the BSD kernel API in Tiger.
Uh, you know there's a difference between a port and emulation, right?
Funny, the most functional Linux desktop setup for me looks nothing like windows at all. Yes, they start out looking like windows for sake of familiarity, but are quickly adaptable in ways windows is incapable of without a raft of 3rd party cpu hogging extensions and replacements.
Here, pasting the results next to the columns it's logically related to. Trust me, Unix has assloads of text processing abilities. Use the shell for a while and you learn lots of nice little tricks and commands.
Ick. More ramblings from a peak oil nutcase. Yes, there are problems, no they're not going to cause the end of civilization like the author of the site is suggesting.
hence why I said and made wise investment choices
So that by the time you're 65 and have made wise investment choices with your money, you'll be able to buy better medicines with the discoveries created in part by your miniscule investment in running protein folding simulations on an otherwise idle console. I think the prospect of a longer, fuller life is a damn good one, non?
The only reason that Fedex doesn't deliver first class mail is because it's against the law for them to do so. In the interests of universal service, the government decided that no one other than the postal service is allowed to deliver first class mail.
Well, it could be worse, he could have the european mindset of "throw money and bureaucrats at a problem until it goes away". I wouldn't trust them with anything that matters either. Best solution, like nearly everything, probably lies outside of government waste.
Probably a problem with mysql. Y'know, all your database are belong to us and all...
Okay, so if I am an ISP that just deals with customers within my state, you'd exempt me, right?
Intel's codenames are a bit more complex out of the necessities of a wide market. x86 is a wide market with hundreds of millions of processors. As a result, the players in making chips have to be more diverse in what they offer. Apple was easy because they usually only used one or two cores at a time; the x86 market is just too diverse for that.
I imagine there are still a few people who write apps using the oldschool win16 api. However, the situation is a lot different there as Win16 was obsoleted by newer software. There are still people who port software to the all but dead OS/2 platform as well; if there is a vested interest, say millions of users, there are going to be more than a few developers that keep that market running for a very long time.
The author was trolling the mac community when he said he got the G5 as a gift. He had gotten a case from a mac retailer friend and crafted the story that he got the G5 as a gift. After stating this, the more rabid maclots still bashed him out of some sense of righteous indignation.
I imagine it'll be a non-US developed software product, so not very much. The big distro makers won't bundle it, but people who want it will know where to get it.
Nah. I'll just be counting the days until they port Mac On Linux to the x86. I give it 27 days.