From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev problems
Date: Sun, 07 Mar 2004 13:44:07 +0000 [thread overview]
Message-ID: <1078667046.1170.14.camel@pim> (raw)
In-Reply-To: <200403071315.02925.michal@cihar.com>
On Sun, 2004-03-07 at 13:47, Michal Èihaø wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> No need to cc me, I'm subsribed.
Yes, but it's quite common.
I just reply to all and do not edit the mail header.
The list needs several hours to deliver some days,
so this isn't a option anyway.
And you receive your own mail too, right? :)
> On Sunday 07 of March 2004 13:29, Kay Sievers wrote:
> > What is this "apacer.sh" for? What's in there?
>
> See attachment, it just generates device name.
I'll take a look.
> > Most removable media devices are unable to report media changes, you
> > have to poll the device, but thats not a udev task.
>
> Okay, this problem is solvable.
>
> > So your choice is to dis-/reconnect for partition update
>
> This doesn't work, it doesn't report partiotions even if card inserted while
> connecting.
Are the partitons in /sys ?
Something like /sys/block/sda/sda1/ ?
> > or create all partitions if the main device is connected with
> > NAME{all_partitions}=.
>
> Probably best solution.
Yes, but no symlinks.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÌk
_______________________________________________
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-03-07 13:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 12:15 udev problems Michal Čihař
2004-03-07 12:29 ` Kay Sievers
2004-03-07 12:47 ` Michal Čihař
2004-03-07 13:10 ` Michal Čihař
2004-03-07 13:44 ` Kay Sievers [this message]
2004-03-07 13:49 ` Michal Čihař
2004-03-07 14:05 ` Kay Sievers
2004-03-07 14:16 ` Kay Sievers
2004-03-07 14:20 ` Michal Čihař
2004-03-07 14:28 ` Kay Sievers
2004-03-07 14:30 ` Michal Čihař
2004-03-07 14:41 ` Kay Sievers
2004-03-07 14:43 ` Michal Čihař
2004-03-07 15:11 ` Michal Čihař
2004-03-07 15:28 ` Michal Čihař
2004-03-07 15:46 ` Michal Čihař
2005-04-18 18:13 ` clemens
2005-04-18 20:49 ` Greg KH
2005-04-18 21:02 ` David Zeuthen
2005-04-18 21:12 ` Greg KH
2005-04-18 21:27 ` clemens
2005-04-18 21:36 ` Kay Sievers
2005-04-19 7:36 ` clemens
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=1078667046.1170.14.camel@pim \
--to=kay.sievers@vrfy.org \
--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).