hostname
Posted: Tue 31 Jan 2012, 20:17
Hi Shinobar
Since your introduction with your FirstRUN it has become a startup "statue" to single screen localization as many have taken advantage of your design.
As a result, some, many, most new Pups from Puppyland have tended to adopt or attempt duplication of FirstRUN, alias "Personalize Settings".
Because of this all 64bit and several 32bit PUPs will boot from CD all the way to desktop to complete localization versus stopping at text mode screens before getting to desktop.
One of the great benefits to your effort has been for users to set the local PC's name (hostname).
Here's an issue that I think FirstRUN can make consistent in its implementation for all in Puppyland. And, I'll begin by stating the issue and sharing who has addressed it, individually and perhaps differently.
Issue: Setting of the hostname properly in ALL system fields for system/subsystem application use. There are actually 5 system parms/fields that reflect the hostname. I see these by executing the following commands
# hostname
Slacko-LaptopP3
# echo $HOSTNAME
Slacko-LaptopP3
# cat /etc/hosts
127.0.0.1 localhost Slacko-LaptopP3
192.168.1.1 pc2
192.168.1.2 pc3
192.168.1.3 pc4
# cat /etc/hostname
Slacko-LaptopP3
I had found that is the cases where FirstRUN is being used, it was important to exit the desktop and issue a logout before restarting the desktop via xwin.
This is evidence that shows what FirstRUN provides during its operation after initial system start.
But, here's the problem. The above shows ALL fields to be set properly, resulting from it being changed in FirstRUN, But, there is some in-memory remnants of the original hostname that remain for system use UNTIL A LOGOUT OCCURS! When a logout occurs, then all in-memory as well as these above parms are properly set for any system/subsystem/application use as it carries out operations on behalf of the user.
So, my question is as following
Can/should/would FirstRUN address the hostname issue by a "logout and xwin restart" whenever a hostname change is entered in the hostname field of FirstRUN.
If this is done, the total community benefits because there will be a consistent fashion for handling of desktop startup for all distro builders and users, alike.
Please weigh a practical solution for this in FirstRUN. And, please keep in mind that a logout seems be a key ingredient of proper settings for all hostname fields.
Also, remember that 01Micko, Playdayz, and TaZoC have addressed this...but in different ways. A common approach would remove the need for specific, independent designs to address this issue.
In summary, i feel that should any user use FirstRun to set/reset the PC's name (hostname), some utility (FirstRUN) should schedule an immediate Logout and restart of the desktop when the OK button is clicked in FirstRUN.
Thanks in advance.
Since your introduction with your FirstRUN it has become a startup "statue" to single screen localization as many have taken advantage of your design.
As a result, some, many, most new Pups from Puppyland have tended to adopt or attempt duplication of FirstRUN, alias "Personalize Settings".
Because of this all 64bit and several 32bit PUPs will boot from CD all the way to desktop to complete localization versus stopping at text mode screens before getting to desktop.
One of the great benefits to your effort has been for users to set the local PC's name (hostname).
Here's an issue that I think FirstRUN can make consistent in its implementation for all in Puppyland. And, I'll begin by stating the issue and sharing who has addressed it, individually and perhaps differently.
Issue: Setting of the hostname properly in ALL system fields for system/subsystem application use. There are actually 5 system parms/fields that reflect the hostname. I see these by executing the following commands
# hostname
Slacko-LaptopP3
# echo $HOSTNAME
Slacko-LaptopP3
# cat /etc/hosts
127.0.0.1 localhost Slacko-LaptopP3
192.168.1.1 pc2
192.168.1.2 pc3
192.168.1.3 pc4
# cat /etc/hostname
Slacko-LaptopP3
I had found that is the cases where FirstRUN is being used, it was important to exit the desktop and issue a logout before restarting the desktop via xwin.
This is evidence that shows what FirstRUN provides during its operation after initial system start.
But, here's the problem. The above shows ALL fields to be set properly, resulting from it being changed in FirstRUN, But, there is some in-memory remnants of the original hostname that remain for system use UNTIL A LOGOUT OCCURS! When a logout occurs, then all in-memory as well as these above parms are properly set for any system/subsystem/application use as it carries out operations on behalf of the user.
- TaZoC solved it one way
- Playdayz solved it a different way
- 01Micko solved it in a different way
So, my question is as following
Can/should/would FirstRUN address the hostname issue by a "logout and xwin restart" whenever a hostname change is entered in the hostname field of FirstRUN.
If this is done, the total community benefits because there will be a consistent fashion for handling of desktop startup for all distro builders and users, alike.
Please weigh a practical solution for this in FirstRUN. And, please keep in mind that a logout seems be a key ingredient of proper settings for all hostname fields.
Also, remember that 01Micko, Playdayz, and TaZoC have addressed this...but in different ways. A common approach would remove the need for specific, independent designs to address this issue.
In summary, i feel that should any user use FirstRun to set/reset the PC's name (hostname), some utility (FirstRUN) should schedule an immediate Logout and restart of the desktop when the OK button is clicked in FirstRUN.
Thanks in advance.
