On Wed, Apr 11, 2001 at 10:53:33AM -0400, Adam Di Carlo wrote:
> Anyhow, this does highlight that we need to cope with errors and
> problems in debootstrap a *lot* more gracefully. I don't know if
> that has well defined exit codes (archive not found, out of memory,
> out of disk, etc). I hope so, because we can't very well do an
> interface without that.
Yes, this needs fixing. How should boot-floppies and debootstrap interact?
Possible interactions are:
* failures/success (duh)
* progress -- how much has downloaded (x%), what's happening
(I: installing essential packages), etc
* interactivity -- "please insert the 5th base-system floppy"
I'm happy to do just about anything on the debootstrap end for this;
what's convenient for boot-floppies? Calling a program, displaying the
slang stuff "myself", using a named pipe, using stdio?
Cheers,
aj
--
Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``_Any_ increase in interface difficulty, in exchange for a benefit you
do not understand, cannot perceive, or don't care about, is too much.''
-- John S. Novak, III (The Humblest Man on the Net)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
