Date: Tue, 21 Mar 2017 10:28:36 -0500 (CDT) From: "Valeri Galtsev" <galtsev@kicp.uchicago.edu> To: Trond =?iso-8859-1?Q?Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> Cc: "Ernie Luzar" <luzar722@gmail.com>, "FreeBSD questions" <freebsd-questions@freebsd.org> Subject: Re: command line history broken in 11.0 Message-ID: <64898.128.135.52.6.1490110116.squirrel@cosmo.uchicago.edu> In-Reply-To: <alpine.BSF.2.20.1703211544340.533@mail.fig.ol.no> References: <58D019EE.9030508@gmail.com> <alpine.BSF.2.20.1703210942220.533@mail.fig.ol.no> <58D1310E.6050000@gmail.com> <alpine.BSF.2.20.1703211544340.533@mail.fig.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, March 21, 2017 9:48 am, Trond Endrestøl wrote: > On Tue, 21 Mar 2017 09:56-0400, Ernie Luzar wrote: > > Running a command like this one in csh has always had the desired > effect: > > shutdown -r now Upgrade to base/stable/11 r315683. ; exit > > I usually just type in the first initial characters, like "shu", hit > the up arrow key one or more times, edit the command if needed, read > the entire command one more time, and hit the enter key. During rather long sysadmin life I learn to never do anything like that. I even can point to some examples when doing things differently screwed up fellow sysadmin (luckily that was another guy in all cases): 1. You want to execute the command and _know_ that you executed right command: _type_ the whole path to the command beginning from leading slash, e.g.: /usr/bin/su One day you will be in unusual environment, not doing so, e.g., just executing su may screw you up. This way smart students caught my older sysadmin mate: they asked him to help them with something from their account, and one of the super user commands he predictably executed was script with the same name they placed in their PATH, that piped what they needed into actual command. Bingo, they owned him. 2. Never use my own history, to execute same or similar command. You may accidentally execute next that command in history (if keyboard/ screen is slow...) Recipe for big screw up, hence bad habit. 3. Never edit different command from history. Similar recipe for screw up, psychology is such that often it is "wishful reading" - you see what you expect/want to see instead of similar yet different thing. Typing the whole command with all options forces your brain work though it thus you will be doing what you actually want to do. I know this is digression from the thread, my apologies for that. But I'd love to hear what others may add in the same lines of good sysadmin's habits. Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64898.128.135.52.6.1490110116.squirrel>