From: Ian L. <Ian...@mq...> - 2004-07-22 01:11:23
|
Hi all, I finally put the hard yards into getting CHAOS (openMosix distribution) and coLinux together, into CosMos; http://itsecurity.mq.edu.au/cosmos/setup-0.1.4.1.exe However, two things trouble me; 1. INITRD 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) includes; initrd=/chaos/chaos.rdz root=/dev/ram0 rw boot=/dev/cdrom:iso9660 init=/sbin/init So I would expect a config.xml of; <initrd path="initrd.fs" /> <bootparams>root=/dev/ram0 rw</bootparams> <!-- <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 configured). 2. TAP 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. -- Ian Latter Internet and Networking Security Officer Macquarie University |
From: Dan A. <da...@gm...> - 2004-07-22 20:53:09
|
On Thu, Jul 22, 2004 at 12:21:17PM +1000, Ian Latter wrote: > I finally put the hard yards into getting CHAOS (openMosix > distribution) and coLinux together, into CosMos; > > http://itsecurity.mq.edu.au/cosmos/setup-0.1.4.1.exe Very nice. > ie; the CHAOS isolinux APPEND line (for the kernel params) > includes; > initrd=/chaos/chaos.rdz root=/dev/ram0 rw > boot=/dev/cdrom:iso9660 init=/sbin/init > > So I would expect a config.xml of; > <initrd path="initrd.fs" /> > <bootparams>root=/dev/ram0 rw</bootparams> > <!-- <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. Did you try it without "root=/dev/ram0 rw" ? I don't see why it's needed. -- Dan Aloni da...@co... |