> Anyway, the point is that a file that I can access should be a file I > can access via VI or MORE or EMACS or GREP or any other tool without > having those tools each having FTP and HTTP and SSH support built in to > them. The OS should handle it. Yes, this should be nice. There's a similar project for Linux here: http://ftpfs.sourceforge.net/ (FTP only). It would be amusing to port it into a KLD file. -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Should URL's be pervasive. David O'Brien
- Re: Should URL's be pervasive. Steve Roome
- Re: Should URL's be pervasive. David O'Brien
- Re: Should URL's be pervasive. Richard Hodges
- Re: Should URL's be pervasive. Hroi Sigurdsson
- Re: Should URL's be pervasive. Bruce A. Mah
- Re: Should URL's be pervasive. Leo Bicknell
- Re: Should URL's be pervasive. Matthew D. Fuller
- Re: Should URL's be pervasive. Richard Hodges
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Sansonetti Laurent
- Re: Should URL's be pervasive. Charlie Root
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Kenneth P. Stox
- Re: Should URL's be pervasive. Michael Sinz
- Re: Should URL's be pervasive. Charlie Root
- Re: Should URL's be pervasive. Joseph Mallett
- Re: Should URL's be pervasive. Mattias Pantzare
- Re: Should URL's be pervasive. Kevin Way
- Re: Should URL's be pervasive. Mike Meyer