dkminor(). Use $((1 << 29)) instead of a mysterious decimal number for
$scisctl. Use dkminor() instead of repeating part of it for special cases.
Shortened some long lines.
bell type on boot. Slightly annoying when your system doesn't have a speaker.
This adds a `keybell' frob for setting it. Closes PR#2519
Submitted-By: Jonathan Mini <mini@hydrogen.nike.efn.org>
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
I've added an installation from optical disk drive facility.
This enables FreeBSD to be installed from an optical disk, which
may be formatted in "super floppy" style or sliced into MSDOS-FS
and UFS partitions.
Note: ncr.c should be reviewed by Stefan Esser <se@freebsd.org>
and cd.c by Joerg Wunsch <joerg@freebsd.org> before bringing this
into 2.2.
Submitted-By: Shunsuke Akiyama <akiyama@kme.mei.co.jp>
Fixed some style bugs for cua* and tty*.
Removed superfluous chmod for consolectl.
FIxed a tiny security bug for perfmon and changed the style for
perfmon to match the style of the non-std devices.
create the PC-CARD devices.
Note: The APM character special device is named /dev/apm and not apm0 as
was prvioiusly since only one APM device can exist in a system at a time
according to the the APM specifications.
tape_umask=017 for all tapes. This has a significant effect only
for ft and st (they were created with the wrong umask 002 and then
chmod'ed to mode 640; now they are created with mode 660).
Chmod the st control devices (mode 3) to 600. These need to be
more secure than the st i/o devices, but were less secure.
Use the default umask of 077 for joy0. 002 gave mode 664, which
is insecure.
Use umask 037 for ch*. Cosmetic.
Removed redundant chmod's.
Sorted case lists for disks.
rest of the memory group - std. Also correct the permissions so as not
to force a security hole. If /dev/*random have the permission 640 and
ownership bin.kmem, it forces applications that need random numbers
to be at least SGID. Picture the scene of a SGID PGP being able to
read /dev/kmem!
example without optios would create floppies that waste half of their
space in i-node areas. :) (Comment only)
Add a sample entry for a Sony 650 MB MOD.
Move `Individual slices' case earlier so that it can be used to handle
sliced floppies.
Remove superfluous `chmod 600's.
Fix formatting of device list.
Don't group setting of umasks with setting of units.
Remove superfluous trailing semicolons.
Submitted by: bde
rc.i386 failed messily when I used a serial console.
Editors note:
Use file redirection so that all the kbdcontrol and vidcontrol
commands act upon /dev/ttyv0 instead of stdin. Though this feature
is not documented it is the intended behavior of {vid,kbd}control
and shall be documented in the future as such.
FreeBSD), add mach-4 target to MAKEDEV; it creates various compatability
devices for Mach4.
Submitted by: (Submitter name unknown) <root@ns2.redline.ru>
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.
