Skip to main content
Topic: Rock64 (Read 1533 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: Rock64

Reply #15
after running the chroot script from here
https://forum.artixlinux.org/index.php/topic,6921.0.html# modified to a path of /mnt/drive/Rock64/armenv/
Code: [Select]
pacman -Syu
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 armtix is up to date
:: Starting full system upgrade...
 there is nothing to do
# dinitctl list
dinitctl: connecting to socket: /run/dinitctl: No such file or directory
# sudo dinitctl list
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: error initializing audit plugin sudoers_audit

what am i doing wrong?

Re: Rock64

Reply #16
after running the chroot script from here
https://forum.artixlinux.org/index.php/topic,6921.0.html# modified to a path of /mnt/drive/Rock64/armenv/
Code: [Select]
pacman -Syu
:: Synchronizing package databases...
 system is up to date
 world is up to date
 galaxy is up to date
 armtix is up to date
:: Starting full system upgrade...
 there is nothing to do
# dinitctl list
dinitctl: connecting to socket: /run/dinitctl: No such file or directory
# sudo dinitctl list
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: error initializing audit plugin sudoers_audit

what am i doing wrong?
well you need to change the permissions on your sudoers file.  looks like you edited it with something other than vim?

Happy Sabbath.  I'm out until sabbath ends.
Cat Herders of Linux


 



Re: Rock64

Reply #21

 Yes, at boot time. It is not persisted (/run is tmpfs)
I see. So i need to create it for chroot.

Why not persist it?
That's how /run is designed. It only contains runtime data which should be erased after shutdown. Same for dinit socket - it makes no sense to keep unix socket file if nothing listens to it
ARMtix