Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
What is it that separates the user from the administrator? What is it that is expected from an administrator? Those of you that have been RHELAs, would you be able to share what you do in a typical day?
What is it that separates the user from the administrator?
Responsibility, scope, privileges, knowledge. Some users may have the required knowledge and may even act responsibly but most of the time they have limited access to systems or services and are focused solely on causing harm completing their tasks whatever that may be.
Originally Posted by dprotaganist
What is it that is expected from an administrator?
To keep the whole infrastructure functioning continuously, securely, resiliently and with the best performance, all in the face of current and future threats upstream, supplier, vendor, fellow admin and user SNAFUs.
Originally Posted by dprotaganist
Those of you that have been RHELAs, would you be able to share what you do in a typical day?
The administrator is the one who has administrative privileges. If you don't have administrative privileges, then you're a regular user, plain and simple.
Can users be more technically qualified than administrators? Absolutely. I've been granted user access on Linux systems that are administered by people who know significantly less than I do about Linux administration, but I'm still a user and they're the administrator. I've even had to walk administrators through the process of whitelisting my IP because they didn't set the password on my account properly and I was automatically blacklisted by their denyhosts script, which they didn't even know was installed, how it worked, or how to bypass it once an IP was flagged.
What is expected from an administrator? The administrator is responsible for the system as a whole, including its security, stability, and reliability. The administrator needs to know all of the system's potential vulnerabilities and the measures that are in place to mitigate those vulnerabilities - IE: what ports are open to the LAN, who has access to the LAN and can it be trusted, what ports are open to the public, what services are listening on those ports, are those services up-to-date, what firewall rules are in place to limit access to those ports, what users have access, through what channels do they have access, what permissions do they have once they're in, can secure files be accessed by unauthorized users, what are the repercussions of an authorized user's remote system getting hacked/stolen, how could those vulnerabilities be mitigated, etc. And ultimately, how can the system be configured such that all of the above is reasonably secure while still allowing the users to do their jobs and reducing the administrator's labor requirements to a reasonable level.
Note that there is a fine line between allowing users the freedom to do their jobs and restricting the network adequately to protect it from users being idiots. It's up to the administrator (in cooperation with the CEO/CTO/C?O/Board/Management) to decide where this line needs to be drawn. Startups and small companies often err on the side of trust and freedom, allowing their users the ability to do whatever needs doing to get the job done, within reason. Large companies often err on the side of caution, assuming their users are idiots and clamping down wherever possible to limit the fallout when somebody does something stupid and compromises the network. Neither approach is better than the other, is all about mitigating risk at the expense of users' freedom/havoc-wreaking-ability.
I have no idea what an RHELA is, but I am the administrator for my company's network (it's a small company). My daily tasks rarely have anything at all to do with IT or Linux administration, they're typically focused on what I was actually hired for - data analysis and embedded systems development (hardware and software). When I do need to put on my administrator hat, It's typically to add a user to the system, update a user's permissions, add a new shared directory for a project that's accessible by all authorized users, install a new library or program that's required by one or more of the users for a project, or simple routine updates.
Last edited by suicidaleggroll; 07-08-2015 at 10:11 PM.
The administrator (root in Linux) has power to do everything and anything in the system. This includes power to break the system.
Users (members of the "user" group in Linux) are allowed to run programs and manage data files in their home directories, but they cannot install, remove, modify, or access system files, programs, or processes. Users may have additional privileges granted to them if root makes them members of various groups which have additional privileges, such as the "wheel" group (I learned this week that the term, "wheel," is derived from the expression "big wheel," and has nothing to do with mouse wheels).
being a sysadmin/RHELA or whatever you call it (linux admin/engineer/technician) - the work revolves around the operating systems of Linux/Unix systems - from overall systems administrations , troubleshooting, providing after hour support , storage allocation , security on files/folders , provisioning of quota , commissioning and decommissioning of servers , storage , sometimes network switch, ddos firewalls, iptables firewall and some capacity planning , DR ..... hope this helps
many kind of servers are there - depending on business needs.
I am bit familiar only with HP servers - and i can name a few types.
The term "server" refers to what the machine does, not who makes it or what model it is. A raspberry pi can be a perfectly adequate server for many different services if it's set up as such.
When a company markets a machine as a "server", they're basically saying that it's good at high bandwidth I/O and number crunching, crappy at video, and is loud and obnoxious. There's no reason any other system can't be used as a server as well, it's just that "servers", as marketed by the groups you mentioned, can really only do that, they're ill-equipped for much else. In other words, a "workstation" would be perfectly suited for server duty, but you'll never find a "server" pulling workstation duty...it would be horrible for everyone involved.
Last edited by suicidaleggroll; 07-09-2015 at 11:41 PM.