Replace .boot file

QNX Newsgroups (Archives) qdn.public.qnxrtp.os
1

Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in “boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff

2

Try to place your newly created boot file as /.altboot and then during boot
press ESC for booting altboot.

–
Jens

“Jeff HOFFMEYER” <jean-francois.hoffmeyer@schiller.fr> wrote in message
news:bgo6q0$dvb$1@inn.qnx.com…

Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in
“boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff

3

The device has no keyboard, it is not a standard PC but an industrial
device.

“Jens H Jorgensen” <jhj@remove-nospam-videk.com> a écrit dans le message
news: bgo853$emc$1@inn.qnx.com…

Try to place your newly created boot file as /.altboot and then during
boot
press ESC for booting altboot.

–
Jens

“Jeff HOFFMEYER” <> jean-francois.hoffmeyer@schiller.fr> > wrote in message
news:bgo6q0$dvb$> 1@inn.qnx.com> …
Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in
“boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff

\

4

Can you boot to another partition?

How was QNX installed on the embedded system?

–
Jens



“Jeff HOFFMEYER” <jean-francois.hoffmeyer@schiller.fr> wrote in message
news:bgoe7b$j58$1@inn.qnx.com…

The device has no keyboard, it is not a standard PC but an industrial
device.

“Jens H Jorgensen” <> jhj@remove-nospam-videk.com> > a écrit dans le message
news: bgo853$emc$> 1@inn.qnx.com> …
Try to place your newly created boot file as /.altboot and then during
boot
press ESC for booting altboot.

–
Jens

“Jeff HOFFMEYER” <> jean-francois.hoffmeyer@schiller.fr> > wrote in message
news:bgo6q0$dvb$> 1@inn.qnx.com> …
Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in
“boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff



\

5

/.boot is not an ordinary file, and does not allow itself to be removed.
This causes cp invocations with the -f flag to fail. Try it without -f.

Marty Doane
Siemens Dematic

“Jeff HOFFMEYER” <jean-francois.hoffmeyer@schiller.fr> wrote in message
news:bgo6q0$dvb$1@inn.qnx.com…

Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in
“boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff

6

In article <bgo6q0$dvb$1@inn.qnx.com>, jean-francois.hoffmeyer@schiller.fr says…

Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in “boot_script”
the instruction :
cp -vf /new_boot /.boot

try cp -t
just shoot in the dark :slight_smile:

ed1k

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff
\

7

Thanks. I try without the -f option and it works !

Jeff

“Marty Doane” <martin.doane@siemens.com> a écrit dans le message news:
bgolr1$ccu$1@nntp.qnx.com…

/.boot is not an ordinary file, and does not allow itself to be removed.
This causes cp invocations with the -f flag to fail. Try it without -f.

Marty Doane
Siemens Dematic

“Jeff HOFFMEYER” <> jean-francois.hoffmeyer@schiller.fr> > wrote in message
news:bgo6q0$dvb$> 1@inn.qnx.com> …
Hi -

I have created a .boot file with a script like this :

[virtual=x86,bios +compress] .bootstrap = {
…
…
}
[+script] .script = {
…
…
sh /DG2004/download/boot_script
esh /etc/rc.d/rc.local
}

This mean that at each boot I call a script file called “boot_script”.
Now I want to replace my .boot file automaticaly by adding in
“boot_script”
the instruction :
cp -vf /new_boot /.boot

But I always have the errors :
cp: Can’t unlink file /.boot : Resource busy
cp: Can’t open destination file. (/.boot): Resource busy

Any tricks and comments are welcome.

regards…
Jeff

\