Home > Server Admin > Mandriva 2009.1: Administration Advantages/Disadvantages

Mandriva 2009.1: Administration Advantages/Disadvantages

I train administrators every day. I often work with administrators who are moving from a Windows server background to Linux. One of the most often asked questions is, “Is there a graphical interface to administer the server with?” One of the solutions, though it be a partial solution, is using Mandriva 2009.1. Mandriva offers an administrative option under Administration/Configure Your Computer. This provides intuitive access to much of server administration. “Intuitive” is a key word here. By “intuitive” I mean, you can look at something, click on it and just by viewing the information you get an idea on where or what you should do next. For example with a graphical tool for adding users when you want to add a user and you see the button “Add User” you know what to do and it gets you there for the most part.

I think one of the issues that many distros are missing as far as administration, is the huge fear of the command line. Having used the command line for 12 years, I am all for it..faster, more efficient, etc. But, many in the new generation of Linux administrators are coming from Windows administration, are required to produce Linux projects for their company with little sympathy for the difficulties of learning from the Linux command line. Mandriva and Suse are two distros trying to help in that direction, both have merit. Note that both have server models that cost for support but provide more administrative options. All that said, let’s face it Linux was designed to be administered from the command line and it is very important to be heading in that direction. Mandriva, may provide an option to fill the transition to the command line.


As you review the graphical tools it is easy to see that each leads you down the path that you are looking to work with. The tools are easy to work with and each option is mostly laid out for you.



Networking today can be a nightmere with all of the options. Mandriva helps you work through those with the interface options. You still need to know a few terms, like are you using a DSL connection, Ethernet …wireless? But it is straightforward and can be usefull for almost all users.




Under “Security” one very nice feature is the easy to use firewall configuration, Ubuntu could take a lesson here. Click the options you want, save and you are set. You also have “Parental Controls” which allows a time restriction and Blacklist/Whitelist options. It is very basic and not going to be as useful as could be, but it is a start for a parent.



Having tried several with easy solutions I decided to use the graphical tools to create quotas on the /home directory. This is a good test as that task is always a little challenging from the command line. Go to Local Disks/Manage disk partitions and choose Continue…they do warn you about making mistakes here, Click on the /home directory and then “Toggle to expert mode” so you can see additional options. Choose “Options”.


Once you open the Options you will see a check box to initiate User Quotas. Save and restart the system, at least that was logical to do for the system to detect and load quotas.


The bad news was that after a restart userquota was installed in the /etc/fstab but it did not work. This is a disaster for an new administrator trying to work with graphical tools. To make it even worse the default install does not install the text tools for quota so you are completely stuck with a mess to fix. This is certainly not what an administrator who is trying to find a easier solution needs, it is a show stopper.

Though I did not work with every tool for this article, I will say that most tools worked fine. I will also say that the hardware management with Mandriva is excellent which means easier work with hardware devices. The tools that are a part of the Control Center are basic tools and seem to be fine for someone who is doing basic administration, but not up to speed for more advanced options.

  1. shamil
    May 10, 2009 at 9:28 am

    Great review of the mandriva control center. Other distro’s need this. To a great extent ubuntu does, but their firewall sucks. Suse has their YAST. Idk why yast is so popular when mandriva control center is way better. Hell, configuring options in ubuntu is easier than yast. Anyway, the control panel, i wish, was ported over to debian. So far it’s just a mandriva/pclinuxos thing. I don’t use all of the options in there, but it does have a lot and i’m glad.

  2. May 11, 2009 at 7:56 am

    Don’t hesitate to open a bug report concerning quota support at http://qa.mandriva.com

    By the way, you have also server wizard ( dns, dhcp+pxe, ntp, … ). Just install the drakwizard package.

  3. Tom Bridemore
    May 11, 2009 at 4:46 pm

    This is a philosophical question: What are the major negatives/turn-offs for having a GUI on a machine that’ll be a file/web/mail server for a family of five?

    Considering that I come from the days of Unix System III, command line *IS* my god. However, I like having a GUI in order to help others in my family learn their way from GUI–>Command Line–>Remote SSH for administration. My family’s used to Window$ environments, and of course having a GUI helps them move towards the ultimate goal of a pure non-GUI server.

    The server will *not* be used for casual computing but instead shall be used for administration of our web site, internal email and file service. Having the GUI allows for ease of use when it comes to administration (for the rest of the family) while I can always ssh to the machine and do what needs be done. So many articles I’ve read scream, “DANGER! DANGER! NEVER EVER USE A GUI IF YOU RUN A LINUX SERVER! THE END OF THE WORLD SHALL BEFALL US! WOE AND DOOM….” but I cannot ascertain as to what specifically is so harmful. Is it due to services being run that “shouldn’t” be running? I want Apache. I want email. I want file service via samba. I’ll set up the server to kill services I *don’t* need. I can and will do this. So what remains that causes a GUI to be so terrifying?

    The short question, is:
    What harm/damage/horrible things come from having the GUI up and running versus pure command-line?

  4. travisn000
    May 14, 2009 at 9:53 am

    Very nice review.. fair & balanced conclusions!

    @tom: I’ve often wondered the same thing.. the best explanation I have seen says that more stuff = more possible points of entry.. nothing specific to the GUI environment.. one option is to have a GUI environment, then unoad it when it is not needed.. “init 3” from c/l. ..my favorite option is to use Werbmin; it offers a great web-based interface to configuration of most aspects of your system, while still allowing access to config files, etc.. a great way to transition from gui to c/l (there is even a place to run shell commands from your browser if the gui doesn’t do what you like.. and of coarse, full ssh / https support!)

  5. nikoTron
    May 15, 2009 at 10:38 am

    @tom : try nmap on a system where only ssh is *ON* and then on a full service and GUI (x, rpc, etc)

  6. May 15, 2009 at 2:35 pm

    Tom Bridemore> It should be not that most Mandriva tools can :
    – be run run in CLI ( no X needed, it will fallback to a text version if available )
    – and of course can be run over SSH 🙂

  7. June 9, 2009 at 1:22 pm

    I still prefer the command line than the GUI, although previously worked with windows servers
    perhaps this habit of mind
    although.. yes.. the first time was scary problems)
    sorry for my bad english(

  1. August 3, 2009 at 1:53 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: