Re: NetWare client in -current

1999-09-13 Thread Dominic Mitchell

On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
 Growing up programming on a KL-10, I still think the correct place for
 line-editing is in the driver.  Hell - it's already doing basic
 erase/kill line editing as it is.  Then you don't have to hack every
 command-line app to get line-editing.

Yeah, but how do you specify completion then?

Unix went here a long time ago and backed out of it.  Have a look at the
paper http://www.cs.princeton.edu/~jlk/kornshell/doc/vhll.ps.gz (linked
from www.kornshell.com) in particular, the history section.
-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

"vi has two modes the one in which it beeps and the one in which it doesnt."
-- Anon.


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-13 Thread Dominic Mitchell
On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
 Growing up programming on a KL-10, I still think the correct place for
 line-editing is in the driver.  Hell - it's already doing basic
 erase/kill line editing as it is.  Then you don't have to hack every
 command-line app to get line-editing.

Yeah, but how do you specify completion then?

Unix went here a long time ago and backed out of it.  Have a look at the
paper http://www.cs.princeton.edu/~jlk/kornshell/doc/vhll.ps.gz (linked
from www.kornshell.com) in particular, the history section.
-- 
Dom Mitchell -- Palmer  Harvey McLane -- Unix Systems Administrator

vi has two modes the one in which it beeps and the one in which it doesnt.
-- Anon.


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-13 Thread Matthew Jacob


 On Fri, Sep 10, 1999 at 11:15:12AM -0700, Parag Patel wrote:
  Growing up programming on a KL-10, I still think the correct place for
  line-editing is in the driver.  Hell - it's already doing basic
  erase/kill line editing as it is.  Then you don't have to hack every
  command-line app to get line-editing.

Yeah, and this is why VMS 4.X (early) had a terrific security bug- if you
type '#' (or was it '') as the first character after you logged in, your
accounting records for that session were wiped.

No, a driver is *not* the place to put this kind of fooling around.




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



RE: NetWare client in -current

1999-09-10 Thread Daniel O'Connor


On 10-Sep-99 Boris Popov wrote:
   mount_nwfs  - similar to mount_nfs
   ncplogin- creates permanent connection to a NetWare server
 without an actual mount, 
   ncplogout   - destroy permanent connection,
   ncplist - displays various information about client itself
 and NetWare servers,
   ncprint - allows to send job to NetWare printer,
   ncpsend - sends message to NetWare user or server console,
   ncplpd  - simple NetWare print server,
   ncpurge - purge specified salvagable files,
   ncpsvc  - remote control for a NetWare server,
   ncpasswd- allows to change password for a NetWare user.

Is there any reason to not have it as a port?

The only possible candidate for contrib'ifying I could see would be mount_nwfs
because building it without the kernel source could be a problem, but the rest
of it could be a port I think :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum

 PGP signature


Re: NetWare client in -current

1999-09-10 Thread Ruslan Ermilov

On Fri, Sep 10, 1999 at 06:29:57PM +0930, Daniel O'Connor wrote:
 
 On 10-Sep-99 Boris Popov wrote:
mount_nwfs  - similar to mount_nfs
ncplogin- creates permanent connection to a NetWare server
  without an actual mount, 
ncplogout   - destroy permanent connection,
ncplist - displays various information about client itself
  and NetWare servers,
ncprint - allows to send job to NetWare printer,
ncpsend - sends message to NetWare user or server console,
ncplpd  - simple NetWare print server,
ncpurge - purge specified salvagable files,
ncpsvc  - remote control for a NetWare server,
ncpasswd- allows to change password for a NetWare user.
 
 Is there any reason to not have it as a port?
 
IMHO, only the basic IPX/SPX functionality should be included into the
source tree.  Anything else could be available as ports/net/nw-utils.

-- 
Ruslan Ermilov  Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.247.647Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



RE: NetWare client in -current

1999-09-10 Thread Boris Popov

On Fri, 10 Sep 1999, Daniel O'Connor wrote:

 Is there any reason to not have it as a port?
 
 The only possible candidate for contrib'ifying I could see would be mount_nwfs
 because building it without the kernel source could be a problem, but the rest
 of it could be a port I think :)

Yes, that's acceptable. But mount_nwfs require libncp.so and this 
means that ncp library sources will be also required. So KLD, mount_nwfs
and libncp should go into source tree and other utilities can be a port.

Other thoughts ?

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov

On Fri, 10 Sep 1999, Ruslan Ermilov wrote:

  Is there any reason to not have it as a port?
  
 IMHO, only the basic IPX/SPX functionality should be included into the
 source tree.  Anything else could be available as ports/net/nw-utils.

An IPX/SPX stack is already in the tree and past year made it more
or less functional.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov

On Fri, 10 Sep 1999, Ruslan Ermilov wrote:

  An IPX/SPX stack is already in the tree and past year made it more
  or less functional.
  
 Read: I fully agree with Daniel.

Daniel also left mount_nwfs :)
 
 Forgive me my ignorance, but I'd like a quick response: what about multiple
 ethernet frames for IPX?  Is it supported in -current?  In -stable?

There is an if_ef driver which supports all four ethernet frames
for IPX protocol and can be easily adapted for others (see
http://www.butya.kz/~bp/ipxen.html for details).  It requires two simple
patches to sys/net/if.c file and work on both -current and -stable.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Ruslan Ermilov

On Fri, Sep 10, 1999 at 05:24:00PM +0700, Boris Popov wrote:
 On Fri, 10 Sep 1999, Ruslan Ermilov wrote:
 
 An IPX/SPX stack is already in the tree and past year made it more
   or less functional.
   
  Read: I fully agree with Daniel.
 
   Daniel also left mount_nwfs :)
 
All kernel-related staff (protocol, file-system support and required libraries)
should be available in the tree.  Everything else as a port(s).

  Forgive me my ignorance, but I'd like a quick response: what about multiple
  ethernet frames for IPX?  Is it supported in -current?  In -stable?
 
   There is an if_ef driver which supports all four ethernet frames
 for IPX protocol and can be easily adapted for others (see
 http://www.butya.kz/~bp/ipxen.html for details).  It requires two simple
 patches to sys/net/if.c file and work on both -current and -stable.
 
That's really cool, good job!


-- 
Ruslan Ermilov  Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.247.647Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Peter Wemm

Boris Popov wrote:
 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be mount_n
wfs
  because building it without the kernel source could be a problem, but the r
est
  of it could be a port I think :)
 
   Yes, that's acceptable. But mount_nwfs require libncp.so and this 
 means that ncp library sources will be also required. So KLD, mount_nwfs
 and libncp should go into source tree and other utilities can be a port.
 
   Other thoughts ?

I'm really not sure I see the value in splitting it up like that.. Are
things like ncplogin required to support mount_nwfs?  Personally, I think
it might be better to take the whole lot and later on (nearer 4.0 time)
decide if it's worth splitting the ncp* off to a port if it's worth doing.
Otherwise version skew is going to be a hassle while it's under
development.

Cheers,
-Peter




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov

On Fri, 10 Sep 1999, Peter Wemm wrote:

  Yes, that's acceptable. But mount_nwfs require libncp.so and this 
  means that ncp library sources will be also required. So KLD, mount_nwfs
  and libncp should go into source tree and other utilities can be a port.
  
  Other thoughts ?
 
 I'm really not sure I see the value in splitting it up like that.. Are
 things like ncplogin required to support mount_nwfs?  Personally, I think
 it might be better to take the whole lot and later on (nearer 4.0 time)
 decide if it's worth splitting the ncp* off to a port if it's worth doing.
 Otherwise version skew is going to be a hassle while it's under
 development.

Thats why I suggested an original scheme...

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Marcel Moolenaar

Boris Popov wrote:

 Currently I'm trying to determine a reasonable set of NetWare
 utilities which should be included in the source tree.

Is it possible to have utilities to query and modify NDS?

 ncpurge - purge specified salvagable files,

From a user perspective, is salvaging not also important?

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking  Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



RE: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd

On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 On 10-Sep-99 Boris Popov wrote:
mount_nwfs  - similar to mount_nfs
ncplogin- creates permanent connection to a NetWare server
  without an actual mount, 
ncplogout   - destroy permanent connection,
ncplist - displays various information about client itself
  and NetWare servers,
ncprint - allows to send job to NetWare printer,
ncpsend - sends message to NetWare user or server console,
ncplpd  - simple NetWare print server,
ncpurge - purge specified salvagable files,
ncpsvc  - remote control for a NetWare server,
ncpasswd- allows to change password for a NetWare user.
 
 Is there any reason to not have it as a port?
 
 The only possible candidate for contrib'ifying I could see would be
 mount_nwfs because building it without the kernel source could be a
 problem, but the rest of it could be a port I think :)

Thats like suggesting we make the 'ipfw' command a port and leave the
kernel bits in the tree.  Since all this stuff depends on being in sync,
the only reasonable way to do this is to put it in the tree.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Peter Wemm

"Matthew N. Dodd" wrote:
 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
  On 10-Sep-99 Boris Popov wrote:
 mount_nwfs  - similar to mount_nfs
 ncplogin- creates permanent connection to a NetWare server
   without an actual mount, 
 ncplogout   - destroy permanent connection,
 ncplist - displays various information about client itself
   and NetWare servers,
 ncprint - allows to send job to NetWare printer,
 ncpsend - sends message to NetWare user or server console,
 ncplpd  - simple NetWare print server,
 ncpurge - purge specified salvagable files,
 ncpsvc  - remote control for a NetWare server,
 ncpasswd- allows to change password for a NetWare user.
  
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be
  mount_nwfs because building it without the kernel source could be a
  problem, but the rest of it could be a port I think :)
 
 Thats like suggesting we make the 'ipfw' command a port and leave the
 kernel bits in the tree.  Since all this stuff depends on being in sync,
 the only reasonable way to do this is to put it in the tree.

Or having mount_nfs in the base but moving nfsd/nfsiod/nfsstat to ports.
:-)

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov

On Fri, 10 Sep 1999, Marcel Moolenaar wrote:

  Currently I'm trying to determine a reasonable set of NetWare
  utilities which should be included in the source tree.
 
 Is it possible to have utilities to query and modify NDS?

I'm working on this (currently only queries). NDS library will be
separate package from ncplib.

 
  ncpurge - purge specified salvagable files,
 
 From a user perspective, is salvaging not also important?

Yes it is important, but requires dialogue with user because
there can be more than one deleted file with same name. I'm trying to get
Novell to respond on my query about source code for 'filer' utility but
they keeps quiet at the moment.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Mike Smith

 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be mount_nwfs
  because building it without the kernel source could be a problem, but the rest
  of it could be a port I think :)
 
   Yes, that's acceptable. But mount_nwfs require libncp.so and this 
 means that ncp library sources will be also required. So KLD, mount_nwfs
 and libncp should go into source tree and other utilities can be a port.

You could still build the KLD as a port, actually.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Daniel O'Connor



"Matthew N. Dodd" wrote:
  The only possible candidate for contrib'ifying I could see would be
  mount_nwfs because building it without the kernel source could be a
  problem, but the rest of it could be a port I think :)
 Thats like suggesting we make the 'ipfw' command a port and leave the
 kernel bits in the tree.  Since all this stuff depends on being in sync,
 the only reasonable way to do this is to put it in the tree.

Why? What kernel code does this need?

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd

On Sat, 11 Sep 1999, Daniel O'Connor wrote:
 "Matthew N. Dodd" wrote:
   The only possible candidate for contrib'ifying I could see would be
   mount_nwfs because building it without the kernel source could be a
   problem, but the rest of it could be a port I think :)
  Thats like suggesting we make the 'ipfw' command a port and leave the
  kernel bits in the tree.  Since all this stuff depends on being in sync,
  the only reasonable way to do this is to put it in the tree.
 
 Why? What kernel code does this need?

The ncpfs kernel code for one.

We're talking about less than 500k of code here.

You want to take the anti-bloatist stance you'll have to do better than
that.  Try libreadline for starters.  :)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Parag Patel


On Sat, 11 Sep 1999 03:08:40 +0930, "Daniel O'Connor" wrote:

"Matthew N. Dodd" wrote:
 You want to take the anti-bloatist stance you'll have to do better than
 that.  Try libreadline for starters.  :)

Bah like I care enough to care ;)

Yow!  I had no idea it was so large!

I have an (as yet still incomplete) full-screen text-editor library I
wrote a long time ago - in C++ even - that supports (on a terminal using
termlib but not curses) full-screen editing, simultaneous "live"
multiple overlapping windows/views of buffers, full left/right up/down
scrolling, line-numbering, unlimited undo/redo including any buffer
marks, regular-expression searching, and arbitrary depth key-bindings.

It's less than half the size of libreadline.

I am so depressed.


-- Parag Patel


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd

On Fri, 10 Sep 1999, Parag Patel wrote:
 I have an (as yet still incomplete) full-screen text-editor library I
 wrote a long time ago - in C++ even - that supports (on a terminal using
 termlib but not curses) full-screen editing, simultaneous "live"
 multiple overlapping windows/views of buffers, full left/right up/down
 scrolling, line-numbering, unlimited undo/redo including any buffer
 marks, regular-expression searching, and arbitrary depth key-bindings.
 
 It's less than half the size of libreadline.
 
 I am so depressed.

Clean it up and add perl bindings to it.  Thats something that perl sorely
misses.  Come to think of it, libedit could use perl bindings...  Hummm...

Kevin?  :)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Parag Patel

On Fri, 10 Sep 1999 14:07:12 EDT, "Matthew N. Dodd" wrote:

Clean it up and add perl bindings to it.  Thats something that perl sorely
misses.  Come to think of it, libedit could use perl bindings...  Hummm...

Gaah - another big line-editing library!  My editor's even smaller than
libedit!

   textdata bss dec hex filename
  601134352   0   64465fbd1 /usr/lib/libedit.so
 117406   140041464  132874   2070a /usr/lib/libreadline.so
  48843 6364492   53971d2d3 tst

I'll add my editing package to my things-to-clean-up list and make it
available when I next have some time.

I've never cared for perl tho'.  

Growing up programming on a KL-10, I still think the correct place for
line-editing is in the driver.  Hell - it's already doing basic
erase/kill line editing as it is.  Then you don't have to hack every
command-line app to get line-editing.


-- Parag Patel


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew Hunt

On Fri, Sep 10, 1999 at 02:07:12PM -0400, Matthew N. Dodd wrote:

 Clean it up and add perl bindings to it.  Thats something that perl sorely
 misses.  Come to think of it, libedit could use perl bindings...  Hummm...

/usr/ports/devel/p5-ReadLine-Gnu

Also /usr/ports/devel/p5-ReadLine-Perl, which is pure Perl, instead of
using an external library.

If you say "use Term::ReadLine", Perl will use either of those if
available, or use a useless dummy version that ships with Perl otherwise.

Bindings for libedit which are compatible with these would be cool.

-- 
Matthew Hunt [EMAIL PROTECTED] * UNIX is a lever for the
http://www.pobox.com/~mph/   * intellect. -J.R. Mashey


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Warner Losh

In message [EMAIL PROTECTED] "Daniel O'Connor" writes:
:  Thats like suggesting we make the 'ipfw' command a port and leave the
:  kernel bits in the tree.  Since all this stuff depends on being in sync,
:  the only reasonable way to do this is to put it in the tree.
: 
: Why? What kernel code does this need?

The IPFILTER kernel option.  ipfw just builds the IPFILTER kernel tables.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kevin Doherty

And thus spake Matthew N. Dodd, on Fri, Sep 10, 1999 at 02:07:12PM -0400:
 Clean it up and add perl bindings to it.  Thats something that perl sorely
 misses.  Come to think of it, libedit could use perl bindings...  Hummm...
 
 Kevin?  :)

Bleah, one thing at a time :)  Once I finish with my current project I'll
probably work on this if there's any interest, though.

--
Kevin Doherty, [EMAIL PROTECTED]
"Multiple exclamation marks are a sure sign of a diseased mind."
   -- Rincewind (from _Eric_)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd

On Fri, 10 Sep 1999, Kris Kennaway wrote:
 I tend to agree. If we bring in all of this stuff (even though I
 appreciate it's very useful) we should also bring in samba into the
 base tree by symmetry.

Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
import it into the tree the same as the Netware client stuff.

You were maybe talking about Samba, which doesn't have any kernel
components or userland tools that are dependent on them.

An in-kernel SMB/CIFS server would be on the same order as the NFS server
support; something we would want to have in the tree so as to keep an eye
on it and lower maintainence cost for the developer.  (Not that this has
kept the NFS server code free of interesting incidents.)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kris Kennaway

On Fri, 10 Sep 1999, Matthew N. Dodd wrote:

 On Fri, 10 Sep 1999, Kris Kennaway wrote:
  I tend to agree. If we bring in all of this stuff (even though I
  appreciate it's very useful) we should also bring in samba into the
  base tree by symmetry.
 
 Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
 import it into the tree the same as the Netware client stuff.

Okay. If that's the plan, then I don't have any objections.

I do hate the idea of having to reimplement samba because of the licensing
though - it already does quite a good job at SMB serving, it seems a waste
to duplicate the effort instead of just adding kernel support to the
existing code.

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd

On Fri, 10 Sep 1999, Kris Kennaway wrote:
  Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
  import it into the tree the same as the Netware client stuff.
 
 Okay. If that's the plan, then I don't have any objections.
 
 I do hate the idea of having to reimplement samba because of the licensing
 though - it already does quite a good job at SMB serving, it seems a waste
 to duplicate the effort instead of just adding kernel support to the
 existing code.

SAMBA implements an SMB/CIFS server.  We're talking about client support.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kris Kennaway

On Fri, 10 Sep 1999, Matthew N. Dodd wrote:

  Okay. If that's the plan, then I don't have any objections.
  
  I do hate the idea of having to reimplement samba because of the licensing
  though - it already does quite a good job at SMB serving, it seems a waste
  to duplicate the effort instead of just adding kernel support to the
  existing code.
 
 SAMBA implements an SMB/CIFS server.  We're talking about client support.

It also does that (smbclient), though not as an FS, and there's
sharity-light for a (n)fs interface.

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



RE: NetWare client in -current

1999-09-10 Thread Daniel O'Connor

On 10-Sep-99 Boris Popov wrote:
   mount_nwfs  - similar to mount_nfs
   ncplogin- creates permanent connection to a NetWare server
 without an actual mount, 
   ncplogout   - destroy permanent connection,
   ncplist - displays various information about client itself
 and NetWare servers,
   ncprint - allows to send job to NetWare printer,
   ncpsend - sends message to NetWare user or server console,
   ncplpd  - simple NetWare print server,
   ncpurge - purge specified salvagable files,
   ncpsvc  - remote control for a NetWare server,
   ncpasswd- allows to change password for a NetWare user.

Is there any reason to not have it as a port?

The only possible candidate for contrib'ifying I could see would be mount_nwfs
because building it without the kernel source could be a problem, but the rest
of it could be a port I think :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum


pgp4hSW27GG7P.pgp
Description: PGP signature


Re: NetWare client in -current

1999-09-10 Thread Ruslan Ermilov
On Fri, Sep 10, 1999 at 06:29:57PM +0930, Daniel O'Connor wrote:
 
 On 10-Sep-99 Boris Popov wrote:
mount_nwfs  - similar to mount_nfs
ncplogin- creates permanent connection to a NetWare server
  without an actual mount, 
ncplogout   - destroy permanent connection,
ncplist - displays various information about client itself
  and NetWare servers,
ncprint - allows to send job to NetWare printer,
ncpsend - sends message to NetWare user or server console,
ncplpd  - simple NetWare print server,
ncpurge - purge specified salvagable files,
ncpsvc  - remote control for a NetWare server,
ncpasswd- allows to change password for a NetWare user.
 
 Is there any reason to not have it as a port?
 
IMHO, only the basic IPX/SPX functionality should be included into the
source tree.  Anything else could be available as ports/net/nw-utils.

-- 
Ruslan Ermilov  Sysadmin and DBA of the
r...@ucb.crimea.ua  United Commercial Bank,
r...@freebsd.orgFreeBSD committer,
+380.652.247.647Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



RE: NetWare client in -current

1999-09-10 Thread Boris Popov
On Fri, 10 Sep 1999, Daniel O'Connor wrote:

 Is there any reason to not have it as a port?
 
 The only possible candidate for contrib'ifying I could see would be mount_nwfs
 because building it without the kernel source could be a problem, but the rest
 of it could be a port I think :)

Yes, that's acceptable. But mount_nwfs require libncp.so and this 
means that ncp library sources will be also required. So KLD, mount_nwfs
and libncp should go into source tree and other utilities can be a port.

Other thoughts ?

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov
On Fri, 10 Sep 1999, Ruslan Ermilov wrote:

  Is there any reason to not have it as a port?
  
 IMHO, only the basic IPX/SPX functionality should be included into the
 source tree.  Anything else could be available as ports/net/nw-utils.

An IPX/SPX stack is already in the tree and past year made it more
or less functional.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Ruslan Ermilov
On Fri, Sep 10, 1999 at 04:58:52PM +0700, Boris Popov wrote:
 On Fri, 10 Sep 1999, Ruslan Ermilov wrote:
 
   Is there any reason to not have it as a port?
   
  IMHO, only the basic IPX/SPX functionality should be included into the
  source tree.  Anything else could be available as ports/net/nw-utils.
 
   An IPX/SPX stack is already in the tree and past year made it more
 or less functional.
 
Read: I fully agree with Daniel.

Forgive me my ignorance, but I'd like a quick response: what about multiple
ethernet frames for IPX?  Is it supported in -current?  In -stable?


Thanks,
-- 
Ruslan Ermilov  Sysadmin and DBA of the
r...@ucb.crimea.ua  United Commercial Bank,
r...@freebsd.orgFreeBSD committer,
+380.652.247.647Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov
On Fri, 10 Sep 1999, Ruslan Ermilov wrote:

  An IPX/SPX stack is already in the tree and past year made it more
  or less functional.
  
 Read: I fully agree with Daniel.

Daniel also left mount_nwfs :)
 
 Forgive me my ignorance, but I'd like a quick response: what about multiple
 ethernet frames for IPX?  Is it supported in -current?  In -stable?

There is an if_ef driver which supports all four ethernet frames
for IPX protocol and can be easily adapted for others (see
http://www.butya.kz/~bp/ipxen.html for details).  It requires two simple
patches to sys/net/if.c file and work on both -current and -stable.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Ruslan Ermilov
On Fri, Sep 10, 1999 at 05:24:00PM +0700, Boris Popov wrote:
 On Fri, 10 Sep 1999, Ruslan Ermilov wrote:
 
 An IPX/SPX stack is already in the tree and past year made it more
   or less functional.
   
  Read: I fully agree with Daniel.
 
   Daniel also left mount_nwfs :)
 
All kernel-related staff (protocol, file-system support and required libraries)
should be available in the tree.  Everything else as a port(s).

  Forgive me my ignorance, but I'd like a quick response: what about multiple
  ethernet frames for IPX?  Is it supported in -current?  In -stable?
 
   There is an if_ef driver which supports all four ethernet frames
 for IPX protocol and can be easily adapted for others (see
 http://www.butya.kz/~bp/ipxen.html for details).  It requires two simple
 patches to sys/net/if.c file and work on both -current and -stable.
 
That's really cool, good job!


-- 
Ruslan Ermilov  Sysadmin and DBA of the
r...@ucb.crimea.ua  United Commercial Bank,
r...@freebsd.orgFreeBSD committer,
+380.652.247.647Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Peter Wemm
Boris Popov wrote:
 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be mount_n
wfs
  because building it without the kernel source could be a problem, but the r
est
  of it could be a port I think :)
 
   Yes, that's acceptable. But mount_nwfs require libncp.so and this 
 means that ncp library sources will be also required. So KLD, mount_nwfs
 and libncp should go into source tree and other utilities can be a port.
 
   Other thoughts ?

I'm really not sure I see the value in splitting it up like that.. Are
things like ncplogin required to support mount_nwfs?  Personally, I think
it might be better to take the whole lot and later on (nearer 4.0 time)
decide if it's worth splitting the ncp* off to a port if it's worth doing.
Otherwise version skew is going to be a hassle while it's under
development.

Cheers,
-Peter




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov
On Fri, 10 Sep 1999, Peter Wemm wrote:

  Yes, that's acceptable. But mount_nwfs require libncp.so and this 
  means that ncp library sources will be also required. So KLD, mount_nwfs
  and libncp should go into source tree and other utilities can be a port.
  
  Other thoughts ?
 
 I'm really not sure I see the value in splitting it up like that.. Are
 things like ncplogin required to support mount_nwfs?  Personally, I think
 it might be better to take the whole lot and later on (nearer 4.0 time)
 decide if it's worth splitting the ncp* off to a port if it's worth doing.
 Otherwise version skew is going to be a hassle while it's under
 development.

Thats why I suggested an original scheme...

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Marcel Moolenaar
Boris Popov wrote:

 Currently I'm trying to determine a reasonable set of NetWare
 utilities which should be included in the source tree.

Is it possible to have utilities to query and modify NDS?

 ncpurge - purge specified salvagable files,


RE: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd
On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 On 10-Sep-99 Boris Popov wrote:
mount_nwfs  - similar to mount_nfs
ncplogin- creates permanent connection to a NetWare server
  without an actual mount, 
ncplogout   - destroy permanent connection,
ncplist - displays various information about client itself
  and NetWare servers,
ncprint - allows to send job to NetWare printer,
ncpsend - sends message to NetWare user or server console,
ncplpd  - simple NetWare print server,
ncpurge - purge specified salvagable files,
ncpsvc  - remote control for a NetWare server,
ncpasswd- allows to change password for a NetWare user.
 
 Is there any reason to not have it as a port?
 
 The only possible candidate for contrib'ifying I could see would be
 mount_nwfs because building it without the kernel source could be a
 problem, but the rest of it could be a port I think :)

Thats like suggesting we make the 'ipfw' command a port and leave the
kernel bits in the tree.  Since all this stuff depends on being in sync,
the only reasonable way to do this is to put it in the tree.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| win...@jurai.net |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Peter Wemm
Matthew N. Dodd wrote:
 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
  On 10-Sep-99 Boris Popov wrote:
 mount_nwfs  - similar to mount_nfs
 ncplogin- creates permanent connection to a NetWare server
   without an actual mount, 
 ncplogout   - destroy permanent connection,
 ncplist - displays various information about client itself
   and NetWare servers,
 ncprint - allows to send job to NetWare printer,
 ncpsend - sends message to NetWare user or server console,
 ncplpd  - simple NetWare print server,
 ncpurge - purge specified salvagable files,
 ncpsvc  - remote control for a NetWare server,
 ncpasswd- allows to change password for a NetWare user.
  
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be
  mount_nwfs because building it without the kernel source could be a
  problem, but the rest of it could be a port I think :)
 
 Thats like suggesting we make the 'ipfw' command a port and leave the
 kernel bits in the tree.  Since all this stuff depends on being in sync,
 the only reasonable way to do this is to put it in the tree.

Or having mount_nfs in the base but moving nfsd/nfsiod/nfsstat to ports.
:-)

Cheers,
-Peter
--
Peter Wemm - pe...@freebsd.org; pe...@yahoo-inc.com; pe...@netplex.com.au



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Boris Popov
On Fri, 10 Sep 1999, Marcel Moolenaar wrote:

  Currently I'm trying to determine a reasonable set of NetWare
  utilities which should be included in the source tree.
 
 Is it possible to have utilities to query and modify NDS?

I'm working on this (currently only queries). NDS library will be
separate package from ncplib.

 
  ncpurge - purge specified salvagable files,
 
 From a user perspective, is salvaging not also important?

Yes it is important, but requires dialogue with user because
there can be more than one deleted file with same name. I'm trying to get
Novell to respond on my query about source code for 'filer' utility but
they keeps quiet at the moment.

--
Boris Popov
http://www.butya.kz/~bp/



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Mike Smith
 On Fri, 10 Sep 1999, Daniel O'Connor wrote:
 
  Is there any reason to not have it as a port?
  
  The only possible candidate for contrib'ifying I could see would be 
  mount_nwfs
  because building it without the kernel source could be a problem, but the 
  rest
  of it could be a port I think :)
 
   Yes, that's acceptable. But mount_nwfs require libncp.so and this 
 means that ncp library sources will be also required. So KLD, mount_nwfs
 and libncp should go into source tree and other utilities can be a port.

You could still build the KLD as a port, actually.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  msm...@freebsd.org
\\-- Joseph Merrick   \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Daniel O'Connor


Matthew N. Dodd wrote:
  The only possible candidate for contrib'ifying I could see would be
  mount_nwfs because building it without the kernel source could be a
  problem, but the rest of it could be a port I think :)
 Thats like suggesting we make the 'ipfw' command a port and leave the
 kernel bits in the tree.  Since all this stuff depends on being in sync,
 the only reasonable way to do this is to put it in the tree.

Why? What kernel code does this need?

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd
On Sat, 11 Sep 1999, Daniel O'Connor wrote:
 Matthew N. Dodd wrote:
   The only possible candidate for contrib'ifying I could see would be
   mount_nwfs because building it without the kernel source could be a
   problem, but the rest of it could be a port I think :)
  Thats like suggesting we make the 'ipfw' command a port and leave the
  kernel bits in the tree.  Since all this stuff depends on being in sync,
  the only reasonable way to do this is to put it in the tree.
 
 Why? What kernel code does this need?

The ncpfs kernel code for one.

We're talking about less than 500k of code here.

You want to take the anti-bloatist stance you'll have to do better than
that.  Try libreadline for starters.  :)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| win...@jurai.net |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Daniel O'Connor
Matthew N. Dodd wrote:
  Why? What kernel code does this need?
 The ncpfs kernel code for one.
 We're talking about less than 500k of code here.
 You want to take the anti-bloatist stance you'll have to do better than
 that.  Try libreadline for starters.  :)

Bah like I care enough to care ;)

If it has a fair amount of kernel code then its a good idea..
Also as you pointed out, it aids interoperability..

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Parag Patel

On Sat, 11 Sep 1999 03:08:40 +0930, Daniel O'Connor wrote:

Matthew N. Dodd wrote:
 You want to take the anti-bloatist stance you'll have to do better than
 that.  Try libreadline for starters.  :)

Bah like I care enough to care ;)

Yow!  I had no idea it was so large!

I have an (as yet still incomplete) full-screen text-editor library I
wrote a long time ago - in C++ even - that supports (on a terminal using
termlib but not curses) full-screen editing, simultaneous live
multiple overlapping windows/views of buffers, full left/right up/down
scrolling, line-numbering, unlimited undo/redo including any buffer
marks, regular-expression searching, and arbitrary depth key-bindings.

It's less than half the size of libreadline.

I am so depressed.


-- Parag Patel


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd
On Fri, 10 Sep 1999, Parag Patel wrote:
 I have an (as yet still incomplete) full-screen text-editor library I
 wrote a long time ago - in C++ even - that supports (on a terminal using
 termlib but not curses) full-screen editing, simultaneous live
 multiple overlapping windows/views of buffers, full left/right up/down
 scrolling, line-numbering, unlimited undo/redo including any buffer
 marks, regular-expression searching, and arbitrary depth key-bindings.
 
 It's less than half the size of libreadline.
 
 I am so depressed.

Clean it up and add perl bindings to it.  Thats something that perl sorely
misses.  Come to think of it, libedit could use perl bindings...  Hummm...

Kevin?  :)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| win...@jurai.net |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Parag Patel
On Fri, 10 Sep 1999 14:07:12 EDT, Matthew N. Dodd wrote:

Clean it up and add perl bindings to it.  Thats something that perl sorely
misses.  Come to think of it, libedit could use perl bindings...  Hummm...

Gaah - another big line-editing library!  My editor's even smaller than
libedit!

   textdata bss dec hex filename
  601134352   0   64465fbd1 /usr/lib/libedit.so
 117406   140041464  132874   2070a /usr/lib/libreadline.so
  48843 6364492   53971d2d3 tst

I'll add my editing package to my things-to-clean-up list and make it
available when I next have some time.

I've never cared for perl tho'.  

Growing up programming on a KL-10, I still think the correct place for
line-editing is in the driver.  Hell - it's already doing basic
erase/kill line editing as it is.  Then you don't have to hack every
command-line app to get line-editing.


-- Parag Patel


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew Hunt
On Fri, Sep 10, 1999 at 02:07:12PM -0400, Matthew N. Dodd wrote:

 Clean it up and add perl bindings to it.  Thats something that perl sorely
 misses.  Come to think of it, libedit could use perl bindings...  Hummm...

/usr/ports/devel/p5-ReadLine-Gnu

Also /usr/ports/devel/p5-ReadLine-Perl, which is pure Perl, instead of
using an external library.

If you say use Term::ReadLine, Perl will use either of those if
available, or use a useless dummy version that ships with Perl otherwise.

Bindings for libedit which are compatible with these would be cool.

-- 
Matthew Hunt m...@astro.caltech.edu * UNIX is a lever for the
http://www.pobox.com/~mph/   * intellect. -J.R. Mashey


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Warner Losh
In message 37d93d65.627a...@dons.net.au Daniel O'Connor writes:
:  Thats like suggesting we make the 'ipfw' command a port and leave the
:  kernel bits in the tree.  Since all this stuff depends on being in sync,
:  the only reasonable way to do this is to put it in the tree.
: 
: Why? What kernel code does this need?

The IPFILTER kernel option.  ipfw just builds the IPFILTER kernel tables.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kevin Doherty
And thus spake Matthew N. Dodd, on Fri, Sep 10, 1999 at 02:07:12PM -0400:
 Clean it up and add perl bindings to it.  Thats something that perl sorely
 misses.  Come to think of it, libedit could use perl bindings...  Hummm...
 
 Kevin?  :)

Bleah, one thing at a time :)  Once I finish with my current project I'll
probably work on this if there's any interest, though.

--
Kevin Doherty, kdohe...@cosanostra.net
Multiple exclamation marks are a sure sign of a diseased mind.
   -- Rincewind (from _Eric_)


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kris Kennaway
On Fri, 10 Sep 1999, Ruslan Ermilov wrote:

  Is there any reason to not have it as a port?
  
 IMHO, only the basic IPX/SPX functionality should be included into the
 source tree.  Anything else could be available as ports/net/nw-utils.

I tend to agree. If we bring in all of this stuff (even though I
appreciate it's very useful) we should also bring in samba into the base
tree by symmetry.

Kris



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd
On Fri, 10 Sep 1999, Kris Kennaway wrote:
 I tend to agree. If we bring in all of this stuff (even though I
 appreciate it's very useful) we should also bring in samba into the
 base tree by symmetry.

Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
import it into the tree the same as the Netware client stuff.

You were maybe talking about Samba, which doesn't have any kernel
components or userland tools that are dependent on them.

An in-kernel SMB/CIFS server would be on the same order as the NFS server
support; something we would want to have in the tree so as to keep an eye
on it and lower maintainence cost for the developer.  (Not that this has
kept the NFS server code free of interesting incidents.)

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| win...@jurai.net |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kris Kennaway
On Fri, 10 Sep 1999, Matthew N. Dodd wrote:

 On Fri, 10 Sep 1999, Kris Kennaway wrote:
  I tend to agree. If we bring in all of this stuff (even though I
  appreciate it's very useful) we should also bring in samba into the
  base tree by symmetry.
 
 Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
 import it into the tree the same as the Netware client stuff.

Okay. If that's the plan, then I don't have any objections.

I do hate the idea of having to reimplement samba because of the licensing
though - it already does quite a good job at SMB serving, it seems a waste
to duplicate the effort instead of just adding kernel support to the
existing code.

Kris



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Matthew N. Dodd
On Fri, 10 Sep 1999, Kris Kennaway wrote:
  Thats the idea.  Once Boris gets a chance to finish cifsfs the plan is to
  import it into the tree the same as the Netware client stuff.
 
 Okay. If that's the plan, then I don't have any objections.
 
 I do hate the idea of having to reimplement samba because of the licensing
 though - it already does quite a good job at SMB serving, it seems a waste
 to duplicate the effort instead of just adding kernel support to the
 existing code.

SAMBA implements an SMB/CIFS server.  We're talking about client support.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| win...@jurai.net |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: NetWare client in -current

1999-09-10 Thread Kris Kennaway
On Fri, 10 Sep 1999, Matthew N. Dodd wrote:

  Okay. If that's the plan, then I don't have any objections.
  
  I do hate the idea of having to reimplement samba because of the licensing
  though - it already does quite a good job at SMB serving, it seems a waste
  to duplicate the effort instead of just adding kernel support to the
  existing code.
 
 SAMBA implements an SMB/CIFS server.  We're talking about client support.

It also does that (smbclient), though not as an FS, and there's
sharity-light for a (n)fs interface.

Kris



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message