[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to practice.



For me when I use it enough it sticks.  But there is a old quote someone told me that I don't know the source of, but it really helped me - it goes along the lines of "Why should I memorize something I don't need when I can just go read it from a book when I do need it."

For me, I take that to mean learn everything you can, but for the stuff that doesn't stick, know where to find it.

On Fri, May 18, 2012 at 6:54 AM, shawn wilson <ag4ve.us@gmail.com> wrote:
On Fri, May 18, 2012 at 8:18 AM, Muhammad Yousuf Khan <sirtcp@gmail.com> wrote:
> Ok I have been working in IT network field since 7 years and just one and
> half year back i have started exploring Linux and I believe, someone said to
> me lately that if you start loving black and white terminal then you will
> never look back to Windows GUI.

b/w terminals are lame, most terminals support (at least) 256 colors,
so use them - i like a bright blue prompt with [user@host : pwd]
(actually, sometimes each field is a different color if i feel like
playing). and a bright yellow cursor. i like my black background
though.

> I literally can experience this thing at the
> stage I am standing with Linux. As I consider myself a newbie in Linux but
> according to my previous experience if i don’t practice I will forget things
> very easy (as there are tons of commands to remember which I will forget
> with less or 0 practice).

so, install it as your desktop environment, use it for your servers,
use it as low cost or backup routers (i'd go bsd for this but...).

> so i am here to ask all the old Pros that how you
> guys manage to remember all the commands and practice all the previous work.

i remember the basics really. the rest will come as you have a problem
you bang your head against for a day and then find there is a command
that solves it - you don't really forget after that. seriously,
(besides built-in bash or zsh commands) i probably use ls, echo, cat,
file, vim, chown, chmod, nmap, lsof, iptables, ssh (ssh-keygen etc
too), screen (trying tmux), perl, gdb, gcc, make, service, apt-get,
yum, chkconfig, git, find, xargs, grep.

what's that, about 20 commands? i even included project specific
commands (and forgot others for managing vms etc) for dealing with
code and network stuff.

> Since after the deployment of some Linux services there is only the log
> which i have to see for further errors. So how it is possible to keep in my
> mind all the old stuff and along with that I can move forward with the new
> goals.

actually, you really shouldn't have to review logs much (see
graylog2.... or splunk if you feel like paying). and really, i'm going
through the opposite change as you - i'm trying to get into doing more
things with code on windows and can't remember simple stuff like netsh
commands and the like for basic config (because i hadn't done much
with windows for ~3 years).


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] CAH_OBien+mTR9KjAeRXfZrG0U9z1kqTam+gZo_41QjM0DfpyCA@mail.gmail.com" target="_blank">http://lists.debian.org/[🔎] CAH_OBien+mTR9KjAeRXfZrG0U9z1kqTam+gZo_41QjM0DfpyCA@mail.gmail.com




--
Shane D. Johnson
IT Administrator
Rasmussen Equipment



Reply to: