| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [slx-dmsetup] Tweak service ordering, wait for HDDs | Simon Rettberg | 2025-04-09 | 1 | -1/+21 |
| | | |||||
| * | Fix dumb typo | Simon Rettberg | 2025-04-09 | 1 | -1/+1 |
| | | |||||
| * | [slx-dmsetup] Remove unreachable exit statements | Simon Rettberg | 2025-04-09 | 1 | -2/+0 |
| | | |||||
| * | [slx-dmsetup] Split dmsetup-slx-device into smaller services | Simon Rettberg | 2025-04-09 | 4 | -194/+146 |
| | | |||||
| * | Avoid loading dracut-lib.sh in several scripts | Simon Rettberg | 2025-04-02 | 1 | -9/+11 |
| | | |||||
| * | [slx-dmsetup] More robust error handling, more logging | Simon Rettberg | 2025-03-11 | 1 | -112/+179 |
| | | |||||
| * | [slx-dmsetup] Better not encrypt the rootfs AFTER building the CoW layer | Simon Rettberg | 2024-06-14 | 1 | -16/+14 |
| | | |||||
| * | [slx-dmsetup] Try to fix some snapshot brain damage | Simon Rettberg | 2024-06-14 | 1 | -10/+8 |
| | | | | | | | | create_snapshot was always using hard-coded $writable_device, but surrounding code at one callsite suggested it was expected to use $scratch_device - this would at least explain why we could end up with overlapping dm targets... -.- | ||||
| * | [slx-dmsetup] busybox mktemp needs AT LEAST 6 X -.- | Simon Rettberg | 2024-06-14 | 1 | -4/+6 |
| | | |||||
| * | [slx-dmsetup] Fix another busybox mktemp call | Simon Rettberg | 2024-06-14 | 1 | -1/+1 |
| | | |||||
| * | [slx-dmsetup] Fix braindead mktemp call by removing it | Simon Rettberg | 2024-06-13 | 1 | -4/+5 |
| | | |||||
| * | [slx-dmsetup] Kill stray line | Simon Rettberg | 2024-06-13 | 1 | -1/+0 |
| | | |||||
| * | [slx-dmsetup] Avoid unnecessary dm targets, rename crypted ones | Simon Rettberg | 2024-06-13 | 1 | -34/+72 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | 1) Avoid creating linear targets that would be fully covered by an encrypted target later. Also don't create a linear slice for the thinpool if it's going to be the only thing we put in our writable partition. 2) Previously, when we created an encrypted device, it would look like | ` devicename ` devicename-crypt Which was a bit confusing/surprising, because the final name was not what was specified in our custom partition table. Now, the result would look like | ` devicename-k ` devicename So the final device you'd use has the expected name. | ||||
| * | [slx-dmsetup] Make sure id44 slices are 4k-aligned | Simon Rettberg | 2024-03-01 | 1 | -4/+8 |
| | | |||||
| * | [slx-dmsetup] grow: Preserve exit status now that it's a service | Simon Rettberg | 2024-01-29 | 1 | -3/+2 |
| | | |||||
| * | Try to use more systemd services | Simon Rettberg | 2024-01-29 | 2 | -0/+839 |
 |
index : openslx-ng/systemd-init.git | |
| Systemd init mit dracut (Masterprojekt) | OpenSLX |
| summaryrefslogtreecommitdiffstats |