2 ms·
1. How long have you been using command line? 2. So don't use Vi/Vim (or Emac for that matter). I always use graphical editors unless I'm on a remote host or j
by eximius 12y ago
1. How long have you been using command line?
2. So don't use Vi/Vim (or Emac for that matter). I always use graphical editors unless I'm on a remote host or just wanna make a real quick edit in which case I use nano. It is, by far, simpler and much easier to use.
3. Help? ... Really, depending on how long you've been using it, the best way is practice. Try doing an Arch Linux install or an LFS install. Don't be intimidated by either, they have excellent documentation. Just... use a blank machine so you don't break nothin'. :)
3.5 Alternatives: This is where google needs to come in. What exactly do you need alternatives FOR? Firewall? gufw works. Otherwise... idk, what do you need? If it doesn't exist... you could write one yourself? (that is slightly hardcore though. lol)
- eximius 12y agoI should note that I've been using CLI stuff for... oh, 8 years? I can't really point to a specific date when I got comfortable with it. I just, got better at it and grew more comfortable with basic tasks as I went. Then I'd fuck something up (apt-get remove gnome-common, I believe was my first big mistake... that was a fun night learning to fix that :)) and be less sure of myself, but learn from it and grow. But you don't have to be totally comfortable. There are a lot of things you need to do from the command line. But you can use GUI as much as possible and script away the rest of the things you're uncomfortable with. It would be pretty easy to write a Python or Go wrapper around some commands and have GUI's with buttons to do common tasks.