Re: mol-0.9.55 uploaded


Subject: Re: mol-0.9.55 uploaded
From: Philippe Lelédy (phl@leledy.org)
Date: Sat Jan 27 2001 - 12:53:40 MST


On Fri, 26 Jan 2001, Samuel Rydh wrote:

>
> I've uploaded the 0.9.55 version (the nvram image name
> bug has been fixed). Once I get confirmation that this
> version works well, I'll update the web site. Until then,
> it can be found in the FTP directory.
>

I'm afraid I've the same problem than previously.

Furthermore I don't understand well the nvram issue.
I found no mention of nvram in recent molrc.

One more strange issue: rpm -Uvh mol-9.55 didn't install the rpm molrc
but leaves in place the previous molrc. It's the first time this occurs.

Here is what happens: (2.4.0test11, MacOS 9.04)

startmol
Mac-on-Linux 0.9.55, (C) 1997-2000 Samuel Rydh <samuel@ibrium.se>
Removing stale lockfile /var/lock/mol

Version 0.9.55
MOL kernel module 1.1.55
Resource file: /etc/molrc
Library directory: /usr/lib/mol
Using ADB keycodes
OF device tree: oftrees/oftree.nw
96MB RAM mapped at 0x20000000
Running in PowerPC 750 mode (G3)
DEC frequency: 25 MHz, 250:10 mticks/usec
Using nvram-image 'nvram/nvram.nw'
Running on VT 9.
Using usb mouse on /dev/usbmouse
Cache enabled for console-video
Video module 'console_video' installed.

MODE: 1024* 768, depth 32 { 75.0 } Hz

No video mode match the default one.
Starting in video mode 1024*768, depth 32, 75.0 Hz [offs:0, rb:4096]
Autoswitching to console
Ethernet Interface (port 1) 'sheep-<tap0>' @ FE:FD:DE:AD:BE:EF

HFS disk: 0 MB, images/moldisk.im [read-only]
----> (disk_open) Opening /dev/cdrom: No medium found
HFS disk: 9216 MB, /dev/hdb10 [read-write]
HFS disk: 3072 MB, /dev/hdb9 [read-only]
HFS disk: 1200 MB, /dev/hdb6 [read-only]
HFS disk: 1200 MB, /dev/hdb5 [read-only]
HFS disk: 1000 MB, /dev/hda10 [read-write]
HFS disk: 100 MB, /dev/hda9 [read-write]
HFS disk: 300 MB, /dev/hda8 [read-write]
HFS disk: 300 MB, /dev/hda7 [read-write]
HFS disk: 400 MB, /dev/hda5 [read-write]
HFS disk: 400 MB, /dev/hda6 [read-write]

Mapping GC at 80800000
Starting emulation...

**** SIGNAL Hangup in thread async-io thread ****
Exiting due to a crashed thread
cleaning up...
**** SIGNAL Hangup in thread <non-registered thread> ****
**** SIGNAL Hangup in thread startboing ****

I answer Samuel: "SIGNAL Hangup" is spontaneous.

Salutations.
----------



This archive was generated by hypermail 2a24 : Sat Jan 27 2001 - 12:54:50 MST