On Tue, 2008-11-04 at 20:42 -0600, Lukasz Szybalski wrote:
> On Tue, Nov 4, 2008 at 7:10 PM, Jeff Kalchik <[EMAIL PROTECTED]> wrote:
> >>> I'm talking about opening a terminal on local /home with few folders
> >>> which have few hounded gb in them.
> >>> I'm not connection to anything at that point
On Tue, Nov 4, 2008 at 7:10 PM, Jeff Kalchik <[EMAIL PROTECTED]> wrote:
>>> I'm talking about opening a terminal on local /home with few folders
>>> which have few hounded gb in them.
>>> I'm not connection to anything at that point. I'm talking about
>>> opening a nautilus browser and that takes 2
On Tue, Nov 4, 2008 at 8:10 PM, Jeff Kalchik <[EMAIL PROTECTED]> wrote:
>>> I'm talking about opening a terminal on local /home with few folders
>>> which have few hounded gb in them.
>>> I'm not connection to anything at that point. I'm talking about
>>> opening a nautilus browser and that takes 2
>> I'm talking about opening a terminal on local /home with few folders
>> which have few hounded gb in them.
>> I'm not connection to anything at that point. I'm talking about
>> opening a nautilus browser and that takes 2 seconds.
>> Not sure what ldap, windbind or nscd have to do with file syste
> I'm talking about opening a terminal on local /home with few folders
> which have few hounded gb in them.
> I'm not connection to anything at that point. I'm talking about
> opening a nautilus browser and that takes 2 seconds.
> Not sure what ldap, windbind or nscd have to do with file system
> a
I'm talking about opening a terminal on local /home with few folders
which have few hounded gb in them.
I'm not connection to anything at that point. I'm talking about
opening a nautilus browser and that takes 2 seconds.
Not sure what ldap, windbind or nscd have to do with file system
access time?
