Hi,
On Fri, Apr 04, 2025 at 05:21:45AM -0400, gene heskett wrote:
> On 4/3/25 13:39, Andy Smith wrote:
> > Historically we do not get very far here when talking about IPv6 with
> > Gene.
> True Andy, but there's no ipv6 within 100 miles of me.
The Linux kernel comes with IPv6 on every interface (
On 4/3/25 13:39, Andy Smith wrote:
Hi,
On Thu, Apr 03, 2025 at 01:28:43PM -, Greg wrote:
On 2025-04-03, Dan Purgert wrote:
Indeed, the entirety of 127.0.0.0/8 is the virtual loopback adapter
(i.e. "localhost").
I thought IPV6 opened up the flood gates of assigning "real" ip
addresses
In
Hi,
On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> Without the conf package, I still don't get why it populated only one
> ipv4 nameserver target and ignored the ipv6 target.
Are you sure this is not just what the installation process did?
Without "resolvconf" the /etc/resolv.conf file i
Hi,
On Thu, Mar 27, 2025 at 03:24:24PM -, Greg wrote:
> I wonder humorously if this discussion might devolve into yet another
> gargantuan thread concerning resolv.conf and whether it's kosher to set
> the immutable bit on that file in order to prevent whatever the heck is
> writing to it fro
On 2025-03-27, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
>> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
>> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
>> > there's limited things that would be editing it.
On Thu, Mar 27, 2025 at 13:58:49 +, Andy Smith wrote:
> I think all DHCP clients in Debian have a "Recomends" relationship on
> resolvconf to do this modification for them.
hobbit:~$ apt-cache show isc-dhcp-client | grep -e Recommends -e resolv
Recommends: isc-dhcp-common
Suggests: resolvconf,
Hi,
On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
> > there's limited things that would be editing it. The guesses of "you"
> > or "the installer
On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> > Without the conf package, I still don't get why it populated only one
> > ipv4 nameserver target and ignored the ipv6 target.
>
> Are you sure this is not just what the ins
The interfaces.d directory was empty.
>
root@debian:/home/user:/etc/network/interfaces.d# ls -lt
total 0
Adding that package did add the missing v6 nameserver successfully -
thank you *Greg* !
To your question on the resolv.conf file - on another 12.10 machine, I
have the same conf and the file
On Thu, Mar 27, 2025 at 14:34:13 +1030, Mal wrote:
> root@debian:/home/user# more /etc/network/interfaces
> source /etc/network/interfaces.d/*
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> allow-hotplug enp1s0
> iface enp1s0 inet static
> address 12.34.56.78
> net
Hi,
On Thu, Mar 27, 2025 at 02:34:13PM +1030, Mal wrote:
> On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
> with both IPv4 & IPv6 addressing and Name-servers set.
I don't know why only your IPv4 address is making it into resolv.conf,
but if the network setup is static th
The issue is the missing nameserver target in resolv. I am expecting
two in the echo.
Receiving records over the only nameserver target (v4) works fine
as expected - using DIG or ping.
In my configuration no IPv6 nameserver target is present in resolv,
hence it will never use IPv6 towards
Mal writes:
> On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
> with both IPv4 & IPv6 addressing and Name-servers set.
[...]
> On another older machine (running kernel 4.9.35-v7+) with exactly the
> same configuration layout, I get BOTH the IPv4 & IPv6 addresses returne
Hello,
first of all the nameservers in /etc/resolv.conf are queried in order.
That means the 2'nd one is only queried when the first one does not
answer. Even NXDOMAIN is a valid answer.
So the first one should also return IPv6 over a IPv4 connection.
How do you query the nameserver? dig, 'get
On Fri, 2 Feb 2024, Ralph Aichinger wrote:
Hi fellow Debian users!
In my quest to advance the IPv6 preparedness of my home LAN I want to
find a solution to use IP tokens on all my clients. IP tokens (keeping
the host part of the IPv6 address static while getting the subnet part
by SLAAC) seem v
On Fri, 2024-02-02 at 15:31 +0100, Marco Moock wrote:
> It should be if you enter "save" in the nmcli.
Thanks, I did not realize this was possible. I probably
will use nmcli more often in the future.
Ralph
Am 02.02.2024 schrieb Ralph Aichinger :
> On Fri, 2024-02-02 at 14:28 +0100, Marco Moock wrote:
> > # nmcli c mod enp4s0 ipv6.addr-gen-mode eui64
> > # nmcli c mod enp4s0 ipv6.token ::deca:fbad:c0:ffee
>
> This is not permanent, is it?
It should be if you enter "save" in the nmcli.
On Fri, 2024-02-02 at 14:28 +0100, Marco Moock wrote:
> In the past the default was to use EUI-64 and have the MAC address in
> the address. If that is suitable for you (privacy!), use that.
I basically don't care about the privacy aspect for now (it is more of
a lab setup, and my IPv4 address is
Am 02.02.2024 schrieb Ralph Aichinger :
> In my quest to advance the IPv6 preparedness of my home LAN I want to
> find a solution to use IP tokens on all my clients. IP tokens (keeping
> the host part of the IPv6 address static while getting the subnet part
> by SLAAC) seem very elegant to me, bec
Am 08.01.2024 um 13:01:38 Uhr schrieb Andreas B:
> I haven't checked thoroughly (yet), but the only immediate difference
> I can see, is that the router lifetime is 600 seconds (RA). My ISP's
> router used a lifetime of 86400 seconds (24h), I think.
That affect when the old addresses must be remo
A follow up on this.
I recently swapped my ISP's router with my own.
New temp-addresses are now generated when old ones become deprecated, as
expected.
I haven't checked thoroughly (yet), but the only immediate difference I can
see, is that the router lifetime is 600 seconds (RA).
My ISP's rout
On 8/13/23 13:59, Celejar wrote:
On Fri, 10 Feb 2023 16:20:00 +0300
Reco wrote:
Hi.
On Fri, Feb 10, 2023 at 08:04:38AM -0500, Greg Wooledge wrote:
On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
hosts: files mymachines dns myhostname
This is wrong.
But I
On Fri, 10 Feb 2023 16:20:00 +0300
Reco wrote:
> Hi.
>
> On Fri, Feb 10, 2023 at 08:04:38AM -0500, Greg Wooledge wrote:
> > On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
> > > hosts: files mymachines dns myhostname
> >
> > This is wrong.
>
> You're correct, but f
Arno,
Thank you so much for your prompt response.
Very interesting that it's working as expected for you.
At least I can isolate the problem to being local for my network.
I asked about this in #debian on irc, and it was suggested that I
check if I use dhcpv6 or dhcpv6-pd. I'm not 100% into ipv6
Hi Andreas,
Am 26.06.2023 um 11:13 schrieb Andreas B:
Hi,
I'm very puzzled by the behaviour of ipv6 temp addresses on Debian 12.
Expected behaviour: as soon as a temp address becomes deprecated, a
new one is generated. This is the behaviour on Debian 11.
Reasonable expectation, I think.
..
On Wed, 24 May 2023, cor...@free.fr wrote:
greetings,
today I got a server from OVH with ipv6 only.
is there any lightweight getting started tutorial for using ipv6 on debian?
such as ipv6 setup, route, filters, DNS, etc.
thanks in advance.
Corey
Do you mean already configured and working o
Am Tue, Feb 14, 2023 at 01:41:41PM -0500 schrieb gene heskett:
Hello Gene and Dave,,
> On 2/14/23 10:49, David Wright wrote:
> > Wisely done: we don't need it twice … and logs can be lengthy.
[...]
> Alright guys, I may have an existing system here that shows a 169, but not
> as default. Runnin
On Wed, Feb 15, 2023 at 11:49:51AM +0100, to...@tuxteam.de wrote:
On Tue, Feb 14, 2023 at 03:07:08PM -0500, Michael Stone wrote:
On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote:
> On Fri, 10 Feb 2023, jeremy ardley wrote:
> > you can ping them as in
> >
> > ping fe80::87d:c6ff:fea4:a
On Wed, Feb 15, 2023 at 04:24:36PM -0500, gene heskett wrote:
you basically just made this up
No Michael, just recalling our interaction history, the general tone
being to give me hell for using hosts files instead of running a dns.
I have not told you that you need to use bind instead of hos
On 2/15/23 13:08, Michael Stone wrote:
On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
True. But I'd also suggest that if you do not want to support
/etc/hosts files name resolution methods
/etc/hosts works and has worked fine on debian for decades
I've got around 5 machines sti
On Wed, Feb 15, 2023 at 01:07:29PM -0500, Michael Stone wrote:
> On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
> > True. But I'd also suggest that if you do not want to support /etc/hosts
> > files name resolution methods
>
> /etc/hosts works and has worked fine on debian for decad
On Wed, Feb 15, 2023 at 10:12:32AM -0500, Greg Wooledge wrote:
Sorry, Gene's line was actually "search hosts, nameserver".
So, "ping coyote" should have triggered name resolution for "coyote.hosts"
and/or "coyote.nameserver".
It's just barely conceivable that *something* might have created a
re
On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote:
True. But I'd also suggest that if you do not want to support
/etc/hosts files name resolution methods
/etc/hosts works and has worked fine on debian for decades
to. Your attitude that everybody with a two machine home network
shou
On Wed, Feb 15, 2023 at 10:04:14AM -0500, Greg Wooledge wrote:
> The part I still don't understand is how adding "search files, nameserver"
> to /etc/resolv.conf and rebooting could change the behavior of any of
> Gene's commands.
Sorry, Gene's line was actually "search hosts, nameserver".
So, "p
On Wed, Feb 15, 2023 at 08:34:49AM -0500, Michael Stone wrote:
> On Wed, Feb 15, 2023 at 07:30:44AM -0500, Greg Wooledge wrote:
> > That said, I'm curious about this part oF Gene's result:
> >
> > > > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > > > 192.168.71.12 bpi54.coyote.den
On 2/15/23 09:20, Charles Curley wrote:
On Wed, 15 Feb 2023 07:57:09 -0500
gene heskett wrote:
192.168.71.4sixty40.coyote.den sixty40
192.168.71.7vna.coyote.deb vna
I think you have a typo in the line for vna.
Correct, Charles, but that machine died 2 o
On 2/15/23 08:41, Michael Stone wrote:
On Wed, Feb 15, 2023 at 07:57:09AM -0500, gene heskett wrote:
And this disclosed that I had not properly added coyote.coyote.den to
the /etc/hosts file on that machine. That mistake, fixed, now makes
the local net pingable. The rest of it, whats powered up
On Wed, 15 Feb 2023 07:57:09 -0500
gene heskett wrote:
> 192.168.71.4 sixty40.coyote.den sixty40
> 192.168.71.7 vna.coyote.deb vna
I think you have a typo in the line for vna.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescu
On Wed, Feb 15, 2023 at 03:46:21PM +0300, Reco wrote:
libnss-myhostname does that.
Why it chooses ipv6 link-local over ipv4 static IP is another question.
perhaps because ipv6 is preferred and there is no public ip6. it doesn't
really matter because normal users won't notice or care whether it
On Wed, Feb 15, 2023 at 07:57:09AM -0500, gene heskett wrote:
And this disclosed that I had not properly added coyote.coyote.den to
the /etc/hosts file on that machine. That mistake, fixed, now makes
the local net pingable. The rest of it, whats powered up, was/is all
pingable. It just wasn't t
On Wed, Feb 15, 2023 at 07:30:44AM -0500, Greg Wooledge wrote:
That said, I'm curious about this part oF Gene's result:
> gene@bpi54:~$ grep -i bpi54 /etc/hosts
> 192.168.71.12 bpi54.coyote.denbpi54
> gene@bpi54:~$ getent hosts bpi54
> fe80::4765:bca4:565d:3c6 bpi54
Wher
On 2/15/23 07:31, Greg Wooledge wrote:
On Wed, Feb 15, 2023 at 08:30:08AM +0100, Michel Verdier wrote:
Le 15 février 2023 gene heskett a écrit :
gene@bpi54:~$ grep -i bpi54 /etc/hosts
192.168.71.12 bpi54.coyote.denbpi54
gene@bpi54:~$ getent hosts bpi54
fe80::4765:bca4:565d:3c
Hi.
On Wed, Feb 15, 2023 at 07:30:44AM -0500, Greg Wooledge wrote:
> That said, I'm curious about this part oF Gene's result:
>
> > > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > > 192.168.71.12 bpi54.coyote.denbpi54
> > > gene@bpi54:~$ getent hosts bpi54
> > > fe80::4
On 2/15/23 02:30, Michel Verdier wrote:
Le 15 février 2023 gene heskett a écrit :
gene@bpi54:~$ grep -i bpi54 /etc/hosts
192.168.71.12 bpi54.coyote.denbpi54
gene@bpi54:~$ getent hosts bpi54
fe80::4765:bca4:565d:3c6 bpi54
gene@bpi54:~$ ping -c1 coyote (this machines alias in /e
On Wed, Feb 15, 2023 at 08:30:08AM +0100, Michel Verdier wrote:
> Le 15 février 2023 gene heskett a écrit :
>
> > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > 192.168.71.12 bpi54.coyote.denbpi54
> > gene@bpi54:~$ getent hosts bpi54
> > fe80::4765:bca4:565d:3c6 bpi54
> > gene@bp
On Tue, Feb 14, 2023 at 03:07:08PM -0500, Michael Stone wrote:
> On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote:
> > On Fri, 10 Feb 2023, jeremy ardley wrote:
> > > you can ping them as in
> > >
> > > ping fe80::87d:c6ff:fea4:a6fc
> > >
> >
> > ooh, I didn't know that worked.
> >
>
Le 15 février 2023 gene heskett a écrit :
> gene@bpi54:~$ grep -i bpi54 /etc/hosts
> 192.168.71.12 bpi54.coyote.denbpi54
> gene@bpi54:~$ getent hosts bpi54
> fe80::4765:bca4:565d:3c6 bpi54
> gene@bpi54:~$ ping -c1 coyote (this machines alias in /etc/hosts)
> ping: coyote: Name or s
On 2/14/23 18:12, Greg Wooledge wrote:
On Tue, Feb 14, 2023 at 05:51:52PM -0500, gene heskett wrote:
Already done that a month or so ago, to satisfy my own curiosity, the answer
is yes host lookups did fail again without it.
And just to make sure, I just went to it, removed the lsattr i, from
r
On Tue, Feb 14, 2023 at 05:51:52PM -0500, gene heskett wrote:
> Already done that a month or so ago, to satisfy my own curiosity, the answer
> is yes host lookups did fail again without it.
>
> And just to make sure, I just went to it, removed the lsattr i, from
> resolv.conf, commented that line
On 2/14/23 15:20, Greg Wooledge wrote:
On Tue, Feb 14, 2023 at 03:01:18PM -0500, Michael Stone wrote:
On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
Yes Greg, you keep telling me that. But I'm in the process of bringing
up a 3dprinter farm, each printer with a bpi5 to manage octo
On Tue, Feb 14, 2023 at 03:01:18PM -0500, Michael Stone wrote:
> On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
> > Yes Greg, you keep telling me that. But I'm in the process of bringing
> > up a 3dprinter farm, each printer with a bpi5 to manage octoprint. Joing
> > the other 4 on t
On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote:
On Fri, 10 Feb 2023, jeremy ardley wrote:
you can ping them as in
ping fe80::87d:c6ff:fea4:a6fc
ooh, I didn't know that worked.
Same as
ping fe80::87d:c6ff:fea4:a6fc%eth0
on my machines at least. No idea how it picks the interfac
On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote:
Yes Greg, you keep telling me that. But I'm in the process of bringing
up a 3dprinter farm, each printer with a bpi5 to manage octoprint.
Joing the other 4 on this net running buster and linuxcnc.
Just last week I added another bpi5
On Tue, Feb 14, 2023 at 07:42:59PM +, Brian wrote:
I was attracted by this idea and it gave me pause for
thought. Leaving aside printers that include a network
interface, the IPP-over-USB standard applies to a
non-network-capable printer.
The specs require IPP (put in firmware, I suppose)
On 2/14/23 10:49, David Wright wrote:
Wisely done: we don't need it twice … and logs can be lengthy.
I have seen the 169.254.xxx.yyy on my system, too.
It is a Debian Bullseye. To check if Debian works on this hardware I
have simply select the xfce4 option in the installer. Either the avahi
stu
Am Tue, Feb 14, 2023 at 09:48:11AM -0600 schrieb David Wright:
Hello David,
> On Mon 13 Feb 2023 at 11:39:31 (+0100), Christoph Brinkhaus wrote:
> > Am Sat, Feb 11, 2023 at 09:29:16PM -0600 schrieb David Wright:
> > > On Fri 10 Feb 2023 at 06:40:42 (+0100), to...@tuxteam.de wrote:
> > > > On Thu,
David Wright (12023-02-14):
> > lsusb -v > /tmp/1
> > sudo lsusb -v > /tmp/2
> > diff -u /tmp/1 /tmp/2
> Irrespective of the lines that interested Brian, how did your system
> manage to produce no output
I copy-pasted only the commands, not their output.
Regards,
--
Nicolas George
On Tue 14 Feb 2023 at 13:32:37 (+0100), Nicolas George wrote:
> Brian (12023-02-14):
> > > FWIW, if you invoke lsusb with the -v option, you need
> > > some superpowers. So better "sudo lsusb -v".
> > I do not believe that to be the case.
>
> experiment > belief
>
> lsusb -v > /tmp/1
> sudo lsusb
On Mon 13 Feb 2023 at 11:39:31 (+0100), Christoph Brinkhaus wrote:
> Am Sat, Feb 11, 2023 at 09:29:16PM -0600 schrieb David Wright:
>
> please excuse the late reply. I have had a side discussion with Tomas
> in German about the issue I observed, too.
>
> > On Fri 10 Feb 2023 at 06:40:42 (+0100),
> Network printers from 2016 almost certainly (always in my
> experience) do ship with IPP-over-USB. For some reason USB-only
> devices generally do not provide it; it's very hit-and-miss.
IPP-over-USB basically requires the whole traditional networking stack,
so it's no surprise that it's usually
On 2/14/23 07:58, Brian wrote:
[...]
Brother HL-L2320D L2300D best budget laser printer review
https://www.youtube.com › watch
7:51
A quick demonstration and review of the Brother HL-L2320D laser printer.Buy it
on Amazon here: http://amzn.to/2haHDsdOr buy the similar ...
YouTube · DarkStoneCastl
On Tue 14 Feb 2023 at 14:02:05 +0100, Nicolas George wrote:
> Greg Wooledge (12023-02-14):
> > It's certainly more than "the error messages went away".
>
> Yes, but Reco was smarter than us, with the "> /dev/null".
OK, my belief, backed up by experience, is that sudo is
not needed to obtain the
On 2/14/23 07:21, Greg Wooledge wrote:
On Tue, Feb 14, 2023 at 07:07:58AM -0500, gene heskett wrote:
On 2/14/23 06:29, Brian wrote:
Anyway, this USB-only printer from 2016 does not provide
an IPP-over-USB service. This is not unexpected.
Are you saying that this printer has been sitting on th
Greg Wooledge (12023-02-14):
> It's certainly more than "the error messages went away".
Yes, but Reco was smarter than us, with the "> /dev/null".
Regards,
--
Nicolas George
On Tue, Feb 14, 2023 at 03:37:58PM +0300, Reco wrote:
> lsusb -v >/dev/null
>
> sudo lsusb -v >/dev/null
>
>
> First one shows: "Couldn't open device, some information will be
> missing". Second one does not.
diff -u <(lsusb -v 2>&1) <(sudo lsusb -v 2>&1) | less
gives me 252 lines of diff outp
On Tue 14 Feb 2023 at 07:21:00 -0500, Greg Wooledge wrote:
> On Tue, Feb 14, 2023 at 07:07:58AM -0500, gene heskett wrote:
> > On 2/14/23 06:29, Brian wrote:
> > > Anyway, this USB-only printer from 2016 does not provide
> > > an IPP-over-USB service. This is not unexpected.
> > >
> > Are you say
Hi.
On Tue, Feb 14, 2023 at 01:32:37PM +0100, Nicolas George wrote:
> Brian (12023-02-14):
> > > FWIW, if you invoke lsusb with the -v option, you need
> > > some superpowers. So better "sudo lsusb -v".
> > I do not believe that to be the case.
>
> experiment > belief
Indeed.
lsusb -v >
Brian (12023-02-14):
> > FWIW, if you invoke lsusb with the -v option, you need
> > some superpowers. So better "sudo lsusb -v".
> I do not believe that to be the case.
experiment > belief
lsusb -v > /tmp/1
sudo lsusb -v > /tmp/2
diff -u /tmp/1 /tmp/2
Regards,
--
Nicolas George
On Tue, Feb 14, 2023 at 07:07:58AM -0500, gene heskett wrote:
> On 2/14/23 06:29, Brian wrote:
> > Anyway, this USB-only printer from 2016 does not provide
> > an IPP-over-USB service. This is not unexpected.
> >
> Are you saying that this printer has been sitting on the Staples display for
> 5 ye
On 2/14/23 06:29, Brian wrote:
On Tue 14 Feb 2023 at 06:23:34 +0100, to...@tuxteam.de wrote:
On Mon, Feb 13, 2023 at 04:04:29PM -0500, gene heskett wrote:
On 2/13/23 14:10, Brian wrote:
lsusb -v | grep -A 3 bInterfaceClass.*7
FWIW, if you invoke lsusb with the -v option, you need
some super
On Tue 14 Feb 2023 at 06:23:34 +0100, to...@tuxteam.de wrote:
> On Mon, Feb 13, 2023 at 04:04:29PM -0500, gene heskett wrote:
> > On 2/13/23 14:10, Brian wrote:
> > > lsusb -v | grep -A 3 bInterfaceClass.*7
>
> FWIW, if you invoke lsusb with the -v option, you need
> some superpowers. So better "
On Mon, Feb 13, 2023 at 04:04:29PM -0500, gene heskett wrote:
> On 2/13/23 14:10, Brian wrote:
> > lsusb -v | grep -A 3 bInterfaceClass.*7
FWIW, if you invoke lsusb with the -v option, you need
some superpowers. So better "sudo lsusb -v".
Cheers
--
t
signature.asc
Description: PGP signature
On 2/13/23 14:10, Brian wrote:
lsusb -v | grep -A 3 bInterfaceClass.*7
gene@coyote:~/Downloads/3dp.stf/trident/stl.stf_from_slipper/02面板安装部分$
lsusb -v | grep -A 3 bInterfaceClass.*7
Couldn't open device, some information will be missing
Couldn't open device, some information will be missing
On 2/13/23 12:12, Brian wrote:
And the model of b&w laser?
HL-L2320D
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make
On Mon 13 Feb 2023 at 11:21:00 -0500, gene heskett wrote:
> On 2/13/23 10:30, Brian wrote:
> > On Mon 13 Feb 2023 at 10:08:22 -0500, gene heskett wrote:
> >
> > > On 2/13/23 10:00, Brian wrote:
> > > > On Mon 13 Feb 2023 at 09:30:32 -0500, gene heskett wrote:
> > > >
> > > > > On 2/13/23 06:01,
On Mon 13 Feb 2023 at 11:11:38 -0500, gene heskett wrote:
[...]
> "Distributed by Debian" is the key phrase here. That qualifier apparently
> does not include the better Brothers.
The Brother drivers are non-free. They will cease to work.
It will be up to Brother to accomodate them to the New
A
On 2/13/23 10:30, Brian wrote:
On Mon 13 Feb 2023 at 10:08:22 -0500, gene heskett wrote:
On 2/13/23 10:00, Brian wrote:
On Mon 13 Feb 2023 at 09:30:32 -0500, gene heskett wrote:
On 2/13/23 06:01, Brian wrote:
On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
On Sun, Feb 12, 20
On 2/13/23 10:00, Brian wrote:
On Mon 13 Feb 2023 at 09:30:32 -0500, gene heskett wrote:
On 2/13/23 06:01, Brian wrote:
On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
[...]
Fortunately, the vast majority of users with a
On 2/13/23 10:00, Brian wrote:
On Mon 13 Feb 2023 at 09:30:32 -0500, gene heskett wrote:
On 2/13/23 06:01, Brian wrote:
On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
[...]
Fortunately, the vast majority of users with a
On Mon 13 Feb 2023 at 09:30:32 -0500, gene heskett wrote:
> On 2/13/23 06:01, Brian wrote:
> > On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
> >
> > > On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
> > >
> > > [...]
> > >
> > > > Fortunately, the vast majority of users w
On Mon, Feb 13, 2023 at 09:25:22AM -0500, gene heskett wrote:
[...]
> Ahh nice Tomas, until it says Brother on the printer. Brother has a system
> of drivers AND a Linux installer that will make their printers work exactly
> on Linux as they do on windows [...]
Last Brother I had was straight PS
On 2/13/23 06:01, Brian wrote:
On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
[...]
Fortunately, the vast majority of users with a modern printer have
not taken a similar view. They now enjoy an effortless and enjoyable
pr
On Mon, Feb 13, 2023 at 11:00:48AM +, Brian wrote:
[...]
> > My printer is all well, thankyouverymuch. Whenever I'm after an
> > "experience", I take my bike and ride to the mountains, very
> > enjoyable :)
>
> Such a journey would give ample opportunity to ponder why mDNS
> multicasting is
On Mon 13 Feb 2023 at 09:25:15 +0100, to...@tuxteam.de wrote:
> On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
>
> [...]
>
> > Fortunately, the vast majority of users with a modern printer have
> > not taken a similar view. They now enjoy an effortless and enjoyable
> > printing experien
Am Sat, Feb 11, 2023 at 09:29:16PM -0600 schrieb David Wright:
Hi David,
please excuse the late reply. I have had a side discussion with Tomas
in German about the issue I observed, too.
> On Fri 10 Feb 2023 at 06:40:42 (+0100), to...@tuxteam.de wrote:
> > On Thu, Feb 09, 2023 at 03:32:46PM -0500
On Sun, Feb 12, 2023 at 07:12:42PM +, Brian wrote:
[...]
> Fortunately, the vast majority of users with a modern printer have
> not taken a similar view. They now enjoy an effortless and enjoyable
> printing experience.
My printer is all well, thankyouverymuch. Whenever I'm after an
"experie
On Sun 12 Feb 2023 at 07:55:04 +0100, to...@tuxteam.de wrote:
> On Sat, Feb 11, 2023 at 09:29:16PM -0600, David Wright wrote:
[...]
> > So it's difficult to figure out why some are plagued by these
> > addresses, made worse when one gets used for the default route, eg
> > https://lists.debian.
* On 2023 11 Feb 21:30 -0600, David Wright wrote:
> I've read that machines give themselves a 169.254.… address when they
> boot up and can't find a DHCP server. But I never see those addresses
> when I boot up a machine, disconnected or connected. All I see is
> localhost on 127.0.0.1, the machine
On Sat, Feb 11, 2023 at 09:29:16PM -0600, David Wright wrote:
> My systems all have avahi-daemon and avahi-utils installed, and the
> laptops have avahi-autoipd as well, but I never see 169.254.…
> addresses in the output of ip a¹ or in the logs², or in the output
> of avahi-browse -art³ (
On Fri 10 Feb 2023 at 06:40:42 (+0100), to...@tuxteam.de wrote:
> On Thu, Feb 09, 2023 at 03:32:46PM -0500, gene heskett wrote:
> > On 2/9/23 07:53, to...@tuxteam.de wrote:
> > > On Thu, Feb 09, 2023 at 07:32:18AM -0500, Greg Wooledge wrote:
> > >
> > > [...]
> > >
> > > > (I have no idea what md
On Fri, Feb 10, 2023 at 02:11:43PM +, Darac Marjal wrote:
> "mymachines" comes from libnss-mymachines:
> "myhostname" comes from libnss-myhostname:
Fascinating. And confusing.
So, Gene's Armbian distribution uses those packages by default, and
Debian does not, right?
Either way, those entr
On 2/10/23 08:05, Greg Wooledge wrote:
On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
hosts: files mymachines dns myhostname
This is wrong. I don't know where you got it from, but "mymachines"
and "myhostname" are not valid entries in this file. NOT EVEN IF THEY
ARE F
On 2/10/23 06:15, Carles Pina i Estany wrote:
Hi,
I'm just an interested reader (now writer?) of this thread and many
other threads here.
On Feb/10/2023, gene heskett wrote:
gene@coyote:~$ cat /sshnet/bpi54/etc/nsswitch.conf:
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Servic
On Fri, 10 Feb 2023, jeremy ardley wrote:
you can ping them as in
ping fe80::87d:c6ff:fea4:a6fc
ooh, I didn't know that worked.
Same as
ping fe80::87d:c6ff:fea4:a6fc%eth0
on my machines at least. No idea how it picks the interface when there's
more than one.
The interface seems mandatory
On 10/02/2023 13:04, Greg Wooledge wrote:
On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
hosts: files mymachines dns myhostname
This is wrong. I don't know where you got it from, but "mymachines"
and "myhostname" are not valid entries in this file. NOT EVEN IF THEY
AR
Hi.
On Fri, Feb 10, 2023 at 08:04:38AM -0500, Greg Wooledge wrote:
> On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
> > hosts: files mymachines dns myhostname
>
> This is wrong.
You're correct, but for the wrong reason.
> I don't know where you got it from, but "
On Fri, Feb 10, 2023 at 05:58:07AM -0500, gene heskett wrote:
> hosts: files mymachines dns myhostname
This is wrong. I don't know where you got it from, but "mymachines"
and "myhostname" are not valid entries in this file. NOT EVEN IF THEY
ARE FUCKING METASYNTACTIC PLACEHOLDERS for "co
Hi,
On Feb/10/2023, to...@tuxteam.de wrote:
> > > gene@bpi54:~$ pinfo libc "name server switch"
> >
> > I think that you intended to use "info", not "pinfo"?
>
> pinfo is a program (part of the like-named package) for people who
> want to miss what info has to offer -- uh -- an alternative us
On Fri, Feb 10, 2023 at 11:05:22AM +, Carles Pina i Estany wrote:
>
> Hi,
>
> I'm just an interested reader (now writer?) of this thread and many
> other threads here.
>
> On Feb/10/2023, gene heskett wrote:
>
> > gene@coyote:~$ cat /sshnet/bpi54/etc/nsswitch.conf:
> >
> > # /etc/nsswitch.
Hi,
I'm just an interested reader (now writer?) of this thread and many
other threads here.
On Feb/10/2023, gene heskett wrote:
> gene@coyote:~$ cat /sshnet/bpi54/etc/nsswitch.conf:
>
> # /etc/nsswitch.conf
> #
> # Example configuration of GNU Name Service Switch functionality.
> # If you hav
1 - 100 of 370 matches
Mail list logo
