Re: Boot better have mounted on root or /boot ?

[Andrei POPESCU]

On Jo, 08 apr 21, 08:55:47, Robbi Nespu wrote:
> 
> I use auto partitioning (if not mistaken) and boot mounted on root "/"
> instead of creating own "/boot" partition
> 
> $ df -h /boot/
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda1   110G   62G   43G  60% /
> 
> What actually the best way for boot directory? put on same root directory
> like I have right now or it better to have it own partition?

The "best" way depends a lot on the criteria used to evaluate.

For me the simplicity of having 'boot' on '/' wins in most cases. It 
avoids a lot of issues (like running out of space in /boot) with no 
significant downside I'm aware of.

I've used a separate boot only when there was no way around it, e.g. the 
original RaspberryPi needs a FAT /boot partition.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Andrei POPESCU]

On Mi, 07 apr 21, 23:49:46, deloptes wrote:
> Rainer Dorsch wrote:
> 
> > I have a bullseye system with an on-board Intel sound device and a
> > Logitech USB headset. Everything works perfect, if I boot without the USB
> > headset plugged in. Both devices are detected and I can switch between
> > them as expected. If I boot with the USB headset plugged in, inxi still
> > finds both devices, but pacmd list-cards outputs only the USB headset. I
> > am wondering if that is a pulseaudio feature or a bug.
> 
> don't know if it will help but it is always a good idea to give index > 0 to
> usb audio
> 
> $ cat /etc/modprobe.d/alsa-base.conf
> options snd_hda_intel index=0
> options snd-usb-audio index=1

This is taken care of automatically for most cases:

$ grep snd-usb-audio /lib/modprobe.d/aliases.conf
options snd-usb-audio index=-2


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Andrei POPESCU]

On Mi, 07 apr 21, 20:38:46, Rainer Dorsch wrote:
> Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU:
> > On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote:
> > > Hello,
> > > 
> > > I have a bullseye system with an on-board Intel sound device and a
> > > Logitech
> > > USB headset. Everything works perfect, if I boot without the USB headset
> > > plugged in. Both devices are detected and I can switch between them as
> > > expected. If I boot with the USB headset plugged in, inxi still finds both
> > > devices, but pacmd list-cards outputs only the USB headset. I am wondering
> > > if that is a pulseaudio feature or a bug.
> > 
> > Please post the output of 'aplay -l' in both cases.
> 
> For me it looks identical, but see yourself:

This is ok, at least there doesn't appear to be conflict at ALSA level.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: vlan interface renamed

[deloptes]

Erwan David wrote:

> Le 06/04/2021 à 22:39, deloptes a écrit :

>>> Is it a bug in ifrename ?
>> 
>> if you refer to something like this here
>> https://wiki.debian.org/InterfaceRenaming
>> IMO it means youare living in the past
> 
> I am in the present and the present does not work. That's the problem. A
> logical interface defined and configured in /etc/network/interfaces
> should keep the name defined in the config file and be configured
> according to the configuration.

Sorry for the accusation. On the debian servers I do not use systemd yet. On
the RedHat with systemd the configuration is done in a different way.

Re: Access to PPA's

[Peter Ehlert]

On 4/7/21 2:06 PM, Gary L. Roach wrote:

Hi all,

Some of my most useful software is only available through Ubuntu PPA's 
. I can no longer access PPA's since Debian changed their security 
policies. When trying to access a PPA I get the following:


 The repository 
'http://ppa.launchpad.net/elmer-csc-ubuntu/elmer-csc-ppa/ubuntu 
hirsute Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.



The man page alludes to a couple of different ways to bypass the 
system but really sketchy about how to apply them. There is at least a 
half dozen files that could be involved. Further, there is a note that 
basically says that all of the methods will be discontinued in the 
future.  This would essentially  preclude the use of Ubuntu PPA's. The 
example given is for an elmer-csc package which is one of the most 
powerful opensource MultiPhysics analysis packages available.


Could someone show me how to bypass this security lock.

I have never tried this:
https://wiki.debian.org/CreatePackageFromPPA

in theory it is possible

as others have said it might be better to use Ubuntu
I usually have other systems on separate partitions/drives for those odd 
tasks





Gary R.

Re: Boot better have mounted on root or /boot ?

[Stefan Monnier]

> I use auto partitioning (if not mistaken) and boot mounted on root "/"
> instead of creating own "/boot" partition
>
> $ df -h /boot/
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda1   110G   62G   43G  60% /
>
> What actually the best way for boot directory?

The best way is the one that works.
Apparently your way works, so ...


Stefan

Re: Boot better have mounted on root or /boot ?

[Greg Wooledge]

On Thu, Apr 08, 2021 at 08:55:47AM +0800, Robbi Nespu wrote:
> $ df -h /boot/
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/sda1   110G   62G   43G  60% /
> 
> What actually the best way for boot directory? put on same root directory
> like I have right now or it better to have it own partition?

The only time you *need* to make it a separate partition is when
you're doing certain flavors of disk encryption.  Under those setups,
you need an unencrypted /boot so you can boot and mount your encrypted
root file system.

Re: Access to PPA's

[Jochen Spieker]

Gary L. Roach:
> 
> Some of my most useful software is only available through Ubuntu PPA's . I
> can no longer access PPA's since Debian changed their security policies.
> When trying to access a PPA I get the following:
> 
>  The repository
> 'http://ppa.launchpad.net/elmer-csc-ubuntu/elmer-csc-ppa/ubuntu hirsute
> Release' does not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration
> details.
> 
> 
> The man page alludes to a couple of different ways to bypass the system but
> really sketchy about how to apply them. There is at least a half dozen files
> that could be involved.

I do not find that confusing or sketchy:

| You can force all APT clients to raise only warnings by setting the
| configuration option Acquire::AllowInsecureRepositories to true.
| Individual repositories can also be allowed to be insecure via the
| sources.list(5) option allow-insecure=yes.

You can set Acquire::AllowInsecureRepositories in, for example,
/etc/apt/apt-conf.d/local. This is a standard apt configuration
mechanism, see apt.conf(5). For individual repositories you are referred
to sources.list(5) which mentions this format:

|  deb [ option1=value1 option2=value2 ] uri suite [component1] [component2] […]

So you can just add allow-insecure=yes after the "deb" keyword (and the
following whitespace) like so:

deb [allow-insecure=yes] http://deb.debian.org/debian/ buster main

Do you understand the implications of this? It basically means that apt
will be unable to protect you from installing manipulated packages.
Without a Release file, there is no crpytographic signature that could
ensure that the packages you are installing contain what the PPA author
intends them to contain.

> Further, there is a note that basically says that
> all of the methods will be discontinued in the future.  This would
> essentially  preclude the use of Ubuntu PPA's.

Using packages compiled for a different distribution is always a bad
choice. I understand you are saying it is your only choice, but it is
still bad and has a high chance of leading to problems. You might be
better off using the targeted distribution instead. Not necessarily on
bare metal, maybe a VM, a chroot or a container image serve your
purposes better.

J.
-- 
There is no justice in road accidents.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: Access to PPA's

[Robbi Nespu]

On 4/8/21 5:06 AM, Gary L. Roach wrote:

Hi all,

Some of my most useful software is only available through Ubuntu PPA's . 
I can no longer access PPA's since Debian changed their security 
policies. When trying to access a PPA I get the following:


  The repository 
'http://ppa.launchpad.net/elmer-csc-ubuntu/elmer-csc-ppa/ubuntu hirsute 
Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.



The man page alludes to a couple of different ways to bypass the system 
but really sketchy about how to apply them. There is at least a half 
dozen files that could be involved. Further, there is a note that 
basically says that all of the methods will be discontinued in the 
future.  This would essentially  preclude the use of Ubuntu PPA's. The 
example given is for an elmer-csc package which is one of the most 
powerful opensource MultiPhysics analysis packages available.


Could someone show me how to bypass this security lock.


Gary R.


For long term solution, try asking Debian Science Team[1] for this 
package by sending Request for package / RFP from they source[2], I cc 
the Debian Science Team maintainer mailing list


While waiting, instead of using PPA, how about try using it with docker 
or VM as I saw they said it also available to use on read me file


[1] https://wiki.debian.org/DebianScience
[2] 
https://git.launchpad.net/~elmer-csc-ubuntu/elmercsc/+git/elmer-github-devel/tree/


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Boot better have mounted on root or /boot ?

[Robbi Nespu]

I use auto partitioning (if not mistaken) and boot mounted on root "/" 
instead of creating own "/boot" partition


$ df -h /boot/
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda1   110G   62G   43G  60% /

What actually the best way for boot directory? put on same root 
directory like I have right now or it better to have it own partition?


I am curious..
--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Rainer Dorsch]

Am Mittwoch, 7. April 2021, 20:38:46 CEST schrieb Rainer Dorsch:
> Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU:
> > On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote:
> > > Hello,
> > > 
> > > I have a bullseye system with an on-board Intel sound device and a
> > > Logitech
> > > USB headset. Everything works perfect, if I boot without the USB headset
> > > plugged in. Both devices are detected and I can switch between them as
> > > expected. If I boot with the USB headset plugged in, inxi still finds
> > > both
> > > devices, but pacmd list-cards outputs only the USB headset. I am
> > > wondering
> > > if that is a pulseaudio feature or a bug.
> > 
> > Please post the output of 'aplay -l' in both cases.
> 
> [...]

Small update: I cannot really repro anymore that the on-board sound works, 
even if I boot w/o a headset, I saw this correlation several times in the 
past, but right now, pulseaudio always seems to be unhappy with on-board 
sound, e.g. if I boot without USB headset:

rd@h370:~$ pacmd list-cards
0 card(s) available.
rd@h370:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
rd@h370:~$ 

Any idea or hint is welcome.

Regards
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Rainer Dorsch]

Am Mittwoch, 7. April 2021, 19:47:47 CEST schrieb Andrei POPESCU:
> On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote:
> > Hello,
> > 
> > I have a bullseye system with an on-board Intel sound device and a
> > Logitech
> > USB headset. Everything works perfect, if I boot without the USB headset
> > plugged in. Both devices are detected and I can switch between them as
> > expected. If I boot with the USB headset plugged in, inxi still finds both
> > devices, but pacmd list-cards outputs only the USB headset. I am wondering
> > if that is a pulseaudio feature or a bug.
> 
> Please post the output of 'aplay -l' in both cases.

For me it looks identical, but see yourself:

If USB headset is plugged at boot:

rd@h370:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
rd@h370:~$ 

If USB headset is not plugged at boot, before plugging the headset:

rd@h370:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
rd@h370:~$ 

If USB headset is not plugged at boot, after plugging the headset:

rd@h370:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 1: ALC887-VD Digital [ALC887-VD Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
rd@h370:~$ 

Thanks
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/

Re: .profile not being src'd at login on uptodate buster

[Greg Wooledge]

On Wed, Apr 07, 2021 at 09:41:51PM +, Lee wrote:
> Interesting..  "echo foo" in .bashrc does break scp, but not "echo foo >2"

That redirects to a file named "2".

> .. but that doesn't work for bash, so hhrmm.. > /dev/stderr seems to
> work in all cases:

You wanted >&2 .

Re: Access to PPA's

[Dan Ritter]

Gary L. Roach wrote: 
> Hi all,
> 
> Some of my most useful software is only available through Ubuntu PPA's . I
> can no longer access PPA's since Debian changed their security policies.
> When trying to access a PPA I get the following:
> 
>  The repository
> 'http://ppa.launchpad.net/elmer-csc-ubuntu/elmer-csc-ppa/ubuntu hirsute
> Release' does not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration
> details.
> 
> 
> The man page alludes to a couple of different ways to bypass the system but
> really sketchy about how to apply them. There is at least a half dozen files
> that could be involved. Further, there is a note that basically says that
> all of the methods will be discontinued in the future.  This would
> essentially  preclude the use of Ubuntu PPA's. The example given is for an
> elmer-csc package which is one of the most powerful opensource MultiPhysics
> analysis packages available.
> 
> Could someone show me how to bypass this security lock.

The obvious way is to change over to Ubuntu.

https://wiki.debian.org/DontBreakDebian

there's a bunch of useful advice there.

-dsr-

Re: Sound issue in bulleye with USB Headset and Internal Audio

[deloptes]

Rainer Dorsch wrote:

> I have a bullseye system with an on-board Intel sound device and a
> Logitech USB headset. Everything works perfect, if I boot without the USB
> headset plugged in. Both devices are detected and I can switch between
> them as expected. If I boot with the USB headset plugged in, inxi still
> finds both devices, but pacmd list-cards outputs only the USB headset. I
> am wondering if that is a pulseaudio feature or a bug.

don't know if it will help but it is always a good idea to give index > 0 to
usb audio

$ cat /etc/modprobe.d/alsa-base.conf
options snd_hda_intel index=0
options snd-usb-audio index=1

Re: .profile not being src'd at login on uptodate buster

[Lee]

On 4/7/21, Marco Ippolito  wrote:
>> Where I want output, I protect it with:
>>
>> [ -n "$PS1" ] && printf …
>
> Maybe consider:
>
>   [[ -t 1 ]] && printf ...

Until your script that was started via crontab silently fails.  I
*like* always having error messages enabled.

Lee

Re: .profile not being src'd at login on uptodate buster

[Lee]

On 4/7/21, Greg Wooledge  wrote:
> On Wed, Apr 07, 2021 at 03:16:41PM +, Lee wrote:
>> On 4/7/21, Gene Heskett  wrote:
  <.. snip ..>
>> > Any idea why its not working?
>>
>> A typo in your script?  Add an else clause that shows the error and
>> that will probably show you what's wrong -- eg
>>
>> dir="$HOME/AppImages"
>> if [ -d "$dir" ] ; then
>>   PATH="$dir:$PATH"
>> else
>>   echo "OnNoes!! The directory \"$dir\" does not exist!"
>> fi
>
> Writing error messages to stdout from a .profile isn't generally the
> best idea.  Writing to stderr would be slightly better, but both of
> them should be avoided in a permanent configuration if possible.  Profiles
> that scribble to stdout or stderr during login can break things like scp.

Interesting..  "echo foo" in .bashrc does break scp, but not "echo foo >2"
.. but that doesn't work for bash, so hhrmm.. > /dev/stderr seems to
work in all cases:

$ head -12 .bashrc
lee@izzy:~$ head -12 ~/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

if [ -n "$DEBUG" ]; then
#  don't bother with the rest if I've been here before
   echo "bashrc:  DEBUG already set: $DEBUG" >/dev/stderr
   return
else
   echo ".bashrc: First time here!" >/dev/stderr
fi


> As a *temporary* debugging measure, it's fine.

I don't see any breakage, so I'd disagree with you.  Especially here,
where the test is a belt & suspenders thing because the directory is
always supposed to exist.

Regards,
Lee

Re: .profile not being src'd at login on uptodate buster

[Marco Ippolito]

> Where I want output, I protect it with:
> 
> [ -n "$PS1" ] && printf …

Maybe consider:

[[ -t 1 ]] && printf ...

Access to PPA's

[Gary L. Roach]

Hi all,

Some of my most useful software is only available through Ubuntu PPA's . 
I can no longer access PPA's since Debian changed their security 
policies. When trying to access a PPA I get the following:


 The repository 
'http://ppa.launchpad.net/elmer-csc-ubuntu/elmer-csc-ppa/ubuntu hirsute 
Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.



The man page alludes to a couple of different ways to bypass the system 
but really sketchy about how to apply them. There is at least a half 
dozen files that could be involved. Further, there is a note that 
basically says that all of the methods will be discontinued in the 
future.  This would essentially  preclude the use of Ubuntu PPA's. The 
example given is for an elmer-csc package which is one of the most 
powerful opensource MultiPhysics analysis packages available.


Could someone show me how to bypass this security lock.


Gary R.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Marco Ippolito]

> I decided to let MY initramfs images go on diet
> and added a little script which removes a few drivers that I certainly
> don't need (checked with lsmod) and which contained lots of firmwares
> and similar stuff.

Creative. I liked it. Indeed the ``most'' strategy produces large files.

Re: Firefox profiles on fresh install: default{-esr}

[Marco Ippolito]

> Which Firefox do you have installed?

ii  firefox-esr78.8.0esr-1~deb10u1 amd64Mozilla
Firefox web browser - Extended Support Release (ESR)

ii  firefox-esr-l10n-en-gb 78.8.0esr-1~deb10u1 all  English
(United Kingdom) language package for Firefox ESR

Re: Firefox profiles on fresh install: default{-esr}

[Joe]

On Wed, 7 Apr 2021 21:59:33 +0200
Marco Ippolito  wrote:

> I reinstalled Buster (basic installation with GUI, no additional
> packages chosen) and typed "about:profiles" in Firefox's URL bar.
> 
> It shows two profiles:
> 
> * Profile: default-esr
> * Profile: default
> 
> with different Root Directories.
> 
> What is the purpose of this duality and which Profile should I use?

Which Firefox do you have installed? The up-to-date (as much as it can
be) one or the ESR version? Or both, as I have? On unstable, the
current Firefox 87 is appallingly bad, crashing on about half of all
websites I try. It's so bad, I'm using Chromium or Opera when FF
crashes. Oddly, Epiphany is pretty awful as well, and Konqueror hasn't
worked for me for months.

If you only have one of the two installed, use the appropriate profile.

-- 
Joe

Sound issue in bulleye with USB Headset and Internal Audio

[Rainer Dorsch]

Hello,

I have a bullseye system with an on-board Intel sound device and a Logitech 
USB headset. Everything works perfect, if I boot without the USB headset 
plugged in. Both devices are detected and I can switch between them as 
expected. If I boot with the USB headset plugged in, inxi still finds both 
devices, but pacmd list-cards outputs only the USB headset. I am wondering if 
that is a pulseaudio feature or a bug.

Unfortunately, unplugging the USB device and pulseaudio -k does not fix the 
problem :-/ Any ideas or hints for a workaround to avoid a reboot are very 
welcome.

Here is the output of inxi -F
[...]
Audio: Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel  
  Device-2: Logitech Headset H390 type: USB driver: hid-generic,snd-
usb-audio,usbhid  
  Sound Server: ALSA v: k5.10.0-5-amd64 
[...]

pacmd lists both cards

rd@h370:~$ pacmd list-cards
2 card(s) available.
index: 0
name: 
driver: 
owner module: 6
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xa113 irq 127"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "a348"
device.product.name = "Cannon Lake PCH cAVS"
device.form_factor = "internal"
device.string = "0"
device.description = "Internes Audio"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-stereo: Analog Stereo-Eingabe (priority 65, 
available: no)
output:analog-stereo: Analog Stereo-Ausgabe (priority 6500, 
available: unknown)
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex 
(priority 6565, available: no)
output:iec958-stereo: Digital Stereo (IEC958)-Ausgabe 
(priority 5500, available: unknown)
output:iec958-stereo+input:analog-stereo: Digital Stereo 
(IEC958)-Ausgabe + Analog Stereo-Eingabe (priority 5565, available: no)
output:iec958-ac3-surround-51: Digital Surround 5.1 (IEC958/
AC3)-Ausgabe (priority 300, available: unknown)
output:iec958-ac3-surround-51+input:analog-stereo: Digital 
Surround 5.1 (IEC958/AC3)-Ausgabe + Analog Stereo-Eingabe (priority 365, 
available: no)
output:hdmi-stereo: Digital Stereo (HDMI)-Ausgabe (priority 
5900, available: no)
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI)-
Ausgabe + Analog Stereo-Eingabe (priority 5965, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI)-Ausgabe 
(priority 800, available: no)
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 
(HDMI)-Ausgabe + Analog Stereo-Eingabe (priority 865, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI)-Ausgabe 
(priority 800, available: no)
output:hdmi-surround71+input:analog-stereo: Digital Surround 
7.1 (HDMI)-Ausgabe + Analog Stereo-Eingabe (priority 865, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2)-Ausgabe 
(priority 5700, available: unknown)
output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo 
(HDMI 2)-Ausgabe + Analog Stereo-Eingabe (priority 5765, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3)-Ausgabe 
(priority 5700, available: no)
output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo 
(HDMI 3)-Ausgabe + Analog Stereo-Eingabe (priority 5765, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)-
Ausgabe (priority 600, available: no)
output:hdmi-surround-extra2+input:analog-stereo: Digital 
Surround 5.1 (HDMI 3)-Ausgabe + Analog Stereo-Eingabe (priority 665, 
available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)-
Ausgabe (priority 600, available: no)
output:hdmi-surround71-extra2+input:analog-stereo: Digital 
Surround 7.1 (HDMI 3)-Ausgabe + Analog Stereo-Eingabe (priority 665, 
available: no)
output:hdmi-stereo-extra3: Digital Stereo (HDMI 4)-Ausgabe 
(priority 5700, available: no)
output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo 
(HDMI 4)-Ausgabe + Analog Stereo-Eingabe (priority 5765, available: no)
output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4)-
Ausgabe (priority 600, available: no)
output:hdmi-surround-extra3+input:analog-stereo: Digital 
Surround 5.1 (HDMI 4)-Ausgabe + Analog Stere

Firefox profiles on fresh install: default{-esr}

[Marco Ippolito]

I reinstalled Buster (basic installation with GUI, no additional packages
chosen) and typed "about:profiles" in Firefox's URL bar.

It shows two profiles:

* Profile: default-esr
* Profile: default

with different Root Directories.

What is the purpose of this duality and which Profile should I use?

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Eduard Bloch]

Hallo,
* Marco Ippolito [Wed, Apr 07 2021, 09:20:46AM]:

> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess 
> returned
>  error exit status 1
>  Errors were encountered while processing:
>   initramfs-tools
>
> # df -h /boot
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M 0 100% /boot

That's not much if you have more than a few kernels installed. They are
simply too fat nowadays, too many drivers included. And with the "most"
strategy (which you normally want to have a bootable system), they are
just too fat nowadays. I decided to let MY initramfs images go on diet
and added a little script which removes a few drivers that I certainly
don't need (checked with lsmod) and which contained lots of firmwares
and similar stuff.

So, one _might_ try that but only on your own risk, it could render your
system unbootable. I selected those three because they contributed most
to the overall usage (unpacked initramfs image with unmkinitramfs and
checking with "du|sort -n").

$ cat /etc/initramfs-tools/hooks/zz_drop_stuff
#!/bin/sh

if ! test "$DESTDIR"; then
. /usr/share/initramfs-tools/hook-functions
fi

set -x

#experiments: radeon infiniband lpfc qla2xxx qla4xxx cxgb4 drbd nfs bfa f2fs 
xfs btrfs aic7xxx gma500

for nam in i915 amdgpu ethernet
do
find ${DESTDIR} -name $nam | xargs --no-run-if-empty rm -rv
done

#USEDMODPAT=$(lsmod | grep -v " 0 " | sed -e "s, .*,,;s,_,.,g;s,$,.ko,")
#for pat in $USEDMODPAT
#do
#find ${DESTDIR} | grep "/${pat}$" || echo "WARNING: $pat not found, 
essential module missing!"

That script probably should be set executable.

Best regards,
Eduard.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[David Wright]

On Wed 07 Apr 2021 at 14:02:58 (-0400), Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> > While I'm a big fan of aptitude's patterns it's also not installed by 
> > default. For basic uses 'apt' is fine as well and supports globs:
> > 
> > apt list --installed linux-image-4*
> > 
> > apt purge linux-image-4.9.10-?-amd64
> 
> Remember that you need to quote these globs (at least the special
> characters in them), or else one day you *will* get a nasty surprise
> when one of them matches a file in your current working directory.

And I'm a big fan of -s with commands like these, so that
you know what's going to be changed. Then recall the command
and remove the -s.

I'm also a big fan of   mv -i   rather than rm, for similar
reasons. Remove the files only when you're sure the system
still works without them.

Cheers,
David.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Hans]

Am Mittwoch, 7. April 2021, 19:40:58 CEST schrieb Andrei POPESCU:
Hi Andrei,

yes, you casn do this also with using apt. However, I forgot how to do this, 
it was a litttle bit more complicated.

The syntax was something like "apt-get --purge remove `somestring` " or 
similar. Apt was then using regexp, and the string had to be put in backticks 
or ticks whatever. 

Really, maybe google is telling more. I just forgot, how to do it. 

Last time I used it many years ago and my history is not that long. :-)

Best regards

Hans 

> On Mi, 07 apr 21, 11:11:55, Marco Ippolito wrote:
> > > Hi Marco,
> > 
> > Hi Hans :)
> > 
> > > aptitude purge ~n4.9.10-amd64-*
> > 
> > Hadn't thought of matching a pattern, thanks.
> 
> While I'm a big fan of aptitude's patterns it's also not installed by
> default. For basic uses 'apt' is fine as well and supports globs:
> 
> apt list --installed linux-image-4*
> 
> apt purge linux-image-4.9.10-?-amd64
> 
> 
> (just an example, adjust as needed)
> 
> Hope this helps,
> Andrei

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Greg Wooledge]

On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> While I'm a big fan of aptitude's patterns it's also not installed by 
> default. For basic uses 'apt' is fine as well and supports globs:
> 
> apt list --installed linux-image-4*
> 
> apt purge linux-image-4.9.10-?-amd64

Remember that you need to quote these globs (at least the special
characters in them), or else one day you *will* get a nasty surprise
when one of them matches a file in your current working directory.

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Andrei POPESCU]

On Mi, 07 apr 21, 18:39:21, Rainer Dorsch wrote:
> Hello,
> 
> I have a bullseye system with an on-board Intel sound device and a Logitech 
> USB headset. Everything works perfect, if I boot without the USB headset 
> plugged in. Both devices are detected and I can switch between them as 
> expected. If I boot with the USB headset plugged in, inxi still finds both 
> devices, but pacmd list-cards outputs only the USB headset. I am wondering if 
> that is a pulseaudio feature or a bug.

Please post the output of 'aplay -l' in both cases.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Andrei POPESCU]

On Mi, 07 apr 21, 11:11:55, Marco Ippolito wrote:
> > Hi Marco, 
> 
> Hi Hans :)
> 
> > aptitude purge ~n4.9.10-amd64-* 
> 
> Hadn't thought of matching a pattern, thanks.

While I'm a big fan of aptitude's patterns it's also not installed by 
default. For basic uses 'apt' is fine as well and supports globs:

apt list --installed linux-image-4*

apt purge linux-image-4.9.10-?-amd64


(just an example, adjust as needed)

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Sound issue in bulleye with USB Headset and Internal Audio

[Robbi Nespu]

On 4/8/21 12:39 AM, Rainer Dorsch wrote:

system with an on-board Intel sound device and a Logitech
USB headset. Everything works perfect, if I boot without the USB headset
plugged in. Both devices are detected and I can switch between them a
Try checking "dmesg --human" output, there maybe something from there . 
Try compare it for both situation


--
Email : Robbi Nespu 
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

Re: How to save filtered less results in a file or on stdout

[David Wright]

On Wed 07 Apr 2021 at 08:30:30 (+), Curt wrote:
> On 2021-04-07, David Wright  wrote:
> >> >
> >> > But I don't know how vim would do on-the-fly filtering like
> >> > less can do with & (not being very familiar with vim).
> >> 
> >>  :g/pattern/.w! >> output.txt 
> >> 
> >> I pressed 'v' in less, searched a pattern and wrote the filtered output
> >> to a file using the method above. Seemed to work except the results of
> >> the filtering are not visualized using this method. Of course, you can
> >> visualize them prior to writing the results to a file (:g/pattern).
> >> Maybe a little fastidious.
> >
> > OK, you "pressed 'v' in less", but what was your command line?
> > Without that, it's difficult to replicate your actions.
> 
> I opened a text file in less, pressed 'v' to invoke my default editor (vim),
> filtered for *pattern* and wrote the filtered output to a file 
> (':g/pattern/.w!>> output.txt'), then quit vim and was returned to 
> less again.

There's the difference, then. In your case, most people would
just edit the file by typing   vim filename   rather than
less filename   and then  v.

More of a challenge is the example I gave, since snipped, where
the input has been piped into less, so there is no file to edit.
Here, again, with vim:

  $ sort -m /var/log/kern.log /var/log/user.log | EDITOR=vim less

  Pressing v gives me:

  Cannot edit standard input  (press RETURN)

> Maybe I'm off the mark here. I thought this was what the OP wanted
> to do (but natively, as it were; however, I found no method of
> doing this with less' native commands).

Strictly, neither could I, the problem being that filtering only
affects what you see, and less logs whatever input is *read*.
(There's a hint: when you filter, the line numbers and percentages
displayed are still tied to the input lines, not just the filtered
ones.)

So the best I could manage was to use grep through the shell escape,
to repeat the filtering that the OP found satisfactory in less.
And even that required copy/paste to transfer less's filter to
grep's command line. A word of warning on that: if you habitually
use case-insensitive searching in less (as I do), you may need to
add -i to the grep command to match the pasted string.

Cheers,
David.

Re: .profile not being src'd at login on uptodate buster

[David Wright]

On Wed 07 Apr 2021 at 11:33:02 (-0400), Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 03:16:41PM +, Lee wrote:
> > A typo in your script?  Add an else clause that shows the error and
> > that will probably show you what's wrong -- eg
> > 
> > dir="$HOME/AppImages"
> > if [ -d "$dir" ] ; then
> >   PATH="$dir:$PATH"
> > else
> >   echo "OnNoes!! The directory \"$dir\" does not exist!"
> > fi
> 
> Writing error messages to stdout from a .profile isn't generally the
> best idea.  Writing to stderr would be slightly better, but both of
> them should be avoided in a permanent configuration if possible.  Profiles
> that scribble to stdout or stderr during login can break things like scp.
> 
> As a *temporary* debugging measure, it's fine.

Where I want output, I protect it with:

[ -n "$PS1" ] && printf …

> > note that $HOME/AppImages is listed only once.  That makes sure that
> > your test, path and diagnostic output are all using the same directory
> > name.
> 
> That's good advice in general, yeah.

As so often, we're reduced to guessing, because we're not shown
the *actual* text of the problem, but just some paraphrase.

Cheers,
David.

Re: Buster 10.9 why does apt -y update followed by apt -y upgrade not proceed with upgrades

[Curt]

On 2021-04-07, Keith Christian  wrote:
> Looking on the www, some people recommend using apt-get -y upgrade or
> apt-get -y install to avoid the following message:
>
> "NNN packages can be upgraded. Run 'apt list
> --upgradable' to see them."

That's the message you receive after running 'apt update,' if there are
new packages available for upgrade. 

> Is "apt" unable to perform an "upgrade," or am I missing a command
> line option (e.g. force?)

'apt upgrade' is capable of upgrading; 'apt update' is designed to
download package information from your configured sources. It is usually
advised to run the latter before the former so you'll be working with
the latest package information.

> Thanks.


-- 

[NEWS]: Ludovic Courtès

[Katarina Rostova]

https://gnu.support/richard-stallman/Ludovic-Court%C3%A8s-Guix-is-accusing-Stallman-of-Thoughtcrime-on-his-own-domain-GNU-org.html

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Stefan Monnier]

>> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
>> me (more or less shrunk the initrd images by a factor 3-4).
> Thank you.
> Why did you choose lzma Vs xz or zstd, by the way? Measured diff?

`lzma` and `xz` should be pretty much identical, it was a toss-up (I
have a preference for `lzip` in that space, but it's not available ;-).

`zstd` should compress significantly less (but is significantly faster
both to compress and to uncompress).  I focused on disk space usage
(but I did notice that uncompression takes a non-negligible amount of
time on my old Thinkpad X30 when the initrd image is large (e.g. with
`modules=most`)).

>> > Doubt: after this, by default old kernels will be cleaned up in
>> >Bullseye Vs Buster?
>> I don't think APT ever cleans up old kernels for you (at least in its
>> default configuration).
> Read something about it during the upgrade.. was checking here.

Maybe my info is out of date then.


Stefan

Re: .profile not being src'd at login on uptodate buster

[Gene Heskett]

On Wednesday 07 April 2021 08:28:49 IL Ka wrote:

> > The first of them will be added but not the other if I
> > . .profile
>
> Try to debug it. First of all, run this from the command line:
>
> [  -d "$HOME/AppImages" ] ; echo $?
>
> result should be "0". If not, then there must be some problem with
> this directory (check name, case, etc).
>
> Then try
>
> set -v
> . .profile
>
> and check output carefully
found it, missing $ sign in .profile.
Thanks, I wasn't aware of the +-v effect till now

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: .profile not being src'd at login on uptodate buster

[Greg Wooledge]

On Wed, Apr 07, 2021 at 03:16:41PM +, Lee wrote:
> On 4/7/21, Gene Heskett  wrote:
> > Greetings all;
> >
> > I just installed buster on a Dell 7010 and I have added two stanza's to
> > my .profile, to find a logout and back in does not establish a new
> > $PATH.
> 
> Probably because you've got a window manager that does the login stuph for 
> you..

Display Manager.

> > The first of them will be added but not the other if I
> > . .profile

> > # set PATH so it includes user's private AppImages if it exists
> > if [ -d "$HOME/AppImages" ] ; then
> > PATH="$HOME/AppImages:$PATH"
> > fi
> > =
> > Both directories do exist.

Prove it, by running  ls -ld $HOME/AppImages  in a terminal, and then
pasting the shell prompt, the command, and its output from the terminal
session into the body of the email.  For example,

unicorn:~$ ls -ld $HOME/AppImages
ls: cannot access '/home/greg/AppImages': No such file or directory

> > Any idea why its not working?
> 
> A typo in your script?  Add an else clause that shows the error and
> that will probably show you what's wrong -- eg
> 
> dir="$HOME/AppImages"
> if [ -d "$dir" ] ; then
>   PATH="$dir:$PATH"
> else
>   echo "OnNoes!! The directory \"$dir\" does not exist!"
> fi

Writing error messages to stdout from a .profile isn't generally the
best idea.  Writing to stderr would be slightly better, but both of
them should be avoided in a permanent configuration if possible.  Profiles
that scribble to stdout or stderr during login can break things like scp.

As a *temporary* debugging measure, it's fine.

> note that $HOME/AppImages is listed only once.  That makes sure that
> your test, path and diagnostic output are all using the same directory
> name.

That's good advice in general, yeah.

Re: .profile not being src'd at login on uptodate buster

[Gene Heskett]

On Wednesday 07 April 2021 08:28:49 IL Ka wrote:

> > The first of them will be added but not the other if I
> > . .profile
>
> Try to debug it. First of all, run this from the command line:
>
> [  -d "$HOME/AppImages" ] ; echo $?
>
> result should be "0". If not, then there must be some problem with
> this directory (check name, case, etc).
>
> Then try
>
> set -v
> . .profile
>
> and check output carefully

And it worked. Why? Set +v turns off the echo and it still works.
Go figure.  Thanks Oh wait, go try it on the machine its not woking on.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: .profile not being src'd at login on uptodate buster

[Lee]

On 4/7/21, Gene Heskett  wrote:
> Greetings all;
>
> I just installed buster on a Dell 7010 and I have added two stanza's to
> my .profile, to find a logout and back in does not establish a new
> $PATH.

Probably because you've got a window manager that does the login stuph for you..

> The first of them will be added but not the other if I
> . .profile
>
> The additions to .profile are:
> =
> # set PATH so it includes user's private bin if it exists
> if [ -d "$HOME/bin" ] ; then
> PATH="$HOME/bin:$PATH"
> fi
>
> # set PATH so it includes user's private AppImages if it exists
> if [ -d "$HOME/AppImages" ] ; then
> PATH="$HOME/AppImages:$PATH"
> fi
> =
> Both directories do exist.
>
> Any idea why its not working?

A typo in your script?  Add an else clause that shows the error and
that will probably show you what's wrong -- eg

dir="$HOME/AppImages"
if [ -d "$dir" ] ; then
  PATH="$dir:$PATH"
else
  echo "OnNoes!! The directory \"$dir\" does not exist!"
fi

note that $HOME/AppImages is listed only once.  That makes sure that
your test, path and diagnostic output are all using the same directory
name.

Regards,
Lee

Re: Buster 10.9 why does apt -y update followed by apt -y upgrade not proceed with upgrades

[David Wright]

On Wed 07 Apr 2021 at 08:19:40 (-0600), Keith Christian wrote:
> Looking on the www, some people recommend using apt-get -y upgrade or
> apt-get -y install to avoid the following message:
> 
> "NNN packages can be upgraded. Run 'apt list
> --upgradable' to see them."
> 
> Is "apt" unable to perform an "upgrade," or am I missing a command
> line option (e.g. force?)

I can't understand the connection between your Subject line and the
text of the post. Why not cut and paste something so that we see which
command you're talking about.

Cheers,
David.

Re: .profile not being src'd at login on uptodate buster

[David Wright]

On Wed 07 Apr 2021 at 08:16:43 (-0400), Gene Heskett wrote:
> 
> I just installed buster on a Dell 7010 and I have added two stanza's to 
> my .profile, to find a logout and back in does not establish a new 
> $PATH.
> 
> The first of them will be added but not the other if I
> . .profile
> 
> The additions to .profile are:
> =
> # set PATH so it includes user's private bin if it exists
> if [ -d "$HOME/bin" ] ; then
> PATH="$HOME/bin:$PATH"
> fi
> 
> # set PATH so it includes user's private AppImages if it exists
> if [ -d "$HOME/AppImages" ] ; then
> PATH="$HOME/AppImages:$PATH"
> fi
> =
> Both directories do exist.

Sure?

> Any idea why its not working?

Singular, or plural?

https://lists.debian.org/debian-user/2020/08/msg00183.html

Cheers,
David.

Re: Buster 10.9 why does apt -y update followed by apt -y upgrade not proceed with upgrades

[IL Ka]

works for me:

$ apt -y update && apt upgrade -y

You can also use yes(1):
yes | apt upgrade


On Wed, Apr 7, 2021 at 5:20 PM Keith Christian 
wrote:

> Looking on the www, some people recommend using apt-get -y upgrade or
> apt-get -y install to avoid the following message:
>
> "NNN packages can be upgraded. Run 'apt list
> --upgradable' to see them."
>
> Is "apt" unable to perform an "upgrade," or am I missing a command
> line option (e.g. force?)
>
> Thanks.
>
>

Buster 10.9 why does apt -y update followed by apt -y upgrade not proceed with upgrades

[Keith Christian]

Looking on the www, some people recommend using apt-get -y upgrade or
apt-get -y install to avoid the following message:

"NNN packages can be upgraded. Run 'apt list
--upgradable' to see them."

Is "apt" unable to perform an "upgrade," or am I missing a command
line option (e.g. force?)

Thanks.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Marco Ippolito]

> Hi Marco, 

Hi Hans :)

> aptitude purge ~n4.9.10-amd64-* 

Hadn't thought of matching a pattern, thanks.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Marco Ippolito]

> Recently that was fixed at unstable [1]

I thought I had noticed a warning about this clean-up, but it does not happen
during the upgrade so I run out of space.

> I found a interesting manpage for this issue [2]

Good catch. Functionality now in apt and purge-old-kernels got deprecated.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Marco Ippolito]

> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).

Thank you.

Why did you choose lzma Vs xz or zstd, by the way? Measured diff?

> > Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
> >Buster?
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).

Read something about it during the upgrade.. was checking here.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Erwan David]

Le 07/04/2021 à 14:58, Stefan Monnier a écrit :

What do you recommend I do?


Other than purging old kernels, I also recommend you check

 /etc/initramfs-tools/initramfs.conf

where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
me (more or less shrunk the initrd images by a factor 3-4).


Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
Buster?


I don't think APT ever cleans up old kernels for you (at least in its
default configuration).


 Stefan




I also found that firmware need space, especially amd64 graphics firmware.

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Javier Barroso]

El mié., 7 abr. 2021 14:58, Stefan Monnier 
escribió:

> > What do you recommend I do?
>
> Other than purging old kernels, I also recommend you check
>
> /etc/initramfs-tools/initramfs.conf
>
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).
>

Thanks I will test!

>
> > Doubt: after this, by default old kernels will be cleaned up in Bullseye
> Vs
> >Buster?
>
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).
>

Recently that was fixed at unstable [1]

I found a interesting manpage for this issue [2]

Regards

[1] https://blog.jak-linux.org/2021/02/18/apt-2.2/
[2] https://manpages.debian.org/stretch/byobu/purge-old-kernels.1.en.html

>
>
> Stefan
>
>

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Hans]

Am Mittwoch, 7. April 2021, 14:20:46 CEST schrieb Marco Ippolito:
Hi Marco, 
just get rid of older kernels.


This is may way:


1st, check your running actual kernel:

uname -a

Then check all installed kernel versions:

ls /boot

You will see several kernels. I suppose, apt-get autoremove will not unistall 
them, so 
just use aptitude with the version you want to uninstall:

aptitude purge ~n4.9.10-amd64-* 

This will uninstall all stuff with "4.9.10-amd64-" in its name, this means 
kernel, headers 
and maybe selfcompiled kernel modules like the nvidia-stuff.

Please check before saying "Y" what is going to be uninstalled.

Do this with all the kernels, except the one you are actually running.

This is working well for me, so good luck!

Best regards

Hans





> Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted
> in recovery mode and cleaned up space. Restarted and run:
> 
> # dpkg --configure -a
> Setting up initramfs-tools (0.139) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.139) ...
> update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64
> cat: write error: No space left on device
> update-initramfs: failed for /boot/initrd.img-5.10.0-5-amd64 with 1.
> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess
> returned error exit status 1
>  Errors were encountered while processing:
>   initramfs-tools
> 
> # df -h /boot
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M 0 100% /boot
> 
> What do you recommend I do?
> 
> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>Buster?


-- 
*Hans-J. Ullrich*
zertifizierter Datenschutzbeauftragter
zertifizierter Datenschutzauditor
zertifizierter Penetrationtester
zertifizierter IT-Security Professionell
zertifizierter IT-Forensik Professionell
zertifizierter Network Vulnerabilty Professionell

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Stefan Monnier]

> What do you recommend I do?

Other than purging old kernels, I also recommend you check

/etc/initramfs-tools/initramfs.conf

where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
me (more or less shrunk the initrd images by a factor 3-4).

> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>Buster?

I don't think APT ever cleans up old kernels for you (at least in its
default configuration).


Stefan

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[IL Ka]

>
>
> # df -h /boot
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M 0 100% /boot
>
> What do you recommend I do?
>

1. Autoremove old automatically installed stuff

$ apt purge --autoremove

2. Check packages:

$ dpkg-query --show -f='${Installed-Size}\t${Package}\t${Status}\n' | sort
-nr | head

This will give you the biggest packages (latest field should show if they
are really installed).
Find the one you do not need  (old kernel probably, but be sure not to
delete the current kernel: check "uname -r" !)

Then, purge them:
apt purge "package name"



>
> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>Buster?
>
>
AFAIK yes, when you call "autoremove" , but one prev. kernel left untouched.

see
/etc/apt/apt.conf.d/01autoremove-kernels
or something like this

Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Greg Wooledge]

On Wed, Apr 07, 2021 at 09:20:46AM -0300, Marco Ippolito wrote:
> # df -h /boot
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M 0 100% /boot
> 
> What do you recommend I do?

Purge one or more of your kernel images.

Re: .profile not being src'd at login on uptodate buster

[Greg Wooledge]

On Wed, Apr 07, 2021 at 08:16:43AM -0400, Gene Heskett wrote:
> I just installed buster on a Dell 7010 and I have added two stanza's to 
> my .profile, to find a logout and back in does not establish a new 
> $PATH.

> Any idea why its not working?

How do you log in?  Probably with a GUI, yes?

https://wiki.debian.org/Xsession

Re: .profile not being src'd at login on uptodate buster

[IL Ka]

>
>
> The first of them will be added but not the other if I
> . .profile
>

Try to debug it. First of all, run this from the command line:

[  -d "$HOME/AppImages" ] ; echo $?

result should be "0". If not, then there must be some problem with this
directory (check name, case, etc).

Then try

set -v
. .profile

and check output carefully

No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Marco Ippolito]

Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted in
recovery mode and cleaned up space. Restarted and run:

# dpkg --configure -a
Setting up initramfs-tools (0.139) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64
cat: write error: No space left on device
update-initramfs: failed for /boot/initrd.img-5.10.0-5-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
 error exit status 1
 Errors were encountered while processing:
  initramfs-tools

# df -h /boot
Filesystem  Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  236M  233M 0 100% /boot

What do you recommend I do?

Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
   Buster?

.profile not being src'd at login on uptodate buster

[Gene Heskett]

Greetings all;

I just installed buster on a Dell 7010 and I have added two stanza's to 
my .profile, to find a logout and back in does not establish a new 
$PATH.

The first of them will be added but not the other if I
. .profile

The additions to .profile are:
=
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private AppImages if it exists
if [ -d "$HOME/AppImages" ] ; then
PATH="$HOME/AppImages:$PATH"
fi
=
Both directories do exist.

Any idea why its not working?

Thanks all.

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)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: ubuntu/snap future

[Dan Ritter]

riveravaldez wrote: 
> On Tuesday, April 6, 2021, Brian  wrote:
> > On Tue 06 Apr 2021 at 11:20:58 +0200, Yoann LE BARS wrote:
> >
> > I had occasion to install Zoom a few weeks ago;'snap install zoom-client'.
> > Everything went smoothly and I quite like having this proprietary package
> > strictly confined.
> 
> Hi, I was under the impression that (besides being fully open) Flatpack had
> better confinement method that Canonical's Snap, anybody knows if this is
> correct?


"Two years ago I wrote about then heavily-pushed Flatpak,
self-proclaimed "Future of Apps on Linux". The article
criticized the following three major flows in Flatpak:

Most of the apps have full access to the host system but
users are misled to believe the apps are sandboxed
The flatpak runtimes and apps do not get security updates
Flatpak breaks many aspects of desktop integration"

-- https://flatkill.org/2020/


(the article then says that they fixed some desktop integration
issues)

-dsr-

Re: vlan interface renamed

[Erwan David]

Le 07/04/2021 à 10:54, Reco a écrit :

Hi.

On Wed, Apr 07, 2021 at 09:53:57AM +0200, Erwan David wrote:

How Am I a supposed to have this working ?


By disabling problematic renaming of course:

cat > /etc/systemd/network/00-vlan.link << EOF
[Match]
Type=vlan

[Link]
NamePolicy=kernel
MACAddressPolicy=none
EOF

update-initramfs -k all -u



Alas it does not work. interface is still renamed


And here it gets interesting.
What about:

udevadm test /sys/class/net/rename12

Reco




Thanks it gave the explanation. I had .link units for renaming the 
physical interfaces (a systemd upgrade changed it's scheme thus my 
configuration was useless enp4s0f0 became enp4s0f0np0)


the unit only matched on the mac address

[Match]
MACAddress=24:8a:07:5a:93:9c

[Link]
Name=lan0

But bond interface gets mac address of it's first interface and vlan 
interface of its master interface.
Thus this unit applied to my bond0.4011 and renaming failed because of 
existing interface with name lan0

udevadm told me the unit was applicable.

I changed it to

[Match]
Driver=mlx5_core
MACAddress=24:8a:07:5a:93:9c

[Link]
Name=lan0

and it now works.

Thanks for the help.

--
Erwan

Re: How to save filtered less results in a file or on stdout

[Curt]

On 2021-04-07, David Wright  wrote:
>> >
>> > But I don't know how vim would do on-the-fly filtering like
>> > less can do with & (not being very familiar with vim).
>> 
>>  :g/pattern/.w! >> output.txt 
>> 
>> I pressed 'v' in less, searched a pattern and wrote the filtered output
>> to a file using the method above. Seemed to work except the results of
>> the filtering are not visualized using this method. Of course, you can
>> visualize them prior to writing the results to a file (:g/pattern).
>> Maybe a little fastidious.
>
> OK, you "pressed 'v' in less", but what was your command line?
> Without that, it's difficult to replicate your actions.
>

I opened a text file in less, pressed 'v' to invoke my default editor (vim),
filtered for *pattern* and wrote the filtered output to a file 
(':g/pattern/.w!>> output.txt'), then quit vim and was returned to 
less again.
 
 curty@einstein:~$ cat son.txt 

 J'ai négligé de lire le encore très volumineux--si j'ose dire--fils,
 mais j'ai remarqué depuis le début (un début perdu dans l'obscurité
 croissante du passé) le même phénomène chez moi que vous décrivez.

 Il semble qu'une différence de gamme dynamique entre les deux supports
 (plus large en ce qui concerne le mini par rapport à la TNT et donc
 donnant l'impression d'être moins fort dans le milieu de plage) pourrait
 expliquer l'effet constaté.

 Si toutefois mon hypothèse de départ est vraie !

 curty@einstein:~$ less son.txt 
 v
 :g/décrivez/.w! >> output.txt
 :q
 now I'm back in less looking at son.txt
 q

 curty@einstein:~$ cat output.txt 
 croissante du passé) le même phénomène chez moi que vous décrivez.
 
Maybe I'm off the mark here. I thought this was what the OP wanted
to do (but natively, as it were; however, I found no method of
doing this with less' native commands).

Re: vlan interface renamed

[Reco]

Hi.

On Wed, Apr 07, 2021 at 09:53:57AM +0200, Erwan David wrote:
> > > How Am I a supposed to have this working ?
> > 
> > By disabling problematic renaming of course:
> > 
> > cat > /etc/systemd/network/00-vlan.link << EOF
> > [Match]
> > Type=vlan
> > 
> > [Link]
> > NamePolicy=kernel
> > MACAddressPolicy=none
> > EOF
> > 
> > update-initramfs -k all -u
> > 
> 
> Alas it does not work. interface is still renamed

And here it gets interesting.
What about:

udevadm test /sys/class/net/rename12

Reco

Re: vlan interface renamed

[Erwan David]

Le 06/04/2021 à 22:39, deloptes a écrit :

Erwan David wrote:


Hello,


I have a machine with a working bond0 interface



Not clear what debian your machine is running


It's a debian10




In my /etc/network/interfaces I have a configuration for a vlan
subinterface

auto bond0.4011
address 80.74.78.202/31
pointtopoint 80.74.78.203

At boot, interface bond0.4011 is created and immediately renamed rename12.

How Am I a supposed to have this working ?


I would suggest you read this and update your setup accordingly

https://wiki.debian.org/NetworkConfiguration#Bridges_and_VLANs


That's not bridge, that's bonding I follow the example on 
https://wiki.debian.org/Bonding#Configuration_-_Example_4_-_.28very_complex_server_setup.29__with_LACP_Bonded_trunk_and_VLANs_split_out_of_the_trunk.2C_different_MTU.27s_on_the_VLANs 
except the MTU part which I keep the same on bond0 and vlan interface



Is it a bug in ifrename ?


if you refer to something like this here
https://wiki.debian.org/InterfaceRenaming
IMO it means youare living in the past


I am in the present and the present does not work. That's the problem. A 
logical interface defined and configured in /etc/network/interfaces 
should keep the name defined in the config file and be configured 
according to the configuration.

Re: vlan interface renamed

[Erwan David]

Le 07/04/2021 à 08:23, Reco a écrit :

Hi.

On Tue, Apr 06, 2021 at 06:41:21PM +0200, Erwan David wrote:

At boot, interface bond0.4011 is created and immediately renamed rename12.

How Am I a supposed to have this working ?


By disabling problematic renaming of course:

cat > /etc/systemd/network/00-vlan.link << EOF
[Match]
Type=vlan

[Link]
NamePolicy=kernel
MACAddressPolicy=none
EOF

update-initramfs -k all -u



Alas it does not work. interface is still renamed