public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fresh install and problem with net.* init.d script
Date: Tue, 23 Jul 2013 01:13:41 +0100	[thread overview]
Message-ID: <20130723011341.236a55ff@hactar.digimed.co.uk> (raw)
In-Reply-To: <0e65969e5c3c43ccae24491a194a4031@drakonix.fr>

[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]

On Mon, 22 Jul 2013 23:45:04 +0100, FredL wrote:

> I just use my current gentoo system for building a new one from
> scratch, so I only use my current system as it was only a livecd. I
> won't use my current world file or anything else coming from my current
> system (except things like hostname, hosts, or kernel config).  In fact
> I'm building a little script for deploying a very basic gentoo system 
> without typing the full list of commands listed in the installation 
> documentation. Just a hobby for lazy guy ;)
> Another reason for this fresh install is that I plan to write a full
> doc for describing the installation process for building a cluster
> hosting my own services (ftp, web, mail, etc...) in a para virtualised 
> environnement (xen) . So I don't want to have any rubish coming from
> the desktop I currently used, and want to keep things as clean as
> possible.

Sets are your friend here. I have a base set containing all the useful
things I put on all installs, including the things details in the
handbook like a cron daemon and system logger as well as the likes of
eix, conf-update, portage-utils and emacs. Then I have sets for desktop,
laptop etc, each of which inherits the base set.

so it's pretty much a case of partition the disk, unpack the stage3,
emerge @laptop (or whatever, compile the kernel, configure the bootloader
and reboot.


-- 
Neil Bothwick

Like an atheist in a grave: all dressed up and no place to go.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-07-23  0:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 20:42 [gentoo-user] Fresh install and problem with net.* init.d script FredL
2013-07-22 20:54 ` Paul Hartman
2013-07-22 21:13   ` FredL
2013-07-22 21:35     ` FredL
2013-07-22 21:44       ` Alan McKinnon
2013-07-22 22:02         ` FredL
2013-07-22 22:08           ` Alan McKinnon
2013-07-22 22:45             ` FredL
2013-07-23  0:13               ` Neil Bothwick [this message]
2013-07-23  7:43                 ` FredL
2013-07-23 11:06             ` Tanstaafl
2013-07-23 12:02               ` Bruce Hill
2013-07-23 12:20               ` Yohan Pereira
2013-07-23 14:22                 ` FredL
2013-07-24  2:17         ` [gentoo-user] " Steven J. Long
2013-07-24  9:02           ` Neil Bothwick
2013-07-24  9:39             ` Alan McKinnon
2013-07-24 17:51               ` [gentoo-user] " Steven J. Long
2013-07-24 19:37                 ` Alan McKinnon
2013-07-24 20:18                   ` [gentoo-user] " Steven J. Long
2013-07-24 21:04                     ` Alan McKinnon
2013-07-27 18:28                       ` [gentoo-user] Reinventing the wheel Steven J. Long
2013-07-24 17:32             ` [gentoo-user] Re: Re: Fresh install and problem with net.* init.d script Steven J. Long
2013-07-26 19:59       ` [gentoo-user] " Markus Kaindl

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=20130723011341.236a55ff@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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