Minimal load of photon - how?

I would like to start just enough photon to run my application on my
target, which is an AMD486-133 with 8 megs of ram (Jumptec
superMOPSpro). After installing QRTP (the machine already had QNX4
running so I installed qnxrtp.tar.F) I can log in to NTO ok, but can’t
run photon due to lack of memory. I am trying to get more of the
(discontinued) memory, but in the meantime is there any way to load
less photon? If I run pidin info I get 3316/7804 Kb, in other words
about 3.2 megs free with no photon running. If I slay a few possibly
uneeded processes I can get it up to about 3.5 megs, but ph -s still
won’t work. After one attempt I had Photon, phfontFA and fontsleuth in
memory, but only had 584 Kb free! Any suggestions? BTW, please don’t
assume I know which directories to run photon components from. Thanks
for your help.

Bruce Davis <bruce.r.davis@boeing.com> wrote:

I would like to start just enough photon to run my application on my
target, which is an AMD486-133 with 8 megs of ram (Jumptec
superMOPSpro). After installing QRTP (the machine already had QNX4
running so I installed qnxrtp.tar.F) I can log in to NTO ok, but can’t
run photon due to lack of memory. I am trying to get more of the
(discontinued) memory, but in the meantime is there any way to load
less photon? If I run pidin info I get 3316/7804 Kb, in other words
about 3.2 megs free with no photon running. If I slay a few possibly
uneeded processes I can get it up to about 3.5 megs, but ph -s still
won’t work. After one attempt I had Photon, phfontFA and fontsleuth in
memory, but only had 584 Kb free! Any suggestions? BTW, please don’t
assume I know which directories to run photon components from. Thanks
for your help.

Bruce,

I would start with a different approach to begin with. The first
thing I would do is create a full RTP development system on some other
PC. This should be relatively painless if you just use the windows
install (or if you happen to have a spare partition lying around).
the next thing I would do is to build a custom boot image and start
loading things from there. I can’t speak to the photon side of things
but looking at my stock RTP system things that I would get rid of
to make a smaller memory footprint include (some of these may not be
running depending on your system configuration):

fs-pkg – lay out your files manually on the spare partition or in
a new directory on your target machine.
slogger – unless you need logging in your environment
dumper – unless you need core files in your environment
mqueue – unless you need mqueue’s for your applications
pipe – unless you need pipe’s for your applications
devc-par – unless you need parallel port support
spooler – unless you need printer support
devc-XXX – unless you need serial port support
deva-XXX – unless you need audio support

The next thing to do would be to edit the photon startup script
(or write your own) so that it doesn’t start things like saver,
bkgdmgr and the like.

Hope this helps a bit … someone else from Photonland will be
able to help with more specifics about Photon itself.

Thomas

Thanks for your response. The information you provided is very useful
because now I know what all those processes do! Except for fs-pkg, which I
still don’t get - what does it do? Is it for downloading files into the
package filesystem? If I slay it seems to cause me to lose the path to the
shell commands?

Actually I do have a full development system on another PC which I am using
to develop my application. And I know I will have to eventually figure out
how to create a custom boot image. But I was hoping that I could just strip
down what is running on the target after a standard install and figure out
how to configure the way photon loads so it doesn’t load anything I don’t
need.

So I really need to know where the photon configuration files are and how to
modify them. Seems like I will need to know this either way (customized boot
image or screwing around with the standard install). Thanks.

Thomas Fletcher wrote:

Bruce Davis <> bruce.r.davis@boeing.com> > wrote:
I would like to start just enough photon to run my application on my
target, which is an AMD486-133 with 8 megs of ram (Jumptec
superMOPSpro). After installing QRTP (the machine already had QNX4
running so I installed qnxrtp.tar.F) I can log in to NTO ok, but can’t
run photon due to lack of memory. I am trying to get more of the
(discontinued) memory, but in the meantime is there any way to load
less photon? If I run pidin info I get 3316/7804 Kb, in other words
about 3.2 megs free with no photon running. If I slay a few possibly
uneeded processes I can get it up to about 3.5 megs, but ph -s still
won’t work. After one attempt I had Photon, phfontFA and fontsleuth in
memory, but only had 584 Kb free! Any suggestions? BTW, please don’t
assume I know which directories to run photon components from. Thanks
for your help.

Bruce,

I would start with a different approach to begin with. The first
thing I would do is create a full RTP development system on some other
PC. This should be relatively painless if you just use the windows
install (or if you happen to have a spare partition lying around).
the next thing I would do is to build a custom boot image and start
loading things from there. I can’t speak to the photon side of things
but looking at my stock RTP system things that I would get rid of
to make a smaller memory footprint include (some of these may not be
running depending on your system configuration):

fs-pkg – lay out your files manually on the spare partition or in
a new directory on your target machine.
slogger – unless you need logging in your environment
dumper – unless you need core files in your environment
mqueue – unless you need mqueue’s for your applications
pipe – unless you need pipe’s for your applications
devc-par – unless you need parallel port support
spooler – unless you need printer support
devc-XXX – unless you need serial port support
deva-XXX – unless you need audio support

The next thing to do would be to edit the photon startup script
(or write your own) so that it doesn’t start things like saver,
bkgdmgr and the like.

Hope this helps a bit … someone else from Photonland will be
able to help with more specifics about Photon itself.

Thomas

you don’t really need the package filesystem, the problem is when you slay it the virtual filesystem is gone. to work around that, copy the files that you need into a small filesystem with a dir structure the is the same as what you see with fs-pkg working.

for example
mount /dev/hd0t78 /mnt

then
mkdir /mnt/bin
‘’ /mnt/usr

then

cp /bin /mnt/bin

and put all the scripts where they make sense


Previously, Bruce Davis wrote in qdn.public.qnxrtp.installation:
{ Thanks for your response. The information you provided is very useful
{ because now I know what all those processes do! Except for fs-pkg, which I
{ still don’t get - what does it do? Is it for downloading files into the
{ package filesystem?

It’s a virtual filesystem that you can change versions upgrade, backdate
what ever. Look in the /pkgs directory ( try /pkgs/base/os/core2.X/x86)
those are the real files

{ If I slay it seems to cause me to lose the path to the
{ shell commands?
{
{ Actually I do have a full development system on another PC which I am using
{ to develop my application. And I know I will have to eventually figure out
{ how to create a custom boot image. But I was hoping that I could just strip
{ down what is running on the target after a standard install and figure out
{ how to configure the way photon loads so it doesn’t load anything I don’t
{ need.


use cp -r of all the directories BUT /pkgs

{
{ So I really need to know where the photon configuration files are and how to
{ modify them. Seems like I will need to know this either way (customized boot
{ image or screwing around with the standard install). Thanks.
{
{ Thomas Fletcher wrote:
{
{ > Bruce Davis <bruce.r.davis@boeing.com> wrote:
{ > > I would like to start just enough photon to run my application on my
{ > > target, which is an AMD486-133 with 8 megs of ram (Jumptec
{ > > superMOPSpro). After installing QRTP (the machine already had QNX4
{ > > running so I installed qnxrtp.tar.F) I can log in to NTO ok, but can’t
{ > > run photon due to lack of memory. I am trying to get more of the
{ > > (discontinued) memory, but in the meantime is there any way to load
{ > > less photon? If I run pidin info I get 3316/7804 Kb, in other words
{ > > about 3.2 megs free with no photon running. If I slay a few possibly
{ > > uneeded processes I can get it up to about 3.5 megs, but ph -s still
{ > > won’t work. After one attempt I had Photon, phfontFA and fontsleuth in
{ > > memory, but only had 584 Kb free! Any suggestions? BTW, please don’t
{ > > assume I know which directories to run photon components from. Thanks
{ > > for your help.
{ >
{ > Bruce,
{ >
{ > I would start with a different approach to begin with. The first
{ > thing I would do is create a full RTP development system on some other
{ > PC. This should be relatively painless if you just use the windows
{ > install (or if you happen to have a spare partition lying around).
{ > the next thing I would do is to build a custom boot image and start
{ > loading things from there. I can’t speak to the photon side of things
{ > but looking at my stock RTP system things that I would get rid of
{ > to make a smaller memory footprint include (some of these may not be
{ > running depending on your system configuration):
{ >
{ > fs-pkg – lay out your files manually on the spare partition or in
{ > a new directory on your target machine.
{ > slogger – unless you need logging in your environment
{ > dumper – unless you need core files in your environment
{ > mqueue – unless you need mqueue’s for your applications
{ > pipe – unless you need pipe’s for your applications
{ > devc-par – unless you need parallel port support
{ > spooler – unless you need printer support
{ > devc-XXX – unless you need serial port support
{ > deva-XXX – unless you need audio support
{ >
{ > The next thing to do would be to edit the photon startup script
{ > (or write your own) so that it doesn’t start things like saver,
{ > bkgdmgr and the like.
{ >
{ > Hope this helps a bit … someone else from Photonland will be
{ > able to help with more specifics about Photon itself.
{ >
{ > Thomas
{
{


Pat Ford email: pford@qnx.com
QNX Software Systems, Ltd. WWW: http://www.qnx.com
(613) 591-0931 (voice) mail: 175 Terence Matthews
(613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8