All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lindsay Haisley <fmouse-gentoo@fmp.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#286040: please allow permissions.d to follow symlinks
Date: Tue, 21 Dec 2004 16:11:06 +0000	[thread overview]
Message-ID: <20041221161106.GC18870@fmp.com> (raw)
In-Reply-To: <20041217083115.GA4050@wonderland.linux.it>

Thus spake martin f krafft on Tue, Dec 21, 2004 at 02:04:13AM CST
> also sprach Lindsay Haisley <fmouse-gentoo@fmp.com> [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://pubkeys.fmp.com>
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

  parent reply	other threads:[~2004-12-21 16:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17  8:31 Bug#286040: please allow permissions.d to follow symlinks Marco d'Itri
2004-12-17 10:11 ` Stefan Schweizer
2004-12-17 10:48 ` martin f krafft
2004-12-17 13:24 ` Kay Sievers
2004-12-17 13:38 ` martin f krafft
2004-12-17 13:40 ` Marco d'Itri
2004-12-17 13:45 ` Kay Sievers
2004-12-17 13:47 ` Kay Sievers
2004-12-17 13:49 ` Marco d'Itri
2004-12-17 13:56 ` Kay Sievers
2004-12-17 13:58 ` martin f krafft
2004-12-17 14:13 ` Kay Sievers
2004-12-17 14:19 ` martin f krafft
2004-12-17 14:20 ` Kay Sievers
2004-12-17 14:35 ` martin f krafft
2004-12-17 14:36 ` Stefan Schweizer
2004-12-17 14:42 ` martin f krafft
2004-12-17 14:45 ` Kay Sievers
2004-12-17 14:52 ` martin f krafft
2004-12-17 15:50 ` Greg KH
2004-12-17 16:14 ` martin f krafft
2004-12-17 16:45 ` Greg KH
2004-12-17 17:10 ` martin f krafft
2004-12-17 17:45 ` Stefan Schweizer
2004-12-17 18:33 ` Greg KH
2004-12-17 18:40 ` martin f krafft
2004-12-17 23:25 ` Kay Sievers
2004-12-17 23:41 ` martin f krafft
2004-12-18  0:25 ` Lindsay Haisley
2004-12-18  0:53 ` martin f krafft
2004-12-18  1:18 ` martin f krafft
2004-12-18  3:04 ` Greg KH
2004-12-18  4:18 ` Lindsay Haisley
2004-12-18  4:21 ` martin f krafft
2004-12-18  9:48 ` Stefan Schweizer
2004-12-18 12:33 ` Tobias Klauser
2004-12-18 13:04 ` Marco d'Itri
2004-12-19  4:34 ` Randy.Dunlap
2004-12-20  9:39 ` martin f krafft
2004-12-20 17:56 ` Lindsay Haisley
2004-12-20 18:04 ` martin f krafft
2004-12-20 19:05 ` Lindsay Haisley
2004-12-21  8:04 ` martin f krafft
2004-12-21 16:11 ` Lindsay Haisley [this message]
2004-12-21 16:31 ` Lindsay Haisley
2004-12-21 16:38 ` martin f krafft
2004-12-21 16:48 ` Tobias Klauser
2004-12-21 16:54 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041221161106.GC18870@fmp.com \
    --to=fmouse-gentoo@fmp.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.