From: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Brant Gardner <mail@lnklnx.com>, 34580@debbugs.gnu.org
Subject: bug#34580: Service ssh-daemon could not be started
Date: Sat, 28 Sep 2019 20:23:29 +0200 [thread overview]
Message-ID: <20190928202329.473e4665@scratchpost.org> (raw)
In-Reply-To: <87tv8wqpsf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Hi everyone,
On Sat, 28 Sep 2019 19:44:16 +0200
Ludovic Courtès <ludo@gnu.org> wrote:
> ‘term-auto’ is actually something that doesn’t start; it’s confusing, we
> should present it differently, maybe as a one-shot service.
term-auto automatically provides a shell on the console if that is a serial
console. Maybe it's not represented ideally, but bootstrapping (and
sometimes using) ARM boards without it is a nightmare.
What it does is check /proc/cmdline for a "console" argument and if it's
a serial console, start a serial getty for login.
If the "console" argument is not a serial console, term-auto will fail
(f.e. in order to prevent shepherd from auto-restarting it).
If you then log out again, it will restart the getty, so it's not one-shot.
Maybe we could somehow automatically load another service into shepherd
(it can be scripted at runtime--including what services are provided, right?).
So we could have a one-shot service "term-auto" which checks /proc/cmdline
(which can't change until the next reboot anyway), and if there's a serial
console, register a new (normal) service "term-ttyACM0" or whatever. Otherwise
it would just not register the "term-ttyACM0" service. In both cases, its job
would be done afterwards. How then do we make shepherd actually start the new
service?
To anyone trying this (including me if I do try it), please don't break it
(when changing it) while the sshd problem is still broken--that would REALLY
lock you out of your machines.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-28 18:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:21 bug#34580: Service ssh-daemon could not be started Andreas Enge
2019-02-20 22:21 ` Leo Famulari
2019-02-20 22:48 ` Andreas Enge
2019-02-20 22:51 ` Leo Famulari
2019-02-20 23:08 ` Andreas Enge
2019-02-20 23:56 ` Leo Famulari
2019-03-14 22:11 ` Leo Famulari
2019-03-15 16:35 ` Leo Famulari
2019-02-22 6:52 ` Chris Marusich
2019-09-20 20:00 ` Brant Gardner
2019-09-24 8:08 ` Ludovic Courtès
2019-09-24 12:20 ` Brant Gardner
2019-09-26 20:48 ` Ludovic Courtès
2019-09-27 14:57 ` Brant Gardner
2019-09-28 9:45 ` Ludovic Courtès
2019-09-28 12:38 ` Brant Gardner
2019-09-28 13:54 ` pelzflorian (Florian Pelz)
2019-09-28 17:44 ` Ludovic Courtès
2019-09-28 18:23 ` Danny Milosavljevic [this message]
2019-09-28 18:31 ` Danny Milosavljevic
2019-09-28 19:47 ` Ludovic Courtès
2019-09-28 19:47 ` Ludovic Courtès
2019-09-29 13:02 ` Brant Gardner
2019-09-28 14:11 ` Ludovic Courtès
2019-10-09 14:49 ` Brant Gardner
2019-10-11 10:14 ` Ludovic Courtès
2019-10-12 12:09 ` Brant Gardner
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=20190928202329.473e4665@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=34580@debbugs.gnu.org \
--cc=mail@lnklnx.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).