It may, but do not have to. You may put your kernel image at a fixed MTD partition at the beginning of the flash chip and feed the rest of the flash to UBI. The point is that you do not have to give UBI whole flash chip, you just give it some MTD partition.

No, you don't have to. Although UBI stores some internal information, you may feed it an empty MTD device and UBI will format it automatically. The resulting MTD device will have all the internal data in place and no user volumes. Note, "empty flash" means that it has to contain only 0xFF bytes, i.e., to be fully erased. You may use the flash_eraseall MTD utility to wipe out MTD devices.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

DISCLAIMER: Messing around with boot loader issues can make your harddisks unbootable. Please make backups before doing so. Please install a new boot loader only when you really now what you do. We reject any responsibility for damages that may occur on your system. GRUB - the GRand Unified Bootloader - needs to access some files in order to run. Its best you place them on a small - 50MB is enough even for further extensions - FAT 16/32 partition.

In January 1987, several Washington State agencies that work with the business community joined together to launch the Unified Business Identifier (UBI) program. A UBI number is a nine-digit number that is assigned to your business when you apply for a business license through the Master License Service of the Department of Licensing or register with the Departments of Revenue, Labor and Industries, Employment Security, or the Secretary of State.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

FreeBSD's boot loader is incorrectly recognizing the hard drive's geometry. This must be manually set within fdisk when creating or modifying FreeBSD's slice. The correct drive geometry values can be found within the machine's BIOS. Look for the number of cylinders, heads and sectors for the particular drive. A dialog will pop up requesting the number of cylinders, heads and sectors. Type the numbers found from the BIOS separates by forward slashes.

The general idea is that you copy the first sector of your native root FreeBSD partition into a file in the DOS/Windows NT partition. Assuming you name that file something like c:\bootsect.bsd (inspired by c:\bootsect.dos), you can then edit the c:\boot.ini file to come up with something like this: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT" C:\BOOTSECT.

The general idea is that you copy the first sector of your native root Solaris/x86 partition into a file in the DOS/NT partition. Assuming you name that file something like c:\bootsect.sun (inspired by c:\bootsect.dos) you can then edit the c:\boot.ini file (copy boot.ini to boot.

The best way to figure out which format you have is to look for a logo imprinted on it, then visit our formats page. It might help to measure the tape and compare it to those pictured on our format line-up. Keep in mind that the physical dimensions are only part of the format. There are different ways to write information on those tapes. Don't worry about that too much. All you really need to know is whether it was recorded in America or somewhere overseas. We'll sort the rest out for you.

UBI is now in mainline kernel - it was pulled by Linus after 2.6.21 was released, so one can find it in later kernels. There is also an UBI development tree available at git://git.infradead.org/home/dedekind/ubi-2.6.git. User-space UBI utilities are available at the mtd-utils git repository ( git://git.infradead.org/mtd-utils.git). There is also a bunch of UBI tests in this repository.

In the linux configuration menu, go to "Device Drivers" -> "Memory Technology Devices (MTD)" -> "UBI - Unsorted block images", and mark the "Enable UBI" check-box. UBI may be either compiled into the kernel or built as a kernel module.

When debugging UBI you don't have to use a real embedded platform and real flash. You may use a PC with an MTD device emulator and run UBI on top of this emulated MTD device. For example, to get a 32MiB fake NOR flash, run "modprobe mtdram total_size=32768" or if you need a 64MiB fake NAND flash, run "modprobe nandsim second_id_byte=0x36". To ensure that you have fake MTD devices, run "cat /prof/mtd".

This depends on exactly what you want to do, and which application you are intending to use. The easiest thing is to execute the following Python command (the wrapping here is just for display - this should all be a single line): python -c "from spambayes.Options import options ; print options.display_full()" This will print out a complete list of the options, including a description of the option, and its default value.

You are probably trying to boot from a MacOS partition and have forgotten to extract the raw kernel file from archive that it is in (many kernel files are uploaded as tar archives, gzipped archives, or both). You can get a copy of the enhanced Stuffit Expander or the MacGzip and Tar utilities to extract the raw kernel file. Make sure that you do not do any sort of end-of-line (i.e. text) translation in the process, or you will corrupt the kernel binary.

You can't usually make up a clean boot disk on a system which has been booted from an infected floppy or hard disk. So how do you know you're booting clean? Actually, you can never be 100% sure. If you buy a PC with the system already installed, you can't be sure the supplier didn't format it with an infected disk.