Hi Josip,
On Fri, Dec 28, 2007 at 01:39:09AM +0100, Josip Rodin wrote:
There's S10checkroot.sh, but it should be safe to assume that if the system
has already booted from the root partition, multipath can't change it
We must ensure the partition mappings (from kpartx) are already there
but
On Wed, Dec 26, 2007 at 10:34:35PM +0100, Josip Rodin wrote:
I suppose, although that's a much more general change that would have many
more consequences. How was the current priority for multipath-tools-boot
selected, is there a rationale for it being as high as 3 (now 4)?
I can't say I can
On Thu, Dec 27, 2007 at 09:59:15AM +0100, Guido Guenther wrote:
On Wed, Dec 26, 2007 at 10:34:35PM +0100, Josip Rodin wrote:
I suppose, although that's a much more general change that would have many
more consequences. How was the current priority for multipath-tools-boot
selected, is there
Hi Josip,
On Wed, Dec 26, 2007 at 01:11:18AM +0100, Josip Rodin wrote:
S0(3|4)multipath-tools-boot needs to be moved to something like
S21multipath-tools-boot, and after this, things work all right
because /etc/modules loads qla2xxx and multipath runs fine.
Wouldn't it make more sense to move
On Wed, Dec 26, 2007 at 05:17:44PM +0100, Guido Guenther wrote:
Hi Josip,
On Wed, Dec 26, 2007 at 01:11:18AM +0100, Josip Rodin wrote:
S0(3|4)multipath-tools-boot needs to be moved to something like
S21multipath-tools-boot, and after this, things work all right
because /etc/modules loads
Package: multipath-tools
Version: 0.4.7-1.1, 0.4.8-5
Hi,
The package installs the multipath-tools-boot init script in the S runlevel
at the position 03 (etch) or 04 (sid). However, module-init-tools is started
at position 20 in the S runlevel, which means that the kernel modules which
aren't
6 matches
Mail list logo
