Date: Sun, 19 Jun 2005 11:18:48 +0200 From: Thomas Wintergerst <Thomas.Wintergerst@nord-com.net> To: Cian Hughes <cianlists@cian.ws> Cc: freebsd-isdn@freebsd.org Subject: Re: Problem with C4B on FreeBSD-Stable Message-ID: <42B53878.2020407@nord-com.net> In-Reply-To: <BD18D7E5-79CC-41B5-9755-6D31C5286CA9@cian.ws> References: <7112CBFA-724E-4846-AA2E-1EFBC4B49CE2@cian.ws> <475744B9-48D9-474F-96E9-4C48869FD970@cian.ws> <42B3DFF6.3070705@nord-com.net> <BD18D7E5-79CC-41B5-9755-6D31C5286CA9@cian.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Cian, Cian Hughes wrote: > Ok, well i've done lots of messing around since i last wrote anything, I > have cvsup'ed my src to FreeBSD-Current, and made a new patchset for > c4b, with only some minor changes to the Makefiles it all compiled, and > I have asterisk talking to my AVM B1 through chan_capi.so, which is very > nice, I have got one vmcore from a panic (my old kernel did not have > debug flags enabled), unfortunately it weighs in a 132MB so I haven't > attached it, I think it's usefulness may be limited, someone else with > ssh access to the box thinks they may have accidentally cvsuped src-all > since I compiled the kernel last week, so I think that the panic may > have been due to source synchronisation issue, to be safe I actually > dumped /usr/src & /usr/obj and started again, my reason for not posting > again is that the patch & compile of everything (world included) only > finished at 11.30pm last night. For the moment I'll put the Sun compile O.K., so we'll see what happends next on your system. > on Hold, and concentrate on making a new patchset for FreeBSD-Current. > How hard do you think it would be to get c4b incorporated into > FreeBSD-Current, this patching lark is a bit of a pain. You are right. We are working on this topic. But during the current code freeze it will not be possible. -- Gruss, Thomas Wintergerst
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B53878.2020407>