Sin ve

Is there a QNX6 equivlant to sin ve?
Is there documentation about how a program I am writing can reply to a
version request?


Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net

“Bill Caroselli” <qtps@earthlink.net> wrote in message
news:9ruk7a$fsf$2@inn.qnx.com

Is there a QNX6 equivlant to sin ve?

You could look at the manifest for the program groups you’re looking for.
Eg. /pkgs/base/qnx/os/core-2.1.2/MANIFEST. Of course spilled files would
cause problems.

Is there documentation about how a program I am writing can reply to a
version request?

I’m not sure what a “version request” might look like - my thoughts would be
a special ioctl message (or devctl if your prefer). But then all
applications would have to respond to this “devctl”.

-Adam

OK.
It sounds like the short answer is no.

In QNX 4 a server type of process could register with proc and say, "I am
willing to answer version requests. Then when someone typed sin ve, sin (or
Proc on behalf on sin) would iterate through each process and send a version
request back to Proc. Sin would then display this information to the
screen. It was a very easy way for the user to get version information from
all important running processes.

But wait! If you act right now you get more!

Since this information is returned dynamically it was a great way to get
state information from a running process. I guess you could send a signal
to the process and let it print out it’s own information. But then you have
no way of telling the server process ‘where’ to display that information.


Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Operating System Tech Support” <os@qnx.com> wrote in message
news:9rut1g$dkb$1@nntp.qnx.com

“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:9ruk7a$fsf$> 2@inn.qnx.com> …
Is there a QNX6 equivlant to sin ve?

You could look at the manifest for the program groups you’re looking for.
Eg. /pkgs/base/qnx/os/core-2.1.2/MANIFEST. Of course spilled files would
cause problems.

Is there documentation about how a program I am writing can reply to a
version request?

I’m not sure what a “version request” might look like - my thoughts would
be
a special ioctl message (or devctl if your prefer). But then all
applications would have to respond to this “devctl”.

-Adam

Bill Caroselli <qtps@earthlink.net> wrote:

OK.
It sounds like the short answer is no.

In QNX 4 a server type of process could register with proc and say, "I am
willing to answer version requests. Then when someone typed sin ve, sin (or
Proc on behalf on sin) would iterate through each process and send a version
request back to Proc. Sin would then display this information to the
screen. It was a very easy way for the user to get version information from
all important running processes.

But wait! If you act right now you get more!

Since this information is returned dynamically it was a great way to get
state information from a running process. I guess you could send a signal
to the process and let it print out it’s own information. But then you have
no way of telling the server process ‘where’ to display that information.

Here’s an idea. Can either QSSL decide that “yes there will be a version
number message, here’s the defined IOCTL number, and here’s the format.”
or can “we the community” decide that “by convention” we’ll use a certain
number with a certain format.

I can see the need for the version number message; so I think it would be
in everyone’s best interest if QSSL simply defined an IOCTL and a struct
for it and left it at that. The only work on QSSL’s part would be to
add a “ver” command to “pidin”.

As an enhancement, you might also consider an id function for threads :slight_smile:

Cheers,
-RK



Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net



“Operating System Tech Support” <> os@qnx.com> > wrote in message
news:9rut1g$dkb$> 1@nntp.qnx.com> …
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:9ruk7a$fsf$> 2@inn.qnx.com> …
Is there a QNX6 equivlant to sin ve?

You could look at the manifest for the program groups you’re looking for.
Eg. /pkgs/base/qnx/os/core-2.1.2/MANIFEST. Of course spilled files would
cause problems.

Is there documentation about how a program I am writing can reply to a
version request?

I’m not sure what a “version request” might look like - my thoughts would
be
a special ioctl message (or devctl if your prefer). But then all
applications would have to respond to this “devctl”.

-Adam


Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at www.parse.com
Email my initials at parse dot com.

<nospam93@parse.com> wrote in message news:9s428r$qr8$2@inn.qnx.com

Bill Caroselli <> qtps@earthlink.net> > wrote:
OK.
It sounds like the short answer is no.

In QNX 4 a server type of process could register with proc and say, "I
am
willing to answer version requests. Then when someone typed sin ve, sin
(or
Proc on behalf on sin) would iterate through each process and send a
version
request back to Proc. Sin would then display this information to the
screen. It was a very easy way for the user to get version information
from
all important running processes.

But wait! If you act right now you get more!

Since this information is returned dynamically it was a great way to get
state information from a running process. I guess you could send a
signal
to the process and let it print out it’s own information. But then you
have
no way of telling the server process ‘where’ to display that
information.

Here’s an idea. Can either QSSL decide that “yes there will be a version
number message, here’s the defined IOCTL number, and here’s the format.”
or can “we the community” decide that “by convention” we’ll use a certain
number with a certain format.

I can see the need for the version number message; so I think it would be
in everyone’s best interest if QSSL simply defined an IOCTL and a struct
for it and left it at that. The only work on QSSL’s part would be to
add a “ver” command to “pidin”.

As an enhancement, you might also consider an id function for threads > :slight_smile:

I’ve complain about this 2-3 months ago and got no feedback.

For now all my resource manager attach a */version file. Hence I can
do “cat /dev/resmgr/version” .

Cheers,
-RK

\

Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Operating System Tech Support” <> os@qnx.com> > wrote in message
news:9rut1g$dkb$> 1@nntp.qnx.com> …
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:9ruk7a$fsf$> 2@inn.qnx.com> …
Is there a QNX6 equivlant to sin ve?

You could look at the manifest for the program groups you’re looking
for.
Eg. /pkgs/base/qnx/os/core-2.1.2/MANIFEST. Of course spilled files
would
cause problems.

Is there documentation about how a program I am writing can reply to
a
version request?

I’m not sure what a “version request” might look like - my thoughts
would
be
a special ioctl message (or devctl if your prefer). But then all
applications would have to respond to this “devctl”.

-Adam




\

Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at > www.parse.com
Email my initials at parse dot com.

Nice solution Mario.

It is easy to find and allows a resmgr to determine exactly what
info it needs to return.

That takes me to my next question that I’ve meant to ask a number
of times…

I’m used to walking the prefix tree in QNX4…
I know about /proc/mount in NTO…
I am aware of the ‘union’ filesystem in NTO…

How do you walk the “prefix” tree in NTO to find out exactly
what “prefixes” are registered, which processes have registered
for them, and what their resolution priority is for a give “prefix”.

I’ve looked at the io_open code and the calls it makes but it seems
way to kludgy to walk every directory entry and ask for resolution
and see what responds.

The reason I ask is if you can get a list of “prefixes” and processes
then the version file is easy. Make it “hidden” and just remember
that you could have multiple version files for a given mount point
(/ = /fs/… and fs-pkg) so you have to “open” each one and read
using io_open logic.

I also want this to help my understanding and debugging skills :wink:

Thanks,
Jay


Mario Charest wrote in message <9s4i9m$70f$1@inn.qnx.com>…

nospam93@parse.com> > wrote in message news:9s428r$qr8$> 2@inn.qnx.com> …
Bill Caroselli <> qtps@earthlink.net> > wrote:
OK.
It sounds like the short answer is no.

In QNX 4 a server type of process could register with proc and say, "I
am
willing to answer version requests. Then when someone typed sin ve,
sin
(or
Proc on behalf on sin) would iterate through each process and send a
version
request back to Proc. Sin would then display this information to the
screen. It was a very easy way for the user to get version information
from
all important running processes.

But wait! If you act right now you get more!

Since this information is returned dynamically it was a great way to
get
state information from a running process. I guess you could send a
signal
to the process and let it print out it’s own information. But then you
have
no way of telling the server process ‘where’ to display that
information.

Here’s an idea. Can either QSSL decide that “yes there will be a version
number message, here’s the defined IOCTL number, and here’s the format.”
or can “we the community” decide that “by convention” we’ll use a certain
number with a certain format.

I can see the need for the version number message; so I think it would be
in everyone’s best interest if QSSL simply defined an IOCTL and a struct
for it and left it at that. The only work on QSSL’s part would be to
add a “ver” command to “pidin”.

As an enhancement, you might also consider an id function for threads > :slight_smile:

I’ve complain about this 2-3 months ago and got no feedback.

For now all my resource manager attach a */version file. Hence I can
do “cat /dev/resmgr/version” .


Cheers,
-RK

\

Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net


“Operating System Tech Support” <> os@qnx.com> > wrote in message
news:9rut1g$dkb$> 1@nntp.qnx.com> …
“Bill Caroselli” <> qtps@earthlink.net> > wrote in message
news:9ruk7a$fsf$> 2@inn.qnx.com> …
Is there a QNX6 equivlant to sin ve?

You could look at the manifest for the program groups you’re looking
for.
Eg. /pkgs/base/qnx/os/core-2.1.2/MANIFEST. Of course spilled files
would
cause problems.

Is there documentation about how a program I am writing can reply to
a
version request?

I’m not sure what a “version request” might look like - my thoughts
would
be
a special ioctl message (or devctl if your prefer). But then all
applications would have to respond to this “devctl”.

-Adam




\

Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Consulting and Training at > www.parse.com
Email my initials at parse dot com.