On Mon, 4 Oct 1999, Reinoud Zandijk wrote:

# Hi Greywolf,
# 
# On Sat, 2 Oct 1999, Greywolf wrote:
# 
# > I'm attempting to build a boot floopy using the INSTALL kernel as
# > a template, and I have a couple of questions:
# > 
# > 1.  Why in the *world* is this kernel so damn big?  2.7M vs 1.6M...
# 
# Well, because it has a installation memorydisk image in it ?? A complete
# filingsystem with /bin, /sbin/, /etc, /var etc. + installation program...

Oh, it hauls everything in automagically?  Wow!  I didn't know *THAT*!
And here I am trying to crunchgen everything.

# > 2.  How do I get a root filesystem in there?
# 
# It's allready in the installation kernel :-). It's different to Linux in
# this way. I find it more convenient this way!

D'oh!

# > 3.  What else needs to be done?  I assume this is a SSTO floppy,
# > 	more or less, vs. the DSTO set we used to use (am I wrong?).
# 
# ??? what is a SSTO/DSTO ?? When you have the boot-floppies, you can
# install the stuff with `sysinst' (starts up automatically).

SSTO == "Single Stage To Orbit", DSTO == "Double Stage To Orbit".
An SSTO disk can get you from boot to installation in one go; the "old"
method was to have the boot/kernel on one floopy, after which the
first floppy was puked out and the second requested.

# > 4.  This should probably be question #2:  Is there a document on this
# > 	anywhere?  (I must be blind -- I can't seem to find one).
# 
# Err.. try the install notes on the web-page. You can find it in the sparc
# port page..

I wasn't looking for INSTALL docs as much as how to actually generate
an INSTALL floppy (more for dizasta recovery than anything).

# Cheers,
# 
# Reinoud

THANK you for the information!  It's not the mechanics which were
confusing me as much as that we have realigned the concept of an
install floopy.

				--*greywolf;
--
"Do not meddle in the affairs of wizards,
 for you are crunchy and taste good with ketchup."  --unknown;