forks/archiso/configs/releng/grub, branch custom_configFork of the official archiso scripts repositoryhttps://git.freethoughts.de/forks/archiso/atom?h=custom_config2024-04-19T10:45:04Zconfigs/: replace archisodevice boot parameter with archisosearchuuid2024-04-19T10:45:04Znl6720nl6720@gmail.com2024-04-05T10:33:45Zurn:sha1:43e4d9ce364a4776f6f8873dcfb1e53e86211feb
`archisosearchuuid=` first searches for a matching UUID. If that fails,
then it mounts and looks for a `/boot/${archisosearchuuid}.uuid` file in
all detected block devices (in whatever order `blkid` lists them).
This implements "file system transposition" without relaying on boot
loader specific features and does not tie us to GRUB anymore.
Related to https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio-archiso/-/merge_requests/48
Fixes https://gitlab.archlinux.org/archlinux/archiso/-/issues/217
configs/releng/: use mkinitcpio's microcode hook instead of external microcode images2024-04-19T07:53:42Znl6720nl6720@gmail.com2024-04-01T15:39:09Zurn:sha1:2facc4630cd3677e5c61705a25d5d5594fd0cc80
This simplifies boot loader configuration, but custom PXE setups will
be forced to update theirs.
Implements https://gitlab.archlinux.org/archlinux/archiso/-/issues/226
Add configs/*/grub/loopback.cfg2023-09-28T07:09:10Znl6720nl6720@gmail.com2023-01-26T13:51:23Zurn:sha1:4280af747466c4a7d37eabc6502c1ed697210db9
See https://www.supergrubdisk.org/wiki/Loopback.cfg for details.
Only `${iso_path}` is guaranteed, so we need to search for the volume,
on which the ISO file resides, ourselves.
Implements https://gitlab.archlinux.org/archlinux/archiso/-/issues/165
configs/*/grub/grub.cfg: do not hardcode the architecture and platform2023-09-28T07:08:36Znl6720nl6720@gmail.com2023-02-24T15:56:19Zurn:sha1:0cd0cc0c3b93e159451bca5cd880c7ca458cfb49
Construct a human readable platform identifier from GRUB's built-in
variables and use it in menu item descriptions.
Only add the menu entries for the additional tools (UEFI shell,
Memtest86+) if the files exist.
Modify baseline's `grub.cfg` to closer match releng.
configs/releng/grub/grub.cfg: play init tune at the end2023-09-28T07:08:36Znl6720nl6720@gmail.com2023-02-24T15:52:11Zurn:sha1:8fb5246de6e72d94008006066328d39f67649ad5
Move the `play` command to the end of the file so it plays after the
menu entries are shown and ready.
configs/*/grub/grub.cfg: rearrange module loading2023-09-28T07:08:36Znl6720nl6720@gmail.com2023-02-24T15:50:13Zurn:sha1:0a3a57a88bd55ce2396e685ab2cf0bde8359be9c
* Do not manually load modules that will get loaded by invoking a command.
* Explicitly load serial modules.
* Move `insmod all_video` after the font is loaded.
Added classes for Memtest86+ and UEFI Shell menuentries2023-05-14T15:10:02ZAntonio Vcrazysnob@live.it2023-05-14T15:10:02Zurn:sha1:751f6ed9baa787765fb10f1a23279d57c3ac0d23Use console as grub's terminal_output2023-02-27T18:31:45ZDavid Rungedvzrv@archlinux.org2023-02-27T18:31:45Zurn:sha1:8535d695ff6dadb1fd47973c083c9af4698b56fc
configs/{baseline,releng}/grub/grub.cfg:
Use `console` as grub's `terminal_output`, as with `gfxterm` only a blank screen is shown on some hardware.
Fixes #212
configs/*/grub/grub.cfg: replace /dev/disk/by-uuid/ with UUID=2023-02-24T09:41:14Znl6720nl6720@gmail.com2023-02-22T08:57:27Zurn:sha1:cedb3d142c470511ba1bb86fa987fd9bb39501d2
Use the shorter and more nicer looking `UUID=` *tags* instead of the
`/dev/disk/by-uuid/` paths.
This requires mkinitcpio-archiso v68.
Related to #202
Move the .uuid file to /boot/grub/YYYY-mm-dd-HH-MM-SS-00.uuid2023-02-24T08:22:41Znl6720nl6720@gmail.com2023-02-09T09:16:52Zurn:sha1:c8474f8dbe2df8fa9af11e4b3d0bde24bb8b54f9
To prevent the file from being accidentally missed when someone copies
the ISO's contents, let's not place it in a directory that starts with a
dot. Since all GRUB related files are in /boot/grub/, put it there too.
Instead of using a more unique UUID for the file name, use
`YYYY-mm-dd-HH-MM-SS-00.uuid` which matches the ISO's modification date
in UTC,i.e. its "UUID". If multiple ISOs would be generated in the exact
same second, the ISO 9660 modification date (i.e. its "UUID") would be
the same, so there would be not way to distinguish between the volumes
anyway. This also makes the file look less suspicious to the casual
glance.