Re: LTSP with Debian
Shri Shrikumar wrote:
That was my second option. I was just concerned that this might not work
so well with the gcc-3.2 transition messing with packages from the
stable branch.
I might actually just port the packages from woody to work with g++-3.2
or start from testing since I am not going to be so concerned with
security. All the users are trusted (more importantly, they are windoze
users who dont have a clue what a buffer means)
Thanks for that though. I would like to thank John as well for the RAM
recommendation. I will increase it especially once they start using more
than one client.
Shri
I have a preferences file where stable->700 and testing->600
That keeps stable as the first choice and I upgrade to testing only those
packages I recognize as needing more up-to-date. This keeps me in stable by
default, but doesn't interfere with installations that are targed at testing.
I also have unstable->50, but I don't think I have anything in there anymore.
What happens is I grab an unstable package and leave it until it gets
over-loaded by something in testing. It might take a month or more.
And RAM, you will need lots of RAM.
I had a problem with java applets. Two LTSP clients and one workstation
user, all running a java applet game took up my 768MB of RAM and some swap as
well. That was pretty ugly. But then, LTSP isn't really good for gaming.
Other than that one event, I have found 768MB RAM to be decent (it's also all
I can get!) for most "real" applications (no games).
--
When the wind is great, bow before it;
when the wind is heavy, yield to it.
Reply to: