Plex Inphiniti | 11 Apr 2004 20:07
Picon
Favicon

gopher newbie quesstion: .names

I am setting up gopherd, it all looks fine, except it doesn't read the .names
file. when connecting the server all I see is the list of data files.

__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html

Cameron Kaiser | 12 Apr 2004 20:50
Favicon

not quite Slashdotted ...

http://www.wired.com/news/technology/0,1282,62988,00.html?tw=wn_tophead_2

So far the public proxy is handling the load well ...

Since Port-a-Goph was mentioned in it :) I found a nasty bug in it I'm still
trying to repair.

--

-- 
---------------------------------- personal: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Floodgap Systems Ltd * So. Calif., USA * ckaiser@...p.com
-- "Kirk to Enterprise: beam down yeoman Rand and a six-pack." ----------------

John Goerzen | 12 Apr 2004 21:20
Favicon

Re: not quite Slashdotted ...

On Mon, Apr 12, 2004 at 11:50:18AM -0700, Cameron Kaiser wrote:
> http://www.wired.com/news/technology/0,1282,62988,00.html?tw=wn_tophead_2
> 
> So far the public proxy is handling the load well ...
> 
> Since Port-a-Goph was mentioned in it :) I found a nasty bug in it I'm still
> trying to repair.

Excellent! (to the load handling, not the bug, part :-)

Lore asked me a few questions a little while back.  I didn't know the
article was actually going forward until I saw it on Wired today.

BTW, where can we get Port-a-Goph? :-)

-- John

Cameron Kaiser | 12 Apr 2004 22:57
Favicon

Re: not quite Slashdotted ...

> BTW, where can we get Port-a-Goph? :-)

I want to fix the bug (it's in the download to VFS card portion), but if
you just want to play with it (remember it still has the problem with
hanging up the unit with servers that don't answer; this is a problem with
the runtime library), I'll try to get it up minus that portion sometime
this week.

--

-- 
---------------------------------- personal: http://www.armory.com/~spectre/ --
 Cameron Kaiser, Floodgap Systems Ltd * So. Calif., USA * ckaiser@...p.com
-- Make welfare as hard to get as building permits. ---------------------------

Alessandro Selli | 14 Apr 2004 09:53
Favicon

pygopherd on Debian stable

  Hello,
  	I'm considering installing pygopherd to replace UMN gopherd on a
Debian stable server running on a SPARCStation5.  However, this distribution
comes with python version 2.1.3, while pygopherd needs version 2.3.  In order
to have pygopherd running I'd need to upgrade the server to the testing python
package, plus a small number of other dependencies.  I wished I didn't need to
have mixed stable/unstable packages on the "frontline" server, so before I
give up on the server's "purity" and upgrade python with the testing package I
wanted to ask this: when pygopherd was developped, was python 2.3 used because
some of it's features where needed in order to have a fully functional gopherd
server, or was it just because that was the python version available on the
developer's computer and maybe pygopherd can work on python2.1?
Any idea?  Should I just try that?

  Thanks,

  Sandro

--

-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9

John Goerzen | 14 Apr 2004 16:01
Favicon

Re: pygopherd on Debian stable

On Wed, Apr 14, 2004 at 09:53:03AM +0200, Alessandro Selli wrote:

>   	I'm considering installing pygopherd to replace UMN gopherd on a
>   	Debian stable server running on a SPARCStation5.  However, this
>   	distribution comes with python version 2.1.3, while pygopherd
>   	needs version 2.3.  In order to have pygopherd running I'd need
>   	to upgrade the server to the testing python package, plus a
>   	small number of other dependencies.  I wished I didn't need to

You have several different options.  You can probably get a usable
Python for woody from www.backports.org or www.apt-get.org.

However, I have an even easier solution -- you can just install Python
from source.  Python is easy to build and install from source and you'll
have no problem doing this on your woody box.  Just download Python 2.3
and configure it to go to somewhere other than the system's default
location -- /opt/python2.3, for instance.  This location should also
*NOT* be on your PATH.  PyGopherd uses few C extensions to Python, so
you don't have to worry about the Tk, GDBM, etc. stuff that the Debian
maintainers do.  Essentially, all that happens when you build Python
from source like this is that it builds the interpreter and installs the
Python sources and C modules for the standard library.

Now, install PyGopherd from source.  All you should have to do is run
"/opt/python2.3/bin/python setup.py install" in the PyGopherd directory
and you should be set.

>   	have mixed stable/unstable packages on the "frontline" server,
>   	so before I give up on the server's "purity" and upgrade python
>   	with the testing package I wanted to ask this: when pygopherd
(Continue reading)

Alessandro Selli | 14 Apr 2004 19:29
Favicon

Re: pygopherd on Debian stable

Il giorno Wed, 14 Apr 2004, John Goerzen così ha scritto:

|>   	I'm considering installing pygopherd to replace UMN gopherd on a
|>   	Debian stable server running on a SPARCStation5.  However, this
|>   	distribution comes with python version 2.1.3, while pygopherd
|>   	needs version 2.3.  In order to have pygopherd running I'd need
|>   	to upgrade the server to the testing python package, plus a
|>   	small number of other dependencies.  I wished I didn't need to
|
|You have several different options.  You can probably get a usable
|Python for woody from www.backports.org or www.apt-get.org.

  They both carry python2.2 for the Sparc architecture.  Humm...

|However, I have an even easier solution -- you can just install Python
|from source.

  I like this idea.  Yes, I will definitely do this.
  Than you,

  Sandro

--

-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9


Gmane