What controls the order at which files are stored the the image.
I’d like to have control over the order?
- Mario
Mario Charest <goto@nothingness.com> wrote:
What controls the order at which files are stored the the image.
I’d like to have control over the order?
I am not sure that you can. However, I would be VERY interested to know why
you want to be able to control this in case you are unable to with
the current version of mkifs. Is there a performance gain you can get
by placing something at a specific place in the image on your board?
Good to know what limits people are hitting.
chris
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
“Chris McKillop” <cdm@qnx.com> wrote in message
news:a7u98b$4dn$1@nntp.qnx.com…
Mario Charest <> goto@nothingness.com> > wrote:
What controls the order at which files are stored the the image.
I’d like to have control over the order?
I am not sure that you can. However, I would be VERY interested to know
why
you want to be able to control this in case you are unable to with
the current version of mkifs. Is there a performance gain you can get
by placing something at a specific place in the image on your board?
I’m createing a 2Meg image to go in FLASH. The image has a good number
of file in it. I’m doing lots of test and programming 2M of flash
takes a while (the FLASH is accessed via IO).
I optimized the utility that I use to write the flash image
to be as efficient as possible (it doesn’t erase sectors that
are identical). Since I’m often changing only a few
files, I would like to store theses files at the end of the image to reduce
the time it takes to program the flash.
Currently the file I’m working on (’/etc/sysinit") is being place at the
begining
of the image. Hence if I add one byte to it, the whole flash has to be
reprogram.
Good to know what limits people are hitting.
Well I couldn’t qualify it has a limit but it would definitily
make me more efficient in my work 
chris
–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
In this case I belive you could use the “chain” option in your buildfile
to setup a secondary image filesystem at a known location.
chris
Mario Charest <goto@nothingness.com> wrote:
“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:a7u98b$4dn$> 1@nntp.qnx.com> …
Mario Charest <> goto@nothingness.com> > wrote:
What controls the order at which files are stored the the image.
I’d like to have control over the order?
I am not sure that you can. However, I would be VERY interested to know
why
you want to be able to control this in case you are unable to with
the current version of mkifs. Is there a performance gain you can get
by placing something at a specific place in the image on your board?I’m createing a 2Meg image to go in FLASH. The image has a good number
of file in it. I’m doing lots of test and programming 2M of flash
takes a while (the FLASH is accessed via IO).
I optimized the utility that I use to write the flash image
to be as efficient as possible (it doesn’t erase sectors that
are identical). Since I’m often changing only a few
files, I would like to store theses files at the end of the image to reduce
the time it takes to program the flash.Currently the file I’m working on (’/etc/sysinit") is being place at the
begining
of the image. Hence if I add one byte to it, the whole flash has to be
reprogram.Good to know what limits people are hitting.
Well I couldn’t qualify it has a limit but it would definitily
make me more efficient in my work >
chris–
Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/
Chris McKillop <cdm@qnx.com> wrote in news:a7vuec$c8k$2@nntp.qnx.com:
In this case I belive you could use the “chain” option in your
buildfile to setup a secondary image filesystem at a known location.
I believe you must make the secondary image bootable as well for it to
chain (I don’t know why, it’s an issue that being looked at).
Why not just put the files in a flash partition, and everytime you want to
update a specific file, you can just stick the new version in the image,
and once booted, you mount the flash, and copy the binary over. That way
the image only has the binaries you want to update.
I’m assuming the board has no means of communication, like networking etc.
otherwise you could just put the binaries in flash. Updates could be done
using nfs (which the boot image would support).
\
Cheers,
Adam
QNX Software Systems Ltd.
[ amallory@qnx.com ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Adam Mallory” <amallory@qnx.com> wrote in message
news:Xns91DFA79433320amalloryqnxcom@209.226.137.4…
Chris McKillop <> cdm@qnx.com> > wrote in news:a7vuec$c8k$> 2@nntp.qnx.com> :
In this case I belive you could use the “chain” option in your
buildfile to setup a secondary image filesystem at a known location.I believe you must make the secondary image bootable as well for it to
chain (I don’t know why, it’s an issue that being looked at).Why not just put the files in a flash partition, and everytime you want to
update a specific file, you can just stick the new version in the image,
and once booted, you mount the flash, and copy the binary over. That way
the image only has the binaries you want to update.
Since the beginning I wanted to avoid to write to a flash driver for
simplicity.
A single 2M image is clean an efficient
I’m assuming the board has no means of communication, like networking etc.
otherwise you could just put the binaries in flash. Updates could be done
using nfs (which the boot image would support).
\Cheers,
AdamQNX Software Systems Ltd.
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net