Skip to content

[dynparts] Upgrade initramfs to Debian trixie#46

Open
fredldotme wants to merge 4 commits into
dynpartsfrom
new-hotness
Open

[dynparts] Upgrade initramfs to Debian trixie#46
fredldotme wants to merge 4 commits into
dynpartsfrom
new-hotness

Conversation

@fredldotme

Copy link
Copy Markdown

Upgrade to trixie plus some modifications to go along with it.

…ce renaming

- Upgrade the created chroot to Debian trixie. And while we're at it, also point the
  UBports repo to 24.04-1.x, which is mostly compatible with trixie.
- Since stretch additional systemd-udevd network interface renaming files have appeared.
  Let's not take any chances and force-disable it using symlinks to /dev/null.
… telnet

"ifconfig" from the net-tools package is not shipped by default in trixie anymore,
but Busybox ships a CLI-compatible version of it. Use that instead.
The newer dmsetup in Debian trixie allows for the "create --concise" command to be used.
"parse-android-dynparts" from UBports' 24.04-1.x repo already returns a compatible
concise specification, to hook those two together.
@fredldotme fredldotme requested a review from NotKit March 27, 2026 19:04
@fredldotme

Copy link
Copy Markdown
Author

@NotKit care to take a look at this and the non-dynparts PR?

@NotKit

NotKit commented Apr 25, 2026

Copy link
Copy Markdown

@fredldotme there was a reason I had to revert to stretch on the dynparts branch earlier, as some devices failed to boot with the newer (buster?) base and it was a pain to debug. I think Droidian had similar problems, as they still keep stretch and then ship newer glibc and binaries separarely: https://github.com/droidian/initramfs-tools-halium

I'm not against updating the initramfs if it can be done, but it will need more testing per device. Maybe we should start just from the dynparts branch again to limit the impact, or the other way around?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants