From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: discussion: root password switch for next guixsd release
Date: Sun, 12 Jun 2016 00:48:26 +0000 [thread overview]
Message-ID: <20160612004825.GA4146@khazad-dum> (raw)
In-Reply-To: <20160612002447.GA21956@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On 2016-06-11(08:24:47-0400), Leo Famulari wrote:
> On Tue, Jun 07, 2016 at 10:17:02AM +0000, ng0 wrote:
> > Could we target a similar behavior for GuixSD for the next release,
> > where people could pass at least a password to startup parameters?
>
> I don't understand your use case fully, but would it suffice to provide
> the password in the operation system declaration, as described in 7.5.2
> User Accounts?
Insert/Load the guixsd image on a remote/local-remote system, provide
a password which is not empty, start an sshd (lsh/openssh) and be able
to do the installation this way... or at least let it be a step towards
remote setup, as there might be some more things needed for this.
> https://www.gnu.org/software/guix/manual/html_node/User-Accounts.html#User-Accounts
Possibly, if the image is created this way, but I was more thinking
of a possibility where you can pass a password before booting into
the setup.
This however might or might not be possible with the current way
release disks are produced.
I think gentoo's catalyst software produces an image with isolinux,
where you pass the things I mentioned to the kernel like
$kernel arg arg1 arg2 etc
or better:
gentoo dosshd passwd=foo
--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-06-12 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 10:17 discussion: root password switch for next guixsd release ng0
2016-06-12 0:24 ` Leo Famulari
2016-06-12 0:48 ` ng0 [this message]
2016-06-12 1:39 ` Leo Famulari
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=20160612004825.GA4146@khazad-dum \
--to=ng0@we.make.ritual.n0.is \
--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).