Compare cert salaries and plan your next career move
knwminus wrote: » Well I plan to move my main laptop over to ubuntu. I am also plan to move 1 of my server boxes to linux as well. Why? Because I want to be a Linux engineer and a wise man once told me " If you want to be a good Linux engineer, use it." I do plan to keep 1 windows machine on my network so I can set up samba. My laptop should be finished before the end of the weekend and my server should be done by next week. This should be something fun to do (besides CCNA studying). Anyone have any advice on best practices?
Solaris_UNIX wrote: » Congratulations on getting ready to take those brave, daring and dangerous first steps to format over everything on those two machines with Linux. In spite the bad economy there is still a big shortage of qualified Linux and UNIX techs and admins out there in the world right now. Some of President Obama's new CIO / CTO appointees are huge FOSS (free open source software) advocates (I think the new guy Obama is putting in charge of I.T. for the DoD is a huge FOSS advocate who participates in the LKML) so it's safe to conclude that open source software is only going to be gaining more ground from here on out in both the government sector and the private sector, which means more job opportunities for people who are familiar with FOSS technologies like Linux, Apache, Mysql, BASH shell scripting, Postfix / Dovecot, Perl, gcc, Python, etc. Even with no certifications, you can actually still make good money in the Linux business provided that you actually know what you are doing and have a lot of experience and a well proven track record of delivering results on time and under budget. The advice I'll give you depends on the hardware specs on your laptop and your server. When you boot up your laptop into an Ubuntu live CD, "sudo su" to become root and tell me what you see as output for these commands: free -mt fdisk -l lspci | more more /proc/cpuinfo
jmanrta wrote: » Wanna get into linux, huh? Well's here a couple challenges, projects I have done in the past you mentioned samba, if you want to have some real fun try setting up samba as a PDC and having your Windows Machine authenticate against it then try to get roaming profiles to work with it. My next challenge for you is to setup an FTP server with the following stipulations: -mysql authentication -A php script for account creation and password resets -a web client running on the machine -quotas setting up the web client for ftp will give you good experience with apache. Also having you create a PHP script will give you programming/scripting experience. One thing I haven't gotten around to yet is setting up OpenLDAP and having all the services authenticate against, that's something I'll be working on in the near future. As others have pointed out try to stay away from the GUI if you can. The only time I really like using the GUI is for text editing (I don't like the CLI text editors) or if I am in a hurry. Also if you want, I'll break your system for you, and then have you try to fix it. Hope this was helpful good luck to you.
knwminus wrote: » Seems like the running theme is use the command line. I think I will focus on that.
fleck wrote: » The Linux command line is a joke to me. Has been for years. Get a Linux bible.
knwminus wrote: » hmm....(i know I may regret this later)... What do you mean it is a joke?
fleck wrote: » It's easy.
qwertyiop wrote: » I hope your kidding. The command line is where you get the most power out of your OS.
msteinhilber wrote: » I would hate to lead someone to believe that there are not complex situations that you can encounter on a Linux command line. I would agree that basic to intermediate command line skills are relatively easy after you use them a handful of times. Editing config files from the command line is childs play, even young aspiring IT professionals with the latest leet speak and other generally acceptable by teenagers Internet slang can figure it out. To become good at the command line isn't just knowing how to use some basic commands and edit config files with nano/pico, navigate the file system, remove files, change permissions/ownership, etc. Learning to use vi/vim very well, being able to use sed and awk well, regex, etc - just to name a few, are what are really going to make one effective at using the command line efficiently.
fleck wrote: » Yeah, all I'm saying is that it's not some big scary thing. Once you start using the commands and you learn your way around it's not bad. There are complex situations you can run into, but with the right knowledge/documentation you can overcome anything.
Hyper-Me wrote: » Even if you went the windows route, i would expect the same to be true in the next few years. With the quick evolution of PowerShell and installation options like Server Core (R2 supports powershell, btw), I think we will see a lot of backend server installations running nothing but a CLI.
fleck wrote: » Nah. You're talking about access servers with specialized purposes. Windows will always be mainly GUI for like 99% of things. For nix it just so happens that that's the way it's always been and it's still preferred to have shell skills for system maintenance. For Windows it's not even necessary.
msteinhilber wrote: » I hope you don't plan on ever becoming a good Windows administrator...
fleck wrote: » Why, because ipconfig and tracert are gonna break my fingers? I'm pretty sure that 'powershell mastermind' isn't a prerequisite for Windows Server admin. Is it really popular with anyone except code monkeys?
fleck wrote: » I'm a seasoned expert on the nix command line. I've made my own shell scripts for a variety of different reasons. One time I made an entire package with config files which would switch a system from dial-up to ICS configs just because I would switch my connection method almost daily in my house (my sister and I were sharing a phone line). That stuff is not really a challenge for me anymore, it was fun in high school.
Compare salaries for top cybersecurity certifications. Free download for TechExams community.
