[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#678696: Event based block device handling (fixes USB and nested devices problem)



On Tue, 2015-03-10 at 12:47 +0100, Goswin von Brederlow wrote:
> On Wed, Mar 04, 2015 at 09:30:24PM +0000, Ben Hutchings wrote:
> > Thanks for your work on this bug.  I ended up with a somewhat different
> > implementation as I don't think it's necessary to duplicate the
> > information that udev provides, and as we may now need to mount more
> > than one filesystem.  But I should have credited you in the changelog
> > for prototyping this, and I forgot to do so.
> > 
> > Ben.
> 
> The idea with the udev rule was to wait up to ROOTDELAY seconds
> without a new device apearing before giving up. Now you wait ROOTDELAY
> seconds in total, which then can depend on the number of devices.

It's now max(rootdelay, 30) because the rootdelay kernel parameter
wasn't meant for this purpose at all.

> Add  new disk and you have to increase the ROOTDELAY.

I hope not!

> Also it was ment so that block scripts could specifically target the
> new devices instead of having to scan all devices every time. For
> example say you have a crypt device and you forgot the password. Now I
> think you will be asked 30 times for the password before the initramfs
> gives up.

True, but so far as I could see you didn't send scripts that made use of
that.  We could still implement that later, I think.

And now that we potentially have to mount /usr (and possibly other
filesystems), not just root and swap, lvm2's script needed to be told
which device we're looking for, not which devices appeared.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: