I downloaded QNX RTP 6.1.0 a few days ago. I’m having difficulties
getting a second and third partition to mount to specific (standard) points.
I’ve dedicated my P233, with 4 (tiny) scsi drives, entirely to QNX (no
windows, linux, *bsd, etc). The first drive, hd0t79 is the boot drive,
and works as expected, although it’s 87% full. The other three drives,
after a sound fdisk’ing and dinit’ing automatically get mounted to
/fs/hd-qnx4 at boot (where is 1-3).
I would like to mount the remaining drives, hd1t79;hd2t79;hd3t79, to
/home, /var, and /tmp respectively.
Things I’ve tried to no sucess:
Creating rc.local (owned by root.sys, with 775 access) in /etc/rc.d
with the lines:
mount -t qnx4 /dev/hd1t79 /home
mount -t qnx4 /dev/hd2t79 /var
mount -t qnx4 /dev/hd3t79 /tmp
Adding the text
“automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to DEVB_OPTIONS in /etc/system/enum/include/block.
Bulding a custom image by appending “-odevb-aha4
automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to where diskboot gets called in my build script (which is just a copy
of /boot/build/qnxbasedma.build)
(I did run mkifs, I did copy the new image to /.boot, and I did reboot
the system, everything worked fine EXCEPT getting the drives to mount to
the points I want them).
creating another custom image where, after calling diskboot, I added
the lines:
mount -t qnx4 /dev/hd1t79 /home
mount -t qnx4 /dev/hd2t79 /var
mount -t qnx4 /dev/hd3t79 /tmp
(again, mkifs, cp /.boot, shutdown, reboot, no joy).
Cursing and gnashing my teeth
So, I’m at a loss. How do I get /dev/hd1t79 to mount to /home,
/dev/hd2t79 to mount to /var, and /dev/hd3t79 to mount to /tmp at boot?
Best regards, and thank you for reading:
– Thom
P.S. Yes, I could symbolically link the directory to the appropriate
/fs/hd-qnx4, but that solution isn’t elegant.
Hi Thom,
Banish diskboot from image. Take a look at thread “Booting without diskboot” in
qdn.public.qnxrtp.installation, created 09 Nov 01. Take a look at articles on QDN web site (links
are in that thread).
I downloaded QNX RTP 6.1.0 a few days ago. I’m having difficulties
getting a second and third partition to mount to specific (standard) points.
I’ve dedicated my P233, with 4 (tiny) scsi drives, entirely to QNX (no
windows, linux, *bsd, etc). The first drive, hd0t79 is the boot drive,
and works as expected, although it’s 87% full. The other three drives,
after a sound fdisk’ing and dinit’ing automatically get mounted to
/fs/hd-qnx4 at boot (where is 1-3).
I would like to mount the remaining drives, hd1t79;hd2t79;hd3t79, to
/home, /var, and /tmp respectively.
Things I’ve tried to no sucess:
Creating rc.local (owned by root.sys, with 775 access) in /etc/rc.d
with the lines:
mount -t qnx4 /dev/hd1t79 /home
mount -t qnx4 /dev/hd2t79 /var
mount -t qnx4 /dev/hd3t79 /tmp
I guess you have to umount before…
Adding the text
“automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to DEVB_OPTIONS in /etc/system/enum/include/block.
It seems for me like “Keyboard not present, press F1 to continue”. But there are people with other
point of view
Bulding a custom image by appending “-odevb-aha4
automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to where diskboot gets called in my build script (which is just a copy
of /boot/build/qnxbasedma.build)
(I did run mkifs, I did copy the new image to /.boot, and I did reboot
the system, everything worked fine EXCEPT getting the drives to mount to
the points I want them).
It just add your options to end of standard line, driver ignore it. It is knowen bug of diskboot.
creating another custom image where, after calling diskboot, I added
the lines:
mount -t qnx4 /dev/hd1t79 /home
mount -t qnx4 /dev/hd2t79 /var
mount -t qnx4 /dev/hd3t79 /tmp
(again, mkifs, cp /.boot, shutdown, reboot, no joy).
Did you unmount? Did you include mount and umount to image?
Rid diskboot at all
Cursing and gnashing my teeth
So, I’m at a loss. How do I get /dev/hd1t79 to mount to /home,
/dev/hd2t79 to mount to /var, and /dev/hd3t79 to mount to /tmp at boot?
Best regards, and thank you for reading:
– Thom
P.S. Yes, I could symbolically link the directory to the appropriate
/fs/hd-qnx4, but that solution isn’t elegant.
Bulding a custom image by appending “-odevb-aha4
automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to where diskboot gets called in my build script (which is just a copy
of /boot/build/qnxbasedma.build)
You could start the driver before diskboot with these options (read help for all options, or just
type “pidin ar |grep devb-aha4” to get default args). AND you have to EXCLUDE the driver for
diskboot by appending -xdevb-aha4.
Bulding a custom image by appending “-odevb-aha4
automount=hd1t79:/home:qnx4,automount=hd2t79:/var:qnx4,automount=hd3t79:/tmp:qnx4”
to where diskboot gets called in my build script (which is just a copy
of /boot/build/qnxbasedma.build)
You could start the driver before diskboot with these options (read help for all options, or just
type “pidin ar |grep devb-aha4” to get default args). AND you have to EXCLUDE the driver for
diskboot by appending -xdevb-aha4.
Regards,
Eduard.
Thank you so much for your help Eduard,
For some reason, diskboot was ignoring -x devb-aha4, so I went with your
first suggestion of just getting rid of diskboot.
For some reason, diskboot was ignoring -x devb-aha4, so I went with your
first suggestion of just getting rid of diskboot.
Good news for entomologist. I have no SCSI drives, so I did not try it, sorry. But -xdevb-eide
works well - diskboot completely skips across the “Detecting EIDE…” section. I’m guessing
here, but maybe SCSI detection is in this section too. (I never saw “Detecting SCSI…” message )
