One important configuration is specifying which HFS[+] volumes mol should use. This is done by editing the /etc/molrc file. Note that mol can access both HFS and HFS+ volumes (no kernel filesystem support is needed since the access since block-level access is used). In the following HFS stands for both HFS and HFS+.
blkdev: /dev/hda9 -rw
specfies that the partition /dev/hda9 should be mounted r/w in mol. If /dev/hda9 does not contain a HFS filesystem, it will be ignored unless the '-force' switch is used. The force switch is useful primarily when a partition is to be initialized by MacOS. A line like
blkdev: /dev/sda -rw
(sda is the first SCSI disk, hda the first IDE disk) is equaivalent to:
blkdev: /dev/sda1 -rw
blkdev: /dev/sda2 -rw
blkdev: /dev/sda3 -rw
If a particular disk has many partitions, make certain all the individual partitions have entries in /dev/. The startup disk is specified by adding a '-boot' flag, e.g.
blkdev: /dev/cdrom -cd -boot
The above line is suitable for booting MacOS from the installation CD. If no boot partition is specified, mol will search for a bootable disk among the available HFS disks.
The pdisk utility (/sbin/pdisk) can be used to find out the partition numbers of HFS volumes (but be careful - pdisk is a tool to edit the partitioning of your harddisk!). It might be simpler to just use the /dev/sda syntax. Mol will print out the exact partitions when it examines the device.
Note: If a CD/DVD device is exported, e.g. 'blkdev: /dev/cdrom -cd -boot', then you might experience a freeze if you try to start mol with a non-data CD in the CD player. This is due to a kernel bug.