unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: George myglc2 Clemmer <myglc2@gmail.com>
Cc: 30467@debbugs.gnu.org
Subject: bug#30467: GuixSD fails to display login prompt on headless server
Date: Thu, 15 Feb 2018 16:54:55 +0100	[thread overview]
Message-ID: <20180215165455.09a9efa3@scratchpost.org> (raw)
In-Reply-To: <868tbu9u0r.fsf@gmail.com>

Hi George,

Leo added a comment to the services/base.scm code:

;;; FIXME This doesn't work as expected. According to agetty(8), if this option
;;; is not passed, then the default is 'auto'. However, in my tests, when that
;;; option is selected, agetty never presents the login prompt, and the
;;; term-ttyS0 service respawns every few seconds.
                                #$@(if local-line
                                       #~(#$(match local-line
                                              ('auto "--local-line=auto")
                                              ('always "--local-line=always")
                                              ('never "-local-line=never")))
                                       #~())

So try specifying local-line ?



Also, can you try updating again?

I've pushed some agetty consolidation to guix-master (only) today.

Also, you have

 (kernel-arguments '("console=ttyS1,115200"))

AND

(agetty-service (agetty-configuration (tty "ttyS1")
							 (baud-rate "115200")))

.

Starting today, the second one will be automatically configured by %base-services.

I wonder whether we can provide a nice upgrade path for users.

Can be automatically remove duplicates from the service definitions?
Can we warn about duplicates in the final service definition?

Does agetty lock the serial port?
Or does it happily start two gettys?  The latter would be bad.

So please keep your config the same and reconfigure and let's see what happens.

In the long run please remove your agetty-service, it should automatically appear
(it recovers the settings from the "console" kernel-argument).

If it doesn't work you can always return to the previous generation so no worries!

  reply	other threads:[~2018-02-15 15:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 15:01 bug#30467: GuixSD fails to display login prompt on headless server George myglc2 Clemmer
2018-02-15 15:54 ` Danny Milosavljevic [this message]
2018-02-15 16:23   ` Leo Famulari
2018-02-15 21:29   ` George myglc2 Clemmer
2018-02-16  0:24     ` George myglc2 Clemmer
2018-02-16  0:53     ` Danny Milosavljevic
2018-02-16  1:38       ` George myglc2 Clemmer
2018-02-17 17:04         ` Danny Milosavljevic
2018-02-22  1:35           ` George myglc2 Clemmer
2018-02-22  3:29             ` George myglc2 Clemmer
2018-02-22 11:41             ` Danny Milosavljevic
2018-02-23 15:46               ` George myglc2 Clemmer
2018-02-24 14:51                 ` Danny Milosavljevic
2018-02-26 17:02                   ` George myglc2 Clemmer
2018-02-26 17:32                     ` Danny Milosavljevic
2018-02-26 18:50                       ` George myglc2 Clemmer
2018-02-27 12:08                         ` Danny Milosavljevic
2018-02-27 13:39                           ` George myglc2 Clemmer
2018-02-17 17:05         ` Danny Milosavljevic
2018-03-08 14:16 ` myglc2
2018-03-09 23:23   ` 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=20180215165455.09a9efa3@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=30467@debbugs.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).