While I understand this to be a desire of many who use the browsers in
this manner, I don't understand "why" this is. The browser was never
designed to do such a thing. Why would one want it to? Why not just kill
the browser now and then, dump the cache and restart the browser. Since
linux memory management is already good enough to handle running
non-stop without trouble it would appear that users, rather then the
software would have to make an adjustment here.
Mark
Bill Barnes wrote:
>
> Well, part of the rush is for what is hoped to be an
> acceptable browser.
>
> Opera, Netscape6, Netscape 4.76 inevitably crash about
> the time you get a decent mix of websites up. I
> expect the browser to be up 24/7. Maybe Konqueror
> Final can do this.
>
> -Bill
>
> --- Mark Weaver <[EMAIL PROTECTED]> wrote:
> > All in good time. what's the rush?
> >
> > --
> > Mark
> >
> > "If you don't share your concepts and ideals, they
> > end up being worthless,"
> > "Sharing is what makes them powerful."
> >
> >
> > On Tue, 27 Feb 2001, Ron Stodden wrote:
> >
> > > Date: Tue, 27 Feb 2001 13:33:42 +1100
> > > From: Ron Stodden <[EMAIL PROTECTED]>
> > > Reply-To: [EMAIL PROTECTED]
> > > To: Mandrake Expert <[EMAIL PROTECTED]>
> > > Subject: [expert] KDE 2.1 final
> > >
> > > KDE 2.1 final in binary form for the various
> > distributions was
> > > promised on the KDE site by Monday February 26.
> > >
> > > It is now 3.5 hours into Tuesday GMT and there is
> > no sign of the KDE
> > > 2.1 final update to Mandrake 7.2.
> > >
> > > Where is it? What is happening? When and where
> > will it appear?
> > >
> > >
> >
> >
>
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
