|
icehewk posted:Is there a good book/youtube channel to get started with working and administrating *nix? My general suggestion for leaning *nix in a general way is to install a linux distro on a VM, and break it as much as you can. Once you are used to fixing the dumb poo poo that people do, try getting a fully working Gentoo installation going from scratch. This isn't gonna teach you best practices or anything, but damned if you won't end up with a good idea of how everything fits together. Once you do that find a RHCSA book, or something similar, to learn the best practices type stuff, tho alot of that seems to vary based on what flavor of *nix you are using(Learning Solaris has been interesting after working Linux for a while)
|
#
?
Mar 19, 2014 04:05
|
|
|
|
| # ? May 11, 2024 21:55 |
|
|
Lord Dudeguy posted:I... what? They are technically network admins, and use a Windows-based remote administration GUI almost all the time. Still, I find it hard to believe that they've never used any sort of shell other than Cisco given the proliferation of *nix-based network appliances in the world. Hell, even Windows has "cd" at least on the command line. The breadth of knowledge required in modern IT pretty much guarantees that you're going to have significant knowledge gaps somewhere. I can't tell you jack poo poo about anything below the network layer beyond "switches/ethernet/802.11x/CatX/FC/etc. is voodoo magic operated by gremlins.
|
|
#
?
Mar 19, 2014 04:09
|
|
|
scroogle nmaps posted:The breadth of knowledge required in modern IT pretty much guarantees that you're going to have significant knowledge gaps somewhere. I can't tell you jack poo poo about anything below the network layer beyond "switches/ethernet/802.11x/CatX/FC/etc. is voodoo magic operated by gremlins. A good admin doesn't have to know everything, but they should at least be able to figure stuff out given some time and Internet access. Hell, I don't know much about networking beyond how to configure a server so its packets go to the right places and don't all disappear up its own rear end in a top hat, but I've helped our networking team troubleshoot issues several times. I was on a conference call with a network hardware vendor once while we were working on a particularly annoying issue, and fifteen minutes into the call I was having to frantically google up manuals so I could tell the vendor support guy the right command syntax to run on the network device whose interface I'd never laid eyes on before that call. (I also ended up finding the workaround for the issue we were having in the end, so the vendor support kinda struck out entirely that time...  )
|
|
#
?
Mar 19, 2014 04:41
|
|
|
Che Delilas posted:I've heard that southern Texas's weather is "like Florida" in that it's oppressively hot+humid. I keep hearing people complain about how bad it is to live in weather that is both hot and humid. There was a week this last January where the air here was so hot and dry I was woken up each morning for 7 days straight by blood noses. 8 hours of not drinking was long enough for surface blood vessels to start cracking from lack of moisture. No blood on the pillow either, I am way to good at this poo poo. Take your humidity like a man and count your blessings. Driest state on the driest continent in the world, represent! 
|
|
#
?
Mar 19, 2014 04:56
|
|
|
Sickening posted:Less than a hour of work and I am done! Things went down like this.... This is glorious! This is what happens when you stick to your principles and not sell yourself short! Great job Sickening!!! E: Awful app posting 
Baby Town Frolics fucked around with this message at 14:34 on Mar 19, 2014 |
|
#
?
Mar 19, 2014 05:23
|
|
|
RFC2324 posted:My general suggestion for leaning *nix in a general way is to install a linux distro on a VM, and break it as much as you can. Once you are used to fixing the dumb poo poo that people do, try getting a fully working Gentoo installation going from scratch. Breaking a bunch of poo poo is just as pointless as installing Arch. Install Vagrant. Run teams of servers (nginx+mongo+redis or whatever). Build, don't break. You have to do useful things to learn useful things. This is exactly the methodology the RH* certs use as well.
|
|
#
?
Mar 19, 2014 05:51
|
|
|
evol262 posted:Breaking a bunch of poo poo is just as pointless as installing Arch. Install Vagrant. Run teams of servers (nginx+mongo+redis or whatever). Build, don't break. You have to do useful things to learn useful things. This is exactly the methodology the RH* certs use as well. I dunno, learning to fix things that have been broken seems like an awfully useful skill to have. I know its been 75%+ of my job in various sysadmin roles so far. Far better to learn how to break things(and hence how to fix them) on a VM on your home machine than in a production environment.
|
|
#
?
Mar 19, 2014 06:05
|
|
|
Sir_Substance posted:I keep hearing people complain about how bad it is to live in weather that is both hot and humid. Hang on - which state are you in where that happens? I'm going to take a random guess and say WA?
|
|
#
?
Mar 19, 2014 07:15
|
|
|
RFC2324 posted:My general suggestion for leaning *nix in a general way is to install a linux distro on a VM, and break it as much as you can. Once you are used to fixing the dumb poo poo that people do, try getting a fully working Gentoo installation going from scratch. Yeah, just experiment. I learned linux with the help of someone over IRC back before #SHSC got hijacked by anti-goons. I used to tinker with old laptops and decided that I was tired of Mac OS 9 on my original ibook so I went and installed linux on it and got some help setting it up. 3 kernel recompiles later and we finally got everything working, including the sound. I still have that laptop and it's still running a (by now very old) version of slackintosh. Later on at an internship they set up an ESXi box for the interns to test some software on and in my spare time I went nuts installing every free operating system I could find on it to get a feel for things and developed an appreciation for FreeBSD. There are probably plenty of people here who are willing to provide advice if you're serious and we have a free moment, myself included. I don't think this is the right thread for it though.
|
|
#
?
Mar 19, 2014 08:11
|
|
|
Helushune posted:I think it was earlier in this thread, someone had mentioned that Dell doesn't update any of the drivers on their FTP site anymore or something like that. I still use it because it's still heaps better than trying to use Dell's support site when I need a driver to inject in some WDS images. That was me when someone just linked to an outdated page on that site. Just browse from http://ftp.dell.com, and you should be good.
|
|
#
?
Mar 19, 2014 08:53
|
|
|
Humphreys posted:Hang on - which state are you in where that happens? I'm going to take a random guess and say WA? SA bro. We wish we got as much rainfall as WA, that way we wouldn't have to water our crops with Victorian piss! Check out the surface runoff figure.
|
|
#
?
Mar 19, 2014 09:00
|
|
|
Sir_Substance posted:SA bro. We wish we got as much rainfall as WA, that way we wouldn't have to water our crops with Victorian piss! I'll be staying on the east coast thankyou very much! I've heard enough horror stories about heat and fire in SA
|
|
#
?
Mar 19, 2014 09:05
|
|
|
Humphreys posted:I'll be staying on the east coast thankyou very much! I've heard enough horror stories about heat and fire in SA Yeah, but it's a dry heat.
|
|
#
?
Mar 19, 2014 10:21
|
|
|
Sir_Substance posted:I keep hearing people complain about how bad it is to live in weather that is both hot and humid. Dude, humidifiers exist for a reason. Buy one. I even run one in Michigan all throughout winter because otherwise my skin feels unbearably dry and I wake up with a sore throat in the mornings, and that's with 30%+ humidity outside.
|
|
#
?
Mar 19, 2014 11:52
|
|
|
Sirotan posted:Dude, humidifiers exist for a reason. Buy one. I even run one in Michigan all throughout winter because otherwise my skin feels unbearably dry and I wake up with a sore throat in the mornings, and that's with 30%+ humidity outside. Not a bad idea. It's not something I'd really heard of or considered until now, but apparently they're available here. Might be a buy for next summer.
|
|
#
?
Mar 19, 2014 12:12
|
|
|
Sir_Substance posted:Not a bad idea. It's not something I'd really heard of or considered until now, but apparently they're available here. Might be a buy for next summer. I think even here room humidifiers are probably most associated with (sick) children, but they are a life saver in the winter even if all they do is keep me from zapping myself on everything, all the time. I used to think it was always my forced air furnace that was drying the air out until I just this year lived in an apartment with baseboard heat and it was just as bad.
|
|
#
?
Mar 19, 2014 12:28
|
|
|
RFC2324 posted:I dunno, learning to fix things that have been broken seems like an awfully useful skill to have. I know its been 75%+ of my job in various sysadmin roles so far. Yeah but how do you know how to "break things"? Am I supposed to just install CentOS on an extra computer I have lying around and delete random files? "Just break stuff and learn how to fix it!" is pretty useless advice and people only give it because they already know the systems involved.
|
|
#
?
Mar 19, 2014 13:36
|
|
|
Fixing stuff that's broken was a good 75% of my last job too (and 100% of my current one). Doesn't mean learning to break it is useful. Learning how something works and loving it up (by accident) is far more useful, as it'll give you an inkling of where some people might go wrong with it, how to troubleshoot, what steps to take, etc. Just breaking poo poo to fix it is like poking holes in a piece of wood and then trying to figure out which part goes where. Its obvious, because you just did it, on purpose.
|
|
#
?
Mar 19, 2014 13:45
|
|
|
Inspector_666 posted:"Just break stuff and learn how to fix it!" is pretty useless advice and people only give it because they already know the systems involved. The process is no different to how we all learned computers in the first place. Just dick around. No one ever became good at computers by reading a textbook from front to back. Pick a bunch of random web services and see how many you can make run at once. I promise you you'll have some kind of issue by the time you get to number three, and by the time you get to 10 it'll be a miracle if they aren't trying to eat each other like starved dogs in a cage.
|
|
#
?
Mar 19, 2014 13:52
|
|
|
Sir_Substance posted:The process is no different to how we all learned computers in the first place. Just dick around. No one ever became good at computers by reading a textbook from front to back. Pick a bunch of random web services and see how many you can make run at once. I promise you you'll have some kind of issue by the time you get to number three, and by the time you get to 10 it'll be a miracle if they aren't trying to eat each other like starved dogs in a cage. Right, but "Set a goal and get it working" is practically the polar opposite of "Just break stuff and then fix it."
|
|
#
?
Mar 19, 2014 14:05
|
|
|
Good lord we're arguing Symantecs here. Build things, break them by doing something wrong unintentionally, build your skillset by figuring out how to unbreak them. Sip Coffee, repeat until you're either fluent in *nix or experience a burning ragequit.
|
|
#
?
Mar 19, 2014 14:22
|
|
|
I live and work in Boston. I work for a security company that creates applications for penetration testing and security analytics. I recently had the delight of doing the technical interviews for all the potential folks looking to get into one of our senior support roles. Due to the nature of the work the people we need to know networking pretty well and know a good bit of linux admin. My boss made me do all the technical questions of which I made a page or 2 of softball questions just to screen out the idiots. The follow is a typical conversation with people that actually came in to interview. VanOwen -  Your resume says you know linux!RandomPerson -  Sure do!VanOwen - Great! How would I see all the files in a directory?RandomPerson - - Uhh... Not sure!VanOwen -  Uh... OK. Maybe you're nervous? You must be nervous. Its 'ls'. RandomPerson - Oh right. Of course! Ha ha!VanOwen - Ha ha! OK so how could I show all the permissions on files and folders in a directory?RandomPerson - Uhh... Not sure!VanOwen -  So... you... ah... OK. Hey! Your resume says you know DNS! That's a thing!RandomPerson - Sure do!VanOwen - So how does name resolution work?RandomPerson - - Uhh... whats that?VanOwen -  Repeat this half a dozen times. And bear in mind I haven't even gotten to the stuff on networking, LDAP, SQL, python, regexp, or up-teen other items on my list. VanOwen fucked around with this message at 14:41 on Mar 19, 2014 |
|
#
?
Mar 19, 2014 14:23
|
|
|
VanOwen posted:I live and work in Boston. I work for a security company that creates applications for penetration testing and security analytics. I recently had the delight of doing the technical interviews for all the potential folks looking to get into one of our support roles. Due to the nature of the work the people we need to know networking pretty well and know a good bit of linux admin. My boss made me do all the technical questions of which I made a page or 2 of softball questions just to screen out the idiots. The follow is a typical conversation with people that actually came in to interview. Hiring support people who are strong with networking and know linux has to be a tough sell. I am guessing you are paying standard support person rates?
|
|
#
?
Mar 19, 2014 14:26
|
|
|
I am not in charge of the money (I would abuse that so hard so fast) so I don't know for sure. Glassdoor claims the average here is like $70k/year and I want to say we are paying a little better then that but, I am not sure. I made more then that but, who knows what budget they have for that slot now. Oh this was for a senior tech support role too. I probably should have mentioned that. We obviously wouldn't expect a new person to know everything but, a more senior person we might expect more. I was actually the senior support guy but, they are moving me into professional services (  ) so they are making me ask all the low level detail questions for these folks.
|
|
#
?
Mar 19, 2014 14:40
|
|
|
Pretty much no matter who you are though, if you list linux as a skill, then you should know what ls are. Same with DNS and then not knowing what name resolution is. It's not like it's hard, I bet you than just being able to answer that it translates between names and ip adresses would have been enough. I am glad I am not involved in the hiring process, I bet that would make me lose my faith in humanity fast
|
|
#
?
Mar 19, 2014 14:47
|
|
|
I have practically zero Linux experience (absolutely none in a "production" environment) and even I know what ls is.
|
|
#
?
Mar 19, 2014 14:53
|
|
|
VanOwen posted:I live and work in Boston. I work for a security company that creates applications for penetration testing and security analytics. I recently had the delight of doing the technical interviews for all the potential folks looking to get into one of our senior support roles. Due to the nature of the work the people we need to know networking pretty well and know a good bit of linux admin. My boss made me do all the technical questions of which I made a page or 2 of softball questions just to screen out the idiots. The follow is a typical conversation with people that actually came in to interview. It's fizzbuzz all over again. Surprised there isn't an equivalent for tech support.
|
|
#
?
Mar 19, 2014 15:27
|
|
|
hihifellow posted:It's fizzbuzz all over again. Surprised there isn't an equivalent for tech support. For Windows stuff it's just "please troubleshoot this error", followed by seeing if they can figure out how to open the event log.
|
|
#
?
Mar 19, 2014 15:29
|
|
|
EAT THE EGGS RICOLA posted:For Windows stuff it's just "please troubleshoot this error", followed by seeing if they can figure out how to open the event log. "Here is a common problem with multiple possible causes. Walk me through your troubleshooting process, starting with the simplest solutions and advancing to more difficult ones." Examples: -User calls complaining that they can't access a network drive. -User indicates their wireless isn't working. -Outlook shows Exchange is disconnected. Show me that you can think. Show me that you know how to analyze a problem and look through potential solutions in a sensible order.
|
|
#
?
Mar 19, 2014 15:40
|
|
|
RFC2324 posted:My general suggestion for leaning *nix in a general way is to install a linux distro on a VM, and break it as much as you can. Once you are used to fixing the dumb poo poo that people do, try getting a fully working Gentoo installation going from scratch. Gentoo doesn't teach you poo poo other than how to type emerge.  Your best bet is to do a lfs distro and read up on every package you install and what it does. That's what I did back in the day. 
|
|
#
?
Mar 19, 2014 15:41
|
|
|
1> Hey guys, we need to do some e-mail account migrations in Exchange, almost 2000 of them across sites all over North America. What do you think the best way track this process is? Microsoft Excel? Super, let's do that. 2> Surprise audit by one of our certification companies or something, I have no idea who they are or what they want, but I am the only salaried person here, so I guess I get to waste a few hours of my day until someone gets back. Not happy.
|
|
#
?
Mar 19, 2014 15:56
|
|
|
AlternateAccount posted:1> Hey guys, we need to do some e-mail account migrations in Exchange, almost 2000 of them across sites all over North America. What do you think the best way track this process is? Microsoft Excel? Super, let's do that. Which certification company?
|
|
#
?
Mar 19, 2014 16:18
|
|
|
Sickening posted:Which certification company? http://www.naidonline.org/
|
|
#
?
Mar 19, 2014 16:44
|
|
|
Should I have heard of this organization before? Are they like the industry standard in data destruction or something? Is that even a thing?
|
|
#
?
Mar 19, 2014 16:47
|
|
|
ratbert90 posted:Gentoo doesn't teach you poo poo other than how to type emerge. FreeBSD. Compile everything from ports (which makes non-IT people wonder what the hell you are doing with all the 'gibberish' constantly scrolling by). Then try another distro. I enjoy FreeBSD and like Debian as headless machines. I like OpenSUSE (KDE) when I'm using a GUI.
|
|
#
?
Mar 19, 2014 16:50
|
|
|
Sickening posted:Should I have heard of this organization before? Are they like the industry standard in data destruction or something? Is that even a thing? Maybe? This is my first job in this industry. If you look at basically anyone who does "secure shredding" then they're likely to have it. Reading the requirements, it's basically just stating that you shred things properly and don't drive big open dump trucks full of sensitive data. And they do "random" inspections, but we've had THREE in less than 12 months, which is apparently absurd enough for the inspector to comment on it.
|
|
#
?
Mar 19, 2014 17:13
|
|
|
wintermuteCF posted:"Here is a common problem with multiple possible causes. Walk me through your troubleshooting process, starting with the simplest solutions and advancing to more difficult ones." I got given a situation involving an office network being down, and I guess I did well on it since I got hired, but man was it hard for me to go through my usual checklist in order without the equipment actually in front of me.
|
|
#
?
Mar 19, 2014 17:55
|
|
|
A c E posted:FreeBSD. Compile everything from ports (which makes non-IT people wonder what the hell you are doing with all the 'gibberish' constantly scrolling by). Then try another distro. Note: If you compile packages on an enterprise-supported OS (RHEL, Ubuntu), your support phone calls will suddenly become incredibly short. "Hi, I'm having a problem with BIND." "I notice you compiled your own version of $unrelated_package" "Well yeah I..." "Please get your system back to a point where it's using our repositories exclusively, then call back. Thanks for choosing RedHat!"
|
|
#
?
Mar 19, 2014 18:02
|
|
|
A c E posted:FreeBSD. Compile everything from ports (which makes non-IT people wonder what the hell you are doing with all the 'gibberish' constantly scrolling by). Then try another distro. This has exactly the same problems as Gentoo. New users have no idea what they're picking in portconfs or make.conf, have no idea what the compiler output means (it's 'gibberish' to them as well), and will quickly get frustrated with spending all their time installing random stuff, assuming they can even find anything they give a poo poo about installing. Read the CentOS Deployment Guide or the FreeBSD handbook instead. Lord Dudeguy posted:Note: If you compile packages on an enterprise-supported OS (RHEL, Ubuntu), your support phone calls will suddenly become incredibly short. As a Redhat employee, this is total bollocks. We'll still give you best effort support no matter what stupid thing you did. If we can't reproduce your problem and it's eating too much of our time, sure, we'll ask you reproduce it with stock RHEL RPMs. But it's not even close to the first response.
|
|
#
?
Mar 19, 2014 18:09
|
|
|
|
| # ? May 11, 2024 21:55 |
|
|
Lord Dudeguy posted:Note: If you compile packages on an enterprise-supported OS (RHEL, Ubuntu), your support phone calls will suddenly become incredibly short. Heh, looks like somebody still uses $var instead of ${var}.
|
|
#
?
Mar 19, 2014 18:15
|
|