But there's no money to be made with p2p networks the way things are now. There is virtually an unlimited supply of 16-bit music to share for almost nothing. People like to share, and the love of money isn't always the path of least resistance. Nor does the love of money produce better music.
The record industry hasn't kept up with the times. What they should have done 5 years ago is make a new music CD format with 24-bit 96khz sampling rate and 5.1 Dolby sound. There, now they've kept up with technology, and the supply of such a data-heavy format isn't suitable for most broadband users.
At that point, their creation of p2p networks carrying their OWN lower fidelity, 16-bit mp3s could have eliminated the now-crushing load that AOR corporate radio people put on music label's marketing budgets. MP3 killed the radio store, rather than MP3 killed the record store.
Firstly, for (the feds) to get involved, they need at least $5000 damage, which he couldn't speak to.
That was really my point. First, hijacking dns services is illegal regardless of damages, right? Second, no local law inforcement has jurisdiction over something as national or international as was the dns hijacking.
The analogy I want to draw is that somebody is pointing a gun at somebody else's head. Now, should law enforcement get involved, even if the potential victim doesn't have a large financial portfolio?
...called the FBI back this morning, only to be told they generally didn't investigate these types of crimes for individuals, but usually only for companies that had lost at least a couple thousand dollars.
I really don't know what to say, except what I put in the subject line. The subject was lifted from the famous line in Blade Runner, "If you're not cop, you're little people." These days, money incurrs rights and protection granted by the government. Odd how things have turned out, eh?
A blighted landscape vs. air polution? Imagine how fucked up the outside would look if solar panels produced all our electricity, let alone wind machines or geothermal of biomass production.
The world's real problem is overpopulation of human beings. Alternative energy projects are a band-aide hiding the ultimate challenge for humanity, which is how to reduce the population.
On the other hand, if SCO loses, it will send a strong message to the world: "Stay away from anything GPL, or you'll find your proprietary code taken away from you."
SCO's tactics are a study of ill will. What an honest company would do if they found their code in some GPL software is send an email informing the project leader. Then, certainly 99% of the time, the offending code would be removed from the project. End of story.
SCO isn't protecting their code. They're attempting to blackmail another company for monetary reasons.
Somehow, opening up software purchases to competitive bidding never seems to work with governments due to corruption. So mandating what software to purchase within an organization (such as a government) is a no brainer. Government agencies are best kept when they are tightly managed, rather than having "freedom", don't you think?
The real concern management has with Linux is support. If there is a hardware or software problem, we can call Sun/IBM 24x7 and they will work on the problem and if necessary call in people with specific expertise to resolve the issue. Those maintenance contracts cost a lot of money, but that is part of the cost of doing business when you have SLAs to maintain. I cannot get that kind of support for Linux. Checking Google for a fix is simply not an alternative.
If you are willing to pay IBM for AIX support, why aren't you willing to pay IBM for Linux support?
I remember how Apple rolled over Microware with the OS-9 naming lawsuit. Microware didn't have enough money to win against the Apple, even though Apple had clearly stolen the name of their product. I just don't get that warm, fuzzy feeling when I think about Apple.
Next time you receive your weekly store flyers, pay attention to the pricing backdrop styles. They're all star bursts.
I admit I'm a snotty-nosed book designer, but I remember working at a shopper back in the old days when we used to make all those starbursts by hand with an exacto knife.
I made a small fortune coding and selling an XPress extension called Punch XT that made stylized in-line text outlines and in-text image texturing, automatic price formatting and shadowing. The No. 1 feature requested feature was star burst effects.
Hey, what's a few hundred bucks when they've added all those awesome features like the Automatic Star Button right on the toolbar and the ability to save your layout as an exceptionally lame static-sized web page? And not to mention an insanely great pallette of web safe colors!
I'm ready with my credit card because I know that Operators are Standing By!
The old way of configuring the same package differently depending on your distribution needs to end. And this extra proprietary "layer" on top are steps in the right direction. All we need to do now is make these layers un-proprietary;)
Maybe that will come from KDE or Gnome. There's already several 'configure' apps I've seen for KDE: Kuser; Kcron; Knetfilter; Printing Manager. I've played with a KDE app that interfaces to the kernel config. Never have actually used them for real world, though.
Obviously you've never seen/used/pushed-to-the-limit a RH AS 2.1 in a big machine.
RH is composed from off-the shelf opensource binaries available to anyone with an internet connection. Seriously, the idea that Red Hat's collection is somehow better suited for your 'pushed-to-the-limit' servers than a self-compiled, self-configured system is pure FUD itself.
And sometimes, it is even worse. Do you recall Red Hat's horrible internally-released gcc 2.96 piece of crap? That one never made it through the rigours of open-source public testing, and was later exposed as producing incompatible binaries. Sweet, heh? Yet, Red Hat produced an entire release using that thing. I wouldn't TRUST my 'pushed-to-the-limit' servers to that kind of stuff. I get mine from the source.
If there is an issue or a nasty bug in any major package/project, I'll soon know about it because I keep myself informed. I do so because I consider myself a professional.
With a commercial distro, you'll know about a bug when they've fixed it (read "recompiled a new binary") on their time and on their dime. If your company has a reasonably-sized, competent staff, divide up the important projects (kernel, binutils, gcc, glibc, apache, etc.) amongst everybody. When a new version gets released, the caretaker of that project compiles it, and a week later after testing and checking the project's sourceforge page for any issues, the binary gets released company-wide. We keep our machines very lean -- we don't run crap just because it's included in some compiled-for-lowest-common-denominator-586 distro.
I'm calling the emperor's new clothes for what they are: a crutch for enterprise Linux newbies. By all means, if you're looking at your first company-wide rollout from Windows to Linux, get it. The high-cost and support are a good substitute for in-house expertise. But if that expertise doesn't ever manifest, then the IT department has some problems, doesn't it? If you've had experience with Linux or UNIX, forget it.
In my opinion, Red Hat Enterprise is a crutch for enterprise Linux newbies. Paying so much more for a few little kernel config options, their claim that it is more 'stable', the Red Hat layer of obfuscation over the text files in/etc, and the RPM jail in the long run can make administration as problematic as one of those sick little MSWindows Wizards. If you ever need to stick your head out of their prefabricated box, you're likely to face an administration nightmare.
Simplicity is the winner here, and the bigger the enterprise, the more sense it makes to go with LFS, Gentoo or perhaps Debian.
whats stopping IBM from making these chips available
with an appropriate motherboard for folks who would like to run linux/bsd/ on them?
In 2004, IBM will produce a chipset and subsequently subcontracts a Taiwan motherboard company to produce boards for the White Box market. These boards run Linux/BSD/OSX. Price point for a single-CPU board is seeded (with a small subsidy from IBM) at about US$200.
Apple whines and whimpers, but their contract with IBM does not prohibit IBM from doing chipsets or motherboards. The cat is out of the bag.
Apple then counters with their own White-Box board (based on their $1,999 low-end G5 model and offers it to authorized dealers for resale at a list price of $499. While attractively packaged, the board does not sell well. Soon, tier two computer vendors are offering OSX-compatible computers for less than $1,000. Apple's sales begin to tank badly.
Steve Jobs is forced out of Apple, and some clever dot.com thumbhead takes over. Apple sells off their hardware division to Vector Capitol (for too much money), and subsequently releases an OSX-64 version for the Opteron. Apple throws away Mach-O in favor of the Linux kernel, touting the 'thousands of drivers' supported. OSX now retails for $299.
OSX market share slowly climbs to 5%, then 10%, then 15%. Intel releases an Opteron-compatible Pentium4-based architecture. Apple's new CEO makes a short speech at Intel's public P-64 announcement. Later that day, Microsoft pulls Office 2005 and Internet Explorer for OSX off the market, and begins making lots of phone calls to members of Congress.
VIA releases a chipset for the Power PC 970, and single-CPU boards now sell for less than $100. IBM subcontracts PPC970 production to UMC as sales continue to climb. Dell, for the first time, sells a computer bundled with OSX.
I've always maintained that Linux needs to be virtually indentical to Windows in feel, down to the DOS prompt drive letters to make the techies feel at home.
Very funny! However, I don't think that most techies feel comfortable with drive letters and Windows look & feel.
Re:Cringley, Linus, and Christoph Hellwig
on
Today's SCO News
·
· Score: 1
And it was just a coincidence that the announcement of the deal with SCO was made at this time?
I've been wondering what kind of latency MOSIX gives when it moves an X client over to another machine. Can you describe what it feels like for the user?
I've been running into issues that I used to be able to do easily in NeXTStep. Showing evil invisibles, for instance. I want to see my.files, especially my.. directory so I can get to the higher directory quickly by double-clicking on it. I prefer the icon view under OSX finder, so I want to see the invisibles and naughty directories, such as/etc and/usr.
Slashdot Mirror
The record industry hasn't kept up with the times. What they should have done 5 years ago is make a new music CD format with 24-bit 96khz sampling rate and 5.1 Dolby sound. There, now they've kept up with technology, and the supply of such a data-heavy format isn't suitable for most broadband users.
At that point, their creation of p2p networks carrying their OWN lower fidelity, 16-bit mp3s could have eliminated the now-crushing load that AOR corporate radio people put on music label's marketing budgets. MP3 killed the radio store, rather than MP3 killed the record store.
That was really my point. First, hijacking dns services is illegal regardless of damages, right? Second, no local law inforcement has jurisdiction over something as national or international as was the dns hijacking.
The analogy I want to draw is that somebody is pointing a gun at somebody else's head. Now, should law enforcement get involved, even if the potential victim doesn't have a large financial portfolio?
I really don't know what to say, except what I put in the subject line. The subject was lifted from the famous line in Blade Runner, "If you're not cop, you're little people." These days, money incurrs rights and protection granted by the government. Odd how things have turned out, eh?
Give us another million years and we'll breed away the hair on the muff forever.
The world's real problem is overpopulation of human beings. Alternative energy projects are a band-aide hiding the ultimate challenge for humanity, which is how to reduce the population.
SCO's tactics are a study of ill will. What an honest company would do if they found their code in some GPL software is send an email informing the project leader. Then, certainly 99% of the time, the offending code would be removed from the project. End of story.
SCO isn't protecting their code. They're attempting to blackmail another company for monetary reasons.
I'm going to donate my $13 to the EFF.
Somehow, opening up software purchases to competitive bidding never seems to work with governments due to corruption. So mandating what software to purchase within an organization (such as a government) is a no brainer. Government agencies are best kept when they are tightly managed, rather than having "freedom", don't you think?
If you are willing to pay IBM for AIX support, why aren't you willing to pay IBM for Linux support?
And what do you think Apple would do if I sold a Linux distro that was named, Linux OS X?
I admit I'm a snotty-nosed book designer, but I remember working at a shopper back in the old days when we used to make all those starbursts by hand with an exacto knife.
I made a small fortune coding and selling an XPress extension called Punch XT that made stylized in-line text outlines and in-text image texturing, automatic price formatting and shadowing. The No. 1 feature requested feature was star burst effects.
Good for you! I hope your success cointinues!
I'm ready with my credit card because I know that Operators are Standing By!
Maybe that will come from KDE or Gnome. There's already several 'configure' apps I've seen for KDE: Kuser; Kcron; Knetfilter; Printing Manager. I've played with a KDE app that interfaces to the kernel config. Never have actually used them for real world, though.
RH is composed from off-the shelf opensource binaries available to anyone with an internet connection. Seriously, the idea that Red Hat's collection is somehow better suited for your 'pushed-to-the-limit' servers than a self-compiled, self-configured system is pure FUD itself.
And sometimes, it is even worse. Do you recall Red Hat's horrible internally-released gcc 2.96 piece of crap? That one never made it through the rigours of open-source public testing, and was later exposed as producing incompatible binaries. Sweet, heh? Yet, Red Hat produced an entire release using that thing. I wouldn't TRUST my 'pushed-to-the-limit' servers to that kind of stuff. I get mine from the source.
If there is an issue or a nasty bug in any major package/project, I'll soon know about it because I keep myself informed. I do so because I consider myself a professional.
With a commercial distro, you'll know about a bug when they've fixed it (read "recompiled a new binary") on their time and on their dime. If your company has a reasonably-sized, competent staff, divide up the important projects (kernel, binutils, gcc, glibc, apache, etc.) amongst everybody. When a new version gets released, the caretaker of that project compiles it, and a week later after testing and checking the project's sourceforge page for any issues, the binary gets released company-wide. We keep our machines very lean -- we don't run crap just because it's included in some compiled-for-lowest-common-denominator-586 distro.
I'm calling the emperor's new clothes for what they are: a crutch for enterprise Linux newbies. By all means, if you're looking at your first company-wide rollout from Windows to Linux, get it. The high-cost and support are a good substitute for in-house expertise. But if that expertise doesn't ever manifest, then the IT department has some problems, doesn't it? If you've had experience with Linux or UNIX, forget it.
Simplicity is the winner here, and the bigger the enterprise, the more sense it makes to go with LFS, Gentoo or perhaps Debian.
In 2004, IBM will produce a chipset and subsequently subcontracts a Taiwan motherboard company to produce boards for the White Box market. These boards run Linux/BSD/OSX. Price point for a single-CPU board is seeded (with a small subsidy from IBM) at about US$200.
Apple whines and whimpers, but their contract with IBM does not prohibit IBM from doing chipsets or motherboards. The cat is out of the bag.
Apple then counters with their own White-Box board (based on their $1,999 low-end G5 model and offers it to authorized dealers for resale at a list price of $499. While attractively packaged, the board does not sell well. Soon, tier two computer vendors are offering OSX-compatible computers for less than $1,000. Apple's sales begin to tank badly.
Steve Jobs is forced out of Apple, and some clever dot.com thumbhead takes over. Apple sells off their hardware division to Vector Capitol (for too much money), and subsequently releases an OSX-64 version for the Opteron. Apple throws away Mach-O in favor of the Linux kernel, touting the 'thousands of drivers' supported. OSX now retails for $299.
OSX market share slowly climbs to 5%, then 10%, then 15%. Intel releases an Opteron-compatible Pentium4-based architecture. Apple's new CEO makes a short speech at Intel's public P-64 announcement. Later that day, Microsoft pulls Office 2005 and Internet Explorer for OSX off the market, and begins making lots of phone calls to members of Congress.
VIA releases a chipset for the Power PC 970, and single-CPU boards now sell for less than $100. IBM subcontracts PPC970 production to UMC as sales continue to climb. Dell, for the first time, sells a computer bundled with OSX.
Etc., etc., etc.
We need more people. Too many turtles. Kill them.
Very funny! However, I don't think that most techies feel comfortable with drive letters and Windows look & feel.
And it was just a coincidence that the announcement of the deal with SCO was made at this time?