From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] tweak node unlink handling
Date: Fri, 02 Apr 2004 22:17:15 +0000 [thread overview]
Message-ID: <20040402221714.GB12204@kroah.com> (raw)
In-Reply-To: <20040402220452.GA17866@vrfy.org>
On Sat, Apr 03, 2004 at 12:04:52AM +0200, Kay Sievers wrote:
> Based on a patch from Olaf Hering we remove the node now only if the
> requested dev_t is different from the already existing node, so any
> run of udevstart should preserve the inode number of the node file.
>
> syslog while the right node is already there:
> creating device node '/udev/hda'
> make_node: preserve file '/udev/hda', cause it has correct dev_t
> make_node: chmod(/udev/hda, 060600)
>
> syslog for wrong file already there:
> creating device node '/udev/hda'
> make_node: already present file '/udev/hda' unlinked
> make_node: chmod(/udev/hda, 060600)
>
> syslog for directory with same name already there:
> creating device node '/udev/hda'
> make_node: unlink(/udev/hda) failed with error '21'
Nice, thanks for cleaning up the patch and getting it to apply.
greg k-h
-------------------------------------------------------
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=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
prev parent reply other threads:[~2004-04-02 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 22:04 [PATCH] tweak node unlink handling Kay Sievers
2004-04-02 22:17 ` 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=20040402221714.GB12204@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).