egrain
Been asking questions there, no one ever replies.
Oh, a Chroot install howto would be nice by the way. I mean I'm getting there, but it's not easy if you first tell me how to enable service and then on a wiki page later that I first have to install serivce-66serv packages to actually be able to do it.
Anyway, IRC support would be nice.
banned_9-26-2021
Welcome nevertheless.
It seems that the father of Obarun has gone on a trip and is not in contact for some days, JM I don't know ??, and I don't use irc at all.
Weren't there other users, usually the experienced ones know how to help. You must have tried in a bad day :)
A chroot installation wiki would be a good idea, I've basically written it here a few times.
Also you can use the installer and install the minimal base then build it up through chroot.
What I do after I make a new partition is mount it at /mnt
From obarun live
# mount /dev/sdxxx /mnt
# mkdir -p /mnt/var/lib/pacman
# pacman -Sy pacman -r /mnt
# pacman -S base linux or linux-lts ... arch-install-scripts -r /mnt (also base-devel if you are going to be building packages and using AUR)
# arch-chroot /mnt zsh
# genfstab -U >/etc/fstab
# passwd
# useradd "username"
# passwd "username"
# 66-tree -n boot
# 66-tree -ncE root
# 66-enable -t boot boot
# 66-enable -t root ......tty@ tty1 ... (look at the wiki intro to 66)
fix grub or syslinux (bootloaders)
# edit /etc/66/boot.conf
Ready for reboot
When you first boot and log in run pacman-key --init and then pacman -Syu to make sure pacman is ready to install whatever you like.
Let me know if you want any help.
For efi-boot configuration look at the wiki for efi bootloading configuration.
banned_9-26-2021
PS Any day/week now there is going to be a bomb that will explode, ready for some time, that will alter the way boot services work. Since 66 v0.4 anything and everything can be set as a module instead of a plain service, meaning you can have various configurations for the same service (or service bundle like boot-66serv is). So I may wait till this new boot-66serv is introduced, which will be accompanied by a specific wiki for modules, then maybe write a chroot install wiki page based on the new configuration, and edit the 66-intro and a couple of other pages according to the new boot configuration.
egrain
Thanks so much.
That was also just in time. I just dd if=gentoo of=/dev/sdb because I was fed up after Obarun not working and no one responding in the channel. I must have gotten two bad days actually. I didn't know about the -init-key thing for pacman, I guess that was my problem. The other stuff I managed to figure out myself.
The s6 guy is very friendly by the way.
Anyway, thanks for replying.
[deleted]
Hi
@ fungal_net
I'm already here and on IRC, but it happen that konversation notification doesn't work as expected when I'm on another virtual screen on KDE.
@ egrain
Hi.
As I said I'm on IRC # obarun channel. Ask and if I can help during a pause in my work, I will. Are you also installing gentoo? I'm in charge of 66 for Gentoo and it's working very well on one of my machines ( with ZFS on rootfs by the way ^^ ). If you are interested I will tell you how to replace openrc by s6 and 66 from my overlay
CU later.
banned_9-26-2021
I made a correction on the above instructions, make a note of it.
On pacman use -r /mnt to define the target root directory to where pkgs will install.
negative
fungal_net wroteWelcome nevertheless.
It seems that the father of Obarun has gone on a trip and is not in contact for some days, JM I don't know ??, and I don't use irc at all.
Weren't there other users, usually the experienced ones know how to help. You must have tried in a bad day :)
A chroot installation wiki would be a good idea, I've basically written it here a few times.
Also you can use the installer and install the minimal base then build it up through chroot.
What I do after I make a new partition is mount it at /mnt
From obarun live
# mount /dev/sdxxx /mnt
# mkdir -p /mnt/var/lib/pacman
# pacman -Sy pacman -r /mnt
# pacman -S base linux or linux-lts ... arch-install-scripts -r /mnt (also base-devel if you are going to be building packages and using AUR)
# arch-chroot /mnt zsh
# genfstab -U >/etc/fstab
# passwd
# useradd "username"
# passwd "username"
# 66-tree -n boot
# 66-tree -ncE root
# 66-enable -t boot boot
# 66-enable -t root ......tty@ tty1 ... (look at the wiki intro to 66)
fix grub or syslinux (bootloaders)
# edit /etc/66/boot.conf
Ready for reboot
When you first boot and log in run pacman-key --init and then pacman -Syu to make sure pacman is ready to install whatever you like.
Let me know if you want any help.
For efi-boot configuration look at the wiki for efi bootloading configuration.
chroot method of installing should be added to official guides, if its not there already.
Q: is the 66 services included already on what package? base?
banned_9-26-2021
tty dhcpcd boot -66serv are included, other specific services you need must be added manually.
pacman -Si obcore/base will tell you exactly what is included
I don't have a problem with adding this to a wiki but the distro officially has an installer (obarun-install) which has a base minimal option, and the outcome of this option doesn't differ much as a result or procedure from this. But it saves you an hour worth of work from setting up a user, editing groups, configuring 66/boot.conf etc etc. Still within the installer, if you know what you are doing, you can edit the pkg list "proposed", leave things out, add things you want, but the outcome is your responsibility not the distro's. If for example you change linux to linux-zen and your hw doesn't like it .... don't come out saying the installer didn't work.
I may write this as a user in the forum, it is not officially supported by obarun. If something is not working I am personally responsible to help you get out of a bind or change things.
egrain
Doesn't boot. I end up in grub>
[root@ ob66 /]# 66-intree
Name : boot
Initialized : yes
Enabled : no
Starts after : None
Current : no
Allowed : root
Symlinks : svc->backup db->backup
Contents : tty12 mount-proc mount-sys mount-dev mount-pts system-hostname mount-run populate-run mount-tmp populate-tmp populate-sys mount-shm populate-dev mount-cgroups 00 all-Mount modules-kernel udevd udevadm
devices-dmraid devices-btrfs devices-crypttab devices-lvm devices-zfs system-Devices system-fontnkey system-fsck mount-fstab system-hwclock system-random modules-system system-sysctl all-System mount-rw
local-iptables local-time mount-swap local-ip6tables local-loop local-sethostname local-authfiles local-tmpfiles local-rc local-dmesg all-Local all-Runtime All
Name : net
Initialized : no
Enabled : yes
Starts after : root
Current : no
Allowed : root
Symlinks : svc->backup db->source
Contents : sshd-log sshd
Name : root
Initialized : yes
Enabled : yes
Starts after : None
Current : yes
Allowed : root
Symlinks : svc->backup db->source
Contents : tty@ tty2 tty@ tty1
[deleted]
Moved on the appropriate forum section
Thx
egrain
Oh, i had no kernel in /boot i thought base base-devel was enough. Apparently it wasn't. I'll install and then try again.
Thanks for moving.
egrain
Now it boots and ends here:
Trying to run sulogin command ... something something press enter for maintenance ( ctrl +d to continue )
control-d brought me: sulogin: cannot read /dev/tty1: Operation not permitted
Nothing else is happening. I'll reboot again. If I press enter instead of ctrl+d I'm logged in as root.
banned_9-26-2021
I did say linux or linux-lts along with base, so don't blame me for leaving it out :)
You have sshd enabled but no networking service. I would add dhcpcd on root, but I am not sure this is the problem.
Try # 66-intree -g
It gives more detailed output,
Also you have tty12 (C-A-F12) to log in as user then use su
# 66-all -t -v4 root up
egrain
All good.
I initialize my network manual via rc.local, which apparently has to be in /etc/66/. Now something else is wrong. If you wanna see:
https://dpaste.com/AYGGQHYZF
/var/log is a tmpf is here, so the sshd log thing is normal. Haven't figured out how disable sshd log. Doesn't matter anyway. This is all the time I had. Didn't get it to run in two days. Going back to Arch. Next time I'll go straight to Gentoo.
Thanks for all your help though.
banned_9-26-2021
You mean you want sshd running but not its log?
66-inservice sshd gives you all the information you need. You can't disable it since it is a dependency. If you customize its .conf file and remove the dependency from sshd then you can turn it off, I think. First you have to copy the service file into /etc/66/service and then edit it.
I think
[deleted]
@ egrain
There is nothing wrong. Your /var/log mounted on tmpfs does not make any sense.
@ fungal_net
It is indeed a possibility by disabling the logger but I maintain that it is totally non-sense to mount /var/log on tmpfs.
egrain
I'm not forcing you to do it, but I like it like that. So I will keep it like that.
eric
this is really simple to remove the log from sshd service:
# cp /usr/lib/66/service/sshd /etc/66/service/sshd
then edit the /etc/66/service/sshd service file and remove the log options like this and leave the rest as it
@ options = ( env )
finally enable again the service replacing <tree> by the name of the tree where your sshd service was previously enabled and reload it:
# 66-enable -F -t <tree> sshd
# 66-start -R -t <tree> sshd
banned_9-26-2021
Are you doing this for your machine or someone else's ? :)
egrain
Both. I'm testing stuff and then I spread it. I'm patient 0.