These files are OEM versions of Ontrack. They have got a big bug: an error occures when you want to rename a file. The IBM*.COM files nativly support the new partition type 0Fh (LBA). It's not recommended to use these files if you don't know what you do. The COMMAND.COM file seems to be okay, but I didn't notice any changes.

Yes, but it is a little tricky. You should not use the usual user space functions open, read, write, and close. Instead you should use filp_open and the methods in the returned struct. Always remember to cleanup after yourself. Here is an example: (FIXME: Put the updated version here) kcp.c. If you need more examples I suggest you take a look on the sourcecode for the khttpd or tux webserver. Always remember that file access is only possible in a process context.

ADB) Production or stable kernels have a well defined feature set, a low number of known bugs, and tried and proven drivers. They are released less frequently than the experimental kernels, but even so some "vintages" are considered better than others. GNU/Linux distributions are usually based on chosen stable kernel versions, not necessarily the latest production version.

ADB) These are intermediate pre-release versions of version f.g.hh. Note that usually i < 5, but e.g. 2.0.34prei was available with i = 1 to 16. Sometimes "pre" is replaced by the initials of the developer putting together the kernel revision, e.g. 2.1.105ac4 means the 4th intermediate release of kernel version 2.1.105 by Alan Cox.

RRR) Depending on your patch there are several ways to get it into the kernel. The first thing is to determine under which maintainer does your code fall into (look in the MAINTAINERS file). If your patch is only a small bugfix and you're sure that it is 'obviously correct', then by all means send it to the appropriate maintainer and post it to the list. If there is urgency to the bugfix (i.e.

REG) Originally, Linus Torvalds maintained the kernel. As the kernel has matured, he has delegated maintenance for older stable versions to others, while he continues development of the latest "bleeding edge" release. As of 27-MAY-2002, the following kernel versions are maintained by these people:

REG) See the Kernel HOWTO for some information. Also, there are people at http://www.kernelnewbies.org/ who are usually willing to help. William Stearns) The Buildkernel script walks you through an entire kernel build, including downloading the necessary files, patching the source, building the kernel and modules, installing the lot into lilo, and optionally building pcmcia-cs, cipe, and freeswan code for that kernel.

Several FTP clients have broken file date handling, and display the incorrect date. Please make sure you're using a more robust client, and this problem will disappear for you. Technically, it is because FTP doesn't have a specified way to request a machine-readable directory listing.

Building a new kernel was originally pretty much a required step in a FreeBSD installation, but more recent releases have benefited from the introduction of a much friendlier kernel configuration tool. When at the FreeBSD boot prompt (boot:), use the -c flag and you will be dropped into a visual configuration screen which allows you to configure the kernel's settings for most common ISA cards.

ADB) Linux kernel versions are divided in two series: experimental (odd series e.g. 1.3.xx or 2.1.x) and production (even series e.g. 1.2.xx, 2.0.xx, 2.2.x, 2.4.x and so on). The experimental series are fast moving versions which are used to test new features, algorithms, device drivers, etc. By their own nature the experimental kernels may behave in unpredictable ways, so one may experience data losses, random machine lockups, etc.

ADB) The primary site for the Linux kernel (experimental and production) sources is hosted by Transmeta (the company Linus Torvalds used to work for) on a dedicated Web server at http://www.kernel.org/. This site is mirrored across the world, and has pointers to mirrors for each country. You can go directly to a mirror for your country by going to http://www.CODE.kernel.org/ where "CODE" is the appropriate country code.

REG) There are many places which provide various extra patches to the kernel for new features. One fairly good archive is available at: http://www.linuxhq.com/.

If you have a 2.2 or a 2.0 kernel, you can upgrade to 2.4 ;) Sorry but I don't support those kernels.

Believe me: Nothing. The driver runs completely in user space and therefore shouls not produce kernel panics. This seems to be an OS bug. Please write down the message (or take a photograph) and mail it to me along with a detailled description about what you did when you encountered this and your system configuration. I will try to find the cause and contact Apple to find a solution.

VPShosting.net.au does not allow for any kernel modifications. You will be running a variant of Linux 2.6.x which is the latest stable Linux kernel.

The basic design of QNX® is a micro kernel. Win95, NT, UNIX and OS/2 all have a "monolithic" design in which the core operating system code is very large. Generally speaking, system level functions like hardware drivers must be part of the kernel to run. This is for, among other reasons, processor "supervisor" privileges are usually limited to kernel code for protection.

The latest kernel sources are available from ftp.netbsd.org or one of the mirrors in the directory /pub/NetBSD/NetBSD-current/src/sys/ . Check out the NetBSD/mac68k Meta-FAQ for more information on following current sources.

A kernel module is a piece of code placed in the kernel address space. This is similar to shared libraries. The module can contain data and code as you wish. Being in shared memory the module and it's code can be accessed by any thread in kernel mode. When the module is loaded a special initialization function will be called and should quickly return success or failure. Before the module is unloaded an optional cleanup function is called, this must do whatever cleanup needs to be done.

Yes you can do that. Most modules don't need to create any kernel threads. If you are writing a driver and think you need a kernel thread you could easily be wrong.