From: "florent manni" <mannivelle@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: linux automatic logging and automatic script execution
Date: Tue, 28 Oct 2008 13:54:03 +0100 [thread overview]
Message-ID: <f451b120810280554k10044f01o930d4ec0f5e7282d@mail.gmail.com> (raw)
In-Reply-To: <f451b120810280553g1889098ei1c5e8139b175535c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
2008/10/28 florent manni <mannivelle@gmail.com>
> thanks a lots for the answer indeed that was inittab (my mistake for initrd
> twice).
>
> Now (thaks to you) I know exactly where to set up things (as busybox
> doesn't support runlevel by default I'll try to write something in inittab).
>
> thanks a lot
>
> florent
>
>
>
> 2008/10/28 Chris Skepper <skepper@ukf.net>
>
> On Tue, 28 Oct 2008, florent manni wrote:
>>
>> I try to make my embedded linux auto-logging and auto-executing a program
>>> after kernel loads thus I haven't got to use the terminal to logging and
>>> start my embedded program.
>>>
>>> does anyone has got a clue where I should look to set this option (I
>>> think
>>> it might be around /etc/initrd but I'm not sure).
>>>
>>
>> Hi Florent,
>>
>> You might be thinking of the file /etc/inittab or /etc/init.d/. These
>> file(s) control what process are started by /sbin/init in different
>> run-levels. Look at "man init" on a Linux system for more info, or read the
>> documentation for the version of init on the system. That should enable you
>> to start whatever you want on bootup.
>>
>> If init is too heavyweight you can start any other application with the
>> the init= kernel parameter, but that's probably not recommended unless you
>> know what you are doing.
>>
>> Chris.
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2118 bytes --]
prev parent reply other threads:[~2008-10-28 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 8:06 linux automatic logging and automatic script execution florent manni
2008-10-28 11:36 ` Chris Skepper
[not found] ` <f451b120810280553g1889098ei1c5e8139b175535c@mail.gmail.com>
2008-10-28 12:54 ` florent manni [this message]
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=f451b120810280554k10044f01o930d4ec0f5e7282d@mail.gmail.com \
--to=mannivelle@gmail.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).