I’d be very careful with doing that. Imagine installation is aborted either via hardware failure or because the user pressed ctrl+c at the wrong time. Then you might have an updated extlinux.conf but the kernel isn’t working yet. Also, how do you handle the version? What do you do when there are multiple kernels installed at the same time? All of this can be solved by extlinux.conf being generated dynamically after kernel installation is complete and then being replaced atomically. In Debian, the package u-boot-menu does that job in case you want to have a look.
No. There are classic Reforms with imx8mq that do not support it but none of the newer models.
I should have been more clear. What I really meant was should I skip generating boot.scr entirely in exchange for generating extlinux.conf and it seems like yes. I’ll definitely generate it dynamically
I am going to try and make this a proper void package, but I don’t understand how debian packages work. Is there an easy way for me to see what commands are being run to build this package? I mostly just need to know what files get installed where
The magic for dkms packages in not in the build process. The “binary” package only contains source code. The real magic happens on the user’s computer when that source code is then compiled into a module at installation time.
Yeah, I don’t have all of the tools working yet. I need to make some PRs into the repo to add stuff for runit/dracut. I can absolutely help you get a running system, it’s just not a clean process just yet.
reform-standby needs to run before suspend and after resume
Note also, that soon the reform-tools repository will not have a ./debian subdirectory anymore but will come without one and then be a normal upstream project that each distro can source from and customize as they usually do. This will happen once the reform-tools package has been accepted by ftp-master: Debian NEW and BYHAND Packages
Note, that currently, the reform-tools package depends on systemd. It does not depend on systemd-sysv so it does not prohibit you from installing reform-tools on a system without systemd as init system.
In any case: I’m not married to systemd. If you send patches, other init systems will be supported as well.
You’ll have a hard time getting JWM running on a pocket reform. It looks like it depends on X11 and I couldn’t get X11 working well on my pocket reform. After some very light research, I saw some talk about X11 needing to be patched to work correctly with the imx8mp’s graphics driver (etnaviv I believe). I gave up and switched to Wayland at that point since I’m not going to pretend to understand how X11 works
With that said, if you do figure it out, please update this thread with your findings because I’d love to see it working.
The problem I couldn’t fix was the mouse cursor would smear across my screen whenever I’d move it, then the more cursors that appeared, the more my whole system would slow down. I tried changing config files, but I had no luck
