im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…
vince
As far as I know, mkifs is only for making bootable images. Are you
trying to compress the files that are on the QNX4 filesystem on the
floppy?
Couldn’t you put them in a compressed tar, and uncompress them at install
time?
vince <vgeisler@engineer.com> wrote:
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file[+compress]
[data=copy]/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <> vgeisler@engineer.com
wrote:im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file
[+compress]
[data=copy]
/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…
also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <vgeisler@engineer.com>
wrote:
im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
according to the manual you can use mkifs to create bootable and non
bootable images.
what i have is a minimal neutrino and minimal photon setup on my CF
what i want to do is put all the files that aren’t used for booting
and put them on a compressed image that is mounted after boot. then
the files can be decompressed to ram before they are used thus saving
some space… essencally im trying to perform the same function as the
qncbase.ifs and qnxbase.qfs files just on a minimal scale…
vince
On 7 Dec 2000 22:23:24 GMT, cburgess@qnx.com wrote:
As far as I know, mkifs is only for making bootable images. Are you
trying to compress the files that are on the QNX4 filesystem on the
floppy?Couldn’t you put them in a compressed tar, and uncompress them at install
time?vince <> vgeisler@engineer.com> > wrote:
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file[+compress]
[data=copy]/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <> vgeisler@engineer.com
wrote:im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
mkifs means “Make Image File System”. The image file system is the one that’s
mounted as /proc/boot and is tightly integrated with the whole kernel startup
thing. You cannot use mkifs to make any other sort of filesystem, therefor
it’s not applicable for what you’re trying to do. It only builds boot images,
to be copied to /.boot and/or /.altboot.
mkefs makes an embedded filesystem to be used with the devf-* family of
drivers. I don’t know of any way to mount an efs image without them, but
perhaps one of the filesystem gurus will know of one.
-Warren
“vince” <vgeisler@engineer.com> wrote in message
news:qh703t8t1hm9d3gpn8gkkmikbf4qkr94in@4ax.com…
| according to the manual you can use mkifs to create bootable and non
| bootable images.
|
| what i have is a minimal neutrino and minimal photon setup on my CF
| what i want to do is put all the files that aren’t used for booting
| and put them on a compressed image that is mounted after boot. then
| the files can be decompressed to ram before they are used thus saving
| some space… essencally im trying to perform the same function as the
| qncbase.ifs and qnxbase.qfs files just on a minimal scale…
|
|
| vince
|
|
| On 7 Dec 2000 22:23:24 GMT, cburgess@qnx.com wrote:
|
| >As far as I know, mkifs is only for making bootable images. Are you
| >trying to compress the files that are on the QNX4 filesystem on the
| >floppy?
| >
| >Couldn’t you put them in a compressed tar, and uncompress them at install
| >time?
| >
| >vince <vgeisler@engineer.com> wrote:
| >> ok im think im figuring out how to do this… rather than using efs
| >> (which i now understand to be for flash only) im using ifs… here’s
| >> the build file im using
| >> #ifs file test file
| >
| >> [+compress]
| >> [data=copy]
| >
| >> /root/test
| >
| >> #eof
| >
| >> all work ok untill i add the +compress and then wen i try to mkifs it
| >> core dumps… so what am i doing wrong here…
| >
| >> also how do you mount this thing once i do have a good ifs?
| >
| >> vince
| >
| >
| >
| >> On Thu, 07 Dec 2000 12:27:04 -0800, vince <vgeisler@engineer.com>
| >> wrote:
| >
| >>>im wondering if i could make my install even smaller by building all
| >>>my executables/config files into a compressed efs. is this possable? i
| >>>tried the +compress flag but it didn’t seem to like it.
| >>>my other question is after you have your nifty fileysstem image how do
| >>>you mount the thing? i know that rtos does something like this with
| >>>its qnxbase.qfs file but i dont quite grock how this works…
| >>>
| >>>vince
|
I’m going to defer to the image filesystem gurus here, but I don’t think
this was the intention of this ability.
What you might do instead is to use devf-ram to build a compressed
image which you can then restore at runtime.
vince <vgeisler@engineer.com> wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.what i have is a minimal neutrino and minimal photon setup on my CF
what i want to do is put all the files that aren’t used for booting
and put them on a compressed image that is mounted after boot. then
the files can be decompressed to ram before they are used thus saving
some space… essencally im trying to perform the same function as the
qncbase.ifs and qnxbase.qfs files just on a minimal scale…
vince
On 7 Dec 2000 22:23:24 GMT, > cburgess@qnx.com > wrote:As far as I know, mkifs is only for making bootable images. Are you
trying to compress the files that are on the QNX4 filesystem on the
floppy?Couldn’t you put them in a compressed tar, and uncompress them at install
time?vince <> vgeisler@engineer.com> > wrote:
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file[+compress]
[data=copy]/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <> vgeisler@engineer.com
wrote:im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
thanks for pointing me in the right direction. i think that that is
exactly what i want. now i just have to figure out how it works… im
still reading up on mkefs,flashctrl and flashzip but hopefully i can
figure out how it all works…
vince…
On 8 Dec 2000 04:54:51 GMT, cburgess@qnx.com wrote:
I’m going to defer to the image filesystem gurus here, but I don’t think
this was the intention of this ability.What you might do instead is to use devf-ram to build a compressed
image which you can then restore at runtime.vince <> vgeisler@engineer.com> > wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.what i have is a minimal neutrino and minimal photon setup on my CF
what i want to do is put all the files that aren’t used for booting
and put them on a compressed image that is mounted after boot. then
the files can be decompressed to ram before they are used thus saving
some space… essencally im trying to perform the same function as the
qncbase.ifs and qnxbase.qfs files just on a minimal scale…
vince
On 7 Dec 2000 22:23:24 GMT, > cburgess@qnx.com > wrote:As far as I know, mkifs is only for making bootable images. Are you
trying to compress the files that are on the QNX4 filesystem on the
floppy?Couldn’t you put them in a compressed tar, and uncompress them at install
time?vince <> vgeisler@engineer.com> > wrote:
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file[+compress]
[data=copy]/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <> vgeisler@engineer.com
wrote:im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
vince <vgeisler@engineer.com> wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.
The non-bootable comment is for that future day when you can
say:
mount -tifs /foo /home/bstecher/ifs-created-by-mkifs
or even:
mount -Tifs /foo 0x
Brian Stecher (bstecher@qnx.com) QNX Software Systems, Ltd.
phone: +1 (613) 591-0931 (voice) 175 Terence Matthews Cr.
+1 (613) 591-3579 (fax) Kanata, Ontario, Canada K2M 1W8
any idea when that happy day may come??
i wish they would mark things like this as “Future features” im
manuals. it makes it really difficult for a newby to figure out the
proper way of going about things…
vince
On 8 Dec 2000 14:51:24 GMT, Brian Stecher <bstecher@qnx.com> wrote:
vince <> vgeisler@engineer.com> > wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.The non-bootable comment is for that future day when you can
say:mount -tifs /foo /home/bstecher/ifs-created-by-mkifs
or even:
mount -Tifs /foo 0x<physical-address-where-a-ROM-with-an-ifs-is
and have the files appear under “/foo”.
im playing around with devf-ram . but im not having any success at it.
i suspect i’m probably going about it the wrong way. i did read the
documentation but didn’t find anything specifically about what i’m
trying to do.
i tried devf-ram my-efs-image.efs and all that happened was i got
one raw and one partition device in my /dev
i could not mount them or do anything useful with them… i’m beginning
to think i’m going about this wrong… Unfortunately i can’t find many
examples of how to correctly use devf-ram so i’m kinda hacking at it
hoping i get lucky… can anyone clear up the mystery of how to
correctly use devf-ram
vince
On 8 Dec 2000 04:54:51 GMT, cburgess@qnx.com wrote:
I’m going to defer to the image filesystem gurus here, but I don’t think
this was the intention of this ability.What you might do instead is to use devf-ram to build a compressed
image which you can then restore at runtime.vince <> vgeisler@engineer.com> > wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.what i have is a minimal neutrino and minimal photon setup on my CF
what i want to do is put all the files that aren’t used for booting
and put them on a compressed image that is mounted after boot. then
the files can be decompressed to ram before they are used thus saving
some space… essencally im trying to perform the same function as the
qncbase.ifs and qnxbase.qfs files just on a minimal scale…
vince
On 7 Dec 2000 22:23:24 GMT, > cburgess@qnx.com > wrote:As far as I know, mkifs is only for making bootable images. Are you
trying to compress the files that are on the QNX4 filesystem on the
floppy?Couldn’t you put them in a compressed tar, and uncompress them at install
time?vince <> vgeisler@engineer.com> > wrote:
ok im think im figuring out how to do this… rather than using efs
(which i now understand to be for flash only) im using ifs… here’s
the build file im using
#ifs file test file[+compress]
[data=copy]/root/test
#eof
all work ok untill i add the +compress and then wen i try to mkifs it
core dumps… so what am i doing wrong here…also how do you mount this thing once i do have a good ifs?
vince
On Thu, 07 Dec 2000 12:27:04 -0800, vince <> vgeisler@engineer.com
wrote:im wondering if i could make my install even smaller by building all
my executables/config files into a compressed efs. is this possable? i
tried the +compress flag but it didn’t seem to like it.
my other question is after you have your nifty fileysstem image how do
you mount the thing? i know that rtos does something like this with
its qnxbase.qfs file but i dont quite grock how this works…vince
vince <vgeisler@engineer.com> wrote:
: im playing around with devf-ram . but im not having any success at it.
: i suspect i’m probably going about it the wrong way. i did read the
: documentation but didn’t find anything specifically about what i’m
: trying to do.
: i tried devf-ram my-efs-image.efs and all that happened was i got
: one raw and one partition device in my /dev
: i could not mount them or do anything useful with them… i’m beginning
: to think i’m going about this wrong… Unfortunately i can’t find many
: examples of how to correctly use devf-ram so i’m kinda hacking at it
: hoping i get lucky… can anyone clear up the mystery of how to
: correctly use devf-ram
Disclaimer: I’m not a filesystem guru but I have used flash drivers.
To start it, I use:
devf-ram -u2 -t1 -r -s0,8M&
(the u option is for update level, t sets the number of threads and r
enables fault recovery, the s sets a size)
that creates a flash device
then you have to
flashctl -p/dev/fs0p0 -v -e -f
(format it with a useable filesystem, the fs0p0 is the default flash
device created, so if you’ve passed a -i option to devf-ram.)c
options v is verbose, should see some '.'s, -e erases it and -f
will format it with a valid filesystem.
In your root partition you should now have a /fs0p0 which is accessable.
You should be able to get all of this information out of the docs on
devf-ram and flashctl.
Peter
: vince
: On 8 Dec 2000 04:54:51 GMT, cburgess@qnx.com wrote:
:>I’m going to defer to the image filesystem gurus here, but I don’t think
:>this was the intention of this ability.
:>
:>What you might do instead is to use devf-ram to build a compressed
:>image which you can then restore at runtime.
:>
:>vince <vgeisler@engineer.com> wrote:
:>> according to the manual you can use mkifs to create bootable and non
:>> bootable images.
:>
:>> what i have is a minimal neutrino and minimal photon setup on my CF
:>> what i want to do is put all the files that aren’t used for booting
:>> and put them on a compressed image that is mounted after boot. then
:>> the files can be decompressed to ram before they are used thus saving
:>> some space… essencally im trying to perform the same function as the
:>> qncbase.ifs and qnxbase.qfs files just on a minimal scale…
:>
:>
:>> vince
:>
:>
:>> On 7 Dec 2000 22:23:24 GMT, cburgess@qnx.com wrote:
:>
:>>>As far as I know, mkifs is only for making bootable images. Are you
:>>>trying to compress the files that are on the QNX4 filesystem on the
:>>>floppy?
:>>>
:>>>Couldn’t you put them in a compressed tar, and uncompress them at install
:>>>time?
:>>>
:>>>vince <vgeisler@engineer.com> wrote:
:>>>> ok im think im figuring out how to do this… rather than using efs
:>>>> (which i now understand to be for flash only) im using ifs… here’s
:>>>> the build file im using
:>>>> #ifs file test file
:>>>
:>>>> [+compress]
:>>>> [data=copy]
:>>>
:>>>> /root/test
:>>>
:>>>> #eof
:>>>
:>>>> all work ok untill i add the +compress and then wen i try to mkifs it
:>>>> core dumps… so what am i doing wrong here…
:>>>
:>>>> also how do you mount this thing once i do have a good ifs?
:>>>
:>>>> vince
:>>>
:>>>
:>>>
:>>>> On Thu, 07 Dec 2000 12:27:04 -0800, vince <vgeisler@engineer.com>
:>>>> wrote:
:>>>
:>>>>>im wondering if i could make my install even smaller by building all
:>>>>>my executables/config files into a compressed efs. is this possable? i
:>>>>>tried the +compress flag but it didn’t seem to like it.
:>>>>>my other question is after you have your nifty fileysstem image how do
:>>>>>you mount the thing? i know that rtos does something like this with
:>>>>>its qnxbase.qfs file but i dont quite grock how this works…
:>>>>>
:>>>>>vince
vince <vgeisler@engineer.com> wrote:
any idea when that happy day may come??
i wish they would mark things like this as “Future features” im
manuals. it makes it really difficult for a newby to figure out the
proper way of going about things…
Sooner than you may think =;-)
Thomas
On 8 Dec 2000 14:51:24 GMT, Brian Stecher <> bstecher@qnx.com> > wrote:
vince <> vgeisler@engineer.com> > wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.The non-bootable comment is for that future day when you can
say:mount -tifs /foo /home/bstecher/ifs-created-by-mkifs
or even:
mount -Tifs /foo 0x<physical-address-where-a-ROM-with-an-ifs-is
and have the files appear under “/foo”.
On 8 Dec 2000 22:09:06 GMT, Thomas Fletcher <thomasf@qnx.com> wrote:
vince <> vgeisler@engineer.com> > wrote:
any idea when that happy day may come??
i wish they would mark things like this as “Future features” im
manuals. it makes it really difficult for a newby to figure out the
proper way of going about things…Sooner than you may think =;-)
Thomas
i await salivating with anticipation. >
On 8 Dec 2000 14:51:24 GMT, Brian Stecher <> bstecher@qnx.com> > wrote:vince <> vgeisler@engineer.com> > wrote:
according to the manual you can use mkifs to create bootable and non
bootable images.The non-bootable comment is for that future day when you can
say:mount -tifs /foo /home/bstecher/ifs-created-by-mkifs
or even:
mount -Tifs /foo 0x<physical-address-where-a-ROM-with-an-ifs-is
and have the files appear under “/foo”.
