Re: to move csup 90 to subversion 91rc
On 02/09/2012 23:43, Darrel wrote:
Hello,
If my csup file looks about like this:
*default host=this_working_mirror
*default base=/var/db
*default prefix=/usr
*default release=cvs tag=RELENG_9_0
*default delete use-rel-suffix
and my machine now has devel/subversion
what is the quickest way to get the new release candidate sources with svn?
Then, can I simply build{w,k}, install{w,k} as before?
I'm not sure if svn can be made to 'take over' a tree of files already
obtained by non-svn means. I believe not. Therefore to get hold of
9.1rc do:
# cd /usr
# mv src src.old
# svn co http://svn.freebsd.org/base/releng/9.1 src
and then later on to update your tree with any changes from upstream:
# svn up
Note: the first time you update from a SVN tree, you'll get a lot of
mergemaster false positives, because the format of the $FreeBSD$ VCS id
string is different. Use of 'mergemaster -F' is recommended.
Et voilà.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: Sharing COM ports to Windows hosts
On 3-9-2012 5:02, Victor Sudakov wrote: Colleagues, There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? Maybe some Windows drivers for hardware console servers (like Moxa) would work with tits etc? Thanks a lot for any advice. If I understand your question correctly, then AFAICT the only way to access serial ports over the network is with a piece of additional hardware, like a terminal server, for instance: http://www.perle.com/products/Terminal-Server.shtml?utm_source=ppcutm_medium=cpcutm_campaign=server Peter -- http://www.boosten.org - Geen virus gevonden in dit bericht. Gecontroleerd door AVG - www.avg.com Versie: 2012.0.2197 / Virusdatabase: 2437/5242 - datum van uitgifte: 09/02/12 ___ 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: Sharing COM ports to Windows hosts
Victor Sudakov v...@mpeks.tomsk.su writes: Hi, There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? Yes, sredird on the FreeBSD box NetDialout from PCMicro on the Windows box. There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? http://en.wikipedia.org/wiki/COM_port_redirector#Open_source_solutions com0com Project's com2tcp may be what you're expecting. Regards Éric Masson -- l'anarchie, c'est pt'etre pas genial comme mode de gouvernement, mais c'est mieux que pas de gouvernement du tout. -+- Kevin in http://www.le-gnu.net -+- Ni Root, ni Maître. -+- ___ 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: Sharing COM ports to Windows hosts
Peter Boosten pe...@boosten.org wrote: On 3-9-2012 5:02, Victor Sudakov wrote: There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? If I understand your question correctly, then AFAICT the only way to access serial ports over the network is with a piece of additional hardware, like a terminal server, for instance: http://www.perle.com/products/Terminal-Server.shtml?utm_source=ppcutm_medium=cpcutm_campaign=server I believe the OP wants to use a FreeBSD machine, that has several serial ports and a network connection, _as_ a terminal server. I can think of no reason why such an arrangement could not be made to work; the question is whether someone has already written the necessary FreeBSD code to accept a telnet/ssh/whatever connection, initiated by a Windows terminal-server driver, and _transparently_ connect the session to a serial port on the FreeBSD machine via tip(1) or some such. (If all that's needed is access from a Windows Command window, it is a simple matter of ssh-ing to the FreeBSD box and then running tip(1).) ___ 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: Sharing COM ports to Windows hosts
per...@pluto.rain.com wrote: There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? If I understand your question correctly, then AFAICT the only way to access serial ports over the network is with a piece of additional hardware, like a terminal server, for instance: http://www.perle.com/products/Terminal-Server.shtml?utm_source=ppcutm_medium=cpcutm_campaign=server I believe the OP wants to use a FreeBSD machine, that has several serial ports and a network connection, _as_ a terminal server. Correct. I can think of no reason why such an arrangement could not be made to work; the question is whether someone has already written the necessary FreeBSD code to accept a telnet/ssh/whatever connection, There are several in the ports collection. Some even implement RFC2217. Some work and some don't. initiated by a Windows terminal-server driver, and _transparently_ connect the session to a serial port on the FreeBSD machine In fact, the question is whether there is a standards compliant (not written for some proprietary hardware terminal server protocol) driver for Windows. Not exactly a FreeBSD question, I know :) -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: Sharing COM ports to Windows hosts
Eric Masson wrote: There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? Yes, sredird on the FreeBSD box NetDialout from PCMicro on the Windows box. Oh, NetDialout is commercial software, but thanks anyway. There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? http://en.wikipedia.org/wiki/COM_port_redirector#Open_source_solutions com0com Project's com2tcp may be what you're expecting. At least it has an example of an RFC 2217 client (COM port to TCP redirector) in its README file. Thanks again, will look at it. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: Sharing COM ports to Windows hosts
On Mon, 3 Sep 2012 10:02:17 +0700, Victor Sudakov wrote: Colleagues, There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? Maybe some Windows drivers for hardware console servers (like Moxa) would work with tits etc? It is _easily_ possible, even though my own experiences do not include doing this with Windows, but with other BSD boxes and even DOS. First you have to enable a serial terminal connection just the same way you handle the virtual terminals in text mode: Edit /etc/ttys and enable the line ttyu0 /usr/libexec/getty std.19200 dialup on secure Now you can connect to that port via a serial cable, using a terminal emulator (for example Kermit). Make sure you have set the proper speed, 19k2 in this example (faster than the default 9k6). See man 5 ttys for examples. If you use a UNIX or Linux client, you can use the cu program. See man cu for details. However, what you need on Windows side is a program that can communicate via serial port. I don't know if such a program is still included in today's modern versions of Windows, but I seem to remember that the 3.11 and 95 versions came with such a program. In worst case, maybe you can use a DOS program like Kermit under Windows? I'm sure the compatibility is restricted, but maybe you can give it a try. http://www.columbia.edu/kermit/mskermit.html Note that I haven't tried this with any recent FreeBSD system. But it _was_ possible with FreeBSD 4 and 5. -- 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: Sharing COM ports to Windows hosts
Polytropon wrote: There is a FreeBSD box with several RS232 ports. Can those ports be accessed by Windows hosts over the network? Actually, does anyone have a success story for such a scenario? There is some software like comms/serialoverip, comms/tits etc but are there any (freeware) Windows virtual COM port drivers compatible therewith? Maybe some Windows drivers for hardware console servers (like Moxa) would work with tits etc? It is _easily_ possible, even though my own experiences do not include doing this with Windows, but with other BSD boxes and even DOS. First you have to enable a serial terminal connection just the same way you handle the virtual terminals in text mode: Edit /etc/ttys and enable the line ttyu0 /usr/libexec/getty std.19200 dialup on secure Sorry, Polytropon, you understood the challenge the wrong way around. Have you ever heard of reverse telnet and reverse ssh (these are terms from the Cisco world though). I am trying to use an existing FreeBSD box as an el cheapo portserver. I don't need to use the Windows box as a serial terminal. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: Wine-fbsd64 updated to 1.5.12 (32bit Wine for 64bit FreeBSD)
OK, I have solved the problem. 1.5.10 is fine for 9.0 RELEASE. 1.5.111.5.12 have the same error on it. After 9.0 RELEASE (9.0 STABLE, etc.), all version is fine. Thanks! 在 2012-9-1 下午11:10，David Naylor naylor.b.da...@gmail.com写道： Hi, Packages [1] for wine-fbsd64-1.5.12 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [4] for nVidia users is now included in the package and is run on installation (if the relevant files are accessible). Please read the installation messages for further information. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.12,1.tbz) = 335ef444a2f6f375dd22cf932b651919 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.12,1.txz) = e06673c4ab9a0bb82a7d48dad5b8877f MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.12,1.txz) = aafe06b15176f810c25cbf708c11aabb [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng [4] The patch is located at /usr/local/share/wine/patch-nvidia.sh ___ 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
Error after upgrading to php 5.4.6
My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ 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: Error after upgrading to php 5.4.6
On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version Disclaimer: http://www.ose.nl/email ___ 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
AUTO: KVVSN Murthy is out of the office. (returning 09/07/2012)
I am out of the office until 09/07/2012. I am unavailable in TDC1 as i am going to CTOV for Roche audit preparation, please coordinate with Mr.KN Rao Mr.K.Siva Prasad for PET related activities in my obsence. Note: This is an automated response to your message freebsd-questions Digest, Vol 431, Issue 1 sent on 9/3/2012 5:30:53 PM. This is the only notification you will receive while this person is away. Disclaimer This message contains legally privileged and/or confidential information. If you are not the intended recipient(s), or employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ___ 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: Sharing COM ports to Windows hosts
Hello. 2012/09/03 14:29:20 +0700 Victor Sudakov v...@mpeks.tomsk.su = To freebsd-questions@freebsd.org : VS There is a FreeBSD box with several RS232 ports. Can those ports be VS accessed by Windows hosts over the network? Actually, does anyone VS have a success story for such a scenario? VS At least it has an example of an RFC 2217 client (COM port to TCP VS redirector) in its README file. Thanks again, will look at it. From what I remember the os/2 smb protocol implementation could share COM ports as easily as LPT ports for printers. I can't remind though if this was for 'printer-only' purposes e. g. output-only, supplied with a mandatory queueing facilities, etc., or not. Who knows if modern smb protocol implementations could do this, too. Depending on a task I think the most interactive user-friendly solution here is a minicom(s) each in its own ssh'ed jail(s). -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: A0E26627 ___ 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: Error after upgrading to php 5.4.6
On Mon, 03 Sep 2012 13:52:45 +0200 Bas Smeelen articulated: On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version I completely removed all traces of PHP from my system, including configuration files, made sure to run make config in each PHP port I intended to install and then installed the latest version of PHP without a single problem. I believe, although I can not prove it, that the problem is not in the PHP port but rather in the update process. Running portmanager with the -p option might take care of some ports not being updated correctly with PHP also. Again, there is nothing wrong with the latest version but rather in the way it is presently running on your system. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Error after upgrading to php 5.4.6
On 09/03/2012 03:23 PM, Jerry wrote: On Mon, 03 Sep 2012 13:52:45 +0200 Bas Smeelen articulated: On 09/03/2012 01:26 PM, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? I had the same issue on a 8.3-STABLE machine. On other machines php is still at 5.4.3 and does not have this problems. On the machine where 5.4.6 gave the problems I completely removed php and installed lang/php53 (5.3.16) which solved the issue If you are using portmaster -b to update ports, then a backup of the previous port will be in /usr/ports/packages and you can reinstall the previous version I completely removed all traces of PHP from my system, including configuration files, made sure to run make config in each PHP port I intended to install and then installed the latest version of PHP without a single problem. I believe, although I can not prove it, that the problem is not in the PHP port but rather in the update process. Running portmanager with the -p option might take care of some ports not being updated correctly with PHP also. Again, there is nothing wrong with the latest version but rather in the way it is presently running on your system. OK thanks voor the insight, I only checked the extensions.ini file after updating I will go ahead and try it the clean way with version 5.4.6 Disclaimer: http://www.ose.nl/email ___ 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
[solved]: to move csup 90 to subversion 91rc
Thanks, Matthew- and especially for mentioning to use -F on the first subsequent run of mergemaster. svn co http://svn.freebsd.org/base/releng/9.1 src For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports or can the most recent ports be run with a release, like this: svn co http://svn.freebsd.org/ports/head ports Someone off of the list recommended something like this: svn co svn://svn.penx.com/base/releng/9.1 /usr/src svn co svn://svn.penx.com/ports/head /usr/ports Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
Darrel levi...@iglou.com writes: Thanks, Matthew- and especially for mentioning to use -F on the first subsequent run of mergemaster. svn co http://svn.freebsd.org/base/releng/9.1 src For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports or can the most recent ports be run with a release, like this: svn co http://svn.freebsd.org/ports/head ports Someone off of the list recommended something like this: svn co svn://svn.penx.com/base/releng/9.1 /usr/src svn co svn://svn.penx.com/ports/head /usr/ports I would expect ports to still be best with head, as I haven't heard anything about branching it. I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. ___ 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: [solved]: to move csup 90 to subversion 91rc
Darrel levi...@iglou.com wrote: For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports 404. There are no branches in the ports, in exactly the same way that there wasn't a RELENG_9 tag you could use in a ports supfile. Head is the only option with ports. On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [solved]: to move csup 90 to subversion 91rc
Matthew Seaman matt...@freebsd.org writes: On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Ah, yes, that makes sense. I hadn't looked higher than the releng part of the path. Is anyone working on documenting this for the cutting edge section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). ___ 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: Error after upgrading to php 5.4.6
On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? Thanks___ 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 try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ 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: [solved]: to move csup 90 to subversion 91rc
Lowell Gilbert writes: Is anyone working on documenting this for the cutting edge section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). That would be hugely appreciated; none of the current references (I'm aware of) carry the imprimitur of the Handbook. 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
Re: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Lowell Gilbert wrote: Matthew Seaman matt...@freebsd.org writes: On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Ah, yes, that makes sense. I hadn't looked higher than the releng part of the path. Is anyone working on documenting this for the cutting edge section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). If you do decide to write a new section, I could possibly offer help on dumbing it down. :) At least with the English version. Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? Since in the past several years I installed minimal fbsd and then used portsnap for ports, so I was not aware that -head was the only option for ports- is that what Lowell was pointing out? It turns out that mergemaster would have been alright in my case, due to .mergemasterrc, I can not recall why this was selected, comments are welcomed: # cat .mergemasterrc FREEBSD_ID=YES VERBOSE=YES AUTO_INSTALL=YES RUN_UPDATES=YES COMP_CONFS=YES PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` DELETE_STALE_RC_FILES=YES Kind regards, Darrel ___ 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: Error after upgrading to php 5.4.6
Hi! After any upgrade of php i'm use one script that was founded on
freebsd.org
$ cd /usr/local/etc/php
$ cat fixphpextorder.sh
#!/bin/sh
# =
# Fix php/extensions.ini order
#
# Script based on the idea and information(s) of
# - http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround
# - http://nerdstock.org/php_extensions
#
# Please copy your original php/extensions.ini to a save place before
# running this script!
#
# There is no guaranty the script is working for you or don't damage
# your system. Use at own Risk!
#
# 2011-04-03 olli hauer
#
# License: BSD
# http://www.freebsd.org/copyright/freebsd-license.html
#
#
# Updates:
# 2011-12-26:
# Make sed expression more explicit.
# Reported by Kartsten Schmidt
#
INI=/usr/local/etc/php/extensions.ini
EXT=session.so fileinfo.so crack.so ssh2.so imagick.so ldap.so
simplexml.so dba.so ctype.so apc.so ftp.so mbstring.so tokenizer.so
filter.so pgsql.so gmp.so mcrypt.so tidy.so xmlwriter.so mhash.so gd.so
ncurses.so readline.so gettext.so iconv.so dbase.so calendar.so exif.so
zlib.so curl.so mailparse.so xmlrpc.so bz2.so sysvmsg.so pdf.so openssl.so
ming.so dom.so hash.so xmlreader.so gnupg.so bcmath.so pcre.so xsl.so
wddx.so memcache.so soap.so spl.so sqlite.so recode.so pdo.so pdo_mysql.so
pdo_sqlite.so mysqli.so mysql.so imap.so sockets.so pspell.so xml.so
if [ ! -e ${INI} ] ; then
echo cannot find ${INI}
exit 1
fi
# cleanup previous run
[ -e ${INI}.new ] rm -f ${INI}.new
cp -f ${INI} ${INI}.work
for e in ${EXT}; do
if egrep -q ^extension=${e} ${INI}.work ; then
echo extension=${e} ${INI}.new
sed -i '' -e /^extension=${e}/d ${INI}.work
fi
done
if [ -s ${INI}.work ]; then
echo ; additional extension(s) not known by $(basename $0) ${INI}.new
# sybase_ct needs to be loaded last.
grep ^extension ${INI}.work | grep -v sybase_ct.so ${INI}.new
grep ^extension=sybase_ct.so ${INI}.work ${INI}.new
AE=1
fi
[ -e ${INI}.work ] rm -f ${INI}.work
if cmp -s ${INI} ${INI}.new ; then
echo No changes found, remove ${INI}.new
rm -f ${INI}.new
AE=0
fi
if [ ${AE} -ne 0 ]; then
cat _EOF
==
New INI is saved as ${INI}.new
Additional extension(s) not known by $(basename $0)
are added to the end of new INI file.
Please review the new INI, and replace it on your own!
Do some Basic tests:
php -V
php -m
php -i
apachectl graceful
...
_EOF
fi
cat _EOF
If the segfault issue is not gone, or you cannot find the issue
- ask on the ports@ mailing list
or
- open a PR:
Synopsys: lang/php5 Segmentation fault.
Additional try debugging with command:
gdb php ./php.core
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/debugging.html
_EOF
Best regards,
Vladimir
Unix Sysadmin
03.09.2012 15:26, Darrell Betts пишет:
My php pages will no longer render in a web browser after upgrading to php
5.4.6. Used port upgrade to do this. Running apache 2.2.22_6.
Checked the error log and this is what I receive
[notice] child pid 38232 exit signal Segmentation fault (11)
This does this on all php pages.
Any idea how to fix this error?
Thanks___
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: [solved]: to move csup 90 to subversion 91rc
On 03/09/2012 19:00, Darrel wrote: Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? Why don't you try it and see? All you'll get is an error message essentially saying 'file not found.' Simply put, there isn't a path ports/releng/9.1 or ports/stable/9 in the FreeBSD SVN repository. Look here if you don't believe me: http://svnweb.freebsd.org/ Click on 'ports' and look at the subdirectories under there. The *only* bit of the SVN repository that follows the branching structure you seem so enamoured of is base -- the system sources. Get that clear in your head, and you will have a much better time of it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Combining netcat with fifos results in stuck queues/sbwait
I was hoping to establish a simple processing server using nc(1). After finding numerous examples of combining netcat with fifos (named pipes) I am unable to establish a reliable setup. E.g. following the example of the canonical netcat server: server: #mkfifo backpipe #nc -l 4242 backpipe | tr -u [:lower:] [:upper:] backpipe client: #mkfifo frontpipe #nc localhost 4242 frontpipe testfile.out #cat testfile.in frontpipe For any non-trivially small testfile I inevitably end up with the processes at both ends stuck in sbwait. I have managed to avoid the stuck condition by setting the TCP buffer sizes at both ends: nc -I 2048 -O 1024 with a resulting throughput of ~40kB/s (and a supplementary problem of truncation). There are other oddities, such as not using the fifo on the client end: #nc -I 2048 -O 1024 localhost 4242 testfile.in testfile.out also results in stuck processes. So far I've tried on 8.2/8.3 i386 and amd64. The full implementation is planned to use fifos for input and output along with fd redirection but attempts using that have fared no better. Can anyone provide a secret-sauce recipe for netcat/fifo success? Thanks, Wayne ___ 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: [solved]: to move csup 90 to subversion 91rc
Darrel levi...@iglou.com writes: For ports would it be better to match -fbsd91, like this: svn co http://svn.freebsd.org/ports/releng/9.1 ports On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? No. Since in the past several years I installed minimal fbsd and then used portsnap for ports, so I was not aware that -head was the only option for ports- is that what Lowell was pointing out? Yes. There is never any branching in the ports tree. The latest (i.e., head) version is, at any given time, expected to work for all (then) supported versions of the base system. This is not a change -- this has always been the case, and the current (cvsup-centric) text in the Handbook describes it explicitly. It turns out that mergemaster would have been alright in my case, due to .mergemasterrc, I can not recall why this was selected, comments are welcomed: # cat .mergemasterrc FREEBSD_ID=YES Equivalent to -F. VERBOSE=YES AUTO_INSTALL=YES RUN_UPDATES=YES COMP_CONFS=YES PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` DELETE_STALE_RC_FILES=YES A reasonable set of defaults, although I prefer a little more human interaction on major changes. Why it would have been alright(sic) in your case isn't clear, because you don't describe the alternative, but the manual for mergemaster(8) almost certainly has the answer. ___ 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: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Matthew Seaman wrote: On 03/09/2012 19:00, Darrel wrote: Could I then run: svn co svn://svn.freebsd.org/ports/releng/[ 91 9.1] /usr/ports/ or | and svn co svn://svn.freebsd.org/ports/stable/9 /usr/ports/ ? Why don't you try it and see? All you'll get is an error message essentially saying 'file not found.' After reading so many of your intelligent posts, then I typically default to believing in your methods. To get svn:// to work then the fileserver, i.e., -fbsd9 and at the moment becoming -fbsd91 required service svn added outbound in pf.conf. The gateway is -obsd51 and needed the port number out in pf.conf, since svn is not included in /etc/services. :) Simply put, there isn't a path ports/releng/9.1 or ports/stable/9 in the FreeBSD SVN repository. Look here if you don't believe me: http://svnweb.freebsd.org/ Click on 'ports' and look at the subdirectories under there. The *only* bit of the SVN repository that follows the branching structure you seem so enamoured of is base -- the system sources. Get that clear in your head, and you will have a much better time of it. The releases seem neat to me because fbsd reports to have security officers tracking the specified version. I am not necessarily enamoured with it. I have followed -stable and -current before. I can use portsnap as before, or experiment. I might try: svn co svn://svn.freebsd.org/ports /usr/ports I probably know everything for my purposes at this point. As the fileserver is building, some of the points seem obvious now. Thanks to you and Lowell. Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
stable/9 is the SVN equivalent of RELENG_9 src only, understood now. Thanks, Matthew. Yes. There is never any branching in the ports tree. The latest (i.e., head) version is, at any given time, expected to work for all (then) supported versions of the base system. This is not a change -- this has always been the case, and the current (cvsup-centric) text in the Handbook describes it explicitly. same as nbsd, then. I probably need to read fbsd handbook again It turns out that mergemaster would have been alright in my case, due to .mergemasterrc, I can not recall why this was selected, comments are welcomed: # cat .mergemasterrc FREEBSD_ID=YES Equivalent to -F. VERBOSE=YES AUTO_INSTALL=YES RUN_UPDATES=YES COMP_CONFS=YES PRESERVE_FILES_DIR=/var/tmp/mergemaster/preserved-files-`date +%y%m%d-%H%M%S` DELETE_STALE_RC_FILES=YES A reasonable set of defaults, although I prefer a little more human interaction on major changes. Why it would have been alright(sic) in your case isn't clear, because you don't describe the alternative, but the manual for mergemaster(8) almost certainly has the answer. Hopefully not to have bored you too much, Matthew's mention of -F with mergemaster solved this problem of conversion from csup to svn- yet as you saw it was already in my .mergemasterrc , that is why I wrote that it would have been alright. I like human interaction in every case where it is beneficial. If you want to send some guidance, it is welcomed. Other than that, I will let it be and also study the manual again; i.e. man 8 mergemaster. Kind regards, Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
Darrel levi...@iglou.com writes: On Mon, 3 Sep 2012, Lowell Gilbert wrote: Matthew Seaman matt...@freebsd.org writes: On 03/09/2012 17:29, Lowell Gilbert wrote: I'm not sure whether there's any equivalent to tracking RELENG_9 (as opposed to tracking RELENG_9_1) under the branching scheme being used with subversion. stable/9 is the SVN equivalent of RELENG_9 Ah, yes, that makes sense. I hadn't looked higher than the releng part of the path. Is anyone working on documenting this for the cutting edge section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). If you do decide to write a new section, I could possibly offer help on dumbing it down. :) At least with the English version. http://www.freebsd.org/cgi/query-pr.cgi?pr=171292 I don't think dumbing it down is an issue. What I may have left out that beginners wouldn't think of... more of a concern. ___ 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: [solved]: to move csup 90 to subversion 91rc
Is anyone working on documenting this for the cutting edge section of the Handbook? I could take a shot at it myself, but I likely couldn't produce anything intelligible for beginners (at least, not before 9.1 is out). If you do decide to write a new section, I could possibly offer help on dumbing it down. :) At least with the English version. http://www.freebsd.org/cgi/query-pr.cgi?pr=171292 I don't think dumbing it down is an issue. What I may have left out that beginners wouldn't think of... more of a concern. I apologize- that comment was intended to be taken with a grain of salt. As I am asking just now changing from csup to svn, it seems like I might have the insight of a beginner in this instance. - considering my file server: It appears that buildkernel is going well. Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. Peace be to you, Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
Darrel writes: Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity.) 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
Re: Sharing COM ports to Windows hosts
Victor Sudakov v...@mpeks.tomsk.su wrote: In fact, the question is whether there is a standards compliant (not written for some proprietary hardware terminal server protocol) driver for Windows. Not exactly a FreeBSD question, I know :) Finding a Windows driver that will work with an existing FreeBSD program is certainly one possible approach. Another, which I understood to be the intent of the original inquiry, is finding a FreeBSD solution that will work with an existing Windows driver. There's surely no reason why a FreeBSD system _can't_ support a protocol originally developed by a hardware terminal server manufacturer, as vpnc does for the Cisco VPN protocol. ___ 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: Error after upgrading to php 5.4.6
Paul Macdonald wrote: On 03/09/2012 12:26, Darrell Betts wrote: My php pages will no longer render in a web browser after upgrading to php 5.4.6. Used port upgrade to do this. Running apache 2.2.22_6. Checked the error log and this is what I receive [notice] child pid 38232 exit signal Segmentation fault (11) This does this on all php pages. Any idea how to fix this error? [snip] try editing your /usr/local/etc/php/extensions.ini, comment out all extensions (restart apache) and see if it stops seg faulting. If it works, add in the modules one by one until it stops. Previously i've seen people posting about the order being important Some while back I thought portupgrading PHP caused the extensions.ini to be edited after each and every extension rebuild/reinstall, causing a shuffle like effect. Since I do a backup before, including all configs, I got into the habit of just copying my old extensions.ini back into place afterwards prior to restarting PHP and/or web servers. -Mike ___ 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: [solved]: to move csup 90 to subversion 91rc
Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity. Hello Robert, Other than my csup-file, I found these: /home/var.db/sup/src-all/checkouts.cvs:RELENG_9 /home/var.db/sup/src-all/checkouts.cvs:RELENG_9_0 /.snap /home/.snap /home/var.db/portsnap /home/var.db/portsnap/* /tmp/.snap /usr/.snap /var/.snap Also, on my amd64 kernel I had to remove 'device atapicam'. The failed kernel build might be a bug, perhaps I should file a report. Thank you, Darrel ___ 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: [solved]: to move csup 90 to subversion 91rc
On Mon, 3 Sep 2012, Darrel wrote: Next, I will decide whether to keep /usr/ports with portsnap or move ports to svn as well. I just did this (ports and docs) and - modulo an error on my part - it has been remarkably painless. (Make sure you eradicate all vesitges of c(v)sup activity. Hello Robert, Other than my csup-file, I found these: /home/var.db/sup/src-all/checkouts.cvs:RELENG_9 /home/var.db/sup/src-all/checkouts.cvs:RELENG_9_0 /.snap /home/.snap /home/var.db/portsnap /home/var.db/portsnap/* /tmp/.snap /usr/.snap /var/.snap Also, on my amd64 kernel I had to remove 'device atapicam'. The failed kernel build might be a bug, perhaps I should file a report. Thank you, Darrel I found these files as well: /var/db/portsnap/ /var/db/sup/ Darrel ___ 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
