| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
|
| |
Submitted by: Ashley Penney <ashp@unloved.org>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
device search code i introduce nearly six years ago in rev 1.8. Bruce
suggested to rather use the device name of the root filesystem instead
which is certainly the most sensible default. Since there are many
possible cases for a root filesystem name (device with and without
slices, consider /dev/vinum/root even though it currently could not
work as such), there's some heuristic using a RE in order to find out
the canonical device name from the mounted name. This probably won't
quite fit for a NFS root (can't test that right now), but then,
there's hard to find a good default for those machines anyway. ;-)
This unbreaks the functionality of rev 1.2 i once broke in 1.8. :)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
to use 0xffffffff (INADDR_NONE) as a netmask value. The fix
is to use inet_addr(3) which doesn't suffer from this problem.
PR: bin/28873
Also, while here, fixed the bug when netmask value was ignored
(RTF_HOST flag was set) if the "destination gateway netmask"
syntax is used, e.g. ``route add 1.2.3.4 127.1 255.255.255.255''.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Restored .Pa for ``dumpdates'' (it's still a file).
Also, removed duplicate ``file'' words.
|
|
|
|
|
|
|
| |
'icmp' rules could drop into infinite loops when given bad arguments.
Reviewed by: ru, des
Approved by: ru
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
|
|
|
|
|
| |
be MFC'd)
Submitted by: Dima Dorfman <dima@unixfreak.org>
|
| |
|
|
|
|
|
|
|
| |
changed, so independant entities backing up the same thing to different
media can be made not to trip over each other.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
The original code was certainly broken; it knows that whereto is
to be used for a sockaddr_in, so it should be declared as such.
To support multiple protocols, there is also a sockaddr_storage
struct that can be used; I don't think struct sockaddr is supposed
to be used anywhere other than for casts and pointers.
Submitted by: Ian Dowse <iedowse@maths.tcd.ie>
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This one is strange and goes against my rusty compiler knowledge.
The global declaration
struct sockaddr whereto;
produces for both i386 && alpha:
.comm whereto,16,1
which means common storage, byte aligned. Ahem. I though structs
were supposed to be ALDOUBLE always? I mean, w/o pragma packed?
Later on, this address is coerced to:
to = (struct sockaddr_in *)&whereto;
Up until now, we've been fine on alpha because the address
just ended up aligned to a 4 byte boundary. Lately, though,
it end up as:
0000000120027b0f B whereto
And, tra la, you get unaligned access faults. The solution I picked, in
lieu of understanding what the compiler was doing, is to put whereto
as a union of a sockaddr and sockaddr_in. That's more formally correct
if somewhat awkward looking.
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: ru
|
| |
|
|
|
|
|
|
|
|
|
|
| |
prematurely terminate the search for a usable disk. ENOENT is quite
normal in particulare now with the advent of devfs.
While being here, also remove /dev/wd0 and /dev/od0 from the list of
disks to search since we don't have them anymore.
MFC after: 1 week
|
| |
|
|
|
|
| |
Keep document title (.Dt) in CAPITALS, as required by the mdoc(7) manpage.
|
| |
|
| |
|
|
|
|
| |
kernel, and remove setgid kmem, which is not needed any more.
|
|
|
|
| |
MFC after: 5 days
|
|
|
|
|
| |
PR: 8479
Submitted by: Adrian Filipi-Martin <adrian@ubergeeks.com>
|
|
|
|
|
|
|
|
| |
backslash as nothing, treat it like a space so that adjacent lines
aren't glued together.
PR: 8479
Submitted by: Adrian Filipi-Martin <adrian@ubergeeks.com>
|
|
|
|
|
|
| |
Reviewed by: ru, ume
Obtained from: NetBSD
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
| |
PR: bin/17640
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
user runs with privilege, allowing the sending of icmp packets with
larger size (up to 48k, the default receive buffer size in ping),
which is useful for network driver development testing, as well
as experimentation with fragmentation.
Reviewed by: wpaul
|
|
|
|
| |
Thanks to: dd for noticing the need for a cast.
|
|
|
|
|
|
|
| |
- a wording improvement in BUGS (ping vs ping6 issue)
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
option, regardless of the -f option.
based on a comment from Tomohide Nagashima <tomohide@japan-telecom.co.jp>.
Obtained from: KAME
MFC after: 1 week
|