Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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 exactly is the difference b/w sys admin and a n/w admin ? in my experience they both are the same, isn't it ? , but i keep hearing from some people that they are different ? what exactly is the true story ?
My understanding is that they have a different focus. A sysadmin works mainly on servers like installing software, configuration etc.
A network admin works mainly on routers, switches and so on.
If you have package loss you go to the network admin, if you need an upgrade on a web server you ask the sysadmin.
Well generally the network admin looks after the network and the systems admin looks after the systems. Sorry if that sounds crude / rude, but the clue is in the title. Of course many many many businesses combine the roles formally or informally, but past a certain size of infrastructure the work on the servers, server operating systems and applications is seperated from the work on the routers, switches and firewalls. Maybe you'd be suprised how many sysadmins have no idea about TCP/IP past an ip address and default gateway.
Well that's down to the way a company works. If you can afford people who can cover an entire infrastructure at a suitable level then that's the better option usually - until sheer vast scale makes it unworkable. I used to be a strictly assigned network admin in a team of about 5 people at the higher technical level. Currently I'm right across the board with Linux and Network as specialities in a flexible pool of about 40... horses for courses really.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.