BUSCAIDEAS@xxxxxxxx writes:
> This is my first mail in this list. I write you because I have recently
> recompiled a 2.4.17 linux kernel on top of a RH7.2 system to test devfs
> and it was just a matter of following the instructions in the documentation
> of the kernel. The configuration makes use of /dev-state to save ownerships
> from boot to boot. (Yes, I have changed /etc/rc.d/rc.sysinit according
> to instructions and uncommented the suggested lines in /etc/devfsd.conf).
>
> It works basically right and now /dev looks much prettier and cleaner on
> my system. Just a couple of questions:
>
> 1) When loading, there is an error in "Copying /dev-state/fb to /dev/fb".
> However, then it works fine. Maybe, is there a need to build a tarfile
> for that devices?
No, no tarfiles! Please send the complete error message and any other
information that you might think will help identify the problem.
> 2) The most serious comes when shuting down. I get the following messages
> almost at the end (while it is unmounting everything)
> ///////////////////////////////////////////
> umount2: Device or resource busy
You can't unmount devfs, because it is always being used. A newer
version of umount(8) (from util-linux) fixes the "umount -a" case.
> umount: devfs: not found
I guess umount(8) got confused.
> umount: /dev: Illegal seek
Even more so. Just symptoms of the underlying problem. Don't unmount
devfs.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|