| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
magic.
|
|
|
|
|
|
|
|
|
|
| |
checking and only recognizes numbers in base 10. The attached patch
checks errno after strtol() and uses a base of 0 to allow octal, or hex
sector numbers too.
PR: 73112
Submitted by: keramida
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
strings. This isn't necessarily a bug, but it can be slightly inconvenient,
because atol() doesn't know how to parse hexadecimal or octal numbers and at
least one of the options of ffsinfo(8) would be easier to use if it did.
Changing atol() -> strtol() allows one to use hex masks for -l MASK, i.e.:
orion:/a/freebsd/src/sbin/ffsinfo# ./ffsinfo -l 0x3ff /
PR: 73110
Submitted by: keramida
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
tree.
MFC after: 3 days
Submitted by: bkoenig at cs dot tu-berlin dot de
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
special-purpose code to display status for an interface for
state that was not address-oriented. This status reporting
was merged in to the address-oriented status reporting but
did not work for link address reporting (as discovered with
fwip interfaces). Correct this mis-merge and eliminate the
bogus kludge that was used for link-level address reporting.
o add an af_other_status method for an address family for
reporting status of things like media, vlan, etc.
o call the af_other_status methods after reporting address
status for an interface
o special-case link address status; when reporting all
status for an interface invoke it specially prior to
reporting af_other_status methods (since it requires the
sockaddr_dl that is passed in to status separately from
the rtmsg address state)
o correct the calling convention for link address status;
don't cast types, construct the proper parameter
This fixes ifconfig on fwip interfaces.
|
|
|
|
|
|
|
| |
printed for status (allows cut&paste)
o accept undef for the deftxkey/weptxkey so you can reset state
Requested by: phk
|
| |
|
|
|
|
|
| |
PR: 75616
Submitted by: n-kogane@syd.odn.ne.jp
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
|
|
|
| |
message, i.e.:
geom: usage: geom <class> <command> [options]
PR: bin/71537
Submitted by: bugghy <bugghy@phenix.rootshell.be>
MFC after: 5 days
|
|
|
|
|
|
|
|
|
| |
show file name for 'mdconfig -l -u <x>' command.
This allows to preserve API/ABI compatibility with version 0 (that's why
I changed version number back to 0) and will allow to merge this change
to RELENG_5.
MFC after: 5 days
|
|
|
|
| |
Noticed by: clement
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, when component is disconnected because of an I/O error,
it will not be connected and synchronized automatically, it will be logged
as broken and skipped. Autosynchronization can occur, when component is
disconnected (on orphan event) and connected again - there were no I/O
error, so there is no need to not connected the component, but when there were
writes while it wasn't connected, it will be synchronized.
This fix cases, when component is disconnected because of I/O error and can be
connected again and again.
- Bump version number.
- Implement backward compatibility mechanism. After this change when metadata in
old version is detected, it is automatically upgraded to the new (current)
version.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, when component is disconnected because of an I/O error,
it will not be connected and synchronized automatically, it will be logged
as broken and skipped. Autosynchronization can occur, when component is
disconnected (on orphan event) and connected again - there were no I/O
error, so there is no need to not connected the component, but when there were
writes while it wasn't connected, it will be synchronized.
This fix cases, when component is disconnected because of I/O error and can be
connected again and again.
- Bump version number.
- Add version change history.
- Implement backward compatibility mechanism. After this change when metadata in
old version is detected, it is automatically upgraded to the new (current)
version.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
OK'ed by: core
|
|
|
|
|
|
| |
describing the changes in device management since FreeBSD 4.0.
Reviewed by: ru
|
|
|
|
| |
we added a WARNS 7 level, it shouldn't be assumed this code will pass it.
|
| |
|
| |
|
|
|
|
|
|
| |
until all the command line args have been processed
Reviewed by: ambrisko
|
|
|
|
|
|
|
| |
required when using ucred based rules.
Pointed out by: seanc (thanks!)
MFC after: 1 month
|
|
|
|
|
| |
when this mode is used.
- Manual page update.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o break per-address family support out into separate files
o modularize per-address family and functional operations using
a registration mechanism; this permits configuration according
to which files you include (but beware that order of the files
is important to insure backwards compatibility)
o many cleanups to eliminate incestuous behaviour, global variables,
and poor coding practices (still much more to fix)
The original motivation of this work was to support dynamic addition
of functionality based on the interface so we can eliminate the various
little control programs and so that vendors can distribute ifconfig
plugins that support their in-kernel code. That work is still to be
completed.
o Update 802.11 support for all the new net80211 functionality; some
of these operations (e.g. list *) may be better suited in a different
program
|
|
|
|
| |
The filesystem is named "ufs" not "ffs".
|
|
|
|
|
| |
PR: docs/44435
Submitted by: Slaven Rezic slaven dot rezic at berlin dot de
|
|
|
|
|
|
|
|
|
| |
PR: bin/69977
o Remove unused ddates_in.
Obtained from: NetBSD
MFC after: 3 weeks
|
|
|
|
| |
but allows a "nodev" in /etc/fstab, etc.
|
|
|
|
|
| |
Submitted by: Janusz Muc'ka (Defacto) <gdef at cvd dot pl>
MFC after: 3 days
|
|
|
|
| |
Asked to commit by: phk
|
|
|
|
|
|
|
|
| |
Prompted by
PR: docs/73668
Submitted by: Dan Pelleg
MFC After: 3 days
|
|
|
|
| |
including other headers.
|
|
|
|
| |
for debugging and emergency purposes.
|
| |
|
|
|
|
|
|
| |
front of it.
Reviewed by: phk
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
previous two commits and combine them with the existing flags
that were already there.
Pointed out by: ru@
|
|
|
|
|
| |
with unknown partitions is not migrated. By specifying the -f option
migration will happen and unknown partitions will be lost.
|
|
|
|
|
|
|
| |
allows the user to force the creation of a GPT even when there's a
MBR on the device. The MBR is simply wiped and any partitions
described by it are lost. Without the -f option one cannot create
a GPT when there's a MBR.
|
|
|
|
|
|
| |
Might as well do them all while I'm at it :-)
Submitted by: Steve Kargl <sgk@troutmask.apl.washington.edu>
|
|
|
|
|
|
|
|
| |
and 'mediasz' is in bytes. As it so happens, we define 'last' as the
sector number of the last sector on the medium which also is the size
of the PMBR partition. Therefore, use 'last' instead of 'mediasz'.
Submitted by: Dan Markarian <markarian at apple dot com>
|