I mix both, for simple tasks like joining a wireless network i use GUI (if its available) Its easier to right click, enter password and enter than ifconfig wlan0 up iwlist wlan0 scan iwlan wlan0 essid <networkname> key <wireless key> dhclient wlan0 BUT for getting down and dirty like routing, network diagnosis, multiple interface management, traffic shaping - I dip into CLI Also GUI are mostly wrappers of CLI commands so they never really get to be as flexible as CLI On 4 March 2014 17:18, Stephen Munguti <kamitu.sm@gmail.com> wrote:
GUI was designed to keep people from understanding what is happening in the back-end. CLI all the way
On Tue, Mar 4, 2014 at 2:26 PM, Thuo Wilson <lixton@gmail.com> wrote:
On 4 March 2014 10:33, Philip Musyoki <pmusyoki@gmail.com> wrote:
powerful
I find myself doing things on CLI linux that i don't even know where the equivalent is on GUI. CLI the best.
Kind Regards, Wilson./
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke
--
Best Regards, Stephen Munguti.
+254720425104
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke