| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
PR: docs/17060
Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
|
|
|
|
|
| |
PR: docs/17080
Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
|
|
|
|
|
|
|
|
|
| |
Describe stop -f to stop when config updates are disabled.
Explain in more detail why Vinum needs its own partition type, and why
you can't make it the c partition.
Implicitly-sanctioned-by: jkh
|
|
|
|
| |
Implicitly-sanctioned-by: jkh
|
|
|
|
|
|
| |
be marked as stalled, from 1 second to 5 seconds.
Implicitly-sanctioned-by: jkh
|
|
|
|
|
|
|
| |
process, move the body of vinum_rebuildparity and vinum_checkparity to
a new function, parityops.
Implicitly-sanctioned-by: jkh
|
| |
|
|
|
|
| |
Approved-by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
replaces an older attempt to silence vinum(8) when started in
single-user mode.
Add entries for vinum_raid[45].
Replace the preprocessor variable name CDEV_MAJOR with
VINUM_CDEV_MAJOR.
continue_revive: Set the proc title to 'reviving <sdname>' so that it
can be recognized in a ps list.
Approved-by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
drive if it is set.
vinum_lvi: Change line spacing. This is still not right.
Change checks for striped or RAID-5 plexes to a macro 'isstriped',
which now also includes RAID-4.
Change checks for RAID-5 plexes to a macro 'isparity', which now also
includes RAID-4.
vinum_lsi: If the subdisk is initializing or reviving, don't wait a
whole second to check whether it's advancing; wait in increments of 50
ms up to 1 second. This makes for a barely perceptible delay.
Approved-by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enabled and print a warning message in varous places if they are not.
Fix typos in comments.
Change some indents to approach style(9).
initvol: If init fails, place the subdisks in a "down" state.
vinum_start(): If we're starting a plex, try doing it directly. It's
possible that the state of the plex differs from that of the subdisks,
for example if somebody has used 'setupstate'.
New functions vinum_raid4 and vinum_raid5 to create RAID-4 and RAID-5
volumes, analagous to vinum_mirror and vinum_stripe.
vinum_checkparity: Don't try to check the parity of a non-parity plex,
print a rude remark instead.
Approved-by: jkh
|
|
|
|
|
|
|
| |
devices, but it's certainly possible to make use of them.
PR: 17013
Submitted by: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DIR I=64512 CONNECTED. PARENT WAS I=4032
fsck: cannot find inode 995904
fsdb found the inodes with no problem:
fsdb (inum: 64512)> inode 995904
current inode: directory
I=995904 MODE=40777 SIZE=512
MTIME=Feb 14 15:27:07 2000 [0 nsec]
CTIME=Feb 14 15:27:07 2000 [0 nsec]
ATIME=Feb 24 10:31:58 2000 [0 nsec]
OWNER=nobody GRP=nobody LINKCNT=4 FLAGS=0 BLKCNT=2 GEN=38a41386
Direct blocks: 8094568 0 0 0 0 0 0 0 0 0 0 0
Indirect blocks: 0 0 0
The problem turns out to be a program logic error in fsck. It stores
directory inodes internally in hash lists, using the number of
directories to form the hash key:
inpp = &inphead[inumber % numdirs];
Elsewhere, however, it increments numdirs when it finds unattached
directories. I've made the following fix, which solved the problem in
the case in hand.
Submitted by: Greg Lehey <grog@lemis.com>
Reviewed by: Matthew Dillon <dillon@apollo.backplane.com>
Approved by: Kirk McKusick <mckusick@mckusick.com>
|
|
|
|
| |
Approved by: jkh
|
|
|
|
| |
Reviewed by: luigi, sheldonh
|
| |
|
|
|
|
|
|
|
|
|
| |
Improve compatibility with BSD/OS, and also more accurately reflect that
IP aliases aren't really any different than the primary IP address on an
interface.
Reviewed by: dcs
Approved by: jkh
|
|
|
|
| |
better read.
|
| |
|
|
|
|
|
|
| |
PR: 16900
Reviewed by: "Crist J. Clark" <cjclark@home.com>, jkh
Approved by: jkh
|
| |
|
|
|
|
|
|
|
|
|
| |
-Open socket() at first and then setuid() to actual user.
-Allow ping6 preload option only for root.
Approved by: jkh
Submitted by: Neil Blakey-Milner <nbm@mithrandr.moria.org>
|
|
|
|
|
|
| |
command.
This is a workaround for some kernel interface which can't treat sin6_scope_id,
yet.
|
|
|
|
|
|
|
| |
Kirk argees that the comment about corruption caused by switching the flags
on an already mounted manpage are bogus, it doesn't happen.
Ok by: mckusick
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
256 bytes) caused it to break on many devices.
The SCSI spec says that for commands with 8-bit length fields, a value of 0
means 256 bytes. As it turns out, many devices don't deal with that
properly. Some interpret the 0 as 0, and return no data. Others return
more than 256 bytes of data, and cause an overrun.
The fix is to tell the device we've only allocated SHORT_INQUIRY_LENGTH (36
bytes) of inquiry data, instead of sizeof(struct scsi_inquiry_data).
camcontrol.c: Change inq_len in the call to scsi_inquiry() to
SHORT_INQUIRY_LENGTH, and add a long comment
explaining the reason for the change.
scsi_all.h: Add a comment above the definitinon of
SHORT_INQUIRY_LENGTH alerting people that it is
both the initial probe inquiry length, and the
minimum amount of data needed for scsi_print_inquiry()
to function.
scsi_all.c: Add a comment about SHORT_INQUIRY_LENGTH being the
minimum amount of data needed for
scsi_print_inquiry() to function.
Reviewed by: gibbs
Approved by: jkh
Reported by: "John W. DeBoskey" <jwd@unx.sas.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Sorry for the flapping, but no change will be done for 4.0 anymore.
Official standard will be published around April or later.
If different format would be adopted at that time, then support for
the new format will be added to the succeeding FreeBSD 4.x.
Approved by: jkh
|
|
|
|
|
| |
PR: 15600
Reviewed by: jim
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Communication"
include a copy of the 3.0.1 firmware for the PCA200E card in the fore_dnld
program.
There are various and subtle compatibility issues between the hfa driver and
the microcode, this version is belived to work best.
If a file is specified on the command line it will be used instead of the
embedded image.
Approved by: jkh
|
| |
|
|
|
|
| |
Approved by: jkh
|
|
|
|
| |
Approved-by: jordan
|
|
|
|
|
|
|
|
|
| |
IPv6 scoped addr display is not yet supported by ifconfig
and route. Now almost of IPv6 apps support it, so its support
in ifconfig and route is important to keep consisetncy, and
to avoid user confusion.
Approved by: jkh
|
| |
|
|
|
|
|
| |
that we supported an IPv6 firewall since version 2.0. It now correctly
says `4.0'.
|
|
|
|
|
|
| |
Approved by: jkh
Submitted by: Matthew Reimer <mreimer@vpop.net>
|
|
|
|
|
|
|
| |
Without this change, you cannot do the required init on a new raid5 volume.
Reviewed by: grog
Approved by: jkh
|
|
|
|
|
| |
Submitted by: T-Om <tom@iki.fi>
Approved by: jkh
|
|
|
|
| |
Submitted by: joerg
|
| |
|
|
|
|
|
|
|
| |
device, they are equivalent now (or more accurately we no longer have block
devices).
Submitted by: Gregory Sutter <gsutter@pobox.com>
|
|
|
|
|
|
|
|
|
|
| |
Yes it is almost code freeze, but as the result of many thought, now I
think this should be added before 4.0...
make world check, kernel build check is done.
Reviewed by: green
Obtained from: KAME project
|
|
|
|
| |
due to recently incremented namespace pollution in <unistd.h>.
|
|
|
|
| |
Obtained from: KAME Project
|
|
|
|
|
|
|
| |
the interface MTU change (src/sys/net/if_sl.c,v 1.83), track
interface MTU with -dynamic option as well.
PR: 15494
|
|
|
|
|
| |
the strings "FreeBSD" and "NetBSD". Use the .Fx or .Nx macro
instead.
|
|
|
|
| |
Reviewed by: ken@freebsd.org
|
|
|
|
|
|
|
| |
as a separate line so we can override it on the command line if
we need to.
Reviewed by: ken@freebsd.org
|