On Wed, 2022-08-31 at 08:49 +0800, Jeremy Ardley wrote:
> A result of the use of resolved is the start-up and dependency logic.
Another problem I had with systemd-resolved on an Ubuntu box was that
it refuses to forward single part names to the DNS server it got by
DHCP (names like 'printer1' as o
On 8/30/22, Anssi Saari wrote:
> Leandro Noferini writes:
>
>> In these days I upgraded the server to bullseye and so I have not yet
>> archivemail: what could I use as subsitute?
>
> I wonder about that too,
Hi, not an archivemail user, but just in case it's useful: you can
check the right colu
On Wed, Aug 31, 2022, 5:36 AM riveravaldez
wrote:
> On 8/30/22, Anssi Saari wrote:
> > Leandro Noferini writes:
> >
> >> In these days I upgraded the server to bullseye and so I have not yet
> >> archivemail: what could I use as subsitute?
> >
> > I wonder about that too,
>
> Hi, not an archive
Greg Wooledge writes:
> On Wed, Aug 31, 2022 at 08:49:29AM +0800, Jeremy Ardley wrote:
>> One of my problems with systemd is the that name resolution is by default
>> done by resolved.
>
> Not in Debian.
>
> unicorn:~$ systemctl status systemd-resolved
> ● systemd-resolved.service - Network Name
On 31/8/22 9:16 pm, Anssi Saari wrote:
I wonder what bugs Jeremy has found and reported against
systemd-resolved though. I remember getting a big headache trying to get
interface specific DNS configuration going only to eventually find out
it really wasn't working in the version Debian packaged
I would appreciate advice from the community about a failing hard drive.
When booting up, the computer complained about /dev/sdb, which is a ext4
HDD with data (not the computer main disk). dmesg shows `AE_NOT_FOUND`
and `failed command: READ FPDMA QUEUED` messages (full dmesg log at
https://
Hi.
After I rebooted for a new kernel, I am having trouble with my 5 GHz
wifi access point using hostapd.
My setup is a Debian Testing updated almost daily, except for the summer
weeks.
Before summer, this configuration used to work:
interface=wlan1
ssid=cigaes_paris2
country_code=FR
# 36 48 ok
On 8/30/22 8:49 PM, Jeremy Ardley wrote:
> On 30/8/22 9:56 am, Ross Boylan wrote:
> >
> > Now everything just works.
> >
> > Thanks again to everyone.
> >
> > There are probably some general lessons, though I'm not sure what they
> > are. Clearly the systemd semantics tripped me up; it's kind of a
On 31/8/22 10:45 pm, Chuck Zmudzinski wrote:
I don't use haproxy but I see there is a package for it in the Debian
repos. I think what you are seeing should be reported as a bug in
haproxy if you are using the Debian packaged version. The haproxy
package should start haproxy at the appropriate
On Wed, 31 Aug 2022 15:25:36 +0200
ppr wrote:
> Should I wait hoping for a speeding? Should I pass different option
> to ddrescue or use another tool?
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
On 2022-08-31 08:47 -0400, Kenneth Parker wrote:
> On Wed, Aug 31, 2022, 5:36 AM riveravaldez
> wrote:
>
>> On 8/30/22, Anssi Saari wrote:
>> > Leandro Noferini writes:
>> >
>> >> In these days I upgraded the server to bullseye and so I have not yet
>> >> archivemail: what could I use as subsit
On Wed, Aug 31, 2022 at 03:25:36PM +0200, ppr wrote:
> I would appreciate advice from the community about a failing hard drive.
>
[...]
> I did not try to mount the HDD. I plugged an external HDD (ext4) and
> launched ddrescue. After two days it has recovered 33GB of 1TB but the speed
> are now
On 8/31/22, to...@tuxteam.de wrote:
> On Wed, Aug 31, 2022 at 03:25:36PM +0200, ppr wrote:
>> I would appreciate advice from the community about a failing hard drive.
>>
>
> [...]
>
>> I did not try to mount the HDD. I plugged an external HDD (ext4) and
>> launched ddrescue. After two days it has
On Wed, Aug 31, 2022 at 03:25:36PM +0200, ppr wrote:
I did not try to mount the HDD. I plugged an external HDD (ext4) and
launched ddrescue. After two days it has recovered 33GB of 1TB but the
speed are now so slow it will take 7104 days to complete.
is the img file still growing? in general y
On 8/31/22 06:25, ppr wrote:
I would appreciate advice from the community about a failing hard drive.
When booting up, the computer complained about /dev/sdb, which is a ext4
HDD with data (not the computer main disk). dmesg shows `AE_NOT_FOUND`
and `failed command: READ FPDMA QUEUED` message
On 8/31/22 11:03 AM, Jeremy Ardley wrote:
> On 31/8/22 10:45 pm, Chuck Zmudzinski wrote:
> >
> > I don't use haproxy but I see there is a package for it in the Debian
> > repos. I think what you are seeing should be reported as a bug in
> > haproxy if you are using the Debian packaged version. The
On Wed 31 Aug 2022 at 15:25:36 (+0200), ppr wrote:
> Copying non-tried blocks... Pass 1 (forwards)^C
>
> Should I wait hoping for a speeding? Should I pass different option to
> ddrescue or use another tool?
I would look at two options you could try adding to your command line:
-K --skip-size co
On Wed 31 Aug 2022 at 15:27:04 (-0400), Michael Stone wrote:
> On Wed, Aug 31, 2022 at 03:25:36PM +0200, ppr wrote:
> > I did not try to mount the HDD. I plugged an external HDD (ext4)
> > and launched ddrescue. After two days it has recovered 33GB of 1TB
> > but the speed are now so slow it will t
On Wed 31 Aug 2022 at 14:02:19 (-0700), David Christensen wrote:
> On 8/31/22 06:25, ppr wrote:
> > I would appreciate advice from the community about a failing hard drive.
> >
> > When booting up, the computer complained about /dev/sdb, which is
> > a ext4 HDD with data (not the computer main dis
On 8/31/22 15:35, David Wright wrote:
On Wed 31 Aug 2022 at 14:02:19 (-0700), David Christensen wrote:
On 8/31/22 06:25, ppr wrote:
I would appreciate advice from the community about a failing hard drive.
When booting up, the computer complained about /dev/sdb, which is
a ext4 HDD with data (n
20 matches
Mail list logo
