The Future of QUICS newsgroups

[Debbie_Kane]

As the QDN newsgroups have had significant activity over the last few
months, we feel it is time to make the move and archive the QUICS
conferences, which will continue to be available as a reference. As of the
end of this week, we will no longer be monitoring the QUICS conferences.
(We will continue to provide access to quics.private.* and quics.beta.*)

QNX developers will enjoy unlimited read/write access to all public QNX
newsgroups, using standard newsreaders, TIN, TRN, or Vmail. To access the
following newsgroups directly, simply go to news://inn.qnx.com.

qdn.public.qnx2
qdn.public.neutrino
qdn.public.qnx4
qdn.public.photon
qdn.public.porting
qdn.public.news
qdn.public.qnxjobs
qdn.public.qnxrealtimeplatform.beta

We will, of course, continue support for ongoing threads in QUICS, but new
postings shouldl be directed to the QDN.

For comments, please post in qdn.public.news

Debbie Kane
Manager, Technical Support

[Sam_Roberts]

So all of quics.experts.* have been replaced by qdn.public.qnx4/photon/news,
and all but photon questions should be posted to the qnx4 group?

Sam

Previously, Debbie Kane wrote in qdn.public.news:

As the QDN newsgroups have had significant activity over the last few
months, we feel it is time to make the move and archive the QUICS
conferences, which will continue to be available as a reference. As of the
end of this week, we will no longer be monitoring the QUICS conferences.
(We will continue to provide access to quics.private.* and quics.beta.*)

QNX developers will enjoy unlimited read/write access to all public QNX
newsgroups, using standard newsreaders, TIN, TRN, or Vmail. To access the
following newsgroups directly, simply go to news://inn.qnx.com.

qdn.public.qnx2
qdn.public.neutrino
qdn.public.qnx4
qdn.public.photon
qdn.public.porting
qdn.public.news
qdn.public.qnxjobs
qdn.public.qnxrealtimeplatform.beta

We will, of course, continue support for ongoing threads in QUICS, but new
postings shouldl be directed to the QDN.

For comments, please post in qdn.public.news

Debbie Kane
Manager, Technical Support



\

–
Sam Roberts (sam@cogent.ca), Cogent Real-Time Systems (www.cogent.ca)

[Igor_Kovalenko2]

How do you plan to support corporate customers, most of which are behind firewalls? I can’t access any NNTP servers outside of Motorola from my work. The QUICS newsgroups have advantage that we could read them using tin in a telnet session (most companies allow telnet & ftp access in one way or another).

I tried to use tin on QUICS to read qdn.x.x groups, but since /etc/nntpserver is unwritable for me and my embedded-too-restricted-almost-shell does not recognize environment variables in command line and does no allow to export them, I can’t use tin on QUICS to access any NNTP servers.

You could of course change /etc/nntpserver to point to inn.qnx.com, but then how do we access private and beta groups from news.qnx.com?

The bottom line, you need some kind of two-way news-mail gateway. Then there could be a mailing list dubbing every qdn group. Otherwise you could create comp.os.qnx.xxx groups.

• igor

Previously, Debbie Kane wrote in qdn.public.news:

As the QDN newsgroups have had significant activity over the last few
months, we feel it is time to make the move and archive the QUICS
conferences, which will continue to be available as a reference. As of the
end of this week, we will no longer be monitoring the QUICS conferences.
(We will continue to provide access to quics.private.* and quics.beta.*)

QNX developers will enjoy unlimited read/write access to all public QNX
newsgroups, using standard newsreaders, TIN, TRN, or Vmail. To access the
following newsgroups directly, simply go to news://inn.qnx.com.

qdn.public.qnx2
qdn.public.neutrino
qdn.public.qnx4
qdn.public.photon
qdn.public.porting
qdn.public.news
qdn.public.qnxjobs
qdn.public.qnxrealtimeplatform.beta

We will, of course, continue support for ongoing threads in QUICS, but new
postings shouldl be directed to the QDN.

For comments, please post in qdn.public.news

Debbie Kane
Manager, Technical Support


\

[Colin_Burgess1]

Igor Kovalenko <kovalenko@home.com> wrote:

How do you plan to support corporate customers, most of which are behind firewalls? I can’t access any NNTP servers outside of Motorola from my work. The QUICS newsgroups have advantage that we could read them using tin in a telnet session (most companies allow telnet & ftp access in one way or another).

I tried to use tin on QUICS to read qdn.x.x groups, but since /etc/nntpserver is unwritable for me and my embedded-too-restricted-almost-shell does not recognize environment variables in command line and does no allow to export them, I can’t use tin on QUICS to access any NNTP servers.

You could of course change /etc/nntpserver to point to inn.qnx.com, but then how do we access private and beta groups from news.qnx.com?

The bottom line, you need some kind of two-way news-mail gateway. Then there could be a mailing list dubbing every qdn group. Otherwise you could create comp.os.qnx.xxx groups.

• igor

Wow, this is the first time that I’ve seen someone actually prefer
telnet/tin over an external NNTP reader! ;v)

–
cburgess@qnx.com

[Brown_Richard]

Is there any plans to move private and beta over with user authentication?
It is a bit of a pain to have to switch to and fro.

• Richard

Debbie Kane <debbie@qnx.com> wrote in article
<8nula0$nrp$1@nntp.qnx.com>…

(We will continue to provide access to quics.private.* and quics.beta.*)
Debbie Kane
Manager, Technical Support


\

[system]

Igor Kovalenko <kovalenko@home.com> wrote:

How do you plan to support corporate customers, most of which are behind
firewalls? I can’t access any NNTP servers outside of Motorola from my
work. The QUICS newsgroups have advantage that we could read them using
tin in a telnet session (most companies allow telnet & ftp access in one
way or another).

I guess we are push these types of issues into your court… I’m sure if you
speak with your friendly neighbourhood IT guys, they could open up 119 to
inn.qnx.com The whole idea here is to make this service more flexible to
the masses… and it was decided that NNTP was the way to go.

You could always telnet to the box you posted this message from and read/post
at inn.qnx.com

I tried to use tin on QUICS to read qdn.x.x groups, but since
/etc/nntpserver is unwritable for me and my
embedded-too-restricted-almost-shell does not recognize environment
variables in command line and does no allow to export them, I can’t
use tin on QUICS to access any NNTP servers.

That is correct. This will NOT be available. The tin you are running at
quics.qnx.com is a hacked up version… that is very limited. Not to mention
the very restricted shell account that you are using it in…

You could of course change /etc/nntpserver to point to inn.qnx.com, but
then how do we access private and beta groups from news.qnx.com?

The bottom line, you need some kind of two-way news-mail gateway. Then
there could be a mailing list dubbing every qdn group.

I doubt that this will happen… as we are moving away from our proprietary
conferencing service… this would just prolong the life of QUICS and debbie
has been telling everyone for months that the traditional QUICS service model
is being replaced by QDN (http://support.qnx.com & news://inn.qnx.com)

Otherwise you could create comp.os.qnx.xxx groups.

–
Joe Bishop (joe@qnx.com)

[Debbie_Kane]

“Brown, Richard” <brownr@aecl.ca> wrote in message
news:01c00cf0$496516e0$b5a7e184@spw1296…

Is there any plans to move private and beta over with user authentication?
It is a bit of a pain to have to switch to and fro.

• Richard

Yes, this is the plan, but we aren’t ready yet.

[Igor_Kovalenko2]

Previously, joe@qnx.com wrote in qdn.public.news, quics.info:

Igor Kovalenko <> kovalenko@home.com> > wrote:
How do you plan to support corporate customers, most of which are behind
firewalls? I can’t access any NNTP servers outside of Motorola from my
work. The QUICS newsgroups have advantage that we could read them using
tin in a telnet session (most companies allow telnet & ftp access in one
way or another).


I guess we are push these types of issues into your court… I’m sure if you
speak with your friendly neighbourhood IT guys, they could open up 119 to
inn.qnx.com >

However friendly they are, “that is not an option” was the answer.

The whole idea here is to make this service more flexible to

the masses… and it was decided that NNTP was the way to go.

You could always telnet to the box you posted this message from and read/post
at inn.qnx.com >

Yes, but that requires one to have box with account and good connection running somewhere outside. The one I’m posting from is my home box and I’ll have to let it run NTO non-stop to do that, which will undoubtedly interfere with my children who want to play games while I’m at work !

I doubt that this will happen… as we are moving away from our proprietary
conferencing service… this would just prolong the life of QUICS and debbie
has been telling everyone for months that the traditional QUICS service model
is being replaced by QDN (> http://support.qnx.com > & news://inn.qnx.com)

Whatever you do, if you make life of corporate customers harder than it should be, you’re looking for long term financial problems. I bet not everyone will be persistent enough to work around the problem of getting to technical support channel.

• Igor

[Bill_at_Sierra_Desig]

Colin Burgess <cburgess@qnx.com> wrote in message
news:8o09ns$mta$1@nntp.qnx.com…

Igor Kovalenko <> kovalenko@home.com> > wrote:
How do you plan to support corporate customers, most of which are behind
firewalls? I can’t access any NNTP servers outside of Motorola from my work.

The QUICS newsgroups have advantage that we could read them using tin in a
telnet session (most companies allow telnet & ftp access in one way or
another).

Wow, this is the first time that I’ve seen someone actually prefer
telnet/tin over an external NNTP reader! ;v)

–
cburgess@qnx.com

No it’s not!

Read all of the complaints in Quics about doing away with Quics.

[system]

Debbie Kane <debbie@qnx.com> wrote:

As the QDN newsgroups have had significant activity over the last few
months, we feel it is time to make the move and archive the QUICS
conferences, which will continue to be available as a reference. As of the
end of this week, we will no longer be monitoring the QUICS conferences.
(We will continue to provide access to quics.private.* and quics.beta.*)

Sorry if this has already been answered, but what’s QUICS?

Can I get a copy?

[Sam_Roberts]

ping.

Previously, Sam Roberts wrote in qdn.public.news:

So all of quics.experts.* have been replaced by qdn.public.qnx4/photon/news,
and all but photon questions should be posted to the qnx4 group?

Sam

Previously, Debbie Kane wrote in qdn.public.news:
As the QDN newsgroups have had significant activity over the last few
months, we feel it is time to make the move and archive the QUICS
conferences, which will continue to be available as a reference. As of the
end of this week, we will no longer be monitoring the QUICS conferences.
(We will continue to provide access to quics.private.* and quics.beta.*)

QNX developers will enjoy unlimited read/write access to all public QNX
newsgroups, using standard newsreaders, TIN, TRN, or Vmail. To access the
following newsgroups directly, simply go to news://inn.qnx.com.

qdn.public.qnx2
qdn.public.neutrino
qdn.public.qnx4
qdn.public.photon
qdn.public.porting
qdn.public.news
qdn.public.qnxjobs
qdn.public.qnxrealtimeplatform.beta

We will, of course, continue support for ongoing threads in QUICS, but new
postings shouldl be directed to the QDN.

For comments, please post in qdn.public.news

Debbie Kane
Manager, Technical Support






\

Sam Roberts (> sam@cogent.ca> ), Cogent Real-Time Systems (> www.cogent.ca> )

–
Sam Roberts (sam@cogent.ca), Cogent Real-Time Systems (www.cogent.ca)

[Debbie_Kane]

“Sam Roberts” <sam@cogent.ca> wrote in message
news:Voyager.000822171044.7664A@sam.cogent.ca…

So all of quics.experts.* have been replaced by
qdn.public.qnx4/photon/news,
and all but photon questions should be posted to the qnx4 group?

Sam

yes

[Igor_Kovalenko2]

Bill at Sierra Design <BC@SierraDesign.com> wrote in message
news:8o1hq8$ima$1@inn.qnx.com…

Colin Burgess <> cburgess@qnx.com> > wrote in message
news:8o09ns$mta$> 1@nntp.qnx.com> …
Igor Kovalenko <> kovalenko@home.com> > wrote:
How do you plan to support corporate customers, most of which are
behind
firewalls? I can’t access any NNTP servers outside of Motorola from my
work.
The QUICS newsgroups have advantage that we could read them using tin in a
telnet session (most companies allow telnet & ftp access in one way or
another).


Wow, this is the first time that I’ve seen someone actually prefer
telnet/tin over an external NNTP reader! ;v)

–
cburgess@qnx.com

No it’s not!

Read all of the complaints in Quics about doing away with Quics.

Not that I likeed it, just had no choice
Well, I’m posting from Motorola now, finally got SOCKS working…

• igor

[system]

Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:

Not that I likeed it, just had no choice >
Well, I’m posting from Motorola now, finally got SOCKS working…

Well that’s good to hear, welcome to the 90’s

–
Joe Bishop (joe@qnx.com)

[Igor_Kovalenko2]

Hey it’s not 90’s anymore

joe@qnx.com wrote:

Igor Kovalenko <> Igor.Kovalenko@motorola.com> > wrote:
Not that I likeed it, just had no choice >
Well, I’m posting from Motorola now, finally got SOCKS working…

Well that’s good to hear, welcome to the 90’s >

–
Joe Bishop (> joe@qnx.com> )

[Debbie_Kane]

“Norton Allen” <allen@huarp.harvard.edu> wrote in message
news:39AE7ED4.F1ACFFDD@huarp.harvard.edu…

Why was the higher granularity abandoned? I found it very
useful when I didn’t have too much free time to just check
a couple conferences in which I was active to see if I needed
to reply to anything. Now with everything mixed in, it takes
much more effort to figure out what is relevant.

I think with QUICS, the granularity was too fine, so these are the groups we
are starting out with.
Do you have any suggestions for QNX4 breakdown?

[Norton_Allen2]

Debbie Kane wrote:

“Sam Roberts” <> sam@cogent.ca> > wrote in message
news:> Voyager.000822171044.7664A@sam.cogent.ca> …

So all of quics.experts.* have been replaced by
qdn.public.qnx4/photon/news,
and all but photon questions should be posted to the qnx4 group?

Sam

yes

Why was the higher granularity abandoned? I found it very
useful when I didn’t have too much free time to just check
a couple conferences in which I was active to see if I needed
to reply to anything. Now with everything mixed in, it takes
much more effort to figure out what is relevant.

[Bill_at_Sierra_Desig]

Funny! I though it could have been broken down even more. I think a great
conference would have been for SHELL questions.

Count me in for better (increased) “granularity” (more specific
conferences).

At a very minimum, each program product should have it’s own conference.


Debbie Kane <debbie@qnx.com> wrote in message
news:8olv9j$a5j$1@nntp.qnx.com…

“Norton Allen” <> allen@huarp.harvard.edu> > wrote in message
news:> 39AE7ED4.F1ACFFDD@huarp.harvard.edu> …


Why was the higher granularity abandoned? I found it very
useful when I didn’t have too much free time to just check
a couple conferences in which I was active to see if I needed
to reply to anything. Now with everything mixed in, it takes
much more effort to figure out what is relevant.

I think with QUICS, the granularity was too fine, so these are the groups
we
are starting out with.
Do you have any suggestions for QNX4 breakdown?

[Stephen_Thomas]

Debbie Kane <debbie@qnx.com> wrote in message
news:8olv9j$a5j$1@nntp.qnx.com…

“Norton Allen” <> allen@huarp.harvard.edu> > wrote in message
news:> 39AE7ED4.F1ACFFDD@huarp.harvard.edu> …


Why was the higher granularity abandoned? I found it very
useful when I didn’t have too much free time to just check
a couple conferences in which I was active to see if I needed
to reply to anything. Now with everything mixed in, it takes
much more effort to figure out what is relevant.

I think with QUICS, the granularity was too fine, so these are the groups
we
are starting out with.
Do you have any suggestions for QNX4 breakdown?

Yes, I see a need for at least the following:
qdn.public.qnx4.net
qdn.public.qnx4.fsys
qdn.public.qnx4.migration (to NTO)

Most of these look familiar, no doubt.
This would also make it easier on QSSL developer to quickly find and answer
questions in their area. Also, perhaps qdn.public.photon should be replaced
with two groups specific to photon on QNX4 or NTO?

[Sam_Roberts]

Previously, Stephen Thomas wrote in qdn.public.news:

Debbie Kane <> debbie@qnx.com> > wrote in message
news:8olv9j$a5j$> 1@nntp.qnx.com> …
Do you have any suggestions for QNX4 breakdown?

Yes, I see a need for at least the following:
qdn.public.qnx4.net
qdn.public.qnx4.fsys
qdn.public.qnx4.migration (to NTO)

Or maybe break configuration/setup questions out from
development?

rtp.setup
rtp.devel

Sam

–
Sam Roberts, sroberts at uniserve dot com, www.emyr.net/Sam