Do you really mean '2.0.0'? If so, why? If you really mean 2.0.0, go
ahead and see if 2.0.39 (the one currently on tomsrtbt) fixes the problem.
-Tom
On Sun, 20 May 2001, Klaus Reinhardt wrote:
> Date: Sun, 20 May 2001 08:52:52 +0200
> From: Klaus Reinhardt <[EMAIL PROTECTED]>
> To: Toms Group <[EMAIL PROTECTED]>
> Subject: [tomsrtbt] H2 get vfat compiled in 2.0.0?
>
> ----------------- mailto:[EMAIL PROTECTED] start -------------------
> Hi
> I have (the orig and recomp) version 2.0.0 of linux and got
> trying mount of a b-partition the error:
> wrong fs-type or super-block.
> The System.map has on the other hand the following entries:
>
> 0000000000159ffc t vfat_ioctl_fill
> 000000000015e6cc T vfat_put_super
> 000000000015e89c T vfat_read_super
> 000000000015e8f4 t vfat_valid_longname
> 000000000015ea24 t vfat_valid_shortname
> 000000000015ed54 t vfat_format_name
> 000000000015f120 t vfat_create_shortname
> 000000000015f63c t vfat_find_free_slots
> 000000000015f8e8 t vfat_fill_long_slots
> 000000000015fa8c t vfat_build_slots
> 000000000015fbac t vfat_readdir_cb
> 000000000015fc88 t vfat_find
> 0000000000160048 T vfat_lookup
> 0000000000160258 t vfat_create_entry
> 0000000000160380 T vfat_create
> 00000000001603d0 t vfat_create_a_dotdir
> 00000000001604f4 t vfat_create_dotdirs
> 00000000001605f8 t vfat_empty
> 00000000001606f8 t vfat_rmdir_free_ino
> 00000000001607e4 t vfat_unlink_free_ino
> 00000000001608a8 t vfat_remove_entry
> 0000000000160988 t vfat_rmdirx
> 0000000000160a3c T vfat_rmdir
> 0000000000160a64 t vfat_unlinkx
> 0000000000160afc T vfat_mkdir
> 0000000000160bb8 T vfat_unlink
> 0000000000160be0 T vfat_rename
> 0000000000161280 T vfat_read_inode
> 0000000000161294 T init_vfat_fs
> 00000000001af720 d vfat_sops
> 00000000001af798 D vfat_dir_inode_operations
> 00000000001af7e0 d vfat_fs_type
> 00000000001af7f0 d vfat_syms
>
>
> K@Rdt
> ----------------- mailto:[EMAIL PROTECTED] !end! -------------------
>
>
