Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Luis E. Garcia" <luis@bitamins.net>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] trying a pcengines box
Date: Sat, 23 Apr 2016 10:52:37 +0100	[thread overview]
Message-ID: <CANmMgnGymU8inPudpDJr+FbQNHxBchV0wCjnGEDxuh_j65iX1g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5GnGiuie2rcKqbzS6y8YCtX1Z4tvobgh63zjHpRHDHsA@mail.gmail.com>

On 23/04/2016, Dave Taht <dave.taht@gmail.com> wrote:
> I have it built and running 16.04 off of the msata card now. :woot:
>
> last major trick - always install openssl-server before rebooting.
>
> (I haven't figured out how to make systemd do a serial console either, yet).

Huh, it's supposed to just work, following the kernel settings.

pasting from Google cache, as Poetterings blog is down -


To make use of a serial console, just use console=ttyS0 on the kernel
command line, and systemd will automatically start a getty on it for
you."

By default systemd will instantiate one serial-getty@.service on the
main kernel[4] console, if it is not a virtual terminal

This logic is implemented in a generator called
systemd-getty-generator that is run early at boot and pulls in the
necessary services depending on the execution environment.

sometimes there's the need to manually configure a serial getty, for
example, if more than one serial login prompt is needed or the kernel
console should be redirected to a different terminal than the login
prompt. To facilitate this it is sufficient to instantiate
serial-getty@.service once for each serial port you want it to run
on[7]:

# systemctl enable serial-getty@ttyS2.service
# systemctl start serial-getty@ttyS2.service

Sometimes, there's the need to configure the login prompt in even more
detail. For example, if the default baud rate configured by the kernel
is not correct or other agetty parameters need to be changed. In such
a case simply copy the default unit template to /etc/systemd/system
and edit it there:

# cp /usr/lib/systemd/system/serial-getty@.service
/etc/systemd/system/serial-getty@ttyS2.service
# vi /etc/systemd/system/serial-getty@ttyS2.service
 .... now make your changes to the agetty command line ...
# ln -s /etc/systemd/system/serial-getty@ttyS2.service
/etc/systemd/system/getty.target.wants/
# systemctl daemon-reload
# systemctl start serial-getty@ttyS2.service

This creates a unit file that is specific to serial port ttyS2, so
that you can make specific changes to this port and this port only.


[7] Note that this systemctl enable syntax only works with systemd 188
and newer (i.e. F18). On older versions use ln -s
/usr/lib/systemd/system/serial-getty@.service
/etc/systemd/system/getty.target.wants/serial-getty@ttyS2.service ;
systemctl daemon-reload instead.

  parent reply	other threads:[~2016-04-23  9:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  4:07 Dave Taht
2016-04-20  5:58 ` Erkki Lintunen
2016-04-20  7:09   ` Dave Taht
2016-04-20  7:12   ` Luis E. Garcia
2016-04-20  7:29     ` Dave Taht
2016-04-20 22:01       ` Luis E. Garcia
2016-04-23  0:42     ` Dave Taht
2016-04-23  1:00       ` Luis E. Garcia
2016-04-23  1:29         ` Luis E. Garcia
2016-04-23  1:39           ` Dave Taht
2016-04-23  2:31             ` Dave Taht
2016-04-23  5:14               ` Luis E. Garcia
2016-04-23  5:42                 ` Dave Taht
2016-04-23  5:45                   ` Luis E. Garcia
2016-04-24  7:24                     ` Dave Taht
2016-04-24 16:50                       ` Dave Taht
2016-04-24 18:01                         ` Luis E. Garcia
2016-04-23  9:52                   ` Alan Jenkins [this message]
2016-04-23  1:30         ` Dave Taht
2016-04-23  1:34           ` Outback Dingo

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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANmMgnGymU8inPudpDJr+FbQNHxBchV0wCjnGEDxuh_j65iX1g@mail.gmail.com \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=luis@bitamins.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox