From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Managing multiple systems with identical hardware
Date: Mon, 30 Sep 2013 23:19:31 -0700 [thread overview]
Message-ID: <CAN0CFw2+JVYOvAstO06EMmBO96Mt+rPzx0Ny4Q+o=+h9uCDJcw@mail.gmail.com> (raw)
In-Reply-To: <20130930195320.GA8812@methusalix.lan>
>> > Puppet seems like overkill for what I need. I think all I really need
>> > is something to manage config file differences and user accounts. At
>> > this point I'm thinking I shouldn't push packages themselves, but
>> > portage config files and then let each laptop emerge unattended based
>> > on those portage configs. I'm going to bring this to the 'salt'
>> > mailing list to see if it might be a good fit. It seems like a much
>> > lighter weight application.
>>
>> Two general points I can add:
>>
>> 1. Sharing config files turns out to be really hard. By far the easiest
>> way is to just share /etc but that is an all or nothing approach, and
>> you just need one file to be different to break it. Like /etc/hostname
>>
>> You *could* create a "share" directory inside /etc and symlink common
>> files in there, but that gets very tedious quickly.
>
> How about using something like unison? I've been using it for a while
> now to sync a specific subset of ~ between three computers.
> It allows for exclude rules for host-specific stuff.
I think what I'd be missing with unison is something to manage the
differences in those host-specific files.
- Grant
next prev parent reply other threads:[~2013-10-01 6:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 21:18 [gentoo-user] Managing multiple systems with identical hardware Grant
2013-09-25 21:42 ` Alan McKinnon
2013-09-26 9:08 ` Grant
2013-09-26 20:42 ` Alan McKinnon
2013-09-27 4:33 ` Johann Schmitz
2013-09-27 5:34 ` Alan McKinnon
2013-09-27 10:37 ` Grant
2013-09-27 19:44 ` Alan McKinnon
2013-09-27 20:30 ` [gentoo-user] " James
2013-09-29 18:36 ` Grant
2013-09-29 20:39 ` Alan McKinnon
2013-09-29 18:31 ` [gentoo-user] " Grant
2013-09-29 19:06 ` Neil Bothwick
2013-09-29 20:57 ` Alan McKinnon
2013-09-30 17:31 ` Grant
2013-09-30 19:28 ` thegeezer
2013-09-30 19:31 ` Alan McKinnon
2013-09-30 19:53 ` Frank Steinmetzger
2013-10-01 6:19 ` Grant [this message]
2013-10-01 14:04 ` Michael Orlitzky
2013-10-01 15:00 ` Neil Bothwick
2013-09-30 21:02 ` Neil Bothwick
2013-10-01 6:26 ` Grant
2013-10-01 6:07 ` Grant
2013-10-01 6:20 ` Alan McKinnon
2013-10-02 18:54 ` Grant
2013-12-12 23:54 ` Grant
2013-12-13 0:16 ` Poison BL.
2013-12-13 0:34 ` wraeth
2013-12-13 2:06 ` Grant
2013-12-13 9:12 ` Neil Bothwick
2013-12-13 1:49 ` Grant
2013-12-13 7:57 ` Alan McKinnon
2013-12-13 9:18 ` Neil Bothwick
2013-12-13 7:52 ` Alan McKinnon
2013-10-01 7:43 ` Neil Bothwick
2013-10-01 18:37 ` joost
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='CAN0CFw2+JVYOvAstO06EMmBO96Mt+rPzx0Ny4Q+o=+h9uCDJcw@mail.gmail.com' \
--to=emailgrant@gmail.com \
--cc=gentoo-user@lists.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