Posts are the individual questions or replies that people submit and threads are the series of posts in reply to the original post or question.

Use the "New Posts" option on the main forum toolbar at the top of every page to find threads with the most recent posts. Threads with unread posts are bold, and have a small blue, square icon next to them that will take you right to the first unread message. vBulletin does its best to track which posts you have and have not read, but it's not perfect.

A forum may not display any threads if there are no threads in the forum or if filters on the forms have been applied and no threads match the filter. An example of a filter is filtering to display threads newer than a certain date, such as threads new in the past 2 weeks.

ADB) Very shortly, threads are "lightweight" processes (see the definition of a process in the Linux Kernel book) that can run in parallel. This is a lot different from standard UNIX processes that are scheduled and run in sequential fashion. More threads information can be found here or in the excellent Linux Parallel Processing HOWTO by Professor Hank Dietz. REG) When people talk about threads, they usually mean kernel threads i.e. threads that can be scheduled by the kernel.

A forum may not display any threads if there are no threads in the forum or if filters on the forms have been applied and no threads match the filter. An example of a filter is filtering to display threads newer than a certain date, such as threads new in the past 2 weeks.

Erm... sorry about that, this is just a proof-of-concept page and it isn't really production quality. Also this project is hosted on a cheap webhost so may go off from time-to-time. I'm afraid that there are no guarantees that any old threads will be available as betfair may delete them at any point, offhand I don't know their schedule. This project doesn't check for actual thread existence but may do in the future. I can assure you that I'm not.

I will be commenting on YouTube videos and members, both old and new. I'll go back and forth between old favorites and new undiscovered gems. Most posts will contain at least one video, embedded in the post, and with a link to the video on YouTube. I'll also be doing interviews of YouTube members so that you can learn more about them!

Yes, look in static.doc and the USENET file distributed with Waffle for /spy=monitor. basically just have 'DEFAULT /spy=monitor' at the top of your waffle/system/usenet file, and you'll probably be ok (unless you drastically changed your 'forums' static file entry).

The 2.4.xx kernel does not provide proper support for grouping threads by process. Hacks exist to group them anyway, but such hacks will falsely group similar tasks and will fail to group tasks due to race conditions. The hacks are also slow. As none of this is acceptable in a critical system tool, task grouping is not currently available for the 2.4.xx kernel. The 2.6.xx kernel allows for proper thread grouping and reporting.

Currently, PAPI only supports thread level measurements with kernel or bound threads. Each thread must manipulate and read its own counters. When a thread is created, it inherits no PAPI information from the calling thread. Support for this kind of functionality is being implemented.

Vertical feedneck threading is unique to the Shocker NXT only. The Impulse, Nerve, Ion, Shocker Sport, and Shocker SFT, Omen, Bushmaster, Invert, which are all threaded identically between them, are threaded differently than the NXT feednecks.

The only reason to use Autococker threads is for the compatibility with some other markers. However, from a design standpoint, Impulse threads are all around better. They're more difficult to strip, easier to quickly re-align, require less turns to remove and reinstall, and have a shorter barrel hood which matches the short Shocker body better (if Autococker threads were used, the body would be made unnecessarily longer).