"You said you were on an OpenVZ hosted VPS, right? That means you're
using the host's kernel, which is generally not going to be the same
as what you would have on a non-virtual Debian 12 system."
So, is that my problem?
Thanks.
Dave.
On 6/27/23, Greg Wooledge wrote:
> On Tue, Jun 27, 2023 at
On Tue, Jun 27, 2023 at 08:33:21PM -0400, David Mehler wrote:
> The question is this, what kernel version (I believe it is 6.x?) comes
> with Debian 12? The reason I ask is because of this:
>
>
> #uname -a
> Linux hostname.example.com 4.19.0 #1 SMP Thu Dec 15 20:31:06 MSK 2022
> x86_64 GNU/Linux
comes
with Debian 12? The reason I ask is because of this:
#uname -a
Linux hostname.example.com 4.19.0 #1 SMP Thu Dec 15 20:31:06 MSK 2022
x86_64 GNU/Linux
#uname -r
4.19.0
#hostnamectl
Static hostname: hostname.example.com
Icon name: computer-container
Chassis: cont
es.d/hostname.rules
echo '-a always,exit -F path=/proc/sys/kernel/hostname -F perm=wa' \
>> /etc/audit/rules.d/hostname.rules
service auditd restart
reboot
Whatever's trying to change the hostname should leave a trace in
/var/log/audit/audit.log.
PS Here it's custo
t just fine. I set my time zone that stuck and
>> is persisting then went for the hostname, I am doing this via ssh, in
>> setting the hostname it won't persist through a reboot.
>>
>> In the below output I've x-d out items like the device chasis ID and
>> the
https://www.makeuseof.com/upgrade-to-debian-12-bookworm-from-debian-11/
the upgrade itself went just fine. I set my time zone that stuck and
is persisting then went for the hostname, I am doing this via ssh, in
setting the hostname it won't persist through a reboot.
In the below output I've x-d
Hi.
On Tue, Jun 27, 2023 at 08:06:17AM -0400, David Mehler wrote:
> You might be on to something though here's what is in
> /etc/dhcp/dhclient.conf I'm just not sure what options to comment out?
That's even easier. Instead of
send host-name = gethostname();
request subnet-mask, broadcas
ime zone that stuck and
>> is persisting then went for the hostname, I am doing this via ssh, in
>> setting the hostname it won't persist through a reboot.
>
> One of the possible reasons for this is "cloud-init".
> Purge the package, or set "preserve_host
Hi.
On Tue, Jun 27, 2023 at 06:48:52AM -0400, David Mehler wrote:
> the upgrade itself went just fine. I set my time zone that stuck and
> is persisting then went for the hostname, I am doing this via ssh, in
> setting the hostname it won't persist through a reboot.
One o
an-12-bookworm-from-debian-11/
the upgrade itself went just fine. I set my time zone that stuck and
is persisting then went for the hostname, I am doing this via ssh, in
setting the hostname it won't persist through a reboot.
In the below output I've x-d out items like the device chasis ID
Hi,
I just launched an ubuntu container in that namespace and installed
dnsutils/iputils-ping to resolve the hostname issue.
Thank you.
On Sat, Mar 4, 2023 at 1:11 PM Rodrigo Cunha
wrote:
> I have bitnami/mysql container (debian OS) running on kubernetes.
>> This container
Greg Wooledge (12023-03-03):
> Dedicated lookup tools:
>
> getent hosts
> host
> dnsqr
It is important to know that host and dnsqr do actual DNS requests, and
therefore ignore local configuration about other means of resolving
hosts, including /etc/hosts.
getent hosts is the dedicated command, t
ping
> dig
> nslookup
> net-tools
>
> Do you know any other way to resolve a hostname by manual on this
> container?
>
> Thanks
> Ken
>
--
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil
On 04/03/2023 07:53, Ken Young wrote:
Do you know any other way to resolve a hostname by manual on this
container?
systemd-resolve
However I am unsure concerning k8s containers. Some interpreters:
python3 -c 'import socket as s, sys;
print(s.gethostbyname(sys.argv[1]))' debian.net
On Sat, Mar 04, 2023 at 08:53:39AM +0800, Ken Young wrote:
> ping
> dig
> nslookup
> net-tools
>
> Do you know any other way to resolve a hostname by manual on this
> container?
Dedicated lookup tools:
getent hosts
host
dnsqr
Utilities that resolve hostnames as a side ef
Hello,
I have bitnami/mysql container (debian OS) running on kubernetes.
This container seems too restricted for system software, these following
commands are removed:
sudo (so I can't su to root for apt)
ping
dig
nslookup
net-tools
Do you know any other way to resolve a hostname by manua
enerally better to add the FQDN to /etc/hosts instead, to cut down
> on DNS queries for the local hostname.
In one scenario, sure. There are plenty of other scenarios where doing
that doesn't make sense. For example, that bullseye system was one of
20 containers that are spun up from o
r the local hostname.
On 2022-06-26 21:07:13 +, tuxi...@posteo.de wrote:
> I checked using strace and it's appearently going through the following:
>
> 1. uname
This is due to the call to gethostname(), as seen with "hostname"
without any option.
The following is due to the call to getadd
On Sonntag, 26. Juni 2022 22:32:38 CEST Jim Popovitch wrote:
> where does `hostname -f` derive the domainname from?
>
> I have 2 systems, the first was buster --> bullseye with /etc/hostname
> containing "oscar" and `hostname -f` returning "oscar.domain.tld"
On Sun, 2022-06-26 at 16:52 -0400, Greg Wooledge wrote:
> Both sections are vague and murky about what happens if you *don't* have
> an entry for your hostname in /etc/hosts.
>
> Fortunately, Debian adds a line exactly like this in /etc/hosts, for
> your hostname with your &q
On Sun, Jun 26, 2022 at 04:32:38PM -0400, Jim Popovitch wrote:
> where does `hostname -f` derive the domainname from?
Start with the man page, always.
-f, --fqdn, --long
Display the FQDN (Fully Qualified Domain Name). A FQDN consists
of a short host name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
--- Original Message ---
On Sunday, June 26th, 2022 at 2:32 PM, Jim Popovitch wrote:
> where does `hostname -f` derive the domainname from?
/etc/hosts, I think.
--
Glenn English
-BEGIN PGP SIGNATURE-
Version: ProtonM
where does `hostname -f` derive the domainname from?
I have 2 systems, the first was buster --> bullseye with /etc/hostname
containing "oscar" and `hostname -f` returning "oscar.domain.tld".
The second system is a clean install of bullseye with /etc/hostname
containing &
wledge of DHCP.
People do usually suggest that you don't put your question in the
Subject line but rather in the body. Of course, "Discovering DHCP
hostname during original system installation" isn't a question, either
(not that I understand what the dhcp hostname could possibly
On Thu 02 Jun 2022 at 08:53:12 (-0500), Richard Owlett wrote:
> On 05/31/2022 08:13 AM, Richard Owlett wrote:
> > I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto
> > a Lenovo T510 [Thinkpad].
> >
> > I know the netinstaller works on this laptop as I have done a
> > successful in
On 05/31/2022 08:13 AM, Richard Owlett wrote:
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
I know the netinstaller works on this laptop as I have done a successful
install when within range of of local library's wifi and the installer
is success
es
> requiring non-free drivers.
Again, the OP never made any mention of this.
> I tried to succinctly state MY topic in the Subject line.
> When The DHCP auto-detection during install fails,
> "How do I manually discover DHCP [server] hostname(s)?"
Ah, now, I recognise
On Wed 01 Jun 2022 at 06:32:07 -0500, Richard Owlett wrote:
[...]
> As stated in this post the particular machine is dedicated to
> EXPERIMENTATION. The goal of the experimentation is to be able to describe
> how the Debian installation process could simultaneously be simpler and more
> versatile
On 05/31/2022 02:00 PM, Richard Owlett wrote:
*SNIP*
I am doing a fresh install from home using an Alcatel Linkzone to
connect to my T-mobile account. I have had no problems doing this with
standard netinstallers.
? That seems to be a new interpretation of the thread:
https://lists.debian.
read might be something about official vs firmware
rather than, say wifi vs ethernet in the normal scenario, or wifi vs
some sort of ?USB link in your case.
No ;/
I tried to succinctly state MY topic in the Subject line.
When The DHCP auto-detection during install fails,
"How do I manually discov
On Tue 31 May 2022 at 14:00:51 (-0500), Richard Owlett wrote:
> On 05/31/2022 11:13 AM, David Wright wrote:
> > On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
> > > I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
> > > Lenovo T510 [Thinkpad].
> >
> > ✓
> >
> >
On 05/31/2022 11:13 AM, David Wright wrote:
On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
✓
I know the netinstaller works on this laptop as I have done a
successful install when withi
On Tue 31 May 2022 at 08:13:57 (-0500), Richard Owlett wrote:
> I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
> Lenovo T510 [Thinkpad].
✓
> I know the netinstaller works on this laptop as I have done a
> successful install when within range of of local library's wifi and
>
I'm using firmware-11.3.0-amd64-netinst.iso to install Debian onto a
Lenovo T510 [Thinkpad].
I know the netinstaller works on this laptop as I have done a successful
install when within range of of local library's wifi and the installer
is successfully detecting multiple local wifi sources.
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.
required.
>
> Less than optimal (yes, I'm lazy), but I might be able to live with it ;)
It grows on you :).
> Is there a way to have "generic" names, e.g. something like "mpd.local",
> independent of the system's hostname?
Let's see if this addresses
; > Can mDNS resolve only hostnames or is it necessary to always mention the
> > '.local' domain?
>
> .local is required.
Less than optimal (yes, I'm lazy), but I might be able to live with it ;)
Is there a way to have "generic" names, e.g. something like
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
year—
less frequently really, as often they're paired +-.
(And I did answer Andrei's comment, albeit after you'd posted.
It's no harder to distribute transformed files than identical ones.)
But to get back to Gene's network, and his lack of certainty that,
when "ssh -Y rp
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
; > 192.168.1.2 cascade.corpcascade
> > 127.0.1.1 acer.corp acer# 192.168.1.10
> > # The following lines are desirable for IPv6 capable hosts
> > ::1 localhost ip6-localhost ip6-loopback
> > ff02::1 ip6-allnodes
> > ff02::2 ip6-allro
; > 192.168.1.2 cascade.corpcascade
> > 127.0.1.1 acer.corp acer# 192.168.1.10
> > # The following lines are desirable for IPv6 capable hosts
> > ::1 localhost ip6-localhost ip6-loopback
> > ff02::1 ip6-allnodes
> > ff02::2 ip6-allro
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
# The following lines are desirable for IPv6 capable hosts
> ::1 localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> and the hostname, acer, will be different on each host.
Instead of listing the machine's name with 127.0.1.1
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
here is not a running server on my local net, its all in the
hosts file, and changing the hostname torpedo's the hosts file lookups.
zero-conf stuff to me has never been anything but a headache.
> As for avahi, my notes have
> disable multicast DNS (avahi-daemon)
> $ sudo systemc
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
l hosts
> file on every machine in my tiny home network to describe my local
> network is bad, to be denigrated at every turn of the screw you can
> manage.
Because the basic /etc/hosts file looks something like:
127.0.0.1 localhost
192.168.1.1 router.corp router
192.168.
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:
Each system must configure its own IP address, netmask, and default
>route (gateway). This can be done in /etc/network/interfaces if the
> interface name is well defined.
It is well defined, but overridden at reboot because something edited the
/etc/hostname file, restoring the installers
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
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.
The "search" line doesn't actually do much here, because all of your
Internet queries are going to contain dots (like www.debian.org), and
therefore the search domain isn't used. But just in case you ever
try to hand a LAN hostname like "tlm" to a progra
urn querys my isp after NATing the request, to look up the name.
That way the only 2 limitations on local host and domain names is that
they cannot start with a number, but must be alpha. And they must NOT be
volatile. Which explains why one of my machines, a 6040 4 axis milliing
machine, is calle
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.
>
> Int
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.
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
1 - 100 of 1011 matches
Mail list logo
