banned_9-26-2021
1 I suspect what you want is to build an obarun installation from scratch, so why start with arch and not obarun itself?
2 I think you mean arch-install-scripts because tools doesn't exist as a package.
3 If in fact you want to build your own system starting from an empty partition and install piece by piece what you need I think you should start with pacman
wget
https://repo.obarun.org/obcore/pacman-5.1.3-11-x86_64.pkg.tar.xz
Pacman allows to install any package to a different partition that is mounted. So say you make a new one and mount it on /mnt (or anywhere you like), and you can then use the installed pacman on target instead of the one on the host.
The syntax is something like this, but you should look through the manual (man pacman)
first you must create a directory for pacman lib
# mkdir /mnt/var
# mkdir /mnt/var/lib
# mkdir /mnt/var/lib/pacman
# pacman -U pacman-5.1.3-11-x86_64.pkg.tar.xz -r /mnt
# pacman -S filesystem -r /mnt -b /mnt/var/lib/pacman
You then going to need a shell, I can't remember if bash comes with the base filesystem, but you can add zsh and obarun-zsh
At this point if you chroot (# arch-chroot /mnt zsh) into the mounted partition pacman is working so you can add what you need. To boot you are going to need the base s6 66 and a kernel.
This is like linux from scratch based on obarun/arch
saleem
Everything went smooth but when I enable sddm I get error as segmentation fault and same on disable sddm too, startx does not exist.....any ideas?
I have installed Openbox , how to start it without sddm ( by disabling sddm ) ? I made these changes to " .xinitrc " conents
# # Select the session to start
# ${cmd} jwm
${cmd} openbox-session
# ${cmd} startkde
but startx does not start openbox either even if sddm is disabled
From chroot into this test install Obarun I found these
# 66-info -T
boot
Initialized: yes| Current: no
Contains: | Enabled: no
├─(0,Enabled,oneshot) system-hostname
├─(0,Enabled,oneshot) mount-run
├─(0,Enabled,oneshot) populate-run
├─(0,Enabled,oneshot) mount-tmp
├─(0,Enabled,oneshot) populate-tmp
├─(0,Enabled,oneshot) mount-proc
├─(0,Enabled,oneshot) mount-sys
├─(0,Enabled,oneshot) populate-sys
├─(0,Enabled,oneshot) mount-dev
├─(0,Enabled,oneshot) mount-pts
├─(0,Enabled,oneshot) mount-shm
├─(0,Enabled,oneshot) populate-dev
├─(0,Enabled,bundle) 00
├─(0,Enabled,oneshot) system-sysctl
├─(0,Enabled,oneshot) system-hwclock
├─(0,Enabled,oneshot) modules-kernel
├─(0,Enabled,oneshot) system-random
├─(0,Enabled,oneshot) modules-system
├─(502,Enabled,longrun) udevd
├─(0,Enabled,oneshot) udevadm
├─(0,Enabled,oneshot) system-fontnkey
├─(0,Enabled,oneshot) devices-dmraid
├─(0,Enabled,oneshot) devices-btrfs
├─(0,Enabled,oneshot) devices-crypttab
├─(0,Enabled,oneshot) devices-lvm
├─(0,Enabled,bundle) system-Devices
├─(0,Enabled,oneshot) system-fsck
├─(0,Enabled,oneshot) mount-fstab
├─(0,Enabled,bundle) all-System
├─(0,Enabled,oneshot) mount-rw
├─(0,Enabled,oneshot) mount-cgroups
├─(0,Enabled,oneshot) mount-swap
├─(0,Enabled,oneshot) mount-zfs
├─(0,Enabled,bundle) all-Mount
├─(0,Enabled,oneshot) local-iptables
├─(0,Enabled,oneshot) local-ip6tables
├─(0,Enabled,oneshot) local-loop
├─(0,Enabled,oneshot) local-time
├─(0,Enabled,oneshot) local-authfiles
├─(0,Enabled,oneshot) local-tmpfiles
├─(0,Enabled,oneshot) local-rc
├─(0,Enabled,oneshot) local-dmesg
├─(0,Enabled,bundle) all-Local
├─(0,Enabled,oneshot) all-Runtime
├─(282,Enabled,classic) tty12
└─(0,Enabled,bundle) All
boot-user
Initialized: yes| Current: no
Contains: | Enabled: yes
├─(0,Enabled,oneshot) setenv-saleem
├─(0,Enabled,oneshot) mount-run-saleem
├─(810,Enabled,longrun) scandir-saleem-log
├─(831,Enabled,longrun) scandir-saleem
└─(0,Enabled,bundle) All-saleem
root
Initialized: yes| Current: yes
Contains: | Enabled: yes
Segmentation fault
# 66-info -T root
root
Initialized: yes| Current: yes
Contains: | Enabled: yes
Segmentation fault
From chroot when I tried
# 66-enable -t root -C -S tty@ tty1 tty@ tty2
Segmentation fault
eric
ok, let start again from the beginning between us because apparently we don't use the same word to describe the same thing.
When you say:
From chroot into this test install Obarun I found these
that mean for me that you 're are on a operational host (system). Then you mount the partition containing the buggy system on .e.g /mnt directory and you "chroot" this system.
Now you have two different manner to chroot a system. You can chroot it by arch-chroot script or directly by the chroot command. In the second case you need to manually mount the /mnt/proc, /mnt/sys, /mnt/dev and /mnt/run. Without those directories you chroot will not work properly.
So, this is very confusing for me when you said ,"i chroot the system" and i see a pid on eudev o_O.
Anyway, first question:
How did you install 66? by pacman? making a clone of the framagit repository and doing a make install scheme?
second question:
How you build your boot, boot-user, root tree?
Now, i need your help to be able to help you.
Please, from your functionnal obarun system chroot(so the main scandir is NOT running, you don't have any pid from any tree) the buggy one and do the following command:
# 66-enable -v3 -t root tty@ tty1
post the output
then
# strace -vf -s256 66-enable -v3 -t root tty@ tty1
and post the output.
do
# 66-tree -v3 -t root -R
if you got a segmentation fault on this command do:
# strace -vf -s256 66-tree -v3 -t root -R
and post the output.
If the process go well, try to rebuilt the tree
# 66-tree -v3 -cnE root
again if you got trouble do
# strace -vf -s256 66-tree -v3 -cnE root
and post the output.
Obviously, strace need to be installed on your buggy system.
Note: i'm really surprised by those segmentation fault, and i would like know how you get it.
Thanks for your help
saleem
eric wroteok, let start again from the beginning between us because apparently we don't use the same word to describe the same thing.
When you say:
From chroot into this test install Obarun I found these
that mean for me that you 're are on a operational host (system). Then you mount the partition containing the buggy system on .e.g /mnt directory and you "chroot" this system.
Now you have two different manner to chroot a system. You can chroot it by arch-chroot script or directly by the chroot command. In the second case you need to manually mount the /mnt/proc, /mnt/sys, /mnt/dev and /mnt/run. Without those directories you chroot will not work properly.
So, this is very confusing for me when you said ,"i chroot the system" and i see a pid on eudev o_O.
Anyway, first question:
How did you install 66? by pacman? making a clone of the framagit repository and doing a make install scheme?
second question:
How you build your boot, boot-user, root tree?
Now, i need your help to be able to help you.
Please, from your functionnal obarun system chroot(so the main scandir is NOT running, you don't have any pid from any tree) the buggy one and do the following command:
# 66-enable -v3 -t root tty@ tty1
post the output
then
# strace -vf -s256 66-enable -v3 -t root tty@ tty1
and post the output.
do
# 66-tree -v3 -t root -R
if you got a segmentation fault on this command do:
# strace -vf -s256 66-tree -v3 -t root -R
and post the output.
If the process go well, try to rebuilt the tree
# 66-tree -v3 -cnE root
again if you got trouble do
# strace -vf -s256 66-tree -v3 -cnE root
and post the output.
Obviously, strace need to be installed on your buggy system.
Note: i'm really surprised by those segmentation fault, and i would like know how you get it.
Thanks for your help
first question:
How did you install 66? by pacman? Yes by this command
# pacman -S skalibs execline 66 s6 s6-rc boot-66serv tty@ -66serv dhcpcd-66serv
second question:
How you build your boot, boot-user, root tree?
by following these commands
# 66-tree -n boot
# 66-enable -t boot boot
# 66-tree -ncE root
# 66-enable tty@ tty1 tty@ tty2 dhcpcd
Now I am pasting all the desired commands and out put I got here in one go for you
home-pc# mount /dev/sda21 /mnt && mount --bind /dev /mnt/dev && mount --bind /dev/pts /mnt/dev/pts && mount --bind /proc /mnt/proc && mount --bind /sys /mnt/sys
home-pc# cp /etc/resolv.conf /mnt/etc/resolv.conf
home-pc# chroot /mnt /bin/bash
# 66-enable -v3 -t root tty@ tty1
66-enable: info: Read service file of : tty1 from: /tmp/tty1:jsRatB
66-enable: info: Read service file of : tty1 from: /tmp/tty1:08IsV5
66-enable: info: /usr/lib/66/service/tty@ tty1: haven't dependencies
Segmentation fault
# strace -vf -s256 66-enable -v3 -t root tty@ tty1
bash: strace: command not found ( installed strace and got output , I am posting link , very long out put so might not be complete)
https://nopaste.xyz/?f57f6c069aad096a# 0jN1qpe3ExGZQKY6I/nPkweoUFFMi2YK8nbxJwHxKds=
66-tree -v3 -t root -R
66-tree: usage: 66-tree [ -h ] [ -v verbosity ] [ -l ] [ -n|R ] [ -a|d ] [ -c ] [ -E|D ] [ -U ] [ -C clone ] tree
66-tree -v3 -cnE root
66-tree: info: sanitize root ...
66-tree: fatal: unable to create /var/lib/66/system/root: already exist
# strace -vf -s256 66-tree -v3 -cnE root
https://nopaste.xyz/?a02bb5a45d31e048# WGq3WPrPA83mKPkHws4rQmAgGBZcql4vGK+HbmHX4H4=
Hope this will give you some clue what did I do incorrectly. Pardon me if I did not post all the required out puts correctly
saleem
eric wroteyou did nothing wrong, you can blame 66 and his fFu@ # ]^~ dev.
First sorry, my bad, the real command to remove a tree is
# 66-tree -v3 -R root
Anyway that not the trouble here , i think i made a mistake when i did the patch (see
https://forum.obarun.org/viewtopic.php?id=885).
What version of 66 do you use ?
If you use 0.2.0.4-3 version, please try to downgrade to 0.2.0.4-2 , remove the tree root and build it again.
I have not time right now to investigate the patch that i did.
Please let me a few hours to fix this.
Many thanks for your help.
Sigh of relief :)
I did manage to boot that buggy installation but could not connect it to wifi ( a different story which might need attention later on )
I have checked
# pacman -Qs 66
local/66 0.2.0.4-3 (base s6-suite)
small tools built around s6 and s6-rc programs
local/boot-66serv 0.1.0.1-3 (base s6-suite)
Complete and portable set of services to properly boot a machine with 66
tools
local/boot-user-@ -66mod 0.1.0-1
boot-user-@ -66mod modules for 66 tools
local/consolekit-66serv 0.1.1-1
consolekit service for 66 tools
local/dbus-66serv 0.1.1-1
dbus service for 66 tools
local/dhcpcd-66serv 0.1.1-2
dhcpcd service for 66 tools
local/ntpd-66serv 0.1.1-3
ntpd service for 66 tools
local/sddm-66serv 0.1.1-1
sddm service for 66 tools
local/tty@ -66serv 0.1.1-1
tty@ service for 66 tools
so I have 0.2.0.4-3 version, when I tried to downgrade it I get same package available instead of 0.2.0.4-2
downgrade 66
loading packages...
warning: 66-0.2.0.4-3 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
66 0.2.0.4-3 0.2.0.4-3 0.00 MiB
Total Installed Size: 2.18 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
So what to do ?
EDIT : I proceeded ahead with installation ( supposing that you have fixed the package and this is new one ) , enabled root tree again , time to reboot and check how things go now ( ran the commands you mentioned above and did not see any segmentation fault this time )
Finally the buggy test installation is up and running without an issue
I tried to enable connman to connect to wifi but get this error ( I am doing this through chroot from my working Obarun )
# 66-enable -S -t root connman
66-enable: fatal: unable to resolve source path of: connman
What am I doing wrongly?