On Thu, Jan 15, 2009 at 2:03 PM, Scott James Remnant <email address hidden>wrote:
> Actually, I believe you're mistaking tmpfs with ramfs here. Space is
> not reserved for a tmpfs, it simply sets the maximum size to which the
> tmpfs may grow.
>
> If a tmpfs is only using 5MB, then it will only consume 5MB of memory;
> it's backed by the page cache, so there is little overhead for such
> things as filesystem (in fact, there isn't one!)
>
I know that
>
>
> /dev is not writable by ordinary users, there is no danger of users
> filling this filesystem with other data.
>
> However there it is preferred that this filesystem "not become full", if
> the udev daemon is unable to make device nodes, or maintain its
> database, then system features such as hotplug fail to work and newly
> connected devices are not available.
>
I tottaly agree with you
>
> It is for this reason that we choose not to limit the size of the
> filesystem.
>
I think that you misunderstood me, I'm not suggesting to limit the size, I'm
suggesting to allow people if they want, they can limit the size. Currently
on ubuntu, I can do this on /dev/shm, /var/lock, /var/run, /lib/init/rw [1],
but I can't on /dev
The default behavior of my patch is to do nothing because the default
contents of /etc/default/tmpfs on my ubuntu is to not limit size. So the
patch only add support to allow people to choose the size, the patch is not
imposing the size.
IMHO I think that allowing people to choose the max size a good thing, but,
anyway, the final decision is yours, and I will respect it.
Thank you for your feedback
[1] see the contents of /etc/init.d/mountkernfs.sh,
/etc/init.d/mountdevsubfs.sh, /etc/init.d/mtab.sh
--
Iuri Diniz http://iuridiniz.com [Sou um agitador, não um advogado] http://blog.igdium.com [Linux on Limbo]
Hello Scott,
On Thu, Jan 15, 2009 at 2:03 PM, Scott James Remnant <email address hidden>wrote:
> Actually, I believe you're mistaking tmpfs with ramfs here. Space is
> not reserved for a tmpfs, it simply sets the maximum size to which the
> tmpfs may grow.
>
> If a tmpfs is only using 5MB, then it will only consume 5MB of memory;
> it's backed by the page cache, so there is little overhead for such
> things as filesystem (in fact, there isn't one!)
>
I know that
>
>
> /dev is not writable by ordinary users, there is no danger of users
> filling this filesystem with other data.
>
> However there it is preferred that this filesystem "not become full", if
> the udev daemon is unable to make device nodes, or maintain its
> database, then system features such as hotplug fail to work and newly
> connected devices are not available.
>
I tottaly agree with you
>
> It is for this reason that we choose not to limit the size of the
> filesystem.
>
I think that you misunderstood me, I'm not suggesting to limit the size, I'm
suggesting to allow people if they want, they can limit the size. Currently
on ubuntu, I can do this on /dev/shm, /var/lock, /var/run, /lib/init/rw [1],
but I can't on /dev
The default behavior of my patch is to do nothing because the default
contents of /etc/default/tmpfs on my ubuntu is to not limit size. So the
patch only add support to allow people to choose the size, the patch is not
imposing the size.
IMHO I think that allowing people to choose the max size a good thing, but,
anyway, the final decision is yours, and I will respect it.
Thank you for your feedback
[1] see the contents of /etc/init. d/mountkernfs. sh, d/mountdevsubfs .sh, /etc/init.d/mtab.sh iuridiniz. com [Sou um agitador, não um advogado] blog.igdium. com [Linux on Limbo]
/etc/init.
--
Iuri Diniz
http://
http://