From: Gioele Barabucci <ml@gioelebarabucci.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] multple rules files support/symlink rules support
Date: Tue, 03 Feb 2004 11:25:09 +0000 [thread overview]
Message-ID: <200402031225.10292.ml@gioelebarabucci.com> (raw)
In-Reply-To: <200401172313.00189.arvidjaar@mail.ru>
On Tuesday 03 February 2004 02:04, Greg KH wrote:
> On Thu, Jan 22, 2004 at 06:44:53PM +0100, Svetoslav Slavtchev wrote:
> But the "owner" is the "system", right? They are really the same
> person. I think it looks like a neat hack to be able to add symlinks,
> but I can't see a real use for it in the world.
Maybe user actions should be limited to ~/Devices, or something similar...
> Take a look at /etc/fstab, or any of the other system wide config files
> in /etc. They don't provide a place that a user can add more items in
> another file, do they? All that is needed is to modify the original
> file to add your new items.
But this is not a virtue of the actual way-of-doing-things!!! This is one of
the most unfriendly issues that you have to face when running a Linux distro
or a Unix system.
These global files are never updated enought to support the "latest cheap
camera" I bougth. So I need to add items to these files... but how?
1) su -c "vim /etc/somefile" -- you need to know root password
2) sudo vim /etc/somefile -- This opens security holes like shell excaping
3) vim ~/.my_devices -- Just parse it in a safe way and use a dir under $HOME,
no security probs at all
And solutions 1 and 2 permits to a simple user to screw up the whole system in
a second :(
At my uni labs we run only linux boxes but we are not allowed to attach
usb-keys, card-readers and other peripherals for this very problem (try to
update 100+ boxes with different a configuration for every student...). It
would be nice to be able to do so in the future.
--
Gioele Barabucci
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
next prev parent reply other threads:[~2004-02-03 11:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 20:13 [PATCH] multple rules files support/symlink rules support Andrey Borzenkov
2004-01-20 17:09 ` Andrey Borzenkov
2004-01-20 17:57 ` Svetoslav Slavtchev
2004-01-20 18:45 ` Andrey Borzenkov
2004-01-20 23:10 ` Svetoslav Slavtchev
2004-01-21 23:51 ` Greg KH
2004-01-22 17:44 ` Svetoslav Slavtchev
2004-01-26 17:31 ` Andrey Borzenkov
2004-01-26 23:42 ` Kay Sievers
2004-01-27 9:54 ` "Andrey Borzenkov"
2004-01-27 11:43 ` Marco d'Itri
2004-02-03 1:04 ` Greg KH
2004-02-03 11:25 ` Gioele Barabucci [this message]
2004-02-16 22:34 ` Greg KH
2004-02-17 7:29 ` "Andrey Borzenkov"
2004-02-17 17:29 ` 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=200402031225.10292.ml@gioelebarabucci.com \
--to=ml@gioelebarabucci.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).