QNX4 sysinit followup processing

What is the simple path from /.boot, mount hard drive thru /etc/sysinit
which finished with a tinit a la the old QNX4 way?

I can build really neat QNX6 /.boot collections but I don’t understand what
diskboot really does and I have a QNX4 mentality where after I mount the
hard drive it continues thru /etc/sysinit which finished with tinit. What is
the process for making home groan simple booting processes where you keep
the /.boot small and do all the work later on the hard drive? I haven’t read
through all the previous postings and the answer is probably there somewhere
but maybe some kind person could save me the research time.


Thanks
GE Industrial Systems, Salem, Va
Dennis

Here’s one that I’m using. No diskboot in this image.

Dave

–Cut Here–
###########################################################################

Neutrino on an PC BIOS compatible system

This is for building a bootable neutrino image that will run from its

own filesystem partition.

To do this make a t79 partition for neutrino, then “mount /dev/hd0t79 /usr/nto”

This build file will also mount t77 partitions as “/usr/qnx4”

Note that the default image links at 4M. If you have 4M or less,

uncomment the line below

[image=1m]

###########################################################################

[search=/sbin:/usr/sbin:/bin:/usr/bin:/lib:/lib/dll:/boot/sys:/boot/build]

[virtual=x86,bios +compress] boot = {
startup-bios -s64K -N qnxsj03
PATH=/proc/boot:/bin:/usr/bin LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}

[+script] startup-script = {
PATH=/proc/boot:/bin:/usr/bin:/sbin:/usr/sbin

Start up some consoles

devc-con -n4 &
reopen /dev/con1

seedres

Start the pci server

pci-bios &
waitfor /dev/pci
display_msg “Waiting for disk drives now…”

devb-eide blk auto=partition,cache=4M eide dma,ioport=0x1f0,irq=14,geometry=255:789:63:0 eide dma,ioport=0x170,irq=15 &
waitfor /dev/hd0 60

sleep 2

waitfor /dev/hd0t79
mount -w -t qnx4 /dev/hd0t79 /
mount -w -t dos /dev/hd0t11 /fs/dos
waitfor /fs/dos

display_msg “Mounted dos as /fs/dos”

mount -wt qnx4 /fs/dos/“Program Files”/qnx/boot/fs/root.qfs /fs/nto

mount -wt qnx4 /fs/dos/“Program Files”/qnx/boot/fs/root.qfs /

waitfor /boot

display_msg “mounted root.qfs as /”

sleep 1

waitfor /boot/fs/qnxbase.qfs
mount -w -t qnx4 /boot/fs/qnxbase.qfs /pkgs/base

mount -w -t qnx4 /fs/dos/“Program Files”/qnx/boot/fs/qnxbase.qfs /pkgs/base

waitfor /pkgs/base
display_msg “Mounted /pkgs/base”

sleep 1

fs-pkg -a/pkgs/base/safe-config/etc/system/package/packages

waitfor /x86

sleep 7

waitfor /x86

BOOTSRC=disk
ROOTDEV=/dev/hd0t79
SAFEMODE=
VERBOSE=1

These env variables inherited by all the programs which follow

SYSNAME=nto
TERM=qansi-m

[pri=10o] /bin/ksh /etc/system/sysinit

[pri=10o] /bin/ksh /etc/system/dwdsysinit

}

\

Cheat and make the /temp point to the shared memory area…

[type=link] /tmp=/dev/shmem

Redirect console messages for syslog

[type=link] /dev/console=/dev/con1

Programs require the runtime linker (ldqnx.so) to be at a fixed location

[type=link] /usr/lib/ldqnx.so.1=/proc/boot/libc.so.1

We use the “c” shared lib (which also contains the runtime linker)

libc.so

Just incase someone needs floating point…

#fpemu.so

Include the hard disk files so we can access files on the disk

libcam.so
io-blk.so

filesystem required shared libs

cam-disk.so
fs-qnx4.so
fs-dos.so

cdrom required shared libs

cam-cdrom.so
fs-cd.so

The files above this line can be shared by mutiple processes

[data=c]

Executables must currently be below this line

Include a console driver

devc-con

Include the disk drivers.

devb-eide

Include pci server

pci-bios

seedres

mount
fs-pkg

sleep
ls

–Cut Here–

Previously, Dennis Morehart wrote in qdn.public.qnxrtp.os:

What is the simple path from /.boot, mount hard drive thru /etc/sysinit
which finished with a tinit a la the old QNX4 way?

I can build really neat QNX6 /.boot collections but I don’t understand what
diskboot really does and I have a QNX4 mentality where after I mount the
hard drive it continues thru /etc/sysinit which finished with tinit. What is
the process for making home groan simple booting processes where you keep
the /.boot small and do all the work later on the hard drive? I haven’t read
through all the previous postings and the answer is probably there somewhere
but maybe some kind person could save me the research time.


Thanks
GE Industrial Systems, Salem, Va
Dennis
\