From: Sagaert Johan <sagaert.johan@skynet.be>
To: buildroot@busybox.net
Subject: [Buildroot] Selecting custom skeleton hides terminal settingsWhy ?
Date: Sun, 21 Oct 2012 22:40:12 +0200 [thread overview]
Message-ID: <ECFD4F3FAD0A470AB0295E623FA9C18B@JohanW7> (raw)
In-Reply-To: <87y5izr2iq.fsf@macbook.be.48ers.dk>
Hi Peter ;
I will try to make a patch so when a custom skeleton is selected you get a choice whether you would like to configure the console
yes/no ?
Could you agree with that ?
Johan
-----Oorspronkelijk bericht-----
Van: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] Namens Peter Korsgaard
Verzonden: zondag 21 oktober 2012 22:31
Aan: Sagaert Johan
CC: buildroot at busybox.net
Onderwerp: Re: [Buildroot] Selecting custom skeleton hides terminal settingsWhy ?
>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
Sagaert> Hi
Sagaert> (2012.11 git)
Sagaert> When i select a custom skeleton the settings for the login Sagaert> prompt (ttyxxx) and baudrate are hidden .
Sagaert> Can someone explain why this was altered this way ?
Because it relies on a specific syntax in the default /etc/inittab, that might not be present if you use a custom skeleton (perhaps
you don't even have an inittab).
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2012-10-21 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 19:36 [Buildroot] Selecting custom skeleton hides terminal settings Why ? Sagaert Johan
2012-10-21 20:30 ` Peter Korsgaard
2012-10-21 20:40 ` Sagaert Johan [this message]
2012-10-21 21:10 ` [Buildroot] Selecting custom skeleton hides terminal settingsWhy ? Peter Korsgaard
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=ECFD4F3FAD0A470AB0295E623FA9C18B@JohanW7 \
--to=sagaert.johan@skynet.be \
--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