summaryrefslogtreecommitdiffstats
path: root/sbin/bsdlabel
Commit message (Collapse)AuthorAgeFilesLines
* Only automatically create an 'a' partition when there is nothingphk2003-10-181-4/+22
| | | | but a 'c' partition.
* Remove the hardcoded default block/frag/cpg values from bsdlabeliedowse2003-10-051-44/+5
| | | | | | | | | and the logic for setting them according to the partition size. Instead, unspecified filesystem values are left at 0 so that newfs will use its own defaults. It just caused confusion to have the defaults duplicated in two different places. Reviewed by: phk
* mdoc(7): Properly mark C headers.ru2003-09-101-1/+1
|
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* When we initialize a disk with a virgin label, create also an 'a'phk2003-08-271-0/+4
| | | | | partition which starts after the bootstrap area and fills the entire disk.
* Augh! Fix the sparc64 build:phk2003-06-071-0/+8
| | | | | If we don't have a default label location for the compiled architecture, insist that a -m <architecture> option is specified.
* Sanitize setting of labeloffset and labelsector.phk2003-06-072-12/+5
|
* Give ia64 the exact same semantics as i386 with respect to non-512phk2003-06-041-1/+2
| | | | byte sector devices.
* Unbreak ia64. 'nuff said.marcel2003-06-041-0/+4
|
* Fix sectorsize != 512 on i386 and pc98. Add test cases for same.phk2003-06-022-21/+39
|
* Simplify the GEOM OAM api: Drop the request type, and let everythingphk2003-06-011-6/+6
| | | | | | | | hinge on the "verb" parameter which the class gets to interpret as it sees fit. Move the entire request into the kernel and move changed parameters back when done.
* Add pc98 arch to test set.phk2003-06-011-2/+2
| | | | Remove ktrace which leaked out of test-setup.
* Protext copyright[].obrien2003-05-311-3/+2
|
* mdoc(7) fixes.ru2003-05-241-19/+22
| | | | Approved by: re (blanket)
* Add amd64 to the MACHINE_ARCH list of systems that link bsdlabel topeter2003-05-231-1/+2
| | | | | | | | disklabel. I just got burnt again by having an old disklabel binary kicking around. Discussed with: phk Approved by: re (safe amd64 stuff)
* Style fixes.ru2003-05-171-13/+8
| | | | | Reviewed by: phk Approved by: re (scottl)
* 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
|
OpenPOWER on IntegriCloud