Sergei Haller schrieb:

On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:

...

Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.

shouldn't the device be automatically created when you load the module nvram?

    Sergei

Yes, when I load nvram.ko /dev/nvram is created. But with Suse 10.0. I did not had to load nvram.ko, but /dev/nvram was created by the entry in static_devices.txt, and that was sufficient. Should nvram be loaded by some automatism, or do I have to put it in boot.local? Jörg

Dr. Werner Fink schrieb:

On Sat, May 20, 2006 at 04:46:03PM +0200, Joerg Riechardt wrote:

...

Sergei Haller schrieb:

...

On Fri, 19 May 2006, Joerg Riechardt (JR) wrote:

...

Well that IS what I do, but it´s only a workaround. The Suse installer moved my static_devices.txt to static_devices.txt.rpmsave, probably there is a reason for that, I wonder how the "correct" udev solution looks.

shouldn't the device be automatically created when you load the module nvram?

   Sergei

Yes, when I load nvram.ko /dev/nvram is created. But with Suse 10.0. I did not had to load nvram.ko, but /dev/nvram was created by the entry in static_devices.txt, and that was sufficient. Should nvram be loaded by some automatism, or do I have to put it in boot.local? Jörg

Run

vi +/MODULES_LOADED_ON_BOOT /etc/sysconfig/kernel

read the text above and just do what you've read:)

   Werner

thanks, Jörg