summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* sprintf -> snprintfkris2001-07-241-1/+2
| | | | | Obtained from: OpenBSD MFC After: 1 week
* s/adress/address/kris2001-07-231-2/+2
| | | | | Inspired by: OpenBSD MFC After: 1 week
* Fix some bugs and general brain damage in mounttab:iedowse2001-07-221-4/+3
| | | | | | | | | | | | | | | | | | | | - Declare mtabhead as an extern in mounttab.h and define it only in mounttab.c. - Remove shared global `verbose' and instead pass it as a parameter. - Remove the `mtabp' argument to read_mtab(). It served no purpose whatsoever, although read_mtab() did use it as a temporary local variable. - Don't check for impossible conditions when parsing mounttab, and do detect zero-length fields. - Correctly test for strtoul() failures - just testing ERANGE is wrong. - Include a field name in syslog errors, and avoid passing NULL to a syslog %s field. - Don't test if arrays are NULL. - If there are duplicates when writing out mounttab, keep the last entry instead of the first, as it will have a later timestamp. - Fix a few formatting issues. Update rpc.umntall and umount to match the mounttab interface changes.
* Error messaging in ipfw(8) was out of hand, almost 50 lines of usagecjc2001-07-221-109/+114
| | | | | | | | | | | | | | information for any command line error, the actual error message almost always (and sometimes irretrievably) lost scrolling off the top of the screen. Now just print the error. Give ipfw(8) no arguments for the old usage summary. Thanks to Lyndon Nerenberg <lyndon@orthanc.ab.ca> for the patch and PR, but I had already done this when ru pointed out the PR. PR: bin/28729 Approved by: ru MFC after: 1 week
* Include the remote hostname in RPC-related warning messages. Exitiedowse2001-07-221-25/+24
| | | | | | | | | | | | | | | | | | immediately if a host specified by the -h flag cannot be parsed instead of attempting to unmount all NFS filesystems, which was bad. Add a missing return statement at the end of checkname(); this could result in a non-zero exit status in some cases even if the unmount succeeded. Group two separate NFS-related operations into one block to make it more obvious that a variable (hostp) is not dereferenced when uninitialised. Initialise it to NULL anyway to avoid a warning. Pass in the read_mtab()'s bogus argument as NULL instead of messing with a local variable to achieve the same effect. A later commit will clean up this mounttab interface.
* Change the foreground mount behaviour so that we keep retryingiedowse2001-07-212-7/+26
| | | | | | | | | | forever by default. This matches what mount_nfs did before revision 1.40, and it is the generally expected behaviour for NFS mounts. Document the current defaults near the start of the man page and mention the options that can be used to change them. Discussed on: -hackers
* Dike out the IPX bits if RELEASE_CRUNCH is defined.obrien2001-07-212-2/+23
|
* Perform a major cleanup of the usr.sbin Makefiles.obrien2001-07-201-8/+11
| | | | | These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before.
* Since revision 1.40/1.41, the default behaviour for mount_nfs isiedowse2001-07-192-12/+20
| | | | | | | | | | | | | | | | | to give up after one attempt unless a background mount is requested. Background mounts would retry 10000 times (at least 7 days) before giving up. For some situations such as diskless terminals, an NFS filesystem may be critical to the boot process, so neither the "try once" nor background mounts are appropiate. To cater for this situation, unbreak the -R (retry count) parameter so that it also works in the non-background case. Interpret a zero retry count as "retry forever". The defaults are now "try once" for non-background mounts and "retry forever" for background mounts; both can be overridden via -R. Add a description of this behaviour to the manpage.
* Document "-F".obrien2001-07-191-0/+7
|
* Change exit return value to better match fsck_ffs(8).obrien2001-07-191-1/+1
|
* Recognize the "-F" option which requests whether the filesystem needs toobrien2001-07-191-1/+5
| | | | | | | be cleaned immediately in foreground, or if its cleaning can be deferred to background. Submitted by: Maxime Henrion <mux@qualys.com>
* Use MD_NAME and MDCTL_NAME constants where appropriate.dd2001-07-181-1/+2
|
* fdisk(8): document the default for -b, add xref to boot0cfg(8).ru2001-07-182-0/+6
| | | | | | boot0cfg(8): add FILES section. Reviewed by: rnordier
* Sort options in DESCRIPTION.dd2001-07-151-14/+14
|
* Bump date for addition of -D.dd2001-07-151-1/+1
|
* Set WARNS=2 on programs which compile cleanly.dd2001-07-154-0/+4
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* Remove whitespace at EOL.dd2001-07-1549-356/+356
|
* Constify, de-register-ify, and set WARNS=2.dd2001-07-152-12/+15
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* Constify, de-register-ify, __unused-ify, and set WARNS=2.dd2001-07-152-10/+12
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* Constify and set WARNS=2.dd2001-07-152-1/+3
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* Fix a prototype and set WARNS=2.dd2001-07-152-2/+9
| | | | Submitted by: Mike Barcroft <mike@q9media.com>
* add -a to usage()billf2001-07-141-1/+1
| | | | | Submitted by: Ashley Penney <ashp@unloved.org> MFC after: 3 days
* After some (long-standing ;-) critics from Bruce, throw away the oldjoerg2001-07-134-78/+130
| | | | | | | | | | | | | | 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. :)
* mdoc(7) police: -xwidth has been fold into -width.ru2001-07-131-1/+1
|
* Due to the documented bug in inet_aton(3), it wasn't possibleru2001-07-111-2/+3
| | | | | | | | | | | 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''.
* mdoc(7) police: fixed markup and program name.ru2001-07-111-13/+16
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-1056-56/+56
|
* mdoc(7) police: minor markup tweaks.ru2001-07-101-2/+4
|
* mdoc(7) police:ru2001-07-101-11/+25
| | | | | Restored .Pa for ``dumpdates'' (it's still a file). Also, removed duplicate ``file'' words.
* Fix rule parsing breakage introduced in 1.103 cleanup. 'tcp' andcjc2001-07-101-5/+8
| | | | | | | 'icmp' rules could drop into infinite loops when given bad arguments. Reviewed by: ru, des Approved by: ru
* Fix disordering.obrien2001-07-091-1/+1
|
* Add fsck_msdosfsobrien2001-07-091-0/+1
|
* Style tweaks.obrien2001-07-091-2/+4
|
* Add fsck_msdosfs.obrien2001-07-099-0/+2716
| | | | Obtained from: NetBSD
* mdoc(7) police: remove extraneous .Pp before and/or after .Sh.dd2001-07-0912-17/+0
|
* Fix the type of the NULL arg to execl()brian2001-07-092-2/+2
| | | | Idea from: Theo de Raadt <deraadt@openbsd.org>
* Add manual page and usage for dump -D (supplied by Dima Dorfman) (will alsodillon2001-07-092-10/+24
| | | | | | be MFC'd) Submitted by: Dima Dorfman <dima@unixfreak.org>
* Oops, forgot to add 'D' to the option morphing block.dillon2001-07-081-0/+1
|
* Add a -D option to dump, allowing the path for the /etc/dumpdates file to bedillon2001-07-081-2/+6
| | | | | | | 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
* Ian Dowse writes:mjacob2001-07-071-16/+7
| | | | | | | | | | | 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
* Fix unaligned access faults on alpha.mjacob2001-07-071-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* mdoc(7) police: sort SEE ALSO xrefs (sort -b -f +2 -3 +1 -2).ru2001-07-065-10/+10
|
* mdoc(7) police: cosmetics.ru2001-07-061-1/+1
|
* mdoc(7) police: fix markup.ru2001-07-051-101/+159
|
* Update the dmesg man page to reflect the recent changes to dmesg.tmm2001-07-051-8/+14
| | | | Reviewed by: ru
* mdoc(7) police: fixed formatting.ru2001-07-051-37/+33
|
* Make open_disk() fail nicely upon encountering an ENOENT so to notjoerg2001-07-052-4/+8
| | | | | | | | | | 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
* Spelling police: extention -> extension.dd2001-07-051-1/+1
|
OpenPOWER on IntegriCloud