-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thinstation.conf. is not applied #247
Comments
If you review you Tftp logs(sometimes in syslog), you should see the path that the client is actually trying to download files from.
Sent from Yahoo Mail for iPhone
On Wednesday, October 25, 2017, 9:05 AM, mgarciaHWL <notifications@github.com> wrote:
Dears
I'm doing my first steps with Thinstation (5.5.1) , until now I have been using succesfully thinstation with USB drive , but I want go one step ahead a setup an evniroment base in PXE booting TFTP server and multiple configurations files.
Right now I have a working prototype with TFTP server (Synologic NAS) and DHCP server . On the PXE booting the computer can contact successfully with the TFTP server and get the Thinstation image.
My issue comes when I want have a different configurations files , I've done many many test but any off them with successfull result .
What I did?
On the thinstation image I have enabled the following parameters build.conf.
param basename thinstation
param basepath ts5.5
and at Thinstation.conf.builtime
NET_FILE_ENABLED=On
NET_FILE_METHOD=tftp
The second step has been create the thinstation.conf files for get a different settings applied.
I have test with the following files
thinstation.conf.network
thinstation.conf-
thinstation.conf-
We have place the files on the folder ts5.5 and the folder is located on the TFTP root and aslo in boot folder and pxelinux , but at any of them works.
Where I should placed the conf files?
Thank you !!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
You are right. On the TFTP log I see that thinstation is getting the files correctly my mistake is not in the file location.
My error should be in the file or some missconfiguration at buid.config. Below the thinstation.conf.network AUDIO_LEVEL=90 |
as per the TFTP log the files are read correctly , but the config is not applied |
Depending on what you are trying to configure, it might be to late by the time network files are downloaded. Specifically, the network can’t be reconfigured, and storage volumes have already been mounted. What are you trying to change dynamically?
Sent from Yahoo Mail for iPhone
On Tuesday, October 31, 2017, 6:26 AM, mgarciaHWL <notifications@github.com> wrote:
as per the TFTP log the files are read correctly , but the config is not applied
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
First I tried a simple change like hostname (NET_HOSTNAME=ES_2*) , but the final wish is be able to have multiple configuration files define settings like monitor resolution , double screen and mouse left/right buttons. |
The monitor and mouse stuff should work, but the hostname is part of network configuration, so it’s already done, so that you could download files.
Sent from Yahoo Mail for iPhone
On Tuesday, October 31, 2017, 7:10 AM, mgarciaHWL <notifications@github.com> wrote:
First I tried a simple change like hostname (NET_HOSTNAME=ES_2*) , but the final wish is be able to have multiple configuration files define settings like monitor resolution , double screen and mouse left/right buttons.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Do you have any more questions about this issue? |
I had the same problem. Could you add to the documentation the list of options that can (or can not if it’s shorter) be used in thinstation.conf.network? By the way, great job, thanks for the work you are doing in Thinstation. |
A fair request.
…On Sun, Dec 31, 2017 at 7:21 PM, ferfebles ***@***.***> wrote:
I had the same problem.
Could you add to the documentation the list of options that can (or can
not if it’s shorter) be used in thinstation.conf.network?
By the way, great job, thanks for the work you are doing in Thinstation.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#247 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACtufv88I4WM9ro8N0nnUCFlX79okAsAks5tGE9WgaJpZM4QGQfr>
.
|
solved? |
I did add some documentation. I don’t know if it is sufficient.
…Sent from my iPhone
On Jan 13, 2018, at 2:37 AM, trentasis ***@***.***> wrote:
solved?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Much better, thank you. |
Dears
I'm doing my first steps with Thinstation (5.5.1) , until now I have been using succesfully thinstation with USB drive , but I want go one step ahead a setup an evniroment base in PXE booting TFTP server and multiple configurations files.
Right now I have a working prototype with TFTP server (Synologic NAS) and DHCP server . On the PXE booting the computer can contact successfully with the TFTP server and get the Thinstation image.
My issue comes when I want have a different configurations files , I've done many many test but any off them with successfull result .
What I did?
On the thinstation image I have enabled the following parameters build.conf.
param basename thinstation
param basepath ts5.5
and at Thinstation.conf.builtime
NET_FILE_ENABLED=On
NET_FILE_METHOD=tftp
The second step has been create the thinstation.conf files for get a different settings applied.
I have test with the following files
thinstation.conf.network
thinstation.conf-
thinstation.conf-
We have place the files on the folder ts5.5 and the folder is located on the TFTP root and aslo in boot folder and pxelinux , but at any of them works.
Where I should placed the conf files?
Thank you !!
The text was updated successfully, but these errors were encountered: