4 ms·
Hmmm... I wonder what went wrong that the author ended up with a shell without line editing and without a properly defined path. I'm sure the article would've b
by johnklos 4y ago
Hmmm... I wonder what went wrong that the author ended up with a shell without line editing and without a properly defined path. I'm sure the article would've been much different were it not for whatever caused that.
- drewg123 4y agoI wonder if he wound up in single user mode using /bin/sh on his first boot, and then after installing stuff, he rebooted at some point and would up with a proper shell?
- lproven 4y agoNo. I am a fairly clueful xNix user and I have been working with xNix boxes on a professional basis for over ⅓ of a century. When I say "CLI editing didn't work", I mean "I can't use the cursor keys to move left and right." TBH I do not care if some weird Emacs keys work. I personally detest both Emacs and Vi. I am very even-handed like that. :-D I am a fairly competent Unix user -- I am typing on an xNix box right now -- but I am also a Mac user and I have been using Macs since System 6 and Windows since v2.01. I tend to prefer GUIs and GUI editors.
- lproven 4y agoThe author is the same person who submitted the link. Me. My username matches the byline on the article: I am using my real name. So feel free to ask away. I am here and I am listening. :-) FWIW I do still have the VM here on my machine, so if you want me to, I can check stuff. However do note that as I said in the article, once I managed to install Xfce, a lot of things magically started working, including CLI editing on the console.