Skip to main content
replaced http://serverfault.com/ with https://serverfault.com/
Source Link

I noticed the Jeff Atwood close this server fault question for not being sysadmin realted: Linux Source CodeLinux Source Code

"...am looking for the source code to learn about their working in Linux for all the common commands which we use in our day to day life like cal, su, sudo, ls -l, dir, pwd etc. where really does the source code for these commands present in linux distributions? ..." ...

I respectfully, but strongly, disagree with closing this question for that reason, and I feel he might have touched a sensitive topic that might alienate Linux Administrators. I think having access to the source code is a fundamental part of the whole Linux / Open Source culture, even as an Administrator.

Part of troubleshooting ( administering ) you can look at the source code of the kernel, common utilities, and servers ( such as Apache ). It is also part of how and Administrator might learn more about Linux to be more effective at their job.

I have never had an interview where I haven't been asked about if I am familiar with compiling source code (and configuring compile options) for Linux. I may have also been asked how to get the source code -- I can't remember for sure.

I think this maybe different from the general scope of being a Windows Administrator, but not the scope of being a Linux Administrator. My question for the other Linux Administrators is if they more or less agree with this, and what their arguments might be for or against this.

I noticed the Jeff Atwood close this server fault question for not being sysadmin realted: Linux Source Code

"...am looking for the source code to learn about their working in Linux for all the common commands which we use in our day to day life like cal, su, sudo, ls -l, dir, pwd etc. where really does the source code for these commands present in linux distributions? ..." ...

I respectfully, but strongly, disagree with closing this question for that reason, and I feel he might have touched a sensitive topic that might alienate Linux Administrators. I think having access to the source code is a fundamental part of the whole Linux / Open Source culture, even as an Administrator.

Part of troubleshooting ( administering ) you can look at the source code of the kernel, common utilities, and servers ( such as Apache ). It is also part of how and Administrator might learn more about Linux to be more effective at their job.

I have never had an interview where I haven't been asked about if I am familiar with compiling source code (and configuring compile options) for Linux. I may have also been asked how to get the source code -- I can't remember for sure.

I think this maybe different from the general scope of being a Windows Administrator, but not the scope of being a Linux Administrator. My question for the other Linux Administrators is if they more or less agree with this, and what their arguments might be for or against this.

I noticed the Jeff Atwood close this server fault question for not being sysadmin realted: Linux Source Code

"...am looking for the source code to learn about their working in Linux for all the common commands which we use in our day to day life like cal, su, sudo, ls -l, dir, pwd etc. where really does the source code for these commands present in linux distributions? ..." ...

I respectfully, but strongly, disagree with closing this question for that reason, and I feel he might have touched a sensitive topic that might alienate Linux Administrators. I think having access to the source code is a fundamental part of the whole Linux / Open Source culture, even as an Administrator.

Part of troubleshooting ( administering ) you can look at the source code of the kernel, common utilities, and servers ( such as Apache ). It is also part of how and Administrator might learn more about Linux to be more effective at their job.

I have never had an interview where I haven't been asked about if I am familiar with compiling source code (and configuring compile options) for Linux. I may have also been asked how to get the source code -- I can't remember for sure.

I think this maybe different from the general scope of being a Windows Administrator, but not the scope of being a Linux Administrator. My question for the other Linux Administrators is if they more or less agree with this, and what their arguments might be for or against this.

Post Migrated Here from meta.stackexchange.com (revisions)
Source Link
Kyle Brandt
Kyle Brandt

Linux Source code Closed Question closed on Serverfault

I noticed the Jeff Atwood close this server fault question for not being sysadmin realted: Linux Source Code

"...am looking for the source code to learn about their working in Linux for all the common commands which we use in our day to day life like cal, su, sudo, ls -l, dir, pwd etc. where really does the source code for these commands present in linux distributions? ..." ...

I respectfully, but strongly, disagree with closing this question for that reason, and I feel he might have touched a sensitive topic that might alienate Linux Administrators. I think having access to the source code is a fundamental part of the whole Linux / Open Source culture, even as an Administrator.

Part of troubleshooting ( administering ) you can look at the source code of the kernel, common utilities, and servers ( such as Apache ). It is also part of how and Administrator might learn more about Linux to be more effective at their job.

I have never had an interview where I haven't been asked about if I am familiar with compiling source code (and configuring compile options) for Linux. I may have also been asked how to get the source code -- I can't remember for sure.

I think this maybe different from the general scope of being a Windows Administrator, but not the scope of being a Linux Administrator. My question for the other Linux Administrators is if they more or less agree with this, and what their arguments might be for or against this.