[olibenu]

My linux installation just turned a year old.
It's a Linux 2.6.33.3-85.fc13.i686.PAE.

I was wondering if there's any stuff I should have learnt
while using it for a year. Things like good dev apps, shortcuts,
tricks and the like.

[BenignDesign]

I suppose that would depend on what you HAVE learned. If everyone recommends the same dev app and you already use it... then this thread was kind of pointless, wasn't it?

[GWatt]

Have you learned about IO redirection? How about man pages?
Just throwing out the two first things I thought.

Fedora specific:
Have you learned how to upgrade your fedora system to the latest version? (F15)

[Nykc]

Have you learned apt-get? Have you learned command line (cd, ls, mkdir)? git? grep? sed?

Now get back to work!

[olibenu]

i've learnt and use:
-man pages
-eclipse, codeblocks
-io redirection too

not learnt
-scripts
-enough not to use virtualbox

[olibenu]

not yet updated to f15. i know how though.
hmmm, apt-get, i use yum.
i've used grep but git and sed, no.
the terminal commands i've used.

[olibenu]

BenignDesign, on 29 June 2011 - 06:01 AM, said:

I suppose that would depend on what you HAVE learned. If everyone recommends the same dev app and you already use it... then this thread was kind of pointless, wasn't it?

I'd hoped for a kind of timeline from those who have used the OS for more than this time.
Something like:
3mnths: mastering log files
6mnths: partition mounting
9mnths: internal mail, shell scripts etc

at least, something that could tell me how far i've gone without taking a test.

[Nykc]

The real answer to your question is what are you trying to accomplish by using Linux? Do you want to learn more about the OS or it's many applications? Do you want to develop on Linux or become a command line ninja?

Do you think Bill Gates and Steve Jobs are douchebags or real men of Genius?

[olibenu]

You've hit the nail on the head.
What I've been trying to say is that I've used it for:
-development (eclipse & codeblocks which isn't really using linux but its apps)
-playing my mp3s (yes, one of the first things i did)
-running windows (on virtualbox, openoffice plays with my line spacings. an expert could recommend something here)

I want to use it for more (and advanced) dev related stuff like:
-debugging, logging
-partition mounting
-managing mail
-shell scripting

and other stuff it might be used for in order of simple to complex
so that i can make a checklist and start a quest.

[olibenu]

when i started this topic, these issues were raised:
- what HAVE I learnt?
- what do I USE my linux for?

so, during the holiday (Nigeria was 51 on Oct 1, sigh!),
i came up with this code to analyze my bash history.

Hopefully, you'll:
- see what I've been doing
- tell me better ways of doing it
- show me what you've been doing (if it isn't too much to ask)
- and i'll check my man pages for more.

I've attached the code here, so just
- download
- terminal: g++ bash_history.cpp -o bash_history
- terminal: ./bash_history ~/.bash_history or ./bash_history ~/.bash_history your_preferred_file
- terminal: gedit ~/.bash_history_frequency& or gedit your_preferred_file&

i've posted some of my own history.

you'll notice that the code uses only the first word (before a space).
this is to avoid exposing other arguments which may contain sensitive information.

unfortunately, this also works against seeing how the professionals use common commands powerfully.
like the echo (16 times) and less (12 times) which i use for hashing like echo -n olibenu | md5sum

if you can tweak the code so that it can teach someone some of your cool tricks, feel free!

exit [130]
cd [53]
ls [37]
man [31]
clear [29]
su [24]
finger [20]
echo [16]
less [12]
doxygen [11]
rpm [6]
lsusb [5]
rm [4]

Attached File(s)

•  bash_history.cpp.txt (6.92K)
  Number of downloads: 102

This post has been edited by olibenu: 05 October 2011 - 06:02 AM

[Tarkenfire]

olibenu, on 29 June 2011 - 06:09 AM, said:

i've learnt and use:
-man pages
-eclipse, codeblocks
-io redirection too

not learnt
-scripts
-enough not to use virtualbox

Basically, if you're conformable with ding most things from a shell window, you can write shell scripts. To be honest, you don't right insanely complex scripts that much, and most are written to preform small tasks because it's quicker to write a shell script than a program. (they are also easier to "time" with cron-stuffs.), so it's not that complicated.

olibenu, on 29 June 2011 - 06:52 AM, said:

not yet updated to f15. i know how though.
hmmm, apt-get, i use yum.
i've used grep but git and sed, no.
the terminal commands i've used.

Don't bother with F15 yet. GNOME 3 is...something that should be avoided for a while. Also, Fedora in general isn't the best "main OS" since it's more or less RHEL's testing ground for stuff they want to test for Red Hat.

[WolfCoder]

Nykc, on 29 June 2011 - 08:05 AM, said:

...
Do you think Bill Gates and Steve Jobs are douchebags or real men of Genius?

A little from column a and a little from column b.

[supersloth]

the real question is why are you assigning yourself artificial timelines? you must be in management.

[jon.kiparsky]

In my experience with Unix/Linux tools, you learn more from doing something with the tools than from trying to read about them. It's only after you understand the usage from experience that you can learn a lot from in-depth study, and that's only when you really want to drill down into the details of that tool.

Learn by doing: make the command line your home, and do everything with command line tools. Develop your code in vi or emacs, and compile it from the command line. Play command-line games, even (nethack is the best time-sink ever).
As you do this, you will find things to learn. Necessity is a great teacher; you need to create necessity.

[NeoTifa]

man man