From owner-freebsd-current Sun Aug 6 0: 2:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id B7AE537B639; Sun, 6 Aug 2000 00:02:33 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id OAA78797; Sun, 6 Aug 2000 14:02:30 +0700 (NOVST) (envelope-from nnd) Date: Sun, 6 Aug 2000 14:02:30 +0700 (NOVST) Message-Id: <200008060702.OAA78797@wint.itfs.nsk.su> From: Nickolay Dudorov To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys select.h In-Reply-To: <200008060214.TAA89337@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000726 ("Lucretia") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008060214.TAA89337@freefall.freebsd.org> you wrote: > green 2000/08/05 19:14:53 PDT > > Modified files: > sys/sys select.h > Log: > None of select.h needs to be exposed to !_KERNEL. But 'src/lib/lib/libkvm/libkvm_proc.c' does '#include ' which in turn has the line: #include /* For struct selinfo */ As a result 'make buildworld' stops in 'src/lib/libkvm'. N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 2:59:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.kt.rim.or.jp (ip37-178.fli.psinet.ne.jp [210.158.37.178]) by hub.freebsd.org (Postfix) with ESMTP id 759EE37B6D3 for ; Sun, 6 Aug 2000 02:59:20 -0700 (PDT) (envelope-from yoshiaki@kt.rim.or.jp) From: yoshiaki@kt.rim.or.jp Date: Sun, 06 Aug 2000 18:58:58 +0900 (JST) Message-Id: <20000806.185858.59464911.yoshiaki@kt.rim.or.jp> To: freebsd-current@FreeBSD.ORG Subject: Re: Kernel build failing in ip6_input.c In-Reply-To: <20000806.165615.74752860.yoshiaki@kt.rim.or.jp> References: <200008060450.EAA44099@hun.org> X-Mailer: Mew version 1.95b41 on Emacs 20.6 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> From: attila! >>>>> Date: Sun, 6 Aug 2000 04:50:06 GMT > on Sat, 5 Aug 2000 20:49:21 -0300 (ADT), > Brandon Hume wrote: > > > I went about a week without updating my source tree, but yesterday when I > > went to build a kernel (and day), I get the following: > > ... > > cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/ip6_input.c > > ../../netinet6/ip6_input.c: In function `ip6_input': > > ../../netinet6/ip6_input.c:312: `inetsw' undeclared (first use in this > > function) > > ../../netinet6/ip6_input.c:312: (Each undeclared identifier is reported only once > > ../../netinet6/ip6_input.c:312: for each function it appears in.) > > ../../netinet6/ip6_input.c:312: `ip_protox' undeclared (first use in this function) > > *** Error code 1 > > > > This error is generated that I use IPFILTER and INET6 with configuration file. This is my dirty hack. This code does not do a check of action of IPv6. --- ../ip6_input.c Mon Jul 31 22:11:42 2000 +++ ip6_input.c Sun Aug 6 16:39:33 2000 @@ -309,7 +309,7 @@ * in the list may have previously cleared it. */ m0 = m; - pfh = pfil_hook_get(PFIL_IN, &inetsw[ip_protox[IPPROTO_IPV6]].pr_pfh); + pfh = pfil_hook_get(PFIL_IN, &inet6sw[ip6_protox[IPPROTO_IPV6]].pr_pfh); for (; pfh; pfh = pfh->pfil_link.tqe_next) if (pfh->pfil_func) { rv = pfh->pfil_func(ip6, sizeof(*ip6), --- ../ip6_output.c Mon Jul 31 22:11:42 2000 +++ ip6_output.c Sun Aug 6 16:39:40 2000 @@ -110,6 +110,8 @@ #include #endif +#include + static MALLOC_DEFINE(M_IPMOPTS, "ip6_moptions", "internet multicast options"); struct ip6_exthdrs { @@ -130,6 +132,9 @@ static int ip6_insert_jumboopt __P((struct ip6_exthdrs *, u_int32_t)); static int ip6_splithdr __P((struct mbuf *, struct ip6_exthdrs *)); +extern struct ip6protosw inet6sw[]; +extern u_char ip6_protox[IPPROTO_MAX]; + /* * IP6 output. The packet in mbuf chain m contains a skeletal IP6 * header (with pri, len, nxt, hlim, src, dst). @@ -854,7 +859,7 @@ * Run through list of hooks for output packets. */ m1 = m; - pfh = pfil_hook_get(PFIL_OUT, &inetsw[ip_protox[IPPROTO_IPV6]].pr_pfh); + pfh = pfil_hook_get(PFIL_OUT, &inet6sw[ip6_protox[IPPROTO_IPV6]].pr_pfh); for (; pfh; pfh = pfh->pfil_link.tqe_next) if (pfh->pfil_func) { rv = pfh->pfil_func(ip6, sizeof(*ip6), ifp, 1, &m1); --- yoshiaki@kt.rim.or.jp yoshiaki@jp.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 4:37:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 06A9E37BB51 for ; Sun, 6 Aug 2000 04:37:16 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA06556 for current@freebsd.org; Sun, 6 Aug 2000 13:37:11 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008061137.NAA06556@freebsd.dk> Subject: Intel 815E chipset ATA100 tester wanted!! To: current@freebsd.org Date: Sun, 6 Aug 2000 13:37:11 +0200 (CEST) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well subject says it all, anybody with such a beast also called ICH2 which is currently unsupported in -current You need to have the 815E chipset and an ATA100 capable disk to test out the code in question here.. Oh, and this _might_ cause trouble, so you have been warned :) Thanks! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 6:24:54 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Sun Aug 6 9: 7:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 55AA237B62C for ; Sun, 6 Aug 2000 09:07:26 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.31.124]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FYV00G67ORGWL@mta6.snfc21.pbi.net> for freebsd-current@freebsd.org; Sun, 6 Aug 2000 09:06:52 -0700 (PDT) Date: Sun, 06 Aug 2000 09:07:17 -0700 From: "George W. Dinolt" Subject: Failure build libkvm To: freebsd-current@freebsd.org Message-id: <398D8D35.40C069CC@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quick report: I saw a failure building libkvm while trying to do a build world using sources cvsuped aound 1.00 A.M. Pacific Daylight Time (U.S.) Sunday, Aug 6. The error messages I saw were cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libkvm/kvm_proc.c -o kvm_proc.o In file included from /usr/src/lib/libkvm/kvm_proc.c:57: /usr/src/lib/libkvm/../../sys/sys/tty.h:84: field `t_rsel' has incomplete type /usr/src/lib/libkvm/../../sys/sys/tty.h:85: field `t_wsel' has incomplete type *** Error code 1 Maybe someone has an idea of what has happened recently. Unfortunately, (actually, for obscure reasons it is fortunately) I have to work on Sunday so I won't be able to investigate further. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 10: 0:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7077C37B928; Sun, 6 Aug 2000 10:00:54 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Sun, 6 Aug 2000 12:37:16 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Nickolay Dudorov Cc: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys select.h In-Reply-To: <200008060702.OAA78797@wint.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Nickolay Dudorov wrote: > In article <200008060214.TAA89337@freefall.freebsd.org> you wrote: > > green 2000/08/05 19:14:53 PDT > > > > Modified files: > > sys/sys select.h > > Log: > > None of select.h needs to be exposed to !_KERNEL. > > But 'src/lib/lib/libkvm/libkvm_proc.c' does > '#include ' which in turn has the line: > > #include /* For struct selinfo */ > > > As a result 'make buildworld' stops in > 'src/lib/libkvm'. I knew something like this would happen and we'd catch some improperly written software. Thanks :) > N.Dudorov -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 11:28: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 30FA337B767; Sun, 6 Aug 2000 11:28:00 -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 UAA18417; Sun, 6 Aug 2000 20:27:54 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id D473B8889; Sun, 6 Aug 2000 20:27:35 +0200 (CEST) Date: Sun, 6 Aug 2000 20:27:35 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Cc: cg@freebsd.org Subject: [Neomagic] newpcm problems under current Message-ID: <20000806202735.A1224@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list , cg@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 Installed devices: pcm0: at memory 0xfe000000, 0xfea00000 irq 9 (1p/1r channels duplex) The first time I run mpg123, it does nothing (that is, no sound is emitted) and afterwards, /dev/dsp can't be opened at all... 404 [20:24] roberto@sidhe:~> mpg123 Lily_Was_Here.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Can't open /dev/dsp! $FreeBSD: src/sys/dev/sound/pci/neomagic.c,v 1.13 2000/07/03 20:52:27 cg Exp $ $FreeBSD: src/sys/dev/sound/pci/neomagic.h,v 1.1 2000/01/09 08:14:11 cg Exp $ Any idea ? -- 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-current" in the body of the message From owner-freebsd-current Sun Aug 6 12:56:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id A965337B52C; Sun, 6 Aug 2000 12:56:52 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:oqYnYRooR1RTGAONv+dOSsVLH+3aWrONZ4mFquZRoPHYdI8AoVSYB8Er8iGyAhoF@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/3.7W-peace) with ESMTP id e76JucP51706; Mon, 7 Aug 2000 04:56:38 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Mon, 07 Aug 2000 04:56:31 +0900 (JST) Message-Id: <20000807.045631.112579805.ume@mahoroba.org> To: mobile@freebsd.org, current@freebsd.org Subject: CFR: apm obtain per battery information From: Hajimu UMEMOTO X-Mailer: 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I added output of per battery information to apm(1). To obtain this information safely, I propose new ioctl APMIO_GETPWSTATUS. http://www.imasy.or.jp/~ume/FreeBSD/apm-pwstatus.diff If there is no objection, I'll commit this next week end. Thanks, -- 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-current" in the body of the message From owner-freebsd-current Sun Aug 6 13: 2:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 76E9B37B6DF for ; Sun, 6 Aug 2000 13:02:52 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA43597 for current@freebsd.org; Sun, 6 Aug 2000 21:54:17 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008061954.VAA43597@freebsd.dk> Subject: HEADS UP! experimental ATA100 added.. To: current@freebsd.org Date: Sun, 6 Aug 2000 21:54:17 +0200 (CEST) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just committed support for the following ATA100 controllers: Promise Ultra100 / Fasttrak100 HighPoint HPT370 controllers (fx Abit KA7-100 onboard ctrl, Abit HotRod 100) Intel ICH2 (Intel 815E based motherboards) So far I can read >90MB/s on the Promise and the HPT370. I can write >64MB/s on the promise and >50MB/s on the HPT370 so it seems writing is still done in ATA66 mode :( The ICH2 support is untested as of yet... Reports are very welcome! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 13: 7:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 2C0CB37BD13 for ; Sun, 6 Aug 2000 13:07:23 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 32187 invoked from network); 6 Aug 2000 20:07:21 -0000 Received: from acs-24-154-26-128.zoominternet.net (24.154.26.128) by scully.zoominternet.net with SMTP; 6 Aug 2000 20:07:21 -0000 Date: Sun, 6 Aug 2000 16:07:20 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-26-128.zoominternet.net To: current@freebsd.org Subject: vga0, atkbdc0, fdc0 attaching to ISA bus? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-152021635-965592440=:5522" Sender: owner-freebsd-current@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-152021635-965592440=:5522 Content-Type: TEXT/PLAIN; charset=US-ASCII Anyone know why these devices want to attach to the ISA bus on a primarily PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA and PCI slots. I was wondering maybe if even machines that have all PCI slots, that there's still an internal ISA bus? Check out my dmesg. Specifically: pci0: at 19.0 irq 11 The video controller is on the PCI. But vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 How can the VGA be ISA when the controller is on the PCI bus? Also, fdc0: at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 atapci0: port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 See how the floppy controller is on the ISA bus while the ATA driver is attaching to the PCI bus? Is there some bug in the bus probing routines? - Donn --0-152021635-965592440=:5522 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMwOiBUaHUgQXVnICAzIDEw OjA1OjE4IEVEVCAyMDAwDQogICAgZG1taWxsZXJAYWNzLTI0LTE1NC0yNC0x MzEuem9vbWludGVybmV0Lm5ldDovdXNyL3NyYy9zeXMvY29tcGlsZS9DVVNU T00NClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgyIEh6 DQpUaW1lY291bnRlciAiVFNDIiAgZnJlcXVlbmN5IDE2NjQ1MDYwNSBIeg0K Q1BVOiBQZW50aXVtL1A1NUMgKDE2Ni40NS1NSHogNTg2LWNsYXNzIENQVSkN CiAgT3JpZ2luID0gIkdlbnVpbmVJbnRlbCIgIElkID0gMHg1NDMgIFN0ZXBw aW5nID0gMw0KICBGZWF0dXJlcz0weDgwMDFiZjxGUFUsVk1FLERFLFBTRSxU U0MsTVNSLE1DRSxDWDgsTU1YPg0KcmVhbCBtZW1vcnkgID0gNjI5MTQ1NjAg KDYxNDQwSyBieXRlcykNCmF2YWlsIG1lbW9yeSA9IDU3NzYxNzkyICg1NjQw OEsgYnl0ZXMpDQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAw eGMwMzdhMDAwLg0KUHJlbG9hZGVkIHVzZXJjb25maWdfc2NyaXB0ICIvYm9v dC9rZXJuZWwuY29uZiIgYXQgMHhjMDM3YTA5Yy4NCkludGVsIFBlbnRpdW0g ZGV0ZWN0ZWQsIGluc3RhbGxpbmcgd29ya2Fyb3VuZCBmb3IgRjAwRiBidWcN Cm1kMDogTWFsbG9jIGRpc2sNCm5weDA6IDxtYXRoIHByb2Nlc3Nvcj4gb24g bW90aGVyYm9hcmQNCm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCnBjaWIwOiA8 SG9zdCB0byBQQ0kgYnJpZGdlPiBvbiBtb3RoZXJib2FyZA0KcGNpMDogPFBD SSBidXM+IG9uIHBjaWIwDQpwY2kwOiA8SG9zdCB0byBQQ0kgYnJpZGdlICh2 ZW5kb3I9MTAzOSBkZXZpY2U9NTU5Nyk+IGF0IDAuMA0KaXNhYjA6IDxTaVMg ODVjNTAzIFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgMS4wIG9uIHBjaTAN CmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMA0KYXRhcGNpMDogPFNpUyA1NTkx IEFUQTMzIGNvbnRyb2xsZXI+IHBvcnQgMHhkMDAwLTB4ZDAwZiwweGQ0MDAt MHhkNDAzLDB4ZDgwMC0weGQ4MDcsMHhlMDAwLTB4ZTAwMywweGU0MDAtMHhl NDA3IGlycSAxMSBhdCBkZXZpY2UgMS4xIG9uIHBjaTANCmF0YTA6IGF0IDB4 MWYwIGlycSAxNCBvbiBhdGFwY2kwDQphdGExOiBhdCAweDE3MCBpcnEgMTUg b24gYXRhcGNpMA0KZWQwOiA8TkUyMDAwIFBDSSBFdGhlcm5ldCAoUmVhbFRl ayA4MDI5KT4gcG9ydCAweGI4MDAtMHhiODFmIGlycSAxMCBhdCBkZXZpY2Ug MTAuMCBvbiBwY2kwDQplZDA6IGFkZHJlc3MgMDA6YzA6ZGY6ZWQ6MGI6MTcs IHR5cGUgTkUyMDAwICgxNiBiaXQpIA0KcGNpMDogPFNpUyA1NTk3Lzk4IFNW R0EgY29udHJvbGxlcj4gYXQgMTkuMCBpcnEgMTENCnNpbzIgYXQgcG9ydCAw eDNlOC0weDNlZiBpcnEgNCBvbiBpc2EwDQpzaW8yOiB0eXBlIDE2NTUwQQ0K bXNlMDogPEJ1cy9JblBvcnQgTW91c2U+IGF0IHBvcnQgMHgyM2MtMHgyM2Yg aXJxIDMgb24gaXNhMA0Kc2MwOiA8U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTAN CnNjMDogVkdBIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDIwMD4N CnZnYTA6IDxHZW5lcmljIElTQSBWR0E+IGF0IHBvcnQgMHgzYzAtMHgzZGYg aW9tZW0gMHhhMDAwMC0weGJmZmZmIG9uIGlzYTANCnNiYzE6IDxFU1MgRVMx ODY4PiBhdCBwb3J0IDB4MjIwLTB4MjJmLDB4Mzg4LTB4MzhiLDB4MzMwLTB4 MzMxIGlycSA1IGRycSAxLDAgb24gaXNhMA0KcGNtMDogPEVTUyAxOHh4IERT UD4gb24gc2JjMQ0KcHBjMDogPEVDUCBwYXJhbGxlbCBwcmludGVyIHBvcnQ+ IGF0IHBvcnQgMHgzNzgtMHgzN2YsMHg3NzgtMHg3N2YgaXJxIDcgZHJxIDMg b24gaXNhMA0KcHBjMDogU01DLWxpa2UgY2hpcHNldCAoRUNQL0VQUC9QUzIv TklCQkxFKSBpbiBDT01QQVRJQkxFIG1vZGUNCnBwYzA6IEZJRk8gd2l0aCAx Ni8xNi8xNiBieXRlcyB0aHJlc2hvbGQNCnBsaXAwOiA8UExJUCBuZXR3b3Jr IGludGVyZmFjZT4gb24gcHBidXMwDQpscHQwOiA8UHJpbnRlcj4gb24gcHBi dXMwDQpscHQwOiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQNCnBwaTA6IDxQYXJh bGxlbCBJL08+IG9uIHBwYnVzMA0KdW5rbm93bjogPFBOUDA1MDE+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwNTAxPiBjYW4ndCBh c3NpZ24gcmVzb3VyY2VzDQpmZGMwOiA8TkVDIDcyMDY1QiBvciBjbG9uZT4g YXQgcG9ydCAweDNmMi0weDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBpc2Ew DQphdGtiZGMwOiA8S2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBhdCBw b3J0IDB4NjAsMHg2NCBpcnEgMSBvbiBpc2EwDQphdGtiZDA6IDxBVCBLZXli b2FyZD4gZmxhZ3MgMHgxIGlycSAxIG9uIGF0a2JkYzANCmtiZDAgYXQgYXRr YmQwDQphZDA6IDMwOTNNQiA8RlVKSVRTVSBNUEIzMDMyQVRVPiBbNjcwNC8x NS82M10gYXQgYXRhMC1tYXN0ZXIgdXNpbmcgVURNQTMzDQphZDE6IDEwNDBN QiA8TTE2MTRUQT4gWzIxMTQvMTYvNjNdIGF0IGF0YTAtc2xhdmUgdXNpbmcg V0RNQTINCmFjZDA6IENEUk9NIDxCQ0QtMjRYIDE5OTctMDYtMjc+IGF0IGF0 YTEtbWFzdGVyIHVzaW5nIFdETUEyDQo= --0-152021635-965592440=:5522-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 13:44:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id DB05737BC1D; Sun, 6 Aug 2000 13:44:30 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id NAA20472; Sun, 6 Aug 2000 13:44:30 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id NAA14188; Sun, 6 Aug 2000 13:44:26 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200008062044.NAA14188@realtime.exit.com> Subject: Breakage in emu10k1.c ver 1.13? To: current@freebsd.org Date: Sun, 6 Aug 2000 13:44:26 -0700 (PDT) Cc: cg@freebsd.org Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw Cameron's checkin and decided to try it out; I update to that version of emu10k1.c, tried to build and got an undefined for "CCR_READADDRESS." Grepping around, it doesn't seem to be defined anywhere; I would expect to find it in gnu/dev/sound/pci/emu10k1.h but no joy. There _is_ a "CCR_READADDRESS_MASK" there, but no "CCR_READADDRESS." -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 13:57:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id B766B37BA22 for ; Sun, 6 Aug 2000 13:57:51 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA64736; Sun, 6 Aug 2000 16:57:50 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sun, 6 Aug 2000 16:57:50 -0400 (EDT) From: "Brandon D. Valentine" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Donn Miller wrote: >Anyone know why these devices want to attach to the ISA bus on a primarily >PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA >and PCI slots. I was wondering maybe if even machines that have all PCI >slots, that there's still an internal ISA bus? Check out my dmesg. I've got a machine with an Abit SL6 w/ AGP/PCI/CNR onboard, but no ISA slots, and it still has an ISA to PCI bridge built in. Some of the devices still register with the kernel on the ISA bus, even though they are quite obviously connected to the PCI bus. I suspect that some of these devices may be tied to the ISA bus in the BIOS for arcane PC/AT reasons. I would be interested to know details though, if someone could spare a moment to give an over-the-top explanation of why this is true. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 15:20:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.jakinternet.co.uk (proxy.jakinternet.co.uk [212.41.43.4]) by hub.freebsd.org (Postfix) with ESMTP id 8DB8437BBF7; Sun, 6 Aug 2000 15:20:42 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from smtp.jakinternet.co.uk (smtp.jakinternet.co.uk [212.41.41.61]) by smtp2.jakinternet.co.uk (Postfix) with SMTP id D029EA7730; Sun, 6 Aug 2000 23:18:07 +0100 (BST) Received: from vilnya.demon.co.uk ([212.41.35.79]) by smtp.jakinternet.co.uk ; Sun, 06 Aug 2000 23:19:36 -0100 Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id AB905D9A8; Sun, 6 Aug 2000 23:19:24 +0100 (BST) Message-ID: <00ae01bffff4$2959fe50$0504020a@haveblue> From: "Cameron Grant" To: "Ollivier Robert" , "FreeBSD Current Users' list" Cc: References: <20000806202735.A1224@keltia.freenix.fr> Subject: Re: [Neomagic] newpcm problems under current Date: Sun, 6 Aug 2000 23:17:43 +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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The first time I run mpg123, it does nothing (that is, no sound is emitted) > and afterwards, /dev/dsp can't be opened at all... > Any idea ? this is a known problem. it seems the neomagic driver never worked right, so when newpcm became dependant on interrupts it ceased functioning. now we trap the lack of irqs and disable the channel and emit a warning to the console. access to hardware would make this easier to fix. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 15:22:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 6A3FC37BB00; Sun, 6 Aug 2000 15:22:43 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 13LYoV-000FN5-0A; Sun, 6 Aug 2000 22:22:38 +0000 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id XAA23306; Sun, 6 Aug 2000 23:22:06 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id TAA76097; Sun, 6 Aug 2000 19:47:54 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Sun, 6 Aug 2000 19:47:52 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Frank Mayhar Cc: current@freebsd.org, stable@freebsd.org Subject: Re: Will the urio dev make it to -stable? In-Reply-To: <200007161748.KAA37326@realtime.exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to lack of time and other priorities I've not had a good look at the driver for problems. I think that the initial submitter has a more recent version available and that one should be tested. The NetBSD version is also different and I need to look at what that one does. Also, a patch to the UHCI driver is needed to get performance up to reasonable levels (bandwidth reclamation). Nick On Sun, 16 Jul 2000, Frank Mayhar wrote: > ...any time soon? It's been in current since 3/16 so it would seem MFCable, > but what do I know. Nick? (I run 4-stable and don't plan to run -current > any time soon, _and_ I want to buy a Rio 500, but not if I can't hook it to > FreeBSD.) > > Sent to both -current and -stable as both lists seem relevant. Please > limit followups, though. > -- > Frank Mayhar frank@exit.com http://www.exit.com/ > Exit Consulting http://store.exit.com/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 15:31:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id E8C7837BBF7 for ; Sun, 6 Aug 2000 15:31:21 -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 AAA02715; Mon, 7 Aug 2000 00:31:16 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 460568889; Mon, 7 Aug 2000 00:30:33 +0200 (CEST) Date: Mon, 7 Aug 2000 00:30:33 +0200 From: Ollivier Robert To: "FreeBSD Current Users' list" Cc: Cameron Grant Subject: Re: [Neomagic] newpcm problems under current Message-ID: <20000807003033.A50498@keltia.freenix.fr> Mail-Followup-To: FreeBSD Current Users' list , Cameron Grant References: <20000806202735.A1224@keltia.freenix.fr> <00ae01bffff4$2959fe50$0504020a@haveblue> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <00ae01bffff4$2959fe50$0504020a@haveblue>; from gandalf@vilnya.demon.co.uk on Sun, Aug 06, 2000 at 11:17:43PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Cameron Grant: > this is a known problem. it seems the neomagic driver never worked right, Well, it used to work :) > so when newpcm became dependant on interrupts it ceased functioning. now we > trap the lack of irqs and disable the channel and emit a warning to the > console. I do get lots of interrupt. I patched my kernel in June to generate a printf for each interrupt and I was seeing lots of them without even running mpg123. Aug 3 19:17:28 sidhe /kernel: getting an intr Aug 3 19:17:59 sidhe last message repeated 33 times Aug 3 19:18:57 sidhe last message repeated 73 times Aug 3 19:18:58 sidhe /kernel: getting an intr Aug 3 19:19:29 sidhe last message repeated 53 times Aug 3 19:20:37 sidhe last message repeated 93 times > access to hardware would make this easier to fix. I would be difficult to send you my laptop, I do use it :-) -- 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-current" in the body of the message From owner-freebsd-current Sun Aug 6 15:56:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.jakinternet.co.uk (proxy.jakinternet.co.uk [212.41.43.4]) by hub.freebsd.org (Postfix) with ESMTP id D822B37BAAD for ; Sun, 6 Aug 2000 15:56:36 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from smtp.jakinternet.co.uk (smtp.jakinternet.co.uk [212.41.41.61]) by smtp2.jakinternet.co.uk (Postfix) with SMTP id CF3B3A776F for ; Sun, 6 Aug 2000 23:54:07 +0100 (BST) Received: from vilnya.demon.co.uk ([212.41.35.79]) by smtp.jakinternet.co.uk ; Sun, 06 Aug 2000 23:55:42 -0100 Received: from haveblue (haveblue.rings [10.2.4.5]) by vilnya.demon.co.uk (Postfix) with SMTP id 6B594D9B6; Sun, 6 Aug 2000 23:55:33 +0100 (BST) Message-ID: <00b801bffff9$33cb6310$0504020a@haveblue> From: "Cameron Grant" To: "Ollivier Robert" , "FreeBSD Current Users' list" References: <20000806202735.A1224@keltia.freenix.fr> <00ae01bffff4$2959fe50$0504020a@haveblue> <20000807003033.A50498@keltia.freenix.fr> Subject: Re: [Neomagic] newpcm problems under current Date: Sun, 6 Aug 2000 23:53:51 +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.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Cameron Grant: > > this is a known problem. it seems the neomagic driver never worked right, > Well, it used to work :) it used to *appear* to work. > > so when newpcm became dependant on interrupts it ceased functioning. now we > > trap the lack of irqs and disable the channel and emit a warning to the > > console. > I do get lots of interrupt. I patched my kernel in June to generate a printf > for each interrupt and I was seeing lots of them without even running mpg123. is the irq shared? have your printf display the neomagic status - i'll bet it's 0 indicating the irq was not generated by the neomagic. > > access to hardware would make this easier to fix. > > I would be difficult to send you my laptop, I do use it :-) :) -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 18: 6:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 1855437B817 for ; Sun, 6 Aug 2000 18:06:53 -0700 (PDT) (envelope-from kuriyama@FreeBSD.org) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e7716sG06603 for ; Mon, 7 Aug 2000 10:06:55 +0900 (JST) Date: Mon, 07 Aug 2000 10:06:54 +0900 Message-ID: <7m4s4xg9qp.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: Current Subject: libexec/telnetd broken? User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 10) (Capitol Reef) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my -current box, buildworld failed as below. ===> libexec/telnetd cc -g -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -I/usr/src/libexec/telnetd/../../lib -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/telnetd/global.c cc -g -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -I/usr/src/libexec/telnetd/../../lib -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/telnetd/slc.c cc -g -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -I/usr/src/libexec/telnetd/../../lib -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/telnetd/state.c cc -g -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK -I/usr/src/libexec/telnetd/../../lib -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/telnetd/sys_term.c In file included from /usr/src/libexec/telnetd/sys_term.c:117: /usr/obj/usr/src/i386/usr/include/sys/tty.h:84: field `t_rsel' has incomplete type /usr/obj/usr/src/i386/usr/include/sys/tty.h:85: field `t_wsel' has incomplete type *** Error code 1 Stop in /usr/src/libexec/telnetd. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 -- Jun Kuriyama // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 18:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mike.dhis.org (hiper1-d176.stk.cwnet.com [209.142.56.176]) by hub.freebsd.org (Postfix) with ESMTP id 4925437BCCC for ; Sun, 6 Aug 2000 18:41:47 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with ESMTP id 81E21DA; Sun, 6 Aug 2000 18:41:39 -0700 (PDT) Message-ID: <398E13D2.C3D754CA@es.co.nz> Date: Sun, 06 Aug 2000 18:41:38 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brandon D. Valentine" Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brandon D. Valentine" wrote: > > On Sun, 6 Aug 2000, Donn Miller wrote: > > >Anyone know why these devices want to attach to the ISA bus on a primarily > >PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA > >and PCI slots. I was wondering maybe if even machines that have all PCI > >slots, that there's still an internal ISA bus? Check out my dmesg. > > I've got a machine with an Abit SL6 w/ AGP/PCI/CNR onboard, but no ISA > slots, and it still has an ISA to PCI bridge built in. Some of the > devices still register with the kernel on the ISA bus, even though they > are quite obviously connected to the PCI bus. I suspect that some of > these devices may be tied to the ISA bus in the BIOS for arcane PC/AT > reasons. I would be interested to know details though, if someone could > spare a moment to give an over-the-top explanation of why this is true. I'm working on a little util similar to pciconf -l right now.. but using a large array of vendor/device strings for the id's.. Does pciconf -l display those devices as being part of the PCI bus or are they out of the picture completely? -mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 19:48: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 752BC37B5C2; Sun, 6 Aug 2000 19:47:59 -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 DAA10751; Mon, 7 Aug 2000 03:25:01 +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 DAA18300; Mon, 7 Aug 2000 03:25:21 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008070225.DAA18300@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Sheldon Hearn Cc: Poul-Henning Kamp , brian@FreeBSD.ORG, current@FreeBSD.ORG, brian@Awfulhak.org, Ben Smithurst Subject: Re: if_tun.ko seems broken In-Reply-To: Message from Sheldon Hearn of "Thu, 27 Jul 2000 14:09:46 +0200." <63773.964699786@axl.ops.uunet.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 03:25:20 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for the delay (I've been away for 2 weeks). As Ben pointed out, the act of opening the /dev device is the key - specifically, the if_attach() called from tuncreate() called from tunopen() does some permanent damage^Wgood. I don't think ifconfig really has a chance of doing the right thing here. It simply kldload()s the module, but you can't tell kldload() what interface you're interested in, therefore tunattach() just adds the devsw and leaves it at that, not if_attach()ing any specific interfaces. ifconfig then goes through the interfaces available and doesn't find what it was trying to load. I don't think it's right for ifconfig() to know any more, and I don't think kldload() should know anything about unit numbers, so this magic isn't really possible AFAICT. > On Thu, 27 Jul 2000 09:37:11 +0200, Poul-Henning Kamp wrote: > > > > ifconfig tun0 inet 10.0.0.1 > > > > I think you are seing the "interesting" side effect of the BSD > > concept of "POINT2POINT" lines. > > I think that's anotehr issue. Once I'd read 0 bytes from /dev/tun0 with > dd(1), I was able to do > > ifconfig tun0 inet 10.0.0.1 10.0.0.1 > > which is actually what I wanted. > > Ciao, > Sheldon. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 20:21:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2BB1337BC3D; Sun, 6 Aug 2000 20:21:31 -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 VAA84883; Sun, 6 Aug 2000 21:21:29 -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 VAA28570; Sun, 6 Aug 2000 21:21:13 -0600 (MDT) Message-Id: <200008070321.VAA28570@harmony.village.org> To: Brian Fundakowski Feldman Subject: Re: cvs commit: src/sys/sys select.h Cc: Nickolay Dudorov , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 Aug 2000 12:37:16 EDT." References: Date: Sun, 06 Aug 2000 21:21:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Fundakowski Feldman writes: : I knew something like this would happen and we'd catch some improperly : written software. Thanks :) No offense, but if you knew this was going to happen, why didn't you do a make buildworld first? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 20:23:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8AFE537B6AB for ; Sun, 6 Aug 2000 20:23:37 -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 VAA84892; Sun, 6 Aug 2000 21:23:31 -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 VAA28590; Sun, 6 Aug 2000 21:23:13 -0600 (MDT) Message-Id: <200008070323.VAA28590@harmony.village.org> To: "Brandon D. Valentine" Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? Cc: Donn Miller , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 Aug 2000 16:57:50 EDT." References: Date: Sun, 06 Aug 2000 21:23:13 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Brandon D. Valentine" writes: : I've got a machine with an Abit SL6 w/ AGP/PCI/CNR onboard, but no ISA : slots, and it still has an ISA to PCI bridge built in. Some of the : devices still register with the kernel on the ISA bus, even though they : are quite obviously connected to the PCI bus. I suspect that some of : these devices may be tied to the ISA bus in the BIOS for arcane PC/AT : reasons. I would be interested to know details though, if someone could : spare a moment to give an over-the-top explanation of why this is true. Well, here's the short answer: The reason you have a ISA to PCI bridge still is that the serial ports, parallel ports, floppy, keyboard and mouse devices still live on the ISA bus. They aren't full PCI nodes just yet in most hardware designs (I've yet to see a floppy, keyboard or mouse on the pci bus, but I'm sure people will tell me where I can find such beasts). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 20:27:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 91FE537BC4D for ; Sun, 6 Aug 2000 20:27:10 -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 VAA84908; Sun, 6 Aug 2000 21:27:08 -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 VAA28643; Sun, 6 Aug 2000 21:26:53 -0600 (MDT) Message-Id: <200008070326.VAA28643@harmony.village.org> Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? Cc: "Brandon D. Valentine" , Donn Miller , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 Aug 2000 21:23:13 MDT." <200008070323.VAA28590@harmony.village.org> References: <200008070323.VAA28590@harmony.village.org> Date: Sun, 06 Aug 2000 21:26:53 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008070323.VAA28590@harmony.village.org> Warner Losh writes: : The reason you have a ISA to PCI bridge still is that the serial : ports, parallel ports, floppy, keyboard and mouse devices still live : on the ISA bus. They aren't full PCI nodes just yet in most hardware : designs (I've yet to see a floppy, keyboard or mouse on the pci bus, : but I'm sure people will tell me where I can find such beasts). I should have also added: Even though there are no ISA expansion slots on your machine, you still have an ISA bus living inside (unless it is a legacy free machine we keep hearing about, which I didn't think was on the market). The PC-99 standard (not to be confused with the Japanese PC-98 machines) states that you cannot have a ISA expansion slot, but a later clarification to the standard states clearly that you can still have ISA devices built into the mother board. In other words, No ISA slots doesn't necessarily mean that the machine doesn't have an ISA bus. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 21:47:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EB3E737BC9D; Sun, 6 Aug 2000 21:47:48 -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 AAA93842; Mon, 7 Aug 2000 00:47:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 7 Aug 2000 00:47:38 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ollivier Robert Cc: "FreeBSD Current Users' list" , cg@freebsd.org Subject: Re: [Neomagic] newpcm problems under current In-Reply-To: <20000806202735.A1224@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "me too" pcm0: mem 0xfda00000-0xfdafffff,0xfac00000-0xfaffffff irq 5 at device 0.1 on pci1 pcm0: play interrupt timeout, channel dead Then EBUSY until the cows come home. I chatted with Cam some this evening; this problem seems to have come about as a result of driver restructuring. This chipset used to "just work" on my Dell notebook under some earlier 4.0 revision. On Sun, 6 Aug 2000, Ollivier Robert wrote: > FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 > > FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 > Installed devices: > pcm0: at memory 0xfe000000, 0xfea00000 irq 9 (1p/1r channels duplex) > > The first time I run mpg123, it does nothing (that is, no sound is emitted) > and afterwards, /dev/dsp can't be opened at all... 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-current" in the body of the message From owner-freebsd-current Sun Aug 6 21:57:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A354537B546; Sun, 6 Aug 2000 21:57:24 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Mon, 7 Aug 2000 00:33:47 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Warner Losh Cc: Nickolay Dudorov , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/sys select.h In-Reply-To: <200008070321.VAA28570@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Warner Losh wrote: > In message Brian Fundakowski Feldman writes: > : I knew something like this would happen and we'd catch some improperly > : written software. Thanks :) > > No offense, but if you knew this was going to happen, why didn't you > do a make buildworld first? There are only three choices. One is to break some of the software. Another is to break some other amount of the software. The other is to make our headers even more totally horrid than they are now, but still tenuously allowing "all" of the software to work, no matter how wrong it is. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22: 4:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 27FA737BCC8; Sun, 6 Aug 2000 22:04:13 -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 XAA85225; Sun, 6 Aug 2000 23:04:11 -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 XAA29285; Sun, 6 Aug 2000 23:03:56 -0600 (MDT) Message-Id: <200008070503.XAA29285@harmony.village.org> To: Brian Fundakowski Feldman Subject: Re: cvs commit: src/sys/sys select.h Cc: Nickolay Dudorov , current@FreeBSD.org In-reply-to: Your message of "Mon, 07 Aug 2000 00:33:47 EDT." References: Date: Sun, 06 Aug 2000 23:03:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Fundakowski Feldman writes: : There are only three choices. One is to break some of the software. : Another is to break some other amount of the software. The other is : to make our headers even more totally horrid than they are now, but : still tenuously allowing "all" of the software to work, no matter how : wrong it is. I guess my point was rather aimed at saying "If you were going to make that change, you should have at least done a make buildworld to see what it would break and fixed that in the tree." Since you've reverted the change, I'll not worry about it further. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22:36: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id B259D37B686 for ; Sun, 6 Aug 2000 22:35:57 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA68646; Mon, 7 Aug 2000 01:35:34 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 7 Aug 2000 01:35:34 -0400 (EDT) From: "Brandon D. Valentine" To: Warner Losh Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? In-Reply-To: <200008070326.VAA28643@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 6 Aug 2000, Warner Losh wrote: >In message <200008070323.VAA28590@harmony.village.org> Warner Losh writes: >: The reason you have a ISA to PCI bridge still is that the serial >: ports, parallel ports, floppy, keyboard and mouse devices still live >: on the ISA bus. They aren't full PCI nodes just yet in most hardware >: designs (I've yet to see a floppy, keyboard or mouse on the pci bus, >: but I'm sure people will tell me where I can find such beasts). > >I should have also added: > >Even though there are no ISA expansion slots on your machine, you >still have an ISA bus living inside (unless it is a legacy free >machine we keep hearing about, which I didn't think was on the >market). The PC-99 standard (not to be confused with the Japanese >PC-98 machines) states that you cannot have a ISA expansion slot, but >a later clarification to the standard states clearly that you can >still have ISA devices built into the mother board. > >In other words, No ISA slots doesn't necessarily mean that the machine >doesn't have an ISA bus. Well, I understand that, my question is, why are true PCI devices like video controllers still shown as being on isa0 by the kernel? I wanted an explanation of that. That's what doesn't make sense to me. Perhaps there's a valid PC/AT hardware limitation reason for it. Otherwise it seems silly. =) Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22:39:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 81A9637B8E4 for ; Sun, 6 Aug 2000 22:39:39 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA68671; Mon, 7 Aug 2000 01:39:28 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 7 Aug 2000 01:39:27 -0400 (EDT) From: "Brandon D. Valentine" To: Warner Losh Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, Brandon D. Valentine wrote: >Well, I understand that, my question is, why are true PCI devices like >video controllers still shown as being on isa0 by the kernel? I wanted >an explanation of that. That's what doesn't make sense to me. Perhaps >there's a valid PC/AT hardware limitation reason for it. Otherwise it >seems silly. =) If you can forget something, so can I. ;-) I should have added: vga0: rev 0x00 int a irq 12 on pci0.16.0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa ^^^^^^^^^ ^^^ That's what I'm talking about. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22:44:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 2D27A37BC98 for ; Sun, 6 Aug 2000 22:44:45 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:DYPubaJsK+sD7FD/HJjJWdZ0u77kNFzq@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA07711; Mon, 7 Aug 2000 14:44:41 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:uG/rUkOjBJTyofnv6HJfBuADgGfhiZFP@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id OAA27378; Mon, 7 Aug 2000 14:51:31 +0900 (JST) Message-Id: <200008070551.OAA27378@zodiac.mech.utsunomiya-u.ac.jp> To: "Brandon D. Valentine" Cc: Warner Losh , Donn Miller , current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? In-reply-to: Your message of "Mon, 07 Aug 2000 01:35:34 -0400." References: Date: Mon, 07 Aug 2000 14:51:30 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sun, 6 Aug 2000, Warner Losh wrote: > >>In message <200008070323.VAA28590@harmony.village.org> Warner Losh writes: >>: The reason you have a ISA to PCI bridge still is that the serial >>: ports, parallel ports, floppy, keyboard and mouse devices still live >>: on the ISA bus. They aren't full PCI nodes just yet in most hardware >>: designs (I've yet to see a floppy, keyboard or mouse on the pci bus, >>: but I'm sure people will tell me where I can find such beasts). >> >>I should have also added: >> >>Even though there are no ISA expansion slots on your machine, you >>still have an ISA bus living inside (unless it is a legacy free >>machine we keep hearing about, which I didn't think was on the >>market). The PC-99 standard (not to be confused with the Japanese >>PC-98 machines) states that you cannot have a ISA expansion slot, but >>a later clarification to the standard states clearly that you can >>still have ISA devices built into the mother board. >> >>In other words, No ISA slots doesn't necessarily mean that the machine >>doesn't have an ISA bus. > >Well, I understand that, my question is, why are true PCI devices like >video controllers still shown as being on isa0 by the kernel? I wanted >an explanation of that. That's what doesn't make sense to me. Perhaps >there's a valid PC/AT hardware limitation reason for it. Otherwise it >seems silly. =) > >Brandon D. Valentine If you read the PCI's specification, video cards are given special treatment due to necessary backward compatibility with ISA video cards. PCI video cards occupies ISA bus resources (ports and memory range) and these are handled in a special manner which is not quite PCI bus's way. If a video card uses only PCI bus resources and does not occupy any of legacy ISA bus resoruces, it is indeed silly that it is recognized to be on the ISA bus. But, the reality is that the PCI video card is a half-PCI and half-ISA device... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22:47:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1A11137BC9D for ; Sun, 6 Aug 2000 22:47:37 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA68756; Mon, 7 Aug 2000 01:47:12 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 7 Aug 2000 01:47:12 -0400 (EDT) From: "Brandon D. Valentine" To: Kazutaka YOKOTA Cc: Warner Losh , Donn Miller , current@FreeBSD.ORG Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? In-Reply-To: <200008070551.OAA27378@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, Kazutaka YOKOTA wrote: >recognized to be on the ISA bus. But, the reality is that the PCI >video card is a half-PCI and half-ISA device... Thank you, Kazu. That sucks, but at least it makes sense now. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 22:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0132537BC9D for ; Sun, 6 Aug 2000 22:49:38 -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 XAA85432; Sun, 6 Aug 2000 23:49:34 -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 XAA29774; Sun, 6 Aug 2000 23:49:18 -0600 (MDT) Message-Id: <200008070549.XAA29774@harmony.village.org> To: Kazutaka YOKOTA Subject: Re: vga0, atkbdc0, fdc0 attaching to ISA bus? Cc: "Brandon D. Valentine" , Donn Miller , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 07 Aug 2000 14:51:30 +0900." <200008070551.OAA27378@zodiac.mech.utsunomiya-u.ac.jp> References: <200008070551.OAA27378@zodiac.mech.utsunomiya-u.ac.jp> Date: Sun, 06 Aug 2000 23:49:18 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : >Well, I understand that, my question is, why are true PCI devices like : >video controllers still shown as being on isa0 by the kernel? Yokota-san's answer is correct here, which I've not repeated. however, atkbdc0 is a isa device as is fdc0. For some drivers it is easier to hack a pci front end that kicks the device into isa legacy mode. video is one (since it must support legacy things). pcic is another, because writing a native cardbus bridge code is a lot harder than writing a front end that kicks it into compat mode. but atakbdc and fdc, those really are isa devices. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 6 23:13: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 3C3AE37BCD8 for ; Sun, 6 Aug 2000 23:12:57 -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 IAA20707; Mon, 7 Aug 2000 08:12:55 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4BB288889; Mon, 7 Aug 2000 08:01:26 +0200 (CEST) Date: Mon, 7 Aug 2000 08:01:26 +0200 From: Ollivier Robert To: Cameron Grant Cc: "FreeBSD Current Users' list" Subject: Re: [Neomagic] newpcm problems under current Message-ID: <20000807080126.A53015@keltia.freenix.fr> Mail-Followup-To: Cameron Grant , FreeBSD Current Users' list References: <20000806202735.A1224@keltia.freenix.fr> <00ae01bffff4$2959fe50$0504020a@haveblue> <20000807003033.A50498@keltia.freenix.fr> <00b801bffff9$33cb6310$0504020a@haveblue> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <00b801bffff9$33cb6310$0504020a@haveblue>; from gandalf@vilnya.demon.co.uk on Sun, Aug 06, 2000 at 11:53:51PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Cameron Grant: > is the irq shared? have your printf display the neomagic status - i'll bet > it's 0 indicating the irq was not generated by the neomagic. Ahem, yes it is shared, by almost everything on the machine. Should have thought of that... -- 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 0: 0: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id D602637B58E; Sun, 6 Aug 2000 23:59:45 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.10.1/8.10.1) id e776wvO49577; Mon, 7 Aug 2000 08:58:57 +0200 (SAT) From: John Hay Message-Id: <200008070658.e776wvO49577@zibbi.mikom.csir.co.za> Subject: Re: [Neomagic] newpcm problems under current In-Reply-To: from Robert Watson at "Aug 7, 2000 00:47:38 am" To: rwatson@FreeBSD.ORG (Robert Watson) Date: Mon, 7 Aug 2000 08:58:57 +0200 (SAT) Cc: roberto@keltia.freenix.fr (Ollivier Robert), freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list), cg@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 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. I'm seeing something like this. I have an and mpg123 will play a list of songs correctly, but if I ^C out of it and try again, I see the "pcm0: play interrupt timeout, channel dead" message and it don't want to play again until a reboot. The gusc0 device is the only one using irq 5 and I have used this setup for quite a while. gusc0: at port 0x220,0x320-0x327,0x32c-0x333 irq 5 drq 1,3 flags 0x13 on isa0 pcm0: on gusc0 John -- John Hay -- John.Hay@icomtek.csir.co.za > > "me too" > > pcm0: mem 0xfda00000-0xfdafffff,0xfac00000-0xfaffffff irq > 5 at device 0.1 on pci1 > pcm0: play interrupt timeout, channel dead > > Then EBUSY until the cows come home. I chatted with Cam some this > evening; this problem seems to have come about as a result of driver > restructuring. This chipset used to "just work" on my Dell notebook under > some earlier 4.0 revision. > > On Sun, 6 Aug 2000, Ollivier Robert wrote: > > > FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 > > > > FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 > > Installed devices: > > pcm0: at memory 0xfe000000, 0xfea00000 irq 9 (1p/1r channels duplex) > > > > The first time I run mpg123, it does nothing (that is, no sound is emitted) > > and afterwards, /dev/dsp can't be opened at all... > > 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 0:16:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 879FF37BA01 for ; Mon, 7 Aug 2000 00:16:04 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 18739 invoked from network); 7 Aug 2000 07:15:59 -0000 Received: from p3e9bdab9.dip.t-dialin.net (HELO steele.intra) ([62.155.218.185]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 7 Aug 2000 07:15:59 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id JAA00419 for current@FreeBSD.ORG; Mon, 7 Aug 2000 09:15:51 +0200 (CEST) (envelope-from steele) Date: Mon, 7 Aug 2000 09:15:50 +0200 From: Benedikt Schmidt To: current@FreeBSD.ORG Subject: emu10k1 problems solved Message-ID: <20000807091550.A364@cloaked.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to say that with the recent changes in the emu10k1 driver all my problems with it have disappeared. There are no more "dodgy irq" messages and the sound quality has improved too (no more crackling). Great work Cameron. ___ Benedikt Schmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 0:55: 8 2000 Delivered-To: freebsd-current@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 C34DD37BD0A for ; Mon, 7 Aug 2000 00:55:03 -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 13Lhk3-0001XV-00; Mon, 07 Aug 2000 09:54:35 +0200 From: Sheldon Hearn To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Sun, 06 Aug 2000 01:49:49 +1000." <200008051549.BAA10791@dungeon.home> Date: Mon, 07 Aug 2000 09:54:35 +0200 Message-ID: <5920.965634875@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 06 Aug 2000 01:49:49 +1000, Stephen McKay wrote: > I think shutdown time has gotten uglier and slower than it needs to be. Probably because you already understand what's going on. The existing text for the "stopping process" messages is designed to help folks stay calm while their machines apparently lock up at shutdown time. I think they're very healthy and should stay exactly as they are. The second patch is of no importance to me. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 1: 3:52 2000 Delivered-To: freebsd-current@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 58DDE37BD0A; Mon, 7 Aug 2000 01:03:46 -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 13Lhss-0001fQ-00; Mon, 07 Aug 2000 10:03:42 +0200 From: Sheldon Hearn To: Jun Kuriyama Cc: Current Subject: Re: libexec/telnetd broken? In-reply-to: Your message of "Mon, 07 Aug 2000 10:06:54 +0900." <7m4s4xg9qp.wl@waterblue.imgsrc.co.jp> Date: Mon, 07 Aug 2000 10:03:42 +0200 Message-ID: <6411.965635422@axl.ops.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 07 Aug 2000 10:06:54 +0900, Jun Kuriyama wrote: > In file included from /usr/src/libexec/telnetd/sys_term.c:117: > /usr/obj/usr/src/i386/usr/include/sys/tty.h:84: field `t_rsel' has incomplete type Not sure what caused this, but I saw it too last night. It seems to be fixed now, though. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 1:19: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 5666B37BD2B; Mon, 7 Aug 2000 01:19:03 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e778Isr25292; Mon, 7 Aug 2000 01:18:54 -0700 (PDT) Date: Mon, 7 Aug 2000 01:18:54 -0700 From: Alfred Perlstein To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown Message-ID: <20000807011854.Q4854@fw.wintelcom.net> References: <200008051549.BAA10791@dungeon.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008051549.BAA10791@dungeon.home>; from mckay@thehub.com.au on Sun, Aug 06, 2000 at 01:49:49AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Stephen McKay [000805 08:49] wrote: > > Patch 2 is smaller and possibly controversial. Normally bufdaemon and > syncer are sleeping when they are told to suspend. This delays shutdown > by a few boring seconds. With this patch, it is zippier. I expect people > to complain about this shortcut, but every sleeping process should expect > to be woken for no reason at all. Basic kernel premise. You better bet it's controversial, this isn't "Basic kernel premise" it's quite possible and acceptable for some piece of code to expect this sequence: me someone else put myself at the head of a queue waiting for some resource finish with resource and perform wakeup assume wakeup was notification of resource availability and use it without checking for a 'stray' wakeup. *boom* *crash* *ow* :) > I've been running these patches on a 4.x machine for a while now. No > problems except I am now surprised by the slow and ugly shutdown of > unpatched machines. :-) If you want to speed it up "properly" then either set up some protocol or do something along the lines of what speedup_syncer() does: if (updateproc->p_wchan == &lbolt) setrunnable(updateproc); It 'knows' that the syncer is safe to wakeup when sleeping on lbolt (only) and only wakes it up then, otherwise it may be in some other random part of vfsbio and blow up. but... Actually I think that speedup_syncer() is somewhat bogus and should also check some sort of variable that says "syncer is idle" rather than lbolt, because we never know when an lbolt sleep may happen in the codepath. (ugh) The syncer would need to set this variable before sleeping to declare itself "safe" for per-emptive wakeup. It's a bit of hysteria but it's definetly possible. hope this helps, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 1:25:47 2000 Delivered-To: freebsd-current@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 D591F37BD3B; Mon, 7 Aug 2000 01:25:44 -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 BAA02380; Mon, 7 Aug 2000 01:36:57 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008070836.BAA02380@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 01:18:54 PDT." <20000807011854.Q4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Aug 2000 01:36:57 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Stephen McKay [000805 08:49] wrote: > > > > Patch 2 is smaller and possibly controversial. Normally bufdaemon and > > syncer are sleeping when they are told to suspend. This delays shutdown > > by a few boring seconds. With this patch, it is zippier. I expect people > > to complain about this shortcut, but every sleeping process should expect > > to be woken for no reason at all. Basic kernel premise. > > You better bet it's controversial, this isn't "Basic kernel premise" Actually, that depends. It is definitely poor programming practice to not check the condition for which you slept on wakeup. > *boom* *crash* *ow* :) Doctor: So don't do that. In this case, the relevant processes just need to learn to check whether they've been woken in order to die. -- ... 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 1:50:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3451537BD5B; Mon, 7 Aug 2000 01:50:23 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e778oIX26055; Mon, 7 Aug 2000 01:50:18 -0700 (PDT) Date: Mon, 7 Aug 2000 01:50:18 -0700 From: Alfred Perlstein To: Mike Smith Cc: Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown Message-ID: <20000807015018.R4854@fw.wintelcom.net> References: <20000807011854.Q4854@fw.wintelcom.net> <200008070836.BAA02380@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008070836.BAA02380@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Mon, Aug 07, 2000 at 01:36:57AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Smith [000807 01:25] wrote: > > * Stephen McKay [000805 08:49] wrote: > > > > > > Patch 2 is smaller and possibly controversial. Normally bufdaemon and > > > syncer are sleeping when they are told to suspend. This delays shutdown > > > by a few boring seconds. With this patch, it is zippier. I expect people > > > to complain about this shortcut, but every sleeping process should expect > > > to be woken for no reason at all. Basic kernel premise. > > > > You better bet it's controversial, this isn't "Basic kernel premise" > > Actually, that depends. It is definitely poor programming practice to > not check the condition for which you slept on wakeup. Stephen's patches didn't give them that option, the syncer could be in some other part of vfs that doesn't expect to be woken up, perhaps in uniterruptable sleep... perhaps waiting for a DMA transfer? How does one check if the data filled into a buffer is actually from the driver and not just stale? > > *boom* *crash* *ow* :) > > Doctor: So don't do that. > > In this case, the relevant processes just need to learn to check whether > they've been woken in order to die. No, they need to signify that it's safe to wake them up early. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 7:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from smople.thehub.com.au (smople.thehub.com.au [203.143.240.10]) by hub.freebsd.org (Postfix) with ESMTP id 96A5037B5AF; Mon, 7 Aug 2000 07:17:23 -0700 (PDT) (envelope-from mckay@thehub.com.au) Received: from gift.home (ppp215.dyn248.pacific.net.au [203.143.248.215]) by smople.thehub.com.au (8.9.3/8.9.1) with ESMTP id AAA92482; Tue, 8 Aug 2000 00:17:08 +1000 (EST) Received: (from mckay@localhost) by gift.home (8.9.3/8.9.3) id AAA00524; Tue, 8 Aug 2000 00:17:48 +1000 (EST) (envelope-from mckay) Date: Tue, 8 Aug 2000 00:17:48 +1000 (EST) From: Stephen McKay Message-Id: <200008071417.AAA00524@gift.home> To: Alfred Perlstein Cc: Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown References: <20000807011854.Q4854@fw.wintelcom.net> <200008070836.BAA02380@mass.osd.bsdi.com> <20000807015018.R4854@fw.wintelcom.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Mike Smith [000807 01:25] wrote: > > > * Stephen McKay [000805 08:49] wrote: > > > > > > > > ... every sleeping process should expect > > > > to be woken for no reason at all. Basic kernel premise. > > > > > > You better bet it's controversial, this isn't "Basic kernel premise" > > > > Actually, that depends. It is definitely poor programming practice to > > not check the condition for which you slept on wakeup. > > Stephen's patches didn't give them that option, the syncer could be > in some other part of vfs that doesn't expect to be woken up, perhaps > in uniterruptable sleep... perhaps waiting for a DMA transfer? > > How does one check if the data filled into a buffer is actually from > the driver and not just stale? The time honoured standard is: raise cpu priority while (we do not have exclusive use of some item) { set some sort of "I want this item" flag (optional) sleep on a variable related to the item } use the item/data we waited for lower cpu priority A typical example from vfs_subr.c: s = splbio(); while (vp->v_numoutput) { vp->v_flag |= VBWAIT; error = tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "vinvlbuf", slptimeo); if (error) { splx(s); return (error); } } ... the code plays a little with vp here ... splx(s); A simpler example from swap_pager.c: s = splbio(); while ((bp->b_flags & B_DONE) == 0) { tsleep(bp, PVM, "swwrt", 0); } ... code uses bp here ... splx(s); Both of these examples are safe from side effects due to waking up early. This is how all such code should be. To do otherwise is to introduce possible race conditions. At your prompting, though, I've looked at more code and have found an example that violates this principle. I assume it is a bug waiting to bite us. In the 4.1.0 source (sorry, that's all I have on operational computers at this moment) line 581 of vfs_bio.c sleeps without looping. It would seem that Alfred's assertion of lurking danger is correct. This stuff should be fixed. > > > *boom* *crash* *ow* :) > > > > Doctor: So don't do that. > > > > In this case, the relevant processes just need to learn to check whether > > they've been woken in order to die. > > No, they need to signify that it's safe to wake them up early. When I return to the land of FreeBSD I'll offer a speedup that does not wake processes in arbitrary places (to avoid tickling lurking bugs). To do this I would make processes that want to use the suspension mechanism call a routine in kern_kthread.c for their just-loafing-about sleep. Then that module will have enough information to do the job quickly. And back to the simpler bit (the bike shed bit). Does everyone else actually *like* the verbose messages currently used? And the gratuitous extra newline in the "syncing..." message? Stephen. PS My main machine has blown its power supply. Contact with me will be patchy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 8:53:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 1FC7937B744 for ; Mon, 7 Aug 2000 08:53:35 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id KAA05672; Mon, 7 Aug 2000 10:53:27 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Mon, 7 Aug 2000 10:53:27 -0500 (CDT) From: David Scheidt To: Mike Muir Cc: Stephen Hocking , current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: <398B2BEE.CA9BD5CD@es.co.nz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Aug 2000, Mike Muir wrote: :Stephen Hocking wrote: :> :> About a week ago, I complained of mysterious Sig 11s during a make world. :> After some experimentation, a PC100 DIMM was found to be better suited for a :> 66MHz memory bus in another machine, who obligingly donated a DIMM in return :> that actually works with a 100MHz bus. I think the trip from Australia and :> this Texas heat finally pushed the dodgy one over the edge. : :Have you tried any memory testing routines such as memtest86 ? Its the :only you write to a floppy and it runs before any bootstrap kicks in -- :independant of the OS -- and takes around 18 hours for a single pass. It :appears to be quite a comprehensive torture test. If so, how did that Software memory testers don't work. They may sometimes find problems, true, but if they don't, it doesn't mean the memory is good. Lots of failures are only triggered by certain access paterns, which is why it's so hard to convince people that their memory is bad. The only reliable way to test memory is with a hardware testor, or swapping known good memory in. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 8:55: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2A07537B69E for ; Mon, 7 Aug 2000 08:55:06 -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 JAA87313; Mon, 7 Aug 2000 09:55:03 -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 JAA32390; Mon, 7 Aug 2000 09:54:47 -0600 (MDT) Message-Id: <200008071554.JAA32390@harmony.village.org> To: Stephen McKay Subject: Re: Ugly, slow shutdown Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 08 Aug 2000 00:17:48 +1000." <200008071417.AAA00524@gift.home> References: <200008071417.AAA00524@gift.home> <20000807011854.Q4854@fw.wintelcom.net> <200008070836.BAA02380@mass.osd.bsdi.com> <20000807015018.R4854@fw.wintelcom.net> Date: Mon, 07 Aug 2000 09:54:47 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008071417.AAA00524@gift.home> Stephen McKay writes: : And back to the simpler bit (the bike shed bit). Does everyone else actually : *like* the verbose messages currently used? And the gratuitous extra newline : in the "syncing..." message? I like the newer messages in your patch, but I don't care enough to bikeshed this :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 8:58: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5948337B5D2 for ; Mon, 7 Aug 2000 08:58: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 JAA87343; Mon, 7 Aug 2000 09:58:01 -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 JAA32453; Mon, 7 Aug 2000 09:57:45 -0600 (MDT) Message-Id: <200008071557.JAA32453@harmony.village.org> To: David Scheidt Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 07 Aug 2000 10:53:27 CDT." References: Date: Mon, 07 Aug 2000 09:57:45 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message David Scheidt writes: : convince people that their memory is bad. The only reliable way to test : memory is with a hardware testor, or swapping known good memory in. Yes. while (1) do ; make world; done is a close second to a hardware tester. I can't tell you the number of times I've had flakey systems that made people sure FreeBSD was busted. A new CPU, mobo or memory fixed these right up. Troubleshooting that can be interesting... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 9: 6: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id DF5EC37B7BF for ; Mon, 7 Aug 2000 09:05:57 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id LAA11093; Mon, 7 Aug 2000 11:05:55 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Mon, 7 Aug 2000 11:05:55 -0500 (CDT) From: David Scheidt To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: <200008071557.JAA32453@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, Warner Losh wrote: :In message David Scheidt writes: :: convince people that their memory is bad. The only reliable way to test :: memory is with a hardware testor, or swapping known good memory in. : :Yes. while (1) do ; make world; done is a close second to a hardware :tester. Ah, that tells you have a problem. It unfortunatly, doesn't distinguish a bad memory module from a bad memory bus. One of my abits blew up a bit ago with SIGSEGVs, I swapped memory in and around till I got to the point that I realized that as long as I didn't populate the last DIMM slot, it worked fine. It's not long for this earth, that machine. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 9:19:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 2C61C37B98C for ; Mon, 7 Aug 2000 09:19:06 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id MAA73188; Mon, 7 Aug 2000 12:19:11 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 7 Aug 2000 12:19:11 -0400 (EDT) From: "Brandon D. Valentine" To: David Scheidt Cc: current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, David Scheidt wrote: >Ah, that tells you have a problem. It unfortunatly, doesn't distinguish >a bad memory module from a bad memory bus. One of my abits blew up a bit >ago with SIGSEGVs, I swapped memory in and around till I got to the point >that I realized that as long as I didn't populate the last DIMM slot, it >worked fine. It's not long for this earth, that machine. Reminds me of the 4-5 SIMM pair on Tyan Tomcat P5 SMP motherboards. They're notorious for not working. I've got a pair of those boards and cannot put exactly 6 SIMMs despite the claims of requiring pairs. It *really* wants SIMMs installed 4 at a time. They were nice boards otherwise though. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 9:47:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843290.broadbandoffice.net [64.47.83.26]) by hub.freebsd.org (Postfix) with ESMTP id 496F337B50B; Mon, 7 Aug 2000 09:47:48 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id JAA36775; Mon, 7 Aug 2000 09:47:36 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 Aug 2000 09:47:36 -0700 (PDT) From: Matt Dillon Message-Id: <200008071647.JAA36775@earth.backplane.com> To: Mike Smith Cc: Alfred Perlstein , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown References: <200008070836.BAA02380@mass.osd.bsdi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> * Stephen McKay [000805 08:49] wrote: :> > :> > Patch 2 is smaller and possibly controversial. Normally bufdaemon and :> > syncer are sleeping when they are told to suspend. This delays shutdown :> > by a few boring seconds. With this patch, it is zippier. I expect people :> > to complain about this shortcut, but every sleeping process should expect :> > to be woken for no reason at all. Basic kernel premise. :> :> You better bet it's controversial, this isn't "Basic kernel premise" : :Actually, that depends. It is definitely poor programming practice to :not check the condition for which you slept on wakeup. : :> *boom* *crash* *ow* :) : :Doctor: So don't do that. I gotta agree. This is very bad programming practice. There are many, many places in the kernel where tsleep() is called with a 0 delay and assumed not to return until something meaningful happens. For example, for handling NFS retries, some of the locking code (I think), and I could probably find many others. In general 'quick hacks' only cause immense pain later on... sometimes years later on. It is NOT WORTH IT. In the case of buf_daemon, waking up the process is a definite no-no. You can wakeup &lbolt, but you can't just go wakeup the process willy-nilly -- it could be sitting anywhere. What I would suggest is to add another argument to the shutdown event-handler registration, an optional wakeup address. If NULL, no wakeup is performed. Otherwise a wakeup on the specified address is performed. You can then pass &lbolt to it when the syncer & buf_daemon processes register. That is a simple, safe solution. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 10: 3:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C49AF37B9BD; Mon, 7 Aug 2000 10:03:13 -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 TAA10028; Mon, 7 Aug 2000 19:03:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Mike Smith , Alfred Perlstein , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-Reply-To: Your message of "Mon, 07 Aug 2000 09:47:36 PDT." <200008071647.JAA36775@earth.backplane.com> Date: Mon, 07 Aug 2000 19:03:08 +0200 Message-ID: <10026.965667788@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008071647.JAA36775@earth.backplane.com>, Matt Dillon writes: >:> * Stephen McKay [000805 08:49] wrote: >:> > >:> > Patch 2 is smaller and possibly controversial. Normally bufdaemon and >:> > syncer are sleeping when they are told to suspend. This delays shutdown >:> > by a few boring seconds. With this patch, it is zippier. I expect people >:> > to complain about this shortcut, but every sleeping process should expect >:> > to be woken for no reason at all. Basic kernel premise. >:> >:> You better bet it's controversial, this isn't "Basic kernel premise" >: >:Actually, that depends. It is definitely poor programming practice to >:not check the condition for which you slept on wakeup. >: >:> *boom* *crash* *ow* :) >: >:Doctor: So don't do that. > > I gotta agree. This is very bad programming practice. There are many, > many places in the kernel where tsleep() is called with a 0 delay and > assumed not to return until something meaningful happens. For example, > for handling NFS retries, some of the locking code (I think), and I > could probably find many others. Then this code should be changed to do the right thing, which is to *always* check the condition being slept on before proceeding. -- 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 11:28:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EC71937BA0B; Mon, 7 Aug 2000 11:28:47 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e77IQCC08866; Mon, 7 Aug 2000 11:26:12 -0700 (PDT) Date: Mon, 7 Aug 2000 11:26:12 -0700 From: Alfred Perlstein To: Poul-Henning Kamp Cc: Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown Message-ID: <20000807112612.V4854@fw.wintelcom.net> References: <200008071647.JAA36775@earth.backplane.com> <10026.965667788@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <10026.965667788@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Aug 07, 2000 at 07:03:08PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Poul-Henning Kamp [000807 10:03] wrote: > In message <200008071647.JAA36775@earth.backplane.com>, Matt Dillon writes: > >:> * Stephen McKay [000805 08:49] wrote: > >:> > > >:> > Patch 2 is smaller and possibly controversial. Normally bufdaemon and > >:> > syncer are sleeping when they are told to suspend. This delays shutdown > >:> > by a few boring seconds. With this patch, it is zippier. I expect people > >:> > to complain about this shortcut, but every sleeping process should expect > >:> > to be woken for no reason at all. Basic kernel premise. > >:> > >:> You better bet it's controversial, this isn't "Basic kernel premise" > >: > >:Actually, that depends. It is definitely poor programming practice to > >:not check the condition for which you slept on wakeup. > >: > >:> *boom* *crash* *ow* :) > >: > >:Doctor: So don't do that. > > > > I gotta agree. This is very bad programming practice. There are many, > > many places in the kernel where tsleep() is called with a 0 delay and > > assumed not to return until something meaningful happens. For example, > > for handling NFS retries, some of the locking code (I think), and I > > could probably find many others. > > Then this code should be changed to do the right thing, which is > to *always* check the condition being slept on before proceeding. Can you give a reason why we'll have to now start coding defensively because our arguments to tsleep() are just "advisory" now? I'm not really sure why for a single reader/writer situation we have to have hysterics for a stray wakeup, it bloats code and is not needed in all places. I can also imagine some fun infinite loops like so: monitor issues wakeup producer wakes and terminates or goes away consumer spins checking on availability Also, one must now do this? timeo = currenttime + 2; while (timeo != currenttime) tsleep(timeo); ? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 11:34:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 3056037B94A; Mon, 7 Aug 2000 11:34:11 -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 UAA10528; Mon, 7 Aug 2000 20:34:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-Reply-To: Your message of "Mon, 07 Aug 2000 11:26:12 PDT." <20000807112612.V4854@fw.wintelcom.net> Date: Mon, 07 Aug 2000 20:34:03 +0200 Message-ID: <10526.965673243@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000807112612.V4854@fw.wintelcom.net>, Alfred Perlstein writes: >> Then this code should be changed to do the right thing, which is >> to *always* check the condition being slept on before proceeding. > >Can you give a reason why we'll have to now start coding defensively >because our arguments to tsleep() are just "advisory" now? It is not something we "suddenly have to do" it's been The Right Way even since I first sharpened my teeth on unix kernels many years ago. Coding defensively btw, is in the same category :-) >I can also imagine some fun infinite loops like so: > >monitor issues wakeup >producer wakes and terminates or goes away >consumer spins checking on availability This is wrong code. It should be: monitor issues wakeup producer wakes and terminates or goes away consumer spins checking on producer still present and on availability You'll find plenty examples of such code in the tty code. >Also, one must now do this? > > timeo = currenttime + 2; > while (timeo != currenttime) > tsleep(timeo); > >? If the exact duration of your timeout is important, you should always calibrate it against getmicrotime() or getmicrouptime() (depending on it being UTC locked or not). This has also always been the case. -- 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 12:21:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 41E2937B754; Mon, 7 Aug 2000 12:21:39 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA03649; Mon, 7 Aug 2000 12:03:43 -0700 (PDT) Message-Id: <200008071903.MAA03649@implode.root.com> To: Poul-Henning Kamp Cc: Alfred Perlstein , Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 20:34:03 +0200." <10526.965673243@critter.freebsd.dk> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Aug 2000 12:03:43 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Can you give a reason why we'll have to now start coding defensively >>because our arguments to tsleep() are just "advisory" now? > >It is not something we "suddenly have to do" it's been The Right Way >even since I first sharpened my teeth on unix kernels many years ago. Uh, Poul, I think you're full of it. The previous behavior of tsleep where you can make assumptions about who wakes you and under what conditions is a long and well established idiom. We (the kernel developers of BSD) have always coded to the established kernel programming interface and most of us consider it bad form to check for conditions which can't happen because the kernel API doesn't allow it. For example, we don't check for a NULL return from malloc in the case of !NO_WAIT, because we knew that the code would never do that. There are many other examples of similar assumptions in the kernel. We write the code to be efficient and only check for bogus conditions that might happen. The only exception to this is programatic ASSERTs that do internal consistency checks, but the purpose of those is quite different. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 12:52:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4F60F37BED3 for ; Mon, 7 Aug 2000 12:52:29 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id OAA23678; Mon, 7 Aug 2000 14:52:19 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 7 Aug 2000 14:52:19 -0500 (CDT) From: Chris Dillon To: David Scheidt Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: When Good DIMMS go Bad (or how I fixed my sig11) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Aug 2000, David Scheidt wrote: > On Mon, 7 Aug 2000, Warner Losh wrote: > > :In message David Scheidt writes: > :: convince people that their memory is bad. The only reliable way to test > :: memory is with a hardware testor, or swapping known good memory in. > : > :Yes. while (1) do ; make world; done is a close second to a hardware > :tester. > > Ah, that tells you have a problem. It unfortunatly, doesn't distinguish > a bad memory module from a bad memory bus. One of my abits blew up a bit > ago with SIGSEGVs, I swapped memory in and around till I got to the point > that I realized that as long as I didn't populate the last DIMM slot, it > worked fine. It's not long for this earth, that machine. Many motherboards are unstable when you populate all DIMM slots. You generally have limitations to what types of DIMMs you can use (i.e. single-sided only, registered only, etc.) when you do populate all of them. The manual _should_ specify these limitations. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 13: 2:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843290.broadbandoffice.net [64.47.83.26]) by hub.freebsd.org (Postfix) with ESMTP id 4FF9337BEDE; Mon, 7 Aug 2000 13:02:40 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.9.3/8.9.3) id NAA38592; Mon, 7 Aug 2000 13:02:37 -0700 (PDT) (envelope-from dillon) Date: Mon, 7 Aug 2000 13:02:37 -0700 (PDT) From: Matt Dillon Message-Id: <200008072002.NAA38592@earth.backplane.com> To: David Greenman Cc: Poul-Henning Kamp , Alfred Perlstein , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown References: <200008071903.MAA03649@implode.root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick perusal of the kernel code shows a number of possible unexpected side effects from unexpected wakeups. I see several places where a 'WANTED' flag is set in a loop waiting for something and assumed to be cleared after the tsleep() returns. Some of these side effects are quite persistent. For example, if PG_WANTED is set in a page the VM system will activate the page rather then deactivate it. An unexpected wakeup in the VM system could lead to a page with PG_WANTED *LEFT* *SET* on the page! It might not be fatal, but it sure isn't the type of operation we want! There are a couple of places in the NFS code where a sleep wakeup results in a retry. There is a place where LC_EXPIREDWANTED is checked and causes a whole sequence of conditionals to be skipped. This is after 5 minutes of searching. I'm not going to spend N hours trying to find every case. Just finding two in 5 minutes is enough proof for me that it's just too dangerous to go and change expected tsleep/wakeup semantics without going through and auditing and documenting every piece of code that uses tsleep/wakeup. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 13:13:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx6.port.ru (mx6.port.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 80DF037B9D2 for ; Mon, 7 Aug 2000 13:13:07 -0700 (PDT) (envelope-from kolygin@mail.ru) Received: from f10.int ([10.0.0.78] helo=f10.mail.ru) by mx6.port.ru with esmtp (Exim 3.14 #4) id 13LtGj-0009ff-00 for freebsd-current@freebsd.org; Tue, 08 Aug 2000 00:13:05 +0400 Received: from mail by f10.mail.ru with local (Exim 3.14 #4) id 13LtGj-000J9f-00 for freebsd-current@FreeBSD.ORG; Tue, 08 Aug 2000 00:13:05 +0400 Received: from [194.85.81.203] by win.mail.port.ru with HTTP; Mon, 07 Aug 2000 20:13:05 +0000 (GMT) From: "äÅÎÉÓ á. ëÏÌÙÇÉÎ" To: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [194.85.81.203] Reply-To: "äÅÎÉÓ á. ëÏÌÙÇÉÎ" Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Date: Tue, 08 Aug 2000 00:13:05 +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 76254f08 unsubscribe freebsd-current kolygin@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 14:56:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id 789CD37BC09; Mon, 7 Aug 2000 14:56:27 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mailgate.originative.co.uk (Postfix) with ESMTP id 63AA01D13D; Mon, 7 Aug 2000 22:56:25 +0100 (BST) Message-ID: <398F3089.416DEA1@originative.co.uk> Date: Mon, 07 Aug 2000 22:56:25 +0100 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: dg@root.com Cc: Poul-Henning Kamp , Alfred Perlstein , Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown References: <200008071903.MAA03649@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >>Can you give a reason why we'll have to now start coding defensively > >>because our arguments to tsleep() are just "advisory" now? > > > >It is not something we "suddenly have to do" it's been The Right Way > >even since I first sharpened my teeth on unix kernels many years ago. > > Uh, Poul, I think you're full of it. The previous behavior of tsleep where > you can make assumptions about who wakes you and under what conditions is a > long and well established idiom. We (the kernel developers of BSD) have always > coded to the established kernel programming interface and most of us consider > it bad form to check for conditions which can't happen because the kernel > API doesn't allow it. For example, we don't check for a NULL return from malloc > in the case of !NO_WAIT, because we knew that the code would never do that. > There are many other examples of similar assumptions in the kernel. We write > the code to be efficient and only check for bogus conditions that might > happen. The only exception to this is programatic ASSERTs that do internal > consistency checks, but the purpose of those is quite different. In the particular case of sleeping though, a woken process does need to check the condition that it slept on because one of the other processes sleeping on that resource may have had a chance to run first and changed some state. So as a general rule, you shouldn't assume that everything is fine when you return from being asleep because it might not be. I agree with your sentiment about defensive coding in the kernel though. Defensive coding should only be used on the boundary of your interface, i.e. if you're getting non-deterministic data from somewhere, most commonly user behaviour. Everything inside the kernel implementation should be deterministic and therefore there shouldn't be any need for defensive programming. Any cause of errors that defensive programming catches in the kernel can only be caused by bugs and therefore falls into the category of diagnostics. There's actually a lot of defensive programming creeping into the kernel which should really be wrapped in an #ifdef INVARIANTS. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 15: 7:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id BA5F837B90F; Mon, 7 Aug 2000 15:07:29 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA04253; Mon, 7 Aug 2000 14:49:34 -0700 (PDT) Message-Id: <200008072149.OAA04253@implode.root.com> To: Paul Richards Cc: Poul-Henning Kamp , Alfred Perlstein , Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 22:56:25 BST." <398F3089.416DEA1@originative.co.uk> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Aug 2000 14:49:34 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In the particular case of sleeping though, a woken process does need to >check the condition that it slept on because one of the other processes >sleeping on that resource may have had a chance to run first and changed >some state. So as a general rule, you shouldn't assume that everything >is fine when you return from being asleep because it might not be. No, that's not true, and there are many examples in the kernel where a bogus wakeup would lead to bad things happening. I recall some code in the advisory locking code, and VM system, that assume that there is only one wakeup event and that the thing causing it assures that certain other things have occured before issuing it. That's just the way it has worked since the dawn of time. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 15:21:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id BF5C237B8DF; Mon, 7 Aug 2000 15:21:51 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mailgate.originative.co.uk (Postfix) with ESMTP id 4CB961D13D; Mon, 7 Aug 2000 23:21:48 +0100 (BST) Message-ID: <398F367C.27DD39DA@originative.co.uk> Date: Mon, 07 Aug 2000 23:21:48 +0100 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: dg@root.com Cc: Poul-Henning Kamp , Alfred Perlstein , Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown References: <200008072149.OAA04253@implode.root.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > > >In the particular case of sleeping though, a woken process does need to > >check the condition that it slept on because one of the other processes > >sleeping on that resource may have had a chance to run first and changed > >some state. So as a general rule, you shouldn't assume that everything > >is fine when you return from being asleep because it might not be. > > No, that's not true, and there are many examples in the kernel where a > bogus wakeup would lead to bad things happening. I recall some code in the > advisory locking code, and VM system, that assume that there is only one > wakeup event and that the thing causing it assures that certain other > things have occured before issuing it. That's just the way it has worked > since the dawn of time. I did say "as a general rule". If you know that "by design" nothing else is going to mess with what you're sleeping on before you wake up then you can make tighter optimisations but that's not the general case. There is such a thing as over optimisation though and for the sake of a simple if statement it is probably better to write code that is robust to changes made elsewhere in the system rather than squeeze every inch of performance out of the code, unless there's a real need to optimize in that particular area. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 15:33:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 7C12D37BBAD; Mon, 7 Aug 2000 15:33:34 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id PAA04340; Mon, 7 Aug 2000 15:14:57 -0700 (PDT) Message-Id: <200008072214.PAA04340@implode.root.com> To: Paul Richards Cc: Poul-Henning Kamp , Alfred Perlstein , Matt Dillon , Mike Smith , Stephen McKay , freebsd-current@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 23:21:48 BST." <398F367C.27DD39DA@originative.co.uk> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Aug 2000 15:14:56 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I did say "as a general rule". If you know that "by design" nothing else >is going to mess with what you're sleeping on before you wake up then >you can make tighter optimisations but that's not the general case. >There is such a thing as over optimisation though and for the sake of a >simple if statement it is probably better to write code that is robust >to changes made elsewhere in the system rather than squeeze every inch >of performance out of the code, unless there's a real need to optimize >in that particular area. In some cases it isn't practical or very expensive to verify that the condition that caused the sleep in the first place has been satisfied - that's often why certain parts of the kernel rely on the established tsleep symantics. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 16: 3: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from manatee.mammalia.org (manatee.mammalia.org [216.231.50.6]) by hub.freebsd.org (Postfix) with ESMTP id CAA5137B891 for ; Mon, 7 Aug 2000 16:03:07 -0700 (PDT) (envelope-from rjoseph@mammalia.org) Received: by manatee.mammalia.org (Postfix, from userid 1000) id 500F511CD18; Mon, 7 Aug 2000 16:03:07 -0700 (PDT) Date: Mon, 7 Aug 2000 16:03:07 -0700 From: R Joseph Wright To: freebsd-current Subject: mouse madness under X Message-ID: <20000807160307.A81627@mammalia.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a problem I've had starting with the last couple of builds. If I switch from X to a virtual console, then back again, *sometimes* the mouse cursor will be stuck on the right hand side of the screen. I can move it up and down, but not side to side. The way to cure the problem is to go back to the console, wait a few seconds, then come back into X. The problem goes away. At first I thought this was a problem with my wm, but I tried a different one and got the same result. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 17: 0:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4F72C37B50C for ; Mon, 7 Aug 2000 17:00:39 -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 RAA03445; Mon, 7 Aug 2000 17:00:36 -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 RAA40298; Mon, 7 Aug 2000 17:00:36 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 7 Aug 2000 17:00:36 -0700 (PDT) Message-Id: <200008080000.RAA40298@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: bright@wintelcom.net Subject: Re: Ugly, slow shutdown In-Reply-To: <20000807112612.V4854@fw.wintelcom.net> References: <200008071647.JAA36775@earth.backplane.com> <10026.965667788@critter.freebsd.dk> <20000807112612.V4854@fw.wintelcom.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000807112612.V4854@fw.wintelcom.net>, Alfred Perlstein wrote: > * Poul-Henning Kamp [000807 10:03] wrote: > > > > Then this code should be changed to do the right thing, which is > > to *always* check the condition being slept on before proceeding. > > Can you give a reason why we'll have to now start coding defensively > because our arguments to tsleep() are just "advisory" now? > > I'm not really sure why for a single reader/writer situation we have > to have hysterics for a stray wakeup, it bloats code and is not needed > in all places. It is just basic good programming practice. In his classic paper, "An Introduction to Programming with Threads" [1] Andrew Birrell argues for the explicit test in his discussion of condition variables, which are very similar to the kernel's tsleep/wakeup constructs. After giving a couple of purely technical reasons, he goes on to say: But the main reason for advocating use of this pattern is to make your program more obviously, and more robustly, correct. With this style it is immediately clear that the "expression" is true before the following statements are executed. Without it, this fact could be verified only by looking at all the places that might signal the condition variable. In other words, this programming convention allows you to verify correctness by local inspection, which is always preferable to global inspection. I will add that this is the pattern that Kirk teaches in his kernel internals class. [1] http://gatekeeper.dec.com/pub/DEC/SRC/research-reports/abstracts/src-rr-035.html 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 18:51: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id D981337B5A9 for ; Mon, 7 Aug 2000 18:50:59 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA04815; Mon, 7 Aug 2000 18:35:59 -0700 (PDT) Message-Id: <200008080135.SAA04815@implode.root.com> To: current@FreeBSD.ORG Cc: bright@wintelcom.net Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 17:00:36 PDT." <200008080000.RAA40298@vashon.polstra.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Aug 2000 18:35:59 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I will add that this is the pattern that Kirk teaches in his kernel >internals class. If that's true, then he should practice what he preaches. Some of the code that I'm refering to (e.g. lockf) was apparantly written by him. I'll say again, however, that some of the cases that rely on the historical symantics would become very expensive if they had to go through a series of complex checks (perhaps list traversals, etc), in order to verify that the wakeup wasn't bogus. I personally don't think this is an improvement. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 19:38:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9BDB237B53C for ; Mon, 7 Aug 2000 19:38:20 -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 TAA03786; Mon, 7 Aug 2000 19:38:08 -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 TAA40871; Mon, 7 Aug 2000 19:38:07 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Mon, 7 Aug 2000 19:38:07 -0700 (PDT) Message-Id: <200008080238.TAA40871@vashon.polstra.com> To: current@freebsd.org Reply-To: current@freebsd.org Cc: dg@root.com Subject: Re: Ugly, slow shutdown In-Reply-To: <200008080135.SAA04815@implode.root.com> References: <200008080135.SAA04815@implode.root.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008080135.SAA04815@implode.root.com>, David Greenman wrote: > >I will add that this is the pattern that Kirk teaches in his kernel > >internals class. > > If that's true, Do you want me to fax you a copy of page 15 of his class notes from the course he gave at last year's FreeBSDCon, or will you just take my word for it? > then he should practice what he preaches. Some of the code that I'm > refering to (e.g. lockf) was apparantly written by him. Whether Kirk practices what he preaches is irrelevant to this discussion. Instead of focusing on a 1-sentence "I will add ..." from my posting, why not respond to the main thrust of it -- the paragraph I quoted from the Birrell paper? > I'll say again, however, that some of the cases that rely on the > historical symantics would become very expensive if they had to go > through a series of complex checks (perhaps list traversals, etc), > in order to verify that the wakeup wasn't bogus. I personally don't > think this is an improvement. Some of them might be expensive, but most of them would not. Obviously the waker-upper knows that the condition is true. Otherwise the existing code which doesn't check wouldn't work. In the expensive cases the waker-upper could simply set a flag for the sleeper to check. Note, I am not expressing an opinion about whether the sleeps should be terminated prematurely during shutdown. But I am expressing a strong opinion about whether sleepers should do a reality check before proceeding. 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-current" in the body of the message From owner-freebsd-current Mon Aug 7 22:34:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 48F0437B6AA for ; Mon, 7 Aug 2000 22:34:26 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id HAA45245 for freebsd-current@freebsd.org; Tue, 8 Aug 2000 07:34:19 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.9.3) with ESMTP id e785Y0553659 for ; Tue, 8 Aug 2000 07:34:04 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Tue, 8 Aug 2000 07:33:54 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: inheriting certificate trust Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a verisign'ed certificate for our webserver. According to Microsoft explorer/outlook, it can be used for verifying the servers identity, but not for mail. I've used this certificate to sign a new certificate, and Microsoft recognizes it and the trust chain, and will use it for verifying the servers identity, but not for mail. According to openssl x509, both certificates are usable for smime. Can I use the webserver certificate to make mail-certificates, or is it because the root CA at verisign is not for mail, then none of its children can be for mail? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 23:13:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id D01CA37B6AF for ; Mon, 7 Aug 2000 23:13:19 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA05458 for ; Mon, 7 Aug 2000 22:58:17 -0700 (PDT) Message-Id: <200008080558.WAA05458@implode.root.com> To: current@freebsd.org Subject: Re: Ugly, slow shutdown In-reply-to: Your message of "Mon, 07 Aug 2000 19:38:07 PDT." <200008080238.TAA40871@vashon.polstra.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Aug 2000 22:58:17 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In article <200008080135.SAA04815@implode.root.com>, David Greenman > wrote: >> >I will add that this is the pattern that Kirk teaches in his kernel >> >internals class. >> >> If that's true, > >Do you want me to fax you a copy of page 15 of his class notes from >the course he gave at last year's FreeBSDCon, or will you just take my >word for it? I'm not calling you a liar. I think it is possible that you may have misunderstood what Kirk was saying, however. Having not been in the class myself, it is perhaps a bit presumptuous for me to think that. There are cases where one must check for the condition after the wakeup - the cases where multiple sleepers/consumers are waiting on the same condition/resource, for example. ...and there are cases that simply don't work that way and aren't suseptible to that inherent race condition. Is it possible that Kirk was speaking about the race condition cases? >> then he should practice what he preaches. Some of the code that I'm >> refering to (e.g. lockf) was apparantly written by him. > >Whether Kirk practices what he preaches is irrelevant to this >discussion. Instead of focusing on a 1-sentence "I will add ..." from >my posting, why not respond to the main thrust of it -- the paragraph >I quoted from the Birrell paper? Because I haven't decided whether I agree with it or not. I think an argument could be made that adding the checks in a case where a bogus wakeup can never happen might actually obscure the code by leading the programmer into thinking that there could be multiple sleepers/consumers. Perhaps I read more into code than I should, but I naturally assume that if a check is made for something then the condition being checked for can happen. If it cannot, then that just leads me astray. Certainly comments are a good thing to keep people on the right path, but then this applies whether you check the post-tsleep state or not. >> I'll say again, however, that some of the cases that rely on the >> historical symantics would become very expensive if they had to go >> through a series of complex checks (perhaps list traversals, etc), >> in order to verify that the wakeup wasn't bogus. I personally don't >> think this is an improvement. > >Some of them might be expensive, but most of them would not. That could be - I honestly don't know and it seems to me that a thorough code review would be needed before a conclusion can be drawn. >Obviously the waker-upper knows that the condition is true. Otherwise >the existing code which doesn't check wouldn't work. In the expensive >cases the waker-upper could simply set a flag for the sleeper to >check. For me, that doesn't make the code easier to read or understand - it has the opposite effect. ...but then I'm used to the historical symantics and naturally consider the possible cases when looking at the code. >Note, I am not expressing an opinion about whether the sleeps should >be terminated prematurely during shutdown. But I am expressing a >strong opinion about whether sleepers should do a reality check before >proceeding. I could be persuaded to think that way, but I still remain unconvinced. Again, I'm used to the historical symantics, so changing them requires a pretty good justification and a bit of brain rewiring, which I naturally resist. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 7 23:45:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from marge.mikom.csir.co.za (marge.mikom.csir.co.za [146.64.28.1]) by hub.freebsd.org (Postfix) with ESMTP id 05A1237BD2A for ; Mon, 7 Aug 2000 23:44:59 -0700 (PDT) (envelope-from jhugo@mikom.csir.co.za) Received: from garfield.mikom.csir.co.za (d-25-185.mikom.csir.co.za [146.64.25.185]) by marge.mikom.csir.co.za (8.9.3/8.9.3) with SMTP id IAA08491 for ; Tue, 8 Aug 2000 08:44:42 +0200 (SAST) (envelope-from jhugo@mikom.csir.co.za) From: Johann Hugo Organization: CSIR To: freebsd-current@FreeBSD.ORG Subject: Re: mouse madness under X Date: Tue, 8 Aug 2000 08:38:40 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20000807160307.A81627@mammalia.org> In-Reply-To: <20000807160307.A81627@mammalia.org> MIME-Version: 1.0 Message-Id: <00080808453400.09984@garfield.mikom.csir.co.za> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 08 Aug 2000, you wrote: > This is a problem I've had starting with the last couple of builds. If I > switch from X to a virtual console, then back again, *sometimes* the mouse > cursor will be stuck on the right hand side of the screen. I can move it up > and down, but not side to side. The way to cure the problem is to go back > to the console, wait a few seconds, then come back into X. The problem goes > away. At first I thought this was a problem with my wm, but I tried a > different one and got the same result. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I've experienced the same mouse problem yesterday. I eventually had to restarted moused to cure the problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 0:51:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id CCC3D37B69A for ; Tue, 8 Aug 2000 00:51:02 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e787p0r29468; Tue, 8 Aug 2000 00:51:00 -0700 (PDT) Date: Tue, 8 Aug 2000 00:51:00 -0700 From: Alfred Perlstein To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: Ugly, slow shutdown Message-ID: <20000808005100.A4854@fw.wintelcom.net> References: <200008080238.TAA40871@vashon.polstra.com> <200008080558.WAA05458@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200008080558.WAA05458@implode.root.com>; from dg@root.com on Mon, Aug 07, 2000 at 10:58:17PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Greenman [000807 23:15] wrote: > >In article <200008080135.SAA04815@implode.root.com>, David Greenman > > wrote: > > >Obviously the waker-upper knows that the condition is true. Otherwise > >the existing code which doesn't check wouldn't work. In the expensive > >cases the waker-upper could simply set a flag for the sleeper to > >check. > > For me, that doesn't make the code easier to read or understand - it has > the opposite effect. ...but then I'm used to the historical symantics and > naturally consider the possible cases when looking at the code. > > >Note, I am not expressing an opinion about whether the sleeps should > >be terminated prematurely during shutdown. But I am expressing a > >strong opinion about whether sleepers should do a reality check before > >proceeding. > > I could be persuaded to think that way, but I still remain unconvinced. > Again, I'm used to the historical symantics, so changing them requires a > pretty good justification and a bit of brain rewiring, which I naturally > resist. It's not just that, if you always have to cover your behind when doing tsleep you may wind up masking wakeup bugs. Places like "vfs_bio.c" line 586 of 3182: bp->b_xflags |= BX_BKGRDWAIT; tsleep(&bp->b_xflags, PRIBIO, "biord", 0); if (bp->b_xflags & BX_BKGRDINPROG) panic("bwrite: still writing"); } If replaced by a while() _may_ obscure a buffercache bug. Personally I'd like to be able to catch such bugs than let them go because the API (wakeups can happen at any time) prohibits this. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 7: 5:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C045537B559 for ; Tue, 8 Aug 2000 07:05:27 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA13534; Tue, 8 Aug 2000 10:05:13 -0400 (EDT) (envelope-from wollman) Date: Tue, 8 Aug 2000 10:05:13 -0400 (EDT) From: Garrett Wollman Message-Id: <200008081405.KAA13534@khavrinen.lcs.mit.edu> To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: inheriting certificate trust In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I've used this certificate to sign a new certificate, and Microsoft > recognizes it and the trust chain, and will use it for verifying the > servers identity, but not for mail. My guess is that (regardless of the software issues involved) you've just violated your agreement with Veri$ign. I would not be surprised if Exploder and Outbreak will only accept a certificate for one purpose, regardless of how many options are set in the certificate's keyUsage. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 10: 3:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 3B6B037B5CE for ; Tue, 8 Aug 2000 10:03:17 -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 LAA05203; Tue, 8 Aug 2000 11:03:12 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id LAA28034; Tue, 8 Aug 2000 11:02:53 -0600 (MDT) (envelope-from nate) Date: Tue, 8 Aug 2000 11:02:53 -0600 (MDT) Message-Id: <200008081702.LAA28034@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alfred Perlstein Cc: David Greenman , current@FreeBSD.ORG Subject: Re: Ugly, slow shutdown In-Reply-To: <20000808005100.A4854@fw.wintelcom.net> References: <200008080238.TAA40871@vashon.polstra.com> <200008080558.WAA05458@implode.root.com> <20000808005100.A4854@fw.wintelcom.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's not just that, if you always have to cover your behind when > doing tsleep you may wind up masking wakeup bugs. Places like > "vfs_bio.c" line 586 of 3182: > > bp->b_xflags |= BX_BKGRDWAIT; > tsleep(&bp->b_xflags, PRIBIO, "biord", 0); > if (bp->b_xflags & BX_BKGRDINPROG) > panic("bwrite: still writing"); > } > > If replaced by a while() _may_ obscure a buffercache bug. > > Personally I'd like to be able to catch such bugs than let them go > because the API (wakeups can happen at any time) prohibits this. No in a fully threaded world..... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 15:44:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id AE55D37B824; Tue, 8 Aug 2000 15:44:10 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.9.3/8.8.8) id PAA04819; Tue, 8 Aug 2000 15:44:09 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200008082244.PAA04819@ns.altadena.net> Subject: crypt(3) problems To: current@freebsd.org Date: Tue, 8 Aug 2000 15:44:09 -0700 (PDT) Cc: stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are many cases (e.g. apache with external sources doing crypt) where it is necessary to have libscrypt the default crypt for logins, etc, and libdescrypt available for linking (e.g. apache). Since the realignment of crypt sources to the internat versions (which I generally like), this is not possible without a change to the makefile in /usr/src/secure/lib/libcrypt so that LCRYPTBASE is libdescrypt and NOT libcrypt. The corresponding change may be needed in libscrypt sources too? There are also cases (generating passwords for cisco) where the opposite is needed. The bottom line is that if one asks explicitly for either -ldescrypt or -lscrypt it should get ONLY that library and not the other, independent of the symlinks. This was working fine till the merge of usa and internat versions. There was other related heartburn but I finally discovered the change to make.conf that fixed it :-) -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 16: 6:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D7B9B37B7CC; Tue, 8 Aug 2000 16:06:29 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Tue, 8 Aug 2000 18:42:52 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Pete Carah Cc: current@freebsd.org, stable@freebsd.org Subject: Re: crypt(3) problems In-Reply-To: <200008082244.PAA04819@ns.altadena.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We should switch to using just libdescrypt and being allowed to switch crypt formats easily between md5 and des. My proposed solution using login.conf is at http://people.FreeBSD.org/~green/crypt_switching.patch, and it's going to be put into production usage relatively soon (that is, whether or not it's actually in FreeBSD). -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 16:59:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 98B6A37B89A for ; Tue, 8 Aug 2000 16:59:36 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.63]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000809005842.DLR3760.mta02-svc.ntlworld.com@parish.my.domain> for ; Wed, 9 Aug 2000 00:58:42 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA04803 for current@freebsd.org; Wed, 9 Aug 2000 00:59:30 +0100 (BST) (envelope-from mark) Date: Wed, 9 Aug 2000 00:59:29 +0100 From: Mark Ovens To: current@freebsd.org Subject: Request for review/comments - new option for uname(1) Message-ID: <20000809005929.K250@parish> Reply-To: Mark Ovens Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit The output of ``uname -a'' appears in hundreds of e-mails and PRs yet the output format is not ideal for this (especially e-mail in 80-column mail readers) as it is a single line. Attached is a patch for an enhancement I've made that adds a new option ``-A'' (rather than change ``-a'') that splits it up into 3 lines thus making it better for including verbatim in e-mails and PRs: # uname -A FreeBSD parish 4.1-STABLE FreeBSD 4.1-STABLE #0: Tue Aug 8 00:51:02 BST 2000 mark@parish:/usr/src/sys/compile/PARISH i386 The only thing I couldn't work out is why sysctl() adds 5 spaces after the date sub-string, so I've haven't stripped them out (hence the indented third line). Is there any reason why this is unacceptable and could not be committed? BTW, please Cc: me. Thanks for your time. -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Description: Diff for uname.c Content-Disposition: attachment; filename="uname.diff" --- uname.c.orig Tue Aug 8 21:32:36 2000 +++ uname.c Tue Aug 8 21:53:20 2000 @@ -61,16 +61,20 @@ #define RFLAG 0x04 #define SFLAG 0x08 #define VFLAG 0x10 +#define AFLAG 0x20 u_int flags; int ch, mib[2]; size_t len, tlen; char *p, *prefix, buf[1024]; flags = 0; - while ((ch = getopt(argc, argv, "amnprsv")) != -1) + while ((ch = getopt(argc, argv, "Aamnprsv")) != -1) switch(ch) { + case 'A': case 'a': flags |= (MFLAG | NFLAG | RFLAG | SFLAG | VFLAG); + if (ch == 'A') + flags |= AFLAG; break; case 'p': case 'm': @@ -137,9 +141,22 @@ len = sizeof(buf); if (sysctl(mib, 2, &buf, &len, NULL, 0) == -1) err(1, "sysctl"); - for (p = buf, tlen = len; tlen--; ++p) - if (*p == '\n' || *p == '\t') - *p = ' '; + + if (flags & AFLAG) { + for (p = buf, tlen = len; tlen--; ++p) + if (*p == ':') { + *++p = '\n'; + break; + } + + if (buf[strlen(buf) - 1] == '\n') + buf[strlen(buf) - 1] = '\0'; + } else { + for (p = buf, tlen = len; tlen--; ++p) + if (*p == '\n' || *p == '\t') + *p = ' '; + } + (void)printf("%s%.*s", prefix, (int)len, buf); prefix = " "; } --82I3+IH0IqGh5yIs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 20:26:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from Millenium.kabsi.at (radio.kabsi.at [195.202.128.3]) by hub.freebsd.org (Postfix) with ESMTP id AFFD237B6E7 for ; Tue, 8 Aug 2000 20:26:49 -0700 (PDT) (envelope-from entropy@kabsi.at) Received: from reality.kabsi.at (hell@[195.202.183.184]) by Millenium.kabsi.at (8.9.3/8.9.3) with ESMTP id FAA19191 for ; Wed, 9 Aug 2000 05:32:31 +0200 Message-Id: <5.0.0.11.2.20000809051808.00a52fc0@mail.kabsi.at> X-Sender: e1977a01@mail.kabsi.at X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.11 (Beta) Date: Wed, 09 Aug 2000 05:20:59 +0200 To: current@FreeBSD.ORG From: Alexander Sanda Subject: Re: emu10k1 problems solved In-Reply-To: <20000807091550.A364@cloaked.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:15 07.08.2000 +0200, Benedikt Schmidt wrote: >Just wanted to say that with the recent changes in the >emu10k1 driver all my problems with it have disappeared. > >There are no more "dodgy irq" messages >and the sound quality has improved too (no more crackling). Just a quick question... Is it possible to get this driver working under 4.1-STABLE aswell, or are the changes in the -current kernel already too big? Or is it officially planned to merge this updated driver into the -STABLE branch? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:16:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mr.usu.edu (mr.usu.edu [129.123.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 14E5637B99D for ; Tue, 8 Aug 2000 21:16:29 -0700 (PDT) (envelope-from irwanhadi@iname.com) Received: from sl585 (sl585.dorms.usu.edu [129.123.238.132]) by mr.usu.edu (Postfix) with ESMTP id AED491D2BE for ; Tue, 8 Aug 2000 22:16:27 -0600 (MDT) Message-Id: <4.2.0.58.20000808221617.00a98480@staf.bpkpenabur.or.id> X-Nil: Date: Tue, 08 Aug 2000 22:16:25 -0600 To: freebsd-current@freebsd.org From: Irwan Hadi Subject: hotmail now running win2000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sigh http://www.netcraft.com/whats/?host=www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id EE02D37BD9F for ; Tue, 8 Aug 2000 21:23:22 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id AAA61610; Wed, 9 Aug 2000 00:28:35 -0400 (EDT) From: Brian Hechinger Message-Id: <200008090428.AAA61610@entropy.tmok.com> Subject: Re: hotmail now running win2000 In-Reply-To: <4.2.0.58.20000808221617.00a98480@staf.bpkpenabur.or.id> from Irwan Hadi at "Aug 8, 2000 10:16:25 pm" To: irwanhadi@iname.com (Irwan Hadi) Date: Wed, 9 Aug 2000 00:28:35 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Irwan Hadi drunkenly mumbled... > Sigh http://www.netcraft.com/whats/?host=www.hotmail.com not on all the machines however. re-run the query, sometimes you get: www.hotmail.com is running Apache/1.3.6 (Unix) mod_ssl/2.2.8 SSLeay/0.9.0b on FreeBSD got both goin. just in case w2k didn't make the grade i assume. -brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:29:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from falcon.home.hentschel.net (d83b0468.dsl.flashcom.net [216.59.4.104]) by hub.freebsd.org (Postfix) with ESMTP id 4BEA937B548 for ; Tue, 8 Aug 2000 21:29:07 -0700 (PDT) (envelope-from thomas@hentschel.net) Received: from hentschel.net (thomas@localhost [127.0.0.1]) by falcon.home.hentschel.net (8.9.3/8.9.3) with ESMTP id VAA55899; Tue, 8 Aug 2000 21:29:45 -0700 (PDT) (envelope-from thomas@hentschel.net) Message-Id: <200008090429.VAA55899@falcon.home.hentschel.net> Date: Tue, 8 Aug 2000 21:29:44 -0700 (PDT) From: thomas@hentschel.net Subject: Re: hotmail now running win2000 (not all of it) To: Irwan Hadi Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <4.2.0.58.20000808221617.00a98480@staf.bpkpenabur.or.id> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 Aug, Irwan Hadi wrote: > Sigh http://www.netcraft.com/whats/?host=www.hotmail.com www.hotmail.com is running Apache/1.3.6 (Unix) mod_ssl/2.2.8 SSLeay/0.9.0b on FreeBSD at least on my query. Every 3rd query comes up with W2k. This time they approaching this a bit more careful ... -Th To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:30:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mr.usu.edu (mr.usu.edu [129.123.1.3]) by hub.freebsd.org (Postfix) with ESMTP id B0A6837B548 for ; Tue, 8 Aug 2000 21:30:48 -0700 (PDT) (envelope-from irwanhadi@iname.com) Received: from sl585 (sl585.dorms.usu.edu [129.123.238.132]) by mr.usu.edu (Postfix) with ESMTP id 0238D1D2C3; Tue, 8 Aug 2000 22:30:46 -0600 (MDT) Message-Id: <4.2.0.58.20000808222949.00a86390@staf.bpkpenabur.or.id> X-Nil: Date: Tue, 08 Aug 2000 22:30:44 -0600 To: wonko@entropy.tmok.com From: Irwan Hadi Subject: Re: hotmail now running win2000 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200008090428.AAA61610@entropy.tmok.com> References: <4.2.0.58.20000808221617.00a98480@staf.bpkpenabur.or.id> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:28 AM 8/9/00 -0400, Brian Hechinger wrote: >Irwan Hadi drunkenly mumbled... > > Sigh http://www.netcraft.com/whats/?host=www.hotmail.com > >not on all the machines however. re-run the query, sometimes you get: > >www.hotmail.com is running Apache/1.3.6 (Unix) mod_ssl/2.2.8 SSLeay/0.9.0b >on FreeBSD > >got both goin. just in case w2k didn't make the grade i assume. But I guess soon they will change all their freeBSD servers ;( and I wonder, how many people should be employed by Microsoft, just to press the restart button at their 2000 servers for Hotmail, in case they got BSOD ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:39:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id BFA1637B9FA for ; Tue, 8 Aug 2000 21:39:34 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id AAA61833; Wed, 9 Aug 2000 00:44:47 -0400 (EDT) From: Brian Hechinger Message-Id: <200008090444.AAA61833@entropy.tmok.com> Subject: Re: hotmail now running win2000 In-Reply-To: <4.2.0.58.20000808222949.00a86390@staf.bpkpenabur.or.id> from Irwan Hadi at "Aug 8, 2000 10:30:44 pm" To: irwanhadi@iname.com (Irwan Hadi) Date: Wed, 9 Aug 2000 00:44:47 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Irwan Hadi drunkenly mumbled... > > But I guess soon they will change all their freeBSD servers ;( > and I wonder, how many people should be employed by Microsoft, just to > press the restart button at their 2000 servers for Hotmail, in case they > got BSOD ? it's called the APC MasterSwitch (or similar peoduct by alternate vendor) reboot machines over the network. takes the place of 64.2% of all people employed with the word microsoft in their title. -b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:48:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mr.usu.edu (mr.usu.edu [129.123.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 2E07C37B6AE for ; Tue, 8 Aug 2000 21:48:49 -0700 (PDT) (envelope-from irwanhadi@iname.com) Received: from sl585 (sl585.dorms.usu.edu [129.123.238.132]) by mr.usu.edu (Postfix) with ESMTP id BF6531D2C6; Tue, 8 Aug 2000 22:48:45 -0600 (MDT) Message-Id: <4.2.0.58.20000808224658.00a83c70@staf.bpkpenabur.or.id> X-Nil: Date: Tue, 08 Aug 2000 22:48:43 -0600 To: wonko@entropy.tmok.com From: Irwan Hadi Subject: Re: hotmail now running win2000 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200008090444.AAA61833@entropy.tmok.com> References: <4.2.0.58.20000808222949.00a86390@staf.bpkpenabur.or.id> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:44 AM 8/9/00 -0400, Brian Hechinger wrote: >Irwan Hadi drunkenly mumbled... > > > > But I guess soon they will change all their freeBSD servers ;( > > and I wonder, how many people should be employed by Microsoft, just to > > press the restart button at their 2000 servers for Hotmail, in case they > > got BSOD ? > >it's called the APC MasterSwitch (or similar peoduct by alternate vendor) > >reboot machines over the network. takes the place of 64.2% of all people >employed with the word microsoft in their title. Including MCSE, MCP , etc ? ;) :) BTW how can the administrator of hotmail determine if a server is BSOD or not then ?, because they have 2000 servers and I think without enough employees to watch the system and how can APC master switch reboot the machine in case it BSOD ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:49:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.159.mpoweredpc.net [142.177.193.159]) by hub.freebsd.org (Postfix) with ESMTP id 6A43037B776 for ; Tue, 8 Aug 2000 21:49:15 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id BAA42115; Wed, 9 Aug 2000 01:46:52 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 9 Aug 2000 01:46:52 -0300 (ADT) From: The Hermit Hacker To: wonko@entropy.tmok.com Cc: Irwan Hadi , freebsd-current@FreeBSD.ORG Subject: Re: hotmail now running win2000 In-Reply-To: <200008090444.AAA61833@entropy.tmok.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Brian Hechinger wrote: > Irwan Hadi drunkenly mumbled... > > > > But I guess soon they will change all their freeBSD servers ;( > > and I wonder, how many people should be employed by Microsoft, just to > > press the restart button at their 2000 servers for Hotmail, in case they > > got BSOD ? > > it's called the APC MasterSwitch (or similar peoduct by alternate vendor) > > reboot machines over the network. takes the place of 64.2% of all people > employed with the word microsoft in their title. and they do have their own 'Foundry' like product that they can use as a front end ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:53:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 44DF937B776 for ; Tue, 8 Aug 2000 21:53:50 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id AAA62024; Wed, 9 Aug 2000 00:59:03 -0400 (EDT) From: Brian Hechinger Message-Id: <200008090459.AAA62024@entropy.tmok.com> Subject: Re: hotmail now running win2000 In-Reply-To: <4.2.0.58.20000808224658.00a83c70@staf.bpkpenabur.or.id> from Irwan Hadi at "Aug 8, 2000 10:48:43 pm" To: irwanhadi@iname.com (Irwan Hadi) Date: Wed, 9 Aug 2000 00:59:02 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Irwan Hadi drunkenly mumbled... > > Including MCSE, MCP , etc ? ;) :) bingo. > BTW how can the administrator of hotmail determine if a server is BSOD or > not then ?, because they have 2000 servers and I think without enough > employees to watch the system and how can APC master switch reboot the > machine in case it BSOD ? SNMP is your friend. -b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 21:55:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat193.159.mpoweredpc.net [142.177.193.159]) by hub.freebsd.org (Postfix) with ESMTP id 9F80937B776 for ; Tue, 8 Aug 2000 21:55:07 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id BAA42164; Wed, 9 Aug 2000 01:51:44 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 9 Aug 2000 01:51:44 -0300 (ADT) From: The Hermit Hacker To: Irwan Hadi Cc: wonko@entropy.tmok.com, freebsd-current@FreeBSD.ORG Subject: Re: hotmail now running win2000 In-Reply-To: <4.2.0.58.20000808224658.00a83c70@staf.bpkpenabur.or.id> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Irwan Hadi wrote: > At 12:44 AM 8/9/00 -0400, Brian Hechinger wrote: > >Irwan Hadi drunkenly mumbled... > > > > > > But I guess soon they will change all their freeBSD servers ;( > > > and I wonder, how many people should be employed by Microsoft, just to > > > press the restart button at their 2000 servers for Hotmail, in case they > > > got BSOD ? > > > >it's called the APC MasterSwitch (or similar peoduct by alternate vendor) > > > >reboot machines over the network. takes the place of 64.2% of all people > >employed with the word microsoft in their title. > > Including MCSE, MCP , etc ? ;) :) > > BTW how can the administrator of hotmail determine if a server is BSOD or > not then ?, because they have 2000 servers and I think without enough > employees to watch the system and how can APC master switch reboot the > machine in case it BSOD ? use something like netsaint to monitor those machines? and the APC master switch is web administered, so it would be too easy to build a quick perl script to trigger a power outlet correspondign to the partiular server that was n olonger responding ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 22: 0:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id B593437B776 for ; Tue, 8 Aug 2000 22:00:07 -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 OAA07054; Wed, 9 Aug 2000 14:29:50 +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 14:29:49 +0930 (CST) From: "Daniel O'Connor" To: The Hermit Hacker Subject: Re: hotmail now running win2000 Cc: freebsd-current@FreeBSD.ORG, wonko@entropy.tmok.com, Irwan Hadi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Aug-00 The Hermit Hacker wrote: > use something like netsaint to monitor those machines? and the APC master > switch is web administered, so it would be too easy to build a quick perl > script to trigger a power outlet correspondign to the partiular server > that was n olonger responding ... Personally I would wire something up to the reset switch instead.. Much less potential for accidentally nuking your hardware if your script is broken and starts toggling machines on and off like mad.. (much less violent on disk etc too) --- 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-current" in the body of the message From owner-freebsd-current Tue Aug 8 22:12:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id AAC9537B9FA for ; Tue, 8 Aug 2000 22:12:32 -0700 (PDT) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id BAA62285; Wed, 9 Aug 2000 01:17:29 -0400 (EDT) From: Brian Hechinger Message-Id: <200008090517.BAA62285@entropy.tmok.com> Subject: Re: hotmail now running win2000 In-Reply-To: from "Daniel O'Connor" at "Aug 9, 2000 2:29:49 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Wed, 9 Aug 2000 01:17:29 -0400 (EDT) Cc: scrappy@hub.org, freebsd-current@FreeBSD.ORG, irwanhadi@iname.com Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor drunkenly mumbled... > > Personally I would wire something up to the reset switch instead.. > > Much less potential for accidentally nuking your hardware if your script is > broken and starts toggling machines on and off like mad.. > (much less violent on disk etc too) but how feasable is that for a large installation. would you like to pull 2000 machines apart and make the needed modifications? the masterswitch solutions is "plug 'n play" it just a powerstip as far as i''m concerned. just food for thought. -b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 22:19:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1179537BD2D for ; Tue, 8 Aug 2000 22:19:08 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA91063; Wed, 9 Aug 2000 01:18:39 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Wed, 9 Aug 2000 01:18:39 -0400 (EDT) From: "Brandon D. Valentine" To: wonko@entropy.tmok.com Cc: "Daniel O'Connor" , scrappy@hub.org, freebsd-current@FreeBSD.ORG, irwanhadi@iname.com Subject: Re: hotmail now running win2000 In-Reply-To: <200008090517.BAA62285@entropy.tmok.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Take this to -chat or -advocacy, PLEASE. This is nowhere near a relevant topic for -current. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 22:28:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 5361E37BD06; Tue, 8 Aug 2000 22:28:43 -0700 (PDT) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA64703; Wed, 9 Aug 2000 12:28:34 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 9 Aug 2000 12:28:34 +0700 (NSS) From: Max Khon To: Brian Fundakowski Feldman Cc: Pete Carah , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: crypt(3) problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 8 Aug 2000, Brian Fundakowski Feldman wrote: > We should switch to using just libdescrypt and being allowed to switch > crypt formats easily between md5 and des. My proposed solution using > login.conf is at http://people.FreeBSD.org/~green/crypt_switching.patch, > and it's going to be put into production usage relatively soon (that is, > whether or not it's actually in FreeBSD). this would solve a lot of problems with libcrypt for third-party software developers. at this time to ensure that our product will work on any FreeBSD installation we link libdescrypt statically (which is a pain in the ass if f.e. libtool is used) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 22:58:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 54A6537B7A4 for ; Tue, 8 Aug 2000 22:58:33 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA91339; Wed, 9 Aug 2000 01:58:32 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Wed, 9 Aug 2000 01:58:32 -0400 (EDT) From: Adam To: Irwan Hadi Cc: wonko@entropy.tmok.com, freebsd-current@FreeBSD.ORG Subject: Re: hotmail now running win2000 In-Reply-To: <4.2.0.58.20000808222949.00a86390@staf.bpkpenabur.or.id> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Aug 2000, Irwan Hadi wrote: >At 12:28 AM 8/9/00 -0400, Brian Hechinger wrote: >>Irwan Hadi drunkenly mumbled... >> > Sigh http://www.netcraft.com/whats/?host=www.hotmail.com >> >>not on all the machines however. re-run the query, sometimes you get: >> >>www.hotmail.com is running Apache/1.3.6 (Unix) mod_ssl/2.2.8 SSLeay/0.9.0b >>on FreeBSD >> >>got both goin. just in case w2k didn't make the grade i assume. > >But I guess soon they will change all their freeBSD servers ;( >and I wonder, how many people should be employed by Microsoft, just to >press the restart button at their 2000 servers for Hotmail, in case they >got BSOD ? I hate to dissapoint you all, but Windows NT (certainly 4 and 5(win2k), not sure about 3.51 because I havent used it) has a "feature" to enable automatic reboot at BSOD. Its just off by default, whereas FreeBSD has this feature on by default :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 8 23:42:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mike.dhis.org (hiper1-d216.stk.cwnet.com [209.142.56.216]) by hub.freebsd.org (Postfix) with ESMTP id 77E3D37B936 for ; Tue, 8 Aug 2000 23:42:48 -0700 (PDT) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (ogre.lan [192.168.100.1]) by mike.dhis.org (Postfix) with ESMTP id F03C453; Tue, 8 Aug 2000 23:42:45 -0700 (PDT) Message-ID: <3990FD64.C38B0A0D@es.co.nz> Date: Tue, 08 Aug 2000 23:42:44 -0700 From: Mike Muir Reply-To: mmuir@es.co.nz X-Mailer: Mozilla 4.73 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Sanda Cc: current@FreeBSD.ORG Subject: Re: emu10k1 problems solved References: <5.0.0.11.2.20000809051808.00a52fc0@mail.kabsi.at> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Sanda wrote: > > At 09:15 07.08.2000 +0200, Benedikt Schmidt wrote: > > >Just wanted to say that with the recent changes in the > >emu10k1 driver all my problems with it have disappeared. > > > >There are no more "dodgy irq" messages > >and the sound quality has improved too (no more crackling). > > Just a quick question... > > Is it possible to get this driver working under 4.1-STABLE aswell, or are > the changes in the -current kernel already too big? > > Or is it officially planned to merge this updated driver into the -STABLE > branch? Grab /sys/dev/sound/pci/emu10k1.c and /sys/gnu/dev/sound/pci/emu10k1.h from -current and recompile kernel.. no problems. -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 6:37: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (Postfix) with ESMTP id 3AAD137B999 for ; Wed, 9 Aug 2000 06:37:03 -0700 (PDT) (envelope-from tinguely@plains.NoDak.edu) Received: (from tinguely@localhost) by plains.NoDak.edu (8.9.3/8.9.3) id IAA25610; Wed, 9 Aug 2000 08:36:54 -0500 (CDT) Date: Wed, 9 Aug 2000 08:36:54 -0500 (CDT) From: Mark Tinguely Message-Id: <200008091336.IAA25610@plains.NoDak.edu> To: doconnor@gsoft.com.au, scrappy@hub.org Subject: Re: hotmail now running win2000 Cc: freebsd-current@FreeBSD.ORG, irwanhadi@iname.com, wonko@entropy.tmok.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 09-Aug-00 The Hermit Hacker wrote: > > use something like netsaint to monitor those machines? and the APC master > > switch is web administered, so it would be too easy to build a quick perl > > script to trigger a power outlet correspondign to the partiular server > > that was n olonger responding ... > > Personally I would wire something up to the reset switch instead.. there are watchdog cards like the Berkshire to do this. I was asked to fix a Linux driver problem for one of these cards and wrote a FreeBSD driver for the card. Thankfully *BSD is stable enough that this board is not needed, but (trying to justify my time in doing the driver for BSD) the card also has a temperature feature that you could use with a ATX power supply and the FreeBSD 3.x/4.x init to shut off the machine if the internals get to hot. --mark tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 7: 1:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from hc1.hci.net (hc1.hci.net [204.255.136.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B44D37B665 for ; Wed, 9 Aug 2000 07:01:37 -0700 (PDT) (envelope-from ahze@wp.cc.nc.us) Received: from 24-216-177-184.hsacorp.net (ahze@24-216-177-184.hsacorp.net [24.216.177.184]) by hc1.hci.net (8.9.0/8.9.0) with ESMTP id KAA18840; Wed, 9 Aug 2000 10:01:08 -0400 (EDT) Message-Id: <200008091401.KAA18840@hc1.hci.net> Date: Wed, 09 Aug 2000 10:01:21 EDT From: Mike Johnson To: thomas@hentschel.net, Irwan Hadi Cc: freebsd-current@FreeBSD.ORG Subject: Re: hotmail now running win2000 Reply-To: ahze@wp.cc.nc.us 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder what the back servers that handle the mail are running though... I wonder if they are gonna be changed to windows 2000 .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 7:14: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from neimail.networkengines.com (wks7.networkengines.com [64.55.6.7]) by hub.freebsd.org (Postfix) with ESMTP id 254D637BD1D for ; Wed, 9 Aug 2000 07:14:07 -0700 (PDT) (envelope-from Craig.Hughes@networkengines.com) Received: by neimail.networkengines.com with Internet Mail Service (5.5.2650.21) id ; Wed, 9 Aug 2000 10:14:27 -0400 Message-ID: <8D18C4F9CBA1D311900F00A0C990C97F01044526@neimail.networkengines.com> From: Craig Hughes To: 'Mark Tinguely' , doconnor@gsoft.com.au, scrappy@hub.org Cc: freebsd-current@FreeBSD.ORG, irwanhadi@iname.com, wonko@entropy.tmok.com Subject: RE: hotmail now running win2000 Date: Wed, 9 Aug 2000 10:14:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Or you could use something like Network Engines servers and AdminEngine that have built in out-of-band management...even if the main OS loses its lunch, you can still reach the machine (including power cycling, temp. detection, etc.). Craig (Disclaimer: I work for them!) -----Original Message----- From: Mark Tinguely [mailto:tinguely@plains.NoDak.edu] > On 09-Aug-00 The Hermit Hacker wrote: > > use something like netsaint to monitor those machines? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 8:31:49 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Wed Aug 9 9:42:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 71A6237B55F; Wed, 9 Aug 2000 09:42:20 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([208.191.149.190]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FZ100BJAA41U4@mta4.rcsntx.swbell.net>; Wed, 9 Aug 2000 11:36:02 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id LAA29805; Wed, 09 Aug 2000 11:36:03 -0500 (CDT envelope-from chris) Date: Wed, 09 Aug 2000 11:36:02 -0500 From: Chris Costello Subject: Re: Request for review/comments - new option for uname(1) In-reply-to: <20000809005929.K250@parish> To: Mark Ovens Cc: current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000809113602.C26695@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <20000809005929.K250@parish> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, August 09, 2000, Mark Ovens wrote: > The only thing I couldn't work out is why sysctl() adds 5 spaces after > the date sub-string, so I've haven't stripped them out (hence the > indented third line). sysctl() does not do that, that's what the data in the kernel is. Look at src/sys/compile/[yourkernel]/vers.c (or /usr/obj/usr/src/sys/[yourkernel]/vers.c). -- |Chris Costello |Computers are not intelligent. They only think they are. `--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 10: 4:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E648437BE1D for ; Wed, 9 Aug 2000 10:04:27 -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 LAA97993 for ; Wed, 9 Aug 2000 11:04:26 -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 LAA48738 for ; Wed, 9 Aug 2000 11:04:02 -0600 (MDT) Message-Id: <200008091704.LAA48738@harmony.village.org> To: current@freebsd.org Subject: Upgrading 2.2.8 -> current Date: Wed, 09 Aug 2000 11:04:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK. I have a laptop that's running 2.2.8 right now. I had planned on upgrading it to 3.5 via a source build and then again to -current from there. Before I did that, since this is a 486 DX4 100 pc98 machine, I thought I'd ask if the 2.2.8 -> current path ever was fixed. Also, if someone has a pc98 snapshot that an ipv4 host can get to, please let me know. I've had problems getting to the last location I was sent. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 10: 7:44 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Wed Aug 9 10: 9: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 8750C37BECE for ; Wed, 9 Aug 2000 10:08:50 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 14346 invoked from network); 9 Aug 2000 17:08:49 -0000 Received: from acs-24-154-26-155.zoominternet.net (24.154.26.155) by scully.zoominternet.net with SMTP; 9 Aug 2000 17:08:49 -0000 Date: Wed, 9 Aug 2000 13:08:49 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-26-155.zoominternet.net To: current@freebsd.org Subject: ESS 1868 (isa) - no more crackling! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for finally solving the PCM interrupts problem. Before, my sound card (ESS 1868 isa) was having problems with crackling noises while playing MP3's. Thanks for solving this. BTW, anyone else have this sound card? Not the greatest, but it's something I have to live with for the time being. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 10:50:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mr.usu.edu (mr.usu.edu [129.123.1.3]) by hub.freebsd.org (Postfix) with ESMTP id 6944537BF14 for ; Wed, 9 Aug 2000 10:50:40 -0700 (PDT) (envelope-from irwanhadi@iname.com) Received: from sl585 (sl585.dorms.usu.edu [129.123.238.132]) by mr.usu.edu (Postfix) with ESMTP id 2170B1D377; Wed, 9 Aug 2000 11:50:39 -0600 (MDT) Message-Id: <4.2.0.58.20000809115010.00a41920@staf.bpkpenabur.or.id> X-Nil: Date: Wed, 09 Aug 2000 11:50:36 -0600 To: ahze@wp.cc.nc.us, thomas@hentschel.net From: Irwan Hadi Subject: Re: hotmail now running win2000 Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <200008091401.KAA18840@hc1.hci.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:01 AM 8/9/00 -0400, Mike Johnson wrote: >I wonder what the back servers that handle the mail are running though... I >wonder if they are gonna be changed to windows 2000 .. Seems Microsoft SMTPSVC for the mail. You can try sending an email to your account from a hotmail account to prove ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 11:37: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.mich.com (mercury.mich.com [64.79.64.32]) by hub.freebsd.org (Postfix) with ESMTP id 8013A37BEFC; Wed, 9 Aug 2000 11:37:04 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm007-041.dialup.bignet.net [64.79.81.73]) by mercury.mich.com (8.9.3/8.9.3) with ESMTP id OAA02704; Wed, 9 Aug 2000 14:36:55 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id 3220D1999; Wed, 9 Aug 2000 14:33:44 -0400 (EDT) Date: Wed, 9 Aug 2000 14:33:44 -0400 From: Will Andrews To: Mark Ovens Cc: current@FreeBSD.ORG Subject: Re: Request for review/comments - new option for uname(1) Message-ID: <20000809143344.L29987@argon.gryphonsoft.com> Mail-Followup-To: Mark Ovens , current@FreeBSD.ORG References: <20000809005929.K250@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000809005929.K250@parish>; from marko@FreeBSD.ORG on Wed, Aug 09, 2000 at 12:59:29AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 12:59:29AM +0100, Mark Ovens wrote: > Is there any reason why this is unacceptable and could not be committed? Because it can be done with an awk/sed script? -- Will Andrews GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e>++++ h! r- y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 11:55:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 381A537BEEE; Wed, 9 Aug 2000 11:55:28 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.9.3/8.8.8) id LAA02796; Wed, 9 Aug 2000 11:55:22 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200008091855.LAA02796@ns.altadena.net> Subject: Re: crypt(3) problems In-Reply-To: from Brian Fundakowski Feldman at "Aug 8, 2000 06:42:52 pm" To: Brian Fundakowski Feldman Date: Wed, 9 Aug 2000 11:55:22 -0700 (PDT) Cc: current@FreeBSD.org, stable@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We should switch to using just libdescrypt and being allowed to switch > crypt formats easily between md5 and des. My proposed solution using > login.conf is at http://people.FreeBSD.org/~green/crypt_switching.patch, > and it's going to be put into production usage relatively soon (that is, > whether or not it's actually in FreeBSD). As long as things get switched around so that the format decision is external to libdescrypt and the existing password, so we can change an existing des passwd to md5. However, in our case, apache still needs to generate des but *all* other uses want md5. The link choice is the easiest way to select this, with environment next. Config files won't really work since they can't anticipate all uses. The full-blown pam implementations do it with pam parameters; login.conf is fine but won't work for "third-party" situations like I was commenting on (i.e. apache needs to accept and generate des but most other need md5, etc etc)... Perhaps an environment variable? libdescrypt is close since it will accept either; a fixed choice for what it generates, external to *any* application code (e.g. environment vars (easiest) or (if possible) config files that are somehow *completely* universal (I don't see how to do this without application mods unless the library can transparently get at argv[0] independently of what the app does like ++argv, etc)) would be nice. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 12: 9:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 860A637BAA5 for ; Wed, 9 Aug 2000 12:09:39 -0700 (PDT) (envelope-from mailto:professional3d@home.com) Received: from home.com ([24.20.70.64]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000809190907.RZNI6751.femail4.sdc1.sfba.home.com@home.com> for ; Wed, 9 Aug 2000 12:09:07 -0700 Message-ID: <3991ACFC.D9AC9EB2@home.com> Date: Wed, 09 Aug 2000 12:11:57 -0700 From: xavian anderson macpherson Reply-To: mailto:xavian@professional3d.com Organization: http://www.professional3d.com X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: membership Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i am not versed on the mechanics of freebsd; in fact, i barely understand the mechanics of the suse linux 6.4 package that i sm currently using. i became aware of the bsd package after seeing one for sale (freebsd 'powerpak') in a computer. i read on the box that bsd will run linux app's, so i decided to download bsd and try it on my system. it will be interesting to see how this works. if you-someone contacts me, i would be surprised and greatly appreciative. thank you, xavian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 12:52:28 2000 Delivered-To: freebsd-current@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 40CB537B64A for ; Wed, 9 Aug 2000 12:52:25 -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 13Mbtn-0005Bj-00; Wed, 09 Aug 2000 19:52:23 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id VAA10489; Wed, 9 Aug 2000 21:52:20 +0200 (CEST) (envelope-from wkb) Date: Wed, 9 Aug 2000 21:52:20 +0200 From: Wilko Bulte To: Donn Miller Cc: current@freebsd.org Subject: Re: ESS 1868 (isa) - no more crackling! Message-ID: <20000809215220.A10469@freebie.demon.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from dmmiller@cvzoom.net on Wed, Aug 09, 2000 at 01:08:49PM -0400 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 01:08:49PM -0400, Donn Miller wrote: > Thanks for finally solving the PCM interrupts problem. Before, my sound > card (ESS 1868 isa) was having problems with crackling noises while > playing MP3's. Thanks for solving this. BTW, anyone else have this sound > card? Not the greatest, but it's something I have to live with for the > time being. Sounds promising.. Will it also solve the identical problem the ESS1371 PCI has? -- Wilko Bulte wilko@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 12:54:10 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Wed Aug 9 13: 0:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 2BEB737B5DD for ; Wed, 9 Aug 2000 13:00:21 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 5491 invoked from network); 9 Aug 2000 20:00:16 -0000 Received: from acs-24-154-26-155.zoominternet.net (HELO cvzoom.net) (24.154.26.155) by ns.cvzoom.net with SMTP; 9 Aug 2000 20:00:16 -0000 Message-ID: <3991B84F.B834BF19@cvzoom.net> Date: Wed, 09 Aug 2000 16:00:15 -0400 From: Donn Miller X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Wilko Bulte Cc: current@freebsd.org Subject: Re: ESS 1868 (isa) - no more crackling! References: <20000809215220.A10469@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > On Wed, Aug 09, 2000 at 01:08:49PM -0400, Donn Miller wrote: > > Thanks for finally solving the PCM interrupts problem. > Sounds promising.. Will it also solve the identical problem the ESS1371 > PCI has? I just did a re-cvsup this morning, and this is the first time in a long while that I've noticed the problems were fixed. How long ago did you build your kernel? Note: now I'm seeing messages like this: Aug 9 12:13:56 /kernel: pcm0: hwptr went backwards 2144 -> 1132 Aug 9 12:13:57 /kernel: pcm0: hwptr went backwards 72 -> 3332 Aug 9 15:33:36 /kernel: pcm0: hwptr went backwards 172 -> 24 Aug 9 15:34:13 /kernel: pcm0: hwptr went backwards 100 -> 3820 Aug 9 15:35:27 /kernel: pcm0: hwptr went backwards 212 -> 28 Aug 9 15:35:28 /kernel: pcm0: hwptr went backwards 184 -> 3288 Aug 9 15:35:28 /kernel: pcm0: hwptr went backwards 2240 -> 2196 Aug 9 15:42:16 /kernel: pcm0: hwptr went backwards 2116 -> 1140 Aug 9 15:43:41 /kernel: pcm0: hwptr went backwards 184 -> 20 But, maybe these debugging messages were recently added to channel.c. I know the problem was in channel.c. Otherwise, mp3's play OK now. -- - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 13:22:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id BB03037B6D1; Wed, 9 Aug 2000 13:22:41 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Wed, 9 Aug 2000 15:59:02 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Pete Carah Cc: current@FreeBSD.org, stable@FreeBSD.org Subject: Re: crypt(3) problems In-Reply-To: <200008091855.LAA02796@ns.altadena.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Pete Carah wrote: > > We should switch to using just libdescrypt and being allowed to switch > > crypt formats easily between md5 and des. My proposed solution using > > login.conf is at http://people.FreeBSD.org/~green/crypt_switching.patch, > > and it's going to be put into production usage relatively soon (that is, > > whether or not it's actually in FreeBSD). > > As long as things get switched around so that the format decision is > external to libdescrypt and the existing password, so we can change an existing > des passwd to md5. However, in our case, apache still needs to > generate des but *all* other uses want md5. The link choice is the > easiest way to select this, with environment next. Config files won't > really work since they can't anticipate all uses. Well, first of all assume that by default DES-based scheme is what crypt() uses. > The full-blown pam implementations do it with pam parameters; login.conf > is fine but won't work for "third-party" situations like I was commenting > on (i.e. apache needs to accept and generate des but most other need > md5, etc etc)... Perhaps an environment variable? PAM still needs support from the crypt() library. There's not going to be a way to do it without a proper interface to the crypt library :-/ Right now there is int crypt_set_format(const char *format); This wouldn't be thread-safe to change formats, but crypt() isn't thread safe in the slightest bit anyway, by design. > libdescrypt is close since it will accept either; a fixed choice for > what it generates, external to *any* application code (e.g. environment > vars (easiest) or (if possible) config files that are somehow *completely* > universal (I don't see how to do this without application mods unless the > library can transparently get at argv[0] independently of what the app does > like ++argv, etc)) would be nice. You really cannot do this properly. It's best just to do what it takes to get the right format on a given platform. On FreeBSD now, that's use libdescrypt and crypt() with a normal salt, or to get MD5 use a salt with the "$1$" format. On FreeBSD with the changes I have, you call e.g. crypt_set_format("md5") and then crypt() with a generic salt. > -- Pete -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 14: 5:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.osd.bsdi.com (zippy.osd.bsdi.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9476637B65F for ; Wed, 9 Aug 2000 14:05:24 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA08328; Wed, 9 Aug 2000 14:04:50 -0700 (PDT) (envelope-from jkh@zippy.osd.bsdi.com) To: wonko@entropy.tmok.com Cc: doconnor@gsoft.com.au (Daniel O'Connor), scrappy@hub.org, freebsd-current@FreeBSD.ORG, irwanhadi@iname.com Subject: Re: hotmail now running win2000 In-reply-to: Your message of "Wed, 09 Aug 2000 01:17:29 EDT." <200008090517.BAA62285@entropy.tmok.com> Date: Wed, 09 Aug 2000 14:04:50 -0700 Message-ID: <8325.965855090@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erm, can I ask what this thread POSSIBLY has to do with freebsd-current? Do people even care about posting on-topic things to the correct mailing lists anymore? At best, this is and always was freebsd-chat material. Thank you. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 14:11:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 72BB937B877; Wed, 9 Aug 2000 14:11:22 -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 OAA46630; Wed, 9 Aug 2000 14:11:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 9 Aug 2000 14:11:22 -0700 (PDT) From: Kris Kennaway To: Warner Losh Cc: current@freebsd.org Subject: Re: Upgrading 2.2.8 -> current In-Reply-To: <200008091704.LAA48738@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, Warner Losh wrote: > OK. I have a laptop that's running 2.2.8 right now. I had planned on > upgrading it to 3.5 via a source build and then again to -current from > there. Before I did that, since this is a 486 DX4 100 pc98 machine, I > thought I'd ask if the 2.2.8 -> current path ever was fixed. Didn't we axe some of the aout-to-elf gunk? 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-current" in the body of the message From owner-freebsd-current Wed Aug 9 14:23:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 082F137BB3D for ; Wed, 9 Aug 2000 14:23:43 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id RAA47592; Wed, 9 Aug 2000 17:23:40 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008092123.RAA47592@blackhelicopters.org> Subject: Re: membership In-Reply-To: <3991ACFC.D9AC9EB2@home.com> from xavian anderson macpherson at "Aug 9, 2000 12:11:57 pm" To: mailto:xavian@professional3d.com Date: Wed, 9 Aug 2000 17:23:40 -0400 (EDT) Cc: freebsd-current@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Xavian, You'd have better luck talking to questions@freebsd.org with any specific problems you have. This list is for nitty-gritty discussion of some of FreeBSD's guts. While the folks here are friendly enough, they aren't really interested in answering basic questions and helping new users. You might also check out the freebsd-newbies list. Regards, Michael > i am not versed on the mechanics of freebsd; in fact, i barely > understand the mechanics of the suse linux 6.4 package that i sm > currently using. i became aware of the bsd package after seeing one for > sale (freebsd 'powerpak') in a computer. i read on the box that bsd will > run linux app's, so i decided to download bsd and try it on my system. > it will be interesting to see how this works. if you-someone contacts > me, i would be surprised and greatly appreciative. > > thank you, xavian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 15: 2:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E065037B780; Wed, 9 Aug 2000 15:02: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 QAA99653; Wed, 9 Aug 2000 16:02:45 -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 QAA51594; Wed, 9 Aug 2000 16:02:21 -0600 (MDT) Message-Id: <200008092202.QAA51594@harmony.village.org> To: Kris Kennaway Subject: Re: Upgrading 2.2.8 -> current Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 09 Aug 2000 14:11:22 PDT." References: Date: Wed, 09 Aug 2000 16:02:21 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kris Kennaway writes: : On Wed, 9 Aug 2000, Warner Losh wrote: : : > OK. I have a laptop that's running 2.2.8 right now. I had planned on : > upgrading it to 3.5 via a source build and then again to -current from : > there. Before I did that, since this is a 486 DX4 100 pc98 machine, I : > thought I'd ask if the 2.2.8 -> current path ever was fixed. : : Didn't we axe some of the aout-to-elf gunk? I think you are right. I'm currently looking at the "make buildworld on my fast box, make installworld on the laptop". Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 15:35: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from falcon.home.hentschel.net (d83b0468.dsl.flashcom.net [216.59.4.104]) by hub.freebsd.org (Postfix) with ESMTP id 788D337B75B for ; Wed, 9 Aug 2000 15:34:58 -0700 (PDT) (envelope-from thomas@hentschel.net) Received: from hentschel.net (thomas@localhost [127.0.0.1]) by falcon.home.hentschel.net (8.9.3/8.9.3) with ESMTP id NAA61462; Wed, 9 Aug 2000 13:04:04 -0700 (PDT) (envelope-from thomas@hentschel.net) Message-Id: <200008092004.NAA61462@falcon.home.hentschel.net> Date: Wed, 9 Aug 2000 13:04:03 -0700 (PDT) From: thomas@hentschel.net Subject: Re: membership To: xavian@professional3d.com Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <3991ACFC.D9AC9EB2@home.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Aug, xavian anderson macpherson wrote: > i am not versed on the mechanics of freebsd; in fact, i barely > understand the mechanics of the suse linux 6.4 package that i sm > currently using. i became aware of the bsd package after seeing one for > sale (freebsd 'powerpak') in a computer. i read on the box that bsd will > run linux app's, so i decided to download bsd and try it on my system. > it will be interesting to see how this works. if you-someone contacts > me, i would be surprised and greatly appreciative. > > thank you, xavian > > Well, your best bet is the freebsd website http://www.freebsd.org and in particular http://www.freebsd.org/projects/newbies.html should be of help to you. You may also wish to subscribe to the -questions mailing list (make sure you understand how to do this at http://www.freebsd.org/support.html#mailing-list ). Also, your request is off topic for this list, make sure you understand the charter of each list before posting to it. Otherwise, welcome on board -Th To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 16:39:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id F1E7837B5FF for ; Wed, 9 Aug 2000 16:39:09 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.88.132]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000809233907.GPDA26680.mta01-svc.ntlworld.com@parish.my.domain> for ; Thu, 10 Aug 2000 00:39:07 +0100 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id AAA01137 for current@FreeBSD.ORG; Thu, 10 Aug 2000 00:39:04 +0100 (BST) (envelope-from mark) Date: Thu, 10 Aug 2000 00:38:58 +0100 From: Mark Ovens To: current@FreeBSD.ORG Subject: Re: Request for review/comments - new option for uname(1) Message-ID: <20000810003858.D251@parish> References: <20000809005929.K250@parish> <20000809143344.L29987@argon.gryphonsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20000809143344.L29987@argon.gryphonsoft.com>; from andrews@technologist.com on Wed, Aug 09, 2000 at 02:33:44PM -0400 Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 02:33:44PM -0400, Will Andrews wrote: > On Wed, Aug 09, 2000 at 12:59:29AM +0100, Mark Ovens wrote: > > Is there any reason why this is unacceptable and could not be committed? > > Because it can be done with an awk/sed script? > I'll forget about it then. I only did it because I was fed up with manually editing the output so it was tidier in e-mails and PRs. Like I said, it's not important. Thanks for the feedback. > -- > Will Andrews > GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w--- > O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ > G++ e>++++ h! r- y? -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 17:18:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from addr2.addr.com (addr.com [209.249.147.252]) by hub.freebsd.org (Postfix) with ESMTP id 5D7AA37BF01; Wed, 9 Aug 2000 17:18:41 -0700 (PDT) (envelope-from jwpauler@jwpages.com) Received: from hernandez (141-102.lgtch02.fais.net [208.249.141.102]) by addr2.addr.com (8.9.3/8.9.1) with SMTP id RAA80318; Wed, 9 Aug 2000 17:20:24 -0700 (PDT) (envelope-from jwpauler@jwpages.com) Message-ID: <000801c00260$657d4b80$668df9d0@hernandez> From: "justin" To: Cc: Subject: USER PPP Date: Wed, 9 Aug 2000 19:17:37 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C00236.7AD8EC20" 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C00236.7AD8EC20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey fellas... Allright, here is the situation. I just had a second phone line = installed in my house, a POTS (plain old telephone service) line. I have = plugged it directly into my FreeBSD 4.1-STABLE workstation/server. I = allready have PPP setup and when I execute it, it runs fine. Now then, = what I would eventually like to do is have all of my windows based = machines connect to this one and use it as a gateway for internet = traffic. However, that will come later. What I would like to do right now, however, is guarantee that = anytime, anyday, barring a problem with my ISP, that my box is connected = to the internet. I have it currently setup to dial the internet when it = boots and that seems, so far to work ok. My problem you ask? My ISP = implements a 5 minute no transfer policy, they disconnect my connection = after 5 minutes of 'idling'. What I would like to do is have some kind = of check to verify if I am still connected to the internet and if not, = execute it. I was thinking some type of script running from crontab = every 5 minutes. If I am not connected, then automatically reconnect to = the internet. Now there is another possible solution I cannot find an answer to. = Is there a BSD option to 'keep-alive' the connection so I do not time = out? I would prefer not to leave an X session opening refreshing CNN = every five minutes :P Your help and/or scripts are welcome :) Justin W. Pauler JWPages Web Development jwpauler@jwpages.com ------=_NextPart_000_0005_01C00236.7AD8EC20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hey fellas...
 
    Allright, here is = the situation.=20 I just had a second phone line installed in my house, a POTS (plain old=20 telephone service) line. I have plugged it directly into my FreeBSD = 4.1-STABLE=20 workstation/server. I allready have PPP setup and when I execute it, it = runs=20 fine. Now then, what I would eventually like to do is have all of my = windows=20 based machines connect to this one and use it as a gateway for internet = traffic.=20 However, that will come later.
 
    What I would like to = do right=20 now, however, is guarantee that anytime, anyday, barring a problem with = my ISP,=20 that my box is connected to the internet. I have it currently setup to = dial the=20 internet when it boots and that seems, so far to work ok. My = problem you=20 ask? My ISP implements a 5 minute no transfer policy, they disconnect my = connection after 5 minutes of 'idling'. What I would like to do is have = some=20 kind of check to verify if I am still connected to the internet and if = not,=20 execute it. I was thinking some type of script running from crontab = every 5=20 minutes. If I am not connected, then automatically reconnect to the=20 internet.
 
    Now there is another = possible=20 solution I cannot find an answer to. Is there a BSD option to = 'keep-alive' the=20 connection so I do not time out? I would prefer not to leave an X = session=20 opening refreshing CNN every five minutes :P
 
    Your help and/or = scripts are=20 welcome :)
 
Justin W. Pauler
JWPages Web Development
jwpauler@jwpages.com
 
 
------=_NextPart_000_0005_01C00236.7AD8EC20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 17:25:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta02-svc.ntlworld.com (mta02-svc.ntlworld.com [62.253.162.42]) by hub.freebsd.org (Postfix) with ESMTP id 1ECA837B7F0; Wed, 9 Aug 2000 17:25:10 -0700 (PDT) (envelope-from mark@ukug.uk.freebsd.org) Received: from parish.my.domain ([62.253.84.152]) by mta02-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000810012412.IEGP3760.mta02-svc.ntlworld.com@parish.my.domain>; Thu, 10 Aug 2000 01:24:12 +0000 Received: (from mark@localhost) by parish.my.domain (8.9.3/8.9.3) id BAA06880; Thu, 10 Aug 2000 01:25:03 +0100 (BST) (envelope-from mark) Date: Thu, 10 Aug 2000 01:25:02 +0100 From: Mark Ovens To: justin Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: USER PPP Message-ID: <20000810012502.B6678@parish> References: <000801c00260$657d4b80$668df9d0@hernandez> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <000801c00260$657d4b80$668df9d0@hernandez>; from jwpauler@jwpages.com on Wed, Aug 09, 2000 at 07:17:37PM -0500 Organization: Total lack of Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 07:17:37PM -0500, justin wrote: > Hey fellas... > > Allright, here is the situation. I just had a second phone line installed in my house, a POTS (plain old telephone service) line. I have plugged it directly into my FreeBSD 4.1-STABLE workstation/server. I allready have PPP setup and when I execute it, it runs fine. Now then, what I would eventually like to do is have all of my windows based machines connect to this one and use it as a gateway for internet traffic. However, that will come later. > > What I would like to do right now, however, is guarantee that anytime, anyday, barring a problem with my ISP, that my box is connected to the internet. I have it currently setup to dial the internet when it boots and that seems, so far to work ok. My problem you ask? My ISP implements a 5 minute no transfer policy, they disconnect my connection after 5 minutes of 'idling'. What I would like to do is have some kind of check to verify if I am still connected to the internet and if not, execute it. I was thinking some type of script running from crontab every 5 minutes. If I am not connected, then automatically reconnect to the internet. > > Now there is another possible solution I cannot find an answer to. Is there a BSD option to 'keep-alive' the connection so I do not time out? I would prefer not to leave an X session opening refreshing CNN every five minutes :P > Firstly, please set your mailer to wrap lines at ~70 chars please. Add `` set reconnect'' to /etc/ppp/ppp.conf. From the manpage: set reconnect timeout ntries This command tells ppp to re-establish the connection ntries times on loss of carrier with a pause of timeout seconds before each try.For example, > Your help and/or scripts are welcome :) > > Justin W. Pauler > JWPages Web Development > jwpauler@jwpages.com > > -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 17:29:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 6C39137B7F0; Wed, 9 Aug 2000 17:29:25 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id UAA00732; Wed, 9 Aug 2000 20:29:51 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Wed, 9 Aug 2000 20:29:50 -0400 (EDT) From: "Brandon D. Valentine" To: justin Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: USER PPP In-Reply-To: <000801c00260$657d4b80$668df9d0@hernandez> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Wrap text at 72 columns.] On Wed, 9 Aug 2000, justin wrote: > What I would like to do right now, however, is guarantee that anytime, anyday, barring a problem with my ISP, that my box is connected to the internet. I have it currently setup to dial the internet when it boots and that seems, so far to work ok. My problem you ask? My ISP implements a 5 minute no transfer policy, they disconnect my connection after 5 minutes of 'idling'. What I would like to do is have some kind of check to verify if I am still connected to the internet and if not, execute it. I was thinking some type of script running from crontab every 5 minutes. If I am not connected, then automatically reconnect to the internet. Read the ppp(8) manpage and you will discover the -ddial flag which implements the functionality you have discussed. It would probably be more advisable to use the -auto flag though, but that's your own decision to make. Read the manpage. This is really a -questions issue. Now you know, don't ask questions like this here again, it's the wrong place for it. Read the mailing list charters at: http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL for more information. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 9 17:41: 0 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Wed Aug 9 22:36:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 723AF37B8E7 for ; Wed, 9 Aug 2000 22:36:15 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115242>; Thu, 10 Aug 2000 15:36:04 +1000 Content-return: prohibited Date: Thu, 10 Aug 2000 15:36:01 +1000 From: Peter Jeremy Subject: Slow ssh throughput with -current To: current@freebsd.org Mail-followup-to: current@freebsd.org Message-Id: <00Aug10.153604est.115242@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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed a really peculiar network slowdown with -current from about a week ago. The machine has two NICs - an old 16-bit SMC card (ed0) running 10baseT and a PCI SMC card (tx0) running 100baseTX full duplex. When I scp (either ssh-1.2.27 or OpenSSH) to a remote machine via ed0, I get a throughput of ~8KB/sec. When I go via tx0, I get ~3MB/sec (CPU limited). If I use ftp via ed0, I get wire speed (just over 1MB/sec). (I haven't tried Looking at the packets sent via ed0 with tcpdump, I find: 15:29:58.140543 remote.ssh > local.4825: . ack 3344 win 33580 (DF) [tos 0x8] 15:29:58.141278 local.4825 > remote.ssh: . 3344:4804(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:58.340556 remote.ssh > local.4825: . ack 4804 win 33580 (DF) [tos 0x8] 15:29:58.341180 local.4825 > remote.ssh: . 4804:6264(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:58.540553 remote.ssh > local.4825: . ack 6264 win 33580 (DF) [tos 0x8] 15:29:58.541172 local.4825 > remote.ssh: . 6264:7724(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:58.740559 remote.ssh > local.4825: . ack 7724 win 33580 (DF) [tos 0x8] 15:29:58.741185 local.4825 > remote.ssh: . 7724:9184(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:58.940554 remote.ssh > local.4825: . ack 9184 win 33580 (DF) [tos 0x8] 15:29:58.941164 local.4825 > remote.ssh: . 9184:10644(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:59.140553 remote.ssh > local.4825: . ack 10644 win 33580 (DF) [tos 0x8] 15:29:59.141178 local.4825 > remote.ssh: . 10644:12104(1460) ack 552 win 17520 (DF) [tos 0x8] 15:29:59.340556 remote.ssh > local.4825: . ack 12104 win 33580 (DF) [tos 0x8] Notice that although it's advertising a window size of 17520, it's not sending the next packet until the previous packet is ack'd. When I ftp via ed0, or use ftp or scp via tx0, I get the expected behaviour - the send side is several packets ahead of the ack's. I didn't notice this before I upgraded last week (though it was previously running software from just prior to 4.0-RELEASE). The possibly unusual things in the machine: - It has VLAN support compiled in (though not currently in use). - It has IPFW support compiled in (via a couple of rules to ignore an HP OpenView machine that wants to manage every host in the company). - There are also a couple of serial user-land ppp links active. I can't understand why it only affects ssh on one link. If it affected everything on ed0, or if it affected ssh on both NICs, I'd have some idea where to start looking. Does anyone have any ideas? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 4:30:55 2000 Delivered-To: freebsd-current@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 375CF37B8DE for ; Thu, 10 Aug 2000 04:30:48 -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 13MqXu-000AVN-00; Thu, 10 Aug 2000 11:30:46 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id LAA00811; Thu, 10 Aug 2000 11:56:38 +0200 (CEST) (envelope-from wkb) Date: Thu, 10 Aug 2000 11:56:38 +0200 From: Wilko Bulte To: Donn Miller Cc: current@freebsd.org Subject: Re: ESS 1868 (isa) - no more crackling! Message-ID: <20000810115638.B739@freebie.demon.nl> References: <20000809215220.A10469@freebie.demon.nl> <3991B84F.B834BF19@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3991B84F.B834BF19@cvzoom.net>; from dmmiller@cvzoom.net on Wed, Aug 09, 2000 at 04:00:15PM -0400 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Aug 09, 2000 at 04:00:15PM -0400, Donn Miller wrote: > Wilko Bulte wrote: > > > > On Wed, Aug 09, 2000 at 01:08:49PM -0400, Donn Miller wrote: > > > Thanks for finally solving the PCM interrupts problem. > > > Sounds promising.. Will it also solve the identical problem the ESS1371 > > PCI has? > > I just did a re-cvsup this morning, and this is the first time in a > long while that I've noticed the problems were fixed. How long ago > did you build your kernel? I now run a 4.1-stable kernel based on yesterday evening's sources. Question is of course if the fix put in current is completely in -stable too. I'll have to check that. But in any case: the problem is still there. > Aug 9 15:42:16 /kernel: pcm0: hwptr went backwards 2116 -> 1140 > Aug 9 15:43:41 /kernel: pcm0: hwptr went backwards 184 -> 20 > > But, maybe these debugging messages were recently added to channel.c. > I know the problem was in channel.c. Otherwise, mp3's play OK now. Don't see those. -- Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 5:38:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id E3CA137BDA2 for ; Thu, 10 Aug 2000 05:38:48 -0700 (PDT) (envelope-from robd@gmx.net) Received: (qmail 31568 invoked by uid 0); 10 Aug 2000 12:38:47 -0000 Received: from p3ee2887b.dip0.t-ipconnect.de (HELO gmx.net) (62.226.136.123) by mail.gmx.net with SMTP; 10 Aug 2000 12:38:47 -0000 Message-ID: <3992A282.DA7A9F44@gmx.net> Date: Thu, 10 Aug 2000 14:39:30 +0200 From: Robert Drehmel X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Wilko Bulte Cc: Donn Miller , current@freebsd.org Subject: Re: ESS 1868 (isa) - no more crackling! References: <20000809215220.A10469@freebie.demon.nl> <3991B84F.B834BF19@cvzoom.net> <20000810115638.B739@freebie.demon.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000810115638.B739@freebie.demon.nl>, Wilko Bulte wrote: > I now run a 4.1-stable kernel based on yesterday evening's sources. > Question is of course if the fix put in current is completely in > -stable too. I'll have to check that. > > But in any case: the problem is still there. I am running 5.0-20000809-CURRENT from current.FreeBSD.org. src-sys was last cvsup'ed 10 Aug, 04:10 CEST. The card is an old onboard ESS 1688 and all the crackling that I had in 4.1-RELEASE is completely gone. In <3991B84F.B834BF19@cvzoom.net>, Donn Miller wrote: > Note: now I'm seeing messages like this: > > Aug 9 12:13:56 /kernel: pcm0: hwptr went backwards 2144 -> 1132 > Aug 9 12:13:57 /kernel: pcm0: hwptr went backwards 72 -> 3332 > Aug 9 15:33:36 /kernel: pcm0: hwptr went backwards 172 -> 24 [...] I get those too when there is not enough CPU time... pcm1: hwptr went backwards 56 -> 3388 pcm1: hwptr went backwards 48 -> 3488 pcm1: hwptr went backwards 64 -> 4064 -- Robert S. F. Drehmel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 5:43: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from hal.medianet.ie (hal.medianet.ie [212.17.32.26]) by hub.freebsd.org (Postfix) with ESMTP id 4E73937B983 for ; Thu, 10 Aug 2000 05:42:44 -0700 (PDT) (envelope-from dermot@traveldev.com) Received: [from teebar.traveldev.com (tikka.medianet.ie [212.17.34.234] by hal.medianet.ie (DIESPAM) with ESMTP id e7ACgVh05952 for ; Thu, 10 Aug 2000 13:42:32 +0100] Received: from traveldev.com (dermot.traveldev.com [192.168.0.50]) by teebar.traveldev.com (8.10.2/8.10.2) with ESMTP id e7ACgnA15811 for ; Thu, 10 Aug 2000 13:42:49 +0100 (IST) Message-ID: <3992A35B.4D213DFB@traveldev.com> Date: Thu, 10 Aug 2000 13:43:07 +0100 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Proposed enhancement to FTP autocompletion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Something that has constantly annoyed me about the filename completion in ftp (its great usefulness notwithstanding) is how the completion of directory names works differently to in (say) bash. My preferred behaviour is that, when a directory name is completed, a slash is appended. This makes it easier to enter long paths. I set out to try to change ftp's behaviour in this way. I've made it work for the case of local files, but obviously remote files are a bit more complicated. I haven't looked comprehensively into what's involved for this, and there's a good chance that it would be unrealistic to expect to make it work for all flavours of remote FTP server. Before I tackle this, I wanted to solicit feedback - is this something people would find useful? Assuming it's possible to do it without making things really inefficient, I can't see any snags with adding the trailing slash. It will Do The Right Thing in all cases I can think of (except "get directory.tar.gz", I suppose). Also, to what extent would this cause divergence with NetBSD, which appears to be the source of autocompletion in the first place? Dermot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 7:19: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailer.seidata.com (mailer.seidata.com [208.10.211.10]) by hub.freebsd.org (Postfix) with ESMTP id E637937BE4E for ; Thu, 10 Aug 2000 07:19:00 -0700 (PDT) (envelope-from valentin@seidata.com) Received: from shell.seidata.com (shell.seidata.com [208.10.211.6] (may be forged)) by mailer.seidata.com (8.9.3/Pro-8.9.3) with ESMTP id KAA25125 for ; Thu, 10 Aug 2000 10:18:58 -0400 (EDT) Date: Thu, 10 Aug 2000 10:18:51 -0400 (EDT) From: "Valentin S. Chopov" To: current@freebsd.org Subject: ip6_input.c & ip6_output.c compile errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in sys/netinet6/ip6_input.c sys/netinet6/ip6_otput.c inetsw and ip_protox are used instead of inet6sw and ip6_protox Val == Valentin S. Chopov Phone: 1-888-200-4392 x597 E-Mail: valentin@seidata.com == To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 7:52:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 5E49837BF07 for ; Thu, 10 Aug 2000 07:51:57 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 4425 invoked from network); 10 Aug 2000 14:51:54 -0000 Received: from p3ee0d4e9.dip.t-dialin.net (HELO steele.intra) ([62.224.212.233]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 10 Aug 2000 14:51:54 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id EAA02291 for current@FreeBSD.org; Fri, 11 Aug 2000 04:51:42 +0200 (CEST) (envelope-from steele) Date: Fri, 11 Aug 2000 04:51:42 +0200 From: Benedikt Schmidt To: current@FreeBSD.org Subject: umount hangs system Message-ID: <20000811045142.A2215@cloaked.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Everytime I try to unmount one of the ufs partitions on my harddisk the system hangs and I can do nothing but a hard reset. This happens whenever I shutdown the system too. It tries to unmount one of the partitions and hangs before the "dirty flag" is removed from any of the partitions. Thats why all the partitions are checked/repaired by fsck _everytime_ I boot. I have no problem whith unmounting nfs/msdos/ext2 partitions. This problem appeared some weeks ago and I never had it before with -current. Any ideas how the problem can be solved ? ___ Benedikt Schmidt --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=fstab # Device Mountpoint FStype Options Dump Pass# /dev/ad2s1b none swap sw 0 0 /dev/ad2s1a / ufs rw 1 1 /dev/ad2s3e /usr/src ufs rw,noauto 0 0 /dev/ad2s4e /usr/home ufs rw,noauto 0 0 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 /dev/acd0c /dvd cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Tue Aug 8 05:18:42 CEST 2000 steele@steele.intra:/usr/src/sys/compile/STEELE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 412502164 Hz CPU: Pentium II/Pentium II Xeon/Celeron (412.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127184896 (124204K bytes) Preloaded elf kernel "kernel" at 0xc036c000. Preloaded elf module "randomdev.ko" at 0xc036c09c. Pentium Pro MTRR support enabled VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc02fc9b7 (1000117) VESA: 3dfx Interactive, Inc. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 0.0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: <3Dfx Voodoo 3 graphics accelerator> at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 pci0: at 7.3 sym0: <810a> port 0xa400-0xa4ff mem 0xeb001000-0xeb0010ff irq 11 at device 11.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using LOAD/STORE-based firmware. sym0: PCI BUS clock seems too high: 37822 KHz. rl0: port 0xa800-0xa8ff mem 0xeb000000-0xeb0000ff irq 5 at device 13.0 on pci0 rl0: Ethernet address: 00:e0:7d:7c:2b:37 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xac00-0xac1f irq 10 at device 15.0 on pci0 atapci1: port 0xbc00-0xbcff,0xb800-0xb803,0xb400-0xb407 irq 11 at device 19.0 on pci0 atapci2: port 0xc800-0xc8ff,0xc400-0xc403,0xc000-0xc007 irq 11 at device 19.1 on pci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 24833MB [50456/16/63] at ata0-master using UDMA33 ad2: 13783MB [28005/16/63] at ata1-master using UDMA33 acd0: DVD-ROM at ata0-slave using UDMA33 Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/ad2s1a WARNING: / was not properly dismounted cd0 at sym0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [272143 x 2048 byte records] --9jxsPFA5p3P2qPhR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 8:17: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (ppp168.dialup.st.keio.ac.jp [131.113.27.168]) by hub.freebsd.org (Postfix) with ESMTP id B66FE37BF1C for ; Thu, 10 Aug 2000 08:16:35 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.sanpei.org (8.9.3/3.7W) id AAA00961; Fri, 11 Aug 2000 00:16:26 +0900 (JST) Message-Id: <200008101516.AAA00961@lavender.sanpei.org> To: FreeBSD-current@FreeBSD.org Subject: [Problem] ata disk driver panic at boot time X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 11 Aug 2000 00:16:25 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. With latest 5-current kernel, it will always panic. My HDD does not support DMA mode. So with old kernel(maybe before sos's latest ata changes), it fallback to PIO mode(see attached text). Do only I have this problem? Thank you. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. ===== latest 5-current ==== atapci0: port 0xfcf0-0xfcff at device 20.0 on pci0ata0: at 0x1f0 irq 14 on atapci0 <> ad0: 4645MB [10068/15/63] at ata0-master using WDMA2 Mounting root from ufs:/dev/ad0s3c ad0: READ command timeout - resetting ata0: resetting devices .. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01631a4 stack pointer = 0x10:0xc02b4e1c frame pointer = 0x10:0xc02b4e40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault syncing disks... ========== ===== old 5-current kernel === ad0: 4645MB [10068/15/63] at ata0-master using WDMA2 Mounting root from ufs:/dev/ad0s3c pccard: card inserted, slot 0 ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad0: trying fallback to PIO mode ata0: resetting devices .. done ========== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 9:23:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AFBFA37B699; Thu, 10 Aug 2000 09:23:20 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id SAA01761; Thu, 10 Aug 2000 18:23:14 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.9.3) with ESMTP id e7AGN3562215; Thu, 10 Aug 2000 18:23:07 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Thu, 10 Aug 2000 18:22:58 +0200 (CEST) From: Leif Neland To: justin Cc: freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: USER PPP In-Reply-To: <000801c00260$657d4b80$668df9d0@hernandez> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Aug 2000, justin wrote: > Hey fellas... > > What I would like to do right now, however, is guarantee that > anytime, anyday, barring a problem with my ISP, that my box is > connected to the internet. I have it currently setup to dial the > internet when it boots and that seems, so far to work ok. My problem > you ask? My ISP implements a 5 minute no transfer policy, they > disconnect my connection after 5 minutes of 'idling'. What I would > like to do is have some kind of check to verify if I am still > connected to the internet and if not, execute it. I was thinking some > type of script running from crontab every 5 minutes. If I am not > connected, then automatically reconnect to the internet. > Why do you want to be online all the time? Are you running a server which should be accessible from the internet? Do you have adsl or the like available? Perhaps we will see questions on the radius- or isp-lists: How do I disconnect an user when the traffic is below a certain limit? How do I limit the number of connects daily from an user? How do I limit the number of minutes daily per user? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 10: 1:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by hub.freebsd.org (Postfix) with ESMTP id 3FCD037B957 for ; Thu, 10 Aug 2000 10:01:27 -0700 (PDT) (envelope-from Alain.Thivillon@hsc.fr) Received: from yoko.hsc.fr (yoko.hsc.fr [192.70.106.76]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "yoko.hsc.fr", Issuer CN "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id A64A010ED1; Thu, 10 Aug 2000 19:00:50 +0200 (CEST) Received: by yoko.hsc.fr (Postfix-TLS, from userid 1001) id 941B29B253; Thu, 10 Aug 2000 07:54:23 +0200 (CEST) Date: Thu, 10 Aug 2000 07:54:23 +0200 From: Alain Thivillon To: Peter Jeremy Cc: current@freebsd.org Subject: Re: Slow ssh throughput with -current Message-ID: <20000810075423.E30498@yoko.hsc.fr> References: <00Aug10.153604est.115242@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.2i In-Reply-To: <00Aug10.153604est.115242@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Thu, Aug 10, 2000 at 03:36:01PM +1000 X-Organization: Herve Schauer Consultants X-Operating-System: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy écrivait (wrote) : > Notice that although it's advertising a window size of 17520, it's > not sending the next packet until the previous packet is ack'd. I have seen the same behaviour with postfix: it seems that window is not used and that every packet should be acked before sending data. Probleme went away after a reboot. I dont known what caused problem, i use current on a laptop with ep0 and frequent suspend/resume cycles. The only non standard thing is ipfilter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 12:14:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.ocsny.com (apollo.ocsny.com [204.107.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 0083F37BAB3; Thu, 10 Aug 2000 12:14:38 -0700 (PDT) (envelope-from mikel@ocsny.com) Received: from ocsny.com (thoth.upan.org [204.107.76.16]) by apollo.ocsny.com (8.9.2/8.9.3) with ESMTP id PAA86947; Thu, 10 Aug 2000 15:12:55 -0400 (EDT) Message-ID: <39930109.DE53403@ocsny.com> Date: Thu, 10 Aug 2000 15:22:49 -0400 From: Mikel Organization: Optimized Computer Solutions, Inc. X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en,it MIME-Version: 1.0 To: Leif Neland Cc: justin , freebsd-current@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: USER PPP References: Content-Type: multipart/mixed; boundary="------------BF060A585ECDBE9A0AE4D59D" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------BF060A585ECDBE9A0AE4D59D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit better yet why not have your email client automatically download your email every 4 minutes... Leif Neland wrote: > On Wed, 9 Aug 2000, justin wrote: > > > Hey fellas... > > > > What I would like to do right now, however, is guarantee that > > anytime, anyday, barring a problem with my ISP, that my box is > > connected to the internet. I have it currently setup to dial the > > internet when it boots and that seems, so far to work ok. My problem > > you ask? My ISP implements a 5 minute no transfer policy, they > > disconnect my connection after 5 minutes of 'idling'. What I would > > like to do is have some kind of check to verify if I am still > > connected to the internet and if not, execute it. I was thinking some > > type of script running from crontab every 5 minutes. If I am not > > connected, then automatically reconnect to the internet. > > > Why do you want to be online all the time? Are you running a server which > should be accessible from the internet? > Do you have adsl or the like available? > > Perhaps we will see questions on the radius- or isp-lists: > > How do I disconnect an user when the traffic is below a certain limit? > How do I limit the number of connects daily from an user? > How do I limit the number of minutes daily per user? > > Leif > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Cheers, Mikel +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ | Optimized Computer Solutions, Inc http://www.ocsny.com | 39 W14th Street, Suite 203 212 727 2238 x132 | New York, NY 10011 +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ --------------BF060A585ECDBE9A0AE4D59D Content-Type: text/x-vcard; charset=us-ascii; name="mikel.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Mikel Content-Disposition: attachment; filename="mikel.vcf" begin:vcard n:King;Mikel tel;fax:2124638402 tel;home:http://www.upan.org tel;work:2127272100 x-mozilla-html:TRUE org:Optimized Computer Solutions version:2.1 email;internet:mikel@ocsny.com title:Director of Network Operations & Technology adr;quoted-printable:;;39 W14th St.=0D=0ASte 203;New York;NY;10011;US note;quoted-printable:fBSD, PHP, MySql and OCS Rule!!!=0D=0A=0D=0AGoal is to be MS free by the end of 2k. x-mozilla-cpt:;7312 fn:Mikel King end:vcard --------------BF060A585ECDBE9A0AE4D59D-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 14:49:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 216D837BC89 for ; Thu, 10 Aug 2000 14:49:10 -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 22:49:02 +0100 (BST) Date: Thu, 10 Aug 2000 22:49:02 +0100 From: David Malone To: Benedikt Schmidt Cc: current@FreeBSD.org Subject: Re: umount hangs system Message-ID: <20000810224902.A12029@walton.maths.tcd.ie> References: <20000811045142.A2215@cloaked.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000811045142.A2215@cloaked.de>; from BeSchmidt@cloaked.de on Fri, Aug 11, 2000 at 04:51:42AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 11, 2000 at 04:51:42AM +0200, Benedikt Schmidt wrote: > Everytime I try to unmount one of the ufs partitions on my harddisk the system > hangs and I can do nothing but a hard reset. The following was commited in the last few days - could this be what you're seeing? David. tegge 2000/08/08 17:41:54 PDT Modified files: sys/ufs/ffs ffs_softdep_stub.c Log: Initialize *countp to 0 in stub for softdep_flushworklist(). This allows ffs_fsync() to break out of a loop that might otherwise be infinite on kernels compiled without the SOFTUPDATES option. The observed symptom was a system hang at the first unmount attempt. Revision Changes Path 1.14 +2 -1 src/sys/ufs/ffs/ffs_softdep_stub.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 21:21:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id D9D8C37BBFD; Thu, 10 Aug 2000 21:21:42 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.9.3/8.8.8) id VAA68802; Thu, 10 Aug 2000 21:21:31 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200008110421.VAA68802@ns.altadena.net> Subject: Another crypto problem; no kerb4 rshd/rlogind To: current@freebsd.org, stable@freebsd.org Date: Thu, 10 Aug 2000 21:21:30 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somehow in the internat merge the kerb4 versions of rshd and rlogind disappeared (rshd -k; rlogind -ek and -k). They are often used for scripting in ways that kerberized telnet can't handle (yes, I can use expect but what a kluge :-), or I could adapt ssh for this and probably will, but that is problematic sometimes; it is harder to keep audit trails than with k4). k5 didn't implement this either at least within the fbsd "make world" context... If fbsd handles suid (not necessarily root) scripts correctly then it isn't too hard to do the wrappers needed. I've not seen whether that is ok or not in any of the normal docs. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 10 23:24: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id DA7CB37BEC5; Thu, 10 Aug 2000 23:23:55 -0700 (PDT) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id NAA06674; Fri, 11 Aug 2000 13:23:53 +0700 (NOVST) (envelope-from nnd) Date: Fri, 11 Aug 2000 13:23:53 +0700 (NOVST) Message-Id: <200008110623.NAA06674@wint.itfs.nsk.su> From: Nickolay Dudorov To: Warner Losh To: current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pccard pccard_nbk.c pcic.c In-Reply-To: <200008101735.KAA21513@freefall.freebsd.org> X-Newsgroups: itfs.freebsd.cvs.all User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After the next commit 'make buildkernel' stops in 'sys/modules/oldcard' directory. After applaing the following patch I can make buildkernel. N.Dudorov > imp 2000/08/10 10:35:11 PDT > > Modified files: > sys/pccard pccard_nbk.c pcic.c > Log: > Add some infrastructure support for dealing with large attribute > memory space needed by the raylink driver (in progress, nearing > completion). > > This is a minorly cleaned up diff from Duncan to help him reduce the > diffs from stock FreeBSD. > > Submitted by: Duncan Barclay > > Revision Changes Path > 1.20 +10 -1 src/sys/pccard/pccard_nbk.c > 1.95 +53 -6 src/sys/pccard/pcic.c > Index: sys/dev/pccard/card_if.m =================================================================== RCS file: /store/CVS/src/sys/dev/pccard/card_if.m,v retrieving revision 1.6 diff -b -u -r1.6 card_if.m --- sys/dev/pccard/card_if.m 2000/06/18 05:02:09 1.6 +++ sys/dev/pccard/card_if.m 2000/08/11 06:00:24 @@ -66,6 +66,13 @@ u_int32_t offset; } +METHOD int get_memory_offset { + device_t dev; + device_t child; + int rid; + u_int32_t *offset; +} + # # pccard bridges call this method to initate the attachment of a card # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 7:25: 7 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 7:48:38 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 8:34:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from lax.whistle.com (s205m133.whistle.com [207.76.205.133]) by hub.freebsd.org (Postfix) with ESMTP id 782A937B650 for ; Fri, 11 Aug 2000 08:34:09 -0700 (PDT) (envelope-from evan@whistle.com) Received: from whistle.com (localhost [127.0.0.1]) by lax.whistle.com (8.9.3/8.9.3) with ESMTP id XAA73199; Thu, 10 Aug 2000 23:24:07 -0700 (PDT) (envelope-from evan@whistle.com) Message-ID: <39939C07.52AB0061@whistle.com> Date: Thu, 10 Aug 2000 23:24:07 -0700 From: Evan Oldford Organization: Whistle Communications X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Benedikt Schmidt Cc: current@FreeBSD.ORG Subject: Re: umount hangs system References: <20000811045142.A2215@cloaked.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Benedikt Schmidt wrote: > > Everytime I try to unmount one of the ufs partitions on my harddisk the system > hangs and I can do nothing but a hard reset. > > This happens whenever I shutdown the system too. It tries to unmount one of > the partitions and hangs before the "dirty flag" is removed from any of the > partitions. Thats why all the partitions are checked/repaired by fsck > _everytime_ I boot. > > I have no problem whith unmounting nfs/msdos/ext2 partitions. > > This problem appeared some weeks ago and I never had it before with -current. > > Any ideas how the problem can be solved ? Did you take the "device apm" out of your kernel? I saw this same behavior on my laptop when I took apm out of my kernel. When I put it back in everything was back to normal. > > ___ > Benedikt Schmidt > > -- ___________________________________________________________________________ Evan Oldford * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 8:35:38 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 8:55: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D700637BF9B for ; Fri, 11 Aug 2000 08:54:59 -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 JAA08739; Fri, 11 Aug 2000 09:54:58 -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 JAA34677; Fri, 11 Aug 2000 09:54:27 -0600 (MDT) Message-Id: <200008111554.JAA34677@harmony.village.org> To: Nickolay Dudorov Subject: Re: cvs commit: src/sys/pccard pccard_nbk.c pcic.c Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 11 Aug 2000 13:23:53 +0700." <200008110623.NAA06674@wint.itfs.nsk.su> References: <200008110623.NAA06674@wint.itfs.nsk.su> Date: Fri, 11 Aug 2000 09:54:27 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200008110623.NAA06674@wint.itfs.nsk.su> Nickolay Dudorov writes: : After the next commit 'make buildkernel' stops in : 'sys/modules/oldcard' directory. After applaing the following patch : I can make buildkernel. I broke this, I'm sorry. I just committed a fix. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 9:56:16 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 10: 6:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from smople.thehub.com.au (smople.thehub.com.au [203.143.240.10]) by hub.freebsd.org (Postfix) with ESMTP id 535F237B5B1 for ; Fri, 11 Aug 2000 10:06:49 -0700 (PDT) (envelope-from mckay@thehub.com.au) Received: from gift.home (ppp98.dyn248.pacific.net.au [203.143.248.98]) by smople.thehub.com.au (8.9.3/8.9.1) with ESMTP id DAA57750; Sat, 12 Aug 2000 03:06:15 +1000 (EST) Received: (from mckay@localhost) by gift.home (8.9.3/8.9.3) id DAA00692; Sat, 12 Aug 2000 03:02:41 +1000 (EST) (envelope-from mckay) Date: Sat, 12 Aug 2000 03:02:40 +1000 From: Stephen McKay To: freebsd-current@freebsd.org Cc: David Greenman , Alfred Perlstein , Stephen McKay Subject: Re: Ugly, slow shutdown Message-ID: <20000812030240.A668@gift.home> References: <200008080238.TAA40871@vashon.polstra.com> <200008080558.WAA05458@implode.root.com> <20000808005100.A4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000808005100.A4854@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Aug 08, 2000 at 12:51:00AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I've failed in my main objective (to deuglify the shutdown messages), but an interesting debate has resulted instead, so I can't feel too bad. I did a little research to support my position on sleep/wakeup, and here's the best I have. This is pretty long, and unlikely to shake your world view, so those of you with drooping eyelids can just head over to slashdot, or something. :-) Some pseudo code from "The Design of the Unix Operating System", by Maurice Bach, page 33 shows how sleep() is used: while (condition is true) sleep (event: the condition becomes false); set condition true; and the next page shows how wakeup() is used: set condition false; wakeup (event: the condition is false); In the description, it says `Thus, the "while-sleep" loop insures that at most one process can gain access to a resource.' Not the most convincing evidence, but on the other hand, he does not mention the idea of *not* protecting against sudden wakeup. From "Writing a Unix Device Driver", by Egan and Teixeira, on page 92 we find It is not uncommon for several processes to sleep on the same channel. They may be competing for the same resource, or they may be waiting for different reasons that have been associated with the same channel value. In this situation a single wakeup call on the common channel will cause all the sleeping processes to become executable; ... A driver routine must not assume that it can proceed after a return from a sleep call. It should check to see whether the event it was waiting for has actually occurred; if it has not it should sleep again, and repeat this cycle until the awaited event has actually occurred. The book is oriented rather towards I/O, so perhaps not all possible uses of routines are covered. But again, no mention of *not* using a while loop. Quite the opposite. Also "Magic Garden Explained" points out that you really want to sleep on an "event", but all you have is the address of some data. So, you often have multiple semantically different events represented by the same integer wakeup channel. A good reason to program defensively, I think. But the best evidence is from kern_synch.c from 4.2 BSD, line 98, in the header comment of the sleep() routine: * Callers of this routine must be prepared for * premature return, and check that the reason for * sleeping has gone away. That comment on sleep() is present from 4.0 BSD up to and including 4.3 tahoe, but disappears in 4.3 reno, when the 4.4 style tsleep() was introduced. After a bit of searching through the PUPS archive, I see it is even present in Edition 6, character for character, in a file called slp.c. Well, I knew I wasn't a senile old fart yet, and Kirk's BSD CD compendium and the PUPS archive show that I remember some things correctly still. For a considerable portion of Unix history, sleep() could return for no good reason at all, and was documented to do so (if only in the source code). Now, how does this relate to the current day? Nobody in the BSD world uses plain sleep() any more. Once tsleep() appeared, the rules seem to have changed. Perhaps some people had gotten away with ignoring the dire warnings in the sleep() code, and decided that unexpected wakeups weren't such a useful part of the API. I hope Kirk or other BSD veterans can be coaxed into offering an opinion. I'd offer at least one beer for this purpose. :-) Regardless of the history of it all, FreeBSD is full of places where unexpected wakeups can stuff you right up. Should we regard tsleep() like the older sleep() call, as suspect, and program defensively? Should we be pragmatic, admit "We've gotten away with it so far", and document the "no sudden wakeups" behaviour? I quite like the general principle outlined in one of the earlier replies, that a while loop can be shown to be correct through a local code reading, but a simple conditional must be verified by reading all the rest of the code. That's close to the same argument I use against global variables. Their use is too hard to verify as correct. In short, I'd like to see all cases where tsleep() is not carefully used in a loop repaired. Practically speaking, though, I can't see that happening, especially if we have any major players against the idea (DG for example). Given that, I'd like as a minimum a bit more of the history of sleep() in the tsleep() manual page, and a discussion of when a while-loop protected tsleep() is mandatory, and when it is optional. Some sort of pronouncement against issuing wakeup() calls against arbitrary addresses would help too. I would do that right now, except I'm escaping computing for a few months. Almost heresy nowadays, I suppose. And I won't be the first in line for a brain implanted net connection either. ;-) Stephen. PS By the time you read this, I've probably unsubscribed to everything. Please CC me in any replies. I'll read mail when I get a chance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 10:18: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout2.silyn-tek.de (mout2.silyn-tek.de [194.25.165.70]) by hub.freebsd.org (Postfix) with ESMTP id BACB637B77B for ; Fri, 11 Aug 2000 10:17:58 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.33] (helo=mx1.silyn-tek.de) by mout2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13NIQh-0005Tm-00; Fri, 11 Aug 2000 19:17:11 +0200 Received: from p3e9e278a.dip0.t-ipconnect.de ([62.158.39.138] helo=neutron.cichlids.com) by mx1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13NIQg-0006KR-00; Fri, 11 Aug 2000 19:17:10 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 0CC95AB91; Fri, 11 Aug 2000 19:17:32 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 6AC2314A66; Fri, 11 Aug 2000 19:16:57 +0200 (CEST) Date: Fri, 11 Aug 2000 19:16:57 +0200 To: The Hermit Hacker Cc: Irwan Hadi , wonko@entropy.tmok.com, freebsd-current@FreeBSD.ORG Subject: Re: hotmail now running win2000 Message-ID: <20000811191657.A8035@cichlids.cichlids.com> Mail-Followup-To: The Hermit Hacker , Irwan Hadi , wonko@entropy.tmok.com, freebsd-current@FreeBSD.ORG References: <4.2.0.58.20000808224658.00a83c70@staf.bpkpenabur.or.id> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from scrappy@hub.org on Wed, Aug 09, 2000 at 01:51:44AM -0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake The Hermit Hacker (scrappy@hub.org): > switch is web administered, so it would be too easy to build a quick perl > script to trigger a power outlet correspondign to the partiular server a quick DirectActiveVBScript, you mean. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 10:28: 4 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 11: 7:59 2000 Delivered-To: freebsd-current@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-current@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-current" in the body of the message From owner-freebsd-current Fri Aug 11 11:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 4408237B5A6 for ; Fri, 11 Aug 2000 11:23:10 -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 UAA23504; Fri, 11 Aug 2000 20:22:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG, David Greenman , Alfred Perlstein Subject: Re: Ugly, slow shutdown In-Reply-To: Your message of "Sat, 12 Aug 2000 03:02:40 +1000." <20000812030240.A668@gift.home> Date: Fri, 11 Aug 2000 20:22:46 +0200 Message-ID: <23502.966018166@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000812030240.A668@gift.home>, Stephen McKay writes: >Regardless of the history of it all, FreeBSD is full of places where >unexpected wakeups can stuff you right up. Should we regard tsleep() like >the older sleep() call, as suspect, and program defensively? Should we >be pragmatic, admit "We've gotten away with it so far", and document the >"no sudden wakeups" behaviour? > >I quite like the general principle outlined in one of the earlier replies, >that a while loop can be shown to be correct through a local code reading, >but a simple conditional must be verified by reading all the rest of the >code. That's close to the same argument I use against global variables. >Their use is too hard to verify as correct. I support this notion with a footnote to the effect that if the test is expensive the while() can be left out if a comment points out exactly why the while() isn't needed. -- 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-current" in the body of the message From owner-freebsd-current Fri Aug 11 15:31:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-201-63-44.dsl.snfc21.pacbell.net [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id BFB6C37B9C7 for ; Fri, 11 Aug 2000 15:31:41 -0700 (PDT) (envelope-from mike@adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id PAA48672; Fri, 11 Aug 2000 15:30:54 -0700 (PDT) (envelope-from mike@adept.org) Date: Fri, 11 Aug 2000 15:30:54 -0700 (PDT) From: Mike Hoskins To: Evan Oldford Cc: Benedikt Schmidt , current@FreeBSD.ORG Subject: Re: umount hangs system In-Reply-To: <39939C07.52AB0061@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Aug 2000, Evan Oldford wrote: > > This happens whenever I shutdown the system too. It tries to unmount one of > > the partitions and hangs before the "dirty flag" is removed from any of the > > partitions. Thats why all the partitions are checked/repaired by fsck > > _everytime_ I boot. > Did you take the "device apm" out of your kernel? > I saw this same behavior on my laptop when I took apm out > of my kernel. When I put it back in everything was > back to normal. I saw this same behavior 1-2 weeks ago on my -current desktop without apm. Now... FreeBSD storm.adept.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Aug 8 20:34:08 PDT 2000 mike@storm.adept.org:/usr/src/sys/compile/STORM i386 ...I do not see the behavior when I reboot. -mrh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 15:40:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id A751237BC31 for ; Fri, 11 Aug 2000 15:40:48 -0700 (PDT) (envelope-from markk@knigma.org) Received: from modem-102.sodium.dialup.pol.co.uk ([62.136.10.102] helo=lap.knigma.org) by mail5.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13NNTq-0000qS-00 for freebsd-current@freebsd.org; Fri, 11 Aug 2000 23:40:47 +0100 Message-ID: Date: Fri, 11 Aug 2000 23:40:11 +0100 To: freebsd-current@freebsd.org From: Mark Knight Subject: cvsup overzealous MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With world and kernel of 10th August, 01:00 GMT cvsup is reporting 'SetAttrs' adjustments for every file it encounters on repeated runs against a server that has not been updated. Running under an old kernel, cvsup is not performing any updates. -- Mark Knight PGP Public Key: finger mkn@knigma.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 11 19:21:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 496E937BD15 for ; Fri, 11 Aug 2000 19:21:32 -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 TAA27025; Fri, 11 Aug 2000 19:21: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 TAA60376; Fri, 11 Aug 2000 19:21:26 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 11 Aug 2000 19:21:26 -0700 (PDT) Message-Id: <200008120221.TAA60376@vashon.polstra.com> To: current@freebsd.org Cc: markk@knigma.org Subject: Re: -current kernel causes CVSup SetAttrs flood (was: cvsup overzealous) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I changed the subject to something more represenative.] In article , Mark Knight wrote: > With world and kernel of 10th August, 01:00 GMT cvsup is reporting > 'SetAttrs' adjustments for every file it encounters on repeated runs > against a server that has not been updated. > > Running under an old kernel, cvsup is not performing any updates. Stranger things have happened, but still I am skeptical of this. Please make sure that the kernel is really the only difference. Especially check that on each run you: - have the same umask - are logged in as the same user - are using the same cvsup command line and supfile Thanks, 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-current" in the body of the message From owner-freebsd-current Fri Aug 11 20:59:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.teleport.com (mail2.teleport.com [192.108.254.43]) by hub.freebsd.org (Postfix) with SMTP id 22A7037B69D for ; Fri, 11 Aug 2000 20:59:35 -0700 (PDT) (envelope-from anholt@teleport.com) Received: (qmail 15478 invoked from network); 12 Aug 2000 03:59:32 -0000 Received: from i48-04-27.pdx.du.teleport.com (HELO ?192.168.0.11?) (216.26.2.219) by mail2.teleport.com with SMTP; 12 Aug 2000 03:59:32 -0000 Mime-Version: 1.0 X-Sender: anholt@mail.teleport.com Message-Id: Date: Fri, 11 Aug 2000 20:58:48 -0700 To: freebsd-current@freebsd.org From: Eric Anholt Subject: ppp troubles Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been seeing these errors for about a month now. When PPP is first started, it outputs: calwell:/usr/src/bzflag>ppp -ddial -nat papchap Working in ddial mode Using interface: tun0 Warning: Add route failed: 0.0.0.0: errno: Network is unreachable It still dials and connects, then gets an IP, but I never get the default route. I have to manually ifconfig to find the ip and route add default it. Before: calwell:/usr/src/bzflag> netstat -rn | head Routing tables Internet: Destination Gateway Flags Netif Expire 127.0.0.1 127.0.0.1 UH 4 69726 lo0 192.168/16 link#1 UC 0 0 rl0 => 192.168.0.1 0:c0:ca:12:7d:30 UHLW 0 8 lo0 192.168.0.11 0:5:2:b6:ad:21 UHLW 1 106946 rl0 251 192.168.0.12 0:80:ad:b0:3b:ef UHLW 2 342 rl0 1162 192.168.255.255 ff:ff:ff:ff:ff:ff UHLWb 3 155 rl0 After: calwell:/usr/src/bzflag> netstat -rn | head Routing tables Internet: Destination Gateway Flags Netif Expire default 216.26.1.5 UGSc 3 24 tun0 127.0.0.1 127.0.0.1 UH 4 69750 lo0 192.168/16 link#1 UC 0 0 rl0 => 192.168.0.1 0:c0:ca:12:7d:30 UHLW 0 8 lo0 192.168.0.11 0:5:2:b6:ad:21 UHLW 1 106973 rl0 208 192.168.0.12 0:80:ad:b0:3b:ef UHLW 2 342 rl0 1119 calwell:/usr/src/bzflag> ifconfig tun0 tun0: flags=8051 mtu 1524 inet6 fe80::2c0:caff:fe12:7d30%tun0 --> :: prefixlen 64 scopeid 0xa inet 216.26.2.219 --> 216.26.1.5 netmask 0xffffff00 Opened by PID 21106 Excerpts from ppp.conf default: set device /dev/cuaa0 set log Phase Chat LCP IPCP tun command connect #CCP set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 120 # 3 mintue idle timer (the default) set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 add default HISADDR # Add a (sticky) default route (then the regular papchap stuff) Can anyone help me? This is really annying, especially since I have a very nasty connection that keeps dropping and making me route delete, ifconfig -a ( & repeat), route add again. If there is any other info needed, I would be glad to post. -- -- Eric Anholt anholt@teleport.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 2:17:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 2E24037BC4E for ; Sat, 12 Aug 2000 02:17:12 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id B56E32CE6A; Sat, 12 Aug 2000 11:17:07 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1001) id 8E8604CFB; Sat, 12 Aug 2000 11:18:09 +0200 (EET) Date: Sat, 12 Aug 2000 11:18:09 +0200 From: Vallo Kallaste To: Eric Anholt Cc: freebsd-current@freebsd.org Subject: Re: ppp troubles Message-ID: <20000812111809.A10559@myhakas.matti.ee> Reply-To: vallo@matti.ee 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 anholt@teleport.com on Fri, Aug 11, 2000 at 08:58:48PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 11, 2000 at 08:58:48PM -0700, Eric Anholt wrote: > I've been seeing these errors for about a month now. When PPP is > first started, it outputs: > calwell:/usr/src/bzflag>ppp -ddial -nat papchap > Working in ddial mode > Using interface: tun0 > Warning: Add route failed: 0.0.0.0: errno: Network is unreachable > > It still dials and connects, then gets an IP, but I never get the > default route. I have to manually ifconfig to find the ip and route > add default it. > Can anyone help me? This is really annying, especially since I have > a very nasty connection that keeps dropping and making me route > delete, ifconfig -a ( & repeat), route add again. I'm getting same behaviour, workaround is to put the HISADDR line to ppp.linkup file, so it tries to set up default route after link is up. I'm running -current as of few days ago. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 3:45:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.silyn-tek.de (mout1.silyn-tek.de [194.25.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 4D75437B833; Sat, 12 Aug 2000 03:45:24 -0700 (PDT) (envelope-from alex@big.endian.de) Received: from [192.168.32.34] (helo=mx2.silyn-tek.de) by mout1.silyn-tek.de with esmtp (Exim 3.13 #1) id 13NYn4-0007JJ-00; Sat, 12 Aug 2000 12:45:22 +0200 Received: from p3ee1c3c5.dip0.t-ipconnect.de ([62.225.195.197] helo=neutron.cichlids.com) by mx2.silyn-tek.de with esmtp (Exim 3.13 #1) id 13NYn4-0007Bd-00; Sat, 12 Aug 2000 12:45:22 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 59BE4AB91; Sat, 12 Aug 2000 12:45:53 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 48BA614A66; Sat, 12 Aug 2000 12:45:23 +0200 (CEST) Date: Sat, 12 Aug 2000 12:45:22 +0200 To: current@freebsd.org Cc: semenu@freebsd.org Subject: mount_hpfs not built by default Message-ID: <20000812124522.A3026@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org, semenu@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. From: alex@big.endian.de (Alexander Langer) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! In PR docs/20369 it was mentioned that mount_hpfs isn't built by default. Am I missing something? Why not? From the cvs-logs, it seems, it has just been forgotten :) However, I'm asking because maybe I missed a discussion back in December. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 7:23:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail5.svr.pol.co.uk (mail5.svr.pol.co.uk [195.92.193.20]) by hub.freebsd.org (Postfix) with ESMTP id 77DAE37B6E6 for ; Sat, 12 Aug 2000 07:23:27 -0700 (PDT) (envelope-from markk@knigma.org) Received: from modem-237.sodium.dialup.pol.co.uk ([62.136.10.237] helo=lap.knigma.org) by mail5.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 13NcC5-0007kb-00 for freebsd-current@freebsd.org; Sat, 12 Aug 2000 15:23:26 +0100 Message-ID: Date: Sat, 12 Aug 2000 15:22:53 +0100 To: freebsd-current@freebsd.org From: Mark Knight Subject: Re: -current kernel causes CVSup SetAttrs flood (was: cvsup overzealous) References: <200008120221.TAA60376@vashon.polstra.com> In-Reply-To: <200008120221.TAA60376@vashon.polstra.com> MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 U Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200008120221.TAA60376@vashon.polstra.com>, John Polstra writes >[I changed the subject to something more represenative.] > >In article , >Mark Knight wrote: >> With world and kernel of 10th August, 01:00 GMT cvsup is reporting >> 'SetAttrs' adjustments for every file it encounters on repeated runs >> against a server that has not been updated. >> >> Running under an old kernel, cvsup is not performing any updates. > >Stranger things have happened, but still I am skeptical of this. >Please make sure that the kernel is really the only difference. >Especially check that on each run you: > > - have the same umask yes > - are logged in as the same user yes > - are using the same cvsup command line and supfile yes It was repeatable over several reboots, switching between the two kernels. I've just performed a new sup, and with a new kernel everything is fine again... I'll put it down to a bad snapshot for want of a better explanation. Thanks! -- Mark Knight PGP Public Key: finger mkn@knigma.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 8:49:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from numbertwo.domainfactory.de (numbertwo.domainfactory.de [194.221.134.226]) by hub.freebsd.org (Postfix) with SMTP id 9C47237BDB8 for ; Sat, 12 Aug 2000 08:49:23 -0700 (PDT) (envelope-from steele@cloaked.de) Received: (qmail 5108 invoked from network); 12 Aug 2000 15:49:20 -0000 Received: from p3ee07fc5.dip.t-dialin.net (HELO steele.intra) ([62.224.127.197]) (envelope-sender ) by numbertwo.domainfactory.de (qmail-ldap-1.03) with SMTP for ; 12 Aug 2000 15:49:20 -0000 Received: (from steele@localhost) by steele.intra (8.9.3/8.9.3) id FAA00948; Sun, 13 Aug 2000 05:48:56 +0200 (CEST) (envelope-from steele) Date: Sun, 13 Aug 2000 05:48:55 +0200 From: Benedikt Schmidt To: Mike Hoskins Cc: Evan Oldford , current@FreeBSD.ORG Subject: Re: umount hangs system Message-ID: <20000813054855.A390@cloaked.de> References: <39939C07.52AB0061@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from mike@adept.org on Fri, Aug 11, 2000 at 03:30:54PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 11, 2000 at 03:30:54PM -0700, Mike Hoskins wrote: > On Thu, 10 Aug 2000, Evan Oldford wrote: > > > > This happens whenever I shutdown the system too. It tries to unmount one of > > > the partitions and hangs before the "dirty flag" is removed from any of the > > > partitions. Thats why all the partitions are checked/repaired by fsck > > > _everytime_ I boot. > > Did you take the "device apm" out of your kernel? > > I saw this same behavior on my laptop when I took apm out > > of my kernel. When I put it back in everything was > > back to normal. > > I saw this same behavior 1-2 weeks ago on my -current desktop without > apm. Now... > > FreeBSD storm.adept.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Aug 8 > 20:34:08 PDT 2000 mike@storm.adept.org:/usr/src/sys/compile/STORM > i386 > > ...I do not see the behavior when I reboot. A make world with the updated sources didn't solve the problem. I had to put "device apm" back in the kernel. I put it in some weeks ago because I wanted to try out automatic powerdown. But since it didn't work I removed the "device apm" line and it seems like that caused the umount problem. ___ Benedikt Schmidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 11: 4:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B34837B55E for ; Sat, 12 Aug 2000 11:04:37 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.9.3/8.8.8) id LAA41768 for current@freebsd.org; Sat, 12 Aug 2000 11:04:13 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200008121804.LAA41768@ns.altadena.net> Subject: inet6 STILL!!! To: current@freebsd.org Date: Sat, 12 Aug 2000 11:04:13 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvsup this morning; there was a patch out for this a week ago? ----------------------------------------------------------------------- cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/ip6_fw.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../netinet6/ip6_input.c ../../netinet6/ip6_input.c: In function `ip6_input': ../../netinet6/ip6_input.c:312: `inetsw' undeclared (first use in this function) ../../netinet6/ip6_input.c:312: (Each undeclared identifier is reported only once ../../netinet6/ip6_input.c:312: for each function it appears in.) ../../netinet6/ip6_input.c:312: `ip_protox' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sys/compile/PUFFIN. ------------------------------------------------------------------------- -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 11:19: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id D780A37B676 for ; Sat, 12 Aug 2000 11:19:01 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:OlC105unix6gadoYyNFgq1J8F30bSpetIyOfRMasLbuekDkdve99926J/kO+jlrc@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/8.11.0/peace) with ESMTP/inet6 id e7CII9u09139; Sun, 13 Aug 2000 03:18:09 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 13 Aug 2000 03:18:05 +0900 (JST) Message-Id: <20000813.031805.59468859.ume@mahoroba.org> To: pete@ns.altadena.net Cc: current@freebsd.org Subject: Re: inet6 STILL!!! From: Hajimu UMEMOTO In-Reply-To: <200008121804.LAA41768@ns.altadena.net> References: <200008121804.LAA41768@ns.altadena.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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Sat, 12 Aug 2000 11:04:13 -0700 (PDT) >>>>> Pete Carah said: pete> cvsup this morning; there was a patch out for this a week ago? I just committed it. However, I have never using ipfilter at all. I don't know if ipfilter works for IPv6. At least, KAME doesn't have ipfilter. -- 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-current" in the body of the message From owner-freebsd-current Sat Aug 12 11:53:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id B6F0637B9D6; Sat, 12 Aug 2000 11:53:21 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:5sW48FFNo1i0pCyagAAcsyzpCR+1Wc6Ea42r9xq+xLkT8ORVWuY8kG3Xy3r0Ctoe@localhost [::1]) (authenticated) by peace.mahoroba.org (8.11.0/8.11.0/peace) with ESMTP/inet6 id e7CIqku09217; Sun, 13 Aug 2000 03:52:46 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 13 Aug 2000 03:52:43 +0900 (JST) Message-Id: <20000813.035243.92583336.ume@mahoroba.org> To: mobile@freebsd.org, current@freebsd.org Subject: CFR: apm obtain per battery information From: Hajimu UMEMOTO X-Mailer: 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wish to merge UNIX domain socket feature to pccardd from PAO. This makes pccard related PAO3/ports such as gxcardmon work. This means you can control your pccard from GUI based application. It requires introducing inactive state to cardstate in the kernel. This state is "the card stays in the slot, but power is not supplied". http://www.imasy.or.jp/~ume/FreeBSD/4.1-RC-pccard-server.diff This patch is actually for 4.1-RC. But it is applicable to 5.0-CURRENT or 4.1-STABLE. If there is no objection, I'll commit this next week end. Thanks, -- 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-current" in the body of the message From owner-freebsd-current Sat Aug 12 12: 3: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from tribble.medianet.ie (tribble.medianet.ie [212.17.32.6]) by hub.freebsd.org (Postfix) with ESMTP id 0748737B52C for ; Sat, 12 Aug 2000 12:02:58 -0700 (PDT) (envelope-from dermot@traveldev.com) Received: [from teebar.traveldev.com (butteredtoast.medianet.ie [212.17.34.43]) by tribble.medianet.ie (DIESPAM) with ESMTP id e7CJ2tv28842 for ; Sat, 12 Aug 2000 20:02:55 +0100] Received: from traveldev.com (dermot.traveldev.com [192.168.0.50]) by teebar.traveldev.com (8.10.2/8.10.2) with ESMTP id e7CJ3FR15975 for ; Sat, 12 Aug 2000 20:03:15 +0100 (IST) Message-ID: <39959F8E.8D3FB78@traveldev.com> Date: Sat, 12 Aug 2000 20:03:42 +0100 From: Dermot McNally X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Proposed enhancement to FTP autocompletion References: <3992A35B.4D213DFB@traveldev.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Since I got some encouragement in private mail, I've produced the enclosed patches to ftp. The changes are direct copies from the NetBSD ftp client and from "lukemftp" (ftp://ftp.netbsd.org/pub/NetBSD/misc/lukemftp/). They do the following: Spaces in completed file/directory names (local and remote) are now escaped (NetBSD) Slashes are now appended to completed local directories (lukemftp) There's a bunch of other stuff in lukemftp that may be worth using, but it doesn't append slashes for remote directories either - I'll be having a closer look at this, it's certainly doable, but possibly not very elegantly. Comments, criticism? Dermot Index: complete.c =================================================================== RCS file: /usr/local/ncvs/src/usr.bin/ftp/complete.c,v retrieving revision 1.5 diff -c -r1.5 complete.c *** complete.c 1999/08/28 01:01:30 1.5 --- complete.c 2000/08/12 18:33:11 *************** *** 56,61 **** --- 56,62 ---- #include #include #include + #include #include "ftp_var.h" *************** *** 83,89 **** StringList *words; { char insertstr[MAXPATHLEN]; ! char *lastmatch; int i, j; size_t matchlen, wordlen; --- 84,90 ---- StringList *words; { char insertstr[MAXPATHLEN]; ! char *lastmatch, *p; int i, j; size_t matchlen, wordlen; *************** *** 92,99 **** return (CC_ERROR); /* no choices available */ if (words->sl_cur == 1) { /* only once choice available */ ! (void)strcpy(insertstr, words->sl_str[0]); ! if (el_insertstr(el, insertstr + wordlen) == -1) return (CC_ERROR); else return (CC_REFRESH); --- 93,103 ---- return (CC_ERROR); /* no choices available */ if (words->sl_cur == 1) { /* only once choice available */ ! p = words->sl_str[0] + wordlen; ! if (*p == '\0') /* at end of word? */ ! return (CC_REFRESH); ! ftpvis(insertstr, sizeof(insertstr), p, strlen(p)); ! if (el_insertstr(el, insertstr) == -1) return (CC_ERROR); else return (CC_REFRESH); *************** *** 111,119 **** matchlen = j; } if (matchlen > wordlen) { ! (void)strncpy(insertstr, lastmatch, matchlen); ! insertstr[matchlen] = '\0'; ! if (el_insertstr(el, insertstr + wordlen) == -1) return (CC_ERROR); else /* --- 115,123 ---- matchlen = j; } if (matchlen > wordlen) { ! ftpvis(insertstr, sizeof(insertstr), ! lastmatch + wordlen, matchlen - wordlen); ! if (el_insertstr(el, insertstr) == -1) return (CC_ERROR); else /* *************** *** 209,214 **** --- 213,235 ---- closedir(dd); rv = complete_ambiguous(file, list, words); + if (rv == CC_REFRESH) { + struct stat sb; + char path[MAXPATHLEN]; + + (void)strlcpy(path, dir, sizeof(path)); + (void)strlcat(path, "/", sizeof(path)); + (void)strlcat(path, words->sl_str[0], sizeof(path)); + + if (stat(path, &sb) >= 0) { + char suffix[2] = " "; + + if (S_ISDIR(sb.st_mode)) + suffix[0] = '/'; + if (el_insertstr(el, suffix) == -1) + rv = CC_ERROR; + } + } sl_free(words, 1); return (rv); } Index: util.c =================================================================== RCS file: /usr/local/ncvs/src/usr.bin/ftp/util.c,v retrieving revision 1.13 diff -c -r1.13 util.c *** util.c 2000/05/22 17:18:38 1.13 --- util.c 2000/08/12 18:29:56 *************** *** 851,856 **** --- 851,886 ---- #endif /* !SMALL */ /* + * Copy characters from src into dst, \ quoting characters that require it + */ + void + ftpvis(char *dst, size_t dstlen, const char *src, size_t srclen) + { + int di, si; + + for (di = si = 0; + src[si] != '\0' && di < dstlen && si < srclen; + di++, si++) { + switch (src[si]) { + case '\\': + case ' ': + case '\t': + case '\r': + case '\n': + case '"': + dst[di++] = '\\'; + if (di >= dstlen) + break; + /* FALLTHROUGH */ + default: + dst[di] = src[si]; + } + } + dst[di] = '\0'; + } + + + /* * Determine if given string is an IPv6 address or not. * Return 1 for yes, 0 for no */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 15:40:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 6634C37B804 for ; Sat, 12 Aug 2000 15:40:25 -0700 (PDT) (envelope-from gshapiro@gshapiro.net) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.0/8.11.0) id e7CMePt74927; Sat, 12 Aug 2000 15:40:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14741.53848.763058.787717@horsey.gshapiro.net> Date: Sat, 12 Aug 2000 15:40:24 -0700 (PDT) From: Gregory Neil Shapiro To: freebsd-current@freebsd.org Subject: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current X-Mailer: VM 6.75 under 21.2 (beta35) "Nike" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sendmail has been updated from 8.9.3 to 8.11.0. Some of the more visible changes that may immediately affect your configuration include: - New default file locations from src/contrib/sendmail/cf/README - newaliases limited to root and trusted users - MSA port (587) turned on by default - New queue file naming system so can't go from 8.11 -> 8.9 - mail.local FreeBSD-only -b option changed to -B - FEATURE(`rbl') renamed to FEATURE(`dnsbl') - FEATURE(`nullclient') is more full featured - FEATURE(`nouucp') requires an argument: `reject' or `nospecial' - See src/contrib/sendmail/RELEASE_NOTES for more info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 15:50:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 5400E37BA94 for ; Sat, 12 Aug 2000 15:50:08 -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 XAA12886; Sat, 12 Aug 2000 23:49:25 +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 VAA02385; Sat, 12 Aug 2000 21:34:55 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008122034.VAA02385@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Leif Neland" Cc: freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: ppp.linkdown In-Reply-To: Message from "Leif Neland" of "Mon, 31 Jul 2000 19:49:35 +0200." <007701bffb18$4e58e9e0$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Aug 2000 21:34:55 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is ppp.linkdown executed before or after the link is down? > > I'd like to change a dyndns, but will link activity done in linkdown defeat > the timeout, or start a new call? It'll start a new call in auto mode. > Leif -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 15:50:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id F0AAF37BBF8 for ; Sat, 12 Aug 2000 15:50:12 -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 XAA12884; Sat, 12 Aug 2000 23:49:24 +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 WAA00462; Sat, 12 Aug 2000 22:50:44 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008122150.WAA00462@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Knight Cc: freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: cvsup overzealous In-Reply-To: Message from Mark Knight of "Fri, 11 Aug 2000 23:40:11 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Aug 2000 22:50:44 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > With world and kernel of 10th August, 01:00 GMT cvsup is reporting > 'SetAttrs' adjustments for every file it encounters on repeated runs > against a server that has not been updated. > > Running under an old kernel, cvsup is not performing any updates. This isn't by any chance because you cvsup'd from my laptop is it ? I chmod my repository with g+w, so if you sup from me, then from a real machine you get shed-loads of setattrs.... > -- > Mark Knight PGP Public Key: finger mkn@knigma.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 15:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 7AED837BA94 for ; Sat, 12 Aug 2000 15:50:20 -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 XAA12885; Sat, 12 Aug 2000 23:49:25 +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 WAA00491; Sat, 12 Aug 2000 22:55:08 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200008122155.WAA00491@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: vallo@matti.ee Cc: Eric Anholt , freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: ppp troubles In-Reply-To: Message from Vallo Kallaste of "Sat, 12 Aug 2000 11:18:09 +0200." <20000812111809.A10559@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Aug 2000 22:55:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Aug 11, 2000 at 08:58:48PM -0700, Eric Anholt wrote: > > > I've been seeing these errors for about a month now. When PPP is > > first started, it outputs: > > calwell:/usr/src/bzflag>ppp -ddial -nat papchap > > Working in ddial mode > > Using interface: tun0 > > Warning: Add route failed: 0.0.0.0: errno: Network is unreachable > > > > It still dials and connects, then gets an IP, but I never get the > > default route. I have to manually ifconfig to find the ip and route > > add default it. > > > Can anyone help me? This is really annying, especially since I have > > a very nasty connection that keeps dropping and making me route > > delete, ifconfig -a ( & repeat), route add again. > > I'm getting same behaviour, workaround is to put the HISADDR line to > ppp.linkup file, so it tries to set up default route after link is up. > I'm running -current as of few days ago. The problem is that when ppp is *not* in -auto mode, it doesn't bother configuring the interface until it's actually agreed an IP number with the peer. The ``add'' line is actioned immediately, and fails. So, your config is fine for -auto mode, but it's better to have the ``add'' in ppp.linkup for any other mode. Things still work though because you're using ``HISADDR'' as this makes it a sticky route, and your eventual interface configuration causes a re-application of all sticky routes. > -- > > Vallo Kallaste > vallo@matti.ee -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 16: 2: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 722DE37BD54 for ; Sat, 12 Aug 2000 16:02:06 -0700 (PDT) (envelope-from gshapiro@gshapiro.net) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.0/8.11.0) id e7CN23I91509; Sat, 12 Aug 2000 16:02:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14741.55147.202130.156007@horsey.gshapiro.net> Date: Sat, 12 Aug 2000 16:02:03 -0700 (PDT) From: Gregory Neil Shapiro To: "Scot W. Hetzel" Cc: Subject: Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current In-Reply-To: <001201c004b0$cfe63660$8dfee0d1@westbend.net> References: <14741.53848.763058.787717@horsey.gshapiro.net> <001201c004b0$cfe63660$8dfee0d1@westbend.net> X-Mailer: VM 6.75 under 21.2 (beta35) "Nike" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hetzels> Sendmail 8.11 has the ablity to due secure authentication with hetzels> mail clients when compiled with Cyrus-SASL. hetzels> Will the Cyrus-SASL library be imported to provide this hetzels> capability? Or at least a make.conf variable. My first step in the process was to get sendmail up-to-date. Once it is MFC'ed to STABLE, I'll look at enhancements. After September 21, I want to turn on STARTTLS support. I'm not sure about importing SASL -- I might be convinced to put in Makefile support if it happens to already been installed via ports. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 16:22:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id 3344C37B9F6; Sat, 12 Aug 2000 16:22:07 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id SAA59473; Sat, 12 Aug 2000 18:22:06 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <002f01c004b4$2120dc80$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Gregory Neil Shapiro" Cc: References: <14741.53848.763058.787717@horsey.gshapiro.net><001201c004b0$cfe63660$8dfee0d1@westbend.net> <14741.55147.202130.156007@horsey.gshapiro.net> Subject: Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current Date: Sat, 12 Aug 2000 18:22:05 -0500 Organization: West Bend Internet X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Gregory Neil Shapiro" > hetzels> Sendmail 8.11 has the ablity to due secure authentication with > hetzels> mail clients when compiled with Cyrus-SASL. > > hetzels> Will the Cyrus-SASL library be imported to provide this > hetzels> capability? Or at least a make.conf variable. > > My first step in the process was to get sendmail up-to-date. Once it is > MFC'ed to STABLE, I'll look at enhancements. After September 21, I want to > turn on STARTTLS support. I'm not sure about importing SASL -- I might be > convinced to put in Makefile support if it happens to already been > installed via ports. > Makefile support for SASL would be fine. Thanks for bringing in 8.11. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 20:11:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id C7CB937BDE9; Sat, 12 Aug 2000 20:11:08 -0700 (PDT) (envelope-from gary@eyelab.psy.msu.edu) Received: from piper (dyn1-tnt13-180.detroit.mi.ameritech.net [199.179.188.180]) by eyelab.psy.msu.edu (8.9.3/8.9.3) with ESMTP id XAA44825; Sat, 12 Aug 2000 23:11:07 -0400 (EDT) (envelope-from gary@eyelab.psy.msu.edu) Message-Id: <4.2.2.20000812230656.0209b170@eyelab.msu.edu> X-Sender: gary@eyelab.msu.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 12 Aug 2000 23:12:06 -0400 To: Gregory Neil Shapiro From: Gary Schrock Subject: Re: HEADS UP: sendmail updated from 8.9.3 to 8.11.0 in -current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <14741.55147.202130.156007@horsey.gshapiro.net> References: <001201c004b0$cfe63660$8dfee0d1@westbend.net> <14741.53848.763058.787717@horsey.gshapiro.net> <001201c004b0$cfe63660$8dfee0d1@westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:02 PM 8/12/2000 -0700, you wrote: >hetzels> Sendmail 8.11 has the ablity to due secure authentication with >hetzels> mail clients when compiled with Cyrus-SASL. > >hetzels> Will the Cyrus-SASL library be imported to provide this >hetzels> capability? Or at least a make.conf variable. > >My first step in the process was to get sendmail up-to-date. Once it is >MFC'ed to STABLE, I'll look at enhancements. After September 21, I want to >turn on STARTTLS support. I'm not sure about importing SASL -- I might be >convinced to put in Makefile support if it happens to already been >installed via ports. I'll admit that I'm something of a clueless idiot when it comes to something like STARTTLS, but looking at the stuff on sendmails page about it, I don't really see a listing of clients that it can work with. One advantage of the SASL stuff is that a fair number of clients seem to support the thing, including several for windows (yeah, I know, the evil term, but some of us actually have people that use windows clients to do their mail). Now, maybe I just don't know what magic STARTTLS offers me, and I'd convert if I knew better. Gary Schrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 21: 2:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 5895937B551 for ; Sat, 12 Aug 2000 21:02:03 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20631 invoked from network); 13 Aug 2000 04:01:58 -0000 Received: from acs-24-154-25-30.zoominternet.net (24.154.25.30) by scully.zoominternet.net with SMTP; 13 Aug 2000 04:01:58 -0000 Date: Sun, 13 Aug 2000 00:01:57 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-25-30.zoominternet.net To: current@freebsd.org Subject: Problems with ATAPI CD driver Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1085953163-966139317=:270" Sender: owner-freebsd-current@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-1085953163-966139317=:270 Content-Type: TEXT/PLAIN; charset=US-ASCII I've got a BTC 24x ATAPI CDROM driver, and I can't mount it. Attached is my dmesg.out. Typing mount /cdrom causes the mount command to hang, and it never did this before. Also, I'm getting these strange syslog messages. (See attached file messages.out.) I tried disabling DMA for ATAPI devices in my kernel config file to no avail. - Donn --0-1085953163-966139317=:270 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.out" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1DVVJSRU5UICMyOiBTYXQgQXVnIDEyIDIz OjQ5OjUzIEVEVCAyMDAwDQogICAgZG1taWxsZXJAYWNzLTI0LTE1NC0yNS0z MC56b29taW50ZXJuZXQubmV0Oi91c3Ivc3JjL3N5cy9jb21waWxlL0NVU1RP TQ0KQ2FsaWJyYXRpbmcgY2xvY2socykgLi4uIFRTQyBjbG9jazogMTY2NDQ1 NzQzIEh6LCBpODI1NCBjbG9jazogMTE5MzE2NCBIeg0KQ0xLX1VTRV9JODI1 NF9DQUxJQlJBVElPTiBub3Qgc3BlY2lmaWVkIC0gdXNpbmcgZGVmYXVsdCBm cmVxdWVuY3kNClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkz MTgyIEh6DQpDTEtfVVNFX1RTQ19DQUxJQlJBVElPTiBub3Qgc3BlY2lmaWVk IC0gdXNpbmcgb2xkIGNhbGlicmF0aW9uIG1ldGhvZA0KVGltZWNvdW50ZXIg IlRTQyIgIGZyZXF1ZW5jeSAxNjY0NDk3NTYgSHoNCkNQVTogUGVudGl1bS9Q NTVDICgxNjYuNDUtTUh6IDU4Ni1jbGFzcyBDUFUpDQogIE9yaWdpbiA9ICJH ZW51aW5lSW50ZWwiICBJZCA9IDB4NTQzICBTdGVwcGluZyA9IDMNCiAgRmVh dHVyZXM9MHg4MDAxYmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixNQ0UsQ1g4 LE1NWD4NCnJlYWwgbWVtb3J5ICA9IDYyOTE0NTYwICg2MTQ0MEsgYnl0ZXMp DQpQaHlzaWNhbCBtZW1vcnkgY2h1bmsocyk6DQoweDAwMDAxMDAwIC0gMHgw MDA5ZmZmZiwgNjUxMjY0IGJ5dGVzICgxNTkgcGFnZXMpDQoweDAwMzk2MDAw IC0gMHgwM2JmN2ZmZiwgNTkxMjE2NjQgYnl0ZXMgKDE0NDM0IHBhZ2VzKQ0K YXZhaWwgbWVtb3J5ID0gNTc3NDk1MDQgKDU2Mzk2SyBieXRlcykNCmJpb3Mz MjogRm91bmQgQklPUzMyIFNlcnZpY2UgRGlyZWN0b3J5IGhlYWRlciBhdCAw eGMwMGY5YTAwDQpiaW9zMzI6IEVudHJ5ID0gMHhmMDRiMCAoYzAwZjA0YjAp ICBSZXYgPSAwICBMZW4gPSAxDQpwY2liaW9zOiBQQ0kgQklPUyBlbnRyeSBh dCAweGYwMDAwKzB4NGUwDQpwbnBiaW9zOiBGb3VuZCBQblAgQklPUyBkYXRh IGF0IDB4YzAwZmQwMjANCnBucGJpb3M6IEVudHJ5ID0gZjAwMDA6ZDA1MCAg UmV2ID0gMS4wDQpwbnBiaW9zOiBPRU0gSUQgY2QwNDENCk90aGVyIEJJT1Mg c2lnbmF0dXJlcyBmb3VuZDoNCkFDUEk6IDAwMDAwMDAwDQpQcmVsb2FkZWQg ZWxmIGtlcm5lbCAia2VybmVsIiBhdCAweGMwMzdkMDAwLg0KUHJlbG9hZGVk IHVzZXJjb25maWdfc2NyaXB0ICIvYm9vdC9rZXJuZWwuY29uZiIgYXQgMHhj MDM3ZDBhOC4NCkludGVsIFBlbnRpdW0gZGV0ZWN0ZWQsIGluc3RhbGxpbmcg d29ya2Fyb3VuZCBmb3IgRjAwRiBidWcNCm51bGxkZXY6IDxudWxsIGRldmlj ZSwgemVybyBkZXZpY2U+DQpyYW5kb206IDxlbnRyb3B5IHNvdXJjZT4NCm1l bTogPG1lbW9yeSAmIEkvTz4NCkNyZWF0aW5nIERJU0sgbWQwDQptZDA6IE1h bGxvYyBkaXNrDQpucHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9uIG1vdGhlcmJv YXJkDQpucHgwOiBJTlQgMTYgaW50ZXJmYWNlDQppNTg2X2J6ZXJvKCkgYmFu ZHdpZHRoID0gNDY4NTU5NjQgYnl0ZXMvc2VjDQpiemVybygpIGJhbmR3aWR0 aCA9IDI0NTM1NjYyIGJ5dGVzL3NlYw0KcGNpYjA6IDxIb3N0IHRvIFBDSSBi cmlkZ2U+IG9uIG1vdGhlcmJvYXJkDQpmb3VuZC0+CXZlbmRvcj0weDEwMzks IGRldj0weDU1OTcsIHJldmlkPTB4MDINCgljbGFzcz0wNi0wMC0wMCwgaGRy dHlwZT0weDAwLCBtZmRldj0wDQoJc3Vib3JkaW5hdGVidXM9MCAJc2Vjb25k YXJ5YnVzPTANCmZvdW5kLT4JdmVuZG9yPTB4MTAzOSwgZGV2PTB4MDAwOCwg cmV2aWQ9MHgwMQ0KCWNsYXNzPTA2LTAxLTAwLCBoZHJ0eXBlPTB4MDAsIG1m ZGV2PTENCglzdWJvcmRpbmF0ZWJ1cz0wIAlzZWNvbmRhcnlidXM9MA0KZm91 bmQtPgl2ZW5kb3I9MHgxMDM5LCBkZXY9MHg1NTEzLCByZXZpZD0weGQwDQoJ Y2xhc3M9MDEtMDEtOGEsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQ0KCXN1Ym9y ZGluYXRlYnVzPTAgCXNlY29uZGFyeWJ1cz0wDQoJaW50cGluPWEsIGlycT0x MQ0KCW1hcFsxMF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMGU0MDAs IHNpemUgIDMsIGVuYWJsZWQNCgltYXBbMTRdOiB0eXBlIDQsIHJhbmdlIDMy LCBiYXNlIDAwMDBlMDAwLCBzaXplICAyLCBlbmFibGVkDQoJbWFwWzE4XTog dHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwZDgwMCwgc2l6ZSAgMywgZW5h YmxlZA0KCW1hcFsxY106IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMGQ0 MDAsIHNpemUgIDIsIGVuYWJsZWQNCgltYXBbMjBdOiB0eXBlIDQsIHJhbmdl IDMyLCBiYXNlIDAwMDBkMDAwLCBzaXplICA0LCBlbmFibGVkDQpmb3VuZC0+ CXZlbmRvcj0weDEwZWMsIGRldj0weDgwMjksIHJldmlkPTB4MDANCgljbGFz cz0wMi0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wDQoJc3Vib3JkaW5h dGVidXM9MCAJc2Vjb25kYXJ5YnVzPTANCglpbnRwaW49YSwgaXJxPTEwDQoJ bWFwWzEwXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwYjgwMCwgc2l6 ZSAgNSwgZW5hYmxlZA0KZm91bmQtPgl2ZW5kb3I9MHgxMDM5LCBkZXY9MHgw MjAwLCByZXZpZD0weDY1DQoJY2xhc3M9MDMtMDAtMDAsIGhkcnR5cGU9MHgw MCwgbWZkZXY9MA0KCXN1Ym9yZGluYXRlYnVzPTAgCXNlY29uZGFyeWJ1cz0w DQoJaW50cGluPWEsIGlycT0xMQ0KCW1hcFsxMF06IHR5cGUgMywgcmFuZ2Ug MzIsIGJhc2UgZTc4MDAwMDAsIHNpemUgMjIsIGVuYWJsZWQNCgltYXBbMTRd OiB0eXBlIDEsIHJhbmdlIDMyLCBiYXNlIGU2MDAwMDAwLCBzaXplIDE2LCBl bmFibGVkDQoJbWFwWzE4XTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAw YjQwMCwgc2l6ZSAgNywgZW5hYmxlZA0KcGNpMDogPFBDSSBidXM+IG9uIHBj aWIwDQpwY2kwOiA8SG9zdCB0byBQQ0kgYnJpZGdlICh2ZW5kb3I9MTAzOSBk ZXZpY2U9NTU5Nyk+ICh2ZW5kb3I9MHgxMDM5LCBkZXY9MHg1NTk3KSBhdCAw LjANCmlzYWIwOiA8U2lTIDg1YzUwMyBQQ0ktSVNBIGJyaWRnZT4gYXQgZGV2 aWNlIDEuMCBvbiBwY2kwDQppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjANCmF0 YXBjaTA6IDxTaVMgNTU5MSBBVEEzMyBjb250cm9sbGVyPiBwb3J0IDB4ZDAw MC0weGQwMGYsMHhkNDAwLTB4ZDQwMywweGQ4MDAtMHhkODA3LDB4ZTAwMC0w eGUwMDMsMHhlNDAwLTB4ZTQwNyBpcnEgMTEgYXQgZGV2aWNlIDEuMSBvbiBw Y2kwDQphdGEwOiBpb2Jhc2U9MHgwMWYwIGFsdGlvYmFzZT0weDAzZjYgYm1h ZGRyPTB4ZDAwMA0KYXRhMDogbWFzaz0wMyBzdGF0dXMwPTUwIHN0YXR1czE9 NTANCmF0YTA6IG1hc2s9MDMgc3RhdHVzMD01MCBzdGF0dXMxPTUwDQphdGEw OiBkZXZpY2VzID0gMHgzDQphdGEwOiBhdCAweDFmMCBpcnEgMTQgb24gYXRh cGNpMA0KYXRhMTogaW9iYXNlPTB4MDE3MCBhbHRpb2Jhc2U9MHgwMzc2IGJt YWRkcj0weGQwMDgNCmF0YTE6IG1hc2s9MDMgc3RhdHVzMD01MCBzdGF0dXMx PTUxDQphdGExOiBtYXNrPTAzIHN0YXR1czA9MTAgc3RhdHVzMT0wMA0KYXRh MTogZGV2aWNlcyA9IDB4NA0KYXRhMTogYXQgMHgxNzAgaXJxIDE1IG9uIGF0 YXBjaTANCmVkMDogPE5FMjAwMCBQQ0kgRXRoZXJuZXQgKFJlYWxUZWsgODAy OSk+IHBvcnQgMHhiODAwLTB4YjgxZiBpcnEgMTAgYXQgZGV2aWNlIDEwLjAg b24gcGNpMA0KYnBmOiBlZDAgYXR0YWNoZWQNCmVkMDogYWRkcmVzcyAwMDpj MDpkZjplZDowYjoxNywgdHlwZSBORTIwMDAgKDE2IGJpdCkgDQpwY2kwOiA8 U2lTIDU1OTcvOTggU1ZHQSBjb250cm9sbGVyPiAodmVuZG9yPTB4MTAzOSwg ZGV2PTB4MDIwMCkgYXQgMTkuMCBpcnEgMTENClRyeWluZyBSZWFkX1BvcnQg YXQgMjAzDQpFU1MwMDAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg4MDAtMHhmZmYs IHNpemU9MHg4LCBhbGlnbj0weDgNCkVTUzE4Njg6IHN0YXJ0IGRlcGVuZGFu dA0KRVNTMTg2ODogYWRkaW5nIGRtYSBtYXNrIDB4Mg0KRVNTMTg2ODogYWRk aW5nIGRtYSBtYXNrIDB4OQ0KRVNTMTg2ODogYWRkaW5nIGlycSBtYXNrIDB4 MjANCkVTUzE4Njg6IGFkZGluZyBmaXhlZCBpbyByYW5nZSAweDIyMC0weDIy Ziwgc2l6ZT0weDEwLCBhbGlnbj0weDENCkVTUzE4Njg6IGFkZGluZyBmaXhl ZCBpbyByYW5nZSAweDM4OC0weDM4Yiwgc2l6ZT0weDQsIGFsaWduPTB4MQ0K RVNTMTg2ODogYWRkaW5nIGZpeGVkIGlvIHJhbmdlIDB4MzMwLTB4MzMxLCBz aXplPTB4MiwgYWxpZ249MHgxDQpFU1MxODY4OiBzdGFydCBkZXBlbmRhbnQN CkVTUzE4Njg6IGFkZGluZyBkbWEgbWFzayAweDINCkVTUzE4Njg6IGFkZGlu ZyBkbWEgbWFzayAweDkNCkVTUzE4Njg6IGFkZGluZyBpcnEgbWFzayAweDZh MA0KRVNTMTg2ODogYWRkaW5nIGlvIHJhbmdlIDB4MjIwLTB4MjRmLCBzaXpl PTB4MTAsIGFsaWduPTB4MjANCkVTUzE4Njg6IGFkZGluZyBmaXhlZCBpbyBy YW5nZSAweDM4OC0weDM4Yiwgc2l6ZT0weDQsIGFsaWduPTB4MQ0KRVNTMTg2 ODogYWRkaW5nIGlvIHJhbmdlIDB4MzAwLTB4MzMxLCBzaXplPTB4MiwgYWxp Z249MHgzMA0KRVNTMTg2ODogc3RhcnQgZGVwZW5kYW50DQpFU1MxODY4OiBh ZGRpbmcgZG1hIG1hc2sgMHhiDQpFU1MxODY4OiBhZGRpbmcgZG1hIG1hc2sg MHhiDQpFU1MxODY4OiBhZGRpbmcgaXJxIG1hc2sgMHgxZWEwDQpFU1MxODY4 OiBhZGRpbmcgaW8gcmFuZ2UgMHgyMjAtMHgyOGYsIHNpemU9MHgxMCwgYWxp Z249MHgyMA0KRVNTMTg2ODogYWRkaW5nIGZpeGVkIGlvIHJhbmdlIDB4Mzg4 LTB4MzhiLCBzaXplPTB4NCwgYWxpZ249MHgxDQpFU1MxODY4OiBhZGRpbmcg aW8gcmFuZ2UgMHgzMDAtMHgzMzEsIHNpemU9MHgyLCBhbGlnbj0weDMwDQpF U1MxODY4OiBzdGFydCBkZXBlbmRhbnQNCkVTUzE4Njg6IGFkZGluZyBkbWEg bWFzayAweGINCkVTUzE4Njg6IGFkZGluZyBkbWEgbWFzayAweGINCkVTUzE4 Njg6IGFkZGluZyBpcnEgbWFzayAweDFlYTANCkVTUzE4Njg6IGFkZGluZyBp byByYW5nZSAweDIyMC0weDI4Ziwgc2l6ZT0weDEwLCBhbGlnbj0weDIwDQpF U1MxODY4OiBhZGRpbmcgZml4ZWQgaW8gcmFuZ2UgMHgzODgtMHgzOGIsIHNp emU9MHg0LCBhbGlnbj0weDENCkVTUzE4Njg6IGFkZGluZyBpbyByYW5nZSAw eDgwMC0weGZmZiwgc2l6ZT0weDIsIGFsaWduPTB4Mg0KRVNTMTg2ODogc3Rh cnQgZGVwZW5kYW50DQpFU1MxODY4OiBhZGRpbmcgZG1hIG1hc2sgMHhiDQpF U1MxODY4OiBhZGRpbmcgZG1hIG1hc2sgMHhiDQpFU1MxODY4OiBhZGRpbmcg aXJxIG1hc2sgMHgxZWEwDQpFU1MxODY4OiBhZGRpbmcgaW8gcmFuZ2UgMHgy MjAtMHgyOGYsIHNpemU9MHgxMCwgYWxpZ249MHgyMA0KRVNTMTg2ODogYWRk aW5nIGlvIHJhbmdlIDB4ODAwLTB4ZmZmLCBzaXplPTB4NCwgYWxpZ249MHg0 DQpFU1MxODY4OiBhZGRpbmcgaW8gcmFuZ2UgMHg4MDAtMHhmZmYsIHNpemU9 MHgyLCBhbGlnbj0weDINCkVTUzE4Njg6IGVuZCBkZXBlbmRhbnQNCkVTUzAw MDE6IHN0YXJ0IGRlcGVuZGFudA0KRVNTMDAwMTogYWRkaW5nIGZpeGVkIGlv IHJhbmdlIDB4MjAxLTB4MjAxLCBzaXplPTB4MSwgYWxpZ249MHgxDQpFU1Mw MDAxOiBzdGFydCBkZXBlbmRhbnQNCkVTUzAwMDE6IGFkZGluZyBpbyByYW5n ZSAweDIwMC0weDIwZiwgc2l6ZT0weDEsIGFsaWduPTB4MQ0KRVNTMDAwMTog ZW5kIGRlcGVuZGFudA0KcG5wYmlvczogMTQgZGV2aWNlcywgbGFyZ2VzdCAx MTAgYnl0ZXMNClBOUDA0MDE6IGFkZGluZyBkbWEgbWFzayAweDgNClBOUDA0 MDE6IGFkZGluZyBpcnEgbWFzayAweDgwDQpQTlAwNDAxOiBhZGRpbmcgaW8g cmFuZ2UgMHgzNzgtMHgzN2YsIHNpemU9MHg4LCBhbGlnbj0wDQpQTlAwNDAx OiBhZGRpbmcgaW8gcmFuZ2UgMHg3NzgtMHg3N2YsIHNpemU9MHg4LCBhbGln bj0wDQpQTlAwNDAxOiBlbmQgY29uZmlnDQpwbnBiaW9zOiBoYW5kbGUgMSBk ZXZpY2UgSUQgUE5QMDQwMSAoMDEwNGQwNDEpDQpQTlAwNTAxOiBhZGRpbmcg aXJxIG1hc2sgMHgxMA0KUE5QMDUwMTogYWRkaW5nIGlvIHJhbmdlIDB4M2Y4 LTB4M2ZmLCBzaXplPTB4OCwgYWxpZ249MA0KUE5QMDUwMTogZW5kIGNvbmZp Zw0KcG5wYmlvczogaGFuZGxlIDIgZGV2aWNlIElEIFBOUDA1MDEgKDAxMDVk MDQxKQ0KUE5QMDUwMTogYWRkaW5nIGlycSBtYXNrIDB4OA0KUE5QMDUwMTog YWRkaW5nIGlvIHJhbmdlIDB4MmY4LTB4MmZmLCBzaXplPTB4OCwgYWxpZ249 MA0KUE5QMDUwMTogZW5kIGNvbmZpZw0KcG5wYmlvczogaGFuZGxlIDMgZGV2 aWNlIElEIFBOUDA1MDEgKDAxMDVkMDQxKQ0KUE5QMDcwMDogYWRkaW5nIGly cSBtYXNrIDB4NDANClBOUDA3MDA6IGFkZGluZyBkbWEgbWFzayAweDQNClBO UDA3MDA6IGFkZGluZyBpbyByYW5nZSAweDNmMi0weDNmNSwgc2l6ZT0weDQs IGFsaWduPTANClBOUDA3MDA6IGVuZCBjb25maWcNCnBucGJpb3M6IGhhbmRs ZSA0IGRldmljZSBJRCBQTlAwNzAwICgwMDA3ZDA0MSkNClBOUDBjMDE6IGFk ZGluZyBmaXhlZCBtZW1vcnkzMiByYW5nZSAwLTB4OWZmZmYsIHNpemU9MHhh MDAwMA0KUE5QMGMwMTogYWRkaW5nIGZpeGVkIG1lbW9yeTMyIHJhbmdlIDB4 MTAwMDAwLTB4M2JmZmZmZiwgc2l6ZT0weDNiMDAwMDANClBOUDBjMDE6IGFk ZGluZyBmaXhlZCBtZW1vcnkzMiByYW5nZSAweGU4MDAwLTB4ZmZmZmYsIHNp emU9MHgxODAwMA0KUE5QMGMwMTogYWRkaW5nIGZpeGVkIG1lbW9yeTMyIHJh bmdlIDB4ZmZmZTAwMDAtMHhmZmZmZmZmZiwgc2l6ZT0weDIwMDAwDQpQTlAw YzAxOiBhZGRpbmcgZml4ZWQgbWVtb3J5MzIgcmFuZ2UgMHhmZmVlMDAwMC0w eGZmZWZmZmZmLCBzaXplPTB4MjAwMDANClBOUDBjMDE6IGVuZCBjb25maWcN CnBucGJpb3M6IGhhbmRsZSA2IGRldmljZSBJRCBQTlAwYzAxICgwMTBjZDA0 MSkNClBOUDAwMDA6IGFkZGluZyBpcnEgbWFzayAweDQNClBOUDAwMDA6IGFk ZGluZyBpbyByYW5nZSAweDIwLTB4MjEsIHNpemU9MHgyLCBhbGlnbj0wDQpQ TlAwMDAwOiBhZGRpbmcgaW8gcmFuZ2UgMHhhMC0weGExLCBzaXplPTB4Miwg YWxpZ249MA0KUE5QMDAwMDogYWRkaW5nIGlvIHJhbmdlIDB4NGQwLTB4NGQx LCBzaXplPTB4MiwgYWxpZ249MA0KUE5QMDAwMDogZW5kIGNvbmZpZw0KcG5w YmlvczogaGFuZGxlIDcgZGV2aWNlIElEIFBOUDAwMDAgKDAwMDBkMDQxKQ0K UE5QMDEwMDogYWRkaW5nIGlycSBtYXNrIDB4MQ0KUE5QMDEwMDogYWRkaW5n IGlvIHJhbmdlIDB4NDAtMHg0Mywgc2l6ZT0weDQsIGFsaWduPTANClBOUDAx MDA6IGVuZCBjb25maWcNCnBucGJpb3M6IGhhbmRsZSA4IGRldmljZSBJRCBQ TlAwMTAwICgwMDAxZDA0MSkNClBOUDBiMDA6IGFkZGluZyBpcnEgbWFzayAw eDEwMA0KUE5QMGIwMDogYWRkaW5nIGlvIHJhbmdlIDB4NzAtMHg3MSwgc2l6 ZT0weDIsIGFsaWduPTANClBOUDBiMDA6IGVuZCBjb25maWcNCnBucGJpb3M6 IGhhbmRsZSA5IGRldmljZSBJRCBQTlAwYjAwICgwMDBiZDA0MSkNClBOUDAz MDM6IGFkZGluZyBpcnEgbWFzayAweDINClBOUDAzMDM6IGFkZGluZyBpbyBy YW5nZSAweDYwLTB4NjAsIHNpemU9MHgxLCBhbGlnbj0wDQpQTlAwMzAzOiBh ZGRpbmcgaW8gcmFuZ2UgMHg2NC0weDY0LCBzaXplPTB4MSwgYWxpZ249MA0K UE5QMDMwMzogZW5kIGNvbmZpZw0KcG5wYmlvczogaGFuZGxlIDEwIGRldmlj ZSBJRCBQTlAwMzAzICgwMzAzZDA0MSkNClBOUDBjMDQ6IGFkZGluZyBpcnEg bWFzayAweDIwMDANClBOUDBjMDQ6IGFkZGluZyBpbyByYW5nZSAweGYwLTB4 ZjAsIHNpemU9MHgxLCBhbGlnbj0wDQpQTlAwYzA0OiBlbmQgY29uZmlnDQpw bnBiaW9zOiBoYW5kbGUgMTEgZGV2aWNlIElEIFBOUDBjMDQgKDA0MGNkMDQx KQ0KUE5QMDIwMDogYWRkaW5nIGRtYSBtYXNrIDB4MTANClBOUDAyMDA6IGFk ZGluZyBpbyByYW5nZSAwLTB4Ziwgc2l6ZT0weDEwLCBhbGlnbj0wDQpQTlAw MjAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg4MC0weDkwLCBzaXplPTB4MTEsIGFs aWduPTANClBOUDAyMDA6IGFkZGluZyBpbyByYW5nZSAweDk0LTB4OWYsIHNp emU9MHhjLCBhbGlnbj0wDQpQTlAwMjAwOiBhZGRpbmcgaW8gcmFuZ2UgMHhj MC0weGRlLCBzaXplPTB4MWYsIGFsaWduPTANClBOUDAyMDA6IGVuZCBjb25m aWcNCnBucGJpb3M6IGhhbmRsZSAxMiBkZXZpY2UgSUQgUE5QMDIwMCAoMDAw MmQwNDEpDQpQTlAwODAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg2MS0weDYxLCBz aXplPTB4MSwgYWxpZ249MHgxDQpQTlAwODAwOiBlbmQgY29uZmlnDQpwbnBi aW9zOiBoYW5kbGUgMTMgZGV2aWNlIElEIFBOUDA4MDAgKDAwMDhkMDQxKQ0K UE5QMGEwMzogYWRkaW5nIGlvIHJhbmdlIDB4Y2Y4LTB4Y2ZmLCBzaXplPTB4 OCwgYWxpZ249MA0KUE5QMGEwMzogZW5kIGNvbmZpZw0KcG5wYmlvczogaGFu ZGxlIDE0IGRldmljZSBJRCBQTlAwYTAzICgwMzBhZDA0MSkNClBOUDBjMDI6 IGFkZGluZyBpbyByYW5nZSAweGVjMDAtMHhlYzNmLCBzaXplPTB4NDAsIGFs aWduPTANClBOUDBjMDI6IGVuZCBjb25maWcNCnBucGJpb3M6IGhhbmRsZSAx NSBkZXZpY2UgSUQgUE5QMGMwMiAoMDIwY2QwNDEpDQpzYy06IHNjMCBleGlz dHMsIHVzaW5nIG5leHQgYXZhaWxhYmxlIHVuaXQgbnVtYmVyDQp2Z2EtOiB2 Z2EwIGV4aXN0cywgdXNpbmcgbmV4dCBhdmFpbGFibGUgdW5pdCBudW1iZXIN CmlzYV9wcm9iZV9jaGlsZHJlbjogZGlzYWJsaW5nIFBuUCBkZXZpY2VzDQpp c2FfcHJvYmVfY2hpbGRyZW46IHByb2Jpbmcgbm9uLVBuUCBkZXZpY2VzDQp2 Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlv bWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwDQpmYjA6IHZnYTAsIHZnYSwg dHlwZTpWR0EgKDUpLCBmbGFnczoweDcwMDdmDQpmYjA6IHBvcnQ6MHgzYzAt MHgzZGYsIGNydGM6MHgzZDQsIG1lbToweGEwMDAwIDB4MjAwMDANCmZiMDog aW5pdCBtb2RlOjI0LCBiaW9zIG1vZGU6MywgY3VycmVudCBtb2RlOjI0DQpm YjA6IHdpbmRvdzoweGMwMGI4MDAwIHNpemU6MzJrIGdyYW46MzJrLCBidWY6 MCBzaXplOjMyaw0KVkdBIHBhcmFtZXRlcnMgdXBvbiBwb3dlci11cA0KNTAg MTggMTAgMDAgMDAgMDAgMDMgMDAgMDIgNjcgNWYgNGYgNTAgODIgNTMgOWYg DQpiZiAxZiAwMCA0ZiAwZCAwZSAwMCAwMCAwNyA4MCA5YiA4ZCA4ZiAyOCAx ZiA5NiANCmI5IGEzIGZmIDAwIDAxIDAyIDAzIDA0IDA1IDE0IDA3IDM4IDM5 IDNhIDNiIDNjIA0KM2QgM2UgM2YgMGMgMDAgMGYgMDggMDAgMDAgMDAgMDAg MDAgMTAgMGUgMDAgZmYgDQpWR0EgcGFyYW1ldGVycyBpbiBCSU9TIGZvciBt b2RlIDI0DQo1MCAxOCAxMCAwMCAxMCAwMCAwMyAwMCAwMiA2NyA1ZiA0ZiA1 MCA4MiA1MyA5ZiANCmJmIDFmIDAwIDRmIDBkIDBlIDAwIDAwIDAwIDAwIDli IDhkIDhmIDI4IDFmIDk2IA0KYjkgYTMgZmYgMDAgMDEgMDIgMDMgMDQgMDUg MTQgMDcgMzggMzkgM2EgM2IgM2MgDQozZCAzZSAzZiAwYyAwMCAwZiAwOCAw MCAwMCAwMCAwMCAwMCAxMCAwZSAwMCBmZiANCkVHQS9WR0EgcGFyYW1ldGVy cyB0byBiZSB1c2VkIGZvciBtb2RlIDI0DQo1MCAxOCAxMCAwMCAxMCAwMCAw MyAwMCAwMiA2NyA1ZiA0ZiA1MCA4MiA1MyA5ZiANCmJmIDFmIDAwIDRmIDBk IDBlIDAwIDAwIDAwIDAwIDliIDhkIDhmIDI4IDFmIDk2IA0KYjkgYTMgZmYg MDAgMDEgMDIgMDMgMDQgMDUgMTQgMDcgMzggMzkgM2EgM2IgM2MgDQozZCAz ZSAzZiAwYyAwMCAwZiAwOCAwMCAwMCAwMCAwMCAwMCAxMCAwZSAwMCBmZiAN CmF0a2JkOiB0aGUgY3VycmVudCBrYmQgY29udHJvbGxlciBjb21tYW5kIGJ5 dGUgMDA2Nw0KYXRrYmQ6IGtleWJvYXJkIElEIDB4NDFhYiAoMikNCmtiZGM6 IFJFU0VUX0tCRCByZXR1cm4gY29kZTowMGZhDQprYmRjOiBSRVNFVF9LQkQg c3RhdHVzOjAwYWENCnNjMDogPFN5c3RlbSBjb25zb2xlPiBhdCBmbGFncyAw eDEwMCBvbiBpc2EwDQpzYzA6IFZHQSA8MTYgdmlydHVhbCBjb25zb2xlcywg ZmxhZ3M9MHgzMDA+DQpzYzA6IGZiMCwga2JkMCwgdGVybWluYWwgZW11bGF0 b3I6IHNjIChzeXNjb25zIHRlcm1pbmFsKQ0KYXRrYmRjMDogPEtleWJvYXJk IGNvbnRyb2xsZXIgKGk4MDQyKT4gYXQgcG9ydCAweDYwLDB4NjQgb24gaXNh MA0KYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGZsYWdzIDB4MSBpcnEgMSBvbiBh dGtiZGMwDQprYmQwIGF0IGF0a2JkMA0Ka2JkMDogYXRrYmQwLCBBVCAxMDEv MTAyICgyKSwgY29uZmlnOjB4MSwgZmxhZ3M6MHgzZDAwMDANCnNpbzA6IG5v dCBwcm9iZWQgKGRpc2FibGVkKQ0Kc2lvMTogbm90IHByb2JlZCAoZGlzYWJs ZWQpDQpzaW8yOiBpcnEgbWFwczogMHgyMSAweDM5IDB4MjkgMHgyMQ0Kc2lv MiBhdCBwb3J0IDB4M2U4LTB4M2VmIGlycSA0IG9uIGlzYTANCnNpbzI6IHR5 cGUgMTY1NTBBDQpzaW8zOiBub3QgcHJvYmVkIChkaXNhYmxlZCkNCm1zZTA6 IDxCdXMvSW5Qb3J0IE1vdXNlPiBhdCBwb3J0IDB4MjNjLTB4MjNmIGlycSAz IG9uIGlzYTANCnNiYzAgZmFpbGVkIHRvIHByb2JlIGF0IHBvcnQgMHgyMjAt MHgyMmYgaXJxIDUgZHJxIDEgZmxhZ3MgMHgxNSBvbiBpc2EwDQpzYzE6IG5v IHZpZGVvIGFkYXB0ZXIgaXMgZm91bmQuDQpzYzE6IDxTeXN0ZW0gY29uc29s ZT4gZmFpbGVkIHRvIHByb2JlIG9uIGlzYTANCnZnYTE6IDxHZW5lcmljIElT QSBWR0E+IGZhaWxlZCB0byBwcm9iZSBvbiBpc2EwDQppc2FfcHJvYmVfY2hp bGRyZW46IHByb2JpbmcgUG5QIGRldmljZXMNCnVua25vd246IDxFU1MgRVMx ODY4IFBsdWcgYW5kIFBsYXkgQXVkaW9Ecml2ZT4gZmFpbGVkIHRvIHByb2Jl IGF0IHBvcnQgMHg4MDAtMHg4MDcgb24gaXNhMA0Kc2JjMTogPEVTUyBFUzE4 Njg+IGF0IHBvcnQgMHgyMjAtMHgyMmYsMHgzODgtMHgzOGIsMHgzMzAtMHgz MzEgaXJxIDUgZHJxIDEsMCBvbiBpc2EwDQpwY20wOiA8RVNTIDE4eHggRFNQ PiBvbiBzYmMxDQpwY20wOiBFU1MxODY4IGRldGVjdGVkDQpwY206IHNldG1h cCA3MDAwLCAxMDAwOyAweGM1MjQ5MDAwIC0+IDcwMDANCnBjbTogc2V0bWFw IDgwMDAsIDEwMDA7IDB4YzUyNGEwMDAgLT4gODAwMA0KdW5rbm93bjogPEVT UyBFUzE4NjggUGx1ZyBhbmQgUGxheSBBdWRpb0RyaXZlPiBmYWlsZWQgdG8g cHJvYmUgYXQgcG9ydCAweDIwMSBvbiBpc2EwDQpwcGMwOiB1c2luZyBleHRl bmRlZCBJL08gcG9ydCByYW5nZQ0KcHBjMDogRUNQIFNQUCBFQ1ArRVBQIFNQ UA0KcHBjMDogPEVDUCBwYXJhbGxlbCBwcmludGVyIHBvcnQ+IGF0IHBvcnQg MHgzNzgtMHgzN2YsMHg3NzgtMHg3N2YgaXJxIDcgZHJxIDMgb24gaXNhMA0K cHBjMDogU01DLWxpa2UgY2hpcHNldCAoRUNQL0VQUC9QUzIvTklCQkxFKSBp biBDT01QQVRJQkxFIG1vZGUNCnBwYzA6IEZJRk8gd2l0aCAxNi8xNi8xNiBi eXRlcyB0aHJlc2hvbGQNCnBsaXAwOiA8UExJUCBuZXR3b3JrIGludGVyZmFj ZT4gb24gcHBidXMwDQpicGY6IGxwMCBhdHRhY2hlZA0KbHB0MDogPFByaW50 ZXI+IG9uIHBwYnVzMA0KbHB0MDogSW50ZXJydXB0LWRyaXZlbiBwb3J0DQpw cGkwOiA8UGFyYWxsZWwgSS9PPiBvbiBwcGJ1czANCnVua25vd246IDxQTlAw NTAxPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzDQp1bmtub3duOiA8UE5QMDUw MT4gYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBvbiBpc2EwDQp1bmtub3du OiA8UE5QMDUwMT4gY2FuJ3QgYXNzaWduIHJlc291cmNlcw0KdW5rbm93bjog PFBOUDA1MDE+IGF0IHBvcnQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhMA0K ZmRjMDogPE5FQyA3MjA2NUIgb3IgY2xvbmU+IGF0IHBvcnQgMHgzZjItMHgz ZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gaXNhMA0KdW5rbm93bjogPFBOUDAz MDM+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMNCnVua25vd246IDxQTlAwMzAz PiBhdCBwb3J0IDB4NjAgb24gaXNhMA0KdW5rbm93bjogPFBOUDA4MDA+IGZh aWxlZCB0byBwcm9iZSBhdCBwb3J0IDB4NjEgb24gaXNhMA0KQklPUyBHZW9t ZXRyaWVzOg0KIDA6MDMwZjdmM2YgMC4uNzgzPTc4NCBjeWxpbmRlcnMsIDAu LjEyNz0xMjggaGVhZHMsIDEuLjYzPTYzIHNlY3RvcnMNCiAxOjAyMGUzZjNm IDAuLjUyNj01MjcgY3lsaW5kZXJzLCAwLi42Mz02NCBoZWFkcywgMS4uNjM9 NjMgc2VjdG9ycw0KIDAgYWNjb3VudGVkIGZvcg0KRGV2aWNlIGNvbmZpZ3Vy YXRpb24gZmluaXNoZWQuDQpicGY6IHBwcDAgYXR0YWNoZWQNCm5ldyBtYXNr czogYmlvIDY4YzA0MCwgdHR5IDYzMDBiYSwgbmV0IDY3MDRiYQ0KYnBmOiBm YWl0aDAgYXR0YWNoZWQNCmJwZjogZ2lmMCBhdHRhY2hlZA0KYnBmOiBnaWYx IGF0dGFjaGVkDQpicGY6IGdpZjIgYXR0YWNoZWQNCmJwZjogZ2lmMyBhdHRh Y2hlZA0KYnBmOiBsbzAgYXR0YWNoZWQNCkxpbnV4LUVMRiBleGVjIGhhbmRs ZXIgaW5zdGFsbGVkDQphdGEwLW1hc3Rlcjogc3VjY2VzcyBzZXR0aW5nIHVw IFVETUEyIG1vZGUgb24gU2lTIGNoaXANCmFkMDogPEZVSklUU1UgTVBCMzAz MkFUVS8yMDA5PiBBVEEtMyBkaXNrIGF0IGF0YTAgYXMgbWFzdGVyDQphZDA6 IDMwOTNNQiAoNjMzNTI4MCBzZWN0b3JzKSwgNjcwNCBjeWxzLCAxNSBoZWFk cywgNjMgUy9ULCA1MTIgQi9TDQphZDA6IDE2IHNlY3MvaW50LCAxIGRlcHRo IHF1ZXVlLCBVRE1BMzMNCmFkMDogcGlvbW9kZT00IGRtYW1vZGU9MiB1ZG1h bW9kZT0yIGNibGlkPTANCkNyZWF0aW5nIERJU0sgYWQwDQphdGEwLXNsYXZl OiBzdWNjZXNzIHNldHRpbmcgdXAgV0RNQTIgbW9kZSBvbiBTaVMgY2hpcA0K YWQxOiA8TTE2MTRUQS84RC00NC0yMT4gQVRBLTAgZGlzayBhdCBhdGEwIGFz IHNsYXZlDQphZDE6IDEwNDBNQiAoMjEzMDkxMiBzZWN0b3JzKSwgMjExNCBj eWxzLCAxNiBoZWFkcywgNjMgUy9ULCA1MTIgQi9TDQphZDE6IDEgc2Vjcy9p bnQsIDEgZGVwdGggcXVldWUsIFdETUEyDQphZDE6IHBpb21vZGU9NCBkbWFt b2RlPTIgdWRtYW1vZGU9LTEgY2JsaWQ9MA0KQ3JlYXRpbmcgRElTSyBhZDEN CmF0YTEtbWFzdGVyOiBwaW9tb2RlPTQgZG1hbW9kZT0yIHVkbWFtb2RlPS0x IGRtYWZsYWc9MQ0KYXRhMS1tYXN0ZXI6IHN1Y2Nlc3Mgc2V0dGluZyB1cCBQ SU80IG1vZGUgb24gZ2VuZXJpYyBjaGlwDQphY2QwOiA8QkNELTI0WCAxOTk3 LTA2LTI3L1ZFUiAyLjA+IENEUk9NIGRyaXZlIGF0IGF0YTEgYXMgbWFzdGVy DQphY2QwOiByZWFkIDUxNUtCL3MgKDE3MThLQi9zKSwgMTI4S0IgYnVmZmVy LCBQSU80DQphY2QwOiBSZWFkczogQ0QtREENCmFjZDA6IEF1ZGlvOiBwbGF5 LCAyNTUgdm9sdW1lIGxldmVscw0KYWNkMDogTWVjaGFuaXNtOiBlamVjdGFi bGUgdHJheQ0KYWNkMDogTWVkaXVtOiBDRC1ST00gMTIwbW0gZGF0YSBkaXNj IGxvYWRlZCwgdW5sb2NrZWQNCk1vdW50aW5nIHJvb3QgZnJvbSB1ZnM6L2Rl di9hZDBzMWENCmFkMHMxOiB0eXBlIDB4YTUsIHN0YXJ0IDYzLCBlbmQgPSAy NjYxMTEsIHNpemUgMjY2MDQ5IDogT0sNCmFkMHMyOiB0eXBlIDB4YTUsIHN0 YXJ0IDI2NjExMiwgZW5kID0gNTMyMjIzLCBzaXplIDI2NjExMiA6IE9LDQph ZDBzMzogdHlwZSAweGE1LCBzdGFydCA1MzIyMjQsIGVuZCA9IDYzMzAyMzks IHNpemUgNTc5ODAxNiA6IE9LDQpXQVJOSU5HOiAvIHdhcyBub3QgcHJvcGVy bHkgZGlzbW91bnRlZA0Kc3RhcnRfaW5pdDogdHJ5aW5nIC9zYmluL2luaXQN CmFkMXMxOiB0eXBlIDB4YTUsIHN0YXJ0IDYzLCBlbmQgPSAyMTI4ODk1LCBz aXplIDIxMjg4MzMgOiBPSw0KYWQxczE6IHR5cGUgMHhhNSwgc3RhcnQgNjMs IGVuZCA9IDIxMjg4OTUsIHNpemUgMjEyODgzMyA6IE9LDQphcnA6IDAwOjAw OmNhOjBkOjQ1OjJjIGlzIHVzaW5nIG15IElQIGFkZHJlc3MgMC4wLjAuMCEN CmFycDogMDA6MDA6Y2E6MGY6MjA6MDIgaXMgdXNpbmcgbXkgSVAgYWRkcmVz cyAwLjAuMC4wIQ0KYXJwOiAwMDowMDpjYTowZjoyMDowMiBpcyB1c2luZyBt eSBJUCBhZGRyZXNzIDAuMC4wLjAhDQphcnA6IDAwOjAwOmNhOjBkOjQ1OjJj IGlzIHVzaW5nIG15IElQIGFkZHJlc3MgMC4wLjAuMCENCmFycDogMDA6MDA6 Y2E6MDY6MjE6MTggaXMgdXNpbmcgbXkgSVAgYWRkcmVzcyAwLjAuMC4wIQ0K YXJwOiAwMDowMDpjYTowNjoyMToxOCBpcyB1c2luZyBteSBJUCBhZGRyZXNz IDAuMC4wLjAhDQphcnA6IDAwOjAwOmNhOjBkOjQ1OjJjIGlzIHVzaW5nIG15 IElQIGFkZHJlc3MgMC4wLjAuMCENCmFycDogMDA6MDA6Y2E6MGY6MjA6MDIg aXMgdXNpbmcgbXkgSVAgYWRkcmVzcyAwLjAuMC4wIQ0KYXJwOiAwMDowMDpj YTowNjoyMToxOCBpcyB1c2luZyBteSBJUCBhZGRyZXNzIDAuMC4wLjAhDQph cnA6IDAwOjAwOmNhOjBkOjQ1OjJjIGlzIHVzaW5nIG15IElQIGFkZHJlc3Mg MC4wLjAuMCENCmFycDogMDA6MDA6Y2E6MDY6MjE6MTggaXMgdXNpbmcgbXkg SVAgYWRkcmVzcyAwLjAuMC4wIQ0KYXJwOiAwMDowMDpjYTowZjoyMDowMiBp cyB1c2luZyBteSBJUCBhZGRyZXNzIDAuMC4wLjAhDQpzcGxhc2g6IGltYWdl IGRlY29kZXIgZm91bmQ6IGdyZWVuX3NhdmVyDQphY2QwOiBSRUFEX0NEIGNv bW1hbmQgdGltZW91dCAtIHJlc2V0dGluZw0KYXRhMTogcmVzZXR0aW5nIGRl dmljZXMgLi4gYXRhMTogbWFzaz0wMSBzdGF0dXMwPTEwIHN0YXR1czE9MDAN CmF0YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgZm9yIGNvbW1hbmQ9ZWYg cz05MCBlPTYwDQphdGExLW1hc3RlcjogZmFpbGVkIHNldHRpbmcgdXAgUElP NCBtb2RlIG9uIGdlbmVyaWMgY2hpcA0KYXRhMS1tYXN0ZXI6IHVzaW5nIFBJ TyBtb2RlIHNldCBieSBCSU9TDQpkb25lDQphdGExLW1hc3RlcjogdGltZW91 dCB3YWl0aW5nIHRvIGdpdmUgY29tbWFuZD1hMCBzPTkwIGU9NjANCmFjZDA6 IGZhaWx1cmUgdG8gc2VuZCBBVEFQSSBwYWNrZXQgY29tbWFuZA0KYWNkMDog ZmFpbHVyZSB0byBleGVjdXRlIEFUQVBJIHBhY2tldCBjb21tYW5kDQphY2Qw OiBSRUFEX0NEIGNvbW1hbmQgdGltZW91dCAtIHJlc2V0dGluZw0KYXRhMTog cmVzZXR0aW5nIGRldmljZXMgLi4gYXRhMTogbWFzaz0wMSBzdGF0dXMwPTEw IHN0YXR1czE9MDANCmF0YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgZm9y IGNvbW1hbmQ9ZWYgcz05MCBlPTYwDQphdGExLW1hc3RlcjogZmFpbGVkIHNl dHRpbmcgdXAgUElPNCBtb2RlIG9uIGdlbmVyaWMgY2hpcA0KYXRhMS1tYXN0 ZXI6IHVzaW5nIFBJTyBtb2RlIHNldCBieSBCSU9TDQpkb25lDQphdGExLW1h c3RlcjogdGltZW91dCB3YWl0aW5nIHRvIGdpdmUgY29tbWFuZD1hMCBzPTkw IGU9NjANCmFjZDA6IGZhaWx1cmUgdG8gc2VuZCBBVEFQSSBwYWNrZXQgY29t bWFuZA0KYWNkMDogZmFpbHVyZSB0byBleGVjdXRlIEFUQVBJIHBhY2tldCBj b21tYW5kDQphY2QwOiBSRUFEX0NEIGNvbW1hbmQgdGltZW91dCAtIHJlc2V0 dGluZw0KYXRhMTogcmVzZXR0aW5nIGRldmljZXMgLi4gYXRhMTogbWFzaz0w MSBzdGF0dXMwPTEwIHN0YXR1czE9MDANCmF0YTEtbWFzdGVyOiB0aW1lb3V0 IHdhaXRpbmcgZm9yIGNvbW1hbmQ9ZWYgcz05MCBlPTYwDQphdGExLW1hc3Rl cjogZmFpbGVkIHNldHRpbmcgdXAgUElPNCBtb2RlIG9uIGdlbmVyaWMgY2hp cA0KYXRhMS1tYXN0ZXI6IHVzaW5nIFBJTyBtb2RlIHNldCBieSBCSU9TDQpk b25lDQphdGExLW1hc3RlcjogdGltZW91dCB3YWl0aW5nIHRvIGdpdmUgY29t bWFuZD1hMCBzPTkwIGU9NjANCmFjZDA6IGZhaWx1cmUgdG8gc2VuZCBBVEFQ SSBwYWNrZXQgY29tbWFuZA0KYWNkMDogZmFpbHVyZSB0byBleGVjdXRlIEFU QVBJIHBhY2tldCBjb21tYW5kDQphY2QwOiBSRUFEX0NEIGNvbW1hbmQgdGlt ZW91dCAtIHJlc2V0dGluZw0KYXRhMTogcmVzZXR0aW5nIGRldmljZXMgLi4g YXRhMTogbWFzaz0wMSBzdGF0dXMwPTEwIHN0YXR1czE9MDANCmF0YTEtbWFz dGVyOiB0aW1lb3V0IHdhaXRpbmcgZm9yIGNvbW1hbmQ9ZWYgcz05MCBlPTYw DQphdGExLW1hc3RlcjogZmFpbGVkIHNldHRpbmcgdXAgUElPNCBtb2RlIG9u IGdlbmVyaWMgY2hpcA0KYXRhMS1tYXN0ZXI6IHVzaW5nIFBJTyBtb2RlIHNl dCBieSBCSU9TDQpkb25lDQo= --0-1085953163-966139317=:270 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="messages.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="messages.out" QXVnIDEyIDIzOjU0OjUxICAva2VybmVsOiBhcnA6IDAwOjAwOmNhOjA2OjIx OjE4IGlzIHVzaW5nIG15IElQIGFkZHJlc3MgMC4wLjAuMCENCkF1ZyAxMiAy Mzo1NDo1MSAgL2tlcm5lbDogYXJwOiAwMDowMDpjYTowZDo0NToyYyBpcyB1 c2luZyBteSBJUCBhZGRyZXNzIDAuMC4wLjAhDQpBdWcgMTIgMjM6NTQ6NTEg IC9rZXJuZWw6IGFycDogMDA6MDA6Y2E6MDY6MjE6MTggaXMgdXNpbmcgbXkg SVAgYWRkcmVzcyAwLjAuMC4wIQ0KQXVnIDEyIDIzOjU0OjUxICAva2VybmVs OiBhcnA6IDAwOjAwOmNhOjBmOjIwOjAyIGlzIHVzaW5nIG15IElQIGFkZHJl c3MgMC4wLjAuMCENCkF1ZyAxMiAyMzo1NDo1NSAgL2tlcm5lbDogc3BsYXNo OiBpbWFnZSBkZWNvZGVyIGZvdW5kOiBncmVlbl9zYXZlcg0KQXVnIDEyIDIz OjU1OjE3ICBzdTogZG1taWxsZXIgdG8gcm9vdCBvbiAvZGV2L3R0eXYxDQpB dWcgMTIgMjM6NTY6MDIgIC9rZXJuZWw6IGFjZDA6IFJFQURfQ0QgY29tbWFu ZCB0aW1lb3V0IC0gcmVzZXR0aW5nDQpBdWcgMTIgMjM6NTY6MDIgIC9rZXJu ZWw6IGF0YTE6IHJlc2V0dGluZyBkZXZpY2VzIC4uIGF0YTE6IG1hc2s9MDEg c3RhdHVzMD0xMCBzdGF0dXMxPTAwDQpBdWcgMTIgMjM6NTY6MDIgIC9rZXJu ZWw6IGF0YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgZm9yIGNvbW1hbmQ9 ZWYgcz05MCBlPTYwDQpBdWcgMTIgMjM6NTY6MDIgIC9rZXJuZWw6IGF0YTEt bWFzdGVyOiBmYWlsZWQgc2V0dGluZyB1cCBQSU80IG1vZGUgb24gZ2VuZXJp YyBjaGlwDQpBdWcgMTIgMjM6NTY6MDIgIC9rZXJuZWw6IGF0YTEtbWFzdGVy OiB1c2luZyBQSU8gbW9kZSBzZXQgYnkgQklPUw0KQXVnIDEyIDIzOjU2OjAy ICAva2VybmVsOiBkb25lDQpBdWcgMTIgMjM6NTY6MDIgIC9rZXJuZWw6IGF0 YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgdG8gZ2l2ZSBjb21tYW5kPWEw IHM9OTAgZT02MA0KQXVnIDEyIDIzOjU2OjAyICAva2VybmVsOiBhY2QwOiBm YWlsdXJlIHRvIHNlbmQgQVRBUEkgcGFja2V0IGNvbW1hbmQNCkF1ZyAxMiAy Mzo1NjowMiAgL2tlcm5lbDogYWNkMDogZmFpbHVyZSB0byBleGVjdXRlIEFU QVBJIHBhY2tldCBjb21tYW5kDQpBdWcgMTIgMjM6NTY6MzcgIC9rZXJuZWw6 IGFjZDA6IFJFQURfQ0QgY29tbWFuZCB0aW1lb3V0IC0gcmVzZXR0aW5nDQpB dWcgMTIgMjM6NTY6MzcgIC9rZXJuZWw6IGF0YTE6IHJlc2V0dGluZyBkZXZp Y2VzIC4uIGF0YTE6IG1hc2s9MDEgc3RhdHVzMD0xMCBzdGF0dXMxPTAwDQpB dWcgMTIgMjM6NTY6MzcgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiB0aW1lb3V0 IHdhaXRpbmcgZm9yIGNvbW1hbmQ9ZWYgcz05MCBlPTYwDQpBdWcgMTIgMjM6 NTY6MzcgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiBmYWlsZWQgc2V0dGluZyB1 cCBQSU80IG1vZGUgb24gZ2VuZXJpYyBjaGlwDQpBdWcgMTIgMjM6NTY6Mzcg IC9rZXJuZWw6IGF0YTEtbWFzdGVyOiB1c2luZyBQSU8gbW9kZSBzZXQgYnkg QklPUw0KQXVnIDEyIDIzOjU2OjM3ICAva2VybmVsOiBkb25lDQpBdWcgMTIg MjM6NTY6MzcgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRp bmcgdG8gZ2l2ZSBjb21tYW5kPWEwIHM9OTAgZT02MA0KQXVnIDEyIDIzOjU2 OjM3ICAva2VybmVsOiBhY2QwOiBmYWlsdXJlIHRvIHNlbmQgQVRBUEkgcGFj a2V0IGNvbW1hbmQNCkF1ZyAxMiAyMzo1NjozNyAgL2tlcm5lbDogYWNkMDog ZmFpbHVyZSB0byBleGVjdXRlIEFUQVBJIHBhY2tldCBjb21tYW5kDQpBdWcg MTIgMjM6NTc6MTIgIC9rZXJuZWw6IGFjZDA6IFJFQURfQ0QgY29tbWFuZCB0 aW1lb3V0IC0gcmVzZXR0aW5nDQpBdWcgMTIgMjM6NTc6MTIgIC9rZXJuZWw6 IGF0YTE6IHJlc2V0dGluZyBkZXZpY2VzIC4uIGF0YTE6IG1hc2s9MDEgc3Rh dHVzMD0xMCBzdGF0dXMxPTAwDQpBdWcgMTIgMjM6NTc6MTIgIC9rZXJuZWw6 IGF0YTEtbWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgZm9yIGNvbW1hbmQ9ZWYg cz05MCBlPTYwDQpBdWcgMTIgMjM6NTc6MTIgIC9rZXJuZWw6IGF0YTEtbWFz dGVyOiBmYWlsZWQgc2V0dGluZyB1cCBQSU80IG1vZGUgb24gZ2VuZXJpYyBj aGlwDQpBdWcgMTIgMjM6NTc6MTIgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiB1 c2luZyBQSU8gbW9kZSBzZXQgYnkgQklPUw0KQXVnIDEyIDIzOjU3OjEyICAv a2VybmVsOiBkb25lDQpBdWcgMTIgMjM6NTc6MTIgIC9rZXJuZWw6IGF0YTEt bWFzdGVyOiB0aW1lb3V0IHdhaXRpbmcgdG8gZ2l2ZSBjb21tYW5kPWEwIHM9 OTAgZT02MA0KQXVnIDEyIDIzOjU3OjEyICAva2VybmVsOiBhY2QwOiBmYWls dXJlIHRvIHNlbmQgQVRBUEkgcGFja2V0IGNvbW1hbmQNCkF1ZyAxMiAyMzo1 NzoxMiAgL2tlcm5lbDogYWNkMDogZmFpbHVyZSB0byBleGVjdXRlIEFUQVBJ IHBhY2tldCBjb21tYW5kDQpBdWcgMTIgMjM6NTc6NDIgIC9rZXJuZWw6IGFj ZDA6IFJFQURfQ0QgY29tbWFuZCB0aW1lb3V0IC0gcmVzZXR0aW5nDQpBdWcg MTIgMjM6NTc6NDIgIC9rZXJuZWw6IGF0YTE6IHJlc2V0dGluZyBkZXZpY2Vz IC4uIGF0YTE6IG1hc2s9MDEgc3RhdHVzMD0xMCBzdGF0dXMxPTAwDQpBdWcg MTIgMjM6NTc6NDIgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiB0aW1lb3V0IHdh aXRpbmcgZm9yIGNvbW1hbmQ9ZWYgcz05MCBlPTYwDQpBdWcgMTIgMjM6NTc6 NDIgIC9rZXJuZWw6IGF0YTEtbWFzdGVyOiBmYWlsZWQgc2V0dGluZyB1cCBQ SU80IG1vZGUgb24gZ2VuZXJpYyBjaGlwDQpBdWcgMTIgMjM6NTc6NDIgIC9r ZXJuZWw6IGF0YTEtbWFzdGVyOiB1c2luZyBQSU8gbW9kZSBzZXQgYnkgQklP Uw0KQXVnIDEyIDIzOjU3OjQyICAva2VybmVsOiBkb25lDQpBdWcgMTMgMDA6 MDA6MDAgYWNzLTI0LTE1NC0yNS0zMCBuZXdzeXNsb2dbMjgwXTogbG9nZmls ZSB0dXJuZWQgb3Zlcg0K --0-1085953163-966139317=:270-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 22: 8:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from RedDust.BlueSky.net.au (reddust.bluesky.net.au [203.31.37.15]) by hub.freebsd.org (Postfix) with ESMTP id EC14D37BF2B for ; Sat, 12 Aug 2000 22:08:16 -0700 (PDT) (envelope-from receiver@RedDust.BlueSky.net.au) Received: from localhost (receiver@localhost) by RedDust.BlueSky.net.au (8.9.3/8.9.3) with ESMTP id PAA77403 for ; Sun, 13 Aug 2000 15:09:02 +1000 (EST) (envelope-from receiver@RedDust.BlueSky.net.au) Date: Sun, 13 Aug 2000 15:09:02 +1000 (EST) From: Idea Receiver To: freebsd-current@FreeBSD.ORG Subject: fail to compile kernel... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i have try to upgrade one of my 4.1 release to -current. however, when i try to build the kernel, it failed as following message. please help! thanks in advance.... ===> oldcard cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pccard.c cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: `card_get_memory_offset_desc' undeclared here (not in a function) /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: initializer element is not constant /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: (near initialization for `pcic_methods[16].desc') *** Error code 1 Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard. *** Error code 1 Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules. *** Error code 1 Stop in /usr/obj/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/WHITESUN-LWY-00. *** Error code 1 Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src. *** Error code 1 Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 22:18:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11]) by hub.freebsd.org (Postfix) with ESMTP id E72B837BE13; Sat, 12 Aug 2000 22:18:33 -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 PAA07250; Sun, 13 Aug 2000 15:18:32 +1000 (EST) From: Darren Reed Message-Id: <200008130518.PAA07250@cairo.anu.edu.au> Subject: ipfilter 3.4.9 imported To: current@freebsd.org Date: Sun, 13 Aug 2000 15:18:32 +1000 (Australia/NSW) Cc: security@freebsd.org 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forwarded message: > From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 13 15:15 EST 2000 > From: owner-freebsd-hackers@FreeBSD.ORG > To: avalon@coombs.anu.edu.au > Subject: Excessive cross-posting: 3 lists. > Message-Id: <20000813051533.1141637BFA6@hub.freebsd.org> > Date: Sat, 12 Aug 2000 22:15:33 -0700 (PDT) > Content-Type: text > Content-Length: 1542 > > do not send mail to more than two lists! > you sent mail to: > hackers@freebsd.org > current@freebsd.org > security@freebsd.org > > > > From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 12 22:15:31 2000 > Return-Path: > 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 3B58D37BE13; Sat, 12 Aug 2000 22:15:26 -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 PAA06842; > Sun, 13 Aug 2000 15:15:22 +1000 (EST) > From: Darren Reed > Message-Id: <200008130515.PAA06842@cairo.anu.edu.au> > Subject: ipfilter 3.4.9 imported > To: hackers@freebsd.org, current@freebsd.org > Date: Sun, 13 Aug 2000 15:15:22 +1000 (Australia/NSW) > Cc: security@freebsd.org > X-Mailer: ELM [version 2.5 PL1] > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > Sender: avalon@cairo.anu.edu.au > > > I have just imported IP Filter 3.4.9 into -current. My attempts to compile > a kernel on freefall/builder failed due to kern_sig.c/machdep.c so I don't > know if all is well there (i.e. don't blame me for not making use of > available resources - I tried to use them but they failed and nobody > has responded to an email about this)...it built cleanly in the IP Filter > directly. If there are no problems, *maybe* next weekend (if not later) > I'll look at pulling it up into -stable. > > Darren > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 22:44:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BFC5C37BE13 for ; Sat, 12 Aug 2000 22:44:12 -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 XAA17064; Sat, 12 Aug 2000 23:44:09 -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 XAA06549; Sat, 12 Aug 2000 23:43:34 -0600 (MDT) Message-Id: <200008130543.XAA06549@harmony.village.org> To: Idea Receiver Subject: Re: fail to compile kernel... Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 13 Aug 2000 15:09:02 +1000." References: Date: Sat, 12 Aug 2000 23:43:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Idea Receiver writes: : i have try to upgrade one of my 4.1 release to -current. : however, when i try to build the kernel, it failed as following : message. Upgrade your sources and try again. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 22:51: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-111.telepath.com [216.14.0.111]) by hub.freebsd.org (Postfix) with SMTP id B24C537B5CB for ; Sat, 12 Aug 2000 22:50:33 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 7548 invoked by uid 100); 13 Aug 2000 05:49:54 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14742.14082.837564.871879@guru.mired.org> Date: Sun, 13 Aug 2000 00:49:54 -0500 (CDT) To: Idea Receiver Cc: freebsd-current@FreeBSD.ORG Subject: fail to compile kernel... In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Idea Receiver writes: > i have try to upgrade one of my 4.1 release to -current. > however, when i try to build the kernel, it failed as following > message. The nasty downside of the the module system is that people who don't adequately test module code before checking it in will screw up kernel builds for kernels that don't need that code. Since you probably don't need the oldcard module. Just comment it out of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want to comment out pccard as well. ===> oldcard > cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/../include -mpreferred-stack-boundary=2 -c > /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pccard.c > cc -O -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/../include -mpreferred-stack-boundary=2 -c > /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c > /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: > `card_get_memory_offset_desc' undeclared here (not in a function) > /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: > initializer element is not constant > /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard/../../pccard/pcic.c:1020: > (near initialization for `pcic_methods[16].desc') > *** Error code 1 > > Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules/oldcard. > *** Error code 1 > > Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/mnt/ad4s1e/FreeBSD-CURRENT/src/sys/WHITESUN-LWY-00. > *** Error code 1 > > Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src. > *** Error code 1 > > Stop in /mnt/ad4s1e/FreeBSD-CURRENT/src. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 22:54:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 57E2537B5EE for ; Sat, 12 Aug 2000 22:54:11 -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 XAA17102; Sat, 12 Aug 2000 23:54:09 -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 XAA06673; Sat, 12 Aug 2000 23:53:34 -0600 (MDT) Message-Id: <200008130553.XAA06673@harmony.village.org> To: Mike Meyer Subject: Re: fail to compile kernel... Cc: Idea Receiver , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 13 Aug 2000 00:49:54 CDT." <14742.14082.837564.871879@guru.mired.org> References: <14742.14082.837564.871879@guru.mired.org> Date: Sat, 12 Aug 2000 23:53:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14742.14082.837564.871879@guru.mired.org> Mike Meyer writes: : The nasty downside of the the module system is that people who don't : adequately test module code before checking it in will screw up kernel : builds for kernels that don't need that code. But I did test it. But I had an uncommitted file on my machine... : Since you probably don't need the oldcard module. Just comment it out : of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want : to comment out pccard as well. Or you can just update your sources. There was a 8 hour window where this was broken... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 12 23:17:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-146.telepath.com [216.14.0.146]) by hub.freebsd.org (Postfix) with SMTP id AF6E937B6A8 for ; Sat, 12 Aug 2000 23:16:45 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 29793 invoked by uid 100); 13 Aug 2000 06:16:27 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14742.15675.412839.269577@guru.mired.org> Date: Sun, 13 Aug 2000 01:16:27 -0500 (CDT) To: freebsd-current@FreeBSD.ORG Cc: Mike Meyer , Idea Receiver , Warner Losh Subject: Build breakage (was: fail to compile kernel...) In-Reply-To: <200008130553.XAA06673@harmony.village.org> References: <14742.14082.837564.871879@guru.mired.org> <200008130553.XAA06673@harmony.village.org> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <14742.14082.837564.871879@guru.mired.org> Mike Meyer writes: > : The nasty downside of the the module system is that people who don't > : adequately test module code before checking it in will screw up kernel > : builds for kernels that don't need that code. > But I did test it. But I had an uncommitted file on my machine... Won't the 'cvs diff' command tell you about such things? If not, that's yet another argument for ditching cvs in favor of something without so many flaws (like Perforce). > : Since you probably don't need the oldcard module. Just comment it out > : of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want > : to comment out pccard as well. > Or you can just update your sources. There was a 8 hour window where > this was broken... Well, it was still broken as of about 30 minutes before he asked the question. I'd look at it for trivial fixes, then just quit trying to build it because I wasn't going to need it. I didn't mean to finger you particularly. It's just a bit upsetting to realize that I can't remember the last time I managed to do an update to -current without some kind of breakage. I realize that -current isn't guaranteed to build, but that's a bit ridiculous. I mean - I was pleasantly surprised that I could build the world first time out. To find the kernel breaking for a module that I have no absolutely no use for on this machine was a bit upsetting. I'm beginning to wonder if I shouldn't use -stable as a buffer, and just let the committers deals with things not being up to -current. Or maybe check to see if the other *BSD's aren't a bit more demanding of committers.