---------- Forwarded message ----------
From: Lisa Hsu <[EMAIL PROTECTED] >
Date: Oct 26, 2005 11:10 AM
Subject: linux-dist
To: [email protected]
hi everyone,
a few people have asked about linux-dist, so i've posted the tarball at
http://m5.eecs.umich.edu/dist/linux-dist.tgz
just to let you know, this is something we grew out of the PTXdist package, version 0.7. the differences mostly are just from adding new applications that we wnated to build on the image, as well as automatic specweb fileset creation, and probalby some other things i don't remember. however, since we've got a working image, we no longer use linux-dist and it's sort of broken.
here's how linux-dist used to/is supposed to work:
1 if build cross-compiler, build cross compiler (including binutils, glibc, all that jazz)
2 use said cross-compiler to build everything specified by user, like kernel, libraries, utilities, applications
3 mk a blank disk image
4 mount image, copy everything onto it
5 if specified, make specweb fileset and copy it onto disk image
The broken part is, the cross-compiler we build in linux-dist is incapable of building everything we tell it without errors.
what we mostly do now is take a current image, cross-compile some benchmark or application we want to add to our disk image, and mount the image and copy it in. (more detailed instructions can be seen in our powerpoint tutorial, which you can get a link to from m5.eecs.umich.edu). however, if this is not sufficient for you or you want to use linux-dist, one possible solution is to build a cross compiler on your own, outside of the linux-dist package, point linux-dist to that cross-compiler, and then use linux dist to do steps 2-5. or, if you want to take a crack at fixing linux-dist so it is a stable image building solution from steps 1-5, that would be awesome too.
a few people have asked about linux-dist, so i've posted the tarball at
http://m5.eecs.umich.edu/dist/linux-dist.tgz
just to let you know, this is something we grew out of the PTXdist package, version 0.7. the differences mostly are just from adding new applications that we wnated to build on the image, as well as automatic specweb fileset creation, and probalby some other things i don't remember. however, since we've got a working image, we no longer use linux-dist and it's sort of broken.
here's how linux-dist used to/is supposed to work:
1 if build cross-compiler, build cross compiler (including binutils, glibc, all that jazz)
2 use said cross-compiler to build everything specified by user, like kernel, libraries, utilities, applications
3 mk a blank disk image
4 mount image, copy everything onto it
5 if specified, make specweb fileset and copy it onto disk image
The broken part is, the cross-compiler we build in linux-dist is incapable of building everything we tell it without errors.
what we mostly do now is take a current image, cross-compile some benchmark or application we want to add to our disk image, and mount the image and copy it in. (more detailed instructions can be seen in our powerpoint tutorial, which you can get a link to from m5.eecs.umich.edu). however, if this is not sufficient for you or you want to use linux-dist, one possible solution is to build a cross compiler on your own, outside of the linux-dist package, point linux-dist to that cross-compiler, and then use linux dist to do steps 2-5. or, if you want to take a crack at fixing linux-dist so it is a stable image building solution from steps 1-5, that would be awesome too.
lisa
