On 2019-05-06 08:17 PM, Knurpht-openSUSE wrote:
Op dinsdag 7 mei 2019 03:46:30 CEST schreef Darryl Gregorash:
As I was saying, it sets that in the /etc/hosts file. Using YaST > Network Services > Hostnames. Why insist on working on on something that does not work, instead of doing it incl. YaST usage in a way that does work. Things change. Because Carlos wants to give each machine a fixed hostname, and assign its IP by DHCP! That should be possible to do without editing a text file by hand. Things like this are what YaST was designed to do, are
On 2019-05-06 06:21 PM, Knurpht-openSUSE wrote: they not? Yes, but like said, things change. I have a cheap > 12 year old router that can bind/reserve a fixed IP address to a machine's ethernet interface ( IIRC on mac address ). Why does it have to be a variable IP address? Even in my Maybe you should ask that question of Carlos; it's his network. My response to this is, that is what Carlos wants to do, and I don't see any reason why he should be disallowed from doing it. UNIX days ( 1990s, AT&T UNIX System V ) I was tought that a reliable server should have the same IP address all the time and not rely on a DHCP pool. I I rather imagine that his server system does have the same IP all the time; it is the rest of his LAN that he wishes to have dynamic IPs. YaST is not designed to last forever in the same way it started. Networking hasn't. What can be configured in the system should be possible to do in YaST, should it not? Honestly, I don't see the point.
I have a vague mental image of some Boeing software developer saying the same thing in response to the question, "How do you turn MCAS off if it starts to misbehave?" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org