Jimmy Jazz wrote:
Instead /sbin/functions.sh has helped me a lot to write a script
that does approximately the same but in ash and with candies too :)
Now you're making more sense -- you prefer baselayout written in bash
because you are copying and mangling its code in ways that the
developers didn't intend. I see.
FYI, baselayout-2 no longer requires bash.
Right, a shell is not what handles the best concurrency issues but
"wait" and "jobs" have been quite improved. If you have an example i
could try. Also, that makes life exciting and i cheer you up. I'm sure
you will succeed and improve gentoo even better :)
The problem is that a few baselayout operations can be running
concurrently, and these processes will share the same resources (e.g.
service state files). baselayout-1 makes very little effort to serialize
access to any of these resources, resulting in several highly repeatable
failure conditions due to races.
The original bug report:
https://bugs.gentoo.org/show_bug.cgi?id=154670
My attempt to fix it:
https://bugs.gentoo.org/show_bug.cgi?id=166545
However, it turns out my locking implementation can be easily broken and
is not race free.
I'm not quite good in politics but i will follow your advice :). I just
have feared you will definitely drop baselayout-1. (anyway, maintaining
two different kinds of software that do approximately the same thing is
a pain). I will need to reconvert sooner or later.
I'm not involved in baselayout development, but yes, I am fairly sure
that baselayout-1 will be completely dropped in the near future. It's
partially unmaintained at the moment -- there are known bugs which will
not be fixed in the 1.x branches.
Daniel
--
[EMAIL PROTECTED] mailing list
