From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: let's talk about SLIM Date: Sat, 26 Aug 2017 21:32:53 +0000 Message-ID: <20170826213253.qxyveyztlhao22bu@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="z7rpf3jqz4p5y3qg" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60529) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dlihw-0008Uu-MR for guix-devel@gnu.org; Sat, 26 Aug 2017 17:33:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dlihs-00067G-0m for guix-devel@gnu.org; Sat, 26 Aug 2017 17:33:32 -0400 Received: from aibo.runbox.com ([91.220.196.211]:56052) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dlihr-00066r-PN for guix-devel@gnu.org; Sat, 26 Aug 2017 17:33:27 -0400 Received: from [10.9.9.211] (helo=mailfront11.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dliho-0001GM-I6 for guix-devel@gnu.org; Sat, 26 Aug 2017 23:33:24 +0200 Received: from ns3067031.ip-79-137-67.eu ([79.137.67.116] helo=localhost) by mailfront11.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1dlihV-0007Ni-Pq for guix-devel@gnu.org; Sat, 26 Aug 2017 23:33:06 +0200 Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --z7rpf3jqz4p5y3qg Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable It seems to me as if SLIM can be dropped once we have something else in place. Would you agree? The big pro for this is that it is dormant for a considerable long time now. If so, I could spare myself the time to fix our slim-service to make it functional with tcsh. I think it only work (tested) with zsh and bash, maybe even fish. tcsh needs another login_command for SLIM as we have this in tcsh: tcsh --help | grep "act as login" -l act as a login shell, must be the only option specified This is not just a tcsh issue. So I have something I am about to try, but: is it really worth it? In my opinion: No. Only if we keep Slim around for a long time. To be clear: I'm not asking for tcsh support, I'm just trying to make it easier for shells which aren't Bash to give their users the freedom to use them without too much work on their own. The login manager is part of a bigger picture. --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --z7rpf3jqz4p5y3qg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmh6QUACgkQ4i+bv+40 hYicjBAAiSuV2uvPO2kdZjVtXEZS/u4QSjum8VS8syHaHh2wI2rtnepK/fk1LEej ap+aIn1NpAGhKnuy1pAajNecc0AWmLSgiHFPU3MlqgmZa4JsqWIrZtCpTi+IRQSr HAHlSmZ9PJ8zpezhMeZm0cs0+mU9uMkx43Ov35t3LarfmUXT89xRs2l3ZxZwJWRS xy6junjQc0IOPfL348GwrKSodhFpIox9qEBnUaE7B0gHG7zagDqyEYEOHAC0ZOIb hidg5X9XOqjfbk1cPRKdQfsHh95+r9wE6a9PuN6prEPl5VoN/0hgYhi+E3qlcKQz wULYllDv2cTMGx1EEwmLipsHAN7IYGyWRZLqYqpwstJfq/i1N5XiGM07I4Zvg5KQ uktCcuyf4dvuSCArRMS2h7nVeOuT10w6ZYWicjhUqoYx+GRarzWw4ypnaZSum/a1 FmYXdUiqNYbJNFcrV/jbtEawOXT2zvk59BPxBaxQA8sW80xmL8sW1/cJvhWC6SUc SBnU3CiIKYuIPCTzmwHY/2x2/yj04EhSC7p2m8vr6XJfV58xjKWxNtj7Qr94dGso AgbJY2g4CL6D4pXXLj6XXexS1CwngxmmpuIcUsj7ZdLPqCzDwHgzDGaXHOKGkY67 KwE3RFKEqPR/Ubgn7BcjtsxcC1tt0pmvOpNN0kyyoGAfvla8ipY= =O67A -----END PGP SIGNATURE----- --z7rpf3jqz4p5y3qg--