Re: Finding an illegal instruction in gnucash/guile

2005-08-07 Thread Vasil Dimov
On Sat, Aug 06, 2005 at 09:49:36PM +1000, Peter Jeremy wrote: > ... > scratch with different CPUTYPE and/or CFLAGS? (I'm currently using > CPUTYPE=athlon-xp and CFLAGS=-O -g). Hmmz, CFLAGS=-O -g, what do you expect from this combination? gcc(1): Without `-O', the compiler's goal is to reduce the

pthreads problem

2005-08-07 Thread Gerhard Hoffmann
Hi Phil, I think the easiest solution for your problem is something like this: #include #include volatile unsigned long len = 0; pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER; pthread_cond_t cond = PTHREAD_COND_INITIALIZER; static void cleanup_handler(void *arg) { (void)pt

Re: How to do proper locking

2005-08-07 Thread Hans Petter Selasky
On Saturday 06 August 2005 18:02, Ian Dowse wrote: > In message <[EMAIL PROTECTED]>, Hans Petter Selasky writes: > >Yes, you are right, but the problem is, that for most callback systems in > > the kernel, there is no mechanism that will pre-lock some custom mutex > > before calling the callback.

Re: Finding an illegal instruction in gnucash/guile

2005-08-07 Thread Peter Jeremy
On Sun, 2005-Aug-07 11:07:16 +0300, Vasil Dimov wrote: >On Sat, Aug 06, 2005 at 09:49:36PM +1000, Peter Jeremy wrote: >> >... >> scratch with different CPUTYPE and/or CFLAGS? (I'm currently using >> CPUTYPE=athlon-xp and CFLAGS=-O -g). > >Hmmz, CFLAGS=-O -g, what do you expect from this combinatio

Model device driver / Newbus

2005-08-07 Thread Alex Burke
Hi, I want to try writing a driver for an MCA card. I am just wondering if there is any skeleton driver (preferably a bus like PCI), and also whether the newbus framework is used for MCA drivers. What is the preferred method of writing drivers now? Thanks, Alex J Burke. _

Soc ssh fs: dummy Fuse module aviable for review

2005-08-07 Thread Csaba Henk
Hi! I am Csaba Henk, Google Summer of Code participant at FreeBSD. I am to create an ssh based virtual networking filesystem, by now that boils down to porting Fuse (http://fuse.sourceforge.net) (doing so brings much more to FreeBSD than having an ssh based filesystem). Now I want to tell you a

unionfs umount problem

2005-08-07 Thread Justin Hopper
Hello, If this question belongs on freebsd-fs, let me know and I'll repost. I had emailed a question to the list a few months ago, asking what the current status was on unionfs and whether it was now somewhat stable, since the man page still reports it as broken and without a maintainer. Some peo

Re: Model device driver / Newbus

2005-08-07 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Alex Burke <[EMAIL PROTECTED]> writes: : Hi, : : I want to try writing a driver for an MCA card. : : I am just wondering if there is any skeleton driver (preferably a bus : like PCI), and also whether the newbus framework is used for MCA : drivers. What

Re: Model device driver / Newbus

2005-08-07 Thread Julian Elischer
M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Alex Burke <[EMAIL PROTECTED]> writes: : Hi, : : I want to try writing a driver for an MCA card. : : I am just wondering if there is any skeleton driver (preferably a bus : like PCI), and also whether the newbus framework is use

Re: Sound problem

2005-08-07 Thread Aleksander (Andy) Rozman
On Tuesday 02 of August 2005 11:03, ALeine wrote: > You may want to set the kernel variable hw.snd.pcm0.vchans to 0 > and tune other hw.snd.* kernel variables with sysctl(8). > Hi ! Problem is that if I set vchans to zero, sound stops working altogether under KDE. I have some weird mother board w

FreeBSD port of ICC 9.0 wanted!?

2005-08-07 Thread Tetsuji \"Maverick\" Rai
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I installed ICC 8.1(Intel C++ compiler) for Linux on FreeBSD in ports/lang/icc and it's working fine. However Intel has released version 9.0 (I'm not sure how much performance has been improved, though) So I tried to install it on FreeBSD box (virt

Re: [RFC] Bumping ufs.dirhash_maxmem to a larger value?

2005-08-07 Thread Borja Marcos
So why not make the determination of "dirhash_maxmem" the result of some calculation(s) that takes into account RAM size, etc ? The obvious lesson here is that picking a number to be a limit based on the current size of machines fails the test of time. I think that changing it now with