IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
If the ISO image has a FAT partition and the image is written
to a flash drive, then it is possible to write to this partition
of the flash drive.
This is necessary, for example, if the user
does not want to install the system, but wants to constantly work
in LiveCD mode with or without recording sessions.
In order for this code to work, you need to make changes
to the FAT partition of the image on the flash drive:
Add the 1st line to the grub.cfg file:
set pfxfat=${prefix}
Write a 1kb file grubenv.
If grub.cfg contains a line like '^default=id',
then the read value is not used.
This prepares the ability to write and read
the default menu item from the grubenv file.
If grub.cfg contains a line like '^default=id',
then the read value is not used.
Setting the default menu item from the grubenv file
will be indented inside the 'if' optator and therefore
does not match the '^default' pattern.
Previously, you had to specify two parameters MKIMAGE_PREFIX and
GLOBAL_PREFIX with the same value - the path to mkimage. And this
behavior has not been documented. The GLOBAL_PREFIX variable is
defined in mkimage in config.mk and rules.mk.
Since we are now using fuuid, it doesn't depend on mkimage version.
But it depends on the propagator version.
Needed propagator >= 20210329-alt1
See-also: commit 52e90c264d
As new exfat filesystem is merged into linux-5.7 kernel, exfatprogs is
created as an official userspace utilities that contain all of the standard
utilities for creating and fixing and debugging exfat filesystem in linux
system.
std-def kernel in Sisyphus 5.10.
Wrote that it's a bashism myself and neglected
to specify the proper shell, sigh.
This SHELL manipulation could ruin tracing
piggybacked onto it within lib/report.mk
but it's too late at this stage anyways.
The first half of both pipes was clearly a copy-pasted
initial logfile processing; the file can be of considerable
size (e.g. several megabytes) so it might be slightly more
efficient and cool (but a bit more arcane) to use bash(1)'s
process substitution along with good ol' tee(1) like this:
$ echo -e '1\n2\n3' |tee /dev/stderr 2> >(grep 2 >STDERR) |grep 1 >STDOUT
$ head STD*
==> STDERR <==
2
==> STDOUT <==
1
That "clever hack" with two rev(1) invocations
seems pretty stupid to me: too much processes
and processing instead of simple prefix removal.
One can also have that as ${var##*/} when dealing
with a shell variable and avoiding extra forks, BTW.
plymouth might better be used through the corresponding feature
(it's the single place to know how it performs on various arches),
and some other packages are just missing.
The missing glob resulted in disk images properly
partitioned only for e2kv3 ("e2k" for historical
reasons in ALT), and v4+ ones only got a single
ext4 partition that wouldn't work with current
MCST's Boot code.
