Linux skills are hard to find
-
@scottalanmiller said in Linux skills are hard to find:
@Dashrender said in Linux skills are hard to find:
@PSX_Defector said:
I can do lots of things in both types of environments, but that's because I'm old and have seen it all. I stick with Microsoft because its more lucrative, being that people expect if you know Windows then you know SQL, Sharepoint, Exchange, and XBox. Opens more doors for me.
While this is bizzare, I've definitely it to be true - Just because you know Windows, well hell then you must know SQL, SP, etc.
If you think that you see this in the Windows space, at least those are all products from the same vendor for the same OS. It's knowing the "Microsoft ecosystem." Which is, of course, still a rediculous thing to assume that someone knows. But on Linux we are often expected to just "know" three or four or five different operating systems, all of their tools, and a massive array of totally random third party applications that run on them. One database that we are just expected to know? Try ten. One web server, try three. One web application, try five. And none are predictable or from the vendor(s) in question.
The problem here is that the masses (and I'm talking about non IT management here) don't understand the difference between Linux distros. Goodness knows I didn't until you explained it a few months ago. If I recall correctly - The difference between distros is like the difference between Windows and Mac - except that all Linux distros run the Linux Kernel.
I'm still not entirely sure what makes one Linux OS better than another. Why this one is good for storage, and this one is good for DBs and this one is good for PBXes, etc..
-
OK Powershell I'll give you - I don't recall when it came out though, was it Windows 2000 or Windows 2003? A totally new OS?
Of course a new OS. DOS/Windows was replaced by Windows NT (based on OS/2.) They are fully unrelated OSes other than some slight attempt at a unified look and feel for end users. Nothing similar under the hood in the slightest.
One of the things that UNIX people often point to as a problem in the Windows space is that the Windows community is often unaware of even their own OS and see it only from the graphical perspective and not from the product itself.
Windows 98 was a DOS OS, not Windows NT. Windows NT 3.1, 3.5, 3.51, 4.0, 2000, XP, 2003, 2008, 2008 R2, 2012, 2012 R2 and 2016 are a different OS and OS family entirely from DOS which included DOS 1 - 7.x, Windows 1 - 3.11 WFW, 95, OSR2, 98, SE and ME
-
@scottalanmiller said in Linux skills are hard to find:
@wirestyle22 said in Linux skills are hard to find:
@coliver said:
@wirestyle22 said in Linux skills are hard to find:
I wonder if people run into the same issues that I do where it's hard to find the best/most accurate information regarding all of these things.
What do you mean? It is generally very easy to find accurate information for Linux and Windows. Understanding how to apply that information is a different thing all together though.
I mean in regards to nuances. I ran into this specific error code. I attempt to find an answer but it's a generic error code. Now you're subjected to other people's opinions. Look at ML vs. SW. Would I know the difference between a good opinion and a bad one at this point? Probably not.
Well if you have a generic error code, you are only going to deal with opinion. You need to move on to more troubleshooting to determine the actual problem.
I have very little Linux experience outside of learning through a few guides. At this point I wouldn't be able to troubleshoot effectively. Still learning how everything functions.
-
@Dashrender said in Linux skills are hard to find:
OK Powershell I'll give you - I don't recall when it came out though, was it Windows 2000 or Windows 2003? A totally new OS? The changes from XP to Win7 were pretty minor. As for XP to Win 10 - sure there are many more tool changes, but I'd say less than half actually changed. But if you were a PS user before, I don't think that changed all that much other than expanding on what was there before.
PS was huge, bigger than anything in the UNIX space within a single OS. Active Directory was huge, also bigger than anything in the UNIX space.
The interface leaps from NT4 to 2000 were pretty huge as well, as were the 3.51 to leaps.
-
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
-
@Dashrender said in Linux skills are hard to find:
I'm still not entirely sure what makes one Linux OS better than another. Why this one is good for storage, and this one is good for DBs and this one is good for PBXes, etc..
Different kernel models, drivers, features, file systems, support, and such. For example, Suse supports high availability clustering and the BtrFS file system, Ubuntu does not. This alone gives Suse a massive advantage in storage as it has a lot more options. Only some distros support DRBD, also huge for storage.
-
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Yeah that's where I'm at currently. It's going to take time but I will figure it out eventually. A lot of it does make sense to me even now with the small amount of experience I have.
-
@wirestyle22 said in Linux skills are hard to find:
@scottalanmiller said in Linux skills are hard to find:
@wirestyle22 said in Linux skills are hard to find:
@coliver said:
@wirestyle22 said in Linux skills are hard to find:
I wonder if people run into the same issues that I do where it's hard to find the best/most accurate information regarding all of these things.
What do you mean? It is generally very easy to find accurate information for Linux and Windows. Understanding how to apply that information is a different thing all together though.
I mean in regards to nuances. I ran into this specific error code. I attempt to find an answer but it's a generic error code. Now you're subjected to other people's opinions. Look at ML vs. SW. Would I know the difference between a good opinion and a bad one at this point? Probably not.
Well if you have a generic error code, you are only going to deal with opinion. You need to move on to more troubleshooting to determine the actual problem.
I have very little Linux experience outside of learning through a few guides. At this point I wouldn't be able to troubleshoot effectively. Still learning how everything functions.
Understood, but my point was about why you are seeing opinion - it's because you are at an opinion point. If you can only get opinion, or really random opinion, it is likely because you aren't looking deep enough or providing enough detail for anyone to know what is going on, or at least no one but the one running the system.
-
@coliver said:
Powershell has changed drastically. Every version is different then the previous one. The one thing that seems to remain the same is the awful Verb-Noun commands. Don't get me wrong, the changes are for the better, but they are still fairly dramatic changes.
Not only that.. Linux Bash is easy and logical..
Powershell is not something you can just think of like linux you have to memorize every command because they are not logical or easy to remember at all.
Which does against the nature of any command line interface, even switches/routers like Cisco IOS.
-
@Jason said in Linux skills are hard to find:
@coliver said:
Powershell has changed drastically. Every version is different then the previous one. The one thing that seems to remain the same is the awful Verb-Noun commands. Don't get me wrong, the changes are for the better, but they are still fairly dramatic changes.
Not only that.. Linux Bash is easy and logical..
Powershell is not something you can just think of like linux you have to memorize every command because they are not logical or easy to remember at all.
Which does against the nature of any command line interface, even switches/routers like Cisco IOS.
No question there. I will say that the basic commands are pretty intuitive Get-ComputerName is a really easy one to remember. However when you get into things like specific properties and finding properties of a command you will run into issues. Even the Get-Help (Powershell man-like pages) are pretty useless.
-
@scottalanmiller said in Linux skills are hard to find:
OK Powershell I'll give you - I don't recall when it came out though, was it Windows 2000 or Windows 2003? A totally new OS?
Of course a new OS. DOS/Windows was replaced by Windows NT (based on OS/2.) They are fully unrelated OSes other than some slight attempt at a unified look and feel for end users. Nothing similar under the hood in the slightest.
One of the things that UNIX people often point to as a problem in the Windows space is that the Windows community is often unaware of even their own OS and see it only from the graphical perspective and not from the product itself.
Windows 98 was a DOS OS, not Windows NT. Windows NT 3.1, 3.5, 3.51, 4.0, 2000, XP, 2003, 2008, 2008 R2, 2012, 2012 R2 and 2016 are a different OS and OS family entirely from DOS which included DOS 1 - 7.x, Windows 1 - 3.11 WFW, 95, OSR2, 98, SE and ME
You mentioned XP eariler when you were talking about a different OS - so I was starting at XP as the base for the discussion, not DOS or even Win9x. I did know that DOS/Win9x-ME are a different OS from the NT line.
-
@Jason said in Linux skills are hard to find:
@coliver said:
Powershell has changed drastically. Every version is different then the previous one. The one thing that seems to remain the same is the awful Verb-Noun commands. Don't get me wrong, the changes are for the better, but they are still fairly dramatic changes.
Not only that.. Linux Bash is easy and logical..
Powershell is not something you can just think of like linux you have to memorize every command because they are not logical or easy to remember at all.
Which does against the nature of any command line interface, even switches/routers like Cisco IOS.
Very true. PS is powerful, but totally non-intuitive and not simple. If you use it all day, every day, it would be awesome. But so few people do that. You have to memorize way too many very specific commands. In Linux there are very few (relatively) and BASH itself is super simple (and only has a couple of commands itself like for, do and source.)
-
@coliver said in Linux skills are hard to find:
@Jason said in Linux skills are hard to find:
@coliver said:
Powershell has changed drastically. Every version is different then the previous one. The one thing that seems to remain the same is the awful Verb-Noun commands. Don't get me wrong, the changes are for the better, but they are still fairly dramatic changes.
Not only that.. Linux Bash is easy and logical..
Powershell is not something you can just think of like linux you have to memorize every command because they are not logical or easy to remember at all.
Which does against the nature of any command line interface, even switches/routers like Cisco IOS.
No question there. I will say that the basic commands are pretty intuitive Get-ComputerName is a really easy one to remember. However when you get into things like specific properties and finding properties of a command you will run into issues. Even the Get-Help (Powershell man-like pages) are pretty useless.
Except the correct term is Hostname. So why would I think of putting Computername?
-
@Dashrender said in Linux skills are hard to find:
@scottalanmiller said in Linux skills are hard to find:
OK Powershell I'll give you - I don't recall when it came out though, was it Windows 2000 or Windows 2003? A totally new OS?
Of course a new OS. DOS/Windows was replaced by Windows NT (based on OS/2.) They are fully unrelated OSes other than some slight attempt at a unified look and feel for end users. Nothing similar under the hood in the slightest.
One of the things that UNIX people often point to as a problem in the Windows space is that the Windows community is often unaware of even their own OS and see it only from the graphical perspective and not from the product itself.
Windows 98 was a DOS OS, not Windows NT. Windows NT 3.1, 3.5, 3.51, 4.0, 2000, XP, 2003, 2008, 2008 R2, 2012, 2012 R2 and 2016 are a different OS and OS family entirely from DOS which included DOS 1 - 7.x, Windows 1 - 3.11 WFW, 95, OSR2, 98, SE and ME
You mentioned XP eariler when you were talking about a different OS - so I was starting at XP as the base for the discussion, not DOS or even Win9x. I did know that DOS/Win9x-ME are a different OS from the NT line.
When did I mention that?
-
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Assuming this is your day job, it seems appropriate that work should have some lab space for you to work in to solve work related problems. You should rarely if ever be required to use your own stuff to work out problems like this.
-
@Dashrender said in Linux skills are hard to find:
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Assuming this is your day job, it seems appropriate that work should have some lab space for you to work in to solve work related problems. You should rarely if ever be required to use your own stuff to work out problems like this.
Right, a home lab is for developing skills. For troubleshooting, that's what the work lab is for.
-
@Dashrender said in Linux skills are hard to find:
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Assuming this is your day job, it seems appropriate that work should have some lab space for you to work in to solve work related problems. You should rarely if ever be required to use your own stuff to work out problems like this.
I was just using it as an example and Linux only as we do not currently use a single Linux server here. We do not have a test environment
-
@scottalanmiller said in Linux skills are hard to find:
@Dashrender said in Linux skills are hard to find:
I'm still not entirely sure what makes one Linux OS better than another. Why this one is good for storage, and this one is good for DBs and this one is good for PBXes, etc..
Different kernel models, drivers, features, file systems, support, and such. For example, Suse supports high availability clustering and the BtrFS file system, Ubuntu does not. This alone gives Suse a massive advantage in storage as it has a lot more options. Only some distros support DRBD, also huge for storage.
But, can't you add all of these features to any distro? download the open source, compile and install? Sure, huge PITA, but possible. So it's nice to know that others have already done that with the different distros.
-
@Dashrender said in Linux skills are hard to find:
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Assuming this is your day job, it seems appropriate that work should have some lab space for you to work in to solve work related problems. You should rarely if ever be required to use your own stuff to work out problems like this.
I was going off what @wirestyle22 was saying. He was saying a few guides which lead me to believe this was for personal development more then production.
-
@wirestyle22 said in Linux skills are hard to find:
@Dashrender said in Linux skills are hard to find:
@coliver said in Linux skills are hard to find:
@wirestyle22 Sometimes codes are all that the logs will give you. Then you need to investigate what isn't working or what is working differently then expected. This is where a home lab comes into play.
Assuming this is your day job, it seems appropriate that work should have some lab space for you to work in to solve work related problems. You should rarely if ever be required to use your own stuff to work out problems like this.
I was just using it as an example and Linux only as we do not currently use a single Linux server here. We do not have a test environment
No test environments means it's not really your problem (Windows, Linux or otherwise.) It's the job or your job to provide the tools to do your job, not your job to provide them. If having test and troubleshooting environments is not important to them, it should not be important to you.
