On Fri, Sep 17, 2004 at 03:07:12PM -0400, Joey Hess wrote: > Paul Hampson wrote: > > The issues arises when apt-install mdadm installs mdadm, > > "mdadm --monitor" is run without debconf asking questions, > > as it does if it's installed with apt-get install. In > > particular, mdadm/start_daemon is skipped, and defaults to > > "true". > > > Now that I've found the process being undertaken for this > > menu option, I can either manually simulate it myself, or > > try and stop mdadm starting mdadm --monitor... > > > > It looks to me like a change in mdadm caused this, in > > particular 1.6.0-1's changelog lists: > > * Changed default to autostart RAID array. > > (closes: Bug#250792)
> Of course the bug there was that without this change, mdadm did not > start when booting the installed system, so we didn't get raid at all > then. Kinda damned if we do and damned if we don't. It sounds as if we Actually, not quite... I'm referring to mdadm --monitor which is seperate from starting raid support, as far as I can tell.... It's two different environment variables in /etc/default/mdadm. (I can't recall what they _are_ mind you... AUTOSTART and AUTOSTART_DAEMON I think.) As I said, I'm not sure if the above change modified _both_ variables to default to true. My initial reading suggested that only one was, but I've not looked through snapshots.debian.net to check. > need to arrange for mdadm to not be started when the installer is run, > but do continue to let it be started afterwards. > > My ideal preference would be for mdadm --monitor to not run > > during the install, irrespective of whether the user wants it > > when the system's running. But short of adding 'killall mdadm' > > after apt-install mdadm in base-install's postinst, I dunno > > how else to do that. > Well, I think that would be a good quick fix. Note there's no killall in > the installer, but you can probably instead add this: > chroot /target /etc/init.d/mdadm stop > If that works for you well enough we can look for a better fix.. such as > applying the patch in bug #264451. That would work, since the mdadm-udeb (I think?) already starts the raid arrays... I'll give it a try hopefully this weekend, and see how it goes with that patch (which I see has been applied. ^_^) I suspect a tangent to this issue is that when apt-install installs mdadm, the debconf prompts aren't shown. (Since it sets DEBCONF_FRONTEND=noninteractive)... I assume it does this to not muck with debian-installer, but... Hmm. I guess that's why we _have_ defaults... Maybe base-installer could put up a note "If you want to change where your mdadm notification emails go, dpkg-reconfigure mdadm or change /etc/default/mdadm"? -- ----------------------------------------------------------- Paul "TBBle" Hampson, MCSE 7th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] "No survivors? Then where do the stories come from I wonder?" -- Capt. Jack Sparrow, "Pirates of the Caribbean" This email is licensed to the recipient for non-commercial use, duplication and distribution. -----------------------------------------------------------
signature.asc
Description: Digital signature
