Re: Strange New Installation Behavior

2024-04-22 Thread David Christensen
rom one OS installation to another OS installation, please see my comments on another thread: https://lists.debian.org/debian-user/2024/04/msg00336.html Once you have logged in to your new account on your fresh install, I suggest that you restore your /home/comp backup to a subdirectory and manually

Re: Strange New Installation Behavior

2024-04-22 Thread Stephen P. Molnar
On 04/22/2024 11:03 AM, debian-u...@howorth.org.uk wrote: Michael Kjörling <2695bd53d...@ewoof.net> wrote: On 22 Apr 2024 09:00 -0400, from s.mol...@sbcglobal.net (Stephen P. Molnar): I downloaded and ran the 512 check sum on a copy of Debian-12.5.0-amd64-DVD-1.iso and ran the Graphical

Re: Strange New Installation Behavior

2024-04-22 Thread Michael Kjörling
On 22 Apr 2024 16:03 +0100, from debian-u...@howorth.org.uk: > He said he wanted to revert to Bullseye rather than Bookworm, so it's > to be expected that there will be older kernels, if that's really what > he meant and what he did. But as you say, without a clear statement of > the intent and

Re: Strange New Installation Behavior

2024-04-22 Thread debian-user
Michael Kjörling <2695bd53d...@ewoof.net> wrote: > On 22 Apr 2024 09:00 -0400, from s.mol...@sbcglobal.net (Stephen P. > Molnar): > > I downloaded and ran the 512 check sum on a copy of > > Debian-12.5.0-amd64-DVD-1.iso and ran the Graphical Install mode on > > the 1.0 TD SSD on my Computer. The

Re: Strange New Installation Behavior

2024-04-22 Thread Michael Kjörling
On 22 Apr 2024 09:00 -0400, from s.mol...@sbcglobal.net (Stephen P. Molnar): > I downloaded and ran the 512 check sum on a copy of > Debian-12.5.0-amd64-DVD-1.iso and ran the Graphical Install mode on the 1.0 > TD SSD on my Computer. The installation went smoothly without any warning or > error

Strange New Installation Behavior

2024-04-22 Thread Stephen P. Molnar
I am running Bookworm and cleaned up a couple of files too many resulting in a messed up Xfce Desktop. I decided that this would be a good time to reinstall the Bullseye. I made a backup of my /home/comp directory using Deja-dup. I downloaded and ran the 512 check sum on a copy of

Re: testing new sdm drive

2024-03-26 Thread David Wright
On Tue 26 Mar 2024 at 04:38:52 (-0400), gene heskett wrote: > On 2/9/24 20:36, Alexander V. Makartsev wrote: [ … ] > > It's not possible for me to know what went wrong. > > Have you created "reftestfile" inside "/mnt/disktest" directory? > > How many "testfile*" files, if any, were created on the

Re: testing new sdm drive

2024-03-26 Thread gene heskett
On 2/9/24 20:36, Alexander V. Makartsev wrote: On 10.02.2024 03:34, gene heskett wrote: On 2/8/24 07:22, Alexander V. Makartsev wrote: This is how I would test it. First create a new GPT partition table and a new 2TB partition: $ sudo gdisk /dev/sdX check /!\  Make double sure you've

Re: cruft report: The new kid on the block

2024-02-16 Thread Gremlin
: Complete pakman: 2024-02-13: Run Complete Installation/pakman -i ethtool pakman: 2024-02-13 Installing: ethtool Package: ethtool New packages: ethtool Continue Install y Installing: ethtool Reading package lists... Building dependency tree... Reading state information... The following NE

Re: cruft report: The new kid on the block

2024-02-16 Thread Sven Joachim
On 2024-02-16 09:06 -0500, Gremlin wrote: > cruft report: Fri Feb 16 08:54:01 2024 > missing: dpkg > /etc/network/if-post-down.d/wireless-tools > /etc/network/if-pre-up.d/ethtool > /etc/network/if-pre-up.d/wireless-tools > /etc/network/if-up.d/ethtool > >

cruft report: The new kid on the block

2024-02-16 Thread Gremlin
cruft report: Fri Feb 16 08:54:01 2024 missing: dpkg /etc/network/if-post-down.d/wireless-tools /etc/network/if-pre-up.d/ethtool /etc/network/if-pre-up.d/wireless-tools /etc/network/if-up.d/ethtool wireless-tools and ethtool owns these files but are

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.

2024-02-11 Thread Darac Marjal
On 10/02/2024 21:48, Maureen Thomas wrote: So can I please get some help.  I have a portable CD/DVD and I made a USB with a ISO on it.  The computer does not have a cd/dvd burner but I have a portable one.  Can some one tell me if there are any special things I need to do to put Debian 12 on

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.

2024-02-10 Thread tomas
On Sun, Feb 11, 2024 at 12:48:52AM -0500, Jeffrey Walton wrote: > On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas wrote: > > > > Do you really _not_ know how to use email? > > Or is this Phase II of the Sophie experiment? Jeffrey, please. Having a bad day? Cheer up -- tomás signature.asc

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm.

2024-02-10 Thread Jeffrey Walton
On Sat, Feb 10, 2024 at 12:27 AM Maureen Thomas wrote: > Do you really _not_ know how to use email? Or is this Phase II of the Sophie experiment? Jeff

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

2024-02-10 Thread hw
https://fostips.com/6-ways-create-bootable-debian-ubuntu-usb-installer/ On Sat, 2024-02-10 at 21:48 +, Maureen Thomas wrote: > So can I please get some help.  I have a portable CD/DVD and I made a USB > with a ISO on it.  The computer does not have a cd/dvd burner but I have a > portable

Re: testing new sdm drive continued

2024-02-10 Thread David Christensen
On 2/10/24 08:25, gene heskett wrote: I managed to kill f3write, so f3probe could access it: ene@coyote:/mnt/disktest$ sudo f3probe --destructive --time-ops /dev/sdm F3 probe 8.0 Copyright (C) 2010 Digirati Internet LTDA. This is free software; see the source for copying conditions. WARNING:

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

2024-02-10 Thread Andrew M.A. Cater
On Sat, Feb 10, 2024 at 09:48:52PM +, Maureen Thomas wrote: > So can I please get some help.  I have a portable CD/DVD and I made a USB > with a ISO on it.  The computer does not have a cd/dvd burner but I have a > portable one.  Can some one tell me if there are any special things I need

Re: -new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm

2024-02-10 Thread Maureen Thomas
So can I please get some help.  I have a portable CD/DVD and I made a USB with a ISO on it.  The computer does not have a cd/dvd burner but I have a portable one.  Can some one tell me if there are any special things I need to do to put Debian 12 on this machine.  I really hate windows and

Re: testing new sdm drive

2024-02-10 Thread gene heskett
On 2/10/24 00:46, David Christensen wrote: On 2/9/24 00:51, gene heskett wrote: On 2/8/24 13:25, David Christensen wrote: On 2/7/24 23:14, gene heskett wrote: gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm ... scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0

Re: testing new sdm drive

2024-02-10 Thread gene heskett
On 2/9/24 20:37, Alexander V. Makartsev wrote: On 10.02.2024 03:34, gene heskett wrote: On 2/8/24 07:22, Alexander V. Makartsev wrote: This is how I would test it. First create a new GPT partition table and a new 2TB partition: $ sudo gdisk /dev/sdX check /!\  Make double sure you've

Re: testing new sdm drive continued

2024-02-10 Thread gene heskett
On 2/8/24 15:36, Linux-Fan wrote: Alexander V. Makartsev writes: [...] I managed to kill f3write, so f3probe could access it: ene@coyote:/mnt/disktest$ sudo f3probe --destructive --time-ops /dev/sdm F3 probe 8.0 Copyright (C) 2010 Digirati Internet LTDA. This is free software; see the source

Re: testing new sdm drive

2024-02-10 Thread gene heskett
rst create a new GPT partition table and a new 2TB partition:     $ sudo gdisk /dev/sdX /!\  Make double sure you've selected the right device by using "lsblk" and "blkid" utilities.  /!\ /!\   It could change from 'sdm' to ano

Re: testing new sdm drive

2024-02-09 Thread David Christensen
On 2/9/24 00:51, gene heskett wrote: On 2/8/24 13:25, David Christensen wrote: On 2/7/24 23:14, gene heskett wrote: gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm ... scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 scsiModePageOffset: response length too

Re: testing new sdm drive

2024-02-09 Thread Alexander V. Makartsev
On 10.02.2024 03:34, gene heskett wrote: On 2/8/24 07:22, Alexander V. Makartsev wrote: This is how I would test it. First create a new GPT partition table and a new 2TB partition: $ sudo gdisk /dev/sdX check /!\  Make double sure you've selected the right device by using "

-new HP AMD ryzen with realtec audio. The HP is mo1-F3xxx It has winblows 11 on it and I want it gone. It does have a 256GB SSD. Is there any thing i need to know before i try to install Bookworm. Ca

2024-02-09 Thread Maureen Thomas
,, 1

Re: testing new sdm drive

2024-02-09 Thread gene heskett
Cheers, Gene Heskett, CET. Looks like a scam. Probably a reprogrammed controller to falsely report 2TB of space to the system. This is how I would test it. First create a new GPT partition table and a new 2TB partition:     $ sudo gdisk /dev/sdX check /!\  Make double sure you've selected the

Re: testing new sdm drive

2024-02-09 Thread tomas
On Fri, Feb 09, 2024 at 09:21:24AM -0500, Stefan Monnier wrote: > >> So, if you want to use `badblocks`, you may want to do it on an > >> encrypted partition (that covers the whole device) rather than on the > >> raw device. > > This is an interesting idea. I haven't wrapped my head around "what

Re: testing new sdm drive

2024-02-09 Thread Max Nikulin
On 09/02/2024 20:23, Dan Ritter wrote: I would (I have, in the past) generate a non-random but mostly incompressible large file There are 2 kinds of random number generators: - Cryptographic grade are intentionally hard to predict - Pseudo-random A pseudo-random generator of reasonable

Re: testing new sdm drive

2024-02-09 Thread Stefan Monnier
>> So, if you want to use `badblocks`, you may want to do it on an >> encrypted partition (that covers the whole device) rather than on the >> raw device. > This is an interesting idea. I haven't wrapped my head around "what if > the controller maps several block addresses to the same physical

Re: testing new sdm drive

2024-02-09 Thread tomas
On Fri, Feb 09, 2024 at 08:23:30AM -0500, Dan Ritter wrote: > to...@tuxteam.de wrote: > > On Fri, Feb 09, 2024 at 07:50:18AM -0500, Stefan Monnier wrote: > > > So, if you want to use `badblocks`, you may want to do it on an > > > encrypted partition (that covers the whole device) rather than on

Re: testing new sdm drive

2024-02-09 Thread Dan Ritter
to...@tuxteam.de wrote: > On Fri, Feb 09, 2024 at 07:50:18AM -0500, Stefan Monnier wrote: > > So, if you want to use `badblocks`, you may want to do it on an > > encrypted partition (that covers the whole device) rather than on the > > raw device. > > This is an interesting idea. I haven't

Re: testing new sdm drive

2024-02-09 Thread tomas
FAIK, so if > the drive just remaps new logical blocks to already used physical > blocks, `badblocks` may be convinced that the drive works fine even when > it doesn't. Absolutely right. And most probably it checks a block right after writing, and doesn't try to fill up the disk first. >

Re: testing new sdm drive

2024-02-09 Thread Stefan Monnier
> BTW2, there is a program for that, "badblocks", part of e2fsprograms, so > chances are it's installed. I'd look into that man page. `badblocks` sadly writes the same pattern on every block, AFAIK, so if the drive just remaps new logical blocks to already used physical blocks,

Re: testing new sdm drive

2024-02-09 Thread gene heskett
and perform I/O on the target drive and RAM. I don't think it could crash the system, but the load could be significant enough to disturb your work, so if I was in your place I'd wait until the machine is free from any work or load and then test the new drive. That is my intentions, but I'm

Re: testing new sdm drive

2024-02-09 Thread gene heskett
On 2/8/24 13:25, David Christensen wrote: On 2/7/24 23:14, gene heskett wrote: gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org ===

Re: testing new sdm drive

2024-02-08 Thread David Christensen
On 2/8/24 12:36, Linux-Fan wrote: Alexander V. Makartsev writes: From here on I'd suggest trying the tools from package `f3`. Thank you for the suggestion -- I was hoping somebody knew of a FOSS Debian package that can validate drive capacity: https://packages.debian.org/bookworm/f3

Re: testing new sdm drive

2024-02-08 Thread David Christensen
maintenance; especially not your primary workstation. Use a spare computer. I thought you were going to hook up all the new USB SSD's to a USB hub to a SBC, and turn it into a file server, backup server, or some such? David

Re: testing new sdm drive

2024-02-08 Thread tomas
turning corrupted data, I guess the kernel will cope, but things are... complex ;-) > I don't think it could crash the system, but the load could be significant > enough to disturb your work, so > if I was in your place I'd wait until the machine is free from any work or > load and then te

Re: testing new sdm drive

2024-02-08 Thread Linux-Fan
>www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Product:  SSD 3.0 [...] Looks like a scam. Probably a reprogrammed controller to falsely report 2TB of space to the system. I support this view :) This is how I would test it. First create a new GPT partition ta

Re: testing new sdm drive

2024-02-08 Thread Alexander V. Makartsev
don't think it could crash the system, but the load could be significant enough to disturb your work, so if I was in your place I'd wait until the machine is free from any work or load and then test the new drive. -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal

Re: testing new sdm drive

2024-02-08 Thread gene heskett
Cheers, Gene Heskett, CET. Looks like a scam. Probably a reprogrammed controller to falsely report 2TB of space to the system. This is how I would test it. First create a new GPT partition table and a new 2TB partition:     $ sudo gdisk /dev/sdX /!\  Make double sure you've selected the right

Re: testing new sdm drive

2024-02-08 Thread Dan Ritter
David Christensen wrote: > > Page 1-16 states: > > USB 3.1 Gen 1 connectors (20-1 pin U31G1_12; U31G1_34) > > This connector allows you to connect a USB 3.1 Gen 1 module for additional > USB 3.1 Gen 1 front or rear panel ports. With an installed USB 3.1 Gen 1 > module, you can enjoy all the

Re: testing new sdm drive

2024-02-08 Thread David Christensen
On 2/8/24 10:24, David Christensen wrote: On 2/7/24 23:14, gene heskett wrote: gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm ... scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0  >>

Re: testing new sdm drive

2024-02-08 Thread David Christensen
On 2/7/24 23:14, gene heskett wrote: gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor:

Re: testing new sdm drive

2024-02-08 Thread Alexander V. Makartsev
a scam. Probably a reprogrammed controller to falsely report 2TB of space to the system. This is how I would test it. First create a new GPT partition table and a new 2TB partition:     $ sudo gdisk /dev/sdX /!\  Make double sure you've selected the right device by using "lsblk" and &

testing new sdm drive

2024-02-07 Thread gene heskett
gene@coyote:/etc$ sudo smartctl --all -dscsi /dev/sdm smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-17-rt-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Product: SSD 3.0 Revision:

Re: normally start new xterms

2024-01-19 Thread David Wright
On Fri 19 Jan 2024 at 09:06:05 (+0100), Thomas Schmitt wrote: > to...@tuxteam.de wrote: > > I coopted the otherwise useless "Windows" key (aka "Left Super" for > > WM things: Super-L makes an xterm: > > # Terminal > > Key "t" A 4 Exec exec xterm > > For me the Flying Windows keys pop up

Re: normally start new xterms

2024-01-19 Thread tomas
> > > > > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg > > > wheat -fg black -sl 1 +sb > > > > > > This causes a button in the button box which creates a new xterm when > > > clicked. > > > > I c

Re: normally start new xterms

2024-01-19 Thread Henning Follmann
; > wheat -fg black -sl 1 +sb > > > > This causes a button in the button box which creates a new xterm when > > clicked. > > I coopted the otherwise useless "Windows" key (aka "Left Super" for > WM things: Super-L makes an xterm: > >

Re: normally start new xterms

2024-01-19 Thread tomas
On Fri, Jan 19, 2024 at 10:16:56AM +0100, Thomas Schmitt wrote: > Hi, [...] > to...@tuxteam.de wrote: > > It's Modifier (that Flying Window thing), aka "4" and the regular "t" > > (my mnemonics: "terminal"). > > Ah. You use it as modifier for other keys, i use it as plain key. Yes, I was avid

Re: normally start new xterms

2024-01-19 Thread Thomas Schmitt
Hi, to...@tuxteam.de wrote: > > > I coopted the otherwise useless "Windows" key (aka "Left Super" for > > > WM things: Super-L makes an xterm: > > > # Terminal > > > Key "t" A 4 Exec exec xterm i wrote: > > For me the Flying Windows keys pop up or push down the affected window: > >

Re: normally start new xterms

2024-01-19 Thread tomas
On Fri, Jan 19, 2024 at 09:06:05AM +0100, Thomas Schmitt wrote: > Hi, > > to...@tuxteam.de wrote: > > I coopted the otherwise useless "Windows" key (aka "Left Super" for > > WM things: Super-L makes an xterm: > > # Terminal > > Key "t" A 4 Exec exec xterm > > For me the Flying Windows

Re: normally start new xterms

2024-01-19 Thread Thomas Schmitt
Hi, to...@tuxteam.de wrote: > I coopted the otherwise useless "Windows" key (aka "Left Super" for > WM things: Super-L makes an xterm: > # Terminal > Key "t" A 4 Exec exec xterm For me the Flying Windows keys pop up or push down the affected window: Key Super_L A N RaiseLower Key

Re: normally start new xterms

2024-01-18 Thread tomas
On Thu, Jan 18, 2024 at 08:06:24PM +0100, Thomas Schmitt wrote: [...] > I have it in ~/.fvwm2rc as: > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat > -fg black -sl 1 +sb > > This causes a button in the button box which creates a new xt

Re: normally start new xterms

2024-01-18 Thread John Conover
Thanks Thomas. Have a good one ... John Thomas Schmitt writes: > Hi, > > i wrote: > > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg > > > wheat -fg black -sl 1 +sb > > John Conover wrote: > > > >

Re: normally start new xterms

2024-01-18 Thread Thomas Schmitt
Hi, i wrote: > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg > > wheat -fg black -sl 1 +sb John Conover wrote: > >Action 'Exec exec xterm ...' The framework of this line probably

Re: normally start new xterms

2024-01-18 Thread John Conover
exec xterm ...' Maybe John > > This causes a button in the button box which creates a new xterm when > clicked. > -- John Conover, cono...@panix.com, http://www.johncon.com/

Re: normally start new xterms

2024-01-18 Thread Thomas Schmitt
*FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 1 +sb This causes a button in the button box which creates a new xterm when clicked. Have a nice day :) Thomas

normally start new xterms [was: Re: smartctl cannot access my storage, need syntax help]

2024-01-18 Thread Max Nikulin
On 18/01/2024 04:20, Thomas Schmitt wrote: I normally start new xterms by xterm -ls -geometry 80x24 -bg wheat -fg black -sl 1 +sb & Options may be put into ~/.Xresources xterm*vt100.saveLines: 1 xterm*VT100.background: wheat xterm*VT100.foreground: black ! etc Use xrdb to m

Re: new thread, are gigastone ssd's good/bad

2024-01-15 Thread David Christensen
based upon details from the manufacturer. I expect that there are time delays between smartctl(8) supporting a given drive and when that version of smartctl(8) makes it into Debian stable. Power_On_Hours raw value is 912. You have stated that this is a relatively new drive. "Ol

new thread, are gigastone ssd's good/bad

2024-01-14 Thread gene heskett
in buster days. The newwer 16 port card has 4, 2T gigastone's on it, unused for anything yet, intending to either make me a new, bigger raid10 for /home, or maybe an 8T lvm for amanda's vtapes. And a 5th gigastone that I have now had its data cable plugg into all 3 choices of sata ports, 1, built

mediawiki 1.39.5 unable to create new thumbnails

2023-12-27 Thread kjohnson
When I upload new files to our wiki, the thumbnails are not created. Thumbnails created prior to applying the 1.39.5 update still work fine. It appears that the location where new thumbnails would be created has changed with 1.39.5. How can I find out where mediawiki is trying to create

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread David Wright
On Fri 15 Dec 2023 at 08:58:10 (-0500), Greg Wooledge wrote: > On Fri, Dec 15, 2023 at 02:30:21PM +0100, Nicolas George wrote: > > Greg Wooledge (12023-12-15): > > > readarray -d '' fndar < <( > > > find "$sdir" ... -printf 'stuff\0' | > > > sort -z --otherflags > > > ) >

Re: Is it safe to install Bookworm on a new machine now?

2023-12-15 Thread John Crawley
On 15/12/2023 13:39, John Crawley wrote: If you don't want to wait for 6.1.67-1 to arrive in Bookworm stable, it is available in bookworm-proposed-updates [1][2], so one workaround would be to temporarily add that repository [3] to apt sources before upgrading. Debian point release 12.4 has

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Nicolas George
Greg Wooledge (12023-12-15): > Equally safe, perhaps. Not safer. I don't know those particular perl > modules -- are they included in a standard Debian system, or does > one need to install optional packages? And then there's a learning > curve for them as well. File::Find is a standard

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Greg Wooledge
On Fri, Dec 15, 2023 at 02:30:21PM +0100, Nicolas George wrote: > Greg Wooledge (12023-12-15): > > readarray -d '' fndar < <( > > find "$sdir" ... -printf 'stuff\0' | > > sort -z --otherflags > > ) > It is possible to do it safely in bash plus command-line tools, indeed. >

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Nicolas George
Greg Wooledge (12023-12-15): > On Fri, Dec 15, 2023 at 01:42:14PM +0100, Nicolas George wrote: > > Also, note that file names can also contain newlines in general. The > > only robust delimiter is the NUL character. > > True. In order to be 100% safe, the OP's code would need to look > more like

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Greg Wooledge
On Fri, Dec 15, 2023 at 01:42:14PM +0100, Nicolas George wrote: > Also, note that file names can also contain newlines in general. The > only robust delimiter is the NUL character. True. In order to be 100% safe, the OP's code would need to look more like this: readarray -d '' fndar < <(

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Albretch Mueller
On 12/15/23, Greg Wooledge wrote: > More to the point, bash has a 'readarray' command which does what you > *actually* want: > > readarray -t fndar < <(find "$sdir" ...) > Yes, that was what I actually needed! lbrtchx

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Nicolas George
Albretch Mueller (12023-12-15): > sdir="$(pwd)" > #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td > %TI:%TM|%s\n' | sort --version-sort --reverse)) > #fndar=($(IFS='\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td > %TI:%TM|%s\n' | sort --version-sort --reverse)) > fndar=($(find

Re: setting IFS to new line doesn't work while searching?

2023-12-15 Thread Greg Wooledge
On Fri, Dec 15, 2023 at 12:33:01PM +, Albretch Mueller wrote: > #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td > %TI:%TM|%s\n' | sort --version-sort --reverse)) > the array construct ($( ... )) is using the space (between the date > and the time) also to split array

setting IFS to new line doesn't work while searching?

2023-12-15 Thread Albretch Mueller
sdir="$(pwd)" #fndar=($(IFS=$'\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td %TI:%TM|%s\n' | sort --version-sort --reverse)) #fndar=($(IFS='\n'; find "$sdir" -type f -printf '%P|%TY-%Tm-%Td %TI:%TM|%s\n' | sort --version-sort --reverse)) fndar=($(find "$sdir" -type f -printf '%P|%TY-%Tm-%Td

Re: Is it safe to install Bookworm on a new machine now?

2023-12-14 Thread John Crawley
On 15/12/2023 02:48, Kevin Price wrote: "The bug" (Bug#1057967 & Bug#1057969) occurs only in kernel version 6.1.66-1 (package -6.1.0-15, released with bookworm 12.4). No other debian kernel version has this bug. It might not affect you, and it can be remedied/worked around. If it does affect

Re: Is it safe to install Bookworm on a new machine now?

2023-12-14 Thread Kevin Price
Rick: Am 13.12.23 um 02:47 schrieb Rick Thomas: > Is there a netinst iso that I can use to safely install Bookworm (stable) on > a new PC? Possibly yes, but please read on. > If so, where can I download it from? Please always use official sources: https://www.debian.org/CD/ >

Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Geert Stappers
On Wed, Dec 13, 2023 at 06:35:08AM +0100, to...@tuxteam.de wrote: > On Tue, Dec 12, 2023 at 10:39:55PM -0600, David Wright wrote: > > On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote: > > > > Well, the machine in question has a wi-fi but I don't plan on using it. > > > > Though unless

Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread tomas
On Tue, Dec 12, 2023 at 10:39:55PM -0600, David Wright wrote: > On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote: > > > Well, the machine in question has a wi-fi but I don't plan on using it. > > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is > > > enough to

Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Gareth Evans
Can anyone please explain: 1. Why upgrades of stable into a potentially seriously compromised state were allowed to continue, twice, rather than pulling the upgrades? or... 2. Why the best temporary solution isn't to revert the kernel to the last known good version so

Re: The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread David Wright
On Tue 12 Dec 2023 at 23:05:49 (-0500), Stefan Monnier wrote: > > Well, the machine in question has a wi-fi but I don't plan on using it. > > Though unless I'm misunderstanding, just having a wi-fi (used or not) is > > enough to trigger the bug. Please correct me if I'm wrong. > > "the bug"? >

The bug (was: Is it safe to install Bookworm on a new machine now?)

2023-12-12 Thread Stefan Monnier
> Well, the machine in question has a wi-fi but I don't plan on using it. > Though unless I'm misunderstanding, just having a wi-fi (used or not) is > enough to trigger the bug. Please correct me if I'm wrong. "the bug"? What's this bug you're referring to? Stefan

Re: Is it safe to install Bookworm on a new machine now?

2023-12-12 Thread Rick Thomas
On Tue, Dec 12, 2023, at 6:22 PM, Greg Wooledge wrote: > On Tue, Dec 12, 2023 at 05:47:48PM -0800, Rick Thomas wrote: >> Is there a netinst iso that I can use to safely install Bookworm (stable) on >> a new PC? > > Well, with a netinst, the issue isn't what's on the

Re: Is it safe to install Bookworm on a new machine now?

2023-12-12 Thread Greg Wooledge
On Tue, Dec 12, 2023 at 05:47:48PM -0800, Rick Thomas wrote: > Is there a netinst iso that I can use to safely install Bookworm (stable) on > a new PC? Well, with a netinst, the issue isn't what's on the netinst medium. It's what's on the Debian mirrors, which the installer will use fo

Is it safe to install Bookworm on a new machine now?

2023-12-12 Thread Rick Thomas
Is there a netinst iso that I can use to safely install Bookworm (stable) on a new PC? If so, where can I download it from? If not, how much longer is it likely to be before one exists? Thanks! Rick

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-11 Thread Махно
> rašė: > > > > On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > > > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume > > > this is the fixed version. > > > > It certainly should be, but some people have rep

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-11 Thread Махно
the mirrors now. I assume > > this is the fixed version. > > It certainly should be, but some people have reported other issues > with the new 12.4 upgrade. See other recent posts to this list. > > -- > Michael Kjörling  https://michael.kjorling.se >

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-11 Thread Michael Kjörling
On 11 Dec 2023 11:34 -0500, from g...@extremeground.com (Gary Dale): > Pleased to note that 6.1.0-15 seems to have hit the mirrors now. I assume > this is the fixed version. It certainly should be, but some people have reported other issues with the new 12.4 upgrade. See other recent

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-11 Thread Gary Dale
On 2023-12-09 13:09, Dan Ritter wrote: https://fulda.social/@Ganneff/111551628003050712 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 The new kernel release is reported to contain an ext4 data corruption bug. It's prudent not to upgrade, or if you have started to upgrade

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Andrew M.A. Cater
On Sun, Dec 10, 2023 at 02:27:38PM -0700, Charles Curley wrote: > On Sat, 9 Dec 2023 13:09:23 -0500 > Dan Ritter wrote: > > > https://fulda.social/@Ganneff/111551628003050712 > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > > > The ne

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Charles Curley
On Sat, 9 Dec 2023 13:09:23 -0500 Dan Ritter wrote: > https://fulda.social/@Ganneff/111551628003050712 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843 > > The new kernel release is reported to contain an ext4 data > corruption bug. It's prudent not to upgra

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread tomas
On Sun, Dec 10, 2023 at 01:36:52PM -0600, Nicholas Geovanis wrote: > On Sun, Dec 10, 2023, 12:47 PM Curt wrote: [...] > > It is the notion of simultaneity itself (the now of now) that is > > relative rather than universal. > > > > I thought metaphysics was off-topic for this group. Moderators!!

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Nicholas Geovanis
On Sun, Dec 10, 2023, 12:47 PM Curt wrote: > On 2023-12-10, Gary Dale wrote: > > > > On 2023-12-10 12:24, Greg Wooledge wrote: > >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > >>> On 2023-12-10, Andrew M.A. Cater wrote: > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 >

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Curt
On 2023-12-10, Gary Dale wrote: > > On 2023-12-10 12:24, Greg Wooledge wrote: >> On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: >>> On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 >>> You mean in the Zulu Time Zone (as I am all at sea)? >>

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Gary Dale
On 2023-12-10 11:56, Andrew M.A. Cater wrote: On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote: On 2023-12-09 14:18, Michael Kjörling wrote: On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): I just upgraded to Bookworm this morning. I did reboot a couple of times

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Gary Dale
On 2023-12-10 12:24, Greg Wooledge wrote: On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: On 2023-12-10, Andrew M.A. Cater wrote: "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread John Hasler
Andy writes: > This fails with leap seconds, potentially, and also TAI astronomical > time seems to be its own animal. TAI isn't good enough for the astronomers. https://en.wikipedia.org/wiki/Terrestrial_Time -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread tomas
On Sun, Dec 10, 2023 at 05:20:40PM +, Andrew M.A. Cater wrote: > On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > > On 2023-12-10, Andrew M.A. Cater wrote: > > > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > > > You mean in the Zulu Time Zone (as I am all at sea)? > >

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Greg Wooledge
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? Use "date -u" to see current UTC time. That should be sufficient to let you know

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Andrew M.A. Cater
On Sun, Dec 10, 2023 at 05:09:15PM -, Curt wrote: > On 2023-12-10, Andrew M.A. Cater wrote: > > > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 > > You mean in the Zulu Time Zone (as I am all at sea)? > > > Andy > > (amaca...@debian.org) > > > > > Not this again :) GMT (was) the

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Curt
On 2023-12-10, Andrew M.A. Cater wrote: > > "Now" is almost exactly Sun 10 Dec 16:55:43 UTC 2023 You mean in the Zulu Time Zone (as I am all at sea)? > Andy > (amaca...@debian.org) > >

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Andrew M.A. Cater
On Sun, Dec 10, 2023 at 11:50:18AM -0500, Gary Dale wrote: > On 2023-12-09 14:18, Michael Kjörling wrote: > > On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): > > > I just upgraded to Bookworm this morning. I did reboot a couple of > > > times but there seems to be no problem

Re: IMPORTANT: do NOT upgrade to new stable point release

2023-12-10 Thread Gary Dale
On 2023-12-09 14:18, Michael Kjörling wrote: On 9 Dec 2023 20:54 +0200, from ale...@nanoid.net (Alexis Grigoriou): I just upgraded to Bookworm this morning. I did reboot a couple of times but there seems to be no problem (yet). Is there anything I should look for or do other than rebooting? If

  1   2   3   4   5   6   7   8   9   10   >