Apply a more consistent style to the echo statements in /etc/ scripts.
* Put quotes around each line
* Single quotes for lines with no variable interpolation
* Double quotes if there is
* Capitalize each word that begins a line
* Make echo -n 'Doing foo:' ... echo '.' more of a standard
Also:
* Use rm -f on /var/run/dev.db so if it's not there (devfs) it doesn't error
* Shorten the ldconfig messages so that the default fits on one line
* Test whether /var/msgs/bounds is a link before overwriting it
* Generally futz around with whitespace
* Put quotes around each line
* Single quotes for lines with no variable interpolation
* Double quotes if there is
* Capitalize each word that begins a line
* Make echo -n 'Doing foo:' ... echo '.' more of a standard
No functionality changes
In a few days I will commit a patch which changes vn(4) to use the
disk-minilayer. This will make vn(4) fully DEVFS friendly but have
the side effect that vnconfig needs the vn%d.ctl devices to be able
to configure vn(4).
Please remake your /dev/vn entries with this revision of MAKEDEV if
you don't rung DEVFS already.
from "PCMCIA SCSI MBH1040" to "PCMCIA SCSI MBH10401" "01". They are
based on the spc driver.
This will fix the conflicts of entry with REX-5536AM, REX-9836A,
and ICM PSC-2401 ("MBH10404" ones) which are based on stg driver.
The problem was pointed out in bsd-nomads several times since PAO2 days.
-Comment out the entry for "MBH10401" ones. The spc driver is
not supported yet.
-Add more comment about cards which has broken CIS
(some cards which has tuple of "PCMCIA SCSI MBH10404" "01").
Reported by: takachan@running-dog.net, y-nakaga@nwsl.mesh.ad.jp,
yuki@dayo.ne.jp
Obtained from: discussion in bsd-nomads mailing list
for a hung `daily' run to keep a `weekly' run from happening.
Same for `monthly'. We have always run `weekly' and `monthly' reguardless
of the execution status of `daily'. Until there is some consensus we should
not change the behavior.
On Saturdays, run daily and weekly sequentially, starting at 03:01 am.
This prevents daily and weekly from overlapping, while running weekly as
early as possible (i.e. as soon as daily finishes) to give it time to
finish before monthly starts at 05:30 am.
It's probably possible to do something similar with monthly, making it
run as soon as daily (and possibly weekly, if the first of the month
is a Saturday) finishes, but this is left as an exercise for the reader.
work right when the administrator has modified their runtime environment
in a manner not anticipated by our script.
Requested by: Tom Maher <tardis@ece.cmu.edu>
for a while, but a recent email to -stable suggests it should be spelled
out as the documentation of "password_format" is sparse.
Also add a `des_users' entry.
Submitted by: Sean O'Connell <sean@stat.Duke.EDU>
over the past couple years. The most recent came to the general consensus
that this was the best time, but no one actually made the change, so I'll
don my asbestos undies and dive in.
Please note that this time was chosen with input from people in various
countries with various methods and schedules for switching to and from DST.
There is no perfect time to schedule this job that works for everyone, but
this time both A) Works for more people, and B) Causes problems for fewer
people. And, ultimately, you can always change it if you need to.
ENABLE_SUID_SSH being defined reenable it for those that want it.
This follows discussion favoring the change from September. It
is not usually necessary to be setuid root, possibly less safe,
and less convenient (cannot use $HOSTALIASES, for example).
Submitted by: jedgar
overwriting $PATH, and find mknod $PATH instead of hardcoding /sbin so
that the copy of MAKEDEV on the fixit floppy is usable, since mknod and
expr live in /mnt2/stand when the fixit floppy is running.
Get rid of the sed invokation in release/Makefile that attempts to
delete the PATH setting stuff from MAKEDEV on the fixit floppy. This
hasn't worked since a long ago change to MAKEDEV caused the sed
expression to no longer match.
PR: misc/21241
a) the configured default printer entry might turn out to become a security hole
Although lpd isn't enabled by default in FreeBSD 4 and later versions
bad things might happen because of a simple copy and paste failure:
- fill up root-fs, if /dev/lpt0 doesn't exist
- fill up the spool dir (either root-fs or var-fs) if machine hadn't been
designed as print server
Therefore best decision: if people want printing, then configure both
1. /etc/rc.conf
2. /etc/printcap
the default entry wouldn't have served well all tastes and needs anyway...
design of most of our config files is, to have commented out suggestions
if a service is not active.
b) [Garance]
fix old and wrong documentation:
input filters are possible even if you print to a remote printer
this makes FreeBSDs implementation of lpd currently the best without
having to switch to port monster LPRng ...
c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number
I'm only referring to the printing section, otherwise this would have to be fixed several
times, if the chapters should be reordered again ...
d) typo: chose -> choose
Submitted by: me and some suggestions by Garance
Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
cosmetic changes
use /etc/pccard_ether for Xircom CreditCard Netwave
and 3Com Corporation" "3C562" (BUT NOT SUPPORTED).
fix `card line' of RATOC REX-5572 (as SCSI only)
use `config auto' for RATOC REX-5536AM, REX-9836A,
ICM PSC-2401 SCSI
- rtsol should be work for only one interface
- new variable ipv6_defaultrouter is added
- option name of rtadvd in comment are corrected
- ipv6_firewall_enable, ipv6_firewall_type, ipv6_firewall_script,
ipv6_firewall_logging are added to introduce rc.firewall6.
IPv6 firewall rule is just starting point and should be brushed up.
This commit includes PR18621, PR21694, PR22051.
PR: conf/18621, conf/21694, conf/22051
Reviewed by: asmodai
used in lower layer (scsi_low.c).
The flag of ncv for KME KXLC004 was chaged from 0x1 to 0x100.
The flag of nsp for PIO mode was chaged from 0x1 to 0x100.
I wasn't dropping the interface correctly, but not noticing because
the interface was going away when the card was ejected.
Submitted by: Motomichi Matsuzaki <mzaki@e-mail.ne.jp>
This confilcted with the entry of non PIO mode.
If you want to use them in PIO mode comment out entry of the non PIO mode
and uncommnet the PIO mode entry.
and stg drivers. Also all config indexes for these cards are changed
to auto.
Note, still if you would like to use cards which has a comment;
# (Do not put this entry under Bustoaster)
you need some quick hack. Uncomment the entry above.
Reviewed by: sanpei@FreeBSD.org
bind distribution, but until now was not being built as a separate
entity. For documentation, see these man pages:
assertions(3), eventlib(3), heap(3), logging(3), memcluster(3), tree(3).
Reviewed by: jdp
brought them to BSDcon and gratiously allowed me to test each one with
the wireless setup here. In addition, support another CF card which
YAMAMOTO-san also brought.
Also add a Lexar CF card which didn't work with auto on many laptops.
the 'ifconfig ifN delete' into pccard_ether under the 'stop'
function.
In addition start dhclient with a pid file based on the interface
name, e.g. /var/run/dhclient.ep0.pid, and kill the correct dhclient
(or dhcpc) process when the card is removed.
convinced myself that it's better then what we have, but still
not perfect.
/etc/rc : Attempt to seed /dev/random with multiple backoffs.
/etc/rc.shutdown : Attempt to write the entropy_file.
In debugging the above changes, I've run into some
inconsistancies... rc.shutdown is run via 'init 6', but
does not appear to be run via '/sbin/reboot'. Thus, this
set of changes improves life depending on the mechanism
used to shut the system down.
Submitted by: Doug Barton <DougB@gorean.org>
Approved by: markm
