InstallationKwikis
Here are some helpful kwikis for installing Linux.
Be sure to also check the ArchLUG Kwiki page for kwikis that are specific to your distribution of Linux.
SystemRescueCD
SystemRescueCD - http://www.sysresccd.org/
SystemRescueCD is a linux system on a bootable cdrom for repairing your system and your data after a crash. It also aims to provide an easy way to carry out admin tasks on your computer, such as creating and editing the partitions of the hard disk. It contains a lot of system utilities (parted, partimage, fstools, ...) and basic ones (editors, midnight commander, network tools). It aims to be very easy to use: just boot from the cdrom, and you can do everything. The kernel of the system supports most important file systems (ext2/ext3, reiserfs, xfs, jfs, vfat, ntfs, iso9660), and network ones (samba and nfs).
Resizing NTFS and XP partitions to make room for Linux
- ntfsresize - http://linux-ntfs.sourceforge.net/
- QtParted - http://qtparted.sourceforge.net/
- The ntfsresize FAQ
- The NTFS Problem for Linux Installers Summary
Accessing NTFS and XP partitions from Linux
- Paragon NTFS for Linux Driver - a commercial product. Can write safely to NTFS. Reasonable performance.
- Captive drivers - a wrapper driver around the native Windows drivers. Can write safely to NTFS. Not fast.
- Kernel drivers - still experimental and READ-ONLY. Writing is NOT safe. Reading is quite fast.
- Linux Magazine Review
Booting Linux with the NT Loader
Dual Boot and MBR change detection by Windows/anti-virus programs
On dual-boot with Linux and Windows, you should be alert for a latent warning from Windows. After a period of use, Windows or your anti-virus program will spot a difference in the boot record, which is related to the changes made when you installed your bootloader (LILO or GRUB) into the MBR (Master Boot Record) of your hard drive, and fixed up the boot sequence.
Windows (or your anti-virus program) will notify you that it has detected a change in the MBR boot record, and offer to "fix it", ignore it, or adjust itself to this change.
You do not want it to fix the problem, as that will destroy the ability of your chosen boot loader to work.
Select the 'ignore' option, and let Windows or your anti-virus program "digest" this information "as an expected change" and you should not get any such message in the future.
Keep this in the back of your mind (or tell the owner of this new dual-boot system), as it will not happen immediately. Windows and most anti-virus programs only look in the boot record (MBR) when you ask it to scan a particular file, or a remnant of a cleaned virus toggles an auto-protect scan.
"EBDA too big" message during boot
Q: After recompiling the kernel, changing lilo.conf and executing lilo I get the following error message printed right after "LILO ... Loading Linux" when booting:
EBDA too big
A: Please make the following change to /usr/share/misc/magic as described in DebianBugReport : 106898 . Then run "file" on the kernel and see if it is the right type of kernel.
Here is the first three lines of the Linux kernel recognition. The third line used to check for =0x201, the correct check is for >=0x200 (which is the check performed by lilo). The magic file should match lilo's checks for this to help in debugging lilo problems.
# Linux kernel boot images (i386 arch) (Wolfram Kleff) 514 string HdrS Linux kernel >510 leshort 0xAA55 x86 boot executable >>518 leshort >=0x200
|
|