| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
header is now in two parts: bsdxml.h and bsdxml_external.h, representing
the expat.h and expat_external.h headers. Updated the info on the man
page as well. Also, fixed a type-error in a printf in
sbin/ifconfig/regdomain.c that would cause a compiler warning.
Approved by: sam, phk
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
alowing the DDB output capture buffer to be easily extracted from
user space. Both of these commands include -M/-N arguments, allowing
them to be used with kernel crash dumps (or /dev/mem).
This makes it easier to use DDB scripting and output capture with
minidumps or full dumps rather than with text dumps, allowing DDB
output (scripted or otherwise) to be easily extracted from a crash
dump.
MFC after: 1 week
Discussed with: brooks, jhb
|
|
|
|
|
|
|
|
|
|
|
| |
Note this includes changes to all drivers and moves some device firmware
loading to use firmware(9) and a separate module (e.g. ral). Also there
no longer are separate wlan_scan* modules; this functionality is now
bundled into the wlan module.
Supported by: Hobnob and Marvell
Reviewed by: many
Obtained from: Atheros (some bits)
|
|
|
|
|
|
|
|
| |
directly rather than bogusly sending it out as a link layer broadcast
(which fails to be received on some networks).
PR: bin/96018
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
files containing directory and ownership data. If /tmp fills, the
console is blasted with zillions of "file system full" errors, and
restore continues on, even though directory and/or ownership data
has been lost. This is particularly likely to happen when running
from the live CD, which has little /tmp space.
PR: bin/93603, also probably bin/107213
Fix from: Ken Lalonde
|
|
|
|
|
| |
is supported for the MBR, GPT and PC98 schemes, where GPT
installs boot code into the PMBR.
|
|
|
|
|
|
| |
year to 2008.
Noticed by: ceri
|
|
|
|
|
|
| |
PR: docs/122702
Submitted by: Yoshihiro Ota <ota@j.email.ne.jp>
MFC After: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
catastrophic recovery. Currently, this mode only validates whether a
cylindergroup has good signature data, and prompts the user to decide
whether to clear it as a whole.
This mode is useful when there is data damage on a disk and you are
working on copy of the original disk, as fsck_ffs(8) tends to abnormally
exit in such case, as a last resort to recover data from the disk.
|
|
|
|
|
|
| |
PR: bin/122403
Submitted by: az
MFC after: 3 days
|
|
|
|
|
|
| |
MFC after: 3 days
PR: bin/119976
Submitted by: Cian Hughes Ci of nhugh.es
|
|
|
|
| |
- Revise the manpage.
|
|
|
|
|
|
| |
doing an update mount on a read-only file system.
Requested by: yar
|
|
|
|
| |
Reviewed by: security-team
|
|
|
|
|
|
|
|
|
|
|
| |
o mark cmds/parameters to indicate they are potential arguments to a clone
operation (e.g. vlantag)
o when handling a create/clone operation do the callback on seeing the first
non-clone cmd line argument so the new device is created and can be used;
and re-setup operating state to reflect the newly created device
Reviewed by: Eugene Grosbein
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
interface is one with the default route (or there isn't one). Use it to
decide if we should adjust the default route and /etc/resolv.conf.
Fix the delete of the default route. The if statement was totally bogus
and the delete only worked due to a typo. [1]
Reported by: Jordan Coleman <jordan at JordanColeman dot com> [1]
MFC after: 1 week
|
|
|
|
| |
build libkse. This should fix WITHOUT_LIBTHR builds as a side effect.
|
|
|
|
|
|
| |
The is comment is left over from the old disklabel command.
Reviewed by: phk
|
|
|
|
|
|
|
|
|
|
| |
lease: track the current bssid and if it changes (as reported in an
assoc/reassoc) event only then kick the state machine. This gives us
immediate response when roaming but otherwise causes us to fallback on
the normal state machine.
Reviewed by: brooks, jhb
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
'get'. Since rtmsg() always gets called and returns 0 on success and -1
on failure, it's possible to exit with a suitable exit code by calling
exit(ret != 0) instead, as is done at the end of newroute().
PR: bin/112303
Submitted by: bruce@cran.org.uk
MFC after: 1 week
|
|
|
|
| |
C++ lets me get away with it.
|
|
|
|
|
|
|
|
|
|
| |
replace this with vinum.4, but that's the kernel interface manual, which
is not appropriate in my understanding. I think that gvinum is a suitable
replacement for this.
PR: docs/121938
Submitted by: "Federico" <federicogalvezdurand at yahoo dot com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for a configurable number of seconds, spin the disk down. Spin it back
up on the next request.
Notice that the timeout is only armed by a request, so to spin down a
disk you may have to do:
atacontrol spindown ad10 5
dd if=/dev/ad10 of=/dev/null count=1
To disable spindown, set timeout to zero:
atacontrol spindown ad10 0
In order to debug any trouble caused, this code is somewhat noisy on the
console.
Enabling spindown on a disk containing / or /var/log/messages is not
going to do anything sensible.
Spinning a disk up and down all the time will wear it out, use sensibly.
Approved by: sos
|
| |
|
|
|
|
|
|
|
|
|
| |
after labeling the provider more obvious. (1)
- Correct nomenclature usage
PR: 121487 (1)
Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
| |
file system may be passed using -o.
Approved by: remko, rodrigc
|
|
|
|
|
|
|
|
| |
lines down to '-o below'.
Approved by: remko
Noticed by: rodrigc
Pointyhat by: me
|
|
|
|
|
|
| |
mount_unionfs(8).
Approved by: remko
|
|
|
|
|
|
| |
PR: 121486
Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com>
MFC after: 3 days
|
|
|
|
|
| |
Ok'ed by: marcel
No objection: -current@
|
| |
|
|
|
|
| |
feature in ipfw(8).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
doing the MNT_RELOAD, pass in "ro" and "update"
string mount options to nmount() instead of MNT_RDONLY and MNT_UPDATE flags.
Due to the complexity of the mount parsing code especially
with respect to the root file system, passing in MNT_RDONLY and MNT_UPDATE
flags would do weird things and would cause fsck to convert the root
file system from a read-only mount to read-write.
To test:
- boot into single user mode
- show mounted file systems with: mount
- root file system should be mounted read-only
- fsck /
- show mounted file systems with: mount
- root file system should still be mounted read-only
PR: 120319
MFC after: 1 month
Reported by: yar
|
|
|
|
| |
do that internally inside nmount() in revision 1.267 of vfs_mount.c.
|
|
|
|
|
| |
Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the limit in bytes) hard coded into both the kernel and userland.
Make both these limits a sysctl, so it is easy to change the limit.
If the userland part of ipfw finds that the sysctls don't exist,
it will just fall back to the traditional limits.
(100 packets is quite a small limit these days. If you want to test
TCP at 100Mbps, 100 packets can only accommodate a DBP of 12ms.)
Note these sysctls in the man page and warn against increasing them
without thinking first.
MFC after: 3 weeks
|
|
|
|
|
|
| |
number read from cylinder group. Chances that we read a smarshed
cylinder group, and we can not 100% trust information it has
supplied. fsck_ffs(8) will crash otherwise for some cases.
|
|
|
|
|
|
| |
processing the information. chk1 is more prone to crash when insane
information is provided by the on-disk inode, and does not even work
if the inode is being smarshed badly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
whether fs_bsize is larger than MINBSIZE, which is larger than the
value that is used to compared with fs_bsize, the sizeof fs, so the
check followed, will be always true.
By inspecting the code and some old commit log, I believe that the
check must be that *fs_sbsize* is larger than sizeof fs. We round
up the size to nearest dev_bsize, as the smallest accepted fs_sbsize,
personally, I think this can be even changed to equal, because this
number is mostly an invariant in file systems.
With this check, fsck_ffs(8) will be more picky and has better
chance rejecting bad first superblock rather than referring to bad
value it supplied, thus gives better chance for it to check the
filesystem carefully.
|
|
|
|
|
|
|
|
|
|
| |
from .01 to .000001.
Note that due to the architecture of ping6,
you are still limited to kern.hz pings per
second.
MFC after: 2 weeks
|
|
|
|
| |
MFC After: 1 week
|
|
|
|
|
|
|
| |
-Whitespace elimination.
Bug spotted by: Luiz Otavio O Souza
MFC After: 3 days
|
| |
|
|
|
|
|
|
|
| |
sbin/mount_nfs/mount_nfs.c #1.76. Let the dragons sleep.
Requested by: rodrigc, des
PR: kern/120319 (welcome the bug back)
|
|
|
|
|
|
| |
Bug spotted by: Luiz Otavio O Souza
PR: 120734
MFC After: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
table 'values' as IP addresses, use an explicit argument (-i).
This is a 'POLA' issue. This is a low risk change and should be MFC'd
to RELENG_6 and RELENG 7. it might be put as an errata item for 6.3.
(not sure about 6.2).
Fix suggested by: Eugene Grosbein
PR: 120720
MFC After: 3 days
|