On Sat, May 07, 2005 at 08:10:18PM -0500, David Masover wrote: > > The blocklist is only needed to find the blocks in the nested file, > > which is huge. (I don't know anything about reiser packing, but > > things like tail-merging aren't a serious problem.) > > Yet, it's still a problem. You want a standardized way to map files to > underlying blocks, and before Reiser4, I'd say this was easy. But now, > who knows what the FS does to bastardize the file on the way down? > Crypto/compression? Tail-packing? Stenography? The possibilities are > endless...
Can't you disable these things for the special nested file? You only need the block list for one file! > > Small users are happy to leave their computer overnight. > > Maybe you are, but newbies aren't. Maybe you got it wrong? Maybe you > got all your stuff moved around properly, but didn't leave room for a > swap partition? Looks like you have to start over! Ideally, you'd have a tool where you plan the entire job first (including creating the new swap partition), and then execute it in one hit. > Unless the newbies are following a VERY specific recipie or VERY good > tools, this process could easily take a few weeks, instead of a few > hours with the repacker. And that repacker looks easier to implement > than a noob-proof UI. Of course, people who know tell me I'm naive on > both counts... Clearly, a repacker would be better for users. > The current situation is not impossible, unless you want real users (not > fanboys) to choose Reiser4 over ANYTHING else. Why would I choose > Reiser4+convertfs over ReiserFS 3 + resize_reiserfs? Or even > ntfs+ntfsresize? Why do newbies ever choose reiserfs? Crypto? Cheers, Andrew
