Linked by Thom Holwerda on Tue 9th Oct 2007 16:10 UTC, submitted by elsewhere
Novell and Ximian "Novell's long journey from NetWare to Linux is finally complete. On Oct. 8, Novell released Open Enterprise Server 2 to its customers worldwide. Shortly after acquiring SUSE and its enterprise-focused Linux distribution, Novell announced that its follow-on to NetWare 6.5 would ship as a set of network services that could run atop the NetWare and the Linux kernel, OES 1.0. OES, which began shipping in April 2005, was the first major step in Novell moving NetWare's services from its native operating system to Linux. Now, with OES 2.0, the NetWare operating system kernel, NetWare 6.5 SP7, is still there if you run it, but it runs on top of the Xen hypervisor. You can also run the NetWare services, or a para-virtualized instance of NetWare, on top of Xen with the SLES 10 SP 1 kernel. So, if you're wedded to NetWare and its way of doing things, you don't have to wave good-bye to it."
Permalink for comment 277536
To read all comments associated with this story, please click here.
RE[5]: Goodbye Novell
by IanSVT on Wed 10th Oct 2007 19:39 UTC in reply to "RE[4]: Goodbye Novell"
IanSVT
Member since:
2005-07-06

Phasing out shouldn't be necessary. At the moment, many people are caught in limbo between one and the other. Virtualisation provides Netware with something of a future for people who need all of it, but OES should have been released with all the tools necessary for people to migrate from Netware to Linux and have it be a drop-in replacement. Many jumped ship when that didn't happen.


How many jumped ship because of that and who? Novell's entire reason for running 2 kernels parallel with similar feature sets was because the customers wanted it. You can't rip and replace like that. If you really want to drive customers away, then having OES services sitting on the NetWare kernel only one version and then eliminating that and going with the Linux kernel only on the next version would basically kill your File/Print business. Migrations paths are not supposed to be static rip and replace scenarios that are equal across the board. They need to provide as many options as possible for the varying situations one customer might have compared to the next. To do so is ignoring your customers and what they might want.

That's good, yes, but the two are named completely differently, and really, there should still just be one product.


That's just the point, they are not one product. OES proprietary services sit on top of SLES, but it provides radically different services than basic SLES. Not everyone needs those services. Otherwise you're basically using the analogy that Exchange 2007 should come with Windows Server 2003 because it direct extends the server and the directory.

I think everyone can understand that, but Novell's customers don't care and simply want a network operating system to do what Netware did with quite a bit extra. Frankly, Novell have failed to provide it.


Have you used OES2 yet? Have you thoroughly tested it to make that conclusion? I don't know about you, but have a load of NetWare servers 30 feet away from me right now. I want to be able to run the OES services on new hardware which is becoming more and more difficult on the NetWare path. I also can't go in to my server room and rip and replace all my NetWare servers with OES2 Linux boxes. My next(as in time) best option moving foward seems to be OES2 Linux at this point. Although to be fair, I have not tested it myself, so my opinion on what the next best option is based on what I have read, what I have heard from people who have gotten their hands on it already, and the realities of supported hardware with NetWare.

I'm not saying they should open source all of it - just the parts that they can get up and running on Linux.


Why? I'm not saying it's a terrible idea, I'm just curious as to what benefit would it be for them? Everything they need from NetWare has been ported to Linux already.

Edited 2007-10-10 19:44

Reply Parent Score: 4