> > > I'll appreciate your comments on this document Jim, Jonas and > > > others: > > > http://developer.skolelinux.no/driftskonsepter/2004-09-06-thin-clie > > >nts.html > > > > i'm curious about several things in the chart. > > > > is the "3. alt." "Lessdisk" exploring lessdisks as a "half-thick > > client"? > > It's a figure of speak. When a user application runs at the local CPU, > not the server, then I call it half-thick. i understand the half-thick client concept, but i was wondering if you were targeting using lessdisks *as* a half-thick client, or exploring using only as a replacement for the current LTSP, or both. > > what are the memory requirements based on? ?i've mostly used > > lessdisks with 32-64MB of ram. > > I corrected it. this really depends on what kind of applications you'd want to run- if it is used as a conventional thin-client or half-thick client... that's why i was wondering if you were exploring lessdisks as a "half-thick client", because the memory and CPU requirements seemed high for a typical lessdisks "thin-client". > > what does the "Band width" mean? it is a range of used bandwidth, (i meant to say, "is it", not "it is" :) > > from boot-up to average useage? ?does that include loading the initrd > > at boot-time? ?there are some simple machanisms to reduce the size of > > the initrd dramatically, which will save a lot of bandwidth during > > boot. > > "band width" is a unfortunate misspelling of bandwidth. i understood that, too, but was more interested in where the numbers came from- what they actually represented. > > i hope to have a new upstream lessdisks release by the end of the > > week, with some significant changes and improvements. > > We have questions concerning use of bandwidth, maintenance, and > integration with Skolelinux. Finn-Arne will follow this up tomorrow ... good good. thanks for considering lessdisks, hopefully we can make it meet debian-edu's needs. live well, vagrant
Attachment:
signature.asc
Description: Digital signature