I may be getting a part-time job at a local data center that runs primarily everything on CentOS. I've honestly only dabbled with Mint, Fedora, OpenSUSE and Ubuntu on desktop and I mean LIGHTLY dabbled. I can find myself around any desktop, it doesn't scare me to get thrown into a new OS and "figure it out" I can do so with ease. However, I'm still below or par with an amateur with Linux in general, period.
For all you Linux gurus out there, what is your #1 "must know" for basic Linux server usage; something you'd want your apprentice to learn immediately.
With my limited knowledge, I'm guessing that command is the equivalent of deleting/removing root admin privileges so you can be a cool haxor?
A Linux "job"? Are you kidding me? You are not fooling us, everybody knows that lincucks is a hobby OS and that everyone in the industry and in the job market use MS Windows and write reports in MS Word. There is no such thing as a "Linux Job", at least in the real world, unless you consider a job sucking freetard dick for 5 bucks or a muffin to avoid dying of starvation.
Here's the companies website. http://www.cyberverse.com/
You better inform them there is no such thing as a "Linux job".
It's only for your account, root still exists and other accounts will have to use sudo. If your account has a password it's fine. Sure it's not as secure, but it's hella convenient, that guy was talking about being a leet haxor anyway but event being able to use ifconfig, iwconfig, and update without having to type in my password a billion times is worth it for me.
Take a look at the goddamn thread name "Top Linux SERVER 'Must-Knows'".
That fucking means SERVERS. You fucking think everyone in the job market has a server on their desk? Unix-like systems run more than 65% of all internet servers. Linux is fucking BUILT for server use.
A "Linux" job would be something like system administration. Working on a server so normies can send each other nudes and faggots like you can post shit on a taiwanese basket-weaving site.
rm "remove" - deletes files
-r "recursive" - traverse directories, deletes symlinks but doesn't follow
-f "force" force delete, no matter what
/ - root directory, the top most directory on the filesystem, contains all attached drives, network drives, everything on the system
--no-preserve-root - disables a safety feature so that you can actually delete the root directory. Only useful in very specific circumstances, eg chroot
i this can be pretty useful for many peopledd if=/dev/zero of=image.img bs=1M count=1024
This will create an ext3 filesystem in a 1GiB file called 'image.img'. You can now mount this file as and use it to store stuff. Very handy when you want to deal with a lot of small files without cluttering your current filesystem directly. You can mount this bymkdir mountpoint
sudo mount image.img $PWD/mountpoint
I'm 25 and I applied? I've worked with Windows Servers forever, I've done customer support and network support for 2+ years. Again, note "PART-TIME", its not like I'm going to be senior network admin or some crazy shit. It's all fairly menial tasks. They plan on training me and then possibly boosting my position to full time if I prove competent. Also NOTE that I didn't say I have this job in the bag, I said "I may be getting a part-time job."
root does not cause exploits, but running everything as root means that malware and virusses also run as root.
Also, it allows the user to accidentally wipe stuff without confirmation.
Did we ever talked about exploited, fag? No, not really. The next time read better and stop blaming others for your own faults.
Watch at him: >>52629793
>but running everything as root means that malware and virusses also run as root.
No, it doesn't. Only if you run infected stuff.
So, if as root, you do not surf the web, you are pretty safe.
>No, it doesn't. Only if you run infected stuff.
Sure and you know which USB is not infacted and which USb is a badUSB or which pdf is infected and which pdf is not infected. When is the time you know if stuff is infected or not?
>So, if as root, you do not surf the web, you are pretty safe.
And all the services of a programm etc in the background don't can communicate with the WWW or to other servers? And you change everytime from root to non-root when you search? Before I have to change everytime I just run as non-rot and when I need the privileged I logging in as root. Wtf? That make no sense m8.
>Its a server setup, not a desktop environment.
Sure, I know. But e.g. a terminal server with different thin clients are not a server setup? I can infect the terminal server above a thin client? What is with all the shh connections, when ssh services are available from outside? There are enough examples...
But why you have to run always as root privileged, there is no sense? Explain it? You just have to run as root privileged when you need it.
Enthusiast distros are for enthusiast uses, desktop distros are for desktop uses; not for work and servers. No Gentoo, Arch, Fedora, Slackware or Mint. Use the server distro your most comfortable with: CentOS/Scientific Linux for RPM based, Ubuntu Server (LTS) or Debian (stable) for apt based.
Man is your friend. There is a wealth of information right on your system, and often it will tell you what you need. Type a /, then a weird your looking for, then hit enter to search. There are plenty of long time *nix users where I work who didn't know that.
Likewise, Google is your friend, and Ubuntu forums is your well intentioned half wit friend who remembers kludgy fixes for a 1977 VW, and insists you can fix your 2015 model year Corvette the exact same way.
Document the shit out of what you do, and keep it to yourself. Seriously, a tiny private dokuwiki server will save your ass ten months after you had to tweak some odd sysctl settings and have to recreate it.
Page through some your logs once in a while. Google for their meaning. Gives you an idea of what's normal.
Monitoring is as Important as firewall rules. Rules on inbound and outbound traffic are important, but running a SMART hard drive check is just as important. Smart monitors to monitor hard drives, install and enable sar to get some local detailed metrics on the system. If you're setting up shop, install a monitoring system like nagios/icinga. Letting a server get penetrated because you didn't setup reasonable firewall rules is just as lose your job worthy as losing the production database because half your RAID 1 had been retrofit fort months and finally died hard.
>You just have to run as root privileged when you need it.
But that doesn't imply that you are safe. Even a compromised program can run sudo under your name and if you have sudo privilege, your done. Wheel group, chroot jails, restricted shells, disabling non-essential apps and not using your server as a desktop and ssh with client certificates do contribute towards running a shell as root.
Have you investigated how you access an AWS cluster?
>For all you Linux gurus out there, what is your #1 "must know" for basic Linux server usage; something you'd want your apprentice to learn immediately.
Sysadmins are the worst people you will ever meet.
>But that doesn't imply that you are safe.
never said that.
>Even a compromised program can run sudo under your name and if you have sudo privilege, your done.
Yes, thats right. But I seperate it correctly.
>Wheel group, chroot jails, restricted shells, disabling non-essential apps and not using your server as a desktop and ssh with client certificates do contribute towards running a shell as root.
So, who's got a wireless keyboard connected to their console?