Bug#398312: Re: Bug#398312: INITRDSTART='none' doesn't work

2006-11-13 Thread dean gaudet
On Mon, 13 Nov 2006, martin f krafft wrote: > also sprach dean gaudet <[EMAIL PROTECTED]> [2006.11.13.1107 +0100]: > > which causes the is_true() in info() to return 1 which causes the set -e > > to terminate the script. > > What shell are you using? my SHELL=/bin/zsh, but that won't affect the

Bug#398312: Re: Bug#398312: INITRDSTART='none' doesn't work

2006-11-13 Thread martin f krafft
also sprach dean gaudet <[EMAIL PROTECTED]> [2006.11.13.1107 +0100]: > which causes the is_true() in info() to return 1 which causes the set -e > to terminate the script. What shell are you using? Does it work if you change info() to info() { is_true ${VERBOSE:-false} && write I "$@" || : }

Bug#398312: INITRDSTART='none' doesn't work

2006-11-13 Thread dean gaudet
On Mon, 13 Nov 2006, martin f krafft wrote: > severity 398312 important > tags 398312 unreproducible moreinfo > thanks > > > even though i have INITRDSTART='none' in my /etc/default/mdadm and rebuilt > > the initrd, it still goes and does array discovery at boot time. > > piper:/tmp/cdt.d.Ns8889

Bug#398312: INITRDSTART='none' doesn't work

2006-11-13 Thread martin f krafft
severity 398312 important tags 398312 unreproducible moreinfo thanks > even though i have INITRDSTART='none' in my /etc/default/mdadm and rebuilt > the initrd, it still goes and does array discovery at boot time. piper:/tmp/cdt.d.Ns8889# grep '^INITRD' /etc/default/mdadm INITRDSTART='none' piper:

Bug#398312: INITRDSTART='none' doesn't work

2006-11-12 Thread dean gaudet
Package: mdadm Version: 2.5.5-1 Severity: grave even though i have INITRDSTART='none' in my /etc/default/mdadm and rebuilt the initrd, it still goes and does array discovery at boot time. this is marked grave because it can cause dataloss if drives with stale superblocks are put together in an