RE: Error while building jdk15 from ports
Dmesg only has standard system info, snip acd0: CDROM TEAC CD-ROM CD-224E-N/3.AB at ata0-master UDMA33 mfi0: 1836 (260622349s/0x0008/0) - Battery temperature is normal mfi0: 1837 (260622349s/0x0008/0) - Current capacity of the battery is above threshold mfid0: MFI Logical Disk on mfi0 mfid0: 138752MB (284164096 sectors) RAID volume 'Virtual Disk 0' is optimal SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/mfid0s1a bce0: link state changed to UP mfi0: 1838 (260679600s/0x0020/0) - Patrol Read started mfi0: 1869 (260680674s/0x0020/0) - Patrol Read complete /snip Rudi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anatoly Borodin Sent: Saturday, April 05, 2008 12:44 AM To: freebsd ports Subject: Re: Error while building jdk15 from ports Hi! On Fri, Apr 4, 2008 at 3:52 PM, Rudi Kramer - MWEB [EMAIL PROTECTED] wrote: gcc: Internal error: Killed: 9 (program cc1plus) Does dmesg say anything about it? -- Mit freundlichen Grüßen, Anatoly Borodin business: [EMAIL PROTECTED] privat: [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: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: On Sun, 2008-04-06 at 23:07 +0530, Ashish Shukla आशीष शुक्ल wrote: Joe Marcus Clarke writes: Joe On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: Hi, Whenever I try to unlock my screen, locked using gnome-screensaver, it doesn't accept my password, rejects with Incorrect password. I'm running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. During password verification, there is some non-uniform delay (sometime more, sometimes less) . Is there anyone else experiencing this issue, hmm...? Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. So, is there a scenario where PAM and gnome-screensaver *do* work? If not, then why is PAM an option? I admit that I don't fully understand PAM, but have noticed that there's a whole bunch of PAM stuff in recent FreeBSD configurations, even at the non-ports level, so I have it in gnome-screensaver, too. I thought that was just how it was supposed to be done. Therefore, whenever I mistakenly allow the screen to be locked, I have to log-in from another machine and kill the screen saver... My FreeBSD system is physically secure, so I don't have it lock automatically when the screen saver comes on, so this only happens when I mis-mouse in the GNOME System menu. So it hasn't bothered me enough to really try debugging it, up to now. (Although I did try to remove the lock screen menu item, but the menu-editing facility did not facilitate that...) Cheers, -- Andrew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Mon, 2008-04-07 at 16:36 +1000, Andrew Reilly wrote: On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: On Sun, 2008-04-06 at 23:07 +0530, Ashish Shukla आशीष शुक्ल wrote: Joe Marcus Clarke writes: Joe On Sun, 2008-04-06 at 15:59 +0530, Ashish Shukla आशीष शुक्ल wrote: Hi, Whenever I try to unlock my screen, locked using gnome-screensaver, it doesn't accept my password, rejects with Incorrect password. I'm running x11/gnome-screensaver-2.22.1 . Any ideas what is causing this ? And BtW, I've compiled gnome-screensaver-2.22.1 with PAM support. During password verification, there is some non-uniform delay (sometime more, sometimes less) . Is there anyone else experiencing this issue, hmm...? Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. So, is there a scenario where PAM and gnome-screensaver *do* work? If not, then why is PAM an option? If you're using a PAM module which doesn't require root privileges (e.g. pam_ldap) then PAM support should work. I admit that I don't fully understand PAM, but have noticed that there's a whole bunch of PAM stuff in recent FreeBSD configurations, even at the non-ports level, so I have it in gnome-screensaver, too. I thought that was just how it was supposed to be done. Therefore, whenever I mistakenly allow the screen to be locked, I have to log-in from another machine and kill the screen saver... My FreeBSD system is physically secure, so I don't have it lock automatically when the screen saver comes on, so this only happens when I mis-mouse in the GNOME System menu. So it hasn't bothered me enough to really try debugging it, up to now. (Although I did try to remove the lock screen menu item, but the menu-editing facility did not facilitate that...) I filed a bug against gnome-screensaver a long time ago (see http://bugzilla.gnome.org/show_bug.cgi?id=370847). I don't see this bug ever being fixed in gnome-screensaver, though. If anyone wants to work on a setuid wrapper which can handle the PAM dialog, I would be happy to integrate it into our port. There already exists support in gnome-screensaver to handle such a wrapper, but since the non-PAM (default) configuration works for me, I haven't been bothered enough to implement this myself. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Mon, Apr 07, 2008 at 04:36:51PM +1000, Andrew Reilly wrote: On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. Just to add a bit more noise to this discussion: I've just re-configured gnome-screensaver to not use PAM, and re-installed. When doing so, I discovered that this installs gnome-screensaver-dialog, which is setuid root. Clearly, that's necessary in order to look at master.passwd directly. Isn't the same setuid-root done when PAM is involved? Cheers, -- Andrew ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
forcibly reinstall one port with portmaster
How can I reinstall just one port without version change? If I did portmaster -f mod_python-3.3.1, portmaster reinstall all dependencies. === The following actions were performed: Re-installation of python25-2.5.2_1 Re-installation of libtool-1.5.24 Re-installation of libiconv-1.11_1 Re-installation of gettext-0.16.1_3 Re-installation of gmake-3.81_2 Re-installation of m4-1.4.9,1 Re-installation of perl-5.8.8_1 Re-installation of p5-gettext-1.05_1 Re-installation of help2man-1.36.4_1 Re-installation of autoconf-wrapper-20071109 Re-installation of autoconf-2.61_2 Re-installation of expat-2.0.0_1 Re-installation of apache-2.2.8 Re-installation of mod_python-3.3.1 (if this is expected behaviour, could it be better documented in man page?) Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Current unassigned ports problem reports
Current FreeBSD problem reports The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. Bugs can be in one of several states: o - open A problem report has been submitted, no sanity checking performed. a - analyzed The problem is understood and a solution is being sought. f - feedback Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution. p - patched A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open. r - repocopy The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion. s - suspended The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended. c - closed A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned. Critical problems S Tracker Resp. Description f ports/122390misc/esniper version update 1 problem total. Serious problems S Tracker Resp. Description o ports/106369vpnd caused kernel panic with ppp mode o ports/106372vpnd can't run with slip mode f ports/108077www/linux-flashplugin9 crashes linux-firefox o ports/108413[patch] net/vnc does not works. o ports/111430[ PATCH ] security/isakmpd with OpenSSL 0.9.8b and new f ports/112921x11-wm/Beryl not loading focus and keybinding settings s ports/113144print/ghostscript-gnu dumps core with several output d o ports/116378xorg 7.3 on -stable breaks math/scilab f ports/116385net/vnc using vnc.so crashes Xorg 7.3 when remote comp f ports/116586net/isc-dhcp3-server does not work when compiled with f ports/116777The math/scilab port fails in demos-signal-bode. f ports/116778security/nmap ping-scan misses some hosts o ports/117025multimedia/pwcbsd: Pwcbsd-1.4.0 + New USBStack not wor o ports/117128security/ipsec-tools racoon.sh fails with /var on mfs o ports/118877audio/streamripper does not detect song title from str f ports/119546net/nss_ldap makes /usr/bin/ssh dump core in getpwuid( o ports/120372java/linux-sun-jdk16: linux-sun-jre1.6.0 plugin doesn' f ports/121346building net/ekiga fails o ports/121473graphics/gsnapshot crashes upon startup on FreeBSD-6.3 f ports/121830net-mgmt/nagios-plugins: check_disk plugin works incor o ports/122030mail/listmanager needs to install listmanager with mai f ports/122083www/mod_clamav refuses to build with apache22 installe o ports/122128Class not found error during print/pdftk port installa f ports/122150devel/libusb port fails to build o ports/122161Update port: multimedia/mpeg_encode Fix for new distfi f ports/122187[patch] security/ipsec-tools failed build on FreeBSD 7 o ports/122251New port: graphics/sK1 An opensource vector graphics e f ports/122276Compiled audio/musicpd segfaults on FreeBSD 7.0 o ports/122306misc/compat5x port fails to extract if you're root o ports/122381net-mgmt/collectd in FreeBSD 7.0 i386 and sparc64 segf f ports/122416deskutils/kmatrix3d and deskutils/ksmoothdock don't in 31 problems total. Non-critical problems S Tracker Resp. Description o ports/85513 Intel C++ compiler not 100% binary compatible with sys o ports/102544ltmdm driver (comms/ltmdm) crashes system whene line r o ports/107354net/icmpinfo: icmpinfo -vvv does not recocnize any ICM f ports/107937jailed net/isc-dhcp3-server wouldn't run with an immut o ports/108795ports/icc: Proposed update to icc port for intel compi o ports/110144New port: math/Matlab7 o ports/110697New port: ports-mgmt/pkg_deps s ports/112887net/nxserver 1.4.0_1 fails to compile after upgrading o ports/113423Update for ports net/freenx to version 0.6.0 o ports/114825pam module security/pam_abl not working s ports/115216ADA devel/florist exit_process program doesn't compile s ports/115217Ada devel/florist socket
FreeBSD Port: tikiwiki-1.9.9
Hello When will Tikiwiki be updated to the latest version in the ports tree? Thank you. Med venlig hilsen / Best Regards Søren Christian Aarup IT Consultant Vesterbrogade 121 7th floor 1620 Copenhagen V Denmark T: +45 3690 3060 F: +45 3332 7368 E: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] W: billetkontoret.dk http://www.billetkontoret.dk/ W: Ticket2travel.dk http://www.ticket2travel.dk/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/gnome-screensaver-2.22.1 is not unlocking screen on entry of correct password.
On Mon, 2008-04-07 at 17:07 +1000, Andrew Reilly wrote: On Mon, Apr 07, 2008 at 04:36:51PM +1000, Andrew Reilly wrote: On Sun, Apr 06, 2008 at 01:51:13PM -0400, Joe Marcus Clarke wrote: Joe This is typically the case when one builds gnome-screensaver with PAM Joe support, but they are currently using a PAM module which requires the Joe executable be setuid root (e.g. pam_unix). The only workaround is to Joe rebuild gnome-screensaver without PAM support, or use a different PAM Joe module which does not require root privileges. I've tried copying /etc/pam.d/gdm to /etc/pam.d/gnome-screensaver, but also thats of no use. Any ideas, why is that not working inspite of /usr/local/libexec/gnome-screensaver-dialog being setuid, hmm...? PAM and gnome-screensaver do not work together if you are using pam_unix. Rebuild gnome-screensaver without PAM support, and it will instead read /etc/master.passwd directly to authenticate the user. That will work. Just to add a bit more noise to this discussion: I've just re-configured gnome-screensaver to not use PAM, and re-installed. When doing so, I discovered that this installs gnome-screensaver-dialog, which is setuid root. Clearly, that's necessary in order to look at master.passwd directly. Isn't the same setuid-root done when PAM is involved? The setuid privileges are dropped once initialization is done since GTK+ apps cannot run set[ug]id. If they could, or if gnome-screesaver-dialog was not a GTK+ app, this wouldn't be a problem. That's why a wrapper that actually does the PAM dialog would work here. Linux, on the other hand, includes a setuid tool with Linux PAM which does the privileged work for pam_unix. This means that none of their login apps need to be setuid root. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Wine wine-0.9.59
On Sunday 06 April 2008 09:54:18 Sam Fourman Jr. wrote: I just upgraded to wine-0.9.59 from http://bugs.winehq.org/show_bug.cgi?id=1798, and it seems when I start World Of Warcraft, in full screen my app looses keyboard focus, and the terminal window that I type wine wow.exe in has my keyboard focus. this never happened before in wine-0.9.57. I did some searching on google is this related? http://bugs.winehq.org/show_bug.cgi?id=1798 , in the wine notes for wine 0.9.58 it states that they fixed the keyboard focus bug. but I seem to have caught the bug now. It's best to report this as a regression on the wine-users mailing list or leave a comment on the bug report. There have been quite a few window management changes lately, so instead of a wine bug, it's possible these changes triggered a window manager bug. But either way, it's best to let the wine devs know about this. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mail/up-imapproxy 1.2.6 rc script issue
I just recently upgraded from 1.2.5 and noticed right away the rc script
wouldn't pick the correct location for my configuration file. I had to
re-write the script to get things working correctly.
Here is a copy of my working rc script for the package:
#!/bin/sh
#
# $FreeBSD: ports/mail/up-imapproxy/files/imapproxyd.sh.in,v 1.4
2007/07/21 03:59:50 mbr Exp $
#
# PROVIDE: imapproxyd
# REQUIRE: DAEMON courier_imap_imapd courier_imap_imapd_ssl cyrus_imapd
inetd
# KEYWORD: shutdown
#
# Add the following line to /etc/rc.conf to enable imapproxyd:
#
# imapproxyd_enable (bool): Set YES to enable imapproxyd
# Default is NO
# imapproxyd_conf (file): Set location of conf file.
# Default is /usr/local/etc/imapproxyd.conf
. /etc/rc.subr
name=imapproxyd
rcvar=`set_rcvar`
: ${imapproxyd_enable=NO}
: ${imapproxyd_conf=/usr/local/etc/imapproxyd.conf}
command=/usr/local/sbin/in.imapproxyd
command_args=-f ${imapproxyd_conf}
required_files=/usr/local/etc/imapproxyd.conf
load_rc_config $name
run_rc_command $1
#EOF
---
Cheers!
Jeff
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Python 3.0 port?
On Sun, Apr 06, 2008 at 07:52:58PM -0400, Maxim Khitrov wrote: I realize that it's still in the alpha stage, but is there any chance of getting Python 3.0 into the ports tree? I suggest you email [EMAIL PROTECTED] - that list is dedicated to Python on FreeBSD. -- 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. pgpNMXHtd1n0V.pgp Description: PGP signature
/usr/ports/audio/beep requires /dev/speaker
Just a suggestion that a blurb be put in as part of the post-install of /usr/ports/audio/beep that it requires /dev/speaker. If one tries to run beep without /dev/speaker, beep will error. IIRC, GENERIC doesn't include the device entry for speaker anymore and thus requires one to load the module for speaker via: kldload speaker Once that is done, beep will work as expected. The default permissions for /dev/speaker is 600 as well. Thanks Reuben -- Reuben A. Popp Systems Administrator Information Technology Department East Central College 1+ 636 583 5195 x2480 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
