The mistake of blender-2.49
I update my ports in Jun. the distinfo of version 1.12 is below MD5 (blender-2.49.tar.gz) = a0f58391ca2554df83375eeaaa8a3fb3 SHA256 (blender-2.49.tar.gz) = 797a9c255b31e62ebc831952dba9149787f0b7c9ab8945948a619eae32d81a15 SIZE (blender-2.49.tar.gz) = 23030434 but, when I download the blender-2.49.tar.gz I found the distinfo is fault. (my url of blender is http://download.blender.org/source/blender-2.49.tar.gz) the md5 code,sha256 code and size of the source file is all fault. I don't know where can I report this,so I send the letter for you. yours Wayne ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why not use normal CONFLICTS in lang/gcc43 instead of custom?
Using the full path will not work too well either with different LOCALBASEs
though I guess one could check /usr/local, $PREFIX, and $LOCALBASE and
consider that good enough.
I think ${LOCALBASE}/bin/gcc295 would be enough. As you say, gcc295 is
dying, while ccache is actively used. It's quite annoying to remove such
check from the Makefile, while I doubt anyone is still going to compile
gcc43 with gcc295 installed in a non-standard location.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: The mistake of blender-2.49
Hi, yes, I can second that. My guess is that the blender crew reviewed the bugs reported for Blender 2.49, and updated the source tarball without changing its version number. The review was to be held on June the 7th, according to the website. But there's no information of its outcome. From what I gathered all known sites have a tarball of the same size: - public.planetmirror.com - mirror.cs.umn.edu - download.blender.org The tarball appears to be fine, though, no error is reported while untaring it, so this should be no case of a truncated upload. I'm currently trying to compile blender with NO_CHECKSUM=yes set. Regards Christian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [Call For Testing] VirtualBox for FreeBSD! take 6
BTW, it seems that the port doesn't do kldxref on /boot/modules after installation (or un-installation). Ditto for the package built from the port. Also, the package (unlike the port) can not install the kld module. It seem that this happens because of the leading / in %%KMODDIR%%. That is, plist (+CONTENTS) expands to: @cwd / /boot/modules/vboxdrv.ko But I think that it should be: @cwd / boot/modules/vboxdrv.ko -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
x11-drivers/input-wacom on FreeBSD 8
Hi, Based on the BROKEN message and the kernel module, I presume that this port has not been adapted for USB2. Do you have any plans to upgrade this port to work with FreeBSD 8.x? -- Peter Jeremy pgp8O18xBA1pV.pgp Description: PGP signature
New 2009 University of Phoenix programs near 55102
3DA You are receiving t= his message because you submitted the email address po...@freebsd.org to receive information from http://www.directscholar.com on Jun 09 2009 07:25AM. [1]Go here to add us to your address= book [2]View in Browser | [3]Unsubscribe style== color:#66; text-decoration:noneRemove My Email This email was sent to you at po...@freebsd.org because you expressed interest in= receiving information about University of Phoenix and/or its educational partners. [4]3DCant [5]3D [6]Dear = John: Perhaps you're new to college and seeking an associate's degree. Maybe you'= re ready to complete your bachelor's or advanced degree. Either way, Univer= sity of Phoenix is here to help. We offer a wide variety of degree programs that meet your needs and interes= ts as a working student in today's workplace. Explore real-world degree programs at Un= iversity of Phoenix. At University of Phoenix, you can choose a learning format that fits your l= ifestyle and learning style. Depending upon the degree program you select, = you can attend classes on campus or online. Some campuses offer a combined = campus-based and online learning format. Find a University of Phoenix degree prog= ram that fits your life today! [7]3D [8]3D If you do not wish to receive informative up= dates about University of Phoenix in the future, simply [9]click here. University of Phoenix is a private institution of higher learning founded i= n Phoenix, Arizona, in 1976. The University is accredited by The Higher Lea= rning Commission and is a member of the North Central Association ([10]ncahlc.org). Axia College is a college of University of Phoenix. [11]Accreditation Thi= s email was sent by: College.us.com 2711 N. Sepulveda Blvd. # 148, Manhattan Beach, CA 90266 You have subscribed to receive information from us with po...@freebsd.org This email was sent to you because you requested we send you periodic= al information about schools and colleges. To stop receiving email from College.us.com, [12]Remove me or write us at the address li= sted above Please view our [13]Privacy Policy [jtdpwcscd_aqrlqjwqrtr.gifo=] References 1. 3Dhttp://www.news.college.us.com/ohngvtbnb_aqrlqjwqrtr_c 2. 3Dhttp://www.news.college.us.com/gbpjqkdph_aqrlqjwqrtr_gbpsjtz 3. 3Dhttp://www.news.col=/ 4. 3Dhttp://www.news.college.us.com/pwkzqptnk_ 5. 3Dhttp://www.news.college.us.com/eswmrhvnn_aqrlqjwqrtr_czpnbqg 6. 3Dhttp://www.news.college.us.com/czpbtdhfd_ 7. 3Dhttp://www.news.college.us.com/kwvlmbwjr_aqrlqjwqrtr_eswtmbc 8. 3Dhttp://www.news.college.us.com/bncmkhpgm_aqrlqjwqrtr_kwvslrk 9. 3Dhttp://w=/ 10. =http://www.news.college.us.com/zrvsbmnfp_aqrlqjwqrtr_tdcjhzbj.html; 11. 3Dhttp://www.news.college.us.com/jtdp 12. 3Dhttp://www.ne=/ 13. 3Dhttp://www.news.college.us.com/bncmkhphk freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
dropping maintainership
Hello, Unfortunately, job and family demands are resulting in a lack of time to properly maintain the following ports, and thus I will need to drop their maintainership: audio/streamripper graphics/mypaint irc/bip multimedia/gpodder If anyone is interested in picking them up, please feel free to do so. Thanks. -- Chess Griffin pgpTdHkNoPykV.pgp Description: PGP signature
Re: dropping maintainership
On Jun 16, 2009, at 8:56 AM, Chess Griffin ch...@chessgriffin.com wrote: audio/streamripper irc/bip I can take these two if not already claimed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Why not use normal CONFLICTS in lang/gcc43 instead of custom?
On Tue, 16 Jun 2009 03:54:18 -0500, Alex Dupre a...@freebsd.org wrote:
Using the full path will not work too well either with different
LOCALBASEs
though I guess one could check /usr/local, $PREFIX, and $LOCALBASE and
consider that good enough.
I think ${LOCALBASE}/bin/gcc295 would be enough. As you say, gcc295 is
dying, while ccache is actively used. It's quite annoying to remove such
check from the Makefile, while I doubt anyone is still going to compile
gcc43 with gcc295 installed in a non-standard location.
Yes, I agree about that ${LOCALBASE}. Either put full path or remove
gcc295 sound good to me.
Cheers,
Mezz
--
me...@cox.net - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
VirtualBox regression in the ports tree
Martin Wilke wrote: ... http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz Happy Testing! This worked perfectly when built and installed under 7.2-STABLE (i386) as of a couple of days ago. I just uninstalled it, and built and installed VirtualBox in the ports tree. My machine paniced when I tried to kldload vboxdrv (running X, so I couldn't see the message(s)). I loaded vboxdrv from the boot loader when rebooting; no problem there, but when I started a virtual machine the virtual console stayed black. The VM itself ran fine, however. I didn't have vboxdrv.ko loaded when doing any of the builds, by the way. I'm now going to try to revert to the previous installation. I'll be happy to run any tests requested; thanks again for all the work! - Rich -- Richard Kuhns Wintek Corporation E-mail: r...@wintek.com 427 N 6th Street STE C Receptionist: 765-742-8428 Lafayette, IN 47901-2211 Direct Line: 765-269-8541 United States of America ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: dropping maintainership
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 16, 2009 09:48:52 am Sahil Tandon wrote: On Jun 16, 2009, at 8:56 AM, Chess Griffin ch...@chessgriffin.com wrote: audio/streamripper irc/bip I can take these two if not already claimed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org Sahil I see streamripper needs and update, claim that one via PR with update, and ping me, I will try claim it and transfer bip at the same time. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAko3p7UACgkQ5Gm/jNBp8qCQEwCeOCWU9nCJY52ZlM800LyPq1Ed 1hUAnjuIjqZwm2UmvDrCXFuosYXxqubb =y8An -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[CFT] GTK frontend for VirtualBox
Hello! For GTK lovers I've created a port for vboxgtk 0.4.1: http://www.logvinov.ru/files/dist/vboxgtk.tar . Sometimes it works. :) 2VBox Team: The latest 0.5.0-beta1 version of vboxgtk wants python bindings for the VirtualBox Python API support. Any chance to get it? -- Best regards, Alexander Logvinov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: dropping maintainership
* Chess Griffin (ch...@chessgriffin.com) wrote: audio/streamripper graphics/mypaint irc/bip multimedia/gpodder If anyone is interested in picking them up, please feel free to do so. I've taken mypaint. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [CFT] GTK frontend for VirtualBox
On Tue, Jun 16, 2009 at 10:45 AM, Alexander Logvinova...@logvinov.com wrote: Hello! For GTK lovers I've created a port for vboxgtk 0.4.1: Great! http://www.logvinov.ru/files/dist/vboxgtk.tar . Sometimes it works. :) Heh. Sometimes. :) 2VBox Team: The latest 0.5.0-beta1 version of vboxgtk wants python bindings for the VirtualBox Python API support. Any chance to get it? -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: VirtualBox regression in the ports tree
On Tue, Jun 16, 2009 at 10:37 AM, Richard Kuhnsr...@wintek.com wrote: Martin Wilke wrote: ... http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz Happy Testing! This worked perfectly when built and installed under 7.2-STABLE (i386) as of a couple of days ago. I just uninstalled it, and built and installed VirtualBox in the ports tree. My machine paniced when I tried to kldload vboxdrv (running X, so I couldn't see the message(s)). Take a look in /var/crash for a 'vmcore.N' dump. If it exists, you can get debugging information by doing: cd /usr/obj/usr/src/sys/MYKERNEL kgdb kernel.debug /var/crash/vmcore.N (replacing 'N' with the latest crash file number). To get the backtrace, type 'bt' in kgdb. Full debugging information can be found at: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html -- Glen Barber ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_libchk: a missing library is not detected
Mel Flynn wrote: On Monday 15 June 2009 02:55:09 Dominic Fandrey wrote: Sorry for the late reply, this was auto-sorted into the ports@ mails and drowned there. Boris Samorodov wrote: As I understand pkg_upgrade does not preserve old libraries at /usr/local/lib/compat? That's true. I consider this common approach a security risk. It is a service interruption to delete libraries that are still used and this can also lead to security problems. However, pkg_upgrade cannot ever hope to fix this problem, because the buildservers do not unconditionally rebuild packages that mention the upgraded port in LIB_DEPENDS, therefore it is better to leave these shared libraries around. To me something not working seems to be less of a security problem than linking to a vulnerable library. To ensure that you get the newest packages wipe /usr/ports/packages/All. Erm, the download time associated with that approach doesn't really speed up things, nor does it guarantee that you will have working binaries if the port maintainer forgot to version bump a port. Well, you don't ever need them again after having them installed once, so I don't see the problem. And at least from pointyhead I've never head broken linking, even when the package was not version bumped, so I think there's some kind of human intervention, or I was lucky. Proper version bumping solves both problems, though and it is rarely forgotten lately. So the issue is much smaller, now than it would have been a couple of years ago. Also I do not see a way for my tool to handle this in any acceptable way. If you've got an idea, go ahead and tell me. I actually want to deal with as many problems as possible without user intervention. It's about making life easier, after all. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: x11-drivers/input-wacom on FreeBSD 8
Peter Jeremy wrote: Hi, Based on the BROKEN message and the kernel module, I presume that this port has not been adapted for USB2. Do you have any plans to upgrade this port to work with FreeBSD 8.x? Bartosh told me he's working on it. But there is nothing like a date for this happening. Additionally the driver also cause problems with Xorg 7.4 for many people (even on RELENG_7), so there's a lot of work to be done on it. I suppose it would be nice if someone comfortable with USB stuff took a look at this. Bartosz told me he hasn't really had a look into the USB2 stuff, yet. He's working on RELENG_7 and the Xorg 7.4 stuff first it seems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: nessus-2.2.9_1
hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [REPOST] problem upgrading perl
Thanks for sending me your response directly. The digest including your response has yet to appear. On Tue, 16 Jun 2009 04:41:49 -0700 Kent Stewart kstew...@owt.com wrote: On Monday 15 June 2009 08:25:59 pm you wrote: I got no responses when I posted this a few days ago, so I'm reposting it now. I'd really like to finish the perl upgrade process, so I could move on to installing/updating other ports safely, but could use some advice. You ask below what part of upgrading perl with portupgrade I didn't understand in the note in /usr/ports/UPGRADING. Given that I had written-- and you quoted-- Following the instructions in /usr/ports/UPDATING for upgrading from ^ lang/perl5.8 to lang/perl5.10 using portmaster, the first part seems to go I'm not sure I see your point. well. The last line of that process is where the excerpt below begins. The second step, as you will see, fails with the error message shown. /usr/ports/UPDATING neglects to mention what to do next, and the process looks incomplete at this point. If someone could offer instructions for completing the process, I would be grateful. === Upgrade of perl-5.8.9_2 to perl-threaded-5.10.0_3 complete hellas# nice +18 portmaster -v -r perl\* What part of 2) Reinstall everything that depends on Perl: portupgrade -fr perl in /usr/ports/UPDATING didn't you understand :). See above. Having begun the process with portmaster, it seemed wise to finish it with portmaster. The note in /usr/ports/UPDATING says, 20090328: AFFECTS: users of lang/perl* AUTHOR: s...@freebsd.org lang/perl5.10 is out. If you want to switch to it from, for example lang/perl5.8, that is: Portupgrade users: 0) Fix pkgdb.db (for safety): pkgdb -Ff 1) Reinstall perl with new 5.10: portupgrade -o lang/perl5.10 -f perl-5.8.\* 2) Reinstall everything that depends on Perl: portupgrade -fr perl Portmaster users: portmaster -o lang/perl5.10 lang/perl5.8 portmaster -r perl\* So there are only two commands in the process, which seem pretty straightforward to understand, but perhaps I've missed something, in which case I'd appreciate someone pointing it out to me. There may be a couple of things causing problems but -v wouldn't force the I generally use -v because I prefer the extra information in the output. upgrade, which is needed. There is a half page set of instructions in UPDATING that tell you what to do with updating perl to version 5.10. I've included the instructions above. In my original posting, I wrote--and you quoted it, as you can see above--that I was following those instructions w.r.t. upgrading perl with portmaster. Go back and search for 20090328. It has the complete sequence of instructions for both portmaster and portupgrade. There are a lot of people that want to do the updates in a more historical manner but this perl update is a really good example of why the new ways are so much better. Which new ways are you referring to? If they are so much better, then why are they not mentioned in the note in /usr/ports/UPDATING? BTW, I also need to do it but there are a lot of ports that depend on perl and they will all be rebuilt. Exactly. If you (or anyone else) can suggest how to proceed from this point in dealing with the process's complaint about a missing ORIGIN, which you omitted, I would appreciate it. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [REPOST] problem upgrading perl
On Mon, Jun 15, 2009 at 10:25:59PM -0500, Scott Bennett wrote: I got no responses when I posted this a few days ago, so I'm reposting it now. I'd really like to finish the perl upgrade process, so I could move on to installing/updating other ports safely, but could use some advice. Following the instructions in /usr/ports/UPDATING for upgrading from lang/perl5.8 to lang/perl5.10 using portmaster, the first part seems to go well. The last line of that process is where the excerpt below begins. The second step, as you will see, fails with the error message shown. /usr/ports/UPDATING neglects to mention what to do next, and the process looks incomplete at this point. If someone could offer instructions for completing the process, I would be grateful. === Upgrade of perl-5.8.9_2 to perl-threaded-5.10.0_3 complete hellas# nice +18 portmaster -v -r perl\* === No ORIGIN in /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS:@comment ORIGIN:lang/perl5.10 /var/db/pkg/perltidy-20071205/+CONTENTS:@comment ORIGIN:devel/perltidy/+CONTENTS === Aborting update The something is wrong with packages database in /var/db/pkg or portmaster doesn't like it. Please, show the output from the following commands to start: head /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS head /var/db/pkg/perltidy-20071205/+CONTENTS Mine is (no perltidy though): ~ head /var/db/pkg/perl-5.10.0_3/+CONTENTS @comment PKG_FORMAT_REVISION:1.1 @name perl-5.10.0_3 @comment ORIGIN:lang/perl5.10 @cwd /usr/local @conflicts perl-5.6.* @conflicts perl-5.8.* @conflicts perl-threaded-5.8.* man/man1/a2p.1.gz @comment MD5:41051bd143f495e113fa136ac0e9cb6f man/man1/c2ph.1.gz Hmmm... Looking at portmaster sources I've got one idea. Can you try more precise command to upgrade everything depending on perl? nice +18 portmaster -v -r perl-threaded-5.10.0_3 The point is that perl\* wildcard gives you both perl-threaded-XXX and perltidy- which might be bad idea. If this is the case I think UPDATING entry should be improved to use perl-\* wildcard. hellas# Please copy me in on any responses. I'm subscribed to the digest form of this list, so responses sent only to the list may take up to a day to be sent to me as part of the digest. Thanks in advance for any assistance in proceeding with the perl upgrade. Just 0.02$, Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
No, there are no further updates as 2.2.9 is the last open source version. Udo On Tue, Jun 16, 2009 at 12:16:54 -0500, phillip.gonza...@metavante.com wrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 - This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [REPOST] problem upgrading perl
=== No ORIGIN in /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS:@comment ORIGIN:lang/perl5.10 /var/db/pkg/perltidy-20071205/+CONTENTS:@comment ORIGIN:devel/perltidy/+CONTENTS === Aborting update Looks something in your /var/db/pkg got corrupted. Fix it or forcibly remove perltidy and rebuild it later. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 Consultant - P6M7G8 Inc.http://p6m7g8.net Senior Sys Admin- RideCharge, Inc. http://ridecharge.com Contractor - PositiveEnergyUSA http://positiveenergyusa.com ASF Member - Apache Software Foundation http://apache.org FreeBSD Committer - FreeBSD Foundation http://freebsd.org Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Nessus 4.0.1 for FreeBSD
Has anyone downloaded this binary distro and gotten it working on FreeBSD? I tried it recently, with disasterous results. It not only didn't work, but it blew up my port install, which now refuses to update the plugins. If someone knows how to get 4.0.1 working on FreeBSD, I'd sure appreciate a brief tutorial. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_libchk: a missing library is not detected
On Tuesday 16 June 2009 07:34:47 Dominic Fandrey wrote: Mel Flynn wrote: On Monday 15 June 2009 02:55:09 Dominic Fandrey wrote: Sorry for the late reply, this was auto-sorted into the ports@ mails and drowned there. Boris Samorodov wrote: As I understand pkg_upgrade does not preserve old libraries at /usr/local/lib/compat? That's true. I consider this common approach a security risk. It is a service interruption to delete libraries that are still used and this can also lead to security problems. However, pkg_upgrade cannot ever hope to fix this problem, because the buildservers do not unconditionally rebuild packages that mention the upgraded port in LIB_DEPENDS, therefore it is better to leave these shared libraries around. To me something not working seems to be less of a security problem than linking to a vulnerable library. Depends what is not working. If it's the monitoring software, do you still agree? Also, a library with a vulnerability does not always constitute an exploitable library for the way a running vital application uses it. Either way, I don't think you should unconditionally interrupt service, because you think yours is the right way. It should be optional and because of your own conviction, you could choose to make the default security over service. To ensure that you get the newest packages wipe /usr/ports/packages/All. Erm, the download time associated with that approach doesn't really speed up things, nor does it guarantee that you will have working binaries if the port maintainer forgot to version bump a port. Well, you don't ever need them again after having them installed once, so I don't see the problem. True I guess for most cases, but if that's true, then why remove them if you're not ever going to download them twice? And at least from pointyhead I've never head broken linking, even when the package was not version bumped, so I think there's some kind of human intervention, or I was lucky. Luck. The app linking to the old library will have a dependency on the old version. pkg_add will find the origin, issue a warning about app-1.0 needing lib-0.1 but lib-0.2 is installed and proceed. app will not start, because of the missing library. Proper version bumping solves both problems, though and it is rarely forgotten lately. So the issue is much smaller, now than it would have been a couple of years ago. Also I do not see a way for my tool to handle this in any acceptable way. If you've got an idea, go ahead and tell me. I actually want to deal with as many problems as possible without user intervention. It's about making life easier, after all. You can't without the buildservers providing hashes for the packages (to detect if a package has been repacked) or in less good case checking lastmod time and size plus the buildservers rebuilding dependents. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: devel/boost-python
Hallo, I've installed graphics/gimp which installed devel/boost. Now I'm trying to install x11/kdebase4* that want devel/boost-python which is in conflict with devel/boost. I don't think I've modified any port options, therefore I'm wondering why the ports fail to install. :-/ What should I do to remedy the situation pls ? Cheers, M. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [REPOST] problem upgrading perl
Scott Bennett wrote: I got no responses when I posted this a few days ago, so I'm reposting it now. I'd really like to finish the perl upgrade process, so I could move on to installing/updating other ports safely, but could use some advice. Following the instructions in /usr/ports/UPDATING for upgrading from lang/perl5.8 to lang/perl5.10 using portmaster, the first part seems to go well. The last line of that process is where the excerpt below begins. The second step, as you will see, fails with the error message shown. /usr/ports/UPDATING neglects to mention what to do next, and the process looks incomplete at this point. If someone could offer instructions for completing the process, I would be grateful. === Upgrade of perl-5.8.9_2 to perl-threaded-5.10.0_3 complete hellas# nice +18 portmaster -v -r perl\* As someone else already pointed out, the -r option can only take one port, so if the glob matches more than one it won't work. Specifying the specific installed port from the directory in /var/db/pkg is the way to go. hope this helps, Doug ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
On Tue, Jun 16, 2009 at 1:39 PM, Schweigert, Udo CERT udo.schweig...@siemens.com wrote: No, there are no further updates as 2.2.9 is the last open source version. Udo On Tue, Jun 16, 2009 at 12:16:54 -0500, phillip.gonza...@metavante.comwrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 You have to go to the nessus website to grab the package now since it's no longer open source ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: pkg_libchk: a missing library is not detected
Mel Flynn wrote: On Tuesday 16 June 2009 07:34:47 Dominic Fandrey wrote: Mel Flynn wrote: On Monday 15 June 2009 02:55:09 Dominic Fandrey wrote: Sorry for the late reply, this was auto-sorted into the ports@ mails and drowned there. Boris Samorodov wrote: As I understand pkg_upgrade does not preserve old libraries at /usr/local/lib/compat? That's true. I consider this common approach a security risk. It is a service interruption to delete libraries that are still used and this can also lead to security problems. However, pkg_upgrade cannot ever hope to fix this problem, because the buildservers do not unconditionally rebuild packages that mention the upgraded port in LIB_DEPENDS, therefore it is better to leave these shared libraries around. To me something not working seems to be less of a security problem than linking to a vulnerable library. Depends what is not working. If it's the monitoring software, do you still agree? Yes I do. Virus scanners and personal firewalls have proven to be security hazards in the past. Any kind of monitoring is as likely to be a gateway to be exploited, especially considering that monitoring software normally has a lot of privileges. Also, a library with a vulnerability does not always constitute an exploitable library for the way a running vital application uses it. Do you have a convincing example? None comes to my mind. Either way, I don't think you should unconditionally interrupt service, because you think yours is the right way. It should be optional and because of your own conviction, you could choose to make the default security over service. Provide an example where it make sense to keep a vulnerable library around and I will add the option to preserve libraries. To ensure that you get the newest packages wipe /usr/ports/packages/All. Erm, the download time associated with that approach doesn't really speed up things, nor does it guarantee that you will have working binaries if the port maintainer forgot to version bump a port. Well, you don't ever need them again after having them installed once, so I don't see the problem. True I guess for most cases, but if that's true, then why remove them if you're not ever going to download them twice? Because you want to download them again if they have been rebuilt without a version change. Something that actually seems to be happening on pointyhead. And at least from pointyhead I've never head broken linking, even when the package was not version bumped, so I think there's some kind of human intervention, or I was lucky. Luck. The app linking to the old library will have a dependency on the old version. pkg_add will find the origin, issue a warning about app-1.0 needing lib-0.1 but lib-0.2 is installed and proceed. app will not start, because of the missing library. I've never had this case. I've got the impression that pointyhead rebuilds all dependencies. Proper version bumping solves both problems, though and it is rarely forgotten lately. So the issue is much smaller, now than it would have been a couple of years ago. Also I do not see a way for my tool to handle this in any acceptable way. If you've got an idea, go ahead and tell me. I actually want to deal with as many problems as possible without user intervention. It's about making life easier, after all. You can't without the buildservers providing hashes for the packages (to detect if a package has been repacked) or in less good case checking lastmod time and size plus the buildservers rebuilding dependents. We've got a PR for this kind of thing around (actually we only request hashes for the INDEX, one step at a time), but I doubt someone is interested in providing this feature. Maybe one day I'll create patches for pointyhead myself, but not before I have done everything that I want to do with pkg_upgrade. There's still so much to be done, it does not yet seem worthwile to invest time into getting to know some else's code, patching it and complaining long enough to get the patches committed. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Possibly unbuildable ports reminder
Bill Fenner wrote: Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! This is about my ports: http://people.freebsd.org/~fenner/errorlogs/kamik...@bsdforen.de-date.html error no. 3: outdated, the port has long since been moved and updated error no. 2: cannot reproduce, I have a dim memory of an error like this, I think it got fixed a long time ago error no. 1: there's no error message in the log, it builds fine on my 7.2-stable/amd64 system ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
On Tue, Jun 16, 2009 at 07:07:12PM -0400, matt donovan wrote: On Tue, Jun 16, 2009 at 1:39 PM, Schweigert, Udo CERT udo.schweig...@siemens.com wrote: No, there are no further updates as 2.2.9 is the last open source version. Udo On Tue, Jun 16, 2009 at 12:16:54 -0500, phillip.gonza...@metavante.comwrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 You have to go to the nessus website to grab the package now since it's no longer open source I don't use nessus myself but just checking their website I see 2.2.11 as the latest open source version. Just 0.02$, Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
On Tue, Jun 16, 2009 at 7:21 PM, Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Tue, Jun 16, 2009 at 07:07:12PM -0400, matt donovan wrote: On Tue, Jun 16, 2009 at 1:39 PM, Schweigert, Udo CERT udo.schweig...@siemens.com wrote: No, there are no further updates as 2.2.9 is the last open source version. Udo On Tue, Jun 16, 2009 at 12:16:54 -0500, phillip.gonza...@metavante.comwrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? thanks for your time, Phillip P Gonzalez Information Security Analyst Sr. Security Analysis and Testing Metavante Corporation tel: 414.357.3156 You have to go to the nessus website to grab the package now since it's no longer open source I don't use nessus myself but just checking their website I see 2.2.11 as the latest open source version. Just 0.02$, Alexey. yes which is out of date anyways might as well just grab the freebsd package ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Nessus 4.0.1 for FreeBSD
--On Tuesday, June 16, 2009 13:17:52 -0500 Paul Schmehl pschmehl_li...@tx.rr.com wrote: Has anyone downloaded this binary distro and gotten it working on FreeBSD? I tried it recently, with disasterous results. It not only didn't work, but it blew up my port install, which now refuses to update the plugins. If someone knows how to get 4.0.1 working on FreeBSD, I'd sure appreciate a brief tutorial. Apparently persistence pays off. After installing (using pkg_add), and had to run nessusd -R twice to fix the plugins dbs so that the daemon would start and run properly. So anyone who's trying to do this, after registering and fetching the plugins, run nessusd -R twice (if it craters the first time, as it did for me) before starting the daemon. After that everything should work as expected. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** Check the headers before clicking on Reply. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Nessus 4.0.1 for FreeBSD
Paul Schmehl wrote: Apparently persistence pays off. After installing (using pkg_add), and had to run nessusd -R twice to fix the plugins dbs so that the daemon would start and run properly. So anyone who's trying to do this, after registering and fetching the plugins, run nessusd -R twice (if it craters the first time, as it did for me) before starting the daemon. After that everything should work as expected. Had this same problem as I'm sure everyone else does. I manually update plugins with nessus-update-plugins and find that after doing so you have to rerun the rebuild (nessusd -R) before restarting. Might be the case after you restart nessus with auto-update enabled?? Anyway, the forums at discussions.nessus.org are the best place for help. --Jason ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: nessus-2.2.9_1
phillip.gonza...@metavante.com wrote: hi, i'm looking at the nessus port on one of my FreeBSD boxes(recently updated ports tree) and it looks like it's at version 2.2.9. has this port not been updated or am i missing something? Abandoned long ago and moved to a closed source version. OpenVAS is the current fork of nessus 2.x. ls -l /usr/ports/security |grep openvas --Jason ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: devel/boost-python
2009/6/16 martinko gam...@users.sf.net: Hallo, I've installed graphics/gimp which installed devel/boost. Now I'm trying to install x11/kdebase4* that want devel/boost-python which is in conflict with devel/boost. I don't think I've modified any port options, therefore I'm wondering why the ports fail to install. :-/ What should I do to remedy the situation pls ? Either uninstall graphics/gimp and devel/boost. First install devel/boost-python then graphics/gimp. Or use either portupgrade or pormaster to replace devel/boost with devel/boost-python: If using portupgrade: # portupgrade -o devel/boost-python devel/boost If using portmaster: # portmaster -o ldevel/boost-python devel/boost Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
New Costa Rica Homes 129,000!
Close to airport, beaches, shopping and health care. Visit: http://wiseinvestcr.com/a4rio3 for more details. Excellent returns. Rich Group SA Calle 3, Avenida 11, 150 metros norte del Banco Nacional San Jose Centro, San Jose, Costa Rica 0 800 0150 6631/877-900-1188 unsubscribe: http://wiseinvestcr.com/unsubscribe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: devel/boost-python
On Tue, 16 Jun 2009 19:34:43 -0500, Scot Hetzel swhet...@gmail.com wrote: 2009/6/16 martinko gam...@users.sf.net: Hallo, I've installed graphics/gimp which installed devel/boost. Now I'm trying to install x11/kdebase4* that want devel/boost-python which is in conflict with devel/boost. I don't think I've modified any port options, therefore I'm wondering why the ports fail to install. :-/ What should I do to remedy the situation pls ? Either uninstall graphics/gimp and devel/boost. First install devel/boost-python then graphics/gimp. You don't need to uninstall gimp. All you have to do is reinstall boost with python option. The fix is on way from boost maintainer and being test. Cheers, Mezz Or use either portupgrade or pormaster to replace devel/boost with devel/boost-python: If using portupgrade: # portupgrade -o devel/boost-python devel/boost If using portmaster: # portmaster -o ldevel/boost-python devel/boost Scot -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Safe to run squid_user=root ?
www/squid30 sets up an rc.d startup script that includes
squid_user=${squid_user:-squid}
This makes it impossible to get squid to listen on a port lower than
1024.
If I specify
squid_user=root
in my rc.conf will I be doing something stupid? Does squid
appropriately drop privileges after binding to a socket?
The background for this is that I want to set up a proxy to listen on
port 70 (yes that is gopher). There is a bit of a move afoot to set
up proxies to allow people from Iran to get to sites like twitter and
facebook which are currently being blocked by the Iranian government.
They have just started blocking things to destination ports like 8080
and 3128.
FreeBSD 7-STABLE, www/squid30
Cheers,
-j
--
Jeffrey Goldberghttp://www.goldmark.org/jeff/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [REPOST] problem upgrading perl
On Tue, 16 Jun 2009 20:07:26 +0200 Alexey Shuvaev shuv...@physik.uni-wuerzburg.de wrote: On Mon, Jun 15, 2009 at 10:25:59PM -0500, Scott Bennett wrote: I got no responses when I posted this a few days ago, so I'm reposting it now. I'd really like to finish the perl upgrade process, so I could move on to installing/updating other ports safely, but could use some advice. Following the instructions in /usr/ports/UPDATING for upgrading from lang/perl5.8 to lang/perl5.10 using portmaster, the first part seems to go well. The last line of that process is where the excerpt below begins. The second step, as you will see, fails with the error message shown. /usr/ports/UPDATING neglects to mention what to do next, and the process looks incomplete at this point. If someone could offer instructions for completing the process, I would be grateful. === Upgrade of perl-5.8.9_2 to perl-threaded-5.10.0_3 complete hellas# nice +18 portmaster -v -r perl\* === No ORIGIN in /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS:@comment ORIGIN:lang/perl5.10 /var/db/pkg/perltidy-20071205/+CONTENTS:@comment ORIGIN:devel/perltidy/+CONTENTS === Aborting update The something is wrong with packages database in /var/db/pkg or portmaster doesn't like it. Please, show the output from the following commands to start: head /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS head /var/db/pkg/perltidy-20071205/+CONTENTS Script started on Tue Jun 16 22:48:33 2009 [hellas] 101 % head /var/db/pkg/perl-threaded-5.10.0_3/+CONTENTS @comment PKG_FORMAT_REVISION:1.1 @name perl-threaded-5.10.0_3 @comment ORIGIN:lang/perl5.10 @cwd /usr/local @pkgdep gdbm-1.8.3_3 @comment DEPORIGIN:databases/gdbm @conflicts perl-5.6.* @conflicts perl-5.8.* @conflicts perl-threaded-5.8.* man/man1/a2p.1.gz [hellas] 102 % head /var/db/pkg/perltidy-20071205/+CONTENTS @comment PKG_FORMAT_REVISION:1.1 @name perltidy-20071205 @comment ORIGIN:devel/perltidy @cwd /usr/local @pkgdep perl-threaded-5.10.0_3 @comment DEPORIGIN:lang/perl5.10 man/man1/perltidy.1.gz @comment MD5:5b629d5917cb885aa24509e40da51b9f lib/perl5/5.8.9/man/man3/Perl::Tidy.3.gz @comment MD5:dcedd0294434f2a88ad1caa048847ce0 [hellas] 103 % exit exit Script done on Tue Jun 16 22:49:49 2009 Mine is (no perltidy though): ~ head /var/db/pkg/perl-5.10.0_3/+CONTENTS @comment PKG_FORMAT_REVISION:1.1 @name perl-5.10.0_3 @comment ORIGIN:lang/perl5.10 @cwd /usr/local @conflicts perl-5.6.* @conflicts perl-5.8.* @conflicts perl-threaded-5.8.* man/man1/a2p.1.gz @comment MD5:41051bd143f495e113fa136ac0e9cb6f man/man1/c2ph.1.gz Hmmm... Looking at portmaster sources I've got one idea. Can you try more precise command to upgrade everything depending on perl? nice +18 portmaster -v -r perl-threaded-5.10.0_3 The point is that perl\* wildcard gives you both perl-threaded-XXX and perltidy- which might be bad idea. Bingo!! Very nice call. It has now driven me to distraction with dialog boxes for configuration stuff for many ports/packages, and is now busily reinstalling perl intself. If this is the case I think UPDATING entry should be improved to use perl-\* wildcard. I think you meant to *not* use the wildcard, and yes, /usr/ports/UPDATING is clearly wrong in this case and should be fixed. Thanks very much for solving this. I still have to deal with some problems with options on the various packages/ports to be updated, but I can proceed for now. Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [Call For Testing] VirtualBox for FreeBSD! take 6
Hi, I've test it on my FreeBSD-7.2p1 amd64 box. I got 2 VirtualBox processes-probrem. but I'd kill 2nd process, then it works fine. So I'd tried to boot FreeBSD-7.2-RELEASE-amd64 installer DVD. loader work fine. but try to launch /stand/sysinstall, it does not work. it stopped ;-( installer's dialogue does not displaied. i386 version was work fine. Thanks. This message was sent using IMP, the Internet Messaging Program. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [Call For Testing] VirtualBox for FreeBSD! take 6
Martin Wilke m...@freebsd.org さんは言われました： -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Huhu, Yes we life and that's good :-). Changes: - Fix build error when compiling in debug mode on FreeBSD HEAD - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite timeout. - Some FreeBSD relate typos - Enable shared OpenGL service. Completely untested due to lack of appropriate hardware but it compiles at least - Add support for shared clipboards. Requires libXt - FreeBSD: Implement preemption API for guest SMP and enable it (slightly tested). Add neccessary RTMP* methods in userspace for the frontends to detect the number of CPUs - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex instead of a spinlock to fix the problems users are seeing (assertions with debugging enabled) while still being able to run on 100Hz hosts. No problems detected so far and Solaris doesn't use a spin mutex in this code too so it shouldn't do any harm (keeping fingers crossed)space for the frontends to detect the number of CPUs - Add support for curl - Add VBoxSharedClipboard Ports Changes; - Force guestadditions version to 2.2.4 - Removed Qt3 include replacements (already upstream) - Removed cosmetic X11 include path patch Please make SURE, your world and kernel is in sync and you've read the pkg-messages. Also please unload the kernel module before you update the port ;-). Many thx to all Vbox Devs, All supporters, my nice team! :-) http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz Happy Testing! - - Martin - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkoxXvUACgkQdLJIhLHm/OmHHQCcCvJ6EKNehym1siBuQICX+7+l i2sAn0InwBQW7jf+l/PqjIM/BR/g3qhi =hDW+ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org This message was sent using IMP, the Internet Messaging Program. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: acroread9 crashes after maybe 10 seconds of operation.
Robert Huff roberth...@rcn.com wrote in 18997.22089.242834.29...@jerusalem.litteratus.org: ro Hiroki Sato writes: ro ro ec Is anyone else seeing the following termination message after maybe 10 ro ec seconds of acroread9 operation? ro roCan you add more detailed information on your environment? Packages royou installed and compat.linux.osrelease sysctl are needed at the rovery least. ro ro compat.linux.osrelease: 2.6.16 ro linux_base-f8-8_11 ro roAcrobat 9 works with compat.linux.osrelease=2.4.2 and rolinux_base-fc-4_13 on 7.2-RELEASE. On other environments it may roor may not work. ro ro Um. ro Are there plans to get it to work with something more recent? ro I was under the (uninformed) impression linux_base-fc-4 was, ah, ro workable but no longer favored. The ports collection still assumes fc4 as the default, so I think it is the primary target. Anyway, I will try other configurations including one in your report. I guess the issue is due to some incomplete (or not-fully-compatible) compat-layer implementations of features available in Linux 2.6.x. -- Hiroki pgpaxT359l0UU.pgp Description: PGP signature
Re: Safe to run squid_user=root ?
2009/6/17 Jeffrey Goldberg jeff...@goldmark.org:
www/squid30 sets up an rc.d startup script that includes
squid_user=${squid_user:-squid}
This makes it impossible to get squid to listen on a port lower than 1024.
If I specify
squid_user=root
in my rc.conf will I be doing something stupid? Does squid appropriately
drop privileges after binding to a socket?
I'm not sure if squid works if you configure it to listen to port 80.
If it won't work, I see three possibilities:
1. use a jail and set squid_user=root (maybe it won't hurt that much
if someone hacks into the proxy)
2. Set up squid with its standard port, and use SSHs port forwarding
feature. This might be done as root. E.g. squid listens to
localhost:3128, and the port forwarding goes to $EXT_IP:70.
3. Use any other unprivileged port that is used by any protocol.
There's a nice list at
http://www.iana.org/assignments/port-numbers
The background for this is that I want to set up a proxy to listen on port
70 (yes that is gopher). There is a bit of a move afoot to set up proxies
to allow people from Iran to get to sites like twitter and facebook which
are currently being blocked by the Iranian government. They have just
started blocking things to destination ports like 8080 and 3128.
Yes, I heard and thinking about setting up a proxy, too. I'm just not
sure that I want to have everyone on the net to be able to access it.
I'm not sure if authentication is an option here, though.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
