date:20221113

On Sun 13 Nov 2022 at 13:25:05 (-), Curt wrote:
> On 2022-11-13, David Wright  wrote:
> > On Sat 12 Nov 2022 at 13:41:35 (-), Curt wrote:
> >> On 2022-11-12, David Wright  wrote:
> >> >
> >> > If and when that works, it should be simple to get exim to send
> >> > to the smarthost in the same manner. It should involve only the
> >> > two files /etc/exim4/{passwd.client,update-exim4.conf.conf} in
> >> > most cases.
> >> 
> >> https://groups.google.com/g/linux.debian.user/c/bAI10SqfmGA
> >> 
> >> He asked the same question back in May but with some other data
> >> points, not that it probably makes any difference.
> >
> > Yes, I referred to that, without citing it. However, the data points
> > were related to exim, and also lacked much context.
> >
> > https://lists.debian.org/debian-user/2022/05/msg00193.html
> >
> > It's quite possible that the OP has messed up exim's configuration
> > by tinkering with it, so I think it's simpler (and may give confidence
> > that frontier.com is not particularly unusual) by sending something
> > via mutt alone. Then the data used by mutt can be translated into
> > the equivalents for exim.
> >
> > BTW this goes back somewhat further—does this ring a bell?
> >
> > https://lists.debian.org/debian-user/2018/07/msg00115.html
> 
> No, but the following thread I do remember vaguely:
> 
> https://linux.debian.user.narkive.com/3PRw93ts/email-lacks-sender-address

Or, as I would know it,

https://lists.debian.org/debian-user/2022/04/msg00714.html

(You do get your debian-user posts from a variety of sources!)

Yes, that thread's a good example of how you can go round the houses
configuring exim. I suspect the purported solution might not even
have been the actual fix, as the OP had probably made a number of
other changes along the way, that we were not party to.

AFAIK the most verbose exim logs are still just a set of abbreviated
codes rather than a dialog, whereas mutt's debug 5 output gives the
entire SMTP dialog from start to finish, so about the only thing
missing is the TLS negotiation, for which I assume openssl would be
a better tool to investigate with.

Cheers,
David.

Re: ping

On Sun 13 Nov 2022 at 14:50:58 (+), Andrew M.A. Cater wrote:
> On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote:
> > root@joule:/home/root# /bin/ping -c 3  192.168.0.12
> > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
> > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
> > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
> > 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms
> > 
> > --- 192.168.0.12 ping statistics ---
> > 3 packets transmitted, 3 received, 0% packet loss, time 2041ms
> > rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
> > root@joule:/home/root# echo $PATH
> > /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.

Nobody has commented on that final period yet …  …  …  …  …  …   ↑

> > root@joule:/home/root# which ping
> > /bin/ping
> > root@joule:/home/root# ping -c 3  192.168.0.12
> > 
> > No response.
> > 
> > Ideas?
> 
> How did you become root? If with su, remember to now use su -
> 
> If with sudo, use sudo -s, maybe.

Perhaps https://lists.debian.org/debian-user/2022/02/msg00120.html
gives you a hint of explanation.

Cheers,
David.

Re: No Public Key

2022-11-13 Thread Thomas George


Still strugglng. command suggested returns new key but no user id - skipped

On 11/13/22 15:08, Darac Marjal wrote:


On 13/11/2022 19:14, Thomas George wrote:
I want to do a new verified instillation of a debian iso. I have the 
iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried


gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No 
Public Key


I thought to skip this step and tried

gpg --verify SHA515SUMS.sign.txt debian-11.5.0-amd64-netinst.iso with 
the result Can't open signed data debian-11.5.0-amd64-netinst.iso


Clearly I am making some elementary mistakes. I have spent fruitless 
hours trying find and use a public key. One source suggested Curl 
ipinfo.io/ip. This outputs an ip address that seams to have nothing 
to do with my problem.


A reference to a step-by-step procedure would be appreciated.


https://www.debian.org/CD/verify says "The keys used for these 
signatures are all in the Debian GPG keyring and the best way to check 
them is to use that keyring to validate via the web of trust.". If you 
are using a Debian system, you can get those keys by installing 
"debian-archive-keyring". IF you're not (which is likely, given you're 
trying to install Debian), then that page also lists the fingerprints 
of the keys:


pub   rsa4096/988021A964E6EA7D 2009-10-03
  Key fingerprint = 1046 0DAD 7616 5AD8 1FBC  0CE9 9880 21A9 64E6 
EA7D

uid  Debian CD signing key 

pub   rsa4096/DA87E80D6294BE9B 2011-01-05 [SC]
  Key fingerprint = DF9B 9C49 EAA9 2984 3258  9D76 DA87 E80D 6294 
BE9B

uid  Debian CD signing key 

pub   rsa4096/42468F4009EA8AC3 2014-04-15 [SC]
  Key fingerprint = F41D 3034 2F35 4669 5F65  C669 4246 8F40 09EA 
8AC3
uid  Debian Testing CDs Automatic Signing Key 



So you should just be able to do, for example:

    $ gpg --receive-keys "1046 0DAD 7616 5AD8 1FBC  0CE9 9880 21A9 
64E6 EA7D"





Tom George

Re: No Public Key

2022-11-13 Thread Thomas George


Still struggling command 3 below responds invalid option --key-server

On 11/13/22 15:46, Gökşin Akdeniz wrote:

Hello,

13.11.2022 22:14 tarihinde Thomas George yazdı:
I want to do a new verified instillation of a debian iso. I have the 
iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried


gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No 
Public Key




Debian public keys are listed on web pages for downloads. Here is the 
link for download page with checksums and public keys.


https://www.debian.org/download

Keys: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS.sign


Checksums: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS



A reference to a step-by-step procedure would be appreciated.



1. Get GnuPG key info from SHA512SUMS.sign with command "gpg --verify 
SHA512SUM.sign SHA512SUMS"


2.GnuPG will report for missing keys in keyring. Simply copy GnuPG key 
id "DF9B9C49EAA9298432589D76DA87E80D6294BE9B" from output.


3 Get public key from Debian Keyservers with command: "gpg 
--key-server keyring.debian.org --recv-keys 
DF9B9C49EAA9298432589D76DA87E80D6294BE9B"


4.GnuPG will download the public key.

5. Rerun verify command for checksum control: "gpg --verify 
SHA512SUM.sign SHA512SUMS"


6. GnuPG will report if the SHA512SUMS file signature matches with 
SHA512SUM.sign


7. If checksum of file is correct, then check the integrity of ISO 
files.: "sha512sum debian-11.5.0-amd64-netinst.iso"


7.Calculated checksums and SHA512SUMS should match.


I hope, it helps.

Re: how to add more ipv6 addresses to an interface that is being configured through dhcpv6

2022-11-13 Thread jeremy ardley




On 14/11/2022 7:50 am, jeremy ardley wrote:

> How do I additionally assign fd53::40/16?
I faced exactly the same problem on a recent new install of Debian 11.

I decided to use systemd-networkd service and removed most of the 
stuff from /etc/network/interfaces


This is my /etc/systemd/network/wired.lan.network file (name arbitrary)

I also get an additional static IPv4 address


--


I should note with my basic setup, I get an IPv6 address derived from my 
MAC address, an additional set of temporary IPv6 address for privacy 
with outgoing connections, and my static IPv6 address for incoming 
connections.


cat /etc/systemd/network/wired_lan.network
[Match]
Name=enp7s0

[Network]

DHCP=yes

Address=192.168.1.68/24
Gateway=192.168.1.1
DNS=192.168.1.4 192.168.1.5

Address=2001:db8:beef::44/64
IPv6PrivacyExtensions=yes
IPv6AcceptRA=yes

Domains=lan bronzemail.com

[IPv6AcceptRA]

 ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp7s0:  mtu 1500 qdisc pfifo_fast 
state UP group default qlen 1000

    link/ether 50:3e:aa:02:64:41 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.68/24 brd 192.168.1.255 scope global dynamic enp7s0
   valid_lft 78631sec preferred_lft 78631sec
    inet6 2001:db8:f4f:e649:b1fc:f160/64 scope global temporary dynamic
   valid_lft 6072sec preferred_lft 2471sec
    inet6 2001:db8:2673:e619:a00e:e392/64 scope global temporary 
deprecated dynamic

   valid_lft 6072sec preferred_lft 0sec
    inet6 2001:db8:5d63:bbf8:f876:7888/64 scope global temporary 
deprecated dynamic

   valid_lft 6072sec preferred_lft 0sec
    inet6 2001:db8:a01c:1cb6:323d:8ea4/64 scope global temporary 
deprecated dynamic

   valid_lft 6072sec preferred_lft 0sec
    inet6 2001:db8:e94c:ba84:af63:1af0/64 scope global temporary 
deprecated dynamic

   valid_lft 6072sec preferred_lft 0sec
    inet6 2001:db8:b71b:949f:390f:1acf/64 scope global temporary 
deprecated dynamic

   valid_lft 6072sec preferred_lft 0sec
    inet6 2001:db8:523e:aaff:fe02:6441/64 scope global dynamic 
mngtmpaddr noprefixroute

   valid_lft 6072sec preferred_lft 2471sec
    inet6 2001:db8:beef::44/64 scope global
   valid_lft forever preferred_lft forever
    inet6 fe80::523e:aaff:fe02:6441/64 scope link
   valid_lft forever preferred_lft forever



Jeremy

Re: how to add more ipv6 addresses to an interface that is being configured through dhcpv6

2022-11-13 Thread jeremy ardley




On 14/11/2022 12:07 am, hw wrote:
 > Hi, > > the subject says it ... I have an interface that is being 
configured > with IPv4 and IPv6 addresses via dhcp. I need to assign an 
> additional IPv6 address to the interface. > > > > How do I 
additionally assign fd53::40/16?

I faced exactly the same problem on a recent new install of Debian 11.

I decided to use systemd-networkd service and removed most of the stuff 
from /etc/network/interfaces


This is my /etc/systemd/network/wired.lan.network file (name arbitrary)

I also get an additional static IPv4 address


cat /etc/systemd/network/wired_lan.network

[Match]

Name=enp7s0

[Network]

DHCP=yes

Address=192.168.0.10/24

Gateway=192.168.0.1

DNS=192.168.0.4 192.168.0.5

Address=2345:0425:2CA1*::*0567:5673:23b5/64

IPv6PrivacyExtensions=yes

IPv6AcceptRA=yes

Domains=lan exampledomain.com

[IPv6AcceptRA]



cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback


--

Jeremy

Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))

2022-11-13 Thread David Christensen


On 11/13/22 13:02, hw wrote:

On Fri, 2022-11-11 at 07:55 -0500, Dan Ritter wrote:

hw wrote:

On Thu, 2022-11-10 at 20:32 -0500, Dan Ritter wrote:

Linux-Fan wrote:


[...]
* RAID 5 and 6 restoration incurs additional stress on the other
   disks in the RAID which makes it more likely that one of them
   will fail. The advantage of RAID 6 is that it can then recover
   from that...


Disks are always being stressed when used, and they're being stessed as well
when other types of RAID arrays than 5 or 6 are being rebuild.  And is there
evidence that disks fail *because* RAID arrays are being rebuild or would
they
have failed anyway when stressed?


Does it matter? The observed fact is that some notable
proportion of RAID 5/6 rebuilds fail because another drive in
that group has failed.


Fortunately, I haven't observed that.  And why would only RAID 5 or 6 be
affected and not RAID 1 or other levels?



Any RAID level can suffer additional disk failures while recovering from 
a disk failure.  I saw this exact scenario on my SOHO server in August 
2022.  The machine has a stripe of two mirrors of two HDD's each (e.g. 
ZFS equivalent of RAID10).  One disk was dying, so I replaced it.  While 
the replacement disk was resilvering, a disk in the other mirror started 
dying.  I let the first resilver finish, then replaced the second disk. 
Thankfully, no more disks failed.  I got lucky.



David

Re: /boot size and kernel updates

2022-11-13 Thread Mike Kupfer

Hi Stefan!

Stefan Monnier wrote:

> I use `MODULES=dep` and my kernel+initrd uses less than 20MB still so my
> 250MB /boot partition is currently 21% full with 2 kernels installed.

Ah, thanks for the tip.  I'll give that a try, as well as trying more
aggressive compression (thanks, Peter!).

> This said, my newer installs just don't bother with a separate
> /boot partition.

My understanding is that for LUKS-encrypted disks, /boot needs to be
separate so that it can remain unencrypted.

> PS: FWIW, my first HDD had a capacity of 50MB.  I didn't consider it "large"
> but it was quite sufficient for the system I used back then (MiNT).
> The 500MB disk in the Alpha workstations in my university's lab seemed
> quite large (all the home directories were on an NFS server, so most of
> the 500MB lay unused since the OS itself used a lot less than that,
> even that included a full X11 environment, Emacs, etc...).
> I suspect your experience is not very different, right?

I suppose so.  The first computer hardware that I purchased for myself
was a 1GB drive to supplement the storage on the sun4c system that my
employer let me take home.  I didn't need something that big, but it was
cheap enough, and I liked not having to think much about how much
storage I had available.  My current desktop has a 1TB drive and is
about half full, with most of the occupied storage consisting of
VirtualBox virtual disks and snapshots.

mike

Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))

On Fri, 2022-11-11 at 22:11 +0100, Linux-Fan wrote:
> hw writes:
> 
> > On Thu, 2022-11-10 at 22:37 +0100, Linux-Fan wrote:
> 
> [...]
> 
> > >  If you do not value the uptime making actual (even
> > >  scheduled) copies of the data may be recommendable over
> > >  using a RAID because such schemes may (among other advantages)
> > >  protect you from accidental file deletions, too.
> > 
> > Huh?
> 
> RAID is limited in its capabilities because it acts at the file system,  
> block (or in case of hardware RAID even disk) level. Copying files can  
> operate on any subset of the data and is very flexible when it comes to  
> changing what is going to be copied, how, when and where to.

How do you intend to copy files at any other level than at file level?  At that
level, the only thing you know about is files.

> ### what
> 
> When copying files, its a standard feature to allow certain patterns of file  
> names to be exclueded.

sure

> [...]
> ### how
> 
> Multiple, well established tools exist for file tree copying. In RAID  
> scenarios the mode of operation is integral to the solution.

What has file tree copying to do with RAID scenarios?

> ### where to
> 
> File trees are much easier copied to network locations compared to adding a  
> “network mirror” to any RAID (although that _is_ indeed an option, DRBD was  
> mentioned in another post...).

Dunno, btrfs and ZFS have some ability to send file systems over the network,
which intended to make copying more efficient.  There must be reasons why this
feature was developed.

> File trees can be copied to slow target storages without slowing down the  
> source file system significantly. On the other hand, in RAID scenarios,  
> slow members are expected to slow down the performance of the entire array.  
> This alone may allow saving a lot of money. E.g. one could consider copying  
> the entire tree of VM images that is residing on a fast (and expensive) SSD  
> to a slow SMR HDD that only costs a fraction of the SSD. The same thing is  
> not possible with a RAID mirror except by slowing down the write operations  
> on the mirror to the speed of the HDD or by having two (or more) of the  
> expensive SSDs. SMR drives are advised against in RAID scenarios btw.

Copying the VM images to the slow HDD would slow the target down just as it
might slow down a RAID array.

> ### when
> 
> For file copies, the target storage need not always be online. You can  
> connect it only for the time of synchronization. This reduces the chance  
> that line overvoltages and other hardware faults destroy both copies at the  
> same time. For a RAID, all drives must be online at all times (lest the  
> array becomes degraded).

No, you can always turn off the array just as you can turn off single disks. 
When I'm done making backups, I shut down the server and not much can happen to
the backups.

> Additionally, when using files, only the _used_ space matters. Beyond that,  
> the size of the source and target file systems are decoupled. On the other  
> hand, RAID mandates that the sizes of disks adhere to certain properties  
> (like all being equal or wasting some of the storage).

And?

> > > > Is anyone still using ext4?  I'm not saying it's bad or anything, it  
> > > > only seems that it has gone out of fashion.
> > > 
> > > IIRC its still Debian's default.
> > 
> > Hm, I haven't really used Debian in a long time.  There's probably no
> > reason  
> > to change that.  If you want something else, you can always go for it.
> 
> Why are you asking on a Debian list when you neiter use it nor intend to use  
> it?

I didn't say that I don't use Debian, nor that I don't intend to use it.

> [...]
> > > licensing or stability issues whatsoever. By its popularity its probably  
> > > one of the most widely-deployed Linux file systems which may enhance the  
> > > chance that whatever problem you incur with ext4 someone else has had
> > > before...
> > 
> > I'm not sure it's most widespread.
> [...]
> Now check with 
> 
> I get the following (smaller number => more popular):
> 
> 87   e2fsprogs
> 1657 btrfs-progs
> 2314 xfsprogs
> 2903 zfs-dkms 
> 
> Surely this does not really measure if people are actually use these  
> file systems. Feel free to provide a more accurate means of measurement. For  
> me this strongly suggests that the most popular FS on Debian is ext4.

ext4 doesn't show up in this list.  And it doesen't matter if ext4 is most
widespread on Debian when more widespread distributions use different file
systems.  I don't have a way to get the numbers for that.

Today I installed Debian on my backup server and didn't use ext4.  Perhaps the
"most widely-deployed" file system is FAT.

> > So assuming that RHEL and Centos may be more widespread than Debian because
> > there's lots of hardware supporting those but not Debian, I wouldn't think  
> > that
> > ext4 is most widespread

Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))

On Fri, 2022-11-11 at 07:55 -0500, Dan Ritter wrote:
> hw wrote: 
> > On Thu, 2022-11-10 at 20:32 -0500, Dan Ritter wrote:
> > > Linux-Fan wrote: 
> > > 
> > > 
> > > [...]
> > > * RAID 5 and 6 restoration incurs additional stress on the other
> > >   disks in the RAID which makes it more likely that one of them
> > >   will fail. The advantage of RAID 6 is that it can then recover
> > >   from that...
> > 
> > Disks are always being stressed when used, and they're being stessed as well
> > when other types of RAID arrays than 5 or 6 are being rebuild.  And is there
> > evidence that disks fail *because* RAID arrays are being rebuild or would
> > they
> > have failed anyway when stressed?
> 
> Does it matter? The observed fact is that some notable
> proportion of RAID 5/6 rebuilds fail because another drive in
> that group has failed.

Fortunately, I haven't observed that.  And why would only RAID 5 or 6 be
affected and not RAID 1 or other levels?

>  The drives were likely to be from the
> same cohort of the manufacturer, and to have experienced very
> similar read/write activity over their lifetime.

Yes, and that means that might they fail all at about the same time due to age
and not because an array is being rebuild.

The question remains what the ratio between surviving volumes and lost volumes
is.

Re: ping

2022-11-13 Thread Klaus Singvogel

pe...@easthope.ca wrote:
> root@joule:/home/root# /bin/ping -c 3  192.168.0.12
> PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
> 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
> 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
> 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms
> 
> --- 192.168.0.12 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2041ms
> rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
> root@joule:/home/root# echo $PATH
> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
> root@joule:/home/root# which ping
> /bin/ping
> root@joule:/home/root# ping -c 3  192.168.0.12
> 
> No response.
> 
> Ideas?

Strange that "which ping" is reporting /bin/ping and not /usr/bin/ping as first 
executable. The strange thing is that /usr/bin/ping is locate before /bin/ping 
in your $PATH and both are the same files in a standard installation (the 
inodes are identical).

So I assume, there is something utterly broken with your system (or your 
report), because of this.

But my hottest solution in your report is an alias.
Having an alias of ping will never be reported by "which" neither. So I can 
imaging you've defined ping as an alias.
And as Greg said, try "type ping" to find this out (and not "which ping").

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: No Public Key

2022-11-13 Thread Gökşin Akdeniz


Hello,

13.11.2022 22:14 tarihinde Thomas George yazdı:
I want to do a new verified instillation of a debian iso. I have the iso 
and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried


gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No 
Public Key




Debian public keys are listed on web pages for downloads. Here is the 
link for download page with checksums and public keys.


https://www.debian.org/download

Keys: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS.sign


Checksums: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/SHA512SUMS



A reference to a step-by-step procedure would be appreciated.



1. Get GnuPG key info from SHA512SUMS.sign with command "gpg --verify 
SHA512SUM.sign SHA512SUMS"


2.GnuPG will report for missing keys in keyring. Simply copy GnuPG key 
id "DF9B9C49EAA9298432589D76DA87E80D6294BE9B" from output.


3 Get public key from Debian Keyservers with command: "gpg --key-server 
keyring.debian.org --recv-keys DF9B9C49EAA9298432589D76DA87E80D6294BE9B"


4.GnuPG will download the public key.

5. Rerun verify command for checksum control: "gpg --verify 
SHA512SUM.sign SHA512SUMS"


6. GnuPG will report if the SHA512SUMS file signature matches with 
SHA512SUM.sign


7. If checksum of file is correct, then check the integrity of ISO 
files.: "sha512sum debian-11.5.0-amd64-netinst.iso"


7.Calculated checksums and SHA512SUMS should match.


I hope, it helps.


OpenPGP_0x648AAD2AAA3BAD5F_and_old_rev.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: /boot size and kernel updates

2022-11-13 Thread Stefan Monnier

Hi Mike,

> I've had the problem with /boot being too small on 2 systems.  I tried
> reinstalling one of them so that I could get a larger /boot.  And the
> installer did make /boot larger, but not as much as I wanted.  IIRC, it
> went from 250M to 500M, whereas I wanted to give it at least 1 GB.  I
> tried adjusting the sizes with the installer's partition manager, but I
> got stuck.  Unfortunately, I don't have adequate notes about how I got
> stuck.  I'm suspecting it had something to do with the fact that I had
> asked for a LUKS-encrypted disk.

I use `MODULES=dep` and my kernel+initrd uses less than 20MB still so my
250MB /boot partition is currently 21% full with 2 kernels installed.

This said, my newer installs just don't bother with a separate
/boot partition.


Stefan


PS: FWIW, my first HDD had a capacity of 50MB.  I didn't consider it "large"
but it was quite sufficient for the system I used back then (MiNT).
The 500MB disk in the Alpha workstations in my university's lab seemed
quite large (all the home directories were on an NFS server, so most of
the 500MB lay unused since the OS itself used a lot less than that,
even that included a full X11 environment, Emacs, etc...).
I suspect your experience is not very different, right?

Re: No Public Key

2022-11-13 Thread Darac Marjal



On 13/11/2022 19:14, Thomas George wrote:
I want to do a new verified instillation of a debian iso. I have the 
iso and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried


gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No 
Public Key


I thought to skip this step and tried

gpg --verify SHA515SUMS.sign.txt debian-11.5.0-amd64-netinst.iso with 
the result Can't open signed data debian-11.5.0-amd64-netinst.iso


Clearly I am making some elementary mistakes. I have spent fruitless 
hours trying find and use a public key. One source suggested Curl 
ipinfo.io/ip. This outputs an ip address that seams to have nothing to 
do with my problem.


A reference to a step-by-step procedure would be appreciated.


https://www.debian.org/CD/verify says "The keys used for these 
signatures are all in the Debian GPG keyring and the best way to check 
them is to use that keyring to validate via the web of trust.". If you 
are using a Debian system, you can get those keys by installing 
"debian-archive-keyring". IF you're not (which is likely, given you're 
trying to install Debian), then that page also lists the fingerprints of 
the keys:


pub   rsa4096/988021A964E6EA7D 2009-10-03
  Key fingerprint = 1046 0DAD 7616 5AD8 1FBC  0CE9 9880 21A9 64E6 EA7D
uid  Debian CD signing key 

pub   rsa4096/DA87E80D6294BE9B 2011-01-05 [SC]
  Key fingerprint = DF9B 9C49 EAA9 2984 3258  9D76 DA87 E80D 6294 BE9B
uid  Debian CD signing key 

pub   rsa4096/42468F4009EA8AC3 2014-04-15 [SC]
  Key fingerprint = F41D 3034 2F35 4669 5F65  C669 4246 8F40 09EA 8AC3
uid  Debian Testing CDs Automatic Signing Key 



So you should just be able to do, for example:

    $ gpg --receive-keys "1046 0DAD 7616 5AD8 1FBC  0CE9 9880 21A9 64E6 
EA7D"





Tom George



OpenPGP_signature
Description: OpenPGP digital signature

Re: sid - no sound on speakers

2022-11-13 Thread Jude DaShiell

An audio screen reader user would have noticed this problem as soon as it
happened.  If others are on sid, and haven't got to the same upgrade
level, running speaker-test after each upgrade may narrow down the likely
culprits.

Jude  "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)

.

On Sun, 13 Nov 2022, Tixy wrote:

> On Sat, 2022-11-12 at 19:01 +1000, David wrote:
> > What are you running?
> > Stable, Testing, Unstable?
>
> The subject line if prefixed with 'sid'. So Unstable I presume.
>
>

Re: how to add more ipv6 addresses to an interface that is being configured through dhcpv6

2022-11-13 Thread Darac Marjal



On 13/11/2022 16:07, hw wrote:

Hi,

the subject says it ... I have an interface that is being configured with IPv4
and IPv6 addresses via dhcp.  I need to assign an additional IPv6 address to the
interface.

This is all very easy with network-manager but that seems to be kinda deprecated
and we're supposed to use the anachronistic /etc/network/interfaces file.  The
manual page isn't helpful for this at all.

So I have


auto enp7s0
allow-hotplug enp7s0
iface enp7s0 inet dhcp
iface enp7s0 inet6 dhcp


How do I additionally assign fd53::40/16?

Probably the easiest option is "post-up ip addr add  fd53::40/16 dev 
$IFACE" and "pre-down ip addr del fd53::40/16 dev $IFACE".


OpenPGP_signature
Description: OpenPGP digital signature

No Public Key

2022-11-13 Thread Thomas George

I want to do a new verified instillation of a debian iso. I have the iso 
and SHA512SUMS.sign.txt and SHHA512SUMS.txt and have tried


gpg --verify SHA512SUMS.sign.txt SHA512SUMS.txt with the result No 
Public Key


I thought to skip this step and tried

gpg --verify SHA515SUMS.sign.txt debian-11.5.0-amd64-netinst.iso with 
the result Can't open signed data debian-11.5.0-amd64-netinst.iso


Clearly I am making some elementary mistakes. I have spent fruitless 
hours trying find and use a public key. One source suggested Curl 
ipinfo.io/ip. This outputs an ip address that seams to have nothing to 
do with my problem.


A reference to a step-by-step procedure would be appreciated.

Tom George

Re: Re: howto install Debian on software RAID1 when UEFI?

Hi hw,

Having followed through the steps I outlined:

> I'm about to try this on a VM with two disks. I'm going to initially partition
> as if I were using LVM and all in one partition on one disk, then on the other

> That should give me identically sized partitions.

> At that point, I'll change the type on the LVM partitions to RAID, and use
> use the RAID partitioner to make a RAID1 device.

> At that point, I'll change the type on the LVM partitions to RAID, and use
> use the RAID partitioner to make a RAID1 device.

> After that, I'll use one of the ESP partitons and tell the partitioner
> to install all in one partition on the RAID device.

> I'll then change the type of the partition installed to btrfs.

> That should give me EFI - RAID - swap on each of two disks.
> The RAID should be RAID1 and will be mounted as /

This all worked.

I then rebooted into rescue mode, typed in the root password and typed 

update-grub /dev/sdb

which appeared to work fine.

Hope this helps, with every good wish as ever,

Andy Cater

Re: sid - no sound on speakers

2022-11-13 Thread Tixy

On Sat, 2022-11-12 at 19:01 +1000, David wrote:
> What are you running?
> Stable, Testing, Unstable?

The subject line if prefixed with 'sid'. So Unstable I presume.

-- 
Tixy

Re: MTBF interpretations (Re: ZFS performance)

2022-11-13 Thread hede

On Sat, 12 Nov 2022 07:52:32 -0500 Dan Ritter  wrote:

> No, my interpretation is that the average (mean) lifetime
> between failures should be the listed value. At 114 years, half
> of the population of drives should still be working.
> 
> This is obviously not congruent with reality.

I'd say it's like with many things in life: If expectation doesn't match the 
definition, outcome is "not congruent with reality".

MTBF is, like Stefan already said, not a lifetime expectation.

> [...]
> Some drive models are lucky. Some are unlucky. Overall you
> should expect about 1.54% of disks to fail each year in a large
> mixed-age population, not quite double what you estimated. But
> the range of annualized failure rates is from 0 to 9% -- you
> could be lucky, or very unlucky.

That's what is to expect here. They are using desktop drives in enterprise 
environment. This naturally gives results not foreseen by the disk vendor. Even 
for some of the "sub par" disks the result is probably fine. And Backblaze 
itself do know this. They safe money with having some more failed cheap disks 
like the ST4000DM000 - a disk with a power-on-ratio of 9/5 instead of 24/7 
(2400 hours per year) and no MTBF rating (AFAICS)?

I'd simply not mix this into some 1.000.000 hours MTBF rating expectation... 

hede

Re: ping

2022-11-13 Thread Greg Wooledge

On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote:
> root@joule:/home/root# /bin/ping -c 3  192.168.0.12
> PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
> 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
> 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
> 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms
> 
> --- 192.168.0.12 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2041ms
> rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms

> root@joule:/home/root# which ping
> /bin/ping

"which" is useless.

> root@joule:/home/root# ping -c 3  192.168.0.12
> 
> No response.

What does "type ping" say in that shell?

Re: definiing deduplication

2022-11-13 Thread Michael Stone


On Sat, Nov 12, 2022 at 01:39:56PM -0500, Stefan Monnier wrote:

But as I mentioned, higher-layers (the filesystem layer, and the
applications running on top of that) *should* try and make sure that
a hard failure (kernel crash, power failure, ... these and up taking
a snapshot of your block device) can never result in an
inconsistent state.

That's the core of the ext3 improvement over ext2, for example.


Actually, it isn't--the core of ext3 improvement over ext2 is faster 
startup time after an unplanned shutdown, by avoiding a fsck; it does 
not offer stronger consistency guarantees than ext2 if the application 
is being careful in how it writes data. It's possible to run ext3 in 
full data journalling mode, which does change things, but that isn't 
normally done because the performance impact is significant. (And 
because in most cases it doesn't help much in practice--applications 
that are careful about how they write data already cope with 
non-data-journaling filesystems because that's the normal case, and 
applications which aren't careful about how they write data can still 
end up in a situation where data is consistent from the filesystem pov 
but partially written/corrupt from the application pov.)

Re: howto install Debian on software RAID1 when UEFI?

On Sun, Nov 13, 2022 at 05:29:17PM +0100, hw wrote:
> On Sun, 2022-11-13 at 14:32 +, Andrew M.A. Cater wrote:
> > On Sun, Nov 13, 2022 at 02:49:28PM +0100, hw wrote:
> > > 
> > > Hi,
> > > 
> > > the Debian installer is horrible.  It won't let me install on software 
> > > RAID1
> > > on
> > > a server with an UEFI BIOS.  I can't find any good guide about that, 
> > > either.
> > > 
> > 
> > Hi hw
> > 
> > You might want to *start* with using the expert install - found under the 
> > advanced menu option. That will give you more control, including advanced
> > partitioning.
> 
> That's where I kept ending up.  I didn't want that, it needs to be easy to
> install on software RAID.  Not everyone has hardware RAID to boot from.
> 

And that's why I suggested the advanced partitioning. I only have software
RAID - as do most people now.

I'm about to try this on a VM with two disks. I'm going to initially partition
as if I were using LVM and all in one partition on one disk, then on the other.
That should give me identically sized partitions.

At that point, I'll change the type on the LVM partitions to RAID, and use
use the RAID partitioner to make a RAID1 device.

After that, I'll use one of the ESP partitons and tell the partitioner
to install all in one partition on the RAID device.

[I'm fairly sure Fedora also installs LVM by default as it makes it a lot
easier to resize partitions if necessary when adding more storage.]
I'll then change the type of the partition installed to btrfs.

That should give me EFI - RAID - swap on each of two disks.
The RAID should be RAID1 and will be mounted as /

> > > I want root on brtfs with RAID1.  How do I get Debian installed?
> > 
> > I'd suggest that you partition one disk with "all files in one partition"
> > as a test run to see the sizes you'll need and then rerun the partitioner.
> 
> Yeah that failed.  The installer was unable to install grub, then it was 
> unable
> to mount /boot/efi ...  It's not working right at all.
> 

Let me run through the process: I'm reformatting a spare machine so that its
running Stable then I'll run through in a KVM/QEMU machine with virt-manager.

> > > From memory, I think you end up with something like an EFI partition of
> > > 512M,
> > a root partition of (the rest - 1G) and then a 1G swap.
> > 
> > If you partition both disks to have an EFI partition at the beginning, then
> > a RAID partition, then 2 x 1G swap at the end.
> 
> Yeah that's what I tried.
> 
> > Then use the RAID manager to set up RAID1 and LVM over the top.
> 
> There's no way that I would use LVM.  That's yet another layer of complexitiy
> with no advantages whatsoever and a nightmare to deal with.  I used it once 
> and
> I'll never do that again.
> 
> >  I'm unsure how
> > you would install GRUB to the second disk of the RAID - it might be that 
> > you'd
> > need to restart once the install is complete, use the rescue option and
> > specifically install GRUB on the second disk of the RAID.
> 
> It used to be possible to just install it on the other disk.  But I didn't get
> that far.
> 
> After over half a day and some reboots, I finally got it to install on a 
> single
> disk without any redundancy.  I'll have to partition the 2nd disk later after 
> I
> figured out how to add another IPv6 address to one of the interfaces --- easy
> with network manager on Fedora (which also installs on software RAID),
> impossible with Debian.
> 
> I won't be able to boot when the disk I installed on failed.  In this case, it
> doesn't matter too much, but if that was a remote server there would be no way
> to get it installed without hardware RAID.
> 
> Debian really needs to work a lot on the installer.  It used to be easy to
> install Debian, but now it's a nightmare.
> 
> > > 
> > > The graphical version crashes with a kernel panic when booting from an USB
> > > stick, so I need to use the normal installer.
> > 
> > Then you have wider problems than just installation, perhaps?
> > 
> 
> No, why would you say that.
> 

If you can't boot the graphical installer but you can boot the text
installer, there's something wrong somewhere. How did you write the USB
stick and did you test the integrity of the media?

> > > There's even not a way to select RAID1 for btrfs.  What an anachronism ...
> > > 
> > 
> > You do know that this is a general purpose installer that covers 12 or so
> > filesystem types and allows for flexibility?
> 
> Fedoras installer does a better much job.  I didn't want endless flexibility 
> but
> a simple standard installation on software RAID.  That used to be easy with
> Debian.
> 

Your "standard" installation may not be everyone's standard, especially with
RAID and btrfs. If you want us to add it to the various installation methods
we try with each point release, we might be persuaded, though we already
have a combinatorial explosion of options to test each time. (I help with
CD/DVD media testing on point release days).

> > With every good

Initramfs compression algorithm - was Re: /boot size and kernel updates

2022-11-13 Thread Peter von Kaehne

To reduce size of initramfs I change the compression setting in 

/etc/initramfs/initramfs.conf 

and set it to “xz”

After that one needs to rebuild initramfs.

Sent from my phone. Please forgive misspellings and weird “corrections”

> On 13 Nov 2022, at 16:35, David Christensen  wrote:
> 
> On 11/13/22 01:41, Peter von Kaehne wrote:
>> I mostly let the installer do what it likes to do when installing Debian and 
>> this has worked out fine until the last couple installs on UEFI rather than 
>> legacy boot.
>> It now appears that the automatic installer does not get size of /boot right 
>> - even with only one new kernel update wanting to install itself it often 
>> fails with lack of space. One solution I found is to change the initramfs 
>> compression algorithm, which gives me space for two full kernels and 
>> initramfses. But this is still problematic. Are there other solutions other 
>> than reinstall with a larger boot partition?
>> For me the main problem are a couple of elderly relatives etc whose 
>> computers I administer mostly in a hands off fashion - with automatic 
>> security updates only and occasionally some more work during visits.
>> Now I am needing to look into sorting out remote access or simply disable 
>> all updates, neither of which is ideal for any variety of reasons.
>> Any clever suggestions which bring me back into a place where a few kernels 
>> can easily install without things getting too crowded?
>> Sent from my phone. Please forgive misspellings and weird “corrections”
> 
> 
> Please run the following commands as root and post the complete console 
> session -- prompts, commands entered, and output displayed:
> 
> 2022-11-13 08:32:14 root@laalaa ~
> # cat /etc/debian_version ; uname -a
> 11.5
> Linux laalaa 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 
> GNU/Linux
> 
> 2022-11-13 08:32:24 root@laalaa ~
> # ls -lF /boot
> total 109188
> -rw-r--r-- 1 root root   83 Sep  2 06:54 System.map-5.10.0-18-amd64
> -rw-r--r-- 1 root root   83 Oct 21 13:24 System.map-5.10.0-19-amd64
> -rw-r--r-- 1 root root   236286 Sep  2 06:54 config-5.10.0-18-amd64
> -rw-r--r-- 1 root root   236275 Oct 21 13:24 config-5.10.0-19-amd64
> drwxr-xr-x 5 root root 4096 Oct 29 13:48 grub/
> -rw-r--r-- 1 root root 48673909 Sep 24 17:33 initrd.img-5.10.0-18-amd64
> -rw-r--r-- 1 root root 48693403 Oct 29 13:19 initrd.img-5.10.0-19-amd64
> drwx-- 2 root root16384 Jan  9  2022 lost+found/
> -rw-r--r-- 1 root root  6962016 Sep  2 06:54 vmlinuz-5.10.0-18-amd64
> -rw-r--r-- 1 root root  6963648 Oct 21 13:24 vmlinuz-5.10.0-19-amd64
> 
> 2022-11-13 08:32:50 root@laalaa ~
> # du -bc /boot
> 4379325/boot/grub/locale
> 2010385/boot/grub/i386-pc
> 2398204/boot/grub/fonts
> 11195075/boot/grub
> 16384/boot/lost+found
> 122981258/boot
> 122981258total
> 
> 2022-11-13 08:33:20 root@laalaa ~
> # df /boot
> Filesystem 1M-blocks  Used Available Use% Mounted on
> /dev/sda1   920M  118M  739M  14% /boot
> 
> 
> David
>

Re: RFC: What would be the "correct debian way" to clean up unwanted languages from an installation?

2022-11-13 Thread Andy Smith

Hello,

On Sun, Nov 13, 2022 at 04:32:51PM +0100, DdB wrote:
> Would anyone be willing to take a look at what i have been doing and
> guide me to a resolution of the missing parts?
> 
> My current (bash) script can be found here:
> https://paste.debian.net/1260563/

There is an existing package "localpurge" in Debian that does this.
Here's more info:

https://sleeplessbeastie.eu/2018/09/03/how-to-remove-useless-localizations/

I've only used it in one place but it worked fine.

It also manages dpkg configuration to filter out the relevant file paths
from future installation.

Cheers,
Andy

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

Re: /boot size and kernel updates

2022-11-13 Thread Charles Curley

On Sun, 13 Nov 2022 14:45:15 +
"Andrew M.A. Cater"  wrote:

> Ideally, you shouldn't need more than the current kernel and,
> perhaps, the previous version.

One nitpick: I believe that installing a new kernel means installing
the new kernel, and only if that is successful removing an old one. (At
least that's how I would do it so I had a fallback if the installation
fails.) In that case if you want N kernels installed, /boot has to have
room for at least N + 1 kernels.

My preferred /boot size these days is 512M.

-- 
Does anybody read signatures any more?

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

Re: /boot size and kernel updates

2022-11-13 Thread David Christensen


On 11/13/22 01:41, Peter von Kaehne wrote:

I mostly let the installer do what it likes to do when installing Debian and 
this has worked out fine until the last couple installs on UEFI rather than 
legacy boot.

It now appears that the automatic installer does not get size of /boot right - 
even with only one new kernel update wanting to install itself it often fails 
with lack of space. One solution I found is to change the initramfs compression 
algorithm, which gives me space for two full kernels and initramfses. But this 
is still problematic. Are there other solutions other than reinstall with a 
larger boot partition?

For me the main problem are a couple of elderly relatives etc whose computers I 
administer mostly in a hands off fashion - with automatic security updates only 
and occasionally some more work during visits.

Now I am needing to look into sorting out remote access or simply disable all 
updates, neither of which is ideal for any variety of reasons.

Any clever suggestions which bring me back into a place where a few kernels can 
easily install without things getting too crowded?

Sent from my phone. Please forgive misspellings and weird “corrections”



Please run the following commands as root and post the complete console 
session -- prompts, commands entered, and output displayed:


2022-11-13 08:32:14 root@laalaa ~
# cat /etc/debian_version ; uname -a
11.5
Linux laalaa 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) 
x86_64 GNU/Linux


2022-11-13 08:32:24 root@laalaa ~
# ls -lF /boot
total 109188
-rw-r--r-- 1 root root   83 Sep  2 06:54 System.map-5.10.0-18-amd64
-rw-r--r-- 1 root root   83 Oct 21 13:24 System.map-5.10.0-19-amd64
-rw-r--r-- 1 root root   236286 Sep  2 06:54 config-5.10.0-18-amd64
-rw-r--r-- 1 root root   236275 Oct 21 13:24 config-5.10.0-19-amd64
drwxr-xr-x 5 root root 4096 Oct 29 13:48 grub/
-rw-r--r-- 1 root root 48673909 Sep 24 17:33 initrd.img-5.10.0-18-amd64
-rw-r--r-- 1 root root 48693403 Oct 29 13:19 initrd.img-5.10.0-19-amd64
drwx-- 2 root root16384 Jan  9  2022 lost+found/
-rw-r--r-- 1 root root  6962016 Sep  2 06:54 vmlinuz-5.10.0-18-amd64
-rw-r--r-- 1 root root  6963648 Oct 21 13:24 vmlinuz-5.10.0-19-amd64

2022-11-13 08:32:50 root@laalaa ~
# du -bc /boot
4379325 /boot/grub/locale
2010385 /boot/grub/i386-pc
2398204 /boot/grub/fonts
11195075/boot/grub
16384   /boot/lost+found
122981258   /boot
122981258   total

2022-11-13 08:33:20 root@laalaa ~
# df /boot
Filesystem 1M-blocks  Used Available Use% Mounted on
/dev/sda1   920M  118M  739M  14% /boot


David

Re: Problem with card reader on Debian 11

2022-11-13 Thread Curt

On 2022-11-12, to...@tuxteam.de  wrote:
>
> If that is successful, the next step would be to tell udev to stop
> loading that module. But first steps first :)
>

There is an oddly analogous thread (but maybe 64 bytes from ttyacm0 is a
thing) below from way back when that incriminates the code, which
probably won't be helpful (but we have so many electrons there's really
no use being frugal about them):

https://stackoverflow.com/questions/18288839/ttyacm0-only-reads-64-bytes

Re: RFC: What would be the "correct debian way" to clean up unwanted languages from an installation?

2022-11-13 Thread Charles Curley

On Sun, 13 Nov 2022 16:32:51 +0100
DdB  wrote:

> every backup contains loads of unnecessary language files, and i saw
> them scroll by during rsync. So one day, i wanted to get rid of those.

You might take a look at the localepurge package.

-- 
Does anybody read signatures any more?

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

Re: howto install Debian on software RAID1 when UEFI?

On Sun, 2022-11-13 at 14:32 +, Andrew M.A. Cater wrote:
> On Sun, Nov 13, 2022 at 02:49:28PM +0100, hw wrote:
> > 
> > Hi,
> > 
> > the Debian installer is horrible.  It won't let me install on software RAID1
> > on
> > a server with an UEFI BIOS.  I can't find any good guide about that, either.
> > 
> 
> Hi hw
> 
> You might want to *start* with using the expert install - found under the 
> advanced menu option. That will give you more control, including advanced
> partitioning.

That's where I kept ending up.  I didn't want that, it needs to be easy to
install on software RAID.  Not everyone has hardware RAID to boot from.

> > I want root on brtfs with RAID1.  How do I get Debian installed?
> 
> I'd suggest that you partition one disk with "all files in one partition"
> as a test run to see the sizes you'll need and then rerun the partitioner.

Yeah that failed.  The installer was unable to install grub, then it was unable
to mount /boot/efi ...  It's not working right at all.

> > From memory, I think you end up with something like an EFI partition of
> > 512M,
> a root partition of (the rest - 1G) and then a 1G swap.
> 
> If you partition both disks to have an EFI partition at the beginning, then
> a RAID partition, then 2 x 1G swap at the end.

Yeah that's what I tried.

> Then use the RAID manager to set up RAID1 and LVM over the top.

There's no way that I would use LVM.  That's yet another layer of complexitiy
with no advantages whatsoever and a nightmare to deal with.  I used it once and
I'll never do that again.

>  I'm unsure how
> you would install GRUB to the second disk of the RAID - it might be that you'd
> need to restart once the install is complete, use the rescue option and
> specifically install GRUB on the second disk of the RAID.

It used to be possible to just install it on the other disk.  But I didn't get
that far.

After over half a day and some reboots, I finally got it to install on a single
disk without any redundancy.  I'll have to partition the 2nd disk later after I
figured out how to add another IPv6 address to one of the interfaces --- easy
with network manager on Fedora (which also installs on software RAID),
impossible with Debian.

I won't be able to boot when the disk I installed on failed.  In this case, it
doesn't matter too much, but if that was a remote server there would be no way
to get it installed without hardware RAID.

Debian really needs to work a lot on the installer.  It used to be easy to
install Debian, but now it's a nightmare.

> > 
> > The graphical version crashes with a kernel panic when booting from an USB
> > stick, so I need to use the normal installer.
> 
> Then you have wider problems than just installation, perhaps?
> 

No, why would you say that.

> > There's even not a way to select RAID1 for btrfs.  What an anachronism ...
> > 
> 
> You do know that this is a general purpose installer that covers 12 or so
> filesystem types and allows for flexibility?

Fedoras installer does a better much job.  I didn't want endless flexibility but
a simple standard installation on software RAID.  That used to be easy with
Debian.

> With every good wish, as ever,
> 
> Andy Cater 
>

Re: howto install Debian on software RAID1 when UEFI?

2022-11-13 Thread Andy Smith

Hello,

On Sun, Nov 13, 2022 at 02:32:06PM +, Andrew M.A. Cater wrote:
> If you partition both disks to have an EFI partition at the beginning, then
> a RAID partition, then 2 x 1G swap at the end.
> 
> Then use the RAID manager to set up RAID1 and LVM over the top. I'm unsure how
> you would install GRUB to the second disk of the RAID - it might be that you'd
> need to restart once the install is complete, use the rescue option and
> specifically install GRUB on the second disk of the RAID.

Do note that OP has not made clear whether they want btrfs on top of MD
RAID-1, or btrfs with its own "raid1" data profile (which is not at all
the same as MD RAID-1 and isn't installed the same way).

I'm not sure whether you can set up multi-device btrfs in the installer,
though if you can't it would be easy to just install to one device, add
the second device afterwards and then do a balance to split the data
equally.

Also OP should note that whichever way you go, the EFI System Partition
technically can't go in any form of software RAID, so at the moment you
have to have two of them and manage them individually somehow:

"Redundancy for EFI System Partition: what do people do in 2020?"
https://lists.debian.org/debian-user/2020/11/msg00455.html

(same answers now in 2022)

Cheers,
Andy

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

Re: ping

2022-11-13 Thread Charles Curley

On Sun, 13 Nov 2022 06:13:38 -0800
pe...@easthope.ca wrote:

> root@joule:/home/root# /bin/ping -c 3  192.168.0.12
> PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
> 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
> 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
> 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms
> 
> --- 192.168.0.12 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2041ms
> rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
> root@joule:/home/root# echo $PATH
> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
> root@joule:/home/root# which ping
> /bin/ping
> root@joule:/home/root# ping -c 3  192.168.0.12
> 
> No response.

What system are you running? I am running pretty much standard Debian
11, and I notice these differences:

You appear to have root's home at /home/root. Mine is at /root, and I
have no /home/root.

root@jhegaala:~# cd
root@jhegaala:~# pwd
/root
root@jhegaala:~# ll /home/
total 28
drwxr-xr-x  4 rootroot 4096 Oct 10  2021 ./
drwxr-xr-x 19 rootroot 4096 Oct 19 06:27 ../
drwxr-xr-x 50 charles charles  4096 Nov 10 08:00 charles/
drwx--  2 rootroot16384 Oct 10  2021 lost+found/
root@jhegaala:~# 


which finds ping at /usr/bin/ping.

root@jhegaala:~# which ping
/usr/bin/ping
root@jhegaala:~#

although the two are the same:

root@jhegaala:~# ls -i /bin/ping /usr/bin/ping
7607442 /bin/ping  7607442 /usr/bin/ping
root@jhegaala:~# 


I get a different response when I try to execute a program that the
shell cannot find.

root@jhegaala:~# foo
-bash: foo: command not found
root@jhegaala:~# 

And, of course, I have no problem running ping without specifying a
full path to the executable.

root@jhegaala:~# ping -c 3 chaffee
PING chaffee.localdomain (192.168.100.30) 56(84) bytes of data.
64 bytes from chaffee.localdomain (192.168.100.30): icmp_seq=1 ttl=64 time=1.33 
ms
64 bytes from chaffee.localdomain (192.168.100.30): icmp_seq=2 ttl=64 time=1.99 
ms
64 bytes from chaffee.localdomain (192.168.100.30): icmp_seq=3 ttl=64 time=3.15 
ms

--- chaffee.localdomain ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 1.334/2.157/3.153/0.752 ms
root@jhegaala:~# 




-- 
Does anybody read signatures any more?

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

Re: ping

2022-11-13 Thread David Christensen


On 11/13/22 06:13, pe...@easthope.ca wrote:

root@joule:/home/root# /bin/ping -c 3  192.168.0.12
PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

--- 192.168.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2041ms
rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
root@joule:/home/root# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
root@joule:/home/root# which ping
/bin/ping
root@joule:/home/root# ping -c 3  192.168.0.12

No response.

Ideas?

Thanks, ... Peter E.




mobile: +1 778 951 5147
   VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope



If you run Bash, RTFM bash(1), "SHELL BUILTIN COMMANDS",
"command [-pVv] command [arg ...]":

2022-11-13 08:12:17 dpchrist@laalaa ~
$ command -V test ll ping
test is a shell builtin
ll is aliased to `ls -al --time-style="+%Y-%m-%d %H:%M:%S"'
ping is /usr/bin/ping


David

Re: /boot size and kernel updates

2022-11-13 Thread Mike Kupfer

Peter von Kaehne wrote:

> It now appears that the automatic installer does not get size of /boot
> right - even with only one new kernel update wanting to install itself
> it often fails with lack of space. 

I have had this problem, too, so thank you for bringing it up on the
list.

> One solution I found is to change the initramfs compression algorithm,
> which gives me space for two full kernels and initramfses.

Can you (or someone) point me at the documentation that says how to
change the compression algorithm?

> Are there other solutions other than reinstall with a larger boot
> partition?

I've had the problem with /boot being too small on 2 systems.  I tried
reinstalling one of them so that I could get a larger /boot.  And the
installer did make /boot larger, but not as much as I wanted.  IIRC, it
went from 250M to 500M, whereas I wanted to give it at least 1 GB.  I
tried adjusting the sizes with the installer's partition manager, but I
got stuck.  Unfortunately, I don't have adequate notes about how I got
stuck.  I'm suspecting it had something to do with the fact that I had
asked for a LUKS-encrypted disk.

best wishes,
mike

how to add more ipv6 addresses to an interface that is being configured through dhcpv6



Hi,

the subject says it ... I have an interface that is being configured with IPv4
and IPv6 addresses via dhcp.  I need to assign an additional IPv6 address to the
interface.

This is all very easy with network-manager but that seems to be kinda deprecated
and we're supposed to use the anachronistic /etc/network/interfaces file.  The
manual page isn't helpful for this at all.

So I have


auto enp7s0
allow-hotplug enp7s0
iface enp7s0 inet dhcp
iface enp7s0 inet6 dhcp


How do I additionally assign fd53::40/16?

Re: /boot size and kernel updates

2022-11-13 Thread Mike Kupfer

Andrew M.A. Cater wrote:

> Ideally, you shouldn't need more than the current kernel and, perhaps, the
> previous version. If the current kernel works on the reboot, then you should
> be able to remove all previous variants with the same major version number.

It used to be that I could leave the old kernel installed.  After a
third kernel got installed, an "apt autoremove" would remove the old
one.  I found that much more convenient than what I currently have to
do, which is (remember to) manually delete the old kernel before
installing the third one.  But it requires space in /boot for 3 images.

best wishes,
mike

RFC: What would be the "correct debian way" to clean up unwanted languages from an installation?

2022-11-13 Thread DdB

Hello,

every backup contains loads of unnecessary language files, and i saw
them scroll by during rsync. So one day, i wanted to get rid of those.

What a surprise: doing it in my (rather simplistic) fashion, i got rid
of almost 1,5 GB from every buster machine, i had ... only to find, that
they were eventually coming back through system updates. :-(

But - since my know-how on debian is very restrained - i did create a
script, that allowed me to examine the situation more easily, without
damaging the install, i was looking at. And only after verification did
i run the removal. (BTW: in bullseye, i found there was much less
unnecessary stuff) But still, the deleted files came back through
updates, because i dont know, how to tell apt about my removals the
proper way.

Would anyone be willing to take a look at what i have been doing and
guide me to a resolution of the missing parts?

My current (bash) script can be found here:
https://paste.debian.net/1260563/

Thank you for your attention
DdB

Re: ping

2022-11-13 Thread Peter Ehlert




On 11/13/22 06:50, Andrew M.A. Cater wrote:

On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote:

root@joule:/home/root# /bin/ping -c 3  192.168.0.12
PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

--- 192.168.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2041ms
rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
root@joule:/home/root# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
root@joule:/home/root# which ping
/bin/ping
root@joule:/home/root# ping -c 3  192.168.0.12

No response.

Ideas?

Thanks, ... Peter E.




How did you become root? If with su, remember to now use su -

If with sudo, use sudo -s, maybe.

is this the expected response?

peter@z840:~$ su -
Password:
root@z840:~#  /bin/ping -c 3  192.168.0.12
PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.

--- 192.168.0.12 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2060ms

root@z840:~#



All the very best, as ever,

Andy Cater

mobile: +1 778 951 5147
   VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope

ping

2022-11-13 Thread peter

root@joule:/home/root# /bin/ping -c 3  192.168.0.12
PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

--- 192.168.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2041ms
rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
root@joule:/home/root# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
root@joule:/home/root# which ping
/bin/ping
root@joule:/home/root# ping -c 3  192.168.0.12

No response.

Ideas?

Thanks, ... Peter E.




mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope

Re: ping

On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote:
> root@joule:/home/root# /bin/ping -c 3  192.168.0.12
> PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
> 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
> 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
> 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms
> 
> --- 192.168.0.12 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2041ms
> rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
> root@joule:/home/root# echo $PATH
> /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
> root@joule:/home/root# which ping
> /bin/ping
> root@joule:/home/root# ping -c 3  192.168.0.12
> 
> No response.
> 
> Ideas?
> 
> Thanks, ... Peter E.
> 
> 
>

How did you become root? If with su, remember to now use su -

If with sudo, use sudo -s, maybe.

All the very best, as ever,

Andy Cater 
> 
> mobile: +1 778 951 5147
>   VoIP: +1 604 670 0140
> https://en.wikibooks.org/wiki/User:PeterEasthope
>

Re: Falta de firmware

2022-11-13 Thread Camaleón

El 2022-11-13 a las 09:34 -0300, Simeón Ignacio Martirén escribió:

> Hola lista. Soy usuario no experto. Trato de actualizar mi PC de escritorio

(...)

> y me presenta esta situación:
> 
> root@Bulls:/home/ign# sudo apt-get update && apt-get upgrade

Mejor que «apt-get upgrade» es «apt-get dist-upgrade», sobre todo si 
estás con la versión estable, no te generará ningún problema.

(...)

> 19 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no
> actualizados.

(...)

Ejecuta como root «dmesg | grep -i firmware» y si no ves ningún error, 
puedes omitir esos mensajes del kernel ya que el firmware no es 
necesario.

Nos pasa a todos, pero son errores inocuos.

> W: initramfs-tools configuration sets 
> RESUME=UUID=dd7d3adf-3dab-4956-92a4-79943fefd136
> W: but no matching swap device is available.
> I: The initramfs will attempt to resume from /dev/sda5
> I: (UUID=f23cfe7c-7ccf-42d4-8062-dfc04548c9b6)
> I: Set the RESUME variable to override this.

Esto parece indicar que has cambiado la partición swap, revisa si está 
bien asignada/identificada  en «/etc/fstab».

Saludos,

-- 
Camaleón

Re: /boot size and kernel updates

On Sun, Nov 13, 2022 at 09:41:43AM +, Peter von Kaehne wrote:
> I mostly let the installer do what it likes to do when installing Debian and 
> this has worked out fine until the last couple installs on UEFI rather than 
> legacy boot. 
> 
> It now appears that the automatic installer does not get size of /boot right 
> - even with only one new kernel update wanting to install itself it often 
> fails with lack of space. One solution I found is to change the initramfs 
> compression algorithm, which gives me space for two full kernels and 
> initramfses. But this is still problematic. Are there other solutions other 
> than reinstall with a larger boot partition? 
> 

If you do have a working Debian, then there ought to be space for 2 x kernel
+ initrd in /boot (although I see in another thread that someone is complaining
that kernel images have increased massively in size recently.)

> For me the main problem are a couple of elderly relatives etc whose computers 
> I administer mostly in a hands off fashion - with automatic security updates 
> only and occasionally some more work during visits. 
> 

Understood :) In theory, at least, if you get a kernel update, you should 
arrange to reboot to ensure that you're running the latest kernel - many
of the kernel updates are there specifically for security reasons.

In practice, you can then apt remove / autoremove older kernels that you are no 
longer running.

Ideally, you shouldn't need more than the current kernel and, perhaps, the
previous version. If the current kernel works on the reboot, then you should
be able to remove all previous variants with the same major version number.
(So if 5.10.0-19 is working, you can remove 5.10.0-18 and prior versions).

So - in theory - my /boot partition on this machine is 471M but only
68M of that is used by the vmlinuz and initrd for linux-image-5.10.0-19-amd64
(which is actually also 5.10.149-2) leaving space for a few more kernels
at least.

Hope this helps, and with every good wish, as ever,

Andy Cater

> Now I am needing to look into sorting out remote access or simply disable all 
> updates, neither of which is ideal for any variety of reasons. 
> 
> Any clever suggestions which bring me back into a place where a few kernels 
> can easily install without things getting too crowded? 
> 
> Sent from my phone. Please forgive misspellings and weird “corrections”

ping

2022-11-13 Thread peter

root@joule:/home/root# /bin/ping -c 3  192.168.0.12
PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data.
64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms
64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms
64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

--- 192.168.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2041ms
rtt min/avg/max/mdev = 0.079/0.102/0.114/0.016 ms
root@joule:/home/root# echo $PATH
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
root@joule:/home/root# which ping
/bin/ping
root@joule:/home/root# ping -c 3  192.168.0.12

No response.

Ideas?

Thanks, ... Peter E.




mobile: +1 778 951 5147
  VoIP: +1 604 670 0140
https://en.wikibooks.org/wiki/User:PeterEasthope

Re: howto install Debian on software RAID1 when UEFI?

On Sun, Nov 13, 2022 at 02:49:28PM +0100, hw wrote:
> 
> Hi,
> 
> the Debian installer is horrible.  It won't let me install on software RAID1 
> on
> a server with an UEFI BIOS.  I can't find any good guide about that, either.
> 

Hi hw

You might want to *start* with using the expert install - found under the 
advanced menu option. That will give you more control, including advanced
partitioning.

> I want root on brtfs with RAID1.  How do I get Debian installed?

I'd suggest that you partition one disk with "all files in one partition"
as a test run to see the sizes you'll need and then rerun the partitioner.

>From memory, I think you end up with something like an EFI partition of 512M,
a root partition of (the rest - 1G) and then a 1G swap.

If you partition both disks to have an EFI partition at the beginning, then
a RAID partition, then 2 x 1G swap at the end.

Then use the RAID manager to set up RAID1 and LVM over the top. I'm unsure how
you would install GRUB to the second disk of the RAID - it might be that you'd
need to restart once the install is complete, use the rescue option and
specifically install GRUB on the second disk of the RAID.

> 
> The graphical version crashes with a kernel panic when booting from an USB
> stick, so I need to use the normal installer.

Then you have wider problems than just installation, perhaps?

> 
> There's even not a way to select RAID1 for btrfs.  What an anachronism ...
>

You do know that this is a general purpose installer that covers 12 or so
filesystem types and allows for flexibility?

With every good wish, as ever,

Andy Cater

Como va? Si, en algunos equipos pasa eso, pero no es en si un error sino
que el kernel tiene
el modulo activo pero falta el firmware (driver). Es un tema de ciertas
arquitecturas de Intel.
Solucion manual: vas aca
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/
y bajas todo lo que necesites a un directorio. Ejemplo: en el dir i915
vas a tener todos los archivos que

que te faltan para intel y en rt_nic lo mismo.
Los archivos que bajaste los tenes que copiar/mover a :
|/lib/firmware/rtl_nic/ o ||/lib/firmware/i915/ , o sea

en un terminal:
|

|sudo cp /directoriodebajada/*.fw /lib/firmware/rtl_nic/ |
||sudo cp /directoriodebajada/*.fw /lib/firmware/i915/ Y despues
cargarlos al initramfs : |sudo update-initramfs -u| El initramfs es un sistema de archivos
generado en RAM (un disco en RAM) donde residen todos los modulos
(drivers) del kernel. Por un tema de diseño los kernels se puede
compilar como monoliticos (con todo disponible pero muy grandes y
pesados) o como modulares (mas chicos y ligeros con todos los drivers
como modulos) La desventaja de esto ultimo es que si un hardware
necesitra su driver en el momento del boot todavia no va a estar
disponible. Por eso se hace este disco en RAM con todos lo modulos la
alcance del sistema. Aparentemente existe una solucion mas automatica
que consiste en agregar a los repositorios de apt la opcion non-free
pero por alguna razon no me ha resultado. No te aburro mas, espero que
sirva. Saludos ||

||
El 13/11/22 a las 09:34, Simeón Ignacio Martirén escribió:
Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for
module i915

--
*/Gerardo Braica
*/gbra...@gmail.com.ar
/*/*

howto install Debian on software RAID1 when UEFI?



Hi,

the Debian installer is horrible.  It won't let me install on software RAID1 on
a server with an UEFI BIOS.  I can't find any good guide about that, either.

I want root on brtfs with RAID1.  How do I get Debian installed?

The graphical version crashes with a kernel panic when booting from an USB
stick, so I need to use the normal installer.

There's even not a way to select RAID1 for btrfs.  What an anachronism ...

Re: does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

2022-11-13 Thread jindam, vani

On Sun, Nov 13, 2022 at 09:56:21AM +, jindam, vani wrote:
> i have only deb http://deb.debian.org/debian bullseye main contrib non-free 
> in my sources.list. 
> 
> does apt upgrade & full-upgrade packages from Security Updates (Debian 
> Security Advisories (DSA))?

> No, you have to add the security repo to your sources.

> which is correct?
> deb http://security.debian.org/debian-security bullseye-security main contrib 
> non-free (1)
> deb http://deb.debian.org/debian-security/ bullseye-security main contrib 
> non-free

I think it's the first one.

yes, thank you. both README.security (1)(2) on security.debian & deb.debian 
say samething... interesting. debian wiki (3) says 
otherwise, perhaps need to update it.

regards,
jindam, vani

toots: @jindam_v...@c.im
others: en.wikipedia.org/wiki/User:Jindam_vani


(1) http://deb.debian.org/debian-security/README.security
(2) https://security.debian.org/debian-security/README.security
(3) https://wiki.debian.org/SourcesList

> Cheers
>-- 
>t

Re: exim4 vs. frontier.com

2022-11-13 Thread Curt

On 2022-11-13, David Wright  wrote:
> On Sat 12 Nov 2022 at 13:41:35 (-), Curt wrote:
>> On 2022-11-12, David Wright  wrote:
>> >
>> > If and when that works, it should be simple to get exim to send
>> > to the smarthost in the same manner. It should involve only the
>> > two files /etc/exim4/{passwd.client,update-exim4.conf.conf} in
>> > most cases.
>> 
>> https://groups.google.com/g/linux.debian.user/c/bAI10SqfmGA
>> 
>> He asked the same question back in May but with some other data
>> points, not that it probably makes any difference.
>
> Yes, I referred to that, without citing it. However, the data points
> were related to exim, and also lacked much context.
>
> https://lists.debian.org/debian-user/2022/05/msg00193.html
>
> It's quite possible that the OP has messed up exim's configuration
> by tinkering with it, so I think it's simpler (and may give confidence
> that frontier.com is not particularly unusual) by sending something
> via mutt alone. Then the data used by mutt can be translated into
> the equivalents for exim.
>
> BTW this goes back somewhat further—does this ring a bell?
>
> https://lists.debian.org/debian-user/2018/07/msg00115.html

No, but the following thread I do remember vaguely:

https://linux.debian.user.narkive.com/3PRw93ts/email-lacks-sender-address

> Cheers,
> David.


--

Re: Falta de firmware

2022-11-13 Thread Parodper


O 13/11/22 ás 13:34, Simeón Ignacio Martirén escribiu:

Procesando disparadores para initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-19-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module

> [...]

W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module
r8169


Esto está en el paquete firmware-realtek.


W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for
module i915

> [...]

W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_02.bin for
module i915


Esto está en el paquete firmware-misc-nonfree.

Para esta clase de cosas es muy útil el programa apt-file.


W: initramfs-tools configuration sets
RESUME=UUID=dd7d3adf-3dab-4956-92a4-79943fefd136
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=f23cfe7c-7ccf-42d4-8062-dfc04548c9b6)
I: Set the RESUME variable to override this.


¿Has cambiado algún disco duro o partición? En principio no debería 
pasar nada, pero comprueba las entradas en /etc/fstab. Para saber los 
UUID puedes usar el comando «lsblk -o name,size,uuid». Probablemente 
también tengas que cambiar el UUID en /etc/initramfs-tools/conf.d/resume 
para que funcione la hibernación y suspensión.



Procesando disparadores para hicolor-icon-theme (0.17-2) ...
Procesando disparadores para gnome-menus (3.36.0-1) ...
Procesando disparadores para libc-bin (2.31-13+deb11u5) ...
Procesando disparadores para man-db (2.9.4-2) ...
Procesando disparadores para mailcap (3.69) ...
root@Bulls:/home/ign#

Con lo que no sé si en realidad la actualización del sistema se ha
completado y me generará problemas futuros.
Gracias mil desde ya.


La instalación se ha completado, y si no te falla nada no tienes por que 
instalar los paquetes de firmware, que además no son libres.

Falta de firmware

2022-11-13 Thread Simeón Ignacio Martirén

Hola lista. Soy usuario no experto. Trato de actualizar mi PC de escritorio
root@Bulls:/home/ign# sudo lshw
bulls
description: Desktop Computer
product: System Product Name (SKU)
vendor: System manufacturer
version: System Version
serial: System Serial Number
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: boot=normal chassis=desktop family=To be filled by
O.E.M. sku=SKU uuid=19646C73-8A37-1204-3086-74D02BCADC5E
  *-core
   description: Motherboard
   product: H61M-K
   vendor: ASUSTeK COMPUTER INC.
   physical id: 0
   version: Rev X.0x
   serial: 130713430608156
   slot: To be filled by O.E.M.
 *-firmware
  description: BIOS
  vendor: American Megatrends Inc.
  physical id: 0
  version: 0504
  date: 07/02/2013
  size: 64KiB
  capacity: 8MiB
  capabilities: pci upgrade shadowing cdboot bootselect socketedrom
edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
 *-cpu
  description: CPU
  product: Intel(R) Pentium(R) CPU G2020 @ 2.90GHz
  vendor: Intel Corp.
  physical id: 4
  bus info: cpu@0
  version: Intel(R) Pentium(R) CPU G2020 @ 2.90GHz
  serial: To Be Filled By O.E.M.
  slot: LGA1155
  size: 1631MHz
  capacity: 3800MHz
  width: 64 bits
  clock: 100MHz
  capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce
cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2
ss ht tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64
monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt
tsc_deadline_timer xsave lahf_lm cpuid_fault epb pti fsgsbase smep erms
xsaveopt dtherm arat pln pts cpufreq
  configuration: cores=2 enabledcores=1
*-cache:0
 description: L1 cache
 physical id: 5
 slot: L1-Cache
 size: 128KiB
 capacity: 128KiB
 capabilities: internal write-back unified
 configuration: level=1
*-cache:1
 description: L2 cache
 physical id: 6
 slot: L2-Cache
 size: 512KiB
 capacity: 512KiB
 capabilities: internal varies unified
 configuration: level=2
*-cache:2 DISABLED
 description: L3 cache
 physical id: 7
 slot: L3-Cache
 size: 3MiB
 capacity: 3MiB
 capabilities: internal unified
 configuration: level=3
(continua la devolución, muy larga, supongo innecesaria)


y me presenta esta situación:

root@Bulls:/home/ign# sudo apt-get update && apt-get upgrade
Obj:1 http://debian.unnoba.edu.ar/debian bullseye InRelease
Obj:2 http://debian.unnoba.edu.ar/debian bullseye-updates InRelease
Obj:3 http://security.debian.org/debian-security bullseye-security InRelease
Leyendo lista de paquetes... Hecho
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias... Hecho
Leyendo la información de estado... Hecho
Calculando la actualización... Hecho
Se actualizarán los siguientes paquetes:
  gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libavcodec58 libavfilter7
  libavformat58 libavresample4 libavutil56 libexpat1
  libjavascriptcoregtk-4.0-18 libntfs-3g883 libpixman-1-0 libpostproc55
  libswresample3 libswscale5 libwebkit2gtk-4.0-37 libxml2 ntfs-3g
thunderbird
  tzdata
19 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no
actualizados.
Se necesita descargar 0 B/86,1 MB de archivos.
Se liberarán 357 kB después de esta operación.
¿Desea continuar? [S/n] S
Leyendo lista de cambios... Hecho.
Preconfigurando paquetes ...
(Leyendo la base de datos ... 211222 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../00-tzdata_2021a-1+deb11u8_all.deb ...
Desempaquetando tzdata (2021a-1+deb11u8) sobre (2021a-1+deb11u7) ...
Preparando para desempaquetar
.../01-gir1.2-webkit2-4.0_2.38.2-1~deb11u1_amd64.deb ...
Desempaquetando gir1.2-webkit2-4.0:amd64 (2.38.2-1~deb11u1) sobre
(2.38.0-1~deb11u1) ...
Preparando para desempaquetar
.../02-gir1.2-javascriptcoregtk-4.0_2.38.2-1~deb11u1_amd64.deb ...
Desempaquetando gir1.2-javascriptcoregtk-4.0:amd64 (2.38.2-1~deb11u1) sobre
(2.38.0-1~deb11u1) ...
Preparando para desempaquetar
.../03-libwebkit2gtk-4.0-37_2.38.2-1~deb11u1_amd64.deb ...
Desempaquetando libwebkit2gtk-4.0-37:amd64 (2.38.2-1~deb11u1) sobre
(2.38.0-1~deb11u1) ...
Preparando para desempaquetar
.../04-libjavascriptcoregtk-4.0-18_2.38.2-1~deb11u1_amd64.deb ...
Desempaquetando libjavascriptcoregtk-4.0-18:amd64 (2.38.2-1~deb11u1) sobre
(2.38.0-1~deb11u1) ...
Preparando para desempaquetar
.../05-libxml2_2.9.10+dfsg-6.7+deb11u3_amd64.deb ...

Re: initrd sizes mushroomed several months ago

2022-11-13 Thread The Wanderer

On 2022-11-12 at 01:57, Felix Miata wrote:

> # grep MODULES= /etc/initramfs-tools/initramfs.conf
> MODULES=dep
> # ls -Ggh /boot/initrd.img-[5,6]*
> -rw-r--r-- 1 6.8M May  8  2022 /boot/initrd.img-5.17.0-1-686
> -rw-r--r-- 1  31M Aug  2 03:06 /boot/initrd.img-5.18.0-3-686
> -rw-r--r-- 1  31M Sep 30 15:43 /boot/initrd.img-5.19.0-2-686
> -rw-r--r-- 1  36M Nov 12 01:36 /boot/initrd.img-6.0.0-3-686
> 
> Does anyone here have an explanation for the mega-change in size of initrds 
> after
> kernel 5.17? My initramfs.conf has had MODULES=dep since before 
> testing/bullseye
> became testing/bookworm.

Just a stab in the dark, but:

The changelog history for linux-image-5.18.0-4-amd64, on my system,
gives the change from 5.17 to 5.18 as having happened in May of 2022.

The changelog for initramfs-tools, on my system, shows exactly one
version newer than May of 2022, released in July of 2022.

The changelog for that version of initramfs-tools (0.142) includes the
entry:

  [ Dimitri John Ledkov ]
  * [d8c5864] mkinitramfs: decompress compressed kernel modules

with no reason or other information given. (There are a few other
changes listed, which could also be relevant, but seem less obviously so
from the brief descriptions - although it is of course hard to judge.)

Just at first blush, it looks like something like that could produce an
increase in size, potentially a notable one.

(The previous version's changelog entry also switches compression to
zstd, but that version came out in April, so it's unlikely to be the
culprit.)

-- 
   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: does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

2022-11-13 Thread tomas

On Sun, Nov 13, 2022 at 09:56:21AM +, jindam, vani wrote:
> i have only deb http://deb.debian.org/debian bullseye main contrib non-free 
> in my sources.list. 
> 
> does apt upgrade & full-upgrade packages from Security Updates (Debian 
> Security Advisories (DSA))?

No, you have to add the security repo to your sources.

> which is correct?
> deb http://security.debian.org/debian-security bullseye-security main contrib 
> non-free (1)
> deb http://deb.debian.org/debian-security/ bullseye-security main contrib 
> non-free

I think it's the first one.

Cheers
-- 
t


signature.asc
Description: PGP signature

does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

2022-11-13 Thread jindam, vani

i have only deb http://deb.debian.org/debian bullseye main contrib non-free in 
my sources.list. 

does apt upgrade & full-upgrade packages from Security Updates (Debian Security 
Advisories (DSA))?

which is correct?
deb http://security.debian.org/debian-security bullseye-security main contrib 
non-free (1)
deb http://deb.debian.org/debian-security/ bullseye-security main contrib 
non-free


(1) https://www.debian.org/security/

regards,
jindam, vani

toots: @jindam_v...@c.im
others: en.wikipedia.org/wiki/User:Jindam_vani

Re: exim4 vs. frontier.com

On Sat 12 Nov 2022 at 13:41:35 (-), Curt wrote:
> On 2022-11-12, David Wright  wrote:
> >
> > If and when that works, it should be simple to get exim to send
> > to the smarthost in the same manner. It should involve only the
> > two files /etc/exim4/{passwd.client,update-exim4.conf.conf} in
> > most cases.
> 
> https://groups.google.com/g/linux.debian.user/c/bAI10SqfmGA
> 
> He asked the same question back in May but with some other data
> points, not that it probably makes any difference.

Yes, I referred to that, without citing it. However, the data points
were related to exim, and also lacked much context.

https://lists.debian.org/debian-user/2022/05/msg00193.html

It's quite possible that the OP has messed up exim's configuration
by tinkering with it, so I think it's simpler (and may give confidence
that frontier.com is not particularly unusual) by sending something
via mutt alone. Then the data used by mutt can be translated into
the equivalents for exim.

BTW this goes back somewhat further—does this ring a bell?

https://lists.debian.org/debian-user/2018/07/msg00115.html

Cheers,
David.

Re: Sysstemd question