Thinstation

Wouldn't that be similar to thinstation.conf.network?

Mike

On Tue, 19 Oct 2004, Michael Joyner wrote:

> is there a way to specify a thinstation config by network vs ip?
> 
> i.e.:
> 
> thinstation.conf-192.168.0
> 
> to handle the entire 192.168.0 network?
> 
> vs putting in
> 
> thinstation.conf-192.168.0.1
> .
> .
> thinstation.conf-192.168.0.254
> 
> ???
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
> 

-- 
Thinstation FAQ maintainer
http://thinstation.sourceforge.net
- a light, full featured linux based thin client OS

isn't thinstation.conf.network pulled by all thinstations globally?

I need the ability to specify by subnet a thinstation.config

FYI:

My thinstations are hard-wired to pull their config from 
thinstation-ftp.DOMAIN

The DHCP server is not modified for thinstation use, nor can it be 
(windows centric environment/management)

I use FreeDOS to fdisk+format a HD to 39 megs.
Then copy the thinstation files onto it.
Then run syslinux to enable boot.

project info:

I work at a college.
We are putting thinstations into the dorms
each dorm is on a seperate subnet
I need different dorms to run different session_0 configs to manually 
load balance against my low-end terminal servers


Mike Eriksen wrote:
> Wouldn't that be similar to thinstation.conf.network?
> 
> Mike
> 
> On Tue, 19 Oct 2004, Michael Joyner wrote:
> 
> 
>>is there a way to specify a thinstation config by network vs ip?
>>
>>i.e.:
>>
>>thinstation.conf-192.168.0
>>
>>to handle the entire 192.168.0 network?
>>
>>vs putting in
>>
>>thinstation.conf-192.168.0.1
>>.
>>.
>>thinstation.conf-192.168.0.254
>>
>>???
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>>Use IT products in your business? Tell us what you think of them. Give us
>>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>_______________________________________________
>>Thinstation-general mailing list
>>Thinstation-general@...
>>https://lists.sourceforge.net/lists/listinfo/thinstation-general
>>
> 
>

"Globally" here means, to the best of my knowledge, the subnet. TFPT can't 
be routed - it's a broadcast. But you do need a TFTPD per subnet.

Mike

On Tue, 19 Oct 2004, Michael Joyner wrote:

> isn't thinstation.conf.network pulled by all thinstations globally?
> 
> I need the ability to specify by subnet a thinstation.config
> 
> FYI:
> 
> My thinstations are hard-wired to pull their config from 
> thinstation-ftp.DOMAIN
> 
> The DHCP server is not modified for thinstation use, nor can it be 
> (windows centric environment/management)
> 
> I use FreeDOS to fdisk+format a HD to 39 megs.
> Then copy the thinstation files onto it.
> Then run syslinux to enable boot.
> 
> project info:
> 
> I work at a college.
> We are putting thinstations into the dorms
> each dorm is on a seperate subnet
> I need different dorms to run different session_0 configs to manually 
> load balance against my low-end terminal servers
> 
> 
> Mike Eriksen wrote:
> > Wouldn't that be similar to thinstation.conf.network?
> > 
> > Mike
> > 
> > On Tue, 19 Oct 2004, Michael Joyner wrote:
> > 
> > 
> >>is there a way to specify a thinstation config by network vs ip?
> >>
> >>i.e.:
> >>
> >>thinstation.conf-192.168.0
> >>
> >>to handle the entire 192.168.0 network?
> >>
> >>vs putting in
> >>
> >>thinstation.conf-192.168.0.1
> >>.
> >>.
> >>thinstation.conf-192.168.0.254
> >>
> >>???
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> >>Use IT products in your business? Tell us what you think of them. Give us
> >>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> >>http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >>_______________________________________________
> >>Thinstation-general mailing list
> >>Thinstation-general@...
> >>https://lists.sourceforge.net/lists/listinfo/thinstation-general
> >>
> > 
> > 
> 

-- 
Thinstation FAQ maintainer
http://thinstation.sourceforge.net
- a light, full featured linux based thin client OS

So use several tftp servers, letting each dhcp range specify their own tftp 
with different thinstation.conf.network files.

Having subnet-conf files would be easier for you, I know, but where does it 
end then? Someone else would probably like to use different settings for 
computers with mac adresses in a certain range (certain NIC manufacturers) 
or some other characteristics.

Klaus Bech Jensen
IT-koordinator
Aaskov Kommune

----- Original Message ----- 
From: "Michael Joyner" <mjoyner@...>
To: "Mike Eriksen" <kme3@...>
Cc: <thinstation-general@...>
Sent: Tuesday, October 19, 2004 9:11 PM
Subject: Re: [Thinstation-general] tftp thinstation config


> isn't thinstation.conf.network pulled by all thinstations globally?
>
> I need the ability to specify by subnet a thinstation.config
>
> FYI:
>
> My thinstations are hard-wired to pull their config from 
> thinstation-ftp.DOMAIN
>
> The DHCP server is not modified for thinstation use, nor can it be 
> (windows centric environment/management)
>
> I use FreeDOS to fdisk+format a HD to 39 megs.
> Then copy the thinstation files onto it.
> Then run syslinux to enable boot.
>
> project info:
>
> I work at a college.
> We are putting thinstations into the dorms
> each dorm is on a seperate subnet
> I need different dorms to run different session_0 configs to manually load 
> balance against my low-end terminal servers
>
>
> Mike Eriksen wrote:
>> Wouldn't that be similar to thinstation.conf.network?
>>
>> Mike
>>
>> On Tue, 19 Oct 2004, Michael Joyner wrote:
>>
>>
>>>is there a way to specify a thinstation config by network vs ip?
>>>
>>>i.e.:
>>>
>>>thinstation.conf-192.168.0
>>>
>>>to handle the entire 192.168.0 network?
>>>
>>>vs putting in
>>>
>>>thinstation.conf-192.168.0.1
>>>.
>>>.
>>>thinstation.conf-192.168.0.254
>>>
>>>???
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>>>Use IT products in your business? Tell us what you think of them. Give us
>>>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
>>>more
>>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>>_______________________________________________
>>>Thinstation-general mailing list
>>>Thinstation-general@...
>>>https://lists.sourceforge.net/lists/listinfo/thinstation-general
>>>
>>
>>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>

Isn't that what thinstation.hosts is supposed to be for?

As you have 'hardwired' each PC, can't you just assign them to a group per dorm
and have a thinstation.conf.group-<dorm> file for each dorm?

Trevor B

Quoting Klaus Bech Jensen <kbj@...>:

> So use several tftp servers, letting each dhcp range specify their own tftp
> with different thinstation.conf.network files.
>
> Having subnet-conf files would be easier for you, I know, but where does it
> end then? Someone else would probably like to use different settings for
> computers with mac adresses in a certain range (certain NIC manufacturers)
> or some other characteristics.
>
> Klaus Bech Jensen
> IT-koordinator
> Aaskov Kommune
>
> ----- Original Message -----
> From: "Michael Joyner" <mjoyner@...>
> To: "Mike Eriksen" <kme3@...>
> Cc: <thinstation-general@...>
> Sent: Tuesday, October 19, 2004 9:11 PM
> Subject: Re: [Thinstation-general] tftp thinstation config
>
>
> > isn't thinstation.conf.network pulled by all thinstations globally?
> >
> > I need the ability to specify by subnet a thinstation.config
> >
> > FYI:
> >
> > My thinstations are hard-wired to pull their config from
> > thinstation-ftp.DOMAIN
> >
> > The DHCP server is not modified for thinstation use, nor can it be
> > (windows centric environment/management)
> >
> > I use FreeDOS to fdisk+format a HD to 39 megs.
> > Then copy the thinstation files onto it.
> > Then run syslinux to enable boot.
> >
> > project info:
> >
> > I work at a college.
> > We are putting thinstations into the dorms
> > each dorm is on a seperate subnet
> > I need different dorms to run different session_0 configs to manually load
> > balance against my low-end terminal servers
> >
> >
> > Mike Eriksen wrote:
> >> Wouldn't that be similar to thinstation.conf.network?
> >>
> >> Mike
> >>
> >> On Tue, 19 Oct 2004, Michael Joyner wrote:
> >>
> >>
> >>>is there a way to specify a thinstation config by network vs ip?
> >>>
> >>>i.e.:
> >>>
> >>>thinstation.conf-192.168.0
> >>>
> >>>to handle the entire 192.168.0 network?
> >>>
> >>>vs putting in
> >>>
> >>>thinstation.conf-192.168.0.1
> >>>.
> >>>.
> >>>thinstation.conf-192.168.0.254
> >>>
> >>>???
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> >>>Use IT products in your business? Tell us what you think of them. Give us
> >>>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> >>>more
> >>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >>>_______________________________________________
> >>>Thinstation-general mailing list
> >>>Thinstation-general@...
> >>>https://lists.sourceforge.net/lists/listinfo/thinstation-general
> >>>
> >>
> >>
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> > Use IT products in your business? Tell us what you think of them. Give us
> > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
> > more
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Thinstation-general mailing list
> > Thinstation-general@...
> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>


>----------------------------
Trevor Batley
trevor_AT_batley.id.au

Mike Eriksen wrote:
> "Globally" here means, to the best of my knowledge, the subnet. TFPT can't 
> be routed - it's a broadcast. But you do need a TFTPD per subnet.

Hrm... it seems to be working fine here across subnets.
I am using a single tftp server, the tftp settings are not set by DHCP 
(the ftp server hostname is hardwired into the image) and I do not have 
the option to change the DHCP server settings

Klaus Bech Jensen wrote:
> So use several tftp servers, letting each dhcp range specify their own 
> tftp with different thinstation.conf.network files.
Using several tftp servers is not an option.
The clients have a hardwired tftp server.
> 
> Having subnet-conf files would be easier for you, I know, but where does 
> it end then? Someone else would probably like to use different settings 
> for computers with mac adresses in a certain range (certain NIC 
> manufacturers) or some other characteristics.
>

Trevor Batley wrote:
> Isn't that what thinstation.hosts is supposed to be for?

Is there a way to specify a subnet for grouping in the thinstation.hosts?

I need the units to "automagically" pull in their settings according to 
the subnet I place them in, especially as I expect them to be moved 
about periodically and most of what I am doing here now w/ thinclients 
is beyond all personnel in the IT department except me.

> 
> As you have 'hardwired' each PC, can't you just assign them to a group per dorm
> and have a thinstation.conf.group-<dorm> file for each dorm?
> 
> Trevor B
> 
> Quoting Klaus Bech Jensen <kbj@...>:

On Tue, 19 Oct 2004, Michael Joyner wrote:

> Mike Eriksen wrote:
> > "Globally" here means, to the best of my knowledge, the subnet. TFPT can't 
> > be routed - it's a broadcast. But you do need a TFTPD per subnet.
> 
> Hrm... it seems to be working fine here across subnets.
> I am using a single tftp server, the tftp settings are not set by DHCP 
> (the ftp server hostname is hardwired into the image) and I do not have 
> the option to change the DHCP server settings

Maybe we have a slight disagreement on terms. To me a "subnet" is someting 
you can broadcast within. Outside you can't broadcast, thus you can't 
reach a TFTPD outside your subnet.

Mike
-- 
Thinstation FAQ maintainer
http://thinstation.sourceforge.net
- a light, full featured linux based thin client OS

Quoting Michael Joyner <mjoyner@...>:

> Trevor Batley wrote:
> > Isn't that what thinstation.hosts is supposed to be for?
>
> Is there a way to specify a subnet for grouping in the thinstation.hosts?

Not that I know of. thinstation.hosts is based on mac addresses.

Your real issue is not having adequate access to the dhcp server settings*,
which is where I would be putting the groupings (I am assuming that all the
dorms use the same dhcp server....). If you put subnet settings anywhere else
you will have to keep those in sync with the dhcp server etc. etc.

Good Luck on finding a solution.

Trevor B
PS. *I must admit to not knowing what you can/can't do with M$ dhcp
>
> I need the units to "automagically" pull in their settings according to
> the subnet I place them in, especially as I expect them to be moved
> about periodically and most of what I am doing here now w/ thinclients
> is beyond all personnel in the IT department except me.
>
> >
> > As you have 'hardwired' each PC, can't you just assign them to a group per
> dorm
> > and have a thinstation.conf.group-<dorm> file for each dorm?
> >
> > Trevor B
> >
> > Quoting Klaus Bech Jensen <kbj@...>:
>


>----------------------------
Trevor Batley
trevor_AT_batley.id.au

Michael,

it may be easier in your case to hack the /packages/base/etc/init.d/network
script (in the get_config_files() function) and have it look for a
thinstation.conf-<subnet> file before the <IP> one.

Trevor B

Quoting Michael Joyner <mjoyner@...>:

> Trevor Batley wrote:
> > Isn't that what thinstation.hosts is supposed to be for?
>
> Is there a way to specify a subnet for grouping in the thinstation.hosts?
>
> I need the units to "automagically" pull in their settings according to
> the subnet I place them in, especially as I expect them to be moved
> about periodically and most of what I am doing here now w/ thinclients
> is beyond all personnel in the IT department except me.
>
> >
> > As you have 'hardwired' each PC, can't you just assign them to a group per
> dorm
> > and have a thinstation.conf.group-<dorm> file for each dorm?
> >
> > Trevor B
> >
> > Quoting Klaus Bech Jensen <kbj@...>:
>


>----------------------------
Trevor Batley
trevor_AT_batley.id.au

Mike Eriksen wrote:
> 
> Maybe we have a slight disagreement on terms. To me a "subnet" is someting 
> you can broadcast within. Outside you can't broadcast, thus you can't 
> reach a TFTPD outside your subnet.

Incorrect, you can reach tftp servers across routers/subnets/broadcast 
segments.

Trevor Batley wrote:
> Michael,
> 
> it may be easier in your case to hack the /packages/base/etc/init.d/network
> script (in the get_config_files() function) and have it look for a
> thinstation.conf-<subnet> file before the <IP> one.
> 
> 
How would one go about doing this with TS-O-MATIC ?

Have a nice chat with someone who is running TS-O-Matic (such as me, for =
instance...).

Klaus Bech Jensen, IT-koordinator
(INTP)
Aaskov Kommune
Tlf. 99992300 - Dir. 99992354


-----Oprindelig meddelelse-----
Fra: Michael Joyner [mailto:mjoyner@...]
Sendt: 20. oktober 2004 14:18
Til: Trevor Batley
Cc: thinstation-general@...
Emne: Re: [Thinstation-general] tftp thinstation config

Trevor Batley wrote:
> Michael,
>=20
> it may be easier in your case to hack the =
/packages/base/etc/init.d/network
> script (in the get_config_files() function) and have it look for a
> thinstation.conf-<subnet> file before the <IP> one.
>=20
>=20
How would one go about doing this with TS-O-MATIC ?

-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give =
us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out =
more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Thinstation-general mailing list
Thinstation-general@...
https://lists.sourceforge.net/lists/listinfo/thinstation-general

Ah,

that would be an issue..... :-) Have you talked to Klaus (as in his e-mail)?

To do real tricky stuff, it is much easier to have your own version of linux,
where you can alter some of the core parts of thinstation and build your own.

If you can't play in your own sandbox, then I suggest that you ask someone who
can to try the changes for you (I sort of got the impression that you had
access /knowledge of linux....). It would be easier if you had determined the
changes required before you ask (I have attached a copy of the build script for
beta8 for your info).

Trevor B
PS. I can also setup a TS-O-Matic with those changes for you.

Quoting Michael Joyner <mjoyner@...>:

> Trevor Batley wrote:
> > Michael,
> >
> > it may be easier in your case to hack the /packages/base/etc/init.d/network
> > script (in the get_config_files() function) and have it look for a
> > thinstation.conf-<subnet> file before the <IP> one.
> >
> >
> How would one go about doing this with TS-O-MATIC ?
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Thinstation-general mailing list
> Thinstation-general@...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>


>----------------------------
Trevor Batley
trevor_AT_batley.id.au

Maybe this time I'll attach the file you are interested in ;-)

Quoting Trevor Batley <trevor@...>:

> Ah,
>
> that would be an issue..... :-) Have you talked to Klaus (as in his e-mail)?
>
> To do real tricky stuff, it is much easier to have your own version of linux,
> where you can alter some of the core parts of thinstation and build your own.
>
> If you can't play in your own sandbox, then I suggest that you ask someone
> who
> can to try the changes for you (I sort of got the impression that you had
> access /knowledge of linux....). It would be easier if you had determined the
> changes required before you ask (I have attached a copy of the build script
> for
> beta8 for your info).
>
> Trevor B
> PS. I can also setup a TS-O-Matic with those changes for you.
>
> Quoting Michael Joyner <mjoyner@...>:
>
> > Trevor Batley wrote:
> > > Michael,
> > >
> > > it may be easier in your case to hack the
> /packages/base/etc/init.d/network
> > > script (in the get_config_files() function) and have it look for a
> > > thinstation.conf-<subnet> file before the <IP> one.
> > >
> > >
> > How would one go about doing this with TS-O-MATIC ?
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> > Use IT products in your business? Tell us what you think of them. Give us
> > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> > http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > _______________________________________________
> > Thinstation-general mailing list
> > Thinstation-general@...
> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
> >
>
>
> >----------------------------
> Trevor Batley
> trevor_AT_batley.id.au


>----------------------------
Trevor Batley
trevor_AT_batley.id.au

Trevor Batley wrote:
> Ah,
> 
> that would be an issue..... :-) Have you talked to Klaus (as in his e-mail)?
indeed. :)
I have a response in my inbox right this second. :)
> 
> To do real tricky stuff, it is much easier to have your own version of linux,
> where you can alter some of the core parts of thinstation and build your own.
Ah, but one of my goals is to keep it distribution un-altered as much as 
possible.

> 
> If you can't play in your own sandbox, then I suggest that you ask someone who
> can to try the changes for you
:)

  (I sort of got the impression that you had
> access /knowledge of linux....).
FreeBSD

  It would be easier if you had determined the
> changes required before you ask (I have attached a copy of the build script for
> beta8 for your info).
I downloaded and extracted the 2.0? and looked at the init scripts 
looking for some sort of functionality to accomplish the goal, but alas, 
didn't see it, which prompted my question to the list.

> 
> Trevor B
> PS. I can also setup a TS-O-Matic with those changes for you.
Klaus has done so. Thanks!
>

Trevor Batley wrote:
> Maybe this time I'll attach the file you are interested in ;-)
> 
:)