> What I'm asking about is a cross-refernce list which would allow me to
> pick the correct modifier for each video card that might be used.
>
> That list is probably huge by now, with all the new video cards that
> have been released in the last decade or two, but I'm wondering if there
> is such a list and if so, where would it be found?
I don't know of a list, but I agree, it would be helpful. Here are some
examples from my lts.conf file if they are helpful
XSERVER = auto
# XSERVER = nsc
# XSERVER = geode
XSERVER = XF86_5530
XSERVER = vesa
XSERVER = vesa
XSERVER = i810
XSERVER = i810
>
> Also, Xorg seems to have changed how the individual modules would be
> labelled in the lts.conf file where the prefix "XF86" is no longer
> necessary (?), and therefore that list may become a lot more important
> as Xorg becomes the defacto standard with future releases of LTSP.
>
> I saw an email earlier this morning where Jim was suggesting that
> someone use
>
> "XSERVER = i810"
>
> for a particular video card in order to solve a problem someone was
> having. For others having similar problems, having a cross-refernce list
> which could tell people what to use wold be very handy, especially if
> the modifier of the comment needs to change now due to Xorg.
agreed
-snip-
>
> >
> > not sure what you mean. I use dns instead of the hosts file anyway.
>
> OK, I'll try to clarify. DHCP leases IP addresses in reverse order -
> starting with the highest IP address it has in it's subnet-range. If
> that range is configured in DHCp as "192.168.0.65 to 192.168.0.254",
> then the DHCP server hands out the highest IP address of that range to
> the first system requesting an IP address (which would be 192.168.0.254)
> but the average person (IMHO) would usually start building an LTSP
> betwork with the first terminal they want to deploy.
This is not my experience with the ISC dhcp server. I have always noticed it
starting at the beginning of the range... but anyway.
>
> That first terminal would probably be called WS001 or WS002 as per the
> hosts file. The hosts file created by the ltspcfg wizard on the other
> hand, is written in such a way that [WS002] is first in the file and is
> given an IP address of 192.168.0.2.
>
> Since it is possible and sometimes necessary to assign a specific IP
> address to a particular terminal, DHCP allows you to define that option
> with the following "Custom Defninition";
>
> host WS002 {
> hardware ethernet 00:EE:B0:00:DB:17;
> fixed-address 192.168.0.2;
>
> This can be done for all the terminals in the network and allows the
> administrator to send commands to a particular terminal as needed. By
> creating the corresponding entry in lts.conf;
>
> [ws002]
> SERVER = 10.0.0.1
> XSERVER = auto
> X_MOUSE_PROTOCOL = "PS/2"
> X_MOUSE_DEVICE = "/dev/psaux"
> X_MOUSE_RESOLUTION = 400
> X_MOUSE_BUTTONS = 3
> USE_XFS = N
> LOCAL_APPS = Y
> RUNLEVEL = 5
>
> You can now manage each terminal independantly of the others. However,
> the hosts file created by the ltspcfg wizard reverses the addresses so
> that WS002 is noted as having 192.168.0.2, when the DHCP server has that
> terminal using 192.168.0.254, if you leave the defaults in place.
>
> I'm just pointing out that it would be considerably more convenient if
> that hosts file had the IP addresses listed in reverse order to
> correspond with the natural order that the DHCP server leases them.
> Since the hosts file contains over 250 entries (typical for a total
> subnet), it could take a lot of time to re-write the hosts file to work
> with DHCPD.
The current host file as it is generated corresponds to my experience of the
dhcp server starting at the beginning of the range. Maybe others have noticed
the situation you are experiencing. I don't use the hosts file at all though.
I have ~95 terminals on our network and here is my hosts file
_________________
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
172.16.1.202 xproject3.gouldacademy.internal xproject3
198.202.151.252 mail2
__________________
I find it more convienient to set up forward and reverse dns for all the
terminals on the dns server. You can do this ahead of time based on your
network. Although I haven't implemented it yet, dynamic dns that gets updated
by the dhcp server is even better. Then when you add a new dhcp entry for a
terminal, the dns server gets updated automagically.
-Derek
>
> It would make a lot more sense to modify the file at it's source than to
> modify the file manually for each installation. It would certainly save
> a lot of fingertips! Grin!
>
> >
> > -Derek
> >
>
> Hope that helps to clarify my earlier comments.
>
> --
> Lanman
> Registered Linux User #190712
>
>
--
Derek Dresser
http://network.gouldacademy.org/
Gould Academy
Bethel, ME 04217
(207)824-7700
"What is research but a blind date with knowledge?"
--Will Harvey
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_____________________________________________________________________
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
