Posted on 02/27/2019 3:25:59 AM PST by ShadowAce
I was a Unix admin for 30 years. It was a fun job. I really enjoyed being able to set up sturdy systems and fixing them when necessary. Even better, it didn’t require me to be a people person.
I love these posts.
Yup--It is my dream job, and I am enjoying every day.
“””The umask masks permissions by restricting them by a certain value.”””
And, people wonder why others are confused by Linux....
Ah, a flashback to my days working on Solaris Unix systems fir a defense contractor. The group settings and permissions were the most critical for us.
I’m not a people person and am trying to automate and remote control everything I can.
BFRL. Thanks for all you’re doing to promote Linux and educate those interested in learning the commands.
You are welcome. If you have any requests or suggestions, I’m open to hearing them.
DILBERT: Uh, Boss. In this memo, I think you meant the company needs more “Unix” admins, not “eunich” admins.
BOSS: Oh! Well, when she comes by, tell the company nurse: “Never mind.”
I should probably add so were the "Other" settings and permissions, but for us, most of those were set to "---".
heh heh
I once was temporarily assigned to an account where the client took away our root privilege because one of our guys f-ed up bad (who I filled in for). When there was a problem, we sat by helplessly until the VP could be tracked down and authorize root. Then they gave us the password. Talk about gelding a Unix admin.
It was a happy day when I returned to my real job.
heh heh
I once was temporarily assigned to an account where the client took away our root privilege because one of our guys f-ed up bad (who I filled in for). When there was a problem, we sat by helplessly until the VP could be tracked down and authorize root. Then they gave us the password. Talk about gelding a Unix admin.
It was a happy day when I returned to my real job.
You do a fine job! I wouldn’t want to suggest a thing to mess it up! :-)
I only have one thing to say about Unix...I don’t get it.
I started coding on a Commodore 128, in BASIC...just for fun. I got pretty good at it.
Then came DOS, and I could get around ok with that, even write some simple apps.
Next came Windows; I played around with Visual Basic, and did pretty good.
Lotus Notes came along, and I became an award winning (from Lotus), and published Lotus Notes developer.
When Notes fizzled, I tried Unix...as they said it was the “up and coming thing”.
I picked up a couple of things, like “grep”, but never really got the thrill of Unix; it was a big step backwards for me, like learning a different kind of DOS.
So, to this day, I still shy away from anything Unix, or Lenox, or whatever.
I’m 73 now and don’t want to strain what’s left of my brain on learning another coding language.
Sorry.
Unix is not a "coding language." It is an Operating System.
It sounds like you had a very rewarding career. Great things to look back on. I hope to be able to do the same one day.
No need to be sorry--we all have our own niches. We're all different parts of the same body.
Unix was designed by counter-culture anti-establishment Berkley hippies in the late 60’s.
It should come as no surprise that those “programmers” would set up default permissions value as 666, and have commands that kill parent and child processes.
At 73 I think you’ve earned a break! :-) Hope you’re enjoying life.
Not to be picky but if you’re going to leave links in the post, you should change them from relative to absolute.
Well, since your premise is incorrect, it comes as no surprise that your conclusion is also incorrect.
From Unix.org:
Since it began to escape from AT&T's Bell Laboratories in the early 1970's, the success of the UNIX operating system has led to many different versions: recipients of the (at that time free) UNIX system code all began developing their own different versions in their own, different, ways for use and sale. Universities, research institutes, government bodies and computer companies all began using the powerful UNIX system to develop many of the technologies which today are part of a UNIX system.
From Wikipedia:
The history of Unix dates back to the mid-1960s when the Massachusetts Institute of Technology, AT&T Bell Labs, and General Electric were jointly developing an experimental time sharing operating system called Multics for the GE-645 mainframe.[1] Multics introduced many innovations, but had many problems.Those are just two sources that refute your premise.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.