All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] Adding sanity to OE startup process
Date: Thu, 5 Apr 2007 18:27:52 +0300	[thread overview]
Message-ID: <1597775703.20070405182752@gmail.com> (raw)

Hello openembedded-devel,

  I hope many people will agree that boot process is one of the pain
points of OE. Boot/service scripts are collected from Debian and other
various sources, which are mostly intended for "desktop" systems, and
doesn't really scale for embedded usage. For example, on typical
desktop system you have:

1. Big screen and good chance to see a message before it scrolls
away.
2. Ability to pause boot process from console with common Ctrl+S/Q.
3. Scrollback buffer.

  All these are usually not available for embedded system (not
speaking that some embedded systems don't have screen at all).

  So, to start with, I'd like to propose to make it possible for boot
process to log to syslog. I have following in mind:

1. Make a convention that boot/service scripts should use "$echo"
instead of "echo" to do output.
2. Have default define of "echo=echo" for this.
3. Turn /etc/init.d/syslogd into /etc/init.d/syslogd.sh so it was
sourced by /etc/init.d/rc and could export new value for the rest of
scripts.
4. Make /etc/init.d/syslogd.sh start earlier so it could capture as
mush output as possible.
5. Using syslogd for boot messages capture is of course optional.


Thanks,

-- 
 Paul                          mailto:pmiscml@gmail.com




             reply	other threads:[~2007-04-05 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 15:27 Paul Sokolovsky [this message]
2007-04-05 15:33 ` [RFC] Adding sanity to OE startup process Sergey Lapin
2007-04-05 15:49   ` Paul Sokolovsky
2007-04-05 21:36 ` Rod Whitby
2007-04-05 21:45   ` Koen Kooi
2007-04-05 22:07     ` Rod Whitby
2007-04-10 12:27   ` Paul Sokolovsky
2007-04-11  6:53     ` Rod Whitby
2007-04-23  7:15       ` Paul Sokolovsky
2007-04-23  7:59         ` Koen Kooi
2007-04-24 12:26           ` Paul Sokolovsky
2007-04-10 11:27 ` Michael 'Mickey' Lauer

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=1597775703.20070405182752@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.