On 2017-05-21, Michael Pope <mich...@dtcorp.com.au> wrote:
> I'm using LTSP under Debian 8 Jessie which I've just upgraded from
> Wheezy. The upgraded went great.

Given that Debian stretch is in the deep stages of freeze... you might
want to consider upgrading to stretch soon, and basically skip jessie
entirely...


> The problem I have is I would like to install kernel 4.9 under the LTSP
> client but I'm getting these errors when I boot a thin client.
>
>         : modprobe: module overlayfs not found in modules.dep
>         : modprobe: module aufs not found in modules.dep
>         : Could not load neither overlayfs nor aufs.

You'll need to use ltsp-client and ltsp-client-core packages from
jessie-backports if you want to use a kernel from jessie-backports, or
switch back to the kernels that are supported in plain jessie.

I think the version of LTSP in jessie only supports "overlayfs" (an
out-of-tree module not present in Debian, but used in Ubuntu for some
releases), not to be confused with "overlay" fs (in mainline linux
4+). The jessie-backports and stretch kernels only support "overlay" fs.

Additionally, "overlay" fs doesn't have the best track record at NFS
compatibility, so the default for LTSP in jessie-backports and stretch
is to use NBD+squashfs.

Hope that's helpful!


>         - [X] Try downloading aufs-dkms under the chroot section

I've been meaning to try aufs-dkms to see if it would work with recent
4.x kernels, but haven't gotten around to it yet...


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to