Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete a
file in /x86/bin it disappears out of /bin, but if I create a file in /bin
or /x86/bin it does not appear in the other. The reson that I ask this is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
Rodney Stevens a écrit :
Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete a
file in /x86/bin it disappears out of /bin, but if I create a file in /bin
or /x86/bin it does not appear in the other. The reson that I ask this is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email > r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
This is for a really interesting feature of the package filesystem.
Imagine:
You could have an UC working with a x86 cpu with a hard disk which could
contain a x86 directory tree, a ppc directory tree and a mips directory tree.
Now, you decide to have a ppc diskless motherboard to do something and a mips
diskless motherboard to do other thing.
The last two cards can boot through the network or on a small image and then
their filesystem will be mapped on your x86 motherboard hard disk.
Start the three platforms, the x86 one will map the x86 directory tree as ‘/’,
the mips one will map the mips directory tree as ‘/’, the ppc one will map the
ppc directory tree as ‘/’.
What it’s important to see is that it’s not a files duplication, looking at
‘/’ is a virtual image of what exist in ‘cpu/’
you can look at the following doc for more precise infos
http://staff.qnx.com/~docs/wip.html
Regards,
Alain.
Rodney Stevens a écrit :
Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete a
file in /x86/bin it disappears out of /bin, but if I create a file in /bin
or /x86/bin it does not appear in the other. The reson that I ask this is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email > r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
I didn’t answer to the problem of the file copied in /x86/bin.
As I explained, what you see below / is an image of what is in /x86 according
to what give the package description to the package filesystem. It’s very
interesting if you want to choose what version of qrtp you want to use for
example. Like that, every package describe the file it contains. So, if you
decide to run qrtp 6.0, you will only have the 6.0 distribution below ‘/’. If
you decide to run the 6.1, you will have the 6.1 distribution’s files below
‘/’.
Regards,
Alain.
Thanks Alain
I thought it may be somthing to do with the package system and one was not
real.
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3B84A55D.C69928AB@icbt.com…
Rodney Stevens a écrit :
Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete
a
file in /x86/bin it disappears out of /bin, but if I create a file in
/bin
or /x86/bin it does not appear in the other. The reson that I ask this
is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email > r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
This is for a really interesting feature of the package filesystem.
Imagine:
You could have an UC working with a x86 cpu with a hard disk which could
contain a x86 directory tree, a ppc directory tree and a mips directory
tree.
Now, you decide to have a ppc diskless motherboard to do something and a
mips
diskless motherboard to do other thing.
The last two cards can boot through the network or on a small image and
then
their filesystem will be mapped on your x86 motherboard hard disk.
Start the three platforms, the x86 one will map the x86 directory tree as
‘/’,
the mips one will map the mips directory tree as ‘/’, the ppc one will map
the
ppc directory tree as ‘/’.
What it’s important to see is that it’s not a files duplication, looking
at
‘/’ is a virtual image of what exist in ‘cpu/’
you can look at the following doc for more precise infos
http://staff.qnx.com/~docs/wip.html
Regards,
Alain.
Alain
When I was copying files from a hard disk to my diskonchip and transfering
the devb-doc driver to the image to make the system boot off the diskonchip
the /bin /sbin /usr etc definitely took up real diskonchip space. Should I
not just copy the files over, should I some how intall the package file
system to the diskonchip. In qnx 4.25 just copying the hard disk to the
diskonchip worked fine with symbolic links to files that had different
names/locations.
Rod
“Alain Bonnefoy” <alain.bonnefoy@icbt.com> wrote in message
news:3B84CE8C.31A021AB@icbt.com…
Rodney Stevens a écrit :
Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete
a
file in /x86/bin it disappears out of /bin, but if I create a file in
/bin
or /x86/bin it does not appear in the other. The reson that I ask this
is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email > r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
I didn’t answer to the problem of the file copied in /x86/bin.
As I explained, what you see below / is an image of what is in /x86
according
to what give the package description to the package filesystem. It’s very
interesting if you want to choose what version of qrtp you want to use for
example. Like that, every package describe the file it contains. So, if
you
decide to run qrtp 6.0, you will only have the 6.0 distribution below ‘/’.
If
you decide to run the 6.1, you will have the 6.1 distribution’s files
below
‘/’.
Regards,
Alain.
Rodney Stevens a écrit :
Alain
When I was copying files from a hard disk to my diskonchip and transfering
the devb-doc driver to the image to make the system boot off the diskonchip
the /bin /sbin /usr etc definitely took up real diskonchip space. Should I
not just copy the files over, should I some how intall the package file
system to the diskonchip. In qnx 4.25 just copying the hard disk to the
diskonchip worked fine with symbolic links to files that had different
names/locations.
Rod
“Alain Bonnefoy” <> alain.bonnefoy@icbt.com> > wrote in message
news:> 3B84CE8C.31A021AB@icbt.com> …
Rodney Stevens a écrit :
Dear All
Can someone explain to me the need for the x86 directory. It seems to
contain copies of all the files in /bin /sbin /usr/bin etc. If I delete
a
file in /x86/bin it disappears out of /bin, but if I create a file in
/bin
or /x86/bin it does not appear in the other. The reson that I ask this
is
that I want to put qnxrtp 6.1 on a DiskOnChip and it would appear that I
could save a lot of space if I could do without this duplification.
Rod
Rodney Stevens
CSIRO Minerals
Phone 61 2 97106701
Fax 61 2 97106789
Email > r.stevens@minerals.csiro.au
Elan SS s/e 45/7616
http://sites.netscape.net/rodjohnstevens/homepage
I didn’t answer to the problem of the file copied in /x86/bin.
As I explained, what you see below / is an image of what is in /x86
according
to what give the package description to the package filesystem. It’s very
interesting if you want to choose what version of qrtp you want to use for
example. Like that, every package describe the file it contains. So, if
you
decide to run qrtp 6.0, you will only have the 6.0 distribution below ‘/’.
If
you decide to run the 6.1, you will have the 6.1 distribution’s files
below
‘/’.
Regards,
Alain.
In your case I don’t think so, as far as you won’t use the network boot facility
with other cpus than x86.
It’s a facility for multiplatform support.
Now, if you install the package installer on this platform and want to install
some packages or upgrade your system from it, I don’t know if it will work. I
don’t know if the package installer will specifically look for a x86 directory
or it will accept to install directly to / if x86 doesn’t exist.
Regards,
Alain.