View Single Post
Old 06-29-2012, 08:07 AM   #17
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by knc1 View Post
Or you have problems making your chroot'd system work.
The people who are not interested are free to ignore the details.
(Like the people who ignore our indexed content.)
MY chrooted system worked fine on my K3 (including my tmpFS mounts). What does simply defining a RAMdisk as "files stored in directories that exist in RAM" have to do with "problems making YOUR chroot'd system work"? I can't find mention of chroot anywhere in the previous posts in this thread. In my experience, files stored in /tmp/ ARE stored in RAM (without delving into deep technical implementation details). I am more than a little confused about what your recent posts have to do with this thread.

Last edited by geekmaster; 06-29-2012 at 08:29 AM.
geekmaster is offline   Reply With Quote