So recently I updated Ubuntu. Mind you this was my main OS on my main production computer at home. I figured: “Hey, 11.10 is a new update… Unity should be better now… Right? And definitely there would be updates for a few other quirky bugs in Ubuntu… Right?” … Well that’s what we all would like to think huh.
Needless to say I updated my computer and it did very little to fix things and more to destroy things. This update made the OS pretty much unusable. So now I figure either I revert back to an LTS of Ubuntu, or switch distros all together. A buddy of mine suggested openSUSE for a change. Plus another buddy was using it and they both were quite satisfied. Well one mans treasure is another mans trash (the saying is vise-versa I know, but it fits good like this here). I would like to think I gave openSUSE a fair shot, I stuck with it for over a week, troubleshot with it. Attempting to get it setup to the production level that I had my last semi-stable Ubuntu running at. This was not happening for three main reasons. openSUSE lacks dkms, this is used to help assist with kernel updates when proprietary modules are plugged in after the matter (which I use often). There is a ‘critical’ bug with iSCSI, which I use extensively for file sharing. Lastly I could not get eclipse to run. Now I am sure if I spent more (and more) time troubleshooting and configuring this issue I might have been able to reach a resolutiong. But I was looking for quick setup and then back to production, over a week is not my idea of quick setup.
Welcome Linux Mint. Yet another Linux distro, this time based off of the Ubuntu I was using prior. Except there are a few main differences that cause it to shine. First is there is no Unity, there is gnome 2, plus a bridge port that supports gnome 3 applications as well. I installed it on one day, got updates ran, plus installed all of the applications I would normally use. Next day I got all of my server-type services setup and running (iSCSI most notably) along with all of my virtuals running and connecting to the shared iSCSI. Then lastly, eclipse ran right out of the box (the tar.gz box that is). Ahhh it feels good to be back into a production-able setting.
New fan and follower of Linux Mint. We will see how well it treats me.
Learned about a characteristic of ActionScript today. Although I have observed this attribute with the language, and had also learned how to work around it. I just had never had someone spell it out to me, and thus didn’t know the name/terms of “blocking” and “yielding”.
It makes sense from the overview of how AS3 is actually constructed and runs, but it is nice to have ‘closure’ of sorts and to have a full understanding as to why it acts this way.
Here is where I read about it
Here are the important snips of the above article:
“… there is no yielding or blocking in Actionscript either. If the next line of code is supposed to run, you cannot prevent the next line of code from running. That means that when you call Alert.show(), the next line of code following that runs right away. In many other runtimes, the Alert window has to be closed before the next line of code continues.”
“…There is no solution to allow for blocking or yielding other than refactoring the application to be event-driven…”
Which with the event-driven solution mentioned above is actually what I have personally started using to solve this problem (or condition) before actually knowing about this content.
And so now you know.
Learned about a new technique today dealing with making the performance of your webpages faster:
<?php flush(); ?>
The article here is where I found it:
TODO: fill out more about this library.
If you are Debian based, then auto-starting a service is usually handled by getting the script in place (usually in the “/etc/init.d/” directory) and registering it with an update-rc.d command. On a RHEL based distro, it is a tad easier with the following command:
Run it as root (sudo su -) and you will be provided with a nice ncurses GUI to choose which service you want to auto start on boot.
Here is the link that helped me discover this tool, really good article:
I have grown sick of FireFox, there are a few quirks in it that really annoy me some.
So I figured I would switch to Opera, yet I have noticed subtle areas that show Operas lacking of maturity.
I will not go back to IE.
I refuse to try safari, simply because every time I have used a mac, I have lothed it.
I have tried Chrome when it first came out, and now perhaps I will give chrome a second round, just as long as I can install a download accelerator instead of the built in one that pisses me off to no end. I am installing it now, and perhaps this time I will be a little more open to change and see how well it works for me. I will let you know.
I have noticed often that when working on a project I will either discover or consider a new technique or way to do a certain process. Yet even if the benefits are clearly evident, I will balk at converting my current development process for fear that it will disrupt the current work-flow or slow progress.
I think almost always my balking is a good thing, as it makes me pause and consider the choice… But I’m not so certain that my choice (which is more often than not) to hold off on implementing the change is to the better of the project. The reason I say this is because the losing out of the advancement often slows progress in the long run for missed functionality or ease of use.
Perhaps with more experience I will be a better balker.