What to do after installing ubuntu 12.04

[Lexcortex]

What do you right after installing ubuntu 12.04? just need some help...

[lucid]

Lol I don't know go to the bathroom? Make a sandwich? Uninstall ubuntu and get a better distro?

[Xires]

set up personal shell environment, enable root, remove bloat, modify a few init scripts, modify PAM security crap, add a few groups, reassign groups for specific binaries, adjust sources.list, install useful CLI tools, secure permissions, limited optimization, install ksplice, install useful GUI tools, secondary optimization, set up VM environment, install Intel compiler suite, install needed documentation for important libraries, set up personal GUI environment, test->fix->repeat, bench->optimize->repeat, audit->secure->repeat, bitch about everything that went wrong, watch movie, remember something important previously forgotten, bitch about how it was Ubuntu's fault, re-analyze system, test->fix->repeat, bench->optimize->repeat, audit->secure->repeat, consider installing something else, load up some VMs w/ different distros for testing, consider the amount of work just done & having to do it all over again, never quite get un-lazy enough to do it outside a fresh system, audit->secure->repeat, remember the glory days, remind self of eternal grumpiness, eventually get around to actually doing some work, audit->secure->repeat(forever)

[Kulverstukas]

What xires said + install gnome?

[Xires]

What xires said + install gnome?

I think Kulverstukas means GNOME3 rather than Ubuntu's crappy Unity BS.  Personally, I dislike the newer GNOME and prefer XFCE.  Of course, if you're new to it, then you should experiment with all of them until you find something that you like.  Remember that it's more important to find something that you can USE, not just something that LOOKS pretty.  There's no sense in having eye candy that you have to fight with for functionality.

[Lexcortex]

Thanks for your contribution, but what about some configurations to do, and packages or programs to install or download, as a developer in general.

[Kulverstukas]

That usually depends on what you want to do, but you could get some great gedit plugins: http://evilzone.org/scripting-languages/%28python%29-gedit-plugins-every-coder-must-have/msg8276/#msg8276

and install Geany as a scripting IDE. It's basically Notepad++ for linux

[lucid]

I think Kulverstukas means GNOME3 rather than Ubuntu's crappy Unity BS.  Personally, I dislike the newer GNOME and prefer XFCE.  Of course, if you're new to it, then you should experiment with all of them until you find something that you like.  Remember that it's more important to find something that you can USE, not just something that LOOKS pretty.  There's no sense in having eye candy that you have to fight with for functionality.

If using GNOME, GNOME2 is where it's at. Although I prefer openbox. Not a huge XFCE fan.

[Snayler]

list of stuff

Nice list Xires. I like especially the "audit->secure->repeat" part and how you repeated it multiple times. One can't stress enough how important it is to keep testing your system's security, even after you think it is already secured.

On-topic: OP, Get Conky! You'll sure have some fun with it.

[lucid]

but what about some configurations to do

For that I shall refer you to Xires' previous list. Otherwise, I don't know, mess around with iptables.

[Axon]

Start from here.
http://evilzone.org/ebooks/the-linux-command-line-a-complete-introduction/msg33243/#msg33243
Learn basic command lines to help you navigate your system properly.

[proxx]

What do you right after installing ubuntu 12.04? just need some help...

Do whatever it is you do , thats what an OS is for.
Break it would be my advice, that way I learned the most.

Use the terminal , prefer the terminal.
The disadvantage of ubuntu and all its GUI's is that it hides the magic behind the curtains.

[Xires]

I don't personally see Ubuntu as having a disadvantage there as the powerful repositories give you access to anything you want.  If you want a pretty lean development system, Ubuntu can still do it and quite well at that.

If you're going to be beginning development, then I'd suggest you learn:

• gcc et al - specifically gcc, gdb & make
• some editor - nano is easier, vim is more useful
• tmux - simply better than screen and pretty easy with the right .tmux.conf
• bash - 'cause...duh

Speaking as a developer, there are a few 'configurations' that I personally consider an absolute requirement.  Of course, please keep in mind that I have my own specific reasons & purposes and they may not match yours(or anyone else's, for that matter).  Also, I've been doing this a while so this might get a little 'heavy' if you're brand-new to Linux.

The way that you organize your $HOME directory is key to developmental survival.  If it's unorganized, so it will be with your mentality and ultimately the outcome of your code.  A decent structure is extremely helpful for getting started off right.  I organize mine as such:

Code: (bash) [Select]

$ mkdir -vp -- bak bin conf/build lib/{books,plugins,docs/rfcs,vpn/{certs,keys,sec/mnt}} per/{gaming,music,pics,screens} proj/{code/{ada,asm,c,c--,c++,d,delphi,erlang,forth,fortran,golang,haskell,hla,java,lisp,lua,molotov,objc,pascal,perl,php,python,rpg,ruby,scala,shell,tcl,verilog,vhdl,web},craft,hardware,misc} srv tmp work/{contracts,favors,fun,students}

Which creates a directory structure as:

Code: (bash) [Select]

$ tree -F .
.
|-- bak/
|-- bin/
|-- conf/
|   `-- build/
|-- lib/
|   |-- books/
|   |-- docs/
|   |   `-- rfcs/
|   |-- plugins/
|   `-- vpn/
|       |-- certs/
|       |-- keys/
|       `-- sec/
|           `-- mnt/
|-- per/
|   |-- gaming/
|   |-- music/
|   |-- pics/
|   `-- screens/
|-- proj/
|   |-- code/
|   |   |-- ada/
|   |   |-- asm/
|   |   |-- c/
|   |   |-- c--/
|   |   |-- c++/
|   |   |-- d/
|   |   |-- delphi/
|   |   |-- erlang/
|   |   |-- forth/
|   |   |-- fortran/
|   |   |-- golang/
|   |   |-- haskell/
|   |   |-- hla/
|   |   |-- java/
|   |   |-- lisp/
|   |   |-- lua/
|   |   |-- molotov/ # created by a friend; the point of the lang is essentially that it's a memory map of a process w/ some macro magic; it can all go horribly wrong with the slightest mistake...hence the name
|   |   |-- objc/
|   |   |-- pascal/
|   |   |-- perl/
|   |   |-- php/
|   |   |-- python/
|   |   |-- rpg/
|   |   |-- ruby/
|   |   |-- scala/
|   |   |-- shell/
|   |   |-- tcl/
|   |   |-- verilog/
|   |   |-- vhdl/
|   |   `-- web/
|   |-- craft/
|   |-- hardware/
|   `-- misc/
|-- srv/
|-- tmp/
`-- work/
    |-- contracts/
    |-- favors/
    |-- fun/
    `-- students/

Specific configuration files of importance(to me) are as follows.
NOTE: I'm not going to give out every script I have; it'd be a waste of space on the forum.  However, if there is something specific that you're interested in, let me know and I can post & comment on it.

• .alias
• .bash-completion
• .bash_logout
• .bash_profile
• .bashrc
• .cvsrc
• .dir_colors
• .env
• .gdbinit
• .gitconfig
• .indent.pro
• .inputrc
• .nanorc
• .path
• .profile
• .prompt
• .screenrc
• .ssh/config
• .subversion/config
• .svnrc
• .tmux.conf
• .toprc
• .vimrc
• .Xauthority
• .Xresources
• .Xdefaults

Some CLI tools:

• Intel compiler & debugging suite - I prefer using this compiler for personal projects or tools that I create myself.  It's free for Linux but you should be aware of the mess that you're getting yourself into if you decide to take it for a spin.
• gcc, g++, gdb, automake, autoconf, etc. - GNU build & debug tools + important supporting libs/tools
• tmux, screen - terminal multiplexers
• tree, most, less, bc, dc, etc. - a few basic things I hate going without
• curl, wget, aria2c, axel - various download tools
• telnet(with SSL), netcat, stunnel, etc. - connection tools/protocol manglers
• nano, vim, emacs - various editors
• tar, bzip2, 7z, arj, zip, gzip, rar, etc. - various archive handling tools
• host, dig, nslookup, etc. - various DNS tools
• nmap, tcpdump, tcprelay, pcap, fping, hping, etc. - various network diagnostic tools
• inxi, top, htop - some system information tools

Some GUI tools:

• XFCE - my preferred DE if I'm going to be in X for a while
• codeblocks, anjuta, eclipse, geany, qt creator, scite, sublime text 2 - various IDEs & code editors(Daemon introduced me to sublime)
• ddd, nemiver, diffuse, meld, edb, ida pro - various debuggers
• dia, wireframesketcher studio, gimp - graphical tools for diagramming & such(I use gimp primarily for scanning in diagrams & editing them)
• deluge, transmission, filezilla, steadyflow - download utilities
• firefox, chromium, dillo, epiphany, links2, netsurf - browsers
• xchat, skype, pidgin - communications
• freemind, freeplane, notes(xfce4-notes) - idea logging
• libreoffice, abiword, gnumeric - office stuffs
• wine, virtualbox, vmware, bochs, qemu, dosbox - virtualization
• gparted, baobab, unetbootin - disk management(6 TBs of stuff, at least 25% of which is development-related is a lot to manage)
• urxvt - terminal emulator of choice

This is part of my setup.  This is only my opinion(though it's the 'right' one ;-P). YMMV.

[kenjoe41]

Phew! Nice one Xires. I've been using linux for sometime now but i guess i still have some more to learn here. Asante!!

Afew videos for some basic networking, Vm, etla...on linux. Just give them a second.
http://evilzone.org/video-tutorials/some-good-linux-commands-for-beginners-videos/msg61577/#msg61577

[wookie]

Thanks for your contribution, but what about some configurations to do, and packages or programs to install or download, as a developer in general.

All you need is VIM.. dum da dum dum... All you need is VIM.. VIM.. VIM is all you need...