From: Mateusz Marzantowicz <mateuszm@server.pl>
To: xtekhne@gmail.com
Cc: linux-admin@vger.kernel.org
Subject: Re: [--tech--]Re: installing multuple distributions
Date: Tue, 10 Feb 2009 10:57:48 +0100 [thread overview]
Message-ID: <1234259868.6246.11.camel@ubuntu-mobile> (raw)
In-Reply-To: <gmor6p$urf$3@ger.gmane.org>
On Mon, 2009-02-09 at 09:46 +0100, Pol wrote:
> <posted & mailed>
>
> Yuri Csapo wrote:
>
> > Pol,
> >
> > Yes, it would certainly work. The important files to look at are, as you
> > said, /etc/passwd and /etc/group; but also /etc/shadow. I don't think
> > it's a good idea to make them the same because different distros will
> > have different ways of doing things and different required
> > administrative users and groups; things like lp, admin, etc. All you
> > need to do is make sure that your own user entry (and those of other
> > users of the system) has the same UID and belongs to the same primary
> > group, which should have the same GID. Also, I'd make the passwords the
> > same across the distros just to keep sane... Good luck!
>
> yes, i realise /etc/passwd and /etc/group might contain
> distribution-specific details
> thank you
... as well as other files in /etc directory. I think it'd be good idea
to have /etc unshared between your Linux distros.
Things that could possibly be problematic when sharing /etc are:
- passwd and group (as mentioned)
- boot scripts in rcN.d and init.d
- PAM configuration (if any is present, but most of Linux distros uses
it)
- other common system config (you'll need to merge all common files
which may be different in various Linux distros)
--
Mateusz Marzantowicz
next prev parent reply other threads:[~2009-02-10 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 7:55 installing multuple distributions Pol
2009-02-06 11:00 ` Adam T. Bowen
2009-02-09 8:57 ` Pol
2009-02-09 11:37 ` urgrue
2009-02-07 2:00 ` Yuri Csapo
2009-02-09 8:46 ` [--tech--]Re: " Pol
2009-02-10 9:57 ` Mateusz Marzantowicz [this message]
2009-02-11 9:51 ` Glynn Clements
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=1234259868.6246.11.camel@ubuntu-mobile \
--to=mateuszm@server.pl \
--cc=linux-admin@vger.kernel.org \
--cc=xtekhne@gmail.com \
/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).