php5: php5-zip/php5-filter fail to upgrade after the portupdate of php5
Both with php5-filter and php5-zip I run into trouble. After php5 got updated (I followed steps located in ports/UPDATING, but I guess I missed something) I can not upgrade the packages php5-zip php5-filter Both report an error in /usr/local/include/php/ext/pcre/php_pcre.h. I tried to move the above php_pcre.h to php_pcre.h.off with the success being unable to build anything. Reinstalling of ports pcre, phph5.5.X.X didn't result in success. What to do? Is there a remnant/old file/header out there? Thanks for the help. Regards, O. Hartmann In file included from /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:30: /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No such file or directory In file included from /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:30: /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /usr/local/include/php/ext/pcre/php_pcre.h:38: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /usr/local/include/php/ext/pcre/php_pcre.h:44: error: expected specifier-qualifier-list before 'pcre' /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c: In function 'php_zip_pcre': /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: 'pcre' undeclared (first use in this function) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: (Each undeclared identifier is reported only once /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: for each function it appears in.) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: 're' undeclared (first use in this function) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:603: error: 'pcre_extra' undeclared (first use in this function) *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/archivers/php5-zip. === make failed for archivers/php5-zip === Aborting update -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: php5: php5-zip/php5-filter fail to upgrade after the portupdate of php5
try to uninstall all php5-* ports, and reinstall again. I guess there are some problem with old (php52) header files. 2010/4/16 O. Hartmann ohart...@zedat.fu-berlin.de Both with php5-filter and php5-zip I run into trouble. After php5 got updated (I followed steps located in ports/UPDATING, but I guess I missed something) I can not upgrade the packages php5-zip php5-filter Both report an error in /usr/local/include/php/ext/pcre/php_pcre.h. I tried to move the above php_pcre.h to php_pcre.h.off with the success being unable to build anything. Reinstalling of ports pcre, phph5.5.X.X didn't result in success. What to do? Is there a remnant/old file/header out there? Thanks for the help. Regards, O. Hartmann In file included from /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:30: /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No such file or directory In file included from /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:30: /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /usr/local/include/php/ext/pcre/php_pcre.h:38: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token /usr/local/include/php/ext/pcre/php_pcre.h:44: error: expected specifier-qualifier-list before 'pcre' /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c: In function 'php_zip_pcre': /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: 'pcre' undeclared (first use in this function) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: (Each undeclared identifier is reported only once /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: for each function it appears in.) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:602: error: 're' undeclared (first use in this function) /usr/ports/archivers/php5-zip/work/php-5.3.2/ext/zip/php_zip.c:603: error: 'pcre_extra' undeclared (first use in this function) *** Error code 1 1 error *** Error code 1 Stop in /usr/ports/archivers/php5-zip. === make failed for archivers/php5-zip === Aborting update -- ___ freebsd-po...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ACPI? problem with release 8.0 | Perhaps solved?
My RELEASE-8.0 has now been up for about 2hr, not long enough to be sure the difficulty is circumvented, but long enough to look promising. Previously RELEASE-8.0 has not stayed up more than about 4min. I tried setting machdep.idle to acpi and then to hlt without success. But I now have set machdep.idle=spin. Discovered there can be some problem in trying to set this too early -- in particular in loader.conf -- presumably because acpi.ko is not yet loaded. I ended up making sure everything was ready by putting: #!/bin/sh echo setting machdep.idle=spin /sbin/sysctl machdep.idle=spin in /etc/rc.local To check what is happening I've created /usr/local/bin/sysctldump.sh as: #!/bin/sh [ -f /tmp/sysctl.dump.4 ] mv -f /tmp/sysctl.dump.4 /tmp/sysctl.dump.5 [ -f /tmp/sysctl.dump.3 ] mv -f /tmp/sysctl.dump.3 /tmp/sysctl.dump.4 [ -f /tmp/sysctl.dump.2 ] mv -f /tmp/sysctl.dump.2 /tmp/sysctl.dump.3 [ -f /tmp/sysctl.dump.1 ] mv -f /tmp/sysctl.dump.1 /tmp/sysctl.dump.2 [ -f /tmp/sysctl.dump ] mv -f /tmp/sysctl.dump /tmp/sysctl.dump.1 sysctl -ao /tmp/sysctl.dump and adding: #sysctl dump 1-59/2 * * * * root /usr/local/bin/sysctldump.sh to /etc/crontab. I feel somewhat concerned that this cronjob may be sufficiently frequent to prevent the system looking for the idle state and thus circumventing the problem in same other way. So I'm not yet convinced that I have a real solution. I'll try removing the cronjob. Thanks again for your attention, Regards, Malcolm Kay On Tue, 13 Apr 2010 02:38 pm, Malcolm Kay wrote: On Tue, 13 Apr 2010 04:03 am, Ian Smith wrote: In freebsd-questions Digest, Vol 306, Issue 1, Message: 18 On Mon, 12 Apr 2010 15:31:33 +0930 Malcolm Kay malcolm@internode.on.net wrote: I desperately need to make some progress on this issue. Then I suggest taking it to freebsd-acpi@ without passing go .. maybe with a bit more data to hand, as outlined in the ACPI debugging section of the handbook. Yes, I have now realised this; but now somewhat reticent to move there now and be criticised for cross-posting Is it likely that the issue is real rather than hardware or disk corruption? Earlier releases are operating OK on the same machine. Sounds like a real issue, but I don't know the hardware. Does it have the latest available BIOS update? If not, that's step one. Will it stay up long enough to get a verbose dmesg off it? Do you have a verbose dmesg from an earlier working release for comparison? Probably not; I have considered it. But the manufacturer's site warns not to upgrade unless you have identifyable problems (or something similar). And since earlier release work well I'm not anxious to open a new can of worms. If I become sufficiently desparate I'll try it. I have now confirmed that: debug.acpi.disabled=acad button cpu lid thermal timer video still leaves the system crashing and powering down when idle for a while. And the more extensive: debug.acpi.disabled=acad bus children button cmbat cpu ec isa lid pci pci_link sysresource thermal timer video does the same. I don't really need power management but with acpi disabled the disks are not visible to the system. ACPI needs to work on modern hardware, no question. Are there sysctl variables that can influence this behaviour? Currently I believe we have: hw.acpi.supported_sleep_state: S1 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: NONE hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 May help to set hw.acpi.verbose=1 in /boot/loader.conf while debugging; especially useful after verbose boot for detail in dmesg and messages. Looks as though it might be useful, but I'm starting to believe acpi itself may not be the problem hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.cpu.cx_lowest: C1 Is that with acpi.thermal disabled? No, this is run with acpi as default configured. Boot | login as root | sysctl -a sysctl.dump | shutdown -p now (Get out before crash so that I don't get into trouble with fsck on reboot, yes it runs in the background but takes forever.) Rebooting in FreeBSD 7.0 I can now mount the 8.0 partitions and look at the dump in my own time -- and also prepare these emails. (Fsck also runs under 7.0 on the 8.0 partitions if 8.0 was allowed to crash.) If so, showing hw.acpi and debug.acpi with everything enabled might provide more clues. OK machdep.idle: amdc1e machdep.idle_available: spin, amdc1e, hlt, acpi, However on the earlier RELEASEs that work I note we do not have machdep.idle or machdep.idle_available. Instead I find: machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 Although I've not been
ports/144403: graphics/php5-gd does not load libpng
Does it solved in PHP 5.3.x only? Unfortunately 5.3 and 5.2 code are not fully compatible, PHP-based software (like CMS and BBs) updates slowly, and most of webmasters couldn't migrate to 5.3 just in moment. Would it be fixed for 5.2.x? Or the only way to get gd work with PHP 5.2.x is downgrading of *png* port? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: installation problem
I guess I have the same problem. I trying to install 7.2-RELEASE on server with Supermicro X8DTU-Fhttp://market.yandex.ru/model.xml?modelid=4633058MB. BIOS is the newest. Just in time I boot from CD I get such errors after detecting CPU: acd0: TIMEOUT - READ_BIG retrying (1 retry left) acd0: TIMEOUT - READ_BIG retrying (0 retry left) acd0: FAILURE - READ_BIG timed out And boot fails. But if I eject CD from CD-ROM after FreeBSD kernel loads, all going OK. But in this way I unable to continue installation from CD, course even I insert CD during sysinstall, it cannot mount it and copy distributions to my machine. I have tried to boot through choosing 6 in loader menu and type - set hw.ata.atapi_dma=0 - boot But it doesn't give any effect. Situation was recalled on two X8DTU-F motherboards, so it isn't hardware problem. CD-ROM is SATA, TEAC DV-28S. Photo: http://img-fotki.yandex.ru/get/3809/rc5hack.22/0_3aa92_84133e96_orig ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD PXE installation howto
Hi all, I have seen a way for reducing some steps... after installing dhcpd and active tftpd in inetd.conf and starting inetd... have just done : tar -C /expert/netboot/freebsd8 -pxvf 8.0-RELEASE-amd64-disc1.iso (really it's an own release based on release plus security patches RELENG_8_0 but for the example is the same...) and after just entering the install.cfg in the mfsroot and after changing in nfs-root-path/boot/loader.conf for having the line : vfs.root.mountfrom=ufs:/dev/md0 it works the same way too... Are the freebsd iso releases (either of the web or those made by make release) shipped with all necessary for all boot modes (pxe, cd, hd...).. without needing to do nothing for, for example making a freebsd installation server?.. Thanks a lot for you're time. Bye!! Hi, I'm working on a project for setting up a freebsd installation server with pxe. When I started I see the doc was a bit old-fashioned... so I started looking at some blogs... freebsd doc that could help me understanding the whole process and so on... finally I have ended looking at source code of some involved parts like sysintall, boot stages and so on for understanding all properly for setting up this service. I have written a documentation that if you see it to be ok... (it seems to be working fine) perhaps, would be nice to appear in handbook or in some official documentation site... So if you see something that should be done in another way... or some point wich you consider it's wrong... please make me know and I'll correct it. The url in wich you could fetch the pdf file is : http://postfixquotareject.ramattack.net/freebsdpxehowto.pdf Thank you very much. Bye!!___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql60 port broken? Its 10:00. Do U know where ur mysqlclient.16 is?
On Thu, 15 Apr 2010 20:26:58 -0500, Gene f...@brightstar.bomgardner.net articulated: Hi - I'm running FBSD 8.0 amd64. Already installed are ports fo php5 and mysql server and client 5.5.2. Before beginning I did a portsnap fetch update. I've been trying to install databases/php5-mysqli. It complains that it can't find mysqlclient.16. So I thought the missing file might be part of mysql version 60. When attempting to make mysql60-server, I get: === mysql-server-6.0.11 cannot install: unknown MySQL version: 60. *** Error code 1 Stop in /usr/ports/databases/mysql60-server. Question 1) Why can mysqlclient.16 not be found? Could it actually need libmysqlclient.so.16? Question 2) What's up with mysql60-server? Is the port broken? grep -i mysql60 /usr/ports/MOVED databases/mysql60-client||2010-01-10|Has expired: no longer under development databases/mysql60-server||2010-01-10|Has expired: no longer under development databases/mysql60-scripts||2010-01-10|Has expired: no longer under development databases/p5-DBD-mysql60||2010-01-10|Has expired: no longer under development The MySQL60 port has been gone for a while now. I know, because I was in the same boat. Use portupgrade with the -o flag to fix the problem. -- Jerry freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Fortune's Office Door Sign of the Week: Do not incorrige. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql60 port broken? Its 10:00. Do U know where ur mysqlclient.16 is?
Jerry writes: Question 1) Why can mysqlclient.16 not be found? Could it actually need libmysqlclient.so.16? Question 2) What's up with mysql60-server? Is the port broken? The MySQL60 port has been gone for a while now. I know, because I was in the same boat. Use portupgrade with the -o flag to fix the problem. When this happened to me, I was tolk 5.5 is the line under active development. I (with trepidation) de-installed 6.0, installed 5.5, and everything worked. Of course, I'm using it mainly to learn how; your experience may be different. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Requesting community opinion regarding security/pam_ldap groupdn and member_attribute
Hello community, I am working these days on implementing a centralized authentication/authorization service for all the FBSD servers I have. I am using OpenLDAP to store the user and GOsa (https://oss.gonicus.de/) as a web frontend to administer the directory. To enable SSH/console authentication from LDAP I noticed that one can use security/pam_ldap from ports and net/nss_ldap so that the name service switch can get groups/passwd info from LDAP too. I have successfully configured OpenLDAP and created a user as follows: dn: cn=Valentin BUD,ou=people,dc=example,dc=com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: shadowAccount sn: BUD givenName: Valentin uid: mtx cn: Valentin BUD homeDirectory: /home/mtx loginShell: /bin/tcsh uidNumber: 5001 gidNumber: 5001 gecos: Valentin BUD and a posixGroup as follows: dn: cn=ssh,ou=groups,ou=people,dc=example,dc=com objectClass: top objectClass: posixGroup cn: ssh gidNumber: 7000 description: SSH allowed users memberUid: mtx I have configured pam_ldap to honor group membership using pam_groupdn cn=ssh,ou=groups,ou=people,dc=example,dc=com pam_member_attribute memberUid The problem is that pam_ldap wants the memberUid attribute to contain the user's DN and there is no option to change this behavior. My question is: what is the argument behind this and do you think it should stay this way or could it be changed? In my case I really need pam_ldap to check just for UID not DN of a user in memberUid attribute. I have asked our friend google what does he has to say about this and found out that there is a patch on Debian which can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341541 that gives the user the possibility to choose if the memberUid attribute holds the DN or UID. I would really like that feature so I have patched pam_ldap to no success and since my C programming skills are close to none I am stuck. Would you people think that the above patch would be useful? Please argument on this. How can I/we make that patch work? Thank you very much and a great day, v -- network warrior since 2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: console no responding to key in.
On Thu, 15 Apr 2010 14:15:24 -0700, Chuck Swiger cswi...@mac.com wrote: On Apr 15, 2010, at 1:26 PM, Jessie Xu wrote: I must fix the problem since I need console login with root. Any insight on this? thanks. Our machines are Dell PowerEdge 2650 (2U rack mountable) , come with Video port, PS2 keyboard/Mouse ports, and two Serial ports. -- I also tried the serial ports for console access, no lucky. PS/2 isn't a hot-pluggable interface. On older hardware, you can blow a fuse on the motherboard by trying to do so while the machine is on, although newer equipment uses a polyfuse (aka PPTC or resettable fuse) to avoid permanent damage. An important advice! If there was no keyboard there initially, then the hardware may never attempt to use one added later, short of a power-cycle. If there was no atkbd: at boot time, attaching it later on will not introduce it to the system. As you said, Chuck, it may even destroy hardware to try to do so, leading to the fact that you have a server with *no* AT keyboard at all. I've already seen that with older systems not using a resettable fuse. In such cases, trying a USB keyboard instead might work better. Jessie Xu initially said he was on FreeBSD 4. If I remember correctly, what you suggest isn't possible in the default configuration. Maybe a USB keyboard will be detected, causing a ukbd: message in the log, but that's all - no input from it. You need to type kbdcontrol -k device to switch over from the default AT keyboard to the USB keyboard, there's no kbdmux in 4. As for servers, trying to connect via serial console seems to be the standard way. Otherwise, attach keyboard and monitor to the system while the power is off. REALLY OFF (pull mains plug to be really sure - see PS/2 defect mentioned above). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
OpenSSL 0.9.8k - 0.9.8l
Hi, I run a few web servers with need to be PCI compliant. Apparently there's a problem with OpenSSL 0.9.8k that requires us to upgrade to 0.9.8l for us to maintain our compliance level. I've csup'd to RELENG_8_0 and did a build/install cycle and OpenSSL is still at 0.9.8k. Using RELENG_8 isn't really an option for me because the last I upgraded to that level, ipfw was broken and I'm not sure that the problem with ipfw has been fixed (Luigi tells me that it has, but I haven't had time to test it yet). Is there any movement to patch RELENG_8_0 with OpenSSL 0.9.8l? Or will I be stuck with 0.9.8k until I move to RELENG_8? Tim Gustafson Baskin School of Engineering UC Santa Cruz t...@soe.ucsc.edu 831-459-5354 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: console no responding to key in.
Thanks. But I have some of consoles did work - response the key in after the keyboard pluged in after. This is important. Almost all the servers in rack don't have keyboard collected unless we need to login to console. I couldn't plug in the keyboard then reboot the server to get access to the console. Jessie Xu Unix Administrator jessie...@cryptologic.com desk phone: 416 545 1453 x 5618 Skype: Jessie.xu972 -Original Message- From: Polytropon [mailto:free...@edvax.de] Sent: Friday, April 16, 2010 10:26 AM To: Chuck Swiger Cc: Jessie Xu; freebsd-questions@freebsd.org Subject: Re: console no responding to key in. On Thu, 15 Apr 2010 14:15:24 -0700, Chuck Swiger cswi...@mac.com wrote: On Apr 15, 2010, at 1:26 PM, Jessie Xu wrote: I must fix the problem since I need console login with root. Any insight on this? thanks. Our machines are Dell PowerEdge 2650 (2U rack mountable) , come with Video port, PS2 keyboard/Mouse ports, and two Serial ports. -- I also tried the serial ports for console access, no lucky. PS/2 isn't a hot-pluggable interface. On older hardware, you can blow a fuse on the motherboard by trying to do so while the machine is on, although newer equipment uses a polyfuse (aka PPTC or resettable fuse) to avoid permanent damage. An important advice! If there was no keyboard there initially, then the hardware may never attempt to use one added later, short of a power-cycle. If there was no atkbd: at boot time, attaching it later on will not introduce it to the system. As you said, Chuck, it may even destroy hardware to try to do so, leading to the fact that you have a server with *no* AT keyboard at all. I've already seen that with older systems not using a resettable fuse. In such cases, trying a USB keyboard instead might work better. Jessie Xu initially said he was on FreeBSD 4. If I remember correctly, what you suggest isn't possible in the default configuration. Maybe a USB keyboard will be detected, causing a ukbd: message in the log, but that's all - no input from it. You need to type kbdcontrol -k device to switch over from the default AT keyboard to the USB keyboard, there's no kbdmux in 4. As for servers, trying to connect via serial console seems to be the standard way. Otherwise, attach keyboard and monitor to the system while the power is off. REALLY OFF (pull mains plug to be really sure - see PS/2 defect mentioned above). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: console no responding to key in.
On Fri, 16 Apr 2010 12:20:46 -0400, Jessie Xu jessie...@cryptologic.com wrote: But I have some of consoles did work - response the key in after the keyboard pluged in after. This could be a configuration topic. In /etc/ttys you can intendedly disable consoles (virtual terminals). If this has been the case, trying to login locally won't work. You could try to boot the system from a live CD or DVD to check the configuration. If you can reboot the machines, try to enter into single user mode. In this case, local console login usually is enabled, but it may require the root password. See man 5 ttys for possible details. This is important. Almost all the servers in rack don't have keyboard collected unless we need to login to console. As it has been mentioned, connecting a PS/2 keyboard to a running machine can be a really bad idea - even causing a defect of the PS/2 keyboard connectors. And with USB, you're mostly unlucky on FreeBSD 4 machines due to the lack of kbdmux / automatisms like via devd. I couldn't plug in the keyboard then reboot the server to get access to the console. If configured properly, it should be sufficient to press the power key to initiate a controlled system shutdown. This should give you the chance to try SUM or a live CD. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Porting NetworkManager to FreeBSD
Has there been any movement on porting NetworkManager http://projects.gnome.org/NetworkManager/ to FreeBSD? I read something awhile ago, I don't remember where, that it was planned for the 8.0 release (I think). I have seen it in use on a friends PC, and it is really awesome. -- Jerry freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ The Martian Canals were clearly the Martian's last ditch effort! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freeze PHP5 at specific version
Recently I discovered that PHP 5.3.x broke my Viart installation. It turned out that ZendOptimizer 3.3.0.a cannot function with PHP 5.3.x. Thus I was forced to downgrade down to PHP5-5.2.12_2. Question: How can I force portupgrade not to upgrade to PHP5-5.3.x? I've tried googling and researching ports management manpages to no avail. I noticed that there's a line for Perl in /etc/make.conf that freezes Perl at a specific version (i.e. PERL_VERSION=5.10.1) but I do not see anything similar to that for PHP5. I must be missing something! I do not know the appropriate search keyword for freezing a port at a specific version. ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: console no responding to key in.
Thanks. I will try to reboot to single user mode, change configuration to enable serial console. Jessie Xu Unix Administrator jessie...@cryptologic.com desk phone: 416 545 1453 x 5618 Skype: Jessie.xu972 -Original Message- From: Polytropon [mailto:free...@edvax.de] Sent: Friday, April 16, 2010 12:50 PM To: Jessie Xu Cc: Chuck Swiger; freebsd-questions@freebsd.org Subject: Re: console no responding to key in. On Fri, 16 Apr 2010 12:20:46 -0400, Jessie Xu jessie...@cryptologic.com wrote: But I have some of consoles did work - response the key in after the keyboard pluged in after. This could be a configuration topic. In /etc/ttys you can intendedly disable consoles (virtual terminals). If this has been the case, trying to login locally won't work. You could try to boot the system from a live CD or DVD to check the configuration. If you can reboot the machines, try to enter into single user mode. In this case, local console login usually is enabled, but it may require the root password. See man 5 ttys for possible details. This is important. Almost all the servers in rack don't have keyboard collected unless we need to login to console. As it has been mentioned, connecting a PS/2 keyboard to a running machine can be a really bad idea - even causing a defect of the PS/2 keyboard connectors. And with USB, you're mostly unlucky on FreeBSD 4 machines due to the lack of kbdmux / automatisms like via devd. I couldn't plug in the keyboard then reboot the server to get access to the console. If configured properly, it should be sufficient to press the power key to initiate a controlled system shutdown. This should give you the chance to try SUM or a live CD. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze PHP5 at specific version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Sampson wrote: Recently I discovered that PHP 5.3.x broke my Viart installation. It turned out that ZendOptimizer 3.3.0.a cannot function with PHP 5.3.x. Thus I was forced to downgrade down to PHP5-5.2.12_2. Question: How can I force portupgrade not to upgrade to PHP5-5.3.x? I've tried googling and researching ports management manpages to no avail. I noticed that there's a line for Perl in /etc/make.conf that freezes Perl at a specific version (i.e. PERL_VERSION=5.10.1) but I do not see anything similar to that for PHP5. I must be missing something! I do not know the appropriate search keyword for freezing a port at a specific version. ~Doug Hi Doug, Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLyKGx0sRouByUApARAn4FAJ96DDcZu/3tcACFePe1BBLitmo4oACgvjpY fT3m2G7AvkAta/PbYmDpOO8= =7Cho -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: downgrade php5
On Thu, Apr 15, 2010 at 10:10 PM, Greg Larkin glar...@freebsd.org wrote: I hope your environment is stable again, and please continue to post with any questions or issues, and we'll do our best to help you resolve them. Thanks for all the info you provided. Currently the environment is stable. Over the next week or so, I will be working with our developers for a plan to move our applications to php 5.3.x doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ACPI? problem with release 8.0 | Perhaps solved?
On Fri, 16 Apr 2010 17:13:48 +0930, Malcolm Kay wrote: My RELEASE-8.0 has now been up for about 2hr, not long enough to be sure the difficulty is circumvented, but long enough to look promising. Previously RELEASE-8.0 has not stayed up more than about 4min. Sounds promising .. I tried setting machdep.idle to acpi and then to hlt without success. But I now have set machdep.idle=spin. Wow, ok. I only have a vague idea of how these work, but having to change this definitely indicates a bug somewhere; whether your BIOS settings or ACPI implementation or kernel or what else, I've no idea. Discovered there can be some problem in trying to set this too early -- in particular in loader.conf -- presumably because acpi.ko is not yet loaded. I ended up making sure everything was ready by putting: Don't presume too easily .. acpi.ko gets loaded really early, it's needed fired up even before scanning busses and initialising most devices. A verbose dmesg.boot should give some indication to anyone familiar with what should be. An acpidump may be useful too. Can you put files up anywhere to fetch? If not, you can mail me them, they're each too big to attach to -questions. The usual deal on acpi@ is to put up URL(s) to such files; I'd be happy to host them here. But you really should take this afresh to acpi@ .. they don't bite, the worst that can happen is they'll ignore you :) and with a new message with the concise story to date, I'd expect someone to take an interest; maybe just to say 'turn this off|on' or or 'that was fixed in -stable last month' or 'try this patch' or 'show us your [whatever]' .. #!/bin/sh echo setting machdep.idle=spin /sbin/sysctl machdep.idle=spin in /etc/rc.local Ok. dmesg.boot then will show what happens before that gets switched. If you enable console.log in syslog.conf that change will show up there after boot messages, maybe other useful stuff, but at least show dmesg. To check what is happening I've created /usr/local/bin/sysctldump.sh as: #!/bin/sh [ -f /tmp/sysctl.dump.4 ] mv -f /tmp/sysctl.dump.4 /tmp/sysctl.dump.5 [ -f /tmp/sysctl.dump.3 ] mv -f /tmp/sysctl.dump.3 /tmp/sysctl.dump.4 [ -f /tmp/sysctl.dump.2 ] mv -f /tmp/sysctl.dump.2 /tmp/sysctl.dump.3 [ -f /tmp/sysctl.dump.1 ] mv -f /tmp/sysctl.dump.1 /tmp/sysctl.dump.2 [ -f /tmp/sysctl.dump ] mv -f /tmp/sysctl.dump /tmp/sysctl.dump.1 sysctl -ao /tmp/sysctl.dump and adding: #sysctl dump 1-59/2 * * * * root /usr/local/bin/sysctldump.sh to /etc/crontab. sysctl -ao is likely Way Too Much Information, though I suppose diffs between them might show something useful changing over time. 'sysctl hw dev acpi' is probably plenty to chew on. I feel somewhat concerned that this cronjob may be sufficiently frequent to prevent the system looking for the idle state and thus circumventing the problem in same other way. So I'm not yet convinced that I have a real solution. We're not talking about idle in the sense top shows you - this is about the kernel having nothing to do for perhaps hundreds of microseconds so entering a microsleep state. The old 386s just had the HLT instruction which had the CPU wait for an interrupt (to save power). These days there are multiple C-states with varying levels of power reduction with different latencies, ie times to wake up, usually managed by ACPI. I suspect 'spin' just loops awaiting an interrupt, staying busy? C1E is one such newer state. I know nothing about it, but that's what your system thought it should use the amdc1e cpufreq? driver for, so your problem definitely seems related to that. This clearly is within the ambit of the acpi@ list, and most of those folks seem rarely to have the sort of spare time needed to follow -questions. Also at least check the change log between your BIOS and the latest; if there's anything related to C states or similar, you should try it; they always say not to do it unless you need to - you might need to, and that might be all you need to do. I'll try removing the cronjob. Thanks again for your attention, Regards, Malcolm Kay Thanks for cc'ing me, I read -digests which can take half a day and make replying a bit tedious, not to mention breaking list threading. cheers, Ian [..] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: freeze PHP5 at specific version
Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Bingo! That is what I'm looking for! Say, do I need to list each PHP5 extension in the HOLD_PKG section? For example, I have the following PHP5 extensions on top of the lang/php5 as follows: corvus-root@/usr/ports/databases/php5-sqlite: portversion -v | g php5 php5-5.2.12_2 needs updating (port has 5.3.2) php5-bcmath-5.2.12_2 needs updating (port has 5.3.2) php5-bz2-5.2.12_2 needs updating (port has 5.3.2) php5-ctype-5.2.12_2 needs updating (port has 5.3.2) php5-curl-5.2.12_2needs updating (port has 5.3.2) php5-dba-5.2.12_2 needs updating (port has 5.3.2) php5-dom-5.2.12_2 needs updating (port has 5.3.2) php5-exif-5.2.12_2needs updating (port has 5.3.2) php5-filter-5.2.12_2 needs updating (port has 5.3.2) php5-ftp-5.2.12_2 needs updating (port has 5.3.2) php5-gd-5.2.12_2 needs updating (port has 5.3.2) php5-gettext-5.2.12_2 needs updating (port has 5.3.2) php5-hash-5.2.12_2needs updating (port has 5.3.2) php5-iconv-5.2.12_2 needs updating (port has 5.3.2) php5-json-5.2.12_2needs updating (port has 5.3.2) php5-mbstring-5.2.12_2needs updating (port has 5.3.2) php5-mcrypt-5.2.12_2 needs updating (port has 5.3.2) php5-mhash-5.2.12_2 = up-to-date with port php5-ncurses-5.2.12_2 = up-to-date with port php5-openssl-5.2.12_2 needs updating (port has 5.3.2) php5-pcre-5.2.12_2 = up-to-date with port php5-pdo-5.2.12_2 needs updating (port has 5.3.2) php5-pdo_sqlite-5.2.12_2 needs updating (port has 5.3.2) php5-pgsql-5.2.12_2 needs updating (port has 5.3.2) php5-posix-5.2.12_2 needs updating (port has 5.3.2) php5-pspell-5.2.12_2 needs updating (port has 5.3.2) php5-readline-5.2.12_2needs updating (port has 5.3.2) php5-session-5.2.12_2 needs updating (port has 5.3.2) php5-simplexml-5.2.12_2 needs updating (port has 5.3.2) php5-soap-5.2.12_2needs updating (port has 5.3.2) php5-sockets-5.2.12_2 needs updating (port has 5.3.2) php5-spl-5.2.12_2 = up-to-date with port php5-sqlite-5.2.12_2 needs updating (port has 5.3.2) php5-tidy-5.2.12_2needs updating (port has 5.3.2) php5-tokenizer-5.2.12_2 needs updating (port has 5.3.2) php5-xml-5.2.12_2 needs updating (port has 5.3.2) php5-xmlreader-5.2.12_2 needs updating (port has 5.3.2) php5-xmlrpc-5.2.12_2 needs updating (port has 5.3.2) php5-xmlwriter-5.2.12_2 needs updating (port has 5.3.2) php5-xsl-5.2.12_2 needs updating (port has 5.3.2) php5-zip-5.2.12_2 needs updating (port has 5.3.2) php5-zlib-5.2.12_2needs updating (port has 5.3.2) corvus-root@/usr/ports/databases/php5-sqlite: Is pkgtools a port that I need to install? Another question: I also use portmaster and portmanager. Does these two tools make use of the /usr/local/etc/pkgtools.conf file? ~Doug ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze PHP5 at specific version
On Fri, 16 Apr 2010 13:43:13 -0400, Greg Larkin glar...@freebsd.org articulated: Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. WOT http://www.mywot.com/en/scorecard/myfreebsd.homeunix.net gives a warning when accessing that site. I assume it is harmless, although I wonder why it is doing it. -- Jerry freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Self Test for Paranoia: You know you have it when you can't think of anything that's your own fault. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Extended VLAN?
On 4/14/2010 1:04 AM, Dan D Niles wrote: I have two FreeBSD routers. I would like both locations to share the 10.10.0.0/16 network. If I were using Cisco routers I would use extended VLANs. How would I do that with FreeBSD routers? I already have a tunnel set up and routing different networks in the 192.168.0.0/16 range. Router A: ifconfig em2 inet 192.168.1.1 netmask 255.255.255.0 ifconfig gif0 create 192.168.1.1 192.168.2.1 netmask 255.255.255.0 tunnelrouterA routerB route add 192.168.2.0/24 129.168.2.1 Router B: ifconfig em2 inet 192.168.2.1 netmask 255.255.255.0 ifconfig gif0 create 192.168.2.1 192.168.1.1 netmask 255.255.255.0 tunnelrouterB routerA route add 192.168.1.0/24 129.168.1.1 This routes traffic between 192.168.1.0/24 and 192.168.2.0/24 as I would expect. The docs say I can use a tunnel with a bridge, which seems like it would do what I want. Router A: ifconfig em3 inet 10.10.1.1 netmask 255.255.0.0 ifconfig bridge0 create addm em3 addm gif0 Router B: ifconfig em3 inet 10.10.2.1 netmask 255.255.0.0 ifconfig bridge0 create addm em3 addm gif0 I cannot ping 10.10.2.1 from router A or 10.10.1.1 from router B. Should I be able to use a bridge this way? Am I missing some piece? If I recall correctly the recommended setup is to assign the IP address to the bridge interface and leave the bridge members unnumbered. These problems you are seeing must be some corner case in FreeBSD's routing and/or ARP subsystems. See if assigning the IP to bridge0 helps Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Extended VLAN?
On 4/14/2010 6:38 PM, Dan D Niles wrote: OK, this is weird. I ran wireshark on the destination side (across the bridge). When I try to ping the destination router, the arp request is sent across the bridge, but there is no arp reply. It seems like the destination router is not responding to arp requests that come in over the bridge. Since the router knows that 10.10.0.0/16 is attached to the em3 interface it sends the ARP reply over that interface and not the gif0 one. That ARP reply does not goes to the other side of the bridge as it should. I don't know the reasoning behind it but I have heard it in the past. Perhaps assigning IP addresses to member interfaces of a bridge is probably bad practice (at least regarding the particular implementation). HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freeze PHP5 at specific version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Sampson wrote: Have a look at this page: http://myfreebsd.homeunix.net/hints_n_kinks/ports-pkgtools.html. If you add the php port names to the HOLD_PKGS array, that prevents portupgrade from touching them. Bingo! That is what I'm looking for! Say, do I need to list each PHP5 extension in the HOLD_PKG section? For example, I have the following PHP5 extensions on top of the lang/php5 as follows: corvus-root@/usr/ports/databases/php5-sqlite: portversion -v | g php5 php5-5.2.12_2 needs updating (port has 5.3.2) [...] corvus-root@/usr/ports/databases/php5-sqlite: Is pkgtools a port that I need to install? Another question: I also use portmaster and portmanager. Does these two tools make use of the /usr/local/etc/pkgtools.conf file? ~Doug Hi Doug, This should work, but please test it to make sure: HOLD_PKGS = [ 'bsdpan-*', 'php5*', ] /usr/local/etc/pkgtools.conf is installed as part of the portupgrade port (ports-mgmt/portupgrade or ports-mgmt/portupgrade-devel). portmaster has a -x option where you can specify a glob, like so: portmaster -x 'php5*' -x 'foobar*' ... I have not tested that either, so experimentat on some throwaway port first. For portmanager, it reads pkgtools.conf for setting port build options, but it looks to me like the pkgtools-to-portmanager.rb script converts the contents of HOLD_PKGS to a form that portmanager understands. Cheers, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLyLA30sRouByUApARApTqAJ9o14/4fv1z5IVYzeKh8jIiGOblIACdHcD1 sdbAUZ4Cz+Nf8yXeW+O2FmM= =sHIe -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Magento
I want to download and develop a Megento website. The published OS requirement is: Supported Operating Systems: * Linux x86, x86-64 Will FreeBSD 8 work for this application? Thanks, Jim __ Jim Bernstorf, EdD Montessori Academy 6021 Cloverland Drive Brentwood, TN 37027 615-833-3610 (Voice) 615-833-0323 (Fax) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Magento
On 4/16/10 9:24 PM, Jim Bernstorf wrote: I want to download and develop a Megento website. The published OS requirement is: Supported Operating Systems: * Linux x86, x86-64 Will FreeBSD 8 work for this application? It will work. I have 2 magento sites on 7.0 and 8.0. It runs perfectly. :) -- Adam PAPAI ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Magento
On Fri, Apr 16, 2010 at 2:24 PM, Jim Bernstorf jimbernst...@montessoriacad.org wrote: I want to download and develop a Megento website. The published OS requirement is: Supported Operating Systems: * Linux x86, x86-64 http://www.freebsd.org/cgi/url.cgi?ports/www/magento/pkg-descr -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Magento
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Bernstorf wrote: I want to download and develop a Megento website. The published OS requirement is: Supported Operating Systems: * Linux x86, x86-64 Will FreeBSD 8 work for this application? Thanks, Jim Hi Jim, Magento was added to the ports tree in March, and you can install it with the following command: cd /usr/ports/www/magento make install clean The FreshPorts page may be useful, too: http://www.freshports.org/www/magento/ Hope that helps, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLyMMf0sRouByUApARAk80AKCnX8el3oBxfaEuRiMw10kZz5tbewCgm9tt xAkj5J/Z8Xx8cpBo834EoeI= =AxAa -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OpenSSL 0.9.8k - 0.9.8l
Tim Gustafson wrote: Hi, I run a few web servers with need to be PCI compliant. Apparently there's a problem with OpenSSL 0.9.8k that requires us to upgrade to 0.9.8l for us to maintain our compliance level. I've csup'd to RELENG_8_0 and did a build/install cycle and OpenSSL is still at 0.9.8k. Using RELENG_8 isn't really an option for me because the last I upgraded to that level, ipfw was broken and I'm not sure that the problem with ipfw has been fixed (Luigi tells me that it has, but I haven't had time to test it yet). Is there any movement to patch RELENG_8_0 with OpenSSL 0.9.8l? Or will I be stuck with 0.9.8k until I move to RELENG_8? Try asking on the freebsd-security@ list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mysql60 port broken? Its 10:00. Do U know where ur mysqlclient.16 is?
On Fri, 16 Apr 2010 08:42:45 -0400, Robert Huff wrote Jerry writes: Question 1) Why can mysqlclient.16 not be found? Could it actually need libmysqlclient.so.16? Question 2) What's up with mysql60-server? Is the port broken? The MySQL60 port has been gone for a while now. I know, because I was in the same boat. Use portupgrade with the -o flag to fix the problem. When this happened to me, I was tolk 5.5 is the line under active development. I (with trepidation) de-installed 6.0, installed 5.5, and everything worked. Of course, I'm using it mainly to learn how; your experience may be different. Robert Huff I installed mysql-client ver. 5.3.2. I'm still trying to compile the php5-mysqli port, and still coming up against the problem: Error: shared library mysqlclient.16 does not exist Interestingly mysqlclient.15 DOES exist. Tried creating a link to it, but no such luck. I also noted that php5's mysql.so also is among the missing. Is the package dependent on mysql 6.0? Maybe I could back up the php and mysqli ports to an earlier version? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
