unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Changing user-account's shell
Date: Fri, 19 Apr 2019 23:30:24 +0200	[thread overview]
Message-ID: <20190419213024.sc25c4qlyppg5sua@melmoth> (raw)
In-Reply-To: <87r29yciaf.fsf@gnu.org>

Le 04/19, Ludovic Courtès a écrit :
> Tanguy Le Carrour <tanguy@bioneland.org> skribis:
> > Le 04/18, Ludovic Courtès a écrit :
> >> Tanguy Le Carrour <tanguy@bioneland.org> skribis:
> >> > I'm trying to set my user's shell through the Guix configuration system,
> >> > but without success.
> >> > […]
> > Bug or feature?!
> 
> I say “feature”, but we can discuss it.  :-)
> 
> The (gnu build accounts) module, which populates /etc/passwd, considers
> the user shell to be “state”
> […]
> WDYT?

Definitively Feature! You've convinced me!
But, I guess, it will still feel weird for a little while not to see
the exact "state" describe in my config be applied on `reconfigure`.

I was thinking that maybe this could be documented like `password` is:

    You would normally leave this field to ‘#f’, initialize user
    passwords as ‘root’ with the ‘passwd’ command, and then let
    users change it with ‘passwd’.  Passwords set with ‘passwd’
    are of course preserved across reboot and reconfiguration.

Something like:

    … and then let users change it with `chsh`. Shells set with `chsh`
    are of course preserved across reboot and reconfiguration.

Anyway, thanks for your time geeks!

-- 
Tanguy

  reply	other threads:[~2019-04-19 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 19:59 Changing user-account's shell Tanguy Le Carrour
2019-04-18 14:45 ` Ludovic Courtès
2019-04-18 20:51   ` Tanguy Le Carrour
2019-04-19 12:04     ` Ludovic Courtès
2019-04-19 21:30       ` Tanguy Le Carrour [this message]
     [not found] ` <87d0lkz5jw.fsf@ambrevar.xyz>
2019-04-18 20:22   ` Tanguy Le Carrour
2019-04-19  6:53     ` Pierre Neidhardt
2019-04-19 21:24       ` Tanguy Le Carrour

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190419213024.sc25c4qlyppg5sua@melmoth \
    --to=tanguy@bioneland.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).