> > 14. Friendly names for drivers. I shouldn't need to > google for the 3 or 4 letter driver name I need, add > it, tweak driver_aliases.......: I want the hardware > to Just Work (TM). > So i need to google or check the dmesg just because I > would like to know > what kind of card i am using like in linux where > every ethernet adapther is eth?
On windows I do this for devices that don't have drivers in the base OS: 1. Go to manufacturer's website to get drivers. 2. Install. 3. Configure NIC in the GUI. This is the ultimate aim, however it is unrealistic at this stage to expect every hardware vendor to have Solaris drivers. In the meantime, we need a community maintained resource, part in the binary distro, part online, that provides the user with the easiest path to install. A big fat directory with working installable packages for cards that are known to work with community-derived drivers is the first logical step. Community review of installable packages before entry to list required (e.g. one of Masayuki Murayama's drivers I tried out had a broken install script that failed to update driver_aliases on the particular Nevada build I used). We *badly* need some sort of repository for non-Sun hardware drivers, plus packages that give us specific driver_aliases entries for individual hardware items, in the same way that Blastwave and Sun Freeware give us non-Sun apps and tools. Andrew. -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://opensolaris.org/mailman/listinfo/indiana-discuss
