On Tue, Mar 25, 2025 at 12:27 AM Xiyue Deng wrote:
>
> 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:
> >>
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.1.0-32-amd64 package post-installation script
On Mon, Mar 24, 2025 at 04:56:33PM CET, Felix Miata said:
> Barry Newberger composed on 2025-03-24 08:05 (UTC-0500):
> ...
> > update-initramfs: Generating /boot/initrd.img-6.1.0-32-amd64
> > cpio: write error: No space left on device
> > E: mkinitramfs failure cpio 2
>
Barry Newberger composed on 2025-03-24 08:05 (UTC-0500):
...
> update-initramfs: Generating /boot/initrd.img-6.1.0-32-amd64
> cpio: write error: No space left on device
> E: mkinitramfs failure cpio 2
> update-initramfs: failed for /boot/initrd.img-6.1.0-32-amd64 with 1.
> run-par
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
> subprocess returned error exit s
rnel/postinst.d/initramfs-tools:
> update-initramfs: Generating /boot/initrd.img-6.1.0-32-amd64
> cpio: write error: No space left on device
> E: mkinitramfs failure cpio 2
Either one of your file systems needs to be cleaned out, or there's
something *odd* happening. Hopefully it's the former.
: mkinitramfs failure cpio 2
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 post
> from the menu, or skip it and choose something else. The failing step
> > is: Select and install software
> >
> > This failure occurs during the "Select and install software" stage. The
> > root cause is an attempt to install security updates from th
om the official DVD ISO
> fails with the following error:
>
> Installation step failed
> An installation step failed. You can try to run the failing item again
> from the menu, or skip it and choose something else. The failing step
> is: Select and install software
>
> Thi
om the official DVD ISO
> fails with the following error:
>
> Installation step failed
> An installation step failed. You can try to run the failing item again
> from the menu, or skip it and choose something else. The failing step
> is: Select and install software
>
> Thi
ation step failed. You can try to run the failing item again
from the menu, or skip it and choose something else. The failing step
is: Select and install software
This failure occurs during the "Select and install software" stage. The
root cause is an attempt to install security updates fr
On 11/18/24 12:45, Gupta, Tulika wrote:
Dear support team
I have purchased a new APC UPS which I want to connect with four Linux Debian
clusters.
The APC UPS Model: SURTD3000XLIM (APC model) has one serial com connector and
one USB connector on the back of the UPS. Two cables were provided al
On Mon, 18 Nov 2024 11:45:33 +
"Gupta, Tulika" wrote:
> The APC UPS Model: SURTD3000XLIM (APC model) has one serial com
> connector and one USB connector on the back of the UPS. Two cables
> were provided alongwith the UPS purchase- a) RJ-45 to DB-9
> communication cable (goes to the serial c
Dear support team
I have purchased a new APC UPS which I want to connect with four Linux Debian
clusters.
The APC UPS Model: SURTD3000XLIM (APC model) has one serial com connector and
one USB connector on the back of the UPS. Two cables were provided alongwith
the UPS purchase- a) RJ-45 to DB-
+
> 2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_check: DNS error: -3, Temporary failure in name resolution
> 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS:
> dns_take_status: None=>temp, 3
> 2024-03-06T14:58:19.572547+0
ntpd[35823]: DNS:
dns_check: DNS error: -3, Temporary failure in name resolution
2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_take_status: None=>temp, 3
2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS:
dns_probe: None, cast_flags:1, flags:20801
2024
This is a post meant to help anyone who finds his/her system unbootable
- as I did - after updating to the latest version of the testing stream
which comes with a 6.6.13-amd64 kernel.
When I updated last week, my system refused to boot. Checking revealed
that the system-load-modules service wa
Curt writes:
> Yet the reserved gTLDs from the 2018 ICANN resolution are .home, .corp,
> and .mail. Does home.arpa comply with that resolution?
Yes. Turns out that there were existing uses of '.home'. Also, putting
it under 'arpa.' puts it under IETF control.
https://datatracker.ietf.org/doc/ht
Curt wrote:
> On 2024-01-12, debian-u...@howorth.org.uk
> wrote:
> > Curt wrote:
> >> On 2024-01-11, Max Nikulin wrote:
> >> >
> >> > There was a thread that "home" as the top level domain might not
> >> > be really safe (somebody might register it). A reserved domain
> >> > is "home.arpa"
On Fri, Jan 12, 2024 at 12:33 PM wrote:
>
> Jeffrey Walton wrote:
> > On Fri, Jan 12, 2024 at 11:08 AM Curt wrote:
> > >
> > > On 2024-01-12, debian-u...@howorth.org.uk
> > > wrote:
> > > > Curt wrote:
> > > >> On 2024-01-11, Max Nikulin wrote:
> > > >> >
> > > >> > There was a thread that "h
Jeffrey Walton wrote:
> On Fri, Jan 12, 2024 at 11:08 AM Curt wrote:
> >
> > On 2024-01-12, debian-u...@howorth.org.uk
> > wrote:
> > > Curt wrote:
> > >> On 2024-01-11, Max Nikulin wrote:
> > >> >
> > >> > There was a thread that "home" as the top level domain might
> > >> > not be real
On Fri, Jan 12, 2024 at 11:08 AM Curt wrote:
>
> On 2024-01-12, debian-u...@howorth.org.uk wrote:
> > Curt wrote:
> >> On 2024-01-11, Max Nikulin wrote:
> >> >
> >> > There was a thread that "home" as the top level domain might not be
> >> > really safe (somebody might register it). A reserved
On 2024-01-12, debian-u...@howorth.org.uk wrote:
> Curt wrote:
>> On 2024-01-11, Max Nikulin wrote:
>> >
>> > There was a thread that "home" as the top level domain might not be
>> > really safe (somebody might register it). A reserved domain is
>> > "home.arpa" so e.g. to have "thinkpad", the
On Fri, Jan 12, 2024 at 11:24:53AM +, debian-u...@howorth.org.uk wrote:
> Curt wrote:
> > On 2024-01-11, Max Nikulin wrote:
> > >
> > > There was a thread that "home" as the top level domain might not be
> > > really safe (somebody might register it). A reserved domain is
> > > "home.arpa"
Curt wrote:
> On 2024-01-11, Max Nikulin wrote:
> >
> > There was a thread that "home" as the top level domain might not be
> > really safe (somebody might register it). A reserved domain is
> > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should
> > be
> >
> > 127.0.1.1 t
On 11/01/2024 10:19, Greg Wooledge wrote:
On Thu, Jan 11, 2024 at 10:10:43AM +0700, Max Nikulin wrote:
On 11/01/2024 03:25, Greg Wooledge wrote:
On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote:
Greg Wooledge writes:
What is the output of "grep -F $(hostname) /etc/hosts"?
Am 11.01.2024 um 16:34:01 Uhr schrieb Curt:
> On 2024-01-11, Max Nikulin wrote:
> >
> > There was a thread that "home" as the top level domain might not be
> > really safe (somebody might register it). A reserved domain is
> > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should
On 2024-01-11, Max Nikulin wrote:
>
> There was a thread that "home" as the top level domain might not be
> really safe (somebody might register it). A reserved domain is
> "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should be
>
> 127.0.1.1 thinkpad.home.arpa thinkpad
>
On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote:
> Greg Wooledge writes:
>
> > On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote:
> >> writes:
> >> > Where/how does this error message "appear"?
> >>
> >> As an output of the `startx' command.
> >
> > It would be lovel
On Thu 11 Jan 2024 at 10:10:43 (+0700), Max Nikulin wrote:
> There was a thread that "home" as the top level domain might not be
> really safe (somebody might register it). A reserved domain is
> "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should be
>
> 127.0.1.1 thinkpad.h
On Thu, Jan 11, 2024 at 10:10:43AM +0700, Max Nikulin wrote:
> On 11/01/2024 03:25, Greg Wooledge wrote:
> > On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote:
> > > Greg Wooledge writes:
> > > > What is the output of the "hostname" command?
> > >
> > > It's: `thinkpad'.
> > >
> > >
On 11/01/2024 03:25, Greg Wooledge wrote:
On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote:
Greg Wooledge writes:
What is the output of the "hostname" command?
It's: `thinkpad'.
What is the output of "grep -F $(hostname) /etc/hosts"?
127.0.1.1 caterina-thinkpad.home
On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote:
> Greg Wooledge writes:
> > What is the output of the "hostname" command?
>
> It's: `thinkpad'.
>
> > What is the output of "grep -F $(hostname) /etc/hosts"?
>
> It's:
>
> 127.0.1.1 caterina-thinkpad.home caterina-thinkpad
Am 10.01.2024 um 19:19:41 Uhr schrieb Rodolfo Medina:
> > What is the output of "grep -F $(hostname) /etc/hosts"?
>
> It's:
>
> 127.0.1.1 caterina-thinkpad.home caterina-thinkpad
Add
::1 localhost localhost.localdomain ip6-localhost ip6-loopback
127.0.0.1 localhost localhos
Greg Wooledge writes:
> On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote:
>> writes:
>> > Where/how does this error message "appear"?
>>
>> As an output of the `startx' command.
>
> It would be lovely to see the *entire* error message, in case some part
> of it identifies the prog
On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote:
> writes:
> > Where/how does this error message "appear"?
>
> As an output of the `startx' command.
It would be lovely to see the *entire* error message, in case some part
of it identifies the program that produced the error. Many
writes:
> On Wed, Jan 10, 2024 at 06:13:55PM +, Rodolfo Medina wrote:
>> Debian 12 on Thinkpad T450s.
>>
>> The error message `Temporary failure in name resolution' appears whenever I
>> log into X with `startx' at prompt after boot, but it *only* occu
On Wed, Jan 10, 2024 at 06:13:55PM +, Rodolfo Medina wrote:
> Debian 12 on Thinkpad T450s.
>
> The error message `Temporary failure in name resolution' appears whenever I
> log
> into X with `startx' at prompt after boot, but it *only* occurs if the PC is
>
Debian 12 on Thinkpad T450s.
The error message `Temporary failure in name resolution' appears whenever I log
into X with `startx' at prompt after boot, but it *only* occurs if the PC is
*not* connected to internet; otherwise it does not appear; nevertheless, it
annoys me and I wish to
wipe/ fresh install/ configure/
restore data.
I would go even farther. Backups should be designed such that
recovering from a catastrophic storage failure, such as getting hit by
ransomware, unintentionally doing a destructive badblocks write test
or the sudden failure of a storage device, is pos
ipe/ fresh install/ configure/
> restore data.
I would go even farther. Backups should be designed such that
recovering from a catastrophic storage failure, such as getting hit by
ransomware, unintentionally doing a destructive badblocks write test
or the sudden failure of a storage device, is po
On 04/12/2023 23:41, Max Nikulin wrote:
Installing of libpam-fscrypt caused authentication failures:
dovecot[72165]: auth-worker: Error: fatal error: failed to reserve page
summary memory
dovecot[72165]: auth-worker: Error:
dovecot[72165]: auth-worker: Error: runtime stack:
dovecot[72165]: aut
authentication failure. I can not figure out
if it is pam_fscrypt or dovecot auth-worker failure, e.g. improper
compile or link options, perhaps some runtime protections intended to
prevent memory leaks or some sort of attack.
; 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 noprefixroute
> valid_lft forever preferred_lft forever
>
> 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen
> 1000
>link/sit 0.0.0.0 brd 0.0.0.0
>
> 3: enX0: mtu 1500 qdisc
> pfifo_fast state UP group default
> qlen 1000
>link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff
>inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0
> valid_lft forever preferred_lft forever
>inet6 fe80::216:3eff:fe12:3456/64 scope link
> valid_lft forever preferred_lft forever
>
> root@bookworm:~# ping google.it
> ping: google.it: Temporary failure in name resolution
>
>
> Where can be the error ? thanks.
>
> --
> Mario.
quot;Successful vif-route ${command} for ${dev}."
>> if [ "${command}" = "online" ]
>> then
>> success
>> fi
>>
>>
>> B) on the guest os (Debian 12)
>>
>>
>> /etc/network/interfaces :
>>
>> source
worm:~# ping google.it <http://google.it>
ping: google.it <http://google.it>: Temporary failure in name resolution
In the client try the command
dig @8.8.8.8 lists.debian.org mx
This will tell if your network config allows your client to access the
8.8.8.8 DNS server.
What is the co
;
>
> this is what happens within the guest os (Debian 12) :
>
>
> root@bookworm:~# ifup enX0
>
> root@bookworm:~# 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 noprefixroute
> valid_lft forever preferred_lft forever
>
> 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen
> 1000
>link/sit 0.0.0.0 brd 0.0.0.0
>
> 3: enX0: mtu 1500 qdisc
> pfifo_fast state UP group default
> qlen 1000
>link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff
>inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0
> valid_lft forever preferred_lft forever
>inet6 fe80::216:3eff:fe12:3456/64 scope link
> valid_lft forever preferred_lft forever
>
> root@bookworm:~# ping google.it
> ping: google.it: Temporary failure in name resolution
>
>
> Where can be the error ? thanks.
>
> --
> Mario.
>
--
Mario.
e:12:34:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0
valid_lft forever preferred_lft forever
inet6 fe80::216:3eff:fe12:3456/64 scope link
valid_lft forever preferred_lft forever
root@bookworm:~# ping google.it
ping: google.it: Temporary failure in name resolution
Where can be the error ? thanks.
--
Mario.
Salut Didier!
didier gaumet writes:
> Le 04/08/2023 à 11:44, Loris Bennett a écrit :
>> Hi,
>> I have a 10 year-old Dell E6230 laptop which I have updated
>> regularly,
>> starting from Squeeze and have now updated to Bookworm. Everything
>> seems to work except for the fact that a module fails
Le 04/08/2023 à 11:44, Loris Bennett a écrit :
Hi,
I have a 10 year-old Dell E6230 laptop which I have updated regularly,
starting from Squeeze and have now updated to Bookworm. Everything
seems to work except for the fact that a module fails to build for the
new kernel:
Error! Bad return s
Hi,
I have a 10 year-old Dell E6230 laptop which I have updated regularly,
starting from Squeeze and have now updated to Bookworm. Everything
seems to work except for the fact that a module fails to build for the
new kernel:
Error! Bad return status for module build on kernel: 6.1.0-10-amd64 (
version `GLIBC_2.34' not found
> > (required by /lib/x86_64-linux-gnu/libselinux.so.1)
> >
> > As no system tool was usable in this situation (dpkg crashed too),
> > I
> > powered-off the machine and restored it from backup. I then
> > installed
> >
On Mon, Jun 12, 2023 at 09:35:13PM +, bw wrote:
> Right now I'm studying and trying to come up with a way to identify duplicate
> filenames and/or symlinks between /bin /sbin /lib, and /usr/bin /usr/sbin
> /usr/lib. I bet someone on the list could do it in a one line command.
Well, it's not *
in-reply-to=
>> On Mon, Jun 12, 2023 at 11:24:00AM +0200, Bastien Durel wrote:
> During bookworm upgrade, I ran into some usrmerge failures, which led
> to an hard-to-fix situation
...
>>Well, that's somewhat terrifying. I looked at bugs.debian.org/usrmerge
>>and didn't see any bugs like this alr
34' not found (required
> by /lib/x86_64-linux-gnu/libselinux.so.1)
>
> As no system tool was usable in this situation (dpkg crashed too), I
> powered-off the machine and restored it from backup. I then installed
> usrmerge on bullseye, fixed the problems, then done the bookworm
&
On 2023-06-12 10:24 -0400, Greg Wooledge wrote:
> On Mon, Jun 12, 2023 at 09:45:15AM -0400, Greg Wooledge wrote:
>> I think I might try grabbing an older-than-buster version of debootstrap
>> out of snapshot.debian.org and see if I can manage to reproduce something.
>> But don't count on my succes
On Mon, Jun 12, 2023 at 09:45:15AM -0400, Greg Wooledge wrote:
> I think I might try grabbing an older-than-buster version of debootstrap
> out of snapshot.debian.org and see if I can manage to reproduce something.
> But don't count on my success.
I've succeeded in *partially* reproducing this err
ives you a
system with an already-merged /usr, so it's not helpful in setting up
a minimal chroot-able system where we can try to reproduce the failure.
According to <https://wiki.debian.org/UsrMerge> one would need a version
of debootstrap between 1.0.87 and 1.0.101, and according to
<
ne the bookworm
upgrade without any other problems.
As usrmerge is mandatory on bookworm ; and usrmerge failure during
upgrade leads to (could lead to ?) big problems ; shouldn't its
installation be advised in 4.1 or 4.2 chapters of the upgrade guide ?
I know 5.1.14 says merged-/usr is now requ
On Mon, 10 Apr 2023, Tim Woodall wrote:
On Mon, 10 Apr 2023, Lee wrote:
Why are you using google as forwarders ?
To eliminate as many variables as possible.
delv talking to google works.
delv talking to bind talking to google fails.
When talking directly, delv is using udp to talk to goog
On Mon, 10 Apr 2023, Lee wrote:
Why are you using google as forwarders ?
To eliminate as many variables as possible.
delv talking to google works.
delv talking to bind talking to google fails.
When talking directly, delv is using udp to talk to google
When talking via bind, bind is using tc
On Sun, 9 Apr 2023, Andy Smith wrote:
Hi Badli,
On Sun, Apr 09, 2023 at 07:59:32AM +, Badli Al Rashid wrote:
I got a temporary failure resolving deb.debian.org and
www.debian.org since last week thursday. I can resolve other sites
like www.kernel.org and others.
Broke last monday for me
On 4/9/23, Tim Woodall wrote:
> On Sun, 9 Apr 2023, Badli Al Rashid wrote:
>
>> Hi All,
>>
>> Gooday everybody. Anyone having temporary failure when running apt update
>> with own bind local resolver ? I got a temporary failure resolving
>> deb.debian.or
Hi Badli,
On Sun, Apr 09, 2023 at 07:59:32AM +, Badli Al Rashid wrote:
> I got a temporary failure resolving deb.debian.org and
> www.debian.org since last week thursday. I can resolve other sites
> like www.kernel.org and others.
>
> When I switch to other DNS server
On Sun, 9 Apr 2023, Badli Al Rashid wrote:
Hi All,
Gooday everybody. Anyone having temporary failure when running apt update with
own bind local resolver ? I got a temporary failure resolving deb.debian.org
and www.debian.org since last week thursday. I can resolve other sites like
Hi All,
Gooday everybody. Anyone having temporary failure when running apt update with
own bind local resolver ? I got a temporary failure resolving deb.debian.org
and www.debian.org since last week thursday. I can resolve other sites like
www.kernel.org and others.
When I switch to other DNS
On Sun 26 Mar 2023 at 12:47:45 (-0700), pe...@easthope.ca wrote:
>
> (4) "TLS on connect is not natively supported." OK but the test
> confirmed that it can work. Documentation could tell how to
> configure. Otherwise link to instructions at least.
>
> (5)
> https://www.exim.org/exim-html-curr
In-reply-to:
References:
<5319ac62b1294b2290d3d14a6cd8b...@easthope.ca>
From: David Wright
Date: Sat, 25 Mar 2023 23:34:54 -0500
In the first instance, just try sending a test message using the
commands I gave, except starting off with:
$ openssl s_client -crlf -connect mail.east
On Sat 25 Mar 2023 at 19:47:35 (-0700), pe...@easthope.ca wrote:
> > That looks fine, and shows that you're going to send through their
> > port 465, which will require TLS and authentication. So first you need
> > to encode your username and password with:
> >
> > $ echo -e -n '\0username\0passw
In-reply-to:
References: <9ef536feee6ec3ae2e3032d22e06d...@easthope.ca>
From: David Wright
Date: Fri, 24 Mar 2023 23:18:47 -0500
That looks fine, and shows that you're going to send through their
port 465, which will require TLS and authentication. So first you need
to encode your u
On Thu 23 Mar 2023 at 11:27:17 (-0700), pe...@easthope.ca wrote:
>
> # /etc/exim4/update-exim4.conf.conf
> #
> # Most of the heading comments removed.
> #
> # This is a Debian specific file
>
> dc_eximconfig_configtype='smarthost'
> dc_other_hostnames=''
> dc_local_interfaces='127.0.0.1'
> dc_rea
Header lines not handled by Web interface.
In-reply-to:
References: <5674e986a67af53a04b27f08cd161...@easthope.ca>
From: David Wright
Date: Wed, 22 Mar 2023 17:06:20 -0500
What are the contents of /etc/exim4/update-exim4.conf.conf, the
configuration file?
# /etc/exim4/update-exim4
On Wed 22 Mar 2023 at 13:52:00 (-0700), pe...@easthope.ca wrote:
>
> After configuring exim for a new smarthost, message sending fails.
What are the contents of /etc/exim4/update-exim4.conf.conf, the
configuration file?
> This might help to identify the problem.
>
> root@dalton:/home/root# exim
Hi,
In case this message is duplicated, apology in advance.
After configuring exim for a new smarthost, message sending fails.
This might help to identify the problem.
root@dalton:/home/root# exim -bh 142.103.1m.1n
SMTP testing session as if from host 142.103.1m.1n
but without any id
Hi
did you solve this? i got this problem, too with qemu 7 and ubuntu 22.04.1
--
--
cordially
Charlie Schindler
+66 9 1083 7897
On 29.10.2022 21:32, Joe Pfeiffer wrote:
Further follow-up: the problem appears to be that something else has
already put mount.fuse3 in the initramfs. Replacing the failing line
with
copy_exec /sbin/mount.fuse3 /sbin || true
allows me to create the initramfs, and the system boots, but I doub
Further follow-up: the problem appears to be that something else has
already put mount.fuse3 in the initramfs. Replacing the failing line
with
copy_exec /sbin/mount.fuse3 /sbin || true
allows me to create the initramfs, and the system boots, but I doubt
it's an optimal solution.
didier gaumet writes:
> Le 27/10/2022 à 00:52, Joe Pfeiffer a écrit :
>> I'm trying to do an update to my Debian 11 system, and keep getting the
>> following failure:
>> E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
>> Trying to get a little m
Le 27/10/2022 à 00:52, Joe Pfeiffer a écrit :
I'm trying to do an update to my Debian 11 system, and keep getting the
following failure:
E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
Trying to get a little more information, I ran
update-initramfs -u -v -k all
and after
I'm trying to do an update to my Debian 11 system, and keep getting the
following failure:
E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
Trying to get a little more information, I ran
update-initramfs -u -v -k all
and after many lines of output, got:
Adding binary /us
David composed on 2022-10-19 18:40 (UTC-0400):
> Just a general warning, for anyone who has not noticed, that
> installing the latest kernel (linux-image-5.10.0-19-amd64) on a
> machine with AMD graphics is causing numerous people to
> report boot failures:
> https://bugs.debian.org/cgi-bin/bugre
David wrote:
> Hello list,
>
> Just a general warning, for anyone who has not noticed, that
> installing the latest kernel (linux-image-5.10.0-19-amd64) on a
> machine with AMD graphics is causing numerous people to
> report boot failures:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=10
Hello list,
Just a general warning, for anyone who has not noticed, that
installing the latest kernel (linux-image-5.10.0-19-amd64) on a
machine with AMD graphics is causing numerous people to
report boot failures:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025
https://bugs.debian.org/
On 2022-07-17, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for
> testing purposes.
>
> I followed the instructions at:
>
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.conca
On Sun, Jul 17, 2022 at 06:37:55PM -0700, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for
> testing purposes.
>
> I followed the instructions at:
>
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot
On Sun, Jul 17, 2022, at 6:37 PM, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep
> around for testing purposes.
>
> I followed the instructions at:
>
>
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/S
I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for
testing purposes.
I followed the instructions at:
http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
Then I dd'ed the resulting
Currently camera output is displayed by qv4l2 and transferred to GIMP
using File > Create > Screenshot. GIMP allows annotation of the image
and export as JPG or PNG.
Probably there's a more direct way to acquire the image from the
Inogeni adapter into GIMP; ie. skip display with qv4l2. If GIMP
From: Reco
Date: Thu, 7 Sep 2017 09:53:12 +0300
> If either of these show something - you're in luck, your hardware is
> supported, etc.
> If not - I'm out of ideas, sorry.
The original objective was to take the VGA output from a JVC camera
and convert it to a digital image in a commonly
Charlie Gibbs wrote:
> Thanks, everyone, for all your help. I think I might have found
> the solution thanks to songbird:
>
> > then remove the zero length file and remove the .overview file
> > for that group and see if you can then get that message again.
> > i think a missing .overview file s
Thanks, everyone, for all your help. I think I might have found
the solution thanks to songbird:
> then remove the zero length file and remove the .overview file
> for that group and see if you can then get that message again.
> i think a missing .overview file should be regenerated every time
On Tue, 19 Apr 2022, Tim Woodall wrote:
On Mon, 18 Apr 2022, Charlie Gibbs wrote:
Again, my issue is not with the spool, but why slrn seems to
be trying to bypass it and access the server directly. Unless
that "server read failed" message is a red herring...
So I got interested and went i
On Mon, 18 Apr 2022, Charlie Gibbs wrote:
Again, my issue is not with the spool, but why slrn seems to
be trying to bypass it and access the server directly. Unless
that "server read failed" message is a red herring...
So I got interested and went investigating and I confess that I have
abs
Curt wrote:
> On 2022-04-18, Charlie Gibbs wrote:
>>
>> Again, my issue is not with the spool, but why slrn seems to
>> be trying to bypass it and access the server directly. Unless
>> that "server read failed" message is a red herring...
>>
>
>
>
> slrn --debug FILE
>
> Then look in FILE for po
On 2022-04-18, Charlie Gibbs wrote:
>
> Again, my issue is not with the spool, but why slrn seems to
> be trying to bypass it and access the server directly. Unless
> that "server read failed" message is a red herring...
>
slrn --debug FILE
Then look in FILE for possible edification.
On Mon, 18 Apr 2022 02:50:01 +0200 songbird
wrote:
[description of .jnewsrc snipped]
I've tried fiddling with .jnewsrc, but that doesn't seem to be
the problem. I retrieve news with slrnpull, which retrieves
articles and updates .jnewsrc accordingly. This has worked
properly both before and a
Charlie Gibbs wrote:
...
> The zero-length files were easy enough to find, and few enough
> that I just deleted them by hand. No luck. I've even tried
> deleting the entire contents of a group, e.g.:
>
> rm /var/spool/slrnpull/news/linux/debian/user/*
>
> Still no luck. The group header window s
On Sat, 16 Apr 2022 05:40:02 +0200 songbird
wrote:
["Server read failed." when trying to enter a newsgroup]
> i have four thoughts.
>
> first one would be to do a fsck on that file system (after
> unmounting it).
No joy
> second one is to restore from backup or redownload articles
> after
Charlie Gibbs wrote:
> Running Buster:
> Linux cjglap2 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17)
> x86_64 GNU/Linux
>
> Today when I tried reading Usenet I ran into problems. I use slrnpull
> to fetch news from a server - that part still works. When I run slrn to
> read the news, i
Running Buster:
Linux cjglap2 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17)
x86_64 GNU/Linux
Today when I tried reading Usenet I ran into problems. I use slrnpull
to fetch news from a server - that part still works. When I run slrn to
read the news, it comes up with the normal list
1 - 100 of 2209 matches
Mail list logo
