summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* Allow classes to specify local source files.pjd2005-04-071-2/+2
| | | | MFC after: 3 weeks
* Empty error buffer is not an error.pjd2005-04-071-1/+1
| | | | MFC after: 3 weeks
* Document the configuration files used.jcamou2005-04-051-0/+3
| | | | | | PR: docs/79572 Submitted by: Josh Paetzel <josh@tcbug.org> Approved by: trhodes (mentor)
* Be more specific when complaining about bit masks.brooks2005-04-051-2/+2
|
* Remove debug from last commitimp2005-04-031-2/+0
|
* /*-imp2005-04-031-1/+1
|
* Don't define FS_DEBUG by default, as this causes growfs to write debuggingrwatson2005-03-311-1/+0
| | | | | | | information to /tmp/growfs.debug, which is a world-writable directory. MFC after: 3 days Reported by: Jon Passki <cykyc@yahoo.com>
* Don't default to '/var/tmp/ffsinfo' for the output of ffsinfo(8), sincerwatson2005-03-312-8/+8
| | | | | | | /var/tmp is a world-writable directory. MFC after: 3 days Reported by: Jon Passki <cykyc@yahoo.com>
* Fix grammar error caused by my previous edit.joerg2005-03-301-2/+2
| | | | | | While being here, also update the copyright year. Submitted by: ru
* This is the much rumoured ATA mkIII update that I've been working on.sos2005-03-301-14/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | o ATA is now fully newbus'd and split into modules. This means that on a modern system you just load "atapci and ata" to get the base support, and then one or more of the device subdrivers "atadisk atapicd atapifd atapist ataraid". All can be loaded/unloaded anytime, but for obvious reasons you dont want to unload atadisk when you have mounted filesystems. o The device identify part of the probe has been rewritten to fix the problems with odd devices the old had, and to try to remove so of the long delays some HW could provoke. Also probing is done without the need for interrupts, making earlier probing possible. o SATA devices can be hot inserted/removed and devices will be created/ removed in /dev accordingly. NOTE: only supported on controllers that has this feature: Promise and Silicon Image for now. On other controllers the usual atacontrol detach/attach dance is still needed. o Support for "atomic" composite ATA requests used for RAID. o ATA RAID support has been rewritten and and now supports these metadata formats: "Adaptec HostRAID" "Highpoint V2 RocketRAID" "Highpoint V3 RocketRAID" "Intel MatrixRAID" "Integrated Technology Express" "LSILogic V2 MegaRAID" "LSILogic V3 MegaRAID" "Promise FastTrak" "Silicon Image Medley" "FreeBSD PseudoRAID" o Update the ioctl API to match new RAID levels etc. o Update atacontrol to know about the new RAID levels etc NOTE: you need to recompile atacontrol with the new sys/ata.h, make world will take care of that. NOTE2: that rebuild is done differently from the old system as the rebuild is now done piggybacked on read requests to the array, so atacontrol simply starts a background "dd" to rebuild the array. o The reinit code has been worked over to be much more robust. o The timeout code has been overhauled for races. o Support of new chipsets. o Lots of fixes for bugs found while doing the modulerization and reviewing the old code. Missing or changed features from current ATA: o atapi-cd no longer has support for ATAPI changers. Todays its much cheaper and alot faster to copy those CD images to disk and serve them from there. Besides they dont seem to be made anymore, maybe for that exact reason. o ATA RAID can only read metadata from all the above metadata formats, not write all of them (Promise and Highpoint V2 so far). This means that arrays can be picked up from the BIOS, but they cannot be created from FreeBSD. There is more to it than just the missing write metadata support, those formats are not unique to a given controller like Promise and Highpoint formats, instead they exist for several types, and even worse, some controllers can have different formats and its impossible to tell which one. The outcome is that we cannot reliably create the metadata of those formats and be sure the controller BIOS will understand it. However write support is needed to update/fail/rebuild the arrays properly so it sits fairly high on the TODO list. o So far atapicam is not supported with these changes. When/if this will change is up to the maintainer of atapi-cam so go there for questions. HW donated by: Webveveriet AS HW donated by: Frode Nordahl HW donated by: Yahoo! HW donated by: Sentex Patience by: Vife and my boys (and even the cats)
* Support VTOC volume names. This can be useful to distinguish multiplejoerg2005-03-302-6/+59
| | | | | | | disks in a system. Solaris' format(1m) displays the volume names in the disk overview. MFC after: 1 month
* Initialize iovlen variable to 0 before passing it by reference to thekan2005-03-281-0/+1
| | | | | | build_iovec function. Tripped over by: Craig Rodrigues
* Add "report only" functionality to 'camcontrol format', so users can get aken2005-03-262-5/+20
| | | | | | | | | | report on the status of a format already running on a drive. Fix status reporting for 'camcontrol format'. This was broken in rev 1.34 of camcontrol.c, almost 4 years ago! Submitted by: joerg (most of the reportonly changes) MFC after: 3 days
* When executing mount_foo, pass "mount_foo" as argv[0] instead of "foo".cperciva2005-03-261-2/+4
| | | | | | | | This unbreaks "/rescue/mount -t foo" -- previously it was necessary to explicitly call "/rescue/mount_foo". Hints from: gordon X-MFC after: 3 days (if approved by re@)
* Remove bogus (but harmless) -I.. from CFLAGS. It makes no difference tobrooks2005-03-251-2/+1
| | | | | | | | | | .depends other then the commant line. Also remove -g from CFLAGS. The user should add it to CFLAGS if they desire debug support. Reviewed by: ru (in concept) MFC After: 7 days
* Revert bogus += -g change. I needed it to debug the problem.imp2005-03-251-1/+0
| | | | Noticed by: njl, Andrej Tobola
* Restore the ability to read FreeBSD 1 tapes (and I think any net2imp2005-03-253-0/+24
| | | | | | | | | | | | | | | based tapes, but I'm not sure where NFS_MAGIC was introduced after 4.3). When support for the pre-4.4 format was removed (the ability to read 4.2 and 4.3 BSD tapes), the old format inode conversion was junked as well. However, FreeBSD 1 dump tapes use the NFS_MAGIC format, but have this inode format. Before, restore would fail complaining that '.' wasn't found and the root directory wasn't on this tape. Since the conversion from the not so old format is relatively trivial, restore the code to make that conversion. FreeBSD 1 dumps are once again readable. MFC After: a few days
* dcvt is unused since the support for converting pre-4.4 tapes wasimp2005-03-252-25/+3
| | | | | | | removed. Go ahead and remove it and struct odirent since it too is unused. # FreeBSD 1.1.5 tapes are still unreadable, but 2.0 and newer work.
* c_tapea and c_firstrec are used for TS_TAPE blocks, so convert themimp2005-03-251-0/+2
| | | | | | | | | for the old (4.4-lite through FreeBSD 4.x and *BSD) format. It looks like they aren't used for TS_INODE, but conversion costs so little there that I've not removed them there (in case my grep was wrong). This makes at least some of the tapes work for me again. Now, to regresion test all my dusty tapes...
* Add verbiage to the description of the noexec mount option clarifyingcperciva2005-03-231-0/+5
| | | | | | | that it really wasn't intended as a security feature. Wording mostly by: simon Discussed with: secteam
* Fix use of uninitialized buf[0].pjd2005-03-221-2/+2
| | | | | Reported by: stefanf MFC after: 3 days
* Truncate nextboot.conf file on creation, so existing garbage will be removed.pjd2005-03-211-1/+2
| | | | | | Submitted by: Gary Allan <dragonfly@gallan.plus.com> Obtained from: DragonFlyBSD MFC after: 3 days
* Xref carp(4) and polling(4).brueffer2005-03-191-0/+2
| | | | MFC after: 3 days
* In order to print out the dump dates correctly, the date and ddate fieldsimp2005-03-181-0/+4
| | | | also need to be convereted for old tapes for records of type TAPE.
* Typo.phk2005-03-181-1/+1
| | | | Submitted by: Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp>
* Sync usage and man page with reality. There's no '-c' command lineimp2005-03-182-19/+10
| | | | | flag today. Maybe we should still retain it, but I'll let others fight that windmill.
* Forgot to change the pointer to the snmp_atm sources after repo-copy.harti2005-03-151-1/+1
| | | | | | | | Correct this by pointing to the new location. Pointy hat to: harti Submitted by: keramida
* Be sure that class name storaed in 'class_name' is lower case.pjd2005-03-141-0/+3
| | | | MFC after: 1 week
* Define subcommands' usage inside g_command structure.pjd2005-03-147-141/+109
| | | | MFC after: 1 week
* - Add gc_usage field to g_command structure. This will allow to definepjd2005-03-142-56/+52
| | | | | | | | | | | | usage for a subcommand, so no 'usage' function has to be implemented in class library. - Bump version number as it breaks ABI, but don't provide backward compatibility, because there are probably no external consumers of this geom(8). This allows to print more precise usage for standard commands and simplify class libraries a bit. MFC after: 1 week
* Instead of documenting every standard subcommand's argument everywhere,pjd2005-03-147-98/+56
| | | | | | just leave reference to geom(8). MFC after: 1 week
* Document subcommands' arguments.pjd2005-03-141-2/+18
| | | | MFC after: 1 week
* Document '-s' option of 'status' subcommand.pjd2005-03-141-0/+6
| | | | MFC after: 1 week
* Add '-s' option to 'status' subcommand. It produces script-friendly output:pjd2005-03-141-26/+50
| | | | | | | | | | | | | | | | | | | # gmirror status Name Status Components mirror/root COMPLETE ad0s1a ad2s1a mirror/data DEGRADED da0 da1 (76%) da2 # gmirror status -s Name Status Components mirror/root COMPLETE ad0s1a mirror/root COMPLETE ad2s1a mirror/data DEGRADED da0 mirror/data DEGRADED da1 (76%) mirror/data DEGRADED da2 MFC after: 1 week
* Use int instead of size_t (%*s needs int).pjd2005-03-141-9/+9
| | | | MFC after: 1 week
* printf(3) expects that %*s having an int parameter, which generatesdelphij2005-03-141-5/+5
| | | | | | | warning on 64-bit platforms. Explicitly cast these values to int to work around this issue, as these values are tend to be small. Spotted by: ia64 tinderbox
* - Document 'status' subcommand.pjd2005-03-138-17/+68
| | | | | | - Update copyrights. MFC after: 1 week
* Add 'status' command which prints general information about devices.pjd2005-03-131-0/+176
| | | | | | | | | | | | | | For example: # gmirror status Name Status Components mirror/root COMPLETE ad0s1a ad2s1a mirror/data DEGRADED da0 da1 (76%) da2 MFC after: 1 week
* Update copyrights.pjd2005-03-131-1/+1
|
* Change function names related to 'list' command from 'show_one_*' topjd2005-03-131-7/+7
| | | | | | 'list_one_*'. MFC after: 1 week
* 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
OpenPOWER on IntegriCloud