Switching careers, need Linux experience

[next-Jin]

I'm in the Army and I want to switch my MOS from 25N Nodal Network Systems Operator-Maintainer to a 25D Cyber Network Defender.

Basically with my current job I manage and install networks as small as a Company sized element all the way to Division level. I have my A+ and Net+ but this particular MOS requires at least Sec+ to submit a packet (GSEC all the way up to CISSP are also fine, but well beyond Sec+).

I am already working on my Sec+ but my main concern is Linux and Python coding. I have the CBT Nuggets for both along with the All-In-One books by Darrill Gibson and others.

With Linux I will be working with Kali (basically BackTrack 6). I installed it on a spare laptop and tried working with it but it was above my level. I am very experienced in Windows and OSX but Linux seems like another animal. Command Line is huge and I don't know where to begin.

I have tried;

• Kali
• OpenSUSE
• Ubuntu
• Mint
• Pear Linux
• Elementary

At the moment I am on Elementary and it looks great, but I am still lost.

What are the best websites to teach Linux, not just to get around but actually dive into it? I ordered the Linux Bible and the Linux+ books already but it will take awhile before they get to Korea.

I want to eventually settle on Kali because it has every PENtesting software I could ever train with already installed.

 

[icemoth]

From my own experience, I was able to understand Linux a lot better by running Arch.

I mucked around with Ubuntu, openSUSE, Fedora and the like for years, but it wasn't until I started using Arch that I discovered how everything fits together and works on a Linux system. By forcing you to essentially build your own system from virtually scratch, it allows you to understand what's going on to make your system work.

It doesn't seem very friendly at first, but if you closely follow the Wiki tutorial on how to install Arch and make it usable, you'll be fine. The beginner's guide on the Wiki is excellent. If you get stuck at any point, the forums are very active over there for you to ask away.

There's also Gentoo if Arch isn't to your liking. I haven't had much experience with it, but it's pretty hands on too and also has a very active community.


Whilst they are all Linux and bear the Linux kernel, I guess one of the main differences between the major distributions is their package management systems - each of varying flexibility and complexity.

For example Ubuntu/Debian uses apt, openSUSE uses YaST (ZYpp), Gentoo uses Portage and Arch uses Pacman to name a few.


Online resources are usually your best bet for learning about Linux. While the books may be good for teaching about Linux concepts and such, when it comes to specifics you might find them a little out of date. That's just the nature of the Linux project - it's an ever changing beast. Here's some initial pointers for you:

The Linux.com tutorials section might be a good place to find resources.

Linux.org usually has some pretty interesting stuff.

Phoronix is a good place to find Linux related news.

The Ubuntu Forums are a great place for newcomers and experienced users alike to ask questions.

If you're into subscribing to magazines, you should check out the British based Linux Magazine. I've always enjoyed their articles when I've had my hands on one.

Oh, and yes, learning commands is very useful for administering a Linux system. Here's a cheat sheet to get you started.
​

Anyway, this is just a small selection of what's really out there. If you have a bit of a search around you'll find that it really is endless amount of resources.

 

[4saken]

Work with AWS and spin up free t1.micro instances. You can mess with amazons linux distro which is RHE based, and also spin up Ubuntu 12.04 LTS instances. You will probably learn quite a bit quick since its console only access and you would be forced to deal with ssh keys right off. Messing with *NIX desktop is pretty worthless IMO for learning linux. It just allows you to sidestep learning the console for some pretty basic fundamentals you would otherwise learn quickly going all CLI.

Plus there are lots of tutorials for spinning up lamp stacks/etc/etc/ect well written for AWS already. On top of the other resources you and previous poster have put.

I think Distros are less important to focus on and i'd rather be learning package management along with deploying and managing apache2/mysql/etc on systems. It would also be a good opportunity to pick up some ruby/json/scripting if you decided to work with Chef/Vagrant/etc for deploying systems, which today is one of the most sought after skill sets with changes in the IT environment to be more CI intensive with hybrid 'clouds'.

 

[jwcalla]

I think the best method is to just open up a terminal and start trying to do everything you want to do through it. You're not going to know how to do it at first, so you'll use Google to find those answers. Take notes along the way if you have to. Then it'll start to stick.

Right now probably the best reference would be one that explains all the shortcuts and stuff for the shell you'll be using, like bash or csh or whatever. This will help you manipulate the commands easily and you won't get frustrated re-typing everything.


As it is now, I'm completely lost without a command line. When I go over to Windows and have to do any kind of configuration or whatever, I get cold feet and sweaty hands and start stammering like Ralph Kramden.

 

[next-Jin]

One thing I am having the most issue with is installing software. I know the commands are different depending on what you are using, however most the guides I have been reading are saying to get this repository, update install this package.

How do I supposed to know this without having to research for 20 minutes for every single program? Is there a standard or concept that I am overlooking currently?

They appear to all be different repositories for each piece of software.

EDIT: I figured it out, each distro has their own unique repository. Some programs have to use their own or another unofficial one.

 

[Ruoh]

One thing I am having the most issue with is installing software. I know the commands are different depending on what you are using, however most the guides I have been reading are saying to get this repository, update install this package.

How do I supposed to know this without having to research for 20 minutes for every single program? Is there a standard or concept that I am overlooking currently?

They appear to all be different repositories for each piece of software.

Generally you can add more than one repo, and tell your updater (yum, apt-get etc) to update all the packages at once.

 

[next-Jin]

Generally you can add more than one repo, and tell your updater (yum, apt-get etc) to update all the packages at once.

Yea I think I'm going to do what the first responder mentioned and use arch first, I have been hearing really good things about pacman (even though I don't know what the pros actually are lol)

 

[Ruoh]

Arch is pretty good. It's bleeding edge, so you'll want to keep an eye on the forums. From time to time there were issues with an update here and there, but nothing drastic. Be patient and follow the instructions, even the ones you glance over thinking they don't apply.