Skip to Content.
Sympa Menu

baslinux - Re: [BL] hd problem

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] hd problem
  • Date: Sun, 20 Feb 2005 20:15:43 +0000 (UTC)

On Mon, 21 Feb 2005 3aoo-cvfd AT dea.spamcon.org wrote:

sindi keesan wrote:

I notice that BL3 mounts /initrd/DOS

/initrd/DOS is mounted by the initial ramdisk
(in order to access fs.img).

but is it mounting the partition with loadlin

Once the kernel boots. loadlin is irrelevant.
In fact it is possible to run loadlin successfully
from a device that the kernel is incapable of
accessing.

or the partition with fs.img?

The loop version of BL3 must have access to
/initrd/DOS/baslin/fs.img because that is
the root filesystem.

if I am likely to mess up FAT32 partitions with
the regular kernel.

I have seen no evidence that the BL3 kernel is
messing up FAT32 partition.

What is linux using vfat for in BL2?

To read/write long filenames on Windows partitions.

I am trying to think of some situation where I would want to do this and I cannot do so. I have been using FAT12 floppy and FAT16 (?) zip formats, and if I need to transfer long file names between computers via disk, I just rename them shorter. I don't normally read Windows files with linux. I think I will recompile with vfat=N and see how it goes. Unless someone can give me a reason why I would want vfat in the kernel.

I still don't know what went wrong with the partition table. But I see no reason to put FAT32 on a computer again.

Cheers,
Steven






____________________________
http://www.basiclinux.com.ru
_______________________________________________
BasLinux mailing list
BasLinux AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/baslinux


keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org




Archive powered by MHonArc 2.6.24.

Top of Page