Hey Alasdair,
thanks for your comments.
On 04/11/2010 Alasdair G Kergon wrote:
If the complex processing doesn't work for everyone then yes, simplify
it and activate everything always.
To do it the other way you need logic something like:
Every time you boot, check if the stack of
I haven't fully looked at this so perhaps it's unrelated,...
But one main problem I see here (that may be related), is that lvm's
init-scripts are simply wrong, and abusing some things.
I've already told Bastian this and there are even several bugs open.
The problem is that lvm's init script
Hey Christoph,
On 04/11/2010 Christoph Anton Mitterer wrote:
I haven't fully looked at this so perhaps it's unrelated,...
But one main problem I see here (that may be related), is that lvm's
init-scripts are simply wrong, and abusing some things.
I've already told Bastian this and there are
Hey Christoph,
On 04/11/2010 Christoph Anton Mitterer wrote:
I haven't fully looked at this so perhaps it's unrelated,...
But one main problem I see here (that may be related), is that lvm's
init-scripts are simply wrong, and abusing some things.
I've already told Bastian this and there are
If the complex processing doesn't work for everyone then yes, simplify
it and activate everything always.
To do it the other way you need logic something like:
Every time you boot, check if the stack of devices necessary to be
activated has changed, and if so, update the information for use
Hello,
Again I tried to work on this bugreport. I'm absolutely sure that
different bugs are spotted. Most people are hitting the following bug:
the debian-installer was changed to configure devices in fstab and
crypttab in the 'UUID=...' style some time ago. this works for most
systems, with the
6 matches
Mail list logo
