Re: kazaa client
Scott I. Remick wrote: On Tue, 23 Dec 2003 04:08:55 +0200, Anton Alin-Adrian wrote: Thanks. Seems I am going to develop a GTK UI for fasttrack ;P Hmm maybe as an easier start, someone can add giFToxic to the FreeBSD ports collection? http://giftoxic.sourceforge.net/ Porting is currently outside my own abilities. I'd love to do this, but I don't know enough about how to create a port. I downloaded release 0.0.9 and got it to compile on my FreeBSD 4.8 machine with two small changes necessary: 1) Must compile with gcc version 3.3.3, not version 2.95.4. (IE, I set my environment CC=gcc33 before configuring) 2) The final linking of the executable must also include -lgnugetopts or getopts_long is undefined. This requires the port devel/libgnugetopt installed. I just hacked src/Makefile after configuring, but this should probably be done more intelligently. One of these days I may figure out for myself how to make a port of it, but please don't hold your (or anyone else's) breath. -- Jim Ramsay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kazaa client
Anton Alin-Adrian wrote: If anyone knows a kazaa compatible program working under FreeBSD, preferably GTK based and present in the ports, I would be gratefull for any information regarding that. You want: /usr/ports/net/gift /usr/ports/net/gift-fasttrack /usr/ports/net/giftcurs And probably gift-openft and gift-gnutella too, for more excellent search possibilities. The 'fasttrack network' is kazaa. -- Jim Ramsay ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing /etc/termcap in 4.8 - How can I?
Malcolm Kay wrote:
On Wed, 17 Dec 2003 06:47, Jim Ramsay wrote:
I have tried to add an extra entry to /etc/termcap:
rxvt-cygwin-native|rxvt terminal emulator (native MS Windows/Cygwin):\
:pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:\
:
:ac=+\257,\256-^0\333`\004a\261f\370g\361h\260j\331k\277l\332m\300n\305o~p\
:304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330~\376:\
:
:tc=rxvt-mono:
to try to get linedrawing characters working correctly in my connection
from my work computer (cygwin/ssh) to my freebsd machine at home.
1) I edited the file as root and put it just after the existing 'rxvt'
entry.
The directory entry /etc/termcap is normally a symbolic link to
/usr/share/misc/termcap, which I think you already realised.
The tricky bit is what happens when you attempt to edit a file via a
symbolic link. Either of two things can happen depending on the editor you
are using:
1) You actually edit the file at the end of the link and the link remains
intact.
I used vim and I think that this occurred.
2) The editor presents you with the text from the file at the end of the link
but on saving the changes deletes the link and substitutes the changed text as
a file. The file that was at the end of the link remains unchanged.
So you should make sure /etc/termcap is still a link to
/usr/share/misc/termcap.
Now go to /usr/share/misc and edit termcap and then execute cap_mkdb.
I have tried this also, but no difference in tcsh's behaviour.
I have even tried editing termcap.src in /usr/src/share/termcap/ and
doing a 'make install' there to see if I'm missing a step... but no luck.
I also received an off-list tip from Karl Vogel:
I've noticed that both zsh and tcsh can get really snotty if the
environment variables are not set in this order:
unsetenv TERMCAP
unsetenv TERMINFO
unsetenv TERM
setenv TERMCAP /path/to/your/termcap/file (or actual termcap entry)
setenv TERMINFO /path/to/your/terminfo/directory
setenv TERM xterm
But neither TERMCAP nor TERMINFO are set in my normal tcsh environment.
I have tried setting and unsetting them in the order given here and
many other permutations, to no success.
I have tried logging out and back in again, in case tcsh caches termcap
somewhere that isn't updated without re-running tcsh, but I don't think
this is the case.
The only thing I haven't tried yet is rebooting - technically I don't
think I would have to.
Is there some utility somewhere that can tell me if I've got a typo in
my termcap or something which would prevent tcsh from reading my new
entry properly?
I suppose could write my own curses program to do this... maybe.
Is there some utility somewhere which will translate my termcap into
terminfo so I can try that? Why is there no terminfo stuff in FreeBSD 4.8?
--
Jim Ramsay
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Changing /etc/termcap in 4.8 - How can I?
I have tried to add an extra entry to /etc/termcap:
rxvt-cygwin-native|rxvt terminal emulator (native MS Windows/Cygwin):\
:pa#64:Co#8:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:\
:ac=+\257,\256-^0\333`\004a\261f\370g\361h\260j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330~\376:\
:tc=rxvt-mono:
to try to get linedrawing characters working correctly in my connection
from my work computer (cygwin/ssh) to my freebsd machine at home.
1) I edited the file as root and put it just after the existing 'rxvt'
entry.
2) I then went into /usr/share/misc and did `cap_mkdb termcap` to update
termcap.db.
However, when I try to `setenv TERM rxvt-cygwin-native`in tcsh, I get
the error:
tcsh: Cannot open /etc/termcap.
tcsh: using dumb terminal settings.
Which is the same error if I try to set TERM to something like
aoeuaoeu which doesn't exist in the termcap.
Is there some step I'm missing here to make tcsh recognize the new
termcap info? Is termcap cached somewhere that I haven't updated or
something?
--
Jim Ramsay
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
