Slashdot Mirror
Novell's Linux Business Takes a Seat At the Grown-Up Table
CNet is reporting that while Novell still has a long way to go before they start making Red Hat nervous, they have at least gotten a seat at the grown-up table. Reporting 31% year-over-year growth in their Linux business, Novell attributes very little of this success to their Microsoft partnership, looking to their Redmond connection mainly for interoperability work. "Novell's core Linux business is growing. By 'core,' I mean that our non-Microsoft- related Linux business is growing. These are Suse Linux Enterprise Server subscriptions sold directly by the Novell sales force or by our channel partners, without any Microsoft certificates or Microsoft salespeople involved. However, the important thing is that our total revenue picture for Suse Linux Enterprise is growing, as our customers increasingly don't distinguish. As we've said before, Microsoft offers an alternate avenue for purchasing subscriptions but we are focused on growth of the whole category."
In getting somebody on the phone, they are about a tie in time, but Novell edges them out in hold music.
In getting solutions, RH loves to point you to articles, Novell likes to get lots of logs, but goes a bit further sometimes. I have 2 stories to share on that.
At one prior company that switched from MS infrastructure servers to Linux, they moved from RHEL 3 to SLES 9 and 10 on VMware. I had an issue with logging into their servers via SSH using the company approved terminal program (not free, but oru version was not in support, being about 2 versions out of date. PuTTY worked fine.) After calling their support and escalating, their 2nd level guy said he'd call me back. A few hours later, having downloaded and installed the trial for the terminal program, he gave me the settings I had to change in the sshd_config to make it work.
At the same company as above, we had issues using SAMBA/Winbind to authenticate users to the server. It kept losing kerberos tickets in our environment. We sent various logs to them and finally were sent to 3d level support. They shortly sent us to engineering support and issued us a patch for "our" environment and told us to use this version of SAMBA and to email them when the next version alert for it was sent to us with the reference to this case so they could check the change logs and backport the fixes they had implemented when/if we wanted to upgrade.
Hell, I love their cool solutions pages and even use the novell docs sometimes to get things done on Redhat, due to their being more informative.