openrc/modloop.initd.readme


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55


Fri 17 Jan 2025 12:19:32 AM EST

This is in continuation of issue #16843.

This modification to modloop.initd now allows mounting of squashfs firmware from 
modloop-lts.d directory, onto /.modloop/modules/firmware/<folder>, after modoop-lts has been mounted.

Eg. linux-firmware-intel-20241210-r0.apk can be made into squashfs and mounted on /.modloop/modules/firmware/intel.

Code for rsa.sign.keys and verification has been left-out.
Also not included is code for splitting and creating modloop-lts.firmware.<dir> files,

1. Link: [https://git.insteps.net/mess/aportsbag/tree/openrc/modloop.initd]

Why do this?
1. This will further allow add/remove firmwares based on folder or brand.

----

Thu 16 Jan 2025 05:26:59 AM EST

Modification to modloop.initd now allows mounting of modloop-lts.firmware file
onto /.modloop/modules/firmware/ directory, after modoop-lts has been mounted.

Not quite familiar with verification of modloop-lts and code/files relating it.
I have added and commented some lines which likely should be enabled when proper verification 
code(rsa.sign.keys) is generated and related code changed.
Also not included is code for splitting and creating modloop-lts.firmware file.

Why do this?
1. Once users figures out all the firmwares needed for their target device, using overlay method
(see below), can then create squashfs from it and save space.
2. Users can download full firmware from upstream and squashfs it and create a universal boot disk.
3. Will relieve Alpinelinux devs from firmware requests.

----

Tue 14 Jan 2025 09:14:48 PM EST

modloop initd scripts allows firmwares to be loaded from boot medias' /firmware directory.
This is helpful, but that means having to know all the firmwares for the given device and
 copying onto /firmware folder. This can be improved if a script can figure all the needed
 ones and create/print a list.

Feature asked below modifies the exiting modloop overlay functionalities and copys' /firmware
 onto it. Now, I only need to have other needed firmwares in /firmware directory.

I am not aware if modloop overlay is meant for to be used in some other way, having
 it documented would be nice.

Hope this explains the need. The idea is some-what implemented in POC scripts
 (find attached below)