From owner-freebsd-hackers Sun Aug 6 6:24:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 4D0D737BABF; Sun, 6 Aug 2000 06:24:38 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id UAA72591; Sun, 6 Aug 2000 20:24:15 +0700 (NSS) (envelope-from semen@iclub.nsu.ru) Date: Sun, 6 Aug 2000 20:24:15 +0700 (NSS) From: Ustimenko Semen To: freebsd-hackers@FreeBSD.org, freebsd-current@FreeBSD.org Cc: fjoe@iclub.nsu.ru Subject: nullfs patch Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-177650955-965568055=:72320" Content-ID: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-177650955-965568055=:72320 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Hi! Here is a patch, it seems it fix some bugs in nullfs. At least i was able to make kernel on nullfs mounted filesystem. All results are welcome! Good luck! --0-177650955-965568055=:72320 Content-Type: APPLICATION/octet-stream; name="nullfs.diff.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: patch Content-Disposition: attachment; filename="nullfs.diff.gz" H4sICAZkjTkAA251bGxmcy5kaWZmANVae3PbuBH/W/kUSO4mkRTqLVmS06R1 YvnOc7blsRUnnZsbDk1CEmqK4PEhx82ln727eFCgRMlypr1OPbZMAVjsYrGP 3wL8wBcLHpA4vfVYRN2ER4zGh6TeCFLfn8Z1+D5rfLi5Jk7gZa3Y8Mxj0ymp uWtD8dleTmMexvVVX775WbVa3UVWOokYOUpnhHRJ6+CwMzjsDkm72Ww+q9Vq W+YsXaeBpDkgreFhb3DY7kiaav5HMO/1rYMDIr4SAr9x4iTMJedHZ2fjD/bx 6OT0YlQ+ty8+np2dXJ9fTCzyQj6TBU+D5MXad6CPUjdJI/qi8gZnrOkZWZCU pLj2dJ7wZUhs+7JcluMVcXURWmoGMmUeqcJHaMEcJfghRHctA+5RkHkZhhXB ZZOFO6fuHf3yGJOYu3eO50WkGjgLC2ZSjHAqUqVfkqnvzOLV+NSNKIhVxX9O wIOt/CWrLczduQMcQyeZwzOytxPiOYmzEkDRgFCUYQ/I562kCCPuAv023r+n PHHcxN/GHtfmLjyLpMwDzvBpCXNCUxgSeKr9d0zhf71Prwv4A6mTJNEe2gJy zRR+XB7EidpInAB3arWZTjRbG7+5c0XSPNUxXj/dMf7fDLMoZnX6bavTH+io VcpzR95fsblRffaclEiVfP78mdTIURynCxqTgIs1wQLB+DziwGpAPOI7DzSq Ix2pNvBfRMF2A1JuitV8Ey7S6feszqCjnWQvzpM5jSiYBEXOt+l0SqOYJJxM /TQGPTsxuafE48GrRBHhz9xZUnIzvrTfnx9d1sn7NCFJNk/ozGhcJ8dIQwyi u4Dfkzn86dnVyB2LKlTvoGN1hs1MvSzgsBvw+cZYsmFqetkoiZr/5uTavvlp NCmfjz9eTCZjjAvisbwIK7V3qPAFJizcc24RtFcpz1qYkEofDECeLDLtKc9r HJgQGkU8Qm8riSfy9vtkw9mmpCzmqAi/05qUTW/y6y+LjIwi2RCCnISW0b5R ODnhltUW7sawY3WbzXVjz6LA0zbl5OfJ+Oby8aWL+PLIvnSbbavb2nCG/STb uT3fI+Wfs0O7oF5QiPSC3UAveDrOCzZgXrt52OwdtgbbYV6nb3U72oaI/CBH gUtjwLnxofhe+lv5h4rPIVBrFq16m5Tf0+iO+vShQg4arUFj2AY8BsQ/nkSU vr8+PiRx5Dbih7ixYLGrhFyT1VqSVr0zADg6HDZa7UarhatstQ97B4SyJQNA PQIM8KMUo16vA8SGz5VUejKPSh2DYE0ybDeaffglHz+cHZET5qYxRuJ/AHaX i5QR2+q2pYkW6aUFsa41UKkEx7cGbas1zIz6Bxa4fgqm+xdcoUh79fm7jY6F 4/vcLeqBgI/Nrwn8rnqWi8ZyIdvXGhGR0Cgo7uO3uLiiPmHIGO0jxc2UY3Nj pKQ50xZZ0L5NZ/btQ+jEMbhi8w2osVElU3BMj0LXjAWzQ0ID59aHRKrGhRFQ T19BF+aYQiUPW1a72TGUPDywOt3WJtbUYMF2XDDNOAcUljxUzTbgqxhwVzHQ sGdUYLoNYtWeo95AYThKZM0ictHxCHcWAMRhkL3X6XXHI/RgR3cbtNj4KB2/ S8MCSmx+ZM08pMEGJTYqumKOYuM3yETrI/zCdIuOdcdOvlCc+w5bbBCr9kd4 RxS9uIAYm3fyjbfYVbyXXQEBZJnZwya56nhkf9Og0DJk8yO87yOWbC5ZtK5R wi+A19cY4D9RQKGB51NAnkwgVuqzBVgxTCUQMxR60OjzexrBsySaMhi/4BDS ZxqgClR6P3/IYC7BYHkvZrUkVcjjmN36Ykg856nv1UVHI7cW+GLsYBlExjS/ ZQ8hbAmQsQZAHHvqLcM3xT1rHS5fhDygQSIMBge4wRbSZOukyWOTJnrSb7Be 3Aj88tVcmZwKWUBMdsLaO4NffszUGDItHmHOMi2eJTEZyRE4CDT6Aat1kQ7c CLas5tElcymReq/L/RIorAzca++Wqtp8/pagwFlDhfzxB47EmqWM3F6+JJsU JkGlonYTJ5eaECMk0CstIwAool0CwRL1Y6q6IKSYPWKCFaHozTrlPFNvvSH7 rsHj6PPx6Ea2fcMP/MsBS5kb1/JHQCPm6hCjPe7bY14n4SnJ0r/Qv/A6UIMT S7JlIIO4xyGq4oA0XrmQ4Ts4qMBzjFhvGGAOoCsTuIRSFzMzUEDYYjxQu67h +/6r3weyryxPKkFqABA6gFT5rNF7hYijJMKSmPpTAvNKaxZ2VoWQA8O8B1lX g/8REBbGMHBIB0NS1i5XszE/KWMVcnM5GZ+NP42uoDiR/gGWYSlXCfUDHjpl sm+uaG3DL50AwhuW+teTq6PJ6Ke/r3RbJ9ciGkoJQ9gkdV4gSWU0zR8V7Iib OtEU7P9GDspsIETxyi9yExySi/GEnJ5fno3ORxeT0fHzFxvrHY0vYdD1x8vL LVYeUOrJ/MFlSBGpI2b/pHgMFQAIsLD7jtJQm3iGcQkAnXuWzCGaRpFwCU27 a/0i3xUs3siDW7PGWhRPGcdW+KeiCngKcWzG8RwyP1KeREqr2CfOG8E3H50F T/zQ3Zo7n05tgO/0HhVgtHDfy1p2ubJEB/8Zh1ZTfwy9fMxCQSz0OPqFxYm4 Qlnfb8/IHzL2S1od+tVyQCSzt/YuDVThswxC/LOzRZeUToAEdAUjGbdBNYDX VrlAD3mn1aUzw8raEOBhD0hlaTWvYv9eTg72nsaUKJ2RMqSdP6CeqEgUHPE0 YQE8oFoCnjnzak8UThIpAXwFcq7pDeAmODuSXY2OjsU0+OXT1elkpCg5USWV OhIsyA26wClwkY3aJzNetXRTXdoyjPmkNesAucgiJSZ3eYwtGyL6O5KYKjQE 1NVBgYBrhcN+Ahrz7Stg/BC4ujNKlo4fK1lFFdtQBysT3CfM3nNKWs3aURjV hm1dL6vdrm85ex1anWF3VSr32n2r1+kapbJmcq3KERfgNGBtFktYLb0Zeugi TGJ0OZRCnG6jSAJPga9hOqzxwH+QpkCO/HhHLLaETXlgRGEYcSjxct4tZ1hw j02ZKxOXEBFPnHH7CDHrJ7F7RWsX54nNvrH2btvqdQd67V83zxPXgqXRL1RT XTrGAGkUZigU+iQKsi5x2BJQMV4lIQK9uRjfHJ0BViW6K2UedpTF/UQl6xfn 6/Cjh83UsFl+WNYPKgK4nCxBI26OUbFaOk2r28nuaPEeJkuyV+OTa1Etlkpo gvCxfsK5LxAlhg3Ly8CW1Rs2s8Pdx7gi4+9JGc8NDCh0ZMR2BPkIu0zdyXiu dVZB+o3wK6WBNHQqjF+hPp1lMtsGfEGhjIXQaB6fGTc3OfJ4HrHgTjgTzmCh N9xnMMa4hWEBhAUm8p++7RFYZQmKCFxoKlf+Sk4xlgd3BlnAFeuG1kluyc/3 SntSH9tylzlhpqbNU/KVIRSaY3dodXuGlx40O9ZBa2BEKOlPT7eGCq6yWRGG tbUSOHHuYAdi5kFMwpjlIWpnGOBthHxlwOO3aVKv63I0c37p3EBohIyswqy9 WwSJmKA+FYPqsIm/Nn8TjAvuzYiZ3X9WBRsIsxaFZcoFdWwJu4387YIKlJJM xEmSy3Lm8aeAqkUb1GsNrV7bONI+GDStfnPlyisAqmIqTh1weZJUzgO56zQM eQTgU3TiGS+HqkkfcQpDiw3ctrVI0q58c5kv9JoVrWF1JCGC78u35F9nv9in UFtcnY0//PLG3ILvCWtr9fVSbJYo7o1KmsQc0C/8V8dRtE7GeOl67zxIWnB3 qBbB5ZeQS2GrXY4PydzBFxQWFA1xDuQRXUCHDDSSEKbVx2R1CQ4S6s4D9ntK 1WjAft7SCRKBB0HFMM9cgT6wZsJUrSfO0jgKRUCqXTak96jAivIH0dvtqNOx etrR98+82b0aqX7BMTfyAq+8lFeJa9No7b8lX0J5tWerpjcyhqsIecwhQGLI nJEyQhFb6MNWmKqio/YnByr6ja0F12M+UcfDlhoKoUPsnOwElQaEp5EhPkK4 ADsUgXhfQOCgiKYxXoFkXCE7wCR+Zlkyr8yVBAp84XexakXF8FWE+5UzJVDq z+ZqTjXmYjQ6vv40vvrlkFyDhXnOgyVePWEeojlFiVcvanzGEw0aJBXLSqIH 1BvIBdEHKTA1Mf22gayjndC5ZT5LGJhfeWkzr6K6fXZHZRaEfCf1Id7+IOq+ QWrFhWVpbUxAq6/w5IqTRerOyT2PJKiE1ZopDiuU04ujD5PTm1FZCZ2dpUhb wSEfLzACGBC9uTaoIDQXOYTa/gJ/yN0bCHfAqNlv9qx+e7h+u/1nmr9CMVdg y0682tiEJ47/YGhRqSjTYU5DMEZ6g+43AdIJj6BKwwN5DG53UNxaKiCJCERo AMajOK1LSHREFzzOTq8nUH2ej2Ezv2CdjCNxDpPdR3mHgX6mFNDYb5v3SMKf ZHCeRpSSBSwB5AZzzcVCgQzkNYQopSUhvlZTJ+VLFfTRT2apE3kKb4l3haAt 5Fg4YJy/R4rKjtj7FFMrjLwHTatnvN+0kbB32mJtP1usPcUWxYucGI1rMizx hB4K0LVak6XxqTib9wDn6At7W77CKWOuzKGvElG24ilFjNkRLAKPbetyXEMy I0fTRMRNiJQQ5NksWIA9WrJByHyPQRfyArnFPFpLY+rVFfkOa63ttlbQ78nV aFRebb9Fzu3J6PxSdhpmIecs9rFiexWRpdO2+qvb7ydur0TYT5dwi0CF9jcE RG8W4v3egdXvZxAfdz2BXvOtDDs0Li3NBfBwaYswYgNUdEmOBtsh4/z6G8gp Vv6VvMTJPTp1Uj8RFFapVFYMK2YtQb5ZKiwoIgWOi2kUEhc0muB24YSbw/EB ZAOrigH7IsWKhX6DoJiHfu8gxyQ7OdtKI88Ac3wyhFZMlEGGHJG4By4mEFF3 bbB4LWDbcJHac+sQN0TFw8XFU252+Q5A8Wj51kBu7uzwbgtFWqQjHUqLafQ7 Ajk+6n54G4WANTke8c79jov2O7tJ2UKj3wLI8VGX+MUk6uI/x0VeWRSPl6Wn nh/d35KnKOjv33Z46aZ/Zq1vn/0bvV5sfB4xAAA= --0-177650955-965568055=:72320-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 11:53:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mesache.encomix.es (mesache.encomix.es [194.143.192.3]) by hub.freebsd.org (Postfix) with SMTP id C014337BC7A for ; Sun, 6 Aug 2000 11:53:17 -0700 (PDT) (envelope-from arnaiz@encomix.es) Received: (qmail 7786 invoked from network); 6 Aug 2000 18:53:04 -0000 Received: from unknown (HELO feliz) (195.114.199.31) by mesache.encomix.es with SMTP; 6 Aug 2000 18:53:04 -0000 From: =?iso-8859-1?B?SmVz+nMgQXJu4Wl6?= To: Subject: subscribe Date: Sun, 6 Aug 2000 20:51:48 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 12: 5:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 0EC3237B533 for ; Sun, 6 Aug 2000 12:05:22 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 56160 invoked by uid 1000); 6 Aug 2000 19:05:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Aug 2000 19:05:21 -0000 Date: Sun, 6 Aug 2000 14:05:21 -0500 (CDT) From: Mike Silbersack To: Doug White Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: FreeBSD belly up with big config In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Mike Silbersack wrote: > If my memory serves me right, someone who was working with doing squid > benchmarks had such patches. Searching through the archive for -net for > squid and/or freebsd 3.2 should find the message - he linked to a page > with performance tuning tips. I'm not sure if there was much merit to > most of the suggestions, but one of them was definitely related to the > number of interfaces. > > Mike "Silby" Silbersack Here's the site I was thinking of: http://polygraph.ircache.net/Tips/FreeBSD-3.3/ Benchmarks of the interface hash specifically are here: http://www.ircache.net/~wessels/Junk/aliases/ The patch is for FreeBSD 3.3 as far as I can tell. I'd assume it would apply to 3.4, but I have no clue about 4 or 5. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 12:45: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 327E037B5A3 for ; Sun, 6 Aug 2000 12:45:02 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id MAA04098; Sun, 6 Aug 2000 12:44:30 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008061944.MAA04098@bubba.whistle.com> Subject: Re: ether_ifattach() issue In-Reply-To: <200008051445.KAA00231@etinc.com> from Dennis at "Aug 5, 2000 10:59:02 am" To: Dennis Date: Sun, 6 Aug 2000 12:44:30 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis writes: > The change in 4.1 to ether_ifattach() needs a check to see if the device is > already attached. > > calling ether_ifattch() with a device already attached will lock up the > system consistently. No interface should be attached twice, Ethernet or other, right? So try this patch and find out which driver is broken. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: sys/net/if.c =================================================================== RCS file: /home/ncvs/src/sys/net/if.c,v retrieving revision 1.91 diff -u -r1.91 if.c --- if.c 2000/07/16 01:46:42 1.91 +++ if.c 2000/08/06 19:42:47 @@ -146,6 +146,17 @@ inited = 1; } +#ifdef INVARIANTS + { + struct ifnet *qent; + + TAILQ_FOREACH(qent, &ifnet, if_link) { + KASSERT(qent != ifp, ("%s%d: already attached", + ifp->if_name, ifp->if_unit)); + } + } +#endif + TAILQ_INSERT_TAIL(&ifnet, ifp, if_link); ifp->if_index = ++if_index; /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 13: 6:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 7504E37BA0E for ; Sun, 6 Aug 2000 13:06:46 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13LWgW-000NAr-00; Sun, 06 Aug 2000 22:06:12 +0200 Date: Sun, 6 Aug 2000 22:06:12 +0200 From: Neil Blakey-Milner To: Archie Cobbs Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: ether_ifattach() issue Message-ID: <20000806220611.A89046@mithrandr.moria.org> References: <200008051445.KAA00231@etinc.com> <200008061944.MAA04098@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008061944.MAA04098@bubba.whistle.com>; from archie@whistle.com on Sun, Aug 06, 2000 at 12:44:30PM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 2000-08-06 (12:44), Archie Cobbs wrote: > No interface should be attached twice, Ethernet or other, right? > So try this patch and find out which driver is broken. I think the concern was because the semantics to attach devices changed, meaning that drivers from before no longer work. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 13:29:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 640D637B9A2 for ; Sun, 6 Aug 2000 13:29:18 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id NAA04330; Sun, 6 Aug 2000 13:28:07 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008062028.NAA04330@bubba.whistle.com> Subject: Re: ether_ifattach() issue In-Reply-To: <20000806220611.A89046@mithrandr.moria.org> from Neil Blakey-Milner at "Aug 6, 2000 10:06:12 pm" To: Neil Blakey-Milner Date: Sun, 6 Aug 2000 13:28:07 -0700 (PDT) Cc: dennis@etinc.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner writes: > > No interface should be attached twice, Ethernet or other, right? > > So try this patch and find out which driver is broken. > > I think the concern was because the semantics to attach devices changed, > meaning that drivers from before no longer work. Hmm.. my understanding was that it was never OK to attach the same interface twice (without detaching in between). So if this behavior worked before then it was just "luck". In any case, IMHO in the future it doesn't make sense to allow an interface to attach twice... what would that mean anyway? Admittedly there may be a backward compatibility problem, but it seems like the origin of the problem is in the driver, not the ether_attach() routine. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 13:40:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 8A32C37BA22 for ; Sun, 6 Aug 2000 13:40:22 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13LXDN-000NGz-00; Sun, 06 Aug 2000 22:40:09 +0200 Date: Sun, 6 Aug 2000 22:40:09 +0200 From: Neil Blakey-Milner To: Archie Cobbs Cc: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: ether_ifattach() issue Message-ID: <20000806224009.A89400@mithrandr.moria.org> References: <20000806220611.A89046@mithrandr.moria.org> <200008062028.NAA04330@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008062028.NAA04330@bubba.whistle.com>; from archie@whistle.com on Sun, Aug 06, 2000 at 01:28:07PM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun 2000-08-06 (13:28), Archie Cobbs wrote: > > > No interface should be attached twice, Ethernet or other, right? > > > So try this patch and find out which driver is broken. > > > > I think the concern was because the semantics to attach devices changed, > > meaning that drivers from before no longer work. > > Hmm.. my understanding was that it was never OK to attach the > same interface twice (without detaching in between). So if this > behavior worked before then it was just "luck". > > In any case, IMHO in the future it doesn't make sense to allow > an interface to attach twice... what would that mean anyway? > > Admittedly there may be a backward compatibility problem, but > it seems like the origin of the problem is in the driver, not > the ether_attach() routine. Using dev/awi/awi.c as an example: sc->sc_dev.dv_xname, sc->sc_mib_phy.IEEE_PHY_Type == AWI_PHY_TYPE_FH ? "FH" : "DS", sc->sc_tx_rate / 10, ether_sprintf(sc->sc_mib_addr.aMAC_Address)); - if_attach(ifp); #ifdef __FreeBSD__ - ether_ifattach(ifp); -#if NBPFILTER > 0 - bpfattach(ifp, DLT_EN10MB, sizeof(struct ether_header)); -#endif + ether_ifattach(ifp, ETHER_BPF_SUPPORTED); #else + if_attach(ifp); ether_ifattach(ifp, sc->sc_mib_addr.aMAC_Address); #if NBPFILTER > 0 bpfattach(&ifp->if_bpf, ifp, DLT_EN10MB, sizeof(struct ether_header)); In other words - if_attach is no more. But, older drivers still use if_attach, and thus when ether_ifattach occurs, that's the second time that happens. Of course, I have no idea how the ether_ifattach argument change affects things - I'm just guessing as to why Dennis may be asking. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 14: 3:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lysimachus.hosting.swbell.net (lysimachus.hosting.swbell.net [216.100.98.6]) by hub.freebsd.org (Postfix) with ESMTP id AE34237BA22 for ; Sun, 6 Aug 2000 14:03:11 -0700 (PDT) (envelope-from alc@imimic.com) Received: from imimic.com (adsl-216-63-78-19.dsl.hstntx.swbell.net [216.63.78.19]) by lysimachus.hosting.swbell.net id RAA03431; Sun, 6 Aug 2000 17:02:50 -0400 (EDT) [ConcentricHost SMTP Relay 1.7] Message-ID: <398DD279.8FFCC13D@imimic.com> Date: Sun, 06 Aug 2000 16:02:49 -0500 From: "Alan L. Cox" Organization: iMimic Networking, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Doug White , hackers@FreeBSD.ORG Subject: Re: FreeBSD belly up with big config Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's the site I was thinking of: > > http://polygraph.ircache.net/Tips/FreeBSD-3.3/ Beware...their patch does a malloc M_WAITOK in interrupt state. I've pointed this out to them, but they haven't changed it yet. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 15:56:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from narcissus.net (narcissus.net [209.73.230.146]) by hub.freebsd.org (Postfix) with ESMTP id 2423137BC49 for ; Sun, 6 Aug 2000 15:56:14 -0700 (PDT) (envelope-from ben@narcissus.net) Received: by narcissus.net (Postfix, from userid 1000) id AD523206; Sun, 6 Aug 2000 18:44:36 -0400 (EDT) Date: Sun, 6 Aug 2000 18:44:36 -0400 From: Ben Rosengart To: hackers@freebsd.org Subject: MD_NSECT apparently not working? Message-ID: <20000806184436.A1641@narcissus.net> Mime-Version: 1.0 Content-Type: message/rfc822 Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am using an MD-based /tmp. This defaults to 20000 sectors, or 10 megs. According to LINT and to md(4), I can change this by compiling options MD_NSECT=300000 into my kernel for a 150-meg /tmp. But I have done so, and it seems to make no difference. I must be missing something. % uname -a FreeBSD narcissus.net 4.1-STABLE FreeBSD 4.1-STABLE #0: Thu Aug 3 16:58:39 EDT 2000 ben@narcissus.net:/usr/obj/usr/src/sys/NARCISSUS i386 % grep -i md NARCISSUS options MD_NSECT=300000 pseudo-device md (BTW: I tried this question on -questions and -stable and got no answer.) -- Ben "I didn't order any WOO-WOO... Maybe a YUBBA... But no WOO-WOO!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 16:15:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9169737BAB2; Sun, 6 Aug 2000 16:15:18 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id TAA90717; Sun, 6 Aug 2000 19:14:59 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 6 Aug 2000 19:14:59 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: vns@delta.odessa.ua Cc: freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: <200008032335.TAA01440@jupiter.delta.ny.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote: > >Bridging on by default may > >have nasty side effects for multi-interface machines (especially security > >side effects). > It's several ways to work around about that: > - compile kernel without bridging support. > - remove bridge starting code vmware.sh file in rc.d directory. > - create special bridge cluster with one real interface and with one emulated Actually, I was hoping that the vmware port wouldn't interfere with existing configurations on the box :-). I compile in the BRIDGE code so that I can test/develop with it, not so that ethernet support on the notebook can be broken after I install the vmware port, or so that a port can arbitrarily turn on bridging of all attached ethernet devices. > >I haven't read the code (I admit) but I finding the > >current behavior both (a) irritating (messages) and (b) worrying > >(unpredicted bridging with potential side effects). > I don't know I never seen such effect. Could you to do more testing > about that. The behavior with the wi0 ethernet driver seems to be continuous printing of the output included in my previous message. With the ep0 driver, the results are actually much worse -- I'm unable to use networking at all while the bridging sysctl is enabled (the default). While the sysctl is enabled, dhclient fails for that interface, and any attempt to manually configure and use it results in a route not found. When I disable the sysctl, networking begins to work on the box. The following default-installed startup script is really, really scary: sysctl net.link.ether.bridge_refresh && bridge="_bridge" kldload if_tap.ko echo -n >/compat/linux/dev/vmnet1 ifconfig vmnet1 $host_ip netmask $netmask if [ _$bridge != _ ]; then sysctl -w net.link.ether.bridge_refresh=1 sysctl -w net.link.ether.bridge=1 fi Un-announced, the vmware port enabled bridging between the ethernet interfaces on my notebook, generated voluminous output for wi0, and broke networking for ep0. This is a security risk, in that it automatically enables bridging between previously un-connected LAN segments that may have different security properties. This is against POLA in that it breaks functionality (networking), bridges packets unto unexpected segments (potentially breaking many other things, especially DHCP), etc. Previously, use of networking support would create a virtual network between the host and the guest OS, but not affect other networking functionality. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 16:50:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B470637BC5B; Sun, 6 Aug 2000 16:50:28 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA13407; Sun, 6 Aug 2000 16:50:28 -0700 Date: Sun, 6 Aug 2000 16:50:31 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Robert Watson Cc: freebsd-hackers@FreeBSD.ORG Subject: Speaking about vmware... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone been having their system just plain lock up running vmware? Mine has been.. (4.1-stable).. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 19:56:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 4402A37BAFE; Sun, 6 Aug 2000 19:56:38 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA85979; Sun, 6 Aug 2000 19:56:38 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 6 Aug 2000 19:56:38 -0700 (PDT) From: Kris Kennaway To: Robert Watson Cc: vns@delta.odessa.ua, freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Robert Watson wrote: > Un-announced, the vmware port enabled bridging between the ethernet > interfaces on my notebook This is bad - ethernet segments should not be bridged without explicit user confirmation, because they are commonly separated precisely for security reasons. Someone please fix the port appropriately..thanks. Kris FreeBSD Security Officer Team -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 23:43: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 81A0D37B509 for ; Sun, 6 Aug 2000 23:43:00 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA01626; Sun, 6 Aug 2000 23:54:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008070654.XAA01626@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: FreeBSD belly up with big config In-reply-to: Your message of "Sat, 05 Aug 2000 13:21:47 EDT." <200008051708.NAA00486@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Aug 2000 23:54:11 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With 1800 interfaces in the system Freebsd seems to use about 50Mhz of cpu > when idle in "interrupts" even when there are no interrupts to process. on > a 500Mhz box it uses 10% of the cpu and it seems linear with different > speed processors. > > the 1800 interfaces are 900 DLCIs on a T3 frame with 900 bridge groups > (rather common for a DSL delivered via Frame). This with just one > line...the same problem could occur with say 8 T1 lines with 100+ DLCIs on > each. > > It seems that there is substantial overhead just scanning interfaces for > some routine maintenance...is there any hope of alleviating this deboggle? Probably. Without some idea of what's actually happening, though, it's a little hard to point a finger and say "look here". A profiling dump of the system when idle would be very illuminating, as it'd give you a good idea of what's actually going on to use so much CPU. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 6 23:46:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id ACA4037B753 for ; Sun, 6 Aug 2000 23:46:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id XAA01677; Sun, 6 Aug 2000 23:57:37 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008070657.XAA01677@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Sayer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Drivers for Dollars (was Re: US$100 prize for adding ESS Audiodrive support to pcm) In-reply-to: Your message of "Sat, 05 Aug 2000 18:53:26 PDT." <398CC516.C30108EF@quack.kfu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Aug 2000 23:57:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since my experience with the Solo driver (it's still not quite done) > bounty, > I will put up a page where folks offering "driver bounties" can make > their offers > known. Such sites exist for software in general, but I will make one > just for > FreeBSD drivers. This should probably be integrated with the BSD Driver Database. (http://www.posi.net/freebsd/drivers) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 2: 8:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 5D37D37BD8D for ; Mon, 7 Aug 2000 02:08:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA02797; Mon, 7 Aug 2000 02:20:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008070920.CAA02797@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hm@kts.org Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 3Com 10/100 Mini PCI Ethernet In-reply-to: Your message of "Thu, 03 Aug 2000 08:21:02 +0200." <20000803062102.18BD31F1C@bert.kts.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 02:20:13 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > I'm looking for docs for the Mini PCI card in the subject, it has the 3Com > > > part/product no. 3CN3AV1556. It is a 10/100 ethernet 56k modem combo card > > > built into an HP laptop. > > > > Have you tried booting FreeBSD on this system yet? If so, does the 'xl' > > driver pick it up? If not, can you send the output of 'pciconf -l', as > > it may just require a new PCI ID in the driver. > > Yes, i first tried the ep driver, then the xl and then the vx by adding the > chip id (0x6055) to the probe routine. > > I think the ep driver (which does some funny things to the eeprom) managed > to overwrite part of the eeprom so that the xl driver failed to recognize > the card. I then tried to add it to the vx driver (at that point i think > i started to know what i did) which failed too, so i wrote a subroutine > to display the eeprom contents which (because i did not understood the > the OP and SubOP command fields before running it) finally erased the > eeprom contents to 0xffff in all locations (which now prevents the card > from being initialized by the BIOS - has anybody an idea how to revive > such a PCI card ????). You would need to write the original EEPROM contents back into the EEPROM, after manually configuring it. Very difficult. > Do i understand you right in that you would do a fresh start with this > card using the xl driver ? I'm a bit concerned about again accidentially > overwriting the eeprom, its an _expensive_ card ... ;-) That's correct. The xl driver is not likely to trash the eeprom, although I'm quite surprised that the 'ep' driver did. What possessed you to start with an ISA-only driver when the device is so clearly a PCI device? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 2: 9:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from terrapin.ru.ac.za (terrapin.ru.ac.za [146.231.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 32CF637BD50 for ; Mon, 7 Aug 2000 02:09:23 -0700 (PDT) (envelope-from g98p1836@campus.ru.ac.za) Received: from eg090.lab.ru.ac.za ([146.231.105.90] helo=edengrovetest) by terrapin.ru.ac.za with esmtp (Exim 3.14 #1) id 13LiuN-000Ajf-00 for freebsd-hackers@FreeBSD.org; Mon, 07 Aug 2000 11:09:19 +0200 From: "DOMINIC CHARLES PARRY" To: freebsd-hackers@FreeBSD.org Date: Mon, 7 Aug 2000 11:07:17 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: subscribe Reply-To: g98p1836@campus.ru.ac.za X-mailer: Pegasus Mail for Win32 (v3.12b) Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'd like to subscribe to the list, at the address parrydc@hotmial.com. Thanks Dominic Parry ---------------------------- |From DOMINIC CHARLES PARRY | |MAIL : G98P1836 | ---------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 3: 4:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.ops.uunet.co.za (axl.ops.uunet.co.za [196.31.2.163]) by hub.freebsd.org (Postfix) with ESMTP id A941F37B5D2 for ; Mon, 7 Aug 2000 03:04:44 -0700 (PDT) (envelope-from sheldonh@axl.ops.uunet.co.za) Received: from sheldonh (helo=axl.ops.uunet.co.za) by axl.ops.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13Ljlx-0002Pz-00 for freebsd-hackers@FreeBSD.org; Mon, 07 Aug 2000 12:04:41 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.org Subject: Does sio have a maintainer? Date: Mon, 07 Aug 2000 12:04:41 +0200 Message-ID: <9298.965642681@axl.ops.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Does the sio driver have a maintainer? There are two PR's open that contain patches to provide support for new devices, but I can't find anyone to pin them on. :-) kern/20341 support Cronyx-Omega-PCI serial multiport adapters kern/20410 support high-speed NS16550A, ST16650A and TI16750 Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 4:44:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 9EC6737BD89; Mon, 7 Aug 2000 04:44:39 -0700 (PDT) (envelope-from kts.org!hm@worker.thw-IP.NET) Received: from localhost (2561 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Mon, 7 Aug 2000 13:44:37 +0200 (CEST) (Smail-3.2.0.111 2000-Feb-17 #12 built 2000-May-16) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 8427E52CED; Mon, 7 Aug 2000 13:37:03 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id B38461F1C; Mon, 7 Aug 2000 13:36:57 +0200 (CEST) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <200008070920.CAA02797@mass.osd.bsdi.com> from Mike Smith at "Aug 7, 2000 2:20:13 am" To: msmith@FreeBSD.ORG (Mike Smith) Date: Mon, 7 Aug 2000 13:36:57 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1602 Message-Id: <20000807113657.B38461F1C@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I think the ep driver (which does some funny things to the eeprom) managed > > to overwrite part of the eeprom so that the xl driver failed to recognize > > the card. I then tried to add it to the vx driver (at that point i think > > i started to know what i did) which failed too, so i wrote a subroutine > > to display the eeprom contents which (because i did not understood the > > the OP and SubOP command fields before running it) finally erased the > > eeprom contents to 0xffff in all locations (which now prevents the card > > from being initialized by the BIOS - has anybody an idea how to revive > > such a PCI card ????). > > You would need to write the original EEPROM contents back into the > EEPROM, after manually configuring it. Very difficult. Am i right assuming that pciconf is the right tool for this (manually configuring) job ? > > Do i understand you right in that you would do a fresh start with this > > card using the xl driver ? I'm a bit concerned about again accidentially > > overwriting the eeprom, its an _expensive_ card ... ;-) > > That's correct. The xl driver is not likely to trash the eeprom, > although I'm quite surprised that the 'ep' driver did. > > What possessed you to start with an ISA-only driver when the device is so > clearly a PCI device? It was the device ID 0x6055 in the ep driver which is identical to the device ID in the Mini PCI version. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 5: 1:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 9C39A37BD90; Mon, 7 Aug 2000 05:01:04 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny7-10.ix.netcom.com [198.211.17.138]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id IAA17708; Mon, 7 Aug 2000 08:01:01 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id IAA00335; Mon, 7 Aug 2000 08:00:59 -0400 (EDT) (envelope-from vsilyaev) Date: Sun, 6 Aug 2000 23:23:39 -0400 From: "Vladimir N. Silyaev" To: emulation@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000806232339.A3251@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" X-Mailer: Mutt 1.0i X-Mailer: Mutt 1.0i In-Reply-To: ; from rwatson@FreeBSD.ORG on Sun, Aug 06, 2000 at 07:14:59PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Ok, guys. See in the attachment fix, you should apply it to prevent current behavior. On Sun, Aug 06, 2000 at 07:14:59PM -0400, Robert Watson wrote: > On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote: > > > >Bridging on by default may > > >have nasty side effects for multi-interface machines (especially security > > >side effects). > > It's several ways to work around about that: > > - compile kernel without bridging support. > > - remove bridge starting code vmware.sh file in rc.d directory. > > - create special bridge cluster with one real interface and with one emulated > > Actually, I was hoping that the vmware port wouldn't interfere with > existing configurations on the box :-). I compile in the BRIDGE code so > that I can test/develop with it, not so that ethernet support on the > notebook can be broken after I install the vmware port, or so that a port > can arbitrarily turn on bridging of all attached ethernet devices. > > > >I haven't read the code (I admit) but I finding the > > >current behavior both (a) irritating (messages) and (b) worrying > > >(unpredicted bridging with potential side effects). > > I don't know I never seen such effect. Could you to do more testing > > about that. > > The behavior with the wi0 ethernet driver seems to be continuous printing > of the output included in my previous message. > > With the ep0 driver, the results are actually much worse -- I'm unable to > use networking at all while the bridging sysctl is enabled (the default). > While the sysctl is enabled, dhclient fails for that interface, and any > attempt to manually configure and use it results in a route not found. > When I disable the sysctl, networking begins to work on the box. > > The following default-installed startup script is really, really scary: > > sysctl net.link.ether.bridge_refresh && bridge="_bridge" > kldload if_tap.ko > echo -n >/compat/linux/dev/vmnet1 > ifconfig vmnet1 $host_ip netmask $netmask > if [ _$bridge != _ ]; then > sysctl -w net.link.ether.bridge_refresh=1 > sysctl -w net.link.ether.bridge=1 > fi > > Un-announced, the vmware port enabled bridging between the ethernet > interfaces on my notebook, generated voluminous output for wi0, and broke > networking for ep0. This is a security risk, in that it automatically > enables bridging between previously un-connected LAN segments that may > have different security properties. This is against POLA in that it > breaks functionality (networking), bridges packets unto unexpected > segments (potentially breaking many other things, especially DHCP), etc. > Previously, use of networking support would create a virtual network > between the host and the guest OS, but not affect other networking > functionality. -- Vladimir --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vmware.diff" Index: files/vmware.sh =================================================================== RCS file: /home/vns/cvs/vmware/vmware/vmmon-only/freebsd/port/files/vmware.sh,v retrieving revision 1.5 diff -u -r1.5 vmware.sh --- files/vmware.sh 2000/07/31 00:54:37 1.5 +++ files/vmware.sh 2000/08/07 03:16:16 @@ -8,6 +8,7 @@ networking=@@NETWORKING@@ host_ip=@@HOST_IP@@ netmask=@@NETMASK@@ +start_bridge=0 [ -x $vmware_dir/bin/vmware ] || exit @@ -19,17 +20,32 @@ exec >/dev/null + if [ $networking -eq 1 ]; then + if sysctl net.link.ether.bridge_refresh; then + if sysctl net.link.ether.bridge|grep 1; then + bridge="_bridge_on" + start_bridge=0 + else + if [ $start_bridge -eq 1 ]; then + bridge="_bridge" + else + bridge="_bridge_off" + fi + fi + fi + fi + case $1 in start) kldload ${vmware_dir}/lib/modules/vmmon_${suffix}.ko if [ $networking -eq 1 ]; then - sysctl net.link.ether.bridge_refresh && bridge="_bridge" kldload if_tap.ko echo -n >@@LINUX_DIR@@/dev/vmnet1 ifconfig vmnet1 $host_ip netmask $netmask + sysctl net.link.ether.bridge if [ _$bridge != _ ]; then sysctl -w net.link.ether.bridge_refresh=1 - sysctl -w net.link.ether.bridge=1 + [ $start_bridge -eq 1 ] && sysctl -w net.link.ether.bridge=1 fi fi echo -n " VMware${bridge}" >&2 @@ -40,7 +56,6 @@ if [ $networking -eq 1 ]; then ifconfig vmnet1 down ifconfig vmnet1 delete $host_ip - sysctl net.link.ether.bridge_refresh && bridge="_bridge" [ _$bridge != _ ] && sysctl -w net.link.ether.bridge_refresh=1 fi ;; --azLHFNyN32YCQGCU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 5: 8:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 6700237BDB5 for ; Mon, 7 Aug 2000 05:08:38 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 13Llhq-00066n-00 for hackers@freebsd.org; Mon, 7 Aug 2000 13:08:34 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id NAA05465 for hackers@freebsd.org; Mon, 7 Aug 2000 13:08:33 +0100 (BST) (envelope-from jcm) Date: Mon, 7 Aug 2000 13:08:33 +0100 From: j mckitrick To: hackers@freebsd.org Subject: newbus questions Message-ID: <20000807130833.A5347@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, there are two recent articles on newbus on daemonnews, and one at people.freebsd.org/~asmodai by jeroen. Does anyone remember seeing any others? I thought for sure i remembered seeing a article explaining the OO design concepts behind newbus, particularly the use of soft_c, the local data, the global data, and methods for a particular device. jm -- ------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org Honk if you hate people too. ------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 6:30:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id DAEFC37B98D; Mon, 7 Aug 2000 06:30:13 -0700 (PDT) (envelope-from bad@wireless.net) Received: from localhost (bad@localhost) by wireless.net (8.9.3/8.9.3) with SMTP id GAA08093; Mon, 7 Aug 2000 06:30:15 -0700 (PDT) Date: Mon, 7 Aug 2000 06:30:15 -0700 (PDT) From: Bernie Doehner To: hackers@freebsd.org, questions@freebsd.org Cc: buaas@wireless.net Subject: Restoring old IPv4 raw socket behavior under 4.1-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All: Just upgraded from 4.0-RELEASE to 4.1-RELEASE, and now a custom application of ours that used to do: socket(AF_INET, SOCK_RAW, 4); No longer works with: Protocol not supported opening socket. As far as I can tell, this is because SOCK_RAW sockets now default to IPv6. Is there a SIMPLE way to restore old ipv4 SOCK_RAW socket() behavior, so that I don't need to have any IPv6 routes at all? I tried replacing AF_INET with AF_INET6, but then I got host unreachable from the sendto(), because I don't have IPv6 routes set up. Thanks, Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 6:55:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tepid.osl.fast.no (tepid.osl.fast.no [213.188.9.130]) by hub.freebsd.org (Postfix) with ESMTP id C4CBF37B557 for ; Mon, 7 Aug 2000 06:55:06 -0700 (PDT) (envelope-from raw@fast.no) Received: from raw.gren.fast.no (fw-oslo.fast.no [213.188.9.129]) by tepid.osl.fast.no (8.9.3/8.9.1) with ESMTP id OAA22058; Mon, 7 Aug 2000 14:05:04 GMT (envelope-from raw@fast.no) Received: (from raw@localhost) by raw.gren.fast.no (8.9.3/8.9.3) id PAA07165; Mon, 7 Aug 2000 15:56:20 +0200 (CEST) (envelope-from raw) From: Raymond Wiker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14734.49156.249444.881713@raw.gren.fast.no> Date: Mon, 7 Aug 2000 15:56:20 +0200 (CEST) To: "Daniel O'Connor" Cc: Raymond Wiker , freebsd-hackers@freebsd.org Subject: RE: dlopen() and friends from a statically-linked binary? In-Reply-To: References: <14711.10742.914512.819982@raw.gren.fast.no> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor writes: > > On 20-Jul-00 Raymond Wiker wrote: > > Is it possible, at all, to use dlopen etc from a > > statically-linked executable? My experiments with FreeBSD-4.0 (see > > below) indicate that it's not possible. > > You can't do it from a statically linked binary, however you can > create a dynamic executable with no external unresolved > references.. I forget how though :-/ OK... I'll take a look at this. Thanks to everyone who responded. > > > The reason that I'd like this to work is that SBCL (a Common > > Lisp implementation, see http://sbcl.sourceforge.net) needs the > > addresses of certain library symbols (e.g, errno) when building the > > initial lisp image. This seems to require static linking. On the other > > hand, SBCL is severely handicapped if it cannot subsequently use > > dlopen() to load foreign code into the running lisp system. > > Well, I don't see why it would need static linking for that.. When > the binary runs the libraries it uses will get loaded, and then it > can use dlsym() to get the addresses it needs.. (ie what I am > saying is I don't understand your explanation :) A running SBCL system includes a runtime substrate written in C, along with Lisp code compiled into native code or byte-code. The C runtime calls a top-level function in the Lisp system at startup; this call does not return until the top-level Lisp function exits. The top-level Lisp function calls into the C substrate for various low-level services, including garbage-collecting of Lisp objects. This implies a circular dependency: the C runtime must have the address of the top-level Lisp function, while the Lisp code needs the addresses of various code and data in the C runtime. In SBCL this is solved in the bootstrapping process, by a function that patches up the Lisp code with the addresses from the C code. This cannot be done at startup, as the Lisp object format differs from the conventional formats (a.out or ELF). At the moment, my options seem to be: 1) find a way of compiling the C runtime so that there are no unresolved externals, while still producing a dynamic executable. 2) identify a small set of symbols from libc.so, and encapsulate them (possibly using dlsym("foo", RTLD_NEXT)?) 3) modify SBCL so that the patchup is done at startup time, instead of at compilation time. Of these, 1) is probably the least work, 2) is slightly more work and inelegant, and 3) is the most work but carries a few other benefits (notably, it reduces the Lisp -> C dependency). //Raymond. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 10:31:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by hub.freebsd.org (Postfix) with ESMTP id CF43B37B56C; Mon, 7 Aug 2000 10:31:43 -0700 (PDT) (envelope-from mht@clark.net) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13LqkW-0007ab-00; Mon, 07 Aug 2000 17:31:40 +0000 Received: from [204.179.132.99] (helo=brainwash.clark.net) by dfw-mmp1.email.verio.net with esmtp (Exim 3.15 #4) id 13LqkV-0000tm-00; Mon, 07 Aug 2000 17:31:40 +0000 Message-Id: <4.3.2.7.2.20000807102249.00c9b100@pop3.clark.net> X-Sender: mht@pop3.clark.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 07 Aug 2000 10:23:35 -0700 To: mjacob@feral.com, Robert Watson From: mht@clark.net Subject: Re: Speaking about vmware... Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, It appears that there is an occasional glitch with FreeBSD and VMware. I have to record the core.. /m At 04:50 PM 8/6/00 -0700, Matthew Jacob wrote: >Has anyone been having their system just plain lock up running vmware? Mine >has been.. (4.1-stable).. > >-matt > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 11:29:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 04EFF37B859; Mon, 7 Aug 2000 11:29:43 -0700 (PDT) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <20000807113657.B38461F1C@bert.kts.org> from Hellmuth Michaelis at "Aug 7, 2000 01:36:57 pm" To: hm@kts.org Date: Mon, 7 Aug 2000 11:29:42 -0700 (PDT) Cc: freebsd-hackers@freebsd.org, msmith@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000807182943.04EFF37B859@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > I think the ep driver (which does some funny things to the eeprom) managed > > > to overwrite part of the eeprom so that the xl driver failed to recognize > > > the card. I then tried to add it to the vx driver (at that point i think > > > i started to know what i did) which failed too, so i wrote a subroutine > > > to display the eeprom contents which (because i did not understood the > > > the OP and SubOP command fields before running it) finally erased the > > > eeprom contents to 0xffff in all locations (which now prevents the card > > > from being initialized by the BIOS - has anybody an idea how to revive > > > such a PCI card ????). > > > > You would need to write the original EEPROM contents back into the > > EEPROM, after manually configuring it. Very difficult. > > Am i right assuming that pciconf is the right tool for this (manually > configuring) job ? No, you are wrong. The only way to write to the EEPROM (that I know of anyway) is via the usual EEPROM control registers in the card's I/O space, which won't be mapped if the card is so fubared that the BIOS won't initialize it. > > > Do i understand you right in that you would do a fresh start with this > > > card using the xl driver ? I'm a bit concerned about again accidentially > > > overwriting the eeprom, its an _expensive_ card ... ;-) Then you should have been more careful with it. > > That's correct. The xl driver is not likely to trash the eeprom, > > although I'm quite surprised that the 'ep' driver did. > > > > What possessed you to start with an ISA-only driver when the device is so > > clearly a PCI device? > > It was the device ID 0x6055 in the ep driver which is identical to the > device ID in the Mini PCI version. I'm sorry, but after reading this thread, I'm having a hard time coming up with an explanation for this nonsense which doesn't involve you being a dumbass. The device ID in question is in if_ep_pccard.c which is for PCMCIA devices only! Not PCI! There is no way that the ep driver will probe a PCI device unless you go to some lengths to twist its arm! Why you resorted to this arm-twisting instead of the blazingly obvious action of trying an actual PCI driver is beyond me. (_How_ you even managed to twist its arm is also beyond me. Obviously you decided not to tell us exactly what you did for fear of being found out. Too late.) This is not one of those "it's nobody's fault" situations. You did not make an innocent mistake: you screwed up. In front of god and everything. You ignored all of the signs, portents, and the dude with the spooky black robe and scythe standing over your shoulder. And then you tried to cover it up. Now, get out a piece of paper, write "I damaged this card because I'm a dumbass" on it, stick it to the card, then take it back to where you got it and try to get it replaced. Alternatively, tell us where you got it so I can order one and try to get it supported properly instead of having my blood pressure driven off the scale by yet another tale of foot-shooting idiocy. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 12: 6: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id A903F37B692 for ; Mon, 7 Aug 2000 12:06:04 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id MAA12811 for freebsd-hackers@freebsd.org; Mon, 7 Aug 2000 12:06:04 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008071906.MAA12811@bubba.whistle.com> Subject: CVS question To: freebsd-hackers@freebsd.org Date: Mon, 7 Aug 2000 12:06:04 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Consider this source file: http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/xntpd/lib/Attic/ranny.c Question: what version should this command checkout? $ cvs co -D 'January 18, 1999 0:00' freebsd/src/usr.sbin/xntpd/lib/ranny.c Perhaps version 1.1.1.2 would be correct, but instead you get 1.1. It seems CVS is being inconsistent: - If you had done a 'head' checkout on that date you would have gotten 1.1.1.2 - If you later do a 'head' checkout, and specify that date, you get 1.1 What am I missing here.. ? Has this behavior in CVS changed at some point? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 12:38:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 804C437B672 for ; Mon, 7 Aug 2000 12:38:55 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (qmail 20650 invoked from network); 7 Aug 2000 19:47:31 -0000 Received: from jhs.muc.de (HELO park.jhs.no?domain) (193.149.49.84) by slarti.muc.de with SMTP; 7 Aug 2000 19:47:31 -0000 Received: from park.jhs.no_domain (localhost [127.0.0.1]) by park.jhs.no_domain (8.9.3/8.9.3) with ESMTP id NAA01914; Mon, 7 Aug 2000 13:15:14 GMT (envelope-from jhs@park.jhs.no_domain) Message-Id: <200008071315.NAA01914@park.jhs.no_domain> To: Ollivier Robert Cc: hackers@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... From: "Julian Stacey" Organization: Vector Systems Ltd - Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Fri, 28 Jul 2000 00:01:08 +0200." <20000728000108.A44138@keltia.freenix.fr> Date: Mon, 07 Aug 2000 15:15:14 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > According to Julian Stacey: > > just as today I'd use an encrypting file system on my new laptop, > > but such file system don't exist on FreeBSD unfortunately. > > Ahem. Why did I sent an update for security/cfs to green a few months ago? :-) 4.1-release produces no /sbin/mount_cfs, & man mount give no hint, If you have patches to test, I volunteer to test on 4.1 or 3.4 :-) Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 12:51:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pedigree.cs.ubc.ca (pedigree.cs.ubc.ca [142.103.6.50]) by hub.freebsd.org (Postfix) with ESMTP id 8B14937BBF9 for ; Mon, 7 Aug 2000 12:51:28 -0700 (PDT) (envelope-from ycoady@cs.ubc.ca) Received: from newcastle.cs.ubc.ca (ycoady@newcastle.cs.ubc.ca [142.103.6.21]) by pedigree.cs.ubc.ca (8.8.8/8.6.9) with ESMTP id MAA00039 for ; Mon, 7 Aug 2000 12:51:17 -0700 (PDT) Received: from localhost (ycoady@localhost) by newcastle.cs.ubc.ca (8.9.3/8.6.12) with ESMTP id MAA20608 for ; Mon, 7 Aug 2000 12:51:17 -0700 (PDT) X-Authentication-Warning: newcastle.cs.ubc.ca: ycoady owned process doing -bs Date: Mon, 7 Aug 2000 12:51:16 -0700 (PDT) From: Yvonne Coady To: freebsd-hackers@freebsd.org Subject: ffs_getpages() Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering if anyone can shed some light on the changes in the page fault handling code in 3.3 vs 4.0. I've noticed that the async read ahead that used to work for mmaped files via a VOP_READ in ffs_getpages() is no longer there... I've run some very simple (and by no means exhaustive) tests, and on the surface the tradeoff appears to be that in 3.3 the disk is accessed synchronously, 16 pages at a time, whereas in 4.0 access may be asynchronous, 32 pages at a time. I am aware of the fact that in 3.3, using the vnode vlastr field was maybe not a perfect way to detect seq access for "normal" objects in ffs_getpages, but I thought the asynch read ahead was a real bonus - I might be overlooking something obvious here, but can anyone tell me why this has changed? Thanks, Yvonne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 12:52:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 3BFE537BF04; Mon, 7 Aug 2000 12:52:42 -0700 (PDT) (envelope-from kts.org!hm@worker.thw-IP.NET) Received: from localhost (2591 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Mon, 7 Aug 2000 21:52:34 +0200 (CEST) (Smail-3.2.0.111 2000-Feb-17 #12 built 2000-May-16) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id E14FD52CED; Mon, 7 Aug 2000 21:52:02 +0200 (CEST) Received: by bert.kts.org (Postfix, from userid 100) id BC7FB1F1C; Mon, 7 Aug 2000 21:51:47 +0200 (CEST) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <20000807182943.04EFF37B859@hub.freebsd.org> from Bill Paul at "Aug 7, 2000 11:29:42 am" To: wpaul@FreeBSD.ORG (Bill Paul) Date: Mon, 7 Aug 2000 21:51:47 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1633 Message-Id: <20000807195147.BC7FB1F1C@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > I'm sorry, but after reading this thread, I'm having a hard time coming > up with an explanation for this nonsense which doesn't involve you being > a dumbass. Yes, i am. I'm guilty for the death of this innocent card, and it is just and only my personal fault and nobody else's. Please, whoever it currently has, give me the conical hat and i'll wear it for the next 2 or 3 months and i promise, i'll stick this "I damaged this card because, I'm a dumbass" paper on the top of the hat so everyone can see it. I will not anymore write PCI probe/attach routines for an unknown chip to connect it to drivers meant only for ISA, MCA, EISA and PCMCIA devices. I'm also very sorry to be the cause of your blood pressure going up, please accept my apologies. AFAIK, this card is a 3Com OEM product which is not available for purchase, all i can give you is an HP part number. It is also not a "normal" PCI card but a so called "Mini PCI" card and its about as large as a matchbox or even a bit smaller. Anyway, i have replaced the card, and i will try hard not to make the same mistakes again (before this whole mess, i was under the impression that only monitors can be destroyed by software, now i know better ...). But, i want to get this card supported. In case you have one or the other good suggestion (except "stay away from the card, don't even look at it !!") on how to proceed in a more orderly fashion, please let me hear them. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 14: 8:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 1F72137B50F for ; Mon, 7 Aug 2000 14:08:14 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id RAA03430; Mon, 7 Aug 2000 17:08:01 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 7 Aug 2000 17:08:01 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dennis Cc: hackers@freebsd.org Subject: Re: FreeBSD belly up with big config In-Reply-To: <200008051708.NAA00486@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Aug 2000, Dennis wrote: > With 1800 interfaces in the system Freebsd seems to use about 50Mhz of cpu > when idle in "interrupts" even when there are no interrupts to process. on > a 500Mhz box it uses 10% of the cpu and it seems linear with different > speed processors. > > the 1800 interfaces are 900 DLCIs on a T3 frame with 900 bridge groups > (rather common for a DSL delivered via Frame). This with just one > line...the same problem could occur with say 8 T1 lines with 100+ DLCIs on > each. > > It seems that there is substantial overhead just scanning interfaces for > some routine maintenance...is there any hope of alleviating this deboggle? I'd made some similar observations about the current lack of scalability both in management of (struct ifnet) chains, and mountpoints in the file system. As we move to a more dynamic network environment, a lot of things about ifnet handling need to be improved, including fixing (really fixing) the freeing of struct ifnet (lots of loose mbuf pointers hanging around to the struct ifnet, as well as stuff in filtering rules, et al). The bridging code isn't currently designed to work in this manner, and also has problems with dynamically introduced interfaces (try and use options BRIDGE and the sysctl enabled with a pccard sometime). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 14:35:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id C933237BAC8; Mon, 7 Aug 2000 14:35:44 -0700 (PDT) Subject: Re: 3Com 10/100 Mini PCI Ethernet In-Reply-To: <20000807195147.BC7FB1F1C@bert.kts.org> from Hellmuth Michaelis at "Aug 7, 2000 09:51:47 pm" To: hm@kts.org Date: Mon, 7 Aug 2000 14:35:44 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000807213544.C933237BAC8@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > AFAIK, this card is a 3Com OEM product which is not available for purchase, > all i can give you is an HP part number. It is also not a "normal" PCI card > but a so called "Mini PCI" card and its about as large as a matchbox or > even a bit smaller. > > Anyway, i have replaced the card, and i will try hard not to make the same > mistakes again (before this whole mess, i was under the impression that > only monitors can be destroyed by software, now i know better ...). > > But, i want to get this card supported. In case you have one or the other > good suggestion (except "stay away from the card, don't even look at it !!") > on how to proceed in a more orderly fashion, please let me hear them. Type "pciconf -l" and show us the results so we can actually see the vendor/device ID data. If it is indeed vendor ID 0x10B7 and device ID 0x6055, then try the patch included with this e-mail. To apply it, do the following: - Save this message to a file, e.g. /tmp/xl.diff - cd /sys/pci - patch < /tmp/xl.diff Then make a new kernel and/or if_xl.ko module and test it. If it works correctly, you should see the ethernet address and proper media selections in the dmesg output. And, more importantly, you should be able to send and receive traffic. If it doesn't probe correctly, then it's probably not a Cyclone/Hurricane/Tornado chipset and the xl driver won't support it. I believe that it is a Cyclone/Hurricane/Tornado chipset though, since 3Com doesn't make any other 10/100 devices except for what's on the 3CR990 card, which is a) undocumented and b) overkill for an embedded laptop ethernet adapter. -Bill *** if_xl.c.orig Mon Aug 7 14:25:39 2000 --- if_xl.c Mon Aug 7 14:25:03 2000 *************** *** 55,60 **** --- 55,61 ---- * 3Com 3c980C-TX 10/100Mbps server adapter (Tornado ASIC) * 3Com 3cSOHO100-TX 10/100Mbps/RJ-45 (Hurricane ASIC) * 3Com 3c450-TX 10/100Mbps/RJ-45 (Tornado ASIC) + * 3Com 3cN3AV1556 10/100Mpps/RJ-45 HP laptop ethernet (Tornado ASIC?) * Dell Optiplex GX1 on-board 3c918 10/100Mbps/RJ-45 * Dell on-board 3c920 10/100Mbps/RJ-45 * Dell Precision on-board 3c905B 10/100Mbps/RJ-45 *************** *** 184,189 **** --- 185,192 ---- "3Com 3cSOHO100-TX OfficeConnect" }, { TC_VENDORID, TC_DEVICEID_TORNADO_HOMECONNECT, "3Com 3c450-TX HomeConnect" }, + { TC_VENDORID, TC_DEVICEID_3CN3AV1556, + "3Com 3CN3AV1556 Fast Etherlink XL" }, { 0, 0, NULL } }; *************** *** 1142,1147 **** --- 1145,1151 ---- case TC_DEVICEID_HURRICANE_SOHO100TX: /* 3cSOHO100-TX */ case TC_DEVICEID_TORNADO_10_100BT: /* 3c905C-TX */ case TC_DEVICEID_TORNADO_HOMECONNECT: /* 3c450-TX */ + case TC_DEVICEID_3CN3AV1556: /* 3cN3AV1556 */ sc->xl_media = XL_MEDIAOPT_BTX; sc->xl_xcvr = XL_XCVR_AUTO; if (verbose) *** if_xlreg.h.orig Mon Aug 7 14:25:39 2000 --- if_xlreg.h Mon Aug 7 14:20:14 2000 *************** *** 641,646 **** --- 641,647 ---- #define TC_DEVICEID_TORNADO_10_100BT_SERV 0x9805 #define TC_DEVICEID_HURRICANE_SOHO100TX 0x7646 #define TC_DEVICEID_TORNADO_HOMECONNECT 0x4500 + #define TC_DEVICEID_3CN3AV1556 0x6055 /* * PCI low memory base and low I/O base register, and To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 14:40:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id EA0AA37B6E3; Mon, 7 Aug 2000 14:40:42 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id XAA07204; Mon, 7 Aug 2000 23:40:31 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id ABA3E888A; Mon, 7 Aug 2000 23:39:02 +0200 (CEST) Date: Mon, 7 Aug 2000 23:39:02 +0200 From: Ollivier Robert To: Julian Stacey Cc: hackers@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: ELF rtld and environment variables... Message-ID: <20000807233902.B58920@keltia.freenix.fr> Mail-Followup-To: Julian Stacey , hackers@FreeBSD.ORG, green@FreeBSD.ORG References: <20000728000108.A44138@keltia.freenix.fr> <200008071315.NAA01914@park.jhs.no_domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008071315.NAA01914@park.jhs.no_domain>; from jhs@jhs.muc.de on Mon, Aug 07, 2000 at 03:15:14PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Stacey: > 4.1-release produces no /sbin/mount_cfs, & man mount give no hint, > If you have patches to test, I volunteer to test on 4.1 or 3.4 :-) It is a port. I'd love to import it into CURRENT though. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 14:58: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id EAC5937B90F for ; Mon, 7 Aug 2000 14:57:46 -0700 (PDT) (envelope-from julian@elischer.org) Received: from pretoria-14.budapest.interware.hu ([195.70.53.78] helo=jules.elischer.org) by mail.interware.hu with smtp (Exim 3.12 #1 (Debian)) id 13LutD-0005xx-00; Mon, 07 Aug 2000 23:56:56 +0200 Message-ID: <398F3081.167EB0E7@elischer.org> Date: Mon, 07 Aug 2000 14:56:17 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Alan Clegg Cc: Andrzej Bialecki , Cameron Grant , freebsd-hackers@freebsd.org Subject: Re: US$100 prize for adding ESS Audiodrive support to pcm References: <004501bffb0b$27bf8c60$0504020a@haveblue> <20000805155806.A94702@diskfarm.firehouse.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alan Clegg wrote: > > On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly [...] > Add $100 from me. There is one that works for some folks out there > by , but it does not work for me. where do you find this? > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ;_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 15:10:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id BD30937B825; Mon, 7 Aug 2000 15:10:12 -0700 (PDT) (envelope-from fanf@dotat.at) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13Lv5w-000DbQ-00; Mon, 07 Aug 2000 22:10:04 +0000 Date: Mon, 7 Aug 2000 22:10:04 +0000 From: Tony Finch To: Robert Watson Cc: Dennis , hackers@freebsd.org Subject: Re: FreeBSD belly up with big config Message-ID: <20000807221004.U24886@hand.dotat.at> References: <200008051708.NAA00486@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Watson wrote: > >I'd made some similar observations about the current lack of scalability >both in management of (struct ifnet) chains, and mountpoints in the file >system. When I had a brief look at the way mount points are handled I concluded that most of the time they were found via the vnode tree which is independent of the number of mounted filesystems. The list of mountpoints is only scanned rarely, when you are doing heavy stuff like mounting or unmounting a filesystem. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 18:10:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 236BF37B51B; Mon, 7 Aug 2000 18:10:17 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id VAA06151; Mon, 7 Aug 2000 21:11:42 -0400 (EDT) Message-Id: X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 07 Aug 2000 21:24:01 -0400 To: Mike Smith From: Dennis Subject: Re: FreeBSD belly up with big config Cc: hackers@freebsd.org In-Reply-To: <200008070654.XAA01626@mass.osd.bsdi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:54 PM 8/6/00 -0700, Mike Smith wrote: >> With 1800 interfaces in the system Freebsd seems to use about 50Mhz of cpu >> when idle in "interrupts" even when there are no interrupts to process. on >> a 500Mhz box it uses 10% of the cpu and it seems linear with different >> speed processors. >> >> the 1800 interfaces are 900 DLCIs on a T3 frame with 900 bridge groups >> (rather common for a DSL delivered via Frame). This with just one >> line...the same problem could occur with say 8 T1 lines with 100+ DLCIs on >> each. >> >> It seems that there is substantial overhead just scanning interfaces for >> some routine maintenance...is there any hope of alleviating this deboggle? > >Probably. Without some idea of what's actually happening, though, it's a >little hard to point a finger and say "look here". > >A profiling dump of the system when idle would be very illuminating, as >it'd give you a good idea of what's actually going on to use so much CPU How do I do this in 4.1? I have a test bed set up that demonstrates the problem. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 21:15:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-56.dsl.snfc21.pacbell.net [63.206.89.56]) by hub.freebsd.org (Postfix) with ESMTP id 3471B37B825 for ; Mon, 7 Aug 2000 21:15:50 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id VAA08691; Mon, 7 Aug 2000 21:27:12 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008080427.VAA08691@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@freebsd.org Subject: Re: FreeBSD belly up with big config In-reply-to: Your message of "Mon, 07 Aug 2000 21:24:01 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 21:27:12 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It seems that there is substantial overhead just scanning interfaces for > >> some routine maintenance...is there any hope of alleviating this deboggle? > > > >Probably. Without some idea of what's actually happening, though, it's a > >little hard to point a finger and say "look here". > > > >A profiling dump of the system when idle would be very illuminating, as > >it'd give you a good idea of what's actually going on to use so much CPU > > How do I do this in 4.1? I have a test bed set up that demonstrates the > problem. Config your kernel with '-pg', build and install. (See config(8)) Low-resolution profiling should be fine. Boot the new kernel, and when it's running use kgmon to grab a profiling dump for, say, 30 seconds. Then use gprof to translate the dump into readable output; at this point the flat profile is a good place to start to get a feel for where the code is busiest. Hope this helps. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 22:36:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 7A3FC37B72D; Mon, 7 Aug 2000 22:36:40 -0700 (PDT) (envelope-from knu@idaemons.org) Received: from daemon.local.idaemons.org (203-165-77-17.sugnm1.kt.home.ne.jp [203.165.77.17]) by ms.tokyo.jcom.ne.jp (8.9.3/3.7W 04/27/00) with ESMTP id OAA27125; Tue, 8 Aug 2000 14:36:36 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id OAA65922; Tue, 8 Aug 2000 14:36:04 +0900 (JST) Date: Tue, 08 Aug 2000 14:36:02 +0900 Message-ID: <86bsz4co1p.wl@localhost.local.idaemons.org> From: "Akinori -Aki- MUSHA" To: "Vladimir N. Silyaev" Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG, emulation@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess In-Reply-To: In your message of "Sun, 6 Aug 2000 23:23:39 -0400" <20000806232339.A3251@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> <20000806232339.A3251@jupiter.delta.ny.us> User-Agent: Wanderlust/2.3.0 (Roam) EMIKO/1.13.12 (Euglena sociabilis) FLIM/1.13.2 (Kasanui) APEL/10.2 MULE XEmacs/21.1 (patch 11) (Carlsbad Caverns) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 1BEF D9B2 BABD 25D7 659A FD08 89C2 F3BE E981 4E16 MIME-Version: 1.0 (generated by EMIKO 1.13.12 - "Euglena sociabilis") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At a quick glance, "start_bridge" doesn't seem to have chance to be 1, does it? And, what's the difference among those three values of "bridge"? > + bridge="_bridge_on" > + bridge="_bridge" > + bridge="_bridge_off" -- / /__ __ / ) ) ) ) / Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org "We're only at home when we're on the run, on the wing, on the fly" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 7 23:28:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id D583137B565 for ; Mon, 7 Aug 2000 23:28:20 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115205>; Tue, 8 Aug 2000 16:27:56 +1000 Content-return: prohibited Date: Tue, 08 Aug 2000 16:27:52 +1000 From: Peter Jeremy Subject: VLAN Support in FreeBSD To: hackers@FreeBSD.ORG Cc: dgilbert@velocet.ca Message-Id: <00Aug8.162756est.115205@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About a month ago, David Gilbert started a thread in freebsd-stable about supporting a 1500MTU through a VLAN trunk (see Message-ID: <14689.22689.894466.908666@trooper.velocet.net>). Since this would be very useful to me, I did some digging into it and looked through the code (there being no other documentation). As far as I can tell from the code, the only thing restricting VLAN over ethernet devices to an MTU of 1496 is the code deleted in the following patch. Based on references to if_mtu, ifi_mtu, if_hdrlen and ifi_hdrlen, there is nothing in the system which will get upset if the MTU+hdrlen on the VLAN interface is more than the MTU+hdrlen on the trunk interface (the VLAN parent). When I try this in practise, I can send 1500 byte packets without problem, but when a 1500 byte packet is sent to me, it never arrives (at least at bpf_tap() on the trunk interface). Unfortunately, I can't tell (at this stage) whether this is a problem with the 3Com 3C905 NIC, or the switch. (There's no problem with shorter packets). Has anyone else played with VLAN's in FreeBSD? Does anyone know which (if any) NICs are likely to object to receiving VLAN trunk frames (1522 instead of 1518 bytes). Index: if_vlan.c =================================================================== RCS file: /home/CVSROOT/src/sys/net/if_vlan.c,v retrieving revision 1.18 diff -u -r1.18 if_vlan.c --- if_vlan.c 2000/07/13 22:54:30 1.18 +++ if_vlan.c 2000/08/08 06:11:02 @@ -356,11 +356,7 @@ if (ifv->ifv_p) return EBUSY; ifv->ifv_p = p; - if (p->if_data.ifi_hdrlen == sizeof(struct ether_vlan_header)) - ifv->ifv_if.if_mtu = p->if_mtu; - else - ifv->ifv_if.if_mtu = p->if_data.ifi_mtu - EVL_ENCAPLEN; - + ifv->ifv_if.if_mtu = p->if_mtu; /* * Preserve the state of the LINK0 flag for ourselves. */ Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 2:32:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id EB94037BFFF; Tue, 8 Aug 2000 02:32:24 -0700 (PDT) (envelope-from danny@cs.huji.ac.il) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13M5kB-0002Zk-00; Tue, 08 Aug 2000 12:32:19 +0300 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.03 #1) id 13M5kA-0001Zs-00; Tue, 08 Aug 2000 12:32:18 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: "Vladimir N. Silyaev" Cc: emulation@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: vmware ... In-reply-to: Your message of Sun, 6 Aug 2000 23:23:39 -0400 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Aug 2000 12:32:18 +0300 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, im trying to 'install' vmware, and im missing if_tap.ko, can someone point me in the right direction? danny PS: it's FreeBSD 4.1-RELEASE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 4:15:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id E3F5637B60B; Tue, 8 Aug 2000 04:15:52 -0700 (PDT) (envelope-from vsilyaev@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny5-11.ix.netcom.com [198.211.17.11]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id HAA11918; Tue, 8 Aug 2000 07:15:49 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id HAA00414; Tue, 8 Aug 2000 07:15:47 -0400 (EDT) (envelope-from vsilyaev) Date: Tue, 8 Aug 2000 07:15:46 -0400 From: "Vladimir N. Silyaev" To: Akinori -Aki- MUSHA Cc: Robert Watson , freebsd-hackers@FreeBSD.ORG, security-officer@FreeBSD.ORG, emulation@FreeBSD.ORG Subject: Re: vmware changes result in nasty bridging mess Message-ID: <20000808071546.C360@jupiter.delta.ny.us> References: <200008032335.TAA01440@jupiter.delta.ny.us> <20000806232339.A3251@jupiter.delta.ny.us> <86bsz4co1p.wl@localhost.local.idaemons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86bsz4co1p.wl@localhost.local.idaemons.org>; from knu@idaemons.org on Tue, Aug 08, 2000 at 02:36:02PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 02:36:02PM +0900, Akinori -Aki- MUSHA wrote: > At a quick glance, "start_bridge" doesn't seem to have chance to be 1, > does it? It's depend. I'm pretty tired that discussian about bridging. So if people want to use bridge let set start_bridge to 1, if not leave it in zero. Also it's possible to setup that value at configuration stage, whatever. > And, what's the difference among those three values of > "bridge"? To diagnostic current behaviour about bridging. > > > + bridge="_bridge_on" Startup script configured do not touch bridging and at the time when script starting, bridging was enabled. > > + bridge="_bridge_off" /.../ disabled. > > > + bridge="_bridge" Script configured to setup bridging and did successfully When bridge == "" its means that kernel compiled without bridging support, or outdated kernel. -- Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 5:42:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 2690A37B8F1; Tue, 8 Aug 2000 05:42:22 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: NO-IDENT-SERVICE [port 1422]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <111641-226>; Tue, 8 Aug 2000 14:42:15 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 3F9641362C; Tue, 8 Aug 2000 14:42:02 +0200 (CEST) From: Daniel Lang To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Installation Problems on Dell PowerEdge 6100/200 Message-ID: <20000808144202.A14579@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Date: Tue, 8 Aug 2000 14:42:04 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, we've got a Dell PowerEdge 6100/200 here, which is an older SMP server, featuring 4 PPro 200 CPU's two internal AIC7880 channels and an Adaptec 2940UW PCI controller. One of the AIC's is connected to a SCA Backplane that holds 4 disks. Now before even having a chance to see if FreeBSD-SMP works with this box, I didn't manage to install FreeBSD (4.1) correctly. Well, installation seems to go well in any attempt: - Floppy boots, Kernel finds all ahc's and disks - Installation seems to succeed (Partitioning, installation, etc) But then, the machine won't boot. It seems to happen, that the MBR of the target device (da0, which is the first disk on the second controller, channel A of internal AIC's) is found, but the next stage of the bootstrapping process cannot be found. I played also around using boot0 and installing on other disks, this is like what I got: Standard MBR and System on da0: -> Missing operating system boot0 MBR and System on da0: -> F1 -> *beep* (nothing else) boot0 MBR (and old System) on da0, standard MBR and System on da1: booting from da0: F1 -> *beep*, F5 (disk2) -> Missing operating system booting from da1: -> Missing operating system So it seems no boot-block after the MBR can be found. I tried: - installing and booting from different disks on internal ahc - disabling some of the controllers - installing and booting from a disk on the 2940, as well while disabling the others It all had no effect. All adaptec's BIOS has Disks > 1GB and INT13 enabled (of course the BIOS itself is enabled, too) Previously Solaris 7/x86 was running on this machine, there were no such problems, but we don't really want to run Solaris... :-} Any clue ? Many thanks, Daniel -- IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you will be approximated. - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* -- IRCnet: Mr-Spock - May His Shadow fall upon thee - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6: 0:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id 68F1837B909; Tue, 8 Aug 2000 06:00:29 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from flf960r1.ems.att.com ([135.71.244.37]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA22074; Tue, 8 Aug 2000 09:00:19 -0400 (EDT) Received: from mo3980bh3.ems.att.com by flf960r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id IAA13704; Tue, 8 Aug 2000 08:56:16 -0400 (EDT) Received: by mo3980bh3.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Tue, 8 Aug 2000 08:00:18 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Danny Braniss'" , "Vladimir N. Silyaev" Cc: emulation@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: RE: vmware ... Date: Tue, 8 Aug 2000 08:00:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > im trying to 'install' vmware, and im missing > if_tap.ko, can someone > point me in the right direction? the tap (if_tap.ko) driver is part of -current and RELENG_4. it was not included in 4.1-RC. should you need to use it, please, download sources from -current or RELENG_4 and compile it. i hope it will be included in the next release. thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6:52:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id D250E37BD84 for ; Tue, 8 Aug 2000 06:52:26 -0700 (PDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id IAA28788 for freebsd-hackers@freebsd.org; Tue, 8 Aug 2000 08:52:26 -0500 (CDT) (envelope-from bob) Date: Tue, 8 Aug 2000 08:52:25 -0500 From: Bob Willcox To: hackers list Subject: How do I change serial console tty speed? Message-ID: <20000808085225.A27718@luke.immure.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I have tried everything I could think of to raise the speed of my system's serial console from 9600 baud to something faster w/o any success. The things that I have tried are: setting "options CONSPEED=38400" in my kernel config file and putting a "set CONSPEED=38400" in the /boot/loader.rc file to no avail. No doubt I am missing something. Any help would be greatly appreciated! Thanks, Bob -- Bob Willcox Man usually avoids attributing cleverness to somebody else -- bob@immure.com unless it is an enemy. Austin, TX -- A. Einstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6:53:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from animaths.com (AMontsouris-101-2-95.abo.wanadoo.fr [193.251.54.95]) by hub.freebsd.org (Postfix) with SMTP id 61CC037B6B3 for ; Tue, 8 Aug 2000 06:53:49 -0700 (PDT) (envelope-from nicolas.leonard@animaths.com) Received: (qmail 18535 invoked by uid 31); 8 Aug 2000 13:56:41 -0000 Received: from nicolas.leonard@animaths.com by ns.masa.com with scan4virus-0.53 (uvscan: v4.0.50/v4088. . Clean. Processed in 0.227266 secs); 08/08/2000 15:56:41 Received: from nld.masa.com (HELO nld) (172.16.2.15) by ns.masa.com with SMTP; 8 Aug 2000 13:56:41 -0000 Message-ID: <00f101c00140$2a4b5a50$0f0210ac@masa.com> From: "Nicolas Leonard" To: Subject: How to generate a core dump explicily Date: Tue, 8 Aug 2000 15:54:26 +0200 Organization: =?Windows-1252?Q?Math=E9matiques_Appliqu=E9es_SA?= MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I would like to generate a core dump 'explicitly' in my program. How can that be done ? Thanks. Leon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6:54: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.immure.com (luke.immure.com [207.8.42.74]) by hub.freebsd.org (Postfix) with ESMTP id 0DA1437B6B3 for ; Tue, 8 Aug 2000 06:54:00 -0700 (PDT) (envelope-from bob@luke.immure.com) Received: (from bob@localhost) by luke.immure.com (8.9.3/8.9.3) id IAA28825 for freebsd-hackers@freebsd.org; Tue, 8 Aug 2000 08:53:59 -0500 (CDT) (envelope-from bob) Date: Tue, 8 Aug 2000 08:53:59 -0500 From: Bob Willcox To: hackers list Subject: Re: How do I change serial console tty speed? Message-ID: <20000808085359.B27718@luke.immure.com> Reply-To: Bob Willcox References: <20000808085225.A27718@luke.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000808085225.A27718@luke.immure.com>; from bob@luke.immure.com on Tue, Aug 08, 2000 at 08:52:25AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, I forgot to add that this is on a 4.0-stable system (from about 3 months ago). Thanks again, Bob On Tue, Aug 08, 2000 at 08:52:25AM -0500, Bob Willcox wrote: > Hi All, > > I have tried everything I could think of to raise the speed of my > system's serial console from 9600 baud to something faster w/o > any success. The things that I have tried are: setting "options > CONSPEED=38400" in my kernel config file and putting a "set > CONSPEED=38400" in the /boot/loader.rc file to no avail. > > No doubt I am missing something. > > Any help would be greatly appreciated! > > Thanks, > Bob > > -- > Bob Willcox Man usually avoids attributing cleverness to somebody else -- > bob@immure.com unless it is an enemy. > Austin, TX -- A. Einstein -- Bob Willcox Man usually avoids attributing cleverness to somebody else -- bob@immure.com unless it is an enemy. Austin, TX -- A. Einstein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6:56:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id B433537B7EC for ; Tue, 8 Aug 2000 06:56:54 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 0C1FD19090; Tue, 8 Aug 2000 15:56:53 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id 352FA2C5; Tue, 8 Aug 2000 15:56:51 +0200 (CEST) Date: Tue, 8 Aug 2000 15:56:50 +0200 To: Nicolas Leonard Cc: hackers@freebsd.org Subject: Re: How to generate a core dump explicily References: <00f101c00140$2a4b5a50$0f0210ac@masa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00f101c00140$2a4b5a50$0f0210ac@masa.com>; from nicolas.leonard@animaths.com on Tue, Aug 08, 2000 at 03:54:26PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-08-08-15-56-50+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8/08, Nicolas Leonard wrote: | I would like to generate a core dump 'explicitly' in | my program. How can that be done ? Use abort(3). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 6:59:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id CB0F937B9E1 for ; Tue, 8 Aug 2000 06:59:33 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 3E7949B03; Tue, 8 Aug 2000 09:59:32 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 32F89BA11; Tue, 8 Aug 2000 09:59:32 -0400 (EDT) Date: Tue, 8 Aug 2000 09:59:32 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Bob Willcox Cc: hackers list Subject: Re: How do I change serial console tty speed? In-Reply-To: <20000808085225.A27718@luke.immure.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Bob Willcox wrote: > Hi All, > > I have tried everything I could think of to raise the speed of my > system's serial console from 9600 baud to something faster w/o > any success. The things that I have tried are: setting "options > CONSPEED=38400" in my kernel config file and putting a "set > CONSPEED=38400" in the /boot/loader.rc file to no avail. > See /etc/defaults/make.conf WRT BOOT_COMCONSOLE_SPEED, set the appropriate value in /etc/make.conf, and compile/install the boot blocks. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 7: 9:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 9DEE937B79C for ; Tue, 8 Aug 2000 07:09:43 -0700 (PDT) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id C6F68174FC; Tue, 8 Aug 2000 16:09:36 +0200 (MET DST) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id QAA33246; Tue, 8 Aug 2000 16:09:36 +0200 (CEST) (envelope-from fn@gatekeeper.radio-do.de) Date: Tue, 8 Aug 2000 16:09:36 +0200 From: Frank Nobis To: Nicolas Leonard Cc: hackers@FreeBSD.ORG Subject: Re: How to generate a core dump explicily Message-ID: <20000808160936.A33231@radio-do.de> References: <00f101c00140$2a4b5a50$0f0210ac@masa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <00f101c00140$2a4b5a50$0f0210ac@masa.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Aug 08, 2000 at 03:54:26PM +0200, Nicolas Leonard wrote: > Hi, > > I would like to generate a core dump 'explicitly' in > my program. How can that be done ? Send yourself a signal that creates a core dump. For example SIGQUIT would do the job. This asumes that you have not hanged the default behaviour of the signals you are willing to receive in your program. man signal, kill, getpid are your friends. kill(getpid(),SIGQUIT) should be ok. Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 7:10: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id 27C7437BDCA for ; Tue, 8 Aug 2000 07:09:46 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA27596; Tue, 8 Aug 2000 10:09:29 -0400 (EDT) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA20328; Tue, 8 Aug 2000 10:07:10 -0400 (EDT) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Tue, 8 Aug 2000 10:08:23 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Nicolas Leonard'" , hackers@FreeBSD.ORG Subject: RE: How to generate a core dump explicily Date: Tue, 8 Aug 2000 10:08:20 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man abort > I would like to generate a core dump 'explicitly' in > my program. How can that be done ? thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 7:41: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from animaths.com (AMontsouris-101-2-95.abo.wanadoo.fr [193.251.54.95]) by hub.freebsd.org (Postfix) with SMTP id 5207337B98A for ; Tue, 8 Aug 2000 07:41:02 -0700 (PDT) (envelope-from nicolas.leonard@animaths.com) Received: (qmail 19356 invoked by uid 31); 8 Aug 2000 14:44:01 -0000 Received: from nicolas.leonard@animaths.com by ns.masa.com with scan4virus-0.53 (uvscan: v4.0.50/v4088. . Clean. Processed in 0.223277 secs); 08/08/2000 16:44:01 Received: from nld.masa.com (HELO nld) (172.16.2.15) by ns.masa.com with SMTP; 8 Aug 2000 14:44:01 -0000 Message-ID: <011301c00146$c709f170$0f0210ac@masa.com> From: "Nicolas Leonard" To: "Samuel Tardieu" Cc: References: <00f101c00140$2a4b5a50$0f0210ac@masa.com> <2000-08-08-15-56-50+trackit+sam@inf.enst.fr> Subject: Re: How to generate a core dump explicily Date: Tue, 8 Aug 2000 16:41:46 +0200 Organization: =?iso-8859-1?Q?Math=E9matiques_Appliqu=E9es_SA?= MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry, I wasn't precise enough . In fact, I caught the SIGABRT signal (and the others signals which are ending the program) and I'm doing some ending stuff, and after that, I would like to dump a core file. I could remove the handler of SIGABRT after my ending suff done, and kill myself another time, but I would like to know if it's possible to dump the core explicitly. (With a dumpcore() function or whatever ) ----- Message d'origine ----- De : Samuel Tardieu À : Nicolas Leonard Cc : Envoyé : mardi 8 août 2000 15:56 Objet : Re: How to generate a core dump explicily > On 8/08, Nicolas Leonard wrote: > > | I would like to generate a core dump 'explicitly' in > | my program. How can that be done ? > > Use abort(3). > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 7:50: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id EC7EA37B9AA for ; Tue, 8 Aug 2000 07:50:03 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id DDC9619015; Tue, 8 Aug 2000 16:49:58 +0200 (CEST) Received: by antinea.enst.fr (Postfix, from userid 1000) id CC25F2C5; Tue, 8 Aug 2000 16:49:57 +0200 (CEST) Date: Tue, 8 Aug 2000 16:49:56 +0200 To: Nicolas Leonard Cc: hackers@freebsd.org Subject: Re: How to generate a core dump explicily References: <00f101c00140$2a4b5a50$0f0210ac@masa.com> <2000-08-08-15-56-50+trackit+sam@inf.enst.fr> <011301c00146$c709f170$0f0210ac@masa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <011301c00146$c709f170$0f0210ac@masa.com>; from nicolas.leonard@animaths.com on Tue, Aug 08, 2000 at 04:41:46PM +0200 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-08-08-16-49-57+trackit+sam@inf.enst.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8/08, Nicolas Leonard wrote: | Sorry, I wasn't precise enough . | | In fact, I caught the SIGABRT signal (and the others signals which are | ending the program) | and I'm doing some ending stuff, and after that, I would like to dump a core | file. | | I could remove the handler of SIGABRT after my ending suff done, and kill | myself another | time, but I would like to know if it's possible to dump the core explicitly. | (With a dumpcore() | function or whatever ) You better remove the handler of SIGABRT then call abort(), which will not only send the SIGABRT again and dump a core but also flush all your buffers (look at /usr/src/lib/libc/stdlib/abort.c). But why don't you just use atexit(3) for registering your cleaning stuff, and let SIGABRT with its default handling? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 8: 6:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id AD67837B5AE for ; Tue, 8 Aug 2000 08:06:14 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 660985D1C; Tue, 8 Aug 2000 17:06:11 +0200 (CEST) Date: Tue, 8 Aug 2000 17:06:11 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Peter Jeremy Cc: hackers@FreeBSD.ORG, dgilbert@velocet.ca Subject: Re: VLAN Support in FreeBSD In-Reply-To: <00Aug8.162756est.115205@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As far as I can tell from the code, the only thing restricting VLAN > over ethernet devices to an MTU of 1496 is the code deleted in the > following patch. Based on references to if_mtu, ifi_mtu, if_hdrlen > and ifi_hdrlen, there is nothing in the system which will get upset > if the MTU+hdrlen on the VLAN interface is more than the MTU+hdrlen > on the trunk interface (the VLAN parent). Take a look at: http://www.euitt.upm.es/~pjlobo/fbsdvlan.html Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 8:47:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 4197637B7E8 for ; Tue, 8 Aug 2000 08:47:41 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id IAA83823; Tue, 8 Aug 2000 08:47:22 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <39902AC7.CB39BCD8@owp.csus.edu> Date: Tue, 08 Aug 2000 08:44:08 -0700 From: Joseph Scott X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Julian Elischer Cc: Alan Clegg , Andrzej Bialecki , Cameron Grant , freebsd-hackers@FreeBSD.ORG Subject: Re: US$100 prize for adding ESS Audiodrive support to pcm References: <004501bffb0b$27bf8c60$0504020a@haveblue> <20000805155806.A94702@diskfarm.firehouse.net> <398F3081.167EB0E7@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Alan Clegg wrote: > > > > On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly > [...] > > Add $100 from me. There is one that works for some folks out there > > by , but it does not work for me. > > where do you find this? I'm not sure about Alan, but I got it from an email from Taku YAMAMOTO . I've included the email below. One thing to note, myself and a few others have only been able to get sound to work out of the audio out jack. For some reason the internal speakers just don't work. I've played with the settings on the notebook quite a bit, and they do still work when I boot into Windows. However, sound, even without the internal speakers, is better than no sound at all :-) --- I've written up Maestro driver (beta, mixer and playback). Please test it. But this is beta quality and may have lots of problems. Beware! To install: 0. Get driver source tarball from: http://access.cent.saitama-u.ac.jp/~taku/freebsd/maestro/releng4-20000725.tar.gz 1. Check MD5 checksum if you want. MD5 (releng4-20000725.tar.gz) = b42179b09016d2cf77055ae559395a67 2. If your kernel doesn't have device pcm, add following line to your config and recompile: device pcm 3. Untar the archive. 4. cd to maestro, make and make install. If you get errors, unter the archive under sys/modules and retry. 5. Your card is not a Maestro-2E, you can kldload maestro without reboot. Otherwise, add following to /boot/loader.conf and reboot: maestro_load="YES" 6. Enjoy. 7. When you find problems, please mail to me :) The driver can also be statically linked to your kernel. Just FYI. Good luck. --- -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 9: 4:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id DD5F237B7E8 for ; Tue, 8 Aug 2000 09:04:39 -0700 (PDT) (envelope-from mitja@hermes.si) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id SAA06442 for ; Tue, 8 Aug 2000 18:04:31 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id SAA20206 for ; Tue, 8 Aug 2000 18:04:27 +0200 Received: from akira.hermes.si(10.17.1.122) by primus.hermes.si via smap (V2.1) id xma019113; Tue, 8 Aug 00 18:03:10 +0200 Received: from lamu.hermes.si (lamu.hermes.si [10.17.1.230]) by akira.hermes.si with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id SAA11004 for ; Tue, 8 Aug 2000 18:06:21 +0200 (METDST) Message-Id: <200008081606.SAA11004@akira.hermes.si> Date: Tue, 08 Aug 2000 18:03:08 CEST From: Mitja Horvat To: freebsd-hackers@freebsd.org Subject: 4.1-RELEASE problem writing to async mounted filesystem Reply-To: mitja.horvat@hermes.si X-Mailer: Spruce 0.6.5 for X11 w/smtpio 0.7.9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently upgraded to FreeBSD 4.1-RELEASE(CD image). I noticed that while writing to an asynchronously mounted filesystem(mount -o async / ...) all other IO operations to the FS are almost blocked. I have only one asynchronously mounted partition(/) and the following shell script makes the machine unresponsive so I cannot even telnet to it: while true; do rm -f foo; dd if=/dev/zero of=foo bs=1024k count=256; done 4.0-RELEASE does a much better job at handling similar situations... I'm using softupdates, but even without them the problem persists. This does not happen if the fs is mounted synchronously, but I also get MUCH slower IO throughput(800kb/s compared to 12MB/s with async). I know that mounting filesystems asynchronously is dangerous, but this is my workstation and is being backed up on a daily basis, so a filesystem crash is not something I'm worried about... I suspect this is something related to the buffer code and currently have no much time to inspect that. Can somebody give me a hint how to solve the problem? Thank you, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 9:26:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.superscript.com (zeus.superscript.com [206.234.89.16]) by hub.freebsd.org (Postfix) with SMTP id D249737B585 for ; Tue, 8 Aug 2000 09:26:20 -0700 (PDT) (envelope-from web@superscript.com) Received: (qmail 28988 invoked by uid 1008); 8 Aug 2000 16:26:02 -0000 Date: Tue, 8 Aug 2000 11:26:02 -0500 From: "William E. Baxter" To: freebsd-hackers@freebsd.org Subject: getpeereid() syscall patch for FreeBSD 4.0 Message-ID: <20000808112602.A17676@zeus.superscript.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A patch implementing a getpeereid() syscall in FreeBSD 4.0 is available at http://www.superscript.com/patches/freebsd_4_0.getpeereid A local-domain server uses getpeereid() to obtain client credentials. Based on getpeereid() I created ucspi-ipc, a local-domain analogue to Dan Bernstein's ucspi-tcp. The project came about after I read the "Wiping out setuid programs" discussion the the BugTraq archives. At present, ucspi-ipc runs on patched OpenBSD, patched FreeBSD, and on Linux kernels that support SO_PEERCRED with getsockopt(). Using ucspi-ipc, you can easily create local-domain client/server programs that allow privileged servers to act on behalf of nonprivileged clients. No setuid programs are required, and access is configurable, based on client user and group ID. For ucspi-ipc documentation, links to the relevant background information, patches, and information about the ucspi mailing list, please visit the ucspi-ipc home page at http://www.superscript.com/ucspi-ipc/intro.html I'd like to see getpeereid(), or sufficient basis for it, incorporated into future FreeBSD releases, so that we can all use ucspi-ipc without the need for a kernel patch. Regards, W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 9:30:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.rdc1.sfba.home.com (mail1.rdc1.sfba.home.com [24.0.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 84E3837B5CE for ; Tue, 8 Aug 2000 09:30:54 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail1.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000808163054.IXYM28364.mail1.rdc1.sfba.home.com@beastie.localdomain> for ; Tue, 8 Aug 2000 09:30:54 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id JAA96303 for freebsd-hackers@freebsd.org; Tue, 8 Aug 2000 09:31:19 -0700 (PDT) (envelope-from brian) Date: Tue, 8 Aug 2000 09:31:19 -0700 From: "Brian O'Shea" To: freebsd-hackers@freebsd.org Subject: Hardware suppported needed by reboot(2) for RB_POWEROFF Message-ID: <20000808093119.C351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, For the record, I am running FreeBSD-CURRENT from August 2: # uname -a FreeBSD panic.localdomain 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Aug 2 17:55:17 PDT 2000 root@panic.localdomain:/usr/obj/usr/local/cvsup/cur rent/src/sys/PANIC i386 What is the interface used by the reboot() system call to power off the machine when the RB_POWEROFF flag is set? The man page makes mention of hardware support, but doesn't specify what that support is, or how to use it. Thanks, -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 9:35:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4629637B5CE for ; Tue, 8 Aug 2000 09:35:37 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e78GZSw10339; Tue, 8 Aug 2000 09:35:28 -0700 (PDT) Date: Tue, 8 Aug 2000 09:35:28 -0700 From: Alfred Perlstein To: "William E. Baxter" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: getpeereid() syscall patch for FreeBSD 4.0 Message-ID: <20000808093527.D4854@fw.wintelcom.net> References: <20000808112602.A17676@zeus.superscript.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000808112602.A17676@zeus.superscript.com>; from web@superscript.com on Tue, Aug 08, 2000 at 11:26:02AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * William E. Baxter [000808 09:27] wrote: > A patch implementing a getpeereid() syscall in FreeBSD 4.0 is > available at > > http://www.superscript.com/patches/freebsd_4_0.getpeereid > > A local-domain server uses getpeereid() to obtain client credentials. > Based on getpeereid() I created ucspi-ipc, a local-domain analogue to > Dan Bernstein's ucspi-tcp. The project came about after I read the > "Wiping out setuid programs" discussion the the BugTraq archives. At > present, ucspi-ipc runs on patched OpenBSD, patched FreeBSD, and on > Linux kernels that support SO_PEERCRED with getsockopt(). I haven't used the credential passing feature of sendmsg(), but I was wondering what advantages this has over being able to pass kernel verified id's through a unix domain socket using SCM_CREDS. My reading of UNP seems to indicate that it offers the same features. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10: 0:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C931637B5C3 for ; Tue, 8 Aug 2000 10:00:19 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id NAA01387 for ; Tue, 8 Aug 2000 13:00:18 -0400 (EDT) Date: Tue, 8 Aug 2000 12:57:27 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: bridge driver and Yamaha YMF 724 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does 4.1-Release support YAMAHA PCI Audio Controller YMF 724? I have tried the suggestion given by man pcm without success. By the way, what is a card with bridge driver support and a PnP card as mentioned by man pcm? Thanks for your help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10: 1:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bsa-1-as01-7-a46.gd.uol.com.br (bsa-1-as01-7-a46.gd.uol.com.br [200.197.118.46]) by hub.freebsd.org (Postfix) with ESMTP id E3E6237B7DE for ; Tue, 8 Aug 2000 10:01:43 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 16145 invoked by uid 1001); 8 Aug 2000 16:36:03 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Tue, 8 Aug 2000 13:35:41 -0300 To: freebsd-hackers@freebsd.org Subject: make release: how I do make it into a bootable cd? Message-ID: <20000808133541.B9262@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I know I should know better. Please do not flame me. Well, I did a good 1st make release on my little stable (cvsupped 07/08/2000) machine. I have disc[12] under cdrom. Everything looks fine. But .... (there is always a but) Does anyone have a 'burn the CD' cookbook? This is what I have so far (pretty obvious); of course, the same applies to disc2. 1) mkisofs -o disc1.iso -R -J disc1 - create a filesystem with RockRidge and Joliet extensions 2) cdrecord -v speed=s4 dev=something disc1.iso However, I have a few doubts: 1) What sort of device should I use? cdrecord -scanbus is not returning anything. I am trying to use an ATAPI recorder but I do not know what to use. Besides, what should I use for my cdrom reader? Trying /dev/acd0c for my recorder returns -- Cdrecord 1.9 (i386-unknown-freebsd4.1) Copyright (C) 1995-2000 Jörg Schilling cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. --- I am running it as root. Odd. --- ahc0: port 0xb800-0xb8ff mem 0xe8040000-0xe8040fff irq 5 at device 9.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs acd0: CD-RW at ata1-master using PIO3 cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device --- dmesg useful info --- FreeBSD Fedaykin.here 4.1-STABLE FreeBSD 4.1-STABLE #0: Sun Aug 7 14:13:58 BRT 2000 root@Fedaykin.here:/usr/obj/usr/src/sys/LIOUX i386 --- uname -a 1) (cont.) I could use burncd but I am bugged by the fact that I can't use cdrecord. :) The devices are a Sony CRX100 CDR and a Plextor Ultraplex 40max CDRom. 2) How do I make it a full-fledged FreeBSD bootable distribution CDRom? I mean, where do I get the el-torrito boot image? How do I make it use it and then run sysinstall seamlessly? Just like a disc1 from distribution. Well, FreeBSD distribution won't be comming to town anytime soon and I only have a 33.6K connection to the internet; therefore, this would really prove handy while I wait. Can I try the /boot/cdboot stuff or the floppies/boot.flp as a boot image? 3) Any tips to make it a complete distribution CDRom are welcome. Regards, Mario Ferreira ps: Looks like this belongs in, yet, another FAQ entry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10: 4:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-56.dsl.snfc21.pacbell.net [63.206.89.56]) by hub.freebsd.org (Postfix) with ESMTP id 7592937BA37 for ; Tue, 8 Aug 2000 10:04:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id KAA12467; Tue, 8 Aug 2000 10:15:52 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008081715.KAA12467@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: boshea@ricochet.net Cc: freebsd-hackers@freebsd.org Subject: Re: Hardware suppported needed by reboot(2) for RB_POWEROFF In-reply-to: Your message of "Tue, 08 Aug 2000 09:31:19 PDT." <20000808093119.C351@beastie.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Aug 2000 10:15:52 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > For the record, I am running FreeBSD-CURRENT from August 2: > > # uname -a > FreeBSD panic.localdomain 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Aug 2 > 17:55:17 PDT 2000 root@panic.localdomain:/usr/obj/usr/local/cvsup/cur > rent/src/sys/PANIC i386 > > What is the interface used by the reboot() system call to power off the > machine when the RB_POWEROFF flag is set? The man page makes mention of > hardware support, but doesn't specify what that support is, or how to > use it. That's platform-dependant. On the x86, a conforming APM BIOS is required (or a device driver with a suitable hook for some other control interface). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10:19:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.superscript.com (zeus.superscript.com [206.234.89.16]) by hub.freebsd.org (Postfix) with SMTP id 47FAD37BA5A for ; Tue, 8 Aug 2000 10:19:08 -0700 (PDT) (envelope-from web@superscript.com) Received: (qmail 10929 invoked by uid 1008); 8 Aug 2000 17:18:49 -0000 Date: Tue, 8 Aug 2000 12:18:49 -0500 From: "William E. Baxter" To: freebsd-hackers@FreeBSD.ORG Cc: bright@wintelcom.net Subject: Re: getpeereid() syscall patch for FreeBSD 4.0 Message-ID: <20000808121849.A27414@zeus.superscript.com> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG, bright@wintelcom.net References: <20000808112602.A17676@zeus.superscript.com> <20000808093527.D4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000808093527.D4854@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Aug 08, 2000 at 09:35:28AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With getpeereid() the credentials are passed at connect() and do not require the client to send data. Therefore clients cannot consume connections anonymously. W. On Tue, Aug 08, 2000 at 09:35:28AM -0700, Alfred Perlstein wrote: > > I haven't used the credential passing feature of sendmsg(), but I > was wondering what advantages this has over being able to pass > kernel verified id's through a unix domain socket using SCM_CREDS. > My reading of UNP seems to indicate that it offers the same features. > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10:28:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from redsun.nsl.ru (redsun.nsl.ru [195.210.168.7]) by hub.freebsd.org (Postfix) with ESMTP id A26DB37B80A for ; Tue, 8 Aug 2000 10:28:37 -0700 (PDT) (envelope-from rulgand@redsun.nsl.ru) Received: (from root@localhost) by redsun.nsl.ru (8.9.3/8.9.3) id VAA00799; Tue, 8 Aug 2000 21:28:07 +0400 (MSD) (envelope-from rulgand) Date: Tue, 8 Aug 2000 21:28:07 +0400 (MSD) From: "Alexey V. Antipovsky" Message-Id: <200008081728.VAA00799@redsun.nsl.ru> To: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-URL: file://localhost/usr/share/doc/en_US.ISO_8859-1/books/handbook/contrib.html X-Mailer: Lynx, Version 2.8.2rel.1 Subject: subscribe alexey@nsl.ru Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe alexey@nsl.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10:31:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from goldgate.nsl.ru (goldgate.nsl.ru [195.210.169.1]) by hub.freebsd.org (Postfix) with ESMTP id D8C6637B7C7 for ; Tue, 8 Aug 2000 10:31:36 -0700 (PDT) (envelope-from root@nsl.ru) Received: from redsun.nsl.ru (redsun.nsl.ru [195.210.168.7]) by goldgate.nsl.ru (8.9.3/8.9.3) with ESMTP id VAA02603 for ; Tue, 8 Aug 2000 21:31:58 +0400 (MSD) (envelope-from root@nsl.ru) Date: Tue, 8 Aug 2000 21:31:12 +0400 (MSD) From: Charlie ROOT To: freebsd-hackers@FreeBSD.org Subject: subscribe alexey@nsl.ru Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe alexey@nsl.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 10:44: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phobos.illtel.denver.co.us (dsl-206.169.4.82.wenet.com [206.169.4.82]) by hub.freebsd.org (Postfix) with ESMTP id E205C37B51D for ; Tue, 8 Aug 2000 10:44:00 -0700 (PDT) (envelope-from abelits@phobos.illtel.denver.co.us) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.9.3/8.9.3) with ESMTP id KAA01645; Tue, 8 Aug 2000 10:43:51 -0700 Date: Tue, 8 Aug 2000 10:43:51 -0700 (PDT) From: Alex Belits To: alexey@nsl.ru Cc: freebsd-hackers@FreeBSD.org Subject: Re: subscribe alexey@nsl.ru In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Charlie ROOT wrote: > Date: Tue, 8 Aug 2000 21:31:12 +0400 (MSD) > From: Charlie ROOT > To: freebsd-hackers@FreeBSD.org > Subject: subscribe alexey@nsl.ru > > subscribe alexey@nsl.ru > Users started "subscribing" in this manner? Congratulations, FreeBSD is officially mainstream. -- Alex ---------------------------------------------------------------------- Excellent.. now give users the option to cut your hair you hippie! -- Anonymous Coward To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 11:24:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 4AE3037B5AE; Tue, 8 Aug 2000 11:24:26 -0700 (PDT) Subject: Re: getpeereid() syscall patch for FreeBSD 4.0 In-Reply-To: <20000808093527.D4854@fw.wintelcom.net> from Alfred Perlstein at "Aug 8, 2000 09:35:28 am" To: bright@wintelcom.net (Alfred Perlstein) Date: Tue, 8 Aug 2000 11:24:26 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000808182426.4AE3037B5AE@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * William E. Baxter [000808 09:27] wrote: > > A patch implementing a getpeereid() syscall in FreeBSD 4.0 is > > available at > > > > http://www.superscript.com/patches/freebsd_4_0.getpeereid > > > > A local-domain server uses getpeereid() to obtain client credentials. > > Based on getpeereid() I created ucspi-ipc, a local-domain analogue to > > Dan Bernstein's ucspi-tcp. The project came about after I read the > > "Wiping out setuid programs" discussion the the BugTraq archives. At > > present, ucspi-ipc runs on patched OpenBSD, patched FreeBSD, and on > > Linux kernels that support SO_PEERCRED with getsockopt(). > > I haven't used the credential passing feature of sendmsg(), but I > was wondering what advantages this has over being able to pass > kernel verified id's through a unix domain socket using SCM_CREDS. > My reading of UNP seems to indicate that it offers the same features. The implementation of SCM_CREDS in FreeBSD is my doing, and I did it that way for a reason. At the time, I wanted a way to perform RPCs via UNIX domain sockets and have the server know with reasonable certainty the identity of the client. And I wanted to do it without using AUTH_DES authentication because I was trying to bootstrap AUTH_DES authentication in keyserv. The problem is that RPCs are by definition messages. Things are handled at the application layer on a per-message basis, not on a per-socket basis, even for TCP connections. The problem with having credentials established once when a socket is opened is that the client process can conceivably fork, at which point you will have two clients sharing one socket with the same credential data. This isn't likely, but it's possible, and it bothered me. By having the credentials inserted into the message each time by each process, there's no ambiguity, even though you only have one socket. However this may not be the ideal solution for everyone. You may be satisfied with the "create credentials once when you open the socket" method, in which case the best thing is to support both approaches with hopefully similar code. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 11:28:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 1B28937B835 for ; Tue, 8 Aug 2000 11:28:40 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id LAA75113; Tue, 8 Aug 2000 11:28:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200008081828.LAA75113@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: "William E. Baxter" Cc: freebsd-hackers@FreeBSD.ORG, bright@wintelcom.net Subject: Re: getpeereid() syscall patch for FreeBSD 4.0 In-Reply-To: <20000808121849.A27414@zeus.superscript.com> Date: Tue, 08 Aug 2000 11:28:16 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "William E. Baxter" wrote: > With getpeereid() the credentials are passed at connect() and do not > require the client to send data. Therefore clients cannot consume > connections anonymously. In the patch: + error = copyout((caddr_t) &g, (caddr_t)(uap->egid), sizeof(gid_t)); + return (error); ... Passing only one gid is nearly useless. You should copy them all or not at all. I would like to see real and effective uid's as well. For what it's worth, we presently use SCM_CREDS in our RPC library to verify identity. This is mainly for keyserv and rpc.yppasswdd. The biggest problem with a "get the other side's credential" type operation is that it is ambiguous in the case of forked or shared fd's. Also, what about the case of changing uids? Do you give it the current uid or the uid at time of connection? SCM_CREDS has the ability for the client to authenticate at exactly the right time and without ambiguity. > W. > > On Tue, Aug 08, 2000 at 09:35:28AM -0700, Alfred Perlstein wrote: > > > > I haven't used the credential passing feature of sendmsg(), but I > > was wondering what advantages this has over being able to pass > > kernel verified id's through a unix domain socket using SCM_CREDS. > > My reading of UNP seems to indicate that it offers the same features. > > > > > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > "I have the heart of a child; I keep it in a jar on my desk." > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 12:29:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.superscript.com (zeus.superscript.com [206.234.89.16]) by hub.freebsd.org (Postfix) with SMTP id 2151437B674 for ; Tue, 8 Aug 2000 12:29:48 -0700 (PDT) (envelope-from web@superscript.com) Received: (qmail 21628 invoked by uid 1008); 8 Aug 2000 19:29:23 -0000 Date: Tue, 8 Aug 2000 14:29:23 -0500 From: "William E. Baxter" To: freebsd-hackers@FreeBSD.ORG Subject: Re: getpeereid() syscall patch for FreeBSD 4.0 Message-ID: <20000808142923.A15042@zeus.superscript.com> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <20000808121849.A27414@zeus.superscript.com> <200008081828.LAA75113@netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008081828.LAA75113@netplex.com.au>; from peter@netplex.com.au on Tue, Aug 08, 2000 at 11:28:16AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 11:28:16AM -0700, Peter Wemm wrote: > > Passing only one gid is nearly useless. You should copy them all or not > at all. I would like to see real and effective uid's as well. Completeness certainly has its appeal, but is it necessary? What can you not accomplish without the additional information? > about the case of changing uids? Do you give it the current uid or the uid > at time of connection? SCM_CREDS has the ability for the client to > authenticate at exactly the right time and without ambiguity. I need only connect()-time ID (but cannot wait for the client to provide it) and chose effective uid and gid. If the client changes its ID before or after calling connect(), so be it. If one cares, there is always SCM_CREDS. Regards, W. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 13:25:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 6F02237B735 for ; Tue, 8 Aug 2000 13:25:40 -0700 (PDT) (envelope-from float@firedrake.org) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13MFuq-0007Jp-00; Tue, 08 Aug 2000 21:24:00 +0100 Date: Tue, 8 Aug 2000 21:24:00 +0100 From: void To: Mitja Horvat Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1-RELEASE problem writing to async mounted filesystem Message-ID: <20000808212400.B26432@firedrake.org> References: <200008081606.SAA11004@akira.hermes.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <200008081606.SAA11004@akira.hermes.si>; from mitja.horvat@hermes.si on Tue, Aug 08, 2000 at 06:03:08PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 06:03:08PM +0200, Mitja Horvat wrote: > > Hi, > > I recently upgraded to FreeBSD 4.1-RELEASE(CD image). I noticed that while > writing > to an asynchronously mounted filesystem(mount -o async / ...) all other IO > operations to the FS are almost blocked. I have only one asynchronously > mounted > partition(/) and the following shell script makes the machine unresponsive > so I cannot > even telnet to it: > > while true; do rm -f foo; dd if=/dev/zero of=foo bs=1024k count=256; done > > 4.0-RELEASE does a much better job at handling similar situations... > > I'm using softupdates, but even without them the problem persists. There's no reason to use softupdates and async together. SU gets you the same benefits, but much more safely. > This does not happen if the fs is mounted synchronously, but I also get > MUCH slower IO > throughput(800kb/s compared to 12MB/s with async). Mounted sync or noasync? They're not the same thing. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 14: 8:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.rdc1.sfba.home.com (mail1.rdc1.sfba.home.com [24.0.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 367AB37B716; Tue, 8 Aug 2000 14:08:23 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail1.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000808210822.OBDG28364.mail1.rdc1.sfba.home.com@beastie.localdomain>; Tue, 8 Aug 2000 14:08:22 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id OAA96889; Tue, 8 Aug 2000 14:08:48 -0700 (PDT) (envelope-from brian) Date: Tue, 8 Aug 2000 14:08:48 -0700 From: "Brian O'Shea" To: Mike Smith Cc: boshea@ricochet.net, freebsd-hackers@freebsd.org Subject: Re: Hardware suppported needed by reboot(2) for RB_POWEROFF Message-ID: <20000808140848.E351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Mike Smith , boshea@ricochet.net, freebsd-hackers@freebsd.org References: <20000808093119.C351@beastie.localdomain> <200008081715.KAA12467@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200008081715.KAA12467@mass.osd.bsdi.com>; from Mike Smith on Tue, Aug 08, 2000 at 10:15:52AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 10:15:52AM -0700, Mike Smith wrote: > > > > What is the interface used by the reboot() system call to power off the > > machine when the RB_POWEROFF flag is set? The man page makes mention of > > hardware support, but doesn't specify what that support is, or how to > > use it. > > That's platform-dependant. On the x86, a conforming APM BIOS is required > (or a device driver with a suitable hook for some other control > interface). apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 Excellent, thanks. -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 14:23:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.beattie-home.net (219.164.200.216.fastpoint.net [216.200.164.219]) by hub.freebsd.org (Postfix) with ESMTP id BC6C637BA84 for ; Tue, 8 Aug 2000 14:23:10 -0700 (PDT) (envelope-from beattie@beattie-home.net) Received: from raven.pdx.beattie-home.net (raven.pdx.beattie-home.net [192.168.0.1]) by mail.beattie-home.net (Postfix) with ESMTP id 174D1AD90 for ; Tue, 8 Aug 2000 14:29:13 -0700 (PDT) Date: Tue, 8 Aug 2000 14:23:51 -0700 (PDT) From: Brian Beattie X-Sender: beattie@raven.pdx.beattie-home.net To: freebsd-hackers@FreeBSD.ORG Subject: vmware and vmnet devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG running a very recent 4.x-STABLE and today's vmware2 port, when I power on the virtual machine I get a pop-up with the message: could not open vmnet0, ethernet device 0 not configured and the virtual device does not power up. Is there a readme some where that tells me how to create those nodes? Brian Beattie | This email was produced using professional quality, beattie@beattie-home.net | standards based software. Users of Microsoft | products or other substandard software should www.beattie-home.net | contact the author about receiving a Free upgrade to | FreeBSD or Linux. "FreeBSD: The power to serve" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 15: 9:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uranium.dashmail.net (uranium.dashmail.net [216.36.26.29]) by hub.freebsd.org (Postfix) with ESMTP id 2FB2937B675 for ; Tue, 8 Aug 2000 15:09:18 -0700 (PDT) (envelope-from ptacek@dashmail.net) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by uranium.dashmail.net (8.10.1/8.10.1) with SMTP id e78MBTW14836 for ; Tue, 8 Aug 2000 22:11:30 GMT Reply-To: From: "Chris Ptacek" To: Subject: PCI Device Drivers? Date: Tue, 8 Aug 2000 15:09:03 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been given the task of writing a PCI device driver for a card that we will be using with one of our products. My question is where can I find the best documentation for writing PCI drivers? I assume that the best method would probably be examining current drivers, could anyone suggest specific drivers that might be simple or well written to examine. By the way the card is a Triple DES encryption card. - Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 15:25:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 9CB4937BED6 for ; Tue, 8 Aug 2000 15:25:01 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.15 #1) id 13MGSL-000Bhe-00; Tue, 08 Aug 2000 21:58:37 +0100 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.15 #1) id 13MGSO-0003Wx-00; Tue, 08 Aug 2000 21:58:40 +0100 Date: Tue, 8 Aug 2000 21:58:39 +0100 From: Ben Smithurst To: Mario Sergio Fujikawa Ferreira Cc: freebsd-hackers@freebsd.org Subject: Re: make release: how I do make it into a bootable cd? Message-ID: <20000808215839.S65753@strontium.scientia.demon.co.uk> References: <20000808133541.B9262@Fedaykin.here> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000808133541.B9262@Fedaykin.here> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mario Sergio Fujikawa Ferreira wrote: > 1) (cont.) I could use burncd but I am bugged by the fact > that I can't use cdrecord. :) Why? I think it was designed for SCSI devices, and you don't have one, so just use burncd. > 2) How do I make it a full-fledged FreeBSD bootable > distribution CDRom? I mean, where do I get the el-torrito boot > image? How do I make it use it and then run sysinstall seamlessly? Use floppies/boot.flp as the boot image, see "man mkisofs" for how to set the boot image. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D FreeBSD Documentation Project / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 15:27:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 7C01F37B64E for ; Tue, 8 Aug 2000 15:27:40 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115210>; Wed, 9 Aug 2000 08:27:28 +1000 Content-return: prohibited Date: Wed, 09 Aug 2000 08:27:15 +1000 From: Peter Jeremy Subject: Re: VLAN Support in FreeBSD In-reply-to: ; from blaz@amis.net on Tue, Aug 08, 2000 at 05:06:11PM +0200 To: Blaz Zupan , hackers@FreeBSD.ORG Message-Id: <00Aug9.082728est.115210@border.alcanet.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.4i References: <00Aug8.162756est.115205@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Aug-08 17:06:11 +0200, Blaz Zupan wrote: >http://www.euitt.upm.es/~pjlobo/fbsdvlan.html Very useful. Upon further reflection last night, I decided that the problem was most likely related to the NIC's idea of what was the largest allowed frame - and the URL above includes fixes for the FXP and 3C905B. Currently, the vlan code (in if_vlan.c:vlan_config()) uses the parent device's if_data.ifi_hdrlen to decide whether the device can support 802.1q frames (ie whether or not to decrease the vlan MTU by 4 bytes). I'm not sure that this is the correct approach - it definitely strikes me as a hack (and isn't supported by any drivers). In any case, since FreeBSD can support a mixture of 802.1q and standard frames on the one NIC, the correct value for ifi_hdrlen is unclear. I believe a better approach to the problem would be to define a new interface flag bit (eg IFF_802_1Q or IFF_VLAN) which a NIC driver sets if it can correctly handle 802.1q frames (ie 1522 bytes). if_vlan.c:vlan_config() would then test this bit to see if it can use the parent devices MTU, or has to allow for the encapsulation overhead itself. The biggest problem with this approach is that there are no free bits in if_flags. I don't believe any of the existing bits can be reused (in particular, all 3 link bits are used by a number of ethernet drivers). I can't readily see any other free bits in struct ifnet (though there's 2 byte of padding in struct if_data). Another alternative would be for if_vlan.c:vlan_config() to use a callback to the parent device to check for 802.1q support. The driver could then configure itself to support 802.1q frames (if possible), update if_data.ifi_hdrlen as appropriate and return the MTU allowed for the vlan device. I believe this approach would be overkill (since it needs an additional callback in struct ifnet and an additional function in (eventually) most ethernet drivers - for little apparent benefit). Is there justification for increasing the size of if_flags? (Or splitting them between struct ifnet and struct if_data). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 15:37:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.dcnv.com (mail.dcnv.com [216.33.117.136]) by hub.freebsd.org (Postfix) with ESMTP id 1601D37B830; Tue, 8 Aug 2000 15:37:12 -0700 (PDT) (envelope-from aedmonds@digitalconvergence.com) Received: from digitalconvergence.com (sledge [207.158.100.67]) by mail.dcnv.com (8.9.3/8.9.3) with ESMTP id RAA13196; Tue, 8 Aug 2000 17:34:55 -0500 (CDT) (envelope-from aedmonds@digitalconvergence.com) Message-ID: <39908B80.9FF47254@digitalconvergence.com> Date: Tue, 08 Aug 2000 17:36:48 -0500 From: Alan Edmonds X-Mailer: Mozilla 4.74 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ben Smithurst Cc: Mario Sergio Fujikawa Ferreira , freebsd-hackers@freebsd.org Subject: Re: make release: how I do make it into a bootable cd? References: <20000808133541.B9262@Fedaykin.here> <20000808215839.S65753@strontium.scientia.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This was brought up last week; I'm not sure if it was this list. See /usr/share/examples/worm for a couple of scripts used to create the FreeBSD release CDs. Very informative. Ben Smithurst wrote: > > Mario Sergio Fujikawa Ferreira wrote: > > > 1) (cont.) I could use burncd but I am bugged by the fact > > that I can't use cdrecord. :) > > Why? I think it was designed for SCSI devices, and you don't have one, so > just use burncd. > > > 2) How do I make it a full-fledged FreeBSD bootable > > distribution CDRom? I mean, where do I get the el-torrito boot > > image? How do I make it use it and then run sysinstall seamlessly? > > Use floppies/boot.flp as the boot image, see "man mkisofs" for how to > set the boot image. > > -- > Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D > FreeBSD Documentation Project / > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Alan Edmonds Director of International Technology DigitalConvergence.:Com aedmonds@digitalconvergence.com Phone: +1-214-292-6040 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 17:19:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with SMTP id 0AD1937B6C3 for ; Tue, 8 Aug 2000 17:19:27 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 63663 invoked by uid 1000); 9 Aug 2000 00:19:26 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Aug 2000 00:19:26 -0000 Date: Tue, 8 Aug 2000 19:19:26 -0500 (CDT) From: Mike Silbersack To: Alex Belits Cc: alexey@nsl.ru, freebsd-hackers@FreeBSD.org Subject: Re: subscribe alexey@nsl.ru In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Alex Belits wrote: > Users started "subscribing" in this manner? Congratulations, FreeBSD is > officially mainstream. > > -- > Alex And majordomo is, as always, confusing and in dire need of replacement. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 18:15:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C70AF37B868 for ; Tue, 8 Aug 2000 18:15:29 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 882561C70; Tue, 8 Aug 2000 21:15:26 -0400 (EDT) Date: Tue, 8 Aug 2000 21:15:26 -0400 From: Bill Fumerola To: Mike Silbersack Cc: Alex Belits , alexey@nsl.ru, freebsd-hackers@FreeBSD.org Subject: Re: subscribe alexey@nsl.ru Message-ID: <20000808211526.J95620@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from silby@silby.com on Tue, Aug 08, 2000 at 07:19:26PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 07:19:26PM -0500, Mike Silbersack wrote: > And majordomo is, as always, confusing and in dire need of replacement. Every Nth time this happens we all wonder why postmaster doesn't just add a filter that catches 99% of these and bounce them. Then we all forget and wait for N more people to do it and complain about it again. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 18:22:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9D02B37B8C9 for ; Tue, 8 Aug 2000 18:22:20 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA29727; Wed, 9 Aug 2000 10:52:10 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 09 Aug 2000 10:52:10 +0930 (CST) From: "Daniel O'Connor" To: Chris Ptacek Subject: RE: PCI Device Drivers? Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Aug-00 Chris Ptacek wrote: > Hi, I have been given the task of writing a PCI device driver for a card > that we will be using with one of our products. My question is where can I > find the best documentation for writing PCI drivers? I assume that the best > method would probably be examining current drivers, could anyone suggest > specific drivers that might be simple or well written to examine. By the > way the card is a Triple DES encryption card. The best/only documentation is the source code :) There are plenty of examples of PCI code in the tree, so copy a suitable driver.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 19: 6:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 6814237B93F for ; Tue, 8 Aug 2000 19:06:34 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 53275A845; Wed, 9 Aug 2000 12:07:22 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 4842E544A; Wed, 9 Aug 2000 12:07:22 +1000 (EST) Date: Wed, 9 Aug 2000 12:07:22 +1000 (EST) From: andrew@ugh.net.au To: Nicolas Leonard Cc: hackers@freebsd.org Subject: Re: How to generate a core dump explicily In-Reply-To: <00f101c00140$2a4b5a50$0f0210ac@masa.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Nicolas Leonard wrote: > I would like to generate a core dump 'explicitly' in > my program. How can that be done ? Call abort(3) Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 19:26:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 96B3A37B958 for ; Tue, 8 Aug 2000 19:26:29 -0700 (PDT) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ive7mn.dialup.mindspring.com [165.247.30.215]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id WAA05812 for ; Tue, 8 Aug 2000 22:26:23 -0400 (EDT) Message-ID: <3990C10F.B21AEF92@confusion.net> Date: Tue, 08 Aug 2000 22:25:19 -0400 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: God I feel stupid (gcc issue) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been going through the PR database, thinking maybe it was my turn to do something for FreeBSD. I looked at pr bin/2036. Problem? long isn't big enough to count all the bytes we could hold. So I look in the code and find /* Total number of bytes read and written for all files. Now that many tape drives hold more than 4Gb we need more than 32 bits to hold input_bytes and output_bytes. But it's not worth the trouble of adding special multi-precision arithmetic if the compiler doesn't support 64 bit ints since input_bytes and output_bytes are only used to print the number of blocks copied. */ #ifdef __GNUC__ long long input_bytes, output_bytes; #else long input_bytes, output_bytes; #endif in global.c So I thought, "we don't define __GNUC__?" I figured I'd check. After much mind wracking, I can't for the life of me figure out how to get gcc to output a list of what is and isnt defined by default... help! -- Laurence Berland <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 19:34:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 1733237B964 for ; Tue, 8 Aug 2000 19:34:40 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 99E439B03; Tue, 8 Aug 2000 22:34:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 8C46BBA11; Tue, 8 Aug 2000 22:34:39 -0400 (EDT) Date: Tue, 8 Aug 2000 22:34:39 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Laurence Berland Cc: hackers@freebsd.org Subject: Re: God I feel stupid (gcc issue) In-Reply-To: <3990C10F.B21AEF92@confusion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Laurence Berland wrote: > So I thought, "we don't define __GNUC__?" I figured I'd check. After > much mind wracking, I can't for the life of me figure out how to get gcc > to output a list of what is and isnt defined by default... help! > From 4.1-STABLE: jedgar@wopr:~$ cpp -v Using builtin specs. gcc version 2.95.2 19991024 (release) /usr/libexec/cpp -lang-c -v -Di386 -Dunix -D__FreeBSD__=4 -D__FreeBSD_cc_version=410000 -D__i386__ -D__unix__ -D__FreeBSD__=4 -D__FreeBSD_cc_version=410000 -D__i386 -D__unix -Acpu(i386) -Amachine(i386) -Asystem(unix) -Asystem(FreeBSD) -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__ELF__ - GNU CPP version 2.95.2 19991024 (release) (i386 FreeBSD/ELF) *snip* ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 19:56: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.hutchtel.net (ns1.hutchtel.net [206.9.112.100]) by hub.freebsd.org (Postfix) with ESMTP id 3C95637B882; Tue, 8 Aug 2000 19:55:48 -0700 (PDT) (envelope-from jpaetzel@hutchtel.net) Received: from mark8 (hutch-646.hutchtel.net [206.10.68.174]) by ns1.hutchtel.net (8.9.1/8.9.0) with SMTP id VAA27589; Tue, 8 Aug 2000 21:54:27 -0500 (CDT) Message-ID: <019b01c001ae$07ac3f00$ae440ace@mark8> From: "Josh Paetzel" To: "Daniel Lang" , , References: <20000808144202.A14579@atrbg11.informatik.tu-muenchen.de> Subject: Re: Installation Problems on Dell PowerEdge 6100/200 Date: Tue, 8 Aug 2000 22:00:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Daniel Lang" To: ; Sent: Tuesday, August 08, 2000 9:42 AM Subject: Installation Problems on Dell PowerEdge 6100/200 > Hi, > > we've got a Dell PowerEdge 6100/200 here, which is an older > SMP server, featuring 4 PPro 200 CPU's two internal AIC7880 > channels and an Adaptec 2940UW PCI controller. One of the > AIC's is connected to a SCA Backplane that holds 4 disks. > > Now before even having a chance to see if FreeBSD-SMP > works with this box, I didn't manage to install FreeBSD > (4.1) correctly. Well, installation seems to go well in > any attempt: > > - Floppy boots, Kernel finds all ahc's and disks > - Installation seems to succeed (Partitioning, installation, etc) > > But then, the machine won't boot. It seems to happen, that the > MBR of the target device (da0, which is the first disk on the > second controller, channel A of internal AIC's) is found, but > the next stage of the bootstrapping process cannot be found. > I played also around using boot0 and installing on other disks, > this is like what I got: > > Standard MBR and System on da0: -> Missing operating system > boot0 MBR and System on da0: -> F1 -> *beep* (nothing else) > boot0 MBR (and old System) on da0, standard MBR and System on da1: > booting from da0: F1 -> *beep*, F5 (disk2) -> Missing operating system > booting from da1: -> Missing operating system > > So it seems no boot-block after the MBR can be found. > > I tried: - installing and booting from different disks on internal ahc > - disabling some of the controllers > - installing and booting from a disk on the 2940, > as well while disabling the others > > It all had no effect. > > All adaptec's BIOS has Disks > 1GB and INT13 enabled (of course the > BIOS itself is enabled, too) > > Previously Solaris 7/x86 was running on this machine, there > were no such problems, but we don't really want to run Solaris... :-} > > Any clue ? > If it is worth anything, I tried installing on a poweredge 2450 once and to make a long story short couldn't get the onboard RAID to work or the SMP to work. I hear it got sent back for something else (that wasn't a dell!) Josh > Many thanks, > Daniel > -- > IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you > will be approximated. - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* > > -- > IRCnet: Mr-Spock - May His Shadow fall upon thee - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 20: 0:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 6935F37B599 for ; Tue, 8 Aug 2000 20:00:34 -0700 (PDT) (envelope-from chuckr@picnic.chuckr.org) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.9.3/8.9.3) with ESMTP id WAA19514; Tue, 8 Aug 2000 22:59:45 -0400 (EDT) (envelope-from chuckr@picnic.chuckr.org) Date: Tue, 8 Aug 2000 22:58:19 -0400 (EDT) From: Chuck Robey To: Laurence Berland Cc: hackers@FreeBSD.ORG Subject: Re: God I feel stupid (gcc issue) In-Reply-To: <3990C10F.B21AEF92@confusion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Laurence Berland wrote: > I've been going through the PR database, thinking maybe it was my turn > to do something for FreeBSD. I looked at pr bin/2036. Problem? long > isn't big enough to count all the bytes we could hold. So I look in the > code and find > > > /* Total number of bytes read and written for all files. > Now that many tape drives hold more than 4Gb we need more than 32 > bits to hold input_bytes and output_bytes. But it's not worth > the trouble of adding special multi-precision arithmetic if the > compiler doesn't support 64 bit ints since input_bytes and > output_bytes are only used to print the number of blocks copied. */ > #ifdef __GNUC__ > long long input_bytes, output_bytes; > #else > long input_bytes, output_bytes; > #endif > > in global.c > > So I thought, "we don't define __GNUC__?" I figured I'd check. After > much mind wracking, I can't for the life of me figure out how to get gcc > to output a list of what is and isnt defined by default... help! Don't feel stupid, it's a good question. touch null.c;gcc -v null.c;rm null.c That'll do it. You can also look at the gcc specs file with -dumpspecs. You can also use -save-temps to save all intermediate compilation products (output of cpp, assembler output). All this can be useful when fighting a make problem. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.chuckr.org| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 20: 3:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-89-56.dsl.snfc21.pacbell.net [63.206.89.56]) by hub.freebsd.org (Postfix) with ESMTP id 8BE9D37BD26; Tue, 8 Aug 2000 20:03:51 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id UAA15544; Tue, 8 Aug 2000 20:15:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008090315.UAA15544@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Josh Paetzel" Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Installation Problems on Dell PowerEdge 6100/200 In-reply-to: Your message of "Tue, 08 Aug 2000 22:00:51 CDT." <019b01c001ae$07ac3f00$ae440ace@mark8> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Aug 2000 20:15:00 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If it is worth anything, I tried installing on a poweredge 2450 once and to > make a long story short couldn't get the onboard RAID to work or the SMP to > work. I hear it got sent back for something else (that wasn't a dell!) Onboard RAID will be working shortly (waiting for someome to lend me hardware), SMP works as of 4.1-RELEASE. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 20: 7:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id 6898337B8C9 for ; Tue, 8 Aug 2000 20:07:13 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([208.191.149.190]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZ0008JX8A1X0@mta5.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Tue, 8 Aug 2000 21:58:50 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA27918; Tue, 08 Aug 2000 21:59:44 -0500 (CDT envelope-from chris) Date: Tue, 08 Aug 2000 21:59:23 -0500 From: Chris Costello Subject: Re: God I feel stupid (gcc issue) In-reply-to: <3990C10F.B21AEF92@confusion.net> To: Laurence Berland Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000808215923.A26695@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <3990C10F.B21AEF92@confusion.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, August 08, 2000, Laurence Berland wrote: > So I thought, "we don't define __GNUC__?" I figured I'd check. After > much mind wracking, I can't for the life of me figure out how to get gcc > to output a list of what is and isnt defined by default... help! gcc -E -dM - < /dev/null -- |Chris Costello |Use free-form input where possible. `---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 20: 7:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 8C80E37B9B7 for ; Tue, 8 Aug 2000 20:07:16 -0700 (PDT) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.228.43]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e7937AG23632 for ; Tue, 8 Aug 2000 23:07:10 -0400 (EDT) Message-ID: <3990CADE.65C585F6@glue.umd.edu> Date: Tue, 08 Aug 2000 23:07:10 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: SMBFS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the current status the native smbfs support? Can it act as a both a client and a server? How does it compare to Samba in terms of functionality? Thanks, Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 21:30:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.rdc1.sfba.home.com (mail1.rdc1.sfba.home.com [24.0.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 6224337B548 for ; Tue, 8 Aug 2000 21:30:25 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail1.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000809043023.WMBM28364.mail1.rdc1.sfba.home.com@beastie.localdomain>; Tue, 8 Aug 2000 21:30:23 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id VAA97789; Tue, 8 Aug 2000 21:30:50 -0700 (PDT) (envelope-from brian) Date: Tue, 8 Aug 2000 21:30:50 -0700 From: "Brian O'Shea" To: Nicolas Leonard Cc: Samuel Tardieu , hackers@FreeBSD.ORG Subject: Re: How to generate a core dump explicily Message-ID: <20000808213050.J351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: Nicolas Leonard , Samuel Tardieu , hackers@FreeBSD.ORG References: <00f101c00140$2a4b5a50$0f0210ac@masa.com> <2000-08-08-15-56-50+trackit+sam@inf.enst.fr> <011301c00146$c709f170$0f0210ac@masa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <011301c00146$c709f170$0f0210ac@masa.com>; from Nicolas Leonard on Tue, Aug 08, 2000 at 04:41:46PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 04:41:46PM +0200, Nicolas Leonard wrote: > Sorry, I wasn't precise enough . > > In fact, I caught the SIGABRT signal (and the others signals which are > ending the program) > and I'm doing some ending stuff, and after that, I would like to dump a core > file. > > I could remove the handler of SIGABRT after my ending suff done, and kill > myself another > time, but I would like to know if it's possible to dump the core explicitly. > (With a dumpcore() > function or whatever ) > There's no need to remove the handler for SIGABRT, unless you exit normally inside the handler. If you would like to handle SIGABRT, and you also want abort() to terminate the process and cause it to generate a core file, just remove any calls to exit() inside the handler. After your handler returns, the process will abort and dump core. If you use the same handler for all signals, you can conditionally exit based on the signal number. This example (handler.c) illustrates: #include #include #include void sig_handler __P((int)); int main(argc, argv) int argc; char *argv[]; { sig_t handler; handler = signal(SIGABRT, sig_handler); printf("Calling abort() ...\n"); abort(); printf("NOTREACHED\n"); return 0; } void sig_handler(sig) int sig; { printf("Caught signal %d\n", sig); /* exit(0); */ return; } Note from the backtrace (included below the program output) that the program dies at line 17. This is in the kill() function (as called from abort(), which never returns), but after the handler has returned (as can be seen by the output). [beastie:/home/brian]% cc -g handler.c -o handler [beastie:/home/brian]% ./handler Calling abort() ... Caught signal 6 zsh: 97734 abort (core dumped) ./handler [beastie:/home/brian]% gdb handler handler.core (gdb) bt #0 0x28094c78 in kill () from /usr/lib/libc.so.3 #1 0x280c8e57 in abort () from /usr/lib/libc.so.3 #2 0x80484a8 in main (argc=1, argv=0xbfbfd6ec) at handler.c:17 #3 0x8048419 in _start () -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 22:24:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 976CD37B9FA for ; Tue, 8 Aug 2000 22:24:33 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA02699; Tue, 8 Aug 2000 23:23:58 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <3990EC39.8D12BE22@softweyr.com> Date: Tue, 08 Aug 2000 23:29:29 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: andrew@ugh.net.au Cc: Nicolas Leonard , hackers@FreeBSD.ORG Subject: Re: How to generate a core dump explicily References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG andrew@ugh.net.au wrote: > > On Tue, 8 Aug 2000, Nicolas Leonard wrote: > > > I would like to generate a core dump 'explicitly' in > > my program. How can that be done ? > > Call abort(3) If you want to coredump it "interactively", hit your QUIT character (usually ^\). To do the same from another tty, or to a background or daemon process, send it a QUIT signal with kill(1). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 8 22:55:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 3A3C337B6B9 for ; Tue, 8 Aug 2000 22:55:29 -0700 (PDT) (envelope-from crossd@prolog.cs.rpi.edu) Received: from prolog.cs.rpi.edu (prolog.cs.rpi.edu [128.213.12.16]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id BAA66799; Wed, 9 Aug 2000 01:55:27 -0400 (EDT) Message-Id: <200008090555.BAA66799@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: crossd@cs.rpi.edu Subject: NFS/TCP problems. 4.0-RELEASE server, sol 8 client Date: Wed, 09 Aug 2000 01:55:27 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have recently had the time to start devoting more time to FreeBSD; especially the NFS code. I have stumbled upon a problem that seems to be out of my league. The problem is manifested when NFS/TCP connections just hang. Sometimes for only a few seconds, other times for minutes. Below is a network capture of all traffic between a server and a client (captured from the server): The intermittent UDP traffic is AMD issuing a null NFS request to verify that the server is still alive. Of note is the very long delays. Simply put, the FreeBSD box is not responding, not even an ACK. Also of note, about line 23 there is an ACK to a connection that does not even exist, with no noticeable activity on it for at least 2 seconds; what is is ACK-ing? It appears the Sol client keeps issuing RSTs until the client and server get back in sync WRT TCP sequence numbers, but what is driving them out of sequence, and why is the FreeBSD server not saying anything to the client (there is no firewall on any machine in this configuration.) 22:35:45.342966 10.1.1.1.1020 > 10.1.1.7.2049: S 1733116406:1733116406(0) win 24820 (DF) 22:35:54.723772 10.1.1.1.1020 > 10.1.1.7.2049: R 1733116407:1733116407(0) ack 0 win 24820 (DF) 22:35:54.723870 10.1.1.1.1020 > 10.1.1.7.2049: S 1747908437:1747908437(0) win 24820 (DF) 22:35:58.094003 10.1.1.1.1020 > 10.1.1.7.2049: S 1747908437:1747908437(0) win 24820 (DF) 22:36:02.054379 10.1.1.1.7906 > 10.1.1.7.2049: 40 null (DF) 22:36:02.054668 10.1.1.7.2049 > 10.1.1.1.7906: reply ok 24 null 22:36:04.844523 10.1.1.1.1020 > 10.1.1.7.2049: S 1747908437:1747908437(0) win 24820 (DF) 22:36:18.345779 arp who-has 10.1.1.7 (ff:ff:ff:ff:ff:ff) tell 10.1.1.1 22:36:18.345848 arp reply 10.1.1.7 is-at 0:a0:c9:55:94:18 22:36:18.346070 10.1.1.1.1020 > 10.1.1.7.2049: S 1747908437:1747908437(0) win 24820 (DF) 22:36:32.056867 10.1.1.1.7938 > 10.1.1.7.2049: 40 null (DF) 22:36:32.057258 10.1.1.7.2049 > 10.1.1.1.7938: reply ok 24 null 22:36:45.347892 10.1.1.1.1020 > 10.1.1.7.2049: S 1747908437:1747908437(0) win 24820 (DF) 22:36:54.728709 10.1.1.1.1020 > 10.1.1.7.2049: R 14792031:14792031(0) ack 1 win 24820 (DF) 22:36:54.728810 10.1.1.1.1020 > 10.1.1.7.2049: S 1762707767:1762707767(0) win 24820 (DF) 22:36:58.098954 10.1.1.1.1020 > 10.1.1.7.2049: S 1762707767:1762707767(0) win 24820 (DF) 22:37:02.059319 10.1.1.1.7970 > 10.1.1.7.2049: 40 null (DF) 22:37:02.059632 10.1.1.7.2049 > 10.1.1.1.7970: reply ok 24 null 22:37:04.849475 10.1.1.1.1020 > 10.1.1.7.2049: S 1762707767:1762707767(0) win 24820 (DF) 22:37:18.350703 arp who-has 10.1.1.7 (ff:ff:ff:ff:ff:ff) tell 10.1.1.1 22:37:18.350788 arp reply 10.1.1.7 is-at 0:a0:c9:55:94:18 22:37:18.350972 10.1.1.1.1020 > 10.1.1.7.2049: S 1762707767:1762707767(0) win 24820 (DF) 22:37:25.648257 10.1.1.7.2049 > 10.1.1.1.1022: . ack 73099259 win 33176 22:37:25.648451 10.1.1.1.1022 > 10.1.1.7.2049: R 73099259:73099259(0) win 0 (DF) 22:37:32.061812 10.1.1.1.8002 > 10.1.1.7.2049: 40 null (DF) 22:37:32.062179 10.1.1.7.2049 > 10.1.1.1.8002: reply ok 24 null 22:37:38.483949 arp who-has 10.1.1.254 tell 10.1.1.7 22:37:38.484115 arp reply 10.1.1.254 is-at 0:50:da:23:e7:2 22:37:45.352837 10.1.1.1.1020 > 10.1.1.7.2049: S 1762707767:1762707767(0) win 24820 (DF) 22:37:54.733653 10.1.1.1.1020 > 10.1.1.7.2049: R 29591361:29591361(0) ack 1 win 24820 (DF) 22:37:54.733759 10.1.1.1.1020 > 10.1.1.7.2049: S 1777476913:1777476913(0) win 24820 (DF) 22:37:58.103890 10.1.1.1.1020 > 10.1.1.7.2049: S 1777476913:1777476913(0) win 24820 (DF) 22:38:02.064269 10.1.1.1.8034 > 10.1.1.7.2049: 40 null (DF) 22:38:02.064651 10.1.1.7.2049 > 10.1.1.1.8034: reply ok 24 null 22:38:04.854408 10.1.1.1.1020 > 10.1.1.7.2049: S 1777476913:1777476913(0) win 24820 (DF) 22:38:18.355715 10.1.1.1.1020 > 10.1.1.7.2049: S 1777476913:1777476913(0) win 24820 (DF) 22:38:32.066736 10.1.1.1.8066 > 10.1.1.7.2049: 40 null (DF) 22:38:32.067015 10.1.1.7.2049 > 10.1.1.1.8066: reply ok 24 null 22:38:45.357792 10.1.1.1.1020 > 10.1.1.7.2049: S 1777476913:1777476913(0) win 24820 (DF) 22:38:54.738595 10.1.1.1.1020 > 10.1.1.7.2049: R 44360507:44360507(0) ack 1 win 24820 (DF) 22:38:54.738693 10.1.1.1.1020 > 10.1.1.7.2049: S 1792277515:1792277515(0) win 24820 (DF) 22:38:58.108813 10.1.1.1.1020 > 10.1.1.7.2049: S 1792277515:1792277515(0) win 24820 (DF) 22:39:02.069178 10.1.1.1.8098 > 10.1.1.7.2049: 40 null (DF) 22:39:02.069497 10.1.1.7.2049 > 10.1.1.1.8098: reply ok 24 null 22:39:04.859336 10.1.1.1.1020 > 10.1.1.7.2049: S 1792277515:1792277515(0) win 24820 (DF) 22:39:18.360595 arp who-has 10.1.1.7 (ff:ff:ff:ff:ff:ff) tell 10.1.1.1 22:39:18.360667 arp reply 10.1.1.7 is-at 0:a0:c9:55:94:18 22:39:18.360895 10.1.1.1.1020 > 10.1.1.7.2049: S 1792277515:1792277515(0) win 24820 (DF) 22:39:32.084018 10.1.1.1.8130 > 10.1.1.7.2049: 40 null (DF) 22:39:32.084397 10.1.1.7.2049 > 10.1.1.1.8130: reply ok 24 null 22:39:45.362736 10.1.1.1.1020 > 10.1.1.7.2049: S 1792277515:1792277515(0) win 24820 (DF) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 0:26: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 1445037BDAE; Wed, 9 Aug 2000 00:25:54 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from morpheus.kfu.com (morpheus.kfu.com [205.178.90.230]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id AAA42958; Wed, 9 Aug 2000 00:25:52 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by morpheus.kfu.com with ESMTP (8.9.3//ident-1.0) id AAA41025; Wed, 9 Aug 2000 00:25:52 -0700 (PDT) Message-ID: <39910780.A0B7567B@quack.kfu.com> Date: Wed, 09 Aug 2000 00:25:52 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-GB, en-US, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, cg@FreeBSD.ORG Subject: Solo-1 appears to work (was Re: US$100 prize for adding ESS Audiodrive support to pcm) References: <3985A21A.7CD51B31@quack.kfu.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I invite anyone capable to please test the Solo-1 driver. So far as I am able to test, it appears to work, but further field trials would be a good thing, especially in light of the wacky workaround that I found necessary to get recording to work (see the latest commit). Unless show-stoppers appear in the near future, I am inclined to award the US$100 prize to Cameron Grant, who provided a driver that was most of the way there. I would also like to publicly recognize and thank Klaus Klein who pointed me towards the (actually, his) NetBSD driver. Perusing his source gave me the hint about the record audio being big endian (thank ewe, ESS). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 0:27:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bsa-1-as01-7-a62.gd.uol.com.br (bsa-1-as01-7-a62.gd.uol.com.br [200.197.118.62]) by hub.freebsd.org (Postfix) with ESMTP id B8A9737BE49 for ; Wed, 9 Aug 2000 00:27:03 -0700 (PDT) (envelope-from lioux@uol.com.br) Received: (qmail 1052 invoked by uid 1001); 9 Aug 2000 07:26:53 -0000 From: "Mario Sergio Fujikawa Ferreira" Date: Wed, 9 Aug 2000 04:26:31 -0300 To: Alan Edmonds Cc: Ben Smithurst , Mario Sergio Fujikawa Ferreira , freebsd-hackers@FreeBSD.org Subject: Re: make release: how I do make it into a bootable cd? Message-ID: <20000809042630.B540@Fedaykin.here> References: <20000808133541.B9262@Fedaykin.here> <20000808215839.S65753@strontium.scientia.demon.co.uk> <39908B80.9FF47254@digitalconvergence.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39908B80.9FF47254@digitalconvergence.com>; from aedmonds@digitalconvergence.com on Tue, Aug 08, 2000 at 05:36:26PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 08, 2000 at 05:36:26PM -0500, Alan Edmonds wrote: > This was brought up last week; I'm not sure if it was this list. > > See /usr/share/examples/worm for a couple of scripts used > to create the FreeBSD release CDs. Very informative. > > Ben Smithurst wrote: > > > > Mario Sergio Fujikawa Ferreira wrote: > > > > > 1) (cont.) I could use burncd but I am bugged by the fact > > > that I can't use cdrecord. :) > > > > Why? I think it was designed for SCSI devices, and you don't have one, so > > just use burncd. > > > > > 2) How do I make it a full-fledged FreeBSD bootable > > > distribution CDRom? I mean, where do I get the el-torrito boot > > > image? How do I make it use it and then run sysinstall seamlessly? > > > > Use floppies/boot.flp as the boot image, see "man mkisofs" for how to > > set the boot image. > > Thanks to you both. As per the not being able to use cdrecord, I was just wondering if I could somehow access the atapi through an abstration layer such as ASPI. Who knows? Thanks though, I'll stick to burncd. :) Regards, Mario Ferreira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 2:23:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from copernicus.tranquility.net (copernicus.tranquility.net [206.152.117.186]) by hub.freebsd.org (Postfix) with ESMTP id 43BCF37B78E; Wed, 9 Aug 2000 02:23:31 -0700 (PDT) (envelope-from bweaver@copernicus.tranquility.net) Received: (from bweaver@localhost) by copernicus.tranquility.net (8.9.3/8.9.3) id EAA46025; Wed, 9 Aug 2000 04:25:14 -0500 (CDT) (envelope-from bweaver) Date: Wed, 9 Aug 2000 04:25:14 -0500 From: Ben Weaver To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: An sblock magic number is... Message-ID: <20000809042514.A46006@tranquility.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all, Here's the story... I am trying to back up a server running freebsd 2.2.8 onto another freebsd box running 4.0-RELEASE. I am attempting to achieve this by using dump over ssh. I created a user on the 2.2.8 box called backup and put it into the correct group allowing it read access to the raw drives. Here is the info on the 2.2.8 box: $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0s1a 3976982 909105 2749719 25% / /dev/sd1s1e 3976982 3359343 299481 92% /home /dev/sd2s1f 992751 817542 95789 90% /var procfs 4 4 0 100% /proc $ ls -l /dev | grep rsd0s1a crw-r----- 1 root operator 13, 0x00020000 Feb 27 1998 rsd0s1a $ ls -l /dev | grep rsd1s1e crw-r----- 1 root operator 13, 0x0002000c Aug 5 1999 rsd1s1e $ ls -l /dev | grep rsd2s1f crw-r----- 1 root operator 13, 0x00020015 Aug 5 1999 rsd2s1f I made the backup user a member of the operator group... On the 4.0 box, I created a large partition called /hold which will hold the dump until it can be written to a tape. On the 4.0 box, I cd to the /hold partition, su to root, and execute this command: ssh backup@serv1 /sbin/dump -0a -f - /dev/sd0s1a | dd of=t1.root serv1 is the hostname for the 2.2.8 box. This dumps the root partition of serv1 into /hold/t1.root. This works like a charm, I am able to do a restore -i -f t1.root and browse the dump just fine. The problem arises when I attempt to dump the /var and /home partitions on serv1: bash-2.03# ssh backup@tranq1 /sbin/dump -0a -f - /dev/sd0s1f | dd of=t1.var backup@tranq1's password: DUMP: Date of this level 0 dump: Wed Aug 9 02:18:04 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/sd0s1f to standard output DUMP: bad sblock magic number DUMP: The ENTIRE dump is aborted. 0+0 records in 0+0 records out 0 bytes transferred in 6.265023 secs (0 bytes/sec) bash-2.03# ssh backup@tranq1 /sbin/dump -0a -f - /dev/sd0s1e | dd of=t1.home backup@tranq1's password: DUMP: Date of this level 0 dump: Wed Aug 9 02:18:28 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/sd0s1e to standard output DUMP: bad sblock magic number DUMP: The ENTIRE dump is aborted. 0+0 records in 0+0 records out 0 bytes transferred in 4.395262 secs (0 bytes/sec) There are my two attempts at /var and /home (attempting to dump the the files t1.var and t1.home) It appears that the dumps are completely failing because of a bad sblock magic number, but I don't know what that is... Is this something that can be fixed? Thanks in advance for your help and please try to reply to my email address as well as the mailing list, since I am not a member of all of the lists I have sent this to. -Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 3: 5:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id DBE8D37BA00; Wed, 9 Aug 2000 03:05:44 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Aug 2000 11:05:43 +0100 (BST) Date: Wed, 9 Aug 2000 11:05:43 +0100 From: David Malone To: Ben Weaver Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... Message-ID: <20000809110543.A73193@walton.maths.tcd.ie> References: <20000809042514.A46006@tranquility.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000809042514.A46006@tranquility.net>; from bweaver@tranquility.net on Wed, Aug 09, 2000 at 04:25:14AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 04:25:14AM -0500, Ben Weaver wrote: > bash-2.03# ssh backup@tranq1 /sbin/dump -0a -f - /dev/sd0s1f | dd of=t1.var ^^^^^^ Doesn't dump take the raw device, or the filesystem name? Maybe it can take both - I don't have a 2.2.X box to check. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 3:36:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from guardian.hermes.si (guardian.hermes.si [193.77.5.150]) by hub.freebsd.org (Postfix) with ESMTP id A295537B75D for ; Wed, 9 Aug 2000 03:36:36 -0700 (PDT) (envelope-from mitja@hermes.si) Received: from hermes.si (primus.hermes.si [193.77.5.98]) by guardian.hermes.si (8.9.3/8.9.3) with ESMTP id MAA22273; Wed, 9 Aug 2000 12:36:21 +0200 (METDST) Received: (from uucp@localhost) by hermes.si (8.9.3/8.9.3) id MAA25602; Wed, 9 Aug 2000 12:36:20 +0200 Received: from akira.hermes.si(10.17.1.122) by primus.hermes.si via smap (V2.1) id xma024999; Wed, 9 Aug 00 12:35:17 +0200 Received: from lamu.hermes.si (lamu.hermes.si [10.17.1.230]) by akira.hermes.si with ESMTP (8.8.6 (PHNE_17135)/8.7.1) id MAA03452; Wed, 9 Aug 2000 12:38:28 +0200 (METDST) Message-Id: <200008091038.MAA03452@akira.hermes.si> Date: Wed, 09 Aug 2000 12:35:11 CEST From: Mitja Horvat To: void , Mitja Horvat Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1-RELEASE problem writing to async mounted filesystem Reply-To: mitja.horvat@hermes.si X-Mailer: Spruce 0.6.5 for X11 w/smtpio 0.7.9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > There's no reason to use softupdates and async together. SU gets you > the same benefits, but much more safely. You are right... I thought async was only for data updates, not metadata too... Thanks for clearing this out... As I understand SU, it's just a method to do metadata asynchronously in a safe way, so using noasync with SU does still have a point? > > This does not happen if the fs is mounted synchronously, but I also get > > MUCH slower IO > > throughput(800kb/s compared to 12MB/s with async). > > Mounted sync or noasync? They're not the same thing. > It was mounted async. I mounted it noasync and it behaves much better... It's not as responsive as when mounted sync, but the throughput is 12MB/s. Thank you for your help, Mitja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 5: 2:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from diskfarm.firehouse.net (rdu25-12-043.nc.rr.com [24.25.12.43]) by hub.freebsd.org (Postfix) with ESMTP id 1594637B61A; Wed, 9 Aug 2000 05:02:14 -0700 (PDT) (envelope-from abc@diskfarm.firehouse.net) Received: (from abc@localhost) by diskfarm.firehouse.net (8.9.3/8.9.3) id IAA55275; Wed, 9 Aug 2000 08:07:35 GMT (envelope-from abc) Date: Wed, 9 Aug 2000 08:07:35 +0000 From: Alan Clegg To: Ben Weaver Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... Message-ID: <20000809080735.A55136@diskfarm.firehouse.net> Mail-Followup-To: Alan Clegg , Ben Weaver , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org References: <20000809042514.A46006@tranquility.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000809042514.A46006@tranquility.net>; from bweaver@tranquility.net on Wed, Aug 09, 2000 at 04:25:14AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of the ether, Ben Weaver spewed forth the following bitstream: > $ df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd0s1a 3976982 909105 2749719 25% / > /dev/sd1s1e 3976982 3359343 299481 92% /home > /dev/sd2s1f 992751 817542 95789 90% /var > procfs 4 4 0 100% /proc > bash-2.03# ssh backup@tranq1 /sbin/dump -0a -f - /dev/sd0s1f | dd of=t1.var > DUMP: bad sblock magic number Note that you are dumping /dev/sd0s1f and not /dev/sd2s1f. /dev/sd0s1f does not contain a valid filesystem, thus can't be dumped. AlanC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 7:19:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id BC6E437BB21 for ; Wed, 9 Aug 2000 07:19:11 -0700 (PDT) (envelope-from t.vanklaveren@student.utwente.nl) Received: from phoenix (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.8.6/MQT) with SMTP id QAA15173 for ; Wed, 9 Aug 2000 16:19:07 +0200 (METDST) Message-ID: <001e01c0020c$d257b3c0$19e55982@student.utwente.nl> From: "Theo van Klaveren" To: Subject: In-kernel ioctl calls Date: Wed, 9 Aug 2000 16:19:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I've finally figured out why AudioFS isn't working (aside from an endianess error in v0.1), but I can't think of a solution. The problem I've found is as follows: The code in atapi-cd.c (from Soren's ATA driver) assumes the passed buffer (in the ioctl struct) is in user-space. The following is the offending piece of code from the CDIOCREADAUDIO ioctl call: --- snip --- if ((error = atapi_queue_cmd(cdp->atp, ccb, buffer, size, ATPR_F_READ, 30, NULL,NULL))) break; if ((error = copyout(buffer, ubuf, size))) break; --- snip --- The first statement issues the read command to the device, I presume. It copies the data to an internal (kernel-space) buffer. Next, the internal buffer is copyout()ed to ubuf (which is my ioctl buffer), which fails because in the case of AudioFS it's in kernel space. Boing, break, abort, no data for you. Bad boy. This, of course, caused the buffer's data not to be initialized, causing noise and crackles. And AudioFS didn't know the ioctl call failed, because the driver didn't return an error. Am I just doing it wrong, or should atapi-cd.c be patched to verify if the buffer is in user space or in kernel space? If so, what function checks if an address is in kernel space or in user space? If not, what am I doing wrong? Theo van Klaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 7:24:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 52CAB37BB21 for ; Wed, 9 Aug 2000 07:24:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA09041; Wed, 9 Aug 2000 16:24:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Theo van Klaveren" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: In-kernel ioctl calls In-Reply-To: Your message of "Wed, 09 Aug 2000 16:19:25 +0200." <001e01c0020c$d257b3c0$19e55982@student.utwente.nl> Date: Wed, 09 Aug 2000 16:24:23 +0200 Message-ID: <9039.965831063@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001e01c0020c$d257b3c0$19e55982@student.utwente.nl>, "Theo van Klaveren" writes: >I think I've finally figured out why AudioFS isn't working (aside from an >endianess error in v0.1), but I can't think of a solution. The problem I've >found is as follows: The code in atapi-cd.c (from Soren's ATA driver) >assumes the passed buffer (in the ioctl struct) is in user-space. The >following is the offending piece of code from the CDIOCREADAUDIO ioctl call: > >--- snip --- > if ((error = atapi_queue_cmd(cdp->atp, ccb, buffer, size, > ATPR_F_READ, 30, NULL,NULL))) > break; > > if ((error = copyout(buffer, ubuf, size))) > break; >--- snip --- You want to look at "struct uio", but it may be an ugly thing to get it used where you need it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 7:40:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f305.law7.hotmail.com [216.33.236.183]) by hub.freebsd.org (Postfix) with ESMTP id 23D3937BB11; Wed, 9 Aug 2000 07:40:34 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 9 Aug 2000 07:40:27 -0700 Received: from 209.249.186.215 by lw7fd.law7.hotmail.msn.com with HTTP; Wed, 09 Aug 2000 GMT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: freebsd-hackers@FreeBSD.ORG, freebsd-net@freebsd.org Subject: threadsafe name resolution Date: Wed, 09 Aug 2000 10:40:27 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 09 Aug 2000 14:40:27.0286 (UTC) FILETIME=[C23C2360:01C0020F] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've just received confirmation from the author of the KAME resolution code that it isn't at all thread safe: >Sure. As noted in name6.c, thread related stuff is not implemented yet. >Since our resolver code based on bind4 doesn't aware thread safeness, >all I can do now would be only putting mutex, anyway. sure enough, name6.c says: /* * TODO for thread safe * use mutex for _hostconf, _hostconf_init. * rewrite resolvers to be thread safe */ now, i'd say that it's fairly important for some form of threadsafe name resolution to exist. until the KAME code is fixed, how about adding in the ipv4 _r methods that have been discussed from time to time? or, at the very least, put something in the manpage for getipnodebyname and friends indicating that the funcs are not threadsafe. as you can probably tell, i wasted several hours worth of work bumping into this problem. -- -greg ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 8:30:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 4BF7E37BDEB for ; Wed, 9 Aug 2000 08:30:41 -0700 (PDT) (envelope-from float@firedrake.org) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13MXnC-0000rl-00; Wed, 09 Aug 2000 16:29:18 +0100 Date: Wed, 9 Aug 2000 16:29:18 +0100 From: void To: Mitja Horvat Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1-RELEASE problem writing to async mounted filesystem Message-ID: <20000809162918.A3293@firedrake.org> References: <200008091038.MAA03452@akira.hermes.si> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <200008091038.MAA03452@akira.hermes.si>; from mitja.horvat@hermes.si on Wed, Aug 09, 2000 at 12:35:11PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 12:35:11PM +0200, Mitja Horvat wrote: > > As I understand SU, it's just a method to do metadata asynchronously in a > safe way, > so using noasync with SU does still have a point? "Using noasync" is a no-op; noasync is the default. -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 8:31:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id AE86137BDD6; Wed, 9 Aug 2000 08:31:00 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e79FUrZ55173; Thu, 10 Aug 2000 00:30:54 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: freebsd-current@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org, acpi-jp@jp.FreeBSD.org Subject: ACPI project progress report (final?) X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000810003052A.iwasaki@jp.FreeBSD.org> Date: Thu, 10 Aug 2000 00:30:52 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 443 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, here is the latest (and maybe final?) report on our ACPI project's progress. We are ready now to merge our work on ACPI into main source tree! Our prototype development is going to finish. AML interpreter development is almost completed, region access facility (SystemMemory, SystemIO and PCI_Config) is almost completed, device major number is officialy assigned, source code cleanup is finished. Also some of us are committers of freefall to work on it. Of cause we still have a lot of things should be done to complete this project, but we think it's good enough as a prototype and want to work together with you, many people who are interested in ACPI implementation. Folks, there are a lot of exciting and cool things, like Processor and Device Power State Control, Thermal Management, Replacement PnP system, OS initiated hibernation and many :-) I think now is the time to start open and development, not only in Japan, for FreeBSD ACPI support! At USENIX 2000, I luckily had a discussion with Mike Smith, John Baldwin, Doug Rabson, Peter Wemm and some people. I very much appreciate very useful suggestions from them (especially Mike, thanks a lot). Once merge happened, we will stop maintaining our ACPI CVS repository except for DSDT/ASL data collection. Discussions in Japanese mailing-list will be continued but it will be just for some people who want to get information in Japanese. Most of Japanese ACPI developers will work based on CURRENT. Recently we imported CURRENT sys tree as of 2000/8/4 into our ACPI repository and prepared diffs against CURREN at; http://people.FreeBSD.org/~iwasaki/acpi/acpi-sys-20000804.diff.gz and snapshot of userland tools is available at; http://people.FreeBSD.org/~iwasaki/acpi/acpi-usr.sbin-20000804.tar.gz Please get and taste them, we are going to merge them into CURRENT sometime around end of this month. How to use: # cd /usr/src # gzip -dc < /somewhere/acpi-sys-20000804.diff.gz | patch # tar xzpvf /somewhere/acpi-usr.sbin-20000804.tar.gz # cp sys/sys/acpi.h /usr/include/sys/ # cd /usr/src/usr.sbin/acpi # make obj depend all install # mknod /dev/acpi c 152 0 # cd /usr/src/sys/i386/conf # echo 'device acpi' >> MYKERNEL # echo 'options ACPI_DEBUG' >> MYKERNEL # echo 'options AML_DEBUG' >> MYKERNEL # config -r MYKERNEL # cd ../../compile/MYKERNEL # make depend; make all install # shutdown -r now (reboot...) # acpiconf -s 5 (sleeping state 5, shutdown & power off) or press Power button to shutdown if supported. Directory tour: - kernel space side src/sys/i386/i386/machdep.c getmemsize() try to get ACPI related memory range from SMAP. src/sys/i386/i386/bios.c bios32_init() try to find RSD PTR signature (probe ACPI BIOS). src/sys/sys/acpi.h The acpi related structs and function declaration. This need to be installed in /usr/include/sys/ to compile acpi userland tools. src/sys/dev/acpi/acpi.c acpi device driver. src/sys/dev/acpi/aml/ AML interpreter code. aml_parse.c was originally developed based on dfr's AML disassembler program. These files can be compiled and work in both of kernel/userland side. src/sys/i386/conf/NOTES sample configration and possible options for acpi driver. src/sys/i386/i386/acpi_machdep.c i386 dependent implementations to be added here. src/sys/i386/include/acpica_osd.h ACPICA interface implementation (part of OS-dependent code). src/sys/conf/{files|options} src/sys/conf/files.i386 file and option configuration for ACPI. - userland side src/usr.sbin/acpi/acpiconf enabler/disabler and sleeping state transition ioctl requests generator. src/usr.sbin/acpi/acpidump ASL and AML dump tool (modified dfr's tool a bit). src/usr.sbin/acpi/amldb The debugger for AML interpreter. - device file /dev/acpi major/minor should be 152, 0 (officially assigned). You need to create this file like # mknod /dev/acpi c 152 0 to use userland tools. ACPI device driver: This driver has - ACPI memory range management - The pmap stuff for ACPI - ACPI registers manipulation stuff - ACPI tables handlers * - System sleeping state stuff - AML interpreter callers for special control methods; _PTS and _WAK * - Event handler (power/sleep button for now) - Interrupt handler (for general purpose events maybe incomplete) - Event enabler (PM1 only, GPE not yet) - Device file manipulation stuff - The new-bus dependent code *: acpi_handle_dsdt() and acpi_execute_{pts|wak}() invoke AML interpreter. AML interpreter source files: - aml_amlmem.c memory manager instance for AML interpreter - aml_amlmem.h memory manager instance for AML interpreter - aml_common.c common functions for some component - aml_common.h common function declarations and macros for kernel/userland portability - aml_env.h AML execution environment - aml_evalobj.c evaluation of named objects - aml_evalobj.h evaluation of named objects - aml_memman.c generic memory manager - aml_memman.h generic memory manager - aml_name.c named object and tree manipulation - aml_name.h named object and tree manipulation - aml_obj.c ACPI object manipulation - aml_obj.h ACPI object manipulation and structure declaration - aml_parse.c AML parser - aml_parse.h AML parser - aml_region.c region I/O routines for system resources * - aml_region.h region I/O routines for system resources - aml_status.h interpreter and debugger execution status declaration - aml_store.c Store operation implementation - aml_store.h Store operation implementation *: SystemMemory and SystemIO I/O routines are supported, PCI_Config is almost completed but we need to combine ACPI namespace and new-bus device tree together in order to finish work. EmbeddedController and SMBus are not supported for now. ACPI userland tools: - acpiconf acpiconf [-e] [-d] write enable/disable value to SMI command port (specified in FACP). acpiconf -s [0-5] set sleeping state (only 1 and 5 are implemented) - acpidump acpidump print ASL code from DSDT via /dev/mem. acpidump -o dsdt_file print ASL and dump DSDT data block to the file. acpidump -f dsdt_file print ASL code from given dsdt data file. - amldb amldb dsdt_files... interpret and execute AML from given dsdt files. This has I/O simulator (tiny virtual machine?) in order to execute ACPI control methods in userland. Values from/to the I/O simulator can be changed by prompt before actual accessing occurred. Initial content file for simulator is region.ini. If -d option was given, file region.dmp will be generated (final status of simulator contents). debugger commands are; s Single step n Step program c Continue program being debugged q Quit method execution t Show local name space tree and variables i Toggle region input prompt o Toggle region output prompt m Show memory management statistics r Run specified method f Find named objects from namespace. h Show this messsage example; % amldb 3110CT.dsdt.dat Loading 3110CT.dsdt.dat...done AML>f _PS2 \_SB_.PCI0.VGA_._PS2. AML>r \_SB_.PCI0.VGA_._PS2 Method: Arg 8 From 0x280603a6 To 0x2806043f ==== Running \_SB_.PCI0.VGA_._PS2. ==== AML>s [\_SB_.PCI0.VGA_._PS2. START] Store(0x1, \_SB_.MEM_.IESI) [aml_region_write(0, 0, 0x1, 0x100b0000, 0x34080, 0x20)] amldb: region.ini: No such file or directory [0:0x00@0x100b6810]->[0:0x01@0x100b6810] [0:0x00@0x100b6811]->[0:0x00@0x100b6811] [0:0x00@0x100b6812]->[0:0x00@0x100b6812] [0:0x00@0x100b6813]->[0:0x00@0x100b6813] [write(0, 0x1, 0x100b6810)] [aml_region_read(0, 0, 0x100b0000, 0x34080, 0x20)] [0:0x01@0x100b6810] [0:0x00@0x100b6811] [0:0x00@0x100b6812] [0:0x00@0x100b6813] DEBUG[read(0, 0x100b6813)&mask:0x1](default: 0x1 / 1) >> [read(0, 0x100b6810)->0x1] AML> amldb -d dump contents of I/O simulator when exiting. amldb -s print memory statistics when exiting. AML interpreter has own memory management system to reduce malloc/free calling overhead and memory leak possibilities. Initial memory blocks was pre-allocated for each defined-structures during compile-time. If initial memory block is consumed completely, then this will try to obtain many blocks at once by malloc(). Also normal malloc/free() like interfaces are supported (with statistics) for flexible size memory allocations which can't be determined until the interpreter is executed at runtime. amldb -t print namespace tree when starting. Additional files for amldb: - amldb.c main funcion - debug.c debugger - region.c userland version of region I/O routines using I/O simulator Data files for testing: http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/util/takawata/acpi/?cvsroot=freebsd-jp and http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/util/dfr/acpitest/?cvsroot=freebsd-jp DSDT data block files (AML) and ASL code files respectively. Other 3rd vendor tools: - ASL compiler http://www.teleport.com/~acpi/samples.htm example) % wine 'asl.exe Trajan.asl' ACPI Source Language Assembler Version 1.0.11 [Jan 18 1999, 17:50:22] Copyright (c) 1996,1999 Microsoft Corporation Compliant with ACPI 1.0 specification Trajan.asl: lm75.asl: px4smb.asl: NS338.asl: 338_uar1.asl: 338_uar2.asl: 338_prt.asl: 338_fdc.asl: mb_dev.asl: dock.asl: asl(trajan.aml): Image Size=9204, Image Checksum=0x1a - ACPI Spec 2.0 http://www.teleport.com/%7Eacpi/2spec.htm - ACPICA (ACPI Component Archtecture) source code and document This is yet another AML interpreter implementaion. Linux take this one in thier kernel. http://developer.intel.com/technology/iapc/tech.htm ASL code and DSDT data collection: We are gathering them for further implementation and testing. % acpidump -o foo.dsdt > foo.asl and finally send them to takawata@shidahara1.planet.sci.kobe-u.ac.jp. Submitted data will be stored in ACPI CVS repository. The following is updates from our last report issued June. New/Changed items are marked as *. TODO: - combine sys/isa/pnpparse.c with interpreter. - support S2, S3, S4 (hibernation) sleeping transition. S4 sleep require some hack in boot loader.... needs help. - implement serialization and synchronization mechanism. - migrate to Intel ACPICA? (but that's too large to understand. I'm not sure whether this has licencing issue or welcome to import it into FreeBSD repository in terms of licencing policy... ours? Yes, it's BSD Licence. No problem at all :-) * I've attached Licence term of ACPICA for your reference in this mail. * writing manpages. I take this one for userland tools first :-) * support Dock. * support General-Purpose Event (GPE) and Notity() implementatioin. * implement the rest of AML interpreter. * implement ACPI event thread to handle events of devices which is waiting for interrupts such as buttons or Embedded Controller. * design/implement Policy Management daemon program. - and many. Current status: * The aml interpreter development is almost finished and also we've ported it to kernel. Now that we can build ACPI namespace and search any named objects from there in kernel space. The aml interpreter code can be compiled and executed in both userland (using I/O simulator) and kernel space so that we can continue development even after we ported the code in kernel. * Implementation of the accessing facility for SystemMemory, SystemIO was completed. PCI_Config is almost finished with some limitations. And now simple method (eg _PTS with 1 or 5 and _WAK) is nicely executed already. * Thus, we've achieved our goal of prototype development! Obtaining latest source code: * Note that this repository will be obsolete soon after merge to CURRENT. To get ACPI project repository, please try CVSup with; --------------------------------------- *default host=cvsup.jp.FreeBSD.org *default base=/usr *default prefix=/home/cvs *default release=cvs *default delete use-rel-suffix jp-acpi --------------------------------------- cvsweb is also available at; . Thanks! Appendix: Licence terms of ACPICA /****************************************************************************** * * 1. Copyright Notice * * Some or all of this work - Copyright (c) 1999, Intel Corp. All rights * reserved. * * 2. License * * 2.1. This is your license from Intel Corp. under its intellectual property * rights. You may have additional license terms from the party that provided * you this software, covering your right to use that party's intellectual * property rights. * * 2.2. Intel grants, free of charge, to any person ("Licensee") obtaining a * copy of the source code appearing in this file ("Covered Code") an * irrevocable, perpetual, worldwide license under Intel's copyrights in the * base code distributed originally by Intel ("Original Intel Code") to copy, * make derivatives, distribute, use and display any portion of the Covered * Code in any form, with the right to sublicense such rights; and * * 2.3. Intel grants Licensee a non-exclusive and non-transferable patent * license (with the right to sublicense), under only those claims of Intel * patents that are infringed by the Original Intel Code, to make, use, sell, * offer to sell, and import the Covered Code and derivative works thereof * solely to the minimum extent necessary to exercise the above copyright * license, and in no event shall the patent license extend to any additions * to or modifications of the Original Intel Code. No other license or right * is granted directly or by implication, estoppel or otherwise; * * The above copyright and patent license is granted only if the following * conditions are met: * * 3. Conditions * * 3.1. Redistribution of Source with Rights to Further Distribute Source. * Redistribution of source code of any substantial portion of the Covered * Code or modification with rights to further distribute source must include * the above Copyright Notice, the above License, this list of Conditions, * and the following Disclaimer and Export Compliance provision. In addition, * Licensee must cause all Covered Code to which Licensee contributes to * contain a file documenting the changes Licensee made to create that Covered * Code and the date of any change. Licensee must include in that file the * documentation of any changes made by any predecessor Licensee. Licensee * must include a prominent statement that the modification is derived, * directly or indirectly, from Original Intel Code. * * 3.2. Redistribution of Source with no Rights to Further Distribute Source. * Redistribution of source code of any substantial portion of the Covered * Code or modification without rights to further distribute source must * include the following Disclaimer and Export Compliance provision in the * documentation and/or other materials provided with distribution. In * addition, Licensee may not authorize further sublicense of source of any * portion of the Covered Code, and must include terms to the effect that the * license from Licensee to its licensee is limited to the intellectual * property embodied in the software Licensee provides to its licensee, and * not to intellectual property embodied in modifications its licensee may * make. * * 3.3. Redistribution of Executable. Redistribution in executable form of any * substantial portion of the Covered Code or modification must reproduce the * above Copyright Notice, and the following Disclaimer and Export Compliance * provision in the documentation and/or other materials provided with the * distribution. * * 3.4. Intel retains all right, title, and interest in and to the Original * Intel Code. * * 3.5. Neither the name Intel nor any other trademark owned or controlled by * Intel shall be used in advertising or otherwise to promote the sale, use or * other dealings in products derived from or relating to the Covered Code * without prior written authorization from Intel. * * 4. Disclaimer and Export Compliance * * 4.1. INTEL MAKES NO WARRANTY OF ANY KIND REGARDING ANY SOFTWARE PROVIDED * HERE. ANY SOFTWARE ORIGINATING FROM INTEL OR DERIVED FROM INTEL SOFTWARE * IS PROVIDED "AS IS," AND INTEL WILL NOT PROVIDE ANY SUPPORT, ASSISTANCE, * INSTALLATION, TRAINING OR OTHER SERVICES. INTEL WILL NOT PROVIDE ANY * UPDATES, ENHANCEMENTS OR EXTENSIONS. INTEL SPECIFICALLY DISCLAIMS ANY * IMPLIED WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT AND FITNESS FOR A * PARTICULAR PURPOSE. * * 4.2. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY TO LICENSEE, ITS LICENSEES * OR ANY OTHER THIRD PARTY, FOR ANY LOST PROFITS, LOST DATA, LOSS OF USE OR * COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY INDIRECT, * SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, UNDER ANY * CAUSE OF ACTION OR THEORY OF LIABILITY, AND IRRESPECTIVE OF WHETHER INTEL * HAS ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. THESE LIMITATIONS * SHALL APPLY NOTWITHSTANDING THE FAILURE OF THE ESSENTIAL PURPOSE OF ANY * LIMITED REMEDY. * * 4.3. Licensee shall not export, either directly or indirectly, any of this * software or system incorporating such software without first obtaining any * required license or other approval from the U. S. Department of Commerce or * any other agency or department of the United States Government. In the * event Licensee exports any such software from the United States or * re-exports any such software from a foreign destination, Licensee shall * ensure that the distribution and export/re-export of the software is in * compliance with all laws, regulations, orders, or other restrictions of the * U.S. Export Administration Regulations. Licensee agrees that neither it nor * any of its subsidiaries will export/re-export any technical data, process, * software, or service, directly or indirectly, to any country for which the * United States government or any agency thereof requires an export license, * other governmental approval, or letter of assurance, without first obtaining * such license, approval or letter. * *****************************************************************************/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 8:51:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BDB8C37BB79 for ; Wed, 9 Aug 2000 08:51:06 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA77500; Wed, 9 Aug 2000 17:51:02 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008091551.RAA77500@freebsd.dk> Subject: Re: In-kernel ioctl calls In-Reply-To: <001e01c0020c$d257b3c0$19e55982@student.utwente.nl> from Theo van Klaveren at "Aug 9, 2000 04:19:25 pm" To: t.vanklaveren@student.utwente.nl (Theo van Klaveren) Date: Wed, 9 Aug 2000 17:51:02 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Theo van Klaveren wrote: > > I think I've finally figured out why AudioFS isn't working (aside from an > endianess error in v0.1), but I can't think of a solution. The problem I've > found is as follows: The code in atapi-cd.c (from Soren's ATA driver) > assumes the passed buffer (in the ioctl struct) is in user-space. The > following is the offending piece of code from the CDIOCREADAUDIO ioctl call: > > --- snip --- > if ((error = atapi_queue_cmd(cdp->atp, ccb, buffer, size, > ATPR_F_READ, 30, NULL,NULL))) > break; > > if ((error = copyout(buffer, ubuf, size))) > break; > --- snip --- > > The first statement issues the read command to the device, I presume. It > copies the data to an internal (kernel-space) buffer. Next, the internal > buffer is copyout()ed to ubuf (which is my ioctl buffer), which fails > because in the case of AudioFS it's in kernel space. > > Boing, break, abort, no data for you. Bad boy. > > This, of course, caused the buffer's data not to be initialized, causing > noise and crackles. And AudioFS didn't know the ioctl call failed, because > the driver didn't return an error. > > Am I just doing it wrong, or should atapi-cd.c be patched to verify if the > buffer is in user space or in kernel space? If so, what function checks if > an address is in kernel space or in user space? If not, what am I doing > wrong? Here's another idea, the ata driver can read/write 2352 sector size blocks directly, no need to use that ugly ioctl. You just have to set the right blocksize, I could provide you with a function for that, no more ioctl mess ;) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 8:55:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 67EF837BA74 for ; Wed, 9 Aug 2000 08:55:07 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA12824; Wed, 9 Aug 2000 08:54:59 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA53597; Wed, 9 Aug 2000 08:54:58 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 9 Aug 2000 08:54:58 -0700 (PDT) Message-Id: <200008091554.IAA53597@vashon.polstra.com> To: hackers@freebsd.org Cc: archie@whistle.com Subject: Re: CVS question In-Reply-To: <200008071906.MAA12811@bubba.whistle.com> References: <200008071906.MAA12811@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008071906.MAA12811@bubba.whistle.com>, Archie Cobbs wrote: > Consider this source file: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/xntpd/lib/Attic/ranny.c > > Question: what version should this command checkout? > > $ cvs co -D 'January 18, 1999 0:00' freebsd/src/usr.sbin/xntpd/lib/ranny.c > > Perhaps version 1.1.1.2 would be correct, but instead you get 1.1. CVS is really screwy in this area. I remember I had to add some special cases to CVSup long ago to try to mimic CVS's behavior in odd cases. > It seems CVS is being inconsistent: > > - If you had done a 'head' checkout on that date you would have > gotten 1.1.1.2 That makes sense, because on that date the file had not yet left the vendor branch, and its default branch attribute still pointed to the vendor branch. > - If you later do a 'head' checkout, and specify that date, you get 1.1 CVS has a heuristic that does the wrong thing for this particular file. The code is around line 3252 of src/contrib/cvs/src/rcs.c in the function RCS_getdate(): if (! STREQ (cur_rev, "1.1")) return (xstrdup (cur_rev)); /* This is 1.1; if the date of 1.1 is not the same as that for the 1.1.1.1 version, then return 1.1. This happens when the first version of a file is created by a regular cvs add and commit, and there is a subsequent cvs import of the same file. */ p = findnode (rcs->versions, "1.1.1.1"); if (p) { vers = (RCSVers *) p->data; if (RCS_datecmp (vers->date, date) != 0) return xstrdup ("1.1"); } It compares the dates on the theory that an import will set identical dates in revisions 1.1 and 1.1.1.1. But in the file you mentioned, they are off by 1 second. So CVS doesn't recognize it as an import. revision 1.1 date: 1993/12/21 18:36:22; author: wollman; state: Exp; revision 1.1.1.1 date: 1993/12/21 18:36:23; author: wollman; state: Exp; lines: +0 -0 Probably the import straddled the seconds boundary. I hope current versions of CVS force the dates to be the same on an import. I haven't checked to see whether that's the case or not. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9: 1:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 541AF37BB8E for ; Wed, 9 Aug 2000 09:01:19 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JSRX1X810U00086O@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 9 Aug 2000 18:01:14 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 09 Aug 2000 18:01:14 +0100 Content-return: allowed Date: Wed, 09 Aug 2000 18:01:12 +0100 From: "Koster, K.J." Subject: audiofs mixing audio and data tracks To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7782@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, I'm not sure if I'm off into the woods on this one, but I'm sure you will correct me. :-) Could you perhaps make it so that all the audio tracks appear als slice 1, while the data track appears as slice 2. Mount data-only cdrom: mount -t cd9660 /dev/cd0s1c -or- mount -t cd9660 /dev/cd0c Mount audio and data part of audio/data cdrom: mount -t cd9660 /dev/cd0s1c mount -t audio /dev/cd0s2c Mount audio-only cdrom: mount -t audio /dev/cd0s2c -or- mount -t audio /dev/cd0c Or, another idea, make the data appear a /dev/cd0c and the audio as /dev/cd0a. (Although I'd agree that this breaks partition conventions, perhaps /dev/cd0d is better for data tracks, "c" referring to the whole disk) This way, as a sysop you would not care if it's an audio or data only cdrom, or if it has both. Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9: 1:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 828F037BB79 for ; Wed, 9 Aug 2000 09:01:38 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA12864; Wed, 9 Aug 2000 09:01:27 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA53642; Wed, 9 Aug 2000 09:01:27 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 9 Aug 2000 09:01:27 -0700 (PDT) Message-Id: <200008091601.JAA53642@vashon.polstra.com> To: hackers@freebsd.org Cc: jedgar@fxp.org Subject: Re: God I feel stupid (gcc issue) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chris D. Faulhaber wrote: > On Tue, 8 Aug 2000, Laurence Berland wrote: > > > So I thought, "we don't define __GNUC__?" I figured I'd check. After > > much mind wracking, I can't for the life of me figure out how to get gcc > > to output a list of what is and isnt defined by default... help! > > > > From 4.1-STABLE: > > jedgar@wopr:~$ cpp -v That's the wrong way to do it because cpp behaves differently than cc. Another poster gave the right answer: "gcc -E -dM - < /dev/null". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9: 6:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 920DE37BB6D for ; Wed, 9 Aug 2000 09:06:48 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA12890; Wed, 9 Aug 2000 09:06:38 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA53678; Wed, 9 Aug 2000 09:06:37 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 9 Aug 2000 09:06:37 -0700 (PDT) Message-Id: <200008091606.JAA53678@vashon.polstra.com> To: hackers@freebsd.org Cc: stuyman@confusion.net Subject: Re: God I feel stupid (gcc issue) In-Reply-To: <3990C10F.B21AEF92@confusion.net> References: <3990C10F.B21AEF92@confusion.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3990C10F.B21AEF92@confusion.net>, Laurence Berland wrote: > So I thought, "we don't define __GNUC__?" But our compiler _does_ define that macro. > I figured I'd check. After much mind wracking, I can't for the life > of me figure out how to get gcc to output a list of what is and isnt > defined by default... help! Another poster already answered your specific question. The general way to find out stuff like this is with "info gcc". (Or use the equivalent emacs incantation -- CTRL-META-WiggleLeftToe, I believe it is.) Follow the links Invoking GCC -> Preprocessor Options and you'll find out how to get all sorts of useful information from the compiler. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9: 9: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 3369A37BAC2 for ; Wed, 9 Aug 2000 09:08:57 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id MAA45997; Wed, 9 Aug 2000 12:08:50 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008091608.MAA45997@blackhelicopters.org> Subject: Re: SMBFS In-Reply-To: <3990CADE.65C585F6@glue.umd.edu> from Brandon Fosdick at "Aug 8, 2000 11: 7:10 pm" To: bfoz@glue.umd.edu (Brandon Fosdick) Date: Wed, 9 Aug 2000 12:08:50 -0400 (EDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My understanding of SMBFS is that it's not intended to be a server. It's a pretty solid client, though. I use it extensively, without trouble. ==ml > What's the current status the native smbfs support? Can it act as a both a > client and a server? How does it compare to Samba in terms of functionality? > > Thanks, > Brandon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9:51:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id B353437BE69; Wed, 9 Aug 2000 09:51:16 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id MAA00815; Wed, 9 Aug 2000 12:51:12 -0400 (EDT) (envelope-from dan) Date: Wed, 9 Aug 2000 12:51:12 -0400 From: Dan Moschuk To: Greg Thompson Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: threadsafe name resolution Message-ID: <20000809125112.C293@spirit.jaded.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from johnnyteardrop@hotmail.com on Wed, Aug 09, 2000 at 10:40:27AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | i've just received confirmation from the author of the KAME resolution code | that it isn't at all thread safe: | | >Sure. As noted in name6.c, thread related stuff is not implemented yet. | >Since our resolver code based on bind4 doesn't aware thread safeness, | >all I can do now would be only putting mutex, anyway. | | sure enough, name6.c says: | | /* | * TODO for thread safe | * use mutex for _hostconf, _hostconf_init. | * rewrite resolvers to be thread safe | */ | | now, i'd say that it's fairly important for some form of threadsafe name | resolution to exist. until the KAME code is fixed, how about adding in the | ipv4 _r methods that have been discussed from time to time? or, at the very | least, put something in the manpage for getipnodebyname and friends | indicating that the funcs are not threadsafe. | | as you can probably tell, i wasted several hours worth of work bumping into | this problem. The problem lies deeper than that. Calls like gethostbyname() and friends are not threadsafe either, as they use an internal struct hostent and return a pointer to it (that another thread would happily clobber with its own data). Thread-happy functions we're supposed to be added by the Vixie people, and since I haven't checked up on it in about a year, they could be in there by now, but since we use BINDs name-resolver library, it's a contrib/ issue and our policy isn't to hack up the contrib/ tree. Of course, the door is always open for you to write the code and submit it to the bind team. 8) -Dan -- Man is a rational animal who always loses his temper when he is called upon to act in accordance with the dictates of reason. -- Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 9:58:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from copernicus.tranquility.net (copernicus.tranquility.net [206.152.117.186]) by hub.freebsd.org (Postfix) with ESMTP id B3BB537BEFD; Wed, 9 Aug 2000 09:58:26 -0700 (PDT) (envelope-from bweaver@copernicus.tranquility.net) Received: (from bweaver@localhost) by copernicus.tranquility.net (8.9.3/8.9.3) id MAA46378; Wed, 9 Aug 2000 12:00:06 -0500 (CDT) (envelope-from bweaver) Date: Wed, 9 Aug 2000 12:00:06 -0500 From: Ben Weaver To: Alan Clegg , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... Message-ID: <20000809120006.A46354@tranquility.net> References: <20000809042514.A46006@tranquility.net> <20000809080735.A55136@diskfarm.firehouse.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000809080735.A55136@diskfarm.firehouse.net>; from abc@bsdi.com on Wed, Aug 09, 2000 at 08:07:35AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heh... OK I'm done having my stupid moment... Thank's for seeing that :-) I'm still curious (just so I know) what an sblock magic number is. Thanks, -Ben On Wed, Aug 09, 2000 at 08:07:35AM +0000, Alan Clegg wrote: > Out of the ether, Ben Weaver spewed forth the following bitstream: > > > $ df > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/sd0s1a 3976982 909105 2749719 25% / > > /dev/sd1s1e 3976982 3359343 299481 92% /home > > /dev/sd2s1f 992751 817542 95789 90% /var > > procfs 4 4 0 100% /proc > > > bash-2.03# ssh backup@tranq1 /sbin/dump -0a -f - /dev/sd0s1f | dd of=t1.var > > DUMP: bad sblock magic number > > Note that you are dumping /dev/sd0s1f and not /dev/sd2s1f. /dev/sd0s1f does > not contain a valid filesystem, thus can't be dumped. > > AlanC > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 10: 7:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id ECB3C37BE4E; Wed, 9 Aug 2000 10:07:38 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA118432; Wed, 9 Aug 2000 13:07:25 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000810003052A.iwasaki@jp.FreeBSD.org> References: <20000810003052A.iwasaki@jp.FreeBSD.org> Date: Wed, 9 Aug 2000 13:08:09 -0400 To: Mitsuru IWASAKI , freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: ACPI project progress report (final?) Cc: freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:30 AM +0900 8/10/00, Mitsuru IWASAKI wrote: >Hi, here is the latest (and maybe final?) report on our ACPI >project's progress. > >We are ready now to merge our work on ACPI into main source tree! > >[...skipping...] >Folks, there are a lot of exciting and cool things, like Processor >and Device Power State Control, Thermal Management, Replacement >PnP system, OS initiated hibernation and many :-) I think now is >the time to start open and development, not only in Japan, for >FreeBSD ACPI support! This all sounds very useful! Glad to see it's merging into the current branch! --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 10:31: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.wmptl.com (mail2.wmptl.com [216.221.73.131]) by hub.freebsd.org (Postfix) with ESMTP id 0F9AC37B850 for ; Wed, 9 Aug 2000 10:30:55 -0700 (PDT) (envelope-from webmaster@wmptl.com) Received: from wmptl.com ([10.0.0.168]) by mail2.wmptl.com (8.9.3/8.9.3) with ESMTP id NAA76515; Wed, 9 Aug 2000 13:29:17 -0400 (EDT) (envelope-from webmaster@wmptl.com) Message-ID: <399194DB.47DCA8CD@wmptl.com> Date: Wed, 09 Aug 2000 13:28:59 -0400 From: Nathan Vidican X-Mailer: Mozilla 4.72 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Michael Lucas Cc: hackers@freebsd.org Subject: Re: SMBFS References: <200008091608.MAA45997@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > > My understanding of SMBFS is that it's not intended to be a server. > > It's a pretty solid client, though. I use it extensively, without trouble. > > ==ml > > > What's the current status the native smbfs support? Can it act as a both a > > client and a server? How does it compare to Samba in terms of functionality? > > > > Thanks, > > Brandon > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message How did you implement SMBFS? Is it yet a part of FreeBSD 4.1-STABLE or? New kernel option? -- Nathan Vidican webmaster@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 10:36:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 6E61F37B850 for ; Wed, 9 Aug 2000 10:36:29 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id NAA46435; Wed, 9 Aug 2000 13:36:18 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008091736.NAA46435@blackhelicopters.org> Subject: Re: SMBFS In-Reply-To: <399194DB.47DCA8CD@wmptl.com> from Nathan Vidican at "Aug 9, 2000 1:28:59 pm" To: webmaster@wmptl.com (Nathan Vidican) Date: Wed, 9 Aug 2000 13:36:18 -0400 (EDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How did you implement SMBFS? Is it yet a part of FreeBSD 4.1-STABLE or? > New kernel option? > Take a look at http://www.oreillynet.com/pub/a/bsd/2000/07/13/Big_Scary_Daemons.html. All the links, and some hints, appear there. Also, I don't want to claim even indirectly that I implemented it; I can't code my way out of a paper bag, unless it's wet. All I do is write about this stuff. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11: 7:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 4951A37BE60; Wed, 9 Aug 2000 11:07:15 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Wed, 9 Aug 2000 12:07:03 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B301302978F3E@bdr-xcln.is.matchlogic.com> From: Charles Randall To: Dan Moschuk , Greg Thompson Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: RE: threadsafe name resolution Date: Wed, 9 Aug 2000 12:07:01 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a reason that ADNS won't work for this? http://www.chiark.greenend.org.uk/~ian/adns/ Charles -----Original Message----- From: Dan Moschuk [mailto:dan@FreeBSD.ORG] Sent: Wednesday, August 09, 2000 10:51 AM To: Greg Thompson Cc: freebsd-hackers@FreeBSD.ORG; freebsd-net@FreeBSD.ORG Subject: Re: threadsafe name resolution | i've just received confirmation from the author of the KAME resolution code | that it isn't at all thread safe: | | >Sure. As noted in name6.c, thread related stuff is not implemented yet. | >Since our resolver code based on bind4 doesn't aware thread safeness, | >all I can do now would be only putting mutex, anyway. | | sure enough, name6.c says: | | /* | * TODO for thread safe | * use mutex for _hostconf, _hostconf_init. | * rewrite resolvers to be thread safe | */ | | now, i'd say that it's fairly important for some form of threadsafe name | resolution to exist. until the KAME code is fixed, how about adding in the | ipv4 _r methods that have been discussed from time to time? or, at the very | least, put something in the manpage for getipnodebyname and friends | indicating that the funcs are not threadsafe. | | as you can probably tell, i wasted several hours worth of work bumping into | this problem. The problem lies deeper than that. Calls like gethostbyname() and friends are not threadsafe either, as they use an internal struct hostent and return a pointer to it (that another thread would happily clobber with its own data). Thread-happy functions we're supposed to be added by the Vixie people, and since I haven't checked up on it in about a year, they could be in there by now, but since we use BINDs name-resolver library, it's a contrib/ issue and our policy isn't to hack up the contrib/ tree. Of course, the door is always open for you to write the code and submit it to the bind team. 8) -Dan -- Man is a rational animal who always loses his temper when he is called upon to act in accordance with the dictates of reason. -- Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11:14:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 09C5E37BEDC; Wed, 9 Aug 2000 11:13:30 -0700 (PDT) (envelope-from lplist@closedsrc.org) Received: from localhost (lplist@localhost) by q.closedsrc.org (8.11.0/8.11.0) with ESMTP id e79ICLn27184; Wed, 9 Aug 2000 11:12:21 -0700 (PDT) (envelope-from lplist@closedsrc.org) Date: Wed, 9 Aug 2000 11:12:21 -0700 (PDT) From: Linh Pham To: Mike Smith Cc: Josh Paetzel , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Installation Problems on Dell PowerEdge 6100/200 In-Reply-To: <200008090315.UAA15544@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Mike Smith mumbled: > > If it is worth anything, I tried installing on a poweredge 2450 once and to > > make a long story short couldn't get the onboard RAID to work or the SMP to > > work. I hear it got sent back for something else (that wasn't a dell!) > > Onboard RAID will be working shortly (waiting for someome to lend me > hardware), SMP works as of 4.1-RELEASE. The Dell PowerEdge 2450 server does not run off of an Intel chipset, but rather the ServerWorks SMP 100/133Mhz chiset. I don't know if FreeBSD supports SMP on non-Intel chipsets or not, but that might the problem :) // Linh Pham // http://closedsrc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11:15:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from spirit.jaded.net (shortbus.jaded.net [216.94.132.8]) by hub.freebsd.org (Postfix) with ESMTP id 5703337C0BE; Wed, 9 Aug 2000 11:15:12 -0700 (PDT) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id OAA01367; Wed, 9 Aug 2000 14:14:56 -0400 (EDT) (envelope-from dan) Date: Wed, 9 Aug 2000 14:14:56 -0400 From: Dan Moschuk To: Charles Randall Cc: Greg Thompson , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: threadsafe name resolution Message-ID: <20000809141456.L293@spirit.jaded.net> References: <5FE9B713CCCDD311A03400508B8B301302978F3E@bdr-xcln.is.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5FE9B713CCCDD311A03400508B8B301302978F3E@bdr-xcln.is.matchlogic.com>; from crandall@matchlogic.com on Wed, Aug 09, 2000 at 12:07:01PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Is there a reason that ADNS won't work for this? | | http://www.chiark.greenend.org.uk/~ian/adns/ Technically, no. Morally, it's GNU. :-) -- Man is a rational animal who always loses his temper when he is called upon to act in accordance with the dictates of reason. -- Oscar Wilde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11:21:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id 4F9EF37BA7D; Wed, 9 Aug 2000 11:21:19 -0700 (PDT) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 13MaTQ-000478-00; Wed, 09 Aug 2000 19:21:04 +0100 Date: Wed, 9 Aug 2000 19:21:04 +0100 From: Mike Bristow To: Charles Randall Cc: Dan Moschuk , Greg Thompson , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: threadsafe name resolution Message-ID: <20000809192104.A15793@lindt.urgle.com> References: <5FE9B713CCCDD311A03400508B8B301302978F3E@bdr-xcln.is.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <5FE9B713CCCDD311A03400508B8B301302978F3E@bdr-xcln.is.matchlogic.com>; from crandall@matchlogic.com on Wed, Aug 09, 2000 at 12:07:01PM -0600 X-Rated: IRA, insider dealing Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 12:07:01PM -0600, Charles Randall wrote: > Is there a reason that ADNS won't work for this? Firstly, adns doesn't do IPv6 (at least not yet, according to the web page you gave). Secondly, I'm not sure if it's thread safe (although being nice 'n async it's not hard to use it in threaded apps even if it isn't). Thirdly, adns is GPLed, which means you'll have a hell of a job getting people to include it into the base system. -- Mike Bristow, seebitwopie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11:36:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f39.law7.hotmail.com [216.33.237.39]) by hub.freebsd.org (Postfix) with ESMTP id 6EBCD37BA1C; Wed, 9 Aug 2000 11:36:44 -0700 (PDT) (envelope-from johnnyteardrop@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 9 Aug 2000 11:36:40 -0700 Received: from 209.249.186.215 by lw7fd.law7.hotmail.msn.com with HTTP; Wed, 09 Aug 2000 GMT X-Originating-IP: [209.249.186.215] From: "Greg Thompson" To: crandall@matchlogic.com Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: RE: threadsafe name resolution Date: Wed, 09 Aug 2000 14:36:40 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 09 Aug 2000 18:36:40.0153 (UTC) FILETIME=[C1EC0490:01C00230] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Charles Randall > >Is there a reason that ADNS won't work for this? > >http://www.chiark.greenend.org.uk/~ian/adns/ in addition to the other reasons mentioned, it won't work for me because it's not a part of the os. as an application developer, i'd expect the basic services to work without me having to grab random packages to solve already solved problems. someone else pointed out that the old gethostbyname/addr pair isn't threadsafe. i realize this. what i was suggesting is that someone could perhaps implement gethostbyname_r and gethostbyaddr_r. call these a hack if you will, but they solve the problem just fine on other platforms. as long as nothing other than getipnodebyname and byaddr share resources with those two, i'm safe if i just throw a mutex around my calls to byname/addr. unfortuantely, this solution gets the "big suck" rating. if the operating system ships with mechanisms that are documented as being thread-safe, they should be. if they're not, it should be clearly stated in a bug report somewhere that this is the case. i have submitted a bug with KAME. i hope they fix it soon. in the meantime, it'd be nice if freebsd had an alternative. ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 11:37:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 9CFA437C0D8 for ; Wed, 9 Aug 2000 11:37:11 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id LAA33249; Wed, 9 Aug 2000 11:36:39 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008091836.LAA33249@bubba.whistle.com> Subject: Re: CVS question In-Reply-To: <200008091554.IAA53597@vashon.polstra.com> from John Polstra at "Aug 9, 2000 08:54:58 am" To: John Polstra Date: Wed, 9 Aug 2000 11:36:39 -0700 (PDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > > $ cvs co -D 'January 18, 1999 0:00' freebsd/src/usr.sbin/xntpd/lib/ranny.c > > > > Perhaps version 1.1.1.2 would be correct, but instead you get 1.1. > > CVS has a heuristic that does the wrong thing for this particular > file. The code is around line 3252 of src/contrib/cvs/src/rcs.c in > the function RCS_getdate(): > > if (! STREQ (cur_rev, "1.1")) > return (xstrdup (cur_rev)); > > /* This is 1.1; if the date of 1.1 is not the same as that for the > 1.1.1.1 version, then return 1.1. This happens when the first > version of a file is created by a regular cvs add and commit, > and there is a subsequent cvs import of the same file. */ > p = findnode (rcs->versions, "1.1.1.1"); > if (p) > { > vers = (RCSVers *) p->data; > if (RCS_datecmp (vers->date, date) != 0) > return xstrdup ("1.1"); > } > > It compares the dates on the theory that an import will set > identical dates in revisions 1.1 and 1.1.1.1. But in the file you > mentioned, they are off by 1 second. So CVS doesn't recognize it as > an import. > > revision 1.1 > date: 1993/12/21 18:36:22; author: wollman; state: Exp; > > revision 1.1.1.1 > date: 1993/12/21 18:36:23; author: wollman; state: Exp; lines: +0 -0 > > Probably the import straddled the seconds boundary. I hope current > versions of CVS force the dates to be the same on an import. I > haven't checked to see whether that's the case or not. Hmm.. sounds like we should do one or both of these things.. 1/ Fix the bug in CVS that caused the import to set two different dates 2/ Modify this cvs file to set the dates to be the same What do you think? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 12:47:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 983F037B635; Wed, 9 Aug 2000 12:47:13 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13Mbol-000J2n-00; Wed, 09 Aug 2000 19:47:11 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA10411; Wed, 9 Aug 2000 21:47:03 +0200 (CEST) (envelope-from wkb) Date: Wed, 9 Aug 2000 21:47:03 +0200 From: Wilko Bulte To: Ben Weaver Cc: Alan Clegg , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... Message-ID: <20000809214703.A10364@freebie.demon.nl> References: <20000809042514.A46006@tranquility.net> <20000809080735.A55136@diskfarm.firehouse.net> <20000809120006.A46354@tranquility.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000809120006.A46354@tranquility.net>; from bweaver@tranquility.net on Wed, Aug 09, 2000 at 12:00:06PM -0500 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 12:00:06PM -0500, Ben Weaver wrote: > Heh... OK I'm done having my stupid moment... Thank's for seeing that :-) > > I'm still curious (just so I know) what an sblock magic number is. Guessing: superblock? -- Wilko Bulte wilko@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 12:54:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5038D37B626; Wed, 9 Aug 2000 12:54:03 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA99070; Wed, 9 Aug 2000 13:53:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA50150; Wed, 9 Aug 2000 13:53:21 -0600 (MDT) Message-Id: <200008091953.NAA50150@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: ACPI project progress report (final?) Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org In-reply-to: Your message of "Thu, 10 Aug 2000 00:30:52 +0900." <20000810003052A.iwasaki@jp.FreeBSD.org> References: <20000810003052A.iwasaki@jp.FreeBSD.org> Date: Wed, 09 Aug 2000 13:53:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000810003052A.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: : Hi, here is the latest (and maybe final?) report on our ACPI project's : progress. : : We are ready now to merge our work on ACPI into main source tree! Bravo! Wonderful work! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 13:11:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mesache.encomix.es (mesache.encomix.es [194.143.192.3]) by hub.freebsd.org (Postfix) with SMTP id 3EEC537B5C6 for ; Wed, 9 Aug 2000 13:11:07 -0700 (PDT) (envelope-from arnaiz@encomix.es) Received: (qmail 26978 invoked from network); 9 Aug 2000 20:11:04 -0000 Received: from unknown (HELO feliz) (195.114.199.228) by mesache.encomix.es with SMTP; 9 Aug 2000 20:11:04 -0000 From: =?iso-8859-1?B?SmVz+nMgQXJu4Wl6?= To: "freebsd-hackers" Subject: Logging changes in files. Date: Wed, 9 Aug 2000 22:09:47 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Everyone! I'm using FreeBSD and I'm interesting in log when a user modifies some file and the changes made on it. Have someone done something similar or have some idea to help me?. Thanks in advance. Jesús Arnáiz. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 14: 9:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id D2FD137B65F for ; Wed, 9 Aug 2000 14:09:09 -0700 (PDT) (envelope-from t.vanklaveren@student.utwente.nl) Received: from phoenix (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.8.6/MQT) with SMTP id XAA23623; Wed, 9 Aug 2000 23:07:54 +0200 (METDST) Message-ID: <003f01c00245$eddc2340$19e55982@student.utwente.nl> From: "Theo van Klaveren" To: "Soren Schmidt" Cc: References: <200008091551.RAA77500@freebsd.dk> Subject: Re: In-kernel ioctl calls Date: Wed, 9 Aug 2000 23:08:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: -long story snipped- | > Am I just doing it wrong, or should atapi-cd.c be patched to verify if the | > buffer is in user space or in kernel space? If so, what function checks if | > an address is in kernel space or in user space? If not, what am I doing | > wrong? | | Here's another idea, the ata driver can read/write 2352 sector size | blocks directly, no need to use that ugly ioctl. You just have to | set the right blocksize, I could provide you with a function for | that, no more ioctl mess ;) That would be _greatly_ appreciated! The question is, would this be 'portable' to other drivers? In other words, how much trouble would it cost me to get AudioFS to work with SCSI? (On a side note, I'll be getting a SCSI card and accompanying Plextor CDROM from a friend of mine soon, so I can work at getting AudioFS to work on SCSI CDROMs). Theo van Klaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 14:14:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lychee.itojun.org (h066.p043.iij4u.or.jp [210.130.43.66]) by hub.freebsd.org (Postfix) with ESMTP id 9FC9C37BA28; Wed, 9 Aug 2000 14:14:47 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.10.0/3.7W) with ESMTP id e79LEI610855; Thu, 10 Aug 2000 06:14:18 +0900 (JST) Message-Id: <200008092114.e79LEI610855@itojun.org> To: "Greg Thompson" Cc: crandall@matchlogic.com, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG In-reply-to: johnnyteardrop's message of Wed, 09 Aug 2000 14:36:40 EDT. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: threadsafe name resolution From: Jun-ichiro itojun Hagino Date: Thu, 10 Aug 2000 06:14:18 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >as long as nothing other than getipnodebyname and byaddr share resources >with those two, i'm safe if i just throw a mutex around my calls to >byname/addr. unfortuantely, this solution gets the "big suck" rating. if >the operating system ships with mechanisms that are documented as being >thread-safe, they should be. if they're not, it should be clearly stated in >a bug report somewhere that this is the case. i have submitted a bug with >KAME. i hope they fix it soon. in the meantime, it'd be nice if freebsd >had an alternative. sorry for bad documentation, manpage should be updated to state "the current implementation is not thread safe" in BUGS section. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 14:19:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id CB7FD37B78B for ; Wed, 9 Aug 2000 14:19:17 -0700 (PDT) (envelope-from t.vanklaveren@student.utwente.nl) Received: from phoenix (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.8.6/MQT) with SMTP id XAA26051; Wed, 9 Aug 2000 23:19:14 +0200 (METDST) Message-ID: <007901c00247$82fe2080$19e55982@student.utwente.nl> From: "Theo van Klaveren" To: "Koster, K.J." Cc: "FreeBSD Hackers" References: <59063B5B4D98D311BC0D0001FA7E4522026D7782@l04.research.kpn.com> Subject: Re: audiofs mixing audio and data tracks Date: Wed, 9 Aug 2000 23:19:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Koster, K.J. wrote: | Could you perhaps make it so that all the audio tracks appear als slice 1, | while the data track appears as slice 2. Sorry if I come across rude, but I've had numerous requests for this and just wanted to say what I think about it. I can't think of any way of accomplishing this without either: 1) Combining the code for AudioFS and CD9660, as both require access to the mounted device, and hacking them to respect each other, or 2) Hacking the ATAPI-CD and SCSI-CD drivers to bits and teaching them about the various regions on the CD. Neither are very attractive, IMHO, and I don't think the trouble is worth it by far. But if anyone knows a clean, un-hackish way to accomplish double-mounting a multi-track CD, please make yourself heard. Otherwise, I declare this subject closed. Theo van Klaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 15: 6:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DB4AA37B95D; Wed, 9 Aug 2000 15:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA53520; Wed, 9 Aug 2000 15:06:45 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 9 Aug 2000 15:06:45 -0700 (PDT) From: Kris Kennaway To: =?iso-8859-1?B?SmVz+nMgQXJu4Wl6?= Cc: freebsd-hackers Subject: Re: Logging changes in files. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, [iso-8859-1] Jes=FAs Arn=E1iz wrote: > Hi Everyone! >=20 > I'm using FreeBSD and I'm interesting in log when a user modifies some fi= le > and the changes made on it. See the kqueue(2) manpage in FreeBSD 4.1. It would be a trivial matter to write a utility that watches files for activity and logs it, although finding out who modified the file would be harder. The "proper" way to do this is using a kernel event audit system, which is something the TrustedBSD project (www.trustedbsd.org) will provide, but AFAIK no code is available for this yet. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 16: 6:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual.valuelinx.net (virtual.valuelinx.net [208.189.209.17]) by hub.freebsd.org (Postfix) with ESMTP id 8563C37B626 for ; Wed, 9 Aug 2000 16:06:33 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org (ppp8825.on.bellglobal.com [207.236.126.9]) by virtual.valuelinx.net (8.9.1/8.9.1) with SMTP id XAA30722 for ; Wed, 9 Aug 2000 23:06:25 GMT Message-ID: <3991E2EE.ADB4CD2E@penix.org> Date: Wed, 09 Aug 2000 19:02:06 -0400 From: Paul Halliday X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: PC compatibility cards. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Kinda off topic, but maybe not. I just aquired a few pc compatibility cards. From what I can ascertain they have an onboard p166 processor, 16m ram, 2 meg ati video, 256k cache, etc. Anyway, after a little reading i figured out what these little buggers do. Now, has anyone ever tried to mod one of these things and use it in a "pc"?, they are designed for Macs. If anyone has played with one of these, any info would be greatly appreciated. Paul H. ============================================================================ Don't underestimate the power of stupid people in large groups. Email: dp@penix.org GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 Public Key available here: http://www3.sympatico.ca/transmogrify/dp.asc Linux < FreeBSD ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 16:37: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 5566B37B5FF for ; Wed, 9 Aug 2000 16:36:52 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id SAA61463; Wed, 9 Aug 2000 18:36:48 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Wed, 9 Aug 2000 18:36:48 -0500 (CDT) From: David Scheidt To: Paul Halliday Cc: hackers@freebsd.org Subject: Re: PC compatibility cards. In-Reply-To: <3991E2EE.ADB4CD2E@penix.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Paul Halliday wrote: : Hi. : : Kinda off topic, but maybe not. : :I just aquired a few pc compatibility cards. From what I can ascertain :they have an onboard p166 processor, 16m ram, 2 meg ati video, 256k :cache, etc. Anyway, after a little reading i figured out what these :little buggers do. Now, has anyone ever tried to mod one of these things :and use it in a "pc"?, they are designed for Macs. : : If anyone has played with one of these, any info would be greatly :appreciated. : The ones I am familiar with were 486 somethings in PowerMac 6100s. I have no idea if you could run FreeBSD on them; they certainly wouldn't work *in* a PC, being PDS cards. ARe the ones you have PCI? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 16:50: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual.valuelinx.net (virtual.valuelinx.net [208.189.209.17]) by hub.freebsd.org (Postfix) with ESMTP id 0BF5537B5FF for ; Wed, 9 Aug 2000 16:49:54 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org (ppp8825.on.bellglobal.com [207.236.126.9]) by virtual.valuelinx.net (8.9.1/8.9.1) with SMTP id XAA00579; Wed, 9 Aug 2000 23:49:46 GMT Message-ID: <3991ED15.8345F03F@penix.org> Date: Wed, 09 Aug 2000 19:45:25 -0400 From: Paul Halliday X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Scheidt Cc: hackers@freebsd.org Subject: Re: PC compatibility cards. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > The ones I am familiar with were 486 somethings in PowerMac 6100s. I have > no idea if you could run FreeBSD on them; they certainly wouldn't work *in* > a PC, being PDS cards. ARe the ones you have PCI? > > David As a matter of fact, they are. Or at least appear to be. -- Paul H. ============================================================================ Don't underestimate the power of stupid people in large groups. Email: dp@penix.org GPG Key fingerprint: 2D7C A7E2 DB1F EA5F 8C6F D5EC 3D39 F274 4AA3 E8B9 Public Key available here: http://www3.sympatico.ca/transmogrify/dp.txt Linux < FreeBSD ============================================================================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 17:40:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c1030098-a.wtrlo1.ia.home.com (c1030098-a.wtrlo1.ia.home.com [24.14.126.45]) by hub.freebsd.org (Postfix) with ESMTP id 1FF9637BF0E; Wed, 9 Aug 2000 17:40:55 -0700 (PDT) (envelope-from mdharnois@home.com) Received: (from mdharnois@localhost) by c1030098-a.wtrlo1.ia.home.com (8.9.3/8.9.3) id TAA07191; Wed, 9 Aug 2000 19:40:44 -0500 (CDT) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) References: <20000810003052A.iwasaki@jp.FreeBSD.org> From: Michael Harnois Date: 09 Aug 2000 19:40:44 -0500 In-Reply-To: Mitsuru IWASAKI's message of "Thu, 10 Aug 2000 00:30:52 +0900" Message-ID: <868zu6uewj.fsf@mharnois.workgroup.net> Lines: 8 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Carlsbad Caverns) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not quite sure what it does, but it seems to work fine here on my ASUS CUSL2, at least the shutdown part. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org When the stomach is satisfied, and lust is spent, man spares a little time for God. -- Will Durant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 18: 8: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id DE9CD37B736; Wed, 9 Aug 2000 18:08:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA02527; Wed, 9 Aug 2000 18:19:47 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008100119.SAA02527@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-questions@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Installation Problems on Dell PowerEdge 6100/200 In-reply-to: Your message of "Wed, 09 Aug 2000 11:12:21 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Aug 2000 18:19:47 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 8 Aug 2000, Mike Smith mumbled: > > > > If it is worth anything, I tried installing on a poweredge 2450 once and to > > > make a long story short couldn't get the onboard RAID to work or the SMP to > > > work. I hear it got sent back for something else (that wasn't a dell!) > > > > Onboard RAID will be working shortly (waiting for someome to lend me > > hardware), SMP works as of 4.1-RELEASE. > > The Dell PowerEdge 2450 server does not run off of an Intel chipset, > but rather the ServerWorks SMP 100/133Mhz chiset. > > I don't know if FreeBSD supports SMP on non-Intel chipsets or not, but > that might the problem :) You will note in my previous message that I said that SMP works on this system as of 4.1. Obviously, this means that we run on the RCC ServerWorks chipsets... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 18:39:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ipperformance.com (cooper.gilhooley.com [207.8.92.84]) by hub.freebsd.org (Postfix) with ESMTP id 94CCF37B5E3 for ; Wed, 9 Aug 2000 18:39:32 -0700 (PDT) (envelope-from rbg@ipperformance.com) Received: from rbg.gilhooley.com ([10.1.0.66]) by ipperformance.com (8.9.3/8.9.3) with ESMTP id TAA30425 for ; Wed, 9 Aug 2000 19:28:47 -0500 (CDT) (envelope-from rbg@ipperformance.com) Received: from localhost (localhost [127.0.0.1]) by rbg.gilhooley.com (8.9.3/8.9.3) with ESMTP id KAA06343; Tue, 8 Aug 2000 10:24:42 -0500 (CDT) (envelope-from rbg@ipperformance.com) From: rbg@ipperformance.com Date: Tue, 08 Aug 2000 10:24:42 -0500 (CDT) Message-Id: <20000808.102442.23011361.rbg@ipperformance.com> To: bob@immure.com, bob@luke.immure.com Cc: freebsd-hackers@freebsd.org Subject: Re: How do I change serial console tty speed? In-Reply-To: <20000808085359.B27718@luke.immure.com> References: <20000808085225.A27718@luke.immure.com> <20000808085359.B27718@luke.immure.com> X-Mailer: Mew version 1.95b43 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Bob, Did you try setting it with sysctl in one of the rc.* files ? Good luck! Robert........ > On Tue, 8 Aug 2000 08:53:59 -0500 you said: bob> Oops, I forgot to add that this is on a 4.0-stable system (from about 3 bob> months ago). bob> bob> Thanks again, bob> Bob bob> bob> On Tue, Aug 08, 2000 at 08:52:25AM -0500, Bob Willcox wrote: bob> > Hi All, bob> > bob> > I have tried everything I could think of to raise the speed of my bob> > system's serial console from 9600 baud to something faster w/o bob> > any success. The things that I have tried are: setting "options bob> > CONSPEED=38400" in my kernel config file and putting a "set bob> > CONSPEED=38400" in the /boot/loader.rc file to no avail. bob> > bob> > No doubt I am missing something. bob> > bob> > Any help would be greatly appreciated! bob> > bob> > Thanks, bob> > Bob bob> > bob> > -- bob> > Bob Willcox Man usually avoids attributing cleverness to somebody else -- bob> > bob@immure.com unless it is an enemy. bob> > Austin, TX -- A. Einstein bob> bob> -- bob> Bob Willcox Man usually avoids attributing cleverness to somebody else -- bob> bob@immure.com unless it is an enemy. bob> Austin, TX -- A. Einstein bob> bob> bob> To Unsubscribe: send mail to majordomo@FreeBSD.org bob> with "unsubscribe freebsd-hackers" in the body of the message __________________________________________________________________________ Robert Gordon rbg@ipperformance.com IP Performance, Inc Austin, Texas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 20: 9:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 414B937B556 for ; Wed, 9 Aug 2000 20:09:27 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.7/nospam) with UUCP id FAA27117 for freebsd-hackers@freebsd.org; Thu, 10 Aug 2000 05:09:25 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 2FA008889; Thu, 10 Aug 2000 00:46:34 +0200 (CEST) Date: Thu, 10 Aug 2000 00:46:34 +0200 From: Ollivier Robert To: freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... Message-ID: <20000810004633.A74732@keltia.freenix.fr> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20000809042514.A46006@tranquility.net> <20000809080735.A55136@diskfarm.firehouse.net> <20000809120006.A46354@tranquility.net> <20000809214703.A10364@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <20000809214703.A10364@freebie.demon.nl>; from wkb@freebie.demon.nl on Wed, Aug 09, 2000 at 09:47:03PM +0200 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wilko Bulte: > Guessing: superblock? Yes. Our dump is only able to backup complete filesystems. Historically, SunOS' one is able to backup partial FS (i.e. directories) and ironically, when Rémy Card (of ext2fs fame) ported it to Linux, he added back that functionality. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 20:35:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id F362137B638 for ; Wed, 9 Aug 2000 20:35:11 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id E28AAA845; Thu, 10 Aug 2000 13:35:58 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id D7984544C for ; Thu, 10 Aug 2000 13:35:58 +1000 (EST) Date: Thu, 10 Aug 2000 13:35:58 +1000 (EST) From: andrew@ugh.net.au To: freebsd-hackers@freebsd.org Subject: libvgl and splitting the screen Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is it possible to use libvgl but get it to use just part of the screen so I have a regular text console above? I'm guessing not... I'm trying to get text to scroll along the bottom of the screen (lame I know)...is there another way? I can scroll in character chunks by printing substrings of the string but that looks a bit jerky to the eye. I didn't want to have to use libvgl to do all the drawing of text on the rest of the screen. If I do end up using libvgl what are legal values for VGLInit? The only value that seems to work is SW_VGA_MODEX but I was after something with a bit higher resolution...SW_VGA_VG640 is mentioned in a comment in examples/libvgl/demo.c but is undefined, SW_VGA_CG640 returns an error (-1). I'm guessing it depends on the video card about which dmesg says: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Its in a Compaq Prolinea 4/50 and I have no idea what it is but it can do 640x480 under X (using VGA16 and the 'generic' chipset). Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 20:43:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 039D137B645 for ; Wed, 9 Aug 2000 20:43:17 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 58BD7A845; Thu, 10 Aug 2000 13:44:09 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 55799544C for ; Thu, 10 Aug 2000 13:44:09 +1000 (EST) Date: Thu, 10 Aug 2000 13:44:09 +1000 (EST) From: andrew@ugh.net.au To: freebsd-hackers@freebsd.org Subject: Re: libvgl and splitting the screen In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to follow up on my own posting but this is under 4.1-STABLE as of last week. Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 9 23:48:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DB6FF37B80E for ; Wed, 9 Aug 2000 23:48:52 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA91303; Thu, 10 Aug 2000 08:48:50 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008100648.IAA91303@freebsd.dk> Subject: Re: In-kernel ioctl calls In-Reply-To: <003f01c00245$eddc2340$19e55982@student.utwente.nl> from Theo van Klaveren at "Aug 9, 2000 11:08:12 pm" To: t.vanklaveren@student.utwente.nl (Theo van Klaveren) Date: Thu, 10 Aug 2000 08:48:50 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Theo van Klaveren wrote: > | Here's another idea, the ata driver can read/write 2352 sector size > | blocks directly, no need to use that ugly ioctl. You just have to > | set the right blocksize, I could provide you with a function for > | that, no more ioctl mess ;) > > That would be _greatly_ appreciated! The question is, would this be > 'portable' to other drivers? In other words, how much trouble would it cost > me to get AudioFS to work with SCSI? I dont think the SCSI/CAM system can cope with != % 512 byte blocks, so you are out of luck there, but then again SCSI/CAM doesnt support CDIOCREADAUDIO either, so you are not worse of than now :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 0:36:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 6C20637B981 for ; Thu, 10 Aug 2000 00:36:09 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA70153; Thu, 10 Aug 2000 01:34:32 -0600 (MDT) (envelope-from ken) Date: Thu, 10 Aug 2000 01:34:32 -0600 From: "Kenneth D. Merry" To: Theo van Klaveren Cc: Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: In-kernel ioctl calls Message-ID: <20000810013431.A69961@panzer.kdm.org> References: <200008091551.RAA77500@freebsd.dk> <003f01c00245$eddc2340$19e55982@student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <003f01c00245$eddc2340$19e55982@student.utwente.nl>; from t.vanklaveren@student.utwente.nl on Wed, Aug 09, 2000 at 11:08:12PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 23:08:12 +0200, Theo van Klaveren wrote: > Soren Schmidt wrote: > -long story snipped- > | > Am I just doing it wrong, or should atapi-cd.c be patched to verify if > the > | > buffer is in user space or in kernel space? If so, what function checks > if > | > an address is in kernel space or in user space? If not, what am I doing > | > wrong? > | > | Here's another idea, the ata driver can read/write 2352 sector size > | blocks directly, no need to use that ugly ioctl. You just have to > | set the right blocksize, I could provide you with a function for > | that, no more ioctl mess ;) > > That would be _greatly_ appreciated! The question is, would this be > 'portable' to other drivers? In other words, how much trouble would it cost > me to get AudioFS to work with SCSI? Getting AudioFS to work with SCSI drives is non-trivial, if you want it to work with a wide variety of drives. The reason is that different SCSI CDROM vendors had (have?) different ways of reading CD audio data off the drive. If you just want it to work with MMC-compliant drives, it might not be that hard to implement. If you want it to work with more than just MMC-compliant drives (and there are a lot of them out there), it'll take a fair number of quirk entries and device-specific code to do it. For an idea of the variety of different drives out there, take a look at tosha or cdda2wav (comes with cdrecord). They handle most of the drives on the market. (Thus the reason I didn't put all the code in the driver to do it.) If you decide you want to tackle it, let me know. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 0:43:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 21E1237BA48 for ; Thu, 10 Aug 2000 00:43:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA70193; Thu, 10 Aug 2000 01:42:50 -0600 (MDT) (envelope-from ken) Date: Thu, 10 Aug 2000 01:42:50 -0600 From: "Kenneth D. Merry" To: Soren Schmidt Cc: Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: In-kernel ioctl calls Message-ID: <20000810014250.B69961@panzer.kdm.org> References: <003f01c00245$eddc2340$19e55982@student.utwente.nl> <200008100648.IAA91303@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008100648.IAA91303@freebsd.dk>; from sos@freebsd.dk on Thu, Aug 10, 2000 at 08:48:50AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 08:48:50 +0200, Soren Schmidt wrote: > It seems Theo van Klaveren wrote: > > | Here's another idea, the ata driver can read/write 2352 sector size > > | blocks directly, no need to use that ugly ioctl. You just have to > > | set the right blocksize, I could provide you with a function for > > | that, no more ioctl mess ;) > > > > That would be _greatly_ appreciated! The question is, would this be > > 'portable' to other drivers? In other words, how much trouble would it cost > > me to get AudioFS to work with SCSI? > > I dont think the SCSI/CAM system can cope with != % 512 byte blocks, so > you are out of luck there, but then again SCSI/CAM doesnt support > CDIOCREADAUDIO either, so you are not worse of than now :) True enough, the cd(4) driver uses whatever blocksize the drive returns in response to a read capacity command. (And that is generally either 2048 or 512 bytes.) As for the CDIOCREADAUDIO ioctl, as I mentioned to Theo in a previous message, there are a wide variety of methods that SCSI CDROM vendors have used to get CDDA data off the disks. Thus the reason I've left support for CDDA extraction to external programs like tosha and cdda2wav. :) Neither one of those obstacles is insurmountable, but they will make it more difficult to support something like AudioFS with the SCSI CD driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 0:59:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id D45AB37B645 for ; Thu, 10 Aug 2000 00:59:19 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JSSUIN3OQU00084M@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Thu, 10 Aug 2000 09:59:13 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Thu, 10 Aug 2000 09:59:12 +0100 Content-return: allowed Date: Thu, 10 Aug 2000 09:59:12 +0100 From: "Koster, K.J." Subject: RE: audiofs mixing audio and data tracks To: 'Theo van Klaveren' Cc: FreeBSD Hackers Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7786@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I can't think of any way of accomplishing this without > either: > 1) Combining the code for AudioFS and CD9660, as both > require access to the mounted device, and hacking them > to respect each other, or > 2) Hacking the ATAPI-CD and SCSI-CD drivers to bits and > teaching them about the various regions on the CD. > I'm a little surprised that the functionality of accessing a track on a digital storage medium and doing stuff like getting a directory listing out of a track are in the same chunk of code. I lived under the impression that there were some layers of abstraction between those two. I guess not. I learn a little every day. Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 1:24:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4555837BA5F for ; Thu, 10 Aug 2000 01:24:49 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA13546; Thu, 10 Aug 2000 10:24:45 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008100824.KAA13546@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7786@l04.research.kpn.com> from "Koster, K.J." at "Aug 10, 2000 09:59:12 am" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Thu, 10 Aug 2000 10:24:45 +0200 (CEST) Cc: t.vanklaveren@student.utwente.nl ('Theo van Klaveren'), freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Koster, K.J. wrote: > > > > I can't think of any way of accomplishing this without > > either: > > 1) Combining the code for AudioFS and CD9660, as both > > require access to the mounted device, and hacking them > > to respect each other, or > > 2) Hacking the ATAPI-CD and SCSI-CD drivers to bits and > > teaching them about the various regions on the CD. > > > I'm a little surprised that the functionality of accessing a track on a > digital storage medium and doing stuff like getting a directory listing out > of a track are in the same chunk of code. I lived under the impression that > there were some layers of abstraction between those two. > > I guess not. I learn a little every day. Ahem, maybe its time I chime in here. Luigi and I once had an idea of having each track on a CD represented by a device node, ie track0 = /dev/acd0t1 track1 = /dev/acd0t2 etc etc, that way you could mount each track with whatever fs it supported. This could be used to do what you want, and now where the ata driver supports odd sector sizes, there is nothing hindering doing the mount of an audio track (given the right mount_bla util that is). The only problem is that we have to abuse the minor# etc to get space for the 99 tracks a CD can hold, but that is not too bad... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 1:25: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by hub.freebsd.org (Postfix) with ESMTP id 9E83D37BA86 for ; Thu, 10 Aug 2000 01:24:55 -0700 (PDT) (envelope-from johan@ockle.dev.nanoteq.co.za) Received: (from johan@localhost) by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id KAA04385; Thu, 10 Aug 2000 10:34:52 +0200 (SAST) (envelope-from johan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 10 Aug 2000 10:34:52 +0200 (SAST) Organization: Nanoteq From: Johan Kruger To: andrew@ugh.net.au Subject: RE: libvgl and splitting the screen Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Use VGLInit(SW_CG640x480); Look in the /sys/console.h for modes, plenty of them ( of course not all will work with every card but htis one seems mostly usable) Enjoy ;-) And O, yip , i guess you would have to do the scrolling the hard way. Half the screen 640x240 pixels ( the bottom half ) could be addressed by allocating a seperate memeory biffer of that size , draw into it, and the move the memory ( or copy it if you want to keep it ) to the current videobuffer by using the pointer libvgl provides. On 10-Aug-00 andrew@ugh.net.au wrote: > substrings of the string but that looks a bit jerky to the eye. I didn't > .... ... > > Its in a Compaq Prolinea 4/50 and I have no idea what it is but it can do > 640x480 under X (using VGA16 and the 'generic' chipset). > > Thanks, > > Andrew > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------- E-Mail: Johan Kruger Date: 10-Aug-00 Time: 10:29:44 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 1:32: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 65BFD37BA0D for ; Thu, 10 Aug 2000 01:32:00 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JSSVN978S00006Z1@research.kpn.com> for freebsd-hackers@FreeBSD.ORG; Thu, 10 Aug 2000 10:31:58 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Thu, 10 Aug 2000 10:31:57 +0100 Content-return: allowed Date: Thu, 10 Aug 2000 10:31:56 +0100 From: "Koster, K.J." Subject: RE: audiofs mixing audio and data tracks To: 'Soren Schmidt' Cc: freebsd-hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7789@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > that way you could mount each track with whatever fs it > supported. > Same thing as I proposed, I guess. Am I right in thinking that a cdrom can have at most one data track? In that case, I'd suggest assighing that track a standard device node. That way I could just mount the data track of a cdrom, without worrying if that's track 4 or track 1. Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. Douglas Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 1:36:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 12F3337B9E7 for ; Thu, 10 Aug 2000 01:36:16 -0700 (PDT) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id SAA21155; Thu, 10 Aug 2000 18:31:46 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <200008100831.SAA21155@mail.theinternet.com.au> Subject: Re: libvgl and splitting the screen In-Reply-To: from Johan Kruger at "Aug 10, 2000 10:34:52 am" To: Johan Kruger Date: Thu, 10 Aug 2000 18:31:46 +1000 (EST) Cc: andrew@ugh.net.au, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG +----[ Johan Kruger ]--------------------------------------------- | Use VGLInit(SW_CG640x480); | Look in the /sys/console.h for modes, plenty of them ( of course | not all will work with every card but htis one seems mostly usable) | Enjoy ;-) | | And O, yip , i guess you would have to do the scrolling the hard way. | Half the screen 640x240 pixels ( the bottom half ) could be addressed by | allocating a seperate memeory biffer of that size , draw into it, and the move | the memory ( or copy it if you want to keep it ) to the current videobuffer | by using the pointer libvgl provides. You could also look at microwindows:- http://microwindows.censoft.com/ I have made this work with libVgl, and moused. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 1:42:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8C83137BB08 for ; Thu, 10 Aug 2000 01:42:43 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA17703; Thu, 10 Aug 2000 10:42:41 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008100842.KAA17703@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7789@l04.research.kpn.com> from "Koster, K.J." at "Aug 10, 2000 10:31:56 am" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Thu, 10 Aug 2000 10:42:41 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Koster, K.J. wrote: > > > > that way you could mount each track with whatever fs it > > supported. > > > Same thing as I proposed, I guess. > > Am I right in thinking that a cdrom can have at most one data track? In that > case, I'd suggest assighing that track a standard device node. That way I > could just mount the data track of a cdrom, without worrying if that's track > 4 or track 1. Mostly yes, but there is nothing hindering multiple data tracks on the same CD. At any rate we only have access to one now anyways so that wouldn't hurt anything :) I'll look into it again, it could be a "very nice thing to have" (tm), imagine ripping audio just by dd if=/dev/acd0ct4 of=title4.raw bs=2352 well that kindof works already ;) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 2: 3:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id D2DC237B655 for ; Thu, 10 Aug 2000 02:03:49 -0700 (PDT) (envelope-from fanf@dotat.at) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13MoEq-000Bp2-00; Thu, 10 Aug 2000 09:02:56 +0000 Date: Thu, 10 Aug 2000 09:02:55 +0000 From: Tony Finch To: Soren Schmidt Cc: "Koster, K.J." , freebsd-hackers@FreeBSD.ORG Subject: Re: audiofs mixing audio and data tracks Message-ID: <20000810090255.F468@hand.dotat.at> References: <59063B5B4D98D311BC0D0001FA7E4522026D7789@l04.research.kpn.com> <200008100842.KAA17703@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008100842.KAA17703@freebsd.dk> Organization: Covalent Technologies, Inc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: >It seems Koster, K.J. wrote: >> >> Am I right in thinking that a cdrom can have at most one data track? In that >> case, I'd suggest assighing that track a standard device node. That way I >> could just mount the data track of a cdrom, without worrying if that's track >> 4 or track 1. > >Mostly yes, but there is nothing hindering multiple data tracks on >the same CD. At any rate we only have access to one now anyways so >that wouldn't hurt anything :) How does this relate to multi-session CDs? Does that happen at a lower layer? Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 2:28: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C436037B518 for ; Thu, 10 Aug 2000 02:28:00 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA28154; Thu, 10 Aug 2000 11:27:56 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008100927.LAA28154@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks In-Reply-To: <20000810090255.F468@hand.dotat.at> from Tony Finch at "Aug 10, 2000 09:02:55 am" To: dot@dotat.at (Tony Finch) Date: Thu, 10 Aug 2000 11:27:56 +0200 (CEST) Cc: K.J.Koster@kpn.com (Koster K.J.), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tony Finch wrote: > Soren Schmidt wrote: > >It seems Koster, K.J. wrote: > >> > >> Am I right in thinking that a cdrom can have at most one data track? In that > >> case, I'd suggest assighing that track a standard device node. That way I > >> could just mount the data track of a cdrom, without worrying if that's track > >> 4 or track 1. > > > >Mostly yes, but there is nothing hindering multiple data tracks on > >the same CD. At any rate we only have access to one now anyways so > >that wouldn't hurt anything :) > > How does this relate to multi-session CDs? Does that happen at a lower layer? Same thing, we always uses the last session written (which can include parts from earlier written sessions), so the first track on the last session will be the default track you get on /dev/acdN[ac] just as it is now. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 2:30:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id 6EF1537B966 for ; Thu, 10 Aug 2000 02:30:26 -0700 (PDT) (envelope-from t.vanklaveren@student.utwente.nl) Received: from phoenix (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.8.6/MQT) with SMTP id LAA13374; Thu, 10 Aug 2000 11:29:04 +0200 (METDST) Message-ID: <004701c002ad$77378960$19e55982@student.utwente.nl> From: "Theo van Klaveren" To: "Soren Schmidt" , "Koster, K.J." Cc: "FreeBSD Hackers" References: <200008100824.KAA13546@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks Date: Thu, 10 Aug 2000 11:29:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: | Ahem, maybe its time I chime in here. | Luigi and I once had an idea of having each track on a CD represented | by a device node, ie track0 = /dev/acd0t1 track1 = /dev/acd0t2 etc etc, | that way you could mount each track with whatever fs it supported. | This could be used to do what you want, and now where the ata driver | supports odd sector sizes, there is nothing hindering doing the | mount of an audio track (given the right mount_bla util that is). I stand corrected. I hadn't thought the ATA driver was so close to doing that already. Then again, I haven't extensively studied the ATA code yet. | The only problem is that we have to abuse the minor# etc to | get space for the 99 tracks a CD can hold, but that is not too bad... Tracks, as in audio tracks? You wouldn't want a device for each audio track, you want one device for _all_ audio tracks and one device per data track. Or am I misunderstanding you here? Theo van Klaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 2:37:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7176A37BA0D for ; Thu, 10 Aug 2000 02:37:20 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA30319; Thu, 10 Aug 2000 11:37:16 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008100937.LAA30319@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks In-Reply-To: <004701c002ad$77378960$19e55982@student.utwente.nl> from Theo van Klaveren at "Aug 10, 2000 11:29:21 am" To: t.vanklaveren@student.utwente.nl (Theo van Klaveren) Date: Thu, 10 Aug 2000 11:37:16 +0200 (CEST) Cc: K.J.Koster@kpn.com (Koster K.J.), freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Theo van Klaveren wrote: > | Ahem, maybe its time I chime in here. > | Luigi and I once had an idea of having each track on a CD represented > | by a device node, ie track0 = /dev/acd0t1 track1 = /dev/acd0t2 etc etc, > | that way you could mount each track with whatever fs it supported. > | This could be used to do what you want, and now where the ata driver > | supports odd sector sizes, there is nothing hindering doing the > | mount of an audio track (given the right mount_bla util that is). > > I stand corrected. I hadn't thought the ATA driver was so close to doing > that already. Then again, I haven't extensively studied the ATA code yet. :) > | The only problem is that we have to abuse the minor# etc to > | get space for the 99 tracks a CD can hold, but that is not too bad... > > Tracks, as in audio tracks? You wouldn't want a device for each audio track, > you want one device for _all_ audio tracks and one device per data track. Or > am I misunderstanding you here? Well, the idea is that you get one device pr CD track, that way you can do what you want with them, ie to rip audio track 4 you do: dd if=/dev/acdNt4 of=track4.raw bs=2352 To mount data track5 with an ISO filesys: mount -t cd9660 /dev/acdNt5 /cdrom If you want to collect all audio tracks together you would just use the normal /dev/acd0c device, read the TOC of the CD so you know where they are, set the right blocksize, and there you go (that works now BTW). -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 3:12: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ockle.dev.nanoteq.co.za (ockle.dev.nanoteq.co.za [196.7.114.28]) by hub.freebsd.org (Postfix) with ESMTP id AE86037B704 for ; Thu, 10 Aug 2000 03:11:32 -0700 (PDT) (envelope-from johan@ockle.dev.nanoteq.co.za) Received: (from johan@localhost) by ockle.dev.nanoteq.co.za (8.9.3/8.9.3) id MAA04715 for freebsd-hackers@FreeBSD.org; Thu, 10 Aug 2000 12:21:50 +0200 (SAST) (envelope-from johan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 10 Aug 2000 12:21:50 +0200 (SAST) Organization: Nanoteq From: Johan Kruger To: freebsd-hackers@FreeBSD.org Subject: Using libvgl in single user mode - HOW ? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote 2 small programs which i want to use for a customized CD installation The first is a loadable module and the other is a deamon which listens to sysctl's changes. The module creates dynamic coordinate/function variables which could be changed from the command line, perl script / sh whatever. e.g. You fill in x1,x2,... and a function e.g. 'Box' and then do sysctl -w jjk_vga.activate=1 It draws a box or whwatever function you need. . . . compat.linux.oss_version: 198144 jjk_vga.activate: 0 jjk_vga.x1: 10 jjk_vga.y1: 150 jjk_vga.x2: 200 jjk_vga.y2: 300 jjk_vga.xbegin: 0 jjk_vga.xstop: 100 jjk_vga.ybegin: 0 jjk_vga.ystop: 0 jjk_vga.g_init: 0 jjk_vga.g_stop: 0 jjk_vga.fgcolor: 1 jjk_vga.bgcolor: 0 jjk_vga.string: This is a test program jjk_vga.function: Box It works great, can now use perl to write a custom installation for my allready made custom installation CD. My problem is : When i boot from CD, i go into single user mode, to partition the disks and if you do a 'tty' you get /dev/console while in multi usermode if you do a 'tty' you get /dev/ttyv0 LIBVGL works on tty's and not on /dev/console, so my program does'nt want to initialize the graphics mode in single user mode. I looked in /usr/src/lib/libvgl/main.c and saw references to VT_whatever, MY question is , what must i replaced this references with, looked through cons.h, and console.h and so on, but i cant deem to find something. Could i instead make init use /dev/ttyv0 in single user mode ? - HOW If i boot FreeBSD PC ( not my CD ) in single usermode boot /kernel -s, and i do a /usr/libexec/getty and sh /etc/rc and login, my system seems in multiusermode BUT 'tty' then also report /dev/console and my prog does'nt work !!!!!!!!!!!!!!!!!! SO, it works in multiuser mode BUT not in single And that is because 'tty' = /dev/console in single user mode and 'tty' = /dev/ttyv0 in multi user mode HOW DO I FIX THIS - any suggestions ?? !!!!!!!!!!!!!!!! ---------------------------------- E-Mail: Johan Kruger Date: 10-Aug-00 Time: 12:19:14 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 3:15:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from studict.student.utwente.nl (studict.student.utwente.nl [130.89.220.2]) by hub.freebsd.org (Postfix) with ESMTP id 1555737BF18 for ; Thu, 10 Aug 2000 03:15:23 -0700 (PDT) (envelope-from t.vanklaveren@student.utwente.nl) Received: from phoenix (cal30b054.student.utwente.nl [130.89.229.25]) by studict.student.utwente.nl (8.8.6/MQT) with SMTP id MAA25986; Thu, 10 Aug 2000 12:14:09 +0200 (METDST) Message-ID: <000b01c002b3$c3cd7f40$19e55982@student.utwente.nl> From: "Theo van Klaveren" To: "Soren Schmidt" Cc: "Koster K.J." , "FreeBSD Hackers" References: <200008100937.LAA30319@freebsd.dk> Subject: Re: audiofs mixing audio and data tracks Date: Thu, 10 Aug 2000 12:14:26 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: | Well, the idea is that you get one device pr CD track, that way you can | do what you want with them, ie to rip audio track 4 you do: | | dd if=/dev/acdNt4 of=track4.raw bs=2352 | | To mount data track5 with an ISO filesys: | | mount -t cd9660 /dev/acdNt5 /cdrom | | If you want to collect all audio tracks together you would just | use the normal /dev/acd0c device, read the TOC of the CD so | you know where they are, set the right blocksize, and there | you go (that works now BTW). Ah, okay, that's great, but that's what audiofs already does (or will do with that function of yours), so I'll just go on hacking now :-) Theo van Klaveren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 4:34: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.44.236]) by hub.freebsd.org (Postfix) with ESMTP id 096C937BD1E for ; Thu, 10 Aug 2000 04:33:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id NAA14959 for ; Thu, 10 Aug 2000 13:33:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org Subject: mhn, sendmail & laptop at large... From: Poul-Henning Kamp Date: Thu, 10 Aug 2000 13:33:54 +0200 Message-ID: <14956.965907234@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The only way I can get sendmail to accept emails from nhm when my laptop is InterNet challenged is by applying this patch to sendmail.cf. nhm connects to sendmail on port 127.0.0.1:25 and sendmail complains that it cannot look stuff up in DNS. The way I see it, these two checks are reversed from the logical sequence, but when I tried to explain this to Eric he said my config was "wrong somehow". Can anybody tell me the right way to make this work ? Poul-Henning --- freebsd.cf Fri Aug 4 23:33:30 2000 +++ /etc/mail/sendmail.cf Thu Aug 10 10:40:14 2000 @@ -15,9 +15,9 @@ ##### ##### SENDMAIL CONFIGURATION FILE ##### -##### built by root@flutter.freebsd.dk on Fri Aug 4 23:33:30 CEST 2000 -##### in /freebsd/src/etc/sendmail -##### using /freebsd/src/etc/sendmail/../../contrib/sendmail/cf/ as configuration include directory +##### built by root@usw2.freebsd.org on Mon Jul 31 11:32:29 GMT 2000 +##### in /usr/src/etc/sendmail +##### using /usr/src/etc/sendmail/../../contrib/sendmail/cf/ as configuration include directory ##### ###################################################################### ###################################################################### @@ -1005,6 +1005,9 @@ R $* $@ RELAY R<$*> <$*> $: $2 +# anything originating locally is ok +R$* $: $&{client_name} + # allow relaying for hosts which we MX serve R$+ < @ $* > $: < : $(mxserved $2 $) : > $1 < @ $2 > R< : $* : > $* $#error $@ 4.7.1 $: "450 Can not check MX records for recipient host " $1 @@ -1018,8 +1021,6 @@ R $+ $@ OK R<$+> $* $: $2 -# anything originating locally is ok -R$* $: $&{client_name} # check if bracketed IP address (forward lookup != reverse lookup) R [$+] $: [$1] # pass to name server to make hostname canonical -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 4:34:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (samar.sasi.com.56.164.164.in-addr.arpa [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 899CA37BD3B; Thu, 10 Aug 2000 04:34:41 -0700 (PDT) (envelope-from gbnaidu@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id RAA18063; Thu, 10 Aug 2000 17:05:37 +0530 (IST) Received: from pcd75.sasi.com ([10.0.16.75]) by sasi.com; Thu, 10 Aug 2000 17:05:36 +0000 (IST) Received: from localhost (gbnaidu@localhost) by pcd75.sasi.com (8.9.3/8.9.3) with ESMTP id RAA01794; Thu, 10 Aug 2000 17:05:26 +0530 Date: Thu, 10 Aug 2000 17:05:26 +0530 (IST) From: "G.B.Naidu" To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org, gbnaidu@sasi.com Subject: Memory leakage... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been getting this error message on my FreeBSD 3.3 system: swap_pager: Out of Swap space. After digging a little bit, we found that there is a lot of memory leakage happening. This is how we went about finding: ps -aux for the process showed that vsz column was increasing very fast. But the rss column was almost stable( was not changing much). pstat -S also showed drastic fall in available swap space. My question is what could be the reason for this drastic increase in vsz column of ps -aux output? Is it because of unfreed malloced memory? Why rss is stable? Somebody could help me when will the vsz(virtual size) increases? thanks a lot --gb -- Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 4:45: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 89C4C37B81E for ; Thu, 10 Aug 2000 04:45:02 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 147639B2A; Thu, 10 Aug 2000 12:45:01 +0100 (BST) Date: Thu, 10 Aug 2000 12:45:01 +0100 From: Josef Karthauser To: Theo van Klaveren Cc: Soren Schmidt , "Koster K.J." , FreeBSD Hackers Subject: Re: audiofs mixing audio and data tracks Message-ID: <20000810124501.K1050@pavilion.net> Mail-Followup-To: Josef Karthauser , Theo van Klaveren , Soren Schmidt , "Koster K.J." , FreeBSD Hackers References: <200008100937.LAA30319@freebsd.dk> <000b01c002b3$c3cd7f40$19e55982@student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000b01c002b3$c3cd7f40$19e55982@student.utwente.nl>; from t.vanklaveren@student.utwente.nl on Thu, Aug 10, 2000 at 12:14:26PM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 12:14:26PM +0200, Theo van Klaveren wrote: > Soren Schmidt wrote: > > | Well, the idea is that you get one device pr CD track, that way you can > | do what you want with them, ie to rip audio track 4 you do: > | > | dd if=/dev/acdNt4 of=track4.raw bs=2352 > | > | To mount data track5 with an ISO filesys: > | > | mount -t cd9660 /dev/acdNt5 /cdrom > | > | If you want to collect all audio tracks together you would just > | use the normal /dev/acd0c device, read the TOC of the CD so > | you know where they are, set the right blocksize, and there > | you go (that works now BTW). > > Ah, okay, that's great, but that's what audiofs already does (or will do > with that function of yours), so I'll just go on hacking now :-) I'd got one step further. I'm working on some changes in cdcontrol to support cdid, which could enables us to get a directory name (the album name) and track names (the title of the tracks) for the file system. Of course this is only possible on a net connected machine, but would be cool :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 4:46:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id 80B2837B81E for ; Thu, 10 Aug 2000 04:46:03 -0700 (PDT) (envelope-from joe@pavilion.net) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 5EABB9B2B; Thu, 10 Aug 2000 12:46:02 +0100 (BST) Date: Thu, 10 Aug 2000 12:46:02 +0100 From: Josef Karthauser To: Soren Schmidt Cc: Tony Finch , "Koster K.J." , freebsd-hackers@FreeBSD.ORG Subject: Re: audiofs mixing audio and data tracks Message-ID: <20000810124602.L1050@pavilion.net> Mail-Followup-To: Josef Karthauser , Soren Schmidt , Tony Finch , "Koster K.J." , freebsd-hackers@FreeBSD.ORG References: <20000810090255.F468@hand.dotat.at> <200008100927.LAA28154@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008100927.LAA28154@freebsd.dk>; from sos@freebsd.dk on Thu, Aug 10, 2000 at 11:27:56AM +0200 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 11:27:56AM +0200, Soren Schmidt wrote: > It seems Tony Finch wrote: > > Soren Schmidt wrote: > > >It seems Koster, K.J. wrote: > > >> > > >> Am I right in thinking that a cdrom can have at most one data track? In that > > >> case, I'd suggest assighing that track a standard device node. That way I > > >> could just mount the data track of a cdrom, without worrying if that's track > > >> 4 or track 1. > > > > > >Mostly yes, but there is nothing hindering multiple data tracks on > > >the same CD. At any rate we only have access to one now anyways so > > >that wouldn't hurt anything :) > > > > How does this relate to multi-session CDs? Does that happen at a lower layer? > > Same thing, we always uses the last session written (which can > include parts from earlier written sessions), so the first track > on the last session will be the default track you get on /dev/acdN[ac] > just as it is now. Am I correct in thinking that the meta data in later sessions can point to data block in the earlier sessions? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 5: 2: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 779E737B63B; Thu, 10 Aug 2000 05:01:57 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 10 Aug 2000 13:01:54 +0100 (BST) Date: Thu, 10 Aug 2000 13:01:54 +0100 From: David Malone To: "G.B.Naidu" Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Memory leakage... Message-ID: <20000810130154.A1196@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gbnaidu@sasi.com on Thu, Aug 10, 2000 at 05:05:26PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 05:05:26PM +0530, G.B.Naidu wrote: > My question is what could be the reason for this drastic increase in vsz > column of ps -aux output? Is it because of unfreed malloced memory? Why > rss is stable? Somebody could help me when will the vsz(virtual > size) increases? Sounds like you're allocating memory and not freeing it. Once the your program is finished with the memory and then allocates more the unused memory will be swapped out, and so not contribute to the residant size. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 5:46:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id D9A3937B9C1; Thu, 10 Aug 2000 05:46:51 -0700 (PDT) (envelope-from langd@informatik.tu-muenchen.de) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: NO-IDENT-SERVICE [port 2071]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <112002-226>; Thu, 10 Aug 2000 14:46:45 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 2BFD31362C; Thu, 10 Aug 2000 14:46:31 +0200 (CEST) From: Daniel Lang To: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Bootstrapping ? (was Re: Installation Problems on Dell PowerEdge 6100/200 ) Message-ID: <20000810144631.D18204@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Date: Thu, 10 Aug 2000 14:46:31 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, its nice to hear that, 4.1 will support the 2450 server, but unfortunately it doesn't really help with my problem. (Message-ID: <20000808144202.A14579@atrbg11.informatik.tu-muenchen.de>) Maybe s.b. more familiar with the bootstrapping process could give some hints, where to dig for a solution. Many thanks, Daniel -- IRCnet: Mr-Spock - Cool people don't move, they just hang around. - Daniel Lang * dl@leo.org * ++49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 6: 3:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from black.nik.gov.pl (black.nik.gov.pl [212.160.156.114]) by hub.freebsd.org (Postfix) with ESMTP id 2147137B9AF for ; Thu, 10 Aug 2000 06:02:57 -0700 (PDT) (envelope-from Damian_Kuczynski@nik.gov.pl) Received: from green.nik.gov.pl (green.nik.gov.pl [172.20.11.4]) by black.nik.gov.pl (8.9.3+Sun/8.9.3) with ESMTP id PAA07204 for ; Thu, 10 Aug 2000 15:06:18 +0200 (MET DST) Message-ID: <3992A8C7.1B5CC765@nik.gov.pl> Date: Thu, 10 Aug 2000 15:06:15 +0200 From: Damian Kuczynski Reply-To: Damian_Kuczynski@nik.gov.pl Organization: NIK X-Mailer: Mozilla 4.73 [pl] (X11; I; FreeBSD 3.5-STABLE i386) X-Accept-Language: pl, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: quotas and file creditentials Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello When I tried to analizee problem with mail.local writing messages to user mailmox over quota limit I saw, that once root open a file which belongs to nonprivileged user ex. test1, and after that drops his privlegees to this user then user test1 is able to write to this file as many data an he want and qverquota his disk limits mail.local works in this maneer so it is able to overquota user mailbox. Is this normal, or maybe file should be writen under permissions effective user (euid=test1) Best regards Damian Kuczynski To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 6:32:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-5-187.zoominternet.net [24.154.5.187]) by hub.freebsd.org (Postfix) with ESMTP id 61DAD37BDEF for ; Thu, 10 Aug 2000 06:32:38 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from localhost (localhost [127.0.0.1]) by topperwein.dyndns.org (8.9.3/8.9.3) with ESMTP id JAA18490 for ; Thu, 10 Aug 2000 09:34:03 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Thu, 10 Aug 2000 09:34:03 -0400 (EDT) From: Chris BeHanna Reply-To: behanna@zbzoom.net To: freebsd-hackers@freebsd.org Subject: Re: An sblock magic number is... In-Reply-To: <20000810004633.A74732@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Aug 2000, Ollivier Robert wrote: > According to Wilko Bulte: > > Guessing: superblock? > > Yes. > > Our dump is only able to backup complete filesystems. Historically, SunOS' one > is able to backup partial FS (i.e. directories) and ironically, when Rémy Card > (of ext2fs fame) ported it to Linux, he added back that functionality. Short of that, this should work, shouldn't it? ssh user@host tar cvf - | gzip -c > myarchive.tgz If not, then pipe it to dd first, then gzip it. -- Chris BeHanna Software Engineer (at yourfit.com) behanna@zbzoom.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 6:38:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id DF5C037B9BB for ; Thu, 10 Aug 2000 06:38:32 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA23083; Thu, 10 Aug 2000 09:38:06 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 10 Aug 2000 09:38:06 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Theo van Klaveren Cc: freebsd-hackers@freebsd.org Subject: Re: In-kernel ioctl calls In-Reply-To: <001e01c0020c$d257b3c0$19e55982@student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Theo van Klaveren wrote: > The first statement issues the read command to the device, I presume. It > copies the data to an internal (kernel-space) buffer. Next, the internal > buffer is copyout()ed to ubuf (which is my ioctl buffer), which fails > because in the case of AudioFS it's in kernel space. I've actually run into this problem in a number of places -- specifically, aio support. I needed to generate aio requests in kernel, and the calls were intended to be instantiated only from userland. The linux emulation code presumably also jumps through hoops to deal with calls that require data coming from userland. This has, I think, a lot to do with the design of the syscall and implementation of the syscalls. As mentioned in another forum a few weeks ago, it also makes authorization hard, as it happens in many places. I'd really rather see the calling of syscalls broken out into "service" and "abi" layers, where the "service" layer implements the service, and uses struct uio for all argument reads/writes, and the ABI layer is responsible for setting all that up, but not much else. This would allow then ABI layers such as FreeBSD, BSD/OS, Linux, to contain minimal service implementation, moving all implementation into the service layer, which would not have to be aware of much in terms of whether arguments came from {user,sys}space, locking semantics, or authorization. Now, this is somewhat far from the current implementation, but I think is a worthwhile goal. For ioctls, which are down a few layers in the implementation, maybe we need to start passing down an explicit "this call is kernel or user initiated". There are already situations in, for example, the quota and extattr code, where a NULL struct cred indicates "authorize as kernel", which is a somewhat similar issue. Maybe we need a USERSPACE/SYSSPACE argument in kernel to calls that may or may not do their own copyin/copyout. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 7:49:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web2.sea.nwserv.com (web2.sea.nwserv.com [216.145.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 6024437BE90 for ; Thu, 10 Aug 2000 07:49:31 -0700 (PDT) (envelope-from dpk@nwserv.com) Received: from localhost (dpk@localhost) by web2.sea.nwserv.com (8.9.3/8.9.2) with ESMTP id HAA37926 for ; Thu, 10 Aug 2000 07:49:27 -0700 (PDT) (envelope-from dpk@nwserv.com) Date: Thu, 10 Aug 2000 07:49:27 -0700 (PDT) From: David Kirchner X-Sender: dpk@web2.sea.nwserv.com To: freebsd-hackers@freebsd.org Subject: quotacheck on a live filesystem; safe? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Envelope-To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've searched the archives and I've seen this question asked a few other times, but I did not see any response. Does anyone know the answer? ---------- Forwarded message ---------- Date: Wed, 9 Aug 2000 14:15:17 -0700 (PDT) From: David Kirchner To: freebsd-questions@FreeBSD.ORG Subject: quotacheck on a live filesystem; safe? Hi, I've been reading over source for quotacheck and ufs_quota.c and so far I have not found a reason why running quotacheck on a live filesystem would cause anything but inconsistencies in the quota.user file. Is this an incorrect belief? >From what I understand: the quota.user file is used as a storage for quota information between boots and by the various userland quota reporting utilities. The kernel maintains an idea of the quota in memory, and commits it to disk when necessary. If this is correct, then I could expect, at worst, someone's quota to be invalid if the machine crashes while quotacheck is running and their files are being modified? Thanks, David Kirchner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 9:29:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3C01A37B757 for ; Thu, 10 Aug 2000 09:29:36 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA14223; Thu, 10 Aug 2000 10:29:34 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA08822; Thu, 10 Aug 2000 10:29:08 -0600 (MDT) (envelope-from nate) Date: Thu, 10 Aug 2000 10:29:08 -0600 (MDT) Message-Id: <200008101629.KAA08822@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: hackers@FreeBSD.ORG, archie@whistle.com Subject: Re: CVS question In-Reply-To: <200008091554.IAA53597@vashon.polstra.com> References: <200008071906.MAA12811@bubba.whistle.com> <200008091554.IAA53597@vashon.polstra.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ CVS has screwy behavior ] > CVS has a heuristic that does the wrong thing for this particular > file. [ Code and discussion deleted ] > I hope current > versions of CVS force the dates to be the same on an import. I > haven't checked to see whether that's the case or not. Suggestions like this would be good to send to the new CVS maintainers. Checkout www.cvshome.org, and send in a bug report, if you would please. You probably know CVS bugs better than many of the maintainers. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 10:35:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.rdc1.sfba.home.com (mail2.rdc1.sfba.home.com [24.0.0.75]) by hub.freebsd.org (Postfix) with ESMTP id E34FE37B8B6; Thu, 10 Aug 2000 10:35:22 -0700 (PDT) (envelope-from boshea@ricochet.net) Received: from beastie.localdomain ([24.19.158.41]) by mail2.rdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000810173522.RTEH6679.mail2.rdc1.sfba.home.com@beastie.localdomain>; Thu, 10 Aug 2000 10:35:22 -0700 Received: (from brian@localhost) by beastie.localdomain (8.9.3/8.8.7) id KAA01658; Thu, 10 Aug 2000 10:35:52 -0700 (PDT) (envelope-from brian) Date: Thu, 10 Aug 2000 10:35:52 -0700 From: "Brian O'Shea" To: "G.B.Naidu" Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Memory leakage... Message-ID: <20000810103552.O351@beastie.localdomain> Reply-To: boshea@ricochet.net Mail-Followup-To: "G.B.Naidu" , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from G.B.Naidu on Thu, Aug 10, 2000 at 05:05:26PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 05:05:26PM +0530, G.B.Naidu wrote: > > Hi, > > I have been getting this error message on my FreeBSD 3.3 system: > > swap_pager: Out of Swap space. After digging a little bit, we found that > there is a lot of memory leakage happening. This is how we went about > finding: > > ps -aux for the process showed that vsz column was increasing very > fast. But the rss column was almost stable( was not changing much). For what process? (what program was running that had such a large vsz?) > > pstat -S also showed drastic fall in available swap space. > > My question is what could be the reason for this drastic increase in vsz > column of ps -aux output? Is it because of unfreed malloced memory? Why > rss is stable? Somebody could help me when will the vsz(virtual > size) increases? Yes, it is because of unfreed malloc()'ed memory. If it is a memory leak, the only way to free the memory is to kill the process that is leaking it. > -- > Never trust an operating system you don't have sources for. ;-) Don't get too comfortable. ;) -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 10:58:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9C5D237B58F for ; Thu, 10 Aug 2000 10:58:17 -0700 (PDT) (envelope-from larse@ISI.EDU) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id KAA23913 for ; Thu, 10 Aug 2000 10:58:12 -0700 (PDT) Message-ID: <3992ED33.7AD785CB@isi.edu> Date: Thu, 10 Aug 2000 10:58:11 -0700 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: hackers@freebsd.org Subject: measuring bus utilization Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quick question: Is there a way to measure PCI bus utilization using the P6 performance monitoring capabilities? Specifically, is BUS_DRDY_CLOCKS/ticks a a meaningful figure? Thanks, Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 11:53:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 5191A37B96B; Thu, 10 Aug 2000 11:53:19 -0700 (PDT) (envelope-from frederik@freddym.org) Received: from server.wes.mee.com (p3E9C035B.dip.t-dialin.net [62.156.3.91]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id UAA06447; Thu, 10 Aug 2000 20:53:16 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id UAA02090; Thu, 10 Aug 2000 20:31:59 +0200 (CEST) Date: Thu, 10 Aug 2000 20:31:59 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: Nick Sayer Cc: freebsd-hackers@freebsd.org, cg@freebsd.org Subject: Re: Solo-1 appears to work (was Re: US$100 prize for adding ESS Audiodrive support to pcm) In-Reply-To: <39910780.A0B7567B@quack.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Can anyone (or is it already) include this driver to the latest -current source tree?! Thanks -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13: 1:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 421E837BAD8 for ; Thu, 10 Aug 2000 13:01:34 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id EF0191925E for ; Thu, 10 Aug 2000 15:01:31 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id PAA79370 for hackers@freebsd.org; Thu, 10 Aug 2000 15:01:31 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Thu, 10 Aug 2000 15:01:31 -0500 From: "Jacques A. Vidrine" To: hackers@freebsd.org Subject: What exactly does this mean? (ld: size of symbol changed) Message-ID: <20000810150131.A79323@hamlet.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hope someone might be able to clue me in. I'm having a hard time tracking this down. I've added some code to libc, and while building the world I get this misery in src/sbin/dhclient: cc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"' -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o ethernet.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o /usr/lib/libc.a(err.o): In function `warn': err.o(.text+0x1e0): multiple definition of `warn' errwarn.o(.text+0xd8): first defined here /usr/libexec/elf/ld: Warning: size of symbol `warn' changed from 141 to 30 in err.o *** Error code 1 I guess I just don't understand exactly what the linker is trying to tell me. BTW, this is ~ 4.1-RELEASE. Thanks, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13: 8:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 8BF0B37BA85 for ; Thu, 10 Aug 2000 13:08:23 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA28582 for ; Thu, 10 Aug 2000 16:08:21 -0400 (EDT) Date: Thu, 10 Aug 2000 16:05:27 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: recompiling boot blocks & serial console Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want to set up a serial console on a freebsd 4.1 box. I follow the instructions at http://www.mostgraveconcern.com/freebsd/. I tried to do the following: # cd /sys/boot/i386/boo2 # make clean # make I got "cannot open ../btx/lib/crt0.o". What happened? Besides, I want to use another freebsd box as console. Can I use kermit as the terminal program? If so, can I configure it as for normal login purpose? Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13:11:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 50A4A37BC63 for ; Thu, 10 Aug 2000 13:11:31 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA00734; Thu, 10 Aug 2000 13:23:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008102023.NAA00734@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: recompiling boot blocks & serial console In-reply-to: Your message of "Thu, 10 Aug 2000 16:05:27 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Aug 2000 13:23:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I want to set up a serial console on a freebsd 4.1 box. I follow the > instructions at http://www.mostgraveconcern.com/freebsd/. I tried to do > the following: Put -h in /boot.config. Now you have a serial console. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13:12:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 39B8637BC2C for ; Thu, 10 Aug 2000 13:12:33 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id QAA19685; Thu, 10 Aug 2000 16:12:23 -0400 (EDT) (envelope-from jim@thehousleys.net) Message-ID: <39930CA7.3D672027@thehousleys.net> Date: Thu, 10 Aug 2000 16:12:23 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jacques A. Vidrine" Cc: hackers@FreeBSD.ORG Subject: Re: What exactly does this mean? (ld: size of symbol changed) References: <20000810150131.A79323@hamlet.nectar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jacques A. Vidrine" wrote: > > I hope someone might be able to clue me in. I'm having a hard time tracking > this down. I've added some code to libc, and while building the world I get > this misery in src/sbin/dhclient: > > cc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -DCLIENT_PATH='"PATH=/sbin:/bin:/usr/sbin:/usr/bin"' -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o ethernet.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o > /usr/lib/libc.a(err.o): In function `warn': > err.o(.text+0x1e0): multiple definition of `warn' > errwarn.o(.text+0xd8): first defined here > /usr/libexec/elf/ld: Warning: size of symbol `warn' changed from 141 to 30 in err.o > *** Error code 1 > My guess is that you (or someone) have redefined the function warn(). errwarn.c is dhclient. Are you compiling dhclient from /usr/src/contrib/isc-dhcp instead of /usr/src/sbin/dhclient? The second is the correct locaion. Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13:18:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 0615A37BABD for ; Thu, 10 Aug 2000 13:18:38 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 35D721925E; Thu, 10 Aug 2000 15:18:35 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id PAA79447; Thu, 10 Aug 2000 15:18:35 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Thu, 10 Aug 2000 15:18:35 -0500 From: "Jacques A. Vidrine" To: James Housley Cc: hackers@FreeBSD.ORG Subject: Re: What exactly does this mean? (ld: size of symbol changed) Message-ID: <20000810151835.A79419@hamlet.nectar.com> References: <20000810150131.A79323@hamlet.nectar.com> <39930CA7.3D672027@thehousleys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39930CA7.3D672027@thehousleys.net>; from jim@thehousleys.net on Thu, Aug 10, 2000 at 04:12:23PM -0400 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 10, 2000 at 04:12:23PM -0400, James Housley wrote: > My guess is that you (or someone) have redefined the function warn(). Good guess, but no cigar :-) warn is defined once in libc, and once in errwarn.c. This is OK normally, but I've screwed up something in the build. > errwarn.c is dhclient. Are you compiling dhclient from > /usr/src/contrib/isc-dhcp instead of /usr/src/sbin/dhclient? The second > is the correct locaion. src/sbin/dhclient as I mentioned in my first message. Could `CFLAGS+= -I${.OBJDIR}' in src/lib/libc/net/Makefile.inc cause me to lose in this fashion? If so, how else might I get to a generated file (i.e. header output from yacc)? Thanks, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13:23:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 3C2BC37BABD for ; Thu, 10 Aug 2000 13:23:13 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id NAA71643; Thu, 10 Aug 2000 13:21:58 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008102021.NAA71643@bubba.whistle.com> Subject: Re: CVS question In-Reply-To: <200008101629.KAA08822@nomad.yogotech.com> from Nate Williams at "Aug 10, 2000 10:29:08 am" To: Nate Williams Date: Thu, 10 Aug 2000 13:21:58 -0700 (PDT) Cc: John Polstra , hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > > I hope current > > versions of CVS force the dates to be the same on an import. I > > haven't checked to see whether that's the case or not. > > Suggestions like this would be good to send to the new CVS maintainers. > Checkout www.cvshome.org, and send in a bug report, if you would > please. You probably know CVS bugs better than many of the > maintainers.:) Done. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 13:42:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id C624437C105; Thu, 10 Aug 2000 13:42:26 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA12342; Thu, 10 Aug 2000 16:42:24 -0400 (EDT) Date: Thu, 10 Aug 2000 16:39:29 -0400 (EDT) From: Zhihui Zhang To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: recompiling boot blocks & serial console In-Reply-To: <200008102023.NAA00734@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Aug 2000, Mike Smith wrote: > > > > I want to set up a serial console on a freebsd 4.1 box. I follow the > > instructions at http://www.mostgraveconcern.com/freebsd/. I tried to do > > the following: > > Put > > -h > > in /boot.config. Now you have a serial console. Yes! Two more quick questions: how to change baud rate? Can kermit capture the output? (I use kermit on the other FreeBSD machine). -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 14:18:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 8329637B616 for ; Thu, 10 Aug 2000 14:18:40 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA01509; Thu, 10 Aug 2000 14:30:29 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008102130.OAA01509@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: recompiling boot blocks & serial console In-reply-to: Your message of "Thu, 10 Aug 2000 16:39:29 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Aug 2000 14:30:29 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 10 Aug 2000, Mike Smith wrote: > > > > > > > I want to set up a serial console on a freebsd 4.1 box. I follow the > > > instructions at http://www.mostgraveconcern.com/freebsd/. I tried to do > > > the following: > > > > Put > > > > -h > > > > in /boot.config. Now you have a serial console. > > Yes! Two more quick questions: how to change baud rate? Can kermit > capture the output? (I use kermit on the other FreeBSD machine). You need to recompile the bootblocks to change the baudrate; set BOOT_COMCONSOLE_SPEED in /etc/make.conf, then do: # cd /sys/boot # make clean cleandepend # make depend && make && make install # disklabel -B -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 14:41:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 2879837BA2B; Thu, 10 Aug 2000 14:41:12 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id RAA24893; Thu, 10 Aug 2000 17:41:08 -0400 (EDT) Date: Thu, 10 Aug 2000 17:38:16 -0400 (EDT) From: Zhihui Zhang To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: recompiling boot blocks & serial console In-Reply-To: <200008102130.OAA01509@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Aug 2000, Mike Smith wrote: > > On Thu, 10 Aug 2000, Mike Smith wrote: > > > > > > > > > > I want to set up a serial console on a freebsd 4.1 box. I follow the > > > > instructions at http://www.mostgraveconcern.com/freebsd/. I tried to do > > > > the following: > > > > > > Put > > > > > > -h > > > > > > in /boot.config. Now you have a serial console. > > > > Yes! Two more quick questions: how to change baud rate? Can kermit > > capture the output? (I use kermit on the other FreeBSD machine). > > You need to recompile the bootblocks to change the baudrate; set > BOOT_COMCONSOLE_SPEED in /etc/make.conf, then do: > > # cd /sys/boot > # make clean cleandepend > # make depend && make && make install > # disklabel -B > Done! I use Windows 98 HyperTerminal right now because I do not know which Unix terminal program can capture its output into a file. Thanks! BTW, the web page should tell readers to do "make cleandepend" and "make depend". -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 16:15: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 535C537BB31; Thu, 10 Aug 2000 16:14:57 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA44891; Fri, 11 Aug 2000 00:10:41 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA28283; Fri, 11 Aug 2000 00:10:38 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008102310.AAA28283@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Robert Watson Cc: Isaac Waldron , freebsd-hackers@FreeBSD.org, freebsd-arch@FreeBSD.org, brian@Awfulhak.org Subject: Re: Writing device drivers (ioctl issue) In-Reply-To: Message from Robert Watson of "Thu, 27 Jul 2000 16:13:08 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Aug 2000 00:10:38 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I ran into this same problem when modifying the vmmon VMWare driver for > FreeBSD to support mulitple emulator instances. FreeBSD's VFS does not > have a concept of stateful file access: there are open's and close's, but > the VOP_READ/WRITE operations are not associated with sessions. This [.....] > There are a number of possible solutions to this problem, including the [.....] > My preferred solution, and I actually hacked around with a kernel a bit to > do this, is to make the VFS provide (optional) stateful vnode sessions. > vop_open() would gain an additional call-by-reference argument, probably a > void**. When NULL, the caller would be requesting a stateless vnode open, [.....] > My changes are incomplete as I was working on it on the plane, and > comments on the idea would be welcome. One thing this would allow is for [.....] I think this is something that BSD lacks big-time. It simplifies the way userland opens devices and should be fairly easy to implement. If you haven't got time, I'd be willing to pick this up. Do you have anything worth sending me (patches) ? Cheers. > Robert N M Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 16:52:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id BA05F37BB36 for ; Thu, 10 Aug 2000 16:52:16 -0700 (PDT) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id IAA11817; Fri, 11 Aug 2000 08:51:45 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma011608; Fri, 11 Aug 00 08:51:32 +0900 Received: from jkpc15.tk.kubota.co.jp ([192.168.7.250]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id IAA08491; Fri, 11 Aug 2000 08:51:30 +0900 (JST) Received: from localhost (localhost.ttr.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-02/21/99) with ESMTP id IAA00818; Fri, 11 Aug 2000 08:48:27 +0900 (JST) To: joseph.scott@owp.csus.edu, taku@cent.saitama-u.ac.jp Cc: julian@elischer.org, abc@bsdi.com, abial@webgiro.com, gandalf@vilnya.demon.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Maestro2E patch (Was: US$100 prize for adding ESS Audiodrive support to pcm) In-Reply-To: <39902AC7.CB39BCD8@owp.csus.edu> References: <20000805155806.A94702@diskfarm.firehouse.net> <398F3081.167EB0E7@elischer.org> <39902AC7.CB39BCD8@owp.csus.edu> X-Mailer: Mew version 1.94.1 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Aug_11_08:47:09_2000_809)--" Content-Transfer-Encoding: 7bit Message-Id: <20000811084827Y.haro@tk.kubota.co.jp> Date: Fri, 11 Aug 2000 08:48:27 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 209 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Fri_Aug_11_08:47:09_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, From: Joseph Scott Date: Tue, 08 Aug 2000 08:44:08 -0700 ::> > > On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly ::> [...] ::> > Add $100 from me. There is one that works for some folks out there ::> > by , but it does not work for me. ::> ::> where do you find this? :: :: I'm not sure about Alan, but I got it from an email from Taku ::YAMAMOTO . I've included the email below. ::One thing to note, myself and a few others have only been able to get ::sound to work out of the audio out jack. For some reason the internal ::speakers just don't work. I've played with the settings on the ::notebook quite a bit, and they do still work when I boot into ::Windows. However, sound, even without the internal speakers, is ::better than no sound at all :-) I have created a patch that trys to enable internal speakers. It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works for everybody. Patch is based on Linux driver, but simplified. If it does not work, 1) try setting GPIO values to what your PC is at when rebooting from Windows, 2) try original way the Linux driver do. Let me know, if you want to know what Linux driver does. The patch is based on Taku YAMAMOTO's maestro driver found at: http://access.cent.saitama-u.ac.jp/~taku/freebsd/maestro/releng4-20000725.tar.gz FYI, I also was writing Maestro2E driver myself, but I stopped. Because YAMAMOTO-san's driver works better than mine. :-) Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp ----Next_Part(Fri_Aug_11_08:47:09_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mstr2_spr.patch" --- maestro.c.org Fri Aug 11 08:23:46 2000 +++ maestro.c Fri Aug 11 08:27:06 2000 @@ -50,6 +50,9 @@ #define MAESTRO_2_PCI_ID 0x1968125d #define MAESTRO_2E_PCI_ID 0x1978125d +#define NEC_SUBID1 0x80581033 /* Taken from Linux driver */ +#define NEC_SUBID2 0x803c1033 /* NEC VersaProNX VA26D */ + #define AGG_MAXPLAYCH 4 #define AGG_BUFSIZ (8 << 10) @@ -87,6 +90,8 @@ unsigned playchns, active; struct agg_chinfo pch[AGG_MAXPLAYCH]; struct agg_chinfo rch; + + u_int32_t subid; }; @@ -95,8 +100,8 @@ static void set_timer(struct agg_info*); -static u_int32_t agg_rdcodec(struct agg_info*, int); -static void agg_wrcodec(struct agg_info*, int, u_int32_t); +static u_int32_t agg_rdcodec(void *, int); +static void agg_wrcodec(void *, int, u_int32_t); static inline void ringbus_setdest(struct agg_info*, int, int); @@ -117,9 +122,9 @@ static void agg_init(struct agg_info*); static void agg_deinit(struct agg_info*); -static u_int32_t agg_ac97_init(struct agg_info*); +static u_int32_t agg_ac97_init(void *); -static void agg_intr(struct agg_info*); +static void agg_intr(void *); static pcmchan_init_t aggch_init; static pcmchan_setdir_t aggch_setdir; static pcmchan_setformat_t aggch_setplayformat; @@ -143,8 +148,9 @@ /* Codec/Ringbus */ static u_int32_t -agg_rdcodec(struct agg_info *ess, int regno) +agg_rdcodec(void *s, int regno) { + struct agg_info *ess = (struct agg_info *)s; unsigned t; /* We have to wait for a SAFE time to write addr/data */ @@ -178,8 +184,9 @@ } static void -agg_wrcodec(struct agg_info *ess, int regno, u_int32_t data) +agg_wrcodec(void *s, int regno, u_int32_t data) { + struct agg_info *ess = (struct agg_info *)s; unsigned t; /* We have to wait for a SAFE time to write addr/data */ @@ -351,6 +358,32 @@ | WAVCACHE_WAVETABLE_SIZE_2MB); wp_wrreg(ess, WPREG_BASE, 0x8500); wp_wrreg(ess, WPREG_TIMER_ENABLE, 1); + + /* + * Setup GPIO. + * There seems to be speciality with NEC systems. + */ + switch (ess->subid) { + case NEC_SUBID1: + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, 0x09ff); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DIR)| 0x600); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, 0x0209); + break; + case NEC_SUBID2: + /* For VersaProNX VA26D */ + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, 0x09e4); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, 0x061b); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, 0x03ef); + break; + default: + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_MASK) & 0xfffe); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DIR) | 0x11); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DATA) | 0x01); + } } static void @@ -371,8 +404,9 @@ } static u_int32_t -agg_ac97_init(struct agg_info *ess) +agg_ac97_init(void *s) { + struct agg_info *ess = (struct agg_info *)s; u_int32_t data; data = bus_space_read_4(ess->st, ess->sh, PORT_RINGBUS_CTRL); @@ -391,8 +425,9 @@ } static void -agg_intr(struct agg_info* ess) +agg_intr(void *s) { + struct agg_info *ess = (struct agg_info *)s; u_int16_t status; int i; @@ -745,7 +780,7 @@ struct agg_info *ess = NULL; u_int32_t data; int mapped = 0; - int regid = PCI_MAP_REG_START; + int regid = PCIR_MAPS; struct resource *reg = NULL; struct ac97_info *codec = NULL; int irqid = 0; @@ -793,6 +828,8 @@ device_printf(dev, "unable to map register space\n"); goto bad; } + + ess->subid = pci_read_config(dev, PCIR_SUBVEND_0, 4); agg_init(ess); codec = ac97_create(dev, ess, agg_ac97_init, agg_rdcodec, agg_wrcodec); --- maestro_reg.h.org Fri Aug 11 08:23:58 2000 +++ maestro_reg.h Fri Aug 11 08:23:15 2000 @@ -144,6 +144,11 @@ #define RINGBUS_DEST_DSOUND_IN 4 #define RINGBUS_DEST_ASSP_IN 5 +/* GPIO control */ +#define PORT_GPIO_DATA 0x60 /* WORD RW */ +#define PORT_GPIO_MASK 0x64 /* WORD RW */ +#define PORT_GPIO_DIR 0x68 /* WORD RW */ + /* ----------------------------- * Wave Processor Indexed Data Registers. ----Next_Part(Fri_Aug_11_08:47:09_2000_809)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 17:42:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id B6A6F37B93A for ; Thu, 10 Aug 2000 17:42:08 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id RAA09567; Thu, 10 Aug 2000 17:40:12 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <39934AA4.5722D1C5@owp.csus.edu> Date: Thu, 10 Aug 2000 17:36:52 -0700 From: Joseph Scott X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Munehiro Matsuda Cc: taku@cent.saitama-u.ac.jp, julian@elischer.org, abc@bsdi.com, abial@webgiro.com, gandalf@vilnya.demon.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Maestro2E patch (Was: US$100 prize for adding ESS Audiodrivesupport to pcm) References: <20000805155806.A94702@diskfarm.firehouse.net> <398F3081.167EB0E7@elischer.org> <39902AC7.CB39BCD8@owp.csus.edu> <20000811084827Y.haro@tk.kubota.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Munehiro Matsuda wrote: > > Hi all, > > From: Joseph Scott > Date: Tue, 08 Aug 2000 08:44:08 -0700 > ::> > > On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly > ::> [...] > ::> > Add $100 from me. There is one that works for some folks out there > ::> > by , but it does not work for me. > ::> > ::> where do you find this? > :: > :: I'm not sure about Alan, but I got it from an email from Taku > ::YAMAMOTO . I've included the email below. > ::One thing to note, myself and a few others have only been able to get > ::sound to work out of the audio out jack. For some reason the internal > ::speakers just don't work. I've played with the settings on the > ::notebook quite a bit, and they do still work when I boot into > ::Windows. However, sound, even without the internal speakers, is > ::better than no sound at all :-) > > I have created a patch that trys to enable internal speakers. The first part of the patch (for maestro.c) didn't apply cleanly for me, so I ended up doing it by hand. > > It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works > for everybody. Patch is based on Linux driver, but simplified. > > If it does not work, 1) try setting GPIO values to what your PC is at > when rebooting from Windows, 2) try original way the Linux driver do. > Let me know, if you want to know what Linux driver does. Unfortunately this didn't work for mine (Dell Inspiron 7500). How to I find out the GPIO values that make windows work? I'm open to trying what the Linux driver does. Mind you my C programing skills are pretty much useless, but I'm willing to try things out :-) Thanks again to the people working on this, it's nice to have sound working. > > The patch is based on Taku YAMAMOTO's maestro driver found at: > http://access.cent.saitama-u.ac.jp/~taku/freebsd/maestro/releng4-20000725.tar.gz > > FYI, I also was writing Maestro2E driver myself, but I stopped. > Because YAMAMOTO-san's driver works better than mine. :-) > > Thank you, > Haro -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 17:49:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id 9629937BB99 for ; Thu, 10 Aug 2000 17:49:51 -0700 (PDT) (envelope-from owensmk@earthlink.net) Received: from earthlink.net (sdn-ar-002txfworP026.dialsprint.net [168.191.159.138]) by hawk.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id RAA23715 for ; Thu, 10 Aug 2000 17:49:49 -0700 (PDT) Message-ID: <39934E64.A5BEE8EE@earthlink.net> Date: Thu, 10 Aug 2000 19:52:52 -0500 From: Michael Owens X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: R. Stevens select() Collisions Scenario Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Purpose: I am trying to write a non-blocking, preforked server, specifically to run on FreeBSD, and have a general question as to whether or not my strategy is sound. Problem: In Unix Network Programming Vol. 1 (section 27.6, p.741), Stevens mentions a scenario under a preforked server design where multiple children are calling select() on the same descriptor, causing collisions for the kernel to resolve. The children would look something like... . . . for( ; ; ){ FD_SET(listfd,&rset); Select(listfd+1,&rset,NULL,NULL,NULL); if(FD_ISSET(listfd,&rset)==0) err_quit("listenfd readable"); clilen = addrlen; connfd = Accept(listenfd, cliaddr, &clilen); process(connfd); Close(connfd); } . . . Hypothesis: If you were implement the server such that the children used non-blocking I/O, so that select() returned immediately, would this alleviate the problem of collisions in the kernel and its associated overhead? If so, would you then have to worry about mutual exclusion when select did return a ready descriptor for accept(). For example, a child gets switched just after calling select() but just before it makes it to accept(). Thus, the next child would also receive the same descriptor ready for accept()? Now only one of the two children will get to accept() first, leaving the other blocking on accept(). Stevens mentions a similar case at the end of the Nonblocking I/O chapter (section 15.6, p. 422) and to avoid this he recommends 1) setting the listening descriptor to non-blocking and 2) ignoring EWOULDBLOCK, ECONNABORTED, etc. on accept(). So, if you make the listening descriptor non-blocking, and treat select() and accept() appropriately, you should be alright in both avoiding select collisions and there overhead, as well as avoid children blocking due to losing possible race conditions for the listen descriptor in the event (albiet small) of a context switch between select() and accept(). Apology: The reason I bother you with all this is that while I (think I) understand the logic, I (know I) am at the limits of my understanding, and might be missing some important considerations as to other goings on in the kernel, and that there might be a better way to go about all this. Summary: Ultimately, all I am seeking to do is have an efficient and scalable server design, and to my knowledge, this would consist of a number of preforked children who are non-blocking/multiplexing themselves. Furthermore, each child will have a pool of worker threads which will handle jobs sent by different clients. As long as the threads' work doesn't entail an operation that blocks for appreciable amount of time (so that a single thread puts the whole child to sleep), it would seem like this might be a decent proposal: multiple clients and multiple jobs being handled simultaneously by each child, and the number of children can be controlled by the parent according to the load and limits of the hardware. Does this seem like a good way to go about it? Thanks: Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 18: 8:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 90CD437BBA8 for ; Thu, 10 Aug 2000 18:08:40 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7B18ck01677; Thu, 10 Aug 2000 18:08:38 -0700 (PDT) Date: Thu, 10 Aug 2000 18:08:38 -0700 From: Alfred Perlstein To: Michael Owens Cc: hackers@FreeBSD.ORG Subject: Re: R. Stevens select() Collisions Scenario Message-ID: <20000810180838.V4854@fw.wintelcom.net> References: <39934E64.A5BEE8EE@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39934E64.A5BEE8EE@earthlink.net>; from owensmk@earthlink.net on Thu, Aug 10, 2000 at 07:52:52PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael Owens [000810 17:51] wrote: > Purpose: > > I am trying to write a non-blocking, preforked server, specifically to > run on FreeBSD, and have a general question as to whether or not my > strategy is sound. > > > Problem: > > In Unix Network Programming Vol. 1 (section 27.6, p.741), Stevens > mentions a scenario under a preforked server design where multiple > children are calling select() on the same descriptor, causing collisions > for the kernel to resolve. The children would look something like... > . > . > . > for( ; ; ){ > FD_SET(listfd,&rset); > Select(listfd+1,&rset,NULL,NULL,NULL); > if(FD_ISSET(listfd,&rset)==0) > err_quit("listenfd readable"); > > clilen = addrlen; > connfd = Accept(listenfd, cliaddr, &clilen); > > process(connfd); > Close(connfd); > } > . > . > . > > Hypothesis: > > If you were implement the server such that the children used > non-blocking I/O, so that select() returned immediately, would this > alleviate the problem of collisions in the kernel and its associated > overhead? Select ignores non-blocking IO, if you have a non-blocking socket and perform a select on it, you _will_ block (unless you use a zero valued timeout). > If so, would you then have to worry about mutual exclusion when select > did return a ready descriptor for accept(). For example, a child gets > switched just after calling select() but just before it makes it to > accept(). Thus, the next child would also receive the same descriptor > ready for accept()? Now only one of the two children will get to > accept() first, leaving the other blocking on accept(). Stevens mentions > a similar case at the end of the Nonblocking I/O chapter (section 15.6, > p. 422) and to avoid this he recommends 1) setting the listening > descriptor to non-blocking and 2) ignoring EWOULDBLOCK, ECONNABORTED, > etc. on accept(). Yes, that is correct and the correct thing to do. > So, if you make the listening descriptor non-blocking, and treat > select() and accept() appropriately, you should be alright in both > avoiding select collisions and there overhead, as well as avoid children > blocking due to losing possible race conditions for the listen > descriptor in the event (albiet small) of a context switch between > select() and accept(). Another way of doing this would be to have a 'master' accept process that uses fd passing (it's in your book) to hand off connections to children, this would avoid select collisions at the cost of an additional context switch. > > Apology: > > The reason I bother you with all this is that while I (think I) > understand the logic, I (know I) am at the limits of my understanding, > and might be missing some important considerations as to other goings on > in the kernel, and that there might be a better way to go about all > this. Well for one thing I wouldn't be using select, I would use FreeBSD's kqueue mechanism, it's vastly superior to select and poll, although given the choice of select vs poll I would use poll(). > > Summary: > > Ultimately, all I am seeking to do is have an efficient and scalable > server design, and to my knowledge, this would consist of a number of > preforked children who are non-blocking/multiplexing themselves. > Furthermore, each child will have a pool of worker threads which will > handle jobs sent by different clients. As long as the threads' work > doesn't entail an operation that blocks for appreciable amount of time > (so that a single thread puts the whole child to sleep), it would seem > like this might be a decent proposal: multiple clients and multiple jobs > being handled simultaneously by each child, and the number of children > can be controlled by the parent according to the load and limits of the > hardware. > > Does this seem like a good way to go about it? Yes. :) When FreeBSD gets scheduler activations you'll be able to change to a single threaded process that will have excellent performance, the scheduler activations are just around the corner. > > Thanks: you're welcome. > > Thanks. too much coffee today? :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 20:57:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id EEA6237B6ED; Thu, 10 Aug 2000 20:57:15 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id VAA07160; Thu, 10 Aug 2000 21:57:12 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39937AED.7A9DCAE@softweyr.com> Date: Thu, 10 Aug 2000 22:02:53 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Thompson Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: threadsafe name resolution References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Thompson wrote: > > i've just received confirmation from the author of the KAME resolution code > that it isn't at all thread safe: > > >Sure. As noted in name6.c, thread related stuff is not implemented yet. > >Since our resolver code based on bind4 doesn't aware thread safeness, > >all I can do now would be only putting mutex, anyway. > > sure enough, name6.c says: > > /* > * TODO for thread safe > * use mutex for _hostconf, _hostconf_init. > * rewrite resolvers to be thread safe > */ > > now, i'd say that it's fairly important for some form of threadsafe name > resolution to exist. until the KAME code is fixed, how about adding in the > ipv4 _r methods that have been discussed from time to time? or, at the very > least, put something in the manpage for getipnodebyname and friends > indicating that the funcs are not threadsafe. > > as you can probably tell, i wasted several hours worth of work bumping into > this problem. I've been working on fleshing out the _r routines for quite some time now. I've done all the easy ones, and the ones you're looking for are just screaming butt-ugly. It would be simple enough to create a mutex-protected variant of each, but that's not nearly as good a solution as make a REAL _r implementation. If you have implementations to offer, I'd be quite happy to review and commit them. I haven't had enough spare time to even crack the code in months now, unfortunately. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 21:50:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 6C51537BBFD for ; Thu, 10 Aug 2000 21:50:21 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id VAA73535 for ; Thu, 10 Aug 2000 21:50:20 -0700 (PDT) (envelope-from nsayer@medusa.kfu.com) Received: (from nsayer@localhost) by medusa.kfu.com (8.9.3/8.8.8) id VAA93536 for freebsd-hackers@freebsd.org; Thu, 10 Aug 2000 21:50:20 -0700 (PDT) (envelope-from nsayer) Date: Thu, 10 Aug 2000 21:50:20 -0700 (PDT) From: Nick Sayer Message-Id: <200008110450.VAA93536@medusa.kfu.com> To: freebsd-hackers@freebsd.org Subject: ESS Solo users, try this patch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that sometimes ESS sound chips can give back whacky numbers under some circumstances when the dma count register is read while DMA is in progress. I believe this may be a good workaround. I'm considering applying this, but I'd like it to get some more testing first. If you have an ESS Solo: Try this and see if recording 16 bit stereo 44100 audio doesn't generate hwptr warnings. If you have some other ESS chip, see if you can modify the getpos entry of the applicable driver to do something like this. In preliminary testing, I've never seen _good_ adjacent reads be more than 1 number apart, but 16 gives room for slow processors. I've never seen j have to go past 3 (and past 2 only once in a great while). If it gets past 1000, then IMHO the DMA count register has become a pretty good random number generator. :-) The 1000 factor is to avoid infinite loops if the impossible happens. :-) --- src/sys/dev/sound/pci/solo.c 2000/08/09 07:14:56 1.8 +++ src/sys/dev/sound/pci/solo.c 2000/08/11 04:43:30 @@ -756,7 +756,7 @@ static int ess_dmapos(struct ess_info *sc, int ch) { - int p = 0; + int p = 0, i, j = 0; u_long flags; KASSERT(ch == 1 || ch == 2, ("bad ch")); @@ -766,11 +766,17 @@ /* * During recording, this register is known to give back * garbage if it's not quiescent while being read. That's - * why we spl, stop the DMA, wait, and be vewy, vewy quiet + * why we spl, stop the DMA, and try over and over until + * adjacent reads are "close". */ ess_dmatrigger(sc, ch, 0); - DELAY(20); - p = port_rd(sc->vc, 0x4, 2) + 1; + do { + if (j) + printf("DMA count reg bogus: %0x & %0x\n", + i, p); + i = port_rd(sc->vc, 0x4, 2) + 1; + p = port_rd(sc->vc, 0x4, 2) + 1; + } while ((i < p || (p - i) > 0x10) && j++ < 1000) ess_dmatrigger(sc, ch, 1); } else if (ch == 2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 10 22:40:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbtfw.kubota.co.jp (kbtfw.kubota.co.jp [133.253.102.202]) by hub.freebsd.org (Postfix) with ESMTP id 4F64B37BB7E for ; Thu, 10 Aug 2000 22:40:08 -0700 (PDT) (envelope-from haro@tk.kubota.co.jp) Received: by kbtfw.kubota.co.jp; id OAA13284; Fri, 11 Aug 2000 14:40:04 +0900 (JST) Received: from unknown(133.253.122.1) by kbtfw.kubota.co.jp via smap (V4.2) id xma013198; Fri, 11 Aug 00 14:39:59 +0900 Received: from jkpc15.tk.kubota.co.jp ([192.168.7.250]) by kbtmx.eto.kubota.co.jp (8.9.3+3.2W/3.7W) with ESMTP id OAA22236; Fri, 11 Aug 2000 14:39:56 +0900 (JST) Received: from localhost (localhost.ttr.kubota.co.jp [127.0.0.1]) by jkpc15.tk.kubota.co.jp (8.9.3/3.7W-02/21/99) with ESMTP id OAA01814; Fri, 11 Aug 2000 14:36:51 +0900 (JST) To: joseph.scott@owp.csus.edu Cc: taku@cent.saitama-u.ac.jp, julian@elischer.org, abc@bsdi.com, abial@webgiro.com, gandalf@vilnya.demon.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Maestro2E patch (Was: US$100 prize for adding ESS Audiodrivesupport to pcm) In-Reply-To: <39934AA4.5722D1C5@owp.csus.edu> References: <39902AC7.CB39BCD8@owp.csus.edu> <20000811084827Y.haro@tk.kubota.co.jp> <39934AA4.5722D1C5@owp.csus.edu> X-Mailer: Mew version 1.94.1 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Aug_11_14:35:42_2000_518)--" Content-Transfer-Encoding: 7bit Message-Id: <20000811143651N.haro@tk.kubota.co.jp> Date: Fri, 11 Aug 2000 14:36:51 +0900 From: haro@tk.kubota.co.jp (Munehiro Matsuda) X-Dispatcher: imput version 990905(IM130) Lines: 260 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Fri_Aug_11_14:35:42_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Joseph, From: Joseph Scott Date: Thu, 10 Aug 2000 17:36:52 -0700 ::> I have created a patch that trys to enable internal speakers. :: :: The first part of the patch (for maestro.c) didn't apply cleanly for ::me, so I ended up doing it by hand. Thats funny. Did you aply my patch to the original 20000725 version? ::> It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works ::> for everybody. Patch is based on Linux driver, but simplified. ::> ::> If it does not work, 1) try setting GPIO values to what your PC is at ::> when rebooting from Windows, 2) try original way the Linux driver do. ::> Let me know, if you want to know what Linux driver does. :: :: Unfortunately this didn't work for mine (Dell Inspiron 7500). How to ::I find out the GPIO values that make windows work? I'm open to trying ::what the Linux driver does. Mind you my C programing skills are ::pretty much useless, but I'm willing to try things out :-) Aha, Dell Inspiron 7500! There was some extra stuff in the Linux driver for it. I have recreated my patch (mstr2_spk.patch2) to include them. Please aply the new patch to the original 20000725 version source code! And also, I added a small patch (mstr2_gpio.patch) that should print GPIO values. Aply GPIO patch after the mstr2_spk.patch2! Let me know how that works out. BTW, I'll be out of town for few days. So my reply may get delayed. sorry. Thank you, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: haro@kubota.co.jp ----Next_Part(Fri_Aug_11_14:35:42_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mstr2_spk.patch2" --- maestro.c.org Tue Jul 25 03:20:26 2000 +++ maestro.c Fri Aug 11 14:11:33 2000 @@ -50,6 +50,9 @@ #define MAESTRO_2_PCI_ID 0x1968125d #define MAESTRO_2E_PCI_ID 0x1978125d +#define NEC_SUBID1 0x80581033 /* Taken from Linux driver */ +#define NEC_SUBID2 0x803c1033 /* NEC VersaProNX VA26D */ + #define AGG_MAXPLAYCH 4 #define AGG_BUFSIZ (8 << 10) @@ -87,6 +90,8 @@ unsigned playchns, active; struct agg_chinfo pch[AGG_MAXPLAYCH]; struct agg_chinfo rch; + + u_int32_t subid; }; @@ -95,8 +100,8 @@ static void set_timer(struct agg_info*); -static u_int32_t agg_rdcodec(struct agg_info*, int); -static void agg_wrcodec(struct agg_info*, int, u_int32_t); +static u_int32_t agg_rdcodec(void *, int); +static void agg_wrcodec(void *, int, u_int32_t); static inline void ringbus_setdest(struct agg_info*, int, int); @@ -117,9 +122,9 @@ static void agg_init(struct agg_info*); static void agg_deinit(struct agg_info*); -static u_int32_t agg_ac97_init(struct agg_info*); +static u_int32_t agg_ac97_init(void *); -static void agg_intr(struct agg_info*); +static void agg_intr(void *); static pcmchan_init_t aggch_init; static pcmchan_setdir_t aggch_setdir; static pcmchan_setformat_t aggch_setplayformat; @@ -143,8 +148,9 @@ /* Codec/Ringbus */ static u_int32_t -agg_rdcodec(struct agg_info *ess, int regno) +agg_rdcodec(void *s, int regno) { + struct agg_info *ess = (struct agg_info *)s; unsigned t; /* We have to wait for a SAFE time to write addr/data */ @@ -178,8 +184,9 @@ } static void -agg_wrcodec(struct agg_info *ess, int regno, u_int32_t data) +agg_wrcodec(void *s, int regno, u_int32_t data) { + struct agg_info *ess = (struct agg_info *)s; unsigned t; /* We have to wait for a SAFE time to write addr/data */ @@ -351,6 +358,37 @@ | WAVCACHE_WAVETABLE_SIZE_2MB); wp_wrreg(ess, WPREG_BASE, 0x8500); wp_wrreg(ess, WPREG_TIMER_ENABLE, 1); + + /* Setup ASSP. Needed for Dell Inspiron 7500? */ + bus_space_write_1(ess->st, ess->sh, PORT_ASSP_CNTL_B, 0x00); + bus_space_write_1(ess->st, ess->sh, PORT_ASSP_CNTL_A, 0x03); + bus_space_write_1(ess->st, ess->sh, PORT_ASSP_CNTL_C, 0x00); + + /* + * Setup GPIO. + * There seems to be speciality with NEC systems. + */ + switch (ess->subid) { + case NEC_SUBID1: + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, 0x09ff); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DIR)| 0x600); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, 0x0209); + break; + case NEC_SUBID2: + /* For VersaProNX VA26D */ + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, 0x09e4); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, 0x061b); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, 0x03ef); + break; + default: + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_MASK, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_MASK) & 0xfffe); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DIR, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DIR) | 0x11); + bus_space_write_2(ess->st, ess->sh, PORT_GPIO_DATA, + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DATA) | 0x01); + } } static void @@ -371,8 +409,9 @@ } static u_int32_t -agg_ac97_init(struct agg_info *ess) +agg_ac97_init(void *s) { + struct agg_info *ess = (struct agg_info *)s; u_int32_t data; data = bus_space_read_4(ess->st, ess->sh, PORT_RINGBUS_CTRL); @@ -391,8 +430,9 @@ } static void -agg_intr(struct agg_info* ess) +agg_intr(void *s) { + struct agg_info *ess = (struct agg_info *)s; u_int16_t status; int i; @@ -745,7 +785,7 @@ struct agg_info *ess = NULL; u_int32_t data; int mapped = 0; - int regid = PCI_MAP_REG_START; + int regid = PCIR_MAPS; struct resource *reg = NULL; struct ac97_info *codec = NULL; int irqid = 0; @@ -793,6 +833,12 @@ device_printf(dev, "unable to map register space\n"); goto bad; } + + ess->subid = pci_read_config(dev, PCIR_SUBVEND_0, 4); + + /* Needed for Dell Inspiron 7500? */ + data = pci_read_config(dev, CONFIGURATION_B, 2); + pci_write_config(dev, CONFIGURATION_B, data|ENABLE_DSP_IF, 2); agg_init(ess); codec = ac97_create(dev, ess, agg_ac97_init, agg_rdcodec, agg_wrcodec); --- maestro_reg.h.org Tue Jul 25 03:11:52 2000 +++ maestro_reg.h Fri Aug 11 14:12:44 2000 @@ -43,6 +43,10 @@ #define PPMI_D2 2 /* Low power */ #define PPMI_D3 3 /* Turned off */ +/* Maestro2E Configuration B */ +#define CONFIGURATION_B 0x52 /* WORD RW */ +#define ENABLE_DSP_IF 0x0010 + /* ----------------------------- * I/O ports @@ -143,6 +147,17 @@ #define RINGBUS_DEST_RESERVED3 3 #define RINGBUS_DEST_DSOUND_IN 4 #define RINGBUS_DEST_ASSP_IN 5 + +/* GPIO control */ +#define PORT_GPIO_DATA 0x60 /* WORD RW */ +#define PORT_GPIO_MASK 0x64 /* WORD RW */ +#define PORT_GPIO_DIR 0x68 /* WORD RW */ + +/* ASSP control */ +#define PORT_ASSP_CNTL_A 0xa2 /* BYTE RW */ +#define PORT_ASSP_CNTL_B 0xa4 /* BYTE RW */ +#define PORT_ASSP_CNTL_C 0xa6 /* BYTE RW */ + /* ----------------------------- ----Next_Part(Fri_Aug_11_14:35:42_2000_518)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mstr2_gpio.patch" --- maestro.c.org1 Fri Aug 11 14:13:28 2000 +++ maestro.c Fri Aug 11 14:18:42 2000 @@ -834,6 +834,16 @@ goto bad; } +#define DEBUG_GPIO +#ifdef DEBUG_GPIO + printf("GIPO_MASK: %04x\n", + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_MASK)); + printf("GIPO_DIR : %04x\n", + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DIR)); + printf("GIPO_DATA: %04x\n", + bus_space_read_2(ess->st, ess->sh, PORT_GPIO_DATA)); +#endif + ess->subid = pci_read_config(dev, PCIR_SUBVEND_0, 4); /* Needed for Dell Inspiron 7500? */ ----Next_Part(Fri_Aug_11_14:35:42_2000_518)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 1:42:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id DF27F37BFD1; Fri, 11 Aug 2000 01:42:37 -0700 (PDT) (envelope-from nicole@unixgirl.com) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id 2C07220F04; Fri, 11 Aug 2000 01:38:57 -0700 (PDT) Content-Length: 1834 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 11 Aug 2000 01:42:37 -0700 (PDT) From: "Nicole Harrington." To: Brian Fundakowski Feldman Subject: Re: /tmp on a ramdisk? Cc: dillon@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, Doug Barton , Adam Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jul-00 Brian Fundakowski Feldman wrote: > The issue is that mount_mfs is simply newfs with a catch: it > constructs the new filesystem completely in memory and lives on as > the storage for the mounted filesystem. If you view the processes on > a system using MFS, you will notice that one of them is the original > mount_mfs, having become a daemon. > > Yes, things are stored twice in memory: once in the buffer cache and > once in the MFS process. Yes, they are also copied multiple times. > MFS simply can't perform as well as you might expect. The malloc disk > device can because it simply creates a kernel-memory backing store. > The disadvantage here is that it's wired memory and can't get swapped > out like mount_mfs can. > > -- > Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / > green@FreeBSD.org `------------------------------' > > Please forgive my late reply.. Just trying to catch up.. Given all of the above statements, why does BSD/OS (at least on 4.0 and 4.1) want to set up tmp as a Ramdisk? I don't even think there is a way around it during the install. Nicole > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Strong enough for a man - But made for a Woman -- -- OWNED? MS: Who's Been In/Virused Your Computer Today? -- ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 3:26:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sophia.inria.fr (sophia.inria.fr [138.96.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 33F7E37B82C for ; Fri, 11 Aug 2000 03:26:11 -0700 (PDT) (envelope-from Emmanuel.Duros@UDcast.com) Received: from UDcast.com by sophia.inria.fr (8.10.0/8.10.0) with ESMTP id e7BAQ7G26040 for ; Fri, 11 Aug 2000 12:26:08 +0200 (MET DST) X-Authentication-Warning: sophia.inria.fr: Host chouette.inria.fr [138.96.24.103] claimed to be UDcast.com Message-ID: <3993D4BF.F8648EB7@UDcast.com> Date: Fri, 11 Aug 2000 12:26:07 +0200 From: Emmanuel Duros Organization: UniDirectional broadcast corp X-Mailer: Mozilla 4.73 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: fr-FR,en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: module if_disc.ko - network module Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using FreeBSD 3.4R. I am currently investigating on how easy it is to transform a kernel network device driver into a dynamically loadable module. I found and loaded the if_disc.ko module into memory, it seems to work fine because I have a new entry with ifconfig -a. I have no idea what this pseudo network interface is for, and I could not find any man on it. Any idea, pointers ? Where could I find the source ? I wrote a network device driver for a very specialized satellite reception card. This driver is compiled, as most of the network drivers, in the kernel. I am just wondering if it is possible to make this driver a loadable module. Assuming that the board is in on PCI bus, supports DMA bus mastering, may transfer data up to 40Mbps. Any idea, pointers ? What should I pay attention to, what are the limits... ? Thanks in advance, Emmanuel Duros -- UDcast: Where IP and UniDirectional links meet http://www.UDcast.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 3:53:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id E92EE37B960 for ; Fri, 11 Aug 2000 03:53:08 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id UAA57977; Fri, 11 Aug 2000 20:23:05 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id UAA02988; Fri, 11 Aug 2000 20:23:03 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3993D4BF.F8648EB7@UDcast.com> Date: Fri, 11 Aug 2000 20:23:02 +0930 (CST) From: "Daniel O'Connor" To: Emmanuel Duros Subject: RE: module if_disc.ko - network module Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Aug-00 Emmanuel Duros wrote: > I am using FreeBSD 3.4R. Ahh well.. > I am currently investigating on how easy it is to transform a kernel network > device driver into a dynamically loadable module. Upgrade, and ye shall see.. At least it's in -current, and I'm fairly sure it's in 4.0 too. Last I checked though, unloading the network interface tended to be a risky prospect so maybe it hasn't been MFC'd yet.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 5:24: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id CDC2537C0D5 for ; Fri, 11 Aug 2000 05:23:57 -0700 (PDT) (envelope-from frederik@freddym.org) Received: from server.wes.mee.com (pC19EB3B5.dip.t-dialin.net [193.158.179.181]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id OAA29483 for ; Fri, 11 Aug 2000 14:23:55 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id OAA01614 for ; Fri, 11 Aug 2000 14:20:25 +0200 (CEST) Date: Fri, 11 Aug 2000 14:20:25 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: freebsd-hackers@freebsd.org Subject: makeLINT.pl - Bug or am I just stupid Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there! I just searched the LINT config file, and I just saw a makeLINT.pl. So I thought this would build me my configuration file. But it just builds me error messages: [frederik@server conf]$ sh makeLINT.pl =0: not found makeLINT.pl: 5: Syntax error: redirection unexpected [frederik@server conf]$ Line 5 sais: while (<>) { I'm not familiar with Perl, so I can't fix the problem myself. Or am I just stupid. I'm running a just build userland from last Thursday. TIA -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 6: 3:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69]) by hub.freebsd.org (Postfix) with ESMTP id DD0F737C23C for ; Fri, 11 Aug 2000 06:03:39 -0700 (PDT) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id JAA29553; Fri, 11 Aug 2000 09:03:37 -0400 (EDT) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id JAA07618; Fri, 11 Aug 2000 09:02:22 -0400 (EDT) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2652.35) id ; Fri, 11 Aug 2000 09:03:36 -0400 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Frederik Meerwaldt'" , freebsd-hackers@FreeBSD.ORG Subject: RE: makeLINT.pl - Bug or am I just stupid Date: Fri, 11 Aug 2000 09:03:31 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.35) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [frederik@server conf]$ sh makeLINT.pl > =0: not found > makeLINT.pl: 5: Syntax error: redirection unexpected > [frederik@server conf]$ try: perl makeLINT.pl < NOTES thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 6:32:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id CE18237BDDF for ; Fri, 11 Aug 2000 06:32:29 -0700 (PDT) (envelope-from frederik@freddym.org) Received: from server.wes.mee.com (pC19EB37A.dip.t-dialin.net [193.158.179.122]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id PAA14048; Fri, 11 Aug 2000 15:32:27 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by server.wes.mee.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id PAA00763; Fri, 11 Aug 2000 15:11:20 +0200 (CEST) Date: Fri, 11 Aug 2000 15:11:20 +0200 (CEST) From: Frederik Meerwaldt X-Sender: frederik@server.wes.mee.com To: "Yevmenkin, Maksim N, CSCIO" Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: makeLINT.pl - Bug or am I just stupid In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > try: > > perl makeLINT.pl < NOTES Thanks! It works! -- Best Regards, Freddy ===================================================================== Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 7:25: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 204BA37B749; Fri, 11 Aug 2000 07:24:58 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e7BEOsZ08464; Fri, 11 Aug 2000 23:24:54 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: drosih@rpi.edu Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) In-Reply-To: References: <20000810003052A.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000811232450S.iwasaki@jp.FreeBSD.org> Date: Fri, 11 Aug 2000 23:24:50 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 17 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Folks, there are a lot of exciting and cool things, like Processor > >and Device Power State Control, Thermal Management, Replacement > >PnP system, OS initiated hibernation and many :-) I think now is > >the time to start open and development, not only in Japan, for > >FreeBSD ACPI support! > > This all sounds very useful! Glad to see it's merging into the > current branch! Thanks! I know that we need to have a lot of developers to implement these things :-) # We are a very small team in Japan and capabilities is also limited... Now we got very fundamental facility of ACPI here, I hope that many people will have fun hacking them and be involved in the projects. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 7:48:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 4352C37BBCB; Fri, 11 Aug 2000 07:48:33 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e7BEmUZ19307; Fri, 11 Aug 2000 23:48:30 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: imp@village.org Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) In-Reply-To: <200008091953.NAA50150@harmony.village.org> References: <20000810003052A.iwasaki@jp.FreeBSD.org> <200008091953.NAA50150@harmony.village.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000811234827K.iwasaki@jp.FreeBSD.org> Date: Fri, 11 Aug 2000 23:48:27 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 10 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20000810003052A.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: > : Hi, here is the latest (and maybe final?) report on our ACPI project's > : progress. > : > : We are ready now to merge our work on ACPI into main source tree! > > Bravo! Wonderful work! Thanks. I think we need to implement power management features by ACPI replacing APM at least before BIOS w/o APM become majority... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 8:35:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 6A21D37BF39; Fri, 11 Aug 2000 08:35:34 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e7BFZUZ35976; Sat, 12 Aug 2000 00:35:30 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: mdharnois@home.com Cc: iwasaki@jp.FreeBSD.org, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) In-Reply-To: <868zu6uewj.fsf@mharnois.workgroup.net> References: <20000810003052A.iwasaki@jp.FreeBSD.org> <868zu6uewj.fsf@mharnois.workgroup.net> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000812003527P.iwasaki@jp.FreeBSD.org> Date: Sat, 12 Aug 2000 00:35:27 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not quite sure what it does, but it seems to work fine here on my > ASUS CUSL2, at least the shutdown part. Thank you for your report. It would be helpful to check http://www.teleport.com/~acpi/whatis1.htm and it's links. It is related with quite wide areas, not only for power management. # I'm interested in power management part personally for the first step # though. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 9:24: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.cs.umn.edu (mail.cs.umn.edu [128.101.36.200]) by hub.freebsd.org (Postfix) with ESMTP id E2D1437C0FF; Fri, 11 Aug 2000 09:23:46 -0700 (PDT) (envelope-from beyer@cs.umn.edu) Received: from debussey.cs.umn.edu (IDENT:root@debussey.cs.umn.edu [128.101.34.193]) by mail.cs.umn.edu (8.9.3/8.9.3) with ESMTP id LAA25984; Fri, 11 Aug 2000 11:23:44 -0500 (CDT) Received: from localhost (beyer@localhost) by debussey.cs.umn.edu (8.9.3/8.9.0) with ESMTP id LAA04435; Fri, 11 Aug 2000 11:23:43 -0500 X-Authentication-Warning: debussey.cs.umn.edu: beyer owned process doing -bs Date: Fri, 11 Aug 2000 11:23:43 -0500 (CDT) From: "James C. Beyer" To: Daniel Lang Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Installation Problems on Dell PowerEdge 6100/200 In-Reply-To: <20000808144202.A14579@atrbg11.informatik.tu-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have a machine here in the lab that is the precurser of your machine that we also had boot problems with. What I found was that the adaptec BIOS Disks > 1GB support was breaking the linux and FreeBSD boot routine. When I disabled Disks > 1GB my problems were solved. It seems the BIOS setting is for machines running OSes that need help looking at large disks. I hope this helps. If you already have your machine working great; I hope this my help someone else then. james On Tue, 8 Aug 2000, Daniel Lang wrote: > Hi, > > we've got a Dell PowerEdge 6100/200 here, which is an older > SMP server, featuring 4 PPro 200 CPU's two internal AIC7880 > channels and an Adaptec 2940UW PCI controller. One of the > AIC's is connected to a SCA Backplane that holds 4 disks. > > Now before even having a chance to see if FreeBSD-SMP > works with this box, I didn't manage to install FreeBSD > (4.1) correctly. Well, installation seems to go well in > any attempt: > > - Floppy boots, Kernel finds all ahc's and disks > - Installation seems to succeed (Partitioning, installation, etc) > > But then, the machine won't boot. It seems to happen, that the > MBR of the target device (da0, which is the first disk on the > second controller, channel A of internal AIC's) is found, but > the next stage of the bootstrapping process cannot be found. > I played also around using boot0 and installing on other disks, > this is like what I got: > > Standard MBR and System on da0: -> Missing operating system > boot0 MBR and System on da0: -> F1 -> *beep* (nothing else) > boot0 MBR (and old System) on da0, standard MBR and System on da1: > booting from da0: F1 -> *beep*, F5 (disk2) -> Missing operating system > booting from da1: -> Missing operating system > > So it seems no boot-block after the MBR can be found. > > I tried: - installing and booting from different disks on internal ahc > - disabling some of the controllers > - installing and booting from a disk on the 2940, > as well while disabling the others > > It all had no effect. > > All adaptec's BIOS has Disks > 1GB and INT13 enabled (of course the > BIOS itself is enabled, too) > > Previously Solaris 7/x86 was running on this machine, there > were no such problems, but we don't really want to run Solaris... :-} > > Any clue ? > > Many thanks, > Daniel > -- > IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you > will be approximated. - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* > > -- > IRCnet: Mr-Spock - May His Shadow fall upon thee - > *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 9:38:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fobos.marketsite.ru (fobos.marketsite.ru [194.226.198.36]) by hub.freebsd.org (Postfix) with ESMTP id F097537B55C for ; Fri, 11 Aug 2000 09:37:39 -0700 (PDT) (envelope-from diwil@dataart.com) Received: from bb.marketsite.ru ([194.226.198.1] helo=runnet-gw.marketsite.ru) by fobos.marketsite.ru with esmtp (Exim 3.02 #4) id 13NHoI-000KKI-00 for freebsd-hackers@freebsd.org; Fri, 11 Aug 2000 20:37:30 +0400 Content-Length: 24813 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 11 Aug 2000 20:37:56 +0400 (MSD) Reply-To: diwil@dataart.com From: dimmy the wild To: freebsd-hackers@freebsd.org Subject: fm801 sound chip Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi fellows, hi fellows, I'm just wondering if somebody has thought about writing a driver for fm801 based sound chip. I did. I have got hot-687z motherboard with fm801 sound on-board. Actually, I never wrote sound drivers before and the code below is my first attempt to write sound driver for FreeBSD. Even more - I do not have _ANY_ specifications of the fm801 sound chip. The code is a mixture of ALSA and NetBSD drivers. It works fine in 8000/sps, mono... But... The problem with the driver is - It cannot change play formats correctly. and sometimes is loops while playing. Sometimes it loops forever. Does anybody know anything about fm801? Or has somebody any datasheet on fm801? Thanks in advance, Dmitry ------------------ CUT HERE ------------------------------ #include #include #include #include #include #define PCI_VENDOR_FORTEMEDIA 0x1319 #define PCI_DEVICE_FORTEMEDIA1 0x08011319 #define PCI_DEVICE_FORTEMEDIA2 0x08021319 #define FM_PCM_VOLUME 0x00 #define FM_FM_VOLUME 0x02 #define FM_I2S_VOLUME 0x04 #define FM_RECORD_SOURCE 0x06 #define FM_PLAY_CTL 0x08 #define FM_PLAY_RATE_MASK 0x0f00 #define FM_PLAY_BUF1_LAST 0x0001 #define FM_PLAY_BUF2_LAST 0x0002 #define FM_PLAY_START 0x0020 #define FM_PLAY_PAUSE 0x0040 #define FM_PLAY_STOPNOW 0x0080 #define FM_PLAY_16BIT 0x4000 #define FM_PLAY_STEREO 0x8000 #define FM_PLAY_DMALEN 0x0a #define FM_PLAY_DMABUF1 0x0c #define FM_PLAY_DMABUF2 0x10 #define FM_REC_CTL 0x14 #define FM_REC_RATE_MASK 0x0f00 #define FM_REC_BUF1_LAST 0x0001 #define FM_REC_BUF2_LAST 0x0002 #define FM_REC_START 0x0020 #define FM_REC_PAUSE 0x0040 #define FM_REC_STOPNOW 0x0080 #define FM_REC_16BIT 0x4000 #define FM_REC_STEREO 0x8000 #define FM_REC_DMALEN 0x16 #define FM_REC_DMABUF1 0x18 #define FM_REC_DMABUF2 0x1c #define FM_CODEC_CTL 0x22 #define FM_VOLUME 0x26 #define FM_VOLUME_MUTE 0x8000 #define FM_CODEC_CMD 0x2a #define FM_CODEC_CMD_READ 0x0080 #define FM_CODEC_CMD_VALID 0x0100 #define FM_CODEC_CMD_BUSY 0x0200 #define FM_CODEC_DATA 0x2c #define FM_IO_CTL 0x52 #define FM_CARD_CTL 0x54 #define FM_INTMASK 0x56 #define FM_INTMASK_PLAY 0x0001 #define FM_INTMASK_REC 0x0002 #define FM_INTMASK_VOL 0x0040 #define FM_INTMASK_MPU 0x0080 #define FM_INTSTATUS 0x5a #define FM_INTSTATUS_PLAY 0x0100 #define FM_INTSTATUS_REC 0x0200 #define FM_INTSTATUS_VOL 0x4000 #define FM_INTSTATUS_MPU 0x8000 #define FM801_BUFFSIZE 1024*32 /* channel interface */ static void *fm801ch_init(void *devinfo, snd_dbuf *b, pcm_channel *c, int dir); static int fm801ch_setdir(void *data, int dir); static int fm801ch_setformat(void *data, u_int32_t format); static int fm801ch_setspeed(void *data, u_int32_t speed); static int fm801ch_setblocksize(void *data, u_int32_t blocksize); static int fm801ch_trigger(void *data, int go); static int fm801ch_getptr(void *data); static pcmchan_caps *fm801ch_getcaps(void *data); /* static int fm801ch_setup(pcm_channel *c); */ static pcmchan_caps fm801ch_caps = { 4000, 48000, AFMT_STEREO | AFMT_U8 | AFMT_S8 | AFMT_S16_LE | AFMT_S16_BE | AFMT_U16_LE | AFMT_U16_BE, AFMT_STEREO | AFMT_U8 | AFMT_S16_LE }; static pcm_channel fm801_chantemplate = { fm801ch_init, fm801ch_setdir, fm801ch_setformat, fm801ch_setspeed, fm801ch_setblocksize, fm801ch_trigger, fm801ch_getptr, fm801ch_getcaps, }; struct fm801_info; struct fm801_chinfo { struct fm801_info *parent; pcm_channel *channel; snd_dbuf *buffer; u_int32_t spd, dir, fmt; /* speed, direction, format */ u_int32_t shift; }; struct fm801_info { int type; bus_space_tag_t st; bus_space_handle_t sh; bus_dma_tag_t parent_dmat; device_t dev; int num; u_int32_t unit; struct resource *reg, *irq; int regtype, regid, irqid; void *ih; u_int32_t play_pos, play_count, play_size, play_buffer, play_flip, play_nextblk, play_end, play_start, play_blksize, play_fmt, play_shift; u_int32_t rec_pos, rec_count, rec_size, rec_buffer, rec_flip, rec_nextblk, rec_end, rec_start, rec_blksize, rec_fmt, rec_shift; struct fm801_chinfo pch, rch; }; static struct fm801_info *save801; struct fm801_info *fm801_get __P((void )); static void fm801_save(struct fm801_info *fm801) { save801 = fm801; } struct fm801_info * fm801_get(void ) { return save801; } /* Bus Read / Write routines */ static u_int32_t fm801_rd(struct fm801_info *fm801, int regno, int size) { switch(size) { case 1: return (bus_space_read_1(fm801->st, fm801->sh, regno)); case 2: return (bus_space_read_2(fm801->st, fm801->sh, regno)); case 4: return (bus_space_read_4(fm801->st, fm801->sh, regno)); default: return 0xffffffff; } } static void fm801_wr(struct fm801_info *fm801, int regno, u_int32_t data, int size) { switch(size) { case 1: return bus_space_write_1(fm801->st, fm801->sh, regno, data); case 2: return bus_space_write_2(fm801->st, fm801->sh, regno, data); case 4: return bus_space_write_4(fm801->st, fm801->sh, regno, data); default: return; } } /* * ac97 codec routines */ #define TIMO 50 static u_int32_t fm801_rdcd(void *devinfo, int regno) { struct fm801_info *fm801 = (struct fm801_info *)devinfo; int i; for (i = 0; i < TIMO && fm801_rd(fm801,FM_CODEC_CMD,2) & FM_CODEC_CMD_BUSY; i++) { DELAY(10000); } if (i >= TIMO) { printf("fm801 rdcd: codec busy\n"); return 0; } fm801_wr(fm801,FM_CODEC_CMD, regno|FM_CODEC_CMD_READ,2); for (i = 0; i < TIMO && !(fm801_rd(fm801,FM_CODEC_CMD,2) & FM_CODEC_CMD_VALID); i++) { DELAY(10000); } if (i >= TIMO) { printf("fm801 rdcd: write codec invalid\n"); return 0; } return fm801_rd(fm801,FM_CODEC_DATA,2); } static void fm801_wrcd(void *devinfo, int regno, u_int32_t data) { struct fm801_info *fm801 = (struct fm801_info *)devinfo; int i; /* Poll until codec is ready */ for (i = 0; i < TIMO && fm801_rd(fm801,FM_CODEC_CMD,2) & FM_CODEC_CMD_BUSY; i++) { DELAY(10000); } if (i >= TIMO) { printf("fm801 wrcd: read codec busy\n"); return; } fm801_wr(fm801,FM_CODEC_DATA,data, 2); fm801_wr(fm801,FM_CODEC_CMD, regno,2); return; } /* * The interrupt handler * Alsa+NetBSD symbiosys */ static void fm801_intr(void *p) { struct fm801_info *fm801 = (struct fm801_info *)p; u_int32_t intsrc = fm801_rd(fm801, FM_INTSTATUS, 2); printf("fm801_intr intsrc 0x%x, nextblk %d \n",intsrc, fm801->play_start + fm801->play_blksize ); if(intsrc & FM_INTSTATUS_PLAY) { if ( (fm801->play_nextblk += fm801->play_blksize) >= fm801->play_end) fm801->play_nextblk = fm801->play_start; fm801_wr(fm801, fm801->play_flip++ & 1 ? FM_PLAY_DMABUF2 : FM_PLAY_DMABUF1, fm801->play_nextblk,4); } else if(intsrc & FM_INTSTATUS_REC) { if ( (fm801->rec_nextblk += fm801->rec_blksize) >= fm801->rec_end) fm801->rec_nextblk = fm801->rec_start; fm801_wr(fm801, fm801->rec_flip++ & 1 ? FM_REC_DMABUF2 : FM_REC_DMABUF1, fm801->rec_nextblk,4); } /* clear interrupt */ fm801_wr(fm801, FM_INTSTATUS, intsrc & (FM_INTSTATUS_PLAY | FM_INTSTATUS_REC), 2); printf("fm801_intr status restored\n"); } /* * Init routine is taken from original NetBSD driver */ static int fm801_init(struct fm801_info *fm801) { u_int32_t k1; /* reset codec */ fm801_wr(fm801, FM_CODEC_CTL, 0x0020,2); DELAY(100000); fm801_wr(fm801, FM_CODEC_CTL, 0x0000,2); DELAY(100000); fm801_wr(fm801, FM_PCM_VOLUME, 0x0808,2); fm801_wr(fm801, FM_FM_VOLUME, 0x0808,2); fm801_wr(fm801, FM_I2S_VOLUME, 0x0808,2); fm801_wr((void *)fm801, FM_RECORD_SOURCE, 0x0000,2); /* Unmask playback, record and mpu interrupts, mask the rest */ k1 = fm801_rd((void *)fm801, FM_INTMASK,2); fm801_wr(fm801, FM_INTMASK, (k1 & ~(FM_INTMASK_PLAY | FM_INTMASK_REC | FM_INTMASK_MPU)) | FM_INTMASK_VOL,2); fm801_wr(fm801, FM_INTSTATUS, FM_INTSTATUS_PLAY | FM_INTSTATUS_REC | FM_INTSTATUS_MPU | FM_INTSTATUS_VOL,2); printf("FM801 init Ok\n"); return 0; } static int fm801_pci_attach(device_t dev) { snddev_info *d; u_int32_t data; struct ac97_info *codec; struct fm801_info *fm801; int i; int mapped = 0; char status[SND_STATUSLEN]; d = device_get_softc(dev); if ((fm801 = (struct fm801_info *)malloc(sizeof(*fm801),M_DEVBUF, M_NOWAIT)) == NULL) { device_printf(dev, "cannot allocate softc\n"); return ENXIO; } bzero(fm801, sizeof(*fm801)); fm801->type = pci_get_devid(dev); data = pci_read_config(dev, PCIR_COMMAND, 2); data |= (PCIM_CMD_PORTEN|PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); pci_write_config(dev, PCIR_COMMAND, data, 2); data = pci_read_config(dev, PCIR_COMMAND, 2); for (i = 0; (mapped == 0) && (i < PCI_MAXMAPS_0); i++) { fm801->regid = PCIR_MAPS + i*4; fm801->regtype = SYS_RES_MEMORY; fm801->reg = bus_alloc_resource(dev, fm801->regtype, &fm801->regid, 0, ~0, 1, RF_ACTIVE); if(!fm801->reg) { fm801->regtype = SYS_RES_IOPORT; fm801->reg = bus_alloc_resource(dev, fm801->regtype, &fm801->regid, 0, ~0, 1, RF_ACTIVE); } if(fm801->reg) { fm801->st = rman_get_bustag(fm801->reg); fm801->sh = rman_get_bushandle(fm801->reg); mapped++; } } if (mapped == 0) { device_printf(dev, "unable to map register space\n"); goto oops; } fm801_init(fm801); codec = ac97_create(dev, (void *)fm801, NULL, fm801_rdcd, fm801_wrcd); if (codec == NULL) goto oops; if (mixer_init(d, &ac97_mixer, codec) == -1) goto oops; fm801->irqid = 0; fm801->irq = bus_alloc_resource(dev, SYS_RES_IRQ, &fm801->irqid, 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); if (!fm801->irq || bus_setup_intr(dev, fm801->irq, INTR_TYPE_TTY, fm801_intr, fm801, &fm801->ih)) { device_printf(dev, "unable to map interrupt\n"); goto oops; } if (bus_dma_tag_create(/*parent*/NULL, /*alignment*/2, /*boundary*/0, /*lowaddr*/BUS_SPACE_MAXADDR_32BIT, /*highaddr*/BUS_SPACE_MAXADDR, /*filter*/NULL, /*filterarg*/NULL, /*maxsize*/FM801_BUFFSIZE, /*nsegments*/1, /*maxsegz*/0x3ffff, /*flags*/0, &fm801->parent_dmat) != 0) { device_printf(dev, "unable to create dma tag\n"); goto oops; } snprintf(status, 64, "at %s 0x%lx irq %ld", (fm801->regtype == SYS_RES_IOPORT)? "io" : "memory", rman_get_start(fm801->reg), rman_get_start(fm801->irq)); #define FM801_MAXPLAYCH 1 if (pcm_register(dev, fm801, FM801_MAXPLAYCH, 1)) goto oops; pcm_addchan(dev, PCMDIR_PLAY, &fm801_chantemplate, fm801); pcm_addchan(dev, PCMDIR_REC, &fm801_chantemplate, fm801); pcm_setstatus(dev, status); fm801_save(fm801); return 0; oops: printf("Forte Media FM801 initialization failed\n"); if (fm801->reg) bus_release_resource(dev, fm801->regtype, fm801->regid, fm801->reg); if (fm801->ih) bus_teardown_intr(dev, fm801->irq, fm801->ih); if (fm801->irq) bus_release_resource(dev, SYS_RES_IRQ, fm801->irqid, fm801->irq); free(fm801, M_DEVBUF); return ENXIO; } static int fm801_pci_probe( device_t dev ) { int id; if ((id = pci_get_devid(dev)) == PCI_DEVICE_FORTEMEDIA1 ) { device_set_desc(dev, "Forte Media FM801 Audio Controller"); return 0; } /* if ((id = pci_get_devid(dev)) == PCI_DEVICE_FORTEMEDIA2 ) { device_set_desc(dev, "Forte Media FM801 Input Device(?)"); return 0; } */ return ENXIO; } /* copied from NetBSD driver */ struct { int limit; int rate; } fm801_rates[11] = { { 6600, 5500 }, { 8750, 8000 }, { 10250, 9600 }, { 13200, 11025 }, { 17500, 16000 }, { 20500, 19200 }, { 26500, 22050 }, { 35000, 32000 }, { 41000, 38400 }, { 46000, 44100 }, { 48000, 48000 }, /* anything above -> 48000 */ }; /* channel interface */ static void * fm801ch_init(void *devinfo, snd_dbuf *b, pcm_channel *c, int dir) { struct fm801_info *fm801 = (struct fm801_info *)devinfo; struct fm801_chinfo *ch = (dir == PCMDIR_PLAY)? &fm801->pch : &fm801->rch; printf("fm801ch_init, direction = %d\n", dir); ch->parent = fm801; ch->channel = c; ch->buffer = b; ch->buffer->bufsize = FM801_BUFFSIZE; ch->dir = dir; if( chn_allocbuf(ch->buffer, fm801->parent_dmat) == -1) return NULL; return (void *)ch; } static int fm801ch_setdir(void *data, int dir) { struct fm801_chinfo *ch = data; ch->dir = dir; printf("fm801ch_setdir -> %x\n", dir); return 0; } static int fm801ch_setformat(void *data, u_int32_t format) { struct fm801_chinfo *ch = data; struct fm801_info *fm801 = ch->parent; int k1; printf("fm801ch_setformat -> 0x%x of 0x%x\n", format, fm801ch_caps.formats); if(ch->dir == PCMDIR_PLAY) { fm801->play_fmt = (format & AFMT_STEREO)? FM_PLAY_STEREO:0 | (format & (AFMT_S16_LE | AFMT_S16_BE | AFMT_U16_LE | AFMT_U16_BE) ) ? FM_PLAY_16BIT:0 | fm801->play_shift ; k1 = ~( FM_PLAY_START | FM_PLAY_16BIT | FM_PLAY_STEREO| FM_PLAY_RATE_MASK); fm801->play_fmt |= k1; fm801_wr(fm801, FM_PLAY_CTL, fm801->play_fmt, 2); printf("FORMAT 0x%x (k1 0x%x)\n", fm801->play_fmt, k1); return fm801->play_fmt; } if(ch->dir == PCMDIR_REC ) { fm801->rec_fmt = (format & AFMT_STEREO)? FM_REC_STEREO:0 | (format & (AFMT_S16_LE | AFMT_S16_BE | AFMT_U16_LE | AFMT_U16_BE) ) ? FM_REC_16BIT:0 | fm801->rec_shift ; k1 = ~( FM_REC_START | FM_REC_16BIT | FM_REC_STEREO| FM_REC_RATE_MASK); fm801->rec_fmt |= k1; return fm801->rec_fmt; } return 0; } static int fm801ch_setspeed(void *data, u_int32_t speed) { struct fm801_chinfo *ch = data; struct fm801_info *fm801 = ch->parent; register int i; for (i = 0; i < 10 && fm801_rates[i].limit < speed; i++) ; printf("fm801ch_setspeed -> req: %d , avail: %d, (dir %d)\n", speed, fm801_rates[i].rate, ch->dir); if(ch->dir == PCMDIR_PLAY) { fm801->pch.spd = fm801_rates[i].rate; fm801->pch.shift = (i<<8); } if(ch->dir == PCMDIR_REC ) { fm801->rch.spd = fm801_rates[i].rate; fm801->rch.shift = (i<<8); } return fm801_rates[i].rate; } static int fm801ch_setblocksize(void *data, u_int32_t blocksize) { struct fm801_chinfo *ch = data; struct fm801_info *fm801 = ch->parent; fm801->play_blksize = blocksize; fm801->rec_blksize = blocksize; printf("fm801ch_setblocksize %d (dir %d)\n",blocksize, ch->dir); return blocksize; } static int fm801ch_trigger(void *data, int go) { struct fm801_chinfo *ch = data; struct fm801_info *fm801 = ch->parent; u_int32_t baseaddr = vtophys(ch->buffer->buf); snd_dbuf *b = ch->buffer; u_int32_t k1; printf("fm801ch_trigger -> go %d, dir %d (size %d)\n", go, ch->dir, b->fp - b->rp ); if (go == PCMTRIG_EMLDMAWR || go == PCMTRIG_EMLDMARD) return 0; if (ch->dir == PCMDIR_PLAY) { if (go == PCMTRIG_START) { fm801->play_start = baseaddr; fm801->play_end = fm801->play_start + b->fp - b->rp; fm801->play_blksize = b->blksz; fm801->play_nextblk = fm801->play_start + fm801->play_blksize; fm801->play_flip = 0; fm801_wr(fm801, FM_PLAY_DMALEN, fm801->play_blksize /* -1 */, 2); fm801_wr(fm801, FM_PLAY_DMABUF1,fm801->play_start,4); fm801_wr(fm801, FM_PLAY_DMABUF2,fm801->play_nextblk,4); fm801_wr(fm801, FM_PLAY_CTL, FM_PLAY_START | FM_PLAY_STOPNOW, /* * As follows from the NetBSD driver we should put * 'fm801->play_fmt' as bitwise OR right here, * but if this set everything works very strange - * no sound can be heard and getptr() returns 0x800 permanently. * | fm801->play_fmt * */ 2 ); } else { k1 = fm801_rd(fm801, FM_PLAY_CTL,2); fm801_wr(fm801, FM_PLAY_CTL, (k1 & ~(FM_PLAY_STOPNOW | FM_PLAY_START)) | FM_PLAY_BUF1_LAST | FM_PLAY_BUF2_LAST, 2 ); } } else if(ch->dir == PCMDIR_REC) { if (go == PCMTRIG_START) { fm801->rec_start = baseaddr; fm801->rec_end = fm801->rec_start + b->fp - b->rp; fm801->rec_blksize = b->blksz; fm801->rec_nextblk = fm801->rec_start + fm801->rec_blksize; fm801->rec_flip = 0; fm801_wr(fm801, FM_REC_DMALEN, fm801->rec_blksize - 1, 2); fm801_wr(fm801, FM_REC_DMABUF1,fm801->rec_start,4); fm801_wr(fm801, FM_REC_DMABUF2,fm801->rec_nextblk,4); fm801_wr(fm801, FM_REC_CTL, FM_REC_START | FM_REC_STOPNOW, 2 ); } else { k1 = fm801_rd(fm801, FM_REC_CTL,2); fm801_wr(fm801, FM_REC_CTL, (k1 & ~(FM_REC_STOPNOW | FM_REC_START)) | FM_REC_BUF1_LAST | FM_REC_BUF2_LAST, 2); } } return 0; } /* Almost ALSA copy */ static int fm801ch_getptr(void *data) { struct fm801_chinfo *ch = data; struct fm801_info *fm801 = ch->parent; int result; if (ch->dir == PCMDIR_PLAY) { result = fm801_rd(fm801, FM_PLAY_DMALEN,2) - 1; } else if (ch->dir == PCMDIR_REC) { result = fm801_rd(fm801, FM_REC_DMALEN,2) + 1; } else { result = 0; } printf("fm801ch_getptr (dir %d) result 0x%x\n",ch->dir,result); return result; } static pcmchan_caps * fm801ch_getcaps(void *data) { struct fm801_chinfo *ch = data; printf("fm801ch_getcaps (dir %d)\n", ch->dir); return &fm801ch_caps; } static int fm801_pci_detach(device_t dev) { struct fm801_info *fm801 = fm801_get(); printf("Forte Media FM801 detach\n"); if (fm801->reg) bus_release_resource(dev, fm801->regtype, fm801->regid, fm801->reg); if (fm801->ih) bus_teardown_intr(dev, fm801->irq, fm801->ih); if (fm801->irq) bus_release_resource(dev, SYS_RES_IRQ, fm801->irqid, fm801->irq); free(fm801, M_DEVBUF); return 0; } static device_method_t fm801_methods[] = { /* Device interface */ DEVMETHOD(device_probe, fm801_pci_probe), DEVMETHOD(device_attach, fm801_pci_attach), DEVMETHOD(device_detach, fm801_pci_detach), { 0, 0} }; static driver_t fm801_driver = { "pcm", fm801_methods, sizeof(snddev_info), }; static devclass_t pcm_devclass; DRIVER_MODULE(fm801, pci, fm801_driver, pcm_devclass, 0, 0); ------------------ CUT HERE ------------------------------ -- ********************************************************************** ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) DataArt Enterprises, Inc. (_Y_.)' ._ ) `._ `. ``-..-' Serpukhovskaja street, 10 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3261780, 5552490 ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 9:56:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 1A7A237B527; Fri, 11 Aug 2000 09:56:06 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13NI6G-00074s-00; Fri, 11 Aug 2000 16:56:04 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id SAA07107; Fri, 11 Aug 2000 18:56:03 +0200 (CEST) (envelope-from wkb) Date: Fri, 11 Aug 2000 18:56:03 +0200 From: Wilko Bulte To: Mitsuru IWASAKI Cc: mdharnois@home.com, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) Message-ID: <20000811185603.B7043@freebie.demon.nl> References: <20000810003052A.iwasaki@jp.FreeBSD.org> <868zu6uewj.fsf@mharnois.workgroup.net> <20000812003527P.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000812003527P.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Sat, Aug 12, 2000 at 12:35:27AM +0900 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 12, 2000 at 12:35:27AM +0900, Mitsuru IWASAKI wrote: > > I'm not quite sure what it does, but it seems to work fine here on my > > ASUS CUSL2, at least the shutdown part. > > Thank you for your report. It would be helpful to check > http://www.teleport.com/~acpi/whatis1.htm > and it's links. Interesting information, thanks for the pointer. > It is related with quite wide areas, not only for power management. > # I'm interested in power management part personally for the first step > # though. Do I understand correctly that things like monitoring cooling fans etc is also possible? I guess the people running (lots of) servers will be interested in those features too. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 10: 4:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [205.178.90.194]) by hub.freebsd.org (Postfix) with ESMTP id 611FD37B6A0; Fri, 11 Aug 2000 10:04:22 -0700 (PDT) (envelope-from nsayer@freebsd.org) Received: from medusa.kfu.com (medusa.kfu.com [205.178.90.222]) by quack.kfu.com (8.9.3/8.9.3) with ESMTP id KAA78180; Fri, 11 Aug 2000 10:04:21 -0700 (PDT) (envelope-from nsayer@freebsd.org) Received: from localhost (nsayer@localhost) by medusa.kfu.com (8.9.3/8.8.8) with ESMTP id KAA99112; Fri, 11 Aug 2000 10:04:21 -0700 (PDT) (envelope-from nsayer@freebsd.org) X-Authentication-Warning: medusa.kfu.com: nsayer owned process doing -bs Date: Fri, 11 Aug 2000 10:04:21 -0700 (PDT) From: Nick Sayer X-Sender: nsayer@medusa.kfu.com To: freebsd-hackers@freebsd.org Cc: cg@freebsd.org Subject: Re: ESS Solo users, try this patch In-Reply-To: <200008110450.VAA93536@medusa.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-601538151-966013461=:99078" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-601538151-966013461=:99078 Content-Type: TEXT/PLAIN; charset=US-ASCII The last patch improved, but did not completely eliminate the warnings. This one appears to do the job perfectly. The question is, does calling DELAY() like this cause any concerns for anyone? --0-601538151-966013461=:99078 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=p Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=p SW5kZXg6IHNvbG8uYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZp bGU6IC9ob21lL25jdnMvc3JjL3N5cy9kZXYvc291bmQvcGNpL3NvbG8uYyx2 DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuOA0KZGlmZiAtdSAtcjEuOCBzb2xv LmMNCi0tLSBzb2xvLmMJMjAwMC8wOC8wOSAwNzoxNDo1NgkxLjgNCisrKyBz b2xvLmMJMjAwMC8wOC8xMSAxNzowMToyMg0KQEAgLTc1Niw3ICs3NTYsNyBA QA0KIHN0YXRpYyBpbnQNCiBlc3NfZG1hcG9zKHN0cnVjdCBlc3NfaW5mbyAq c2MsIGludCBjaCkNCiB7DQotCWludCBwID0gMDsNCisJaW50IHAgPSAwLCBp ID0gMCwgaiA9IDA7DQogCXVfbG9uZyBmbGFnczsNCiANCiAJS0FTU0VSVChj aCA9PSAxIHx8IGNoID09IDIsICgiYmFkIGNoIikpOw0KQEAgLTc2NiwxMSAr NzY2LDIwIEBADQogLyoNCiAgKiBEdXJpbmcgcmVjb3JkaW5nLCB0aGlzIHJl Z2lzdGVyIGlzIGtub3duIHRvIGdpdmUgYmFjaw0KICAqIGdhcmJhZ2UgaWYg aXQncyBub3QgcXVpZXNjZW50IHdoaWxlIGJlaW5nIHJlYWQuIFRoYXQncw0K LSAqIHdoeSB3ZSBzcGwsIHN0b3AgdGhlIERNQSwgd2FpdCwgYW5kIGJlIHZl d3ksIHZld3kgcXVpZXQNCisgKiB3aHkgd2Ugc3BsLCBzdG9wIHRoZSBETUEs IGFuZCB0cnkgb3ZlciBhbmQgb3ZlciB1bnRpbA0KKyAqIGFkamFjZW50IHJl YWRzIGFyZSAiY2xvc2UiLCBpbiB0aGUgcmlnaHQgb3JkZXIgYW5kIG5vdA0K KyAqIGJpZ2dlciB0aGFuIGlzIG90aGVyd2lzZSBwb3NzaWJsZS4NCiAgKi8N CiAJCWVzc19kbWF0cmlnZ2VyKHNjLCBjaCwgMCk7DQotICAgIAkJREVMQVko MjApOw0KLQkJcCA9IHBvcnRfcmQoc2MtPnZjLCAweDQsIDIpICsgMTsNCisJ CURFTEFZKDIwKTsNCisJCWRvIHsNCisJCQlERUxBWSgxMCk7DQorCQkJaWYg KGogPiAxKQ0KKwkJCQlwcmludGYoIkRNQSBjb3VudCByZWcgYm9ndXM6ICUw NHggJiAlMDR4XG4iLA0KKwkJCQkJaSwgcCk7DQorCQkJaSA9IHBvcnRfcmQo c2MtPnZjLCAweDQsIDIpICsgMTsNCisJCQlwID0gcG9ydF9yZChzYy0+dmMs IDB4NCwgMikgKyAxOw0KKwkJfSB3aGlsZSAoKHAgPiBzYy0+ZG1hc3pbY2gg LTEgXSB8fCBpIDwgcCB8fCAocCAtIGkpID4gMHg4KSAmJiBqKysgPCAxMDAw KTsNCiAJCWVzc19kbWF0cmlnZ2VyKHNjLCBjaCwgMSk7DQogCX0NCiAJZWxz ZSBpZiAoY2ggPT0gMikNCg== --0-601538151-966013461=:99078-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 10:28: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 83F3437B71C; Fri, 11 Aug 2000 10:27:55 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e7BHRmZ73399; Sat, 12 Aug 2000 02:27:49 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: wkb@freebie.demon.nl Cc: iwasaki@jp.FreeBSD.org, mdharnois@home.com, freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Re: ACPI project progress report (final?) In-Reply-To: <20000811185603.B7043@freebie.demon.nl> References: <868zu6uewj.fsf@mharnois.workgroup.net> <20000812003527P.iwasaki@jp.FreeBSD.org> <20000811185603.B7043@freebie.demon.nl> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000812022747W.iwasaki@jp.FreeBSD.org> Date: Sat, 12 Aug 2000 02:27:47 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 27 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is related with quite wide areas, not only for power management. > > # I'm interested in power management part personally for the first step > > # though. > > Do I understand correctly that things like monitoring cooling fans etc is > also possible? I guess the people running (lots of) servers will be > interested in those features too. Yes, of course :-) ACPI covers the thermal management also. I could imagine that there are quite big needs in this area for server computing. I think this is what you are interested in, from ACPI 1.0b spec. contents; 12. THERMAL MANAGEMENT 12.1 Thermal Control 12.1.1 Active, Passive, and Critical Policies 12.1.2 Dynamically Changing Cooling Temperatures 12.1.3 Hardware Thermal Events 12.1.4 Active Cooling Strength 12.1.5 Passive Cooling Equation 12.1.6 Critical Shutdown You can get ACPI spec. documents from http://www.teleport.com/~acpi/spec.htm # I haven't checked ACPI spec 2.0 yet though :-) Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 10:43:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 2BE3B37B571 for ; Fri, 11 Aug 2000 10:43:07 -0700 (PDT) (envelope-from jonas.bulow@servicefactory.se) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id TAA22850 for ; Fri, 11 Aug 2000 19:43:03 +0200 (MET DST) Message-ID: <39943B24.90B7AB04@servicefactory.se> Date: Fri, 11 Aug 2000 19:43:00 +0200 From: Jonas Bulow Organization: Service Factory X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: hackers@FreeBSD.ORG Subject: Re: R. Stevens select() Collisions Scenario References: <39934E64.A5BEE8EE@earthlink.net> <20000810180838.V4854@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > Yes. :) When FreeBSD gets scheduler activations you'll be able to change > to a single threaded process that will have excellent performance, the > scheduler activations are just around the corner. Can you explain what scheduler activations are? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 10:47:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E0A137B568 for ; Fri, 11 Aug 2000 10:47:41 -0700 (PDT) (envelope-from jonas.bulow@servicefactory.se) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id TAA22957 for ; Fri, 11 Aug 2000 19:47:38 +0200 (MET DST) Message-ID: <39943C37.76D2DBCC@servicefactory.se> Date: Fri, 11 Aug 2000 19:47:36 +0200 From: Jonas Bulow Organization: Service Factory X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: IPC, shared memory, syncronization Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid race conditions, etc)? Right now I'm using posix semaphores but I would like to know if there is a substitute like the way kqueue is for select/poll. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 11: 7:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0FB8937B5A6; Fri, 11 Aug 2000 11:07:47 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA09441; Fri, 11 Aug 2000 12:07:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA35981; Fri, 11 Aug 2000 12:07:05 -0600 (MDT) Message-Id: <200008111807.MAA35981@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: ACPI project progress report (final?) Cc: wkb@freebie.demon.nl, mdharnois@home.com, freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org In-reply-to: Your message of "Sat, 12 Aug 2000 02:27:47 +0900." <20000812022747W.iwasaki@jp.FreeBSD.org> References: <20000812022747W.iwasaki@jp.FreeBSD.org> <868zu6uewj.fsf@mharnois.workgroup.net> <20000812003527P.iwasaki@jp.FreeBSD.org> <20000811185603.B7043@freebie.demon.nl> Date: Fri, 11 Aug 2000 12:07:05 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000812022747W.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes: : # I haven't checked ACPI spec 2.0 yet though :-) Wouldn't you know it. I printed the 1.0, and then the errata for it. Now I have to kill another couple of trees to print the 2.0 spec. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 11:13:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 6E75337B529 for ; Fri, 11 Aug 2000 11:13:53 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7BIDmG23728; Fri, 11 Aug 2000 11:13:48 -0700 (PDT) Date: Fri, 11 Aug 2000 11:13:48 -0700 From: Alfred Perlstein To: Jonas Bulow Cc: hackers@FreeBSD.ORG Subject: Re: R. Stevens select() Collisions Scenario Message-ID: <20000811111348.Z4854@fw.wintelcom.net> References: <39934E64.A5BEE8EE@earthlink.net> <20000810180838.V4854@fw.wintelcom.net> <39943B24.90B7AB04@servicefactory.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <39943B24.90B7AB04@servicefactory.se>; from jonas.bulow@servicefactory.se on Fri, Aug 11, 2000 at 07:43:00PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jonas Bulow [000811 10:45] wrote: > Alfred Perlstein wrote: > > Yes. :) When FreeBSD gets scheduler activations you'll be able to change > > to a single threaded process that will have excellent performance, the > > scheduler activations are just around the corner. > > Can you explain what scheduler activations are? Please CC. schedulder activations are like 'LWP on-demand' a really simplified explanation would be shared address space fork that only happens when you block in certain parts of the kernel, like during disk/io. the problem with normal LWP is that if you're going to do any sort of disk IO you really want an LWP _per_ disk bound thread otherwise you risk blocking on disk IO inside the kernel, scheduler activations make sure you almost never block as well as making it unnecessary to 'pre-allocate' LWP contexts to avoid such problems. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 11:27:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id E2E6037B6B2 for ; Fri, 11 Aug 2000 11:27:49 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id LAA15454; Fri, 11 Aug 2000 11:27:25 -0700 (PDT) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <399444C4.C0F4C02F@owp.csus.edu> Date: Fri, 11 Aug 2000 11:24:04 -0700 From: Joseph Scott X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Munehiro Matsuda Cc: taku@cent.saitama-u.ac.jp, julian@elischer.org, abc@bsdi.com, abial@webgiro.com, gandalf@vilnya.demon.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Maestro2E patch (Was: US$100 prize for adding ESSAudiodrivesupport to pcm) References: <39902AC7.CB39BCD8@owp.csus.edu> <20000811084827Y.haro@tk.kubota.co.jp> <39934AA4.5722D1C5@owp.csus.edu> <20000811143651N.haro@tk.kubota.co.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Munehiro Matsuda wrote: > > Hello Joseph, > > From: Joseph Scott > Date: Thu, 10 Aug 2000 17:36:52 -0700 > ::> I have created a patch that trys to enable internal speakers. > :: > :: The first part of the patch (for maestro.c) didn't apply cleanly for > ::me, so I ended up doing it by hand. > > Thats funny. Did you aply my patch to the original 20000725 version? Yes. I even went and redownloaded it to make sure. The first patch you included below didn't apply cleanly either. I applied it by hand again. > ::> It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works > ::> for everybody. Patch is based on Linux driver, but simplified. > ::> > ::> If it does not work, 1) try setting GPIO values to what your PC is at > ::> when rebooting from Windows, 2) try original way the Linux driver do. > ::> Let me know, if you want to know what Linux driver does. > :: > :: Unfortunately this didn't work for mine (Dell Inspiron 7500). How to > ::I find out the GPIO values that make windows work? I'm open to trying > ::what the Linux driver does. Mind you my C programing skills are > ::pretty much useless, but I'm willing to try things out :-) > > Aha, Dell Inspiron 7500! > There was some extra stuff in the Linux driver for it. > I have recreated my patch (mstr2_spk.patch2) to include them. > Please aply the new patch to the original 20000725 version source code! This seems to have to done the trick! I now get sound out of both internal speakers! Yeah!!!! > And also, I added a small patch (mstr2_gpio.patch) that should print > GPIO values. Aply GPIO patch after the mstr2_spk.patch2! I didn't try this patch since the first one got the speakers working. Would it be helpful to find out GPIO values at this point? If so let me know and I'll apply the patch and see what I get. Otherwise I'll just go with what I've got. > > Let me know how that works out. > > BTW, I'll be out of town for few days. So my reply may get delayed. sorry. > > Thank you, > Haro No problem. Thank you again, now I won't have to carry about headphones or external speakers with my notebook :-) -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 11:33:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 71BEB37B56D for ; Fri, 11 Aug 2000 11:33:08 -0700 (PDT) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id LAA28018 for ; Fri, 11 Aug 2000 11:33:11 -0700 (PDT) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id LAA27540 for ; Fri, 11 Aug 2000 11:25:37 -0700 (PDT) (envelope-from dbutter@wireless.net) Message-ID: <399446E0.D4F51CCA@wireless.net> Date: Fri, 11 Aug 2000 11:33:04 -0700 From: Devin Butterfield X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Need help with driver.... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I'm a newbie to device driver writing and I have been learning well by reading the code of the other drivers in the system. I would ultimately like to port a linux driver for a VoIP telephony card (Quicknet PhoneJack) to FreeBSD, and so far I have a skeleton driver which does successfully probe the card. The problem I'm having is that I don't know how to tell whether or not the card is attaching correctly. How can I determine this? I thought that I would be able to make a device file in /dev if it correctly attached but MAKEDEV responds with: {root@dbm /dev]# ./MAKEDEV phone phone - no such device name For reference, here is my attach routine: static int ixj_isa_attach (dev) /* attach device */ device_t dev; { int unit = device_get_unit(dev); struct ixj_softc *sc = device_get_softc(dev); struct resource *res; int rid; int size; if (sc->port_used > 0) { size = sc->port_used; rid = sc->port_rid; res = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0, ~0, size, RF_ACTIVE); if (res) { sc->port_rid = rid; sc->port_res = res; sc->port_used = size; } } make_dev(&ixj_cdevsw, UNIT(dev), UID_ROOT, GID_WHEEL, 0666, "phone%d", unit); return (0); } What am I doing wrong? How can I tell if this is working? Why can't I make the device file? Thanks in advance. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 15:11:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id D65EF37C228 for ; Fri, 11 Aug 2000 15:11:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.9.3/8.9.3) with ESMTP id PAA92911; Fri, 11 Aug 2000 15:11:06 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200008112211.PAA92911@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Yevmenkin, Maksim N, CSCIO" Cc: "'Frederik Meerwaldt'" , freebsd-hackers@FreeBSD.ORG Subject: Re: makeLINT.pl - Bug or am I just stupid In-Reply-To: Date: Fri, 11 Aug 2000 15:11:05 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Yevmenkin, Maksim N, CSCIO" wrote: > > [frederik@server conf]$ sh makeLINT.pl > > =0: not found > > makeLINT.pl: 5: Syntax error: redirection unexpected > > [frederik@server conf]$ > > try: > > perl makeLINT.pl < NOTES > > thanks, > emax or: make LINT which is easier still. :-) Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 15:24:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 1E7E837BCB7 for ; Fri, 11 Aug 2000 15:24:07 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA00839; Fri, 11 Aug 2000 15:35:30 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008112235.PAA00839@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Devin Butterfield Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Need help with driver.... In-reply-to: Your message of "Fri, 11 Aug 2000 11:33:04 PDT." <399446E0.D4F51CCA@wireless.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Aug 2000 15:35:30 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm a newbie to device driver writing and I have been learning well by > reading the code of the other drivers in the system. I would ultimately > like to port a linux driver for a VoIP telephony card (Quicknet > PhoneJack) to FreeBSD, and so far I have a skeleton driver which does > successfully probe the card. It does? How? Is this a PnP card? > The problem I'm having is that I don't know how to tell whether or not > the card is attaching correctly. How can I determine this? I thought > that I would be able to make a device file in /dev if it correctly > attached but MAKEDEV responds with: > > {root@dbm /dev]# ./MAKEDEV phone > phone - no such device name MAKEDEV is a script which does not interact with the kernel in any way. You need to explicitly update MAKEDEV to know about your device. > For reference, here is my attach routine: > > static int > ixj_isa_attach (dev) /* attach device */ > device_t dev; > { > int unit = device_get_unit(dev); > struct ixj_softc *sc = device_get_softc(dev); > struct resource *res; > int rid; > int size; > > if (sc->port_used > 0) { > size = sc->port_used; > rid = sc->port_rid; Where are you initialising these fields in the softc? (I assume, in your probe, correct?) > res = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, > 0, ~0, size, RF_ACTIVE); > if (res) { > sc->port_rid = rid; > sc->port_res = res; > sc->port_used = size; > } > > } > make_dev(&ixj_cdevsw, UNIT(dev), UID_ROOT, GID_WHEEL, > 0666, "phone%d", unit); > > return (0); > } > > > What am I doing wrong? How can I tell if this is working? You should check the return values from bus_alloc_resource and make_dev, both of which you need to save in the softc so that you can detach correctly. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 15:50:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F8AE37BC72 for ; Fri, 11 Aug 2000 15:50:32 -0700 (PDT) (envelope-from jonas.bulow@servicefactory.se) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id AAA27091 for ; Sat, 12 Aug 2000 00:50:29 +0200 (MET DST) Message-ID: <39948331.5E83DE1B@servicefactory.se> Date: Sat, 12 Aug 2000 00:50:26 +0200 From: Jonas Bulow X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: IPC, shared memory, syncronization References: <39943C37.76D2DBCC@servicefactory.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonas Bulow wrote: > > What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid > race conditions, etc)? Right now I'm using posix semaphores but I would > like to know if there is a substitute like the way kqueue is for > select/poll. Hmm, I think I lost some word and deeper thought in my previous mail. :-) The problem is as follows: I have a couple of processes using a mmap:ed file as common data area. What I want to do is to make it safe for all processes to update data in this common memory area. I was thinking about using some part of the common data area for semaphores in some way. I just want a simple "test-and-set" operation I can use to make sure there is only one process writing to the common data area. To take the "test-and-set" further, I would like to make the process wait for the lock to be released. Can anyone give me hint how this is best implemented with FreeBSD as OS? I apology if this is not a pure FreeBSD related question but I could not find a better forum for this question. I could only find out solutions based on posix semaphores. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 18:56:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from galima.2y.net (HSE-Toronto-ppp174193.sympatico.ca [64.229.66.100]) by hub.freebsd.org (Postfix) with ESMTP id 2B17437BA48 for ; Fri, 11 Aug 2000 18:56:27 -0700 (PDT) (envelope-from cactoss@yahoo.com) Received: from localhost (cactoss@localhost) by galima.2y.net (8.9.3/8.9.3) with ESMTP id VAA00691 for ; Fri, 11 Aug 2000 21:57:51 -0400 (EDT) (envelope-from cactoss@yahoo.com) X-Authentication-Warning: galima.2y.net: cactoss owned process doing -bs Date: Fri, 11 Aug 2000 21:57:50 -0400 (EDT) From: Alexander Anderson To: freebsd-hackers@freebsd.org Subject: localhost cannot be resolved Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone! I sent this question to freebsd-questions, but no one had replied, so I decided to try my luck here. I'm having trouble resolving "localhost" for telnet and fetchmail. All other programs (ftp, rlogin, rsh, ping, lynx) seem to understand "localhost". I'm going to include my configuration files. Please tell me if you'd like to get more info on something. > cat /etc/hosts 127.0.0.1 localhost localhost.my.domain myname.my.domain ::1 localhost localhost.my.domain myname.my.domain > cat /etc/host.conf hosts bind > cat /etc/resolv.conf nameserver 209.226.175.224 nameserver 204.101.251.2 All looks right, does it? Now, when I run telnet or fetchmail, they complain. > telnet localhost localhost: No address associated with hostname > echo $? 1 > fetchmail 9 messages for MYUSERNAME at pop.mail.yahoo.com (64648 octets). reading message 1 of 9 (13403 octets) .fetchmail: SMTP connect to localhost failed fetchmail: SMTP transaction error while fetching from pop.mail.yahoo.com fetchmail: Query status=SMTP > echo $? 10 At the same time fetchmail causes ipfw to produce these messages: Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from ::0001:1063 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1065 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from ::0001:1066 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1067 Actually, could someone tell me, what does ::0001 mean? Should this be in /etc/hosts with an alias of localhost? These strange things started to happen soon after I cvsup'ed ports-all and reinstalled libtool. I also compiled firewall support into the kernel a few days ago. Just in case any of this might be related to the problem. Thank you all for any suggestions! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 19:31: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 30C0337B666 for ; Fri, 11 Aug 2000 19:30:58 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA27044; Fri, 11 Aug 2000 19:30:48 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA60410; Fri, 11 Aug 2000 19:30:47 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 11 Aug 2000 19:30:47 -0700 (PDT) Message-Id: <200008120230.TAA60410@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jonas.bulow@servicefactory.se Subject: Re: IPC, shared memory, syncronization In-Reply-To: <39948331.5E83DE1B@servicefactory.se> References: <39943C37.76D2DBCC@servicefactory.se> <39948331.5E83DE1B@servicefactory.se> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <39948331.5E83DE1B@servicefactory.se>, Jonas Bulow wrote: > Jonas Bulow wrote: > > > > What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid > > race conditions, etc)? Right now I'm using posix semaphores but I would > > like to know if there is a substitute like the way kqueue is for > > select/poll. > > Hmm, I think I lost some word and deeper thought in my previous mail. > :-) > > The problem is as follows: > > I have a couple of processes using a mmap:ed file as common data area. > What I want to do is to make it safe for all processes to update data in > this common memory area. I was thinking about using some part of the > common data area for semaphores in some way. I just want a simple > "test-and-set" operation I can use to make sure there is only one > process writing to the common data area. If you want the "BSD way" you should probably create a 0-length temporary file somewhere and use the flock(2) system call on it. The file itself isn't important; it's just something to lock. Or you could use semop(2) on semaphores. But that's the SYSV way, not the BSD way. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 11 20: 3:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id AE20337B51F for ; Fri, 11 Aug 2000 20:03:57 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id VAA545802; Fri, 11 Aug 2000 21:03:53 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id VAA06789; Fri, 11 Aug 2000 21:03:53 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Fri, 11 Aug 2000 21:03:53 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: hackers@FreeBSD.ORG Cc: jonas.bulow@servicefactory.se Subject: Re: IPC, shared memory, syncronization In-Reply-To: <200008120230.TAA60410@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Aug 2000, John Polstra wrote: > In article <39948331.5E83DE1B@servicefactory.se>, > Jonas Bulow wrote: > > Jonas Bulow wrote: > > > > > > What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid > > > race conditions, etc)? Right now I'm using posix semaphores but I would > > > like to know if there is a substitute like the way kqueue is for > > > select/poll. I don't know about the "bsd" or whatever way. If you're doing real parallel programming and want real performance, you'll use a test-and-set like function that uses the low-level machine instructions for same. I do have one of these (posted to this list about 6 years ago) if you want it. uses any kind of system call or flock for high performance programs will not work well. It's ok if you need to synchronize access every minute or so ... ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 0:41:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id D783137B87F for ; Sat, 12 Aug 2000 00:41:38 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id e7C6e5214161; Sat, 12 Aug 2000 15:40:05 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:PyIpMsRvogWwjShDByyquCfZpKtv8xsGMPNtzUh8B8q9dwjhpcjPx3Xg6nHEWJjy@peace.mahoroba.org [2001:200:301:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.10.2/8.10.2/chaos) with ESMTP/inet6 id e7C6cM027572; Sat, 12 Aug 2000 15:38:22 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 12 Aug 2000 15:38:21 +0900 (JST) Message-Id: <20000812.153821.102583385.ume@mahoroba.org> To: cactoss@yahoo.com Cc: freebsd-hackers@freebsd.org Subject: Re: localhost cannot be resolved From: Hajimu UMEMOTO In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Fri, 11 Aug 2000 21:57:50 -0400 (EDT) >>>>> Alexander Anderson said: cactoss> I'm having trouble resolving "localhost" for telnet and fetchmail. All cactoss> other programs (ftp, rlogin, rsh, ping, lynx) seem to understand cactoss> "localhost". Which version of FreeBSD are you using? cactoss> I'm going to include my configuration files. Please tell me if you'd like cactoss> to get more info on something. cactoss> > cat /etc/hosts cactoss> 127.0.0.1 localhost localhost.my.domain myname.my.domain cactoss> ::1 localhost localhost.my.domain myname.my.domain cactoss> > cat /etc/host.conf cactoss> hosts cactoss> bind cactoss> > cat /etc/resolv.conf cactoss> nameserver 209.226.175.224 cactoss> nameserver 204.101.251.2 cactoss> All looks right, does it? It seems right for me. cactoss> Now, when I run telnet or fetchmail, they complain. > telnet localhost cactoss> localhost: No address associated with hostname > echo $? cactoss> 1 It seems getaddrinfo(3) was failed. What's curious. Rlogin, rsh and ftp call getaddrinfo(3), too. Why is it only telnet and fetchmail? cactoss> > fetchmail cactoss> 9 messages for MYUSERNAME at pop.mail.yahoo.com (64648 octets). cactoss> reading message 1 of 9 (13403 octets) .fetchmail: SMTP connect to cactoss> localhost failed cactoss> fetchmail: SMTP transaction error while fetching from pop.mail.yahoo.com cactoss> fetchmail: Query status=SMTP > echo $? cactoss> 10 cactoss> At the same time fetchmail causes ipfw to produce these messages: cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from cactoss> ::0001:1063 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 cactoss> from 127.0.0.1:1065 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from cactoss> ::0001:1066 cactoss> Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 cactoss> from 127.0.0.1:1067 You don't have SMTP/IPv6 listen. This should be OK. So, SMTP connection to ::1 was fail. Then, SMTP connection to 127.0.0.1 was tried. It seems IDENT query was made in correspondings to SMTP connection to 127.0.0.1. I think you have SMTP/IPv4 listen. cactoss> Actually, could someone tell me, what does ::0001 mean? Should this be in cactoss> /etc/hosts with an alias of localhost? ::0001 is same as ::1. Leading zero can be omittled in IPv6 address format. cactoss> These strange things started to happen soon after I cvsup'ed ports-all and cactoss> reinstalled libtool. I also compiled firewall support into the kernel a cactoss> few days ago. Just in case any of this might be related to the problem. I think libtool has no relation with this problem. It may rely on firewall rule. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 2:18:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id 75D9537BD1A for ; Sat, 12 Aug 2000 02:18:44 -0700 (PDT) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id TAA21483 for hackers@freebsd.org; Sat, 12 Aug 2000 19:18:39 +1000 (EST) From: Darren Reed Message-Id: <200008120918.TAA21483@cairo.anu.edu.au> Subject: Breaking kernel compiles. To: hackers@freebsd.org Date: Sat, 12 Aug 2000 19:18:39 +1000 (Australia/NSW) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an attempt to do the right thing, I checked out sys and config'd a kernel and went to compile (on builder, as it were)... cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I/usr/include -D_KERNEL -include opt_global.h -elf -mp referred-stack-boundary=2 ../../kern/kern_sig.c ../../kern/kern_sig.c:359: warning: function declaration isn't a prototype ../../kern/kern_sig.c: In function `osigaction': ../../kern/kern_sig.c:367: dereferencing pointer to incomplete type ../../kern/kern_sig.c:367: dereferencing pointer to incomplete type ../../kern/kern_sig.c:369: dereferencing pointer to incomplete type ../../kern/kern_sig.c:370: dereferencing pointer to incomplete type ../../kern/kern_sig.c:372: dereferencing pointer to incomplete type ../../kern/kern_sig.c:379: dereferencing pointer to incomplete type ../../kern/kern_sig.c:384: dereferencing pointer to incomplete type ../../kern/kern_sig.c: At top level: ../../kern/kern_sig.c:532: warning: function declaration isn't a prototype ../../kern/kern_sig.c: In function `osigprocmask': ../../kern/kern_sig.c:538: dereferencing pointer to incomplete type ../../kern/kern_sig.c:539: dereferencing pointer to incomplete type ../../kern/kern_sig.c: At top level: ../../kern/kern_sig.c:567: warning: function declaration isn't a prototype ../../kern/kern_sig.c:721: warning: function declaration isn't a prototype ../../kern/kern_sig.c: In function `osigsuspend': ../../kern/kern_sig.c:729: dereferencing pointer to incomplete type Did I do something wrong or are kernel compiles breaking not really that irregular ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 3:17:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id C704C37BC4E for ; Sat, 12 Aug 2000 03:17:37 -0700 (PDT) (envelope-from jonas.bulow@servicefactory.se) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id MAA06241; Sat, 12 Aug 2000 12:17:30 +0200 (MET DST) Message-ID: <39952437.EFCAA381@servicefactory.se> Date: Sat, 12 Aug 2000 12:17:27 +0200 From: Jonas Bulow X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Ronald G Minnich Cc: hackers@FreeBSD.ORG Subject: Re: IPC, shared memory, syncronization References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ronald G Minnich wrote: > On Fri, 11 Aug 2000, John Polstra wrote: > > In article <39948331.5E83DE1B@servicefactory.se>, > > Jonas Bulow wrote: > > > Jonas Bulow wrote: > > > > > > > > What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid > > > > race conditions, etc)? Right now I'm using posix semaphores but I would > > > > like to know if there is a substitute like the way kqueue is for > > > > select/poll. > > I don't know about the "bsd" or whatever way. If you're doing real > parallel programming and want real performance, you'll use a test-and-set > like function that uses the low-level machine instructions for same. That is exacly what I'm looking for! I found it to be overkill to involve the kernel just because I wanted to have a context switch during the "test-and-set". > > I do have one of these (posted to this list about 6 years ago) if you want > it. I tried to find it but didn't have any luck. Maybe you can point me to it? /jcb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 4:14:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id E729E37BCD5; Sat, 12 Aug 2000 04:14:32 -0700 (PDT) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id EAA02671; Sat, 12 Aug 2000 04:14:33 -0700 (PDT) Received: from wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with ESMTP id EAA35348; Sat, 12 Aug 2000 04:07:07 -0700 (PDT) (envelope-from dbutter@wireless.net) Message-ID: <39953196.1103F555@wireless.net> Date: Sat, 12 Aug 2000 04:14:30 -0700 From: Devin Butterfield X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Need help with driver....(long) References: <200008112235.PAA00839@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I'm a newbie to device driver writing and I have been learning well by > > reading the code of the other drivers in the system. I would ultimately > > like to port a linux driver for a VoIP telephony card (Quicknet > > PhoneJack) to FreeBSD, and so far I have a skeleton driver which does > > successfully probe the card. > > It does? How? Is this a PnP card? Yes, it is a PnP card. > MAKEDEV is a script which does not interact with the kernel in any way. > You need to explicitly update MAKEDEV to know about your device. Ok, thanks for clearing that up. :) > Where are you initialising these fields in the softc? (I assume, in your > probe, correct?) > Well, I think I'm initializing it correctly...see below. > You should check the return values from bus_alloc_resource and make_dev, > both of which you need to save in the softc so that you can detach > correctly. Ok, I'll try this... One thing I did try, was to write a very simple program to open the device (now that I have correctly created the node in /dev) and I inserted a printf in my ixj_open() in the driver to indicate that it entered the open function...and this does seem to work. If open succeeds, can I safely conclude that I'm doing things right? On another note, I also compiled my skeleton driver as a module and it loads ok, but if I try to use my little program to open the device, it fails. I then tried inserting printf's in the probe and attach functions, but when I load the module I still don't get any output. It doesn't seem the driver probes or attaches if I load it as a module. What am I doing wrong? Below is the skeleton driver. I apologize if posting the entire thing was inappropriate, but this way you guys can see exactly what I'm doing, and more specifically, what I'm doing wrong. ;) Thanks again. -- Regards, Devin. #include #include #include #include #include #include #include #include #include #include #include #include #include /* more ISA stuff... */ struct ixj_softc { /* param struct per a dev. */ dev_t dev; int port_rid; /* resource id for port range */ int port_used; /* nonzero if ports used */ struct resource* port_res; /* resource for port range */ }; /* Function prototypes */ static devclass_t ixj_isa_devclass; static int ixj_isa_probe(device_t dev); static int ixj_isa_attach(device_t dev); static int ixj_isa_detach(device_t dev); static d_open_t ixj_open; static d_close_t ixj_close; static d_read_t ixj_read; static d_write_t ixj_write; static d_ioctl_t ixj_ioctl; #define CDEV_MAJOR 100 #define NIXJ 16 static struct cdevsw ixj_cdevsw = { ixj_open, /* open */ ixj_close, /* close */ ixj_read, /* read */ ixj_write, /* write */ ixj_ioctl, /* ioctl */ nopoll, nommap, nostrategy, "ixj", /* name */ CDEV_MAJOR, /* major */ nodump, nopsize, 0, -1 /* bmaj */ }; /* Possible Vendor ID's */ /* add ID's for all cards here */ static struct isa_pnp_id ixj_ids[] = { { 0x10048946, "QTI0400 Internet PhoneJack" }, /* QTI0400 */ { 0, NULL } }; static int ixj_isa_probe(device_t dev) /* isapnp probe */ { struct ixj_softc *sc = device_get_softc(dev); /* initialize softc */ bzero(sc, sizeof(struct ixj_softc)); /* get value from pnp probe */ if(ISA_PNP_PROBE(device_get_parent(dev), dev, ixj_ids) == ENXIO) return ENXIO; return (0); } static int ixj_isa_attach (device_t dev) /* attach device */ { /* int unit = device_get_unit(dev); */ struct ixj_softc *sc = device_get_softc(dev); struct resource *res; int rid; int size; printf("attaching device.\n"); if (sc->port_used > 0) { size = sc->port_used; rid = sc->port_rid; res = bus_alloc_resource(dev, SYS_RES_IOPORT, &rid, 0ul, ~0ul, size, RF_ACTIVE); if (res) { sc->port_rid = rid; sc->port_res = res; sc->port_used = size; } } sc->dev = make_dev(&ixj_cdevsw, 0, UID_ROOT, GID_WHEEL, 0666, "phone0"); return (0); } static int ixj_isa_detach (dev) /* detach device */ device_t dev; { struct ixj_softc *sc = device_get_softc(dev); /* release io resources */ bus_release_resource(dev, SYS_RES_IOPORT, sc->port_rid, sc->port_res); return (0); } static device_method_t ixj_isa_methods[] = { /* Device interface */ DEVMETHOD(device_probe, ixj_isa_probe), DEVMETHOD(device_attach, ixj_isa_attach), DEVMETHOD(device_detach, ixj_isa_detach), { 0, 0 } }; static driver_t ixj_isa_driver = { "ixj", ixj_isa_methods, sizeof(struct ixj_softc) }; static int ixj_open(dev_t dev, int oflags, int devtype, struct proc *p) { /* do stuff here */ printf("Phone device successfully opened.\n"); return (0); } static int ixj_close(dev_t dev, int fflag, int devtype, struct proc *p) { /* do stuff here */ printf("Phone device successfully closed.\n"); return (0); } static int ixj_read(dev_t dev, struct uio *uio, int ioflag) { /* do stuff here */ return (0); } static int ixj_write(dev_t dev, struct uio *uio, int ioflag) { /* do stuff here */ return (0); } static int ixj_ioctl (dev_t dev, u_long cmd, caddr_t data, int flag, struct proc *p) { /* do stuff here */ return (0); } DRIVER_MODULE(ixj, isa, ixj_isa_driver, ixj_isa_devclass, 0, 0); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 4:27:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id EF6A637BCE1 for ; Sat, 12 Aug 2000 04:27:45 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id C119BA84B; Sat, 12 Aug 2000 21:28:44 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id B71CA544C for ; Sat, 12 Aug 2000 21:28:44 +1000 (EST) Date: Sat, 12 Aug 2000 21:28:44 +1000 (EST) From: andrew@ugh.net.au To: freebsd-hackers@freebsd.org Subject: libvgl: free(): warning: junk pointer, too high to make sense. Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using libvgl but when I call VGLTextSetFontFile(FONT) I get: free(): warning: junk pointer, too high to make sense. What am I doing wrong? The only other vgl call I have made at this point is VGLInit. Also what sort of file is it after? I guessed one of the fonts in /usr/share/syscons/fonts/ after uudecoding... BTW not all fonts in there have $FreeBSD$ lines...I'm not sure if thats deliberate or not... Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 4:40:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kwanon.research.canon.com.au (kwanon.research.canon.com.au [203.12.172.254]) by hub.freebsd.org (Postfix) with ESMTP id EF0B037BCE1 for ; Sat, 12 Aug 2000 04:40:25 -0700 (PDT) (envelope-from iain@research.canon.com.au) Received: from bellmann.research.canon.com.au (bellmann.research.canon.com.au [10.5.0.3]) by kwanon.research.canon.com.au (Postfix) with ESMTP id 7B09F8A890; Sat, 12 Aug 2000 11:43:35 +0000 (UTC) Received: from elph.research.canon.com.au (elph.research.canon.com.au [203.12.174.253]) by bellmann.research.canon.com.au (Postfix) with ESMTP id 2FB638B10; Sat, 12 Aug 2000 21:36:00 +1000 (EST) Received: from elph.research.canon.com.au (elph.research.canon.com.au [10.2.0.253]) by elph.research.canon.com.au (Postfix) with ESMTP id 22FF1208; Sat, 12 Aug 2000 21:40:00 +1000 (EST) Date: Sat, 12 Aug 2000 21:40:00 +1000 (EST) From: Iain Templeton To: andrew@ugh.net.au Cc: freebsd-hackers@freebsd.org Subject: Re: libvgl: free(): warning: junk pointer, too high to make sense. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000 andrew@ugh.net.au wrote: > Hi, > Hi Andrew :-) > I'm using libvgl but when I call VGLTextSetFontFile(FONT) I get: > > free(): warning: junk pointer, too high to make sense. > > What am I doing wrong? The only other vgl call I have made at this point > is VGLInit. > Well, VGLInit() calls VGLTextSetFontFile((byte *)0) We see in VGLTextSetFontFile() that if (filename==NULL) { VGLTextFont->Width = 8; VGLTextFont->Height = 8; VGLTextFont->BitmapArray = VGLFont; } But I think that when you call VGLTextSetFontFile() later you'll run the code at the beginning of the function if (VGLTextFont) { if (VGLTextFont->BitmapArray) free (VGLTextFont->BitmapArray); <--- This Line free(VGLTextFont); } So what I suspect might be happening is that its the free() of the line marked above thats failing, because it is trying to free something at the address of VGLFont, which is a global array within libvgl.a. Using gdb on the program should make it possible to confirm that or not. As for how to get around it, I would say that this is a bug in libvgl. > Also what sort of file is it after? I guessed one of the fonts in > /usr/share/syscons/fonts/ after uudecoding... > I think it might be. It reads the first 2 characters as width and height, then the rest seems to be raw font data, which is read into memory, not sure of the format other than that though. Iain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 5:29:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from oden.exmandato.se (oden.exmandato.se [192.71.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 5770E37B891 for ; Sat, 12 Aug 2000 05:29:20 -0700 (PDT) (envelope-from jonas.bulow@servicefactory.se) Received: from servicefactory.se (root@oden.exmandato.se [192.71.33.1]) by oden.exmandato.se (8.8.8/8.8.5) with ESMTP id OAA06989 for ; Sat, 12 Aug 2000 14:29:17 +0200 (MET DST) Message-ID: <3995431A.324F8C89@servicefactory.se> Date: Sat, 12 Aug 2000 14:29:14 +0200 From: Jonas Bulow X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: IPC, shared memory, syncronization References: <39943C37.76D2DBCC@servicefactory.se> <39948331.5E83DE1B@servicefactory.se> <200008120230.TAA60410@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > If you want the "BSD way" you should probably create a 0-length > temporary file somewhere and use the flock(2) system call on it. The > file itself isn't important; it's just something to lock. I don't see any reason to do system calls just because I want to do an atomic operation (i.e aquire/release a lock). I found some really good code (:-)) in /usr/src/libexec/rtld-elf/i386/lockdflt.c that seems to do what I want. It's more the "i386"-way than the BSD-way. Maybe I havn't been thinking enough but wouldn't this lock mechanism be a good choice to use for mmaped:memory accessed by multiple processes? In lock_create the lock is aligned to CACHE_LINE_SIZE. Why is that important? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 6: 2:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 175CE37BD64 for ; Sat, 12 Aug 2000 06:02:13 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny7-11.ix.netcom.com [198.211.17.139]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA11418; Sat, 12 Aug 2000 09:02:10 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id JAA00442; Sat, 12 Aug 2000 09:02:02 -0400 (EDT) (envelope-from vns) Date: Sat, 12 Aug 2000 09:02:02 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200008121302.JAA00442@jupiter.delta.ny.us> To: dbutter@wireless.net Cc: freebsd-hackers@freebsd.org Subject: Re: Need help with driver....(long) In-Reply-To: <39953196.1103F555@wireless.net> References: <200008112235.PAA00839@mass.osd.bsdi.com> <39953196.1103F555@wireless.net> Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In muc.lists.freebsd.hackers, you wrote: >One thing I did try, was to write a very simple program to open the >device You can (should) just use echo -n >device_file, that's it. BTW for testing purpose it doesn't required to put now in the /dev directory, /dev doesn't mean nothing magical. >(now that I have correctly created the node in /dev) and I >inserted a printf in my ixj_open() in the driver to indicate that it >entered the open function...and this does seem to work. If open >succeeds, can I safely conclude that I'm doing things right? That's just means that you are able to find your card in ISA bus. >On another note, I also compiled my skeleton driver as a module and it >loads ok, but if I try to use my little program to open the device, it >fails. I then tried inserting printf's in the probe and attach >functions, but when I load the module I still don't get any output. It >doesn't seem the driver probes or attaches if I load it as a module. How you are compiled your driver as a module. You should to use Makefile like that: -=-=-=-=-=-- NOMAN= YES KMOD= ixj SRCS= ixj.c device_if.h bus_if.h isa_if.h .include -=-=-=-=-=-- What FreeBSD version you are using now? -- Vladimir P.S. The line sc->dev = make_dev(&ixj_cdevsw, 0, UID_ROOT, GID_WHEEL, 0666, "phone0"); better to rewrite as int unit = device_get_unit(dev); ... "ilx%d", unit), and after that to check the value of sc->dev. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 6: 8:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id 110D637BD7B for ; Sat, 12 Aug 2000 06:08:14 -0700 (PDT) (envelope-from vns@mindspring.com) Received: from jupiter.delta.ny.us (nyf-ny7-11.ix.netcom.com [198.211.17.139]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA05766; Sat, 12 Aug 2000 09:08:02 -0400 (EDT) Received: (from vsilyaev@localhost) by jupiter.delta.ny.us (8.9.3/8.9.3) id JAA00456; Sat, 12 Aug 2000 09:07:55 -0400 (EDT) (envelope-from vns) Date: Sat, 12 Aug 2000 09:07:55 -0400 (EDT) From: "Vladimir N.Silyaev" Message-Id: <200008121307.JAA00456@jupiter.delta.ny.us> To: jkruger@oskar.dev.nanoteq.co.za Cc: freebsd-hackers@freebsd.org Subject: Re: Using libvgl in single user mode - HOW ? In-Reply-To: References: Reply-To: vns@delta.odessa.ua Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In muc.lists.freebsd.hackers, you wrote: > >It works great, can now use perl to write a custom installation for my allready >made custom installation CD. >My problem is : > When i boot from CD, i go into single user mode, to partition the disks > and if you do a 'tty' you get /dev/console > while in multi usermode if you do a 'tty' you get /dev/ttyv0 > >LIBVGL works on tty's and not on /dev/console, so my program does'nt want to >initialize the graphics mode in single user mode. LIBVGL use stdin as handle to device, if you want to be sure, that you are using vty with number n, you should start you application as 'coolinstall ; Sat, 12 Aug 2000 07:46:19 -0700 (PDT) (envelope-from cactoss@galima.2y.net) Received: (from cactoss@localhost) by galima.2y.net (8.9.3/8.9.3) id KAA03691; Sat, 12 Aug 2000 10:47:43 -0400 (EDT) (envelope-from cactoss) Date: Sat, 12 Aug 2000 10:47:43 -0400 (EDT) From: Alexander Anderson Message-Id: <200008121447.KAA03691@galima.2y.net> To: freebsd-hackers@freebsd.org Subject: Re: localhost cannot be resolved In-Reply-To: <8n2v5k$kjv$1@FreeBSD.csie.NCTU.edu.tw> References: <8n2v5k$kjv$1@FreeBSD.csie.NCTU.edu.tw> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Which version of FreeBSD are you using? 4.0-RELEASE > > telnet localhost > cactoss> localhost: No address associated with hostname > > echo $? > cactoss> 1 > > It seems getaddrinfo(3) was failed. > What's curious. Rlogin, rsh and ftp call getaddrinfo(3), too. Why is > it only telnet and fetchmail? I tried to look at the sources for telnet. In file commands.c:2292, there's an assignment of variable "family". I couldn't understand where the variable is coming from. Still, I wrote a simple program to see under what circumstances getaddrinfo fails for localhost. It doesn't seem to fail at all?!.. #include #include #include #include #include int main( int argc, char** argv ) { struct addrinfo hints, *res; int status; if ( argc != 2 ) { fprintf( stderr, "usage: %s hostname\n", argv[0] ); exit(2); } memset( &hints, 0, sizeof(hints) ); /*hints.ai_flags = AI_NUMERICHOST;*/ /*hints.ai_flags = AI_PASSIVE;*/ hints.ai_flags = AI_CANONNAME; /*hints.ai_family = PF_UNSPEC;*/ hints.ai_family = AF_INET6; hints.ai_socktype = SOCK_STREAM; status = getaddrinfo( argv[1], "telnet", &hints, &res ); if ( status == 0 ) { printf( "success\n" ); } else { fprintf( stderr, "%s\n", gai_strerror( status ) ); } return 0; } [skipped] > You don't have SMTP/IPv6 listen. This should be OK. > So, SMTP connection to ::1 was fail. Then, SMTP connection to > 127.0.0.1 was tried. > It seems IDENT query was made in correspondings to SMTP connection to > 127.0.0.1. I think you have SMTP/IPv4 listen. Yes, sendmail is listening on port 25. I can telnet 127.0.0.1 25. Could you please take a look at `ifconfig lo0`: lo0: flags=8049 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 Does it look okay? [skipped] > I think libtool has no relation with this problem. It may rely on > firewall rule. My firewall is open. I decided that I'd only block certain ports: # ipfw show 00100 560 33466 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 21 924 allow tcp from any to any 25 via tun0 setup 00400 57 2524 allow tcp from any to any 80 via tun0 setup 00500 10 424 deny tcp from any to any 1-1024 in recv tun0 00600 68 2860 deny tcp from any 1-1024 to any out xmit tun0 00700 0 0 deny tcp from any to any 6000-6063 in recv tun0 00800 0 0 deny tcp from any 6000-6063 to any out xmit tun0 00900 0 0 deny tcp from any to any 3306 in recv tun0 01000 0 0 deny tcp from any 3306 to any out xmit tun0 65000 4982 1773612 allow ip from any to any 65535 0 0 deny ip from any to any I also tried flushing all the rules and allowing all traffic to see whether the firewall was the cause of my problem. I didn't change anything, so I doubt it is the firewall. One question. Firewall rules apply to both IPv4 and IPv6, right? There shouldn't be separate rules to IPv6, should there? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 8:29:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 74F0537BE2A for ; Sat, 12 Aug 2000 08:29:27 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:qzZJQaBP1p04i7YYjdRyAhYtdVilZX+XnbVNqiTXRZrB1ffu3KodTrOvvlaa7nDX@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/8.11.0/peace) with ESMTP/inet6 id e7CFQDu08614; Sun, 13 Aug 2000 00:26:13 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 13 Aug 2000 00:26:10 +0900 (JST) Message-Id: <20000813.002610.88470063.ume@mahoroba.org> To: cactoss@galima.2y.net Cc: freebsd-hackers@freebsd.org Subject: Re: localhost cannot be resolved From: Hajimu UMEMOTO In-Reply-To: <200008121447.KAA03691@galima.2y.net> References: <8n2v5k$kjv$1@FreeBSD.csie.NCTU.edu.tw> <200008121447.KAA03691@galima.2y.net> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Sat, 12 Aug 2000 10:47:43 -0400 (EDT) >>>>> Alexander Anderson said: > Which version of FreeBSD are you using? cactoss> 4.0-RELEASE Please update to 4.1-RELEASE. 4.0-RELEASE's getaddrinfo(3) has DNS query order problem and it was fixed in 4.1-RELEASE. Or, at least you should update libc/net/getaddrinfo.c and libc/net/name6.c I don't know why getaddrinfo(3) fails for localhost query, exactly. However, probably updating to 4.1-RELEASE fixes your problem. cactoss> I tried to look at the sources for telnet. In file commands.c:2292, there's cactoss> an assignment of variable "family". I couldn't understand where the variable cactoss> is coming from. The variable `family' is came from command line of telnet. If -4 is specified, telnet tries only AF_INET. If -6 is specified, telnet tries only AF_INET6. Default is AF_UNSPEC, that is try both IPv6 and IPv4. cactoss> Could you please take a look at `ifconfig lo0`: cactoss> lo0: flags=8049 mtu 16384 cactoss> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 cactoss> inet6 ::1 prefixlen 128 cactoss> inet 127.0.0.1 netmask 0xff000000 cactoss> Does it look okay? It seems fine. cactoss> One question. Firewall rules apply to both IPv4 and IPv6, right? There cactoss> shouldn't be separate rules to IPv6, should there? No. Rules for IPv6 is set separately by ip6fw. Firewall for IPv6 is enabled by specifying `options IPV6FIREWALL' in your kernel config. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 9:40:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EAD1B37B7BF for ; Sat, 12 Aug 2000 09:39:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA01686; Sat, 12 Aug 2000 09:39:54 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA63479; Sat, 12 Aug 2000 09:39:54 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sat, 12 Aug 2000 09:39:54 -0700 (PDT) Message-Id: <200008121639.JAA63479@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jonas.bulow@servicefactory.se Subject: Re: IPC, shared memory, syncronization In-Reply-To: <3995431A.324F8C89@servicefactory.se> References: <39943C37.76D2DBCC@servicefactory.se> <39948331.5E83DE1B@servicefactory.se> <200008120230.TAA60410@vashon.polstra.com> <3995431A.324F8C89@servicefactory.se> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3995431A.324F8C89@servicefactory.se>, Jonas Bulow wrote: > John Polstra wrote: > > If you want the "BSD way" you should probably create a 0-length > > temporary file somewhere and use the flock(2) system call on it. The > > file itself isn't important; it's just something to lock. > > I don't see any reason to do system calls just because I want to do an > atomic operation (i.e aquire/release a lock). Fair enough. It's a trade-off between simplicity and overhead and it depends also on the amount of contention you expect for the locks. > I found some really good code (:-)) in > /usr/src/libexec/rtld-elf/i386/lockdflt.c :-) > that seems to do what I want. It's more the "i386"-way than the > BSD-way. Well, there is alpha code there too. :-) > Maybe I havn't been thinking enough but wouldn't this lock mechanism > be a good choice to use for mmaped:memory accessed by multiple > processes? It depends on the amount of contention you expect. The code in lockdflt.c was designed for a very low-contention situation (usually no contention at all). It also had to work in a very restrictive environment where the threads package was unknown and could be practically anything. Also it was designed to do locking between two threads running in the same process, which is not the problem you're trying to solve. Your environment is much more controlled, so you can probably do better. I think the ideal solution would first try to lock the test-and-set lock, maybe spinning on it just a few times. If that failed it would fall back to using a system-call lock such as flock() which would allow the process to block without spinning. But I don't have any code to do that. (If you write some, could I have a copy?) > In lock_create the lock is aligned to CACHE_LINE_SIZE. Why is that > important? It's just more efficient that way. The spinlock tends to hammer the cache line containing the lock (i.e., invalidate the whole line over and over). If anything else is also accessing the same cache line, there is a big performance penalty. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 10:39:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 82E1D37B69D; Sat, 12 Aug 2000 10:39:43 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sat, 12 Aug 2000 13:39:42 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Jonas Bulow Cc: hackers@freebsd.org Subject: Re: IPC, shared memory, syncronization In-Reply-To: <3995431A.324F8C89@servicefactory.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000, Jonas Bulow wrote: > John Polstra wrote: > > If you want the "BSD way" you should probably create a 0-length > > temporary file somewhere and use the flock(2) system call on it. The > > file itself isn't important; it's just something to lock. > > I don't see any reason to do system calls just because I want to do an > atomic operation (i.e aquire/release a lock). > > I found some really good code (:-)) in > /usr/src/libexec/rtld-elf/i386/lockdflt.c that seems to do what I want. > It's more the "i386"-way than the BSD-way. Maybe I havn't been thinking > enough but wouldn't this lock mechanism be a good choice to use for > mmaped:memory accessed by multiple processes? I was just going to suggest this =) The best way to go about this method is, IMHO, to map a range of memory you'll get "locks" from and use that as a zone-type allocator. For the most part, you can reuse lockdflt.c for the i386 and alpha archs and it will probably work well :) The caveats are that you need to have mmap()-shared locks themselves, if you're not threaded you'll probably want to take all the signal-related stuff out. If you don't need shared locks, you can simplify things by just using machdep cmpxchgl() and cmp0_and_store_int() routines, along with probably wanted to do a nanosleep() like the rtld-elf code, too. I assume if you were doing things with threads, you'd be using the pthread_mutex_t routines, of course ;) > In lock_create the lock is aligned to CACHE_LINE_SIZE. Why is that > important? I'm thinking it's to keep things in one line of the data cache so as to not impact performance more than necessary. I didn't really pay attention to this part of the implementation, but it makes sense to me :) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 11:48:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id C5F0037B9D6 for ; Sat, 12 Aug 2000 11:48:24 -0700 (PDT) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7CJ3F310720 for ; Sat, 12 Aug 2000 12:03:15 -0700 (PDT) Date: Sat, 12 Aug 2000 12:03:15 -0700 (PDT) From: FengYue To: hackers@FreeBSD.ORG Subject: ipfw drop packets based on SYN &TTL In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need to drop packets using ipfw based on the value of TTL and the value of TTL on a 2.2.8-stable system. It seems ipfw does not support this, what options do I have? thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 11:51:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 1F8D237BC6A for ; Sat, 12 Aug 2000 11:51:36 -0700 (PDT) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7CJ6Ox10729 for ; Sat, 12 Aug 2000 12:06:24 -0700 (PDT) Date: Sat, 12 Aug 2000 12:06:24 -0700 (PDT) From: FengYue To: hackers@FreeBSD.ORG Subject: Re: ipfw drop packets based on SYN &TTL In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000, FengYue wrote: > > Hi, I need to drop packets using ipfw based on the value of > TTL and the value of TTL on a 2.2.8-stable system. It seems ^^^ I meant SYN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:12:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C678A37B915 for ; Sat, 12 Aug 2000 14:12:11 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA22358 for ; Sat, 12 Aug 2000 17:14:28 -0400 (EDT) Message-Id: <200008122114.RAA22358@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 12 Aug 2000 17:27:07 -0400 To: hackers@freebsd.org From: Dennis Subject: vmstat and top failing in 4.1-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ETR1500# vmstat -i vmstat: undefined symbols: _cp_time _kmemstatistics _bucket _zlist ETR1500# top top: nlist failed I have the same kernel config on another machine and all works fine. What could it be? Thanks, Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:16:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 8CE2A37B530 for ; Sat, 12 Aug 2000 14:16:39 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id AA7815D4E; Sat, 12 Aug 2000 23:16:35 +0200 (CEST) Date: Sat, 12 Aug 2000 23:16:35 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Dennis Cc: hackers@freebsd.org Subject: Re: vmstat and top failing in 4.1-STABLE In-Reply-To: <200008122114.RAA22358@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ETR1500# vmstat -i > vmstat: undefined symbols: > _cp_time _kmemstatistics _bucket _zlist > ETR1500# top > top: nlist failed > > > I have the same kernel config on another machine and all works fine. What > could it be? Do you by any chance boot the kernel directly, instead of using /boot/loader? Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:20:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2CC8E37B7D5 for ; Sat, 12 Aug 2000 14:20:36 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA22401; Sat, 12 Aug 2000 17:22:57 -0400 (EDT) Message-Id: <200008122122.RAA22401@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 12 Aug 2000 17:35:35 -0400 To: Blaz Zupan From: Dennis Subject: Re: vmstat and top failing in 4.1-STABLE Cc: hackers@freebsd.org In-Reply-To: References: <200008122114.RAA22358@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:16 PM 8/12/00 +0200, Blaz Zupan wrote: >> ETR1500# vmstat -i >> vmstat: undefined symbols: >> _cp_time _kmemstatistics _bucket _zlist >> ETR1500# top >> top: nlist failed >> >> >> I have the same kernel config on another machine and all works fine. What >> could it be? > >Do you by any chance boot the kernel directly, instead of using /boot/loader? Im not sure what you mean, but the machine that is having the problem is using the old-style boot loader from 3.x days. What is the issue? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:34: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 8D1D837B915 for ; Sat, 12 Aug 2000 14:34:05 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 8E3221C4D; Sat, 12 Aug 2000 17:34:04 -0400 (EDT) Date: Sat, 12 Aug 2000 17:34:04 -0400 From: Bill Fumerola To: FengYue Cc: hackers@FreeBSD.ORG Subject: Re: ipfw drop packets based on SYN &TTL Message-ID: <20000812173404.F65562@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from fengyue@bluerose.windmoon.nu on Sat, Aug 12, 2000 at 12:03:15PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 12, 2000 at 12:03:15PM -0700, FengYue wrote: > Hi, I need to drop packets using ipfw based on the value of > TTL and the value of TTL on a 2.2.8-stable system. It seems > ipfw does not support this, what options do I have? I can write this, but you're going to have to upgrade to 4.x-stable or 5.0-current to get it once I'm done. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:35: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 950BF37B915 for ; Sat, 12 Aug 2000 14:35:05 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 359221C4D; Sat, 12 Aug 2000 17:35:05 -0400 (EDT) Date: Sat, 12 Aug 2000 17:35:05 -0400 From: Bill Fumerola To: FengYue Cc: hackers@FreeBSD.ORG Subject: Re: ipfw drop packets based on SYN &TTL Message-ID: <20000812173505.G65562@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from fengyue@bluerose.windmoon.nu on Sat, Aug 12, 2000 at 12:06:24PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Aug 12, 2000 at 12:06:24PM -0700, FengYue wrote: > > Hi, I need to drop packets using ipfw based on the value of > > TTL and the value of TTL on a 2.2.8-stable system. It seems > ^^^ > I meant SYN Okay, then I already wrote this and just haven't committed it. I will within the next week, but again, you'll have to upgrade to 5.x/4.x -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 14:44:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0418F37B965 for ; Sat, 12 Aug 2000 14:44:10 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id RAA22473; Sat, 12 Aug 2000 17:46:16 -0400 (EDT) Message-Id: <200008122146.RAA22473@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 12 Aug 2000 17:58:55 -0400 To: Bill Fumerola , FengYue From: Dennis Subject: Re: ipfw drop packets based on SYN &TTL Cc: hackers@FreeBSD.ORG In-Reply-To: <20000812173404.F65562@jade.chc-chimes.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:34 PM 8/12/00 -0400, Bill Fumerola wrote: >On Sat, Aug 12, 2000 at 12:03:15PM -0700, FengYue wrote: > >> Hi, I need to drop packets using ipfw based on the value of >> TTL and the value of TTL on a 2.2.8-stable system. It seems >> ipfw does not support this, what options do I have? Why dont you just hack the IP code? its a lot easier than upgrading. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 15: 7:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta2-svc.virgin.net (mta2-svc.virgin.net [194.168.54.143]) by hub.freebsd.org (Postfix) with ESMTP id 5408B37B804 for ; Sat, 12 Aug 2000 15:07:26 -0700 (PDT) (envelope-from m.melville@virgin.net) Received: from c4d6d0 ([212.250.68.174]) by mta2-svc.virgin.net (InterMail vM.4.01.02.27 201-229-119-110) with SMTP id <20000812220638.KPOB8119.mta2-svc.virgin.net@c4d6d0> for ; Sat, 12 Aug 2000 23:06:38 +0100 Message-ID: <000601c004a9$589de1e0$ae44fad4@c4d6d0> From: "midge" To: References: Subject: Re: freebsd-hackers-digest V4 #919 Date: Sat, 12 Aug 2000 23:04:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe free-bsd hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 16: 1:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 43BEF37BD88 for ; Sat, 12 Aug 2000 16:01:24 -0700 (PDT) (envelope-from fengyue@bluerose.windmoon.nu) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7CNGEb11221 for ; Sat, 12 Aug 2000 16:16:14 -0700 (PDT) Date: Sat, 12 Aug 2000 16:16:14 -0700 (PDT) From: FengYue To: hackers@FreeBSD.ORG Subject: Re: ipfw drop packets based on SYN &TTL In-Reply-To: <200008122146.RAA22473@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000, Dennis wrote: > At 05:34 PM 8/12/00 -0400, Bill Fumerola wrote: > >On Sat, Aug 12, 2000 at 12:03:15PM -0700, FengYue wrote: > > > >> Hi, I need to drop packets using ipfw based on the value of > >> TTL and the value of TTL on a 2.2.8-stable system. It seems > >> ipfw does not support this, what options do I have? > > Why dont you just hack the IP code? its a lot easier than upgrading. > > DB That's what I'm going to do:). Thanks people, and Bill, it's very nice that we're going to have those options in 4.x/5.x. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 19:55:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 5EF8F37BB0B for ; Sat, 12 Aug 2000 19:55:10 -0700 (PDT) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 6E265A84B; Sun, 13 Aug 2000 12:56:12 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 63136544C; Sun, 13 Aug 2000 12:56:12 +1000 (EST) Date: Sun, 13 Aug 2000 12:56:12 +1000 (EST) From: andrew@ugh.net.au To: Iain Templeton Cc: freebsd-hackers@freebsd.org Subject: Re: libvgl: free(): warning: junk pointer, too high to make sense. In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000, Iain Templeton wrote: > Hi Andrew :-) Hi Iain :-) > marked above thats failing, because it is trying to free something at > the address of VGLFont, which is a global array within libvgl.a. Yes that looks right. > Using gdb on the program should make it possible to confirm that or not. Using gdb on libvgl programs is an art I think...you have to debug in one window and run in another but you cant switch consoles unless the program is running....I'll have to try debugging it from another machine. Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 21: 6: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id EB41137BC41 for ; Sat, 12 Aug 2000 21:06:04 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (Foolstrustident!@homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA13303; Sat, 12 Aug 2000 22:05:54 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39962001.35378CFE@softweyr.com> Date: Sat, 12 Aug 2000 22:11:45 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Jonas Bulow Cc: Ronald G Minnich , hackers@FreeBSD.ORG Subject: Re: IPC, shared memory, syncronization References: <39952437.EFCAA381@servicefactory.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonas Bulow wrote: > > Ronald G Minnich wrote: > > > > I don't know about the "bsd" or whatever way. If you're doing real > > parallel programming and want real performance, you'll use a test-and-set > > like function that uses the low-level machine instructions for same. > > That is exacly what I'm looking for! I found it to be overkill to > involve the kernel just because I wanted to have a context switch during > the "test-and-set". Precisely how do you expect to "have a context switch" without "involving the kernel"? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 22:41:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id D19D337BE13 for ; Sat, 12 Aug 2000 22:41:20 -0700 (PDT) (envelope-from blaz@amis.net) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 48CE95D0F; Sun, 13 Aug 2000 07:41:18 +0200 (CEST) Date: Sun, 13 Aug 2000 07:41:18 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Dennis Cc: hackers@freebsd.org Subject: Re: vmstat and top failing in 4.1-STABLE In-Reply-To: <200008122122.RAA22401@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Do you by any chance boot the kernel directly, instead of using /boot/loader? > > Im not sure what you mean, but the machine that is having the problem is > using the old-style boot loader from 3.x days. > > What is the issue? Take a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=17422 Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 23: 7:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 9550437C0F9 for ; Sat, 12 Aug 2000 23:07:12 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id AAA27098; Sun, 13 Aug 2000 00:06:53 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id AAA26841; Sun, 13 Aug 2000 00:06:16 -0600 (MDT) (envelope-from nate) Date: Sun, 13 Aug 2000 00:06:16 -0600 (MDT) Message-Id: <200008130606.AAA26841@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Wes Peters Cc: Jonas Bulow , Ronald G Minnich , hackers@FreeBSD.ORG Subject: Re: IPC, shared memory, syncronization In-Reply-To: <39962001.35378CFE@softweyr.com> References: <39952437.EFCAA381@servicefactory.se> <39962001.35378CFE@softweyr.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I don't know about the "bsd" or whatever way. If you're doing real > > > parallel programming and want real performance, you'll use a test-and-set > > > like function that uses the low-level machine instructions for same. > > > > That is exacly what I'm looking for! I found it to be overkill to > > involve the kernel just because I wanted to have a context switch during > > the "test-and-set". > > Precisely how do you expect to "have a context switch" without "involving > the kernel"? If your threads are implemented wholly in userland, you can easily do a context switch w/out involving the kernel. Our current pthreads library does this now, and the JDK's internal (green) threads implementation does it as well. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 12 23:14:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id 3CE6D37B630 for ; Sat, 12 Aug 2000 23:14:38 -0700 (PDT) (envelope-from avalon@cairo.anu.edu.au) Received: (from avalon@localhost) by cairo.anu.edu.au (8.9.3/8.9.3) id QAA11216 for hackers@freebsd.org; Sun, 13 Aug 2000 16:14:36 +1000 (EST) From: Darren Reed Message-Id: <200008130614.QAA11216@cairo.anu.edu.au> Subject: COMPAT_43 and kernel compiles. To: hackers@freebsd.org Date: Sun, 13 Aug 2000 16:14:36 +1000 (Australia/NSW) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it meant to be possible to compile a kernel *without* COMPAT_43 ? Has anyone else tried this recently ? For me, it seems to break the compile in (at least) kern_sig.c Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message