| #
545236f4 |
| 09-Apr-2024 |
nia <nia@NetBSD.org> |
Add new sets: base32, debug32, manhtml
- base32 contains (when MKCOMPAT=yes) shared libraries for 32-bit compatibility, previously included in base
- debug32 contains (when MKCOMPAT=yes) debug sy
Add new sets: base32, debug32, manhtml
- base32 contains (when MKCOMPAT=yes) shared libraries for 32-bit compatibility, previously included in base
- debug32 contains (when MKCOMPAT=yes) debug symbols and static libraries containing debug symbols for 32-bit compatiblity, previously included in debug
- manhtml contains (when MKHTML=yes) the HTML files previously included in 'man', which are of limited utility without third-party software.
The motivation for this change is to be able to easily exclude sets from CD-ROM images that go over the size limit without xz compression (which many NetBSD platforms struggle to extract at acceptable speeds).
show more ...
|
| #
f54624bd |
| 25-Sep-2021 |
maya <maya@NetBSD.org> |
Move DRM-driver firmware from base to its own set, gpufw
This set is only installed on amd64,i386,evbarm. This set is installed on minimal installs and on install media, in case someone needs it for
Move DRM-driver firmware from base to its own set, gpufw
This set is only installed on amd64,i386,evbarm. This set is installed on minimal installs and on install media, in case someone needs it for basic driver functionality.
Comments: Switched to a single MK tunable for it - that is probably unneeded.
An upcoming DRM update will include even fatter firmware, and we'd like to minimize the impact of it.
show more ...
|
| #
325b9996 |
| 05-Oct-2020 |
martin <martin@NetBSD.org> |
Add a heuristic to detect and properly mark EFI system partitions when re-using pre-existing partitions.
|
| #
2f0931af |
| 16-Nov-2019 |
martin <martin@NetBSD.org> |
On amd64 support installation with a KASLR kernel, via "custom install" and selecting the GENERIC_KASLR kernel set. Setup /prekern and boot.cfg accordingly.
|
| #
50f74585 |
| 02-Oct-2019 |
maya <maya@NetBSD.org> |
Split out /rescue to its own set and adapt installers/images to add it.
This is meant to make updates safer: if something goes wrong with updating base, we still have the old, standalone /rescue to
Split out /rescue to its own set and adapt installers/images to add it.
This is meant to make updates safer: if something goes wrong with updating base, we still have the old, standalone /rescue to recover from.
show more ...
|
| #
32ea71a6 |
| 14-Jul-2019 |
martin <martin@NetBSD.org> |
Work in progress UEFI boot support, don't try this at home yet!
|
| #
4103857b |
| 12-Jun-2019 |
martin <martin@NetBSD.org> |
Rework internal data structures and "interfaces to user interface" functions to get rid of all disklabel assumptions.
Previously (even for GPT partitioning) struct disklabel was used, which obviousl
Rework internal data structures and "interfaces to user interface" functions to get rid of all disklabel assumptions.
Previously (even for GPT partitioning) struct disklabel was used, which obviously breaks large disk setups. Also many MD parts and parts of the user interface assumed (a) a struct disklabel is used internally to store partitioning information and (b) partitions are named 'a' ... $MAXPART.
Get rid of this and replace it with a quite abstract interface that should be able to deal with all variants in partition storage:
- partitions are stored in a (partly abstract) struct disk_partitions and most parts of it are only accessed via accessor functions provided by a "partitioning scheme".
- implement partitioning schemes for MBR, disklabel and GPT (with likely RDB [amiga] and Apple Partition Map [mac*] to follow soon)
- partitioning schemes may be cascaded, e.g. on x86 when using MBR as "outer partitions", we have disklabel as "inner partitions".
- all user interface goes via accessor functions in the partitioning scheme, some of which return pointers to special user interface descriptors (e.g. to allow editing partition flags, which are scheme specific)
Overall the user interface changes (in this initial step) are minimal but noticable. A new Anita is needed for automatic test setups - many thanks to Andreas Gustafsson for lots of early testing and a new Anita version, and to Manuel Bouyer for cooperation and tests of the Anita release.
This work was sponsored by The NetBSD Foundation, Inc.
show more ...
|
| #
de7834a3 |
| 18-Nov-2018 |
martin <martin@NetBSD.org> |
More size estimate fixes
|
| #
7a391039 |
| 05-Nov-2018 |
martin <martin@NetBSD.org> |
Get rid of hard coded disk names and use sysctl hw.disknames instead.
|
| #
7935b6fc |
| 14-Nov-2015 |
pgoyette <pgoyette@NetBSD.org> |
Enable installation of amd64 on an lfsv2 partition.
XXX Other ports will need similar changes to arch/.../md.h after testing!
XXX The mount_lfs warning about lfs being experimental may confuse or X
Enable installation of amd64 on an lfsv2 partition.
XXX Other ports will need similar changes to arch/.../md.h after testing!
XXX The mount_lfs warning about lfs being experimental may confuse or XXX corrupt the sysinst display window.
show more ...
|
| #
50dbef1a |
| 26-Jul-2014 |
dholland <dholland@NetBSD.org> |
Move sysinst sources to usr.sbin.
This commit only physically moves the sources - there are no other changes, to maximize the probability that this will be treated as a rename if we ever do manage t
Move sysinst sources to usr.sbin.
This commit only physically moves the sources - there are no other changes, to maximize the probability that this will be treated as a rename if we ever do manage to migrate away from CVS.
Moving sysinst has been discussed on and off for years and has two goals: making it easier to work on sysinst, and also making sysinst available on running systems for use installing chroots and VM images and other such things. None of the latter is possible yet, but as they say, one thing at a time.
Doing this now was approved in an impromptu fashion by mrg, riz, riastradh, me, and groo.
show more ...
|