From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] console_name for systemd based systems
Date: Wed, 28 Mar 2012 13:02:23 +0200 [thread overview]
Message-ID: <fa72e3ae9ab807946bf36cd866f26884@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20120328104414.GE27119@pengutronix.de>
Am 2012-03-28 12:44, schrieb Michael Olbrich:
> Which kernel version? systemd uses /sys/class/tty/console/active to
> determine where to start a getty.
$ uname -r
2.6.36.4
(It's planned to upgrade to 3.0.x but we have to port the kernel module
code for our own hardware first.)
$ ls /sys/class/tty/console/
dev power subsystem uevent
> Is "agetty" installed?
Yes: PTXCONF_UTIL_LINUX_NG_AGETTY=y
$ which agetty
/sbin/agetty
>> On the other hand I have still problems with systemd-logind, maybe this
>> prevents correct loading. Do you have special settings for this one?
>
> No, but it's possible that you're missing some necessary kernel config
> options.
Maybe, at least /sys/class/tty/console/active is missing. I already had
to activate some kernel stuff for udev before. The kernel config was not
made by me and I didn't have time to have a close look on it yet. Which
config options do you refer to?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-03-28 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:09 Alexander Dahl
2012-03-28 9:26 ` Michael Olbrich
2012-03-28 10:25 ` Alexander Dahl
2012-03-28 10:44 ` Michael Olbrich
2012-03-28 11:02 ` Alexander Dahl [this message]
2012-03-28 11:10 ` Michael Olbrich
2012-03-28 11:27 ` Alexander Dahl
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=fa72e3ae9ab807946bf36cd866f26884@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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