Re: firefox[2,3] will not start after recent ports upgrade
On Tuesday 03 February 2009, Daniel Roethlisberger wrote:
Garrett Cooper yanef...@gmail.com 2009-02-02:
On Mon, Feb 2, 2009 at 8:38 AM, Daniel Roethlisberger dan...@roe.ch
wrote:
Alexander Konovalenko k...@kth.se 2009-02-01:
From: Daniel Roethlisberger dan...@roe.ch
...
Could it be the case that firefox-bin hangs in umtxn state?
you're right!
(Check using ps -laux instead of -aux)
http://daemon.nanophys.kth.se/~kono/ktrace_ff2.txt
http://daemon.nanophys.kth.se/~kono/ktrace_ff3.txt
These trace the wrong process: the wrapper shell script (sh).
The actual hanging process would be firefox-bin, not sh. Try
ktracing with child processes (-i).
ktrace -i showed last line:
firefox-bin CALL _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0)
http://daemon.nanophys.kth.se/~kono/ktrace_ff3_ktrace-i.txt
Do you know which port/lib causing this hang on _umtx_op?
Unfortunately, no. I have a box with ports tree from around
mid-January on which I was unable to fix this problem. Native
firefox 2 and 3 hung in umtxn state. So I did pkg_delete -a, rm
-rf /usr/local, rebuilt and installed all ports: now the firefox3
build hangs in umtxn state while running a tool called shlibsign.
No idea how to fix this. I don't want to update the ports tree
to after the unpretty xorg-7.4 changes just yet.
I suspect the problem may be related to upgrading using
freebsd-update from 7.0 to 7.1, but that's just a wild guess
based on the problem appearing after the upgrade; I did make sure
no old leftover libraries or binaries were still lying around.
Have you read UPDATING yet about the libxcb upgrade?
Cheers,
-Garrett
$ fgrep xcb /usr/{ports,src}/UPDATING | wc -l
0
Note that this is a non-current ports tree from before the xorg
7.4 update (mid-January), which used to work fine in the exact
same configuration on RELENG_7_0, but broke on RELENG_7_1. This
is using the version of libxcb committed by miwi in September
2008. The libxcb shlib version bump really cannot be related to
this unless I am very much mistaken.
I upgraded many ports on my office amd64 machine (RELENG_7, 7.1-PRERELEASE
#1: Tue Sep 30 13:26:39 CEST 2008 ) and both firefox23 work now with no
problem. I have libxcb-1.1.93.
/Alexander Konovalenko
___
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: MailScanner-4.67.6_3
Hi, sorry to bother you but I have a question! Are there any plans of upgrading the MailScanner port? Thanks for you time and effort! Cheers, Anders Troback -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: MailScanner-4.67.6_3
On Mon, 2 Feb 2009 22:19:27 +0100 Anders Troback free...@troback.com wrote: Hi, sorry to bother you but I have a question! Are there any plans of upgrading the MailScanner port? You should probably be directing that question to the port maintainer: j.koopm...@seceidos.de -- Jerry ges...@yahoo.com Lots of folks confuse bad management with destiny. Frank Hubbard signature.asc Description: PGP signature
Re: how remove old lib in portupgrade -fr libxcb [SOLVED]
On Mon, 2009-02-02 at 06:46 -0500, Jerry wrote: On Sun, 01 Feb 2009 21:02:17 +0100 Sebastien Chassot si...@fsfe.org wrote: I did another try portupgrade -frP libxcb I believe the 'P' options is causing the problem. Update your ports tree and run it with that option; i.e., portupgrade -fr libxcb as shown in UPDATING. Thank you, it works now. I'll took care with port/package in the future. -- Sebastien ___ 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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Tuesday 03 February 2009 15:05:19 Max Brazhnikov wrote:
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default fonts
and Use anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
I suspect this has something to do with nvidia driver. If one changes the
fonts to bitstream then anti-aliasing does work (but not with the default
fonts).
2. Network Settings doesn't detect anything to do with FreeBSD (it
probably still needs to be told about FreeBSD).
This part surely requires someone who can add support for FreeBSD.
Btw, k...@freebsd team are seeking for developers who would like to improve
KDE4 support for FreeBSD.
Should I file a PR for this, considering there probably isn't enough man-power
to actually resolve it?
3. ksudo does not install?
${KDE$_PREFIX}/lib/kde4/libexec/kdesu
Ask kde devs why kdesu is there.
Please ignore. It appears ksudo or kdesudo is a Kubuntu specific program (why
haven't they pushed the changes upstream?)
4. Samba config module doesn't find smb.conf by default. It should look
in multiple places?
This could be fixed easily I believe.
One the correct place in the code is found, yes it is. See attached. Patch
does compile cleanly and samba config module does not find smb.conf.
Makefile should probably be extended to change the lookup patch if
${LOCALBASE} isn't /usr/local? If so just
# sed -e s|/usr/local/etc/smb.conf|${LOCALBASE}/etc/smb.conf|'
$WRKSRC/kio/kio/ksambashare.cpp
I have also filed a PR (bug #183006) with an improved patch.
5. When I was changing desktop effects X froze. It was a once off
thing...
If it reappears I will file a PR.
I'll ping Alex about the status of mysql_embedded. Meantime you can try
ports/128757 for mysql_embedded and ports/130634 for amarok port.
I already have :-). I had a problem with downloading the patch... But once
that was done amarok2 installed fine :-)
The only app now that is really missing is k3b. Grrr... :-(
Regards,
David
signature.asc
Description: This is a digitally signed message part.
RE: FreeBSD Port: MailScanner-4.67.6_3
On Mon, 2 Feb 2009 22:19:27 +0100 Anders Troback free...@troback.com wrote: Hi, sorry to bother you but I have a question! Are there any plans of upgrading the MailScanner port? You should probably be directing that question to the port maintainer: j.koopm...@seceidos.de -- Jerry ges...@yahoo.com Lots of folks confuse bad management with destiny. Frank Hubbard He did and cc’ed to the list ;-) Regards, Johan ___ 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: [Ticket#2009013010000513] FreeBSD Port: rancid-2.3.1_3 / Re: Submit BUG report to FreeBSD for RANCID port with PATCH
Dear All,
Your reques has been Forwarded to the authors.
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882
On Mon, 2 Feb 2009, Network Infrastructure Support wrote:
The following patches, taken from
'http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html' address
some
issues with netscreen firewalls.
Please see inline patches below. Thanks!
Your Ticket-Team
Michael Joyner
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
Forwarded message from Network Infrastructure Support
netw...@otrs.ewc.edu ---
From:
Network Infrastructure Support netw...@otrs.ewc.edu
To:
it-gr...@listserv.ewc.edu
Subject:
[Ticket#200901301513] Submit BUG report to FreeBSD for RANCID port with
PATCH
Created:
01/30/2009 13:11:56
http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html
=
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nlogin.dist nlogin
*** nlogin.dist Fri Jan 30 12:46:12 2009
--- nlogin Fri Jan 30 12:54:43 2009
***
*** 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
! if { $enable } {
! if {[do_enable $enauser $enapasswd]} {
! if { $do_command || $do_script } {
! close; wait
! continue
! }
! }
! }
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
--- 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
! # if { $enable } {
! # if {[do_enable $enauser $enapasswd]} {
! # if { $do_command || $do_script } {
! # close; wait
! # continue
! # }
! # }
! #}
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nrancid.dist nrancid
*** nrancid.dist Fri Jan 30 12:54:49 2009
--- nrancid Fri Jan 30 12:55:01 2009
***
*** 195,204
--- 195,205
if (/^set admin user (\S+) password (\S+) privilege (\S+)$/
$filter_pwds = 1) {
ProcessHistory(ADMIN,,,
!set admin user $1 password removed privilege $3\n);
next;
+ }
ProcessHistory(,,,$_);
}
$found_end=1;
return(1);
}
Your Ticket-Team
Michael Joyner
___
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: [Ticket#2009020210000574] FreeBSD Port: rancid-2.3.1_3 / modification to nlogoin patch to fix hang at password prompt / nlogi [...]
Your request has been forwarded the the author of rancid.
Best Regards,
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882
On Mon, 2 Feb 2009, Network Infrastructure Support wrote:
Created:
02/02/2009 13:37:50
--- nlogin.dist 2009-01-30 12:46:12.0 -0500
+++ nlogin 2009-02-02 13:33:41.0 -0500
@@ -353,21 +353,12 @@
set uprompt_seen 1
exp_continue
}
- @\[^\r\n]+\[Pp]assword: {
+ password: {
# ssh pwd prompt
sleep 1
send $userpswd\r
exp_continue
}
- \[Pp]assword: {
- sleep 1;
- if {$uprompt_seen == 1} {
- send $userpswd\r
- } else {
- send $passwd\r
- }
- exp_continue
- }
$prompt { break; }
}
}
@@ -485,14 +476,14 @@
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
-if { $enable } {
- if {[do_enable $enauser $enapasswd]} {
- if { $do_command || $do_script } {
- close; wait
- continue
- }
- }
-}
+# if { $enable } {
+# if {[do_enable $enauser $enapasswd]} {
+# if { $do_command || $do_script } {
+# close; wait
+# continue
+# }
+# }
+#}
# we are logged in, now figure out the full prompt
send \r
expect {
___
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: A plea or sanity in port options menu
On Mon, Feb 02, 2009 at 03:39:25PM -0500, Bill Moran wrote: In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. This particular example is nonexistent and thus too far from reality. [snip] I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. I don't see any difference here. OpenGL = Open Graphics Library, so your description is redundunt (Use Open Graphics Library graphics library). Well, you can write 'Use Open Graphics Library', but it is again not so much different from 'OpenGL support'. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. As quite a number of other 'bad' option descriptions. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) ^^ Exactly what you are fighting against. [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support ^^^ The above 2 also. [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... Ok let's examine my 4 ports 3 of which do use OPTIONS. x11-toolkits/gtkdatabox: OPTIONS=GLADE Enable libglade2 support off \ GLADEUI Enable glade3 support off /usr/ports/devel/libglade2 cat pkg-descr LibGlade allows GLADE interfaces to be handled at runtime, freeing GUI development from code development. This allows an interface to be changed without requiring a re-compilation. /usr/ports/devel/glade3 cat pkg-descr Glade is a RAD tool to enable quick easy development of user interfaces for GTK+/GNOME. It can generate the C source code needed to create the interfaces designed within Glade's interface editor. Any idea here how to put all these into small line of description field? [RAD = Rapid Application Development, hope you know what GUI is] Do these long descriptions help you? x11-toolkits/slgtkdatabox: OPTIONS=SLGLADE Enable slglade support (run-time) off /usr/ports/devel/slglade cat pkg-descr SLglade is a S-Lang module that provides S-Lang bindings for the libglade library. Used in conjunction with SLgtk, it allows you to design your GUI with Glade (a GTK+ user interface builder), save the interface description in a Glade XML file, and then generate your S-Lang script's graphical interface directly from the XML at runtime. This should reduce the time spent developing SLgtk applications considerably, as it eliminates the tedious job of writing interface-creation code by hand. This is an update for Christopher Stawarz's SLglade module. WWW: http://laurent.perez2.free.fr/comp/slang/modules/modules.html Same here, short version of pkg-descr for slglade??? x11-toolkits/slgtk: OPTIONS=FITS Install gdk-pixbuf FITS image loader off
Re: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
David Naylor wrote:
On Tuesday 03 February 2009 15:05:19 Max Brazhnikov wrote:
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default fonts
and Use anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
I suspect this has something to do with nvidia driver. If one changes the
fonts to bitstream then anti-aliasing does work (but not with the default
fonts).
Have any of you guys been able to get KDE 4.2 to work with the latest
Xorg 7.4 in ports, and the nvidia driver? I'm playing with it here, and
it always seems to crash X right after KDE finishes logging into my
desktop. When I switch to vesa it works just fine.
Using nvidia 180.25, Xorg 7.4, KDE 4.2, etc.
--
Kris Moore
PC-BSD Software
http://www.pcbsd.com
___
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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Tuesday 03 February 2009 18:44:55 Kris Moore wrote:
David Naylor wrote:
On Tuesday 03 February 2009 15:05:19 Max Brazhnikov wrote:
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default
fonts and Use anti-aliasing: Enabled {with sub-pixel rendering
[RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
I suspect this has something to do with nvidia driver. If one changes
the fonts to bitstream then anti-aliasing does work (but not with the
default fonts).
Have any of you guys been able to get KDE 4.2 to work with the latest
Xorg 7.4 in ports, and the nvidia driver? I'm playing with it here, and
it always seems to crash X right after KDE finishes logging into my
desktop. When I switch to vesa it works just fine.
Using nvidia 180.25, Xorg 7.4, KDE 4.2, etc.
I had some problems with Xorg and undefined symbols but that was just for
probing. Another problem I had was my previous xorg.conf didn't work, I
needed to provide BusID in my Device section.
Other then that now everything appears fine. Desktop Effects are working
without glitch. I did have some problems logging in, X/KDE just freezes but
Ctrl-Alt-Backspace and relogin works just fine?
I'm using nvidia-driver-177.80, xorg-7.4 on FreeBSD 7.1 (Nvidia 7600GT x2).
Does you xorg.log say anything useful, have you tried with a new config file
(Xorg -configure, nvidia-settings)?
signature.asc
Description: This is a digitally signed message part.
Re: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
Kris Moore-3 wrote: Have any of you guys been able to get KDE 4.2 to work with the latest Xorg 7.4 in ports, and the nvidia driver? I'm playing with it here, and it always seems to crash X right after KDE finishes logging into my desktop. When I switch to vesa it works just fine. Using nvidia 180.25, Xorg 7.4, KDE 4.2, etc. I managed to install KDE 4.2 with Xorg 7.4 successfully on PC-BSD 7.0.2, I'm using nvidia-driver-177.80 though. One problem is that every time I log into KDE, plasma crashes. There seems to be some configuration problem (from 4.2beta2), because when I delete ~/.kde4/share/config/plasma-appletsrc, it doesn't crash, but looks weird in other ways. And when I delete the whole ~/.kde4, it works perfectly OK. I haven't investigated it further yet.. Anyway, at least it's working. -- Silver -- View this message in context: http://www.nabble.com/Call-for-Testing-KDE-4.2-for-FreeBSD-tp21780360p21815312.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 freebsd-ports-unsubscr...@freebsd.org
Re: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
On Sunday 01 February 2009 23:02:28 Martin Wilke wrote:
Howdy Guys,
The KDE FreeBSD team is happy to announce the first public
Call for Testing for KDE 4.2. Over the past weeks we have
focused on the complex and very time consuming task to get
KDE 4.2 running.
Please read UPDATING-area51 before you start your update.
To get KDE 4.2:
try
svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/
/path/to/area51
More info here:
https://kf.athame.co.uk/access.php
- Martin (on behalf of the KDE FreeBSD team)
Hi,
I'll get started on testing today. I however have this strange desire to
use USB2 (the new USB stack introduced to FreeBSD-Current).
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default fonts
and Use anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
2. Network Settings doesn't detect anything to do with FreeBSD (it
probably still needs to be told about FreeBSD).
This part surely requires someone who can add support for FreeBSD.
Btw, k...@freebsd team are seeking for developers who would like to improve
KDE4 support for FreeBSD.
3. ksudo does not install?
${KDE$_PREFIX}/lib/kde4/libexec/kdesu
Ask kde devs why kdesu is there.
4. Samba config module doesn't find smb.conf by default. It should look
in multiple places?
This could be fixed easily I believe.
5. When I was changing desktop effects X froze. It was a once off thing...
Items 1,2, 4, (5) probably qualify for a PR, can anyone confirm these?
Item 3 probably has something to do with our ports. I really prefer to use
(k)sudo (since ksu doesn't like root without a password). Item 4 should be
fixed with a patch (until upstream comes with a proper solution).
If you wait a few hours I'll see what I can do about providing patches for
items 3, 4.
Welcome!
Is KDE4 happy with USB2 (or to be more precise, is hald happy with USB2
yet)?
I'll try compile hald with USB2. If that doesn't work (i.e. starts taking
100% CPU on a core) then I will not persue the issue. I'm not sure ports
has been converted to handle the base system's libusb20 in -current?
Oh and I am still having problems with HTTPS and proxy. I am going to try
put up a Squid proxy and see if Squid behaves better then WinGate. And I
am hoping Qt 4.5 will fix this proxy/socks problem (if it will hurry up and
get released :-)).
Everything else is looking good :-) and working on the FreeBSD side.
Thanks
David
P.S. Any hope in getting Amarok 2 into ports with KDE 4.2. Last I saw it
was pending on a PR to fix mysql_embedded?
I'll ping Alex about the status of mysql_embedded. Meantime you can try
ports/128757 for mysql_embedded and ports/130634 for amarok port.
Max.
___
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: [Ticket#2009020210000574] FreeBSD Port: rancid-2.3.1_3 / modification to nlogoin patch to fix hang at password prompt / nlogi [...]
Dear Mohacsi Janos,
Thank you!
02/03/2009 11:48 - Mohacsi Janos wrote:
Your request has been forwarded the the author of rancid.
Best Regards,
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882
On Mon, 2 Feb 2009, Network Infrastructure Support wrote:
Created:
02/02/2009 13:37:50
--- nlogin.dist 2009-01-30 12:46:12.0 -0500
+++ nlogin 2009-02-02 13:33:41.0 -0500
@@ -353,21 +353,12 @@
set uprompt_seen 1
exp_continue
}
- @\[^\r\n]+\[Pp]assword: {
+ password: {
# ssh pwd prompt
sleep 1
send $userpswd\r
exp_continue
}
- \[Pp]assword: {
- sleep 1;
- if {$uprompt_seen == 1} {
- send $userpswd\r
- } else {
- send $passwd\r
- }
- exp_continue
- }
$prompt { break; }
}
}
@@ -485,14 +476,14 @@
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt
$cmethod
$cyphertype]} {
continue
}
-if { $enable } {
- if {[do_enable $enauser $enapasswd]} {
- if { $do_command || $do_script } {
- close; wait
- continue
- }
- }
-}
+# if { $enable } {
+# if {[do_enable $enauser $enapasswd]} {
+# if { $do_command || $do_script } {
+# close; wait
+# continue
+# }
+# }
+#}
# we are logged in, now figure out the full prompt
send \r
expect {
Your Ticket-Team
Michael Joyner
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
___
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: [Ticket#2009013010000513] FreeBSD Port: rancid-2.3.1_3 / Re: Submit BUG report to FreeBSD for RANCID port with PATCH
Dear Mohacsi Janos,
Thank you!
02/03/2009 11:48 - Mohacsi Janos wrote:
Dear All,
Your reques has been Forwarded to the authors.
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00 70EF 9882
On Mon, 2 Feb 2009, Network Infrastructure Support wrote:
The following patches, taken from
'http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html'
address some
issues with netscreen firewalls.
Please see inline patches below. Thanks!
Your Ticket-Team
Michael Joyner
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
Forwarded message from Network Infrastructure Support
netw...@otrs.ewc.edu ---
From:
Network Infrastructure Support netw...@otrs.ewc.edu
To:
it-gr...@listserv.ewc.edu
Subject:
[Ticket#200901301513] Submit BUG report to FreeBSD for RANCID port with
PATCH
Created:
01/30/2009 13:11:56
http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html
=
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nlogin.dist nlogin
*** nlogin.dist Fri Jan 30 12:46:12 2009
--- nlogin Fri Jan 30 12:54:43 2009
***
*** 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt
$cmethod
$cyphertype]} {
continue
}
! if { $enable } {
! if {[do_enable $enauser $enapasswd]} {
! if { $do_command || $do_script } {
! close; wait
! continue
! }
! }
! }
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
--- 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt
$cmethod
$cyphertype]} {
continue
}
! # if { $enable } {
! # if {[do_enable $enauser $enapasswd]} {
! # if { $do_command || $do_script } {
! # close; wait
! # continue
! # }
! # }
! #}
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nrancid.dist nrancid
*** nrancid.dist Fri Jan 30 12:54:49 2009
--- nrancid Fri Jan 30 12:55:01 2009
***
*** 195,204
--- 195,205
if (/^set admin user (\S+) password (\S+) privilege (\S+)$/
$filter_pwds = 1) {
ProcessHistory(ADMIN,,,
!set admin user $1 password removed privilege $3\n);
next;
+ }
ProcessHistory(,,,$_);
}
$found_end=1;
return(1);
}
Your Ticket-Team
Michael Joyner
Your Ticket-Team
Michael Joyner
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
___
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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
Kris Moore schrieb:
David Naylor wrote:
On Tuesday 03 February 2009 15:05:19 Max Brazhnikov wrote:
On Tue, 3 Feb 2009 08:31:10 +0200, David Naylor wrote:
On Monday 02 February 2009 12:01:10 David Naylor wrote:
Just finished compiling on FreeBSD 7.1 and have found the following
problems: 1. The fonts are not being anti-aliased? (Using default fonts
and Use anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
man fonts-conf? Never had problems with fonts, can't help here :(
I suspect this has something to do with nvidia driver. If one changes the
fonts to bitstream then anti-aliasing does work (but not with the default
fonts).
Have any of you guys been able to get KDE 4.2 to work with the latest
Xorg 7.4 in ports, and the nvidia driver? I'm playing with it here, and
it always seems to crash X right after KDE finishes logging into my
desktop. When I switch to vesa it works just fine.
Using nvidia 180.25, Xorg 7.4, KDE 4.2, etc.
Have you first installed Xorg and then nvidia-drivers or vice versa?
They install files in the same place, libGLu or whatever...
It's 180.22 btw, I just start compiling on my i386 nvidia box and then
I'll see if it reproduces, may last until tomorrow. Are you loggin in
through kdm, or do you use startx?
Regards,
Dorian
___
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: X drivers depend on Gnome?
On Tue, 03 Feb 2009 13:03:47 -0600, Alex Goncharov
alex-goncha...@comcast.net wrote:
I am trying to disengage from the latest X, and have had reasonable
success in this (thanks to everybody who had made the suggestions!):
1. Got the old (2008.12.23) ports tree and rebuilt the X-based
components as necessary.
2. Restarted my desktop (resulting in a perfect work environment).
3. Got the new (last night) ports tree and rebuilt higher-level
components (e.g. twm and xterm) on the foundation of the old X
core pieces (such as xproto, xorg-server and libxcb).
Going forward, I am going to keep the X core pieces as they are
(e.g. xorg-server-1.4.2,1), and update higher-level ports as I always
did.
I am slowly moving down the X ports dependency stack, trying to
understand what I should leave in a frozen state and what keep
upgrading.
Here I came across something that stunned me: the X drivers depend on
Gnome. E.g.
--
$ pwd; make -V _DEPEND_DIRS; pkg_which /usr/ports/devel/pkg-config
/usr/ports/x11-drivers/xf86-video-nv
. /usr/ports/x11/xproto /usr/ports/devel/pkg-config
--
The pkg-config is not GNOME. Even the GTK+2 is not GNOME. By the way, why
don't you check the size of pkg-config. I am VERY surpised about that you
are whining over it.
Which is explained by:
--
$ grep XORG_CAT Makefile
XORG_CAT= driver
--
and in bsd.xorg.mk we find:
--
# bsd.xorg.mk - Support for X.Org ports and dependencies
#
# Created by: Florent Thoumie f...@freebsd.org
#
# !!! Here be dragons !!! (yeah, here as well...)
#
# $FreeBSD: ports/Mk/bsd.xorg.mk,v 1.9 2009/01/23 16:27:14 flz Exp $
. if ${XORG_CAT} == driver
USE_GNOME+= pkgconfig
--
The semantics of USE_GNOME is defined as follows:
# USE_GNOME - A list of the Gnome dependencies the port has (e.g.,
# glib12, gtk12). Implies that the port needs
# Gnome. Implies inclusion of bsd.gnome.mk.
Can you please explain why X drivers need Gnome pieces? (I think it's
wrong.)
Thanks,
-- Alex -- alex-goncha...@comcast.net --
--
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
Re: X drivers depend on Gnome?
,--- You/Jeremy (Tue, 03 Feb 2009 17:19:12 -0600) * | The pkg-config is not GNOME. Even the GTK+2 is not GNOME. | I am VERY surpised about that you are whining over it. In other words, you think that making base X11 blocks (such as drivers and libxcb) depend on Gnome, per this definition in bsd.port.mk: # USE_GNOME - A list of the Gnome dependencies the port has (e.g., # glib12, gtk12). Implies that the port needs Gnome. # Implies inclusion of bsd.gnome.mk. See bsd.gnome.mk # or http://www.FreeBSD.org/gnome/docs/porting.html # for more details. is the right thing, correct? -- Alex -- alex-goncha...@comcast.net -- ___ 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: trying out xfce 4.6 RC1?
Oliver Lehmann schreef: Hi, If someone wants to try out xfce 4.6 RC1 here are my patches: http://people.freebsd.org/~oliver/xfce/xfce-4.5.99.1.diff This one needs to be applied below /usr/ports. With xfce 4.6 there are also 3 new ports. You will find them here: http://people.freebsd.org/~oliver/xfce/xfce-4.5.99.1.tar.gz Please extract this tarball also below /usr/ports. Then deinstall your xfce 4.4 ports, cd into /usr/ports/x11-wm/xfce4 and make install. Any comments welcome.. I get an error when starting up xfce4. I think the problem is that /usr/local/libexec/xfconfd is not run correctly. Both hald and dbus are running at startup, and the environment variable XDG_CONFIG_DIRS is set to /usr/local/etc I first tried portmaster -a after applying the patch and extracting the new ports. When that didn't work, I removed all xfce* ports and reinstalled them, giving the same result. Any ideas? (stale files?) Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) ___ 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: enlightenment-0.16.999.042_1,2
Hi, I'm having some problems with installing the enlightenment-devel port. I posted on FreeBSD forums here: http://forums.freebsd.org/showthread.php?t=1958 thanks -- Sondre Tristan Midttun blodv...@gmail.com ___ 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
X drivers depend on Gnome?
I am trying to disengage from the latest X, and have had reasonable
success in this (thanks to everybody who had made the suggestions!):
1. Got the old (2008.12.23) ports tree and rebuilt the X-based
components as necessary.
2. Restarted my desktop (resulting in a perfect work environment).
3. Got the new (last night) ports tree and rebuilt higher-level
components (e.g. twm and xterm) on the foundation of the old X
core pieces (such as xproto, xorg-server and libxcb).
Going forward, I am going to keep the X core pieces as they are
(e.g. xorg-server-1.4.2,1), and update higher-level ports as I always
did.
I am slowly moving down the X ports dependency stack, trying to
understand what I should leave in a frozen state and what keep
upgrading.
Here I came across something that stunned me: the X drivers depend on
Gnome. E.g.
--
$ pwd; make -V _DEPEND_DIRS; pkg_which /usr/ports/devel/pkg-config
/usr/ports/x11-drivers/xf86-video-nv
. /usr/ports/x11/xproto /usr/ports/devel/pkg-config
--
Which is explained by:
--
$ grep XORG_CAT Makefile
XORG_CAT= driver
--
and in bsd.xorg.mk we find:
--
# bsd.xorg.mk - Support for X.Org ports and dependencies
#
# Created by: Florent Thoumie f...@freebsd.org
#
# !!! Here be dragons !!! (yeah, here as well...)
#
# $FreeBSD: ports/Mk/bsd.xorg.mk,v 1.9 2009/01/23 16:27:14 flz Exp $
. if ${XORG_CAT} == driver
USE_GNOME+= pkgconfig
--
The semantics of USE_GNOME is defined as follows:
# USE_GNOME - A list of the Gnome dependencies the port has (e.g.,
# glib12, gtk12). Implies that the port needs
# Gnome. Implies inclusion of bsd.gnome.mk.
Can you please explain why X drivers need Gnome pieces? (I think it's
wrong.)
Thanks,
-- Alex -- alex-goncha...@comcast.net --
___
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: X drivers depend on Gnome?
On Tue, Feb 3, 2009 at 2:03 PM, Alex Goncharov alex-goncha...@comcast.net wrote: I am slowly moving down the X ports dependency stack, trying to understand what I should leave in a frozen state and what keep upgrading. I know this isn't your real question in this thread, but for what it's worth, I've found that xorg-drivers, xorg-server, and xf86-*, when kept at the 'pkg_add' version provides me with a somewhat stable X. Just thought I'd provide this, in case you were still digging about at all. -- 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
FreeBSD Port: rt-3.8.1_5
Good evening, I'm just curious if you will be updating the 3.8 branch to 3.8.2? I noticed that there are quite a few fixes in 3.8.2. Cheers, -Chris ___ 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
Question about WRKSRC
I maintain the sguil ports; security/sguil-server, security/sguil-sensor and security/sguil-agent. It came to my attention today that the pkg-install script that I've written for the security/sguil-server port fails during package building. (The script works fine when compiling from source.) The problem appears to be related to the location of WRCSRC, which appears to be different than it is when building from source. Am I correct about that? Is WRCSRC different when building packages? If so, is there a way to differentiate programmatically between a port being built from source and one being built from a package? Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ 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: net/samba-libsmbclient fails build
On Thu, 2009-01-29 at 12:22 +1100, David N wrote: 2009/1/27 Da Rock rock_on_the_...@comcen.com.au: I get the following error in this build (make, make install clean): In file included from libsmb/libsmbclient.c:25: include/includes.h:1112: error: conflicting types for 'krb5_set_real_time' /usr/local/include/krb5-protos.h:3486: error: previous declaration of 'krb5_set_real_time' was here I was considering debugging this myself and submitting it to you guys here, but then I looked closer... my question is now where do I submit this kind of info? If not here then let me know where. Cheers FreeBSD laptop1.herveybayaustralia.com.au 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Thu Jan 15 16:27:55 EST 2009 xxx...@laptop1.herveybayaustralia.com.au:/usr/obj/usr/src/sys/GENERIC amd64 ___ 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 try rebuilding it with KRB5_HOME=/usr/local i think you need to do a make clean first and then do make install KRB5_HOME=/usr/local That didn't work. I've narrowed it down to broken Active Directory support, but I haven't been able to debug further- I will post when I get the time to do so. For now my system should start working again properly :) Perhaps, though, someone could add a note in the options that AD support is broken for this port? ___ 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: rt-3.8.1_5
Chris Jones jo...@chrisdavid.ca writes: I'm just curious if you will be updating the 3.8 branch to 3.8.2? I noticed that there are quite a few fixes in 3.8.2. You may try this an submit a followup to the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131167 WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: trying out xfce 4.6 RC1?
Rene Ladan wrote: I get an error when starting up xfce4. I think the problem is that /usr/local/libexec/xfconfd is not run correctly. what is the errormessage you are getting? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ 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: X drivers depend on Gnome?
Quoting Alex Goncharov alex-goncha...@comcast.net (from Tue, 03 Feb 2009 19:30:18 -0500): ,--- You/Jeremy (Tue, 03 Feb 2009 17:19:12 -0600) * | The pkg-config is not GNOME. Even the GTK+2 is not GNOME. | I am VERY surpised about that you are whining over it. In other words, you think that making base X11 blocks (such as drivers and libxcb) depend on Gnome, per this definition in bsd.port.mk: # USE_GNOME - A list of the Gnome dependencies the port has (e.g., # glib12, gtk12). Implies that the port needs Gnome. # Implies inclusion of bsd.gnome.mk. See bsd.gnome.mk # or http://www.FreeBSD.org/gnome/docs/porting.html # for more details. is the right thing, correct? To repeat what mezz said, the X stuff does not depend upon GNOME. The X stuff depends upon pkgconfig. pkgconfig is also used by GNOME. It's a little and useful infrastructure thing. With pkgconfig you can check if software Y is installed, which version it has, which include path you need to compile it, and which libs to link to if you want to use it in your software Z. All it does is to do echo $libs or echo $includes or similar. The benefit is that you as a author of software Y just need a little config file which lists everything, and pkgconfig is responsible for all the common tasks like version check and printing. It also unifies the interface if you need to query for software. It originated in GNOME, but as it is small and light, it is used now in more or less everything. For example openssl uses it too (but unfortunately openssl in the FreeBSD base system does not install the corresponding config file), but this does not make openssl depend upon GNOME. It just looks to you like GNOME because the config variable in our ports infrastructure is spelled USE_GNOME. This is for historical reasons, it could also be named USE_INFRASTRUCTURE (it automatically adds suitable BUILD_DEPENDS, RUN_DEPENDS and/or LIB_DEPENDS and additional stuff just by adding a keyword). pkgconfig could be extracted from the USE_GNOME stuff, and it could even maintained by someone else than the FreeBSD gnome team, but the FreeBSD gnome team is doing a good job at maintaining it, and there's no benefit in extracting pkgconfig from USE_GNOME. HTH, Alexander. -- Nothing shortens a journey so pleasantly as an account of misfortunes at which the hearer is permitted to laugh. -- Quentin Crisp http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ 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
