Re: php5 port compile problem
Well, yeah that's what I did and it did solve my problem. Not the best way to solve it, but if you really want php5 you can do it like that :) I believe 5-stable solved this problem because it switched to bind9, but 4-stable still misses those functions (because of bind8?). Xander - Original Message - From: [EMAIL PROTECTED] To: Xander Damen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday 01 November 2004 2:18 Subject: Re: php5 port compile problem Hi Xander, Thanks for the info, but do you mean the bind9 port? I'm not excited about installing a port for bind when it is in the base distro already, but... joel I know this problem! I encountered it a few months ago when php5 was this beta. What I found was that you need bind9 for php5, so install bind9 and your problem is solved. Greets, Xander - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday 29 October 2004 8:03 Subject: php5 port compile problem Hi, After a make update in /usr/src today (about an hour ago): ext/standard/dns.lo(.text+0x1c6c): In function `.L163': : undefined reference to `res_ninit' ext/standard/dns.lo(.text+0x1cd8): In function `.L163': : undefined reference to `res_nmkquery' ext/standard/dns.lo(.text+0x1d0a): In function `.L163': : undefined reference to `res_nsend' ext/standard/dns.lo(.text+0x1e9a): In function `.L163': : undefined reference to `res_nclose' *** Error code 1 Stop in /usr/ports/lang/php5/work/php-5.0.2. *** Error code 1 Stop in /usr/ports/lang/php5. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall88483.0 make DEPENDS_TARGET=package ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! lang/php5 (linker error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Hope this is the right place to bring this up? joel -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
firewall stable vs current
Hello All, what is the diffrent between firewall stable and current what is diffrent beetween deny or reject what is the best market practice Best Regards , @ Mohd Rasfan Bin Mohd Nor System Network Administrator Mobile : 019-2792472 Office : 03-42967102 Fax: 03-42967126 Website: http://www.nadi-it.com E-Mail : rasfan[at]nadi-it.com : rasfan[at]rasfan.net @ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Future support for PERC 4e/XX cards
On Oct 26, 2004, at 10:51 AM, Gareth Hopkins wrote: Was wondering if the following cards would be supported in the near future by BSD 4.10. PERC 4e/Si and PERC 4e/Di. These are from the new Dell poweredge 1850 and 2850 servers. Did you try them and they did not work, or are you looking to see if they will work before you buy them? I suspect they'll work since Dell uses mostly AMI cards which work with the amr RAID driver, or the Adaptec cards which work with the aac driver. If you ask your dell server specialist, they can tell you what chipset is uses and that will be a better indication of whether it will work.
Problems After Upgrading from 4.9-RELEASE-p4 To 4.10-RELEASE-p3
I've been happily using 4.9-RELEASE-p4 since April 2004. Over the weekend, I decided to upgrade to 4.10-RELEASE-p3 to fix the pthreads problem since I had just added an external tape drive to the QLogic SCSI card that was already in my system. Anyway, after upgrading, I experienced the same symptoms as described in this message: http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016933.html In reading the thread, it seems there was an infinite loop problem in the ahc driver code that was fixed later by Justin Gibbs. So I tried upgrading to 4-STABLE to see if the problem was fixed there. But I still have the same symptoms. I also see these odd processes in my ps output: root34 0.0 0.0 212 40 ?? Is 10:19PM 0:00.00 adjkerntz root20 0.0 0.0 596 48 ?? DLs 10:08PM 0:00.02 vinum root13 0.0 0.0 00 ?? DL 10:08PM 0:00.04 vnlru root12 0.0 0.0 00 ?? DL 10:08PM 0:01.39 syncer root11 0.0 0.0 00 ?? DL 10:08PM 0:00.26 bufdaemon root10 0.0 0.0 00 ?? DL 10:08PM 0:00.00 vmdaemon root 9 0.0 0.0 00 ?? DL 10:08PM 0:00.73 pagedaemon root 8 0.0 0.0 00 ?? DL 10:08PM 0:00.00 aic_recovery1 root 7 0.0 0.0 00 ?? DL 10:08PM 0:00.00 aic_recovery1 root 6 0.0 0.0 00 ?? DL 10:08PM 0:00.00 aic_recovery0 root 5 0.0 0.0 00 ?? DL 10:08PM 0:00.00 aic_recovery0 root 4 0.0 0.0 00 ?? DL 10:08PM 0:00.00 usbtask root 3 0.0 0.0 00 ?? DL 10:08PM 0:00.00 usb0 root 2 0.0 0.0 00 ?? DL 10:08PM 0:00.00 taskqueue root 1 0.0 0.1 552 128 ?? ILs 10:08PM 0:00.01 init root 0 0.0 0.0 00 ?? DLs 10:08PM 0:00.00 swapper I find them odd because the system was powered off/on at 6:19AM after the machine was shutdown at about 10:08PM. (I tried waiting overnight to see if it would actually finish it's shutdown.) And finally, I have one vinum volume that has problems. However after the system comes up, I can remove and re-create the volume and all of my data is intact. I'm assuming that if I get the shutdown issue resolved, these other problems will heal themselves. I'd appreciate any advice you might have on how to get my system running on 4.10. My dmesg output follows. Please let me know if there's any other info I can provide. Thanks, Drew - blacklamb# uname -a FreeBSD blacklamb.mykitchentable.net 4.10-STABLE FreeBSD 4.10-STABLE #0: Sun Oct 31 21:23:11 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLACKLAMB i386 blacklamb# dmesg Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #0: Sun Oct 31 21:23:11 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLACKLAMB Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x387fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 201261056 (196544K bytes) config # di pcic0 Invalid command or syntax. Type `?' for help. config # di ata1 Invalid command or syntax. Type `?' for help. config # di ata0 Invalid command or syntax. Type `?' for help. config # di aic0 Invalid command or syntax. Type `?' for help. config # di adv0 Invalid command or syntax. Type `?' for help. config q avail memory = 191930368 (187432K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc03bb000. Preloaded userconfig_script /boot/kernel.conf at 0xc03bb09c. Preloaded elf module ispfw.ko at 0xc03bb0ec. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00fdf10 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard IOAPIC #0 intpin 19 - irq 2 IOAPIC #0 intpin 18 - irq 5 IOAPIC #0 intpin 17 - irq 10 IOAPIC #0 intpin 16 - irq 11 pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: ATI Mach64-GZ graphics accelerator at 0.0 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0x1c90-0x1c9f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port
Re: Why the mode of /dev/null is changed after system reboot?
On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote: I have a gateway running FreeBSD 4.10-p3. Normally, the mode of /dev/null should be 666, but recently, I find that its mode is changed to 600 automatically after reboot, I have checked all /etc/rc* and /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( Probably a local error. Try changing scripts to #!/bin/sh -x and carefully watch (or log) the boot process. Start with any local scripts you have since it's most likely to be a problem there. Kris pgpM1lvdAkgJS.pgp Description: PGP signature
Re: Why the mode of /dev/null is changed after system reboot?
On Mon, 2004-11-01 at 09:30 -0800, Kris Kennaway wrote: On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote: I have a gateway running FreeBSD 4.10-p3. Normally, the mode of /dev/null should be 666, but recently, I find that its mode is changed to 600 automatically after reboot, I have checked all /etc/rc* and /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( Probably a local error. Try changing scripts to #!/bin/sh -x and carefully watch (or log) the boot process. Start with any local scripts you have since it's most likely to be a problem there. Kris Actually I have found this happening on my 4.10 boxen as well. I thought it was some one-time glitch and just chmodded the thing back. Didn't even think about it until I saw this post. I will try to see if I can catch the circumstances surrounding it if it happens again. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why the mode of /dev/null is changed after system reboot?
On Mon, Nov 01, 2004 at 02:49:48PM -0500, Sven Willenberger wrote: On Mon, 2004-11-01 at 09:30 -0800, Kris Kennaway wrote: On Mon, Nov 01, 2004 at 09:19:12AM +0800, Iva Hesy wrote: I have a gateway running FreeBSD 4.10-p3. Normally, the mode of /dev/null should be 666, but recently, I find that its mode is changed to 600 automatically after reboot, I have checked all /etc/rc* and /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( Probably a local error. Try changing scripts to #!/bin/sh -x and carefully watch (or log) the boot process. Start with any local scripts you have since it's most likely to be a problem there. Kris Actually I have found this happening on my 4.10 boxen as well. I thought it was some one-time glitch and just chmodded the thing back. Didn't even think about it until I saw this post. I will try to see if I can catch the circumstances surrounding it if it happens again. It could be a port doing this at startup, but we still need more debugging.. Kris pgpR0wgaJKS5D.pgp Description: PGP signature
exim-sa Build procedure issues.
Hi, I recently installed Exim 4 with SpamAssassin at smtp-time suport from FreeBSD ports. (Most recent collection downloaded from the freebsd.org site.) The port is exim-sa-exim in the mail collection. There were some problems with the build procedure that could be automated : 1. The sa-exim-4.1 files are downloaded properly, but the exim source is not patched by the localscan_dlopen_exim_4.20_or_better.patch file. 2. localscan_dlopen_exim_4.20_or_better.patch needs to actually be edited itself to work on FreeBSD - the line reading : +LFLAGS=-rdynamic -ldl should actually read : +LFLAGS=-rdynamic Once exim is then built, getting it to work with spamassassin is quite simple. [nb. reading through a newsgate] -- Regards, Andy Davidson http://fotoserve.com/ - Real photographic prints from your digital camera. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why the mode of /dev/null is changed after system reboot?
On Mon, 1 Nov 2004, Sven Willenberger wrote: SW I have a gateway running FreeBSD 4.10-p3. Normally, the mode of SW /dev/null should be 666, but recently, I find that its mode is changed SW to 600 automatically after reboot, I have checked all /etc/rc* and SW /usr/local/etc/rc.d/*, but I can't get anything that led to it...:-( SW SW Probably a local error. Try changing scripts to #!/bin/sh -x and SW carefully watch (or log) the boot process. Start with any local SW scripts you have since it's most likely to be a problem there. SW SW Actually I have found this happening on my 4.10 boxen as well. I thought SW it was some one-time glitch and just chmodded the thing back. Didn't SW even think about it until I saw this post. I will try to see if I can SW catch the circumstances surrounding it if it happens again. I remember I stepped into this once or twice in the past. Bad umask at mergemaster/MAKEDEV time possibly? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why the mode of /dev/null is changed after system reboot?
It could be a port doing this at startup, but we still need more debugging.. Kris I think that sshd2 does this. because I installed it only recently... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why the mode of /dev/null is changed after system reboot?
No, it just happened after system reboot...:-) If I chmod it to 666it will re-chmod it to 600 after system reboot. On Tue, 2 Nov 2004 09:08:15 +0300 (MSK), Dmitry Morozovsky [EMAIL PROTECTED] wrote: I remember I stepped into this once or twice in the past. Bad umask at mergemaster/MAKEDEV time possibly? Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
