unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [V2 PATCH 1/1] services: Add agetty service.
Date: Fri, 17 Feb 2017 17:59:47 -0500	[thread overview]
Message-ID: <20170217225947.GA16812@jasmine> (raw)
In-Reply-To: <86poig3bsv.fsf@gmail.com>

On Fri, Feb 17, 2017 at 01:35:44PM -0500, myglc2 wrote:
> Hi Leo,
> 
> I think that what you have is great. With this in my system config ...
> 
>     (agetty-service (agetty-configuration
> 		     (tty "ttyS1")
> 		     (baud-rate "115200")))
>
> ... it works painlessly on a headless GuixSD server over IPMI.  I think
> you can put a brief example in the doc, refer the user to the code and
> the agetty man page for more info, and declare victory.

Awesome!

Veering off-topic, I wonder what created that device node /dev/ttyS1? I
have 32 of them, but (gnu build linux-boot) appears to only create the
first one:

https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/linux-boot.scm#n160

> But let me digress a bit on this topic. What if, in situations like
> this, Guix provided an easy way to export the "native config" generated
> by Guix?
> 
> Then we could tell the user ...
> 
> 1) If you want to know exactly what we are doing, export the native
> config and read the native doc.
> 
> 2) If you want features we don't support, export the native config, read
> the doc, modify it, and feed it into the "native config hatch."
> 
> With this approach, we could implement and document only "key features"
> with a clear conscience.  When we haven't implemented a feature the user
> needs they will be no worse off that they were before. In fact, they
> will usually be ahead, because Guix has taken care of the general
> requirements and provided a sound starting point for a native config.

An interesting idea! I guess the implementation would vary based on
services that use a configuration file (like nginx) and those that are
configured on the command-line (like agetty). But I'm still finding my
way around services, in general, so I'm not sure.

  reply	other threads:[~2017-02-17 22:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  0:12 [PATCH 1/1] services: Add agetty service Leo Famulari
2017-02-15  0:24 ` Leo Famulari
2017-02-15 15:21   ` myglc2
2017-02-15 19:38   ` Leo Famulari
2017-02-16  7:06   ` [V2 PATCH " Leo Famulari
2017-02-17  7:48     ` Ricardo Wurmus
2017-02-17 14:24       ` Leo Famulari
2017-02-17 18:35     ` myglc2
2017-02-17 22:59       ` Leo Famulari [this message]
2017-02-18  1:23         ` myglc2
2017-03-07 14:43         ` 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=20170217225947.GA16812@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=myglc2@gmail.com \
    /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).