From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Package compile failures with "internal compiler error: Segmentation fault".
Date: Thu, 05 Sep 2024 09:42:55 +0100 [thread overview]
Message-ID: <1979874.PYKUYFuaPT@rogueboard> (raw)
In-Reply-To: <cdd50f10-c346-ee7b-c5de-b8f8650376b5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
On Thursday 5 September 2024 09:36:36 BST Dale wrote:
> I've ran fsck before mounting on every file system so far. I ran it on
> the OS file systems while booted from the Live image. The others I just
> did before mounting. I realize this doesn't mean the files themselves
> are OK but at least the file system under them is OK.
This could put your mind mostly at rest, at least the OS structure is OK and
the error was not running for too long.
> I'm not sure how
> to know if any damage was done between when the memory stick failed and
> when I started the repair process. I could find the ones I copied from
> place to place and check them but other than watching every single
> video, I'm not sure how to know if one is bad or not. So far,
> thumbnails work. o_O
If you have a copy of these files on another machine, you can run rsync with
--checksum. This will only (re)copy the file over if the checksum is
different.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-05 8:43 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 23:28 [gentoo-user] Package compile failures with "internal compiler error: Segmentation fault" Dale
2024-09-04 0:12 ` [gentoo-user] " Grant Edwards
2024-09-04 0:39 ` Dale
2024-09-04 4:16 ` corbin bird
2024-09-06 20:15 ` Dale
2024-09-06 23:17 ` Michael
2024-09-07 3:02 ` Dale
2024-09-07 22:12 ` Wols Lists
2024-09-08 1:59 ` Dale
2024-09-08 13:32 ` Michael
2024-09-08 9:15 ` Michael
2024-09-08 20:19 ` Wol
2024-09-04 7:53 ` Raffaele Belardi
2024-09-04 4:26 ` [gentoo-user] " Eli Schwartz
2024-09-04 10:48 ` [gentoo-user] " Dale
2024-09-04 11:05 ` Frank Steinmetzger
2024-09-04 11:21 ` Dale
2024-09-04 15:57 ` Peter Humphrey
2024-09-04 19:09 ` Grant Edwards
2024-09-04 21:08 ` Frank Steinmetzger
2024-09-04 21:22 ` Grant Edwards
2024-09-04 21:53 ` Dale
2024-09-04 22:07 ` Grant Edwards
2024-09-04 22:14 ` Dale
2024-09-04 22:38 ` Michael
2024-09-05 0:11 ` Dale
2024-09-05 8:05 ` Michael
2024-09-05 8:36 ` Dale
2024-09-05 8:42 ` Michael [this message]
2024-09-05 10:53 ` Dale
2024-09-05 11:08 ` Michael
2024-09-05 11:30 ` Dale
2024-09-05 18:55 ` Frank Steinmetzger
2024-09-05 22:06 ` Michael
2024-09-06 0:43 ` Dale
2024-09-06 12:21 ` Michael
2024-09-06 21:41 ` Frank Steinmetzger
2024-09-07 9:37 ` Michael
2024-09-07 16:28 ` Frank Steinmetzger
2024-09-07 17:08 ` Mark Knecht
2024-09-14 19:46 ` Dale
2024-09-15 22:29 ` Frank Steinmetzger
2024-09-16 10:24 ` Dale
2024-09-07 22:48 ` Wols Lists
2024-09-08 9:37 ` Michael
2024-09-05 9:08 ` Frank Steinmetzger
2024-09-05 9:36 ` Michael
2024-09-05 10:01 ` Frank Steinmetzger
2024-09-05 10:59 ` Dale
2024-09-04 14:21 ` Grant Edwards
2024-09-04 11:37 ` Dale
2024-09-04 14:23 ` Grant Edwards
2024-09-04 15:58 ` Peter Humphrey
2024-09-04 19:28 ` Dale
2024-09-25 20:41 ` Dale
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=1979874.PYKUYFuaPT@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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