From: HiPhish <HiPhish@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux-firmware-network-20230804_1: [unpack] failed to unpack files from archive
Date: Fri, 15 Sep 2023 21:19:30 +0200 [thread overview]
Message-ID: <20230915191930.wW4bqHlWQTlVLrnrnopwH3Pum8JoxFOTFK_Dp0Xok0M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46054@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
New comment by HiPhish on void-packages repository
https://github.com/void-linux/void-packages/issues/46054#issuecomment-1721733991
Comment:
Well, that sucks. I have bought a new SSD, can I simply use `dd if=/dev/sda of=/dev/sdb` (with the proper device paths substituted) to get a drop-in replacement clone or should I re-install Void from scratch on the new drive? The new drive is now 2TB large (the old one was 1TB), I don't know if that is relevant. I don't feel like re-installing everything from scratch, but I don't want a broken system either.
next prev parent reply other threads:[~2023-09-15 19:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 7:41 [ISSUE] " HiPhish
2023-09-14 7:51 ` classabbyamp
2023-09-14 7:54 ` HiPhish
2023-09-14 7:56 ` classabbyamp
2023-09-14 7:56 ` classabbyamp
2023-09-14 12:47 ` HiPhish
2023-09-14 13:00 ` Duncaen
2023-09-14 13:03 ` HiPhish
2023-09-14 13:06 ` Duncaen
2023-09-14 13:07 ` Anachron
2023-09-14 13:14 ` HiPhish
2023-09-14 13:17 ` Duncaen
2023-09-14 13:19 ` Duncaen
2023-09-14 13:31 ` HiPhish
2023-09-14 13:33 ` HiPhish
2023-09-14 13:47 ` Duncaen
2023-09-15 11:51 ` HiPhish
2023-09-15 16:54 ` Anachron
2023-09-15 19:19 ` HiPhish [this message]
2023-09-16 15:44 ` Anachron
2023-09-16 15:45 ` Anachron
2023-09-16 15:46 ` Anachron
2023-09-20 17:05 ` HiPhish
2023-09-20 17:05 ` [ISSUE] [CLOSED] " HiPhish
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=20230915191930.wW4bqHlWQTlVLrnrnopwH3Pum8JoxFOTFK_Dp0Xok0M@z \
--to=hiphish@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).