Re: No fool like an old fool (debian installation probs)

[David Wright]

On Tue 02 May 2023 at 02:21:20 (+0200), DdB wrote:
> Am 01.05.2023 um 21:38 schrieb David Wright:
> > And PARTLABELs aren't interfered with even by the installer.
> 
> This at least i can contradict for a fact.

So is this post the rebuttal, or are you posting the evidence elsewhere?

> VM is functional with known
> and documented partlabels, then the installer handles partitions
> (reformat is permitted) and the UUID's AND the PARTUUIDS were changed,
> which was a huge surprise.

OK, just so that it's clear, you have a disk with documented
PARTLABELs, and after installing an OS with the d-i, the UUIDs
and PARTUUIDs have been altered.

You /seem/ to then be saying that /this/ is evidence that the
PARTLABELs have been altered. Is that your contradiction?

If the PARTUUIDs are altered, it would be interesting to know what
you are doing in the partitioner step of the d-i. Your posts have
only mentioned reformatting partitions, not repartitioning disks.

> Just knowing about this, i can deal with the situation, but i think,
> this is based on a false understanding of how a persistent
> identification should be dealt with.

Cheers,
David.

Re: disk usage for /usr/lib on bullseye

[David Wright]

On Mon 01 May 2023 at 23:24:56 (-0400), Timothy M Butterworth wrote:
> On Mon, May 1, 2023 at 10:45 PM Rick Thomas  wrote:
> > On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> > > On 2/5/23 02:06, David Christensen wrote:
> > >> On 5/1/23 06:51, Bonno Bloksma wrote:
> > >>> The cause seems to be the folder /usr/lib/modules#
> > >>> linams:/usr/lib/modules# du * -sh
> > >>> 4.7M5.10.0-10-amd64
> > >>> 4.7M5.10.0-11-amd64
> > >>> 4.7M5.10.0-12-amd64
> > >>> 4.7M5.10.0-13-amd64
> > >>> 4.7M5.10.0-15-amd64
> > >>> 4.7M5.10.0-16-amd64
> > >>> 309M5.10.0-18-amd64
> > >>> 309M5.10.0-19-amd64
> > >>> 309M5.10.0-20-amd64
> > >>> 309M5.10.0-21-amd64
> > >>> 309M5.10.0-22-amd64
> > >>> 4.7M5.10.0-7-amd64
> > >>> 4.7M5.10.0-8-amd64
> > >>> 4.7M5.10.0-9-amd64
> > >>>
> 
> Did anyone else notice the massive jump in file size here? 4.7M to 309M is
> a huge increase in file size!

4.7MB is the size of the modules.* that are created during
installation, as I mentioned in my post. These are deleted
by purge but not by remove, whereas:

$ du -sh /lib/modules/5.10.0-22-amd64/
309M/lib/modules/5.10.0-22-amd64/
$ 

is the modules themselves, awaiting deletion. (Actually, this
particular listing is my live kernel.)

Host linams is the most burdened one, with five sets of modules.
I'm assuming that the kernels/initrds have gone from /boot. If
all five are still there, then the good news is that my first
post doesn't apply, and they've simply forgotten to remove the
1st, 2nd and 3rd oldest kernels (and it's best to use purge
for less clutter).

> > > Have you tried running also
> > > apt autoclean

I thought that just cleared /var/cache/apt/archives/.

> > > and
> > > apt purge

I've never tried that without a package name. What does it do?

Cheers,
David.

Re: disk usage for /usr/lib on bullseye

[Timothy M Butterworth]

On Mon, May 1, 2023 at 10:45 PM Rick Thomas  wrote:

> On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> > On 2/5/23 02:06, David Christensen wrote:
> >> On 5/1/23 06:51, Bonno Bloksma wrote:
> >>> Hi,
> >>>
> >>> On my "new" Bullseye machines the root volume starts to fill up. The
> >>> cause seems to be the /usr/lib folder.
> >>> On my older Buster (10.13) machine the total /usr directory is 701M,
> >>> the /usr/lib folder is 260M
> >>> In my /usr/lib folder on Buster is NO /usr/lib/modules folder
> >>>
> >>> On my Bullseye machines the /usr/lib folder is 2+GB on the machines
> >>> that have been operating for a while and 1+G on a machine that has
> >>> been operating for a shorter while.
> >>>
> >>> The cause seems to be the folder /usr/lib/modules#
> >>> linams:/usr/lib/modules# du * -sh
> >>> 4.7M5.10.0-10-amd64
> >>> 4.7M5.10.0-11-amd64
> >>> 4.7M5.10.0-12-amd64
> >>> 4.7M5.10.0-13-amd64
> >>> 4.7M5.10.0-15-amd64
> >>> 4.7M5.10.0-16-amd64
> >>> 309M5.10.0-18-amd64
> >>> 309M5.10.0-19-amd64
> >>> 309M5.10.0-20-amd64
> >>> 309M5.10.0-21-amd64
> >>> 309M5.10.0-22-amd64
> >>> 4.7M5.10.0-7-amd64
> >>> 4.7M5.10.0-8-amd64
> >>> 4.7M5.10.0-9-amd64
> >>>
> >>> And
> >>> linutr:/usr/lib/modules# du * -sh
> >>> 4.7M5.10.0-16-amd64
> >>> 4.7M5.10.0-17-amd64
> >>> 309M5.10.0-18-amd64
> >>> 309M5.10.0-19-amd64
> >>> 309M5.10.0-20-amd64
> >>> 309M5.10.0-21-amd64
> >>>
> >>> And
> >>> lola:/usr/lib/modules# du * -sh
> >>> 4.7M5.10.0-13-amd64
>


> >>> 4.7M5.10.0-19-amd64
> >>> 309M5.10.0-20-amd64
>

Did anyone else notice the massive jump in file size here? 4.7M to 309M is
a huge increase in file size!


> >>> 309M5.10.0-21-amd64
> >>> 309M5.10.0-22-amd64
> >>>
> >>> Guessing on what I see these are libraries for older kernel versions.
> >>> I usually clean up older kernel versions by using
> >>> # apt autoremove"
> >>> All 3 servers have 1 older kernel version installed according to apt
> >>> autoremove.
> >>>
> >
> > Have you tried running also
> > apt autoclean
> > and
> > apt purge
> > ?
> >
> > --
> > ..
> > Bret Busby
> > Armadale
> > West Australia
> > (UTC+0800)
> > ..
>
> Another thing I usually do after doing an "apt upgrade" that installs a
> new kernel is:
> aptitude -P purge '~o'
> aptitude -P purge '~c'
>
> The "-P" tells aptitude to ask permission before actually deleting
> anything.
>
> Rick
>
>

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

Re: disk usage for /usr/lib on bullseye

[Rick Thomas]

On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> On 2/5/23 02:06, David Christensen wrote:
>> On 5/1/23 06:51, Bonno Bloksma wrote:
>>> Hi,
>>>
>>> On my "new" Bullseye machines the root volume starts to fill up. The 
>>> cause seems to be the /usr/lib folder.
>>> On my older Buster (10.13) machine the total /usr directory is 701M, 
>>> the /usr/lib folder is 260M
>>> In my /usr/lib folder on Buster is NO /usr/lib/modules folder
>>>
>>> On my Bullseye machines the /usr/lib folder is 2+GB on the machines 
>>> that have been operating for a while and 1+G on a machine that has 
>>> been operating for a shorter while.
>>>
>>> The cause seems to be the folder /usr/lib/modules#
>>> linams:/usr/lib/modules# du * -sh
>>> 4.7M    5.10.0-10-amd64
>>> 4.7M    5.10.0-11-amd64
>>> 4.7M    5.10.0-12-amd64
>>> 4.7M    5.10.0-13-amd64
>>> 4.7M    5.10.0-15-amd64
>>> 4.7M    5.10.0-16-amd64
>>> 309M    5.10.0-18-amd64
>>> 309M    5.10.0-19-amd64
>>> 309M    5.10.0-20-amd64
>>> 309M    5.10.0-21-amd64
>>> 309M    5.10.0-22-amd64
>>> 4.7M    5.10.0-7-amd64
>>> 4.7M    5.10.0-8-amd64
>>> 4.7M    5.10.0-9-amd64
>>>
>>> And
>>> linutr:/usr/lib/modules# du * -sh
>>> 4.7M    5.10.0-16-amd64
>>> 4.7M    5.10.0-17-amd64
>>> 309M    5.10.0-18-amd64
>>> 309M    5.10.0-19-amd64
>>> 309M    5.10.0-20-amd64
>>> 309M    5.10.0-21-amd64
>>>
>>> And
>>> lola:/usr/lib/modules# du * -sh
>>> 4.7M    5.10.0-13-amd64
>>> 4.7M    5.10.0-19-amd64
>>> 309M    5.10.0-20-amd64
>>> 309M    5.10.0-21-amd64
>>> 309M    5.10.0-22-amd64
>>>
>>> Guessing on what I see these are libraries for older kernel versions. 
>>> I usually clean up older kernel versions by using
>>> # apt autoremove"
>>> All 3 servers have 1 older kernel version installed according to apt 
>>> autoremove.
>>>
>
> Have you tried running also
> apt autoclean
> and
> apt purge
> ?
>
> -- 
> ..
> Bret Busby
> Armadale
> West Australia
> (UTC+0800)
> ..

Another thing I usually do after doing an "apt upgrade" that installs a new 
kernel is:
aptitude -P purge '~o'
aptitude -P purge '~c'

The "-P" tells aptitude to ask permission before actually deleting anything.

Rick

Re: I need help with my var partition.

[The Wanderer]

On 2023-05-01 at 21:51, Maureen L Thomas wrote:

> Unfortunately I cannot install anything.  I used the command line and
> the app but neither of them will work.

I suspect that if you don't have the various directories under /var/,
you may not be able to use apt or aptitude or synaptic or the like, but
dpkg (in the form of 'dpkg -i /path/to/filename.deb') may still work.

If it doesn't, the only fallbacks that I can think of that would be
*more* likely to work - short of reinstalling Debian, anyway - involve
carefully extracting the .deb's contents into the correct root path, and
running any necessary follow-on scripts, *by hand*. And that would be
daunting even to me, though I understand that it's certainly possible.

> I have no idea what to do next. I used su and sudo first.  It just
> keeps saying it cannot connect with the base from which I get
> updates, etc.  I used the reinstall on brasero and it just said that
> it was up to date.  I am so confused.

This description seems to suggest that you're using a tool which is
trying to download the .deb file from a remote location. Those tools are
fairly likely to have problems if the directories under /var/ don't
exist.

Instead, I suggest that you try:

$ su -
# dpkg -i /var/cache/apt/archives/base-files_12_amd64.deb

(Or whatever the version number and architecture of your base-files
package may be; that's the oldest one I have on hand myself, from August
of 2021. You should probably be able to tab-complete the filename from
before the first underscore, but that depends on how your system is set
up.)

dpkg should, I think, have fewer dependencies on directory structure (et
cetera) than anything APT-based will have. It still might not be few
*enough*, but it's worth a shot.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: I need help with my var partition.

[Maureen L Thomas]

Unfortunately I cannot install anything.  I used the command line and 
the app but neither of them will work.  I have no idea what to do next.  
I used su and sudo first.  It just keeps saying it cannot connect with 
the base from which I get updates, etc.  I used the reinstall on brasero 
and it just said that it was up to date.  I am so confused.


On 5/1/23 9:15 PM, Tom Dial wrote:
This Debian-user thread seems to have gone silent, but it is not clear 
whether your problem is solved. If it is, just ignore this and move 
on. If not:


The Wanderer, in an earlier post (04/28/2023 at 19;02), suggested 
reinstalling the base-files package. I believe this is the correct 
procedure, at least to start with. It should be relatively free from 
any risk of doing further damage to your system. The same post also 
suggested you might need to reinstall other packages if they had 
created subdirectories under /var that are not included in the 
base-files package, That also should not significantly risk any 
further damage. Reinstalling installed packages sometimes helps and in 
my experience (almost 30 years now) is unlikely to be harmful. 
Reinstalling base-files (and other packages as needed) also should 
correct any permission problems that may have crept in.


How to reinstall a package depends on how you maintain or upgrade your 
system.


If you use synaptic or aptitude, both have reinstall options that you 
can choose from the menu or submenu you would use for a new package 
installation.


If you log in as root on a terminal or terminal emulator to install 
and upgrade software, the command would be


apt install --reinstall  - for example,
apt install --reinstall base-files

If you use sudo in a terminal or terminal emulator to maintain 
software, use the above commands prefixed by "sudo" as you normally 
would for actions that need administrator privileges.


This should reinstall the version of the base-files (or other named 
package) that matches the most recently installed version.


I think the reinstall process might sometimes pause to ask you to 
choose between installing the default configuration file from the 
package or keeping an existing one that you might have changed. It 
should be safe to keep the one already installed.


If you have questions about any of this, feel free to ask, either 
privately or on the list.


Regards,
Tom Dial



On 4/28/23 20:36, Maureen L Thomas wrote:

Here is what I got.

root@debian:/var# /bin/ls -ld */
drwxr-xr-x  2 root root   4096 Apr 28 15:46 backups/
drwxr-xr-x 19 root root   4096 Apr 12 20:20 cache/
drwxr-xr-x  2 root root   4096 Apr 28 20:59 cores/
drwxr-xr-x  2 root root   4096 Nov 13  2020 games/
drwxr-xr-x 62 root root   4096 Apr 12 20:20 lib/
drwxrwsr-x  2 root staff  4096 Sep 19  2020 local/
drwxrwxrwt  3 root root    100 Apr 28 21:13 lock/
drwxr-xr-x  8 root root   4096 Apr 28 21:36 log/
drwx--  2 root root  16384 Nov 12  2020 lost+found/
drwxrwsr-x  2 root mail   4096 Nov 12  2020 mail/
drwxr-xr-x  2 root root   4096 Nov 12  2020 opt/
drwxr-xr-x 27 root root    760 Apr 28 22:31 run/
drwxr-xr-x 14 root root   4096 Apr 27 22:58 snap/
drwxr-xr-x  7 root root   4096 Nov 12  2020 spool/
drwxr-xr-x  8 root root   4096 Apr 28 22:32 tmp/
root@debian:/var#


Reinstalling the base-files package should create or correct the 
following directories under /var:

/var
/var/backups
/var/cache
/var/lib
/var/lib/dpkg
/var/lib/misc
/var/local
/var/lock
/var/log
/var/run
/var/spool
/var/tmp




On 4/28/23 10:17 PM, Greg Wooledge wrote:

On Fri, Apr 28, 2023 at 10:05:01PM -0400, Maureen L Thomas wrote:
Yes my figures are very similar to yours.  But even after a reboot 
I still

cannot burn a back up disk.

Do not look at the NUMBERS.

OWNER.

GROUP.

PERMISSIONS.

The numbers mean nothing.


On 4/28/23 9:04 PM, Greg Wooledge wrote:

Make sure you get the ownership and permissions correct.

unicorn:/var$ /bin/ls -ld */
drwxr-xr-x  2 root root  4096 Apr 22 06:25 backups/
drwxr-xr-x 12 root root  4096 Jul 31  2022 cache/
drwxr-xr-x  3 root root  4096 Mar  3  2018 games/
drwxr-xr-x 50 root root  4096 Jul 31  2022 lib/
drwxrwsr-x  2 root staff 4096 Nov 19  2017 local/
See that?  Group write.  Set-group-id.  Group staff.  Probably not a 
big

deal, because who the hell uses /var/local for anything, but there is
no excuse for not checking the OWNER, GROUP and PERMISSIONS.


drwxrwxrwt  3 root root    80 Mar 25 16:03 lock/

Group and world write.  Sticky bit.


drwxr-xr-x 15 root root  4096 Apr 24 08:12 log/
drwxrwsr-x  2 root mail  4096 Oct 28  2021 mail/

Group write, setgid.


drwxr-xr-x  2 root root  4096 Jan 11  2018 opt/
drwxr-xr-x 10 root qmail 4096 Jan 12  2018 qmail/
drwxr-xr-x 26 root root   760 Mar 27 15:39 run/
drwxr-xr-x  6 root root  4096 Jan 29  2021 spool/
drwxrwxrwt  6 root root  4096 Apr 28 21:02 tmp/

Group and world write.  Sticky bit.

THIS is what matters.

Re: I need help with my var partition.

[Tom Dial]

This Debian-user thread seems to have gone silent, but it is not clear whether 
your problem is solved. If it is, just ignore this and move on. If not:

The Wanderer, in an earlier post (04/28/2023 at 19;02), suggested reinstalling 
the base-files package. I believe this is the correct procedure, at least to 
start with. It should be relatively free from any risk of doing further damage 
to your system. The same post also suggested you might need to reinstall other 
packages if they had created subdirectories under /var that are not included in 
the base-files package, That also should not significantly risk any further 
damage. Reinstalling installed packages sometimes helps and in my experience 
(almost 30 years now) is unlikely to be harmful. Reinstalling base-files (and 
other packages as needed) also should correct any permission problems that may 
have crept in.

How to reinstall a package depends on how you maintain or upgrade your system.

If you use synaptic or aptitude, both have reinstall options that you can 
choose from the menu or submenu you would use for a new package installation.

If you log in as root on a terminal or terminal emulator to install and upgrade 
software, the command would be

apt install --reinstall  - for example,
apt install --reinstall base-files

If you use sudo in a terminal or terminal emulator to maintain software, use the above 
commands prefixed by "sudo" as you normally would for actions that need 
administrator privileges.

This should reinstall the version of the base-files (or other named package) 
that matches the most recently installed version.

I think the reinstall process might sometimes pause to ask you to choose 
between installing the default configuration file from the package or keeping 
an existing one that you might have changed. It should be safe to keep the one 
already installed.

If you have questions about any of this, feel free to ask, either privately or 
on the list.

Regards,
Tom Dial



On 4/28/23 20:36, Maureen L Thomas wrote:

Here is what I got.

root@debian:/var# /bin/ls -ld */
drwxr-xr-x  2 root root   4096 Apr 28 15:46 backups/
drwxr-xr-x 19 root root   4096 Apr 12 20:20 cache/
drwxr-xr-x  2 root root   4096 Apr 28 20:59 cores/
drwxr-xr-x  2 root root   4096 Nov 13  2020 games/
drwxr-xr-x 62 root root   4096 Apr 12 20:20 lib/
drwxrwsr-x  2 root staff  4096 Sep 19  2020 local/
drwxrwxrwt  3 root root    100 Apr 28 21:13 lock/
drwxr-xr-x  8 root root   4096 Apr 28 21:36 log/
drwx--  2 root root  16384 Nov 12  2020 lost+found/
drwxrwsr-x  2 root mail   4096 Nov 12  2020 mail/
drwxr-xr-x  2 root root   4096 Nov 12  2020 opt/
drwxr-xr-x 27 root root    760 Apr 28 22:31 run/
drwxr-xr-x 14 root root   4096 Apr 27 22:58 snap/
drwxr-xr-x  7 root root   4096 Nov 12  2020 spool/
drwxr-xr-x  8 root root   4096 Apr 28 22:32 tmp/
root@debian:/var#


Reinstalling the base-files package should create or correct the following 
directories under /var:
/var
/var/backups
/var/cache
/var/lib
/var/lib/dpkg
/var/lib/misc
/var/local
/var/lock
/var/log
/var/run
/var/spool
/var/tmp




On 4/28/23 10:17 PM, Greg Wooledge wrote:

On Fri, Apr 28, 2023 at 10:05:01PM -0400, Maureen L Thomas wrote:

Yes my figures are very similar to yours.  But even after a reboot I still
cannot burn a back up disk.

Do not look at the NUMBERS.

OWNER.

GROUP.

PERMISSIONS.

The numbers mean nothing.


On 4/28/23 9:04 PM, Greg Wooledge wrote:

Make sure you get the ownership and permissions correct.

unicorn:/var$ /bin/ls -ld */
drwxr-xr-x  2 root root  4096 Apr 22 06:25 backups/
drwxr-xr-x 12 root root  4096 Jul 31  2022 cache/
drwxr-xr-x  3 root root  4096 Mar  3  2018 games/
drwxr-xr-x 50 root root  4096 Jul 31  2022 lib/
drwxrwsr-x  2 root staff 4096 Nov 19  2017 local/

See that?  Group write.  Set-group-id.  Group staff.  Probably not a big
deal, because who the hell uses /var/local for anything, but there is
no excuse for not checking the OWNER, GROUP and PERMISSIONS.


drwxrwxrwt  3 root root    80 Mar 25 16:03 lock/

Group and world write.  Sticky bit.


drwxr-xr-x 15 root root  4096 Apr 24 08:12 log/
drwxrwsr-x  2 root mail  4096 Oct 28  2021 mail/

Group write, setgid.


drwxr-xr-x  2 root root  4096 Jan 11  2018 opt/
drwxr-xr-x 10 root qmail 4096 Jan 12  2018 qmail/
drwxr-xr-x 26 root root   760 Mar 27 15:39 run/
drwxr-xr-x  6 root root  4096 Jan 29  2021 spool/
drwxrwxrwt  6 root root  4096 Apr 28 21:02 tmp/

Group and world write.  Sticky bit.

THIS is what matters.

Re: No fool like an old fool (debian installation probs)

[DdB]

Am 01.05.2023 um 21:38 schrieb David Wright:
> And PARTLABELs aren't interfered with even by the installer.

This at least i can contradict for a fact. VM is functional with known
and documented partlabels, then the installer handles partitions
(reformat is permitted) and the UUID's AND the PARTUUIDS were changed,
which was a huge surprise.

Just knowing about this, i can deal with the situation, but i think,
this is based on a false understanding of how a persistent
identification should be dealt with.

my 2 cents
DdB

Re: No fool like an old fool (debian installation probs)

[DdB]

Am 01.05.2023 um 19:46 schrieb David Christensen:
> Reading the above plus your previous post "Looking for
> inspiration/advice/best practices on system upgrade", it seems that you
> are making things too complicated.
> 
> 
> I would pick one machine, disable/ disconnect/ uninstall all of the
> drives except optical, install a zeroed 2.5" SATA SSD, make a decision
> regarding BIOS/MBR (legacy) vs. UEFI/GPT, run the Setup utility and
> configure CMOS/NVRAM settings accordingly, boot the Debian installer,
> pick "Install", partition the SSD manually with a 1 GB ESP (if doing
> EUFI/GPT), a 1 GB boot partition (ext4), 1 GB or larger swap partition,
> and a 12 GB root partition (ext4), at the "Choose software" page select
> "SSH server", select "standard system utilities", and deselect
> everything else.  After reboot, you should have a working Debian instance.

I am sorry, i do not really understand, what you want to point to.
Your suggestions are coming without even knowing, what my needs and
options are, and involve alternatives that look unnecessary in my view.

Just to give you an idea: my OS partitions are 20 GB and that seems to
be a little too small, i had to delete stuff in order to keep the
systems in good shape.
I did abandon MBR years ago, and look with some bemusement at the many
places, whare that old technology still lingers.
Physical un-/plugging at the machines always involves getting external
help, due to a handicap.
Maybe your feeling is correct and i am in fact complicating things, i
don't know. OTOH, i am dealing with 2 dozen disks, server grade HW,
DUAL-CPU EPYC, 128 GB ECC RAM, nvme-ssd, aso.
My understanding is, that precautions are in order to keep the system(s)
up and running and useable for someoone, who is bad at typing.

I have installed many debian VM's before, all of them with a desktop,
and many of them are in use while i am investigating, how to
replace/upgrade the host OS. Do you get the idea?

But thanks for voicing your concerns, somthing i am trying to understand
and consider. Just keep in mind, that if a problem arises, i might not
be able too deal with, i will be cut off from everything, no paper based
calendar even exists. So i am careful.

DdB

Re: sha256sum --text generating blank spaces and hyphens?

[Albretch Mueller]

On 4/27/23, David Christensen  wrote:
> Please see the OP, step (d).

>On 4/26/23, Albretch Mueller  wrote:
>>  a) encode the string name as base64
>> b) calculate the sha256sum of §a
>>  c) use §b as file name (of course, leaving the original extension as it
>> is)
>>  d) include a "§b_file_name.txt" plain text file descriptor which only
>> content is the actual prehash name of that file.

 I do that because base64 would (must?) work on any OS and the
conversion from and to any other encoding is straightforward. As you
suggested, I am more friendly to the idea of including hashes of the
data payload, even though I think it is not that important, because
the actual big problem that corpora research people have is files with
exactly the same look and feel and the same content which have
different hashes (for example, pdf files). I have been thinking about
a way to compute hashes which resemble more faithfully, both,
structural and content similarity among files. Do you know of any way
to do such thing? The structural aspect should be "easy". It could be
handled as DAGs of some sort of XPaths.

  I was actually going to show to you what I meant, but I was happy to
see "I was wrong". I even waited to try it from some other access
point. I have used this one liner to show how
google/youtube/NSA/"Vladimir Putin"/... was watermarking files for
whatever reason, but it worked fine when I was trying to show it to
you ;-)

_YT_URI=EngW7tLk6R8; _OFL="${_YT_URI}_"$(date +%Y%m%d%H%M%S)".mp4";
./yt-dlp --verbose --format "mp4" --output "${_OFL}" -- "${_YT_URI}";
ls -l "${_OFL}"; file --brief "${_OFL}"; time sha256sum "${_OFL}"


-rwxrwxrwx 1 user user 828540 Aug 15  2022 EngW7tLk6R8_20230501185618.mp4
ISO Media, MP4 v2 [ISO 14496-14]
0b950b88667b5fec35f3dd54005c16e5e742c703a0c776ec6da11b60a4775ae6
EngW7tLk6R8_20230501185618.mp4

-rwxrwxrwx 1 user user 828540 Aug 15  2022 EngW7tLk6R8_20230501185657.mp4
ISO Media, MP4 v2 [ISO 14496-14]
0b950b88667b5fec35f3dd54005c16e5e742c703a0c776ec6da11b60a4775ae6
EngW7tLk6R8_20230501185657.mp4

 Max Nikulin (12023-04-28):
> And you will quickly face servers that sends incorrectly Content-Type or
> intentionally put application/octet-stream with no sniff header to force
> browser to save the file instead of opening it e.g. in built-in PDF
> reader.

 Even if not totally syntactic (so you can't functionally solve it
with some code), this is a relatively manageable problem, you would:

 a) take notice of the sites that do such things;
 b) sniff not only the http headers, but notice the file extension of
the file; and
 c) safe the file to a temp repository for the Linux util "file" to be
run on it ...

 Out of those heuristics you should be able to strategize around such problems.

 lbrtchx

Re: No fool like an old fool (debian installation probs)

[DdB]

Am 01.05.2023 um 10:33 schrieb Michel Verdier:
> Le 1 mai 2023 DdB a écrit :
> 
>> Any suggestions/questions/hints from the power-users in here?
>> ... would be wildly appreciated ...
> 
> When installing you have to stop on your first problem. The others could
> be created from it. It's longer but easier to cope with. So give us full
> details on your first problem or choice you don't understand.
> 
> 
Thank you for being this clear.
In the meantime i changed my plan somewhat (as stated earlier, i am now
willing to defer the resolution of the PARTUUID topic till later, in
order to see, if the upgraded GNOME will be able to serve me well, just
as the buster one did). Also, i wanted to be certain, that i will be
able to deal with the zfs upgrade.

Today, i found, that GNOME extensions are causing quite a bit of
trouble. The cause being, that the one extension, i have been using very
extensively ("Quick-Toggler") has been orphaned and is way out of sync
with current gnome-shell. That really hurts, as it had already been a
replacement for another extension, that had been orphaned in jessie
IIRC. - This is already the second time, that i have to find adjustments
in my workflow after an upgrade, due to changing functionality and lack
of compatibility. ... makes me somewhat unhappy, as i have been involved
 quite a bit in software rollout processes and we cared very much for
(paying) customer satisfaction. Ofc, this could be different in a
project based on the workforce from volunteers.

But it got even worse:
The site extensions.gnome.org let me know, that it cannot sync
extensions with my gnome-shell, because of a version mismatch. So i read
up a bit to understand, what is going on, and found the most concice
description here: (1)
Funny little detail: Ubuntu is suffering way less, because their
distribution is based on more recent version than debian stable is.

At least i saw some guy posting a video on youtube showing, how he
upgraded gnome-shell to experimental thereby creating a frankendebian,
something, i thought was an absolute no-go!

So i could not resolve the issue (You need to update
gnome-browser-connector to at least version 42.0), because the version
from debian is something like 10.1 or so.

Once again, i am happy to just playing around, not touching the
workhorse, that is still on buster, until i find a safe way forward.

zfs seems to be working fine on bullseye, the dev from the Quick-Toggler
published, that he abandonned the software due to his switch to KDE a
few years back.

Now, i am considering, if i should investigate the other desktops before
making a decision?

(1)
https://bugs.launchpad.net/ubuntu/+source/chrome-gnome-shell/+bug/1983851

Very sad, that the upgrade turns out to be rather difficult for a human
being like me, that is more or less isolated in his basement with no
friends sharing the passion for computing, or debian - for that matter.

So this is my todays report. Confused and undecided, i will head over to
get some rest now.
Ofc, i am curious to learn, how the crowd of "standard users" is dealing
with gnome extensions atm.

Re: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 17:53:08 -0400, gene heskett wrote:

> On 5/1/23 13:34, Brian wrote:

[...]

> > A possible way forward is to execute
> > 
> >sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D 
> > -E -m raw
> which gets me this warning:
> gene@bpi51:~$ sudo lpadmin -p HLL2320D-RAW -v
> ipp://192.168.71.3:631/printers/HLL2320D -E -m raw
> [sudo] password for gene:
> lpadmin: Raw queues are deprecated and will stop working in a future version
> of CUPS.

A standard warning that is clear enough.

> lpadmin: Use the 'everywhere' model for shared printers.
> 
> And I wouldn't use the everywhere option ever as it cripples the printer
> down to the lowest common performing option list, losing among other things,
> the duplex ability. So it MUST use the Brother driver.

Your demand is granted. -m raw uses the Brother driver on coyote.
 
> > 
> > and try
> > 
> then I ran this w/o the sudo:
> >lp -d HLL2320D-RAW printer.cfg
> And got this:
> gene@bpi51:~$ lp -d HLL2320D-RAW printer.cfg
> request id is HLL2320D-RAW-1 (1 file(s))

That's OK.

> printing the file in portrait mode, full duplex, but the file is wider and I
> would normally put it in landscape mode to reduce the auto-word-wrapping
> confusion. Does -o landscape still work with the raw option?
> 
> Yes, provided the -olandscape is after the -d argument. That file is a 3d
> printer description for klipper, 5 pages in landscape mode.  And is the
> first and 2nd time I've been able to print it. Thank you very much.
> Can we continue, making a shell script to do this again with all variations
> available for the -o options of lp?

See the lpadmin manual for how to set up different queues with differnent
options on bpi51.

Glad you are now printing, but you really need to fix the CUPS installation.

-- 
Brian.

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 17:22, Brian wrote:

On Mon 01 May 2023 at 20:59:50 +0100, debian-u...@howorth.org.uk wrote:


gene heskett  wrote:


I'd think I could start by comparing cupsd.conf's, but miss And I
can't see the trees for all this forest in the way in both, but
missing is a client.conf. I think... But that is probably whats
wrong, me thinking.


Your directory listings showed that both had a ppd directory, but you
didn't show the content of those directories. Since your error message
was specifically that it couldn't find the PPD, the first thing I'd do
is compare those two directories.


The message was not about not being able to *find* a PPD. Finding something
implies it already exists. Here is the message againn:


lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class
does not exist.



And it did not exist until the lpadmin created it.

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: repeat of previous question that has goneunansweredseveraltimes.

[gene heskett]

On 5/1/23 16:00, debian-u...@howorth.org.uk wrote:

gene heskett  wrote:


I'd think I could start by comparing cupsd.conf's, but miss And I
can't see the trees for all this forest in the way in both, but
missing is a client.conf. I think... But that is probably whats
wrong, me thinking.


Your directory listings showed that both had a ppd directory, but you
didn't show the content of those directories. Since your error message
was specifically that it couldn't find the PPD, the first thing I'd do
is compare those two directories.


The 1st armbian, bpi51, /etc/cups/ppd does contain the PDF generator PPD
The 4th one, bpi54 /etc/cups/ppd is empty. All were installed with the 
same bullseye 11.6 installer. The other two are presently powered down 
in the middle of building a quad of 3d printers around them.


I might be getting on in the middle of my 88th year here, but I can 
still carve useful things in OpenSCAD and in gcode. At the link in my 
sig you'll find a link to this machine, and in that link are some pix of 
what I'm doing. I wrote every byte of the gcode that carves those wooden 
screws in a couple of those pix.


Stronger by quite a bit than anything you can get from fleabay at any price.

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: Segfaults after upgrade to Debian 11.7 on virtualized systems with AMD Ryzen CPU

[NetValue Operations Centre]

Good thinking, trying that.

I worked through some of the cpu features, and when removing the line:



the test VM on 5.10.0-22-amd64 booted successfully.

https://www.kernel.org/doc/Documentation/x86/protection-keys.txt

"Memory Protection Keys provides a mechanism for enforcing page-based
protections"

"The kernel will send a SIGSEGV in both cases, but si_code will be set
to SEGV_PKERR when violating protection keys versus SEGV_ACCERR when
the plain mprotect() permissions are violated."

So, sounds like a memory protection system which can result in seg faults.

AFAICT the host system is running just fine with PKU feature on hosts 
running either 5.10.0-21-amd64 or 5.10.0-22-amd64, and the host kernel 
doesn't seem to affect the guest's behaviour either, only if the guest 
is running 5.10.0-22-amd64 with PKU passed through.


I don't know the best bug tracker to create a ticket in would be... 
https://packages.debian.org/bullseye/linux-image-5.10.0-22-amd64 ?


Regards,
--
Alan Jackson   | Systems Administrator
NetValue Limited

Re: repeat of previous question that has goneunansweredseveraltimes.

[gene heskett]

On 5/1/23 16:00, debian-u...@howorth.org.uk wrote:

gene heskett  wrote:


I'd think I could start by comparing cupsd.conf's, but miss And I
can't see the trees for all this forest in the way in both, but
missing is a client.conf. I think... But that is probably whats
wrong, me thinking.


Your directory listings showed that both had a ppd directory, but you
didn't show the content of those directories. Since your error message
was specifically that it couldn't find the PPD, the first thing I'd do
is compare those two directories.


The ppd dirs are empty.

And if a copy/paste from this machine, hosting the printers fixes it on 
the other bullseye machines so these printers are available to whomever 
wants to use them, like geany or okular etc, can we create a cups bug 
entry? Perms on those empty ppd dirs are:

gene@bpi54:~$ ls -l /etc/cups
total 80
-rw-r--r-- 1 root root30 Apr  8 20:07 client.conf
-rw-r--r-- 1 root root 30456 Apr 14 03:14 cups-browsed.conf
-rw-r--r-- 1 root root  6486 Apr 30 05:09 cupsd.conf
-rw-r--r-- 1 root root  3047 May 23  2022 cups-files.conf
drwxr-xr-x 2 root root  4096 May 23  2022 interfaces
drwxr-xr-x 2 root lp4096 May 23  2022 ppd
-rw-r--r-- 1 root root   240 Oct 15  2022 raw.convs
-rw-r--r-- 1 root root   211 Oct 15  2022 raw.types
-rw-r--r-- 1 root root   142 May 23  2022 snmp.conf
drwx-- 2 root lp4096 May 23  2022 ssl
-rw-r- 1 root lp  93 Feb  6 23:41 subscriptions.conf
-rw-r- 1 root lp 335 Feb  6 23:35 subscriptions.conf.O
gene@bpi54:~$ ls -l /etc/cups/ppd
total 0

So it looks to me like cups, to add a printer, needs to be either root, 
ask a sudo pw, or be a member of group lp.


But group lp is bereft of any other members with "lp:x:7:" as its one 
and only member, but cups on these machines has yet to ask me for a pw. 
This looks like it could be part of the original show stopper problem?

Or, am I overthinking this again?



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: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 14:31, Brian wrote:

On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote:


On 5/1/23 12:30, Brian wrote:


[...]


The -l option asks the queue for the specific options it offers. The response
indicates something wrong with CUPS on bpi51. I haven't any problem when doing
this and getting sensible outputs on my Debian unstable machine.


Which isn't quite a 1:1 comparison as that will be bookworm shortly.

Or, should I update the bullseyes to unstable? IDK and I'm not even sure
how...


Forget about doing that. I was merely commenting that my Debian did not
behave like yours. Is yours a fruit-flavoured varian?


Assuming your buster machines (which are working) have similar setups to bpi51,


Which is a bullseye machine. And has a totally different content to the
/etc/cups directory as shown by my last post, much more complex on the
bullseye installs that don't work.


THe difference is highly likely to be relevant. You are grasping at straws.


you couls try the two commands (and all the others in this thread) on one of
those.


I'd think I could start by comparing cupsd.conf's, but miss And I can't see
the trees for all this forest in the way in both, but missing is a
client.conf. I think... But that is probably whats wrong, me thinking.


A client.conf is unneeded on a well-behaved CUPS system that obtains info
from avahi-daemon.

in the past, its been required to nuke any and all instances found with 
avahi in its name in order to get rid of the totally bogus 
169.xx.xxx.xxx. default route address as is now reported by ip r after a 
reboot.  This has been true even before jessie. However I've now 
re-installed it on two of these armbian bullseye machines w/o losing my 
network. Perhaps it has learned some manners since jessie? Network 
Manager, my other major headache certainly has.


Take care and stay well Brian.

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: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 13:34, Brian wrote:

On Mon 01 May 2023 at 13:03:50 -0400, gene heskett wrote:


On 5/1/23 12:30, Brian wrote:


Assuming your buster machines (which are working) have similar setups to bpi51,
you couls try the two commands (and all the others in this thread) on one of
those.


one of those machines reports this for the -l option:

gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l
PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive
FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6
4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm
CUSTOM1 CUSTOM2 CUSTOM3
BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK
ENVTHIN RECYCLED
InputSlot/InputSlot: MANUAL *TRAY1
Duplex/Duplex: DuplexTumble *DuplexNoTumble None
Resolution/Resolution: 300dpi *600dpi 2400x600dpi
TonerSaveMode/Toner Save: *OFF ON
Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes


Looks reasonable. A similar command on the server should give a similar output.

The reason 'lp -d HLL2320D_coyote printer.cfg' failed is because CUPS is unable
to query the HLL2320D_coyote printer for its attributes. Printing from anything
else, such as Firefox, will also fail. CUPS on the bullseye machine appears to
be broken.

[...]

A possible way forward is to execute

   sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E 
-m raw

which gets me this warning:
gene@bpi51:~$ sudo lpadmin -p HLL2320D-RAW -v 
ipp://192.168.71.3:631/printers/HLL2320D -E -m raw

[sudo] password for gene:
lpadmin: Raw queues are deprecated and will stop working in a future 
version of CUPS.

lpadmin: Use the 'everywhere' model for shared printers.

And I wouldn't use the everywhere option ever as it cripples the printer 
down to the lowest common performing option list, losing among other 
things, the duplex ability. So it MUST use the Brother driver.




and try


then I ran this w/o the sudo:

   lp -d HLL2320D-RAW printer.cfg

And got this:
gene@bpi51:~$ lp -d HLL2320D-RAW printer.cfg
request id is HLL2320D-RAW-1 (1 file(s))

printing the file in portrait mode, full duplex, but the file is wider 
and I would normally put it in landscape mode to reduce the 
auto-word-wrapping confusion. Does -o landscape still work with the raw 
option?


Yes, provided the -olandscape is after the -d argument. That file is a 
3d printer description for klipper, 5 pages in landscape mode.  And is 
the first and 2nd time I've been able to print it. Thank you very much.
Can we continue, making a shell script to do this again with all 
variations available for the -o options of lp?


Take care & stay well Brian.





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: repeat of previous question that has gone unansweredseveraltimes.

[debian-user]

gene heskett  wrote:

> I'd think I could start by comparing cupsd.conf's, but miss And I
> can't see the trees for all this forest in the way in both, but
> missing is a client.conf. I think... But that is probably whats
> wrong, me thinking.

Your directory listings showed that both had a ppd directory, but you
didn't show the content of those directories. Since your error message
was specifically that it couldn't find the PPD, the first thing I'd do
is compare those two directories.

Re: disk usage for /usr/lib on bullseye

[Brad Rogers]

On Mon, 1 May 2023 12:10:08 -0600
Charles Curley  wrote:

Hello Charles,

>Ah. I don't recall that I've ever tried that. Maybe one should
>experiment on a throw-away VM. :-)

Go ahead:  What's life without a little jeopardy?   :-)

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Shut it up you silly cow
Golden Green - Wonder Stuff


pgpjFrQmDr15o.pgp
Description: OpenPGP digital signature

Re: disk usage for /usr/lib on bullseye

[Brad Rogers]

On Mon, 01 May 2023 14:09:56 -0400
Stefan Monnier  wrote:

Hello Stefan,

>The main downside is usually that you won't be able to access

Or reboot, into a working system,  if it's the *only* kernel.  But
hey... :-)

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
There's no point in asking you'll get no reply
Pretty Vacant - Sex Pistols


pgpIooN_C1AIY.pgp
Description: OpenPGP digital signature

Re: No fool like an old fool (debian installation probs)

[David Wright]

On Mon 01 May 2023 at 13:08:56 (+0200), DdB wrote:

> One explanation of my choice to stick with PARTUUID's:
> In my overall stategy of using my computer, i am sometimes copying (dd)
> whole partitions into a backup, a secondary partition or a VM, which can
> easily lead to difficulties, if the same LABELS were used, which can be
> changed, but reside INSIDE the partition itself, whereas PARTUUID's
> reside in the GPT, which is not affected on partition copy operations.

PARTLABELs also reside in the GPT.

> Thus my choice was related to convenience, avoiding some adjustments
> after partition copy operations. Only the installer interferes with the
> so called "persistent" PARTUUID's, which i regard as being offensive (or
> ignorant - for that matter).

And PARTLABELs aren't interfered with even by the installer.

> I am going to fix that later (on my machine), returning to my preferred
> fstab format of using PARTUUID whereever appropriate.

Your choice, of course. This post is just FTR.

Cheers,
David.

Re: disk usage for /usr/lib on bullseye

[David Christensen]

On 5/1/23 11:14, Bret Busby wrote:


On 5/1/23 06:51, Bonno Bloksma wrote:

Hi,

On my "new" Bullseye machines the root volume starts to fill up.



Have you tried running also
apt autoclean
and
apt purge
?



I updated and cleaned my daily driver recently:

2023-04-29 11:54:03 root@taz ~
# apt-get update


2023-04-29 11:54:29 root@taz ~
# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  linux-headers-amd64 linux-image-amd64

Do you want to continue? [Y/n] n
Abort.

2023-04-29 11:54:55 root@taz ~
# apt-get dist-upgrade


2023-04-29 12:31:08 root@taz ~
# apt autoremove


2023-04-29 12:32:11 root@taz ~
# apt clean


2023-04-29 12:34:22 root@taz ~/taz.tracy.holgerdanske.com
# fstrim -a



Something for today -- systemd journal:

2023-05-01 12:20:57 root@taz ~
# du -mx -d 1 /var/log | sort -nr | head
426 /var/log
401 /var/log/journal
15  /var/log/installer
1   /var/log/speech-dispatcher
1   /var/log/runit
1   /var/log/private
1   /var/log/lightdm
1   /var/log/cups
1   /var/log/apt

2023-05-01 12:23:03 root@taz ~
# journalctl --disk-usage
Archived and active journals take up 400.0M in the file system.

2023-05-01 12:25:46 root@taz ~
# journalctl --vacuum-size=100M


2023-05-01 12:28:05 root@taz ~
# journalctl --disk-usage
Archived and active journals take up 104.0M in the file system.

2023-05-01 12:28:35 root@taz ~
# du -mx -d 1 /var/log | sort -nr | head
130 /var/log
105 /var/log/journal
15  /var/log/installer
1   /var/log/speech-dispatcher
1   /var/log/runit
1   /var/log/private
1   /var/log/lightdm
1   /var/log/cups
1   /var/log/apt


Current usage of boot and root:

2023-05-01 12:34:52 root@taz ~
# df /boot /
Filesystem 1M-blocks  Used Available Use% Mounted on
/dev/sda2   921M  118M  740M  14% /boot
/dev/mapper/sda4_crypt11145M 6575M 3983M  63% /


David

Re: disk usage for /usr/lib on bullseye

[David Wright]

On Mon 01 May 2023 at 11:06:25 (-0600), Charles Curley wrote:
> On Mon, 1 May 2023 13:51:06 + > Bonno Bloksma wrote:
> 
> > Guessing on what I see these are libraries for older kernel versions.
> > I usually clean up older kernel versions by using # apt autoremove"
> > All 3 servers have 1 older kernel version installed according to apt
> > autoremove.
> 
> Autoremove removes packages, it does not purge. The difference is that
> remove leaves configuration files in place. So you have a tedious bit
> of "apt purge linux-image-… [linux-image-…]" etc. ahead. Just be sure
> to not purge the two most recent kernel packages, and especially not
> the kernel you are currently running on.

The modules aren't configuration files. AFAICT linux-image-*.debs
don't contain any. A small number of module.* files are generated
at installation time, eg modules.dep is probably the best known.

> > Why is this stuff there? Can I delete it?
> > If I can delete it, is there a proper way to clean it up or do I just
> > rm /usr/lib/modules/5.10.0- for the older kernels?
> 
> See above.
> 
> I conjecture that the reason updating the kernel removes rather than
> purges old kernels is in case the user has a custom kernel and wishes
> to preserve those customizations.

But if you create custom modules in the modules tree (which
I used to do with ndiswrapper), then they don't appear in
/var/lib/dpkg/info/linux-image-*.md5sums, so they should get
left behind by remove or purge.

The only other files that remove will normally leave behind
are those that are generated at installation time. The
package's postrm script attempts to delete these, and lastly
the /lib/modules/$version/ directory if it is empty.

Cheers,
David.

Re: disk usage for /usr/lib on bullseye

[Bret Busby]

On 2/5/23 02:06, David Christensen wrote:

On 5/1/23 06:51, Bonno Bloksma wrote:

Hi,

On my "new" Bullseye machines the root volume starts to fill up. The 
cause seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M, 
the /usr/lib folder is 260M

In my /usr/lib folder on Buster is NO /usr/lib/modules folder

On my Bullseye machines the /usr/lib folder is 2+GB on the machines 
that have been operating for a while and 1+G on a machine that has 
been operating for a shorter while.


The cause seems to be the folder /usr/lib/modules#
linams:/usr/lib/modules# du * -sh
4.7M    5.10.0-10-amd64
4.7M    5.10.0-11-amd64
4.7M    5.10.0-12-amd64
4.7M    5.10.0-13-amd64
4.7M    5.10.0-15-amd64
4.7M    5.10.0-16-amd64
309M    5.10.0-18-amd64
309M    5.10.0-19-amd64
309M    5.10.0-20-amd64
309M    5.10.0-21-amd64
309M    5.10.0-22-amd64
4.7M    5.10.0-7-amd64
4.7M    5.10.0-8-amd64
4.7M    5.10.0-9-amd64

And
linutr:/usr/lib/modules# du * -sh
4.7M    5.10.0-16-amd64
4.7M    5.10.0-17-amd64
309M    5.10.0-18-amd64
309M    5.10.0-19-amd64
309M    5.10.0-20-amd64
309M    5.10.0-21-amd64

And
lola:/usr/lib/modules# du * -sh
4.7M    5.10.0-13-amd64
4.7M    5.10.0-19-amd64
309M    5.10.0-20-amd64
309M    5.10.0-21-amd64
309M    5.10.0-22-amd64

Guessing on what I see these are libraries for older kernel versions. 
I usually clean up older kernel versions by using

# apt autoremove"
All 3 servers have 1 older kernel version installed according to apt 
autoremove.




Have you tried running also
apt autoclean
and
apt purge
?

--
..
Bret Busby
Armadale
West Australia
(UTC+0800)
..

Re: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote:

> On 5/1/23 12:30, Brian wrote:

[...]

> > The -l option asks the queue for the specific options it offers. The 
> > response
> > indicates something wrong with CUPS on bpi51. I haven't any problem when 
> > doing
> > this and getting sensible outputs on my Debian unstable machine.
> 
> Which isn't quite a 1:1 comparison as that will be bookworm shortly.
> 
> Or, should I update the bullseyes to unstable? IDK and I'm not even sure
> how...

Forget about doing that. I was merely commenting that my Debian did not
behave like yours. Is yours a fruit-flavoured varian?

> > Assuming your buster machines (which are working) have similar setups to 
> > bpi51,
> 
> Which is a bullseye machine. And has a totally different content to the
> /etc/cups directory as shown by my last post, much more complex on the
> bullseye installs that don't work.

THe difference is highly likely to be relevant. You are grasping at straws.

> > you couls try the two commands (and all the others in this thread) on one of
> > those.
> > 
> I'd think I could start by comparing cupsd.conf's, but miss And I can't see
> the trees for all this forest in the way in both, but missing is a
> client.conf. I think... But that is probably whats wrong, me thinking.

A client.conf is unneeded on a well-behaved CUPS system that obtains info
from avahi-daemon.

-- 
Brian.

Re: disk usage for /usr/lib on bullseye

[Charles Curley]

On Mon, 1 May 2023 18:52:09 +0100
Brad Rogers  wrote:

> If memory serves, should one try to do that, warnings are issued.
> 
> Not quite HAL in "2001, A Space Odyssey", but near enough.   :-)

Ah. I don't recall that I've ever tried that. Maybe one should
experiment on a throw-away VM. :-)

Daisy, Daisy! I'm half crazy!
etc.

-- 
Does anybody read signatures any more?

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

Re: disk usage for /usr/lib on bullseye

[Stefan Monnier]

>>to not purge the two most recent kernel packages, and especially not
>>the kernel you are currently running on.
> If memory serves, should one try to do that, warnings are issued.
> Not quite HAL in "2001, A Space Odyssey", but near enough.   :-)

Also, purging the current kernel is not nearly as dangerous as
it sounds: in many (most) cases, the system will keep working just as
well as before (IIUC even hibernation will keep working since you can
now resume using a different initrd&kernel than the one you're resuming
to).  The main downside is usually that you won't be able to access
devices that require different drivers than the ones already loaded.


Stefan

Re: disk usage for /usr/lib on bullseye

[David Christensen]

On 5/1/23 06:51, Bonno Bloksma wrote:

Hi,

On my "new" Bullseye machines the root volume starts to fill up. The cause 
seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M, the 
/usr/lib folder is 260M
In my /usr/lib folder on Buster is NO /usr/lib/modules folder

On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have 
been operating for a while and 1+G on a machine that has been operating for a 
shorter while.

The cause seems to be the folder /usr/lib/modules#
linams:/usr/lib/modules# du * -sh
4.7M5.10.0-10-amd64
4.7M5.10.0-11-amd64
4.7M5.10.0-12-amd64
4.7M5.10.0-13-amd64
4.7M5.10.0-15-amd64
4.7M5.10.0-16-amd64
309M5.10.0-18-amd64
309M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64
309M5.10.0-22-amd64
4.7M5.10.0-7-amd64
4.7M5.10.0-8-amd64
4.7M5.10.0-9-amd64

And
linutr:/usr/lib/modules# du * -sh
4.7M5.10.0-16-amd64
4.7M5.10.0-17-amd64
309M5.10.0-18-amd64
309M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64

And
lola:/usr/lib/modules# du * -sh
4.7M5.10.0-13-amd64
4.7M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64
309M5.10.0-22-amd64

Guessing on what I see these are libraries for older kernel versions. I usually 
clean up older kernel versions by using
# apt autoremove"
All 3 servers have 1 older kernel version installed according to apt autoremove.


Why is this stuff there? Can I delete it?
If I can delete it, is there a proper way to clean it up or do I just rm 
/usr/lib/modules/5.10.0- for the older kernels?

Is this a BUG in Bullseye?


p.s. Looking at this I just noticed I need to do an update on lunutr, I will 
dis that right after sending this mail ;-)


Met vriendelijke groet,
Bonno Bloksma
Senior Systeembeheerder


St. Jacobsstraat 400 | 3511 BT | Utrecht
030 - 3036 877 | direct 040-7 999 832
b.blok...@tio.nl | www.tio.nl

Volg ons op Facebook | LinkedIn | Instagram | YouTube




I use apt-get(8) 'update', 'upgrade', and 'dist-upgrade' on my Debian 
instances and let it deal with /usr/lib/modules.  Here is my daily 
driver, installed on March 16, 2023, and updated/ dist-upgraded on April 
29, 2023:


2023-05-01 10:55:22 root@taz ~
# cat /etc/debian_version ; uname -a
11.7
Linux taz 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 
GNU/Linux


2023-05-01 11:00:53 root@taz ~
# l -1 /boot/vmlinuz*
/boot/vmlinuz-5.10.0-21-amd64
/boot/vmlinuz-5.10.0-22-amd64

2023-05-01 11:01:36 root@taz ~
# du -mx -d 2 /usr/lib | sort -rh | head
2886/usr/lib
950 /usr/lib/x86_64-linux-gnu
634 /usr/lib/modules
315 /usr/lib/modules/5.10.0-22-amd64
315 /usr/lib/modules/5.10.0-21-amd64
286 /usr/lib/libreoffice
215 /usr/lib/firefox-esr
211 /usr/lib/libreoffice/program
175 /usr/lib/jvm/java-11-openjdk-amd64
175 /usr/lib/jvm


Please run the above commands on one of your Debian 11 instances and 
reply with the console session.



David

Re: disk usage for /usr/lib on bullseye

[Brad Rogers]

On Mon, 1 May 2023 11:06:25 -0600
Charles Curley  wrote:

Hello Charles,

>to not purge the two most recent kernel packages, and especially not
>the kernel you are currently running on.

If memory serves, should one try to do that, warnings are issued.

Not quite HAL in "2001, A Space Odyssey", but near enough.   :-)

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
What do you call that noise, that you put on?
This Is Pop - XTC


pgpYSyo6Nt_c5.pgp
Description: OpenPGP digital signature

Re: No fool like an old fool (debian installation probs)

[David Christensen]

On 4/30/23 18:11, DdB wrote:

Hello list,

after receiving so much good advice, i finally made up my mind and began
playing through the installation (debian bullseye, current stable) in my
simulation-VM in order to learn about the pitfalls to avoid. After more
than a dozen tries, i am running out of fuel, because i am continuously
running into problems, that i would have preferred to circumvent.

At first, i picked a debian (debian-11.6.0-amd64-DVD-1.iso), as the 11.7
release was not yet out), and installed from there, choosing the Expert
Install. The main reason was, that i was expecting to be invited into
customizing the system picking software to install by hand.

But at first, i ran into a multitude of problems with the partitioning
tool, even though the system was already properly configured (GPT +
EFISYS + OS + Swap + several other partitions booting in UEFI style).

For example, when i allow the use of the swap partition, it gets
reformatted and another PARTUUID is assigned to it, leading to failures
booting other systems from that disk. OTOH Disallowing its use for the
time being leads to install failures due to the 4GB of RAM apparently
not being enough for that VM.

Another problem, similar but distinctly different happens around the OS
partition. Whenever i gave it to the installer, it reformatted it while
changing the PARTUUID, again leading to failures in the boot process of
the other partitions... Until i discovered this workaround: Assign the
partition to ext4 and the mountpoint / but not allowing to delete its
content (as that would induce the reformatting). Instead, after
finishing partitioning, i asked for a shell and from there manually
deleted ONLY THE DATA from the partition(s) used. Then installation
progressed further.

BTW: Apparently, this was the only way to keep the PARTUUID, as deleting
the data by overwriting with zeroes lead to the installer overwriting
the fs structures making another mke2fs necessary.

But the worst of all, was the software selection: Even though i asked
for debconf priority low, i got only a few checkboxes to pick from. And
choosing GNOME did automatically install software i neither need nor want.

But omitting GNOME from the list lead to a system failing to boot with
tons of messages stating the absense of all kind of gnome parts.

So, just in order to make some progress, i had to willingly and
temporarily kill the bootability of other partitions in order to have
the install terminate without failures.

At that point, i decided to try the netinstall, as it is now available
with release 11.7 and i did expect there to be more choices. And when
even that one failed to boot without GNOME, i even did check the
sha512sum to make sure, i was using the proper one. - I did!

Now, i am confused. Many years ago, the expert installer was very
difficult to use and did provide very many choices (and liberties to
spoil the fun). Now, i dont seem to be able at coming to the stage,
where i can seriously test more complicated things (like multi-boot,
zfs, and other things) that make up my current host in its buster version.

It is quite obvious, that i am lacking SOME kind of understanding,
because what i am trying to accomplish should really be quite easy, but
i am only experiencing troubles.

Oh, as a side note: As a nicety of my setup, i can use bash scripts,
that work well from my main OS, or from the simulation VM which can be
used to test functionality before it is rolled out to the host. That is
why, i am relying/insisting on absolutely identical PARTUUIDs inside
that VM.

Now, i am really curious as to how to get to a proper system without
having to go through the baby-steps beginning with debootstrap, and all
the millions of configuration steps, that i did not even bother to list.

I am really interested to understand, in which way i am creating all
those problems for myself. Could it be related to the fact, that i am
accessing the net fom a VPN? - I don't think so.

Any suggestions/questions/hints from the power-users in here?
... would be wildly appreciated ...
DdB



On 5/1/23 04:08, DdB wrote:
> Am 01.05.2023 um 10:23 schrieb Michel Verdier:

>> To install without gnome I select the task ssh server then after I
>> manually select what I want, and a WM if needed.
>>
>>
> Thank you for encouraging me. A good night sleep did help as well.
> Following your advice, i retried a fresh install. This time round, i did
> permit the reformatting of everything, and just noted a new todo to
> resolve that later. But ...
>
> The install succeeded, an sshd is running ON a machine with GNOME and
> all its (un-) pleasant surprises like: firefox, openoffice, and much
> more. But i know for sure, that i deselected it and only left Desktop +
> ssh server. I guess, that means, that the installer chose gnome as its
> preferred desktop.
>
> Ok, i will go on from here, as i certainly want a DE + GNOME, only the
> standard tools, i wouldnt have all of them.
>
> ==

Re: AW: Was it a good idea to buy an Epson printer?

[Andrew M.A. Cater]

On Fri, Apr 28, 2023 at 10:20:59AM +, Schwibinger Michael wrote:
> Good afternoon
> 
> 
> Thank You for help.
> 
> Its Debian 11 LXDE
> 

In English locale:

Preferences -> Print Settings from the menus
> 
> I did not find a button:
> 
> Install printer.
> 
> 
> Regards
> Sophie
> 
> 
> 
> Von: Andrew M.A. Cater 
> Gesendet: Montag, 24. April 2023 21:41
> An: debian-user@lists.debian.org 
> Betreff: Re: Was it a good idea to buy an Epson printer?
> 
> On Mon, Apr 24, 2023 at 01:36:24PM +, Schwibinger Michael wrote:
> >
> >
> > Good afternoon
> >
> > Thank You
> > Was it a good idea to buy EPSON?
> >
> > Regards
> > Sophie
> >
> 
> Good evening, Sophie
> 
> Many printers can be supported in Debian: one way or another we should be
> able to help you.
> 
> Since we cannot be with you to see exactly what you are doing: could you
> please answer some questions for the list to help us to help you?
> 
> Just to check: Exactly which version of Debian are you using?
> 
> You can find this in the file /etc/debian_version
> 
> Which desktop environment are you running?
> 
> GNOME or KDE or one of the others?
> 
> Many desktop environments have Settings or something similar gathering
> together tools to set up screens, sound and printers.
> 
> Thank you for your help in helping us :)
> 
> With best wishes
> 
> Andy Cater
> or something similar which gathers together tools to set up sound, screens
> and so on.
> 
> >
> >
> > 
> > Von: The Wanderer
> > Gesendet: Freitag, 14. April 2023 23:28
> > Bis: debian-user@lists.debian.org
> > Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are 
> > using the wrong driver
> >
> > On 2023-04-14 at 19:17, Brian wrote:
> >
> > > On Fri 14 Apr 2023 at 19:06:08 -0400, The Wanderer wrote:
> > >
> > >> On 2023-04-14 at 18:52, Brian wrote:
> >
> > >>> The EPSON ET M 1120 doesn't exist. Do we have to guess its
> > >>> correct name as well as any other relevant information?
> > >>
> > >> When I searched for
> > >>
> > >> Epson ET M 1120
> > >>
> > >> I got a suggestion that I may have meant "M1120" instead of the
> > >> last two search terms, and hits for the "Epson EcoTank ET M1120"
> > >> and/or "Epson EcoTank M1120", which look to be different names for
> > >> the same model and to be a fairly clear match.
> > >>
> > >> While, yes, specifying the exact name clearly would be preferable,
> > >> this is far from unreasonably difficult to figure out.
> > >
> > > I decided to take your signature as a template for my original
> > > response :).
> >
> > I can respect that!
> >
> > >>> I haven't a clue what you are going on about here. Shift-L in
> > >>> mutt was used at this end.
> > >>
> > >> Your replies to the OP have been fine, AFAIK. The OP's message was
> > >> itself a reply, as can be seen by looking at its headers
> > >> (In-Reply-To: and References:), but was otherwise presented as if
> > >> it had been the start of a new thread; that is not fine, because it
> > >> hides the "new thread" inside of the existing one, at least for
> > >> anyone using a threaded view of the list of messages.
> > >
> > > That's an issue for the OP, not me.
> >
> > Certainly. I was meaning that bullet-point item as an addendum to the
> > list you provided (which I understand to have been aimed at the OP), not
> > as something directed at you.
> >
> > --
> >The Wanderer
> >
> > The reasonable man adapts himself to the world; the unreasonable one
> > persists in trying to adapt the world to himself. Therefore all
> > progress depends on the unreasonable man. -- George Bernard Shaw
> >
> 

Re: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 13:03:50 -0400, gene heskett wrote:

> On 5/1/23 12:30, Brian wrote:
> > 
> > Assuming your buster machines (which are working) have similar setups to 
> > bpi51,
> > you couls try the two commands (and all the others in this thread) on one of
> > those.
> > 
> one of those machines reports this for the -l option:
> 
> gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l
> PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive
> FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6
> 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm
> CUSTOM1 CUSTOM2 CUSTOM3
> BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK
> ENVTHIN RECYCLED
> InputSlot/InputSlot: MANUAL *TRAY1
> Duplex/Duplex: DuplexTumble *DuplexNoTumble None
> Resolution/Resolution: 300dpi *600dpi 2400x600dpi
> TonerSaveMode/Toner Save: *OFF ON
> Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes

Looks reasonable. A similar command on the server should give a similar output.

The reason 'lp -d HLL2320D_coyote printer.cfg' failed is because CUPS is unable
to query the HLL2320D_coyote printer for its attributes. Printing from anything
else, such as Firefox, will also fail. CUPS on the bullseye machine appears to
be broken.

[...]

A possible way forward is to execute

  sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E 
-m raw

and try

  lp -d HLL2320D-RAW printer.cfg

-- 
Brian.

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 12:30, Brian wrote:

On Mon 01 May 2023 at 11:39:29 -0400, gene heskett wrote:


On 5/1/23 11:28, Brian wrote:

On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote:


On 5/1/23 10:40, Brian wrote:


[...]


Your printing situation appears to be a sane one, so now for a test. Do

 lp -d HLL2320D_coyote ANY_FILE_YOU_WANT


Is not working, shell appears frozen but eventually returns:
gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
lp: The printer or class does not exist.


But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e'
and 'sudo lpinfo -v'. Give

lpoptopns -p HLL2320D_coyote

gene@bpi51:~$ lpoptions -p HLL2320D_coyote
device-uri=ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
printer-info='HLL2320D @ coyote' printer-make-and-model='Brother HL-L2320D
series' printer-type=25202710


The print queue specified by -p is queried for some information about itself.
Its reponse is given and it seems a very reasonable one.


lpoptions -p HLL2320D_coyote -l

gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l
lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class
does not exist.


The -l option asks the queue for the specific options it offers. The response
indicates something wrong with CUPS on bpi51. I haven't any problem when doing
this and getting sensible outputs on my Debian unstable machine.


Which isn't quite a 1:1 comparison as that will be bookworm shortly.

Or, should I update the bullseyes to unstable? IDK and I'm not even sure 
how...



Assuming your buster machines (which are working) have similar setups to bpi51,


Which is a bullseye machine. And has a totally different content to the 
/etc/cups directory as shown by my last post, much more complex on the 
bullseye installs that don't work.



you couls try the two commands (and all the others in this thread) on one of
those.

I'd think I could start by comparing cupsd.conf's, but miss And I can't 
see the trees for all this forest in the way in both, but missing is a 
client.conf. I think... But that is probably whats wrong, me thinking.


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: disk usage for /usr/lib on bullseye

[Charles Curley]

On Mon, 1 May 2023 13:51:06 +
Bonno Bloksma  wrote:

> Guessing on what I see these are libraries for older kernel versions.
> I usually clean up older kernel versions by using # apt autoremove"
> All 3 servers have 1 older kernel version installed according to apt
> autoremove.

Autoremove removes packages, it does not purge. The difference is that
remove leaves configuration files in place. So you have a tedious bit
of "apt purge linux-image-… [linux-image-…]" etc. ahead. Just be sure
to not purge the two most recent kernel packages, and especially not
the kernel you are currently running on.


> 
> 
> Why is this stuff there? Can I delete it?
> If I can delete it, is there a proper way to clean it up or do I just
> rm /usr/lib/modules/5.10.0- for the older kernels?

See above.

I conjecture that the reason updating the kernel removes rather than
purges old kernels is in case the user has a custom kernel and wishes
to preserve those customizations.

-- 
Does anybody read signatures any more?

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

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 12:30, Brian wrote:

On Mon 01 May 2023 at 11:39:29 -0400, gene heskett wrote:


On 5/1/23 11:28, Brian wrote:

On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote:


On 5/1/23 10:40, Brian wrote:


[...]


Your printing situation appears to be a sane one, so now for a test. Do

 lp -d HLL2320D_coyote ANY_FILE_YOU_WANT


Is not working, shell appears frozen but eventually returns:
gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
lp: The printer or class does not exist.


But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e'
and 'sudo lpinfo -v'. Give

lpoptopns -p HLL2320D_coyote

gene@bpi51:~$ lpoptions -p HLL2320D_coyote
device-uri=ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
printer-info='HLL2320D @ coyote' printer-make-and-model='Brother HL-L2320D
series' printer-type=25202710


The print queue specified by -p is queried for some information about itself.
Its reponse is given and it seems a very reasonable one.


lpoptions -p HLL2320D_coyote -l

gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l
lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class
does not exist.


The -l option asks the queue for the specific options it offers. The response
indicates something wrong with CUPS on bpi51. I haven't any problem when doing
this and getting sensible outputs on my Debian unstable machine.

Assuming your buster machines (which are working) have similar setups to bpi51,
you couls try the two commands (and all the others in this thread) on one of
those.


one of those machines reports this for the -l option:

gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l
PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive 
FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 
B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 
197x273mm CUSTOM1 CUSTOM2 CUSTOM3
BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK 
ENVTHIN RECYCLED

InputSlot/InputSlot: MANUAL *TRAY1
Duplex/Duplex: DuplexTumble *DuplexNoTumble None
Resolution/Resolution: 300dpi *600dpi 2400x600dpi
TonerSaveMode/Toner Save: *OFF ON
Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes

the diff between a working buster from an ls -l /etc/cups showing:
gene@GO704:~/linuxcnc/src$ ls -l /etc/cups
total 64
-rw-r--r-- 1 root root 27303 Apr 10  2019 cups-browsed.conf
-rw-r--r-- 1 root root  6402 Feb 26 15:05 cupsd.conf
-rw-r--r-- 1 root root  2923 May 23  2022 cups-files.conf
drwxr-xr-x 2 root lp4096 May  1 00:00 ppd
-rw--- 1 root lp1882 May  1 00:00 printers.conf
-rw--- 1 root lp 111 May  1 00:00 printers.conf.O
drwx-- 2 root lp4096 May 23  2022 ssl
-rw-r- 1 root lp 387 May  1 00:00 subscriptions.conf
-rw-r- 1 root lp  93 May  1 00:00 subscriptions.conf.O
which works fine, And a non-working bullseye:
gene@bpi51:~$ ls -l /etc/cups/
total 100
-rw--- 1 root lp 111 Dec  2 23:13 classes.conf
-rw-r--r-- 1 root root 30436 Mar 14  2022 cups-browsed.conf
-rw-r--r-- 1 root root  6456 Oct 15  2022 cupsd.conf
-rw-r--r-- 1 root root  3047 May 23  2022 cups-files.conf
-rw-r--r-- 1 root root 10982 Jan  2  2021 cups-pdf.conf
drwxr-xr-x 2 root root  4096 May 23  2022 interfaces
drwxr-xr-x 2 root lp4096 Dec  2 23:13 ppd
-rw--- 1 root lp 529 May  1 10:37 printers.conf
-rw--- 1 root lp 529 May  1 10:36 printers.conf.O
-rw-r--r-- 1 root root   240 Oct 15  2022 raw.convs
-rw-r--r-- 1 root root   211 Oct 15  2022 raw.types
-rw-r--r-- 1 root root   142 May 23  2022 snmp.conf
drwx-- 2 root lp4096 May 23  2022 ssl
-rw-r- 1 root lp 524 May  1 00:00 subscriptions.conf
-rw-r- 1 root lp 234 May  1 00:00 subscriptions.conf.O

So call me puzzled. I've been called worse.;o)>


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: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 11:39:29 -0400, gene heskett wrote:

> On 5/1/23 11:28, Brian wrote:
> > On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote:
> > 
> > > On 5/1/23 10:40, Brian wrote:
> > 
> > [...]
> > 
> > > > Your printing situation appears to be a sane one, so now for a test. Do
> > > > 
> > > > lp -d HLL2320D_coyote ANY_FILE_YOU_WANT
> > > > 
> > > Is not working, shell appears frozen but eventually returns:
> > > gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
> > > lp: The printer or class does not exist.
> > 
> > But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e'
> > and 'sudo lpinfo -v'. Give
> > 
> >lpoptopns -p HLL2320D_coyote
> gene@bpi51:~$ lpoptions -p HLL2320D_coyote
> device-uri=ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
> printer-info='HLL2320D @ coyote' printer-make-and-model='Brother HL-L2320D
> series' printer-type=25202710

The print queue specified by -p is queried for some information about itself.
Its reponse is given and it seems a very reasonable one.

> >lpoptions -p HLL2320D_coyote -l
> gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l
> lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class
> does not exist.

The -l option asks the queue for the specific options it offers. The response
indicates something wrong with CUPS on bpi51. I haven't any problem when doing
this and getting sensible outputs on my Debian unstable machine.

Assuming your buster machines (which are working) have similar setups to bpi51,
you couls try the two commands (and all the others in this thread) on one of
those.

-- 
Brian.

Changing TTL after socket is connected

[Tim Woodall]

Hi,

If I have a SOCK_STREAM that is connected and working, is/should it be
possible to change the TTL before sending the next packet? (C++
applicatiom)

If I have to I'll resort to SOCK_RAW, but I don't want to have to deal
with all of the required headache of setting up a TCP connection so I
can mangle the TTL on a single packet if I don't need to.

My testing suggests that I cannot change the TTL of a connected socket -
but I'm not sure if that's because I cannot do this or whether it's
because I'm doing something wrong, this isn't something I've attempted
before...

setsockopt(sock, IPPROTO_IP, IP_TTL, &ttl, sizeof(ttl)) succeeds, but
setting a ttl of 1 - when the target is 15 hops away, and the packet
still gets there!


Tim.

Re: disk usage for /usr/lib on bullseye

[David Wright]

On Mon 01 May 2023 at 13:51:06 (+), Bonno Bloksma wrote:

Hmm, that took a long time to get posted.

> On my "new" Bullseye machines the root volume starts to fill up. The cause 
> seems to be the /usr/lib folder.
> On my older Buster (10.13) machine the total /usr directory is 701M, the 
> /usr/lib folder is 260M
> In my /usr/lib folder on Buster is NO /usr/lib/modules folder
> 
> On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have 
> been operating for a while and 1+G on a machine that has been operating for a 
> shorter while.

I wonder whether you have a problem with usrmerge.
What does this show:

  $ ls -ld /lib*
  lrwxrwxrwx 1 root root  7 Apr 16  2022 /lib -> usr/lib
  lrwxrwxrwx 1 root root  9 Apr 16  2022 /lib32 -> usr/lib32
  lrwxrwxrwx 1 root root  9 Apr 16  2022 /lib64 -> usr/lib64
  lrwxrwxrwx 1 root root 10 Apr 16  2022 /libx32 -> usr/libx32
  $ 

  $ namei -l /usr/lib/modules/5.10.0-22-amd64/
  f: /usr/lib/modules/5.10.0-22-amd64/
  drwxr-xr-x root root /
  drwxr-xr-x root root usr
  drwxr-xr-x root root lib
  drwxr-xr-x root root modules
  drwxr-xr-x root root 5.10.0-22-amd64
  $ 

Cheers,
David.

Re: disk usage for /usr/lib on bullseye

[Tixy]

On Mon, 2023-05-01 at 13:51 +, Bonno Bloksma wrote:
[...]
> On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have 
> been operating for a while and 1+G on a machine that has been operating for a 
> shorter while.
> 
> The cause seems to be the folder /usr/lib/modules# 
> linams:/usr/lib/modules# du * -sh
> 4.7M    5.10.0-10-amd64
> 4.7M    5.10.0-11-amd64
> 4.7M    5.10.0-12-amd64
> 4.7M    5.10.0-13-amd64
> 4.7M    5.10.0-15-amd64
> 4.7M    5.10.0-16-amd64
> 309M    5.10.0-18-amd64
> 309M    5.10.0-19-amd64
> 309M    5.10.0-20-amd64
> 309M    5.10.0-21-amd64
> 309M    5.10.0-22-amd64
> 4.7M    5.10.0-7-amd64
> 4.7M    5.10.0-8-amd64
> 4.7M    5.10.0-9-amd64

I think I see the same issue. I just looked at /usr/lib/modules and see
one extra directory for kernel that isn't installed (5.10.0-18-amd64).
Because this issue seemed familiar I looked at my bash command history
and that has me cd'ing into that directory and doing a du command there
and then deleting stuff. So I guess I've also resorted to manually
cleaning it up in the past.

-- 
Tixy

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 11:28, Brian wrote:

On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote:


On 5/1/23 10:40, Brian wrote:


[...]


Your printing situation appears to be a sane one, so now for a test. Do

lp -d HLL2320D_coyote ANY_FILE_YOU_WANT


Is not working, shell appears frozen but eventually returns:
gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
lp: The printer or class does not exist.


But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e'
and 'sudo lpinfo -v'. Give

   lpoptopns -p HLL2320D_coyote

gene@bpi51:~$ lpoptions -p HLL2320D_coyote
device-uri=ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups 
printer-info='HLL2320D @ coyote' printer-make-and-model='Brother 
HL-L2320D series' printer-type=25202710



   lpoptions -p HLL2320D_coyote -l

gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l
lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or 
class does not exist.






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: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 10:56:00 -0400, gene heskett wrote:

> On 5/1/23 10:08, David Wright wrote:
> > On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote:
> > > > lpinfo -v
> > > gene@bpi51:~$ lpinfo -v
> > > -bash: lpinfo: command not found
> > > gene@bpi51:~$ sudo apt install lpinfo
> > > Reading package lists... Done
> > > Building dependency tree... Done
> > > Reading state information... Done
> > > E: Unable to locate package lpinfo
> > 
> > You need root:
> > 
> ># lpinfo -v
> >network beh
> >network lpd
> >file cups-brf:/
> >network socket
> >network ipps
> >network https
> >network ipp
> >network http
> >file cups-pdf:/
> >network 
> > dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771
> >network ipp://Brother%20HL-L2390DW._ipp._tcp.local/
> >network lpd://BRW90324B75E771/BINARY_P1
> >#
> > 
> > Cheers,
> > David.
> > 
> > .
> Ah so
> gene@bpi51:~$ sudo lpinfo -v
> [sudo] password for gene:
> Sorry, try again.
> [sudo] password for gene:
> network beh
> network socket
> network http
> network ipps
> network lpd
> network https
> network ipp
> file cups-brf:/
> file cups-pdf:/
> network 
> dnssd://Brother%20HL-L2320D%20series%20%40%20coyote._ipp._tcp.local/cups?uuid=391b5af9-9bac-3249-65f0-795f553651fe
> network 
> dnssd://Brother%20MFC-J6920DW%20%40%20coyote._ipp._tcp.local/cups?uuid=831942b6-acfd-3e55-7013-00336f687aa2
> network 
> dnssd://HLL2320D%20%40%20coyote._ipp._tcp.local/cups?uuid=36139eb5-df51-332f-4f80-ebf162ecc0ae
> network 
> dnssd://MFCJ6920DW%20_tray_2%20%40%20coyote._ipp._tcp.local/cups?uuid=58daf55b-1dc3-31b0-7442-4a936bde800c
> 
> Thats better, but does it show "why"

THe network is probed and the dnssd backend of CUPS find the same four printers 
as
'lpsta -l -e' does.

-- 
Brian.

Re: repeat of previous question that has gone unansweredseveraltimes.

[Brian]

On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote:

> On 5/1/23 10:40, Brian wrote:

[...]

> > Your printing situation appears to be a sane one, so now for a test. Do
> > 
> >lp -d HLL2320D_coyote ANY_FILE_YOU_WANT
> > 
> Is not working, shell appears frozen but eventually returns:
> gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
> lp: The printer or class does not exist.

But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e'
and 'sudo lpinfo -v'. Give

  lpoptopns -p HLL2320D_coyote
  lpoptions -p HLL2320D_coyote -l

-- 
Brian.

disk usage for /usr/lib on bullseye

[Bonno Bloksma]

Hi,

On my "new" Bullseye machines the root volume starts to fill up. The cause 
seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M, the 
/usr/lib folder is 260M
In my /usr/lib folder on Buster is NO /usr/lib/modules folder

On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have 
been operating for a while and 1+G on a machine that has been operating for a 
shorter while.

The cause seems to be the folder /usr/lib/modules# 
linams:/usr/lib/modules# du * -sh
4.7M5.10.0-10-amd64
4.7M5.10.0-11-amd64
4.7M5.10.0-12-amd64
4.7M5.10.0-13-amd64
4.7M5.10.0-15-amd64
4.7M5.10.0-16-amd64
309M5.10.0-18-amd64
309M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64
309M5.10.0-22-amd64
4.7M5.10.0-7-amd64
4.7M5.10.0-8-amd64
4.7M5.10.0-9-amd64

And
linutr:/usr/lib/modules# du * -sh
4.7M5.10.0-16-amd64
4.7M5.10.0-17-amd64
309M5.10.0-18-amd64
309M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64

And
lola:/usr/lib/modules# du * -sh
4.7M5.10.0-13-amd64
4.7M5.10.0-19-amd64
309M5.10.0-20-amd64
309M5.10.0-21-amd64
309M5.10.0-22-amd64

Guessing on what I see these are libraries for older kernel versions. I usually 
clean up older kernel versions by using
# apt autoremove"
All 3 servers have 1 older kernel version installed according to apt autoremove.


Why is this stuff there? Can I delete it?
If I can delete it, is there a proper way to clean it up or do I just rm 
/usr/lib/modules/5.10.0- for the older kernels?

Is this a BUG in Bullseye?


p.s. Looking at this I just noticed I need to do an update on lunutr, I will 
dis that right after sending this mail ;-)


Met vriendelijke groet,
Bonno Bloksma
Senior Systeembeheerder


St. Jacobsstraat 400 | 3511 BT | Utrecht
030 - 3036 877 | direct 040-7 999 832
b.blok...@tio.nl | www.tio.nl

Volg ons op Facebook | LinkedIn | Instagram | YouTube 

Re: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 11:03, gene heskett wrote:

On 5/1/23 10:40, Brian wrote:

On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote:


gene@bpi51:~$ lpstat -l -e
Brother_HL_L2320D_series_coyote network none
ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups

Brother_MFC_J6920DW_coyote network none
ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups

HLL2320D_coyote network none
ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups

MFCJ6920DW_tray_2_coyote network none
ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups


There you are! CUPS sees all four print queues shared by coyote. At this
stage we are golden. Note that all four are designated as "network".


PDF permanent ipp://localhost/printers/PDF cups-pdf:/


This is a manual queue (permanent) set up locally on bpi51. It isn't 
of any

further interest.


gene@bpi51:~$ lpstat -a
PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05


You may care to take note that 'lpstat -a' and 'lpstat -t' only show 
local
printers (permanent) and not those that are on the network. That also 
goes

for the Printers section at localhost:631.

Local printers can also be auto-setup by cups-browsed. You do not have it
installed/running. Thar's OK; there isn't any obligation (or for that 
matter,
any need) to use it. Having mentioned it, we will now completely put 
it out

of our minds.

gene@bpi51:~$ lpinfo -v
-bash: lpinfo: command not found


sudo lpinfo -v

Your printing situation appears to be a sane one, so now for a test. Do

   lp -d HLL2320D_coyote ANY_FILE_YOU_WANT


Is not working, shell appears frozen but eventually returns:
gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
lp: The printer or class does not exist.



repeat same error if s sudo is put in front of it.


Cheers, Gene Heskett.


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: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 10:40, Brian wrote:

On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote:


gene@bpi51:~$ lpstat -l -e
Brother_HL_L2320D_series_coyote network none
ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups

Brother_MFC_J6920DW_coyote network none
ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups

HLL2320D_coyote network none
ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups

MFCJ6920DW_tray_2_coyote network none
ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups


There you are! CUPS sees all four print queues shared by coyote. At this
stage we are golden. Note that all four are designated as "network".


PDF permanent ipp://localhost/printers/PDF cups-pdf:/


This is a manual queue (permanent) set up locally on bpi51. It isn't of any
further interest.


gene@bpi51:~$ lpstat -a
PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05


You may care to take note that 'lpstat -a' and 'lpstat -t' only show local
printers (permanent) and not those that are on the network. That also goes
for the Printers section at localhost:631.

Local printers can also be auto-setup by cups-browsed. You do not have it
installed/running. Thar's OK; there isn't any obligation (or for that matter,
any need) to use it. Having mentioned it, we will now completely put it out
of our minds.
  

gene@bpi51:~$ lpinfo -v
-bash: lpinfo: command not found


sudo lpinfo -v

Your printing situation appears to be a sane one, so now for a test. Do

   lp -d HLL2320D_coyote ANY_FILE_YOU_WANT


Is not working, shell appears frozen but eventually returns:
gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg
lp: The printer or class does not exist.


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: repeat of previous question that has gone unanswered severaltimes.

[gene heskett]

On 5/1/23 08:56, Brian wrote:

On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote:


avahi-browse -rt _ipp._tcp

gene@bpi51:~$ avahi-browse -rt _ipp._tcp
+   eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer
local
+   eth0 IPv4 Brother MFC-J6920DW @ coyote  Internet Printer
local
+   eth0 IPv4 HLL2320D @ coyote Internet Printer
local
+   eth0 IPv4 MFCJ6920DW _tray_2 @ coyote   Internet Printer
local


You have exactly four (not five or six) print queues manually set up on
the CUPS server coyote (192.168.71.3). It is assumed that when sat at
coyote it is possible to print to any of Brother HL-L2320D series, Brother
MFC-J6920DW, HLL2320D and  MFCJ6920DW _tray_2. Im particular - can you
print to HLL2320D from the server?

[...]


=   eth0 IPv4 HLL2320D @ coyote Internet Printer
local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2"
"UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0"
"adminurl=https://coyote.local.:631/printers/HLL2320D"; "ty=Brother HL-L2320D
for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]


As well as three other printers, the host bpi51 sees the shared HLL2320D @ 
coyote
queue via mDNS/DNS-SD. All is well and good up to now. Let's have

   lpstat -l -e

gene@bpi51:~$ lpstat -l -e
Brother_HL_L2320D_series_coyote network none 
ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups
Brother_MFC_J6920DW_coyote network none 
ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups
HLL2320D_coyote network none 
ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
MFCJ6920DW_tray_2_coyote network none 
ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups

PDF permanent ipp://localhost/printers/PDF cups-pdf:/


   lpstat -a
   lpinfo -v

from bpi51.



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: repeat of previous question that has gone unansweredseveraltimes.

[gene heskett]

On 5/1/23 10:08, David Wright wrote:

On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote:

lpinfo -v

gene@bpi51:~$ lpinfo -v
-bash: lpinfo: command not found
gene@bpi51:~$ sudo apt install lpinfo
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package lpinfo


You need root:

   # lpinfo -v
   network beh
   network lpd
   file cups-brf:/
   network socket
   network ipps
   network https
   network ipp
   network http
   file cups-pdf:/
   network 
dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771
   network ipp://Brother%20HL-L2390DW._ipp._tcp.local/
   network lpd://BRW90324B75E771/BINARY_P1
   #

Cheers,
David.

.

Ah so
gene@bpi51:~$ sudo lpinfo -v
[sudo] password for gene:
Sorry, try again.
[sudo] password for gene:
network beh
network socket
network http
network ipps
network lpd
network https
network ipp
file cups-brf:/
file cups-pdf:/
network 
dnssd://Brother%20HL-L2320D%20series%20%40%20coyote._ipp._tcp.local/cups?uuid=391b5af9-9bac-3249-65f0-795f553651fe
network 
dnssd://Brother%20MFC-J6920DW%20%40%20coyote._ipp._tcp.local/cups?uuid=831942b6-acfd-3e55-7013-00336f687aa2
network 
dnssd://HLL2320D%20%40%20coyote._ipp._tcp.local/cups?uuid=36139eb5-df51-332f-4f80-ebf162ecc0ae
network 
dnssd://MFCJ6920DW%20_tray_2%20%40%20coyote._ipp._tcp.local/cups?uuid=58daf55b-1dc3-31b0-7442-4a936bde800c


Thats better, but does it show "why"

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: Impossible to change ownership of a file to user when user is UID 0

[Jeffrey Walton]

On Mon, May 1, 2023 at 10:50 AM Greg Wooledge  wrote:
>
> On Mon, May 01, 2023 at 04:37:34PM +0200, Pierre Willaime wrote:
> > On this system (not installed by me), my user has an UID and GID of 0 in
> > /etc/passwd. Several users share root privileges like this on the server.
>
> >
> >   root@server:~# chown user /home/user/.ssh/authorized_keys
> >   root@server:~# ls -la /home/user/.ssh/authorized_keys
> >   -rw--- 1 root user 395  1 mai   15:38 .ssh/authorized_keys
>
> Is "user" one of the accounts with UID 0?  If so, this is absolutely
> expected behavior.  ...

Ugh, that sounds like a bad idea.

I'd love to hear the backstory about why that was done.

Jeff

Re: Impossible to change ownership of a file to user when user is UID 0

[Jeffrey Walton]

On Mon, May 1, 2023 at 10:44 AM Pierre Willaime
 wrote:
>
> Hi,
>
> I am unable to connect via SSH without password (ssh-copy-id was launched) to 
> a VM running Debian Stable.
>
> After some investigations, it is most likely a permission issue
>
> May  1 15:32:42 vm sshd[131848]: debug1: trying public key file 
> /home/user/.ssh/authorized_keys
> May  1 15:32:42 vm sshd[131848]: debug1: fd 5 clearing O_NONBLOCK
> May  1 15:32:42 vm sshd[131848]: Authentication refused: bad ownership or 
> modes for directory /home/user
>
> On this system (not installed by me), my user has an UID and GID of 0 in 
> /etc/passwd. Several users share root privileges like this on the server.
>
> After a ssh connexion (it is working with password authentification) done as 
> 'user'
>
> $ ssh user@server
> user@server's password: 
>
> I am directly connected as root
>
> root@server:~# whoami
> root
> root@server:~# su user
> root@server:~# whoami
> root
>
> .ssh files of user directory are owned by root
>
> # ls -la /home/user/.ssh/
> total 4
> drwx-- 2 root user  29  1 mai   15:38 .
> drwxr-xr-x 3 1001 user 106 11 févr. 11:10 ..
> -rw--- 1 root user 395  1 mai   15:38 authorized_keys

Perform a `chown -R user:group /home/user/*`. Then perform a `chmod -R
o-rwx /home/user/.ssh/`. (You only need to remove 'other' access).

> I tried to change the owner of the file authorized_keys (I guess if it 
> matches the user used in ssh connexion command, it will allow the ssh 
> connexion by keys) but chown fails silently.
>
> root@server:~# chown user /home/user/.ssh/authorized_keys
> root@server:~# ls -la /home/user/.ssh/authorized_keys
> -rw--- 1 root user 395  1 mai   15:38 .ssh/authorized_keys
>
> I tried a `chattr -i` on the file, unsuccessfully.
>
> If I launch again ssh-copy-id with root@server instead of user@server, I can 
> connect without password. But I would prefer to connect with my user.
>
> What is my best move here?

Root is usually not allowed to login via ssh. Login as a regular user,
then do something like `sudo -i` or `sudo su -`.

If you want to allow root logins, I believe your sshd_config needs to
be updated. Here's the one I set to disallow root. You should do the
opposite:

$ cat /etc/ssh/sshd_config.d/20-no_root_login.conf
PermitRootLogin no

I also only allow PublicKey methods:
 cat /etc/ssh/sshd_config.d/10-pubkey_auth.conf
# Disable passwords
PasswordAuthentication no
ChallengeResponseAuthentication no
KerberosAuthentication no
KerberosOrLocalPasswd no
GSSAPIAuthentication no
UsePAM no

# Enable public key
PubkeyAuthentication yes

Jeff

Re: Impossible to change ownership of a file to user when user is UID 0

[Greg Wooledge]

On Mon, May 01, 2023 at 04:37:34PM +0200, Pierre Willaime wrote:
> On this system (not installed by me), my user has an UID and GID of 0 in
> /etc/passwd. Several users share root privileges like this on the server.

> 
>   root@server:~# chown user /home/user/.ssh/authorized_keys 
>   root@server:~# ls -la /home/user/.ssh/authorized_keys 
>   -rw--- 1 root user 395  1 mai   15:38 .ssh/authorized_keys

Is "user" one of the accounts with UID 0?  If so, this is absolutely
expected behavior.  You're asking chown to change the owner to UID 0,
and it does so (which is a no-op).  Then you're asking ls to show you
a textual representation of the owner.  Obediently, ls uses the first
account that matches this UID, which happens to be named "root".

Impossible to change ownership of a file to user when user is UID 0

[Pierre Willaime]

Hi,

I am unable to connect via SSH without password (ssh-copy-id was launched) to a 
VM running Debian Stable. 

After some investigations, it is most likely a permission issue

May  1 15:32:42 vm sshd[131848]: debug1: trying public key file 
/home/user/.ssh/authorized_keys
May  1 15:32:42 vm sshd[131848]: debug1: fd 5 clearing O_NONBLOCK
May  1 15:32:42 vm sshd[131848]: Authentication refused: bad ownership or modes 
for directory /home/user

On this system (not installed by me), my user has an UID and GID of 0 in 
/etc/passwd. Several users share root privileges like this on the server.

After a ssh connexion (it is working with password authentification) done as 
'user'

$ ssh user@server
user@server's password: 

I am directly connected as root

root@server:~# whoami
root
root@server:~# su user
root@server:~# whoami
root

.ssh files of user directory are owned by root

# ls -la /home/user/.ssh/
total 4
drwx-- 2 root user  29  1 mai   15:38 .
drwxr-xr-x 3 1001 user 106 11 févr. 11:10 ..
-rw--- 1 root user 395  1 mai   15:38 authorized_keys

I tried to change the owner of the file authorized_keys (I guess if it matches 
the user used in ssh connexion command, it will allow the ssh connexion by 
keys) but chown fails silently.

root@server:~# chown user /home/user/.ssh/authorized_keys 
root@server:~# ls -la /home/user/.ssh/authorized_keys 
-rw--- 1 root user 395  1 mai   15:38 .ssh/authorized_keys

I tried a `chattr -i` on the file, unsuccessfully. 

If I launch again ssh-copy-id with root@server instead of user@server, I can 
connect without password. But I would prefer to connect with my user.

What is my best move here?

Re: repeat of previous question that has gone unanswered severaltimes.

[Brian]

On Mon 01 May 2023 at 09:07:53 -0500, David Wright wrote:

> On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote:
> > >lpinfo -v
> > gene@bpi51:~$ lpinfo -v
> > -bash: lpinfo: command not found
> > gene@bpi51:~$ sudo apt install lpinfo
> > Reading package lists... Done
> > Building dependency tree... Done
> > Reading state information... Done
> > E: Unable to locate package lpinfo
> 
> You need root:
> 
>   # lpinfo -v
>   network beh
>   network lpd
>   file cups-brf:/
>   network socket
>   network ipps
>   network https
>   network ipp
>   network http
>   file cups-pdf:/
>   network 
> dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771
>   network ipp://Brother%20HL-L2390DW._ipp._tcp.local/
>   network lpd://BRW90324B75E771/BINARY_P1

Indeed you do. I forgot that root privilege is required because the USB bus
is probed.

-- 
Brian.

Re: repeat of previous question that has gone unanswered severaltimes.

[Brian]

On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote:

> gene@bpi51:~$ lpstat -l -e
> Brother_HL_L2320D_series_coyote network none
> ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups
>
> Brother_MFC_J6920DW_coyote network none
> ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups
>
> HLL2320D_coyote network none
> ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
>
> MFCJ6920DW_tray_2_coyote network none
> ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups

There you are! CUPS sees all four print queues shared by coyote. At this
stage we are golden. Note that all four are designated as "network".

> PDF permanent ipp://localhost/printers/PDF cups-pdf:/

This is a manual queue (permanent) set up locally on bpi51. It isn't of any
further interest.

> gene@bpi51:~$ lpstat -a
> PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05

You may care to take note that 'lpstat -a' and 'lpstat -t' only show local
printers (permanent) and not those that are on the network. That also goes
for the Printers section at localhost:631.

Local printers can also be auto-setup by cups-browsed. You do not have it
installed/running. Thar's OK; there isn't any obligation (or for that matter,
any need) to use it. Having mentioned it, we will now completely put it out
of our minds.
 
> gene@bpi51:~$ lpinfo -v
> -bash: lpinfo: command not found

sudo lpinfo -v

Your printing situation appears to be a sane one, so now for a test. Do

  lp -d HLL2320D_coyote ANY_FILE_YOU_WANT

-- 
Brian.

Re: repeat of previous question that has gone unanswered severaltimes.

[Jeffrey Walton]

On Mon, May 1, 2023 at 9:40 AM gene heskett  wrote:
>
>  [...]
> >lpinfo -v
> gene@bpi51:~$ lpinfo -v
> -bash: lpinfo: command not found
> gene@bpi51:~$ sudo apt install lpinfo
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> E: Unable to locate package lpinfo

$ apt-cache search lpinfo
$ dpkg -S lpinfo
cups-client: /usr/share/man/de/man8/lpinfo.8.gz
cups-client: /usr/share/man/man8/lpinfo.8.gz
cups-server-common: /usr/share/cups/doc-root/help/man-lpinfo.html
cups-client: /usr/sbin/lpinfo
cups-client: /usr/share/man/fr/man8/lpinfo.8.gz

Re: repeat of previous question that has gone unanswered severaltimes.

[David Wright]

On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote:
> >lpinfo -v
> gene@bpi51:~$ lpinfo -v
> -bash: lpinfo: command not found
> gene@bpi51:~$ sudo apt install lpinfo
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> E: Unable to locate package lpinfo

You need root:

  # lpinfo -v
  network beh
  network lpd
  file cups-brf:/
  network socket
  network ipps
  network https
  network ipp
  network http
  file cups-pdf:/
  network 
dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771
  network ipp://Brother%20HL-L2390DW._ipp._tcp.local/
  network lpd://BRW90324B75E771/BINARY_P1
  # 

Cheers,
David.

Re: repeat of previous question that has gone unanswered severaltimes.

[gene heskett]

On 5/1/23 08:56, Brian wrote:

On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote:


avahi-browse -rt _ipp._tcp

gene@bpi51:~$ avahi-browse -rt _ipp._tcp
+   eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer
local
+   eth0 IPv4 Brother MFC-J6920DW @ coyote  Internet Printer
local
+   eth0 IPv4 HLL2320D @ coyote Internet Printer
local
+   eth0 IPv4 MFCJ6920DW _tray_2 @ coyote   Internet Printer
local


You have exactly four (not five or six) print queues manually set up on
the CUPS server coyote (192.168.71.3). It is assumed that when sat at
coyote it is possible to print to any of Brother HL-L2320D series, Brother
MFC-J6920DW, HLL2320D and  MFCJ6920DW _tray_2. Im particular - can you
print to HLL2320D from the server?


Yes, and from any buster machine on my local network.

[...]


=   eth0 IPv4 HLL2320D @ coyote Internet Printer
local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2"
"UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0"
"adminurl=https://coyote.local.:631/printers/HLL2320D"; "ty=Brother HL-L2320D
for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]


As well as three other printers, the host bpi51 sees the shared HLL2320D @ 
coyote
queue via mDNS/DNS-SD. All is well and good up to now. Let's have

   lpstat -l -e

gene@bpi51:~$ lpstat -l -e
Brother_HL_L2320D_series_coyote network none 
ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups
Brother_MFC_J6920DW_coyote network none 
ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups
HLL2320D_coyote network none 
ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
MFCJ6920DW_tray_2_coyote network none 
ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups

PDF permanent ipp://localhost/printers/PDF cups-pdf:/


   lpstat -a

gene@bpi51:~$ lpstat -a
PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05


   lpinfo -v

gene@bpi51:~$ lpinfo -v
-bash: lpinfo: command not found
gene@bpi51:~$ sudo apt install lpinfo
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package lpinfo



from bpi51.


Thank you Brian

Take care and stay well.

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: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[gene heskett]

On 5/1/23 08:36, Thomas Hochstein wrote:

Greg Wooledge wrote:


If you still have issues with your printer, I strongly advise you to ask
on the German mailing list, or whichever mailing list speaks your primary
language.  I don't think anyone on this list is interested in continuing
to offer help to you.


They started on the German mailing list, about a year ago ...

.
The last epson I had that worked with linux was a 4 color C82, well over 
a decade ago. Then it looks as if they started making windows only 
printers because all the normal printer stuff was moved from the driver 
in the printer and put into the windows driver, leaving only the ability 
to put a drop of the chosen color at the chosen xy spot on the paper in 
the printer.  That and the constant battle to keep the nozzle unclogged 
got tiresome and limited the last printer I bought to about 2 months 
life. So that was replaced by a Brother color laser, which worked well 
for around 4 years, then slowly lost its corona wire voltage, an easy 
enough to diagnose problem for me as I am a CET, but brother refused to 
sell me a board despite the fact that I am a CET, fully capable of 
handling that high voltage item. So I brought home their biggest inkjet. 
That was about 8 years ago, and it is still pumping out full color 
images on paper up to tabloid size. A huge device, its also a scanner 
for 11x17 tabloid. I also have a much faster HLL2320dw a B&W laser that 
does duplex on copy paper at 19 pages a minute. And running on linux, 
using the drivers they supply, both run to their full capabilities.


Obviously I am now a Brother fan and I believe in supporting the makers 
who support us. Glaringly obvious in my previous post. But apparently 
this person doesn't want to admit a mistake was made, and the only way 
to solve it is to run an all windows house at much more cost than buying 
another printer that is supported would be.  Brother's consumables cost 
less per page than epson so you get the difference back over time and 
reams of paper.


This may be a duplicate of what wallmart had for sale at $31.95 3 or 4 
years ago, and which I saw the epson label and drove the cart right on by.


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: Segfaults after upgrade to Debian 11.7 on virtualized systems with AMD Ryzen CPU

[Andreas Haumer]

Hi!

Thank you all for your reply!

Am 01.05.23 um 00:39 schrieb NetValue Operations Centre:
> I've tried downgrading libc (and related packages) to 2.31-13+deb11u5, but no 
> success - still getting segmentation faults. Booting back to the 5.10.0-21 
> kernel seems the only solution at the moment.
> 

I now found out, that the 5.10.0-22 kernel boots fine, if I set the CPU
model manually to "EPYC-Rome" in my VM configuration (I use "virt-manager")

In that case, "virsh dumpxml" tells me about the VM's CPU:

  
EPYC-Rome







  


On the other hand, if I set the CPU model as "copy from host",
booting the 5.10.0-22 kernel results in the reported segfaults.

In that case, "virsh dumpxml" tells me the following:

  
EPYC-Rome
AMD































  

On the host, "lscpu" tells me:

root@pauli:~# lscpu
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   48 bits physical, 48 bits virtual
CPU(s):  32
On-line CPU(s) list: 0-31
Thread(s) per core:  2
Core(s) per socket:  16
Socket(s):   1
NUMA node(s):1
Vendor ID:   AuthenticAMD
CPU family:  25
Model:   33
Model name:  AMD Ryzen 9 5950X 16-Core Processor
Stepping:2
Frequency boost: enabled
CPU MHz: 2200.000
CPU max MHz: 5980,4678
CPU min MHz: 2200,
BogoMIPS:8000.67
Virtualization:  AMD-V
L1d cache:   512 KiB
L1i cache:   512 KiB
L2 cache:8 MiB
L3 cache:64 MiB
NUMA node0 CPU(s):   0-31
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf:  Not affected
Vulnerability Mds:   Not affected
Vulnerability Meltdown:  Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:  Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled 
via prctl
Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
Vulnerability Spectre v2:Mitigation; Retpolines, IBPB conditional, 
IBRS_FW, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext 
fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid 
extd_apicid aperfmperf rapl pni pclmulqdq monit
 or ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt 
aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a 
misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core 
perfctr_nb bpext perfctr_llc mwaitx cpb cat_
 l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp 
vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap 
clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc 
cqm_mbm_total cqm_mbm_local clzero irperf
  xsaveerptr rdpru wbnoinvd arat npt lbrv 
svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter 
pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes 
vpclmulqdq rdpid overflow_recov succor smca fsrm

I still do not see which system component is to blame here exactly, but it 
seems,
there actually is some issue with the current Debian 11.7 5.10.0-22 kernel.

Time to create a Debian bugreport?

Regards

- andreas

-- 
Andreas Haumer
*x Software + Systeme  | mailto:andr...@xss.co.at
Karmarschgasse 51/2/20 | https://www.xss.co.at/
A-1100 Vienna, Austria | Tel: +43-1-6060114-0



OpenPGP_signature
Description: OpenPGP digital signature

Re: repeat of previous question that has gone unanswered several times.

[Brian]

On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote:

> >avahi-browse -rt _ipp._tcp
> gene@bpi51:~$ avahi-browse -rt _ipp._tcp
> +   eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer
> local
> +   eth0 IPv4 Brother MFC-J6920DW @ coyote  Internet Printer
> local
> +   eth0 IPv4 HLL2320D @ coyote Internet Printer
> local
> +   eth0 IPv4 MFCJ6920DW _tray_2 @ coyote   Internet Printer
> local

You have exactly four (not five or six) print queues manually set up on
the CUPS server coyote (192.168.71.3). It is assumed that when sat at
coyote it is possible to print to any of Brother HL-L2320D series, Brother
MFC-J6920DW, HLL2320D and  MFCJ6920DW _tray_2. Im particular - can you
print to HLL2320D from the server?

[...]

> =   eth0 IPv4 HLL2320D @ coyote Internet Printer
> local
>hostname = [coyote.local]
>address = [192.168.71.3]
>port = [631]
>txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2"
> "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" 
> "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
> "product=(Brother HL-L2320D series)" "priority=0"
> "adminurl=https://coyote.local.:631/printers/HLL2320D"; "ty=Brother HL-L2320D
> for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]

As well as three other printers, the host bpi51 sees the shared HLL2320D @ 
coyote
queue via mDNS/DNS-SD. All is well and good up to now. Let's have

  lpstat -l -e
  lpstat -a
  lpinfo -v

from bpi51.

-- 
Brian.

Re: repeat of previous question that has gone unanswered several times.

[Brian]

On Mon 01 May 2023 at 13:41:10 +0200, to...@tuxteam.de wrote:

> On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote:
> 
> [...]
> 
> > Please refrain from polluting the list when you do not get an answer.
> 
> I think repeating a question after a while doesn't count as
> "polluting". That's what debian-user is for, after all.

Indeed. Persistaence has a place and may pay off.

-- 
Brian.

Re: Evolution email (problem?) (IMAP, Gmail, email compacting)

[rhkramer]

Oh, I meant to add that compacting is typically useful when record (email?) 
storage is in something like an mbox file -- it saves the need to rewrite the 
file each time a single file is deleted (for example).  

On the other  hand, with storage in something like mdirr files (right name -- 
one email / record per file) it is not really relevant (unless those records / 
emails are indexed by some other indexing system that stores pointers to all 
of those records).

In (older versions?) of kmail, with mbox storage, compactiing is necessary to 
reclaim unused space after deletions, and there is an option in the context 
menu for (most) kmail folders to initiate compaction.

On Monday, May 01, 2023 08:45:15 AM rhkra...@gmail.com wrote:
> On Sunday, April 30, 2023 06:24:14 PM Default User wrote:
> > > What is 'compacting', what is it meant to do?
> 
> The definition of compacting as I "grew up" with it (not sure where I first
> encountered it is the idea that in some applications, the act of "deleting"
> something doesn't actually delete it from the file, instead it is marked
> for deletion (and no longer visible to the user).
> 
> Compacting actually deletes that thing, and shrinks the file to avoid any
> wasted (empty") space previously used by those deleted things.
> 
> I suspect I first encountered that back in the early days of DOS based
> databases, even prior to dBase II.

-- 
rhk 

| No entity has permission to use this email to train an AI. 

Re: Evolution email (problem?) (IMAP, Gmail, email compacting)

[rhkramer]

On Sunday, April 30, 2023 06:24:14 PM Default User wrote:
> > What is 'compacting', what is it meant to do? 

The definition of compacting as I "grew up" with it (not sure where I first 
encountered it is the idea that in some applications, the act of "deleting" 
something doesn't actually delete it from the file, instead it is marked for 
deletion (and no longer visible to the user).

Compacting actually deletes that thing, and shrinks the file to avoid any 
wasted (empty") space previously used by those deleted things.

I suspect I first encountered that back in the early days of DOS based 
databases, even prior to dBase II.

-- 
rhk 

(sig revised 20230312 -- modified first paragraph, some other irrelevant 
wordsmithing)

| No entity has permission to use this email to train an AI. 

If you reply: snip, snip, and snip again; leave attributions; avoid HTML; 
avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon) 
included at no charge.)  If you revise the topic, change the Subject: line.  
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents 
excepted?) -- make it easier for your reader by various means, including 
liberal use of whitespace (short paragraphs, separated by whitespace / blank 
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and 
references.

If someone has already responded to a question, decide whether any response 
you add will be helpful or not ...

A picture is worth a thousand words.  A video (or "audio"): not so much -- 
divide by 10 for each minute of video (or audio) or create a transcript and 
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental 
disability, or may be showing disrespect for his listeners by not properly 
preparing in advance and thinking before speaking. (That speaker might have 
been "trained" to do this by being interrupted often if he pauses.)  (Remember 
Cicero who did not have enough time to write a short missive.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or 
very low pitched / gravelly voices) (which older people might not be able to 
hear properly) disrespects its listeners.   Likewise if it broadcasts 
extraneous or disturbing sounds (like gunfire or crying), or broadcasts 
speakers using their native language (with or without an overdubbed 
translation).

A person who writes a sig this long probably has issues and disrespects (and 
offends) a large number of readers. ;-)
'

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

[Thomas Hochstein]

Greg Wooledge wrote:

> If you still have issues with your printer, I strongly advise you to ask
> on the German mailing list, or whichever mailing list speaks your primary
> language.  I don't think anyone on this list is interested in continuing
> to offer help to you.

They started on the German mailing list, about a year ago ...

Re: HFLB Holding SA

[steve]

Bonjour Marie,

C'est visé de mon côté, à Olivier de jouer.

  ~ steve ~ 


Le lundi 01 mai 2023 à 08:04, Marie Vazquez a écrit :


  Chère Madame, chers Messieurs,


  Nous avons saisi ce jour le paiement détaillé ci-après par le débit du
  compte de la société citée en objet, soit :


* Fiduciaire Dreyfus et Zurbuchen SA - facture datée du 31.03.2023
  concernant les travaux effectués durant la période allant du 1^er
  janvier au 28 février 2023.

Re: repeat of previous question that has gone unanswered several times.

[tomas]

On Mon, May 01, 2023 at 09:37:59AM +0200, john doe wrote:

[...]

> Please refrain from polluting the list when you do not get an answer.

I think repeating a question after a while doesn't count as
"polluting". That's what debian-user is for, after all.

Cheers
-- 
t


signature.asc
Description: PGP signature

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

[Greg Wooledge]

On Mon, May 01, 2023 at 08:31:11AM +, Schwibinger Michael wrote:
> Good morning
> Thank You for email.
> 
> 
> Plonk!
> 
> Wat is a plonk?
> A bug?

http://www.catb.org/jargon/html/P/plonk.html

It means that person has put you on their ignore list, or killfile, or
whatever it's called in their mail reader.  They have chosen never to
see anything you write, ever again.

If you still have issues with your printer, I strongly advise you to ask
on the German mailing list, or whichever mailing list speaks your primary
language.  I don't think anyone on this list is interested in continuing
to offer help to you.

Re: No fool like an old fool (debian installation probs)

[Greg Wooledge]

On Mon, May 01, 2023 at 01:08:56PM +0200, DdB wrote:
> Am 01.05.2023 um 10:23 schrieb Michel Verdier:
> > Le 1 mai 2023 DdB a écrit :
> > 
> >> But omitting GNOME from the list lead to a system failing to boot with
> >> tons of messages stating the absense of all kind of gnome parts.
> > 
> > To install without gnome I select the task ssh server then after I
> > manually select what I want, and a WM if needed.

I believe Michel actually means "I deselect all of the Debian Desktop
type stuff, and then select ssh server".

> Thank you for encouraging me. A good night sleep did help as well.
> Following your advice, i retried a fresh install. This time round, i did
> permit the reformatting of everything, and just noted a new todo to
> resolve that later. But ...
> 
> The install succeeded, an sshd is running ON a machine with GNOME and
> all its (un-) pleasant surprises like: firefox, openoffice, and much
> more. But i know for sure, that i deselected it and only left Desktop +
> ssh server. I guess, that means, that the installer chose gnome as its
> preferred desktop.

If you leave "Debian Desktop" selected, the installer chooses a Desktop
Environment for you.  And guess which one it chooses by default?  That's
right: GNOME.  Assuming you're using a standard installer image, and
not one that has a DE in its name.

I have no idea why this confusing default auto-selection exists, but
it does.

Re: Evolution email (problem?) (IMAP, Gmail, email compacting)

[tomas]

On Mon, May 01, 2023 at 07:38:45AM +0100, Tixy wrote:
> On Sun, 2023-04-30 at 18:24 -0400, Default User wrote:
> > It does occur to me that Evolution may use the maildir format rather
> > than the mbox format [...]

> I thought we were talking about IMAP protocol access to Google? In
> which case Evolution isn't storing email in any format [1], it's
> accessing it on a remote server [...]

Oh, goody. I only brought mbox up as an attempt to explain how such
a kind of unser interface (mark for deletion, then bulk expunge/
compact/whatyoucallit) might have developed.

After that, users might expect that kind of interface regardless of
the actual storage backend, so many mailers offer it.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Wireshark does not show physical interfaces for capture

[Victor Sudakov]

daven...@tuxfamily.org wrote:

[dd]
> > 
> > I have a vague memory of having to do
> >   sudo dpkg-reconfigure wireshark-common
> > a few years ago before I was able to capture packets without using sudo
> 
> Good memory, actually. The full steps are
> 
> $ sudo dpkg-reconfigure wireshark-common # [1]
> Should non-superusers be able to capture packets => Yes

This interactive step is performed by "apt install wireshark" actually.

> 
> $ sudo usermod -a -G wireshark $USER # [1]
> $ newgrp wireshark

I even did a full logout/login from Mate to make sure my user picks up
the new group.

> $ groups # The output should now include "wireshark" group name

Turns out these steps are not sufficient now.

I wonder if Wireshark uses `dumpcap -D` internally to show the list of
interfaces? I can do this now from my user account:

$ dumpcap -D
1. enp3s0
2. any
3. lo (Loopback)
4. bluetooth-monitor
5. nflog
6. nfqueue
7. dbus-system
8. dbus-session


but still cannot see those interfaces in the Wireshark GUI.


-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet


signature.asc
Description: PGP signature

No fool like an old fool (debian installation probs)

[DdB]

Am 01.05.2023 um 10:23 schrieb Michel Verdier:
> Le 1 mai 2023 DdB a écrit :
> 
>> But omitting GNOME from the list lead to a system failing to boot with
>> tons of messages stating the absense of all kind of gnome parts.
> 
> To install without gnome I select the task ssh server then after I
> manually select what I want, and a WM if needed.
> 
> 
Thank you for encouraging me. A good night sleep did help as well.
Following your advice, i retried a fresh install. This time round, i did
permit the reformatting of everything, and just noted a new todo to
resolve that later. But ...

The install succeeded, an sshd is running ON a machine with GNOME and
all its (un-) pleasant surprises like: firefox, openoffice, and much
more. But i know for sure, that i deselected it and only left Desktop +
ssh server. I guess, that means, that the installer chose gnome as its
preferred desktop.

Ok, i will go on from here, as i certainly want a DE + GNOME, only the
standard tools, i wouldnt have all of them.

==

One explanation of my choice to stick with PARTUUID's:
In my overall stategy of using my computer, i am sometimes copying (dd)
whole partitions into a backup, a secondary partition or a VM, which can
easily lead to difficulties, if the same LABELS were used, which can be
changed, but reside INSIDE the partition itself, whereas PARTUUID's
reside in the GPT, which is not affected on partition copy operations.
Thus my choice was related to convenience, avoiding some adjustments
after partition copy operations. Only the installer interferes with the
so called "persistent" PARTUUID's, which i regard as being offensive (or
ignorant - for that matter).

I am going to fix that later (on my machine), returning to my preferred
fstab format of using PARTUUID whereever appropriate.

Bonne journée
DdB

Re: Wireshark does not show physical interfaces for capture

[Victor Sudakov]

Lee wrote:
> >
> >> >
> >> > However when I startup wireshark from the GUI, it does not show the
> >> > physical interfaces in the list of interfaces to capture from, so I
> >> > cannot really capture anything from the non-root user. When started
> >> > via sudo, it does show enp3s0 and other interfaces and can capture.
> >> >
> >> > What am I missing?
> >>
> >> See if the interfaces have been hidden from the GUI.  eg
> >> $ grep devices_hide .config/wireshark/preferences
> >> capture.devices_hide: any,nflog,nfqueue,dbus-system,dbus-session
> >
> > Nothing much there:
> >
> > $ grep devices_hide .config/wireshark/preferences
> > #capture.devices_hide:
> >
> >>
> >> Or check from the GUI:
> >> Capture / Refresh Interfaces
> >
> > Does not add the NICs to the list.
> >
> >> Capture / Options
> >> select the Input tab and click Manage Interfaces
> >> select the Local Interfaces tab and make sure there's a checkmark
> >> under Show for all the physical interface names
> >
> > I don't see any physical interfaces there, this is all I see:
> > https://ibb.co/190ytwv
> 
> Have you looked at
> https://www.wireshark.org/faq.html#capprobunix

Yes, I have, and I have also read
https://gitlab.com/wireshark/wireshark/-/raw/master/packaging/debian/README.Debian

> 
> I have a vague memory of having to do
>   sudo dpkg-reconfigure wireshark-common
> a few years ago before I was able to capture packets without using sudo

All this command does IMHO is create the "wireshark" group with sufficient
privileges to capture packets. I clearly remember answering "Yes" to
that question while installing Wireshark.

That is why I wrote in my first mail that dumpcap can list interfaces
and capture packets when run from my account:

$ whoami ; dumpcap -D
vas
1. enp3s0
2. any
3. lo (Loopback)
4. bluetooth-monitor
5. nflog
6. nfqueue
7. dbus-system
8. dbus-session
$

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet


signature.asc
Description: PGP signature

Monthly FAQ for Debian-user mailing list (unmodified April 1)

[Andrew M.A. Cater]

Debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics. 

Some guidelines which may help explain how the list works:

* The language on this mailing list is English. There may be other mailing 
  lists that are language-specific, for example, debian-user-french 

* It is common for users to be redirected here from other lists, for example,
  from debian-project. It is also common for people to be posting here when 
  English is not their primary language. Please be considerate.

* The list is a Debian communication forum. As such, it is subject to both 
  the Debian mailing list Code of Conduct and the main Debian Code of Conduct
  https://www.debian.org/MailingLists/#codeofconduct
  https://www.debian.org/code_of_conduct

* This is a fairly busy mailing list and you may have to wait for an
  answer - please be patient. Please post answers back to the list so
  others can benefit; private conversations don't benefit people who
  may be following along on the list or reading the archives later.

* Help and advice on this list is provided by volunteers in their own time.
  It is common for there to be different opinions or answers provided.

 * Please try to stay on topic. Arguments for the sake of it are not
   welcome here. Partisan political / religious / cultural arguments
   do not belong here either. Debian's community is world wide; do not
   assume others will agree with your views or need to read them on a
   Debian list.

* There is an FAQ on the Debian wiki derived from some questions asked on this
  list at https://wiki.debian.org/FAQsFromDebianUser

* One question that comes up on almost all Debian lists from time to time
  is of the form:

  "I have done something wrong / included personal details in an email.
   Could you please delete my name / details / remove the mail"

Practically, this is impossible: the mailing lists are archived, potentially
cached by Google and so on.

Unfortunately, there is nothing much we can do to ensure that all copies
anywhere on the Internet are deleted. Asking to do this may only serve to
draw further attention - the so-called "Streisand effect"
See:  https://en.wikipedia.org/wiki/Streisand_effect

Problems?
=

Complaints about inappropriate behaviour should be referred to the
Debian Community Team .

Inappropriate behaviour on the list may lead to warnings; repeated bad
behaviour may lead to temporary or permanent bans for offenders.

Re: No fool like an old fool (debian installation probs)

[Michel Verdier]

Le 1 mai 2023 DdB a écrit :

> Any suggestions/questions/hints from the power-users in here?
> ... would be wildly appreciated ...

When installing you have to stop on your first problem. The others could
be created from it. It's longer but easier to cope with. So give us full
details on your first problem or choice you don't understand.

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

[Schwibinger Michael]

Good morning
Thank You for email.


Plonk!

Wat is a plonk?
A bug?

Regards
Sophie



Von: Jeffrey Walton 
Gesendet: Samstag, 29. April 2023 11:47
An: Schwibinger Michael 
Cc: debian-user@lists.debian.org 
Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are using 
the wrong driver

On Fri, Apr 14, 2023 at 5:16 PM Schwibinger Michael  wrote:
>
> Good afternoon.
> The new printer is not  working.
> EPSON is saying
> You cant use EPSON with Linux.
>
> Is this true?

Plonk!

Re: No fool like an old fool (debian installation probs)

[Michel Verdier]

Le 1 mai 2023 DdB a écrit :

> But omitting GNOME from the list lead to a system failing to boot with
> tons of messages stating the absense of all kind of gnome parts.

To install without gnome I select the task ssh server then after I
manually select what I want, and a WM if needed.

Re: repeat of previous question that has gone unanswered several times.

[john doe]

On 5/1/23 01:05, gene heskett wrote:

Greetings all;

I have a mixed home network, some buster, some bullseye, all up to date
a/o yesterday.

I have 2 printers shared on this bullseye main box, available as 5 or 6
printers, each configured in cups to do a specific job. Good printers,
both running on brother's own linux drivers for that printer.

All my buster machines can use both of these printers just as if they
were plugged into that machine, but a machine shop full of sawdust and
metal shavings is not a good printer environment, even if there was room
for them, which there isn't.

All of my bullseye machines are locked out, printer screen at
localhost:631 is empty, and no printers can be found and added.

But open a shell, and type "lpstat -t" and it gets the full list of
available printers on that same bullseye machine whose cups output is
empty.

Why?



Please refrain from polluting the list when you do not get an answer.

--
John Doe

Re: repeat of previous question that has gone unanswered several times.

[gene heskett]

On 4/30/23 20:19, Lee wrote:

On 4/30/23, gene heskett  wrote:

Greetings all;

I have a mixed home network, some buster, some bullseye, all up to date
a/o yesterday.

I have 2 printers shared on this bullseye main box, available as 5 or 6
printers, each configured in cups to do a specific job. Good printers,
both running on brother's own linux drivers for that printer.

All my buster machines can use both of these printers just as if they
were plugged into that machine, but a machine shop full of sawdust and
metal shavings is not a good printer environment, even if there was room
for them, which there isn't.

All of my bullseye machines are locked out, printer screen at
localhost:631 is empty, and no printers can be found and added.

But open a shell, and type "lpstat -t" and it gets the full list of
available printers on that same bullseye machine whose cups output is
empty.

Why?


Take a look at
   https://wiki.debian.org/CUPSQuickPrintQueues

The quick ref is to install avahi-utils and run
   avahi-browse -rt _ipp._tcp  | grep URF


had to install it, pulled in 7 other pkgs: then:
gene@bpi51:~$ avahi-browse -rt _ipp._tcp  | grep URF
   txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=831942b6-acfd-3e55-7013-00336f687aa2" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(MFC-J6920DW)" "priority=0" "note=letss see if this works" 
"adminurl=https://coyote.local.:631/printers/Brother_MFC-J6920DW_photo"; 
"ty=Brother MFC-J6920DW CUPS" "rp=printers/Brother_MFC-J6920DW_photo" 
"qtotal=1" "txtvers=1"]
   txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=58daf55b-1dc3-31b0-7442-4a936bde800c" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(MFC-J6920DW)" "priority=0" "note=coyote.den duplex bottom 
tray" "adminurl=https://coyote.local.:631/printers/MFCJ6920DW"; 
"ty=Brother MFC-J6920DW CUPS" "rp=printers/MFCJ6920DW" "qtotal=1" 
"txtvers=1"]
   txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" 
"TLS=1.2" "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(Brother HL-L2320D series)" "priority=0" 
"adminurl=https://coyote.local.:631/printers/HLL2320D"; "ty=Brother 
HL-L2320D for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]
   txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" 
"TLS=1.2" "UUID=391b5af9-9bac-3249-65f0-795f553651fe" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(Brother HL-L2320D series)" "priority=0" "note=floor in den" 
"adminurl=https://coyote.local.:631/printers/Brother_HL-L2320D_series"; 
"ty=Brother HL-L2320D for CUPS" "rp=printers/Brother_HL-L2320D_series" 
"qtotal=1" "txtvers=1"]




If you get a line matching URF the printer supports the AirPrint
service.  Install cups and see if it works (which is all that I needed
to do to get the printer working).  If no, what does


cups already installed as part of armbian


   avahi-browse -rt _ipp._tcp

gene@bpi51:~$ avahi-browse -rt _ipp._tcp
+   eth0 IPv4 Brother HL-L2320D series @ coyote Internet 
Printer local
+   eth0 IPv4 Brother MFC-J6920DW @ coyote  Internet 
Printer local
+   eth0 IPv4 HLL2320D @ coyote Internet 
Printer local
+   eth0 IPv4 MFCJ6920DW _tray_2 @ coyote   Internet 
Printer local
=   eth0 IPv4 Brother HL-L2320D series @ coyote Internet 
Printer local

   hostname = [coyote.local]
   address = [192.168.71.3]
   port = [631]
   txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" 
"TLS=1.2" "UUID=391b5af9-9bac-3249-65f0-795f553651fe" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(Brother HL-L2320D series)" "priority=0" "note=floor in den" 
"adminurl=https://coyote.local.:631/printers/Brother_HL-L2320D_series"; 
"ty=Brother HL-L2320D for CUPS" "rp=printers/Brother_HL-L2320D_series" 
"qtotal=1" "txtvers=1"]
=   eth0 IPv4 Brother MFC-J6920DW @ coyote  Internet 
Printer local

   hostname = [coyote.local]
   address = [192.168.71.3]
   port = [631]
   txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2" 
"UUID=831942b6-acfd-3e55-7013-00336f687aa2" "URF=DM3" 
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" 
"product=(MFC-J6920DW)" "priority=0" "note=letss see if this works" 
"adminurl=https://coyote.local.:631/printers/Brother_MFC-J6920DW_photo"; 
"ty=Brother MFC-J6920DW CUPS" "rp=printers/Brother_MFC-J6920DW_photo" 
"qtotal=1" "txtvers=1"]
=   eth0 IPv4