I’m creating a sort of rescue-disk for QNX v4.25G, where everything is unpacked into RAM-disk.
3.5" floppy can store just the very basic set of utilities, I need to put there /boot/sys too.
If I strip off the use- and debug- info - Proc32 becomes nearly twice as small. Is it usable for including in the .boot image when stripped?
Tony.
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsf92c8qao93ri4@mobile…
I’m creating a sort of rescue-disk for QNX v4.25G, where everything is
unpacked into RAM-disk.
3.5" floppy can store just the very basic set of utilities, I need to put
there /boot/sys too.If I strip off the use- and debug- info - Proc32 becomes nearly twice as
small. Is it usable for including in the .boot image when stripped?
How do you strip it? Funny cause I always though Proc32 was not a “normal”
application.
Tony.
On Fri, 22 Oct 2004 18:14:28 -0400, Mario Charest <nowheretobefound@8thdimension.com> wrote:
How do you strip it? Funny cause I always though Proc32 was not a “normal”
application.
The “usage” I strip out like this:
“usemsg Proc32 /dev/null”
The debug-info I strip as usual:
“wstrip Proc32”
I wonder why the debug-info is there, what in the production installation might depend on it?
Tony.
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsgbg4hf6o93ri4@mobile…
On Fri, 22 Oct 2004 18:14:28 -0400, Mario Charest
nowheretobefound@8thdimension.com> > wrote:How do you strip it? Funny cause I always though Proc32 was not a
“normal”
application.
The “usage” I strip out like this:
“usemsg Proc32 /dev/null”The debug-info I strip as usual:
“wstrip Proc32”I wonder why the debug-info is there, what in the production installation
might depend on it?
I’m guessing the info is stripped by the build process, which mean
stripping it won’t have any effect on the size of the image file.
Tony.
On Sat, 23 Oct 2004 17:23:04 -0400, Mario Charest <nowheretobefound@8thdimension.com> wrote:
I’m guessing the info is stripped by the build process, which mean stripping it won’t have any effect on the size of the image file.
Yes, the image seems to be of the same size.
But may be it is needed for /bin/buildqnx to work properly?
Or, for reporting the OS-level problems?
Tony.
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsgdb59joo93ri4@mobile…
On Sat, 23 Oct 2004 17:23:04 -0400, Mario Charest
nowheretobefound@8thdimension.com> > wrote:I’m guessing the info is stripped by the build process, which mean
stripping it won’t have any effect on the size of the image file.
Yes, the image seems to be of the same size.
If they are the same, then there is no point in stripping them and spent
brain power on this issue 
But may be it is needed for /bin/buildqnx to work properly?
Or, for reporting the OS-level problems?
Tony.
On Sun, 24 Oct 2004 15:07:05 -0400, Mario Charest <nowheretobefound@8thdimension.com> wrote:
If they are the same, then there is no point in stripping them and spent brain power on this issue >
Well…
I need to save some valuable storage space on my floppy. If the the boot-image will be some how defective because of those strippings - I need to know that in advance.
Tony.
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsgff70abo93ri4@mobile…
On Sun, 24 Oct 2004 15:07:05 -0400, Mario Charest
nowheretobefound@8thdimension.com> > wrote:If they are the same, then there is no point in stripping them and spent
brain power on this issue >
Well…I need to save some valuable storage space on my floppy. If the the
boot-image will be some how defective because of those strippings - I need
to know that in advance.
You said the boot-image is of the same size whether you strip or not, so
what’s the point in stripping in the first place, just don’t strip forget
about it. Unless I misunderstood and you want to store Proc32 on the floppy
along with the boot image for some reason.
Tony.
On Mon, 25 Oct 2004 12:09:13 -0400, Mario Charest <nowheretobefound@8thdimension.com> wrote:
Unless I misunderstood and you want to store Proc32 on the floppy along with the boot image for some reason.
I do store /boot/sys/Proc32, /boot/sys/Slib32, /boot/sys/boot and /bin/buildqnx on the floppy to be able to re-build the image on the HDD being repaired.
Tony.
“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsgfqvaf6o93ri4@mobile.wst.quantum.ru…
On Mon, 25 Oct 2004 12:09:13 -0400, Mario Charest
nowheretobefound@8thdimension.com> > wrote:Unless I misunderstood and you want to store Proc32 on the floppy along
with the boot image for some reason.
I do store /boot/sys/Proc32, /boot/sys/Slib32, /boot/sys/boot and
/bin/buildqnx on the floppy to be able to re-build the image on the HDD
being repaired.
I’m not 100% familiar with your process nor is it clear to mean what you
want to acheive, but to build an image you would also need mount, Fsys,
Fsys.eide and sinit
Tony.
Tony wrote:
On Mon, 25 Oct 2004 12:09:13 -0400, Mario Charest
nowheretobefound@8thdimension.com> > wrote:Unless I misunderstood and you want to store Proc32 on the floppy
along with the boot image for some reason.I do store /boot/sys/Proc32, /boot/sys/Slib32, /boot/sys/boot and
/bin/buildqnx on the floppy to be able to re-build the image on the HDD
being repaired.Tony.
Wouldn’t it be easier to just build an hd os image, and gzip it rather
than include all the components, and tools to rebuild the image onto a
floppy?
–
Cheers,
Adam
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>
On Mon, 25 Oct 2004 15:57:42 -0400, Adam Mallory <amallory@qnx.com> wrote:
Wouldn’t it be easier to just build an hd os image, and gzip it rather than include all the components, and tools to rebuild the image onto a floppy?
And what should I do if I need to change the node number?!
Well, seems, since you did not warn me about any harm of stripping the Proc32 - I’m safe.
Tony.
On Mon, 25 Oct 2004 14:37:59 -0400, Mario Charest <nowheretobefound@8thdimension.com> wrote:
I’m not 100% familiar with your process nor is it clear to mean what you want to acheive, but to build an image you would also need mount, Fsys, Fsys.eide and sinit
Yes, all those are stored as well.
The rescue disk is based on the description of the bootdisk from the QNX v4.23A documentation. I just push the idea forward - include mqc and other handy tools there too.
Tony.
Tony wrote:
And what should I do if I need to change the node number?!
Well, this is an emergency disk - not a full featured install. What if
you plugged in a SCSI disk or needed Network access, but changed your
NIC card?
I understood the purpose is to get your HD bootable with an OS image
again and to that, a single OS image should probably cover you mostly.
Well, seems, since you did not warn me about any harm of stripping the
Proc32 - I’m safe.
buildqnx doesn’t require the debug info, but I’m not going to suggest
that using wstrip against the Proc32 binary is a good idea. If it works
fine for you, fill y’er boots.
–
Cheers,
Adam
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>
On Tue, 26 Oct 2004 00:42:41 -0400, Adam Mallory <amallory@qnx.com> wrote:
Well, this is an emergency disk - not a full featured install. What if you plugged in a SCSI disk or needed Network access, but changed your NIC card?
All the Net.* and network-related utils are packed onto the second floppy and are unpacked into RAM-disk if needed.
buildqnx doesn’t require the debug info, but I’m not going to suggest that using wstrip against the Proc32 binary is a good idea.
This is the answer I wanted to hear!
I need these two floppyes just to resurrect a faulty box, so after this, as FLEET or TCP/IP starts - it will be easier to put there the remaning software.
Tony.
Tony wrote:
I need these two floppyes just to resurrect a faulty box, so after this, as FLEET or TCP/IP starts - it will be easier to put there the remaning software.
In that case, it might be much easier to boot the box over the network
(see http://etherboot.sourceforge.net/).
You’d only need to create a bootable Etherboot floppy for your network
card (pre-built images can be downloaded from http://www.rom-o-matic.net/)
and set up a QNX4 boot server (with bootp/tftp) - complete instructions
are in the Etherboot tarball below contrib/mkQNXnbi/).
Cheers
Anders
On Tue, 26 Oct 2004 21:29:16 +0200, Anders Larsen <al@alarsen.net> wrote:
…and set up a QNX4 boot server (with bootp/tftp)…
Wow!
This is an overkill for me.
With the two floppyes I create I’m able to do practically everything with the faulty box. I’ll post their contents and the instructions here.
Tony.