Ask whether the user wants to delete the fetched files (ftp and floppy) after
install. Delete after sucessful install of each file.
Kill bufferred tty input in a couple of places when typeahead will be wrong.
Code added to run.c to do a 'cd' in the child, unused (so far).
for the location of the source of the sets.
Put the menu in the place on the screen that used to contian a display
of what was selected.
Now these screen work the same way as the disk partitioning ones.
Leaves more screen real-estate for more questions.
asks you where to load stuff from.
Initialise stuff so that 'install default set of sets' works.
Fix install loop, removing infinite loop if/when first kernel not selected.
of the sets after an error.
A side effect is that it now does fetch-install-fetch-install..., not
fetch-...-fetch-install-...install.
The set selection code now uses a byte per set (not a bit-pattern) removing
the restriction of 32 sets, and allowing a per set status display (TBC).
Also TBC is deleting sets from /usr/INSTALL.
However I believe it works...
systems where the bios doesn't support LBA reads.
Due to faked geometries the last few (over 30000!) sectors may not be reported
as being readable, but we expect them to be in swap. So we don't force a
root+usr install in that case.
selection (eg selecting the X sets).
libcurses got changed earlier in the year so that the erase (and refresh)
of the message window caused all the unchanged spaces to be redrawn
overwriting most of the main set selection window.
non-reentrant version here in order to avoid linker conflicts when
the rest of this file is attempted linked together with libc's
getgrent.o.
Reviewed by christos.
Since all the x_<prog> get build into crunched binaries (which does a
reachover build these days) I suspect this is entirely unnecessary.
But having deleted x_dmesg we must ensure it doesn't go there.
It is worth remembering that trailing spaces are significant in the message
files - they cause a line break if the text is auto-filled to the RH margin.
(This is often the case when the text is a format string.)
Note: nothing (yet) checks the number (or type) of the format effectors in
the message strings. I found and fixed one big error, but others will
cause core dumps.
