First, my apologies for not getting to this sooner. I only
became aware today…
At first glance I would agree with Colin that the license
issue is not related (it would be related to the mounting
diskboot does when running in safe mode). It would appear
that diskboot is broken w.r.t. to the debug shell and/or
I have run in safe mode to get to a standard login many times,
typically when I mess up my Photon settings. I have yet to
see this problem. Though it looks easy to reproduce.
I’m looking into it and will post my findings shortly.
I will also investigate how to improve the usability of the safe
mode to make it really safe. I’m thinking along the lines of
standard *nix single user mode. One console, no extra drivers
beyond what is in the boot image.
BTW, there is a sample build file in the helpveiwer documentation
which performs the same basic functionality as diskboot. I believe
it is in the Neutrino User’s Guide Appendix (Examples). This would
not help in this case since the drivers and other services are started
via etc/system/sysinit, not diskboot.
John Nagle wrote:
We haven’t heard anything.
This is apparently a problem with overly aggressive
copy protection in “diskboot”, which runs so early
that a workaround is tough. We may have to wait
for the next release of QNX. Our QNX 6.3 test system
sits idle, awaiting a fix.
We continue to use QNX 6.21 for real work. It’s working
well for us. We demonstrated our robot vehicle to about
30 people today, in our first public demo. Some well known
Silicon Vally names were present.
We may just stay with QNX 6.21, rather than fighting
with the copy protection in 6.3. It eats up too much
of our time.
Evan Hillas wrote:
John Nagle wrote:
F1 F3 yields a mode in which the file systems are mounted.
As the help page says:
The chkfsys utility should be used only when the filesystem is stable.
There should be NO files open for writing when chkfsys is running.
You CAN run “chkfsys” from the F1 F3 state, but it does NOT lead
to a clean file system. I’m unable to reach a state where
“chkfsys” reports no errors. If I reboot and rerun it again,
I see problems caused by daemons which have been started up.
The F1 F3 “safe mode” mounts all file systems, runs
the “rc.local” file, and even starts up “lpd”.
That’s not “safe” enough for “chkfsys”.
So it seems that if a QNX 6.3 system crashes, no simple
recovery is possible.