| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
The is comment is left over from the old disklabel command.
Reviewed by: phk
Notes:
svn path=/head/; revision=177517
|
|
|
|
|
|
|
|
| |
by virtue of there not being any (lower-case) letters avaliable for
more partitions.
Notes:
svn path=/head/; revision=174501
|
|
|
|
|
|
|
|
|
| |
PR: bin/104616
Submitted by: Oliver Fromme
MFC after: 1 week
Notes:
svn path=/head/; revision=163539
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to take into account the new default of starting the first partition
after the boot blocks instead of at sector 0. If you used automatic
sizing when the first partition did not start at 0, you would get
an error that the automatically sized partition extended beyond the
end of the disk.
Note that there are probably still many more complex cases where
automatic sizing and placement will not work (e.g. non-contiguous
or out of order partitions).
Notes:
svn path=/head/; revision=149061
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
complementing the existing special case of a not existing /dev prefix
with the recognition of an already existing /dev prefix.
This implicitly solves the following two issues related to working on
GEOM devices /dev/foo/bar (which have the GEOM provider name "foo/bar")
with the expected commands like "bsdlabel /dev/foo/bar":
1. the error "Geom not found" when trying to write or edit the BSD
label (because previously the incorrect GEOM name "bar" instead of
"foo/bar" was derived from "/dev/foo/bar").
2. the multiple times reported "magically introduced" partition offset
of 63 blocks and the resulting errors like "partition extends past
end of unit" and "partition c doesn't start at 0!".
This implicitly resulted because bsdlabel(8) determines the "MBR
offset" via GEOM and (intentionally) silently falls back to an offset
of 0 if it could not be queried (which is the case if the name was
incorrectly derived).
Usually (at least on PCs) the offset for the first slice is 63 blocks
and bsdlabel(8) automatically subtracts them from the absolute
offsets in the read on-disk BSD label, resulting in the display of an
effective offset of 0. If the GEOM query fails, the assumed offset of
0 is subtracted and an incorrect effective offset of 63 is displayed
and tried to be worked upon.
Reviewed by: pjd
MFC after: 1 week
Notes:
svn path=/head/; revision=139856
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
0xffffffff sectors. Document this limit and avoid installing bogus
labels on disks with more sectors.
Allowing the installation of labels addressing as much of the disk as
possiable may be a useful addition in some situations, but this was easy
to implement and should reduce confusion.
PR: bin/71408
Notes:
svn path=/head/; revision=134973
|
|
|
|
| |
Notes:
svn path=/head/; revision=133384
|
|
|
|
|
|
|
|
| |
support for the T multiplier; improve the error message for unrecognized
multipliers.
Notes:
svn path=/head/; revision=133348
|
|
|
|
|
|
|
| |
avoid confusing auto-indenting editors.
Notes:
svn path=/head/; revision=133347
|
|
|
|
|
|
|
| |
disk partitions.
Notes:
svn path=/head/; revision=127650
|
|
|
|
|
|
|
|
|
|
|
| |
length, and flags fields at the end of the SRM boot sector so that SRM can
find the bootstrap code. This fixes bsdlabel -m alpha to generate bootable
disklabels.
Reviewed by: phk
Notes:
svn path=/head/; revision=127044
|
|
|
|
|
|
|
| |
but a 'c' partition.
Notes:
svn path=/head/; revision=121222
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=120821
|
|
|
|
|
|
|
|
| |
partition which starts after the bootstrap area and fills the entire
disk.
Notes:
svn path=/head/; revision=119510
|
|
|
|
|
|
|
|
| |
If we don't have a default label location for the compiled architecture,
insist that a -m <architecture> option is specified.
Notes:
svn path=/head/; revision=115995
|
|
|
|
| |
Notes:
svn path=/head/; revision=115948
|
|
|
|
|
|
|
| |
byte sector devices.
Notes:
svn path=/head/; revision=115809
|
|
|
|
| |
Notes:
svn path=/head/; revision=115794
|
|
|
|
| |
Notes:
svn path=/head/; revision=115696
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=115624
|
|
|
|
| |
Notes:
svn path=/head/; revision=115449
|
|
|
|
|
|
|
| |
Approved by: re/rwatson
Notes:
svn path=/head/; revision=114982
|
|
|
|
|
|
|
|
|
| |
getasciipartspec() has a sectorisize in case it needs one.
Approved by: re/jhb
Notes:
svn path=/head/; revision=114862
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=114860
|
|
|
|
| |
Notes:
svn path=/head/; revision=114673
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=114574
|
|
|
|
| |
Notes:
svn path=/head/; revision=114571
|
|
|
|
|
|
|
| |
Various cleanup.
Notes:
svn path=/head/; revision=114569
|
|
|
|
| |
Notes:
svn path=/head/; revision=114557
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=114552
|
|
|
|
| |
Notes:
svn path=/head/; revision=114551
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=114550
|
|
|
|
|
|
|
|
| |
from dd(1)'ing the boot code off one drive and have bsdlabel write it
on another.
Notes:
svn path=/head/; revision=114545
|
|
|
|
|
|
|
| |
bsdlabel.5 deliberately exempted, its contents looks less than useful.
Notes:
svn path=/head/; revision=113680
|
|
|
|
|
|
|
|
|
| |
in a saved disklabel file.
MFC after: 1 week
Notes:
svn path=/head/; revision=112945
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=112307
|
|
|
|
| |
Notes:
svn path=/head/; revision=111286
|
|
|
|
|
|
|
|
|
| |
to fiddle the disk we can get away with it.
Try to use DIOCBSDBB to write boot code.
Notes:
svn path=/head/; revision=109901
|
|
|
|
|
|
|
|
|
| |
back.
Pointed out by: peter
Notes:
svn path=/head/; revision=109891
|
|
|
|
|
|
|
|
|
|
|
| |
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.
Notes:
svn path=/head/; revision=109889
|
|
|
|
|
|
|
|
| |
and if we get such an architecture, we can just avoid using the relevant
options.
Notes:
svn path=/head/; revision=109887
|
|
|
|
|
|
|
| |
Remove yet a usage message about -N/-W
Notes:
svn path=/head/; revision=109884
|
|
|
|
| |
Notes:
svn path=/head/; revision=109882
|
|
|
|
|
|
|
| |
so no hacks are needed.
Notes:
svn path=/head/; revision=109879
|
|
|
|
|
|
|
| |
Rearrange bits in writelabel() a bit for improved readability.
Notes:
svn path=/head/; revision=109878
|
|
|
|
| |
Notes:
svn path=/head/; revision=109875
|
|
|
|
| |
Notes:
svn path=/head/; revision=109874
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/head/; revision=109872
|
|
|
|
|
|
|
|
|
|
|
| |
ascii label; otherwise checklabel() might report spurious errors because
of leftovers from a previous pass.
Reviewed by: bde
MFC after: 1 week
Notes:
svn path=/head/; revision=109378
|
|
|
|
| |
Notes:
svn path=/head/; revision=108650
|