| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
support for the T multiplier; improve the error message for unrecognized
multipliers.
|
|
|
|
| |
avoid confusing auto-indenting editors.
|
| |
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
|
|
|
| |
disk partitions.
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
but a 'c' partition.
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
| |
partition which starts after the bootstrap area and fills the entire
disk.
|
|
|
|
|
| |
If we don't have a default label location for the compiled architecture,
insist that a -m <architecture> option is specified.
|
| |
|
|
|
|
| |
byte sector devices.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Remove ktrace which leaked out of test-setup.
|
| |
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
| |
disklabel. I just got burnt again by having an old disklabel binary
kicking around.
Discussed with: phk
Approved by: re (safe amd64 stuff)
|
|
|
|
|
| |
Reviewed by: phk
Approved by: re (scottl)
|
|
|
|
|
| |
Reviewed by: phk
Approved by: re (scottl)
|
|
|
|
| |
Approved by: re/rwatson
|
|
|
|
|
|
| |
getasciipartspec() has a sectorisize in case it needs one.
Approved by: re/jhb
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Various cleanup.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
from dd(1)'ing the boot code off one drive and have bsdlabel write it
on another.
|
|
|
|
| |
in there to run over the various architectures.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
bsdlabel.5 deliberately exempted, its contents looks less than useful.
|
| |
|
|
|
|
|
|
| |
in a saved disklabel file.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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. ;-)
|