Re: More SpamAssassin questions - it won't run.
Hey all. I know this has come up recently, and I've looked at the pages posted recently. My problem isn't getting it set up in procmail, it's getting SpamAssassin to execute without errors. I know, this is just a little OT. Sorry, but this is usually the best place to get answers on almost anything that even comes into contact with FreeBSD. The problem is related with the (implicit) dependency on the p5-File-Spec package. Unfortunately, the splitpath method appeared in a version of the module that is newer than the one bundled with base perl(1). This could be specified in spamassassin with use File::Spec 0.8; (or whatever). I worked around the problem installing the p5-File-Spec port by hand. In my opinion, this should be handled properly by the ports system, but couldn't figure out how to fix it myself. :-( Regards To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: SSH through a firewall
Hi, You can set up por forwarding for ssh connections to 10.0.0.2 as follows: ssh -L 2022:10.0.0.2:22 12.225.249.250 And while that connection remains open, you can do: scp -P 2022 file.txt localhost: Please note that the requested password or key will be the one on the destination host, not the gateway. Also, that you can do multiple port forwardings at once: ssh -L 2022:10.0.0.2:22 -L 2122:10.0.0.3:22 -L :10.0.0.4:22 12.225.249.250 HTH - Original Message - From: Joshua Lokken [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 15, 2002 3:58 PM Subject: SSH through a firewall Hi, folks I often transfer files to my home machines from work using scp. Currently, if I want to move a file to a machine on my LAN, I first have to copy the file to a user home dir on the gateway box, then recopy it from the gateway to the internal box. How do I avoid this extra step? eg, 130.94.160.46 -- 12.225.249.250 10.0.0.2 (remote machine) (gateway) (destination) I have the proper keys in the proper places and the hosts files are OK. I appreciate any help. Please cc me, as this address is not subscribed to the list. Thanks! -- Best Regards, Joshua Lokken OMIC Portland Branch [EMAIL PROTECTED] 503 807 6538 - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: pkg_add failure on 4.6.2
Hi Kris et al, I just installed 4.6.2, and I wanted to install cvsup. So I brought the cvsup-16-1f.tbz from ftp.freebsd.org, and did a 'pkg_add cvsup-16-1f.tbz', but whenever I run pkg_add, it core dumps. You should use the 4.6.2-RELEASE packages with 4.6.2; they're in .tgz format. Just a note about this. The remote fetching feature (-r option) is broken in pkg_add(1) as distributed with 4.6.2-RELEASE. It needs to be upgraded to the version tagged RELENG_4_6. Otherwise, packages will download from the stable branch. HTH To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: KDE and KDM issues still
Hi,
ttyv8 /usr/local/bin/kdmxterm on secure
You're missing the -nodaemon option here. It should read:
ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure
Please note that if you're running:
kdebase-3.0_1 Base modules for the KDE integrated X11 desktop
kdelibs-3.0_1 Libraries for KDE
As packaged with RELEASE-4.6.2, you should start kdm from somewhere
else. Starting it from init(1) brings a problem with konsole. I use
this in rc.local:
( sleep 45 ; /usr/local/bin/kdm )
echo -n ' kdm'
[The 45 second sleep depends on how much are you starting from
/usr/local/etc/rc.d -- this should happen after all you plain text
console(4) getty's start.]
I keep getting these errors messages in my logs: Sep 7 13:00:28
bsdguru kdm_config[12241]: Unknown command line option 'ttyv8'
Kdm doesn't like the tty argument as passed from init(1). Here's a
patch for that problem:
Index: init.c
===
RCS file: /home/ncvs/src/sbin/init/init.c,v
retrieving revision 1.38.2.8
diff -u -p -r1.38.2.8 init.c
--- init.c 2001/10/22 11:27:32 1.38.2.8
+++ init.c 2002/09/20 17:43:36
@@ -1027,8 +1027,13 @@ setupargv(sp, typ)
free(sp-se_getty_argv_space);
free(sp-se_getty_argv);
}
- sp-se_getty = malloc(strlen(typ-ty_getty) + strlen(typ-ty_name) + 2);
- (void) sprintf(sp-se_getty, %s %s, typ-ty_getty, typ-ty_name);
+ if (strstr(typ-ty_getty, kdm)) {
+ /* kdm doesn't expect a tty name */
+ sp-se_getty = strdup(typ-ty_getty);
+ } else {
+ sp-se_getty = malloc(strlen(typ-ty_getty) + strlen(typ-ty_name) +
+2);
+ (void) sprintf(sp-se_getty, %s %s, typ-ty_getty, typ-ty_name);
+ }
sp-se_getty_argv_space = strdup(sp-se_getty);
sp-se_getty_argv = construct_argv(sp-se_getty_argv_space);
if (sp-se_getty_argv == 0) {
IMO there should be an elegant way to let init(1) know which programs
expect this argument, possibly with an option in /etc/ttys, or have a
wrapper script around kdm to avoid this.
HTH
Regards
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: atapi cd-r/cd-rw drives?
Hi, how recent? as in, implemented, but relatively stable, or implemented, but still in need of heavy tinkering to be considered useable? just kinda curious about that one. I found the so-called ATAPI/CAM interface a couple of weeks ago when encountered the reported DAO recording problems with burncd(8). Now I'm using cdrecord(1) and cdrdao(1), installed from packages. The code is available at: http://www.cuivre.fr.eu.org/~thomas/atapicam/ According to the published patches and information available the code is six months old, at least, and has been recently committed to CVS. The patches merged *flawlessly* and they're a great contribution to the kernel -- it was indeed a missing component. Merci beaucoup, Thomas. it isn't intended as slander..based on the limited amount of info i've run across about burncd, i could've sworn i saw a few things mentioning it as having a lack of widespread cd-r drive support. perhaps i'm mistaken, but research time is a little limited at the moment. The supported drive list seems to be rather outdated/incomplete. My Sony drive is not in the list and works pretty well with burncd(8) with the only exception of DAO mode audio discs. From what I've read, most recent ATAPI drives should work reasonably well. to elaborate a bit, i've got a dj gig tomorrow and i'm unsure of whether or not i'll have access to turntables. for that reason, i figured i'd burn a couple discs of mp3's that i have of some of my vinyl releases, just in case. :-) Regards To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
