From: Avi B. <avi...@gm...> - 2005-04-12 11:36:47
|
Hello again, I think writing a launcher that will use a default .ini file as command line parameters for colinux-daemon will indeed do the trick, though I have another problem now. I tried running colinux off my USB drive on a computer which doesn't have colinux already installed, and it won't boot. The output colinux gives is: ----------------------------------------------------------------------------------------------------------------- colinux: manager open: last error: The system cannot find the file specified. Cooperative Linux Daemon, 0.6.2 Compiled on Sat Feb 5 10:19:28 2005 using 'vmlinux' as kernel image configuring 32 MB of virtual RAM mapping cobd0 to \??\E:\coLinux\busybox.img kernel boot parameters: 'root=/dev/cobd0' colinux: manager open: last error: The system cannot find the file specified. daemon: exit code 87c09c01 daemon: error - CO_RC_ERROR_ERROR, line 39, file colinux/user/monitor.o (62) ----------------------------------------------------------------------------------------------------------------- The line used to run it: "colinux-daemon mem=32 kernel=vmlinux cobd0=busybox.img root=/dev/cbd0" This same line works fine on my personal computer which has colinux already installed with the win32 installer. Avi. On Apr 12, 2005 6:11 AM, Sam Moffatt <pa...@gm...> wrote: > This is a known issue, the proposed solution was to have a 'colinux > launcher' style application that determined where it was running from, > and filled the blanks and wrote out a configuration file and started > coLinux. > > I'm sure no one would object if you wrote a program to do such a task, > but that is the only method available at the moment. > > On Apr 12, 2005 7:36 AM, Avi Berkovich <avi...@gm...> wrote: > > Hello all, > > > > I want to boot a busybox image off a USB flash drive, and I stumbled > > over the following problem: > > > > if I omit the entire path to the dist image (in order to boot without > > depending on the host system) in the <block_device> element in the xml > > conf file, coLinux will go into Kernel Panic on boot with the error > > message: ``Cannot open root device "cobd0" or unknown-block(117,0) > > please append a correct "root=" boot option ". > > > > (By the way, my boot params: <bootparams>root=/dev/cobd0</bootparams>) > > > > For example, this works: <block_device index="0" > > path="\DosDevices\I:\coLinux\busybox" /> > > this doesn't: <block_device index="0" path="busybox" /> > > > > Ofcource, I run colinux-daemon.exe from the dist image path. > > > > Hope anyone else has already tried this, and maybe has other tips to > > using coLinux with a USB flash drive. > > > > Avi. > > |