To get people to read your post and answer your question: - Read "Linux Documents Explained for Newbies" - posted weekly (see below). - Please do not post questions answered in the FAQ lists. - Please do not post "Please send me the FAQ". See below. - Please do not post "Split this group now". See below. - Be informative, both in subject line and body. See below. - Please read the documentation for the program you have a problem with. - Linux-specific posts only please - Unix, X, C, etc. groups listed below. For more information read on ... ** Linux Documents Explained for Newbies ** is is posted weekly by Jay MacDonald. If you can't find it email me or Jay <jay-m@equinox.unr.edu>. It will tell you about the Linux FAQ, the INFO-SHEET, the META-FAQ, etc. These are posted regularly to comp.os.linux and c.o.l.announce, and can be found in /pub/usenet/news.answers/linux-faq at rtfm.mit.edu and on the Linux archive sites. If you can't get them there, try mailing "mailserver@nic.funet.fi", "mail-server@rtfm.mit.edu" or "ftpmail@decwrl.dec.com". If you can't get them any other way, e-mail me. Splitting the group: It's been tried, and all the new groups except .announce failed. It can't be tried again within 6 months. See the FAQ for details, or read news.announce.newgroups. If you insist on discussing it, do so in news.groups (if c.o.l has too much volume already, why make it worse?). With threaded newsreaders now in widespread use using a good, specific, polite subject line will get you many more readers. Most people will ignore posts with subjects like "Linux", "Help", "SLS", etc. Don't shout to get attention. Put as much information in your post as possible - preferably a brief summary followed by session transcripts, etc. as appropriate. Include the precise text of any error messages printed, etc., and appropriate info about your setup. Linux is a Unix clone running on PCs; X has its own groups. One of the following groups is is quite likely to be more appropriate for your question: Unix: comp.unix.questions, .admin, .programmer, .shell etc. X: comp.windows.x, comp.windows.x.i386unix (for XFree86 etc) GNU: gnu.emacs.help, comp.emacs, gnu.gcc.help, gnu.* generally PCs: comp.sys.ibm.pc.hardware C: comp.lang.c -- Ian Jackson ijackson@nyx.cs.du.edu PGP2 public key available on request Home: 35 Molewood Close, Cambridge, UK, CB4 3SR; +44 223 327029. These opin- Work and urgent email: iwj@cam-orl.co.uk; +44 223 343398 ions are my own. Olivetti Research Ltd, Old Addenbrookes Site, Trumpington St, Cambridge, UK;
| Ingo Molnar | Re: [PATCH 00/34] AMD IOMMU driver |
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Ryan Hope | reiser4 for 2.6.27-rc1 |
git: | |
| Linus Torvalds | Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins |
| Jon Smirl | Re: VCS comparison table |
| Junio C Hamano | Re: [PATCH] Teach remote machinery about remotes.default config variable |
| Dmitry Kakurin | Re: Git on MSys (or how to make it easy for Windows users to compile git) |
| Octavian Purdila | race in skb_splice_bits? |
| Wolfgang Walter | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
| Ingo Molnar | Re: [bug, netconsole, SLUB] BUG skbuff_head_cache: Poison overwritten |
| Rick Jones | Re: 2.6.24 BUG: soft lockup - CPU#X |
| Richard Stallman | Real men don't attack straw men |
| chefren | Kuro5hin: OpenBSD Founder Theo deRaadt Has Conflict of Interest With AMD |
| Pieter Verberne | File collision while using pkg_add |
| Jason Dixon | Re: Hardware recommendation for firewalls (more than 4 NICs) |
