OK, so I have signed up to the linux-kernel mailing list, after reading and re-reading the various brief and out-dated FAQs and DOs and DON'Ts of the list.

I have sent the prerequesite 'help' email to vger, and also sent a couple test emails to autoreply@vger.kernel.org intended to verify that MX traffic can successfully get from vger to me.

I sort of got a reply to both emails after about 24-36 hours: but both emails were empty (to be suspected I guess with the MX test, but not the help message!?) so all I know at this point is that traffic can indeed get from me <--> vger.

Can someone give me (and anyone else interested) a couple tips on interacting with the mailing list?

For example, I'd like to contribute info about a regression from 2.6.28.7 --> 2.6.29, and I have searched the list/archives to see if anyone has pointed it out yet, and I don't see anything yet. So, what do I do *if* I want to start a thread or comment on an existing thread? Do I wait till I get a daily digest (or full daily update) and then reply to that email? Or what?

Tips welcome

Thanks,
Sasha

I think the recommended practice with any mailing list is to "lurk" for awhile to become familiar with the "society." On the other hand, if you lurk too long your information my be irrelevant. I'd look at http://kernel.org/pub/linux/docs/lkml/#s3 and specifically http://kernel.org/pub/linux/docs/lkml/#s3-12 before posting. Be humble, but if you really think you found something that no one else has found, then post it.

Did you follow the steps outlined in this guide;
http://www.kernel.org/pub/linux/docs...ting-bugs.html

Been a while since I signed up, but if you were successful you'd know about it. The traffic is horrendous - I usually stay off-list unless I have a need.

You will need:
- a good threading mail client
- a (really) thick skin
- an alpha male personality

It ain't your average mail-list.

Thanks to all who responded;

It seems my subscription did not succeed, and though I have tried again, I am not getting the Majordomo 'help' message reply either. I DO get a reply from Majordomo, but there's no content, no help. Weird.. (I have been on Majordomo mailing lists before, but not any Linux ones, and IIRC there was a comprehensive HELP email sent by the server on request.. Not here though.)

As suggested above, YES I have read the page about 'reporting bugs in the kernel' and much of it doesn't apply in this case; as well, I cannot find the driver or a maintainer in the MAINTAINERS file, and Google hasn't been helpful either.

I have also thoroughly reviewed the docs as indicated in the link above provided by weibulguy, and am confident I can provide a useful, brief, list-compliant email to the list, and duck any '@-the-newbie' flack that comes of it if 'they' don't like it lol..

Well, for the time being (next 24-48 hours) I'll continue to lurk unsubscribed...


UPDATE/EDIT:

I have found in the maintainers file a reference to the 'net-dev' mailing list, which appears to be a better place to post my situation (the driver in question is forcedeth.c for nvidia NICs) so for the moment I will just lurk around linux-kernel, but will put together a report and send it to net-dev. It looks as though much of what is on the net-dev list is CC'd to the kernel list anyway.

Thanks again,

Sasha