View Single Post
Posts: 946 | Thanked: 1,650 times | Joined on Oct 2009 @ Germany
#18
Originally Posted by javispedro View Post
Until such a software is made, I see no benefit to having a sparse FAT32 file over the current dual partition approach.
I already agreed that for the default configuration a fully allocated FAT image
would be the simplest and a comparable solution to the current approach.
Advanced users, however, may play with sparse files or whatever they like.
For you, there would be neither an immediate benefit (maybe later?) but also no disadvantages.
If you can find some drawbacks of the approach, I would be happy to discuss
them. but so far you only defend status quo because YOU see no benefits.

So why don't you create the larger ext3 partition into the loop file instead?
because the FAT partition is exported for USB mass storage

Originally Posted by javispedro View Post
This has nothing to do with the partition layout. $HOME has never been visible to the standard applications, even when MyDocs was in the same partition as $HOME.
yes, that's a separate (reported) bug, but if MyDocs was a ext3 directory I could simply symlink its subdirs to my $HOME subdirs...

If you're really interested in this, you can "move" where applications expect MyDocs. At least, you could in Diablo with the $MYDOCSDIR environment variable.
IIRC it failed when I tried last time but, thanks, I'll give it another try.

Last edited by titan; 2009-12-29 at 23:56.