On 2022-03-20 8:00 a.m., Tim ignored_mailbox@yahoo.com.au>R. G. Newbury wrote:
edit your /etc/hosts file to give the hdhomerun unit a fixed IP address.
When has the /etc/hosts file ever given anything an IP address?
You are correct, and I am completely wrong. A static address for the computer would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the network config gui to do the same thing.
But everything else needs to be given an address by the router acting as a dhcp server or by a separate dhcp server (which can deliver a static address by using the MAC address of the unit to give the desired address).
Been so long since I have had to do that, I forgot which was the cart and which the mule.
Geoff
On Sun, 20 Mar 2022, R. G. Newbury wrote:
On 2022-03-20 8:00 a.m., Tim ignored_mailbox@yahoo.com.au>R. G. Newbury wrote:
edit your /etc/hosts file to give the hdhomerun unit a fixed IP address.
When has the /etc/hosts file ever given anything an IP address?
You are correct, and I am completely wrong. A static address for the computer would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the network config gui to do the same thing.
Huh?
From man hosts:
SYNOPSIS /etc/hosts
For each host a single line should be present with the following information:
IP_address canonical_hostname [aliases...]
In modern systems, even though the host table has been superseded by DNS, it is still widely used for: bootstrapping Most systems have a small host table containing the name and ad- dress information for important hosts on the local network. This is useful when DNS is not running, for example during sys- tem bootup.
On 3/24/22 20:34, Michael Hennebry wrote:
On Sun, 20 Mar 2022, R. G. Newbury wrote:
On 2022-03-20 8:00 a.m., Tim ignored_mailbox@yahoo.com.au>R. G. Newbury wrote:
edit your /etc/hosts file to give the hdhomerun unit a fixed IP address.
When has the /etc/hosts file ever given anything an IP address?
You are correct, and I am completely wrong. A static address for the computer would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the network config gui to do the same thing.
Huh?
From man hosts:
That's not *giving* anything an IP address. It's assigning a name for the local host to be able to *lookup* an IP address.
R. G. Newbury:
edit your /etc/hosts file to give the hdhomerun unit a fixed IP address.
Tim <ignored_mailbox@yahoo.com.au:
When has the /etc/hosts file ever given anything an IP address?
R. G. Newbury
You are correct, and I am completely wrong. A static address for the computer would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the network config gui to do the same thing.
Michael Hennebry:
Huh?
From man hosts: SYNOPSIS /etc/hosts
For each host a single line should be present with the following information:
IP_address canonical_hostname [aliases...]
Samuel Sieb:
That's not *giving* anything an IP address. It's assigning a name for the local host to be able to *lookup* an IP address.
The above posts are in sequence, how the thread progressed, and the thread was written with the responses in that sequence, with each message containing all that text. Read through them before replying. Don't just read the top one and respond to that. It's already been answered.
Michael, when replying to messages, reply to the right one. Your "huh?" posting should NOT have been to the one where R G Newbury, started going on ifcfg files, but one or two prior where hosts was being misunderstood. By now, that mistake had been addressed and corrected. Don't just hop into a thread, miles later and discuss something that has already passed by. If you want to redundantly add to a thread, go back and reply to the right one.
Samuel, I can't tell if you've misunderstood, or grammar has gone out of whack. The hosts file is doing nothing to enable looking up an IP address just because it's given a name to the local host. Sure, it gives an answer for the things written in it, but it does nothing else. It answers no other questions. It gives no other clues about how to work out other addresses. Naming the local loopback address does nothing to aid looking up other addresses.
On 3/25/22 00:48, Tim via users wrote:
R. G. Newbury:
edit your /etc/hosts file to give the hdhomerun unit a fixed IP address.
Tim <ignored_mailbox@yahoo.com.au:
When has the /etc/hosts file ever given anything an IP address?
R. G. Newbury
You are correct, and I am completely wrong. A static address for the computer would be set by editing /etc/sysconfig/network-scripts/ifcfg-eno1 (or whatever) or using the network config gui to do the same thing.
Michael Hennebry:
Huh?
From man hosts: SYNOPSIS /etc/hosts
For each host a single line should be present with the following information:
IP_address canonical_hostname [aliases...]Samuel Sieb:
That's not *giving* anything an IP address. It's assigning a name for the local host to be able to *lookup* an IP address.
Samuel, I can't tell if you've misunderstood, or grammar has gone out of whack. The hosts file is doing nothing to enable looking up an IP address just because it's given a name to the local host. Sure, it gives an answer for the things written in it, but it does nothing else. It answers no other questions. It gives no other clues about how to work out other addresses. Naming the local loopback address does nothing to aid looking up other addresses.
I know exactly how the thread progressed and I was replying to Michael who seemed to be implying that the hosts file should be giving something an IP address. Maybe he was replying to the wrong thing, but I have no way to know that. I also didn't say anything about a loopback address, so I don't know where that is coming from. Maybe you are misunderstanding what I wrote. The second sentence is directly related to the first one. i.e. The hosts file assigns a name to an IP address so that the local host (the one holding the hosts file) can find that IP address.
It seems I badly misnterpreted the verb "to give".