Friday May 27, 2011

A bit more on Solaris 11 + SPARC + Sun Ray

A problem I had yesterday lead to a bit more of a writeup in this saga. A gotcha that bit me a few months after the transition and a good story about upgrading to the new Sun Ray software.

More details at Sun Ray on Solaris 11 SPARC.

Monday Mar 14, 2011

Summarising my "Nevada to OpenSolaris Sun Ray on SPARC" series

As previously noted, I finished my series on migrating from Nevada to OpenSolaris Sun Ray on SPARC. There are eight articles on this and it's taken me just under a year, generally trying to find time to work on it.

A lot has gone on in that year. I recognise that "OpenSolaris" is probably the wrong word to be using in the titles, but I'm not going to go back and change it. Please regard the term interchangeable for the purpose of this discussion.

The end result is that I am back running Sun Ray Server on the machine that I originally have nevada on right up until we stopped doing nevada distributions. The machine is running a current Development build and is serving me well.

Anyway, I thought that a small article summarising and linking to each of the posts would be in order and this seemed a good first real article for me back on

  1. Nevada to OpenSolaris on SPARC

    I look at the problems of getting OpenSolaris on to a SPARC Sun Blade 2000 that does not have a dvd reader on it. The end result was to install a late nevada on it and use the wanboot image of this installation to get something onto it. There were a few things which needed tidying up but it worked. I should note that I have subsequently installed Solaris 11 Express onto an Ultra 45 from the install CD, and it went flawlessly. Maybe it would have been easier to find a dvd drive for the box than all these hoops.

  2. Nevada to OpenSolaris on SPARC (part 2)

    I mention some problems I was having with sh returning an Exec format error when trying to do things as myself - the solution to which is outlined here.

    Also show how I migrated the zpools to the temporary machine.

  3. Nevada to OpenSolaris Sun Ray on SPARC (part 3 - reboot)

    Disaster strikes. My lab booking ran out and someone re-installed the box meaning I had to start from scratch. This blog is probably a much better technical reference for all that I had done before (isn't it always the way that when you have to do something over again, you manage to do a better job?).

  4. Nevada to OpenSolaris Sun Ray on SPARC ( part 4 - imapd)

    Everything I had to do to get imapd running. Starting with installing the compilers, downloading the source code, working out the Makefile hacks to make it build, making the SSL certificates (oops I have to do that again now I am on a machine with a different name).

  5. Nevada to OpenSolaris Sun Ray on SPARC (part 5 - Sun Ray Server)

    Step by step of getting around dependencies of Solaris 10 inside the Sun Ray software to get it running on this box. As I say at the end of the article ,"Getting Sun Ray running like this OpenSolaris completely voids any warranty and support. Don't do it if you don't know what you are doing."

  6. Nevada to OpenSolaris Sun Ray on SPARC (part 6 - cutting over)

    Smoke test time. What happened when I cut over to trying to do my day job on this machine. I realised I had missed a few things that were important, like openoffice, flash and acroread. The entry details the installations and also about installing certificates for the extras repository.

  7. Nevada to OpenSolaris Sun Ray on SPARC (part 7 - printing)

    Details how I got CUPS up and running. I believe that Solaris 11 Express comes with all of the packages already installed so you only need to configure things.

  8. Nevada to OpenSolaris Sun Ray on SPARC (part 8 - back to the original hardware)

    The last installment on moving everything back to the original machine, as I really did not want to be tieing up a lab resource (though I had it booked for close to a year), and vesvi actually had a little more memory in it.

    I cover some gotchas in using cloned disks like this as well as how I ended up doing it, how to change a nodename now as well as a couple of local network gotchas that had me confused for a while.

Going back through this I realise that I may have left out configuring a couple of packages, like MySQL. I may do a final part 9 to cover these once I've made a list of them and I'll add that to here too.

Tuesday Mar 29, 2005

Solaris Express 3/05 available March 29

Just saw the note saying that it will be available on Tuesday. As in the February build, Solaris Express is based on the current development code, currently called Nevada). This release is based on build 9.

You will now start to see bug fixes going into Nevada prior to backporting to the released versions of Solaris.

The mozilla issue is still there. This was fixed for build 10 so should be fixed in the following release.

Some of the new stuff this month includes

  • New plockstat arguments - see plockstat(1M) for -e, -n count, -v and -x.
  • New lockstat argument - see lockstat(1M) for -x.
  • Network Layer 7 Cache - completes the integration of the Network Cache Accelerator into the kernel by porting it's HTTP layer and object cache into sockfs.
  • Kernel level atomic operations - see atomic_ops(9f).
  • Added functionality to poolbind to execute a given command bound to trhe named pool (see poolbind(1M), specifically -e.

Technorati Tag:

Tuesday Mar 01, 2005

Fixing Mozilla on Solaris Express 2/05

I mentioned the other day that there was a well used script that does not (yet) deal with uname -r returning 5.10.1.

You guessed it, the script in question is /usr/sfw/bin/mozilla.

The bug1 has the effect that if you double click on the mozilla icon, nothing happens. If you try to run mozilla, you get it telling you:

    Mozilla 1.7 requires Solaris 8 or later

Fortunately this is pretty easy to fix.

On lines 217-218 of /usr/sfw/bin/mozilla, you will see the following:

        case "$OS_VERSION" in
        "5.8" | "5.9" | "5.10" ) ;;

Simply change this to read :

        case "$OS_VERSION" in
        "5.8" | "5.9" | "5.10" | "5.10.1") ;;

I believe the real fix will be to remove this code entirely and has been done for build 10.

Technorati Tag:

1. 6212965 mozilla needs to understand uname -r returning 5.10.1 for nevada

Thursday Feb 24, 2005

Solaris Express 02.05 (snv_07) available on February 28

This is the new development version (beyond Solaris 10), based upon the Nevada source tree.

You will note that uname -r will return 5.10.1, so if you have programs that compare against this output you may need to make the aware of this micro release. There is at least one script that I know of for which there is a pending bug that is affected like this. I'll post some more on how to deal with that particular script once I see what we are going to say about it in the release notes.

New Features

  • Support for iCSSI Devices
  • Fibre Channel HBA Port Utility (32-bit x86 only)
  • Metaslot in the Cryptographic Framework
  • IKE Enhancements
  • X.Org Release 6.8.2
  • Chelsio 10G Ethernet Driver (chxge)

Technorati Tag:

Monday Jan 10, 2005

Serverwatch give Solaris 10 (Beta 72) four stars out of five

Serverwatch put up a brief summary of their review of Solaris Express.

Looks like did pretty well overall, and perhaps would have done better if not for the reviewers belief that you could not install it with other Operating Systems.

Version10 (Beta 72)
DateJan 05, 2005
(out of 5)
64-bit AMD processor support, x86
processor support, containers, DTrace, and
process rights management
DescriptionSun's industrial-strength Unix for the Sun
SPARC platform
Product is free, but support must be
CompanySun Microsystems

I'm not quite sure about why that last link points to the trusted Solaris homepage, but Oh well. The description looks like it may have been a cut and paste as well as the article discusses x86 and opteron.

Friday Jan 07, 2005

Solaris Express after the Solaris 10 release

I've been asked a few times about what is happenning with Express. There was no release in December and nothing had been heard about January.

Well, ...

Solaris Express 11/04 was build 72 of Solaris 10. We will be releasing Solaris 10 (build 74L2) on January 31. As such it looks like there will not be a Solaris Express this month either. We get back into the swing of Solaris Express with 2/05, where we will continue to make the Solaris development work available.

You should look forward to seeing such things as Janus and ZFS in the not too distant future, along with some more new stuff.

In the mean time, Solaris Express 11/04 is available and Solaris 10 will be released on January 31.

You should also be keeping an eye out for announcements about .

Wednesday Nov 24, 2004

Solaris Express 11/04 is coming

The decision has just been made (inside the last hour). Solaris Express 11/04 will be build 72 and should be available on or around November 30.

The big thing for this one is...

64 bit Solaris on AMD.

Other enhancements include...

  • Webmin
  • Intelligent Platform Management Interface - implementing IPMI. IPMI is an x86 industry standard for remote sensing and lights out hardware management.
  • The new login screen and logo (had to get that in)
  • Apache Version 2

There are also enhancments to...

  • Dtrace (which I'm sure that Adam will discuss)
  • System V IPC and Other Resource Controls
  • New and updated drivers (e.g. support for the S2io Xframe 10gb ethernet adapter)

As usual, the documentation will be available for free at

I found that some of the changes meant that I had to address a problem in the bcf driver in order to get my network working (and nort panicing the notebook. I'm communicating these back to Murayama-san.

There's more in here than what I have listed, these are just the initial highlights. I'm sure that others will make their own highlights lists shortly (I may even add some more myself later).

Enjoy Folks.

Friday Nov 19, 2004

Reply to a reply on slashdot "Linux - Sunisms debunked"

There was a reply to a story on slashdot about the Solaris 10 launch that I felt I could supply some answers to. I'm not Scott or Jonathan, but I can certainly speak to some of what you ask.

Shoot your marketing department. (Score:5, Interesting)
by Soko (17987) Alter Relationship on Friday November 19, @01:26AM (#10862308)

At the end of the launch event Jonathan Schwartz made an impromptu speech; I didn't hear most of it, as I was too far away, but he did end his comments with something about Slashdotters. I ambled over to Schwartz and said, "If anyone here is going to get an article onto Slashdot, it's probably going to be me (since NewsForge and Slashdot are both part of OSTG). Tell me what you'd like Slashdot readers to know."

"Tell them that we're returning to our roots," Schwartz said, referring to the company's renewed focus on the Solaris operating environment.

"And we want developers back on our side. If there's more for us to do, we'll go do it," McNealy added. It was the first time all day that I felt that the two had broken character and simply told me what was on their minds.

As a long time Slashdotter who has had to use and deploy Solaris on occasion, let me tell Mr. McNealy and Mr. Scwartz what's on my mind about Sun. I know they'll be reading, so here goes:

First, cut the marketing BS. No press wars with Redhat, IBM or HP. No trumped up, spin laden press releases about Solaris 10. I don't even want to see a comaprison paper. Give me a technical white paper about what the OS can do and STFU - I then can see for myself whether Solaris 10 is a good or great OS. I can also then decide for myself if it's a good fit in my architecture. Most on Slashdot are technically adept - that's why we can run and support Linux or \*BSD without Redhat's help. It's the PHBs who require that kind of hand holding, not us. (Hey, I just invented a new comic book villian - Spin Laden, the Marketing Terrarist!)

The problem is that your's is only one of the opinions out there. We also have folks screaming for comparisons. What you also need to realise is that Sun is a for profit company. So is RedHat. Companies compete. Sometimes it looks ugly. On this particular issue, Jonathan has been misquoted so many times as equating Linux with RedHat. This is the case being put by those who are not reading all of what he is saying, or simply don't want to understand it. We most certainly do not equate the two. What we are getting at is that a lot of the commercial world do, and RedHat does very little to discourage this as it directly impacts their income (companies try to make money). Large shops want to have the third party vendors support their product on the platform that they deploy. Generally in the Linux world, the vendors qualify RedHat. As the RedHat execs joked about at the shareholders meeting, this qualification process can be expensive (up to around $4 million I think was quoted from memory), so it's not done for a lot of distributions.

I like the name Spin Laden :)

Open your dev process, as well as your code. I don't (necessarily) mean provide CVS access, I mean accept and credit quality patches to the code base. Open code would mean we can fix our own damned stuff when things in Solaris break and get our jobs done, while benefiting anyone else who has the same bug - we tend to like to share the fact we're smart enough to repair someone else's broken code. For large contributions, pay the contributor and pay him well.

This one I can say something I think you'll like. The development process is part of what is being opened up as a part of the open sourcing. It's also one of the issues being discussed in the pilot. I believe that one of the presentors mentioned that at the event, but don't recall who off the top of my head (probably Jonathan though).

Stay away from the rest of my systems unless I ask you in. No embedded Java in the OS, no Sun only core stuff (think Microsoft and Kerberos 5), just a big box of properly impelmented tools that I can use to make systems work, work well and work reliably. Your products will be sharing my network with other vendors, so play nice whenever you can. If that means re-writing some Solaris code to put into linux so it interoperates properly and GPLing it, so be it. That way I know that you're concerned about me and not just "maximizing value".

Sun's history is of playing nice with the other vendors. In fact we go out of our way to write to the open standards. I'd be interested in hearing you expand on this paragraph, as I'm not really clear on exactly what it is you are wanting us to do (seriously I am).

Contriubute to the industry. Some of us think RMS is a real looney, but we have the utmost respect him and his contributions. Mr. Gates, IMHO, does not contribute to the general cause or making my life easier unless there's a price tag, be it in dollars or having to shut out one of his colleagues - he calls them compeditors - from my architecture. Real contributions move the whole industry forward, and provide new opportunities for everyone to make a little $_CURRENCY, not just a select few.

In what way are we not contributing to the industry? We have a lot of folks working with projects like GNOME, X.Org, Mozilla, Open Office. We are the largest commercial contributor of code to the Open Source movement. We're opening the crown jewels (Solaris), what more would you have of us?

Censure that person who 'escorted' out the interviewer. We like plain talk. We know you have fiduciary responsibilities, and most of us try to take those into account, but trying to hide what you really want to say doesn't wash. If you hate linux or love it, say so, and say why - with no spin on the matter. Speaking of plain talk, you'll get some from us. We know you're the head of a big, powerful Corp., but you should be willing to learn from us. When it comes to putting the tech on the floor, we are your betters, not your underlings.

On the escorting out, I have to agree with you on. For goodness sake, the guy was talking with the COO of the company at the time. A little patience and tact surely would not have been too difficult.

We certainly are willing to learn from and listen to our users and customers. Part of the problem of speaking with no spin, is that it will still be read as if we are spinning, so that leaves us looking worse than we want to project. Folks get cynical of companies. If you want to read about what we are doing without the marketing spin, straight from the engineers, I can recommend

I'd prefer to think that we are closer to equals when it comes to the tech stuff. We can all learn from each other. That's part of the reason we are open sourcing Solaris. It would be arrogant to say that we have all the best engineers and nobody outside could possibly contribute anything of worth. In reality, we have some damn good engineers, but there are also folks external with great ideas and skillsets.

Lastly, put your engineering department off limits to marketing personnel. OFF-LIMITS. Spin Laden should be shot on sight (by a Nerf gun, of course) if he dares tread where something cool is being made. No "That's a killer system, and we can leverage it to sell..." baloney please. I'm still loathe to implement AD because it's actually proprietary technology, even though it would make administrating my network a little easier.

When marketing doesn't talk to the engineers, we see things like ZFS being renamed to Dynamic File Service. I'd rather at least keep up some conversation with them. Like I said, if you want to see what we are talking about without the marketing spin, check out the engineers blogs.

Thanks for tuning in to my little rant. HAND.

Hey , if no-one rants, we don't find out about the concerns. I even had my own little rant the other day (read further down the blog if you're interested

Wednesday Nov 17, 2004

And here comes the Solaris 10 FUD from HP

Not even a day after the launch and already the FUD starts to flow. One recently brought to my attention was Martin Fink, at Martin Fink is HP's Linux Vice-President.

Martin takes it on himself to inform folks about what Sun is not telling about Solaris 10/x86.

I'll try to correct some of his misperceptions. The headings are below are Martin's. I won't quote the actual article, you can read it in his blog.

Is it really Solaris?

Martin's argument here is that because SPARC is big-endian and x86 is little-endian, and that applications compiled for SPARC will not run on x86, that it can't really be Solaris.

Sun has never claimed binary compatibility across different chip architectures (as against our claim of compatibility across multiple releases of the OS). I suspect Martin would be surprised to learn that Solaris on SPARC and Solaris on x86 are actually built from the same source tree... (you know, kind of like Linux for x86, linux for SPARC, linux for ...).

He also makes a comment about moving data between Solaris SPARC and Solaris x86. I can only assume that he means physically moving disks as folks have been shipping information across networks for ages. Yes, if you try to move a disk with a ufs filesystem on it between the two architectures you will run into problems. However, ZFS is endian-neutral, so that problem goes away.

Is it really open?

Martin states that Sun has only ever talked about open sourcing Solaris on x86. Didn't I already mention that Solaris is built from the same source tree? It's going to be both.

While we have not decided on the actual license we will be using (which would explain why we have not announced it), there is commitment that the license will be OSI compliant.

Why I don't think SUN will use the GPL

As I've already stated, OSI compliant. The GPL is not the be all and end all of open source licenses. It may be what we go for, it may not. We don't know yet. As such I can't really offer a lot of comment here, but he's certainly entitled to his opinion.

Who can check-in code?

Unfortunately I'm involved in some of the discussion on this so there is not a lot that I can say, except that we would look pretty silly if we were to call it open and not allow external check-in to the open source code.

Linux inside; Well, maybe

Martin treats project Janus as an admission that there are more linux applicatoins out there than there are solaris applications. And this is news how?

It would be pretty arrogant not to acknowledge that there are some good linux applications out there that have not been built for Solaris. OK, so if we run these under Janus, we get the hardening that is Solaris as well as all of the cool stuff in 10 with regards to observability of tools like DTrace.

What we also get is server consolidation. Think about multiple instances of Janus inside Zones running on something as beefy as a V40Z; along with running your Solaris applications as well. Oh yes, you could also factor in the resource manager as well for sharing out the zones in a fair and predictable manner. Certainly sounds interesting to me.

Is Janus Indemnified?

Mu. That is, the question does not make sense.

We have not built a clone of a linux kernel, we have written to the kernel API. All of the code is our own. Indemnification does not enter into it.

Applications need developers

He continues to harp on about the admission of more applications available for linux here and tyhen goes on about how linux now has a collection of more than 9000 developr tools on freshmeat and another 12000 under development. I don't know about you Martin, but thats a few too many for me. We and a lot of third parties have been developing for Solaris for a long time. We're pretty happy with our toolset. You may not have noticed, but a lot of the tools that are made available for linux also actually compile and work under Solaris (there's a shock, hey!).

He asks where the applications for Solaris are going to come from. Hmmm OK, off the top of my head how about we start with Oracle, Sybase, Veritas and Siebel. There's a lot more, but I don't have a list handy.

Where will the developer community come from?

Martin claims that there is no developer community for Solaris. Martin, you are sadly mistaken.

You only have to look at places like for a single example of this.

What problem is SUN trying to solve?

Martin makes some good points in here about what opening up code can achieve, however he is still under the delusion that Sun intends to control the codebase. Again he tries to say that Solaris SPARC and Solaris x86 are two entities. Didn't I already point out that Solaris is built from the same source tree?

And who says we are trying to turn Solaris into Linux?

I would have thought that many of the benefits that he has already mentioned would be sufficient. We also know that there are folks out there who want to work with Solaris. The feedback we are seeing in the pilot programme certainly confirms this.

Ah, but what about TCO

In this topic, Martin questions the sustainability of Sun's Solaris pricing plan. What he overlooks is that Sun is more than an Operating System company. Sun also sells hardware, support, middleware and applications. He again flogs the dead horse about Solaris SPARC and Solaris x86 being two different beasts. Do I have to say it again? They are built from the same source tree.

He also speaks about server shipments from various companies and how we compare, again questioning Sun's viability. I won't go into depth on the figures, it's a huge paragraph. One thing I will mention though is that there already in excess of a million Solaris x86 licenses out there. Our demise has been predicted more than a few times in the past 23 years. Guess what? We're still here.

He asks how many people are interested in running Solaris on x86 hardware. You only have to go back to when we deferred Solaris 9 to answer that one. The backlash was incredible.

In the end

I could say that if Martin doesnt understand our strategy, then that's good for us and bad for HP. I think the main point that Martin has missed is that Sun is not an OS company. We are not a server company. We are not a storage company. We are not an applications or middleware company. We are a Solutions company. Unlike most of our competition we can provide a soltion from the hardware, through the kernel and middleware up into user space. We also don't have to pay anyone in order to provide it, as we own the IP. OK, A customer doesn't want to run on SPARC Solaris or x86 Solaris, why should we then not sell them hardware that is capable of running Linux or even (shock horror) Windows?

In a way I guess it's predictable that the FUD has already started. I have faith that those who make the real decisions can tell the difference between FACT and FUD.


I mucked up the url for blastwave when I saved this. It's right now.

Tuesday Nov 16, 2004

Sun, Solaris, Open Source and Slashdot

At the moment I keep getting the following message whenever I try to post to slashdot.

Sorry, but according to our tests, you are trying to post from an open HTTP proxy. Please close the proxy or ask your sysadmin or ISP to do so, because open proxies are used to spam web boards like this one.

If you have questions, mention that your proxy is at XXX.XXX.XXX.XXX on port 8080.

I mailed Cowboy Neal, but have not had a response on this.

I do hope they fix this soon. I don't believe we have an open proxy, what we have is a proxy with around 33000 people behind it.

Anyway, here is the response that I was trying to make to Solaris 10 Released, Updated & Free (Like Speech).

I find the bashers who claim that Sun is going to play a bait and switch with Open Sourcing Solaris a continuing amazement.

There is a commitment from Jonathan and from Scott that Solaris will released under an OSI compliant license. That's a pretty clear statement.

I am one of the engineers taking part in the pilot. The pilot is coming along nicely and there is a lot of good discussion going on. There are things that are still being ironed out, but progress is being made, and its not just internal folk.

The thing that won't surprise me is that when it does get released as advertised, is that the foksk who are bashing now are not going to come out and say "Oops, guess I was wrong". But that's slashdot.


Looks like it is just one of the Sun proxies that slashdot doesn't like. Strange. I managed to post against the article now.

Thursday Oct 28, 2004

Sun Education has a DTrace Course Available

How about that? For anyone who wants to do some training, Sun Education is running a two day course titled

Dynamic Performance Tuning and Troubleshooting with DTrace

The course code is SA-325-S10, and you can find out more about it at the Sun Education site.

The course content as listed on the site is...

Module 1: DTrace Fundamentals
  • Describe the features of DTrace
  • Describe the DTrace architecture
Module 2: Using DTrace
  • Examining performance problems using DTrace
  • Use DTrace to obtain information about system calls
  • Create D Scripts that Use Arguments
Module 3: Debug Applications with DTrace
  • Use DTrace to profile an application
  • Use DTrace to access application variables
  • Use DTrace to find transient system call errors
  • Use DTrace to determine the names of files being opened
Module 4: Finding System Problems with DTrace
  • Use DTrace to access kernel variables
  • Use DTrace to obtain information about read calls
  • Use DTrace to do anonymous tracing
  • Use DTrace to do speculative tracing
  • Explain the privileges necessary to run DTrace operations
Module 5: Troubleshooting DTrace Problems
  • Describe how to lessen the performance impact of DTrace
  • Describe how to use and tune DTrace buffers
  • Debug DTrace scripts

Tuesday Oct 26, 2004

Solaris Express 10/04 is coming

Solaris Express 10/04 (s10_69) should be available for download around October 29!

Some of the new features for the release include:

  • Solaris Service Manager(Greenline)
  • JDS Release 3
  • Oban (Solaris Volume Manager for SunCluster)
  • Ipsec/IKE NAT traversal
  • OpenSSL and PKCS#11 for OpenSSL
  • Hardware Random Number Generation support
  • Failed Account Login Account Locking
  • Track Uptime across reboots
  • Solaris 1394 Mass Storage Driver-x86
  • Remove Netscape4.7xin Solaris \*Mozilla 1.4 removal
  • Xorg replaces Xsun as the default X server on x86
  • DTrace USDT (User-land Statically Defined Tracing) and plockstat Provider
  • New Realtek NIC driver

As usual, the documentation will be available at

Greenline and the Xorg transition are likely to cause a little frustration. Greenline because it is such a complete mindset change, and Xorg in getting the configurations correct. I am expecting to see some of the respective engineers blogging on at least these two over the next few weeks.

Sunday Oct 17, 2004

Two new articles in On#Sun

This issue I have two articles in On#Sun.

Why are Sun engineers so excited about Solaris 10?

Part 1 of a two part article briefly discussing some of the reasons why we are exited. In this part I touch on

  • Fire Engine
  • DTrace
  • Zones
  • KMDB

It was going to be a larger one part article, but after writing it I was informed of a two page limit and had to break it up.

Open Solaris

Hopefully answering some of the questions that folk have been asking on the topic.

On a side note, isn't it funny how they can get the spelling of your name right in one article, but not in another; in the same issue!

Friday Sep 17, 2004

Notebooks (and other uniprocessors) get power-off in Solaris 10

A putback notification I've been waiting for for quite a while now happened yesterday.

The uppc driver (uniprocessor) now has ACPI power-off functionality. It will appear in build 69.

I just run an update onto my Dell Inspiron 8500 and it works fabulously.

I can now just type

# init 5

just before getting off the train, pack the notebook up into it's back and be assured that it will actually power off without me having to hit the power button.

Thanks Andrew Gabriel for doing the work on it.


* - Solaris and Network Domain, Technical Support Centre

Alan is a kernel and performance engineer based in Australia who tends to have the nasty calls gravitate towards him


« October 2016

No bookmarks in folder

Sun Folk

No bookmarks in folder

Non-Sun Folk
Non-Sun Folks

No bookmarks in folder