Re: Shell question
From: Jordan Gordeev <[EMAIL PROTECTED]> To: freebsd-questions@freebsd.org Subject: Re: Shell question Date: Thu, 26 Oct 2006 20:05:50 +0300 Jack Stone wrote: From: Warren Block <[EMAIL PROTECTED]> To: Jack Stone <[EMAIL PROTECTED]> CC: freebsd-questions@freebsd.org Subject: Re: Shell question Date: Wed, 25 Oct 2006 21:35:55 -0600 (MDT) On Wed, 25 Oct 2006, Jack Stone wrote: Folks: I have managed to piece together a shell script that is able to retrieve the domains from the spams of the day and summarize those in a special file that can then be added to the sendmail's rejects in the access.db. But, first I have to eyeball the list and remove any obvious good-guy domains. I would like to create another list of those same good guys that can be added to each day as they show up, then compare it to the above main list and delete the good guy domains before adding to the access.db. Greylisting will be much more effective than this approach, and is easier to implement. Combine that with sbl-xbl and maybe a few other DNSBLs, add greet_pause of five or ten seconds, and you have much more effectiveness with less false positives and much less maintenance. Adding clamav rounds out the whole thing. I wrote an article that covers some of this: http://www.wonkity.com/~wblock/greylist.pdf -Warren Block * Rapid City, South Dakota USA This shell script is just icing on the cake -- In addition to the DNSBLs, I have had all of those other filters running for years plus milter-regex in the front line, then greylist, then clamav, SA. It's the SA (SpamAssassin) that provides me the list of bad-guy domains. It's a very short list so I can always still eyeball it and remove any obvious good ones. It's just sometimes I have made a mistake and let in a good guy, say, like one of my own domains. If I had a "good-guy list" to watch over my shoulder and check the bad-guy list before adding to the access-reject, then those would never happen again. Those bad guys are pretty obvious by their names. Even if the domains are "throw-aways", I can stop a few more this way although I have to purge the sendmail access DB ever so often. My users might get 1 or 2 spams a month with my line of defenses. Takes a lot of my time, but worth the results. This shell would be a big help tho. Would appreciate any more tips on how to have my daily bad-guy list checked against the good-guy list. Both are flat files with the domains listed in a single column. Thanks guys! Jack See comm(1). ___ Yep, that's it!! Thanks, Jack _ Stay in touch with old friends and meet new ones with Windows Live Spaces http://clk.atdmt.com/MSN/go/msnnkwsp007001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell question
Jack Stone wrote: From: Warren Block <[EMAIL PROTECTED]> To: Jack Stone <[EMAIL PROTECTED]> CC: freebsd-questions@freebsd.org Subject: Re: Shell question Date: Wed, 25 Oct 2006 21:35:55 -0600 (MDT) On Wed, 25 Oct 2006, Jack Stone wrote: Folks: I have managed to piece together a shell script that is able to retrieve the domains from the spams of the day and summarize those in a special file that can then be added to the sendmail's rejects in the access.db. But, first I have to eyeball the list and remove any obvious good-guy domains. I would like to create another list of those same good guys that can be added to each day as they show up, then compare it to the above main list and delete the good guy domains before adding to the access.db. Greylisting will be much more effective than this approach, and is easier to implement. Combine that with sbl-xbl and maybe a few other DNSBLs, add greet_pause of five or ten seconds, and you have much more effectiveness with less false positives and much less maintenance. Adding clamav rounds out the whole thing. I wrote an article that covers some of this: http://www.wonkity.com/~wblock/greylist.pdf -Warren Block * Rapid City, South Dakota USA This shell script is just icing on the cake -- In addition to the DNSBLs, I have had all of those other filters running for years plus milter-regex in the front line, then greylist, then clamav, SA. It's the SA (SpamAssassin) that provides me the list of bad-guy domains. It's a very short list so I can always still eyeball it and remove any obvious good ones. It's just sometimes I have made a mistake and let in a good guy, say, like one of my own domains. If I had a "good-guy list" to watch over my shoulder and check the bad-guy list before adding to the access-reject, then those would never happen again. Those bad guys are pretty obvious by their names. Even if the domains are "throw-aways", I can stop a few more this way although I have to purge the sendmail access DB ever so often. My users might get 1 or 2 spams a month with my line of defenses. Takes a lot of my time, but worth the results. This shell would be a big help tho. Would appreciate any more tips on how to have my daily bad-guy list checked against the good-guy list. Both are flat files with the domains listed in a single column. Thanks guys! Jack See comm(1). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell question
From: Warren Block <[EMAIL PROTECTED]> To: Jack Stone <[EMAIL PROTECTED]> CC: freebsd-questions@freebsd.org Subject: Re: Shell question Date: Wed, 25 Oct 2006 21:35:55 -0600 (MDT) On Wed, 25 Oct 2006, Jack Stone wrote: Folks: I have managed to piece together a shell script that is able to retrieve the domains from the spams of the day and summarize those in a special file that can then be added to the sendmail's rejects in the access.db. But, first I have to eyeball the list and remove any obvious good-guy domains. I would like to create another list of those same good guys that can be added to each day as they show up, then compare it to the above main list and delete the good guy domains before adding to the access.db. Greylisting will be much more effective than this approach, and is easier to implement. Combine that with sbl-xbl and maybe a few other DNSBLs, add greet_pause of five or ten seconds, and you have much more effectiveness with less false positives and much less maintenance. Adding clamav rounds out the whole thing. I wrote an article that covers some of this: http://www.wonkity.com/~wblock/greylist.pdf -Warren Block * Rapid City, South Dakota USA This shell script is just icing on the cake -- In addition to the DNSBLs, I have had all of those other filters running for years plus milter-regex in the front line, then greylist, then clamav, SA. It's the SA (SpamAssassin) that provides me the list of bad-guy domains. It's a very short list so I can always still eyeball it and remove any obvious good ones. It's just sometimes I have made a mistake and let in a good guy, say, like one of my own domains. If I had a "good-guy list" to watch over my shoulder and check the bad-guy list before adding to the access-reject, then those would never happen again. Those bad guys are pretty obvious by their names. Even if the domains are "throw-aways", I can stop a few more this way although I have to purge the sendmail access DB ever so often. My users might get 1 or 2 spams a month with my line of defenses. Takes a lot of my time, but worth the results. This shell would be a big help tho. Would appreciate any more tips on how to have my daily bad-guy list checked against the good-guy list. Both are flat files with the domains listed in a single column. Thanks guys! Jack _ Try Search Survival Kits: Fix up your home and better handle your cash with Live Search! http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmtagline ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell question
On Wed, 25 Oct 2006, Jack Stone wrote: Folks: I have managed to piece together a shell script that is able to retrieve the domains from the spams of the day and summarize those in a special file that can then be added to the sendmail's rejects in the access.db. But, first I have to eyeball the list and remove any obvious good-guy domains. I would like to create another list of those same good guys that can be added to each day as they show up, then compare it to the above main list and delete the good guy domains before adding to the access.db. Greylisting will be much more effective than this approach, and is easier to implement. Combine that with sbl-xbl and maybe a few other DNSBLs, add greet_pause of five or ten seconds, and you have much more effectiveness with less false positives and much less maintenance. Adding clamav rounds out the whole thing. I wrote an article that covers some of this: http://www.wonkity.com/~wblock/greylist.pdf -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell question
On Wed, Oct 25, 2006 at 09:53:47AM -0500, Jack Stone wrote: > I have managed to piece together a shell script that is able to retrieve > the domains from the spams of the day and summarize those in a special file > that can then be added to the sendmail's rejects in the access.db. But, > first I have to eyeball the list and remove any obvious good-guy domains. The domains from the spams? That's almost always pretty useless: 1. The only reliable information is what's in the SMTP envelope. Headers like From: etc... are always spoofed and almost always pointing to either inexistant or innocent victim domains (which then get flooded by bounces). 2. The IP-Addresses from the senders (from the SMTP envelope or at most the last Received: header, if you don't operate your own MTA), will almost always point to PTR of some big broadband ISPs hosting some infected Windows spam drones. Blocking the *domain* name of the ISP (esp. the big ones) would be is silly, because that would lock out a lot of legitimate users that send mails through their (ISPs) mailers. The bottom line: you'll end up banning 99% of innocent domains, and still get flooded with spams, since spammers can and do fake a HUGE amount of domain names. However, blocking IP addresses using RBLs like spamhaus.org, greylisting, and, to a lesser extent, using SPF (once it gets more widely adopted) can do wonders, if you operate your own MTA. E.g. the following Postfix configuration in /usr/local/etc/postfix/main.cf is a bit tight, but very effective in most setups: smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, reject_unauth_pipelining, reject_non_fqdn_recipient, reject_unknown_recipient_domain, # check_sender_access hash:/usr/local/etc/postfix/sender_access, # check_recipient_access hash:/usr/local/etc/postfix/recipient_access, # check_helo_access hash:/usr/local/etc/postfix/secondary_mx_access, # reject_rbl_client bl.spamcop.net, reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client list.dsbl.org, reject_rbl_client dnsbl.njabl.org, reject_rbl_client relays.ordb.org, reject_rbl_client opm.blitzed.org, # reject_rbl_client dnsbl.sorbs.net, check_policy_service unix:private/spfpolicy, check_policy_service inet:127.0.0.1:10023, # The following are a bit tight, but they won't do any harm reject_invalid_hostname, reject_non_fqdn_hostname, reject_unknown_hostname, reject_non_fqdn_sender, reject_unknown_sender_domain, # check_client_access hash:/usr/local/etc/postfix/client_access, reject_unknown_client One can do even more, but that should be enough for now, considerung the current "state of the art" of the spam engines. If you prefer sendmail, a sendmail guru will certainly help translating most directives from this config... ;) > Jack Good luck, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shell question
Jack Stone wrote: > Folks: > I have managed to piece together a shell script that is able to retrieve > the domains from the spams of the day and summarize those in a special > file that can then be added to the sendmail's rejects in the access.db. > But, first I have to eyeball the list and remove any obvious good-guy > domains. > > I would like to create another list of those same good guys that can be > added to each day as they show up, then compare it to the above main > list and delete the good guy domains before adding to the access.db. > > What would be the best way of doing the above in a few lines added to my > (sh) shell script? > hmm probably not the best but egrep -v -f goodguys.txt spamers.txt will only spit out the domains in spammers.txt that are not in goodguys.txt goodguys.txt is a file of good guys domains in the format aa.com|bb.com|cc.com|dd.com creating this file programaticly shouldnt be too hard. not sure how well this will scale as i only tested it with 5 or so names. Vince > BTW: The "spam" list of domains are listed in a column one below the > other in a flat file. > > Appreciate your usual fine advice on this. Hope I have been clear. > > Thanks! > > Jack > > _ > Find a local pizza place, music store, museum and more…then map the best > route! http://local.live.com?FORM=MGA001 > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Shell question
Folks: I have managed to piece together a shell script that is able to retrieve the domains from the spams of the day and summarize those in a special file that can then be added to the sendmail's rejects in the access.db. But, first I have to eyeball the list and remove any obvious good-guy domains. I would like to create another list of those same good guys that can be added to each day as they show up, then compare it to the above main list and delete the good guy domains before adding to the access.db. What would be the best way of doing the above in a few lines added to my (sh) shell script? BTW: The "spam" list of domains are listed in a column one below the other in a flat file. Appreciate your usual fine advice on this. Hope I have been clear. Thanks! Jack _ Find a local pizza place, music store, museum and more then map the best route! http://local.live.com?FORM=MGA001 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: shell question
On Wed, 6 Apr 2005, Richard Caley wrote: > In article <[EMAIL PROTECTED]>, mrspock (m) writes: > > m> The problem is that I don't want to use the temporary > m> file that I used above (stdout, stderr, out), I just > m> want a "filter" > > If you want to rearange the output so that all the errors are after > all the non errors, then you are going to need storage of some sort. I > think that is logically unavoidable. > > There may be some kind of shuffle you can do with named pipes or > something, but those kind of things have limited storage. Any time > your command produces more error output than that space can hold, it > will be stopped. Since you are not reading that stream until the main > output is finished you'd then have a deadlock. > > -- > Mail me as [EMAIL PROTECTED]_O_ > |< Thank you, Richard. Efectively, I found that is easier to create a temporary file with one of the output files, in this case "stderr". Stderr is used, in this case to create a listing of the data that the program is using and, occasionally, it issues an error message, in this case the program stops. I finally programmed this process in this way: program 2> tempfile | (cat && a2sp tempfile) | ps2pdf As I already stated, my program is creating a PostScript output in its stdout and a "listing" in the stderr file. a2ps is converting this listing to PostScript and both of them, finally, are converted to a PDF document with GhostScripts [in the ports]. Finally, the name "pipes" is very precise to describe what is happening with the "streams"; obviously, if I want to process one of the streams after the other one, I need to contain the "water" of the second temporally. Thanks for your time and your help. Eduardo. PS. Perhaps you are interested in visiting my page: http://michelle.esfm.ipn.mx/~mrspock/superspiro Cut & Paste one of the examples and execute the program at the end of the page. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: shell question
On Tue, 5 Apr 2005, Björn König wrote: > mrspock at esfm dot ipn dot mx wrote: > > > I need to concatenate the standard output and then > standard > > error output in a file, but I need to convert the standard > > > output into PostScript before the concatenation. > > > > program stdout 2> stderr > > cat stdout > out > > a2ps stderr >> out > > > > a2ps is in the ports and it converts plain text into > PostScript. > > > > The problem is that I don't want to use the temporary file > > > that I used above (stdout, stderr, out), I just want a > "filter" > > program < stdin 3>&1 1>&2 2>&3 | a2ps > > Regards Björn > Thanks for your help, Björn. I think I'd better study a little more this redirection operators. Thanks again. Eduardo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: shell question
In article <[EMAIL PROTECTED]>, mrspock (m) writes: m> The problem is that I don't want to use the temporary m> file that I used above (stdout, stderr, out), I just m> want a "filter" If you want to rearange the output so that all the errors are after all the non errors, then you are going to need storage of some sort. I think that is logically unavoidable. There may be some kind of shuffle you can do with named pipes or something, but those kind of things have limited storage. Any time your command produces more error output than that space can hold, it will be stopped. Since you are not reading that stream until the main output is finished you'd then have a deadlock. -- Mail me as [EMAIL PROTECTED]_O_ |< ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: shell question
On Tue, 5 Apr 2005, Björn König wrote: > > > > program stdout 2> stderr > > > cat stdout > out > > > a2ps stdout >> out > > You meant > >program stdout 2> stderr >cat stdout > out >a2ps **stderr** >> out > > Don't you? > yes! sorry! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: shell question
> > program stdout 2> stderr > > cat stdout > out > > a2ps stdout >> out You meant program stdout 2> stderr cat stdout > out a2ps **stderr** >> out Don't you? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: shell question
mrspock at esfm dot ipn dot mx wrote: > I need to concatenate the standard output and then standard > error output in a file, but I need to convert the standard > output into PostScript before the concatenation. > > program stdout 2> stderr > cat stdout > out > a2ps stdout >> out > > a2ps is in the ports and it converts plain text into PostScript. > > The problem is that I don't want to use the temporary file > that I used above (stdout, stderr, out), I just want a "filter" program < stdin 3>&1 1>&2 2>&3 | a2ps Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
shell question
Hello FreeBSD gurus! I address you in hope of enlightment. Here is the problem: I have a program that creates a PostScript output and writes it to its standard output. This program also writes diagnostic messages to the standard error output at the same time, in this case the messages are written in plain text. I need to concatenate the standard output and then standard error output in a file, but I need to convert the standard output into PostScript before the concatenation. program stdout 2> stderr cat stdout > out a2ps stdout >> out a2ps is in the ports and it converts plain text into PostScript. The problem is that I don't want to use the temporary file that I used above (stdout, stderr, out), I just want a "filter" In a diagram, it can be seen as: stdin ==> program ==> [stdout, a2ps(stderr)] I have tried: cat stdin | program 2> tmp | ( cat && a2ps tmp ) but I still need a temporary file. Can it be done? Can you help me and tell me how ? Thanks in advance. -Eduardo. PS. Please, answer to my e-mail address, I am not subscribed to the list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
On Fri, 14 Jan 2005 06:55:19 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > I don't see the perl module for Text::Aspell in the ports, by doing > all sorts of permutations of this: > cd /usr/ports && make search name=p5 |grep Aspell Ah, sorry, didn't see that in your posts about this. > So, once again, sorry if this is really basic stuff, but how to I get > Text::Aspell - Perl interface to the Aspell library installed? This seems a good CPAN reference, including info on how to debug test failures: http://sial.org/howto/perl/life-with-cpan/ (first Google result on "perl cpan shell test fail") Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto (DONE)
On Fri, Jan 14, 2005 at 06:55:19AM -0900, Andy Firman wrote: > On Fri, Jan 14, 2005 at 10:29:05AM -0500, Bryan Fullerton wrote: > > On Fri, 14 Jan 2005 06:20:49 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > > > On Fri, Jan 14, 2005 at 03:08:23PM +, Gary Hayers wrote: > > [snip] > > I don't see the perl module for Text::Aspell in the ports, by doing > all sorts of permutations of this: > cd /usr/ports && make search name=p5 |grep Aspell > > So, once again, sorry if this is really basic stuff, but how to I get > Text::Aspell - Perl interface to the Aspell library installed? There is no port for Text::Aspell, so I had to install from source. Text::Aspell depends on XML::DOM and CGI, which I installed from the ports system. (p5-XML-DOM-1.43, p5-CGI.pm-3.05) The "make test" keeps failing for the source install of Text::Aspell, but I did "make install" anyway, and all seems to be working now. Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
On Fri, Jan 14, 2005 at 10:29:05AM -0500, Bryan Fullerton wrote: > On Fri, 14 Jan 2005 06:20:49 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > > On Fri, Jan 14, 2005 at 03:08:23PM +, Gary Hayers wrote: > [snip] > > > If you have the Ports tree installed you can install it from the ports > > > tree > > > > > > # cd /usr/ports/textproc/p5-XML-DOM && make install clean > > > > Understood. But I am having a hard time figuring out how Perl modules > > "should" get installed on a system. > > The generally preferred way on a FreeBSD system is to use the FreeBSD > ports as noted above. > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Yeah...I understand that, I read the whole manual, and I read the whole book, The Complete FreeBSD. Sorry if I am missing something really basic. I don't see the perl module for Text::Aspell in the ports, by doing all sorts of permutations of this: cd /usr/ports && make search name=p5 |grep Aspell So, once again, sorry if this is really basic stuff, but how to I get Text::Aspell - Perl interface to the Aspell library installed? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
On Fri, 14 Jan 2005 06:20:49 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > On Fri, Jan 14, 2005 at 03:08:23PM +, Gary Hayers wrote: [snip] > > If you have the Ports tree installed you can install it from the ports tree > > > > # cd /usr/ports/textproc/p5-XML-DOM && make install clean > > Understood. But I am having a hard time figuring out how Perl modules > "should" get installed on a system. The generally preferred way on a FreeBSD system is to use the FreeBSD ports as noted above. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
On Fri, Jan 14, 2005 at 03:08:23PM +, Gary Hayers wrote: > Andy Firman wrote: > >Using FreeBSD 4.10 stable, perl-5.8.5 installed from ports. > > > >su-2.05b# perl -v > >This is perl, v5.8.5 built for i386-freebsd-64int > > > >When using perl -MCPAN -e shell, I can install the bundle fine, > >but the when I try to install XML::DOM, or Text::Aspell, they fail. > > > >Where can I go for help on getting the bsdpan ports installed? > >Or is there a howto on this stuff because I am clueless? > > > >Thanks, > >Andy > > If you have the Ports tree installed you can install it from the ports tree > > # cd /usr/ports/textproc/p5-XML-DOM && make install clean Understood. But I am having a hard time figuring out how Perl modules "should" get installed on a system. One can use perl -MCPAN -e shell to install modules right? One can install from source in /usr/local/src right? One can install perl p5-Bla-Bla-1.03 from the ports right? Which is the right way? I have learned in the past it is very good practice to stick with the system package management system if at all possible. It will save you in the future big time with dependancey problems. Hence my hesitation with moving forward by throwing anything at the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
Andy Firman wrote: Using FreeBSD 4.10 stable, perl-5.8.5 installed from ports. su-2.05b# perl -v This is perl, v5.8.5 built for i386-freebsd-64int When using perl -MCPAN -e shell, I can install the bundle fine, but the when I try to install XML::DOM, or Text::Aspell, they fail. Where can I go for help on getting the bsdpan ports installed? Or is there a howto on this stuff because I am clueless? Thanks, Andy If you have the Ports tree installed you can install it from the ports tree # cd /usr/ports/textproc/p5-XML-DOM && make install clean ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: perl -MCPAN -e shell question - need a howto
On Fri, Jan 14, 2005 at 09:42:06AM -0500, Bryan Fullerton wrote: > On Fri, 14 Jan 2005 04:34:33 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > > > > Using FreeBSD 4.10 stable, perl-5.8.5 installed from ports. > > > > su-2.05b# perl -v > > This is perl, v5.8.5 built for i386-freebsd-64int > > > > When using perl -MCPAN -e shell, I can install the bundle fine, > > but the when I try to install XML::DOM, or Text::Aspell, they fail. > > What are the errors when they fail? Trying to install the XML::DOM I get this: cpan> install XML::DOM Manifying blib/man3/XML::DOM::Parser.3 Manifying blib/man3/XML::DOM::Comment.3 Manifying blib/man3/XML::DOM::Element.3 Manifying blib/man3/XML::DOM::XMLDecl.3 Manifying blib/man3/XML::DOM::CDATASection.3 Manifying blib/man3/XML::DOM::Node.3 Manifying blib/man3/XML::DOM::ElementDecl.3 Manifying blib/man3/XML::DOM::DOMImplementation.3 Manifying blib/man3/XML::DOM::EntityReference.3 Manifying blib/man3/XML::DOM::AttDef.3 Manifying blib/man3/XML::DOM::Text.3 Manifying blib/man3/XML::DOM::NodeList.3 Manifying blib/man3/XML::DOM::CharacterData.3 /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.5 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/build_dom...ok t/dom_astress.ok t/dom_attrok t/dom_cdata...ok t/dom_documenttypeok t/dom_encode..ok t/dom_example.ok t/dom_extent..ok t/dom_jp_astress..ok t/dom_jp_attr.FAILED tests 3, 9, 12, 14, 19, 22 Failed 6/23 tests, 73.91% okay t/dom_jp_cdataFAILED test 3 Failed 1/3 tests, 66.67% okay t/dom_jp_example..ok t/dom_jp_minusFAILED test 2 Failed 1/2 tests, 50.00% okay t/dom_jp_modify...FAILED test 16 Failed 1/16 tests, 93.75% okay t/dom_jp_printFAILED tests 2-3 Failed 2/3 tests, 33.33% okay t/dom_minus...ok t/dom_modify..ok t/dom_noexpandok t/dom_print...ok t/dom_templateok t/dom_textok Failed Test Stat Wstat Total Fail Failed List of Failed --- t/dom_jp_attr.t 236 26.09% 3 9 12 14 19 22 t/dom_jp_cdata.t 31 33.33% 3 t/dom_jp_minus.t 21 50.00% 2 t/dom_jp_modify.t 161 6.25% 16 t/dom_jp_print.t 32 66.67% 2-3 Failed 5/21 test scripts, 76.19% okay. 11/129 subtests failed, 91.47% okay. *** Error code 2 Stop in /root/.cpan/build/XML-DOM-1.43. /usr/bin/make test -- NOT OK Running make install make test had returned bad status, won't install without force # Then with installing Text::Aspell I get this: cpan> install Text::Aspell CPAN: Storable loaded ok Going to read /root/.cpan/Metadata Database was generated on Thu, 13 Jan 2005 09:50:06 GMT Running install for module Text::Aspell Running make for H/HA/HANK/Text-Aspell-0.04.tar.gz CPAN: Digest::MD5 loaded ok CPAN: Compress::Zlib loaded ok Checksum for /root/.cpan/sources/authors/id/H/HA/HANK/Text-Aspell-0.04.tar.gz ok Scanning cache /root/.cpan/build for sizes Text-Aspell-0.04/ Text-Aspell-0.04/t/ Text-Aspell-0.04/t/test.t Text-Aspell-0.04/MANIFEST Text-Aspell-0.04/typemap Text-Aspell-0.04/Aspell.xs Text-Aspell-0.04/META.yml Text-Aspell-0.04/Aspell.pm Text-Aspell-0.04/Changes Text-Aspell-0.04/Makefile.PL Text-Aspell-0.04/README Removing previously used /root/.cpan/build/Text-Aspell-0.04 CPAN.pm: Going to build H/HA/HANK/Text-Aspell-0.04.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Text::Aspell cp Aspell.pm blib/lib/Text/Aspell.pm /usr/local/bin/perl5.8.5 /usr/local/lib/perl5/5.8.5/ExtUtils/xsubpp -noprototypes -typemap /usr/local/lib/perl5/5.8.5/ExtUtils/typemap -typemap typemap Aspell.xs > Aspell.xsc && mv Aspell.xsc Aspell.c cc -c-DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.5/BSDPAN" -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include -O -pipe-DVERSION=\"0.04\" -DXS_VERSION=\"0.04\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.5/mach/CORE" Aspell.c Aspell.c: In function `XS_Text__Aspell_DESTROY': Aspell.c:98: warning: cast to pointer from integer of different size Aspell.c: In function `XS_Text__Aspell_create_speller': Aspell.c:125: warning: cast to pointer from integer of different size Aspell.c: In function `XS_Text__Aspell_print_config': Aspell.c:158: warning: cast to pointer from integer of different size Aspell.c: In function `XS_Text__Aspell_set_option': Aspell.c:194: warning: cast to pointer from integer of different size Aspell.c: In function `XS_Text__Aspell_remove_option': Aspell.c:230: warning: cast to pointer from integer of different size Aspell.c: In function `XS_Text__Aspell_get_option': Aspell.c:266: warning: cast to pointer from integer of different size Aspell.c: In functi
Re: perl -MCPAN -e shell question - need a howto
On Fri, 14 Jan 2005 04:34:33 -0900, Andy Firman <[EMAIL PROTECTED]> wrote: > > Using FreeBSD 4.10 stable, perl-5.8.5 installed from ports. > > su-2.05b# perl -v > This is perl, v5.8.5 built for i386-freebsd-64int > > When using perl -MCPAN -e shell, I can install the bundle fine, > but the when I try to install XML::DOM, or Text::Aspell, they fail. What are the errors when they fail? Bryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
perl -MCPAN -e shell question - need a howto
Using FreeBSD 4.10 stable, perl-5.8.5 installed from ports. su-2.05b# perl -v This is perl, v5.8.5 built for i386-freebsd-64int When using perl -MCPAN -e shell, I can install the bundle fine, but the when I try to install XML::DOM, or Text::Aspell, they fail. Where can I go for help on getting the bsdpan ports installed? Or is there a howto on this stuff because I am clueless? Thanks, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
