Tried to rename .altboot on a running system, to prepare
for testing a new boot image. “mv .altboot oldaltboot” yielded
a “resource busy” message. Tried this on 6.2.1NC and 6.2.1PE,
on two different machines. So how do I install a new .boot
or .altboot without clearing the whole disk?
John Nagle
Team Overbot
…boot and .altboot are ‘special’, you can’t move them. You can,
however, copy from and onto them.
John Nagle <nagle@overbot.com> wrote:
Tried to rename .altboot on a running system, to prepare
for testing a new boot image. “mv .altboot oldaltboot” yielded
a “resource busy” message. Tried this on 6.2.1NC and 6.2.1PE,
on two different machines. So how do I install a new .boot
or .altboot without clearing the whole disk?John Nagle
Team Overbot
John Nagle <nagle@overbot.com> wrote:
Tried to rename .altboot on a running system, to prepare
for testing a new boot image. “mv .altboot oldaltboot” yielded
a “resource busy” message. Tried this on 6.2.1NC and 6.2.1PE,
on two different machines. So how do I install a new .boot
or .altboot without clearing the whole disk?
cp /.altboot /oldaltboot
cp newboot /.altboot
/.boot and /.altboot can not be unlinked, renamed, etc. They can
be opened for read/write – so the contents can be changed – but
their place in the pathnamespace can not.
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Ah. I was being cautious and trying to move them. Thanks.
It would be useful to document this where
Helpviewer can find it, perhaps in the “mkifs” document.
John Nagle
Team Overbot
David Gibbs wrote:
John Nagle <> nagle@overbot.com> > wrote:
Tried to rename .altboot on a running system, to prepare
for testing a new boot image. “mv .altboot oldaltboot” yielded
a “resource busy” message. Tried this on 6.2.1NC and 6.2.1PE,
on two different machines. So how do I install a new .boot
or .altboot without clearing the whole disk?
cp /.altboot /oldaltboot
cp newboot /.altboot/.boot and /.altboot can not be unlinked, renamed, etc. They can
be opened for read/write – so the contents can be changed – but
their place in the pathnamespace can not.-David
John Nagle <nagle@downside.com> wrote:
: Ah. I was being cautious and trying to move them. Thanks.
: It would be useful to document this where
: Helpviewer can find it, perhaps in the “mkifs” document.
I’ll pass this on to the writer, and I’ll add it to the Neutrino
User’s Guide. Thanks for the suggestion.