Re: fsck and async mode

Moshe Zadka wrote: > On Sun, 7 May 2000, Omer wrote: > > > (define linux > > (lambda question t)) > > hm. > > Didn't you mean > > (define linux > (lambda question #t)) > > ? > > "t" is just a symbol like any other, while #t is the "canonical truth > value" Wrong - in R4RS t is #t and

Re: fsck and async mode

On Sun, 7 May 2000, Omer wrote: > (define linux > (lambda question t)) hm. Didn't you mean (define linux (lambda question #t)) ? "t" is just a symbol like any other, while #t is the "canonical truth value" -- Moshe Zadka <[EMAIL PROTECTED]> http://www.oreilly.com/news/prescod_030

Re: fsck and async mode

On Sun, May 07, 2000 at 12:32:18AM +0300, Omer wrote: > :>>Adi once suggested printing a T-shirt with the following: > :>>LILO boot: linux init=/usr/bin/emacs > :>> The Return of the LISP Machines Seriously though

Re: fsck and async mode

On Fri, 5 May 2000, Moshe Zadka wrote: :On Thu, 4 May 2000, Adi Stav wrote: : :>>Adi once suggested printing a T-shirt with the following: :>>LILO boot: linux init=/usr/bin/emacs :>> The Return of the LISP Machines

Re: fsck and async mode

On Thu, 4 May 2000, Adi Stav wrote: > >Adi once suggested printing a T-shirt with the following: > >LILO boot: linux init=/usr/bin/emacs > > The Return of the LISP Machines > That was Moshe Zadka, not me...

Re: fsck and async mode

>Adi once suggested printing a T-shirt with the following: > >LILO boot: linux init=/usr/bin/emacs > The Return of the LISP Machines

Re: fsck and async mode

Adi once suggested printing a T-shirt with the following: LILO boot: linux init=/usr/bin/emacs The Return of the LISP Machines Anyone still interested? ;-) -- Alex Shnitman| http://www.debian.org [EMAIL PROTECTED], [EMAIL PROTECTED] +--- htt

Re: fsck and async mode

"Stanislav Malyshev a.k.a Frodo" <[EMAIL PROTECTED]> writes: > OG>> Is this an allusion to lisp? It is compiled now. Actually, I am > > As I see, most interpreted languages become more or less "compiled" > as they develop... Most non-interpreted languages are now dead, aren't they? ;-) Well,

Re: fsck and async mode

OG>> Is this an allusion to lisp? It is compiled now. Actually, I am As I see, most interpreted languages become more or less "compiled" as they develop... -- [EMAIL PROTECTED] \/ There shall be counsels taken Stanislav Malyshev /\ Stronger than Morgul-spells phone +972-3-9316425

Re: fsck and async mode

Chen Shapira <[EMAIL PROTECTED]> writes: > Speaking of which - if anyone has any clue on how to find a lispmachine, > lispmachine cards or lispmachine parts - I'll be very gratefull for those. A couple of years ago (well, maybe 3) I recall noticing an offer of Lisp Machines complete with monitor

Re: fsck and async mode

Omer Mussaev <[EMAIL PROTECTED]> writes: > Interpreted Languages will win Is this an allusion to lisp? It is compiled now. Actually, I am not sure it was compilable when Lisp Machines were used - will try to ask. But running a Lisp Machine on a modern Lisp base could be fun. I know, I know, it

Re: JFS is bad ( was: Re: fsck and async mode)

rought reiserfs mailing list archive. This question is asked a lot there. - Original Message - From: Mike Almogy <[EMAIL PROTECTED]> To: Ury Segal <[EMAIL PROTECTED]> Cc: Linux-il <[EMAIL PROTECTED]> Sent: Tuesday, May 02, 2000 4:59 PM Subject: Re: JFS is bad ( was: Re: fsck a

Re: JFS is bad ( was: Re: fsck and async mode)

On Tue, 2 May 2000, Mike Almogy wrote: > Hi. > But if i want to use it in order to make my proxy server faster, will it > still have problems ? like Ury said, it's an NFS problem, and what he describes sounds too close to a bug I had with ex2 and NFS with sun machines mounting, it may be an nfsd

Re: JFS is bad ( was: Re: fsck and async mode)

later" - Original Message - From: "Ury Segal" <[EMAIL PROTECTED]> To: "Evgeny Zemlerub" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, May 02, 2000 5:17 PM Subject: JFS is bad ( was: Re: fsck and async mode) > Evgen

Re: JFS is bad ( was: Re: fsck and async mode)

Yep, kind of forgot about this one (I have read about it on mailinig list of reiserfs). But if you don't use NFS you are pretty safe (at least i am till now) > > I am sorry to tell you that ReiserFS have horrible bugs > in the caching mechanism. It occur when you remove > a file, and then re-c

JFS is bad ( was: Re: fsck and async mode)

Evgeny Zemlerub wrote: > > > > crash) > > > > > > Sure! > > > You can use ReiserFS (or other journaling file systems like XFS or > EXT3) - I am sorry to tell you that ReiserFS have horrible bugs in the caching mechanism. It occur when you remove a file, and then re-create a file with the same na

Re: fsck and async mode

Chen Shapira wrote: > > Is there a way to fasten the fsck check ? > > I have proxy with 9 GB disk and it takes forever to start it > > You can use ReiserFS (or other journaling file systems like XFS or EXT3) - > they boot and fsck really fast. ReiserFS does require a kernel patch but works quit

Re: fsck and async mode

> > > crash) > > > > Sure! > > You can use ReiserFS (or other journaling file systems like XFS or EXT3) - > > they boot and fsck really fast. > > I think it requires a kernel patch, but I'm not sure. You can find alot of > > documentation on the web. > > > > jfs. I belive that jfs and xfs are in

Re: fsck and async mode

Chen Shapira wrote: > > Is there a way to fasten the fsck check ? > > I have proxy with 9 GB disk and it takes forever to start it > > up. (after a > > crash) > > Sure! > You can use ReiserFS (or other journaling file systems like XFS or EXT3) - > they boot and fsck really fast. > I think it requ

RE: fsck and async mode

> Is there a way to fasten the fsck check ? > I have proxy with 9 GB disk and it takes forever to start it > up. (after a > crash) Sure! You can use ReiserFS (or other journaling file systems like XFS or EXT3) - they boot and fsck really fast. I think it requires a kernel patch, but I'm not sur