On Tue, 2008-07-29 at 14:56 -0500, Richard Shaw wrote: > I'm trying to get to some files on an NTFS partition at boot time and > tried searching all over google with very limited success. It seems > the ntfs.ko module does not support read/write well and the ntfs-3g > module uses fuse. The only reason you should need to have this in the initrd is if you're booting / off ntfs-3g, which I would strongly discourage. Can you explain exactly why you need this? Thanks, ~spot (ntfs-3g Fedora maintainer)

On Tue, 2008-07-29 at 16:09 -0500, Richard Shaw wrote: > I'm using the livecd-iso-to-disk to make a bootable USB thumb drive > for a laptop where I don't want to alter the drive partitioning. I've > got a 1GB overlay on it but trying to update F9 from the iso to > current pretty much max's it out. I have created a 4GB overlay file on > the HD but it is a NTFS partition. > > I updated the syslinux.cfg to get it to find the overlay file on the > HD and it attempted it (I changed out the overlay= command to use the > HD label and UUID) but it complained that it didn't understand the > filesystem type. Since I can access the HD once I boot I assume I need > NTFS support in the initrd. Okay, I'm with you. Unfortunately, the Fedora initrd doesn't have any concept of fuse, or performing fuse mounts. It is not as simple as simply including the necessary files in the initrd, you'd need to be sure that the fuse kernel module, as well as the ntfs-3g bits (and probably the fuse userspace bits and anything they depend on) were there, yes, but you'd also have to add the mount commands into the initrd execution sequence. It's possible, but I'm not volunteering to hack it up... sorry. ~spot

Would it be pretty easy to get the modules (ricoh_mmc and dependencies) required to use the ricoh internal SD card reader in the initrd? The other thing i wanted to do was just put syslinux on the USB drive since it will boot to that, but not the card reader, and then actually have the livecd image on an SD card.