Top products from r/linux4noobs

We found 88 product mentions on r/linux4noobs. We ranked the 222 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/linux4noobs:

u/two-gun · 29 pointsr/linux4noobs

Sorry for getting all dramatic, but for me you're asking a red pill/blue pill question. I applaud your curiosity and can only recommend you follow your gut and take the red pill. The truth is by asking the question you already know what to do next. Just keep going. However I'll give you a few ideas because you got me excited.

  1. Get in touch with your osx terminal
  2. Get linux ASAP
  3. Learn the command line

    OSX Terminal

    Underneath the shiny GUI surface of your mac you have an incredible unix style OS just waiting to be played with and mastered. A few tips to get you going.

    Download iTerm 2. Press cmd-return, cmd-d and command-shift-d.

    Congrats. you now have a hollywood hacker style computer

    Copy and paste this line into your terminal and say yes to xcode.

    ruby -e "$(curl -fsSL"

    Awesome you now have homebrew. A linux style package manager.

    May as well get cask too.

    brew install caskroom/cask/brew-cask

    Now you can install programs by typing a couple of words.


    brew cask install virtualbox

    Get Linux ASAP

    Linux is relatively easy to get up and running and awesome fun. try any of these options

  • Download virtual box and install a 'virtual machine' to run linux on your mac (see above).
  • Buy a Raspberry Pi.
  • Create a bootable usb and install refind on your mac.
  • Take a friends old laptop and install linux on it from your live usb distro.

    If any of the above seems slightly daunting don't sweat it. Be confident and you may just surprise yourself at how much you can learn in such a short amount of time.

    Learn the command line

    The command line opens up the wonderfully powerful and creative world of unix. Push on.

  • Get the basics down with codecademy
  • Play with some books (this or this for eg)
  • Watch some youtube videos (this guy's good for webdev)
  • Learn a text editor (Try Vim. You already have it. Type 'vimtutor' in your terminal to get started)

    Play, Play, Play

    Do what gets you excited.

    I got a big kick out of learning ssh and then pranking my friends with commands like

    say hello friend, i am your computer. i think your friend two-gun is very handsome. Is he single?


    open -a "Google Chrome"

    Do what you find fun. Oh and check out Richard Stallman. He's a good egg.



    forgot iTerm link


    Wow! Gold! Ha! Thank you. This is so unexpected! I'd like to thank the academy, my agent, my mom...

u/[deleted] · 1 pointr/linux4noobs

Systems (Linux) engineer here.

All of your programs are supported on Linux, so no fear :)

You will need to use a cmd.exe like interface called a terminal and it is infinitely more powerful than cmd.exe (not including powershell).

If you want to get better with bash read this book, but more importantly, if you want to do anything in the system, do as much as possible via commandline, instead of the GUI

I would HIGHLY recommend getting a Lenovo laptop. They are one of the few manufacturers that officially support Linux on their machines and they work really nice, if you have the cash, the X1 carbon is nice.

Honestly the learning curve is different for each individual. You will not be an expert in one month, but you should be familiar enough with it to use it. Remember: Google ALL the things. Seriously, linux has a fantastic community. Stack Overflow,, etc. are some great resources to check out.

u/textandmetal · 76 pointsr/linux4noobs

I love learrning linux! I love the community! You aren't following a trail of breadcrumbs, you are racing down a superhighway of information. Google/duckduckgo is now you best friend, it pays to learn how to work with them.


The linux command line

The Linux Bible

UNIX and Linux System Administration Handbook


Where to ask questions and find information:


How to ask questions for maximum help:



Linux Journey

This dude called Ryan is pretty cool

This guy Dave has a really nice voice on youtube

Linux Foundation




Linux learning games:




Subreddits you might want to get into at some stage, or subscribe to, I just made a big multireddit that I use when I want to focus my redditing on positive use of my time:

u/doss_ · 7 pointsr/linux4noobs

the easiest way is to strictly identify which part is really the variable:


cp $foofile testdir/. # cp: missing destination file operand after 'testdir/.' ($foofile doesn't exist and expanded to null, not enough required params for cp)

cp "$foofile" testdir/. # cp: cannot stat '': No such file or directory ($foofile still doesn't exist, but expanded to '' due to double quotes usage - good practice)

cp ${foo}file testdir/. # will compy 'testfile' if exists

Also it is usefull to access command line params from inside the script if there are more than 9 params, to access 10th param use ${10}

and here is some list i noticed for myself of how to use this braces, while reading this book - would recommend:

Sorry for formating issues, reddit treats spaces and new lines in special way..

variable substitution:

Bash supports various variables substitutions:

$a - will be substituted with 'a' value

${a} - same as $a but could be concatenated w/ string w/o spaces:

${a}.txt - will be expanded in a_value.txt

${11} - 11th positional parameter given to script from shell

${var:-word} - if 'variable' is set, the result will be its value

if 'variable' is unset - the result will be 'word'

$(var:=word} - if variable is set results in its value substituted

if variable is unset, it will be assigned to 'word'

such assignment will not work for positinal params(see 'shift')

and other special variables

${var:?word} - if variable is unset error with reason 'word' will be

generated, exit code of such construct will be 1

${var:+word} - if 'variable' is set, the result will be 'word',

(but variable's value will not be changed)

otherwise result will be EMPTY string


$ echo ${variable:-ls} - variable unset - ls used

> ls

$ export variable=1

$ echo ${variable:-ls} - variable is set- its value used

> 1

$ echo ${variable:+ls} - variable is set - ls used

> ls

$ echo ${variable1:+ls} - variable unset - empty line used


${!prefix} or ${[email protected]} - returns NAMES of existing variables

that starts from 'prefix.


$ echo ${!BASH


string variables substitution:

${#var} - returns length of string in variable's value


$ var=123456789 #this could be interpreted as a string too now

> 9 #string length is 9

${#} or $# or ${#@} or ${#} - returns number of positional parameters

of the script being executed

${var:number} - return string from number to the end, spaces trimmed

variable is unchanged.


$ var="This string is to long."

$ echo ${var:5} #returns string from 5th symbol

> string is to long.

Example: spaces are trimmed:

$ echo ${var:5} | wc -c #count chars

$ 19

$ echo ${var:4} | wc -c #return starts from space

$ 19 #space is trimmed so same number of chars

${var: -number} - return string from end to number, spaces trimmed

NOTE - space between ':' and '-' signs


$ echo ${var: -5}

> long.

${var:number:length} - return string from number till end of lenth


$ echo ${var:5:6}

> string

${var: -number: -length} - return string number between number(from the

end) and length (also from the end)

NOTE: number must be > than length


$ echo ${var: -18: -2} #var is This string is to long.

> string is to lon

${@} - return all values of positional params

leaving spaces inside strings (like "[email protected]" ) - bcs it know how

many arguments script has

} is the same form, it seems

${@:num} - displays values of positional params but from num

$(@:1) - works same as ${@}

${@: -2} works , but starts from the end

${@:num:length} - same as with strings but with positional params

${@: -num: -length} - same as with strings but with positional params

${param#pattern} - finds shortest match and deletes it (lazy match)





${param##pattern} - finds longest match and deletes it (greedy match)




${param%pattern} - same as # but deletes from the end of the file



${foo%.} - note . instead of . in # example


${param%%pattern} - same as ##



Search and replace:

${param/pattern/string} - replaces first occurance of pattern with string

${param//pattern/string} - replaces all occurances of pattern with string

${param/#pattern/string} - replaces only if at the beginning of the line

${param/%pattern/string} - replacesonly if at the end of the line

u/z-oid · 2 pointsr/linux4noobs

Not exactly what you want to hear, but the best way to learn the shell is by doing. Reading can give you a good base knowledge, but application is key.

This is by far the best way I've found to learn Linux quickly. Install Linux onto a extra computer, dual boot, or pick up a raspberry pi. Try things out, when you can't figure something out look it up. If you still can't find the answer head over to #linux on freenode. (Or Distro specific channels like #fedora #ubuntu etc.)

HOWEVER! I DO have a phenomenal book suggestion for you.

u/mvm92 · 1 pointr/linux4noobs

Linux From Scratch is a little head first, trial by fire, but if you are willing to spend a lot of time getting your system to work, it could be cool. Another distribution to think about is Arch Linux and Gentoo. No matter which distribution you chose to learn on, read through all of the installation instructions, as these will explain why the defaults are as such. Don't just keep hitting enter, you have to read.

In addition, pick up a good Bash reference, like this one or this one (O'Rielly makes good books for this kind of stuff) and learn some Bash as the Bash shell is one of the most powerful aspects of linux.

Another thing that you may want to try is setting up a LAMP stack without following a step by step guide. LAMP meaning Linux, Apache, MySQL, PHP. This is a common configuration for a Linux webserver.

Finally, once you have gotten comfortable with Arch or Gentoo, mix it up. Try debian, or fedora. See and learn how every distribution does things in a slightly different way. Keep trying new things, you will never be done learning.

u/shittyanimalfacts · 3 pointsr/linux4noobs

Try out some of these:


The linux command line

The Linux Bible

UNIX and Linux System Administration Handbook


Where to ask questions and find information:


How to ask questions for maximum help:



Linux Journey

This dude called Ryan is pretty cool

This guy Dave has a really nice voice on youtube

Linux Foundation



Engineer Man. thank you to u/dk1998 for the reminder

Bash Guide by Greg Wooledge


Linux learning games:




Subreddits you might want to get into at some stage, or subscribe to, I just made a big multireddit that I use when I want to focus my redditing on positive use of my time:

u/Slinkwyde · 2 pointsr/linux4noobs

Here's one I have that has always worked in any Linux machine I've tried it in.

The downside is it only supports 2.4GHz, so interference could be a problem if you're in an apartment or other place with lots of WiFi congestion. Also, it's 802.11n (previous gen) instead of 802.11ac (current gen) so it's theoretically slower, but it might still be faster than your Internet connection and should be fast enough for use in a crypto mining rig (as opposed to say, a box for streaming 4K video).

Again, the benefit of that adapter is that it works in Ubuntu (including 16.04) out of the box with absolutely no setup or drivers/firmware required. You just just plug it in, pick your network, put in the password, and you're done.

For dual-band (2.4GHz/5GHz) and 802.11ac that similarly works out of the box in Ubuntu, my Intel 8260 has been great, but that's a mini-PCIe card rather than USB.

There may well be other, better options than these, but I'm just giving you the ones I have personal experience with. The key factor in Linux compatibility for Wi-Fi adapters is the chipset it uses. The same chipset can be used in a wide variety of Wi-Fi adapters from different brands. If given adapter supports Linux out of the box, then any other adapter using the same chipset will also work out of the box.

u/Your_Left_Hand · 2 pointsr/linux4noobs

If you are willing to spend a little money, I'd suggest the Linux Command Line and Shell Scripting Bible. It will first teach you about the commands you can use on the CLI. Then it will delve into shell scripting. After finishing that book up you should have a very decent understanding of bash.

Another good tutorial that I can Recommend is The Linux Command Line. There are free lessons on the website that cover the same material as his book does. The book is just a lot more in depth.

Also, after you gain some familiarity you can try reading through the bash man page. It's a heavy read, but you can definitely learn a lot from it.

Good luck!

u/confusador · 2 pointsr/linux4noobs

I can recommend Jang's RHCE study guide as a good comprehensive introduction to RHEL, and it does a good job of going through the details of the installation process so you can be sure you didn't miss anything. Also check your support contract! You may be paying RH to help with this kind of thing.

u/createthiscom · 1 pointr/linux4noobs

I'm not sure what you're having trouble with. You talk about networks and firewalls, LAMP setup, disk encryption, backups, etc.

I get the feeling this is an emotional outburst type post, and that's fine, but I'm not good at emotional support. You'll need to ask a specific question to receive a helpful answer.

You can literally google for any problem these days and have a high rate of success. However, if you're looking for a ground up explanation of *nix along with some history for perspective, I recommend the UNIX and Linux System Administrator's handbook:

It was the one book that helped me understand where all of this stuff came from when I got started.

However, for specific issues (bacula, for example), you'll do better asking specific questions.

u/tdk2fe · 6 pointsr/linux4noobs

Get the Unix and Linux Administration Handbook, 4th Edition, by Evi Nemeth, Garth Snyder, Trent Hein and Ben Whaley.

This book covers both Ubuntu and other Linux flavors, along with traditional Unix. It is my defacto go-to when I need to look up a topic, and goes into incredible detail about not only how to do things, but also some of the theory behind them. A good example is that it explains how to set up a DNS server, but also details how DNS actually works.

For something cheaper - just google the Rute Manual. This also details a wide array of OS concepts and how they are embodied in Linux.

And while your learning - i'd like to throw this tidbit that I absolutely love from the Rute guide:

>Any system reference will require you to read it at least three times before you get a reasonable picture of what to do. If you need to read it more than three times, then there is probably some other information that you really should be reading first. If you are reading a document only once, then you are being too impatient with yourself.

>It is important to identify the exact terms that you fail to understand in a document. Always try to backtrack to the precise word before you continue.

>Its also probably not a good idea to learn new things according to deadlines. Your UNIX knowledge should evolve by grace and fascination, rather than pressure

u/ixipaulixi · 1 pointr/linux4noobs

The Linux Documentation Project is a great free resource:

A Practical Guide to Linux Commands, Editors, and Shell Programming (4th Edition)

The first two are for learning Bash; this is an awesome resource for learning how to administer RHEL/CentOS7:

RHCSA/RHCE Red Hat Linux Certification Study Guide, Seventh Edition (Exams EX200 & EX300)

u/Nezteb · 4 pointsr/linux4noobs

Some info on distro differences:

u/mantrout · 1 pointr/linux4noobs

Online tutorials can answer any questions you might ever have, but when learning something new I like the condensed nature of a well written book on a subject. For shells, I thought this book was excellent, and still reference it from time to time:

also.... ZSH FOR LIFE!

u/HanoverWilliam · 0 pointsr/linux4noobs

Typically if your USB wireless adapter functions and your network sucks... It's not a safe bet to assume correlation causation with drivers and updates. It's typically your home network.

Consider looking into Ubiquiti's line of UNIFI products. Or you can find your own brand you may prefer which sell "Access Points". Then I would wire all access points to a central area.

You haven't told us how large your house may be or what physical barriers you may have..

If you really believe it's your USB wireless hardware that may be the source of the issue, I would heavily recommend something like this ALFA NETWORKS RT2800 USB Iteration.It should be natively supported across most distributions.

Good luck. Reply if you have any questions.

u/cstoner · 1 pointr/linux4noobs

First thing first, there is nothing you can do with Linux that you couldn't do with Windows or a Mac. And similarly they can be made to do everything that Linux can. It's just a matter of how you go about getting those things done.

Learning sysadmin stuff will help with dev work (in my opinion as a former Linux sysadmin and current Java/Linux dev), but I'd bet you probably won't end up caring about setting up sendmail, bind, nfs, etc. which is a good chunk of the content of that book. I'd leaf through it and see if any of it seems interesting, but it'd probably make sense to return it.

If you're just looking to try to understand what linux is all about, it's tough to go wrong with

It's free, but if you prefer dead tree versions like I do, you can buy it in a variety of places. Here it is on Amazon:

A lot of the command line stuff builds on itself, so don't feel bad if it doesn't make sense at first. Once you get comfortable with the shell, you can start dabbling in whatever else tickles your fancy.

u/remimms · 4 pointsr/linux4noobs

I found the book The Linux Command Line to be very useful. Good luck on your CEH!

u/youfuckedupdude · 1 pointr/linux4noobs


I would say if you just want to learn the basics of Linux the best way of doing it is using the free resources. When you find an area that interests you, thats when you dish out for the specific textbooks.

There is no shame in googling something while you're on-site or at the office. I fucking encourage it.

u/GobTotem · 5 pointsr/linux4noobs

I am a beginner too and just finished this book TLCL.Another one i would recommend is shell scripting bible.For most part use google to learn about commands and man page is your friend. I am more of a book kind of guy so never used video resources. Most important you should know where to look for help when stuck.

u/chadillac83 · 3 pointsr/linux4noobs

Pretty good, goes from basics to full system administration pretty quickly, and explains it simply... if you want more in depth detail it provides reference sources and suggested reading. I've been using Linux as my primary OS for a couple years now and still am picking up new little bits and pieces of knowledge that I'd either forgotten or just didn't know about. It also covers some simple stuff that you can read up on on the net, but you have to know to look for it, this at least introduces you to those ideas/terms/etc.

TL;DR I like this book.

u/beepbupe · 8 pointsr/linux4noobs

2nd this.

The Linux Command Line. Author offers free PDF for download or you can support and buy from amazon.

u/rowboat__cop · 3 pointsr/linux4noobs

Considering that the best book about Linux, Kerrisk’s The Linux Programming
was published in
2010, the answer is a determined yes. Just make sure to read a good
book. Most of the knowledge, even if technically obsolete by now, should be
transferable in a way to the state of the art.

u/chillysurfer · 4 pointsr/linux4noobs

For that purpose I can highly recommend the book How Linux Works. I thoroughly enjoyed it and it'll give you plenty of info.

Just to stack hands and echo what was said before, reading about will keep it in your brain for a day. Doing it keeps it there forever though.

u/systemd-plus-Linux · 9 pointsr/linux4noobs

”How Linux Works” is one of the better in depth explanations of Linux I've read.

It's written in a way that anyone can read and understand it, but it gets pretty deep into Linux under the hood.

u/Lokus_ZAsrithe · 5 pointsr/linux4noobs

That is probably some of the craziest shit I've read in a while, and that's impressive, this being the internet and all.

EDIT: OP, to make a suggestion, the Linux Bible is a great resource for someone just starting out, and helps get you in the mindset of how Linux works when coming from other operating systems.

u/underpaid-sysadmin · 8 pointsr/linux4noobs

Go get Mike Jang's book on RHCSA/RHCE - If you can do everything listed in the first 9 chapters of that book without much thought, you will pass most entry level interviews.

Once you have basics, script everything you can in bash. Once you've done that, go learn ansible or puppet or chef. Turn all your scripts into runbooks. Once you've done that, recode it all to Python.

More advanced stuff: Learn AWS and an infrastructure as code tool like Terraform or K-Ops. Docker/K8s are also highly desired once you've got the above mastered.

Source: I screen candidates for my current department and will hire you for T1 if you have the basics listed above. T2 and T3 people need to know more code. My SREs need to know pure CI/CD and infra as code with containers.

u/TsuDoughNym · 1 pointr/linux4noobs

I use the Edimax Wireless N adapter if I need one with guaranteed Linux support -- can confirm it's worked without issue on at least 5 different physical systems, varying between Linux and Windows.

I also have a ZyDas ZD1211 adapter that we used in my networking class for packet injection/wireless sniffing, so that's also got good compatibility.

u/fromagi · 6 pointsr/linux4noobs

How Linux Works was suggested on another thread. I picked it up, and while I am only on chapter 2, it seems like a good primer.

u/2o2o472o64o6 · 2 pointsr/linux4noobs


I bought it as a means of looking things up for those brain fart moments, it’s a good resource, but I wouldn’t recommend trying to read the whole thing in one hit as it’s a lot of information to take in.

u/orispy · 7 pointsr/linux4noobs

This is the best book. Sets a firm foundation that you get nowhere else.

How Linux Works, 2nd Edition: What Every Superuser Should Know

u/MIH-Dave · 3 pointsr/linux4noobs

Yes, there are multiple USB WiFi adapters that will work with Linux. I just received a EDIMAX AC600 for a small work project that came with the Linux drivers on CD.

A co-worker also purchased an [Alpha Long-Range AC1200] ( and has it working with Kali.

By no means is this an extensive list, but just a couple that I've seen success with in the past few days alone.

u/wuts_interweb · 1 pointr/linux4noobs

For cash-in-pocket noobs who like to have a book in hand I'd recommend any of these books by Mark G. Sobell.

A Practical Guide to Linux
Old (1997) but takes you from the basics to intermediate.

A Practical Guide to Linux Commands, Editors, and Shell Programming, 4th. Ed.
Also covers the basics but it's more focused on those subjects included in the title.

A Practical Guide to Ubuntu Linux, 4th. Ed
I have no experience with this book but I'm including it for completeness.

A Practical Guide to Fedora and Red Hat Enterprise Linux, 7th. Ed.
Same. No experience.

u/HyperKiwi · 1 pointr/linux4noobs

OP Linux Command Line book, is an excellent place to start.

u/LeaveTheMatrix · 1 pointr/linux4noobs

Some people will say put both OS on the same SSD, however if something ever happens to that SSD then you have a completely unbootable system. Due to that, I often recommend a separate disk for each OS.

If you go through old posts you will see that many people who try to do Windows/Linux dual boot have had issues with trying to use Grub as the boot loader and this is why [I usually link people here]( which is the basic setup for individual drives on each OS and using the Windows boot loader.

EDIT: These directions are the same that I use for every dual boot setup I do, and currently running 3 Windows installs (2xWin10, 1xWin7), 1 Ubuntu, and a "shared" data drive. Have done so many setups like this for many people and haven't seen any problems crop up.

In your particular case, if you do not want each drive to see each other then you may want to use a HDD switcher similar to this , unfortunately I couldn't locate one specific to SSD.

u/archebus · 2 pointsr/linux4noobs

I am following a similar path to you at the moment. Here was my general plan after doing some reading on Linux:

  1. Download latest Ubuntu release and boot up a live CD. Ensure I can connect to the internet.
  2. Backup data. Install Ubuntu with default settings and migrate my data. (adaptation period)
  3. Complete the code-academy "Learn the command line" course here.
  4. Purchase the Linux Bible 9th Edition and work through the entire book.
  5. Replace Ubuntu with Arch Linux.
  6. Touch up on specifics of RHCSA and register for the course.
  7. Ace the RHCSA and start applying to entry level Linux admin jobs.

    I am currently on step 4 and am up to Chapter 7 of the Bible. The reason for my change is because I have just moved to a city where Linux admin is in high demand and pays well.
u/jjanel · 1 pointr/linux4noobs

TL;dr sorry. +1 chillysurfer: "How Linux Works" 2nd ed. (yes, ok for a HiIQ_n00b)

Please @JAU, let me know what you think of it (via Amazon 'Look Inside' or AllITeBooks etc)

u/phabeon · 4 pointsr/linux4noobs

Just get these 2 books(all you'll need, peep the reviews for proof) and thank me later

Linux Command Line

How Linux Works

u/JasonZX12R · 3 pointsr/linux4noobs

I have been a Unix admin for 5+ years and I am always finding cool tricks with commands I have been using for years. Or built in shell commands even, such as:

Is one of the books I have been going back over.

u/moderatorsaretoxic · 0 pointsr/linux4noobs
  1. Learn linux -,204,203,200_QL40_&dpSrc=srch

  2. Learn your distro - IE find a good book on debian, ubuntu, fedora, or the arch wiki

  3. Interact with their forums

  4. Remember that no one knows everything; but most people will expect that you at least do a google search to find more information about your poblem.
u/DefinitelyNotInsane · 2 pointsr/linux4noobs

You can even buy a SATA switch to power only the drive(s) you want to use.

u/Linuxllc · 1 pointr/linux4noobs

So does your wifi work on other Linux distro's?

If so then your wifi will work in any Linux distro. You just have to use the exact package/libraries and drivers of the Linux distro that your wifi work in.

Give me your wifi info and I can find the right drivers for you to use in Ubuntu.

And if your wifi isn't working right in any Linux distro. Then just use a USB nano wifi adaptor that works in Linux.

u/doc_willis · 4 pointsr/linux4noobs

seen this one recommended. but not tried it personally, and it's not a tiny dongle.

Alfa Long-Range Dual-Band AC1200 Wireless USB 3.0 Wi-Fi Adapter w/2x 5dBi External Antennas – 2.4GHz 300Mbps/5GHz 867Mbps – 802.11ac & A, B, G, N

u/poply · 2 pointsr/linux4noobs

I hear this is great UNIX and Linux System Administration Handbook

Although I can't personally vouch for it.

u/l0go5 · 3 pointsr/linux4noobs

Understanding the Linux Kernel, Third Edition Writing my own kernel this semester for a class, this is the course textbook and has been an invaluable reference!

u/mv46 · 3 pointsr/linux4noobs

Most books are still made out of paper.

Try these : UTLK
and Linux Programming Interface

u/takehomemedrunkim · 2 pointsr/linux4noobs

I've done the same setup on my desktop. I bought this Kingwin HDD Power Switch Module 6 Switches for 5.25-Inch Bay (HDD-PS6) from Amazon. Inside my desktop I mapped the toggle buttons to my different hardrives. The sata cables remain connected at all times. Your motherboard may give a warning on every boot that a sata device is missing, in my case it doesn't.

I did this mainly so me playing on Linux didn't mess up my personal files in Windows but now a days it's more so that Windows doesn't mess up Ubuntu.

u/Avaholic92 · 1 pointr/linux4noobs

Unix and Linux System Administration Handbook is always on my desk


I would go through LinuxAcademy’s course on How to Get a Linux Job.

The down side is you’re probably not going to be a sysadmin out of the gate unless you already hold an IT job. SysAdmins usually warrant 3+ years of experience in the field in various other positions.

I started as a repair tech and have worked my way up to sysadmin status.

My day to day consists of email management to dns and everything in between. I work for a web host so my daily tasks may differ from an environment you may potentially work in.

It boils down to,

What is your skill set ?
How much experience do you have?
Can you handle yourself with minimal to no handholding depending on the environment? I say minimal here because some environments I’ve seen are heavily customized and you have to reverse engineer things to figure out how it all works together.