Unix and Linux network configuration. Multiple network interfaces. Bridged NICs. High-availability network configurations.


Reviews of latest Unix and Linux software. Helpful tips for application support admins. Automating application support.


Disk partitioning, filesystems, directories, and files. Volume management, logical volumes, HA filesystems. Backups and disaster recovery.


Distributed server monitoring. Server performance and capacity planning. Monitoring applications, network status and user activity.

Commands & Shells

Cool Unix shell commands and options. Command-line tools and application. Things every Unix sysadmin needs to know.

Home » Web Design

Late Night Rant #25: HP’s Web Site Fail

Submitted by on February 12, 2015 – 6:24 pm One Comment

I’ve already mentioned my dislike for the epic mess of broken links HP gingerly called its Web site. Nearly a year-and-a-half later the situation did not improve. Actually, it might have gotten worse.

One would think at the very least HP would take care to ensure functionality of the home page for one of its latest flagship products – the HP Moonshot server. Nope. It would seem even that was too much work for HP and its massive array of enterprise-class Web monitoring solutions.

If you google “HP Moonshot” and click on the top search result, you will get HP’s clever and informative “Oops. We can’t find that page for you”, accompanied by a picture of what looks like the backside of HP Web team’s senior manager wearing golf shorts.


Print Friendly, PDF & Email

One Comment »

  • ackmac says:

    Hi Igor, Agree that the broken links are not putting HP’s
    best foot forward. Perhaps after separation, the two more nimble and agile companies, Hewlett Packard Enterprise and HP Inc., will be able effectively keep the links current. Tried googling “HP Moonshot” and was successfully sent to an active page, albeit nearly two months after your rant. Perhaps they saw your article and fixed the problem :). Thanks for the excellent material!

Leave a Reply

%d bloggers like this: