the needed endianism of the architecture. One step towards cross-building
releases.
Not touched are newfs calls in install scripts as they run on the desired
machine and thus default correctly.
commandlines for all tar operations. (work supplied by Matt Green)
2) Update arch/*/md.c to deal with new sysinst/run.c. Special case
anything that needs to do a redirect or a pipe.
3) #if 0 some unused code in target.c. This code will need to be updated,
or special cased with do_system.
Big thank you to Matt for all his work on this.
boot. Yes, NetBSD/alpha finally gets sysinst on all media types.
The new boot makes a single ramdisk which is then divided via ustarfs
onto a two-floppy set, and a second unified image for CD's, HD's, or
tapes is also created.
though it is gzip'ed; we want the first scan through the FS to open the file.
Print out the number of bytes free on disk 2. Label disk 2 with it's volume
number and tack on a bunch of label comments...date created, md5 of disk1 of
volume set...
the userland strings(1) to the binutils version. Well, crunchgen(8) links
all the stuff together ... can you say: "GPL pollution"?
If anyone knows a good reason to have strings(1) on an install disk, I can
resurrect a BSD-licensed strings. "Send me email". (ross@netbsd.org)
old alpha boot floppy, but uses the new libsa ustar FS instead of ffs
and loads in 1 minute instead of 3. (5 minutes in 1.3.2). Future work
will make use of the extra space, and also make a dual-floppy sysinst
boot out of this or another clone dir.
run diskless without having to netboot, which, besides being difficult,
isn't always possible on a particular firmware rev.
Also, this gives the tc machines a floppy that does something, although
they will get a proper install floppy "one of these days".
in its belly. This differs from the floppy kernel in that it uses the
sysinst installation tool (and thus requires more space; the ramdisk is
3M).
This is useful for netbooting and installing or for placing on a CD-ROM.
