hello,
I use mkifs to create a qnx image. I put the image on a disk with dinit.
But whe
n the image is larger than +/- 600ko, the loader freeze on boot. Why ?
What’s the size limit ? How can I put many apps (such as ping, telnet,
ifconfig…) on my disk ?
Regards,
b
Jean-Yves Moulin <jym@waycom.net> wrote:
hello,
I use mkifs to create a qnx image. I put the image on a disk with dinit.
But whe
n the image is larger than +/- 600ko, the loader freeze on boot. Why ?
You are at the limit, I think it is about 600K.
What’s the size limit ? How can I put many apps (such as ping, telnet,
ifconfig…) on my disk ?
You will have to have access to a hard-drive or a network card(which has
access to a filesystem), run the appropriate drivers and then run the command
waitfor /path_to_more_commands in your build file.
You may also use the +compress attribute in the bootstrap file to compress
your image.
For more details check out the QNX Neutrino Building Embedded Systems,
chapter 3 Making a Neutrino Image.
Chris
Regards,
b
Bios limitation. Sounds like the 640Kb limit in dos land? ( I’m assuming X86
here, as I have much larger images for other machines
Previously, Jean-Yves Moulin wrote in qdn.public.qnxrtp.os:
{ hello,
{
{ I use mkifs to create a qnx image. I put the image on a disk with dinit.
{ But whe
{ n the image is larger than +/- 600ko, the loader freeze on boot. Why ?
you are in real mode, until the image starts
{
{ What’s the size limit ? How can I put many apps (such as ping, telnet,
{ ifconfig…) on my disk ?
make a file system that gets loaded after proc has run
{
{ Regards,
{
{ b
{
–
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
Hi
Basically as you guessed you’ve hit the upper limit of the image but
unfortunately there is no meaningful message to inform you of the fact
I can’t remember exactly the size but they are documented somewhere in the
documentation. It also varies on your setup.
What you need to do is trim the image down as small as you can get and load
any apps you require onto your target filesystem for instance I have a
PC/104 card which has an 8Meg DiskOnChip (solid state device) - I mount that
on startup and access all my apps from there. Basically once you have got
the apps onto your target filesystem you can reduce your build image to do
little more than mounting your target filesystem and then you can access
your apps from there. It can be a bit tedious getting the apps on the target
initially though although if your target has a network connection you can
use CIFS/FTP or something similar to get the apps over.
I can’t really comment much as I don’t know the ins and outs of your target
platform.
I can symathise with you if you’re booting from floppy though 8-P
Oh the joys of making trial and error image files…
Jean-Yves Moulin wrote in message <39F433F4.71052588@waycom.net>…
hello,
I use mkifs to create a qnx image. I put the image on a disk with dinit.
But whe
n the image is larger than +/- 600ko, the loader freeze on boot. Why ?What’s the size limit ? How can I put many apps (such as ping, telnet,
ifconfig…) on my disk ?Regards,
b
Jim Atkins wrote:
Hi
Basically as you guessed you’ve hit the upper limit of the image but
unfortunately there is no meaningful message to inform you of the fact
[cut]
I can’t really comment much as I don’t know the ins and outs of your target
platform.I can symathise with you if you’re booting from floppy though 8-P
ok, I want to make a floppy with all what I need for access the network.
In doc, there are example to create a ramdisk, there are example to
create an image for a flash filesystem (mkefs) but how can I load this
image build with mkefs in a ramdisk on boot ? It’s possible ? (It’s the
only way that I found).
Thanks
jym
Any files which are in your boot image will be accessible/runable from
/proc/boot once the system is up. The proc filesystem exists only in ram, not
on hard disk. This is pretty much the same thing as a ram disk.
Previously, Jean-Yves Moulin wrote in qdn.public.qnxrtp.os:
Jim Atkins wrote:
Hi
Basically as you guessed you’ve hit the upper limit of the image but
unfortunately there is no meaningful message to inform you of the fact[cut]
I can’t really comment much as I don’t know the ins and outs of your target
platform.I can symathise with you if you’re booting from floppy though 8-P
ok, I want to make a floppy with all what I need for access the network.
In doc, there are example to create a ramdisk, there are example to
create an image for a flash filesystem (mkefs) but how can I load this
image build with mkefs in a ramdisk on boot ? It’s possible ? (It’s the
only way that I found).Thanks
jym
Chris Foran <cforan@qnx.com> wrote:
: Any files which are in your boot image will be accessible/runable from
: /proc/boot once the system is up. The proc filesystem exists only in ram, not
: on hard disk. This is pretty much the same thing as a ram disk.
A read only ram filesystem mind you =;-)
Thomas
Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf
“Jean-Yves Moulin” <jym@ldh.org> wrote in message
news:39F4454C.792B5F9C@ldh.org…
|
| ok, I want to make a floppy with all what I need for access the network.
| In doc, there are example to create a ramdisk, there are example to
| create an image for a flash filesystem (mkefs) but how can I load this
| image build with mkefs in a ramdisk on boot ? It’s possible ? (It’s the
| only way that I found).
|
| Thanks
|
|
|
| jym
In your boot image you’re going to need certain things (libc.so, console
driver, and so on) and not need certain things (serial port drivers, anything
else that can be started “later”). So if you built a boot image with your
basic floppy driver on it, then mounted the filesystem that was on the floppy,
you could have access to more than 640k of stuff. If you used a compressed tar
archive for example, that you expanded to RAM disk once you had a minimal
system running, you could then run your network driver which would presumable
give you access to any other processes which you were intending to run. If you
could squeeze everything in to the compressed archive, then you wouldn’t need
to go across the network to load 'em even.
I hope that gives you some ideas.
-Warren
Jim,
Are you running RTP on this card. Is the DOC driver for RTP avialable?
Dave
Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
Hi
Basically as you guessed you’ve hit the upper limit of the image but
unfortunately there is no meaningful message to inform you of the fact
I can’t remember exactly the size but they are documented somewhere in the
documentation. It also varies on your setup.What you need to do is trim the image down as small as you can get and load
any apps you require onto your target filesystem for instance I have a
PC/104 card which has an 8Meg DiskOnChip (solid state device) - I mount that
on startup and access all my apps from there. Basically once you have got
the apps onto your target filesystem you can reduce your build image to do
little more than mounting your target filesystem and then you can access
your apps from there. It can be a bit tedious getting the apps on the target
initially though although if your target has a network connection you can
use CIFS/FTP or something similar to get the apps over.I can’t really comment much as I don’t know the ins and outs of your target
platform.I can symathise with you if you’re booting from floppy though 8-P
Oh the joys of making trial and error image files…
Jean-Yves Moulin wrote in message <> 39F433F4.71052588@waycom.net> >…
hello,I use mkifs to create a qnx image. I put the image on a disk with dinit.
But whe
n the image is larger than +/- 600ko, the loader freeze on boot. Why ?What’s the size limit ? How can I put many apps (such as ping, telnet,
ifconfig…) on my disk ?Regards,
b
\
–
David L. Hawley D.L. Hawley and Associates
“David Hawley” <David.L.Hawley@computer.org> wrote in message
news:Voyager.001113103014.19715A@dave…
Jim,
Are you running RTP on this card. Is the DOC driver for RTP avialable?
The DOC driver is in beta, it’s from M-System. You gotta get in touch
with them to obtain it.
Dave
Previously, Jim Atkins wrote in qdn.public.qnxrtp.os:
HiBasically as you guessed you’ve hit the upper limit of the image but
unfortunately there is no meaningful message to inform you of the fact
I can’t remember exactly the size but they are documented somewhere in
the
documentation. It also varies on your setup.What you need to do is trim the image down as small as you can get and
load
any apps you require onto your target filesystem for instance I have a
PC/104 card which has an 8Meg DiskOnChip (solid state device) - I mount
that
on startup and access all my apps from there. Basically once you have
got
the apps onto your target filesystem you can reduce your build image to
do
little more than mounting your target filesystem and then you can access
your apps from there. It can be a bit tedious getting the apps on the
target
initially though although if your target has a network connection you
can
use CIFS/FTP or something similar to get the apps over.I can’t really comment much as I don’t know the ins and outs of your
target
platform.I can symathise with you if you’re booting from floppy though 8-P
Oh the joys of making trial and error image files…
Jean-Yves Moulin wrote in message <> 39F433F4.71052588@waycom.net> >…
hello,I use mkifs to create a qnx image. I put the image on a disk with
dinit.
But whe
n the image is larger than +/- 600ko, the loader freeze on boot. Why ?What’s the size limit ? How can I put many apps (such as ping, telnet,
ifconfig…) on my disk ?Regards,
b
\David L. Hawley D.L. Hawley and Associates