Linux SUCKS and should never be used by human beings.

Page 7 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Markbnj

Elite Member <br>Moderator Emeritus
Moderator
Sep 16, 2005
15,682
13
81
www.markbetz.net
Binary drivers on a free operating system are stupid, and I wish they'd be removed permenantly. It's an affront to consumers everywhere.

As far as I know the sole argument in favor of distributing drivers in source code format is that a few geeks will be able to look at them and maybe fix a bug or two. On the other hand, it also means that anyone with a less virtuous motive will also be able to look at them, and find exploitable holes. It also means that different versions of the driver will make their way into the field where they will be picked up and used by people who don't know any better, and who will call the hardware OEM when things don't work right. In short, there is no motivation for a hardware OEM to release driver source. The Linux model just doesn't work for hardware vendors. I would think that has been made more than clear by the near-total failure of the Linux community to convince them that it does. Maybe if it were a much larger market... but it isn't.
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
sudo apt-get install vsftpd

ftp localhost


wow, I installed AND VERIFIED an ftp server in 2 steps. Lets see a GUI do it in two clicks of the mouse...



Guess what, my grandma can't install a program on WINDOWS or LINUX.....until someone TEACHES HER.

btw, she runs great on Ubuntu...email, web, that's about it. And I don't have to worry about crap happening on her box, because she uses a decent OS.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
As far as I know the sole argument in favor of distributing drivers in source code format is that a few geeks will be able to look at them and maybe fix a bug or two.

I would say that 'maybe' is extraneous, OSS drivers have been orders of magnitudes more reliable than their closed source alternatives. And that's ignoring the unstable Linux kernel API, whenver an API change happens in the kernel all of the in-tree drivers are updated at the same time so that nothing breaks but out-of-tree and closed drivers have to be updated manually by the maintainer and that can take weeks or sometimes even months.

On the other hand, it also means that anyone with a less virtuous motive will also be able to look at them, and find exploitable holes.

Yea, because those with bad intent have always had a really hard time finding exploits in closed source programs and drivers...

In short, there is no motivation for a hardware OEM to release driver source. The Linux model just doesn't work for hardware vendors. I would think that has been made more than clear by the near-total failure of the Linux community to convince them that it does. Maybe if it were a much larger market... but it isn't.

Yes, there is motivation, that of course depends on them wanting to support Linux to some extent but if they do then they should want to GPL their drivers and get them accepted into the upstream tree since it'll save them a lot of work in the long run. It seems to work fine for Intel, HP, Dell, 3Ware, Promise, Adaptec, Cyclades, IBM, etc.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: Markbnj
Binary drivers on a free operating system are stupid, and I wish they'd be removed permenantly. It's an affront to consumers everywhere.

As far as I know the sole argument in favor of distributing drivers in source code format is that a few geeks will be able to look at them and maybe fix a bug or two.

And continue to support older hardware even when the manufacturer won't. And to have a driver that is well integrated into the system that will work well (See: BSD).

And the source isn't the best part, the best part is good hardware documentation. Which seems to be a problem for US based companies, but less of a problem for non-US entities. Nothing like holding back the US technology sector. AGAIN. Documentation helps out when the vendor driver breaks or could be further optimized, which can be relatively often on smaller OSes (em(4) on OpenBSD).

On the other hand, it also means that anyone with a less virtuous motive will also be able to look at them, and find exploitable holes.

Or people with virtuous motives can look at them and try to find exploitable holes. Vulnerability pimps and researchers are important.

It also means that different versions of the driver will make their way into the field where they will be picked up and used by people who don't know any better, and who will call the hardware OEM when things don't work right.

No they won't. If you're using Linux you know that the vendors who don't provide the source code won't help you. You turn to the authors of the drivers when you find bugs, or the support groups for those drivers.

In short, there is no motivation for a hardware OEM to release driver source.

That's fine, open the docs! There is no moral reason not to, and even less of a technical one. Hell, it'll even help sales.

The Linux model just doesn't work for hardware vendors. I would think that has been made more than clear by the near-total failure of the Linux community to convince them that it does. Maybe if it were a much larger market... but it isn't.

Between non-US companies accepting open source as something viable and the hard work the reverse engineers are doing (god's work really), the FLOSS community isn't doing too bad. Now if the linux culture as a whole got behind the movement...
 

Markbnj

Elite Member <br>Moderator Emeritus
Moderator
Sep 16, 2005
15,682
13
81
www.markbetz.net
Forgive me for mashing replies to two posts into this.

Nothinman...

I would say that 'maybe' is extraneous, OSS drivers have been orders of magnitudes more reliable than their closed source alternatives.

I haven't had an unusual problem with unstable XP drivers, for example, and that is almost completely a closed source model. I prefer knowing who is responsible for interfacing the hardware to the o/s, and I prefer that to be the hardware vendor or a partner of theirs.

Yea, because those with bad intent have always had a really hard time finding exploits in closed source programs and drivers...

Are you arguing that having the source code doesn't make it easier?

Yes, there is motivation, that of course depends on them wanting to support Linux to some extent but if they do then they should want to GPL their drivers and get them accepted into the upstream tree since it'll save them a lot of work in the long run. It seems to work fine for Intel, HP, Dell, 3Ware, Promise, Adaptec, Cyclades, IBM, etc.

Maybe it's the other way around. Maybe they would be more eager to support Linux if it didn't encourage them to (require that they?) change their software asset management processes. Commercial entities have to spec out and deliver interfaces on a budget and a timeline. I wouldn't even know how to begin managing the open source community to achieve those goals.

n0cmonkey...

And continue to support older hardware even when the manufacturer won't. And to have a driver that is well integrated into the system that will work well (See: BSD).

The first argument is a good one. I would like to see hardware vendors GPL their drivers and interface specs once they go out of support. The second argument... I just don't see any issues with the current proprietary model that require addressing. It works fine for nearly everyone, and the edge cases can be handled with support, which is clearly the responsibility of the driver authors/hardware OEM in the proprietary model.

And the source isn't the best part, the best part is good hardware documentation. Which seems to be a problem for US based companies, but less of a problem for non-US entities.

I'm with you on this one. I benefitted a lot in the past from complete IBM, Intel, and Motorola hardware specifications and interface documentation. But in the end it is their hardware, and their support responsibility. If they feel relesasing complete specs will lead to more trouble than it's worth, or disadvantage them competitively, that's their decision.

No they won't. If you're using Linux you know that the vendors who don't provide the source code won't help you. You turn to the authors of the drivers when you find bugs, or the support groups for those drivers.

No what won't? Different versions of the software won't make their way into the field? Of course they will. People won't call the hardware OEM looking for help? Of course they will. Once again you guys simply don't understand that you aren't representative of the computing user community, or even remotely close to it. You're a technically-oriented geek fringe that is meaningless in terms of gauging user behavior.

I think a good common ground is to ask hardware vendors to open the docs as you suggest, so the nix communities can take care of themselves. But if they don't think that is in their interests, then from my point of view you guys offer no economic incentive to change anybody's business model, now or in any near-term future that I can see.
 

Smilin

Diamond Member
Mar 4, 2002
7,357
0
0
This thread is a wheelbarrow full of troll sh1t.


I think Windows is superior but anyone who truly thinks linux sucks is probably just confused by their own noobness.
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
MarkBnj...

have you tried creative products on VIsta? I haven't, but I've been seeing a multitude of threads on the craptastic driver support thus far. If the h/w is documented properly, then the OSS community will usually have a good, stable driver out quickly.

I think the point about open/closed source security was to say that it has no bearing on security.

IIS5 was closed source with a lousy security track record. IIS6 is closed source with a good security track record. To say "OMG!!1!! Haxxors can s33 the c0de and haxx0rs it!!1!" as another poster said (I'm paraphrasing ) is dumb.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
I haven't had an unusual problem with unstable XP drivers, for example, and that is almost completely a closed source model. I prefer knowing who is responsible for interfacing the hardware to the o/s, and I prefer that to be the hardware vendor or a partner of theirs.

Well I haven't ran Windows in a serious fashion in a long time but I wouldn't call the problems I've seen unusual either, but I think that's part of the problem. =) A decent example is a friend of mine who does still use Windows as his primary OS (even though he bought a Mac Pro and put Windows on that), just this weekend when I was over there his machine froze while in WoW. I didn't investigate too much since it he didn't ask for any help, but I did see him reinstalling some nVidia drivers and didn't notice it freeze on him the rest of the weekend.

And I do know who's responsible for interfacing the hardware to the OS and their email address is right there in the MAINTAINERS file with the kernel, I like being able to email a normal person with problems instead of some support@ address that will likely get ignored.

Are you arguing that having the source code doesn't make it easier?

I'm saying that not having it doesn't make it any harder, those that know how to write the exploits have just as easy of a time reading assembly as they do C.

Maybe it's the other way around. Maybe they would be more eager to support Linux if it didn't encourage them to (require that they?) change their software asset management processes. Commercial entities have to spec out and deliver interfaces on a budget and a timeline. I wouldn't even know how to begin managing the open source community to achieve those goals.

And there's your problem, _you_ don't manage the OSS community. If you want your hardware to work in Linux you have 3 choices:

1) develop your own binary-only driver and deal with the constantly changing kernel API.
2) develop your own GPL driver and release it
3) release the specs for youra hardware and let someone else develop a free driver

1 will cost you the most overall since you'll have to be constantly following development to keep your driver compiling. 2 will cost you a bit up front but once the driver is accepted upstream it'll be maintained for free as long as the hardware is still in use by someone. 3 will cost you nothing at all and you still get Linux support.

The second argument... I just don't see any issues with the current proprietary model that require addressing. It works fine for nearly everyone, and the edge cases can be handled with support, which is clearly the responsibility of the driver authors/hardware OEM in the proprietary model.

It only seems to work well because it's all that Windows users know. I installed XP a few months back on this machine and it was a huge PITA because none of the hardware was supported out of the box, and since none of my other machines have X installed I had to scrounge around the Internet looking for drivers with w3m. nVidia's website definitely wasn't designed with text browsers in mind...

Different versions of the software won't make their way into the field?

Not likely, at least not any worse than there is with current binary drivers. Can you name any OSS drivers that have had significant forks?
 

Robor

Elite Member
Oct 9, 1999
16,979
0
76
Originally posted by: nweaver
MarkBnj...

have you tried creative products on VIsta? I haven't, but I've been seeing a multitude of threads on the craptastic driver support thus far. If the h/w is documented properly, then the OSS community will usually have a good, stable driver out quickly.

I think the point about open/closed source security was to say that it has no bearing on security.

IIS5 was closed source with a lousy security track record. IIS6 is closed source with a good security track record. To say "OMG!!1!! Haxxors can s33 the c0de and haxx0rs it!!1!" as another poster said (I'm paraphrasing ) is dumb.

I can confirm the craptacular Audigy Vista drivers. I installed the beta Audigy driver for my Audigy 2 ZS Gamer. No errors or crashes but I have to have my system at full volume and the speakers at 2/3 - 3/4 volume just for an average listening volume.

I had Vista (latest from MSDN) installed for about 36 hours and went back to XP Pro. I installed Ghost Recon: Advanced Warfighter and was unable to log into GameSpy from within the game. I patched the game and after that it wouldn't launch. Another problem was Firefox would install and launch but after I ran it once and closed it the next attempt would say something about a previous install still running (even after a reboot). I've tried previous versions of Vista and never had that before so I'm sure it's something abnormal.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: Markbnj
n0cmonkey...

And continue to support older hardware even when the manufacturer won't. And to have a driver that is well integrated into the system that will work well (See: BSD).

The first argument is a good one. I would like to see hardware vendors GPL their drivers and interface specs once they go out of support. The second argument... I just don't see any issues with the current proprietary model that require addressing. It works fine for nearly everyone, and the edge cases can be handled with support, which is clearly the responsibility of the driver authors/hardware OEM in the proprietary model.

But it doesn't work for everyone, my model DOES.

Open the hardware specs so that FLOSS developers can write drivers. They support their drivers, the hardware manufacturer supports the drivers they write, everyone is happy.

And the source isn't the best part, the best part is good hardware documentation. Which seems to be a problem for US based companies, but less of a problem for non-US entities.

I'm with you on this one. I benefitted a lot in the past from complete IBM, Intel, and Motorola hardware specifications and interface documentation. But in the end it is their hardware, and their support responsibility. If they feel relesasing complete specs will lead to more trouble than it's worth, or disadvantage them competitively, that's their decision.

Yes, it is their decision. But, there shouldn't be anything in the docs that gives anyone else a competitive edge. If there is, they didn't create a good enough API.

They won't have to support anything, just release the docs and wash their hands. Engineers could help out if they wanted, but that isn't necessary (although nice).

If I buy a piece of hardware I should be able to freely find out how to interface with it. I'm not getting a license to the hardware, I'm getting the hardware.

No what won't?

Go to the vendor for support on a driver the vendor did not release.

Different versions of the software won't make their way into the field? Of course they will. People won't call the hardware OEM looking for help? Of course they will. Once again you guys simply don't understand that you aren't representative of the computing user community, or even remotely close to it. You're a technically-oriented geek fringe that is meaningless in terms of gauging user behavior.

And you are?

I thought we were talking about Linux users for a moment, who are generally part of that "technically-oriented geek fringe."

I think a good common ground is to ask hardware vendors to open the docs as you suggest, so the nix communities can take care of themselves. But if they don't think that is in their interests, then from my point of view you guys offer no economic incentive to change anybody's business model, now or in any near-term future that I can see.

If a piece of hardware is supported in more OSes, you get more sales because more people can use it. Just because it isn't billions of billions of dollars doesn't mean it's meaningless.

That and the fact there is a moral responsiblity to open that documentation for the people that buy the hardware.
 

Markbnj

Elite Member <br>Moderator Emeritus
Moderator
Sep 16, 2005
15,682
13
81
www.markbetz.net
nweaver...

have you tried creative products on VIsta? I haven't, but I've been seeing a multitude of threads on the craptastic driver support thus far. If the h/w is documented properly, then the OSS community will usually have a good, stable driver out quickly.

This is a bit of a stretch, to be honest. Vista doesn't even release until tomorrow, and you think the open source community would have been ahead of the hardware OEMs in having signed stable drivers ready to go? I haven't seen anything to suggest that would have happened.

IIS5 was closed source with a lousy security track record. IIS6 is closed source with a good security track record. To say "OMG!!1!! Haxxors can s33 the c0de and haxx0rs it!!1!" as another poster said (I'm paraphrasing ) is dumb.

That was me, and it's not dumb . I'm a developer, and if you don't think it would be easier for me to exploit a piece of software to which I had source, as opposed to one where I was working from a disassembly, then you don't write software. What I will grant you is that it is also easier for someone else to find that same hole and patch it, but whether that dance works in favor of security, or against it, is a question neither of us have enough evidence to answer. In the past, in the face of questions like this, the default behavior has been to hide as much as possible. I think if you want to see the model changed the onus is on you to show that it would result in better security for the end user.

Nothinman...

A decent example is a friend of mine who does still use Windows as his primary OS (even though he bought a Mac Pro and put Windows on that), just this weekend when I was over there his machine froze while in WoW. I didn't investigate too much since it he didn't ask for any help, but I did see him reinstalling some nVidia drivers and didn't notice it freeze on him the rest of the weekend.

Maybe he was running old drivers and they patched the program. Point is he resinstalled the official nVidia drivers and it solved the problem. If WoW ran on Linux, do you think the average WoW player would have an easier time keeping drivers up to date?

I'm saying that not having it doesn't make it any harder, those that know how to write the exploits have just as easy of a time reading assembly as they do C.

Sorry dude, that's BS. I've been writing assembly since 1985. It's one thing to write in assembly, with symbols, and another thing to work from a disassembly without them. If you think that's as easy as reading C code then you haven't done much farting around with raw disassembly .

And there's your problem, _you_ don't manage the OSS community. If you want your hardware to work in Linux you have 3 choices:

1) develop your own binary-only driver and deal with the constantly changing kernel API.
2) develop your own GPL driver and release it
3) release the specs for youra hardware and let someone else develop a free driver

1 will cost you the most overall since you'll have to be constantly following development to keep your driver compiling. 2 will cost you a bit up front but once the driver is accepted upstream it'll be maintained for free as long as the hardware is still in use by someone. 3 will cost you nothing at all and you still get Linux support.

Fair enough. I'll give you my own assessment.

(1) gets you the best chance of being done to a schedule, or close to it, and to a budget, or close to it. Afterwards you have to deal with a "constantly changing kernel," instead of working to updates from one company that uses service pack releases to update the O/S. So that's _your_ problem, in terms of the Linux community. Why would anyone stake their business on such an environment?

(2) gets you all of the work, with none of the benefits of keeping it proprietary and in-house (i.e. you know exactly what's out there and what people are using because you control it).

(3) gets you nothing. Who is going to develop a new piece of hardware for a mass computing market and hope the open source community will get the drivers ready by the time the trucks arrive at Newegg? Nobody. This idea can't be taken seriously, at all.

It only seems to work well because it's all that Windows users know. I installed XP a few months back on this machine and it was a huge PITA because none of the hardware was supported out of the box, and since none of my other machines have X installed I had to scrounge around the Internet looking for drivers with w3m. nVidia's website definitely wasn't designed with text browsers in mind...

It always seems to come back to the poor ignorant Windows users for you guys. You just don't get it. Windows works well-enough for the vast majority of the couple of hundred million ordinary, non-technical people who use it every day. 97% of them would shoot themselves if you threw them into the Linux world tomorrow and told them they had to get their work done there. You cannot say your model works better for a mass market, because it has never been subjected to the test. The current model has. It evolved over forty years of capitalist economic trial and error. You say your system works better? So prove it the old fashioned way: attract people to it by showing how easy it is. When you get around to that let me know.

Not likely, at least not any worse than there is with current binary drivers. Can you name any OSS drivers that have had significant forks?

Well, since, as you have stated, most hardware OEMs aren't supportive of your model, we don't really know, do we? It's meaningless to look at the track record of current OSS drivers that are largely serving a niche market.

n0cmonkey...

But it doesn't work for everyone, my model DOES.

Open the hardware specs so that FLOSS developers can write drivers. They support their drivers, the hardware manufacturer supports the drivers they write, everyone is happy.

Yeah, as I said, I don't have any problem with that model at all, but then you have to convince the hardware guys to support it out of self-interest, because the hardware interfaces and driver specs are their property.

If I buy a piece of hardware I should be able to freely find out how to interface with it. I'm not getting a license to the hardware, I'm getting the hardware.

I'm sure you know that this isn't quite so clear a picture. Much of the newer hardware is actually running on programmable logic that defines the API in firmware.

Go to the vendor for support on a driver the vendor did not release.

You have a much greater faith in the average Linux user than I have in the average Windows user, and so you should.

And you are?

I thought we were talking about Linux users for a moment, who are generally part of that "technically-oriented geek fringe."

I'm the same, but I don't mistake myself for being the normal case. But you're right: if we're talking just about Linux users then the model probably works as you suggest. But if we're talking just about Linux users, and not a mass-market community for some future "easy to use" Linux, then why should the hardware OEMs bother? What are we talking about here? An increase of .5% of revenue for them?

If a piece of hardware is supported in more OSes, you get more sales because more people can use it. Just because it isn't billions of billions of dollars doesn't mean it's meaningless.

Actually in business such calculations are damned important. Focus is difficult to maintain, and if the amount of revenue to be gained isn't significant enough then yes, it's meaningless and should be avoided as a costly distraction.
 

n0cmonkey

Elite Member
Jun 10, 2001
42,936
1
0
Originally posted by: Markbnj
n0cmonkey...

I'm sure you know that this isn't quite so clear a picture. Much of the newer hardware is actually running on programmable logic that defines the API in firmware.

It's clear enough. We (the sane ones ) aren't asking for the firmware source code, just a way to interface with it.

And I consider the firmware to just be part of the hardware, whether it's embedded on there properly or not.

You have a much greater faith in the average Linux user than I have in the average Windows user, and so you should.

Linux is a niche market after all. For some value of niche, which is less than the market share of Microsoft Windows.

I'm the same, but I don't mistake myself for being the normal case. But you're right: if we're talking just about Linux users then the model probably works as you suggest. But if we're talking just about Linux users, and not a mass-market community for some future "easy to use" Linux, then why should the hardware OEMs bother? What are we talking about here? An increase of .5% of revenue for them?

Ask RALink. Or LSI. Or Intel. Or AMD.

I don't see any reason for the current model for Windows/OS X drivers to change. It should continue the way it is (it's safer for the users that way). I only want to affect change where it is lacking: FLOSS.

Actually in business such calculations are damned important. Focus is difficult to maintain, and if the amount of revenue to be gained isn't significant enough then yes, it's meaningless and should be avoided as a costly distraction.

The documentation not only helps outside developers but also helps those internal to the company. It's a win-win. These companies already have FTP servers, and a couple of well done PDFs aren't going to be big (and poorly done ones will be smaller than Creative's driver files).
 

Gamingphreek

Lifer
Mar 31, 2003
11,679
0
81
Ok without reading the entire post I have a few things to say and ask.

1. OP when you first started computers. I don't care how long ago or how much you think you know, when you first started could you sit down on a Windows based machine and go to work. I grew up during MS-DOS, Windows 3.1, 3.11, 95 and let me tell you, I didn't know half of what I was doing (Granted I was ~7 years old doing command prompt lines and editing Config.sys and Autoexec.bat just for fun). No one can sit down, including on Windows and just get everything to work.

2. Seriously, you claim to have a small business that repairs PC's. Do you get this frustrated with new customers? I'm mean come on, it is an Operating System. You didn't just get a speeding ticket for going a 1 MPH/KPH over the speed limit!

3. Maybe you could be open minded enough to see that Linux has some clear-cut advantages. Maybe some users want the level of customization that it offers. Maybe some want the increased security. Just because you don't like it, doesn't make it stupid.

4. You are using Ubuntu with the Gnome interface and you are complaining about too much command line!?!?!?! Dear lord, what in the world are you doing in the command line half the time. Ubuntu with Gnome or KDE is virtually all GUI.

5. If you need help ASK!!! xtknight, Pepsi, nothinman, nocmonkey, among others will go through very lengthy posts and PM's just to help you out.

Seriously, did you just make this thread to flame. Linux has some flaws, Windows has some flaws, why whine and complain to us about them who are more than willing to help you out with either of them.

-Kevin
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
Originally posted by: Markbnj
That was me, and it's not dumb . I'm a developer, and if you don't think it would be easier for me to exploit a piece of software to which I had source, as opposed to one where I was working from a disassembly, then you don't write software. What I will grant you is that it is also easier for someone else to find that same hole and patch it, but whether that dance works in favor of security, or against it, is a question neither of us have enough evidence to answer. In the past, in the face of questions like this, the default behavior has been to hide as much as possible. I think if you want to see the model changed the onus is on you to show that it would result in better security for the end user.

Ok, IIS5 versus apache 1.3.x....one is closed source, and a swiss cheese product, security wise. The other is stable, open source, and has very few critical security vunerabilities.

Maybe he was running old drivers and they patched the program. Point is he resinstalled the official nVidia drivers and it solved the problem. If WoW ran on Linux, do you think the average WoW player would have an easier time keeping drivers up to date?

easy. If they are using a distro that has support for 3d accel in the kernel/distributes binary blob drivers, then the little icon pops up in the system tray, you click update now, type in your password, and then away you go. Much easier, two clicks and a password. Oh, and it would have done that as soon as they driver was updated in the repositories, instead of crashing and having the user go look for a patch.
they do C.[/quote]

(2) gets you all of the work, with none of the benefits of keeping it proprietary and in-house (i.e. you know exactly what's out there and what people are using because you control it).
what are the benefits of keeping it proprietary? You still don't control it, because someone who doesn't update their kernel or modules still runs an older version.

(3) gets you nothing. Who is going to develop a new piece of hardware for a mass computing market and hope the open source community will get the drivers ready by the time the trucks arrive at Newegg? Nobody. This idea can't be taken seriously, at all.

That is how several do it now...no major us companies. The advantage is you know support linux, and can point all your support cases to the current maintainers, and the drivers are usually of very high quality (I don't think I have had an open source driver crash my box EVER)
It always seems to come back to the poor ignorant Windows users for you guys. You just don't get it. Windows works well-enough for the vast majority of the couple of hundred million ordinary, non-technical people who use it every day. 97% of them would shoot themselves if you threw them into the Linux world tomorrow and told them they had to get their work done there. You cannot say your model works better for a mass market, because it has never been subjected to the test. The current model has. It evolved over forty years of capitalist economic trial and error. You say your system works better? So prove it the old fashioned way: attract people to it by showing how easy it is. When you get around to that let me know.
Give your grandma a bare slate box, and a current windows CD (vista or XP, I don't care which) and an Ubuntu CD and either way, they are going to get a deer in the headlights look when you talk about installing the OS, partitioning, drivers, etc. Windows hasn't really made it easier, just more common. And when you get a vendor like HP, who has products that are very unfriendly (Photosmart printers and Officejet AIO's a few years ago were flat out incompatible) it's the same boat. The HP PS and AIO problem usually resulted in a format of the hard drive, and picking ONE of the printers to use. HP's GPLed linux drivers (although about 2 months later then windows) worked fine with both.

edit: Nested quoting is a lot harder then it looks
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
In the past, in the face of questions like this, the default behavior has been to hide as much as possible.

Those who forget history are doomed to repeat it? Security by obscurity has never worked well, would you trust an encryption algorithm that was never published?

Maybe he was running old drivers and they patched the program. Point is he resinstalled the official nVidia drivers and it solved the problem. If WoW ran on Linux, do you think the average WoW player would have an easier time keeping drivers up to date?

I doubt he was running drivers older than a week or so, he's one of those people with OCD about that kind of stuff. And WoW does run on Linux via Cedega, I know a handful of people that play that way all of the time. But the point was that people do still have problems with binary drivers and when that happens you're at the mercy of the manufacturer with the only real option being to reinstall something and hope for the best. I haven't had an OSS driver kill my machine in a very long time, infact I can't remember the last machine-crashing level problem I had that I couldn't attribute to either nVidia or VMWare.

Sorry dude, that's BS. I've been writing assembly since 1985. It's one thing to write in assembly, with symbols, and another thing to work from a disassembly without them. If you think that's as easy as reading C code then you haven't done much farting around with raw disassembly

Alright so they're not of equal difficulty, but you can't deny that making software closed source hasn't helped from a security perspective. Hell just look at the wifi firmware exploit that came out last year, you can't get much more removed from the system than the firmware of a device and people still found a way to exploit it.

(1) gets you the best chance of being done to a schedule, or close to it, and to a budget, or close to it. Afterwards you have to deal with a "constantly changing kernel," instead of working to updates from one company that uses service pack releases to update the O/S. So that's _your_ problem, in terms of the Linux community. Why would anyone stake their business on such an environment?

You also have to deal with the bad press from people labeling you a non-community player and recommending your competitor's products since they do release their source code.

(2) gets you all of the work, with none of the benefits of keeping it proprietary and in-house (i.e. you know exactly what's out there and what people are using because you control it).

The benefits of keeping the driver proprietary are questionable, as I said there's a lot of hardware companies that seem to get by just fine with OSS drivers.

(3) gets you nothing. Who is going to develop a new piece of hardware for a mass computing market and hope the open source community will get the drivers ready by the time the trucks arrive at Newegg? Nobody. This idea can't be taken seriously, at all.

Obviously we're not talking about Linux-only hardware here so no one's staking their business on someone else writing drivers for them. Release the hardware with Windows and OS X drivers but make the specs available so that someone can work on drivers if they like. If you are releasing Linux-only hardware then it only makes sense to go with option 2 so you have a driver ready on release day and you won't get shunned by the community.

It always seems to come back to the poor ignorant Windows users for you guys. You just don't get it. Windows works well-enough for the vast majority of the couple of hundred million ordinary, non-technical people who use it every day.

I do get it and I know that Windows is "good enough" for lots of people, but that doesn't mean that Windows doesn't suck. Millions of people eat at McDonald's everyday, does that automatically mean that they produce quality hamburgers?

97% of them would shoot themselves if you threw them into the Linux world tomorrow and told them they had to get their work done there.

Not likely, the relatively small transition from Win2K->XP was a huge PITA for a lot of people but they survived and XP->Vista will be even worse. If it's in a controlled environment where people are available for training, like say a corporation, then the transition wouldn't be any worse than any other software transition. At my last job everyone was used to doing their timesheets on VMS via telnet but when they rolled out the ERP system they had to get used to doing it via a website, and IMO the new software is pure crap, but everyone managed to figure it out and move on. Even the non-technical people still there from pre-ERP still look back on the VMS timesheet days fondly but no one died in the transition.

The current model has. It evolved over forty years of capitalist economic trial and error.

Capitalistic trial and error? How can you call a monopoly dictating how things will be done for the past 15 years capitalistic trial and error? You honestly think people like having to install a dozen drivers from a dozen different websites after installing their OS? Wouldn't they rather the core kernel already had all of the drivers and they were all updated at the same time automatically?

Well, since, as you have stated, most hardware OEMs aren't supportive of your model, we don't really know, do we? It's meaningless to look at the track record of current OSS drivers that are largely serving a niche market.

I would say you're overstating things a bit, most of the large OEMs support Linux just fine these days.
 

aidanjm

Lifer
Aug 9, 2004
12,411
2
0
The argument that hackers only target what is popular, and that if linux was as popular as windows it would face the same problems as windows (re: security breaches) doesn't hold water when you consider that linux is more widely deployed than windows in many areas. For example linux variants are used on 2/3 of the world's web servers and is widely regarded as being a safer bet than is a windows platform server (less likely to be compromised by hackers). IN this area, the open source model is clearly producing vastly superior results than the closed source model. This despite M$'s billions.
 

nweaver

Diamond Member
Jan 21, 2001
6,813
1
0
Originally posted by: aidanjm
The argument that hackers only target what is popular, and that if linux was as popular as windows it would face the same problems as windows (re: security breaches) doesn't hold water when you consider that linux is more widely deployed than windows in many areas. For example linux variants are used on 2/3 of the world's web servers and is widely regarded as being a safer bet than is a windows platform server (less likely to be compromised by hackers). IN this area, the open source model is clearly producing vastly superior results than the closed source model. This despite M$'s billions.

but....IIS6 has gone leaps and bounds to change this even. Just another shot in the corner of security isn't impacted by opening/closing source.
 

drag

Elite Member
Jul 4, 2002
8,708
0
0
The benefits of keeping the driver proprietary are questionable, as I said there's a lot of hardware companies that seem to get by just fine with OSS drivers.


The benifits of having OSS driver support in Linux is very very attractive for hardware manufacturers.

Generally speaking the code quality of closed source drivers is very poor. Evidence for this is show in the fact that even the highest quality closed source drivers in Linux are subject to innumberable hard-to-trigger bugs which never get fixed.

Also drivers that end up being released open source after being closed source for a while tend to be of very low code quality. Sure they work, but only in specific circumstances. They usually have to be re-written before getting accepted into the kernel itself.





As for Linux vs Windows...

One thing that I can't do in windows without difficulty is this:
Secure remote access, network, and file sharing.

To do it in Linux or other Unix system using Openssh...
ssh-keygen -t dsa
(give it a good passphrase, or leave it blank so you can do it passwordless)

This gives you two files...
~/.ssh/id-dsa
~/.ssh/id-dsa.pub

Then the next step is that you you take ~/.ssh/id-dsa.pub and copy it to any *nix box you want easy access to. Add the contents of it to ~/.ssh/authorized_keys file, or create the file if it isn't there.

Any machine you do that with will then accept your ssh connection without using the system password. If you didn't add a passphrase for it then it will just let you automaticly log in. The only thing you have to worry about then is keeping your ~/.ssh/id-dsa file very private.

Now you have a strongly authenticated system with full authentication that is safe to use over the internet as it is in LANs. It's spoof-proof, sniff-proof, and nobody can guess your password (if you disable password authentication in your ssh server, which is recommended. For paranoid security you use shared keys with passphrase)



With -X switch you now can use GUI applications security and have their output integrate cleanly in with your local desktop. Applications, copy-n-paste, look-n-feel, act and look as if they are local to your machine but actually running on a remote computer using that computer's resources. With versions of X that support AIGLX then you can also do it with 3d hardware acceleration.

With ssh you can get secure shell, which it was originally for. But also you with ssh you can remotely execute commands without having to access the remote shell first.

With sftp you can use secure ftp emulation, which numerious GUI applications support.

With scp you can easily copy files from one computer to another.

with sshfs you can easily setup user persmissions to safely mount and export access to remote file systems. Very easy. Also desktop KDE and Gnome support have their own ways of having remote systems displayed as folders using ssh.

Also you can do port forwarding and a sort of vpn using ssh so that you can remotely access network services operating on the far side of a firewall. A bit more complex then previously stuff, but it is still quite possible.


And remember with shared keys (and password authentication disabled) then it's fully encrypted, almost impossible to spoof, virtually impossible to sniff, and no way a person can guess your passwords. The only serious security concene is keeping your id-dsa file secret, and even if it gets stolen if you using passphrases they still have to then figure out your password.

All of this is aviable and the only considuration is that the remote machine has to be running a ssh server and if there is a firewall then have a single tcp port forwarded to it. (usually port 22)

 

regnez

Golden Member
Aug 11, 2006
1,156
0
76
Originally posted by: Tick
Linux SUCKS. Why? Because:

1) Command lines/Lack of GUI's

Why the fvck would I want to use a command line? I have a modern computer, capable of displaying color and icons. Why should their be a command line? And further, why doesn't everything have a gui? Gui's are good, and easy, and don't require me to learn commands. Yey for Gui's.

2)Root/sudo is stupid.

Why on earth should I have to deal with either using sudo or running as root to actually use my programs? I still can't get a lot of programs to run because they keep whining about permissions. What ever happened to good old admin accounts? Why does sudo break everything?

3)Apt-get

Now this is just plane stupid. Why is it so damn hard to install anything? I have a desktop, why not do it the way it should be done? I get the installer icon, click on it, press forward a few times, wait, and have a nice icon on my desktop. Why isn't it done this way?

4)Compiling

Again, stupid. Just give me a fvcking installer program. None of this compiling sh1t.




Come on Linux. The rest of the world has moved beyond 1990. It's time for you to do so also. I'm giving up and installing windows.

Plane stupid?

Linux is free, and no one is forcing you to use it. Just because you are either too ignorant, too impatient, or (most likely) just plane stupid, does not make Linux a bad OS; it makes Linux a bad OS for you.

If you have such a problem with operating systems, why not just get a Mac? The mouse that comes bundled with Macs only has one large button.

I think you would like it.
 

Tweakin

Platinum Member
Feb 7, 2000
2,532
0
71
I have to agree that Linux is not as easy to use as windoze. I have tried several versions "distros" and my favorite was ubuntu 6.06.1.

I have also given up several times as there are no drivers for my Linksys PCI card...and it's hard to get the thing running correctly without the ability to download...at least it was for me.

It is still sitting on my desk and I'm sure I'll drop it in again some day and give it another whril.
 

wirednuts

Diamond Member
Jan 26, 2007
7,121
4
0
there are some really nice linux packages out, but as said a lot before its just not practical. everything is designed for windows, theres nothing easier to use/nothing more compatible
 

Markbnj

Elite Member <br>Moderator Emeritus
Moderator
Sep 16, 2005
15,682
13
81
www.markbetz.net
nweaver...

Ok, IIS5 versus apache 1.3.x....one is closed source, and a swiss cheese product, security wise. The other is stable, open source, and has very few critical security vunerabilities.

It's a straw-man argument, to be honest. Of course either model can produce a bad implementation. The question is whether access to source code makes it easier to find and exploit holes. I'd say it is obvious that it does.

easy. If they are using a distro that has support for 3d accel in the kernel/distributes binary blob drivers, then the little icon pops up in the system tray, you click update now, type in your password, and then away you go. Much easier, two clicks and a password. Oh, and it would have done that as soon as they driver was updated in the repositories, instead of crashing and having the user go look for a patch.

Again, you're cherry picking. If the user is running the right distro, and if they got it set up correctly to begin with, and if they know their admin password, and whatever other conditions apply, then it's easy to update the driver. The fact is that virtually everyone at this point knows how to go install a new driver for Windows. That's why it matters when something becomes a de facto consumer standard.

what are the benefits of keeping it proprietary? You still don't control it, because someone who doesn't update their kernel or modules still runs an older version.

Unavoidable anyway. The point is that there are no versions out there that you didn't write, and can't support.

That is how several do it now...no major us companies. The advantage is you know support linux, and can point all your support cases to the current maintainers, and the drivers are usually of very high quality (I don't think I have had an open source driver crash my box EVER)

It really doesn't matter. Companies buy into or sell out of technical "movements" all the time that don't end up going anywhere, and they have various reasons for doing so. Most of the examples you come up with are companies that have adopted a different model in order to distinguish themselves from Microsoft. I don't think any of us are in doubt as to why Oracle, IBM, Sun, HP, etc., support Open Source as vigorously as they do, are we? The number of technology coalitions that have come and gone as a response to a dominant competitor over the last twenty years is large. The only question that matter is whether it is a better model. If it is, then it will eventually take hold and win out over the alternatives. I wouldn't hold my breath on open source, myself, but maybe I'm wrong.

Windows hasn't really made it easier, just more common.

I would say Windows has made it both easier, and more common.

Nothinman...

Those who forget history are doomed to repeat it? Security by obscurity has never worked well, would you trust an encryption algorithm that was never published?

There are some areas where security by obscurity works very well. In large swaths of banking, defense, utility management, etc., system source code is treated as a highly proprietary asset, for this and other reasons. Encryption algorithms aren't a very good example, imho, not least of all because they are small and very self-contained, and thus not as vulnerable to hidden complexity and forgotten corners of poorly engineered code.

But the point was that people do still have problems with binary drivers and when that happens you're at the mercy of the manufacturer with the only real option being to reinstall something and hope for the best. I haven't had an OSS driver kill my machine in a very long time, infact I can't remember the last machine-crashing level problem I had that I couldn't attribute to either nVidia or VMWare.

I haven't had a closed source driver kill my XP box in a very long time, so what's the point? Being at the mercy of the manufacturer hasn't caused me any problems, because my platform of choice is extremely popular and thus very well-supported. But we keep mixing things up here. If we're just talking about Linux on the desktop, then it's understandable why you guys would want drivers open sourced, since that is one way to at least get drivers.

Alright so they're not of equal difficulty, but you can't deny that making software closed source hasn't helped from a security perspective. Hell just look at the wifi firmware exploit that came out last year, you can't get much more removed from the system than the firmware of a device and people still found a way to exploit it.

I can't prove that negative any more than I can prove that even if I had left my front door open last night I would not have been robbed. But on the other hand I can render a judgement that leaving my door open is likely to increase the chance of being robbed. There have been cases where the accessibility of source code has led to people finding and exploiting holes. There was one recently where someone fairly well-known in FOSS circles complained about his open source forums being repeatedly hacked. In that particular case it's likely that having the source proprietary would have prevented the attacks, because they were simple mischief that someone would probably not have devoted a huge amount of time to.

You also have to deal with the bad press from people labeling you a non-community player and recommending your competitor's products since they do release their source code.

Hah, you mean that if a company doesn't rely on an open source model for its business it will be slammed by people who prefer an open source model, and so they should adopt an open source model to prevent that? What does "community minded" have to do with anything? The only community a business needs to care about from a commercial perspective is the community of its paying customers. If enough of them want open source then a smart business will provide them. By definition, open source will win if it makes sense, not because the FOSS protesters march in front of some vendor's parking lot .

The benefits of keeping the driver proprietary are questionable, as I said there's a lot of hardware companies that seem to get by just fine with OSS drivers.

"Get[ting] by just fine" is hardly a stirring description of the advantages. If the benefits of proprietary software are questionable, after forty years of evolution of the business model, should we just accept that the open source model is better, after ten years of little success?

I do get it and I know that Windows is "good enough" for lots of people, but that doesn't mean that Windows doesn't suck. Millions of people eat at McDonald's everyday, does that automatically mean that they produce quality hamburgers?

Yes, because there is no inherent standard of value. A thing is worth what the consumer thinks it is worth at the time of consumption. At the moment when someone wants a hot, fast, cheap meal McDonalds might very well make the best hamburger in the world.

Capitalistic trial and error? How can you call a monopoly dictating how things will be done for the past 15 years capitalistic trial and error? You honestly think people like having to install a dozen drivers from a dozen different websites after installing their OS? Wouldn't they rather the core kernel already had all of the drivers and they were all updated at the same time automatically?

Pretty lame argument on several levels. First, Microsoft hasn't dictated anything that really matters to ISVs. What they have done is produce a very popular operating platform, on which anyone can develop software with certain expectations as to the platform's capabilities, and have those expectations fulfilled at runtime. Secondly, all of the major innovators of the last twenty years, whether Lotus, or Quicken, or Adobe, or whomever, have taken advantage of Microsoft's success, not the other way around. Thirdly, nobody has to visit a dozen websites for drivers after installing XP. I have exactly three pieces of hardware that require drivers on this machine: the Audigy, the TV Wonder, and the 7600GT. Sound and Video work out of the box on XP. The TV Wonder works out of the box on Vista.
 

IEC

Elite Member
Super Moderator
Jun 10, 2004
14,362
5,033
136
Linux ROCKS. Why? Because:

1) Several different GUIs/user environments to choose from, infinitely customizable desktop

2) Root/sudo prevents people from doing stupid things and is good security practice

3) Apt-get is one of the ways to upgrade - it also happens to be very easy. There are also GUI-based package managers

4) Compiling? Don't need to with an rpm or other package.

I'm sorry Tick, but I guess you just downloaded a Linux distro from 1990. All the ones I've tried in the past 2-3 years have been pretty easy to use.

Windows is for you.
 

M00T

Golden Member
Mar 12, 2000
1,214
1
0
Closed source equates to reinventing the wheel over and over again, unless you have the money to "license" the "invention."

Open source is the right direction for making human progress. I only wish the fundamental ideas could be implemented in other aspects of our lives.
 
sale-70-410-exam    | Exam-200-125-pdf    | we-sale-70-410-exam    | hot-sale-70-410-exam    | Latest-exam-700-603-Dumps    | Dumps-98-363-exams-date    | Certs-200-125-date    | Dumps-300-075-exams-date    | hot-sale-book-C8010-726-book    | Hot-Sale-200-310-Exam    | Exam-Description-200-310-dumps?    | hot-sale-book-200-125-book    | Latest-Updated-300-209-Exam    | Dumps-210-260-exams-date    | Download-200-125-Exam-PDF    | Exam-Description-300-101-dumps    | Certs-300-101-date    | Hot-Sale-300-075-Exam    | Latest-exam-200-125-Dumps    | Exam-Description-200-125-dumps    | Latest-Updated-300-075-Exam    | hot-sale-book-210-260-book    | Dumps-200-901-exams-date    | Certs-200-901-date    | Latest-exam-1Z0-062-Dumps    | Hot-Sale-1Z0-062-Exam    | Certs-CSSLP-date    | 100%-Pass-70-383-Exams    | Latest-JN0-360-real-exam-questions    | 100%-Pass-4A0-100-Real-Exam-Questions    | Dumps-300-135-exams-date    | Passed-200-105-Tech-Exams    | Latest-Updated-200-310-Exam    | Download-300-070-Exam-PDF    | Hot-Sale-JN0-360-Exam    | 100%-Pass-JN0-360-Exams    | 100%-Pass-JN0-360-Real-Exam-Questions    | Dumps-JN0-360-exams-date    | Exam-Description-1Z0-876-dumps    | Latest-exam-1Z0-876-Dumps    | Dumps-HPE0-Y53-exams-date    | 2017-Latest-HPE0-Y53-Exam    | 100%-Pass-HPE0-Y53-Real-Exam-Questions    | Pass-4A0-100-Exam    | Latest-4A0-100-Questions    | Dumps-98-365-exams-date    | 2017-Latest-98-365-Exam    | 100%-Pass-VCS-254-Exams    | 2017-Latest-VCS-273-Exam    | Dumps-200-355-exams-date    | 2017-Latest-300-320-Exam    | Pass-300-101-Exam    | 100%-Pass-300-115-Exams    |
http://www.portvapes.co.uk/    | http://www.portvapes.co.uk/    |