QNX Public Newsgroups

[Newsgroup Admin]

As a member of the QNX Community, we would like to inform you about some
upcoming changes to the QNX Public Newsgroups.

As a result of the launch of the new QNX Website mid-month, the QNX Public
Newsgroups will be streamlined to create a better framework for sharing,
managing and accessing information. Here's a sneak peak at the list of new
newsgroups that will be created at <news://inn.qnx.com/>:


qnx.newuser - Installation, configuration and administration of the QNX
Neutrino or QNX Momentics environments

qnx.rtos - Writing resources managers, and general discussion around
the QNX Neutrino RTOS

qnx.gui - Creating graphical applications within a GUI environment, such
as Photon or PhAB

qnx.development_tools - Self-hosted graphical development with the
Eclipse IDE and cross-hosted development on Solaris, Linux, or Windows

qnx.ddk - Writing device drivers for scanners, video card, optical
mouse, etc

qnx.porting - Discuss migrating applications from QNX4, VxWorks, PSOS,
or Linux to QNX Neutrino

qnx.bsp - Discuss building an image, flashing a board or using a BSP

qnx.qnx4 - General QNX4 Discussion Group

qnx.3rdparty_product_announcements

Existing qdn.public newsgroups will be deprecated before the end of 2003.
However, for your convenience, these newsgroups will still be available
in a read-only archive.

If you have any questions, send email to newsgroup_admin@qnx.com

[Guest]

Proposal: a newsgroup to post patches, sample codes and sources;
could be
qnx.sources
qnx.porting.sources (for ported codes only?)
whatever.
--
kabe

[Frank Liu]

kabe@sra-tohoku.co.jp wrote:

Proposal: a newsgroup to post patches, sample codes and sources;
could be
qnx.sources
qnx.porting.sources (for ported codes only?)
whatever.

maybe call it qnx.binaries where you can post anything with
a binary attachment. (uuencoded or whatever). then, QSS can
filter out binaries in other groups (inn can do that).
I've seen people posting MP3's in the qdn.cafe in the past,
they should be redirected to "this" binary group then

[Bill Caroselli]

kabe@sra-tohoku.co.jp wrote:
kstcj > Proposal: a newsgroup to post patches, sample codes and sources;
kstcj > could be
kstcj > qnx.sources
kstcj > qnx.porting.sources (for ported codes only?)
kstcj > whatever.
kstcj > --
kstcj > kabe

I would like to recomend a qnx.networking for TCP/IP and QNET issues.

In fact, if it were up to me, I would have the groups be as specific as
possible. Although I would have made some of them sub-groups such
as you did with the qdn.ddk.* groups. For instance, all of the BSP
groups.

And I never really understood why there were the duplication of groups
like:
qdn.public.devtools and qdn.public.qnxrtp.devtools
and
qdn.public.installation and qdn.public.qnxrtp.installation.

[Bill Caroselli]

One more thought. Can you add the groups descriptions (in addition to
the names) for the new groups.


Bill Caroselli <qtps@earthlink.net> wrote:
BC > I would like to recomend a qnx.networking for TCP/IP and QNET issues.

BC > In fact, if it were up to me, I would have the groups be as specific as
BC > possible. Although I would have made some of them sub-groups such
BC > as you did with the qdn.ddk.* groups. For instance, all of the BSP
BC > groups.

BC > And I never really understood why there were the duplication of groups
BC > like:
BC > qdn.public.devtools and qdn.public.qnxrtp.devtools
BC > and
BC > qdn.public.installation and qdn.public.qnxrtp.installation.

[Guest]

qtps@earthlink.net sed in <bsc56m$ojm$1@inn.qnx.com>:

qdn.public.devtools and qdn.public.qnxrtp.devtools
and
qdn.public.installation and qdn.public.qnxrtp.installation.

<URL:news:bcat5h$j91$2@nntp.qnx.com>
<URL:nntp://inn.qnx.com/qdn.public.installation/450>

Summary: QSSL tried to ditch *.qnxrtp.* when 6.2 (Momentics) came out,
but couldn't as usage level was high.

The "official" newsgroups could be the non- *.qnxrtp.* groups
as mentioned in <URL:http://www.qnx.com/support/sd_newsgroups.html>.
But the fact seems to be the advanced users still is actively
using *.qnxrtp.* .


From: David Gibbs <dagibbs@qnx.com>
Newsgroups: qdn.public.installation
Subject: Re: devn-rtl driver fails with "unable to mmap_device_memory"
Date: 12 Jun 2003 22:00:17 GMT
Message-ID: <bcat5h$j91$2@nntp.qnx.com>
Xref: inn.qnx.com qdn.public.installation:450

[snip]

Well, "qnxrtp" stood for 'QNX Real Time Platform', and we're
not marketing anything under that name anymore. (Much of
what was RTP is now QNX Momentics Non Commercial Edition.)

qdn.public.installation was created to replace the .qnxrtp.
version, and .qnxrtp. version was disabled (closed). In fact
all the "deprecated" .qnxrtp. newsgroups were deprecated and
closed -- but they were being used, so that closure was reversed,
and now we have some overlapping groups.

Though, the .qnxrtp.installation would tend to be primarily
self-hosted install issues, while the other could also cover
Windows and Solaris hosted install issues.

More than you need to know...

-David

[Guest]

newsgroup_admin@qnx.com sed in <br4gac$sp4$1@inn.qnx.com>:

qnx.newuser - Installation, configuration and administration of the QNX
Neutrino or QNX Momentics environments

qnx.rtos - Writing resources managers, and general discussion around
the QNX Neutrino RTOS
[snip]

Can you install these descriptions as the "charter", just like
the existing groups?
(I forgot what file it was in INN; the info itself is retrievable
from NNTP "list newsgroups")
--
kabe