Re: How to download source package using only console?

[Alexander V. Makartsev]

On 15.05.2023 05:43, Vincent Lefevre wrote:

On 2023-05-14 14:17:05 +0500, Alexander V. Makartsev wrote:

[...]
I think you haven't noticed that I requested for "4.9.1-1" version from
"testing" specifically,

You can't. You can either request some given version, e.g. 4.9.1-1
(but this will work only if it can be found from your local database),
or the version from some given distribution, e.g. "testing".

But my point is that your database is obsolete, because if you ask
the version from testing, apt thinks that it is 3.2.0-3.1, while it
should be 4.9.1-1. You need to fix that.
What is the best approach to fix that? Keep in mind, I only need a 
source package(-s) from "testing".

So, just to be safe, "deb" source for "testing" was commented out:

   $ cat /etc/apt/sources.list | grep -iE "testing"
   #deb https://deb.debian.org/debian/ testing main contrib non-free
   deb-src https://deb.debian.org/debian/ testing main contrib non-free



hence why the command was "$ apt source lego/testing" not just "$ apt source
lego".
There is no reason for building a backport package for "stable" using a
source package from "stable"...

I've changed all my repo mirrors to "deb.debian.org" suspecting the previous
mirror I used was somehow out-of-date. Why is my output differ from yours?

$ apt-show-versions -a lego
lego:amd64 3.2.0-3.1+b5 bullseye deb.debian.org
No proposed-updates version
No stable-updates version
No testing version
No unstable version
lego:amd64 not installed
lego:i386 3.2.0-3.1+b5 bullseye deb.debian.org
No proposed-updates version
No stable-updates version
No testing version
No unstable version
lego:i386 not installed

After changing your sources.list, you need an "apt update" again.
Of course, I always do "$ sudo apt update" after changing apt config 
files and before any package manipulation.



Yet "rmadison" reports there is a version "4.9.1-1" available in "testing":

$ rmadison lego
lego   | 0.3.1-5+b13   | oldstable  | amd64, arm64, armel,
armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
lego   | 3.2.0-3.1+b5  | stable | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
lego   | 4.9.1-1   | testing    | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x
lego   | 4.9.1-1   | unstable   | amd64, arm64, armel,
armhf, i386, mips64el, mipsel, ppc64el, s390x

I suspect "apt-show-versions" output is inconsistent because I only request
"deb-src" from "testing" in "sources.list", as I've shown before.

Probably. "apt-show-versions" considers only the binary packages
(but "lego" is only a binary package).
I see. "rmadison" utility is checking out repos directly, where as 
"apt-show-versions" rely on local database information.



[...]

I did some additional research and I think I got it.
"lego" package is special because its source package is named differently:

Yes, as said by apt above:

   Picking 'golang-github-xenolf-lego' as source package instead of 'lego'

[...]

But why "apt" doesn't play along, since it knows the source package for
"lego" has different name, but ignores the "testing" part of the request?

$ apt source lego/testing
Reading package lists... Done
Picking 'golang-github-xenolf-lego' as source package instead of 'lego'
E: Can not find version '3.2.0-3.1' of package 'lego'
E: Unable to find a source package for golang-github-xenolf-lego

Looks like an "apt" bug to me.

Probably not. You are doing a request on a binary package (since
"lego" is not a source package). The translation from the binary
package to the source package depends on the particular version of
the binary package. So lego/testing will correspond to the binary
package from testing, which is 3.2.0-3.1+b5 in your case (because
of your obsolete database due to the missing "deb" for testing in
sources.list). Then apt translates this to the source package (of
the same version) golang-github-xenolf-lego 3.2.0-3.1, which is
unknown on your machine because the deb-src database is up-to-date
(contrary to the deb database). Something like that.

I see. That explains why I can request source package 
"golang-github-xenolf-lego/testing" directly and get the right one.
So, in my case, I won't be able to reliably get a source package(-s) 
from "testing" if I don't add "deb" part of "testing" to "sources.list", 
which could be a different can of worms...
Is this something for me to just be aware of and leave it as is now, or 
is there more elegant solution?


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: how to find out regdomain/country of wifi network

[David Wright]

On Mon 15 May 2023 at 06:37:32 (+0200), to...@tuxteam.de wrote:
> On Sun, May 14, 2023 at 01:59:10PM -0500, David Wright wrote:
> 
> [...]
> 
> > Final thought from this (lwn) source:
> > 
> >  "Software transitions like this are invariably an unwanted
> >   distraction [...] But the world we live in does not stand
> >   still, so such transitions are simply going to happen [...]
> 
> To me, this seems like an unnecessary authoritarian stance,
> which, in free software's context seems strange.
> 
> As long as there are maintainers and upstream I see no reason
> to drop a package.

It doesn't necessarily imply dropping any package, but just that
if a new package is written that handles cases that the old
package can't, then gradually the old package may break under
various circumstances, and the people who might have fixed it
may have moved on.

AIUI, in the packages under discussion, ifconfig both lacks
netlink support, and produces wrong information when it
encounters information it doesn't understand. So the transition
is not just because "ip is better than ifconfig", but because
ifconfig just isn't up to it in certain situations.

> Which one is the default, of course, is a decision to be taken
> by the distribution as a whole. After all, the system scripts
> have to be adapted to it.

Choosing ifconfig as the default would be a strange choice indeed.

> And whining is not maintaining, so if someone really wants the
> package, (s)he better puts the keyboard where the mouth is :)

I read somewhere that the recent tweaks (improvements?) to
ifconfig's output were breaking scripts, which is hardly surprising.

Cheers,
David.

Re: how to find out regdomain/country of wifi network

[tomas]

On Sun, May 14, 2023 at 09:11:55PM +, Andy Smith wrote:
> Hello,
> 
> On Sun, May 14, 2023 at 08:08:06PM +0200, to...@tuxteam.de wrote:
> > I think the problem here is that the user dreamt up a feature ifconfig
> > has never had. At least not the linux ifconfig.
> 
> Yes, it seems their use of FreeBSD ifconfig led them to believe that
> ifconfig would work the same on every platform.
> 
> So would you agree that had Debian NOT given in to the people who
> demanded ifconfig remain packaged, OP would have been in a better
> position as then they would have known that ifconfig is not the
> command they need in Debian even if it is in FreeBSD?

As I mentioned in another post -- no, I don't like authoritarian
approaches. As long as someone's willing to keep the thing alive
(upstream and packaging) it should exist.

Cheers
-- 
t 


signature.asc
Description: PGP signature

Re: how to find out regdomain/country of wifi network

[tomas]

On Sun, May 14, 2023 at 03:44:42PM -0400, Jeffrey Walton wrote:

[...]

> Boy, this thread reached critical mass and melted down quickly...

Probably with a reason (OK, there were some blind alleys
around, as that one giving ifconfig powers it never had,
at least in Linux distros), but those transitions are
always big social events. No wonder there's discussion.

I think this is healthy.

> Is this going to be another thread that never dies :)

With a live community you get that from time to time.
People have been polite all along, as far as I can see.
What's not to like?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: how to find out regdomain/country of wifi network

[tomas]

On Sun, May 14, 2023 at 01:59:10PM -0500, David Wright wrote:

[...]

> Final thought from this (lwn) source:
> 
>  "Software transitions like this are invariably an unwanted
>   distraction [...] But the world we live in does not stand
>   still, so such transitions are simply going to happen [...]

To me, this seems like an unnecessary authoritarian stance,
which, in free software's context seems strange.

As long as there are maintainers and upstream I see no reason
to drop a package.

Which one is the default, of course, is a decision to be taken
by the distribution as a whole. After all, the system scripts
have to be adapted to it.

And whining is not maintaining, so if someone really wants the
package, (s)he better puts the keyboard where the mouth is :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: No space left on device ...

[Charles Curley]

On Mon, 15 May 2023 00:32:01 +
Albretch Mueller  wrote:

> when I try to save or download a file I consistently get the same
> error message:
> 
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on device

That *shouldn't* work. I get:

charles@jhegaala:~$ cp "No space left on device" > No_space_left_on_device.txt
cp: missing destination file operand after 'No space left on device'
Try 'cp --help' for more information.
charles@jhegaala:~$ 

But I do get a file created with length 0.

Try echo instead of cp:

charles@jhegaala:~$ echo "No space left on device" > No_space_left_on_device.txt
charles@jhegaala:~$ cat No_space_left_on_device.txt 
No space left on device
charles@jhegaala:~$ ll No_space_left_on_device.txt 
-rw-r--r-- 1 charles charles 24 May 14 21:04 No_space_left_on_device.txt
charles@jhegaala:~$ 

Also, I have no reason to believe from what you've shown that your
current directory is /media/user/60320G593EB7250F. Did you run

cd /media/user/60320G593EB7250F

before running the above commands? I would expect to get an
out-of-space error if I were still on the CD.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: CUPS on Bullseye and Bookworm

[Charles Curley]

On Sun, 14 May 2023 23:30:25 +0100
Brian  wrote:

> On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:


> 
> We take it that dragon, hawk and the printer are network connected.
> 
> Give what you get from dragon with
> 
>   avahi-browse -rt _ipp._tcp
>   avahi-browse -rt _uscan._tcp
>   driverless
>   lpstat -l -e
> 
> avahi-browse is in the avahi-utils package.
> 

root@dragon:~# avahi-browse -rt _ipp._tcp
+ wlp2s2 IPv4 HP LaserJet MFP M234sdw (C0FB67)  Internet Printer
 local
= wlp2s2 IPv4 HP LaserJet MFP M234sdw (C0FB67)  Internet Printer
 local
   hostname = [hpm234ethernet.local]
   address = [192.168.100.134]
   port = [631]
   txt = ["mopria-certified=2.1" "mac=6c:02:e0:c0:fb:67" "usb_MDL=HP LaserJet 
MFP M232-M237" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4" 
"kind=document,envelope,photo" "UUID=d532fa73-f559-43ca-9f8e-1eef16972345" 
"Fax=F" "Scan=T" "Duplex=T" "Color=F" "note=" 
"adminurl=http://hpm234ethernet.local./hp/device/info_config_AirPrint.html?tab=Networking&menu=AirPrintStatus";
 "priority=10" "product=(HP LaserJet MFP M232-M237)" "ty=HP LaserJet MFP 
M232-M237" "URF=V1.4,CP99,W8,OB10,PQ3-4,DM1,IS1-4,MT1-3-5,RS300-600" 
"rp=ipp/print" "pdl=application/PCLm,application/octet-stream,image/pwg-raster" 
"qtotal=1" "txtvers=1"]
root@dragon:~# avahi-browse -rt _uscan._tcp
+ wlp2s2 IPv4 HP LaserJet MFP M234sdw (C0FB67)  _uscan._tcp 
 local
= wlp2s2 IPv4 HP LaserJet MFP M234sdw (C0FB67)  _uscan._tcp 
 local
   hostname = [hpm234ethernet.local]
   address = [192.168.100.134]
   port = [8080]
   txt = ["mopria-certified-scan=1.3" "note=" "duplex=F" "is=platen,adf" 
"cs=color,grayscale" "pdl=application/pdf,image/jpeg" 
"uuid=d532fa73-f559-43ca-9f8e-1eef16972345" "rs=eSCL" 
"representation=http://hpm234ethernet.local./ipp/images/printer.png"; 
"vers=2.63" "usb_MDL=HP LaserJet MFP M232-M237" "usb_MFG=HP" "mdl=LaserJet MFP 
M232-M237" "mfg=HP" "ty=HP LaserJet MFP M232-M237" 
"adminurl=http://hpm234ethernet.local."; "txtvers=1"]
root@dragon:~# driverless
ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
root@dragon:~# lpstat -l -e
HP-HP-LaserJet-MFP-M232-M237 permanent 
ipp://localhost/printers/HP-HP-LaserJet-MFP-M232-M237 
dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345
HP-HP-LaserJet-MFP-M232-M237-2 permanent 
ipp://localhost/printers/HP-HP-LaserJet-MFP-M232-M237-2 
ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
HP-LaserJet-MFP-M232-M237 permanent 
ipp://localhost/printers/HP-LaserJet-MFP-M232-M237 
socket://hpm234ethernet.localdomain:9100
HP_LaserJet_MFP_M234sdw_C0FB67 network none 
ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
root@dragon:~# 




-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: iptables reject with TCP RST

[Andy Smith]

Hello,

On Mon, May 15, 2023 at 09:40:10AM +0800, Tom Reed wrote:
> Yes after each telnet from client host, the count was increased.
> 
> 0 0 REJECT tcp  --  anyany anywhere
> anywhere tcp dpt:imaps reject-with tcp-reset
> 0 0 REJECT tcp  --  anyany anywhere
> anywhere tcp dpt:imap2 reject-with tcp-reset
>99  4620 REJECT tcp  --  anyany anywhere
> anywhere tcp dpt:submission reject-with tcp-reset

In that case, we must conclude that the TCP RST being sent back never
gets to your source host.

You can try a tcpdump at both ends that shows only RST packets:

# tcpdump -n -v "tcp[tcpflags] & (tcp-rst) != 0"

then when you do the telnet, do you see a packet with "Flags [R…]"
at both server side and client side?

You could also try --reject-with icmp-port-unreachable to see if
that behaves differently.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: iptables reject with TCP RST

[Tom Reed]

> Hello,
>
> On Mon, May 15, 2023 at 09:10:24AM +0800, Tom Reed wrote:
>> If I clean iptables in the destination host, this telnet will get
>> success
>> at once.
>>
>> Any hints?
>
> Why have you not used "iptables -vL" to show the packet counts of
> each rule so you can see which rules the packets match? They are
> clearly matching some other earlier rule, and I suggested that in
> the email you have replied to for the exact purpose of checking that
> out.
>

Yes after each telnet from client host, the count was increased.

0 0 REJECT tcp  --  anyany anywhere
anywhere tcp dpt:imaps reject-with tcp-reset
0 0 REJECT tcp  --  anyany anywhere
anywhere tcp dpt:imap2 reject-with tcp-reset
   99  4620 REJECT tcp  --  anyany anywhere
anywhere tcp dpt:submission reject-with tcp-reset


regards


-- 
sent from https://dkinbox.com/

Bookworm soft lockup

[Christian Gelinek]

Hi,

I encountered my Debian frozen this morning. This is the 2nd time this 
happened, the 1st one was on April 10, with very similar symptoms: The 
PC was still running, but moving the mouse or typing didn't wake up my 
screens and I couldn't connect to it via SSH.


After force-rebooting, I had a look at journalctl and these are the 
messages before the reboot:


May 14 00:00:09 gar systemd[1]: Starting cups.service - CUPS Scheduler...
May 14 00:00:09 gar audit[2912]: AVC apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=2912 comm="cupsd" 
capability=12  capname="net_admin"

May 14 00:00:09 gar systemd[1]: Started cups.service - CUPS Scheduler.
May 14 00:00:09 gar kernel: audit: type=1400 audit(1683988209.079:32): 
apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=2912 
comm="cupsd" capability=12  capname="net_admin"
May 14 00:00:09 gar systemd[1]: Started cups-browsed.service - Make 
remote CUPS printers available locally.

May 14 00:00:09 gar systemd[1]: logrotate.service: Deactivated successfully.
May 14 00:00:09 gar systemd[1]: Finished logrotate.service - Rotate log 
files.
May 14 00:17:01 gar CRON[2929]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
May 14 00:17:01 gar CRON[2930]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
May 14 00:17:01 gar CRON[2929]: pam_unix(cron:session): session closed 
for user root
May 14 00:54:00 gar kernel: snd_hda_intel :04:00.0: Unable to change 
power state from D3hot to D0, device inaccessible
May 14 00:54:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
May 14 00:54:03 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:07 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
May 14 00:54:07 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]

May 14 00:54:11 gar kernel: hrtimer: interrupt took 252466383 ns
May 14 00:54:11 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
May 14 00:54:11 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:16 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* gt: timed out waiting for forcewake ack to clear.
May 14 00:54:16 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:17 gar kernel: i915 :03:00.0: [drm] *ERROR* CT: 
Corrupted descriptor head=4294967295 tail=4294967295 status=0x
May 14 00:54:26 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* render: timed out waiting for forcewake ack to clear.
May 14 00:54:26 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:26 gar kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* gt: timed out waiting for forcewake ack to clear.
May 14 00:54:26 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x230 [i915]
May 14 00:54:26 gar kernel: watchdog: BUG: soft lockup - CPU#15 stuck 
for 26s! [kworker/15:1:233]
May 14 00:54:26 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 
dns_resolver nfs lockd grace fscache netfs rfkill qrtr sunrpc 
binfmt_misc nls_ascii nls_cp437 vfat fat snd_sof_pci_>
May 14 00:54:26 gar kernel:  intel_uncore ee1004 pcspkr watchdog snd 
soundcore intel_vsec serial_multi_instantiate acpi_pad intel_pmc_core 
acpi_tad mei_me sg mei evdev parport_pc ppdev lp parport fuse loop 
efi_pstore configfs efivarfs ip_tables x_tables autof>
May 14 00:54:26 gar kernel: CPU: 15 PID: 233 Comm: kworker/15:1 Tainted: 
G U  W  6.1.0-8-amd64 #1  Debian 6.1.25-1
May 14 00:54:26 gar kernel: Hardware name: Micro-Star International Co., 
Ltd. MS-7E02/PRO B760M-P DDR4 (MS-7E02), BIOS 1.00 10/21/2022

May 14 00:54:26 gar kernel: Workqueue: pm pm_runtime_work
May 14 00:54:26 gar kernel: RIP: 0010:pci_mmcfg_read+0xb0/0xe0
May 14 00:54:26 gar kernel: Code: 5d 41 5e 41 5f c3 cc cc cc cc 4c 01 e0 
66 8b 00 0f b7 c0 89 45 00 eb dc 4c 01 e0 8a 00 0f b6 c0 89 45 00 eb cf 
4c 01 e0 8b 00 <89> 45 00 eb c5 e8 66 a2 78 ff c7 45 00 ff ff ff ff b8 
ea ff ff ff

May 14 00:54:26 gar kernel: RSP: 0018:a9d000947cc0 EFLAGS: 0286
May 14 00:54:26 gar kernel: RAX:  RBX: 0040 
RCX: 0ffc
May 14 00:54:26 gar kernel: RDX: 00ff RSI: 0004 
RDI: 
May 14 00:54:26 gar kernel: RBP: a9d000947cfc R08: 0004 
R09: a9d000947cfc

Re: iptables reject with TCP RST

[Andy Smith]

Hello,

On Mon, May 15, 2023 at 09:10:24AM +0800, Tom Reed wrote:
> If I clean iptables in the destination host, this telnet will get success
> at once.
> 
> Any hints?

Why have you not used "iptables -vL" to show the packet counts of
each rule so you can see which rules the packets match? They are
clearly matching some other earlier rule, and I suggested that in
the email you have replied to for the exact purpose of checking that
out.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: iptables reject with TCP RST

[Tom Reed]

>
> so whatever your 193.106.250.x host is, maybe it did indeed block
> the packets itself, but would be good to verify.
>

Hello

I have checked for details but didn't get the luck.

My destination host does have the rules:

REJECT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:993
reject-with tcp-reset
REJECT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:143
reject-with tcp-reset
REJECT tcp  --  0.0.0.0/00.0.0.0/0tcp dpt:587
reject-with tcp-reset


And I telnet from two different DCs (one is Dallas, another is LA), both
got timeout, rather than the expected disconnection quickly.

$ telnet 193.106.250.86 587
Trying 193.106.250.86...
telnet: Unable to connect to remote host: Connection timed out


If I clean iptables in the destination host, this telnet will get success
at once.

Any hints?

Thanks.


-- 
sent from https://dkinbox.com/

Re: No space left on device ...

[Jeffrey Walton]

On Sun, May 14, 2023 at 8:32 PM Albretch Mueller  wrote:
>
> I have been mounting an NTFS file system on a Windows laptop without
> any problems whatsoever with a Debian Live DVD:
>
> $ uname -a
> Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
> x86_64 GNU/Linux
>
> and even though Linux utilities are telling me I do have space on the drive:
>
> $ date; sudo df -h | grep "Filesystem\|/dev/sd"
> Sun 14 May 2023 06:55:23 PM UTC
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda1   286G  167G  120G  59% /media/user/60320G593EB7250F
> $
>
> $ date; time sudo du --summarize --human-readable  
> /media/user/60320G593EB7250F
> Sun 14 May 2023 07:13:43 PM UTC
> 166G/media/user/60320G593EB7250F
>
> real0m45.230s
> user0m1.073s
> sys 0m15.443s
> $
>
> when I try to save or download a file I consistently get the same error 
> message:
>
> $ cp "No space left on device" > No_space_left_on_device.txt
> bash: No_space_left_on_device.txt: No space left on device
>
> that started happening right after a WiFi connection at a library was
> shutdown, which I waited for with my script running, accessing the
> Internet, because I wanted to test such a case. Script "gracefully"
> worked as programmed to do, but that other error started right after
> the connection was cut off.
>
> I have no idea how could those two things be related! Why would that
> happen? Any suggestions, please?

I don't know if it's related...

I seem to recall the GNUlib folks talking about a cp bug on sparse
files. It looks like it may be fixed in coreutils release 9.2
(2023-03-20): https://github.com/coreutils/coreutils/blob/master/NEWS#L233

If I recall correctly, it had something to do with the way
copy_file_range worked. (Or maybe, it did not work as expected).

Jeff

Re: How to download source package using only console?

[Vincent Lefevre]

On 2023-05-14 14:17:05 +0500, Alexander V. Makartsev wrote:
> On 14.05.2023 10:06, Vincent Lefevre wrote:
> > On 2023-05-14 00:15:39 +0500, Alexander V. Makartsev wrote:
> > > Hello, fellow Debian users.
> > > 
> > > When I need to build a backport of a package, I sometimes find it 
> > > difficult
> > > to obtain actual source package(-s) from Debian repos using console.
> > > Following advice from a wiki page [1], after "apt update", doesn't do it:
> > > 
> > > $ apt source lego/testing
> > > Reading package lists... Done
> > > Picking 'golang-github-xenolf-lego' as source package instead of 
> > > 'lego'
> > > E: Can not find version '3.2.0-3.1' of package 'lego'
> > > E: Unable to find a source package for golang-github-xenolf-lego
> > zira:~> apt-show-versions -a lego
> > lego:amd64 3.2.0-3.1+b5 stableftp.debian.org
> > No stable-updates version
> > lego:amd64 4.9.1-1  testingftp.debian.org
> > lego:amd64 4.9.1-1  unstableftp.debian.org
> > No experimental version
> > lego:amd64 not installed
> > 
> > Indeed, 3.2.0-3.1 is no longer the testing version. Your database
> > seems to be out-of-date.
> > 
> I think you haven't noticed that I requested for "4.9.1-1" version from
> "testing" specifically,

You can't. You can either request some given version, e.g. 4.9.1-1
(but this will work only if it can be found from your local database),
or the version from some given distribution, e.g. "testing".

But my point is that your database is obsolete, because if you ask
the version from testing, apt thinks that it is 3.2.0-3.1, while it
should be 4.9.1-1. You need to fix that.

> hence why the command was "$ apt source lego/testing" not just "$ apt source
> lego".
> There is no reason for building a backport package for "stable" using a
> source package from "stable"...
> 
> I've changed all my repo mirrors to "deb.debian.org" suspecting the previous
> mirror I used was somehow out-of-date. Why is my output differ from yours?
> 
>$ apt-show-versions -a lego
>lego:amd64 3.2.0-3.1+b5 bullseye deb.debian.org
>No proposed-updates version
>No stable-updates version
>No testing version
>No unstable version
>lego:amd64 not installed
>lego:i386 3.2.0-3.1+b5 bullseye deb.debian.org
>No proposed-updates version
>No stable-updates version
>No testing version
>No unstable version
>lego:i386 not installed

After changing your sources.list, you need an "apt update" again.

> Yet "rmadison" reports there is a version "4.9.1-1" available in "testing":
> 
>$ rmadison lego
>lego   | 0.3.1-5+b13   | oldstable  | amd64, arm64, armel,
>armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
>lego   | 3.2.0-3.1+b5  | stable | amd64, arm64, armel,
>armhf, i386, mips64el, mipsel, ppc64el, s390x
>lego   | 4.9.1-1   | testing    | amd64, arm64, armel,
>armhf, i386, mips64el, mipsel, ppc64el, s390x
>lego   | 4.9.1-1   | unstable   | amd64, arm64, armel,
>armhf, i386, mips64el, mipsel, ppc64el, s390x
> 
> I suspect "apt-show-versions" output is inconsistent because I only request
> "deb-src" from "testing" in "sources.list", as I've shown before.

Probably. "apt-show-versions" considers only the binary packages
(but "lego" is only a binary package).

[...]
> I did some additional research and I think I got it.
> "lego" package is special because its source package is named differently:

Yes, as said by apt above:

  Picking 'golang-github-xenolf-lego' as source package instead of 'lego'

[...]
> But why "apt" doesn't play along, since it knows the source package for
> "lego" has different name, but ignores the "testing" part of the request?
> 
>$ apt source lego/testing
>Reading package lists... Done
>Picking 'golang-github-xenolf-lego' as source package instead of 'lego'
>E: Can not find version '3.2.0-3.1' of package 'lego'
>E: Unable to find a source package for golang-github-xenolf-lego
> 
> Looks like an "apt" bug to me.

Probably not. You are doing a request on a binary package (since
"lego" is not a source package). The translation from the binary
package to the source package depends on the particular version of
the binary package. So lego/testing will correspond to the binary
package from testing, which is 3.2.0-3.1+b5 in your case (because
of your obsolete database due to the missing "deb" for testing in
sources.list). Then apt translates this to the source package (of
the same version) golang-github-xenolf-lego 3.2.0-3.1, which is
unknown on your machine because the deb-src database is up-to-date
(contrary to the deb database). Something like that.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

No space left on device ...

[Albretch Mueller]

I have been mounting an NTFS file system on a Windows laptop without
any problems whatsoever with a Debian Live DVD:

$ uname -a
Linux debian 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02)
x86_64 GNU/Linux

and even though Linux utilities are telling me I do have space on the drive:

$ date; sudo df -h | grep "Filesystem\|/dev/sd"
Sun 14 May 2023 06:55:23 PM UTC
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda1   286G  167G  120G  59% /media/user/60320G593EB7250F
$

$ date; time sudo du --summarize --human-readable  /media/user/60320G593EB7250F
Sun 14 May 2023 07:13:43 PM UTC
166G/media/user/60320G593EB7250F

real0m45.230s
user0m1.073s
sys 0m15.443s
$

when I try to save or download a file I consistently get the same error message:

$ cp "No space left on device" > No_space_left_on_device.txt
bash: No_space_left_on_device.txt: No space left on device

that started happening right after a WiFi connection at a library was
shutdown, which I waited for with my script running, accessing the
Internet, because I wanted to test such a case. Script "gracefully"
worked as programmed to do, but that other error started right after
the connection was cut off.

I have no idea how could those two things be related! Why would that
happen? Any suggestions, please?

lbrtchx

Re: CUPS on Bullseye and Bookworm

[Brian]

On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:

> On Sun, 14 May 2023 19:48:07 +0200
> john doe  wrote:
> 
> > On 5/14/23 19:29, Charles Curley wrote:
> >  [...]  
> > 
> > The below, is what I would try:
> > 
> > - On the non-working client, Are you restricting outbound traffic at
> > all
> 
> Not that I know of.
> 
> > or for testing  purposes can you disable the FW?
> 
> I shut the firewall down ("systemctl stop firewalld"), ran test pages.
> Same non-results, except that system-control-printer now reports:
> 
> Idle - Print job canceled at printer.
> 
> 
> I tried increasing the logging, which involved stopping and restarting
> the cups service. In the process of doing that, the client and server
> both managed to forget the printer. I re-installed it. On the server, I
> have one instance of the printer, protocol:
> 
> hp:/usb/HP_LaserJet_MFP_M232-M237?serial=VNB4J02590
> 
> On the non-working client, cups discovered two versions of the printer:
> 
> dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345
> 
> ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
> 
> I have been testing both and getting the same results.
> 
> > 
> > - How are the working clients connected to the printer (protocol
> > wise)?
> 
> implicitclass://HP_LaserJet_MFP_M234sdw_C0FB67_/
> 
> 
> > - Is the non-working client using that same protocol?
> 
> Clearly not.
> 
> So I had the working client discover the printer again. It offered the
> same two as I have on the non-working client. Both printed test pages.
> 
> ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/
> 
> dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345
> 
> 
> > - If you do not use MDNS and point manually to the server, does it
> > work any better?
> 
> 
> 
> I tried setting up a printer manually on the non-working client.
> 
> ipp://hawk.localdomain/printers/HP_LaserJet_MFP_M232-M237
> 
> No test page, and I got:
> 
> Processing - The printer may not exist or is unavailable at this time.
> 
> However, I checked the CUPS on-line documentation, and did not find any
> documentation on how to set up a URI, so it's possible I did that
> incorrectly.
> 
> I also enabled "port 9100" printing on the printer, and went directly to
> it:
> 
> socket://hpm234ethernet.localdomain:9100
> 
> The printer spun its wheels, reported an error and stopped without
> printing. Nothing in the event log.

We take it that dragon, hawk and the printer are network connected.

Give what you get from dragon with

  avahi-browse -rt _ipp._tcp
  avahi-browse -rt _uscan._tcp
  driverless
  lpstat -l -e

avahi-browse is in the avahi-utils package.

-- 
Brian.

Re: Gene's avahi bogeyman is not real (Was Re: how to find outregdomain/country of wifi network)

[gene heskett]

On 5/14/23 17:21, Andy Smith wrote:

Dear debian-user archives,

On Sun, May 14, 2023 at 02:42:05PM -0400, gene heskett wrote:

I've literally spent a frigging week trying to get iproute to
over-ride the broken 169.xx.xx.xx primary route that earlier
avahi's insisted on putting into a network config, that is why to
this day the first thing I do after an install, is find avahi and
rm it and reboot. rm because you could not remove it with apt w/o
tearing down the system far enough the only recourse was to
reinstall.  That is obviously an endless loop.


Routine note for the archive that avahi is another one of Gene's
Demons and the above is not in any way true. I have 50+ Debian hosts
that do not have avahi installed at all, and several more that
intentionally do and work fine.

As usual, Gene's experiences are due to a misconfiguration that
Gene made and cannot be helped with, despite many people trying over
a period of years.

When you see a post from Gene mentioning liberal use of "rm" and
"chattr +i" on parts of the operating system, do begin to question
what you are reading.

Thanks,
Andy


Thanks for the vote of no confidence Andy.

The diff as I see it, is that I refuse to actually run a dns server 
here, bind and I agreed to disagree nearly 25 years ago when bind was at 
4 something and half the planet was cleaning after attacks on bind. The 
other half wasn't aware of anything except the net was dead, no dns.


The box in question was running rh 6.1 so that might give you a time 
frame. 2001 maybe. IDK, IDC.


We bought a block of 16 ipv4 addresses and registered & ran the tv 
stations net access, about 40 mostly windoze boxes preferring /etc/host 
files for local lookups. It works if the router relays, its fast, and 
bulletproof. The way I've configured is to first check the hosts file 
for a match, and failing that, fwd the lookup request to my dd-wrt 
router, and if dnsmasq doesn't know it, forward it to my ISP. And its 
all transparent in about 30 milliseconds.  The reason I used rm on it is 
because back about wheezy I tried to remove it with apt, and its 
dependencies took 247 other packages with it totally killing the system.


I screamed about it at the time, years ago, everybody sneered and made 
fun of me, and ever so slowly the dependencies went away and I can now 
remove it with apt, but it appears I no longer need to. So it has been 
reinstalled.


Take care & stay well Andy.

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 the law respectable.
 - Louis D. Brandeis
Genes Web page 

Gene's avahi bogeyman is not real (Was Re: how to find out regdomain/country of wifi network)

[Andy Smith]

Dear debian-user archives,

On Sun, May 14, 2023 at 02:42:05PM -0400, gene heskett wrote:
> I've literally spent a frigging week trying to get iproute to
> over-ride the broken 169.xx.xx.xx primary route that earlier
> avahi's insisted on putting into a network config, that is why to
> this day the first thing I do after an install, is find avahi and
> rm it and reboot. rm because you could not remove it with apt w/o
> tearing down the system far enough the only recourse was to
> reinstall.  That is obviously an endless loop.

Routine note for the archive that avahi is another one of Gene's
Demons and the above is not in any way true. I have 50+ Debian hosts
that do not have avahi installed at all, and several more that
intentionally do and work fine.

As usual, Gene's experiences are due to a misconfiguration that
Gene made and cannot be helped with, despite many people trying over
a period of years.

When you see a post from Gene mentioning liberal use of "rm" and
"chattr +i" on parts of the operating system, do begin to question
what you are reading.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: how to find out regdomain/country of wifi network

[Andy Smith]

Hello,

On Sun, May 14, 2023 at 08:08:06PM +0200, to...@tuxteam.de wrote:
> I think the problem here is that the user dreamt up a feature ifconfig
> has never had. At least not the linux ifconfig.

Yes, it seems their use of FreeBSD ifconfig led them to believe that
ifconfig would work the same on every platform.

So would you agree that had Debian NOT given in to the people who
demanded ifconfig remain packaged, OP would have been in a better
position as then they would have known that ifconfig is not the
command they need in Debian even if it is in FreeBSD?

(Making net-tools ifconfig behave the way FreeBSD ifconfig does is
presumably not an option on the table since clearly no one wants to
do that work, and anyway possibly there are yet some other platforms
that have an ifconfig that behaves differently again.)

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: how to find out regdomain/country of wifi network

[Andy Smith]

Hello,

On Sun, May 14, 2023 at 01:41:40PM -0400, gene heskett wrote:
> On 5/14/23 12:09, Andy Smith wrote:
> > the arguments for its continued usage are extremely tenuous and
> > basically boil down to, "it's always worked for me!" Which is
> > fine, but does lead to situations like this where we have a
> > whole thread of confusion about why it doesn't have some
> > particular feature that a user, who was not aware that ifconfig
> > is no longer the thing to use, continued to try to use it.
> > 
> That is all fine & dandy Andy, but how about replacing ifconfig with a bash
> script that recommends to the user, ip for hard wired stuff, iw for radio
> stuff. User education solved in one swell foop.  Makes perfect sense to me.

By all means contact the current maintainers of net-tools and say
something like

On behalf of experienced ifconfig users who also won't read
manuals or do the simplest of Internet searches, please will you
implement every command and feature of FreeBSD ifconfig but with
prompts that direct the user to the appropriate command in
Linux, for example if I type "ifconfig wlan0 list" then if wlan0
is a valid wifi interface I want it to respond with "The correct
tool for this on Linux is iw" instead of interpreting "list" as
a hostname like Linux ifconfig did before wifi was a thing.

I am guessing for an even split between:

- No I don't feel like that is a good use of my time, sorry

and

- I hate this suggestion and think experienced ifconfig users should
  be able to work things out for themselves

but I'm not one of those maintainers so what I think matters very
little, those are just my predictions. Sending your suggestions
anywhere else (such as debian-user) will do no good whatsoever.

Personally I think time is better spent doing a 5 second search and
moving on with life.

Every thread about ifconfig now is just people wishing that other
people would do some work to keep it alive, when it's so far dead
that even mentioning it is now a distraction for people coming into
this after the thing ceased being relevant. The OP's user experience
would have been clearly better had there been no ifconfig command
even present in Debian - they would have been forced to search for
the correct command and would have found it very easily.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: how to boot freebsd from bullseye?

[hl]

Thank didier gaumet! os-prober seems to be installed by default. it 
thinks my freebsd is unknown linux distro. if it's windows, i bet it can 
detect it correctly. freebsd is close cousin of linux they say, it is 
treated shabbily

Re: CUPS on Bullseye and Bookworm

[Charles Curley]

On Sun, 14 May 2023 19:48:07 +0200
john doe  wrote:

> On 5/14/23 19:29, Charles Curley wrote:
>  [...]  
> 
> The below, is what I would try:
> 
> - On the non-working client, Are you restricting outbound traffic at
> all

Not that I know of.

> or for testing  purposes can you disable the FW?

I shut the firewall down ("systemctl stop firewalld"), ran test pages.
Same non-results, except that system-control-printer now reports:

Idle - Print job canceled at printer.


I tried increasing the logging, which involved stopping and restarting
the cups service. In the process of doing that, the client and server
both managed to forget the printer. I re-installed it. On the server, I
have one instance of the printer, protocol:

hp:/usb/HP_LaserJet_MFP_M232-M237?serial=VNB4J02590

On the non-working client, cups discovered two versions of the printer:

dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345

ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/

I have been testing both and getting the same results.

> 
> - How are the working clients connected to the printer (protocol
> wise)?

implicitclass://HP_LaserJet_MFP_M234sdw_C0FB67_/


> - Is the non-working client using that same protocol?

Clearly not.

So I had the working client discover the printer again. It offered the
same two as I have on the non-working client. Both printed test pages.

ipps://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipps._tcp.local/

dnssd://HP%20LaserJet%20MFP%20M234sdw%20(C0FB67)._ipp._tcp.local/?uuid=d532fa73-f559-43ca-9f8e-1eef16972345


> - If you do not use MDNS and point manually to the server, does it
> work any better?



I tried setting up a printer manually on the non-working client.

ipp://hawk.localdomain/printers/HP_LaserJet_MFP_M232-M237

No test page, and I got:

Processing - The printer may not exist or is unavailable at this time.

However, I checked the CUPS on-line documentation, and did not find any
documentation on how to set up a URI, so it's possible I did that
incorrectly.

I also enabled "port 9100" printing on the printer, and went directly to
it:

socket://hpm234ethernet.localdomain:9100

The printer spun its wheels, reported an error and stopped without
printing. Nothing in the event log.


> 
> --
> John Doe
> 



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: how to find out regdomain/country of wifi network

[Jeffrey Walton]

On Sat, May 13, 2023 at 5:35 AM hl  wrote:
>
> freebsd ask me regdomain/country of wifi when i set up wifi
>
> my wifi works in buster, how to find out regdomain/country it uses?
>
> https://wiki.freebsd.org/action/show/WiFi/RegulatoryDomainSupport?action=show&redirect=WiFiRegulatory
>
> To view the current list of regulatory domains and SKUs:
>
>  # ifconfig wlan0 list countries
>
> To view the current regulatory domain frequency and operating modes:
>
>  # ifconfig wlan0 list regdomain
>
> but ifconfig isn't available in buster

Boy, this thread reached critical mass and melted down quickly...

Is this going to be another thread that never dies :)

Re: how to find out regdomain/country of wifi network

[David Wright]

On Sun 14 May 2023 at 16:27:31 (-), Curt wrote:
>  Hence, our plans are to replace net-tools completely with iproute, maybe
>  leading the route for other distributions to follow. Of course, most people 
> and
>  tools use and remember the venerable old interface, so the first step would 
> be
>  to write wrappers, trying to be compatible with net-tools.
> 
>  At the same time, we believe that most packages using net-tools should be
>  patched to use iproute instead, while others can continue using the wrappers
>  for some time. The ifupdown package is obviously the first candidate, but it
>  seems that a version using iproute has been available in experimental since
>  2007.

On Sun 14 May 2023 at 20:11:28 (+0200), to...@tuxteam.de wrote:
> Thanks for the interesting data point. History seems to have unfolded
> differently from plan (happens all the time :) but it wouldn't be too
> late to fix.
> 
> Who is writing the wrappers?

In 2023?

 "Debian, as it happens, is having this discussion a bit late.
  OpenSUSE discussed removing net-tools in 2009, but has not
  done so. Red Hat and Fedora got serious in 2011, and the
  RHEL 7 release no longer installs net-tools by default.
  The fact that this change is not universally popular shows
  how reluctant users can be to let go of their long-used tools."

AIUI people thought patching software that used net-tools was more
productive than writing and supporting wrappers.

 "Distributors have to choose where to expend their energy,
  and there will come a point where dragging along obsoleted
  tools that the old folks want falls off the list."

Final thought from this (lwn) source:

 "Software transitions like this are invariably an unwanted
  distraction for users who are uninterested in whatever new
  features are available and would prefer that their systems
  (and their habits) just continue to work. But the world we
  live in does not stand still, so such transitions are simply
  going to happen, and distributors will find themselves caught
  in the middle. As those distributors strive to keep everybody
  happy, we should not be surprised to see more of these
  transitions take a decade or more."

Cheers,
David.

Re: how to find out regdomain/country of wifi network

[gene heskett]

On 5/14/23 12:28, Curt wrote:

On 2023-05-14,   wrote:


So Redhat. But hey, look at packages.debian.org (I know, looking at


https://wiki.debian.org/NetToolsDeprecation

https://lists.debian.org/debian-devel/2009/03/msg00780.html

2009!!

  Luk Claes and me, as the current maintainers of net-tools, we've been
  thinking about it's future. Net-tools has been a core part of Debian and any
  other linux based distro for many years, but it's showing its age.

  It doesnt support many of the modern features of the linux kernel, the
  interface is far from optimal and difficult to use in automatisation, and 
also,
  it hasn't got much love in the last years.

  On the other side, the iproute suite, introduced around the 2.2 kernel
  line, has both a much better and consistent interface, is more powerful, and 
is
  almost ten years old, so nobody would say it's untested.

  Hence, our plans are to replace net-tools completely with iproute, maybe
  leading the route for other distributions to follow. Of course, most people 
and
  tools use and remember the venerable old interface, so the first step would be
  to write wrappers, trying to be compatible with net-tools.

  At the same time, we believe that most packages using net-tools should be
  patched to use iproute instead, while others can continue using the wrappers
  for some time. The ifupdown package is obviously the first candidate, but it
  seems that a version using iproute has been available in experimental since
  2007.

All are good ideas, Curt, but the power in iproute is, maybe now s/b was 
lacking, I've literally spent a frigging week trying to get iproute to 
over-ride the broken 169.xx.xx.xx primary route that earlier avahi's 
insisted on putting into a network config, that is why to this day the 
first thing I do after an install, is find avahi and rm it and reboot. 
rm because you could not remove it with apt w/o tearing down the system 
far enough the only recourse was to reinstall.  That is obviously an 
endless loop.


I find that in bullseye, finally, avahi has developed some manners in 
that it is now happy to the the 2nd route. Ditto for NM, it finally 
after a decade of insisting it be done its way even when its way didn't 
work, so that stuff got fixed and immediately a "sudo chattr +i" applied 
so NM could not screw it up. Fortunately, NM had the good graces not to 
flood the logs with "I can't screw it up" complaints.


So while we are making progress in just works networking and its not 
nice to dig up old dirt, but why did it take 10 years to get those 
major, show stopping problems fixed?  That's what I have failed to 
understand. I've been networking stuff since the middle 80's, Went from 
os9 level 1 on an original coco,then level 2 on a coco3 to amigados, 
running exclusively linux since 1998, I've seen kernel bugs get fixed in 
an hour so why did it take a decade to fix that show stopper routing 
problem? I think that is a legitimate question.




.


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 the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: how to find out regdomain/country of wifi network

[tomas]

On Sun, May 14, 2023 at 04:27:31PM -, Curt wrote:
> On 2023-05-14,   wrote:
> >
> > So Redhat. But hey, look at packages.debian.org (I know, looking at
> 
> https://wiki.debian.org/NetToolsDeprecation
> 
> https://lists.debian.org/debian-devel/2009/03/msg00780.html
> 
> 2009!!
> 
>  Luk Claes and me, as the current maintainers of net-tools, we've been
>  thinking about it's future. Net-tools has been a core part of Debian and any
>  other linux based distro for many years, but it's showing its age.

Thanks for the interesting data point. History seems to have unfolded
differently from plan (happens all the time :) but it wouldn't be too
late to fix.

Who is writing the wrappers?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: how to find out regdomain/country of wifi network

[tomas]

On Sun, May 14, 2023 at 04:08:55PM +, Andy Smith wrote:
> Hello,
> 
> On Sun, May 14, 2023 at 06:48:59AM +0200, to...@tuxteam.de wrote:
> > So no, it doesn't look dead to me.
> 
> It (Linux ifconfig) exists and is still installable but will not be
> getting any new features. It also displays incorrect information for
> some features it does not understand.
> 
> So the arguments for its continued usage are extremely tenuous and
> basically boil down to, "it's always worked for me!" Which is fine,
> but does lead to situations like this where we have a whole thread
> of confusion about why it doesn't have some particular feature that
> a user, who was not aware that ifconfig is no longer the thing to
> use, continued to try to use it.

I think the problem here is that the user dreamt up a feature ifconfig
has never had. At least not the linux ifconfig.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: CUPS on Bullseye and Bookworm

[john doe]

On 5/14/23 19:29, Charles Curley wrote:

I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
"no driver" multifunction printers. It works fine on Bullseye. I have
the printer hooked up via USB to a server, hawk, and it prints just
fine.

I have a client, ideapc, which sees the printer and prints to it just
fine.

I also have an ancient i386 IBM R51 running Bookworm, dragon. On dragon,
using system-config-printer, I can see the printer automagically
discovered. I can open up the queue window for the printer, and request
a test page.

Alas, I see the test page in the queue briefly. The queue window says
"processing - not connected?", then "Printer error". Then the print job
disappears, leaving no error message. (This is a change in behavior from
Bullseye. I do not like it.)

The printer does come awake and report an error when I ask for the test
page. I don't see anything in the printer's logs.

Logging on both machines shows no errors. I am running firewalld on
dragon, and did enable logging for unicast. firewalld-cmd reports the
following, among other things:

services: ipp ipp-client mdns samba-client smtp ssh



The below, is what I would try:

- On the non-working client, Are you restricting outbound traffic at all
or for testing  purposes can you disable the FW?

- How are the working clients connected to the printer (protocol wise)?
- Is the non-working client using that same protocol?
- If you do not use MDNS and point manually to the server, does it work
any better?

--
John Doe

Re: how to find out regdomain/country of wifi network

[gene heskett]

On 5/14/23 12:09, Andy Smith wrote:

Hello,

On Sun, May 14, 2023 at 06:48:59AM +0200, to...@tuxteam.de wrote:

So no, it doesn't look dead to me.


It (Linux ifconfig) exists and is still installable but will not be
getting any new features. It also displays incorrect information for
some features it does not understand.

So the arguments for its continued usage are extremely tenuous and
basically boil down to, "it's always worked for me!" Which is fine,
but does lead to situations like this where we have a whole thread
of confusion about why it doesn't have some particular feature that
a user, who was not aware that ifconfig is no longer the thing to
use, continued to try to use it.

Cheers,
Andy

That is all fine & dandy Andy, but how about replacing ifconfig with a 
bash script that recommends to the user, ip for hard wired stuff, iw for 
radio stuff. User education solved in one swell foop.  Makes perfect 
sense to me.


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 the law respectable.
 - Louis D. Brandeis
Genes Web page 

CUPS on Bullseye and Bookworm

[Charles Curley]

I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
"no driver" multifunction printers. It works fine on Bullseye. I have
the printer hooked up via USB to a server, hawk, and it prints just
fine.

I have a client, ideapc, which sees the printer and prints to it just
fine.

I also have an ancient i386 IBM R51 running Bookworm, dragon. On dragon,
using system-config-printer, I can see the printer automagically
discovered. I can open up the queue window for the printer, and request
a test page.

Alas, I see the test page in the queue briefly. The queue window says
"processing - not connected?", then "Printer error". Then the print job
disappears, leaving no error message. (This is a change in behavior from
Bullseye. I do not like it.)

The printer does come awake and report an error when I ask for the test
page. I don't see anything in the printer's logs.

Logging on both machines shows no errors. I am running firewalld on
dragon, and did enable logging for unicast. firewalld-cmd reports the
following, among other things:

   services: ipp ipp-client mdns samba-client smtp ssh

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: shell script run in backend

[Greg Wooledge]

On Sun, May 14, 2023 at 04:36:03PM +, Andy Smith wrote:
> On Sun, May 14, 2023 at 05:04:50PM +0800, Tom Reed wrote:
> > I know convert it to a perl script and run it under App::Daemon for
> > background jobs.
> 
> Having it as a systemd service is a much cleaner solution, whether
> it is shell or Perl or any other language.
> 
> The main point of the App::Daemon module is to detach from shell,
> redirect stdout etc and provide start/stop/status commands, all of
> which are provided by systemd.
> 
> I suppose if aiming for it to be portable to other init systems it
> could still be useful, but even so if on a machine with systemd I'd
> run it as a systemd service and tell App::Daemon to run it
> foreground (so that systemd takes care of backgrounding it).

Or, simply don't use App::Daemon at all.  Just let your program work
in a normal way -- as a single process, with no funky gymnastics.
That's the easiest thing to handle.  It's the correct way.

Re: iptables reject with TCP RST

[Andy Smith]

Hi,

On Sun, May 14, 2023 at 08:14:04AM +0800, Tom Reed wrote:
> I have these iptables rules which reject tcp connections with tcp rst.

First question, why are you using iptables instead of nft? On a new
Debian install you actually are using nftables with an iptables
compat layer, but a new install is a good opportunity to directly
use the "nft" tool.

iptables is still supported and will be for years to come, so "I
don't have time to learn a new thing" is a perfectly reasonable
answer, but:

https://wiki.debian.org/nftables
"nftables is the default and recommended firewalling framework
in Debian, and it replaces the old iptables (and related) tools."

> /usr/sbin/iptables -A INPUT -p tcp --dport 143 -j REJECT --reject-with
> tcp-reset
> /usr/sbin/iptables -A INPUT -p tcp --dport 587 -j REJECT --reject-with
> tcp-reset

Possibly this is implicit in the above command but I am used to also
having to specify "-m tcp" first,. i.e.

# iptables -A INPUT -m tcp -p tcp --dport 143 -j REJECT --reject-with tcp-reset

> When I telnet from another host to the protected port, it gets timeout
> message as follows.
> 
> telnet: Unable to connect to remote host: Connection timed out

Have you verified by looking at the packet counters, that apckets
are actually hitting your rule?

# iptables -vnL INPUT

If you don't see incrementing numbers for packets and bytes next
to your above rules, packets aren't hitting them and are instead
being dropped somewhere in the middle.

Have you verified with tcptraceroute that you can reach all the way
from your client host to your machine with iptables on port 143?

e.g. I used 193.106.250.1 since you obscured the IP (which only
makes our task of helping you harder) but this seems to be blocked
one hop after 213.200.112.170:

$ sudo tcptraceroute 193.106.250.1 587
[sudo] password for andy:
Selected device eth0, address 85.119.80.223, port 48267 for outgoing packets
Tracing the path to 193.106.250.1 on TCP port 587 (submission), 30 hops max
 1  limoncello.bitfolk.com (85.119.80.29)  0.157 ms  0.143 ms  0.440 ms
 2  e3b.bitfolk.com (185.168.136.3)  1.669 ms  1.828 ms  1.542 ms
 3  c5.jump.net.uk (194.153.169.140)  1.729 ms  1.625 ms  1.674 ms
 4  t5.jump.net.uk (194.153.169.232)  0.535 ms  0.539 ms  0.393 ms
 5  as2914.jump.net.uk (194.153.169.185)  0.827 ms  4.001 ms  7.779 ms
 6  ae-14.r20.londen12.uk.bb.gin.ntt.net (129.250.3.248)  1.279 ms  0.859 ms  
1.171 ms
 7  ae-1.r04.londen05.uk.bb.gin.ntt.net (129.250.4.141)  1.056 ms  1.012 ms  
1.240 ms
 8  ae15.cr11-lon2.ip4.gtt.net (77.67.98.53)  19.353 ms  1.425 ms  0.628 ms
 9  ae1.cr2-nyc4.ip4.gtt.net (213.200.112.170)  70.567 ms  69.967 ms  70.946 ms
10  * * *
11  * * *
12  *^C

compare to mtr (which partially uses simple ping):

$ mtr -bzwrc10 193.106.250.1
Start: 2023-05-14T16:52:01+
HOST: use   Loss%   Snt 
  Last   Avg  Best  Wrst StDev
  1. AS8943   limoncello.bitfolk.com (85.119.80.29)  0.0%10 
   0.3   0.3   0.1   1.0   0.2
  2. AS???e3b.bitfolk.com (185.168.136.3)0.0%10 
   2.2   1.8   1.6   2.2   0.2
  3. AS???c5.jump.net.uk (194.153.169.140)   0.0%10 
   2.0   3.6   1.6  17.9   5.0
  4. AS???t5.jump.net.uk (194.153.169.232)   0.0%10 
   0.5   1.1   0.4   4.5   1.3
  5. AS???as2914.jump.net.uk (194.153.169.185)   0.0%10 
   0.6   3.1   0.6   8.5   2.8
  6. AS2914   ae-14.r20.londen12.uk.bb.gin.ntt.net (129.250.3.248)   0.0%10 
   1.1   1.6   0.6   4.5   1.4
  7. AS2914   ae-1.r04.londen05.uk.bb.gin.ntt.net (129.250.4.141)0.0%10 
   1.2   1.2   1.0   1.7   0.2
  8. AS3257   ae15.cr11-lon2.ip4.gtt.net (77.67.98.53)  20.0%10 
   0.7   4.2   0.6  19.4   6.9
  9. AS3257   ae1.cr2-nyc4.ip4.gtt.net (213.200.112.170) 0.0%10 
  84.2  88.3  70.5 102.1   8.6
 10. AS63023  193.106.250.1  0.0%10 
  73.1  74.7  72.9  81.1   3.0

so whatever your 193.106.250.x host is, maybe it did indeed block
the packets itself, but would be good to verify.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: shell script run in backend

[Andy Smith]

Hello,

On Sun, May 14, 2023 at 05:04:50PM +0800, Tom Reed wrote:
> I know convert it to a perl script and run it under App::Daemon for
> background jobs.

Having it as a systemd service is a much cleaner solution, whether
it is shell or Perl or any other language.

The main point of the App::Daemon module is to detach from shell,
redirect stdout etc and provide start/stop/status commands, all of
which are provided by systemd.

I suppose if aiming for it to be portable to other init systems it
could still be useful, but even so if on a machine with systemd I'd
run it as a systemd service and tell App::Daemon to run it
foreground (so that systemd takes care of backgrounding it).

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: how to find out regdomain/country of wifi network

[Curt]

On 2023-05-14,   wrote:
>
> So Redhat. But hey, look at packages.debian.org (I know, looking at

https://wiki.debian.org/NetToolsDeprecation

https://lists.debian.org/debian-devel/2009/03/msg00780.html

2009!!

 Luk Claes and me, as the current maintainers of net-tools, we've been
 thinking about it's future. Net-tools has been a core part of Debian and any
 other linux based distro for many years, but it's showing its age.

 It doesnt support many of the modern features of the linux kernel, the
 interface is far from optimal and difficult to use in automatisation, and also,
 it hasn't got much love in the last years.

 On the other side, the iproute suite, introduced around the 2.2 kernel
 line, has both a much better and consistent interface, is more powerful, and is
 almost ten years old, so nobody would say it's untested.

 Hence, our plans are to replace net-tools completely with iproute, maybe
 leading the route for other distributions to follow. Of course, most people and
 tools use and remember the venerable old interface, so the first step would be
 to write wrappers, trying to be compatible with net-tools.

 At the same time, we believe that most packages using net-tools should be
 patched to use iproute instead, while others can continue using the wrappers
 for some time. The ifupdown package is obviously the first candidate, but it
 seems that a version using iproute has been available in experimental since
 2007.

Re: how to find out regdomain/country of wifi network

[Andy Smith]

Hello,

On Sat, May 13, 2023 at 06:18:57PM -0400, gene heskett wrote:
> On 5/13/23 15:40, Greg Wooledge wrote:
> > :
> >  The ip command is the future of network config commands. ifconfig
> >  has been officially deprecated for the ip suite, so while many of
> >  us are still using the old ways, it is time to put those habits to
> >  rest and move on with the world.
> 
> While you are correct, Greg, the lack of documentation to help with that
> transition is staggering. They just thru it on the table and didn't even say
> use this instead.

This is not true. The first hit on most web searches for "linux wifi
regulatory domain" will be the "iw" command.

Both you and the OP have been sidetracked (blinded?) by assumptions
that iufconfig is and will always be the command to use, and then
gave up without doing any further research,

Elsewhere in this thread copious links to documentation from Red Hat
and Arch were posted, to which the old guard say, "don't believe
everything you read on the web".

Live in the 20th century if you want, but don't tell me the
information isn't out there.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: how to find out regdomain/country of wifi network

[Andy Smith]

Hello,

On Sun, May 14, 2023 at 06:48:59AM +0200, to...@tuxteam.de wrote:
> So no, it doesn't look dead to me.

It (Linux ifconfig) exists and is still installable but will not be
getting any new features. It also displays incorrect information for
some features it does not understand.

So the arguments for its continued usage are extremely tenuous and
basically boil down to, "it's always worked for me!" Which is fine,
but does lead to situations like this where we have a whole thread
of confusion about why it doesn't have some particular feature that
a user, who was not aware that ifconfig is no longer the thing to
use, continued to try to use it.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: iptables reject with TCP RST

[Tim Woodall]

tcptraceroute might give you more clues as to where it's going wrong. In
particular I'd look at local egress rules not allowing connections to
port 587 outside of the lan.

On Sun, 14 May 2023, Tom Reed wrote:


On Sun, May 14, 2023 at 08:36:38AM +0800, Tom Reed wrote:

tcp0  0 0.0.0.0:587 0.0.0.0:*
LISTEN
 32157/master


And the telnet results:

$ telnet 193.106.250.xx 587
Trying 193.106.250.xx...
telnet: Unable to connect to remote host: Connection timed out


So, it looks like it's not a LAN address.  It's a mail server on the
public Internet?  As in, your telnet client and your server are NOT
talking directly to each other over a straight ethernet connection?
There's routers and stuff in between them?


Yes. my mailserver is in NYC DC, and the client host is in Dallas DC.




You'd need to investigate the possibility of a firewall-equivalent at
each hop along the way.



I may need tcpdump for watching the rst packages.

Thank you
Tom

Re: how to find out regdomain/country of wifi network

[David Wright]

On Sun 14 May 2023 at 07:10:02 (+0200), Vincent Lefevre wrote:
> On 2023-05-13 18:41:12 +0800, hl wrote:
> > On 5/13/23 18:01, Vincent Lefevre wrote:
> > > On 2023-05-13 17:19:01 +0800, hl wrote:
> > > > but ifconfig isn't available in buster
> > > I've used it for many years, and it is still there, currently in
> > > the net-tools package (try "apt-file search bin/ifconfig").
> > > 
> > Thank Vincent! i install net-tools, but it doesn't work as i have hoped
> > 
> > root@debian:~# /sbin/ifconfig  wlx12345 list regdomain
> > list: Unknown host
> > ifconfig: `--help' gives usage information.
> > root@debian:~#
> 
> Indeed, "ifconfig --help" doesn't mention a "list" feature.
> ifconfig accepts some other keywords, otherwise an address
> (possibly specified as a hostname), hence the "Unknown host"
> error.

The OP is on freebsd. It seems every linux/unix has its own
version of ifconfig, all different.

Cheers,
David.

Re: how to find out regdomain/country of wifi network

[David Wright]

On Sun 14 May 2023 at 06:54:25 (+0200), to...@tuxteam.de wrote:
> On Sat, May 13, 2023 at 11:00:23PM -0500, David Wright wrote:
> 
> [...]
> 
> >   5.1.3. Noteworthy obsolete packages
> > 
> >   The following is a list of known and noteworthy obsolete packages
> >   (see Section 4.8, “Obsolete packages” for a description).
> 
> [...]
> 
> Now this one has more substance. It seems to me, though, that
> upstream found maintainers and someone in Debian cares enough
> to keep the package alive -- so it went from deprecated to
> just non-default.

In 2009, the path ahead was outlined in:

  https://lists.debian.org/debian-devel/2009/03/msg00780.html

but I don't think some of the options (like wrappers) are under
consideration after more than a decade of parallel working with ip.

This opinion raised a chuckle in the lwn article:

 "But I'm not seeing any real advantage here. Sure,
  ifconfig doesn't support all the new networking features,
  but basic "ifconfig blah0 up" still works just fine.

Cheers,
David.

Re: Stable and testing together?

[David Wright]

On Sun 14 May 2023 at 09:08:00 (+0200), Hans wrote:

> As we are only one month away from releasing the actual testing (which is in 
> freeze state) to stable, I could upgrade now, if I want to. I tried a 
> dry-run, 
> and saw i.e. digikam to get being uninstalled and some others.
> 
> Also it tries to uninstall my NVidia package, which is worse, as it is 
> running 
> and I have to avoid this, because it will break my system. As it is a 
> notebook 
> I cannot change the graphics card. And no, nouveau is NOT an option!
> 
> Worse: I never will get it back, as once deinstalled, I will no more be able 
> to build it again, as also the needed compiler and header files are gone in 
> testing. Yeah, hard luck, ey?

That worry seems all the more reason to set up a second root partition
on which to install the new release and check that all your required
features are still present. Particularly true for a laptop, where you
can't just throw in another disk.

> As I said, no mourning, just telling, why I believe, deleting packages from 
> the repo is not the best idea. However, this is only my personally view and 
> maybe I am the only person in the world, who might be affected.

They don't delete packages from the repository. So you can continue
to run bullseye on one partition as long as you like, until you're
completely happy with your alternative.

Cheers,
David.

Re: How to download source package using only console?

[Greg Wooledge]

On Sun, May 14, 2023 at 02:17:05PM +0500, Alexander V. Makartsev wrote:
> hence why the command was "$ apt source lego/testing" not just "$ apt source
> lego".
> There is no reason for building a backport package for "stable" using a
> source package from "stable"...

If you're trying to build a backport, you add "deb-src" lines for
testing, then "apt-get update", and then simply use
"apt-get source pkgname".  Or their "apt" equivalents, I guess.

Re: Stable and testing together?

[Andrew M.A. Cater]

On Sun, May 14, 2023 at 09:08:00AM +0200, Hans wrote:
> Hi folks,
> 
> thanks for all the answers. Yes, I know, mixing both might be causing 
> troubles. But sometimes I got no choice. 
> 
> For example, the NVidie kernel driver can not be compiled on newer kernels 
> than 5.10.22. Reason is, that in the herader files of the newer kernel 
> package 
> some files are missing, which the compiler needs.
> 
> I filed a bugreport, but the devolper will not fix it, as they claim it an 
> NVidia-issue. That does of course not explain, why it on one kernel versions 
> builds and the next version not. However, I do not want to mourne about it, 
> just tell, what I mean.
> 

It *is* an Nvidia issue: the proprietary drivers are something we can't fix.
If Nvidia deprecate them, we do too. If they are full of security issues
that Nvidia will no longer fix, we can't help you in Debian

They are tightly coupled to particular kernel versions. "On one kernel versions
build and the next version not" - there are approximately 2 1/2 years worth
of kernel changes between Debian major releases: that is to be expected.

Likewise, nouveau has improved significantly in that 2 1/2 years and works more
successfully than it did.

> Then I saw, in testing the famous application "digikam" will be removed. So, 
> if one did use digikam for a long time, he will be surprised and maybe angry, 
> that suddenly digikam has gone.

https://packages.debian.org/bookworm/digikam suggests it's still there ...
> 
> These are only two examples, which can be trouble for users. You can of 
> course 
> say: "Hard luck!", but the only way to avoid this, is to mix stable and 
> testing. Or (in case of graphics driver), buy a new hardware.
> 

You can follow a release from testing -> stable -> oldstable -> oldoldstable.
That may or may not be desirable. It will keep you running older software.
As it gets older, you may find that packages get removed as unsupportable.

You always have a choice. 

> As we are only one month away from releasing the actual testing (which is in 
> freeze state) to stable, I could upgrade now, if I want to. I tried a 
> dry-run, 
> and saw i.e. digikam to get being uninstalled and some others.
> 

If you're currently running a mix of stable and testing - you're almost
certainly already running mostly testing unless you've pinned your kernel
and several other libraries, as others have said..

> Also it tries to uninstall my NVidia package, which is worse, as it is 
> running 
> and I have to avoid this, because it will break my system. As it is a 
> notebook 
> I cannot change the graphics card. And no, nouveau is NOT an option!
> 
> Worse: I never will get it back, as once deinstalled, I will no more be able 
> to build it again, as also the needed compiler and header files are gone in 
> testing. Yeah, hard luck, ey?
> 

You always have a choice: you can change your /etc/apt/sources.list to *only*
refernce bullseye and follow it down to oldoldstable or whatever.
You can remove any references to testing and attempt to downgrade what you
have. Downgrades are explicitly *not* supported in Debian - it's often far
more straightforward to do a full reinstall.

Without seeing your actual /etc/apt/sources.list I don't know what you 
currently have but this thread is a very good illustration of why we
use codenames to fix releases and how "stable" and "testing" are in general
a bad idea to use in sources lists. That has been deprecated for a couple
of releases now.

> As I said, no mourning, just telling, why I believe, deleting packages from 
> the repo is not the best idea. However, this is only my personally view and 
> maybe I am the only person in the world, who might be affected.
> 

In general: packages follow the suite they're in. So bullseye today will
still be bullseye on 12th June when bookworm is (hopefully) released.
All the packages there will still be the same: they will track with
that codebase. 

That means you don't get new packages / you don't get large package changes.
That's the definition of stability over a period of years.
So bullseye won't be deleted until it goes past oldoldstable - and even
then it will be available from the archives.


> Anyway, I understood all the dangers, and as I (believe) I know, what I am 
> doing, I hope upgrade to the next release will be without major problems.
> 
> Thunbs pressing!! 
> 
> Best regards
> 
> Hans 
> 
> 

Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[Will Mengarini]

* Schwibinger Michael  [23-05/14=Sun 09:32 +]:
> This is not working:
> https://tutorialforlinux.com/2021/03/06/step-by-step-driver-epson-et-m1100-et-m1120-ubuntu-20-04-installation/2/

We need to know what fails.  Exactly what do
you do, and what results does it produce?

On Sun, May 07, 2023 at 08:51:29AM -0400, Greg Wooledge wrote:
>> How on earth would we know whether the
>> messages are important without seeing them?
>
> [...]
>
> OK.  I'm going to have one more go at this. [...]

And once again, and wiser in no wise,
I chase your colored phantom on the air,
And sob and curse and fall and weep and rise
And stumble pitifully on to where,
Miserable and lost, with stinging eyes,
Once more I clasp -- and there is nothing there.
-- Edna St Vincent Millay

  /* return TRUE if the monster tends to revive */
  #define is_reviver(ptr) (is_rider(ptr) || (ptr)->mlet == S_TROLL)
-- https://nethackwiki.com/wiki/Source:NetHack_3.6.1/include/mondata.h

Re: how to boot freebsd from bullseye?

[didier gaumet]

Correction: there is no Debian i686 architecture: this is still called 
i386, even if CPUs before i686 are not supported anymore

AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[Schwibinger Michael]

Good morning.
Thank You.


I hope this email is more polite.


This is not working:
https://tutorialforlinux.com/2021/03/06/step-by-step-driver-epson-et-m1100-et-m1120-ubuntu-20-04-installation/2/

or:

https://www.club.computerwissen.de/qa/109588-epson-drucker-et-m1120-auf-linux
[https://www.club.computerwissen.de/components/com_easydiscuss/themes/wireframe/images/placeholder-facebook.png]
Epson Drucker ET-M1120 auf 
LINUX
Meine Epson Drucker ET-M1120 als auch Epson Stylus D120 lassen sich nicht auf 
Ubuntu-Linux installieren. Datei aus Email-Antwort der Firma EPSON Level One 
vom Dienstag,den 11.Jan. 2022 lässt sich nicht hochladen. [Antwort vom 
Kunden-support Linux-und Unix-Betriebssysteme werden von Epson nicht 
unterstützt] Erbitte von Herrn Kaner Etem Drucker-Inst...
www.club.computerwissen.de


Regards Sopjie




Von: chris 
Gesendet: Sonntag, 7. Mai 2023 21:45
An: Andrew M.A. Cater 
Cc: Debian User 
Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are using 
the wrong driver

True

On Sun, May 7, 2023, 4:28 PM Andrew M.A. Cater 
mailto:amaca...@einval.com>> wrote:
On Sun, May 07, 2023 at 08:51:29AM -0400, Greg Wooledge wrote:
> On Sun, May 07, 2023 at 09:26:33AM +, Schwibinger Michael wrote:
> > There are some other messages from the printer.
> >
> > Are they important?
>
> How on earth would we know whether the messages are important without
> seeing them?
>
> This is why nobody is offering you any more help.  You are presenting
> yourself as either a troll, or as someone who is so fundamentally
> incompetent that helping you is impossible.
>

OK. I'm going to have one more go at this. For the avoidance of doubt:
I'll assume that Sophie is genuine - maybe a teenager, certainly
someone whose first language is German.

I'm going to assume good faith, despite some evidence to the contrary.**

>From looking on Epson's website:

1. They do not support this printer under Linux officially.

2. The printer is listed as a printer supported only under Windows - lots
of variants.

3. It is listed as a GDI compatible printer - this is indicative of a printer
that requires a specific Windows driver to compose the page.

4. It is compatible with older Epson printing protocols called Esc/P and
Esc/P-R.

5. Epson do have a filter program available to make this printer work
as an Esc/P printer under Linux using CUPS to manage the printer.

6. If CUPS setup is possible - you will need to read documents to be
able to set up CUPS.

See: 
https://www.epson.co.uk/products/printers/inkjet/consumer/ecotank-et-m1120/p/23162

See: https://download.ebz.epson.net/man/linux/escpr.html

> Do you want my advice?  Go find a local Linux users group, and ask them
> what kind of printers they're using.  Then buy one of THOSE printers,
> and have the Linux users group help you set it up.
>

This is possibly not the best advice: I would suggest that you find a
fellow student who uses Linux and is an enthusiast to help you out.

** Michael Tobias Schwibinger (or similar spelling) appears to be a
Dipl. Ing, interested in software, psychology and clown therapy / circus
skills and clown theory?

In the hope that this can finally put an end to this neverending thread.

With every good wish, as ever,

Andy Cater

Re: how to boot freebsd from bullseye?

[didier gaumet]

You seem to be using i686 Debian architecture:
- if it is an educated choice and you do want want 32 bits only, that is 
perfectly fine
- if you have chosen i686 Debian architecture because you have an Intel 
CPU, please be aware that in Debian, i686 architecture is for 32 bits 
Intel or AMD CPUs, while amd64 architecture is the one to go for 64 bits 
CPUs, either Intel or AMD.

Re: how to boot freebsd from bullseye?

[didier gaumet]

There is a utility called os-prober that scans for other OSes than the 
one os-prober is running in. This utility is called by update-grub. but 
I think this has been modified from Debian 12 Bookworm on.


please verify if os-prober is installed:
$ dpkg -l os-prober

if it is not installed, install it:
$ sudo apt install os-prober

verify it is active:
$ grep GRUB_DISABLE_OS_PROBER /etc/default/grub

if the result of the previous command is not void, then edit (as root or 
privileged user) the /etc/default/grub file to comment out the line 
containing GRUB_DISABLE_OS_PROBER


plug your USB disk containing your FreeBSD install

then run update-grub (Debian script to launch grub-mkconfig) , it will 
call automatically os-prober


This should be sufficient. If your FreeBSD install does not appear in 
Grub menu, perhaps you will have to tinker a bit ("multiboot manual 
config" section of the grub doc here:)

https://www.gnu.org/software/grub/manual/grub/grub.html

Re: How to download source package using only console?

[Alexander V. Makartsev]

On 14.05.2023 10:06, Vincent Lefevre wrote:

On 2023-05-14 00:15:39 +0500, Alexander V. Makartsev wrote:

Hello, fellow Debian users.

When I need to build a backport of a package, I sometimes find it difficult
to obtain actual source package(-s) from Debian repos using console.
Following advice from a wiki page [1], after "apt update", doesn't do it:

$ apt source lego/testing
Reading package lists... Done
Picking 'golang-github-xenolf-lego' as source package instead of 'lego'
E: Can not find version '3.2.0-3.1' of package 'lego'
E: Unable to find a source package for golang-github-xenolf-lego

zira:~> apt-show-versions -a lego
lego:amd64 3.2.0-3.1+b5 stableftp.debian.org
No stable-updates version
lego:amd64 4.9.1-1  testingftp.debian.org
lego:amd64 4.9.1-1  unstableftp.debian.org
No experimental version
lego:amd64 not installed

Indeed, 3.2.0-3.1 is no longer the testing version. Your database
seems to be out-of-date.

I think you haven't noticed that I requested for "4.9.1-1" version from 
"testing" specifically,
hence why the command was "$ apt source lego/testing" not just "$ apt 
source lego".
There is no reason for building a backport package for "stable" using a 
source package from "stable"...


I've changed all my repo mirrors to "deb.debian.org" suspecting the 
previous mirror I used was somehow out-of-date. Why is my output differ 
from yours?


   $ apt-show-versions -a lego
   lego:amd64 3.2.0-3.1+b5 bullseye deb.debian.org
   No proposed-updates version
   No stable-updates version
   No testing version
   No unstable version
   lego:amd64 not installed
   lego:i386 3.2.0-3.1+b5 bullseye deb.debian.org
   No proposed-updates version
   No stable-updates version
   No testing version
   No unstable version
   lego:i386 not installed

Yet "rmadison" reports there is a version "4.9.1-1" available in "testing":

   $ rmadison lego
   lego   | 0.3.1-5+b13   | oldstable  | amd64, arm64, armel,
   armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
   lego   | 3.2.0-3.1+b5  | stable | amd64, arm64, armel,
   armhf, i386, mips64el, mipsel, ppc64el, s390x
   lego   | 4.9.1-1   | testing    | amd64, arm64, armel,
   armhf, i386, mips64el, mipsel, ppc64el, s390x
   lego   | 4.9.1-1   | unstable   | amd64, arm64, armel,
   armhf, i386, mips64el, mipsel, ppc64el, s390x

I suspect "apt-show-versions" output is inconsistent because I only 
request "deb-src" from "testing" in "sources.list", as I've shown before.


Here is another example package that works as expected:

   $ rmadison roundcube
   roundcube  | 1.3.17+dfsg.1-1~deb10u2 | oldstable    |
   source, all
   roundcube  | 1.4.13+dfsg.1-1~deb11u1~bpo10+1 | buster-backports |
   source, all
   roundcube  | 1.4.13+dfsg.1-1~deb11u1 | stable   |
   source, all
   roundcube  | 1.6.1+dfsg-1    | testing  |
   source, all
   roundcube  | 1.6.1+dfsg-1    | unstable |
   source, all

   $ apt-show-versions -a roundcube
   roundcube:all 1.4.13+dfsg.1-1~deb11u1 bullseye  deb.debian.org
   roundcube:all 1.4.13+dfsg.1-1~deb11u1 bullseye-security deb.debian.org
   No proposed-updates version
   No stable-updates version
   No testing version
   No unstable version
   roundcube:all not installed

   $ apt source roundcube/testing
   Reading package lists... Done
   Selected version '1.6.1+dfsg-1' (testing) for roundcube
   ...


I did some additional research and I think I got it.
"lego" package is special because its source package is named differently:

   $ rmadison golang-github-xenolf-lego
   golang-github-xenolf-lego | 0.3.1-5   | oldstable  | source
   golang-github-xenolf-lego | 3.2.0-3.1 | stable | source
   golang-github-xenolf-lego | 4.9.1-1   | testing    | source
   golang-github-xenolf-lego | 4.9.1-1   | unstable   | source
   golang-github-xenolf-lego | 4.9.1-1   | unstable-debug | source

   $ apt source golang-github-xenolf-lego/testing
   Reading package lists... Done
   Selected version '4.9.1-1' (testing) for golang-github-xenolf-lego
   ...

But why "apt" doesn't play along, since it knows the source package for 
"lego" has different name, but ignores the "testing" part of the request?


   $ apt source lego/testing
   Reading package lists... Done
   Picking 'golang-github-xenolf-lego' as source package instead of 'lego'
   E: Can not find version '3.2.0-3.1' of package 'lego'
   E: Unable to find a source package for golang-github-xenolf-lego


Looks like an "apt" bug to me.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: shell script run in backend

[Tom Reed]

stem service as Jeremy Ardley suggests in a different reply.
>
> Exactly:
>
>   script > /tmp/script.log 2>&1 &
>
> (adjust paths to taste). For good measure, and if your shell
> has job control, it will output the job number and PID, like
> so:
>
>   [1] 15211
>
> (1 is the job number, 15211 is the PID, actual numbers will
> vary). You then issue
>
>   disown %1
>
> (assuming bash here), which lets your shell "forget" about job
> number 1 and keep it for messing around once you leave your
> shell (in some setups, terminating the shell might terminate
> the background jobs, but my memory might be fuzzy).
>

Thanks for all your helps.
I know convert it to a perl script and run it under App::Daemon for
background jobs.

regards
Tom


-- 
sent from https://dkinbox.com/

Re: debian-user-digest Digest V2023 #447

[Richard Jones]

Is the list software blind to language _and_ spam?

On 14/5/23 11:59, debian-user-digest-requ...@lists.debian.org wrote:

how to boot freebsd from bullseye?

[hl]

i've installed freebsd 12 at 2nd partition of usb disk

after installation and reboot, bullseye's grub appears, bullseye is 
installed at 1st partition


i suppose freebsd installer has found existing boot loader, it decide to 
let grub or me to take care of booting bsd


but i'm inexperienced, i've run update-grub, it doesn't add bsd to grub 
menu.


how to add bsd entry to grub menu? below is menu for bullseye:

menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class 
gnu --class os $menuentry_id_option 
'gnulinux-simple-1a99c626-2623-438f-b730-797dc4db34d5' {

    load_video
    insmod gzio
    if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
    insmod part_msdos
    insmod ext2
    set root='hd1,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 
1a99c626-2623-438f-b730-797dc4db34d5

    else
      search --no-floppy --fs-uuid --set=root 
1a99c626-2623-438f-b730-797dc4db34d5

    fi
    echo    'Loading Linux 5.10.0-20-686-pae ...'
    linux    /boot/vmlinuz-5.10.0-20-686-pae 
root=UUID=1a99c626-2623-438f-b730-797dc4db34d5 ro  quiet

    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd.img-5.10.0-20-686-pae
}

Re: shell script run in backend

[tomas]

On Sun, May 14, 2023 at 12:20:02AM -0700, Will Mengarini wrote:
> * Tom Reed  [23-05/14=Sun 14:21 +0800]:
> > I have a long run shell script [...].  Currently the script
> > is running in front-end in shell.  How can I run it with
> > the backend way? Can I register it as a system service?
> 
> Just run 'myScript&' (the trailing '&' tells the shell to
> run it in the background) if there is no terminal output
> from the running script (terminal output will pause it); if
> there is, enclose the content of the script in redirection of
> standard output and standard error to a log file, or code a
> system service as Jeremy Ardley suggests in a different reply.

Exactly:

  script > /tmp/script.log 2>&1 &

(adjust paths to taste). For good measure, and if your shell
has job control, it will output the job number and PID, like
so:

  [1] 15211

(1 is the job number, 15211 is the PID, actual numbers will
vary). You then issue

  disown %1

(assuming bash here), which lets your shell "forget" about job
number 1 and keep it for messing around once you leave your
shell (in some setups, terminating the shell might terminate
the background jobs, but my memory might be fuzzy).

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: shell script run in backend

[Will Mengarini]

* Tom Reed  [23-05/14=Sun 14:21 +0800]:
> I have a long run shell script [...].  Currently the script
> is running in front-end in shell.  How can I run it with
> the backend way? Can I register it as a system service?

Just run 'myScript&' (the trailing '&' tells the shell to
run it in the background) if there is no terminal output
from the running script (terminal output will pause it); if
there is, enclose the content of the script in redirection of
standard output and standard error to a log file, or code a
system service as Jeremy Ardley suggests in a different reply.

Re: Stable and testing together?

[Hans]

Hi folks,

thanks for all the answers. Yes, I know, mixing both might be causing 
troubles. But sometimes I got no choice. 

For example, the NVidie kernel driver can not be compiled on newer kernels 
than 5.10.22. Reason is, that in the herader files of the newer kernel package 
some files are missing, which the compiler needs.

I filed a bugreport, but the devolper will not fix it, as they claim it an 
NVidia-issue. That does of course not explain, why it on one kernel versions 
builds and the next version not. However, I do not want to mourne about it, 
just tell, what I mean.

Then I saw, in testing the famous application "digikam" will be removed. So, 
if one did use digikam for a long time, he will be surprised and maybe angry, 
that suddenly digikam has gone.

These are only two examples, which can be trouble for users. You can of course 
say: "Hard luck!", but the only way to avoid this, is to mix stable and 
testing. Or (in case of graphics driver), buy a new hardware.

As we are only one month away from releasing the actual testing (which is in 
freeze state) to stable, I could upgrade now, if I want to. I tried a dry-run, 
and saw i.e. digikam to get being uninstalled and some others.

Also it tries to uninstall my NVidia package, which is worse, as it is running 
and I have to avoid this, because it will break my system. As it is a notebook 
I cannot change the graphics card. And no, nouveau is NOT an option!

Worse: I never will get it back, as once deinstalled, I will no more be able 
to build it again, as also the needed compiler and header files are gone in 
testing. Yeah, hard luck, ey?

As I said, no mourning, just telling, why I believe, deleting packages from 
the repo is not the best idea. However, this is only my personally view and 
maybe I am the only person in the world, who might be affected.

Anyway, I understood all the dangers, and as I (believe) I know, what I am 
doing, I hope upgrade to the next release will be without major problems.

Thunbs pressing!! 

Best regards

Hans