From owner-freebsd-hackers Mon Oct 2 5:15:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 07FAB37B502 for ; Mon, 2 Oct 2000 05:15:21 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA87283; Mon, 2 Oct 2000 14:15:15 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Marc Tardif Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions References: From: Dag-Erling Smorgrav Date: 02 Oct 2000 14:15:14 +0200 In-Reply-To: Marc Tardif's message of "Fri, 29 Sep 2000 16:39:59 -0400 (EDT)" Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc Tardif writes: > How can I find the source to specific functions in /usr/src/sys? DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 5:18:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EE2EE37B66E for ; Mon, 2 Oct 2000 05:18:31 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA87304; Mon, 2 Oct 2000 14:18:28 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Nat Lanza Cc: Arindum Mukerji , Marc Tardif , freebsd-hackers@FreeBSD.ORG Subject: Re: finding source to functions References: <20000930143820.A18501@earth.execpc.com> From: Dag-Erling Smorgrav Date: 02 Oct 2000 14:18:27 +0200 In-Reply-To: Nat Lanza's message of "30 Sep 2000 21:40:03 -0400" Message-ID: Lines: 15 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nat Lanza writes: > I tend to feed my tree to LXR, which has a nice function search, along > with a wrapper for glimpse and some reasonable source browsing. I have > my own hacked version, but the original code can be found at > http://lxr.linux.no. It was written to index the Linux kernel, but > works pretty well for the BSD kernel as well. If anyone wants, I could > clean up what I have and produce a patch. Arne and Per Kristian already have the FreeBSD-CURRENT kernel source up on lxr.linux.no. Per Kristian is actually a closet BSD user - it seems my rabid FreeBSD propaganda has paid off :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 7:34:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id DECDF37B503 for ; Mon, 2 Oct 2000 07:34:46 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-73-43.netcologne.de [213.168.73.43]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id QAA14897 for ; Mon, 2 Oct 2000 16:34:44 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e92EYbl00913 for ; Mon, 2 Oct 2000 16:34:37 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Mon, 2 Oct 2000 16:34:37 +0200 (CEST) From: Paul Herman To: hackers@FreeBSD.ORG Subject: Blowfish passwords Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've come up with a small patchset to libcrypt (ported from OpenBSD) which adds the blowfish password digest in addition to des and md5. Features include: * Compatibility with OpenBSD (for those of us using NIS) * switchable behavior in /etc/login.conf (passwd_format=bf) * ability to do multiple rounds on the fly, i.e. 2^x iterations 1; Mon, 2 Oct 2000 07:56:24 -0700 (PDT) Received: from aurum (aurum.springer.cx [10.0.0.52]) by minerva.springer.cx (8.9.3/8.9.3) with SMTP id QAA21956 for ; Mon, 2 Oct 2000 16:03:50 -0400 Message-ID: <000f01c02c89$089ca840$3400000a@springer.cx> From: "Rink Springer" To: Subject: Need some help developing my ethernet driver. Date: Mon, 2 Oct 2000 17:54:22 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am currently working on a driver for the D-Link DE620 Parallel Ethernet card driver. I used the if_el.c code as a base, for it appears to be a relatively easy driver (my driver is called dl0 BTW, for D-Link. Anyknow know if this conflicts somewhere?). Anyhow, the problem is: I've gotten FreeBSD to recognize a 'device dl0 at isa? port 0x378 irq 7' line in the kernel. It happily compiles my source file and links the kernel. But, for some reason, the new kernel never probes for the driver! Can anyone tell me what I might have missed? In order to add the driver, I've added i386/isa/if_dl.c optional dl to /sys/conf/files.i386 in order to get the kernel to use my code... but why won't the thing probe for it? I've added debugging messages like: printf ("dl: Probing\n"); and such, but I don't see them, and the kernel doesn't say 'dl0 at blah blah' or 'dl0 not detected at blah blah'. What am I doing wrong? *please* help me! Thanks! --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 8:17:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 060DE37B502 for ; Mon, 2 Oct 2000 08:17:25 -0700 (PDT) Received: from libr.scitec.kobe-u.ac.jp (cs22133.ppp.infoweb.ne.jp [202.219.4.49]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id AAA76434; Tue, 3 Oct 2000 00:15:31 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id AAA01660; Tue, 3 Oct 2000 00:08:25 +0900 (JST) From: takawata@shidahara1.planet.sci.kobe-u.ac.jp Message-Id: <200010021508.AAA01660@libr.scitec.kobe-u.ac.jp> To: "Rink Springer" Cc: hackers@freebsd.org Subject: Re: Need some help developing my ethernet driver. In-reply-to: Your message of "Mon, 02 Oct 2000 17:54:22 +0200." <000f01c02c89$089ca840$3400000a@springer.cx> Date: Tue, 03 Oct 2000 00:08:24 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000f01c02c89$089ca840$3400000a@springer.cx>, "Rink Springer" $B$5$s$$(B $B$o$/(B: > >But, for some reason, the new kernel never probes for the driver! Can anyone >tell me what I might have missed? In order to add the driver, I've added > >i386/isa/if_dl.c optional dl > >to /sys/conf/files.i386 in order to get the kernel to use my code... but why >won't the thing probe for it? I've added debugging messages like: > >printf ("dl: Probing\n"); > >and such, but I don't see them, and the kernel doesn't say 'dl0 at blah >blah' or 'dl0 not detected at blah blah'. > Are you make sure your configuration have end with \n? If you edit files.i386 with emacs,and you add it at last, it is often dropped. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 8:23:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7613037B502 for ; Mon, 2 Oct 2000 08:23:21 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e92FNII02276; Mon, 2 Oct 2000 09:23:18 -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 JAA11279; Mon, 2 Oct 2000 09:23:18 -0600 (MDT) Message-Id: <200010021523.JAA11279@harmony.village.org> To: "Rink Springer" Subject: Re: Need some help developing my ethernet driver. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Oct 2000 17:54:22 +0200." <000f01c02c89$089ca840$3400000a@springer.cx> References: <000f01c02c89$089ca840$3400000a@springer.cx> Date: Mon, 02 Oct 2000 09:23:17 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000f01c02c89$089ca840$3400000a@springer.cx> "Rink Springer" writes: : Hi, : : I am currently working on a driver for the D-Link DE620 Parallel Ethernet : card driver. I used the if_el.c code as a base, for it appears to be a : relatively easy driver (my driver is called dl0 BTW, for D-Link. Anyknow : know if this conflicts somewhere?). I don't think there's a dl driver currently. : Anyhow, the problem is: I've gotten FreeBSD to recognize a 'device dl0 at : isa? port 0x378 irq 7' line in the kernel. It happily compiles my source : file and links the kernel. : But, for some reason, the new kernel never probes for the driver! Can anyone : tell me what I might have missed? In order to add the driver, I've added Likely because all parallel port access should go throught the ppbus driver. That's likely the reason that you aren't seeing the probe. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 9: 3:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B69D837B503 for ; Mon, 2 Oct 2000 09:03:10 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id LAA00499; Mon, 2 Oct 2000 11:57:48 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001002115302.02042ab0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 02 Oct 2000 12:05:45 -0400 To: Adam From: Dennis Subject: Re: if_de driver woes Cc: hackers@freebsd.org In-Reply-To: References: <200009301301.NAA00573@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:01 AM 10/01/2000 -0400, you wrote: >On Sat, 30 Sep 2000, Dennis wrote: > > > > >The saga continues. the de driver in 4.1 now doesnt properly detect the > >media of original SMC BNC cards. Upgrading an old system proved quite an > >adventure. > > > >db > >You seem to have forgotten to attach dmesg, pciconf -l, the card model >name, description, and symptoms... maybe your mailer ate them? Oct 2 10:32:36 et-gw /kernel: de0: port 0xf880-0xf8ff mem 0xffbefe80-0xffbefeff irq 9 at device 17.0 on pci0 Oct 2 10:32:36 et-gw /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 Oct 2 10:32:36 et-gw /kernel: de0: address 00:00:c0:1a:49:d0 I dont know the exact model, but the vendor ID is 1011 and the device IDs are 0x0014 and 0x0002. The 0x0014 device sets up with 10baseT media (there is only a coax BNC on the card, and the 0x0002 devices comes up with AUI and 10baseT/UTP capabilty, but there is only a coax BNC on the card, so you cant even set it to BNC manually. These worked just fine under 2.2.8. DB >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 9:18:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (d4044.dtk.chello.nl [213.46.4.44]) by hub.freebsd.org (Postfix) with ESMTP id 9F66F37B502 for ; Mon, 2 Oct 2000 09:18:49 -0700 (PDT) Received: from aurum (aurum.springer.cx [10.0.0.52]) by minerva.springer.cx (8.9.3/8.9.3) with SMTP id RAA22192; Mon, 2 Oct 2000 17:25:59 -0400 Message-ID: <001801c02c94$83c6ce00$3400000a@springer.cx> From: "Rink Springer" To: "Warner Losh" Cc: References: <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> Subject: Re: Need some help developing my ethernet driver. Date: Mon, 2 Oct 2000 19:16:29 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Warner Losh" To: "Rink Springer" Cc: Sent: Monday, October 02, 2000 5:23 PM Subject: Re: Need some help developing my ethernet driver. Hi, > In message <000f01c02c89$089ca840$3400000a@springer.cx> "Rink Springer" writes: > : Hi, > : > [snip] > > Likely because all parallel port access should go throught the ppbus > driver. That's likely the reason that you aren't seeing the probe. Well, I've taken out the parallel driver from my kernel (and ppbus as well). So, someone got any ideas? Would it help if I quickly dump my source file online? > > Warner > Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 9:21:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CE2BD37B502 for ; Mon, 2 Oct 2000 09:21:42 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e92GLeI02671; Mon, 2 Oct 2000 10:21:40 -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 KAA11813; Mon, 2 Oct 2000 10:21:40 -0600 (MDT) Message-Id: <200010021621.KAA11813@harmony.village.org> To: "Rink Springer" Subject: Re: Need some help developing my ethernet driver. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Oct 2000 19:16:29 +0200." <001801c02c94$83c6ce00$3400000a@springer.cx> References: <001801c02c94$83c6ce00$3400000a@springer.cx> <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> Date: Mon, 02 Oct 2000 10:21:39 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001801c02c94$83c6ce00$3400000a@springer.cx> "Rink Springer" writes: : Well, I've taken out the parallel driver from my kernel (and ppbus as well). : So, someone got any ideas? Would it help if I quickly dump my source file : online? Yes. It likely would. What version of FreeBSD are you using? Also, you'll find two benefits from using ppbus. First, it makes your life easier when dealing with all those nibbles and such that yuo have to send to the device. Second, it increases the chances that your driver will be included in FreeBSD in the future. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 9:29:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (d4044.dtk.chello.nl [213.46.4.44]) by hub.freebsd.org (Postfix) with ESMTP id BABE737B503 for ; Mon, 2 Oct 2000 09:29:13 -0700 (PDT) Received: from aurum (aurum.springer.cx [10.0.0.52]) by minerva.springer.cx (8.9.3/8.9.3) with SMTP id RAA22281; Mon, 2 Oct 2000 17:36:36 -0400 Message-ID: <001d01c02c95$fc7eede0$3400000a@springer.cx> From: "Rink Springer" To: "Warner Losh" Cc: References: <001801c02c94$83c6ce00$3400000a@springer.cx> <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> <200010021621.KAA11813@harmony.village.org> Subject: Re: Need some help developing my ethernet driver. Date: Mon, 2 Oct 2000 19:27:06 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Okay... the source is at http://www.rink.springer.cx/tmp/if_dl.c. I agree that using ppc is a very good idea, and I'm definatly going to do that once it works (I'm not going to from start because I hope to use this driver for NetBSD too eventually, and FAIK, it doesn't support ppc). Thanks! --Rink ----- Original Message ----- From: "Warner Losh" To: "Rink Springer" Cc: Sent: Monday, October 02, 2000 6:21 PM Subject: Re: Need some help developing my ethernet driver. > In message <001801c02c94$83c6ce00$3400000a@springer.cx> "Rink Springer" writes: > : Well, I've taken out the parallel driver from my kernel (and ppbus as well). > : So, someone got any ideas? Would it help if I quickly dump my source file > : online? > > Yes. It likely would. > > What version of FreeBSD are you using? > > Also, you'll find two benefits from using ppbus. First, it makes your > life easier when dealing with all those nibbles and such that yuo have > to send to the device. Second, it increases the chances that your > driver will be included in FreeBSD in the future. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 9:32:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 804FB37B502 for ; Mon, 2 Oct 2000 09:32:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e92GWAI02753; Mon, 2 Oct 2000 10:32: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 KAA11958; Mon, 2 Oct 2000 10:32:10 -0600 (MDT) Message-Id: <200010021632.KAA11958@harmony.village.org> To: "Rink Springer" Subject: Re: Need some help developing my ethernet driver. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Oct 2000 19:27:06 +0200." <001d01c02c95$fc7eede0$3400000a@springer.cx> References: <001d01c02c95$fc7eede0$3400000a@springer.cx> <001801c02c94$83c6ce00$3400000a@springer.cx> <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> <200010021621.KAA11813@harmony.village.org> Date: Mon, 02 Oct 2000 10:32:10 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <001d01c02c95$fc7eede0$3400000a@springer.cx> "Rink Springer" writes: : Okay... the source is at http://www.rink.springer.cx/tmp/if_dl.c. I agree : that using ppc is a very good idea, and I'm definatly going to do that once : it works (I'm not going to from start because I hope to use this driver for : NetBSD too eventually, and FAIK, it doesn't support ppc). Which version of FreeBSD are you using? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 11: 8:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from minerva.springer.cx (d4044.dtk.chello.nl [213.46.4.44]) by hub.freebsd.org (Postfix) with ESMTP id B0FE237B502 for ; Mon, 2 Oct 2000 11:08:24 -0700 (PDT) Received: from aurum (aurum.springer.cx [10.0.0.52]) by minerva.springer.cx (8.9.3/8.9.3) with SMTP id TAA22608 for ; Mon, 2 Oct 2000 19:15:55 -0400 Message-ID: <001d01c02ca3$dbf60a00$3400000a@springer.cx> From: "Rink Springer" To: References: <001301c02c96$a0c5ad80$3400000a@springer.cx> <001d01c02c95$fc7eede0$3400000a@springer.cx> <001801c02c94$83c6ce00$3400000a@springer.cx> <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> <200010021621.KAA11813@harmony.village.org> <200010021632.KAA11958@harmony.village.org> <200010021641.KAA12076@harmony.village.org> Subject: Re: Need some help developing my ethernet driver. Date: Mon, 2 Oct 2000 21:04:41 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Warner Losh" To: "Rink Springer" Sent: Monday, October 02, 2000 6:41 PM Subject: Re: Need some help developing my ethernet driver. Hi! > : 4.1-RELEASE. > > OK. That's the problem. You need to use newbus rather than the > legacy interface. The el driver still uses the legacy driver > interface. The ed, ep or sn driver might be a better one to start > with... > > Warner > Thanks pal! Now, the thing's at least probing for it (for some reason twice, but I'll figure that out). One final problem here now... how can I determine which I/O address FreeBSD is willing me to probe for the device? I cannot find it in any of the existing drivers... anyone? --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 11:18:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 2ABE337B503 for ; Mon, 2 Oct 2000 11:18:43 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id OAA19855 for ; Mon, 2 Oct 2000 14:18:29 -0400 (EDT) Date: Mon, 2 Oct 2000 14:18:01 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: process scheduling quantum Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Suppose a process is scheduled to run, will it run until its quantum ends unless it calls tsleep() on his own? In other words, is it possible for a process to give up its quantum earlier without having it to do so voluntarily? Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 14:53:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C30DF37B502; Mon, 2 Oct 2000 14:53:32 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92LrSN43780; Mon, 2 Oct 2000 23:53:28 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, hackers@freebsd.org Subject: mtree verification output format From: Poul-Henning Kamp Date: Mon, 02 Oct 2000 23:53:28 +0200 Message-ID: <43778.970523608@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to change the outputformat of mtree(8) to be more systematic and machine-readable. The changes amount to: make "extra" and "missing" attributes in the output rather than prefixes which can be confused with filenames. Don't do the "run-in" of the first attribute with a short filename I attach below a before/after example which show the effect. Any objections ? Poul-Henning Before: ------------ rc: size (13134, 13135) cksum (2005920215, 873112433) ttys: cksum (2486739860, 2798556681) extra: bla malloc.conf: permissions (0755, 0777) missing: ./objformat ------------ After: ------------ rc: size (13134, 13135) cksum (2005920215, 873112433) ttys: cksum (2486739860, 2798556681) bla: extra malloc.conf: permissions (0755, 0777) ./objformat: missing ------------ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 14:57:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 63C9F37B502; Mon, 2 Oct 2000 14:57:30 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA30548; Mon, 2 Oct 2000 17:57:29 -0400 (EDT) (envelope-from wollman) Date: Mon, 2 Oct 2000 17:57:29 -0400 (EDT) From: Garrett Wollman Message-Id: <200010022157.RAA30548@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: mtree verification output format In-Reply-To: <43778.970523608@critter> References: <43778.970523608@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > make "extra" and "missing" attributes in the output > rather than prefixes which can be confused with filenames. > Don't do the "run-in" of the first attribute with a short > filename This looks like a good change, but while you're there: > size (13134, 13135) > cksum (2005920215, 873112433) This is still very obscure; I'd like to see: size (was 1234, should be 5678) cksum (was 42424242, should be 69696969) ...so that it's clear what the meaning of the numbers is. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 14:59:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id F3ABC37B502; Mon, 2 Oct 2000 14:59:24 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e92LxJN43885; Mon, 2 Oct 2000 23:59:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format In-Reply-To: Your message of "Mon, 02 Oct 2000 17:57:29 EDT." <200010022157.RAA30548@khavrinen.lcs.mit.edu> Date: Mon, 02 Oct 2000 23:59:19 +0200 Message-ID: <43883.970523959@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010022157.RAA30548@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >< said: > >> make "extra" and "missing" attributes in the output >> rather than prefixes which can be confused with filenames. > >> Don't do the "run-in" of the first attribute with a short >> filename > >This looks like a good change, but while you're there: > >> size (13134, 13135) >> cksum (2005920215, 873112433) > >This is still very obscure; I'd like to see: > > size (was 1234, should be 5678) > cksum (was 42424242, should be 69696969) > >...so that it's clear what the meaning of the numbers is. In that case I think I would like to loose the ',' also. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 15:28: 0 2000 Delivered-To: freebsd-hackers@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 84D7B37B503 for ; Mon, 2 Oct 2000 15:27:58 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA34893; Mon, 2 Oct 2000 18:28:14 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 2 Oct 2000 18:28:14 -0400 (EDT) From: Adam To: Dennis Cc: hackers@freebsd.org Subject: Re: if_de driver woes In-Reply-To: <5.0.0.25.0.20001002115302.02042ab0@mail.etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Oct 2000, Dennis wrote: >At 02:01 AM 10/01/2000 -0400, you wrote: >>On Sat, 30 Sep 2000, Dennis wrote: >> >> > >> >The saga continues. the de driver in 4.1 now doesnt properly detect the >> >media of original SMC BNC cards. Upgrading an old system proved quite an >> >adventure. >> > >> >db >> >>You seem to have forgotten to attach dmesg, pciconf -l, the card model >>name, description, and symptoms... maybe your mailer ate them? > > >Oct 2 10:32:36 et-gw /kernel: de0: port 0xf880-0xf8ff >mem 0xffbefe80-0xffbefeff irq 9 at device 17.0 on pci0 >Oct 2 10:32:36 et-gw /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 >Oct 2 10:32:36 et-gw /kernel: de0: address 00:00:c0:1a:49:d0 > >I dont know the exact model, but the vendor ID is 1011 and the device IDs >are 0x0014 and 0x0002. The 0x0014 device sets up with 10baseT media (there >is only a coax BNC on the card, and the 0x0002 devices comes up with AUI >and 10baseT/UTP capabilty, but there is only a coax BNC on the card, so you >cant even set it to BNC manually. I'm not sure what and how 0x0014 and 0x0002 are used, but have you tried ifconfig de0 media 10base2/BNC ? Also what does ifconfig de0 report for the supported media types(if any)? My ed card supports tp and bnc but it doesnt report them in ifconfig, not sure what de does. > >These worked just fine under 2.2.8. > >DB > > > > >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 16:41:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 96AEE37B66C for ; Mon, 2 Oct 2000 16:41:22 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id TAA00299; Mon, 2 Oct 2000 19:36:09 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001002194135.03828c80@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 02 Oct 2000 19:44:03 -0400 To: Adam From: Dennis Subject: Re: if_de driver woes Cc: hackers@freebsd.org In-Reply-To: References: <5.0.0.25.0.20001002115302.02042ab0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It might be useful if someone familiar with the driver answered, but there seems little hope of that. Maybe the guy that broke it...which would mean someone who modified it since 2.2.8 came out. You know who you are....., but unfortunately the audit trail in the source is useless since there is none. Dennis At 06:28 PM 10/02/2000 -0400, you wrote: >On Mon, 2 Oct 2000, Dennis wrote: > > >At 02:01 AM 10/01/2000 -0400, you wrote: > >>On Sat, 30 Sep 2000, Dennis wrote: > >> > >> > > >> >The saga continues. the de driver in 4.1 now doesnt properly detect the > >> >media of original SMC BNC cards. Upgrading an old system proved quite an > >> >adventure. > >> > > >> >db > >> > >>You seem to have forgotten to attach dmesg, pciconf -l, the card model > >>name, description, and symptoms... maybe your mailer ate them? > > > > > >Oct 2 10:32:36 et-gw /kernel: de0: port > 0xf880-0xf8ff > >mem 0xffbefe80-0xffbefeff irq 9 at device 17.0 on pci0 > >Oct 2 10:32:36 et-gw /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 > >Oct 2 10:32:36 et-gw /kernel: de0: address 00:00:c0:1a:49:d0 > > > >I dont know the exact model, but the vendor ID is 1011 and the device IDs > >are 0x0014 and 0x0002. The 0x0014 device sets up with 10baseT media (there > >is only a coax BNC on the card, and the 0x0002 devices comes up with AUI > >and 10baseT/UTP capabilty, but there is only a coax BNC on the card, so you > >cant even set it to BNC manually. > >I'm not sure what and how 0x0014 and 0x0002 are used, but have you tried >ifconfig de0 media 10base2/BNC ? > >Also what does ifconfig de0 report for the supported media types(if any)? >My ed card supports tp and bnc but it doesnt report them in ifconfig, not >sure what de does. > > > > > >These worked just fine under 2.2.8. > > > >DB > > > > > > > > > >>To Unsubscribe: send mail to majordomo@FreeBSD.org > >>with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 17:31:53 2000 Delivered-To: freebsd-hackers@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 E35B337B502 for ; Mon, 2 Oct 2000 17:31:50 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id UAA36075; Mon, 2 Oct 2000 20:32:07 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Mon, 2 Oct 2000 20:32:07 -0400 (EDT) From: Adam To: Dennis Cc: hackers@freebsd.org Subject: Re: if_de driver woes In-Reply-To: <5.0.0.25.0.20001002194135.03828c80@mail.etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe if you just answered the question for the benefit of anyone else who might be able to help but not willing to until you act like you appreciate or deserve it. On Mon, 2 Oct 2000, Dennis wrote: >It might be useful if someone familiar with the driver answered, but there >seems little hope of that. > >Maybe the guy that broke it...which would mean someone who modified it >since 2.2.8 came out. > >You know who you are....., but unfortunately the audit trail in the source >is useless since there is none. > >Dennis >At 06:28 PM 10/02/2000 -0400, you wrote: >>On Mon, 2 Oct 2000, Dennis wrote: >> >> >At 02:01 AM 10/01/2000 -0400, you wrote: >> >>On Sat, 30 Sep 2000, Dennis wrote: >> >> >> >> > >> >> >The saga continues. the de driver in 4.1 now doesnt properly detect the >> >> >media of original SMC BNC cards. Upgrading an old system proved quite an >> >> >adventure. >> >> > >> >> >db >> >> >> >>You seem to have forgotten to attach dmesg, pciconf -l, the card model >> >>name, description, and symptoms... maybe your mailer ate them? >> > >> > >> >Oct 2 10:32:36 et-gw /kernel: de0: port >> 0xf880-0xf8ff >> >mem 0xffbefe80-0xffbefeff irq 9 at device 17.0 on pci0 >> >Oct 2 10:32:36 et-gw /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 >> >Oct 2 10:32:36 et-gw /kernel: de0: address 00:00:c0:1a:49:d0 >> > >> >I dont know the exact model, but the vendor ID is 1011 and the device IDs >> >are 0x0014 and 0x0002. The 0x0014 device sets up with 10baseT media (there >> >is only a coax BNC on the card, and the 0x0002 devices comes up with AUI >> >and 10baseT/UTP capabilty, but there is only a coax BNC on the card, so you >> >cant even set it to BNC manually. >> >>I'm not sure what and how 0x0014 and 0x0002 are used, but have you tried >>ifconfig de0 media 10base2/BNC ? >> >>Also what does ifconfig de0 report for the supported media types(if any)? >>My ed card supports tp and bnc but it doesnt report them in ifconfig, not >>sure what de does. >> >> >> > >> >These worked just fine under 2.2.8. >> > >> >DB >> > >> > >> > >> > >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >> >>with "unsubscribe freebsd-hackers" in the body of the message >> > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 17:47:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gba.oz.au (gba.gw.bit.net.au [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 4A8F937B503 for ; Mon, 2 Oct 2000 17:47:05 -0700 (PDT) Received: (qmail 90162 invoked by uid 1001); 3 Oct 2000 10:46:56 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Tue, 03 Oct 2000 10:46:56 +1000 From: Greg Black To: Poul-Henning Kamp Cc: Garrett Wollman , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format References: <43883.970523959@critter> In-reply-to: <43883.970523959@critter> of Mon, 02 Oct 2000 23:59:19 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >This is still very obscure; I'd like to see: > > > > size (was 1234, should be 5678) > > cksum (was 42424242, should be 69696969) > > > >...so that it's clear what the meaning of the numbers is. > > In that case I think I would like to loose the ',' also. While you're at it, why not use single word verbs: size (got 1234 wanted 5678) cksum (got 42424242 wanted 69696969) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 17:55: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 8AA7437B503; Mon, 2 Oct 2000 17:54:57 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id A61D1382; Mon, 2 Oct 2000 20:54:56 -0400 (EDT) Received: (from jon@localhost) by fury.csh.rit.edu (8.9.3+Sun/8.9.1) id UAA23283; Mon, 2 Oct 2000 20:54:28 -0400 (EDT) Date: Mon, 2 Oct 2000 20:54:28 -0400 From: Jon Parise To: Greg Black Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format Message-ID: <20001002205427.A23243@csh.rit.edu> References: <43883.970523959@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gjb-freebsd@gba.oz.au on Tue, Oct 03, 2000 at 10:46:56AM +1000 X-Operating-System: SunOS 5.7 (sun4u) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 03, 2000 at 10:46:56AM +1000, Greg Black wrote: > > > size (was 1234, should be 5678) > > > cksum (was 42424242, should be 69696969) > > > > > >...so that it's clear what the meaning of the numbers is. > > > > In that case I think I would like to loose the ',' also. > > While you're at it, why not use single word verbs: > > size (got 1234 wanted 5678) > cksum (got 42424242 wanted 69696969) Or perhaps: size (got 1234 expected 5678) cksum (got 42424242 expected 69696969) -- Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 17:57:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 2170737B502; Mon, 2 Oct 2000 17:57:12 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e930wfh04015; Mon, 2 Oct 2000 17:58:42 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010030058.e930wfh04015@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Black Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format In-reply-to: Your message of "Tue, 03 Oct 2000 10:46:56 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Oct 2000 17:58:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >This is still very obscure; I'd like to see: > > > > > > size (was 1234, should be 5678) > > > cksum (was 42424242, should be 69696969) > > > > > >...so that it's clear what the meaning of the numbers is. > > > > In that case I think I would like to loose the ',' also. > > While you're at it, why not use single word verbs: > > size (got 1234 wanted 5678) > cksum (got 42424242 wanted 69696969) Try "expected", but yes, this is a better idea. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 17:59:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gba.oz.au (gba.gw.bit.net.au [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id 1C80D37B66E for ; Mon, 2 Oct 2000 17:59:48 -0700 (PDT) Received: (qmail 90542 invoked by uid 1001); 3 Oct 2000 10:59:45 +1000 X-Posted-By: GBA-Post 2.06 15-Sep-2000 X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B C249 1CE1 493B 2B5A CE30 Message-Id: Date: Tue, 03 Oct 2000 10:59:45 +1000 From: Greg Black To: Mike Smith Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: mtree verification output format References: <200010030058.e930wfh04015@mass.osd.bsdi.com> In-reply-to: <200010030058.e930wfh04015@mass.osd.bsdi.com> of Mon, 02 Oct 2000 17:58:41 MST Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >This is still very obscure; I'd like to see: > > > > > > > > size (was 1234, should be 5678) > > > > cksum (was 42424242, should be 69696969) > > > > > > > >...so that it's clear what the meaning of the numbers is. > > > > > > In that case I think I would like to loose the ',' also. > > > > While you're at it, why not use single word verbs: > > > > size (got 1234 wanted 5678) > > cksum (got 42424242 wanted 69696969) > > Try "expected", but yes, this is a better idea. You're right, "expected" is better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 18:33: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 790B137B502 for ; Mon, 2 Oct 2000 18:32:52 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13gGwn-000GUj-00; Tue, 03 Oct 2000 03:32:45 +0200 Date: Tue, 3 Oct 2000 03:32:45 +0200 From: Neil Blakey-Milner To: FreeBSD Hackers Cc: Doug Barton , Sheldon Hearn Subject: Making /etc/defaults/rc.conf a configuration file. Message-ID: <20001003033245.A63319@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Qxx1br4bt0+wmkIi" Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, With these patches, and the new tiny util 'sourceconf', we can make /etc/defaults/rc.conf and /etc/defaults/periodic.conf configuration files again, such that they can be parsed by things other than 'sh'. It also allows you to set 'rc_conf_files' (or, actually, whatever you set filevar to) in lower places than the default file, so that you don't change the default file. This only shows how to replace things using rc.conf - changing scripts to use periodic.conf is as simple as replacing if [ -r /etc/defaults/periodic.conf ] then . /etc/defaults/periodic.conf source_periodic_confs fi with rcfile=/etc/defaults/periodic.conf listvar=periodic_conf_files . /etc/sourceconf Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sc.patch" Index: etc/netstart =================================================================== RCS file: /home/ncvs/src/etc/netstart,v retrieving revision 1.55 diff -u -r1.55 netstart --- etc/netstart 2000/04/27 08:43:47 1.55 +++ etc/netstart 2000/10/03 01:14:04 @@ -9,13 +9,9 @@ # the network by hand, this script will do it for you). # -# If there is a global system configuration file, suck it in. -if [ -f /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -f /etc/rc.conf ]; then - . /etc/rc.conf -fi +# Suck in the configuration variables +# +. /etc/sourceconf if [ -f /etc/rc.network ]; then . /etc/rc.network Index: etc/pccard_ether =================================================================== RCS file: /home/ncvs/src/etc/pccard_ether,v retrieving revision 1.18 diff -u -r1.18 pccard_ether --- etc/pccard_ether 2000/09/07 03:06:06 1.18 +++ etc/pccard_ether 2000/10/03 01:02:26 @@ -9,12 +9,7 @@ # Suck in the configuration variables # -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconf interface=$1 shift Index: etc/rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.230 diff -u -r1.230 rc --- etc/rc 2000/08/21 14:37:52 1.230 +++ etc/rc 2000/10/03 01:13:43 @@ -34,14 +34,9 @@ fi fi -# If there is a global system configuration file, suck it in. +# Suck in the configuration variables # -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconfs # Configure ccd devices. # @@ -564,18 +559,13 @@ echo . # Do traditional (but rather obsolete) rc.local file if it exists. If you -# use this file and want to make it programmatic, source /etc/defaults/rc.conf +# use this file and want to make it programmatic, source /etc/sourceconf # in /etc/rc.local and add your custom variables to /etc/rc.conf, as # shown below. Please do not put local extensions into /etc/rc itself. # Use /etc/rc.local # # ---- rc.local ---- -# if [ -r /etc/defaults/rc.conf ]; then -# . /etc/defaults/rc.conf -# source_rc_confs -# elif [ -r /etc/rc.conf ]; then -# . /etc/rc.conf -# fi +# . /etc/sourceconf # # ... additional startup conditionals ... # ---- rc.local ---- Index: etc/rc.devfs =================================================================== RCS file: /home/ncvs/src/etc/rc.devfs,v retrieving revision 1.8 diff -u -r1.8 rc.devfs --- etc/rc.devfs 2000/04/27 08:43:48 1.8 +++ etc/rc.devfs 2000/10/03 01:14:34 @@ -1,14 +1,9 @@ # # $FreeBSD: src/etc/rc.devfs,v 1.8 2000/04/27 08:43:48 sheldonh Exp $ # -# If there is a global system configuration file, suck it in. +# Suck in the configuration variables # -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconf # Setup DEVFS, ie permissions, links etc. # Index: etc/rc.diskless2 =================================================================== RCS file: /home/ncvs/src/etc/rc.diskless2,v retrieving revision 1.6 diff -u -r1.6 rc.diskless2 --- etc/rc.diskless2 2000/04/27 08:43:48 1.6 +++ etc/rc.diskless2 2000/10/03 01:04:43 @@ -5,12 +5,7 @@ # If there is a global system configuration file, suck it in. # -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconf mount_mfs -s ${varsize:=65536} -T qp120at dummy /var var_dirs="run dev db msgs tmp spool spool/mqueue spool/lpd spool/output \ Index: etc/rc.firewall =================================================================== RCS file: /home/ncvs/src/etc/rc.firewall,v retrieving revision 1.37 diff -u -r1.37 rc.firewall --- etc/rc.firewall 2000/08/30 13:14:32 1.37 +++ etc/rc.firewall 2000/10/03 01:04:57 @@ -3,12 +3,7 @@ # $FreeBSD: src/etc/rc.firewall,v 1.37 2000/08/30 13:14:32 ru Exp $ # Suck in the configuration variables. -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconf ############ # Define the firewall type in /etc/rc.conf. Valid values are: Index: etc/rc.shutdown =================================================================== RCS file: /home/ncvs/src/etc/rc.shutdown,v retrieving revision 1.11 diff -u -r1.11 rc.shutdown --- etc/rc.shutdown 2000/08/18 10:34:11 1.11 +++ etc/rc.shutdown 2000/10/03 01:14:46 @@ -17,14 +17,9 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export HOME PATH -# If there is a global system configuration file, suck it in. +# Suck in the configuration variables # -if [ -r /etc/defaults/rc.conf ]; then - . /etc/defaults/rc.conf - source_rc_confs -elif [ -r /etc/rc.conf ]; then - . /etc/rc.conf -fi +. /etc/sourceconf # Write some entropy so the rebooting /dev/random can reseed # Index: etc/defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.78 diff -u -r1.78 rc.conf --- etc/defaults/rc.conf 2000/09/01 01:08:52 1.78 +++ etc/defaults/rc.conf 2000/10/03 01:23:32 @@ -298,28 +298,3 @@ start_vinum="" # set to YES to start vinum entropy_file="/var/db/entropy" # Set to NO to disable caching entropy through reboots - -############################################################## -### Define source_rc_confs, the mechanism used by /etc/rc.* ## -### scripts to source rc_conf_files overrides safely. ## -############################################################## - -if [ -z "${source_rc_confs_defined}" ]; then - source_rc_confs_defined=yes - source_rc_confs ( ) { - local i sourced_files - for i in ${rc_conf_files}; do - case ${sourced_files} in - *:$i:*) - ;; - *) - sourced_files="${sourced_files}:$i:" - if [ -r $i ]; then - . $i - fi - ;; - esac - done - } -fi - --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=sourceconf #!/bin/sh # # Copyright (c) 2000 Neil Blakey-Milner # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # Original code by Doug Barton # sourceconf_decho ( ) { case "$sourceconf_debug" in '') ;; *) echo $* ;; esac } sourceconf_dosrc ( ) { local ${listvar} for i in $*; do case "${sourceconf_sourced_files}" in *:$i:*) ;; *) sourceconf_sourced_files="${sourceconf_sourced_files}:$i:" sourceconf_decho $i if [ -r $i ]; then . $i eval sourceconf_dosrc \$${listvar} fi ;; esac done } sourceconf_start ( ) { local rcfile local sourceconf_sourced_files local listvar sourceconf_sourced_files= case "$rcfile" in '') rcfile=/etc/defaults/rc.conf ;; esac case "$listvar" in '') listvar=rc_conf_files ;; esac sourceconf_dosrc $rcfile } sourceconf_start unset sourceconf_start unset sourceconf_dosrc unset sourceconf_decho --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 18:37:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 83B8937B502 for ; Mon, 2 Oct 2000 18:37:35 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e931avG11062; Mon, 2 Oct 2000 18:36:57 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010030136.e931avG11062@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: Adam , hackers@FreeBSD.ORG Subject: Re: if_de driver woes In-Reply-To: <5.0.0.25.0.20001002194135.03828c80@mail.etinc.com> Date: Mon, 02 Oct 2000 18:36:57 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > It might be useful if someone familiar with the driver answered, but there > seems little hope of that. Nearly all the older (pre-100Mbit) tulip cards are different to the other older ones. The newer ones based on the 2114[0123] chips had a lot more in common and generally required less tweaks. Getting some random older 10Mbit card to work is somewhat a black art. > Maybe the guy that broke it...which would mean someone who modified it > since 2.2.8 came out. > > You know who you are....., but unfortunately the audit trail in the source > is useless since there is none. Audit trails do not belong in the source. That is what source code management systems are for: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/if_de.c The majority of the changes were as a result of syncing up with the original auther and later on some cleanup. If you can find (specifically) what change broke it, I'd love to hear from you. I'd also like to know if a NetBSD kernel runs with it or not. > Dennis > At 06:28 PM 10/02/2000 -0400, you wrote: > >On Mon, 2 Oct 2000, Dennis wrote: > > > > >At 02:01 AM 10/01/2000 -0400, you wrote: > > >>On Sat, 30 Sep 2000, Dennis wrote: > > >> > > >> > > > >> >The saga continues. the de driver in 4.1 now doesnt properly detect the > > >> >media of original SMC BNC cards. Upgrading an old system proved quite a n > > >> >adventure. > > >> > > > >> >db > > >> > > >>You seem to have forgotten to attach dmesg, pciconf -l, the card model > > >>name, description, and symptoms... maybe your mailer ate them? > > > > > > > > >Oct 2 10:32:36 et-gw /kernel: de0: port > > 0xf880-0xf8ff > > >mem 0xffbefe80-0xffbefeff irq 9 at device 17.0 on pci0 > > >Oct 2 10:32:36 et-gw /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 > > >Oct 2 10:32:36 et-gw /kernel: de0: address 00:00:c0:1a:49:d0 > > > > > >I dont know the exact model, but the vendor ID is 1011 and the device IDs > > >are 0x0014 and 0x0002. The 0x0014 device sets up with 10baseT media (there > > >is only a coax BNC on the card, and the 0x0002 devices comes up with AUI > > >and 10baseT/UTP capabilty, but there is only a coax BNC on the card, so yo u > > >cant even set it to BNC manually. > > > >I'm not sure what and how 0x0014 and 0x0002 are used, but have you tried > >ifconfig de0 media 10base2/BNC ? > > > >Also what does ifconfig de0 report for the supported media types(if any)? > >My ed card supports tp and bnc but it doesnt report them in ifconfig, not > >sure what de does. > > > > > > > > > >These worked just fine under 2.2.8. > > > > > >DB Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 20:10:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from october.pacificlaw.org (bblaw17.northcoast.com [208.25.164.83]) by hub.freebsd.org (Postfix) with ESMTP id B84DE37B503 for ; Mon, 2 Oct 2000 20:10:26 -0700 (PDT) Received: from 208.25.164.82 (localhost.pacificlaw.org [127.0.0.1]) by october.pacificlaw.org (8.9.3/8.9.3) with ESMTP id UAA01352 for ; Mon, 2 Oct 2000 20:11:17 -0700 (PDT) (envelope-from LOONY@208.25.164.82.pacificlaw.org) Message-ID: <39D94E55.6E33BD67@208.25.164.82> Date: Mon, 02 Oct 2000 20:11:17 -0700 From: Loony Bomber X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: XFreeBSD Install - 4.1-RELEASE #:0 Fri Jul 28 14:30:31 GMT 2000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok it's a bad thing to submit to a mailing list I don't subscribe to, but, the FreeBSD Handbook says general comments should be posted here, and I am inspired, dammit. The purpose of this comment is to provide general comments on the installation of FreeBSD - RELEASE 4.1. It took me about one day to get FreeBSD w/ X windows running reliably with a new MB, memory, and CPU's & support for svga, mail, web-browsers, and a smorgasborg of ports. Some components, primarily support for my creative AWE GOLD soundcard and 32x CDROM aren't presently usable. I am still not satisfied I have KDE and Gnome running correctly. I believe I answered the setup and installation questions correctly. It is relevant that this is only the second *nix (FreeBSD) system I've ever done, and, that the only thing I knew about *nix before I started reading the FreeBSD documentation project materials was that a friend I met playing Quake told me to go to FreeBSD.org and that I could download a free operating system that would perform much better as a network router/firewall/gateway/modem device driver (ISDN then, ADSL now) than win nt 4.0 server. Given these qualifications, and the fact that the first router I built on a recycled 286 system (as a lark) really does perform tons better than win nt 4.0 Routing & RAS, I am extemely impressed by the relative ease of using FreeBSD. There's no way I'd recommend win2k server for the role my fBSD plays for the lawfirm/school I admin. Just then for the edification of the people who continue to contribute to the development of this project, it is helpful to describe where a new user such as I found problems: First, the CDROM on the 286 system went in like a charm ... that is, I don't believe I did anything specially related to the CDROM to get it working. That was with version 3.3, which I installed from the CDROM after making the boot floppies and installing them first on the target drive. This time around, with version 4.1, the CDROM didn't get picked up or configured properly automatically during the installation process. The differences are that I installed by booting from the CDROM this time around, and, the system is a dual p3 600 p133 tyan tiger w/ 256 mem. I chose to install xfreebsd with KDE, Gnome, and some ports (I forget which) which use Enlightement or maybe are part of it. This was my first time doing it and I did have problems, which after fussing with the windowmanager, produce not the most pleasing desktop, but, at least something I can get work on. For instance, at first, I didn't know how to get X-Windows running after the installation ended and the system re-booted. Has anyone considered having an option for FreeBSD to prompt people who have installed KDE, Gnome, X-windows support to start the system in X-Windows mode after installation? When I finally figured that startx works better than xwin (or whatever xwin commands I first came across (logically), I was totally confounded by the fact that I now had 4 taskbars on the top and bottom of the screen, two hidden behind others. I'm doing unorthodox things like loading KDE as a non-managed session in windowmanager to get my desktop approximating a single taskbar desktop. In short, the visual installation program didn't provide me with a harmonious desktop. Would it be too hard to get the KDE and Gnome folks together with installation program coders to figure out an improved x-windows installation routine? The sound card didn't go in either. Ok, so ya purposefully wanted to give people incentive to build their own kernels. After all the hard work you put into it, I can see that you might just want to throw up your hands and say, "If ya can't do that, go back to whatever OS ya' came from." Im sorry, what was supposed to be a quick 'helpful' comment is turning into a gripe, which is almost opposite of the reason why I thought I would make my 'contribution.' Please note I said, 'relative ease' above. What I mean by that is unlike windows nt, where you have to go out and buy some book, hire some person, or purchase new software when something MS says works doesn't work, you can at least look up the answers and solve things for yourself, if you have the time and patience. So far I haven't come across anything that I can eventually fix by entering the proper values someplace I never beforehand knew existed. unaloony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 2 23:33:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id E480A37B503 for ; Mon, 2 Oct 2000 23:33:39 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13gLdu-0005eJ-00; Tue, 3 Oct 2000 08:33:35 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e936XXj05468; Tue, 3 Oct 2000 08:33:36 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200010030633.e936XXj05468@grimreaper.grondar.za> To: Paul Herman Cc: hackers@FreeBSD.ORG Subject: Re: Blowfish passwords References: In-Reply-To: ; from Paul Herman "Mon, 02 Oct 2000 16:34:37 +0200." Date: Tue, 03 Oct 2000 08:33:33 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It patches cleanly against -STABLE and -CURRENT, and only touches > libcrypt. Take a look at it, feedback/patches are welcome, and if you > like it, maybe someone can integrate it into -CURRENT. (I don't know > whose dept. this would be -- Mark Murray perhaps? ) > > http://www.frenchfries.net/paul/freebsd/blowfish.passwd.patch.gz Cool! Thank you! :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 0: 1:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 6D1E337B502 for ; Tue, 3 Oct 2000 00:01:36 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001003070136.MWAT26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Tue, 3 Oct 2000 00:01:36 -0700 Content-Length: 1651 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: <00b701c0273b$39f7aaa0$0901a8c0@haym.transactionsite.com> Date: Tue, 03 Oct 2000 00:01:39 -0700 (PDT) From: John Baldwin To: Jan Mikkelsen Subject: Re: atomic operations Cc: FreeBSD Hackers , Cc: FreeBSD Hackers , Kevin Mills Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Sep-00 Jan Mikkelsen wrote: > Kevin Mills wrote: >>I found the atomic_* functions in , but noticed that they >>have no return value. What I need is a function that increments/decrements >>the given value *and* returns the new value in an atomic operation. I >>suppose this is possible, yes? How would one modify the assembly to make >>this work? > > > Atomic decrement, in the Intel style: > > long atomic_decrement(volatile long* address) > { > asm { > mov ecx, [address] > mov eax, -1 > lock xadd [ecx], eax > dec eax > } > /* Return value in EAX */ > } > > An untested conversion into the GNU/AT&T style: > > long atomic_decrement(volatile long* address) > { > asm("movl 8(%ebp),%ecx"); > asm("movl $-1, %eax"); > asm("lock xaddl %eax,(%ecx)"); > asm("decl %eax"); > /* Return value in %eax */ > } Uh, there is no xaddl instruction in the x86 instruction set. There is a fetchadd instruction in ia64, but that doesn't help much here. You can use a loop with the atomic_cmpset_* primitives though to achieve this. e.g.: volatile int value; int save, increment; value = 3; increment = 4; do { save = value; } while (atomic_cmpset_int(&value, save, save + increment) == 0); foo = some_array[save + increment]; You can use this to control access to a circular buffer w/o needing a lock to obtain new entries for example. This will only work with -current though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 0: 1:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 57B8437B502 for ; Tue, 3 Oct 2000 00:01:48 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001003070147.MWBN26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Tue, 3 Oct 2000 00:01:47 -0700 Content-Length: 682 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: Tue, 03 Oct 2000 00:01:51 -0700 (PDT) From: John Baldwin To: Zhiui Zhang Subject: RE: process scheduling quantum Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Oct-00 Zhiui Zhang wrote: > > Suppose a process is scheduled to run, will it run until its quantum ends > unless it calls tsleep() on his own? In other words, is it possible for a > process to give up its quantum earlier without having it to do so > voluntarily? Thanks. If an interrupt occurs and puts a thread on the run queue (which will have higher priority than the currently running proceess) then the current process will be stopped so that the interrupt thread can run. > -Zhihui -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 0: 5:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id C7B0237B503 for ; Tue, 3 Oct 2000 00:05:44 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.11.0/8.10.2) with ESMTP id e9377pS07745 for ; Tue, 3 Oct 2000 00:07:51 -0700 (PDT) Date: Tue, 3 Oct 2000 00:07:51 -0700 (PDT) From: FengYue To: freebsd-hackers@FreeBSD.ORG Subject: 4.1-stable crash. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, could someone take a look at this crash. The box is a 4.1-stable as Sep 6th. Any hints on what could have caused the crash? This box crashs almost every 3-5 days. Thanks! ==========================cut here================================= gdb -k kernel.debug /var/crash/vmcore.0 [GDB messages...] This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2863104 initial pcb at 247960 panicstr: page fault panic messages: --- dmesg: kvm_read: --- #0 0xc0132df8 in boot () (kgdb) where #0 0xc0132df8 in boot () Cannot access memory at address 0xce51d9b8. (kgdb) ====================================end=========================== As you can see, I can't seem to be able to do a backtrace. below is the dmesg output: ----------------------------------cut here=--------------------- FreeBSD 4.1-STABLE #3: Mon Sep 25 14:28:27 PDT 2000 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 651480181 Hz CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 201244672 (196528K bytes) avail memory = 192761856 (188244K bytes) Preloaded elf kernel "kernel" at 0xc02a9000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 10 pci0: at 4.3 irq 10 fxp0: port 0xb800-0xb81f mem 0xe0800000-0xe08f ffff,0xe3000000-0xe3000fff irq 10 at device 16.0 on pci0 fxp0: Ethernet address 00:20:35:67:5b:fc pcib1: on motherboard pci2: on pcib1 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 atkbdc0: at port 0x60,0x64 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled ad0: 9541MB [19386/16/63] at ata0-master using UDMA66 ad1: 6869MB [13957/16/63] at ata0-slave using UDMA33 ad2: 14649MB [29765/16/63] at ata1-master using UDMA66 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 1: 3:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from penfold.transactionsite.com (penfold.transactionsite.com [203.14.245.1]) by hub.freebsd.org (Postfix) with SMTP id 1321237B502 for ; Tue, 3 Oct 2000 01:03:03 -0700 (PDT) Received: (qmail 22679 invoked from network); 3 Oct 2000 08:02:51 -0000 Received: from haym.transactionsite.com (HELO haym) (192.168.1.9) by penfold.transactionsite.com with SMTP; 3 Oct 2000 08:02:51 -0000 Message-ID: <001201c02d0f$790c9140$0901a8c0@haym.transactionsite.com> From: "Jan Mikkelsen" To: "John Baldwin" Cc: "FreeBSD Hackers" , "Kevin Mills" Subject: Re: atomic operations Date: Tue, 3 Oct 2000 18:56:43 +1100 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 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: >Uh, there is no xaddl instruction in the x86 instruction set. It was introduced in the '486. I've been using it for some years now, so I am confident of its existence. A quick test using my example: $ objdump -d jan.o jan.o: file format elf32-i386 Disassembly of section .text: 00000000 : 0: 55 push %ebp 1: 89 e5 mov %esp,%ebp 3: 8b 4d 08 mov 0x8(%ebp),%ecx 6: b8 ff ff ff ff mov $0xffffffff,%eax b: f0 0f c1 01 lock xadd %eax,(%ecx) f: 48 dec %eax 10: c9 leave 11: c3 ret There shouldn't be a need for a loop like the one you describe for a simple atomic increment. I'm pretty new to FreeBSD: what is changing in -current which alters the behaviour of your code? Jan Mikkelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 1:19: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id 56C0837B502 for ; Tue, 3 Oct 2000 01:18:59 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001003081858.NIDU26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Tue, 3 Oct 2000 01:18:58 -0700 Content-Length: 829 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: <001201c02d0f$790c9140$0901a8c0@haym.transactionsite.com> Date: Tue, 03 Oct 2000 01:19:02 -0700 (PDT) From: John Baldwin To: Jan Mikkelsen Subject: Re: atomic operations Cc: Kevin Mills , Cc: Kevin Mills , FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Oct-00 Jan Mikkelsen wrote: > John Baldwin wrote: >>Uh, there is no xaddl instruction in the x86 instruction set. > > It was introduced in the '486. I've been using it for some years now, so I > am confident of its existence. Freaky. Time for a new atomic op perhaps. > There shouldn't be a need for a loop like the one you describe for a simple > atomic increment. The trick is that I want to increment and read at the same time. > I'm pretty new to FreeBSD: what is changing in -current which alters the > behaviour of your code? atomic_cmpset_* don't exist in stable, they are part of SMPng. > Jan Mikkelsen -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 1:22:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7E93137B503; Tue, 3 Oct 2000 01:22:41 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e938Mec19063; Tue, 3 Oct 2000 01:22:40 -0700 (PDT) Date: Tue, 3 Oct 2000 01:22:40 -0700 From: Alfred Perlstein To: John Baldwin Cc: Jan Mikkelsen , FreeBSD Hackers , Kevin Mills Subject: Re: atomic operations Message-ID: <20001003012240.G27736@fw.wintelcom.net> References: <00b701c0273b$39f7aaa0$0901a8c0@haym.transactionsite.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 jhb@FreeBSD.ORG on Tue, Oct 03, 2000 at 12:01:39AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Baldwin [001003 00:01] wrote: > > On 25-Sep-00 Jan Mikkelsen wrote: > > Kevin Mills wrote: > >>I found the atomic_* functions in , but noticed that they > >>have no return value. What I need is a function that increments/decrements > >>the given value *and* returns the new value in an atomic operation. I > >>suppose this is possible, yes? How would one modify the assembly to make > >>this work? > > > > > > Atomic decrement, in the Intel style: > > > > long atomic_decrement(volatile long* address) > > { > > asm { > > mov ecx, [address] > > mov eax, -1 > > lock xadd [ecx], eax > > dec eax > > } > > /* Return value in EAX */ > > } > > > > An untested conversion into the GNU/AT&T style: > > > > long atomic_decrement(volatile long* address) > > { > > asm("movl 8(%ebp),%ecx"); > > asm("movl $-1, %eax"); > > asm("lock xaddl %eax,(%ecx)"); > > asm("decl %eax"); > > /* Return value in %eax */ > > } > > Uh, there is no xaddl instruction in the x86 instruction set. There is > a fetchadd instruction in ia64, but that doesn't help much here. You > can use a loop with the atomic_cmpset_* primitives though to achieve this. > e.g.: > > volatile int value; > int save, increment; > > value = 3; increment = 4; > do { > save = value; > } while (atomic_cmpset_int(&value, save, save + increment) == 0); > foo = some_array[save + increment]; > > You can use this to control access to a circular buffer w/o needing a > lock to obtain new entries for example. This will only work with -current > though. Mike Smith and I discussed atomic types and the problem is that not all arches can do all the ops we want, as a compromise we can use macros to wrap the ops as long as we use constructors and destructors for atomic_t. this could use some testing/comments, my gcc+asm is terrible: Index: atomic.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/atomic.h,v retrieving revision 1.12 diff -u -u -r1.12 atomic.h --- atomic.h 2000/09/06 11:21:14 1.12 +++ atomic.h 2000/10/03 07:05:59 @@ -218,6 +218,31 @@ return ( atomic_cmpset_int((volatile u_int *)dst, (u_int)exp, (u_int)src)); } -#endif + +typedef struct { volatile int a; } atomic_t; + +#define atomic_init(p, v) do { p->a = v; } while(0) +#define atomic_destroy(p) do { ; } while(0) +#define atomic_add(p, v) atomic_add_int(&(p->a), v) +#define atomic_sub(p, v) atomic_subtract_int(&(p->a), v) +#define atomic_or(p, v) atomic_set_int(&(p->a), v) +#define atomic_and(p, v) atomic_clear_int(&(p->a), v) +#define atomic_read(p) ((p)->a) +#define atomic_set(p, v) do { (p)->a = (v); } while(0); +/* XXX: maybe use decl/incl ? */ +#define atomic_dec(p) atomic_sub(&(p->a), 1) +#define atomic_inc(p) atomic_add(&(p->a), 1) + +static __inline int +atomic_dec_and_test(volatile atomic_t *v) +{ + unsigned char c; + + __asm __volatile("lock ; decl %0; sete %1" + : "=m" (v->a), "=qm" (c) + : "m" (v->a)); + return (c != 0); +} +#endif /* !WANT_FUNCTIONS */ #endif /* ! _MACHINE_ATOMIC_H_ */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 1:36:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id BF6E037B66D; Tue, 3 Oct 2000 01:36:15 -0700 (PDT) Received: from stinky.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id KAA09439; Tue, 3 Oct 2000 10:41:03 +0200 (IST) Message-Id: <5.0.0.23.0.20001003100820.00ad9470@192.116.19.220> X-Sender: mustafa@192.116.19.220 X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.23 (Beta) Date: Tue, 03 Oct 2000 10:17:51 +0200 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org From: Mustafa Deeb Subject: Internet Prepaid Card Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I'm working on building a system that will handle Internet Prepaid Cards where the user would connect for a certain amount of time and then disconnect ofcourse this is not implemented in Radius. after some digging, I was able to control it through Session-Timeout Attribute in Radius and some scripts that will decrement the value until it reaches 1, but still this means I'll have to put an entry for each card in the users file along with another entry in master.passwd file, I don't if radiusd can handle that amount of entries, and anyways, if my password file is more than 10k lines, that's not good. the other approach that I'm looking into is through database, radiusd is patched to do auth and acct from database, but not read configuration I wonder if someone did this before, make radiusd read its configuration from a database my aim here is to make radius read the Session-Timeout from a database or use Oracle Radius Adapter, on and oracle database, but I couldn't find Session-Timeout in it too. did somebody did this before? Best Regards Mustafa N. Deeb Palnet Communications Ltd. Technical Director To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 1:57:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from penfold.transactionsite.com (penfold.transactionsite.com [203.14.245.1]) by hub.freebsd.org (Postfix) with SMTP id F2EBB37B503 for ; Tue, 3 Oct 2000 01:57:27 -0700 (PDT) Received: (qmail 22898 invoked from network); 3 Oct 2000 08:57:24 -0000 Received: from haym.transactionsite.com (HELO haym) (192.168.1.9) by penfold.transactionsite.com with SMTP; 3 Oct 2000 08:57:24 -0000 Message-ID: <005801c02d17$17efc0a0$0901a8c0@haym.transactionsite.com> From: "Jan Mikkelsen" To: "John Baldwin" Cc: "Kevin Mills" , "FreeBSD Hackers" Subject: Re: atomic operations Date: Tue, 3 Oct 2000 19:51:16 +1100 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 4.72.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: >On 03-Oct-00 Jan Mikkelsen wrote: >> There shouldn't be a need for a loop like the one you describe for a simple >> atomic increment. > >The trick is that I want to increment and read at the same time. I don't know the exact semantics of atomic_cmpset_int, but it looks like a compare and swap operation which returns zero if the operation failed, some other value on success. Unless I've missed something, the basic operation of your loop can be done (on a '486 or better) without the loop by using the xadd instruction. Of course, if the code needs to run on earlier processors, xadd fails and a loop is necessary. Jan Mikkelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 2: 0:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id EC59E37B503; Tue, 3 Oct 2000 02:00:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e938xuN46870; Tue, 3 Oct 2000 10:59:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jan Mikkelsen" Cc: "John Baldwin" , "Kevin Mills" , "FreeBSD Hackers" Subject: Re: atomic operations In-Reply-To: Your message of "Tue, 03 Oct 2000 19:51:16 +1100." <005801c02d17$17efc0a0$0901a8c0@haym.transactionsite.com> Date: Tue, 03 Oct 2000 10:59:56 +0200 Message-ID: <46868.970563596@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <005801c02d17$17efc0a0$0901a8c0@haym.transactionsite.com>, "Jan Mikk elsen" writes: >John Baldwin wrote: > >>On 03-Oct-00 Jan Mikkelsen wrote: >>> There shouldn't be a need for a loop like the one you describe for a >simple >>> atomic increment. >> >>The trick is that I want to increment and read at the same time. > > >I don't know the exact semantics of atomic_cmpset_int, but it looks like a >compare and swap operation which returns zero if the operation failed, some >other value on success. That is exactly what atomic_cmpset_int is for, look in sys/fs/devfs/devfs_devs.c for some examples -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 3:41:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 4C53F37B502; Tue, 3 Oct 2000 03:41:12 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id GAA10482; Tue, 3 Oct 2000 06:40:50 -0400 (EDT) Date: Tue, 3 Oct 2000 06:40:50 -0400 (EDT) From: Daniel Eischen To: John Baldwin Cc: Zhiui Zhang , freebsd-hackers@FreeBSD.ORG Subject: RE: process scheduling quantum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Oct 2000, John Baldwin wrote: > > On 02-Oct-00 Zhiui Zhang wrote: > > > > Suppose a process is scheduled to run, will it run until its quantum ends > > unless it calls tsleep() on his own? In other words, is it possible for a > > process to give up its quantum earlier without having it to do so > > voluntarily? Thanks. > > If an interrupt occurs and puts a thread on the run queue (which will have > higher priority than the currently running proceess) then the current > process will be stopped so that the interrupt thread can run. Uhh, I think he wants a process to be able to willingly give up its remaining quantum. This is called sched_yield(2). -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 3:46:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5051037B66C for ; Tue, 3 Oct 2000 03:46:41 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA92939; Tue, 3 Oct 2000 12:45:24 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Loony Bomber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: XFreeBSD Install - 4.1-RELEASE #:0 Fri Jul 28 14:30:31 GMT 2000 References: <39D94E55.6E33BD67@208.25.164.82> From: Dag-Erling Smorgrav Date: 03 Oct 2000 12:45:23 +0200 In-Reply-To: Loony Bomber's message of "Mon, 02 Oct 2000 20:11:17 -0700" Message-ID: Lines: 45 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Loony Bomber writes: > Given these qualifications, and the fact > that the first router I built on a recycled 286 system (as a lark) FreeBSD won't run on a 286 (and never has). The 286 is a 16-bit processor, and FreeBSD is (and has always been) a 32-bit OS. > I chose to install xfreebsd with KDE, Gnome, and some ports There is no such thing as XFreeBSD. Maybe you mean XFree86? > When I finally figured > that startx works better than xwin (or whatever xwin commands I first > came across (logically), startx is not the Right Way. Look for 'xdm' in /etc/ttys. > I was totally confounded by the fact that I now > had 4 taskbars on the top and bottom of the screen, two hidden behind > others. I'm doing unorthodox things like loading KDE as a non-managed > session in windowmanager to get my desktop approximating a single > taskbar desktop. Just create a .xsession file in your home directory that contains the single line 'exec /usr/local/bin/startkde'. > Would it be too hard to get the > KDE and Gnome folks together with installation program coders to figure > out an improved x-windows installation routine? The KDE and Gnome folks have no part in this. > The sound card didn't go in either. Ok, so ya purposefully wanted to > give people incentive to build their own kernels. After all the hard > work you put into it, I can see that you might just want to throw up > your hands and say, "If ya can't do that, go back to whatever OS ya' > came from." No, but the sound drivers in 4.1 aren't dynamically loadable, and we don't want to put too much into the GENERIC kernel. 5.0 can load the sound drivers dynamically, and I expect 4.2 will as well. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 3:47:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C42D437B502 for ; Tue, 3 Oct 2000 03:47:47 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA92946; Tue, 3 Oct 2000 12:47:25 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: FengYue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1-stable crash. References: From: Dag-Erling Smorgrav Date: 03 Oct 2000 12:47:24 +0200 In-Reply-To: FengYue's message of "Tue, 3 Oct 2000 00:07:51 -0700 (PDT)" Message-ID: Lines: 25 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FengYue writes: > gdb -k kernel.debug /var/crash/vmcore.0 > [GDB messages...] > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD 2863104 > initial pcb at 247960 > panicstr: page fault > panic messages: > --- Where are the panic messages? > dmesg: kvm_read: > --- > #0 0xc0132df8 in boot () > (kgdb) where > #0 0xc0132df8 in boot () > Cannot access memory at address 0xce51d9b8. > (kgdb) This probably means the panic was in a KLD. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 3:57: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 59C4237B502 for ; Tue, 3 Oct 2000 03:56:56 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id MAA92991; Tue, 3 Oct 2000 12:56:20 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Rink Springer" Cc: Subject: Re: Need some help developing my ethernet driver. References: <000f01c02c89$089ca840$3400000a@springer.cx> From: Dag-Erling Smorgrav Date: 03 Oct 2000 12:56:19 +0200 In-Reply-To: "Rink Springer"'s message of "Mon, 2 Oct 2000 17:54:22 +0200" Message-ID: Lines: 14 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rink Springer" writes: > I am currently working on a driver for the D-Link DE620 Parallel Ethernet > card driver. I used the if_el.c code as a base, for it appears to be a > relatively easy driver (my driver is called dl0 BTW, for D-Link. Anyknow > know if this conflicts somewhere?). You might want to look at src/sys/i386/isa/if_rdp.c instead. And yes, dl is available, though there's a header file called if_dl.h; if your driver needs its own header file, call it if_dlreg.h. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 4: 0:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by hub.freebsd.org (Postfix) with ESMTP id BBD3837B503 for ; Tue, 3 Oct 2000 04:00:55 -0700 (PDT) Received: from toad.stack.nl (toad.ipv6.stack.nl [3ffe:604:3:9:200:e8ff:fe55:346d]) by mailhost.stack.nl (Postfix) with ESMTP id C7E31159E0 for ; Tue, 3 Oct 2000 13:00:54 +0200 (CEST) Received: from stack.nl (dyn68-aud.nbw.tue.nl [::ffff:131.155.32.68]) by toad.stack.nl (Postfix) with ESMTP id 6914E9717 for ; Tue, 3 Oct 2000 13:00:54 +0200 (CEST) Message-ID: <39D9BC63.7C7EDD43@stack.nl> Date: Tue, 03 Oct 2000 13:00:51 +0200 From: Willem van Engen X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.1.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: FreeBSD 4.x kld device driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm writing a device driver for FreeBSD 3.x and 4.x for the application panel of the fujitsu lifebook c4110 notebook (a led, lcd and some buttons). It took me some time to get a working driver (compiles on both 3.x and 4.x), but it's not really clean code. I'd like to rewrite it, but I can't find how to do it properly (the kernel sources don't help me enough). How do I use uimove, DECLARE_MODULE, etc properly? How do I use more than one device in one module? Currently I use outb and inb to access the hardware resources. Should newbus be used in FreeBSD 4.x? Another question is the architecure of the device driver. How exactly should the interface to the device be? Currently, I'm thinking of three devices to control the three different parts /dev/led (led), /dev/lcd (lcd) and /dev/abtn (buttons). Ascii numbers should be written to/read from the character devices. Is this the way to do it, or should system calls be used (harder to use in shell scripts) or binary values? Thanks in advance. Willem van Engen See the application panel project at http://willem.n3.net/fujitsu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 4:40:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 64D9937B503 for ; Tue, 3 Oct 2000 04:40:14 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e93Bfph06288; Tue, 3 Oct 2000 04:41:52 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010031141.e93Bfph06288@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Willem van Engen Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 4.x kld device driver In-reply-to: Your message of "Tue, 03 Oct 2000 13:00:51 +0200." <39D9BC63.7C7EDD43@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Oct 2000 04:41:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have a look at the simple device driver I wrote for the Linksys Gigadrive's front panel LEDs, etc. http://people.freebsd.org/~msmith/gigadrive This approach should suit you well. I would use a single device node and a small set of ioctls for your control interface, as this will keep things simple. You could also use a couple of sysctl nodes (this would make it possible to talk to it without needing a device node). Let me know if you want more comments on your code... > I'm writing a device driver for FreeBSD 3.x and 4.x for the application > panel of the fujitsu lifebook c4110 notebook (a led, lcd and some > buttons). It took me some time to get a working driver (compiles on both > 3.x and 4.x), but it's not really clean code. I'd like to rewrite it, > but I can't find how to do it properly (the kernel sources don't help me > enough). How do I use uimove, DECLARE_MODULE, etc properly? How do I use > more than one device in one module? > Currently I use outb and inb to access the hardware resources. Should > newbus be used in FreeBSD 4.x? > > Another question is the architecure of the device driver. How exactly > should the interface to the device be? Currently, I'm thinking of three > devices to control the three different parts /dev/led (led), /dev/lcd > (lcd) and /dev/abtn (buttons). Ascii numbers should be written to/read > from the character devices. Is this the way to do it, or should system > calls be used (harder to use in shell scripts) or binary values? > > Thanks in advance. > > Willem van Engen > > See the application panel project at http://willem.n3.net/fujitsu/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 5:23:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by hub.freebsd.org (Postfix) with ESMTP id 116FF37B502 for ; Tue, 3 Oct 2000 05:23:42 -0700 (PDT) Received: from toad.stack.nl (toad.ipv6.stack.nl [3ffe:604:3:9:200:e8ff:fe55:346d]) by mailhost.stack.nl (Postfix) with ESMTP id CB24A15A06 for ; Tue, 3 Oct 2000 14:23:39 +0200 (CEST) Received: from stack.nl (dhcp6.stack.nl [::ffff:131.155.141.126]) by toad.stack.nl (Postfix) with ESMTP id B27D09717 for ; Tue, 3 Oct 2000 14:23:39 +0200 (CEST) Message-ID: <39D9CFC8.9C53434D@stack.nl> Date: Tue, 03 Oct 2000 14:23:36 +0200 From: Willem van Engen X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 4.1.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 4.x/3.x kld device driver References: <200010031141.e93Bfph06288@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG  > > Have a look at the simple device driver I wrote for the Linksys > Gigadrive's front panel LEDs, etc. > > http://people.freebsd.org/~msmith/gigadrive Thanks! I think I'll be able to make a working driver with your code. I'd also like to use it on FreeBSD 3.x. When compiling gigadrive there, the file device_if.h can't be found. Any ideas to solve this? > > This approach should suit you well. I would use a single device node and > a small set of ioctls for your control interface, as this will keep > things simple. You could also use a couple of sysctl nodes (this would > make it possible to talk to it without needing a device node). What would you suggest? I have no idea what's best. > > Let me know if you want more comments on your code... > > > I'm writing a device driver for FreeBSD 3.x and 4.x for the application > > panel of the fujitsu lifebook c4110 notebook (a led, lcd and some > > buttons). It took me some time to get a working driver (compiles on both > > 3.x and 4.x), but it's not really clean code. I'd like to rewrite it, > > but I can't find how to do it properly (the kernel sources don't help me > > enough). How do I use uimove, DECLARE_MODULE, etc properly? How do I use > > more than one device in one module? > > Currently I use outb and inb to access the hardware resources. Should > > newbus be used in FreeBSD 4.x? > > > > Another question is the architecure of the device driver. How exactly > > should the interface to the device be? Currently, I'm thinking of three > > devices to control the three different parts /dev/led (led), /dev/lcd > > (lcd) and /dev/abtn (buttons). Ascii numbers should be written to/read > > from the character devices. Is this the way to do it, or should system > > calls be used (harder to use in shell scripts) or binary values? > > > > Thanks in advance. > > > > Willem van Engen > > > > See the application panel project at http://willem.n3.net/fujitsu/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > ... 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] > V I C T O R Y N O T V E N G E A N C E > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 5:28:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neutron.cichlids.com (p3E9E2636.dip.t-dialin.net [62.158.38.54]) by hub.freebsd.org (Postfix) with ESMTP id AD07C37B502 for ; Tue, 3 Oct 2000 05:28:30 -0700 (PDT) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 6FEA6AB91; Tue, 3 Oct 2000 14:29:24 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id B450814A9B; Tue, 3 Oct 2000 14:28:02 +0200 (CEST) Date: Tue, 3 Oct 2000 14:28:02 +0200 To: Rink Springer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Need some help developing my ethernet driver. Message-ID: <20001003142802.A5976@cichlids.cichlids.com> References: <001301c02c96$a0c5ad80$3400000a@springer.cx> <001d01c02c95$fc7eede0$3400000a@springer.cx> <001801c02c94$83c6ce00$3400000a@springer.cx> <000f01c02c89$089ca840$3400000a@springer.cx> <200010021523.JAA11279@harmony.village.org> <200010021621.KAA11813@harmony.village.org> <200010021632.KAA11958@harmony.village.org> <200010021641.KAA12076@harmony.village.org> <001d01c02ca3$dbf60a00$3400000a@springer.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001d01c02ca3$dbf60a00$3400000a@springer.cx>; from rink@springer.cx on Mon, Oct 02, 2000 at 09:04:41PM +0200 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Rink Springer (rink@springer.cx): > One final problem here now... how can I determine which I/O address FreeBSD > is willing me to probe for the device? I cannot find it in any of the > existing drivers... anyone? This is done automatically. Alex -- cat: /home/alex/.sig: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 5:30:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from neutron.cichlids.com (p3E9E2636.dip.t-dialin.net [62.158.38.54]) by hub.freebsd.org (Postfix) with ESMTP id 6031F37B502 for ; Tue, 3 Oct 2000 05:30:20 -0700 (PDT) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (Postfix) with ESMTP id 76005AB91; Tue, 3 Oct 2000 14:31:15 +0200 (CEST) Received: by cichlids.cichlids.com (Postfix, from userid 1001) id 4998214A9B; Tue, 3 Oct 2000 14:30:02 +0200 (CEST) Date: Tue, 3 Oct 2000 14:30:02 +0200 To: Willem van Engen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 4.x/3.x kld device driver Message-ID: <20001003143002.B5976@cichlids.cichlids.com> References: <200010031141.e93Bfph06288@mass.osd.bsdi.com> <39D9CFC8.9C53434D@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39D9CFC8.9C53434D@stack.nl>; from wvengen@stack.nl on Tue, Oct 03, 2000 at 02:23:36PM +0200 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-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Willem van Engen (wvengen@stack.nl): > I'd also like to use it on FreeBSD 3.x. When compiling gigadrive there, > the > file device_if.h can't be found. Any ideas to solve this? This is code that is only working in FreeBSD 4.0 or greater. You really should update if you develop drivers. It's also much easier with the new driver-interface in 4.0 and above. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 6:24:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rccr1.rccr.cremona.it (rccr1.rccr.cremona.it [194.20.53.49]) by hub.freebsd.org (Postfix) with ESMTP id 8C93A37B503 for ; Tue, 3 Oct 2000 06:24:20 -0700 (PDT) Received: from mailman.endymion.com (rccr1.rccr.cremona.it [194.20.53.49] (may be forged)) by rccr1.rccr.cremona.it (8.9.3/8.9.3) with SMTP id PAA21704 for ; Tue, 3 Oct 2000 15:24:32 +0200 Message-Id: <200010031324.PAA21704@rccr1.rccr.cremona.it> To: freebsd-hackers@FreeBSD.org From: mirko.viviani@rccr.cremona.it Subject: dlopen() & objc initializer... Date: Tue, 3 Oct 2000 15:24:33 +0000 X-Mailer: Endymion MailMan Standard Edition v3.0.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ciao! I have an ObjC shared object compiled in this way: gcc -shared -rdynamic -o Bundle BreakTest.o SetTestCase.o -lSenFoundation -lSenTestingKit When I load this object with dlopen() the __objc_exec_class() initializer of the libraries's classes are called first than the objc initializers of the bundle shared objects (BreakTest.o and SetTestCase.o). Why ? Is it possible to tell the dynamic loader to call the BreakTest/SetTestCase objc initializer before the libs initializers ? When I open an handle with dlopen() is possible to get the executable names/paths of the libs linked to it ? Is there in elf something like the __CTOR_LIST__ ? With this example is possible to know in which libs a particular symbol resides ? Thanks in advance. --- Bye, Mirko (NeXTmail, MIME) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 7:27: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B7F9D37B502; Tue, 3 Oct 2000 07:27:00 -0700 (PDT) Received: from jade (jade.cs.binghamton.edu [128.226.140.161]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA24355; Tue, 3 Oct 2000 10:26:59 -0400 (EDT) Date: Tue, 3 Oct 2000 10:26:26 -0400 (EDT) From: Zhiui Zhang X-Sender: zzhang@jade To: John Baldwin Cc: freebsd-hackers@FreeBSD.org Subject: RE: process scheduling quantum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Oct 2000, John Baldwin wrote: > > On 02-Oct-00 Zhiui Zhang wrote: > > > > Suppose a process is scheduled to run, will it run until its quantum ends > > unless it calls tsleep() on his own? In other words, is it possible for a > > process to give up its quantum earlier without having it to do so > > voluntarily? Thanks. > > If an interrupt occurs and puts a thread on the run queue (which will have > higher priority than the currently running proceess) then the current > process will be stopped so that the interrupt thread can run. Thanks. But I guess that you are talking about the new SMP threads. For FreeBSD 4.1-Release, I am not sure this can happen. I am wondering any time taken by interrupts (hardware or software) will be accounted to the current process. If so, the process's quantum is stolen away and nothing useful for that process is done. I wrote program the other day. It read the number of context switches done so far in a loop. If the number changes, then the process exits. In between, it calls getpid(). I just want to see how many system calls can be done between context switch. It turns out sometimes the number of calls to getpid() is zero. That is why I am asking the above question. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 11: 4:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id EF07937B502 for ; Tue, 3 Oct 2000 11:04:31 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.11.0/8.10.2) with ESMTP id e93I6Xt08233; Tue, 3 Oct 2000 11:06:33 -0700 (PDT) Date: Tue, 3 Oct 2000 11:06:28 -0700 (PDT) From: FengYue To: Dag-Erling Smorgrav Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1-stable crash. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 3 Oct 2000, Dag-Erling Smorgrav wrote: ->> panic messages: ->> --- -> ->Where are the panic messages? Unfortunately, there is no panic messages. I compiled the kernel with -g (without DDB), and set the dumpdev in rc.conf. Did I do anything wrong? ->> Cannot access memory at address 0xce51d9b8. ->> (kgdb) -> ->This probably means the panic was in a KLD. How could I know which KLD was having the problem? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 11:12:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 721FB37B66C for ; Tue, 3 Oct 2000 11:12:50 -0700 (PDT) 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 LAA00773; Tue, 3 Oct 2000 11:12:07 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e93IC6l16826; Tue, 3 Oct 2000 11:12:06 -0700 (PDT) (envelope-from jdp) Date: Tue, 3 Oct 2000 11:12:06 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010031812.e93IC6l16826@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: mirko.viviani@rccr.cremona.it Subject: Re: dlopen() & objc initializer... In-Reply-To: <200010031324.PAA21704@rccr1.rccr.cremona.it> References: <200010031324.PAA21704@rccr1.rccr.cremona.it> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200010031324.PAA21704@rccr1.rccr.cremona.it>, wrote: > I have an ObjC shared object compiled in this way: > > gcc -shared -rdynamic -o Bundle BreakTest.o SetTestCase.o -lSenFoundation -lSenTestingKit > > When I load this object with dlopen() the __objc_exec_class() initializer > of the libraries's classes are called first than the objc initializers of the > bundle shared objects (BreakTest.o and SetTestCase.o). > Why ? Because by specifying the needed libraries (-lSenFoundation -lSenTestingKit) you are in effect stating that the other shared objects depend on those libraries. The dynamic linker initializes the libraries before it initializes the shared objects which depend on them. That is almost always the correct thing to do. Suppose for example that BreakTest.o contains a constructor which calls a function in libSenFoundation. The library had better be initialized already when that happens. This is also the ordering used in Solaris, by the way. From their ld.so.1(1): o It calls any initialization functions provided by the shared object dependencies. By default these are called in the reverse order of the topologically sorted dependencies. Should cyclic dependencies exist, the initialization functions are called using the sorted order with the cycle removed. ldd(1) can be used to display the initialization order of shared object dependencies. See also LD_BREADTH. I have tried a lot of different strategies for initializing shared libraries, and the current one breaks fewer programs than any of the others. > Is it possible to tell the dynamic loader to call the > BreakTest/SetTestCase objc initializer before the libs initializers > ? No. > When I open an handle with dlopen() is possible to get the executable > names/paths of the libs linked to it ? Not directly. But you might be able to achieve what you want by using dladdr(3). > Is there in elf something like the __CTOR_LIST__ ? No, nothing that is available to application programs. > With this example is possible to know in which libs a particular symbol > resides ? You might be able to look up the symbol using dlsym with RTLD_DEFAULT. Then you could pass its address to dladdr() to find out which shared library contained the definition. See the notes in the BUGS section of dladdr(3), though. Also, you might need to specify RTLD_GLOBAL when loading the libraries, if you use dlopen() for that. By the way, when asking questions it is a good idea to say which version of FreeBSD you are using. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 11:24:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.va.home.com (ha1.rdc1.va.home.com [24.2.32.66]) by hub.freebsd.org (Postfix) with ESMTP id D8AEF37B503 for ; Tue, 3 Oct 2000 11:24:54 -0700 (PDT) Received: from laptop.baldwin.cx ([24.6.244.187]) by mail.rdc1.va.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001003182454.SWJQ26082.mail.rdc1.va.home.com@laptop.baldwin.cx>; Tue, 3 Oct 2000 11:24:54 -0700 Content-Length: 1195 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: Tue, 03 Oct 2000 11:24:57 -0700 (PDT) From: John Baldwin To: Zhiui Zhang Subject: RE: process scheduling quantum Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Oct-00 Zhiui Zhang wrote: > > On Tue, 3 Oct 2000, John Baldwin wrote: >> >> On 02-Oct-00 Zhiui Zhang wrote: >> > >> > Suppose a process is scheduled to run, will it run until its quantum ends >> > unless it calls tsleep() on his own? In other words, is it possible for a >> > process to give up its quantum earlier without having it to do so >> > voluntarily? Thanks. >> >> If an interrupt occurs and puts a thread on the run queue (which will have >> higher priority than the currently running proceess) then the current >> process will be stopped so that the interrupt thread can run. > > Thanks. But I guess that you are talking about the new SMP threads. For > FreeBSD 4.1-Release, I am not sure this can happen. I am wondering any > time taken by interrupts (hardware or software) will be accounted to the > current process. If so, the process's quantum is stolen away and nothing > useful for that process is done. Yes, in pre-SMPng, interrupts use up part of the current process's quantum. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 11:25: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 8228037B66E for ; Tue, 3 Oct 2000 11:25:04 -0700 (PDT) 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 LAA00832; Tue, 3 Oct 2000 11:24:15 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e93IOEQ16876; Tue, 3 Oct 2000 11:24:14 -0700 (PDT) (envelope-from jdp) Date: Tue, 3 Oct 2000 11:24:14 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010031824.e93IOEQ16876@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: bright@wintelcom.net Subject: Re: atomic operations In-Reply-To: <20001003012240.G27736@fw.wintelcom.net> References: <00b701c0273b$39f7aaa0$0901a8c0@haym.transactionsite.com> <20001003012240.G27736@fw.wintelcom.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001003012240.G27736@fw.wintelcom.net>, Alfred Perlstein wrote: > > +typedef struct { volatile int a; } atomic_t; > + > +#define atomic_init(p, v) do { p->a = v; } while(0) > +#define atomic_destroy(p) do { ; } while(0) I don't see the need for the do ... while(0) construct here. Why not something simpler? #define atomic_init(p, v) ((p)->a = (v)) #define atomic_destroy(p) ((void)0) Likewise for atomic_set(), which seems to do the same thing as atomic_init(). John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 12: 2:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 629F237B503; Tue, 3 Oct 2000 12:02:39 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id VAA19690; Tue, 3 Oct 2000 21:00:39 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.11.0/8.11.0) id e93IJEv68378; Tue, 3 Oct 2000 20:19:14 +0200 (CEST) (envelope-from andreas) Date: Tue, 3 Oct 2000 20:19:14 +0200 From: Andreas Klemm To: Edward Elhauge Cc: Alfred Perlstein , freebsd-hackers@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: Frustration with SCSI system Message-ID: <20001003201914.A62553@titan.klemm.gtn.com> References: <20000920125128.F9141@fw.wintelcom.net> <200009202024.NAA45822@ns2.uncanny.net> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009202024.NAA45822@ns2.uncanny.net>; from ee@uncanny.net on Wed, Sep 20, 2000 at 01:24:34PM -0700 X-Operating-System: FreeBSD 4.1.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 01:24:34PM -0700, Edward Elhauge wrote: > OK, vinum is good. But my understanding is that you can't use vinum on > your root partition. By Murphy's Law it always seems to be root that gets > screwed up. And that also causes the biggest problems because then you > have to yank the system apart and find another host disk for booting. What about "duplicating and updating" /, /var and /usr onto a 2nd disk ? This could be automatically done by a shellscript. You only need to fine tune /mirror/etc/fstab to boot from the correct disk after a such a "backup/mirror" run .... If you install the freebsd boot manager you can even easily test booting from the 2nd drive without having to make special settings in the forth boot loader. You could manage this using three disks I think Disk: da0 da1 da2 Fs: ================================================================+ root-fs | s1a s1a (backup) | | ------------------------------------------------+ | swap | swap swap | | ------------------------------------------------+ swap | var-fs | s1f s1f (backup) | | ------------------------------------------------+ | usr-fs | s1g s1g (backup) | | ------------------------------------------------+---------------+ vinum RAID5 | /usr/local | ------------------------------------------------+---------------+ vinum RAID5 | /home | ------------------------------------------------+---------------+ I'm not sure, maybe its even possible to put /var onto a Vinum Software RAID-5 ...... Andreas /// -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 12:46:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (Postfix) with ESMTP id 6FAF537B503 for ; Tue, 3 Oct 2000 12:46:37 -0700 (PDT) Received: from heathers (heathers [199.89.192.5]) by heathers.stdio.com (8.9.3/8.8.8) with ESMTP id PAA98748 for ; Tue, 3 Oct 2000 15:46:36 -0400 (EDT) (envelope-from lile@stdio.com) Date: Tue, 3 Oct 2000 15:46:36 -0400 (EDT) From: Larry Lile To: hackers@freebsd.org Subject: Question about -Wchar-subscripts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just asked a question that I really don't know what the "correct" answer is, so here it is. ...we get scores of warnings about using characters as subscripts to an array (-Wchar-subscripts), which generates so much noise as to mask real warnings burried within. Therefore, I would like to suppress this warning unless someone can explain why using a char as an array subscript is in any way an illegitimate thing to do. As far as I can tell, getting rid of the warning by changing the code would require adding a large number of frivolous casts to scores of source files... So why is using a "char" as an array subscript wrong? I had always avoided it because the compiler complained and that was good enough for me. Just curious. -- Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 12:49:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 69CB037B502 for ; Tue, 3 Oct 2000 12:49:17 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id OAA18055; Tue, 3 Oct 2000 14:49:11 -0500 (CDT) (envelope-from dan) Date: Tue, 3 Oct 2000 14:49:11 -0500 From: Dan Nelson To: Larry Lile Cc: hackers@FreeBSD.ORG Subject: Re: Question about -Wchar-subscripts Message-ID: <20001003144911.A12803@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: ; from "Larry Lile" on Tue Oct 3 15:46:36 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 03), Larry Lile said: > > ...we get scores of warnings about using characters as subscripts > to an array (-Wchar-subscripts), which generates so much noise as > to mask real warnings burried within. Therefore, I would like to > suppress this warning unless someone can explain why using a char > as an array subscript is in any way an illegitimate thing to do. > As far as I can tell, getting rid of the warning by changing the > code would require adding a large number of frivolous casts to > scores of source files... > > So why is using a "char" as an array subscript wrong? I had always > avoided it because the compiler complained and that was good enough > for me. Because your char value could be negative and end up referencing memory before your array start. Mainly a problem with the ctype macros and high-ascii characters. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 13:13:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id E2E2237B502 for ; Tue, 3 Oct 2000 13:13:22 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.10.1/8.10.1) with ESMTP id e93KDFF23441; Tue, 3 Oct 2000 16:13:16 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id QAA40800; Tue, 3 Oct 2000 16:13:14 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id QAA81703; Tue, 3 Oct 2000 16:13:14 -0400 (EDT) Date: Tue, 3 Oct 2000 16:13:14 -0400 (EDT) From: Thomas David Rivers Message-Id: <200010032013.QAA81703@lakes.dignus.com> To: dnelson@emsphone.com, lile@stdio.com Subject: Re: Question about -Wchar-subscripts Cc: hackers@FreeBSD.ORG In-Reply-To: <20001003144911.A12803@dan.emsphone.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In the last episode (Oct 03), Larry Lile said: > > > > ...we get scores of warnings about using characters as subscripts > > to an array (-Wchar-subscripts), which generates so much noise as > > to mask real warnings burried within. Therefore, I would like to > > suppress this warning unless someone can explain why using a char > > as an array subscript is in any way an illegitimate thing to do. > > As far as I can tell, getting rid of the warning by changing the > > code would require adding a large number of frivolous casts to > > scores of source files... > > > > So why is using a "char" as an array subscript wrong? I had always > > avoided it because the compiler complained and that was good enough > > for me. > > Because your char value could be negative and end up referencing memory > before your array start. Mainly a problem with the ctype macros and > high-ascii characters. > That's an interesting reason... any variable can be negative (well, except for the unsigned types...) - what's so interesting about `char'? Is it simply ctype macros that are the concern, or something "bigger"? - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 14:29:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c2-dbn-97.dial-up.net (c2-dbn-97.dial-up.net [196.34.155.225]) by hub.freebsd.org (Postfix) with ESMTP id 579DE37B503 for ; Tue, 3 Oct 2000 14:29:31 -0700 (PDT) Received: (from rnordier@localhost) by c2-dbn-97.dial-up.net (8.8.7/8.6.12) id XAA29173; Tue, 3 Oct 2000 23:27:52 +0200 (SAST) From: Robert Nordier Message-Id: <200010032127.XAA29173@c2-dbn-97.dial-up.net> Subject: Re: Question about -Wchar-subscripts In-Reply-To: <200010032013.QAA81703@lakes.dignus.com> "from Thomas David Rivers at Oct 3, 2000 04:13:14 pm" To: Thomas David Rivers Date: Tue, 3 Oct 2000 23:27:49 +0200 (SAST) Cc: dnelson@emsphone.com, lile@stdio.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > > So why is using a "char" as an array subscript wrong? I had always > > > avoided it because the compiler complained and that was good enough > > > for me. > > > > Because your char value could be negative and end up referencing memory > > before your array start. Mainly a problem with the ctype macros and > > high-ascii characters. > > > > That's an interesting reason... any variable can be negative (well, > except for the unsigned types...) - what's so interesting about > `char'? Is it simply ctype macros that are the concern, or something > "bigger"? What's interesting about char is that it's implementation defined whether "plain" char is the equivalent of "signed char" or "unsigned char" (or even something else). So, given an 8-bit, two's complement implementation of char, the statement char i = 128; may cause 'i' to end up as -128 or 128, for example. An implementation-defined value to your subscript is almost never useful, so this kind of behavior does warrant a warning. You'll notice gcc doesn't warn if explicitly signed or unsigned chars are used as subscripts, as then there is no uncertainty. -- Robert Nordier rnordier@nordier.com rnordier@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 15:21:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EC5A737B66C for ; Tue, 3 Oct 2000 15:21:44 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id AAA96000; Wed, 4 Oct 2000 00:21:26 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: FengYue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1-stable crash. References: From: Dag-Erling Smorgrav Date: 04 Oct 2000 00:21:24 +0200 In-Reply-To: FengYue's message of "Tue, 3 Oct 2000 11:06:28 -0700 (PDT)" Message-ID: Lines: 23 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FengYue writes: > On 3 Oct 2000, Dag-Erling Smorgrav wrote: > -> > panic messages: > -> > --- > -> Where are the panic messages? > > Unfortunately, there is no panic messages. I compiled the kernel with > -g (without DDB), and set the dumpdev in rc.conf. Did I do anything > wrong? The only thing I can think of is that the installed kernel is not the one that paniced, so you are running gdb with the wrong symbol file. > -> > Cannot access memory at address 0xce51d9b8. > -> > (kgdb) > -> This probably means the panic was in a KLD. > How could I know which KLD was having the problem? Hard to tell; usually from context. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 16:26:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9C2CD37B66C for ; Tue, 3 Oct 2000 16:26:26 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id BAA90013 for hackers@FreeBSD.ORG; Wed, 4 Oct 2000 01:26:25 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id e93LU1N04688 for ; Tue, 3 Oct 2000 23:30:02 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <00bf01c02d81$17f90240$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" Cc: References: <20001003144911.A12803@dan.emsphone.com> Subject: Re: Question about -Wchar-subscripts Date: Tue, 3 Oct 2000 23:26:20 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Dan Nelson" To: "Larry Lile" Cc: Sent: Tuesday, October 03, 2000 9:49 PM Subject: Re: Question about -Wchar-subscripts > In the last episode (Oct 03), Larry Lile said: > > > > ...we get scores of warnings about using characters as subscripts > > to an array (-Wchar-subscripts), which generates so much noise as > > to mask real warnings burried within. Therefore, I would like to > > suppress this warning unless someone can explain why using a char > > as an array subscript is in any way an illegitimate thing to do. > > As far as I can tell, getting rid of the warning by changing the > > code would require adding a large number of frivolous casts to > > scores of source files... > > > > So why is using a "char" as an array subscript wrong? I had always > > avoided it because the compiler complained and that was good enough > > for me. > > Because your char value could be negative and end up referencing memory > before your array start. Mainly a problem with the ctype macros and > high-ascii characters. > How about unsigned char? Could that be used for index? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 18:20:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id D4C5337B502 for ; Tue, 3 Oct 2000 18:20:46 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e941JKa77673; Wed, 4 Oct 2000 02:19:20 +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.11.1/8.11.0) with ESMTP id e941HLs37052; Wed, 4 Oct 2000 02:17:21 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200010040117.e941HLs37052@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Neil Blakey-Milner Cc: FreeBSD Hackers , Doug Barton , Sheldon Hearn , brian@Awfulhak.org Subject: Re: Making /etc/defaults/rc.conf a configuration file. In-Reply-To: Message from Neil Blakey-Milner of "Tue, 03 Oct 2000 03:32:45 +0200." <20001003033245.A63319@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Oct 2000 02:17:20 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > With these patches, and the new tiny util 'sourceconf', we can make > /etc/defaults/rc.conf and /etc/defaults/periodic.conf configuration > files again, such that they can be parsed by things other than 'sh'. [.....] Looks good to me ! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 20:41:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 4C2ED37B503 for ; Tue, 3 Oct 2000 20:41:34 -0700 (PDT) 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 VAA09902; Tue, 3 Oct 2000 21:41:32 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id VAA27905; Tue, 3 Oct 2000 21:41:31 -0600 (MDT) (envelope-from nate) Date: Tue, 3 Oct 2000 21:41:31 -0600 (MDT) Message-Id: <200010040341.VAA27905@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jordan Hubbard Cc: freebsd-hackers@FreeBSD.org Subject: Automatic updates (was Re: How long for -stable...) In-Reply-To: <84222.970618959@winston.osd.bsdi.com> References: <39DA7437.EAD39E03@originative.co.uk> <84222.970618959@winston.osd.bsdi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Culled the list way down, and moved it to -hackers ] > We could also look into providing an "update" command or something > which would pull either sources or binaries over from a snapshot box > and make the process of getting up to the branch-head a lot easier. > It's long been on my wishlist and I'm at the point where I'd be > willing to devote some BSDi resources to both writing the software > and setting up a build box for creating the relevant binaries on an > ongoing basis. Whoo hoo. Sounds like a *great* plan! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 21:10: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 940BF37B502 for ; Tue, 3 Oct 2000 21:10:00 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e9449qT12284; Wed, 4 Oct 2000 00:09:54 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id AAA41639; Wed, 4 Oct 2000 00:09:50 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id AAA83630; Wed, 4 Oct 2000 00:09:50 -0400 (EDT) Date: Wed, 4 Oct 2000 00:09:50 -0400 (EDT) From: Thomas David Rivers Message-Id: <200010040409.AAA83630@lakes.dignus.com> To: rivers@dignus.com, rnordier@nordier.com Subject: Re: Question about -Wchar-subscripts Cc: dnelson@emsphone.com, hackers@FreeBSD.ORG, lile@stdio.com In-Reply-To: <200010032127.XAA29173@c2-dbn-97.dial-up.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > Thomas David Rivers wrote: > > > > > So why is using a "char" as an array subscript wrong? I had always > > > > avoided it because the compiler complained and that was good enough > > > > for me. > > > > > > Because your char value could be negative and end up referencing memory > > > before your array start. Mainly a problem with the ctype macros and > > > high-ascii characters. > > > > > > > That's an interesting reason... any variable can be negative (well, > > except for the unsigned types...) - what's so interesting about > > `char'? Is it simply ctype macros that are the concern, or something > > "bigger"? > > What's interesting about char is that it's implementation defined > whether "plain" char is the equivalent of "signed char" or "unsigned > char" (or even something else). > > So, given an 8-bit, two's complement implementation of char, the > statement > > char i = 128; > > may cause 'i' to end up as -128 or 128, for example. > > An implementation-defined value to your subscript is almost never > useful, so this kind of behavior does warrant a warning. You'll > notice gcc doesn't warn if explicitly signed or unsigned chars are > used as subscripts, as then there is no uncertainty. > > -- > Robert Nordier Ah - yes! That makes perfect sense... when you consider that `char' all alone can be signed or unsigned... Thanks for the explanation! - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 3 23:18:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id 1CE0D37B503 for ; Tue, 3 Oct 2000 23:18:34 -0700 (PDT) Received: from home.com ([24.177.36.45]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20001004061823.PNBN6495.femail1.sdc1.sfba.home.com@home.com> for ; Tue, 3 Oct 2000 23:18:23 -0700 Message-ID: <39DACC64.38635986@home.com> Date: Tue, 03 Oct 2000 23:21:24 -0700 From: loconet Organization: loconet X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: World.sh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am makeing a script for newbies to help them upgrade there system it isnt really pretty it mostly just a script that i made in a cuple of hours but does the job and i was wundering if anyone could give it a try and then email me bug/info/ etc.. or if you whant to help me then email me saying so.. to dl goto : world-sh.sourceforge.net or www.sourceforge.net/projects/world-sh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 9:32:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 4F05E37B502 for ; Wed, 4 Oct 2000 09:32:11 -0700 (PDT) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.0/8.11.0) id e94GWAl32020 for freebsd-hackers@freebsd.org; Wed, 4 Oct 2000 12:32:10 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 04 Oct 2000 12:32:09 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: freebsd-hackers@freebsd.org Subject: How to allocate kernel memory with PG_NC_PCD set Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The subject says it all :) What is the best way to allocate kernel memory with non-cacheable bit set? Or, better yet, is it possible to change caching bit on an already kmalloc'ed memory block? Will something like this work? pt_entry_t pte; pte = (pt_entry_t)vtopte(vaddr); *pte |= PG_NC_PCD; invtlb(); ---------------------------------- E-Mail: Alexander N. Kabaev Date: 04-Oct-00 Time: 12:12:22 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 11: 3: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9D40737B503 for ; Wed, 4 Oct 2000 11:02:44 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e94I2gM16593; Wed, 4 Oct 2000 12:02:42 -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 MAA38253; Wed, 4 Oct 2000 12:02:41 -0600 (MDT) Message-Id: <200010041802.MAA38253@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: Automatic updates (was Re: How long for -stable...) Cc: Jordan Hubbard , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 03 Oct 2000 21:41:31 MDT." <200010040341.VAA27905@nomad.yogotech.com> References: <200010040341.VAA27905@nomad.yogotech.com> <39DA7437.EAD39E03@originative.co.uk> <84222.970618959@winston.osd.bsdi.com> Date: Wed, 04 Oct 2000 12:02:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010040341.VAA27905@nomad.yogotech.com> Nate Williams writes: : [ Culled the list way down, and moved it to -hackers ] : : > We could also look into providing an "update" command or something : > which would pull either sources or binaries over from a snapshot box : > and make the process of getting up to the branch-head a lot easier. : > It's long been on my wishlist and I'm at the point where I'd be : > willing to devote some BSDi resources to both writing the software : > and setting up a build box for creating the relevant binaries on an : > ongoing basis. : : Whoo hoo. Sounds like a *great* plan! I think that we can do a lot with cvsupd. I've used cvsupd to grab binaries on an experimental basis and it seems to work great. I've also worked at companies that did this on all their workstations on boot and they updated one area and then rebooted 20-odd machines to update them. Not without its problems, but a lot less hair than even an installworld. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 11:15:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E237C37B503 for ; Wed, 4 Oct 2000 11:15:13 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e94IEwX92176; Wed, 4 Oct 2000 11:14:59 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Warner Losh Cc: nate@yogotech.com (Nate Williams), freebsd-hackers@FreeBSD.ORG Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: Message from Warner Losh of "Wed, 04 Oct 2000 12:02:41 MDT." <200010041802.MAA38253@harmony.village.org> Date: Wed, 04 Oct 2000 11:14:58 -0700 Message-ID: <92172.970683298@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that we can do a lot with cvsupd. I've used cvsupd to grab > binaries on an experimental basis and it seems to work great. I've Hmmm. Does cvsupd also move a target out of the way if it already exists and it's in the process of replacing it? What if the target is chflag'd but can be unprotected at the current security level? What I'm trying to say is that if you have "/sbin/init" and cvsupd is about to replace it, I would expect the steps to be something like this: Receive new init as /sbin/init.${pid} (or something) | |<--------------------------------------------+ | Yes |Yes \/ No | No Mv /sbin/init.${pid} /sbin/init --> chflags noschg /sbin/init --> Fail | | Yes \/ Done If cvsupd does that or can be gimmicked to do that (add --potentially-hose-me flag? ;) then I'd say it's a serious contender for being part of a binary update process. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 11:17:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id CCBCB37B66C for ; Wed, 4 Oct 2000 11:17:24 -0700 (PDT) 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 MAA24168; Wed, 4 Oct 2000 12:17:20 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id MAA01838; Wed, 4 Oct 2000 12:17:19 -0600 (MDT) (envelope-from nate) Date: Wed, 4 Oct 2000 12:17:19 -0600 (MDT) Message-Id: <200010041817.MAA01838@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jordan Hubbard Cc: Warner Losh , nate@yogotech.com (Nate Williams), freebsd-hackers@FreeBSD.ORG Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: <92172.970683298@winston.osd.bsdi.com> References: <200010041802.MAA38253@harmony.village.org> <92172.970683298@winston.osd.bsdi.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think that we can do a lot with cvsupd. I've used cvsupd to grab > > binaries on an experimental basis and it seems to work great. I've > > Hmmm. Does cvsupd also move a target out of the way if it already > exists and it's in the process of replacing it? What if the target is > chflag'd but can be unprotected at the current security level? I know the author, and I'll bet you he could be convinced to modify it to do what we need. *grin* Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 11:24: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8FCDF37B503 for ; Wed, 4 Oct 2000 11:23:59 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e94INvM16758; Wed, 4 Oct 2000 12:23:57 -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 MAA38586; Wed, 4 Oct 2000 12:23:57 -0600 (MDT) Message-Id: <200010041823.MAA38586@harmony.village.org> To: Jordan Hubbard Subject: Re: Automatic updates (was Re: How long for -stable...) Cc: nate@yogotech.com (Nate Williams), freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 04 Oct 2000 11:14:58 PDT." <92172.970683298@winston.osd.bsdi.com> References: <92172.970683298@winston.osd.bsdi.com> Date: Wed, 04 Oct 2000 12:23:57 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <92172.970683298@winston.osd.bsdi.com> Jordan Hubbard writes: : > I think that we can do a lot with cvsupd. I've used cvsupd to grab : > binaries on an experimental basis and it seems to work great. I've : : Hmmm. Does cvsupd also move a target out of the way if it already : exists and it's in the process of replacing it? What if the target is : chflag'd but can be unprotected at the current security level? : : What I'm trying to say is that if you have "/sbin/init" and cvsupd is : about to replace it, I would expect the steps to be something like : this: : : Receive new init as /sbin/init.${pid} (or something) : | : |<--------------------------------------------+ : | Yes |Yes : \/ No | No : Mv /sbin/init.${pid} /sbin/init --> chflags noschg /sbin/init --> Fail : | : | Yes : \/ : Done : : If cvsupd does that or can be gimmicked to do that (add : --potentially-hose-me flag? ;) then I'd say it's a serious : contender for being part of a binary update process. I don't know. I seem to recall that jdp told me at the talk I gave last year that it just wipes the flags completely and doesn't honor them. I think it deals well with this, but I've not tried to replace init on a running system. Given that the Pluto upgrade went well, I'd expect the answer is yes, it works. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 12:55: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-04-real.cdsnet.net (mail-04-real.cdsnet.net [63.163.68.109]) by hub.freebsd.org (Postfix) with SMTP id 48C6837B502 for ; Wed, 4 Oct 2000 12:55:06 -0700 (PDT) Received: (qmail 75698 invoked from network); 4 Oct 2000 19:54:57 -0000 Received: from apocalypse.cdsnet.net (63.163.68.5) by mail-04-real.cdsnet.net with SMTP; 4 Oct 2000 19:54:57 -0000 Date: Wed, 4 Oct 2000 12:54:56 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@apocalypse.cdsnet.net To: hackers@freebsd.org Subject: IDE drives doing BBR? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Used ABBR on SCSI disks all the time, very nice. Remember reading on hackers somewhere that newer drives like IBM supported this feature. I'm getting a few bad blocks on a 75GB IBM drive (at least according to the ata driver), and rather than replacing it and moves on, the disk basically dies. However, I run the IBM drive fitness test, it works some magic in there writing data to the drive, and the drive is back, and the failed block now seems fine. So is there some equivalent of camcontrol or scsicmd for ATA drives that turns on this feature, and allows my running system to take advantage of it? Or do I just write nul's to the block or 0's, and it's supposed to do it automatically? or do I just punt. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 13:43:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id D90EE37B502 for ; Wed, 4 Oct 2000 13:43:24 -0700 (PDT) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id QAA08873 for ; Wed, 4 Oct 2000 16:43:14 -0400 (EDT) Received: from mailsrv2.mitre.org (mailsrv2.mitre.org [129.83.221.17]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id QAA12458 for ; Wed, 4 Oct 2000 16:43:01 -0400 (EDT) Received: from mitre.org ([128.29.145.140]) by mailsrv2.mitre.org (Netscape Messaging Server 4.1) with ESMTP id G1XAW000.Q71; Wed, 4 Oct 2000 16:43:12 -0400 Message-ID: <39DB964A.86AFAE84@mitre.org> Date: Wed, 04 Oct 2000 16:42:50 -0400 From: "Andresen,Jason R." Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: IDE drives doing BBR? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen wrote: > > Used ABBR on SCSI disks all the time, very nice. > > Remember reading on hackers somewhere that newer drives like IBM supported > this feature. I'm getting a few bad blocks on a 75GB IBM drive (at least > according to the ata driver), and rather than replacing it and moves on, > the disk basically dies. > > However, I run the IBM drive fitness test, it works some magic in there > writing data to the drive, and the drive is back, and the failed block now > seems fine. > > So is there some equivalent of camcontrol or scsicmd for ATA drives that > turns on this feature, and allows my running system to take advantage of > it? > > Or do I just write nul's to the block or 0's, and it's supposed to do it > automatically? or do I just punt. Or a possible third option: A 75GB IBM HD is probablly still within the warentee period. Assuming you don't play fetch with your dog and the HD, you can probabally get it replaced. -- _ _ _ ___ ____ ___ ______________________________________ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- jandrese@mitre.org / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/ \_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 14:23:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 8E78037B503 for ; Wed, 4 Oct 2000 14:23:21 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.11.0/8.10.2) with ESMTP id e94LPQ909345 for ; Wed, 4 Oct 2000 14:25:26 -0700 (PDT) Date: Wed, 4 Oct 2000 14:25:26 -0700 (PDT) From: FengYue To: freebsd-hackers@FreeBSD.ORG Subject: anonymous memory map vs mmap on /dev/zero In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, excluding the extra kernel calls of open()/close() on /dev/zero, which one of the following would be more efficient: 1) Using mmap on /dev/zero 2) Using mmap with MAP_ANON flag The purpose is, ofcourse, to share the memory (R&W) among all child processes. It seems that mmap on /dev/zero is more portable. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 14:54:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id E82E937B503 for ; Wed, 4 Oct 2000 14:54:47 -0700 (PDT) Received: from mini.acl.lanl.gov (root@mini.acl.lanl.gov [128.165.147.34]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id PAA6430864; Wed, 4 Oct 2000 15:54:37 -0600 (MDT) Received: from localhost (rminnich@localhost) by mini.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id PAA07895; Wed, 4 Oct 2000 15:54:37 -0600 X-Authentication-Warning: mini.acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 4 Oct 2000 15:54:37 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@mini.acl.lanl.gov To: FengYue Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: anonymous memory map vs mmap on /dev/zero In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Oct 2000, FengYue wrote: > It seems that mmap on /dev/zero is more portable. no really, It won't work at all correctly on linux, and on Tru64 it does the totally wrong thing, but the (fd = -1, MAP_ANONYMOUS) does the right thing on tru64. It's disappointing that this works so unportably :-( ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 17: 4:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 23A2F37B503 for ; Wed, 4 Oct 2000 17:04:27 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e9504Id78606; Wed, 4 Oct 2000 17:04:23 -0700 (PDT) Date: Wed, 4 Oct 2000 17:04:18 -0700 (PDT) From: Doug White To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: IDE drives doing BBR? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Oct 2000, Jaye Mathisen wrote: > Remember reading on hackers somewhere that newer drives like IBM supported > this feature. I'm getting a few bad blocks on a 75GB IBM drive (at least > according to the ata driver), and rather than replacing it and moves on, > the disk basically dies. > > However, I run the IBM drive fitness test, it works some magic in there > writing data to the drive, and the drive is back, and the failed block now > seems fine. > Ran into this today actually ... Yes the IBMs do automatic block remapping ... you may have to scrub the disk a few times to get the bad blocks out. Now you have 75GB of potentially bad blocks so you have to scrub pretty completely. > Or do I just write nul's to the block or 0's, and it's supposed to do it > automatically? or do I just punt. 'dd if=/dev/zero of=/dev/ad1 bs=4k' works great; takes about an hour to scrub the entire disk. Run until clean. Running it right now in fact. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 17:19:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 73A3137B502 for ; Wed, 4 Oct 2000 17:19:54 -0700 (PDT) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA02036; Wed, 4 Oct 2000 17:19:44 -0700 Date: Wed, 4 Oct 2000 17:19:44 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug White Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: IDE drives doing BBR? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Or do I just write nul's to the block or 0's, and it's supposed to do it > > automatically? or do I just punt. > > 'dd if=/dev/zero of=/dev/ad1 bs=4k' works great; takes about an hour to > scrub the entire disk. Run until clean. Running it right now in fact. Err, Umm, I wouldn't assume that drives always know that writes have failed. Do a read pass too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 4 21:14:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 0AA5E37B66C for ; Wed, 4 Oct 2000 21:14:08 -0700 (PDT) Received: from gorean.org (master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA26570; Wed, 4 Oct 2000 21:13:55 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39DC0003.713CF2B7@gorean.org> Date: Wed, 04 Oct 2000 21:13:55 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Neil Blakey-Milner Cc: FreeBSD Hackers , Sheldon Hearn Subject: Re: Making /etc/defaults/rc.conf a configuration file. References: <20001003033245.A63319@mithrandr.moria.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neil Blakey-Milner wrote: > > Hi, > > With these patches, and the new tiny util 'sourceconf', we can make > /etc/defaults/rc.conf and /etc/defaults/periodic.conf configuration > files again, such that they can be parsed by things other than 'sh'. I have been very sick the last few days, so I haven't commented on this yet. > It also allows you to set 'rc_conf_files' (or, actually, whatever you > set filevar to) in lower places than the default file, so that you don't > change the default file. Can you give more details about this process? I'm not sure how it would work to change the list of conf files other than in the default location if you're going to source the defaults anyway. > This only shows how to replace things using rc.conf - changing scripts > to use periodic.conf is as simple as replacing > > if [ -r /etc/defaults/periodic.conf ] > then > . /etc/defaults/periodic.conf > source_periodic_confs > fi > > with > > rcfile=/etc/defaults/periodic.conf listvar=periodic_conf_files . /etc/sourceconf But you're basically doing exactly the same thing(s), just in a different order. With all due respect to Neil, I stated previously that I feel like this is a solution in search of a problem. I'm not arguing for the status quo necessarily, I'm just concerned that when something comes along down the road that *does* need to do something differently, we will end up redoing all of this stuff again. For what it's worth, I do not oppose the change, however I would like to see some comments in the sourceconf file as to what is going on where and why. I can't help feeling that sourceconf_start and sourceconf_dosrc could just as easily be in the same function, but in my current state I'm probably missing something. Also, in the sc.patch the entry for /etc/rc has ". /etc/sourceconfs" instead of ". /etc/sourceconf". In any case, if the patch has been thoroughly tested under a variety of different configurations, it's probably worth putting in -current. It would probably be worth comparing what you're doing here to the work that's happening on the rc files in netbsd that some here have discussed bringing over, in whole or in part. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 0:21:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 5C2FA37B503 for ; Thu, 5 Oct 2000 00:21:14 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e957N3h00680; Thu, 5 Oct 2000 00:23:04 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010050723.e957N3h00680@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Alexander N. Kabaev" Cc: freebsd-hackers@freebsd.org Subject: Re: How to allocate kernel memory with PG_NC_PCD set In-reply-to: Your message of "Wed, 04 Oct 2000 12:32:09 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Oct 2000 00:23:03 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The subject says it all :) > > What is the best way to allocate kernel memory with non-cacheable bit set? Or, > better yet, is it possible to change caching bit on an already kmalloc'ed > memory block? Will something like this work? > > pt_entry_t pte; > pte = (pt_entry_t)vtopte(vaddr); > *pte |= PG_NC_PCD; > invtlb(); Only in i386-specific code. Can you be more explicit about what exactly it is that you're trying to do? The x86 already has strong cache coherence, and mapped PCI space is typically not marked cacheable in the default MTRR setup so this sort of thing is typically unnecessary. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 4:19:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id B638B37B502 for ; Thu, 5 Oct 2000 04:19:30 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13h93J-000NDe-00; Thu, 05 Oct 2000 13:19:05 +0200 Date: Thu, 5 Oct 2000 13:19:05 +0200 From: Neil Blakey-Milner To: Doug Barton Cc: FreeBSD Hackers , Sheldon Hearn Subject: Re: Making /etc/defaults/rc.conf a configuration file. Message-ID: <20001005131905.A89144@mithrandr.moria.org> References: <20001003033245.A63319@mithrandr.moria.org> <39DC0003.713CF2B7@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39DC0003.713CF2B7@gorean.org>; from DougB@gorean.org on Wed, Oct 04, 2000 at 09:13:55PM -0700 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed 2000-10-04 (21:13), Doug Barton wrote: > Can you give more details about this process? I'm not sure how it would > work to change the list of conf files other than in the default location > if you're going to source the defaults anyway. defaults/rc.conf has ``rc_conf_files=/etc/rc.conf /etc/rc.conf.local'' rc.conf doesn't change rc_conf_files rc.conf.local sets rc_conf_files=/etc/rc.conf.script-generated rc.conf.script-generated doesn't change rc_conf_files So, we start with defaults/rc.conf, and read that in, and see listvar (rc_conf_files) says to look in rc.conf, so we read that in, and it doesn't set rc_conf_files, so we go to rc.conf.local, and read that in. It sets rc_conf_files to a file we haven't seen before, so we read it in. This may not be obvious, but it'll be obvious once it's documented. > > This only shows how to replace things using rc.conf - changing scripts > > to use periodic.conf is as simple as replacing > > > > if [ -r /etc/defaults/periodic.conf ] > > then > > . /etc/defaults/periodic.conf > > source_periodic_confs > > fi > > > > with > > > > rcfile=/etc/defaults/periodic.conf listvar=periodic_conf_files . /etc/sourceconf > > But you're basically doing exactly the same thing(s), just in a > different order. With all due respect to Neil, I stated previously that > I feel like this is a solution in search of a problem. I'm not arguing > for the status quo necessarily, I'm just concerned that when something > comes along down the road that *does* need to do something differently, > we will end up redoing all of this stuff again. I can't see how anything _can_ come down the road. It's an interface. If we want to read in configuration variables, we run the command. We don't care _how_ it does it, just that it does. If we need to change something, it'll be within that /etc/sourceconf file. > For what it's worth, I do not oppose the change, however I would like > to see some comments in the sourceconf file as to what is going on where > and why. I can't help feeling that sourceconf_start and sourceconf_dosrc > could just as easily be in the same function, but in my current state > I'm probably missing something. Also, in the sc.patch the entry for > /etc/rc has ". /etc/sourceconfs" instead of ". /etc/sourceconf". Oops, you're write, the patch won't work. That's what I get for generating the patch on another machine by hand, I suppose. The patch I've generated now (with just the one change) is the one I've actually been using to boot for the past few days. I don't mind adding mini-documentation to the scripts, I suppose, if that's required. > In any case, if the patch has been thoroughly tested under a variety of > different configurations, it's probably worth putting in -current. It > would probably be worth comparing what you're doing here to the work > that's happening on the rc files in netbsd that some here have discussed > bringing over, in whole or in part. We're not conflicting with anything that's happened in NetBSD. NetBSD's stuff is quite reasonable, but Daniel Sobral has pointed me at some things that he feels are missing, and I tend to agree after discussion with him. It is my plan (you probably heard me mentioning it) to investigate the NetBSD stuff properly, and compare it with slightly more featureful USM ( http://www.roguetrader.com/~brandon/sas/ ), which unfortunately may do too many things behind your back than what we're used to. However, I have a few things before that in my queue, and one of them is making it possible to develop a simple C API for reading our sh-style configuration, which somewhat requires that non-configuration code to disappear. (I should've continued when my suggestion was totally rebuffed last time, but I didn't have the time) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 11: 4:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palnet.com (mail.palnet.com [192.116.19.220]) by hub.freebsd.org (Postfix) with ESMTP id 45F6F37B503; Thu, 5 Oct 2000 11:04:09 -0700 (PDT) Received: from stinky.palnet.com (dogbert.palnet.com [192.116.17.51]) by mail.palnet.com (8.9.3/8.9.3) with ESMTP id UAA36175; Thu, 5 Oct 2000 20:09:10 +0200 (IST) Message-Id: <5.0.0.23.0.20001005194437.00abf8a8@192.116.19.220> X-Sender: mustafa@192.116.19.220 X-Mailer: QUALCOMM Windows Eudora Version 5.0.0.23 (Beta) Date: Thu, 05 Oct 2000 19:45:40 +0200 To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org From: Mustafa Deeb Subject: Looking for Patches Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, anyone knows where to find a MYSQL patch for cistron? cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 13: 2:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 2B87737B502 for ; Thu, 5 Oct 2000 13:02:48 -0700 (PDT) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id NAA38632 for ; Thu, 5 Oct 2000 13:02:47 -0700 (PDT) (envelope-from rh@matriplex.com) Date: Thu, 5 Oct 2000 13:02:47 -0700 (PDT) From: Richard Hodges To: freebsd-hackers@freebsd.org Subject: A decent way to get CPU idle time? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings! Is there a clean and decent way to find out the percentage of CPU idle time, like top and systat give? I have browsed the source for both, and neither appear to have a simple way of finding this information. I have already tried and rejected getloadavg. In my application, two main processes will always account for 95% or more of the activity. I suppose I could use RDTSC to grab the clock on my system calls, and figure a rudimentary sum of CPU activity, but that won't help me with the expensive file and socket calls. And I would pretty much have to guess about the CPU time spent in the kernel. Any ideas? Thanks. -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. rh@matriplex.com | 769 Basque Way 775-886-6477 | Carson City, NV 89706 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 13:15: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 03E0937B66C for ; Thu, 5 Oct 2000 13:15:02 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id QAA79946 for hackers@freebsd.org; Thu, 5 Oct 2000 16:15:01 -0400 (EDT) (envelope-from mwlucas) Date: Thu, 5 Oct 2000 16:15:01 -0400 From: Michael Lucas To: hackers@freebsd.org Subject: When do you want to see panics? Message-ID: <20001005161501.A79896@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if this is on-topic, but what the heck: I've started playing a little more freely with my laptop. One result is comparatively frequent panics when doing things I know damn well are almost certain to fail, say, while playing with the Linuxulator or in mount_union. Are these panics & debugger dumps something people want to see, or is the general attitude "then don't *do* that!" ? If you folks want 'em, I'll send them. (I suppose the generalized form of this question is, "Are panics normal when the sysadmin is a behaving like a damned fool?" ;) Thanks, Michael -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 13:29:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 8978937B502 for ; Thu, 5 Oct 2000 13:29:50 -0700 (PDT) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1Z00K8C4SWA9@field.videotron.net> for hackers@FreeBSD.ORG; Thu, 5 Oct 2000 16:26:56 -0400 (EDT) Date: Thu, 05 Oct 2000 16:30:54 -0400 (EDT) From: Bosko Milekic Subject: Re: When do you want to see panics? In-reply-to: <20001005161501.A79896@blackhelicopters.org> X-Sender: bmilekic@jehovah.technokratis.com To: Michael Lucas Cc: hackers@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, not in the general case, they are not normal! So feel free to provide the info. :-) On Thu, 5 Oct 2000, Michael Lucas wrote: > Not sure if this is on-topic, but what the heck: > > I've started playing a little more freely with my laptop. One result > is comparatively frequent panics when doing things I know damn well > are almost certain to fail, say, while playing with the Linuxulator or > in mount_union. > > Are these panics & debugger dumps something people want to see, or is > the general attitude "then don't *do* that!" ? > > If you folks want 'em, I'll send them. > > (I suppose the generalized form of this question is, "Are panics > normal when the sysadmin is a behaving like a damned fool?" ;) > > Thanks, > Michael > > -- > Michael Lucas > mwlucas@blackhelicopters.org > http://www.blackhelicopters.org/~mwlucas/ > Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 13:49:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 5D45037B502 for ; Thu, 5 Oct 2000 13:49:22 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e95KnFx05066; Thu, 5 Oct 2000 13:49:15 -0700 (PDT) Date: Thu, 5 Oct 2000 13:49:15 -0700 From: Alfred Perlstein To: Michael Lucas Cc: hackers@FreeBSD.ORG Subject: Re: When do you want to see panics? Message-ID: <20001005134915.D27736@fw.wintelcom.net> References: <20001005161501.A79896@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001005161501.A79896@blackhelicopters.org>; from mwlucas@blackhelicopters.org on Thu, Oct 05, 2000 at 04:15:01PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael Lucas [001005 13:15] wrote: > Not sure if this is on-topic, but what the heck: > > I've started playing a little more freely with my laptop. One result > is comparatively frequent panics when doing things I know damn well > are almost certain to fail, say, while playing with the Linuxulator or > in mount_union. > > Are these panics & debugger dumps something people want to see, or is > the general attitude "then don't *do* that!" ? > > If you folks want 'em, I'll send them. > > (I suppose the generalized form of this question is, "Are panics > normal when the sysadmin is a behaving like a damned fool?" ;) I really depends, if you're doing stuff like randomly writing to /dev/kmem probably not, on the otherhand if you're getting panics just by running linux programs that aren't system related then probably yes. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 13:59:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id 3AF6C37B502 for ; Thu, 5 Oct 2000 13:59:25 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13hI6o-0006VG-00; Thu, 05 Oct 2000 21:59:18 +0100 Date: Thu, 5 Oct 2000 21:59:18 +0100 To: hackers@freebsd.org Subject: "find /proc" Message-ID: <20001005215918.A24987@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why does find(1) operate non-recursively in /proc? % uname -a FreeBSD example.com 4.1-STABLE FreeBSD 4.1-STABLE #0: Thu Aug 31 22:31:20 EDT 2000 root@example.com:/usr/obj/usr/src/sys/EXAMPLE i386 % find /proc /proc /proc/curproc /proc/48643 /proc/48576 /proc/48511 /proc/48510 /proc/48467 /proc/48454 /proc/48453 /proc/1013 /proc/288 /proc/287 /proc/286 /proc/276 /proc/269 /proc/179 /proc/123 /proc/120 /proc/118 /proc/98 /proc/92 /proc/5 /proc/4 /proc/3 /proc/2 /proc/1 /proc/0 % -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 14:24:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9A54E37B503 for ; Thu, 5 Oct 2000 14:24:03 -0700 (PDT) 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 OAA12212; Thu, 5 Oct 2000 14:22:21 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e95LMKW22443; Thu, 5 Oct 2000 14:22:20 -0700 (PDT) (envelope-from jdp) Date: Thu, 5 Oct 2000 14:22:20 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010052122.e95LMKW22443@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jkh@winston.osd.bsdi.com Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: <92172.970683298@winston.osd.bsdi.com> References: <92172.970683298@winston.osd.bsdi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <92172.970683298@winston.osd.bsdi.com>, Jordan Hubbard wrote: > > I think that we can do a lot with cvsupd. I've used cvsupd to grab > > binaries on an experimental basis and it seems to work great. I've > > Hmmm. Does cvsupd also move a target out of the way if it already > exists and it's in the process of replacing it? What if the target is > chflag'd but can be unprotected at the current security level? > > What I'm trying to say is that if you have "/sbin/init" and cvsupd is > about to replace it, I would expect the steps to be something like > this: > > Receive new init as /sbin/init.${pid} (or something) > | > |<--------------------------------------------+ > | Yes |Yes > \/ No | No > Mv /sbin/init.${pid} /sbin/init --> chflags noschg /sbin/init --> Fail > | > | Yes > \/ > Done > > If cvsupd does that or can be gimmicked to do that (add > --potentially-hose-me flag? ;) then I'd say it's a serious > contender for being part of a binary update process. Hmmm ... how can we find out what CVSup does? ... Hmmmm ... :-) It does exactly what you say you want it to do. The sequence goes something like this: - receive new file into a temp file - verify its MD5 signature - clear the flags of the target file to 0 - atomically rename() the temp file to the target name - set the flags of the target to whatever they are supposed to be John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 14:24:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D59A037B66C for ; Thu, 5 Oct 2000 14:24:06 -0700 (PDT) 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 OAA12216; Thu, 5 Oct 2000 14:23:47 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e95LNlC22460; Thu, 5 Oct 2000 14:23:47 -0700 (PDT) (envelope-from jdp) Date: Thu, 5 Oct 2000 14:23:47 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010052123.e95LNlC22460@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: rminnich@lanl.gov Subject: Re: anonymous memory map vs mmap on /dev/zero In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Ronald G Minnich wrote: > On Wed, 4 Oct 2000, FengYue wrote: > > > It seems that mmap on /dev/zero is more portable. > > no really, It won't work at all correctly on linux, and on Tru64 it does > the totally wrong thing, but the (fd = -1, MAP_ANONYMOUS) does the right > thing on tru64. > > It's disappointing that this works so unportably :-( The other oddity about Tru64 is that a 0-length mmap of a 0-length file fails. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 15: 9:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 38EAE37B503 for ; Thu, 5 Oct 2000 15:09:53 -0700 (PDT) Received: from holly.calldei.com ([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 <0G1Z00MI28XV3T@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Thu, 5 Oct 2000 16:56:19 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id QAA28899; Thu, 05 Oct 2000 16:57:50 -0500 (CDT envelope-from chris) Date: Thu, 05 Oct 2000 16:57:50 -0500 From: Chris Costello Subject: Re: "find /proc" In-reply-to: <20001005215918.A24987@firedrake.org> To: void Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20001005165749.D26550@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <20001005215918.A24987@firedrake.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, October 05, 2000, void wrote: > Why does find(1) operate non-recursively in /proc? Because the procfs_readdir() code does not report directories as the correct type (DT_REG as opposed to the proper DT_DIR). -- |Chris Costello |TRAPEZOID - A device for catching zoids. `---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 15:11:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dayspring.firedrake.org (dayspring.firedrake.org [195.82.105.251]) by hub.freebsd.org (Postfix) with ESMTP id E1F6837B503 for ; Thu, 5 Oct 2000 15:11:09 -0700 (PDT) Received: from float by dayspring.firedrake.org with local (Exim 3.12 #1 (Debian)) id 13hJE5-0007I6-00; Thu, 05 Oct 2000 23:10:53 +0100 Date: Thu, 5 Oct 2000 23:10:53 +0100 From: void To: Chris Costello Cc: hackers@FreeBSD.ORG Subject: Re: "find /proc" Message-ID: <20001005231053.A28010@firedrake.org> References: <20001005215918.A24987@firedrake.org> <20001005165749.D26550@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001005165749.D26550@holly.calldei.com>; from chris@calldei.com on Thu, Oct 05, 2000 at 04:57:50PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 05, 2000 at 04:57:50PM -0500, Chris Costello wrote: > On Thursday, October 05, 2000, void wrote: > > Why does find(1) operate non-recursively in /proc? > > Because the procfs_readdir() code does not report directories > as the correct type (DT_REG as opposed to the proper DT_DIR). Sounds like a bug, do you think I should submit a PR? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 15:22: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 47DC737B502 for ; Thu, 5 Oct 2000 15:21:56 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e95MLk308685; Thu, 5 Oct 2000 15:21:46 -0700 (PDT) Date: Thu, 5 Oct 2000 15:21:46 -0700 From: Alfred Perlstein To: void Cc: Chris Costello , hackers@FreeBSD.ORG Subject: Re: "find /proc" Message-ID: <20001005152146.L27736@fw.wintelcom.net> References: <20001005215918.A24987@firedrake.org> <20001005165749.D26550@holly.calldei.com> <20001005231053.A28010@firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001005231053.A28010@firedrake.org>; from float@firedrake.org on Thu, Oct 05, 2000 at 11:10:53PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * void [001005 15:11] wrote: > On Thu, Oct 05, 2000 at 04:57:50PM -0500, Chris Costello wrote: > > On Thursday, October 05, 2000, void wrote: > > > Why does find(1) operate non-recursively in /proc? > > > > Because the procfs_readdir() code does not report directories > > as the correct type (DT_REG as opposed to the proper DT_DIR). > > Sounds like a bug, do you think I should submit a PR? No, try this: Index: procfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/procfs/procfs_vnops.c,v retrieving revision 1.76.2.1 diff -u -u -r1.76.2.1 procfs_vnops.c --- procfs_vnops.c 2000/06/21 09:33:43 1.76.2.1 +++ procfs_vnops.c 2000/10/05 22:19:41 @@ -901,7 +901,7 @@ dp->d_fileno = PROCFS_FILENO(p->p_pid, Pproc); dp->d_namlen = sprintf(dp->d_name, "%ld", (long)p->p_pid); - dp->d_type = DT_REG; + dp->d_type = DT_DIR; p = p->p_list.le_next; break; } Thanks Chris. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 15:59: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id EE00D37B502 for ; Thu, 5 Oct 2000 15:58:55 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e95MwgX01717 for ; Thu, 5 Oct 2000 15:58:44 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: hackers@freebsd.org Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: Message from jdp@polstra.com of "Thu, 05 Oct 2000 14:22:20 PDT." <200010052122.e95LMKW22443@vashon.polstra.com> Date: Thu, 05 Oct 2000 15:58:40 -0700 Message-ID: <1712.970786720@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It does exactly what you say you want it to do. The sequence goes > something like this: Awesome! Thanks; I knew I should have just asked you in the first place. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 16:17:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id 645CB37B502 for ; Thu, 5 Oct 2000 16:17:55 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id 5C27E1925E for ; Thu, 5 Oct 2000 18:17:51 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id SAA68514 for freebsd-hackers@freebsd.org; Thu, 5 Oct 2000 18:17:51 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Thu, 5 Oct 2000 18:17:51 -0500 From: "Jacques A. Vidrine" To: freebsd-hackers@freebsd.org Subject: _THREAD_SAFE in libc Message-ID: <20001005181751.A68499@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it ok to use pthread_rwlock* and other such primitives in code in src/lib/libc (when _THREAD_SAFE is defined, of course)? I ask because I don't see any other code doing this. Perhaps there is a private interface to use? Perhaps I'm barking up the wrong tree? Context: I want to make nsdispatch thread safe (inasmuch as possible-- e.g. I'm not tackling the resolver), so I need to protect its data structures. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 16:23: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2118937B503 for ; Thu, 5 Oct 2000 16:23:01 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e95NMu910844; Thu, 5 Oct 2000 16:22:56 -0700 (PDT) Date: Thu, 5 Oct 2000 16:22:56 -0700 From: Alfred Perlstein To: "Jacques A. Vidrine" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: _THREAD_SAFE in libc Message-ID: <20001005162255.T27736@fw.wintelcom.net> References: <20001005181751.A68499@hamlet.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001005181751.A68499@hamlet.nectar.com>; from n@nectar.com on Thu, Oct 05, 2000 at 06:17:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jacques A. Vidrine [001005 16:18] wrote: > Is it ok to use pthread_rwlock* and other such primitives in code in > src/lib/libc (when _THREAD_SAFE is defined, of course)? > > I ask because I don't see any other code doing this. Perhaps there is a > private interface to use? Perhaps I'm barking up the wrong tree? > > Context: I want to make nsdispatch thread safe (inasmuch as possible-- > e.g. I'm not tackling the resolver), so I need to protect its data > structures. It sure looks like it. cd /usr/src/lib/libc/ ; grep pthread */* -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 18:50:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 7FDF937B502 for ; Thu, 5 Oct 2000 18:50:35 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id VAA81278; Thu, 5 Oct 2000 21:50:32 -0400 (EDT) (envelope-from mwlucas) Date: Thu, 5 Oct 2000 21:50:32 -0400 From: Michael Lucas To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: When do you want to see panics? Message-ID: <20001005215032.A81257@blackhelicopters.org> References: <20001005161501.A79896@blackhelicopters.org> <20001005134915.D27736@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001005134915.D27736@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Oct 05, 2000 at 01:49:15PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 05, 2000 at 01:49:15PM -0700, Alfred Perlstein wrote: > * Michael Lucas [001005 13:15] wrote: > > (I suppose the generalized form of this question is, "Are panics > > normal when the sysadmin is a behaving like a damned fool?" ;) > > I really depends, if you're doing stuff like randomly writing to > /dev/kmem probably not, on the otherhand if you're getting panics > just by running linux programs that aren't system related then > probably yes. :) So the panic from "/compat/linux/sbin/e2fsck /compat/linux/dev/hda3" isn't useful? :) Thanks, I'll send them when they happen. ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 5 20:52:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0B20A37B502 for ; Thu, 5 Oct 2000 20:52:16 -0700 (PDT) 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 UAA13800; Thu, 5 Oct 2000 20:52:13 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id e963qCW23453; Thu, 5 Oct 2000 20:52:12 -0700 (PDT) (envelope-from jdp) Date: Thu, 5 Oct 2000 20:52:12 -0700 (PDT) From: jdp@polstra.com Message-Id: <200010060352.e963qCW23453@vashon.polstra.com> To: hackers@freebsd.org Reply-To: hackers@freebsd.org Cc: jkh@winston.osd.bsdi.com Subject: Re: Automatic updates (was Re: How long for -stable...) In-Reply-To: <1712.970786720@winston.osd.bsdi.com> References: <1712.970786720@winston.osd.bsdi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <1712.970786720@winston.osd.bsdi.com>, Jordan Hubbard wrote: > > It does exactly what you say you want it to do. The sequence goes > > something like this: > > Awesome! Thanks; I knew I should have just asked you in the > first place. :) One caveat (ok, two caveats): it doesn't currently understand named pipes or Unix domain sockets. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 1:14:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id D8F6637B66C for ; Fri, 6 Oct 2000 01:14:37 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13hSeI-000400-00; Fri, 06 Oct 2000 10:14:34 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13hSeH-0003PN-00; Fri, 06 Oct 2000 11:14:33 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: bsdi-users@mailinglists.org Cc: hackers@FreeBSD.ORG Subject: Adaptec AIC 7899 SCSI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 10:14:33 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, somebody dropped a Dell PowerEdge 2450 rackmount server on my lap :-) it has Dell Perc 3/si controller, which seems to be another name for Adaptec AIC-7899. anyway, NT: ok FreeBSD: 4.1.1 does not see it BSDi: 4.1 does see the controller but does not find any disks Linux: not yet tested. any hits? danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 1:19:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id BF38137B66F for ; Fri, 6 Oct 2000 01:19:22 -0700 (PDT) Received: (from root@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id e968JLM47254 for freebsd-hackers@freebsd.org; Fri, 6 Oct 2000 03:19:21 -0500 (EST) (envelope-from steve) Date: Fri, 6 Oct 2000 03:19:21 -0500 (EST) From: Steve Ames Message-Id: <200010060819.e968JLM47254@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: IPFW quirk Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey... I just type 'ipfw -a list' on the command line and got back an invalid argument error. That confused me for a bit so I poked around for a while and then it just started working again. A bit more poking and I discovered that it fails if there is a file called 'list' in the directory the command is being executed from. Seems ipfw checks for a file containing commands before it checks to see if you've issued a valid command? A bit of experimenting ('touch flush', 'ipfw flush') seems to indicate that its true for most commands. Perhaps this is intentional but its behavior confused me a bit... And it means I can't leave a file called 'list' laying around as then /etc/security output is wrong. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 1:29: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id B8E2437B66C for ; Fri, 6 Oct 2000 01:28:59 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id e968Sf080499; Fri, 6 Oct 2000 11:28:41 +0300 (EEST) (envelope-from ru) Date: Fri, 6 Oct 2000 11:28:41 +0300 From: Ruslan Ermilov To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW quirk Message-ID: <20001006112841.A80260@sunbay.com> Mail-Followup-To: Steve Ames , freebsd-hackers@FreeBSD.ORG References: <200010060819.e968JLM47254@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010060819.e968JLM47254@virtual-voodoo.com>; from steve@virtual-voodoo.com on Fri, Oct 06, 2000 at 03:19:21AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 06, 2000 at 03:19:21AM -0500, Steve Ames wrote: > > Hey... I just type 'ipfw -a list' on the command line and got back an > invalid argument error. That confused me for a bit so I poked around > for a while and then it just started working again. A bit more poking > and I discovered that it fails if there is a file called 'list' in > the directory the command is being executed from. > > Seems ipfw checks for a file containing commands before it checks to > see if you've issued a valid command? > > A bit of experimenting ('touch flush', 'ipfw flush') seems to indicate > that its true for most commands. Perhaps this is intentional but its > behavior confused me a bit... And it means I can't leave a file called > 'list' laying around as then /etc/security output is wrong. > Also known as PR 16179. I was planning on looking at it today :-) -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 1:37: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 87E0137B502 for ; Fri, 6 Oct 2000 01:37:00 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e968cbh04977; Fri, 6 Oct 2000 01:38:38 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010060838.e968cbh04977@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Danny Braniss Cc: bsdi-users@mailinglists.org, hackers@FreeBSD.ORG Subject: Re: Adaptec AIC 7899 SCSI In-reply-to: Your message of "Fri, 06 Oct 2000 10:14:33 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 01:38:37 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi all, > somebody dropped a Dell PowerEdge 2450 rackmount server on my lap :-) > it has Dell Perc 3/si controller, which seems to be another name for > Adaptec AIC-7899. No. The 3/Si involves the i960 and the DIMM slot as well. If you have the RAID key in the system (little dongle, plugs over on the righthand side, check the diagram inside the system lid), you will need the 'aac' driver from -current or http://people.freebsd.org/~msmith/RAID/index.html#adaptec If there's no RAID key in the system, then you have a standard aic7899. If there's a RAID key but no DIMM, then you will probably confuse the hell out of things. Note that you need to set the controller up before you can do anything with it. > anyway, > NT: ok > FreeBSD: 4.1.1 does not see it > BSDi: 4.1 does see the controller but does not find any disks I'd be interested to know what BSD/OS thinks it's seeing. I don't believe they support this controller. > Linux: not yet tested. You will need the percraid driver as shipped by Dell, or the aacraid driver as shipping with RedHat 7.0 -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 1:58:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id D7F5337B66D; Fri, 6 Oct 2000 01:58:34 -0700 (PDT) Received: from sexta.cs.huji.ac.il ([132.65.16.13] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.16 #1) id 13hTKo-0004PI-00; Fri, 06 Oct 2000 10:58:30 +0200 Received: from localhost ([127.0.0.1] helo=sexta.cs.huji.ac.il ident=danny) by sexta.cs.huji.ac.il with esmtp (Exim 3.15 #1) id 13hTKn-0003R3-00; Fri, 06 Oct 2000 11:58:29 +0300 X-Mailer: exmh version 2.2 06/23/2000 with nmh-0.24 To: Mike Smith Cc: bsdi-users@mailinglists.org, hackers@FreeBSD.ORG Subject: Re: Adaptec AIC 7899 SCSI In-reply-to: Your message of Fri, 06 Oct 2000 01:38:37 -0700 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 10:58:29 +0200 From: Danny Braniss Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200010060838.e968cbh04977@mass.osd.bsdi.com>you write: }> hi all, }> somebody dropped a Dell PowerEdge 2450 rackmount server on my lap :-) }> it has Dell Perc 3/si controller, which seems to be another name for }> Adaptec AIC-7899. } }No. The 3/Si involves the i960 and the DIMM slot as well. If you have }the RAID key in the system (little dongle, plugs over on the righthand }side, check the diagram inside the system lid), you will need the 'aac' }driver from -current or }http://people.freebsd.org/~msmith/RAID/index.html#adaptec getting it now, will check asap. } }If there's no RAID key in the system, then you have a standard aic7899. }If there's a RAID key but no DIMM, then you will probably confuse the }hell out of things. Note that you need to set the controller up before }you can do anything with it. } it has both, so far i disabled the RAID in the BIOS and now the disk is seen. im at the moment installing FreeBSD 4.1.1, since BSDi though saw the disks couldn't get the exp0/exp1 to work (Grrrrr) }> anyway, }> NT: ok }> FreeBSD: 4.1.1 does not see it }> BSDi: 4.1 does see the controller but does not find any disks } }I'd be interested to know what BSD/OS thinks it's seeing. I don't }believe they support this controller. it does, and saw the 2 ibm disks, and something else which i forgot :-( but didn't check if it could write because my floppy instalation uses the network (see above). } }> Linux: not yet tested. } }You will need the percraid driver as shipped by Dell, or the aacraid }driver as shipping with RedHat 7.0 } thanks, danny PS: BTW, i sent you a bootp.c with dhcp stuff some while ago ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 4: 2:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from threat.tjhsst.edu (threat.tjhsst.edu [198.38.16.9]) by hub.freebsd.org (Postfix) with ESMTP id B0E8D37B503 for ; Fri, 6 Oct 2000 04:02:29 -0700 (PDT) Received: from localhost (abarros@localhost) by threat.tjhsst.edu (8.11.1/8.11.0) with ESMTP id e96As3308383; Fri, 6 Oct 2000 06:54:03 -0400 Date: Fri, 6 Oct 2000 06:54:03 -0400 (EDT) From: Andrew Barros To: Danny Braniss Cc: bsdi-users@mailinglists.org, hackers@FreeBSD.ORG Subject: Re: Adaptec AIC 7899 SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG im almost certain that linux has support for this (I belive it has support for the entire 7xxx sieies) --Andy On Fri, 6 Oct 2000, Danny Braniss wrote: > hi all, > somebody dropped a Dell PowerEdge 2450 rackmount server on my lap :-) > it has Dell Perc 3/si controller, which seems to be another name for > Adaptec AIC-7899. > > anyway, > NT: ok > FreeBSD: 4.1.1 does not see it > BSDi: 4.1 does see the controller but does not find any disks > Linux: not yet tested. > > any hits? > danny > > > > --------------------------------------------------------------------- > Searchable Archive: http://www.nexial.com/cgi-bin/bsdibody > To unsubscribe, e-mail: bsdi-users-unsubscribe@mailinglists.org > For additional commands, e-mail: bsdi-users-help@mailinglists.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 5:44:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id A93F037B503 for ; Fri, 6 Oct 2000 05:44:08 -0700 (PDT) Received: (qmail 5951 invoked by uid 1001); 6 Oct 2000 12:43:59 -0000 Date: Fri, 6 Oct 2000 15:43:59 +0300 From: Peter Pentchev To: freebsd-hackers@freebsd.org Subject: weird rpc.statd memory behavior Message-ID: <20001006154359.C232@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a RELENG_4 machine with the world rebuilt on Sep 27, 'top' gave me the following output after sorting by the 'SIZE' field.. last pid: 424; load averages: 0.17, 0.15, 0.10 up 0+00:29:43 15:39:23 46 processes: 1 running, 45 sleeping CPU states: 4.7% user, 0.0% nice, 1.2% system, 3.1% interrupt, 91.1% idle Mem: 19M Active, 202M Inact, 40M Wired, 80K Cache, 61M Buf, 240M Free Swap: 512M Total, 512M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 125 root 2 0 257M 560K select 0:00 0.00% 0.00% rpc.statd 244 mysql -2 0 12180K 11172K getblk 1:14 5.47% 5.47% mysqld 411 root 2 0 2116K 1580K select 0:00 0.00% 0.00% sshd 269 root 2 0 2116K 1580K select 0:00 0.00% 0.00% sshd [snip more processes] Aaaaaall right then.. what's the deal? :) Yes, I know that those 257 megabytes are not *really* used, allocated, hogged and so on.. but why does statd ask for so much? :) And that's just 29 minutes after a reboot :) G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 6:14:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by hub.freebsd.org (Postfix) with ESMTP id 0D0E237B66C for ; Fri, 6 Oct 2000 06:14:12 -0700 (PDT) Received: from proton.hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.9.3/8.9.3) with ESMTP id PAA03962 for ; Fri, 6 Oct 2000 15:14:13 +0200 (CEST) (envelope-from nighty@proton.hexanet.fr) Message-Id: <200010061314.PAA03962@proton.hexanet.fr> X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: chris@hexanet.fr From: "Christophe Prevotaux" To: freebsd-hackers@freebsd.org Subject: [HELP] AHA 29160N and FreeBSD 4.1.1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 15:14:13 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been trying to install FreeBSD 4.1 and after this 4.1.1 on a machine that has an Adaptec 29160N controller but when formatting the disk I get the following error ahc0: ach_intr - referenced scb not valid during SELTO(15,0) The installation goes on after a while in 4.1 When upgrading to 4.1.1 I had no disks trouble but when trying to install the mysql port under 4.1.1 I ran into a KERNEL PANIC and the system died an reboot and a message about SCB ( again ) I think this has nothing to do with mysql port it just happened to be doing it while I was installing it. does anyone knows what is wrong ? and how to fix this ? -- -- -- =================================================================== Christophe Prevotaux Email: chris@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 6:39:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 921B637B66D for ; Fri, 6 Oct 2000 06:39:51 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-213-168-73-169.netcologne.de [213.168.73.169]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id PAA00497 for ; Fri, 6 Oct 2000 15:39:49 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e96DdeZ00622 for ; Fri, 6 Oct 2000 15:39:40 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 6 Oct 2000 15:39:40 +0200 (CEST) From: Paul Herman To: freebsd-hackers@FreeBSD.ORG Subject: fifos over NFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My take on the nfs code (in nfs_open) is that an open() on a FIFO should return an EACCES. I have no problems with that. But when I NFS Server: mkfifo foo; cat < foo NFS Client: echo "hello world" > foo (over an NFS mount point) the shell hangs on the client trying to open "foo" instead of returning an error. Did I miss something like a mount_nfs option? Thought I'd pick yer brains before digging through the code and sending in a PR. I'm running 4.1.1-RELEASE. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 7: 4:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tuminfo2.informatik.tu-muenchen.de (tuminfo2.informatik.tu-muenchen.de [131.159.0.81]) by hub.freebsd.org (Postfix) with ESMTP id 58D9437B503 for ; Fri, 6 Oct 2000 07:04:10 -0700 (PDT) Received: from atrbg11.informatik.tu-muenchen.de ([131.159.9.196] HELO atrbg11.informatik.tu-muenchen.de ident: postfix [port 2766]) by tuminfo2.informatik.tu-muenchen.de with SMTP id <113684-336>; Fri, 6 Oct 2000 09:36:41 +0000 Received: by atrbg11.informatik.tu-muenchen.de (Postfix, from userid 20455) id 5CEE113631; Fri, 6 Oct 2000 09:36:27 +0200 (CEST) From: Daniel Lang To: freebsd-hackers@freebsd.org Subject: Problems with Serial Console Message-ID: <20001006093627.A17383@atrbg11.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Geek: GCS 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 Date: Fri, 6 Oct 2000 09:36:27 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiho, I have some problems with serial console now under 4.1-STABLE. Ok, this is how I set it up: Flags set for sio0, plugged in cable to terminal-server. dmesg: [..] sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa 0 sio0: type 16550A, console [..] /etc/make.conf: [..] BOOT_COMCONSOLE_PORT= 0x3F8 [..] /boot.config: -Dh This works so far: The boot sequence can be monitored (and changed for e.g. set single-user in loader prompt, visual user config works, too, etc) on the terminal. Now the problem is: I cannot write anything to /dev/console, this just blocks (after the system is up). I realized this, because syslog stopped working, when it tried to do so. I got around this, telling syslog not to write to /dev/console but to /dev/cuaa0. This is another strange thing. The handbook and examples tell, you should use /dev/ttyd0 to run a getty. This did not work either, same problem: I cannot write anything to /dev/ttyd0, it blocks, too. But I got around this by using cuaa0, /etc/ttys: [..] cuaa0 "/usr/libexec/getty std.9600" vt100 on secure [..] Maybe somehow, /dev/console is redirected to /dev/ttyd0 and so both don't seem to work. Well I could live with using /dev/cuaa0 instead, but there comes another problem. When syslog is first started during boot, it complains, it cannot open /dev/cuaa0, because the device is busy. It doesn't hang, but it doesn't write anything to it. Later, if the machine is up, I can send a HUP to syslog, and then it's able to use /dev/cuaa0, without any complaint (and the getty is set up and working, too). Any suggestions ? Best regards, Daniel Lang -- IRCnet: Mr-Spock - ceterum censeo Microsoftinem esse delendam - *Daniel Lang * dl@leo.org * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 7: 4:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.epita.fr (hermes.epita.fr [194.98.116.10]) by hub.freebsd.org (Postfix) with ESMTP id 6C06237B66D; Fri, 6 Oct 2000 07:04:19 -0700 (PDT) Received: from jotun (IDENT:sam@jotun.epita.fr [10.42.42.66]) by hermes.epita.fr id SAA15994 Tue, 3 Oct 2000 18:11:50 GMT Date: Tue, 3 Oct 2000 18:11:49 +0000 From: Sam To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: NFSD stopped in inode state Message-ID: <20001003181149.A5761@epita.fr> Reply-To: sam@epita.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We have 3 Free BSD 4.0 Servers with Ultra160 Adapatec Cards, and ccd'ed U2W drives. They each serve about 500 Pcs (NetBSD), using nfs. Most of the use is from students editing and compiling files. They are heavily used all day (and night) long. The problem is that some times (1 or 2 times every 24 hours), the nfsd process stop in inode state. The Os is still working. i can log on the pc but can't kill the nfsd processes. Sometimes the file system which NFS is exported is unavailable, and unmountable. And we get a fsck of our exported File system. Her are some of our servers confs: ad0: 8223MB [16708/16/63] at ata0-master using UDMA33 ad2: 19574MB [39770/16/63] at ata1-master using UDMA33 ad3: 19574MB [39770/16/63] at ata1-slave using UDMA33 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) (s3 504)# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 4961725 255677 4309110 6% / procfs 4 4 0 100% /proc /dev/ccd0c 138969382 16752490 111099342 13% /space /dev/ccd1c 38856354 22757162 12990684 64% /save (/space is exported...) Thanx for any idea of wath is really happening... Sam ---- sam@epita.fr Admin - Sys EPITA (Ecole pour l'informatique et les techniques avancees) Tel: 01 44 08 01 96 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 7:13: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id 646D737B502 for ; Fri, 6 Oct 2000 07:13:03 -0700 (PDT) Received: from white.acl.lanl.gov (root@white.acl.lanl.gov [128.165.147.100]) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id IAA6950627; Fri, 6 Oct 2000 08:13:02 -0600 (MDT) Received: from localhost (rminnich@localhost) by white.acl.lanl.gov (8.9.3/8.8.8) with ESMTP id IAA32481; Fri, 6 Oct 2000 08:13:01 -0600 X-Authentication-Warning: white.acl.lanl.gov: rminnich owned process doing -bs Date: Fri, 6 Oct 2000 08:13:01 -0600 (MDT) From: Ronald G Minnich X-Sender: rminnich@white.acl.lanl.gov To: Danny Braniss Cc: bsdi-users@mailinglists.org, hackers@FreeBSD.ORG Subject: Re: Adaptec AIC 7899 SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Oct 2000, Danny Braniss wrote: > anyway, > NT: ok > FreeBSD: 4.1.1 does not see it > BSDi: 4.1 does see the controller but does not find any disks > Linux: not yet tested. works here. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 7:39:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 6B48337B502 for ; Fri, 6 Oct 2000 07:39:49 -0700 (PDT) Received: (from steve@localhost) by virtual-voodoo.com (8.11.1/8.11.1) id e96Edli53619 for freebsd-hackers@FreeBSD.ORG; Fri, 6 Oct 2000 09:39:47 -0500 (EST) (envelope-from steve) Date: Fri, 6 Oct 2000 09:39:47 -0500 From: Steve Ames To: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW quirk Message-ID: <20001006093947.A53426@virtual-voodoo.com> References: <200010060819.e968JLM47254@virtual-voodoo.com> <20001006112841.A80260@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001006112841.A80260@sunbay.com>; from ru@sunbay.com on Fri, Oct 06, 2000 at 11:28:41AM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 06, 2000 at 11:28:41AM +0300, Ruslan Ermilov wrote: > On Fri, Oct 06, 2000 at 03:19:21AM -0500, Steve Ames wrote: > > > > Hey... I just type 'ipfw -a list' on the command line and got back an > > invalid argument error. That confused me for a bit so I poked around > > for a while and then it just started working again. A bit more poking > > and I discovered that it fails if there is a file called 'list' in > > the directory the command is being executed from. > > > > Seems ipfw checks for a file containing commands before it checks to > > see if you've issued a valid command? > > > > A bit of experimenting ('touch flush', 'ipfw flush') seems to indicate > > that its true for most commands. Perhaps this is intentional but its > > behavior confused me a bit... And it means I can't leave a file called > > 'list' laying around as then /etc/security output is wrong. > > > Also known as PR 16179. I was planning on looking at it today :-) Yep. That'd be it. My bad for not checking PRs first. Thank you for looking into this. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 7:46:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [208.42.49.153]) by hub.freebsd.org (Postfix) with ESMTP id AF27C37B502 for ; Fri, 6 Oct 2000 07:46:26 -0700 (PDT) Received: from hamlet.nectar.com (hamlet.nectar.com [10.0.1.102]) by gw.nectar.com (Postfix) with ESMTP id A4B2C1925E; Fri, 6 Oct 2000 09:46:25 -0500 (CDT) Received: (from nectar@localhost) by hamlet.nectar.com (8.9.3/8.9.3) id JAA69723; Fri, 6 Oct 2000 09:46:25 -0500 (CDT) (envelope-from nectar@spawn.nectar.com) Date: Fri, 6 Oct 2000 09:46:25 -0500 From: "Jacques A. Vidrine" To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: _THREAD_SAFE in libc Message-ID: <20001006094625.A68725@hamlet.nectar.com> Mail-Followup-To: "Jacques A. Vidrine" , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG References: <20001005181751.A68499@hamlet.nectar.com> <20001005162255.T27736@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001005162255.T27736@fw.wintelcom.net>; from bright@wintelcom.net on Thu, Oct 05, 2000 at 04:22:56PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 05, 2000 at 04:22:56PM -0700, Alfred Perlstein wrote: > * Jacques A. Vidrine [001005 16:18] wrote: > > Is it ok to use pthread_rwlock* and other such primitives in code in > > src/lib/libc (when _THREAD_SAFE is defined, of course)? > > It sure looks like it. > > cd /usr/src/lib/libc/ ; grep pthread */* I didn't see all those pthread_mutex*s because I was looking for pthread_rwlock*s :-) Which leads me to wonder if I _want_ pthread_rwlock. The overhead might outweigh the benefits of finer-grained locking. Besides, there doesn't seem to be a good way of promoting a lock from read->write. -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 8: 7:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alacritech.com (smtp.alacritech.com [209.10.208.82]) by hub.freebsd.org (Postfix) with ESMTP id 9807237B503 for ; Fri, 6 Oct 2000 08:07:36 -0700 (PDT) Received: from [10.1.10.18] by smtp.alacritech.com (NTMail 4.30.0012/NY3553.00.2884f51f) with ESMTP id ckriaaaa for ; Fri, 6 Oct 2000 08:05:50 -0700 From: "Christopher Harrer" To: Subject: Remote Kernel Debugging Date: Fri, 6 Oct 2000 11:05:57 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <20001006093947.A53426@virtual-voodoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, Not sure if this is the right list or not. I tried posting this on FreeBSD-Questions and did not get a response. If this is not the right list, please let me know. Is there anyway to specify the speed for remote Kernel debugging using gdb? For example, I compile my kernel with gdb symbols (-g) and I reboot my target system. When the boot loader starts up, I enter "boot kernel -d" and get to the "db>" prompt. At this point I'd like to enter "gdb -b 115200", but when I do I get a message "Symbol not found" and gdb does not start. Any ideas? I'm suspecting the serial port speed default to 19.2 or worse yet 9600. Thanks in advance! Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 8:24: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 4B2AE37B66C for ; Fri, 6 Oct 2000 08:24:04 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.9.3) id e96FNvY02330; Fri, 6 Oct 2000 10:23:57 -0500 (CDT) (envelope-from dan) Date: Fri, 6 Oct 2000 10:23:57 -0500 From: Dan Nelson To: Paul Herman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fifos over NFS Message-ID: <20001006102356.A29878@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: ; from "Paul Herman" on Fri Oct 6 15:39:40 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 06), Paul Herman said: > My take on the nfs code (in nfs_open) is that an open() on a FIFO > should return an EACCES. I have no problems with that. But when I > > NFS Server: mkfifo foo; cat < foo > NFS Client: echo "hello world" > foo > > (over an NFS mount point) the shell hangs on the client trying to > open "foo" instead of returning an error. Did I miss something like > a mount_nfs option? I think that's expected behaviour. Fifos should be usable on NFS mounts, but an active fifo is only usable for processes running on the same machine. So if you're running completely diskless, or had NFS-mounted home dirs, for example, you can still use fifos. Your example works if you run both lines on the client, or both on the server. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 9:45:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 2D7A637B502 for ; Fri, 6 Oct 2000 09:45:40 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e96Gjc610091; Fri, 6 Oct 2000 09:45:38 -0700 Date: Fri, 6 Oct 2000 09:45:37 -0700 From: Brooks Davis To: Peter Pentchev Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: weird rpc.statd memory behavior Message-ID: <20001006094537.A9865@Odin.AC.HMC.Edu> References: <20001006154359.C232@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001006154359.C232@ringwraith.office1.bg>; from roam@orbitel.bg on Fri, Oct 06, 2000 at 03:43:59PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 06, 2000 at 03:43:59PM +0300, Peter Pentchev wrote: > On a RELENG_4 machine with the world rebuilt on Sep 27, 'top' gave me > the following output after sorting by the 'SIZE' field.. > > last pid: 424; load averages: 0.17, 0.15, 0.10 up 0+00:29:43 15:39:23 > 46 processes: 1 running, 45 sleeping > CPU states: 4.7% user, 0.0% nice, 1.2% system, 3.1% interrupt, 91.1% idle > Mem: 19M Active, 202M Inact, 40M Wired, 80K Cache, 61M Buf, 240M Free > Swap: 512M Total, 512M Free > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 125 root 2 0 257M 560K select 0:00 0.00% 0.00% rpc.statd > 244 mysql -2 0 12180K 11172K getblk 1:14 5.47% 5.47% mysqld > 411 root 2 0 2116K 1580K select 0:00 0.00% 0.00% sshd > 269 root 2 0 2116K 1580K select 0:00 0.00% 0.00% sshd > [snip more processes] > > Aaaaaall right then.. what's the deal? :) Yes, I know that those 257 > megabytes are not *really* used, allocated, hogged and so on.. but why > does statd ask for so much? :) And that's just 29 minutes after a reboot :) Use The Source Luke. Taking a quick look at the source memory is only allocated in two places. On malloc which doesn't account for this and one f*ing hugh mmap of a file in /var to allow for extension of the file. The code in -current mmaps 0x10000000 bytes of address space or exactly 256MB. This is compleatly harmless as it not only doesn't use any real memory, but since it's mmaping a file in /var it doesn't use any swap either. Check it out for your self at: /usr/src/usr.sbin/rpc.statd -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 10:44:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Gloria.CAM.ORG (Gloria.CAM.ORG [205.151.116.34]) by hub.freebsd.org (Postfix) with ESMTP id 7B22237B503 for ; Fri, 6 Oct 2000 10:44:49 -0700 (PDT) Received: from localhost (intmktg@localhost) by Gloria.CAM.ORG (8.9.3/8.9.3) with ESMTP id NAA29225 for ; Fri, 6 Oct 2000 13:46:27 -0400 Date: Fri, 6 Oct 2000 13:46:26 -0400 (EDT) From: Marc Tardif To: freebsd-hackers@freebsd.org Subject: aio_read timeout per request Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I initiate multiple aio_read requests on sockets, how can I set a timeout for each request? If I call aio_waitcomplete, that sets a timeout for all. So, if I have 5 aio_reads, I would call aio_waitcomplete as many times in a loop waiting to process the first finished request. Problem with this approach is that I can end up waiting a maximum of 5*timeout for the last request to finish because aio_waitcomplete is called again with the same timeout each time. I could imagine a way this can be solved by keeping a timer and calling aio_waitcomplete with the time remaining and then, when the timer expires, call aio_return. But is there a simpler way? Is there sample code or documentation I should read on the subject? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 10:52:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 706) id 9212837B502; Fri, 6 Oct 2000 10:52:16 -0700 (PDT) Date: Fri, 6 Oct 2000 10:52:16 -0700 From: Jonathan Lemon To: Marc Tardif Cc: freebsd-hackers@freebsd.org Subject: Re: aio_read timeout per request Message-ID: <20001006105216.C18697@hub.freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Marc Tardif on Fri, Oct 06, 2000 at 01:46:26PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 06, 2000 at 01:46:26PM -0400, Marc Tardif wrote: > If I initiate multiple aio_read requests on sockets, how can > I set a timeout for each request? If I call aio_waitcomplete, > that sets a timeout for all. So, if I have 5 aio_reads, I > would call aio_waitcomplete as many times in a loop waiting > to process the first finished request. Problem with this > approach is that I can end up waiting a maximum of 5*timeout > for the last request to finish because aio_waitcomplete is > called again with the same timeout each time. I could imagine > a way this can be solved by keeping a timer and calling > aio_waitcomplete with the time remaining and then, when the > timer expires, call aio_return. But is there a simpler way? > Is there sample code or documentation I should read on the > subject? I think there's a bit of confusion here. The timeout value to aiowaitcomplete is similar to that of poll; basically you are telling the system how long you are willing to stall until any request comes ready. The value is not indicative of a maximum timeout on the I/O request; there is none. If you want to have a time limit on each request, you will need to implement your own timer mechanism, and call aio_cancel() to terminate those which haevn't completed. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 11:29:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 7738137B502 for ; Fri, 6 Oct 2000 11:29:26 -0700 (PDT) Received: from bagabeedaboo.security.at12.de (dial-195-14-235-94.netcologne.de [195.14.235.94]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id UAA07203; Fri, 6 Oct 2000 20:29:24 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.11.0/8.11.0) with ESMTP id e96ITCo01732; Fri, 6 Oct 2000 20:29:12 +0200 (CEST) (envelope-from pherman@frenchfries.net) Date: Fri, 6 Oct 2000 20:29:12 +0200 (CEST) From: Paul Herman To: Dan Nelson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fifos over NFS In-Reply-To: <20001006102356.A29878@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Oct 2000, Dan Nelson wrote: > I think that's expected behaviour. Fifos should be usable on NFS > mounts, but an active fifo is only usable for processes running on > the same machine. That's cool, seems reasonable. BTW, the hanging behavior I was seeing didn't have anything to do with NFS -- it was the same if I tried to write to a local fifo with nothing listening on the other side (no NFS). So I guess opening a fifo over NFS doesn't even reach nfs_open() in sys/nfs/nfs_vnops.c which would return an EACCES on a VFIFO. OK, I think I'm satisfied. Thanks! -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 11:34:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E267C37B502 for ; Fri, 6 Oct 2000 11:34:50 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id e96IYnH04108; Fri, 6 Oct 2000 12:34:49 -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 MAA10442; Fri, 6 Oct 2000 12:34:48 -0600 (MDT) Message-Id: <200010061834.MAA10442@harmony.village.org> To: Daniel Lang Subject: Re: Problems with Serial Console Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 06 Oct 2000 09:36:27 -0000." <20001006093627.A17383@atrbg11.informatik.tu-muenchen.de> References: <20001006093627.A17383@atrbg11.informatik.tu-muenchen.de> Date: Fri, 06 Oct 2000 12:34:48 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001006093627.A17383@atrbg11.informatik.tu-muenchen.de> Daniel Lang writes: : Maybe somehow, /dev/console is redirected to /dev/ttyd0 and : so both don't seem to work. Modem control might be enabled when in fact you have no modem control lines connecteD? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 11:40:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id A0EE737B503 for ; Fri, 6 Oct 2000 11:40:20 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.9.3) id e96IeHr19684; Fri, 6 Oct 2000 13:40:17 -0500 (CDT) (envelope-from dan) Date: Fri, 6 Oct 2000 13:40:17 -0500 From: Dan Nelson To: Paul Herman Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fifos over NFS Message-ID: <20001006134017.A13617@dan.emsphone.com> References: <20001006102356.A29878@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: ; from "Paul Herman" on Fri Oct 6 20:29:12 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 06), Paul Herman said: > On Fri, 6 Oct 2000, Dan Nelson wrote: > > I think that's expected behaviour. Fifos should be usable on NFS > > mounts, but an active fifo is only usable for processes running on > > the same machine. > > That's cool, seems reasonable. > > BTW, the hanging behavior I was seeing didn't have anything to do > with NFS -- it was the same if I tried to write to a local fifo with > nothing listening on the other side (no NFS). That's how fifos work; you're blocking on the open, not the write. Open with O_NONBLOCK if you want to the call to fail if there's no-one at the other end. > So I guess opening a fifo over NFS doesn't even reach nfs_open() in > sys/nfs/nfs_vnops.c which would return an EACCES on a VFIFO. OK, I > think I'm satisfied. Thanks! That's probably the case, if you're looking at the server code. If a client ever actually tried to open a fifo over NFS (say they're running an OS that doesn't know about them, like Windows), it'll return the error. My guess is that on the Unix client end, the open request is handled by the kernel and nothing is ever sent to the remote NFS server (just like opening a devicenode). -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 16:51:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id 61C6837B66C for ; Fri, 6 Oct 2000 16:51:14 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e96Nqxh07758; Fri, 6 Oct 2000 16:53:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010062353.e96Nqxh07758@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Motomichi Matsuzaki Cc: hackers@FreeBSD.ORG Subject: Re: PnP resource programming In-reply-to: Your message of "Mon, 18 Sep 2000 04:41:37 +0900." <86em2ihklq.wl@tkc.att.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Oct 2000 16:52:59 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > (Note: Initially pointed out by Hirokazu WATANABE ) ... > According to ISA PnP specifications, > maximum number of memory resource set is 4 and there is only 4 sets of > registers for memory resource programming. > But ISA_NMEM is defined to 8 in sys/isa/isavar.h, > and this code causes unexpected I/O writing. Ack! Thanks for noticing this. I've also run into these limits with the ACPI work. I'll commit a fix shortly. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 17: 9:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 4587837B503 for ; Fri, 6 Oct 2000 17:09:31 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id UAA14613 for ; Fri, 6 Oct 2000 20:04:36 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001006201241.0253e1f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 06 Oct 2000 20:13:42 -0400 To: hackers@freebsd.org From: Dennis Subject: if_fxp question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does the fxp driver in 4.1.1 address the PHY issue with the 82259 Revision 8 parts? The 4.1-RELEASE drivers doesnt. thanks, Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 17:17: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kzsu.stanford.edu (KZSU.Stanford.EDU [171.66.118.90]) by hub.freebsd.org (Postfix) with ESMTP id 472A837B503 for ; Fri, 6 Oct 2000 17:16:59 -0700 (PDT) Received: (from romain@localhost) by kzsu.stanford.edu (8.9.3/8.9.3) id RAA17529 for freebsd-hackers@FreeBSD.ORG; Fri, 6 Oct 2000 17:16:59 -0700 (PDT) (envelope-from romain) Date: Fri, 6 Oct 2000 17:16:59 -0700 (PDT) From: Romain Kang Message-Id: <200010070016.RAA17529@kzsu.stanford.edu> To: rh@matriplex.com Subject: Re: A decent way to get CPU idle time? Reply-To: romain@kzsu.stanford.edu Organization: KZSU 90.1 FM, Stanford, Calif. USA Cc: freebsd-hackers@FreeBSD.ORG X-Newsreader: NN version 6.5.3 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am loathe to call kmem readers clean and decent, but I coincidentally did something similar today, ripping out code from vmstat. See below. It doesn't look difficult to implement a sysctl() interface, but I guess if someone considered the data really important, it would have been done already. IMHO, getloadavg() is flagrantly meaningless. There are plenty of ways to skew the numbers without actually changing CPU activity. Romain Kang Disclaimer: I speak for myself alone, romain@kzsu.stanford.edu except when indicated otherwise. | Is there a clean and decent way to find out the percentage | of CPU idle time, like top and systat give? I have browsed | the source for both, and neither appear to have a simple | way of finding this information. | I have already tried and rejected getloadavg. In my | application, two main processes will always account | for 95% or more of the activity. | I suppose I could use RDTSC to grab the clock on my system | calls, and figure a rudimentary sum of CPU activity, but | that won't help me with the expensive file and socket calls. | And I would pretty much have to guess about the CPU time spent | in the kernel. | Any ideas? Thanks. #include #include #include #include #include #include #include struct nlist namelist[] = { #define X_CPTIME 0 { "_cp_time" }, {""} }; char *nlistf = NULL, *memf = NULL; kvm_t *kd; void kread(); void cpu_init(); void cpu_idle(); main() { cpu_init(); cpu_idle(); } void cpu_init() { int c; static char errbuf[BUFSIZ]; /* * Discard setgid privileges if not the running kernel so that bad * guys can't print interesting stuff from kernel memory. */ if (nlistf != NULL || memf != NULL) setgid(getgid()); kd = kvm_openfiles(nlistf, memf, NULL, O_RDONLY, errbuf); if (kd == 0) errx(1, "kvm_openfiles: %s", errbuf); if ((c = kvm_nlist(kd, namelist)) != 0) { if (c > 0) { warnx("undefined symbols:"); for (c = 0; c < sizeof(namelist)/sizeof(namelist[0]); c++) if (namelist[c].n_type == 0) fprintf(stderr, " %s", namelist[c].n_name); (void)fputc('\n', stderr); } else warnx("kvm_nlist: %s", kvm_geterr(kd)); exit(1); } } void cpu_idle() { register int state; double pct, total; long cp_time[CPUSTATES]; int idle_percent; kread(X_CPTIME, cp_time, sizeof(cp_time)); total = 0; for (state = 0; state < CPUSTATES; ++state) total += cp_time[state]; if (total) pct = 100 / total; else pct = 0; idle_percent = cp_time[CP_IDLE] * pct; printf("idle%%=%d\n", idle_percent); } /* * kread reads something from the kernel, given its nlist index. */ void kread(nlx, addr, size) int nlx; void *addr; size_t size; { char *sym; if (namelist[nlx].n_type == 0 || namelist[nlx].n_value == 0) { sym = namelist[nlx].n_name; if (*sym == '_') ++sym; errx(1, "symbol %s not defined", sym); } if (kvm_read(kd, namelist[nlx].n_value, addr, size) != size) { sym = namelist[nlx].n_name; if (*sym == '_') ++sym; errx(1, "%s: %s", sym, kvm_geterr(kd)); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 6 19:17:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id 1F37737B503 for ; Fri, 6 Oct 2000 19:17:11 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e972H3H35014; Fri, 6 Oct 2000 19:17:04 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010070217.e972H3H35014@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp question In-Reply-To: <5.0.0.25.0.20001006201241.0253e1f0@mail.etinc.com> Date: Fri, 06 Oct 2000 19:17:03 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > does the fxp driver in 4.1.1 address the PHY issue with the 82259 Revision > 8 parts? The 4.1-RELEASE drivers doesnt. Have a look at: http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/if_fxp.c?r1=1.77.2.6&only_with_tag=RELENG_4 See the RELENG_4_1_0_RELEASE and RELENG_4_1_1_RELEASE tag markers and look at the log. You can request a diff between those revisions. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 8:10: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id D023937B502 for ; Sat, 7 Oct 2000 08:10:04 -0700 (PDT) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with ESMTP id LAA16015; Sat, 7 Oct 2000 11:04:37 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20001007111133.01de7dd0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 07 Oct 2000 11:13:30 -0400 To: Peter Wemm From: Dennis Subject: Re: if_fxp question Cc: hackers@freebsd.org In-Reply-To: <200010070217.e972H3H35014@netplex.com.au> References: <5.0.0.25.0.20001006201241.0253e1f0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:17 PM 10/06/2000, you wrote: >Dennis wrote: > > > > does the fxp driver in 4.1.1 address the PHY issue with the 82259 Revision > > 8 parts? The 4.1-RELEASE drivers doesnt. > >Have a look at: > >http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/if_fxp.c?r1=1.77.2.6&only_with_tag=RELENG_4 > Unfortunately the comment don't say what symptoms are corrected by the fix, but my assumption is that the answer to my question is "no".... DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 9: 0:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.tetronsoftware.com (ns1.tetronsoftware.com [64.217.1.41]) by hub.freebsd.org (Postfix) with ESMTP id 889C137B66C for ; Sat, 7 Oct 2000 09:00:13 -0700 (PDT) Received: from ns1.tetronsoftware.com (ns1.tetronsoftware.com [64.217.1.41]) by ns1.tetronsoftware.com (8.11.0/8.9.3) with ESMTP id e97G0B586609 for ; Sat, 7 Oct 2000 11:00:12 -0500 (CDT) (envelope-from zeus@tetronsoftware.com) Date: Sat, 7 Oct 2000 11:00:11 -0500 (CDT) From: Gene Harris To: freebsd-hackers@freebsd.org Subject: Information on make Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder if someone could direct me to some readings on "make"? I have dusted off an ancient FORTRAN program from graduate school (circa 1968). It consists of seven modules and all I want to do is create a make file to compile and link this program. I can successfully compile and link the program manually, but make file syntax escapes me. I have tried the following, but it goes down in flames: ======================= cnindo: coord.o ss.o huckl.o iter.o eign.o matout.o perturb.o *.f: *.o ======================= While I realize this could be done by an experienced person quite easily, I'd rather go learn what I should be doing. Many Thanks, Gene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 9:11:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id AD61837B502 for ; Sat, 7 Oct 2000 09:11:22 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 4A9A2A842; Sun, 8 Oct 2000 03:11:15 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 488CF5457; Sun, 8 Oct 2000 02:11:15 +1000 (EST) Date: Sun, 8 Oct 2000 02:11:15 +1000 (EST) From: andrew@ugh.net.au To: Gene Harris Cc: freebsd-hackers@freebsd.org Subject: Re: Information on make In-Reply-To: Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 7 Oct 2000, Gene Harris wrote: > I wonder if someone could direct me to some readings on "make"? I have dusted /usr/share/doc/psd/12.make Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 11:45:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 13D8137B503 for ; Sat, 7 Oct 2000 11:44:59 -0700 (PDT) Received: (qmail 66632 invoked by uid 1000); 7 Oct 2000 18:44:58 -0000 Date: Sat, 7 Oct 2000 20:44:58 +0200 From: "Karsten W. Rohrbach" To: Sam Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NFSD stopped in inode state Message-ID: <20001007204458.E66128@rohrbach.de> Reply-To: karsten@rohrbach.de References: <20001003181149.A5761@epita.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <20001003181149.A5761@epita.fr>; from sam@epita.fr on Tue, Oct 03, 2000 at 06:11:49PM +0000 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you might want to check your scsi bus layout and cabling and of course termination. maybe one drive has a broken interface? do you get timeouts? /k Sam(sam@epita.fr)@Tue, Oct 03, 2000 at 06:11:49PM +0000: > Hi, > > We have 3 Free BSD 4.0 Servers with Ultra160 Adapatec Cards, and ccd'ed U2W drives. > They each serve about 500 Pcs (NetBSD), using nfs. Most of the use is from students editing and > compiling files. > > They are heavily used all day (and night) long. > > The problem is that some times (1 or 2 times every 24 hours), the nfsd process stop in inode state. > > The Os is still working. i can log on the pc but can't kill the nfsd processes. > > Sometimes the file system which NFS is exported is unavailable, and unmountable. > And we get a fsck of our exported File system. > > > > Her are some of our servers confs: > > ad0: 8223MB [16708/16/63] at ata0-master using UDMA33 > ad2: 19574MB [39770/16/63] at ata1-master using UDMA33 > ad3: 19574MB [39770/16/63] at ata1-slave using UDMA33 > Waiting 15 seconds for SCSI devices to settle > Mounting root from ufs:/dev/ad0s1a > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > > (s3 504)# df -k > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ad0s1a 4961725 255677 4309110 6% / > procfs 4 4 0 100% /proc > /dev/ccd0c 138969382 16752490 111099342 13% /space > /dev/ccd1c 38856354 22757162 12990684 64% /save > > (/space is exported...) > > Thanx for any idea of wath is really happening... > > > Sam > ---- > sam@epita.fr > Admin - Sys > EPITA (Ecole pour l'informatique et les techniques avancees) > Tel: 01 44 08 01 96 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- > "Heimat ist für mich überall dort, wo ein Mensch ist, zu dem ich kommen kann, > ohne gefragt zu werden, weshalb ich da bin, der mir einen Tee anbietet, weil > er weiß, dass ich Tee trinke, und wo ich bei dieser Tasse Tee schweigen darf" > -- Reiner Kunze KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 11:59:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.epita.fr (hermes.epita.fr [194.98.116.10]) by hub.freebsd.org (Postfix) with ESMTP id 4384D37B66D; Sat, 7 Oct 2000 11:59:32 -0700 (PDT) Received: from jotun (IDENT:sam@jotun.epita.fr [10.42.42.66]) by hermes.epita.fr id VAA21223 Sat, 7 Oct 2000 21:00:17 GMT Date: Sat, 7 Oct 2000 21:00:16 +0000 From: Sam To: "Karsten W. Rohrbach" Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: NFSD stopped in inode state Message-ID: <20001007210016.A20673@epita.fr> Reply-To: sam@epita.fr References: <20001003181149.A5761@epita.fr> <20001007204458.E66128@rohrbach.de> 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: <20001007204458.E66128@rohrbach.de>; from karsten@rohrbach.de on Sat, Oct 07, 2000 at 08:44:58PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 07, 2000 at 08:44:58PM +0200, Karsten W. Rohrbach wrote: > Date: Sat, 7 Oct 2000 20:44:58 +0200 > From: "Karsten W. Rohrbach" > To: Sam > Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG > Subject: Re: NFSD stopped in inode state > X-Mailer: Mutt 1.0i > > you might want to check your scsi bus layout and cabling and of course > termination. maybe one drive has a broken interface? > do you get timeouts? > /k I really dont think the probleme comes from the scsi layout since it worked great during last 6 month and started to crash since the load grew.. Anyway we found a way to solve our probleme: we swithed to NetBSD and it works a lot better now. Thanx anyway. > > Sam(sam@epita.fr)@Tue, Oct 03, 2000 at 06:11:49PM +0000: > > Hi, > > > > We have 3 Free BSD 4.0 Servers with Ultra160 Adapatec Cards, and ccd'ed U2W drives. > > They each serve about 500 Pcs (NetBSD), using nfs. Most of the use is from students editing and > > compiling files. > > > > They are heavily used all day (and night) long. > > > > The problem is that some times (1 or 2 times every 24 hours), the nfsd process stop in inode state. > > > > The Os is still working. i can log on the pc but can't kill the nfsd processes. > > > > Sometimes the file system which NFS is exported is unavailable, and unmountable. > > And we get a fsck of our exported File system. > > > > > > > > Her are some of our servers confs: > > > > ad0: 8223MB [16708/16/63] at ata0-master using UDMA33 > > ad2: 19574MB [39770/16/63] at ata1-master using UDMA33 > > ad3: 19574MB [39770/16/63] at ata1-slave using UDMA33 > > Waiting 15 seconds for SCSI devices to settle > > Mounting root from ufs:/dev/ad0s1a > > da0 at ahc0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-3 device > > da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > da0: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > > da1 at ahc0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-3 device > > da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled > > da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) > > > > (s3 504)# df -k > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/ad0s1a 4961725 255677 4309110 6% / > > procfs 4 4 0 100% /proc > > /dev/ccd0c 138969382 16752490 111099342 13% /space > > /dev/ccd1c 38856354 22757162 12990684 64% /save > > > > (/space is exported...) > > > > Thanx for any idea of wath is really happening... > > > > > > Sam > > ---- > > sam@epita.fr > > Admin - Sys > > EPITA (Ecole pour l'informatique et les techniques avancees) > > Tel: 01 44 08 01 96 > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > > "Heimat ist für mich überall dort, wo ein Mensch ist, zu dem ich kommen kann, > > ohne gefragt zu werden, weshalb ich da bin, der mir einen Tee anbietet, weil > > er weiß, dass ich Tee trinke, und wo ich bei dieser Tasse Tee schweigen darf" > > -- Reiner Kunze > KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- ---- sam@epita.fr Admin - Sys EPITA (Ecole pour l'informatique et les techniques avancees) Tel: 01 44 08 01 96 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 13:20: 5 2000 Delivered-To: freebsd-hackers@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 568A037B503 for ; Sat, 7 Oct 2000 13:19:49 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA90054; Sat, 7 Oct 2000 16:19:53 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sat, 7 Oct 2000 16:19:53 -0400 (EDT) From: Adam To: Steve Ames Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IPFW quirk In-Reply-To: <200010060819.e968JLM47254@virtual-voodoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ha! I ran across that unfortunate symptom too and never figured out why it worked for some users and not for others. Thanks! :) I ended up training myself to use ipfw show instead. On Fri, 6 Oct 2000, Steve Ames wrote: > >Hey... I just type 'ipfw -a list' on the command line and got back an >invalid argument error. That confused me for a bit so I poked around >for a while and then it just started working again. A bit more poking >and I discovered that it fails if there is a file called 'list' in >the directory the command is being executed from. > >Seems ipfw checks for a file containing commands before it checks to >see if you've issued a valid command? > >A bit of experimenting ('touch flush', 'ipfw flush') seems to indicate >that its true for most commands. Perhaps this is intentional but its >behavior confused me a bit... And it means I can't leave a file called >'list' laying around as then /etc/security output is wrong. > >-Steve > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 14:27:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.tetronsoftware.com (ns1.tetronsoftware.com [64.217.1.41]) by hub.freebsd.org (Postfix) with ESMTP id 9D39537B66C for ; Sat, 7 Oct 2000 14:27:40 -0700 (PDT) Received: from ns1.tetronsoftware.com (ns1.tetronsoftware.com [64.217.1.41]) by ns1.tetronsoftware.com (8.11.0/8.9.3) with ESMTP id e97LRZw86919; Sat, 7 Oct 2000 16:27:40 -0500 (CDT) (envelope-from zeus@tetronsoftware.com) Date: Sat, 7 Oct 2000 16:27:35 -0500 (CDT) From: Gene Harris To: freebsd-hackers@FreeBSD.ORG Cc: Steve Kargl , andrew@ugh.net.au Subject: Re: Information on make In-Reply-To: <200010071632.e97GWLY04678@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks so much Steve and Andrew and all the others that responded. Andrew's reference to the docs and Steve's example were just the ticket I needed. I have had more fun getting started with this again after 30 years. It's nice to have access to a good quality FORTRAN compiler without having to sell my house and car. My hat is off to the FreeBSD folks and the GNU compiler folks! Thanks, Gene Harris On Sat, 7 Oct 2000, Steve Kargl wrote: > Gene Harris wrote: > > I wonder if someone could direct me to some readings on "make"? I have dusted > > off an ancient FORTRAN program from graduate school (circa 1968). It consists > > of seven modules and all I want to do is create a make file to compile and > > link this program. I can successfully compile and link the program manually, > > but make file syntax escapes me. > > > > I have tried the following, but it goes down in flames: > > > > ======================= > > cnindo: coord.o ss.o huckl.o iter.o eign.o matout.o perturb.o > > > > *.f: *.o > > ======================= > > > > While I realize this could be done by an experienced person quite easily, I'd > > rather go learn what I should be doing. > > > > Many Thanks, > > Gene > > > > > > # > # Replace with an actual tab character. > # > F77=f77 > FFLAGS=-O > OBJS=coord.o ss.o huckl.o iter.o eign.o matout.o perturb.o > > all: cnindo > > cnindo: ${OBJS} > ${F77} -o cnindo ${FFLAGS} ${OBJ$} > > clean: > rm -f ${OBJS} > > .f.o: > ${F77} ${FFLAGS} $< > > -- > Steve > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 17:55:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id 7F8FB37B502 for ; Sat, 7 Oct 2000 17:55:53 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e980tnG08223; Sat, 7 Oct 2000 17:55:49 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200010080055.e980tnG08223@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp question In-Reply-To: <5.0.0.25.0.20001007111133.01de7dd0@mail.etinc.com> Date: Sat, 07 Oct 2000 17:55:49 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > At 10:17 PM 10/06/2000, you wrote: > >Dennis wrote: > > > > > > does the fxp driver in 4.1.1 address the PHY issue with the 82259 Revisio n > > > 8 parts? The 4.1-RELEASE drivers doesnt. > > > >Have a look at: > > > >http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/pci/if_fxp.c?r1=1.77.2.6&only_ with_tag=RELENG_4 > > > > Unfortunately the comment don't say what symptoms are corrected by the fix, > but my assumption is that the answer to my question is "no".... I would have thought that it was obvious. The change between 4.1 and 4.1.1 was to silence a gcc warning. If you need somebody to interpret the fact that the only change was cosmetic, then let me be absolutely clear: NO, NOTHING SIGNIFICANT CHANGED. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 7 19:39:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 09E4337B66E for ; Sat, 7 Oct 2000 19:39:31 -0700 (PDT) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id VAA26076 for hackers@freebsd.org; Sat, 7 Oct 2000 21:39:29 -0500 (CDT) Date: Sat, 7 Oct 2000 21:39:29 -0500 From: "Matthew D. Fuller" To: hackers@freebsd.org Subject: Bugfixes, security fixes, versions Message-ID: <20001007213929.C24996@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The whole "Stable Branch" thread on -security gave me an idea that's been perculating for some time. Problem: We have security problems in (say) -STABLE. They get fixed. We post an advisory about it, giving correction dates for -STABLE and -CURRENT, and the associated cutoff in which releases are fixed and which are not. However, tracking dates on buildworlds etc is hard. I'm sure I'm not the only one who usually does build/installworlds on source at least a week old. I check it it, built it, and if it's clean, wait to see if anyone else has any problems with it. And since I tend to put off building the kernel until I install, the date uname gives isn't necessarily useful for checking this sort of stuff. Idea: In the version string (or maybe somewhere else convenient), start adding codes at each -RELEASE along a branch. So, say we find a bug in fingerd. It's in 4.1-RELEASE, fixed in 4.1-STABLE at some point, and fixed in 4.2-RELEASE. We could add an 'a' to the version string in -STABLE, so it will read out as "4.1-STABLE a". Find another bug and fix it, we have "4.1-STABLE b". Presumably, this would only apply to such things as security holes, and potentially showstopper bugfixes. If we really needed more than 26, we could go to capital letters, or doubled in parenthesis ...xyz(aa)(ab). I somehow doubt that'd be a big problem. Then, the version string could indicate what holes have been caulked up in the system they're running. They could be reset at each -RELEASE, so the advisory can say: 4.1 and below is VULNERABLE 4-STABLE with code 'a' is NOT VULNERABLE 4.2 and above are NOT VULNERABLE I can see a few flaws in this idea, but I figured I'd toss it out and let the wolves tear it to shreds ;) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message