From: Paul Sokolovsky <pmiscml@gmail.com>
To: Sergey Lapin <slapinid@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Adding sanity to OE startup process
Date: Thu, 5 Apr 2007 18:49:19 +0300 [thread overview]
Message-ID: <1653144547.20070405184919@gmail.com> (raw)
In-Reply-To: <461516E2.1000505@gmail.com>
Hello Sergey,
Thursday, April 5, 2007, 6:33:54 PM, you wrote:
> Paul Sokolovsky wrote:
>> 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.
> I think some function should suffice.
> aliasing is possible too.
> Function could be more flexible solution.
Well, yes, function would actually even better. I just wasn't sure
if rules for overriding builtins are portable enough. Well, I checked
that it works for both bash and busybox.
>> 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.
> I don't see why.
>> 5. Using syslogd for boot messages capture is of course optional.
> I don't see why.
> We can log to multiple places.
> All the best,
> S.
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-04-05 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 15:27 [RFC] Adding sanity to OE startup process Paul Sokolovsky
2007-04-05 15:33 ` Sergey Lapin
2007-04-05 15:49 ` Paul Sokolovsky [this message]
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=1653144547.20070405184919@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=slapinid@gmail.com \
/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