RE: [Devil-linux-develop] 1.0RC1 - Notes from installation.

[Dean N. <di...@ti...>]

>> >Then you're probably willing to do some research on this:
>> >Can you check if it is possible to resize the shmfs ?
>> >The problem is that we can't umount it, because when you do that, it's
>> >automatically emptied. :-((
>>
>> I'll see what I can find out...
>
>See if the mount -oremount option works without emptying it.
></guess>

Well, according to the research I've done so far - tmpfs (which is listed as
the shmfs replacement?) does allow the remount option to change the size on
the fly.  However, it also states that space used by the tmpfs is NOT
eligible for reclamation by the Out-Of-Memory recovery procedures.  And yes,
mount -o remount, size= does work.

On a side issue, I took a look at what was using the space (remember - this
is -with- Postfix, and -without- SAGATOR and ClamAV at this point).  Here is
the -brief- results:
Total Space: 30MB
Total Space Used: 20MB
Amount used by Postfix: 16MB
Amount used by Postfix's lib directory (/var/spool/postfix/lib): 14MB

So to me, this brings up an obvious question:
How come most of these "jails" can't be prebuilt and reside on the CDROM?
It seems to me that there are there "types" of files, and that some of these
could be built and reside on the CDROM:
o Files copied from /etc.  These can't be on the CDROM, because they didn't
come from the CDROM :-)
o Files from /lib, /usr, /dev, /bin, etc.  These could certainly be prebuilt
and reside on the CDROM.
o Files that are created dynamically.  Normally these are created by the
application.

Just my thoughts.

Dean Nedelman
TimeLord Consulting