On 06/27/2010 03:16 AM, Matthew Burgess wrote: > On Sun, 27 Jun 2010 00:25:16 -0500, DJ Lucas <[email protected]> > wrote: >> I've been downloading the latest kernel and modifying a local copy of >> the book to do 6.6 jhalfs builds. Since the book does recommend that we >> use the latest tiny version of the minor release, and this is the only >> place we recommend a deviation, would it be a big deal to override the >> book version with one specified in the configuration for jhalfs? It's a >> silly little addition, but I figured I'd throw it out here in case it >> seems useful. > > I'm sure you already are aware of this, DJ, but the "proper" way to do this > would be to checkout a working copy of 6.6, edit packages.ent to upgrade the > kernel, then point jhalfs at the working copy instead of the "real" 6.6. > > If jhalfs were modified to be able to accept a user-specified version of the > kernel, you'd have to pass it the version + md5sum anyway, at which point > you may as well just type them into packages.ent as type them in jhalfs' > config file :-) >
Actually, I was thinking of a menu option for the end users. I wouldn't be able to take advantage of it as I am already using a custom copy of the book (initd-tools and svn bootscripts export). -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
