Menu
▾
▴
Re: [coLinux-users] Urgent CO_RC_ERROR_ERROR message.
|
From: John F. <J.P...@as...> - 2005-11-01 13:11:34
|
Date sent: Mon, 31 Oct 2005 10:52:14 +0000 From: Nuno Lucas <nt...@gm...> To: Sam Moffatt <pa...@gm...> Subject: Re: [coLinux-users] Urgent CO_RC_ERROR_ERROR message. Copies to: John Fletcher <J.P...@as...>, col...@li... On 10/31/05, Sam Moffatt <pa...@gm...> wrote: > I was initially going to say that but he said it was an > upgrade...perhaps its something more given there have been a few ot > these recently? The specific error he pointed out is a "file not found error". This is the most common of all colinux errors since the beginning, so can't tell if they are more or less common recently. There was a bug in the initrd loading code that would make colinux loading fail in specific conditions, but that is old. All I can say is that if the error persists, to comment the initrd thing (it's only needed on first boot, anyway). Regards, ~Nuno Lucas > > On 10/31/05, Nuno Lucas <nt...@gm...> wrote: > > On 10/31/05, John Fletcher <J.P...@as...> wrote: > > > I have been updating my CoLinux to 20050524 (0.6.3 pre 13) and I > > > now get the following message when I try to start up. > > > > > > CO_RC_ERROR_ERROR line 33 colinux/os/current/user/file.o > > > > It's the colinux way of saying it failled to open some file, > > usually a bad path in the config, like a typo, bad file > > permissions, etc. > > > > Regards, > > ~Nuno Lucas > > Thanks for all the help. My messages were caused by misspelling the name of the configuration file. It would help if the error message said "file error" more directly, and even echoed back the failing name. Would this be possible for a future release? Thanks again John -- Dr John P. Fletcher Tel: (44) 121 204 3389 (direct line) Chemical Engineering and Applied Chemistry (CEAC), School of Engineering and Applied Science (SEAS), Aston University, Aston Triangle, BIRMINGHAM B4 7ET U.K. CEAC Web site http://www.ceac.aston.ac.uk/ FAX: (44) 121 204 3679 |