On Wed, Aug 02, 2006 at 11:44:08AM +0100, martin f krafft wrote: > also sprach Bas Wijnen <[EMAIL PROTECTED]> [2006.08.02.1051 +0100]: > > > The loop should stay endless, IMHO, to ensure that the user passes > > > a proper device string (or 'all' or 'none'). > > > > The loop being endless if the user actually gets to answer the quesion is > > fine. But my debconf priority is higher than "low", so the question isn't > > asked at all, it just loops until I hit ctrl-C. > > > > But you did just point out a workaround. :-) I can just set my debconf > > priority to low and fill in "none" or "all". > > ouch, this is not good. However, I wonder if it's fixed now. My > analysis is that the system autodetected /dev/md_d0 but then didn't > accept that in the loop and didn't give you a way to change that. > Now it should be able to deal with /dev/md_d0, so even at priority > low, things should be fine, right?
Except that the device is called /dev/md/0, I think it's right, yes. :-) > > > but undoubtedly, the problem you point out should be fixed. > > > > That too, yes. :-) But I think the loop should also not be > > endless if the user isn't asked anything. > > If the user isn't asked anything, the question should have been > auto-answered in a way not to enter an endless loop. This is what > happened previously, but it should not happen now anymore, right? On my system it shouldn't, but it seems fragile to need a name that you recognised when the script was written for things to work (assuming that that isn't really needed). > > Well, that'd patch the current version, not the one yet to be > > unpacked and installed. The problem is that the install doesn't > > succeed, and thus the old package is still the one which has its > > config file there. I'd need to rebuild the package, which is > > a bit too much trouble at the moment. > > You can > > dpkg --unpack /var/cache/apt/archives/mdadm_2.5.2-9_*.deb > > and then apply the patch, then > > dpkg --configure -a > > Does this work? Well, not anymore, I think, since the upgrade worked after I changed the answer (and the /etc/default/mdadm reference) to 'all'. I could try to downgrade again, but at the moment I don't have time for that. I think I should be having the same problems on an other computer when I upgrade it, I'll see if I can try it there. > > > and finally try to reboot > > > > I'd prefer not to, I'm quite happy with my >1 year uptime. :-) > > > > Of course if there's a good reason to reboot, I'd do it, but > > AFAICS things still work pretty well. > > I think any change to the system is a good reason to reboot, or else > you may find a power outage to cycle the system and expose an error > at a time when you don't have the time or nerves to fix it. I trust the Debian community that there won't be that many problems. ;-) Or as you put it: > `- Debian - when you have better things to do than fixing a system Anyway, I have some trouble with X not restoring the display properly when a virtual console is activated, and I really don't feel like doing something about it. So of course you're right that I should better do it when I have time for it, but actually, not doing it at all and manually helping the boot process a little when needed is good enough for me, especially because I hardly ever reboot. Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://129.125.47.90/e-mail.html
signature.asc
Description: Digital signature
