summaryrefslogtreecommitdiffstats
path: root/sbin/bsdlabel
Commit message (Collapse)AuthorAgeFilesLines
...
* Moved libgeom.so dependencies to where they belong.ru2003-05-171-2/+2
| | | | | Reviewed by: phk Approved by: re (scottl)
* Add pc98 archtecture entry.phk2003-05-131-0/+4
| | | | Approved by: re/rwatson
* Before reading an ascii label, initialize with defaults so thatphk2003-05-091-0/+1
| | | | | | getasciipartspec() has a sectorisize in case it needs one. Approved by: re/jhb
* Sigh, this shows just how much one can be conditioned my the environment:phk2003-05-091-9/+7
| | | | | | | | Just because we for the last ten years have fought for every byte in the boot code on i386, doesn't mean that other architectures could not actually have space to spare there. Remore debugging message.
* Compile bsdlabel on all platforms.phk2003-05-051-0/+10
| | | | | | | Install a link to the disklabel(8) name on i386 and alpha platforms. Leave old disklabel(8) sources intact but disconnected from the build for now.
* Add transparent handling of mbroffset for backwards compatibility.phk2003-05-041-1/+25
|
* More axe-work:phk2003-05-032-683/+192
| | | | | | | | | Hide all the historical fields of the label, unless people ask for them with -A, set them to intelligently chosen defaults otherwise. Distill the manual page to remove inaccuracies, misundertandings and obsolete information. It can probably still be done better but now at least it is not misinforming people.
* Some minor remodelling with a large axe.phk2003-05-031-279/+171
|
* Use new geom.ctl based OAM instead of ioctls.phk2003-05-032-95/+100
| | | | Various cleanup.
* bsd_disklabel_le_dec() takes an extra argument now.phk2003-05-021-1/+2
|
* Vastly simplify architecture handling: Use properties of label asphk2003-05-021-124/+19
| | | | | | | | recorded in global variables, rather than checks on the architecture. Drop horribly code to handle MBR/PC98's embedded in the BSD label area. If you need to have an MBR or PC98 on your disk, you should not overlap it with a BSDLABEL, if you don't need it, this code is nothing but trouble.
* Default the location to the compiled for architecture if no -m arg specified.phk2003-05-021-3/+9
|
* Add three global variables which contain the location, size and a flagphk2003-05-021-37/+20
| | | | | | | | | | | | for the alpha checksum, and set them depending on the specified architecture Don't look for disklabels every 16 bytes, look the only place they should be for the current architecture. Always read the label from the raw disk and decode it into struct disklabel rather than trust a cast from random addresses. When writing to the raw disk, encode the label properly.
* Pull in geom_bsd_enc.c from sys/geom to encode and decode our labels.phk2003-05-021-1/+3
|
* Remove the well-intentioned, but ill thought out check which prevents usphk2003-05-021-7/+0
| | | | | from dd(1)'ing the boot code off one drive and have bsdlabel write it on another.
* Update the test-script based on the sunlabel version, but put a for-loopphk2003-05-021-91/+151
| | | | in there to run over the various architectures.
* Add the beginning of a regression test.phk2003-04-182-0/+113
| | | | | | | So far it checks the overwrites of the BSD label inband (ie: dd if=/dev/ad0a of=/dev/ad2a). This excercises the geom::slice::hotspot code.
* First scrub of s/disklabel/bsdlabel/phk2003-04-183-28/+29
| | | | bsdlabel.5 deliberately exempted, its contents looks less than useful.
* Quick grammar fix.trhodes2003-04-171-2/+2
|
* Don't die of SIGSEGV on a missing fstype fieldyar2003-04-011-0/+4
| | | | | | in a saved disklabel file. MFC after: 1 week
* Small mdoc fixseanc2003-03-291-1/+1
|
* Teach disklabel(8) about different hardware architectures.ru2003-03-162-107/+227
| | | | | | | | | | This is aimed at creating floppies during cross-releases. For different endianness machines, a tool like bswapfs(8) is necessary to make the generated floppies readable on the target machine. While here, fixed unaligned access on Alphas. Tested on: i386, alpha
* Give this manpage a good overhaul, including the markup.ru2003-03-151-327/+398
| | | | | | | | | | | | | | | | | Notable changes: - Removed the "disktype" argument from the -B only synopsis form. This form doesn't touch the disk label, and doesn't use this argument. - Fixed the first example in the EXAMPLES section. Support for compatibility slices has been recently dropped from the GEOM kernels, and a bit later GEOM became standard. - Removed the buggy notion from rev. 1.37 that disklabel(8) may be used to define mount points; it cannot. Improve some DOS partition / FreeBSD slice wording. Among these, ``dangerously-dedicated slice'' was just a nonsense. ;-)
* Properly mark "auto" as a keyword.ru2003-03-141-7/+7
|
* Deal with vestiges of d_boot[01].ru2003-02-232-52/+12
|
* If we fail to open O_RDWR, try opening O_RDONLY, if we use ioctlsphk2003-01-261-0/+6
| | | | | | to fiddle the disk we can get away with it. Try to use DIOCBSDBB to write boot code.
* IA64 still needs to be able to run on MBR+BSD combination, so put disklabelphk2003-01-261-0/+1
| | | | | | back. Pointed out by: peter
* Drop the silly notion that i386 has two bootstrap files now that sys/bootphk2003-01-262-163/+35
| | | | | | | | creates a single file named just "boot". Apart from the fact that the option "-s" is now gone and that "-b" should be pointed at /boot/boot instead of /boot/boot1, this patch should be a no-op.
* Remove #if checks for NUMBOOT==0, it's not relevant for any architecturephk2003-01-261-30/+0
| | | | | and if we get such an architecture, we can just avoid using the relevant options.
* Offer better advice in #error.phk2003-01-261-5/+3
| | | | Remove yet a usage message about -N/-W
* Remove ia64 and powerpc #ifdefs: this is i386/pc98/alpha only code.phk2003-01-261-3/+3
|
* Remove #ifdef __sparc64__ code. GEOM uses native SUN labels on this arch,phk2003-01-261-59/+2
| | | | so no hacks are needed.
* Fix typo in last commit.phk2003-01-261-84/+87
| | | | Rearrange bits in writelabel() a bit for improved readability.
* Remember to remove -N and -W from usage.phk2003-01-261-2/+0
|
* Don't fiddle write-protect status of disklabel, it's a discontinued feature.phk2003-01-261-8/+0
|
* Retire the "-N" and "-W" options which implemented write-protectionphk2003-01-262-49/+3
| | | | | | | | | | | | | | | | | | | for the disklabel: This facility is OBE. First of all, we cannot sensibly implement this in a properly stacked environment. Second, if we did, it would confuse the heck out of users who wouldn't be able to "start from scratch" by dd(8)'ing /dev/zero onto /dev/da0. Third, the offered protection is not comprehensive: no other software would respect it. Fourth and finally, the disklabel is already protected against tampering if it controls open partitions. Uselessness of these options discussed with: peter
* Clear part_set, part_size_type and part_offset_type before parsing thedes2003-01-161-0/+3
| | | | | | | | ascii label; otherwise checklabel() might report spurious errors because of leftovers from a previous pass. Reviewed by: bde MFC after: 1 week
* Rename the dos_partition structure for pc98 to pc98_partition.nyan2003-01-041-1/+11
|
* mdoc(7) police: Deal with self-xrefs.ru2002-12-241-1/+1
|
* Uniformly refer to a file system as "file system".ru2002-12-121-1/+1
| | | | Approved by: re
* Relax partition overlap check to allow Vinum partitions to overlapgrog2002-12-021-3/+6
| | | | | | | | | | | | other partitiosns. This is necessary when migrating conventional partitions to Vinum and was broken by recent more stringent overlap checks. This is arguably the wrong way to do it. A better method would be to have the loader understand a subset of Vinum partitioning and allow an install directly to Vinum, but until then, this is the best we have. Reviewed by: jhb Approved by: re (rwatson)
* mdoc(7) police: Added missing markup bit.ru2002-11-251-1/+3
| | | | Approved by: re
* Everything in the disklabel is unsigned so make all the input routinesjulian2002-11-181-57/+52
| | | | | | | | | | | | take unsigned values. his allows one to label disk with the number of blocks > 31 bits (though less then 32 bits) e.g. # size offset fstype [fsize bsize bps/cpg] c: 3125755904 0 unused 0 0 # (Cyl. 0 - 194569*) d: 3125755840 64 unused 0 0 # (Cyl. 0*- 194569*) which is needd to test UFS2
* Document that write(2) et al can return EROFS for attempts to write theschweikh2002-10-101-1/+4
| | | | | | | | disk label area. PR: 43891 Submitted by: Diomidis D. Spinellis <dds@istlab.dmst.aueb.gr> MFC after: 3 days
* Fix to support pc98.nyan2002-10-081-0/+4
|
* Don't be noisy if DIOCWLABEL fails, it's probably because we're writingphk2002-10-051-2/+1
| | | | | | the first label to the raw disk. Sponsored by: DARPA & NAI Labs.
* Split MBR and PC98 on-disk sliceformats out from disklabel.h, step 1:phk2002-10-011-0/+1
| | | | | | | | | | | | | | | | Peter had repocopied sys/disklabel.h to sys/diskpc98.h and sys/diskmbr.h. These two new copies are still intact copies of disklabel.h and therefore protected by #ifndef _SYS_DISKLABEL_H_ so #including them in programs which already include <sys.disklabel.h> is currently a no-op. This commit adds a number of such #includes. Once I have verified that I have fixed all the places which need fixing, I will commit the updated versions of the three #include files. Sponsored by: DARPA & NAI Labs.
* Construct new disklabels based on the medias stated parameters inphk2002-09-201-20/+47
| | | | | | | userland, rather than expect all possible GEOMetries to know about BSD disklabels. Sponsored by: DARPA & NAI Labs
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-213-28/+28
|
* Fix more breakage due to FSTYPENAMES/DKTYPENAMES split.bmilekic2002-08-161-0/+1
| | | | Also submitted by: David Wolfskill <david@catwhisker.org>
OpenPOWER on IntegriCloud