Slackware 9.1

/dev/hda1 = NTFS (WinXP)
/dev/hda2 = NTFS
/dev/hda3 = FAT32
/dev/hdd = Slackware 9.1

yesterday I added a new harddrive to my existing setup, and started installed Slackware 9.1 on it (using the bare.i kernel)

During the installation, it only asked to add /dev/hda3 to my fstab. I suppose this means that the bare.i kernel has no support for NTFS. Should I use a kernel that supports NTFS (which is what in Slackware 9.1 ?)

This stopped me from installing LILO using the simple method (and I'm not expert enough to use expert without manual). I assume that since bare.i can't read the NTFS partitions, that it also won't automatically detect windows and install an option to boot the windows partition. In addition, if I ask it to install to mbr, won't it have to write to the first cylinder of hda1 (which is NTFS) ?

Is there anyone that can confirm whether simple LILO installation will cleanly allow we to dual boot in my configuration. If no, what are the steps that I should take ?

hi there

lilo is confined to /boot and MBR directory of ur system
there after the control is sent to kernel which will load the partitons of th FS it supports

to get ntfs support

either comopile ur kernel with ntfs support

or go to

http://linux-ntfs.sourceforge.net/

regards

So if I understand this correctly, writing LILO will not disturb the NTFS partition, but since slacware 9.1 doesn't know NTFS by default, I will have to manually configure it for Windows XP to boot.

hi there

what lilo does is ---it passes the control from the boot option to the required kernel or device
so say u have 2 option odf windows an d linux
and ur windows is NTFS
so when u choose to boot windows,it will pass the control to the requuired windows partition or vice versa

now when u boot linux,it depends that if u have ntfs support in ur linux then u can load that ntfs partiton in linux

regards