cAos Community Wiki Please log in to access full functionality  



Installation of cAos 2 is done via the Cinch system installer. Cinch is a basic core file system installer that is used for implemention of a minimal core system. It allows for post install configuration using the system administrators assistant "Sidekick".

Creating the installation media

To install cAos 2 you must obtain the Cinch ISO image from the cAos-2/install/ directory of the mirrors. Download the latest version and save it locally (note: if using a web browser, make sure you save it while holding your shift key, or it will not download as binary).

Once the ISO image has been downloaded, you will need to burn the image to CDROM media. For this example, I will demonstrate using ‘cdrecord’.

cdrecord dev=/dev/hdc speed=16 -eject cinch-3.0.0.i386.iso

note: This assumes the CDROM writer is at /dev/hdc, and that the system is running Linux-2.6.

Starting Cinch

Put the newly created CDROM into the system to be installed, and turn it on. If it does not automatically boot with Cinch, you should adjust the boot order in the BIOS to boot from CDROM sooner.

Once the CDROM boots you will be presented with the Cinch boot screen. This screen will wait for user input. The splash screen will show the options, but if you are unsure, just pressing [ENTER] will assume the defaults which work for most installs.

As Cinch boots, it probes for SCSI and storage devices, and does some basic level configuration, then it goes into the main installation menu.

Option1: Configure local disk(s)

Option2: Install the core file system

Option3: Bootloader installation

Option4: Configure your new system with "Sidekick"

Option5: Drop to shell

Option6: Exit and reboot

At logging in for the first time you are requsted for a root password, this password will be entered with your keyboard in the "US-mode". There after you are requsted to select your type of keybord i.e. US, Dutch, Swedish e.t.c. Keep this in mind the next time you are logging as root as it implies that you may mix up your password with a keycombination. Keyboard Configuration

If you installed X and a window manager on your system, now you should be able to start your x-window manager with the command: startx If this does not work you can create your own config file. X Server Configuration

You can also bootstrap a system using yum. Read the instructions on bootstrapping with yum

From the command line you can reconfigure your system, or install more packages, by logging in as root and giving the "sidekick" command.

Posted messages

Top Hide all
author message
Installing 2-2.3a-test3 on a Compaq Proliant 6400R server.
on: 2005-11-26 [14:40 UTC] score: 0.00
The following are the steps I had to take to install cAos 2-2.3a-Test3 on a Compaq Proliant 6400R server with a Compaq Smart Array 4200 Controller using Logical Volume Management:

Cheat and se the Fedora Core install disk to recreate LVMs. Resulting in harddisk with two partitions – first one the boot partition and the
second the LVM partition.

Boot cAos install.

Drop to shell and then create /dev/ida directory and then create device
nodes – ie mknod c0d0 b 72 0, mknod c0d0p1 b 72 1 and mknod c0d0p2 b 72 2

Involke lvm.static and then execute commands vgscan and then vgchange -ay

VERY IMPORTANT (As I eventually discovered!) if you used Fedora to
create ext3 paritions you must now reformat them! For me this was
/dev/ida/c0d0p1 and all the logical volumes under /dev/LogGroup00/
(except the swap partition) and as I couldn’t find mkfs.ext3 I used
mkfs.ext2 followed by tune2fs -j (Not sure whether you can do the
latter this at this stage – if not, treat as ext2 and see later) NB If
you fail to reformat cAos won’t load properly on reboot as Red Hat have "kindly" modified their versions of ext3!!! (Sounds a lot like
Microsoft’s "embrace and enhance" which I detest so much!)

For good measure, execute mkswap on your swap partition too.

Create the directory /newroot, then mount all your new partitions under
here and then involve swapon on your swap partition.

Create the file /cinch/etc/fstab listing all your new partitions and how
they should be mounted. For good measure, I copied this to
/newroot/etc/fstab too.

Exit the shell and install core file system.

Drop to shell and edit the grub file – in my case adding the
line (hd0) /dev/ida/c0d0

Edit grub.conf so it correctly references hd0,0 (and add a password if
you want). NB During one install it failed to copy the stage1 and 2
loaders from /lib/grub/i386-caos to /newroot/boot/grub and I had to do
this manually.

We will need to boot from floppy to install the bootloader – so grab a
spare floppy and execute the following:

# cd /usr/lib/grub/i386-caos
# dd if=stage1 of=/dev/fd0 bs=512 count=1
# dd if=stage2 of=/dev/fd0 bs=512 seek=1

Keep the floppy to hand for later.

The Proliant has quad processors, so execute yum install linux-smp followed by yum remove linux.i386

Exit and then continue install.

When prompted for network configuration enter dhcpd. Continue build.

When installation complete and presented with login screen, login and
edit /etc/sysconfig/network-scripts/ifcfg-eth0 if necessary – in my case
changing to static and adding entry for GATEWAY.

If you were unable to invoke tune2fs earlier, now invoke tune2fs -j on
all ext2 filesystems that you wish to add journalising (ie ext3) to.

Reboot with floppy in drive. Grub should load then type the following
to install bootloader:

grub> root (hd0,0)
grub> setup (hd0)

Then reboot without the floppy.

All being well, grub should start and then boot cAos! 🙂

Page: 1/1

Created by: gmkurtzer last modification: Thursday, January 26, 2006 [03:34:14 UTC] by JohnA

[ Execution time: 0.30 secs ]   [ Memory usage: 7.58MB ]   [ 46 database queries used ]   [ GZIP Enabled ]   [ Server load: 0.61 ]