I thought the rc.devfs was an older (translation unused in the 2.4.0) script...
I could definitely be mistaken. How have you invoked it? Also, I think
the RTLD errors can be fixed by compiling devfsd with `make CC=kgcc install`
under RH 7.0 (I'm not super positive about this, I'm running RH 6.2). Also,
you may need to make sure that you have the updated modutils, e2fsprogs,
util-linux, etc. mentioned in
/wherever/you/untarred/kernel/src/Documentation/Changes.
Thanks,
Jason
At Tue, 16 Jan 2001 13:23:26 -0600, "Ernesto CEDILLO-ARIAS"
<ollidec@xxxxxxxxxxxxx>
wrote:
>
>Hello
>
>There is a file called rc.devfs which I think does the job. You must
>set it
>up in your init scripts. By the way I had problems compiling devfsd
>under
>2.4.0 and glibc-2.2. I had to compile it on another RH6.1 and then copy
>the
>exec to my newer system.
>I got RTLD_NEXT undeclared error. Do you have any idea about this?
>
>
>----- Original Message -----
>From: <corleyja@xxxxxxxxxxxx>
>To: <devfs@xxxxxxxxxxx>
>Sent: Tuesday, January 16, 2001 1:14 PM
>Subject: persistence across reboots
>
>
>>
>> I apologize if this is not the correct forum for this question, but
>I have
>> been unable to find an answer to my questions anywhere else. I have
>the
>> 2.4.0 kernel running with devfs enabled. I have followed the instructions
>> found at http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html to
>a tee,
>> and yet I still cannot get devfs to save permissions across a reboot.
>> For example, if I chown user /dev/sound/* and reboot, when the box
>comes
>> back up, I see that the files are owned by root again. I have added
>the
>> following to my /etc/rc.d/rc.sysinit file:
>>
>> mount --bind /dev /dev-state
>> mount -t devfs none /dev
>> /sbin/devfsd /dev
>>
>> I've also edited my /etc/devfsd.conf file as follows:
>>
>> # Sample /etc/devfsd.conf configuration file.
>> # Richard Gooch <rgooch@xxxxxxxxxxxxx> 3-JUL-2000
>> #
>> # Enable full compatibility mode for old device names. You may comment
>> these
>> # out if you don't use the old device names. Make sure you know what
>you're
>> # doing!
>> REGISTER .* MKOLDCOMPAT
>> UNREGISTER .* RMOLDCOMPAT
>>
>> # You may comment out the above and uncomment the following if you've
>> # configured your system to use the original "new" devfs names or
>the
>really
>> # new names
>> #REGISTER vc/.* MKOLDCOMPAT
>> #UNREGISTER vc/.* RMOLDCOMPAT
>> #REGISTER pty/.* MKOLDCOMPAT
>> #UNREGISTER pty/.* RMOLDCOMPAT
>> #REGISTER misc MKOLDCOMPAT
>> #UNREGISTER misc RMOLDCOMPAT
>>
>> # You may comment these out if you don't use the original "new" names
>> REGISTER .* MKNEWCOMPAT
>> UNREGISTER .* RMNEWCOMPAT
>>
>> # Enable module autoloading. You may comment this out if you don't
>use
>> # autoloading
>> LOOKUP .* MODLOAD
>>
>> #
>> # Uncomment this if you want permissions to be saved and restored
>> REGISTER .* COPY /dev-state/$devname $devpath
>> CHANGE .* COPY $devpath /dev-state/$devname
>> CREATE .* COPY $devpath /dev-state/$devname
>>
>> Is there something I'm missing/not understanding? Well, there's obviously
>> a fair amount I'm not understanding, but is it because I'm misreading
>the
>> documents, looking at the wrong source, etc.? Any help anyone can
>offer
>> would be greatly appreciated.
>>
>> Jason
>> Free, encrypted, secure Web-based email at www.hushmail.com
>
Free, encrypted, secure Web-based email at www.hushmail.com
|