From owner-freebsd-hackers Sun May 14 6:59:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 71F8A37B743 for ; Sun, 14 May 2000 06:59:06 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12qyv6-000Lra-00 for freebsd-hackers@freebsd.org; Sun, 14 May 2000 20:59:00 +0700 Date: Sun, 14 May 2000 20:59:00 +0700 (ALMST) From: Boris Popov To: freebsd-hackers@freebsd.org Subject: Native SMBFS for FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm glad to announce first public release of SMB/CIFS filesystem for FreeBSD. The primary goal is to test compatibilty with various SMB servers. This version should run on FreeBSD-current and 4.0. It will not run on 3.x. I would appreciate any feedback. Please send all comments to bp@butya.kz. Sources can be taken from ftp://ftp.butya.kz/pub/smbfs/smbfs-1.0.2.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 11:49:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 0E4CC37B63F for ; Sun, 14 May 2000 11:49:36 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id OAA27348 for ; Sun, 14 May 2000 14:49:22 -0400 (EDT) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA21076 for ; Sun, 14 May 2000 14:49:34 -0400 (EDT) Received: from rac10.wam.umd.edu (howardjp@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA21071 for ; Sun, 14 May 2000 14:49:33 -0400 (EDT) Message-Id: <200005141849.OAA21071@rac10.wam.umd.edu> X-Authentication-Warning: rac10.wam.umd.edu: howardjp owned process doing -bs To: freebsd-hackers@freebsd.org Subject: mktemp() vs. mkstemp() Date: Sun, 14 May 2000 14:49:28 -0400 From: James Howard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was preparing a port which uses mktemp(). Of course, the linker complained and suggested using mkstemp(). Except mkstemp() returns an integer file descriptor whereas normal people use FILE * pointers, including the author of this port. How about an mkftemp() which wraps around mkstemp() and does an fdopen()? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 12:10:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 5DB1137BE51 for ; Sun, 14 May 2000 12:10:14 -0700 (PDT) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e4EJ9iN09199; Sun, 14 May 2000 13:09:45 -0600 (MDT) Message-Id: <200005141909.e4EJ9iN09199@orthanc.ab.ca> To: James Howard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mktemp() vs. mkstemp() In-reply-to: Your message of "Sun, 14 May 2000 14:49:28 EDT." <200005141849.OAA21071@rac10.wam.umd.edu> Date: Sun, 14 May 2000 13:09:44 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "James" == James Howard writes: James> mkstemp() returns an integer file descriptor whereas normal James> people use FILE * pointers, including the author of this James> port. How about an mkftemp() which wraps around mkstemp() James> and does an fdopen()? Is it that much work to add if ((stream=fdopen(fd, mode)) == NULL) err(...); after a mkstemp call? If you use it that much you can define a function in your application. There's no need to add a non-portable routine to libc for this. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 12:12:41 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 9169037BE4B for ; Sun, 14 May 2000 12:12:33 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA07098; Sun, 14 May 2000 12:12:33 -0700 (PDT) (envelope-from dillon) Date: Sun, 14 May 2000 12:12:33 -0700 (PDT) From: Matthew Dillon Message-Id: <200005141912.MAA07098@apollo.backplane.com> To: freebsd-hackers@freefall.freebsd.org Subject: PR kern/18346 - struct file ref count is a short, can be overflowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PR kern/18346 I would like to bump struct file f_count and f_msgcount from a short to an int, in both 5.x and 4.x, because the program supplied with the PR can demonstratably crash the machine from userland and cause other serious problems, such as file descriptor stealing (what happens when you roll the ref count to 0?). Any objections? Modules that use the struct file directly: (misc in-kernel modules) miscsf/portal miscfs/union miscfs/fdesc miscfs/fifofs netgraph dev/streams linux module Programs: 'pstat' program 'fstat' program -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 12:22:47 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 3BE0A37B63D for ; Sun, 14 May 2000 12:22:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA01177; Sun, 14 May 2000 21:22:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: PR kern/18346 - struct file ref count is a short, can be overflowed In-reply-to: Your message of "Sun, 14 May 2000 12:12:33 PDT." <200005141912.MAA07098@apollo.backplane.com> Date: Sun, 14 May 2000 21:22:03 +0200 Message-ID: <1175.958332123@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200005141912.MAA07098@apollo.backplane.com>, Matthew Dillon writes: > PR kern/18346 > > I would like to bump struct file f_count and f_msgcount from > a short to an int, in both 5.x and 4.x, because the program > supplied with the PR can demonstratably crash the machine from > userland and cause other serious problems, such as file descriptor > stealing (what happens when you roll the ref count to 0?). Any > objections? Agreed. -- 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 Sun May 14 12:45:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 0C47837BD66; Sun, 14 May 2000 12:45:32 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id MAA23400; Sun, 14 May 2000 12:44:01 -0700 (PDT) (envelope-from adsharma) Date: Sun, 14 May 2000 12:44:01 -0700 From: Arun Sharma To: hackers@freebsd.org, freebsd-mozilla@freebsd.org Subject: Can someone comment on this C++ binary compatibility Q ? Message-ID: <20000514124401.A23390@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://bugzilla.mozilla.org/show_bug.cgi?id=33739 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 13:56:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E732837B99E; Sun, 14 May 2000 13:56:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA69938; Sun, 14 May 2000 13:56:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 14 May 2000 13:56:28 -0700 (PDT) From: Kris Kennaway To: James Howard Cc: freebsd-hackers@freebsd.org Subject: Re: mktemp() vs. mkstemp() In-Reply-To: <200005141849.OAA21071@rac10.wam.umd.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 On Sun, 14 May 2000, James Howard wrote: > I was preparing a port which uses mktemp(). Of course, the linker > complained and suggested using mkstemp(). Except mkstemp() returns an > integer file descriptor whereas normal people use FILE * pointers, > including the author of this port. How about an mkftemp() which wraps > around mkstemp() and does an fdopen()? This would be completely non-portable - if you really need this, make one yourself and add it to a library distributed with your code. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 15:26:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id B930037B939 for ; Sun, 14 May 2000 15:26:34 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA09917 for ; Sun, 14 May 2000 15:27:08 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005142227.PAA09917@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: 3ware ATA RAID driver - second Beta released Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 May 2000 15:27:08 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A driver for the 3ware family of ATA RAID controllers is available for FreeBSD-current at http://people.freebsd.org/~msmith/RAID This driver has all basic functionality, but no management at this time. 3ware can be found at http://www.3ware.com. I'd particularly like to thank Janet LeFleur at 3ware for her support in getting hardware for this effort. Comments, feedback, bug reports etc. will all be gratefully received. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 18:23:34 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 3C50D37B66B for ; Sun, 14 May 2000 18:23:32 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.10.0/8.10.0) id e4F1NUd95978 for freebsd-hackers@freebsd.org; Sun, 14 May 2000 20:23:30 -0500 (EST) Date: Sun, 14 May 2000 20:23:30 -0500 (EST) From: Steve Ames Message-Id: <200005150123.e4F1NUd95978@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: can bin/10905 be closed? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone implement the patch from bin/10905? It really does make the output of the 'sa -m' command look much nicer in an environment where your using greater than 8 character usernames... Have been running -CURRENT with that patch for a few days now and no evil side effects :) -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 19:49:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts1-srv.bellnexxia.net (tomts1.bellnexxia.net [209.226.175.139]) by hub.freebsd.org (Postfix) with ESMTP id E66E237B57E; Sun, 14 May 2000 19:49:13 -0700 (PDT) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere ([206.172.76.6]) by tomts1-srv.bellnexxia.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20000515024911.BQKA28912.tomts1-srv.bellnexxia.net@localhost.nowhere>; Sun, 14 May 2000 22:49:11 -0400 Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id WAA14471; Sun, 14 May 2000 22:49:05 -0400 (EDT) (envelope-from tim) Date: Sun, 14 May 2000 22:49:05 -0400 From: Tim Vanderhoek To: Kris Kennaway Cc: James Howard , freebsd-hackers@FreeBSD.org Subject: Re: mktemp() vs. mkstemp() Message-ID: <20000514224905.D14160@mad> References: <200005141849.OAA21071@rac10.wam.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Kris Kennaway on Sun, May 14, 2000 at 01:56:28PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 14, 2000 at 01:56:28PM -0700, Kris Kennaway wrote: > > > integer file descriptor whereas normal people use FILE * pointers, > > including the author of this port. How about an mkftemp() which wraps > > around mkstemp() and does an fdopen()? > > This would be completely non-portable - if you really need this, make one > yourself and add it to a library distributed with your code. It's certainly not like it would be the first non-portable function we've added. Where adding functions to libraries encourages better coding practices, I'm (often) in favour of it, especially if it encourages more secure coding practices. Ultimately everyone benefits, and the pain is short-term. -- Signature withheld by request of author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 20:30: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9567B37B70F; Sun, 14 May 2000 20:29:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA24025; Sun, 14 May 2000 20:29:59 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 14 May 2000 20:29:59 -0700 (PDT) From: Kris Kennaway To: Tim Vanderhoek Cc: James Howard , freebsd-hackers@FreeBSD.org Subject: Re: mktemp() vs. mkstemp() In-Reply-To: <20000514224905.D14160@mad> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 May 2000, Tim Vanderhoek wrote: > It's certainly not like it would be the first non-portable function > we've added. Where adding functions to libraries encourages better > coding practices, I'm (often) in favour of it, especially if it > encourages more secure coding practices. Ultimately everyone > benefits, and the pain is short-term. True, but I'd venture that in most of those cases they did something a little less trivial than one line of code. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 20:46: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1F45637B90B for ; Sun, 14 May 2000 20:46:02 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id XAA69862; Sun, 14 May 2000 23:45:53 -0400 (EDT) Date: Sun, 14 May 2000 23:45:53 -0400 (EDT) From: "Matthew N. Dodd" To: Boris Popov Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Native SMBFS for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 May 2000, Boris Popov wrote: > I'm glad to announce first public release of SMB/CIFS filesystem for > FreeBSD. The primary goal is to test compatibilty with various SMB > servers. This version should run on FreeBSD-current and 4.0. It will > not run on 3.x. Works fine here. Could be a little less vague WRT write errors on a read only share. psvp# cd /mnt psvp# touch foo mb_get_mem(437): incomplete copy touch: foo: RPC struct is bad I'm not sure why it warns about password encryption either since I know it was compiled without it. psvp# mount_smbfs -I 10.0.1.12 //winter@MIHOSHI/D /mnt Warning: no cfg file(s) found. Password: smb_encrypt: password encryption is not available Anyhow, looks pretty good and read performance seems to be acceptable. Good job Boris! -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 20:56:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 3605837B7FE for ; Sun, 14 May 2000 20:55:36 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12rBxs-000N6q-00; Mon, 15 May 2000 10:54:44 +0700 Date: Mon, 15 May 2000 10:54:44 +0700 (ALMST) From: Boris Popov To: "Matthew N. Dodd" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Native SMBFS for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 May 2000, Matthew N. Dodd wrote: > Works fine here. Could be a little less vague WRT write errors on a read > only share. > > psvp# cd /mnt > psvp# touch foo > mb_get_mem(437): incomplete copy > touch: foo: RPC struct is bad Yes, this message looks non-obvious in this case. > Anyhow, looks pretty good and read performance seems to be acceptable. On the 10Mbit network I've got next results on raw read: Samba ~980Kb/s W95 ~700Kb/s W98 ~650Kb/s > Good job Boris! Thanks. P.S. There is some problems with w2000 authentication discovered, so please don't complain :). -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun May 14 23:50:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 55A7E37B5BB for ; Sun, 14 May 2000 23:50:17 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA11105 for ; Sun, 14 May 2000 23:50:51 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005150650.XAA11105@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Subject: 3ware ATA RAID driver updated for -stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 May 2000 23:50:51 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an exercise that was a lot easier than I thought it would be, the 3ware driver is now running on 4-stable. http://people.freebsd.org/~msmith/RAID/3ware/twe-20000515.tar.gz Instructions and code included for both -current and -stable, feedback, suggestions etc. are encouraged as per usual. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 0:11: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gidgate.gid.co.uk (gid.co.uk [194.32.164.225]) by hub.freebsd.org (Postfix) with ESMTP id 7F0CB37B74C for ; Mon, 15 May 2000 00:10:56 -0700 (PDT) (envelope-from rb@gidgate.gid.co.uk) Received: (from rb@localhost) by gidgate.gid.co.uk (8.9.3/8.9.3) id IAA57720; Mon, 15 May 2000 08:10:54 +0100 (BST) (envelope-from rb) Message-Id: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> X-Sender: rbmail@192.168.255.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 15 May 2000 08:09:49 +0100 To: hackers@freebsd.org From: Bob Bishop Subject: Motif goes open source 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 "The Open Group, a vendor and technology-neutral consortium dedicated to enterprise integration, announced today that it is releasing the source code of Motif, using a public license, to the Open Source community." Full details at http://www.opengroup.org/openmotif -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 (0800-1800 UK) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 2: 4:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 12E0F37B74C for ; Mon, 15 May 2000 02:04:18 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12rGnG-000Nkh-00 for freebsd-hackers@freebsd.org; Mon, 15 May 2000 16:04:06 +0700 Date: Mon, 15 May 2000 16:04:06 +0700 (ALMST) From: Boris Popov To: freebsd-hackers@freebsd.org Subject: Re: Native SMBFS for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 May 2000, Boris Popov wrote: > I'm glad to announce first public release of SMB/CIFS filesystem > for FreeBSD. The primary goal is to test compatibilty with various SMB > servers. This version should run on FreeBSD-current and 4.0. It will not > run on 3.x. As always I've made few nasty bugs while merging this version from private tree which causes panics on write. There is also few documentation corrections. An updated version can be taken from: ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz I'm receiving a lot of questions about perfomance, so there is a short list of numbers which I got via 'iozone auto' command (10Mbit network): Win95 machine as server: IOZONE: auto-test mode MB reclen bytes/sec written bytes/sec read 1 512 339791 323416 1 1024 481067 431568 1 2048 648394 588674 1 4096 630130 583555 1 8192 671088 618514 Samba 2.0.6 as server: IOZONE: auto-test mode MB reclen bytes/sec written bytes/sec read 1 512 409200 437191 1 1024 545600 596523 1 2048 729444 798915 1 4096 871543 919299 1 8192 900790 1024562 -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 2:40:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gilgamesch.bik-gmbh.de (T1-Hansenet.BIK-GmbH.de [192.76.134.246]) by hub.freebsd.org (Postfix) with ESMTP id DC60C37B52F for ; Mon, 15 May 2000 02:40:44 -0700 (PDT) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id LAA65954; Mon, 15 May 2000 11:40:02 +0200 (MET DST) Date: Mon, 15 May 2000 11:40:02 +0200 From: Martin Cracauer To: Bob Bishop Cc: hackers@FreeBSD.ORG Subject: Re: Motif goes open source Message-ID: <20000515114002.A64473@cons.org> References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.3.1.2.20000515080753.00abfd70@gid.co.uk>; from rb@gid.co.uk on Mon, May 15, 2000 at 08:09:49AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <4.3.1.2.20000515080753.00abfd70@gid.co.uk>, Bob Bishop wrote: > "The Open Group, a vendor and technology-neutral consortium dedicated to > enterprise integration, announced today that it is releasing the source > code of Motif, using a public license, to the Open Source community." > > Full details at http://www.opengroup.org/openmotif The license seems to make it quite useless. http://www.opengroup.org/openmotif/license/ "Free for use on Operating Systems that are themself Open Source" (note the blank), otherwise with something like a GPL virus, but incompatible with the GPL. As it is not an essential system library, you may not link GPL programs to it. As the point about FreeBSD is that you can make it non-OpenSource at will, no essential system parts of FreeBSD may be linked to it. On the positive side, it seems to allow redistribution in modified form and as such is not as stupid as Sun's "Community" license. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 2:49:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id E7BC137B7E7 for ; Mon, 15 May 2000 02:49:10 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id LAA24298; Mon, 15 May 2000 11:49:03 +0200 (CEST) Date: Mon, 15 May 2000 11:49:02 +0200 From: Martin Cracauer To: Bob Bishop Cc: hackers@FreeBSD.ORG Subject: Re: Motif goes open source Message-ID: <20000515114902.A24268@cons.org> References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <20000515114002.A64473@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000515114002.A64473@cons.org>; from cracauer@cons.org on Mon, May 15, 2000 at 11:40:02AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000515114002.A64473@cons.org>, Martin Cracauer wrote: > In <4.3.1.2.20000515080753.00abfd70@gid.co.uk>, Bob Bishop wrote: > > "The Open Group, a vendor and technology-neutral consortium dedicated to > > enterprise integration, announced today that it is releasing the source > > code of Motif, using a public license, to the Open Source community." > > > > Full details at http://www.opengroup.org/openmotif > > The license seems to make it quite useless. > http://www.opengroup.org/openmotif/license/ > > "Free for use on Operating Systems that are themself Open Source" > (note the blank), otherwise with something like a GPL virus, Ops, sorry, I was mislead. They use the term "Program" for the Motif library, not the application you link to. So it does not infect your own code that uses this library, you just have to ship source for your modifications to the Motif library. Still, it is of course vastly incomatible to the GPL. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 4: 9:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E792D37B697 for ; Mon, 15 May 2000 04:09:21 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id UAA13659; Mon, 15 May 2000 20:09:01 +0900 (JST) Message-ID: <391FDB25.D7FB808F@newsguy.com> Date: Mon, 15 May 2000 20:10:29 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Martin Cracauer Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: Motif goes open source References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <20000515114002.A64473@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > > In <4.3.1.2.20000515080753.00abfd70@gid.co.uk>, Bob Bishop wrote: > > "The Open Group, a vendor and technology-neutral consortium dedicated to > > enterprise integration, announced today that it is releasing the source > > code of Motif, using a public license, to the Open Source community." > > > > Full details at http://www.opengroup.org/openmotif > > The license seems to make it quite useless. > http://www.opengroup.org/openmotif/license/ Huh? The license makes it quite useful, IMHO. > "Free for use on Operating Systems that are themself Open Source" > (note the blank), otherwise with something like a GPL virus, but (blank? what blank?) > incompatible with the GPL. As it is not an essential system library, > you may not link GPL programs to it. As the point about FreeBSD is That's because GPL is brain-damaged. It is, essentially, incompatible with anything but GPL. Even the BSD license had to have a clause removed (and I'm still doubtful if this makes it "compatible" with GPL). > that you can make it non-OpenSource at will, no essential system parts > of FreeBSD may be linked to it. We do have a lot of GPLed code in the system, which cannot be made non-OpenSource. Anyway, the license does not contaminate linked programs. It says so explicitly. In this respect, it is much better than GPL. Also, since X is a separate component, it would be no burden to distribute it with the system. Honestly, I don't know of a single BSD-based solution out there that would have had the least trouble had Motif with the above license been distributed with FreeBSD. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@tutti.capi.bsdconspiracy.org "I agree whole heartily! Who am I to disagree with a wacko like you?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 4:15: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1FE5C37B7E1 for ; Mon, 15 May 2000 04:14:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id NAA04703; Mon, 15 May 2000 13:13:23 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel C. Sobral" Cc: Martin Cracauer , Bob Bishop , hackers@FreeBSD.ORG Subject: Re: Motif goes open source In-reply-to: Your message of "Mon, 15 May 2000 20:10:29 +0900." <391FDB25.D7FB808F@newsguy.com> Date: Mon, 15 May 2000 13:13:22 +0200 Message-ID: <4701.958389202@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <391FDB25.D7FB808F@newsguy.com>, "Daniel C. Sobral" writes: >Martin Cracauer wrote: >> >> In <4.3.1.2.20000515080753.00abfd70@gid.co.uk>, Bob Bishop wrote: >> > "The Open Group, a vendor and technology-neutral consortium dedicated to >> > enterprise integration, announced today that it is releasing the source >> > code of Motif, using a public license, to the Open Source community." >> > >> > Full details at http://www.opengroup.org/openmotif >> >> The license seems to make it quite useless. >> http://www.opengroup.org/openmotif/license/ > >Huh? The license makes it quite useful, IMHO. I think so too. Since X11 is an optional (3rd party even) component of FreeBSD, the license on Motif is not really a big issue: it will always be a port in FreeBSD, it will not be part of the base system. We have other ports with far weirder licenses. Only too bad it took them 10 years to realize what the key to a success in the UNIX world is :-( -- 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 May 15 4:22:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (Postfix) with ESMTP id 4842537B5B5 for ; Mon, 15 May 2000 04:22:12 -0700 (PDT) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id NAA25432; Mon, 15 May 2000 13:21:48 +0200 (CEST) Date: Mon, 15 May 2000 13:21:47 +0200 From: Martin Cracauer To: "Daniel C. Sobral" Cc: Martin Cracauer , Bob Bishop , hackers@FreeBSD.ORG Subject: Re: Motif goes open source Message-ID: <20000515132147.B24644@cons.org> References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <20000515114002.A64473@cons.org> <391FDB25.D7FB808F@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <391FDB25.D7FB808F@newsguy.com>; from dcs@newsguy.com on Mon, May 15, 2000 at 08:10:29PM +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <391FDB25.D7FB808F@newsguy.com>, Daniel C. Sobral wrote: > Martin Cracauer wrote: > > > > In <4.3.1.2.20000515080753.00abfd70@gid.co.uk>, Bob Bishop wrote: > > > "The Open Group, a vendor and technology-neutral consortium dedicated to > > > enterprise integration, announced today that it is releasing the source > > > code of Motif, using a public license, to the Open Source community." > > > > > > Full details at http://www.opengroup.org/openmotif > > > > The license seems to make it quite useless. > > http://www.opengroup.org/openmotif/license/ > > Huh? The license makes it quite useful, IMHO. I already corrected this point. > > "Free for use on Operating Systems that are themself Open Source" > > (note the blank), otherwise with something like a GPL virus, but > > (blank? what blank?) "OpenSource" (without blank) is the term. "Open Source" is like "Free BSD", suit-wearers language showing the unfamilarness with the subject. > > incompatible with the GPL. As it is not an essential system library, > > you may not link GPL programs to it. As the point about FreeBSD is > > That's because GPL is brain-damaged. It is, essentially, incompatible > with anything but GPL. Even the BSD license had to have a clause removed > (and I'm still doubtful if this makes it "compatible" with GPL). I know. http://www.cons.org/cracauer/gpl.html It's an important thing to notice, as no GPL desktop stuff can be built upon it. > > that you can make it non-OpenSource at will, no essential system parts > > of FreeBSD may be linked to it. > > We do have a lot of GPLed code in the system, which cannot be made > non-OpenSource. As I said, I had to correct the point, I was mislead by their term "program" and thought it infected applications using it. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 4:27:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7EF3E37B50C for ; Mon, 15 May 2000 04:27:12 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id UAA18745; Mon, 15 May 2000 20:26:59 +0900 (JST) Message-ID: <391FDF5C.5473F95B@newsguy.com> Date: Mon, 15 May 2000 20:28:28 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Martin Cracauer Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: Motif goes open source References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <20000515114002.A64473@cons.org> <391FDB25.D7FB808F@newsguy.com> <20000515132147.B24644@cons.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Cracauer wrote: > > "OpenSource" (without blank) is the term. "Open Source" is like > "Free BSD", suit-wearers language showing the unfamilarness with the > subject. Really? I have always used (and have no plans to change) "Open Source". I see no point at all in making it a single word. Alas, they use a definition of their own, to suit their needs instead of the political agenda of RMS. > > That's because GPL is brain-damaged. It is, essentially, incompatible > > with anything but GPL. Even the BSD license had to have a clause removed > > (and I'm still doubtful if this makes it "compatible" with GPL). > > I know. http://www.cons.org/cracauer/gpl.html > > It's an important thing to notice, as no GPL desktop stuff can be > built upon it. Hurray! :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@tutti.capi.bsdconspiracy.org "I agree whole heartily! Who am I to disagree with a wacko like you?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 8: 0:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from trauco.colomsat.net.co (trauco.colomsat.net.co [200.13.195.2]) by hub.freebsd.org (Postfix) with ESMTP id CBBB937B71E; Mon, 15 May 2000 07:59:51 -0700 (PDT) (envelope-from y-carden@uniandes.edu.co) Received: from uniandes.edu.co (200.13.193.242) by trauco.colomsat.net.co (NPlex 4.0.068) id 391DB93A00004467; Mon, 15 May 2000 09:56:33 -0500 Message-ID: <39201144.945A05C@uniandes.edu.co> Date: Mon, 15 May 2000 10:01:24 -0500 From: Yonny Cardenas Reply-To: ycardena@yahoo.com X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Cc: freebsd-net@freebsd.org Subject: Late binding between layers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello The network software is commonly layered into hierarchy of protocols, for example the TCP/IP implementation. The FreeBSD kernel support a late binding between layers? How ? Thanks. +--------------------------------+ YONNY CARDENAS B. Systems Engineer UNIX is BSD, and FreeBSD is an advanced 4.4BSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 8:16:52 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 B2A6237BA1E for ; Mon, 15 May 2000 08:16:48 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id LAA20258; Mon, 15 May 2000 11:14:19 -0400 (EDT) Message-Id: <200005151514.LAA20258@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 15 May 2000 11:13:29 -0400 To: Poul-Henning Kamp , "Daniel C. Sobral" From: Dennis Subject: Re: Motif goes open source Cc: Martin Cracauer , Bob Bishop , hackers@FreeBSD.ORG In-Reply-To: <4701.958389202@critter.freebsd.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:13 PM 5/15/00 +0200, Poul-Henning Kamp wrote: >Since X11 is an optional (3rd party even) component of FreeBSD, >the license on Motif is not really a big issue: it will always be >a port in FreeBSD, it will not be part of the base system. > >We have other ports with far weirder licenses. > >Only too bad it took them 10 years to realize what the key to a >success in the UNIX world is :-( That is, if your definition of "success" is wide-spread use rather than profits.... I think that Sun and Oracle are doing rather well. DB Emerging Technologies, Inc. ---------------------------------------------------------------------------- --------- http://www.etinc.com ISA and PCI T1/T3/V35/HSSI Cards for FreeBSD and LINUX Multiport T1 and HSSI/T3 UNIX-based Routers Bandwidth Management Standalone Systems Bandwidth Management software for LINUX and FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 8:33:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id EF77137B766 for ; Mon, 15 May 2000 08:33:43 -0700 (PDT) (envelope-from mbac@nyct.net) Received: from bsd1.nyct.net (root@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.9.3/8.8.7) with ESMTP id LAA73516; Mon, 15 May 2000 11:33:54 -0400 (EDT) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.9.3/8.9.3) with ESMTP id LAA54553; Mon, 15 May 2000 11:33:58 -0400 (EDT) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Mon, 15 May 2000 11:33:58 -0400 (EDT) From: Michael Bacarella To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: Motif goes open source In-Reply-To: <391FDF5C.5473F95B@newsguy.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, 15 May 2000, Daniel C. Sobral wrote: > Martin Cracauer wrote: > > > > "OpenSource" (without blank) is the term. "Open Source" is like > > "Free BSD", suit-wearers language showing the unfamilarness with the > > subject. > > Really? I have always used (and have no plans to change) "Open Source". > I see no point at all in making it a single word. Alas, they use a > definition of their own, to suit their needs instead of the political > agenda of RMS. RMS's politcal agendas do not include the term 'Open Source'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 11:38:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 866DB37B75D; Mon, 15 May 2000 11:38:23 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (ip43.salt-lake-city6.ut.pub-ip.psi.net [38.27.95.43]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id MAA08536; Mon, 15 May 2000 12:38:08 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39204472.706CB1D2@softweyr.com> Date: Mon, 15 May 2000 12:39:46 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Tim Vanderhoek , James Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: mktemp() vs. mkstemp() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sun, 14 May 2000, Tim Vanderhoek wrote: > > > It's certainly not like it would be the first non-portable function > > we've added. Where adding functions to libraries encourages better > > coding practices, I'm (often) in favour of it, especially if it > > encourages more secure coding practices. Ultimately everyone > > benefits, and the pain is short-term. > > True, but I'd venture that in most of those cases they did something a > little less trivial than one line of code. We could simply redefine mktemp to not be such a security hole. Do common programs that use mktemp depend on side effects? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 11:40:29 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 324B137B73D for ; Mon, 15 May 2000 11:40:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA76559 for ; Mon, 15 May 2000 12:40:17 -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 MAA38849 for ; Mon, 15 May 2000 12:39:39 -0600 (MDT) Message-Id: <200005151839.MAA38849@harmony.village.org> To: hackers@freebsd.org Subject: PR closing stats Date: Mon, 15 May 2000 12:39:39 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there some place where a summary of those that have closed PRs can be found? I'd like to see how many I've closed in the last year to know if I should feel guilt or not :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 12: 0:36 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 6ACCC37B6A1; Mon, 15 May 2000 12:00:31 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4FJWvt04153; Mon, 15 May 2000 12:32:57 -0700 (PDT) Date: Mon, 15 May 2000 12:32:57 -0700 From: Alfred Perlstein To: Wes Peters Cc: Kris Kennaway , Tim Vanderhoek , James Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: mktemp() vs. mkstemp() Message-ID: <20000515123256.C249@fw.wintelcom.net> References: <39204472.706CB1D2@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39204472.706CB1D2@softweyr.com>; from wes@softweyr.com on Mon, May 15, 2000 at 12:39:46PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Wes Peters [000515 12:11] wrote: > Kris Kennaway wrote: > > > > On Sun, 14 May 2000, Tim Vanderhoek wrote: > > > > > It's certainly not like it would be the first non-portable function > > > we've added. Where adding functions to libraries encourages better > > > coding practices, I'm (often) in favour of it, especially if it > > > encourages more secure coding practices. Ultimately everyone > > > benefits, and the pain is short-term. > > > > True, but I'd venture that in most of those cases they did something a > > little less trivial than one line of code. > > We could simply redefine mktemp to not be such a security hole. Do > common programs that use mktemp depend on side effects? The side effect they depend on is that the char * returned is unique, but since no file was created it's not garanteed so. You can't fix it. -- -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 Mon May 15 12:19:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news1.newsindex.com (news1.newsindex.com [209.166.166.118]) by hub.freebsd.org (Postfix) with ESMTP id D4B5137B643 for ; Mon, 15 May 2000 12:18:59 -0700 (PDT) (envelope-from speck@news1.newsindex.com) Received: from localhost (speck@localhost) by news1.newsindex.com (8.8.5/8.8.5) with SMTP id PAA15955 for ; Mon, 15 May 2000 15:41:06 -0400 (EDT) Date: Mon, 15 May 2000 15:41:05 -0400 (EDT) From: Sean Peck To: freebsd-hackers@freebsd.org Subject: Apache in FreeBSD 3.3 precompiled with DSO? 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 Is the Apache distributed in 3.3 compiled with DSO? Sean Peck News Index -- The original News Only Search Engine. http://www.newsindex.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 12:21:36 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 C480837B843 for ; Mon, 15 May 2000 12:21:31 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA76781; Mon, 15 May 2000 13:21:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA39122; Mon, 15 May 2000 13:20:51 -0600 (MDT) Message-Id: <200005151920.NAA39122@harmony.village.org> To: Wes Peters Subject: Re: mktemp() vs. mkstemp() Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 15 May 2000 12:39:46 MDT." <39204472.706CB1D2@softweyr.com> References: <39204472.706CB1D2@softweyr.com> Date: Mon, 15 May 2000 13:20:51 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39204472.706CB1D2@softweyr.com> Wes Peters writes: : We could simply redefine mktemp to not be such a security hole. Do : common programs that use mktemp depend on side effects? mktemp cannot be defined such that it isn't a security hole. That's why mkstemp was invented. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 12:50:13 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 0CF2737B578 for ; Mon, 15 May 2000 12:50:09 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA76877; Mon, 15 May 2000 13:50:07 -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 NAA39337; Mon, 15 May 2000 13:49:29 -0600 (MDT) Message-Id: <200005151949.NAA39337@harmony.village.org> To: Bob Bishop Subject: Re: Motif goes open source Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 15 May 2000 08:09:49 BST." <4.3.1.2.20000515080753.00abfd70@gid.co.uk> References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> Date: Mon, 15 May 2000 13:49:29 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.3.1.2.20000515080753.00abfd70@gid.co.uk> Bob Bishop writes: : "The Open Group, a vendor and technology-neutral consortium dedicated to : enterprise integration, announced today that it is releasing the source : code of Motif, using a public license, to the Open Source community." : : Full details at http://www.opengroup.org/openmotif Cool. I have an "in" at ICS who is sending me a cdrom with the sources on it. The servers are slash dotted back into the stone age at this time. This should also make it easier for use to integrate patches in the future since he's a good guy who I worked with back in the OI/uib ObejctBuilder days. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 12:55:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id BC03837B578 for ; Mon, 15 May 2000 12:55:18 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA08455 for ; Mon, 15 May 2000 15:54:57 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA03473 for ; Mon, 15 May 2000 15:55:16 -0400 (EDT) Received: from rac1.wam.umd.edu (howardjp@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA03468 for ; Mon, 15 May 2000 15:55:14 -0400 (EDT) Message-Id: <200005151955.PAA03468@rac1.wam.umd.edu> X-Authentication-Warning: rac1.wam.umd.edu: howardjp owned process doing -bs To: freebsd-hackers@freebsd.org Subject: utmpx, this is gonna hurt... Date: Mon, 15 May 2000 15:55:13 -0400 From: James Howard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How about adding the utmpx as required by SUSV2? It would make writing programs that need to talk to utmp/utmpx a lot simpler. Yes? No? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 12:57:26 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 E287D37B578 for ; Mon, 15 May 2000 12:57:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA76924 for ; Mon, 15 May 2000 13:57:21 -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 NAA39443 for ; Mon, 15 May 2000 13:56:43 -0600 (MDT) Message-Id: <200005151956.NAA39443@harmony.village.org> To: hackers@freebsd.org Subject: CVS question Date: Mon, 15 May 2000 13:56:43 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a CVS question. Normally I wouldn't bother the nice folks here with it, but since it involves backmigrating the local changes Timing Solutions has made to FreeBSD, I thought that others might find its answer useful in the future. We have a CVS repo that we import the FreeBSD sources into from time to time. All FreeBSD sources are kept on a repo branch. This is a big pita because files come and go in FreeBSD all the time, but we have that problem licked. What we don't have licked is the ability to generate diffs easily. One would think that a simple cvs diff -u -rFREEBSD -rHEAD would do the trick. However, it comes up with lots and lots and lots of output because the deleted files somehow still exist on the FREEBSD vendor branch. Some of the changes that we've made won't be merged into FreeBSD as they are rather hackish in nature (an option to make ppb use fast interrupts so that pps has less noise in its measurements is one example). Most of them will. As they migrate back into FreeBSD, we also need to put them back on the vendor branch, which I've done in the past by doing an import and changing the branch rev from 1 to 1.1.1 with cvs admin, so that's covered. Other than using perforce, can anybody recomment a good way to manage this situation? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 13:26:54 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 6CC9437B6A0 for ; Mon, 15 May 2000 13:26:52 -0700 (PDT) (envelope-from chris@holly.calldei.com) Received: from holly.calldei.com ([208.191.155.7]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FUM00FQLBG31M@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Mon, 15 May 2000 15:26:28 -0500 (CDT) Received: (from chris@localhost) by holly.calldei.com (8.9.3/8.9.3) id PAA39954; Mon, 15 May 2000 15:26:11 -0500 (CDT envelope-from chris) Date: Mon, 15 May 2000 15:26:10 -0500 From: Chris Costello Subject: Re: utmpx, this is gonna hurt... In-reply-to: <200005151955.PAA03468@rac1.wam.umd.edu> To: James Howard Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <20000515152610.D35004@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i References: <200005151955.PAA03468@rac1.wam.umd.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, May 15, 2000, James Howard wrote: > How about adding the utmpx as required by SUSV2? It would make writing > programs that need to talk to utmp/utmpx a lot simpler. Yes? No? I agree that this would be a good idea. -- |Chris Costello |Performance proven: It works through beta test. `----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 14: 6: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EA0C37B81C for ; Mon, 15 May 2000 14:05:58 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id WAA18721; Mon, 15 May 2000 22:05:49 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id VAA92912; Mon, 15 May 2000 21:40:03 +0100 (BST) (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <200005151949.NAA39337@harmony.village.org> References: Your message of "Mon, 15 May 2000 08:09:49 BST." <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <4.3.1.2.20000515080753.00abfd70@gid.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 15 May 2000 21:40:03 +0100 To: Warner Losh From: Bob Bishop Subject: Re: Motif goes open source Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >Cool. I have an "in" at ICS who is sending me a cdrom with the >sources on it. The servers are slash dotted back into the stone age >at this time. This should also make it easier for use to integrate >patches in the future since he's a good guy who I worked with back in >the OI/uib ObejctBuilder days. We live in the same offices as IST, who use FreeBSD extensively in-house. I hope you'll find us being quite helpful too :-) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 15: 7:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from front001.cluster1.charter.net (24-216-159-200.hsacorp.net [24.216.159.200]) by hub.freebsd.org (Postfix) with ESMTP id 181D537B89D for ; Mon, 15 May 2000 15:07:27 -0700 (PDT) (envelope-from sstephenson@charter.net) Received: from [24.216.21.76] (HELO thanatos) by front001.cluster1.charter.net (CommuniGate Pro SMTP 3.2.4) with SMTP id 8336289; Mon, 15 May 2000 18:07:25 -0400 Message-ID: <001e01bfbeba$370c2300$0200000a@grapevine.local> From: "Sam Stephenson" To: , "Bob Bishop" References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> Subject: Re: Motif goes open source Date: Mon, 15 May 2000 18:09:18 -0400 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.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, May 15, 2000 at 03:09a, Bob Bishop wrote: > "The Open Group, a vendor and technology-neutral consortium dedicated to > enterprise integration, announced today that it is releasing the source > code of Motif, using a public license, to the Open Source community." > > Full details at http://www.opengroup.org/openmotif > Check out the web page: "We want to support the momentum of Open Source operating systems such as Linux(R) and FreeBSD by developing an Open Motif(R)..." and "UNIX and Motif are registered trademarks of The Open Group in the US and other countries. The Open Group and the X Window System are trademarks of The Open Group. Linux is a registered trademark of Linus Torvalds." Correct me if I'm wrong, but I do believe FreeBSD is a registered trademark of some organization -- FreeBSD, Inc., Walnut Creek, or BSDI. Someone should politely inform The Open Group of FreeBSD's trademark status. -- Sam Stephenson sstephenson@charter.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 17:38:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 2643F37B945 for ; Mon, 15 May 2000 17:38:47 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e4G0cjK63600; Mon, 15 May 2000 17:38:45 -0700 (PDT) Date: Mon, 15 May 2000 17:38:45 -0700 (PDT) From: Doug White To: James Howard Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: utmpx, this is gonna hurt... In-Reply-To: <200005151955.PAA03468@rac1.wam.umd.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 On Mon, 15 May 2000, James Howard wrote: > How about adding the utmpx as required by SUSV2? It would make writing > programs that need to talk to utmp/utmpx a lot simpler. Yes? No? As usual, patches speak louder than words :) 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 Mon May 15 17:54:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 3420E37B6A0 for ; Mon, 15 May 2000 17:54:29 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA67632 for ; Mon, 15 May 2000 20:54:03 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Mon, 15 May 2000 20:54:03 -0400 (EDT) From: Chuck Robey To: FreeBSD Hackers List Subject: Gnu xgcc or as 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 wondering if anyone knows the build process for either gcc or the as part of binutils well enough to tell me ... I've noticed, for the produced binary for either gcc or as (the one for gcc is xgcc), when you try to invoke them directly, for testing, they only preprocess their input, then put the result out to stdout (even if you use a -o flag). They won't produce object files. Howcome? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 19:15: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id CA36C37B91C for ; Mon, 15 May 2000 19:15:03 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA271786; Mon, 15 May 2000 22:14:58 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200005151956.NAA39443@harmony.village.org> References: <200005151956.NAA39443@harmony.village.org> Date: Mon, 15 May 2000 22:14:50 -0400 To: Warner Losh , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: CVS question Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:56 PM -0600 5/15/00, Warner Losh wrote: >I have a CVS question. Normally I wouldn't bother the nice folks here >with it, but since it involves backmigrating the local changes Timing >Solutions has made to FreeBSD, I thought that others might find its >answer useful in the future. I would be interested, for one... :-) >We have a CVS repo that we import the FreeBSD sources into from time >to time. All FreeBSD sources are kept on a repo branch. [...] > >Some of the changes that we've made won't be merged into FreeBSD as >they are rather hackish in nature [...]. Most of them will. As they >migrate back into FreeBSD, we also need to put them back on the vendor >branch, which I've done in the past by doing an import and changing >the branch rev from 1 to 1.1.1 with cvs admin, so that's covered. > >Other than using perforce, can anybody recomment a good way to manage >this situation? Somewhere recently I was reading about an alternate version of cvs which had the idea of cvs repository hierarchies. I *think* it was 'rcvs' (Renegade CVS) which I tripped over at sourceforge, but when I went back to read more on it I couldn't find whatever writeup I had remembered. Since I only read one time, I may have some details mixed up. It was something like you check out a local repository from the main repository. The local developers check things in-and-out of the local repository, and when everyone's happy with it you can 'commit' changes from the local repository back into the repository it came from. I think this 'commit' step required that the local repository included all changes already in it's parent repository, so any conflicts between repository's had to be resolved at the local repository. I don't know if that was actually implemented, or just a blue-sky idea of something they hoped to do. I do know I'd like to do something pretty similar to what you're talking about, and would like to have a good way to keep track of all the pieces. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon May 15 22:25:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 04DE537BA16 for ; Mon, 15 May 2000 22:25:16 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from bone.nectar.com (bone.nectar.com [10.0.1.105]) by gw.nectar.com (Postfix) with ESMTP id C4D169B10 for ; Tue, 16 May 2000 00:25:14 -0500 (CDT) Received: by bone.nectar.com (Postfix, from userid 1001) id F358B1DA2; Tue, 16 May 2000 00:25:13 -0500 (CDT) Date: Tue, 16 May 2000 00:25:13 -0500 From: "Jacques A . Vidrine" To: freebsd-hackers@freebsd.org Subject: need to borrow a clue re: rtld Message-ID: <20000516002513.A65118@bone.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.2i X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Messing about with Dante (the SOCKS5 replacement), I've encountered some difficulty with run-time linking that I don't understand. In brief: $ env LD_PRELOAD=libdsocks.so telnet # works $ env LD_PRELOAD=libdsocks.so xchat # undefined symbol '_gethostbyname' $ env LD_PRELOAD=libc.so:libdsocks.so xchat # works What I don't understand is: = Why is the run-time linker failing to find _gethostbyname in libc in the second case? Looking at a ktrace shows that the relative order of loading libdsocks.so and libc.so is the same for both telnet and xchat, but the latter `doesn't work'. I thought LD_BIND_NOW might be useful here, but it isn't. The same problem is encountered even if the application is linked (dynamically) with -ldsocks at build time (i.e. undefined symbol unless I supply LD_PRELOAD=libc.so). What might I look for in the build of libdsocks.so that would cause such? Thanks for any help! -- Jacques Vidrine / n@nectar.com / 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 Mon May 15 23:48: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id C187D37B553 for ; Mon, 15 May 2000 23:48:03 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JPGMYOG65K0002CG@research.kpn.com> for hackers@FreeBSD.ORG; Tue, 16 May 2000 08:48:01 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 16 May 2000 08:47:58 +0100 Content-return: allowed Date: Tue, 16 May 2000 08:47:54 +0100 From: "Koster, K.J." Subject: Can we use this for the JDK? (was: Motif goes open source) To: hackers@FreeBSD.ORG Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D7520@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all, Is there someone on this list who's into the finer points of copyrighting? I would like to know what the implications are of this for the soon-to-be-coming native FreeBSD JDK port. In what form is Motif going to be available to the general FreeBSD developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or is this going to be more complicated than that? In what form would we have to distribute this with our JDK port (Java/SCCL-legalities aside)? Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 0: 8:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id AB63A37B968 for ; Tue, 16 May 2000 00:08:36 -0700 (PDT) (envelope-from jhix@mindspring.com) Received: from mindspring.com (user-33qtilv.dialup.mindspring.com [199.174.202.191]) by maynard.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id DAA19242 for ; Tue, 16 May 2000 03:08:32 -0400 (EDT) Message-ID: <3920F59C.E6EEDF42@mindspring.com> Date: Tue, 16 May 2000 00:15:40 -0700 From: W Gerald Hicks X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: Can we use this for the JDK? (was: Motif goes open source) References: <59063B5B4D98D311BC0D0001FA7E4522026D7520@l04.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Koster, K.J." wrote: > > Dear all, > > Is there someone on this list who's into the finer points of copyrighting? I > would like to know what the implications are of this for the > soon-to-be-coming native FreeBSD JDK port. > > In what form is Motif going to be available to the general FreeBSD > developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or > is this going to be more complicated than that? > As Poul-Henning Kamp noted earlier we have licenses in the ports tree that are *much* stranger than this one. I'd be very surprised if we don't see an entry in ports/x11-toolkits for Motif sometime soon. I'd also be very interested in what the "Hungry Programmers" have to say about this new development. All in all, I think this was a good day for open-source software. :-) Cheers, Jerry Hicks jhix@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 0:21:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from xenocex.com (europa.your-site.com [140.186.45.2]) by hub.freebsd.org (Postfix) with SMTP id A1FDE37BA50 for ; Tue, 16 May 2000 00:21:17 -0700 (PDT) (envelope-from derick@xenocex.com) Received: from xenom ([209.179.56.66]) by xenocex.com ; Tue, 16 May 2000 03:21:35 -0400 Message-ID: <000001bfbf07$4d5733a0$8401a8c0@earthlink.net> From: "Derick Fernando" To: Subject: Com Port Issue Date: Tue, 16 May 2000 00:19:25 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I wrote a samll program to get weather from a Davis Net weather station attached to a com port (/dev/cuaa0) in this case. It worked on Linux and IRIX, I am wondering why it compiles and runs, but does not get any data back from the device in FreeBSD. A minimal program that just listens for a ACK (\006) from the station can be seen at http://east.dhs.org/test11.c If you know someone that could help me resolve this issue, please let me know. Thanks. Derick J. Fernano To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 2: 1:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id A5D9037B946 for ; Tue, 16 May 2000 02:01:08 -0700 (PDT) (envelope-from arjan@jak.nl) Received: from jaknl by athos.nl.uu.net with UUCP id ; Tue, 16 May 2000 11:00:54 +0200 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id LAA17804 for ; Tue, 16 May 2000 11:06:06 +0200 (CEST) (envelope-from arjan@jak.nl) Message-ID: <39210E15.D3D2F278@jak.nl> Date: Tue, 16 May 2000 11:00:05 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers FreeBSD Subject: Cyclades Cyclom YeP PCI problem Content-Type: multipart/mixed; boundary="------------21C2A32D3287C8994634F562" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------21C2A32D3287C8994634F562 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I have two cyclom YeP PCI board installed with 32 serials ports connected to both on a FreeBSD 4.0 release system. The first board (cy0) is working without problems however the second one (cy1) give some trouble. When I try to connect to a port e.g. cuac10 - cuac1v a kernel warning is displayed: 'WARNING: driver cy should register devices with make_dev () (dev_t = "cy/0x1008f")' but the connected is made. I added some 'printf ()'s to the 'cy.c' file in the 'cyattach_common ()' to verify whether 'make_dev ()' is called for the relevant ports and that seems to be OK. So my question is what wrong here? Can someone give a hint? Thanks, Arjan Knepper --------------21C2A32D3287C8994634F562 Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------21C2A32D3287C8994634F562-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 2:56:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 7D24D37B8A3 for ; Tue, 16 May 2000 02:56:46 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JPGTJLU5060002BC@research.kpn.com> for freebsd-hackers@freebsd.org; Tue, 16 May 2000 11:56:42 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 16 May 2000 11:56:37 +0100 Content-return: allowed Date: Tue, 16 May 2000 11:56:29 +0100 From: "Koster, K.J." Subject: Motif porting discussions on -java To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D752B@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to let the non-java hackers know, there is some Motif porting discussion going on on freebsd-java. You may want to have a looksee there if you're working on Motif too. :) Kees Jan ============================================== You are only young once, but you can stay immature all your life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 4:22:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 4140B37B77C for ; Tue, 16 May 2000 04:22:10 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JPGWJIVKFM0002W1@research.kpn.com> for freebsd-hackers@freebsd.org; Tue, 16 May 2000 13:22:08 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Tue, 16 May 2000 13:22:05 +0100 Content-return: allowed Date: Tue, 16 May 2000 13:21:58 +0100 From: "Koster, K.J." Subject: 3.4 make world dies on groff To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D752D@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Hackers, I have the problem that make world does not grok groff. Please find the final messages of the compilation at the end of this e-mail. I've cvsupped last night, just before the "make world", so I guess my source tree must be sane. I've disabled softupdates, and -pipe, but that makes no difference. I assume that something in my box is seriously broken. I don't think it's hardware, because it dies reproducably at the exact same spot under different loads (i.e. I ran some other compiles in parallel with the make world, and I saw no other strangeness.) What can I do to get groff to build for me? Kees Jan ============================================== You are only young once, but you can stay immature all your life c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/env.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/node.cc c++ -I/usr/obj/usr/src/tmp/usr/include/g++ -O -I/usr/src/gnu/usr.bin/groff/troff/../include -fno-for-scope -DHAVE_UNISTD_H=1 -DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_STDLIB_H=1 -DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 -DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DHAVE_CC_LIMITS_H=1 -DRETSIGTYPE=void -DHAVE_STRUCT_EXCEPTION=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DSYS_SIGLIST_DECLARED=1 -I/usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/include -fno-for-scope -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc: In function `static void input_stack::end_file()': /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Internal compiler error. /usr/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/input.cc:56 6: Please submit a full bug report to `bug-g++@prep.ai.mit.edu'. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 6:23:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 3799037B700 for ; Tue, 16 May 2000 06:23:34 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for hackers@freebsd.org id 12rhJp-000Ckp-00; Tue, 16 May 2000 14:23:29 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id OAA07428 for hackers@freebsd.org; Tue, 16 May 2000 14:23:28 +0100 (BST) (envelope-from jcm) Date: Tue, 16 May 2000 14:23:28 +0100 From: J McKitrick To: hackers@freebsd.org Subject: ECP code Message-ID: <20000516142328.A7389@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't find any significant differences, other than the newbus function calls. Where does the ECP status get reported, and where is the ECP transfer actually handled? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org I am a bomb technician. If you see me running, try to keep up. ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 7:46:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.issei.org (mx1.issei.org [210.254.221.66]) by hub.freebsd.org (Postfix) with ESMTP id 91AD437B660 for ; Tue, 16 May 2000 07:46:45 -0700 (PDT) (envelope-from issei@issei.org) Received: from localhost (IDENT:v6AjQEkpEDQnL0/o7z9bbWpaAVJnzqYz6atrHujiqhzp/mChwGe6JNweqzE585b3@tole.issei.org [3ffe:505:a:1:200:f8ff:fe05:9fa2]) by mx1.issei.org (8.10.1/3.7W-v6) with SMTP id e4GEkco51874 for ; Tue, 16 May 2000 23:46:38 +0900 (JST) (envelope-from issei@issei.org) Date: Tue, 16 May 2000 23:46:38 +0900 (JST) Message-Id: <20000516.234638.15656027.issei@issei.org> To: hackers@freebsd.org Subject: SSE support for FreeBSD From: Issei Suzuki X-Mailer: Mew version 1.95b31 on XEmacs 21.1 (Canyonlands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I add SSE support for FreeBSD 4.0-RELEASE and 5.0-CURRENT. Some more work is needed everything to go well, but it works functionally now. The patches and documents are avaiable at: http://home.jp.freebsd.org/~issei/sse/sse.html Limitations: - Multiprocessor system is not supported. - There is no exception handler to deal with SSE Exceptions. - No spaces are available for SSE registers in struct fpregs. So, we cannot record SSE registers when dumping core, nor access to SSE registers via procfs. Comments, bug reports etc. are welcome. Issei.- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 8: 8: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kiew.egd.igd.fhg.de (kiew.egd.igd.fhg.de [192.102.170.32]) by hub.freebsd.org (Postfix) with ESMTP id 602D237B9FA for ; Tue, 16 May 2000 08:07:55 -0700 (PDT) (envelope-from runge@rostock.zgdv.de) Received: from rostock.zgdv.de (penguin.egd.igd.fhg.de [192.102.170.145]) by kiew.egd.igd.fhg.de (Netscape Messaging Server 3.6) with ESMTP id AAA6A88 for ; Tue, 16 May 2000 17:07:49 +0200 Message-ID: <392164D3.C33AF6F3@rostock.zgdv.de> Date: Tue, 16 May 2000 17:10:11 +0200 From: Thomas Runge X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 Cc: 'FreeBSD Hackers mailing list' Subject: Re: Motif porting discussions on -java References: <59063B5B4D98D311BC0D0001FA7E4522026D752B@l04.research.kpn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Koster, K.J." wrote: > > Just to let the non-java hackers know, there is some Motif porting > discussion going on on freebsd-java. You may want to have a looksee there if > you're working on Motif too. :) Seems, that nobody made a port upto now :-) So, here are my experiences with openmotif. There is a problem with motif's own version of imake. You can copy imakemdep.h from xfree's imake or just use XFree's imake itself. Copy/link Imake.tmpl, Motif.rules and Motif.tmpl (from config/cf) to /usr/X11R6/lib/X11/config for that. And now it gets tricky. lib/Xm/TextF.c needs some wide-charachter functions, that are not present in our libc. You can find a lib with these functions here: http://www.cs.rpi.edu/~crossd/FreeBSD/wcs-19990606.tar.gz I got the needed functions and just copied into the motif- sourcefile. Ah. For shared libs. You need to make the symlinks from libXX.so.a.b to libXX.so manually, if you don't do it, the linker will take the static libs. Well, thats an evil hack, but it gets you started until someone with more time and knowledge makes a "good" port :-) Enjoy. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 8:20:53 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 E753A37B9FA for ; Tue, 16 May 2000 08:20:50 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA00686; Tue, 16 May 2000 11:20:35 -0400 (EDT) Date: Tue, 16 May 2000 11:20:35 -0400 (EDT) From: Daniel Eischen Message-Id: <200005161520.LAA00686@pcnet1.pcnet.com> To: runge@rostock.zgdv.de Subject: Re: Motif porting discussions on -java Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Runge wrote: > "Koster, K.J." wrote: > > > > Just to let the non-java hackers know, there is some Motif porting > > discussion going on on freebsd-java. You may want to have a looksee there if > > you're working on Motif too. :) > > Seems, that nobody made a port upto now :-) > > So, here are my experiences with openmotif. > There is a problem with motif's own version of imake. You can > copy imakemdep.h from xfree's imake or just use XFree's imake > itself. > Copy/link Imake.tmpl, Motif.rules and Motif.tmpl (from config/cf) to > /usr/X11R6/lib/X11/config for that. If Motif has it's own version of imake, make sure it uses gcc -E (or /usr/bin/cpp) instead of /usr/libexec/cpp. -- 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 May 16 9:37:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6ABDD37B54F for ; Tue, 16 May 2000 09:37:46 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA19716; Tue, 16 May 2000 09:37:45 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA82865; Tue, 16 May 2000 09:37:44 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Tue, 16 May 2000 09:37:44 -0700 (PDT) Message-Id: <200005161637.JAA82865@vashon.polstra.com> To: n@nectar.com Subject: Re: need to borrow a clue re: rtld In-Reply-To: <20000516002513.A65118@bone.nectar.com> References: <20000516002513.A65118@bone.nectar.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000516002513.A65118@bone.nectar.com>, Jacques A . Vidrine wrote: > Messing about with Dante (the SOCKS5 replacement), I've encountered > some difficulty with run-time linking that I don't understand. > > In brief: > > $ env LD_PRELOAD=libdsocks.so telnet # works > $ env LD_PRELOAD=libdsocks.so xchat # undefined symbol '_gethostbyname' > $ env LD_PRELOAD=libc.so:libdsocks.so xchat # works Which version of FreeBSD? If you have time, please rebuild "src/libexec/rtld-elf" with DEBUG_FLAGS=-DDEBUG. Make a copy of your existing "/usr/libexec/ld-elf.so.1" and then install the debugging version. Run your first test case like this: script Log.1 env LD_DEBUG=1 LD_PRELOAD=libdsocks.so telnet (exit telnet and get out of "script") and likewise for the failing test case (with a different filename for script, of course). Send the output to me and I'll try to figure out what's happening. After you're done, you should restore your original (non-debugging) rtld. It's more efficient and also probably more secure. 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 May 16 9:51:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gw.nectar.com (gw.nectar.com [209.98.143.44]) by hub.freebsd.org (Postfix) with ESMTP id 719C037B8E7 for ; Tue, 16 May 2000 09:51:11 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from bone.nectar.com (bone.nectar.com [10.0.1.105]) by gw.nectar.com (Postfix) with ESMTP id F25BB9B10; Tue, 16 May 2000 11:51:09 -0500 (CDT) Received: by bone.nectar.com (Postfix, from userid 1001) id 4A8F61DAB; Tue, 16 May 2000 11:51:09 -0500 (CDT) Date: Tue, 16 May 2000 11:51:08 -0500 From: "Jacques A . Vidrine" To: John Polstra Cc: hackers@freebsd.org Subject: Re: need to borrow a clue re: rtld Message-ID: <20000516115108.B66729@bone.nectar.com> References: <20000516002513.A65118@bone.nectar.com> <200005161637.JAA82865@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200005161637.JAA82865@vashon.polstra.com>; from jdp@polstra.com on Tue, May 16, 2000 at 09:37:44AM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 16, 2000 at 09:37:44AM -0700, John Polstra wrote: > Which version of FreeBSD? 4.0-STABLE ~ May 8. > If you have time, please rebuild "src/libexec/rtld-elf" with > DEBUG_FLAGS=-DDEBUG. [logs for telnet and xchat sent off-list] I should have mentioned earlier that in the fail case, xchat operates until it tries to connect to a server (i.e. when you push the connect button), as opposed to failing during the initial loading of libraries. Thanks for helping with this! -- Jacques Vidrine / n@nectar.com / 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 Tue May 16 10:45:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 870E937BB09; Tue, 16 May 2000 10:45:14 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (ip43.salt-lake-city6.ut.pub-ip.psi.net [38.27.95.43]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id LAA10770; Tue, 16 May 2000 11:44:42 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39218971.AE6779B5@softweyr.com> Date: Tue, 16 May 2000 11:46:25 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Kris Kennaway , Tim Vanderhoek , James Howard , freebsd-hackers@FreeBSD.ORG Subject: Re: mktemp() vs. mkstemp() References: <39204472.706CB1D2@softweyr.com> <20000515123256.C249@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Wes Peters [000515 12:11] wrote: > > Kris Kennaway wrote: > > > > > > On Sun, 14 May 2000, Tim Vanderhoek wrote: > > > > > > > It's certainly not like it would be the first non-portable function > > > > we've added. Where adding functions to libraries encourages better > > > > coding practices, I'm (often) in favour of it, especially if it > > > > encourages more secure coding practices. Ultimately everyone > > > > benefits, and the pain is short-term. > > > > > > True, but I'd venture that in most of those cases they did something a > > > little less trivial than one line of code. > > > > We could simply redefine mktemp to not be such a security hole. Do > > common programs that use mktemp depend on side effects? > > The side effect they depend on is that the char * returned is unique, > but since no file was created it's not garanteed so. You can't fix > it. Drat, that's right. Anyone wanna pollute the kernel and filesystem layers with a "reserve this filename" function? That sounds fugly, doesn't it? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 11:13:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 8B02C37B9A4 for ; Tue, 16 May 2000 11:13:19 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-38.bellatlantic.net [151.198.117.38]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id OAA21320; Tue, 16 May 2000 14:13:15 -0400 (EDT) Message-ID: <39218FBD.1FA9B252@bellatlantic.net> Date: Tue, 16 May 2000 14:13:17 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: hackers@freebsd.org, jkh@time.cdrom.com Subject: de-GNUfication of Digiboard driver ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been reading recently some stories about the licensing issues and that brought me to an interesting conclusion: apparently, we are able to change the license of the Digiboard driver from GPL to BSD ? It does not seem to be that much important any more as these cards are obsolete, but still. I was the original author of that driver. To get the information about the Digi interface I've read the Linux driver. I supposed that it made me mentally contaminated with GPL. But all the FreeBSD driver was written from scratch, with none of the Linux code re-used (except for the array with the image of firmware but apparently that one was available as well from non-GPL-contaminated sources, such as Digi's drivers for other Unixes). But now looking at the BSD-USL case it seems like I was wrong about the mental contamination. Apparently none of the author of the later changes to this driver were enthusiastic about GPL as well. So if I'm getting the things right, can we just go ahead now and change its license to BSD ? Or am I wrong ? -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 11:32:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 05C9C37B9B4 for ; Tue, 16 May 2000 11:32:28 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000516183227.LKME18096.mail.rdc1.ct.home.com@home.com> for ; Tue, 16 May 2000 11:32:27 -0700 Message-ID: <3921949C.657643A3@home.com> Date: Tue, 16 May 2000 14:34:04 -0400 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.ORG" Subject: Motif paging Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been a while since I used mwm. I installed the OpenMotif Metrolink binaries and have mwm running. It's just as solid as I remember it. One problem I cannot get paging to work. On an old system I used to use the following worked for paging: .Xdefaults ----------- Mwm*windowMenu: MyWindowMenu Mwm*bitmapDirectory: /usr/X11R6/include/X11/icons !******************************* panning stuff ********* ! setup toggle_pinstate menu entry... ! NOTE - these pixmaps require fully qualified path names... ! see sample.mwmrc file for compete definition. Mwm*pinStateLabelType: PIXMAP Mwm*pinnedPixmap: pinned Mwm*unpinnedPixmap: unpinned ! setup which clients and icons are pinned Mwm*Mwm.clientPinned: True Mwm*iconPinned: True Mwm*xclock.clientPinned: True ! Setup the panning menu Mwm*GotoMenuColor*packing: PACK_COLUMN Mwm*GotoMenuColor*orientation: HORIZONTAL Mwm*GotoMenuColor*alignment: ALIGNMENT_CENTER ! This stops all windows from being repositioned on-screen ! after a restart. Mwm*positionOnScreen: False .mwmrc ------------ # Menu for hopping to different locations on the virtual desktop. # The images should be kept in the location specified by # the "Mwm*bitmapDirectory:" resource. # See sample images in the images directory. The following # image references refer to bitmaps and pixmaps contained in # the examples/images/ directory. Menu GotoMenuColor { link f.goto 0,0 mail f.goto 0,2000 book.2 f.goto 0,4000 knife f.goto 0,6000 plugin f.goto 0,8000 } # Default Window Menu Description Menu MyWindowMenu { @pinned f.toggle_pin_state Restore _R AltF5 f.normalize Move _M AltF7 f.move Size _S AltF8 f.resize Minimize _n AltF9 f.minimize Maximize _x AltF10 f.maximize Refresh _f AltF2 f.refresh_win Lower _L AltF3 f.lower no-label f.separator Close _C AltF4 f.kill } # # key binding descriptions # Keys DefaultKeyBindings { ShiftEscape window|icon f.post_wmenu Metaspace window|icon f.post_wmenu MetaTab root|icon|window f.next_key Meta ShiftTab root|icon|window f.prev_key MetaEscape root|icon|window f.circle_up Meta ShiftEscape root|icon|window f.circle_down Meta Shift Ctrlexclam root|icon|window f.set_behavior MetaF6 window f.next_key transient Meta ShiftF6 window f.prev_key transient F4 icon f.post_wmenu Meta ShiftDelete root|icon|window f.restart AltF10 root|window|icon f.post_rmenu CtrlEscape root|window|icon f.normalize_and_raise_iconbox MetaUp window|root|icon f.pan 0,-100,1 MetaDown window|root|icon f.pan 0,100,1 MetaLeft window|root|icon f.pan -100,0,1 MetaRight window|root|icon f.pan 100,0,1 } # # button binding descriptions # Buttons DefaultButtonBindings { frame|icon f.raise frame|icon f.lower root f.menu Clients root f.menu GotoMenuColor root f.menu Control Meta window|icon f.move Meta window|icon f.resize Meta Shift window|icon f.minimize Meta Shift window|icon f.focus_color Meta Shift window|icon f.post_wmenu Meta root f.track_pan Meta root f.track_pan } Can anyone help me with this or direct me to a place with the info? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 11:53:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 5951E37B97A for ; Tue, 16 May 2000 11:53:36 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id LAA60111; Tue, 16 May 2000 11:49:12 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200005161849.LAA60111@troutmask.apl.washington.edu> Subject: Re: Can we use this for the JDK? (was: Motif goes open source) In-Reply-To: <3920F59C.E6EEDF42@mindspring.com> from W Gerald Hicks at "May 16, 2000 00:15:40 am" To: W Gerald Hicks Date: Tue, 16 May 2000 11:49:12 -0700 (PDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks wrote: > "Koster, K.J." wrote: > > > > In what form is Motif going to be available to the general FreeBSD > > developer? Am I going to find /usr/ports/x11-toolkits/motif anytime soon, or > > is this going to be more complicated than that? > > > > As Poul-Henning Kamp noted earlier we have licenses in the ports tree > that are *much* stranger than this one. I'd be very surprised if we > don't see an entry in ports/x11-toolkits for Motif sometime soon. > > I'd also be very interested in what the "Hungry Programmers" have to say > about this new development. > http://www.lesstif.org/future.html Basically, LessTif is still a viable/valuable toolkit because you can't use Open Motif on any proprietary OS. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 12:14: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id A6ACD37BAE5 for ; Tue, 16 May 2000 12:13:58 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA17772; Tue, 16 May 2000 15:13:29 -0400 (EDT) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA08222; Tue, 16 May 2000 15:13:48 -0400 (EDT) Received: from rac2.wam.umd.edu (howardjp@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA08217; Tue, 16 May 2000 15:13:48 -0400 (EDT) Message-Id: <200005161913.PAA08217@rac2.wam.umd.edu> X-Authentication-Warning: rac2.wam.umd.edu: howardjp owned process doing -bs To: Wes Peters Cc: freebsd-hackers@freebsd.org Subject: Re: mktemp() vs. mkstemp() In-reply-to: Your message of "Tue, 16 May 2000 11:46:25 MDT." <39218971.AE6779B5@softweyr.com> Date: Tue, 16 May 2000 15:13:39 -0400 From: James Howard Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39218971.AE6779B5@softweyr.com>, Wes Peters writes: > Drat, that's right. Anyone wanna pollute the kernel and filesystem > layers with a "reserve this filename" function? That sounds fugly, > doesn't it? That's why I suggested a simpler solution even I can code :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 12:43:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jestocost.cosc.morrisville.edu (jestocoast.cosc.morrisville.edu [136.204.176.67]) by hub.freebsd.org (Postfix) with ESMTP id 7168137B593 for ; Tue, 16 May 2000 12:43:10 -0700 (PDT) (envelope-from root@jestocost.cosc.morrisville.edu) Received: (from root@localhost) by jestocost.cosc.morrisville.edu (8.9.3/8.9.3) id PAA02325; Tue, 16 May 2000 15:39:10 -0400 (EDT) (envelope-from root) Date: Tue, 16 May 2000 15:39:10 -0400 (EDT) From: Charlie Root Message-Id: <200005161939.PAA02325@jestocost.cosc.morrisville.edu> To: freebsd-hackers@freebsd.org Subject: smb printer trouble Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a simple filter to print to an nt print queue through the smbclinet. It tests to see if the file is postscript or text, and if it is text it sends a control code to tell the printer to do the lf->crlf conversion. My problem is that the '\' escapes in the first line get clobbered. for example, if I print this printcap: **** begin printcap **** lp:\ :sh:\ :lp=/dev/lpt0:\ :sd=/var/spool/output/lpd/lp:\ :lf=/var/log/lpd/lpd.log: lplaser:\ :sh:\ :lp=/dev/null:\ :if=/root/filters/smb-filter:\ :sd=/var/spool/output/lpd/lplaser:\ :lf=/var/log/lpd/lpd.log: **** end printap **** the entire entry for "lp" will be on one line, but the "lplaser" entry will print out like it is supposed to. I know why it is doing it, however I don't know how to fix it. Any help will be appreciated (script is below). Thanks, James **** begin smb-filter **** #!/bin/sh #### # Input filter to print to a NT print queue, requires smbclient. # # Author: James Halstead, e-mail: JAHalstead@hotmail.com # # Read stdin to a temp, make sure to determine the print type, then use # smbclient to print to the nt queue. #### SERVER= PRINTER=cw TEMP=/tmp/smbprint TEMP=`mktemp -q $TEMP.XXXXXX` read firstline first_two=`expr "$firstline" : '\(..\)'` if [ "$first_two" != "%!" ]; then printf "\033&k3G" > $TEMP fi #lets see, copy the firstline to temp, cat the rest to the temp, # make one ugly command to print the file to the smb printer then # rm the temp file. echo "$firstline" >> $TEMP && cat >> $TEMP &&\ /usr/local/bin/smbclient \\\\$SERVER\\$PRINTER -UGUEST -N\ -c"print $TEMP" &&\ rm -f $TEMP >/dev/null && exit 0 exit 1 **** end smb-filter **** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 12:45: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id ED40437BA1F for ; Tue, 16 May 2000 12:44:58 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA02884; Tue, 16 May 2000 12:44:26 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005161944.MAA02884@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: J McKitrick Cc: hackers@freebsd.org Subject: Re: ECP code In-reply-to: Your message of "Tue, 16 May 2000 14:23:28 BST." <20000516142328.A7389@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 May 2000 12:44:26 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? > I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't > find any significant differences, other than the newbus function calls. > Where does the ECP status get reported, and where is the ECP transfer > actually handled? It's in the ppc driver (sys/isa/ppc.c). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 12:58:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id E945337BB57; Tue, 16 May 2000 12:58:12 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12rnTl-0000VF-00; Tue, 16 May 2000 20:58:09 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id UAA13068; Tue, 16 May 2000 20:58:05 +0100 (BST) (envelope-from jcm) Date: Tue, 16 May 2000 20:58:05 +0100 From: J McKitrick To: Mike Smith Cc: hackers@freebsd.org Subject: Re: ECP code Message-ID: <20000516205805.A13036@dogma.freebsd-uk.eu.org> References: <20000516142328.A7389@dogma.freebsd-uk.eu.org> <200005161944.MAA02884@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005161944.MAA02884@mass.cdrom.com>; from msmith@freebsd.org on Tue, May 16, 2000 at 12:44:26PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 16, 2000 at 12:44:26PM -0700, Mike Smith wrote: > > Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? > > I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't > > find any significant differences, other than the newbus function calls. > > Where does the ECP status get reported, and where is the ECP transfer > > actually handled? > > It's in the ppc driver (sys/isa/ppc.c). Where was it before? I could look for it at home, but right now i'm searching on a remote 3.4 machine, and i can't find it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13: 2:39 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 74C0337BB24; Tue, 16 May 2000 13:02:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA81549; Tue, 16 May 2000 14:02:27 -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 OAA80550; Tue, 16 May 2000 14:01:45 -0600 (MDT) Message-Id: <200005162001.OAA80550@harmony.village.org> To: Wes Peters Subject: Re: mktemp() vs. mkstemp() Cc: Alfred Perlstein , Kris Kennaway , Tim Vanderhoek , James Howard , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 May 2000 11:46:25 MDT." <39218971.AE6779B5@softweyr.com> References: <39218971.AE6779B5@softweyr.com> <39204472.706CB1D2@softweyr.com> <20000515123256.C249@fw.wintelcom.net> Date: Tue, 16 May 2000 14:01:45 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39218971.AE6779B5@softweyr.com> Wes Peters writes: : Drat, that's right. Anyone wanna pollute the kernel and filesystem : layers with a "reserve this filename" function? That sounds fugly, : doesn't it? Yes. It isn't needed. mkstemp already does the looping to make it safe. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13: 7: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id AB77937BB31; Tue, 16 May 2000 13:07:05 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA03052; Tue, 16 May 2000 13:06:39 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005162006.NAA03052@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: J McKitrick Cc: Mike Smith , hackers@freebsd.org Subject: Re: ECP code In-reply-to: Your message of "Tue, 16 May 2000 20:58:05 BST." <20000516205805.A13036@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 May 2000 13:06:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, May 16, 2000 at 12:44:26PM -0700, Mike Smith wrote: > > > Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory? > > > I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't > > > find any significant differences, other than the newbus function calls. > > > Where does the ECP status get reported, and where is the ECP transfer > > > actually handled? > > > > It's in the ppc driver (sys/isa/ppc.c). > > Where was it before? I could look for it at home, but right now i'm > searching on a remote 3.4 machine, and i can't find it. 'locate ppc.c' is your friend. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:10:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 1CE4A37BB6C for ; Tue, 16 May 2000 13:10:29 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id QAA02087 for ; Tue, 16 May 2000 16:10:28 -0400 (EDT) Message-ID: <3921AB34.73A873DC@thehousleys.net> Date: Tue, 16 May 2000 16:10:28 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: IPv6 and hosts.allow Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is inetd wrapping and hosts.allow supposed to support IPv6 addresses? Because it isn't for me. Not only that but added an IPv6 address to hosts.allow seems to prevent processing of IPv4 anddress on that line. If it should and is broken I will submit a PR. If not I will look and see if I can submit a PR with code. BTW this is 4.0 cvsupd and compile with cvs-cur-6351.gz of this morning (2000/5/16) Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:21: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 2CED337B56D; Tue, 16 May 2000 13:21:00 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12rnpr-0004RH-00; Tue, 16 May 2000 21:20:59 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id VAA13404; Tue, 16 May 2000 21:20:55 +0100 (BST) (envelope-from jcm) Date: Tue, 16 May 2000 21:20:55 +0100 From: J McKitrick To: Mike Smith Cc: hackers@freebsd.org Subject: Re: ECP code Message-ID: <20000516212055.A13352@dogma.freebsd-uk.eu.org> References: <20000516205805.A13036@dogma.freebsd-uk.eu.org> <200005162006.NAA03052@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005162006.NAA03052@mass.cdrom.com>; from msmith@freebsd.org on Tue, May 16, 2000 at 01:06:39PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just realized i think this machine may not have that part of the source installed. Also, the ppc code is even more complex than the ppbus stuff. I don't know how much good i'll be able to do. Does anyone have any ideas on figuring out why ECP is broken? Is it broken in -current as well? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org I am a bomb technician. If you see me running, try to keep up. ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:24:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 2AC6A37B809 for ; Tue, 16 May 2000 13:24:28 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:5e8DYnJuqTYxUOKj7Hvde4H+q0yE9vo2frsytsEfFOrgPomWYXIORDgpct9JiQI2@localhost [::1]) by peace.mahoroba.org (8.10.1/3.7W-peace) with ESMTP id e4GKJsF75988; Wed, 17 May 2000 05:19:54 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 17 May 2000 05:19:54 +0900 (JST) Message-Id: <200005162019.e4GKJsF75988@peace.mahoroba.org> To: jim@thehousleys.net Cc: freebsd-hackers@freebsd.org Subject: Re: IPv6 and hosts.allow In-Reply-To: <3921AB34.73A873DC@thehousleys.net> References: <3921AB34.73A873DC@thehousleys.net> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Hajimu UMEMOTO (=?ISO-2022-JP?B?GyRCR19LXBsoQiA=?= =?ISO-2022-JP?B?GyRCSCUbKEI=?=) X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 16 May 2000 16:10:28 -0400 >>>>> James Housley said: jim> Is inetd wrapping and hosts.allow supposed to support IPv6 addresses? jim> Because it isn't for me. Not only that but added an IPv6 address to jim> hosts.allow seems to prevent processing of IPv4 anddress on that line. jim> If it should and is broken I will submit a PR. If not I will look and jim> see if I can submit a PR with code. BTW this is 4.0 cvsupd and compile jim> with cvs-cur-6351.gz of this morning (2000/5/16) Yes, I wrote IPv6 support code for tcp_wrappers. And, actually, I'm using it. How do you specify IPv6 address? IPv6 address has `:' in it and it conflict with tcp_wrappers's field separator. So, you need to wrap IPv6 address with `[' and `]'. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:34: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 0D36F37BC00 for ; Tue, 16 May 2000 13:34:03 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA03244; Tue, 16 May 2000 13:33:34 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005162033.NAA03244@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: J McKitrick Cc: hackers@freebsd.org Subject: Re: ECP code In-reply-to: Your message of "Tue, 16 May 2000 21:20:55 BST." <20000516212055.A13352@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 May 2000 13:33:34 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, the ppc code is even more complex than the ppbus stuff. I don't know > how much good i'll be able to do. Does anyone have any ideas on figuring > out why ECP is broken? Is it broken in -current as well? No ideas, no. You should be able to fathom at least parts of the code, although you may well end up needing a copy of the 1284 spec. You might also look at the linux code for inspiration. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:37:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 17C9A37B8A4 for ; Tue, 16 May 2000 13:37:09 -0700 (PDT) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (baby.int.thehousleys.net. [192.168.0.24]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id QAA02353; Tue, 16 May 2000 16:37:07 -0400 (EDT) Message-ID: <3921B173.F6E8E479@thehousleys.net> Date: Tue, 16 May 2000 16:37:07 -0400 From: James Housley Organization: The Housleys dot Net X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: ume@mahoroba.org Subject: Re: IPv6 and hosts.allow References: <3921AB34.73A873DC@thehousleys.net> <200005162019.e4GKJsF75988@peace.mahoroba.org> Content-Type: multipart/mixed; boundary="------------B01C241B9A42ED15000AE95C" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------B01C241B9A42ED15000AE95C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Hajimu UMEMOTO ($BG_K\(B $BH%(B)" wrote: > > Yes, I wrote IPv6 support code for tcp_wrappers. And, actually, I'm > using it. > How do you specify IPv6 address? IPv6 address has `:' in it and it > conflict with tcp_wrappers's field separator. So, you need to wrap > IPv6 address with `[' and `]'. > Like this? Would you like me to submit a PR with this or can you commit the changes or better ones??? Jim -- Studies show that 1 out of every 4 Americans suffer some form of mental illness. So look at your three best friends, if they are okay it is YOU! --------------B01C241B9A42ED15000AE95C Content-Type: text/plain; charset=us-ascii; name="hosts.allow.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="hosts.allow.diff" --- hosts.allow Fri May 5 13:58:34 2000 +++ hosts.allow.new Tue May 16 16:34:05 2000 @@ -33,6 +33,8 @@ # name) *MUST* be specified for portmap(8). ALL : localhost 127.0.0.1 : allow ALL : my.machine.example.com 192.0.2.35 : allow +# To use IPv6 addresses you must enclose them in []'s +ALL : [fe80::/10] # Sendmail can help protect you against spammers and relay-rapers sendmail : localhost : allow --------------B01C241B9A42ED15000AE95C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:45:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 3BE8837B8A6; Tue, 16 May 2000 13:45:42 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1131.dip0.t-ipconnect.de [62.156.17.49]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id WAA13411; Tue, 16 May 2000 22:45:37 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 54480AC2C; Tue, 16 May 2000 22:45:44 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id WAA16179; Tue, 16 May 2000 22:45:40 +0200 (CEST) (envelope-from alex) Date: Tue, 16 May 2000 22:45:40 +0200 From: Alexander Langer To: doc@freebsd.org, hackers@freebsd.org Subject: newbus documentation Message-ID: <20000516224540.A16053@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've started a newbus introduction. It covers most aspects of a newbus driver, based on Warner Losh's led-driver. I've added interrupts- and ioctl-handlers. The whole thing "behing" newbus is a little bit vague. Please review my documentation and give me hints for improvements. I'd like to see that introduction in the official docs some time, since I've heard from several people that the bad thing with newbus is its lack of documentation. ftp://big.endian.de/pub/FreeBSD/newbus-intro.tar.gz Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:48: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id B63BB37B62B for ; Tue, 16 May 2000 13:48:03 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (ip43.salt-lake-city6.ut.pub-ip.psi.net [38.27.95.43]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id OAA11147; Tue, 16 May 2000 14:47:37 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <3921B451.F4A4A2A8@softweyr.com> Date: Tue, 16 May 2000 14:49:21 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Sam Stephenson Cc: hackers@FreeBSD.ORG, Bob Bishop , "Robert A. Bruce" Subject: Re: Motif goes open source References: <4.3.1.2.20000515080753.00abfd70@gid.co.uk> <001e01bfbeba$370c2300$0200000a@grapevine.local> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sam Stephenson wrote: > > On Monday, May 15, 2000 at 03:09a, Bob Bishop wrote: > > > "The Open Group, a vendor and technology-neutral consortium dedicated to > > enterprise integration, announced today that it is releasing the source > > code of Motif, using a public license, to the Open Source community." > > > > Full details at http://www.opengroup.org/openmotif > > > > Check out the web page: > > "We want to support the momentum of Open Source operating systems such as > Linux(R) and FreeBSD by developing an Open Motif(R)..." > > and > > "UNIX and Motif are registered trademarks of The Open Group in the US and > other countries. The Open Group and the X Window System are trademarks of > The Open Group. Linux is a registered trademark of Linus Torvalds." Sorry, it's not anymore. There are two registrations for the simple trademark "Linux", including: Rosch, AG (Swiss) for laundry detergents and laundry bleaches for home use; cleaning preparations for home use; degreasing preparations for home use; general purpose scouring powders; skin soap for personal use; perfume; essential oils for personal use; preparations for personal hygiene and cosmetic purposes, hair tonic; toothpaste. Croce, William R. Della, Jr., 33 Snow Hill St. Boston MA 02113 computer operating system software to facilitate computer use and operation. CHANGE IN REGISTRATION HAS OCCURRED. I prefer to use the first because it amuses me. > Correct me if I'm wrong, but I do believe FreeBSD is a registered trademark > of some organization -- FreeBSD, Inc., Walnut Creek, or BSDI. Someone > should politely inform The Open Group of FreeBSD's trademark status. WALNUT CREEK CDROM, INCORPORATED 1547 Palos Verdes Mall, Suite 260 Walnut Creek CALIFORNIA 94596 I see no reason you shouldn't inform them yourself. Do you? http://trademarks.uspto.gov/cgi-bin/search4?ENG+3 -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 13:53:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id CD2CF37B55F; Tue, 16 May 2000 13:53:21 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12roKw-0004x9-00; Tue, 16 May 2000 21:53:06 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id VAA13890; Tue, 16 May 2000 21:53:06 +0100 (BST) (envelope-from jcm) Date: Tue, 16 May 2000 21:53:05 +0100 From: J McKitrick To: Mike Smith Cc: hackers@freebsd.org Subject: Re: ECP code Message-ID: <20000516215305.A13786@dogma.freebsd-uk.eu.org> References: <20000516212055.A13352@dogma.freebsd-uk.eu.org> <200005162033.NAA03244@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005162033.NAA03244@mass.cdrom.com>; from msmith@freebsd.org on Tue, May 16, 2000 at 01:33:34PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 16, 2000 at 01:33:34PM -0700, Mike Smith wrote: > > Also, the ppc code is even more complex than the ppbus stuff. I don't know > > how much good i'll be able to do. Does anyone have any ideas on figuring > > out why ECP is broken? Is it broken in -current as well? > > No ideas, no. You should be able to fathom at least parts of the code, > although you may well end up needing a copy of the 1284 spec. You might > also look at the linux code for inspiration. Well, i can follow things somewhat, but without a list of all the functions and what they do, it's tough to get your bearings. Maybe that's what i should do. Also, i can't tell what relates to the zip drive and what doesn't. The 1284 does, you say? I'll check out the old imm.c driver as well. Thanks. But i don't know if the problem is the driver or the ECP part of the interface. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 14: 2:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id 0BCD537B8C9 for ; Tue, 16 May 2000 14:02:52 -0700 (PDT) (envelope-from arjan@jak.nl) Received: from jaknl by athos.nl.uu.net with UUCP id ; Tue, 16 May 2000 23:02:38 +0200 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id XAA18890 for ; Tue, 16 May 2000 23:08:57 +0200 (CEST) (envelope-from arjan@jak.nl) Message-ID: <3921B782.1EACF767@jak.nl> Date: Tue, 16 May 2000 23:02:58 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers FreeBSD Subject: Re: Cyclades Cyclom YeP PCI problem References: <39210E15.D3D2F278@jak.nl> Content-Type: multipart/mixed; boundary="------------CB8A78FC42326F43A9D0EE52" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------CB8A78FC42326F43A9D0EE52 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 1.) The problem with the cy driver resides in the function cyattach_common in the cy.c file. make_dev is called like this: make_dev(&sio_cdevsw, unit, UID_ROOT, GID_WHEEL , 0600, "ttyc%r%r", adapter, unit % CY_MAX_PORTS); where 'unit' is 0 to 31 for board one 32 to 63 for board two 64 to 95 for board three 96 to 127 for board four. But when I use 'MAKEDEV cuacX' for the installed and configured cy devices, MAKEDEV does the following: minor='ttyminor $unit' minor='expr $card \* 65536 + $minor' The second argument in make_dev function needs a conversion something like : make_dev(&sio_cdevsw, ( adapter * 65536 + ( unit % CY_MAX_PORTS ) ), UID_ROOT, GID_WHEEL , 0600, "ttyc%r%r", adapter, unit %CY_MAX_PORTS); 2.) For some reason there is sometimes a problem with detecting the CD1400 ic's firmware_revision. I solved it by increasing the DELAY values in a loop and inserted some (extra) loops and check's, but I don't know whether or not it might hurt at some point? Arjan Knepper > I have two cyclom YeP PCI board installed with 32 serials ports > connected to both on a FreeBSD 4.0 release system. > > The first board (cy0) is working without problems however the > second one (cy1) give some trouble. > When I try to connect to a port e.g. cuac10 - cuac1v a kernel > warning is displayed: > 'WARNING: driver cy should register devices with make_dev () > (dev_t = "cy/0x1008f")' but the connected is made. > > I added some 'printf ()'s to the 'cy.c' file in the > 'cyattach_common ()' to verify whether 'make_dev ()' is called > for the relevant ports and that seems to be OK. So my question is > what wrong here? Can someone give a hint? --------------CB8A78FC42326F43A9D0EE52 Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------CB8A78FC42326F43A9D0EE52-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 14:22:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id E0FF337B54B for ; Tue, 16 May 2000 14:22:06 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:PhCQqYNnr+ODXBUxOM1jfNzFG7zPPXGZ4VJzsVYGLKAg1E1u9p0SWz2FoCZEr4d1@localhost [::1]) by peace.mahoroba.org (8.10.1/3.7W-peace) with ESMTP id e4GLGWF76144; Wed, 17 May 2000 06:16:32 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 17 May 2000 06:16:32 +0900 (JST) Message-Id: <200005162116.e4GLGWF76144@peace.mahoroba.org> To: jim@thehousleys.net Cc: freebsd-hackers@freebsd.org Subject: Re: IPv6 and hosts.allow In-Reply-To: <3921B173.F6E8E479@thehousleys.net> References: <3921AB34.73A873DC@thehousleys.net> <200005162019.e4GKJsF75988@peace.mahoroba.org> <3921B173.F6E8E479@thehousleys.net> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Hajimu UMEMOTO (=?ISO-2022-JP?B?GyRCR19LXBsoQiA=?= =?ISO-2022-JP?B?GyRCSCUbKEI=?=) X-Dispatcher: imput version 20000228(IM140) Lines: 49 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 16 May 2000 16:37:07 -0400 >>>>> James Housley said: > How do you specify IPv6 address? IPv6 address has `:' in it and it > conflict with tcp_wrappers's field separator. So, you need to wrap > IPv6 address with `[' and `]'. > jim> Like this? No. For example: ALL : [fe80::]/10 Please see manpage for host_access(5). jim> Would you like me to submit a PR with this or can you commit jim> the changes or better ones??? jim> +# To use IPv6 addresses you must enclose them in []'s jim> +ALL : [fe80::/10] To add example in /etc/hosts.allow is good idea. But, use of link-local address is not so good. Because, current IPv6 implementation of tcp_wrappers cannot treat scope-id. So, this means: allow any link-local connections from any neighbor networks It contains not only ethernet but also gif tunnel etc. Do you really need to allow link-local connection? I already rewrote tcp_wrappers to support scoped address and it is shipped as KAME ports. You can obtain it from: http://www.imasy.or.jp/~ume/ipv6/tcp_wrappers_7.6-ipv6-1.9.diff.gz By using this, you can specify: ALL : [fe80::%de0]/10 : allow But, this has some limitations. This is a patch to original tcp_wrappers. And, this doesn't work on 5.0-CURRENT nor 4.0-STABLE due to getaddrinfo() problem around treatment of IPv4 address obtained by specifying PF_UNSPEC. To work it on FreeBSD without additional KAME package, we should correct getaddrinfo(). The patch is ready and now in review. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 15:28: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 2E8C137BAD1 for ; Tue, 16 May 2000 15:27:58 -0700 (PDT) (envelope-from n_hibma@calcaphon.com) Received: from calcaphon.demon.co.uk ([193.237.19.5] helo=bluebottle.qubesoft.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12rpof-0004gm-0A; Tue, 16 May 2000 22:27:55 +0000 Received: from henny.webweaving.org (henny.qubesoft.com [192.168.1.5]) by bluebottle.qubesoft.com (8.9.3/8.9.1) with ESMTP id XAA29188; Tue, 16 May 2000 23:27:23 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id WAA85534; Tue, 16 May 2000 22:51:23 +0100 (BST) (envelope-from n_hibma@calcaphon.com) Date: Tue, 16 May 2000 22:51:22 +0100 (BST) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: What do people think of maybe using the sourceforge software? In-Reply-To: <14620.957842046@localhost> 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 guess that most people leading a project could do with a bit of feature creep, features being shoved under their noses. Even if at first you think that source control solves all our problems, it still could be a way to develop new tools and get them running and tried out before committing them to the tree. Second, the projects page we have now, with all due respect to the people that try to keep it reasonably organised, is a mess due to the lack of updates. people only maintain their project pages perhaps, but certainly not the links that lead to them. Being able to work with more people on the same project on an equal bases would be a good idea IMHO. Nick > http://sourceforge.net/project/filelist.php?group_id=1 > > Contains the software used by source forge to implement the > project/help desk/download tracker thingie which they themselves use > to manage the various projects registered with source forge. > > I think it's also reasonable to say that FreeBSD itself is a bit too > large to register and run as a sourceforge project, but why not use > the same software to offer a higher level of "polish" to the existing > project infrastructure? Comments? I'm just playing with this stuff a > bit myself right now and will say more once I actually know more about > it. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 16:27:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 4650137BB6A for ; Tue, 16 May 2000 16:27:13 -0700 (PDT) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id QAA74062 for ; Tue, 16 May 2000 16:59:11 -0600 (MDT) Date: Tue, 16 May 2000 16:59:11 -0600 (MDT) From: Nick Rogness To: hackers@freebsd.org Subject: Bad Block scan 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 thought FreeBSD had an option on install to run a bad block scan on a drive? Just installed (4.0-RELEASE) and noticed it wasn't there. Any specific reason...or maybe a reference page that explains. Thanks in advance. Nick Rogness - Speak softly and carry a Gigabit switch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 16:39:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 78BD637B59F for ; Tue, 16 May 2000 16:39:22 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id QAA09360; Tue, 16 May 2000 16:39:15 -0700 (PDT) Date: Tue, 16 May 2000 16:39:14 -0700 From: Brooks Davis To: Nick Rogness Cc: hackers@FreeBSD.ORG Subject: Re: Bad Block scan Message-ID: <20000516163914.A8494@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from nick@rapidnet.com on Tue, May 16, 2000 at 04:59:11PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 16, 2000 at 04:59:11PM -0600, Nick Rogness wrote: > > I thought FreeBSD had an option on install to run a bad block scan on a > drive? Just installed (4.0-RELEASE) and noticed it wasn't there. Any > specific reason...or maybe a reference page that explains. Thanks in > advance. Bad block management was removed in 4.0. All modern drives (ATA and SCSI) do hardware bad block management and no one wanted to maintain the old code so it was killed. The general feeling is that if your disk generates errors it has run out of replacement sectors and thus is dying and should be replaced. -- 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 Tue May 16 19:15: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cerberus.techfuel.com (irvine.techfuel.com [209.80.51.55]) by hub.freebsd.org (Postfix) with ESMTP id C67F337B9DF for ; Tue, 16 May 2000 19:14:59 -0700 (PDT) (envelope-from kehlet@techfuel.com) Received: from basilisk.techfuel.com (basilisk.techfuel.com [172.16.1.2]) by cerberus.techfuel.com (8.9.3/8.9.3) with ESMTP id TAA26993 for ; Tue, 16 May 2000 19:14:58 -0700 (PDT) Received: (from root@localhost) by basilisk.techfuel.com (8.9.3/8.9.3) id TAA89913 for freebsd-hackers@freebsd.org; Tue, 16 May 2000 19:14:57 -0700 (PDT) Received: from phoenix.techfuel.com (phoenix.techfuel.com [172.16.1.19]) by basilisk.techfuel.com (8.9.3/8.9.3) with ESMTP id TAA89872 for ; Tue, 16 May 2000 19:14:57 -0700 (PDT) Received: from localhost (kehlet@localhost) by phoenix.techfuel.com (8.9.3/8.9.3) with ESMTP id TAA09056 for ; Tue, 16 May 2000 19:14:57 -0700 X-Authentication-Warning: phoenix.techfuel.com: kehlet owned process doing -bs Date: Tue, 16 May 2000 19:14:56 -0700 (PDT) From: Steven Kehlet To: freebsd-hackers@freebsd.org Subject: enabling -DNAMEBLOCK breaks biosboot build (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-scanner: scanned by Inflex 0.1.4 - (http://www.spyda.co.za/inflex) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I sent this to -questions but no one could help me. TIA if you can help me :-). With 3.4-STABLE code, cvsup'd on Tues May 9th, enabling -DNAMEBLOCK in /sys/i386/boot/biosboot/Makefile breaks the build: ... dd if=boot.nohdr of=boot2 bs=512 skip=1 14+1 records in 14+1 records out 7184 bytes transferred in 0.000439 secs (16362683 bytes/sec) boot2 is too big *** Error code 2 I'd like the NAMEBLOCK feature so I can use nextboot. Is there a new way to boot different kernels, or am I screwed? Thanks! :-) Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 20:33: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kestrel.prod.itd.earthlink.net (kestrel.prod.itd.earthlink.net [207.217.121.155]) by hub.freebsd.org (Postfix) with ESMTP id AEC5237B68A; Tue, 16 May 2000 20:33:03 -0700 (PDT) (envelope-from natepuri@office.ompages.com) Received: from laptop.ompages.com (pool0790.cvx21-bradley.dialup.earthlink.net [209.179.195.25]) by kestrel.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id UAA02932; Tue, 16 May 2000 20:32:59 -0700 (PDT) Received: from laptop.ompages.com (natepuri@localhost.ompages.com [127.0.0.1]) by laptop.ompages.com (8.9.3/8.9.3) with ESMTP id UAA12210; Tue, 16 May 2000 20:32:40 -0700 (PDT) Message-Id: <200005170332.UAA12210@laptop.ompages.com> Date: Tue, 16 May 2000 20:32:39 -0700 (PDT) From: Nate Puri Subject: 4.0 will not send out UDP packets To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org, undrgrid@undergrid.net MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've been having a number of problems with this 4.0 install. I'm running a program called ompages-dhid. It's a rewrite of the dhid.org client and server. My partner actually wrote it. He's a linux programmer and is trying to get this to work on free and open bsds... The openbsd port works fine, but the freebsd-4.0 port will not log to syslog, nor will it send out udp packets to server daemon. I'm getting the following messages. 'icmp-response bandwidth limit 350/200 pps' 'inetd[370] warning: can't get client address: Connection reset by peer' 'rlogind[370]: Can't get peer name of remote host: Socket is not connected' Any ideas. I could really use some help on this source code. If you can help me; I'll send you the source... it's open so that is not a problem.. Thanks... -nate -- Nate Puri, President Installation, Administration, Security BankofData.net (not yet live) and Support for Home and Small Networks... natepuri@office.ompages.com One of The Wheel's Massive Holdings To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 21:37: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id BBD3C37B54A for ; Tue, 16 May 2000 21:36:54 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FUO00FBISNP5T@falla.videotron.net> for hackers@FreeBSD.ORG; Wed, 17 May 2000 00:33:26 -0400 (EDT) Date: Wed, 17 May 2000 00:34:50 -0400 (EDT) From: Bosko Milekic Subject: Re: What do people think of maybe using the sourceforge software? In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Nick Hibma Cc: "Jordan K. Hubbard" , 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 On Tue, 16 May 2000, Nick Hibma wrote: > > I guess that most people leading a project could do with a bit of > feature creep, features being shoved under their noses. Even if at first > you think that source control solves all our problems, it still could be > a way to develop new tools and get them running and tried out before > committing them to the tree. > > Second, the projects page we have now, with all due respect to the > people that try to keep it reasonably organised, is a mess due to the > lack of updates. people only maintain their project pages perhaps, but > certainly not the links that lead to them. > > Being able to work with more people on the same project on an equal > bases would be a good idea IMHO. > > Nick > Although I have no control over what goes on behind the curtains, I must say the following: My feeling is that a lot of the doc people are working really hard to make this sort of stuff happen. I know, for instance, that Jeroen (Asmodai) has great ideas in place for centralization of project listings, and TODO lists, etc. The only thing left is to bind these ideas together and make things like this happen. One of the big issues, I feel, is the duplication of efforts and I, as a "guy who develops from the sidelines" can tell you right now: a centralized information-base such as the one [I believe] these people are working on is key to what I choose to poke at next. Please remember that a lot of people who contribute to the project are not necessarily committers and do not read -commiters mail. The centralization of documentation and various other data will make collaboration possible and, best of all, it'll make it fun (which is what open source is about for many of us). With the centralization of information will come direction. Cheers, Bosko. -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com bmilekic@dsuper.net * bmilekic@technokratis.com * b.milekic@marianopolis.edu "Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat and drink beer all day." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 22: 7:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A02937B620 for ; Tue, 16 May 2000 22:07:12 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA11944; Tue, 16 May 2000 23:06:51 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39222971.3030ED84@softweyr.com> Date: Tue, 16 May 2000 23:09:05 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Derick Fernando Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Com Port Issue References: <000001bfbf07$4d5733a0$8401a8c0@earthlink.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Derick Fernando wrote: > > Hello, > > I wrote a samll program to get weather from a Davis Net weather station > attached to a com port (/dev/cuaa0) in this case. It worked on Linux and > IRIX, I am wondering why it compiles and runs, but does not get any data > back from the device in FreeBSD. A minimal program that just listens for a > ACK (\006) from the station can be seen at http://east.dhs.org/test11.c > > If you know someone that could help me resolve this issue, please let me > know. See /usr/ports/comm/mlan. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue May 16 23:50:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 4F52E37B546 for ; Tue, 16 May 2000 23:50:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA11350; Tue, 16 May 2000 23:53:12 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Nick Hibma Cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: What do people think of maybe using the sourceforge software? In-reply-to: Your message of "Tue, 16 May 2000 22:51:22 BST." Date: Tue, 16 May 2000 23:53:12 -0700 Message-ID: <11347.958546392@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Second, the projects page we have now, with all due respect to the > people that try to keep it reasonably organised, is a mess due to the > lack of updates. people only maintain their project pages perhaps, but > certainly not the links that lead to them. > > Being able to work with more people on the same project on an equal > bases would be a good idea IMHO. Well, I have to say that I installed and played with sourceforge for awhile and it's, well, highly dedicated to being sourceforge. The various product links *all* point back to sourceforge.com relative addresses and there's no concept of "$PROJECTNAME" or "$PROJECTBASE" to customize the sourceforge software for someone else, like the FreeBSD project. It's very much an example of a "code straight to the goal and for one purpose" implementation and, unfortunately, thus completely unsuitable for our purposes without some major hackery. Maybe if we could find something else... - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 0:41: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id 7F4D837B9BC for ; Wed, 17 May 2000 00:41:03 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JPI33KDYW80003FH@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 17 May 2000 09:40:54 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 17 May 2000 09:40:49 +0100 Content-return: allowed Date: Wed, 17 May 2000 09:40:42 +0100 From: "Koster, K.J." Subject: RE: smb printer trouble To: 'Charlie Root' Cc: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D753C@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps there are some invisible spaces after some of the backslashes? Kees Jan ============================================== You are only young once, but you can stay immature all your life > -----Original Message----- > From: Charlie Root [mailto:root@jestocost.cosc.morrisville.edu] > Sent: dinsdag 16 mei 2000 20:39 > To: freebsd-hackers@FreeBSD.ORG > Subject: smb printer trouble > > > I wrote a simple filter to print to an nt print queue through > the smbclinet. It tests to see if the file is postscript or > text, and if it is text it sends a control code to tell the > printer to do the lf->crlf conversion. > > My problem is that the '\' escapes in the first line get clobbered. > for example, if I print this printcap: > > **** begin printcap **** > lp:\ > :sh:\ > :lp=/dev/lpt0:\ > :sd=/var/spool/output/lpd/lp:\ > :lf=/var/log/lpd/lpd.log: > > lplaser:\ > :sh:\ > :lp=/dev/null:\ > :if=/root/filters/smb-filter:\ > :sd=/var/spool/output/lpd/lplaser:\ > :lf=/var/log/lpd/lpd.log: > **** end printap **** > > the entire entry for "lp" will be on one line, but the "lplaser" > entry will print out like it is supposed to. > > I know why it is doing it, however I don't know how to fix it. Any > help will be appreciated (script is below). > > Thanks, > James > > **** begin smb-filter **** > #!/bin/sh > #### > # Input filter to print to a NT print queue, requires smbclient. > # > # Author: James Halstead, e-mail: JAHalstead@hotmail.com > # > # Read stdin to a temp, make sure to determine the print > type, then use > # smbclient to print to the nt queue. > #### > > SERVER= > PRINTER=cw > TEMP=/tmp/smbprint > > TEMP=`mktemp -q $TEMP.XXXXXX` > > read firstline > first_two=`expr "$firstline" : '\(..\)'` > > if [ "$first_two" != "%!" ]; then > printf "\033&k3G" > $TEMP > fi > > #lets see, copy the firstline to temp, cat the rest to the temp, > # make one ugly command to print the file to the smb printer then > # rm the temp file. > > echo "$firstline" >> $TEMP && cat >> $TEMP &&\ > /usr/local/bin/smbclient \\\\$SERVER\\$PRINTER -UGUEST -N\ > -c"print $TEMP" &&\ > rm -f $TEMP >/dev/null && exit 0 > > exit 1 > **** end smb-filter **** > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 1:18:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 4854137B745; Wed, 17 May 2000 01:18:43 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9D38F7.dip0.t-ipconnect.de [62.157.56.247]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id KAA29984; Wed, 17 May 2000 10:18:38 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id B4C41AC2C; Wed, 17 May 2000 10:18:49 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id KAA02548; Wed, 17 May 2000 10:18:44 +0200 (CEST) (envelope-from alex) Date: Wed, 17 May 2000 10:18:44 +0200 From: Alexander Langer To: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: newbus documentation Message-ID: <20000517101844.C493@cichlids.cichlids.com> References: <20000516224540.A16053@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000516224540.A16053@cichlids.cichlids.com>; from alex@big.endian.de on Tue, May 16, 2000 at 10:45:40PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To follow up myself, I got the first important comments from Matthew N. Dodd, which I will merge this evening. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 2:47:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id B76D437B64B for ; Wed, 17 May 2000 02:47:24 -0700 (PDT) (envelope-from gbnaidu@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id PAA29397 for ; Wed, 17 May 2000 15:16:04 +0530 (IST) Received: from pcd75.sasi.com ([10.0.16.75]) by sasi.com; Wed, 17 May 2000 15:16:02 +0000 (IST) Received: from localhost (gbnaidu@localhost) by pcd75.sasi.com (8.9.3/8.9.3) with ESMTP id PAA02384 for ; Wed, 17 May 2000 15:17:48 +0530 Date: Wed, 17 May 2000 15:17:48 +0530 (IST) From: "G.B.Naidu" To: freebsd-hackers@FreeBSD.org Subject: new comer... 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 am G.B. Naidu, a unix maniac. What is the discussion that's going on currently on this list? I have some simple question. Many of you might have written some hooks into the kernel. I wonder what are these hooks and how to write them? Can somebody help me to understand this. thanks --gb -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 6:14: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BB34F37BC2A for ; Wed, 17 May 2000 06:14:04 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA24962; Wed, 17 May 2000 09:14:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA06311; Wed, 17 May 2000 09:14:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 May 2000 09:14:03 -0400 (EDT) To: Issei Suzuki Cc: hackers@freebsd.org Subject: Re: SSE support for FreeBSD In-Reply-To: <20000516.234638.15656027.issei@issei.org> References: <20000516.234638.15656027.issei@issei.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14626.39292.549162.216866@grasshopper.cs.duke.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Issei Suzuki writes: > I add SSE support for FreeBSD 4.0-RELEASE and 5.0-CURRENT. Some more > work is needed everything to go well, but it works functionally now. > > The patches and documents are avaiable at: > > http://home.jp.freebsd.org/~issei/sse/sse.html > > Limitations: > - Multiprocessor system is not supported. > - There is no exception handler to deal with SSE Exceptions. > - No spaces are available for SSE registers in struct fpregs. So, we > cannot record SSE registers when dumping core, nor access to SSE > registers via procfs. > > Comments, bug reports etc. are welcome. Cool! Have you (or anybody else) considered using the PIII SIMD functionality for optimizing kernel bcopy/copyin/copyout and checksums? There are linux kernel patches for this at http://www.redhat.com/~mingo/mmx-patches I have a trivial user-level app which shows a bcopy speedup of between 40% (PIII Xeon, 733MHz) and 50% (PIII, 450MHz) when using the kni memcpy stolen from those patches rather than the bcopy from libc, so I think it could be worth looking into. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 6:52:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id 88F9637BB33; Wed, 17 May 2000 06:52:04 -0700 (PDT) (envelope-from dms@woland.wplus.net) Received: from woland.wplus.net (woland.wplus.net [195.131.0.39]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id RAA73690; Wed, 17 May 2000 17:51:59 +0400 (MSD) X-Real-To: freebsd-hackers@FreeBSD.ORG Received: (from dms@localhost) by woland.wplus.net (8.9.3/8.9.1/wplus.2) id RAA04686; Wed, 17 May 2000 17:51:59 +0400 (MSD) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Wed, 17 May 2000 17:51:59 +0400 (MSD) From: Dmitry Samersoff To: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: bpf question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have traffic metering program using bpf, it works fine on relatevly free net but looses about 30% of packets on havy loaded one. Could any body suggest me something? Thank you! -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 8:56:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id F3F7937B5AC for ; Wed, 17 May 2000 08:56:37 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA307990; Wed, 17 May 2000 11:56:34 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <14619.7058.880620.576742@smpbox> References: <14617.37135.323534.539710@smpbox> <14619.7058.880620.576742@smpbox> Date: Wed, 17 May 2000 11:56:56 -0400 To: Ted Buswell From: Garance A Drosihn Subject: Re: Looking for advice on lpr/lpd changes Cc: hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:56 PM -0400 5/11/00, Ted Buswell wrote: >I don't like the proposed idea (shell script mod of smb.conf) either, >however I was under the impression with your lpr mod you would also >bludgeon the user with 4*5*200 printer shares. > >I had thought that with your lpr mod, you still need to somehow add >the "printer/hm" variations into the list of shares presented by samba. > >Or am I missing a samba configuration option that permits the user to >specify the queue the job is sent to [instead of having them select >from a predefined list] ? We have enough regular printer queues that we ran into trouble presenting a list of shares to the user. (the problem might have only been under win95). Due to that, our users always connect directly to a printer share, they do not browse for it. They have to define a printer as \\sambasrv\unixptr Many of our users are laptop users, so they only add the printers they personally care about. The unix side needs to know all the printer names, but any given laptop (or even any of the PC's in our public labs) only have about 10 printers defined. I had not thought about browsing for printer shares. I'll try to keep that in mind too. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 9: 7:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from www0a.netaddress.usa.net (www0a.netaddress.usa.net [204.68.24.30]) by hub.freebsd.org (Postfix) with SMTP id 02C7437B7B7 for ; Wed, 17 May 2000 09:07:47 -0700 (PDT) (envelope-from joy.ganguly@usa.net) Received: (qmail 12769 invoked by uid 60001); 17 May 2000 16:07:46 -0000 Message-ID: <20000517160746.12768.qmail@www0a.netaddress.usa.net> Received: from 204.68.24.30 by www0a for [206.20.52.130] via web-mailer(34FM1.4.02C) on Wed May 17 16:07:46 GMT 2000 Date: 17 May 00 10:07:46 MDT From: Joy Ganguly To: freebsd-hackers@freeBSD.org Subject: Question about file write???? X-Mailer: USANET web-mailer (34FM1.4.02C) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, = i have written a special ioctl which writes data into a file from a buffe= r in kernel memory. it invokes fo->fo_write() and involves one copy from kerne= l mem to disk cache. however this takes substantially more time than an ordinar= y write which copies from user space to the disk cache. any explanations???= = thanx in advance = joy = ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 9:22:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 2C6D837BB9B for ; Wed, 17 May 2000 09:22:02 -0700 (PDT) (envelope-from danhil@cwnt.com) Received: from localnet.cwnt.co.il (ras3-p198.hfa.netvision.net.il [62.0.147.198]) by alpha.netvision.net.il (8.9.3/8.8.6) with SMTP id TAA06879 for ; Wed, 17 May 2000 19:21:01 +0300 (IDT) Received: from 192.168.0.46 ([192.168.0.46]) by localnet.cwnt.co.il (WinRoute 3.04g) with SMTP; Wed, 17 May 2000 19:15:42 +0300 Message-ID: <01ff01bfc023$b9324110$2e00a8c0@cwnt.co.il> From: "Daniel Hilevich" To: Subject: ATM adapter Date: Wed, 17 May 2000 19:17:05 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm looking to purchase an ATM adapter for my FreeBSD box. The two adapters specified in the "Integrating ATM networking into BSD" document (Adaptec ANA-59x0 & efficient ENI-155) are no longer available. My needs are simple: - PCI/ISA ATM adapter. - Compatibility with the en0 driver (or any other driver that exists for FreeBSD). Does anyone knows about such a device? Thank you, Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 9:32:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 58E8637BC9D for ; Wed, 17 May 2000 09:32:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA02578; Wed, 17 May 2000 18:32:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Daniel Hilevich" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ATM adapter In-reply-to: Your message of "Wed, 17 May 2000 19:17:05 +0200." <01ff01bfc023$b9324110$2e00a8c0@cwnt.co.il> Date: Wed, 17 May 2000 18:32:08 +0200 Message-ID: <2576.958581128@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Get the Fore PCA200 and use the "HARP" ATM code which is far more functional than the "Chuck ATM" code. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 9:40: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 433CE37B546 for ; Wed, 17 May 2000 09:40:02 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 31DA02DC0B; Wed, 17 May 2000 18:42:59 +0200 (CEST) Received: by mx.webgiro.com (Postfix, from userid 1001) id 92EE57817; Wed, 17 May 2000 18:36:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 90C9510E17; Wed, 17 May 2000 18:36:41 +0200 (CEST) Date: Wed, 17 May 2000 18:36:41 +0200 (CEST) From: Andrzej Bialecki To: Daniel Hilevich Cc: freebsd-hackers@freebsd.org Subject: Re: ATM adapter In-Reply-To: <01ff01bfc023$b9324110$2e00a8c0@cwnt.co.il> 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, 17 May 2000, Daniel Hilevich wrote: > Hi, > I'm looking to purchase an ATM adapter for my FreeBSD box. The two adapters > specified in the "Integrating ATM networking into BSD" document (Adaptec > ANA-59x0 & efficient ENI-155) are no longer available. > My needs are simple: > - PCI/ISA ATM adapter. > - Compatibility with the en0 driver (or any other driver that exists for > FreeBSD). The cards and the driver you mention is the old ATM implementation made by Chuck Cranor (sp?). There is much newer and much more sophisticated framework called HARP, which is part of FreeBSD beginning with, I think, 3.0-RELEASE. HARP supports (among others) Fore PCA-200e card which I use. See the docs in /usr/share/examples/atm. NOTE: this card requires loading a firmware each time it's initialized (after reboot). The firmware has to be _exactly_ the version that is mentioned in the HARP docs, because HARP drivers refer to locations in the binary image.. Also, be sure to set proper encapsulation on both sides of your link (e.g. LLC/SNAP). Other than that, the card works perfectly ok for me. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 9:52:33 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 00E6237B9A2 for ; Wed, 17 May 2000 09:52:25 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4HHPHZ15074; Wed, 17 May 2000 10:25:17 -0700 (PDT) Date: Wed, 17 May 2000 10:25:16 -0700 From: Alfred Perlstein To: Joy Ganguly Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about file write???? Message-ID: <20000517102516.B14968@fw.wintelcom.net> References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000517160746.12768.qmail@www0a.netaddress.usa.net>; from joy.ganguly@usa.net on Wed, May 17, 2000 at 10:07:46AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joy Ganguly [000517 09:41] wrote: > > hi all, > > i have written a special ioctl which writes data into a file from a buffer in > kernel memory. it invokes fo->fo_write() and involves one copy from kernel > mem > to disk cache. however this takes substantially more time than an ordinary > write which copies from user space to the disk cache. any explanations??? What are you using for your kernel to kernel copy? (copyin and friends are hand optimized for great speed when copying from/to userspace) -- -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 Wed May 17 10:46:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 6D38C37B587 for ; Wed, 17 May 2000 10:46:46 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id NAA99083; Wed, 17 May 2000 13:46:42 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <3922DB0F.9D9095C9@falcon.niksun.com> Date: Wed, 17 May 2000 13:46:55 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein , freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > * Joy Ganguly [000517 09:41] wrote: > > > > hi all, > > > > i have written a special ioctl which writes data into a file from a buffer in > > kernel memory. it invokes fo->fo_write() and involves one copy from kernel > > mem > > to disk cache. however this takes substantially more time than an ordinary > > write which copies from user space to the disk cache. any explanations??? > > What are you using for your kernel to kernel copy? > fo->fo_write uses uiomove() with seg_flg = UIO_SYSSPACE. uiomove() uses bcopy() to do the actual copying. my ioctl sets up the struct uio to point to the kernel buf and calls fo->fo_write(). Hence the only difference between my ioctl and original write is that the former has seg_flg = UIO_SYSSPACE and the latter has UIO_USERSPACE. > > (copyin and friends are hand optimized for great speed when copying > from/to userspace) > what sort of optimizations are you referrring to?? is there some other way i can do this?? > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 12: 0:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 836C537B55B for ; Wed, 17 May 2000 12:00:28 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by george.lbl.gov () id MAA05337 for hackers@freebsd.org; Wed, 17 May 2000 12:00:24 -0700 (PDT) Date: Wed, 17 May 2000 12:00:24 -0700 (PDT) From: Jin Guojun (FTG staff) Message-Id: <200005171900.MAA05337@george.lbl.gov> To: hackers@freebsd.org Subject: How to make system Sync Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a couple of system out of sync problems. (1) PCI sync problem: ATM adapter updates a buffer return pointer and generates intr, but when driver pulls out the information that updated by adapter, some memory in the last piece of the pool is garbage. e.g. head -> c0100000 tail -> c0100400 c0100000 -> buf0 c0100004 -> buf1 ... c0100100 -> bufn ... c0100160 -> bad address or 0 ... If I let driver tsleep() for a while, the problem can be improved. So, it looks like that adapter pushed (DMA) the data into memory, but not been seen by CPU right way due to the DMA sync issue. How can we sync the DMA transaction in BSD? (2) page fault trap does not show up right way: at #7, lock_ObtainSpin is defined as simple_lock(). Before this line, I put a line code -- char* psp = panicstr; to save the panicstr status, and we can see psp is NULL; i.e., "page fault" has not been trapped yet. Where a few instructions down to tsleep(), the panicstr is set to "page fault", but there is no code in the function _simple_lock() can cause page fault. So, the page should be happened at earlier time somewhere. For this problem, how can we enforce the page trap show up at right spot to catch the problem? -Jin ---------- core information ------ gdb -k kernel.4 vmcore.4 #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc0193059 in panic (fmt=0xc03646ef "page fault") at ../../kern/kern_shutdown.c:554 #2 0xc02c3b4a in trap_fatal (frame=0xc0380fa8, eva=112) at ../../i386/i386/trap.c:924 #3 0xc02c37fd in trap_pfault (frame=0xc0380fa8, usermode=0, eva=112) at ../../i386/i386/trap.c:817 #4 0xc02c3383 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 256, tf_esi = -1070028992, tf_ebp = -1070067700, tf_isp = -1070067756, tf_ebx = 0, tf_edx = 1073741824, tf_ecx = -1069825280, tf_eax = 1074236058, tf_trapno = 12, tf_err = 0, tf_eip = -1072080212, tf_cs = 8, tf_eflags = 66118, tf_esp = 768, tf_ss = -1070133429}) at ../../i386/i386/trap.c:423 #5 0xc0195aac in tsleep (ident=0xc038a740, priority=296, wmesg=0xc033f121 "slock", timo=200) at ../../kern/kern_synch.c:425 #6 0xc018e45e in _simple_lock (alp=0xc03e2e74, id=0xc0370f4b "../sdapi_streams.c", l=768) at ../../kern/kern_lock.c:604 #7 0xc02f7d60 in sd_stream_dispatch (apip=0xc0ec28c0, rockp=0xc03e2280, bufp=0xc0a58200, eventp=0xc0ee2400) at ../sdapi_streams.c:768 #8 0xc02f251b in sd_UpcallEvent (vcp=0xc0ec3200, eventp=0xc0ee2400, bufp=0xc0a58200) at sdapi.c:973 #9 0xc02f2630 in sd_DataCallback (vc_cookie=0xc0ec3100, contextp=0xc0ec3200, bufp=0xc0a58200, packet_arg=0x0) at sdapi.c:1024 #10 0xc02df683 in bcd_service_rbrq (rbrqi=0xc0d7cba8) at ../bcd_rx.c:1560 #11 0xc02e3a3e in bcd_he_intr (bu=0xc0d7b000) at ../FreeBSDK/bcd_he.c:632 (kgdb) up 6 #6 0xc018e45e in _simple_lock (alp=0xc03e2e74, id=0xc0370f4b "../sdapi_streams.c", l=768) at ../../kern/kern_lock.c:604 604 tsleep(&lockpausetime, PCATCH | PPAUSE, "slock", (kgdb) up #7 0xc02f7d60 in sd_stream_dispatch (apip=0xc0ec28c0, rockp=0xc03e2280, bufp=0xc0a58200, eventp=0xc0ee2400) at ../sdapi_streams.c:768 768 lock_ObtainSpin(&sd_user_lock); (kgdb) p psp $1 = 0x0 (kgdb) p panicstr $2 = 0xc03accc0 "page fault" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 13:12:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by hub.freebsd.org (Postfix) with SMTP id 147A937BCAA; Wed, 17 May 2000 13:12:20 -0700 (PDT) (envelope-from ira@MIT.EDU) Received: from GRAND-CENTRAL-STATION.MIT.EDU by MIT.EDU with SMTP id AA02721; Wed, 17 May 00 13:12:19 EST Received: from melbourne-city-street.MIT.EDU (MELBOURNE-CITY-STREET.MIT.EDU [18.69.0.45]) by grand-central-station.MIT.EDU (8.9.2/8.9.2) with ESMTP id OAA25635; Wed, 17 May 2000 14:12:19 -0400 (EDT) Received: from all-night-tool.mit.edu (ALL-NIGHT-TOOL.MIT.EDU [18.184.0.50]) by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id OAA21138; Wed, 17 May 2000 14:12:19 -0400 (EDT) Received: (from ira@localhost) by all-night-tool.mit.edu (8.9.3) id OAA23578; Wed, 17 May 2000 14:12:18 -0400 (EDT) Message-Id: <200005171812.OAA23578@all-night-tool.mit.edu> To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: Laptop support for the mss pcm driver. Date: Wed, 17 May 2000 14:12:18 -0400 From: Ira L Cooper Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those using the mss pcm driver on laptops, this a patch to fix the skipping and volume changes that happen after resuming from hiberation or suspension. Note that your laptop will not resume playing music until you close and re-open the sound device using these patches. The patch is available at http://www.mit.edu/~ira/mss.c.diff and it is relative to -STABLE but it should apply cleanly to -CURRENT. The patch is to src/sys/dev/sound/isa/mss.c. Please e-mail me with any comments on this patch. -Ira To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 13:22:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw2.MEIway.com (mgw2.meiway.com [212.73.210.74]) by hub.freebsd.org (Postfix) with ESMTP id 67ADD37BCD7 for ; Wed, 17 May 2000 13:22:09 -0700 (PDT) (envelope-from lconrad@go2france.com) Received: from memphis.go2france.com (nhd-01-209-142-71-149.sat.idworld.net [209.142.71.149]) by mgw2.MEIway.com (Postfix Relay Hub) with ESMTP id 672C4231 for ; Thu, 18 May 2000 00:38:01 +0200 (CEST) Message-Id: <4.3.1.0.20000517152410.00c344d0@mail.go2france.com> X-Sender: lconrad%go2france.com@mail.go2france.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 17 May 2000 15:26:31 +0200 To: freebsd-hackers@freebsd.org From: Len Conrad Subject: netgraph support for channelized LMC 1504 PCI 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 There was some talk about this back in March or so, leaving me rembering someone said that it wouldn't be too hard or long to do it. Has there been any progress? Len To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 13:24: 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 44A6F37BD2D for ; Wed, 17 May 2000 13:23:58 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4HKujP21003; Wed, 17 May 2000 13:56:45 -0700 (PDT) Date: Wed, 17 May 2000 13:56:44 -0700 From: Alfred Perlstein To: Joy Ganguly Cc: freebsd-hackers Subject: Re: Question about file write???? Message-ID: <20000517135644.D14968@fw.wintelcom.net> References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3922DB0F.9D9095C9@falcon.niksun.com>; from joy@niksun.com on Wed, May 17, 2000 at 01:46:55PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joy Ganguly [000517 11:19] wrote: > Alfred Perlstein wrote: > > > * Joy Ganguly [000517 09:41] wrote: > > > > > > hi all, > > > > > > i have written a special ioctl which writes data into a file from a buffer in > > > kernel memory. it invokes fo->fo_write() and involves one copy from kernel > > > mem > > > to disk cache. however this takes substantially more time than an ordinary > > > write which copies from user space to the disk cache. any explanations??? > > > > What are you using for your kernel to kernel copy? > > > > fo->fo_write uses uiomove() with seg_flg = UIO_SYSSPACE. uiomove() uses > bcopy() to do the actual copying. my ioctl sets up the struct uio to point to the > kernel buf and calls fo->fo_write(). Hence the only difference between my ioctl > and original write is that the former has seg_flg = UIO_SYSSPACE and the latter > has UIO_USERSPACE. > > > > > > > (copyin and friends are hand optimized for great speed when copying > > from/to userspace) > > > > what sort of optimizations are you referrring to?? is there some other way i can > do this?? bcopy should be using the hand optimized code, I think you may have to explain more of what you're doing if anyone is going to be able to help. -- -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 Wed May 17 13:26: 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 0A1EA37BD2D for ; Wed, 17 May 2000 13:25:59 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e4HKwrN21059; Wed, 17 May 2000 13:58:53 -0700 (PDT) Date: Wed, 17 May 2000 13:58:53 -0700 From: Alfred Perlstein To: Jin Guojun Cc: hackers@FreeBSD.ORG Subject: Re: How to make system Sync Message-ID: <20000517135853.E14968@fw.wintelcom.net> References: <200005171900.MAA05337@george.lbl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005171900.MAA05337@george.lbl.gov>; from jin@george.lbl.gov on Wed, May 17, 2000 at 12:00:24PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jin Guojun [000517 12:34] wrote: > I had a couple of system out of sync problems. > > (1) PCI sync problem: > ATM adapter updates a buffer return pointer and generates intr, > but when driver pulls out the information that updated by adapter, > some memory in the last piece of the pool is garbage. > e.g. > head -> c0100000 > tail -> c0100400 > > c0100000 -> buf0 > c0100004 -> buf1 > ... > c0100100 -> bufn > ... > c0100160 -> bad address or 0 > ... > > If I let driver tsleep() for a while, the problem can be improved. > So, it looks like that adapter pushed (DMA) the data into memory, > but not been seen by CPU right way due to the DMA sync issue. > How can we sync the DMA transaction in BSD? I think the way you accomplish this is by telling the adapter to generate an interrupt when it's completed its DMA operation, you seem to be generating interupts at the start instead of the end. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 13:42: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 13A2D37BCD7 for ; Wed, 17 May 2000 13:41:55 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id WAA04188; Wed, 17 May 2000 22:41:31 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Len Conrad Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: netgraph support for channelized LMC 1504 PCI card? In-reply-to: Your message of "Wed, 17 May 2000 15:26:31 +0200." <4.3.1.0.20000517152410.00c344d0@mail.go2france.com> Date: Wed, 17 May 2000 22:41:31 +0200 Message-ID: <4186.958596091@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.3.1.0.20000517152410.00c344d0@mail.go2france.com>, Len Conrad wri tes: >There was some talk about this back in March or so, leaving me rembering >someone said that it wouldn't be too hard or long to do it. > >Has there been any progress? I have still not received my hardware :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 13:45:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 2177E37BCE0; Wed, 17 May 2000 13:44:42 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9D38F7.dip0.t-ipconnect.de [62.157.56.247]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id WAA19129; Wed, 17 May 2000 22:44:32 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 1EE7AAC2C; Wed, 17 May 2000 22:44:44 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id WAA24228; Wed, 17 May 2000 22:44:40 +0200 (CEST) (envelope-from alex) Date: Wed, 17 May 2000 22:44:40 +0200 From: Alexander Langer To: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: newbus documentation Message-ID: <20000517224440.A24185@cichlids.cichlids.com> References: <20000516224540.A16053@cichlids.cichlids.com> <20000517101844.C493@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000517101844.C493@cichlids.cichlids.com>; from alex@big.endian.de on Wed, May 17, 2000 at 10:18:44AM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Second revision is online at http://big.endian.de/misc/newbus-intro.txt The led-driver is still in the tar.gz I posted yesterday, but this tar.gz still has version 1. Please, guys. READ IT! COMMENTS! Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 14:19:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.mobilix.dk (mail.mobilix.dk [194.234.53.85]) by hub.freebsd.org (Postfix) with ESMTP id D2D5137B8D9 for ; Wed, 17 May 2000 14:19:51 -0700 (PDT) (envelope-from vab@mail.mobilix.dk) Received: from lflat.vas.mobilix.dk (fw.mobilinfo.dk [194.234.53.10]) by mail.mobilix.dk (8.8.7/8.8.7) with ESMTP id LAA25091 for ; Tue, 16 May 2000 11:13:01 +0200 Date: Tue, 16 May 2000 11:14:44 +0200 (CEST) From: Vadim Belman X-Sender: vab@lflat.vas.mobilix.dk To: freebsd-hackers@freebsd.org Subject: kernel 'nproc' and 'proc' symbols in FreeBSD 3.x 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 Which symbols might be used instead of 'nproc' and 'proc' (which is FreeBSD 4.0 specific, as far as I understand) with FreeBSD 3.x kernels? I have a local port of ucd-snmp 4.1.1 with host resources module included which works fine but complains about this symbols on all 3.x boxes. -- /Voland Vadim Belman E-mail: voland@hobbes.bsd-dk.dk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 14:40:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (obie.softweyr.com [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id DCC4637BEDE; Wed, 17 May 2000 14:40:05 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.com (ip43.salt-lake-city6.ut.pub-ip.psi.net [38.27.95.43]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id PAA14146; Wed, 17 May 2000 15:39:54 -0600 (MDT) (envelope-from wes@softweyr.com) Message-ID: <39231213.62692C57@softweyr.com> Date: Wed, 17 May 2000 15:41:39 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dmitry Samersoff Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: bpf question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Samersoff wrote: > > I have traffic metering program using bpf, > it works fine on relatevly free net but looses about 30% > of packets on havy loaded one. > > Could any body suggest me something? A much faster processor? What kind of CPU/memory/network interface are you using? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 15:32:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 84E5037BC81 for ; Wed, 17 May 2000 15:32:29 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id SAA03622; Wed, 17 May 2000 18:32:25 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <39231E06.31DFB153@falcon.niksun.com> Date: Wed, 17 May 2000 18:32:38 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein , freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> <20000517135644.D14968@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > bcopy should be using the hand optimized code, I think you may have > to explain more of what you're doing if anyone is going to be able > to help. well this is what i am doing: i have a device buffer in contiguous physical memory. i want to write that buffer into a file disk. for that ive written a simple ioctl which works similar to the syscall write. except that it transfers from kernel space instead of user space. my user program calls this ioctl with the write file desc....the ioctl calls fp->f_ops->fo_write after setting up the uio to do the transfer. earlier the user code looked like:- fd=open("/dev/mydev",O_RDONLY); buf=malloc(BUFSIZE); read(fd,buf,BUFSIZE); w_fd=open("foo",O_WRONLY|O_CREAT); write(w_fd,buf,BUFSIZE); now the user program looks like: fd=open("/dev/mydev",O_RDONLY); ioctl(fd, MYDEVREAD, &size); w_fd=open("foo",O_WRONLY|O_CREAT); ioctl(w_fd,MYDEVWRITE,size); as a result of this the copy involved in the first read is eliminated. but it takes longer to do the 2nd ioctl than to do the write. if this does not explain what i am doing please let me know. thanx in advance > > -- > -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 Wed May 17 15:57: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 75A6C37BEA0 for ; Wed, 17 May 2000 15:57:02 -0700 (PDT) (envelope-from jin@portnoy.lbl.gov) Received: (from jin@localhost) by george.lbl.gov () id PAA25512; Wed, 17 May 2000 15:56:58 -0700 (PDT) Date: Wed, 17 May 2000 15:56:58 -0700 (PDT) From: Jin Guojun (FTG staff) Message-Id: <200005172256.PAA25512@george.lbl.gov> To: bright@wintelcom.net Subject: Re: How to make system Sync Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein stated: > > I had a couple of system out of sync problems. > > > > (1) PCI sync problem: > > ATM adapter updates a buffer return pointer and generates intr, > > but when driver pulls out the information that updated by adapter, > > some memory in the last piece of the pool is garbage. > > e.g. > > head -> c0100000 > > tail -> c0100400 > > > > c0100000 -> buf0 > > c0100004 -> buf1 > > ... > > c0100100 -> bufn > > ... > > c0100160 -> bad address or 0 > > ... > > > > If I let driver tsleep() for a while, the problem can be improved. > > So, it looks like that adapter pushed (DMA) the data into memory, > > but not been seen by CPU right way due to the DMA sync issue. > > How can we sync the DMA transaction in BSD? > > I think the way you accomplish this is by telling the adapter to > generate an interrupt when it's completed its DMA operation, you > seem to be generating interupts at the start instead of the end. I do not think I have control on when interrupt can be started. The interrupts are generated when either the # of buffers below the buffer threshold or the I/O packages greater than I/O threshold. In Solaris driver, a ddi_dma_sync() routine is used for DMA sync in this case: #define BCD_FLUSH_CACHE_FOR_HOST(dhandle, offset, length) \ ddi_dma_sync(dhandle, offset, length, DDI_DMA_SYNC_FORKERNEL) Only thing I am not clear is that reference manual says: For this adapter, the SDRAM_CTRL register "should" have LB_64_ENB bit set to 1. There is no further information on this register. I wonder this could cause the problem since majority PC motherboards have a 32-bit PCI local bus (LB). -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 16:39:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D8F8037B5B3 for ; Wed, 17 May 2000 16:39:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA28046; Wed, 17 May 2000 16:24:40 -0700 (PDT) (envelope-from dillon) Date: Wed, 17 May 2000 16:24:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200005172324.QAA28046@apollo.backplane.com> To: Joy Ganguly Cc: Alfred Perlstein , freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> <20000517135644.D14968@fw.wintelcom.net> <39231E06.31DFB153@falcon.niksun.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :i have a device buffer in contiguous physical memory. i want to write :that buffer into :a file disk. for that ive written a simple ioctl which works similar to :the syscall :write. except that it transfers from kernel space instead of user :space. my user :program calls this ioctl with the write file desc....the ioctl calls :fp->f_ops->fo_write after setting up the uio to do the transfer. : :earlier the user code looked like:- I think it would be a whole lot easier to implement mmap() on the device, then allow the user process to mmap() the device buffer and read() and write() it directly. I don't think you need to implement any ioctl's for this problem. fd = open device ptr = mmap(...) fd = open file read(fd, ptr, BUFSIZE) read from file, store into device buf ... write(fd, ptr, BUFSIZE) read from device buf, store into file -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 18:52:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outgoing.redshift.com (outgoing.redshift.com [216.228.2.99]) by hub.freebsd.org (Postfix) with ESMTP id 7A40837BCF2 for ; Wed, 17 May 2000 18:52:40 -0700 (PDT) (envelope-from yramin@redshift.com) Received: from mail.redshift.com (mail.redshift.com [216.228.2.86]) by outgoing.redshift.com (8.9.3/) with ESMTP id SAA21662 for ; Wed, 17 May 2000 18:52:38 -0700 Received: from atp.atpn.com (pm3-131.sj.redshift.com [216.200.48.131]) by mail.redshift.com (8.10.1/8.10.1) with SMTP id e4I1qaT23198 for ; Wed, 17 May 2000 18:52:36 -0700 From: Yann Ramin To: hackers@freebsd.org Subject: Cisco Port Grouping w/FreeBSD Date: Wed, 17 May 2000 18:47:40 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00051718521700.33266@atp.atpn.com> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a question for the networking gurus out there. How exactly would = you configure a FreeBSD machine connected to a Cisco switch with port groupin= g on two Ethernet channels? =20 Also, for future reference, the funny network delays on the switched netw= ork were solved. It turns out if you force the switch to 100/full on the por= t, the Intel PRO 100/B card will run at 100/half, since it assumes the switch is= a non-autonegotiating hub. Use auto select on both sides works very well. Yann --=20 -------------------------------------------------------------------- Yann Ramin=09=09=09atrus@atrustrivalie.eu.org Atrus Trivalie Productions=09www.atrustrivalie.eu.org =09=09=09=09irm.it.montereyhigh.com Monterey High IT=09=09www.montereyhigh.com ICQ =09=09=09=0946805627 AIM=09=09=09=09oddatrus Marina, CA=09 "All cats die. Socrates is dead. Therefore Socrates is a cat." =09- The Logician =09 =09# fortune "To be responsive at this time, though I will simply say, and therefore this is a repeat of what I said previously, that which I am unable to offer in response is based on information available to make no such statement." -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 20:27:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id F366137B540 for ; Wed, 17 May 2000 20:27:14 -0700 (PDT) (envelope-from halstead@dreamscape.com) Received: from halste07 (sA17-p51.dreamscape.com [209.217.195.242]) by io.dreamscape.com (8.9.3/8.8.4) with SMTP id XAA02147; Wed, 17 May 2000 23:26:08 -0400 (EDT) X-Dreamscape-Track-A: sA17-p51.dreamscape.com [209.217.195.242] X-Dreamscape-Track-B: Wed, 17 May 2000 23:26:08 -0400 (EDT) Message-ID: <002f01bfc079$1d0e1060$f2c3d9d1@halste07> From: "James Halstead" To: "Koster, K.J." Cc: References: <59063B5B4D98D311BC0D0001FA7E4522026D753C@l04.research.kpn.com> Subject: Re: smb printer trouble Date: Wed, 17 May 2000 23:28:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know it is happening because of the ``read firstline'' command. It is using the standard shell way of continuing a line using the '\' char and applying that to the input. That explains why only the first line is effected. Actually, if there is a way that I can read only the first two chars from the standard input that would solve the problem for nearly all the cases. I only need the first two chars to do my test, then I can leave the rest up to cat. It would be even better if sombody could tell me a way to push chars back on to the stdin stream that way I can completly avoid making a temporary file. Thanks, James (root@jestocost.cosc.morrisville.edu) ----- Original Message ----- From: "Koster, K.J." To: "'Charlie Root'" Cc: "'FreeBSD Hackers mailing list'" Sent: Wednesday, May 17, 2000 4:40 AM Subject: RE: smb printer trouble > Perhaps there are some invisible spaces after some of the backslashes? > > Kees Jan > > ============================================== > You are only young once, > but you can stay immature all your life > > > > -----Original Message----- > > From: Charlie Root [mailto:root@jestocost.cosc.morrisville.edu] > > Sent: dinsdag 16 mei 2000 20:39 > > To: freebsd-hackers@FreeBSD.ORG > > Subject: smb printer trouble > > > > **** begin smb-filter **** > > #!/bin/sh > > #### > > # Input filter to print to a NT print queue, requires smbclient. > > # > > # Author: James Halstead, e-mail: JAHalstead@hotmail.com > > # > > # Read stdin to a temp, make sure to determine the print > > type, then use > > # smbclient to print to the nt queue. > > #### > > > > SERVER= > > PRINTER=cw > > TEMP=/tmp/smbprint > > > > TEMP=`mktemp -q $TEMP.XXXXXX` > > > > read firstline > > first_two=`expr "$firstline" : '\(..\)'` > > > > if [ "$first_two" != "%!" ]; then > > printf "\033&k3G" > $TEMP > > fi > > > > #lets see, copy the firstline to temp, cat the rest to the temp, > > # make one ugly command to print the file to the smb printer then > > # rm the temp file. > > > > echo "$firstline" >> $TEMP && cat >> $TEMP &&\ > > /usr/local/bin/smbclient \\\\$SERVER\\$PRINTER -UGUEST -N\ > > -c"print $TEMP" &&\ > > rm -f $TEMP >/dev/null && exit 0 > > > > exit 1 > > **** end smb-filter **** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 20:52:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id CC27C37B703 for ; Wed, 17 May 2000 20:52:20 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for hackers@freebsd.org id 12sHMB-0007mr-00; Thu, 18 May 2000 04:52:19 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id EAA59943 for hackers@freebsd.org; Thu, 18 May 2000 04:52:19 +0100 (BST) (envelope-from jcm) Date: Thu, 18 May 2000 04:52:19 +0100 From: J McKitrick To: hackers@freebsd.org Subject: boot/kernel debugging Message-ID: <20000518045219.A59839@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've used softice for debugging under windows, and i was wondering if gdb offers similar capabilities. It seems the best way to debug the ECP parallel port problem is to step through the code during the boot phase. Can this be done, or is there too much timing-critical stuff going on then? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org I am a bomb technician. If you see me running, try to keep up. ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 22:24:34 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 A2F4237BAAC for ; Wed, 17 May 2000 22:24:31 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA76672 for ; Thu, 18 May 2000 01:25:21 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 18 May 2000 01:25:21 -0400 (EDT) From: Adam To: hackers@freebsd.org Subject: modules and newbus 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 got the impression that newbus would make it easier to make kernel modules out of things. What in general does it take to make something into a kld? I'm thinking of pcm for example. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 22:27:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 57F9237BB1D for ; Wed, 17 May 2000 22:27:05 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FUQ00EB2PT15G@falla.videotron.net> for freebsd-hackers@freebsd.org; Thu, 18 May 2000 01:27:01 -0400 (EDT) Date: Thu, 18 May 2000 01:28:28 -0400 (EDT) From: Bosko Milekic Subject: Re: leaking sockets (closure) In-reply-to: X-Sender: bmilekic@jehovah.technokratis.com To: Mike Silbersack Cc: freebsd-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 Hi Mike, On Wed, 17 May 2000, Mike Silbersack wrote: > Heh, that's sorta neat, I guess. It'll be interesting to find out if the > leak is due to the mbuf waiting in some way, or a totally unrelated bug > we're tickling. I'd almost guess the latter. I finally peeked at the tcp_timer stuff and quickly realized: `grep keepalive /etc/defaults/rc.conf' or, equivalently, `sysctl -A | grep keepalive' should quickly make things clear... :-) Notice the explicit initialization of always_keepalive to zero in tcp_timer.c, which is what at first glance tripped me off. (I have re-simulated the exhaustion and all seems fine). -Bosko -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com bmilekic@dsuper.net * bmilekic@technokratis.com * b.milekic@marianopolis.edu "Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat and drink beer all day." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 22:44:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from facmail.cc.gettysburg.edu (facmail.gettysburg.edu [138.234.4.150]) by hub.freebsd.org (Postfix) with ESMTP id C5F7637BBA7 for ; Wed, 17 May 2000 22:44:24 -0700 (PDT) (envelope-from s467338@gettysburg.edu) Received: from jupiter2 (jupiter2 [138.234.4.6]) by facmail.cc.gettysburg.edu (8.9.3/8.9.3) with SMTP id BAA26430; Thu, 18 May 2000 01:43:50 -0400 (EDT) Date: Thu, 18 May 2000 01:43:49 -0400 (EDT) From: Andrew Reiter X-Sender: s467338@jupiter2 To: Adam Cc: hackers@FreeBSD.ORG Subject: Re: modules and newbus 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 Just as a quite spot note... Im near completion on my KLD programming tutorial... Just got to push out a section or two more and then wait for a review and it will be ready for relaease. This will/should help many with their general questions regarding how to write KLDs and hopefully willhelp with questions regarding "is it useful to write a KLD".. Thanks andrew On Thu, 18 May 2000, Adam wrote: |I got the impression that newbus would make it easier to make kernel |modules out of things. What in general does it take to make something |into a kld? I'm thinking of pcm for example. | | | |To Unsubscribe: send mail to majordomo@FreeBSD.org |with "unsubscribe freebsd-hackers" in the body of the message | --------------------------------------------------------- Andrew Reiter Computer Security Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 22:50:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kbgroup.co.nz (gateway.kbgroup.co.nz [203.96.151.81]) by hub.freebsd.org (Postfix) with ESMTP id 09F7037BC48 for ; Wed, 17 May 2000 22:50:37 -0700 (PDT) (envelope-from dave.preece@kbgroup.co.nz) Received: from kb_exchange.kbgroup.co.nz ([202.202.203.10]) by gateway.kbgroup.co.nz with ESMTP id <115201>; Thu, 18 May 2000 18:06:03 +1200 Received: by internet.kbgroup.co.nz with Internet Mail Service (5.5.2650.21) id ; Thu, 18 May 2000 17:59:22 +1200 Message-ID: <67B808B0DD93D211ABEE0000B498356B02BBF9@internet.kbgroup.co.nz> From: Dave Preece To: hackers@freebsd.org Subject: Musings on ip checksumming MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 18 May 2000 18:05:56 +1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to write a simple static NAT, and have got a bit stuck with the new checksum in the IP header.... thing with me is that I'm not happy about something till I understand it (and it appears that the IP stack is well behaved and won't send something unless the IP checksum is right either). Looking into ping.c for an example we have a checksum calculator (in_cksum) that I have been trying to understand. It takes a header and adds all the 16 bit words to a 32 bit acumulator. Fine. It then takes the top 16 bits and adds them to the bottom 16, (adding an additional one if this operation itself takes the resulting number to 17). Not what I understand as a checksum, but none the less a perfectly valid algorithm. What I *don't* understand is this: The routine appears to be written as if would only work on a big endian system i.e. this would only work if u_short's and int's were stored most significant byte first. This impression is further underscored by using >> 16 to fold the top 16 bits into the lower 16 bits. The pile of htons calls and ntohs calls I was expecting to see is simply not there. So, how come it works? Dave :) (but a bit confused) Ref: /usr/src/sbin/ping/ping.c /usr/src/lib/libalias/alias_local.h (ADJUST_CHECKSUM) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 23: 7:39 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 B084F37BD22 for ; Wed, 17 May 2000 23:07:37 -0700 (PDT) (envelope-from bmilekic@dsuper.net) Received: from modemcable009.62-201-24.mtl.mc.videotron.net ([24.201.62.9]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0FUQ009RSRKN5L@field.videotron.net> for freebsd-hackers@freebsd.org; Thu, 18 May 2000 02:05:11 -0400 (EDT) Date: Thu, 18 May 2000 02:06:38 -0400 (EDT) From: Bosko Milekic Subject: socket leak(s)... X-Sender: bmilekic@jehovah.technokratis.com To: silby@silby.com Cc: freebsd-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 I'm afraid my earlier message was incorrect. This is _still_ an issue... (the always_keepalive is unrelated) ... appologies; and tomorrow will be back to poking around day. -- Bosko Milekic * pages.infinit.net/bmilekic/index.html * www.technokratis.com bmilekic@dsuper.net * bmilekic@technokratis.com * b.milekic@marianopolis.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 23:10:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wcug.wwu.edu (sloth.wcug.wwu.edu [140.160.164.200]) by hub.freebsd.org (Postfix) with SMTP id 80BF737BD26 for ; Wed, 17 May 2000 23:10:46 -0700 (PDT) (envelope-from tcole@wcug.wwu.edu) Received: (qmail 19062 invoked by uid 1085); 18 May 2000 06:10:44 -0000 Date: Wed, 17 May 2000 23:10:44 -0700 From: Travis Cole To: Dmitry Samersoff Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: bpf question Message-ID: <20000517231043.A13544@wcug.wwu.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: ; from dms@wplus.net on Wed, May 17, 2000 at 05:51:59PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 17, 2000 at 05:51:59PM +0400, Dmitry Samersoff wrote: > I have traffic metering program using bpf, > it works fine on relatevly free net but looses about 30% > of packets on havy loaded one. Are you doing dns lookups? Don't do those and you may fix your problem. > > Could any body suggest me something? > > Thank you! > > -- > Dmitry Samersoff, dms@wplus.net, ICQ:3161705 > http://devnull.wplus.net > * There will come soft rains ... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- --Travis "Linux is something for Windows haters, BSD is something for Unix lovers" (Heike S., Febr. 98) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed May 17 23:27:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5063E37BD28 for ; Wed, 17 May 2000 23:27:24 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA29185; Wed, 17 May 2000 23:27:19 -0700 (PDT) (envelope-from dillon) Date: Wed, 17 May 2000 23:27:19 -0700 (PDT) From: Matthew Dillon Message-Id: <200005180627.XAA29185@apollo.backplane.com> To: Dave Preece Cc: hackers@FreeBSD.ORG Subject: Re: Musings on ip checksumming References: <67B808B0DD93D211ABEE0000B498356B02BBF9@internet.kbgroup.co.nz> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm trying to write a simple static NAT, and have got a bit stuck with the :new checksum in the IP header.... thing with me is that I'm not happy about :something till I understand it (and it appears that the IP stack is well :behaved and won't send something unless the IP checksum is right either). : :Looking into ping.c for an example we have a checksum calculator (in_cksum) :that I have been trying to understand. It takes a header and adds all the 16 :bit words to a 32 bit acumulator. Fine. It then takes the top 16 bits and :adds them to the bottom 16, (adding an additional one if this operation :itself takes the resulting number to 17). Not what I understand as a :checksum, but none the less a perfectly valid algorithm. : :What I *don't* understand is this: The routine appears to be written as if :would only work on a big endian system i.e. this would only work if :u_short's and int's were stored most significant byte first. This impression :is further underscored by using >> 16 to fold the top 16 bits into the lower :16 bits. The pile of htons calls and ntohs calls I was expecting to see is :simply not there. : :So, how come it works? : :Dave :) (but a bit confused) : : :Ref: :/usr/src/sbin/ping/ping.c :/usr/src/lib/libalias/alias_local.h (ADJUST_CHECKSUM) All the wierdness is because an IP checksum is a 1's complement summation (not the 2's complement summation we are used to in the digital world). Some of the earliest computers built used 1's complement to store numbers. In 1's complement arithmatic there are two 0's. Take an 8 bit number: 00000000 is a zero, and 11111111 also means zero. Thus when you add two numbers together and get a carry, you have to add it back in. 11111111 + 1 == zero + 1 == one, which is represented by 00000001. (In 2's complement addition there is only one zero, 00000000. 1111111 means -1. -1 + 1 == 0 (00000000), so you do not add the carry back in). An IP checksum is a 16 bit checksum. That is, you do 1's complement summation of each 16 bit word in the packet. It turns out, however, that if you have 32 bit wide registers you can optimize this code to sum 32 bit words and then 'fold' the high word into the low word when you are done. Since the order of the summation doesn't matter, it also doesn't matter which order the two 16 bit halves wind up being in. You get the same result when you fold it. It also turns out that we don't care whether the byte-ordering within the 16 bit word is little or big endian -- the answer is the same either way. The low and high byte of the 16 bit checksum will wind up correct on both a big and little endian machine simply by virtue of the fact that if the words in the packet are in the wrong byte order, the checksum will also wind up in the wrong byte order (and thus be laid out in the RIGHT order). This is a side effect of 1's complement arithmatic -- the symetry between upper and lower bytes in the word does NOT exist with 2's complement arithmatic. For example, take a packet laid out like this: A3 43 23 F7 Little endian: 0x43A3 0xF723 1's complement: 0x43A3 + 0xF723 = 0x13AC6 = 0x3AC7 Result: 0x3AC7, which little-endian is laid out: 3A C7 Big endian: 0xA343 0x23F7 1's complement: 0xA343 0x23F7 = 0xC73A = 0xC73A Result: 0xC73A, which big-endian is laid out: 3A C7 (identical!) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 1:34:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hamsadvani.serc.iisc.ernet.in (hamsadvani.serc.iisc.ernet.in [144.16.79.131]) by hub.freebsd.org (Postfix) with ESMTP id 6702C37BBD0 for ; Thu, 18 May 2000 01:34:07 -0700 (PDT) (envelope-from sureshhl@hamsadvani.serc.iisc.ernet.in) Received: from localhost (sureshhl@localhost) by hamsadvani.serc.iisc.ernet.in (8.9.3/8.9.3) with ESMTP id NAA19556 for ; Thu, 18 May 2000 13:02:39 GMT Date: Thu, 18 May 2000 13:02:39 +0000 (CUT) From: "Suresha H.L." To: hackers@freebsd.org Subject: Sir,one enquiry about Hostile Applets 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 sir, I am Suresh.H.L. working as proj. asst. at Indian Institute of Science, Bangalore. under Supercomputer education and research center chairman Prof. Balakrishnan.N.< http://www.iisc.ernet.in/serc> I want to know that is there is any Indian who developed any Hostile applets, if yes i want to know his name and Name of that Hostile applets and details about that. Please do this favour for me sir Sorry for troubling you -Suresh ._._._._._._._._._._._._._._._._._._._._._._._._._. SURESH.H.L. SERC,IISc Ph : (off)3092896 E-MAIL : sureshhl@mmsl.serc.iisc.ernet.in suresha_hl@yahoo.com ._._._._._._._._._._._._._._._._._._._._._._._._._. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 2:32:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 42E5D37B644; Thu, 18 May 2000 02:32:09 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p09-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.10]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id SAA28651; Thu, 18 May 2000 18:31:46 +0900 (JST) Message-ID: <3923B8D7.FE5A8583@newsguy.com> Date: Thu, 18 May 2000 18:33:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexander Langer Cc: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: newbus documentation References: <20000516224540.A16053@cichlids.cichlids.com> <20000517101844.C493@cichlids.cichlids.com> <20000517224440.A24185@cichlids.cichlids.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote: > > Second revision is online at > http://big.endian.de/misc/newbus-intro.txt > > The led-driver is still in the tar.gz I posted yesterday, but this > tar.gz still has version 1. > > Please, guys. READ IT! COMMENTS! DRIVER_MODULE(9)??? Isn't it driver(9) you are talking about? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 3: 0: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8680937B7EF; Thu, 18 May 2000 02:59:52 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p09-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.10]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id SAA05345; Thu, 18 May 2000 18:59:45 +0900 (JST) Message-ID: <3923BF66.398B3A9A@newsguy.com> Date: Thu, 18 May 2000 19:01:10 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Alexander Langer Cc: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: newbus documentation References: <20000516224540.A16053@cichlids.cichlids.com> <20000517101844.C493@cichlids.cichlids.com> <20000517224440.A24185@cichlids.cichlids.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote: > > Second revision is online at > http://big.endian.de/misc/newbus-intro.txt > > The led-driver is still in the tar.gz I posted yesterday, but this > tar.gz still has version 1. > > Please, guys. READ IT! COMMENTS! Also, don't use abbreviations such as JFYI. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 3: 8:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f110.law8.hotmail.com [216.33.241.110]) by hub.freebsd.org (Postfix) with SMTP id 08AB637B7EF for ; Thu, 18 May 2000 03:08:22 -0700 (PDT) (envelope-from dylan_parker69@hotmail.com) Received: (qmail 58325 invoked by uid 0); 18 May 2000 09:41:37 -0000 Message-ID: <20000518094137.58324.qmail@hotmail.com> Received: from 148.233.166.77 by www.hotmail.com with HTTP; Thu, 18 May 2000 02:41:37 PDT X-Originating-IP: [148.233.166.77] From: "Dylan parker" To: freebsd-hackers@FreeBSD.ORG Subject: i have 4 pwd.db Date: Thu, 18 May 2000 09:41:37 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I want desencrypt the files pwd.db Help me please ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 3:13:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1-ext.oskarmobil.cz (smtp1-ext.oskarmobil.cz [195.47.29.137]) by hub.freebsd.org (Postfix) with ESMTP id A417B37B524; Thu, 18 May 2000 03:13:35 -0700 (PDT) (envelope-from milon.papezik@oskarmobil.cz) Received: from wh01ex02.ceskymobil.cz (exchange.ceskymobil.cz [172.20.128.42]) by smtp1-ext.oskarmobil.cz (8.9.3/8.9.3) with ESMTP id MAA26543; Fri, 19 May 2000 12:10:58 +0200 (CEST) Received: from oskarmobil.cz (papezik.ceskymobil.cz [172.20.128.9]) by wh01ex02.ceskymobil.cz with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id LB625KH2; Thu, 18 May 2000 12:12:12 +0200 Message-ID: <3923C0B0.E71C344D@oskarmobil.cz> Date: Thu, 18 May 2000 12:06:40 +0200 From: Milon Papezik X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: cz, cs, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: ASN.1 parsing in OpenSSL (Apache+mod_ssl problem) References: <3923BD52.7275ACF8@oskarmobil.cz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Yesterday, I installed on the 4.0R server the apache13-php3 port with mod_ssl (using 4.0R ports skeleton) and it seems that I run into similar problem. When I try to connect with Netscape 4.x or Exploder 5 to Apache over SSL I get the following errors in apache_ssl_engine.log: [18/May/2000 16:40:17 65027] [info] Init: Initializing OpenSSL library [18/May/2000 16:40:17 65027] [info] Init: Loading certificate & private key of SSL-aware server www.xxxxxx.cz:443 [18/May/2000 16:40:17 65027] [info] Init: Seeding PRNG with 136 bytes of entropy [18/May/2000 16:40:17 65027] [info] Init: Generating temporary RSA private keys (512/1024 bits) [18/May/2000 16:40:18 65027] [info] Init: Configuring temporary DH parameters (512/1024 bits) [18/May/2000 16:40:22 65038] [info] Init: 2nd startup round (already detached) [18/May/2000 16:40:22 65038] [info] Init: Reinitializing OpenSSL library [18/May/2000 16:40:22 65038] [info] Init: Seeding PRNG with 136 bytes of entropy [18/May/2000 16:40:22 65038] [info] Init: Configuring temporary RSA private keys (512/1024 bits) [18/May/2000 16:40:22 65038] [info] Init: Configuring temporary DH parameters (512/1024 bits) [18/May/2000 16:40:22 65038] [info] Init: Initializing (virtual) servers for SSL [18/May/2000 16:40:22 65038] [info] Init: Configuring server www.xxxxxx.cz:443 for SSL protocol [18/May/2000 16:40:58 65057] [info] Connection to child 2 established (server www.xxxxxx.cz:443, client 172.20.128.10) [18/May/2000 16:40:58 65057] [info] Seeding PRNG with 1160 bytes of entropy [18/May/2000 16:40:58 65057] [error] SSL handshake failed (server www.xxxxxx.cz:443, client 172.20.128.10) (OpenSSL library error follows) [18/May/2000 16:40:58 65057] [error] OpenSSL: error:1409B004:SSL routines:SSL3_SEND_SERVER_KEY_EXCHANGE:nested asn1 error [18/May/2000 16:40:58 65058] [info] Connection to child 3 established (server www.xxxxxx.cz:443, client 172.20.128.10) [18/May/2000 16:40:58 65058] [info] Seeding PRNG with 1160 bytes of entropy [18/May/2000 16:40:58 65058] [error] SSL handshake failed (server www.xxxxxx.cz:443, client 172.20.128.10) (OpenSSL library error follows) [18/May/2000 16:40:58 65058] [error] OpenSSL: error:140BB004:SSL routines:SSL_RSA_PRIVATE_DECRYPT:nested asn1 error The first error happens only with Netscape, the both errors show up for Exploder. This happens regardless of using the SnakeOil test certifikate or using propper certifikace issued by VeriSign. The VeriSign cerifikate works without any problems on my 3.4R server with Apache13-php3 server from 3.4R ports. Is the apache port broken or is it openssl problem? Or is it another well know issue :-( Thanks in advance, any help will be greatly appreciated. Milon -- milon.papezik@oskarmobil.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 3:41:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 318E237B6F3; Thu, 18 May 2000 03:41:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id DAA23478; Thu, 18 May 2000 03:41:07 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 18 May 2000 03:41:07 -0700 (PDT) From: Kris Kennaway To: Milon Papezik Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: ASN.1 parsing in OpenSSL (Apache+mod_ssl problem) In-Reply-To: <3923C0B0.E71C344D@oskarmobil.cz> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 May 2000, Milon Papezik wrote: > When I try to connect with Netscape 4.x or Exploder 5 to Apache over > SSL I get the following errors in apache_ssl_engine.log: I need to compare the contents of a working and non-working certificate - my suspicion is that theres something off about the ASN.1 encoding of the certificate that causes netscape to barf (IE will apparently still read it fine, or it can at least for some people's certs). Install the converters/dumpasn1 port, and run the following on your certificate.pem file: openssl asn1parse -in cert.pem -out cert.der dumpasn1 cert.der > cert.out and mail me cert.out. Do this for both certificates if you have a working and non-working one. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 3:47:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 55AF737BE3A for ; Thu, 18 May 2000 03:47:34 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p09-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.10]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id TAA17558; Thu, 18 May 2000 19:47:25 +0900 (JST) Message-ID: <3923CA91.F7761CED@newsguy.com> Date: Thu, 18 May 2000 19:48:49 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Dylan parker Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i have 4 pwd.db References: <20000518094137.58324.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dylan parker wrote: > > I want desencrypt the files pwd.db Help me please Password files are not decryptable by design. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@another.bsdconspiracy.org "Sentience hurts." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 5:46:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 169C137BDED for ; Thu, 18 May 2000 05:46:42 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-u1-32.hitter.net [207.192.78.32]) by pawn.primelocation.net (Postfix) with ESMTP id 5D1F09B1E; Thu, 18 May 2000 08:46:36 -0400 (EDT) Date: Thu, 18 May 2000 08:46:35 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: "Daniel C. Sobral" Cc: Dylan parker , freebsd-hackers@FreeBSD.ORG Subject: Re: i have 4 pwd.db In-Reply-To: <3923CA91.F7761CED@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 May 2000, Daniel C. Sobral wrote: > Dylan parker wrote: > > > > I want desencrypt the files pwd.db Help me please > > Password files are not decryptable by design. > And encrypted passwords are not stored in pwd.db (see spwd.db) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 8:44:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 82D0237B50D for ; Thu, 18 May 2000 08:44:56 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id LAA13161; Thu, 18 May 2000 11:44:53 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <39241002.1F03763A@falcon.niksun.com> Date: Thu, 18 May 2000 11:45:06 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon , freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> <20000517135644.D14968@fw.wintelcom.net> <39231E06.31DFB153@falcon.niksun.com> <200005172324.QAA28046@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > I think it would be a whole lot easier to implement mmap() on the > device, then allow the user process to mmap() the device buffer > and read() and write() it directly. I don't think you need to > implement any ioctl's for this problem. > > fd = open device > ptr = mmap(...) > > fd = open file > read(fd, ptr, BUFSIZE) read from file, store into device buf > ... > write(fd, ptr, BUFSIZE) read from device buf, store into file > > I can do that but will it improve performance? right now the ioctl which does the write takes substantially more time than the normal write from user space. Is this because the previous read touches the user space buffer and hence it is in the cache?? i am not very sure on this . any suggestions?? thanx in advance joy > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 8:55: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 0982B37BE5B for ; Thu, 18 May 2000 08:55:03 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id LAA13311 for ; Thu, 18 May 2000 11:54:56 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <3924125D.20A907D@falcon.niksun.com> Date: Thu, 18 May 2000 11:55:09 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> <20000517135644.D14968@fw.wintelcom.net> <39231E06.31DFB153@falcon.niksun.com> <200005172324.QAA28046@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I think it would be a whole lot easier to implement mmap() on the > device, then allow the user process to mmap() the device buffer > and read() and write() it directly. I don't think you need to > implement any ioctl's for this problem. > > fd = open device > ptr = mmap(...) > > fd = open file > read(fd, ptr, BUFSIZE) read from file, store into device buf > ... > write(fd, ptr, BUFSIZE) read from device buf, store into file > > I am sorry that i missed this point in my previous post. well the problem with the mmap is that my device does not have a buffer always. earlier the 'read' ioctl on the device used to sleep till a buffer was available. what does the mmap do?? can it block?? i am sorry if this sounds naive bcoz i am a relative newbie thanx in advance -joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 9:25:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5FE0D37BF3C for ; Thu, 18 May 2000 09:25:49 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA32892; Thu, 18 May 2000 09:25:49 -0700 (PDT) (envelope-from dillon) Date: Thu, 18 May 2000 09:25:49 -0700 (PDT) From: Matthew Dillon Message-Id: <200005181625.JAA32892@apollo.backplane.com> To: freebsd-hackers@FreeBSD.ORG Subject: Old linux archives Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest lwn (http://lwn.net/) has a reference to a bunch of old Linux archives that were found and posted by Alan Cox. ftp://ftp.linux.org.uk/pub/linux/alan/Old-Funet-Lists/ Just in case people didn't know, way back then I was pretty heavy into Linux, before FreeBSD stole my heart :-). The '93 archives contains hundreds of postings from yours truely, if you want to see what I was doing back in '93. It should come as no surprise that I was hip deep in the kernel :-) But, man oh man, we were all a hellofalot younger back then! Scarrrrry. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 9:59:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 7B6B237BBD1 for ; Thu, 18 May 2000 09:59:13 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id JAA30021 for hackers@freebsd.org; Thu, 18 May 2000 09:58:51 -0700 Date: Thu, 18 May 2000 09:58:50 -0700 From: Arun Sharma To: hackers@freebsd.org Subject: file creation times ? Message-ID: <20000518095850.A29991@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any reason why FreeBSD doesn't store file creation times on the disk (apart from historical reasons) ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 10: 5: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 9DE0237BADC for ; Thu, 18 May 2000 10:04:57 -0700 (PDT) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id VAA25493; Thu, 18 May 2000 21:04:52 +0400 (MSD) Message-Id: <200005181704.VAA25493@aaz.links.ru> Subject: Re: file creation times ? In-Reply-To: <20000518095850.A29991@sharmas.dhs.org> from "Arun Sharma" at "May 18, 0 09:58:50 am" To: adsharma@sharmas.dhs.org (Arun Sharma) Date: Thu, 18 May 2000 21:04:52 +0400 (MSD) Cc: hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma writes: > Is there any reason why FreeBSD doesn't store file creation times on > the disk (apart from historical reasons) ? in adddition to atime, ctime and mtime? -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 10:35:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id A501237B8B3 for ; Thu, 18 May 2000 10:35:34 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id KAA30107; Thu, 18 May 2000 10:35:11 -0700 Date: Thu, 18 May 2000 10:35:11 -0700 From: Arun Sharma To: "Aleksandr A.Babaylov" Cc: hackers@FreeBSD.ORG Subject: Re: file creation times ? Message-ID: <20000518103511.A30100@sharmas.dhs.org> References: <20000518095850.A29991@sharmas.dhs.org> <200005181704.VAA25493@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <200005181704.VAA25493@aaz.links.ru>; from Aleksandr A.Babaylov on Thu, May 18, 2000 at 09:04:52PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 18, 2000 at 09:04:52PM +0400, Aleksandr A.Babaylov wrote: > Arun Sharma writes: > > Is there any reason why FreeBSD doesn't store file creation times on > > the disk (apart from historical reasons) ? > in adddition to atime, ctime and mtime? struct timespec st_atimespec; /* time of last access */ struct timespec st_mtimespec; /* time of last data modification */ struct timespec st_ctimespec; /* time of last file status change */ None of them tell me when the file was created. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 11:50: 0 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 4953837B721 for ; Thu, 18 May 2000 11:49:57 -0700 (PDT) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.9.3/8.9.3) id OAA80482 for freebsd-hackers@freebsd.org; Thu, 18 May 2000 14:49:55 -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: Thu, 18 May 2000 14:49:50 -0400 (EDT) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: freebsd-hackers@freebsd.org Subject: tconv and friends Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed that tconv is marked as broken in /usr/src/usr.bin/Makefile. Is there any interest in reviving this program? Or may be it makes more sense to start building tic, infocmp and others from ncurses source as part of the buildworld? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 13: 5:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from io.dreamscape.com (io.dreamscape.com [206.64.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 79F3B37B92E for ; Thu, 18 May 2000 13:05:53 -0700 (PDT) (envelope-from halstead@dreamscape.com) Received: from halste07 (sA15-p42.dreamscape.com [209.217.195.105]) by io.dreamscape.com (8.9.3/8.8.4) with SMTP id QAA22135; Thu, 18 May 2000 16:04:39 -0400 (EDT) X-Dreamscape-Track-A: sA15-p42.dreamscape.com [209.217.195.105] X-Dreamscape-Track-B: Thu, 18 May 2000 16:04:39 -0400 (EDT) Message-ID: <000701bfc104$96206a80$69c3d9d1@halste07> From: "James Halstead" To: Cc: References: <3923D7A2.55A0@funbox.demon.co.uk> Subject: Re: smb printer trouble Date: Thu, 18 May 2000 16:06:40 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, and no-thanks at the same time ;) The 'push back' will help (so I can avoid the temp file) and I will put that in. However, my filter is doing just fine on postscript files (and since it is a postscript pinter I don't have to put it through gs). The problem is with _non_ postscript files where the first line contains the '\' char at the end of the line, the read procedure sees that as "chomp the newline, and keep going as if the line never ended" I need to see if there is a way to avoid that behavior so my filter can print all files without messing them up ;) Thanks for the 'push back' help though! James. ----- Original Message ----- From: To: "James Halstead" Sent: Thursday, May 18, 2000 7:44 AM Subject: Re: smb printer trouble > > > Actually, if there is a way that I can read only the first two > > chars from the standard input that would solve the problem for > > nearly all the cases. I only need the first two chars to do my > > test, then I can leave the rest up to cat. It would be even better > > if sombody could tell me a way to push chars back on to the stdin > > stream that way I can completly avoid making a temporary file. > > I don't know if this will help; I filched it from a simple printer > filter example that is somewhere in the distribution. It's a shell > script that checks the first few characters (on stdin) to see if it's > getting a PostScript file or something else. > > #!/bin/sh > > Esc="\033" > > printf "${Esc}E" || { > logger "lp filter: error resetting printer" > printf "lp filter: error resetting printer\n" >&2 > exit 0 # delete job from queue > } > > read First_line > Magic=$(expr "$First_line" : '\(....\)') > > case $Magic in > > %!PS) > /usr/local/bin/gs -dSAFER -dNOPAUSE -q -sDEVICE=cdj550 \ > -sPAPERSIZE=a4 -sOutputFile=- - && exit 0 > ;; > > ~lpx) > Found_end=0 > Type=nil > while [ ${Found_end} -eq 0 ] > do > read Keyword Value > case ${Keyword} in > type) Type=${Value};; > > ... and so on. > > If the first 4 characters ('$Magic') are '%!PS', everything from stdin > is slurped up by /usr/local/bin/gs, which interprets it to stdout and > then exits. > > You'll notice that the first line of stdin does not go to gs (which > doesn't need it). If it had been necessary to 'push back' that first > line, it would have been easy, e.g.: > > (echo $First_line; cat) | /usr/local/bin/gs > > > > > I hope this has been of some help... > > -- Tim Jackson > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 13:38:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id EFD2D37B9DA; Thu, 18 May 2000 13:38:41 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9D38D8.dip0.t-ipconnect.de [62.157.56.216]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id WAA12885; Thu, 18 May 2000 22:38:29 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 288E1AC2C; Thu, 18 May 2000 22:38:50 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id WAA16429; Thu, 18 May 2000 22:38:46 +0200 (CEST) (envelope-from alex) Date: Thu, 18 May 2000 22:38:46 +0200 From: Alexander Langer To: doc@freebsd.org, hackers@freebsd.org Subject: request for review: bus_alloc_resource(9) Message-ID: <20000518223846.A16098@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I've written bus_alloc_resource(9). I need one with _experience_ on newbus to review it. http://big.endian.de/FreeBSD/bus_alloc_resource.9 Thanks! Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 14:42:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 49DF537B923; Thu, 18 May 2000 14:42:55 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA45436; Thu, 18 May 2000 17:42:43 -0400 (EDT) Date: Thu, 18 May 2000 17:42:43 -0400 (EDT) From: "Matthew N. Dodd" To: Alexander Langer Cc: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) In-Reply-To: <20000518223846.A16098@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 May 2000, Alexander Langer wrote: > I've written bus_alloc_resource(9). > > I need one with _experience_ on newbus to review it. > > http://big.endian.de/FreeBSD/bus_alloc_resource.9 You still don't understand what the 'rid' parameter is. Think of an 'rid' as in index into an array of like resources. A resource is just a range; start and length, and a type. The 'rid' has nothing to do with offsets into a memory/port resource. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 14:46:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 8388B37BDC5; Thu, 18 May 2000 14:46:27 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA05154; Thu, 18 May 2000 14:47:17 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005182147.OAA05154@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) In-reply-to: Your message of "Thu, 18 May 2000 17:42:43 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 May 2000 14:47:17 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 18 May 2000, Alexander Langer wrote: > > I've written bus_alloc_resource(9). > > > > I need one with _experience_ on newbus to review it. > > > > http://big.endian.de/FreeBSD/bus_alloc_resource.9 > > You still don't understand what the 'rid' parameter is. > > Think of an 'rid' as in index into an array of like resources. A resource > is just a range; start and length, and a type. The 'rid' has nothing to > do with offsets into a memory/port resource. More to the point, the rid is a bus-specific uniqifier - it's not necessarily even a linear index (consider eg. PCI). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 15:25:33 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 5198537BB12 for ; Thu, 18 May 2000 15:24:44 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id SAA84051; Thu, 18 May 2000 18:25:35 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 18 May 2000 18:25:35 -0400 (EDT) From: Adam To: dylan_parker69@hotmail.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: i have 4 pwd.db In-Reply-To: <3923CA91.F7761CED@newsguy.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 I think he might possibly mean DES-encrypt, if so you need to install the DES libraries (see sysinstall, configure, dists or compile crypto stuff in make world) and make sure the links for lib*crypt stuff points to the des ones, then force password changes (I believe) On Thu, 18 May 2000, Daniel C. Sobral wrote: >Dylan parker wrote: >> >> I want desencrypt the files pwd.db Help me please > >Password files are not decryptable by design. > >-- >Daniel C. Sobral (8-DCS) >dcs@newsguy.com >dcs@freebsd.org >capo@another.bsdconspiracy.org > > "Sentience hurts." > > >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 Thu May 18 16:16: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id E7FCB37B9CB for ; Thu, 18 May 2000 16:15:58 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id SAA19228 for ; Thu, 18 May 2000 18:35:44 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <3924704E.34E62D19@falcon.niksun.com> Date: Thu, 18 May 2000 18:35:58 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: KVA to physical??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all how to get a physical address from a kernel virtual address (the KVA is obtained from contigmalloc() ) thanx in advance -joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:16:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 44C2E37B8D7 for ; Thu, 18 May 2000 16:16:06 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id SAA19041 for ; Thu, 18 May 2000 18:19:52 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <39246C96.58C509A0@falcon.niksun.com> Date: Thu, 18 May 2000 18:20:06 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: KVA to physical address Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all how to get a physical address from a kernel virtual address (the KVA is obtained from contigmalloc() ) thanx in advance -joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:21:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 26D7B37BCD9 for ; Thu, 18 May 2000 16:21:03 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05537; Thu, 18 May 2000 16:22:04 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005182322.QAA05537@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joy Ganguly Cc: freebsd-hackers Subject: Re: KVA to physical address In-reply-to: Your message of "Thu, 18 May 2000 18:20:06 EDT." <39246C96.58C509A0@falcon.niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 May 2000 16:22:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > how to get a physical address from a kernel virtual address (the KVA is > obtained from contigmalloc() ) You don't. You probably need this for busmaster DMA; use the busdma interface instead. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:33:15 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 656EA37BCB7; Thu, 18 May 2000 16:32:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA91431; Thu, 18 May 2000 17:32:55 -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 RAA97696; Thu, 18 May 2000 17:32:06 -0600 (MDT) Message-Id: <200005182332.RAA97696@harmony.village.org> To: Alexander Langer Subject: Re: request for review: bus_alloc_resource(9) Cc: doc@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 May 2000 22:38:46 +0200." <20000518223846.A16098@cichlids.cichlids.com> References: <20000518223846.A16098@cichlids.cichlids.com> Date: Thu, 18 May 2000 17:32:06 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some problems. Here's my comments. I'm posting them in case my understanding is inaccurate. If it is, I don't want you to codify it. And I want to know so I don't keep misunderstanding :-) First, rid. "rid" is a bus specific handle that identifies the resource being allocated. For ISA this is an index into an array of resources that have been setup for this device by either the PnP mechanism, or via the hints mechanism. For PCCARD, similar things are used, but that may change in the future with newcard. For PCI it just happens to be the offset into pci config space which has a word that describes the resource. Who knows what it will be for other things. Second, RF_SHAREABLE should generally never be used. There's one exception. That's for interrupts that can be shared in the hardware. PCI bus is the only bus that does this reliably. Since the PCCARD bus can be bridged to the ISA bus or to PCI bus, you can't reliably share interrupts there. ISA bus interrupts cannot be shared (well, unless you have custom hardware or hack stock hardware, but if you are doing that, then you know what you are doing). Memory resources, ioport resources, etc are not usually shared between devices. There are lots of bus issues with doing that when you have a driver for multiple hungs of hardware. There are exceptions ot that, but not enough to be worth messing with. The dev parameter is the device requesting ownership, and optional activation of this resource. The parent, or its parent, owns the resource until it is delegated to this device. [[ as an aside, this is generally only done in the nexus, but may be done in pccard in the future ]]. When default values are used for start and end, then the count parameter may be ignored and the amount of resource specified by the bus, or the hints mechanism, is used instead of the vaule passed in. This is why you often see '1'. RF_ACTIVE doesn't need to be set. Once can reserve the resource before activating it. RF_ACTIVATE doesn't mean that the device has been activated, but rather that the bus_activate_resource() method should be called to cause the resource to become active. This isn't important on the ISA bus since resources are always active (even in the PnP model). For other buses, this may cause the bus bridges to make the resources actually available. The bus methods are free to change the RIDs that are passed to it. That's why it is a pointer. Many devices in the tree blindly assume that htis isn't the case and do not store the rids for later freeing. Bus interfaces may change in the future which might cause changes to happen where they don't happen today. Think of rids a a well defined cookie. One cookie may be a meta-cookie that causes the real cookie to be returned. Generally, one should mirror one's allocate and release calls. A technique that works well is to set the rid/res in a softc structure and then have the detach function automatically free these resources. This allows one to call, manually, the detach function when the attach fails. One should generally only call these functions in attach. If you must call them in probe, one must release the resource before returning from the probe. However, since they can affect bridge settings, it may be unavoidable to call them from the probe routine. There's no published interface that allows a probe/identify routine to ask if a range of addresses are in use. This generally only bites those busses which aren't self identifying. Currently the ISA bus is the only bus we support that isn't self identifying. PnP helps, but when you are trying to deal with legacy hardware that doesn't support PnP it can get gross. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:33:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 5DBA137BCD9 for ; Thu, 18 May 2000 16:33:37 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id TAA19820 for ; Thu, 18 May 2000 19:33:36 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <39247DDD.C3D2DEB@falcon.niksun.com> Date: Thu, 18 May 2000 19:33:49 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: contigmalloc and mmap?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi i have a buffer obtained from contigmalloc. now i want to mmap it to user space. i have done this in linux but unfortunately i am a freebsd newbie. i read the code and it appeared that the device mmap routine is passed an offset and it has to return the physical page frame no so that the necessary mapping can be created. for that i need to know the physical page frame no from the kva obtained from contigmalloc. i may be totally wrong. so i need help. thanx in advance joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:54:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 42B0237B551; Thu, 18 May 2000 16:54:04 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA05644; Thu, 18 May 2000 16:53:50 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005182353.QAA05644@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) In-reply-to: Your message of "Thu, 18 May 2000 17:32:06 MDT." <200005182332.RAA97696@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 May 2000 16:53:50 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Second, RF_SHAREABLE should generally never be used. There's one > exception. That's for interrupts that can be shared in the hardware. Actually, this is almost exactly the wrong way up; RF_SHAREABLE should always be used unless you know that the interrupt _can't_ be shared. In many cases, the driver can't tell whether it's allocating an interrupt which is or isn't shareable, and the only code that _can_ make this determination is in the parent layers. ie. as this request propagates upwards, the parent bus(ses) code should remove the flag in cases where it's know the interrupt can't be shared. > PCI bus is the only bus that does this reliably. Since the PCCARD bus > can be bridged to the ISA bus or to PCI bus, you can't reliably share > interrupts there. ... and this is why. The pccard/cardbus bridge code, or the parent bus code, needs to decide whether the interrupt is or is not shareable - not the driver. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 16:58:25 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 7425E37B5EC; Thu, 18 May 2000 16:58:15 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA91508; Thu, 18 May 2000 17:58:07 -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 RAA97841; Thu, 18 May 2000 17:57:19 -0600 (MDT) Message-Id: <200005182357.RAA97841@harmony.village.org> To: Mike Smith Subject: Re: request for review: bus_alloc_resource(9) Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 May 2000 16:53:50 PDT." <200005182353.QAA05644@mass.cdrom.com> References: <200005182353.QAA05644@mass.cdrom.com> Date: Thu, 18 May 2000 17:57:19 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200005182353.QAA05644@mass.cdrom.com> Mike Smith writes: : ... and this is why. The pccard/cardbus bridge code, or the parent bus : code, needs to decide whether the interrupt is or is not shareable - not : the driver. Ah. That's a good point. The ISA and PCCARD bridges should turn off interrupt sharing and the PCI and Cardbus bridges should pass it through. One other time when you can't share interrupts: Fast interrupts aren't shareable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 17:26:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camel.ethereal.net (camel.ethereal.net [216.200.22.209]) by hub.freebsd.org (Postfix) with ESMTP id B8BB137B9FF for ; Thu, 18 May 2000 17:26:23 -0700 (PDT) (envelope-from jkb@camel.ethereal.net) Received: (from jkb@localhost) by camel.ethereal.net (8.10.0.Beta10/8.10.0.Beta10) id e4J0PRZ07488; Thu, 18 May 2000 17:25:27 -0700 (PDT) Date: Thu, 18 May 2000 17:25:27 -0700 From: Jan Koum To: "Chris D. Faulhaber" Cc: "Daniel C. Sobral" , Dylan parker , freebsd-hackers@FreeBSD.ORG Subject: Re: i have 4 pwd.db Message-ID: <20000518172527.J10836@ethereal.net> References: <3923CA91.F7761CED@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.14i In-Reply-To: ; from jedgar@fxp.org on Thu, May 18, 2000 at 08:46:35AM -0400 X-Operating-System: FreeBSD camel.ethereal.net 3.4-RELEASE FreeBSD 3.4-RELEASE X-Unix-Uptime: 6:15PM up 8 days, 4:52, 25 users, load averages: 0.02, 0.10, 0.13 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 18, 2000 at 08:46:35AM -0400, "Chris D. Faulhaber" wrote: > On Thu, 18 May 2000, Daniel C. Sobral wrote: > > Dylan parker wrote: > > > > > > I want desencrypt the files pwd.db Help me please > > > > Password files are not decryptable by design. > > > > And encrypted passwords are not stored in pwd.db (see spwd.db) > And the hash itself is of course possible to recover from spwd.db: $ cat c.c #include #include #include #include struct passwd *pw; int main() { while (pw = getpwent()) { printf("%s:%s:%d:%d:%d:%d:%s:%s:%s:%s\n", pw->pw_name, pw->pw_passwd, pw->pw_uid, pw->pw_gid, (int)pw->pw_change, (int)pw->pw_expire, pw->pw_class, pw->pw_gecos, pw->pw_dir, pw->pw_shell); } } $ make c $ sudo ./c -- yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 17:26:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 00C1C37BAD8 for ; Thu, 18 May 2000 17:26:24 -0700 (PDT) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 61ADF1C5C; Thu, 18 May 2000 20:26:23 -0400 (EDT) Date: Thu, 18 May 2000 20:26:23 -0400 From: Bill Fumerola To: Joy Ganguly Cc: freebsd-hackers Subject: Re: KVA to physical??? Message-ID: <20000518202623.C86725@jade.chc-chimes.com> References: <3924704E.34E62D19@falcon.niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3924704E.34E62D19@falcon.niksun.com>; from joy@niksun.com on Thu, May 18, 2000 at 06:35:58PM -0400 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 18, 2000 at 06:35:58PM -0400, Joy Ganguly wrote: > how to get a physical address from a kernel virtual address (the KVA is > obtained from contigmalloc() ) > > thanx in advance Mike Smith's answer wasn't good enough? -- Bill Fumerola - Network Architect / Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 18: 4:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 1626337BDC5; Thu, 18 May 2000 18:04:44 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-33.bellatlantic.net [151.198.135.33]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA05738; Thu, 18 May 2000 21:04:22 -0400 (EDT) Message-ID: <3924931E.A8471B0@bellatlantic.net> Date: Thu, 18 May 2000 21:04:30 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Warner Losh Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) References: <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > One should generally only call these functions in attach. If you must > call them in probe, one must release the resource before returning > from the probe. However, since they can affect bridge settings, it > may be unavoidable to call them from the probe routine. The code seems to guarantee that if the probe routine returns 0 then the attach routine will be called right away. So if the probe routine returns 0 they don't have to be freed. Actually, the comments seem to say explicitly that the resources should be freed only if the probe routine returns a negative value but not 0. Or am I missing something ? -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 18:17:17 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 ED1D637B63E; Thu, 18 May 2000 18:17:10 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA91678; Thu, 18 May 2000 19:17:09 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA98120; Thu, 18 May 2000 19:16:21 -0600 (MDT) Message-Id: <200005190116.TAA98120@harmony.village.org> To: Sergey Babkin Subject: Re: request for review: bus_alloc_resource(9) Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 May 2000 21:04:30 EDT." <3924931E.A8471B0@bellatlantic.net> References: <3924931E.A8471B0@bellatlantic.net> <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> Date: Thu, 18 May 2000 19:16:21 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3924931E.A8471B0@bellatlantic.net> Sergey Babkin writes: : The code seems to guarantee that if the probe routine returns 0 : then the attach routine will be called right away. So if the probe : routine returns 0 they don't have to be freed. Actually, the : comments seem to say explicitly that the resources should be : freed only if the probe routine returns a negative value but not 0. : Or am I missing something ? The code doesn't write the guarantee. In general probe routines are supposed to be idempotent. You are supposed to be able to have them be called multiple times, at least in theory. The probe routine should not hold resources past the end of its execution, positive or negative. I'm not sure where you found the comments that say that the probe routine can hold resources after it is called. I couldn't find any. It is also legal for buses to probe all their devices before attaching any of them (the pci bus does this, iirc, so that generic drivers can handle some hardware and more specific drivers can handle other). There's nothing that states probe_and_attach is the only way to get things done. Finally, there's a comment in subr_bus: device_set_driver(child, best->driver); if (pri < 0) { /* * A bit bogus. Call the probe method again to make sure * that we have the right description. */ DEVICE_PROBE(child); } which indicates to me that the probe routines will be called multiple times if they return < 0 (pri is the priority they returned, 0 meaning it is mine and nobody else's). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 19:55:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id 61B2537BA4C for ; Thu, 18 May 2000 19:55:32 -0700 (PDT) (envelope-from mrcpu@internetcds.com) Received: (qmail 23473 invoked from network); 19 May 2000 02:55:30 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 19 May 2000 02:55:30 -0000 Date: Thu, 18 May 2000 19:50:17 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org, stable@freebsd.org Subject: NFS problems on 4.0-stable. 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 UDP v2 mounts, Netapp Filer. Getting a fair # of: got bad cookie vp 0xd24bf1c0 bp 0xc9090500 got bad cookie vp 0xd24bfda0 bp 0xc906ceb0 on the console, and it seems to lock the machine up for several minutes when it does. Then it comes back to life, and cranks for a while... Not sure where to even start. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu May 18 22:46:30 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 3CF4237BA98; Thu, 18 May 2000 22:46:17 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA92401; Thu, 18 May 2000 23:46:14 -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 XAA99133; Thu, 18 May 2000 23:45:25 -0600 (MDT) Message-Id: <200005190545.XAA99133@harmony.village.org> To: Jaye Mathisen Subject: Re: NFS problems on 4.0-stable. Cc: hackers@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Thu, 18 May 2000 19:50:17 PDT." References: Date: Thu, 18 May 2000 23:45:25 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Jaye Mathisen writes: : got bad cookie vp 0xd24bf1c0 bp 0xc9090500 : got bad cookie vp 0xd24bfda0 bp 0xc906ceb0 Seen these too. Not sure why. Too many other fire to fight. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 0:12:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 4D7CB37BD8E; Fri, 19 May 2000 00:12:38 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C112F.dip0.t-ipconnect.de [62.156.17.47]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id JAA23030; Fri, 19 May 2000 09:12:24 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 320C2AC2C; Fri, 19 May 2000 09:12:48 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id JAA02859; Fri, 19 May 2000 09:12:30 +0200 (CEST) (envelope-from alex) Date: Fri, 19 May 2000 09:12:30 +0200 From: Alexander Langer To: "Matthew N. Dodd" Cc: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) Message-ID: <20000519091230.C2729@cichlids.cichlids.com> References: <20000518223846.A16098@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from winter@jurai.net on Thu, May 18, 2000 at 05:42:43PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Matthew N. Dodd (winter@jurai.net): > is just a range; start and length, and a type. The 'rid' has nothing to > do with offsets into a memory/port resource. Hmm. When I wrote Doug Rabson about newbus months ago, he gave me that part of code: rid = 0x10; /* offset of pci mapping register - check your docs */ res = bus_alloc_resource(dev, SYS_RES_IOPORTS, &rid, 0, ~0, 1, RF_ACTIVE); st = rman_get_bustag(res); sh = rman_get_bushandle(res); This "offset of the pci mapping register" is quite confusing for me then. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 0:14:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 23D9D37BD8E; Fri, 19 May 2000 00:14:18 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C112F.dip0.t-ipconnect.de [62.156.17.47]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id JAA23424; Fri, 19 May 2000 09:14:06 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id E0CFEAC2C; Fri, 19 May 2000 09:14:25 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id JAA03005; Fri, 19 May 2000 09:14:09 +0200 (CEST) (envelope-from alex) Date: Fri, 19 May 2000 09:14:09 +0200 From: Alexander Langer To: "Matthew N. Dodd" Cc: doc@freebsd.org, hackers@freebsd.org Subject: Re: request for review: bus_alloc_resource(9) Message-ID: <20000519091409.D2729@cichlids.cichlids.com> References: <20000518223846.A16098@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from winter@jurai.net on Thu, May 18, 2000 at 05:42:43PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Matthew N. Dodd (winter@jurai.net): > Think of an 'rid' as in index into an array of like resources. A resource > is just a range; start and length, and a type. The 'rid' has nothing to > do with offsets into a memory/port resource. Ah, yes. That is probably why resource_list_alloc(rl, dev, child, type, rid, ... is called for the pci-version of bus_alloc_resource :-) (sys/pci/pci.c) Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 0:16:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 09CB337BCFE; Fri, 19 May 2000 00:16:30 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA07106; Fri, 19 May 2000 00:17:13 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005190717.AAA07106@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Langer Cc: "Matthew N. Dodd" , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) In-reply-to: Your message of "Fri, 19 May 2000 09:12:30 +0200." <20000519091230.C2729@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 May 2000 00:17:13 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thus spake Matthew N. Dodd (winter@jurai.net): > > > is just a range; start and length, and a type. The 'rid' has nothing to > > do with offsets into a memory/port resource. > > Hmm. When I wrote Doug Rabson about newbus months ago, he gave me that > part of code: > > rid = 0x10; /* offset of pci mapping register - check your docs */ > res = bus_alloc_resource(dev, SYS_RES_IOPORTS, &rid, 0, ~0, 1, > RF_ACTIVE); > st = rman_get_bustag(res); > sh = rman_get_bushandle(res); > > This "offset of the pci mapping register" is quite confusing for me > then. Not at all; in the PCI context, that's what the rid is. As has been said several times now, the meaning of the rid is _bus_specific_. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 0:20:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id D736137BD8E; Fri, 19 May 2000 00:20:49 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C112F.dip0.t-ipconnect.de [62.156.17.47]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id JAA24872; Fri, 19 May 2000 09:20:39 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id C2296AC2C; Fri, 19 May 2000 09:21:03 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id JAA03412; Fri, 19 May 2000 09:20:47 +0200 (CEST) (envelope-from alex) Date: Fri, 19 May 2000 09:20:47 +0200 From: Alexander Langer To: Mike Smith Cc: "Matthew N. Dodd" , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) Message-ID: <20000519092047.E2729@cichlids.cichlids.com> References: <20000519091230.C2729@cichlids.cichlids.com> <200005190717.AAA07106@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005190717.AAA07106@mass.cdrom.com>; from msmith@FreeBSD.ORG on Fri, May 19, 2000 at 12:17:13AM -0700 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Mike Smith (msmith@FreeBSD.ORG): > Not at all; in the PCI context, that's what the rid is. As has been said > several times now, the meaning of the rid is _bus_specific_. Ah, I wrote that before reading the next mails, stupid me. Well, thanks for all your comments. I'll add/merge the information you gave me in the evening. Thanks! Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 6:57:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.wplus.net (relay.wplus.net [195.131.52.179]) by hub.freebsd.org (Postfix) with ESMTP id 30B7237BE21; Fri, 19 May 2000 06:57:27 -0700 (PDT) (envelope-from dms@woland.wplus.net) Received: from woland.wplus.net (woland.wplus.net [195.131.0.39]) by relay.wplus.net (8.9.1/8.9.1/wplus.2) with ESMTP id RAA60557; Fri, 19 May 2000 17:57:25 +0400 (MSD) X-Real-To: freebsd-net@FreeBSD.ORG Received: (from dms@localhost) by woland.wplus.net (8.9.3/8.9.1/wplus.2) id RAA00390; Fri, 19 May 2000 17:57:24 +0400 (MSD) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000517231043.A13544@wcug.wwu.edu> Date: Fri, 19 May 2000 17:57:24 +0400 (MSD) From: Dmitry Samersoff To: Travis Cole Subject: Re: bpf question Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-May-2000 Travis Cole wrote: > On Wed, May 17, 2000 at 05:51:59PM +0400, Dmitry Samersoff wrote: >> I have traffic metering program using bpf, >> it works fine on relatevly free net but looses about 30% >> of packets on havy loaded one. > > Are you doing dns lookups? Don't do those and you may fix your problem. Thanks for all. I tryed all usual solution (change CPU, bring packet parsing out of reading thread and so on.) and now I have stoped on perforamnce bpf itself. Is there alternate driver or can changing of bpf queue in kernel help, and where I can read about it? Did any body work with raw ethernet and is it helpfull? -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 7:34:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id C577D37BE99 for ; Fri, 19 May 2000 07:34:40 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id KAA03287; Fri, 19 May 2000 10:34:34 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <3925510C.3F6DFE5C@falcon.niksun.com> Date: Fri, 19 May 2000 10:34:52 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon , freebsd-hackers Subject: Re: Question about file write???? References: <20000517160746.12768.qmail@www0a.netaddress.usa.net> <20000517102516.B14968@fw.wintelcom.net> <3922DB0F.9D9095C9@falcon.niksun.com> <20000517135644.D14968@fw.wintelcom.net> <39231E06.31DFB153@falcon.niksun.com> <200005172324.QAA28046@apollo.backplane.com> <39241174.5CA00E48@falcon.niksun.com> <200005182239.PAA34047@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :I am sorry that i missed this point in my previous post. well the problem with > :the mmap is that my device does not have a buffer always. earlier the 'read' > :ioctl on the device used to sleep till a buffer was available. what does the > :mmap do?? can it block?? i am sorry if this sounds naive bcoz i am a relative > :newbie > : > :thanx in advance > : > :-joy > > No, I was thinking of devices which have a fixed buffer. > > Perhaps what you are looking for is something similar to sendfile(). > Take a look at the sendfile() system call code, it might be possible > to adapt it for your device. > well i hacked the code to do the mmap. but the performance problem is still there. the strange thing is mmap+write takes much longer than read+write. ive mmaped a kernel buffer that was allocated with contigmalloc(). the writing the mmaped buffer to the file takes much longer than the writing read buffer. the ideal thing would be to do something like sendfile(). however i hvnt yet figured out how to do it for a tranfer from a kernel buffer to a file. i think ill have to map disk buffers to my kernel buffer. any suggestions?? thanx in advance joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 8: 2: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.imagination.co.uk (mailgate.imagination.co.uk [194.128.49.32]) by hub.freebsd.org (Postfix) with ESMTP id B07FF37BFB3 for ; Fri, 19 May 2000 08:01:44 -0700 (PDT) (envelope-from jonathan.laventhol@imagination.co.uk) Received: from imagination.co.uk (dhcp-77-54.imagination.co.uk [192.168.77.54]) by mailgate.imagination.co.uk (8.9.3/8.9.3) with ESMTP id PAA35186 for ; Fri, 19 May 2000 15:01:04 GMT Message-ID: <39255860.FC0F2688@imagination.co.uk> Date: Fri, 19 May 2000 16:06:08 +0100 From: Jonathan Laventhol Organization: Imagination Ltd X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: System management with large groups Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD Hackers -- I've got a technically-straightfordward but nonetheless business-critical problem with the groups structures in FreeBSD which perhaps you kind souls can help me with. *** BACKGROUND *** My company is a 400-person design and communications agency. We have approximately 15 NT servers giving file and print service to mixed network of Macintosh / W95 / NT desktop machines with a user community of graphic designers, architects, and business people. The network is essentially pure IP and is global spread over 5 offices in three continents. I am looking at the technical feasibility of moving to FreeBSD with Samba and Netatalk. We currently use FreeBSD 3.3-RELEASE through 4.0-RELEASE via Walnut Creek CDs for DNS, e-mail, web, ftp, various proxies, tacacs and a number of custom web-delivered databases. There are maybe 15 small FreeBSD machines doing these jobs. Only systems management actually log in on the machines, the real users have NOLOGIN shells. We do not currently use NIS but I'm considering it. *** HOW WE WANT TO USE GROUPS *** We would want to use the groups in the following way: Each user would have a group for themselves with UID=GID. Each 'rank' would have a group eg board, vp, depthead, et cetera. Each department would have a group eg finance, graphics et cetera. Each project would have a group eg proj1000, proj1001 Then umask would be 775 chown ernie.ernie /home/ernie chown boss.board /board/minutes chown cfo.finance /dept/finance chown whatever.proj1000 /projects/proj1000 Clearly there would be a lot of groups required: perhaps several thousand. And a particular individual might be in a hundred or more groups; perhaps a few unique individuals would be in all the projects. *** ISSUES *** The most significant issue is the limits on groups. Part of this is because of the inherent limits of user-group-world masks versus ACLS -- which we can live with and would help us by simpifying the problems -- and part is because of long-legacy limits within 4.4bsd. Because of the size and structure of my company a person might need to be in 20 or 30 groups anyway. Because of working around the ACL issue, we'd need to have a large number of groups -- perhaps thousands -- and individual users in large proportion of those. Some users might even be in *every* group. *** APPARENT CAUSES *** 1. I see that the 200-users-per-group limit is gone since 3.0-RELEASE. 2. I'm concerned about the 1+16 groups-per-user issue 3. I'm concerned about large numbers of groups in a flat group(5) file. *** QUESTIONS *** Question 0: Is this a sensible way to solve my access rights issues? Anybody got a better way altogether? (Maybe just hack Samba?) Question 1: Is anybody planning any work on this for future releases? Question 2: What is the relationship between hard-coded NGROUPS and NGROUPS_MAX, and the sysctl kern.ngroups? Question 3: Can I just edit NGROUPS_MAX somewhere and make it bigger? Which one do I fix? (Is there a 'make world faq? Never done it before.) Question 4: What do people think might break? Would it be better, worse, or impossible to do this with NIS? Question 5: Has anybody done anything like a vigr (like vipw) for /etc/group? Our (locally-written) user database would be changing the groups all the time. Many thanks, my FreeBSD heroes, if anybody has anything to offer on this. Best regards, Jonathan. -- Jonathan Laventhol Technology Director ____________________________________________________________________ Imagination 25 Store Street South Crescent London WC1E 7BL England | Tel +44 171 323 3300 Fax +44 171 323 5801 | _______________________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 8:12:18 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 A289837BF21; Fri, 19 May 2000 08:12:05 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id KAA27497; Fri, 19 May 2000 10:11:53 -0500 (CDT) (envelope-from dan) Date: Fri, 19 May 2000 10:11:53 -0500 From: Dan Nelson To: Dmitry Samersoff Cc: Travis Cole , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: bpf question Message-ID: <20000519101153.C18334@dan.emsphone.com> References: <20000517231043.A13544@wcug.wwu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from "Dmitry Samersoff" on Fri May 19 17:57:24 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 19), Dmitry Samersoff said: > On 18-May-2000 Travis Cole wrote: > > On Wed, May 17, 2000 at 05:51:59PM +0400, Dmitry Samersoff wrote: > >> I have traffic metering program using bpf, it works fine on > >> relatevly free net but looses about 30% of packets on havy loaded > >> one. > > > > Are you doing dns lookups? Don't do those and you may fix your problem. > > Thanks for all. I tryed all usual solution (change CPU, bring packet > parsing out of reading thread and so on.) and now Define "heavily loaded". If you just run "tcpdump -n" for a couple minutes and hit ^C, does it report any dropped packets? If it does, then your machine probably isn't fast enough to handle the network load. If I flood my 100mbit network with small packets, and monitor it on a P6/200 with "tcpdump -n", I drop from 1-10% of the packets. If I use "tcpdump -n -w logfile.txt", I drop no packets. -- 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 May 19 9: 1:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 6F04337BDC4 for ; Fri, 19 May 2000 09:01:23 -0700 (PDT) (envelope-from cns@psn.ie) Received: from alto ([192.168.0.254] helo=alto.internal) by mailhub.psn.ie with esmtp (Exim 3.12 #2) id 12spCM-000CNV-00 for hackers@freebsd.org; Fri, 19 May 2000 17:00:26 +0100 Received: from cns by alto.internal with local (Exim 3.12 #1) id 12spCM-0007cf-00 for hackers@freebsd.org; Fri, 19 May 2000 17:00:26 +0100 Date: Fri, 19 May 2000 17:00:26 +0100 From: Cillian Sharkey To: hackers@freebsd.org Subject: Post-shutdown hook for UPS shutdown? Message-ID: <20000519170026.A29241@psn.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Folks, I need to execute a script (which tells the UPS to turn off) *after* the system has come to a safe halt from shutdown -h. I can't place the commands in /etc/rc.shutdown because this is too early in the shutdown sequence. Unfortunately, the UPS in question (APC Back-UPS 650) is not a "smart" one, (i.e. it doesn't have an in-built delay when a shutdown signal is received which gives time for all attached devices to shutdown) and I'm pretty much stuck with it. The software is the Network UPS Tools (NUT) package. Basically, is there currently any way to execute a post-shutdown script once the system has "halted" ? If not, is this feature possible to add ? Thanks in advance, -- Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 9:32:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id A788737BEF9 for ; Fri, 19 May 2000 09:30:53 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e4JGUmc16770; Fri, 19 May 2000 09:30:48 -0700 (PDT) Date: Fri, 19 May 2000 09:30:48 -0700 (PDT) From: Doug White To: Cillian Sharkey Cc: hackers@FreeBSD.ORG Subject: Re: Post-shutdown hook for UPS shutdown? In-Reply-To: <20000519170026.A29241@psn.ie> 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, 19 May 2000, Cillian Sharkey wrote: > Hi Folks, > > I need to execute a script (which tells the UPS to turn off) *after* the > system has come to a safe halt from shutdown -h. I can't place the commands > in /etc/rc.shutdown because this is too early in the shutdown sequence. > > Unfortunately, the UPS in question (APC Back-UPS 650) is not a "smart" one, > (i.e. it doesn't have an in-built delay when a shutdown signal is received > which gives time for all attached devices to shutdown) and I'm pretty much > stuck with it. The software is the Network UPS Tools (NUT) package. To do anything that late you'd have to hack the kernel. I believe APC's units have a 'time-delay shutdown' line that you can throw as late as possible and it'll give you 10 seconds to get all the way down. I'm not sure about the BackUPSs tho. The other option is to not bother turning off the UPS; you're safe one you're halted. That or try turning the machine itself off if apm and shutdown -p can do it. 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 Fri May 19 9:33: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0065837C10D; Fri, 19 May 2000 09:32:39 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA48970; Fri, 19 May 2000 12:32:21 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Fri, 19 May 2000 12:32:40 -0400 To: Jaye Mathisen , hackers@FreeBSD.ORG, stable@FreeBSD.ORG From: Garance A Drosihn Subject: Re: NFS problems on 4.0-stable. Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:50 PM -0700 5/18/00, Jaye Mathisen wrote: >UDP v2 mounts, Netapp Filer. > >Getting a fair # of: >got bad cookie vp 0xd24bf1c0 bp 0xc9090500 >got bad cookie vp 0xd24bfda0 bp 0xc906ceb0 > >on the console, and it seems to lock the machine up for several >minutes when it does. Then it comes back to life, and cranks >for a while... > >Not sure where to even start. More information might help. Is this on an NFS client, or an NFS server? Are BOTH sides (client & server) running freebsd, or is the "other side" (the one not getting these errors) running some other operating system? If you have been running 4.0-stable for some time now, have these errors always existed (say, starting with 4.0-release), or did they just start appearing after some recent sync with 4.0-stable? --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 10: 9: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 6632537BF34 for ; Fri, 19 May 2000 10:08:52 -0700 (PDT) (envelope-from cns@psn.ie) Received: from alto ([192.168.0.254] helo=alto.internal) by mailhub.psn.ie with esmtp (Exim 3.12 #2) id 12sqDF-000CUY-00; Fri, 19 May 2000 18:05:25 +0100 Received: from cns by alto.internal with local (Exim 3.12 #1) id 12sqDF-0007h8-00; Fri, 19 May 2000 18:05:25 +0100 Date: Fri, 19 May 2000 18:05:25 +0100 From: Cillian Sharkey To: Doug White Cc: hackers@freebsd.org Subject: Re: Post-shutdown hook for UPS shutdown? Message-ID: <20000519180525.A29385@psn.ie> References: <20000519170026.A29241@psn.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Fri, May 19, 2000 at 09:30:48AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 May 2000, Doug White wrote: > On Fri, 19 May 2000, Cillian Sharkey wrote: > > I need to execute a script (which tells the UPS to turn off) *after* the > > system has come to a safe halt from shutdown -h. I can't place the commands > > in /etc/rc.shutdown because this is too early in the shutdown sequence. > > To do anything that late you'd have to hack the kernel. Hmm, thought so. However if all filesystems are unmounted after disks are synced, wouldn't that make the software (kept in /usr/local) un-available..? > I believe APC's units have a 'time-delay shutdown' line that you can > throw as late as possible and it'll give you 10 seconds to get all the way > down. I'm not sure about the BackUPSs tho. That's right - BackUPSs don't have the feature; they shutdown the moment they get the signal. > The other option is to not bother turning off the UPS; you're safe one > you're halted. That or try turning the machine itself off if apm and > shutdown -p can do it. I considered this, but we need unattended shutdown when power goes / reboot when power comes back. If the power cut was long enough, the UPS battery would soon cut out and the machines would bootup correctly when the power comes back, however this doesn't work if the power comes on before the battery has fully discharged.. -- Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 10:41:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 6B3C937BAAD for ; Fri, 19 May 2000 10:41:11 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id TAA34870; Fri, 19 May 2000 19:40:56 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by C992631-A.pinol1.sfba.home.com (8.9.3/8.9.3) id KAA12585; Fri, 19 May 2000 10:40:49 -0700 (PDT) (envelope-from reg) Date: Fri, 19 May 2000 10:40:48 -0700 From: Jeremy Lea To: Cillian Sharkey Cc: hackers@FreeBSD.ORG Subject: Re: Post-shutdown hook for UPS shutdown? Message-ID: <20000519104048.A12491@shale.csir.co.za> References: <20000519170026.A29241@psn.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000519170026.A29241@psn.ie>; from cns@psn.ie on Fri, May 19, 2000 at 05:00:26PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just an idea... On Fri, May 19, 2000 at 05:00:26PM +0100, Cillian Sharkey wrote: > Basically, is there currently any way to execute a post-shutdown script once > the system has "halted" ? If not, is this feature possible to add ? Why not let the machine reboot, and check the power before anything else in /etc/rc. If it's bad, just signal the UPS, and let the system power down. The disks should still be unmounted, etc. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... 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 Fri May 19 11:14:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id B54F537B5BA for ; Fri, 19 May 2000 11:14:35 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id UAA37782; Fri, 19 May 2000 20:13:05 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Fri, 19 May 2000 20:13:05 +0200 (EET) From: Narvi To: Jonathan Laventhol Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: System management with large groups In-Reply-To: <39255860.FC0F2688@imagination.co.uk> 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, 19 May 2000, Jonathan Laventhol wrote: > Dear FreeBSD Hackers -- > > I've got a technically-straightfordward but nonetheless > business-critical problem with the groups structures in FreeBSD > which perhaps you kind souls can help me with. > > *** BACKGROUND *** > [snip] > Question 4: What do people think might break? Would it be better, > worse, or impossible to do this with NIS? > My gut feeling says worse. Have you looked into the ACL patches for FreeBSD? > Question 5: Has anybody done anything like a vigr (like vipw) > for /etc/group? Our (locally-written) user database would be > changing the groups all the time. > > > Many thanks, my FreeBSD heroes, if anybody has anything to offer > on this. > > Best regards, > Jonathan. > -- > Jonathan Laventhol > Technology Director > ____________________________________________________________________ > Imagination 25 Store Street South Crescent London WC1E 7BL England | > Tel +44 171 323 3300 Fax +44 171 323 5801 | > _______________________________________________________| > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 11:20:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (adsl-63-206-88-224.dsl.snfc21.pacbell.net [63.206.88.224]) by hub.freebsd.org (Postfix) with ESMTP id 24A9F37B532 for ; Fri, 19 May 2000 11:20:24 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA09144; Fri, 19 May 2000 11:21:16 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005191821.LAA09144@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Cillian Sharkey Cc: Doug White , hackers@freebsd.org Subject: Re: Post-shutdown hook for UPS shutdown? In-reply-to: Your message of "Fri, 19 May 2000 18:05:25 BST." <20000519180525.A29385@psn.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 May 2000 11:21:15 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 19 May 2000, Doug White wrote: > > On Fri, 19 May 2000, Cillian Sharkey wrote: > > > I need to execute a script (which tells the UPS to turn off) *after* the > > > system has come to a safe halt from shutdown -h. I can't place the commands > > > in /etc/rc.shutdown because this is too early in the shutdown sequence. > > > > To do anything that late you'd have to hack the kernel. > > Hmm, thought so. However if all filesystems are unmounted after disks are > synced, wouldn't that make the software (kept in /usr/local) un-available..? > > > I believe APC's units have a 'time-delay shutdown' line that you can > > throw as late as possible and it'll give you 10 seconds to get all the way > > down. I'm not sure about the BackUPSs tho. > > That's right - BackUPSs don't have the feature; they shutdown the moment > they get the signal. > > > The other option is to not bother turning off the UPS; you're safe one > > you're halted. That or try turning the machine itself off if apm and > > shutdown -p can do it. > > I considered this, but we need unattended shutdown when power goes / reboot > when power comes back. If the power cut was long enough, the UPS battery > would soon cut out and the machines would bootup correctly when the power > comes back, however this doesn't work if the power comes on before the > battery has fully discharged.. The canonical way to do this is actually to shudown and reboot. In the _startup_ phase, while the root filesystem is still mounted readonly, you check the UPS status. At this point, you have access to the disk in a read-only fashion, and you can power-off (or have the UPS die) at any time. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 12:41:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2083637BF55; Fri, 19 May 2000 12:41:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA40371; Fri, 19 May 2000 12:41:49 -0700 (PDT) (envelope-from dillon) Date: Fri, 19 May 2000 12:41:49 -0700 (PDT) From: Matthew Dillon Message-Id: <200005191941.MAA40371@apollo.backplane.com> To: Jaye Mathisen , hackers@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NFS problems on 4.0-stable. References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At 7:50 PM -0700 5/18/00, Jaye Mathisen wrote: :>UDP v2 mounts, Netapp Filer. :> :>Getting a fair # of: :>got bad cookie vp 0xd24bf1c0 bp 0xc9090500 :>got bad cookie vp 0xd24bfda0 bp 0xc906ceb0 :> :... :>on the console, and it seems to lock the machine up for several :>minutes when it does. Then it comes back to life, and cranks :>for a while... Hmmm. There is nothing 'wrong' per say with getting a bad cookie during a directory search. When FreeBSD gets a cookie error while scanning a directory, it has to start the scan over again. If you have a very large directory with lots of clients banging on it, a cookie error can result in a long delay. I am guessing that the long blockages are due to getting cookie errors on a very large directory. Why are you using a V2 mount? V3 mounts ought to perform much better, though the cookie error problem you are seeing will probably still be there. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 12:54: 2 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 BA3F137BF9B for ; Fri, 19 May 2000 12:53:57 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA94999; Fri, 19 May 2000 13:53:55 -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 NAA03130; Fri, 19 May 2000 13:53:04 -0600 (MDT) Message-Id: <200005191953.NAA03130@harmony.village.org> To: Cillian Sharkey Subject: Re: Post-shutdown hook for UPS shutdown? Cc: Doug White , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 19 May 2000 18:05:25 BST." <20000519180525.A29385@psn.ie> References: <20000519180525.A29385@psn.ie> <20000519170026.A29241@psn.ie> Date: Fri, 19 May 2000 13:53:04 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You'd like have to hack the kernel. There are hooks in the kernel to execute very late in the game. I even think there is one to do things just before halt that you could use to power things off completely. If this is a UPS, and the signal is several serial characters, you'd have to poll the serial port rather than using interrupts (and you should disable interrupts just in case). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 12:55: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 7DF0E37BF73 for ; Fri, 19 May 2000 12:55:12 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA95020; Fri, 19 May 2000 13:55: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 NAA03169; Fri, 19 May 2000 13:54:20 -0600 (MDT) Message-Id: <200005191954.NAA03169@harmony.village.org> Subject: Re: Post-shutdown hook for UPS shutdown? Cc: Cillian Sharkey , Doug White , hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 19 May 2000 13:53:04 MDT." <200005191953.NAA03130@harmony.village.org> References: <200005191953.NAA03130@harmony.village.org> <20000519180525.A29385@psn.ie> <20000519170026.A29241@psn.ie> Date: Fri, 19 May 2000 13:54:20 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200005191953.NAA03130@harmony.village.org> Warner Losh writes: : You'd like have to hack the kernel. There are hooks in the kernel to : execute very late in the game. I even think there is one to do things : just before halt that you could use to power things off completely. : If this is a UPS, and the signal is several serial characters, you'd : have to poll the serial port rather than using interrupts (and you : should disable interrupts just in case). Actually, forget what I said. Mike smith's way is much cleaner. Assuming that the batteries have enough juice in them to do the reboot. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 13:20:45 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 A4E9637B5FA; Fri, 19 May 2000 13:20:36 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA15659; Fri, 19 May 2000 16:20:35 -0400 (EDT) Date: Fri, 19 May 2000 16:19:43 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: A possible bug in directory lookup code? 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 think I may have found a bug in the directory lookup code in FreeBSD 4.0-Release, although it does not affect normal user. Please be patient and read on. The test code I am using and its result as follows: # cat test.c #include #include main() { int error; error = rename("dir1", "dir2/."); printf("error = %d, errno = %d\n", error, errno); } # mkdir dir1 # mkdir dir2 # cc test.c # ./a.out error = -1, errno = 66 The error code returned is 66 - ENOTEMPTY not the expected 22 - EINVAL. Why do I expect EINVAL error? This is because the following code: (1) In ufs_lookup(), we have the following code for the RENAME case: if (dp->i_number == dp->i_ino) return (EISDIR); This code is never executed when you are looking for dot. (2) In rename() system call, we have the following bogus code: if ((error = namei(&tond)) != 0) { /* Translate error code for rename("dir1", "dir2/."). */ if (error == EISDIR && fvp->v_type == VDIR) error = EINVAL; <-- should change to 22 here! NDFREE(&fromnd, NDF_ONLY_PNBUF); vrele(fromnd.ni_dvp); vrele(fvp); goto out1; } See the bogus comment "Translate error ...", that is exactly what I am using in my test.c code. How does this happen (return 66 instead of 22)? I use remote debugging to find out. In vfs_cache_lookup() (invoked by VOP_LOOKUP()), it calls cache_lookup(), which returns -1 as a dot hit. Then because of the following code: if (pdp == vdp) { /* lookup on "." */ VREF(vdp); error = 0; namei() succeeds on "dir2/." lookup (error = 0). Next, when ufs_rename() is called, the tdvp and tvp are the same vnode! This will make ufs_dirempty() return 0 (even if the directory dir2/. is empty!) and ENOTEMPTY will be set to the variable error. IMHO, this is not the correct way to handle this in the kernel. But the net result from the point of the view of the user is the same (the atomic rename fails). It just makes things very confusing. ufs_dirempty() should not return 0 when the directory is empty. BTW, when I use gdb to do remote debugging, the gdb sometimes fails to display the correct line that is being executed. I wonder what's wrong. Any insights in appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 14:57:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gwnew.niksun.com [206.20.52.130]) by hub.freebsd.org (Postfix) with ESMTP id 0DA3637B762 for ; Fri, 19 May 2000 14:57:54 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id RAA09943 for ; Fri, 19 May 2000 17:57:47 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <3925B8EE.E901BB31@falcon.niksun.com> Date: Fri, 19 May 2000 17:58:06 -0400 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers Subject: OBJ_OPT??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all what does the flag OBJ_OPT mean?? i read it deals with some sort of IO optimization. but i dont know what it actually does. any insights on this?? thanx joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 15:42:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id EEDDB37B635; Fri, 19 May 2000 15:42:47 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1138.dip0.t-ipconnect.de [62.156.17.56]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id AAA08300; Sat, 20 May 2000 00:42:36 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 06CCEAC2C; Sat, 20 May 2000 00:43:03 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id AAA04562; Sat, 20 May 2000 00:42:45 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 00:42:45 +0200 From: Alexander Langer To: doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) Message-ID: <20000520004245.A4202@cichlids.cichlids.com> References: <20000518223846.A16098@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000518223846.A16098@cichlids.cichlids.com>; from alex@big.endian.de on Thu, May 18, 2000 at 10:38:46PM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Second, reworked version now available. http://big.endian.de/FreeBSD/bus_alloc_resource.9 In my eyes, it's quite correct now and is worth a PR/commit. I'll send a PR if I get your ok. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 16: 7:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 5CEFD37B52B; Fri, 19 May 2000 16:07:04 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1138.dip0.t-ipconnect.de [62.156.17.56]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id BAA12724; Sat, 20 May 2000 01:06:51 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 7E5C6AC2C; Sat, 20 May 2000 01:07:19 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id BAA05113; Sat, 20 May 2000 01:07:01 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 01:07:01 +0200 From: Alexander Langer To: hackers@freebsd.org Cc: doc@freebsd.org Subject: new bus_release_resource(9) Message-ID: <20000520010701.B5052@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I just finnished bus_release_resource.9. The technical part should be correct, since I could not do things wrong. Maybe you want to review it anyways. http://big.endian.de/FreeBSD/bus_release_resource.9 Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 16: 7:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 599D237C0A5; Fri, 19 May 2000 16:07:22 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-21.bellatlantic.net [151.198.117.21]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA20685; Fri, 19 May 2000 19:07:00 -0400 (EDT) Message-ID: <3925C91E.9CD7D9EE@bellatlantic.net> Date: Fri, 19 May 2000 19:07:10 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Warner Losh Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) References: <3924931E.A8471B0@bellatlantic.net> <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> <200005190116.TAA98120@harmony.village.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3924931E.A8471B0@bellatlantic.net> Sergey Babkin writes: > : The code seems to guarantee that if the probe routine returns 0 > : then the attach routine will be called right away. So if the probe > : routine returns 0 they don't have to be freed. Actually, the > : comments seem to say explicitly that the resources should be > : freed only if the probe routine returns a negative value but not 0. > : Or am I missing something ? > > The code doesn't write the guarantee. In general probe routines are > supposed to be idempotent. You are supposed to be able to have them > be called multiple times, at least in theory. The probe routine > should not hold resources past the end of its execution, positive or > negative. > > I'm not sure where you found the comments that say that the probe > routine can hold resources after it is called. I couldn't find any. Sorry that I did not quote it in the first e-mail. In kern/device_if.m: # # Probe to see if the device is present. Return 0 if the device exists, # ENXIO if it cannot be found. If some other error happens during the # probe (such as a memory allocation failure), an appropriate error code # should be returned. For cases where more than one driver matches a # device, a priority value can be returned. In this case, success codes # are values less than or equal to zero with the highest value representing # the best match. Failure codes are represented by positive values and # the regular unix error codes should be used for the purpose. # If a driver returns a success code which is less than zero, it must # not assume that it will be the same driver which is attached to the # device. In particular, it must not assume that any values stored in # the softc structure will be available for its attach method and any # resources allocated during probe must be released and re-allocated # if the attach method is called. If a success code of zero is # returned, the driver can assume that it will be the one attached. # # Devices which implement busses should use this method to probe for # the existence of devices attached to the bus and add them as # children. If this is combined with the use of bus_generic_attach, # the child devices will be automatically probed and attached. # METHOD int probe { device_t dev; }; > It is also legal for buses to probe all their devices before attaching > any of them (the pci bus does this, iirc, so that generic drivers can > handle some hardware and more specific drivers can handle other). > There's nothing that states probe_and_attach is the only way to get > things done. That comment does not guarantee that attach will be called right away but I suppose it guarantees that if probe() returns 0 it may expect that attach() will eventually be called and keep the resources and contents of its structs softc between probe() and attach(). > Finally, there's a comment in subr_bus: > device_set_driver(child, best->driver); > if (pri < 0) { > /* > * A bit bogus. Call the probe method again to make sure > * that we have the right description. > */ > DEVICE_PROBE(child); > } > > which indicates to me that the probe routines will be called multiple > times if they return < 0 (pri is the priority they returned, 0 meaning > it is mine and nobody else's). Yes, that's what I said in the first quoted paraghaph: if probe returns <0 (priority arbitration between multiple drivers in a class) or >0 (error) then it must free the resources before exit and don't assume that the contents of struct softc will be presevred between probe and attach. But if probe returns 0 it may keep the resources. Also some resources have problems with freeing them: for example, if a piece of memory was allocated using bus_dmamem_alloc() with lowaddr of BUS_SPACE_MAXADDR_24BIT then bus_dmamem_free() won't really free it but just throw it away (I suppose contigfree() did not exist when it was written). So it's better to keep these resources between probe and attach if probe returns 0. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 16:38:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 91D3537B752 for ; Fri, 19 May 2000 16:38:03 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1138.dip0.t-ipconnect.de [62.156.17.56]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id BAA17724 for ; Sat, 20 May 2000 01:37:42 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 9DF97AC2C for ; Sat, 20 May 2000 01:38:09 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id BAA05861 for hackers@freebsd.org; Sat, 20 May 2000 01:37:51 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 01:37:51 +0200 From: Alexander Langer To: hackers@freebsd.org Subject: further question to bus_alloc_resource Message-ID: <20000520013751.A5852@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! See sys/alpha/isa/mcclock_isa.c: It has attach (which allocs resource), but not detach. Also, it doesn't save the rid in the softc. I wonder, if the generic detach function is capable to clean up the resource without knowing the rid, or if this is a bug. If so, I'm going to write patches. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 16:43:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 9F26537B50B for ; Fri, 19 May 2000 16:43:53 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1138.dip0.t-ipconnect.de [62.156.17.56]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id BAA18525 for ; Sat, 20 May 2000 01:43:41 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 47EE2AC2C for ; Sat, 20 May 2000 01:44:10 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id BAA05971 for hackers@FreeBSD.ORG; Sat, 20 May 2000 01:43:52 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 01:43:52 +0200 From: Alexander Langer To: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource Message-ID: <20000520014352.B5947@cichlids.cichlids.com> References: <20000520013751.A5852@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000520013751.A5852@cichlids.cichlids.com>; from alex@big.endian.de on Sat, May 20, 2000 at 01:37:51AM +0200 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Alexander Langer (alex@big.endian.de): > If so, I'm going to write patches. ... for almost every driver in the tree. Hmm. EITHER almost all people never unloaded their driver, or I still understood wide parts wrong. I grepped through /sys now and only 10% of the drivers save the rid. Strange. Enlighten me, please. .-9 Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 17:35:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (law-f201.hotmail.com [209.185.130.111]) by hub.freebsd.org (Postfix) with SMTP id C9D3937B87E for ; Fri, 19 May 2000 17:35:34 -0700 (PDT) (envelope-from manny8383@hotmail.com) Received: (qmail 91916 invoked by uid 0); 20 May 2000 00:35:34 -0000 Message-ID: <20000520003534.91915.qmail@hotmail.com> Received: from 128.8.96.27 by www.hotmail.com with HTTP; Fri, 19 May 2000 17:35:34 PDT X-Originating-IP: [128.8.96.27] From: "Manny Obrey" To: freebsd-hackers@freebsd.org Date: Fri, 19 May 2000 17:35:34 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw the following near the end of running "make depend;make" during a kernel re-config ... seriously, is this something to be concerned about? I had just d'loaded /usr/src/sys for 4.0-RELEASE about 10 minutes ago. touch hack.c cc -elf -shared -nostdlib hack.c -o hack.So rm -f hack.c ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 17:53:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 590E737BF6E for ; Fri, 19 May 2000 17:53:13 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-18.bellatlantic.net [151.198.117.18]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA23568; Fri, 19 May 2000 20:53:03 -0400 (EDT) Message-ID: <3925E1F6.1D5F02CE@bellatlantic.net> Date: Fri, 19 May 2000 20:53:10 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Jonathan Laventhol Cc: freebsd-hackers@freebsd.org Subject: Re: System management with large groups References: <39255860.FC0F2688@imagination.co.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Laventhol wrote: > > Dear FreeBSD Hackers -- > > I've got a technically-straightfordward but nonetheless > business-critical problem with the groups structures in FreeBSD > which perhaps you kind souls can help me with. > We currently use FreeBSD 3.3-RELEASE through 4.0-RELEASE via > Walnut Creek CDs for DNS, e-mail, web, ftp, various proxies, > tacacs and a number of custom web-delivered databases. There > are maybe 15 small FreeBSD machines doing these jobs. Only > systems management actually log in on the machines, the real > users have NOLOGIN shells. > > We do not currently use NIS but I'm considering it. last time I did something like this was a few years ago with FreeBSD 2.1 but I hope that my comments may be still useful. > I am looking at the technical feasibility of moving to FreeBSD > with Samba and Netatalk. Another approach would be to modify Samba and Netatalk to check the permissions for net users by itself, without bringing this burden to OS. > *** ISSUES *** > > The most significant issue is the limits on groups. Part of this > is because of the inherent limits of user-group-world masks versus > ACLS -- which we can live with and would help us by simpifying > the problems -- and part is because of long-legacy limits within > 4.4bsd. You may want to look at "poor man's ACLs" http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14584 They are not really ACLs but IMHO are useful. > Because of the size and structure of my company a person might need to > be in 20 or 30 groups anyway. > > Because of working around the ACL issue, we'd need to have a large > number > of groups -- perhaps thousands -- and individual users in large > proportion > of those. Some users might even be in *every* group. "In every group" in your case means thousands of groups, not 20 to 30. This may be the real problem. > *** APPARENT CAUSES *** > > 1. I see that the 200-users-per-group limit is gone since 3.0-RELEASE. Was there such a limit ? As far as I remember there are limits for the number of groups in each line of /etc/group and number of characters in each line of /etc/group. But there may be multiple lines in /etc/group (that's true for any kind of Unix except possibly Linux) corresponding to a group. For example: somegroup:*:200:user1,user2,user3 somegroup:*:200:user4,user5,user6 So circumventing these limits is easy. > 2. I'm concerned about the 1+16 groups-per-user issue You can increase that easily. I think NGROUPS is what you need but I can't remember now exactly. I increased that to something like 50 without any problems. But making it equal to a few thousands may be a problem. Or maybe not. Try and see. Of course, it will cause somewhat higher memory consumption and CPU expenses but it may be not that bad. > 3. I'm concerned about large numbers of groups in a flat group(5) file. It may be a bit slow but should not cause any other problems. > *** QUESTIONS *** > > Question 0: Is this a sensible way to solve my access rights > issues? Anybody got a better way altogether? (Maybe just > hack Samba?) Yes, hacking Samba looks like a good solution. > Question 2: What is the relationship between hard-coded NGROUPS > and NGROUPS_MAX, and the sysctl kern.ngroups? NGROUPS is defined to be equal to NGROUPS_MAX. Probably kern.ngroups allows to limit the actual maximal number lower than NGROUPS_MAX. > Question 3: Can I just edit NGROUPS_MAX somewhere and make it Yes. Probably in /sys/sys/syslimits.h. > bigger? Which one do I fix? (Is there a 'make world faq? Never > done it before.) I can't say for sure but most probably you don't need to make world. Just rebuild the kernel and that has a good chance to fix it. Maybe you will also need to rebuild Samba. > Question 4: What do people think might break? Would it be better, > worse, or impossible to do this with NIS? Personally I don't believe in NIS. But NIS may be better in the sense that it uses indexed files instead of /etc/groups, so the searches in them will be fatre. > Question 5: Has anybody done anything like a vigr (like vipw) > for /etc/group? Our (locally-written) user database would be > changing the groups all the time. I think FreeBSD still has no binary indexed file for /etc/group, unlike /etc/master.passwd. So you can just edit /etc/group with vi. It also gives warnings when multiple people try to edit the same file at once. One of the things that I think would be good to implement is the ability to create hierarchies of groups. Say, create a file /etc/metagroups containing: ... group1:*:1000:user1,user2,user3 group2:*:1001:user2,*group1,user4 group3:*:1002:user5,*group2 ... Meaning that group2 also contains all the users from group1 and group3 contains all the users from group2. This file after running some Perl-based or shell-based converter would generate /etc/group containing: ... group1:*:1000:user1,user2,user3 group2:*:1001:user2,user4,user1,user3 group3:*:1002:user5,user2,user4,user1,user3 ... That should be easy enough to implement, just I never got to it. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 18:11:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 6334737B68F for ; Fri, 19 May 2000 18:11:28 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-212.bellatlantic.net [151.198.117.212]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id VAA24310; Fri, 19 May 2000 21:11:17 -0400 (EDT) Message-ID: <3925E63E.EF415CFF@bellatlantic.net> Date: Fri, 19 May 2000 21:11:26 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Alexander Langer Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource References: <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote: > > Thus spake Alexander Langer (alex@big.endian.de): > > > If so, I'm going to write patches. > > ... for almost every driver in the tree. > > Hmm. EITHER almost all people never unloaded their driver, or I still > understood wide parts wrong. > > I grepped through /sys now and only 10% of the drivers save the rid. > > Strange. Enlighten me, please. .-9 If a driver was written with expectation that it will be always compiled in the kernel (as opposed to being loaded as a module) then it never gets unloaded. And many drivers were written before the loadable modules appeared. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 19: 3:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B03C037BE4F; Fri, 19 May 2000 19:03:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA58884; Fri, 19 May 2000 19:03:40 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 19 May 2000 19:03:40 -0700 (PDT) From: Kris Kennaway To: Manny Obrey Cc: freebsd-hackers@freebsd.org Subject: Re: your mail In-Reply-To: <20000520003534.91915.qmail@hotmail.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, 19 May 2000, Manny Obrey wrote: > I saw the following near the end of running "make depend;make" during a > kernel re-config ... seriously, is this something to be concerned about? I No. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri May 19 23: 4: 9 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 0CFFD37BF2D for ; Fri, 19 May 2000 23:04:05 -0700 (PDT) (envelope-from leifn@neland.dk) Received: (from uucp@localhost) by ns.internet.dk (8.9.2/8.9.3) with UUCP id IAA68895; Sat, 20 May 2000 08:04:00 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id IAA85889; Sat, 20 May 2000 08:03:42 +0200 (CEST) (envelope-from leifn@neland.dk) Message-ID: <013501bfc221$2e6a7020$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Cillian Sharkey" , References: <20000519170026.A29241@psn.ie> Subject: Re: Post-shutdown hook for UPS shutdown? Date: Sat, 20 May 2000 08:02:46 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do you control the shutdown? If it is a simple logical signal, i.e. either high or low voltage, perhaps the easiest way would be a hardware solution. It could be as simple as a diode, a large capasitor and a resistor. Your local electronic supplyer could probably build a delay circuit for a few ? or £ ... Leif ----- Original Message ----- From: "Cillian Sharkey" To: Sent: Friday, May 19, 2000 6:00 PM Subject: Post-shutdown hook for UPS shutdown? > Hi Folks, > > I need to execute a script (which tells the UPS to turn off) *after* the > system has come to a safe halt from shutdown -h. I can't place the commands > in /etc/rc.shutdown because this is too early in the shutdown sequence. > > Unfortunately, the UPS in question (APC Back-UPS 650) is not a "smart" one, > (i.e. it doesn't have an in-built delay when a shutdown signal is received > which gives time for all attached devices to shutdown) and I'm pretty much > stuck with it. The software is the Network UPS Tools (NUT) package. > > Basically, is there currently any way to execute a post-shutdown script once > the system has "halted" ? If not, is this feature possible to add ? > > Thanks in advance, > > -- > Cillian > > > 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 May 20 0:12: 2 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 D539437B517; Sat, 20 May 2000 00:11:51 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA96475; Sat, 20 May 2000 01:11:43 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id BAA44934; Sat, 20 May 2000 01:11:00 -0600 (MDT) Message-Id: <200005200711.BAA44934@billy-club.village.org> To: Sergey Babkin Subject: Re: request for review: bus_alloc_resource(9) Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 19 May 2000 19:07:10 EDT." <3925C91E.9CD7D9EE@bellatlantic.net> References: <3925C91E.9CD7D9EE@bellatlantic.net> <3924931E.A8471B0@bellatlantic.net> <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> <200005190116.TAA98120@harmony.village.org> Date: Sat, 20 May 2000 01:11:00 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3925C91E.9CD7D9EE@bellatlantic.net> Sergey Babkin writes: : Warner Losh wrote: : > : > In message <3924931E.A8471B0@bellatlantic.net> Sergey Babkin writes: : > : The code seems to guarantee that if the probe routine returns 0 : > : then the attach routine will be called right away. So if the probe : > : routine returns 0 they don't have to be freed. Actually, the : > : comments seem to say explicitly that the resources should be : > : freed only if the probe routine returns a negative value but not 0. : > : Or am I missing something ? : > : > The code doesn't write the guarantee. In general probe routines are : > supposed to be idempotent. You are supposed to be able to have them : > be called multiple times, at least in theory. The probe routine : > should not hold resources past the end of its execution, positive or : > negative. : > : > I'm not sure where you found the comments that say that the probe : > routine can hold resources after it is called. I couldn't find any. : : Sorry that I did not quote it in the first e-mail. In kern/device_if.m: A pointer would have been sufficient :-) : # Probe to see if the device is present. Return 0 if the device exists, : # ENXIO if it cannot be found. If some other error happens during the : # probe (such as a memory allocation failure), an appropriate error code : # should be returned. For cases where more than one driver matches a : # device, a priority value can be returned. In this case, success codes : # are values less than or equal to zero with the highest value representing : # the best match. Failure codes are represented by positive values and : # the regular unix error codes should be used for the purpose. : : # If a driver returns a success code which is less than zero, it must : # not assume that it will be the same driver which is attached to the : # device. In particular, it must not assume that any values stored in : # the softc structure will be available for its attach method and any : # resources allocated during probe must be released and re-allocated : # if the attach method is called. If a success code of zero is : # returned, the driver can assume that it will be the one attached. Notice it doesn't say that one can hold RESOURCES past the end of probe. Only that values set in the softc (which one should try to avoid) aren't guaranteed to be there if the return value is < 0. It can only assume that it will be the driver that is attached. This comment is poorly worded anyway and should be changed to explicitly state that one shouldn't hold resources at the end of the probe routine. : That comment does not guarantee that attach will be called right : away but I suppose it guarantees that if probe() returns 0 it : may expect that attach() will eventually be called and keep the : resources and contents of its structs softc between probe() and : attach(). Yes and no. It has long been stated that one cannot hold resources past the end of a probe. It is attaches job to allocate them permanantly, code and docs notwithstanding. I recall this coming up from time to time on the newbus list a long time ago, but haven't checked the archives. Going back in time to prenewbus, this certainly was the case. And it is the case in other Unixes that I've worked on in the past. : Yes, that's what I said in the first quoted paraghaph: if probe : returns <0 (priority arbitration between multiple drivers in a class) : or >0 (error) then it must free the resources before exit and don't : assume that the contents of struct softc will be presevred between : probe and attach. But if probe returns 0 it may keep the resources. I'm still not sure that I agree. Unless I hear from the new-bus meister, I won't feel obligated to necessarily keep this condition in the NEWCARD code. I don't think I'll need to violate it, but I will if I have to because of how things are allocated in most device drivers right now. : Also some resources have problems with freeing them: for example, : if a piece of memory was allocated using bus_dmamem_alloc() with : lowaddr of BUS_SPACE_MAXADDR_24BIT then bus_dmamem_free() won't : really free it but just throw it away (I suppose contigfree() did not : exist when it was written). So it's better to keep these resources : between probe and attach if probe returns 0. No. Absolutely not. One should allocate them once only in the attach code. The probe code almost never needs to do a DMA to probe the device. Probes are supposed to be non-destructive (eg read only on the registers) if at all possible. One shouldn't try to allocate it there anyway for the same reason you say we should. If you are using it to see if the device exists, and it doesn't, then you can't free it. Sounds like a bad way to probe the hardware. The probe routine is supposed to do the absolute minimum to the hardware to see if it is really there. It shouldn't be bringing in all kinds of extra resources that it doesn't need to determine if the device is there or not. Probe's role in self-identiftying buses is simple. Check the identifying characteristics against a table and return the string associated with that characteristic. On the ISA bus (the only non-self identifying bus we have), it is sadly necessary to touch the hardware to see if it readlly exists. Some hardware is easy to non-destructively probe. Most of the early pc hardware is impossible to non-destructively probe. The changes to the state of the device for an ISA bus probe shouldn't be relied on in the attach routine (sio violates this, for example). It makes it harder to adapt to self identifying buses in the future (I had to call the isa probe to set the hardware to a known state in the pci probe code which should have just checked the config ID tags and returned). Likewise with pccard. I guess that's another reason I tend to be vehiment in keeping the wall of separation between the two. I've been burned by drivers in the past that didn't and it was a royal PITA to sort that all out. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 0:12:47 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 94E1337BFDE for ; Sat, 20 May 2000 00:12:43 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA96479; Sat, 20 May 2000 01:12:41 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id BAA44947; Sat, 20 May 2000 01:11:58 -0600 (MDT) Message-Id: <200005200711.BAA44947@billy-club.village.org> To: Alexander Langer Subject: Re: further question to bus_alloc_resource Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 May 2000 01:43:52 +0200." <20000520014352.B5947@cichlids.cichlids.com> References: <20000520014352.B5947@cichlids.cichlids.com> <20000520013751.A5852@cichlids.cichlids.com> Date: Sat, 20 May 2000 01:11:58 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000520014352.B5947@cichlids.cichlids.com> Alexander Langer writes: : Strange. Enlighten me, please. .-9 If you don't have a detach routine, you can't unload the driver. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 1: 1:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web4205.mail.yahoo.com (web4205.mail.yahoo.com [216.115.104.138]) by hub.freebsd.org (Postfix) with SMTP id A816137BA8B for ; Sat, 20 May 2000 01:01:43 -0700 (PDT) (envelope-from sh_fazelian@yahoo.com) Message-ID: <20000520080142.18938.qmail@web4205.mail.yahoo.com> Received: from [195.200.226.110] by web4205.mail.yahoo.com; Sat, 20 May 2000 01:01:42 PDT Date: Sat, 20 May 2000 01:01:42 -0700 (PDT) From: Shadi Fazelian Subject: one question: To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello and don't tire from destroying servers one question: in my server all of services is down(like ftp,telnet,....) and in crontab there isn't somthing. but somebody can access to my server and can send e_mail please guide me thanks shadi __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 1:33:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 20E6837B5F2; Sat, 20 May 2000 01:33:09 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1784 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Sat, 20 May 2000 10:32:11 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Postfix, from userid 200) id 129E43F4; Sat, 20 May 2000 10:32:36 +0200 (METDST) Subject: Re: Post-shutdown hook for UPS shutdown? In-Reply-To: <20000519104048.A12491@shale.csir.co.za> from Jeremy Lea at "May 19, 0 10:40:48 am" To: reg@FreeBSD.ORG (Jeremy Lea) Date: Sat, 20 May 2000 10:32:36 +0200 (METDST) Cc: cns@psn.ie, hackers@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 915 Message-Id: <20000520083236.129E43F4@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From the keyboard of Jeremy Lea: > Just an idea... > > On Fri, May 19, 2000 at 05:00:26PM +0100, Cillian Sharkey wrote: > > Basically, is there currently any way to execute a post-shutdown script once > > the system has "halted" ? If not, is this feature possible to add ? > > Why not let the machine reboot, and check the power before anything else > in /etc/rc. This is what i once did for a dumb UPS in FreeBSD 2.x and it worked quite well. That package is still available on http://www.freebsd-support.de/misc with all the scripts and driver if you might want to have a look at it. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 1:33:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 8CE1E37B60E for ; Sat, 20 May 2000 01:33:12 -0700 (PDT) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.9.3/8.8.7) with ESMTP id EAA68425; Sat, 20 May 2000 04:32:11 -0400 (EDT) (envelope-from efutch@nyct.net) Date: Sat, 20 May 2000 04:32:17 -0400 (EDT) From: "Eric D. Futch" To: Shadi Fazelian Cc: hackers@FreeBSD.ORG Subject: Re: one question: In-Reply-To: <20000520080142.18938.qmail@web4205.mail.yahoo.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 You might want to try sticking sendmail_enable="NO" into your /etc/rc.conf. There's a bunch of other services that get started by default, /etc/defaults/rc.conf has all the details. That's for FreeBSD 4 and up atleast. If I remember correctly to fix this in versions smaller than 4, just edit the /etc/rc.conf. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Sat, 20 May 2000, Shadi Fazelian wrote: >Hello >and don't tire from destroying servers >one question: >in my server all of services is down(like >ftp,telnet,....) >and in crontab there isn't somthing. >but somebody can access to my server and can send >e_mail >please guide me >thanks shadi > >__________________________________________________ >Do You Yahoo!? >Send instant messages & get email alerts with Yahoo! Messenger. >http://im.yahoo.com/ > > >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 May 20 1:42: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 4814C37B548 for ; Sat, 20 May 2000 01:41:58 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id EAA00978 for ; Sat, 20 May 2000 04:41:57 -0400 Date: Sat, 20 May 2000 04:41:56 -0400 (EDT) From: Mike Nowlin To: freebsd-hackers@freebsd.org Subject: hardware memory question 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 This isn't really FBSD-related, but this seems like a good place to ask... I have a Linux dual P-II 333 that had the following memory config: bank 1 - 32M DIMM/100 bank 2 - 64M DIMM/100 bank 3 - 64M DIMM/100 Over the last few days, I've started getting tons of sig11's, especially when X is running. "Ding ding ding! Memory's failing!" Sometimes, the machine wouldn't even boot completely without being turned off for half an hour or so to cool down... Pulled out the 32M from bank 1 and moved the 64M from bank 3->bank 1 - no SEGV's yet, and it's pretty loaded right now. (Enlightenment, Gnome, Gimp, Glade, lots of xterms, several Gnome builtins, and the "watch TV" program for my video capture card.) The funny thing is, and my question, is that all of a sudden, things are running MUCH faster now with 128M than with the 160M before. (This is an Intel DK440LX motherboard.) Is there something about DIMMs that could cause a major operational slow-down from a progressively-failing DIMM that doesn't result in any obvious problems like sig11? --tnx, mike - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - "I was thinking of the immortal words of Socrates, who said, 'I drank what?'" -- Chris Knight (Val Kilmer), Real Genius Mike Nowlin, N8NVW mike@argos.org http://www.viewsnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 2:46:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 16C5637B52B for ; Sat, 20 May 2000 02:46:13 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1129.dip0.t-ipconnect.de [62.156.17.41]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id LAA00748; Sat, 20 May 2000 11:45:58 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 65299AC2C; Sat, 20 May 2000 11:46:29 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id LAA02043; Sat, 20 May 2000 11:46:07 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 11:46:07 +0200 From: Alexander Langer To: Sergey Babkin Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource Message-ID: <20000520114607.A1832@cichlids.cichlids.com> References: <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <3925E63E.EF415CFF@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3925E63E.EF415CFF@bellatlantic.net>; from babkin@bellatlantic.net on Fri, May 19, 2000 at 09:11:26PM -0400 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Sergey Babkin (babkin@bellatlantic.net): > compiled in the kernel (as opposed to being loaded as a module) > then it never gets unloaded. And many drivers were written before > the loadable modules appeared. Yes. But what about the others. /sys/dev/aha/aha_mca.c for example - it is part of module (aha), allocs resources, but never releases them. Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 2:57:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id 4CE6F37B55C for ; Sat, 20 May 2000 02:57:00 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1129.dip0.t-ipconnect.de [62.156.17.41]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id LAA02733; Sat, 20 May 2000 11:56:41 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 407FDAC2C; Sat, 20 May 2000 11:57:13 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id LAA02270; Sat, 20 May 2000 11:56:52 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 11:56:52 +0200 From: Alexander Langer To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource Message-ID: <20000520115652.C1832@cichlids.cichlids.com> References: <20000520014352.B5947@cichlids.cichlids.com> <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <200005200711.BAA44947@billy-club.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200005200711.BAA44947@billy-club.village.org>; from imp@village.org on Sat, May 20, 2000 at 01:11:58AM -0600 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Warner Losh (imp@village.org): > : Strange. Enlighten me, please. .-9 > If you don't have a detach routine, you can't unload the driver. How does one unload aha.ko then (for the aha_mca.c cards)? That needs to be fixed. Shall I? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 3:15: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 8A1F737B664 for ; Sat, 20 May 2000 03:14:59 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 12t6HY-00029C-0K; Sat, 20 May 2000 10:14:58 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA39975; Sat, 20 May 2000 11:20:17 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 20 May 2000 11:18:56 +0100 (BST) From: Doug Rabson To: Alexander Langer Cc: hackers@freebsd.org Subject: Re: further question to bus_alloc_resource In-Reply-To: <20000520013751.A5852@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 May 2000, Alexander Langer wrote: > Hello! > > See sys/alpha/isa/mcclock_isa.c: > It has attach (which allocs resource), but not detach. > Also, it doesn't save the rid in the softc. > > I wonder, if the generic detach function is capable to clean up the > resource without knowing the rid, or if this is a bug. > > If so, I'm going to write patches. There is really no need. The mcclock driver can't be detached since its required for normal system functioning (its the main clock source). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 3:19:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.surf1.de (mail.surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id D373137B548 for ; Sat, 20 May 2000 03:19:22 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from cichlids.com (p3E9C1129.dip0.t-ipconnect.de [62.156.17.41]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id MAA06989; Sat, 20 May 2000 12:19:10 +0200 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id CF2D3AC2C; Sat, 20 May 2000 12:19:40 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA03042; Sat, 20 May 2000 12:19:19 +0200 (CEST) (envelope-from alex) Date: Sat, 20 May 2000 12:19:19 +0200 From: Alexander Langer To: Doug Rabson Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource Message-ID: <20000520121919.A3021@cichlids.cichlids.com> References: <20000520013751.A5852@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dfr@nlsystems.com on Sat, May 20, 2000 at 11:18:56AM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Doug Rabson (dfr@nlsystems.com): > There is really no need. The mcclock driver can't be detached since its > required for normal system functioning (its the main clock source). OK. I agree. It was just the first driver I got, so far only an example (bad one). What about aha? Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 4:52:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A8CAF37B589; Sat, 20 May 2000 04:52:45 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id HAA00591; Sat, 20 May 2000 07:52:28 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sat, 20 May 2000 07:52:28 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Dmitry Samersoff Cc: freebsd-net@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: bpf question 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, 17 May 2000, Dmitry Samersoff wrote: > I have traffic metering program using bpf, > it works fine on relatevly free net but looses about 30% > of packets on havy loaded one. Two possibilities come to mind: 1) You machine is too slow (pretty slow), your bus is too slow (ISA), or your cards are too slow (maybe if_ed). 2) You're using multiple processes/rforks to support the application, which results in a full context switch during BPF reads. Instead, use our userland pthreads library. Only you can tell us about (1) -- I can tell you I have successfully snarfed 60+mbps (probably more like 70) off of two 100mbps interfaces simultaneously with the CPU still quite low on FreeBSD 4.0, with a moderately decent machine (400mhzish box). There was no packet loss at all, and I was pulling the whole packet off the wire, not just the header. In this experiment, the limiting factors were the data-pumping machines, not the sniffing machine. Number (2) is interesting -- if I run two tcpdumps at the same time, I see a huge loss of performance, as all copies from kernel to userland happen twice, and many packet deliveries cause both processes to wake up and be scheduled. For high speed sniffing, using only a single process (i.e., just a relatively fast kernel->user1->kernel switch). Preventing a full userland context switch and making sure all BPF data goes through a single process makes a big difference (measurements on a p166). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 5: 2: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 E099837B589 for ; Sat, 20 May 2000 05:02:41 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id IAA12365; Sat, 20 May 2000 08:02:36 -0400 (EDT) Date: Sat, 20 May 2000 08:01:44 -0400 (EDT) From: Zhihui Zhang To: Joy Ganguly Cc: freebsd-hackers Subject: Re: OBJ_OPT??? In-Reply-To: <3925B8EE.E901BB31@falcon.niksun.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, 19 May 2000, Joy Ganguly wrote: > hi all > > what does the flag OBJ_OPT mean?? i read it deals with some sort of IO > optimization. but i dont know what it actually does. any insights on > this?? IIRC, when you do an I/O on a file and some of the pages of that file are already in the memory. In this case, you only need to fix the mapping without any real I/O on these page, this is called I/O OPTmization. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 6:31:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 3D8EF37B67E; Sat, 20 May 2000 06:31:38 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-218.bellatlantic.net [151.198.117.218]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id JAA10766; Sat, 20 May 2000 09:31:24 -0400 (EDT) Message-ID: <392693B6.1FB6C64C@bellatlantic.net> Date: Sat, 20 May 2000 09:31:34 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Warner Losh Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: request for review: bus_alloc_resource(9) References: <3925C91E.9CD7D9EE@bellatlantic.net> <3924931E.A8471B0@bellatlantic.net> <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> <200005190116.TAA98120@harmony.village.org> <200005200711.BAA44934@billy-club.village.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <3925C91E.9CD7D9EE@bellatlantic.net> Sergey Babkin writes: > : # If a driver returns a success code which is less than zero, it must > : # not assume that it will be the same driver which is attached to the > : # device. In particular, it must not assume that any values stored in > : # the softc structure will be available for its attach method and any > : # resources allocated during probe must be released and re-allocated ^^^^^^^^^^^^^^^^^^^^ > : # if the attach method is called. If a success code of zero is > : # returned, the driver can assume that it will be the one attached. > > Notice it doesn't say that one can hold RESOURCES past the end of > probe. Only that values set in the softc (which one should try to It says, about the case of negative return value. So I guess that implies that in case if 0 is returned keeping resources is permitted. > avoid) aren't guaranteed to be there if the return value is < 0. It > can only assume that it will be the driver that is attached. This > comment is poorly worded anyway and should be changed to explicitly > state that one shouldn't hold resources at the end of the probe > routine. I suppose that "driver can assume that it will be the one attached" means that the probe routine will not be called again for this device, thet the resources won't change and that the attach routine will be called eventually. Provided with all this keeping the resources seems to be safe. But of course that's only my interpretation. > : That comment does not guarantee that attach will be called right > : away but I suppose it guarantees that if probe() returns 0 it > : may expect that attach() will eventually be called and keep the > : resources and contents of its structs softc between probe() and > : attach(). > > Yes and no. It has long been stated that one cannot hold resources > past the end of a probe. It is attaches job to allocate them > permanantly, code and docs notwithstanding. I recall this coming up > from time to time on the newbus list a long time ago, but haven't > checked the archives. > > Going back in time to prenewbus, this certainly was the case. And it > is the case in other Unixes that I've worked on in the past. As far as I remember in prenewbus there were no "official resources". Yes, I agree that keeping anything allocated when returning from probe is a bad idea. > : Yes, that's what I said in the first quoted paraghaph: if probe > : returns <0 (priority arbitration between multiple drivers in a class) > : or >0 (error) then it must free the resources before exit and don't > : assume that the contents of struct softc will be presevred between > : probe and attach. But if probe returns 0 it may keep the resources. > > I'm still not sure that I agree. Unless I hear from the new-bus > meister, I won't feel obligated to necessarily keep this condition in > the NEWCARD code. I don't think I'll need to violate it, but I will > if I have to because of how things are allocated in most device > drivers right now. It's not like I'm saying that it MUST keep the resources from probe but I suppose it's allowed to if it really wants. > : Also some resources have problems with freeing them: for example, > : if a piece of memory was allocated using bus_dmamem_alloc() with > : lowaddr of BUS_SPACE_MAXADDR_24BIT then bus_dmamem_free() won't > : really free it but just throw it away (I suppose contigfree() did not > : exist when it was written). So it's better to keep these resources > : between probe and attach if probe returns 0. > > No. Absolutely not. One should allocate them once only in the attach > code. The probe code almost never needs to do a DMA to probe the > device. Probes are supposed to be non-destructive (eg read only on > the registers) if at all possible. One shouldn't try to allocate it > there anyway for the same reason you say we should. If you are using > it to see if the device exists, and it doesn't, then you can't free > it. Sounds like a bad way to probe the hardware. The probe routine What about the case when device exists but is broken/misconfigured ? Suppose, someone got the port address right but the DMA channel wrong. Well, of course, this more intrusive part of probe may as well be moved to the attach routine. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 8:30:22 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 7A8FE37B793 for ; Sat, 20 May 2000 08:30:17 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA99354; Sat, 20 May 2000 09:30:15 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id JAA51630; Sat, 20 May 2000 09:29:36 -0600 (MDT) Message-Id: <200005201529.JAA51630@billy-club.village.org> To: Alexander Langer Subject: Re: further question to bus_alloc_resource Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 May 2000 11:56:52 +0200." <20000520115652.C1832@cichlids.cichlids.com> References: <20000520115652.C1832@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <200005200711.BAA44947@billy-club.village.org> Date: Sat, 20 May 2000 09:29:35 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000520115652.C1832@cichlids.cichlids.com> Alexander Langer writes: : > : Strange. Enlighten me, please. .-9 : > If you don't have a detach routine, you can't unload the driver. : : How does one unload aha.ko then (for the aha_mca.c cards)? One doesn't unload aha right now. : That needs to be fixed. Shall I? Sure. Please have Matt Dodd review it as well as myself. He's the mca maintainer, and I do the aha driver. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 9:24:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out2.apple.com (mail-out2.apple.com [17.254.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 05CCC37B741 for ; Sat, 20 May 2000 09:24:21 -0700 (PDT) (envelope-from justin@walkeridsl1.apple.com) Received: from mailgate2.apple.com (A17-129-100-225.apple.com [17.129.100.225]) by mail-out2.apple.com (8.9.3/8.9.3) with ESMTP id JAA11044 for ; Sat, 20 May 2000 09:24:19 -0700 (PDT) Received: from scv3.apple.com (scv3.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Sat, 20 May 2000 09:24:18 -0700 Received: from walkeridsl1.apple.com (walkeridsl1.apple.com [17.219.158.66]) by scv3.apple.com (8.9.3/8.9.3) with ESMTP id JAA28617; Sat, 20 May 2000 09:24:18 -0700 (PDT) Received: (from justin@localhost) by walkeridsl1.apple.com (8.9.1/8.9.1) id JAA00646; Sat, 20 May 2000 09:24:19 -0700 (PDT) Message-Id: <200005201624.JAA00646@walkeridsl1.apple.com> To: Shadi Fazelian Subject: Re: one question: Cc: hackers@freebsd.org Date: Sat, 20 May 2000 09:24:18 -0700 From: "Justin C. Walker" Reply-To: justin@apple.com X-Mailer: by Apple MailViewer (2.105.dev) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Shadi Fazelian > Date: 2000-05-20 01:20:07 -0700 > To: hackers@FreeBSD.ORG > Subject: one question: > X-Loop: FreeBSD.ORG > Delivered-to: freebsd-hackers@freebsd.org > > Hello > and don't tire from destroying servers > one question: > in my server all of services is down(like > ftp,telnet,....) > and in crontab there isn't somthing. > but somebody can access to my server and can send > e_mail In the /etc/rc* files you should find a line that starts 'sendmail'. That is likely the way that mail is delivered to your system. A "ps aux" will verify whether 'sendmail' is running. Regards, Justin -- Justin C. Walker, Curmudgeon-At-Large * Institute for General Semantics | Manager, CoreOS Networking | When crypto is outlawed, Apple Computer, Inc. | Only outlaws will have crypto. 2 Infinite Loop | Cupertino, CA 95014 | *-------------------------------------*-------------------------------* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 10: 3:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net [207.217.121.31]) by hub.freebsd.org (Postfix) with ESMTP id F253D37B5A0; Sat, 20 May 2000 10:03:07 -0700 (PDT) (envelope-from natepuri@office.ompages.com) Received: from laptop.ompages.com (1Cust148.tnt1.sacramento2.ca.da.uu.net [63.15.247.148]) by emu.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id KAA05615; Sat, 20 May 2000 10:03:00 -0700 (PDT) Received: from laptop.ompages.com (natepuri@localhost.ompages.com [127.0.0.1]) by laptop.ompages.com (8.9.3/8.9.3) with ESMTP id QAA82979; Fri, 19 May 2000 16:54:40 -0700 (PDT) Message-Id: <200005192354.QAA82979@laptop.ompages.com> Date: Fri, 19 May 2000 16:54:39 -0700 (PDT) From: Nate Puri Subject: question about writing apps for freebsd 4.0 To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, This is a question my partner should be asking, but he is a linux guy and doesn't seem interested in pursuing this topic. I'm not a programmer, but it seems I must query this... We have a program that is a re-write of dhis.org dhid application. We intend it to be used to create the infrastructure for what will become a public accessible VPN. The daemon that sits on the client side, sends out udp packets to the server to let it know what the dynamic IP of the box is so that the IP will appear visible to the rest of the www. Our problem is that for some reason on 4.0 no upd packets get sent out at all. Right now our client runs on all Linuxes, and OpenBSD. I have aspirations for all the BSDs to be supported by us. We need some help. We haven't decided what we're going to license this thing under. It's not a child of the dhid.org daemon; it's a total re-write. But we are going to choose either GPL or BSD no doubt. If you are interested in helping, please let me know directly and I will shoot you the URL of the client source. Thanks a lot everyone. Our project is for a good cause. We trying to make it easy for average people to have secure home networks. (As if average people wanted that), but we believe at some point in the near future average people will. For now, geeky people will and that good enough for us... Thanks all in advance... -Nate -- Nate Puri, President Installation, Administration, Security BankofData.net (not yet live) and Support for Home and Small Networks... natepuri@office.ompages.com One of The Wheel's Massive Holdings To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 11: 0:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id B015A37B5E7 for ; Sat, 20 May 2000 11:00:08 -0700 (PDT) (envelope-from cns@psn.ie) Received: from alto ([192.168.0.254] helo=alto.internal) by mailhub.psn.ie with esmtp (Exim 3.12 #2) id 12tDGd-000FNl-00 for hackers@freebsd.org; Sat, 20 May 2000 18:42:27 +0100 Received: from cns by alto.internal with local (Exim 3.12 #1) id 12tDGd-0008rU-00 for hackers@freebsd.org; Sat, 20 May 2000 18:42:27 +0100 Date: Sat, 20 May 2000 18:42:27 +0100 From: Cillian Sharkey To: hackers@freebsd.org Subject: Re: Post-shutdown hook for UPS shutdown? Message-ID: <20000520184227.A34044@psn.ie> References: <20000519170026.A29241@psn.ie> <013501bfc221$2e6a7020$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <013501bfc221$2e6a7020$0e00a8c0@neland.dk>; from leifn@neland.dk on Sat, May 20, 2000 at 08:02:46AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How do you control the shutdown? > > If it is a simple logical signal, i.e. either high or low voltage, perhaps > the easiest way would be a hardware solution. > > It could be as simple as a diode, a large capasitor and a resistor. > > Your local electronic supplyer could probably build a delay circuit for a > few ? or £ ... Hmm, I hadn't considered a hardware solution. But I think I'll try the [slightly easier] software method suggested by a few of the others first, i.e. reboot rather than shutdown and use /etc/rc to manage the situiation from there. Thanks to all who replied! I'll probably report back on my progress later. -- Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 11:41:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 4625E37B53A for ; Sat, 20 May 2000 11:41:45 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id LAA04879; Sat, 20 May 2000 11:38:02 -0700 (PDT) Date: Sat, 20 May 2000 11:38:01 -0700 From: Brooks Davis To: Mike Nowlin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: hardware memory question Message-ID: <20000520113801.A3741@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from mike@argos.org on Sat, May 20, 2000 at 04:41:56AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 20, 2000 at 04:41:56AM -0400, Mike Nowlin wrote: > > This isn't really FBSD-related, but this seems like a good place to ask... > > I have a Linux dual P-II 333 that had the following memory config: > > bank 1 - 32M DIMM/100 > bank 2 - 64M DIMM/100 > bank 3 - 64M DIMM/100 > > Over the last few days, I've started getting tons of sig11's, especially > when X is running. "Ding ding ding! Memory's failing!" Sometimes, the > machine wouldn't even boot completely without being turned off for half an > hour or so to cool down... > > Pulled out the 32M from bank 1 and moved the 64M from bank 3->bank 1 - no > SEGV's yet, and it's pretty loaded right now. (Enlightenment, Gnome, > Gimp, Glade, lots of xterms, several Gnome builtins, and the "watch TV" > program for my video capture card.) > > The funny thing is, and my question, is that all of a sudden, things are > running MUCH faster now with 128M than with the 160M before. (This is an > Intel DK440LX motherboard.) Is there something about DIMMs that could > cause a major operational slow-down from a progressively-failing DIMM that > doesn't result in any obvious problems like sig11? Most motherboard vendors strongly recommend that you not mix DIMMs either in size or manufacture so there might have been some wacky timing issues form the mixed DIMMs. Also, the last bank is sometimes a bit wacked due to chipset limitations so you might have hit something like that. -- 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 Sat May 20 12: 1: 7 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 2704937B67F for ; Sat, 20 May 2000 12:01:05 -0700 (PDT) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id NAA290434; Sat, 20 May 2000 13:00:59 -0600 (MDT) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Sat, 20 May 2000 13:00:59 -0600 From: Ronald G Minnich To: Nick Sayer Cc: hackers@FreeBSD.ORG Subject: Re: rexec as root In-Reply-To: <391C12B5.E5A2DCD3@quack.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 May 2000, Nick Sayer wrote: > I would like to gather some opinions in regards to _very slightly_ > backing off > on rexec's security. > > rexec makes the following checks, and refuses to allow usage if any are > true: > > uid == 0 I turned off this check at sarnoff six years ago. rexec allows you to quickly run lots of commands across a cluster, given the right tool (see http:/www.acl.lanl.gov/~rminnich and look at vex). Using rexec I could run commands across a 128-node cluster in less than a second. Nothing I have ever seen is nearly as fast. A secure low-overhead remote exec is the right thing; rexec with uid == 0 disabled is the next-best thing. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 12:46:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 0924537B514 for ; Sat, 20 May 2000 12:46:42 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12tFCq-000Ajk-0U; Sat, 20 May 2000 20:46:41 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA90886; Sat, 20 May 2000 20:52:12 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 20 May 2000 20:50:45 +0100 (BST) From: Doug Rabson To: Alexander Langer Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource In-Reply-To: <20000520121919.A3021@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 May 2000, Alexander Langer wrote: > Thus spake Doug Rabson (dfr@nlsystems.com): > > > There is really no need. The mcclock driver can't be detached since its > > required for normal system functioning (its the main clock source). > > OK. I agree. > It was just the first driver I got, so far only an example (bad one). > What about aha? It would be nice to be able te detach most drivers. I think that when aha was converted originally, cam didn't support detach but I'm pretty sure it does now. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 13: 8:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id CCD9837B6A1 for ; Sat, 20 May 2000 13:08:49 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-233.bellatlantic.net [151.198.117.233]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id QAA19860; Sat, 20 May 2000 16:08:38 -0400 (EDT) Message-ID: <3926F0CF.DA23E3AD@bellatlantic.net> Date: Sat, 20 May 2000 16:08:47 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Alexander Langer Cc: hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource References: <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <3925E63E.EF415CFF@bellatlantic.net> <20000520114607.A1832@cichlids.cichlids.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Langer wrote: > > Thus spake Sergey Babkin (babkin@bellatlantic.net): > > > compiled in the kernel (as opposed to being loaded as a module) > > then it never gets unloaded. And many drivers were written before > > the loadable modules appeared. > > Yes. But what about the others. > /sys/dev/aha/aha_mca.c for example - it is part of module (aha), > allocs resources, but never releases them. Well, I suppose unloading drivers makes much sense only in case if hardware supports hot-plug. I see the argument of upgrading the driver version without reboot as purely theoretical. For driver debugging the need to chnage the driver commonly happens after the old version somehow wedges the system. And upgrading drivers on a running production system is not something I personally would do. This is a dangerous operation and if it would cause any problems they would better happen at pre-scheduled boot time, not on a running machines with users. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 14: 4:11 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 00B2437B6F2 for ; Sat, 20 May 2000 14:03:50 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA00264; Sat, 20 May 2000 15:03:48 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id PAA53985; Sat, 20 May 2000 15:03:11 -0600 (MDT) Message-Id: <200005202103.PAA53985@billy-club.village.org> To: Alexander Langer Subject: Re: further question to bus_alloc_resource Cc: Sergey Babkin , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 May 2000 11:46:07 +0200." <20000520114607.A1832@cichlids.cichlids.com> References: <20000520114607.A1832@cichlids.cichlids.com> <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <3925E63E.EF415CFF@bellatlantic.net> Date: Sat, 20 May 2000 15:03:11 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000520114607.A1832@cichlids.cichlids.com> Alexander Langer writes: : > compiled in the kernel (as opposed to being loaded as a module) : > then it never gets unloaded. And many drivers were written before : > the loadable modules appeared. : : Yes. But what about the others. : /sys/dev/aha/aha_mca.c for example - it is part of module (aha), : allocs resources, but never releases them. aha doesn't support being unloaded. At the time it was written, CAM drivers couldn't be unloaded. So I never bothered to make it work right. Also, the aha driver was written before newbus, and then gradually hacked to be more and more newbus-like until it has reached the state it is in today, which is good enough to work, but has lots of nits still. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 14: 6: 1 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 0375037B5FE for ; Sat, 20 May 2000 14:05:57 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA00276; Sat, 20 May 2000 15:05:55 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id PAA54031; Sat, 20 May 2000 15:05:19 -0600 (MDT) Message-Id: <200005202105.PAA54031@billy-club.village.org> To: Sergey Babkin Subject: Re: further question to bus_alloc_resource Cc: Alexander Langer , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 May 2000 16:08:47 EDT." <3926F0CF.DA23E3AD@bellatlantic.net> References: <3926F0CF.DA23E3AD@bellatlantic.net> <20000520013751.A5852@cichlids.cichlids.com> <20000520014352.B5947@cichlids.cichlids.com> <3925E63E.EF415CFF@bellatlantic.net> <20000520114607.A1832@cichlids.cichlids.com> Date: Sat, 20 May 2000 15:05:19 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3926F0CF.DA23E3AD@bellatlantic.net> Sergey Babkin writes: : Well, I suppose unloading drivers makes much sense only in case : if hardware supports hot-plug. And when one is developing the driver, it helps a whole lot to add unload capability. kldunload takes 1 second. reboot takes 120. : I see the argument of upgrading the : driver version without reboot as purely theoretical. For driver : debugging the need to chnage the driver commonly happens after : the old version somehow wedges the system. And upgrading drivers : on a running production system is not something I personally would : do. This is a dangerous operation and if it would cause any problems : they would better happen at pre-scheduled boot time, not on a running : machines with users. That's why loading drivers at higher security levels is prohibited. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 14:10:29 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 7D66737B74B; Sat, 20 May 2000 14:10:13 -0700 (PDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA00293; Sat, 20 May 2000 15:10:12 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost.village.org [127.0.0.1]) by billy-club.village.org (8.9.3/8.8.3) with ESMTP id PAA54082; Sat, 20 May 2000 15:09:35 -0600 (MDT) Message-Id: <200005202109.PAA54082@billy-club.village.org> To: Sergey Babkin Subject: Re: request for review: bus_alloc_resource(9) Cc: Alexander Langer , doc@FreeBSD.ORG, hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 20 May 2000 09:31:34 EDT." <392693B6.1FB6C64C@bellatlantic.net> References: <392693B6.1FB6C64C@bellatlantic.net> <3925C91E.9CD7D9EE@bellatlantic.net> <3924931E.A8471B0@bellatlantic.net> <20000518223846.A16098@cichlids.cichlids.com> <200005182332.RAA97696@harmony.village.org> <200005190116.TAA98120@harmony.village.org> <200005200711.BAA44934@billy-club.village.org> Date: Sat, 20 May 2000 15:09:35 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <392693B6.1FB6C64C@bellatlantic.net> Sergey Babkin writes: : Warner Losh wrote: : > : > In message <3925C91E.9CD7D9EE@bellatlantic.net> Sergey Babkin writes: : : > : # If a driver returns a success code which is less than zero, it must : > : # not assume that it will be the same driver which is attached to the : > : # device. In particular, it must not assume that any values stored in : > : # the softc structure will be available for its attach method and any : > : # resources allocated during probe must be released and re-allocated : ^^^^^^^^^^^^^^^^^^^^ : > : # if the attach method is called. If a success code of zero is : > : # returned, the driver can assume that it will be the one attached. : > : > Notice it doesn't say that one can hold RESOURCES past the end of : > probe. Only that values set in the softc (which one should try to : : It says, about the case of negative return value. So I guess that : implies that in case if 0 is returned keeping resources is permitted. I guess I'm on the other side of the fence. It doesn't specifically allow it, so it must be forbidden. I've seen too much hardware docs that say one thing for condition A and one might assume that for A' that wouldn't be the case, but in fact the same condition applies for A' as well. : > avoid) aren't guaranteed to be there if the return value is < 0. It : > can only assume that it will be the driver that is attached. This : > comment is poorly worded anyway and should be changed to explicitly : > state that one shouldn't hold resources at the end of the probe : > routine. : : I suppose that "driver can assume that it will be the one attached" : means that the probe routine will not be called again for this : device, thet the resources won't change and that the attach routine : will be called eventually. Provided with all this keeping the resources : seems to be safe. But of course that's only my interpretation. Yes. I don't think it is safe, and I don't that we should document it as safe. : As far as I remember in prenewbus there were no "official resources". : Yes, I agree that keeping anything allocated when returning : from probe is a bad idea. In prenewbus, one couldn't malloc memory in probe that one didn't return right away. : > : Yes, that's what I said in the first quoted paraghaph: if probe : > : returns <0 (priority arbitration between multiple drivers in a class) : > : or >0 (error) then it must free the resources before exit and don't : > : assume that the contents of struct softc will be presevred between : > : probe and attach. But if probe returns 0 it may keep the resources. : > : > I'm still not sure that I agree. Unless I hear from the new-bus : > meister, I won't feel obligated to necessarily keep this condition in : > the NEWCARD code. I don't think I'll need to violate it, but I will : > if I have to because of how things are allocated in most device : > drivers right now. : : It's not like I'm saying that it MUST keep the resources from probe but : I suppose it's allowed to if it really wants. There might be some cases where it makes sense to do it, but those cases are going to be few and far between, imho. : > : Also some resources have problems with freeing them: for example, : > : if a piece of memory was allocated using bus_dmamem_alloc() with : > : lowaddr of BUS_SPACE_MAXADDR_24BIT then bus_dmamem_free() won't : > : really free it but just throw it away (I suppose contigfree() did not : > : exist when it was written). So it's better to keep these resources : > : between probe and attach if probe returns 0. : > : > No. Absolutely not. One should allocate them once only in the attach : > code. The probe code almost never needs to do a DMA to probe the : > device. Probes are supposed to be non-destructive (eg read only on : > the registers) if at all possible. One shouldn't try to allocate it : > there anyway for the same reason you say we should. If you are using : > it to see if the device exists, and it doesn't, then you can't free : > it. Sounds like a bad way to probe the hardware. The probe routine : : As far as I remember in prenewbus there were no "official resources". : Yes, I agree that keeping anything allocated when returning : from probe is a bad idea. In prenewbus, one couldn't malloc memory in probe that one didn't return right away. : > : Yes, that's what I said in the first quoted paraghaph: if probe : > : returns <0 (priority arbitration between multiple drivers in a class) : > : or >0 (error) then it must free the resources before exit and don't : > : assume that the contents of struct softc will be presevred between : > : probe and attach. But if probe returns 0 it may keep the resources. : > : > I'm still not sure that I agree. Unless I hear from the new-bus : > meister, I won't feel obligated to necessarily keep this condition in : > the NEWCARD code. I don't think I'll need to violate it, but I will : > if I have to because of how things are allocated in most device : > drivers right now. : : It's not like I'm saying that it MUST keep the resources from probe but : I suppose it's allowed to if it really wants. There might be some cases where it makes sense to do it, but those cases are going to be few and far between, imho. : What about the case when device exists but is broken/misconfigured ? : Suppose, someone got the port address right but the DMA channel wrong. : Well, of course, this more intrusive part of probe may as well be moved to : the attach routine. Two cases here. Either you read the DMA channel from the card and ignore what the user has said (which the aha driver does). Or you can't read it from the card, in which case you lose if the user lies to the driver. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 14:16: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3E8DB37B5F6 for ; Sat, 20 May 2000 14:16:05 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA17037; Sat, 20 May 2000 17:15:51 -0400 (EDT) Date: Sat, 20 May 2000 17:15:51 -0400 (EDT) From: "Matthew N. Dodd" To: Alexander Langer Cc: Sergey Babkin , hackers@FreeBSD.ORG Subject: Re: further question to bus_alloc_resource In-Reply-To: <20000520114607.A1832@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 May 2000, Alexander Langer wrote: > Yes. But what about the others. > /sys/dev/aha/aha_mca.c for example - it is part of module (aha), > allocs resources, but never releases them. Not on my system. You can't build a module that includes front ends for busses that may not be loaded. While some of the bus code for EISA/MCA busses could be loaded in a module there are other bits that must be compiled into the kernel. The current 'aha' module only includes support for the ISA bus front end. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 17:53:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 969C937B6DA; Sat, 20 May 2000 17:53:12 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.37]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id RAA91293; Sat, 20 May 2000 17:53:11 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id RAA00777; Sat, 20 May 2000 17:53:10 -0700 (PDT) Message-ID: <39273376.529E92F7@quack.kfu.com> Date: Sat, 20 May 2000 17:53:10 -0700 From: Nick Sayer X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Post-shutdown hook for UPS shutdown? References: <200005191821.LAA09144@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > The canonical way to do this is actually to shudown and reboot. > > In the _startup_ phase, while the root filesystem is still mounted > readonly, you check the UPS status. At this point, you have access to > the disk in a read-only fashion, and you can power-off (or have the UPS > die) at any time. By the way, for anyone interested, one way to achieve this if your UPS is too dumb to provide a "power good" signal is to take a 12vdc wall-wart and plug it into an _unprotected_ outlet. Connect this to a serial port, + to ground, - to DCD. Presto - that port's DCD signal now is a wall-power-good signal. You might optionally put a 1k resistor across the two pins to make sure that any filter caps bleed quickly off (a 12 ma load at 12 volts). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 18: 2:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 4CF3637B7EE for ; Sat, 20 May 2000 18:02:46 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: (from adsharma@localhost) by sharmas.dhs.org (8.9.3/8.9.3) id SAA04396 for freebsd-hackers@freebsd.org; Sat, 20 May 2000 18:02:29 -0700 Date: Sat, 20 May 2000 18:02:29 -0700 From: Arun Sharma To: FreeBSD Hackers Subject: truss(1) with support for fork(2) and friends Message-ID: <20000520180228.A4383@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just implemented the "-f" flag in truss, to trace across fork(2), rfork(2) and vfork(2) (the last one is not tested). The other day I observed that there were two truss processes when I was running "truss -f" on a Solaris box. I just thought it was a much simpler way of implementing "-f" than the strace (on Linux) way. So the implementation forks truss itself for each fork of the process being traced. It seems to work well for the most part, except for a race condition. The race condition happens because the child process could have gone away before the child truss could attach to it. Any suggestions to fix the race would be highly appreciated. I'm guilty of running indent against the source, before I did this work. So I can't generate a clean patch yet. But if I get good feedback on this work, I'll clean it up and produce a patch that can be commited. The tar ball is at: http://sharmas.dhs.org/~adsharma/projects/freebsd/truss.tar.gz This work could be useful to those of you thinking about implementing threads using rfork. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat May 20 22:25:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id CA03137B580 for ; Sat, 20 May 2000 22:25:48 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA21477; Sun, 21 May 2000 01:25:45 -0400 (EDT) Date: Sun, 21 May 2000 01:25:44 -0400 (EDT) From: "Matthew N. Dodd" To: Arun Sharma Cc: FreeBSD Hackers Subject: Re: truss(1) with support for fork(2) and friends In-Reply-To: <20000520180228.A4383@sharmas.dhs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 20 May 2000, Arun Sharma wrote: > I'm guilty of running indent against the source, before I did this > work. So I can't generate a clean patch yet. But if I get good > feedback on this work, I'll clean it up and produce a patch that can > be commited. Its pretty difficult to review this without being able to easily diff it against a CVS tree. You might want to restrict your changes the functional ones and worry about style issues later. Could you submit a diff instead of a tarball? Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message