"That said, if your Athlon system has a 100MHz FSB, something is wrong. The only chipset that defaults to such as speed is the prehistoric AMD750 "
That's not true, quite a few Athlon motherboards default to 100/200MHz fsb. It's pretty common to have to change a jumper or bios setting to enable 133/266 fsb operation. Remember that some Athlons (even some Tbirds) and all Durons come in 100/200 fsb versions.
If in fact you did sell his email address to a spammer in conflict with your own privacy policy then I think he is justified in sending you a bill to cover his time, energy, and resources at a rate he considers reasonable.
I have the same printer and am using it without any problems at all. I'm using Debian & Magicfilter. I also needed to install Gimp-print to get decent photo quality output but normal printing (both B&W and Color) was fine out of the box. If you take your question to one of the Linux news groups and describe your problems in a bit more detail you'll probably get your problems sorted out.
FWIW I translate text files to PS before printing (automatically) rather than printing them directly. This is using GS + Magicfilter though so I'm not sure how you'd do that with CUPS.
" You obviously have not tried Windows 2000/XP etc. "
Or maybe he's just used NT/95/98 more. What is the Win2k/XP installed base? 10%?
"The simple fact is almost every printer out there works with these OS's, out of the box. That is important."
I've run into just as many printers that don't work right under Win2k as under Linux.
"Plug-n-play means you get a dialog box, and half the time the driver is already loaded with windows, otherwise you can use the supplied diskette. "
At which point you either use the drivers built into Windows and give up 2/3 of the printer's feature set or you use the drivers that came on the cd only to find that they are badly broken.
"linux simply has a smaller driver base than windows overall."
Not really, remember that a single driver on Linux may work with dozens of different printers. The actual number of printers supported is probably pretty similar.
"That your rather silly post got modded up indicates that most people reading slashdot don't actually have to support computer installations or havn't actually used linux to print."
Frankly I think you either arn't all that experienced yourself or your convienently forgetting about the times Win2k has failed to work right with a printer.
90% of all SOHO laser printers can emulate a HP Laserjet and thus are supported under Linux. The 10% that are left are just the Laser equivilant of the $59 Walmart ink jet printers and really arn't worth the effort.
"Anyways, Microsoft's claim is entirely legitimate. 'Lindows' is in the same "industry" as 'Windows', and is intentionally abusing the popularity of Windows for its own benefit. "
Except that, alone isn't illegal. There needs to be a possibility (maybe likelyhood?) of consumer confusion.
"This is the same as coming up with an electronics company called Panasoanic -- there is the potential for legitimate consumer confusion."
Well, I disagree but that's what it is going to come down to. Will consumers think Lindows is a MS product? Hmm...
Panasonic Panasoanic....
That would definately be confusing.
Windows Lindows
I don't think anyone who was familiar with Linux would be confused but maybe Joe/Jane consumer would be.
"Let me suggest to you that useful but boring space research gets done because we also do exciting but expensive things. That is, it's hard to get the public interested in a fleet of Earth-orbiting atmospheric science satellites, but human spaceflight galvanizes the public interest enough that a few hundred million can sneak past for other, more scientifically interesting research."
In other words the ISS is a really expensive advertising campaign?
Agreed, SQL Ledger is great. Personally I like the fact that since it is web based (and uses a real database) that it only needs to be installed on one machine but can be accessed by any machine you've given permissions to.
" The problem is that the "crisis" was totally manufactured by Debian itself."
I still don't see how this is true. The LDP maintainer simply pointed out to one of the Debian maintainers that many of the LDP docs didn't fit into Debian's own rules for what was allowed into Debian/main. IMHO the only thing that Debian can be blamed for here is not noticing the problem themselves.
"BFD. They could probably still be released under the "non-free" section. "
That's exactly what will happen.
"mostly documents that predate the "Debian-approved" license they prefer. "
And more specifically, docs that don't allow free modification and distribution.
" Look at your own language! Debian wants to "impose" a license on documents contributed by volunteer authors to a completely independent organization?! "
That's just completely wrong. Debian's rules only dictate wheather they will be able to distribute your documentation and if it will be in the main tree or in the non-free section. No one is "imposing" anything on you.
You have to realize that those of us who use Debian have grown to expect (and in fact Debian has promised) that anything we find in the main tree can be freely modified and distributed as long as we follow a few basic rules. If a piece of software or documentation doesn't meet the DFSG (Debian Free Software Guidlines) then it simply doesn't belong in Debian/main.
AFAIK this issue is mainly about documentation that is distributed seperately such as HOWTOs etc. So what happens if you want to update a HOWTO but the author is unreachable? If the HOWTO is under a license that requires permission from the author to modify it then your only choices are to either re-write it from scratch or let it rot.
" I've seen this happen first hand at two different companies; engineers want to open things up, management looks into OSS/FS, sees the drubbing from the community (and threats of lawsuits everywhere!) other companies take when attempting to go OSS/FS while making very minor missteps with license compliance, usually due to the semantics of trying to mix multiple OSS/FS licenses. Management tends to nix the idea very quickly."
That's just plain silly. Companies in the closed source world sue each other over IP all the time but can you think of even one of the OSS/FS licensing issues that has actually resulted in a law suit?
"it is baffling to me why the Debian nuts think documentation needs to be under its own special licence instead of using the GPL along with the software it documents."
You're probably baffled because the "Debian nuts" never said anything like the above. What exactly gave you the idea that this was even an issue?
"If you read the linux journal article you will see that SIS is an early adopter of this idea. Which is interesting considering that my sis 630 chipset equipped mobo doesn't behave well , or at all, with X."
What sort of problems are you having? I have a 730 based system (basically the Athlon version of the 630) which works just fine in X.
Many people and darn near all businesses have at least one Windows app. that they simply cannot give up. I'd take running 90% Linux native stuff + 1 Windows app. over running 100% Windows any day.
"what non-computer expert can realistically expect to wrestle with Linux when it fails to boot, or they add new hardware, install a new application, or, heaven forbid, they want to upgrade to the latest kernel? It's not for mere mortals. "
Replace "Linux" with "Windows" in the above statement and it rings just as true (except for upgrading the kernel but that's dead simple on most modern Linux distros these days).
That's nothing, check out some of the appropraitions bills some time. You finally work your way through the entire bill only to find an ammendment like "Replace sections 7, 8, and 9 with the word "and"".
Slashdot Mirror
"That said, if your Athlon system has a 100MHz FSB, something is wrong. The only chipset that defaults to such as speed is the prehistoric AMD750 "
That's not true, quite a few Athlon motherboards default to 100/200MHz fsb. It's pretty common to have to change a jumper or bios setting to enable 133/266 fsb operation. Remember that some Athlons (even some Tbirds) and all Durons come in 100/200 fsb versions.
Back when I was using OS/2 I found the voice navigation on the web to be pretty good. I never really found the dictation that usefull though.
If in fact you did sell his email address to a spammer in conflict with your own privacy policy then I think he is justified in sending you a bill to cover his time, energy, and resources at a rate he considers reasonable.
"Really... the only people who object to this are those with something to hide."
And what exactly is wrong with having something to hide?
I have the same printer and am using it without any problems at all. I'm using Debian & Magicfilter. I also needed to install Gimp-print to get decent photo quality output but normal printing (both B&W and Color) was fine out of the box. If you take your question to one of the Linux news groups and describe your problems in a bit more detail you'll probably get your problems sorted out.
FWIW I translate text files to PS before printing (automatically) rather than printing them directly. This is using GS + Magicfilter though so I'm not sure how you'd do that with CUPS.
" You obviously have not tried Windows 2000/XP etc. "
Or maybe he's just used NT/95/98 more. What is the Win2k/XP installed base? 10%?
"The simple fact is almost every printer out there works with these OS's, out of the box. That is important."
I've run into just as many printers that don't work right under Win2k as under Linux.
"Plug-n-play means you get a dialog box, and half the time the driver is already loaded with windows, otherwise you can use the supplied diskette. "
At which point you either use the drivers built into Windows and give up 2/3 of the printer's feature set or you use the drivers that came on the cd only to find that they are badly broken.
"linux simply has a smaller driver base than windows overall."
Not really, remember that a single driver on Linux may work with dozens of different printers. The actual number of printers supported is probably pretty similar.
"That your rather silly post got modded up indicates that most people reading slashdot don't actually have to support computer installations or havn't actually used linux to print."
Frankly I think you either arn't all that experienced yourself or your convienently forgetting about the times Win2k has failed to work right with a printer.
90% of all SOHO laser printers can emulate a HP Laserjet and thus are supported under Linux. The 10% that are left are just the Laser equivilant of the $59 Walmart ink jet printers and really arn't worth the effort.
"Anyways, Microsoft's claim is entirely legitimate. 'Lindows' is in the same "industry" as 'Windows', and is intentionally abusing the popularity of Windows for its own benefit. "
Except that, alone isn't illegal. There needs to be a possibility (maybe likelyhood?) of consumer confusion.
"This is the same as coming up with an electronics company called Panasoanic -- there is the potential for legitimate consumer confusion."
Well, I disagree but that's what it is going to come down to. Will consumers think Lindows is a MS product? Hmm...
Panasonic Panasoanic....
That would definately be confusing.
Windows Lindows
I don't think anyone who was familiar with Linux would be confused but maybe Joe/Jane consumer would be.
"Let me suggest to you that useful but boring space research gets done because we also do exciting but expensive things. That is, it's hard to get the public interested in a fleet of Earth-orbiting atmospheric science satellites, but human spaceflight galvanizes the public interest enough that a few hundred million can sneak past for other, more scientifically interesting research."
In other words the ISS is a really expensive advertising campaign?
Agreed, SQL Ledger is great. Personally I like the fact that since it is web based (and uses a real database) that it only needs to be installed on one machine but can be accessed by any machine you've given permissions to.
" The problem is that the "crisis" was totally manufactured by Debian itself."
I still don't see how this is true. The LDP maintainer simply pointed out to one of the Debian maintainers that many of the LDP docs didn't fit into Debian's own rules for what was allowed into Debian/main. IMHO the only thing that Debian can be blamed for here is not noticing the problem themselves.
"BFD. They could probably still be released under the "non-free" section. "
That's exactly what will happen.
"mostly documents that predate the "Debian-approved" license they prefer. "
And more specifically, docs that don't allow free modification and distribution.
" Look at your own language! Debian wants to "impose" a license on documents contributed by volunteer authors to a completely independent organization?! "
That's just completely wrong. Debian's rules only dictate wheather they will be able to distribute your documentation and if it will be in the main tree or in the non-free section. No one is "imposing" anything on you.
You have to realize that those of us who use Debian have grown to expect (and in fact Debian has promised) that anything we find in the main tree can be freely modified and distributed as long as we follow a few basic rules. If a piece of software or documentation doesn't meet the DFSG (Debian Free Software Guidlines) then it simply doesn't belong in Debian/main.
"Now the documentation is going into the GNU-virus? How are people around the computer field supposed to make money? "
That's a straw man. Nobody here has suggested that commercial publications need to suddenly be made free.
AFAIK this issue is mainly about documentation that is distributed seperately such as HOWTOs etc. So what happens if you want to update a HOWTO but the author is unreachable? If the HOWTO is under a license that requires permission from the author to modify it then your only choices are to either re-write it from scratch or let it rot.
"Having no licenses was the original idea of open source and should remain so. "
If you have no license then you cannot legally make copies (at least in the US).
" I've seen this happen first hand at two different companies; engineers want to open things up, management looks into OSS/FS, sees the drubbing from the community (and threats of lawsuits everywhere!) other companies take when attempting to go OSS/FS while making very minor missteps with license compliance, usually due to the semantics of trying to mix multiple OSS/FS licenses. Management tends to nix the idea very quickly."
That's just plain silly. Companies in the closed source world sue each other over IP all the time but can you think of even one of the OSS/FS licensing issues that has actually resulted in a law suit?
"it is baffling to me why the Debian nuts think documentation needs to be under its own special licence instead of using the GPL along with the software it documents."
You're probably baffled because the "Debian nuts" never said anything like the above. What exactly gave you the idea that this was even an issue?
" Uh, it says in the abstract "(without opening a window). Who looks stupid now? :)"
:)
Why would diging a big hole in the floor require opening a window?
"If you read the linux journal article you will see that SIS is an early adopter of this idea. Which is interesting considering that my sis 630 chipset equipped mobo doesn't behave well , or at all, with X."
What sort of problems are you having? I have a 730 based system (basically the Athlon version of the 630) which works just fine in X.
Many people and darn near all businesses have at least one Windows app. that they simply cannot give up. I'd take running 90% Linux native stuff + 1 Windows app. over running 100% Windows any day.
If MS Office was the only app. anyone cared about you'd be right.
"what non-computer expert can realistically expect to wrestle with Linux when it fails to boot, or they add new hardware, install a new application, or, heaven forbid, they want to upgrade to the latest kernel? It's not for mere mortals. "
Replace "Linux" with "Windows" in the above statement and it rings just as true (except for upgrading the kernel but that's dead simple on most modern Linux distros these days).
"accounting != mission critical."
Thanks for the heads up. I'll remember that next time you complain that Payrole screwed up your over time hours AGAIN.
Yours truly,
The Boss
That's nothing, check out some of the appropraitions bills some time. You finally work your way through the entire bill only to find an ammendment like "Replace sections 7, 8, and 9 with the word "and"".
Very frustrating.