| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
in BUGS, as this is a feature.
Bump the date, as it was forgotten in previous commits and the
page has had significant changes recently
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
boot0.S changes:
+ import a patch from Christoph Mallon to rearrange the various
print functions and save another couple of bytes;
+ implement the suggestion in PR 70531 to enable booting from
any valid partition because even the extended partitions that
were previously in our kill list may contain a valid boot loader.
This simplifies the code and saves some bytes;
+ followwing up PR 127764, implement conditional code to preserve
the 'Volume ID' which might be used by other OS (NT, XP, Vista)
and is located at offset 0x1b8. This requires a relocation of the
parameter block within the boot sector -- there is no other
possible workaround.
To address this, boot0cfg has been updated to handle both
versions of the boot code;
+ slightly rearrange the strings printed in the menus to make
the code buildable with all options. Given the tight memory
budget, this means that with certain options we need to
shrink or remove certain labels.
and especially:
make -DVOLUME_LABEL -DPXE the default options.
This means that the newly built boot0 block will preserve the
Volume ID, and has the (hidden) option F6 to boot from INT18/PXE.
I think the extra functionality is well worth the change.
The most visible difference here is that the 'Default: ' string
now becomes 'Boot: ' (it can be reverted to the old value
but then we need to nuke 1/2 partition name or entries to
make up for the extra room).
boot0cfg changes:
+ modify the code to recognise the new boot0 structure (with the
relocated options block to make room for the Volume id).
+ add two options, '-i xxxx-xxxx' to set the volume ID, -e c
to modify the character printed in case of bad input
PR: 127764 70531
Submitted by: Christoph Mallon (portions)
MFC after: 4 weeks
|
|
|
|
| |
Pointed out by: ru
|
|
|
|
|
|
|
|
| |
- Add an example using fdisk instead
Pointed out by: ru
Submitted by: Warren Block <wblock@wonkity.com>
MFC after: 3 days
|
|
|
|
|
|
| |
PR: doc/111840
Submitted by: Warren Block <wblock@wonkity.com>
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
the mask correspond to slice numbers. Also, clarify the description of the
existing example.
Requested by: Larry Rosenman <ler@lerctr.org>
|
| |
|
|
|
|
|
|
|
| |
and examples of the "-s" option, since these two features operate
completely independently of each other.
Reviewed by: obrien
|
|
|
|
| |
So fix it, and add an example using -s.
|
|
|
|
|
| |
PR: 38015
Submitted by: Chris Pepper <pepper@mail.rockefeller.edu>
|
| |
|
| |
|
|
|
|
|
|
| |
boot0cfg(8): add FILES section.
Reviewed by: rnordier
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR: 20936
Originated by: obrien
|
|
|
|
|
|
|
| |
PR: 18923
Submitted by: Ian Dowse <iedowse@maths.tcd.ie>
Reviewed by: jhb
Approved by: rnordier
|
| |
|
| |
|
|
|
|
|
|
| |
(with care) in those instances where boot0 is not passed the
correct drive number by the PC BIOS. (The symptoms are a
"F5 Drive 0" line, even though the current drive is drive 0.)
|
| |
|
|
CLI utility to do this has been requested by a few people.
|