Page 1 of 1

Resized pup101, free space didn't change

Posted: Sat 05 Nov 2005, 17:37
by jcagle
Maybe this has been mentioned before, I dunno. I've posted this on the Grafpup forum already, but it might be useful to post here.
I'm having a problem here. I just tried to increese the pup101 size by 512 meg.

The size of the pup101 file is 512 more than it was before. Previously, the size was at 743.8 M. That is still being reported by Xdiskusage. Both Xdiskusage and the root resize utility reported that I had 155 meg free, and they still report that, even though I resized the file.

Posted: Sun 06 Nov 2005, 01:54
by jcagle
Anyone helping here?

Posted: Sun 06 Nov 2005, 01:58
by jcagle
I just read that it can only go up to 768 meg...

That's a bummer...My parents wouldn't be happy with me partitioning the drive...

I guess I'll have to put my 30 gig drive from my old computer in when I get a chance.

Posted: Sun 06 Nov 2005, 08:04
by MU
You can create a new pup001 (backup the existing one first)and rename it to myfiles or whatever.
Like his you have a "filesystem in a file".
Then use your old pup001 again.

Now you could mount "myfiles" at startup and delete all files in it. Now you have lots of new free space.

Search for "loop" in the forum for instructions.

When you install Java for example (80 MB), you are asked, where to install it.
You could use /mnt/myfiles then.

Like this you don't need to re-partition the XP-machine.
You also can move existing applications there, and create a symlnk, so that they still work:
mv /usr/local/myapp /mnt/myfiles/myapp
ln -s /mnt/myfiles/myapp /usr/local/myapp

This works in most cases, just this application is not loaded to RAM at boot. It will be loaded from Harddisk, when you run it.

Mark

Posted: Sun 06 Nov 2005, 08:28
by GuestToo
if you build an iso using Puppy Unleashed, it will probably erase your loop-mounted file system without asking (it has happened to me)