I think if you check the makefile in the bw_pipe/ directory, you'll find that it already does most of what you need. Saying 'make' in bw_pipe/ will cause an erosimg file to get built.
If you have a disk partition dedicated to EROS, and you set the environment variable EROS_HD to the name of that partition, e.g.
setenv EROS_HD /dev/hda1
and then type:
make init.hd # first time only -- "formats" the EROS partition make test.hd # when installing a test -- "populates" the EROSpartition
and then boot the EROS partition, the test should run fine.
My suggestion is to chmod the EROS partition device file to 666 so that you do not have to do this as root; it's too easy to typo the environment variable and wipe out something important.
Please note that I have recently discovered (but not yet fixed) a bug in the cross tools. The net effect is that process root nodes do not get fabricated correctly. It is not clear why this is happening, and I'll have to track it down this weekend.
Bengt Kleberg <email@example.com> on 02/04/99 07:28:03 AM
To: Jonathan S Shapiro/Watson/IBM
Subject: Re: generating installation image
> I'ld suggest that before you try to do one yourself you pick one of the
> test cases and try that. The pipe bandwidth test (tests/perf/bw_pipe)
I have managed to give some time to EROS. In accordance with your recommendation I have attempted to try and put the bw_pipe test case on a floppy. A few questions have arisen.
The Makefile creates an image. I then need to create a volume. The volume should be described in a volmap file. There is no such file in the bw_pipe directory. To construct one myself I have decided to use the src/base/tests/perf/bench.volmap as a template.
According to the Cross Development Guide, Crafting a System Image, the volmap can have various 'identifiers' (kernel, divtable, boot...).
My template only has kernel, cklog and object. cklog is not mentioned at all in the manual. I thought that a boot and divtable entry would both be neccessary, no? If not, how much should I estimate their space needs to?
The size of the kernel should be possible to calculate from the image. But how should I do that? I then intend to give the rest of the floppy to object (after boot and divtable have gotten their share)
Finally, if I should have a boot entry, I need to indicate at the boot entry what boot code (file) that should go there. No volmap file I have found seems to do this.
> I'll work on putting together a clean image in sysimg/ this weekend.
Did this happen? I have seen nothing on the eros-port mailing list.
Best Wishes, Bengt