summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* When listing all devices (geoms) from the given class, skip geoms withoutpjd2005-03-131-0/+2
| | | | | | | | providers. This prevents from listing geoms like <name>.sync which can be confusing. It still allows to show details about it by giving its name when listing. MFC after: 1 week
* gbde(8) is also rejndael user.ume2005-03-111-1/+1
| | | | Reported by: phk
* Belatedly update the md5(1) man page to reflect the addition of sha256.cperciva2005-03-101-6/+11
|
* In light of the recent 2^69 operation collision-finding attack on SHA1,cperciva2005-03-092-4/+24
| | | | | | | | add support for SHA256. Tested on: i386, sparc64 Tested using: NIST test vectors, built-in tests X-MFC-after: 5.4-RELEASE
* Prefer the __printflike() macro to GCC's __attribute__ stuff.stefanf2005-03-091-1/+1
|
* Make background fsck based summary adjustments actually work bydelphij2005-03-073-5/+24
| | | | | | | | | | | | | | | | | | | | | | | initializing the sysctl mibs data before actually using them. The original patchset (which is the actual version that is running on my testboxes) have checked whether all of these sysctls and refuses to do background fsck if we don't have them. Kirk has pointed out that refusing running fsck on old kernels is pointless, as old kernels will recompute the summary at mount time, so I have removed these checks. Unfortunatelly, as the checks will initialize the mib values of those sysctl's, and which are vital for the runtime summary adjustment to work, we can not simply remove the check, which will lead to problem when running background fsck over a dirty volume. Add these checks in a different way: give a warning rather than refusing to work, and complain if the functionality is not available when adjustments are necessary. Noticed by: A power failure at my lab Pointy hat: me MFC After: 3 days
* Use a signal-safe type for two variables that are used to synchroniseiedowse2005-03-021-2/+2
| | | | | | with a signal handler. This fixes a race condition introduced by compiler reordering that caused dump to sometimes get stuck, especially while dumping large filesystems.
* We can specify device size in bytes. Document this in usage.pjd2005-03-011-2/+3
|
* Typos and grammar fixes, wordsmithingbrueffer2005-02-281-6/+6
|
* - Add md_provsize field to metadata, which will help withpjd2005-02-276-15/+36
| | | | | | | | | | | | | | | | | shared-last-sector problem. After this change, even if there is more than one provider with the same last sector, the proper one will be chosen based on its size. It still doesn't fix the 'c' partition problem (when da0s1 can be confused with da0s1c) and situation when 'a' partition starts at offset 0 (then da0s1a can be confused with da0s1 and da0s1c). One can use '-h' option there, when creating device or avoid sharing last sector. Actually, when providers share the same last sector and their size is equal, they provide exactly the same data, so the name (da0s1, da0s1a, da0s1c) isn't important at all. - Provide backward compatibility. - Update copyright's year. MFC after: 1 week
* - Add GEOM_LIBRARY_PATH environment variable which allows to specify anpjd2005-02-272-3/+27
| | | | | | | alternative to /lib/geom/ path where shared libraries are stored. - Improve debugging. MFC after: 3 days
* Add SHSEC class to the list of geom(8)-aware classes.pjd2005-02-271-0/+2
| | | | MFC after: 3 days
* Remove filtering on major device number. These are assigned randomlyphk2005-02-272-13/+2
| | | | | these days so filtering on them makes no sense other than as a foot-shooting device.
* style(9).obrien2005-02-261-43/+45
|
* Add a missing comma.pjd2005-02-251-1/+1
|
* Allow a forced dump even if the dump header information is inconsistent.obrien2005-02-242-18/+61
| | | | | | Output more verbosity with additional -v's. Submitted by: seanc
* Fix a couple of grammar nits.trhodes2005-02-241-3/+3
| | | | | PR: 77437 Submitted by: Paul A. Hoadley <paulh@logicsquad.net> (original version)
* Bring back the full packet destination manipulation for 'ipfw fwd'andre2005-02-221-1/+14
| | | | | | | | | | | | | | | | | | | | with the kernel compile time option: options IPFIREWALL_FORWARD_EXTENDED This option has to be specified in addition to IPFIRWALL_FORWARD. With this option even packets targeted for an IP address local to the host can be redirected. All restrictions to ensure proper behaviour for locally generated packets are turned off. Firewall rules have to be carefully crafted to make sure that things like PMTU discovery do not break. Document the two kernel options. PR: kern/71910 PR: kern/73129 MFC after: 1 week
* Use afswch->af_other_status for carp_status() and pfsync_status().glebius2005-02-222-6/+6
| | | | Sponsored by: Rambler
* Add CARP (Common Address Redundancy Protocol), which allows multipleglebius2005-02-223-0/+346
| | | | | | | | | | | | | hosts to share an IP address, providing high availability and load balancing. Original work on CARP done by Michael Shalayeff, with many additions by Marco Pfatschbacher and Ryan McBride. FreeBSD port done solely by Max Laier. Patch by: mlaier Obtained from: OpenBSD (mickey, mcbride)
* Document the terabyte "-s" parameter in the usage string.mr2005-02-211-1/+2
| | | | Split the usage line to not exceed 80 chars.
* The recomputation of file system summary at mount time can be adelphij2005-02-202-0/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | very slow process, especially for large file systems that is just recovered from a crash. Since the summary is already re-sync'ed every 30 second, we will not lag behind too much after a crash. With this consideration in mind, it is more reasonable to transfer the responsibility to background fsck, to reduce the delay after a crash. Add a new sysctl variable, vfs.ffs.compute_summary_at_mount, to control this behavior. When set to nonzero, we will get the "old" behavior, that the summary is computed immediately at mount time. Add five new sysctl variables to adjust ndir, nbfree, nifree, nffree and numclusters respectively. Teach fsck_ffs about these API, however, intentionally not to check the existence, since kernels without these sysctls must have recomputed the summary and hence no adjustments are necessary. This change has eliminated the usual tens of minutes of delay of mounting large dirty volumes. Reviewed by: mckusick MFC After: 1 week
* When creating a new FFS file system, the block size will indirectlydelphij2005-02-201-0/+10
| | | | | | | | | | | | | affect the largest file size that is allowed by the file system. On the other hand, when creating a snapshot, the snapshot file will appear as it is as big as the file system itself. Hence we will not be able to create a file system on large file systems with small block sizes. Add a warning about this, and gives some hints to correct the issue. Reviewed by: mckusick MFC After: 1 week
* Fix year in copyrights.pjd2005-02-162-2/+2
|
* va_list style tweaksobrien2005-02-161-1/+2
|
* Fix grammar error.obrien2005-02-151-1/+1
|
* Expand contractions.ru2005-02-132-3/+3
|
* Expand *n't contractions.ru2005-02-1312-32/+32
|
* Reword a sentence to conform with our mdoc(7) style.trhodes2005-02-121-3/+4
| | | | | | | Modify wording in a sentence to avoid a run on within (). Remove a contraction. Submitted by: Joel Dahl <joel@automatvapen.se> (original version)
* - Fixed description of the "destroy" command options.ru2005-02-122-28/+45
| | | | | - Document the "nuke" command. - Mention which commands correspond to which functions.
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-102-3/+5
|
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-1046-150/+135
|
* - Correctly spell MOD_QUIESCEglebius2005-02-091-1/+3
| | | | | | - use .Dv for it MFC after: 3 days
* Fixed the misplaced $FreeBSD$.ru2005-02-095-7/+7
|
* Sort SEE ALSO.glebius2005-02-071-1/+1
| | | | Submitted by: ru
* Document how interaction with ng_ipfw node is configured.glebius2005-02-051-2/+23
|
* Add a ng_ipfw node, implementing a quick and simple interface betweenglebius2005-02-051-0/+22
| | | | | | ipfw(4) and netgraph(4) facilities. Reviewed by: andre, brooks, julian
* - Sort options.pjd2005-02-031-8/+9
| | | | - Put 'break' into separate line.
* Fix whitespace.pjd2005-02-031-6/+5
|
* - Remove bogus O_CREAT flag. We really don't want to create a file here.pjd2005-02-031-7/+7
| | | | | | | | | | PR: bin/67793 Submitted by: Amir Shalem <amir@boom.org.il> - Sync usage with manual page. Approved by: phk MFC after: 1 week
* Remove unsigned casts.ssouhlal2005-01-311-4/+8
| | | | | Discussed with: delphij, stefanf Approved by: grehan (mentor)
* Document -f in usage().ru2005-01-301-2/+2
|
* Let bsd.prog.mk set SRCS and MAN to their default values.ru2005-01-284-6/+0
|
* Change the ifr_media operation to only get its value and only setambrisko2005-01-271-79/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | its value once per ifconfig run. Use Sam's new callback operation to set it when everything is done. The purpose for this is that if you did something like ifconfig bge0 media 100baseTX mediaopt full-duplex multiple times it would end up causing the PHY to re-sync since it would send the IOCTLs: ifconfig bge0 media 100baseTX -mediaopt full-duplex ifconfig bge0 media 100baseTX mediaopt full-duplex This would cause the PHY to be updated twice even though there really wasn't any change since the check in sys/net/if_media.c would always fail. Caveat is that this doesn't fix the case of: ifconfig bge0 media autoselect etc. since in sys/net/if_media.c it forces an autoselect to go through the entire process in ifmedia_ioctl :-( : /* * If no change, we're done. * XXX Automedia may invole software intervention. * Keep going in case the the connected media changed. * Similarly, if best match changed (kernel debugger?). */ if ((IFM_SUBTYPE(newmedia) != IFM_AUTO) && (newmedia == ifm->ifm_media) && (match == ifm->ifm_cur)) return 0; Briefly looked at by: sam
* Get rid of a NULL dereference when oid is too long.ssouhlal2005-01-251-1/+2
| | | | | | Reviewed by: keramida Approved by: grehan (mentor) MFC after: 1 week
* - Make WARNS?= 6 cleanssouhlal2005-01-252-2/+4
| | | | | | - Add WARNS?= 6 Approved by: stefanf, grehan (mentor)
* Use new style declarations instead of K&R ones.delphij2005-01-251-10/+5
|
* Use modern style defination for main() and move a externdelphij2005-01-252-4/+6
| | | | | | declaration to global section. Bump WARNS?= to 6
* Code style tweaks: Use static and const where suitable.delphij2005-01-251-7/+6
|
* The kernel specified in main() of reboot(8) will be initializeddelphij2005-01-252-5/+5
| | | | | | | | | | | | | with -k option and never be used without kflag. This confuses gcc because we set "kflag" at the same time with "kernel", but the logic is not that apparant for gcc. Since we can initialize "kernel" to NULL then know if "k" option is set through determining whether it is still NULL, don't try to have gcc to guess why we are connecting "kflag" with "kernel" and use "kernel" directly in place of kflag. Bump WARNS?= from 2 to 6
OpenPOWER on IntegriCloud