GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What are your qualifications ? any degrees like RHCE etc...
Have you worked on Linux before (I mean non-officially) ?
I've been a sun admin for about a year now, prior to that I worked in a data centre for around a year (mixed systems, mostly ubuntu and freebsd). I'm currently building nagios plugins for a data centre and an automated nagios build agent (both almost complete).
Things I'm new to:
The effects of running fsck on a rewritable file system (I usually say no and choose to boot off the disks).
Successfully running veritas :S.
VERY old systems which are architecture specific (sun on spark workstations).
I'm not massively experienced but I've worked with fsck before, just the combination of lots of different things makes this slightly more complicated.
Oh I have a degree in systems and networking too.
Last edited by genderbender; 08-27-2010 at 03:52 AM.
I've been a sun admin for about a year now, prior to that I worked in a data centre for around a year (mixed systems, mostly ubuntu and freebsd). I'm currently building nagios plugins for a data centre and an automated nagios build agent (both almost complete).
Things I'm new to:
The effects of running fsck on a rewritable file system (I usually say no and choose to boot off the disks).
Successfully running veritas :S.
VERY old systems which are architecture specific (sun on spark workstations).
I'm not massively experienced but I've worked with fsck before, just the combination of lots of different things makes this slightly more complicated.
All this is really nice but why have you quoted me in that post ? I never questioned your experience
All this is really nice but why have you quoted me in that post ? I never questioned your experience
Oh sorry, completely misread that - thought it was aimed at me Apologies, i probably seem like a complete ass now. I'm gonna mark this as resolved now though seeing as the problem no longer exists and it seems to be causing a small ammount of conflict.
Solution was to move the disks to a new machine. I suggest nobody runs fsck on a r/w filesystem - the results will be unexpected i'd imagine and could damage the entire system.
I think I completely misread what mithilesh parmar mithu was trying to say actually - I thought it was a dig at me, suggesting I was inexperienced and i shouldn't be doing this kind of stuff but now when I read it, it seems like a standard run of the mill "am I smart enough to get a job" type question. Which seeing as I've been a bit unfriendly I'll answer anyway.
Qualifications do matter a great deal, in most of the computer companies ui've worked for they'll have windows systems and a couple of unix/linux systems, these are the systems which run important stuff and you'll slowly gain experience of how to use them (this is entirely dependant on the number of linux systems the company uses). The learning curb is fairly steep but it has a logical pattern which you quickly get used to and although lots of people may disagree with this, there are no HUGE differences between linux distributions (there are between unix systems though). If you can use one you probably have enough skill to do basic things on another (the basic tools you need will always be there).
I worked with a sys admin once who had no unix skills at all and worked with unix systems at home, he was entirely reliant on the command line and didn't touch the gui. He had no educational experience and from what I can gather he initially fell into a job 9like the previous example I've given). I think nower days you're less likely to get into a computery job without somne qualifications but it does still happen and experience counts for everything. So my advice for any 'freshers' out there would be expose yourselves to the command line, ignore the gui (most important servers wont use it), for me I found my knowledge grew much faster when I became quite good at bash scripting. Set yourselves little tasks, the things that linux can do is boarderline unlimited, there are kernels created for things that seem more challenging (ones made for hacking or for making music or for artistic stuff for example). If you do this you'll break the system a few times, slowly (painfully) learn to repair it but eventually be able to do it quickly - this is much better than breaking it in the workplace, trust me! Also the linux community is very vast, if I post a question on here it's usually answered the same day so I rarely feel any distance from someone who can help.
To summarise: Freshers aren't usually let into unix admin roles although this doesnt mean you should rule yourself out. Gather as much experience as possible (find out about inodes all unix interviews have questions on inodes). Ask if you have any serious problems, people enjoy helping.
I came out of uni with very little expose to linux and gradually learnt it and then got into an entirely unix role. Something attracted me to it, I think being in control and not feeling limited by what a gui can do. This 'attraction' is the heart of all my learning and will continue to be until I lose interest. Frankly for every challenge I find it's another reason to stay in my job that little bit longer, it's another hurdle I can jump over, another experience to write down and memorise.
I think I completely misread what mithilesh parmar mithu was trying to say actually - I thought it was a dig at me, suggesting I was inexperienced and i shouldn't be doing this kind of stuff but now when I read it, it seems like a standard run of the mill "am I smart enough to get a job" type question. Which seeing as I've been a bit unfriendly I'll answer anyway.
You really need some sleep now and you have really made a nice effort in answering the poor fellow in POST 16.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.