Juan Pablo Hierro writes:
> El Lun 14 Ene 2002 02:59, escribió:
> > > 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.
> Here is the complete error message:
> Started device management daemon for /dev
> error copying "/dev-state/fb" to "/dev/fb"
> Looking /dev, I find
> ls -l /dev | grep fb ==>
> drwxr-xr-x 1 root root 0 ene 1 1970 fb
> While in /dev-state, I have
> ls -l /dev-state | grep fb
> lrwxrwxrwx 1 root root 3 ene 10 03:16 fb -> fb0
> crw------- 1 root root 29, 0 ago 30 22:30 fb0
> and so on, upto fb31
> Now, I think that, maybe, in /dev-state I have the old /dev from my
> fresh RH7.2 system while in /dev I have the devices used by my new,
> hand-compiled kernel 2.2.17. Of course, I did not compile it with
> the same options. In fact, it has no framebuffer support.
OK. Delete /dev-state/fb and things should work fine. /dev/fb should
not be a symbolic link.