OS and Software > All Things Unix > This may sound silly....

This may sound silly....

reply to donoreo
Fucking korn shell is pissing me off. I do not know how to do the most basic tasks and it is frustrating the hell out of me.

reply to dennismurphy

if [ -x /usr/local/bin/bash ]; then
  exec /usr/local/bin/bash
fi
 

reply to donoreo
After working on Sun and HP systems for many years, my company tried to get us to use AIX systems a few years ago. Neither I (Oracle DBA) nor my department's system administrator liked them. It took major backing from our senior vice president, but we finally sent them packing and were allowed to purchase new Sun systems.

Tim
--
"Life is like this long line, except at the end there ain't no merry-go-round." - Arthur on The King of Queens
~ Project Hope ~

reply to donoreo
I don't know exactly what level of tips you are looking for. I can say that the first thing that I do when I get into a ksh is "set -o vi" so that I can retrieve/modify previously issued commands in the history using vi keystrokes. You can also specify emacs instead of vi on that setting if you are an emacs lover.

So for example:
exec ksh
set -o vi
ls -l /blah/blah2/stuff
(other work goes on here)
esc k Retreives most recent command issued.
Additional presses of "k" retrieves successively older commands.
After first "esc k" you can search for a command
with "/string-to-match". For example "esc k /stuff" would
search back through the history for a line with "stuff" in it, perhaps
the one I typed above. "n" will repeat that same search.
Once a command is retrieved, you can modify it using vi commands
"l" to move right, "h" to move left, "$" to move cursor to end of line,
"r" to replace at cursor, "i" to begin insertion at cursor (exit insert
mode with esc key, "x" to delete character at cursor, etc, etc.

So all of that is functionally equivalent to using up/down/left/right arrows and "ctrl r" to search history in a bash shell.

Is that useful to you, or did I just shoot and miss in the dark?

--
nohup rm -fr /&

I even use "set -o vi" on all my Linux systems. It is the first thing I put in my profile when setting up a system.

Tim

reply to sempergoofy
That is useful, ideally I would like it to be the same as bash for basic things like command history, file name completion, etc.

Have you seen this page? Interactive Korn shell for bash users

esc \
will complete a filename.

I don't know how to make it work like bash works. Maybe that is why there is a bash?

In the end, there is always »www2.research.att.com/sw/downloa···ksh.html
--
nohup rm -fr /&

reply to donoreo
Here is a general Shell resource site that I have always found very useful, although I haven't visited it in the past few years: »www.shelldorado.com/

Tim

Oh yeah. I have trolled shelldorado.com many times in the past. Great site for examples and stuff.
--
nohup rm -fr /&

reply to donoreo
I'm a full time AIX admin. People mentioned about navigating through a shell. You could just call a bash shell and operate out of that if you're more comfortable.

However, you're going to get into some of the more detailed commands that become different than Linux.

Things like ls/cd/mv/etc... the pure basic commands, are basically the same.

Everything else piggy backs from ls/ch/rm/etc. Instead of vgdisplay, you use lsvg.

Another thing is called "smitty". You can just type that command in the prompt and it'll take you through a menu-based window of your options that you can navigate with your keyboard. You can hit F3 (or escape 3) to go up a level. You can type "smitty user" to go to a short menu for user management. You can usually see the name of the short menu. Also, before you finally fire off a command, you can hit F6 inside of the smit menu and it'll tell you the actual command that is being executed, so you can notate it for future reference. PM me if you need assistance with any tasks.

As a native Linux user, you may have more problems completing your tasks than simply getting used to KSH.
--
A government big enough to give you everything you want, is strong enough to take everything you have. -MLK

Thanks for the offer. I do have access to smitty, but not sure how much in it, since I am in as a regular user and not root. I am getting used to the annoyance of two key strokes for history, etc, rather than one.

Another good command is "resize". If you resize your terminal and then try to get into the smit menu, you may notice that your shit gets all garbled up. Just type "resize" and try again, rather than exiting/reopening your terminal.

If you could let me know about some of the tasks you're looking to accomplish, or do on a regular basis, I could assist you. Since you don't have root, you're obviously not doing any kind of volume group management or file system management.
--
A government big enough to give you everything you want, is strong enough to take everything you have. -MLK

Screwing around with the smit menu, and then hitting F6 before I would normally hit enter has helped me learn how to use various commands that I otherwise wouldn't have learned.
--
A government big enough to give you everything you want, is strong enough to take everything you have. -MLK