Full functionality requires Linux 2.4.x or better. (Earlier versions may still work, but are no longer regularly tested.) A large fraction of the code should run on just about anything. While the current code is fairly Linux specific, it should be fairly easy to port the majority of the code to support, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you are into that sort of thing).

ADB) Linus would be the best person to ask, but I don't know if he would have the time and patience to answer this question. There are some development issues that can be mentioned, though: PnP support in the kernel. Right now one can get PnP support using the isapnptools user space package and manually tuning the I/O, IRQ and DMA channel allocation, but future Linux kernels will do that for you.

ADB) There are no more known bugs in later kernel versions than in earlier kernel versions. However, the Linux kernel source code has been growing at a constant rate. As a general rule, large pieces of code tend to have undetected bugs. OTOH, the core code for the Linux kernel seems to have stabilized at around 16 thousand lines of C code, according to Larry McVoy. REW) I'd say more than 23 thousand lines in 2.1.x.

Presently, we support the 2.6 kernel, which is used in most current Linux distributions. Please check with your Linux vendor to determine which kernel version is used in your distribution.

The RDX USB device requires Mass Storage support, and support for USB 2.0 is recommended for maximum performance. Support for these features was available starting with Linux kernel 2.4.22. All Linux 2.6 kernels should support USB Mass Storage and USB 2.0. The RDX SATA device requires support for SATA ATAPI devices. SATA ATAPI support is available and enabled by default on distributions based on kernels 2.6.16 and later.

First, if you see a dialog box that asks "Do you wish to open this email?", you must click the "yes" button. Copy the link (which should look something like http://www.hotshare.net/file/xx-xxxxxxxxxx.html) and paste it into the address bar of a Non-AOL browser, such as Internet Explorer. This should allow you to download your file.

this time, Red Hat Linux 7.2, 7.3 and 8.0, as these have reached their End-Of-Life (EOL). Support for Red Hat Linux 9 will end on April, 31, 2004; we plan to provide legacy support for it, too. Support for Fedora Core releases will be provided on an 1-2-3-out scheme, providing roughly 1.5 years of update service.

There are two kernels to consider. The new code is already in the development Linux Kernel. It was introduced in 2.5.11. The stable Linux Kernel, currently 2.4.20, still has the old driver. We are happy with the state of the code, but we still have to convince the Kernel Gods that it's good.

The usual location of the musikCube library is in C:\Documents and Settings\%user name%\.musikproject\ where there are two database files one for the library, musik_u.db, and one for collected, musik_collected_u.db. However, the location of the musikCube libraries for whole drives exists in the root of the drive. For example, C:\.musikproject or E:\.musikproject Right click on the dynamic playlists menu where it says "dynamic playlists" and there is an option to create stock dynamic playlists.

Product Support Services (PSS) supports MBSA 2.0. Based on the improved detection capability of Microsoft Update, we recommend customers migrate to MBSA 2.0 as quickly as possible to take advantage of the improvements in update scanning. MBSA 1.2.1 is still supported for by PSS when MBSA 2.0 is not suitable based on product update availability in Microsoft Update. Note that the MSSecure.XML detection catalog used by MBSA 1.2.1 will no longer be updated starting in the first quarter of 2006.

There are two current commercial releases of SSH. They are sold by Datafellows and Van Dyke Software. F-Secure Tunnel and Terminal is available at http://www.datafellows.com/products/cryptography/f-sshtt.htm. It runs on UNIX, Windows, and Macintosh. It implements the SSH2 protocol, and does have a command-line scp for Windows. Please contact Datafellows directly for more information. SecureCRT is available at http://www.vandyke.com/products/SecureCRT/.

We will support the current version (lets call it version n) plus the previous version (ie n-1). When version n+1 is released we will only support version n-1 for one to two months to allow users of n-1 to upgrade to n+1. As SmoothWall is a supported Security application we cannot afford to compromise our position by trying to support too many old versions.

REG) Here are some basic guidelines for posting patches. For information on how to generate patches, see the entry by RRR below. Ensure the patch does not have trailing control-M characters on each line. A number of broken tools used to encode patches add control-M for "DOS compatibility". This breaks many versions of patch, so be sure to configure your tools properly, or use unbroken tools, otherwise your patch will be silently deleted. Include the patch inline in your email, in plain text.

ADB) Think again before you subscribe. Do you really want to get that much traffic in your mailbox? Are you so concerned about Linux kernel development that you will patch your kernel once a week, suffer through the oopses, bugs and the resulting time and energy losses? Are you ready to join the Order of the Great Penguin, and be called a "Linux geek" for the rest of your life? Maybe you're better off reading the weekly "Kernel Traffic" summary at http://www.kerneltraffic.org/.

ADB) At the bottom of each and every message sent by the linux-kernel mailing list server one can read:

ADB) Perhaps because there is no Linux Kernel Team, per se. Also because so many people contributed to the Linux kernel that it would be a tough task to setup and maintain such a page. Finally, although this is not a rule, most Linux kernel contributors prefer to keep a low profile, for various reasons.

ADB) You should probably read the definition of creeping featurism first. Related concepts, in increasing order of obfuscation: the KISS rule-of-thumb, the "Small is Beautiful" concept, Occam's Razor and Complexity Theory. A good book to read on these concepts as they apply to OS design is "The Mythical Man-Month" by Frederick P. Brooks, Jr.

RRR) In the root directory of the Linux kernel source tree (e.g. /usr/src/linux/), you will find a file COPYING. The file states that the Linux kernel is placed under the GNU General Public License (version 2), a copy of which is provided. If still in doubt, post to the appropriate forums (such as gnu.misc.discuss) or ask a lawyer, but don't ask about it on the linux-kernel list.

You should be able to edit the .config file and then just type make at the top level. For example, to use Linux's graphical config editor: cd linux-2.6-xen0 # make xconfig (configure however you want) (on old version you need to specify ARCH=xen after make) # cd .. # make If there's already a .config present in the kernel tree we leave it well alone. If there's none present and a ./dist/install/boot/config-2.6-xen0 exists then we copy that to .config.

Some versions of the Linux kernel do better with USB devices -- PalmOS devices in particular -- than others. 2.6.15 has been reported to cause difficulties in Kubuntu, while 2.6.17 is just fine.

enable "RTC support" (from Robert G. Brown). Note that inserting RTC support actually doesn't afaik prevent drift, but according to a discussion [Robert G. Brown] remember from a year ago or so it can prevent lockup when the clock is read at boot time. A note from Richard Jelinek says also that activating the Enhanced RTC is necessary to get the second CPU working (identified) on some original Intel Mainboards.

You need a kernel 2.6 or 2.4 plus cpufreq patch, Alan Cox already included it in the -ac branch. If you use kernel 2.6.0 or higher, everything is already in the kernel, check you have selected the right cpufreq drivers, see also #3. If you own a PowerPC (i.e. Apple) computer, and you use kernel 2.4 and have problems, then upgrade to benh kernel, cpudynd does work very well with his kernel.

The Linux Driver can read all the versions of NTFS. Each version is slightly different, but the driver only has to interpret the files and directories. All the indexes that NTFS maintains can be safely ignored. When the driver becomes able to write to an NTFS Volume, then it may be that the abilities will vary according to the version of NTFS it is writing to.

ADB) Sure. Before you check the list archives, you can search DejaNews and AltaVista (simultaneously, if your browser allows you to open various windows). You can also follow some links on the Linux Documentation Project site.

ADB) Is Hyper123 supported by gcc, or at least is the Hyper architecture supported by gcc? Do you have a target machine with a well defined architecture? If you have answered yes to both questions proceed to REW's answer. If you have answered no to either or both, don't even bother getting started. This is a major project, not exactly the kind of thing you do over the weekend.

ADB) Because it doesn't need one. You can add that feature to the boot loader code, if you want to. The Linux kernel has no graphics primitives, just like any UNIX kernel.

New architectures are implemented. This is usually OK, because the code that is specific to each architecture is (in theory, at least) separate from the others. Common code doesn't grow. New drivers are implemented. Again, this is OK, because each driver has different source files, and those are selectively compiled in the kernel executable or built as modules according to the specified kernel configuration. Old code gets adequately documented.

Since kernel threads are individual tasks with various shared parts, the question naturally arises: how are the threads associated with the parent and how are they accessed? There appear to be two ways: through the language or through the kernel. There exist several languages that support threads intrinsicly: Modula-3, Java, Python 1.4, Smalltalk/X, Objective-C/Gnustep and Ada. Each have language elements to program/access individual threads.