Re: Using a newer kernel (than wheezy) and dracut

[Thomas Lange]

 On Mon, 04 Nov 2013 21:49:09 +0100, Carsten Aulbert 
 cars...@welcomes-you.com said:

 the one FAI 4.0.8 is using during installation) [1]. Thus we inserted
 the latest grml kernel according to
 http://wiki.fai-project.org/wiki/Grml_Kernel

 A simple backport of the current 034 version from jessie works fine as 
well.
Thanks for pointing this out. I just forgot to add the newest dracut
version and the new grml kernel packages to the FAI package repository
at fai-project.org.

I'm also using dracut 034-1 with wheezy (since I'm the package
maintainer), although the default wheezy kernel works for me.

-- 
regards Thomas

Re: Using a newer kernel (than wheezy) and dracut

[Steffen Grunewald]

On Mon, Nov 04, 2013 at 09:49:09PM +0100, Carsten Aulbert wrote:
 
 however, installations always stopped prior to mounting the NFSroot with
 mount.nfs: Protocol not supported. It seems that one needs to manually
 add the kernel drivers nfsv{2,3,4} among others when using a kernel 3.6
 or later *or* upgrade to a much newer dracut than the one in wheezy
 (020) [2].
 
 A simple backport of the current 034 version from jessie works fine as well.

As live-boot seems to resolve the multiple interfaces with DHCP issue,
I haven't migrated to dracut (yet). It turns out that, to install the
current sid/jessie kernel (3.11-1), it's sufficient to also upgrade
the initramfs-tools (to 0.110 or higher, Wheezy is at 0.109).
No backport needed at all.
Checking the initrd contents, I found all the nfsv[234] modules, as
well as aufs and other stuff.
Hopefully that's all that's needed to get FAI running even with newer
kernels. (Of course, one has to provide the linux-image and initramfs-tools
packages for installation.)

 Hopefully this will help others to save some time ;)

It would have saved even more time if there wasn't a new Intel eth i/f
every week...

- S