my blog

This beginner article by Mark Rais provides step-by-step instructions for installing Moodle, a Learning Management System, on to a Fedora Linux server. It provides everything necessary to setup a full powered intranet web-server that can support course listings, event calendars, student/teacher communication and much more. Best of all, a prototype server can be functional within about 45 minutes.

For those unfamiliar with Moodle, let me briefly share why this tool now supercedes nearly all other learning management systems. The Moodle project, started by Martin Dougiamas in 1999, has delivered a most capable and feature rich tool for schools and educators. Moodle, also termed a Course Management System, is a web content tool currently used in over 150 countries. The design and automated functions make installation and support almost too easy. Since Moodle is a purely Open Source development project, licensed under the GPL, it is freely available for all organizations. More importantly, with a world-wide community and use in 70 languages, support and guidance are also readily available.

Before you begin, I strongly encourage you to review the excellent documentation on the Moodle.org website. I especially recommend the official basic installation guide. This article is most effective when used in conjunction with the official guides and documentation. I also recommend that you consider combining the power of Moodle with a Linux Terminal Server. By doing so, you can create entire learning labs within hours using old, used computers and with nearly zero capital expenditures.

Now let's get started installing and running Moodle on Fedora:


Step 1. Assumptions and Needs
I assume that for the following steps you will be using either your root or a superuser account with the necessary access privileges. Although I try as much as possible to include only GUI tools, there may be an occasional need for you to use a command.

Although it is relatively easy, this guide does not explain how to setup your Fedora server network connectivity. I assume your server already has such connectivity working.

Finally, before you begin, please ensure that your system is atleast Fedora Core 4, comes with MySQL database, PHP version 4.1 or higher, and Apache httpd web-server already installed. If you did a full install of Fedora Core 4 or 5, then these items will most likely already be ready for use.


Step 2. Extract the Moodle Installation File
Download and copy the Moodle installation file (.tgz format) to your Fedora system. The latest Moodle file is named something similar to moodle-latest-xx.tgz where xx is replaced by the latest version number. For instance: moodle-latest-15.tgz

The single tgz file you download (around 16MB) is a compressed file that actually contains over 16,000 files and folders (around 58MB). To be able to perform the installation, you must first extract these files.

KDE:
A. From the main menu, choose System Tools, then File Manager - Super User Mode
B. Find the moodle-latest-xx.tgz file and double click on its icon
C. Once you see the Moodle folder, drag-and-drop it on to your Home Folder

This should automatically copy the Moodle folder into your Home Folder and extract all of the files contained within.

GNOME:
A. From the menu, choose Places and then Home Folder or the folder you copied your moodle-latest-xx.tgz into
B. Once you locate the moodle-latest-xx.tgz file, double click on it to start the Archive Manager
C. From the Archive Manager window, choose the Moodle folder and press the Extract button
D. This opens the Extract tool options. Be sure to choose the Re-create folder check box and press Extract

Note which folder the files will be extracted to! Usually the default is Desktop.

If you run into an issue, you may also try the following manual extraction option.

MANUAL EXTRACTION:
A. From either Gnome or KDE choose the Terminal or Console (usually under System Tools)

B. Create a directory for the files to extract into such as moodleextract

mkdir moodleextract

C. Copy your moodle-latest-xx.tgz file into the new directory

mv moodle-latest-15.tgz moodleextract

D. Now go to the new directory and uncompress all of the files

cd moodleextract

tar -xvzf moodle-latest-15.tgz

You should see a massive number of files scroll by and then see a new folder under your moodleextract directory called moodle.


Step 3. Copy Moodle Web-server Files
Now that you have extracted every file related to Moodle, it's time to move the files to the proper location for your web-server.

As noted in the excellent installation instruction guide, Moodle can be placed directly into your web-server's primary html folder so that Moodle is the only web content presented, or it can be included in a sub-folder where Moodle can co-exist with your other intranet web-server content.

In most cases, allowing Moodle to become your principle content management system is both beneficial and easiest. In such an instance you would then copy the moodle folder, we just extracted in the previous steps, directly into this folder: /var/www

If you already have a website or need to divide content you can also place the folder under: /var/www/html

Let's assume you will be using Moodle as your core content management system on this web-server.

KDE:
A. From the main menu, choose System Tools, then File Manager - Super User Mode
B. Find the moodle folder in your file browser and click on it twice
C. You should see about 31 folders & files. Now choose Edit, then Selection, then Select All
D. Once all of the files/folders are highlighted, choose Edit then Cut
E. Now push the up arrow on the File Browser two times and look for the folder labeled var
F. Double click on the var folder, then double click on www, finally double click on html
G. Now choose from the menu Edit, then Paste

GNOME:
A. From the main menu, choose System Tools, then File Browser
B. Find the moodle folder in your file browser and click on it twice
C. You should see about 31 folders/files. Now choose Edit, then Select All
D. Once all of the files/folders are highlighted, choose Edit then Cut
E. Now push the up arrow on the File Browser two times and look for the folder labeled var
F. Double click on the var folder, then double click on www, finally double click on html
G. Now choose from the menu Edit, then Paste

Don't close your File Browser yet! Now over 16,000 files will now be copied to your web-server content area under /var/www/html.

CHANGE FOLDER PERMISSION Before you can proceed with the rest of the installation, it's important to change the permissions for your web folder /html to allow Moodle Installation to create some essential files. Remember, that later you need to return to these steps to change the permission back to the more secure setting.

KDE:
A. From the File Browser window you just used, push the up arrow so you can view your html folder.
B. Right click on the html folder and choose Properties from the mini-menu.
C. Click on the Permissions tab
D. Now click on the Advanced Permissions button and ensure your settings look like this:

GNOME:
A. From the File Browser window you just used, push the up arrow so you can view your html folder.
B. Right click on the html folder and choose Properties from the mini-menu.
C. Click on the Permissions tab
D. Now ensure your settings look like this, then press close:

MANUALLY CHANGE PERMISSIONS Some people prefer speed to nice interfaces. For you the following commands will perform the same function. Remember that later, when the install is complete, you need to return to this same step but change the permissions to 755 instead of 777.

From the Terminal prompt type:

cd /var/www

chmod 777 html

Step 4. Ensure that Web-server and MySQL Are Running
Before going to the configuration step, it's time to ensure that your system is properly running the Apache httpd and MySQL tools.

You can ensure these are operational and active using the GUI tools.

KDE:
A. From the main menu, choose System Settings and then Server Settings
B. You should see the icon labeled Services. Click on it once. This will open the Server Configuration window.
C. Scroll down until you see the following and be sure to check the box beside each: httpd, iptables, mysqld

GNOME:
A. From the main menu, choose Desktop, then System Settings and then Server Settings
B. You should see the icon labeled Services. Click on it once. This will open the Server Configuration window.
C. Scroll down until you see the following and be sure to check the box beside each: httpd, iptables, mysqld

D. Now press the Save button. Now scroll down and choose each one (httpd, mysqld etc) and press the Start button after highlighting each.

You can now test to see whether the web-server daemon (httpd) is operating properly by trying out a browser. In your browser (firefox, mozilla, opera etc) type this url: http://192.168.0.254

Obviously, REPLACE the IP address above with your REAL IP address from your server. If you have a properly configured hostname you can also try the fully qualified name such as: http://test.myschool.org

If your web-server is working, you should instantly be taken to the Moodle Installation screen.

If you do not know your server's IP address, you can always use this command from the terminal or console:

ifconfig

Now try the IP address to ensure it truly is responding.

ping 192.168.0.254

(Replace my example with your IP). If you get a response in milliseconds, all is well. However, if you get Host Unreachable you have some problems with the configuration of your network settings and need to try to correct these first.

SECURITY NOTEIt is wise not to initially connect this server to the Internet. If you plan to eventually connect this server in such a way that it offers external access to the Internet, please ensure that you follow some of the following safety guidelines:

 Always run a firewall (learn more about this from excellent documents including this article)

 Disable all unnecessary processes such as bluetooth, pcmcia etc. You can do so using the same Server Configuration tool above.

 Close all unnecessary ports to your web-server (see this article for more details and ideas)

 Learn more about web-server security from great sources including this FreeSoftware Magazine article.
For now, it is best to keep the prototype installation simple until your Moodle site is properly configured. Keep the connectivity to within a firewall on the intranet for now.


Step 5. Configuring Moodle
It's time to start configuring Moodle. Fear not, this process usually takes about ten minutes at most, but is very important for finalizing your website configuration and operation.

A. LANGUAGE
The first installation screen offers a choice of Language. Please choose your language and press the Next button.

B. PHP SETTINGS
The second window shows your PHP settings and indicates if PHP is properly installed.

Don't worry about the GD library for now, everything else should say Pass. Now press the Next button again.

C. INSTALLATION DIRECTORIES
You will now see the key installation folders. Notice that although it indicates you need a Data directory, you must create this directory yourself. Let's do this now. From a terminal or console type these commands:

cd /var/www/

mkdir moodledata

chmod 777 moodledata

D. DATABASE CONFIGURATION
Press the Next button and you should now see the Database configuration window. Notice the statement "This database must already have been created..." It's now time to drop back to the terminal or console and create our moodle MySQL database.

Start by creating your primary MySQL database. NOTICE that if you already have a database, this information will overwrite the existing database. These steps are intended only for a NEW database.

TIPS: Please ensure you type a unique root password for your self, replacing rootuserpass. Be careful and take your time when typing these commands! Also note that you must create your own user password to replace moodleuserpassword.

ACCESS THE MYSQL DATABASE

mysql -u root

BEGIN USING THE MYSQL TOOL
These commands will be typed beside the mysql> prompt.

USE mysql;

Database changed

UPDATE user SET Password = PASSWORD('rootuserpass') WHERE User = 'root';

Query OK

FLUSH PRIVILEGES;

Query OK

In the steps above you created a root user account with password for your new mysql database. Now let's keep going and setup the moodle database with a moodle user account. Obviously, please create your own password replacing moodleuserpassword. It may help to cut & paste the commands below.

CREATE DATABASE moodle;

Query OK

USE moodle;

Database changed

GRANT ALL PRIVILEGES ON moodle.* TO 'moodleuser'@'localhost' IDENTIFIED BY 'moodleuserpassword';

Query OK

FLUSH PRIVILEGES;

Query OK

quit

Now restart the mysql administrator tool.

mysqladmin -p reload

rootpassword

Replace rootpassword with your root password and you are finished!

Now return to your web browser, view the Database configuration screen and fill in the blanks based on the new moodle user you created.

Press the Next button and you should get a very nice success screen.

You're ready to finalize all Moodle configuration files!


STEP 6. Finalize All Moodle Database Tables
The Moodle configuration tool will begin setup of multiple database entries. The next few windows are simply telling you the tables and settings and in almost all cases you should simply need to press the continue button.

Now scroll down and ensure all items are marked with: Success
Scroll down and locate the Continue button all the way at the bottom and press it.

Do this same process again for the Upgrading Database window. Find the Continue button all the way at the bottom and press it.

Finally, press Continue one more time and you should see another window named: Setup Block Table.

Find the Continue button all the way at the bottom and press it.

You will need to repeat this two times.

Then you will see a new window labeled: Site settings


Step 7. Configure Your Moodle Site
You're finally ready to put the finishing touches for your prototype Moodle site! On the Configuration screen you can make a number of custom selections regarding your website. For now just fill in some basic information. You will be able to return to this page and make future updates any time you wish.

I recommend that you select the Front Page Format option to be News items. Most Moodle sites have a news/updates section that makes up the home page center. You can easily create news items such as announcements, especially useful as you just start your site.

Now press the Save changes button.

You should now see the Administration control window. These options are very important as they dictate how your administrative account will operate. Please use a password that is not easily forgotten but also not easily identified by others.

You may include many other details, although for an administrator account we usually offer as few as possible details.

Be sure to add a New Password, and include a valid email address, the city and country, and then press the Update profile button.

You should now see your prototype Moodle website running!

Now click on the Configuration menu option on the top left menu and you may begin enhancing and customizing your website for your educational organization.


Next Steps
It's a great feeling to see Moodle up and running on your server. However, prior to connecting this server to a wider network, or allowing others to use the Moodle system, you need to address a few open items.

FOLDER PERMISSIONS
Be sure to address some of the overt security issues. In Step 3. you changed permissions for your webserver folder /html and in Step 5. Section C. you changed permissions for /moodledata. Now, using the same steps, go back and change the permissions to reflect a more secure web folder where only you can write or modify the files. The permissions should be set 755 or appear similar to this:

I recommend you change the permissions like this for ALL of your related website folders. Making sure that they are not available for write by anyone other than admin is very important.

STOP UNNECESSARY PROCESSES
You should also return to your Server Settings tool (see Step 4.) and disable all unnecessary processes.

Scroll down the list and identify the overt unneeded processes. On a Moodle server, I usually disable, among others, these items: apmd, apt, bluetooth, cups, dhcpd, isdn, mdmonitor, pcmcia, smb, and winbind. But, be certain iptables (firewall) is enabled!

You can always re-enable any of these in the future. For now, uncheck the services you do not need, press the Save button so the changes are saved for all future bootups. Then I always recommend a full server restart.

ADD USERS & AUTOMATED PROCESSES
Obviously a tool like Moodle is only as useful as it offers access and personalization. It is essential to begin by adding users, either manually or through a text file listing. You can do this through the Administration menu option labeled Users.

If you want Moodle to perform certain functions such as sending automatic emails, you need to ensure that your CRON process is running. CRON allows for automated processes and scripts to run at set times. Learn everything you need about CRON from my article The Basics of CRON and Linux Automation.

CREATE CUSTOM DESIGN
It is also important to customize the site for your organization's needs. Use a browser to return to your Moodle site and log in as admin. Once logged in, choose Configuration from the Administration menu on the left. This will allow you to make changes to many features and site design. For many more themes and design options visit the official Themes webpage. There are many good designs available.

I also recommend you spend some time traversing the various menus and options and testing things for your self. Get to know Moodle and enjoy!

I hope this introductory guide provides you with both the encouragement and confidence to utilize Moodle for your organization's needs. Moodle's relatively easy installation and use makes it a great educational tool.


TROUBLESHOOTING
PROBLEMS? WHO TO CALL?
I want to ask that you please do not bug people on the official Moodle forums or Moodle site with questions specific to THIS article. I or someone else at reallylinux will try to resolve questions you may have that are specific to this "un-official" guide. The fine folks at Moodle have plenty to do already! As always, please ask only after you've thoroughly read the documentation.

MYSQL/PHP ERROR
On rare occasion Fedora Linux will fail with its configurations. Before you begin to tinker with the database files or do some major editing of the PHP.ini file, try these initial steps:

From the main menu, choose Desktop, System Settings, then click on Security Level Select the SELinux tab. Then uncheck the Enabled (Modification Requires Reboot) box and press OK. You must disable SELinux for this to work right. Note that you should reboot your server to update your settings.

Or, maybe you can try using our example php.ini file and see if this resolves your issue. Please reboot after you copy this file to your /etc folder.

ERROR: We could not connect to the database you specified...
This error is almost always a result of improperly configuring the paths and settings in your Installation Database window.

For instance, the default for the user is: moodleuser@localhost
However, this often fails for login and database purposes and needs to be changed to: moodleuser

ERROR: PHP has not been properly configured with the MySQL extension...
This error comes when your server was only configured to use one type of database such as LDAP and not MySQL. In some cases, Fedora versions come with LDAP as the ONLY default database module extension supported. This is easily resolved by using the following steps from a super-user terminal prompt:

nano /etc/php.ini

Now press the CTRL and W keys simultaneously to search on a keyword in the file. Search for this: extension=

You will see the string in the php.ini file that reads:
; extension=msql.so

Now edit this line by removing the semi-colon so the line reads: extension=mysql.so
Notice the 'y' needs to be added.
Now save the updated php.ini file by pressing Ctrl and O and then pressing Ctrl and X.

If you have this issue you also need to copy the necessary mysql module file called mysql.so. You can download our example version or get an updated one on the web. Place this mysql.so file into your /var/lib/php/modules folder. For example, if you download our file into your root folder, you use this command:

cp /root/mysql.so /usr/lib/php/modules/mysql.so

You must now restart httpd and mysqld processes after making updates to modules and configuration files like this. You can restart the processes using the Service Configuration tool noted above in Step 4.

ERROR: Could not write the /config.php contents...
This error is almost always a result of a permissions problem. You may have forgotten before running the installation process to change the permissions for your website directory /html to allow read and write permissions. Please go back to Step 3. and review the details on folder permissions.

Mark Rais serves as senior editor for reallylinux.com and as a freelance writer. Rais promotes Open Source to organizations and government leadership in USA, Asia and Africa, and has written or co/authored five books, including Linux for the Rest of Us 2nd Edition.

Linux is a registered trademark of Linus Torvalds. IBM, PC-DOS, and OS/2 are the registered trademarks or trademarks of International Business Machines. Microsoft, Microsoft Vista, Microsoft Windows are all trademarks or registered trademarks of Microsoft Corporation both in the United States and Internationally. All other trademarks or registered trademarks in this opinion piece belong to their respective owners. FINAL RELEASE VERSION

SuSE Server Setup SuSE Server Setup

This section explains how to set up your server machine to be an install server for SuSE Linux. Bagian ini menjelaskan cara mengatur mesin server anda menjadi server untuk menginstal SuSE Linux. You can set up any Linux distribution to be a SuSE Linux install server, this machine does not necessarily have to be running SuSE Linux itself. Anda dapat mengatur apapun distribusi Linux menjadi server menginstal SuSE Linux, mesin ini tidak perlu harus menjalankan SuSE Linux itu sendiri.

This guide starts from the point where you have a machine installed with Linux which is already up and running and connected to your network. Panduan ini dimulai dari titik di mana Anda memiliki mesin diinstal dengan Linux yang sudah bangun dan berjalan dan terhubung ke jaringan anda. If you require help with installing Linux on your server then please consult the Further Information section of this HOWTO in Appendix A . Jika Anda memerlukan bantuan dengan menginstal Linux di server Anda maka silakan membaca bagian Informasi lebih lanjut HOWTO ini dalam Lampiran A.

4.1 Setting Up Filespace Menyiapkan 4,1 filespace

In order for your server to act as a SuSE Network Install server you will need to put on all the required data that will be needed to perform a full installation of the SuSE version you are serving. Agar server Anda untuk bertindak sebagai server Instal Jaringan SuSE anda perlu memakai semua data yang dibutuhkan yang akan dibutuhkan untuk melakukan instalasi penuh dari versi SuSE melayani Anda. For example, if you are used to installing SuSE using CDs then you will need space on your server to copy ALL the contents of each CD onto your server. Sebagai contoh, jika Anda digunakan untuk menginstal SuSE menggunakan CD maka Anda akan membutuhkan ruang pada server Anda SEMUA untuk menyalin isi dari setiap CD ke server Anda.

So, before you even think about setting up your machine as an install server, you must check that you have the required space available. Jadi, sebelum Anda berpikir tentang pengaturan mesin anda sebagai server menginstal, Anda harus memeriksa bahwa Anda memiliki ruang yang dibutuhkan tersedia. This sounds like a trivial thing to check but it is very important and easily forgotten when you're setting up. Ini kedengarannya seperti hal yang sepele untuk memeriksa tapi sangat penting dan mudah terlupakan ketika Anda sedang menyiapkan.

How much space will you need? Berapa banyak ruang yang akan Anda butuhkan?

A guide for the amount of space that you will require will be the amount or space of install media that you are intending to copy from later. Petunjuk Untuk jumlah ruang yang akan Anda akan memerlukan jumlah atau ruang menginstal media yang Anda berniat untuk menyalin dari kemudian. This might be one of the following examples: Ini mungkin salah satu contoh berikut:

• Number of CDs x 650Mb Jumlah CD x 650Mb

• Number of ISO images x 650Mb Jumlah ISO images x 650Mb

• One DVD which might be roughly 5Gb Satu DVD yang mungkin kasar 5GB

How much space do you have? Berapa banyak ruang yang Anda miliki?

You will need the appropriate amount of space available to your system on some local filesystem. Anda akan memerlukan jumlah yang sesuai ruang yang tersedia untuk sistem Anda pada beberapa filesystem lokal. It does not matter what form this takes, whether it's a RAID device, local disk (either SCSI or IDE), etc. Ensure that the space you intend to use is formatted with your chosen filesystem and is mounted. Tidak peduli bentuk apa yang diperlukan, entah itu sebuah perangkat RAID, disk lokal (baik SCSI atau IDE), dll ruang Pastikan bahwa Anda berniat untuk menggunakan diformat dengan filesystem yang dipilih dan di-mount.

You can check this space with the command: Anda dapat memeriksa ruang ini dengan perintah:

df -h df-h

If this output shows you have enough space to copy your install media then great, you can continue installation. Jika output ini menunjukkan bahwa Anda memiliki cukup ruang untuk menyalin media kemudian menginstal besar, Anda dapat melanjutkan instalasi. If not then it's time to think about an upgrade to your intended server machine! Jika tidak maka sudah saatnya untuk berpikir tentang upgrade ke mesin server yang Anda maksudkan!

4.2 Copy Installation Media 4,2 Salin Media Instalasi

Once you know you have enough space available it's time to start copying your install media to your chosen filesystem and directory. Setelah Anda tahu bahwa Anda memiliki cukup ruang yang tersedia sudah waktunya untuk mulai menyalin media instalasi Anda ke filesystem dan direktori yang dipilih. For the purposes of this HOWTO we will use the following example to represent the directory from which our install server will be setup and running: Untuk keperluan HOWTO ini kita akan menggunakan contoh berikut untuk mewakili direktori dari server yang kita akan menginstal setup dan menjalankan:

/install / install

Copy your install media to /install . Salin Anda media untuk menginstal /install The following example shows you how to do this for copying your SuSE CD images to /install : Contoh berikut menunjukkan kepada Anda bagaimana untuk melakukan hal ini untuk menyalin gambar CD SuSE Anda untuk /install

1. Mount your CD Mount CD
   eg mount /mnt/cdrom misalnya mount /mnt/cdrom

2. Copy the data from CD Copy data dari CD
   eg cp -av /mnt/cdrom /install misalnya cp -av /mnt/cdrom /install

3. Unmount the CD Unmount CD
   eg umount /mnt/cdrom misalnya umount /mnt/cdrom

4. Now swap CDs and repeat from step 1 for each of your CDs you have. Sekarang swap CD dan ulangi dari langkah 1 untuk setiap CD yang anda miliki.

5. Ensure that you have the dot files from the root directory of each CD copied over to /install Pastikan bahwa Anda memiliki titik file dari direktori root masing-masing CD disalin ke /install

Now you should have all you need in /install but if you have copied from CD then as far as SuSE is concerned the /install directory still represents a set of CD images that you have copied. Sekarang Anda harus memiliki semua yang Anda butuhkan di /install tetapi jika Anda telah menyalin dari CD maka sejauh SuSE adalah menyangkut /install direktori masih mewakili seperangkat gambar CD yang telah disalin. You need to change this such that the set of CD images appears as a single installation medium. Anda perlu mengubah seperti ini bahwa himpunan gambar CD muncul sebagai satu media instalasi. Use the following Perl command to do this: Gunakan perintah Perl berikut untuk melakukannya:

perl -pi -e 's/InstPath:\t\d+/InstPath:\t01/' /install/suse/setup/descr/common.pkd perl-pi-e 's / InstPath: \ t \ d + / InstPath: \ T01 /' / install / suse / setup / descr / common.pkd

4.3 Enable Remote Access 4,3 Aktifkan Remote Access

Time to make your install data available to other machines on the network. Waktu untuk membuat data instalasi anda tersedia untuk komputer lain pada jaringan.

NFS NFS

SuSE is best installed over the network using NFS since support for the HTTP and FTP protocols is not necessarily supported during installation, even though later system updates may be applied over HTTP or FTP. SuSE adalah yang terbaik diinstal melalui jaringan menggunakan NFS karena dukungan untuk protokol HTTP dan FTP tidak harus didukung selama instalasi, meskipun update sistem kemudian dapat diterapkan melalui HTTP atau FTP.

To install over NFS you need to meet certain conditions on the server: Untuk menginstal melalui NFS, Anda harus memenuhi syarat-syarat tertentu pada server:

• Your install directory is exported Direktori menginstal Anda diekspor

• NFS is installed and running NFS terinstal dan dijalankan

• Portmap is running Portmap berjalan

To export your install directory edit the /etc/exports file and add an entry for /install to it. Untuk mengekspor direktori menginstal mengedit /etc/exports file dan tambahkan entri untuk /install untuk itu. In our example, we would use the folowing line: Dalam contoh ini, kita akan menggunakan baris folowing:

/install *(ro) / install * (ro)

When you have saved your exports file you must then get your NFS daemon to read its configuration file again in order to export the directory you just added. Do this by running the command: Bila Anda telah menyimpan file ekspor Anda harus kemudian mendapatkan daemon NFS Anda baca lagi file konfigurasi untuk mengekspor direktori saja anda tambahkan. Lakukan ini dengan menjalankan perintah:

exportfs -r exportfs-r

This gives us the most simple read-only export to all hosts on our network. Ini memberi kita yang paling sederhana hanya-baca ekspor ke semua host di jaringan kami. If you want to include more advanced options in your export eg only exporting to certain hosts on the network or a certain subnet, etc then see your man page for the exports file at exports (5). Jika Anda ingin memasukkan lebih banyak pilihan lanjutan dalam misalnya ekspor hanya mengekspor ke host tertentu pada jaringan atau subnet tertentu, dll kemudian melihat halaman manual untuk exports di ekspor (5).

You have now completed the basic setup of your install server. Anda sekarang telah menyelesaikan konfigurasi dasar menginstal server Anda.

4.4 Package Customisation Paket 4,4 penyesuaian

You can, if you wish, add your own packages to the SuSE distribution so that they are installed along with SuSE over the network when you install your clients. Anda bisa, jika anda ingin, tambahkan paket Anda sendiri dengan distribusi SuSE sehingga mereka diinstal bersama dengan SuSE melalui jaringan ketika anda menginstal klien Anda. The advantage of this is that you don't have to spend time configuring each machine for packages that you may want installed that are not included with SuSE. Keuntungan dari ini adalah bahwa Anda tidak perlu menghabiskan waktu konfigurasi setiap mesin untuk paket-paket yang Anda mungkin ingin menginstal yang tidak disertakan dengan SuSE. Examples of this might be your own RPM packages that you have created or some specialised package. Contoh ini mungkin Anda sendiri paket RPM yang telah Anda buat atau beberapa paket khusus.

Simply copy your RPM package files into the following directory Anda cukup menyalin paket RPM file ke dalam direktori berikut

/install/suse/custom / install / suse / custom

NOTE: you may need to create this directory if it does not exist CATATAN: Anda mungkin perlu menciptakan direktori ini jika tidak ada

Your custom RPM packages should now be available to the clients. Paket RPM kustom Anda sekarang harus tersedia bagi klien.

5. SuSE Client Install Instal SuSE Klien

You should have already decided by now using the Quick Guide section of this HOWTO whether you are going to install your machine using the automated process or a manual process. Anda harus telah memutuskan sekarang menggunakan Panduan Cepat bagian HOWTO ini apakah Anda akan menginstal mesin anda dengan menggunakan proses otomatis atau proses manual. The automated process under SuSE is known as AutoYaST and in short provides you with a configuration file for the machine that you are going to install so that you can perform unattended installs of client machines. Proses otomatis di bawah SuSE dikenal sebagai pendek AutoYaST dan dalam menyediakan file konfigurasi mesin yang Anda akan menginstal sehingga Anda dapat melakukan menginstal klien tanpa perawatan mesin.

5.1 Create AutoYaST Config Files 5,1 Buat File Config AutoYaST

You only need to read/follow this section if you are intending to use an automated install process, if you intend to do a manual installation over your network then skip this section. Anda hanya perlu membaca / mengikuti bagian ini jika anda berkeinginan untuk menggunakan proses instalasi secara otomatis, jika Anda bermaksud untuk melakukan instalasi manual di jaringan anda melewatkan bagian ini. Here we go through the process of creating configuration files that the installer will read in order to create the configuration of our client machine we are installing during an unattended network installation. Di sini kita melalui proses yang menciptakan file konfigurasi installer akan membaca dalam rangka menciptakan konfigurasi mesin klien kami, kami menginstal selama instalasi jaringan yang tidak dijaga.

YaST 2 Module Installation Instalasi Modul 2 YaST

In order to start creating your config files you will need to install the AutoYaST module for YaST2 on your SuSE machine. Dalam rangka untuk mulai membuat file konfigurasi anda anda perlu menginstal modul AutoYaST untuk yast2 di SuSE Anda mesin. You will need three RPMs for this, all of which are on your SuSE source media eg CDs. Anda akan memerlukan tiga RPM untuk ini, semua yang ada di media sumber SuSE Anda misalnya CD. The three RPMs are: Ketiga RPM adalah:

• yast2-trans-autoinst yast2-trans-autoinst

• yast2-config-autoinst yast2-config-autoinst

• yast2-module-autoinst yast2-module-autoinst

Check to see if you already have them installed with the command: Periksa untuk melihat apakah Anda sudah memiliki mereka terinstal dengan perintah:

rpm -q {rpm package name} rpm-q (nama paket rpm)

If these packages are not installed then install with the command: Jika paket tersebut tidak terinstal kemudian instal dengan perintah:

rpm -Uvh {rpm package name} rpm-Uvh nama paket rpm ()

Create A Basic Config File Buat Dasar File Config

Once you have confirmed that you have the AutoYaST packages installed on your system, you can now start to create configuration files. Setelah Anda mengkonfirmasi bahwa Anda memiliki paket AutoYaST terinstall pada sistem anda, anda dapat mulai untuk menciptakan file konfigurasi. For most situations the basic configuration described here will be sufficient to perform your installations. Bagi kebanyakan situasi konfigurasi dasar yang dijelaskan di sini akan cukup untuk melakukan instalasi Anda.

Start the YaST2 Autoinstall configuration GUI with the command: Buat halaman AutoInstall yast2 konfigurasi GUI dengan perintah:

yast2 autoyast yast2 autoyast

You will now be presented with a window that allows you to configure most of your installation options as if you were installing a new machine or performing an upgrade. Anda akan disajikan dengan sebuah jendela yang memungkinkan Anda untuk mengkonfigurasikan sebagian besar pilihan instalasi anda seolah-olah Anda sedang memasang mesin baru atau melakukan upgrade. You can proceed through the menu system configuring your options for a particular system or set of similar systems that you wish to automatically install. Anda dapat dilanjutkan melalui sistem menu pilihan untuk mengkonfigurasi sistem tertentu atau seperangkat sistem serupa yang ingin Anda menginstal secara otomatis. Alternatively, you can create class definitions which allows you to save different parts of the configuration setup and then use different classes for different sets of machines. Lainnya, Anda dapat membuat definisi kelas yang memungkinkan Anda untuk menyimpan berbagai bagian konfigurasi setup dan kemudian menggunakan kelas-kelas yang berbeda untuk berbagai set mesin.

The use of classes is particularly good when you have a set of systems that are similar but that you would like installed in slightly different ways. Penggunaan kelas sangat baik bila Anda memiliki serangkaian sistem yang mirip tetapi yang akan diinstal dalam cara yang sedikit berbeda. For example, you could create a class definition for the hardware setup of all your client machines and create a separate class for the packages you want installed on them, whether they are server machines, test machines, workstations, etc. You can then choose which classes are used by which machines when they are installed. Sebagai contoh, Anda dapat membuat definisi kelas untuk hardware setup dari semua mesin klien Anda dan menciptakan kelas yang terpisah untuk paket yang ingin anda diinstal pada mereka, apakah mereka mesin server, mesin uji, workstation, dll Anda kemudian dapat memilih yang kelas-kelas yang digunakan oleh mesin ketika mereka diinstal. In our example here, all the machines would use the same hardware setup, but the workstation machines could install our workstation class of packages, test machines the test class, etc. Dalam contoh kita di sini, semua mesin akan menggunakan setup hardware yang sama, tapi mesin workstation workstation kita bisa memasang kelas paket, mesin tes tes kelas, dll

Once you have progressed through each configuration screen in the config setup GUI from YaST2 you are ready to save out your configuration file to disk. NOTE: it is outside the boundaries of this document to take you through each configuration option for installation, we are just concerned with the principles of network installs here. Sekali Anda telah mengalami kemajuan melalui konfigurasi masing-masing layar di setup konfigurasi GUI dari yast2 Anda siap untuk keluar Anda menyimpan file konfigurasi ke disk. CATATAN: itu adalah di luar batas-batas dari dokumen ini untuk membawa Anda melalui setiap opsi konfigurasi untuk instalasi, kita hanya berkaitan dengan prinsip-prinsip menginstal jaringan di sini. Please consult your SuSE documentation or the SuSE Website for this information. Silakan dokumentasi Anda atau SuSE SuSE Situs Web untuk informasi ini.

When you save your configuration files they will be stored locally in two different locations depending on what file you have created as follows: Ketika Anda menyimpan file-file konfigurasi tersebut akan disimpan secara lokal di dua lokasi yang berbeda tergantung pada file yang telah Anda buat sebagai berikut:

• Machine configuration files are stored in /var/lib/autoinstall/repository Mesin konfigurasi file tersebut disimpan dalam /var/lib/autoinstall/repository

• Class definition files are stored in /var/lib/autoinstall/classes Definisi class file tersebut disimpan dalam /var/lib/autoinstall/classes

Advanced Config File Setup Advanced Config File Setup

Before attempting advanced configuration please make sure that you have first created a valid basic configuration file as described above . It is perfectly possible to create your own configuration files from scratch but it is far easier to use the tools provided to do the job for you! Konfigurasi lanjutan sebelum mencoba pastikan bahwa Anda memiliki yang valid pertama kali membuat file konfigurasi dasar seperti dijelaskan di atas. Sangat mungkin untuk menciptakan file konfigurasi anda sendiri dari awal tetapi jauh lebih mudah untuk menggunakan alat-alat yang disediakan untuk melakukan pekerjaan untuk Anda!

Once you have your configuration file saved, you can open it in your favourite text editor. Setelah konfigurasi anda sudah memiliki file yang disimpan, Anda dapat membukanya di editor teks favorit Anda. The file is in XML format so it is particularly easy to follow and edit manually. File tersebut dalam format XML sehingga sangat mudah diikuti dan mengedit secara manual. You can use or modify any of the existing tags in your file, just so long as the tags, options, and syntax you use are legal. Anda dapat menggunakan atau memodifikasi setiap tag yang ada dalam file Anda, hanya selama tag, opsi, dan sintaks yang Anda gunakan adalah legal. A full guide to the tags and their usage can be found in the AutoYaST manual, please see Appendix A of this guide for a reference. Panduan lengkap untuk tag dan penggunaannya dapat ditemukan di AutoYaST manual, silakan lihat Lampiran A dari panduan ini untuk referensi.

The best use of editing the configuration file manually is probably for adding your own customised packages to the installation. Penggunaan terbaik mengedit file konfigurasi secara manual mungkin untuk menambahkan Anda sendiri paket disesuaikan dengan instalasi. Back in the SuSE Server Setup section we describe how to add your own customised packages to your install server. Kembali ke Server Setup SuSE bagian ini kami menjelaskan cara untuk menambahkan paket disesuaikan sendiri untuk menginstal server Anda. Here, we describe how to access those packages using the configuration file so they can be automatically installed with the rest of the system. Di sini, kami menjelaskan cara untuk mengakses paket-paket dengan menggunakan file konfigurasi sehingga mereka dapat secara otomatis diinstal dengan seluruh sistem.

You should be able to locate a section in your basic configuration file in your editor. Anda harus dapat menemukan bagian dalam file konfigurasi dasar dalam editor anda. You can use a sub-tag inside the software section called the tag which can be used as in the following example: Anda dapat menggunakan sub-tag di dalam bagian perangkat lunak yang disebut tag yang dapat digunakan seperti dalam contoh berikut:

custom kebiasaan

{Your package name} Anda (nama paket)

{Another Package} Paket (lain)

Default Default

The package location is written as custom which describes the directory under the suse directory of you install server where you have put your custom packages, in our example this would be /install/suse/custom , but you only need to write custom here. Lokasi paket ditulis sebagai custom yang menggambarkan direktori di bawah suse direktori anda menginstal server di mana Anda telah menaruh paket-paket kustom Anda, pada contoh kita ini akan menjadi /install/suse/custom tapi Anda hanya perlu menulis custom di sini.

You can include as many package tags under the packages section as you wish. Anda dapat menyertakan banyak package tag di bawah packages bagian yang Anda inginkan. Use one package tag for each custom package you want to include in your config file and install on the client machine. Gunakan satu package kustom tag untuk setiap paket yang ingin Anda sertakan dalam file konfigurasi dan install pada mesin klien.

The base tag at the bottom should be left as you configured it during the basic configuration. The base tag di bagian bawah harus dibiarkan seperti Anda dikonfigurasi selama konfigurasi dasar.

Save your modified configuration file from your text editor and it will then be ready to use in your installations as described below. Menyimpan file konfigurasi diubah dari editor teks Anda dan akan kemudian akan siap untuk digunakan dalam instalasi seperti yang dijelaskan di bawah ini.

5.2 Boot the Machine 5,2 Boot Machine

There are different situations during a network installation boot of one of your client systems that might mean that you wish to boot in one of the ways below. NOTE: you only need use one of the methods described for the particular usage for which it has been described. Ada situasi yang berbeda selama instalasi jaringan boot dari salah satu sistem klien Anda yang mungkin berarti bahwa Anda ingin boot pada salah satu cara di bawah ini. CATATAN: Anda hanya perlu menggunakan salah satu metode yang dijelaskan untuk penggunaan tertentu yang telah dijelaskan.

Manual Installation Manual Instalasi

If you skipped over the section above about creating AutoYaST config files then this is the way in which you should boot your client machines. Jika Anda melompati bagian di atas tentang cara membuat file config AutoYaST maka ini adalah cara di mana Anda harus boot mesin klien Anda.

1. Turn on your machine, ensure the CD drive is in the boot list of your BIOS, insert the CD. Hidupkan komputer anda, pastikan CD drive dalam daftar boot BIOS anda, masukkan CD. You should be faced with the normal boot menu of the SuSE installation program. Anda harus berhadapan dengan menu boot normal dari program instalasi SuSE. As an alternative to booting from CD, you can boot from floppy images, from the network, or using whichever method you would normally use to boot the installation program. Sebagai alternatif untuk boot dari CD, anda dapat boot dari floppy gambar, dari jaringan, atau menggunakan metode apapun yang biasanya digunakan untuk boot program instalasi.

2. Select the "Manual Installation" option from the boot menu Pilih "Manual Instalasi" pilihan dari menu boot

3. Your client should now boot the installation program and present you with a new menu system for the installer Klien Anda sekarang harus boot program instalasi dan hadir Anda dengan sistem menu baru untuk installer

4. Load any network modules you will need in order to connect to your network Load modul jaringan yang anda butuhkan untuk menyambung ke jaringan anda

5. Load any other modules you might need for installation eg SCSI modules if you are installing onto a SCSI type machine. Load modul lain yang mungkin Anda butuhkan untuk instalasi modul SCSI misalnya jika anda sedang menginstal ke mesin jenis SCSI.

6. Select "Start Installation" from the menu Pilih "Start Installation" dari menu

7. Choose the NFS option and fill in the IP addresses when prompted for. These should all be familiar to you ie the IP address of your server, and perhaps your client and nameserver as well if you have not selected to use DHCP. Pilih opsi NFS dan isi alamat IP ketika ditanyakan. Ini semua harus akrab dengan Anda, yaitu alamat IP server Anda, dan mungkin klien dan nameserver Anda juga jika Anda tidak memilih untuk menggunakan DHCP.

8. The installation will now proceed to the configuration screens where you can select the installation options you require for your client in the normal way Instalasi sekarang akan melanjutkan ke konfigurasi layar di mana Anda dapat memilih pilihan instalasi yang Anda butuhkan untuk klien Anda dengan cara biasa

9. Once you have configured all the installation options and selected to start the installation process, instead of reading from the normal CD (or other) media, the installation program will read all the information it needs from the network. Sekali Anda telah mengkonfigurasi semua pilihan instalasi dan memilih untuk memulai proses instalasi, bukannya membaca dari CD normal (atau yang lain) media, program instalasi akan membaca semua informasi yang diperlukan dari jaringan.

10. Don't forget to remove the CD (or other media) from the drive otherwise you could end up with a recursive installation process. Jangan lupa untuk mengeluarkan CD (atau media lainnya) dari drive jika tidak, anda bisa berakhir dengan proses instalasi rekursif.

11. Go grab a cup of something while you wait for your shiny new installation to finish, no changing of installation media needed. Pergi ambil secangkir sesuatu sementara Anda menunggu mengkilat Anda untuk menyelesaikan instalasi baru, tidak ada perubahan media instalasi yang diperlukan.

Automatic Installation Instalasi Otomatis

If you followed the section above about creating AutoYaST config files then this is the way in which you should boot your client machines. Jika Anda mengikuti bagian di atas tentang cara membuat file config AutoYaST maka ini adalah cara di mana Anda harus boot mesin klien Anda.

1. Copy your config file that you have already created as above from your repository directory on your hard disk to your floppy disk as a file called autoinst.xml. Copy file config yang Anda telah Anda buat seperti di atas dari direktori repositori Anda pada hard disk ke floppy disk sebagai file bernama autoinst.xml. You can do this as follows: Anda dapat melakukan hal ini sebagai berikut:

2. Insert and mount a floppy disk Masukkan dan mount floppy disk

3. cp /var/lib/autoinstall/repository/Your-File /dev/fd0/autoinst.xml cp / var / lib / AutoInstall / repositori / anda-File / dev/fd0/autoinst.xml

4. Unmount the floppy disk Unmount floppy disk

5. Put your floppy disk with the config file in your client machine Letakkan floppy disk dengan file konfigurasi mesin klien Anda

6. Turn on your machine, ensure the CD drive is in the boot list of your BIOS, insert the CD. Hidupkan komputer anda, pastikan CD drive dalam daftar boot BIOS anda, masukkan CD. You should be faced with the normal boot menu of the SuSE installation program. Anda harus berhadapan dengan menu boot normal dari program instalasi SuSE. As an alternative to booting from CD, you can boot from floppy images, from the network, or using whichever method you would normally use to boot the installation program. Sebagai alternatif untuk boot dari CD, anda dapat boot dari floppy gambar, dari jaringan, atau menggunakan metode apapun yang biasanya digunakan untuk boot program instalasi.

7. At the boot menu leave the default line as Linux to do the standard boot, but add the following parameters in order to read your configuration file from the floppy disk: Pada menu boot meninggalkan garis default Linux standar untuk melakukan boot, tetapi menambahkan parameter berikut untuk membaca file konfigurasi dari floppy disk:

8. linux autoyast=floppy linux autoyast = floppy

9. Your client should now boot the installation program and it will try to load appropriate modules and install the system with the information that you have provided in the config file. Klien Anda sekarang harus boot program instalasi dan akan mencoba memuat modul-modul yang sesuai dan menginstal sistem dengan informasi yang Anda berikan dalam file config.

10. If you are prompted to input any information for any reason then do so eg if the installer cannot connect to your network. Jika Anda diminta untuk memasukkan informasi apapun untuk alasan apapun lakukan saja misalnya jika installer tidak dapat terhubung ke jaringan anda.

11. Once the installation is running then you can remove the CD and the floppy disk and grab a cup of something while you wait for your shiny new installation to finish, no changing of installation media needed. Setelah instalasi berjalan maka Anda dapat mengeluarkan CD dan floppy disk dan mengambil secangkir sesuatu sementara Anda menunggu mengkilat Anda untuk menyelesaikan instalasi baru, tidak ada perubahan media instalasi yang diperlukan.

Further Boot Options Lebih lanjut Boot Pilihan

This is an extension to the technique used to boot client machines for Automatic Installations as described above. Ini adalah perluasan ke teknik yang digunakan untuk boot mesin klien untuk Instalasi otomatis seperti yang dijelaskan di atas. You should try this method if you have tried and failed with the method above. Anda harus mencoba metode ini jika Anda telah mencoba dan gagal dengan metode di atas. This section should help you if you have had network connection problems during boot, for example, if you do not have a DHCP server on your network. Bagian ini akan membantu Anda jika Anda memiliki koneksi jaringan masalah selama boot, misalnya, jika Anda tidak memiliki sebuah server DHCP pada jaringan Anda.

You can create what we call an " info " file to hold information about your clients network details. Anda dapat membuat apa yang kita sebut sebagai "info" file untuk menyimpan informasi tentang rincian jaringan klien Anda. This can then be used more explicitly by the install process to contact your network. Ini kemudian dapat digunakan lebih eksplisit oleh proses instalasi untuk menghubungi jaringan Anda. This is a plain text file in which you put certain keyword and value combinations that are recognised by the installer. Ini adalah file teks biasa di mana Anda memasukkan kata kunci tertentu dan nilai kombinasi yang diakui oleh installer.

The list of keywords you can use is as follows: Daftar kata kunci Anda dapat menggunakan adalah sebagai berikut:

• autoyast - the location of your configuration file autoyast - lokasi file konfigurasi anda

• gateway - the gateway your client should use (if any) gateway - gateway klien Anda harus menggunakan (jika ada)

• insmod - any special kernel modules you need to be loaded insmod - khusus modul kernel yang anda harus dimuat

• install - a full path to your server installation directory install - sebuah path lengkap ke direktori instalasi server Anda

• ip - the address of your client machine. ip - alamat mesin klien Anda. If this is blank then the installer will try BOOTP/DHCP Jika ini kosong maka installer akan mencoba BOOTP / DHCP

• nameserver - the nameserver address on your network nameserver - pada alamat nameserver jaringan anda

• netdevice - the network adaptor you want to be used netdevice - adaptor jaringan yang Anda inginkan untuk digunakan

• netmask - your client's netmask netmask - netmask klien Anda

• server - the hostname or IP address of the server you have set up ie the machine you have your NFS exports from server - nama host atau alamat IP dari server Anda telah mengatur yaitu mesin NFS Anda memiliki ekspor dari

• serverdir - the directory on your server the installation should be taken from serverdir - direktori pada server Anda instalasi harus diambil dari

Using the above keywords in an example info file, you might end up with something looking a little bit like this: Menggunakan kata kunci di atas dalam sebuah file info contoh, Anda mungkin berakhir dengan sesuatu yang tampak sedikit seperti ini:

install: nfs://10.0.0.100/install/SuSE8.0 install: nfs: / / 10.0.0.100/install/SuSE8.0

netdevice: eth0 netdevice: eth0

server: 10.0.0.100 server: 10.0.0.100

serverdir: /install/SuSE8.0 serverdir: / install/SuSE8.0

ip: 10.0.0.200 ip: 10.0.0.200

netmask: 255.0.0.0 netmask: 255.0.0.0

gateway: 10.0.0.1 gateway: 10.0.0.1

nameserver: 10.0.0.2 nameserver: 10.0.0.2

autoyast: floppy autoyast: floppy

Substitute the IP addresses above for relevant ones for your particular network and save this file with filename info in the root directory of your floppy disk that contains your configuration file autoinst.xml Mengganti alamat IP di atas yang relevan untuk jaringan tertentu dan menyimpan file ini dengan nama file info di direktori root floppy disk yang berisi file konfigurasi anda autoinst.xml