Thin Client /etc/hosts entry

[Mickey Moore]

How will you use the DNS names? To ssh into one of the terminals you will first have to ssh into the LTSP which they are connected to. Since you will be creating the session from the LTSP to a client it should be sufficient to have the names in the /etc/host file of the LTSP server. You can assign specific IP addresses to specific devices by assigning it via MAC address in the DHCPD.conf on the LTSP. At least it is not clear to me how you would know a specific thin-client name/address ahead of time any other way. 


--- On Tue, 1/13/09, M Rathburn <stretchem at gmail.com> wrote:

> From: M Rathburn <stretchem at gmail.com>
> Subject: RE: Thin Client /etc/hosts entry
> To: "'Edubuntu Users Group'" <edubuntu-users at lists.ubuntu.com>
> Date: Tuesday, January 13, 2009, 2:47 PM
> ________________________________
> 
> 	From: ekul taylor [mailto:ekul.taylor at gmail.com] 
> 	Sent: Monday, January 12, 2009 4:40 PM
> 	To: stretchem at gmail.com
> 	Cc: Edubuntu Users Group
> 	Subject: Re: Thin Client /etc/hosts entry
> 	
> 	
> 	I'm not 100% sure but you would either need to write a
> startup
> script to add them each boot or (more ideally) add the
> terminal server as a
> dns server in the dhcp settings and add any hosts you want
> to bind on the
> terminal server
> 	
> 	
> 	On Mon, Jan 12, 2009 at 4:30 PM, M Rathburn
> <stretchem at gmail.com>
> wrote:
> 	
> 
> 		Edubuntu 8.10 on amd64
> 		
> 		How do I make entries into the /etc/hosts for PXE i386
> thin
> clients?  I
> 		noticed that when I chrooted and tried to edit the file,
> it
> shows:
> 		
> 		#This is a ltsp chroot and this file will be rewritten in
> boot process
> 		#of terminal.
> 		127.0.0.1 localhost
> 		
> 		So where would I make the entries so they'll
> propagate to
> the TC's?
> 		
> 		Thanks.
> ------------------------------------
> 
> On the server, /etc/resolv.conf looks like this:
> 
> domain childrenfirstflorida.org
> search childrenfirstflorida.org
> nameserver 192.168.0.254
> nameserver 192.168.1.1
> 
> 
> The 0.254 address is the LTSP server, and the 1.1 address
> is the internet
> router.  When a thin client boots up, it's
> /etc/resolv.conf looks like this:
> 
> domain childrenfirstflorida.org
> search childrenfirstflorida.org
> nameserver 192.168.1.1
> 
> and it's /etc/hosts looks like this:
> 
> 127.0.0.1 localhost
> 127.0.0.2 CFF-1014
> 192.168.0.254 server
> 
> 
> The server's dhcpd.conf portion that matters looks like
> this:
> 
> option domain-name "childrenfirstflorida.org";
> option domain-name-servers 192.168.0.254, 192.168.1.1;
> option broadcast-address 192.168.0.255;
> option routers 192.168.0.254;
>  
> 
> The server's /etc/hosts looks like this:
> 
> 127.0.0.1       localhost
> 127.0.1.1       ltsp1.childrenfirstflorida.org  ltsp1
> 192.168.1.36    portal.childrenfirstflorida.org
> 
> # For thin clients.
> 192.168.0.14    CFF-1014
> 192.168.0.12    FPS-1012
> 192.168.0.16    FPS-1016
> 
> 
> It's that 'portal.scholarshipfunding.org'
> portion that I need to route
> locally first, since it's on the same LAN (don't
> want to go out and back
> in).  How do I make it so that a thin client's
> /etc/hosts has that entry for
> '192.168.1.36   portal.childrenfirstflorida.org',
> OR it's default nameserver
> is 192.168.0.254 and secondary nameserver is 192.168.1.1?
> 
> Thanks.
> 
> 
> -- 
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users