Language Selection

English French German Italian Portuguese Spanish

Secret life of the OpenSolaris code

Filed under
OS

OpenSolaris community manager Jim Grisanzio told ZDNet Australia the code had been relatively free of profanity even before Sun filtered it prior to release. "They went through the code for a great many things," he said, "and I'm sure they cleaned a word or two. Or three."

"But you know, when I got involved in this project last year, even at that time, no one was worried about any comments in the code. Maybe we have clean engineers, I don't know, but for the most part I've heard it's pretty clean."

A cursory search through the code revealed almost a complete lack of commonly-used profanity. This is in contrast with other examples such as the leaked Windows 2000 code and the Linux kernel project -- which are famous in coding circles for the number of rude words programmers have included in an adult-rated effort to describe how a particular portion of the code works.

But the OpenSolaris code is not entirely clean. "This is an ugly PCMCIA hack - ugh!", wrote one developer in the comments section of his code.

Another was realistic about his coding confusion. "Couldn't find the damn thing," he said.

"The following cast 'makes it all work'. Yes, it's ugly," admitted a third.

The much-vaunted dynamic tracing (dtrace) feature of Sun's system may not be as safe to use as most people think.

"This bit me in the ass a couple of times, so lets toss this in as a cursory sanity check," wrote one careful developer in the dtrace section.

Another tried his hand at predicting the future of system speeds. "As of this writing (1996) a clock rate of more than about 10 kHz seems utterly ridiculous, although this observation will no doubt seem quaintly amusing one day," he wrote.

Religion was a common theme in the code. "Oops, did not find this signature, so we must advance on the next signature in the SUA and hope to God that it is in the susp format, or we get hosed," said one developer.

"God help us all if someone changes how lex works," wrote another. "Oh God, what an ugly pile of architecture," moaned a third.

However, the real potty-mouths appeared to be open-source developers whose software made it into the OpenSolaris release in the form of the Perl and GRUB projects.

Full Story.

More in Tux Machines

Linux Foundation: New Members, Certifications and Microsoft Entryism

ETSI/GNU/Linux-based MANO

  • ETSI Open Source MANO announces Release FOUR, moving faster than ever
    ETSI is pleased to announce the availability of OSM Release FOUR. Bringing a large set of new features and enhancements, this version is the most ambitious and innovative OSM Release to date and constitutes a huge leap forward in terms of functionality, user experience and maturity. This new Release brings substantial progress thanks to a number of architectural improvements, which result in a more efficient behaviour and much leaner footprint – up to 75% less RAM consumption. Additionally, its new northbound interface, aligned with ETSI NFV work, and the brand-new cloud-native setup, facilitate OSM’s installation and operation, while making OSM more open and simpler to integrate with pluggable modules and external systems, such as the existing OSS.
  • Open Source MANO Release FOUR lands
    In monitoring, ETSI says OSM Release FOUR's alarm and metric settings are easier to use, and a new policy manager adds push notifications and reactive policy configuration, which the standards body says “opens the door to closed-loop operations”. The monitoring module uses Apache Kafka as its message passing bus, and the module also implements a flexible plugin model so sysadmins can BYO monitoring environment.

today's howtos part 2

Programming: GitLab, Security, Power and Jakarta EE

  • GitLab 10.8 open sources push mirroring
    GitLab 10.8 was released this week with the open sourcing of a highly requested feature. The company announced its push mirroring capability is now open sourced. Push mirroring was originally introduced as a paid feature, but GitLab says it is one of the most frequently requested to be moved into the open-source codebase. This move will add a few new use cases for GitLab Core users, such as freelance developers being able to mirror client repos and users migrating to GitLab being able to use push mirroring to ease the migration path.
  • How Security Can Bridge the Chasm with Development
    Enhancing the relationships between security and engineering is crucial for improving software security. These six steps will bring your teams together. There's always been a troublesome rift between enterprise security teams and software developers. While the friction is understandable, it's also a shame, because the chasm between these teams makes it all the more challenging to build quality applications that are both great to use and safe.
  • Which Programming Languages Use the Least Electricity?
    Can energy usage data tell us anything about the quality of our programming languages? Last year a team of six researchers in Portugal from three different universities decided to investigate this question, ultimately releasing a paper titled “Energy Efficiency Across Programming Languages.” They ran the solutions to 10 programming problems written in 27 different languages, while carefully monitoring how much electricity each one used — as well as its speed and memory usage.
  • How Java EE found new life as Jakarta EE
    The title of this post may seem strange, but if you look a bit into Java EE's recent history, it will make sense. Originally, Sun started and ran Java Enterprise Edition, and later Oracle took over after it acquired Sun. Specifications were driven by a Sun/Oracle-governed process. At more or less regular intervals, they made a new version of the specification available, which was implemented by the server vendors. Those vendors had to license the technology compatibility kits (TCKs) and brand from Oracle. Let's fast-forward a bit. In 2013, Java EE 7 was released, and Oracle began work on EE8, but it did not progress quickly. Meanwhile, new technologies like Docker and Kubernetes came along and changed the way applications run. Instead of running a single fat server process on a big machine, the software is now split into smaller, independent services that run in a (usually) Docker container orchestrated by Kubernetes.