I have downloaded QRTP and a number of the packages. All is well as far as
that goes. But . . .
QRTP is currently installed on top of the Windlows file system. I have
allocated a partition type 77 and want to copy all of the OS, etc. to it’s
own partition. I was able to copy using:
cp -cLnRv / /part77
but there are quite a number of directories that don’t get copied like /home
& /root.
What is the proper way to move QRTP to it’s own partition?
(BTW, I have done this a gazillion times with QNX4 so I’m not a complete
newbie.)
More important question, where is this documented?
(I did make a major effort to find documentation.)
I have downloaded QRTP and a number of the packages. All is well as far as
that goes. But . . .
QRTP is currently installed on top of the Windlows file system. I have
allocated a partition type 77 and want to copy all of the OS, etc. to it’s
own partition. I was able to copy using:
cp -cLnRv / /part77
but there are quite a number of directories that don’t get copied like /home
& /root.
I have downloaded QRTP and a number of the packages. All is well as far
as
that goes. But . . .
QRTP is currently installed on top of the Windlows file system. I have
allocated a partition type 77 and want to copy all of the OS, etc. to
it’s
own partition. I was able to copy using:
cp -cLnRv / /part77
but there are quite a number of directories that don’t get copied like
/home
& /root.
I have downloaded QRTP and a number of the packages. All is well as
far
as
that goes. But . . .
QRTP is currently installed on top of the Windlows file system. I
have
allocated a partition type 77 and want to copy all of the OS, etc. to
it’s
own partition. I was able to copy using:
cp -cLnRv / /part77
but there are quite a number of directories that don’t get copied like
/home
& /root.
Bill at Sierra Design <> BC@sierradesign.com> > wrote:
Aren’t directories like /home & /root implemented on the main file system?
I thought they were, but I’m not the file system guru here… maybe someone
else here can comment…
If I use -D in my copies won’t that include a lot of directoies that I don’t
want, like /proc and the Windows file system?
Also, can I continue to use the default boot image?
I assume not.
What must I do to make the new /dev/hd0t77 my / directory?
Well, your root filesystem in a windows install actually resides in
/Program Files/qnx/boot/fs/root.qfs which is mounted by diskboot (in the
boot image) so yes, it is on a ‘different’ file system. Also note that you
are probably copying the system files three times: once in /bin, once in
/x86/bin and from the package (/pkgs/base/qnx/os/core2.1/x86/bin).
Your best bet is to do this (I haven’t tested this but it should work):
Start with a clean t79 partition.
Copy /Program Files/qnx/boot/fs/qnxbase.qfs to /boot/fs on partition.
Copy /Program Files/qnx/boot/fs/qnxbase.ifs to /.boot on partition.
Create a file in the root of your partition called .diskroot.
It should contain the character ‘/’ (this tells diskboot that this is your
root filesystem).
You should be able to booot from the partition now. All those directories
which are missing will be created on the initial boot.
Once up and running you can mount your old root.qfs file:
mount “/fs/hd0-dos/Program Files/qnx/boot/fs/root.qfs” /oldroot
Now you can copy the needed files from /oldroot.
Note that I may have some locations a bit wrong, but that’s basically
how the partition installer off the CD works. Of course installing using
the CD would be easiest. then mount the qfs file as above.
Your best bet is to do this (I haven’t tested this but it should work):
Start with a clean t79 partition.
Copy /Program Files/qnx/boot/fs/qnxbase.qfs to /boot/fs on partition.
Copy /Program Files/qnx/boot/fs/qnxbase.ifs to /.boot on partition.
Create a file in the root of your partition called .diskroot.
Thank you. This should help.
It should contain the character ‘/’ (this tells diskboot that this is
your
root filesystem).
This is cool. Under Q4 I’ve had to implement something similar to mount
removable disks.
What I wanted was a way to say on each disk, “When this disk is mounted,
mount it here in the QNX namespace”.
But, “Ut Oh” (In an ICQ sounding voice) . . .
If I have disk partitions that I want mounted under one name at some times,
and mounted under a different name at other times (Primary boot vs.
Alternate boot, etc.) this mechanism seems like it would get in the way.
If the .diskroot file is missing, will it just not automount and wait for me
to mount it by hand?
Note that I may have some locations a bit wrong, but that’s basically
how the partition installer off the CD works. Of course installing using
the CD would be easiest. then mount the qfs file as above.
True. If I had a CD drive!
QNX still doesn’t get it. There are many, many, MANY systems out there with
minimal hardware.
THAT’S WHY WE CHOSE QNX!
If I have disk partitions that I want mounted under one name at some times,
and mounted under a different name at other times (Primary boot vs.
Alternate boot, etc.) this mechanism seems like it would get in the way.
If the .diskroot file is missing, will it just not automount and wait for me
to mount it by hand?
Depends. I believe diskboot will default to using the t79 partition if
no .diskroot file exists. Note that the .diskroot file is only used by
dikboot on startup. Thus it’s only useful when running RTP and using the
default image. Otherwise you would have to mount by hand. So I don’t think
it would get in the way.
keith@qnx.com> > wrote in message news:8t9f1r$nfc$> 1@nntp.qnx.com> …
Your best bet is to do this (I haven’t tested this but it should work):
Start with a clean t79 partition.
Copy /Program Files/qnx/boot/fs/qnxbase.qfs to /boot/fs on partition.
Copy /Program Files/qnx/boot/fs/qnxbase.ifs to /.boot on partition.
Create a file in the root of your partition called .diskroot.
Thank you. This should help.
QNX still doesn’t get it. There are many, many, MANY systems out there with
minimal hardware.
THAT’S WHY WE CHOSE QNX!
I know exactly what you mean Bill, but
a) RTP is a public pre-release
b) RTP is for non-commercial use
c) RTP has a required hardware list that includes a CD-ROM drive
d) RTP is a full development system… not just a target
Most of your comments are valid, and will be addressed, but I don’t think
it’s fair to suggest that we `still don’t get it’.
QNX still doesn’t get it. There are many, many, MANY systems out there
with
minimal hardware.
THAT’S WHY WE CHOSE QNX!
I know exactly what you mean Bill, but
a) RTP is a public pre-release
b) RTP is for non-commercial use
c) RTP has a required hardware list that includes a CD-ROM drive
d) RTP is a full development system… not just a target
Most of your comments are valid, and will be addressed, but I don’t think
it’s fair to suggest that we `still don’t get it’.