Re: open of /dev/speaker for writing: Device not configured
Vladimir Mitiouchev wrote: Hi! I'm trying to run beep. beep: open of /dev/speaker for writing: Device not configured I haven't found any modules that looks like speaker driver.. Hm, seems Joerg removed it in March 2005.. Sascha -- http://yoyodyne.ath.cx
Re: open of /dev/speaker for writing: Device not configured
Sascha Wildner wrote: Vladimir Mitiouchev wrote: Hi! I'm trying to run beep. beep: open of /dev/speaker for writing: Device not configured I haven't found any modules that looks like speaker driver.. Hm, seems Joerg removed it in March 2005.. http://www.dragonflybsd.org/cvsweb/src/sys/dev/sound/isa/i386/spkr/Attic/spkr.c Sascha -- http://yoyodyne.ath.cx
Re: make buildworld crash, unwind.h
Vladimir Mitiouchev wrote: Hi! losalamos:/usr/sources/src$ uname -a DragonFly losalamos 1.7.0-DEVELOPMENT DragonFly 1.7.0-DEVELOPMENT #0: Mon Nov 27 18:50:14 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/sources/src/sys/LOSALAMOS i386 rm -rf /usr/sources/src. rm -rf /usr/obj cvsup, cvs... did you run cvs co -P ? cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
Re: make buildworld crash, unwind.h
On Thu, Dec 07, 2006 at 10:37:52AM -0500, Justin C. Sherrill wrote: On Thu, December 7, 2006 5:30 am, Simon 'corecode' Schubert wrote: no, you need cvs -d /usr/sources/dragonfly_cvs checkout -rDragonFly_Preview -P src -P == prune empty directories When is cvsup appropriate vs. cvs? Using cvsup is what we have documented. It appears that he is using cvsup to get the repo, and usung cvs to update his src/ tree. --Peter pgp84AHQLVLr6.pgp Description: PGP signature
Re: make buildworld crash, unwind.h
On Thu, December 7, 2006 3:39 pm, Peter Avalos wrote: When is cvsup appropriate vs. cvs? Using cvsup is what we have documented. It appears that he is using cvsup to get the repo, and usung cvs to update his src/ tree. Should we be describing that in documentation? I see both techniques in use, but I haven't seen a reason one should be described over the other. (I always just used cvsup.)
Re: make buildworld crash, unwind.h
Justin C. Sherrill wrote: On Thu, December 7, 2006 3:39 pm, Peter Avalos wrote: When is cvsup appropriate vs. cvs? Using cvsup is what we have documented. It appears that he is using cvsup to get the repo, and usung cvs to update his src/ tree. Should we be describing that in documentation? I see both techniques in use, but I haven't seen a reason one should be described over the other. (I always just used cvsup.) I love cvsup, but lately we DragonFly fans are completely dependent on a binary cvsup package because ezm3 won't compile. The obvious solution is to use csup, which is a cvsup-workalike written in C. It works flawlessly on FreeBSD and NetBSD but not (yet) on DFBSD because of the newer version of cvs that we use. I've emailed the csup guru (Maxime Henrion) about updating csup, but I've had no answer from him. I hope Maxime is in good health and is just too busy to deal with csup, but I really don't know. Anyone who is interested in updating csup can get the sources here: http://www.mu.org/~mux/csup.html#download
Re: make buildworld crash, unwind.h
On 12/7/06, walt [EMAIL PROTECTED] wrote: Justin C. Sherrill wrote: On Thu, December 7, 2006 3:39 pm, Peter Avalos wrote: When is cvsup appropriate vs. cvs? Using cvsup is what we have documented. It appears that he is using cvsup to get the repo, and usung cvs to update his src/ tree. Should we be describing that in documentation? I see both techniques in use, but I haven't seen a reason one should be described over the other. (I always just used cvsup.) I love cvsup, but lately we DragonFly fans are completely dependent on a binary cvsup package because ezm3 won't compile. The obvious solution is to use csup, which is a cvsup-workalike written in C. It works flawlessly on FreeBSD and NetBSD but not (yet) on DFBSD because of the newer version of cvs that we use. I've emailed the csup guru (Maxime Henrion) about updating csup, but I've had no answer from him. I hope Maxime is in good health and is just too busy to deal with csup, but I really don't know. Anyone who is interested in updating csup can get the sources here: http://www.mu.org/~mux/csup.html#download FWIW, http://mu.org/~mux/csup-snap-20060318.tgz does the trick for me. My supfile is below: -- cut here -- *default host=cvsup.dragonflybsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress dragonfly-cvs-src -- and here -- -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.
Process for patch/build/install/modify/rebuild/reinstall
Greetings, I'm trying to make some code changes in the i810 X server version 6.9.0nb13 because of breakage. I'm trying to find the best/fastest way to: 1. modify code 2. build and install 3. test 4. uninstall 5. goto 1. This is the slow process I've been using: Modified mk.conf so only i810 X server is built # cd /usr/pkgsrc/x11/xorg-server Used pkgsrc to get sources # bmake fetch-list | sh 1. modify code # bmake patch I'm assuming this applies DragonFly patches to the Xorg sources. Correct me if I'm wrong. Make changes in /usr/pkgsrc/x11/xorg-server/work 2. build and install # bmake install 3. test 4. uninstall # bmake deinstall # bmake clean 5. goto 1. At first I thought I could modify code in the work directory and run bmake from /usr/pkgsrc/x11/xorg-server, but that didn't work. Please enlighten me with a better way. Thanks in advance! P.S. I use vi and am learning cscope without X. What non-X tools do other people use for source code browsing?
Re: Process for patch/build/install/modify/rebuild/reinstall
On Thu, 7 Dec 2006, [EMAIL PROTECTED] wrote: I'm trying to make some code changes in the i810 X server version 6.9.0nb13 because of breakage. I'm trying to find the best/fastest way to: I'd suggest you work against Xorg's official release. The monolithic 6.9 series is not maintained upstream. I think the code you need is Xorg's driver/xf86-video-intel (by the way Intel is really supporting this as open source :) There is some work on modualr Xorg in pkgsrc. I use it myself (and have for a very long time). I have committed a few things for DragonFly to Xorg source. I can help you with creating a xf86-video-intel package. I think it would be better to test against supported code versus trying to patch old obsolete and unmaintained code. Hope you get this fake@
