systemback on arch Linux with no systemd #14
Comments
|
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 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) |
|
Currently this works with systemd, openrc and runit |
|
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 |
|
can i have images/screenshots or something similar (log, file grub.cfg of the newly created iso, package list, runit file list)? |
|
Yes sure my email address is [email protected] |
|
Thanks for your information! |
|
To be precise , I tested your packages with native arch , Manjaro , Joborun ( arch+runit) and Spark ( sinit ) . |
|
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:
***@***.***>
|
|
Thank you for your workaround! |
|
The fix number 2 above apparently doesn't work |
|
guess i should use PID 1 for |
|
You are right , I did some messing around and I get a terminal out that init : must be run as PID 1 |
|
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. 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. |
|
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 |
|
How much are these packages different from yours ? https://sourceforge.net/projects/systemback-2021/files/Systemback%202%20-%20Arch%20Linux/ Ok I checked these , this guy has inserted two shareware packages into his package so it's a useless package because in the packages in the above link when you try to make a backup systemback complains of two HOOKS missing and those are only available in the systemback packages available on his website for sale including his source packages |
I don't know in detail as I don't have any of the source code of that link |
|
And I'll find a way to trim the package down and use |
|
How much working directory space is required to make an ISO? What to do ? |
|
Ok I managed to create a 5.4 GB size ISO , if you are interested I can post the whole method how I did it , shall be helpful for others |
It seems to be making large disk image files. Maybe because your system or your /home or /var is too large or some of your configs made them that big |
|
@drmarwat try again please |
|
I made 6 GB native Arch Linux iso successfully and installed it without any issue. But with 66 or runit the iso fails to make or then fails to boot so I guess it won't work with arch Linux with no systemd |
|
Sorry forgot to mention to make a bigger iso change path of creating iso to another partition formatted as ext4 and systemback will create iso in that empty partition. In case it only creates sblive and not an ISO there is a manual method to create an ISO from .sblive , will post that tomorrow. I would say at this stage your systemback binaries are working fine for native Arch with systemd and if you try to make it with arch Linux nonsydtemd you might break your working binaries |
managed to fix up all the non-systemd related problem just 2 days ago |
|
@drmarwat you can try recompiling from source |
|
@shadichy I just tried making an ISO from Joborun ( Arch Linux with no systemd but rather 66 init system and I get thrses errors Terminal shows this error systembackQStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' An error occurred while executing the following command: tar -cf "/home"/joborun-live.sblive -C "/home"/.sblivesystemcreate . Exit code: 2 Please note that with Arch Linux systemd no such error is seen and an ISO is made smoothly. There is something in Joborun settings that is incompatible with systemback @fungilife please have a look . |
|
Tar exit code 2 means it's your (filesystem) fault |
|
It means the program cannot create sblive tarball on your filesystem |
|
On artix it works pretty well |
|
Also on archlinux32 |
|
You are right it even works fine on Spark Linux which is arch Linux with
sinit , I made successful ISO of it
Somehow systemback is not compatible with Joborun
…On Tue, Jul 4, 2023, 5:50 PM Shadichy ***@***.***> wrote:
Also on archlinux32
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE2WILJCABCGVQVHRFYZYX3XOQGS3ANCNFSM6AAAAAAXYIAFQA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
It is very hard, if possible, to address an "issue" without being able to focus, remain on "one" environment, and provide adequate output. Then as shadichy points out the "error" is on tar command is a generic filesystem error. Elsewhere you mention ntfs, which for storing data, txt,pics, etc.. may be ok, but don't expect linux to work on ntfs. Very different system where rights and ownership are only managed by MSwin executables and are all screwed up when they go from ext to ntfs or reverse. A filesystem error can also be due to lack of space. Here we are dealing with various errors on various attempts on various systems and in a variety of ways. No matter what you use to make an iso/img you have to decide first what the object is, what will go with it and what without. If you have 2TB of /var/cache/pacman/pkg and you don't have mounted in another partition and is included in the / system it will be in the iso. If your /home is not mounted separately and it is part of / it will go as well, and if it is not it should be mounted in the target before you begin (ie /mnt is the target /mnt/home should be where that other partition should be mounted). If you are using /home/user/iso as the place where the img will be written first you have to realize the limits of space and that whether the software is smart enough to exclude this directory in the img or try to include itself endlessly multiplying the space till the partition is full. 1 Target object of system you want to make iso of Spark, arch, and artix all use the same mechanism, obarun and joborun don't, they have consolekit2 and seatd as replacement. |
|
From this whole explanation I derive this conclusion that because of the
absence of systemd and packages you mentioned systemback will not be able
to make an ISO of Joborun or Obarun , systemback will only work on systemd
based any arch distro without any issue
May be penguin-eggs might work on joborun , need to check it , for my Arch
Linux Systemback is working fine making an ISO as big as 6 GB without any
issue
…On Thu, Jul 6, 2023, 4:16 PM joborun ***@***.***> wrote:
It is very hard, if possible, to address an "issue" without being able to
focus, remain on "one" environment, and provide adequate output.
The only output you provide are kernel "warnings" which are normal for
when you don't have linux-firmware installed.
Then as shadichy points out the "error" is on tar command is a generic
filesystem error.
Elsewhere you mention ntfs, which for storing data, txt,pics, etc.. may be
ok, but don't expect linux to work on ntfs. Very different system where
rights and ownership are only managed by MSwin executables and are all
screwed up when they go from ext to ntfs or reverse.
A filesystem error can also be due to lack of space. Here we are dealing
with various errors on various attempts on various systems and in a variety
of ways.
No matter what you use to make an iso/img you have to decide first what
the object is, what will go with it and what without. If you have 2TB of
/var/cache/pacman/pkg and you don't have mounted in another partition and
is included in the / system it will be in the iso. If your /home is not
mounted separately and it is part of / it will go as well, and if it is not
it should be mounted in the target before you begin (ie /mnt is the target
/mnt/home should be where that other partition should be mounted).
If you are using /home/user/iso as the place where the img will be written
first you have to realize the limits of space and that whether the software
is smart enough to exclude this directory in the img or try to include
itself endlessly multiplying the space till the partition is full.
1 Target object of system you want to make iso of
2 Where will the workarea and image stored
3 What is the system making the image, is it the same as 1 or a 2nd system
4 systemback requires polkit ... which logind is using this polkit?
consolekit2, elogind, systemd, seatd, ...?
Spark, arch, and artix all use the same mechanism, obarun and joborun
don't, they have consolekit2 and seatd as replacement.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE2WILL7YFMYXHDCC2RMYETXO2NCBANCNFSM6AAAAAAXYIAFQA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
It's not about polkit, you can run it with
/var is excluded by default the problem may be @drmarwat 's /home doesn't have enough space to create the iso (or the file system is corrupted) also, note that this is my systemback port, I'm not the original developer of this piece of software, and bugs are expected |
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 ?
The text was updated successfully, but these errors were encountered: