Typical activities:
[LIST=1][*]modifying operating system configuration and maintaining server services [*]managing file systems and system resources[*]applying operating system patches – Patches OS, Package or Application[*]basic investigation of the most typical problems

Appreciate for the guideline for my new job career. Another words; tutorial for above questions.

What, exactly, is your question here?? What are you asking??? This looks like a list of generic requirements that a job listing would include.

Manage less spam ? (don't use revin.raj@gmail.com as your "user" name) is my advice.
Unless you like spam or it's disposable, or work for gmail.

You will need more than a simple tutorial for those job requirements. You can't just learn it in a day. For reference, I've been using linux as my daily driver + server @ home for 4 years now give or take. I still have a lot to learn and I only recently (as in 3-4 weeks ago) scored an entry level sys admin job. I probably could have done it faster by going to college / uni of some kind. It takes time and hands on experience. My best advice for a "tutorial" is to run linux or bsd even full time on every computer you manage in your home. Constantly try new things and read on how to accomplish them. Google can teach you but you need hands on experience, can't just get that with a basic tutorial.

3 members found this post helpful.

Thank you the tips jmgibson1981.

First, read the LQ Rules about NOT editing your posts. Secondly, both myself and habitual took the time to try to speak with you.

There is no shortcut...LEARN what you need. If you don't have those skills, then YOU ARE NOT QUALIFIED FOR THE JOB, PERIOD. You can't answer a few questions (so PLEASE do not open another thread about "give me some good interview answers"...we've had those by the hundreds here), and get the job. Even if you DO manage to talk your way into a position, what do you think is going to actually happen on day two, after you're hired? You're going to actually have to DO the job...which you don't know how to do. Know what happens then? You get fired, and this *WILL* follow you from then on, when you try to get another job.

If you don't even know what the requirements mean, you certainly aren't qualified.

1 members found this post helpful.

^This++

I just recently saw an ad in the subway in Stockholm that said:
”Become an IT-consultant in 12 weeks”
Well, the original is of course in Swedish. The whole campaign was so idiotic I actually took a picture of the advert with my phone, it can be seen here:
https://s31.postimg.org/b7zrdyfa3/IT_konsult.jpg

THIS IS BULL****!!! Nobody 'becomes' an IT-consultant (and certainly not a sysadmin) in 12 weeks, NOBODY! You become good at what you do by constantly doing it, and by not being afraid to try new things (on your own machines, mind you!), and (most important) by being interested and wanting to learn.

I am still to this day amazed by all the employers who turn people down because they don't have certificate so-and-so. Certificates mean absolutely NOTHING (which this site proves, time and time again).

Very well written jmgibson1981, my hat is off.

Best regards,
HMW

• look
• for
• the
• obvious

I'm not trying to be cute, or smart, but it really is that easy.
Knowing where to look, well, that comes with experience.

Eliminate what is working with absolute certainty.

Experience with AIX/HP-UX/Solaris.
Can't get that off the internet. Wish I had a terminal to one now.
Wonder how I'd "do"?

Nope, the education system in the USA is broken, and only cares about one thing...profit. Its ran by administrators and bureaucrats who have never worked a real job a day in their life. Teaching everything they know from the canned MS Powerpoint slides and obscure theory written in a terrible, overpriced text book.

You got it.

I've learned more about Linux in the last 2 years working as a sys admin, then I ever did in a class room. I've also learned alot coming this forum and others, reading and trying to answer questions. I have so much more to learn.

If I had to do it over again, I would have ditched undergrad/grad school and help desk jobs and start my own pc repair (this is the late 1990s/2000s) instead of working for someone's dead end help desk job and then branch out to sys admin/networking and programming.

Of course, hind site is 20/20 and luckily I lived below my means while in school and have no student debt..........

1 members found this post helpful.

Meh, it's a noob slot so, no worries. They wont let you use toilet paper until you've reviewed the relevant documentation,

modifying operating system configuration and maintaining server services <--- I don't think that's going to be you on day one.

managing file systems and system resources <--- This is more a noob gig. Read up on LVM/ZFS if your rocking Solaris.

applying operating system patches – Patches OS, Package or Application <--- Hehehehe... I don't think that's going to be you either (better hope not).

basic investigation of the most typical problems <----- They call that the googles, you're probably aware of it

other basic activities – Use own knowledge on basic our activities <--- ???? OK, that's a little frightening.

basic knowledge of UNIX operating systems (Linux or AIX) <---- Tell your putz of a boss that Linux isn't a Unix operating system, BSD is.

basic knowledge of computer networks <---- If the plug don't fit in the slot, it's probably the wrong damn hole.

experience with one of the following technologies - AIX/HP-UX/Solaris <--- Which one did you lie about in the interview?

I think after about five years of working with Linux full-time I was qualified to be a sysadmin. Of course, before that I had been working in UNIX, before web browsers or search engines. That was really chaos! But, the bottom line is: reading about how to perform a job is like finding a tutorial on how to drive a car! OR, how to take a shower, make coffee, get dressed and go to work.

You simply will not know how to do it until you try it a few times.