the mergy notes

A couple of years ago, I did a little javascript trick to take the Evernote Bookmarklet code and place it into a Safari bookmark to get webclipper functionality inside iOS for all you Evernote users. Now that I am on Android, here is a way to get that same functionality via Firefox. Here is how.

1. Install Firefox from the Google Play Android App Store.

2. From inside Firefox on Android, go to http://www.evernote.com. Then, click on the side three-dots detail to flip the star bookmark icon.

 

This will give you a new bookmark we will use to park the webclipper on.

3. While you are there, go ahead and login to the web interface of Evernote. This is important as it sets the cookie that the web clipper code and Firefox will use moving forward. If you don’t login, you might get the “Set Third-Party Cookies” error when you try to use this clipper hack. You don’t need to stay logged-in, you just need to do something in Firefox so it will be okay with cookies from evernote.com like a login.

3. Select all and copy the code below in Android. This will be pasted into the Firefox bookmark.

Make sure you get the entire piece of continuous text/code in your clipboard to paste. 

4. Click on the URL field and tab over to Bookmarks. Find the Evernote bookmark we created in Step #2.

5. Click and hold on the Evernote bookmark to get the “Edit” option.

6. Edit the bookmark title to something you want like “Clip to Evernote” and paste the code you have in your Android clipboard from Step #3.

The completed “Edit Bookmark” should look something like this. Click OK to save out.

7. Now, when you are on a page you want to include into your Evernote system, you can just click on the URL field, go to bookmarks and select the “Clip to Evernote” and it will. You will be prompted to login initially, but after that (if you flip the “Remember Me” checkbox) you should all set when you are on a page you want to send to Evernote.

While on the URL you want to  Evernote, go into bookmarks and click it to bring it in as just a URL, whole page or both.

I just got off the phone with an Adobe rep to get the straight deal on the pricing changes proposed with the Creative Cloud changes. Currently, I have a site license of Creative Suite 5 Designer for our school. We purchased a couple of years ago and got educational pricing for the dual Mac and Windows Licenses. We have multiple laptop carts, computer labs, shared workstations, and we have individual users. I am going back to confirm what we paid for the site license when we bought the educational pricing for Adobe CS 5 to get the exact numbers.

Per the Adobe rep, all shared computers for the Creative Cloud CS Suite will be $39 per month. Individual users (named) can go with the $19 per month option. So, we have about 80 users I can do with individual accounts on and about 210 shared computers either in lab spaces or laptop carts. This will bump a little more over the Summer but is ballpark.

80 x $19 = $1,520.00 per month

210 x $39 = $8,190.00 per month

Total = $9,710 per month or $116,520 per year.

No kidding.

I have some more calls in and will correct once Adobe can confirm.

 

 

 

I did something Google Now or Google services in general didn’t like. After doing a bunch of searches, people were all over the place with possible fixes. I tried them all. But, the only solution I found was to delete the Google account data and cache.

Go to Settings >> Apps >> Google Search.

Press “Clear Data” and “Clear Cache” to purge the corrupted data.

 

Clearing this data out should puge the badness causing Google Search to freak-out.

Fan-Control-Daemon has been working great for months on my MacBook Pro 8,2 running Ubuntu 13.04 natively but found it getting hotter and hotter all the time. So, I recompiled FCD from source and moved /etc/mbpfan.conf back to default but that really didn’t help. I had to mess with things a little. Of course, you mess with this on your laptop and you could fry it, so good luck to you. I’m not responsible for melted Macbooks.

But, here is my /etc/mbpfan.conf that I am happy with right now. I bumped the max fan speed up from the default of 6200 and messed with the temps a little while changing the check interval to 3 secs.

 

 

I just had the experience of installing Ubuntu Server 13.04 on a new HP DL320e Gen8 server and it was not as easy as it should have been. It’s kind of pain because Ubuntu is not one of the officially supported operating systems from HP on this server model. So, their “Intelligent Provisioning” is worthless to you. For some crazy reason, Suse Linux is supported but Ubuntu is not. Weird. Anyway, here is what you have to do if you want to get Ubuntu Server going on it.

BIOS Settings

The SATA “fakeRAID” controller from HP that is integrated is not supported, so you will have to run software RAID which you can configure via the Ubuntu Server installer partitioning steps. But, even leaving the setting in the BIOS to have it use the B120i HP RAID controller will mess-up booting into Ubuntu. The Ubuntu OS installer (tried 12.04 and end-up installing 13.04 as it was officially released today) will see the physical drives in the server bays no matter what the BIOS is set to, but the BIOS will have trouble booting after what felt like a successful install. So, you need to go into the BIOS and change the SATA controller setting to “SATA AHCI Support” so you will be able to boot post-install.

I believe the BIOS ships with the “Dynamic HP Smart Array B120i RAID Support” set as the default. It’s not that smart, so get it out of the way. You will be bombarded with warnings, but you have to do it. I did a bunch of test installs and this worked when all other options around leaving the “smart” setting going failed. You can get into the BIOS with F9.

Software RAID Configuration

I went with two terabyte drives and a simple RAID1 setup. If you set the BIOS SATA controller setting or not, the Ubuntu installer will see the individual physical drives in the bays. You need to not use guided partitioning and switch to manual. On each disk, create a partition map and give each drive the full free space you can without any partitions.

Once each drive has free space and partition maps through manual partitioning, you will get an option to do “Configure Software RAID.” Select it and create your RAID with the drives you have and right changes. Then, go into Configure the Logical Volume Manager” and create volumes on the RAID for root and swap.

Yes, you can get fancy with more partitions and we all used to back in the day with various ones for /usr, /var, etc. but not really much of a benefit to do anymore. I match my swap size with the amount of RAM I have. In this case, I had a couple of 1TB drives sw mirrored and gave 8GB-ish to the swap space and the rest to root for Linux.

If you do these two major tweaks, you can get around the SATA problem with Ubuntu on the DL320e. If you get through an install and can reboot because it can’t find the volumes, check the BIOS setting and make sure it is on SATA AHCI or it will not find the installed Linux system and sw RAID.