> God, all this only to do a lseek+write? > For comparison: fsck_minix.c does something like that > with just one small function: > > static void write_block(unsigned nr, void *addr)
very disgusting :D > uuid_generate(fs->super->s_uuid); ... > and I dare not look into get_node_id()... it apparently finds > my network card and reads its MAC - !!!!??? sorry??! there's reasons behind using the MAC to generate the UUID (not that many of them matter in the embedded/busybox space however)... > We already have mkswap_generate_uuid() which is only > 183 bytes long, and is perfectly capable of replacing > uuid_generate(). thanks for that one... > > And so on... > > It's not THAT much work, but it must be done before mke2fs > is back in busybox. My plan of attack on this is to almost start from scratch on the mke2fs utility (grabbing the current upstream one as an example, not the one we currently distribute) and get to where I can create a basic ext2 filesystem of a given size that survives a full fsck with normal e2fsprogs. Then add on functionality (starting with variable block size and journaling) as I have time (potentially with configs for some of them to keep code size down). Then later if I or anyone else wants/needs it we can recreate the full e2fsprogs suite. The main reason I want it is for a custom cd Installer that lives in an initramfs. I don't really **need** it as part of busybox, but it would be cool to do and would keep my memory footprint/cd image smaller. Since the distro I'm installing already has the full e2fsprogs, I can start with just mke2fs for now. Matt _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
