Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Taming The Data Destroyer
Date: 18 Nov 2025 06:32:11 GMT
Lines: 18
Message-ID: <mo2i7aFrmmhU1@mid.individual.net>
References: <10fe1ec$ipc8$1@dont-email.me> <87a50k5yt3.fsf@atr2.ath.cx> <10fggbe$187pd$4@dont-email.me> <R5ycnRlxMf2JSYb0nZ2dnZfqnPednZ2d@giganews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net imMdQdwgMJWKmvhR8EKGtQ9bas3aAvJIBGnxeyXM16R9f1FoqM
Cancel-Lock: sha1:+aeU/PqN+pER1ZeUFhP1/6h4L84= sha256:2dV0SeDFupKOMPTlftcZV++mEuaAa8TMPddt5LR0sts=
User-Agent: Pan/0.162 (Pokrosvk)
Xref: csiph.com comp.os.linux.misc:77704

On Mon, 17 Nov 2025 21:04:04 -0500, c186282 wrote:

> On 11/17/25 19:58, Lawrence D’Oliveiro wrote:
>> On Mon, 17 Nov 2025 12:55:20 -0500, jayjwa wrote:
>> 
>>>> The “lsblk” command can be handy for confirming which block device
>>>> you should be writing to
>>>
>>> What, you don't parse /proc/partitions yourself?
>> 
>>      lsblk -J
> 
>    Why re-invent the wheel eh ? Parsing /proc/partitions is a pain.
>    'lsblk' already does if for you. You can redirect output to a file or
>    capture it direct with system calls in various langs.

Particularly when 'lsblk -e7' gets rid of the 67 loops snap happily 
creates on Ubuntu.