Re: Need an up-to-date, accurate, complete install doc

At 6:44 AM -0400 21/04/2004, Martin Reindl wrote:

>> single drive, and... installer has problems with 'large' partitions

>Yes that's right :) 400MB was still ok for me.

>> I want to have /usr, /var, and /home on sep. partitions
>> I can install onto a 256M / partition everything non-X , but can't
>> figure out how to mount the other partitions appropriately

>> 			mount device path

>> That didn't work.

>Error message? You couldn't mount the filesystems in the Mini Shell?

Now this seems to work (a result of switching off Single-user mode? don't
know - see below). However, since Mini-shell is somewhat limited, I opted
instead to use cpout and cpin to alter the fstab file on the Mac side (in
anticipation of uncommenting mount-point lines in vi later, once the other
mount points are fixed up, using fsck, then mounted and dump/restored using
what's already in / (i.e. the /usr, /var, and /home there).

>> I've tried installing just base, bsd, and etc on the
>> installer-identified / partition. I can boot to that, but the system
>> comes up read-only.

Single-user was checked, and forgotten, in the Booter. Now unchecked.

It's the little things...

>some additional work to be done. But you get faster to the first boot.

>By just making a small / and installing base, etc and the kernel...
>- You can newfs... remaining partitions... over 1GB are possible.

Now we know. Or, at least, I do.

>- "df -h" output won't be false for mkfs formatted partitions

Uhmmm.

>- moving directories like /usr to the new partition and untarring the
>  remaining packages from OpenBSD is still much faster than the Mac OS
>  Installer.

This makes sense. I noticed that installing base, bsd, and etc packages
from a large RAM disk was not appreciably faster than from the hard drive.
But where are the packages that come after these three cpin'ed to (ceteris
paribus for space)? Does it matter?



>> I've tried the recipe at http://www.openbsd.org/faq/faq10.html#DupFS

The command there appears to be syntactically incorrect:

cd /SRC; dump 0f - . | (cd /DST; restore -rf - ) doesn't work - 'extra' );
cd /SRC; dump 0f - . | (cd /DST; restore -rf -) does work.

>>  won't work unless the filesystem is rw.

Single-user mode, again.

>>"mount -o rw /"? And don't forget to uncheck the "Single user"

I did, of course, forget.

>I would recommend mv'ing /usr to /oldusr,
>mkdir'ing /usr, then mounting let's say /dev/sd0g there and then cp'ing
>everything over from /oldusr to /usr.

I've done the dump/restore thing. Feedback suggests not altering fstab to
reflect the new mount points until _after_ everything has been squared away
i.e. after having dump/restored the contents of /usr, /var/, and /home
(empty, at this point, it turns out).

>> Also, the install doc is ambiguous, possibly incorrect, about when
>> (and how often) to Make Devices from within the installer. Do you
>> really run it twice, once before installing anything (is that even
>> possible? - I seem to recall having tried that without success), then
>> again after installing some combination of the base packages?
>
>Right, the installer only builds a minimal - but workable set - of
>devices. You only get such funny things like /dev/systrace by running
>"MAKEDEV all". You can do that after the first boot.

I'll do this. I had a peak at afterboot, but don't recall having seen
reference to "makedev all" there. Later.

>> of/dev/ttyxxs. If there was such a problem, has that been corrected
>
>I am not aware of any problems with /dev/tty* in 3.4 or 3.5.
>
>The install doc is generally ok, it's not perfect

It would be nice - in fact, very helpful - if it were a bit more frank
about the single-drive and small partitions issues. And if references to
sd1 were eliminated, except perhaps for illustration of the convention for
id'ing drives, at least until sd1 is a possibility; as it is, you get the
impression that sd1 _is_ possible.

p.s. Well, everything seems find, almost.

Now booting seems to mount the partitions at the desired points, but things
get hung up on an error message:

... init: can't exec getty '/usr/libexec/getty' for port /dev/ttye0: No
such file or directory

every 30 seconds. Is this a function of the install, to this point, being
only of base, etc, and bsd packages? Or is this a function of the Build
Devices command in the Installer? What's the fix?