pair of crunched binaries that are not built by this, but other than
that it is back to an automated procedure. So many changes it is
hard to describe.
Now minor looks like UU DDDDDD, UU - unit, DDDDDD - density.
If density == 0, CMOS-detect format assumed.
For old users/pgms use fake partitions now, i.e.
ln fd0 fd0[a-h]
No new floppy names added (expect fd? and rfd?),
because don't have agreement yet, so make devices
only for CMOS-detected formats.
E-mail: <sir@kiae.su>, <vak@zebub.msk.su>
added new /dev/wt entries for wt.c version 1.3
8) Some controllers support only 1024 block length.
Setting WT_BSIZE bit in device minor number turns on this mode.
Minor number structure:
0bfffuuu
Fields:
uuu - Unit number. It's possible to install
up to three tape controllers on the same machine,
using DRQs 1..3. Hence, unit number can lie
in range 0..2.
fff - Tape format number:
0 - /dev/rwt0 - default density (auto select)
1 - /dev/rwt0a - QIC 11 (obsolete)
2 - /dev/rwt0b - QIC 24 (60 megabytes)
3 - /dev/rwt0c - QIC 120 (120 megabytes)
4 - /dev/rwt0d - QIC 150 (150 megabytes)
5 - /dev/rwt0e - QIC 300 (300 megabytes?)
6 - /dev/rwt0f - QIC 600 (600 megabytes?)
b - Long block size flag. With this bit set,
the driver will perform all i/o operations
with the controller using 1024-byte
blocks, instead of 512 ones.
Some controllers need it (CMS for example).
If you Wangtek controller does not stream well,
you can try to use /dev/rWt0 device instead
of /dev/rwt0 (uncomment needed lines in /dev/MAKEDEV
to create it).
Block interface (writing blocks less than 2048 bytes) is not functioning
pwoperly. Use raw interface instead.
Thanks to all who helped to test it on the following hardware:
Controller Drive Volume Interface Thanks to
---------------------------------------------------------------------------
Archive SC-499 Archive 2150L 150 Meg QIC-02 KIAE
CMS? ? 150 Meg QIC-02 KIAE
Everex EV 831/833 ? ? QIC-36 Joergen Haegg
Wangtek ASSY Wangtek 60 Meg QIC-02 Ken Whedbee
Tecmar QT150i? Wangtek 5150EQ ? QIC-02? Marko Teiste
? Wangtek 5099EK 60 Meg QIC-36 Robert Shien
Archive SC400S ? 60 Meg ? Warren Toomey
Clean up some stuff so that it reads a little better (some one please
review this for me!)
Adaptec controllers are 154x and 174x series. Add Buslogic 545S.
the RELEASE NOTES.
Adaptec controllers are now 154x and 174x series, no more reference
to specific models. Revamp the CSI hard disk controller section in
general to be more user readable.
Add the fact that the Mitsumi CDROM controller and drive are now
supported.
Add a note that the Intel 82501 serial chip is NOT supported.
Floppy controller is fd0, not fdc0, same for wd disk controller.
files from a MS-DOS partition.
Minor cleanup:
fixed spelling error in inst1.install
capitalized sentences in kc.profile
reworded initial load_fd options
partition of the boot disk. So we have yet another medium via
which to load the FreeBSD distribution files. load_fd() has
options for listing and (if reading from the C: drive) changing
directories.
load_fd's notation assumes that the first Primary partition on
disk is the DOS drive C: (since this and only this one is mounted
by install). Otherwise, the notation may be a bit confusing.
We'll know the assumption is bad if people complain about
not finding files on their "C:" drive...
Added a device file existence check to kc.profile.
first) Primary (un-Extended) DOS partition, providing /dev/xx0h
is available. It is mounted on /dos by default. The /etc/fstab
entry omits the dump and fsck fields, i.e.:
/dev/xx0h /dos pcfs rw
The Secondary DOS partition is not used (System ID 0xF2), because I don't
know what that is.
2) Fixed default sizes so that if someone attempts to install BSD on a 24 Mb
partition by accepting defaults, they don't end up with a 1 Mb /usr
partition (up to USRMIN Mb's). In this case, all space is split between
swap and root.
TODO:
1) Extend load_fd() to support loading distribution files directly from
the DOS partition of the hard disk.
2) Provide translated parameters to the install program (maybe
add an option to fdisk). Currently, the true geometry is used as
default, which is inappropriate for coexistence with DOS.
3) Support installing on multiple or secondary disks.
>Date: Thu, 16 Sep 1993 23:35:48 -0700 (PDT)
There is a typo in disktab in the NetBSD-0.9 distribution. This may be
already fixed in NetBSD-current, but it's not in any of the source that I've
sup'ed.
line 9 reads:
# sc #sectors/cylinder, nc*nt default
should read:
# sc #sectors/cylinder, ns*nt default
Before starting, it is important to know your hard disk's geometry
(i.e., number of cylinders, heads and sectors/track). If installing
FreeBSD on the same disk as another operating system, then the
two systems should use the same geometry. In particular, FreeBSD's
default geometry is inappropriate for MS-DOS. So in this case, the
DOS geometry should be used instead.
[This seems to be true for SCSI disks. What about IDE? With the new
boot blocks, can we ignore the disks true geometry??]
offsets and sizes in units of cylinders. This will help
those who want to install FreeBSD between two existing
partitions.
Faked notes on installing via Kermit
any way I can. Converted all echo "" to be just echo
Removed sync call that seems to hang due to fd/wd driver interaction..
Now rm /.profile before the cpio floppy is copied in, this should fix
a bugger I was having with an open shell script that gets over written.
Subject: Install.notes for FreeBSD-1.0-G
Here is the hacked install notes file for FreeBSD-1.0-GAMMA.
Please get someone to check the few points marked <<please check>>.
From: rgrimes
Checked the <<please check>>, and cleaned up some details.
and miscellaneous programs which get installed into /usr/distbin.
Install now recognizes existing DOS partitions and attempts to install
after them. Theoretically, it also remaps badblocks.
N.B.: The fourth install floppy must have a clean DOS FAT.
Building the new distribution floppies is untested
TODO: Build a disktab entry for existing DOS partitions (except extended
partitions). This would allow loading and/or extracting the distribution
files directly from the DOS hard disk partition.
The following additional changes are needed for the new install disks:
1) Remove from filesystem disk's /filelist: bin/cat, dev/MAKEDEV.local.
2) Remove from the filesystem disk: /bin/cat, /COPYRIGHT and /dev/MAKEDEV.local.
3) Add to the filesystem disk: /sbin/fdisk, /dev/fd1a and /dev/rfd1a.
4) Build a fourth DOS disk containing at least: os-bs, rz/sz
Outstanding problems:
1) If there are >1024 cylinders, then FreeBSD cannot boot unless installed
at cylinder 0 (and since neither can DOS evidently, the two can't share
a disk in this case).
2) If FreeBSD is installed at cylinder 0, subsequent installs tend to fail.
3) If a DOS partition exists, disklabel doesn't seem to update the disk
geometry in the FreeBSD disklabel correctly (so reinstalling FreeBSD with
a new geometry requires installing it at cylinder 0). Rod suggested
invoking disklabel on the raw c-partition. This makes sense, but it
doesn't seem to work (newfs, for instance, can't find the new label).
other tools really want.
Targets sio*) and com*) now create entry named ttyxx, default setup with
a sh MAKEDEV all is to use the sio major numbers, com is all but depreicated
now.
after the cpio floppy has been installed. This fixes the corrupt disk
problem during the install. Still need to add some echo's about expecting
disk corruption at this point in time.
Upgraded release statement to say 1.0 GAMMA. Added a dummy read before
the instuctions so the user does not get confused by the rapid output
and thinks something scrolled off the screen.
extract can be over writen. This is done by coping them to /tmp
before the extract begins, running them from /tmp, then removing them
after the extract has completed.
Removed all section about setting up sendmail.cf, since this was for the
old sendmail stuff and should not be required by the new sendmail.cf file
that is shipped with the system.
file left by inst1.install.
Fixed cpio command so that it works with the new cpio that does not
ignore extra options.
Added echo's about building /dev files so the user knows it is doing something.
has been asked once. Disabled the ability to have different blocking
factors on different partitions since this is known to trash the vm system.
Removed many extranious echo's of the users answers. This was probably put
in for debugging and never removed. It was quite confusing to my test users.
Added autoscan of disk for bad blocks for bad144 type disks using the new
bad144 -s option.
Renabled the asking for verbose installation. Why was this disabled??
Added creation of etc/disktab.install on the hard disk that is a copy
of the disktab used to create the disk with.
Added a mount -at ufs to the .profile so that all the diskpartitions get
mounted on first boot from hard disk, this is so commands that may have been
loaded into a seperate usr partition can be found.
left intact.
Simplified variables for drivename, drivetype, and sect_fwd.
Added rotdelay to newfs commands (defaults to newfs default except
for scsi disks where it defaults to 0).
Made the disk geometry questions more like what PC users are use to
reading (cylinders/heads/sectors).
Added minswap requirement of 8MB, recomendation of 2 x physical memory.
Added messages about what the blocking factor does.
Added message for mount point to NOT include the leading /
How to change disklabel to /sbin/disklabel due to bug in our /bin/sh,
I thought this has been fixed, but it has not!
Changed to use cpio instead of tar, since tar seems so brain dead.
Removed kernfs reference from /etc/fstab creation since FreeBSD does not
have the kernfs. Made /etc/fstab tabbed so it looks pretty :-).
Added default of floppy drive 0 after we boot from hard disk.
Fixed path in inst1.profile, removed /usr/local/bin, /usr/contrib/bin and .
