Bug#611632: Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread Mario 'BitKoenig' Holbe
Not that I like to be nit-picking, but... On Mon, Jan 31, 2011 at 05:39:35PM +0100, martin f krafft wrote: > also sprach Mario 'BitKoenig' Holbe > [2011.01.31.1636 +0100]: > > How can halt, kexec or reboot? ;) > All of these get loaded to RAM before init(8) starts the shutdown > process. Are yo

Bug#611632: Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread martin f krafft
also sprach Mario 'BitKoenig' Holbe [2011.01.31.1636 +0100]: > How can halt, kexec or reboot? ;) All of these get loaded to RAM before init(8) starts the shutdown process. > Of course you know umountroot doesn't (yet) really umount the root > filesystem. Fact is that it's not possible to stop

Bug#611632: Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread Mario 'BitKoenig' Holbe
On Mon, Jan 31, 2011 at 04:25:05PM +0100, martin f krafft wrote: > also sprach Mario 'BitKoenig' Holbe > [2011.01.31.1601 +0100]: > > One could probably even think about X-Stop-After: umountroot, but > > I'm not sure about the side-effects. > Won't work: how should the init.d script run after the

Bug#611632: Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread martin f krafft
also sprach Mario 'BitKoenig' Holbe [2011.01.31.1601 +0100]: > The attached patch schedules mdadm-raid the same with or without > cryptsetup or lvm2 installed. It's tested. Okay, thanks. > One could probably even think about X-Stop-After: umountroot, but > I'm not sure about the side-effects.

Bug#611632: Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread Mario 'BitKoenig' Holbe
On Mon, Jan 31, 2011 at 03:03:58PM +0100, martin f krafft wrote: > also sprach Mario 'BitKoenig' Holbe > [2011.01.26.2235 +0100]: > > On a system without lvm or cryptsetup installed mdadm-raid stop gets > > scheduled quite early: > > ... particularly before umountfs. > > > > I'd suggest altering

Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-31 Thread martin f krafft
clone 610421 -1 retitle -1 Alter stop-dependencies to force umountfs before mdadm-raid severity -1 wishlist tags -1 help moreinfo thanks also sprach Mario 'BitKoenig' Holbe [2011.01.26.2235 +0100]: > Hmmm, I guess since this bug is still open I don't need to create a new > one :) In general, it

Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-26 Thread Mario 'BitKoenig' Holbe
On Tue, Jan 18, 2011 at 01:35:59PM +0100, Mario 'BitKoenig' Holbe wrote: > with the new Dependency based boot sequence the boot sequencing of > mdadm's mdadm-raid ad initscripts's hostname.sh changed. Hmmm, I guess since this bug is still open I don't need to create a new one :) I found another i

Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-18 Thread Mario 'BitKoenig' Holbe
package mdadm user initscripts-ng-de...@lists.alioth.debian.org usertag 610421 + incorrect-dependency thanks signature.asc Description: Digital signature

Bug#610421: mdadm: mdadm-raid init-script should depend on hostname

2011-01-18 Thread Mario 'BitKoenig' Holbe
Package: mdadm Version: 3.1.4-1+8efb9d1 Hello, with the new Dependency based boot sequence the boot sequencing of mdadm's mdadm-raid ad initscripts's hostname.sh changed. With legacy boot sequence mdadm-raid was scheduled after hostname.sh which especially makes sense with the new v1 superblocks