[BadDudes]

Being a newbie and an admin wannabe ... may I ask you people if it's advisable to rely on smitty or dig more CLI?

Thanks

[seth]

Thats not a hard choice 1:0 for smitty for sure. Its quite the same in function but smitty is lightning fast compared to the graphical one. You dont need to worry about exporting your graphical display, you can do quick cut and paste and and and. No End for advantages of smitty!

Long live "Agent" Smitty!
Cheers seth

Update: Sorry I misunderstood the question, thought ist was smit vs smitty not smit(ty) vs Commandline.

[exsnafu]

Originally Posted by BadDudes

Being a newbie and an admin wannabe ... may I ask you people if it's advisable to rely on smitty or dig more CLI?

Thanks

if you're new or unsure i'd definitely stick with using smit(ty) but as an aspiring admin you should in parallel try getting used to the cli, if you do things repetitively in smitty then figure out how to do it on the cli and start doing it that way. understanding the underlying actions taking place can be rewarding in its own twisted little way and will help you with your overall understanding of aix... not to mention speed/flexibility.

you can look at the smit logs to see what it's done, you can get the commandline equivalent from smitty itself and you can have smitty generate script.. very powerful tool

[ross.mather]

Smitty is great for helping you get stuff done - and you can always work your way through the smit.script file to find out what the actual command is.

You'll find that you'll want to know commands for scripts and frequent commands from there, so smitty definately is a great plus point of AIX.

[Frans]

smit(ty) is very usefull

when you run a command you can use F6 or esc+6 to see the command
also F8 or esc+8 will show you the short path to the smitty menu

[kganesan]

SMITTY is software management and installation tool command.
DIAG is Perform hardware problem determination command.
in AIX smitty via you can install and configure software and hardware.

Regards,
Karthikeyan

[wojtekr]

smitty is lightning fast, easy to use, powerfull, usefull (F6 feature) tool to become CLI master.
Other GUI tools (pconsole & wsm) are also helpfull to accomplish some tasks. For instance monitoring is not a part of smitty but is available through wsm.

[alexisl]

I would go with smit, there is less chance for error because everything is laid out for you (all the parameters). Sometimes it might be faster to just type the command but there is a much bigger chance for error.

The shortcuts make smit a little faster. Say you want to do something with users, type "smit user" (no quotes), or someting with print queues "smit spooler", or change a file system "smit chfs" and so on. Also works with smitty.

If it is something you do all the time, by all means, use the command line, or better yet, set up an alias. However if it is some you rarely do use smit.

[rodrigo.tocantins]

In crisis situations, you it does not have time to think and it needs to be objective, therefore CLI is the best exit, always reading MAN. To look for always to repeat activity administrative and common to day-by-day through Shell CLI, fortifies the setting of the commands, for this the first step is to use a Workstation Linux with distro of its preference.

_______________________________________

IBM Certified Power Systems
IBM Certified Advanced Technical Expert
IBM Certified Aix/Linux/HACMP/Virtualization/Enterprise
IBM Certified Deployment Professional - Tivoli Storage Manager 5.5
Linuxuser #303212. LPIC - 2

[psvillanueva]

i'll go for 50 / 50