From 18d1e3039d61b8b5bee99f1845dd4a628903cb36 Mon Sep 17 00:00:00 2001 From: 53hornet Date: Thu, 30 Dec 2021 09:05:38 -0500 Subject: fix: correction and footnote --- posts/2021-12-15-rescuing-freebsd-the-unix-way.php | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'posts/2021-12-15-rescuing-freebsd-the-unix-way.php') diff --git a/posts/2021-12-15-rescuing-freebsd-the-unix-way.php b/posts/2021-12-15-rescuing-freebsd-the-unix-way.php index 306d4d0..f552c62 100644 --- a/posts/2021-12-15-rescuing-freebsd-the-unix-way.php +++ b/posts/2021-12-15-rescuing-freebsd-the-unix-way.php @@ -19,12 +19,12 @@

- So now I could start to fearlessly think about un-effing my install. This is where most people (previously including myself) would suck it up, start from scratch with a USB installer, try to remember all of the customization steps they took to bring the system back to its current working state, and restore user data. But I'm not the man I once was. I've been playing this game long enough. I don't go crawling back to the dusty install media when something as trivial as critical system files go missing or corrupt. I know what I did wrong and I can think of several creative ways to fix it. Say it with me: + So now I could start to fearlessly think about un-effing my install. This is where most people (previously including myself) would suck it up and pull out the install media, try to remember all of the customization steps they took to bring the system back to its current working state, and restore user data. But I'm not the man I once was. I've been playing this game long enough. I don't go crawling back to the dusty install media when something as trivial as critical system files go missing or corrupt. I know what I did wrong and I can think of several creative ways to fix it. Say it with me: it's a unix system

- First of all, my entire system (sans /usr/bin is still somewhat operational. I have access to a root shell (and my X session with a browser) so I'm in pretty good shape. I am lacking some very basic core utilities but I might be able to get them back without even rebooting. I don't have any system-wide snapshots to restore from but I do have another running FreeBSD 13.0-RELEASE system on my network: my server. rclone worked to move data over there in an emergency, so I'll use that to copy my coreutils back where they belong. And it worked. + First of all, my entire system (sans /usr/bin is still somewhat operational. I have access to a root shell (and my X session with a browser) so I'm in pretty good shape. I am lacking some very basic core utilities but I might be able to get them back without even rebooting. I don't have any system-wide snapshots to restore from but I do have another running FreeBSD 13.0-RELEASE system on my network: my server. rclone worked to move data over there in an emergency, so I'll use that to copy my coreutils back where they belong. And it worked. [2] back in business

@@ -174,4 +174,7 @@
  • I actually did move my FreeBSD source to my server to let it pull changes and do automatic builds. Turns out it can chunk out the whole world and kernel in about 1.5 hours.
    • +
  • + I now know you can use the readonly /rescue utilities (such as /rescue/tar) to help with this. +
    • -- cgit v1.2.3