| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
to fiddle the disk we can get away with it.
Try to use DIOCBSDBB to write boot code.
|
|
|
|
|
|
| |
back.
Pointed out by: peter
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
and if we get such an architecture, we can just avoid using the relevant
options.
|
|
|
|
| |
Remove yet a usage message about -N/-W
|
| |
|
|
|
|
| |
so no hacks are needed.
|
|
|
|
| |
Rearrange bits in writelabel() a bit for improved readability.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
ascii label; otherwise checklabel() might report spurious errors because
of leftovers from a previous pass.
Reviewed by: bde
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
the first label to the raw disk.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
userland, rather than expect all possible GEOMetries to know about
BSD disklabels.
Sponsored by: DARPA & NAI Labs
|
| |
|
|
|
|
| |
Also submitted by: David Wolfskill <david@catwhisker.org>
|
|
|
|
| |
definitions; fix some const strings; fix some signedness issues.
|
|
|
|
|
|
|
| |
changed a `goto' to a `continue' in revision 1.52, but it continued
the wrong loop.
Noticed by: bde
|
| |
|