From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] tail -f /var/log/messages in inittab
Date: Thu, 30 Jun 2011 20:03:23 +0200 [thread overview]
Message-ID: <20110630200323.76aff92d@skate> (raw)
In-Reply-To: <4E0CA8F9.7080706@lucaceresoli.net>
Le Thu, 30 Jun 2011 18:48:57 +0200,
Luca Ceresoli <luca@lucaceresoli.net> a ?crit :
> and wondered if it's useful to anybody.
> I guess in many embedded systems it is a useless waste of resources.
> At least it is on mine, so I wiped it in my port.
>
> Out of curiosity, does anybody really use it?
> Or should I send a patch that removes it?
I don't use it, and I don't think many embedded systems have a useful
tty3. So I will definitely ACK a patch that removes it.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-06-30 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 16:48 [Buildroot] tail -f /var/log/messages in inittab Luca Ceresoli
2011-06-30 18:03 ` Thomas Petazzoni [this message]
2011-07-04 19:55 ` 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=20110630200323.76aff92d@skate \
--to=thomas.petazzoni@free-electrons.com \
--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