public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Toby Dickenson <tdickenson@devmail.geminidataloggers.co.uk>
To: daveman@bellatlantic.net, Jeff Jeter <gsfgf@softhome.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Livecds
Date: Mon, 2 Dec 2002 09:30:58 +0000	[thread overview]
Message-ID: <200212020930.58403.tdickenson@devmail.geminidataloggers.co.uk> (raw)
In-Reply-To: <20021202023016.GA19745@bellatlantic.net>

On Monday 02 December 2002 2:30 am, daveman@bellatlantic.net wrote:

> This sounds interesting, I figure I'll give a stab at how I might begin to
> approach such a thing ;-)
>
> *  Make yourself a loopback filesystem of about 640MB in size and mount.

No need for a loopback filesystem. Just chroot into an ordinary directory.

> *  Mount /var and /tmp and /proc from regular filesystem into your new
>    filesystem and chroot.
>
> *  Do your regular gentoo install. When your done, perhaps clean out the
>    /usr/portage area? Unmount.

Or mount your /usr/portage from the outer filesystem like you describe above 
for /proc. I do the same for /usr/src too, since I dont want kernel sources 
on my livecd

* build isolinux. The origin site has a later version than in portage

* copy the initrd image from the original livecd. (no need to modify it)

* look at the isolinux config file from the original livecd. you might want to 
tweak it

* grep for CDBOOT in the original livecd /etc directory. There are a few 
baselayout files that have been tweaked from the original portage versions. 
In this bugzilla entry I suggested it would be nice to standardise this:
http://bugs.gentoo.org/show_bug.cgi?id=11330

> *  Make an el torito CD.(not entirely sure how to do this part)

My build script uses the command:

mkisofs -x "/rescuedisk/image/usr/share/doc" -x 
"/rescuedisk/image/usr/share/man" -o disk.iso -J -r -nobak -b 
isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 
-boot-info-table /rescuedisk/image

> *  Copy over filesystem image to the CD.
>
> *  I'm thinking you'll probably need a RAMDISK for temporary file storage
> and whatnot.

The original livecd initrd takes care of all that nicely.

> Sounds like it would be a fun project. If someone has already done such a
> document it would be very interesting to see. If not, it might be fun to
> write. ;-)

its on my todo list



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2002-12-02  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01 22:47 [gentoo-dev] Livecds Jeff Jeter
2002-12-02  2:30 ` daveman
2002-12-02  9:30   ` Toby Dickenson [this message]
2002-12-03  3:48     ` Jeff Jeter
2002-12-03 12:42       ` Paul de Vrieze
2002-12-03 23:18         ` Jeff Jeter
2002-12-03 23:25           ` Martin Cooper
2002-12-04  0:41             ` Jeff Jeter
2002-12-04  7:52               ` Martin Cooper
2002-12-04  8:35           ` Paul de Vrieze
2002-12-02  4:44 ` Daniel Robbins

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=200212020930.58403.tdickenson@devmail.geminidataloggers.co.uk \
    --to=tdickenson@devmail.geminidataloggers.co.uk \
    --cc=daveman@bellatlantic.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=gsfgf@softhome.net \
    --cc=tdickenson@geminidataloggers.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