Well fuck, I done it. You now have control of the gopher daemon's directory tree. It's pointed at th elibrary. Whatever files you put in there show up. I discovered one odditiy thats actually quite a feature. Gopherd knows how to read a mail message! If you S)ave a mail message, to /u/library/(filename), to gopher it will look like a directory! Each message within it looks like a separate file! Cool! So figger out gopher's link thing. Do man gopherd, skip the voluminous crapola on command line options. Look for the section marked LINKS. Links are special files that gopherd looks for. If they are there, instead of just listing the files in the directory like FTP does (only cleaner), it'll interpret the link file(s). This is what lets you have an entry that says: "William S. Burroughs' latest shit" but really poitn to a directory called wsb99. The reference to the "Curses" client, is jsut the regular gopher client... "curses" is the name of the cursor-movement crap... Later!!! -- Tom Jennings -- tomj@wps.com -- World Power Systems -- San Francisco, Calif. The Little Garden -- admin@admin.tlg.rg.net -- S.F. Bay Area Internetwork > it's almost there. The library access is back up. However I can't drop > the files into their correct directory (i.e. I keep getting a permission > denied message when I try to move the files. The problem was, you were not the owner of the files. I changed it so that you are. For security, you will have to remember to do two things before and after to make changes in there. When you're not working there, you should make all files read-only. Every night, cron will go through and make sure all the files in the library are R/O, and owned by you. This will cover other people puttign files in there (I occasionally save stuff there for general use). It's easier to simply make the whole /u/library tree writable, do whatever you gotta do, then make it all read only again. cd /u/library chmod -R a+rw * change * to rw, -R recurse all dirs work on /u/library... chmod -R a-w * recursively remove -w (write) Do an ls -l (dash ell) to see the bits... d = directory uuu = USER: r)ead w)rite x)ecute ggg = GROUP: r)ead w)rite x)ecute ooo = OTHER: r)ead w)rite x)ecute duuugggooo -rw-r----- 1 tomj staff 1536 Jul 30 13:22 world.notes -rw-r----- 1 tomj staff 145 Nov 17 14:53 wrong USER: you, me, etc. GROUP: all of /u are in group guest. OTHER: users not in my group (and not me) My sample files here are: r/w by user (tomj), readable by my group (staff), not readable, writable or executable by others. -- Tom Jennings -- tomj@wps.com -- World Power Systems -- San Francisco, Calif. The Little Garden -- admin@admin.tlg.rg.net -- S.F. Bay Area Internetwork From flesh@fido.wps.com Fri Dec 17 14:49:27 1993 Received: by fido.wps.com (5.67/wps.com-hackery) id AA01858; Fri, 10 Dec 93 17:23:00 -0800 Date: Fri, 10 Dec 1993 17:22:42 -0800 (PST) From: Flesh Subject: Re: hmmm (fwd) To: flesh@wps.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ---------- Forwarded message ---------- Date: Sun, 5 Dec 1993 11:25:47 -0800 (PST) From: Flesh To: flesh@wps.com Subject: Re: hmmm (fwd) ---------- Forwarded message ---------- Date: Thu, 2 Dec 1993 18:29:29 -0800 (PST) From: Tom Jennings To: Flesh Subject: Re: hmmm > The message I got back was "no opening > menu. Cannot continue." What did I do wrong? Likely nothing. The directory itself -- /u/library -- didn't have read bits set for Group and Other. So gopher couldn't get into the directory. (cd /u/library; ls -la. The current directory is "." or cd to /u and ls -l.) Prtobably I did it in messing around. Its possible you did it with an overly broad chmod command. Not to worry. If you see /u/library without R bits, set 'em: chmod a+rx library (X on a directory means, "can cd there". X on a file means can execute. Welcome to eunuchs) -- Tom Jennings -- tomj@wps.com -- World Power Systems -- San Francisco, Calif. The Little Garden -- admin@admin.tlg.rg.net -- S.F. Bay Area Internetwork From flesh@fido.wps.com Fri Dec 17 14:49:36 1993 Received: by fido.wps.com (5.67/wps.com-hackery) id AA01865; Fri, 10 Dec 93 17:23:39 -0800 Date: Fri, 10 Dec 1993 17:23:12 -0800 (PST) From: Flesh Subject: gopher (fwd) To: flesh@wps.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ---------- Forwarded message ---------- Date: Sun, 5 Dec 1993 11:26:49 -0800 (PST) From: Flesh To: flesh@wps.com Subject: gopher (fwd) ---------- Forwarded message ---------- Date: Fri, 3 Dec 1993 00:39:37 -0800 (PST) From: Tom Jennings To: Flesh Subject: gopher None of the directories had the x bit set... so it didn't work. I fixed that. Let's not worry too much about the r vs. rw thing. Maybe I should just mail you stuff that looks interesting, and you can add 'em, rather than have it so anyone can write in there. PS: when you put in saved email files, manually edit the header off 'en them. Gopher tries to be smart and treats the headers as if they were subdirectories. I edited some of them already. -- Tom Jennings -- tomj@wps.com -- World Power Systems -- San Francisco, Calif. The Little Garden -- admin@admin.tlg.rg.net -- S.F. Bay Area Internetwork