2 Outstanding Issues

[Author's Comments: These are some questions that need to be answered in this document]

Outstanding issues

• Putting new libs in /lib or /usr/lib does not make them available.

  [Author's Comments: Libraries added with the package filesystem include a preprocessor tag specifying the processor. What this means is that binary data, like libraries are install into: /$PROCESSOR/lib,/usr/lib,/bin,/sbin,/usr/sbin,/usr/bin
  Our linker, by default looks in these processor directories - now, if you have an LD_LIBRARY_PATH set with additional values looking into /lib and /usr/lib it should find your new libs. The processor directory at root is used for cross
  platform development, enabling you to hold different library data for different processors on a single machine.]

• No docs mention the pkg spill.

  [Author's Comments: see package filesystem technote]

  [Author's Comments: When to use pkg spill? If a package installs a file to your machine and you plan on modifying it - be aware that your version is actually stored in /var/pkg/spill. If you delete a file installed by a package, the file is only hidden from your filesystem. Since you have not really deleted the package, you can uninstall it. There is a '.fspkg-spilled' file with the names of each file you have modified or deleted. By removing a name and restarting the package filesystem, the file will reappear.]

• There are links to the Quick Tour, however the Quick Tour isn't part of the bookset anymore
• Do we need a separate paragraph on monitoring the system?
• Need something on adjusting priority-nice
• Can I install the voyager 128bit security update? I don't know where to get a key from.
• I want to create a qnx rtp boot disk with only the minimum components required to load the OS and the embedded web server
• Some of the utilities in /sbin can be started by users other than root if they have the right permission, but users other than root cannot see a description of these utilities using "use" unless they have /sbin in their PATH (or, e.g., type use /sbin/tinit)
• Take a look at the old (version 1.14) Photon Users Guide and Installation & Configuration for ideas on further coverage for this doc.
• Q: I know that the sysinit file is no longer available under RTP, but how do I customize my init activities? (for example: I have a second hard drive with more QNX partitions that I want to mount as /home2, I also init the serial ports at a higher baud rate and specific interrupts, and other like issues...) A1: For the HD you could create a file call /etc/rc.d/rc.local. For the higher baud rate I would use the stty command and run it inside rc.local. For changing interrupt I don't know what is the clean way to change that.