This appears to be a bug, although I can't understand why everyone doesn't
get stopped by it:
When I boot, Aurora shows a menu on the left side and then stops
with no way to interact with it. Looking at the output on console 12 indicates
that it started Aurora before root was remounted as rw. It finally stops when
trying to start the system logger.
My Matrox Millennium system supports frame buffering (/proc/fb is present
and contains "0 MATROX VGA"), but as I look through the /etc/rc.d/rc.sysinit
script, I see that the following section is starting Aurora even when root has
not yet been remounted rw:
Snippet from /etc/rc.d/rc.sysinit (commented if was added by me to work around
the problem and get booted):
# If the partition where Monitor resides is mounted, we are able to
# start Aurora at this point. Otherwise, we'l have to wait until it is
# mounted...
if [ -n "$aurora" ] ; then
# if [ "$(grep -s /root\\\ /proc/mounts | grep -c \\\ rw\\\ )" == "1" ] ; then
aurora_start
# fi
fi
Is this problem related to the inability of the system to automatically figure
out that I have 8 MB of VRAM on my Matrox card instead of 4 MB?
The output on terminal 1 finishes with the lines:
....
Mounting proc filesystem...
Setting default font...
Booting Aurora...
The output on terminal 12 is the following:
Init: Entering run level: 5
/etc/rc.d/rc: /var/run/runlevel.dir: Read-only file system
Loading Harddrake
.....
<more expressions of unhappiness at the root filesystem being unreadable>
.....
Mounting other filesystems
Starting system logger:
Any ideas?
Craig Van Degrift
