Hi all,
I saw some strange behaviors from the Momentics 6.3,
- nfs mount a file system while fs-nfs2 was not started, the mount command
returned OK without mounting anything.
- /.boot couldn’t be removed even if root has rwx permission on /.
- copy a new kernel into /.boot, /.boot would not appear as changed (using
ls -l), although it was. The new size of /.boot only appeared after a
reboot.
Thanks for your comments.
Phungte
Phungte <phungte@decru.com> wrote:
Hi all,
I saw some strange behaviors from the Momentics 6.3,
- nfs mount a file system while fs-nfs2 was not started, the mount command
returned OK without mounting anything.
That shouldn’t have happened – if fs-nfs2 is not running, the mount
should fail.
So, exactly what mount command did you issue?
- /.boot couldn’t be removed even if root has rwx permission on /.
This is expected and documented (somewhere) behaviour.
There are some special files in / that can not be removed. They include
…boot, .altboot, .bitmap, and .inodes.
- copy a new kernel into /.boot, /.boot would not appear as changed (using
ls -l), although it was. The new size of /.boot only appeared after a
reboot.
I have never seen this behaviour. Any copy to/from /.boot has always
resulted in the size changing appropriately, and the date changing
appropriately.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
David Gibbs <dagibbs@qnx.com> wrote:
- /.boot couldn’t be removed even if root has rwx permission on /.
This is expected and documented (somewhere) behaviour.
Neutrino User’s Guide
Controlling How Neutrino Starts
Loading a Neutrino image
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems
David Gibbs <dagibbs@qnx.com> wrote:
Phungte <> phungte@decru.com> > wrote:
Hi all,
I saw some strange behaviors from the Momentics 6.3,
- nfs mount a file system while fs-nfs2 was not started, the mount command
returned OK without mounting anything.
That shouldn’t have happened – if fs-nfs2 is not running, the mount
should fail.
I tested with 6.3.0 SP1, apparently PR 19039 fixed this issue with
SP1, and it was broken under 6.3.0.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com