Quote:
Originally Posted by ivancauso
I needed to transfer the file bootsect.lnx from linux to windows (I don't have floppy in my computer) in order to be able to get the boot working, and therefore I could see no other solution but to use FAT32 for windowsxp.
|
You won't need to do that if you allow grub
to control the booting of BOTH linux and windows.
Quote:
Originally Posted by ivancauso
By the way, I heard about security issues when formatting windows partition as FAT32 but I don't really understand why! Does anyone know?
|
The most obvious issue is that FAT32 doesn't allow permissions
to be set on files and directories. Both ext2(&3) and NTFS do allow this,
which vastly improves security and stability in the majority of cases.
Quote:
Originally Posted by ivancauso
What is hda6 (/Boot) for?
|
It isn't strictly necessary in most cases, but I find it useful
to have a separate /boot ... and most distros with
automatic partitioning schemes use it.
The most likely use for it is that you might (eventually)
decide to have EVMS or LVM partitions on your drive
where the modules (and programs to manipulate) to access
those partitions will bo loaded from what's called an
initial ramdisk (initrd) located in /boot.
The kernels and the grub menu are stored in /boot.
(If you use grub instead of LILO).
Lilo's config is /etc/lilo.conf and works differently.
Quote:
Originally Posted by ivancauso
I installed LILO in the MBR and I don't know how am I suposed to use this partition. I made it bootable using fdisk, but that was just a guess... The system is booting normal and evrything seems to be working... I formatted as ext3 as you showed in the example...so how can I use that now?
|
Installed LILO in MBR = GOOD.
Made /boot partition (?) bootable = YES
Formatted as ext3 = GOOD (err. formatted WHAT is ext3?)
"How do I use that?" ... I'm not sure what you mean.
ext3 is a journalling version of ext2 ... which means that
every 5 secs (by default) a log is written that describes the
changes on the disc. If for some reason the system crashes
(eg. power outage) then at restart, the changes to the disk
are 'rewound' rather than checking the WHOLE disk ...
very nice feature.
Are you able to boot into both Windows and Linux?
Do you have a desktop in Linux?
Can you open a terminal or console?
When you've got to this stage, take a look at
/etc/fstab
You need to edit that (as root) and make the line that
mentions the FAT32 partition read something like this:
Code:
/dev/hda5 /mnt/sharedFAT vfat noauto,user,umask=002 0 0
Of course, the /mnt/sharedFAT directory must exist.
The noauto option is so that the partition isn't mounted at boot.
user = so that a normal (non-root) user can mount the partition
and the umask is so that a normal user can write to the mounted filesystem.
To mount it:
Code:
$ mount /mnt/sharedFAT
To unmount it:
Code:
$ umount /mnt/sharedFAT
(umount not unmount)
Depending on the desktop environment installed, you may even have
a nice icon on your desktop or a 'Computer' folder that will
allow you to mount/unmount the partition with the click of
the mouse.
Enjoy.