Text only | Text with Images

Artix Linux Forum

Artix Linux => Announcements => Topic started by: ndowens on 23 May 2021, 01:10:25

Title: Available now: 66
Post by: ndowens on 23 May 2021, 01:10:25
66 init is now available for use on Artix. Currently, there is not a downloadable ISO, but one can be made easily. Install artools
and run buildiso -i 66 -p $PROFILE
Where $PROFILE can be plasma, base, etc
Title: Re: Available now: 66
Post by: strajder on 23 May 2021, 11:29:34
It would be nice if there was a wiki article similar to this one (https://wiki.artixlinux.org/Main/Migration) detailing how to migrate to 66 from an installed system.
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 17:11:15
Quote from: strajder – on
It would be nice if there was a wiki article similar to this one (https://wiki.artixlinux.org/Main/Migration) detailing how to migrate to 66 from an installed system.
Just added 66 pieces to that page
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 17:32:40
Quote from: strajder – on
Awesome! I meant more along the lines of switching from {OpenRC,runit,s6} to 66, though. I apologize for not being clear enough.
I sorta thought so after, so I added notes here:
https://forum.artixlinux.org/index.php/topic,2543.0.html#info_16782
Title: Re: Available now: 66
Post by: strajder on 23 May 2021, 17:49:41
So I just go with
Code: [Select]
# pacman -S 66 elogind-66
then? Because when I try that, I get the message that a bunch of dependencies will be broken and pacman refuses to continue. Just checking, all of those *-s6 packages need to be removed?
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 17:53:58
Quote from: strajder – on
So I just go with
Code: [Select]
# pacman -S 66 elogind-66
then? Because when I try that, I get the message that a bunch of dependencies will be broken and pacman refuses to continue. Just checking, all of those *-s6 packages need to be removed?
Yup all must be replaced by SERVICE-66

Though initially switching from 66 to another init was working, testing again, seems going back causes boot to lock up during boot, like it may not be finding init or so. So keep this in mind for now, something I have to relook at why and find solution.
Edit: OK it seems to work ok. I think my issue happens as I restart VM too fast, probably before drive syncs. To be safer, you can run 'sync' after all the changes and wait just a moment.
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 18:54:33
Quote from: strajder – on
No messages about crash, but I don't get a console to login, the last message says "local-rc: info: starts..." and that's it. I could switch to tty12 and login (I have autostart Xorg), but then my keyboard stopped responding and had to hard reset.
Odd, I don't have any suggestions on this, sounds something was corrupted or some steps may have been missed.
Did you do all these:
66-tree -n boot
66-enable -t boot boot@system
66-env -t boot -e $EDITOR boot@system ( change settings here and enable things needed with !yes, not yes) I've tested lvm and btrfs , not dmraid as I don't use raid.
66-enable -t boot -F boot@system
66-tree -ncE default
66-enable RUNLEVEL_SERVICES (e.g sshd etc)
Title: Re: Available now: 66
Post by: capezotte on 23 May 2021, 19:12:18
Just "solved" the problem by  66-tree -RD default; 66-tree -ncE default and enabling the services again. Things are going smooth so far.
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 19:14:17
Quote from: capezotte – on
Just "solved" the problem by  66-tree -RD default; 66-tree -ncE default and enabling the services again. Things are going smooth so far.
Good :) I view 66 as s6 but made easier, as it uses s6 but with a layer on top to make it easier, including writing services for.
Title: Re: Available now: 66
Post by: ndowens on 23 May 2021, 19:23:49
@strajder Locking this topic as it was meant more for announcement, but feel free to open a topic in suite66
Text only | Text with Images