On 1/31/22 02:11, Tim via users wrote:
And at some stage people are going to stop making devices look for DHCP
and fallback on Avahi, they'll decide to simplify things and just
follow the latest fad. You'll end up with a gadget that only does
Avahi.
You have this quite confused. DHCP and mdns
On Tue, 2022-02-01 at 22:38 +, Barry wrote:
> I thought that mDNS that Avahi implements only uses multicast on the
> LAN. You could set up multicast across multiple LAN segments.
>
> How does that end up getting answers from the internet?
> Especially when all ISPs block multicast it seems.
> On 1 Feb 2022, at 18:59, Tim via users wrote:
>
> If it doesn't already know the IP, then your computer can end up trying
> to query public servers outside your LAN for the answers.
I thought that mDNS that Avahi implements only uses multicast on the LAN.
You could set up multicast across mu
On Mon, 2022-01-31 at 21:52 +1030, Tim via users wrote:
> ".arpa" is owned, and they're able to set rules about its usage (so
> home.arpa was possible). Trying to set up a new top level domain,
> such as .home, would require getting a plethora of organisations to
> agree to something new, and requ
On 1/31/22 06:27, Ed Greshko wrote:
I needed no such change to my F35's host file for it to function
properly. Probably will never find out why
yours did.
Probably because the server configuration was modified. Robert reported:
> On the server:
> [plugh-3g ~]# cat /sys/module/nfsd/paramete
Ed Greshko wrote:
> On 31/01/2022 14:39, Tim via users wrote:
>> Not long ago, 16 Nov 2021, I had one of their email press releases
>> stating that the latest version of 8 had just been released and that
>> it's EOL would be 31 Dec 2021. I had to check that wasn't a typo.
>
> I do need to see wha
On 31/01/2022 22:19, Robert Nichols wrote:
On 1/30/22 11:24 PM, Ed Greshko wrote:
On 31/01/2022 00:13, Robert Nichols wrote:
FINALLY!!
I can get it all to work by putting "fedora.local" in /etc/hostname _and_ editing
/etc/hosts to have "fedora.local" as the _first_ name for 127.0.0.1 .
I ins
On 1/30/22 11:24 PM, Ed Greshko wrote:
On 31/01/2022 00:13, Robert Nichols wrote:
FINALLY!!
I can get it all to work by putting "fedora.local" in /etc/hostname _and_ editing
/etc/hosts to have "fedora.local" as the _first_ name for 127.0.0.1 .
I installed a Centos7 system and during the insta
On Mon, 2022-01-31 at 20:41 +1030, Tim via users wrote:
> Linux had an interesting quirk of using ".localdomain" as its LAN
> domain (at least on the few distros I've played with). Microsoft may
> have used .mshome or .home (as my router uses, actually it also uses
> .router, not that it tells you
On Mon, 2022-01-31 at 16:59 +0800, Ed Greshko wrote:
> I don't know much about Avahi/Bonjour/mDNS/ZeroConf I think it is/was
> a way to shoehorn Linux into some Windows environments. I hardly had
> to deal with that.
>
> I also didn't deal much with SMB as only ever had a couple of Windows
> syst
On 31/01/2022 14:39, Tim via users wrote:
On Mon, 2022-01-31 at 13:24 +0800, Ed Greshko wrote:
I installed a Centos7 system and during the install process called it
fedora.local. By default this was placed in etc/hostname.
Wasn't ".local" and Avahi/Bonjour/mDNS/ZeroConf non-traditional
DHCP an
On Mon, 2022-01-31 at 13:24 +0800, Ed Greshko wrote:
> I installed a Centos7 system and during the install process called it
> fedora.local. By default this was placed in etc/hostname.
Wasn't ".local" and Avahi/Bonjour/mDNS/ZeroConf non-traditional
DHCP and DNS thing? Does it still require diffe
On 31/01/2022 00:13, Robert Nichols wrote:
FINALLY!!
I can get it all to work by putting "fedora.local" in /etc/hostname _and_ editing
/etc/hosts to have "fedora.local" as the _first_ name for 127.0.0.1 .
I installed a Centos7 system and during the install process called it
fedora.local. By
On 1/30/22 1:34 AM, Ed Greshko wrote:
On 30/01/2022 12:36, Robert Nichols wrote:
On 1/29/22 8:25 PM, Gordon Messmer wrote:
On 1/29/22 17:20, Ed Greshko wrote:
In the initial posting by Robert he wrote:
"I have no nfs-idmapd service running"
Right, but on recent kernels, the client doesn't
On 1/29/22 20:36, Robert Nichols wrote:
If I could find any way to set the client's domain name, I would.
Nothing I try has any effect on the domain name.
When I try to set a FQDN with hostnamectl, then "hostnamectl" (with no
arguments) shows that FQDN as the static hostname, but "hostname
--fq
On 30/01/2022 12:36, Robert Nichols wrote:
On 1/29/22 8:25 PM, Gordon Messmer wrote:
On 1/29/22 17:20, Ed Greshko wrote:
In the initial posting by Robert he wrote:
"I have no nfs-idmapd service running"
Right, but on recent kernels, the client doesn't use rpc.idmapd, it uses
"nfsidmap". T
On 1/29/22 8:25 PM, Gordon Messmer wrote:
On 1/29/22 17:20, Ed Greshko wrote:
In the initial posting by Robert he wrote:
"I have no nfs-idmapd service running"
Right, but on recent kernels, the client doesn't use rpc.idmapd, it uses
"nfsidmap". The fact that rpc.idmapd isn't running doesn'
On 1/29/22 17:20, Ed Greshko wrote:
In the initial posting by Robert he wrote:
"I have no nfs-idmapd service running"
Right, but on recent kernels, the client doesn't use rpc.idmapd, it uses
"nfsidmap". The fact that rpc.idmapd isn't running doesn't really tell
us anything.
"all users a
On 30/01/2022 07:44, Gordon Messmer wrote:
On 1/28/22 23:32, Ed Greshko wrote:
But I do have nfs-idmapd.service with "Domain = localdomain" in its
configuration file.
If I change that to "Domain = local" and restart nfs-idmapd.service I do get
[root@fedora ~]# nfsidmap -d
local
But everything
On 1/28/22 23:32, Ed Greshko wrote:
But I do have nfs-idmapd.service with "Domain = localdomain" in its
configuration file.
If I change that to "Domain = local" and restart nfs-idmapd.service I
do get
[root@fedora ~]# nfsidmap -d
local
But everything works no matter what the setting
https
On 29/01/2022 13:44, Gordon Messmer wrote:
On 1/28/22 06:08, Robert Nichols wrote:
Where does Fedora get its domain name? When I type "hostname --fqdn" I get "hostname: Name or
service not known". The CentOS 8 VM apparently gets its domain name from the /etc/hostname file, which
contains "cent
On 29/01/2022 11:44, Robert Nichols wrote:
No change:
[fedora ~]# hostnamectl hostname fedora.local
[fedora ~]# hostnamectl
Static hostname: fedora.local
Icon name: computer-vm
Chassis: vm
Machine ID: 6e701e7fa0dc4996984b6509b40eb940
Boot ID: 256c0a3fa9dd4b88bd611
On 1/28/22 06:08, Robert Nichols wrote:
Where does Fedora get its domain name? When I type "hostname --fqdn"
I get "hostname: Name or service not known". The CentOS 8 VM
apparently gets its domain name from the /etc/hostname file, which
contains "cent9-vm.local". This does not appear to work in
On 1/27/22 9:13 AM, francis.montag...@inria.fr wrote:
Hi.
On Thu, 27 Jan 2022 08:10:53 -0600 Robert Nichols wrote:
On 1/26/22 7:15 PM, Gordon Messmer wrote:
What does the entry for that filesystem in /proc/mounts look like? It should
have negotiated mount options that shed some light.
On 1/28/22 8:53 AM, Ed Greshko wrote:
On 28/01/2022 22:08, Robert Nichols wrote:
On 1/28/22 1:03 AM, Ed Greshko wrote:
On 26/01/2022 00:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs a
On 28/01/2022 22:53, Ed Greshko wrote:
Example: For the host that I mentioned I used "hostnamectl f35ser.greshko.com"
Correction.
hostnamectl hostname f35ser.greshko.com
Too late in my day.
--
Did 황준호 die?
___
users mailing list -- users@lists.
On 28/01/2022 22:08, Robert Nichols wrote:
On 1/28/22 1:03 AM, Ed Greshko wrote:
On 26/01/2022 00:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client.
On 1/28/22 1:03 AM, Ed Greshko wrote:
On 26/01/2022 00:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
"
On 26/01/2022 00:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
"name '@local' does not map into dom
Hi.
On Thu, 27 Jan 2022 08:10:53 -0600 Robert Nichols wrote:
> On 1/26/22 7:15 PM, Gordon Messmer wrote:
>> What does the entry for that filesystem in /proc/mounts look like? It
>> should have negotiated mount options that shed some light.
>> Maybe add the "sec=sys" mount option to the clien
On 1/26/22 7:15 PM, Gordon Messmer wrote:
On 1/25/22 08:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
On 1/25/22 08:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem
are mapped to "nobody" even though the names and numeric IDs are the
same on the server and client. The messages logged are of the form:
"name '@local' does not map into domain
On Tue, 25 Jan 2022 10:35:27 -0600
Robert Nichols wrote:
> In a Fedora 35 VM, all users and groups in an NFS mounted filesystem
> are mapped to "nobody" even though the names and numeric IDs are the
> same on the server and client. The messages logged are of the form:
>
> "name '@local
33 matches
Mail list logo
