From: Wout Mertens <wmertens@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Working on a usb-storage hotplug script
Date: Wed, 10 Dec 2003 19:41:13 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107108549431794@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107006883203516@msgid-missing>
Yesterday at 08:24, Greg KH ponderously produced:
> On Tue, Dec 09, 2003 at 10:05:29AM +0100, Wout Mertens wrote:
> > Hi,
> >
> > I was wondering what the current state of auto-mount-inserted-devices
> > is.
> >
> > I posted my script which is run as a hotplug agent for storage some time
> > ago, someone else had one along the same lines, Mandrake uses devfsd to
> > call their configuration scripts and the fstab editor, Lindows has
> > something, Suse as well, there is the vold project which uses polling, ...
> >
> > It sometimes seems that everyone and their brother has their own
> > solution :(
>
> What's wrong with devlabel? I thougth that's what most people are
> using, as I think it solves the problems you are looking at.
>
> And I don't know anything about devfs :)
Devlabel needs to know about the device beforehand. I can't quickly copy
some pictures to my friends USB stick that way.
Devlabel tries to do something that's important for servers with loads
of drives. It is irrelevant, however, for the behaviour in the previous
paragraph. I insert the key, I copy stuff to the mountpoint, preferrably
through clicking on some icon on the desktop, done. I'll never need that
mountpoint again. It doesn't matter if it is on /dev/sda1 or
/dev/sdz6...
updfstab is another way of handling it, but then the user must remember
to mount first, and unmount afterwards. My script mounts it for the
owner of /dev/console, which means that if you plug in the key before
you're logged in, you don't get access to it.
In any case, I'm happy to see that Linux 2.6 has gotten more much robust
for hotplugging :)
Wout.
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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:[~2003-12-10 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 1:19 Working on a usb-storage hotplug script Martin
2003-11-29 12:33 ` reflex
2003-11-29 14:06 ` Oliver Neukum
2003-11-29 18:05 ` Marco d'Itri
2003-11-30 11:19 ` reflex
2003-11-30 19:38 ` Greg KH
2003-12-09 9:05 ` Wout Mertens
2003-12-09 16:09 ` Olaf Hering
2003-12-09 16:24 ` Greg KH
2003-12-10 19:29 ` Wout Mertens
2003-12-10 19:41 ` Wout Mertens [this message]
2003-12-10 19:49 ` Olaf Hering
2003-12-11 15:37 ` Wout Mertens
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=marc-linux-hotplug-107108549431794@msgid-missing \
--to=wmertens@cisco.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).