public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ben Calvert" <ben@stonehenge-net.com>
To: "Sean P. Kane" <spkane@genomatica.com>
Cc: livewire@gentoo.org, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Creating a Stage 3 for Custom LiveCD
Date: Fri, 13 Jun 2003 11:12:04 -0700 (PDT)	[thread overview]
Message-ID: <33451.10.0.0.91.1055527924.squirrel@www.stonehenge-net.com> (raw)
In-Reply-To: <C42D120999B1CC4C886B6BB2832F356019BF6B@hermes.genomatica.com>

Sean P. Kane said:
> I am working on creating a Multi-OS Rescue CD (i.e. not just for
> rescuing a Linux system) and am doing my first very basic test build
> with livecd-ng. I was wondering how one builds a custom stage3 tar,
> other then simply untarring it and copying your own files over.

I generally roll my own in a chrooted environment on my faster servers (3x
Dell 2650s with distcc ) and then tar up the results.  If you're doing
your own installs, you're not bound by what Daniel puts in the various
stages - mine typically have everything but the kernal compile, grub,
fstab, /etc/hosts, and /etc/hostname.  As much as I love watching things
compile, I'll never go back to compiling KDE on a standalone syste :)

OTOH, If you're building a rescue cd,  you don't actually need any stages
at all.  I regularly use the latest ISO to mount ntfs volumes and fix
issues with them.  I've never tried to mount a UFS volume, so I don't know
if this would work on a *BSD machine, but then those rarely need rescuing
anyway.

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-06-13 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-13 18:00 [gentoo-dev] Creating a Stage 3 for Custom LiveCD Sean P. Kane
2003-06-13 18:09 ` Jon Portnoy
2003-06-13 20:24   ` Sean P. Kane
2003-06-13 18:12 ` Ben Calvert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-13 18:12 Ben Calvert

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=33451.10.0.0.91.1055527924.squirrel@www.stonehenge-net.com \
    --to=ben@stonehenge-net.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=livewire@gentoo.org \
    --cc=spkane@genomatica.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