Yes, I know, I've done it too at the command line It was just a strange thing to suggest for a use case comparison between command line and gui when both can actually do it. My point was let the user decide the tool to use with the task at hand.

Checkmate

A few days ago I installed a new HP All-N-One that was not yet supported by Slack64-C so I made and installed the new hplip package which I blacklisted.
There's two ways to do it.

CLI
su
slackpkg blacklist hplip

GUI
kdesu thunar (cuz dolphin often wont work)
etc>slackpkg>blacklist>(add) hplip

CLI for me is faster

I remember when k3b wouldn't work but the CLI always dose.

man up dude !
log in as root

don't take the name of root in vain! :-)
I'd use the even shorter form:
Especially repeated tasks are indeed much better to script. I'd say that rather than graphical tools replacing the cli tools, I'd prefer graphical tools that are a front-end to the real cli stuff. On top of being proven to work (the cli stuff) they lend themselves to scripting much better than any gui. Then again, a gui can be practical for purposes of overview, or -best of all- generating that complicated command line, which you then can copy/paste and put into your script :-)

Uh, unless I missed something su does by default log into root.

I'm too lazy for all that.
Right click desktop > leave > logout > type "root" > type password > press enter > open terminal > slackpkg blacklist hplip

For the record, Slackware does include KDE partition manager in extra/ so i dont see the point of this "riddle".

No. I can do everything I need to do , and more, with a basic install.
More crap and the next thing you know Wizards will appear. I can get those in Redmond.

only kind of sort of most of the programs in /sbin and /usr/sbin will not run
unless you are loged in as root you don't get root's environment
I don't think you get to write to anything owned by
root like /etc

the way I see it is if I have to type in my 13 charter root password blind
I may as well go ahead and log in to a virtual terminal as root

I was a DOS user long before I ever heard of linux so I know how NOT to trash a system while wielding the power of root
(but just encase I have another copy of linux installed and the install disk handy)

crtl+alt+f6 type "root" type "root's password"

unless you have changed /etc/initab to run gettys for all 6 virtual terminals in run level 4 and 5
then it would be crtl+alt+ f1 to f6

Or get used to GNU screen and keep a root window around. Window 0 is my designated root window -- no need to switch in and out of X, and I only use window 0 if I'm actually doing something that requires root access. GNU screen is one of the best CLI applications in existence. It really makes the terminal usable.

what dose the command line for that look like

the virtual terminal is like running around in my old stomping grounds
(from my DOS days)

I edited that first post you quoted I had sudo and su confused I never use ether one sense I found out about the limitations of them and had to set a long and complex root pass word I could remember

If you're just running one command why don't you use the "-c" parameter of su? (This is why I don't see any reason to use sudo except for gksu for graphical distributions like openSUSE, Fedora or whatever..)

This is going a bit offtopic but sudo has a couple of goodies if compared to "su -c" such as the possibility to restrict/set the environment properly (eg. make sure that users are running things in a trusted PATH like /sbin/fdisk rather than /home/joe/bin/fdisk) and better control over who does and when something can be done (eg. i want to allow webdeveloper01 to restart apache but i don't want him to do anything else).

Not saying that it's "better" or "worse" than su -c, it's a good tool for those who need its features and no one is forced to use it either.