Re: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic copy)
From: Pavel Machek
Date: Thu Apr 26 2007 - 08:41:32 EST
> > > The interface isn't even 64/32-bit compatible...
> > It's not . And it's one of the worst interface I've seen lately. Did
> > anyone actually review this crap before it went in? I completely
> > agree with Linus that these kind of boundaries that lead to horribly
> > complex ioctl interface are totally wrong.
> it's a bit hard to see the point of it anyway: the resume binary (much
> of the focus of the ioctls) fundamentally lives as an 'initrd binary' -
> and most of the stuff that wants to execute in an initrd is
> fundamentally tied to the kernel anyway.
Typically... yes, it needs to be in initrd.
And yes, klibc would help here.
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/