When offered to preview Sprint’s Samsung Galaxy S offering, the SPH-D700, also known as the Epic 4G, I immediately jumped on the opportunity. While my first personal-use Android device was the Nexus One, I’ve handled my share of Android smartphones, and my history of smartphone use has included several Samsung phones over the years. This being the first Galaxy S device I’ve personally handled, I’m glad to say that Samsung does not disappoint, and I can highly recommend the device to users who need a physical keyboard and can sign up for a contract with Sprint.
In the final installment of the SysAdmin Series, I’m going to cover some tools to access a remote system’s desktop using VNC (Virtual Network Computing) clients.
I’ll admit that as a sysadmin, I don’t personally have a lot of use for VNC as almost all of the systems I need to access remotely are text-only systems, and I use a simple SSH client for that work. However, I know some sysadmins who rely on VNC clients to do some work on graphical interfaces when being at a terminal isn’t possible.
See our post about FRF50 for instructions on doing a manual upgrade.
I’ve installed the update from FRF83 (500K) on my own Nexus One, and installation was smooth, as always.
It is unknown what the update brings and whether it will be the last one before we see the final official Eclair>Froyo update.
You can download the update here if you didn't get the OTA yet:
For those of you still holding out on FRF50, here's an update to the latest leaked ROM:
You can now update from FRF72 - see Update 3 below.
Good thing for our readers that I’m a night owl, and I happen to love my Nexus One, and love me some frozen yogurt. Especially together:
And now I have my T-Mobile Nexus One updated with the latest and greatest FRF72 build.
I just happened to be browsing a forum about the upcoming official Android 2.2 Froyo release when I see someone leak a URL for the FRF72 build that Google Employees were given a week ago.
This SysAdmin Series article will cover four of my favorite tools as a sysadmin: two for analyzing network information, and one each for doing DNS lookups and Whois lookups on domain names. As with most apps I cover in my SysAdmin Series articles, I need to fully uninstall the app and wipe all prior data before demonstrating it here for you to protect my employer in case there’s any sensitive information lurking about.
First off, my apologies for the late posting in the SysAdmin series (or very early since tomorrow is Thursday). I had to deal with a double HDD failure on my home PC this weekend which ate up 14+ waking hours between Saturday night and all day Sunday, which would have been my prime writing time. Then the third HDD in that system crashed Monday evening, egad, what are the odds. I digress…
I've been looking for an easy way recently to manage configuration files for remote servers without having to deal with subversion, and even looked at some sort of file sync with Evernote/Dropbox via Android using an FTP client, but neither Evernote or Dropbox give you easy access to files on your SD storage when you download files.
A good diagnostic tool for any sysadmin is a port scanner to ensure a firewall is working as intended to open or close ports. When you want a quick and dirty scanning tool, there are some great free apps in the Market to do the trick. A quick search in the Market shows two apps which seem to be popular: OscanO and Port Scandroid.
This free app in the Market was written by Rich Jones of NewFreedomApps, found at http://www.thenewfreedom.net/ and the app is described by the author like this:
Nagios is by far one of the best solutions for monitoring just about everything on a server, and it’s excellent API system means that anything it doesn’t include out of the box can be written in just about any programming language as long as the program output conforms to their standard. I’ve personally written dozens of modules for micro-managing network interfaces, disk IO and so on. I’ve even heard of elaborate schemes of detecting when system load is too high on web servers and launching more Amazon EC2 instances, or checking when load is low enough to terminate EC2 instances, all fully automated.