Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
sehrguey@debian:~$ sudo apt install sudo
[sudo] password for sehrguey:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
sudo is already the newest version (1.9.5p2-3).
0 upgraded, 0 newly installed, 0 to remove and 50 not upgraded.
sehrguey@debian:~$ sudo mount /dev/sda1 teradisk
bash: sudo: command not found
sehrguey@debian:~$ sudo mount /dev/sda1 teradisk
bash: sudo: command not found
There are 2 spaces after "mount", should only be one.
Command won't work unless you are in the directory containing "teradisk" directory; otherwise specify full path to it.
Maybe filesystem needs to be specified if not defined in fstab (not sure about this one).
Or possibly something else.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”Remember toBACKUP!
seog:
sunrat is exactly right. It's not sudo itself that bash is complaining about; rather it's the malformed mount command. I can re-create the behavior on my system by mis-spelling mount.
A sequence of IFS whitespace characters is also treated as a delimiter.
sunrat wrote: ↑2022-08-05 22:53
Command won't work unless you are in the directory containing "teradisk" directory; otherwise specify full path to it.
Maybe filesystem needs to be specified if not defined in fstab (not sure about this one).
Good point but the error would be different in that case:
sehrguey@debian:~$ sudo mkdir 1
sehrguey@debian:~$
sehrguey@debian:~$ sudo mount /dev/sda1 teradisk
bash: sudo: command not found
sehrguey@debian:~$ sudo rm -r 1
sehrguey@debian:~$
which clears apt of all suspicions and this time the odd space was eliminated from 'sudo mount' and I be f***ed if I can see any rexp or misspelling in the command.
Now, to make a short story long (not my fault you asked for it) I am lazy and so as not to type 'sudo mount...' I kept it in a Text Editor file and used to use when needed. It worked OK. Then gnome slowed down immodestly prompting to switch over to Xfce. Now everything is nice except for mounting the usual way.
Noteworthy: when I type the command manually bash is happy and keeps quiet just doing its job. But I am still lazy.
Any idea or suggestion would be dearly appreciated.
before switching to Xfcee (while at gnome) I used the same copy-past technique from that very Text Editor for months. And yes, I tried the remedy suggested in viewtopic.php?p=757228#p757228 with the result presented in my second message.
OK, it's not really a situation, I can type yet, however just from pure curiosity - what the heck?
You can't believe to something you choose not to believe to. I believe there was the yes with conscientiously reproducing each of steps You suggested (whew! 498 MB downloaded at 'apt full-upgrade'!)
Anyway I feel this conversation deviates from the issue at hand and slides into piquing of super geeks personalities. No thank you! Let's forget this little quirk and enjoy life instead.
Please mark the thread as solved. (I don't know how to do it).
lindi wrote: ↑2022-08-06 07:37You can use multiple whitespace characters if you like. See "man bash", section on "Word splitting":
Good point but the error would be different in that case:
sehrguey@debian:~$ sudo apt install sudo
[sudo] password for sehrguey:
[...]
sehrguey@debian:~$ sudo mount /dev/sda1 teradisk
bash: sudo: command not found
The first output show's sudo successful execution.
The second shows that "sudo " is simply not found at all - it is nothing to do with the mount command, nor the number of spaces, but one of those is not a space - so some "non-printable special characters" (from copy and paste), is almost certainly the culprit.
sehrguey@debian:~$ sudo mount /dev/sda1 teradisk
bash: sudo: command not found
sehrguey@debian:~$ history | tail -n 2 | cat -A
969 M-oM-;M-?sudo mount /dev/sda1 teradisk$
970 history | tail -n 2 | cat -A$
I tried it before yet did not get the meaning of '?' in the output. After the invisible culprit was deleted the command worked as expected and hence 2 conclusions:
1) I owe you an apology to You for taking up so much of Your precious time;
2) bash under Xfce is pickier than under gdm.
Thank You for Your tolerance and patience.
You are right, maybe I'm too rushy at jumping at wrong conclusions, it's only that I used that very same line (containing those pesky special characters) for months when under gnome without a hitch and the problem popped up after switching to Xfce environment.
Anyway, presently the special character is eliminated and bash responds as expected for which I'd like to thank all who found time to help me understand the issue.
Yours`
sehrguey
So was this a copy&paste issue? Or were you just using the up arrow to bring up the old command?
The OP shows a lamentable lack of detail that should be avoided in future. Always explain exactly what you have done in as much detail as possible. We're not psychic.
yes, Sir Head_, so it was, the copy&paste from a file and not revoking the line from the terminal history. Sorry for the paranoically curt style of the OP, Sir. Never-never again. Faith.
dear cynwulf thank You for the link provided, I'll sure follow it. right now cannot find the button here to click up my gratitude to You