MESSAGE
| DATE | 2020-03-19 |
| FROM | Christos Nouskas via artix-general
|
| SUBJECT | Re: [Hangout - NYLXS] [artix-general] migrating from arch and some
|
From hangout-bounces-at-nylxs.com Tue Mar 24 11:53:37 2020
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id D49AE163F80;
Tue, 24 Mar 2020 11:53:35 -0400 (EDT)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id D318E163F79; Tue, 24 Mar 2020 11:53:32 -0400 (EDT)
Resent-From: Ruben Safir
Resent-Date: Tue, 24 Mar 2020 11:53:32 -0400
Resent-Message-ID: <20200324155332.GA16344-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from mail.artixlinux.org (mail.artixlinux.org [144.91.88.22])
by mrbrklyn.com (Postfix) with ESMTP id C447A164005
for ; Thu, 19 Mar 2020 11:46:50 -0400 (EDT)
Received: from [144.91.88.22] (localhost [127.0.0.1])
by mail.artixlinux.org (Postfix) with ESMTP id A3487A257A4;
Thu, 19 Mar 2020 16:46:49 +0100 (CET)
X-Original-To: artix-general-at-artixlinux.org
Delivered-To: artix-general-at-localhost
Received: from hyperion.xyzzy.xyz (ppp005054190232.access.hol.gr
[5.54.190.232])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest
SHA256) (No client certificate requested)
by mail.artixlinux.org (Postfix) with ESMTPSA id 5D9D0A24E64;
Thu, 19 Mar 2020 16:46:46 +0100 (CET)
Date: Thu, 19 Mar 2020 17:46:43 +0200
To: artix-general-at-artixlinux.org
Message-ID: <20200319174643.0e1f0516-at-hyperion.xyzzy.xyz>
In-Reply-To: <7baa35df-0069-8f33-8635-327a53c3e0a8-at-e.email>
References: <7baa35df-0069-8f33-8635-327a53c3e0a8-at-e.email>
Organization: artixlinux.org
X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
X-BeenThere: artix-general-at-artixlinux.org
X-Mailman-Version: 2.1.29
Precedence: list
From: Christos Nouskas via artix-general
Content-Type: multipart/mixed; boundary="===============5277313036097237956=="
Subject: Re: [Hangout - NYLXS] [artix-general] migrating from arch and some
related questions...
X-BeenThere: hangout-at-nylxs.com
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Reply-To: Christos Nouskas
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"
--===============5277313036097237956==
Content-Type: multipart/signed; boundary="Sig_/JJdQndN2Rb04aZPZ+t5Rsdp";
protocol="application/pgp-signature"; micalg=pgp-sha256
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Thu, 19 Mar 2020 02:54:23 -0600
Javier via artix-general wrote:
> Hi !
>=20
> I'd like to migrate from Arch to s6 init Artix. However the migration wi=
ki
> [0] talks about migrating from Arch/Manjaro to openrc init Artix. Actual=
ly
> several packages to install, according to the wiki, are openrc-* ones or
> have the suffix *-openrc (eg. autofs-openrc). Is openrc the only valid
> option to migrate, meaning, for s6 one better install a new system from
> start?
The "hard" part is to get rid of the systemd octopus. Once in openrc, it's
trivial to switch to s6 or runit by just replacing the openrc packages with=
s6
ones. It can even be scripted, but it's always better to maintain control of
the process:
# for p in $(pacman -Qq | grep \\\-openrc); do sudo pacman -Rdd $p; pacman =
-S
$(echo $p | sed s/openrc/s6/); done
There's also a script to fu^Wremove systemd and convert Arch to Artix
(openrc), take a backup and enjoy the perks of science:
http://tiny.cc/fucktheskullofsystemd
> It seems to me the OP still had the Arch repos, though at the very
> bottom... Is that no longer recommended, meaning, no need since Artix is
> maintained pretty up to date with respect to Arch (perhaps some weeks
> behind at the most)?
All of [core] is covered by [system], hence the former MUST be disabled. Mo=
st
of [extra] is in [world], we keep [extra] for packages we haven't yet
imported or are clean of systemd. In [galaxy] go most systemd-infected
[community] packages. So, it's recommended to keep [extra] and [community],
but below Artix repos. AUR is also at your disposal as in every Arch
derivative.
> Are there wikies for how to handle several things that got absorbed by
> systemd and now getting their documentation might not be as easy as on
> prior Arch wikies? Examples are handling the lid on laptops (I don't even
> remember what I used to configure it, but perhaps through acpid), handling
> monitor brightness, performance and power saving tweaks, how to sleep,
> hibernate and the new hybrid (1st sleep and then hibernate), which if I
> recall correctly I used to manage through acpid as well.
In Artix, elogind takes care of such tasks and it should work without any
further configuration. Most if not all exceptions are covered in our wiki;
for the rest, the Arch wiki applies.
=20
> Is sndio fully supported when possible
Every {front,back}end under the sun works in Artix.
> I already asked before in another thread, it seems netcfg is still
> functional, but I guess if not totally functional (definitely
> unmaintained), one could use at least the basic functionality to bring
> interfaces (whether wired or wireless) up, and then let dhcpd and
> wpa_supplicant daemons do their job I'd guess...
You can use any network manager (NM, connman, wicd, dhcp*, static) you like.
OpenRC for example uses netifrc for static configs.
> A recent concern I have is cgroups. Would there be a limitation when usi=
ng
> s6 as the init system for docker or other containers? In the office dock=
er
I'm not a heavy cgroups user, but to date I haven't found a
VM/docker/container implementation that doesn't work in my setups. I use
OpenRC though.
--=20
https://systemd-free.artixlinux.org
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEmK5uMq4KTRJurKyMYCPDvuqwjEoFAl5zk+MACgkQYCPDvuqw
jEq5Twf8D08BaD+nfwemu/ekNGWhfpExkaPTwkNEnsHrd19K1R7/1cJoVMnBVhQb
Lx3/8HuqMY6hHPAjztI1GnCuulTXrND2hM1CeqeZIUtGB3iEVuAQYtgSulVfl2m9
lyG3gPnD8mnP9lCYbJgNp5JpZMog3FUkrN6y8UcAgJTRrfxEYkMKtir6vBTLyVyU
eNd5PvH1Of5/v1VCmQ4W6msbFWPOHiGsyULWssxBVA/O5QE7yK5BCfE7nsQKvPQR
ANwVrgYT3fmTBC3u+nrFPYHhliYYP3bsdN9GqBFaQfnVkgSU5UpNO00+dWGSMwK7
nnVe6Eqp18VIZrdu7+sm04aXnpXYVw==
=0/T3
-----END PGP SIGNATURE-----
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp--
--===============5277313036097237956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
artix-general mailing list
artix-general-at-artixlinux.org
https://lists.artixlinux.org/listinfo/artix-general
--===============5277313036097237956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============5277313036097237956==--
--===============5277313036097237956==
Content-Type: multipart/signed; boundary="Sig_/JJdQndN2Rb04aZPZ+t5Rsdp";
protocol="application/pgp-signature"; micalg=pgp-sha256
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Thu, 19 Mar 2020 02:54:23 -0600
Javier via artix-general wrote:
> Hi !
>=20
> I'd like to migrate from Arch to s6 init Artix. However the migration wi=
ki
> [0] talks about migrating from Arch/Manjaro to openrc init Artix. Actual=
ly
> several packages to install, according to the wiki, are openrc-* ones or
> have the suffix *-openrc (eg. autofs-openrc). Is openrc the only valid
> option to migrate, meaning, for s6 one better install a new system from
> start?
The "hard" part is to get rid of the systemd octopus. Once in openrc, it's
trivial to switch to s6 or runit by just replacing the openrc packages with=
s6
ones. It can even be scripted, but it's always better to maintain control of
the process:
# for p in $(pacman -Qq | grep \\\-openrc); do sudo pacman -Rdd $p; pacman =
-S
$(echo $p | sed s/openrc/s6/); done
There's also a script to fu^Wremove systemd and convert Arch to Artix
(openrc), take a backup and enjoy the perks of science:
http://tiny.cc/fucktheskullofsystemd
> It seems to me the OP still had the Arch repos, though at the very
> bottom... Is that no longer recommended, meaning, no need since Artix is
> maintained pretty up to date with respect to Arch (perhaps some weeks
> behind at the most)?
All of [core] is covered by [system], hence the former MUST be disabled. Mo=
st
of [extra] is in [world], we keep [extra] for packages we haven't yet
imported or are clean of systemd. In [galaxy] go most systemd-infected
[community] packages. So, it's recommended to keep [extra] and [community],
but below Artix repos. AUR is also at your disposal as in every Arch
derivative.
> Are there wikies for how to handle several things that got absorbed by
> systemd and now getting their documentation might not be as easy as on
> prior Arch wikies? Examples are handling the lid on laptops (I don't even
> remember what I used to configure it, but perhaps through acpid), handling
> monitor brightness, performance and power saving tweaks, how to sleep,
> hibernate and the new hybrid (1st sleep and then hibernate), which if I
> recall correctly I used to manage through acpid as well.
In Artix, elogind takes care of such tasks and it should work without any
further configuration. Most if not all exceptions are covered in our wiki;
for the rest, the Arch wiki applies.
=20
> Is sndio fully supported when possible
Every {front,back}end under the sun works in Artix.
> I already asked before in another thread, it seems netcfg is still
> functional, but I guess if not totally functional (definitely
> unmaintained), one could use at least the basic functionality to bring
> interfaces (whether wired or wireless) up, and then let dhcpd and
> wpa_supplicant daemons do their job I'd guess...
You can use any network manager (NM, connman, wicd, dhcp*, static) you like.
OpenRC for example uses netifrc for static configs.
> A recent concern I have is cgroups. Would there be a limitation when usi=
ng
> s6 as the init system for docker or other containers? In the office dock=
er
I'm not a heavy cgroups user, but to date I haven't found a
VM/docker/container implementation that doesn't work in my setups. I use
OpenRC though.
--=20
https://systemd-free.artixlinux.org
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEmK5uMq4KTRJurKyMYCPDvuqwjEoFAl5zk+MACgkQYCPDvuqw
jEq5Twf8D08BaD+nfwemu/ekNGWhfpExkaPTwkNEnsHrd19K1R7/1cJoVMnBVhQb
Lx3/8HuqMY6hHPAjztI1GnCuulTXrND2hM1CeqeZIUtGB3iEVuAQYtgSulVfl2m9
lyG3gPnD8mnP9lCYbJgNp5JpZMog3FUkrN6y8UcAgJTRrfxEYkMKtir6vBTLyVyU
eNd5PvH1Of5/v1VCmQ4W6msbFWPOHiGsyULWssxBVA/O5QE7yK5BCfE7nsQKvPQR
ANwVrgYT3fmTBC3u+nrFPYHhliYYP3bsdN9GqBFaQfnVkgSU5UpNO00+dWGSMwK7
nnVe6Eqp18VIZrdu7+sm04aXnpXYVw==
=0/T3
-----END PGP SIGNATURE-----
--Sig_/JJdQndN2Rb04aZPZ+t5Rsdp--
--===============5277313036097237956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
artix-general mailing list
artix-general-at-artixlinux.org
https://lists.artixlinux.org/listinfo/artix-general
--===============5277313036097237956==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============5277313036097237956==--
|
|
