RE: Kernel hangs if build without I486_CPU

2007-09-12 Thread Andris

Hi,

I have the same problem, but in my case it was not I486_CPU, but SCHED_ULE.
After changing SCHED_ULE to SCHED_4BSD problem was gone.

Andris



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Barner
Sent: Sunday, September 09, 2007 10:56 PM
To: freebsd-stable@freebsd.org
Subject: Kernel hangs if build without I486_CPU

Hello,

when I updated my 6.2-STABLE (i386) system yesterday, I noticed that
the kernel would hang on startup if it was build without I486_CPU.

Unfortunatelly, I did not keep my old kernel binary, but IIRC the
last time I csup'ed was on June 26 2007.

The reason why I am reporting the hang is the I wonder whether the
change that caused the hang was intentional.

I uploaded the dmesg from the updated kernel (with I486_CPU) and my
kernel configuration to

http://people.freebsd.org/~barner/kernelhang/

Just let me know if you need more information...

-- 
Best regards / Viele Grüße, [EMAIL PROTECTED]
 Simon Barner[EMAIL PROTECTED]

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


Re: Via padlock

2007-09-12 Thread Daniel O'Connor
On Wed, 12 Sep 2007, Oliver Fromme wrote:
> padlock_load="YES"
>
> So there's no need to modify your kernel.

I just realised that I checked and amd64 6.2 machine and an 
i386 -current machine, hence my confusion :)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.


Two Day International Conference

2007-09-12 Thread Raghesh A
Friends,
A two day international conference (ICIST2007) is planned at
Thrissur(Kerala, India)
during 14,15 December 2007 with Free Software as the principal theme.

RMS has agreed to engage the participants in a virtual session and
clarify online to any subsequent queries.

Papers are solicited for ICIST2007.

Details are at http://mesengg.ac.in/icist2007.htm
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: BIND 9.3.1 - How to get rid of AAAA querys?

2007-09-12 Thread Mark Andrews

> When looking in the querylog for BIND 9.3.1 running on FreeBSD 5.4, 
> almost every other log entry specifies an  query. The only client is 
> localhost. I see no reason right now to have BIND wasting resources on 
> IPv6 requests, so I added
> 
> named_flags="-4"
> 
> to rc.conf and restarted named. Sockstat tells me named is listening 
> only on udp4 and tcp4, but I still get lots of  entries in the querylog:
> 
> 12-Sep-2007 21:40:47.129 client 127.0.0.1#60103: query: 
> smtp.secureserver.net IN  +
> 12-Sep-2007 21:40:47.648 client 127.0.0.1#64489: query: 
> smtp.where.secureserver.net IN  +
> 12-Sep-2007 21:40:47.847 client 127.0.0.1#61673: query: 
> smtp.secureserver.net IN A +
> 12-Sep-2007 21:40:47.869 client 127.0.0.1#53040: query: 
> mailstore1.secureserver.net IN  +
> 12-Sep-2007 21:40:47.871 client 127.0.0.1#54473: query: 
> mailstore1.secureserver.net IN A +
> 12-Sep-2007 21:40:58.261 client 127.0.0.1#58124: query: 
> 120.86.248.87.in-addr.arpa IN PTR +
> 12-Sep-2007 21:40:58.340 client 127.0.0.1#56511: query: 
> static-ip-87-248-86-120.promax.media.pl IN  +
> 12-Sep-2007 21:40:58.410 client 127.0.0.1#61212: query: 
> static-ip-87-248-86-120.promax.media.pl IN A +
> 
> What can I do to get rid of these?

Teach each and every application not to make them. :-)

-4 stops named *making* and accepting queries *over* IPv6.

It does NOT stop it accepting  queries.
It does NOT stop it making  queries.

Why don't you go the other way and get yourself IPv6
connectivity.  You do realise that you will require it to
reach many sites in about 3 years time as they will be IPv6
only (new IPv4 address space is running out real soon now).
Running dual stacked now is how you debug you system.

If you ISP doesn't yet offer IPv6 natively there are lots
of alternate method.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: BIND 9.3.1 - How to get rid of AAAA querys?

2007-09-12 Thread Jeremy Chadwick
On Wed, Sep 12, 2007 at 09:45:21PM +0200, Andreas Pettersson wrote:
> When looking in the querylog for BIND 9.3.1 running on FreeBSD 5.4, almost 
> every other log entry specifies an  query. The only client is 
> localhost. I see no reason right now to have BIND wasting resources on IPv6 
> requests, so I added
>
> named_flags="-4"
>
> to rc.conf and restarted named. Sockstat tells me named is listening only 
> on udp4 and tcp4, but I still get lots of  entries in the querylog:
>
> 12-Sep-2007 21:40:47.129 client 127.0.0.1#60103: query: 
> smtp.secureserver.net IN  +
> 12-Sep-2007 21:40:47.648 client 127.0.0.1#64489: query: 
> smtp.where.secureserver.net IN  +
> 12-Sep-2007 21:40:47.847 client 127.0.0.1#61673: query: 
> smtp.secureserver.net IN A +
> 12-Sep-2007 21:40:47.869 client 127.0.0.1#53040: query: 
> mailstore1.secureserver.net IN  +
> 12-Sep-2007 21:40:47.871 client 127.0.0.1#54473: query: 
> mailstore1.secureserver.net IN A +
> 12-Sep-2007 21:40:58.261 client 127.0.0.1#58124: query: 
> 120.86.248.87.in-addr.arpa IN PTR +
> 12-Sep-2007 21:40:58.340 client 127.0.0.1#56511: query: 
> static-ip-87-248-86-120.promax.media.pl IN  +
> 12-Sep-2007 21:40:58.410 client 127.0.0.1#61212: query: 
> static-ip-87-248-86-120.promax.media.pl IN A +
>
> What can I do to get rid of these?

I'm not sure you can.  This is how I understand it:

The -4 switch just tells BIND, as a daemon, to only bind to/utilise IPv4
interfaces on your system.  That means named -4 will only listen on IPv4
addresses (e.g. 127.0.0.1) and not things like ::1.

That's completely separate from what *DNS records* BIND will see queries
for -- you have no control over those.  People can ask you for any type
of DNS record (A, , MX, CNAME, NS, TXT, whatever...) and your daemon
will respond for things it's authoritative for (or do recursive queries
if configured to do so).

In English: -4 won't completely remove IPv6-specific zone
data/capability from BIND, it'll just cause the actual daemon to not
bind to an IPv6 interface.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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


Re: BIND 9.3.1 - How to get rid of AAAA querys?

2007-09-12 Thread Max Laier
On Wednesday 12 September 2007, Andreas Pettersson wrote:
> When looking in the querylog for BIND 9.3.1 running on FreeBSD 5.4,
> almost every other log entry specifies an  query. The only client
> is localhost. I see no reason right now to have BIND wasting resources
> on IPv6 requests, so I added
>
> named_flags="-4"
>
> to rc.conf and restarted named. Sockstat tells me named is listening
> only on udp4 and tcp4, but I still get lots of  entries in the
> querylog:
...
> What can I do to get rid of these?

Change your resolver.  The name*server* can nothing do about what the 
*client* asks of them.  The fact that you connect to a nameserver via 
IPv4 says nothing about what kind of queries you want to send to it.  At 
the moment you can't change the behavior of the resolver in libc and (as 
far as I know) that of the isc implementation either.  There has been a 
discussion to provide a environment variable to emit only IPv4 queries, 
though.

-- 
/"\  Best regards,  | [EMAIL PROTECTED]
\ /  Max Laier  | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | [EMAIL PROTECTED]
/ \  ASCII Ribbon Campaign  | Against HTML Mail and News


signature.asc
Description: This is a digitally signed message part.


BIND 9.3.1 - How to get rid of AAAA querys?

2007-09-12 Thread Andreas Pettersson
When looking in the querylog for BIND 9.3.1 running on FreeBSD 5.4, 
almost every other log entry specifies an  query. The only client is 
localhost. I see no reason right now to have BIND wasting resources on 
IPv6 requests, so I added


named_flags="-4"

to rc.conf and restarted named. Sockstat tells me named is listening 
only on udp4 and tcp4, but I still get lots of  entries in the querylog:


12-Sep-2007 21:40:47.129 client 127.0.0.1#60103: query: 
smtp.secureserver.net IN  +
12-Sep-2007 21:40:47.648 client 127.0.0.1#64489: query: 
smtp.where.secureserver.net IN  +
12-Sep-2007 21:40:47.847 client 127.0.0.1#61673: query: 
smtp.secureserver.net IN A +
12-Sep-2007 21:40:47.869 client 127.0.0.1#53040: query: 
mailstore1.secureserver.net IN  +
12-Sep-2007 21:40:47.871 client 127.0.0.1#54473: query: 
mailstore1.secureserver.net IN A +
12-Sep-2007 21:40:58.261 client 127.0.0.1#58124: query: 
120.86.248.87.in-addr.arpa IN PTR +
12-Sep-2007 21:40:58.340 client 127.0.0.1#56511: query: 
static-ip-87-248-86-120.promax.media.pl IN  +
12-Sep-2007 21:40:58.410 client 127.0.0.1#61212: query: 
static-ip-87-248-86-120.promax.media.pl IN A +


What can I do to get rid of these?

--
Andreas


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


Re: Via padlock

2007-09-12 Thread Oliver Fromme
Daniel O'Connor wrote:
 > On Wed, 12 Sep 2007, Minseok Choi wrote:
 > > I found out from googling that VIA Padlock would be supported in
 > > FreeBSD 6.2.
 > > 
 > > But I don't know how to activate it.
 > > Is there any kernel configuration or specific application for the
 > > Padlock?
 > 
 > It appears the man page is missing, but putting 
 > device crypto
 > device padlock
 > 
 > in your kernel should work.
 > 
 > In 7.0 it's a module.

It's a module in 6.x, too.  I have the following line in
/boot/loader.conf on my RELENG_6 machine (VIA C3):

padlock_load="YES"

So there's no need to modify your kernel.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"We, the unwilling, led by the unknowing,
are doing the impossible for the ungrateful.
We have done so much, for so long, with so little,
we are now qualified to do anything with nothing."
        -- Mother Teresa
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: problems with 'periodic' in 4.11 p-24

2007-09-12 Thread Bill Vermillion
I just updated a 4.11 machine to patch level 24.  Somehow I had
overlooked that machine earlier as it's so stable and only
is handling web pages, secondary dns and secondary mail.

I've checked everthing I can think of but now all the scripts
that are run from the root crontab - with the user of 'root' as
shipped in the distrubution now give me error messages.

The messages are from the atrun daemon.

Here is the message I'm getting just as I bounced it to this
account.

Theone difference I see in this is that the Subject line
when viewed in mutt on the original machine has
root?/usr/libexec/atrun.

--
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> root  /usr/libexec/atrun
X-Cron-Env: 
X-Cron-Env: 
X-Cron-Env: 
X-Cron-Env: <[EMAIL PROTECTED]>
X-Cron-Env: 
X-Cron-Env: 
X-UIDL: EO^"!?>h"!Y(@"!+&N"!

root: not found

--

I've checked everywhere I can think of.  I've even added
the MAILTO line in the crontab with an FQDN address.  That didn't
help either.

It must be something simple I've overlooked or else I'd have seen
reports of this before.

The cvsup is only for the RELEASE - so nothing is there that
would be added after the last security update to that last year.

I'm sorry this is so late in time frame of 4.11 - but as I said -
for some reason this is one server I inadvertantly overlooked.
Normally the OS gets updated the day any security changes are made.

Thanks

Bill

-- 
Bill Vermillion - bv @ wjv . com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Via padlock

2007-09-12 Thread Daniel O'Connor
On Wed, 12 Sep 2007, Minseok Choi wrote:
> I found out from googling that VIA Padlock would be supported in
> FreeBSD 6.2.
>
> But I don't know how to activate it.
> Is there any kernel configuration or specific application for the
> Padlock?
>
> If you have any idea about this issue, let me know.
> Currently I am using VIA Epia SP13000, which has Nehemiah CPU with
> RNG, AES support.

It appears the man page is missing, but putting 
device crypto
device padlock

in your kernel should work.

In 7.0 it's a module.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


signature.asc
Description: This is a digitally signed message part.


Via padlock

2007-09-12 Thread Minseok Choi
I found out from googling that VIA Padlock would be supported in FreeBSD 6.2.

But I don't know how to activate it.
Is there any kernel configuration or specific application for the Padlock?

If you have any idea about this issue, let me know.
Currently I am using VIA Epia SP13000, which has Nehemiah CPU with RNG, AES
support.

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