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.
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 ".
One of the things I will sorely miss (haven’t yet, since I’m not doing a
lot of tcpip on QNX6 yet) is the ability to do the following for a tcpip
server app:
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.
This is not something that was present in QNX4, but something I have been
wanting for a long time.
The enhancement would be to add filesystem check to diskboot for QNX4
filesystems. It could be as simple as a flag you add to diskboot, so disk
boot would automatically check the “dirty” flag on a file system before
mounting it.
So for instance if the system didn’t get powered down in a correct manner it
would be checked and repaired automatically before being mounted.
This is similar to what Windows does, which will do a repair on your drive
if it didn’t get powered down correctly.
I know it is possible to do above today but it is real pain, because you
have to create a special boot image where the start up of devb-eide is done
manually. The other option which seems to be suggested sometimes, with
calling chkfsys in one of the startup scripts is not recommended.
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.
If you have multiple partions with a valid QNX installation (.diskboot in
the root) the QNX boot manager comes out and ask which partion to use as
root partition. I would actually prefer if the QNX boot manager (or certain
version of the boot manager) would simply use the partion which is marked as
the active boot partion as the root partion, and not offer up the choice to
the user.
The reason: in a multi partion setup an expect user can control which
partion to boot from and the novice user is not posed with the partion
selection question every time the system is booted.
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.
My wish is that you would fix QNet to be as good as the QNX4 native
networking -
Make it reliable. At present there are too many errors and loss of
service.
Make it work over a serial link WITHOUT having to use TCP/IP and PPP as
well.
Make the ndp reliable and predictable and make it work over any type of
link. At present it does not work at all over a serial link.
Come up with a name location scheme (or similar) that is as good as, or
better than nameloc so that it is technically possible to configure a
logical system without regard for the physical network it runs on.
This is just an outline - if you want me to go into more detail just ask…
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.
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’. (except for spin of course, thanks Igor That’s
something I’ve been wanting to do for a while, since having so many system
information code bases is burdensome. I’ll be sure to add that to the list.
Kris
One of the things I will sorely miss (haven’t yet, since I’m not doing a
lot of tcpip on QNX6 yet) is the ability to do the following for a tcpip
server app:
Thank you for the suggestions. The list I’m compiling is strictly for
utilities (which I’m responsible for) but any other suggestions are much
appreciated. If they aren’t watching this thread already, I’ll be sure to
make sure the right people get them.
My wish is that you would fix QNet to be as good as the QNX4 native
networking -
Make it reliable. At present there are too many errors and loss of
service.
Make it work over a serial link WITHOUT having to use TCP/IP and PPP as
well.
Make the ndp reliable and predictable and make it work over any type of
link. At present it does not work at all over a serial link.
Come up with a name location scheme (or similar) that is as good as, or
better than nameloc so that it is technically possible to configure a
logical system without regard for the physical network it runs on.
This is just an outline - if you want me to go into more detail just
ask…
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.
This is not something that was present in QNX4, but something I have been
wanting for a long time.
The enhancement would be to add filesystem check to diskboot for QNX4
filesystems. It could be as simple as a flag you add to diskboot, so disk
boot would automatically check the “dirty” flag on a file system before
mounting it.
So for instance if the system didn’t get powered down in a correct manner
it
would be checked and repaired automatically before being mounted.
This is similar to what Windows does, which will do a repair on your drive
if it didn’t get powered down correctly.
I know it is possible to do above today but it is real pain, because you
have to create a special boot image where the start up of devb-eide is
done
manually. The other option which seems to be suggested sometimes, with
calling chkfsys in one of the startup scripts is not recommended.
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.
Make it reliable. At present there are too many errors and loss of
service.
Make it work over a serial link WITHOUT having to use TCP/IP and PPP as
well.
Jim,
Xiadong Tang (I hope I spelled his name right, xtang is much easier )
has already done this…in fact all he has to do is comiple qnet with a flag
and it turns it on. I’ve had some lengthy discussions with him about it as
I want it as well. Hopefully someone will hear this, turn this feature on
and give us a .so
Be nice to use a serial cable as a bridge between two qnet networks (radio
modem bridge that is) w/o tcp/ip
Kevin
Make the ndp reliable and predictable and make it work over any type of
link. At present it does not work at all over a serial link.
Come up with a name location scheme (or similar) that is as good as, or
better than nameloc so that it is technically possible to configure a
logical system without regard for the physical network it runs on.
This is just an outline - if you want me to go into more detail just
ask…
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.
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.
I don’t care if these are in sin, or pidin, I just want the info.
(And, these may take kernel work.):
sin rt // list of timers on system and what they’ll fire
sin ir // already mentioned, list of registered irq handlers
prefix // list the pathnames registered with Proc and who owns them
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
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.
My wish is that you would fix QNet to be as good as the QNX4 native
networking -
Make it reliable. At present there are too many errors and loss of
service.
Can you try the 6.2 QNET and give me an example of the error case
of “loss of service” ? I am more interested in relibility now.
Make it work over a serial link WITHOUT having to use TCP/IP and PPP as
well.
This could be done by have QNET fake up ip address, arp, gateways.
Like others posted. I have all the codes in place, just need to
switch them in.
Make the ndp reliable and predictable and make it work over any type of
link. At present it does not work at all over a serial link.
Come up with a name location scheme (or similar) that is as good as, or
better than nameloc so that it is technically possible to configure a
logical system without regard for the physical network it runs on.
NDP by defination is not a “reliable” protocol. But 3 and 4 actually
could be solved by a (nameloc like) master/slave database mode.
This is on the todo list, but I have no idea when it could be done.
This is just an outline - if you want me to go into more detail just ask…
Well, at least I am intereted. Maybe we should open another thread
to discuss this.
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.
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… .
–
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.
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.