I've the following to do:
* test Oxygen (glibc 2.1.3) with CDROM style loading
* replace ps (segfaults) with busybox ps
* bulletproof (?) config file some more
* shift release designator to 1.7-devel
* burn CDROM and release
I've snarfed the patches for 2.4.0-test11 that Charles had and put
them on the disk. All the data is there; everything is close to ready
to go.
All but the bulletproofing will need to be done and won't take very
long at all. Bulletproofing can go on forever :-)
Here's the configuration file I've been using (attached).... The only
parameter needed on the kernel command line is CONF= and the usual
kernel parameters (INITRD_ARCHIVE, RAMDISK_SIZE, etc.) Does anyone
know if ROOT= is one of these? I suspect it is...
This configuration file has totally cleared out the kernel command
line - what a relief!
// This is the Oxygen configuration file. It can be edited like any
// other text file.
// Test configuration
// Comments start with one of:
// .....this; or
# ......this; or
-- .....this
// and can be put at the end of any line.
// There are two "blocks" that need to be defined... volume and source.
#----------------------------------------
# VOLUME BLOCKS
#----------------------------------------
// The volume block defines each disk volume in the system. In particular,
// it fills in the /etc/fstab. Multiple volume blocks are necessary, and each
// successor adds one more volume to the /etc/fstab.
//
// The disk keyword specifies the device name.
//
// The mountpoint keyword specifies where the disk is to be mounted.
//
// The filesystem keyword specifies which filesystem to use.
//
// The options keyword specifies any options to be used in /etc/fstab.
//
// The mount keyword will make the system actually MOUNT the specified
// device or mount point. With this, you can control exactly when
// each device is mounted, if you want.
//
// The size keyword specifies the actual size of the volume in megabytes.
// The megabytes keyword can also be used instead. For most volumes,
// this makes no sense; for RAM volumes it is necessary.
volume {
disk /dev/ram0
mountpoint /
filesystem minix
options rw,noauto
megabytes 12
mount
}
volume {
disk /dev/ram1
mountpoint /var/log
filesystem minix
options rw,noauto,nodev,nosuid
megabytes 4
mount
}
volume {
disk /dev/ram2
mountpoint /tmp
filesystem minix
options rw,noauto,nosuid
megabytes 4
mount
}
volume {
disk /dev/fd0u1440
mountpoint /mnt/floppy
filesystem msdos
options rw,noauto,nodev,noexec,nosuid
}
volume {
disk /dev/fd0u1680
mountpoint /mnt/fd0
filesystem msdos
options rw,noauto,nodev,noexec,nosuid
}
volume {
disk /dev/fd1u1680
mountpoint /mnt/fd1
filesystem msdos
options rw,noauto,nodev,noexec,nosuid
}
volume {
disk /dev/cdrom
mountpoint /mnt/cdrom
filesystem iso9660
options ro,noexec,nosuid
mount
}
volume {
disk /dev/boot
mountpoint /mnt/boot
filesystem msdos
options rw,noauto,nodev,noexec,nosuid
}
volume {
disk /dev/backup
mountpoint /mnt/backup
filesystem msdos
options rw,noauto,nodev,noexec,nosuid
}
#----------------------------------------
# SOURCE BLOCKS
#----------------------------------------
// Each source is a disk, and each one must be specified, and in the
// following format. The format is "free-form" *ONLY* within a line...
// There can be multiple sources.
source {
// image
// prompt "Enter a new disk hubba hubba..."
// decompress bzunzip -c
device /dev/fd0u1680
config config.lrp
packages *.lrp
}
// The above example will load all packages named *.lrp from the disk
// device /dev/fd0u1680.
//
// The package keyword makes no assumptions about the name given;
// the packages can be named *.tgz or *.lrp or anything at all, as long
// as the proper files are contained within and the file was created by
// tar and subsequently compressed by gzip. However, only ONE entry
// is allowed, but multiple packages keyword lines are allowed.
// If no packages keyword line is used, the default is to load
// everything from disk that matches "*.lrp" ...
//
// The packages keywords should come last.
//
// The diskwait (prompt, wait) parameter can be added to wait before mounting;
// however this parameter MUST come before any "packages" in order to be
// effective. A text prompt is optional.
//
// The image parameter can be added to read the entire disk in as an image
// prior to loading packages; again this MUST come before any "packages"
// entries in order to be effective.
//
// The url keyword will support loading packages over the network;
// however, this is not yet present.
