Linux Build Engineer Vs System Administrator
Could you plz. help me in determinig, which stream is better
Linux Build Engineer Vs Linux System Administrator
in terms of financial growth.
And also please tell me whether a software developer earns more than linux system administrator or not.
please suggest me your view points.
It all depends on the company really and whey they do.
I've worked at a company where the majority of the developers make anywhere from 40K a year to 100K a year..
The System Administrators made anywhere from 35K a year to 95K a year. I know some System Administrators that exceed the 100K mark but usually they have a wide range of knowledge, experience and usually have more to deal with. A small company with several servers and such, the System Administrator could range from low 30K to 60K. Larger companies with more IT infrastructure will pay more since there's more for an Administrator to handle, monitor, etc.
A Linux Build Engineer comes off as a person who tests and builds within the Linux environment with maybe some slight Administration work. I've seen these types of jobs start from 30K up to 100K plus, all depending on the work being done and company.
Your best option to research would be to look up job's, their pay and duties on salary sites like www.salary.com or the like..
I would be greatfull, if more LQ people give me their view points regarding post1.
"If you're in it for the money," you might never be satisfied, and you might never do a really good job.
Instead of pondering "who makes more money?" ... think about which (if either) of these jobs you would enjoy doing.
The "systems administrator" is the person who's doing his/her job well when nobody notices that the job is being done. "The show starts precisely on-time and the lights come up and every single light is properly illuminated and pointing in just the right direction, just like last night and the night before," and the systems-admin sees no reason to point out that s/he spent yesterday afternoon looking for and replacing burned-out bulbs. The boss sees no reason to thank him/her, but the boss never has to worry about shadows on the stage...
A "build engineer" is another background-person of a different sort. Because of his/her efforts, there's no doubt in anyone's mind that the CD-ROMs that are now being generated by the thousands (at several dollars apiece), and packaged and sent to customers, will contain the correct information ... will have been properly compiled or recompiled from what is the latest and correct source ... and have been properly QA-tested.
Both people are suitably well-paid. Each of them, obviously, depends very much on the money and damn well earns :) the money... but they're not doing it to count their pennies. Those jobs ain't glamorous. But they're essential. The costs of their failure to do their jobs well are considerable. These individuals are highly trusted.
"Do what you love, and the money will follow."
sundialsvcs, I like your reply :)
What kind of technical expertise and skills a Build/Release engineer is supposed to possess?
Thanks in advance!
linking problem of application with driver
Need help with linking the PLX chip (PCI 9656) driver with the application that has been developed on C.
We built the PLX driver using the downloaded PLX SDK-4.4. Then the codes are successfully compiled and the application is made.
When the application is run, it is unable to detect/select the PLX device.
Although the sample PLX applications(like PlxCm) are running fine and are able to detect the PLX device.
How to link the PLX driver with the application? Is there any specific process for that (other than following the usual build steps for the PLX driver) ?
Is this because of some issue with our application, or this might be due to incorrect build of the driver?
Please suggest how to go about it.
|All times are GMT -5. The time now is 11:14 AM.|