Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Fresh install S6 problem [SOLVED] (Read 2691 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: Fresh install S6 problem

Reply #15 –
Quote from: Dudemanguy – on
If you do random things and ignore my questions, how am I supposed to help you?
I am trying to figure out if it's my mistake, or if this is some issue. So I decied to reinstalled again. If it "random things", sorry, I thought that's best way to eliminate my mistake during install proces.
Quote from: Chris Cromer – on
I thought it was an isolated incident, however we had another user in our telegram with that same problem as the screenshot:
https://t.me/artixlinux/288553

We  fixed it by switching to tty2, logging in, and doing:
Code: [Select]
chown -R s6log:s6log /var/log/dmesg
chown -R s6log:s6log /var/log/udevd

For whatever reason those 2 directories are owned by root instead of by s6log.
Thank you, I'll try fresh install and I hope for the best.

Re: Fresh install S6 problem

Reply #16 –
Restored backed up  S-6 partition. So far, so good.

Re: Fresh install S6 problem [SOLVED]

Reply #17 –
Quote from: Dudemanguy – on
I'm going to need some context here.

That won't work. Well the s6-rc-bundle command is incorrect (you probably want to use s6-rc-bundle-update add default NetworkManager), but more importantly you have to pass the -c since you are in a chrooted environment and s6-rc isn't actually running on that machine. See the Installation page on the wiki (specifically the network configuration) section that gives an example.

As for your screenshot, that looks considerably more concerning. What's the context of this?

Same problem for me. s6-rc-bundle-update add default chrony yields s6-rc-bundle-update: fatal: unable to take lock on /run/s6-rc/compiled: Permission denied even though i am root.