pkgsrc and DragonFly current DragonFly 2.9/x86_64 2011-03-11 15:00
For anyone who is curious, this is the first results I have for a bulk build of pkgsrc on DragonFly using gcc 4.4. This is on x86_64. -- pkgsrc bulk build report DragonFly 2.9/x86_64 Compiler: gcc Build start: 2011-03-11 15:00 Build end: 2011-03-21 20:01 Full report: http://avalon.dragonflybsd.org/reports/x86_64/2.9//20110311.1500/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/x86_64/2.9//20110311.1500/meta/report.bz2 Total number of packages: 10887 Successfully built: 8458 Failed to build: 563 Depending on failed package: 1282 Explicitly broken or masked: 511 Depending on masked package:73 Packages breaking the most other packages Package Breaks Maintainer - print/tex-misc 531 mins...@netbsd.org textproc/gtk-doc 245 pkgsrc-us...@netbsd.org databases/openldap-client201 g...@netbsd.org pkgtools/rpm2pkg 128 t...@netbsd.org databases/postgresql84-client105 a...@netbsd.org print/tex-dvipdfmx-def85 mins...@netbsd.org devel/boost-libs 71 j...@netbsd.org multimedia/xine-lib 62 pkgsrc-us...@netbsd.org lang/ocaml37 a...@netbsd.org lang/mono 31 kef...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org archivers/unalz pkgsrc-wip-disc...@lists.kldp.net audio/adplug jfr...@bsdprojects.net audio/akode-plugins-ffmpeg pkgsrc-us...@netbsd.org audio/akode-plugins-mpc pkgsrc-us...@netbsd.org audio/audacity pkgsrc-us...@netbsd.org audio/daapd nath...@netbsd.org audio/gqmpeg-devel 1 sek...@netbsd.org audio/gst-plugins0.10-jack 1 pkgsrc-us...@netbsd.org audio/libhydrogen 1 chris.ware...@btinternet.com audio/liblastfm1 pkgsrc-us...@netbsd.org audio/libsidplay2 1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/muse pkgsrc-us...@netbsd.org audio/musicpdpkgsrc-us...@netbsd.org audio/ncmpc pkgsrc-us...@netbsd.org audio/normalize1 pkgsrc-us...@netbsd.org audio/openal 6 pkgsrc-us...@netbsd.org audio/qjackctl pkgsrc-us...@netbsd.org audio/sidplaypkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org audio/terminatorxpkgsrc-us...@netbsd.org audio/trmpkgsrc-us...@netbsd.org audio/xmms-cdreadcheu...@tut.by audio/xsidplay pkgsrc-us...@netbsd.org benchmarks/bytebench pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org benchmarks/postalda...@silicium.ath.cx biology/mummer h...@cs.nmsu.edu cad/freehdl pkgsrc-us...@netbsd.org cad/pcb dmcmah...@netbsd.org cad/qcad 5 pkgsrc-us...@netbsd.org chat/amsnpkgsrc-us...@netbsd.org chat/ejabberdpkgsrc-us...@netbsd.org chat/galepkgsrc-us...@netbsd.org chat/gloox 1 schno...@cirr.com chat/kmess pkgsrc-us...@netbsd.org chat/quirc pkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/estic pkgsrc-us...@netbsd.org comms/gammu4 pkgsrc-us...@netbsd.org comms/gsmlib pkgsrc-us...@netbsd.org comms/hylafax 1 hallm...@ahatec.de comms/libopensync-plugin-syncml di...@netbsd.org comms/plppkgsrc-us...@netbsd.org converters/recode 1 kle...@netbsd.org cross/binutils 5 pkgsrc-us...@net
Re: Dual use Filesystem
On Sat, March 19, 2011 12:01 pm, Igor Gritsenko wrote: > Hello all, I need to use one shared disk partition(non-system) both for > Linux and DragonFly. Which filesystem should I use for best performance? ext3 or UFS might be at least readable for each side. However, the lowest-common-denominator of DOS (i.e. FAT) is possibly the most portable.
Summer of Code 2011 - we're in!
We made it into Google Summer of Code for a 4th year! (yay!) http://www.google-melange.com/gsoc/org/show/google/gsoc2011/dragonflybsd If you want to mentor, apply here: http://www.google-melange.com/gsoc/mentor/request/google/gsoc2011/dragonflybsd I'm assuming the applicants are going to be people I know with a direct history with DragonFly; otherwise be prepared to give a good history. Signing up to mentor does not mean you must mentor if there aren't any projects that interest you; it does mean you need to review applications and provide feedback for students March 28th - April 8th. If you want to be a student with DragonFly: Check the projects page for ideas: http://www.dragonflybsd.org/docs/developer/gsocprojectspage/ ... or come up with your own. Get your application together by March 28th. Start talking about it on the mailing list or IRC or however as soon as you can; there's a direct relationship between the amount of preparation we see beforehand and people getting accepted. Here's the timeline: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline
RE: SV: cannot mount disk with hammer file system
On Thu, February 24, 2011 5:56 am, Úlfar Ellenarson wrote: > Hi Alex. > > Thanks for all the help. I managed to solve my boot problem. It was a > matter of disk serial numbers as was mentioned in prior emails. I am more > than willing to share my solution and would think it would be a good > addition to the dragonflybsd site. It could be added as a faq or howto > about moving hard drives between servers or how to migrate dragonfly bsd > from vmware to virtualbox. However, I want to thank everyone who took > time to answer my enquiry. The dragonflybsd.org site is a wiki, so please do add it to the FAQ - we should probably have more on there about virtual environments, since Virtualbox seems to trip people up on every other release.
Re: cannot mount disk with hammer file system
On Tue, February 22, 2011 7:34 am, Úlfar Ellenarson wrote: > Hi. > > My first time posting on this list. My problem in a nutshell is I > installed dragonfly bsd 2.8 in vmware workstation. I reinstalled the host > system that vmware workstation was on and decided on using virtualbox. I > imported my dragonfly bsd vmware workstatation vmdk files into virtualbox. > Upon boot in virtualbox I run into the problem of mounting the disk. I > am prompted at the boot prompt to detect the disk that the system resides > on. I have tried hammer:ad0s1, hammer:ad0s1a, hammer:ad0s1d and just > ad0s1. I am however not able to boot the system. I have also booted from > the live iso image and mounted the system manually into /mnt using > mount_hammer /dev/ad0s1a /mnt and took a screenshot of /etc/fstab. I > however ask if there is a simple way to fix my mount problem. Any > information needed in regards to solving this problem will be gladly > appended. When you are booting from the disk, did you try ad1 instead of ad0? I've encountered that shift a few times, though with physical systems, not virtual. Are you sure it's Hammer and not UFS on your boot dir?
Re: Hammer recover question
On Sun, February 20, 2011 4:28 pm, Tim Darby wrote: > The good news is that it's recovering a ton of data! The > bad news is that it's taking an incredible amount of time. So far it's been > running 24 hours. Is that to be expected? The bad disk had approximately > 50GB on it, as reported by the df utility, but I don't know how much of > that is snapshots. I've had disks that go bad, and reading the raw data for recovery ends up being very, very slow just when trying to read from the actual 'bad' portions of disk. So this could take quite a while, just because of how the physical disk is responding.
Re: installed Postfix, no periodic message
On Wed, February 16, 2011 10:57 am, Chris Turner wrote: > http://www.dragonflybsd.org/docs/handbook/handbook-mail-changingmta/ > our copy (haven't diverged too much) Whatever notes you make, please work them into the new handbook: http://www.dragonflybsd.org/docs/newhandbook/ i.e. take the old page, apply your more recent notes, and stick it in the new section. That way, a new book that is only up-to-date (relative to old content) evolves.
Re: How big is fully loaded?
On Wed, February 16, 2011 11:12 am, Pierre Abbat wrote: > If I wanted a system with every package loaded, and enough space for > recompiling the kernel every month and upgrading the packages every > quarter, how big would it be? I assume you mean disk size. You'd want more disk space for whatever you actually do with the machine, other than installation/compilation. Far more of my disk space is taken with music/images than with installed package binary files. I'd go for 500G - a cheap disk is that size these days, and that's more than you'd need for the basics. You can probably go much smaller, but how much smaller is up to how you use it.
Re: avalon down
On Sun, February 6, 2011 12:21 pm, Pierre Abbat wrote: > Avalon appears to be down. I installed kdebase4 and some other programs > last > night, converted a project to CMake to run in kdevelop4, played around > with > Konqueror, and went to sleep. Now I'm trying to install the Linux emulator > and I get "package is not available on the repository". In the meantime, you can build it in meta-pkgs/suse100. (assuming you have pkgsrc-2010Q4 in /usr/pkgsrc.)
Packages for pkgsrc-2010Q4 built
The uploads are finally complete for binary packages on Avalon. I think each of the package-building machines crashed at least once during the process, but thanks to Matt and Mike and others, they were restarted/fixed quickly. I've changed the links on avalon, so pkg_radd for DragonFly 2.8 and DragonFly 2.9 will now download pkgsrc-2010Q4 packages. There's lots of packages: i386/DragonFly-2.8/pkgsrc-2010Q4 9406 i386/DragonFly-2.9/pkgsrc-2010Q4 9406 x86_64/DragonFly-2.9/pkgsrc-2010Q4 8900 x86_64/DragonFly-2.8/pkgsrc-2010Q4 8917 If you get errors asking for a new pkg_install, see the "Update pkgsrc system packages" section on the pkgsrc page on the DragonFly BSD site: http://www.dragonflybsd.org/docs/howtos/HowToPkgsrc/ (Even if you don't, it's still good information.) I haven't tested this too heavily, but it may be possible to upgrade packages automagically with 'pkg_radd -uv '. This may work better with packages that have less dependencies. i.e. upgrading Vim may work, all of KDE won't. Make sure that your /usr/pkgsrc is on the pkgsrc-2010Q4 branch so that everything matches. Check with 'cd /usr/pkgsrc; git branch'. If you're on an earlier branch, switch with 'git branch pkgsrc-2010Q4; git pull'. (I think; someone correct me if it's wrong.) If you're on pkgsrc master, stick with it unless it's from before 2011, in which case switching to pkgsrc-2010Q4 won't be any trouble. About pkgsrc-current: I'm cobbling together a system to build pkgsrc-current on DragonFly-current. Max Rotvel kindly contributed a CPU, and the last item I need now is some DDR2 RAM. If you're willing to donate 2x 2G sticks, please mail me. (I've been building pkgsrc-current on a VM very nicely contributed by Jan Lentfer. However, I'd like to have something I can physically reach when it has trouble, and has a bit more horsepower.)
Re: [Fwd: v12 pkgsrc 2010Q4 DragonFly 2.8/i386 2011-01-29 03:24]
On Wed, February 2, 2011 11:05 am, Pierre Abbat wrote: > On Tuesday 01 February 2011 16:17:09 Justin C. Sherrill wrote: >> With this last build finished, we should have a complete set of binary >> packages for i386/x86_64 and 2.8/2.9. I don't know if all the actual >> uploads are complete yet; I'll check later tonight. > > I can download packages for i386 2.9, but not i386 2.8, and some packages, > including kde and the new version of pkgin, require liblzma in world, > which > 2.8 doesn't have. I've also had two different failures trying to build 2.9 > world. I goofed up the i386/2.8 upload - should be fixed overnight.
[Fwd: v12 pkgsrc 2010Q4 DragonFly 2.8/i386 2011-01-29 03:24]
With this last build finished, we should have a complete set of binary packages for i386/x86_64 and 2.8/2.9. I don't know if all the actual uploads are complete yet; I'll check later tonight. Original Message Subject: v12 pkgsrc 2010Q4 DragonFly 2.8/i386 2011-01-29 03:24 From:"Charlie Root" Date:Tue, February 1, 2011 4:28 am To: jus...@shiningsilence.com -- pkgsrc bulk build report DragonFly 2.8/i386 Compiler: gcc Build start: 2011-01-29 03:24 Build end: 2011-02-01 09:14 Full report: http://avalon.dragonflybsd.org/reports/i386/2.8/20110129.0324/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/i386/2.8/20110129.0324/meta/report.bz2 Total number of packages: 10483 Successfully built: 9474 Failed to build: 358 Depending on failed package: 157 Explicitly broken or masked: 346 Depending on masked package: 148 Packages breaking the most other packages Package Breaks Maintainer - lang/mono 31 kef...@netbsd.org devel/py-gobject 24 pkgsrc-us...@netbsd.org devel/libthrift9 tonne...@netbsd.org textproc/cabocha 6 oba...@netbsd.org security/lasso 6 m...@netbsd.org devel/libcompizconfig 5 pkgsrc-us...@netbsd.org security/openvas-libraries 4 pkgsrc-us...@netbsd.org security/nessus-libraries 4 pkgsrc-us...@netbsd.org security/botan 4 pkgsrc-us...@netbsd.org lang/g95 4 wennm...@netbsd.org Build failures Package Breaks Maintainer - audio/amarok-kde3pkgsrc-us...@netbsd.org audio/bslpkgsrc-us...@netbsd.org audio/darkicepkgsrc-us...@netbsd.org audio/gogo pkgsrc-us...@netbsd.org audio/liblastfm1 pkgsrc-us...@netbsd.org audio/libvisual0.2-plugins pkgsrc-us...@netbsd.org audio/ncmpc pkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org biology/gromacs pkgsrc-us...@netbsd.org cad/tnt-mmtl dmcmah...@netbsd.org chat/ejabberdpkgsrc-us...@netbsd.org chat/finch pkgsrc-us...@netbsd.org chat/gajim vsevo...@highsecure.ru chat/telepathy-loggerpkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/asterisk18 jnem...@netbsd.org comms/libopensync-plugin-evolution2 pkgsrc-us...@netbsd.org comms/libopensync-plugin-syncml di...@netbsd.org comms/plppkgsrc-us...@netbsd.org converters/bibtex2html mins...@netbsd.org converters/py-zfec 1 g...@ir.bbn.com converters/wv 2 a...@netbsd.org cross/avrdudepkgsrc-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-msdosdjgpppkgsrc-us...@netbsd.org databases/clisp-gdbm a...@inbox.ru databases/couchdbfi...@joyent.com databases/openldap-smbk5pwd g...@netbsd.org databases/slony1 a...@netbsd.org devel/bullet pkgsrc-us...@netbsd.org devel/clisp-pcre a...@inbox.ru devel/clisp-syscalls a...@inbox.ru devel/clisp-zlib a...@inbox.ru devel/coccinelle pkgsrc-us...@netbsd.org devel/electric-fence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/ethos pkgsrc-us...@netbsd.org devel/frama-cto...@netbsd.org devel/gtlpkgsrc-us...@netbsd.org devel/guile-gnomeg...@netbsd.org devel/java-subversion
Re: package maintainer
On Tue, February 1, 2011 8:39 am, Pierre Abbat wrote: > How do I find out who maintains a package? I guess it's some option to > pkg_info, but I don't know what. In addition to what Jeremy posted, I like going to http://pkgsrc.se/ - it's shown there too.
Re: pkgbox64 pkgsrc 2010Q4 DragonFly 2.9/x86_64 2011-01-23 17:19
On Sat, January 29, 2011 6:09 pm, Pierre Abbat wrote: > On Friday 28 January 2011 22:23:14 Justin C. Sherrill wrote: >> I don't know what's up with ruby19-base - it dumps core the same way >> when >> you build it individually. Suggestions welcomed. >> >> Other than that, we're looking good in terms of total packages built. > > If you're succeeding in building policykit, where do you get it from? I > still can't. Oh, wait - policykit - this is one of the things affected by the Sourceforge outage. It was probably built before the outage started. Note that the build started on the 23rd but Sourceforge didn't start turning things off until the 27th.
Re: pkgbox64 pkgsrc 2010Q4 DragonFly 2.9/x86_64 2011-01-23 17:19
On Sat, January 29, 2011 6:09 pm, Pierre Abbat wrote: > On Friday 28 January 2011 22:23:14 Justin C. Sherrill wrote: >> I don't know what's up with ruby19-base - it dumps core the same way >> when >> you build it individually. Suggestions welcomed. >> >> Other than that, we're looking good in terms of total packages built. > > If you're succeeding in building policykit, where do you get it from? I > still can't. This is a 2.9/x86_64 system, and I'm using pkgsrc-2010Q4. I don't know if you're building on the same system or not. e.g. it may not build on i386.
pkgbox64 pkgsrc 2010Q4 DragonFly 2.9/x86_64 2011-01-23 17:19
I don't know what's up with ruby19-base - it dumps core the same way when you build it individually. Suggestions welcomed. Other than that, we're looking good in terms of total packages built. Original Message Subject: pkgbox64 pkgsrc 2010Q4 DragonFly 2.9/x86_64 2011-01-23 17:19 From:"Charlie Root" Date:Fri, January 28, 2011 10:12 pm To: jus...@shiningsilence.com -- pkgsrc bulk build report DragonFly 2.9/x86_64 Compiler: gcc Build start: 2011-01-23 17:19 Build end: 2011-01-29 03:03 Full report: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110123.1719/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110123.1719/meta/report.bz2 Total number of packages: 10483 Successfully built: 8923 Failed to build: 401 Depending on failed package: 581 Explicitly broken or masked: 504 Depending on masked package:74 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby19-base 324 t...@netbsd.org math/R39 ma...@netbsd.org lang/ocaml36 a...@netbsd.org lang/mono 31 kef...@netbsd.org devel/py-gobject 24 pkgsrc-us...@netbsd.org textproc/xerces-c 18 pkgsrc-us...@netbsd.org devel/libthrift9 tonne...@netbsd.org www/w3m7 uebay...@netbsd.org security/lasso 6 m...@netbsd.org devel/libcompizconfig 5 pkgsrc-us...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/bslpkgsrc-us...@netbsd.org audio/daapd nath...@netbsd.org audio/liblastfm1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/muse pkgsrc-us...@netbsd.org audio/ncmpc pkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org audio/terminatorxpkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org cad/tnt-mmtl dmcmah...@netbsd.org chat/ejabberdpkgsrc-us...@netbsd.org chat/finch pkgsrc-us...@netbsd.org chat/gajim vsevo...@highsecure.ru chat/galepkgsrc-us...@netbsd.org chat/silc-client 1 s...@netbsd.org chat/silc-server s...@netbsd.org chat/telepathy-loggerpkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/libopensync-plugin-evolution2 pkgsrc-us...@netbsd.org comms/libopensync-plugin-syncml di...@netbsd.org converters/py-zfec 1 g...@ir.bbn.com converters/wv 2 a...@netbsd.org cross/avrdudepkgsrc-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-msdosdjgpppkgsrc-us...@netbsd.org databases/clisp-gdbm a...@inbox.ru databases/couchdbfi...@joyent.com databases/java-db3 pkgsrc-us...@netbsd.org databases/java-qdbm oba...@netbsd.org databases/java-tokyocabinet oba...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/slony1 a...@netbsd.org devel/avltreewrstu...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org devel/clisp-pcre a...@inbox.ru devel/clisp-syscalls a...@inbox.ru devel/clisp-zlib a...@inbox.ru devel/electric-fence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/ethos pkgsrc-
Re: missing crypto files
On Mon, January 24, 2011 6:57 pm, Pierre Abbat wrote: > I found that libcrypto is version 5 in 2.8.2, but libevent, which is > needed by > tor, is missing. What should I do: install KDE and hold off on Tor, switch > to > Q3 and forgo KDE for now, or wait until Q4 is finished building? You could always build KDE from 2010Q4; having manually built packages from pkgsrc-2010Q4 won't interfere with later binary installations also from 2010Q4. That may be quickest.
Re: bulk build for 2010Q4 progress
On Sat, January 22, 2011 4:09 pm, Sascha Wildner wrote: > On 1/22/2011 21:11, Chris Turner wrote: >> On Thu, Jan 20, 2011 at 08:38:50PM -0500, Justin C. Sherrill wrote: >>> multimedia/py-gstreamer0.10 22 pkgsrc-us...@netbsd.org >> >> Last I tried the attached makefile patch fixed this package - >> still need to submit a fix - >> >> this probably brings up ye-old question of interface to the pkgsrc >> ppl, ports, etc - IIRC kind-of dropped since the last time this >> came up.. > > This has been fixed: > > http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=42598 > > Thus, it should also be fixed in Q4. Why it still fails in this here > bulk build I don't know. It's probably stale data - I normally build from scratch on each new quarterly release/DragonFly release, but I didn't this time because avalon was down right at the same time 2010Q4 came out.
bulk build for 2010Q4 progress
Here's the state of the bulk build for pkgsrc-2010Q4: DragonFly 2.8/i386: 5864 packages built so far DragonFly 2.8/x86_64: 10304 packages built so far DragonFly 2.9/i386: 3144 packages built so far DragonFly 2.9/x86_64: All 10483 packages done - uploading now. The report from the 2.9/x86_64 build is below, for the curious. -- pkgsrc bulk build report DragonFly 2.9/x86_64 Compiler: gcc Build start: 2011-01-20 02:49 Build end: 2011-01-20 15:37 Full report: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110120.0249/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/x86_64/2.9/20110120.0249/meta/report.bz2 Total number of packages: 10381 Successfully built: 8555 Failed to build: 379 Depending on failed package: 813 Explicitly broken or masked: 559 Depending on masked package:75 Packages breaking the most other packages Package Breaks Maintainer - lang/ruby19-base 325 t...@netbsd.org security/heimdal 233 pkgsrc-us...@netbsd.org multimedia/xine-lib 59 pkgsrc-us...@netbsd.org lang/ocaml35 a...@netbsd.org lang/mono 29 kef...@netbsd.org multimedia/py-gstreamer0.10 22 pkgsrc-us...@netbsd.org net/gupnp-igd 19 pkgsrc-us...@netbsd.org textproc/xerces-c 18 pkgsrc-us...@netbsd.org graphics/gimp 15 a...@netbsd.org graphics/sane-backends13 pkgsrc-us...@netbsd.org Build failures Package Breaks Maintainer - archivers/star uebay...@netbsd.org audio/akode-plugins-mpc ha...@netbsd.org audio/buzztard 1 pkgsrc-us...@netbsd.org audio/daapd nath...@netbsd.org audio/liblastfm1 pkgsrc-us...@netbsd.org audio/maplay pkgsrc-us...@netbsd.org audio/ncmpc pkgsrc-us...@netbsd.org audio/sox 11 pkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org benchmarks/netperf pkgsrc-us...@netbsd.org benchmarks/randread pkgsrc-us...@netbsd.org biology/gromacs pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/magicpkgsrc-us...@netbsd.org cad/tnt-mmtl dmcmah...@netbsd.org chat/ejabberdpkgsrc-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/unrealircd pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/libopensync-plugin-syncml di...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/tn3270 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-msdosdjgpppkgsrc-us...@netbsd.org databases/clisp-gdbm a...@inbox.ru databases/couchdbfi...@joyent.com databases/rrdtool 11 pkgsrc-us...@netbsd.org databases/sqlite3-tclpkgsrc-us...@netbsd.org devel/avltreewrstu...@netbsd.org devel/binutils pkgsrc-us...@netbsd.org devel/clisp-pcre a...@inbox.ru devel/clisp-syscalls a...@inbox.ru devel/clisp-zlib a...@inbox.ru devel/electric-fence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/ethos pkgsrc-us...@netbsd.org devel/gsoap chrisware...@chriswareham.demon.co.uk devel/gtl
Re: Where is qmake?
On Wed, January 19, 2011 8:16 am, Pierre Abbat wrote: > > If qmake is not in qconf, where is it? x11/qt4-tools, I think. I base that on searches, not from installation, so YMMV. http://pkgsrc.se/x11/qt4-tools
Re: BitTorrent
On Sun, January 16, 2011 3:25 pm, Pierre Abbat wrote: > Are current ISOs available by BitTorrent? No, at least not in any offical, ongoing way that I know of.
Pkgsrc 2010Q4 out, packages building
The most recent version of pkgsrc's quarterly releases is out: pkgsrc-2010Q4. I'm starting the build of packages now - avalon should be back by the time they finish, for upload. It usually takes at least a week. Packages for i386/2.9 will be delayed somewhat, as avalon was where I built them. (On that note, anyone have an AM2+ CPU, 4G of DDR2 RAM, or a hard drive they'd be willing to donate so I can finish this box I'm putting together for package building?) If you want to pull down pkgsrc-2010Q4 RIGHT NOW and don't want to wait for avalon to come back so you can grab it through git, cvs will work: export cvsroot=anon...@anoncvs.netbsd.org:/cvsroot export CVS_RSH=ssh cd /usr cvs -q checkout -rpkgsrc-2010Q4 -P pkgsrc Update with: cvs -q update -dP Or just switch back to git when it's available - there may be a clever way to update, but I'd just delete the pkgsrc directory and re-download. It may be possible to get the 2010Q4 branch via git from crater; I haven't tried.
Re: Avalon maintainance update
On Tue, January 11, 2011 7:54 pm, Matthew Dillon wrote: > I'd rather not change the DNS, it could create confusion for the > mirrors. And it will probably confuse the hell out of crater and > pkgbox64 too. We shouldn't have any mirrors pulling from crater. Does crater/pkgbox64 pull from git.dragonflybsd.org? This would just be the git target. I may be oversimplifying this in my mind I worry that if something bad happens to mirror-master/avalon right at a release, it would cause a headache. To eliminate that future headache, we'd need either a bunch more hosts or more DNS flexibility.
Re: Avalon maintainance update
On Tue, January 11, 2011 6:01 pm, Matthew Dillon wrote: > Avalon will be down all of this week for maintainance. It is getting > a new storage subsystem. We expect to be able to get it back into a > rack mid-next-week or so. > > In the mean the time the mirrors have a snapshot of the recent bulk > builds and the src and pkgsrc repos can be accessed from the master > site, crater.dragonflybsd.org. > > Our other mirrors will likely be a bit out of date on src and pkgsrc > as they typically mirrored from avalon. Is it worth changing the DNS for git.dragonflybsd.org, temporarily? That way nothing confuses the mirrors, but 'make src-update' and friends work.
Re: DragonFly in the cloud with ARM, Xen, and OpenStack
On Sun, January 9, 2011 5:42 pm, Alexander Orlov wrote: > Hi, > > recently Rackspace introduced NASA's OpenStack.org as a new OSS-based > cloud > implementation, followed by a great feedback form Dell, Intel, and NTT > Data. > I'd like to know whether there are some people trying to run DragonFly on > top of OpenStack/Xen, if it's possible at all and whether it makes sense > considering DragonFly's LWKT architecture. People have asked about it, but that's all that has happened, as far as I know. It would be neat to have, but wouldn't add intrinsic value to DragonFly. > DragonFly currently supports only the x86 architecture but are there plans > (actual implementation efforts) to port DragonFly to ARM. Nvidia and some > other chip manufacturers seeing ARM as a new SMP-capable server platform. I've always wanted a port to ARM, but there isn't enough consumer hardware for it yet.
Re: Avalon being moved
On Sat, January 8, 2011 2:24 pm, Matthew Dillon wrote: >Avalon is being moved and will be offline for a while, possibly 2-3 >days depending. We may use this opportunity to upgrade it's storage >subsystem as well. > >This is rather short notice (as Avalon is already down) but this is >probably the best time to do it. Can git.dragonflybsd.org be pointed somewhere else in the meantime?
Re: Hammer Benchmark Fun
On Sat, January 8, 2011 2:58 am, Alex Hornung wrote: > On 08/01/11 06:12, Siju George wrote: >> Hi, >> >> Some one send this to me >> >> http://www.phoronix.com/scan.php?page=article&item=dragonfly_hammer&num=1 >> [...] >> >> http://en.wikipedia.org/wiki/Phoronix_Test_Suite#Controversies > > While I don't want to get into how useful or useless their tests are, it > would have been nice to see those same tests with a different scheduler, > to see if it made any impact. Especially in the blogbench case it made a > huge difference during my initial testing. > > Overall I think our I/O performance has improved a lot since previous > releases and we are at a comparable level to, at least, other BSDs. All > of this is anecdotal evidence and gut feeling of course :) Looking at those tests, there was a huge jump in relative performance for Hammer once they did multi-threaded tests - and this was on uniprocessor systems! Of course, comparing a filesystem with infinite snapshots and history retention to one that doesn't do it at all is never going to work out the same for speed. It's like comparing elephants and chimpanzees in a weight contest.
Re: Compiling with gcc -march ix86
On Fri, December 24, 2010 5:34 pm, Stephane Russell wrote: > Hi, > > I'm actually trying to compile asterisk on DFBSD. It needs to compile > with the compiler option -march=ix86, with x>3 (gcc spec). But DFBSD > "uname -m" is returning systematically "i386". Is their a workaround for > that, that would allow me to compile without hacking the autotools > scripts? You could set the environment variable UNAME_M to whatever you think would work; I don't know if that would get picked up during the build process, but it's worth a try. I'm interested in seeing asterisk work.
Re: kde in 2010Q3
On Sun, December 12, 2010 5:54 am, Pierre Abbat wrote: > I'm upgrading packages. The pkgsrc for 2010Q3 contains kdelibs and kdebase > in > both versions 3 and 4, but the packages built for 2.8 and 2.9 do not. How > come? The build failed. Looking at the logs, it was because of sane-backends-1.0.21 and heimdal-1.1nb5 not building, for at least 2.8/i386/KDE3.
Re: RegressionTest Results
On Fri, November 26, 2010 4:16 am, Eric Bakan wrote: > Here are the results of running the pcca-test framework. Changes made to a > clean install include modifying the sudoers file, installing ruby, and > installing sudo to comply with the framework's README. I just redirected For those in the audience, this was one of the Google Code-In tasks; to report on our current compliance with beket's regression tests here: http://www.dragonflybsd.org/docs/developer/RegressionTest/ If anyone (including Eric) wants to investigate the failed ones further...
Re: Firefox, Namoroka, Iceweasel
On Wed, November 24, 2010 11:48 am, Pierre Abbat wrote: > I'm accessing a site which doesn't recognize my Firefox and sends code > that > doesn't work. (It does work with Konqueror on my Linux box when I > configure > it to pretend to be MSIE, so the problem's not urgent.) I suspect it's > because Firefox sends a browser ID string that doesn't say "Firefox". It > ends > with "Namoroka 3.6.3" instead. I'm using 2010Q1. If I upgrade (which I As other people noted, there's ways around this, including build options. The reason for it is that there are legal restrictions around the Firefox name, which means it can't be redistributed without an agreement with the Firefox Foundation or whatever it is. We'd have to create a legal entity to sign a document etc. etc. I think the NetBSD Foundation has gone through this, but it does not apply to non-NetBSD releases, to my knowledge.
Re: pkg/44108 (gstreamer0.10-0.10.30 has gst-inspect that never returns on DragonFly)
On Fri, November 19, 2010 12:44 am, Alistair Crooks wrote: > I thought Rumko was brought on board to be a df pkgsrc representative. That process (as far as I know) hasn't completed yet. > We'd be equally interested in getting more df people on board, but our > idea of people who would be good for pkgsrc and dragonfly, and the > dragonfly community's ideas don't seem to match. > > Perhaps we could have some suggestions/volunteers from the DF community > to help look after and guide pkgsrc on DF? Please? The only criteria I could think of is "someone who would create DragonFly-specific fixes to pkgsrc", judged by their existing activity in DragonFly. If the last round of suggested DragonFly people wasn't acceptable based on this, what does it take? What are the criteria?
Re: Compatible Laptops.
On Tue, November 16, 2010 9:33 pm, David Crosswell wrote: > Greetings all, > > My old laptop, an HP Compaq nx6120 is playing up in a number of different > ways, so it looks like retirement time. > > What's a good reliable model? > Any recommendations? There's a number of laptops mentioned on the dragonflybsd.org website. Several people have been using IBM/Lenovo laptops with general success. The "standard" netbook model usually works - Atom processor, etc, if you want that size of computer.
Re: Project.
On Tue, November 9, 2010 6:45 pm, David Crosswell wrote: > I thought I'd contact the list to find out if there would be people here > that would be interested in assisting me with getting my > knowledge within the DragonflyBSD environment up and running as quickly as > possible in order to achieve this. A good place to start may be with the man pages - Hammer has a good explanation there in section 8, as do many other parts of the system.
Re: Linuxulator question, boot loader oddity
On Sun, November 7, 2010 8:45 am, Tim Darby wrote: > That's when I noticed that loader.conf looked like > this: > > VFS.ROOT.MOUNTFROM="HAMMER:SERNO/s0a4j1ta141435.S1D" > linux_load=yes > > I tried changing the mountfrom line to: > vfs.root.mountfrom="hammer:serno/S0A4J1TA141435.s1d" I don't know what editor you use, but is it possible you somehow hit the right key sequence to invert case on that line while entering the linuxulator stuff? It's a guess, but it fits the symptoms.
Google Code-In! (details, instructions)
DragonFly was accepted as 1 of 20 organizations for Google Code-In! http://google-opensource.blogspot.com/2010/11/announcing-accepted-organizations-for.html We're 1 of 3 operating systems involved (us, Debian, and Haiku) and the only BSD involved. * The background: Code-In is like Summer of Code, in that it uses open source projects to assign work to volunteers in school, and Google pays the bill. Google Code-In is for 13 to 18-year-olds, as students. * If you aren't 13-18 years old: As described in the link above, sign up for an account at the Google Melange site: http://google-melange.com/ And request to be a mentor for DragonFly BSD. As a mentor, you can suggest projects for the students, and (if you want to) evaluate their work. We need project ideas that fit in the 8 different categories mentioned on the google-melange.com front page. You can never have too many ideas, so please contribute a few. Consider this an open invitation for everyone involved in DragonFly; not all the tasks have to be strictly code, so there isn't necessarily commit access involved. If you have friends involved in school teaching at the appropriate ages, let them know about this. * If you are 13-18 years old: Tasks become available for DragonFly and other projects November 22nd. Finishing 1 task gets you a T-shirt. Finishing 3 tasks gets you $100. You max out at $500 and 1 shirt. (15 tasks max compensation)
Re: MC not starting
On Thu, November 4, 2010 6:54 pm, PrzemysÅaw PaweÅczyk wrote: > On Thu, 4 Nov 2010 23:38:31 +0100 > Paul Onyschuk wrote: > >> It's Slang problem. MC builded with this options, works just fine >> under localized cons25l2 terminal and csh: >> >> PKG_OPTIONS.mc= ncurses -slang >> >> Other apps that uses devel/libslang2 like news/slrn and misc/most, >> also suffers from the same problem. > > Thanks. > > But is there any chance to get MC working after downloading its > binaries just after fresh installation of DF? Just like it is with > other systems? I think I can do the binary builds with PKG_OPTIONS.mc set to that, along with PKG_OPTIONS.slrn and PKG_OPTIONS.most. If they aren't going to work on DragonFly without that, I can see no downside to that. (Someone please correct me if there's a hidden gotcha.)
Re: 2 questions regarding PF
On Tue, November 2, 2010 7:28 pm, PrzemysÅaw PaweÅczyk wrote: > Hi, > > 1. Why PF 4.2 not 4.7 or 4.8? > > OpenBSD page http://www.openbsd.org/faq/pf/index.html > has one important remark bolded: "In particular, there are > significant differences between 4.6 and 4.7." > > Doeas it mean that I would have to learn something rather > old - how to use PF 4.2 instead of PF 4.7/4.8. Right? Jan Lentfer has been working on upgrading pf - he's gotten us to the present state with a good deal of effort, so I anticipate pf will soon match the released version. I'm not defining "soon" that exactly. > 2. But support for the PF 4.2 is sorta "soft" (weak), as well. > I wasn't able to find PF 4.2 doc files on DF BSD WWW. > I'd like to see them in the form of OpenBSD's "PF: The > OpenBSD Packet Filter" (http://www.openbsd.org/faq/pf/index.html) Why not read that instead? It's right from the source.
Re: Release update -- still not quite yet
On Thu, October 28, 2010 5:37 pm, Matthew Dillon wrote: > I maded a bit of a flub on the ISOs, they couldn't boot UP. We > will be fixing that and rerolling the ISOs and IMGs tonight. > Since we have reroll the stuff anyway we will also be enhancing > the install a bit and I will push a SMP invltlb fix into the > release as well. > > I've removed the pre-staged 2.8.1[A] files from iso-images. > 2.8.2 will go up tonight and should propagate to the mirrors > overnight. > > We are still waiting for the bulk build to finish to officially > declare a release. Currently at package [9621/10381] for 2.8 and [9740/10381] for 2.9 packages. So soon, I hope.
Re: 2.8 release schedule - tentitively Wednesday 27 October.
On Fri, October 22, 2010 1:09 am, Matthew Dillon wrote: > We are still scheduled to officially release mid-next week. I will > be doing the final the MFCs from master on Sunday (as a lot of fixes > have gone in since the branch). All of the big-ticket bugs have been > squashed. There are still a few medium-ticket bugs (e.g. Rumko's > listen/connect issue) which I am looking at now. > > Justin is making progress on pkgsrc though I do not know what the > state of the KDE stuff is. I think Wednesday is a good target to > have it all on the servers ready to go. The KDE patches from Alex were just committed to KDE, but I don't know if they would make it back into the pkgsrc versions, especially the pkgsrc-2010Q3 versions. Specifically prodding some pkgsrc people _may_ do it; I don't have time to chase this down. I'm restarting the x86_64 build on 2.9 with the suggested patches for pango/gstreamer, and the other builds are progressing well, so we should be done Wednesday, barring surprises. (crossing my fingers...)
Re: hammering the drive
On Thu, October 21, 2010 10:37 pm, Matthew Dillon wrote: > Time tends to wear out drives more than the seeking. Dust and grime > from > outside that gets through the filter and material from inside the > drive > itself. Basically just time. You do want to make sure the drive is > well anchored (screwed into) the machine, and doesn't experience any > undo shock while operating. > > The only major mechanical limitation that can cause a drive to fail > other than time is in wear and tear from hard parking and > spindowns/spinups. Basically any time the head has to land in the > parking area. Drives, of course, can fail for a variety of reasons > due to defects in manufacturer, using the wrong lubricant, etc etc. > Seeking is not usually a contributor though. I don't have hard evidence to back this up, but I've felt for some time that having a UPS in place can make a difference too. I've seen similar hardware survive much longer with the only clear difference being a UPS to keep the voltage from fluctuating. Grit is probably worse. Here's a story: One of the computers at my $WORK is in a 10x10 room about 15 feet up the side of a 3-bay truck loader that dispenses thousands of tons of rock salt daily. It's in a closed but not airtight container, and the room has an air filter. Just the salt particles tracked in or drifting in when someone leaves the door open, combined with humidity, literally dissolved the inside of the computer in less than a year. The two lessons here are 1: keep your computers as clean as possible and 2: service contracts for parts and labor are sometimes really worth it.
Re: Bulk buils space requirements
On Thu, October 21, 2010 2:36 am, Siju George wrote: > HI, > > I got around 250 GB free on my desktop. > > I would like to try out a bulkbuild of pkgsrc ;-) > > will that space be enough? I have some scripts that work as a wrapper around the bulk builds I do; this may be more than you need, but I'd like to see if they make sense to someone who is not me: http://www.shiningsilence.com/simplepbulk/ The two caveats for you: - Bulk builds take a week on decent hardware; you're building over 10,000 packages, after all. The limited_list option in the pbulk config can let you limit it to certain packages, which you may want to do. - If you're doing this on Hammer, keep an eye on disk usage. It generates a huge amount of disk activity if you build everything, and Hammer will happily keep track of all those changes. I've filled terabyte disks unintentionally by performing multiple builds.
Re: No package installation method works
On Wed, October 20, 2010 3:54 pm, Torbjorn Granlund wrote: > A long term *BSD user, I decided to extend our GNU package nightly test > system setup with Dragonfly BSD. This is an install under > virtualisation (qemu or Xen). > > The actual install went smoothly, but the package install have failed > utterly. Other people have covered this well so far, but here's details on the pkg_install issue: http://www.shiningsilence.com/dbsdlog/2010/09/26/6472.html pkg_install recently had a version check introduced between the release of 2.6.3 and the most recent quarterly release of pkgsrc; it fails on that. The pkgsrc howto page, which I think may already have been linked, is a good resource for now: http://www.dragonflybsd.org/docs/howtos/HowToPkgsrc/
Re: Packages mentioned in summary file are not on mirrors
On Mon, October 18, 2010 9:50 am, Tomas Bodzar wrote: > Hi all, > > 2010Q2 is done by dfly on mirrors? Eg. mplayer is in summary file and > showed through pkgin or pkg_search, but install is not possible as > it's not in mirror. > Some license issues, sure, but why it's in summary file? Usually, this happens because the file builds during the bulk build, but there's some restriction like NO_BIN_ON_FTP caused by how it's licensed that means it can't be uploaded. I don't see anything for that when looking through the Makefiles for that or for mplayer-common, which it depends on. It's also not listed as something that failed building, which makes sense if it's in the summary. I don't have an immediate answer for this, but I am starting a new set of build builds now; it may become clear with this new build. (or it'll all magically work. And I'll get my own pet pony that farts rainbows. Hope springs eternal.)
Re: Firefox still crashes
On Fri, October 15, 2010 12:52 am, Tomas Bodzar wrote: > That's an excellent reading. It will be great to read more about > technologies in DragonflyBSD. Something like > http://www.openbsd.org/papers ? ;-) http://www.dragonflybsd.org/presentations/ ? Not quite the same, but if this was expanded - or even if it wasn't - this could fit there.
Re: hammer version-upgrade
On Tue, October 12, 2010 10:52 pm, Pierre Abbat wrote: > I'm running Hammer version 1, and can go up to 4. Should I upgrade, and > how long does it take? I recall upgrades taking little time (measured in seconds, generally, not minutes or hours). Yes, you should upgrade - bugs are fixed and you should have noticeably better performance. I never had a problem with upgrades, but if it's with data you absolutely can't lose, make sure it's backed up.
Re: firefox instability may be fixed now in HEAD
On Tue, October 5, 2010 11:20 am, Pierre Abbat wrote: > I think that when I last upgraded all my packages, it was to Q1. For me, a > package upgrade is a big event, because I don't have much free time, and I > have to see if the upgrade broke anything (I frequently find that I have > to > symlink libraries, because the upgrade doesn't replace libraries that have > the same version number but are now linked against newer other libraries). > For the same reason I haven't upgraded my Ubuntu box in a few years. So If you really, really want to be sure, 'pkg_rolling-replace -rsuv', with a /usr/pkgsrc that contains a quarterly release. This will rebuild everything that can be upgraded, and everything that could possibly depend on those packages. It'll take a long time, and there may be a few packages you have to manually delete and reinstall if they've moved (i.e. are now under a different name.) However, this should clear up any lingering library problems.
Re: firefox instability may be fixed now in HEAD
On Tue, October 5, 2010 1:01 am, Matthew Dillon wrote: > > :I'm still using 2010Q1. Should I switch to the 2.8 build of packages once > I > :recompile the kernel and world? > : > :Pierre > > We won't have 2.8 packages until about a week after netbsd rolls Q3. > In fact, right now we are waiting for netbsd to roll Q3 so we can roll > the 2.8 release branch and start building packages. > > I think the 2.6 and 2.7 packages are Q2. The packages on avalon right now are pkgsrc-2010Q2. 2010Q3 was scheduled to be tagged Oct. 1st, but it hasn't happened last I checked. I haven't seen anything on the pkgsrc mailing lists to tie down when it will be.
Re: USB image
On Wed, September 29, 2010 11:42 pm, Tomas Bodzar wrote: > When someone wants to go deeply in some area then there is only one > way - a lot of years of learning and experience. It does not change > just because we have Internet and PR materials from stupid vendors > talks lies. OS is very complex system - take it from the other side - > flying is so easy (at least for birds); why do I need to learn that > complicated stuff about mathematics, physic, meteorology and so on; > why there is not one-click-button-to-fly airplane? How about space > travelling? How about submarines? How about cars? Are you able to > create your own on same level of quality as from those companies? No? > Guess why - because you lack info and experience in that area as it's > not so easy and not because someone wants to be rude against you. The best answer when someone says "This doesn't work for me" isn't "You don't know enough" but rather "Here, let me show you how." To answer the original question, I haven't seen a USB drive solution that didn't involve some other steps - many of them require a Windows user to boot from a live CD image to use dd or equivalent to write to the USB drive, or rarely have a specialized program to write it out (Mandriva). I've heard of Linux installers that were able to understand a fat32 USB drive if files were set up a particular way, but it didn't seem to be easier overall. This looks interesting: http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ Would it work with a DragonFly image? Please, someone try this.
Re: Misleading directory names
On Tue, September 28, 2010 4:31 pm, Antonio Huete Jimenez wrote: > Justin, > > How would anyone be using amd64 directory for 2.0 if we didn't have it > back then? Well, no, but if you think about it for a bit you'll realize it's an example to show how long support can be needed for some people, not an history of when packages for amd64 were out. Nature took its course and we ended up having to move older pkgsrc binaries anyway because the archive was getting too big for people to mirror easily.
Re: Misleading directory names
On Tue, September 28, 2010 6:58 am, PrzemysÅaw PaweÅczyk wrote: > Doesn't it seem to you like being a bit untidy? And, btw, for how long > "the legacy" will be going on...? With so much changes between 2.6.3 > and 2.8.0? Do you really think/know that "the legacy" systems will be > kept running yet after new release (which one)? > > Manpower shortages define status quo, no doubt about it, as > pkg_radd/pkg_search are still unchanged with amd64 links. I appreciate what you're saying about having things be clear to users, but this is the alternative to something that would be more confusing. 'amd64' was hardcoded into a number of package tools, including early versions of pkg_radd. The choice is either leave it untidy with a note about the reason for the directory, or break functionality for older machines. Someone was still running a number of 2.0 machines in an environment that couldn't be easily upgraded, last I asked about this, so untidy is a better choice, in this case. The long-term answer that I would prefer is to not have people need to navigate a package hierarchy at all, and instead have the appropriate software selected automatically. We're closer to that with the pkg_radd tool.
Re: example of dfbsd deployment or product that based on dfbsd
On Tue, September 28, 2010 3:54 am, Iwan Budi Kusnanto wrote: > Hi, > I just have interest in DFBSD and have some questions. > > Can someone give me examples of some big/great DFBSD deployment or some > product that based of DFBSD ? > > Is DFBSD proven to be rock solid in real world ? I don't know if these are the scale you are looking for , but dragonflybsd.org, of course, has been DragonFly-hosted for years. My own domain, shiningsilence.com, has been a DragonFly system for... 5 years now? I have been following regular releases and had very little issues.
Re: Unpopulated subdirectories for amd64
On Tue, September 28, 2010 2:41 am, PrzemysÅaw PaweÅczyk wrote: > Hi, > > I'm learning the DFBSD community website. > > I've found that .../stable/... subdirectories are unpopulated contrary > to .../stable/All. See .../stable/graphics and others. > > http://avalon.dragonflybsd.org/packages/amd64/DragonFly-2.7/stable/All/ These packages are normally uploaded by the bulk build mechanism that creates them all. The bulk build puts all the binary packages in /All, and then creates symlinks in all the other directories. The symlinks aren't uploaded, which hasn't been a problem in general because everything (pkg_add, pkg_radd, etc.) looks in the /All dir by default. I've been a bit nervous about having all those links uploaded; I don't know if mirrors will download them as links or treat them as files and download the actual data all over again.
Re: USB image
On Sun, September 26, 2010 4:32 pm, tron wrote: > If I want to copy the DF USB image onto my USB stick and I am working > under WinXP, can I open the archive with 7zip and just copy the > resulting files/folders to the stick or will I need a special app for > installing the image to the USB stick? (Sorry if this sounds dumb, but > I am only used to the world of Windows and the handbook on DF page only > discusses installation with CD.) I recently used: http://www.chrysocome.net/dd On a Windows 7 machine to write an image to a USB stick and it worked. It's a little fiddly with the backslashes because it's a Windows system, but oh well.
Re: Sub-project donation
On Sat, September 25, 2010 3:27 pm, Waldemar Bergstreiser wrote: > Hi folk, > > I would like to support some sub-projects by a small donation and I have > seen a "code bounty" page > but it seems that "bountys" can be set only by a developer. Did you > already considered opening sub-project related donation for public. And > probably some voting system can also be very useful. > Anyway, a main question: how can I make a donation for a hammer > improvement, e.g. compression or dedupe? The names on the bounty page are added as people want to do it - the money amounts are up to the person adding it, and you don't have to be a developer. It's a wiki, so you can add your own name there too. (Make sure there's contact information, so if/when a project is done, you can be reached.) And, thanks!
Re: chlamydia inconsistency? part III
On Fri, September 24, 2010 6:50 pm, PrzemysÅaw PaweÅczyk wrote: > Hi, > > I checked directory tree. Here's a screenshot: > http://pp.blast.pl/www.png/dfbsd/df_04.png > > The slices' sizes were suggested by DFBSD, I didn't touch them. > Are the values correct? The values are correct, but something ate up the space you have there. It looks like your total disk is 2G, which is pretty small overall. Have you been dumping files in root's home directory? Maybe the core files from those crashes? Something's eating up your space in /; finding that will fix your problem.
Re: chlamydia inconsistency?
On Fri, September 24, 2010 6:38 pm, PrzemysÅaw PaweÅczyk wrote: > 2) http://leaf.dragonflybsd.org/cgi/web-man?command=pkg_radd§ion=1 > Add the following line to /etc/settings.conf to fetch packages from the > European mirror: > BINPKG_BASE=http://chlamydia.fs.ei.tum.de/pub/DragonFly/packages > > What is going on with the server? What should I do? The man page is out of date. You can substitute any mirror that carries packages, if you want. > BTW.1. pkg_radd prints segmentation fault, see the > picture: http://pp.blast.pl/www.png/dfbsd/df_01.png This I've never seen before.
Re: Why did you choose DragonFly?
On Fri, September 24, 2010 9:49 am, Siju George wrote: > Oh thanks :-) > Hope I will get sounds from the VMs too on my hardware. So Iculd run a > Linux VM for flash ;-) I think multimedia/libflashsupport will work, so you can get your browser on DragonFly running it. I had success with it some time back, though it was finicky.
Re: Why did you choose DragonFly?
On Fri, September 24, 2010 6:28 am, Siju George wrote: > What I am looking forward to? > > 1) CARP implementation whereby I can run 2 systems on the same IP > > 2) Qemu support so I can make DragonFly my main Desktop hosting many > virtual machines in which I experiment new stuff Qemu builds and runs on DragonFly - 0.12.4 was building for pkgsrc-2010Q2. You should be able to use it now with a pkg_radd.
Re: Weird entry in ISO
On Fri, September 24, 2010 8:37 am, PrzemysÅaw PaweÅczyk wrote: > I know, and I would expect such answer. No offense please, but for how > long yet such attitude will prevail in Unix community? It lingers from > 80s of the last... Cenury of the last Millennium. ;-) The LiveDVD image (dfly-gui-*) comes with preinstalled packages, including a web browser. I don't think MC's on there but it should be easy to add. Except there doesn't seem to be one for 2.6 - the build for it must have not worked? The error you saw was probably from a pkg_install version check; you can rebuild/upgrade it locally, and then things should work. pkg_install recently had a version check introduced where other packages won't be installed if they were built with a newer version, so it has to be upgraded first.
Re: pkgsrc package builds for 2.8
On Thu, September 23, 2010 5:45 pm, Matthew Dillon wrote: > > :So, I expect to have pkgsrc-2010Q3 packages for 2.8 about a week after > 2.8 > :comes out, if all goes well. I'm not planning (unless 2.8 is delayed > :significantly) to build pkgsrc-2010Q3 on DragonFly 2.6, since it'll > :probably finish right as 2.8 comes out. > : > :If this is a problem for anyone, tell me. You can always build the > :packages yourself if you're staying on 2.6 for a while, but 2.8 looks to > :be so jam-packed I wouldn't want to wait. > > If the timing looks good we will wait for the build to finish before > releasing, and release with the 2010Q3 package set. If we're freezing in a week and then branch 2.8 on October 1st, which should be the same time as pkgsrc-2010Q3 is out, then I can start building immediately. It takes about a week for a complete build, and that gives another week before planned release to handle any problems (of which there always are some) that slow down the build. This could work out well. I'm making some assumptions - that I don't mangle the build, that the pkgsrc release isn't delayed - but what the heck, I feel lucky.
pkgsrc package builds for 2.8
The next release of pkgsrc, 2010Q3, is due out Oct. 1st. DragonFly 2.8 is going to be out soon after. I stopped the automatic builds of pkgsrc in the various places I'm building it, as I don't think there's going to be any changes to really catch at this point. So, I expect to have pkgsrc-2010Q3 packages for 2.8 about a week after 2.8 comes out, if all goes well. I'm not planning (unless 2.8 is delayed significantly) to build pkgsrc-2010Q3 on DragonFly 2.6, since it'll probably finish right as 2.8 comes out. If this is a problem for anyone, tell me. You can always build the packages yourself if you're staying on 2.6 for a while, but 2.8 looks to be so jam-packed I wouldn't want to wait.
Re: SMP (Was: Why did you choose DragonFly?)
On Mon, September 20, 2010 10:15 pm, Matthew Dillon wrote: > TMPFS becomes more viable with swapcache too. We have two bulk > pkgsrc building boxes. More than two even, but two that I regularly > use. One has a swapcache SSD (Pkgbox64) and one does not (Avalon). > There is a gulf of difference in overall system performance between > the two. The system requirements would be much higher, even needing > more disk spindles for reasonable performance, without > TMPFS/swapcache. That explains the noticable performance difference just logging in... I always just thought avalon was getting used for something else I didn't know about... Is there benchmarks around for swapcache? i.e. same hardware, same software task, with and without swapcache?
Re: Why did you choose DragonFly?
On Mon, September 20, 2010 3:33 pm, Samuel J. Greear wrote: > This mail is intended for the infrequent responders and lurkers on the > list just as much as the regular posters. > > What has drawn you to use the DragonFly BSD operating system and/or > participate in its development by following this list? Technical > features, methodologies, something about the community? I suspect the > HAMMER filesystem to be the popular choice, but what other features > affect or do you see affecting your day to day life as an > administrator, developer, or [insert use case here], now or in the > future? I've been following DragonFly because it represented an opportunity to work on the community portion of a BSD system. The DragonFly Digest lets me read and document what's going on; I'm surprised that nobody has done the same with any of the other BSDs, really, in the past... 7 years? Geez. There's so much BSD-oriented material happening and it gets drowned out by the Windows and Linux chatter - not because it's necessarily better, but just because there's so much of it. Oh, and the DragonFly community is made of wonderful people, too. I'm confident I could take a stumbling tour through Europe and at least a few people I've never met face to face would buy me a beer. Or vice versa.
Re: Interview Request
On Sun, August 29, 2010 4:17 pm, Guillermo Amaral wrote: > Hi guys, > > I wanted to see if there is a PR team in Dragonfly BSD I could get in > touch > with. I host "The BSD Show!"[1] and I'm looking for somebody willing to > introduce the project and promote any upcoming release. I can do it - I was on BSDTalk before, and it was fun. Let me know a time and date, and I'll get my data in order.
Re: Heads up: Binary packages updated
On Thu, August 26, 2010 2:22 am, Sascha Wildner wrote: > On 8/25/2010 21:04, Justin C. Sherrill wrote: >> My bad; I saw the build had concluded but the null mount where it's >> copied >> over (since that build happens on that same machine) wasn't set up. I'm >> moving the files over now; should be as expected in a little bit. > > Then next time it should be verified that all packages are really there > before announcing. I did check each directory; I must have missed it in the process or accidentally typoed into one of the full directories. Mistakes happen; I can't realistically start verifying my verifications. :) The package builds take days or weeks and happen on four different and separate machines which are frequently in use by other people for other things, and then have to move to another system for distribution; it's not straightforward. The details on the script I use to build it is here: http://www.shiningsilence.com/simplepbulk/ Suggestions to streamline this are welcome; I'm at the limit of my work capacity. (This is an open question to anyone; Sascha's already got his own workload.)
Re: Heads up: Binary packages updated
On Wed, August 25, 2010 8:36 am, Dennis Melentyev wrote: > Hi Justin, > > > The listing of Avalon's i368/2.7/stable/All: > http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.7/stable/All/ [snip] > Seems to be a little bit short... > Is it still in progress? Or am I waiting in a wrong place? My bad; I saw the build had concluded but the null mount where it's copied over (since that build happens on that same machine) wasn't set up. I'm moving the files over now; should be as expected in a little bit.
Heads up: Binary packages updated
The 'stable' links for binary packages on avalon now point at pkgsrc-2010Q2. This means pkg_radd will pull from a newer batch of packages. Watch out - some of the newer packages will have newer dependencies, so you may be in for some number of upgrades to use these newer binary packages. If you keep a /usr/pkgsrc to match those binary packages (and you should if you are using them), you'll want to update it to match pkgsrc-2010Q2, also. Change /usr/pkgsrc/CVS/Tag to have 2010Q2 in it and 'cvs update -dP' is one way to do it.
Re: Logo Usage Request
On Tue, August 24, 2010 4:35 pm, Jim Brown wrote: > I've managed to make a logo and integrate it with our own distribution of > AQEMU > that we will be using for the lab exam. See the following URL for a > screen capture: > http://sixshooter.v6.thrupoint.net/dfly/aqemu.png It isn't really a permissions thing as much as it is just a way for us to know where the logo's floating around. I don't see any problems with this. There's vector versions of the logo linked at the first item on the images page: http://www.dragonflybsd.org/images/ Specifically: http://www.dragonflybsd.org/images/DragonFly_BSD.eps http://www.dragonflybsd.org/images/DragonFly_BSD.svg http://www.dragonflybsd.org/images/DragonFly_BSD.ai You can create a 'clean' image from those files at any scale, if that helps.
Re: pkgsrc issues
On Sun, August 22, 2010 9:36 pm, Nikolai Lifanov wrote: > I don't seem to be able to update pkgsrc right now... > I need to rebuild nginx with flv support for a streaming project at > work. I would appreciate any help. If I recall correctly... The git repo of pkgsrc from dragonflybsd.org was originally a conversion from CVS; the NetBSD.org servers now actually have a git repo to pull from, but it has a different branch name - master, not vendor. See in your output - there's a 'master' branch, but no 'vendor'. > From git://git.dragonflybsd.org/pkgsrc > * [new branch] master -> origin/master > * [new branch] pkgsrc-2010Q1 -> origin/pkgsrc-2010Q1 > * [new branch] pkgsrc-2010Q2 -> origin/pkgsrc-2010Q2 > cd /usr/pkgsrc && git branch vendor origin/vendor > fatal: Not a valid object name: 'origin/vendor'. If you edit /usr/Makefile and change "vendor" to "master" the three times it appears, it should work. I am saying this without testing it...
pkgsrc 2010Q2 DragonFly 2.6/i386 2010-08-19 19:12
This is the i386/2.6/pkgsrc-2010Q2 build. x86_64 builds appear similar, with the bonus that multimedia/xine-lib and lang/ocaml are broken. If anyone wants to look at them, there's reports on http://avalon.dragonflybsd.org/reports/ . I haven't changed the /stable link on avalon so that pkg_radd downloads pkgsrc-2010Q2 packages yet, cause I'm an idiot and forgot to put in the con job to build i386/2.7 packages on avalon. Sorry! It'll be a few days yet. -- pkgsrc bulk build report DragonFly 2.6/i386 Compiler: gcc Build start: 2010-08-19 19:12 Build end: 2010-08-21 19:24 Full report: http://avalon.dragonflybsd.org/reports/i386/2.6/20100819.1912/meta/report.html Machine readable version: http://avalon.dragonflybsd.org/reports/i386/2.6/20100819.1912/meta/report.bz2 Total number of packages: 9657 Successfully built: 8716 Failed to build: 331 Depending on failed package: 262 Explicitly broken or masked: 296 Depending on masked package:52 Packages breaking the most other packages Package Breaks Maintainer - editors/emacs-snapshot85 mins...@netbsd.org lang/mono 29 kef...@netbsd.org multimedia/py-gstreamer0.10 22 pkgsrc-us...@netbsd.org lang/sun-jre6 20 pkgsrc-us...@netbsd.org net/gupnp-igd 18 pkgsrc-us...@netbsd.org x11/kdebase-workspace416 ma...@netbsd.org security/xmlsec1 10 pkgsrc-us...@netbsd.org x11/py-gnome2-desktop 9 pkgsrc-us...@netbsd.org graphics/libv4l6 tech-multime...@netbsd.org x11/lablgtk5 pkgsrc-us...@netbsd.org Build failures Package Breaks Maintainer - audio/buzztard 1 pkgsrc-us...@netbsd.org audio/gogo pkgsrc-us...@netbsd.org audio/liblastfm1 pkgsrc-us...@netbsd.org audio/libvisual0.2-plugins pkgsrc-us...@netbsd.org audio/taglib-extras1 pkgsrc-us...@netbsd.org benchmarks/iozonepkgsrc-us...@netbsd.org benchmarks/libmicro pkgsrc-us...@netbsd.org benchmarks/netperf pkgsrc-us...@netbsd.org benchmarks/randread pkgsrc-us...@netbsd.org biology/gromacs pkgsrc-us...@netbsd.org biology/rasmol pkgsrc-us...@netbsd.org cad/eagler...@netbsd.org cad/magicpkgsrc-us...@netbsd.org cad/tnt-mmtl dmcmah...@netbsd.org chat/jabberd2 1 e...@cirr.com chat/tircpkgsrc-us...@netbsd.org chat/zircon pkgsrc-us...@netbsd.org comms/asterisk16 jnem...@netbsd.org comms/libopensync-plugin-syncml di...@netbsd.org comms/mgetty+sendfax pkgsrc-us...@netbsd.org comms/modemd tsa...@netbsd.org comms/tn3270 pkgsrc-us...@netbsd.org converters/help2man1 ar...@arved.at cross/avr-libc wennm...@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-msdosdjgpppkgsrc-us...@netbsd.org databases/mysqlccpkgsrc-us...@netbsd.org databases/openldap-smbk5pwd g...@netbsd.org databases/sqlite3-tclpkgsrc-us...@netbsd.org devel/electric-fence pkgsrc-us...@netbsd.org devel/elfsh pkgsrc-us...@netbsd.org devel/gtlpkgsrc-us...@netbsd.org devel/guile-gnomeg...@netbsd.org devel/java-subversionpkgsrc-us...@netbsd.org devel/libFoundation2 pkgsrc-us...@netbsd.org devel/libcompizconfig 5 pkgsrc-us...@netbsd.org devel/libscsi 2 pkgsrc-us...@netbsd.org devel/libstatgrab 1 pkgsrc-us...@netbsd.org devel/libthrift5 tonne...@netbsd.org devel/netbsd-iscsi-lib 2 a...@netbsd.org devel/omake pkgsrc-us...@netbsd.org devel/php-li
pkgsrc 2010Q2 status
The binary build of pkgsrc-2010Q2 is almost done. Packages for 2.6 on i386 and x86_64 are done and uploaded: http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.6/pkgsrc-2010Q2/All/ http://avalon.dragonflybsd.org/packages/x86_64/DragonFly-2.6/pkgsrc-2010Q2/All/ Packages for 2.7/x86_64 are most of the way through uploading; it should finish in the next day or so. http://avalon.dragonflybsd.org/packages/x86_64/DragonFly-2.7/pkgsrc-2010Q2/All/ Packages for 2.7/i386 are only just getting started, because I was having trouble with devel/gettext-base. It turned out that it wouldn't build with multiple MAKE_JOBS set, so it'll probably be at least several days before that completes. When it does finish, it will be here: http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.7/pkgsrc-2010Q2/All/ If you want to see reports on the various builds: http://avalon.dragonflybsd.org/reports/ (Look for the 'meta' report in each directory, sorted by arch, version, and date; e.g. http://avalon.dragonflybsd.org/reports/i386/2.6/20100805.2342/meta/report.html ) If anyone wants to tackle the top failures causing failures in other packages, it'd help... For upgrading: You can manually set pkg_radd to download from these links now, or you can wait until they're all completely uploaded to avalon, and I'll change the default links from 2010Q1 to 2010Q2 and you can download the newer packages automatically. pkg_chk or pkgin should work for upgrades, though setting them up for a binary upgrade is more than I'm going to document here. (mostly cause I don't know it off the top of my head.) Make sure your local /usr/pkgsrc/ is also pkgsrc-2010Q2 in case you have to build from source.
Re: Abnormal termination of greeter - cause is libX11 version
On Sun, August 1, 2010 7:34 pm, Pierre Abbat wrote: > I'm using git; there's a command "git checkout vendor" in /usr/Makefile. > Should I change that to "git checkout pkgsrc-2010Q1"? I don't know if the branches are carried through to the git repo. If it isn't, you will need to either switch to CVS to make sure you have the same version, or stick to building from source for everything. There isn't a collection of binary packages that tracks the bleeding edge of pkgsrc.
Re: Abnormal termination of greeter - cause is libX11 version
On Sat, July 31, 2010 11:58 pm, Pierre Abbat wrote: > I'd also like to reinstall vlc, but it's not in pkgin, and the version in > pkgsrc tries to install the libraries for kde4, which messes up my pkgin > packages. How do I downgrade pkgsrc to match pkgin? The version of pkgsrc you have installed is shown in whatever tag it's against - /usr/pkgsrc/CVS/Tag contains the tag. It should be pkgsrc-2010Q1 to make sure that when you build manually, you're building the same versions as what pkgin is downloading from avalon. If it's not, you can manually make it match and then update with setenv CVSROOT anon...@anoncvs.netbsd.org:/cvsroot setenv CVS_RSH ssh cd /usr cvs -q update -dP You can also delete /usr/pkgsrc and restore it with exactly the version you want with: setenv CVSROOT anon...@anoncvs.netbsd.org:/cvsroot setenv CVS_RSH ssh cd /usr cvs -q checkout -rpkgsrc-2010Q1 -P pkgsrc (notice only the last line is different.) If there's no tag, you're building from the bleeding edge of pkgsrc, which will get you the newest versions but also the newest issues, and is very likely the cause of these version mismatches. I would advise: - Making sure you have pkgsrc-2010Q1 as your /usr/pkgsrc/ - Make sure that pkgin is pointing to the right repository of files on avalon. 2.7 should show in the path, since you are running 2.7. You should be able to build everything at that point. (Look at pkg_rolling-replace if you want something to run through every option for you.) I am working on new pkgsrc-2010Q2 binaries, but it will be at least a few days before those are available, and I'll send out an announcement when they are. When they are available, do as before: make sure your local /usr/pkgsrc is updated to that release, and I'll mention when the "/stable/" link for pkgin is updated to point at packages with that newer release. You mentioned before that you are downloading 2.6 packages on a 2.7 system. That can work right now, but it's better to match exactly. Look at the path set for pkgin.
Re: Abnormal termination of greeter - cause is libX11 version
On Fri, July 30, 2010 9:14 am, Pierre Abbat wrote: > Correction: kwrite is expecting version 6.2.0, but the version that exists > is > 6.3.0. I made a symlink and kwrite came up. So does the greeter. Could > someone recompile kdelibs with 6.3.0 in the pkgin repository? What version of kdelibs and (whatever package contains) kwrite is installed? 3.5.10 is what's on avalon, where these probably came from, and they should match - they were built together. I wonder if packages got mixed from master and a release, somehow.
Re: Abnormal termination of greeter
On Fri, July 30, 2010 1:12 am, Krzysztof Langer wrote: > Usually the problem was with png, atk and glib -> those were out-of-date > and could not be updated with out deleting most gnome stuff (in the end > you had to reinstall all apps or even DFBSD). > > All this started after redirecting vendor to master in Makefile. Stick to the quarterly releases of pkgsrc whenever possible - going to master for pkgsrc means that you could potentially be trying to build packages right in the middle of a transition from one supporting lib to another. png, for instance, is required by thousands of packages. Quarterly releases should have a clean dependency list so you don't end up needing, say, jpeg-7 and jpeg-8 at the same time.
Re: Abnormal termination of greeter
On Thu, July 29, 2010 10:41 pm, Matthew Dillon wrote: > > : > :On Thursday 29 July 2010 21:06:38 Samuel J. Greear wrote: > :> Upgrade to master? full pkgsrc upgrade? What did you upgrade and from > :> what version(s) to what version(s)? > : > :Full pkgin upgrade. I updated a few days ago. How do I find the version > number > :of the repository? > : > :Pierre > > There could be an issue with the pkgsrc branch being used for the > automatic pkgsrc builds, I haven't gone through them all to determine > what branch they are building from recently. I'm pulling from pkgsrc CVS for now, which should be good. I know git is faster, but the various git repos of it (ours and the recent netbsd one) have had some issues.
Re: Abnormal termination of greeter
On Thu, July 29, 2010 9:48 pm, Pierre Abbat wrote: > On Thursday 29 July 2010 21:06:38 Samuel J. Greear wrote: >> Upgrade to master? full pkgsrc upgrade? What did you upgrade and from >> what version(s) to what version(s)? > > Full pkgin upgrade. I updated a few days ago. How do I find the version > number > of the repository? Where is pkgin configured to get packages from? I assume it's avalon.dragonflybsd.org, in which case the file path will tell you what DragonFly version and what pkgsrc release, at least that you built from most recently - the version you were at originally will depend on where you downloaded from at that time.
Re: Is it time to dump disklabel and use GPT instead?
On Thu, July 29, 2010 7:56 pm, elekktrett...@exemail.com.au wrote: >> Yes, it's students-only. Don't wait! Start now. It'll be difficult, >> but >> nothing worthwhile is ever easy. > > So I have to be a uni student or something like that? Yes. http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_eligibility Given that's it's going to be a year until the next one, I wouldn't wait on any work you may want to do; a new GPT editor could be finished in less time, I would guess.
Re: Is it time to dump disklabel and use GPT instead?
On Tue, July 27, 2010 10:55 pm, elekktrett...@exemail.com.au wrote: >> Also, if Linux wants to import *BSD's block devices, >> that's >> a Linux problem, not *BSD's. > > I think that "some" Unix interoperability should be a long term goal for > any Unix system. When you have a recognized standard like GPT, using it > seems to be the right thing to do, instead of developing another solution > that is incompatible with everything else on the market. You're not going > to get Linux to change because of BSD, it's the other way around. At least > in regards to interoperability. Technical merit, maybe. > > I might signup for GSoC 2011. Do I have to be a student? Yes, it's students-only. Don't wait! Start now. It'll be difficult, but nothing worthwhile is ever easy.
Re: can't install audacity
On Fri, July 23, 2010 12:48 am, Pierre Abbat wrote: > I tried with pkgin and got this: > 2 packages to be installed: wxGTK24-2.4.2nb16 audacity-1.2.6nb4 (7026K to > pkg_add: no pkg found for 'jpeg>=8nb1', sorry. Could it be pkgin has an out of date index? jpeg-8nb1 is there, and audacity is there but it's version 1.2.6nb5.
Re: The most supported X desktop for DragonFly
On Mon, June 21, 2010 3:36 pm, Dennis Melentyev wrote: > Can you share your experience with your preferred WM/Desktop? > Please, do not discuss pros'n'cons of them. I'm looking for something like > "I'm happy with XYZ except for feature zyx." I've installed Windowmaker and liked it, but I'm wierd. The best thing in terms of pkgsrc, in my experience, is to install a quarterly release. Check it out into /usr/pkgsrc/: setenv CVSROOT anon...@anoncvs.netbsd.org:/cvsroot setenv CVS_RSH ssh cd /usr cvs -q checkout -rpkgsrc-2010Q1 -P pkgsrc When you need to go to the next release, just edit /usr/pkgsrc/CVS/Tag and then: cvs -q update -dP Since the binary package builds are also using the quarterly releases, you can use pkg_radd without conflict. (As long as you are on the same quarterly release) You can pkg_radd something, and then switch to building from src when it's something that's restricted from distribution in binary form. pkg_rolling-replace also works for upgrading from source. I used that when going to pkgsrc-2009Q3 to pkgsrc-2010Q1, and upgrading took maybe a few hours. The hardest part was that a package name had changed, so I had to manually remove and readd.
Re: configure network and usb into qemu
On Sun, June 13, 2010 12:41 pm, dark0s Optik wrote: > I've installed DragonFly BSD in qmeu 0.12. > Now I want configure usb pendrive and network: > 1) How can I configure DragonFly network in qemu. > 2) How can I mount usb when DragonFly is into qemu. Make sure qemu is running with a network device emulated and attached to a real network device, and then it should show up normally to the DragonFly system and be configured just like a real network card. Same for the USB device - you need to make qemu pass the USB connection from the real system to the virtual one, and then treat as if it was real on the DragnonFly system. I haven't run qemu in a while, so I can't tell you the correct syntax off the top of my head for creating virtual network/passing through USB.
Re: mounting pendrive
On Sat, June 12, 2010 3:26 am, dark0s Optik wrote: > How can I mount my pendrive into dragonflybsd? Stick it in an available slot. Either the console or dmesg (type "dmesg") will show what device it comes up as - probably /dev/da8. Mount that device path - 'mount -t msdos /mnt /dev/daX' (I'm assuming it's a dos-formatted drive) The files should be available under /mnt. Be sure to 'umount /mnt' to unhook it before removing it from the computer.
Re: dragonfly installation into virtualbox
On Sat, June 12, 2010 3:36 am, dark0s Optik wrote:
> I tried to launch dragonfly x86 2.6.3 installation into virtualbox
> 3.2, but it crash.
> The output is:
>
> Debugger("panic"):
> stopped at 0xc0537b3c movb $0, 0xc070fd34
>
> How can to install dragonfly into virtualbox?
Try a different version of Virtualbox, or maybe a different emulator - it
seems like every third release of Virtualbox doesn't work for running
DragonFly, and then it does.
Re: DragonFly 64-bit stability
On Fri, June 11, 2010 2:36 am, Francois Tigeot wrote: > Yeah, I don't believe Postgres is to blame either. > During the pkgsrc build, many make instances were also dying with signal > 11. > > Every time I have tested the amd64/x86-64 DragonFly port, I found out this > segfault problem was a constant. I don't see signal 11 errors on any of the failed builds for x86_64 that I've been doing as bulk builds. (wandering through here for example) http://avalon.dragonflybsd.org/reports/x86_64/2.7/20100611.1041/meta/report.html Has this happened on more than one x86_64 machine? It's strange.
Re: DragonFly 64-bit stability
On Thu, June 10, 2010 4:32 pm, Francois Tigeot wrote: > Installing applications from pkgsrc went well. > > Unfortunately, running Postgres is a different matter: > # /usr/pkg/etc/rc.d/pgsql start > Starting pgsql. > seg-fault accessing address 0x58 rip=0x80077037d pid=20186 > p_comm=pg_ctl Segmentation fault Is this from a prebuilt binary or one that you compiled yourself? It may be worth building locally if you did not before. Otherwise: http://www.postgresql.org/support/submitbug
Re: DragonFly 64-bit stability
On Wed, June 9, 2010 4:52 am, Francois Tigeot wrote: > I'm thinking of upgrading one server from 2GB to 6GB of memory. > > Since the regular DragonFly/i386 version will not be able to fully use it, > I'm > also considering upgrading the OS to Dragonfly/x86-64. > > The machine is mainly running Postgres, Apache and Ruby (fast-cgi) for use > with a Ruby-on-Rails application. > > What is your experience with the 64-bit version ? Is it now stable enough > to be used in a server ? There's rarely some difference in what stuff from pkgsrc compiles on x86_64 vs. i386, though this is usually not because of DragonFly. A way to check would be looking at the reports on avalon: http://avalon.dragonflybsd.org/reports/ - look at the meta/ directory in each report. Postgres, apache, and ruby build fine going on a quick browse...
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Sun, June 6, 2010 1:49 pm, Matthew Dillon wrote: >Let me make this clear. We need to have basic dns utilities in the >system base that are NOT dependent on the bind or any other dns serving >package being installed. > >The whole point is to give users the ability to pkg_remove bind and > pkg_add >something else and not have it break core system utilities. If there was a "bind_utilities" package, or something like that, that installed the needed tools but not BIND, would that be OK? I'd really like to shift maintenance work on third-party software out to where it's already done (pkgsrc). I'd also like to have cake, and eat it too.
Re: HEADS UP: BIND Removal. Short instructions for migration to pkgsrc-BIND
On Sun, June 6, 2010 5:12 am, Jan Lentfer wrote: > Jan Lentfer schrieb: >> After another discussion I have decided to do the following: >> I will only remove BIND from base, no ldns and drill import. So anyone >> wanting to have either of the both will have to install them from pkgsrc >> (before updateing their world, I would recommend). >> >> We will see until next release how we will proceed with this. I prefer >> to just leave it this way and add pkgsrc-BIND to the Live-CD. > > Due to public demand I have now also committed ldns and drill. Does this mean that we now have a live CD that contains BIND from pkgsrc (and so has host, dig, nslookup, etc) _and_ the lnds/drill tools? The whole point of Jan's work was making it so we have less third-party code to update in base, I thought. My understanding is that nobody should be without the normal BIND tools - they'll just be from the pkgsrc package. It would come on the CD/DVD. If you happened to have an older (2.5 -> 2.7) system that was upgraded to remove BIND, it's fixable with 'pkg_radd bind96', rather than needing these additional tools. Someone correct me if I'm not describing reality.
Re: which pkgsrc version do I get via git?
On Fri, May 28, 2010 3:03 am, Chris Turner wrote: > Justin C. Sherrill wrote: >> On Thu, May 27, 2010 3:48 pm, Chris Turner wrote: >> >> >>> will submit PR eventually.. >> >> Please do it - having a bunch of patches for the pkgsrc people won't >> take >> long, and that's 90 packages that would now build for 2.6, 2.7, i386, >> and >> x86_64, so it's useful 360 times over. > > I'll make it a project to get my pkgsrc fixlets in this weekend - > fwiw I don't think the error is the same on gstreamer 64bits - > > will verify > > (that the bug was different on i386 - don't have a 64 bit station and > probably wont for some time) The build reports on avalon will get you to the error messages - for example: http://avalon.dragonflybsd.org/reports/x86_64/2.7/20100526.1040/gstreamer0.10-0.10.28/build.log http://avalon.dragonflybsd.org/reports/i386/2.7/20100527.0630/py26-gstreamer0.10-0.10.18/configure.log Go to http://avalon.dragonflybsd.org/reports/ and work down from there.
Re: which pkgsrc version do I get via git?
On Thu, May 27, 2010 3:48 pm, Chris Turner wrote: > will submit PR eventually.. Please do it - having a bunch of patches for the pkgsrc people won't take long, and that's 90 packages that would now build for 2.6, 2.7, i386, and x86_64, so it's useful 360 times over. If those patches go in and SJG's patch for kde4-libs works out, we'd have no packages left that caused significant dependency breakage - they'd all be in the single digits. That would be wonderful! And possibly unprecedented, at least recently.
Re: which pkgsrc version do I get via git?
On Thu, May 27, 2010 7:14 am, Max Herrgård wrote: > I don't know how to fix it though, but it would be good to have it > fixed. This gstreamer breaks lots of packages in the bulk build. > http://avalon.dragonflybsd.org/reports/x86_64/2.7/20100526.1040/meta/report.html Seconded; gstreamer is one of the worst "offenders" right now in terms of dependent package breakage. It's the same on 2.6,2.7, i386, and x86_64. Dave Shao has identified the problem: http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=43082 It's fixed by using a newer gcc. I assume we're going to want to upgrade gcc, though that may cause issues in other places.
Re: swapcache Setup
On Mon, May 24, 2010 4:42 pm, Matthew Dillon wrote: > For a manufacturer-fresh SSD configuring only 32G out of the 40G > leaves 8G which the SSD firmware will use to enhance its wear-leveling > algorithms, improving the overall life of the SSD. What's the wear rate you've seen on the machines with SSD that you set up? (assuming that the SSDs are still in there and you've been tracking overall I/O) I recall that the wear rate was comfortingly low.
Re: Serious issue with HTTP redirect from dragonflybsd.org to www.dragonflybsd.org
On Thu, May 20, 2010 8:54 am, Daniel Bond wrote: > Hi, > > when redirecting from http://dragonflybsd.org to > http://www.dragonflybsd.org, the PATH-part of the URI is appended to > the TLD. > IE: 'http://dragonflybsd.org/mirrors' redirects to > 'http://www.dragonflybsd.orgmirrors' As I recall, the reason for the setup is because of something with mail, so it couldn't just be aliased directly. In any case, there's probably just a missing '/' in the redirect. This is I think happening on crater, so Matt would have to adjust it.
Re: problem with system freeze
On Tue, May 18, 2010 5:15 pm, Goetz Isenmann wrote: > Any ideas, what I could do before or after it happens the next time, > that might give my some info what's going on? The same problem on two different architectures makes me think it's the one thing that hasn't changed: the hardware. Is there anything else connected to the computer that could be disconnected? Perhaps there's a BIOS setting around USB or some video setting that may change things?
Re: which pkgsrc version do I get via git?
On Tue, May 18, 2010 10:59 am, Siju George wrote: > I guess the packages that get installed using pkg_radd are built from > pkgsrc-stable? Yes - pkgsrc-2010Q1 is the current build.
Re: which pkgsrc version do I get via git?
On Tue, May 18, 2010 10:59 am, Siju George wrote: > I guess the packages that get installed using pkg_radd are built from > pkgsrc-stable? Yes - pkgsrc-2010Q1 is the current build.
[HEADS UP] pkg_radd on 2.3 and older systems
If you have a system older than 2.4, pkg_radd uses an old path to find files. Applying the changes here: http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/3d62c9e33361b5901e858332066162cc93afc27b will make it work with the current layout, and it means I can get rid of the old top level links, which I'll do momentarily. (I figure this only affects a few people running older systems, who may have changed the path already anyway...)
Re: starting Apache
On Sun, May 16, 2010 6:24 am, Sascha Wildner wrote: > Yeah, if RCD_SCRIPTS_DIR isn't set in /usr/pkg/etc/mk.conf, then > /etc/rc.d should be the default. It seems that maybe we should ship with /etc/rc.d set by default. I don't recall if there was discussion of this before. People will still have to enable it via rc.conf anyway.
