linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] DEVNAME on device removal
Date: Tue, 23 Nov 2004 07:50:13 +0000	[thread overview]
Message-ID: <20041123075013.GE23194@kroah.com> (raw)
In-Reply-To: <20041122193836.GA17405@spring.luon.net>

On Mon, Nov 22, 2004 at 08:38:36PM +0100, Sjoerd Simons wrote:
> Hi,
> 
>   I just noticed that the DEVNAME enviroment variable isn't being set anymore
>   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 ? 
> 
>   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.

Applied this to the udev tree, thanks a lot for the patch.

greg k-h


-------------------------------------------------------
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

      parent reply	other threads:[~2004-11-23  7:50 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
2004-11-23  7:50 ` Greg KH [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=20041123075013.GE23194@kroah.com \
    --to=greg@kroah.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).