Novell's SLES 10 preview: Not your father's Suse
New default choices, virtualization package bode well for SLES 10 betaFollow @pvenezia
It appears that there’s been lots of Linux activity in Utah lately: Novell’s SLES (Suse Linux Enterprise Server) 10 is a much different distribution than SLES 9, from stem to stern.
Judging by the UI of the preview version I tested, it appears that part of Novell’s master plan involves borrowing heavily from Apple. From the first boot of the installation CD to the first true boot of an installed server, it’s clear that the layout and design of the GUI takes a page from Mac OS X, and does it well.
Swooping visuals aside, there are lots of changes behind the scenes. The installer is still based on YaST (Yet Another Setup Tool), but its appearance and function are more fluid, and the initial hardware detection code has been improved, making the GUI installer available on more hardware combinations.
Several default installation choices have been changed as well, not the least of which is that the default desktop choice is now Gnome rather than KDE. Novell’s acquisition of Ximian and the Ximian Desktop has finally pushed KDE to the side, which is sure to be a point of contention among hard-line Suse users. A fully configured firewall is also now a default, which wasn’t the case with SLES 9.
Installation revealed a much improved package management system and an online update mechanism that is less apt to throw up a flurry of bizarre dependency problems — and usually fail to handle any updates at all without help. I did run into some unexplained errors during a vanilla installation of SLES 10, specifically with the YaST2 autocloning feature, but that might be due to the prerelease nature of the code. Another interesting back-end change is the deprecation of JFS (journaling filesystem) for ReiserFS 3. Novell claims that this will be the last release of SLES to support JFS by default.
SLES 10 is plastered with Novell’s touch. It ships with Novell AppArmor, which is Novell’s reaction to Red Hat Enterprise SELinux. AppArmor and SELinux function in similar ways; they provide a system watchdog that is configured with known boundaries around individual applications and services, such as Apache and Samba, and will prevent these applications from treading outside their known safe space. This greatly reduces the risk of individual application exploits from interfering with the operating system at large.
Although both SELinux and AppArmor use the Linux Security Module interface, which provides the hooks necessary to handle application security at the kernel level, the biggest difference here is the management tools. SELinux is very complete but is hard to manage due to the limited front-end tools. Novell’s AppArmor, however, comes with a snazzy, YaST-integrated GUI interface to ease the admin burden and provide reports on application behavior.
Another large part of SLES 10 is the XEN 3.0 virtualization package. Much as Red Hat introduced XEN integration in Fedora Core 5, SLES 10 brings it to the production side of the house, offering not only a full Linux server base but also the capability for hosting virtual servers via XEN. (I’m sure Red Hat will follow suit in its next release of Red Hat Enterprise Linux.) A basic installation of SLES 10 offers both kernels at boot time — a standard 2.6.16-based kernel and a 2.6.16 kernel with the XEN hooks compiled in. XEN support is available on both the x86 and x86_64 releases.