User: Password:
|
|
Subscribe / Log in / New account

Using Yast doesn't actually make sense

Using Yast doesn't actually make sense

Posted May 25, 2006 14:46 UTC (Thu) by niner (subscriber, #26151)
In reply to: Using Yast doesn't actually make sense by error27
Parent article: The Novell Partner Linux Driver Process

> 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 when driver updates are available through yast online update, like the kernel is, the user would get both, the new kernel and the updated driver at the same time. So where's the problem?


(Log in to post comments)

Using Yast doesn't actually make sense

Posted May 25, 2006 20:41 UTC (Thu) by error27 (subscriber, #8346) [Link]

Under the old method you would would install with a driver disk. That means you don't have an foo_raid_driver.rpm. So when you upgrade the kernel there are no depends that will force you to upgrade the foo_raid_driver.rpm.

Maybe under the new process the driver disk will install a dummy rpm... I guess that would be amazing and wonderful...

The way I'm reading it, drivers would be in a seperate package from the base kernel. It's still an out of tree driver but it's distributed by SuSE. That's silliness obviously. It would make a lot more sense to include it in the stock SuSE kernel. That way you wouldn't have to worry about dummy RPMs or anything like that.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds