Mini Review: SliceHost v. Linode Customer Service Post: 302376153

Sponsored Content

Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Mini Review: SliceHost v. Linode Customer Service Post 302376153 by Neo on Monday 30th of November 2009 06:35:23 PM

11-30-2009

Administrator

Quote:

Originally Posted by PHLAK

On the note of SliceHost... I've had a single 512 Slice with them for several months now (6-8?), and love them. Everything you've stated I have also found to be true. Their service is great, customer service is helpful and they are extremely transparent about everything they do.

Frantkly , I do worry about the credibility of folks who only have one post in the forums and that post is a glowing review of a company.

On the other hand, my experience with the customer service at Slicehost has been so favorable, it is easy to see how others might post in reply to my mini-review.

A long time ago there was this debate between Cisco and Wellfleet (later acquired by Bay Networks, as I recall). Wellfleets routers featured a faster performing backplane but had to be rebooted to change the configuration. Cisco routers, on the other hand, was a bit slower on the backplane, but you could change the configuration without rebooting the machine.

At the time, I explained to a USAF General in charge of communications that during the heat of battle, you don't want to have to reboot your router to add a filtering rule or change some other configuration.

That was around 1994. The USAF followed my advice (which they paid good money for !) and dropped Wellfleet in favor of Cisco and the rest is history. Few people know that one of Cisco's biggest and most influential customers, the USAF, got their foot in the door based on my work building network control centers and getting rid of the Wellfleets in favor of Cisco.

The theme of my short walk back in time above is to point out that speed, backplane performance, etc. are all great; but they are not the most important features to consider in most circumstances. Customer service is also very important as well.

In the digital age, I expect my VPS to be provisioned within 30 minutes, even with a fraud flag based on a primitive rule and I expect emails to be answered within that same time frame as well. A company should have employees with email on the mobiles answering queries, chatting, and more.

Wire speed is not enough. Linode needs to learn this lesson, I think.

Customer service "speed" is more important than "wire speed" for more people.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

3 More Discussions You Might Find Interesting

1. HP-UX

Customer support engineer

Hi All, I need the help to deploy or implement HP MC service guard 2 node cluster step by step procedure is any1 who can help me to send me the step by step procedure. Thanks and Regards Jahangir

2. Virtualization and Cloud Computing

Mini Review: SliceHost v. Linode Ubuntu 9.10 Setup

October 2010 Update: Linode Versus Slicehost – One Year Later A few days ago I posted Mini Review: SliceHost v. Linode Customer Service. At that time, I was going to cancel my account with Linode based on problems during the sign-up period. However, Linode asked me to give them another...

3. Android

Mini Review: Samsung Galaxy S (Android 2.1) v. Nokia E63

Well, I've had my new Galaxy S around one day now and I must say, I am not sure if I regret buying it or not. Before buying it, I read a lot of reviews about the Galaxy S (e.g. Samsung I9000 Galaxy S review: From outer space), including reviews of problems with the GPS and some intermittent WiFi...

LEARN ABOUT MOJAVE

systemd-networkd.service

SYSTEMD-NETWORKD.SERVICE(8)                                  systemd-networkd.service                                  SYSTEMD-NETWORKD.SERVICE(8)

NAME

       systemd-networkd.service, systemd-networkd - Network manager

SYNOPSIS

       systemd-networkd.service

       /lib/systemd/systemd-networkd

DESCRIPTION

       systemd-networkd is a system service that manages networks. It detects and configures network devices as they appear, as well as creating
       virtual network devices.

       To configure low-level link settings independently of networks, see systemd.link(5).

       systemd-networkd will create network devices based on the configuration in systemd.netdev(5) files, respecting the [Match] sections in
       those files.

       systemd-networkd will manage network addresses and routes for any link for which it finds a .network file with an appropriate [Match]
       section, see systemd.network(5). For those links, it will flush existing network addresses and routes when bringing up the device. Any
       links not matched by one of the .network files will be ignored. It is also possible to explicitly tell systemd-networkd to ignore a link by
       using Unmanaged=yes option, see systemd.network(5).

       When systemd-networkd exits, it generally leaves existing network devices and configuration intact. This makes it possible to transition
       from the initrams and to restart the service without breaking connectivity. This also means that when configuration is updated and
       systemd-networkd is restarted, netdev interfaces for which configuration was removed will not be dropped, and may need to be cleaned up
       manually.

CONFIGURATION FILES

       The configuration files are read from the files located in the system network directory /lib/systemd/network, the volatile runtime network
       directory /run/systemd/network and the local administration network directory /etc/systemd/network.

       Networks are configured in .network files, see systemd.network(5), and virtual network devices are configured in .netdev files, see
       systemd.netdev(5).

SEE ALSO

       systemd(1), systemd.link(5), systemd.network(5), systemd.netdev(5), systemd-networkd-wait-online.service(8)

systemd 237                                                                                                            SYSTEMD-NETWORKD.SERVICE(8)