tinue
with qcow2, and just note for future reference that I may need to do a
conversion every now and then. I see now that the "qemu-img" man page
actually acknowledges this:
"Image conversion is also useful to get smaller image when using a
growable format such as qcow: the empty sector
overed.
>
> If you need functionality that qcow2 provides and raw doesn't, then
> this isn't going to be a solution for you. However, converting the disk
> image (even from qcow2 to qcow2) *might* result in a smaller second
> disk image.
Okay - I tried running "qe
*less* (in addition to providing additional
functionality, such as snapshotting)?
It can be more efficient, and it can be less, as you've discovered.
If you need functionality that qcow2 provides and raw doesn't, then this
isn't going to be a solution for you. However, converting
; did claw back some space by doing so, but not nearly enough.
>
> Is 80G too big? If not, stop the VM, qemu-img convert -O raw in.img
> out.img ; then either something like `mv in.img old.img; mv out.img
> in.img` or edit your VM configuration to point at the new disk image.
Can you elabo
Subject: Recommended backup software to clone Android (Linux) phones to image
files
Good day from Singapore,
Acronis True Image backup software can be used to clone Windows 10 and 11 to
image files with the extension of .tibx.
I am wondering if Acronis True Image backup software can be used
@lists.debian.org
Subject: Re: apt: WTH is a "second pre-image resistance"?
On Mon, Jun 2, 2025 at 5:05 PM Darac Marjal wrote:
>
>
> On 02/06/2025 12:49, Harald Dunkel wrote:
> > Hi folks,
> >
> > trying Trixie "apt update" shows a warning about my loc
r/bin/sqv returned an error code (1), error message is:
> > Signing key on is not bound:
> >No binding signature at time 2025-06-02T09:32:30Z
> > because: Policy rejected non-revocation signature
> > (PositiveCertification
at time 2025-06-02T09:32:30Z
because: Policy rejected non-revocation signature (PositiveCertification)
requiring second pre-image resistance
because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
I know that SHA1 is not secure, but what is this resistance error me
is not bound:
> No binding signature at time 2025-06-02T09:32:30Z
> because: Policy rejected non-revocation signature
> (PositiveCertification) requiring second pre-image resistance
> because: SHA1 is not considered secure since 2026-02-01T00:00:
cy rejected non-revocation signature (PositiveCertification)
requiring second pre-image resistance
because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
I know that SHA1 is not secure, but what is this resistance error message
trying to tell me? InRelease is signed by a RSA4
qemu-img convert -O raw in.img
out.img ; then either something like `mv in.img old.img; mv out.img
in.img` or edit your VM configuration to point at the new disk image.
Remove the old one once you are satisfied the new one is working.
--
Please do not CC me for listmail.
👱🏻 Jon
The Windows OS has
> > undergone various repairs and reinstalls over the years. I was recently
> > quite surprised to discover that the VM image size (actual size on
> > disk, not apparent size) has somehow grown to about 4x the allocated
> > size of the disk:
...
>
t/2GiB.qcow2
# ls -ons /var/local/vtest/2GiB.qcow2
2099792 -rw--- 1 0 4296015872 May 20 02:09 /var/local/vtest/2GiB.qcow2
#
// It's sparse file, we got most all that spare space back.
// Now let's see if we can do likewise for data in the image, if we
replace it with something that
// c
Hi,
I have a QEMU / KVM VM running Windows that has been running as a guest
on various Debian hosts for about a decade. The Windows OS has
undergone various repairs and reinstalls over the years. I was recently
quite surprised to discover that the VM image size (actual size on
disk, not apparent
gt; >> Package failed to install:Error while installing package:
> >> installed linux-image-6.1.0-32-amd64 package post-installation script
> >> subprocess returned error exit status 1
> >
> > Then read backwards until you find the error message from the
> > su
Nicolas George writes:
> Barry Newberger (HE12025-03-24):
>> package: dpkg
>> version: 1.21.22 (amd64)
>>
>> Using Discover update following error occurred:
>>
>> Package failed to install:Error while installing package:
>> installed linux-image-6.
> update-initramfs: failed for /boot/initrd.img-6.1.0-32-amd64 with 1.
> > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> > dpkg: error processing package linux-image-6.1.0-32-amd64 (--configure):
> > installed linux-image-6.1.0-32-amd64 package
ts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
> dpkg: error processing package linux-image-6.1.0-32-amd64 (--configure):
> installed linux-image-6.1.0-32-amd64 package post-installation script
> subprocess returned error exit status 1
> Setting up linux-imag
Barry Newberger (HE12025-03-24):
> package: dpkg
> version: 1.21.22 (amd64)
>
> Using Discover update following error occurred:
>
> Package failed to install:Error while installing package:
> installed linux-image-6.1.0-32-amd64 package post-installation script
> subpro
On Mon, Mar 24, 2025 at 08:05:32 -0500, Barry Newberger wrote:
> Setting up linux-image-6.1.0-32-amd64 (6.1.129-1) ...
> /etc/kernel/postinst.d/dkms:
> dkms: running auto installation service for kernel 6.1.0-32-amd64.
> dkms: autoinstall for kernel: 6.1.0-32-amd64.
> /etc/ke
package: dpkg
version: 1.21.22 (amd64)
Using Discover update following error occurred:
Package failed to install:Error while installing package:
installed linux-image-6.1.0-32-amd64 package post-installation script
subprocess returned error exit status 1
Ran following:
uname -r
6.1.0-31-amd64
First of all thanks to Dan Ritter that replied to my original post but
yet I can't find his reply in the debian-user list.
On Mon, Jun 03, 2024 at 10:32:27PM -0400, A. F. Cano wrote:
>
> I'm trying to get these Lorex SR AIS color cameras, that are supposedly
> capable of 1024 x 768 max and 728 x
Hi,
William Torrez Corea wrote:
> I make a disk image but this makes a backup of free space and full space of
> the disk.
> I am using dd (Unix) and using gnome-disk-utility.
> How can I make a disk image of selected data?
> I don't want to make a backup of the entire disk.
On 12/1/24 10:19, William Torrez Corea wrote:
I make a disk image but this makes a backup of free space and full space of
the disk.
I am using dd (Unix) and using gnome-disk-utility.
How can I make a disk image of selected data?
I don't want to make a backup of the entire disk.
I use
I make a disk image but this makes a backup of free space and full space of
the disk.
I am using dd (Unix) and using gnome-disk-utility.
How can I make a disk image of selected data?
I don't want to make a backup of the entire disk.
--
With kindest regards, William.
*Larry Wall inven
On Sun, 15 Sep 2024 21:04:18 +0200
Christian Britz wrote:
> Am 09.09.24 um 10:27 schrieb David:
>
> > `apt auto-remove'
>
> You generally might want apt --purge auto-remove
> This also cleans up configuration files.
Which is the same as "apt autopurge", which I suggested earlier in this
thre
Am 09.09.24 um 10:27 schrieb David:
> `apt auto-remove'
You generally might want apt --purge auto-remove
This also cleans up configuration files.
On Mon, 2024-09-09 at 11:04 +0300, Anssi Saari wrote:
> Charles Curley writes:
>
> > apt purge linux-image-amd64 linux-headers-amd64
> > apt install linux-image-amd64 linux-headers-amd64
> >
> > You may want an "apt autopurge" in between.
>
>
On Mon, 2024-09-09 at 11:04 +0300, Anssi Saari wrote:
> Charles Curley writes:
>
> > apt purge linux-image-amd64 linux-headers-amd64
> > apt install linux-image-amd64 linux-headers-amd64
> >
> > You may want an "apt autopurge" in between.
>
>
Charles Curley writes:
> apt purge linux-image-amd64 linux-headers-amd64
> apt install linux-image-amd64 linux-headers-amd64
>
> You may want an "apt autopurge" in between.
That should do it although it's apt autoremove I believe but if not you
can explicitly remov
On Fri, 6 Sep 2024 16:39:46 -0600
Rick Macdonald wrote:
> Well, this is embarrassing. I found in the bash history that I ran
> this:
>
> apt install -t bookworm-backports linux-image-amd64
> linux-headers-amd64
>
> Sorry to sound so lame, but I do I remove the backpor
Well, this is embarrassing. I found in the bash history that I ran this:
apt install -t bookworm-backports linux-image-amd64 linux-headers-amd64
but I have no idea why. The timestamp of the deb file is July 18. I
don't remember why I did this. Getting old sucks. Looking at the
histor
any bugs reported.
>
> The 6.10.6 image fails to build:
>
> Errors were encountered while processing:
> linux-image-6.10.6+bpo-amd64
> linux-image-amd64
> linux-headers-6.10.6+bpo-amd64
> linux-headers-amd64
Is there some reason to run the backport kernel? Maybe just run wi
I'm running an up-to-date Bookworm desktop. I have an NVIDIA GeForce GTX
760 (192-bit) using the NVIDIA Driver Version 470.256.02, coming from
the nvidia-tesla-470 packages. I've searched this list and the package
pages and don't see any bugs reported.
The 6.10.6 image
Andrew M.A. Cater wrote:
> If you have problems after using a live image, it might be that the first
> of those was to use a live image :(
>
> The netinst and DVD installers are more mature and potentially better tested.
> The live installer generally relies on different code if yo
On Thu, Aug 15, 2024 at 06:45:33AM -0400, songbird wrote:
> Mike wrote:
>
> > I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
> > hardware. On the way to getting it installed, it was suddenly rebooting.
> > I even got so far as installing it
Mike wrote:
> I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
> hardware. On the way to getting it installed, it was suddenly rebooting.
> I even got so far as installing it and running "apt upgrade", when it
> rebooted again.
>
> Then tha
I'll call this "resolved", not "solved".
> I'll let it run for awhile before I believe that.
I ran the -23- kernel for four days without issue. Then I rebooted into the
previous -22- kernel, still installed. That has run for a day so far. So
the problems no longer seem to be present.
I don't
On Fri, Aug 09, 2024 at 06:23:41PM +1000, George at Clug wrote:
> run a memory test.
Did that already, right after the build. Memtest86+.
Also ran S-TUI stress for awhile. Temps never got above 60C.
> Intel have been experiencing some instability
That's only affected their "K" and "S" series
On Fri, Aug 9, 2024 at 1:37 AM Mike wrote:
>
> I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
> hardware. On the way to getting it installed, it was suddenly rebooting.
> I even got so far as installing it and running "apt upgrade", when it
>
ards, there should be no updates to apply. Your
comment "Then that upgraded linux-image-6.1.0-22-amd64 to -23-" does concern
me, I would prefer to start with a new, clean, working installation, even if
that means installing all over again.
George.
On Friday, 09-08-2024 at 15:09 Mi
I just installed Debian 12.6.0 (from a Debian Live ISO image) on new server
hardware. On the way to getting it installed, it was suddenly rebooting.
I even got so far as installing it and running "apt upgrade", when it
rebooted again.
Then that upgraded linux-image-6.1.0-22-amd64 to
On 4/8/24 09:31, Keith Bainbridge wrote:
I've seen that some recent kernel has had trouble so I thought I'd
report some good news
Error
Update
My vboxdrv module has disappeared. I don't have time this side of a 4
week trip to try to sort it. I'll look for help when I got home.I
On 8/6/24 18:40, cor...@free.fr wrote:
Hi
My Image Viewer on desktop seems not to support webp format.
do you have any ideas?
You might need the package "webp-pixbuf-loader".
"webp-pixbuf-loader integrates libwebp library into GDK image processing
framework, so GDK based appl
On Wed, 2024-08-07 at 06:40 +0800, cor...@free.fr wrote:
> Hi
Hullo,
> My Image Viewer on desktop seems not to support webp format.
> do you have any ideas?
It depends on what you want to do with it, but GIMP can handle webp,
and export to any othwer format you may find easier to handle.
Cheers!
Hi
My Image Viewer on desktop seems not to support webp format.
do you have any ideas?
Thank you.
--
corey hickman
told by it that burn has not been enabled yet.
Xfburn is for optical media, not for memory cards.
Whatever, if the exact message is
"Burn mode is not currently implemented."
in the "Burn image" box, then click at the circle arrow button next to
the media type display. That
rn has not been enabled yet.
Xfburn is for optical media, not for memory cards.
Whatever, if the exact message is
"Burn mode is not currently implemented."
in the "Burn image" box, then click at the circle arrow button next to
the media type display. That's where
I've seen that some recent kernel has had trouble so I thought I'd
report some good news
--
All the best
Keith Bainbridge
keithr...@gmail.com
keith.bainbridge.3...@gmail.com
+61 (0)447 667 468
UTC + 10:00
Am 25.07.2024 um 06:52 schrieb Sam Lander:
> Rackspace Xen 4.7 linux-image-4.19.0-26-cloud-amd64 works,
> linux-image-4.19.0-27-cloud-amd64 does not work.
FWIW: I do not use the *clowd* kernels, but the regular ones in my VM's:
> uname -a
> Linux SuperServer 4.19.0-27-am
Summary
Rackspace Xen 4.7 linux-image-4.19.0-26-cloud-amd64 works,
linux-image-4.19.0-27-cloud-amd64 does not work.
I am running Buster on Rackspace inside a 1GB basic model VM
At the end of June, linux-image-4.19.0-27-cloud-amd64 was added as a
security update
My unattended-upgrades script
On Wed, Jul 24, 2024 at 12:33:51PM +0200, Aleix Piulachs wrote:
> How do you install them and tell me the characteristics of your computer
>
> El El mié, 17 jul 2024 a las 2:38, Greg Wooledge
> escribió:
>
> > On Tue, Jul 16, 2024 at 19:30:20 -, Prajnanaswaroopa wrote:
> > > Hello,
> > > I a
How do you install them and tell me the characteristics of your computer
El El mié, 17 jul 2024 a las 2:38, Greg Wooledge
escribió:
> On Tue, Jul 16, 2024 at 19:30:20 -, Prajnanaswaroopa wrote:
> > Hello,
> > I am using a Kali Linux
>
> https://www.google.com/search?q=kali+linux+support
>
>
problems - leaving unconfigured
Setting up linux-image-6.8.11-rt-amd64-dbg (6.8.11-1kali2) ...
Setting up linux-image-6.8.11-rt-amd64 (6.8.11-1kali2) ...
I: /initrd.img.old is now a symlink to
boot/initrd.img-6.8.11-rt-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto
On Tue, Jul 16, 2024 at 19:30:20 -, Prajnanaswaroopa wrote:
> Hello,
> I am using a Kali Linux
https://www.google.com/search?q=kali+linux+support
on linux-headers-6.8.11-amd64
(= 6.8.11-1kali2); however:
Package linux-headers-6.8.11-amd64 is not configured yet.
dpkg: error processing package linux-headers-amd64
(--configure):
dependency problems - leaving unconfigured
Setting up linux-image-6.8.11-rt-amd64-dbg (6.8.11
Hello,
I am trying to create a custom raspberry image starting from the code here
https://salsa.debian.org/raspi-team/image-specs
I added the ansible step in this file raspi_master.yaml:
- apt: install
packages:
- ansible
- python3
- ca-certificates
- dosfstools
Torito boot image which
serves also as EFI system partition.
The same is done by MBR partition 2. So (cd0,msdos2) is plausible.
MBR partition 1 marks the whole ISO filesystem. It has type 0x00 because
some software hates when partition 1 encloses partition 2. So it is
plausible that (cd0,msdos1) is not
A. F. Cano wrote:
>
> I hope this is the proper forum to post this. The more relevant lists
> of years ago are no longer active:
>
> https://www.linuxtv.org/lists.php
>
> I'm trying to get these Lorex SR AIS color cameras, that are supposedly
> capable of 1024 x 768 max and 728 x 488 NTSC, to
D" devices are for audio. Still, I have plugged in 4 cameras
at a time in the 4 blue coax plugs, labeled VID 1-4, and the 4 green
coax plugs, labeled VID 1-4. and no image shows up when running ffplay
or vlc, on any of the video[0-7] interfaces. I hope it's just the lack
of the proper o
Moving this to the debian-user list and setting reply-to accordingly...
On Fri, Feb 09, 2024 at 12:25:15PM +, guido mezzalana wrote:
>Hello
>
>First of all I wish to thank you all Debian's Team! To still enjoy a free OS:)
>
>I am running Ubuntu XFCE and I am using the Dis
Hi Sven,
Sven Joachim writes:
> On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
>
>> (Please keep me in CC as I'm not subscribed to the users ML.)
>>
>> Hi,
>>
>> TL;DR I've been experience stuck file system operations on cifs mount on
>> latest
On 2024-01-30 10:52 -0800, Xiyue Deng wrote:
> (Please keep me in CC as I'm not subscribed to the users ML.)
>
> Hi,
>
> TL;DR I've been experience stuck file system operations on cifs mount on
> latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
&
(Please keep me in CC as I'm not subscribed to the users ML.)
Hi,
TL;DR I've been experience stuck file system operations on cifs mount on
latest stable kernel (linux-image-6.1.0-17-amd64, 6.1.69-1), and would
like to see if other people are seeing similar issue before actually
fi
server that upgraded. I haven't set any
> special policies on upgrades.
I saw similar here. Of four machines here running Bookworm, three have
kernels:
linux-image-6.1.0-15-amd64 6.1.66-1
linux-image-6.1.0-16-amd64 6.1.67-1
but one has:
linux-image-6.1.0-13-amd64 6.1.55-1
linux-image-6.1
On Thu, Dec 21, 2023 at 09:02:34AM -0500, Gary Dale wrote:
> Several days ago my main server upgraded to kernel 6.1.0-16 but various
> other devices that are also running Bookworm seem stuck at 6.1.0-13. They
> are all using the same architecture. Some are using the same mirror as the
> server that
Several days ago my main server upgraded to kernel 6.1.0-16 but various
other devices that are also running Bookworm seem stuck at 6.1.0-13.
They are all using the same architecture. Some are using the same mirror
as the server that upgraded. I haven't set any special policies on upgrades.
Can
Hi Greg
> Sent: Tuesday, December 12, 2023 at 2:43 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: From which kernel should I upgrade my installed Debian to
> linux-image-6.1.0-15-amd64?
>
> On Mon, Dec 11, 2023 at 07:38:02PM +0100, St
On 11 Dec 2023 21:45 -0700, from charlescur...@charlescurley.com (Charles
Curley):
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
And from the looks of that bug report thread, message #72 onwards,
there is now a candidate fix.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105796
On Tue, Dec 12, 2023 at 06:04:04AM +0800, jeremy ardley wrote:
[...]
> If you look at the NTFS file system [...]
> Underneath the hood of a NTFS file is alternate data streams (ADS). That is
> a single file can contain main different 'sub files' of completely different
> content type. Each ADS h
On Tue, 12 Dec 2023 04:15:33 +
Tom Furie wrote:
> Do we know yet which wifi drivers are "troublesome"? I haven't seen
> anything concrete yet anywhere.
You can read the gory details at Mr. Price's bug report.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057967
--
Does anybody read si
Kevin Price writes:
> 6.1.0-15 brought not only the ext4-bugfix, but along with it introduced
> a terrible new bug: Most computers work fine with -15, except for some
> of those that have wifi, depending upon the driver. There was a certain
> change in Linux's cfg80211 kernel module, which contro
Hey Stella, hey all:
Am 11.12.23 um 19:38 schrieb Stella Ashburne:
> Thank goodness it only happens once in a blue moon.
May I please clarify some basic (mis-)conceptions?
There's "linux-image-amd64". This is a metapackage that contains nothing
but a constructed dependen
On 12/12/23 01:49, Jeremy Nicoll wrote:
There's no concept of filetype in file systems used for the MVS side
of z/OS systems. (These days there's also Unix/Linux environments
& of course they do have more familiar file naming structures.)
If you look at the NTFS file system - supported by m
debian-u...@howorth.org.uk wrote:
> songbird wrote:
>> wrote:
>> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
>> >> wrote:
>>
>> there is rarely a need to e-mail me directly.
>>
>> >> ...
>> >> > That's why I cringe when people name executables "foo.sh". What
>> >> > do
On Mon, Dec 11, 2023 at 07:38:02PM +0100, Stella Ashburne wrote:
> Please see Greg's reply to my other post (URL:
> https://lists.debian.org/debian-user/2023/12/msg00640.html).
>
> For your convenience, I quote a section of his reply (see below):
>
> "Yes, because
Hi Andy
> Sent: Monday, December 11, 2023 at 11:25 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: From which kernel should I upgrade my installed Debian to
> linux-image-6.1.0-15-amd64?
>
>
> If you're not currently boo
On Mon, 11 Dec 2023, at 13:16, Greg Wooledge wrote:
> 4) File extensions are used by programs on every operating system.
Certainly on many OSes, but not all.
They're not present on native RISC OS systems (as in ex-Acorn micros).
Filetype data IS stored, but it is in files' metadata.
There's n
Foster wrote:
> > > > > > On Fri, Dec 08, 2023 at 11:04:54AM -0600, David Wright wrote:
> > > > > > On Fri 08 Dec 2023 at 11:56:12 (-0500), Paul M Foster wrote:
> > > > > > > I'm on Debian bookworm, using neomutt for email. Where th
On Mon, Dec 11, 2023 at 10:10:31AM -0500, Stefan Monnier wrote:
[...]
> I think what you're saying is that it would make sense to use
> a dedicated extension for executables, like, say, `.exe`,
> since "all users rely on it being" executable.
I'd prefer ".com", but hey ;-)
> FWIW, I agree, but
On Mon, Dec 11, 2023 at 02:25:23PM +0100, Kevin Price wrote:
> Am 11.12.23 um 14:16 schrieb Stella Ashburne:
> > Suppose I wish to upgrade to linux-image-6.1.0-15-amd64.
>
> If that were the case, or maybe better to a newer one.
>
> > Should I do it after booting my d
. As for
test=test -n "$DISPLAY", I presume it's there to prevent trying to
run graphical commands on a text terminal, where DISPLAY is unset.
> image/*; (mv %s %s-\; feh -Z %s-\; rm -f %s-)& sleep 0.2s; test=test
> -n "$DISPLAY"
I've never trusted feh since
songbird wrote:
> wrote:
> > On Sun, Dec 10, 2023 at 01:28:20PM -0500, songbird wrote:
> >> wrote:
>
> there is rarely a need to e-mail me directly.
>
> >> ...
> >> > That's why I cringe when people name executables "foo.sh". What
> >> > do you do when you decide to rewrite the thing i
On 2023-12-11 09:34:09 -0500, Pocket wrote:
> On 12/11/23 09:04, Vincent Lefevre wrote:
> > On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> > > 2) When *receiving* email, mutt will use the sender's MIME type label
> > > to decide how to deal with the attachment.
> > But the notion of filen
> (Note that I'd even make a difference: where the implementation matters,
> e.g. some shell code to be sourced in, I'd be more lenient in calling
> the thing ".sh": after all, its users rely on it being shell code. When
> you can change the implementation without changing the function, e.g.
> a sh
:56:12 (-0500), Paul M Foster wrote:
I'm on Debian bookworm, using neomutt for email. Where there is an image to
view, viewing it in neomutt calls up one of the ImageMagick programs. I've set
the mailcap_path variable in my neomutt config to point to ~/.mailcap,
Similarly, I point it to
On Mon, Dec 11, 2023 at 08:52:37AM -0600, David Wright wrote:
> On Sun 10 Dec 2023 at 15:51:02 (-0500), Pocket wrote:
[...]
> > File names in Linux are a character string of 255 chars. Again there are
> > not file extensions in a Linux file name.
> >
> > People are conflating the issue.
> >
>
Dec 2023 at 11:56:12 (-0500), Paul M Foster wrote:
> >>>>
> >>>> I'm on Debian bookworm, using neomutt for email. Where there is an image
> >>>> to
> >>>> view, viewing it in neomutt calls up one of the ImageMagick programs.
> >&g
problematic kernel, linux-image-6.1.0-14-amd64
> (6.1.64-1)]
>
*snip* *snip*
>
>
> If you removed linux-image-6.1.0-14-amd64 and linux-image-amd64 as I'm
> sure many people did, then in order to get back to normalcy, you would
> have to reinstall the linux-image-amd64 me
On 12/11/23 09:34, Vincent Lefevre wrote:
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
I do not care about the "microsoft world", and I doubt that this is
required there at the low level (what would be the equivalent of
On Mon, Dec 11, 2023 at 03:34:28PM +0100, Vincent Lefevre wrote:
> On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> > On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > > I do not care about the "microsoft world", and I doubt that this is
> > > required there at the low lev
On 2023-12-11 15:16:57 +0100, to...@tuxteam.de wrote:
> On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
> > I do not care about the "microsoft world", and I doubt that this is
> > required there at the low level (what would be the equivalent of the
> > Linux kernel) [...]
>
> This
On 12/11/23 09:04, Vincent Lefevre wrote:
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
2) When *receiving* email, mutt will use the sender's MIME type label
to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quoting the
On Mon, Dec 11, 2023 at 02:58:01PM +0100, Vincent Lefevre wrote:
[...]
> I do not care about the "microsoft world", and I doubt that this is
> required there at the low level (what would be the equivalent of the
> Linux kernel) [...]
This depends: the FAT file system (which still is the lowest c
On Mon, Dec 11, 2023 at 02:35:07PM +0100, Stella Ashburne wrote:
> Suppose linux-image-6.1.0-15-amd64 is installed successfully and I reboot my
> device.
>
> A few days from now, I decide to remove linux-image-6.1.0-15-amd64 because it
> is buggy and so in a terminal, I ty
On 2023-12-11 08:16:30 -0500, Greg Wooledge wrote:
> 2) When *receiving* email, mutt will use the sender's MIME type label
>to decide how to deal with the attachment.
But the notion of filename extension is even used in this context too.
Quoting the Mutt manual:
--
On 2023-12-11 07:32:30 -0500, Pocket wrote:
>
> On 12/11/23 07:12, Vincent Lefevre wrote:
> > On 2023-12-10 15:51:02 -0500, Pocket wrote:
> > > On Dec 10, 2023, at 3:05 PM, David Wright
> > > wrote:
> > > > ¹ Re the argument raging in this thread about "extension", the
> > > > term is clearly
Hi Andy
> Sent: Monday, December 11, 2023 at 3:13 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Release process notes [WAS Re: Need clarifications about how to deal
> with the installed problematic kernel, linux-image-6.1.0-14-amd64 (6.1
Am 11.12.23 um 14:16 schrieb Stella Ashburne:
> Suppose I wish to upgrade to linux-image-6.1.0-15-amd64.
If that were the case, or maybe better to a newer one.
> Should I do it after booting my device into
> (1) linux-image-6.1.0-14-amd64 (the problematic kernel)
NO. Don't ever b
On Mon, Dec 11, 2023 at 02:16:39PM +0100, Stella Ashburne wrote:
> (3) doesn't matter which kernel to upgrade from
That.
1 - 100 of 1809 matches
Mail list logo
