[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Chrooted Debian install from base image (was Re: Instalation question: Toshiba TECRA 8000)



On Sat, Apr 06, 2002 at 08:52:50PM -0800, Karsten M. Self wrote:
> This is a draft of a HOWTO I'm working on for doing a chrooted Debian 

thanks for taking your time to add this usefull document.

> install.  It's a method I've found useful over the years.

Yep very handy.  I started using it when I needed woody goodies and
didn't want to take the risk and do a full upgrade.

> The one component I _don't_ address here is module configuration for
> support of networking, sound, etc.  Not sure how best to deal with this.

Not sure what you're at here, but if it's just module configuration
why not hint at modconf?
 
...
> As an alternative, it's possible to bypass the installation CD using one
> of several other methods of getting a base image onto the system.

It would be nice if you could mention some of the other aproaches, like
netinstall and give a link to the iso.

Oh, and I myself are very carefull in my examples to use a telling
prompt.  In your code below you stick to `$ ' as prompt even when
one clearly has to be root for the command to work.  I would suggest
to use `# ' there and use `###' to begin a comment.  Or maybe even
better use `TRB: ' as prompt for the commands used while running
TRB, and switch to `debian: ' once debian is running (chrooted).
 

> 	Performing A chroot Debian Install From A Booted System
> 	-------------------------------------------------------
> 
> The goal is to end up with an upacked tarball of the base system on a

I was under the impression that woody didn't have such a tarball any more,
and now that woody is due to be released next week:) it might be wise to
make this a little bit more future proof.  E.g. debootstrap seems very
promissing it's merely a sh script so I guess it could work with TRB.
I merely tried it from a chrooted woody and from its father potato:

   # apt-get debootstrap
   # debootstrap --verbose --unpack-tarball /tmp/basedebs.tar woody woody2


...
> keep on rolling.  Thus it's a "zero downtime" GNU/Linux install.  Also a

nah, a near zero downtime, you have to reboot once you know:)

...
> Getting Started
> ---------------
...
> My preference is for separate partitions, in order of preference for
> creation: /, swap, /boot, /usr, /home, /tmp, /var, and /usr/local.  If

funny, I would think /boot is far less important to have separate then
/usr.  But then, I've either small disks or modern motherboards, so no
1024 cylinder limit here.  Or do you have other arguments to separate
/ and /boot?

...
> Mount two of your partitions to /mnt/debinst and /mnt/utility.  While
> you're at it, make sure a /mnt/floppy directory exists. 

Is this in accordance with FSH (or what ever the beast is named).  I
remember some discussions a while ago, but missed the final verdict.

 
> Transferring The Base Image
> ---------------------------

This can be done with debootstrap too, so you merely need to tell how
to install debootstrap on a non debian system.  And maybe were to get
basedebs.tar as debootstrap can use a local copy of that tarball too.



> Configuring The Base System
> ------------------------------
> 
> You've now got a real Debian system, though rather lean, on disk.
> Chroot into it:
> 
>     $ chroot . bin/bash

One thing I always wondered how to deal with was with preventing
daemons to start / stop in the chrooted woody, especially as this
automatically happens when you install a new (version) `daemon'
packet.  Initially debootstrap uses a trick to prevent daemons from
really being started.  Might be worth explaining the trick and how it
can be used later on.


...
>    - /etc/hostname -- your system's host name -- 2 - 63 characters.

Maybe worth mentioning that it shouldn't contain the domain part?


...
> Reboot to confirm your settings.  If your system doesn't come up, you've

If you go the debootstrap path, you need to install a kernel package first.


...
>       # In theory, the following works, though I had to kick it a few
>       # times to make it go right:
> 
>       $ apt-get dist-upgrade		# This should work.
>       $ apt-get dselect-upgrade		# This is what I ended up using.
> 
>     FIXME:  ...can someone straighten me out on this?

I'm no expert on the subject, but I thought dselect-upgrade is only usefull
when you used dselect to select packages and want apt-get to install them.

 
-- 
groetjes, carel


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: