From: Thorsten Glaser <tg@debian.org>
To: Bill Unruh <unruh@physics.ubc.ca>
Cc: util-linux@vger.kernel.org
Subject: Re: fdisk corrupts data on USB stick
Date: Mon, 29 Jan 2024 22:45:37 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2401292243180.19873@herc.mirbsd.org> (raw)
In-Reply-To: <10251865-9fc4-2dff-1054-673e64c67fe2@physics.ubc.ca>
Bill Unruh dixit:
> Great. I am just pointing out a program which seems to do exactly what you
> want.
It’s called fdisk. This does what I want. Only the one from
util-linux does more.
> Clearly had others know of your manifold-boot, they might well have used that
> instead of instead of reinventing isohybrid.
Huh? Grml used it.
Anyway, that’s independent, as the problem here does not come from
initial partitioning but from adding one more partition.
And I got an actually useful reply in the other subthread, so no
need to continue here.
bye,
//mirabilos
--
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend. -- Andreas Bogk über boehm-gc in d.a.s.r
next prev parent reply other threads:[~2024-01-29 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 17:04 fdisk corrupts data on USB stick Thorsten Glaser
2024-01-29 20:01 ` Thomas Weißschuh
2024-01-29 20:27 ` Thorsten Glaser
2024-01-29 20:44 ` Thomas Weißschuh
2024-01-29 20:56 ` Karel Zak
2024-01-29 21:29 ` Thorsten Glaser
2024-01-29 22:11 ` Bill Unruh
2024-01-29 22:27 ` Thorsten Glaser
2024-01-29 22:36 ` Bill Unruh
2024-01-29 22:45 ` Thorsten Glaser [this message]
2024-01-29 20:44 ` Bill Unruh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSM.4.64L.2401292243180.19873@herc.mirbsd.org \
--to=tg@debian.org \
--cc=unruh@physics.ubc.ca \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).