PuppyThis forum is for the discussion of Puppy Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Here is a new version of the Ethernet/network wizard.
This version provides a GUI to install network windows drivers using ndiswrapper !
So it is now really becoming a one stop shop for network connectivity.
It also includes the following minor bug fix:
- After loading a module it now shows it in the list of modules loaded. Before it only showed the ones that came with puppy..
To say about ndiswrapper: it's preferrable to use native drivers, so ndiswrapper ought to be used only if no native drivers exist. Many users still tend to use ndiswrapper despite the fact that they could use native drivers, they are just too lazy to go and look around for them (if they're not installed by default). So providing them with easier means of using ndiswrapper means pushing some of them to use non-native drivers, which is exactly what should not be done (unless you will want to encourage manufacturers to only write Windows drivers and never write drivers for Linux).
I understand the advantages of native drivers. I also understand the point about pressuring the card manufacturers to provide native drivers and open their specs.Actually I only use linux drivers for my wireless cards thats why it took me so long to get to make the changes to the wizard.
The fact is that there are many people with cards that don't have native drivers that still want to try linux.
I think that the more people uses linux the more the card vendors will feel that it makes economic sense for them to provide native drivers. The shift is already happening on the server side where now there are more vendors that support linux at the application and hardware level.
So I'm not pushing them to use windows drivers I am helping them use linux. If they ever need the better functionality provided by the native drivers, they will find a way to install them.
By calling people lazy you are doing exactly the oposite than you are preaching.
Please I am just clarifying why I provided this. I don't want to start a flame or religious war. I don't want this thread to become one.
I unfortunately have to use the ndis wrapper since my networkcard manufacturer doesn't include linux drivers. It works great but I have to set it up each time I use puppy. Does this ndis wizard allow it to save to the session so I don't have to run modconfig form the terminal each time I boot?
The fact is that there are many people with cards that don't have native drivers that still want to try linux.
So I'm not pushing them to use windows drivers I am helping them use linux. If they ever need the better functionality provided by the native drivers, they will find a way to install them.
By calling people lazy you are doing exactly the oposite than you are preaching.
Well said!
All I want to do is try Linux (and now I have it installed on two machines).
Thank the higher power for people like you who simply want to help people like me and NOT call me stupid, ignorant, lazy, helpless, or any other of the two thousand words used to describe.......well, I think you get the message.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.