On Thu, Dec 21, 2000 at 02:16:11PM -0800, Joey Hess wrote:
> This demo system is a bit bigger than the previous ones, because it is a
> self-contained chrooted system!
> http://people.debian.org/~joeyh/debian-installer/demo3.tar.gz
Okay, this doesn't work as well as it might, but it does seem to work
okay, so...
http://people.debian.org/~ajt/base-deb-20001228.tar.gz
If you take that and unpack it under the demo system somewhere, then
you should be able to:
cd demo/base-deb-20001228
./get_debs.sh
(wait while around 20MB of stuff is downloaded with wget)
cd ..
sudo chroot . /bin/sh
cd base-deb-20001228
./create_chroot.sh
(wait while your base system is built)
chroot chroot /bin/bash
(play with your newly created, chrooted, Debian system, with apt, bash
and all your favourite tools available)
The good points:
* mostly works fine in the limited udeb environment
* get_debs.sh just downloads the sid/binary-i386/Packages.gz from
ftp.debian.org, and gets the latest versions of the .debs it thinks
are appropriate for the base system
* you end up having downloaded the latest versions of a bunch of .debs
and your /var/cache/apt/archives directory is already populated
with 'em
* your base configuration is all done with debconf, reasonably
magically (although probably not in a manner that integrates
nicely with the main-menu debconf already running...)
The caveats:
* it builds the chroot in ./chroot instead of /target or somewhere.
* get_debs.sh doesn't seem to work properly with busybox wget, or
busybox wget doesn't support proxies or something. It *should*
work, but it just doesn't seem to
* it assumes i386; some changes will be needed to make it work
with other archen
* it uses a faux overrides file to work out what should be in base
and what's in essential. hopefully the real overrides file can
be fixed to do something equivalent, and it can just look at the
Packages file in future
* debconf probably needs to be considered essential, if important
packages are going to pre-depend on it; and debconf probably
shouldn't depend on apt, since apt isn't essential
* debconf shouldn't have to depend on perl-5.6...
At any rate, though, it should work okay as a proof of concept.
Note that a lot of the complexity from b-f's disappears if you're
allowed to interact with the end user while you're dpkg -i'ing the
base packages...
Oh, another caveat, I set it up temporarily to fallback to auric if the
connection to ftp.d.o failed (in get_debs.sh) since ftp.d.o seems not
to have mirrored properly today... You probably want to get rid of that
fallback before using it :)
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``Thanks to all avid pokers out there''
-- linux.conf.au, 17-20 January 2001
Attachment:
pgpL3qms45Rxe.pgp
Description: PGP signature