Re: CVS status

Riley Williams
2002-07-15T05:59:03Z

Hi Harry.

>>> I tried the CVS version of elks this afternoon and it fails to
>>> load init. Is there a known issue?

>> Got the cvs Image working mostly under bochs (my keyboard sometimes
>> doesn't work) However cvs will boot and load init on the root file
>> system from your site, and load the filesystem and start the EDE
>> stuff.

> The problem comes from the new images produced by the elkscmd
> package. I tried the old made root/boot disks from the site with the
> new kernel and it works, as you state.
>
> A closer look shows that the new MAKEDEV script in the root_template
> has some problems(Replacing the new /dev with the /dev from the site
> floppies solves the problem). I don't have the time see what is
> wrong right now, but I suggest more carefull and tested commits from
> now on.

I would presume this was my fault as I tweaked the MAKEDEV script a
while back, but have to report that the resultant script worked fine on
my test system.

The only possible problem that I can see is that the MKSET definition
near the top of the file used a relative path for the MAKESET auxilliary
script, and that shouldn't be the problem as the remaining mknod lines
require that relative path to be correct. However, if the MAKESET script
is missing, that would be a problem.

I've replaced the definition with an absolute path to be safe, so if
that was it, then it isn't now. I've also included a check that the
auxilliary MAKESET script is actually present, displaying an error
message and aborting if not.

Harry: As my testing of this is obviously unreliable, can you check this
out for me please, and advise regarding the results so we can get this
problem sorted out.

Best wishes from Riley.