That was an overly FLAMBOYANT display of my grief at having wronged you.
I was saying that you may ( hopefully ) one day attain the title "Great One" or you may ( unknownst to me) already hold it.
No sarcasm intended. No _obvious_ metaphor.
syntax error - poorly constructed if-then-else statement
-- "Virklich, das tut mir leid!" -- ____________________________________________________
Oh, great, _now_ my memory disgorges this !
***** In recent years , Ubuntu _boots_ *****
***** using "Dash" rather than "Bash". *****
This suggests a different directory path name, and likely
not .bashrc as an initial file ( at system boot ).
-
Many Android apps come with "BusyBox" incorporated into
the package just to make life easier for us "command line"
junkies, and I _don't_ doubt that Ubuntu has BusyBox ( and
therefore Bash ) onboard for possible invocation by users.
( Dash, _if_ it is virtually the same as NetBSD ASH, comes
equipped only with the "dd" built-in-command and not the
more familiar "cp" built-in-command. This is a strong
selling point for Bash. <grin> )
- __________________________
dash(1) - Linux man page __________________________
. . . A login shell first reads commands from the files
/etc/profile and
.profile if they exist.
If the environment variable ENV
is set on entry to an interactive shell, or
is set in the .profile of a login shell,
the shell next reads commands
from the file named in ENV.
Therefore, a user should place commands that are to be
executed only at login time in the .profile file, and commands
that are executed for every interactive shell inside the ENV file.
To set the ENV variable to some file,
place the following line in your .profile of your home directory
ENV=$HOME/.shinit; export ENV
substituting for ''.shinit'' any filename you wish.
If command line arguments besides the options have been
specified, then the shell treats the first argument as the
name of a file from which to read commands (a shell script),
and the remaining arguments are set as the
positional parameters of the shell ($1, $2, etc). Otherwise,
the shell reads commands from its standard input.
That was an overly FLAMBOYANT display of my grief
at having wronged you.
I was saying that you may ( hopefully ) one day attain
the title "Great One" or you may ( unknownst to me)
already hold it.
No sarcasm intended.
No _obvious_ metaphor.
syntax error - poorly constructed if-then-else statement
-- "Virklich, das tut mir leid!" -- _______ _______ _______ _______ _______ _______ ___
_______
Oh, great, _now_ my memory disgorges this !
***** In recent years , Ubuntu _boots_ *****
***** using "Dash" rather than "Bash". *****
This suggests a different directory path name, and likely
not .bashrc as an initial file ( at system boot ).
-
Many Android apps come with "BusyBox" incorporated into
the package just to make life easier for us "command line"
junkies, and I _don't_ doubt that Ubuntu has BusyBox ( and
therefore Bash ) onboard for possible invocation by users.
-
( Dash, _if_ it is virtually the same as NetBSD ASH, comes
equipped only with the "dd" built-in-command and not the
more familiar "cp" built-in-command. This is a strong
selling point for Bash. <grin> )
- _______ _______ _____
_______
dash(1) - Linux man page _______ _______ _____
_______
-
. . . A login shell first reads commands from the files
.profile if they exist.
If the environment variable ENV
is set on entry to an interactive shell, or
is set in the .profile of a login shell,
the shell next reads commands
from the file named in ENV.
-
Therefore, a user should place commands that are to be
executed only at login time in the .profile file, and commands
that are executed for every interactive shell inside the ENV file.
-
To set the ENV variable to some file,
place the following line in your .profile of your home directory
ENV=$HOME/.shinit; export ENV
substituting for ''.shinit'' any filename you wish.
-
If command line arguments besides the options have been
specified, then the shell treats the first argument as the
name of a file from which to read commands (a shell script),
and the remaining arguments are set as the
positional parameters of the shell ($1, $2, etc). Otherwise,
the shell reads commands from its standard input.