On Tue, 2006-06-20 at 08:36 -0400, Peter Billson wrote:
> Gavin,
>If I am not mistaken, the missing 'packages.list' is found on the
> LTSP repository, not on your server.
>
Thanks, Pete. A trap for new players, eh? See Jim's post in reply,
too.
Gavin.
___
Thanks, Jim I'll give that 'cat' a go :-).
Gavin.
On Tue, 2006-06-20 at 08:27 -0400, Jim McQuillan wrote:
> Gavin,
>
> In the /opt/ltsp/pkg_cache directory, where you got the .tgz files from,
> you should also have a .ltsp file for each of the .tgz files. You need to
> cat all of those .ltsp fi
Gavin,
If I am not mistaken, the missing 'packages.list' is found on the
LTSP repository, not on your server.
If you are manually coping the entire LTSP tree over to the new
server, there really is not reason to change where ltspadm points to.
When you run ltspadm it will see what it need
Gavin,
In the /opt/ltsp/pkg_cache directory, where you got the .tgz files from,
you should also have a .ltsp file for each of the .tgz files. You need to
cat all of those .ltsp files together into a packages.list file.
cat *.ltsp >packages.list
Drop that file into the pkg_cache directory on
I have two (potential) ltsp servers/workstations on dialup. I
downloaded ltspadmin and then used it to grab all the necessary ltsp
files (tgz files) to the first PC. Then I went through the
configuration/installation via ltspcfg. Then I tried copying all the
ltsp tgz files from /opt/lstp across
