Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread David E. Cross
Ok... I have *had* it with the meta, but not really, lockd. Are there any kernel issues with correctly implimenting rpc.lockd?How can I take a filehandle and map it into a filename, with path, so I may open it and lock it on the server? Are there any protocol specs? I downloaded the RFC for

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-28 Thread Doug Barton
Alfred Perlstein wrote: > > On Mon, 22 Nov 1999, David E. Cross wrote: > > > Ok... I have *had* it with the meta, but not really, lockd. Are there any > > kernel issues with correctly implimenting rpc.lockd? I can't help with the code, but put me down as both very interested, and wi

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-29 Thread Conrad Minshall
At 1:36 PM -0800 11/25/99, C. Stephen Gunn wrote: >On Mon, Nov 22, 1999 at 02:07:58PM -0800, Alfred Perlstein wrote: >> > Does NetBSD have a working rpc.lockd... that would make this much easier. >> >> at a glance at http://cvsweb.netbsd.org/... no. >I'm fairly certain that rpc.lockd is included

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-29 Thread David E. Cross
Well, I am starting to get pretty seriously involved. It looks pretty easy, just a lot of small details (this is the kind of coding I like :) A couple of issues need to be worked out. First I need to backport the FH open/stat/etc. calls to -STABLE. The main reason for this is that I am devel

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-29 Thread Matthew Dillon
:Well, I am starting to get pretty seriously involved. It looks pretty :easy, just a lot of small details (this is the kind of coding I like :) : :A couple of issues need to be worked out. First I need to backport :the FH open/stat/etc. calls to -STABLE. The main reason for this is that :...

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-29 Thread Matthew Dillon
:I can't help with the code either - what little time I have available :is going towards the SMP project. I will be shorting beginning work ^ shortly.

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-29 Thread Dan Moschuk
| >I'm fairly certain that rpc.lockd is included with Darwin from Apple, | >I've not closely compared it to what we have in -STABLE or -CURRENT | >to see if it actually works. | | It doesn't, sorry... if someone gets a *BSD version of NFS locking operating | I'd help see it into Darwin. | | BT

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-30 Thread Doug Rabson
On Mon, 29 Nov 1999, Dan Moschuk wrote: > > | >I'm fairly certain that rpc.lockd is included with Darwin from Apple, > | >I've not closely compared it to what we have in -STABLE or -CURRENT > | >to see if it actually works. > | > | It doesn't, sorry... if someone gets a *BSD version of NFS loc

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-30 Thread Dan Moschuk
| I reviewed the NFSv4 specs recently and came to the same conclusion. To do | it right will be quite a bit of work and would include a decent kernel | side implementation of rpc and gssapi. Cool! I can take that "I volunteer" ? :-) -- Dan Moschuk ([EMAIL PROTECTED]) "Cure for global warming:

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-30 Thread Doug Rabson
On Tue, 30 Nov 1999, Dan Moschuk wrote: > > | I reviewed the NFSv4 specs recently and came to the same conclusion. To do > | it right will be quite a bit of work and would include a decent kernel > | side implementation of rpc and gssapi. > > Cool! I can take that "I volunteer" ? :-) Not wit

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, David E. Cross wrote: > Ok... I have *had* it with the meta, but not really, lockd. Are there any > kernel issues with correctly implimenting rpc.lockd?How can I take a > filehandle and map it into a filename, with path, so I may open it and lock > it on the server? Are

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread Ronald G. Minnich
Actually I wrote a system call for opening a file given a file handle for freebsd a while back (oh, gee, has it really been 5 years ...), as part of mnfs i'll try to find it. You don't need to map it to a filename to make it go. ron To Unsubscribe: send mail to [EMAIL PROTECTED] with "un

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, Ronald G. Minnich wrote: > Actually I wrote a system call for opening a file given a file handle for > freebsd a while back (oh, gee, has it really been 5 years ...), as part of > mnfs i'll try to find it. You don't need to map it to a filename to > make it go. i forgot

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread David E. Cross
Does NetBSD have a working rpc.lockd... that would make this much easier. -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread Alfred Perlstein
On Mon, 22 Nov 1999, David E. Cross wrote: > Does NetBSD have a working rpc.lockd... that would make this much easier. at a glance at http://cvsweb.netbsd.org/... no. Linux may have one, a temporary GPL'd port would be interesting perhaps. -Alfred To Unsubscribe: send mail to [EMAIL PROTEC

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-22 Thread David E. Cross
> Linux may have one, a temporary GPL'd port would be interesting perhaps. "There is nothing as permanent as a temporary decision." No thanks :) -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrat

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-23 Thread Warner Losh
In message <[EMAIL PROTECTED]> "David E. Cross" writes: : Ok... I have *had* it with the meta, but not really, lockd. Are there any : kernel issues with correctly implimenting rpc.lockd?How can I take a : filehandle and map it into a filename, with path, so I may open it and lock : it on the

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-23 Thread Matthew Jacob
> : Ok... I have *had* it with the meta, but not really, lockd. Are there any > : kernel issues with correctly implimenting rpc.lockd?How can I take a > : filehandle and map it into a filename, with path, so I may open it and lock > : it on the server? Are there any protocol specs? I downl

Re: Ok, that's it, enough is enough! (rpc.lockd)

1999-11-26 Thread C. Stephen Gunn
On Mon, Nov 22, 1999 at 02:07:58PM -0800, Alfred Perlstein wrote: > On Mon, 22 Nov 1999, David E. Cross wrote: > > > Does NetBSD have a working rpc.lockd... that would make this much easier. > > at a glance at http://cvsweb.netbsd.org/... no. > > Linux may have one, a temporary GPL'd port wou