All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@access.unizh.ch>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#286040: please allow permissions.d to follow symlinks
Date: Tue, 21 Dec 2004 16:48:57 +0000	[thread overview]
Message-ID: <200412211749.02086.tklauser@access.unizh.ch> (raw)
In-Reply-To: <20041217083115.GA4050@wonderland.linux.it>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

On Tuesday 21 December 2004 17:38, martin f krafft wrote:
> also sprach Lindsay Haisley <fmouse-gentoo@fmp.com> [2004.12.21.1731 +0100]:
> > The point is that as long as Gentoo provides this feature, which
> > overrides udev rules at boot then udev is potentially only useful
> > for configuring hot plugged devices on a running system and the
> > question of udev rules and permissions.d for setting boot-time
> > options is moot.
>
> ... for Gentoo systems, yes.
>
> Anyway, since the tarball thingie really just defeats the purpose of
> udev, I doubt that Gentoo will support it much longer.

AFAIK the tarball was only a workaround for older udev versions on which some 
nodes (e.g. /dev/console which is needed for booting) were missing during 
bootup. I guess they're fixed now and there is no problem running udev 
without the tarball.

Thanks, Tobias

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-12-21 16:48 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
2004-12-21 16:31 ` Lindsay Haisley
2004-12-21 16:38 ` martin f krafft
2004-12-21 16:48 ` Tobias Klauser [this message]
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=200412211749.02086.tklauser@access.unizh.ch \
    --to=tklauser@access.unizh.ch \
    --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.