Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: What Thomas was trying to do is to get a cheap, fast random number generator. Shred seems to have such. You're better off with /dev/urandom, it's much easier to understand what it's trying to do, vs the rather baroque logic in

Re: shred bug? [was: Unidentified subject!]

On Tue 13 Feb 2024 at 11:21:08 (-0500), Greg Wooledge wrote: > On Tue, Feb 13, 2024 at 09:35:11AM -0600, David Wright wrote: > > On Tue 13 Feb 2024 at 07:15:48 (-0500), Greg Wooledge wrote: > > > On Mon, Feb 12, 2024 at 11:01:47PM -0600, David Wright wrote: > > > > … but not much. For me,

Re: shred bug? [was: Unidentified subject!]

On Tue, Feb 13, 2024 at 01:03:44PM -0800, David Christensen wrote: > On 2/13/24 09:40, debian-u...@howorth.org.uk wrote: > > Greg Wooledge wrote: > > > > > Shred will determine the size of the file, then write data to the > > > file, rewind, write data again, etc. On a traditional hard drive, >

Re: shred bug? [was: Unidentified subject!]

On 2/13/24 16:00, David Christensen wrote: On 2/13/24 11:31, gene heskett wrote: Next experiment is a pair of 4T Silicon Power SSD's When they & the startech usb3 adapters arrive.  I'll get that NAS built for amanda yet. 2.5" SATA SSD's and SATA to USB adapter cables for $187.97 + $10.99 =

Re: shred bug? [was: Unidentified subject!]

On 2/13/24 09:40, debian-u...@howorth.org.uk wrote: Greg Wooledge wrote: Shred will determine the size of the file, then write data to the file, rewind, write data again, etc. On a traditional hard drive, that will overwrite the original private information. On modern devices, it may not.

Re: shred bug? [was: Unidentified subject!]

On 2/13/24 11:31, gene heskett wrote: Next experiment is a pair of 4T Silicon Power SSD's When they & the startech usb3 adapters arrive.  I'll get that NAS built for amanda yet. 2.5" SATA SSD's and SATA to USB adapter cables for $187.97 + $10.99 = $198.96 each set?

Re: shred bug? [was: Unidentified subject!]

On 2/13/24 14:44, Thomas Schmitt wrote: Hi, Gene Heskett wrote: Next experiment is a pair of 4T Silicon Power SSD's When f3 has (hopefully) given its OK, the topic of a full write-and-read test will come up again. I'm looking forward to all the spin-off topics. I'll have to admit it has

Re: shred bug? [was: Unidentified subject!]

Hi, Gene Heskett wrote: > Next experiment is a pair of 4T Silicon Power SSD's When f3 has (hopefully) given its OK, the topic of a full write-and-read test will come up again. I'm looking forward to all the spin-off topics. Have a nice day :) Thomas

Re: shred bug? [was: Unidentified subject!]

Hi, Greg Wooledge wrote: > Heh. Don't forget your own attempts to use a shredder as a PRNG stream. My original idea was to watch a minimal shred run by teeing its work into a checksummer. But then topic drift came in. So we got a farm show of random generators and a discussion about what

Re: shred bug? [was: Unidentified subject!]

On 2/13/24 12:56, Thomas Schmitt wrote: Hi, Greg Wooledge wrote: Let me write out the example again, but with the bug fixed, and then explain what each line does, [... lecture about advanced shell programming ...] And this all because Gene Heskett was adventurous enough to buy a cheap fake

Re: shred bug? [was: Unidentified subject!]

On Tue, Feb 13, 2024 at 06:54:58PM +0100, Thomas Schmitt wrote: > Greg Wooledge wrote: > > Let me write out the example again, but with the bug fixed, and then > > explain what each line does, [... lecture about advanced shell > > programming ...] > > And this all because Gene Heskett was

Re: shred bug? [was: Unidentified subject!]

Hi, Greg Wooledge wrote: > Let me write out the example again, but with the bug fixed, and then > explain what each line does, [... lecture about advanced shell > programming ...] And this all because Gene Heskett was adventurous enough to buy a cheap fake USB disk. :)) Have a nice day :)

Re: shred bug? [was: Unidentified subject!]

Greg Wooledge wrote: > Shred will determine the size of the file, then write data to the > file, rewind, write data again, etc. On a traditional hard drive, > that will overwrite the original private information. On modern > devices, it may not. Thanks for the excellent explanation :) One

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

David Christensen writes: On 2/12/24 08:30, Linux-Fan wrote: David Christensen writes: On 2/11/24 02:26, Linux-Fan wrote: I wrote a program to automatically generate random bytes in multiple threads: https://masysma.net/32/big4.xhtml What algorithm did you implement? I copied the

Re: shred bug? [was: Unidentified subject!]

On Tue, Feb 13, 2024 at 09:35:11AM -0600, David Wright wrote: > On Tue 13 Feb 2024 at 07:15:48 (-0500), Greg Wooledge wrote: > > On Mon, Feb 12, 2024 at 11:01:47PM -0600, David Wright wrote: > > > … but not much. For me, "standard output" is /dev/fd/1, yet it seems > > > unlikely that anyone is

Re: shred bug? [was: Unidentified subject!]

On Tue 13 Feb 2024 at 07:15:48 (-0500), Greg Wooledge wrote: > On Mon, Feb 12, 2024 at 11:01:47PM -0600, David Wright wrote: > > … but not much. For me, "standard output" is /dev/fd/1, yet it seems > > unlikely that anyone is going to use >&1 in the manner of the example. > > Standard output

Re: shred bug? [was: Unidentified subject!]

Hi, "info shred" says: > > > i=$(mktemp) > > > exec 3<>"$i" > > > rm -- "$i" > > > echo "Hello, world" >&3 > > > shred - >&3 > > > exec 3>- Greg Wooledge wrote: > In fact, that last line is > written incorrectly. It should say "exec 3>&-" and what that does >

Re: shred bug? [was: Unidentified subject!]

On Tue, Feb 13, 2024 at 07:36:14AM -0500, Greg Wooledge wrote: > On Tue, Feb 13, 2024 at 07:15:48AM -0500, Greg Wooledge wrote: > > This is an obvious bug in the info page. I wonder how many years > > this has gone unnoticed. > > I've filed Bug#1063837 for it.

Re: shred bug? [was: Unidentified subject!]

On Tue, Feb 13, 2024 at 07:15:48AM -0500, Greg Wooledge wrote: > This is an obvious bug in the info page. I wonder how many years > this has gone unnoticed. I've filed Bug#1063837 for it.

Re: shred bug? [was: Unidentified subject!]

On Mon, Feb 12, 2024 at 11:01:47PM -0600, David Wright wrote: > … but not much. For me, "standard output" is /dev/fd/1, yet it seems > unlikely that anyone is going to use >&1 in the manner of the example. Standard output means "whatever file descriptor 1 points to". That could be a file, a

Re: shred bug? [was: Unidentified subject!]

On Mon, Feb 12, 2024 at 10:07:45PM +0100, Thomas Schmitt wrote: > Hi, > > > https://en.wikipedia.org/wiki/Everything_is_a_file > > But, there is more than one kind of file. > > "All files are equal. > But some files are more equal than others." > > (George Orwell in his dystopic novel "Server

Re: shred bug? [was: Unidentified subject!]

On Sun 11 Feb 2024 at 09:16:00 (-0600), David Wright wrote: > On Sun 11 Feb 2024 at 09:54:24 (-0500), Greg Wooledge wrote: > > On Sun, Feb 11, 2024 at 03:45:21PM +0100, to...@tuxteam.de wrote: > > > Still there's the discrepancy between doc and behaviour. > > > > There isn't. The documentation

Re: shred bug? [was: Unidentified subject!]

On 12/02/2024 05:41, David Christensen wrote: Apparently, shred(1) has both an info(1) page (?) and a man(1) page. The obvious solution is to write one document that is complete and correct, and use it everywhere -- e.g. DRY. https://www.gnu.org/prep/standards/html_node/Man-Pages.html 6.9

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

On 2/12/24 08:30, Linux-Fan wrote: David Christensen writes: On 2/11/24 02:26, Linux-Fan wrote: I wrote a program to automatically generate random bytes in multiple threads: https://masysma.net/32/big4.xhtml What algorithm did you implement? I copied the algorithm from here:

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

On Mon, Feb 12, 2024 at 3:02 PM Linux-Fan wrote: > > David Christensen writes: > > > On 2/11/24 02:26, Linux-Fan wrote: > >> I wrote a program to automatically generate random bytes in multiple > >> threads: > >> https://masysma.net/32/big4.xhtml > >> > >> Before knowing about `fio` this way my

Re: shred bug? [was: Unidentified subject!]

Hi, > https://en.wikipedia.org/wiki/Everything_is_a_file > But, there is more than one kind of file. "All files are equal. But some files are more equal than others." (George Orwell in his dystopic novel "Server Farm".) Have a nice day :) Thomas

Re: shred bug? [was: Unidentified subject!]

On 2/12/24 08:50, Curt wrote: On 2024-02-11, wrote: On Sun, Feb 11, 2024 at 09:54:24AM -0500, Greg Wooledge wrote: [...] If FILE is -, shred standard output. =20 In every sentence, the word FILE appears. There's nothing in there which says "you can operate on a non-file".

Re: shred bug? [was: Unidentified subject!]

On Mon, Feb 12, 2024 at 04:50:50PM -, Curt wrote: > On 2024-02-11, wrote: > > > > > > On Sun, Feb 11, 2024 at 09:54:24AM -0500, Greg Wooledge wrote: > > > > [...] > > > >>If FILE is -, shred standard output. > >>=20 > >> In every sentence, the word FILE appears. There's nothing in

Re: shred bug? [was: Unidentified subject!]

On 2024-02-11, wrote: > > > On Sun, Feb 11, 2024 at 09:54:24AM -0500, Greg Wooledge wrote: > > [...] > >>If FILE is -, shred standard output. >>=20 >> In every sentence, the word FILE appears. There's nothing in there >> which says "you can operate on a non-file". > > Point taken, yes.

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

David Christensen writes: On 2/11/24 02:26, Linux-Fan wrote: I wrote a program to automatically generate random bytes in multiple threads: https://masysma.net/32/big4.xhtml Before knowing about `fio` this way my way to benchmark SSDs :) Example: | $ big4 -b /dev/null 100 GiB | Ma_Sys.ma Big

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

On 2/11/24 02:26, Linux-Fan wrote: I wrote a program to automatically generate random bytes in multiple threads: https://masysma.net/32/big4.xhtml Before knowing about `fio` this way my way to benchmark SSDs :) Example: | $ big4 -b /dev/null 100 GiB | Ma_Sys.ma Big 4.0.2, Copyright (c) 2014,

Re: shred bug? [was: Unidentified subject!]

On 2/11/24 06:54, Greg Wooledge wrote: On Sun, Feb 11, 2024 at 03:45:21PM +0100, to...@tuxteam.de wrote: On Sun, Feb 11, 2024 at 09:37:31AM -0500, Greg Wooledge wrote: On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: [...] What Thomas was trying to do is to get a cheap,

Re: Unidentified subject!

On 2/11/24 03:13, Thomas Schmitt wrote: Hi, David Christensen wrote: Concurrency: threads throughput 8 205+198+180+195+205+184+184+189=1,540 MB/s There remains the question how to join these streams without losing speed in order to produce a single checksum. (Or one would have to

Re: Unidentified subject!

On 2/11/24 00:07, Thomas Schmitt wrote: In the other thread about the /dev/sdm test: Gene Heskett wrote: Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32 [...] $ sudo f3probe --destructive --time-ops /dev/sdm Bad news: The device `/dev/sdm' is a counterfeit of type limbo Device

Re: shred bug? [was: Unidentified subject!]

On Sun 11 Feb 2024 at 09:54:24 (-0500), Greg Wooledge wrote: > On Sun, Feb 11, 2024 at 03:45:21PM +0100, to...@tuxteam.de wrote: > > On Sun, Feb 11, 2024 at 09:37:31AM -0500, Greg Wooledge wrote: > > > On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: > > > > [...] > > > > > >

Re: shred bug? [was: Unidentified subject!]

Hi, to...@tuxteam.de wrote: > Still there's the discrepancy between doc and behaviour. Depends at which documentation you look. Obviously stemming from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=155175#36 i read in

Re: Unidentified subject!

On Sun, Feb 11, 2024 at 9:52 AM Thomas Schmitt wrote: > > David Christensen wrote: > > Concurrency: > > threads throughput > > 8 205+198+180+195+205+184+184+189=1,540 MB/s > > There remains the question how to join these streams without losing speed > in order to produce a single checksum.

Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 09:54:24AM -0500, Greg Wooledge wrote: [...] >If FILE is -, shred standard output. > > In every sentence, the word FILE appears. There's nothing in there > which says "you can operate on a non-file". Point taken, yes. Cheers -- t signature.asc Description:

Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 03:45:21PM +0100, to...@tuxteam.de wrote: > On Sun, Feb 11, 2024 at 09:37:31AM -0500, Greg Wooledge wrote: > > On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: > > [...] > > > > What Thomas was trying to do is to get a cheap, fast random number > > >

Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 09:37:31AM -0500, Greg Wooledge wrote: > On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: [...] > > What Thomas was trying to do is to get a cheap, fast random number > > generator. Shred seems to have such. > > Well... I certainly wouldn't call it a

Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: > On Sat, Feb 10, 2024 at 07:10:54PM -0500, Greg Wooledge wrote: > > On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote: > > > 2024-02-10 16:03:50 dpchrist@laalaa ~ > > > $ shred -s 1K - | wc -c > > > shred: -:

Re: shred bug? [was: Unidentified subject!]

David Christensen wrote: > On 2/10/24 16:10, Greg Wooledge wrote: > > On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote: > >> 2024-02-10 16:03:50 dpchrist@laalaa ~ > >> $ shred -s 1K - | wc -c > >> shred: -: invalid file type > >> 0 > >> > >> > >> It looks like a shred(1) needs

Re: Fast Random Data Generation (Was: Re: Unidentified subject!)

On 2/11/24 05:26, Linux-Fan wrote: David Christensen writes: On 2/11/24 00:11, Thomas Schmitt wrote: [...] Increase block size: 2024-02-11 01:18:51 dpchrist@laalaa ~ $ dd if=/dev/urandom of=/dev/null bs=1M count=1K 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB)

Re: Unidentified subject!

Hi, David Christensen wrote: > Concurrency: > threads throughput > 8 205+198+180+195+205+184+184+189=1,540 MB/s There remains the question how to join these streams without losing speed in order to produce a single checksum. (Or one would have to divide the target into 8 areas which get

Fast Random Data Generation (Was: Re: Unidentified subject!)

David Christensen writes: On 2/11/24 00:11, Thomas Schmitt wrote: [...] Increase block size: 2024-02-11 01:18:51 dpchrist@laalaa ~ $ dd if=/dev/urandom of=/dev/null bs=1M count=1K 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 3.62874 s, 296 MB/s Here

Re: Unidentified subject!

On 2/11/24 00:11, Thomas Schmitt wrote: Hi, David Christensen wrote: $ time dd if=/dev/urandom bs=8K count=128K | wc -c [...] 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.30652 s, 249 MB/s This looks good enough for practical use on spinning rust and slow SSD. Yes. Maybe the "wc" pipe

Re: Unidentified subject!

Hi, David Christensen wrote: > $ time dd if=/dev/urandom bs=8K count=128K | wc -c > [...] > 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 4.30652 s, 249 MB/s This looks good enough for practical use on spinning rust and slow SSD. Maybe the "wc" pipe slows it down ? ... not much on 4 GHz Xeon with

Re: Unidentified subject!

Hi, i wrote: > > In the other thread about the /dev/sdm test: Gene Heskett wrote: > > > Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32 > > > [...] > > > $ sudo f3probe --destructive --time-ops /dev/sdm > > > Bad news: The device `/dev/sdm' is a counterfeit of type limbo > > > Device

Re: shred bug? [was: Unidentified subject!]

On Sat, Feb 10, 2024 at 07:10:54PM -0500, Greg Wooledge wrote: > On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote: > > 2024-02-10 16:03:50 dpchrist@laalaa ~ > > $ shred -s 1K - | wc -c > > shred: -: invalid file type > > 0 > > > > > > It looks like a shred(1) needs a bug report.

Re: shred bug? [was: Unidentified subject!]

On 2/10/24 16:10, Greg Wooledge wrote: On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote: 2024-02-10 16:03:50 dpchrist@laalaa ~ $ shred -s 1K - | wc -c shred: -: invalid file type 0 It looks like a shred(1) needs a bug report. I'm confused what you expected this command to

Re: shred bug? [was: Unidentified subject!]

On Sat, Feb 10, 2024 at 04:05:21PM -0800, David Christensen wrote: > 2024-02-10 16:03:50 dpchrist@laalaa ~ > $ shred -s 1K - | wc -c > shred: -: invalid file type > 0 > > > It looks like a shred(1) needs a bug report. I'm confused what you expected this command to do. You wanted to "destroy"

Re: shred bug? [was: Unidentified subject!]

On 2/10/24 04:40, to...@tuxteam.de wrote: On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote: [...] But shred(1) on Debian 11 refuses on "-" contrary to its documentation: shred: -: invalid file type A non-existing file path causes "No such file or directory". Hmm. This looks

Re: Unidentified subject!

On 2/10/24 10:28, Thomas Schmitt wrote: In the other thread about the /dev/sdm test: Creating file 39.h2w ... 1.98% -- 1.90 MB/s -- 257:11:32 but is taking a few bytes now and then. [...] $ ls -l total 40627044 [...] $ sudo f3probe --destructive --time-ops /dev/sdm Bad news: The device

Re: Unidentified subject!

On 2/10/24 02:38, Thomas Schmitt wrote: I have an own weak-random generator, but shred beats it by a factor of 10 when writing to /dev/null. As a baseline, here is a 2011 Dell Latitude E6520 with Debian generating a non-repeatable 1 GiB stream of cryptographically secure pseudo-random

Re: Unidentified subject!

On 2/10/24 13:30, Thomas Schmitt wrote: Hi, gene heskett wrote: my fading eyesight couldn't see the diffs between () and {} in a 6 point font. I need a bigger, more legible font in t-bird. That's why i propose to copy+paste problematic command lines. Your mouse can read it, your mail

Re: Unidentified subject!

Hi, gene heskett wrote: > my fading eyesight couldn't see > the diffs between () and {} in a 6 point font. I need a bigger, more > legible font in t-bird. That's why i propose to copy+paste problematic command lines. Your mouse can read it, your mail client can send it, and we have youngsters

Re: Unidentified subject!

On 2/10/24 05:39, Thomas Schmitt wrote: Hi, Gene Heskett wrote: Is bash not actually bash these days? It is not doing for loops for me. Come on Gene, be no sophie. Copy+paste your failing line here. :)) Alexander M. posted it a few days ago but my fading eyesight couldn't see the diffs

Re: Things I don't touch with a 3.048m barge pole: USB storage(WasRe: Unidentified subject!)

On 2/10/24 00:54, David Christensen wrote: On 2/9/24 04:53, gene heskett wrote: Interesting report from gdisk however: GPT fdisk (gdisk) version 1.0.9 Partition table scan:    MBR: MBR only    BSD: not present    APM: not present    GPT: not present

Re: Unidentified subject!

>> AFAIK the bogus 128TB drives do properly report such ridiculous sizes: >> the reality only hits when you try to actually store that amount of >> information on them. >> [ I'm not sure how it works under the hood, but since SSDs store their >>data "anywhere" in the flash, they can easily

Re: shred bug? [was: Unidentified subject!]

On Sat, Feb 10, 2024 at 01:40:35PM +0100, to...@tuxteam.de wrote: > On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote: > > [...] > > > But shred(1) on Debian 11 refuses on "-" contrary to its documentation: > > shred: -: invalid file type > > A non-existing file path causes "No

shred bug? [was: Unidentified subject!]

On Sat, Feb 10, 2024 at 11:38:21AM +0100, Thomas Schmitt wrote: [...] > But shred(1) on Debian 11 refuses on "-" contrary to its documentation: > shred: -: invalid file type > A non-existing file path causes "No such file or directory". Hmm. This looks like a genuine bug: the man page

Re: Unidentified subject!

Hi, Gene Heskett wrote: > Is bash not actually bash these days? It is not doing for loops for me. Come on Gene, be no sophie. Copy+paste your failing line here. :)) IIRC the for-loop in question writes several copies of the same file. (

Re: Unidentified subject!

On 2/7/24 23:28, Stefan Monnier wrote: Well the 2T memory everybody was curious about 3 weeks ago got here early. From dmesg after plugging one in: [629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd [629241.066221] usb 1-2: New USB device found, idVendor=048d,

Re: Things I don't touch with a 3.048m barge pole: USB storage (WasRe: Unidentified subject!)

On 2/9/24 04:53, gene heskett wrote: Interesting report from gdisk however: GPT fdisk (gdisk) version 1.0.9 Partition table scan:   MBR: MBR only   BSD: not present   APM: not present   GPT: not present *** Found invalid GPT and

Re: Things I don't touch with a 3.048m barge pole: USB storage (WasRe: Unidentified subject!)

On 2/8/24 15:43, Andy Smith wrote: Hello, On Thu, Feb 08, 2024 at 02:20:59PM -0500, Jeffrey Walton wrote: On Thu, Feb 8, 2024 at 11:57 AM Ralph Aichinger wrote: How does a breaking USB disk differ from a breaking SATA disk? I may be mistaken, but I believe AS is talking about USB thumb

Re: Things I don't touch with a 3.048m barge pole: USB storage (WasRe: Unidentified subject!)

On 2/8/24 11:15, Gremlin wrote: On 2/8/24 10:36, Andy Smith wrote: Hello, On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: [629241.074187] scsi host37: usb-storage 1-2:1.0 USB storage is for phones and cameras etc, not for serious computing. Many people will disagree with that

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hi all, Am 08.02.2024 um 21:38 schrieb Andy Smith: Hello, On Thu, Feb 08, 2024 at 05:40:54PM +0100, Ralph Aichinger wrote: On Thu, 2024-02-08 at 15:36 +, Andy Smith wrote: I learned not to go there a long time ago and have seen plenty of reminders along the way from others' misfortunes

Re: Unidentified subject!

Charles Curley writes: > On Thu, 08 Feb 2024 18:02:36 -0500 > Stefan Monnier wrote: > >> > Test it with Validrive. >> > https://www.grc.com/validrive.htm >> >> Looks like proprietary software for Windows. > > badblocks, available in a Debian repo near you, might be a suitable > replacement.

Re: Unidentified subject!

On Thu, 08 Feb 2024 18:02:36 -0500 Stefan Monnier wrote: > > Test it with Validrive. > > https://www.grc.com/validrive.htm > > Looks like proprietary software for Windows. badblocks, available in a Debian repo near you, might be a suitable replacement. -- Does anybody read signatures any

Re: Unidentified subject!

> Test it with Validrive. > https://www.grc.com/validrive.htm Looks like proprietary software for Windows. Stefan

Re: Unidentified subject!

gene heskett writes: > Well the 2T memory everybody was curious about 3 weeks ago got here early. > > From dmesg after plugging one in: > [629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd > [629241.066221] usb 1-2: New USB device found, idVendor=048d, > idProduct=1234,

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 2/8/24 16:28, Andy Smith wrote: Hello, On Thu, Feb 08, 2024 at 04:22:49PM -0500, Gremlin wrote: On Thu, Feb 08, 2024 at 08:43:17PM +, Andy Smith wrote: I really do mean all forms of USB that come over a USB port. That line was meant to read I really do mean all forms of storage

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Thu, Feb 08, 2024 at 04:22:49PM -0500, Gremlin wrote: > On Thu, Feb 08, 2024 at 08:43:17PM +, Andy Smith wrote: > > I really do mean all forms of USB that come over a USB port. > > That line was meant to read > > I really do mean all forms of storage that come over a USB port.

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 2/8/24 16:16, Andy Smith wrote: On Thu, Feb 08, 2024 at 03:56:19PM -0500, Gremlin wrote: On 2/8/24 15:43, Andy Smith wrote: I wouldn't have much issue with taking a USB drive out of its caddy to get the SATA drive from inside, except that it would have to be an amazingly good deal to make

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Thu, Feb 08, 2024 at 04:00:01PM -0500, Gremlin wrote: > I have been using USB attached HDDs and SSDs for 10 years now and > have never had one unexpectedly go off line. Your postings > suggest you don't know what your talking about. Okay then. Despite this uncharitable comment, I do

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On Thu, Feb 08, 2024 at 03:56:19PM -0500, Gremlin wrote: > On 2/8/24 15:43, Andy Smith wrote: > > I wouldn't have much issue with taking a USB drive out of its caddy > > to get the SATA drive from inside, except that it would have to be > > an amazingly good deal to make it worth voiding the

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 2/8/24 15:35, Andy Smith wrote: Hello, On Fri, Feb 09, 2024 at 12:23:45AM +0700, Max Nikulin wrote: On 08/02/2024 22:36, Andy Smith wrote: On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: [629241.074187] scsi host37: usb-storage 1-2:1.0 USB storage is for phones and cameras

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 2/8/24 15:43, Andy Smith wrote: Hello, On Thu, Feb 08, 2024 at 02:20:59PM -0500, Jeffrey Walton wrote: On Thu, Feb 8, 2024 at 11:57 AM Ralph Aichinger wrote: How does a breaking USB disk differ from a breaking SATA disk? I may be mistaken, but I believe AS is talking about USB thumb

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On Thu, Feb 08, 2024 at 08:43:17PM +, Andy Smith wrote: > I really do mean all forms of USB that come over a USB port. That line was meant to read I really do mean all forms of storage that come over a USB port. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Thu, Feb 08, 2024 at 02:20:59PM -0500, Jeffrey Walton wrote: > On Thu, Feb 8, 2024 at 11:57 AM Ralph Aichinger wrote: > > How does a breaking USB disk differ from a breaking SATA disk? > > I may be mistaken, but I believe AS is talking about USB thumb drives, > SDcards and the like. I

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Thu, Feb 08, 2024 at 05:40:54PM +0100, Ralph Aichinger wrote: > On Thu, 2024-02-08 at 15:36 +, Andy Smith wrote: > > I learned not to go there a long time ago and have seen plenty of > > reminders along the way from others' misfortunes to not ever go > > there again myself. > > How

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Fri, Feb 09, 2024 at 12:23:45AM +0700, Max Nikulin wrote: > On 08/02/2024 22:36, Andy Smith wrote: > > On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: > > > [629241.074187] scsi host37: usb-storage 1-2:1.0 > > > > USB storage is for phones and cameras etc, not for serious

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On Thu, Feb 8, 2024 at 11:57 AM Ralph Aichinger wrote: > > On Thu, 2024-02-08 at 15:36 +, Andy Smith wrote: > > USB storage is for phones and cameras etc, not for serious > > computing. Many people will disagree with that statement and say > > they use it all the time and it is fine. > > I am

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 08/02/2024 22:36, Andy Smith wrote: On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: [629241.074187] scsi host37: usb-storage 1-2:1.0 USB storage is for phones and cameras etc, not for serious computing. Do you mean that a proper backup drive should use uas (USB Attached

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On Thu, 2024-02-08 at 15:36 +, Andy Smith wrote: > USB storage is for phones and cameras etc, not for serious > computing. Many people will disagree with that statement and say > they use it all the time and it is fine.  I am clearly in the latter camp. This mail is delivered via a Raspberry

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hi, On Thu, Feb 08, 2024 at 11:14:24AM -0500, Gremlin wrote: > On 2/8/24 10:36, Andy Smith wrote: > > USB storage is for phones and cameras etc, not for serious > > computing. Many people will disagree with that statement and say > > they use it all the time and it is fine. They will keep saying

Re: Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

On 2/8/24 10:36, Andy Smith wrote: Hello, On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: [629241.074187] scsi host37: usb-storage 1-2:1.0 USB storage is for phones and cameras etc, not for serious computing. Many people will disagree with that statement and say they use it all

Things I don't touch with a 3.048m barge pole: USB storage (Was Re: Unidentified subject!)

Hello, On Wed, Feb 07, 2024 at 03:30:29PM -0500, gene heskett wrote: > [629241.074187] scsi host37: usb-storage 1-2:1.0 USB storage is for phones and cameras etc, not for serious computing. Many people will disagree with that statement and say they use it all the time and it is fine. They will

Re: Portable External Hard Drive 2TB (was: Unidentified subject!)

On 2/7/24 21:55, David Christensen wrote: On 1/22/24 19:55, gene heskett wrote: > 2T ssd's: > > It appears

Re: Portable External Hard Drive 2TB (was: Unidentified subject!)

On 2/7/24 21:55, David Christensen wrote: On 1/22/24 19:55, gene heskett wrote: > 2T ssd's: > > It appears

Re: Unidentified subject!

> Well the 2T memory everybody was curious about 3 weeks ago got here early. > > From dmesg after plugging one in: > [629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd > [629241.066221] usb 1-2: New USB device found, idVendor=048d, > idProduct=1234, bcdDevice= 2.00 >

Portable External Hard Drive 2TB (was: Unidentified subject!)

On 1/22/24 19:55, gene heskett wrote: > 2T ssd's: > > It appears Amazon took down the above web page. Using

Unidentified subject!

Well the 2T memory everybody was curious about 3 weeks ago got here early. From dmesg after plugging one in: [629240.916163] usb 1-2: new high-speed USB device number 39 using xhci_hcd [629241.066221] usb 1-2: New USB device found, idVendor=048d, idProduct=1234, bcdDevice= 2.00 [629241.066234]

Unidentified subject!

which poc...@columbus.rr.com -- Hindi madali ang maging ako

Unidentified subject!

Unidentified subject!

The partition table scheme is GPT and UEFI with Secure Boot is enabled. I do not use legacy BIOS with master boot record. Below is the partition layout of my SDD: 536.9MB EFI system partition (ESP) 511.7MB /boot (unencrypted) 100GB encrypted logical volumes (contains 99GB of / partition, 1GB of

Unidentified subject!

Subject: Re: Network connection of a qemu guest. From: Reco Date: Fri, 12 Mar 2021 08:26:51 +0300 > No, it does not work that way. Got the network connection and added documention here.

Re: Unidentified subject!

Dan Ritter wrote: ... > You want to ignore the USB ports and focus on the attached > devices. udev is the mechanism here. > > For example, in /etc/udev/rules.d/70-ups I have: > > SUBSYSTEM=="usb", ATTR{idVendor}=="0764", ATTR{idProduct}=="0501", > SYMLINK+="ups0", GROUP="nut" > > Which means

Unidentified subject!

rhkra...@gmail.com wrote: > (Intentionally cross posted) > > The following quotes are from an email to a rosegarden mail list -- > Rosegarden > is a music notation (mcow) program. > > A user is describing a problem in which it appears the MIDI ports (connected > via USB ports) change on each

Re: Unidentified subject!

Hi. Mail headers are mangled, but: On Sun, Oct 20, 2019 at 07:45:26AM -0700, pe...@easthope.ca wrote: > > And the problem that you're trying to solve by such "predictable" audio > > devices is? > > AUDIODEV=hw:0,0 play MY/m85.WAV AUDIODEV=dmix:CARD=PCH,DEV=0 play MY/m85.WAV Use "aplay

  1   2   3   4   5   6   7   8   9   10   >