Hi,

Thankyou all for your help.

I've got this going using etch and casper.
Here are my notes. They're in Spanish but Google should do a good job
translating.
http://gatopelao.org/?Remote_thinclient

Cheers.
Chris.

On Jan 20, 2008 1:57 AM, jam <[EMAIL PROTECTED]> wrote:
>
> On Sat, 2008-01-19 at 12:06 -0800,
> [EMAIL PROTECTED] wrote:
>
> > > > I wondering just how practical this idea is. LTSP seems to be very
> > > > remote boot orientated. Do yo really think this is a good idea?
> > > > I has a look at http://lessdisks.carookee.com/ at the doc says
> > that it
> > > > isn't continued because the developer 'Vagrant Cascadian' is now
> > > > maintaining the LTSP5 debian packages.
> > >
> > > Chris for me the advantage would be remote boot is exactly the same
> > as
> > > local boot. All ltsp-5 development applies and occasionally updating
> > the
> > > squash image is quick and easy. I just don't have the time now to
> > > impliment this as a fully fledged public offering (I boot to ram for
> > > other reasons: remote location, guaranteed restart, frequent power
> > outs)
> > >
> >
> > I'm also pondering these same thoughts. Let's see if you think I'm on
> > the right track.
> >
> > If I have a remote office with no server then dhcp, ltspfs, lts.cfg,
> > etc, would be no use to me unless I have a tunnel set up (right?). And
> > to set up a tunnel, I need to have acces to the remote router. If I'm
> > relying on a tunnel, then I can't simply ship a thinclient off to any
> > remote site and expect it to work.
> >
> > So, perhaps the tunnel idea would make it worth while to use ltsp5,
> > but in my case, I don't have access to the router so perhaps it's not
> > my case. (agreed?)
> >
> > Then maybe I'm better off doing a small debian installation in a
> > squashfs and mounting it with a rw flash partition with unionfs as
> > Oliver suggests.
> >
> > Anyway, at the moment I've got as far as ltsp5 going on the flash and
> > presenting LDM. ! :) But (excuse me if I'm wrong), the OS is expecting
> > $SERVER to work properly.
> >
> > Any thought would be kindly welcome.
>
> Chris I agree that you are talking about a stand alone machine not a
> thin client.
>
> What I do (for interest) I've a fairly hefty TC with dual core and 1G
> ram. It sits on an oil exploration rig, mid ocean, splashed by sea,
> touch screen etc. It DOES use dhcp (once, not twice) and lts.conf. I'm
> sure ltspfs and sound work, I just don't need, and have never tried. My
> client boots from a local flash squash image to ram. The server is
> 'downstairs'.
>
> I've played only on a 192.168 but if you use the ssh stuff any IP should
> work.
>
> James
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _____________________________________________________________________
> 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
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_____________________________________________________________________
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