SuSE Linux 6.1
SuSE Advanced X Configuration Tool (SaX) is a graphical interface for configuring X (and we all know how much of a pain that can be). You can navigate its menus with the mouse or the keyboard, and all you have to do is choose your mouse, graphics card and monitor from a few lists and an XF86Config file is created. I noticed that the lists were not as long as I have encountered elsewhere, and some older hardware was missing. SaX configures your keyboard and mouse as well and offers many expert configuration options.
Once you have finished with basic configuration, SaX allows you to test the video modes and make real-time adjustments, rather like xvidtune but graphical and easier to use. You get to see the standard X test pattern for a little while, and that's nice, but I would still prefer keeping it up all the time to get a better idea of how well the screen is configured. It's very simple to use, and if it doesn't work, you can always try the xf86setup or xf86config. Even after your system configured, you can use SaX to update your configuration in case you would like to use higher resolution, a new video card or a new monitor. This is unlike other installers which configure once during installation and require the use of external software or manual modifications afterwards. Once the XF86Config file is created, it's time to try out X.
The default window manager on SuSE Linux 6.1 is KDE, which has, in addition to its standard menus and KDE software, a SuSE menu housing entries for many of the various packages installed by YaST. Also configured in the menuing system are the various Applix programs, though at the moment they insist the license is out of date. (I hope this is corrected in 6.2.) SuSE's custom menus have more to offer than the custom menus of most other distributions, even though some menu options don't work and many installed software packages are not incorporated into the menuing system. Still, it is a clever idea to have YaST configuring KDE's menus during installation in such a way as to have optional packages included. If SuSE had more time to devote to going over the packages and making sure they all were properly collected into the menu tree, the system would be really neat. (The next step would be automatic real-time updating of the menu trees to correspond with the software on the system...)
On the whole, SuSE's window manager works just fine. You might have to know enough during installation to select the right XF86 server, however. SuSE's menuing system looks quite neat, and for the most part, files seem to be in the right places. No menu selections I found led to core dumps or worse, and although many of the packages I installed did not get entered into the menus (and some selections didn't do anything), you can do a lot with KDE as installed on SuSE. If you like GUIs (I, for one, vastly prefer consoles), KDE is very functional.
It is difficult to say anything bad about a Linux distribution; after all, they're all based on Linux and GNU software. Nevertheless, concerns sometimes arise over the decisions made about which programs and versions are used, and sometimes things just don't work. Where installation is concerned, auto-installers are nice when they work, but probing often crashes the system. On the other side, many people have no idea what hardware is inside their system and what IRQ and DMA values they ought to enter. Preconfigured package collections are convenient but lose flexibility, whereas manual selection of packages takes forever. Experimental software usually has enhanced functionality over stable software but often fails unexpectedly, as many of you know who simply must run the latest kernel/library/compiler, even when parts of it aren't working.
The choices to be made by a distributor can be difficult, and the practice of targeting a specific audience guides distributors in their decisions. Although I've recently been recommending SuSE when asked by newbies which distribution to install, I am aware it's not for computer illiterates. At the same time, it is easy to install and use and is rather well-endowed. It appears to be an ideal distribution for the middle 68% of Linux users, often choosing ease-of-use and stability over the cutting edge, while at the same time favoring maximum functionality and flexibility against oversimplification. The installation and configuration utilities (YaST and SaX) are examples of the latter, while the choice between gcc and egcs is an example of the former and latter, respectively.
I tried compiling a number of “problem” packages, sources that have always “bugged out” when I tried to compile them in the past, and every single time, SuSE compiled without error. Obviously, SuSE must have functional libraries in the right locations. (This was a problem with certain distributions years ago.) The kernel has never been one of those problem packages, and recompilation/installation went very smoothly. SuSE has a KDE menu item which starts up the kernel recompilation—another clue that SuSE is geared towards non-neophytes. Upon reboot, everything was in the right place and all the modules worked. This probably has more to do with kernel developers than with SuSE, but someone truly clever could have contrived a way to stop a kernel and its modules from working. In any event, kernel recompilation worked even better on SuSE than on Red Hat (which had some complications involving modules) and Caldera (which isn't targeted at kernel hackers anyway), although Slackware has never presented me with any problems.
SuSE Linux 6.1 has a lot of small things going for it, such as a different color scheme for the ls command, syslog messages logged to alt-F10, a first console which does not clear the screen on logout/login (so you can still read system messages from startup, etc.) and various other details. Unlike Red Hat, SuSE does not stick its logo all over the desktop (or on every single window, as many of you may remember). On the whole, SuSE has a cool, modern feeling to it—it isn't obnoxious. SuSE has not bent over backwards to make system configuration easy for the command-line impaired, so the system itself is not overly complicated or obtuse, yet it still works. And if it doesn't work, there's always support.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Readers' Choice Awards
- BASH script to log IPs on public web server
3 hours 13 min ago
6 hours 49 min ago
- Reply to comment | Linux Journal
7 hours 21 min ago
- All the articles you talked
9 hours 45 min ago
- All the articles you talked
9 hours 48 min ago
- All the articles you talked
9 hours 49 min ago
14 hours 14 min ago
- Keeping track of IP address
16 hours 5 min ago
- Roll your own dynamic dns
21 hours 18 min ago
- Please correct the URL for Salt Stack's web site
1 day 30 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?