PRK recovery – week 4.

The last (two) weeks have been up and down. The nurse surprised me during my last exam when the eye I thought was my fuzzy one was actually better than my ‘good’ eye. Expect lots of that. An eye will be good up close for a couple of days, then distance is better. What is awesome is terrible 48 hours later.

I ran out of steroid drops on the holiday first thing and only got drops in one eye. KU Eye Med (the clinic I had the procedure done at) was apparently closed. It took over 24 hours to get refill drops. It could have just been in my head but my vision appeared to regress significantly. I got the drops back in mid-afternoon and throughout the evening my vision appeared to improve. Distance is still pretty fuzzy but it’s doable.  The most obnoxious part – one eye is sharper than the other at times, right? Prepare for headaches as your brain is angered at the processing changes.

There was a point today when I was driving and I couldn’t read the text on signs until they were closer than I would like where I began to wonder if something was wrong. Then I remembered my vision immediately after the surgery. Hold onto that memory. You will have nearly that level of clarity again. Focus will come and go until the outer layer is fully healed, nothing is wrong at this point.

Spacewalk cluster with self-signed certs.

Spacewalk has a lot of options. There’s a lot of good docs out there by the default docs are somewhat hard to follow. This post is intended to be a framework to create a self-signed CA (or use a third-party CA and skip the self-signed portion), and then apply the root CA cert to the entire cluster simplifying configuration. If you go self-signed, you’re definitely going to want to create the CA certs.

For the purpose of this post, we’re making a master and slave configuration with proxies.

Wewt. We have our signing key. Time to sign some certs. For this post we’re going to have 7 servers: – the spacewalk master server. – These are the spacewalk portal/slave servers. These will pull packages and channels from the master server. – These are the Spacewalk proxies. Each of these sits in front of the Spacewalk slave and caches packages.

A quick note on how this configuration works. The master server pulls in packages and assigns them to channels (repos.) The slave servers sync content with the master. Errata is assigned to the slaves and tied to channels, and packages in those channels. You can run servers directly against the slaves or master, but it can be tipped over under heavy load. The proxies use Squid to cache packages offloading much of the work but otherwise are just relays.

On relays, there’s two basic forms of package management. OSAD, and RHN. OSAD uses a HTTP keepalive sessions from each client to the SW server to allow for pushes. It’s very handy, but it can be a pain to maintain with a large number of clients. RHN is the other method. Each server will check into the proxy/slave/master every 60 minutes by default and see if there are commands queued.

Back to the build. We’re going to make some client certs, then sign them.

Now we have ssl certs for each of the servers in this cluster. Copy them over to each server. The structure of the directories on each server will need to be this:

This imports the cert into the Spacewalk application. Lets create the RPM for the CA, and each server:

Substitute proxy.c.slave for each of the hostnames listed previously. There will be 7 total here. Validate that each cert matches:

If there are any problems, recreate, or resign the certs.

Now that we have the actual SSL certs, lets start applying them. Spacewalk has tools that creates RPM’s for the CA (/root/RHN-ORG-TRUSTED-SSL-CERT) and also the certs.

There’s an additional step on the slaves, and the master:


On the proxies:

There’s some basic management needed next and good guides out there for that stage of things. At a minimum, you need to go into the slave servers and add the proxies, grant them access to any wanted channels and make sure that they have a provisioning entitlement.

On each client to connect to these servers:

This took a lot of piecing things together. It’s not really complex and there’s some good guides out there but it’s hard to get everything working from end to end.

PRK recovery day 8-14

There was a brief window between days 8 and 11 where I had ghosting (a double-image) as the left eye caught up to the right one in terms of being able to see. With that came quite the headache as my brain tried to process out-of-sync information. That cleared up fairly quickly.

Not a lot of changes here. My left eye has gradually caught up with my right one. I still see ghosting in my right eye a little but but the haze is completely gone. Down to a few drops of the steroids a day along with tons of drops. (Did I mention to get them at Costco? They’re a steal there.)

Testing today the eye has been completely healed. I can now take showers again. That will probably be the most enjoyable shower I have ever had. The doctor said one thing that was interesting – the surface of the eye is the holdup for clarity. Even though the flap has closed it’s still rough causing a slight bump. They noted that I was ahead of the healing curve but that I was sitting at 20/20, and 20/15 respectively and things have not cleared up yet. I attribute the accelerated healing to luck, and religiously taking the drops on-time.

No scarring, no corneal haze. Pretty lucky all things considered. My vision is better than it has been for years, even with correction. If you have astigmatism… get PRK. It’s worth it. If you’re on the fence on if PRK is worth it even with the suck of the first week… it is. Even with slightly fuzzy vision.

Other things that are interesting, my next checkup is 6 weeks out and it will likely be my last. At this stage I’m not done with care, I still have 4x daily steroid drops and I have to wear shades outside. There’s a risk of scarring if you don’t. I read a lot of FUD about what the steroids do. In case anyone is reading this and has seen the same – they promote healing, not slow it down. There’s a nice bonus where they reduce inflammation – allowing you to see better against light during the painful days.

I’ll update weekly from here on out, but won’t post daily unless something big happens. Now that I can see again I’ll have to go back and proof-read earlier posts 🙂

Android MTP mounting on OSX

Mounting Android devices on OSX can be a pain. There are commercial options that make it easy, but it’s also not horribly difficult with the help of some good software packages out there:

That’s that for the install. Test it quick to make sure it works:

You should see your phone pop up. If it doesn’t, you have a bad USB cable, your phone isn’t configured to allow connections, you have a power only cable, etc. Also, make sure that your phone is set to MTP, and that the computer is trusted. Once that’s done, you should be set!