From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Q: udev] chmod required?
Date: Tue, 24 Feb 2004 19:25:31 +0000 [thread overview]
Message-ID: <20040224192531.GA452@kroah.com> (raw)
In-Reply-To: <200402241951.10052.mbuesch@freenet.de>
On Tue, Feb 24, 2004 at 08:17:04PM +0100, Michael Buesch wrote:
> Hi,
>
> Why do we chmod() after mknod() in make_node() ?
> Mode is passed as arg1 to mknod(). As I understand
> the glibc documentation, this should be enough to set
> the file-mode, isn't it?
Unfortunatly no. The line in the man page to pay attention to is:
The permissions are modified by the process's umask in the
usual way: the permissions of the created node are (mode &
~umask).
That umask logic just messed with everything. By explictly setting it
with chmod() we solve the problem. See the old changelog entries for
more details on me struggling with this :)
thanks,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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-02-24 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 19:17 [Q: udev] chmod required? Michael Buesch
2004-02-24 19:25 ` 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=20040224192531.GA452@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 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.