there is a special type of format for swaps partitions. But don't use a swap on:

-a Flash Memory Card (SD, MicroSD, CompactFlash, etc.)
-USB thumb drive
-Solid State Drives_________________What consenting adults do in their bedroom is none of your business so if you think there is something wrong with homosexuality and your bothered by it, then you're an idiot who needs to mind their own business.

As I understand a swap partition, it has no specified or defined filesystem, so it is not formatted in the usual sense of the word. It is just.....swap. Virtual memory. Puppy uses it if it runs out of RAM, which is unlikely with 384 MB of RAM unless you watch video or do things with very large files such as image files. In any case, if you can add more RAM to the computer, I highly recommend that you do it.

The partition type should be '82'. Linux partitions meant for filesystems are type '83'. As Flash sort of points out, they need not be formatted with any filesystem at all. Instead of being formatted as a filesystem, they are formatted as swap space using the 'mkswap' command -which basically just divides the partition into 4K 'pages'.

For over 5 years I've run various Puppys exclusively from multisession DVDs. Currently my computer has 4 GB of RAM, but for the first few years after I started using Puppy my computer had first 256 MB then 512 MB of RAM, and no hard disk drive, thus no swap memory. Puppy never ran out of RAM in that computer except once, when I tried to install OpenOffice. That's what I based my statement on.

bark_bark_bark wrote:

there is a special type of format for swaps partitions. But don't use a swap on:

Actually using flash memory for swap is reported to work well. Even Windows uses it.
Flash drive controllers spread the writes around so that the "wear" is not concentrated in one area. Writing to a flash memory is what "wears" it out, but it takes 100,000 to 1,000,000 writes before errors begin to creep in. That would be many years for most applications. Even then, error correction codes are used so that no data is lost as long as only a few errors occur.

That probably won't do it. Run a search on caches in /root and everything is still there. Try RamBack and Memory Restart...you can monitor and clear it easily.

Actually, that does drive the crud out of the RAM (which is the problem). FF (or something related to FF) loads up the RAM to just under 1GB, that operation will usually push the used RAM down to 3-400 MB.

I added in some of the tools you recommended, and it seems to behave a little better. Still effectively overflowed once (the one widget shows RAM usage -- and that time it was at 600MB), but I was pushing it pretty hard (lots of open tabs).

Once place where it regularly clogs up is Facebook (and it will generally load up there, with only 1 or 2 tabs open -- I'll see how the add-ons help).

For reference, I just opened FF, and went straight into Murga. I have 2 tabs open, and the FF monitoring plug-in is showing between 140 and 150 MB used for FF.

That behavior really cramps a low RAM machine.

Edit: Now that's interesting. The FF monitoring too is showing 140MB, but top shows VSZ as 448M (47% of RAM).

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum