From: "Molle Bestefich" <molle.bestefich@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: ext3 corruption
Date: Sat, 12 Aug 2006 12:31:33 +0200 [thread overview]
Message-ID: <62b0912f0608120331k5f4131d1kce351db3de223aaf@mail.gmail.com> (raw)
In-Reply-To: <62b0912f0608120154s1b158732y5da52b17583fdfa0@mail.gmail.com>
Molle Bestefich wrote:
> A solution to your example is to fix two of the three broken pieces of
> software by splitting B into B1 and B2, and either A or C into their
> components likewise:
>
> A1 --> B1 --> C --> B2 --> A2
>
> -or-
>
> C1 --> B1 --> A --> B2 --> C2
To clarify, by the above I didn't necessarily mean "split one process
into two processes". A kernel API where you can wait for a named
object or a subsystem to complete it's startup / shutdown would be
just as well. Or simply waiting on (dis-)appearance of named files in
a dedicated directory named "boot_sequence" in sysfs, would be another
equally fine way to accomplish above scheme.
next prev parent reply other threads:[~2006-08-12 10:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:32 Molle Bestefich
2006-08-08 23:47 ` Molle Bestefich
2006-08-09 1:33 ` Sergio Monteiro Basto
2006-08-09 10:36 ` Molle Bestefich
2006-08-09 11:33 ` linux-os (Dick Johnson)
2006-08-09 15:22 ` Molle Bestefich
2006-08-09 15:38 ` Michael Loftis
2006-08-09 18:28 ` Molle Bestefich
2006-08-09 18:41 ` Mws
2006-08-09 20:17 ` Duane Griffin
2006-08-09 20:47 ` Molle Bestefich
[not found] ` <e9e943910608091527t3b88da7eo837f6adc1e1e6f98@mail.gmail.com>
2006-08-09 23:09 ` Molle Bestefich
2006-08-10 0:08 ` Duane Griffin
2006-08-10 21:00 ` Molle Bestefich
2006-08-12 16:38 ` Theodore Tso
2006-08-12 17:24 ` Molle Bestefich
2006-08-12 21:47 ` Theodore Tso
2006-08-13 19:21 ` Molle Bestefich
2006-08-14 3:23 ` Kyle Moffett
2006-08-14 15:34 ` Theodore Tso
2006-08-14 17:21 ` Molle Bestefich
2006-08-10 3:06 ` Jim Crilly
2006-08-10 9:48 ` Molle Bestefich
2006-08-10 11:41 ` linux-os (Dick Johnson)
2006-08-10 12:21 ` Molle Bestefich
2006-08-10 12:19 ` Helge Hafting
2006-08-10 13:00 ` Molle Bestefich
2006-08-10 14:40 ` gmu 2k6
2006-09-24 8:56 ` Molle Bestefich
2006-09-25 12:27 ` Helge Hafting
2006-10-02 2:40 ` Molle Bestefich
2006-10-02 3:24 ` Gene Heskett
2006-10-02 6:50 ` Kyle Moffett
2006-08-10 16:10 ` John Stoffel
2006-08-10 19:10 ` Molle Bestefich
2006-08-11 8:06 ` Helge Hafting
2006-08-11 13:26 ` Horst H. von Brand
2006-08-12 8:54 ` Molle Bestefich
2006-08-12 10:31 ` Molle Bestefich [this message]
2006-08-17 1:27 ` Horst H. von Brand
2006-08-17 13:46 ` Molle Bestefich
2006-08-10 8:32 ` Bernd Petrovitsch
2006-08-10 7:44 ` Denis Vlasenko
[not found] <Pine.LNX.4.33.0207121337500.8654-100000@coffee.psychology.mcmaster.ca>
2002-07-12 19:05 ` Alec Smith
2002-07-12 20:11 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 15:32 Alec Smith
2002-07-12 15:52 ` Russell King
2002-07-12 19:51 ` Andrew Morton
2002-07-12 16:02 ` Alan Cox
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=62b0912f0608120331k5f4131d1kce351db3de223aaf@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®