-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Mittwoch, 17. November 2004 09:51 schrieb Tom Allison:
> my dhcpd.conf file is on another computer, so I can't use ltspadmin
> tools to manage it.
>
> I noticed the block:
>
> host ws001 {
> hardware ethernet 00:d0:59:39:a8:a1;
> fixed-address 192.168.1.200;
> filename "/lts/vmlinuz-2.4.26-ltsp-2";
> }
>
>
> Am I correct in assuming that in the future, any new kernels will
> require me to change this file (vmlinux-2.4.26-ltsp-2) to point to the
> new kernel?
Yes
> Would there be anything fundamentally "bad" in making a link to a
> generic like /lts/vmlinuz-2.4-ltsp and managing all the LTSP clients in
> that manner?
That's OK. In fact I used to set
filename "/lts/kernel";
and make that a symlink to the appropriate file. This might cause trouble if
the linked kernel file lives in another directory (because of chroot and the
like) so better make sure the symlink is a relative path, optimally in the
same directory.
> I'll assume that my DNS server (yet another machine!) will require
> entries for things such as:
> ws001 IN A 192.168.1.200
Either this, or a fully setup /etc/hosts file. Don't forget reverse DNS
entries as well. Tip: I setup a server machine to be 192.168.0.254, with
ws1..ws99 (no, there is not that many machines, but I'm just prepared for
future expansion :-). I used the $GENERATE keyword in my bind zones, like
$GENERATE 1-99 ws$ A 192.168.0.$
and, in the reverse zone,
$GENERATE 1-99 $ PTR ws$.example.com.
> And lastly. I don't have xdm as my default login screen.
> I use "wings" wdm and WindowMaker as my preferred X experience.
>
> Can someone direct me on the steps (approximately even) I'll need to
> affect in order to get these straightened out?
>
> Initial grepping and such shows that ltsp is configured for
> xdm
> twm
>
> I could probably go in and manually change enough settings to get these
> changed around. Do I need to make these changes or is LTSP going to
> pick up my server settings? Will they stay after I re-run ltspadmin
> functions?
Your login manager has to be able to support XDMCP. Once this is enabled, no
further changes should be necessary. IIRC that's just what the config does
for xdm.
The proper window manager (opposed to login manager) shouldn't care wether the
display is a local one ($DISPLAY=":0.0") or a remote one ($DISPLAY="ws1:0"),
else it should be considered severly broken imho. The major differences
between local and remote are in the fact that neither 3d acceleration and the
like nor sound is natively available to the client machines. The latter can
be setup though with LTSP.
HTH
Anselm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBmxegRGDyvz+XrnkRAup5AJ4mb5ajJndDrJLXBIGbif7lJk86rwCfRf12
fw45KiW6K2ySjdh9NGU6p/k=
=VHXT
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_____________________________________________________________________
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
