pthread, ElectricFence
Hi there! Since a cvsupdate and recompile some time ago, using ElectricFence with pthread programs got impossible. just linking the pthread lib and the efence lib to a simple small program causes a weird error: Fatal error 'Cannot create kernel pipe' at line ? in file /usr/src/lib/libc_r/uthread/uthread_init.c (errno = ?) Abort (core dumped) This was tested on diffrent machines (even the nearly newest stable) but still the same error. No idea what was changed to cause that error, but is there a way to solve my problem? (Not using efence is not a good solution as i tend to make allocation mistakes ;) ) Sperber To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant?
# [EMAIL PROTECTED] / 2003-01-12 21:33:32 -0800: > On Fri, Jan 10, 2003 at 10:48:46PM +0100, Roman Neuhauser wrote: > > # [EMAIL PROTECTED] / 2003-01-10 11:32:22 -0800: > > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > > Cc: [EMAIL PROTECTED] > > > > you sent me a copy again, please, don't do it. > > 1. I don't want one, I'll read your message on the list. > > Then make this clear -- YOU don't provide a Reply-to: or Followup-to:. > So Terry (and myself) aren't to blame. I *do* make it clear: 1. I *do* send out the MFT header, but the freebsd.org MTA's strip it. 2. I make my preference clear in the signature. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant?
# [EMAIL PROTECTED] / 2003-01-12 21:57:25 -0800: > David O'Brien wrote: > > On Fri, Jan 10, 2003 at 10:48:46PM +0100, Roman Neuhauser wrote: > > > # [EMAIL PROTECTED] / 2003-01-10 11:32:22 -0800: > > > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > > > Cc: [EMAIL PROTECTED] > > > > > > you sent me a copy again, please, don't do it. > > > 1. I don't want one, I'll read your message on the list. > > > > Then make this clear -- YOU don't provide a Reply-to: or Followup-to:. > > So Terry (and myself) aren't to blame. > > I guess he doesn't like it showing up in his mail logs, since if > it's via my ISP's mail server, the one to him directly bounces > anyway. Gotta wonder why anyone would care, if they never see the > thing anyway... 8-). No, that's not the reason. I just don't like getting cc's. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant?
In the last episode (Jan 13), Roman Neuhauser said: > # [EMAIL PROTECTED] / 2003-01-12 21:33:32 -0800: > > On Fri, Jan 10, 2003 at 10:48:46PM +0100, Roman Neuhauser wrote: > > > # [EMAIL PROTECTED] / 2003-01-10 11:32:22 -0800: > > > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > > > Cc: [EMAIL PROTECTED] > > > > > > you sent me a copy again, please, don't do it. 1. I don't > > > want one, I'll read your message on the list. > > > > Then make this clear -- YOU don't provide a Reply-to: or > > Followup-to:. So Terry (and myself) aren't to blame. > > I *do* make it clear: > > 1. I *do* send out the MFT header, but the freebsd.org MTA's strip it. Whoa. Who broke that? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant?
# [EMAIL PROTECTED] / 2003-01-13 11:49:15 -0600: > In the last episode (Jan 13), Roman Neuhauser said: > > # [EMAIL PROTECTED] / 2003-01-12 21:33:32 -0800: > > > On Fri, Jan 10, 2003 at 10:48:46PM +0100, Roman Neuhauser wrote: > > > > # [EMAIL PROTECTED] / 2003-01-10 11:32:22 -0800: > > > > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > > > > Cc: [EMAIL PROTECTED] > > > > > > > > you sent me a copy again, please, don't do it. 1. I don't > > > > want one, I'll read your message on the list. > > > > > > Then make this clear -- YOU don't provide a Reply-to: or > > > Followup-to:. So Terry (and myself) aren't to blame. > > > > I *do* make it clear: > > > > 1. I *do* send out the MFT header, but the freebsd.org MTA's strip it. > > Whoa. Who broke that? No idea. I'm slowly trying to resolve this with [EMAIL PROTECTED] -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
5.0 DP2 fixit.flp woes
The fixit.flp from the 5.0 DP2 cdrom appears to be unusable. When I attempt to use it after booting from kern.flp it comes up with errors of the form: fd0c: hard error reading fsbn 2528 of 2528-2530 (ST0 40 \ ST1 4 ST2 10 cyl 70 hd 0 sec 9) accompanied by ominous clicking noises from the floppy drive. === I have created the floppy using both fdimage on Windows NT and dd on FreeBSD. I've tried 3 different floppies. Booting into CURRENT as of January 16 2001 (old, I know) and trying: dd if=/dev/fd0.1440 of=/dev/null - No errors fdformat -v /dev/fd0.1440 - No errors cmp /dev/fd0.1440 fixit.flp - No errors fsck /dev/fd0.1440 gets "cannot read BLK 2552" and similar hard error as above. Mount the floppy on /mnt and try "find /mnt" - hard errors as above. "tar cvf test /mnt " # - hard errors as above === I realise that the superblock layout has changed within the last few months, so I booted up a CURRENT as of 20 October 2002. Now fsck /dev/fd0.1440 gives: cannot get disklabel for /dev/fd0.1440, inappropiate IOCTL for device however this may be because the kernel is slightly out of sync with fsck, I don't know. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: possible cpu_wait() / vm_waitproc() / MAC problem
On 12-Jan-2003 Matthew Dillon wrote: > While working on an MFC I noticed that sys/compat/svr4/svr4_misc.c > (in CURRENT) is calling cpu_wait() in svr4_sys_waitsys() instead of > vm_waitproc(). I believe it needs to call vm_waitproc(). Can anyone > say for sure? > > Also, in kern/kern_exit.c the wait code has this: > >#ifdef MAC > mac_destroy_proc(p) >#endif > > This appears to be missing from svr4_sys_waitsys() as well, also > in -current. Could someone confirm that? The svr4() wait code is just gross. We need to make it just pass a flag into wait1() IMO and have the svr4() implementation be a wrapper function. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: boot2 no longer displays a prompt
REPOST, previous message may have failed to get through. I put -z as an illegal option in /boot.config with the intention of disabling autoboot. The prompt is now displayed, but it does not allow any keyboard input and does not proceed any further. (*** don't try this unless you have a way of recovering /boot.config :-( ) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant ?
Roman Neuhauser wrote: > No, that's not the reason. I just don't like getting cc's. That's easily fixed: I recommend /usr/ports/mail/procmail. You can't expect people on a mailing list to tailor their MUA configuration to suit your choices. It's up to you to set up your own MUA and filters to cater to your own pickiness. - Rahul To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RE: possible cpu_wait() / vm_waitproc() / MAC problem
: : :On 12-Jan-2003 Matthew Dillon wrote: :> While working on an MFC I noticed that sys/compat/svr4/svr4_misc.c :> (in CURRENT) is calling cpu_wait() in svr4_sys_waitsys() instead of :> vm_waitproc(). I believe it needs to call vm_waitproc(). Can anyone :> say for sure? :> :> Also, in kern/kern_exit.c the wait code has this: :> :>#ifdef MAC :> mac_destroy_proc(p) :>#endif :> :> This appears to be missing from svr4_sys_waitsys() as well, also :> in -current. Could someone confirm that? : :The svr4() wait code is just gross. We need to make it just pass a flag :into wait1() IMO and have the svr4() implementation be a wrapper function. : :-- : :John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ :"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ Well, I would prefer to just fix the bug(s) for now, unless someone else wants to have a go at merging it. I have major work on vmapbuf() and friends that I need to do that I don't want to delay it too much longer. Does this patch look good? -Matt Matthew Dillon <[EMAIL PROTECTED]> Index: compat/svr4/svr4_misc.c === RCS file: /home/ncvs/src/sys/compat/svr4/svr4_misc.c,v retrieving revision 1.56 diff -u -r1.56 svr4_misc.c --- compat/svr4/svr4_misc.c 13 Jan 2003 00:28:57 - 1.56 +++ compat/svr4/svr4_misc.c 13 Jan 2003 20:09:38 - @@ -1377,12 +1377,15 @@ * to free anything that cpu_exit couldn't * release while still running in process context. */ - cpu_wait(q); + vm_waitproc(q); #if defined(__NetBSD__) pool_put(&proc_pool, q); #endif #ifdef __FreeBSD__ mtx_destroy(&q->p_mtx); +#ifdef MAC +mac_destroy_proc(q); +#endif uma_zfree(proc_zone, q); #endif nprocs--; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RE: possible cpu_wait() / vm_waitproc() / MAC problem
On 13-Jan-2003 Matthew Dillon wrote: > >: >: >:On 12-Jan-2003 Matthew Dillon wrote: >:> While working on an MFC I noticed that sys/compat/svr4/svr4_misc.c >:> (in CURRENT) is calling cpu_wait() in svr4_sys_waitsys() instead of >:> vm_waitproc(). I believe it needs to call vm_waitproc(). Can anyone >:> say for sure? >:> >:> Also, in kern/kern_exit.c the wait code has this: >:> >:>#ifdef MAC >:> mac_destroy_proc(p) >:>#endif >:> >:> This appears to be missing from svr4_sys_waitsys() as well, also >:> in -current. Could someone confirm that? >: >:The svr4() wait code is just gross. We need to make it just pass a flag >:into wait1() IMO and have the svr4() implementation be a wrapper function. >: >:-- >: >:John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ >:"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > Well, I would prefer to just fix the bug(s) for now, unless someone else > wants to have a go at merging it. I have major work on vmapbuf() and > friends that I need to do that I don't want to delay it too much longer. *nod* I've been meaning to merge the darn thing for a while now. > Does this patch look good? Sure. > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > Index: compat/svr4/svr4_misc.c > === > RCS file: /home/ncvs/src/sys/compat/svr4/svr4_misc.c,v > retrieving revision 1.56 > diff -u -r1.56 svr4_misc.c > --- compat/svr4/svr4_misc.c 13 Jan 2003 00:28:57 - 1.56 > +++ compat/svr4/svr4_misc.c 13 Jan 2003 20:09:38 - > @@ -1377,12 +1377,15 @@ >* to free anything that cpu_exit couldn't >* release while still running in process context. >*/ > - cpu_wait(q); > + vm_waitproc(q); > #if defined(__NetBSD__) > pool_put(&proc_pool, q); > #endif > #ifdef __FreeBSD__ > mtx_destroy(&q->p_mtx); > +#ifdef MAC > +mac_destroy_proc(q); > +#endif > uma_zfree(proc_zone, q); > #endif > nprocs--; -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Soundcard problems on laptop
Hi freebsd-hackers list, I'm new to this list, and first of all want to thank you all for such a nice system, it's my primary OS (in combination with Mac OS X). Secondly: I have sound card problems on my laptop (Celeron 850, bla bla bla). I get a strange message when I start the system : pcm0: irq 10 at device 31.5 on pci0 pcm0: unable to map IO port space device_probe_and_attach: pcm0 attach returned 6 Does anybody know this error? I tracked it down in the ICH driver in the kernel sources, and the error seems to be a pci manager error. Could someone give me some pointers how to fix this error, what's going wrong in the hardware, etc? (and no, this isn't an user problem, I want to fix the driver myself if needed). Thank in advance, Bernard van Gastel smime.p7s Description: S/MIME Cryptographic Signature
Re: boot2 no longer displays a prompt
In message <[EMAIL PROTECTED]> Dave Evans writes: : REPOST, previous message may have failed to get through. : : I put -z as an illegal option in /boot.config with the intention of : disabling autoboot. The prompt is now displayed, but it does not allow : any keyboard input and does not proceed any further. : : (*** don't try this unless you have a way of recovering /boot.config :-( ) I just committed a fix to this that should be in 5.0... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: sendmail: how to get the named of FreeBSD4.7 standards compliant ?
> Roman Neuhauser wrote: > > No, that's not the reason. I just don't like getting cc's. > > That's easily fixed: I recommend /usr/ports/mail/procmail. > > You can't expect people on a mailing list to tailor their MUA > configuration to suit your choices. It's up to you to set up your own > MUA and filters to cater to your own pickiness. Amen! Can we get back on topic now, please? :-) M -- Mark Murray iumop ap!sdn w,I idlaH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
kld && inetsw.pr_protocol overriding + old reuse
I'm interested in whether the following could be acomplished: there's KLD module, installing some new syscalls in the kernel, as well as installing new ``struct ipprotosw'' for some protocol or another(let's assume IPPROTO_UDP). Could we just add some code in the begging of the new protocol handler (counting, statistics , etc...) and call the old one after doing that. If possible, what should be the preparation for that last call ? Any help appreciated! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kld && inetsw.pr_protocol overriding + old reuse
Radoslav Vasilev wrote: > I'm interested in whether the following could be acomplished: > there's KLD module, installing some new syscalls in the kernel, as well as > installing new ``struct ipprotosw'' for some protocol or another(let's > assume IPPROTO_UDP). > Could we just add some code in the begging of the new protocol handler > (counting, statistics , etc...) and call the old one after doing that. If > possible, what should be the preparation for that last call ? > Any help appreciated! This can't really be done, without actually hacking over top of the location that contained the code associated with the previous symbol. The reason for this is that the input path sometimes ends up making direct calls, assuming that the protocol stack is stacked the way it's expected to be stacked (e.g. direct calls to routines that are in struct ipprotosw). If you need to hack over the function, you need a lot more knowledge of assembly language; it is occasionally useful for profiling an existing system. The usual reason for wanting to do this is to make TCP/IP connections that are invisible to the OS, in order to attempt to turn FreeBSD boxes into DDOS robots, without the knowledge of their owners. 8-|. If you have a specific reason for this, you can replace the entry points with explicit entry points for your own routines, that call the real (renamed) routines, indirectly, and then replace the pointers. This will work fine on systems which legitimately belong to you, and for which you are willing to recompile the kernel, in order to make your modules work. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kld && inetsw.pr_protocol overriding + old reuse
It is not very simple. However Netgraph/ng_socket.c does something similar. net_add_domain is called from ngs_mod_event(). However, it is not possible to remove this module because the feature to remove a domain is missing. switch (event) { case MOD_LOAD: /* Register protocol domain */ net_add_domain(&ngdomain); break; case MOD_UNLOAD: /* Insure there are no open netgraph sockets */ if (!LIST_EMPTY(&ngsocklist)) { error = EBUSY; break; } #ifdef NOTYET if ((LIST_EMPTY(&ngsocklist)) && (typestruct.refs == 0)) { /* Unregister protocol domain XXX can't do this yet.. */ if ((error = net_rm_domain(&ngdomain)) != 0) break; } else #endif error = EBUSY; break; I would be interested in this feature too ;-) However there is no reference counter within the protosw structure, neither within the domain structure. It seems to be difficult to remove them. Moreover, how can the domains, that require a "routing layer", be loaded ? rn_init is called only during the boot process in order to find the max_keylen = MAX(dom->dom_maxrtkey). Vincent Le Mardi 14 Janvier 2003 00:53, Radoslav Vasilev a écrit : > I'm interested in whether the following could be acomplished: > there's KLD module, installing some new syscalls in the kernel, as well as > installing new ``struct ipprotosw'' for some protocol or another(let's > assume IPPROTO_UDP). > Could we just add some code in the begging of the new protocol handler > (counting, statistics , etc...) and call the old one after doing that. If > possible, what should be the preparation for that last call ? > Any help appreciated! > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message