cbagger01
Group: Members
Posts: 4264
Joined: Oct. 2003 |
|
Posted: July 06 2006,04:10 |
|
The more I think of it, the whole
/var/tmp -----> /tmp
link should not become the standard mode of operation, and instead should only be used as a temporary workaround until the broken extensions are fixed. (That is, assuming that it even WORKS. Still haven't tried it yet).
Why?
Because extensions should never have "tarred" filename paths that begin with /ramdisk/tmp/xxx or /var/tmp/xxx
These bad extensions would also be problematic when someone tries to use them with a traditional hard disk installation instead of a livecd configuration because with a hard drive based filesystem, /tmp is neither located at /ramdisk/tmp nor at /var/tmp
So the right thing to do is identify the "broken" extensions and request that the contributors fix them.
On a positive note, any extensions created with "deb2dsl" should not suffer from the /var/tmp or /ramdisk/tmp problem.
|