Re: ext3 corruption

[Helge Hafting <helge.hafting@aitel.hist.no>]

Molle Bestefich wrote:
> John Stoffel wrote:
>> Molle> And voila, that difficult task of assessing in which order to
>> Molle> do things is out of the hands of distros like Red Hat, and into
>> Molle> the hands of those people who actually make the binaries.
>>
>> *bwah hah hah!*
>
> No need to ridicule :-).
> After all, I'm just saying that there's got to be a simpler, stabler
> and more transparent way than to have all this logic sit in shell
> scripts.
Shellscripts are both simple and stable.  Still, you are not the only
one dissatisfied with the sysv init program.

Check out initng:
http://initng.thinktux.net/index.php/Main_Page
It uses config files instead of scripts.  Well, the config files
may contain scripts but they don't have to.  Dependencies
are described in a simple way in these files. Another advantage,
services that don't depend on each other start/stop in parallel,
cutting boot time to 1/3 or so. (30s from powerup to X display is easy.)

I use it on one machine.  It is kind of "unfinished" in that it
don't have config files for every service out there, but it works
and you can make your own files if your service isn't supported yet.

When I looked for a init replacement, I found several other
alternatives too.  All trying different approaches, often trying to save
time by starting up things in parallel, but with very different
approaches to dependencies.  Not all were good.  Some made the mistake
of having the dependant software having to start up all the sw
it depends on.  Consider the maintenance nightmare adding and
removing packages from such a system...

Helge Hafting