Re: wrong CPU frequency detection

2003-03-03 Thread Bill Moran
Eugene M. Zheganin wrote:
Hi, All.

Why does my 4.8-PRERELEASE detect my CPU as 1000 MHz instead of real
1200 MHz ?
Just because the processor is rated at 1200 doesn't mean that the
motherboard is running it at that speed.
Any time I've seen this problem, it was because the motherboard was
left to autodetect the CPU speed and didn't do so correctly (don't
know why they seem to incorrectly guess 1G)  Check your BIOS settings.
===Cut===
FreeBSD 4.8-PRERELEASE #0: Sat Mar  1 12:01:00 YEKT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEDOM
Timecounter i8254  frequency 1193182 Hz
CPU: Intel(R) Celeron(TM) CPU1000MHz (1009.95-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6b1  Stepping = 1
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
===Cut===
I have the same problem on 4.6-RELEASE (real CPU frequency is 1700
MHz):
===Cut===
FreeBSD 4.6-RELEASE #0: Mon Oct  7 17:54:30 YEKST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TIGER
Timecounter i8254  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (1009.95-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x6b1  Stepping = 1
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
===Cut===
I have some FreeBSD-boxes running with CPU frequency lower than 1GHz -
FreeBSD detects them correctly.
Is it some kind of misconfiguration ? Can it cause problems ?

Thanks a lot.

  WBR.


--
Bill Moran
Potential Technologies
http://www.potentialtech.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


RE: wrong CPU frequency detection

2003-03-03 Thread Mike Jakubik
FYI: Some bioses will reset the cpu frequency to a lower value if the
machine is reset during a post. (Thinking the user overclocked the cpu,
which caused the system to not boot)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bill Moran
Sent: Monday, March 03, 2003 9:09 AM
To: Eugene M. Zheganin
Cc: [EMAIL PROTECTED]
Subject: Re: wrong CPU frequency detection


Eugene M. Zheganin wrote:
 Hi, All.

 Why does my 4.8-PRERELEASE detect my CPU as 1000 MHz instead of real
 1200 MHz ?

Just because the processor is rated at 1200 doesn't mean that the
motherboard is running it at that speed.
Any time I've seen this problem, it was because the motherboard was
left to autodetect the CPU speed and didn't do so correctly (don't
know why they seem to incorrectly guess 1G)  Check your BIOS settings.


 ===Cut===
 FreeBSD 4.8-PRERELEASE #0: Sat Mar  1 12:01:00 YEKT 2003
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEDOM
 Timecounter i8254  frequency 1193182 Hz
 CPU: Intel(R) Celeron(TM) CPU1000MHz (1009.95-MHz
686-class CPU)
   Origin = GenuineIntel  Id = 0x6b1  Stepping = 1

Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
PAT,PSE36,MMX,FXSR,SSE
 ===Cut===

 I have the same problem on 4.6-RELEASE (real CPU frequency is 1700
 MHz):

 ===Cut===
 FreeBSD 4.6-RELEASE #0: Mon Oct  7 17:54:30 YEKST 2002
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TIGER
 Timecounter i8254  frequency 1193182 Hz
 CPU: Pentium III/Pentium III Xeon/Celeron (1009.95-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x6b1  Stepping = 1

Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,
PAT,PSE36,MMX,FXSR,SSE
 ===Cut===

 I have some FreeBSD-boxes running with CPU frequency lower than 1GHz -
 FreeBSD detects them correctly.

 Is it some kind of misconfiguration ? Can it cause problems ?

 Thanks a lot.

   WBR.


--
Bill Moran
Potential Technologies
http://www.potentialtech.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


FreeBSD 5.0 and MySQL on NFS-mounted partition (NetApp)

2003-03-03 Thread Mark Hennessy
From mysql compiled from ports:
Can't lock file (errno: 45)

I just rebuilt mysql 3.23.55 on FreeBSD 5.0, and I am trying to start
mysqld with my databases, and all of a sudden I'm getting this error.  I
was wondering if anyone has seen this and might know where I should start
looking?

Additionally, it appears that this error only comes up when the DATADIR
for MySQL is set to a directory on an NFS-mounted drive.  I have also
asked one of the MySQL lists, and they suggested looking at rpc.lockd,
but would that be needed if no writes were being made?

--
 Mark P. Hennessy [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


php4 build fail from ports

2003-03-03 Thread Odhiambo Washington

Are there any experienced takers?

FreeBSD-4.{7|8}
cd /usr/ports/www/mod_php4/  make

fails with error below:





===  Building for mod_php4-4.3.1
/bin/sh libtool --silent --mode=compile cc  -Iext/zlib/ 
-I/usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/ -DPHP_ATOM_INC 
-I/usr/ports/www/mod_php4/work/php-4.3.1/include 
-I/usr/ports/www/mod_php4/work/php-4.3.1/main -I/usr/ports/www/mod_php4/work/php-4.3.1 
-I/usr/ports/www/mod_php4/work/php-4.3.1/Zend -I/usr/local/include 
-I/usr/local/include/freetype2 -I/usr/local/include/c-client 
-I/usr/local/include/mysql -I/usr/local/include/pspell  -DMOD_SSL=208112 -DMOD_PERL 
-DUSE_PERL_SSI -DAPPLLIB_EXP=/usr/local/lib/perl5/5.6.1/BSDPAN -DEAPI 
-DAPPLLIB_EXP=/usr/local/lib/perl5/5.6.1/BSDPAN 
-I/usr/ports/www/mod_php4/work/php-4.3.1/TSRM  -O -pipe -I/usr/local/include  
-prefer-pic -c /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c -o 
ext/zlib/zlib.lo
In file included from /usr/include/sys/param.h:104,
 from 
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_config_common.h:14,
 from 
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_virtual_cwd.h:26,
 from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:360,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/include/machine/limits.h:81: warning: `LONG_MAX' redefined
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:189: warning: this is the location 
of the previous definition
/usr/include/machine/limits.h:82: warning: `LONG_MIN' redefined
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:193: warning: this is the location 
of the previous definition
In file included from 
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_config_common.h:14,
 from 
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_virtual_cwd.h:26,
 from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:360,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/include/sys/param.h:193: warning: `MAXPATHLEN' redefined
/usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:237: warning: this is the location 
of the previous definition
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:202,
 from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:34,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend_hash.h:119: syntax error before 
`va_list'
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:203,
 from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:34,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend_llist.h:34: syntax error before 
`va_list'
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:34,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:285: syntax error before `va_list'
/usr/ports/www/mod_php4/work/php-4.3.1/Zend/zend.h:423: syntax error before `va_list'
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:224,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/main/spprintf.h:40: syntax error before 
`va_list'
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:277: syntax error before `va_list'
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/main/php.h:360,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:28:
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_virtual_cwd.h:159: warning: `struct 
utimbuf' declared inside parameter list
/usr/ports/www/mod_php4/work/php-4.3.1/TSRM/tsrm_virtual_cwd.h:159: warning: its scope 
is only this definition or declaration, which is probably not what you want.
In file included from /usr/ports/www/mod_php4/work/php-4.3.1/ext/standard/fsock.h:38,
 from 
/usr/ports/www/mod_php4/work/php-4.3.1/ext/standard/php_standard.h:44,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:48:
/usr/ports/www/mod_php4/work/php-4.3.1/main/php_network.h:113: syntax error before 
`socklen_t'
/usr/ports/www/mod_php4/work/php-4.3.1/main/php_network.h:113: warning: `struct 
sockaddr' declared inside parameter list
In file included from 
/usr/ports/www/mod_php4/work/php-4.3.1/ext/standard/php_standard.h:44,
 from /usr/ports/www/mod_php4/work/php-4.3.1/ext/zlib/zlib.c:48:
/usr/ports/www/mod_php4/work/php-4.3.1/ext/standard/fsock.h:43: warning: `struct 
in_addr' declared inside parameter list
*** Error code 1

Stop in /usr/ports/www/mod_php4/work/php-4.3.1.
*** Error code 1

Stop in /usr/ports/www/mod_php4.
*** Error code 1

Stop in /usr/ports/www/mod_php4.






-Wash

-- 
Odhiambo 

¦³¾÷·|§AÄ@·N¥h¹Á¸Õ¶Ü??

2003-03-03 Thread star
Title: ¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿


¥D¦®: ³o©Î³\¬O±z¥¿¦b´M§äªº¾÷·|³á 
 
 
 
   
   
³o©Î³\¬O±z¥¿¦b§äªº¾÷·|[EMAIL PROTECTED] 
   
¹ï¤£°_¡I¥´ÂZ¤F¡A¦pªG¦]¦¹³y¦¨±zªº§xÂZ¡A½Ðª½±µ§R°£¥»«H¤ÎÂI¿ï¤U¤è¡u¤£·Q¦A¦¬«H¡v¡A§Ú­Ì·|±N±zªº¸ê®Æ§R°£¡I 
   
 
   
 
   
¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿¡A¦¬¤J¦h100­¿¡B¬Æ¦Ü¦h1000­¿¡AÃø¹D¥L¦³¤ñ§A¦hÁo©ú³o»ò¦h¶Ü¡H 
   
µª®×ªÖ©w¤£¬Oªº¡I 
   
[EMAIL PROTECTED] 
   
¥L­Ì¨ì©³°µ¤F¤°»ò¬O§Ú­Ì©Ò¤£ª¾¹Dªº¨Æ¡H 
   
¦Ó§Ú­Ì¨ì©³°µ¿ù¤F¤°»ò¡B¤S¿ù¹L¤F¤°»ò¡H 
   
·Q¤£·Qª¾¹D¤H®a«ç»ò°µ­Ëªº¡I
  
§A¬Û«H¡u®É¶¡¡×ª÷¿ú¡v¡BÁÙ¬O¡u®É¶¡¡Öª÷¿ú¡v
  

  Á|¨Ò¡G
  
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@®É¼Æ¡H
  
¢·¤p®É¡¯¢²¢µ¢´¤Ñ¡¯¢²¢¯¦~¡×¢·¢¶,¢µ¢¯¢¯¤p®É
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]
  
³o¼Ëªº¦¬¤J¡A¨¬°÷¤TÀ\·Å¹¡¡F¶R¨®¤l¡B©Ð¤l«j±j°÷¥Î¡F§O§Ñ¤F¡AÁÙ¦³¤l¤kªº±Ð¨|¶O¡B¦Û¤vªº¾i¦Ñª÷¡BÁÙ¦³¡y¹Ú·Q¡zµ¥«Ý¹ê²{¡I
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@¥Í¡H
  

  

  
¤£·Q¦A¦¬«H(Unsubscribe) 


¡@




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message


Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

2003-03-03 Thread Mike Tancsa
At 09:11 AM 03/03/2003 -0800, FreeBSD Security Advisories wrote:
Module: contrib_sendmail
Announced:  2003-03-03
Credits:Mark Dowd (ISS)
Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4
FreeBSD 4-STABLE prior to the correction date
Corrected:  2003-03-03
1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0,


Hi,
I dont see this in the cvsup commit logs yet ?
---Mike 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


¦³¾÷·|§AÄ@·N¥h¹Á¸Õ¶Ü??

2003-03-03 Thread star
Title: ¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿


¥D¦®: ³o©Î³\¬O±z¥¿¦b´M§äªº¾÷·|³á 
 
 
 
   
   
³o©Î³\¬O±z¥¿¦b§äªº¾÷·|[EMAIL PROTECTED] 
   
¹ï¤£°_¡I¥´ÂZ¤F¡A¦pªG¦]¦¹³y¦¨±zªº§xÂZ¡A½Ðª½±µ§R°£¥»«H¤ÎÂI¿ï¤U¤è¡u¤£·Q¦A¦¬«H¡v¡A§Ú­Ì·|±N±zªº¸ê®Æ§R°£¡I 
   
 
   
 
   
¬°¤°»ò¦³¤H·|¤ñ§A¦¨¥\10­¿¡A¦¬¤J¦h100­¿¡B¬Æ¦Ü¦h1000­¿¡AÃø¹D¥L¦³¤ñ§A¦hÁo©ú³o»ò¦h¶Ü¡H 
   
µª®×ªÖ©w¤£¬Oªº¡I 
   
[EMAIL PROTECTED] 
   
¥L­Ì¨ì©³°µ¤F¤°»ò¬O§Ú­Ì©Ò¤£ª¾¹Dªº¨Æ¡H 
   
¦Ó§Ú­Ì¨ì©³°µ¿ù¤F¤°»ò¡B¤S¿ù¹L¤F¤°»ò¡H 
   
·Q¤£·Qª¾¹D¤H®a«ç»ò°µ­Ëªº¡I
  
§A¬Û«H¡u®É¶¡¡×ª÷¿ú¡v¡BÁÙ¬O¡u®É¶¡¡Öª÷¿ú¡v
  

  Á|¨Ò¡G
  
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@®É¼Æ¡H
  
¢·¤p®É¡¯¢²¢µ¢´¤Ñ¡¯¢²¢¯¦~¡×¢·¢¶,¢µ¢¯¢¯¤p®É
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@[EMAIL PROTECTED]
  
³o¼Ëªº¦¬¤J¡A¨¬°÷¤TÀ\·Å¹¡¡F¶R¨®¤l¡B©Ð¤l«j±j°÷¥Î¡F§O§Ñ¤F¡AÁÙ¦³¤l¤kªº±Ð¨|¶O¡B¦Û¤vªº¾i¦Ñª÷¡BÁÙ¦³¡y¹Ú·Q¡zµ¥«Ý¹ê²{¡I
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]
  
[EMAIL PROTECTED]@¥Í¡H
  

  

  
¤£·Q¦A¦¬«H(Unsubscribe) 


¡@




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message


Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

2003-03-03 Thread Bruce A. Mah
If memory serves me right, Mike Tancsa wrote:
 At 09:11 AM 03/03/2003 -0800, FreeBSD Security Advisories wrote:
 Module: contrib_sendmail
 Announced:  2003-03-03
 Credits:Mark Dowd (ISS)
 Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4
 FreeBSD 4-STABLE prior to the correction date
 Corrected:  2003-03-03
 1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0,
 
 
 Hi,
 I dont see this in the cvsup commit logs yet ?

Every cvsup mirror updates on a periodic schedule.  The commits to the
src tree (which happened about 30 minutes ago) probably haven't made
it to all the mirrors yet.  (You can see the changes in cvsweb,
probably the cvs-all mailing list archives as well.)

Bruce.


pgp0.pgp
Description: PGP signature


Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

2003-03-03 Thread Barney Wolff
On Mon, Mar 03, 2003 at 09:57:06AM -0800, Bruce A. Mah wrote:
 
 Every cvsup mirror updates on a periodic schedule.  The commits to the
 src tree (which happened about 30 minutes ago) probably haven't made
 it to all the mirrors yet.  (You can see the changes in cvsweb,
 probably the cvs-all mailing list archives as well.)

As of 13:06 EST, the commits had made it to head but were NOT tagged
with RELENG_4 or RELENG_5_0 from cvsup3.  I gave up and downloaded the
patch, which worked fine on both of the above.

-- 
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

2003-03-03 Thread Garrett Wollman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

In article [EMAIL PROTECTED] Barney Wolff writes:

As of 13:06 EST, the commits had made it to head but were NOT tagged
with RELENG_4 or RELENG_5_0 from cvsup3.

cvsup3 updates every hour at 15 after.  I'm afraid you were just
unlucky.

- -GAWollman

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE+Y6adI+eG6b7tlG4RAm8mAJ9zvDTk24BAwUdcPCyOgunxCaVTTwCfZG3s
4XdMunELySmG5NpUTrOuMnA=
=Cw+h
-END PGP SIGNATURE-

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


Re: Is XFree86 4.3.0 going to be in 4.8? -nt-

2003-03-03 Thread Bruce A. Mah
At this point, I'd guess probably not, given that there was (is?) some
amount of work for the MAINTAINER to do to get it to build correctly,
and there's not much chance for testing before the release, which is
only two weeks away.

That's just my guess, though, not a policy statement.  :-)

Bruce.



pgp0.pgp
Description: PGP signature


Re: VM issues in -stable?

2003-03-03 Thread Kachun Lee
In article [EMAIL PROTECTED], you say...



David Schultz wrote:

 Thus spake Scott Sewall [EMAIL PROTECTED]:
 
  The FreeBSD July - August 2002 Status Report mentions some VM issues in
  -stable related to vm_map corruption
  on large-memory systems under heavy loads. The report indicates there is
  ongoing work to MFC the bug fixes.
 
  Has the work to MFC the bug fixes to -stable been completed?
 
  I have a 4.6.2 system with 2GB of memory that's getting a page fault
  while in kernel mode. The failure occurs
  when periodic daily is run. The active process is always find. I
  suspect this system may be experiencing the
  problem described by the report.

 If you post the panic message and a backtrace, people might be
 able to tell you more about the particular bug you're running
 into.

Here's the panic message, the gdb backtrace and dmesg boot ouput.

-- Scott


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc02d4f53
stack pointer   = 0x10:0xff605c70
frame pointer   = 0x10:0xff605ca4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 275 (find)
interrupt mask  = bio
panic: from debugger
panic: from debugger

If you don't think you had hardware problem, one possibility could be your 
kernel reached the default 1G size limit (esp with 2G or RAM). Check with:

  sysctl -a | fgrep kvm

if you kvm_free is get very close to the kvm_size, you may want to increase 
KVM_PAGES and see if that fixes your problem.

 [snip


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail

2003-03-03 Thread Stefan `Sec` Zehl
At 09:11 AM 03/03/2003 -0800, FreeBSD Security Advisories wrote:
Module: contrib_sendmail
Announced:  2003-03-03
Credits:Mark Dowd (ISS)
Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4
 FreeBSD 4-STABLE prior to the correction date
Corrected:  2003-03-03
1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0,

I still have a FreeBSD-2.8 (-STABLE) system running which includes
sendmail-8.8.8. As the patches on sendmail.org only apply to
sendmail-8.9 - sendmail-8.12, i ported the patch.

Perhaps someone else needs this patch, so I've put it up for ftp at 
ftp://ftp.42.org/sendmail.8.8.8.patch

As I don't have an example E-Mail to test, I can not _guarantee_ that
this fixes it. But given the fact that I only had to change two lines
(which both were function declarations) from the official supported
patch, I'm sure that this patch fixes the problem.

CU,
Sec
-- 
``oh no! the gronkulator is broken!''

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message


Re: Dell PowerVault 725N support

2003-03-03 Thread Julian C. Dunn
On Thu, 2003-02-27 at 12:33, Patrick Bihan-Faou wrote:

 I tried to get as much information as possible from Dell's web site, but the
 only reference to chipsets and such was 'ServerWorks GC-SL w/CIOB-E'.
 Looking at the hardware notes for the upcoming FreeBSD 4.8 I don't see this
 mentionned anywhere, but it might be just a marketing name for something
 old.

We are using boards with ServerWorks chipsets on all our production
machines running 4.6 and 4.7-STABLE and we have had no problems in
almost two years. The PCI bridge on these boards shows up as a

pcib0: ServerWorks NB6635 3.0LE host to PCI bridge on motherboard

Now, like all good BIOS manufacturers :-) they probably called them
something different even when we bought them.

- Julian

-- 
-- Julian C. Dunn, B.A.Sc.  [EMAIL PROTECTED]
-- Senior Software Developer / UNIX Systems Administrator
-- VerticalScope Inc.
-- 111 Peter St., Suite 700, Toronto, ON
-- Tel: (416) 341-8950 x236  Fax: (416) 341-8959

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message