Re: boot-floppies for stable
I've come across a funny problem: I'm unable to "mkdir chroot". It isn't
there already, so, what do I do?
I checked the man pages for chroot, and lo and behold, it's a command! I
guess you can't make a directory that is a command. Should I just d/l the
source, build, and it will create the directory?
"I don't care if you're going nowhere,
Just take good care of the world."
-- Depeche Mode
>From: Michael Schmitz <email@example.com>
>To: Russell Hires <firstname.lastname@example.org>
>Subject: Re: boot-floppies for stable
>Date: Sat, Apr 14, 2001, 12:37 PM
>> If I knew how to do boot-floppies, I would do them. Of course, I don't even
>> have anything set up for woody...If someone tells me how, I think I would
>> make this effort...
> Jonathan McDowell apparently started on boot-floppies already (the request
> to build was for the upcoming 2.2r3).
> The way we handle unstable builds without resorting to running unstable is
> setting up a build system with unstable packages in
> /usr/local/chroot/unstable, then using sbuild from the buildd system to
> run a chroot build process in there. I have a chroot system for unstable
> on our FTP site for use by the other m68k autobuilders and you could use
> that. The whole buildd stuff has been packaged by Christian Steigies
> recently (http://people.debian.org/~cts/wanna-build/), you can build it
> from source on your stable system, install, then adjust a few config files
> and use sbuild to automagically fetch sources, install packages required
> for building, build the package and remove the installed packages again
> without user intervention. If the build fails, you can fix the build
> source tree and repeat (sbuild will pick up the unpacked source to
> boot-floppies need quite some packages in a mini-archive mirror structure
> to build the base system, but I think the boot-floppies source either has
> a list of those, or a script to fetch them.