I have a question for mkifs gurus (if this is discussed in QNX Help
somewhere please point it out).
mkifs by default will take binaries you point out and scoop them up and drop
them in /proc/boot. Basically my question is: why?
If I specify I want to include /x86/lib/libasound.so for instance why does
it go into /proc/boot and not /x86/lib/ directory on the target? Yes, I’m
aware you can do it manually. What are the benefits of a honkin’ /proc/boot
directory and scads of symlinks over actually putting the files “where they
belong” in the first place?
I have a question for mkifs gurus (if this is discussed in QNX Help
somewhere please point it out).
mkifs by default will take binaries you point out and scoop them up and
drop
them in /proc/boot. Basically my question is: why?
If I specify I want to include /x86/lib/libasound.so for instance why does
it go into /proc/boot and not /x86/lib/ directory on the target? Yes, I’m
aware you can do it manually. What are the benefits of a honkin’
/proc/boot
directory and scads of symlinks over actually putting the files “where
they
belong” in the first place?
I have a question for mkifs gurus (if this is discussed in QNX Help
somewhere please point it out).
mkifs by default will take binaries you point out and scoop them up and drop
them in /proc/boot. Basically my question is: why?
If I specify I want to include /x86/lib/libasound.so for instance why does
it go into /proc/boot and not /x86/lib/ directory on the target? Yes, I’m
aware you can do it manually. What are the benefits of a honkin’ /proc/boot
directory and scads of symlinks over actually putting the files “where they
belong” in the first place?
In your build file you can:
/x86/lib/libasound.so = /x86/lib/libasound.so
Now, it will appear to be in /x86/lib on the target.
or you could do:
/lib/libasound.so = /x86/lib/libasound.so
Since the target is KNOWN to be x86, you can just put things in
/lib, rather than pointing /lib at /x86/lib.
I have a question for mkifs gurus (if this is discussed in QNX Help
somewhere please point it out).
mkifs by default will take binaries you point out and scoop them up and drop
them in /proc/boot. Basically my question is: why?
It gives me a knowledge where is all binaries which are loaded by image. I don’t need look through
all filesystem in order to find them. I know this directory is actually in RAM and binaries are
executed in place, so delete one of them means kill process, but it’s not the same for a file on
hard disk.
If I specify I want to include /x86/lib/libasound.so for instance why does
it go into /proc/boot and not /x86/lib/ directory on the target? Yes, I’m
aware you can do it manually.
If you do not intend to mount someting else which path /x86/lib/ and hate symlinks why not? You can
do it manually
Eduard.
ed1k at ukr dot net
What are the benefits of a honkin’ /proc/boot
directory and scads of symlinks over actually putting the files “where they
belong” in the first place?
