> -----Original Message-----
> From: Igor Pechtchanski
[snip]
>
> On Mon, 16 May 2005, Gary R. Van Sickle wrote:
>
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED] On Behalf Of fergus
>
> Tut-tut... <http://cygwin.com/acronyms/#PCYMTNQREAIYR>...
>
...? I was under the impression that cygwin{}@'s weren't an issue; if
they're harvesting from the list, they already have it anyway, right?
[snip]
> > > (And what is the consequence for memory usage when the virtual
> > > directories /usr/bin/ and /usr/lib/ are created on startup?)
> >
> > This I do: Those are just mount table entries. Memory usage won't
> > change regardless of the number or size of files in the directory a
> > Cygwin mount table entry points to. So there's no
> consequence there.
>
> True for the actual disk space usage. However, if "du -s" is
> used from the root, it will traverse both "/bin" and
> "/usr/bin", and add up the numbers (so you get the size of
> /bin counted twice, same for /lib).
> Igor
Well, right, but he asked about memory (i.e. RAM) usage.
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
