It doesn't actually make sense to use yast for drivers.
Let's say I worked for a RAID manufacturer. I sign up for the free email service. That's nice but it doesn't help me that much. I'm already in the beta program so I already know what new releases are coming out.
So let's say I become a full partner. Now I can just say, "Use yast to install the SCSI driver." But obviously, the customer is going to ask, "How can I use yast when I don't even have the RAID driver to install the blasted system?"
So hopefully SuSE is going to create driver disks for me I guess.
The customer completes the install then upgrades their kernel so now they can't boot. And I say, "You have to install the new driver using yast when you upgrade the kernel. Boot to the old kernel and take care of that."
But the thing is that yast doesn't normally save the old kernel after an upgrade, so the customer is righteously screwed. Since the system isn't bootable they decide to install Windows XP Server Edition instead.
It would be nice if SuSE set up a driver disk page though. That would be useful.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds