Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shérab <Sebastien.Hinderer@ens-lyon.org>
To: buildroot@busybox.net
Subject: [Buildroot] Running several virtual consoles and customizing the keymap
Date: Sat, 3 Mar 2018 10:31:58 +0100	[thread overview]
Message-ID: <20180303093158.GB13445@pema> (raw)
In-Reply-To: <20180302213055.1f294f8d@windsurf.home>

Hi Thomas!

Many thanks for your so prompt and helpful response!

Thomas Petazzoni (2018/03/02 21:30 +0100):
> Hello,
> 
> On Fri, 2 Mar 2018 18:55:32 +0100, Sh?rab wrote:
> 
> > I am new to build root. First of all thanks a lot for having designed
> > such a tool, and for having done so in such an elegant way.
> 
> Thanks!
> 
w> > I use a system in pure text-mode, booted by systemd.
> > 
> > There are two things I don't know how to achieve right now.
> > 
> > 1. Define a (french) keymap. Is there a way to do that in the .config
> > file while not running an X server?
> 
> Use "loadkeys f"

Ah! So should I add this to some startup script,e.g.on the overlay file
system that will be copied on the target?

Where would it be appropriate to add such a command ona system started
with systemd?

> > 2. I am able to run one virtual console but would love to have several of
> > them, typically 6 as on my PC. Can tht be achieved?
> 
> Add more symlinks from /etc/systemd/system/getty.target.wants/ to
> lib/systemd/system/getty at service. See SYSTEMD_INSTALL_SERVICE_TTY in
> package/systemd/systemd.mk.

Thanks for that, too! Again should these links be added to the overlay
filesystem?

Cheers and thanks again for such a nice thing!

Sh?rab.

      reply	other threads:[~2018-03-03  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 17:55 [Buildroot] Running several virtual consoles and customizing the keymap Shérab
2018-03-02 20:30 ` Thomas Petazzoni
2018-03-03  9:31   ` Shérab [this message]

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

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

  git send-email \
    --in-reply-to=20180303093158.GB13445@pema \
    --to=sebastien.hinderer@ens-lyon.org \
    --cc=buildroot@busybox.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