From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lindsay Haisley Date: Tue, 21 Dec 2004 16:11:06 +0000 Subject: Re: Bug#286040: please allow permissions.d to follow symlinks Message-Id: <20041221161106.GC18870@fmp.com> List-Id: References: <20041217083115.GA4050@wonderland.linux.it> In-Reply-To: <20041217083115.GA4050@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Thus spake martin f krafft on Tue, Dec 21, 2004 at 02:04:13AM CST > also sprach Lindsay Haisley [2004.12.20.2005 +0100]: > > as boot-time device config is concerned. Until all device modules from all > > vendors support sysfs then this may be necessary. Red Hat and other distros > > use other methods, but the issue is probably the same. > > As it sounds like a workaround, sure, it should take precedence. > > > I use RC_DEVICE_TARBALL to store and retrieve VMware devices. > > Why not define custom rules? Or is it just not possible without > sysfs support? > > Then maybe you want to add a modutils hook? Yes, you're right. I could use a modules post-install to create the devices. In the case of VMware, I could also put appropriate mknod's in /etc/init.d/vmware, which is what the VMware people suggest. I think I needed to get my guest OS up and running in a hurry, maybe to do my monthly billing or some such and using RC_DEVICE_TARBALL was quick and easy. Because The VMware kernel modules don't support sysfs at all, I don't think it's possible to do a workaround in any kind of udev rule. FYI, here's the word on udev and sysfs from one of the VMware folks on the VMware community forum: > 1. Is there likely to be an evolution of VMWare to > be compatible with udev? There is bug filled on this, but problem is that vmware supports vmnet0-vmnet255 - and we do not want to pollute /dev with them, as normal people need only 2 or 3. In future vmnet will use just one multiplexing device, like Windows's vmnet does, but until then likelihood of udev being supported is rather low. Maybe if SuSE 9.2/10 or RHEL4 will use udev, something will have to be done about it, but I find sysfs really ugly and hard to use. > 2. Is setting up /dev/vmnet0 just a question of > running MAKEDEV with the appropriate major and minor > device numbers? (So that reconstructing the kernel > modules can be avoided.) Yes. Just place appropriate mknod somewhere - probably beginning of /etc/init.d/vmware is best place for them. -- Lindsay Haisley | "Fighting against human | PGP public key FMP Computer Services | creativity is like | available at 512-259-1190 | trying to eradicate | http://www.fmp.com | dandelions" | | (Pamela Jones) | ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel