Re: ext3 corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Horst H. von Brand wrote:
The kernel people are certainly not infallible either. And there are cases
where the right order is A B C, and others in which it is C B A, and still
others where it doesn't matter.

In the quite unlikely situation where that happens, you've obviously
got a piece of software which is broken dependency-wise.  Many of the
current schemes will fail to accommodate that too.

For example, no amount of moving the /etc/rc.d/rc6.d/K35smb script
around will fix that situation on Red Hat.

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

No way to get it right always.

Your example did in no way prove that, so thus far that statement is not true.

In any case, this is wildly off-topic for a list on /kernel/ development.
Better locate a Linux User Group near you, look for mailing lists on running
Linux, trawl Usenet for a group with acceptable signal/noise ratio.

I did mention that:

> Anyway, let's all forget about the init scripts forthwith, they're
> not really relevant for LKML I think.

And:

> Concentrate on the ext3 issue :-).

And my next posting was about ext3 again.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux