 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
 *                                                                         * 
 *   ROCK Linux is Copyright (C) 1998 - 2000  Clifford Wolf                * 
 *                                                                         * 
 *   Read the file 'COPYING' for licensing details.                        * 
 *                                                                         * 
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 


This FAQ is *not* meant to cover everything. It should,
however, help you through any challenge you may have
building, installing and booting ROCK Linux on your system.
Some fairly basic stuff on configuring ROCK Linux is included as well.
For further guidance, please refer to the documentation pointed to in 1.6
The last section of this FAQ covers ROCK Linux standards compliance,
roadmaps etc.

Harass the documentation maintainer for missing details, when you
have written the relevant entry to the FAQ... :-)

Table of Contents:

1.    Documentation overview.
1.1.    Installation and Compilation.
1.2.    man-pages
1.3.    Other sources of documentation

2.    Downloading and building ROCK Linux
2.1.    What documentation is availabile on building ROCK Linux?
2.2.    The download script crashes/fails.
2.3.    I have problems downloading the sourcecode-package <X>.
2.4.    I don't want/need package X.
2.5.    What are the prerequisites for building ROCK Linux?
2.6.    The sources verifies OK, but building fails at <X>.
2.7.    Building a single package.

3.    Partitioning your harddrive
3.1.    Partitions

4.    Initial configuration
4.1.    Documenting your changes
4.2.    Devfs
4.3.    Network
4.4.    Keyboard Mapping
4.5.    Date, Time and Timezone
4.6.    Shell profile
4.7.    Lilo

5.    Network
5.1.    Low level network configuration
5.2.    Hostname and DNS Client settings
5.3.    Sendmail
5.4.    Inetd
5.5.    Sshd

6.    Kernel
6.1.    Kernel sources and patches
6.2.    Loading kernel modules and changing kernel settings
6.3.    PCMCIA Drivers (PCMCIA = PC-Card)
6.4.    The SAK (Secure Attention Key)

7.    System V Init Configuration
7.1.    Runlevels
7.2.    Bootup and Shutdown

8.    Framebuffers, X11 and DRI
8.1.    The kernel framebuffer devices
8.2.    XServer (XFree86)
8.3.    DRI
8.4.    Windowmanager

9.    Package management
9.1.    Package information
9.2.    Installing and removing packages
9.3.    Packages in the RPM format
9.4.    Finding modified files

10.    ROCK Linux and standards
10.1.    Does ROCK Linux obey the FHS standard?
10.2.    Why isn't there a real package management system? Or is there?

11.    ROCK Linux roadmap.
11.1.    What does the future hold for ROCK Linux?

------------------------------------------------------------------------

1.    Documentation overview.


1.1.    Installation and Compilation.

A quick overview of ROCK Linux is given in the file README. A detailed
description of the compilation/build procedure can be found in the file
BUILD. A description of the installation procedure can be found in the file
INSTALL. For specific problems on building and installing ROCK Linux not
covered in the mentioned files, please refer to this FAQ. On a ROCK Linux
system, the native documentation is found in:  /usr/doc/rock
The documentation for the various scripts can be browsed with the Help scripts:
./scripts/Help <Script>


1.2.    man-pages

ROCK Linux comes with a full suite of manpages. To see the man-page for a
particular command or file, execute:  man <command>

To search for multiple man-pages covering a particular keyword, execute:  man
-k <keyword>


1.3.    Other sources of documentation

General Documentation:
  /usr/share/doc/*

Packages:
  /usr/share/doc/packages/*

Kernel:
  /usr/src/linux/README
  /usr/src/linux/Documentation/*



2.    Downloading and building ROCK Linux


2.1.    What documentation is availabile on building ROCK Linux?

A description of how to build (download and compile) ROCK Linux can be found
in the file BUILD. This section of the FAQ gives a few hints to solve a few
frequent 'challenges' which may show up during the download and compile
phase. The FAQ does not give a complete overview of the download/install
procedure.


2.2.    The download script crashes/fails.

Do you have an open network connection? :-) The download script uses wget(1).
Is wget installed on your system? If not, get it from:
ftp://ftp.gnu.org/pub/gnu/wget/

Also, if you are behind a firewall, you need to set two environment variables
in order to tell wget how to get through the firewall. These variables are
"ftp_proxy" and "http_proxy" (note: lowercase) and take the form:
hostname:port.  For example, running tcsh, I would do:  
setenv ftp_proxy www-proxy.mycompany.com:8080

It's also possible to add 'http_proxy = STRING' and 'ftp_proxy = STRING' lines
to the .wgetrc file in your home directory. You can also set other wget
options like 'passive_ftp = on' in this file.

If you need to provide a user/password for getting through the firewall,
refer to the wget man-page.


2.3.    I have problems downloading the sourcecode-package <X>.

Check if you can get in contact with the remote host where the package is
located. If you can't, try to locate the package elsewhere and download it
manually from there. A useful tool for locating files is:
http://ftpsearch.lycos.com/

If you download the file manually, copy it to the appropriate 
directory and re-execute the download script in order to have the file
converted to bzip2 format.

If you do get in contact with the remote host, but the file is missing, do as
above. If the file has been replaced by a more recent version, edit:
pkg-config/<package>/puzzle.pz

to match the new version. Then execute:
./scripts/Puzzle

before re-executing the download script.


2.4.    I don't want/need package X.

If you for some reason decide that you don't need a particular package,
delete the directory ./pkg-config/<x>/ , then rebuild the ./scripts/packages
file by executing:
./scripts/Puzzle

Then execute the download script again.  But please note that a lot of
packages depend on the presence of other packages in order to compile
successfully. It is your choice, but don't bug us if anything fails during
compile...


2.5.    What are the prerequisites for building ROCK Linux?

You need a working development environment in order to build ROCK Linux. If
you can build a new kernel, you should be on the safe side.

Your current kernel should support:
	- loop devices :
		this is needed to create the (boot-)floppies.
		Enable 'loopback devices' in the 'Block Devices' section
		of the kernel configuration.
	- devfs :
		the device filesystem is a patch for the Linux kernel which
		now has become part of the official development kernel.
		Get devfs for 2.2.x kernels from:
		http://www.atnf.csiro.au/~rgooch/linux/kernel-patches.html
		Enable devfs in the 'Filesystems' section of the kernel
		configuration.
	- nfsd :
		It is recommended, but not required that your kernel can act
		as an nfs-server, and that the userland tools for actually
		exporting directories are installed.  Enable nfsd in the
		'Filesystems|Network filesystems' section of the kernel
		configuration.

You need mmv(1). If mmv is missing from your system, install it from your
current distribution, or compile your own from the sources:
./archive/mmv-<vers>.tar.bz2

Most hardware running Linux can compile ROCK Linux. I would recommend a fast
system with a lot of RAM - you will need it (a full re-compilation runs more
than 30 hours on an AMD K6-2 300 MHz with 128 MB RAM and UW-SCSI disks). It is
mostly a matter of how much time you've got. You will need 2.5 GB free disk
space for building the complete ROCK Linux distribution - or more.


2.6.    The sources verifies OK, but building fails at <X>.

Hm. This should not happen, unless you are building a development "snapshot".
Did you obey The Rules?
   - the current kernel supports devfs 
   - keep the terminal where you start building ROCK Linux open until the
     build is complete 
   - have enough disk-space 
   - build to a local filesystem 
   - download/build everything 
   - mmv is installed 
   - /usr/src/linux matches the kernel sources in the distribution

You followed all the rules? And you are sure your hardware isn't flaky? If
the compile bombs out with a "fatal signal 11", please visit:
http://www.bitwizard.nl/sig11/

It may happen that a more recent version of glibc is required. If this is the
case, please perform these commands:

   init s
   [log in as root]
   bzip2 -d /rock-linux/tars/<*>-glibc.tar.bz2
   cd /
   tar xf /rock-linux/tars/<*>-glibc.tar.
   reboot

This will replace the version of glibc you have with the version coming with 
ROCK Linux. [FIXME: can this have any unwanted effects?]

Is there a more recent version of ROCK Linux availabile? If so, try that. The
packages you have downloaded can be manually copied into the new tree.

If you followed all the rules, used the latest ROCK Linux distribution and
you did not get a "signal 11", send an email to rock-linux@clifford.at,
explaining how and what. In particular, please state that you have followed
the guidelines in the FAQ...

In order to complete the build anyway, change this line in ./Config:
   # abortonerror=1
to
   abortonerror=0

Please do 'touch _nodel_' before you restart the build. Otherwise, the build
script will delete all work done so far.


2.7.    Building a single package.

Building a single package is simple:

    # cd /rock-linux
    # ./scripts/Build-Pkg <packagename(s)>

Please also see the help-text for Build-Pkg. (./scripts/Help Build-Pkg


3.    Partitioning your harddrive


3.1.    Partitions

If you are a seasoned Linux hacker, you probably know how you want your disks
and partitions set up. The following is a useful layout for the author:

primary partition 1     20-40 MB        /boot
primary partition 2     1 - 3 GB        /
other partitons         1 - X GB        other root, /home, /usr/src etc.
primary partition 4     100 MB          swap

The only point the author tries to show here is the use of a small /boot
partition. By having a separate boot partiton, it becomes somewhat easier to
play with multiple distributions on the same physical harddisk. This trick is
also useful if you for some reason want to have a network-mounted (or
ramdisk-based) / and/or /usr partition. Please see:
/usr/src/linux/Documentation/nfsroot.txt
and (for ramdisk based systems): 
/usr/src/linux/Documentation/initrd.txt
/usr/src/linux/Documentation/ramdisk.txt

Remember that after bootup, the kernel image on disk is not needed anymore.
Thus /boot does not even have to be mounted for everyday use.

Another useful trick is to put lilo.conf on the /boot partiton and
(optionally) create a symlink to it in /etc. Thus, you can have multiple
root-partitons on the same system, but just one lilo.conf. This is useful if
you are playing with multiple distributions.



4.  Initial configuration


4.1.    Documenting your changes

Please document any change you make in the file /etc/conf/NOTES. The easiest
way to do this is to use the command 'sysnote'. It should be a strict policy
for you to type 'sysnote' after you made a change and write a few lines
documentation - you will love it as soon as something goes wrong ...


4.2.    Devfs

You need to tell ROCK Linux which device is the swap partition and so on.
You can do this by editing /etc/conf/devfs. This script is started by the
boot script and creates symlinks for /dev/swap, /dev/cdrom, /dev/mouse, ...

You can set the permissions and ownerships of your device files by running
chown and chmod on the files from /etc/conf/devfs or using the devfsd config
file (/etc/devfsd.conf).

It's recommended to access the symlinks instead of the real device files for
transparency. You should do as much as possible with devfsd instead of
/etc/conf/devfs. See the manpage for devfsd(8)

The /dev/root symlink is created automatically by the devfs driver - there is
no need to create one in /etc/conf/devfs.


4.3.    Network

Covered in the next section of the FAQ.


4.4.    Keyboard Mapping

The keyboard maps are placed in '/usr/share/keymaps'.  Just create a symlink
for your keyboard mapping to '/etc/default.keymap'. Make sure you are linking
to a file, and not a directory.


4.5.    Date, Time and Timezone

The zoneinfo files are placed in '/usr/share/zoneinfo/'. Just create a
symlink for your timezone to '/etc/localtime'. Make sure you are linking to a
file, and not a directory.  Set the local date and time using the 'date'
command and adjust the hardware clock using the 'hwclock' command. 
Note: When using ROCK Linux the hardware clock is always running at UTC.


4.6.    Shell profile

The file '/etc/conf/profile' is included at the end of '/etc/profile'. It's
always better to edit this file than to edit '/etc/profile'.


4.7.    Lilo

A sample lilo.conf is included with ROCK Linux. Please edit it.
Lilo comes with extensive documentation and man-pages. If this isn't enough,
a really nice article about lilo by computer magazine C't is located here:
http://www.ix.de/ct/english/99/12/166/

When you are done editing lilo.conf, please remember to run 
lilo

lilo should respond with:
Added <label> *
if you did it correctly.



5.  Network


5.1.    Low level network configuration

To set up a simple IP network interface, edit the header of
/etc/conf/network. If you need to do more complex things you probably need to
rewrite the functions start_net and stop_net in this file.  Typically, if you
have an Ethernet card in your system but want to use a ppp-interface as your
default gateway, you want to comment out the 'route add default' stuff in
these functions.


5.2.    Hostname and DNS Client settings

Just write the hostname to the file '/etc/HOSTNAME' and the domainname to the
file '/etc/DOMAINNAME'. The configuration of the DNS resolver is done using
the file '/etc/resolv.conf'.


5.3.    Sendmail

Go to /etc/mail and add all host/domainnames for your server to the file
"sendmail.cw" and your aliases to the file "aliases".  Run 'make -C
/etc/mail' after every change to the aliases file. If you modified the
sendmail.cw file you need to restart sendmail by executing
'/sbin/init.d/sendmail restart'.  Verify that sendmail is activated for your
default runlevel.


5.4.    Inetd

The inetd daemon is configured using the file '/etc/inetd.conf'. By default,
only the services 'telnet', 'talk' and 'ident' are enabled.  Verify that inetd
is activated for your default runlevel.


5.5.    Sshd

The default configuration of the Secure Shell Daemon should be OK for most
servers. You can use 'make-ssh-known-hosts' to create a
'/etc/ssh_known_hosts' file. Verify that sshd is activated for your default
runlevel.



6.    Kernel


6.1.    Kernel sources and patches


The ROCK Linux kernel sources are placed in /usr/src/linux

These are the official (as released from Linus Torvalds) sources, but with
some patches applied. The patches and the official kernel-source tarball can
be found in /usr/src/kernel/.

Like most other Linux Distributions ROCK Linux comes with a pre-compiled
kernel. However: It supports only the most common hardware and it probably
includes a lot of drivers you will never use. So you should always compile
your own kernel! Also note that the precompiled kernel and modules are
compiled for SMP. If you recompile the kernel, you should also recompile
the modules.

For Linux newbies, this is how a new kernel tarball should be installed:

a) download the latest kernel tarball from:
ftp://ftp.xx.kernel.org/pub/linux/kernel/v2.4/

replace xx above with your country's domainname extension.
(I.e. 'at' for Austria.)
 
b) Verify that the directory /usr/src/linux/ is a symlink. If it isn't, move
it to a different directory with mv /usr/src/linux /usr/src/linux-old

Then do:
rm /usr/src/linux                       (if it was symlink....)
cd /usr/src
tar Ixvf /path/to/kernel-tarball.bz     (if .tar.gz, replace 'I' with 'z')
mv linux linux-<version>                (f.x. linux-2.4.0)
ln -s linux-<version> linux
cd linux 
make menuconfig                         (select your options. NB! Enable devfs!)
make dep
make bzImage
make modules
make modules_install
cp arch/i386/boot/bzImage /boot/bzImage-<version>
vi /etc/lilo.conf                       (add a section with the new kernel)
lilo                                    (write the new lilo configuration)


6.2.    Loading kernel modules and changing kernel settings

The kernel modules which come with ROCK Linux are built for SMP kernels.  So
even if you don't have an SMP system you should build an SMP kernel if you
would like to use the pre-built modules (like PCMCIA, PerlFS, ...).

Installing the package "modules" does only make sense for you if you are
going to use the standard kernel. If you are going to build your own kernel
you don't need this package.

The system bootup script calls /etc/conf/kernel. You can insert all commands
you need to load modules and to configure the kernel in this file. This file
should not contain any command which is not a insmod/modprobe call or an echo
to '/proc/sys/*'.

If you have enabled the kernel module loader (which is highly recommended if
you have built any part of the kernel as a module), edit /etc/modules.conf
accordingly. Note that there are a lot of default values, even if the file
does not exist. See the manpage for modprobe(1).


6.3.    PCMCIA Drivers (PCMCIA = PC-Card)

Distributing pre-compiled PCMCIA drivers would be a significant hassle.  It
is complicated because some features can only be selected at compile time,
and because the modules are somewhat dependent on having the "right" kernel
configuration.

That's why you need to compile the PCMCIA driver by yourself. You can do this
by executing this command:  cd /usr/src/pcmcia-cs ; make config ; make all ;
make install
[FIXME! Is this still current?]

Activating the PCMCIA stuff is simply done by adding 'pcmcia' to your
runlevels (using the 'runlvedit' tool).  Note that PCMCIA is gradually being
integrated into the main linux kernel tree.  No matter how integrated PCMCIA
becomes, you will always need a small suite of userland tools. Thus, if you
have the need for PCMCIA support, also install the standalone PCMCIA
package.

Further information on the kernel, modules and supporting packages can be
found in:  
/usr/src/linux/README 
and
/usr/src/linux/Documentation/Changes


6.4.    The SAK (Secure Attention Key)

If the SAK key is pressed, all processes connected with the terminal are
killed and a new login is started. If you would like to use the SAK on the
console you need to apply this patch first to the keyboard map file. It binds
Ctrl-Alt-Backspace to the SAK.

 keycode  14 = Delete           Delete
	control keycode  14 = BackSpace alt     keycode  14 = Meta_Delete
+       control alt keycode  14 = SAK
 keycode  15 = Tab              Tab
	alt     keycode  15 = Meta_Tab

Never use the SAK when an XFree86 Server is running! The server wouldn't
reset the video board and this makes your console unuseable.  It is possible
that SAK kills the gpm daemon (or others).



7.    System V Init Configuration


7.1.    Runlevels

ROCK Linux has a nice runlevel editor: just type "runlvedit" - you will like
it! Set the environment variable EDITOR to your favourite editor first.

The runlevel 'b' contains stuff which will be started at boot time and
stopped at system shut down. This runlevel should contain only stuff which
_does_not_ start any daemons. You should use this runlevel to set up raid
systems or similar stuff (if you can't do it in '/etc/conf/kernel').


7.2.    Bootup and Shutdown

The file /etc/conf/bootdown contains a few settings for the system bootup and
shutdown scripts.




8.    Framebuffers, X11 and DRI


8.1.    The kernel framebuffer devices

Since 2.1.108 Linux supports framebuffer devices on x86 PCs (framebuffer
devices for other architectures long before that).  You can use the
framebuffer drivers from the official kernel by enabling the appropriate 
driver in the 'Console Drivers' | 'Framebuffer support' in the kernel
configuration menu. With a decent graphics card, you get a nice, crisp,
hi-resolution text-console with room for plenty more text than the default
VGA resolution offers. Make sure you read the apropriate documentation in
/usr/src/linux/Documentation/fb/ as well. To get a hi-resolution
console, you also need to edit /etc/lilo.conf in order to pass the correct
options to the framebuffer driver.

There are other excuses for running a framebuffer device, than the 
framebuffer console.

Sometimes, a graphics card is not directly supported by XFree86, but 
your card is VESA 2.0 compatible. In that case, you can build a kernel 
with framebuffer support for VESA 2.0 compatible cards, and run the 
Xserver with the framebuffer module loaded. (See below)


8.2.    XServer (XFree86)

ROCK Linux comes with the XFree86 Xserver. (Currently 4.0.x)
One notable difference between XFree86 3.3.x and 4.0.x, is that 4.0.x
has just one Xserver, whereas 3.3.x had many. Instead of using one
particular Xserver supporting your particular (family of) graphics,
you load the apropriate modules for your hardware.

The XFree86 server can easily be configured with the xf86config script,
which is the way it has been done for a very long time with the XFree86
Xservers. With the release of 4.0.1, you also get the option of autoprobing
the graphics and get a suitable skeleton for the configuration file.
(/etc/X11/XF86Config)
To build the skeleton file, make sure X isn't running, and execute
XFree86 -configure       as root.
The configuration file gets written to /root/XF86Config.new.
You will most likely want to edit this file, before copying it into
/etc/X11/XF86Config

In particular, you may want to add additional modules in the
"Modules" section, like `v4l`, and you definitely want to add 
HorizSync and VertRefresh to the "Monitor" section.
The former is a range in kHz, the latter a range in Hz.
This is one of the very few places where it is possible to destroy
hardware by issuing the wrong keystrokes at the keyboard. Please check
your monitor vendor's documentation and do not exceed the ratings given
for your monitor.

Unless you want to play with oddball resolutions, the default (not listed)
modelines should be sufficient for most people. But you still want to
tell X what depth and resolutions you want to be able to use. My
Screen section looks like this:

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultDepth 16
        SubSection "Display"
                Depth     16
                Modes   "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth     24
        EndSubSection
EndSection



8.3.    DRI

DRI is the Direct Rendering Infrastructure.  This is needed for hw-accellerated 
OpenGL. [FIXME: expand on this]
Also see http://dri.sourceforge.net/


8.4.    Windowmanager

The default work-environment of ROCK Linux is the sawfish windowmanager in 
combination with GNOME. If you don't like sawfish/GNOME you can use the X11 
standard widowmanager 'twm' or build your favorite windowmanager (f.ex. IceWM)
from the sourcecode. To use 'twm' just set the
enviroment variable 'USE_TWM' to a non-zero value when starting X11 with 'xdm'
or 'startx'.  In the default twm configuration of ROCK Linux you can open an
xterm window with right-clicking the root window (i.e. the "desktop").

In order to use your favorite wm, build and install it, then create a file
in your home directory named .xinit.

The authors .xinit contains:
#!/bin/sh
export PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11/bin:
exec /usr/local/bin/icewm

Copy this file to .xsession, and the "right thing" happens no matter if you
start X with xdm or startx.



9.    Package management


9.1.    Package information

All administration information about packages can be found in the directory
/var/adm/. Here you can find the following directories and files:

  /var/adm/flists/{packagename}      A list of the files of this package
  /var/adm/packages/{packagename}    Common package information
  /var/adm/cksums/{packagename}      Checksums - created with 'cksum'
  /var/adm/md5sums/{packagename}     Checksums - created with 'md5sum'


9.2.    Installing and removing packages

To install or remove packages just use the commands 'pkg-install' and
'pkg-remove'.  After installing or removing packages you should always run
the '/usr/sbin/cron.run' script to update some system files.
[FIXME! Is this still current?]


9.3.    Packages in the RPM format

If you want to use RPM or SRPM packages you should use the programs
'rpm2cpio' and 'cpio -i -d' to extract it somewhere. Then install
the stuff manually (to '/opt/' or '/usr/local/').

The 'rpm' program from RedHat is included in ROCK Linux to give you the
possibility to convert RPM packages and/or extract them somewhere.  Please
don't use rpm directly to install packages.


9.4.    Finding modified files

To find modified or new files in the directories 'bin boot etc lib sbin usr
var' just execute the 'pkg-diff' programm. It doesn't make sense to search in
the other directories since no ROCK Linux package installs files in them.

If you want to create an "overlay" - a tarball with all changed files which
you can install on another, identical machine - you can do it like this:

cd / 
pkg-diff / > tmp/big-file-list.txt 
vi tmp/big-file-list.txt  (strip the file for non-interesting files.) 
tar czf tmp/big-archive.tar.gz -T tmp/big-file-list.txt




10.    ROCK Linux and standards

10.1.    Does ROCK Linux obey the FHS standard?

Sort of. With ROCK Linux I try to follow the FHS (Filesystem Hierarchy
Standard). The homepage of the FHS is <http://www.pathname.com/fhs/>. The
ASCII version of the FHS can be found in this directory as 'fhs.txt'.

However - ROCK Linux isn't fully complient with the standard:

 *) A few applications don't support the FHS yet - so I can't guarantee
    that everything is in the right place.

 *) I only take care that all man pages goes to /usr/share/man - to put
    the manual page in the right subdirectory here is up to the package
    makefile.

 *) To guide the user to the new locations and make sure that the packages
    place their files in the right directories I've created a few symlinks:

       /usr/doc           -> /usr/share/doc
       /usr/man           -> /usr/share/man
       /usr/info          -> /usr/share/info
       /usr/opt           -> /opt
       /usr/spool         -> /var/spool
       /usr/tmp           -> /tmp
       /var/spool/locks   -> /var/lock
       /var/spool/mail    -> /var/mail

*) Since a few packages need a /usr/libexec directory, I've created one. The
   FHS does not explicitly forbid such a directory - but from the FHS
   philosophy this stuff should go to /usr/lib/<something>.

*) Most of the FHS implementation is up to the packages - not to the ROCK
   build scripts. But I've tried to do the most importand stuff ...


10.2.    Why isn't there a real package management system? Or is there?

RPM is installed. However, it is not recommended to use RPM to install
software directly on a ROCK Linux distribution. Most RPMs will install stuff
somewhere in /usr, while software which is not part of the distribution
*should* go into /opt.

A simple package management system *is* installed. Please see the appropriate
section of the FAQ, which also explains how to make use of RPMs if you cannot
compile the software yourself.




11.    ROCK Linux roadmap.


11.1.    What does the future hold for ROCK Linux?

This is (and will remain) a moving target. Please see

  http://www.rocklinux.org/misc/TODO

for a more or less up to date roadmap.





---
Clifford Wolf
http://www.clifford.at/
