@Rcrsn51 seems focused merely on SAMBA, yet I have repeated said ROX as well.

Let me make my point again. The current situation, where "puppypc" is used everywhere in the machine, works perfectly well. It only becomes an issue when you start changing the hostname. If a Samba or web server needs to broadcast a name, that name can be easily declared in its own configuration.

IMHO, there is no practical need to do anything else. Other than adhering to some conventional wisdom about hostnames, what is the advantage to changing the status quo?

As we are progressing thru this discussion, I think it may be important to note the following;
Puppy has become (in my mind) a major OS. But its a little different in its implementation.

ALL other major OSes are geared toward HDD installation. Puppy has brought to the table a system which is RAM + LIve Media based. So how this hostname issue is handled from the major OS standpoint is a little different than how it may get addressed in PUPPYland

Microsoft, AIX, HPUX, RedHAT, Suse, Ubuntu, etc all ask at system installation time what the system name (HOSTNAME) is to be, then they set all appropriate fields accordingly. 01Micko+JamesBond has suggested options that this be set during Live media boot or at Live media shutdown. (Boot may be a preferred method with preservation at shutdown)

All magor OSes seem to have "hooked/hacked/made adjustments" in hostname processing so that when the hostname function is activated by the roor user to change the system's hostname, all of the sytem's fields are immediately updated accordingly. This is why we are engaged in this discussion. How should we get this OS, Puppy, to do this accordingly too.

So we, here, are talking about 2 issues.

The hostname command processing in Puppy

the system fields affected by hostname command use.

Hope this helps_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

[ ... Other than adhering to some conventional wisdom about hostnames, what is the advantage to changing the status quo?

To be perfectly clear is to ignore this problem area? No disrespect, but, I hope this is not what you are advocating. Further, we are NOT changing status_quo. This thread is about a problem area in PUPPY. Not status-quo.

I have never subscribed to the "every man (application) for himself" in systems development. I have found it better to solve things that are good for everyone at the sytem level.

You are already aware of the ROX problem.

The advantage is "consistent system information" for all internal applications use. We do NOT have that today. We have inconsistent information in the system.

I have NOT suggested that this is a high priority problem in thet system operation will stop. ROX might not perform optimumly or some other application may read inconsistent information. But, It is not going to magically disappear. Its needs some of our attention.

Hope this helps_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

I have never subscribed to the "every man (application) for himself" in systems development. I have found it better to solve things that are good for everyone at the sytem level.

And I subscribe to the philosophy that the simplest solution is usually the best. You want to change the identifier in several locations, requiring a bunch of code. I want to change the identifier in one location, requiring no additional code.

I have never subscribed to the "every man (application) for himself" in systems development. I have found it better to solve things that are good for everyone at the sytem level.

And I subscribe to the philosophy that the simplest solution is usually the best. You want to change the identifier in several locations, requiring a bunch of code. I want to change the identifier in one location, requiring no additional code.

Both methods would get you effectively the same result.

Then, I think my friend we agree that something should be done, effectively. Thanks for clarifying that.

Although, I still don't understand how you get something for nothing. Are you offering a fix for this that we missed. How can you fix the hostname command to bring the system files into consistency? Can you share how you would do this?

Thanks in advance._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Starting with 01Micko's approach we would arrinve at desktop with a PC on the LAN that is unique. This would suffice for most newbies who would NOT take the time or effort to change the hostname from the defautl that may ve offered on screen to them.

It this is done on initial boot (pfix=ram) there could also be an option somewhere which would force/ask the booting user to enter/change a name for this booting PC. This would, I thnk address 90& of situations for having the system named and the user to know what the name of the booting PC is. As well, all system applications would have consistent information no matter which field they would use internally for their ooperation. Were this to be done, we would cover most situations of IDing the system hostname fields and would significantly reduce/negaate a need to use the hostname command once the system is at desktop.

This seems reasonable.

Does anyone see a problem with an approach like that?_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

To make hostname=HOSTNAME for ROX, we need to reboot PC after the hostname is changed.
Rebooting X is not enough because the script /usr/bin/xwin does not read /etc/profile at reboot.
I am not sure it causes problem, but i think there is a hint.

To make hostname=HOSTNAME for ROX, we need to reboot PC after the hostname is changed.
Rebooting X is not enough because the script /usr/bin/xwin does not read /etc/profile at reboot.
I am not sure it causes problem, but i think there is a hint.

BTW, connecting tools for puppy should be improved to use the hostname provided from the DHCP service.

Hi Shinobar. Thanks for helping.

Couple of points.

#1
All (most) consumer routers do NOT supply a hostname to a PC when issuing IP personality to the PC.

#2 - Is this a possible hint to a solution?
I did find something of interest, when running latest PUP268.

The system boots to FirstRun/Personalize Settings.

I changed the hostname field from puppypc to Luci268-01

I clicked OK to confirm

System gave the normal restart desktop message

I then selected SHUTDOWN > Exit to Prompt

At the prompt, I typed logout

at the next prompt, I typed xwin

desktop restarted

I clicked console icon on desktop, typed "echo $HOSTNAME" and was surprised to find that the hostname is updated by the system to Luci268-01.

This works on this Puppy by Playdayz. I am not sure how many other PUP distros this would work on.

I run a LIve media environment, and this is verifiable by anyone for Pup268. I am not sure how many other PUPs that use FirstRUN to go to desktop, but those PUP distros, who use Personalize Settings may also have the same benefit that its has with Playdayz's-01Micko's distro

Is this a hint to solution?

So, it seems that changes made in the Personalize Settings Utility MAY accomplish the job whenever it run IFF it can accomplish a logout and xwin when the hostname is changed. Can FirstRun be modified to do this when the hostname is changed?

This may be a solution that CAN be incorporated or modeled for all PUPs. If so,_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

That won't upset the apple cart if the user has changed "localhost" and added addresses to /etc/hosts (though at the stage it's run that's extremely unlikely to have happened anyway, unless some one has done a remaster/rebuild)

... here is ... /etc/rc.d/rc.sysint file just after rc.update is run ... That won't upset the apple cart if the user has changed "localhost" and added addresses to /etc/hosts (though at the stage it's run that's extremely unlikely to have happened anyway, unless some one has done a remaster/rebuild) ... hostname is persistent after a reboot. ...

This is well thought-thru, well structured, and well-presented here for understanding.

What 01Micko presents here, will work not only for Live media who are booting for the first-time, but also for startup tools similar to what @Shinobar's FirstRUN/Personalize Settings does for first-boot or for some subsequext use. It paves the way for any distro developer to use other desktop tools or applications that rely on consistent system information in this area.

Does anyone see any downsides? I don't see any at this time.

Help if you can. And Thanks again @01Micko for your level on LAN understanding and your OTB addressing this for all of us._________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

LightHOUSE64 PUP is running a "Modified" version of Personalize Settings on 64bit PCs.which does everything we are discussing in this thread.

As most of us know, Personalize Settings is becoming an user appealing startup utility for doing some very basic system needs on the Puppy desktop; instead of continually stopping during boot processing to ask users questions for system settings needs. This approach is practical as well as appealing while giving any user a Menu item that he can return to whenever needed to make some setting change.

I don't know what he's done as 64bit Linux "MAY" offer something 32bit does not, but, his Personalize Settings updates ALL known needs for hostname in the system when you click OK. This means that every field that a hostname change should address is being addressed, correctly, all within the running desktop!. Maybe he found something in Personalize Settings that handles this for all system fields-files that is overlooked in 32bit PC's use of Personalize Settings.

I am appealing to TazOC for some insights that could be applied in the 32bit community (or ALL PUPs, in general).

Hope this helps

Personalize Settings in LightHouse64.png

Description

64bit LightHouse64

Filesize

103.12 KB

Viewed

987 Time(s)

After PS completion.png

Description

ALL pertinent fields are accurate

Filesize

32.15 KB

Viewed

1040 Time(s)

_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum