| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Implement -E option which will erase the filesystem sectors before
making the new filesystem. Reserved space in front of the superblock
(bootcode) is not erased.
NB: Erasing can take as long time as writing every sector sequentially.
This is relevant for all flash based disks which use wearlevelling.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
file format and about using NAT "instances".
Submitted by: "Andrey V. Elsukov" <bu7cher@yandex.ru>
|
|
|
|
|
| |
Submitted by: Stefan Sperling <stsp@stsp.name>
Reviewed by: brooks
|
|
|
|
|
| |
by virtue of there not being any (lower-case) letters avaliable for
more partitions.
|
|
|
|
| |
Reported by: njl
|
|
|
|
| |
Noticed by: brueffer
|
|
|
|
| |
Noticed by: brueffer
|
|
|
|
|
|
|
|
| |
PR: docs/112935
Submitted by: Julian Stacey <jhs at berklix dot org>
Actually this was inspired by the ticket submitted
by Julian.
MFC After: 3 days
|
|
|
|
|
|
|
|
|
| |
section (if nothing had been specified, or if the auto type had
been specified, a default layout is used).
PR: docs/116047
Submitted by: Ian Smith <smithi at nimnet dot asn dot au>
Minor modifications by me.
|
|
|
|
|
| |
Reviewed by: brooks
MFC after: 3 days
|
|
|
|
|
|
| |
PR: docs/117310
Submitted by: Ted Mittelstaedt <tedm at ipinc dot net>
with minor modifications by me.
|
|
|
|
|
|
| |
PR: docs/113570
Submitted by: lawrance
MFC After: 3 days (where applicable)
|
|
|
|
|
|
| |
previous commit, so make it happen now.
Prodded by: brueffer
|
|
|
|
|
|
| |
PR: docs/115721
Submitted by: Stefan Lambrev <stefan.lambrev@moneybookers.com>
MFC After: 3 days
|
|
|
|
|
|
|
|
|
| |
return -1 on error while any other return value from it can
indicate success. (See RETURN VALUE in our ioctl(2) manpage
and the POSIX spec.)
- Avoid assumptions about the state of the data buffer after
ioctl(2) failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a new option to newfs(8), -r, to specify reserved space at the
end of the device. It can be useful, e.g., when the device is to
become a member of a gmirror array later w/o losing the file system
on it.
Document the new option in the manpage.
While I'm here, improve error handling for -s option, which is
syntactically similar to -r; and document the fact that -s0 selects
the default fs size explicitly, which can be useful, e.g., in a
menu-based wrapper around newfs(8) requiring some value be entered
for the fs size.
Also fix a small typo in the help line for -s (missing space).
Idea and initial implementation by: marck
Discussed on: -fs
Critical review by: bde
Tested with: cmp(1)
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
- refer to the dummynet(4) man page only once, later use rather
the .Nm macro.
- use .Va macro when refering to the sysctl variables
- grammar and markup fixes
Reviewed by: keramida, trhodes, ru (roughly)
MFC-after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
Reviewed by: dwmalone, maxim
MFC after: 2 weeks
|
|
|
|
|
| |
on gcc 4.2. This is required for tinderbox which doesn't have
-f-no-strict-aliasing in it's custom CFLAGS.
|
|
|
|
| |
on at least arm and sparc64. i386/pc98, ia64 and amd64 are all OK.
|
|
|
|
| |
Pointed out by: ru
|
|
|
|
| |
casts from pointer to int here.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If it is set to zero value (default) dummynet module will try to emulate
real link as close as possible (bandwidth & latency): packet will not leave
pipe faster than it should be on real link with given bandwidth.
(This is original behaviour of dummynet which was altered in previous commit)
If it is set to non-zero value only bandwidth is enforced: packet's latency
can be lower comparing to real link with given bandwidth.
- Document recently introduced dummynet(4) sysctl variables.
Requested by: luigi, julian
MFC after: 3 month
|
|
|
|
|
|
|
|
|
| |
with ACCESSPERMS. Document in mount_ntfs(8) only the nine
low-order bits of mask are used (taken from mount_msdosfs(8)).
PR: kern/114856
Submitted by: Ighighi
MFC after: 1 month
|
|
|
|
|
|
| |
PR: conf/116177
Submitted by: Remi Guyomarch <rguyom@pobox.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reviewed by: pjd
MFC after: 3 days
|
|
|
|
|
|
| |
"(-a and -t vnode are implied)"
and reuse it near the cd9660 example.
* Spell 'backing store' as two words.
|
|
|
|
|
|
| |
use a trick submitted by Ruslan.
MFC after: 1 day
|
| |
|
|
|
|
|
|
| |
it appears to be in: there is also CIDR.
Noticed by: tegge
|
|
|
|
|
|
|
|
| |
interface. Once the limit is reached packets with unknown source addresses are
dropped until an existing host cache entry expires or is removed. Useful to
use with the STICKY cache option.
Sponsored by: miniSuperHappyDevHouse NZ
|
|
|
|
| |
has a subset of the classes compiled-in.
|
|
|
|
|
|
|
| |
general code cleanups
Reviewed by: thompsa, avatar
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
a valid PMBR. Without this fix, if label a disk with a GPT, then relabel
it with an MBR the GPT tables are still present. If you then try to create
a GPT with 'gpt create', gpt(8) will fail to open the device because the
partitions in the stale GPT overlap with the slices in the MBR.
MFC after: 1 week
|
|
|
|
|
|
| |
disk devices have to consist of a block of sectors. Thus, when writing
gptboot to the boot partition, round the size of the gptboot file up to a
sector boundary, pre-zero it, and write out the full buffer to disk.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
command would add incorrect routing entries if network numbers weren't
fully "spelled" out according to their class. For example:
# route add 128.0/16 (works)
# route add 128/16 (doesn't work)
# route add 193.0.0/24 (works)
# route add 193/24 (doesn't work)
Also, rework the way a netmask is deduced from network number if
it [netmask] is not specified.
Submitted by: Nuno Antunes <nuno.antunes@gmail.com> (mostly)
MFC after: 1 week
|