[sf-lug] #/etc/init.d/network/restart
Michael Paoli
Michael.Paoli at cal.berkeley.edu
Tue Jan 8 20:04:23 PST 2019
> From: maestro <maestro415 at gmail.com>
> Subject: Re: [sf-lug] thanks for the help
> Date: Tue, 8 Jan 2019 14:35:40 -0800
You're welcome. Uh, ... huh?
Remember boys and girls, to update your Subject: header.
> just for confirm...
> what does this give?...
> [code]
> #/etc/init.d/network/restart
>
> message ends.
Thanks for letting us know - so we can presume anything that followed was
superfluous and merely contributing to the heat death of the universe, etc.
Where does the [code] end? Oh, ew, is somebody using Microsoft Windows
.ini format? Ewwww... perish the thought. Yeah, that would be for *some
other* list/forum.
$ #/etc/init.d/network/restart
$ /etc/init.d/network/restart
-bash: /etc/init.d/network/restart: No such file or directory
$
The first, a nice comment doing nothing.
If one intended execution as superuser (UID 0 "root"),
the conventional prompt indicating that would be: "# ", not a bare #,
or heck, at least end the prompt with "# " (and not including the double
quote characters).
Results will of course vary, depending upon one's Linux distribution,
if one has /etc/init.d/network/restart or related packages installed,
if one executes with appropriate privilege (e.g. "root" - if needed),
and, oh, maybe bothers to very carefully triple check the command
as root, before viciously/affirmatively striking the <ENTER>/<RETURN>
key (or ^J if you're an extreme purist). Perhaps one made not one, but
(at least) two errors in specifying the command? That's a fairly high
bit (and byte!) error rate for about half a line of code. Use of
sha512sum might help ... but mostly only if the input data is good.
GIGO: https://en.wikipedia.org/wiki/Garbage_in,_garbage_out
Caveat: viruses may cause snarkiness and other malfunctions, mostly a non-
issue for Linux (at least reasonably cared for), the human(s),
however ...
HAL: Well, I don't think there is any question about it. It can only be
attributable to human error. This sort of thing has cropped up before,
and it has always been due to human error.
More information about the sf-lug
mailing list