|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1 |
|
| #
7d89978d |
| 14-Feb-2020 |
Sascha Wildner <saw@online.de> |
Use our new partition id (0x6c) in several more places.
Mainly, adjust the USB img's own ID and use it in the installer's
legacy BIOS install.
While here, adjust DragonFly BSD's name in a few place
Use our new partition id (0x6c) in several more places.
Mainly, adjust the USB img's own ID and use it in the installer's
legacy BIOS install.
While here, adjust DragonFly BSD's name in a few places (written with
a space).
Reported-by: zrj
show more ...
|
|
Revision tags: v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5 |
|
| #
059599af |
| 11-Mar-2015 |
Matthew Dillon <dillon@apollo.backplane.com> |
gpt - Bump size of the boot partition from 768MB to 1GB
* Bump the default size of the boot partition to 1GB.
|
|
Revision tags: v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
| #
d342e161 |
| 18-Dec-2011 |
François Tigeot <ftigeot@wolfpond.org> |
gpt(8): increase size of boot slice to 768MB
* aligning it to the size of the boot slice created by the
live cd installer
|
| #
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.
|
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
| #
b9016d53 |
| 21-Aug-2008 |
Thomas Nikolajsen <thomas@dragonflybsd.org> |
Update gpt:
- note that DragonFly supports 32 slices per disk
- increase size of boot slice (slice 0 made by boot command):
increase size from 128MB til 256MB, as total size of
kernel & modules w/
Update gpt:
- note that DragonFly supports 32 slices per disk
- increase size of boot slice (slice 0 made by boot command):
increase size from 128MB til 256MB, as total size of
kernel & modules w/ .old is over 128MB and
it is a hassle to increase size of boot slice later
- add note that boot0 boot manager, which can be manipulated by
boot0cfg command, is used by boot command
- add example of GPT boot disk setup
- improve mark up a bit
show more ...
|
| #
210143e4 |
| 30-Jul-2008 |
Matthew Dillon <dillon@dragonflybsd.org> |
Add a terrible hack to GPT which allows non-EFI BIOSes to boot from it.
With a freshly made gpt on a disk you can run 'gpt boot da0' (specifying
the correct whole-disk name) and GPT will do the follo
Add a terrible hack to GPT which allows non-EFI BIOSes to boot from it.
With a freshly made gpt on a disk you can run 'gpt boot da0' (specifying
the correct whole-disk name) and GPT will do the following:
* It will create a 100MB partition #0 in the GPT
* It will fake up a slice 1 in the PMBR for the BIOS and the loader that
aliases partition #0 in the GPT.
The BIOS and loader will see a bootable slice 1 while the kernel, once
booted, will see a GPT. This can cause confusion because the kernel
will NOT see the fake slice 1 any more, and the partition number in the
GPT of the boot partition 0 (aka da0s0).
The boot partition (da0s0 from the point of view of the kernel) needs
to have a 32 bit disklabel and a UFS filesystem in da0s0a which contains
the kernel image and boot sub-directory. In the boot sub-directory the
loader.conf file must contain a line that points to the root mount, which
say you may have created with gpt add as partition #1.
Older kernels may require the root mount to also be in a disklabel, so you
might have to put a 32 or 64 bit disklabel in partition #1 as well.
This requirement will be removed soon relative to this commit (since the
idea with GPT is to not have to use disklabels).
vfs.root.mountfrom="ufs:ad0s1a"
vfs.root.mountfrom="ufs:ad0s1"
show more ...
|