sfk1 at bigfoot.com
Sat Jun 28 08:07:35 PDT 2003
* Jeroen Coumans <jeroencoumans at gmx.net> wrote:
>> root at canberra:~# ls /var/spool/news/
>> blfs dormant.groups faq interesting.groups lfs out.going
>> de failed.postings in.coming leaf.node message.id temp.files
>> You see the top level hierarchies blfs, de, lfs and *faq*. I also use
>> another news server, news.cis.dfn.de. What if cis.dfn.de decides to
>> create a top level hierarchy named faq? (Yes, I know they won't, but
>> why should LFS use top level hierarchies so lavishly?)
>> One should keep in mind that LFS is not only the LFS project, but also
>> the abbreviation for linuxfromscratch[.org]. The top level hierarchy
>> lfs.* refers to the domain as well as to the project. It would even make
>> sense to drop blfs.* and create groups like lfs.blfs.support. (But I
>> don't really suggest that, just making a point.)
> It's a good point. In my defense, I don't know much about the newsgroups
> since I don't use them.
> Just some thoughts here. Isn't there an option in your newsreader to
> display newsgroups based on servers? I assume that your /var/spool/news
> isn't what you use for reading, right? And certainly you can arrange
> that *.linuxfromscratch.org goes under
> /var/spool/news/www.linuxfromscratch.org, like it's intended? Otherwise,
I run a leafnode, a local news server. /var/spool/news is under leafnode's
control and if I poll a news server which propagates a top level hierarchy
"faq" then leafnode duly creates one.
> how would conflicts be resolved if you subscribe to, say
> bugs at mozilla.org and bugs at gnome.org? They wouldn't both be called
> "bugs", right?
No, that's why the top level hierarchies have different names,
mozilla.bugs and gnome.bugs would be the way to go.
> Also, your complaint applies to the hints too (so there's a precedent
> for faq@ and website@).
stefan:~> telnet linuxfromscratch.org 119
Connected to linuxfromscratch.org.
Escape character is '^]'.
200 belgarath.linuxfromscratch.org InterNetNews NNRP server INN 2.3.5 ready
lfs.test 0000000495 0000000460 y
lfs.dev 0000014404 0000012697 y
lfs.support 0000017095 0000015640 y
alfs.discuss 0000001610 0000001498 y
blfs.support 0000029493 0000026945 y
lfs.traducfr 0000001274 0000001210 y
lfs.security 0000000493 0000000465 y
lfs.hints 0000001523 0000001380 y
You see: test-list <--> lfs.test; hints <--> lfs.hints
No need to change the names of the mailing lists.
Followups should probably go to lfs-chat, too much OT content.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev