From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] DEVNAME on device removal
Date: Mon, 22 Nov 2004 19:55:19 +0000 [thread overview]
Message-ID: <1101153319.7195.131.camel@localhost.localdomain> (raw)
In-Reply-To: <20041122193836.GA17405@spring.luon.net>
On Mon, 2004-11-22 at 20:38 +0100, Sjoerd Simons wrote:
> Hi,
>
> I just noticed that the DEVNAME enviroment variable isn't being set anymore
Yeah, that wasn't on purpose. It just happened by moving some code where
it belongs, sorry.
> in udev 0.046 on device removal, while it was being set in 0.042. We're using
> the property tto do umount -l <devices> when a block device is removed. Afaik
> there is no other way to associate a device with it's DEVNAME on removal ?
No that's right. That information is gone that time.
> Also are there cases where doing umount -l on the removed devices is wrong?
> I guess the device is gone, so there is no sense in keeping it mounted (it's
> not like the filesystem is gonna come back in a sane state again)..
>
> Attached (trivial) patch brings back the DEVNAME variable on device removal.
I will put that in.
Thanks,
Kay
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-11-22 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 19:38 [udev] DEVNAME on device removal Sjoerd Simons
2004-11-22 19:55 ` Kay Sievers [this message]
2004-11-23 7:50 ` 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=1101153319.7195.131.camel@localhost.localdomain \
--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 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.