the
> >> re-compiled packages? If the latter, perhaps apt-build
> >> (https://manpages.debian.org/testing/apt-build/apt-build.1.en.html)
> >> might be of interest to you?
> >
> > Does this apply to Debian like that as well?Does this apply to Debian
> like
&
-build/apt-build.1.en.html)
might be of interest to you?
Does this apply to Debian like that as well?Does this apply to Debian like
that as well? This looks a bit Gentoo specific, but I am not too well with
kernel building. I've never done it myself.
"apt" is a Debian package
On Wednesday, April 23, 2025 8:48:01 PM Central European Summer Time Darac
Marjal wrote:
> Do you need the DVD creation, or are you just looking for the
> re-compiled packages? If the latter, perhaps apt-build
> (https://manpages.debian.org/testing/apt-build/apt-build.1.en.html)
>
On Wednesday, April 23, 2025 11:10:29 PM Central European Summer Time Tim
Woodall wrote:
> Hope the op has a lot of computing resources...
Well, only a single computer, but do you think this would suffice?
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 62.5 GiB of RAM
Thank you
On Wednesday, April 23, 2025 2:30:45 PM Central European Summer Time
to...@tuxteam.de wrote:
> For a more Debian specific link, see
>
> https://wiki.debian.org/DebianBootstrap
>
> Cheers
Yes! This is exactly what I was looking for! Thank you :-)
On Wed, Apr 23, 2025 at 9:27 AM Nils wrote:
>
> I'd like to compile all of DVD-1 myself but using `-Oz` to optimize for binary
> size rather than speed. How do I do that? Where do I start? I could only find
> infos on how to build DVD-1 yourself using existing binary packages..
On Wed, 23 Apr 2025, Joe wrote:
On Wed, 23 Apr 2025 10:58:52 +
Nils wrote:
Hey!
I'd like to compile all of DVD-1 myself but using `-Oz` to optimize
for binary size rather than speed. How do I do that? Where do I
start? I could only find infos on how to build DVD-1 yourself
On 23/04/2025 11:58, Nils wrote:
Hey!
I'd like to compile all of DVD-1 myself but using `-Oz` to optimize for binary
size rather than speed. How do I do that? Where do I start? I could only find
infos on how to build DVD-1 yourself using existing binary packages...
Thank you!
Do you nee
On Wed, Apr 23, 2025 at 01:26:44PM +0100, Joe wrote:
> On Wed, 23 Apr 2025 10:58:52 +
> Nils wrote:
>
> > Hey!
> >
> > I'd like to compile all of DVD-1 myself but using `-Oz` to optimize
> > for binary size rather than speed. How do I do that? Where d
Hey!
I'd like to compile all of DVD-1 myself but using `-Oz` to optimize for binary
size rather than speed. How do I do that? Where do I start? I could only find
infos on how to build DVD-1 yourself using existing binary packages...
Thank you!
On Sat, 11 Jan 2025, Michael Stone wrote:
> > root@titan ~ mdadm --misc /dev/md4 --stop
>
> This is incorrect syntax, and a no-op (so the array did not stop). You want
> `mdadm --misc --stop /dev/md4`. The --misc is implied so you can just use
> `mdadm --stop /dev/md4`
I ran the command
root@t
On Sat, Jan 11, 2025 at 12:11:39PM +0100, Roger Price wrote:
I am unable to erase an unwanted RAID 1 array. Command cat /proc/mdstat
reported
md4 : active raid1 sdb7[0]
20970368 blocks super 1.0 [2/1] [U_]
bitmap: 1/1 pages [4KB], 65536KB chunk
I understand that the array has to
> Sent: Saturday, January 11, 2025 at 9:51 AM
> From: "Roger Price"
> To: "debian-user Mailing List"
> Subject: Re: Removing an unwanted RAID 1 array
>
> On Sat, 11 Jan 2025, Greg Wooledge wrote:
>
> > On Sat, Jan 11, 2025 at 13:10:51 +010
On Sat, 11 Jan 2025, Greg Wooledge wrote:
> On Sat, Jan 11, 2025 at 13:10:51 +0100, Roger Price wrote:
> > On Sat, 11 Jan 2025, Michel Verdier wrote:
> >
> > > If I remember well you have to first set the device as faulty with --fail
> > > before --remove could be accepted.
> >
> > No luck :
>
On Sat, Jan 11, 2025 at 13:10:51 +0100, Roger Price wrote:
> On Sat, 11 Jan 2025, Michel Verdier wrote:
>
> > If I remember well you have to first set the device as faulty with --fail
> > before --remove could be accepted.
>
> No luck :
>
> root@titan ~ mdadm --fail /dev/md4 --remove /dev/sdb7
On Sat, 11 Jan 2025, Michel Verdier wrote:
> If I remember well you have to first set the device as faulty with --fail
> before --remove could be accepted.
No luck :
root@titan ~ mdadm --fail /dev/md4 --remove /dev/sdb7
mdadm: hot remove failed for /dev/sdb7: Device or resource busy
> But if
On 2025-01-11, Roger Price wrote:
> root@titan ~ umount /dev/md4
> root@titan ~ mdadm --misc /dev/md4 --stop
> root@titan ~ mdadm --manage /dev/md4 --remove /dev/sdb7
> mdadm: hot remove failed for /dev/sdb7: Device or resource busy
If I remember well you have to first set the device as fault
I am unable to erase an unwanted RAID 1 array. Command cat /proc/mdstat
reported
md4 : active raid1 sdb7[0]
20970368 blocks super 1.0 [2/1] [U_]
bitmap: 1/1 pages [4KB], 65536KB chunk
I understand that the array has to be inactive before it can be removed, so I
stopped it, but
VISUMPRIS
Kjære kunde
Kjære kunde, du er en av de ti personene vi har valgt fra forskjellige land
til å delta i vårt Visa Card Promotion Program, som har som mål å fremme
bruken av Visa-kort over hele verden. Vi har allerede overført €1 000 000
til et Visa-kort på dine vegne og trenger nå din
On Sat, Nov 09, 2024 at 10:39:32PM -0500, Jeffrey Walton wrote:
> On Sat, Nov 9, 2024 at 10:18 PM wrote:
> >
> > Retrieved utelnetd 0.1.11 from here.
> > https://public.pengutronix.de/software/utelnetd/
> >
> > Installed gcc and tried make.
> > # make DEBUG=
t; as the minimum to set the system clock. The default is 1 for legacy
> purposes; however, for critical applications the value should be
> somewhat higher (e.g. 3) but less than minclock.
>
> Please let me know if the above solves your problem?
Rather than lower minsane to 1, it woul
with 2 NTP servers available. If you only have
a single NTP server, change this to 1 should work - but it naturally
there won't be any redundancy in there.
Last edited by michael_S on 2023-09-26 13:55, edited 1 time in total.
https://docs.ntpsec.org/latest/miscopt.html
minsane _minsane_
Specif
wrote:
> https://docs.ntpsec.org/latest/miscopt.html
> minsane _minsane_
>
> Specify the number of servers used by the selection algorithm
> as the minimum to set the system clock. The default is 1 for legacy
> purposes; however, for critical applications the value should be
er, change this to 1 should work - but it naturally
there won't be any redundancy in there.
Last edited by michael_S on 2023-09-26 13:55, edited 1 time in total.
https://docs.ntpsec.org/latest/miscopt.html
minsane _minsane_
Specify the number of servers used by the selection algorithm
as
Hi,
I had similar issue, but when on my device i put pin, then I do not
have to put it anywhere in Debian.
Best regards,
Łukasz
On 23.08.2024 20:26, Nikita Yurchyk wrote:
bluetooth 5.77-1 (testing/trixie) doesn't show/ask pin dialog window
like bluetooth 5.66-1+deb12u2 (boo
bluetooth 5.77-1 (testing/trixie) doesn't show/ask pin dialog window like
bluetooth 5.66-1+deb12u2 (bookworm). just saying br-connection-unknown,
sometimes Authentication failed.
Steffen Dettmer wrote:
> I encountered multiple times that debian based containers use fail2ban by
> default with a max attempt value of 5, even for SSH logins using strong
> asymmetric keys.
There is no "debian based container" standard. Talk to whoever
built your container. (Why isn't it you?)
Hi,
I encountered multiple times that debian based containers use fail2ban by
default with a max attempt value of 5, even for SSH logins using strong
asymmetric keys.
(Again I just got locked out for 1h (fortunately a container, so I can
access anyway). Do you know what happened? My SSH key agent
e...@gmx.us wrote:
> On 6/4/24 10:59, songbird wrote:
>> t...@tommiller.us wrote:
>>
>>> Hello!
>>>
>>> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
>> ...
>>
>>i've been using the "more" com
Ash Joubert wrote:
> On 2024-06-05 02:59, songbird wrote:
>> t...@tommiller.us wrote:
>>> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
>>i've been using the "more" command provided by the util-linux
>> package.
>
>
On 2024-06-05 02:59, songbird wrote:
t...@tommiller.us wrote:
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
i've been using the "more" command provided by the util-linux
package.
You might be thinking of less(1), a program similar to more(1). The
On 6/4/24 10:59, songbird wrote:
t...@tommiller.us wrote:
Hello!
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
...
i've been using the "more" command provided by the util-linux
package.
How do you use "more" to do what "last&quo
t...@tommiller.us wrote:
> Hello!
>
> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
...
i've been using the "more" command provided by the util-linux
package.
songbird
June 3, 2024 at 9:09 PM, t...@tommiller.us wrote:
>
> Hello!
>
> last(1) seems to have disappeared following an upgrade from 12.5 to sid.
>
> More info is shown below. What is my mistake? Or, could it be a bug?
>
> Please send me copies of replies since I am not
On 2024-06-04 16:09, t...@tommiller.us wrote:
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
I remember seeing in the NEWS for util-linux that last(1) was moved to
the wtmpdb package:
$ zcat /usr/share/doc/util-linux/NEWS.Debian.gz
util-linux (2.40.1-2) unstable
Hello!
last(1) seems to have disappeared following an upgrade from 12.5 to sid.
More info is shown below. What is my mistake? Or, could it be a bug?
Please send me copies of replies since I am not subscribed to this list.
Thanks for your help!
Best!
Tom
<8>
# Pr
On Tue, May 14, 2024 at 04:54:26PM +0800, Bret Busby wrote:
>
> Wasn't sudo echo the name of a pop group?
>
> :)
If it wasn't it should've been one.
Cheers
--
t
signature.asc
Description: PGP signature
Wasn't sudo echo the name of a pop group?
:)
Bret Busby
Armadale
Western Australia
(UTC+0800)
.
On Mon, May 13, 2024 at 08:37:16PM +0200, Erwan David wrote:
> Le 13/05/2024 à 19:45, Stefan Monnier a écrit :
[...]
> > % sudo zsh -l
> > # echo 1 > /proc/sys/net/ipv4/ip_forward
> > # ^D
> > logout
> > %
> >
> > 🙂
&
Le 13/05/2024 à 19:45, Stefan Monnier a écrit :
$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$
I don't need no stinkin' sudo :-)
And if you only have `sudo`, but not the root password, of course:
% sudo zsh -l
# echo 1 > /proc/sys/net
On Mon, May 13, 2024 at 01:45:40PM -0400, Stefan Monnier wrote:
> > $ su -
> > Password:
> > # echo 1 > /proc/sys/net/ipv4/ip_forward
> > # ^D
> > logout
> > $
> >
> > I don't need no stinkin' sudo :-)
>
> And if you only have `
> $ su -
> Password:
> # echo 1 > /proc/sys/net/ipv4/ip_forward
> # ^D
> logout
> $
>
> I don't need no stinkin' sudo :-)
And if you only have `sudo`, but not the root password, of course:
% sudo zsh -l
# echo 1 > /proc/sys/net/ipv4/
On 5/13/24 18:52, to...@tuxteam.de wrote:
Now share your ideas :-)
$ su -
Password:
# echo 1 > /proc/sys/net/ipv4/ip_forward
# ^D
logout
$
I don't need no stinkin' sudo :-)
regards,
chris
Since this happens so often, I'm trying to offer a recap.
As others have noted, the above
sudo echo 1 > /proc/sys/net/ipv4/ip_forward
won't work, since it runs echo under sudo, but the file opening
(that pesky ">") happens in your shell, which is probably running
unp
Hi,
I think that the core problem which led to this also was on GRPCs side.
They should not tell users to compile their library but rather point
them to install it from their distros' packet manager
(https://grpc.io/docs/languages/cpp/quickstart/#install-grpc) if
possible. I will try to do the sw
Hi,
Chung Jonathan wrote:
> Yes, I think the local fix is the way to go.
I wrote:
> > (You forgot to Cc: debian-user@lists.debian.org.
> > Consider to send your mail to the list address, too. I too would then
> > resend my following reply to the list.)
Since my "following reply" is quoted in Jo
On Tue, Apr 02, 2024 at 06:34:43PM -0400, Jeffrey Walton wrote:
> On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan wrote:
> >
> > Dear Franco Martelli, dear Thomas Schmitt,
> >
> > Sorry for the potential duplication. This mail should now also go to the
> > list.
> >
> > I believe I found the probl
On Tue, Apr 2, 2024 at 6:24 PM Chung Jonathan wrote:
>
> Dear Franco Martelli, dear Thomas Schmitt,
>
> Sorry for the potential duplication. This mail should now also go to the list.
>
> I believe I found the problem which was on my side. I do have libz.so.1.3,
> since I manually compiled grpc o
some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111
Installing the version from sid resolves the issue which is clearly not
optimal. I think the fix should be backported.
Can someone help me to file a bug report
Dear Thomas Schmitt,
Yes, I think the local fix is the way to go. Probably even getting rid of the
source of this, my manual GRPC install and replacing it with libgrpc++-dev. But
that’s outside of this issue.
Yours,
Jonathan Chung
Am 02.04.2024 um 23:34 schrieb Thomas Schmitt :
Hi,
(You for
,
>> I'm new with Debian bug reporting and thus need some help with that.
>> pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
>> upstream https://github.com/madler/pigz/issues/111
>> Installing the version from sid resolves the issue which is clearly
On 02/04/24 at 10:27, Jonathan Chung wrote:
Dear sir or madam,
I'm new with Debian bug reporting and thus need some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111
Installing the version from sid resolve
On Tue, 2 Apr 2024 10:27:33 +0200
Jonathan Chung wrote:
> I'm new with Debian bug reporting and thus need some help with that.
> pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
> upstream https://github.com/madler/pigz/issues/111
Are you sure this is a bug and
Hi,
Jonathan Chung wrote:
> > pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
> > upstream https://github.com/madler/pigz/issues/111
> > Installing the version from sid resolves the issue which is clearly not
> > optimal. I think the fix should be backport
On 2 Apr 2024 10:27 +0200, from jch...@student.ethz.ch (Jonathan Chung):
> Can someone help me to file a bug report?
https://www.debian.org/Bugs/Reporting
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
Dear sir or madam,
I'm new with Debian bug reporting and thus need some help with that.
pigz 2.6-1 on Debian 12.5 fails to execute due to a fixed bug on
upstream https://github.com/madler/pigz/issues/111
Installing the version from sid resolves the issue which is clearly not
optimal. I thin
Hi,
On Thu, Mar 14, 2024 at 04:18:26PM -0600, Charles Curley wrote:
> Interesting. My logcheck instance works just fine, andmakes no such
> complaints. However, my
> /etc/logcheck/logcheck.logfiles.d/syslog.logfiles has them commented
> out.
You are probably using the journald support as configur
On Thu, 14 Mar 2024 11:25:52 -0700
cono...@panix.com (John Conover) wrote:
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
>
> The offen
Hi,
On Thu, Mar 14, 2024 at 11:25:52AM -0700, John Conover wrote:
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
>
> The offending file
John Conover wrote:
>
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
They do as soon as you install rsyslog.
Arguably this should be in rsys
On Thu, Mar 14, 2024 at 11:25:52AM -0700, John Conover wrote:
>
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
You'll want to ins
Email from logcheck(1) contains:
E: File could not be read: /var/log/syslog
E: File could not be read: /var/log/auth.log
which do not exist in bookworm 12.5.
The offending file:
/etc/logcheck/logcheck.logfiles.d/syslog.logfiles
contains both filenames.
Thanks,
John
On 1/6/24 04:36, Michael Kjörling wrote:
On 6 Jan 2024 00:37 -0800, from dpchr...@holgerdanske.com (David Christensen):
I suggest taking an image (backup) with dd(1), Clonezilla, etc., when you're
done. This will allow you to restore the image later -- to roll-back a
change you do not lik
On 6 Jan 2024 00:37 -0800, from dpchr...@holgerdanske.com (David Christensen):
> I suggest taking an image (backup) with dd(1), Clonezilla, etc., when you're
> done. This will allow you to restore the image later -- to roll-back a
> change you do not like, to recovery from a disa
On 1/5/24 21:10, Charles Curley wrote:
On Fri, 5 Jan 2024 17:25:48 -0800
David Christensen wrote:
I would be curious to know if a secure erase forces the pending
sector issue and, if so, what the result is.
An interesting thought. Alas, I am far enough along on re-installing
that I do not
On Fri, 5 Jan 2024 17:25:48 -0800
David Christensen wrote:
> I would be curious to know if a secure erase forces the pending
> sector issue and, if so, what the result is.
An interesting thought. Alas, I am far enough along on re-installing
that I do not want to try it. Sorry.
--
Does anybody
On 06/01/2024 08:25, David Christensen wrote:
I like to do a secure erase before re-deploying an SSD. The UEFI ROM
firmware in my newer Dell computers provides an option to make secure
erase easy. Other choices include an SSD manufacturer toolkit or
install/ live/ rescue media with the right
On 1/5/24 15:20, Charles Curley wrote:
On Fri, 5 Jan 2024 21:01:28 + Andy Smith wrote:
So has this coaxed the drive into reducing its pending sector count
to zero or does that still say 1?
Last I looked, it was still at 1. When I finish my reinstallation, I
will look again.
I like to
On Fri, 5 Jan 2024 21:01:28 +
Andy Smith wrote:
> So has this coaxed the drive into reducing its pending sector count
> to zero or does that still say 1?
Last I looked, it was still at 1. When I finish my reinstallation, I
will look again.
>
> I have had drives in the pas
ero or does that still say 1?
I have had drives in the past that never decremented it even though
they had clearly done a remap, and others that took a long time
(weeks) to get around to doing so.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
On 3 Jan 2024 13:25 -0700, from charlescur...@charlescurley.com (Charles
Curley):
>> As a background process, try running something like
>>
>> # ionice find / -xdev -type f -exec cat {} + >/dev/null
>
> That would only reach files on the partition where it is run.
I covered that on the next few
On 04/01/2024 03:25, Charles Curley wrote:
I decided
instead to boot to a USB stick and run badblocks. The read-only test
took 12 minutes and reported no errors.
I now have a writing test (-w) running. It has reported no failures on
its first pass.
Is badblock writing test useful for SSD takin
On Thu, 4 Jan 2024 11:58:54 +0100
wrote:
> >
> > OOPS! -w is the destructive test. I now have a hard drive full of
> > 0x00s. I should have used the -n option. However, it reported no
> > failures.
>
> Ouch, I hope you had a backup.
All the essential stuff, yes.
--
Does anybody read signat
On Wed, Jan 03, 2024 at 04:27:54PM -0700, Charles Curley wrote:
> On Wed, 3 Jan 2024 13:25:26 -0700
> Charles Curley wrote:
>
> > I now have a writing test (-w) running. It has reported no failures on
> > its first pass.
>
> OOPS! -w is the destructive test. I now have a hard drive full of 0x00s
On Wed, 3 Jan 2024 13:25:26 -0700
Charles Curley wrote:
> I now have a writing test (-w) running. It has reported no failures on
> its first pass.
OOPS! -w is the destructive test. I now have a hard drive full of 0x00s.
I should have used the -n option. However, it reported no failures.
--
Doe
On Wed, 3 Jan 2024 11:05:10 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> Since both tests finished without
> finding any errors, there _should_ have been no unreadable sectors.
Agree.
>
> I'm inclined to believe that your drive is fibbing SMART data.
Sigh. I am inclined to agree. O
#x27;m not so sure about that. See the journalctl output at the bottom of
> this email.
I don't see anything but smartd repeatedly warning you about the 1
pending sector.
As I said, it's annoying when a drive doesn't decremement its
pending sector count after remapping. If you
On 2 Jan 2024 20:17 -0700, from charlescur...@charlescurley.com (Charles
Curley):
> Jan 02 20:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently
> unreadable (pending) sectors
This is not the problem. This is smartd reporting something about the
drive's health which y
On Tue, 2024-01-02 at 17:47 -0500, Dan Ritter wrote:
> > root@tiassa:~# journalctl -u smartmontools.service | grep unreadable
> > Jan 02 13:07:39 tiassa smartd[740]: Device: /dev/sda [SAT], 1 Currently
> > unreadable (pending) sectors
> > Jan 02 13:37:39 tiassa smartd[740
only one on the computer.
>
> Like to live dangerously, huh…
No. That's what fast networks, good and multiple backup programs, a
good RAID array on another computer, and multiple off-site backups are
for.
>
> Thanks,
> Andy
>
root@tiassa:~# journalctl -b -u smartmont
FLAG VALUE WORST THRESH TYPE UPDATED
> WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x0032 100 100 050Old_age Always
> - 0
> 5 Reallocated_Sector_Ct 0x0032 100 100 050Old_age Always
> - 1
> 9 Power_On_
Hello,
On Tue, Jan 02, 2024 at 04:42:37PM -0700, Charles Curley wrote:
> If I understand that entry in the SMART report, the offending
> sector should eventually be re-mapped or else marked as
> unrecoverable. If the latter, I'll get really concerned.
If a SMART long self-test came back clean the
On Tue, 2 Jan 2024 18:01:32 -0500
Dan Purgert wrote:
> On Jan 02, 2024, Charles Curley wrote:
> > I have a brand new NVME device, details below, in a brand new
> > computer. smartd just started returning pending sector errors.
>
> Means you've got "N" bad sector(s) on the drive. It happens, e
(0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time:( 2) minutes.
Extended self-test routine
recommended polling time: ( 10) minutes.
SCT capabilities: (0x0001) SCT Sta
ART overall-health self-assessment test result: PASSED
>
> …
>
> SMART Self-test log structure revision number 1
> Num Test_DescriptionStatus Remaining LifeTime(hours)
> LBA_of_first_error
> # 1 Extended offlineCompleted without error
d
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> …
>
> SMART Self-test log structure revision number 1
> Num Test_DescriptionStatus Remaining LifeTime(hours)
> LBA_of_first_error
> #
: PASSED
…
SMART Self-test log structure revision number 1
Num Test_DescriptionStatus Remaining LifeTime(hours)
LBA_of_first_error
# 1 Extended offlineCompleted without error 00% 764 -
# 2 Short offline Completed without error 00
Start by saying you're on Debian unstable. Then give the
> installed package version (as printed by "dpkg -l openssh-client")
> and the output of "ssh -V".
As I've said in my message: I've upgraded to openssh-client 1:9.5p1-2.
The versions up to 9.4 were f
On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote:
> I have the latest version!!! I recall that this is a Debian/unstable
> machine, which I upgrade regularly. So, everytime I get such an error,
> I have the latest client.
Just for the record, saying you have the "latest" version of
Vincent Lefevre wrote:
> I have the latest version!!! I recall that this is a Debian/unstable
> machine, which I upgrade regularly. So, everytime I get such an error,
> I have the latest client.
>
> Note also that this is an error that occurs randomly.
Then I'm sorry, that I can't help you more o
On 2023-12-14 17:03:10 +0100, Klaus Singvogel wrote:
> Vincent Lefevre wrote:
> > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent
> > errors like
> >
> > kex_exchange_identification: read: Connection reset by peer
> > Connection reset by x.x.x.x port 22
>
> This sounds most like
Vincent Lefevre wrote:
> Since 2 years (from early 2022 to 2023-11-26), I've got recurrent
> errors like
>
> kex_exchange_identification: read: Connection reset by peer
> Connection reset by x.x.x.x port 22
This sounds most likely that your SSH client (program at your local machine)
has an outda
, the errors just became
Connection closed by x.x.x.x port 22
though I suspect that this is exactly the same issue.
The sshd server and its config have not changed. Only the client has
changed: I upgraded to openssh-client 1:9.5p1-2 on 2023-11-27 (this
is a Debian/unstable machine).
Is ther
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
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
pe the commands:
>
> sudo apt remove linux-image-6.1.0-15-amd64
>
> or
>
> sudo apt purge linux-image-6.1.0-15-amd64
>
> sudo update-grub
>
> sudo shutdown -r now
>
> Based on the above commands, I have some questions for you. They are:
>
> (1) Is it a &
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
Please see https://bugs.debian.org/1057967 for follow-up.
Am 11.12.23 um 06:21 schrieb Stephan Verbücheln:
[...]
> My hardware is a 2014 Macbook Pro (Intel CPU and graphics).
Stephan and all, would you please post your information there? TIA
--
Kevin Price
Hi Andy
> Sent: Monday, December 11, 2023 at 3:20 PM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
> dpkg is low le
Hi Greg
> Sent: Monday, December 11, 2023 at 11:40 AM
> From: "Greg Wooledge"
> To: debian-user@lists.debian.org
> Subject: Re: Need clarifications about how to deal with the installed
> problematic kernel, linux-image-6.1.0-14-amd64 (6.1.64-1)
>
> On Mon, D
1 - 100 of 2424 matches
Mail list logo
