[EMAIL PROTECTED] writes:
>
> [Alistair Riddoch:]
>
> > As far as I know this has not yet been tried. It may turn out to be
> > dificult to fit it into ELKS very small memory footprint.
>
> Hmm... I thought that the MSDOS filesystem should be simple enough to
> implement inside a small kernel (well, at least DOS can do it). Just
> curious...
>
> Then again, maybe you're right... I just tried pasting the MSDOS code from
> the 2.0.30 kernel source into ELKS -- the compiler gave me a `text segment
> too large to fit into 16-bit' error message, even after I removed Minix
> filesystem support and deleted lots of useless stuff from the MSDOS code
> (FAT32, mount options, etc.). Maybe it's just because I was working with
> ELKS 0.0.66, where the text segment for the original kernel was almost full
> to the brim (63K)...
>
> I'd really like to find out other people's experiences with this (if any).
>
Don't try and do anything with old versions of ELKS. Newer versions all
have significant bug fixes, and perform better than old ones.
The latest kernel will leave plenty of room in the text segment for
experimentation if you config out optional drivers, such as serial parallel
and mem drivers.
I would have imagined it would take more effort than this to convert the
Linux DOSfs code. Did you make sure you replaced any #include <linux/foo.h>
lines with #include <linuxmt/foo.h> to make sure that the correct inode
structures are picked up?
Al
