I have an QNX 6.1, embedded system that runs without photon. The systems are
going to be installed in locations where they would only be accessible
through a telnet/ftp session. I would like to upgrade the embedded system
periodically and using packages seems like the way to go. Is there a way to
install packages without the photon package manager and without the file
manipulation that I read about in the knowledge base article on the same
subject? Ideally, I’d like to find a method that I could do
programmatically, rather than directly under human control.
Thanks,
David Kuechenmeister
David Kuechenmeister <david.kuechenmeister@viasat.com> wrote:
I have an QNX 6.1, embedded system that runs without photon. The systems are
going to be installed in locations where they would only be accessible
through a telnet/ftp session. I would like to upgrade the embedded system
periodically and using packages seems like the way to go. Is there a way to
install packages without the photon package manager and without the file
manipulation that I read about in the knowledge base article on the same
subject? Ideally, I’d like to find a method that I could do
programmatically, rather than directly under human control.
There was a cl-installer at some point – don’t know if it existed
in 6.1. Don’t know how much interactivity it needed, but there’s
always popen().
Do you expect to need to backdate to earlier releases on the embedded
system?
One of the big things that the package filesystem brings is that
ability to activate/deactivate.
If not, you might consider going without the overhead of the package
filesystem, and just using .tar.gz files for your updates, with:
gunzip update.tar.gz | tar -x
being your install command.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Good points. I don’t expect to backdate to any previous releases, so maybe
the package filesystem is going to be unnecessary. I had thought that it
would make controlling releases a little easier, but that is less important
than reducing the memory/cpu use on the embedded processor.
As a side note, tar -xvzf update.tar.gz should give me the same result as
gzip -d update.tar.gz | tar -xvf, shouldn’t it?
Thanks for making the problem more clear.
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:avhjum$svq$1@nntp.qnx.com…
David Kuechenmeister <> david.kuechenmeister@viasat.com> > wrote:
I have an QNX 6.1, embedded system that runs without photon. The systems
are
going to be installed in locations where they would only be accessible
through a telnet/ftp session. I would like to upgrade the embedded
system
periodically and using packages seems like the way to go. Is there a way
to
install packages without the photon package manager and without the file
manipulation that I read about in the knowledge base article on the same
subject? Ideally, I’d like to find a method that I could do
programmatically, rather than directly under human control.
There was a cl-installer at some point – don’t know if it existed
in 6.1. Don’t know how much interactivity it needed, but there’s
always popen().
Do you expect to need to backdate to earlier releases on the embedded
system?
One of the big things that the package filesystem brings is that
ability to activate/deactivate.
If not, you might consider going without the overhead of the package
filesystem, and just using .tar.gz files for your updates, with:
gunzip update.tar.gz | tar -x
being your install command.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
David Kuechenmeister <david.kuechenmeister@viasat.com> wrote:
Good points. I don’t expect to backdate to any previous releases, so maybe
the package filesystem is going to be unnecessary. I had thought that it
would make controlling releases a little easier, but that is less important
than reducing the memory/cpu use on the embedded processor.
That was my thought.
As a side note, tar -xvzf update.tar.gz should give me the same result as
gzip -d update.tar.gz | tar -xvf, shouldn’t it?
I’ve never actually used the -z flag to tar. I would expect it would
be the equivalent of “gzip -d update.tar.gz | tar -xv”. You don’t want
the -f on the tar at the end of the pipe. is the -f is the “here is a file”
flag. You don’t want that in the piped case.
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.