restore but really didn't do it.
Restore message from old rc about configuring syscons whith
echo added before it to go to new line after "echo -n xtend" f.e.
and similar stuff.
changes to it based upon other outstanding bug reports and commits made
after his work.
Comments:
(a) sysconfig is still used to do all configuration. I was not going to
change that out from under you.... a user never need edit netstart
or rc* unless they're being very weird.
(b) rc.maint has been folded back into rc. It is just unworkable as
a separate chunk because of ordering bogosities
(c) netstart does what it says... it starts up enough of the network to
get up, it doesn't start every bloody daemon that might talk to a
socket... netstart ifconfig's the devices and sets up routing if
configured to do so.
(d) nfs disks are mounted immediately after netstart completes
(e) syslog is started as early as possible (right after nfs) so that error
messages can get logged to remote syslog servers properly
(f) named is started (there is an argument that says that named should be
started before syslogd because if you are the dns server for your domain,
you'd like named to resolve remote hosts in syslog.conf, but this is
a minority case and the trivial workarround is to put the syslog host
in /etc/hosts or use an /etc/resolv.conf -- why? because you want syslog
to catch named errors, which is a MUCH more important and likely occurance)
(g) NOW all of the rest of the network daemons such as the time stuff, RPC,
NIS, NFS, Kerberos and inetd are started
(h) the rest of the generic stuff is done (cron/printer/sendmail)
(i) shared libraries are set
(j) /etc/rc.i386 is run (this does FreeBSD/386 specific stuff like ibcs2,
xtend, and all of the syscons stuff
(this is actually started as /etc/rc.`uname -m`
(k) the syscons stuff has gotten a serious cleaning to make it consistent
with rc conventions
(l) rc.local has had the comments about syscons removed (they are not relevant
to this file now) and the full name of the kernel has been restored to
/etc/motd
Submitted by: pts
Fixed the MAKEDEV pattern for SCSI processor type driver so it doesn't
screw up ptys. Does anyone want to suggest a better name than "pt0" for
SCSI processor devices before 2.1?
Support sliced devices better. E.g.:
`sh MAKEDEV sd0' creates [r]sd0 and [r]sd0s[1-4] as well as [r]sd0[a-h]
(the extra devices created by default won't hurt apart from wasting inodes).
`sh MAKEDEV sd0s1[a-h]' creates [r]sd0s1[a-h] (any partition creates all).
`sh MAKEDEV sd0s5' creates [r]sd0s5.
Support unit numbers 0-31 (was 0-6).
For wd:
Remove support for creating DOSpartitions wd*[i-m]. These will get removed
if you run MAKEDEV on `all' or on wd*.
444 -> root.wheel
root -> root.wheel
uucp -> uucp.wheel (perhaps this should be .dialer, but .wheel is safer)
missing -> root.wheel
chown to root is usually bogus because mknod had to be run by root to
create the inode. Setting the group explictly is currently necessary
because MAKEDEV does nothing to ensure that its working directory has
a suitable group.
Driver authors! Please fix any bogons in MAKEDEV that involve your
drivers. The sound devices are still world writable...
for now (there are too many minors to create by default). The special
sliced disk case ssd*|svn*|swd*) can almost replace the standard disk
case sd*|vn*|wd*) now (it just creates a few more devices), but there
will have to be special cases to allow creating slices 6-31 and partitions
on slices 2-31.
Fix bogus default cases.
The group was wrong if MAKEDEV was run in a directory with group other
than wheel. This may have messed up the group in recent SNAPs
(sysinstall/obj should have group bin).
Reset the umask to 77 after running MAKEDEV.local. Some cases depend on
the 77 default. MAKEDEV.local and all cases should probably set the
umask explictly and not depend on a default. Most cases already set it.
match all the port names.
Start using shell functions to avoid duplication.
Make tty* independent of cua*. Restore support for old names (tty0 ==
ttyd0, cua0 = cuaa0...).
Restore making of lpt1 and lpt2 by default.
Keep umask 077 for making vty*. World-ioctable vtys are huge security holes
because of bugs in syscons.
Make vga if a vty is made. It may still be required for X. It got nuked
with pc*.
Start using umask consistently to avoid using chmod.
file anymore after this. My link makes it too painful to make
interactive mods, and I don't have the CVS tree here so making changes
for "previous history" have to get done on freefall, with the corresponding
degree of pain.
|Message-Id: <199412011713.JAA03374@timesink.spk.wa.us>
|To: jkh@whisker.hubbard.ie
|Subject: A little problem with MAKEDEV
|
|For a while now, MAKEDEV's been kinda neat: you create the cua* files,
|and it deletes the tty* files; you create the tty* files and it
|deletes the corresponding cua* files. K00l! :-)
[Ed Note - I think this behavior was wrong, and this fix better].
created by Amancio Hasty (specificly, this, in conjunction with his sound
driver mods for dual-mode DMA will allow VAT compiled for BSD/386 1.1 to
run under FreeBSD 2.x.)
2. Make this say it is 2.0.0 (Development).
3. Update the stty commands to say ^H for erase.
4. Update the disklabel commands to use the new 4.4 syntax.
be installed on, so they should be in /dev as well.
Removed the smoking remains of dcf*. I didn't realize that it had made it
into MAKEDEV. Gone from cdevsw long time ago, gone from /dev now.
actually have a printer connected or online:
- MAKEDEV: remove all signs of lpa
add lpctl? devices (minor # = unit + 128)
- usr.sbin/Makefile add lptcontrol
- sys/i386/isa/lpt.c implement the LP_BYPASS flag: when a unit is
opened with this flag set, the printer is
not primed, and no check is made to see that
the printer is online. This can only be used
to pass ioctls. (giving us /dev/lpctl?)
- lptcontrol.c use /dev/lpctl? (LP_BYPASS)
-f flag removed, -u flag added
- lptcontrol.8 document changes in lptcontrol
rewrite using mandoc macros
Submitted by: Geoff.
upon disk type. In far more cases than not this is the optimal setting
for any disk drive made after 1990.
This now means all installs will have the disks newfs'ed with either:
newfs -b 8192 -f 1024 -d 0 -n 1
or
newfs -n 4096 -f 512 -d 0 -n 1
depending on what the user chooses for the blocking factor.
date!!) and rename them to something more eye-catching so people will read them
again (considering the previous state of affairs, I'm actually rather glad they didn't!).
1. Add to secr and bindists to possibly save the occasional fool who
doesn't RTFM and uses the wrong command to extract this (or even someone
who's legitimately using this to extract on top of a bindist somewhere
*else*).
2. Do the right thing with any symlinks in the src tree. Right now, we're
free of the buggers, but just in case.
The kernel configs already support this, so with a boot floppy or a utility
like booteasy, the user should be able to install and boot off the second drive.
Hurrah.
The configure function now tells the user to type "man 5 resolver"
for more info on resolv.conf, but mentions that the bindist must
be fully installed before this can be done (actually a user won't
have reached this stage if he doesn't have an installed bindist ;-)
2. Added notes that tell the user a little bit about how to use syscons
since they'll be running it from the outset now and would probably like
to know how to switch terminals.
----------------------------
revision 1.13.2.1
date: 1994/05/05 03:58:27; author: rgrimes; state: Exp; lines: +15 -25
Upgrade some things that are now different in 1.1.
----------------------------
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:26; author: rgrimes; state: Exp; lines: +11 -5
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:25; author: rgrimes; state: Exp; lines: +3 -3
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.2.2.3
date: 1994/04/17 19:45:24; author: rgrimes; state: Exp; lines: +13 -2
Eliminate warning messages about /sbin/sh /sbin/init and /etc/termcap
when extracting the bin or des archives. Note this is also the
place I fixed the libc.so.1.0 problem a long time ago by adding
a --exclude libc.so.1.0 to the tar command.
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 .
