systemback on arch Linux with no systemd

[drmarwat]

Just for a test tried systemback on joborun and it gives this error ( joborun uses arch Linux with runit ) Image generation successful
An error occured while creating the following directory
"/media"

Exact same error was popped out on Spark ( Spark uses sinit instead of systemd ) but did not see this error when I used it on my arch Linux , on arch Linux it created live bootable and installable iso successfully.

Any idea what this error means ? How come same error only shows on joborun and Spark but not on native arch Linux ?

[shadichy]

I'm so sorry about this

I'm not so good at C++ and I was making this port for myself so it seems very buggy
right now I'm not able to be working on this project yet, so sorry about that

I'mma work out to fix this problem as soon as I have time. Thank you for your bug report!

If you have any ideas or patches, I'm willing to receive your pull request(s)

[shadichy]

Currently this works with systemd, openrc and runit

[drmarwat]

I fixed this issue by manually creating a " /run/media " manually and the ISO was created successfully and boots normally but then another issue arises

Grub even shows special line for booting runit but when the ISO boots it complains that it can't find that line init=/usr/bin/runit-it

Now I don't know where to look for how systemback deals with grub , checked all it's configuration files but couldn't find where the settings deal with grub settings

[shadichy]

can i have images/screenshots or something similar (log, file grub.cfg of the newly created iso, package list, runit file list)?

[drmarwat]

Yes sure my email address is drmarwat@gmail.com
Please drop me an email I will send you screenshots etc , sorry I don't know how to attach files here to a comment

[shadichy]

shadichy.dev@gmail.com

Thanks for your information!

[drmarwat]

To be precise , I tested your packages with native arch , Manjaro , Joborun ( arch+runit) and Spark ( sinit ) .
It works perfectly on former two but gives exact same error on later two with different init system other than systemd

[drmarwat]

I'm working on it , my friend developer of joborun has pointed out an interesting fact " Kernel defaults for init in /sbin/init which in arch points to /usr/bin/init # cd /usr/bin # ln -sf runit-init init done But on live menu with grub either the main or sumbenu options you can edit with pressing e you go to the end of the linux=////...... and add init=/usr/bin/runit-init try it on what you burned already and then do the linking above and remake " Below are attached errors in screenshots 1 /media You create /run/media manually before creating ISO 2 : Fix mentioned by my friend above I'm testing the fix above and making a new ISO now

…

On Sun, May 7, 2023, 5:02 PM Shadichy ***@***.***> wrote: ***@***.*** Thanks for your information! — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE2WILMZ5SSK5BMDEKYBGWDXE6FMFANCNFSM6AAAAAAXYIAFQA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[shadichy]

Thank you for your workaround!

[drmarwat]

The fix number 2 above apparently doesn't work
Main issue is difference of /usr/sbin/ on arch Linux to which systemback points but on joborun it's /usr/bin/ where runit-it init resides to which systemback doesn't point when booting from live ISO so the issue arises
Some additional command in systemback settings need to be inserted which makes it enabled to see if init is residing in /usr/bin or /usr/sbin and then make ISO accordingly then systemback will be able to make a bootable ISO

[shadichy]

guess i should use PID 1 for init=...

[drmarwat]

You are right , I did some messing around and I get a terminal out that init : must be run as PID 1
But I'm not sure how to do that

[fungilife]

Hello, pid1 for runit is runit-init, and it can't run later, it must be pid1. This is where you get this error, as if you are trying to run runit-init after something else was executed. In joborun the init link of runit is ommited to accomodate an easy addition of s6/66 so you can boot either.
For s6 things are different, because the same program that is pid1 is also the supervisor of services, modules, instances, etc. So different init systems have different . So s6-svscan can run many many times without being pid1.
I have booted runit, chroot to another system, have s6 supervise services in that chroot, or have a main system just boot, then the host do everything else.

I wish you would experiment with limine, which is great for live systems as it handles both bios and uefi with the same setup and config file. Very simple to edit and customize the bootloader menu, and I am told by void users it is 100% reliable with any setup and live booting.

systemd had to stick its dirty fingers into bootloading as well ... and things will keep getting messier and messier for all of us.

[drmarwat]

The whole issue is that of /usr/bin and /usr/sbin/

On Spark /usr/bin points to /usr/sbin so the ISO got created without any issue just like arch Linux