On Thu 27 Jan 2022 at 08:21:49 +, Tixy wrote:
> On Wed, 2022-01-26 at 19:26 +, Brian wrote:
> > On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:
> >
> > [Snipping]
> >
> > > I've worked this way for 15 years and, unlike Gene, I'm not having
> > > to fight any battles over it. I'
Tixy wrote:
>
> I can't see what the problem with DHCP is, if I want to have static IP
> addresses or use names to identify machines on the network, I can take
> a minute to add a line to dnsmasq.conf on my router. I know some people
> say that DHCP is a single point of failure, or they don't wan
On Wed, 2022-01-26 at 19:26 +, Brian wrote:
> On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:
>
> [Snipping]
>
> > I've worked this way for 15 years and, unlike Gene, I'm not having
> > to fight any battles over it. I'm sure mDNS is perfect for people
> > with different demands from
On Wed 26 Jan 2022 at 18:56:17 (+0100), Andrei POPESCU wrote:
> On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote:
> > On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > > should tell you that I don't have that
On Wednesday, January 26, 2022 10:49:35 AM EST Brian wrote:
> On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote:
> > On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> > > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > > > On Tue 25 Jan 2022 at 09:31:57 (+0100), And
On Wednesday, January 26, 2022 11:55:36 AM EST Greg Wooledge wrote:
> On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > should tell you that I don't have that file either, but I downloaded
> > dhcpcd5_7.1.0-2+b
On Wed, Jan 26, 2022 at 07:26:49PM +, Brian wrote:
> On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:
> > I've worked this way for 15 years and, unlike Gene, I'm not having
> > to fight any battles over it. I'm sure mDNS is perfect for people
> > with different demands from mine.
>
>
On Wed 26 Jan 2022 at 10:42:38 -0600, David Wright wrote:
[Snipping]
> I've worked this way for 15 years and, unlike Gene, I'm not having
> to fight any battles over it. I'm sure mDNS is perfect for people
> with different demands from mine.
My question was really directed at all users, particul
On Wed, Jan 26, 2022 at 07:11:36PM +0100, Andrei POPESCU wrote:
> > # fallback to static profile on eth0
> > interface eth0
> > fallback static_eth0
> >
> > So if dhcpd fails, it uses the above, and it Just Works.
> > And I've not found any reference to it in the man page. So I've no clue
> > why
On Ma, 25 ian 22, 21:27:17, gene heskett wrote:
>
> It works fine with no complaints.
>
> Here is the bottom of /etc/dhcpcd.conf:
>
> # Example static IP configuration:
> #interface eth0
> #static ip_address=192.168.0.10/24
> #static ip6_address=fd51:42f8:caae:d92e::ff/64
> #static routers=192.1
On Mi, 26 ian 22, 11:55:36, Greg Wooledge wrote:
> On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> > And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> > should tell you that I don't have that file either, but I downloaded
> > dhcpcd5_7.1.0-2+b1_amd64.deb just as
On Wed, Jan 26, 2022 at 10:42:23AM -0600, David Wright wrote:
> And the first word in "CONTENTS/usr/share/man/man5/dhcpcd.conf.5.gz"
> should tell you that I don't have that file either, but I downloaded
> dhcpcd5_7.1.0-2+b1_amd64.deb just as I did last time you raised this.
> And if I type "man" i
On Wed 26 Jan 2022 at 15:31:46 (+), Brian wrote:
> On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > >
> > > > Resolving hostnames on the local network is simple and r
On Wed 26 Jan 2022 at 05:14:32 (-0500), gene heskett wrote:
> On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote:
> > On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> > > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > > > I can't speak to Gene's wantin
On Wed 26 Jan 2022 at 15:54:38 +, mick crane wrote:
> On 2022-01-26 15:31, Brian wrote:
>
> > Having said that, 'ssh desktop.local' does not require much guidance.
>
> Is .local mDNS specific ?
Yes.
> I thought we are supposed to not use .local for a home network.
That caveat is for alloc
On 2022-01-26 15:31, Brian wrote:
Having said that, 'ssh desktop.local' does not require much guidance.
Is .local mDNS specific ?
I thought we are supposed to not use .local for a home network.
What is this ipv4only.arpa , are we supposed to use that.
mick
--
Key ID4BFEBB31
On Wed 26 Jan 2022 at 10:39:42 -0500, gene heskett wrote:
> On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> > On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
On Wednesday, January 26, 2022 10:31:46 AM EST Brian wrote:
> On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> > On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > > Resolving hostnames on the local network is simple and rel
On Tue 25 Jan 2022 at 18:35:54 -0600, David Wright wrote:
> On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > >
> > > Resolving hostnames on the local network is simple and reliable when
> > > avahi-daemon and linnss-mdns are available.
On Tuesday, January 25, 2022 11:36:05 PM EST David Wright wrote:
> On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> > On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > > I can't speak to Gene's wanting a static network configured by his
> > > method, but I'm happy to
On Tue 25 Jan 2022 at 21:27:17 (-0500), gene heskett wrote:
> On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> > I can't speak to Gene's wanting a static network configured by his
> > method, but I'm happy to defend my choice.
> >
> It works fine with no complaints.
OK. I've alre
On Tue, Jan 25, 2022 at 09:27:17PM -0500, gene heskett wrote:
> Here is the bottom of /etc/dhcpcd.conf:
WHY do you HAVE a dhcpcd.conf file if you don't use DHCP on your network?
Or... well, you're not using Debian. You're using Raspbian, and Raspbian
installs dhcpcd by default as I understand it
On Tuesday, January 25, 2022 7:35:54 PM EST David Wright wrote:
> On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> > On Lu, 24 ian 22, 23:54:41, Brian wrote:
> > > Resolving hostnames on the local network is simple and reliable
> > > when
> > > avahi-daemon and linnss-mdns are availa
On Tue 25 Jan 2022 at 09:31:57 (+0100), Andrei POPESCU wrote:
> On Lu, 24 ian 22, 23:54:41, Brian wrote:
> >
> > Resolving hostnames on the local network is simple and reliable when
> > avahi-daemon and linnss-mdns are available.
> >
> > brian@desktop:~$ getent hosts envy4500.local
> > 192.16
On Tue 25 Jan 2022 at 16:20:49 +, Brian wrote:
> on the same or another machine. _mpd._tcp is a service name and is
Correction. _mpd._tcp is a service type.
--
Brian.
On Tue 25 Jan 2022 at 13:06:49 +0100, Andrei POPESCU wrote:
> On Ma, 25 ian 22, 11:18:21, Brian wrote:
> > On Tue 25 Jan 2022 at 09:31:57 +0100, Andrei POPESCU wrote:
> > >
> > > Could you point to any (reasonably up-to-date) documentation or is it
> > > sufficient to just install avahi-daemon a
On Ma, 25 ian 22, 11:18:21, Brian wrote:
> On Tue 25 Jan 2022 at 09:31:57 +0100, Andrei POPESCU wrote:
> >
> > Could you point to any (reasonably up-to-date) documentation or is it
> > sufficient to just install avahi-daemon and libnss-mdns?
>
> 'apt install avahi-daemon' is sufficient. libnnss-
On Tue 25 Jan 2022 at 09:31:57 +0100, Andrei POPESCU wrote:
> On Lu, 24 ian 22, 23:54:41, Brian wrote:
> >
> > Resolving hostnames on the local network is simple and reliable when
> > avahi-daemon and linnss-mdns are available.
> >
> > brian@desktop:~$ getent hosts envy4500.local
> > 192.168
On Lu, 24 ian 22, 23:54:41, Brian wrote:
>
> Resolving hostnames on the local network is simple and reliable when
> avahi-daemon and linnss-mdns are available.
>
> brian@desktop:~$ getent hosts envy4500.local
> 192.168.7.235 envy4500.local
>
> Continually and nanually maintain /etc/hosts?
On Mon 24 Jan 2022 at 10:39:01 -0600, David Wright wrote:
> On Sun 23 Jan 2022 at 15:01:09 (-0500), Greg Wooledge wrote:
> > On Sun, Jan 23, 2022 at 07:09:27PM +, Brian wrote:
> > > On Sun 23 Jan 2022 at 13:53:01 -0500, gene heskett wrote:
> > > > On Sunday, January 23, 2022 1:26:56 PM EST Fel
On Sun 23 Jan 2022 at 15:01:09 (-0500), Greg Wooledge wrote:
> On Sun, Jan 23, 2022 at 07:09:27PM +, Brian wrote:
> > On Sun 23 Jan 2022 at 13:53:01 -0500, gene heskett wrote:
> > > On Sunday, January 23, 2022 1:26:56 PM EST Felix Miata wrote:
> > > > Greg Wooledge composed on 2022-01-23 08:42
On Sun, 23 Jan 2022 23:42:33 +
Brian wrote:
> I was rather hoping for some mention of the role of Avahi and
> libnss-mdns on the local network amd its minimal maintenamce.
I seem to have it installed, mostly to support an apple Macbook. But I
did not configure it in any way. Apparently, it
On Sun 23 Jan 2022 at 15:14:54 -0500, Felix Miata wrote:
>
>
> Greg Wooledge composed on 2022-01-23 15:01 (UTC-0500):
>
> > * After a change is made, it has to be replicated across your entire
> >network. Manually.
>
> But trivial.
Manual intervention as opposed to no intervention. What
On Sun 23 Jan 2022 at 12:52:27 -0700, Charles Curley wrote:
> On Sun, 23 Jan 2022 19:09:27 +
> Brian wrote:
>
> > What advice would you give to a user regarding the benefits of a hosts
> > file as opposed to more modern techniques?
>
> By "more modern techniques" I will assume you mean DHCP
On Sunday, January 23, 2022 2:09:27 PM EST Brian wrote:
> On Sun 23 Jan 2022 at 13:53:01 -0500, gene heskett wrote:
> > On Sunday, January 23, 2022 1:26:56 PM EST Felix Miata wrote:
> > > Greg Wooledge composed on 2022-01-23 08:42 (UTC-0500):
> > > > On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andrei
Greg Wooledge composed on 2022-01-23 15:01 (UTC-0500):
> * After a change is made, it has to be replicated across your entire
>network. Manually.
But trivial.
> * Any "visitor" machines that are temporarily added to your network will
>need to be configured manually, and they will h
On Sun, Jan 23, 2022 at 07:09:27PM +, Brian wrote:
> On Sun 23 Jan 2022 at 13:53:01 -0500, gene heskett wrote:
>
> > On Sunday, January 23, 2022 1:26:56 PM EST Felix Miata wrote:
> > > Greg Wooledge composed on 2022-01-23 08:42 (UTC-0500):
> > > > On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andr
On Sun, 23 Jan 2022 19:09:27 +
Brian wrote:
> What advice would you give to a user regarding the benefits of a hosts
> file as opposed to more modern techniques?
By "more modern techniques" I will assume you mean DHCP and DNS.
Hosts files are simple, easy to do. They have to be propagated a
On Sun 23 Jan 2022 at 13:53:01 -0500, gene heskett wrote:
> On Sunday, January 23, 2022 1:26:56 PM EST Felix Miata wrote:
> > Greg Wooledge composed on 2022-01-23 08:42 (UTC-0500):
> > > On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andrei POPESCU wrote:
> > >> As far as I can tell (with my limited un
On Sunday, January 23, 2022 1:26:56 PM EST Felix Miata wrote:
> Greg Wooledge composed on 2022-01-23 08:42 (UTC-0500):
> > On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andrei POPESCU wrote:
> >> As far as I can tell (with my limited understanding of DNS) it only
> >> makes it easier to share /etc/host
Greg Wooledge composed on 2022-01-23 08:42 (UTC-0500):
> On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andrei POPESCU wrote:
>> As far as I can tell (with my limited understanding of DNS) it only
>> makes it easier to share /etc/hosts with no obvious downside.
> If that actually works, that's great
On Sun 23 Jan 2022 at 08:50:56 (+0100), Andrei POPESCU wrote:
> On Sb, 22 ian 22, 20:07:45, David Wright wrote:
> >
> > Because the basic /etc/hosts file looks something like:
> >
> > 127.0.0.1 localhost
> > 192.168.1.1 router.corp router
> > 192.168.1.2 cascade.corpcasc
On Sun, Jan 23, 2022 at 08:50:56AM +0100, Andrei POPESCU wrote:
> On Sb, 22 ian 22, 20:07:45, David Wright wrote:
> >
> > Because the basic /etc/hosts file looks something like:
> >
> > 127.0.0.1 localhost
> > 192.168.1.1 router.corp router
> > 192.168.1.2 cascade.corpca
On Sb, 22 ian 22, 07:13:18, gene heskett wrote:
>
> its for its own eth0 on the rpi4b. And I guess it is raspi specific. It
> doesn't exist on this x86-64 bullseye install.
Likely the source of your problems is that Raspberry Pi OS has DHCP
enabled by default.
It might have been done using Deb
Andrew M.A. Cater wrote:
> If you want to know how to run (fairly)
> vanilla Debian - but including the non-free raspberry pi firmware
> and rpi-eeprom - it's possible using either Gunnar Wolf's images
> or Pete Batard's version of UEFI for the Pi 4 and the Debian
> arm64 ISO file. _That_ I can he
On Sb, 22 ian 22, 20:07:45, David Wright wrote:
>
> Because the basic /etc/hosts file looks something like:
>
> 127.0.0.1 localhost
> 192.168.1.1 router.corp router
> 192.168.1.2 cascade.corpcascade
> 127.0.1.1 acer.corp acer# 192.168.1.10
> # The following lines a
On 2022-01-22 at 21:23, gene heskett wrote:
> On Saturday, January 22, 2022 9:08:02 PM EST David Wright wrote:
>
>> On Sat 22 Jan 2022 at 19:07:35 (-0500), The Wanderer wrote:
>> > This is the line which contains the directives involved.
>> >
>> > The 'files' directive tells your system to check
On Saturday, January 22, 2022 9:08:02 PM EST David Wright wrote:
> On Sat 22 Jan 2022 at 19:07:35 (-0500), The Wanderer wrote:
> > On 2022-01-22 at 18:38, gene heskett wrote:
> >
> >
> > > hosts: files mdns4_minimal [NOTFOUND=return] dns
> >
> > This is the line which contains the direc
On Saturday, January 22, 2022 8:52:24 PM EST Lee wrote:
> Hi Gene,
>
> On 1/21/22, gene heskett wrote:
> > This is all well and good, Greg, but it still does NOT give a clue
> > what todo when the system picks a fictitious route out of its rear.
> Once you realize that that your machine getting a
On Sat 22 Jan 2022 at 19:07:35 (-0500), The Wanderer wrote:
> On 2022-01-22 at 18:38, gene heskett wrote:
>
>
> > hosts: files mdns4_minimal [NOTFOUND=return] dns
>
> This is the line which contains the directives involved.
>
> The 'files' directive tells your system to check local fil
On Sat 22 Jan 2022 at 13:57:38 (-0500), gene heskett wrote:
> On Saturday, January 22, 2022 12:14:20 PM EST David Wright wrote:
> > On Sat 22 Jan 2022 at 11:13:59 (+0100), to...@tuxteam.de wrote:
> > > On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> > > > On Saturday, January 22, 20
Hi Gene,
On 1/21/22, gene heskett wrote:
>
> This is all well and good, Greg, but it still does NOT give a clue what
> todo when the system picks a fictitious route out of its rear.
Once you realize that that your machine getting a 169.254.x.x address
https://en.wikipedia.org/wiki/Link-local_
On 2022-01-22 at 18:38, gene heskett wrote:
> On Saturday, January 22, 2022 4:20:07 PM EST Greg Wooledge wrote:
>
>> On Sat, Jan 22, 2022 at 01:57:38PM -0500, gene heskett wrote:
>
>>> So my resolv.conf says to search coyote.den, and failing that,
>>> use my isp's nameserver [...]
>>
>> Again:
On Saturday, January 22, 2022 4:20:07 PM EST Greg Wooledge wrote:
> On Sat, Jan 22, 2022 at 01:57:38PM -0500, gene heskett wrote:
> > So my resolv.conf says to search coyote.den, and failing that, use my
> > isp's nameserver [...]
>
> Again: that is NOT what the resolv.conf file does.
>
> The /et
On Sat, Jan 22, 2022 at 05:20:49PM -0500, gene heskett wrote:
> On Saturday, January 22, 2022 9:33:56 AM EST Charles Curley wrote:
> > On Sat, 22 Jan 2022 07:47:01 +0100
> >
> > wrote:
> > > Reading the source [1], `set-hostname' seems to be obsolete. The
> > > magic
> > > word seems to be simply
On Saturday, January 22, 2022 9:33:56 AM EST Charles Curley wrote:
> On Sat, 22 Jan 2022 07:47:01 +0100
>
> wrote:
> > Reading the source [1], `set-hostname' seems to be obsolete. The
> > magic
> > word seems to be simply `hostname', these days, at least.
>
> Interesting.
>
> I have systemd 247
On Sat, Jan 22, 2022 at 01:57:38PM -0500, gene heskett wrote:
> So my resolv.conf says to search coyote.den, and failing that, use my
> isp's nameserver [...]
Again: that is NOT what the resolv.conf file does.
The /etc/nsswitch.conf file *SHOULD* tell your system to use the /etc/hosts
file first
On Saturday, January 22, 2022 12:14:20 PM EST David Wright wrote:
> On Sat 22 Jan 2022 at 11:13:59 (+0100), to...@tuxteam.de wrote:
> > On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> > > On Saturday, January 22, 2022 2:04:32 AM EST to...@tuxteam.de
wrote:
> > [...]
> >
> > > > On
On Sat 22 Jan 2022 at 11:13:59 (+0100), to...@tuxteam.de wrote:
> On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> > On Saturday, January 22, 2022 2:04:32 AM EST to...@tuxteam.de wrote:
>
> [...]
>
> > > Once that part is flying, tackle names :)
>
> I stay still by this :)
>
> >
On Fri 21 Jan 2022 at 21:34:35 (-0500), gene heskett wrote:
> My whole system here, 7 machines atm, has been as high as a dozen, is
> dhcpd-less, all host name based with a common hosts file on all machines.
> And until avahi sticks its camel nose in, it Just Works. So how do I get
> rid of the
On Sat, Jan 22, 2022 at 07:33:56AM -0700, Charles Curley wrote:
> On Sat, 22 Jan 2022 07:47:01 +0100
> wrote:
>
> > Reading the source [1], `set-hostname' seems to be obsolete. The magic
> > word seems to be simply `hostname', these days, at least.
>
> Interesting.
>
> I have systemd 247.3-6, a
On Sat, 22 Jan 2022 07:47:01 +0100
wrote:
> Reading the source [1], `set-hostname' seems to be obsolete. The magic
> word seems to be simply `hostname', these days, at least.
Interesting.
I have systemd 247.3-6, as provided on Bullseye. The man page mentions
set-hostname only. Looking at your f
On Saturday, January 22, 2022 5:13:59 AM EST to...@tuxteam.de wrote:
> On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> > On Saturday, January 22, 2022 2:04:32 AM EST to...@tuxteam.de wrote:
> [...]
>
> > > Once that part is flying, tackle names :)
>
> I stay still by this :)
>
>
On Sat, Jan 22, 2022 at 04:38:04AM -0500, gene heskett wrote:
> On Saturday, January 22, 2022 2:04:32 AM EST to...@tuxteam.de wrote:
[...]
> > Once that part is flying, tackle names :)
I stay still by this :)
> But, I found, quite by serendipity, in the raspios version of bullseye, a
> fix. Lo
On Saturday, January 22, 2022 2:04:32 AM EST to...@tuxteam.de wrote:
> On Fri, Jan 21, 2022 at 11:51:20PM -0500, gene heskett wrote:
>
> [...]
>
> > This is all well and good, Greg, but it still does NOT give a clue
> > what todo when the system picks a fictitious route out of its rear.
> Start d
On Sat, Jan 22, 2022 at 09:03:06AM -, Curt wrote:
> On 2022-01-22, Greg Wooledge wrote:
> > On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> >> On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> >> > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote
On 2022-01-22, Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
>> On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
>> > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
>> > > So how do I officially set the hostname so its reboot
On Vi, 21 ian 22, 23:51:20, gene heskett wrote:
> On Friday, January 21, 2022 10:46:35 PM EST Greg Wooledge wrote:
[lots of good stuff]
> This is all well and good, Greg, but it still does NOT give a clue what
> todo when the system picks a fictitious route out of its rear.
In order to even try
On Fri, Jan 21, 2022 at 11:51:20PM -0500, gene heskett wrote:
[...]
> This is all well and good, Greg, but it still does NOT give a clue what
> todo when the system picks a fictitious route out of its rear.
Start debugging from bottom to top. For the first round, just deal in IP
addresses and r
On Fri, Jan 21, 2022 at 10:46:35PM -0500, Greg Wooledge wrote:
[...]
> Well, yes. The "hostname" command sets the current hostname, which resides
> in memory only. It has no permanent effect.
>
> And it has nothing at all to do with IP addresses. Or DNS.
[...]
> Routing has nothing to do wi
On Fri, Jan 21, 2022 at 07:46:40PM -0500, Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > > So how do I officially s
On Friday, January 21, 2022 10:46:35 PM EST Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 09:34:35PM -0500, gene heskett wrote:
> > /etc/resolv.conf has:
> > search coyote.den
> > nameserver 192.168.xx.1
> >
> > the search line says to look in the /etc/hosts file, failing that,
> > the
> > namese
On Fri, Jan 21, 2022 at 09:34:35PM -0500, gene heskett wrote:
> /etc/resolv.conf has:
> search coyote.den
> nameserver 192.168.xx.1
>
> the search line says to look in the /etc/hosts file, failing that, the
> nameserver line sends the dns lookup query to the router
No, that's not correct.
The c
On Friday, January 21, 2022 9:34:35 PM EST gene heskett wrote:
> On Friday, January 21, 2022 7:46:40 PM EST Greg Wooledge wrote:
> > On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > > On Fri, Jan 21, 2022 a
On Friday, January 21, 2022 7:46:40 PM EST Greg Wooledge wrote:
> On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> > On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > > So how do I officially
On Fri, Jan 21, 2022 at 07:27:11PM -0500, gene heskett wrote:
> On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> > On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > > So how do I officially set the hostname so its reboot proof?
> >
> > hostnamectl set hostname
On Friday, January 21, 2022 6:45:52 PM EST Andrew M.A. Cater wrote:
> On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> > Hi all;
> >
> > System is an rpi4b/bullseye, uptodate.
> > I had to fix this a year or more ago with buster, but this system has
> > crashed and burned thanks to
On Fri, Jan 21, 2022 at 06:42:38PM -0500, gene heskett wrote:
> Hi all;
>
> System is an rpi4b/bullseye, uptodate.
> I had to fix this a year or more ago with buster, but this system has
> crashed and burned thanks to a 2T shingled drive. Notes if any were ever
> made are gone.
>
> So how do I
78 matches
Mail list logo
