Re: Suggestion fix for ikiwiki search results
Hi, on the DragonFly ikiwiki, search results include navigational elements, from the parsed markdown output. One example is: http://www.dragonflybsd.org/wiki.cgi?P=dma That's a good fix. The only issue is upgrading ikiwiki, since new versions of search.pm will overwrite this change. The plugin is located at: /usr/pkg/lib/perl5/vendor_perl/5.10.0/IkiWiki/Plugin/search.pm So if our changed version goes in any of: /usr/pkg/lib/perl5/site_perl/5.10.0/i386-dragonfly-thread-multi /usr/pkg/lib/perl5/site_perl/5.10.0 /usr/pkg/lib/perl5/vendor_perl/5.10.0/i386-dragonfly-thread-multi (from perl -V) It should get picked up first, I think. There's a slightly newer version of ikiwiki that should be installed first, though, as there's been a few quick minor releases. If I can't get it upgraded tonight, I'll get it done this weekend.
[Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50]
A new set of pkgsrc packages for 2.5/64-bit 2009Q3 DragonFly have been built. It's coming from pkgbox64 behind Matt's connection, so the actual packages are probably still uploading to avalon, but the build report is here and the logs are here: http://avalon.dragonflybsd.org/reports/20091105.0250/ On a related note, has anyone seen ruse39 on IRC? His machine df.v12.su is not responding via ssh for me, and that's where I was building the 32-bit 2.4 packages. Original Message Subject: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50 From:Charlie Root r...@pkgbox64.dragonflybsd.org Date:Thu, November 5, 2009 7:34 pm To: jus...@shiningsilence.com -- pkgsrc bulk build report DragonFly 2.5.1/x86_64 Compiler: gcc Build start: 2009-11-05 02:50 Build end: 2009-11-06 00:21 Full report: http://avalon.dragonflybsd.org/reports//20091105.0250/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports//20091105.0250/meta/report.bz2 Total number of packages: 8969 Successfully built: 7481 Failed to build: 354 Depending on failed package: 573 Explicitly broken or masked: 497 Depending on masked package:64 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby18-base 269 t...@netbsd.org print/ghostscript115 pkgsrc-us...@netbsd.org lang/ocaml35 a...@netbsd.org lang/mono 29 kef...@netbsd.org graphics/evas 15 ya...@yazzy.org textproc/xerces-c 12 pkgsrc-us...@netbsd.org x11/kdebase-workspace411 ma...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org www/w3m7 uebay...@netbsd.org math/gap 7 c...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/bmp-macpkgsrc-us...@netbsd.org audio/buzztard 1 pkgsrc-us...@netbsd.org audio/csound4pkgsrc-us...@netbsd.org audio/libmusepack 1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/mpg123 8 pkgsrc-us...@netbsd.org audio/py-id3lib pkgsrc-us...@netbsd.org py26-id3lib-0.5.1pkgsrc-us...@netbsd.org py25-id3lib-0.5.1pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/randread gr...@netbsd.org biology/py-mol pkgsrc-us...@netbsd.org py26-mol-0.98nb4 pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/atlc dmcmah...@netbsd.org chat/finch pkgsrc-us...@netbsd.org chat/galepkgsrc-us...@netbsd.org chat/silc-client 1 s...@netbsd.org chat/silc-server s...@netbsd.org chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/conserver pkgsrc-us...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/plptools pkgsrc-us...@netbsd.org cross/h8300-hms-gcc pkgsrc-us...@netbsd.org cross/i386-cygwin32 pkgsrc-us...@netbsd.org cross/i386-linux pkgsrc-us...@netbsd.org cross/i386-mingw32 pkgsrc-us...@netbsd.org cross/i386-msdosdjgpppkgsrc-us...@netbsd.org cross/mipsEEel-netbsdpkgsrc-us...@netbsd.org databases/gnats re...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/php-mssql1 jdole...@netbsd.org php4-mssql-4.4.9 1 jdole...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org devel/electricfence
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50]
On Thu, 5 Nov 2009, jus...@shiningsilence.com wrote: A new set of pkgsrc packages for 2.5/64-bit 2009Q3 DragonFly have been built. It's coming from pkgbox64 behind Matt's connection, so the actual packages are probably still uploading to avalon, but the build report is here and the logs are here: http://avalon.dragonflybsd.org/reports/20091105.0250/ A newbie query here, In DragonFly BSD 2.4.1 release, the build triplet for target system is 'amd64-pc-dragonflybsd'. However, the build.log for gcc44-4 (pkgsrc report above) shows the target system as 'x86_64-unknown-dragonflybsd2.5.1' Usually version numbers are not part of the triplet and unknown is either pc or some such. So, is this the build triplet in the interim as the transition happens to a new moniker ? thanks Saifi.
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50]
In DragonFly BSD 2.4.1 release, the build triplet for target system is 'amd64-pc-dragonflybsd'. However, the build.log for gcc44-4 (pkgsrc report above) shows the target system as 'x86_64-unknown-dragonflybsd2.5.1' Usually version numbers are not part of the triplet and unknown is either pc or some such. So, is this the build triplet in the interim as the transition happens to a new moniker ? Our system says amd64, while pkgsrc says x86-64. Corecode I think may be working to change this...
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50]
On Thu, 5 Nov 2009, jus...@shiningsilence.com wrote: In DragonFly BSD 2.4.1 release, the build triplet for target system is 'amd64-pc-dragonflybsd'. However, the build.log for gcc44-4 (pkgsrc report above) shows the target system as 'x86_64-unknown-dragonflybsd2.5.1' Usually version numbers are not part of the triplet and unknown is either pc or some such. So, is this the build triplet in the interim as the transition happens to a new moniker ? Our system says amd64, while pkgsrc says x86-64. Corecode I think may be working to change this... Justin, thank you for your reply. Yes, Simon mentioned about the change from amd64 - x86_64 What i wanted to highlight was the suffix part ! The system triplet suffix is : dragonflybsd The pkgsrc triplet suffix is : dragonflybsd2.5.1 Usually version numbers eg. 2.5.1 are not part of the triplet as they keep changing. thanks Saifi.
Re: [Fwd: pkgbox64 pkgsrc DragonFly 2.5.1/x86_64 2009-11-05 02:50]
On Thu, 5 Nov 2009, jus...@shiningsilence.com wrote: In DragonFly BSD 2.4.1 release, the build triplet for target system is 'amd64-pc-dragonflybsd'. However, the build.log for gcc44-4 (pkgsrc report above) shows the target system as 'x86_64-unknown-dragonflybsd2.5.1' Usually version numbers are not part of the triplet and unknown is either pc or some such. So, is this the build triplet in the interim as the transition happens to a new moniker ? Our system says amd64, while pkgsrc says x86-64. Corecode I think may be working to change this... Justin, thank you for your reply. Yes, Simon mentioned about the change from amd64 - x86_64 What i wanted to highlight was the suffix part ! The system triplet suffix is : dragonflybsd The pkgsrc triplet suffix is : dragonflybsd2.5.1 Usually version numbers eg. 2.5.1 are not part of the triplet as they keep changing. Something may have changed in how pkgsrc builds it. The bulk building process isn't any different...
ACPI version to set in BIOS
Hi: The BIOS setup utility (v02.58 American Megatrends) provides multiple ACPI versions . ACPI v1.0 . ACPI v2.0 . ACPI v3.0 Currently i've configured ACPI v1.0 while running DragonFly BSD HEAD, but i'd like to know what is the recommended version to setup in BIOS while running DragonFly ? thanks Saifi.
Re: Analysis on make parallelism for buildworld
On Thu, 5 Nov 2009, Simon 'corecode' Schubert wrote: Saifi Khan wrote: Please review and let me know if there is any tweak/correction that you deem necessary. Hey! that is interesting. Could you run it with 5 jobs as well so that we can see whether how much difference this makes? Also, are those data points multiple runs or just one? Please find attached make-j-runtimes-2.png which is plotted data with 2 complete run sets with 5 jobs each. thanks Saifi. make-j-runtimes-2.png Description: Binary data
disklabel or disklabel64 for vkernel on AMD64
Hi: On my AMD64X2 box, i've buildworld+buildkernel with SMP enabled and want to setup vkernel. Referring to the vkernel setup here http://www.dragonflybsd.org/docs/user/vKernelSetup/ Should disklabel or disklabel64 be used for vkernel image on AMD64 ? thanks Saifi.
