type this at you Linux command prompt
cat /proc/filesystems
Linux can support a variety of filesystems. Many users choose to use EXT filesystems (ext2,ext3,ext4) but you can also use FAT (windows-compatible) and lesser known filesystems (like ReiserFS)
Windows 98 supports FAT filesystems only. Windows XP supports FAT and NTFS filesystems.
The 2.6 Linux kernel supports up to 4,294,967,296 user IDs. The 2.4 kernel only supports 65,536.
Yes. By default, Ubuntu has supported multi processing since Ubuntu 5, due to the default kernel that loads is and SMP kernel. In other words it assumes a system has multiprocessing. If of course you don't, there is no degradation in performance.
The Linux kernel supports up to the latest Intel and AMD processors, as well as some other architectures. As such, most programs should run about the same on all of them.
ldlinux.sys is the name of the bootloader file used in SYSLINUX and ISOLINUX (used for booting Linux off of FAT32 and ISO9660 filesystems, respectively). It is loaded into memory by the BIOS on bootup. The loader then parses the configuration file (syslinux.cfg or isolinux.cfg) to know which kernel to launch, along with parameters to be passed to it.
NTFS read support has been in the kernel since 2.2. 2.6.0 supports read / write operations.
It varies from system to system, based on what the distributors call it and if you run a custom kernel or not, but the file will usually at least have vmlinuz as part of the name. This means it runs on its own virtual machine and is compressed. Also, there will likely be a ramdisk image accompanying the kernel that will contain necessary drivers and configuration files for the kernel to be able to read and run what's on your hard disk. Remember that the kernel file is an IMAGE, not an executable binary. That means its meant to basically be copied straight into memory unmodified and manipulated from there before execution. You, the user will not be able to modify it very easily. IF your goal is a custom kernel, then get the source code for the kernel, introduce your patches, do your configuration, and build it. If your goal is in seeing what the kernel is "thinking" at any point in time, you'd be best looking at the contents of the /proc and /sys directories, which give you a peek into the innards of the systems current operation, as they are virtual filesystems that base themselves off of the current state of the kernel. You can also normally grab your current kernel's configuration by copying out /proc/config.gz and decompressing it. It will be a plaintext file you can read and write.
Depends on your distribution - most well-documented distributions will tell you how to install a hardened kernel along with kernel extensions that help with enforcing security policies (e.g. SELinux).
It does, you just need to put on the kernel that supports it. I think it's the unofficial one, the one before the newest
mount
The virtual kernel is a kernel that can be used in unbuntu guest. It is a very lean kernel, this helps in reducing overhead. It installs the server kernel via a new name.