unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <niasterisk@grrlz.net>
To: guix-devel@gnu.org
Subject: Re: Shadow -> 4.4
Date: Fri, 20 Jan 2017 11:02:05 +0000	[thread overview]
Message-ID: <87o9z2vvte.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170120051657.GA27443@jasmine>

Leo Famulari <leo@famulari.name> writes:

> On Thu, Jan 19, 2017 at 08:06:34PM +0000, contact.ng0@cryptolab.net wrote:
>> Question: I don't prefer to crash and burn systems, which test is
>> enough to show that it works? Reconfiguring one of my own systems?
>
> Yes. If it breaks your system, you can always reboot into an earlier
> system generation. Another option is to use a VM. I tested both cases,
> and it works for me.
>
> Would anyone else like to test it?

I have just reconfigured my system and I can login, and use
sudo. More testing wasn't done.

By the way, why don't we build 'shadow' with SELinux support?
I know everyone is busy, but I think we really should get that
hardening plan going - or at least come up with a plan on what we
want now and who's interested/will be involved, etc.

-- 
♥Ⓐ  ng0 -- https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-01-20 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 20:06 Shadow -> 4.4 contact.ng0
2017-01-19 20:06 ` [PATCH 1/2] gnu: shadow: Use 'modify-phases' contact.ng0
2017-01-20  5:19   ` Leo Famulari
2017-01-19 20:06 ` [PATCH 2/2] gnu: shadow: Update to 4.4 contact.ng0
2017-01-20  5:18   ` Leo Famulari
2017-01-19 20:15 ` Shadow -> 4.4 contact.ng0
2017-01-20  5:16 ` Leo Famulari
2017-01-20 11:02   ` ng0 [this message]
2017-02-11 18:47     ` Leo Famulari
2017-02-11 19:48       ` ng0
2017-02-11 20:28         ` Leo Famulari
2017-02-17  9:58           ` ng0
2017-01-20 21:07   ` Ludovic Courtès

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=87o9z2vvte.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=niasterisk@grrlz.net \
    --cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).