On 5/7/2015 5:59 PM, Vagrant Cascadian wrote:
> On 2015-05-07, John Hupp wrote:
>> I find that /etc/hosts in the fat client filesystem does not match the
>> /etc/hosts found in the image. It seems that LTSP must be
>> auto-generating one at client boot. In any case /etc/hosts in the fat
>> client
On 2015-05-07, John Hupp wrote:
> I find that /etc/hosts in the fat client filesystem does not match the
> /etc/hosts found in the image. It seems that LTSP must be
> auto-generating one at client boot. In any case /etc/hosts in the fat
> client filesystem has an alias line that resolves "serv
On 5/7/2015 11:53 AM, John Hupp wrote:
On 5/6/2015 1:40 PM, John Hupp wrote:
On 5/5/2015 5:28 PM, John Hupp wrote:
For ease of deployment, I have the LTSP server getting its IP
address by DHCP, and so far I have been able to avoid referring to
it by IP address in various configurations.
But
On 5/6/2015 1:40 PM, John Hupp wrote:
On 5/5/2015 5:28 PM, John Hupp wrote:
For ease of deployment, I have the LTSP server getting its IP address
by DHCP, and so far I have been able to avoid referring to it by IP
address in various configurations.
But trying to set up fat client scanning wit
On 5/5/2015 5:28 PM, John Hupp wrote:
> For ease of deployment, I have the LTSP server getting its IP address
> by DHCP, and so far I have been able to avoid referring to it by IP
> address in various configurations.
>
> But trying to set up fat client scanning with a server-connected
> scanner,
For ease of deployment, I have the LTSP server getting its IP address by
DHCP, and so far I have been able to avoid referring to it by IP address
in various configurations.
But trying to set up fat client scanning with a server-connected
scanner, I have been following this simple tutorial for U
