On Mon, 10 Jan 2005 16:46:12 +0000, Neil Bothwick <[EMAIL PROTECTED]> wrote: > On Mon, 10 Jan 2005 11:18:19 -0500, Dan Barr wrote: > > > The solution was to set RC_DEVICE_TARBALL="yes" in /etc/conf.d/rc. I > > was running a full udev system, so I had set that option to no. But, > > with it set to no, each time I rebooted the machine, the /dev entries > > that vmware_config.pl created would get lost, hence the not configured > > message. Enabling the device tarball persists those /dev entries > > across reboots. > > I fixed this by editing /etc/init.d/vmware and adding three lines to the > beginning of the start() function. > > rm -f /etc/vmware/not_configured > [ -r /dev/vmnet0 ] || mknod -m 600 /dev/vmnet0 c 119 0 > [ -r /dev/vmnet8 ] || mknod -m 600 /dev/vmnet8 c 119 8
Yes, that would be a better way. I didn't really like having to enable the device tarball, since in my mind it kinda defeats the purpose of udev. Thanks for the tip, I didn't know about the /etc/vmware/not_configured file at all. Dan -- Daniel Barr http://www.danbarr.com/ Asst Manager, Network & Security Mercer Insurance Group -- gentoo-user@gentoo.org mailing list
