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

Bug#688794: Circular dependancy after reboot when..



On Tue, Oct 09, 2012 at 07:26:47AM -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 09 Oct 2012, maximilian attems wrote:
> > On Mon, Oct 08, 2012 at 06:03:20PM -0300, Henrique de Moraes Holschuh wrote:
> > > Well, I don't mind changing the name of the initramfs-tools helper scripts
> > > in the *-microcode packages,
> > 
> > please do so.
> 
> As long as the release managers agree.  I will try.

Of course they will as it only your package that triggers this bug.
 
> > > but this _really_ needs to be documented in the
> > > initramfs-tools manpages, AND it needs to generate an warning on
> > > update-initramfs time.  It is really non-obvious.
> > 
> > The corner case infact involves a noexec /var/tmp, which is why allmost
> > no one sees it.
> 
> This makes it worse.  Please document this now, an upload that only changes
> manpages and static docs in /usr/share/doc is not going to endanger the
> freeze.

All the known scripts ship with proper names thus it is not such
a big deal for the stable release itself.
The cornercase is thus smaller than epislon.

It's up to mikap if he retracts his doc change.
 
 
> > > Also, I suggest that initramfs-tools should either provide tsort inside the
> > > initramfs, or drop the code that conditionally uses it.  That codepath could
> > > be hiding landmines as well.
> > 
> > The landmines are that this codepath is real crap, still dating jbailey.
> > No way we going to touch that at this point of the release.
> 
> You're aware that post-freeze or not, the fix for this kind of crap needs to
> go to stable, I hope.  So it is either fix it during the freeze, or fix it
> through stable-proposed-updates.

If you care about it, please send patches. I'd be very welcome to review
test and apply them.
http://anonscm.debian.org/gitweb/?p=kernel/initramfs-tools.git;a=summary

 
> >From what I can see, the only fix that is not going to over-complicate
> things is to make sure update-initramfs will ALWAYS create the ORDER file,
> and remove the other two codepaths from scripts/functions.  If the ORDER
> file is missing, the initramfs code should try to run things in C collation
> order, as that has at least a non-zero chance of working, and therefore it
> is MUCH better than dying with an error message *during boot*.

I totaly do agree, that was what I was implying.

On a related note this !lkml, please keep cool.
happy hacking,

-- 
maks


Reply to: