Re: [K12OSN] k12osn on mandrake

[Warwick Bruce Chapman <warwick thusa co za>]

Quoting Brook Humphrey <bah webmedic net>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Tuesday 29 April 2003 05:00 pm, Warwick Bruce Chapman wrote:
> > Howdy Brooks
> >
> > I also am a Mandrake supporter, also do some packaging. I have implemented
> > LTSP many times over on Mandrake, and would be interested in collaborating
> > with you on this project.  I have been writing a Mandrake/LTSP Guide,
> which
> > may come in handy as well.
> 
> Thanks by any chance have you tried the built in terminal server packages
> that 
> come with mandrake. From my hunting I just realized that they already have a
> 
> built in terminal server that is easy to set up but I would like to know more
> 
> about the pro's and cons of each. I think I understand the majority of it 
> already but it would still be interesting to know.

I haven't tested this package at all. I should try it sometime.
 
> The one thing I noticed is that the mandrake terminal server does require a 
> fair amount of tweeking the dhcp.conf. I have not installed or dealt with 
> lstp yet I have only been doing my homework first. but is lstp more automatic
> 
> in the handling of the clients? Does it need the dhcp.conf edited for each 
> client with mac address and such.

If one uses Etherboot images [www.rom-o-matic.net], and has a network of 
identical driver NIC [eg. eepro100], the etherboot method will allow MACless 
configuration of dhcpd.conf for all terminals but the exceptions.

PXELINUX boot method is more intelligent, and can detect the PCI card and 
autoselect a device driver.  It is a little more complex to set up, but is 
typically also used with a MACless dhcpd.conf

> >
> > Just as a note for others, installing LTSP on Mandrake 9.1 is simply a
> > matter of following the instructions at [incomplete document]:
> > http://www.thusa.co.za/projects/mandrake/ltsp, configure dhcpd as per the
> > LTSP docs and then doing the following:
> >
> > - Install kdm [ # urpmi kdebase-kdm ]
> 
> was there a problem with using mdk-dm or was this done more for preference to
> 
> kde-dm. It does not matter to me either way I'm just curious.

mdk-dm didn't seem to start on the client. I dunnow if it is a fully compliant 
dm.  I like KDM, especially how configurable it is from within KDE Control 
Center. I would choose it over mdk-dm anyway.

> > 
> > > > - Change DM in /etc/sysconfig/desktop from KDE (mdk-dm) to KDM
> (kde-dm)
> > [DEKSTOP = KDM]
> >
> > That's all I needed to do extra to have a working installation.
> >
> > Warwick Chapman
> > Managing Member
> > Thusa Business Support cc
> > Cell: +27 83 7797094
> > Fax: +27 31 2055838
> >
> > -- There are 10 types of people in this world. Those
> > who understand binary, and those who don't.
> >
> you almost got me on this it's been years since I dealt with binary.
> 
> - -- 
>  -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
>                                       Brook Humphrey           
>         Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107        
> http://www.webmedic.net, bah webmedic net, bah linux-mandrake com   
>                                  Holiness unto the Lord
>  -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
> 
> iD8DBQE+rxvOnT1TkA6FgPgRAgDRAJ0SElvSefMU6Ea1anmJCo+7Nh/yXwCfbl63
> NiAcx5o+D870wzlbzkuo7VY=
> =vzI+
> -----END PGP SIGNATURE-----
> 
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://listman.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 

Warwick Chapman
Managing Member
Thusa Business Support cc
Cell: +27 83 7797094
Fax: +27 31 2055838

-- There are 10 types of people in this world. Those
who understand binary, and those who don't.