what is the minimum size to install text based compile tools

We have a project that is using a PC104 card, and can have flash IDE drives
from 32Mb to 128Mb.

If I only want to put the application, and simple tools in a boot image I
could fit it all on a single floppy size flash, or a small portion of the
32M flash disk.

I was wondering though… What would I have to put on a flash hard drive to
be able to do minimal development on the system itself… say, jed for an
editor, and the compiler set, not the full photon development suite???

Is there a simple way to “install” a minimal qnx system from the package
files on the CD?

Thanks,

John

Hi,
First the easy answer. No, there isn’t any way to customize the
installation directly from the QSSL distribution. I asked that question in
the advocacy newsgroup and that was the answer I received. Every install is
a full desktop install. You’ll have to do what I do. Install it to a hard
drive, make the image with what you need, then transfer it to the flash.
Once you get the files on the hard drive, you can use du to estimate the
sizes of the directories you want to include in the final image. I’d
multiply by 2 to give you a good margin on the flash device. The contents of
/bin, /sbin, /lib, /usr/bin, and /usr/sbin will get you started and you can
get rid of a lot from within those directories.
My real question is why do you want to develop applications on the flash,
rather than on a hard drive attached to the cpu?

Regards,
David Kuechenmeister

“John Eddy” <john.h.eddy@lmco.com> wrote in message
news:b8lraf$lq4$1@inn.qnx.com

We have a project that is using a PC104 card, and can have flash IDE
drives
from 32Mb to 128Mb.

If I only want to put the application, and simple tools in a boot image I
could fit it all on a single floppy size flash, or a small portion of the
32M flash disk.

I was wondering though… What would I have to put on a flash hard drive
to
be able to do minimal development on the system itself… say, jed for an
editor, and the compiler set, not the full photon development suite???

Is there a simple way to “install” a minimal qnx system from the package
files on the CD?

Thanks,

John

David Kuechenmeister <david.kuechenmeister@viasat.com> wrote:
DK > Hi,
DK > First the easy answer. No, there isn’t any way to customize the
DK > installation directly from the QSSL distribution. I asked that question in
DK > the advocacy newsgroup and that was the answer I received. Every install is
DK > a full desktop install. You’ll have to do what I do. Install it to a hard
DK > drive, make the image with what you need, then transfer it to the flash.
DK > Once you get the files on the hard drive, you can use du to estimate the
DK > sizes of the directories you want to include in the final image. I’d
DK > multiply by 2 to give you a good margin on the flash device. The contents of
DK > /bin, /sbin, /lib, /usr/bin, and /usr/sbin will get you started and you can
DK > get rid of a lot from within those directories.
DK > My real question is why do you want to develop applications on the flash,
DK > rather than on a hard drive attached to the cpu?

DK > Regards,
DK > David Kuechenmeister

Since this kind of thing comes up a lot, here is my recommendation.

Have one system that is your install base system. Use the QNX package
install methods to get everything that you might need onto that
system.

Then write your own install scripts to install only the pieces of
software that you know you require. I have a installQNX,
installDevelopment, installPhoton, installApps. Here is how I do it.

Have a boot floppy of CD that will bring a new system up AND bring up
networking. Get it talking to your install base system. Execute the
scripts from your base system on your new system to do any partitioning,
dinit’ing, and copying that your scripts require.

PLUSES & MINUSES

If you do this the big downside is that if you ever try to upgrade
these systems you must have a much better knowledge of what depends on
what. The first upside is that you will have a much better knowledge
of what depends on what. Another big plus is that program loading will
be much faster since it no longer has to go through an extra file
system (the package file system).

And of course the final big advantage is that you now have a system
that includes only those things that you require.