public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: gentoo-user@devrieze.net
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] passwd and group files in new baselayout
Date: Fri, 8 Feb 2002 21:46:21 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.43.0202082142170.2186-100000@kubstu.kub.nl> (raw)
In-Reply-To: <000101c1b0db$e4e565d0$b4dc0281@student.umd.edu>

On Fri, 8 Feb 2002, Will Rogers wrote:

> Hi all,
>
> I didn't get any answer for this in the user list, so I'll try it here.
> It's a little more dev-related anyway.
>
> I just merged the new baselayout package, and I have one question:
>
> The new /etc/passwd, /etc/group, and /etc/shadow files have some
> different id numbers for different accounts, and one that I added myself
> (postdrop) is now included, but with a different id than I used.  Should
> I make an effort to change to these new ids, or it not matter?  That is,
> do ebuilds assume certain a uid or gid when installing a package?
>

To my knowledge (I'm not a gentoo developer), the packages depend on names
only. One can never know for most id's what number they have. Your
filesystem does depend on numbers though. This means it is probably the
best solution give your postdrop the same uid it had before things got
changed. If you fear problems with what's installed now, you can also run
a chown on all files that should belong to postdrop.

Good luck,

ps. Root and nobody/nogroup should keep their id's (0 and 99). Those are
standard

-- 
  ___
 /~~~\  | Paul de Vrieze
| O-O | | Student of information management and technology
|  _  | | Mail: Paul@devrieze.net
 \___/  | Homepage: http://www.devrieze.net



  reply	other threads:[~2002-02-08 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08 20:05 [gentoo-dev] passwd and group files in new baselayout Will Rogers
2002-02-08 20:46 ` gentoo-user [this message]
2002-02-17  4:32 ` Martin Schlemmer

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=Pine.LNX.4.43.0202082142170.2186-100000@kubstu.kub.nl \
    --to=gentoo-user@devrieze.net \
    --cc=gentoo-dev@gentoo.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