OK, so we have gone most of the distance in getting DEVFS working on our
ProPack. We still have a few more problems and I was hoping you could
shed some light on these.
1) We have a weird bug where when you mount an IDE CDROM on some machines,
the mount point (let's say /mnt/cdrom) changes from a directory to a
zero-byte flat file with the epoch as its creation date. It sometimes
will mount, but the directory will be empty -- if this happens, the mount
table gets real screwed up and you cannot umount the cd or mount it again
in another directory because it is already mounted.
But, this only happens on some machines...the machines it does happen on,
it consistantly has the problem. Others don't seem to face it. If you
use a non-DEVFS kernel, mounting works fine.
2) For some reason, devfsd is not creating the proper /dev/vcs links on
SuSE 6.4. It works fine on TurboLinux and Red Hat, but on SuSE, these
links are not being created which is causing the mingettys on the virtual
consoles to not start (except for vcs1 which is weird).
3) /dev/fb0 is not being linked to the correct devfs device. (in the FAQ,
it says frame buffers are supported by DEVFS). this does not seem good:
[root@counselor /dev]# ls -l fb/
total 0
lr-xr-xr-x 1 root root 0 May 4 13:26 fb0 -> fb0
this also seems to be true for /dev/unikey and /dev/encode-gb which are
i18n related patches to the kernel that we include for Chinese and
Japanese support. I guess I can use devfsd to add these devices -- is
that the best way? or should I hack the boot scripts to mknod these each
time the machine boots?
Thanks,
-tduffy
PS, on the devfs FAQ page, where it talks about the /etc/securetty, you
may want to mention that if you have login from util-linux 2.10k or
greater, you will need to add vc/1-6 instead of 1-6.
The same goes for console.perms. Change it to vc/[0-9][0-9]*
|