All of lore.kernel.org
 help / color / mirror / Atom feed
From: rich turner <rich@storix.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: group ownership in initrd
Date: Wed, 22 Jun 2005 17:33:17 +0000	[thread overview]
Message-ID: <1119461597.4573.17.camel@rich> (raw)
In-Reply-To: <1119392244.4478.11.camel@rich>

i must still be missing something.

i have now included /etc/group and /etc/passwd in my initrd and the
ownership still is not getting created properly.

here is the rule that is used for /dev/pty* devices. it is found
in /etc/udev/rules.d/50-udev.rules:
KERNEL="pty[pqrstuvwxyzabcdef][0123456789abcdef]", NAME="%k",
GROUP="tty", MODE="666", OPTIONS="ignore_scripts"

when udev starts in my initrd it creates all of the pty devices but with
the wrong group ownership (the same result if i did not put /etc/passwd
and /etc/group in the initrd):
# ls -l /dev/ptya0
crw-rw-rw- 1 0   0   2,176  /dev/ptya0

when the system boots up, i can delete /dev/ptya0, run udevstart, and it
creates it properly. i must be missing something in my initrd.

On Wed, 2005-06-22 at 01:30 +0200, Kay Sievers wrote:
> On Tue, Jun 21, 2005 at 04:17:54PM -0700, rich turner wrote:
> > On Wed, 2005-06-22 at 00:50 +0200, Kay Sievers wrote:
> > > On Tue, Jun 21, 2005 at 03:17:24PM -0700, rich turner wrote:
> > > > i am starting udev in my initrd and it is creating the devices with the
> > > > correct MODE permissions but it is not creating it with the correct
> > > > group permissions.
> > > > 
> > > > what i have in my initrd, among other things, is the entire /etc/udev
> > > > directory and the /sbin/udev and /sbin/udevstart executables. is there
> > > > something else i am missing that will create my device nodes with the
> > > > correct user and group ownership?
> > > 
> > > Do you use numerical id's? If not, make sure initrd can resolve the name
> > > to the uid/gid with prepared udev.
> 
> > are the numerical id's you refer to the group ownership id's indicated
> > in the rules file?
> > 
> > are you saying that if i want to use udev in an initrd i will need to
> > include /etc/group (and perhaps /etc/passwd) in the initrd if my
> > ownership id's are names rather than numbers in my rules files?
> 
> Well, how could udev know the numbers? The kernel does not care about
> your group names and therefore you have to avoid names or provide
> everything neccessary to resolve it in initrd.
> 
> Kay
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&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



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&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

  parent reply	other threads:[~2005-06-22 17:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 22:17 group ownership in initrd rich turner
2005-06-21 22:50 ` Kay Sievers
2005-06-21 23:17 ` rich turner
2005-06-21 23:30 ` Kay Sievers
2005-06-22 17:33 ` rich turner [this message]
2005-06-22 17:47 ` Kay Sievers

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=1119461597.4573.17.camel@rich \
    --to=rich@storix.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.