Hello again!
After looking through this thread I’ve realized that I’m not being very
clear with my questions. So here is a from-the-top description of my
problem.
My disk:
partition partition
type
---------±----------
1 primary linux
2 primary linux
3 primary none (used to be qnx4.x and had QNX on it for a while)
4 extended — container for logical partitions
5 logical linux
6 logical linux
7 logical qnx4.x
8 logical linux
Situation:
I installed QNX (using the CD) on partition 3. I configured the linux boot
loader (LILO in my case) to boot it and it worked fine.
I then did a raw bit-by-bit copy of partition 3 to partition 7, and set up
LILO to boot QNX from partition 7 instead of 3.
(Partition 7 is all under 1024 cylinders)
When I rebooted and chose qnx it actually booted, and gave me a choice of 2
different disk devices to use as root.qfs. If I chose the first one (I
think it was that one that corresponded to partition 3) it booted no
problem. If I chose the second one, it got stuck trying to install
/dev/par port.
I then deleted the contents of partition 3 alltogether and booted again and
now QNX no longer boots, it gets stuck on the
Press Esc for .altboot…
line.
So now I’m asking if it’s even possible to boot QNX off such an extended
partition, and if yes, how it could be done.
Also, the experiment with partition 3 leads me to believe that QNX makes
note of some hard-coded disk addresses for the purposes of booting. Is
this true, and therefore makes QNX unmovable among partitions after
install?
Thanks!
Dana
–
Dana Echtner \ Real-Time Systems Administrator
dana@ece.concordia.ca / ECE, Concordia University, Montreal, Canada
rw-rw-rw-: The file protection of the beast