Date: Thu, 04 Jun 2020 12:40:02 +0200 From: Ralf Mardorf <ralf.mardorf@rocketmail.com> To: freebsd-questions@freebsd.org Subject: Re: Mininal skills Message-ID: <eb6a0c9be7202228c69caeb7c5387d3305ad7b98.camel@rocketmail.com> In-Reply-To: <CAEJNuHz4_OALKm%2BGPPvH0cTw58D6vpxfP4orkEZeWjsZye1FWA@mail.gmail.com> References: <CY4PR19MB0104A2C03F4D66A1DA251A23F9880@CY4PR19MB0104.namprd19.prod.outlook.com> <CAEJNuHwUWB1EgtnhOYvEcBdH3Tip%2B5H8YyvViD9zZU70mHO-Xg@mail.gmail.com> <20200604103920.20ee2d27@archlinux> <CAEJNuHz4_OALKm%2BGPPvH0cTw58D6vpxfP4orkEZeWjsZye1FWA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2020-06-04 at 11:19 +0100, Ottavio Caruso wrote: > On Thu, 4 Jun 2020 at 09:39, Ralf Mardorf wrote: > > On Thu, 4 Jun 2020 09:04:45 +0100, Ottavio Caruso wrote: > > > Install, uninstall, break, fix, reinstall, configure. > > ^^^^^ :D > > I don't know what this is. Never happened to me. > > > > For those who "decide" to "break", first becoming familiar with backup > > strategies might be a good idea. > > You missed the "do it in a VM first". If you've never broken a system > maybe it's because you haven't tried hard. > > By being able to use virtualisation, one also picks other skills. I've > learnt a lot by using qemu, setting up virtual serial consoles, > virtual interfaces, ssh forwarding, etc. Things you can not usually do > on bare metal. I'm kidding ;). It's not that hard to break an install. For example # rm -Ir /tmp/foo/* could easily become # rm -Ir / tmp/foo/* or # rm -Ir /tmp/foo/ * due to a human typo or failure of an aged keyboard. A prompt before removing recursively not necessarily does prevent against continuing with the next mistake.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eb6a0c9be7202228c69caeb7c5387d3305ad7b98.camel>