| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Idea borrowed from disklabel. i.e. Users can now type "print M"
and be rewarded with partition sizes in Megs
|
|
Add a -u flag to fdisk which updates MBR code, but leaves the partition
table intact. There are still issues with 'update' having different behavior,
but I'll resolve those shortly
|
|
parameters editing) -- vassilip@dsl.cis.upenn.edu
|
|
|
|
bios valid cyl,head,sector information (the information comes from the
sd driver) I have made some changes to fdisk to do the following.
Allow the powerpc to specify values larger than the bios limits.
All platforms now have code that will translate the LBA values
in the mbr into CHS values according to the disk geometry.
This occurs if the start and ending CHS values have been stored as
0xffffff.
If writing to the disk and one of the values of a partition violates
the bios limits, it writes the requested values in the LBA fields ,
and stores 0xffffff for the starting and ending CHS values.
This should not change the default formatting of any existing system
other than the CHS and LBA values should always match given the detected
geometry of the disk.
|
|
MBR when doing a 'fdisk -i'. That is because the msdos partition is used
for booting. The OpenBSD part (part 3) is set up to be the rest of the
disk. Also the msdos partition is set as the 'active' partition.
|
|
|
|
absolute offset of the current mbr and its relative position. because:
the starting sector of the first mbr entry in an extended partition is relative
to the starting offset of the whole mbr itself. the starting offset of a new
extended partition is relative to the offset of the very first extended
partition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
editing code. Rewrite from the ground up, save about
20 lines of code. Seems to create valid partition
tables on i386 and alphas.
|
