I finally put the hard yards into getting CHAOS (openMosix
distribution) and coLinux together, into CosMos;
However, two things trouble me;
CHAOS runs entirely from initrd. There is no root. With
CosMos, under coLinux, I can find no way to get either an
init.rdz or an init.fs to load per my understanding of the initrd
docs (that the initrd stays mounted as root until the linuxrc/
init release it, and let the kernel mount the real root).
ie; the CHAOS isolinux APPEND line (for the kernel params)
initrd=/chaos/chaos.rdz root=/dev/ram0 rw
So I would expect a config.xml of;
<initrd path="initrd.fs" />
<!-- <block_device index="0" ..... /> -->
.. to be equivalent ... but the best I can get is an error
that seems to indicate that either /dev/cobd0 has no
FS on it, or that /dev/ram0 has an unrecognisable FS on
it. I have even tried cases where a 1Mbyte ext2fs root
(empty) was made available to cobd0, but it didn't help.
I have no issues when I make the initrd a plain old root fs,
but this is undesirable (this is how the above exe is
I have now seen a case locally, that was previously
reported remotely, where the TAP driver doesn't install
using the devcon method - instead requiring an Add
Hardware intervention (under XP in both cases). Is this
typical? Others have seen this? Is there a better way to
install the driver?
I'd like something more reliable if I can get it (or, can I
check for a condition in the registry to see if the user is
going to have this fault, and notify them, before they
stumble across it? -- like a patch or setting?).
Thanks -- 0.6.1 looks pretty sweet Dan, you're a dude.
Internet and Networking Security Officer