| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
configure devfs rules in /etc/devfs.conf for ZVOLs.
Submitted by: Yarema <yds@CoolRat.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that
we can remove the file as early as possible, but shut up nextboot at this moment
if the operation is failed, because /boot is not necessarily a part of /; the
newly added second run is placed in rc.d/mountlate after all filesystems were
mounted.
Discussed at: -rc@
Suggestions from: brooks, mtm
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
|
| |
because another command (echo) is executed between the mount command
and the check.
Reported by: Sergey Baturov <sergey@toor.org.ru>
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
specific one. Instruct it to listen on all interfaces so that enabling
it in rc.conf(5) works "out of the box."
PR: conf/121406
Submited by: trasz
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
scripts at boot. This is currently disabled by default. /etc/ddb.conf
contains some potentially reasonable default scripts.
PR: conf/119995
Submitted by: Scot Hetzel <swhetzel at gmail dot com> (Earlier version)
X-MFC after: textdumps
|
|
|
|
|
|
|
|
| |
commas due to our deconstruction of the line in cf/feature/dnsbl.m4.
PR: 120038
Submitted by: mattijs vreeling
MFC after: 1 week
|
|
|
|
|
|
| |
PR: 118837
Submitted by: Matthew Seaman
MFC after: 1 week
|
|
|
|
| |
IPv6 addresses for 6 of the root name servers!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
find | sort. As a bonus, this simplifies the logic considerably. Also
remove the bogus "overruning the args to ls" comment and the corresponding
"-n 20" argument to xargs; the whole point with xargs is precisely that it
knows how large the argument list can safely get.
Note that the first run of the updated script may hypotheticall produce
false positives due to differences between find's and sort's sorting
algorithm. I haven't seen this during testing, but others might.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rapid wireless association changes in my experience), there is a race
where dhclient is in the process of exiting due to the link going down
when the link coming up causes devd to try and start a new one. This
results is the link being up, but no dhclient running.
Work around this race by checking a second time after a one second delay
before refusing to start a dhclient instance due to one already being
running.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
is enabled dummynet(4) is added to the list of required modules.
Discussed on: #freebsd-bugbusters (rwatson, trhodes)
PR: conf/79196
MFC after: 1 week
|
|
|
|
|
|
| |
Prompted by PR conf/85363
MFC after: 3 days
|
|
|
|
| |
start using the quiet prefix (i.e. quietstart, quietstop, etc...).
|
|
|
|
| |
start using the quiet prefix (i.e. quietstart, quietstop, etc...).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
out because the rc.conf(5) variable was not enabled. Display a
message that the command wasn't run and offer suggestions on
what the user can do.
Implement a quiet prefix, which will disable some diagnostics. The
fast prefix also implies quiet. During boot we use either fast or
quiet. For shutdown we already use 'faststop'. So, this informational
message should only appear during interactive use.
An additional benefit of having a quiet prefix is that we can start
putting some of our diagnostic messages behind this knob and start
"de-cluttering" the console during boot and shutdown.
|
|
|
|
|
|
|
|
|
|
| |
during boot and shutdown. I think I'll hide it behind autoboot or
maybe take brooks@ suggestion and implement a different command
prefix for booting/shutdown purposes, but in any case it needs more
thought and attention.
Noticed by: ceri
Pointyhat to: mtm
|
|
|
|
|
|
|
|
| |
silently. Display a message that the command wasn't run and make
possible suggestions for what to do.
PR: conf/118770
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
Re-implement the change so that the script once again works with
the krb5 port.
Submitted by: kensmith (slightly modified)
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Allow IP in firewall_nat_interface, just like natd_interface
- Allow additional configuration parameters passed to ipfw via
firewall_nat_flags
- Document firewall_nat_* in defaults/rc.conf
Tested by: Albert B. Wang <abwang at gmail.com>
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
included in the kernel by default. Remove reference to this option
from defaults/rc.conf and rc.conf(5).
PR: conf/119098
Submitted by: Beat Gaetzi
MFC after: 1 week
|
|
|
|
|
|
|
| |
authors list, ISBN, URLs.
PR: conf/119590
MFC after: 1 week
|
|
|
|
| |
could theoretically be allocated one day.
|
|
|
|
|
|
|
|
| |
the rejected mail reports to tally the rejects per blacklist without
providing details about individual sender hosts. The default configuration
keeps the reports in their original form.
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
32-bit binaries.
MFC after: 3 days
|
|
|
|
| |
daemons and don't already have one.
|
| |
|
|
|
|
| |
removed from the Makefile in version 1.5 (2002/09/02) but never GC'ed.
|
| |
|
| |
|
|
|
|
|
| |
with theirs, so this information doesn't need to be in the live file.
Having it in our CVS history is enough.
|
|
|
|
|
|
|
| |
directive. Users get irritated if FreeBSD Update steps on these while
upgrading to a new release.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
.ICE-unix, .font-unix, .XIM-unix) when purging files from /tmp via the
daily 100.clean-tmps job. If you are logged into an X session longer
than the timeout period (default of 3 days), then this job can delete
the X11 sockets out from under the session without this fix.
MFC after: 3 days
|
|
|
|
|
|
| |
anytime that library version is bumped.
XXX: I wonder if this breaks any 6.x binaries using Kerberos5 via GSSAPI.
|
| |
|
|
|
|
|
|
|
| |
[pt]ty[lmnoLMNO][0-9a-v].
MFC after: 3 days
Reviewed by: rwatson
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
PR: conf/116659
Approved by: sam, erwin (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
upgrading to new releases. Important parts of this code include
* automatically determining which optional components (e.g., src,
info, proflibs) are installed.
* merging changes in files which are modified locally and have
changed between the currently running and new release.
* prompting the user to rebuild all 3rd party software before
deleting old shared libraries.
Yes, this is compatible with "freebsd-update rollback" -- you can
test a new -BETA and roll back to the old release if you don't
like it.
Subject to re@ approval, this will be MFCed before 7.0-BETA3 and
6.3-RC1.
MFC after: 2 days
|
|
|
|
| |
other syntax changes. Move pf.conf from /etc to examples, too.
|
|
|
|
| |
Noted by: simon
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
This includes:
o mtree (for legal/intel_wpi)
o manpage for i386/amd64 archs
o module for i386/amd64 archs
o NOTES for i386/amd64 archs
Approved by: mlaier (comentor)
|
|
|
|
| |
Prodded by: jhb@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wpa_supplicant expects that it has exclusive access to the net80211 state so
when its starts poking in the WEP/WPA settings and the card is already
scanning it can cause net80211 to try and associate incorrectly with a
protected AP.
This is an inconvenience for firmware based cards such as iwi where it can be
sent an auth instruction with incomplete security info and cause a firmware
error.
Remove the 'ifconfig up' from network.subr since wpa_supplicant will
immediately down the interface again.
Reported by: Guy Helmer (and others)
Reviewed by: sam, brooks, avatar
MFC after: 3 days
|