Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

lilo hides FAT32 primaries

2 views
Skip to first unread message

brian & pam

unread,
Feb 18, 2002, 3:37:52 PM2/18/02
to
Hello: I'm trying to get my dual-boot (Mandrake 8.1/WinME) system to use lilo to boot. I have the following in /etc/lilo.conf:

boot=/dev/hda
prompt
timeout=150
vga=791
default=windows
lba32
#compact
message=/boot/message
menu-scheme=wb:bw:wb:bw
other=/dev/hda1
label=windows
table=/dev/hda
image=/boot/vmlinuz-2.4.8-26mdk
label=linux
root=/dev/hda4
initrd=/boot/initrd-2.4.8-26mdk.img
vga=788
read-only

I have 2 hard disks - linux has / on hda4 and /home on hdb1. hda has four primary partitions. 1, 2 and 3 are FAT32 - I have data on them that I access from windows and linux. The problem is when I install lilo with the above configuration the hda2 and hda3 partitions are hidden, windows can't see them. I've read 'man lilo' and 'man lilo.conf' and I don't see any reference to lilo hiding partitions. I used to boot this same partition setup from lilo when I had Mandrake 7,2, and never had this problem. Of course, linux has no problem with the setup - but I haven't converted the wife to linux yet.
Any pointers, direction gratefully accepted.
Thanks
brian

Pep

unread,
Feb 18, 2002, 5:11:01 PM2/18/02
to

brian & pam wrote:

What do you mean they are hidden?

The above configuration for Lilo will boot windows of /dev/hda1 and
Linux of /dev/hda4 and the Lilo boot image will be written to the MBR of
/dev/hda.

Are you saying that you cannot see /dev/hda3 and /dev/hda4 from within
windows?

If not but you are syaing that you cannot see them in Linux, it's
probably because you have not mounted them through fstab, of which Lilo
has nothing to do with.

Pep.

Pep

unread,
Feb 18, 2002, 5:38:34 PM2/18/02
to

Pep wrote:


Sorry, /dev/hda2 and /dev/hda3.

Jim Shaffer, Jr.

unread,
Feb 18, 2002, 6:41:39 PM2/18/02
to
Do a Google Groups search on "change-rules reset" to see how to fix this.
Nobody has yet offered me an explanation of why it was ever implemented.


brian & pam

unread,
Feb 19, 2002, 1:54:45 PM2/19/02
to
Yes - what I'm saying is that the above lilo.conf file boots windows which is on hda1 and that windows then cannot see hda2 or hda3 which are FAT32 primary partitions. Of course windows can't see hda4, that's where linux is. Linux can see them all, /etc/fstab is fine thank you.
Any ideas about why this should be, and how to fix it?
Thanks again
brian

brian & pam

unread,
Feb 19, 2002, 6:22:37 PM2/19/02
to
I found the answer - it's at this link. (I'll bet a lot of people are looking for this)

<http://groups.google.com/groups?q=%22change+automatic%22+lilo&hl=en&selm=j01tot8i39ib5ugdf8u1k2pnu3je8er4s3%404ax.com&rnum=1>

It was given to me by someone on the lockergnome.os.linux.software group.

brian

0 new messages