John Garvey wrote:
When I put options in /.diskroot as suggested by kabe, I get
a readonly fs and I can recover write permission by booting
from another disk/partition. I can also issue a
mount -ru /dev/hd0t79 /
on the readonly mount and it appears to succeed: mount
returns 0 to the shell and prints no error. But the fs
is still readonly. Is this intended?
Yes. You’ve asked that it be remounted as read-only … try:
“mount -u /” (ie ‘-r’ is a state, not a toggle, and again note
that I target the filesystem and not the partition).
Sorry, silly mistake. I meant -wu; I just tried that and it did
fail so I must really have used -ru before.
All the same, it still fails:
mount -u /
mount: Can’t remount / (type default)
mount: Possible reason: Resource busy
I guess this is because of what else is mounted, as you described.
The first line here looks a likely candidate:
/pkgs/repository/waukes/htdoc/core-1.0 on / type pkg
/dev/hd0t77 on / type qnx4
/dev/hd2t77 on /tmp/ram type qnx4
/dev/hd1t77 on /flash type qnx4
saturn:/home on /home type NFSv2
/boot/fs/qnxbase.qfs on /pkgs/base type qnx4
Interestingly, if I mount the root filesystem read-only and then
mount another filesystem read-write on /fs, for example /fs/ram,
then the following fails:
mkdir -p /fs/ram/a/b
mkdir: /fs: No such file or directory
mkdir: /fs/ram/a/b: No such file or directory
Thanks for your help