He's also wrong. Try even administering NFS and NIS under Solaris vs. doing so under the major Linux distributiobns. You'll find that Webmin is your friend and makes it all much simpler than the Solaris tools.
The Xorg development has taken a quantum leap from XFree86, a leap restrained by silly licensing from the XFree86 people and by their refusal to deal with platform-level compatibility problems like the CygWin fixes.
For data DVD's and CD's, cdrecord and k3b are more than enough. For video, though, duplicating DVD's enters interesting legal territory. The libdvdcss libraries often used for Linux video DVD burning have been ruled illegal in several countries. Getting a clean copy of a legal, licensed, software package to do DVD burning and avoid the potential liability is understandable.
Also, Nero is considerably better in its interfaces than even k3b.
"One" mistake? The man tried to create an Imperial Presidency, one not bound by the laws of the land nor by the interests of its citizens.
Come to think of it, sounds like Bill Gates should grow big jowls and start saying "My Fellow PC-Users" to get the rest of Nixon's act right. He already did the "Only Nixon could go to China" trick by showing up at the MacWorld Expo on screen somem years back.
And the later theft of core DEC operating system technologies for NT, by hiring David Cutler away along with his cronies and taking much of David's operating sytem work on VMS and the Prism development project with him.
Check out the many, many articles on the DEC lawsuit with Microsoft, and how they settled for making NT always run on Alphas. Ooops, the Alpha hardware secrets got stolen by Microsoft's bed-buddy, Intel? Too bad how that happens when you focus on building new technologies and prefer to settle out of court, rather than actually convicting the felons and making them stop stealing.
Nice try again. No, the NIS is broken above and beyond the call of duty and doesn't work right with Solaris clients or servers, either. The lpd daemon uses options that are not documented and don't work, in particular in the filtering capacity, when dealing with simple network printers.
The shipped compiler refuses to follow simple standards of lexical scoping. And it makes up "include" structures out of the compromises of the OSF instead of following any one standard in a nightmare for stability, especially when include files fail to flag that they've been already been included and thus reset values when they get re-included later with different configurations. It's nasty: what it produces is faster than gcc compiled code due to to the optimizations, but it means your code is not portable to other compilers such as gcc or even the various Sun compilers, or sometimes to compilers on slightly different releases of Tru64.
The inability of a vendor to publish up-to-date versions of core tools, like sendmail, is not an excuse to say "oh, people just install their own anyway because no one keeps it up to date". Other vendors do keep theirs up to date, including several core UNIX vendors like Sun and every flavor of Linux.
Nice try. I've got 4 years hands-on experience with it, trying to keep it running in a mixed environment. The NIS is broken, the printing services don't follow the documentation nor anyone else's standards, the built-in compiler doesn't handle recent open source code because it's not compliant with any other standards, the NFS is poor, and the sendmail is so old and non-standard it should be called Neanderthal sendmail, having forked off into a species that died sometime in the paleolithic.
It's possible to replace a lot of the tools with more powerful, open source ones, but once you've done that you may as well use Linux in the first place.
I agree that HP tried to do the same trick. Unfortunately, with the so-called "open source but not really" software that Tru64 was built on, there was no point to that. The most stable, supportable, maintainable use for Alpha hardware these days is running Linux on it.
Implementation counts for a lot. Coupled with the lower price of the hardware from Intel for the desktop market, and their strong relationship with Microsoft so that new consumer actually worked on it, it was possible for Intel to simply underprice DEC and Alpha technologies for almost all new hardware. Having to implement those technologies on their own would have slowed them down by at least one year, maybe three, and cost them a lot of the mid-range business market and high-end consumer market.
If you want to make money this quarter or this year, it's much easier to steal the good stuff from a company that supports R&D than it is to maintain your own R&D. Carly might have tried that to keep HP advancing, but new developments large enough to fund new businesses for a conglomerate that size are rare and hard to steal.
Sorry, friend, Alpha was already dead. Many of tThe core technologies had been stolen by Intel and woven into the Pentium chipsets, and AMD has finally brought real 64-bit computing into the world at a price point and with source operating systems that people can actually leave. DEC didn't have the resources to bring Alpha technologies to the next physical implementation, and there wasn't software worth running on it.
The Linux-compatible filesystem stuff out of IBM is pretty cool, and they've been putting some serious work into getting their drivers and tools into the Linux kernel to support products they want to sell on the market. That's hard work, and it's been good code and good R&D doing it.
Oddly enough, the lab of 50 PhD's in the US tends to do better for long-term innovation. The ability to "think outside the box" is not as common in most underpaid countries. But industrial efficiencies are well within their typical skills, often because they worry less about EPA and worker safety and stepping on the toes of departmental prima donnas.
Kevin also trashed systems in the process. Find some old DEC employees and ask what he did to to the documentation and backup systems while he was cracking in. Some groups lost months of work due to Mitnick.
Vandalism on that scale is as bad as theft.
"Mean-spirited", my ass. Mitnick was a vaguely competent cracker, and determined. But he did *incredible* damage to other people's systems, for example when he trashed core systems at DEC and wiped out months of people's hard work because the backup system had been corrupted, and was socially stupid when he continued committing crimes while taking money and protection from the FBI.
Kevin was never a "hacker" in the sense of someone who works his way around systems to figure out how they work and make them better. He was a "cracker" in the sense of someonen who wants in and doesn't care about the damage he does. Kevin should still be in jail, not on the streets.
"Please" yourself. Strong passwords get stolen, when people give them out, when they use the same password for their banking as they use for their FTP site, when their computer gets hacked and it's stolen from their email log-in, etc., etc.
Robust single-sign-on password systems such as Kerberos, with an enforced "change your damn password once a year" policy, help quite a lot. But nothing fixes the VP who insists on using his wife's birthday as his password for everything.
No, when they found out the guy had an SO and didn't tell them, they take up with each other and leave him out in the cold. Or, because they share similar tastes, they both take on some new guy who's "sensitive".
My post was modded "informative" because I actually play with BIOS's.
> How did you manage to be moderated informative? My mind is boggling so much i'm starting to feel dizzy...
Because you've hand-waved away the BIOS level reporting into "ACPI does that for you", and consistently left out the bits that are still accessable at BIOS levels only (such as setting boot-on-power-failure behavior, setting boot device orders, enabling serial console, hard-coding IRQ's and other stuff I do at least once a month). A lot of ACPI functionality is deduced guesswork: open source BIOS would remove a huge amount of the guesswork and make the code controllable and reparable.
"Trusted Computing" used to be called "Palladium", but it got so trashed and exposed as an excuse for Microsoft to prevent anyone else from being able to read their files, and even potentially from being able to boot non-Palladium signed operating systems, that they changed the name. Richard Stallman was one of the people who was really raising red flags about its management of core parts of your hardware and denying access to other, non-Microsoft controlled software.
Like putting RFID tags in everyone's backside, there are real potential benefits but incredible social risks of the approach. And "Trusted Computing" is precisely one of the things that an open-source BIOS community would help manage and keep from doing things it blatantly *should not* do, such as be used to prevent motherboard makers from preventing you from using any OS other than their vendor-approved one (Windows).
Slashdot Mirror
Bush was in Fahrenheit 911, and he's a *rotten* actor. Why do we keep recasting him?
And what a wonderful pair of good looks they were, too....
Go to India, and get a job at a tech support call center.
He's also wrong. Try even administering NFS and NIS under Solaris vs. doing so under the major Linux distributiobns. You'll find that Webmin is your friend and makes it all much simpler than the Solaris tools.
The Xorg development has taken a quantum leap from XFree86, a leap restrained by silly licensing from the XFree86 people and by their refusal to deal with platform-level compatibility problems like the CygWin fixes.
Or Akamai. They had something like 20,000 Linux systems live at the peak of the dotcom bubble, and may have more than that alive today.
Thank you for checking it out and giving us the warning that it's not there yet.
Not for DVD's, you usually need growisofs for burning those.
For data DVD's and CD's, cdrecord and k3b are more than enough. For video, though, duplicating DVD's enters interesting legal territory. The libdvdcss libraries often used for Linux video DVD burning have been ruled illegal in several countries. Getting a clean copy of a legal, licensed, software package to do DVD burning and avoid the potential liability is understandable.
Also, Nero is considerably better in its interfaces than even k3b.
"One" mistake? The man tried to create an Imperial Presidency, one not bound by the laws of the land nor by the interests of its citizens. Come to think of it, sounds like Bill Gates should grow big jowls and start saying "My Fellow PC-Users" to get the rest of Nixon's act right. He already did the "Only Nixon could go to China" trick by showing up at the MacWorld Expo on screen somem years back.
And the later theft of core DEC operating system technologies for NT, by hiring David Cutler away along with his cronies and taking much of David's operating sytem work on VMS and the Prism development project with him.
Check out the many, many articles on the DEC lawsuit with Microsoft, and how they settled for making NT always run on Alphas. Ooops, the Alpha hardware secrets got stolen by Microsoft's bed-buddy, Intel? Too bad how that happens when you focus on building new technologies and prefer to settle out of court, rather than actually convicting the felons and making them stop stealing.
Nice try again. No, the NIS is broken above and beyond the call of duty and doesn't work right with Solaris clients or servers, either. The lpd daemon uses options that are not documented and don't work, in particular in the filtering capacity, when dealing with simple network printers.
The shipped compiler refuses to follow simple standards of lexical scoping. And it makes up "include" structures out of the compromises of the OSF instead of following any one standard in a nightmare for stability, especially when include files fail to flag that they've been already been included and thus reset values when they get re-included later with different configurations. It's nasty: what it produces is faster than gcc compiled code due to to the optimizations, but it means your code is not portable to other compilers such as gcc or even the various Sun compilers, or sometimes to compilers on slightly different releases of Tru64.
The inability of a vendor to publish up-to-date versions of core tools, like sendmail, is not an excuse to say "oh, people just install their own anyway because no one keeps it up to date". Other vendors do keep theirs up to date, including several core UNIX vendors like Sun and every flavor of Linux.
Tru64 is moribund.
Nice try. I've got 4 years hands-on experience with it, trying to keep it running in a mixed environment. The NIS is broken, the printing services don't follow the documentation nor anyone else's standards, the built-in compiler doesn't handle recent open source code because it's not compliant with any other standards, the NFS is poor, and the sendmail is so old and non-standard it should be called Neanderthal sendmail, having forked off into a species that died sometime in the paleolithic.
It's possible to replace a lot of the tools with more powerful, open source ones, but once you've done that you may as well use Linux in the first place.
True, but most of them can't write in their native Perl, either.
The old Compaq support people are actually quite good, but they're being phased out by HP.
I agree that HP tried to do the same trick. Unfortunately, with the so-called "open source but not really" software that Tru64 was built on, there was no point to that. The most stable, supportable, maintainable use for Alpha hardware these days is running Linux on it.
Implementation counts for a lot. Coupled with the lower price of the hardware from Intel for the desktop market, and their strong relationship with Microsoft so that new consumer actually worked on it, it was possible for Intel to simply underprice DEC and Alpha technologies for almost all new hardware. Having to implement those technologies on their own would have slowed them down by at least one year, maybe three, and cost them a lot of the mid-range business market and high-end consumer market.
If you want to make money this quarter or this year, it's much easier to steal the good stuff from a company that supports R&D than it is to maintain your own R&D. Carly might have tried that to keep HP advancing, but new developments large enough to fund new businesses for a conglomerate that size are rare and hard to steal.
Sorry, friend, Alpha was already dead. Many of tThe core technologies had been stolen by Intel and woven into the Pentium chipsets, and AMD has finally brought real 64-bit computing into the world at a price point and with source operating systems that people can actually leave. DEC didn't have the resources to bring Alpha technologies to the next physical implementation, and there wasn't software worth running on it.
The Linux-compatible filesystem stuff out of IBM is pretty cool, and they've been putting some serious work into getting their drivers and tools into the Linux kernel to support products they want to sell on the market. That's hard work, and it's been good code and good R&D doing it.
Oddly enough, the lab of 50 PhD's in the US tends to do better for long-term innovation. The ability to "think outside the box" is not as common in most underpaid countries. But industrial efficiencies are well within their typical skills, often because they worry less about EPA and worker safety and stepping on the toes of departmental prima donnas.
Kevin also trashed systems in the process. Find some old DEC employees and ask what he did to to the documentation and backup systems while he was cracking in. Some groups lost months of work due to Mitnick. Vandalism on that scale is as bad as theft.
"Mean-spirited", my ass. Mitnick was a vaguely competent cracker, and determined. But he did *incredible* damage to other people's systems, for example when he trashed core systems at DEC and wiped out months of people's hard work because the backup system had been corrupted, and was socially stupid when he continued committing crimes while taking money and protection from the FBI. Kevin was never a "hacker" in the sense of someone who works his way around systems to figure out how they work and make them better. He was a "cracker" in the sense of someonen who wants in and doesn't care about the damage he does. Kevin should still be in jail, not on the streets.
"Please" yourself. Strong passwords get stolen, when people give them out, when they use the same password for their banking as they use for their FTP site, when their computer gets hacked and it's stolen from their email log-in, etc., etc.
Robust single-sign-on password systems such as Kerberos, with an enforced "change your damn password once a year" policy, help quite a lot. But nothing fixes the VP who insists on using his wife's birthday as his password for everything.
No, when they found out the guy had an SO and didn't tell them, they take up with each other and leave him out in the cold. Or, because they share similar tastes, they both take on some new guy who's "sensitive".
I've seen both happen.
My post was modded "informative" because I actually play with BIOS's.
> How did you manage to be moderated informative? My mind is boggling so much i'm starting to feel dizzy...
Because you've hand-waved away the BIOS level reporting into "ACPI does that for you", and consistently left out the bits that are still accessable at BIOS levels only (such as setting boot-on-power-failure behavior, setting boot device orders, enabling serial console, hard-coding IRQ's and other stuff I do at least once a month). A lot of ACPI functionality is deduced guesswork: open source BIOS would remove a huge amount of the guesswork and make the code controllable and reparable.
"Trusted Computing" used to be called "Palladium", but it got so trashed and exposed as an excuse for Microsoft to prevent anyone else from being able to read their files, and even potentially from being able to boot non-Palladium signed operating systems, that they changed the name. Richard Stallman was one of the people who was really raising red flags about its management of core parts of your hardware and denying access to other, non-Microsoft controlled software.
Like putting RFID tags in everyone's backside, there are real potential benefits but incredible social risks of the approach. And "Trusted Computing" is precisely one of the things that an open-source BIOS community would help manage and keep from doing things it blatantly *should not* do, such as be used to prevent motherboard makers from preventing you from using any OS other than their vendor-approved one (Windows).