[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Re: [Ltsp-discuss] New LTSP + openMosix How-To

Yes.  Exactly.  This is certainly an option worth exploring in several
cases (namely, if your server processor capacity is too limited and it's
getting overloaded, Richard's recommendation would definitely be worth
looking at, IMHO).  It's something I've advocated a number of times myself,

Along the same lines but worthy of mention is the fact that LTSP makes a
wonderful means of getting an openMosix cluster up & running in
minutes--eliminating the need for otherwise installing a full Linux
distribution & openMosix kernel on each client.  For those that are simply
interested in this type of project (those and do not need a GUI running on
their LTSP clients but only want to build a cluster fast) a simple
modification of lts.conf and your ready to go.  Just set RUNLEVEL = 3
instead of 5 and that's it.  Clients boot w/o Xwindows and ta-da, instant
om cluster.

BTW, I installed the 2.4.19-7 openMosix kernels on K12LTSP 2.1.2 and they
worked without a hitch.  No more hanging up during the boot process.

On another (off-topic) note, I also got my old(er) WineX 2.1.1 RPM loaded
on this same system and it's running some of the Windows edutainment
applications I have perfectly one the server.  It's great!  In fact, they
will run on the LTSP clients too but I'm having sound problems <sigh>...

The WineX LTSP test client is a piece of junk.  It's an old 486, 24MB of
RAM w/ a Cirrus Logic video chip displaying a maximum 800x600 resolution in
16-bit color. It only has one PCI slot (holding the 10/100 NIC), the rest
are ISA. No way this particular piece of windows edutainment would run on a
local install of win9x on this box, the minimum requirements are P166 w/
32MB Ram...  LTSP makes a throw-away PC usable again. ;-)

James Jensen

--- Richard Camp <rcamp campworld net> wrote:
> David,
> It is possible to configure openmosix to only run on the servers. 
>  Through the dhcpd.conf file it is also possible to configure certain 
> clients to boot an openmosix kernel.  Add another network card to the 
> server and have that subnet boot openmsoix clients.  AKA diskless 
> servers on a seperate network.  This will take care of bandwidth issues.
> Richard
> David Trask wrote:
> >Ok...what about this?  Is it possible to restrict the cluster to servers
> >only?  That way you don't transmit the Xserver stuff over the network to
> >and from the clients thus possibly messing with bandwidth.  Can we
> simply
> >build a server cluster that balnces among itself...leaving the client
> >processors out of it?
> >
> >
> >k12osn redhat com writes:
> >
> >>If your single server is running out of capacity, one way to expand is
> >>to add additional servers and build an openMosix cluster. For
> >>example, if you work in an organisation that is throwing away PIII
> 600MHz
> >>PCs with 256Mb RAM because they are 'too slow' for Windows XP, then you
> >>can grab them from the rubbish bin and build them into a cluster.
> >>
> >>The advantages of openMosix are said to be you can add and remove
> >>servers from the cluster without interrupting service to users; the
> >>cluster load balances automatically; ... there may be more. I have no
> >>personal experience of the technology; maybe others can help?
> >>
> >>John
> >>
> >
> >
> >David N. Trask
> >Technology Teacher/Coordinator
> >Vassalboro Community School
> >dtrask vcs u52 k12 me us
> >(207)923-3100

Do you Yahoo!?
Yahoo! Mail Plus ? Powerful. Affordable. Sign up now.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]