From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] Problems at shutdown
Date: Tue, 28 Nov 2006 13:34:54 +0100 [thread overview]
Message-ID: <20061128123454.GA18735@aon.at> (raw)
In-Reply-To: <456C2A5C.9010307@computing.dundee.ac.uk>
On Tue, Nov 28, 2006 at 12:23:56PM +0000, Peter Mendham wrote:
>I have a fairly vanilla buildroot system with just the basics of
>BusyBox. I get issues every time I boot as the filesystem has not been
>unmounted before the previous shutdown. It seems like the shutdown
>entries in my inittab are being completely ignored . I added a script
>of my own (just some echos) as another shutdown and it too was ignored.
>What am I doing wrong?
wrong list. Send your problem and of course your inittab to the busybox
list and do not forget to mention which version of busybox, which init
etc you're using.
prev parent reply other threads:[~2006-11-28 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 10:06 [Buildroot] svn commit: trunk/buildroot/toolchain/dependencies aldot at uclibc.org
2006-11-28 12:23 ` [Buildroot] Problems at shutdown Peter Mendham
2006-11-28 12:34 ` Bernhard Fischer [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=20061128123454.GA18735@aon.at \
--to=rep.nop@aon.at \
--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