RFC: QNX4 vs. QNX6

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

Kris Warkentin <kewarken@qnx.com> wrote:

So, if there are any utilities you wish you had or enhanced functionality to
existing utilities, now is the time to let me know so I can try to get them
on the road map.

You can add my vote for “sin fd” and “sin irq” to the list. I’d prefer to see
all the functionality of qnx4’s sin appear in qnx6’s pidin. It is just too
confusing to have pidin AND sin in qnx6, especially when neither of them do all
the things we expect of them.

ditto is pretty high up on the list. It’s essential for maintaining remote QNX
servers (such as QNXZone), especially when updating).

sendmail needs to be ported, and the patches submitted back to the authors. I
know this is somewhat in the 3rd party area, but EVERY unix OS ships with a
working sendmail.

A big one, which would involve changes at the API level as well as the utility
level would be PAM. I’d also like to see the source for “login”, “passwd”, and
“su” appear in the public CVS repository. Those utilities are “protected” by
the requirement of needing root-privs to run, and the encryption that is used.
Revealing their source does not create any security breach. If the source for
those two utilities the user community would have been able to add support for
thing like NIS/YellowPages, and PAM.
The PAM architechture is my main request though, since I beleive it would allow
for the implementation of things like NIS/YellowPages as well even if QSSL is
uncomfortable with releasing the source for the utilities I mentioned.
In a similiar vein, the source for phlogin would also be useful, there are many
instances where a developer needs to customize a login environment.

I would also like to see IBM’s MQ Series available as a runtime for QNX6. I
know it’s out there, but damned if I can find it on their site.

send/expect would also be useful for scripting.

typescript is on my list as well, and would also be welcomed by QSSL’s
customers at the various educational institutions (univerisites and such that
use Unix in their courses often require students to compile and run their
programs within a typescript session and the submit that file along with their
assignment.

I can also give you a list of issues/features with fs-pkg, but that belongs in
another thread.

logical disk volume management would be nice too, so that you could overlay
something like fs-lvm.so on top of existing fs layouts to “merge” multiple
disks into one large logical disk. HP-UX and AIX have excellent implementations
of this sort of thing for you to examine.

I’m sure I’ll think of more over time, I’ll let you know as I think of them.

22

Kris Warkentin wrote:

“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3D09F3D8.3010108@csical.com> …

Kris Warkentin wrote:

Like bill says “sin ir” → “pidin ir” also “sin fi” → “pidin fi”,
“sin fd” → “pidin fd” allow pidin to take a process file name as in
"sin -P ".


Actually, "pidin -P " was fixed a while ago: it’s on 6.2.

The “sin irq” seems to be one of the most requested items I see. What I get
from the above though is that you would like to see certain functionality
from sin put into pidin, perhaps making pidin into ‘the only system info
tool you’ll ever need’.

Yes, one system information tool is desired, however, I couldn’t care
less what name it is given.

Rennie

23

I want to add my vote for a better GDB. I just had the most exhausting day
debugging with the current GDB. I’m starting to see where it has problems,
but I have never EVER taken so long debugging a system than today.
Something has got to be done about this thing. I don’t claim to be the best
developer it the world, but Watcom’s debugger was MUCH better, even some of
the older Borland stuff is better than this. This thing really hurt my
productivity today.

Kevin

“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:aedho6$q6o$1@nntp.qnx.com…

Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but don’t
in
QNX6 but I’m also taking general utils feature requests.

So, if there are any utilities you wish you had or enhanced functionality
to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.

cheers,

Kris

24

I’ve got “who” in our CVS tree. I also got a few things fixed up in tinit
and telnetd (login was already good) to make sure that utmp and wtmp are
kept up to date properly. These are mostly just a matter of getting it
packed and shipped. The other thing would be to wire some utmp/wtmp
accounting into pterms and phlogin. That would be something for the
development roadmap.

Someone else (cdm maybe?) had written a who that figured it out by some
other mechanism but, since all the wtmp/utmp stuff is in place and is the
standard unix way, it seemed best to do it this way. One thought: if
whoever has the non-utmp who would give me the code, I could wire it into
who as a fallback if utmp/wtmp aren’t there.

cheers,

Kris

“Robert Krten” <nospam88@parse.com> wrote in message
news:aedsd6$67$2@inn.qnx.com…

Kris Warkentin <> kewarken@qnx.com> > wrote:
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but don’t
in
QNX6 but I’m also taking general utils feature requests.

who and whois would be nice > :slight_smile: > > :slight_smile:

So, if there are any utilities you wish you had or enhanced
functionality to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.


Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at > www.parse.com> .
Email my initials at parse dot com.

25

Kris Warkentin <kewarken@qnx.com> wrote:

I’ve got “who” in our CVS tree. I also got a few things fixed up in tinit
and telnetd (login was already good) to make sure that utmp and wtmp are
kept up to date properly. These are mostly just a matter of getting it
packed and shipped. The other thing would be to wire some utmp/wtmp
accounting into pterms and phlogin. That would be something for the
development roadmap.

Someone else (cdm maybe?) had written a who that figured it out by some
other mechanism but, since all the wtmp/utmp stuff is in place and is the
standard unix way, it seemed best to do it this way. One thought: if
whoever has the non-utmp who would give me the code, I could wire it into
who as a fallback if utmp/wtmp aren’t there.

Great! Now what about “whois” ? :slight_smile:

Cheers,
-RK

cheers,

Kris

“Robert Krten” <> nospam88@parse.com> > wrote in message
news:aedsd6$67$> 2@inn.qnx.com> …
Kris Warkentin <> kewarken@qnx.com> > wrote:
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but don’t
in
QNX6 but I’m also taking general utils feature requests.

who and whois would be nice > :slight_smile: > > :slight_smile:

So, if there are any utilities you wish you had or enhanced
functionality to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.


Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at > www.parse.com> .
Email my initials at parse dot com.

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.

26

One of our main goals over the next while is to get QNX support in the head
branch for binutils, gdb and gcc. We’ve already got x86 support for
binutils rolled in so it has begun. In house we have made some good
progress with gcc 3.x and gdb 5.2 so it’s just a matter of time. We
actually rolled a native ppc gdb for someone (was it you?) at one point so
it’s quite possible that native debugging could become a reality. Certainly
if our changes are applied to the public GNU source then people could roll
their own. It may not be completely desireable in the future though since
the Eclipse/qconn/pdebug combination is becoming the “Ultimate Debugging
Machine…dum dum dum…™” and just using gdb by itself may be too
limiting.

Note that the toolchain that we ship and any submissions to the GNU people
are completely unrelated. Getting our support in the public tree is to
benefit those who want to use the latest and greatest and also to avoid
future back-porting headaches. Obviously our shipped toolchain must undergo
intense scrutiny and the decision to move to a new version is not a trivial
one.

Thank you for your input Paul.

cheers,

Kris

“Paul D. Smith” <pausmith@nortelnetworks.com> wrote in message
news:p5ptytpces.fsf@lemming.engeast.baynetworks.com…

There’re lots of good utilities out there that would be useful at one
time or another, but the thing I want most is GDB.

By that I mean a real, full port of GDB 5.2 using all the new
facilities, not a hacked version with GDB 4.2-based QNX-specific
implementations of things GDB supports natively in 5.x. Preferably all
donated back to the GDB maintainers for automatic inclusion. Running
native rather than with/in addition to pdebug is highly desirable.


My development platforms are Solaris and Linux and my target platform is
PPC (and in the future SiByte), and I need a robust, reliable debugger
for these (I’m happy to build them myself, as long as they’re good).
QNX hosted environments and the ability to debug on Intel-based boxes
are of absolutely no consequence to me whatsoever. I’ve made the best
of what’s there (I have a 20-line shell script to start GDB) but I still
spend entirely too much time fighting with the debugger rather than
debugging. And I’ve been using GDB for well over 10 years: it’s not GDB
that’s the problem.


A close second on the list would be NIS client and NFS automount
capabilities… > :slight_smile:> .

–

Paul D. Smith <> pausmith@nortelnetworks.com> > HASMAT–HA Software Mthds &
Tools
“Please remain calm…I may be mad, but I am a professional.” --Mad
Scientist

These are my opinions—Nortel Networks takes no responsibility for
them.

27

Interesting. Do you think there would be enough benefit considering that
most Linux code seems to compile fairly nicely for Neutrino? I know that
there are some commercial apps that there is no source available for but it
seems to me that this would only bring a very small bit of functionality in.
Perhaps others disagree?

cheers,

Kris

“thomas hentschel” <nntp@hentschel.net> wrote in message
news:3D0A88AD.50005@hentschel.net…

Kris Warkentin wrote:
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
[snip]

How about lxrun (or a ABI like FreeBSD has) ?

-Th

28

Great list of suggestions. Comments below.
<camz@passageway.com> wrote in message news:aeeqh7$kho$1@inn.qnx.com…

Kris Warkentin <> kewarken@qnx.com> > wrote:
So, if there are any utilities you wish you had or enhanced
functionality to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.

You can add my vote for “sin fd” and “sin irq” to the list. I’d prefer to
see
all the functionality of qnx4’s sin appear in qnx6’s pidin. It is just
too
confusing to have pidin AND sin in qnx6, especially when neither of them
do all
the things we expect of them.

Noted.

ditto is pretty high up on the list. It’s essential for maintaining
remote QNX
servers (such as QNXZone), especially when updating).

Not sure who would be looking at this. I’ll check up on it.

sendmail needs to be ported, and the patches submitted back to the
authors. I
know this is somewhat in the 3rd party area, but EVERY unix OS ships
with a
working sendmail.

I believe this is on the third party CD. I don’t know if there will be any
movement of packages from that distribution to the main one. Probably if
there was enough demand…

A big one, which would involve changes at the API level as well as the
utility
level would be PAM. I’d also like to see the source for “login”,
“passwd”, and
“su” appear in the public CVS repository. Those utilities are “protected”
by
the requirement of needing root-privs to run, and the encryption that is
used.
Revealing their source does not create any security breach. If the source
for
those two utilities the user community would have been able to add support
for
thing like NIS/YellowPages, and PAM.
The PAM architechture is my main request though, since I beleive it would
allow
for the implementation of things like NIS/YellowPages as well even if QSSL
is
uncomfortable with releasing the source for the utilities I mentioned.
In a similiar vein, the source for phlogin would also be useful, there are
many
instances where a developer needs to customize a login environment.

These are things that will be considered because part of the activity over
the next while will involve deciding which utils to release source for. One
of the barriers to getting self hosted QNX6 accepted into corporate
environments is the ability to play nice with corporate infrastructure. I
imaging that NIS/YP would help that.

I would also like to see IBM’s MQ Series available as a runtime for QNX6.
I
know it’s out there, but damned if I can find it on their site.

Don’t know anything about this. I’ll look into it.

send/expect would also be useful for scripting.

If this isn’t on the third party CD, we could probably make sure that it is.
I think some of our testers use expect internally so it could be that it’s
already ported.

typescript is on my list as well, and would also be welcomed by QSSL’s
customers at the various educational institutions (univerisites and such
that
use Unix in their courses often require students to compile and run their
programs within a typescript session and the submit that file along with
their
assignment.

I’ve used the ‘script’ command for quite a while on QNX6. It seems to work
fine.

I can also give you a list of issues/features with fs-pkg, but that
belongs in
another thread.

If you’d like to start a thread, I’m sure someone will be listening. We’re
all working on our long and short term goals.

logical disk volume management would be nice too, so that you could
overlay
something like fs-lvm.so on top of existing fs layouts to “merge” multiple
disks into one large logical disk. HP-UX and AIX have excellent
implementations
of this sort of thing for you to examine.

Some things probably won’t make a roadmap simply because our emphasis is
really on the single developer targetting an embedded board rather than a
server OS. Stuff like LVM is definitely more useful on big iron.

I’m sure I’ll think of more over time, I’ll let you know as I think of
them.

Great. Keep them coming.

cheers,

Kris

29

“Robert Krten” <nospam88@parse.com> wrote in message
news:aegurp$5jj$1@inn.qnx.com…

Kris Warkentin <> kewarken@qnx.com> > wrote:
I’ve got “who” in our CVS tree. I also got a few things fixed up in
tinit
and telnetd (login was already good) to make sure that utmp and wtmp are
kept up to date properly. These are mostly just a matter of getting it
packed and shipped. The other thing would be to wire some utmp/wtmp
accounting into pterms and phlogin. That would be something for the
development roadmap.

Someone else (cdm maybe?) had written a who that figured it out by some
other mechanism but, since all the wtmp/utmp stuff is in place and is
the
standard unix way, it seemed best to do it this way. One thought: if
whoever has the non-utmp who would give me the code, I could wire it
into
who as a fallback if utmp/wtmp aren’t there.


Great! Now what about “whois” ? > :slight_smile:

I’ll have to talk to the networking guys about that one. Do you actually
use that very often?

Kris

Cheers,
-RK

cheers,

Kris

“Robert Krten” <> nospam88@parse.com> > wrote in message
news:aedsd6$67$> 2@inn.qnx.com> …
Kris Warkentin <> kewarken@qnx.com> > wrote:
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but
don’t
in
QNX6 but I’m also taking general utils feature requests.

who and whois would be nice > :slight_smile: > > :slight_smile:

So, if there are any utilities you wish you had or enhanced
functionality to
existing utilities, now is the time to let me know so I can try to
get
them
on the road map.


Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at > www.parse.com> .
Email my initials at parse dot com.


\

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

30

Noted. See my earlier reply to Paul Smith. I hope that the Eclipse
debugger will help you too. I find it a great improvement over plain old
gdb.

cheers,

Kris

“Kevin Stallard” <kevin@ffflyingrobots.com> wrote in message
news:aegcp5$nh1$1@inn.qnx.com…

I want to add my vote for a better GDB. I just had the most exhausting
day
debugging with the current GDB. I’m starting to see where it has
problems,
but I have never EVER taken so long debugging a system than today.
Something has got to be done about this thing. I don’t claim to be the
best
developer it the world, but Watcom’s debugger was MUCH better, even some
of
the older Borland stuff is better than this. This thing really hurt my
productivity today.

Kevin

“Kris Warkentin” <> kewarken@qnx.com> > wrote in message
news:aedho6$q6o$> 1@nntp.qnx.com> …
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but don’t
in
QNX6 but I’m also taking general utils feature requests.

So, if there are any utilities you wish you had or enhanced
functionality
to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.

cheers,

Kris
\

31

ditto is pretty high up on the list. It’s essential for maintaining
remote QNX
servers (such as QNXZone), especially when updating).

Yeah I dearly miss ditto. I know people who are waiting for ditto to switch
to QNX6.

32

Kris Warkentin <kewarken@qnx.com> wrote:

camz@passageway.com> > wrote in message news:aeeqh7$kho$> 1@inn.qnx.com> …

A big one, which would involve changes at the API level as well as the
utility level would be PAM. I’d also like to see the source for “login”,
“passwd”, and “su” appear in the public CVS repository. Those utilities
are “protected” by the requirement of needing root-privs to run,
and the encryption that is used.
Revealing their source does not create any security breach. If the source
for those two utilities the user community would have been able
to add support for thing like NIS/YellowPages, and PAM.
The PAM architechture is my main request though, since I beleive it would
allow
for the implementation of things like NIS/YellowPages as well even if QSSL
is
uncomfortable with releasing the source for the utilities I mentioned.
In a similiar vein, the source for phlogin would also be useful, there are
many
instances where a developer needs to customize a login environment.

These are things that will be considered because part of the activity over
the next while will involve deciding which utils to release source for. One
of the barriers to getting self hosted QNX6 accepted into corporate
environments is the ability to play nice with corporate infrastructure. I
imaging that NIS/YP would help that.

NIS support (and a more up-to-date librpc) is actually on my list.
A little bit low priority right now though.

-xtang

33

Kris Warkentin <kewarken@qnx.com> wrote:

“Robert Krten” <> nospam88@parse.com> > wrote in message
news:aegurp$5jj$> 1@inn.qnx.com> …
Kris Warkentin <> kewarken@qnx.com> > wrote:
I’ve got “who” in our CVS tree. I also got a few things fixed up in
tinit
and telnetd (login was already good) to make sure that utmp and wtmp are
kept up to date properly. These are mostly just a matter of getting it
packed and shipped. The other thing would be to wire some utmp/wtmp
accounting into pterms and phlogin. That would be something for the
development roadmap.

Someone else (cdm maybe?) had written a who that figured it out by some
other mechanism but, since all the wtmp/utmp stuff is in place and is
the
standard unix way, it seemed best to do it this way. One thought: if
whoever has the non-utmp who would give me the code, I could wire it
into
who as a fallback if utmp/wtmp aren’t there.


Great! Now what about “whois” ? > :slight_smile:

I’ll have to talk to the networking guys about that one. Do you actually
use that very often?

All the time. I’m an active spam-fighter, so when I get spam from an IP,
like 1.2.3.4, I can just type:

whois -hwhois.cyberabuse.org 1.2.3.4

And it comes up with the abuse@ email. QUITE handy :slight_smile:

Cheers,
-RK

Kris

Cheers,
-RK

cheers,

Kris

“Robert Krten” <> nospam88@parse.com> > wrote in message
news:aedsd6$67$> 2@inn.qnx.com> …
Kris Warkentin <> kewarken@qnx.com> > wrote:
Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but
don’t
in
QNX6 but I’m also taking general utils feature requests.

who and whois would be nice > :slight_smile: > > :slight_smile:

So, if there are any utilities you wish you had or enhanced
functionality to
existing utilities, now is the time to let me know so I can try to
get
them
on the road map.


Cheers,
-RK

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at > www.parse.com> .
Email my initials at parse dot com.


\

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

–
Robert Krten, PARSE Software Devices +1 613 599 8316.
Realtime Systems Architecture, Books, Video-based and Instructor-led
Training and Consulting at www.parse.com.
Email my initials at parse dot com.

34

Kris Warkentin wrote:

Attention QNX users.

I am compiling a wish-list for utilities development over the next 6 months
to a year. I’m mostly looking for things that existed in QNX4 but don’t in
QNX6 but I’m also taking general utils feature requests.

So, if there are any utilities you wish you had or enhanced functionality to
existing utilities, now is the time to let me know so I can try to get them
on the road map.

cheers,

Kris

install utility, script used by many Make scripts for the ‘make install’
stage.

/Johan

35

phearbear <phearbear@home.se> wrote:

install utility, script used by many Make scripts for the ‘make install’
stage.

it is part of XFree86, /opt/X11R6/bin/install

36

Frank Liu wrote:

phearbear <> phearbear@home.se> > wrote:

install utility, script used by many Make scripts for the ‘make install’
stage.


it is part of XFree86, /opt/X11R6/bin/install

Many non-X programs use this script too, and it should be includeded in

the base install imho

37

Was there any tool which shows
which resmgr is attaching to which /path/ ?

Especially when multiple resmgr is attaching to the same path
you can’t easily guess which resmgr is called first;
only procnto knows for sure.

(and digging through /proc/mount doesn’t seem the correct way)

kabe

38

%% “Kris Warkentin” <kewarken@qnx.com> writes:

nkw> We actually rolled a native ppc gdb for someone (was it you?) at
nkw> one point so it’s quite possible that native debugging could
nkw> become a reality.

Yes, it was us, but the binary we received wouldn’t even start; runtime
linker rejected it: incorrect C library I think we discovered it was.
We were using 6.1.0a at the time and I believe the binary must have been
compiled against the 6.2 prerelease tree or something.

Native debugging will be nice and now that 6.2 is out we’ll try harder
to get it. But mainly I’m interested in getting the new stuff in GDB
5.x available, and getting shared library debugging to work in some sort
of sane fashion on QNX.

nkw> Certainly if our changes are applied to the public GNU source
nkw> then people could roll their own. It may not be completely
nkw> desireable in the future though since the Eclipse/qconn/pdebug
nkw> combination is becoming the “Ultimate Debugging Machine…dum dum
nkw> dum…™” and just using gdb by itself may be too limiting.

I’m not interested in running Eclipse, until/unless you support it on
Linux. And maybe not even then. I don’t have any Windows or Intel/QNX
systems (or SCM toolset is ClearCase so we’ll never move to hosted
QNX–until and unless ClearCase supports it–and maybe not even then :slight_smile:).
And, bulky Java/GUI toolkits like this just run like crap on
Solaris/SPARC, in my experience.

I’ve been using Emacs with GDB et.al. as my IDE for over 14 years and
I’m perfectly happy with that… when it works right :slight_smile:.

nkw> Note that the toolchain that we ship and any submissions to the
nkw> GNU people are completely unrelated. Getting our support in the
nkw> public tree is to benefit those who want to use the latest and
nkw> greatest and also to avoid future back-porting headaches.
nkw> Obviously our shipped toolchain must undergo intense scrutiny and
nkw> the decision to move to a new version is not a trivial one.

Ditto for us: once we get to a stable point we’ll almost certainly stick
with whatever compiler it’s using for quite a while. Just for starters,
we always build with -Werror and any new version of compiler entails
bunches of work fixing the new set of warnings :slight_smile:. Plus, obviously,
complete regression testing to be sure the compiler didn’t invent any
new bugs. The same, of course, for QNX itself.


Thanks for the reply, Kris…

–

Paul D. Smith <pausmith@nortelnetworks.com> HASMAT–HA Software Mthds & Tools
“Please remain calm…I may be mad, but I am a professional.” --Mad Scientist

These are my opinions—Nortel Networks takes no responsibility for them.

39

Kris Warkentin <kewarken@qnx.com> wrote:

Attention QNX users.

I am compiling a wish-list for utilities development over the next 6 months
to a year. I’m mostly looking for things that existed in QNX4 but don’t in
QNX6 but I’m also taking general utils feature requests.

So, if there are any utilities you wish you had or enhanced functionality to
existing utilities, now is the time to let me know so I can try to get them
on the road map.

cheers,

Kris

my proposal: vedit or vp

40

Ok Kris

What about
tinit -c "modem " -t /dev/serx etc

Use to work great on 4.25 a real pain on 6.x. Can I assume that you were
expecting everyone to use pppd/chat for remote modem connection.

Rod


“Kris Warkentin” <kewarken@qnx.com> wrote in message
news:aedho6$q6o$1@nntp.qnx.com…

Attention QNX users.

I am compiling a wish-list for utilities development over the next 6
months
to a year. I’m mostly looking for things that existed in QNX4 but don’t
in
QNX6 but I’m also taking general utils feature requests.

So, if there are any utilities you wish you had or enhanced functionality
to
existing utilities, now is the time to let me know so I can try to get
them
on the road map.

cheers,

Kris