The specific trouble we had was that once the jaunty client was
installed you couldn't actually launch a terminal on it - and you
couldn't login to a remote terminal either. It turned out that this was
because the order of the jobs in rcS.d seemed to be wrong. I can't
remember the exact details, but the bottom line is that it was causing
it to fail to load the terminals into the mtab. There were two scripts
that tried to do this, and one (that ran first) seemed to have a
slightly odd syntax. Changing the order these two scripts ran in fixed
the problem.
This was actually the only problem we found, but if it was doing
something like this then we weren't convinced it wouldn't be doing other
things that we would only discover later on. Using a jaunty base.tgz
resolved this issue (and hopefully any others that we hadn't discovered...)
Richard
Henning Sprang wrote:
Hi Richard,
Richard Grant wrote:
Create a jaunty base.tgz using pbuilder and replace the lenny one in the
nfsroot with this one. (otherwise it appears to install correctly but
various bits don't quite work)
Could you explain what these pieces are?
I did not yet do that with jaunty, but with multiple earlier Ubuntu
versions, I just did and always do most of the things as described here,
and it works, even for RHEL and others, without modifying the nfsroot
contents:
http://faiwiki.informatik.uni-koeln.de/index.php/FAI_multi-distribution
Henning
