Quote:
Originally Posted by ThomasT
The same problems with apt-get as described above, including a heavily bricked K5, happend to me, too.
After replacing
Code:
mount -o loop -t ext3 /mnt/us/debian.ext3 /mnt/debian
by
Code:
mount -o loop -t ext3 /mnt/base-us/debian.ext3 /mnt/debian
everything works fine.
This avoids file transfers through that strange mount loop on /mnt/us. RAM monitoring with
shows always more than 6 MB free RAM.
As I don`t understand that strange /mnt/us loop, I don`t know, whether this is save. Up to now it works.
BTW: I have no swap file/partition. Debian version is testing. /etc/issues says wheezy/sid. |
That is strange, but interesting. I and others have experienced locked up kindles when using loop mounts on /mnt/us. But I thought we were supposed to avoid using /mnt/base-us/.
Can somebody please explain the difference between /mnt/us and /mnt/base-us, and when we should use which one, and why the startup scripts generally use /mnt/us?
Is there a reason why a loop mount would hang on /mnt/us but work on /mnt/base-us, or is that just coincidental here?
Thanks.