fstab

On Thursday 08 June 2006 23:42, Unruh stood up and spoke the following words to the mbuttes incomp.os.linux.misc...:

Thecramfsis a compressed read-only filesystem, mainly used in embedded systems. Here's theWikipediaexplanation on it...:

"The compressed ROM filesystem (or cramfs) is a Free (GPL'ed) read-only Linux file system designed for simplicity and space-efficiency. It is mainly used in embedded systems and small-footprint systems.

Unlike a compressed image of a conventional filesystem, a cramfs image does not have to be uncompressed first and can be used as-is, compressed. For this reason, some Linux distributions also appear to use cramfs as a file system for initial ramdisks (initrd) (recent versions of Debian in particular) and installation images (SuSE in particular), where there are onerous constraints on memory and image size."

From what it appears, those lines are leftovers from an install. Presumably *-tmp-app-$NUMBER-image* is such a filesystem and gets mounted on *-tmp-app-$NUMBER.*

Normally, according to the Filesystem Hierarchy Standard, nothing in *-tmp* should remain there after a reboot.

My advice here would be to runfuseron these mounted filesystems - the entries in *-etc-fstab* define them as user-mountable and not automatically mounted on boot - and if it turns out they are not needed, remove them by doing the following...

# Open up a commandline terminal and become root... su

# Drop to single-user mode... shutdown now

# Remove all that's in *-tmp* ... cdtmp rm -rf *

# Return to normal operation - subsbreastute 3 by 5 if the system # must boot to a GUI login screen... init 3

Hope this helps... ;-)

-- With kind regards,

*Aragorn* (Registered GNU-Linux user #223157)