=== ubuntu64bit is now known as happydays [05:02] i take it that the fat.ko and vfat.ko for my marvell arm processor is the bootloader so what does .ko stand for? [05:07] ok, thanks for the help i found out .ko means kernel object file [05:09] so does fat.ko seach the input/output and vfat.ko point to the actual OS [05:10] or vice-versa [05:12] happydays, fat.ko doesn't have support for long file names [05:12] while vfat does [05:12] fat is only 7.3 file names [05:16] scientes: ok but for an arm processor you wouldn't need much anyway [05:16] happydays, it has nothing to do with the processor [05:17] like, a mobile phone uses 7.3 safe file names [05:17] **digital camera [05:17] when it uses the fat filesystem [05:17] doesn't it act as a bootloader for the arm? [05:18] happydays, that doesn't concern the kernel [05:18] thats uboot code, if you are using that sort ofsetup [05:18] (my sheevaplug just uses a flat uImage partition, and then ubifs) [05:18] oh [05:18] forgot [05:18] sure you can also access i from linux [05:19] but i dont have any comp with that sort of bootloader [05:20] fat is a VERY simple filesystem [05:20] both with and without long file names [05:21] cool ok thanks [05:22] and for that reason it appears in alot of embedded devices [05:22] ...and bootloaders [05:30] i was just running my arm machine got side track on what i was doing and completely forgot about the uboot cause i got into the machine at the password and not the boot lol [05:39] BTW sheevaplug's are great inexpensive devices great for learning the in's and out's of embedded systems === eebrah is now known as Guest60510