[Q] Bootimage for CD

QNX Newsgroups (Archives) qdn.public.qnx4
1

Is there any chance to create a boot image, that I can use on
bootable CDs? I tried something like this, but it never continues after
showing the standard outputs of Fsys.eide.

Are there any secret options that I’m not aware of?


TIA,

Karsten.


And here’s my build file:

sys/boot
$ boot -v

sys/Proc32
$ Proc32 -l 1

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys -d1

/bin/Fsys.eide
$ Fsys.eide

/bin/Iso9660fsys
$ Iso9660fsys /dev/cd0=/

/bin/sinit
$ sinit TZ=cet-01cedt-02,M3.5.0/2,M10.5.0/3 TERM=qnx


\

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

2

Make a boot floppy that does what you want and copy the floppies image (/dev/fdX). That image file becomes the boot image

see here for more general info
http://www.nu2.nu/bootcd/

Previously, Karsten P. Hoffmann wrote in qdn.public.qnx4:
{ Is there any chance to create a boot image, that I can use on
{ bootable CDs? I tried something like this, but it never continues after
{ showing the standard outputs of Fsys.eide.
{
{ Are there any secret options that I’m not aware of?
{
{
{ TIA,
{
{ Karsten.
{
{
{ And here’s my build file:
{
{ sys/boot
{ $ boot -v
{
{ sys/Proc32
{ $ Proc32 -l 1
{
{ sys/Slib32
{ $ Slib32
{
{ sys/Slib16
{ $ Slib16
{
{ /bin/Fsys
{ $ Fsys -d1
{
{ /bin/Fsys.eide
{ $ Fsys.eide
{
{ /bin/Iso9660fsys
{ $ Iso9660fsys /dev/cd0=/
{
{ /bin/sinit
{ $ sinit TZ=cet-01cedt-02,M3.5.0/2,M10.5.0/3 TERM=qnx
{
{
{
{ –
{ __ __ ____ ____
{ | / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
{ | |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
{ | | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
{ || ||// Mobile: +49-172-3812373 D-47809 Krefeld
{
{
{
{

–
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

3

Pat Ford wrote:

Make a boot floppy that does what you want and copy the floppies image (/dev/fdX). That image file becomes the boot image

see here for more general info
http://www.nu2.nu/bootcd/

Well, perhaps my question was a little unclear:

My problem is not to create a bootable CD at all, but I assume some
timing problems when starting Fsys.eide, Iso9660fsys and sinit in the
boot image.

Fsys.eide is obviously starting, but Iso9660fsys does’nt issue any
information
that it has ‘adopted /dev/cd0 as /’ or so.

I also tried to use ‘mount_iso9660’, but this only produced error
messages
about a missing /dev/cd0 before Fsys.eide found it!

So I think, my problem is to synchonize Iso9660fsys, mount and sinit
with the delay of Fsys.eide.

Thanks for the good pointer, anyway!

Previously, Karsten P. Hoffmann wrote in qdn.public.qnx4:
{ Is there any chance to create a boot image, that I can use on
{ bootable CDs? I tried something like this, but it never continues after
{ showing the standard outputs of Fsys.eide.
{
{ Are there any secret options that I’m not aware of?
{
{
{ TIA,
{
{ Karsten.
{
{
{ And here’s my build file:
{
{ sys/boot
{ $ boot -v
{
{ sys/Proc32
{ $ Proc32 -l 1
{
{ sys/Slib32
{ $ Slib32
{
{ sys/Slib16
{ $ Slib16
{
{ /bin/Fsys
{ $ Fsys -d1
{
{ /bin/Fsys.eide
{ $ Fsys.eide
{
{ /bin/Iso9660fsys
{ $ Iso9660fsys /dev/cd0=/
{
{ /bin/sinit
{ $ sinit TZ=cet-01cedt-02,M3.5.0/2,M10.5.0/3 TERM=qnx
{

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

4

Previously, Karsten Hoffmann wrote in qdn.public.qnx4:

My problem is not to create a bootable CD at all, but I assume some
timing problems when starting Fsys.eide, Iso9660fsys and sinit in the
boot image.

Well your boot file look ok to me. To try to debug this, you might
write a program of your own that you can put in the image which
gives you post mortem information. May to start with a program that
every few seconds dumps the /dev directory.

Mitchell Schoenbrun --------- maschoen@pobox.com

5

Mitchell Schoenbrun wrote:

Well your boot file look ok to me. To try to debug this, you might
write a program of your own that you can put in the image which
gives you post mortem information. May to start with a program that
every few seconds dumps the /dev directory.

Thanks for the hint, I’ll try this tomorrow.

Actually the one and only error message is

“Unable to exec /bin/sh: No such file or directory.”

I assume this is issued by ‘sinit’ because it tries to access the
mounted filesystem ‘long time’ before it is settled up completely
by the Iso9660fsys.

I guess, what I need is a possibility to synchronize sinit with
Iso9660fsys
until mounting ist completed …

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

6

Karsten Hoffmann wrote:

Actually the one and only error message is

“Unable to exec /bin/sh: No such file or directory.”

I assume this is issued by ‘sinit’ because it tries to access the
mounted filesystem ‘long time’ before it is settled up completely
by the Iso9660fsys.

I guess, what I need is a possibility to synchronize sinit with
Iso9660fsys until mounting ist completed …

Confirmed!

The root directory is read to use aprox. 1 sec after sinit issued
it’s error message :frowning:(

From the large amount of replies to my question I assume that

I. nobody else was succesfull in this matter, yet

or

II. nobody tried.


Any comments?

P.S.: Any chance to use a QNX6/RTP boot file and start a QNX4 kernel
afterwards? Perhaps a stupid question …

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

7

“Karsten P. Hoffmann” wrote:

Is there any chance to create a boot image, that I can use on
bootable CDs? I tried something like this, but it never continues after
showing the standard outputs of Fsys.eide.

Are there any secret options that I’m not aware of?

TIA,

Karsten.

And here’s my build file:

sys/boot
$ boot -v

sys/Proc32
$ Proc32 -l 1

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys -d1

/bin/Fsys.eide
$ Fsys.eide

/bin/Iso9660fsys
$ Iso9660fsys /dev/cd0=/

Maybe ?
$Iso9660fsys /=/dev/cd0

/bin/sinit
$ sinit TZ=cet-01cedt-02,M3.5.0/2,M10.5.0/3 TERM=qnx

–

| / | __ ) | > Karsten.Hoffmann@mbs-software.de > MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

8

“Oleg A. Khamayko” wrote:

Maybe ?
$Iso9660fsys /=/dev/cd0

You’re right – I tried both ‘versions’ …

I never remember what is meant by

‘cdrom_drive_name’ and ‘qnx_drive_name’

in the usage of Iso9660fsys :slight_smile:)

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

9

Karsten Hoffmann wrote:

“Oleg A. Khamayko” wrote:

Maybe ?
$Iso9660fsys /=/dev/cd0


You’re right – I tried both ‘versions’ …

With no success? It boots here with “Iso9660fsys /=/dev/cd0”.
I’ve also made a special sysinit file for booting from CD and
passed the file name as a parameter to tinit.

Oleg

10

“Oleg A. Khamayko” wrote:

Karsten Hoffmann wrote:

“Oleg A. Khamayko” wrote:

Maybe ?
$Iso9660fsys /=/dev/cd0


You’re right – I tried both ‘versions’ …

With no success? It boots here with “Iso9660fsys /=/dev/cd0”.
I’ve also made a special sysinit file for booting from CD and
passed the file name as a parameter to tinit.
Sorry, sinit - not tinit -:slight_smile:

Oleg

11

“Oleg A. Khamayko” wrote:

With no success? It boots here with “Iso9660fsys /=/dev/cd0”.
I’ve also made a special sysinit file for booting from CD and
passed the file name as a parameter to tinit.

Oleg

Well, still the same: outputs of Fsys.eide as expected, no message of
any CD mounting, as Iso9660fsys normally does.

Have you been successfull?

Can I have some insights into your build file, if possible?

I’m really stuck …

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

12

Hi,

it was last summer I tried, so I’m not quite sure about the details.
I post what I found on the working cd.
Here comes the boot build file:

sys/boot
$ boot -v

sys/Proc32
$ Proc32 -l 1

sys/Slib32
$ Slib32

sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys -r 1024

/bin/Fsys.eide
$ Fsys.eide

/bin/Iso9660fsys
$ Iso9660fsys /=/dev/cd0

/bin/sinit
$ sinit TERM=qnx


And now the sysinit:

set -v
export TZ=utc00
rtc -l hw
Dev &
Dev.ansi -Q -n 6 &
reopen //0/dev/con1
kbd /etc/config/kbd/Germany
Dev.ser &
Dev.par &
Dev.pty &
#Iso9660fsys &
Fsys.floppy &
#Pipe &
dinit /dev/ram
mount /dev/ram /ram
prefix -A /pipe=/ram
emu87 &
nameloc &
freeze -cdz /etc/logo.F
Net -n10 &
Net.ether82557 -v &
netmap -f
license -R3
tinit -T /dev/con* -t /dev/con1 &

Hope it is a help.

Friedhelm Schuetz
H.Kleinknecht & Co. GmbH

13

Friedhelm Schuetz wrote:
[example, which looks pretty close to mine, snipped]

Well, since I couldn’t make out an significant differences
between all the helpful hints, I receveived, I conclude
that the problem must be in the way how I create the ISO
image of the CD.

Actually I use mkisofs v1.11.3, compiled as-it-is on a QNX4.25
machine with WATCOM 10.6.

My command line is:

mkisofs -o cd.iso -r -L -v -l -P"MBS GmbH" -p"My name" -b bootdisk

where bootdisk is a diskimage of a boot floppy.
The .boot file on this floppy is an image create from a build file,
that looks like Friedhelm’s example.

also contains all pathes (/etc, /bin, /usr/bin, ...) and files, drivers etc, which are required to boot-up. In fact: also the boot floppy file contains all that stuff, but it seems, that only the boot image is relevant ... just an assumption.

I wonder if I should use some other options to mkisofs, to get that
damned thing booting, but since there so many options (and therefore
there’s a high number of permutations as well :slight_smile:) ),
I would apprectiate any pointers into the right direction!

TIA,

Karsten.

P.S.: I recently had a look at mkisofs 1.12.? on a LINUX box, and
saw evenmore options regarding ISO levels and boot catalogues …

–

| / | __ ) | Karsten.Hoffmann@mbs-software.de MBS-GmbH
| |/| | _ _ \ Phone : +49-2151-7294-38 Karsten Hoffmann
| | | | |) |__) | Fax : +49-2151-7294-50 Roemerstrasse 15
|| ||// Mobile: +49-172-3812373 D-47809 Krefeld

14

Karsten Hoffmann wrote:

“Oleg A. Khamayko” wrote:
With no success? It boots here with “Iso9660fsys /=/dev/cd0”.
I’ve also made a special sysinit file for booting from CD and
passed the file name as a parameter to tinit.

Oleg

Well, still the same: outputs of Fsys.eide as expected, no message of
any CD mounting, as Iso9660fsys normally does.

Have you been successfull?

Can I have some insights into your build file, if possible?

I’m really stuck …

Sorry for delay, I’ve been out of the Net -:slight_smile:

=== Build Boot image to copy to the boot diskette and make later
1.44 floppy image “eide.cd” :

/boot/sys/boot
$ boot -v

/boot/sys/Proc32
$ Proc32 -l 1

/boot/sys/Slib32
$ Slib32

/boot/sys/Slib16
$ Slib16

/bin/Fsys
$ Fsys -r 4096

/bin/Fsys.eide
$ Fsys.eide

/bin/Iso9660fsys
$ Iso9660fsys /=/dev/cd0

/bin/sinit
$ sinit -i /etc/config/sysinit.cd -s /bin/esh TERM=qnxm



===The sysinit.cd file:

set -v

export NODE=1

export ABLANG=ru_RU
export HOME=///
export KBD=ru_RU_102.kbd
export TZ=mst-03mdt-04,M3.5.0/2,M10.5.0/2
export PATH=/ram:.:/bin:/usr/bin:/usr/ucb:/usr/local/bin
export SHELL=/bin/esh

/boot/sys/Slib16 &

/bin/rtc hw
/bin/Dev &
/bin/emu87 &
/bin/Dev.ser &
/bin/Dev.ansi -Q -n2 &

reopen /dev/con1
/bin/prefix -A /dev/console=/dev/con1
/bin/Dev.par &
/bin/Dev.pty -n16 &
/bin/Fsys.floppy &

/bin/umask 2

/bin/dinit /dev/ram
/bin/mount /dev/ram /ram
/bin/prefix -A /tmp=/ram

/bin/prefix -A /pipe=/ram
/bin/Pipe &

/bin/cp -v /bin/dinit /bin/mount /bin/pax /bin/prefix /ram
/bin/cp -v /bin/esh /ram/sh

echo Welcome to QNX 4.25B
ontty /dev/con1 /bin/sh

and shell script to make the cd

#!/bin/ksh

rm //3/boot/boot.eide.cd

../mkisofs -aflLRT -b eide.cd -c boot/boot.eide.cd -o Host-110e.iso
-x //3/dev
-x //3/.boot
-x //3/.bitmap
-x //3/.inodes
-x //3/.altboot
-x //3/.licenses
-x //3/pipe
-x //3/tmp
-x //3/etc/config/sysinit.3
//3/


And I use mkisofs ver 1.11.3

Maybe this helps. You may email me oleg@sovtigaz.msk.ru

Oleg