MRSA...Kill it dead
If you are having trouble viewing this email, [1]click here. 3D [2]3DAliMed® [3]View on Handheld [4]Forward to Friend 3D [alime=] Home =[5]Online Catal= og About Us = ; [6]Contact Us = [7]Help [8]Catalog Requ= est [alime=] 3D [alime=] MRSA-= Fighters [alime=] 3D [9]3DTouchstone On Sale! Touchstone Silver Hand-Sanitizing S= pray Ne= w! Treat hands less often. Innovative, silver-based, safe, gentle, for= mula kills 650+ pathogens longer. Hurry! Limited time trial offer. [10]LEARN MORE 3D _ 3D [11]3DCitrus Only $1.02 Each! Citrus II® Hand-Sanitizin= g Lotion. Us= e anywhere! Needs no water. Economical, moisturizing. Fresh, natural c= itrus scent. Kills in seconds. [12]LEARN MORE 3D _ 3D [13]3DGOJO GOJO® Purell® Bag-In-Box Dispenser Ma= kes it easy to fight disease throughout your facility. Easy-to-refill dispe= nser for water-free, towel-free hand sanitizer. [14]LEARN MORE 3D _ 3D [15]3DCitrus Citrus II® Antibacterial So= ap Ge= ntle, but powerful. Moisturizer-rich with pleasant citrus scent. Unique, pa= tented formula wipes out a broad spectrum of germs. [16] LE= ARN MORE 3D _ 3D [17]= span style= font-family: Arial;...See more infection-control solutions 3D 3D [alime=] AliMe= d eNews: MRSA Bulletin #2 [alime=] 3D 3D 3D 3D 3D TACKLING MRSA THREAT= S: [18]FREQUENT INTERPERSONAL CONTACT The CDC has identifi= ed specific factors that make conditions ideal for the transmission of MRSA= . Whether in healthcare settings, schools, the workplace, prisons/jails or = elsewhere, these Five C's can help MRSA thrive: * Crowding * [19]Frequent Interpersonal Contact * Compromised Skin * Contaminated Items Surface * Lack of Clea= nliness Prevent the spread o= f MRSA in your facility by recognizing when these factors are present and h= aving a clear plan to counter their effects. This week we'll look at how yo= u can tackle the threat of frequent interpersonal contact. [20]= span style= font-family: Arial;LEARN MORE ABOUT FIGHTING MRSA WHERE FR= EQUENT INTERPERSONAL CONTACT IS COMMON 3D 3D 3D 3D 3D [images.a=] AliMe= d Websites [alime=] 3D 3D 3D3D 3D 3D 3D [21]3DAliMed®3D [22]3DAliMed® 3D 3D 3D3D 3D 3D 3D 3D3D 3D 3D 3D 3D3D 3D 3D 3D [23]3DErgobilities.com 3D [24]3DEasierLiving.com 3D 3D 3D3D 3D 3D 3D 3D3D 3D 3D 3D 3D3D 3D 3D 3D [25]3DArista 3D [26]3DPTDirectOnline.com 3D 3D 3D3D 3D 3D 3D [alime=] [27]Add to Address Book |= nbsp; [28]Subscribe | [29]Unsubscribe = font face=Arial, Helvetica, sans-serif color=#FF size=1| [30]Terms Conditions |nbs= p; [31]Privacy Policy | [32]Shipping = Handling [alime=] Copyright©2008 AliMed. All Rights Reserved. AliMed, Inc. 297 High Street Dedham, MA 02026 Th= is is an advertisement. [click?q=375%3B66887911%3BuEwlvdyof=] References 1. =http://alimed.acc0.com/cts/click?q=375%3B66887911%3BCuUZyycWNBvF0mguZ 2. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B668 3. 3Dhttp://a=/ 4. 3Dhttp://a=/ 5. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911 6. 3Dhttp://ali=/ 7. 3Dhttp://alimed.acc0.com/cts/cl 8. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3B 9. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKn 10. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKnmAG3pf6 11. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKn 12. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKnmAG3pf6 13. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKn 14. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKnmAG3pf6 15. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKn 16. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKnmAG3pf6 17. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B668 18. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66887911%3BpKnmAG3pf6 19. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B66 20. 3Dhttp://alimed.acc0.com/cts/click?q=375%3B6 21. 3Dhttp://alimed=/ 22. 3Dhttp://alimed=/ 23. 3Dhttp://alimed=/ 24. 3Dhttp://alimed=/ 25. 3Dhttp://alimed=/ 26. 3Dhttp://alimed=/ 27. 3Dhttp://a=/ 28.
why are older ports built on Sparc64?
Hi! As far as I know, we don't have enough sparc64 horsepower on the build cluster. But still it seems like old ports are build again and again there (and fail), though new versions have fixes. For example, I have two ports failing on sparc64 for which I've submitted fixes: http://portsmon.freebsd.org/portoverview.py?category=gamesportname=blobandconquer and http://portsmon.freebsd.org/portoverview.py?category=graphicsportname=sharpconstruct Both ports were updated on Jan 03 with patches that will (hopefully) fix them on sparc64 with with PORTREVISIONs bumped, still portsmon shows builds failed on Feb 25, and those are old versions of ports. Seems strange to me. -- Dmitry A. Marakasov| jabber: [EMAIL PROTECTED] [EMAIL PROTECTED] | http://www.amdmi3.ru ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
Beech Rintoul-5 wrote: With me the JDK ports stop and demand I manually download the files, which is even more irritating Given Sun's licensing requirements, what is your suggestion? Sorry, having that port just fail seems to be the right thing to do. FWIW, it doesn't hang up portupgrade. Well does it help when you are attempting openoffice.org and the failure of the jdk ports leads to the entire build of the final package itself being called off, thus effectively canceling the night's build anyway. Personally I would like to see all licenses and configuration options resolved at the start of portupgrade (so they are all done in one go) and then followed by the compilation and downloads, that way nothing gets canceled or stalled unless there is a genuine problem -- View this message in context: http://www.nabble.com/interactive-ports---the-plague-tp15800371p15833478.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
I am not sure it would solve the particular problem, but one could take a look at how NetBSDs pkgsrc build system copes with licenses in general: For each license type, there is a knob. The knob could normally be interactive, yielding the exact same behaviour as now. But if an appropriate ACCEPT_LICENSE_FOO=Yes is found in make.conf, then the user has read and accepted that particular license type once and for all. The downside is that this requires a considerable amount of work and thought. What should happen when the license changes, for instance. On Mon, Mar 3, 2008 at 8:57 PM, Mark Linimon [EMAIL PROTECTED] wrote: On Mon, Mar 03, 2008 at 09:12:37AM -0800, pjd wrote: With me the JDK ports stop and demand I manually download the files, which is even more irritating Given Sun's licensing requirements, what is your suggestion? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: why are older ports built on Sparc64?
Both ports were updated on Jan 03 with patches that will (hopefully) fix them on sparc64 with with PORTREVISIONs bumped, still portsmon shows builds failed on Feb 25, and those are old versions of ports. Because sparc64-7 was (is) still, during that time, doing nothing but building the 7.0 release packages, and rebuilding the ones that had been tag-slipped for security updates. They only finally finished yesterday (!) I have restarted the sparc64-6 build I had started and then interrupted when the last security problems showed up. That's got a tree from Feb. 18: http://pointyhat.freebsd.org/errorlogs/packagestats.html mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD-games/Larn is broken in FreeBSD7.0 Release
Dear [EMAIL PROTECTED], I am sorry to bother you but I did not know where else to go for help. I am running FreeBSD 7.0 i386 Release. I have installed FreeBSD-games from both the package and the port and I have the same problem in both. When you run Larn, and chose to read/eat/drink anything the games exits with a signal 11 ,segfaults and does a coredump. You have found a magic potion Do you (d) drink it, (t) take it, or (i) ignore it? Segmentation fault (core dumped) [SIGSEGV]drink I would like to use Larn on 7.0, what do I suggest I do to fix this ? Many thanks for any help you can give me on this. Barry Tigner [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test qemu-devel port update (2008-03-02 snapshot)
Juergen Lock [EMAIL PROTECTED] writes: Anyway the update is here (also queued on tb3): http://people.freebsd.org/~nox/qemu/qemu-devel-20080302.patch I just gave it a test run with a FreeBSD guest, and it seems to work like expected. The curses option is awesome. Now I can run my text mode guests inside screen. :) -- Christian Laursen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: please test qemu-devel port update (2008-03-02 snapshot)
On Sun, Mar 02, 2008 at 09:21:20PM +0100, Juergen Lock wrote: Hi! Again, interesting things are happening in the qemu development tree, among others the ncurses patch has been committed (allowing to see vga text output without sdl by passing -curses), e1000 emulation i.e. an emulated em(4) that should be even faster than the e100 since it also features TSO is now in (-net nic,model=e1000), and qemu is now moving to a new codegenerator called tcg that's supposed to eliminate the gcc3 dependency once everything has been converted to it. Unfortunately, tcg also seems to cause the first regression I've found, qemu-system-x86_64 now makes the 7.0 amd64 isos pagefault in _thread_lock_flags, even tho I've added the cpu-exec.c patch that fixes the hang of the same guests with qemu 0.9.1 (see http://lists.gnu.org/archive/html/qemu-devel/2008-02/msg00334.html ), I'll post a little more about that in a seperate post to the qemu list. (will crosspost to -emulation.) Anyway the update is here (also queued on tb3): http://people.freebsd.org/~nox/qemu/qemu-devel-20080302.patch Updated patch available, fixed the 7.0 amd64 iso faults (indeed it was a tcg bug, I can boot livefs amd64 also on i386 now and enter fixit), and added the gnutls dependency knob that I just commited to the 0.9.1 qemu port too. enjoy, Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Thunderbird, enigmail, and GCC 3.4
Hi, I'd like to call your attention to ports/117285: http://www.freebsd.org/cgi/query-pr.cgi?pr=117285 There seems to be some trouble when thunderbird is compiled with GCC 4.x. The current manifestation of this problem is a segfault on the registration (when thunderbird restarts) of the enigmail extension, which causes the install to fail to register the internal enigmime service. The above PR suggests downgrading thunderbird to GCC 3.4 until the problem is fixed. I don't know how many other extensions are affected by this. Either that, or the security/enigmail-thunderbird port should be modified so that it displays a message warning the user that it won't work after it is installed. AFAICT, it only affects amd64. Maybe USE_GCC can be 3.4 on amd64, and 3.4+ elsewhere? Thoughts? Comments? -- Coleman Kane ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird, enigmail, and GCC 3.4
On Tue, 04 Mar 2008 17:07:19 -0600, Coleman Kane [EMAIL PROTECTED] wrote: Hi, I'd like to call your attention to ports/117285: http://www.freebsd.org/cgi/query-pr.cgi?pr=117285 There seems to be some trouble when thunderbird is compiled with GCC 4.x. The current manifestation of this problem is a segfault on the registration (when thunderbird restarts) of the enigmail extension, which causes the install to fail to register the internal enigmime service. The above PR suggests downgrading thunderbird to GCC 3.4 until the problem is fixed. I don't know how many other extensions are affected by this. Either that, or the security/enigmail-thunderbird port should be modified so that it displays a message warning the user that it won't work after it is installed. AFAICT, it only affects amd64. Maybe USE_GCC can be 3.4 on amd64, and 3.4+ elsewhere? Thoughts? Comments? The enigmail port has to be fix. I disagree to change in thunderbird port to have that USE_GCC. In the past, I have suggested Aryeh M. Friedman to check in Gentoo to see if it can solves his problem, but I don't know if he did. === http://bugs.gentoo.org/show_bug.cgi?id=187353 http://bugs.gentoo.org/attachment.cgi?id=127337action=view Maybe you can try to remove USE_GCC=3.4 and 'make patch' in engimail-thunderbird then go in work directory and remove the gcc_hidden.h and touch this file. After that, try to build engimail-thunderbird to see if it works for you with GCC 4.x. Make sure Thunderbird is built with GCC 4.x too. If it doesn't work for you, there is another bugzilla that is blaming on binutils bug. http://bugs.gentoo.org/show_bug.cgi?id=186089 === Cheers, Mezz -- Coleman Kane -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird, enigmail, and GCC 3.4
Coleman Kane wrote: Hi, I'd like to call your attention to ports/117285: http://www.freebsd.org/cgi/query-pr.cgi?pr=117285 There seems to be some trouble when thunderbird is compiled with GCC 4.x. The current manifestation of this problem is a segfault on the registration (when thunderbird restarts) of the enigmail extension, which causes the install to fail to register the internal enigmime service. The above PR suggests downgrading thunderbird to GCC 3.4 until the problem is fixed. I don't know how many other extensions are affected by this. Either that, or the security/enigmail-thunderbird port should be modified so that it displays a message warning the user that it won't work after it is installed. AFAICT, it only affects amd64. Maybe USE_GCC can be 3.4 on amd64, and 3.4+ elsewhere? Thoughts? Comments? It seems that latest thunderbird gives me signal 8 (SIGFPE) upon extension registration. I am busy at work right now and have no time to investigate this, but building with gcc 3.4 did not worked for me (I've modified both USE_GCC to 3.4, using -CURRENT as of today) :( Cheers, -- Xin LI [EMAIL PROTECTED]http://www.delphij.net/ FreeBSD - The Power to Serve! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-games/Larn is broken in FreeBSD7.0 Release
Hi, 2008/3/5, tigner [EMAIL PROTECTED]: When you run Larn, and chose to read/eat/drink anything the games exits with a signal 11 ,segfaults and does a coredump. You have found a magic potion Do you (d) drink it, (t) take it, or (i) ignore it? Segmentation fault (core dumped) [SIGSEGV]drink I would like to use Larn on 7.0, what do I suggest I do to fix this ? This is caused by the same problem as freebsd-games/hack. Please refer to the thread beginning with http://lists.freebsd.org/pipermail/freebsd-ports/2008-January/046245.html For the temporary solution, edit freebsd-games/files/patch-larn_Makefile to add -fwritable-strings to CFLAGS and do not forget to use gcc34 or earlier instead of gcc in 7.0. Hope this helps. -- Hiroto Kagotani [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-games/Larn is broken in FreeBSD7.0 Release
On Tue, 04 Mar 2008 20:14:18 -0600, Hiroto Kagotani [EMAIL PROTECTED] wrote: Hi, 2008/3/5, tigner [EMAIL PROTECTED]: When you run Larn, and chose to read/eat/drink anything the games exits with a signal 11 ,segfaults and does a coredump. You have found a magic potion Do you (d) drink it, (t) take it, or (i) ignore it? Segmentation fault (core dumped) [SIGSEGV]drink I would like to use Larn on 7.0, what do I suggest I do to fix this ? This is caused by the same problem as freebsd-games/hack. Please refer to the thread beginning with http://lists.freebsd.org/pipermail/freebsd-ports/2008-January/046245.html For the temporary solution, edit freebsd-games/files/patch-larn_Makefile to add -fwritable-strings to CFLAGS and do not forget to use gcc34 or earlier instead of gcc in 7.0. Hope this helps. I believe that someone in DragonFly BSD did a lot of clean up in the src/games/*. But I don't know if these cleans up will helping with this issue. It might be worth for someone to dig in there and bring in FreeBSD if someone care about these games. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thunderbird, enigmail, and GCC 3.4
On Tue, Mar 04, 2008 at 06:07:19PM -0500, Coleman Kane wrote: Hi, I'd like to call your attention to ports/117285: http://www.freebsd.org/cgi/query-pr.cgi?pr=117285 There seems to be some trouble when thunderbird is compiled with GCC 4.x. The current manifestation of this problem is a segfault on the registration (when thunderbird restarts) of the enigmail extension, which causes the install to fail to register the internal enigmime service. The above PR suggests downgrading thunderbird to GCC 3.4 until the problem is fixed. I don't know how many other extensions are affected by this. JFYI: I didn't need to rebuild thunderbird with GCC 3.4 to get enigmail-thunderbird working, just using GCC 3.4 to build enigmail-thunderbird was enough for me. (-CURRENT/amd64) Either that, or the security/enigmail-thunderbird port should be modified so that it displays a message warning the user that it won't work after it is installed. AFAICT, it only affects amd64. Maybe USE_GCC can be 3.4 on amd64, and 3.4+ elsewhere? Thoughts? Comments? -- Coleman Kane Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interactive ports - the plague
On Tue, Mar 04, 2008 at 07:35:29PM +0100, Jesper Louis Andersen wrote: For each license type, there is a knob. The knob could normally be interactive, yielding the exact same behaviour as now. But if an appropriate ACCEPT_LICENSE_FOO=Yes is found in make.conf, then the user has read and accepted that particular license type once and for all. How does this handle click-through agreements where you have to tick a box to agree to the license before the vendor will release the source code? And Sun requires you to login as well. The downside is that this requires a considerable amount of work and thought. What should happen when the license changes, for instance. If a vendor has gone to the effort of implementing a click-through license and the FreeBSD Project implements a tool to bypass it then I would expect that the vendor would become somewhat annoyed. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpZhgjaodqIk.pgp Description: PGP signature
How to add an entry in the ports/UPDATING file?
Hello I need to add an entry in the ports/UPDATING file for one port I maintain (py-mx-experimental), how can I do that? Can I submit a PR for that? Sergio Mangialardi. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to add an entry in the ports/UPDATING file?
Sergio Mangialardi wrote: Hello I need to add an entry in the ports/UPDATING file for one port I maintain (py-mx-experimental), how can I do that? Can I submit a PR for that? I think if you send a diff against UPDATING using send-pr in the usual way it should receive due consideration. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
