Re: Rock64 Reply #15 – 31 January 2025, 22:54:45 after running the chroot script from herehttps://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 listdinitctl: connecting to socket: /run/dinitctl: No such file or directory# sudo dinitctl listsudo: /etc/sudoers is owned by uid 1000, should be 0sudo: error initializing audit plugin sudoers_auditwhat am i doing wrong? Quote Selected
Re: Rock64 Reply #16 – 31 January 2025, 23:37:07 Quote from: n00b – on 31 January 2025, 22:54:45after running the chroot script from herehttps://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 listdinitctl: connecting to socket: /run/dinitctl: No such file or directory# sudo dinitctl listsudo: /etc/sudoers is owned by uid 1000, should be 0sudo: error initializing audit plugin sudoers_auditwhat 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. Quote Selected
Re: Rock64 Reply #17 – 01 February 2025, 08:43:03 Quote from: n00b – on 31 January 2025, 22:54:45Code: [Select]# dinitctl listdinitctl: connecting to socket: /run/dinitctl: No such file or directoryThere is no dinit runtime directory inside chroot. If you want to add services, you have to create appropriate symlinks Quote Selected
Re: Rock64 Reply #18 – 01 February 2025, 17:08:42 Quote from: phoenix_king_rus – on 01 February 2025, 08:43:03Quote from: n00b – on 31 January 2025, 22:54:45Code: [Select]# dinitctl listdinitctl: connecting to socket: /run/dinitctl: No such file or directoryThere is no dinit runtime directory inside chroot. If you want to add services, you have to create appropriate symlinksshould the dinit armtix create this? Quote Selected
Re: Rock64 Reply #19 – 02 February 2025, 16:22:55 Quote from: n00b – on 01 February 2025, 17:08:42Quote from: phoenix_king_rus – on 01 February 2025, 08:43:03There is no dinit runtime directory inside chroot. If you want to add services, you have to create appropriate symlinksshould the dinit armtix create this? Yes, at boot time. It is not persisted (/run is tmpfs) Quote Selected
Re: Rock64 Reply #20 – 02 February 2025, 23:23:17 Quote from: phoenix_king_rus – on 02 February 2025, 16:22:55Quote from: n00b – on 01 February 2025, 17:08:42should the dinit armtix create this? 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? Quote Selected
Re: Rock64 Reply #21 – 03 February 2025, 07:28:30 Quote from: n00b – on 02 February 2025, 23:23:17Quote from: phoenix_king_rus – on 02 February 2025, 16:22:55 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 Quote Selected