summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* In mapdirs(), do not use the `dp' inode pointer after searchdir()iedowse2003-11-041-3/+3
| | | | | | | | | | | | | | has been called, since it points to a shared inode buffer that may be overwritten. The two cases where `dp' was used incorrectly appear to have been overlooked when "nodump" inheritance was first added in revision 1.12. This is reported to correct propagation of the nodump flag on directories that are larger than one block in size. PR: bin/58912 Submitted by: Volker Paepcke <vpaepcke@incore.de> MFC after: 1 week
* Add missing prototype for cread().iedowse2003-11-041-0/+1
|
* Create a .snap directory mode 770 group operator in the root ofmckusick2003-11-041-6/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | a new filesystem. Dump and fsck will create snapshots in this directory rather than in the root for two reasons: 1) For terabyte-sized filesystems, the snapshot may require many minutes to build. Although the filesystem will not be suspended during most of the snapshot build, the snapshot file itself is locked during the entire snapshot build period. Thus, if it is accessed during the period that it is being built, the process trying to access it will block holding its containing directory locked. If the snapshot is in the root, the root will lock and the system will come to a halt until the snapshot finishes. By putting the snapshot in a subdirectory, it is out of the likely path of any process traversing through the root and hence much less likely to cause a lock race to the root. 2) The dump program is usually run by a non-root user running with operator group privilege. Such a user is typically not permitted to create files in the root of a filesystem. By having a directory in group operator with group write access available, such a user will be able to create a snapshot there. Having the dump program create its snapshot in a subdirectory below the root will benefit from point (1) as well. Sponsored by: DARPA & NAI Labs.
* Check that the user running mksnap_ffs has permission to create andmckusick2003-11-041-1/+33
| | | | | | | remove a snapshot file from the directory in which they have requested to have it made. If they do not have write permission in the directory or the directory is sticky and not owned by the user, then they will not be able to remove the snapshot when they are done with it.
* Set exit code to 1 in case at least one of the input filesse2003-11-022-2/+13
| | | | could not be opened.
* Style.ru2003-11-021-1/+1
|
* Revert the first part of my previous change.trhodes2003-11-011-4/+6
| | | | Requested by: wollman
* The copywrite is not a 'static char', remove the #ifdefs and move the ↵trhodes2003-11-011-6/+4
| | | | | | | | copywrite up into the commented out 'copywrite' section. Include sys/linker.h for kldload(3).
* Fix a few style glitches in the previous commit and make thesilby2003-11-011-5/+5
| | | | | | tunable error message more brief. Suggested by: bde
* We want the length of the string, not the size of its pointer.brooks2003-11-011-1/+1
|
* Temporarily disconnect ipfstat, ipnat, and ipftest to unbreak world.brooks2003-10-311-3/+1
| | | | Pointy hat to: brooks
* Replace the if_name and if_unit members of struct ifnet with new membersbrooks2003-10-312-37/+18
| | | | | | | | | | | | | if_xname, if_dname, and if_dunit. if_xname is the name of the interface and if_dname/unit are the driver name and instance. This change paves the way for interface renaming and enhanced pseudo device creation and configuration symantics. Approved By: re (in principle) Reviewed By: njl, imp Tested On: i386, amd64, sparc64 Obtained From: NetBSD (if_xname)
* Use (char *)NULL to terminate the argument list for execlp().harti2003-10-301-1/+1
| | | | | Without this cast the compiler cannot know that it has to convert the null pointer constant NULL to a null pointer.
* In check.c:trhodes2003-10-302-5/+2
| | | | | Avoid shadowing declarations. Avoid compairing signed and unsigned types.
* Remove a few unused variables.trhodes2003-10-301-3/+2
|
* style(9): sort functions.trhodes2003-10-291-8/+8
|
* Properly prototype C function usage().trhodes2003-10-291-1/+3
| | | | Sync usage() with the manual page: s/file/snapshot_name/g.
* When removing trailing slashes, don't remove the first characteriedowse2003-10-291-3/+3
| | | | | of the name if it is '/'. Also fix a comparison between signed and unsigned quantities (pointed out by trhodes).
* Bump WARNS level and add a '?' to WARNS=.trhodes2003-10-291-1/+1
|
* Remove redundant declaration of the perror() function, it's provided by stdio.h.trhodes2003-10-292-2/+0
| | | | Don't define DKTYPENAMES without using it.
* Defer allocation of the actual receive mbuf until the external bufferharti2003-10-291-0/+1
| | | | | | | | | | is returned from the card to the driver. Add a counter that shows how many times this allocation has failed. Note, that we could even further delay the allocation of the mbuf until we know, that we need it (there are no receive errors and the connection is open). This will be done in a later commit. Print the new statistics field in atmconfig.
* Fix some 64 bit warnings. You can't fit a pointer in an int.peter2003-10-261-4/+4
|
* Fix a 64 bit warning. Have set_T_dev_t() take a pointer to a size_t ratherpeter2003-10-261-2/+2
| | | | than a pointer to an int, since that is what it really wants anyway.
* Fix gcc warnings. If NAME_MAX is 255, and d_namlen is a uint8_t, thenpeter2003-10-261-2/+7
| | | | | d_namlen can never be > NAME_MAX. Stop gcc worrying about this by using a preprocessor test to see if NAME_MAX changes.
* 64 bit fixes. in_addr_t is an uint32_t, not a u_long.peter2003-10-261-1/+1
|
* Give wider types to sscanf to fix two warnings (u_short cannot be > 0xffff)peter2003-10-261-2/+2
| | | | | | | and to make sure that we catch oversized arguments rather than silently truncate them. I dont know if sscanf will reject an integer if it will not fit in the short return variable or not, but this way it should be detected.
* style.Makefile: Add a '?' before '=' in WARNS.trhodes2003-10-261-1/+1
|
* Parse the ! lines that will soon be coming from the kernel. These areimp2003-10-245-10/+48
| | | | | | | | | | a generalized notification mechanism for subsystems wishing to report events. Revieded by: njl # The kernel side seems like it might be causing panics for me, but should # be forthcoming shortly.
* Switch Advanced Sockets API for IPv6 from RFC2292 to RFC3542ume2003-10-243-256/+263
| | | | | | | | | | (aka RFC2292bis). Though I believe this commit doesn't break backward compatibility againt existing binaries, it breaks backward compatibility of API. Now, the applications which use Advanced Sockets API such as telnet, ping6, mld6query and traceroute6 use RFC3542 API. Obtained from: KAME
* Fix several old bugs which got worse over time:trhodes2003-10-233-9/+10
| | | | | | | | | | o WARNS should be WARNS?= (broke in rev 1.21). o Includes should be sorted. o Move "mntopt.h" out of the standard includes section. o Rewrite usage() to match the manual page and make it < 80 characters. o Remove extra .El call on line 187. It is unused and causes mdoc(7) warnings. Discussed with: bde
* Move prototypes into their function.trhodes2003-10-221-3/+1
|
* Make WARNS=2 build without error.trhodes2003-10-222-2/+2
|
* Add back the commas ',' in usage to avoid a garbled usage message.trhodes2003-10-221-2/+2
| | | | They were erroneously removed in revision 1.27.
* Reduce fstab(5)/mount(8) confusion by changing the man pages to say "ro"seanc2003-10-222-4/+3
| | | | | instead of "rdonly". "rdonly" works for mount(8) and mount_std(8) but not from /etc/fstab, whereas "ro" works for all mount_*(8) commands.
* stop use of NI_WITHSCOPEID. it was deprecated.ume2003-10-211-6/+1
| | | | Obtained from: KAME
* Wrap a long line in the previous commitsilby2003-10-211-1/+2
| | | | Suggested by: njl
* Have sysctl print out a more useful error message when it detects that thesilby2003-10-211-1/+6
| | | | user has attempted to write to a read only, tunable value.
* Change the default mode for lost+found from 01777 to 0700. Theiedowse2003-10-191-1/+1
| | | | | | | | | | original intention of the less restrictive permissions was to allow users to move or delete recovered files that they own. However, it is better to not create world-writable directories by default; the administrator can always pre-create lost+found if different permissions are desired. Reviewed by: mckusick
* Only automatically create an 'a' partition when there is nothingphk2003-10-181-4/+22
| | | | but a 'c' partition.
* Make the regression test run also with obj directories.phk2003-10-172-2/+6
|
* - styleume2003-10-171-25/+28
| | | | | | | | - rename variable - use strlcpy - const'fy Obtained from: KAME
* Insert an overview of the plans here, in case I get run over by a bus.phk2003-10-131-0/+32
|
* - support AES counter mode for ESP.ume2003-10-132-0/+6
| | | | | | | | - use size_t as return type of schedlen(), as there's no error check needed. - clear key schedule buffer before freeing. Obtained from: KAME
* - support AES XCBC MAC for AHume2003-10-132-0/+3
| | | | | | - correct SADB_X_AALG_RIPEMD160HMAC to 8 Obtained from: KAME
* - RIPEMD160 supportume2003-10-122-0/+3
| | | | | | - pass size arg to ah->result (avoid assuming result buffer size) Obtained from: KAME
* Describe '-M' in usage().fjoe2003-10-111-5/+7
| | | | | PR: 57462 Submitted by: Ryuichiro Imura <imura@ryu16.org>
* correct unsafe use of realloc().ume2003-10-111-5/+5
| | | | Obtained from: KAME
* Add a full example of a file-backed disk creation, I used the Handbook'sblackend2003-10-111-0/+9
| | | | | | | example. PR: docs/51897 Submitted by: Kevin Oberman <oberman@es.net>
* s/disklabel/bsdlabel where needed.blackend2003-10-113-5/+5
|
* I think it is more correct to use modfind() than kldfind() here.phk2003-10-101-2/+2
|
OpenPOWER on IntegriCloud