On Mon, 17 Dec 2012 22:43:36 +0100 Joerg Sonnenberger <jo...@britannica.bec.de> said:
> On Mon, Dec 17, 2012 at 07:10:01PM -0200, Gustavo Sverzut Barbieri wrote: > > Jokes aside, we appreciate to have E to run well on that, but it > > cannot block development because features that is in the standard for > > 12 years without being implemented. > > First of all, shm_open is an optional part of POSIX. One of the reasons > for reluctantly implementing it is that it is extremely lame. The way > Linux implements it provides ~0 advantage of just using open() with a > file in /tmp. that is total BUNK. a file in /tmp quite possibly lives ON DISK. it SURIVIES REBOOTS... and it will get SYNCED TO DISK WHEN THE FS WANTS TO... an shm file only hits disk when you need to swap- like any ram you may malloc(). UNLESS /tmp happens by luck to be a ramdisk (tmpfs). so no. it's far from lame. it's EXACTLY what is needed. if shm_open HAPPENS to just simply know that this is the os setup and then use /tmp = fine... but then this is a detail each and every app doesn't have to be configured separately for or go figure out. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel