That’s quite an accomplishment.
http://blog.linkedin.com/2014/04/18/the-next-three-billion/
There are now sites in that stratospheric level, but still, it is not an easy accomplishment. Congraluations LinkedIn!
Author: tin
SGI T-shirt
A post on LinkedIn’s ex-SGIers group gotme looking for my SGI t-shirts. One of my favorite pastime is to collect t-shirts, cups, etc. from the companies that I’ve worked for…. and I’ve worked for a lot of companies here in Silicon Valley.
I found my Jurassic T-shirt that I got when Jurassic Park, the movie, came out. That was very big at the time, and I remember SGI rented the near by Shoreline movie theater and let the entire company watch it. That was awesome!
Here is a picture of my T-shirts. It’s a little bit worn out — what do you expect for a 20 years old t-shirt. Also found another SGI t-shirt, this one is for Digital Studio package.
New Year online account clean ups
Every year I make resolutions and do my house cleaning. One of the ritual I do is to review all my online accounts and update my settings, change passwords, etc.
1. I update settings to increase my privacy as much as possible. By default, for social media accounts such as Facebook, Twitter, LinkedIn, Google+ etc. I set my sharing settings to only my circle, unless I specifically say otherwise.
2. I also change my privacy settings to not allow anyone to see more about me than I am comfortable with.
3. I turn on Two Factor Authentication if it is offer. This mean that login to an online account requires both password and something extra, such as a code sent to my phone via SMS. This has saved my bacons a few times when some rather big web sites (whose name shall not be mention) users database got hacked.
4. I also change my password if I’ve used that password for a while on that particular account. Yes, I know about having to keep track of, remember, all these different passwords. That’s why I strongly recommend a password locker. There are apps that run on iOS, Android, Windows and OS X (across all of them too), that you can use keep your passwords in.
5. I use a password generator to generate my 8 to 12 chars password (8 is the minimum I recommend).
Nexus 7 (2012 Wifi) and Kitkat 4.4
I had a scare this weekend with thinking my Nexus7 got bricked by Kitkat update from Google.
Thursday night (11/21/13), my Nexus 7 let me know that it has d/l’ed Kitkat and ready to update. I told it to go ahead since the last few times, updates from Google went fine without any problems.
After my Nexus 7 rebooted and updated, it then rebooted again and seem to be taking a long time at the boot up screen (bouncing color balls). It was late, past 1am, so I left it sitting there on the dresser next to bed and forgot about it. The next night, Friday, I saw it sitting on my dresser and remember about the upgrade, so checked it and found it is STILL at the bootup screen!!! WTF!
I pressed the power button to reboot. Same thing…. Crap! Tried it a number of time, no luck. I was tired, so I left it there in the bootup screen. This evening, I had time to look at it again and the damn thing is still at that screen. It has been a while, so I had forgot how to boot into recovery mode, sigh. Anyway, checking online found lots of complaints from people with similar problems.
This post on AndroidCentral was the one that solved my problem. Just thought I shared it.
The following snippet is from AndroidCentral post, I am putting here in case the post goes away.
” I was in the same situation and ran into that issue as well. What I did was download the 4.3 factory image from here: https://developers.google.com/android/nexus/images
Make sure you get the correct one for your device. I have a 2013 wifi so I chose: Android 4.3 (JSS15R)
Inside that downloaded file, you’ll find image-razor-jss15r.zip. It’s a couple of levels down. Unzip the files from there to your SDK folder (should be boot.img, recovery.img, system.img, userdata.img, and cache.img).
Boot your Nexus 7 to the bootloader (volume down + power) and connect to your PC with USB cable. Do NOT go into Recovery mode yet.
From the command prompt, make sure you can see your device: fastboot devices
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.imgAt this point you have a clean install of 4.3 JSS15R.
Now go to Recovery mode and sideload the 4.4 OTA as you originally tried and it should work this time.
I followed these steps and was able to update to 4.4 without losing any data. YMMV”
Note: Once I was sure that I can boot 4.3 without losing my data, I actually updated to 4.4 using the above method. The difference is that once in Recovery mode, I don’t do sideload, and I wipe dalvik cache, plus format /cache partition.
Dec 10, 2013
And now 4.4.2 update appeared on my Nexus7 and Nexus10. Once again, I accepted the update on my Nexus7, let it boot into recovery and proceed to messed it up. My fault this time. I thought it would be as complicated as the previous update from 4.3 to 4.4. I had to use fastboot procedure above to fix it.
For my Nexus10, I just had to accept the update to 4.4.2. Boot into bootloader, flash CWM recovery, then boot into recovery and ‘adb sideload’ the new SuperSU.
Repurposing netbook into gateway, firewall, AP
The older netbooks, such as ASUS EEE 900 series, have gone down in price. I bought a refurbed EEEPC 900A w/1GB RAM, 4GB SSD and turned it into my gateway, firewall and local AP. Upgraded memory to 2GB RAM, and added an external 8GB SD flash.
I loaded Fedora Core 17 Security Distro on it. Now I have a nice, cheap gateway, firewall and AP (although only 802.11G speed).
I’ll add more to this as I have time…..
Unfortunately the netbook only have one wired 100M enet. I need at least GigE interfaces. I am currently looking at the
OEM Production 2550L2D-MxPC
which is an Atom D2550 based system with 2 Broadcom GigE, small, lower power and up to 8GB of RAM. This should last me a long time as a router/gw/fw.
More to come….
You must be logged in to post a comment.