On Wed, Feb 12, 2003 at 12:08:45PM -0500, Matt Price wrote: > > Presumably you can still see it in a 'lsmod' from within the chroot? > > Have you created the /dev/nv* devices? Do they have reasonable > > permissions? > > argh! that's it -- I didn't create the devices. But now I don't know > how to go further. Ordinarily I would follow some set of instructions > to mknod the file using particular major and minor node numbers; but I > don't have those numbers recorded anywhere. Is there a way to fnd out > what the mode numbers of an existing device file are (then I could > just look them up and duplicate the file...).
Sure. Just 'ls -l /dev/nv*' in your main system, and use mknod to recreate the devices. The X,Y you see in the ls are the major and minor number that mknod wants. > Alternatively, is there anything wrong with just copying the /dev > directory on my main installation over to my chroot? That'll work. > Or better, just making /chroot/dev a symbolic link to the main /dev > directory? That won't work, since a symlink is just a by-name reference to another file; the chroot'd /dev will contain a bunch of files referring to, f'r instance, '../dev/nvctl' which will not be accessible once inside the chroot. > If that's an acceptable solution, it would certainly be the one I > prefer. Symlinks won't work, but there are two kinda similar alternatives: either hardlink (using ln without the -s option) which will create a link based on inode numbers (which will be the same both inside and outside) or kernel 2.4's new 'bind mounts', which let you mount files anywhere within a file system. man mount can tell you more about that. > I imagine this would help me with ALSA as well, which I haven't been > able to interact with either. Ah, yeah. ALSA uses device nodes in /dev/sound/, and if it's compiled with OSS emulation support, it also has /dev/dsp and such. Personally, I'd probably just copy the files over, since I'm lazy, you do have a few other choices. -- Rob Weir <[EMAIL PROTECTED]> http://ertius.org/
msg30419/pgp00000.pgp
Description: PGP signature
