Summary: | sys-apps/baselayout-2 does not create all device nodes within OpenVZ VPS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | geek |
Component: | [OLD] Core system | Assignee: | Gentoo VPS Team (OBSOLETE) <vserver-devs+disabled> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
geek
2007-08-24 21:34:00 UTC
This doesn't use udev, or??? Don't see how's baselayout related to creating device nodes. Yes this is using udev, but I do not think udev is the problem because udev relies on having the right items in /sys to create the device nodes. In this case the /sys tree is missing a lot. Now I thought that the kernel created and populated /sys, but I must be wrong because I am running the same kernel in the Debian virtual env and /sys is fine there, so it must be something in Gentoo that is causing this. I am not sure if it is baselayout and/or makedev, but this is my prime suspect at the moment. Here is my small /sys tree in the virtual env: # ls -l /sys total 0 drwxr-xr-x 4 root root 0 Aug 24 19:18 class # ls -l /sys/class/ total 0 drwxr-xr-x 4 root root 0 Aug 24 19:18 net drwxr-xr-x 3 root root 0 Aug 24 19:18 tty # ls -l /sys/class/net/ total 0 drwxr-xr-x 2 root root 0 Aug 24 22:16 lo drwxr-xr-x 3 root root 0 Aug 24 22:16 venet0 # ls -l /sys/class/tty/ total 0 drwxr-xr-x 2 root root 0 Aug 24 22:16 ptmx (In reply to comment #2) > Yes this is using udev, but I do not think udev is the problem because udev > relies on having the right items in /sys to create the device nodes. In this > case the /sys tree is missing a lot. Well, then that's a kernel issue, not baselayout :) (In reply to comment #3) > Well, then that's a kernel issue, not baselayout :) It may not be baselayout, but I don't think it's a kernel issue either. If I install the template from http://download.openvz.org/template/precreated/gentoo-20060317-amd64-stage3.tar.gz (which is the current "official" gentoo openvz template), then I get a much better /dev lifting as follows: # ls -l /dev total 8 lrwxrwxrwx 1 root root 15 Aug 25 01:18 MAKEDEV -> ../sbin/MAKEDEV lrwxrwxrwx 1 root root 13 Aug 25 01:18 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 Mar 17 2006 full prw------- 1 root root 0 Aug 25 01:19 initctl crw-rw-rw- 1 root root 1, 3 Mar 17 2006 null crw-rw-rw- 1 root tty 5, 2 Mar 17 2006 ptmx drwxr-xr-x 2 root root 4096 Mar 17 2006 pts crw-rw-rw- 1 root tty 2, 0 Aug 25 01:19 ptyp0 crw-rw-rw- 1 root tty 2, 1 Mar 17 2006 ptyp1 crw-rw-rw- 1 root tty 2, 2 Mar 17 2006 ptyp2 crw-rw-rw- 1 root tty 2, 3 Mar 17 2006 ptyp3 crw-rw-rw- 1 root tty 2, 4 Mar 17 2006 ptyp4 crw-rw-rw- 1 root tty 2, 5 Mar 17 2006 ptyp5 crw-rw-rw- 1 root root 1, 8 Mar 17 2006 random drwxr-xr-x 2 root root 4096 Mar 17 2006 shm lrwxrwxrwx 1 root root 4 Aug 25 01:17 stderr -> fd/2 lrwxrwxrwx 1 root root 4 Aug 25 01:17 stdin -> fd/0 lrwxrwxrwx 1 root root 4 Aug 25 01:17 stdout -> fd/1 crw-rw-rw- 1 root tty 5, 0 Mar 17 2006 tty crw--w---- 1 root tty 3, 0 Aug 25 01:19 ttyp0 crw-rw-rw- 1 root tty 3, 1 Mar 17 2006 ttyp1 crw-rw-rw- 1 root tty 3, 2 Mar 17 2006 ttyp2 crw-rw-rw- 1 root tty 3, 3 Mar 17 2006 ttyp3 crw-rw-rw- 1 root tty 3, 4 Mar 17 2006 ttyp4 crw-rw-rw- 1 root tty 3, 5 Mar 17 2006 ttyp5 cr--r--r-- 1 root root 1, 9 Mar 17 2006 urandom crw-rw-rw- 1 root root 1, 5 Mar 17 2006 zero This seems to include all of the things that are missing from the template that I am having the problem with. As far as I understand, OpenVZ shares it's kernel amongst all of it's virtual environments. So I just don't see how it can work in one gentoo environment and not in another. Does this still seem like a kernel issue? you are not even allowed to create device nodes inside, you have to create them from outside (In reply to comment #5) > you are not even allowed to create device nodes inside, you have to create them > from outside Yeah, looks like my problem is fixed when I set RC_DEVICES="static". Now it is bringing in all the devices I have set up in my /vz/private/101/dev area. I guess I was hoping that because baselayout-2 supports VPS environments that it would take care of this automatically. If not then this bug is just a configuration error and can be closed. |