Serious question: are (SCO) #OpenServer 6 and #Unixware 7 getting any actual development, or are they just patching enough so they can milk them for a few more years before the last large customers move on to something else?
I had the impression that during the “IBM stole our IP and put it into Linux” suits that both Unixware and SCO #Unix (OpenServer) were mostly on life support after Caldera bought them from old SCO and renamed itself as “The SCO Group”, and that the company was grasping for straws.
Position Summary:
Perforce is seeking a CentOS Support Engineer to join our OpenLogic team (that's my new team, but this is not my specific position), responsible for providing 24x7 break fix support and services on Open Source technologies to our OpenLogic customers. This position will work closely with members from Support, Sales and Professional Services to assist in resolving a wide variety of customer issues. OpenLogic provides enterprise services for hundreds of open source projects — including OpenJDK, Kubernetes, CentOS, and MariaDB — so you can boost efficiency and savings with free software, while cutting risk.
Responsibilities:
Interact with end users on technical problems.
Tier 1, 2 and 3 support for CentOS and related open source products.
Drive resolution of those problems, which include:
Open source software issues.
Questions around #opensource software usage.
Questions around use and best practices.
Review of the architecture and design where software is implemented.
Conduct professional services and training engagements.
Research, understand, and advocate open source software.
Interact with various open source communities.
Drive early resolution of issues.
Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed
Be a part of the on-call rotation.
Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software
Strong knowledge of the Linux kernel and system architecture.
Understanding of software best practices; SDLC, #SCM and Agile development principles.
Ability to develop with C/C++ in a #UNIX environment.
Utilization of common Linux C/C++ build tools such as gcc.
Solid understanding of CentOS 6.x and 7.x and included frameworks like firewalld, systemd, etc.
Strong #RHEL/CentOS background required
#Debian/ #Ubuntu, #SUSE/ #openSUSE/ #SLES, other distro background a bonus
C, shell scripting, #perl, etc
Virtual Machine experience with qemu/kvm, #Azure, #AWS, VirtualBox, #Vagrant
General experience such as: radius/ #Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc)
Excellent written, verbal, and presentation skills
Knowledge of open source packages
Database administration; #postgresql/ #mysql/ #mariadb experience very desirable
Experience with Linux distro package building (#rpm, #deb, ipkg, etc) preferred
Existing contributions to the CentOS community a major plus
#Unix 's "lots of small languages working together" thing would be a lot better if instead of inventing a bunch of languages it was just subsets of a single capable language, so you don't end up with 6 ways of writing strings and never knowing which characters you should escape
hot take: Haskell would make a good EDSL base for this stuff doesn't even have to be too typed, feel free to error everywhere and stuff
Scheme might also be good. Maybe better. But infix operators can be nice.
Requirements:
Bachelor’s Degree in Computer Science or similar or relevant work experience
2 or more years’ experience providing technical support directly to enterprise customers
Knowledge of C/C++ and #Java and experience with #PHP/MySQL
Knowledge of #Unix & #Linux
Basic networking experience
Experience with Perforce, #Git, or other version control software is desirable
Experience in customer support or customer-facing role
Strong analytics and problem-solving skills
Strong debugging skills
Ability to work in a team environment and contribute ideas and improvements
Able to work well under pressure and prioritize accordingly
Responsibilities:
Represent Perforce as the first point of contact for customer’s technical requests.
Review and research customer issues to determine and provide the best resolution.
Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
Resolve database and performance issues.
Research, document, and escalate cases according to procedure.
Provide customer driven feedback to functional areas in order to influence process/product improvements.
Author technical documents on common issues and solutions in order to build the knowledge base.
Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
Create and set up test environments to reproduce and resolve customer issues.
Recreate customer environments to reproduce issues and experiment with possible solutions.
Please pass this along to anyone you think might be interested!
Requirements:
Bachelor’s Degree in Computer Science or similar or relevant work experience
2 or more years’ experience providing technical support directly to enterprise customers
Knowledge of C/C++ and #Java and experience with #PHP/MySQL
Knowledge of #Unix & #Linux
Basic networking experience
Experience with Perforce, #Git, or other version control software is desirable
Experience in customer support or customer-facing role
Strong analytics and problem-solving skills
Strong debugging skills
Ability to work in a team environment and contribute ideas and improvements
Able to work well under pressure and prioritize accordingly
Responsibilities:
Represent Perforce as the first point of contact for customer’s technical requests.
Review and research customer issues to determine and provide the best resolution.
Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
Resolve database and performance issues.
Research, document, and escalate cases according to procedure.
Provide customer driven feedback to functional areas in order to influence process/product improvements.
Author technical documents on common issues and solutions in order to build the knowledge base.
Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
Create and set up test environments to reproduce and resolve customer issues.
Recreate customer environments to reproduce issues and experiment with possible solutions.
Please pass this along to anyone you think might be interested!
@moonshine@georgia I mute alllll the time. I think there's a difference between not being interested in something and wanting to silence someone so nobody else can hear them.
I'm really only on ~~mastodon~~ the Internet for 1 thing: 0) #unix and 1) #gaming
@librelounge great episode! I've been often thought it would be great to develop interpreters that allow users to enter commands and get responses in more natural language. The standard #UNIX CLI was designed for a time when every byte of RAM and hard drive space was a precious resource and I definitely don't want to lose that sense of econony from computing, quite the opposite. But there's no harm in adding trainer wheel layers that make using CLI more like playing a MUD. @cwebber@emacsen
There's benefits to #vim too: it's a small install, light on memory, easy to extend with plug-ins, tried and tested, open source, still actively maintained, millions of users, and it works on #Unix and #Linux distributions alike.
I found a need to install syntax coloring for #rustlang into #vim. An official solution exists, available on #GitHub, in the RustLang repositories. It has good installation instructions. Setting it up was a breeze.
I'm reading about some of the most boring and surprisingly complex #Unix things: #rsyslog
What I want to remark upon isn't so much all of the things rsyslog does but the fact that some guy, for the last 15 years, has nearly single-handedly decided that his life calling was apparently to make sure that we could all have system log files.