Spamassassin RBL's

[Peter Pluta]

How can I enable spamassasssin RBL's. I'm running FreeBSD 6.1, postfix,
amavisd-new, and spamassassin with razor. I'm getting many spams that
shouldn't be getting thru with RBL's. I havent been able to find anything
useful on Google that can explain how to get RBL working with spamassassin.
Any feedback would be greatly appreciated. 
-- 
View this message in context: 
http://www.nabble.com/Spamassassin-RBL%27s-tf3896464.html#a11046174
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Xorg failed to start after upgrading to 7.2

[Manolis Kiagias]

[EMAIL PROTECTED] wrote:
> On 09/06/07, Xihong Yin <[EMAIL PROTECTED]> top-posted:
>> Thank you for answering my question.
>>
>> On Sat, 9 Jun 2007, Manolis Kiagias wrote:
>>
>> > Xihong Yin wrote:
>> > > After upgrading Xorg from 6.8 to 7.2, I got the following error
>> when I start X.
>> > >
>> > > (EE) Failed to load module "xtt" (module does not exist, 0 )
>> > > (EE) Failed to load module "vesa" (module does not exist, 0 )
>> > > (EE) Failed to load module "module" (module does not exist, 0 )
>> > > (EE) Failed to load module "kbd" (module does not exist, 0 )
>> > >
>> > > Before upgrading Xorg, I just upgraded FreeBSD from 6.0 to 6.2.
>> > >
>
>> > Quick guess: you are still using the same xorg.conf from your 6.8
>> > install. You need to change the
>> > ModulePath to /usr/local/lib/xorg/modules
>
>> I did change my ModulePath to /usr/local/lib/xorg/modules in my
>> xorg.conf file.
>> Under my /usr/local/lib/xorg/modules, there are no such libs as xtt,
>> vesa,
>> mouse, and kbd.
>
> There should be an entry "xorg-7.2"
> in /var/db/pkg (I am going on a hunch
> here), if not you need to install ports/x11/xorg
>
> It would probably not be a bad idea to rerun
> X -configure and ten-finger-merge the results
> with your old config file.
>
You may also do a pkg_info | grep xorg and see what xorg packages where
actually installed.
My guess is you are missing the xorg-drivers metaport for some reason
(since you are missing such basic things as kbd and vesa) but doing a
complete install of ports/x11/xorg as suggested wouldn't harm. If you
want to go with the drivers only thing, the metaport would be
ports/x11-drivers/xorg-drivers
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Upgrading to 6.2-RELEASE from 6.2-STABLE

[Mark Stout]

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 09, 2007 7:32 PM
> To: Mark Stout
> Cc: freebsd-questions@freebsd.org
> Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
>
>
> On 09/06/07, Mark Stout <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: Friday, June 08, 2007 10:30 PM
> > > To: Mark Stout
> > > Cc: freebsd-questions@freebsd.org
> > > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
> > >
> > >
> > > On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote:
> > >
> > > >
> > > > I'd prefer to remain at 6.2-STABLE but I can't find where
> the problem is
> > > > with these IP errors.  I'm figuring I've got a mixed code
> and that's the
> > > > root cause but I'm not sure.
> > >
> > > Did you remove your object directories before
> > > starting the build?
> > > Did you build without an /etc/make.conf?
> > >
> > I did not remove the obj directories and everything in my /etc/make.conf
> > file is commented out except for USA_RESIDENT and PERL_VER=5.8.8 and
> > PERL_VERSION=5.8.8
> >
>
> On a mad hunch I would suspect stale files in /usr/obj/
> If they are still there (and the cause of your problems)
> they will muss up your build on RELENG_6_2 as well.
>
> --
> --

So how should I fix this?

Thank you,
Mark Stout
VPM Global Internet Services, Inc.
530-626-4218 x205 Office
530-626-7182 Fax
530-554-9295 VoIP
916-240-2850 Cell
www.vpm.com 

This email and any files transmitted with it are confidential and intended
solely for the use of the individual to whom they are addressed.  If you are
not the intended recipient, you are hereby notified that any use or
dissemination of this communication is strictly prohibited, and asked to
notify us immediately, then delete this email. E-mail transmission cannot be
guaranteed to be secure or error-free and VPM Global Internet Services, Inc.
does not accept liability for any errors or omissions in the contents of
this message.  Any views or opinions presented are solely those of the
author and do not necessarily represent those of VPM Global Internet
Services, Inc.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

The FreeBSD Diary: 2007-05-20 - 2007-06-09

[Dan Langille]

The FreeBSD Diary contains a large number of practical 
examples and how-to guides.  This message is posted weekly
to freebsd-questions@freebsd.org with the aim of letting people
know what's available on the website.  Before you post a question
here it might be a good idea to first search the mailing list 
archives  
and/or The FreeBSD Diary . 


-- 
Dan Langille
BSDCan - http://www.BSDCan.org/ - BSD Conference

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading to 6.2-RELEASE from 6.2-STABLE

[[EMAIL PROTECTED]]

On 09/06/07, Mark Stout <[EMAIL PROTECTED]> wrote:




> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 08, 2007 10:30 PM
> To: Mark Stout
> Cc: freebsd-questions@freebsd.org
> Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE
>
>
> On 08/06/07, Mark Stout <[EMAIL PROTECTED]> wrote:
>
> >
> > I'd prefer to remain at 6.2-STABLE but I can't find where the problem is
> > with these IP errors.  I'm figuring I've got a mixed code and that's the
> > root cause but I'm not sure.
>
> Did you remove your object directories before
> starting the build?
> Did you build without an /etc/make.conf?
>
I did not remove the obj directories and everything in my /etc/make.conf
file is commented out except for USA_RESIDENT and PERL_VER=5.8.8 and
PERL_VERSION=5.8.8



On a mad hunch I would suspect stale files in /usr/obj/
If they are still there (and the cause of your problems)
they will muss up your build on RELENG_6_2 as well.

--
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Xorg failed to start after upgrading to 7.2

[[EMAIL PROTECTED]]

On 09/06/07, Xihong Yin <[EMAIL PROTECTED]> top-posted:

Thank you for answering my question.

On Sat, 9 Jun 2007, Manolis Kiagias wrote:

> Xihong Yin wrote:
> > After upgrading Xorg from 6.8 to 7.2, I got the following error when I 
start X.
> >
> > (EE) Failed to load module "xtt" (module does not exist, 0 )
> > (EE) Failed to load module "vesa" (module does not exist, 0 )
> > (EE) Failed to load module "module" (module does not exist, 0 )
> > (EE) Failed to load module "kbd" (module does not exist, 0 )
> >
> > Before upgrading Xorg, I just upgraded FreeBSD from 6.0 to 6.2.
> >



> Quick guess: you are still using the same xorg.conf from your 6.8
> install. You need to change the
> ModulePath to /usr/local/lib/xorg/modules



I did change my ModulePath to /usr/local/lib/xorg/modules in my xorg.conf file.
Under my /usr/local/lib/xorg/modules, there are no such libs as xtt, vesa,
mouse, and kbd.


There should be an entry "xorg-7.2"
in /var/db/pkg (I am going on a hunch
here), if not you need to install ports/x11/xorg

It would probably not be a bad idea to rerun
X -configure and ten-finger-merge the results
with your old config file.

--
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Php5 port and Apache Module

[Christopher Hilton]

Jonathan Horne wrote:

Bob wrote:

The php4 & php5 port apache module used to be default before FBSD 6.0.
Many people before you on this list have wanted the php4/5 apache module
turned back on as default but so far the port maintainer has not done
anything
in any way of justifying removing the apache module from the default setting
or re-enable it as the default.


[snip]



seems like it was removed from the default config of lang/php5 for security
reasons.  many people who do build php5 do not need the apache module, so no
sense building it if its not needed.

cd /usr/ports/lang/php5
make config
(edit your choices)
make deinstall
make reinstall

its just one of those things that you learn to live with after a while.



Everyone seems to be misunderstanding my question. I'm aware of how to 
build mod_php5. I'm curious about why the default configuration builds 
php5 as a standalone CLI and CGI rather than as an apache module. I'm 
assuming that there is some good engineering behind this decision but 
I'd like to know a little more about that engineering. Is there some 
advantage to running php as a Fast CGI process?


-- Chris

P.S. Sorry Bob, I've scanned the commit logs for the port and there is 
no mention of security problems with mod_php5.so. To tell the truth I 
cannot imagine that there would be any security issues in mod_php5.so 
that didn't also exist in /usr/local/bin/php-cgi. I could be wrong here 
though and then I would have the answer to my question.


--
  __o  "All I was doing was trying to get home from work."
_`\<,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hilton
pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Xorg failed to start after upgrading to 7.2

[Xihong Yin]

Thank you for answering my question.

I did change my ModulePath to /usr/local/lib/xorg/modules in my xorg.conf file.
Under my /usr/local/lib/xorg/modules, there are no such libs as xtt, vesa,
mouse, and kbd.

Xihong



On Sat, 9 Jun 2007, Manolis Kiagias wrote:

> Xihong Yin wrote:
> > After upgrading Xorg from 6.8 to 7.2, I got the following error when I 
> > start X.
> >
> > (EE) Failed to load module "xtt" (module does not exist, 0 )
> > (EE) Failed to load module "vesa" (module does not exist, 0 )
> > (EE) Failed to load module "module" (module does not exist, 0 )
> > (EE) Failed to load module "kbd" (module does not exist, 0 )
> >
> > Before upgrading Xorg, I just upgraded FreeBSD from 6.0 to 6.2.
> >
> > Please help me!
> >
> > Xihong
> >
> > --
> > Get a free email account with anti spam protection.
> > http://www.bluebottle.com
> >
> > ___
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >
> >
> >
> Quick guess: you are still using the same xorg.conf from your 6.8
> install. You need to change the
> ModulePath to /usr/local/lib/xorg/modules
>
>

--
Get a free email address with REAL anti-spam protection.
http://www.bluebottle.com

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found

[Jin Guojun [VFFS]]

I believe that this is a memory sub-system bug somewhere because 
anything equal to or below 1G


   options MAXDSIZ="(1024*1024*1024)"

will work regardless how many memory is installed in the system.
I doubt this could be a hardware related issue although is memory size 
related.


Finally find cause but no idea why -- in kernel configuration, 
following line causes the problem:


   options MAXDSIZ="(2097152U*1024)"

Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen 
for some program?


Jin Guojun [VFFS] wrote:

I have multiple FreeBSD 6.2 machines with different hardware, but one 
of them encountered

this strange error when running program "wine".
I could not figure out what causes such error since 
/libexec/ld-elf.so.1 absolutely exists, otherwise

no program will run.

It does not matter if the wine is pre-compiled in packages or I built 
it from ports.

All other machine do NOT have such problem.

I reinstalled this machine a few times, and it always does the same 
thing. However other programs

run well.
Would this is related to some particular hardware issue?
This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB 
memory.
Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel 
Laptop, and AMD XP 2100+,

and none of them ever had such problem.

129 /data: ldd `which wine`
/usr/local/bin/wine:
ELF interpreter /libexec/ld-elf.so.1 not found
/usr/local/bin/wine: signal 6

130 /data: ll /libexec/ld-elf.so.1
-r-xr-xr-x  1 root  wheel  158712 Jan 11 23:39 /libexec/ld-elf.so.1*

131 /data: wine
ELF interpreter /libexec/ld-elf.so.1 not found
Abort

132 /data: which wine
/usr/local/bin/wine

Does someone have an idea what is happening here?

-Jin




--
 Jin Guojun --- v --- [EMAIL PROTECTED] ---
Distributed Systems Department  http://www.dsd.lbl.gov/~jin
Lawrence Berkeley National Laboratory,  Berkeley, CA 94720

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found

[Jin Guojun [VFFS]]

Finally find cause but no idea why -- in kernel configuration, following 
line causes the problem:


   options MAXDSIZ="(2097152U*1024)"

Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for 
some program?


Jin Guojun [VFFS] wrote:

I have multiple FreeBSD 6.2 machines with different hardware, but one 
of them encountered

this strange error when running program "wine".
I could not figure out what causes such error since 
/libexec/ld-elf.so.1 absolutely exists, otherwise

no program will run.

It does not matter if the wine is pre-compiled in packages or I built 
it from ports.

All other machine do NOT have such problem.

I reinstalled this machine a few times, and it always does the same 
thing. However other programs

run well.
Would this is related to some particular hardware issue?
This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB 
memory.
Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel Laptop, 
and AMD XP 2100+,

and none of them ever had such problem.

129 /data: ldd `which wine`
/usr/local/bin/wine:
ELF interpreter /libexec/ld-elf.so.1 not found
/usr/local/bin/wine: signal 6

130 /data: ll /libexec/ld-elf.so.1
-r-xr-xr-x  1 root  wheel  158712 Jan 11 23:39 /libexec/ld-elf.so.1*

131 /data: wine
ELF interpreter /libexec/ld-elf.so.1 not found
Abort

132 /data: which wine
/usr/local/bin/wine

Does someone have an idea what is happening here?

-Jin



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading from XFree86 to Xorg

[Warren Liddell]

At 06:33 PM 9/06/2007, Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Warren Liddell wrote:
> Up untill now i have been using XFree86 and being as it is basically no
> longer updated or maintained, so im wishing to know the basic most
> easiest way to change over from XFree to Xorg

If you're still running XFree86 because you're on a FreeBSD 4.x system
where that is the default, then do not even think about trying this as
you will completely banjax your system.  Upgrade to 6.2 first.


All ready running 6.2-STABLE .. so will give your steps a try and see 
how things go from there.  Thanks for the info. 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found

[Jin Guojun [VFFS]]

I have multiple FreeBSD 6.2 machines with different hardware, but one of 
them encountered

this strange error when running program "wine".
I could not figure out what causes such error since /libexec/ld-elf.so.1 
absolutely exists, otherwise

no program will run.

It does not matter if the wine is pre-compiled in packages or I built it 
from ports.

All other machine do NOT have such problem.

I reinstalled this machine a few times, and it always does the same 
thing. However other programs

run well.
Would this is related to some particular hardware issue?
This one is ECS 848P-A7 motherboard with Intel P4 506+ CPU, plus 2 GB 
memory.
Other machines are HP AMD64 laptop, DELL Dual XEON, DELL Intel Laptop, 
and AMD XP 2100+,

and none of them ever had such problem.

129 /data: ldd `which wine`
/usr/local/bin/wine:
ELF interpreter /libexec/ld-elf.so.1 not found
/usr/local/bin/wine: signal 6

130 /data: ll /libexec/ld-elf.so.1
-r-xr-xr-x  1 root  wheel  158712 Jan 11 23:39 /libexec/ld-elf.so.1*

131 /data: wine
ELF interpreter /libexec/ld-elf.so.1 not found
Abort

132 /data: which wine
/usr/local/bin/wine

Does someone have an idea what is happening here?

-Jin

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

problems building ftgl

[Eric Mesa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Whenever I try to build blender, it stops at ftgl, and I get:

checking GL/gl.h usability... no
checking GL/gl.h presence... no
checking for GL/gl.h... no
configure: error: GL/gl.h is needed
exit: Illegal number: please
exit: Illegal number: please

*** Error code 1

Stop in /usr/ports/graphics/ftgl.
*** Error code 1

Stop in /usr/ports/graphics/blender-devel

This is a headless system, so I don't have any GUIs installed.  I'm
just trying to install the minimum X needed for blender - so I may be
missing something.   The whole xorg 7.2 build process was clear as mud
for me.

Thanks for any help you can provide.

- --
Eric Mesa
[EMAIL PROTECTED]
http://www.ericsbinaryworld.com
Note:  All emails from this address should have a GPG signature.  If
you have the proper setup you can use this to confirm my identity and
that the email was not changed in transit.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGayUBPvU+8ApmWXIRAjBkAKCE5Xm03IMGZxGPpzlItW4ZFpe3gACgkigA
KLeEA5GY/N1+LksA7Vippow=
=sTn0
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Php5 port and Apache Module

[Jonathan Horne]

> Bob wrote:
>> The php4 & php5 port apache module used to be default before FBSD 6.0.
>> Many people before you on this list have wanted the php4/5 apache module
>> turned back on as default but so far the port maintainer has not done
>> anything
>> in any way of justifying removing the apache module from the default setting
>> or re-enable it as the default.
>>
>> This has forced all php4/5 users who want to use php in apache to compile it
>> manually with the apache module option selected during the make install of
>> the port.
>> When it was part of the default the php4/5 package was so quick to install
>> and ready to work with apache without any special handling.
>>
>> Hope you have better luck finding the justification for it being removed
>> from the default.
>>
>>
>
> I've been operating under the assumption that:
>
> There is some configuration you can do in
> /usr/local/etc/apache*/httpd.conf to get apache to use the CGI version
> of php;
>
> That this can be done without requiring a shebang (#! ...) line at the
> beginning of every php script;
>
> And that using php as a CGI script offers better performance than
> running it as an apache module.
>
> Looking on the internet though I cannot seem to find a set of
> instructions for configuring php-cgi in apache2. And once I do find the
> configuration I'll have to have a shebang at the start of every php
> module. Further all the performance comparisons that I've seen seem show
> that the performance of php as a FastCGI script and as an Apache Module
> are about equal.
>
> I don't want to get into a war. I'm still assuming that the port
> maintainer knows something that I don't. If I cannot get this running
> soon I guess that I will go back to mod_php5 and revisit this later.
>
> -- Chris
>
> --
>__o  "All I was doing was trying to get home from work."
>  _`\<,_   -Rosa Parks
> ___(*)/_(*)___
> Christopher Sean Hilton
>  pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
> ___

seems like it was removed from the default config of lang/php5 for security
reasons.  many people who do build php5 do not need the apache module, so no
sense building it if its not needed.

cd /usr/ports/lang/php5
make config
(edit your choices)
make deinstall
make reinstall

its just one of those things that you learn to live with after a while.

cheers,
--
Jonathan Horne
[EMAIL PROTECTED]
http://dfwlpiki.dfwlp.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Php5 port and Apache Module

[Christopher Hilton]

Bob wrote:

The php4 & php5 port apache module used to be default before FBSD 6.0.
Many people before you on this list have wanted the php4/5 apache module
turned back on as default but so far the port maintainer has not done
anything
in any way of justifying removing the apache module from the default setting
or re-enable it as the default.

This has forced all php4/5 users who want to use php in apache to compile it
manually with the apache module option selected during the make install of
the port.
When it was part of the default the php4/5 package was so quick to install
and ready to work with apache without any special handling.

Hope you have better luck finding the justification for it being removed
from the default.




I've been operating under the assumption that:

There is some configuration you can do in 
/usr/local/etc/apache*/httpd.conf to get apache to use the CGI version 
of php;


That this can be done without requiring a shebang (#! ...) line at the 
beginning of every php script;


And that using php as a CGI script offers better performance than 
running it as an apache module.


Looking on the internet though I cannot seem to find a set of 
instructions for configuring php-cgi in apache2. And once I do find the 
configuration I'll have to have a shebang at the start of every php 
module. Further all the performance comparisons that I've seen seem show 
that the performance of php as a FastCGI script and as an Apache Module 
are about equal.


I don't want to get into a war. I'm still assuming that the port 
maintainer knows something that I don't. If I cannot get this running 
soon I guess that I will go back to mod_php5 and revisit this later.


-- Chris

--
  __o  "All I was doing was trying to get home from work."
_`\<,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hilton
pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Xorg failed to start after upgrading to 7.2

[Manolis Kiagias]

Xihong Yin wrote:
> After upgrading Xorg from 6.8 to 7.2, I got the following error when I start 
> X.
>
> (EE) Failed to load module "xtt" (module does not exist, 0 )
> (EE) Failed to load module "vesa" (module does not exist, 0 )
> (EE) Failed to load module "module" (module does not exist, 0 )
> (EE) Failed to load module "kbd" (module does not exist, 0 )
>
> Before upgrading Xorg, I just upgraded FreeBSD from 6.0 to 6.2.
>
> Please help me!
>
> Xihong
>
> --
> Get a free email account with anti spam protection.
> http://www.bluebottle.com
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
>
>   
Quick guess: you are still using the same xorg.conf from your 6.8
install. You need to change the
ModulePath to /usr/local/lib/xorg/modules

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Xorg failed to start after upgrading to 7.2

[Xihong Yin]

After upgrading Xorg from 6.8 to 7.2, I got the following error when I start X.

(EE) Failed to load module "xtt" (module does not exist, 0 )
(EE) Failed to load module "vesa" (module does not exist, 0 )
(EE) Failed to load module "module" (module does not exist, 0 )
(EE) Failed to load module "kbd" (module does not exist, 0 )

Before upgrading Xorg, I just upgraded FreeBSD from 6.0 to 6.2.

Please help me!

Xihong

--
Get a free email account with anti spam protection.
http://www.bluebottle.com

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Php5 port and Apache Module

[Bob]

The php4 & php5 port apache module used to be default before FBSD 6.0.
Many people before you on this list have wanted the php4/5 apache module
turned back on as default but so far the port maintainer has not done
anything
in any way of justifying removing the apache module from the default setting
or re-enable it as the default.

This has forced all php4/5 users who want to use php in apache to compile it
manually with the apache module option selected during the make install of
the port.
When it was part of the default the php4/5 package was so quick to install
and ready to work with apache without any special handling.

Hope you have better luck finding the justification for it being removed
from the default.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Christopher Hilton
Sent: Saturday, June 09, 2007 3:51 PM
To: [EMAIL PROTECTED]; User Questions
Subject: Php5 port and Apache Module

I can see that if I build the php5 port it defaults to CLI and CGI mode
but the Apache module is not built. Am I wrong when I assume that the
Apache Module will have the best performance? I guess that I'd just like
to understand the engineering decisions behind the default in the port's
configuration.

-- Chris

--
   __o  "All I was doing was trying to get home from work."
 _`\<,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hilton
 pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
___
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]"

Bery does not work on FreeBSD 7-CURRENT

[Vlad GURDIGA]

Hello,

I've installed beryl today (tried both: from packages and compiled from
updated ports) on a FreeBSD 7-CURRENT.
When I run beryl from console I get this:

# beryl
Something went wrong with Xgl detection.
Something went wrong with Nvidia detection.Something went wrong with system
check.

When I run beryl-manager I get this:

# beryl-manager
# glxinfo: not found

** (beryl-manager:95111): WARNING **: No pidof, this may not work right.

** (beryl-manager:95111): WARNING **: No pidof, this may not work right.

** (beryl-manager:95111): WARNING **: No pidof, this may not work right.

** (beryl-manager:95111): WARNING **: No pidof, this may not work right.

The red diamond on beryl manager apears in the upper notification area of
GNOME desktop, but when I try to select the beryl window manager from it's
contextual menu, there is a flicker and in less than a second everything is
beck to normal look.

When I run beryl-settings I get this:

# beryl-settings
Traceback (most recent call last):
 File "/usr/local/bin/beryl-settings", line 22, in ?
--- endless pause --
^CFatal error 'Thread is not system scope.
' at line 316 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2)
Abort

Do I miss a package or something? Or it is just because of the development
version on FreeBSD?
Or maybe it is because of my ATI Radeon videocard?
The Xorg 7.2 and xf86-video-ati-6.6.3_2 were installed by the book
(/usr/port/UPDATING) and work fine.

Here is my uname -a:

# uname -a
FreeBSD kpax 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Mon Jun  4 00:03:11 EEST
2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

USB disk and write cache

[Dieter]

How do you set a USB disk's write cache to write-through mode?

As far as I can tell, putting "hw.ata.wc=0" in loader.conf
only affects directly connected PATA/SATA disks, not disks
connected via a USB-to-*ATA bridge.

Perhaps via camcontrol?  But "camcontrol modepage da0 -l -v"
returns nothing.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Php5 port and Apache Module

[Christopher Hilton]

I can see that if I build the php5 port it defaults to CLI and CGI mode 
but the Apache module is not built. Am I wrong when I assume that the 
Apache Module will have the best performance? I guess that I'd just like 
to understand the engineering decisions behind the default in the port's 
configuration.


-- Chris

--
  __o  "All I was doing was trying to get home from work."
_`\<,_   -Rosa Parks
___(*)/_(*)___
Christopher Sean Hilton
pgp key: D0957A2D/f5 30 0a e1 55 76 9b 1f 47 0b 07 e9 75 0e 14
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Using courier with dspam

[Graham Wheeler]

HI all

 

I'm having some difficulty with getting courier to work with dspam. I have
the courier local delivery agent configured to be:

 

DEFAULTDELIVERY="| /usr/local/bin/dspam --deliver=innocent --user
\$USER"

 

And I have dspam configured to use courier's maildrop:

 

TrustedDeliveryAgent "/usr/local/bin/maildrop -d %u"

UntrustedDeliveryAgent "/usr/local/bin/maildrop -d %u"

 

Now, mail fails to be delivered with:

 

Jun  9 12:26:08 server courierlocal:
id=02D2B4BC.466AFC77.2769,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]
.com>: /usr/local/bin/dspam: Permission denied

 

Dspam is suid root, with group courier, and owner/group execute permissions.
I believe courierlocal runs as courier:courier; in addition I tried making
it suid courier to be sure. The various Maildir's in user accounts have
group courier, with group rwx permissions, and all the files within them
have group courier with group rw permissions. So I don't understand why I
get this error. Any suggestions would be welcome, thanks!

 

-g

 

 

 

 

 

 

 

 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: X.org 7.2 keyboard layout switching does not work

[Marek Holly]

On Fri, Jun 08, 2007 at 10:38:53AM +0300, Vlad GURDIGA wrote:
>  Hello!
> 
>  After upgrading to Xorg 7.2 "by the book" (/usr/ports/UPDATING), I
>  could not switch my keyboard layouts as I did with the previous
>  version. Even more, I could not switch to text-mode console using
>  Ctrl-Alt-F1.
>  After I've regenerated a new xorg.conf using "Xorg -configure", I was
>  able to switch to text-mode console, but after adding the two lines
>  for keyboard layout switch (from my old xorg.conf):
> 
>  Option "XkbLayout"  "us,ro"
>  Option "XKbOptions" "grp:alt_shift_toggle"
> 
>  Ctrl-Alt-F1 stopped working and the keyboard layout switching did not
>  work. Google gave me some hints from the Gentoo documentation site
>  regarding the imposibility to switch to text-mode console, but the
>  solutions provided there did not work for me.
> 
>  Are there any substantial changes in the way that keyboard layout
>  switching works in X.org 7.2 vs. 6.9?
> 
>  # uname -a
>  FreeBSD kpax 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sat Jun  2 20:00:40
>  EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

Try to install xkeyboard-config-0.8 instead of 0.9 that is currently available
in ports tree.
http://exitcode.org/freebsd/xkeyboard-config-0.8.tar.gz

Works for me as long as the problem with newest version will be resolved.

-- 
Marek Holly 
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: USB optical mouse issue in x

[Nikola Lecic]

On Sat, 9 Jun 2007 04:56:15 -0400
"Dave" <[EMAIL PROTECTED]> wrote:

> Hi,
> Here is my configuration. The first two lines are dmesg output on
> my mouse, the rest is from my xorg.conf file:
> 
> ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass
> 3/1 ums0: 3 buttons and Z dir.
> 
> Section "InputDevice"
>  Identifier  "Mouse0"
>  Driver  "mouse"
>  Option  "CorePointer"
>  Option  "Protocol"  "Auto"
>  Option "Device" "/dev/sysmouse"
>  Option  "ZAxisMapping"  "4 5"
>  Option  "Emulate3Buttons" "true"
> EndSection

Well, try simply this:

  Section "InputDevice"
  Identifier  "Mouse0"
  Driver  "mouse"
  Option  "Protocol"  "auto"
  Option  "Device""/dev/sysmouse"
  Option  "ButtonNumber"  "5"
  Option  "ZAxisMapping"  "4 5"
  # or just Option "ButtonNumber" "3", without ZAxiaMapping
  EndSection

and check if

  InputDevice "Mouse0""CorePointer"

is present in Section "ServerLayout". Also, have you tried to switch
the mouse from ps/2 -> usb and vice versa?

Nikola Lečić
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: amvisd-new set up difficulty

[Kyrre Nygård]

hey wassup dhaneshki must tell you, after i set up postgrey for postfix, i only 
got like 1 spam a week, as opposed to 1000 a day. after i removed amavisd-new, 
spamassassin and all that overly complex bullshit... it made no differencetry 
it out, keep the system clean, good luckkyrre- Original Message -From: 
dhaneshk k <[EMAIL PROTECTED]>Date: Monday, May 28, 2007 10:38 amSubject: 
amvisd-new set up  difficultyTo: [EMAIL PROTECTED]: [EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]> Hi ,> > this is Dhanesh , by the way of finding 
a solution for spam > controll I> come across one  tutorial  Postfix and 
SpamAssassin By> Grzegorz , So I followed the foresaid tutorial ..> > URL 
:http://ezine.daemonnews.org/200309/postfix-spamassassin.html.> > Hope some of  
you may be the right one to help me to > controll spams in my > mail system.If 
not please introduce me to some experts who knows > this > configuration so I 
can touch with them.> > {> These all are I configured in a test machine 
(FreeBSD 6.0, > POSTFIX running > fine in this test machine ..I can send test 
mails between local > users in > this test machine  So if this setup is good 
then I can > install  amavis-new > in my server and can controll spams 
effectively) So I want to > check whether > this configuration is correct ya 
not , for that please give > some  inputs( > imean spam i/ps and how I know 
this is blocking spams  ..> and I want to ask you what I have to add more for 
the three line in> amavisd.conf> HERE I AM ATTCHING THE amvisd.conf file> > > 
read_hash(\%whitelist_sender, '/var/amavis/whitelist');> 
read_hash(\%blacklist_sender, '/var/amavis/blacklist');> 
read_hash(\%spam_lovers, '/var/amavis/spam_lovers');> > }> > > > I had a 
FreeBSD-6.0 box with postfix and mailman working fine > .The problem > is that 
my mailing list members including> me getting lots of spams daily ..so I  
really  got in > trouble .>    From the tutorial I uderstood that  by > 
installing   amavisd-new  will > solve the problem so I went ahead with this 
..> SpamAssain &razor also coming with this amavisd-new (they are> integrated 
with is package ).> > So a box with freeebsd6.0 ,with postfix clamav etc 
installed in > it ..> > (I have installed clamav before  following the tutorial 
through> usr/ports in FreeBSD box) SO I thought this AntiVirus  > clamav may 
be> sufficent for using with amavisd-new> > and  after this I followed the 
turorial for  postfix > and spamassassin> step by step upto   section IV> > 
Section IV - Notifications/DSN, BOUNCE/REJECT/DROP/PASS> destiny,> 
quarantine.   You may want to set these variables:> > $notify_sender_templ> 
$notify_virus_sender_templ> $notify_virus_admin_templ> 
$notify_virus_recips_templ> $notify_spam_sender_templ> 
$notify_spam_admin_templ> >   What valuses to set for this variables ,there is 
no such > variables in> the amavisd.conf file so  I added this in the file and 
> confused of> giving what values to this variables ? so I commented these > 6  
variables> and follwed the tutorial  upto> section V> > > 
read_hash(\%whitelist_sender, '/var/amavis/whitelist');> 
read_hash(\%blacklist_sender, '/var/amavis/blacklist');> 
read_hash(\%spam_lovers, '/var/amavis/spam_lovers');> > > these three lines I 
just added in amavisd.conf   ( I > dont know whether> to add any thing else so 
I added the following lines from the tutorial> to the amvisd.conf file> > > map 
{ $whitelist_sender{lc($_)}=1 } (qw(> freebsd-questions@freebsd.org> [EMAIL 
PROTECTED]> [EMAIL PROTECTED]> [EMAIL PROTECTED]> > ));> > and I went to 
section vii> > added these 2 line> > > $sa_local_tests_only = 0;> 
$sa_auto_whitelist = 1;> > and clamav I installed through ports  so I commented 
all > the  lines> except   the ones related to clamav section.> > then have 
done> > > # su - vscan> $ touch blacklist whitelist spam_lovers> $ mkdir tmp> > 
  but tmp dir is already here so its not needed to create it> explicitly..> > 
then followd spamassassin local.cf configuration as in the > tutorial exactly  
> ..> > But ther is no   .spamassassin  dir in > /var/amavis   so i created 
this> .spamassassin dir here and then given the command below .> > $ touch> 
/var/amavis/.spamassassin/user_prefs> > Then  razor and Bayesian learning 
configured as in the tutorial> > > then executed the command> > > 
/usr/local/sbin/amavisd debug> > But the debug output I dont know if it> 
correct ya not   so I am adding> the debug output here> Please let me know all 
my configurations correct ya not  ?> > > and in 
/usr/ports/security/amavisd-new/work ther is no work directory> and sample spam 
files , so let me give some sample spam code so > I ca> test it ..> > > NB: can 
you send a sample copy of amavisd.conf , spamassassin local.cf> , If my 
configuration is not looking proper one  in  > your view .> > > 
/usr/local/sbin/amavisd debug  o/p> don# /usr/local/sbin/amavisd> debug> May 25 
10:29:53 don.localdomain /usr/local/sbin/amavisd[1599]:> starting.  
/u

Re: FreeBSD arp proxy

[Dominik Zalewski]

On Saturday 09 June 2007 04:35:25 pm Matthew Seaman wrote:
> Dominik Zalewski wrote:
> > Dear All,
> >
> > I have a problem configuring routing. Here is how my setup looks:
> >
> > Internet - - - ADSL modem (bridge mode) - - - FreeBSD BOX - - - - - - -
> > Switch - - - - - - - Server 1 IPOA: 196.218.x.97vr1: 196.218.x.98
> >|  bge0: 196.218.x.100
> >
> >
> >
> >  
> > Server 2 eth0: 196.218.x.101
> >
> >
> >
> >
> > The idea is to give public IPs to servers behind FreeBSD firewall. I
> > don't want to assagin IP addresses to FreeBSD BOX and use binat. I
> > want to servers have IP assigned to their interfaces so I can reach
> > them directly from internet.
> >
> > Someone told me that I have to use arp proxy. As I know FreeBSD has
> > builtin arp proxy using userland arp utillity.
> >
> > When I added arp -s 196.218.x.100 mac_address_of_server1 perm pub . I
> > still couldn't reach 196.218.x.100 .
> >
> > Ofcoure I will have to add: no nat on $ext_if from { 10.0.0.3,
> > 10.0.0.7 } to any .
>
> The usual solution to this sort of problem is to divide up your
> allocated range of IP numbers into subnets and set up your firewall
> to route one or more of those subnets to the machines behind it.
>
> However, given the numbers you quote I suspect that your network
> allocation is 196.218.x.96/29 -- which gives you a network address
> (.96), 6 host addresses (.97 -- .102) and a broadcast address (.103)
> As you'ld need to sacrifice two more of those addresses to divide the
> range into two /30 blocks, and you need three host IPs for your back end
> network, so that isn't going to be feasible.
>
> It might be possible to reduce this idea to its ultimate level and
> set up individual host routes to each of the back-end servers on the
> FreeBSD firewall:
>
> route add -host 196.218.x.101 -interface 12.34.56.78
>
> where 12.34.56.78 should be replaced by the IP of the interface
> plugged into your back-end switch.  '12.34.56.78' should be on a
> different network than 192.218.x.96/29 -- so just grab something out
> of the RFC1918 address space.  While you're about it, you will
> probably find it helps to give your back-end servers all RFC1918
> addresses with the routable 192.218.x.96/29 addresses as aliases on
> the interfaces.
>
> You'ld need to generate equivalent host routes for each of your back
> end hosts, and you'ld need an equivalent host route on the back-end
> machines to reach the firewall:
>
> route add -host 192.168.x.97 12.34.56.78
>
> as well as setting 12.34.56.78 as the 'defaultrouter' in /etc/rc.conf.
>
> Warning: completely untested.  Should work in theory, but...
>
>   Cheers,
>
>   Matthew

I bridged vr1 and rl1. Everything seems to work fine:)

Thanks anyway,

Dominik


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD arp proxy

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dominik Zalewski wrote:
> Dear All,
> 
> I have a problem configuring routing. Here is how my setup looks:
> 
> Internet - - - ADSL modem (bridge mode) - - - FreeBSD BOX - - - - - - - 
> Switch - - - - - - - Server 1
>   IPOA: 196.218.x.97vr1: 196.218.x.98|
>   bge0: 196.218.x.100
>  |
> 
>  |
>  |
>   Server 2
> eth0: 
> 196.218.x.101   
> 
> 
> 
> 
> The idea is to give public IPs to servers behind FreeBSD firewall. I
> don't want to assagin IP addresses to FreeBSD BOX and use binat. I
> want to servers have IP assigned to their interfaces so I can reach
> them directly from internet.
> 
> Someone told me that I have to use arp proxy. As I know FreeBSD has
> builtin arp proxy using userland arp utillity.
> 
> When I added arp -s 196.218.x.100 mac_address_of_server1 perm pub . I
> still couldn't reach 196.218.x.100 .
> 
> Ofcoure I will have to add: no nat on $ext_if from { 10.0.0.3,
> 10.0.0.7 } to any .

The usual solution to this sort of problem is to divide up your
allocated range of IP numbers into subnets and set up your firewall
to route one or more of those subnets to the machines behind it.

However, given the numbers you quote I suspect that your network
allocation is 196.218.x.96/29 -- which gives you a network address
(.96), 6 host addresses (.97 -- .102) and a broadcast address (.103)
As you'ld need to sacrifice two more of those addresses to divide the
range into two /30 blocks, and you need three host IPs for your back end
network, so that isn't going to be feasible.

It might be possible to reduce this idea to its ultimate level and
set up individual host routes to each of the back-end servers on the 
FreeBSD firewall:

route add -host 196.218.x.101 -interface 12.34.56.78

where 12.34.56.78 should be replaced by the IP of the interface
plugged into your back-end switch.  '12.34.56.78' should be on a
different network than 192.218.x.96/29 -- so just grab something out
of the RFC1918 address space.  While you're about it, you will
probably find it helps to give your back-end servers all RFC1918
addresses with the routable 192.218.x.96/29 addresses as aliases on
the interfaces. 

You'ld need to generate equivalent host routes for each of your back
end hosts, and you'ld need an equivalent host route on the back-end
machines to reach the firewall:

route add -host 192.168.x.97 12.34.56.78

as well as setting 12.34.56.78 as the 'defaultrouter' in /etc/rc.conf.

Warning: completely untested.  Should work in theory, but...

Cheers,

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaqyd8Mjk52CukIwRCEpeAJ47a6oAGRcm49i05/MBVM73vSrVgACfXB+1
C0HnSuhr5lVG4eb7AmaT6/g=
=3LJ0
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: rsync install md5 error

[Agus]

Great...thanks a lot..

Greetz

2007/6/8, Beech Rintoul <[EMAIL PROTECTED]>:



> 2007/6/8, Beech Rintoul <[EMAIL PROTECTED]>:
> > On Friday 08 June 2007, Agus said:
> > > Hi all,
> > > I am trying to install /usr/ports/net/rsync and i am getting
> > > MD5 checksum mismatch for rsync-2.6.6.tar.gz
> > >
> > > then it says if u are sure u want to override this check, type
> > > make NO_CHECKSUM=yes
> > >
> > > What does it mean that the MD5 and sha256 checksums are wrong?
> > >
> > > How can i solve it??
> >
> > Try "make distclean" then "make install clean".
> >
> > Cheers,
> >
> > Beech

>On Friday 08 June 2007, Agus said:
> I see that in samba.org the version is 2.6.9...so my bsd tries to
> download it from another place
> is there a way to make install version 2.6.9 instead of the default
> that is trying??

2.6.9 is the current version. You need to update your ports tree.
See the handbook for details.

Beech
--

---
Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED]
/"\   ASCII Ribbon Campaign  | FreeBSD Since 4.x
\ / - NO HTML/RTF in e-mail   | http://www.freebsd.org
X  - NO Word docs in e-mail | Latest Release:
/ \  - http://www.freebsd.org/releases/6.2R/announce.html

---





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

failure in xorg 7.2 compile of vblank.c

[Robert Huff]

Robin Becker writes:

>  > ../common/vblank.c:306: error: for each function it appears in.)
>  > ../common/vblank.c: In function `driWaitForVBlank':
>  > ../common/vblank.c:363: error: `DRM_VBLANK_SECONDARY' undeclared (first 
> use in this function)

I got bit by this: you need to reinstall - by hand if necessary
graphics/dri, and possible graphics/libdrm.


Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: failure in xorg 7.2 compile of vblank.c

[Robin Becker]

On 09/06/07, Robin Becker <[EMAIL PROTECTED]> wrote:


I am trying the build from scratch route of xorg 7.2.

> cc -c -I. -I../../../../../src/mesa/drivers/dri/common -Iserver
-I../../../../../include -I../../../../../include/GL/internal
-I../../../../../src/mesa -I../../../../../src/mesa/main
-I../../../../../src/mesa/glapi -I../../../../../src/mesa/math
-I../../../../../src/mesa/transform -I../../../../../src/mesa/shader
-I../../../../../src/mesa/swrast -I../../../../../src/mesa/swrast_setup
-I../../../../../src/egl/main -I../../../../../src/egl/drivers/dri
`pkg-config --cflags libdrm` -I/usr/local/include -Wall
-O  -Wmissing-prototypes -std=c99 -Wundef -ffast-math -DUSE_X86_ASM
-DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -I/usr/local/include -DPTHREADS
-DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING
-DGLX_INDIRECT_RENDERING -DHAVE_ALIAS   ../common/vblank.c -o
../common/vblank.o
> ../common/vblank.c: In function `driGetCurrentVBlank':
> ../common/vblank.c:306: error: `DRM_VBLANK_SECONDARY' undeclared (first
use in this function)
> ../common/vblank.c:306: error: (Each undeclared identifier is reported
only once
> ../common/vblank.c:306: error: for each function it appears in.)
> ../common/vblank.c: In function `driWaitForVBlank':
> ../common/vblank.c:363: error: `DRM_VBLANK_SECONDARY' undeclared (first
use in this function)







ignore this I figured out it was caused by an unistalled libdrm package.

--
Robin Becker
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD arp proxy

[Dominik Zalewski]

Dear All,

I have a problem configuring routing. Here is how my setup looks:

Internet - - - ADSL modem (bridge mode) - - - FreeBSD BOX - - - - - - - Switch 
- - - - - - - Server 1
  IPOA: 196.218.x.97   vr1: 196.218.x.98
|bge0: 196.218.x.100

   |

   |

   |

Server 2

eth0: 196.218.x.101 




The idea is to give public IPs to servers behind FreeBSD firewall. I don't want 
to assagin IP addresses to FreeBSD BOX and use binat. I want to servers have IP 
assigned to their interfaces so I can
reach them directly from internet.

Someone told me that I have to use arp proxy. As I know FreeBSD has builtin arp 
proxy using userland arp utillity. 

When I added arp -s 196.218.x.100 mac_address_of_server1 perm pub . I still 
couldn't reach 196.218.x.100 .


Ofcoure I will have to add: no nat on $ext_if from { 10.0.0.3, 10.0.0.7 } to 
any .


Thank you in advance,


Dominik



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Increase in the number of ports: upgrade xorg to 7.2...

[Anatoliy]

On Fri, Jun 08, 2007 at 05:07:25PM -0400, Gerard wrote:

On June 08, 2007 at 03:48PM Bill Moran wrote:

[snip]

> It's not an assumption, its OPTIMISM!

That reminds me of an optimist who fell off of a fifty story building.
As he passed each floor on the way down, he yelled, "So, so far!"

Seriously, I hope you are right. I believe it was 'gettext' that was
updated a short time age. That update caused me all sorts of
dependency problems. My shell, bash, would no longer work, etc.
Over a hundred ports had to be updated to get everything back on an
even keel. That is the sort of problem I am worried about. Hopefully,
it won't happen.


FYI, if you'd used an upgrade tool like portupgrade it would have been
seamless because portupgrade keeps the old library version around for
precisely this reason.

Kris
___
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]"

Solved: Problem attaching ELI encrypted disk device

[Erik Norgaard]

Erik Norgaard wrote:

I have an encrypted /home partition using ELI. Recently I changed 
password for the encrypted partition


The previous config used a key, changing the password I did not specify 
the key so it is no longer in use - duh!


Erik

--
Ph: +34.666334818  web: http://www.locolomo.org


smime.p7s
Description: S/MIME Cryptographic Signature

mfi RAID monitoring

[Peter Schuller]

Hello,

the mfi(4) manpage briefly mentions the /dev/mfi? device, and that it
provides a "simple management interface".

Is there any way to monitor the health of an array (the only thing of
interest in this case) using this interface, other than getting the
proprietary Linux blob to work? (I could not get the latter to work.)

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <[EMAIL PROTECTED]>'
Key retrieval: Send an E-Mail to [EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED] Web: http://www.scode.org




signature.asc
Description: OpenPGP digital signature

Re: 6to4 IPv6 problems FreeBSD 6.2 p4

[Ofloo]

Kris Kennaway wrote:
> 
> On Mon, May 28, 2007 at 01:01:49PM -0700, Ofloo wrote:
>> 
>> 
>> 
>> Ofloo wrote:
>> > 
>> > I use 6to4 IPv6 tunnels, when using applications which use a lot of
>> > bandwidth (400kb/s), it is not that much but still, the server gets in
>> > trouble.
>> > 
>> > May 28 19:51:21 narf kernel: arpresolve: can't allocate route for
>> > 192.88.99.1
>> > May 28 19:51:22 narf kernel: arpresolve: can't allocate route for
>> > 192.88.99.1
>> > May 28 20:06:15 narf kernel: arpresolve: can't allocate route for
>> > 192.88.99.1
>> > May 28 20:09:02 narf kernel: arpresolve: can't allocate route for
>> > 192.88.99.1
>> > 
>> > The default route does exist though:
>> > 
>> > narf# netstat -rn -f inet6 | grep default
>> > default   2002:c058:6301::  UGS   
>> > stf0
>> > narf#
>> > 
>> > when this happens it takes about 10 mins and my ssh IPv6 ssh session is
>> > closed, after keeping this up for longer the server crashes, .. any
>> > suggestions ?
>> > 
>> 
>> Using a different default gateway solved this for now, though I don't
>> think
>> a server should crash if its gateway is in trouble, ..
> 
> Submit a bug report with the panic backtrace, etc.
> 
> Kris
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> 

Where am I supposed to get those, I'm sure it's causing it, I'm running 6to4
on a machine which has never crashed on me, I did a ping while the 6to4
relay was down and it crashed.

Suggestions where I can find this panic report, ..

-- 
View this message in context: 
http://www.nabble.com/6to4-IPv6-problems-FreeBSD-6.2-p4-tf3829352.html#a11038960
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Problem attaching ELI encrypted disk device

[Erik Norgaard]

Hi:

I have an encrypted /home partition using ELI. Recently I changed 
password for the encrypted partition and now the following problem 
consistently occurs:


At boot I am queried for a password for the ELI partition, I enter et 
correctly - six times - but it fails every time. After the sixth failure 
the rc script aborts, I am queried for the root password and enter.


I am then able to run

# geli attach /dev/ad0s2d

manually and attach the encrypted device. Then I can run rc manually and 
the machine completes the startup without further problems.


What has happened? How do I solve this?

Thanks, Erik

--
Ph: +34.666334818  web: http://www.locolomo.org


smime.p7s
Description: S/MIME Cryptographic Signature

Re: USB optical mouse issue in x

[Dave]

Hi,
   Here is my configuration. The first two lines are dmesg output on my 
mouse, the rest is from my xorg.conf file:


ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "CorePointer"
Option  "Protocol"  "Auto"
Option "Device" "/dev/sysmouse"
Option  "ZAxisMapping"  "4 5"
Option  "Emulate3Buttons" "true"
EndSection

Thanks.
Dave.

- Original Message - 
From: "Nikola Lecic" <[EMAIL PROTECTED]>

To: "Dave" <[EMAIL PROTECTED]>
Cc: ; "Lowell Gilbert" 
<[EMAIL PROTECTED]>

Sent: Friday, June 08, 2007 9:44 PM
Subject: Re: USB optical mouse issue in x


On Fri, 8 Jun 2007 11:44:34 -0400
"Dave" <[EMAIL PROTECTED]> wrote:


Hello,
Thanks for your reply. No, no buttons work at all, as i said the
mouse cursor moves, but can't click, and yes it does work on the
console under moused. Do i need moused running for x?


Are you sure you have something like

 Section "InputDevice"
 [...]
 Option  "ButtonNumber" "5"
 Option  "ZAxisMapping" "4 5"

in your /etc/X11/xorg.conf?

Nikola Lečić 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Woes of xorg 7.2 upgrade ...

[Jose Luis Alarcon Sanchez]

On Sat, 9 Jun 2007 08:54:43 +0200
"Kiffin Gish" <[EMAIL PROTECTED]> wrote:

> I've been struggling now for 2 weeks trying to do the xorg upgrade,
> following the upgrading instructions to a tee, but it has turned into a
> complete mess.
> 
> If worse comes to worse, what it the best way to proceed?
> 
> Is there an easy way just to reinstall xorg from scratch?
> 
> Thanks a lot in advance.
> 
> -- 
> Kiffin Rex Gish
> Gouda, The Netherlands
> 

Hi Kiffin.

You don't tell us the output of your complete mess.

The best way to proceed is follow step by step what say the file 
/usr/ports/UPDATING, "chunk" 20070519. It's the more simple and
easy way for get Xorg 7.2 running on your FreeBSD 6.2 machine.

Before do just this portupgrade -a i was triying with portmanager -u -l
and others stuffs on my way, but it can't got it.

Keep trying. It isn't very dificult.

Regards.

Jose.

-- 
http://www.lordofunix.org/
 
Not Registered GNU/Hurd User.
Registered BSD User 51101.
Registered Linux User #213309.
Memories. You are talking about memories.
Rick Deckard. Blade Runner.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Upgrading from XFree86 to Xorg

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Warren Liddell wrote:
> Up untill now i have been using XFree86 and being as it is basically no
> longer updated or maintained, so im wishing to know the basic most
> easiest way to change over from XFree to Xorg

If you're still running XFree86 because you're on a FreeBSD 4.x system
where that is the default, then do not even think about trying this as
you will completely banjax your system.  Upgrade to 6.2 first.

0) Back up your system.  You're going to be deleting large swathes of it,
and restoring from backup is your only recourse if you need to back out
these changes.  Also, make a note of all of the ports you have installed
for later reference:

 ls -1 /var/db/pkg | lpr

i) Log into the console as root.  Stop any X stuff running on other vtys.
Delete all X related ports. Something like the following should do the
trick:

 pkg_deinstall -rR XFree86\*

Yes, this will delete the majority of the ports you have installed on
your machine.

ii) Make sure you have your ports tree updated to the latest available.

iii) You will probably have some remnants of a /usr/X11R6 filesystem
left after deleting XFree86.  If not, then create a stub directory
temporarily by 'mkdir /usr/X11R6'

iv) Merge anything left under /usr/X11R6 into /usr/local and do various
other configuration tweaks:

sh /usr/ports/Tools/scripts/mergebase.sh

Follow the instructions this script prints out.  If it finds files etc.
left laying about under the /usr/X11R6 tree it will ask you to clear
them up and then try again.  eg. /usr/X11R6/man/whatis, which can just
be deleted as it is automatically generated from the installed man pages.
Other files you'll have to decide on a case by case basis.  Anyhow, keep
trying that script and moving away stuff it can't cope with until the
script reports success.

After this procedure /usr/X11R6 should be a sym-link pointing at
/usr/local

v) Install the new Xorg:

portinstall x11/xorg

If you're using the x11/nvidia driver, then reinstall that at this point.

vi) Generate a new /etc/X11/xorg.conf file and customise it according to
your preferences:

X -configure
[...etc...]

At this point 'startx' should bring up X successfully and get you into a
screen configured with the correct resolution and colour depth etc. 

vii) Reinstall any X client software you still require.  This is where the
list created in (0) comes in handy.  This is where you'ld reinstall Gnome
or KDE, plus any applications like Firefox or Gimp.

Note: beware of using pkg_add to install pre-compiled ports.  pkg_add
by default will attempt to install packages from the set compiled at
the time the OS was released, and those (of course) pre-date Xorg 7.2
going into the ports tree.  If you want to use precompiled packages
make sure you download them from the 'Latest' directory.  Compiling your
own via the ports is recommended[*] -- it takes longer, but the results
are more certain.

[*] With certain exceptions, like OpenOffice

viii) Enjoy.

I wouldn't characterise this procedure as either 'basic' or 'easy' --
it's certainly going to take a great deal of compiling stuff and you
shouldn't attempt it unless you can afford several days without a
working X environment.  However, if you're careful and don't try any
short cuts it should work well and be completely effective.

Cheers,

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGamXP8Mjk52CukIwRCFcOAJ46/OmPLoHZYlv9W23aNCRu5yxOJwCfTKHk
zSIjPENSsCDBI46SITxBiwE=
=MGkT
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Woes of xorg 7.2 upgrade ...

[Iulian M]

On Saturday 09 June 2007, Jens B wrote:
> * Kiffin Gish <[EMAIL PROTECTED]> [2007-06-09 09:45]:
> > I've been struggling now for 2 weeks trying to do the xorg upgrade,
> > following the upgrading instructions to a tee, but it has turned into a
> > complete mess.
> >
> > If worse comes to worse, what it the best way to proceed?
> >
> > Is there an easy way just to reinstall xorg from scratch?
> >
> > Thanks a lot in advance.
> >
> > --
> > Kiffin Rex Gish
> > Gouda, The Netherlands
>
> In such cases the best would be to deinstall xorg with all
> dependencies and install xorg from scratch.
>
>

hi,

Depending on your setup it might be a good idea to remove All the ports 
installed and check /usr/local ( i guess /usr/X11R6 is already a symlink ) 
for orphaned files that might get in the way of a new install. 

To speed up the initial install of xorg you could use binary packages and if 
you feel like it recompile after from ports... at least you will have X 
working in the meantime. 


-- 
Best Regards,
Iulian Margarintescu
http://www.erata.net
[EMAIL PROTECTED]
(spamassassin & pf & spamd all said it's OK to make it public ;-) )
Key ID: 0x03176E5CEDEFF7AB
I prefer plain text email


pgpldVinlLuWw.pgp
Description: PGP signature

Re: Unable to mount DVD-R Media

[Ivan Carey]

Norberto Meijome wrote:

On Fri, 08 Jun 2007 18:34:33 +1000
Ivan Carey <[EMAIL PROTECTED]> wrote:

  

  

It happens with all blank  dvd -r

It also happened when writing to cd-r in k3b . The disk was written to 
but when the verification ot the files written th error occured. The 
files were written ok.



a dvd and cd that has been burnt mounts ok

Do you think the problem could be with k3b?



i dont know, i dont use kde.

what happens if you use the OS provided tools:

# from an ISO
growisofs -dvd-compat -Z /dev/cd0=BURN.iso
# From FS
growisofs -dvd-compat -Z /dev/cd0 -R -J -V VolID ./BURN/


B
_
{Beto|Norberto|Numard} Meijome

"So limp of brain that for them to conceive an idea is to risk a haemorrhage. So 
limp of body that their purple dresses appear no more a dixative of housing nerves and 
sinews than when they hang suspended from their hooks"
   Mervin Peake, "Gormenghast", chap. 2, on the Earl's twin sisters

I speak for myself, not my employer. Contents may be hot. Slippery when wet. 
Reading disclaimers makes you go blind. Writing them is worse. You have been 
Warned.

.

  

I am starting to understand things better now thanks
The write problem for the DVD in k3b was the write speed. The disk was 
written to ok, I turned off the verify as the error comes up when k3b 
reinserts the disk to verify the write.


Thanks,
Ivan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Woes of xorg 7.2 upgrade ...

[Jens B]

* Kiffin Gish <[EMAIL PROTECTED]> [2007-06-09 09:45]:
> I've been struggling now for 2 weeks trying to do the xorg upgrade,
> following the upgrading instructions to a tee, but it has turned into a
> complete mess.
> 
> If worse comes to worse, what it the best way to proceed?
> 
> Is there an easy way just to reinstall xorg from scratch?
> 
> Thanks a lot in advance.
> 
> -- 
> Kiffin Rex Gish
> Gouda, The Netherlands

In such cases the best would be to deinstall xorg with all
dependencies and install xorg from scratch.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: problem with "pw"

[Matthew Seaman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Eric Dedrick wrote:
> I'm having a nuisance problem, especially when I try to update my
> ports.  I'm using cups as an example, but other ports show the
> problem:
> 
> root# pw usershow cups
> pw: no such user `cups'
> root# pw useradd cups -g cups -u 193
> pw: user 'cups' already exists
> 
> Any idea what the problem is and how to fix it?

pwd_mkdb(8) perhaps.

Cheers,

Matthew
- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGallT8Mjk52CukIwRCBEcAJ0RtLd9ajpxif2Kn+fPAIew5EZ+RQCfSRws
JldcvoXVHpIRqxKgJ6+BBf4=
=Zdt7
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Woes of xorg 7.2 upgrade ...

[Kiffin Gish]

I've been struggling now for 2 weeks trying to do the xorg upgrade,
following the upgrading instructions to a tee, but it has turned into a
complete mess.

If worse comes to worse, what it the best way to proceed?

Is there an easy way just to reinstall xorg from scratch?

Thanks a lot in advance.

-- 
Kiffin Rex Gish
Gouda, The Netherlands

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Upgrading from XFree86 to Xorg

[Warren Liddell]

Up untill now i have been using XFree86 and being as it is basically 
no longer updated or maintained, so im wishing to know the basic most 
easiest way to change over from XFree to Xorg


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"