| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
- While there, make error messages consistent with the rest.
Approved by: kib (mentor)
|
|
|
|
|
| |
PR: bin/127573
Submitted by: Eygene Ryabinkin
|
|
|
|
|
|
|
|
|
| |
duplication of code in fdisk and boot0cfg. Also make use of g_providername to
fix an issue with fdisk and boot0cfg not using the correct provider when
writing the MBR.
Reviewed by: phk
Approved by: pjd (mentor)
|
| |
|
|
|
|
| |
Submitted by: rpaulo (SoC2007 student)
|
|
|
|
|
|
|
|
| |
Now it is possible to do something like fdisk -p ad0 | fdisk -f - ad1.
PR: bin/110182
Submitted by: Jukka A. Ukkonen
MFC after: 1 month
|
|
|
|
| |
- Remove some historical notes about "future" decisions.
|
|
|
|
|
|
| |
: fdisk.c revision 1.74
: date: 2004/06/14 07:21:19; author: phk; state: Exp; lines: +3 -3
: Make fdisk initialize the first instead of the last slice by default.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sector size, instead of later failing with an error about /boot/mbr
not being a multiple of the sector size (since we end up with an
assumed sector size of MAX_SEC_SIZE * 2).
- We query the sector size via an IOCTL anyway, so if that succeeds
use that instead of probing for it via read(2) calls. This fixes
the problem with fdisk failing to operate on at least graid3 and
md(4) devices on kernels with src/sys/geom/geom_dev.c before
rev. 1.90, due to fdisk failing to detect the sector size.
- When detecting the root device allow "/" characters in it, which
happens with e.g. gmirror devices.
Reviewed by: cperciva
MFC after: 1 week
|
|
|
|
|
|
| |
PR: bin/84664
Submitted by: Daan Vreeken <Danovitsch at Vitsch dot net>
MFC after: 3 days
|
|
|
|
| |
This should solve the problem of modifying a busy MBR.
|
| |
|
| |
|
|
|
|
| |
the correct mode for our arguments.
|
|
|
|
| |
Submitted by: Lawrence.Lee@sun.com
|
|
|
|
| |
Reviewed by: jhb
|
| |
|
| |
|
|
|
|
| |
Use WARNS?= instead of WARNS=.
|
|
|
|
|
|
| |
(and perhaps earlier).
Submitted by: Joerg Schilling <schilling@fokus.fraunhofer.de>
|
|
|
|
|
|
| |
if the user agrees, move them out one track.
MFC after: 7 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Always set the magic sequence when we write, rather than trusting the
previously read boot code to do so.
Use explicit encoding/decoding of little endian disk image.
Remove a comment which was OBE.
Change the test vector for "fdisk -I" to reflect that there is a magic
sequence in the result now.
Add test case for "fdisk" which reads the image back.
At least for the two test-cases this program now gives the same result
on sparc64 as on i386. The lack of an installed /boot/mbr on sparc64
raises an (un)interesting question.
|
|
|
|
| |
Add a very simple regression test for "fdisk -I".
|
|
|
|
|
|
|
| |
512 for sectorsize.
63 for sectors.
255 for heads.
This will mostly show up on MD(4) devices.
|
|
|
|
| |
Add FreeBSD Id tag where missing.
|
| |
|
|
|
|
|
|
| |
root is on from the root mount path.
Spotted by: imp
|
|
|
|
| |
issues a useless warning now.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
| |
expecting a bogo-disklabel to contain them, if possible.
This makes fdisk work with GEOM.
|
| |
|
|
|
|
|
|
| |
(but not actual) alignment problems. Both of these bugs were detected
on ia64's and were fatal on ia64's due to premature setting of WARNS
to 4.
|
| |
|
|
|
|
|
| |
no /boot/mbr to read the boot code from (ia64 does not *have* bootblocks!).
fdisk depended on magic in the /boot/mbr file to initialize some fields.
|
|
|
|
| |
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
|
|
|
|
|
|
|
|
|
| |
s/partition/slice/ in fdisk.8
fix a bug in fdisk(8) where it did not honer -t when using -I
PR: 36563 and 35688
Submitted by: bde
Reviewed by: bde
|
|
|
|
| |
linelength.
|
|
|
|
|
| |
PR: i386/14793
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
of unused partition entries and later detection of unused entries.
Use memcpy to be consistent with the rest of the code, and fix a
minor style nit.
Submitted by: bde
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
| |
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pointed out by bde:
- Ask for user confirmation before adjusting to a head/cylinder
boundary (only when running interactively), and separate this
adjustment from the automatic calculation of c/h/s parameters.
- In sanitize_partition, don't change any values in the slice until
we know that the automatic adjustment will succeed.
- When auto-adjusting, ignore unused slices and give an appropriate
error for other zero-size slices depending on the cause.
- Change dos() to do all of the c/h/s calculations for a whole slice;
this fixes a bug where the ending c/h/s of an unused slice was set
incorrectly.
- When changing the active slice, detect the currently active slice
number instead of always defaulting to slice 4.
- Call fflush(stdout) before calling fgets().
- Test for fgets() returning NULL so we don't loop on EOF.
Reviewed by: bde
|
|
|
|
|
|
| |
boot0cfg(8): add FILES section.
Reviewed by: rnordier
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
device search code i introduce nearly six years ago in rev 1.8. Bruce
suggested to rather use the device name of the root filesystem instead
which is certainly the most sensible default. Since there are many
possible cases for a root filesystem name (device with and without
slices, consider /dev/vinum/root even though it currently could not
work as such), there's some heuristic using a RE in order to find out
the canonical device name from the mounted name. This probably won't
quite fit for a NFS root (can't test that right now), but then,
there's hard to find a good default for those machines anyway. ;-)
This unbreaks the functionality of rev 1.2 i once broke in 1.8. :)
|