Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Building Docker Containers
Date: Mon, 30 Mar 2020 12:31:11 -0700
Message-ID: <62EB0F33-BE41-4A2F-A876-CEFF965035EC@gmail.com> (raw)
In-Reply-To: <CAPweEDzzC2DrfUJN=CKrbrVxe2H2_by+18YGhUNoxYWEbkAmDQ@mail.gmail.com>



> On Mar 30, 2020, at 11:58 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> On Mon, Mar 30, 2020 at 7:43 PM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> Don’t worry I kept my ssh keys. But I was having additional problems
>> that I believe were self-inflicted through careless pollution of my global
>> package namespace among other things, so I wanted to do a clean
>> install so that I don’t have erroneous bugs crop up due to this during
>> the HDL workflow setup.
> 
> don't do it!  teach yourself where things live, and how to find them,
> and how to safely remove them, rather than assuming that it's ok to
> blow away a box like it's a "toy Windoze machine" ok?
> 
> because you ain't doing that to a server, i can tell you that *right*
> now!  if people are depending on a server to be up, you are *not*
> going to be able to quotes blow it away quotes.
> 
> i managed once to overwrite the contents of /sbin and /usr/sbin and
> other places, once, on an x86 system by unpacking a cpio-formatted ARM
> initrd on it (cpio unpacks to *absolute* paths by default...)
> 
> i absolutely was *not* going to quotes reinstall it quotes because it
> was a mac, which at the time was a f*****g nuisance to put UEFI
> bootable linux on it.  so i rescued it by mounting then chrooting into
> a live bootable install disk, unpacking some of the relevant .deb
> archives (by hand) and manually copying files over, one by one.

Don’t worry, I would never think to do this to a server, let alone one of 
yours, Jacob’s, someone else’s, or another libre-soc server. Unfortunately,
I already have done this to my local pc, but I don’t plan on doing this again. 
I had spent the past week doing the manual investigation and recovery 
method and was still encountering transient bugs and problems. If this 
were a server I would have—preferably not have been so careless 
in the first place, but barring this—continued on in my debugging, and 
reached out to the list for help if I was still unable to solve the issues 
after a second concerted effort. This is the procedure I will follow should
I unfortunately find myself with a buggy OS in the future, however I am 
planning to be much more careful and mindful about my installations 
and configurations moving forward. 

> 
>> It was my mistaken assumption that changing
>> my username would interfere with the proper functioning of my ssh
>> key because it has my old username instead of my new one. I’m happy
>> I was wrong :)
> 
> yes.  ssh keys have absolutely nothing to do with usernames.
> 
> l.

Good to know, thank you very much!

Cole


_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

  parent reply index

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 13:48 Immanuel, Yehowshua U
2020-03-29 15:26 ` Luke Kenneth Casson Leighton
2020-03-29 16:03   ` Immanuel, Yehowshua U
2020-03-29 16:14     ` Luke Kenneth Casson Leighton
2020-03-29 16:19       ` Immanuel, Yehowshua U
2020-03-29 16:24         ` Luke Kenneth Casson Leighton
2020-03-29 17:21           ` Jacob Lifshay
2020-03-29 18:48             ` Luke Kenneth Casson Leighton
2020-03-29 18:59               ` Jacob Lifshay
2020-03-29 19:33                 ` Immanuel, Yehowshua U
2020-03-29 19:56                   ` Jacob Lifshay
2020-03-29 19:57                   ` Luke Kenneth Casson Leighton
2020-03-29 20:02                     ` Jacob Lifshay
2020-03-29 20:51                       ` Cole Poirier
2020-03-29 21:12                         ` Luke Kenneth Casson Leighton
2020-03-29 21:34                           ` Cole Poirier
2020-03-30  8:59                             ` Luke Kenneth Casson Leighton
2020-03-30 18:13                               ` Jacob Lifshay
2020-03-30 18:43                                 ` Cole Poirier
2020-03-30 18:58                                   ` Luke Kenneth Casson Leighton
2020-03-30 19:08                                     ` Jacob Lifshay
2020-03-30 19:31                                     ` Cole Poirier [this message]
2020-03-29 16:19       ` Luke Kenneth Casson Leighton

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=62EB0F33-BE41-4A2F-A876-CEFF965035EC@gmail.com \
    --to=colepoirier@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git