From: Stefan Schweizer <sschweizer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: ide-devfs.sh and Gentoo [u]
Date: Mon, 13 Dec 2004 21:26:49 +0000 [thread overview]
Message-ID: <e796392204121313267fafc394@mail.gmail.com> (raw)
In-Reply-To: <1102970141.11272.11.camel@nosferatu.lan>
On Mon, 13 Dec 2004 23:12:25 +0200, Martin Schlemmer [c]
<azarah@nosferatu.za.org> wrote:
> That gives the same as the GROUP= currently does (which in my mind sorda
> give that that bug is already fixed ....)
> We (gentoo) wants GROUPÍrw, which means that either:
> 1) Call cdsymlinks.sh in a rule like mentioned bug
> 2) write a different script to return cdrw if it is a
> cdrw/dvdrw/whatever. I did not however want to do this, as it would
> mean maintaining the same code in two places.
or if that bug would be solved in the proper way we could add a proper
rule like:
cdrw:root:cdrw:0660
That would effectively avoid calling cdsymlinks.sh twice and maybe
there is not only this cdrw issue, but also others, then with the
symlink-following-patch we could also easier change their permissions
without the need for userspace helpers or extra rules.
Stefan
-------------------------------------------------------
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
prev parent reply other threads:[~2004-12-13 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 20:35 ide-devfs.sh and Gentoo [u] Martin Schlemmer [c]
2004-12-13 20:54 ` Stefan Schweizer
2004-12-13 21:12 ` Martin Schlemmer [c]
2004-12-13 21:26 ` Stefan Schweizer [this message]
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=e796392204121313267fafc394@mail.gmail.com \
--to=sschweizer@gmail.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.