VERY informative, Jeff!  Very much appreciate this new information....

[EMAIL PROTECTED] wrote:

> vfat is backward-compatible. Microsoft used reserved features in the FAT
> format to implement its features, and included consistency checks with
> fallback to 8.3 behavior in case an older MSDOS system modifies the FAT
> entries.
> 
> Every floppy you use in Windows is treated as vfat.

Interesting!

> > > * What about DOS diskettes? 1.44M preformatted diskettes?
> >
> > Require a reformat assuming that they aren't already VFAT formatted. Even
> > for the average Windows user formatting a disk isn't difficult.
> 
> What about them? They are vfat.

Well!

> The vfat module happens to support both the long filenames and large disk
> support.

And just how much space does VFAT take up?

> The loader has to know the name. "ldd" gets the loader to divulge the
> name(s) expected by a binary on a full distro.  Might be better to steal
> this technique in the package loader than add a new file to the lrp
> format, though that doesn't help those with the old lrpkg figure out
> their problems.

My biggest concern is that someone on one of the other distributions
(e.g., LRP 2.9.8) will load a package, see a SegFault, and then go ask
why it SegFaults - with the accompanying head-scratching by the
wizards as to why a prepackaged *.lrp would SegFault.

The version idea is the simplest..... just query the version and see
if it is xxx(2.1).

I like the long name idea, using VFAT.  The only thing is, VFAT adds
FAT to the kernel (pun intended :-)  Just how big is this thing?

Long names also mean this: someone on an old distribution copies this
*.lrp over, and of course has to shoehorn it into 8.3 - either
deliberately, or via Windows 8.3 mangling for DOS FAT.  Then loading
the package will fail, because the name doesn't match the <pkg>.list
name....  And using VFAT would allow longer names under UNIX as well.

_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to