linux-hotplug.vger.kernel.org archive mirror
 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: Sat, 18 Dec 2004 04:18:24 +0000	[thread overview]
Message-ID: <20041218041824.GE4948@fmp.com> (raw)
In-Reply-To: <20041217083115.GA4050@wonderland.linux.it>

Thus spake martin f krafft on Fri, Dec 17, 2004 at 06:53:58PM CST
> also sprach Lindsay Haisley <fmouse-gentoo@fmp.com> [2004.12.18.0125 +0100]:
> > IMHO, designing in accord with the KISS principle is seldom an
> > evolutionary step backwards.
> 
> I agree that no permissions.d is better than not allowing nodes
> identified by symlinks to be changed.
> 
> However, I also think that having a central place to configure
> device permissions is favourable. Without udev, I can do that in
> /dev. With udev, I will now have to scan all rules, possibly dive
> into scripts and essentially pretend I am a shell script processor
> to figure out which permissions are actually being applied.
> 
> If you come from the system administration background, I wonder how
> you see a benefit in this approach! Are you aware of what
> policy-based approaches are, what they try to solve, and why they
> are a great idea, in programming, security management, or system
> administration?

I do not come from a "systems administration background".  I am an educated
human being who makes his living from providing Internet services that
others want and need, and have had to learn what I need to know to make it
happen.  I really don't give a rip about "policy-based approaches".  What I
_can_ tell you, is that when I encounter a new technology that I need to
use, I approach it in a pretty logical fashion, and expect the
implementation and documentation for it to be free of needless redundancies.
I expect the documentation to readily available, logically presented, and to
use defined terms and referenced concepts to provide a clear and useful path
into the facility it documents.  

I respect the capabilities of the developers who have put a great deal of
their time, effort, and above all their commitment to excellence into the
design of systems such as udev, and, while I may make suggestions from time
to time, I do not in any way presume to pass judgement on their efforts.

> Why do you think Debian has /etc/default and Fedora uses
> /etc/sysconfig (to give just two very trivial examples -- I am
> sorry, I am unaware of how Gentoo does things, but I assume them to
> be similar)?

Gentoo uses similar structures - several of them.

> We are not getting rid of these because they fulfill
> a very specific purpose: centralise configurable aspects of the
> System V init process. The performance impact they produce is
> negligible given how they facilitate administration.

I see no problem with having owner, group and mode spec'd in udev rules
files. Certainly this furthers the the purpose of centralization.  The
syntax of the file is reasonably forgiving, and anyone wanting a greater
degree of order could format it to personal taste so as to make it more
readable.
 
> When I saw permissions.d, I was rather impressed by its elegance
> (very reminiscent of how Debian does many things, actually -- yes,
> I am biased ;^>). How sad to have the developers turn around and
> stick their heads in the sand for no real reason.

Like you, I was reasonably impressed with the elegance and usefulness of the
facility in /etc/udev/permissions.d, however I also see problems with it.  I
happen to agree with the position that spec'd permissions should pass thru
symlinks to the linked devices.  An admin who needs to set device
permissions should be able to do so quickly and simply without reference to
other resources to tell him whether said devices are symlinks or not.  I
also don't particularly care for design redundancy, and furthermore,
although permissions.d is useful, it's overridden by values spec'd in udev
rules files, which begins to get confusing.  Things could be simpler, and it
looks as if Greg, Kay & others are on the right track.
 
-- 
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-18  4:18 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 [this message]
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
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=20041218041824.GE4948@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).