From: Peter Korsgaard <jacmet@sunsite.dk>
To: Baruch Siach <baruch@tkos.co.il>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>,
Vanalme Filip <F.Vanalme@TELEVIC.com>
Subject: Re: booting kernel(s)
Date: Wed, 23 Feb 2011 10:56:50 +0100 [thread overview]
Message-ID: <87y657xee5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110223091652.GA339@jasper.tkos.co.il> (Baruch Siach's message of "Wed, 23 Feb 2011 11:16:52 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
Baruch> A partial solution is to use initramfs (see the kernel
Baruch> Documentation/filesystems/ramfs-rootfs-initramfs.txt). You can
Baruch> mount your rootfs from the /init script of the initramfs. Then,
Baruch> if mount fails because of a corrupt rootfs, you can mount your
Baruch> rescue rootfs instead, or just run whatever rescue application
Baruch> you want directly from initramfs.
This only works if mount does a complete rootfs check, which isn't the
case. In the typical situation of a power loss in the middle of an
update, the superblock will normally be valid and you will only discover
the corruption when you start accessing files.
Baruch> Another partial solution is a to use a hardware watchdog, and a
Baruch> userspace watchdog ping process. Then, upon boot you may check
Baruch> whether this is a normal power-on reset or a watchdog reset,
Baruch> and load the appropriate kernel.
That's imho a better solution, and pretty simply to implement without
any adverse affects on the startup time, whereas the CRC checks do add
to the startup time.
--
Bye, Peter Korsgaard
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-02-23 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 13:15 booting kernel(s) Vanalme Filip
2011-02-23 9:03 ` Sascha Hauer
2011-02-23 9:16 ` Baruch Siach
2011-02-23 9:56 ` Peter Korsgaard [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=87y657xee5.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=F.Vanalme@TELEVIC.com \
--cc=barebox@lists.infradead.org \
--cc=baruch@tkos.co.il \
/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.