From owner-freebsd-hackers Sun Feb 28 4:24: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id EFBDC151EE for ; Sun, 28 Feb 1999 04:24:01 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id NAA18557; Sun, 28 Feb 1999 13:22:08 +0100 (CET) Message-ID: <19990228132208.A18501@foobar.franken.de> Date: Sun, 28 Feb 1999 13:22:08 +0100 From: Harold Gutch To: Dennis , Greg Lehey Cc: hackers@FreeBSD.ORG Subject: Re: Cobalt blames linux for their security problems! References: <19990227211853.N7279@lemis.com> <199902271927.OAA26965@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902271927.OAA26965@etinc.com>; from Dennis on Sat, Feb 27, 1999 at 02:36:06PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 27, 1999 at 02:36:06PM -0500, Dennis wrote: > >>> There's a good idea.. use a free OS and then blame it for your problems.. > >They could just as well have run FreeBSD. The issue here is that they > >(or somebody else) are blaming the OS for their own mistakes. > > One problem with cobalt is that they arent running the latest kernels which > fix > the problem....it seems that THAT is their fault. > The latest Linux-kernels don't allow the shells to create their history-files ? Or do the latest kernels prevent httpds from reading from users' homedirectories ? I somehow fail to see what the kernel should have to do with the "Cobalt-bug". bye, Harold -- Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 5:38:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (Postfix) with ESMTP id 0D8871525D; Sun, 28 Feb 1999 05:37:30 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id OAA19840; Sun, 28 Feb 1999 14:37:12 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.3/8.6.9) id OAA09960; Sat, 27 Feb 1999 14:17:54 +0100 (CET) Date: Sat, 27 Feb 1999 14:17:54 +0100 From: Stefan Esser To: Dennis Cc: Ted Faber , hackers@freebsd.org, Stefan Esser Subject: Re: PCI Card Failures in 3.1 - fixed!!! Message-ID: <19990227141754.B4953@dialup124.mi.uni-koeln.de> Reply-To: se@freebsd.org Mail-Followup-To: Dennis , Ted Faber , hackers@freebsd.org References: <199902261614.LAA20285@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199902261614.LAA20285@etinc.com>; from Dennis on Fri, Feb 26, 1999 at 11:22:50AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-02-26 11:22 -0500, Dennis wrote: > Its seems that our 2.2 driver was not properly setting the > BM bit in the status/command register and Freebsd > 2.2. didnt seem to care, but 3.1 does. the card is > working fine now. Yes, sorry, that is a change between the PCI code in 2.x and 3.x ... It may be wrong to set those bits before calling the driver's attach() and it most probably is too late afterwords. In case you are bitten by the BM bit being set without your knowing, the error is hard to spot, so I decided to no longer set the enable bits by default ... Regards, STefan PS: I did not yet read most of this thread, or any other mail sent to me during the previous week, for lack of time ... Sorry for not having been able to reply sooner ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 5:38:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (Postfix) with ESMTP id CF1831525E; Sun, 28 Feb 1999 05:37:31 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Sisyphos.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id OAA19843; Sun, 28 Feb 1999 14:37:13 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.9.3/8.6.9) id OAA09948; Sat, 27 Feb 1999 14:13:23 +0100 (CET) Date: Sat, 27 Feb 1999 14:13:23 +0100 From: Stefan Esser To: Dennis Cc: Ted Faber , hackers@freebsd.org, Stefan Esser Subject: Re: PCI Card Failures in 3.1 - FYI Message-ID: <19990227141323.A4953@dialup124.mi.uni-koeln.de> Reply-To: se@freebsd.org Mail-Followup-To: Dennis , Ted Faber , hackers@freebsd.org References: <199902261546.KAA20180@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199902261546.KAA20180@etinc.com>; from Dennis on Fri, Feb 26, 1999 at 10:55:12AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-02-26 10:55 -0500, Dennis wrote: > Also, we dont call pci_map_port(), so I doubt that is the > problem. The mapping seems to work (when we map the > registers into memory we can read them and they have > the correct default values). the problem is that is cant > seem to dma to memory...its impossible to tell if it > can read however. You know about the bus-master enable bit in the command register ? There had been problems with cards doing bogus transfers if that feature was enabled by default, so the BIOS may leave it OFF. You are responsible for setting it in your driver, after the chip has been reset/initialzed and can be assumed under control ;-) The call to pci_map_port() exists for symmetry reasons. It does return the port address, but at least on the i386 does not have to setup any mappings. That's much different from pci_map_mem(), which establishes an VM mapping of the requested physical addresses and since there might be systems that provide only indirect access, to I/O ports, the same may be true for those architectures ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 6:39:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.128.1.71]) by hub.freebsd.org (Postfix) with ESMTP id B023214EB5 for ; Sun, 28 Feb 1999 06:39:16 -0800 (PST) (envelope-from housley@frenchknot.ne.mediaone.net) Received: from frenchknot.ne.mediaone.net (frenchknot.ne.mediaone.net [24.128.74.10]) by chmls06.mediaone.net (8.8.7/8.8.7) with ESMTP id JAA17402 for ; Sun, 28 Feb 1999 09:38:59 -0500 (EST) Received: from frenchknot.ne.mediaone.net (localhost [127.0.0.1]) by frenchknot.ne.mediaone.net (8.9.2/8.9.1) with ESMTP id JAA34093 for ; Sun, 28 Feb 1999 09:38:58 -0500 (EST) (envelope-from housley@frenchknot.ne.mediaone.net) Message-ID: <36D95501.57F7A4B7@frenchknot.ne.mediaone.net> Date: Sun, 28 Feb 1999 09:38:57 -0500 From: "James E. Housley" X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: Slice duplication quiestion Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to 6G IDE drives. I have mirrored the e and f slices with ccd. I want to copy the a slice so that under failure I can recover. I have tried dd if=/dev/rwd0s1a of=/dev/rwd2s1a This say the rwd2s1a is a read-only file-system. What am I doing wrong? Here are the disklabes. # /dev/rwd0c: type: ESDI disk: wd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 783 sectors/unit: 12594897 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 196608 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 12*) b: 155648 196608 swap # (Cyl. 12*- 21*) c: 12594897 0 unused 0 0 # (Cyl. 0 - 783*) e: 9437184 352256 4.2BSD 1024 8192 16 # (Cyl. 21*- 609*) f: 2805457 9789440 4.2BSD 1024 8192 16 # (Cyl. 609*- 783*) -- # /dev/rwd2c: type: ESDI disk: wd0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 783 sectors/unit: 12594897 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 196608 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 12*) b: 155648 196608 swap # (Cyl. 12*- 21*) c: 12594897 0 unused 0 0 # (Cyl. 0 - 783*) e: 9437184 352256 4.2BSD 1024 8192 16 # (Cyl. 21*- 609*) f: 2805457 9789440 4.2BSD 1024 8192 16 # (Cyl. 609*- 783*) I know I still need to do disklabel -B ...... to make it bootable. But if this were a copy the diskfix floppy would be enought to recover. Jim James E. Housley PGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: pagejim@notepage.com 7C F0 B5 BF 27 8B 92 FE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 8:53:26 1999 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 304901527F for ; Sun, 28 Feb 1999 08:53:23 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port23.netsvr1.cst.vastnet.net [207.252.73.23]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA00271; Sun, 28 Feb 1999 11:52:24 -0500 (EST) Message-Id: <199902281652.LAA00271@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 28 Feb 1999 11:59:45 -0500 To: Harold Gutch , Greg Lehey From: Dennis Subject: Re: Cobalt blames linux for their security problems! Cc: hackers@FreeBSD.ORG In-Reply-To: <19990228132208.A18501@foobar.franken.de> References: <199902271927.OAA26965@etinc.com> <19990227211853.N7279@lemis.com> <199902271927.OAA26965@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:22 PM 2/28/99 +0100, Harold Gutch wrote: >On Sat, Feb 27, 1999 at 02:36:06PM -0500, Dennis wrote: >> >>> There's a good idea.. use a free OS and then blame it for your problems.. >> >They could just as well have run FreeBSD. The issue here is that they >> >(or somebody else) are blaming the OS for their own mistakes. >> >> One problem with cobalt is that they arent running the latest kernels which >> fix >> the problem....it seems that THAT is their fault. >> >The latest Linux-kernels don't allow the shells to create their >history-files ? Or do the latest kernels prevent httpds from >reading from users' homedirectories ? > >I somehow fail to see what the kernel should have to do with the >"Cobalt-bug". I was referring to the security problems associated with the 2.0.33 kernel which the cobalt was running....again I accept my punishment for not finding the beginning of the thread. :-) Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 9:10:21 1999 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 D965715255 for ; Sun, 28 Feb 1999 09:10:19 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port23.netsvr1.cst.vastnet.net [207.252.73.23]) by etinc.com (8.8.8/8.6.9) with SMTP id MAA00353 for ; Sun, 28 Feb 1999 12:11:58 -0500 (EST) Message-Id: <199902281711.MAA00353@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 28 Feb 1999 12:19:18 -0500 To: hackers@freebsd.org From: Dennis Subject: CPU-type question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What does the "cpu" directive in the kernel config actually do? In the context of a binary driver, is there a potential problem if the binary was compiled on one type of cpu and that cpu type was not specified in the target machine's config? (that is that the driver was compiled on a i586 and the target machine only specified i686). I suppose this has some relevance to loadable drivers as well. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 10:17:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 286B214C91 for ; Sun, 28 Feb 1999 10:17:15 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id NAA13242; Sun, 28 Feb 1999 13:25:42 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199902281825.NAA13242@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Cobalt blames linux for their security problems! In-Reply-To: <199902272256.RAA27543@etinc.com> from Dennis at "Feb 27, 99 06:04:39 pm" To: dennis@etinc.com (Dennis) Date: Sun, 28 Feb 1999 13:25:42 -0500 (EST) Cc: chuckr@mat.net, hackers@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote, > I was generalizing more on the point that many seemed to be making that > you shouldnt blame a free OS for its fallacies that the specifics of the ^^^^ > cobalt situation. Sorry if I didnt make that clear. Exactly. I blame Mircosoft. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 10:25: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id C2B811527F; Sun, 28 Feb 1999 10:25:02 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id NAA13270; Sun, 28 Feb 1999 13:33:44 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199902281833.NAA13270@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Slice duplication quiestion In-Reply-To: <36D95501.57F7A4B7@frenchknot.ne.mediaone.net> from "James E. Housley" at "Feb 28, 99 09:38:57 am" To: housley@frenchknot.ne.mediaone.net (James E. Housley) Date: Sun, 28 Feb 1999 13:33:44 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (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 [This is more of a -questions topic. Replies directed there.] James E. Housley wrote, > I have to 6G IDE drives. I have mirrored the e and f slices with ccd. > I want to copy the a slice so that under failure I can recover. I have > tried dd if=/dev/rwd0s1a of=/dev/rwd2s1a This say the rwd2s1a is a > read-only file-system. What am I doing wrong? Here are the disklabes. [snip] > -- # /dev/rwd2c: > type: ESDI > disk: wd0s1 Huh? Why are these different? Anyway, why are you using 'dd?' IMHO, a dump-restore might be a better choice for the job, # mount /dev/wd2s1 /mnt # cd /mnt # dump -0af - /dev/wd0s1 | restore -rf - -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 12:32:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (ip55.houston2.tx.pub-ip.psi.net [38.11.201.55]) by hub.freebsd.org (Postfix) with ESMTP id EB9801529B for ; Sun, 28 Feb 1999 12:32:27 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.2/8.9.2) id OAA04787; Sun, 28 Feb 1999 14:33:05 -0600 (CST) (envelope-from chris) Date: Sun, 28 Feb 1999 14:33:04 -0600 From: Chris Costello To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Cobalt blames linux for their security problems! Message-ID: <19990228143304.A4692@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from Julian Elischer on Fri, Feb 26, 1999 at 07:26:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 26, 1999, Julian Elischer put this into my mailbox: > > > http://www.wired.com/news/news/technology/story/18109.html > > There's a good idea.. use a free OS and then blame it for your problems.. > > BTW did I tell you about the huge security holes we got from BSD (only > kidding) FreeBSD is a bad OS. This ASM code causes a memory fault! .globl _start .type start,@function _start: jmpl 0xffffffff and when I run it... (chris@holly) misc-> make as -o crash.o crash.s ld -nostdlib -o crash crash.o strip crash (chris@holly) misc-> ./crash Memory fault (core dumped) > > julian > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Powered by FreeBSD 3.1-STABLE. "The Power to Serve!" In the FreeBSD handbook, on a network routing diagram, next to "Windows 95 box," there is commented "(Do not admit to owning one.)" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 12:45:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D5B7152A8 for ; Sun, 28 Feb 1999 12:45:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA39096; Sun, 28 Feb 1999 12:45:26 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Feb 1999 12:45:26 -0800 (PST) From: Matthew Dillon Message-Id: <199902282045.MAA39096@apollo.backplane.com> To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: CPU-type question References: <199902281711.MAA00353@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :What does the "cpu" directive in the kernel config actually do? In the :context of :a binary driver, is there a potential problem if the binary was compiled on :one :type of cpu and that cpu type was not specified in the target machine's :config? :(that is that the driver was compiled on a i586 and the target machine only :specified i686). : :I suppose this has some relevance to loadable drivers as well. : :Dennis The cpu directive is used to compile in alternative cpu-specific code. It is also used to NOT compile in cpu-specific code. For example: cpu "I586_CPU" cpu "I686_CPU" In this case I'm telling the kernel to use Pentium and Pentium II specific features if those processors are detected. But, more noteably, by *NOT* including "I486_cpu" I am telling the kernel to not bother to compile in 386 or 486-specific features. This means that the above kernel will *NOT* run on a 386 or 486, but it will run more efficiently ( though not by much ) on a P or PII because it doesn't bother to check for 486 specific stuff. Or, at least, the kernel will be slightly smaller by not including the 386 or 486 specific stuff. -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 Feb 28 13:52:45 1999 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 14490152D8 for ; Sun, 28 Feb 1999 13:52:43 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id PAA05441; Sun, 28 Feb 1999 15:52:21 -0600 (CST) Date: Sun, 28 Feb 1999 15:52:21 -0600 From: Dan Nelson To: Matthew Dillon Cc: Dennis , hackers@FreeBSD.ORG Subject: Re: CPU-type question Message-ID: <19990228155221.A5190@dan.emsphone.com> References: <199902281711.MAA00353@etinc.com> <199902282045.MAA39096@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902282045.MAA39096@apollo.backplane.com>; from "Matthew Dillon" on Sun Feb 28 12:45:26 GMT 1999 X-OS: FreeBSD 3.1-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 28), Matthew Dillon said: > :What does the "cpu" directive in the kernel config actually do? In > :the context of a binary driver, is there a potential problem if the > :binary was compiled on one type of cpu and that cpu type was not > :specified in the target machine's config? (that is that the driver > :was compiled on a i586 and the target machine only specified i686). > : > :I suppose this has some relevance to loadable drivers as well. > > cpu "I586_CPU" > cpu "I686_CPU" > > This means that the above kernel will *NOT* run on a 386 or 486, > but it will run more efficiently ( though not by much ) on a P or > PII because it doesn't bother to check for 486 specific stuff. > Or, at least, the kernel will be slightly smaller by not > including the 386 or 486 specific stuff. There was a thread in -questions back on October arguing over how much faster your kernel was if you removed the unnecessary CPU types from your config file. Go to http://www.freebsd.org/search/search-mid.html and search for messageid <19981031141836.B2302@emsphone.com> for my response. The summary is that most of the CPU-specific code is in initcpu(), which enables CPU caches, optimized memcpys, and F00F workarounds depending on the detected CPU. So, Dennis, the CPU-types specified in the kernel shouldn't have any bearing on loadable modules, as long as you make sure your module works on all CPU types (i.e. don't put any #ifdef Ix86_CPU blocks in your lkm). -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 Sun Feb 28 15: 3:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.alpha.net.au (sydney.alpha.net.au [203.31.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 17B85152CD for ; Sun, 28 Feb 1999 15:03:16 -0800 (PST) (envelope-from danny@alpha.net.au) Received: from psych (p11-max28.syd.ihug.com.au [206.17.110.11]) by sydney.alpha.net.au (8.8.5/8.8.5) with SMTP id KAA03093; Mon, 1 Mar 1999 10:07:42 +1100 (EST) Message-Id: <3.0.32.19990301095612.006a1aec@pop.alpha.net.au> X-Sender: danny@pop.alpha.net.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 01 Mar 1999 09:56:24 +1100 To: Wes Peters , mjacob@feral.com From: Danny Subject: Setting up a quake server on FREEBSD???? -- need help :) Cc: Anton Marder , "'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 people, Hi I am interested in setting up a quake server hosted on my freebsd box. I know all about IP address stuff and what questions I need to ask my ISP. But where do I begin on Freebsd. reply to me danny@alpha.net.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 15:18:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5BD2B15316 for ; Sun, 28 Feb 1999 15:18:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id PAA11374; Sun, 28 Feb 1999 15:16:11 -0800 Date: Sun, 28 Feb 1999 15:16:11 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Danny Cc: Wes Peters , Anton Marder , "'hackers@FreeBSD.ORG'" Subject: Re: Setting up a quake server on FREEBSD???? -- need help :) In-Reply-To: <3.0.32.19990301095612.006a1aec@pop.alpha.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, why're you asking me (out of curiosity....) On Mon, 1 Mar 1999, Danny wrote: > Hi people, > > Hi I am interested in setting up a quake server hosted on my freebsd box. I > know all about IP address stuff and what questions I need to ask my ISP. > > But where do I begin on Freebsd. > > > reply to me > danny@alpha.net.au > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 15:19: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id 860B115335 for ; Sun, 28 Feb 1999 15:19:01 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA26934; Sun, 28 Feb 1999 16:18:43 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd026911; Sun Feb 28 16:18:40 1999 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id QAA21965; Sun, 28 Feb 1999 16:18:38 -0700 (MST) From: Terry Lambert Message-Id: <199902282318.QAA21965@usr07.primenet.com> Subject: Re: Fixing dlopen, ld.so, and upgrading the resolver To: jdp@polstra.com (John Polstra) Date: Sun, 28 Feb 1999 23:18:34 +0000 (GMT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199902270543.VAA05852@vashon.polstra.com> from "John Polstra" at Feb 26, 99 09:43:36 pm X-Mailer: ELM [version 2.4 PL25] 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 > > SVR4 handles this with a libdlopen, and the execution class loader > > premaps the ld.so into all images. The library stub is basically > > jump table data for the premapped ld.so. > > Terry keeps claiming that operating system X supports dlopen in static > programs, and I keep saying he's wrong. Rather than go through it > again, I'll just suggest that interested readers go to this URL: > > http://www.freebsd.org/cgi/search.cgi?words=dlopen+AND+static+AND+jdp&max=50&sort=date&source=freebsd-stable&source=freebsd-current&source=freebsd-hackers > > As you'll see, Terry has spewed this particular bit of misinformation > over and over since January, 1996. It's just as wrong today as it > was then. Solaris provides this functionality by causing the resulting binary to be linked shared against libdl.so, and static against all others. solaris%1 man libdl File Formats libdl(4) NAME libdl - the dynamic linking interface library SYNOPSIS cc [ flag ... ] file ... -ldl [ library ... ] DESCRIPTION Functions in this library provide direct access to the dynamic linking facilities. This library is implemented as a filter on the runtime linker (see ld.so.1(1)). SVR4, which is *not* Solaris, despite continual pointing at Solaris every time I broach this subject, can provide dlopen functionality by: 1) Using libelf to open the image to locate sections in ld.so 2) mapping ld.so sections 3) using the symbol section to locate ld.so entry points 4) providing stub functions to access ld.so function directly In the developement version of UnixWare 2.x that I used while at Novell/USG (the former USL), based on SVR4.2 ES/MP, this functionality was packaged into something called "libdlopen". I believe the author was Kurt Mahon, a kernel engineer at the Novell, Sandy site, and whose office was almost directly one floor below mine. Regardless, whether or not SVR4 can support this is irrelevent as to whether or not FreeBSD *should* support this. That FreeBSD *should* support dlopen in static binaries (with the addition of a library, of course) is the important point. We need to quit rat-holing on whether or not SVR4 supports it; I worked on an SVR4 that did, but the point is irrlevant. That the SVR4's that you are used to don't support this is not sufficient justification for FreeBSD to *not* support it. If I were to provide a libdlopen.a for use in static binaries, and which would fail in the absence of ld.so, would the code be committed? Alternately, if I were to provide a modified crt0.o for static linking that did the same thing as the one for dynamic linking, but did not fail if the .init section was empty in the absence of an ld.so (e.g., use the same code for static and dynamic), would *that* be committed? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 15:46:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (00-60-67-24-29-83.bconnected.net [209.53.17.55]) by hub.freebsd.org (Postfix) with ESMTP id 9CFB11532E for ; Sun, 28 Feb 1999 15:45:41 -0800 (PST) (envelope-from jwalther@localhost) Received: from jwalther by localhost with local-smtp (Exim 2.11 #1 (Debian)) id 10HFs0-00027A-00; Sun, 28 Feb 1999 15:43:36 -0800 Date: Sun, 28 Feb 1999 15:43:36 -0800 (PST) From: Jonathan Walther X-Sender: jwalther@localhost To: freebsd-hackers@freebsd.org Subject: Re: /dev/vesa usage In-Reply-To: <199902281857.NAA13353@cc942873-a.ewndsr1.nj.home.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 Sun, 28 Feb 1999, Crist J. Clark wrote in reply: > Jonathan Walther wrote to freebsd-questions: > > Does anyone know how to use /dev/vesa to flip into vesa modes, and just in > > general make VESA function calls? Hunting has revealed no documentation, no > > example source code. I apologize for not being god enough to understand the > > interface by looking at the lkm source. > > You might want to try this on -hackers. Some more specific questions > might aid your chances of some useful responses. Has anyone here been using /dev/vesa? I want to use it to switch banks and switch video modes. Jonathan Walther To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 17:10: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id ADA8A154A6 for ; Sun, 28 Feb 1999 17:09:33 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:J+QOIblHlrtMyhI8OUDr3Q9p3P1uwe5f@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id KAA26577; Mon, 1 Mar 1999 10:07:41 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA07570; Mon, 1 Mar 1999 10:10:42 +0900 (JST) Message-Id: <199903010110.KAA07570@zodiac.mech.utsunomiya-u.ac.jp> To: Jonathan Walther Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: /dev/vesa usage In-reply-to: Your message of "Sun, 28 Feb 1999 15:43:36 PST." References: Date: Mon, 01 Mar 1999 10:10:41 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sun, 28 Feb 1999, Crist J. Clark wrote in reply: >> Jonathan Walther wrote to freebsd-questions: >> > Does anyone know how to use /dev/vesa to flip into vesa modes, and just in >> > general make VESA function calls? Hunting has revealed no documentation, >no >> > example source code. I apologize for not being god enough to understand t >he >> > interface by looking at the lkm source. >> >> You might want to try this on -hackers. Some more specific questions >> might aid your chances of some useful responses. > >Has anyone here been using /dev/vesa? I want to use it to switch banks and >switch video modes. There is no such thing as /dev/vesa. If you want to set a video mode of your VESA-compliant VGA card, just issue ioctl to stdin. To change the current vide mode, use one of SW_XXX ioctls. ioctl(0, SW_XXXX, 0); To switch banks, use CONS_SETWINORG ioctl. ioctl(0, CONS_SETWINORG, offset); where `offset' is byte-offset from the beginning of the video memory. Then, the bank containing that byte position will appear in the bank window (usually 0xa0000). The window location and the bank size can be obtained by CONS_MODEINFO ioctl. See the following example. video_info_t mode_info; u_char *vid_mem; int vid_fd; int window; int bank_size; int offset; int w_offset; /* obtain mode information */ mode_info.vi_mode = M_VESA_CG1024x768; ioctl(0, CONS_MODEINFO, &mode_info); window = mode_info.vi_window; bank_size = mode_info.vi_window_size; /* set the new mode */ ioctl(0, SW_VESA_CG_1024x768); /* mmap the window */ vid_fd = open("/dev/mem", O_RDWR); vid_mem = mmap(0, bank_size, PROT_READ | PROT_WRITE, MAP_FILE, vid_fd, window); /* byte-offset from the beginning of the video memory */ offset = what_ever_offset; /* switch banks */ ioctl(0, CONS_SETWINORG, offset); /* write to that location */ w_offset = offset % bank_size; /* offset within the window */ vid_mem[w_offset] = what_ever_value; See /usr/include/machine/console.h for ioctls. Hope this will give you some info. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 17:12:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 7F28115416 for ; Sun, 28 Feb 1999 17:12:37 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA10975 for ; Sun, 28 Feb 1999 17:06:17 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdc10971; Mon Mar 1 01:06:16 1999 Date: Sun, 28 Feb 1999 17:06:12 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Subject: Mailing list archives presently unavailable? 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 someone working on them? I cannot search them as I was expecting... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 18:35:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E98CD15141; Sun, 28 Feb 1999 18:35:06 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA17586; Mon, 1 Mar 1999 13:04:49 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA17472; Mon, 1 Mar 1999 13:04:48 +1030 (CST) Message-ID: <19990301130448.D7279@lemis.com> Date: Mon, 1 Mar 1999 13:04:48 +1030 From: Greg Lehey To: "Li ChunAn (Nokia/Beijing)" Cc: FreeBSD Hackers Subject: Re: interrupt mechanism References: <199903010217.EAA27222@ns10.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903010217.EAA27222@ns10.nokia.com>; from Li ChunAn (Nokia/Beijing) on Mon, Mar 01, 1999 at 04:03:31AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -hackers] On Monday, 1 March 1999 at 4:03:31 +0200, Li ChunAn (Nokia/Beijing) wrote: > Hi > I am doing FreeBSD kernel programming. You should sign up with FreeBSD-hackers, then. FreeBSD-questions is for relatively simple questions about the system. > Would you like to give me some useful guides about kernel > programming? We'd love to. Unfortunately, there aren't as many as we would like. > By the way please tell me the mechanism of interrupt in FreeBSD. I'm not sure what documentation we have. See if you can find something in the FreeBSD handbook, but I fear that you won't find much there. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Feb 28 19:24:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [205.147.43.4]) by hub.freebsd.org (Postfix) with ESMTP id A96E815230 for ; Sun, 28 Feb 1999 19:24:11 -0800 (PST) (envelope-from dave@jetcafe.org) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.8/8.8.5) with ESMTP id TAA21121; Sun, 28 Feb 1999 19:23:38 -0800 (PST) Message-Id: <199903010323.TAA21121@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Quake2 and UDP recvspace Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 19:23:37 -0800 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > 0.01% > Is that acceptable packet loss? Well, yes. However most of that is at high player load. Anything I can do to help things out... > basically, 0.01% of the time the quake server doesn't recv() > fast enough and drops some packets. Hm. > i would suggest not worrying about it. This may be the ticket. :) ------ Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org Keep Usenet Free - http://www.jetcafe.org/~dave/usenet >>> The opinions expressed above are entirely my own <<< "Make no laws whatever concerning speech and, speech will be free; so soon as you make a declaration on paper that speech shall be free, you will have a hundred lawyers proving that "freedom does not mean abuse, nor liberty license;" and they will define and define freedom out of existence." - Voltarine de Cleyre (1866-1912) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 0:11:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 78A2A1530F for ; Mon, 1 Mar 1999 00:10:44 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA42400; Mon, 1 Mar 1999 00:10:27 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Mar 1999 00:10:27 -0800 (PST) From: Matthew Dillon Message-Id: <199903010810.AAA42400@apollo.backplane.com> To: Matthew Jacob , freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG New test patches are available for the getnewbuf() bug. And a couple more bugs found. Only the 'VFS_BIO Fixed to getnewbuf' patch is described in this email. http://www.backplane.com/FreeBSD4/ The patch needs more extensive testing. Bugs fixed: * getnewbuf() recursion reduced to 1 level. 5 levels is too deep for some VFS stacks and can overflow the supervisor stack. * A number of low-memory deadlock situations fixed by redoing the way buffers are written out and freed up. * numfreebuffer, numdirtybuffer accounting fixed - it was broken. Old Bugs not fixed: * I/O saturation is still a problem. There is no easy solution - even reverting to synchronous I/O doesn't help because the STEST script starts up 50 processes doing writes. This isn't a serious bug under normal operating conditions but it is annoying. New bugs found ( and not fixed ): * exec_map can only hold 16 exec'ing processes at once. It needs a counter and a sleep/wait. Sometimes when I ran Matt J's 'breakit' script, a background program would 'Abort trap' out instantly on startup because more then 16 were doing an exec at once. This can only occur in a low-memory or heavy-I/O situation. * Another bug in vfs.ffs.doreallocblks found. When writing large files ( running Matt J's STEST again ) with doreallocblks on and softupdates enabled, blocks associated with the file are apparently reallocated as the file is being written. When writing 50 4MB files ( 200MB ), over 350MB of disk space can be used during the test because softupdates is unable to get in and sync the bitmaps. If the test is paused, softupdates catches up. Otherwise you can run out of disk space. Also, if the filesystem runs out of space during the test, aka 'filesystem full', softupdates sometimes panics with the error: panic: softdep_setup_blkmapdep: found block * Possible hang with NFS ( still under test ). Sometimes NFS gets into loops during flushdirtybuffers() where it tries to rewrite the same block over and over again. I don't know why yet. -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 Mon Mar 1 1:48:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id CCE5E152C8 for ; Mon, 1 Mar 1999 01:46:44 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Mon, 1 Mar 1999 10:48:46 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097550@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: "'mjacob@feral.com'" , Josh MacDonald Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: SCSI Tape (HP SureStore T20) trouble Date: Mon, 1 Mar 1999 10:44:12 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Matthew Jacob [SMTP:mjacob@feral.com] > Sent: Saturday, February 27, 1999 3:02 AM > To: Josh MacDonald > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: SCSI Tape (HP SureStore T20) trouble > > On Fri, 26 Feb 1999, Josh MacDonald wrote: > > > I just installed a HP SureStore T20 SCSI tape drive on 3.0-RELEASE. > > My kernel is configured with the sa0 device, and dmesg reports: > > > > sa0 at ncr0 bus 0 target 5 lun 0 > > sa0: Removable Sequential Access SCSI2 device > > sa0: 3.300MB/s transfers > > Synchronous mode? How cheap.... [ML] Not necessarily. Might be a 3.0R sync negotiation bug, because I get the same rate for IBM DCASmumble hard disk hung off an aha1542CF. The disc and the card are fast SCSI devices, 10 MB/s should be possible (okay, I don't care much because ISA cannot trasfer more than 2-3 MB/s anyway :) /Marino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 2: 6: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id BBE23153A5 for ; Mon, 1 Mar 1999 02:03:42 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id KAA16829 Mon, 1 Mar 1999 10:03:22 GMT Message-ID: <36DA65E9.1CFB@cs.strath.ac.uk> Date: Mon, 01 Mar 1999 10:03:21 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Patch for APIC_IO SMP and PCMCIA controller 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 placed a re-worked patch to prevent SMP kernels panicing when you have a PCMCIA (PCCARD) controller in a SMP machine with APIC_IO. The problem was the redirection of IRQs when APIC_IO is enabled. I would like someone to review the patch, which makes use of the isa_apic_irq() function to map ISA IRQs to APIC IRQs. If I have no objections, I'll commit it. New versions of pcic.c and pccard.c can be found at ftp://telepresence.dmem.strath.ac.uk/pub/pcic These are modified 3.1-Release files. Bye Roger -- Roger Hardiman roger@cs.strath.ac.uk roger@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 Mar 1 3:51: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (Postfix) with ESMTP id 666DD14BE1 for ; Mon, 1 Mar 1999 03:50:59 -0800 (PST) (envelope-from jamesvv@ibm.net) Received: from javlaptop (slip139-92-194-23.por.uk.ibm.net [139.92.194.23]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id LAA68570 for ; Mon, 1 Mar 1999 11:50:41 GMT Reply-To: From: "James Van Vleet" To: Subject: FreeBSD as a serial mux? (Serial <-> FreeBSD <-> WAN <-> FreeBSD <-> Serial) Date: Mon, 1 Mar 1999 11:47:26 -0000 Message-ID: <000301be63d9$475a35e0$17c25c8b@javlaptop.dms-corp.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found this question a few times in my mailing list searches, but couldn't find an answer. If I have the wrong mailing list, please let me know. I have tried -questions with no luck. Is there a way to use FreeBSD as a serial mux? What I want to do is replace an existing leased line that is connected to serial multiplexers with a more modern WAN (TCP/IP) connection. The downside is that I still need to provide the serial muxing connection. So really what I need is a way to remotely run some terminals that are proprietary enough to not have emulation, as in serial in one server and serial out the other server. This seems useful enough that I would be surprised is someone has not already done it (without requiring some expensive terminal servers!) Any thoughts or suggestions are appreciated. -James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 3:57:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 5DECA15369 for ; Mon, 1 Mar 1999 03:56:58 -0800 (PST) (envelope-from edebruin@iname.com) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id MAA19516 for ; Mon, 1 Mar 1999 12:54:58 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1beta6) id kwa19514; Mon Mar 01 12:54:53 1999 Received: from borg.kryptokom.de (borg.Kryptokom.DE [192.168.6.132]) by Cirdan.KryptoKom.DE (8.8.8/8.8.8) with ESMTP id NAA09588 for ; Mon, 1 Mar 1999 13:00:07 +0100 Received: from iname.com (localhost [127.0.0.1]) by borg.kryptokom.de (8.8.8/8.8.8) with ESMTP id NAA07862 for ; Mon, 1 Mar 1999 13:02:35 +0100 (CET) (envelope-from edebruin@iname.com) Message-ID: <36DA81D8.A2D7CC57@iname.com> Date: Mon, 01 Mar 1999 13:02:33 +0100 From: eT Organization: KryptoKom GmbH X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-19980804-SNAP i386) X-Accept-Language: en MIME-Version: 1.0 To: Hackers FreeBSD Subject: config -g KERNEL Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG greets... i am doing some kernel debugging and tracing and have suddently received a message when the kernel boots about there being too many symbols and that there is some kindof BIOS limit? C:2048>1023 (bios limit) this happens just as the symbols are being loaded into memory after the boot: prompt. the kernel that i'm using has been config -g 'd. is there some way i can change the bios limit or reduce the number of symbols? regards -- Etienne de Bruin; eT@kryptokom.de; edebruin@iname.com visit eT on the web: http://listen.to/eT (last update: 18 Feb 1999) "draw me to my knees, so we can talk" - deliriou5, oh lead me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 4:48:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (Postfix) with ESMTP id 173CF14C91 for ; Mon, 1 Mar 1999 04:48:53 -0800 (PST) (envelope-from brandon@ice.cold.org) Received: (from brandon@localhost) by ice.cold.org (8.8.8/8.8.5) id FAA19053 for freebsd-hackers@freebsd.org; Mon, 1 Mar 1999 05:48:36 -0700 (MST) Date: Mon, 1 Mar 1999 05:48:36 -0700 From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: New rc/init system Message-ID: <19990301054835.A18962@ice.cold.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="TB36FDmn/VVEgNH/"; micalg=pgp-md5; protocol="application/pgp-signature" X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 2.2.8-RELEASE X-PGP-Public-Key: http://www.roguetrader.com/~brandon/brandon@roguetrader_com.pubkey Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii After the many responses to the earlier troll I made on the rc/init system in FreeBSD, I closeted myself away and started to hack on an idea, based on the many suggestions people made. The schema I have ended up with is called the Service Administration System (SAS). I have an informal specification for it available at: http://www.roguetrader.com/~brandon/sas/ Along with all of the prototype code I have. So what is it? SAS uses a heirarchy of services and dependancies to determine init order. It maintains a private registry of these services, along with packages that provide the services. The command utility can be used to start/stop services or packages. For example: sas down http sas down apache-1.3b5 Would get the same result (as only one package could be providing any single service). Furthermore, sas would tie into the HTTP dependancies (if there are any) and prompt for the proper actions to take if other services are dependant upon it. Services can also be gathered into collections which simply depend upon other services, thus creating a heirarchy with one (or more) tops, each defining different run-states. For the time being the registry only has one top (System). Furthermore, SAS could be expanded to cover High Availability and multiple Run Modes/States (see the docs for more details). SAS uses the existing /etc/rc.conf setup for configuration information on all services, with a few additions for managing values for each package. Automation scripts (in bourne-shell) are located in sbin/init.d, and the sas registry is located at etc/sas. Furthermore, a few add-ons are suggested for the package system, to help automate package/port registration with the SAS system, when they also require automation and/or provide a service. Current Status: * The SAS utility program (sas) is rudimantarily functional, including allowing for changes to each registry, and proper traversal of the tree for starting services. * Automation script API is defined and two automation scripts are defined (rc-fsck and a skeleton rc-test). Before I start chewing on a bunch of bourne scripts to actually implement a system startup, I figured I would toss the whole thing out to the masses for input. Is it worth pursuing, or just an academic fancy? I look forward to everybodies input. -Brandon Gillespie --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: WQiyDIfril5U7z7VRjNsIaeoHSsQtq+7 iQA/AwUBNtqMo0v5XoQiMgn6EQL4rgCfc1EPVppSupCCzMOc7/XoBgkE7XUAoLV0 b8tc+7A+F+s7vJk3FSezHmKa =IJUK -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 5:50:18 1999 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 41D0115374 for ; Mon, 1 Mar 1999 05:50:05 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id IAA51784; Mon, 1 Mar 1999 08:48:12 -0500 (EST) Date: Mon, 1 Mar 1999 08:48:12 -0500 (EST) From: Chuck Robey To: eT Cc: Hackers FreeBSD Subject: Re: config -g KERNEL In-Reply-To: <36DA81D8.A2D7CC57@iname.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, 1 Mar 1999, eT wrote: > greets... > > i am doing some kernel debugging and tracing and have suddently received a > message when the kernel boots about there being too many symbols and that > there is some kindof BIOS limit? > > C:2048>1023 (bios limit) This hasn't anything to do with symbols, I think. The most notorious bios limit at 1023 is the number of cylinders allowed for in specifying a bootable partition. If your bootable partition *begins* at a cylinder that's greater than 1023, the BIOS only has 10 bits to describe that, and it's going to fail to locate the boot cylinder you want. This hasn't anything to do with any os at all (FreeBSD being an OS, but this would affect Windows just the same way). Look at your partition layout, have you changed something? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 5:53:28 1999 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 A0AF814E33 for ; Mon, 1 Mar 1999 05:53:25 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.1a/8.8.8) id QAA26325; Mon, 1 Mar 1999 16:59:00 +0300 (MSK) (envelope-from babolo) Message-Id: <199903011359.QAA26325@aaz.links.ru> Subject: Re: FreeBSD as a serial mux? (Serial <-> FreeBSD <-> WAN <-> FreeBSD <-> Serial) In-Reply-To: <000301be63d9$475a35e0$17c25c8b@javlaptop.dms-corp.co.uk> from "James Van Vleet" at "Mar 1, 99 11:47:26 am" To: jamesvv@ibm.net Date: Mon, 1 Mar 1999 16:59:00 +0300 (MSK) Cc: freebsd-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 James Van Vleet writes: > I found this question a few times in my mailing list searches, but couldn't > find an answer. If I have the wrong mailing list, please let me know. I > have tried -questions with no luck. > > Is there a way to use FreeBSD as a serial mux? What I want to do is > replace an existing leased line that is connected to serial multiplexers > with a more modern WAN (TCP/IP) connection. The downside is that I still > need to provide the serial muxing connection. So really what I need is a > way to remotely run some terminals that are proprietary enough to not have > emulation, as in serial in one server and serial out the other server. This > seems useful enough that I would be surprised is someone has not already > done it (without requiring some expensive terminal servers!) Any thoughts or > suggestions are appreciated. it is only suggestions: on host 1: socket -qfls -p "kermit -l /dev/ttyd1 -b 38400 -c" 56789 on host2 socket -qf -p "kermit -l /dev/ttyd1 -b 38400 -c" host1 56789 where socket == /usr/ports/sysutils/socket/ kermit == /usr/ports/comms/kermit/ 56789 any (almoust) port -- @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 Mon Mar 1 6:46:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 7365915377 for ; Mon, 1 Mar 1999 06:45:53 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id JAA16752; Mon, 1 Mar 1999 09:45:38 -0500 (EST) Date: Mon, 1 Mar 1999 09:45:37 -0500 (EST) From: Alfred Perlstein To: James Van Vleet Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as a serial mux? (Serial <-> FreeBSD <-> WAN <-> FreeBSD <-> Serial) In-Reply-To: <000301be63d9$475a35e0$17c25c8b@javlaptop.dms-corp.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 Mon, 1 Mar 1999, James Van Vleet wrote: > > I found this question a few times in my mailing list searches, but couldn't > find an answer. If I have the wrong mailing list, please let me know. I > have tried -questions with no luck. > > Is there a way to use FreeBSD as a serial mux? What I want to do is > replace an existing leased line that is connected to serial multiplexers > with a more modern WAN (TCP/IP) connection. The downside is that I still > need to provide the serial muxing connection. So really what I need is a > way to remotely run some terminals that are proprietary enough to not have > emulation, as in serial in one server and serial out the other server. This > seems useful enough that I would be surprised is someone has not already > done it (without requiring some expensive terminal servers!) Any thoughts or > suggestions are appreciated. Whistle Communications has a set of patches for freebsd that allow this to be done in kernel, the interface to the code doesn't seem too bad either. You can pick it up at: ftp://ftp.whistle.com/pub/archie/netgraph/index.html I'm looking into using it for round robin based web load balancing, the reason that it's so appealing is that it is _in kernel_ meaning fast, fast, fast, and very modular. -Alfred > > -James > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 6:50:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 0EA0D15028 for ; Mon, 1 Mar 1999 06:50:41 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp102.dialup.st.keio.ac.jp [131.113.27.102]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id XAA14283 for ; Mon, 1 Mar 1999 23:50:23 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.2/3.7W) id VAA05046; Mon, 1 Mar 1999 21:09:44 +0900 (JST) Message-Id: <199903011209.VAA05046@lavender.yy.cs.keio.ac.jp> To: hackers@FreeBSD.ORG Subject: Does some one create busmaster code for Opti FineStarPlus(82C700) ? X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 01 Mar 1999 21:09:44 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I want to use Busmaster mode with my NOTE-PC and 3.1-RELEASE. I have NOTE-PC which has: NEC MobioNX PCI Chipset: Opti FineStarPlus(82C700) HDD: IBM-DDLA-21620 (PIO Mode-4, Multiword DMA Mode-2) I read Datasheet of FineStar Plus. It support Bus Master IDE HDD. But if I test with flags 0x2000 or 0xa0ff with wdc0, I can't use it. At change root device to wd0s1a, hung-up and light HDD access LED. I think that BIOS is not set some timing of IDE Controller and it is needed to some code of opti_dmainit and opti_status in /sys/pci/ide_pci.c. I read CVS log of ide_pci.c. >It runs on my P6 natoma board with two Maxtor drives, and also >on a Fujitsu machine I have at work with an Opti chipset and >a Quantum drive. Does someone imprement BusMaster capable code for Opti Chip? Thank you MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 6:52:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id D9EC515383 for ; Mon, 1 Mar 1999 06:51:17 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id HAA03605; Mon, 1 Mar 1999 07:50:49 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36DAA948.690A1354@softweyr.com> Date: Mon, 01 Mar 1999 07:50:48 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: chris@calldei.com Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: Cobalt blames linux for their security problems! References: <19990228143304.A4692@holly.dyndns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > > On Fri, Feb 26, 1999, Julian Elischer put this into my mailbox: > > > > > > http://www.wired.com/news/news/technology/story/18109.html > > > > There's a good idea.. use a free OS and then blame it for your problems.. > > > > BTW did I tell you about the huge security holes we got from BSD (only > > kidding) > > > FreeBSD is a bad OS. This ASM code causes a memory fault! > This simple C program: int main() { int *badboy = 0; *badboy = 3; return *badboy; } when run on FreeBSD produces: wes$ ./a.out Segmentation fault (core dumped) It runs fine on DOS, so FreeBSD must be wrong. Can you send me free hardware to fix it? Alternatively, you should upgrade all InterJets in the field to MS-DOS 2.11 so this program won't crash anymore. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 1 7: 6:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (Postfix) with ESMTP id 0F8CB15367 for ; Mon, 1 Mar 1999 07:06:13 -0800 (PST) (envelope-from adrian@ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id KAA29513; Mon, 1 Mar 1999 10:06:33 -0500 (EST) (envelope-from adrian@ubergeeks.com) Date: Mon, 1 Mar 1999 10:06:33 -0500 (EST) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: Cobalt blames linux for their security problems! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 26 Feb 1999, Julian Elischer wrote: > http://www.wired.com/news/news/technology/story/18109.html > > There's a good idea.. use a free OS and then blame it for your problems.. Security configuration and unauthorized external access asside, it was bad practice for the admins to let plain text passwords make it into their history files. I've mistyped passwords at the wrong time, but I immediately set my history file to /dev/nuall as well. Operator error seems to be the most fundamental problem here. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7: 7:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 8E20315373 for ; Mon, 1 Mar 1999 07:06:55 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA17543; Mon, 1 Mar 1999 10:03:29 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA12936; Mon, 1 Mar 1999 10:01:55 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA24830; Mon, 1 Mar 1999 10:01:55 -0500 (EST) Date: Mon, 1 Mar 1999 10:01:55 -0500 (EST) From: Thomas David Rivers Message-Id: <199903011501.KAA24830@lakes.dignus.com> To: brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG Subject: Re: New rc/init system In-Reply-To: <19990301054835.A18962@ice.cold.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an observaction... You might want to pick a different name... "SAS" could be easily confused with the well-known program named "SAS". - Dave Rivers - (former SAS employee) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:13:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (Postfix) with ESMTP id 69A4F153D5 for ; Mon, 1 Mar 1999 07:12:56 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id JAA32093 for ; Mon, 1 Mar 1999 09:13:34 -0600 (CST) Date: Mon, 1 Mar 1999 09:13:33 -0600 (CST) From: "Jasper O'Malley" To: freebsd-hackers@freebsd.org Subject: tn3270 -> tn5250 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone ever taken a look at what it would take to beat on the tn3270 source to turn it into tn5250? I'm following one tn5250 effort that seems to be making decent progress, but it's rather Linux-centric (the name of the project is linux5250). Seems to me that if the tn3270 source could be modified with a minimum of effort, it might make a decent project; one that my programming skills aren't quite up to, unfortunately, but a good one nonetheless. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:17:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 83DCF150BD for ; Mon, 1 Mar 1999 07:17:07 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id IAA03655; Mon, 1 Mar 1999 08:16:32 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36DAAF4F.B558D7CF@softweyr.com> Date: Mon, 01 Mar 1999 08:16:31 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Andy Doran , "'hackers@FreeBSD.ORG'" Subject: Re: FreeBSD for RISC References: <36D70B99.4A2DAF4E@psn.ie> <199902272026.NAA47747@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: > > In message <36D70B99.4A2DAF4E@psn.ie> Andy Doran writes: > : Was a MIPS port ever started (I'm thinking of DECstations here)? > > Yes. Work continues on it even. And is anxiously awaited by others. ;^) The NEC/Packard Bell outlet has refurbished MobilePro 450s for $99, if you have beta testers who need machines, Warner. I have a back- door contact there if you have enough to consider doing a group buy, say 10 or more machines. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 1 7:21:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id D889715004 for ; Mon, 1 Mar 1999 07:21:42 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA20632; Mon, 1 Mar 1999 10:21:05 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA13027; Mon, 1 Mar 1999 10:20:48 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA25107; Mon, 1 Mar 1999 10:20:48 -0500 (EST) Date: Mon, 1 Mar 1999 10:20:48 -0500 (EST) From: Thomas David Rivers Message-Id: <199903011520.KAA25107@lakes.dignus.com> To: brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG, rivers@dignus.com Subject: Re: New rc/init system In-Reply-To: <199903011501.KAA24830@lakes.dignus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just an observaction... ^^^^^^^^^^^^ That should read "observation" - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:22:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A6B7215004 for ; Mon, 1 Mar 1999 07:22:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id HAA14287; Mon, 1 Mar 1999 07:21:53 -0800 Date: Mon, 1 Mar 1999 07:21:52 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: <199903010810.AAA42400@apollo.backplane.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 Most Very Excellent- I'll give it all a try. One comment: > > Old Bugs not fixed: > > * I/O saturation is still a problem. There is no easy solution - > even reverting to synchronous I/O doesn't help because the STEST > script starts up 50 processes doing writes. This isn't a serious > bug under normal operating conditions but it is annoying. > This is a less likely real-world scenario- you don't usually start up multiple things all at once which then suck down the entire buffer cache. Would the problem manifest itself under increasing load? One thing I'm mulling doing is to try and move forward musbus or it's equivalent- eons ago during the initial Solaris development we used musbus and it's ilk to generate stepwise increasing load to find where the kernel broke. Similarily, it may not be the instantaneous load of 50 or 100 writers springing into action that drags a system to unusable, but the slowly increasing load. I'll ponder a couple of ways to make this all a test package at the very least- I don't know about you, but I find this stuff helpful. Oh- I take it from your found but not fixed mail that doreallocblks should set to zero still.... Thanks again, Matt- -matt (the lower case matt). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:24:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 67FB7153C0 for ; Mon, 1 Mar 1999 07:23:42 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 01 Mar 1999 15:23:30 +0000 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id FSG3LD5B; Mon, 1 Mar 1999 15:17:31 -0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10HUZz-0000L2-00; Mon, 1 Mar 1999 15:25:59 +0000 To: "Jasper O'Malley" Cc: freebsd-hackers@freebsd.org Subject: Re: tn3270 -> tn5250 X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: "Jasper O'Malley"'s message of "Mon, 01 Mar 1999 09:13:33 CST" Date: Mon, 01 Mar 1999 15:25:59 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 March 1999, "Jasper O'Malley" proclaimed: > Has anyone ever taken a look at what it would take to beat on the tn3270 > source to turn it into tn5250? I'm following one tn5250 effort that seems > to be making decent progress, but it's rather Linux-centric (the name of > the project is linux5250). Seems to me that if the tn3270 source could be > modified with a minimum of effort, it might make a decent project; one > that my programming skills aren't quite up to, unfortunately, but a good > one nonetheless. The existing tn5250 isn't too bad; it's certainly workable although not terribly flexible. It doesn't have any problems compiling on FreeBSD, although it does require that you have the ncurses port installed (why do we have such an ancient version of ncurses in our tree)? I haven't gotten around to submitting my port yet, because when I tried last time, the ncurses port it depended on was broken. I'll give it another go later this afternoon hopefully, now that you've jogged my memory. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator Free your mind -- http://www.opensource.org/ -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:32:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id E8D601539D for ; Mon, 1 Mar 1999 07:32:32 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id IAA03696; Mon, 1 Mar 1999 08:30:34 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36DAB299.7496F2E1@softweyr.com> Date: Mon, 01 Mar 1999 08:30:33 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Thomas David Rivers Cc: brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG Subject: Re: New rc/init system References: <199903011501.KAA24830@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > Just an observaction... > > You might want to pick a different name... "SAS" could be easily confused > with the well-known program named "SAS". > > - Dave Rivers - > (former SAS employee) Or an airline named SAS, or for some of us, an elite Australian military strike force. (British, too, I think. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@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 Mar 1 7:38:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id E788B15213 for ; Mon, 1 Mar 1999 07:38:43 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA23917; Mon, 1 Mar 1999 10:38:15 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA00342; Mon, 1 Mar 1999 10:38:09 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA03724; Mon, 1 Mar 1999 10:38:11 -0500 (EST) Date: Mon, 1 Mar 1999 10:38:11 -0500 (EST) From: Thomas David Rivers Message-Id: <199903011538.KAA03724@lakes.dignus.com> To: rivers@dignus.com, wes@softweyr.com Subject: Re: New rc/init system Cc: brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <36DAB299.7496F2E1@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Thomas David Rivers wrote: > > > > Just an observaction... > > > > You might want to pick a different name... "SAS" could be easily confused > > with the well-known program named "SAS". > > > > - Dave Rivers - > > (former SAS employee) > > Or an airline named SAS, or for some of us, an elite Australian > military strike force. (British, too, I think. ;^) > Well - the difference here, I think, is that the Airline, and strike forces don't also have software for sale. The SAS corporation could easily view another piece of software with the name SAS as trademark infringement... - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:53:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id EA325152FB for ; Mon, 1 Mar 1999 07:53:27 -0800 (PST) (envelope-from pixel@excalibur.oceanis.net) Received: (from pixel@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id PAA02432; Mon, 1 Mar 1999 15:52:35 GMT From: Emmanuel DELOGET Message-Id: <199903011552.PAA02432@excalibur.oceanis.net> Subject: Re: New rc/init system In-Reply-To: <199903011538.KAA03724@lakes.dignus.com> from Thomas David Rivers at "Mar 1, 1999 10:38:11 am" To: rivers@dignus.com (Thomas David Rivers) Date: Mon, 1 Mar 1999 16:52:34 +0100 (MET) Cc: brandon@roguetrader.com, hackers@FreeBSD.ORG (FreeBSD Hackers Mail List) 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 As the well known Thomas David Rivers said... ->> ->> Thomas David Rivers wrote: ->> > ->> > Just an observaction... ->> > ->> > You might want to pick a different name... "SAS" could be easily confused ->> > with the well-known program named "SAS". ->> > ->> > - Dave Rivers - ->> > (former SAS employee) ->> ->> Or an airline named SAS, or for some of us, an elite Australian ->> military strike force. (British, too, I think. ;^) ->> -> -> Well - the difference here, I think, is that the Airline, and strike ->forces don't also have software for sale. -> -> The SAS corporation could easily view another piece of software with ->the name SAS as trademark infringement... Or a french stupid book :) What do you think of BAS (stands for Basic Administration System) or SWAS (System Wide Administration Scheme). I don't think that SWAS is another strike force :) -> - Dave R. - -- ____________________________________________________________________ Emmanuel DELOGET [pixel] pixel@{dotcom.fr,epita.fr} ---- DotCom SA -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 7:57:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 710A4150BD for ; Mon, 1 Mar 1999 07:57:09 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA27000; Mon, 1 Mar 1999 10:55:42 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id KAA00389; Mon, 1 Mar 1999 10:54:55 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id KAA05346; Mon, 1 Mar 1999 10:54:55 -0500 (EST) Date: Mon, 1 Mar 1999 10:54:55 -0500 (EST) From: Thomas David Rivers Message-Id: <199903011554.KAA05346@lakes.dignus.com> To: pixel@DotCom.FR, rivers@dignus.com Subject: Re: New rc/init system Cc: brandon@roguetrader.com, hackers@FreeBSD.ORG In-Reply-To: <199903011552.PAA02432@excalibur.oceanis.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As the well known Thomas David Rivers said... > ->> > ->> Thomas David Rivers wrote: > ->> > > ->> > Just an observaction... > ->> > > ->> > You might want to pick a different name... "SAS" could be easily confused > ->> > with the well-known program named "SAS". > ->> > > ->> > - Dave Rivers - > ->> > (former SAS employee) > ->> > ->> Or an airline named SAS, or for some of us, an elite Australian > ->> military strike force. (British, too, I think. ;^) > ->> > -> > -> Well - the difference here, I think, is that the Airline, and strike > ->forces don't also have software for sale. > -> > -> The SAS corporation could easily view another piece of software with > ->the name SAS as trademark infringement... > > Or a french stupid book :) > What do you think of BAS (stands for Basic Administration System) > or SWAS (System Wide Administration Scheme). I don't think that > SWAS is another strike force :) > > -> - Dave R. - > I don't know about the other names... they all seem fine to me... - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 8: 6:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (Postfix) with ESMTP id BDC4615382 for ; Mon, 1 Mar 1999 08:04:23 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id KAA00112; Mon, 1 Mar 1999 10:04:54 -0600 (CST) Date: Mon, 1 Mar 1999 10:04:54 -0600 (CST) From: "Jasper O'Malley" To: Dom Mitchell Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tn3270 -> tn5250 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 Mon, 1 Mar 1999, Dom Mitchell wrote: > The existing tn5250 isn't too bad; it's certainly workable although not > terribly flexible. My main problem is the lack of a keyboard configuration file. Being a Linux project, the authors suggest the use of the loadkeys utility, for which there is no non-X equivalent in FreeBSD. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 8:15:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (Postfix) with ESMTP id 3B2D215571 for ; Mon, 1 Mar 1999 08:15:15 -0800 (PST) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.3/8.9.3) id IAA00569; Mon, 1 Mar 1999 08:14:12 -0800 (PST) Message-Id: <199903011614.IAA00569@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: Thomas David Rivers Cc: wes@softweyr.com, brandon@roguetrader.com, freebsd-hackers@FreeBSD.ORG Subject: Re: New rc/init system In-Reply-To: Your message of "Mon, 01 Mar 1999 10:38:11 EST." <199903011538.KAA03724@lakes.dignus.com> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_329830660P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 01 Mar 1999 08:14:12 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_329830660P Content-Type: text/plain; charset=us-ascii If memory serves me right, Thomas David Rivers wrote: > > > > Thomas David Rivers wrote: > > > > > > Just an observaction... > > > > > > You might want to pick a different name... "SAS" could be easily confused > > > with the well-known program named "SAS". > > > > > > - Dave Rivers - > > > (former SAS employee) > > > > Or an airline named SAS, or for some of us, an elite Australian > > military strike force. (British, too, I think. ;^) > > > > Well - the difference here, I think, is that the Airline, and strike > forces don't also have software for sale. It's not inconceivable that the strike force could have software for sale...the United States Marine Corps has a customized version of Doom that they use for training, so.... :-) Aack...off-topic post...*bad*, *bad*, *bad* Bruce! Bruce. --==_Exmh_329830660P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNtq806jOOi0j7CY9AQEehgP/QDoYIXBmn1jgKCx/9wn7oClgMPSzUXc8 MGYiFWdf7L34fMCHkNCL+rd9DfIukffHMHaZj+1wTd/f7iwJEQiVmtl/96YSldbi CpdZkKimI1Sbq5R652+fYADLhAczKrsWRq5XCdyvUw1ehhFBheqgBUMwNfOsVyGh lWtdRpZfqvQ= =Pog4 -----END PGP MESSAGE----- --==_Exmh_329830660P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 8:22:43 1999 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 079EB15460 for ; Mon, 1 Mar 1999 08:22:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id QAA27187; Mon, 1 Mar 1999 16:22:10 GMT 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 JAA07453; Mon, 1 Mar 1999 09:22:59 -0700 (MST) Message-Id: <199903011622.JAA07453@harmony.village.org> To: Wes Peters Subject: Re: FreeBSD for RISC Cc: "'hackers@FreeBSD.ORG'" In-reply-to: Your message of "Mon, 01 Mar 1999 08:16:31 MST." <36DAAF4F.B558D7CF@softweyr.com> References: <36DAAF4F.B558D7CF@softweyr.com> <36D70B99.4A2DAF4E@psn.ie> <199902272026.NAA47747@harmony.village.org> Date: Mon, 01 Mar 1999 09:22:59 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <36DAAF4F.B558D7CF@softweyr.com> Wes Peters writes: : The NEC/Packard Bell outlet has refurbished MobilePro 450s for $99, : if you have beta testers who need machines, Warner. I have a back- : door contact there if you have enough to consider doing a group buy, : say 10 or more machines. I have gotten them on ebay for that price range. Too bad I dropped both of mine and shattered their screens. I have doubts about 4M being enough memory to do anything beyond proof of concept. However, the chipset in them is capable of memory mapping up to 16M of PCMCIA card space, which would effectively give them 20M of main memory (but some interesting swap issues). I am in contact with someone who is actively working on a linload-like loader that I helped design. It will boot kernels <= 256k now! Too bad my MobilePros are busted, or I'd focus my attention in those areas. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 8:51: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id 07D1315416 for ; Mon, 1 Mar 1999 08:51:07 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from tsdev.inktomi.com (tsdev.inktomi.com [209.1.32.119]) by mercury.inktomi.com (8.9.1a/8.9.1) with SMTP id IAA28623; Mon, 1 Mar 1999 08:51:00 -0800 (PST) Received: by tsdev.inktomi.com (SMI-8.6/SMI-SVR4) id IAA22026; Mon, 1 Mar 1999 08:50:50 -0800 Message-ID: <19990301085050.A21935@tsdev.inktomi.com> Date: Mon, 1 Mar 1999 08:50:50 -0800 From: John Plevyak To: Terry Lambert , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: flock and kernel threads References: <19990223214744.A24606@proxydev.inktomi.com> <199902272027.NAA13546@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902272027.NAA13546@usr09.primenet.com>; from Terry Lambert on Sat, Feb 27, 1999 at 08:27:13PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem is a but in the semantics of file locking in FreeBSD because in FreeBSD kernel threads are more 'processes' than 'thread' (i.e. they have their own PID). File locking in threaded programs should work independently of which thread locked the file and which thread closes the file. It should not require registering any cleanup functions. This is how it works on Solaris, IRIX and Digital Unix, and I believe how it should work on FreeBSD. john On Sat, Feb 27, 1999 at 08:27:13PM +0000, Terry Lambert wrote: > > I believe there may be a problem with lockfiles (flock) and > > kernel threads. The problem is demonstrated by the enclosed > > program, which if run twice will fail the second time. > > > > The problem seems to be that termination via signal of > > the non-main thread (non-leader) does not (always) result > > in a call to closef and hence a call to lf_clearlock. > > > > Suggestions, comments welcome. > > This happens because fd's are scoped to the process (it's an > index intpo the per process open file table) and not to the > thread that opened them. Consider that if they were scoped > to the thread that did the open, you would not be able to do > useful things like handing incoming socket connections off to > worker threads. > > To resolve this, you either need to register a cleanup mechanism > that knows about per thread state: > > man pthread_cleanup_push > > This is less than ideal, since it means that your threading > architecture in your program is not very SMP scalable, by its > design. > > In general, thread use should be limited as much as possible > to a "work to do model", with any persistent state that will > survive across transactions scoped globally in a per "session" > state structure. > > Refeerences to the literature available on request (or you can > scan the -current and -hackers list archives). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 9:12:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id BCE4715414 for ; Mon, 1 Mar 1999 09:11:22 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from tsdev.inktomi.com (tsdev.inktomi.com [209.1.32.119]) by mercury.inktomi.com (8.9.1a/8.9.1) with SMTP id JAA00403; Mon, 1 Mar 1999 09:11:15 -0800 (PST) Received: by tsdev.inktomi.com (SMI-8.6/SMI-SVR4) id JAA22097; Mon, 1 Mar 1999 09:11:05 -0800 Message-ID: <19990301091105.B21935@tsdev.inktomi.com> Date: Mon, 1 Mar 1999 09:11:05 -0800 From: John Plevyak To: Terry Lambert , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads References: <19990224165840.A19033@proxydev.inktomi.com> <199902272043.NAA14007@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902272043.NAA14007@usr09.primenet.com>; from Terry Lambert on Sat, Feb 27, 1999 at 08:43:33PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 27, 1999 at 08:43:33PM +0000, Terry Lambert wrote: > > Ok, I found the problem with using kernel threads and fcntl( .. F_SETLK ..). > > The issue is two fold. > > > > 1. the locks are keyed off pid, and if the first thread to exit and close > > them is not the one that took out the lock the close will occur without > > the lock being removed. > > Probably the correct way to deal with this is to put the locks into > seperate collision domains for the keying. > > A very simple way to do this would be to take the NFS server locking > kernel patches from www.freebsd.org/~terry/, and then make rpid the > same as pid for unthreaded process, the same as the thread ID for > threaded processes, and then make the rpid value significant for > both hash bucket selection and locally asserted locks. > > This would result in the locks locking against each other. This is a good idea, and one I considered for the patch. Two problems with this: 1. the obvious choice of rpid is p_leader->p_pid. However, it is possible for the leader to terminate a short time (time to service a 'kill') before the peers. Depending on how overloaded the machine, NFS troubles etc, I might worry about PID recycling. 2. It requires a more substantial change to the locking and a modification of the proc struct. The reason is that currently file locking uses the proc pointer as the 'id' or uniqueness token. I wanted to see if something simpler could be done. Alternatively, if one can ensure that the p_leader does not die before the peers, then one can preserve the locking code and refraim from changing the proc strucure since one can simply pass p->p_leader down to the locking code. Since for unthreaded programs p == p->p_leader this yields very simple code for both cases. Moreover, this change enables other such threading problems to be fixed because logically 'process-type' state can be stored in p->p_leader->foo and logically 'thread-type' state can be stored in p->foo. (this is the change I chose) > > > > 2. the P_ADVLOCK flag is set in p_flags on a per processes basis, so > > we don't even check to see if locks need to be removed if the > > closing (struct proc*) is not the locking (struct proc*). > > POSIX is very explicit, that the first close on a file within a single > process results in the locks being deasserted. > > I think that your patches fail to address this issue, since in reality, > I believe that you want to treat each thread as if it were a seperate > process for the purpose of specifying POSIX close semantics. The patch does in fact handle this case. The first closing thread with pass p->p_leader into the VOP_ADVLOCK and cause the lock to be released. In the current system, only if the original thread which obtained the lock was the first to close it would the lock be released. > > The patches also have the coeslescence problem that made me seperate > the VOP_ADVLOCK code into an assert-veto/affirm-coelesce, instead > of what they do now. > > Basically, the problem is that when you assert a byte range lock on > a file (e.g., a read lock), and an overlapping lock is granted to > another thread in your process (e.g. a read lock with some overlap), > and one or the other of the locks (but not both) are deasserted, then > the overlapping region is no longer read locked for the thread that > did not release it's lock. > > In effect, the locks cast "shadows" onto a linear contention space > for each file, and shadows with the same indices are coelesced. > > The purpose in dealing with this for NFS server locking is that a > single process in user space proxies the locks for a large number > of clients, and locks from one client machine that overlap another > lock from the same client machine results in a condition similar > to multiple threads within the same process asserting locks, and > expecting them to be enforced as if they weren't in the same > contention domain (it happens to clean up VFS advisory locking on > union FS stacking at the same time, but that's just a nice side > effect). > I understand the problem for NFS locking, but for threaded programs it would seem that lock shadowing would be the desired behavior The program is logically one process, and the lock ranges are shared state, not thread-specific state. > > > As a general comment on your original problem, the correct way to > handle signals (according to the pthreads model) is to disable > disnals in all threads but one, which is designated as the signal > handling thread. > > One problem here is that FreeBSD kernel threads using rfork get > different PID's, so the signal handling will never work correctly > anyway. > > For user space threads and the Linux crap, the signal handling > should be possible, if you follow the disallow-all-but-one-thread > rule. I considered that also. There are a few problems with this: 1. some signals cannot be blocked. In particular, if the non-locking thread is 'KILL'ed, then the lock will never be released in the current code. 2. the abort(3) code explicitly unblocks the calling threads signal handler so that strategy will not work for asserts, aborts. 3. signals are used for other purposes, some of which are not amenable to the 'disallow-all-but-on-thread' technique. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message john -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 9:21:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (Postfix) with ESMTP id 3CB5C155DA for ; Mon, 1 Mar 1999 09:21:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA19958; Mon, 1 Mar 1999 09:12:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903011712.JAA19958@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: jamesvv@ibm.net Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD as a serial mux? (Serial <-> FreeBSD <-> WAN <-> FreeBSD <-> Serial) In-reply-to: Your message of "Mon, 01 Mar 1999 11:47:26 GMT." <000301be63d9$475a35e0$17c25c8b@javlaptop.dms-corp.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Mar 1999 09:12:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a way to use FreeBSD as a serial mux? What I want to do is > replace an existing leased line that is connected to serial multiplexers > with a more modern WAN (TCP/IP) connection. The downside is that I still > need to provide the serial muxing connection. So really what I need is a > way to remotely run some terminals that are proprietary enough to not have > emulation, as in serial in one server and serial out the other server. This > seems useful enough that I would be surprised is someone has not already > done it (without requiring some expensive terminal servers!) Any thoughts or > suggestions are appreciated. A serial mux application is so trivial that anyone setting something like this likely to just sit down and write the damn thing. If it's beyond your reach, I'm sure that there are plenty of people that would be happy to roll such an animal for you. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 1 11:10:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id 6F1E815399 for ; Mon, 1 Mar 1999 11:10:16 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id OAA01263 for hackers@freebsd.org; Mon, 1 Mar 1999 14:34:19 -0500 (EST) (envelope-from dervish) Date: Mon, 1 Mar 1999 14:34:18 -0500 From: Natty Rebel To: hackers@freebsd.org Subject: Problems with teac cdroms + symbios based adapters? Message-ID: <19990301143418.A1225@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all. I've recently purchased a Teac 516s 16x cdrom along with a Kouwell 801V10B Fast SCSI adapter (Symbios 53C810a chipset). My problem is that the cdrom drive fails to recognise any cd's placed in it. Here are some results using camcontrol: # camcontrol tur -n cd -v (pass0:ncr0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass0:ncr0:0:3:0): NOT READY asc:3a,0 (pass0:ncr0:0:3:0): Medium not present Unit is not ready the above is the main message that i see (i.e. 'medium not present' and 'unit is not ready'). what's funny is that i can send the eject command and the tray will eject. i've called teac tech support and the rep said there were some known issues with cam and symbios based chipsets. is this correct? the mailing list archives are off-line at the moment so i could not check if this is indeed an issue. here are some other outputs: # camcontrol devlist -v scbus-1 on xpt1116471295 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on ncr0 bus 0: at scbus0 target 3 lun 0 (pass0,cd0) < > at scbus0 target -1 lun -1 () # camcontrol inquiry -n cd Removable CD-ROM SCSI-2 device Serial Number 10.0MB/s transfers (10.0MHz, offset 8) # camcontrol reset -n cd Reset of bus 0 was successful # camcontrol periphlist -n cd pass0: generation: 6 index: 1 status: MORE cd0: generation: 6 index: 2 status: LAST any help is appreciated ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 11:35:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 8FC8015421 for ; Mon, 1 Mar 1999 11:35:39 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA23618; Mon, 1 Mar 1999 14:34:50 -0500 (EST) (envelope-from luoqi) Date: Mon, 1 Mar 1999 14:34:50 -0500 (EST) From: Luoqi Chen Message-Id: <199903011934.OAA23618@lor.watermarkgroup.com> To: dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG, mjacob@feral.com Subject: Re: Panic in FFS/4.0 as of yesterday - update Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > New bugs found ( and not fixed ): > > * exec_map can only hold 16 exec'ing processes at once. It needs a > counter and a sleep/wait. > > Sometimes when I ran Matt J's 'breakit' script, a background program > would 'Abort trap' out instantly on startup because more then 16 > were doing an exec at once. This can only occur in a low-memory > or heavy-I/O situation. > There could also be potential deadlocks when all 16 processes hold a lot in exec_map and then all of them try to allocate more from exec_map (for loading elf interpreter). The simplest solution is to use a separate map. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 11:43:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 3220B15394 for ; Mon, 1 Mar 1999 11:42:21 -0800 (PST) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id OAA11573; Mon, 1 Mar 1999 14:42:00 -0500 (EST) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.8.8/8.8.7) with ESMTP id OAA28487; Mon, 1 Mar 1999 14:41:58 -0500 (EST) (envelope-from ath@stiegl.niksun.com) Message-Id: <199903011941.OAA28487@stiegl.niksun.com> From: Andrew Heybey To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Advice wanted on tracking down bug (or hw problem?) in 3.1R In-reply-to: Your message of Fri, 26 Feb 1999 12:22:25 -0800. <199902262022.MAA09175@dingo.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Mon, 01 Mar 1999 14:41:58 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >>On Fri, 26 Feb 1999 09:52:33 -0800, Mike Smith said: >> >> I have just submitted PR kern/10243, but I thought I would ask >> >> for some advice on hackers as well. >> >> >> >> The bug is that under certain loads, read(2) can return corrupted >> >> data (ie data that are not in the file on disk). The instances I >> >> have seen are relatively small amounts (8-64 bytes) of corrupt >> >> data at the end of a 4k page. The corrupt data is from a file >> >> previously read or another position in the current file. I have >> >> also seen this problem in 3.0-RELEASE but not in 2.2.8-RELEASE. >> >> mike> Can you look at the corrupt data and see if you can identify >> mike> it? In particular, look for objects that look like IP >> mike> addresses, MAC addresses, pointers into kernel space, ascii >> mike> text, etc. This is usually the best way to work out where the >> mike> data is coming from. >> >> The data is always (in every instance that I have examined) from some >> other part of the file currently being read or some other file in my >> set of test files. How my test setup works is that I have 30 50MB >> files. The files are filled with sequential integers (counting over >> the entire 1.5GB). My test program reads from the files (in order, >> starting over at file #0 when it reaches file #29) and compares what >> read(2) returns to what should be there (based on file number and file >> offset). >> >> One other possible clue: This morning I hooked my disks up to the >> regular Ultra SCSI (40MB/s) port of the 7890 controller rather than >> the Ultra/2 (80MB/s) port and I haven't seen the bug yet. I am not >> 100% positive since I have only run it for a few hours so far, but >> before I could almost always make the bug happen withing 10-15 >> minutes. > >Could you try bzero'ing your buffers before every read? This sniffs >very much like short transfers rather than sniping... > More information: I ran a test where I stopped all activity on the system as soon as the first test program observed the bug. That is, I stopped the other programs reading the disk and turned off the packet generator that had been raising the network load. Then I read the file with the garbage data again and it still contains the same garbage at the same offset. If I do enough disk I/O to flush it from the cache and then read it again it is fine. This behavior seems to confirm that it isn't a race condition (because then I would expect the subsequent read of the file to return the correct data). Rather, it seems that the buffer cache has become corrupted because of a short DMA. Any other suggestions? Would this more likely be a driver bug or a hw bug? It still seems to be the case that I cannot duplicate the bug with the disk connected to the 40MB/sec SCSI bus. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 11:43:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id CE4A415394; Mon, 1 Mar 1999 11:43:57 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ISI.EDU (vex-e.isi.edu [128.9.160.240]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id LAA11285; Mon, 1 Mar 1999 11:43:40 -0800 (PST) Message-Id: <199903011943.LAA11285@boreas.isi.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: se@freebsd.org Cc: Dennis , hackers@freebsd.org Subject: Re: PCI Card Failures in 3.1 - FYI In-Reply-To: Your message of "Sat, 27 Feb 1999 14:13:23 +0100." <19990227141323.A4953@dialup124.mi.uni-koeln.de> X-Url: http://www.isi.edu/~faber Date: Mon, 01 Mar 1999 11:43:39 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Stefan Esser wrote: >On 1999-02-26 10:55 -0500, Dennis wrote: >> Also, we dont call pci_map_port(), so I doubt that is the >> problem. The mapping seems to work (when we map the >> registers into memory we can read them and they have >> the correct default values). the problem is that is cant >> seem to dma to memory...its impossible to tell if it >> can read however. > >You know about the bus-master enable bit in the command register ? >There had been problems with cards doing bogus transfers if that >feature was enabled by default, so the BIOS may leave it OFF. > >You are responsible for setting it in your driver, after the chip >has been reset/initialzed and can be assumed under control ;-) That was my problem, too. I don't know why I understood when you said it, and not when Dennis said it. I'll forward patches to Paul. Thanks! - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Key: http://www.isi.edu/~faber/pubkey.asc -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNtrt6ob4eisfQ5rpAQEHsAP+Odc+aqK7aoY8h8+7CeLNPMIoF//0EBvd +Cwr6K2ciSCikkrWoQgTOBlRf4taD+IMkrIfALYM2lA591rPNlYxcyX+yd8eK+aP Trpifw2PSs4NSZyUtUY2GtP5FtJ+AMh67zUw/fXaZQG4NuGMCeFOF+qfIX583W73 qXxqUqqhd1M= =94h9 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 11:45:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (Postfix) with ESMTP id 2C7EF150BD for ; Mon, 1 Mar 1999 11:45:31 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA16503; Mon, 1 Mar 1999 11:40:46 -0800 (PST) Message-Id: <199903011940.LAA16503@implode.root.com> To: Luoqi Chen Cc: dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG, mjacob@feral.com Subject: Re: Panic in FFS/4.0 as of yesterday - update In-reply-to: Your message of "Mon, 01 Mar 1999 14:34:50 EST." <199903011934.OAA23618@lor.watermarkgroup.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Mar 1999 11:40:46 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> New bugs found ( and not fixed ): >> >> * exec_map can only hold 16 exec'ing processes at once. It needs a >> counter and a sleep/wait. >> >> Sometimes when I ran Matt J's 'breakit' script, a background program >> would 'Abort trap' out instantly on startup because more then 16 >> were doing an exec at once. This can only occur in a low-memory >> or heavy-I/O situation. >> >There could also be potential deadlocks when all 16 processes hold a lot in >exec_map and then all of them try to allocate more from exec_map (for loading >elf interpreter). The simplest solution is to use a separate map. Allocations from exec_map are done using kmem_alloc_wait() and frees are done using kmem_free_wakeup, so they already sleep/wakeup as appropriate when the map is full. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 11:56:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A44D0151AA for ; Mon, 1 Mar 1999 11:56:26 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id LAA12308; Mon, 1 Mar 1999 11:55:31 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id LAA07176; Mon, 1 Mar 1999 11:55:30 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id MAA22032; Mon, 1 Mar 1999 12:54:41 -0700 Message-ID: <36DAF08E.6C0028D5@softweyr.com> Date: Mon, 01 Mar 1999 12:54:54 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: jamesvv@ibm.net, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD as a serial mux? (Serial <-> FreeBSD <-> WAN <-> FreeBSD <-> Serial) References: <199903011712.JAA19958@dingo.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: > > > Is there a way to use FreeBSD as a serial mux? What I want to do is > > replace an existing leased line that is connected to serial multiplexers > > with a more modern WAN (TCP/IP) connection. The downside is that I still > > need to provide the serial muxing connection. So really what I need is a > > way to remotely run some terminals that are proprietary enough to not have > > emulation, as in serial in one server and serial out the other server. This > > seems useful enough that I would be surprised is someone has not already > > done it (without requiring some expensive terminal servers!) Any thoughts or > > suggestions are appreciated. > > A serial mux application is so trivial that anyone setting something > like this likely to just sit down and write the damn thing. If it's > beyond your reach, I'm sure that there are plenty of people that would > be happy to roll such an animal for you. Depending on your application, you may not even need any programming. If you're talking about connecting a bunch of terminals on one side to a bunch of serial lines on the other side of the WAN connection, you can probably do this without custom programming, using standard FreeBSD applications. Please describe to me your problem in detail, and I'll see if I can make some recommendations. This may not be of interest to -hackers, please think about this before including the list in your reply. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@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 Mar 1 12:18:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 045C715422 for ; Mon, 1 Mar 1999 12:18:46 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA47735; Mon, 1 Mar 1999 12:18:21 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Mar 1999 12:18:21 -0800 (PST) From: Matthew Dillon Message-Id: <199903012018.MAA47735@apollo.backplane.com> To: David Greenman Cc: Luoqi Chen , freebsd-hackers@FreeBSD.ORG, mjacob@feral.com Subject: Re: Panic in FFS/4.0 as of yesterday - update References: <199903011940.LAA16503@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :>> New bugs found ( and not fixed ): :>> :>> * exec_map can only hold 16 exec'ing processes at once. It needs a :>> counter and a sleep/wait. :>> :>> Sometimes when I ran Matt J's 'breakit' script, a background program :>> would 'Abort trap' out instantly on startup because more then 16 :>> were doing an exec at once. This can only occur in a low-memory :>> or heavy-I/O situation. :>> :>There could also be potential deadlocks when all 16 processes hold a lot in :>exec_map and then all of them try to allocate more from exec_map (for loading :>elf interpreter). The simplest solution is to use a separate map. : : Allocations from exec_map are done using kmem_alloc_wait() and frees are :done using kmem_free_wakeup, so they already sleep/wakeup as appropriate when :the map is full. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project Hmm. Something is going on. Four times now I have gotten 'Abort trap' on some of the processes Matt J's STEST script starts -- it starts up 50 processes at once. The abort occurs prior to main() being called. There is NOTHING in the code that can generate this trap othe then the exec code ... and only if the exec fails after the vmspace is destroyed. So the question is: What is causing exec to fail? -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 Mon Mar 1 12:25:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id E31CE15409 for ; Mon, 1 Mar 1999 12:24:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00514; Mon, 1 Mar 1999 12:19:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903012019.MAA00514@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: eT Cc: Hackers FreeBSD Subject: Re: config -g KERNEL In-reply-to: Your message of "Mon, 01 Mar 1999 13:02:33 +0100." <36DA81D8.A2D7CC57@iname.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Mar 1999 12:19:01 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > greets... > > i am doing some kernel debugging and tracing and have suddently received a > message when the kernel boots about there being too many symbols and that > there is some kindof BIOS limit? > > C:2048>1023 (bios limit) Parts of the root filesystem (and hence the kernel) extend beyond the 1024 cylinder mark, and cannot be read using the BIOS. Your disk layout sucks, and you need to shrink/move your root filesystem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 1 13:11:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id D37391536F for ; Mon, 1 Mar 1999 13:11:12 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id PAA79042; Mon, 1 Mar 1999 15:10:46 -0600 (CST) (envelope-from dick) Date: Mon, 1 Mar 1999 15:10:46 -0600 From: "Richard Seaman, Jr." To: John Plevyak Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads Message-ID: <19990301151046.G1046@tar.com> References: <19990224165840.A19033@proxydev.inktomi.com> <199902272043.NAA14007@usr09.primenet.com> <19990301091105.B21935@tsdev.inktomi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990301091105.B21935@tsdev.inktomi.com>; from John Plevyak on Mon, Mar 01, 1999 at 09:11:05AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 01, 1999 at 09:11:05AM -0800, John Plevyak wrote: > On Sat, Feb 27, 1999 at 08:43:33PM +0000, Terry Lambert wrote: > > As a general comment on your original problem, the correct way to > > handle signals (according to the pthreads model) is to disable > > disnals in all threads but one, which is designated as the signal > > handling thread. This is recommended by many people, and in IMO is best. But, its not a requirement for POSIX pthreads, and POSIX compliant pthreads needs to deal with signals which are not handled this way. > > One problem here is that FreeBSD kernel threads using rfork get > > different PID's, so the signal handling will never work correctly > > anyway. Correct. Not only is signal handling not correct, neither is priority handling, not wait handling, nor any other syscalls that reference pids. POSIX pthreads says that threads should all have the same pid as the process that spawns them. The FreeBSD kernel needs some changes to handle POSIX compliant kernel pthreads. > > For user space threads and the Linux crap, the signal handling > > should be possible, if you follow the disallow-all-but-one-thread > > rule. > > I considered that also. There are a few problems with this: > > 1. some signals cannot be blocked. In particular, if the non-locking > thread is 'KILL'ed, then the lock will never be released in the > current code. > > 2. the abort(3) code explicitly unblocks the calling threads signal > handler so that strategy will not work for asserts, aborts. > > 3. signals are used for other purposes, some of which are not > amenable to the 'disallow-all-but-on-thread' technique. AKAIK, here's an abbreviated version of what POSIX says about signal handling: 1) Sigaction is shared by all threads. 2) Sigmasks are per thread. 3) Signal delivery depends. A synchronous signal generated by an exception is delivered to the thread that generated it. A signal sent to a thread by pthread_kill is delivered to the target thread. A signal sent to the process as a whole is delivered to one thread of the process that has not masked the signal (or if all threads have masked it, it is held pending until some thread unblocks it). The shared signal handling code added to the kernel in Dec/Jan (is this the "Linux crap" Terry refers to?) implement 1) and 2) above. Complete compliance with 3) requires more changes. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 13:45:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id 9B02C15440 for ; Mon, 1 Mar 1999 13:45:19 -0800 (PST) (envelope-from mark.hannon@stockholm.mail.telia.com) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by maile.telia.com (8.8.5/8.8.8) with ESMTP id WAA12594 for ; Mon, 1 Mar 1999 22:44:56 +0100 (CET) Received: from doorway.home.lan (t3o1p15.telia.com [195.67.240.135]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id WAA05033 for ; Mon, 1 Mar 1999 22:44:48 +0100 (CET) Received: from stockholm.mail.telia.com (putte.home.lan [192.168.255.2]) by doorway.home.lan (8.9.2/8.8.7) with ESMTP id WAA57019 for ; Mon, 1 Mar 1999 22:19:24 +0100 (CET) (envelope-from mark.hannon@stockholm.mail.telia.com) Message-ID: <36DB0457.86DE5EC8@stockholm.mail.telia.com> Date: Mon, 01 Mar 1999 22:19:19 +0100 From: Mark Hannon X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Announce: Use leafnode to handle mailing lists 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 just uploaded some modifications to leafnode to allow it to handle mailing lists. I have been using this modification to handle the freebsd mailing lists with some success. Enjoy. /mark http://w1.874.telia.com/~u87405149/mail2leafnode.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 14:30:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id D92DE15474 for ; Mon, 1 Mar 1999 14:28:48 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA235817288; Mon, 1 Mar 1999 17:28:08 -0500 Date: Mon, 1 Mar 1999 17:28:08 -0500 (EST) From: Bill Fumerola To: Jasper O'Malley Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tn3270 -> tn5250 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 Mon, 1 Mar 1999, Jasper O'Malley wrote: > Has anyone ever taken a look at what it would take to beat on the tn3270 > source to turn it into tn5250? I'm following one tn5250 effort that seems > to be making decent progress, but it's rather Linux-centric (the name of > the project is linux5250). Seems to me that if the tn3270 source could be > modified with a minimum of effort, it might make a decent project; one > that my programming skills aren't quite up to, unfortunately, but a good > one nonetheless. See ports/5626. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Mon Mar 1 15:34:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sydney.alpha.net.au (sydney.alpha.net.au [203.31.171.20]) by hub.freebsd.org (Postfix) with ESMTP id 2D112154A6 for ; Mon, 1 Mar 1999 15:34:22 -0800 (PST) (envelope-from danny@alpha.net.au) Received: from psych (p4-max11.syd.ihug.com.au [206.17.105.196]) by sydney.alpha.net.au (8.8.5/8.8.5) with SMTP id KAA01193; Tue, 2 Mar 1999 10:40:32 +1100 (EST) Message-Id: <3.0.32.19990302103635.006aff54@pop.alpha.net.au> X-Sender: danny@pop.alpha.net.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 02 Mar 1999 10:37:01 +1100 To: Terry Lambert , jdp@polstra.com (John Polstra) From: Danny Subject: Re: Fixing dlopen, ld.so, and upgrading the resolver Cc: 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 Can u tell me why everytiime I do a shutdown NOW it keeps asking me for the /bin/sh Then when I type in the commmand again and did a reboot it was the thing was not properly dismounted. Do u know a way around that problem.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 16: 7:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 835051544A for ; Mon, 1 Mar 1999 16:06:40 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA22048; Tue, 2 Mar 1999 10:36:21 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA02373; Tue, 2 Mar 1999 10:36:20 +1030 (CST) Message-ID: <19990302103619.J441@lemis.com> Date: Tue, 2 Mar 1999 10:36:19 +1030 From: Greg Lehey To: Mike Smith , eT Cc: Hackers FreeBSD Subject: Re: config -g KERNEL References: <36DA81D8.A2D7CC57@iname.com> <199903012019.MAA00514@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903012019.MAA00514@dingo.cdrom.com>; from Mike Smith on Mon, Mar 01, 1999 at 12:19:01PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 1 March 1999 at 12:19:01 -0800, Mike Smith wrote: >> greets... >> >> i am doing some kernel debugging and tracing and have suddently received a >> message when the kernel boots about there being too many symbols and that >> there is some kindof BIOS limit? >> >> C:2048>1023 (bios limit) > > Parts of the root filesystem (and hence the kernel) extend beyond the > 1024 cylinder mark, and cannot be read using the BIOS. Your disk > layout sucks, and you need to shrink/move your root filesystem. Specifically, since it obviously worked before, I'd guess that your root file system is very large, but starts before the 1024 cylinder limit. The kernel normally gets installed at the beginning of the file system, but since you installed a debug kernel, there was not enough space there, and parts of it ended up (way) beyond the 1024 cylinder limit. You might find that if you strip the kernel, you can still boot. You can still keep a copy of the kernel with symbols for remote gdb debugging, if that's what you want to do. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 16:31:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 9694814C2D for ; Mon, 1 Mar 1999 16:31:26 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id TAA04581; Mon, 1 Mar 1999 19:31:12 -0500 (EST) Date: Mon, 1 Mar 1999 19:31:10 -0500 (EST) From: Alfred Perlstein To: Danny Cc: hackers@FreeBSD.ORG Subject: shutdown problem In-Reply-To: <3.0.32.19990302103635.006aff54@pop.alpha.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Danny wrote: > Hi > > Can u tell me why everytiime I do a shutdown NOW it keeps asking me for the > /bin/sh > > Then when I type in the commmand again and did a reboot it was the thing > was not properly dismounted. > > Do u know a way around that problem.. err... shutdown -h now the -h is for halt, check the man pages, they can be helpful. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 18:25:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (Postfix) with ESMTP id 2F82714C41 for ; Mon, 1 Mar 1999 18:25:34 -0800 (PST) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id UAA10461; Mon, 1 Mar 1999 20:26:05 -0600 (CST) Date: Mon, 1 Mar 1999 20:26:05 -0600 (CST) From: "Jasper O'Malley" To: Bill Fumerola Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tn3270 -> tn5250 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 Mon, 1 Mar 1999, Bill Fumerola wrote: > See ports/5626. 'ldap' port eats all available CPU time? If you meant ports/7680 - "New port of tn5250", that's the linux5250 port I mentioned in my post. Perhaps I should clarify my intent...I'm curious what it would take to modify the Berkeley tn3270 to process a 5250 datastream, rather than the 3270 datastream. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 19:13: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 2B98C15400 for ; Mon, 1 Mar 1999 19:13:04 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA18425; Mon, 1 Mar 1999 20:12:46 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd018386; Mon Mar 1 20:12:37 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id UAA21878; Mon, 1 Mar 1999 20:12:35 -0700 (MST) From: Terry Lambert Message-Id: <199903020312.UAA21878@usr01.primenet.com> Subject: Re: lockf and kernel threads To: jplevyak@inktomi.com (John Plevyak) Date: Tue, 2 Mar 1999 03:12:35 +0000 (GMT) Cc: tlambert@primenet.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <19990301091105.B21935@tsdev.inktomi.com> from "John Plevyak" at Mar 1, 99 09:11:05 am X-Mailer: ELM [version 2.4 PL25] 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 > Alternatively, if one can ensure that the p_leader does not > die before the peers, then one can preserve the locking code > and refraim from changing the proc strucure since one can > simply pass p->p_leader down to the locking code. Since for > unthreaded programs p == p->p_leader this yields very simple > code for both cases. I think you can do this by recursing on the peers in the middle of handling the kill before you pass it to the trampoline (then it's too late). > Moreover, this change enables other such threading problems to be fixed > because logically 'process-type' state can be stored in > p->p_leader->foo and logically 'thread-type' state can be stored > in p->foo. > > (this is the change I chose) Really, the thread specific data needs to be seperated from the proc struct; that is, the p->p_leader->foo should become meaningless. Basically, the litany on this is "everything that can differ between threads". > > POSIX is very explicit, that the first close on a file within a single > > process results in the locks being deasserted. > > > > I think that your patches fail to address this issue, since in reality, > > I believe that you want to treat each thread as if it were a seperate > > process for the purpose of specifying POSIX close semantics. > > The patch does in fact handle this case. The first closing > thread with pass p->p_leader into the VOP_ADVLOCK and cause the lock > to be released. > > In the current system, only if the original thread which obtained > the lock was the first to close it would the lock be released. I'm confused about the semantics you desire, I think. My opinion would be that the POSIX close/unlock coupling is highly undesirable in general, and that you would want the threads to compete as if they were processes for the semantics. I think this would depends on the lock scoping? E.g.: PTHREAD_PROCESS_PRIVATE PTHREAD_PROCESS_SHARED ? > I understand the problem for NFS locking, but for threaded programs > it would seem that lock shadowing would be the desired behavior > The program is logically one process, and the lock ranges are > shared state, not thread-specific state. I think the POSIX semantics, since they predate threads, can be reasonably interpreted either way. However, the use that you described seemed to want to scope file descriptors to a particular thread, such that a thread exit would result in the close. I don't think this is reasonable (the descriptor space is shared between all threads in a process). The only way to reasonably achieve such scoping is pthread_cleanup_push(). > I considered that also. There are a few problems with this: > > 1. some signals cannot be blocked. In particular, if the non-locking > thread is 'KILL'ed, then the lock will never be released in the > current code. A process that is sent a signal whose default (or uninterceptable) action is to cause the process to exit, stop, or continue *MUST* apply that signal to all threads within the process. If the other threads continue running, then you have delivered the signal not to the process (which is where it's scoped!), but to a particular thread. This is bad. > 2. the abort(3) code explicitly unblocks the calling threads signal > handler so that strategy will not work for asserts, aborts. > > 3. signals are used for other purposes, some of which are not > amenable to the 'disallow-all-but-on-thread' technique. This is a bug. I believe that this was done as a workaround for some other random signal handling change. We actually had to back the change out here, locally, when we were pursuing an ACAP implementation. From my reading of the GO SOLO 2 CDROM: signal/sighold/sigignore/sigpause/sigrelse/sigset ... Use of any of these functions is unspecified in a multi-threaded process. [ ... ] sigaction ... At the time of generation, a determination is made whether the signal has been generated for the process or for a specific thread within the process. Signals which are generated by some action attributable to a particular thread, such as a hardware fault <>, are generated for the thread that caused the signal to be generated. Signals that are generated in association with a process ID or group ID or an asynchronous event such as terminal activity are generated for the process. ... When a signal is delivered to a thread, if the action of that signal specifies termination, stop, or continue, the entire process will be terminated, stopped, or continued, respectively. The whole thing, in its entirety, is a *huge* condemnation of the current FreeBSD implementation, including the process group notification of SIGHUP not being delivered to some group members, and instead read returning 0/-1 for ttys. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 19:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id E3BD514C87 for ; Mon, 1 Mar 1999 19:31:02 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id UAA25163; Mon, 1 Mar 1999 20:30:45 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp03.primenet.com, id smtpd025140; Mon Mar 1 20:30:41 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id UAA22888; Mon, 1 Mar 1999 20:30:39 -0700 (MST) From: Terry Lambert Message-Id: <199903020330.UAA22888@usr01.primenet.com> Subject: Re: lockf and kernel threads To: dick@tar.com (Richard Seaman, Jr.) Date: Tue, 2 Mar 1999 03:30:39 +0000 (GMT) Cc: jplevyak@inktomi.com, tlambert@primenet.com, hackers@FreeBSD.ORG In-Reply-To: <19990301151046.G1046@tar.com> from "Richard Seaman, Jr." at Mar 1, 99 03:10:46 pm X-Mailer: ELM [version 2.4 PL25] 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 > > > For user space threads and the Linux crap, the signal handling > > > should be possible, if you follow the disallow-all-but-one-thread > > > rule. [ ... ] > The shared signal handling code added to the kernel in Dec/Jan (is this > the "Linux crap" Terry refers to?) implement 1) and 2) above. Complete > compliance with 3) requires more changes. No. The kernel threading implementation for Linux kernel threads that is Linux ABI compliant is what I was referring to. The actual implementation is suboptimal. I'd go so far as to compare it to SVR3 shared libraries, which mapped into the same location in all processes, and couldn't be revised without eating a new chunk of the available address space. It's that degree of "suboptimal" I see there. I see many serious issues arising since Jeremy Allison and I did the (admitted) hacks to bring FreeBSD libpthreads into compliance with the Draft 4 specification. I can only say in our defense that: 1) We brought it all into line with a documented interface, instead of leaving it in limbo between standards, and it was thus usable, perhaps moreso than the "almost standard" stuff that's in there now. 2) We limited ourselves to user space, so while we were, in fact peeing in the pool to a degree, at least it wasn't the kernel. Which isn't much, but it's the only semi-valid defense there is. It's actually (IMO) time to step back from all of this bit-hacking and ask "What framework would encompass all of the use models we are trying to provide for?". IMO, the Linux threading, in particular, and the POSIX aio and thread interfaces, in general, represents a bunch of ill-thought-out hacks on hacks by the respective Linux and POSIX responsible persons. The Linux hacks were by people who didn't know better, and the POSIX hacks were political by people who did know better, but didn't have the courage of their convictions. It is time for some considered design. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 19:35: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 0A6C914C9E for ; Mon, 1 Mar 1999 19:34:59 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA03545; Mon, 1 Mar 1999 20:34:42 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd003406; Mon Mar 1 20:34:33 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id UAA23044; Mon, 1 Mar 1999 20:34:33 -0700 (MST) From: Terry Lambert Message-Id: <199903020334.UAA23044@usr01.primenet.com> Subject: Re: Fixing dlopen, ld.so, and upgrading the resolver To: danny@alpha.net.au (Danny) Date: Tue, 2 Mar 1999 03:34:32 +0000 (GMT) Cc: tlambert@primenet.com, jdp@polstra.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.32.19990302103635.006aff54@pop.alpha.net.au> from "Danny" at Mar 2, 99 10:37:01 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > Can u tell me why everytiime I do a shutdown NOW it keeps asking me for the > /bin/sh > > Then when I type in the commmand again and did a reboot it was the thing > was not properly dismounted. > > Do u know a way around that problem.. Yes. Your root device name does not match the one used by your mount and your kernel. When you upgraded your kernel, you failed to upgrade the mount command and/or you failed to redo your "MAKEDEV" and/or you failed to update your /etc/fstab. This particular problem is about a year old (in the -current list archives). I'm betting you did a make world and install to upgrade from 2.x to 3.x. Instructions on what to change are so old they have fallen out of my brain; see the -current list archives, using "mount" and "root" as search terms. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 1 20: 1:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 1AD0C14D04 for ; Mon, 1 Mar 1999 20:01:50 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 11852 invoked from network); 2 Mar 1999 04:01:27 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 2 Mar 1999 04:01:27 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id XAA62227; Mon, 1 Mar 1999 23:01:25 -0500 (EST) Message-Id: <199903020401.XAA62227@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903020330.UAA22888@usr01.primenet.com> from Terry Lambert at "Mar 2, 99 03:30:39 am" To: tlambert@primenet.com (Terry Lambert) Date: Mon, 1 Mar 1999 23:01:25 -0500 (EST) Cc: dick@tar.com, jplevyak@inktomi.com, tlambert@primenet.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Terry Lambert said: > > IMO, the Linux threading, in particular, and the POSIX aio and thread > interfaces, in general, represents a bunch of ill-thought-out hacks > on hacks by the respective Linux and POSIX responsible persons. The > Linux hacks were by people who didn't know better, and the POSIX > hacks were political by people who did know better, but didn't have > the courage of their convictions. It is time for some considered > design. > The AIO api has to be implemented for legitimacy, and likewise the threading. In fact, the AIO API is quite useful. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 1: 0:27 1999 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 19F3A14BD5 for ; Tue, 2 Mar 1999 01:00:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA36675 for ; Tue, 2 Mar 1999 01:00:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: hackers@freebsd.org Subject: Just FYI, I'll be at Linuxworld in San Jose Tuesday and Wednesday. Date: Tue, 02 Mar 1999 01:00:20 -0800 Message-ID: <36671.920365220@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG People complain that we don't "fly our colors" with the Linux folks more often, so Mike Smith and I have wandered down to staff a FreeBSD booth at the LinuxWorld expo thingie here in San Jose at the Convention Center. Those in the bay area who are interested should stop by Walnut Creek CDROM's booth and say hello. Later on in the day, a number of us also plan to geek-out at the tech museum across the street and then go have dinner, so it should be good fun. Anyway, so there you have it. If you can, stop on by and see us! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 1:39:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 7AE9C14CBB for ; Tue, 2 Mar 1999 01:39:17 -0800 (PST) (envelope-from akm@zeus.theinternet.com.au) Received: (from akm@localhost) by zeus.theinternet.com.au (8.8.7/8.8.7) id TAA21535; Tue, 2 Mar 1999 19:38:09 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199903020938.TAA21535@zeus.theinternet.com.au> Subject: Re: Cobalt blames linux for their security problems! In-Reply-To: <36DAA948.690A1354@softweyr.com> from Wes Peters at "Mar 1, 99 07:50:48 am" To: wes@softweyr.com (Wes Peters) Date: Tue, 2 Mar 1999 19:38:09 +1000 (EST) Cc: chris@calldei.com, julian@whistle.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (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 +----[ Wes Peters ]--------------------------------------------- | Chris Costello wrote: | > | > On Fri, Feb 26, 1999, Julian Elischer put this into my mailbox: | > > | > > There's a good idea.. use a free OS and then blame it for your problems.. | > > | > | > | > FreeBSD is a bad OS. This ASM code causes a memory fault! | > | | This simple C program: | | int main() | { | int *badboy = 0; | | *badboy = 3; | | return *badboy; | } | | when run on FreeBSD produces: | | wes$ ./a.out | Segmentation fault (core dumped) You need to use a smaller value of 3. d8) -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 3:32:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id 41B6E14C29 for ; Tue, 2 Mar 1999 03:32:47 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 23929 invoked by uid 1001); 2 Mar 1999 11:32:28 -0000 Date: Tue, 2 Mar 1999 06:32:28 -0500 (EST) From: Vince Vielhaber To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: Fixing dlopen, ld.so, and upgrading the resolver In-Reply-To: <199903020334.UAA23044@usr01.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Terry Lambert wrote: > Instructions on what to change are so old they have fallen out of my > brain; see the -current list archives, using "mount" and "root" as > search terms. Mail archives are still down. Anyone have an idea when they'll be back? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 4:20:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [194.87.112.252]) by hub.freebsd.org (Postfix) with ESMTP id 403F714D40 for ; Tue, 2 Mar 1999 04:18:39 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 10Ho7x-000D8Q-00 for freebsd-hackers@freebsd.org; Tue, 2 Mar 1999 18:18:22 +0600 Date: Tue, 2 Mar 1999 18:18:21 +0600 (ALMT) From: Boris Popov To: freebsd-hackers@freebsd.org Subject: VM and VFS relations 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, currently I try to optimize IO operations in nwfs and don't break consistency between normal and paged IO. After thorough reading of vfs_bio/vfs_aio/vfs_vnode_pager it is seems that VM and VFS layers are not tightly integrated. However code in vfs_bio (BIO layer) a very good candidate to do that (is this right ?). I'm very interesting in history of different IO layers and in plans of future development in that direction. Specially, in ability (possibility ?) of creating a single IO routine which will integrate both paged and normal IO operations for any file system. Any documents pointers, common notes, etc. would be very appreciated. -- Boris Popov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 5:19:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 9089414D54 for ; Tue, 2 Mar 1999 05:19:04 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 12838 invoked from network); 2 Mar 1999 13:18:33 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 2 Mar 1999 13:18:33 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id IAA63853; Tue, 2 Mar 1999 08:18:28 -0500 (EST) Message-Id: <199903021318.IAA63853@y.dyson.net> Subject: Re: VM and VFS relations In-Reply-To: from Boris Popov at "Mar 2, 99 06:18:21 pm" To: bp@butya.kz (Boris Popov) Date: Tue, 2 Mar 1999 08:18:28 -0500 (EST) Cc: freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Boris Popov said: > Hello, > > currently I try to optimize IO operations in nwfs and don't break > consistency between normal and paged IO. After thorough reading of > vfs_bio/vfs_aio/vfs_vnode_pager it is seems that VM and VFS layers are not > tightly integrated. However code in vfs_bio (BIO layer) a very good > candidate to do that (is this right ?). > vfs_bio has most of the stuff, but there are hooks in vfs_subr, and a few other places. > > I'm very interesting in history of different IO layers and > in plans of future development in that direction. Specially, in > ability (possibility ?) of creating a single IO routine which will > integrate both paged and normal IO operations for any file system. > That should be done. The buffer cache stuff was left in for legacy filesystem support. It is unlikely that softupdates would have been added to FreeBSD, if the buffer cache code was fully removed, for example... (That isn't to say that there weren't compatibility problems anyway.) > > Any documents pointers, common notes, etc. would be very > appreciated. > IMO, one of the best things to do, would be to remove the dependency of UFS from the buffer cache code (or at least, remove it for normal file I/O.) That would eliminate alot of the buffer building, reconstitution and destroying overhead. One proposal would be to create big mappings into a file, and explictly fill those mappings. (Don't depend on vm faults for filling buffers, ugh!!!) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 5:35:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penrose.isocor.ie (penrose.isocor.ie [194.106.155.117]) by hub.freebsd.org (Postfix) with ESMTP id 07CFC14BF6 for ; Tue, 2 Mar 1999 05:35:22 -0800 (PST) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (194.106.155.218) by penrose.isocor.ie; 2 Mar 1999 13:35:17 +0000 Message-ID: <36DBE8B5.A612F447@isocor.ie> Date: Tue, 02 Mar 1999 13:33:41 +0000 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: mmap on /dev/zero 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 seem to remember someone a while back suggesting that you could create shared memory between processes using mmap on /dev/zero, and passing the open descriptor to other processes (though I might be wrong). As a result, I thought the following might allow child and parent to share a mapped region: fd = open("/dev/zero", O_RDWR); fork(); p = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); A simple test indicated that the two mappings were seperate. (This was on 2.2.8-RELEASE, if its of any consequence) Is this possible to do such sharing through /dev/zero, or do I need to inherit the mapped region? I'd like to be able to dynamically expand the shared regions without resorting to using a normal file for the mapping, or resorting to SysV shared mem. (If this has been thrashed to death already, sorry, but the -hackers and -questions archives don't appear to be searchable at the moment) Cheers, Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 6:45:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 6FEFF14CD1 for ; Tue, 2 Mar 1999 06:43:15 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id JAA00799; Tue, 2 Mar 1999 09:43:10 -0500 (EST) Date: Tue, 2 Mar 1999 09:43:09 -0500 (EST) From: Alfred Perlstein To: Peter Edwards Cc: freebsd-hackers@FreeBSD.ORG, green@unixhelp.org Subject: Re: mmap on /dev/zero In-Reply-To: <36DBE8B5.A612F447@isocor.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 Tue, 2 Mar 1999, Peter Edwards wrote: > Hi, > I seem to remember someone a while back suggesting that you could create > shared memory between processes using mmap on /dev/zero, and passing the > open descriptor to other processes (though I might be wrong). > As a result, I thought the following might allow child and parent to > share a mapped region: > > fd = open("/dev/zero", O_RDWR); > fork(); > p = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); > > A simple test indicated that the two mappings were seperate. (This was > on 2.2.8-RELEASE, if its of any consequence) > > Is this possible to do such sharing through /dev/zero, or do I need to > inherit the mapped region? I'd like to be able to dynamically expand the > shared regions without resorting to using a normal file for the mapping, > or resorting to SysV shared mem. > (If this has been thrashed to death already, sorry, but the -hackers and > -questions archives don't appear to be searchable at the moment) It has. :) You can not do this, you must inherit the shared segment or use SYSV. I do remeber someone trying some evil hack with /proc but i don't know if they were successful... were you Brian Feldman? :) -Alfred > > Cheers, > Peter. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 7:27:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 88C2615447 for ; Tue, 2 Mar 1999 07:26:55 -0800 (PST) (envelope-from pixel@excalibur.oceanis.net) Received: (from pixel@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id PAA21720 for hackers@FreeBSD.ORG; Tue, 2 Mar 1999 15:26:33 GMT From: Emmanuel DELOGET Message-Id: <199903021526.PAA21720@excalibur.oceanis.net> Subject: bug in sysctl_sysctl_name To: hackers@FreeBSD.ORG (FreeBSD Hackers Mail List) Date: Tue, 2 Mar 1999 16:26:33 +0100 (MET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, hackers [sorry to disturb you] ! Experiencing with sysctls on different FreeBSD (mostly 2.2.8 and 3.1), it appears that I found an interesting bug in the sysctl code. This is the program that shows this bug : The normal invocation for this test program is prg num1 num2 .... numN. It displays the value of the { num1, ... , numN } OID. Ex : ./sysctl_test 1 1 will print the string : FreeBSD Using this proggy with args 0 1 1 1 will gives kern.ostype But... (there's allways a 'but') a) ./sysctl_test 0 1 5 1 --> panic on 3.1-RELEASE (trap 12, supervisor read, page not present) b) ./sysctl_test 0 1 5 0 --> reboot (without even panicing) on my 2.2.8 The fact is that is't not very good to force a reboot when a syscall just failed :) looking at the code in 2.2.8 for the called function sysctl_sysctl_name, I can't figure what's happening. /**** file sysctl_test.c ****************** cut here */ #include #include #include #include void main(int ac,char **av) { int oidnum[128]; int nlen,result; char buffer[32768]; int buflen = 16384; /* so I'm sure... */ char c; if (ac < 2) { printf("usage : %s %s\n", av[0], "oidnum1 oidnum2 ... oidnumN"); exit(-1); } for (nlen=1;nlen; Tue, 2 Mar 1999 07:25:58 -0800 (PST) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (194.106.155.218) by penrose.isocor.ie; 2 Mar 1999 15:25:59 +0000 Message-ID: <36DC02A7.2D99257A@isocor.ie> Date: Tue, 02 Mar 1999 15:24:23 +0000 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG, green@unixhelp.org Subject: Re: mmap on /dev/zero References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm. I think I could write a /dev/zero like driver to do this, or at least learn a lot trying. Would this be a worthwhile exercise? (I must say, that /proc idea has some evil appeal, though...) -- Peter. > > It has. :) > > You can not do this, you must inherit the shared segment or use SYSV. > > I do remeber someone trying some evil hack with /proc but i don't know > if they were successful... were you Brian Feldman? :) > > -Alfred > > > > > Cheers, > > Peter. > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 7:33:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id C8405154A6 for ; Tue, 2 Mar 1999 07:32:26 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id KAA05212; Tue, 2 Mar 1999 10:32:05 -0500 (EST) Date: Tue, 2 Mar 1999 10:32:03 -0500 (EST) From: Alfred Perlstein To: Peter Edwards Cc: freebsd-hackers@FreeBSD.ORG, green@unixhelp.org Subject: Re: mmap on /dev/zero In-Reply-To: <36DC02A7.2D99257A@isocor.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 Tue, 2 Mar 1999, Peter Edwards wrote: > > It has. :) > > > > You can not do this, you must inherit the shared segment or use SYSV. > > > > I do remeber someone trying some evil hack with /proc but i don't know > > if they were successful... were you Brian Feldman? :) > > > Hm. > I think I could write a /dev/zero like driver to do this, or at least > learn a lot trying. Would this be a worthwhile exercise? > (I must say, that /proc idea has some evil appeal, though...) I'm not a commiter, but i think it's functionality that would be most appreciated. -Alfred > -- > Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 8: 5:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from inside.home.documgmt.com (unknown [209.44.27.196]) by hub.freebsd.org (Postfix) with ESMTP id 66C6114E23 for ; Tue, 2 Mar 1999 08:05:04 -0800 (PST) (envelope-from doug@documgmt.com) Received: (from smap@localhost) by inside.home.documgmt.com (8.8.8/8.8.8) id KAA04141 for ; Tue, 2 Mar 1999 10:04:54 -0600 (CST) (envelope-from doug@documgmt.com) X-Authentication-Warning: inside.home.documgmt.com: smap set sender to using -f Received: from freebsd.home.documgmt.com(192.168.2.101) by inside.home.documgmt.com via smap (V2.1) id xma004139; Tue, 2 Mar 99 10:04:31 -0600 Received: from pentium.home.documgmt.com (node2.home.documgmt.com [192.168.2.12]) by documgmt.com (8.9.1/8.9.2) with SMTP id KAA26249 for ; Tue, 2 Mar 1999 10:04:12 -0600 (CST) Message-Id: <199903021604.KAA26249@documgmt.com> X-Sender: doug@freebsd.home.documgmt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 02 Mar 1999 10:04:25 -0600 To: hackers@freebsd.org From: Douglas Myers Subject: 1.) 20G IDE tape 2.) silo overflow 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 have a couple of questions. I run Freebsd on several systems (nothing short of excellent). The ones in question are running 3.0. I have recently purchased a 20G Seagate IDE tape drive that I would like to be able to use with a Freebsd system. The kernel appears to have support for some IDE tape drives but this one does not work. My questions are 1.) does the IDE tape support work on smaller drives? 2.) If so, is anyone working on the newer, larger drives? 3.) If not, or they need assistance I would be willing to help with this development (I have a strong Unix background including kernel device drivers and 20 years of software development experience). My second question regards an error message from the kernel. The message is sio0: silo overflow which seems to indicate received characters overflow on the 16650. This is coming from the serial port on the motherboard of Dell 350Mhz system. Has anyone else experienced this problem? I suspect it has to do with interrrupt configuration on the motherboard resulting in missed interrupts, I also tried to putting in an ISA serial card and had the same problem but not as severe. I've tried both irq3 and irq4 and made sure that these interrupts were reserved for ISA devices and that nothing else was on that interrupt. I have successfully used the sio driver on other systems without this error. Thanks for any suggestions you can send my way (I checked the handbook and FAQ's first but didn't find anything relevant). Douglas Myers Email: doug@documgmt.com Voice: 309-694-8112 Fax: 309-694-8113 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 10:29:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (Postfix) with ESMTP id 2BA6A15659 for ; Tue, 2 Mar 1999 10:29:23 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id MAA22538 for ; Tue, 2 Mar 1999 12:28:30 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id MAA29343 for ; Tue, 2 Mar 1999 12:27:09 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Tue, 2 Mar 1999 12:27:09 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: FreeBSD Hackers Subject: Repeated automatic reboots 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 added a simple system call to my FreeBSD 2.2.8 kernel and compiled it. Everything was okay till I rebooted the machine (Intel 486). After the usual probes for devices etc, it gave me this message: clntudp_create : Out of memory clntudp_create : Out of memory (null) Automatic reboot in 15 seconds... Anyone have any idea why this is happening? I ran an older version of the kernel and it worked fine. Appreciate your comments, Guru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 12: 4:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id EAA4114D63 for ; Tue, 2 Mar 1999 12:02:18 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA081584851; Tue, 2 Mar 1999 15:00:51 -0500 Date: Tue, 2 Mar 1999 15:00:51 -0500 (EST) From: Bill Fumerola To: Jasper O'Malley Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tn3270 -> tn5250 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 Mon, 1 Mar 1999, Jasper O'Malley wrote: > On Mon, 1 Mar 1999, Bill Fumerola wrote: > > > See ports/5626. > > 'ldap' port eats all available CPU time? Whoops. > If you meant ports/7680 - "New port of tn5250", that's the linux5250 port > I mentioned in my post. That's the one I meant, if you query-pr with 'Responsible=billf' you'll notice 5626 and 7680 being close to each other. :> Sorry. > Perhaps I should clarify my intent...I'm curious what it would take to > modify the Berkeley tn3270 to process a 5250 datastream, rather than the > 3270 datastream. Okay. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 12:56:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jedi.burnit.net (jedi.burnit.net [151.198.231.7]) by hub.freebsd.org (Postfix) with ESMTP id B47DE14E16 for ; Tue, 2 Mar 1999 12:55:53 -0800 (PST) (envelope-from wharton@burnit.net) Received: from localhost (wharton@localhost) by jedi.burnit.net (8.9.2/8.9.3) with ESMTP id QAA17924; Tue, 2 Mar 1999 16:00:34 -0500 (EST) Date: Tue, 2 Mar 1999 16:00:33 -0500 (EST) From: "Daniel J. Wharton" To: Gurudatt Shenoy Cc: FreeBSD Hackers Subject: Re: Repeated automatic reboots 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 I am wondering what device it is that you have added to your system. uh... also, how much physical memory do you have? All I can say is that you need to make sure that your new entry in the kernel is correct, and if it is, then maybe you need to add more physical memory to the system. Oh, another thing... is this the first time you compiled the kernel on this system, or is the previous kernel compiled by you? If the previous kernel is compiled by you, you might want to try running the GENERIC kernel to see if you might have screwed up. This will work only ofcourse the device is in the kernel by default. DAN WHARTON ----------------------------------------- System Administrator THE BURNIT NETWORK - www.burnit.net Director of Network Operations BIG SECRET - www.bigsecret.org ----------------------------------------- On Tue, 2 Mar 1999, Gurudatt Shenoy wrote: > > I added a simple system call to my FreeBSD 2.2.8 kernel and compiled it. > Everything was okay till I rebooted the machine (Intel 486). > After the usual probes for devices etc, it gave me this message: > > clntudp_create : Out of memory > clntudp_create : Out of memory > (null) > Automatic reboot in 15 seconds... > > Anyone have any idea why this is happening? > timeval structures, initializing each entry to zero> > > I ran an older version of the kernel and it > worked fine. > > Appreciate your comments, > Guru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 13:12:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 73BF014DF7 for ; Tue, 2 Mar 1999 13:11:47 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA85112; Tue, 2 Mar 1999 22:11:23 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903022111.WAA85112@freebsd.dk> Subject: Re: 1.) 20G IDE tape 2.) silo overflow In-Reply-To: <199903021604.KAA26249@documgmt.com> from Douglas Myers at "Mar 2, 1999 10: 4:25 am" To: doug@documgmt.com (Douglas Myers) Date: Tue, 2 Mar 1999 22:11:23 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Douglas Myers wrote: > Hello, > > I have a couple of questions. I run Freebsd on several systems (nothing > short of excellent). The ones in question are running 3.0. I have > recently purchased a 20G Seagate IDE tape drive that I would like to be > able to use with a Freebsd system. The kernel appears to have support for > some IDE tape drives but this one does not work. My questions are 1.) does > the IDE tape support work on smaller drives? 2.) If so, is anyone working > on the newer, larger drives? 3.) If not, or they need assistance I would be > willing to help with this development (I have a strong Unix background > including kernel device drivers and 20 years of software development > experience). 1. yes it works for me with a travan4 (4G) drive. 2. I'd love to do the support for that, lets see what we can find out. 3. There is a bunch-o-things we could try out, but lets take that in private mail. > My second question regards an error message from the kernel. The message > is sio0: silo overflow which seems to indicate received characters overflow > on the 16650. This is coming from the serial port on the motherboard of > Dell 350Mhz system. Has anyone else experienced this problem? I suspect > it has to do with interrrupt configuration on the motherboard resulting in > missed interrupts, I also tried to putting in an ISA serial card and had > the same problem but not as severe. I've tried both irq3 and irq4 and made > sure that these interrupts were reserved for ISA devices and that nothing > else was on that interrupt. I have successfully used the sio driver on > other systems without this error. Sounds kindof wierd, you must be doing something that keeps interrupts disabled for pretty long, or the fifo's in the 16550 are somehow not used. How fast do you run the ports ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 13:13:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (ip248.houston2.tx.pub-ip.psi.net [38.11.201.248]) by hub.freebsd.org (Postfix) with ESMTP id 6FC7814EAC for ; Tue, 2 Mar 1999 13:13:20 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id PAA34089; Tue, 2 Mar 1999 15:13:39 -0600 (CST) (envelope-from chris) Date: Tue, 2 Mar 1999 15:13:38 -0600 From: Chris Costello To: Gurudatt Shenoy Cc: FreeBSD Hackers Subject: Re: Repeated automatic reboots Message-ID: <19990302151337.D31528@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from Gurudatt Shenoy on Tue, Mar 02, 1999 at 12:27:09PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 2, 1999, Gurudatt Shenoy put this into my mailbox: > > I added a simple system call to my FreeBSD 2.2.8 kernel and compiled it. > Everything was okay till I rebooted the machine (Intel 486). > After the usual probes for devices etc, it gave me this message: > > clntudp_create : Out of memory > clntudp_create : Out of memory > (null) > Automatic reboot in 15 seconds... > > Anyone have any idea why this is happening? > timeval structures, initializing each entry to zero> > > I ran an older version of the kernel and it > worked fine. Perhaps you can specify more about your code. > > Appreciate your comments, > Guru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" In 1750, Isaac Newton became discouraged after having fallen up a flight of stairs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 13:15:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CC80814DC8 for ; Tue, 2 Mar 1999 13:15:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA57990; Tue, 2 Mar 1999 13:14:51 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Mar 1999 13:14:51 -0800 (PST) From: Matthew Dillon Message-Id: <199903022114.NAA57990@apollo.backplane.com> To: Matthew Jacob , freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, we're making progress. I found a major bug ( that Julian is committing now ). Kirk has already comitted fixes to ffs_fsync() for softupdates/NFS combinations and has some alternative code in softupdates for a BMSAFEMAP related issue. The bugfix is also in the queue to be committed into -3.x and hopefully also 2.2.x after we resolve a minor issue that John has brought up. It's a very serious bug though, gladly, it does not happen very often. Basically the getblk() code in kern/vfs_bio.c has a section: /* * This code is used to make sure that a buffer is not * created while the getnewbuf routine is blocked. * Normally the vnode is locked so this isn't a problem. * VBLK type I/O requests, however, don't lock the vnode. */ if (VOP_ISLOCKED(vp) != LK_EXCLUSIVE && gbincore(vp, blkno)) { bp->b_flags |= B_INVAL; brelse(bp); goto loop; } Which really should be: if (gbincore(vp, blkno)) { bp->b_flags |= B_INVAL; brelse(bp); goto loop; } The problem is that the original comment implies that getblk() might be called without the vnode locked. This does, in fact, happen. Ok... but that doesn't mean you can avoid checking gbincore() if you happen to find the vnode locked! Thus, the bogus VOP_ISLOCKED check can result in the system creating duplicate buffers for the same block. Needless to say, this can result in the complete destruction of directories, bitmaps, and filedata, as well as to duplicate allocation of blocks and other bad things. I believe this bug to be responsible for the 5 or 6 times ( over 4.5 years and 40+ machines ) that BEST has experienced severe filesystem corruption after a crash. -- The new VFS BIO and NFS fixes are still in the commit queue and under review, but I expect to get them committed into -4.x soon. Specifically, the new getnewbuf() code solves a low memory lockup problem and a more serious supervisor stack overflow problem ( on machines which have deep VFS call stacks, such as when you use the VN device ). Fixes to NFS's B_DONE handling are part of this mess too. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 13:48: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (Postfix) with ESMTP id 880F214E90 for ; Tue, 2 Mar 1999 13:47:47 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA13873 for ; Tue, 2 Mar 1999 22:56:04 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 2 Mar 1999 22:56:03 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-hackers@freebsd.org Subject: FreeBSD and ThinkPad Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My new employer provided me with a brand new ThinkPad 770X. Of course the first thing I tried was to boot FreeBSD on it. No luck :( The symptoms are as follows: sometime during the probing, or even later if I'm active enough pressing keys (see below) the machine hangs, and never recovers. I suspect it's somehow related to energy saving features - perhaps it just decides to go to sleep? Anyway, after this I'm totally unable to reboot it. The funny thing is that ThinkPad doesn't have the reset button, so I have to pull out the battery in order to reboot it... :-) Perhaps someone already went through this, and can give me a hint... TIA. Oh, BTW - the BIOS setup on this really sucks, it's a winblows oriented dummy icons which really don't give you any control over the details. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | 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 Tue Mar 2 13:48:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 28DE714F08 for ; Tue, 2 Mar 1999 13:48:02 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Hx0p-0004nO-00; Tue, 2 Mar 1999 23:47:35 +0200 From: Sheldon Hearn To: Douglas Myers Cc: hackers@freebsd.org Subject: Re: 1.) 20G IDE tape 2.) silo overflow In-reply-to: Your message of "Tue, 02 Mar 1999 10:04:25 CST." <199903021604.KAA26249@documgmt.com> Date: Tue, 02 Mar 1999 23:47:35 +0200 Message-ID: <18437.920411255@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 02 Mar 1999 10:04:25 CST, Douglas Myers wrote: > My second question regards an error message from the kernel. The > message is sio0: silo overflow which seems to indicate received > characters overflow on the 16650. It is quite possible to receive such an error message without there being any kind of "hardware problem" present. I get these routinely when I run my swampl.pl script and try to move the mouse around a lot while the machine is unresponsive. The swamp.pl script is designed to bring the machine to its knees under heavy paging and random file reads/writes. My take on this is simply that the machine is so damn bogged down that it doesn't get a chance to service the serial interrupts. Can you link the messages you get to some heavy job your machine does, or do you get them while it's chilling? If the former, don't worry about problematic hardware. If the latter, keep asking questions. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 13:51:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D0DF614DAD for ; Tue, 2 Mar 1999 13:51:09 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40347>; Wed, 3 Mar 1999 08:39:23 +1100 Date: Wed, 3 Mar 1999 08:50:43 +1100 From: Peter Jeremy Subject: Re: Panic in FFS/4.0 as of yesterday - update To: hackers@FreeBSD.ORG Message-Id: <99Mar3.083923est.40347@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: >Would the problem manifest itself under increasing load? One thing I'm >mulling doing is to try and move forward musbus or it's equivalent MUSBUS is now quite old - I believe it was developed around 1981. I have a paper Ken McDonell presented at AUUG'91 when he discussed some of its shortcomings at that time [and there are probably more now]. I've also heard him state (possibly during that presentation) that MUSBUS was designed to benchmark systems around 1 MIPS (ie a VAX 11/780), and results obtained on a `current' (ie 5-10 years old now) system probably reflect bottlenecks in MUSBUS, rather than the system under test. [Note that a later developent of MUSBUS - KENBUS - formed part of the SPEC's SDM (System Developent Multitasking) 1.x benchmark suite]. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 14: 8:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A5C414DF4 for ; Tue, 2 Mar 1999 14:08:12 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id OAA21135; Tue, 2 Mar 1999 14:07:48 -0800 Date: Tue, 2 Mar 1999 14:07:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: <199903022114.NAA57990@apollo.backplane.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 All very cool. I can't wait... My testing last night went well, but blew up for other reasons (this time the Fibre Channel loop got wanked). I'm trying to put together another large disk test system at Nasa/AMES. The system I was trying to use has some problems with the AIC driver that neither Justin nor I have been able to figure out- as soon as I find a couple more different SCSI adapters I'll be working with 4 60GB Raid units, plus part time access to at least two 150 GB Raid units. Luoqi has referred to this a couple of times- Do you happen know what interactions with CCDs all of this has? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 14:32: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from postoffice.sarnoff.com (postoffice.sarnoff.com [130.33.10.147]) by hub.freebsd.org (Postfix) with ESMTP id 4D5DD14DC8 for ; Tue, 2 Mar 1999 14:29:54 -0800 (PST) (envelope-from amarks@sarnoff.com) Received: from sarnoff.com ([130.33.14.232]) by postoffice.sarnoff.com (Netscape Messaging Server 3.5) with ESMTP id AAA3420 for ; Tue, 2 Mar 1999 17:29:33 -0500 Message-ID: <36DC669B.707C33C7@sarnoff.com> Date: Tue, 02 Mar 1999 17:30:51 -0500 From: "AARON MARKS" Reply-To: amarks@sarnoff.com Organization: Sarnoff Corporation X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: getpages() for a memory-based fs Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm working on the getpages() routine for a memory-based fs and I don't quite understand how to map my page(s) to kernel vm via the vm_page struct. What's the formal method of copying data to a vm page? Thanks, -A. -- Aaron J. Marks Communications and Computing Systems Lab Assoc. Member Tech Staff Advanced Networks and Computation Group amarks@sarnoff.com Sarnoff Corporation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 15: 5:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id CF87D1522E for ; Tue, 2 Mar 1999 15:05:12 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA08533; Tue, 2 Mar 1999 18:04:38 -0500 (EST) Date: Tue, 2 Mar 1999 18:04:38 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Alfred Perlstein Cc: Peter Edwards , freebsd-hackers@FreeBSD.ORG Subject: Re: mmap on /dev/zero In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Alfred Perlstein wrote: > > > On Tue, 2 Mar 1999, Peter Edwards wrote: > > > Hi, > > I seem to remember someone a while back suggesting that you could create > > shared memory between processes using mmap on /dev/zero, and passing the > > open descriptor to other processes (though I might be wrong). > > As a result, I thought the following might allow child and parent to > > share a mapped region: > > > > fd = open("/dev/zero", O_RDWR); > > fork(); > > p = mmap(0, getpagesize(), PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0); > > > > A simple test indicated that the two mappings were seperate. (This was > > on 2.2.8-RELEASE, if its of any consequence) > > > > Is this possible to do such sharing through /dev/zero, or do I need to > > inherit the mapped region? I'd like to be able to dynamically expand the > > shared regions without resorting to using a normal file for the mapping, > > or resorting to SysV shared mem. > > (If this has been thrashed to death already, sorry, but the -hackers and > > -questions archives don't appear to be searchable at the moment) > > It has. :) > > You can not do this, you must inherit the shared segment or use SYSV. > > I do remeber someone trying some evil hack with /proc but i don't know > if they were successful... were you Brian Feldman? :) Me? I was just mmaping in parts of /proc/foopid/mem =) > > -Alfred > > > > > > Cheers, > > Peter. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 15:31:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from stephens.ml.org (cm2081634025.ponderosa.ispchannel.com [208.163.40.25]) by hub.freebsd.org (Postfix) with ESMTP id 185E8154A4 for ; Tue, 2 Mar 1999 15:31:44 -0800 (PST) (envelope-from tas@stephens.ml.org) Received: from stephens.ml.org (localhost [127.0.0.1]) by stephens.ml.org (8.9.2/8.9.2) with ESMTP id XAA04972; Tue, 2 Mar 1999 23:31:16 GMT (envelope-from tas@stephens.ml.org) Message-Id: <199903022331.XAA04972@stephens.ml.org> To: John Polstra Cc: hackers@freebsd.org, Thomas Stephens From: Thomas Stephens Subject: Re: ELF, System V and multiple ABIs In-reply-to: Your message of "Sat, 27 Feb 1999 11:05:56 PST." <199902271905.LAA10250@vashon.polstra.com> Date: Tue, 02 Mar 1999 15:31:15 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: >In article <199902171844.SAA24903@stephens.ml.org>, >Thomas Stephens wrote: > >> I was looking over the latest System V ABI draft, and noticed there is >> an update (dated April 1998) which includes modifications to the ELF >> format. Significantly, the usage of the e_ident array in the ElfXX_Ehdr >> structure has changed slightly, in order to allow for multiple ABIs on >> each hardware platform. >> >> While the ELF format defined in the previous draft only used the first >> seven bytes of e_ident, with byte eight (EI_PAD) representing the start >> of padding, the current one adds two new values to support an OS/ABI >> identifier number followed by a version. As a side-effect, EI_PAD has >> been redefined: >> >> EI_OSABI 7 (OS/ABI identifier) >> EI_ABIVERSION 8 (OS/ABI version) >> EI_PAD 9 >> >> This new version of ELF currently defines EI_OSABI values for System V, >> HP-UX and stand-alone (embedded) applications, but it seems to me it >> would make things much easier if all ELF-compatible systems were to >> adopt it. > >Thanks very much for pointing this out! I wasn't aware of it. Glad to be of help! >I think it would be great to adopt this, and it looks like we could do >it without breaking backward compatibility for our current "branding" >scheme. Ah, that's good. I had noticed there was some overlap with EI_BRAND, but am new to FreeBSD and hadn't really looked at `branding' in depth. >Today I have written to a contact at SCO to try to get an OS/ABI code >assigned to FreeBSD. Hopefully that will bear some fruit and we can >move on to this scheme. That sounds great! If the other BSDs, Linux, Sun, etc. can be persuaded to adopt the new ELF spec as well, this whole problem of competing ABIs might finally be resolved. Thomas Stephens tas@stephens.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 15:42:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns10.nokia.com (ns10.nokia.com [131.228.6.229]) by hub.freebsd.org (Postfix) with ESMTP id 1066714E00 for ; Tue, 2 Mar 1999 15:42:40 -0800 (PST) (envelope-from chunan.li@nokia.com) Received: from msgws01ntc.ntc.nokia.com (msgws01ntc.ntc.nokia.com [131.228.59.181]) by ns10.nokia.com (8.8.8/8.6.9) with ESMTP id BAA24824 for ; Wed, 3 Mar 1999 01:42:23 +0200 (EET) Message-Id: <199903022342.BAA24824@ns10.nokia.com> Received: by msgws01ntc.ntc.nokia.com with Internet Mail Service (5.5.2232.9) id ; Wed, 3 Mar 1999 01:41:31 +0200 From: "Li ChunAn (Nokia/Beijing)" To: "'freebsd-hackers@FreeBSD.ORG'" Subject: interrupt mechanism Date: Tue, 2 Mar 1999 07:16:05 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I am a kernel programmer. Would you like to tell me something detailed about the interrupt mechanism and kernel programming guides? Where can I find the IRQ-handler table in kernel codes? Thank you! Best Regards Li ChunAn ---------------------------------------------------------------- Advanced Internet Technology Group No. 11 Hepingli Dongjie Dongcheng District Nokia China R&D Center Beijing 100013 chunan.li@ntc.nokia.com Tel. +86 10 84229922 Ext. 2870 chunan.li@research.nokia.com MP. +86 10 1361028331 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 15:59:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0BFD614DE0 for ; Tue, 2 Mar 1999 15:59:49 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id PAA21697; Tue, 2 Mar 1999 15:58:51 -0800 Date: Tue, 2 Mar 1999 15:58:51 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: <99Mar3.083923est.40347@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 3 Mar 1999, Peter Jeremy wrote: > Matthew Jacob wrote: > >Would the problem manifest itself under increasing load? One thing I'm > >mulling doing is to try and move forward musbus or it's equivalent > > MUSBUS is now quite old - I believe it was developed around 1981. I > have a paper Ken McDonell presented at AUUG'91 when he discussed some > of its shortcomings at that time [and there are probably more now]. > > I've also heard him state (possibly during that presentation) that > MUSBUS was designed to benchmark systems around 1 MIPS (ie a VAX > 11/780), and results obtained on a `current' (ie 5-10 years old now) > system probably reflect bottlenecks in MUSBUS, rather than the system > under test. > > [Note that a later developent of MUSBUS - KENBUS - formed part of the > SPEC's SDM (System Developent Multitasking) 1.x benchmark suite]. Yes. I actually played around with KENBUS for NetBSD but couldn't get it compiled since it seemed to depend on some libc calls not in NetBSD. There was a version of MUSBUS in use at Sun - and yes, MUSBUS is indeed quite old- but it's useful in that you get load stages for both context switching, IPC, and, to a lesser extend, disk I/O. There may or may not be bottlenecks intrinsic to MUSBUS, but I can assure you that it's a start. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 16:15:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.249.195.3]) by hub.freebsd.org (Postfix) with ESMTP id D3E9314E6B for ; Tue, 2 Mar 1999 16:15:29 -0800 (PST) (envelope-from paulo@nlink.com.br) Received: from localhost (paulo@localhost) by mirage.nlink.com.br (8.9.3/8.9.1) with SMTP id VAA29050 for ; Tue, 2 Mar 1999 21:15:10 -0300 (EST) Date: Tue, 2 Mar 1999 21:15:10 -0300 (EST) From: Paulo Fragoso To: freebsd-hackers@freebsd.org Subject: Problems with Trumpet Winsock 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'm having problems with my dialin server, after upgrade to FBSD-3.1-RELEASE. My clients using Win95 are ok, but with 3.xx using trumpet don't work. My pppd with kdebug 7 print this results in trumpet conection: Mar 1 17:20:03 xingu /kernel: ppp27: missing UI (0x3), got 0x21 Mar 1 17:20:04 xingu /kernel: ppp27 output:ff03002145000... and in with win95 users: Mar 1 17:19:56 xingu /kernel: ppp27: got 14 bytes Mar 1 17:19:56 xingu /kernel: ff0380210103000a0306c8f9c351 Mar 1 17:19:56 xingu /kernel: ppp27 output: ff0380210203000a0306c8f9c351 It seems with trumpet conections my pppd is not accepting data from trumpet. Are there any solution? We are using trumpet 2.0B and 3.0. Thanks, Paulo. ps.: I make same question in freebsd-isp but I didn't receive any idea, please help me!! ------ " ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else" -David Filo, Yahoo! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 16:15:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 3C75614DDB for ; Tue, 2 Mar 1999 16:15:45 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id SAA02775 for freebsd-hackers@freebsd.org; Tue, 2 Mar 1999 18:15:29 -0600 (CST) (envelope-from bob) Date: Tue, 2 Mar 1999 18:15:28 -0600 From: Bob Willcox To: hackers list Subject: 3.1-stable on MP w/bogus cpu usage times Message-ID: <19990302181528.A2684@luke.pmr.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=NzB8fVQJ5HfG6fxh X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Hi, I just installed a second Xeon processor in my 3.1-stable (as of this morning) system (with a freshly built MP kernel) and have noticed two problems: 1. top, ps, vmstat, and every other system monitor that displays cpu usage that I've tried shows 0 usage for everything, e.g. top displays: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Based upon how the system runs and after quite a bit of searching for any hog processes I believe that the system really is idle. 2. xperfmon++-3.0 dies quickly with a SIGFPE whenever I load the system up (like build a kernel). Does anyone have any idea if these are well-known problems or if there is something I may be doing to cause them? I have attached my kernel configuration file and mptable output. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="LUKE.mp" # # LUKE.mp -- Dual Xeon machine # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: LUKE,v 1.143 1999/01/11 03:18:31 yokota Exp $ machine "i386" cpu "I686_CPU" ident LUKE_mp maxusers 128 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=10000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # Size of the kernel message buffer. Should be N * pagesize. #options "MSGBUF_SIZE=40960" config kernel root on da0 # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs options NBUS=3 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ncr0 controller ahc0 controller scbus0 at ahc0 bus 0 # Twin bus device controller scbus1 at ahc0 bus 1 # Twin bus device controller scbus2 at ncr0 disk da0 at scbus0 target 0 unit 0 disk da1 at scbus0 target 1 unit 0 disk da2 at scbus0 target 2 unit 0 tape sa0 at scbus2 target 5 tape sa2 at scbus2 target 6 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 # Serial ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 # Parallel port device ppc0 at isa? port? net irq 7 # drq ? (from bios setup) controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? # SoundBlaster 32 controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device fxp0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 4 pseudo-device pty 256 pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V ipc's # options SYSVSHM options SYSVSEM options SYSVMSG # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter # USB support #controller uhci0 #controller ohci0 #controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # #device ums0 #device ukbd0 #device ulpt0 #device uhub0 #device ucom0 #device umodem0 #device hid0 #device ugen0 # #options USB_DEBUG #options USBVERBOSE --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mptable.out" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f6df0 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x42 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f69e6 signature: 'PCMP' base table length: 276 version: 1.4 checksum: 0x3e OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 26 local APIC address: 0xfee00000 extended table length: 124 extended table checksum: 177 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 1 0x11 BSP, usable 6 5 2 0x183fbff 0 0x11 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT conforms conforms 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 12 2 12 INT conforms conforms 2 14 2 14 INT active-lo level 1 0:A 2 16 INT active-lo level 0 4:D 2 19 INT active-lo level 0 6:A 2 17 INT active-lo level 0 6:A 2 17 INT active-lo level 0 7:A 2 19 INT active-lo level 0 12:A 2 16 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT active-hi edge 2 0 255 0 NMI active-hi edge 2 0 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- bus ID: 0 address type: I/O address address base: 0x0 address range: 0x10000 -- bus ID: 0 address type: memory address address base: 0x10000000 address range: 0xd1f00000 -- bus ID: 0 address type: prefetch address address base: 0xe1f00000 address range: 0x6100000 -- bus ID: 0 address type: memory address address base: 0xe8000000 address range: 0x18000000 -- bus ID: 0 address type: memory address address base: 0xa0000 address range: 0x20000 -- bus ID: 2 bus info: 0x01 parent bus ID: 0-- bus ID: 0 address modifier: add predefined range: 0x00000000-- bus ID: 0 address modifier: add predefined range: 0x00000001 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=3 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 16:35:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1C49814D13 for ; Tue, 2 Mar 1999 16:35:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA59145; Tue, 2 Mar 1999 16:34:57 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Mar 1999 16:34:57 -0800 (PST) From: Matthew Dillon Message-Id: <199903030034.QAA59145@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :All very cool. I can't wait... : :My testing last night went well, but blew up for other reasons (this time :the Fibre Channel loop got wanked). I'm trying to put together another :large disk test system at Nasa/AMES. The system I was trying to use has :some problems with the AIC driver that neither Justin nor I have been able :to figure out- as soon as I find a couple more different SCSI adapters :I'll be working with 4 60GB Raid units, plus part time access to at least :two 150 GB Raid units. : :Luoqi has referred to this a couple of times- Do you happen know what :interactions with CCDs all of this has? : :-matt I don't know of any operational bugs in the CCD device myself. There are bugs in vinum. The only gotcha with a CCD device that I know of is that you have to remember to offset the first partition by 16 sectors or you risk loosing ccd's disklabel. -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 Tue Mar 2 16:40: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4ABE614DB2 for ; Tue, 2 Mar 1999 16:39:59 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA21796; Tue, 2 Mar 1999 16:39:36 -0800 Date: Tue, 2 Mar 1999 16:39:36 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: <199903030034.QAA59145@apollo.backplane.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 > > :All very cool. I can't wait... > : > :My testing last night went well, but blew up for other reasons (this time > :the Fibre Channel loop got wanked). I'm trying to put together another > :large disk test system at Nasa/AMES. The system I was trying to use has > :some problems with the AIC driver that neither Justin nor I have been able > :to figure out- as soon as I find a couple more different SCSI adapters > :I'll be working with 4 60GB Raid units, plus part time access to at least > :two 150 GB Raid units. > : > :Luoqi has referred to this a couple of times- Do you happen know what > :interactions with CCDs all of this has? > : > :-matt > > I don't know of any operational bugs in the CCD device myself. There > are bugs in vinum. Wasn't planning on using it... > > The only gotcha with a CCD device that I know of is that you have to > remember to offset the first partition by 16 sectors or you risk loosing > ccd's disklabel. > Yah....Good. will try it.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 16:40:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AC83214D90 for ; Tue, 2 Mar 1999 16:40:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA59228; Tue, 2 Mar 1999 16:40:03 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Mar 1999 16:40:03 -0800 (PST) From: Matthew Dillon Message-Id: <199903030040.QAA59228@apollo.backplane.com> To: "AARON MARKS" Cc: hackers@FreeBSD.ORG Subject: Re: getpages() for a memory-based fs References: <36DC669B.707C33C7@sarnoff.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm working on the getpages() routine for a memory-based fs and I don't :quite understand how to map my page(s) to kernel vm via the vm_page :struct. What's the formal method of copying data to a vm page? : :Thanks, :-A. : :-- :Aaron J. Marks Communications and Computing Systems Lab :Assoc. Member Tech Staff Advanced Networks and Computation Group :amarks@sarnoff.com Sarnoff Corporation A vm_page_t is not mapped. Typically you map it by allocating a physical buffer with getpbuf() and mapping up to MAXBSIZE bytes worth of pages into it's reserved KVM space using pmap_qenter(). You must, of course, undo the mappings when finished with them. For an eample if how to do this, look at swap_pager_getpages() in vm/swap_pager.c from FreeBSD-current ( i.e. the -4.x tree, not the -3.x tree. The -3.x version of the function is not very readable ). There are kernel support routines to zero pages, copy pages ( see uiomove, uiomoveco ), and so forth but I think you will be happier using a pbuf. -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 Tue Mar 2 16:59:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 70EB014DF0 for ; Tue, 2 Mar 1999 16:58:35 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id SAA00648 for freebsd-hackers@freebsd.org; Tue, 2 Mar 1999 18:58:16 -0600 (CST) (envelope-from bob) Date: Tue, 2 Mar 1999 18:58:16 -0600 From: Bob Willcox To: hackers list Subject: Re: 3.1-stable on MP w/high tty out and interrupts Message-ID: <19990302185816.A491@luke.pmr.com> Reply-To: Bob Willcox References: <19990302181528.A2684@luke.pmr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990302181528.A2684@luke.pmr.com>; from Bob Willcox on Tue, Mar 02, 1999 at 06:15:28PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some additional observarions: On my most recent boot things seemed normal for awhile with both top and xperfmon++-3.0 behaving normally. However, while reading some mail via mutt I scrolled to the bottom of the mail item and got several beeps (as I tried to go further). At that point the tty out chars/sec on xperfmon++ jumped to over 210,000 and the interrupts went to over 37,000/sec. At the same time Idle CPU % went to zero. Soon xperfmon++ crashed. Upon restarting xperfmon++ I see that I am still getting over 55,000 tty out chars/sec and over 40,000 interrupts/sec. Letting the system idle for several minutes still has the tty out char/sec in the 20,000/sec range and the interrupt/sec at about 17,000. Something does seem really strange. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 17: 8:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (Postfix) with ESMTP id CF55614E12 for ; Tue, 2 Mar 1999 17:08:43 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id TAA15459; Tue, 2 Mar 1999 19:07:38 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id TAA00703; Tue, 2 Mar 1999 19:06:16 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Tue, 2 Mar 1999 19:06:16 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: "Daniel J. Wharton" Cc: FreeBSD Hackers , chris@calldei.com Subject: Re: Repeated automatic reboots 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 Daniel, Chris; thanks for your responses. Here's some more information: I think I have enough physical memory :This was what it showed me while booting: Real Memory: 20480 KB Actual Memory: 17700 KB (Btw, what's the distiction? Is the "actual mem" that which is available after loading all the memory resident modules?) The code I wrote goes like this (It is not device driver code; just a simple routine to carry out some initializations I needed to do to take some jitter measurements) : int jittertab_init(p, uap,retval) struct proc *p; struct jittertab_init_args /*{ Struct definition in sysproto.h int dummy; } */ *uap; int *retval; { int i; jitter_tab_ptr = 0; /* Extern variable; defined in init_main.c */ for(i=0;i I added a simple system call to my FreeBSD 2.2.8 kernel and compiled it. > Everything was okay till I rebooted the machine (Intel 486). > After the usual probes for devices etc, it gave me this message: > > clntudp_create : Out of memory > clntudp_create : Out of memory > (null) > Automatic reboot in 15 seconds... > > Anyone have any idea why this is happening? > timeval structures, initializing each entry to zero> > > I ran an older version of the kernel and it > worked fine. > > Appreciate your comments, > Guru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 18:14:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (Postfix) with ESMTP id 46F4015546 for ; Tue, 2 Mar 1999 18:14:40 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from torrey.cs.utah.edu (torrey.cs.utah.edu [155.99.212.91]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id TAA20375; Tue, 2 Mar 1999 19:14:08 -0700 (MST) Received: (from danderse@localhost) by torrey.cs.utah.edu (8.9.1/8.9.1) id TAA02234; Tue, 2 Mar 1999 19:14:08 -0700 (MST) (envelope-from danderse@cs.utah.edu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 2 Mar 1999 19:14:08 -0700 (MST) From: "David G. Andersen" To: Doug Ambrisko Cc: julian@whistle.com (Julian Elischer), freebsd-hackers@FreeBSD.ORG Subject: Re: Oskit and 3.0? In-Reply-To: Doug Ambrisko's message of Tue, February 16 1999 <199902161900.LAA77291@whistle.com> References: <199902161900.LAA77291@whistle.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14044.39469.671629.529987@torrey.cs.utah.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lo and Behold, Doug Ambrisko said: > Julian Elischer writes: > | we netboot elf kernels and aout kernels here.. > | check with doug ambrisko (ambrisko@whistle.com) for his netbooting stuff. > > It would be nice if some commiter would commit pr: > [1999/01/13] ports/9480 ports ELF kernel netboot > > I know one person is using is using it besides me. Note that since then we > have found 2 bugs in it. One is that in my patches I forgot and > init_serial in main and used option 131 for boot how to which was used > for swap options. If someone lets me know if they are going to commit > it then I will send them the patches. Could you send me the patches? If they're relevant to the OSKit netboot kernels, I'd love to commit them here as well. On the subject of netboot patches, I recently patched up our netboot to have a slightly less braindead NFS pseudo-implementation (it enqueues multiple NFS requests on the wire at a time), and it sped things up by about 30-40% here. There's always that question of relevance to the current BSD netboot, but if someone who's poking around in FreeBSD's netboot is interested, I'd love to drop off some patches. > That OSKit looks interesting. Thank you. :-) -Dave [speaking for myself, etc., etc.] -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Computer Science - Flux Research Group "What's footnote FIVE?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 18:46:35 1999 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 ED56B14ED7 for ; Tue, 2 Mar 1999 18:46:14 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id LAA17187; Wed, 3 Mar 1999 11:46:03 +0900 (JST) Message-ID: <36DC9F5D.3E235BEA@newsguy.com> Date: Wed, 03 Mar 1999 11:33:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Andrzej Bialecki Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > unable to reboot it. The funny thing is that ThinkPad doesn't have the > reset button, so I have to pull out the battery in order to reboot it... You sure it isn't just a matter of for how long you press the power button? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 18:57:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 9071214E91 for ; Tue, 2 Mar 1999 18:56:08 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id SAA59766; Tue, 2 Mar 1999 18:56:04 -0800 (PST) (envelope-from ulf) Message-ID: <19990302185603.A55209@TelcoSucks.org> Date: Tue, 2 Mar 1999 18:56:03 -0800 From: Ulf Zimmermann To: "Daniel C. Sobral" , Andrzej Bialecki Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad Reply-To: ulf@Alameda.net References: <36DC9F5D.3E235BEA@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36DC9F5D.3E235BEA@newsguy.com>; from Daniel C. Sobral on Wed, Mar 03, 1999 at 11:33:01AM +0900 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 03, 1999 at 11:33:01AM +0900, Daniel C. Sobral wrote: > Andrzej Bialecki wrote: > > > > unable to reboot it. The funny thing is that ThinkPad doesn't have the > > reset button, so I have to pull out the battery in order to reboot it... > > You sure it isn't just a matter of for how long you press the power > button? I remember my Thinkpad at the previous job had some needle point reset button hidden on the side somewhere. > > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > > "FreeBSD is Yoda, Linux is Luke Skywalker." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 20:15:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak.texar.com (pak.texar.com [207.112.49.1]) by hub.freebsd.org (Postfix) with ESMTP id D820914BEC for ; Tue, 2 Mar 1999 20:15:16 -0800 (PST) (envelope-from dseg@pak.texar.com) Received: (from dseg@localhost) by pak.texar.com (8.8.8/8.8.3) id XAA19397; Tue, 2 Mar 1999 23:14:58 -0500 (EST) Date: Tue, 2 Mar 1999 23:14:58 -0500 (EST) From: Dan Seguin To: Douglas Myers Cc: hackers@FreeBSD.ORG Subject: Re: 1.) 20G IDE tape 2.) silo overflow In-Reply-To: <199903021604.KAA26249@documgmt.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 Glad you asked about the silo overflow. I get this each and every time I spark up (user) ppp. I use an internal modem (no docs anywhere, except for one line in the FAQ). This happens to me in 2.2.8. After a while (20 minutes, either idle or busy) I have to kill ppp and reconnect. Everyting else checks out, including the ISP (as I use other OS' with this ISP, no probs). I was hoping this would go away with an upgrade (grumble, grumble). The only thing that I suspect (in my case) is incorrect parametres in the kernel config file, i.e. don't use the vector keyword, etc. But I can't find any docs on how to configure these. The simple one example isn't sufficient to generalize from ( in the handbook). Hope you find out, and I hope someone can point me to some docs that I've missed. Thanks! Dan Seguin Azure Automata On Tue, 2 Mar 1999, Douglas Myers wrote: > Hello, > > I have a couple of questions. I run Freebsd on several systems (nothing > short of excellent). The ones in question are running 3.0. I have > > My second question regards an error message from the kernel. The message > is sio0: silo overflow which seems to indicate received characters overflow > on the 16650. This is coming from the serial port on the motherboard of > Dell 350Mhz system. Has anyone else experienced this problem? I > > > Douglas Myers > Email: doug@documgmt.com > Voice: 309-694-8112 > Fax: 309-694-8113 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 2 20:31:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by hub.freebsd.org (Postfix) with ESMTP id 6FFA414E52 for ; Tue, 2 Mar 1999 20:30:50 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: (from durham@localhost) by w2xo.pgh.pa.us (8.9.1/8.9.1) id XAA08604 for freebsd-hackers@freebsd.org; Tue, 2 Mar 1999 23:31:05 -0500 (EST) (envelope-from durham) Date: Tue, 2 Mar 1999 23:31:05 -0500 (EST) From: Jim Durham Message-Id: <199903030431.XAA08604@w2xo.pgh.pa.us> To: freebsd-hackers@freebsd.org Subject: natd core dumps in packetBuf Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a 3.0-RELEASE system, I've had problems with natd core dumping. I compiled it with -g and was able to run gdb with symbols in the last dump. Here's what I see... GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. Core was generated by `natd'. Program terminated with signal 11, Segmentation fault. #0 0x280aca00 in ?? () (gdb) file natd Reading symbols from natd...done. (gdb) where #0 0x280aca00 in ?? () #1 0x804c6c9 in packetBuf () #2 0x280570fd in ?? () #3 0x2805722d in ?? () #4 0x28056298 in ?? () #5 0x280569ee in ?? () #6 0x804977a in DoAliasing (fd=3) at natd.c:492 #7 0x8049503 in main (argc=3, argv=0xefbfd7c4) at natd.c:348 #8 0x8048ea5 in _start () Any ideas? regards, Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 0:51:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 5EB1414BEA for ; Wed, 3 Mar 1999 00:51:13 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA26515 for hackers@freebsd.org; Wed, 3 Mar 1999 09:50:59 +0100 (MET) (envelope-from kuku) Date: Wed, 3 Mar 1999 09:50:59 +0100 (MET) From: Christoph Kukulies Message-Id: <199903030850.JAA26515@gilberto.physik.RWTH-Aachen.DE> To: hackers@freebsd.org Subject: brandelf (necessary?) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In an environment where FreeBSD needs to run linux binaries that are shared with linux systems, would it do harm to brandelf these binaries? Or in other words, would it be possible for FreeBSD to autodetect that it's a linux ELF binary without having to brand it? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 1:55:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with ESMTP id 9007A14D57 for ; Wed, 3 Mar 1999 01:55:18 -0800 (PST) (envelope-from dreamer@ninsei.com) Received: from localhost (dreamer@localhost) by citadel.ninsei.com (8.9.2/8.9.2) with ESMTP id CAA25087 for ; Wed, 3 Mar 1999 02:55:00 GMT (envelope-from dreamer@ninsei.com) X-Authentication-Warning: citadel.ninsei.com: dreamer owned process doing -bs Date: Wed, 3 Mar 1999 02:55:00 +0000 (GMT) From: Steven Young To: freebsd-hackers@freebsd.org Subject: menuconfig 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 Hiya. Although this doesn't seem like quite the right list to mail this to, I'm sending it here for lack of a better alternative.. Anyway, I've started work on a visual ncurses-based kernel config file editor. Therefore, I was wondering, is this a duplication of effort? Is there already something out there that does this? If not, my basic plan is just to have something that looks a lot like the visual boot-time config editor where the user adds everything s/he wants from the "inactive" list to the "active" and eventually the utility in question spits out a file. Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 2: 6:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id AAEF714F46 for ; Wed, 3 Mar 1999 02:05:05 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id UAA14273; Wed, 3 Mar 1999 20:34:47 +1030 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA28412; Wed, 3 Mar 1999 20:34:46 +1030 Date: Wed, 3 Mar 1999 20:34:46 +1030 (CST) From: Kris Kennaway To: Emmanuel DELOGET Cc: FreeBSD Hackers Mail List Subject: Re: bug in sysctl_sysctl_name In-Reply-To: <199903021526.PAA21720@excalibur.oceanis.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 2 Mar 1999, Emmanuel DELOGET wrote: > Experiencing with sysctls on different FreeBSD > (mostly 2.2.8 and 3.1), it appears that I found an > interesting bug in the sysctl code. Is this related to kern/9218? Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 2: 6:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id CA64214F45; Wed, 3 Mar 1999 02:06:12 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.3/8.9.3) with ESMTP id KAA19654; Wed, 3 Mar 1999 10:05:50 GMT Message-ID: <36DD097D.C102C656@tdx.co.uk> Date: Wed, 03 Mar 1999 10:05:49 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Steven Young Cc: freebsd-hackers@FreeBSD.ORG, freebsd-config@FreeBSD.ORG Subject: Re: menuconfig References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steven Young wrote: > Hiya. Although this doesn't seem like quite the right list to mail this > to, I'm sending it here for lack of a better alternative.. Theres always freebsd-config? :) (as cc'd) > Anyway, I've started work on a visual ncurses-based kernel config file > editor. Therefore, I was wondering, is this a duplication of effort? Is > there already something out there that does this? It was discussed a while ago... I myself even starting working on something similar, but the company I work for decided it was cheaper to pay me to maintain their boxes, than it was to have my time taken up writing something that meant other people could maintain them :( > If not, my basic plan is just to have something that looks a lot like > the visual boot-time config editor where the user adds everything s/he > wants from the "inactive" list to the "active" and eventually the utility > in question spits out a file. Sounds good... How are you going to handle keeping it up to date etc? - as FreeBSD changes? (or bits of it change, e.g. Sendmail versions etc.) :) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 2:18:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id AE7DC15517 for ; Wed, 3 Mar 1999 02:18:22 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 5354 invoked by uid 1001); 3 Mar 1999 03:33:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Mar 1999 03:33:43 -0000 Date: Tue, 2 Mar 1999 20:33:43 -0700 (MST) From: Steven Young To: Karl Pielorz Cc: freebsd-hackers@FreeBSD.ORG, freebsd-config@FreeBSD.ORG Subject: Re: menuconfig In-Reply-To: <36DD097D.C102C656@tdx.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 Wed, 3 Mar 1999, Karl Pielorz wrote: > > If not, my basic plan is just to have something that looks a lot like > > the visual boot-time config editor where the user adds everything s/he > > wants from the "inactive" list to the "active" and eventually the utility > > in question spits out a file. > > Sounds good... How are you going to handle keeping it up to date etc? - as > FreeBSD changes? (or bits of it change, e.g. Sendmail versions etc.) :) Well, what I was actually meaning was a kernel configuration utility, not an overall system configuration utility. My general plan is to have spec file of some sort that describes all the different options that can be in the config file and how they relate to each other. Thus, when a new option is added to the kernel, you just have to add a couple of lines to the spec file and voila. Steve (my first 10 minutes running qmail - hope this gets through!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 2:18:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 01B6A14EDD for ; Wed, 3 Mar 1999 02:18:20 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id FAA21353; Wed, 3 Mar 1999 05:18:37 -0500 (EST) Date: Wed, 3 Mar 1999 05:18:35 -0500 (EST) From: Alfred Perlstein To: Steven Young Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: menuconfig 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, 3 Mar 1999, Steven Young wrote: > > Hiya. Although this doesn't seem like quite the right list to mail this > to, I'm sending it here for lack of a better alternative.. > > Anyway, I've started work on a visual ncurses-based kernel config file > editor. Therefore, I was wondering, is this a duplication of effort? Is > there already something out there that does this? > > If not, my basic plan is just to have something that looks a lot like > the visual boot-time config editor where the user adds everything s/he > wants from the "inactive" list to the "active" and eventually the utility > in question spits out a file. many people have offered, none have completed it. 2 things you'll need to take into account for usablity: for users: the ability to suck in a local config file for developers: an interface to make sure the tool is updated and follows LINT without getting rid of lint, perhaps LINT and the template file being auto generated... -Alfred > > Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 2:32:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.102]) by hub.freebsd.org (Postfix) with ESMTP id B577D14F45 for ; Wed, 3 Mar 1999 02:32:17 -0800 (PST) (envelope-from takamune@avrl.mei.co.jp) Received: by bulls.mei.co.jp (8.9.1/3.7W) with ESMTP id TAA09946 for ; Wed, 3 Mar 1999 19:31:50 +0900 (JST) Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id TAA02055 for ; Wed, 3 Mar 1999 19:31:49 +0900 (JST) Received: by avrlgate1.avrl.mei.co.jp (8.6.10+2.4W/3.3W3-avrl3.0) id TAA12321; Wed, 3 Mar 1999 19:30:57 +0900 To: hackers@FreeBSD.ORG Subject: Special source '.MAKE' From: Kazu TAKAMUNE X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990303193059O.takamune@avrl.mei.co.jp> Date: Wed, 03 Mar 1999 19:30:59 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 44 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Does make(1)'s special source (not local variable) '.MAKE' work validly ? I have a try as follows: % cat Makefile doit: .MAKE ${MAKE}${MAKEFLAGS} sub sub: uname % make doit make sub uname FreeBSD % make -n doit make -n sub I expect last result to be make -n sub uname 'Recursive make' will be widely applicable to our development. Apparently it seems that these codes are ... % cd /usr/src/usr.bin/make % grep -n '\.MAKE[^F]' *.[ch] parse.c:215:{ ".MAKE", Attribute, OP_MAKE }, str.c:60: argv[0] = Var_Value(".MAKE", VAR_GLOBAL, &p1); str.c:135: * the first word is always the value of the .MAKE variable. % grep -n 'OP_MAKE' *.[ch] job.c:530: noSpecials = (noExecute && !(job->node->type & OP_MAKE)); job.c:1719: if ((gn->type & OP_MAKE) || (!noExecute && !touchFlag)) { make.h:188:#define OP_MAKE 0x00000200 /* Target is a recurrsive make so its parse.c:215:{ ".MAKE", Attribute, OP_MAKE }, parse.c:231:{ ".RECURSIVE", Attribute, OP_MAKE }, --- With best regards. TAKAMUNE Kazutoki takamune@avrl.mei.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 4:25:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id D63A014CD1 for ; Wed, 3 Mar 1999 04:25:25 -0800 (PST) (envelope-from pixel@excalibur.oceanis.net) Received: (from pixel@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id MAA05418; Wed, 3 Mar 1999 12:24:41 GMT From: Emmanuel DELOGET Message-Id: <199903031224.MAA05418@excalibur.oceanis.net> Subject: Re: bug in sysctl_sysctl_name In-Reply-To: from Kris Kennaway at "Mar 3, 1999 8:34:46 pm" To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Wed, 3 Mar 1999 13:24:41 +0100 (MET) Cc: hackers@FreeBSD.ORG (FreeBSD Hackers Mail List) 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 As the well known Kris Kennaway said... ->On Tue, 2 Mar 1999, Emmanuel DELOGET wrote: -> ->> Experiencing with sysctls on different FreeBSD ->> (mostly 2.2.8 and 3.1), it appears that I found an ->> interesting bug in the sysctl code. -> ->Is this related to kern/9218? I forgot to mention it in my previous mail. It seems it is, that's why I send my report to the hackers list, and didn't send any 'real' bug report. The kern/9218 decribes a bug in the {0,3} (sysctl_sysctl_name2oid()). The crash I experienced was probably in sysctl_sysctl_name(). In fact, the bug may not be located in those functions, but (perhaps) in an upper level function (like sysctl_root() or userland_sysctl()). Reading the code does not help me to find the bug. -> ->Kris -> ->----- ->(ASP) Microsoft Corporation (MSFT) announced today that the release of its ->productivity suite, Office 2000, will be delayed until the first quarter ->of 1901. -> -- ____________________________________________________________________ Emmanuel DELOGET [pixel] pixel@{dotcom.fr,epita.fr} ---- DotCom SA Windows 2000 is a trademark of... Bob Kerstein [www.windows2000.com] -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 8:13:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (Postfix) with SMTP id 4ECB014FFE for ; Wed, 3 Mar 1999 08:12:13 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id LAA05616; Wed, 3 Mar 1999 11:11:46 -0500 Date: Wed, 3 Mar 1999 11:11:46 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@freebsd.org Subject: Moving on and check out my .sig 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 First off, as of March 15th my new address is rminnich@acl.lanl.gov I don't know if my current employer will forward, so if any of you need to contact me there is the place. Note my .sig. 49.7 days is how long it takes a 32-bit millisecond counter to roll over to zero. It's kind of hilarious that nobody seems to have had windows up that long until now. I'm off this list for a while so if you want me to see it cc me. I'll be putting up clustering wares as I develop them on my new web page, and some of the old SRC stuff (netexec, mnfs, etc.) will also reappear. Also some never-released stuff will I hope make it out, e.g. a parallel debugger. At some point I suppose www.acl.lanl.gov/~rminnich will start to work. ron Ron Minnich |A bizarre and probably obscure bug will crash some Windows rminnich@sarnoff.com|computers after about a month and a half of use. (news.com) (609)-734-3120 | [I guess it is bizarre for windows to stay up 49 days] ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 8:13:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 06E6A1551E for ; Wed, 3 Mar 1999 08:12:50 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA09134; Wed, 3 Mar 1999 08:12:01 -0800 (PST) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdol9125; Wed Mar 3 16:11:52 1999 Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id IAA96563; Wed, 3 Mar 1999 08:11:35 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199903031611.IAA96563@whistle.com> Subject: Invitation to participate in Open Source NILO project (fwd) To: freebsd-hackers@FreeBSD.ORG Date: Wed, 3 Mar 1999 08:11:34 -0800 (PST) Cc: ken@nlc.net.au X-Mailer: ELM [version 2.4ME+ PL29 (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 Ken asked me to forward this to the FreeBSD project. He is the main force behind the Etherboot package that I made a port of to boot FreeBSD a.out & ELF kernels. It appears to be GPL'd. It looks like an interesting project. Doug A. ----- Forwarded message from Ken Yap ----- [Hi Doug, I believe you are on some FreeBSD lists. Would you be kind enough to forward this to those lists? TIA, Ken] NLnet is pleased to announce that the NILO (Network Interface LOader) project has commenced in February 1999 with Rob Savoye, of welcomehome.org, as the project contractor. The NILO project has the goal of developing Open Source Software for network booting ROMs based on Linux network adaptor drivers. The resulting ROMs will be able to boot operating systems such as Linux, FreeBSD and Windows. It will support the Intel PXE (Preboot Execution Environment) specification. The project will run until October 1999. For further details please visit the NILO home page at http://www.nilo.org/ The NILO project invites the Open Source community to actively participate in NILO development by joining the NILO developers mailing list and providing feedback on the documents and software releases as they appear on the web site. Details of how to subscribe are on the NILO web page. The NLnet foundation, started in 1982, is the principal founder of global area networking in Europe, in what is called today the Internet. NLnet originates from initiatives taken from the Unix (tm) community and is fully non-profit. Currently NLnet funds network technology projects to stimulate electronic information exchange, mainly on the Internet. See the home page at http://www.nlnet.nl Ken ----- End of forwarded message from Ken Yap ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 8:23:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep03-svc.tin.it (mta03-acc.tin.it [212.216.176.34]) by hub.freebsd.org (Postfix) with ESMTP id A0A2814F05 for ; Wed, 3 Mar 1999 08:23:47 -0800 (PST) (envelope-from paipai@box4.tin.it) Received: from winworkstation ([212.216.234.69]) by fep03-svc.tin.it (InterMail v4.0 201-221-105) with SMTP id <19990303162323.MYQU26875.fep03-svc@winworkstation> for ; Wed, 3 Mar 1999 17:23:23 +0100 From: "Paolo Di Francesco" To: freebsd-hackers@FreeBSD.ORG Date: Wed, 3 Mar 1999 17:31:11 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: menuconfig References: In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990303162323.MYQU26875.fep03-svc@winworkstation> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 2 things you'll need to take into account for usablity: > > for users: the ability to suck in a local config file > And an help system. Something that helps you when you don't know what to choose. Not just a raw help, but more an help assistant. The concept is: the developer writes a new feature in the kernel. He must provide the help file which describes that feature, and with the appropriate format, that file will plugged in the configuration assistant in 5 minutes. Ciao Ciao Paolo Di Francesco _ ->B<- All Recycled Bytes Message ... ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 12: 1:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id 3044215096 for ; Wed, 3 Mar 1999 12:01:19 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id MAA29947; Wed, 3 Mar 1999 12:01:10 -0800 (PST) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id MAA22910; Wed, 3 Mar 1999 12:01:01 -0800 (PST) Message-ID: <19990303120101.A21432@proxydev.inktomi.com> Date: Wed, 3 Mar 1999 12:01:01 -0800 From: John Plevyak To: Terry Lambert , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads References: <19990301091105.B21935@tsdev.inktomi.com> <199903020312.UAA21878@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903020312.UAA21878@usr01.primenet.com>; from Terry Lambert on Tue, Mar 02, 1999 at 03:12:35AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 02, 1999 at 03:12:35AM +0000, Terry Lambert wrote: > > Alternatively, if one can ensure that the p_leader does not > > die before the peers, then one can preserve the locking code > > and refraim from changing the proc strucure since one can > > simply pass p->p_leader down to the locking code. Since for > > unthreaded programs p == p->p_leader this yields very simple > > code for both cases. > > I think you can do this by recursing on the peers in the middle > of handling the kill before you pass it to the trampoline (then > it's too late). Why is it too late after that? In the patch I did the wait in exit1() right after the 'kill' of the peers. /* are we a task leader? */ if(p == p->p_leader) { struct kill_args killArgs; killArgs.signum = SIGKILL; q = p->p_peers; while(q) { killArgs.pid = q->p_pid; /* * The interface for kill is better * than the internal signal */ kill(p, &killArgs); nq = q; q = q->p_peers; } ** while (p->p_peers) ** tsleep((caddr_t)p, PWAIT, "exit1", 0); } This seemed to work. The peers signal when they take themselves off the list farther down in exit1, after the fdfree() call which can result in the close and which would benefit from having the p_leader still around. > > > > Moreover, this change enables other such threading problems to be fixed > > because logically 'process-type' state can be stored in > > p->p_leader->foo and logically 'thread-type' state can be stored > > in p->foo. > > > > (this is the change I chose) > > Really, the thread specific data needs to be seperated from the > proc struct; that is, the p->p_leader->foo should become meaningless. > > Basically, the litany on this is "everything that can differ between > threads". You are very right. In the short term it might be best to separate the parts of 'struct proc' which are thread specific from those which are process specific. The process specific parts can then always be accessed via 'p->p_leader' which would amount to 't->t_proc' when at some future time these two structures can be unwoven. > > > > > POSIX is very explicit, that the first close on a file within a single > > > process results in the locks being deasserted. > > > > > > I think that your patches fail to address this issue, since in reality, > > > I believe that you want to treat each thread as if it were a seperate > > > process for the purpose of specifying POSIX close semantics. > > > > The patch does in fact handle this case. The first closing > > thread with pass p->p_leader into the VOP_ADVLOCK and cause the lock > > to be released. > > > > In the current system, only if the original thread which obtained > > the lock was the first to close it would the lock be released. > > I'm confused about the semantics you desire, I think. My opinion > would be that the POSIX close/unlock coupling is highly undesirable > in general, and that you would want the threads to compete as if > they were processes for the semantics. > > I think this would depends on the lock scoping? E.g.: > > PTHREAD_PROCESS_PRIVATE > PTHREAD_PROCESS_SHARED > > ? I would need to read the spec on this. PTHREAD_PROCESS_SHARED/PRIVATE I have only seen applied to mutexes. While I can see the benefit to having the same semantic options for file locks, I don't see how to set them. I can find no pthread_attr_file_lock_setpshared() call. > > > > I understand the problem for NFS locking, but for threaded programs > > it would seem that lock shadowing would be the desired behavior > > The program is logically one process, and the lock ranges are > > shared state, not thread-specific state. > > I think the POSIX semantics, since they predate threads, can be > reasonably interpreted either way. > > However, the use that you described seemed to want to scope file > descriptors to a particular thread, such that a thread exit would > result in the close. I don't think this is reasonable (the descriptor > space is shared between all threads in a process). The only way > to reasonably achieve such scoping is pthread_cleanup_push(). Actually, the opposite. What I would like is for file locks to have process scope so that (for example) one thread could open the file, a second could take out the lock, and a third could close it, and the lock would be released. Currently the lock is left hanging past when the process exits. I understand that generally signalling and threads is a bit messed up, but I (somewhat urgently) have to solve the smaller problem of file locking being broken for programs which use kernel threads. In any case, FreeBSD should not be leaving the lock lying around past when the process/thread which originated it died. That is clearly a bug. I would like to get some patch into the FreeBSD source since this is going to be an issue for production sites which would likely prefer a 'blessed' solution rather than my personal patch. There are a number of possible solutions including the patch I proposed, using a seperate id (rpid), adding additional bookkeeping to the open fds vector etc. However, I was hoping that by keeping the p_leader around, we could use it as the 'process' and migrate to a model of seperate threads and processes. That is what I am proposing. What do you think? john -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 13: 1:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7547E156BE for ; Wed, 3 Mar 1999 13:01:17 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IIlE-000IrF-00 for hackers@freebsd.org; Wed, 3 Mar 1999 23:00:56 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: ppp.h in contrib/libpcap and contrib/tcpdump Date: Wed, 03 Mar 1999 23:00:56 +0200 Message-ID: <72492.920494856@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, While trawling my buildworld output for warnings, I noticed that we have two identical copies of ppp.h in contrib/libpcap and contrib/tcpdump. If I were to try to get world to use only one ppp.h, where would I put that single file and would I wasting time in the light of historic holy wars? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 14:34:54 1999 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 B9F0714FFB for ; Wed, 3 Mar 1999 14:34:45 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id HAA01926; Thu, 4 Mar 1999 07:34:35 +0900 (JST) Message-ID: <36DDB131.630AF7F1@newsguy.com> Date: Thu, 04 Mar 1999 07:01:21 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Ron G. Minnich" Cc: hackers@FreeBSD.ORG Subject: Re: Moving on and check out my .sig References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ron G. Minnich" wrote: > > Note my .sig. 49.7 days is how long it takes a 32-bit millisecond counter > to roll over to zero. It's kind of hilarious that nobody seems to have had > windows up that long until now. What's worse is that this problem looks obvious. I wonder if whoever was responsible for this part of the code did not simply think along the line "Windows running for 49 days straight? Get real!" -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 14:39:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 088CC15735 for ; Wed, 3 Mar 1999 14:39:27 -0800 (PST) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id RAA25476 for ; Wed, 3 Mar 1999 17:39:07 -0500 (EST) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 03 Mar 1999 17:39:50 -0500 (EST) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: freebsd-hackers@freebsd.org Subject: Adaptec 2930U2 NOT supported Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that the Adaptec 2930U2 is NOT supported. It is 7890-based. The 2940U2 is supported. The PCI vendor id is, of course, 0x9005, and the device id is 0x0011. The 2940U2 has an id of 0x0010. Is there any plans to support the 2930U2 (which I bought today)? -------------------------------------------------------------------- Mark J. Taylor Networking Research Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (734) 668-2567 Ann Arbor, MI 48108 FAX (734) 668-8780 http://www.cybernet.com/ -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 14:56:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id C680E15786 for ; Wed, 3 Mar 1999 14:55:16 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id XAA32433; Wed, 3 Mar 1999 23:49:29 +0100 (CET) Message-Id: <199903032249.XAA32433@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Christoph Kukulies Cc: hackers@FreeBSD.ORG, garyj@peedub.muc.de Subject: Re: brandelf (necessary?) Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 03 Mar 1999 09:50:59 +0100." <199903030850.JAA26515@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Mar 1999 23:49:29 +0100 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies writes: >In an environment where FreeBSD needs to run linux binaries >that are shared with linux systems, would it do harm to brandelf >these binaries? Or in other words, would it be possible for FreeBSD >to autodetect that it's a linux ELF binary without having to brand it? > as long as the linuxulator is loaded (linux.ko) it does not seem to be necessary to brandelf Linux binaries. At least, that's been my experience. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 15: 1:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id B1DBE157B2 for ; Wed, 3 Mar 1999 15:01:04 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id WAA19551; Wed, 3 Mar 1999 22:06:20 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00637; Wed, 3 Mar 1999 08:15:07 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903030815.IAA00637@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Jim Durham Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: natd core dumps in packetBuf In-reply-to: Your message of "Tue, 02 Mar 1999 23:31:05 EST." <199903030431.XAA08604@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Mar 1999 08:15:06 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, that's a pretty strange trace ! > On a 3.0-RELEASE system, I've had problems with > natd core dumping. I compiled it with -g and > was able to run gdb with symbols in the last > dump. > > Here's what I see... > > GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc. > Core was generated by `natd'. > Program terminated with signal 11, Segmentation fault. > #0 0x280aca00 in ?? () > (gdb) file natd > Reading symbols from natd...done. > (gdb) where > #0 0x280aca00 in ?? () > #1 0x804c6c9 in packetBuf () > #2 0x280570fd in ?? () > #3 0x2805722d in ?? () > #4 0x28056298 in ?? () > #5 0x280569ee in ?? () > #6 0x804977a in DoAliasing (fd=3) at natd.c:492 > #7 0x8049503 in main (argc=3, argv=0xefbfd7c4) at natd.c:348 > #8 0x8048ea5 in _start () $ fgrep packetBuf /usr/src/usr.sbin/natd/*.c | head -1 /usr/src/usr.sbin/natd/natd.c:static char packetBuf[IP_MAXPACKET]; Try removing the core and building libalias with symbols too. It may produce interesting results - packetBuf is passed into the alias routines, so it's not impossible that it *is* trying to execute it :-/ > Any ideas? > > regards, > Jim Durham -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 18:19:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 06A9D14C40 for ; Wed, 3 Mar 1999 18:19:44 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.2/8.8.8) with SMTP id KAA21759; Thu, 4 Mar 1999 10:19:25 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id KAA26249; Thu, 4 Mar 1999 10:19:24 +0800 Message-Id: <199903040219.KAA26249@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@freebsd.org Cc: shocking@bandicoot.prth.tensor.pgs.com Subject: Re: Panic in FFS/4.0 as of yesterday - update In-reply-to: Your message of "Wed, 03 Mar 1999 08:13:39 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Mar 1999 10:19:24 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > MUSBUS is now quite old - I believe it was developed around 1981. I > have a paper Ken McDonell presented at AUUG'91 when he discussed some > of its shortcomings at that time [and there are probably more now]. > > I've also heard him state (possibly during that presentation) that > MUSBUS was designed to benchmark systems around 1 MIPS (ie a VAX > 11/780), and results obtained on a `current' (ie 5-10 years old now) > system probably reflect bottlenecks in MUSBUS, rather than the system > under test. > Yeah - remember porting this beast to Microport V.2, back on an old 286. Needed some explicit (char *) casts as I recall (sizeof int != sizeof ptr). Now with the 64 bit CPUs, we're seeing those problems again... Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 20: 7:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A5AB14DE2 for ; Wed, 3 Mar 1999 20:07:53 -0800 (PST) (envelope-from smurf@CSUA.Berkeley.EDU) Received: from soda.CSUA.Berkeley.EDU (localhost [127.0.0.1]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id UAA16340; Wed, 3 Mar 1999 20:07:18 -0800 (PST) env-from (smurf@CSUA.Berkeley.EDU) Message-Id: <199903040407.UAA16340@soda.CSUA.Berkeley.EDU> To: abial@nask.pl Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD and ThinkPad Date: Wed, 03 Mar 1999 20:07:17 -0800 From: Scott MacFiggen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The symptoms are as follows: sometime during the probing, or even later if >I'm active enough pressing keys (see below) the machine hangs, and never >recovers. I suspect it's somehow related to energy saving features - >perhaps it just decides to go to sleep? Anyway, after this I'm totally >unable to reboot it. The funny thing is that ThinkPad doesn't have the >reset button, so I have to pull out the battery in order to reboot it... >:-) > >Perhaps someone already went through this, and can give me a hint... TIA. >Oh, BTW - the BIOS setup on this really sucks, it's a winblows oriented >dummy icons which really don't give you any control over the details. Thinkpads (600's and 560's anyway) have problems like this.. Try this, rebuild the kernel and set the MAXMEM option to TotalMem-4M. ie: If you have 128 meg in your laptop, set it to options "MAXMEM=(128*1024-4096)" or something like that.. -Scott PS: There are a bunch of websites that talk about freebsd and Thinkpads... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 22:18:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from yoshi.iq.org (yoshy.iq.org [203.4.184.224]) by hub.freebsd.org (Postfix) with ESMTP id 48A0E14D4D for ; Wed, 3 Mar 1999 22:18:01 -0800 (PST) (envelope-from proff@yoshi.iq.org) Received: (from proff@localhost) by yoshi.iq.org (8.8.8/8.8.8) id RAA19892; Thu, 4 Mar 1999 17:17:16 +1100 (EST) To: cgd@netbsd.org (Chris G. Demetriou) Cc: Ignatios Souvatzis , tech-misc@netbsd.org, tech-userlevel@netbsd.org, tech-kern@netbsd.org, freebsd-hackers@freebsd.org Subject: Re: htonq References: <199903030130.MAA17738@yoshi.iq.org> <87pv6r8igu.fsf@redmail.redback.com> <19990303124920.B7027@cs.uni-bonn.de> <87hfs25ncv.fsf@redmail.redback.com> Cc: proff@iq.org From: Julian Assange Date: 04 Mar 1999 17:17:13 +1100 In-Reply-To: cgd@netbsd.org's message of "03 Mar 1999 12:28:48 -0800" Message-ID: Lines: 19 User-Agent: Gnus/5.070066 (Pterodactyl Gnus v0.66) XEmacs/20.4 (Emerald) Mime-Version: 1.0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cgd@netbsd.org (Chris G. Demetriou) writes: > do any other OSes do something w.r.t. hton and ntoh for 64-bit > integers? i'm pretty sure Digital UNIX does, but i don't recall what > it is... linux has hton64 / ntoh64 inside the kernel (though not in user land). if past behavior is any indicator this means that everyone else does something completely different :) hton64 is certainly more meaningful, though htonq is more in keeping with tradition, and printf's %q -- Julian Assange http://iq.org/~proff Man is quite insane. He wouldn't know how to create a maggot and he creates Gods by the dozen. - Michel de Montaigne, _Essais_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 3 23:59:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 7692214DA4 for ; Wed, 3 Mar 1999 23:59:27 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id AAA92777; Thu, 4 Mar 1999 00:59:06 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903040759.AAA92777@panzer.plutotech.com> Subject: Re: Adaptec 2930U2 NOT supported In-Reply-To: from "Mark J. Taylor" at "Mar 3, 1999 5:39:50 pm" To: mtaylor@cybernet.com Date: Thu, 4 Mar 1999 00:59:06 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark J. Taylor wrote... > > It seems that the Adaptec 2930U2 is NOT supported. It is 7890-based. > > The 2940U2 is supported. > > The PCI vendor id is, of course, 0x9005, and the device id is 0x0011. Believe it or not, Adaptec has two PCI vendor IDs (0x9004 and 0x9005). Their newer Ultra-2 chips use 0x9005, and their older Ultra chips use 0x9004. > The 2940U2 has an id of 0x0010. > > > Is there any plans to support the 2930U2 (which I bought today)? Try adding the PCI ID into the PCI probe/attach code in the Adaptec driver (sys/pci/ahc_pci.c). (in ahc_probe(), stick it in the same case as the 2940U2.) My guess is that it will work okay. I think that the fact that it isn't supported is just an oversight. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 1:32:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from krdl.org.sg (rodin.krdl.org.sg [137.132.252.27]) by hub.freebsd.org (Postfix) with ESMTP id 8993114E9E for ; Thu, 4 Mar 1999 01:31:42 -0800 (PST) (envelope-from joerg@mailbox.iss.nus.sg) Received: from mailhost.krdl.org.sg (mailbox.krdl.org.sg [137.132.247.30]) by krdl.org.sg (8.9.2/8.9.2) with ESMTP id RAA00292 for ; Thu, 4 Mar 1999 17:37:22 +0800 (SGT) Received: from negara.nus.sg (negara [137.132.248.175]) by mailhost.krdl.org.sg (8.9.2/8.9.2) with ESMTP id RAA16797 for ; Thu, 4 Mar 1999 17:31:07 +0800 (SGT) Received: (from joerg@localhost) by negara.nus.sg (8.9.1b+Sun/8.9.1) id RAA13157 for freebsd-hackers@freebsd.org; Thu, 4 Mar 1999 17:34:07 +0800 (SGT) Message-ID: <19990304173407.O12467@krdl.org.sg> Date: Thu, 4 Mar 1999 17:34:07 +0800 From: "Joerg B. Micheel" To: freebsd-hackers@freebsd.org Subject: Need a cdevsw major number Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Kent Ridge Digital Labs, Singapore Project: SingAREN, the Singapore Advanced Research and Education Network Operating-System: ... drained by Solaris 7 Intel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi hackers, I'd need a character device major number for a driver I have written. I got permission to share with the public. It needs to be: NNN dag University of Waikato DAG network capture boards Thanks! Joerg -- Joerg B. Micheel Email: SingAREN Technology Center Phone: +65 8742582 Kent Ridge Digital Labs, Rm 3-65, C041 Fax: +65 7744990 21 Heng Mui Keng Terrace Pager: +65 96016020 Singapore 119613 Plan: Troubleshooting ATM Republic of Singapore Networks and Applications To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 1:59:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2969014EBD for ; Thu, 4 Mar 1999 01:58:46 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IUtg-0008bC-00 for hackers@freebsd.org; Thu, 4 Mar 1999 11:58:28 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: BIOS reboot question from Linux user Date: Thu, 04 Mar 1999 11:58:28 +0200 Message-ID: <33057.920541508@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, The following question is cluttering up the GNATS database (misc/5552): | I found out today that the Linux parameter of append reboot=bios | (which passes the reboot=bios) is unavailable under FreeBSD. Is this | correct? The keyboard fix in the kernel does not fix my problem, and | the machine still does not reboot. | | Is there a way to tell the machine to reboot via the bios? I don't understand what this chap's talking about and wondered if anyone here with an understanding of how the referenced Linux option works. Does reboot(8) use the BIOS code for rebooting? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 3:47:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 7BED114D25 for ; Thu, 4 Mar 1999 03:47:36 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id DAA01089 for hackers@FreeBSD.org; Thu, 4 Mar 1999 03:47:34 -0800 (PST) (envelope-from ulf) Message-ID: <19990304034734.A322@TelcoSucks.org> Date: Thu, 4 Mar 1999 03:47:34 -0800 From: Ulf Zimmermann To: hackers@FreeBSD.org Subject: vm problems in 3.1-RELEASE and -STABLE Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Langsam habe ich die schnauze voll (for the ones who know german) This machine is a AMD K6-233 with 128MB, Adaptec 2940UW, Brooktree 848, Intel fxp, SB16 PnP. This machine was running 3.0-BETA for > 70 days. As soon I upgraded to 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with wire count already 0, for which Jordan took the panic out. But I am still getting other panics, like page fault. I have several core dumps. If anyone wants to look at them, please contact me. (I am otherwise close to go back to 3.0R). -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 4:52:40 1999 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 2B08C14EBC for ; Thu, 4 Mar 1999 04:52:37 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id MAA28821; Thu, 4 Mar 1999 12:52:19 GMT (envelope-from rb@gid.co.uk) Received: from localhost by seagoon.gid.co.uk; Thu, 4 Mar 1999 12:43:13 GMT Date: Thu, 4 Mar 1999 12:43:12 +0000 (GMT) From: Bob Bishop X-Sender: rb@seagoon To: Ulf Zimmermann Cc: hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE In-Reply-To: <19990304034734.A322@TelcoSucks.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 Thu, 4 Mar 1999, Ulf Zimmermann wrote: > Langsam habe ich die schnauze voll (for the ones who know german) > > This machine is a AMD K6-233 with 128MB, Adaptec 2940UW, Brooktree 848, > Intel fxp, SB16 PnP. > > This machine was running 3.0-BETA for > 70 days. As soon I upgraded to > 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with > wire count already 0, for which Jordan took the panic out. But I am still > getting other panics, like page fault. > > I have several core dumps. If anyone wants to look at them, please contact > me. (I am otherwise close to go back to 3.0R). Have a look at kern/10376 in case there's any common factor (but I doubt it). -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 5:33: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (Postfix) with ESMTP id 3F0B914F95 for ; Thu, 4 Mar 1999 05:32:11 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id MAA12363; Thu, 4 Mar 1999 12:42:55 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 4 Mar 1999 12:42:54 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Scott MacFiggen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad In-Reply-To: <199903040407.UAA16340@soda.CSUA.Berkeley.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 Wed, 3 Mar 1999, Scott MacFiggen wrote: > Thinkpads (600's and 560's anyway) have problems like this.. > Try this, rebuild the kernel and set the MAXMEM option > to TotalMem-4M. ie: > > If you have 128 meg in your laptop, set it to > > options "MAXMEM=(128*1024-4096)" > or something like that.. > > > -Scott > > PS: There are a bunch of websites that talk about > freebsd and Thinkpads... Thanks to all that replied! I'll try to apply your advices. and we'll see.. :-) Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | 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 Thu Mar 4 6: 1:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fsfw.freesoft.hu (fsfw.freesoft.hu [195.228.127.1]) by hub.freebsd.org (Postfix) with ESMTP id AF46614F30 for ; Thu, 4 Mar 1999 06:00:53 -0800 (PST) (envelope-from dbeck@freesoft.hu) Received: (from postmaster@localhost) by fsfw.freesoft.hu (8.7.5/8.7.3) id PAA03914 for ; Thu, 4 Mar 1999 15:00:51 +0100 X-Authentication-Warning: fsfw.freesoft.hu: postmaster set sender to using -f From: dbeck@freesoft.hu (David Beck) To: Subject: Upgrade to 3.x Date: Thu, 4 Mar 1999 15:00:13 +0100 Message-Id: <71FD97AF0B5ED2118FD600E0292558180FC54F@msserv.exchange.freesoft.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya Dear Hackers, I've just upgraded my system to 3.0-rel from 2.2.7 and ran into a bit of a problem: I found that due the crypt algorythm change I can't login any more. Finally I managed to logon and could fix my password, but what can I do with the other users passwords ? The same problem happend to me with the apache passwords... I thought you might have an idea... Thx in advance, David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 6: 7:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id EA2F914E85 for ; Thu, 4 Mar 1999 06:06:52 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10IYl0-0008yW-00; Thu, 4 Mar 1999 16:05:46 +0200 From: Sheldon Hearn To: dbeck@freesoft.hu (David Beck) Cc: freebsd-hackers@freebsd.org Subject: Re: Upgrade to 3.x In-reply-to: Your message of "Thu, 04 Mar 1999 15:00:13 +0100." <71FD97AF0B5ED2118FD600E0292558180FC54F@msserv.exchange.freesoft.hu> Date: Thu, 04 Mar 1999 16:05:46 +0200 Message-ID: <34503.920556346@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Mar 1999 15:00:13 +0100, David Beck wrote: > I found that due the crypt algorythm change I can't login any more. That change has been backed out since then because of exactly this problem. Hard luck. :( > Finally I managed to logon and could fix my password, but what can > I do with the other users passwords ? The same problem happend to me > with the apache passwords... Don't change them, rather fix the problem by upgrading to 3.1-STABLE. I know that's not what you wanna hear, but the only alternative is to have _everyone_ change his/her password. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 6: 7:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bayer2.bayer-ag.de (bayer2.bayer-ag.de [194.120.191.2]) by hub.freebsd.org (Postfix) with SMTP id E0CA414FDF; Thu, 4 Mar 1999 06:07:44 -0800 (PST) (envelope-from ANDREAS.KLEMM.AK@bayer-ag.de) Received: by bayer2.bayer-ag.de id PAA13370 (SMTP Gateway 3.0); Thu, 4 Mar 1999 15:07:25 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-2); Thu, 4 Mar 1999 15:07:25 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-1); Thu, 4 Mar 1999 15:07:25 +0100 From: ANDREAS.KLEMM.AK@bayer-ag.de To: " - (052)dg(a)FreeBSD.ORG" , " - (052)dillon(a)FreeBSD.ORG" Cc: " - (052)hackers(a)FreeBSD.ORG" , " - (052)hardware(a)FreeBSD.ORG" Subject: FreeBSD 2.2.8-STABLE: which fast ethernet card, which is ava Message-Id: <0006800009221765000002L052*@MHS> Date: Thu, 4 Mar 1999 14:46:43 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG =0AHi ! Please help, it burns. Could you please tell me, what Ethernet Card is currently best supported by FreeBSD 2.2.8-STABLE ? The tx0 driver as it is now, seems to suck a lot. I have nothing than p= roblems. My collegue just lost a vi session and lost two hours of work. I have t= o get rid of the SMC PCI network card. But, which card can I buy ??? I wanted to have an Intel Etherexpress Pr= o/100B, but when I look on intels webpage, they only have new cards with 82558 = and 82559 chipset ... Well, what rocks for FreeBSD 2.2.8, what is available now ?= ?? It*%s really urgent, I*%d appreciate any kind of help, many thanks ... Andreas ///= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 6:13:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fsfw.freesoft.hu (fsfw.freesoft.hu [195.228.127.1]) by hub.freebsd.org (Postfix) with ESMTP id C129C14E85 for ; Thu, 4 Mar 1999 06:13:52 -0800 (PST) (envelope-from dbeck@freesoft.hu) Received: (from postmaster@localhost) by fsfw.freesoft.hu (8.7.5/8.7.3) id PAA04051; Thu, 4 Mar 1999 15:13:50 +0100 X-Authentication-Warning: fsfw.freesoft.hu: postmaster set sender to using -f From: dbeck@freesoft.hu (David Beck) To: "'Sheldon Hearn'" Cc: Subject: RE: Upgrade to 3.x Date: Thu, 4 Mar 1999 15:13:03 +0100 Message-Id: <71FD97AF0B5ED2118FD600E0292558180FC550@msserv.exchange.freesoft.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: <34503.920556346@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Don't change them, rather fix the problem by upgrading to 3.1-STABLE. I >know that's not what you wanna hear, but the only alternative is to have >_everyone_ change his/her password. OK, I will upgrade then. Thanx, David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 8: 4:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id C0C7C14EEA for ; Thu, 4 Mar 1999 08:04:51 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from tsdev.inktomi.com (tsdev.inktomi.com [209.1.32.119]) by mercury.inktomi.com (8.9.1a/8.9.1) with SMTP id IAA12409; Thu, 4 Mar 1999 08:04:43 -0800 (PST) Received: by tsdev.inktomi.com (SMI-8.6/SMI-SVR4) id IAA12072; Thu, 4 Mar 1999 08:04:33 -0800 Message-ID: <19990304080433.B12042@tsdev.inktomi.com> Date: Thu, 4 Mar 1999 08:04:33 -0800 From: John Plevyak To: ajit@inktomi.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Adaptec 2930U2 NOT supported References: <199903040759.AAA92777@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903040759.AAA92777@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Mar 04, 1999 at 12:59:06AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Humm.... I could build you a custom installation disk with this change... What was the problem with the IBM machine again? On Thu, Mar 04, 1999 at 12:59:06AM -0700, Kenneth D. Merry wrote: > Mark J. Taylor wrote... > > > > It seems that the Adaptec 2930U2 is NOT supported. It is 7890-based. > > > > The 2940U2 is supported. > > > > The PCI vendor id is, of course, 0x9005, and the device id is 0x0011. > > Believe it or not, Adaptec has two PCI vendor IDs (0x9004 and 0x9005). > Their newer Ultra-2 chips use 0x9005, and their older Ultra chips use > 0x9004. > > > The 2940U2 has an id of 0x0010. > > > > > > Is there any plans to support the 2930U2 (which I bought today)? > > Try adding the PCI ID into the PCI probe/attach code in the Adaptec > driver (sys/pci/ahc_pci.c). (in ahc_probe(), stick it in the same case as > the 2940U2.) My guess is that it will work okay. > > I think that the fact that it isn't supported is just an oversight. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 8:47:36 1999 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 E81BD14FFF; Thu, 4 Mar 1999 08:47:33 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id LAA26211; Thu, 4 Mar 1999 11:50:00 -0500 (EST) Message-Id: <199903041650.LAA26211@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 04 Mar 1999 11:58:57 -0500 To: hackers@freebsd.org From: Dennis Subject: 3.1 benchmarks? Cc: isp@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 Has anyone done any controlled tests between 2.2 and 3.1 systems regarding network performance? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 9:33:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AAC1B15096 for ; Thu, 4 Mar 1999 09:33:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA30220; Thu, 4 Mar 1999 09:33:25 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 09:33:25 -0800 (PST) From: Matthew Dillon Message-Id: <199903041733.JAA30220@apollo.backplane.com> To: Bob Bishop Cc: Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, 4 Mar 1999, Ulf Zimmermann wrote: : :> Langsam habe ich die schnauze voll (for the ones who know german) :> :> This machine is a AMD K6-233 with 128MB, Adaptec 2940UW, Brooktree 848, :> Intel fxp, SB16 PnP. :> :> This machine was running 3.0-BETA for > 70 days. As soon I upgraded to :> 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with :> wire count already 0, for which Jordan took the panic out. But I am still :> getting other panics, like page fault. Someone took a panic out in the VM system? Where? :> I have several core dumps. If anyone wants to look at them, please contact :> me. (I am otherwise close to go back to 3.0R). : :Have a look at kern/10376 in case there's any common factor (but I doubt :it). : :-- :Bob Bishop +44 118 977 4017 :rb@gid.co.uk fax +44 118 989 4254 -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 Mar 4 10:48:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bangkok.office.cdsnet.net (bangkok.office.cdsnet.net [204.118.245.23]) by hub.freebsd.org (Postfix) with ESMTP id 49FDE14BCC for ; Thu, 4 Mar 1999 10:47:55 -0800 (PST) (envelope-from cts@bangkok.office.cdsnet.net) Received: (from cts@localhost) by bangkok.office.cdsnet.net (8.8.8/8.8.5) id KAA27000; Thu, 4 Mar 1999 10:47:36 -0800 (PST) Date: Thu, 4 Mar 1999 10:47:36 -0800 (PST) Message-Id: <199903041847.KAA27000@bangkok.office.cdsnet.net> X-Authentication-Warning: bangkok.office.cdsnet.net: cts set sender to cts@bangkok.office.cdsnet.net using -f MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Craig Spannring To: freebsd-hackers@FreeBSD.ORG Subject: Proposed change to telnet(1). X-Mailer: VM 6.31 under Emacs 20.3.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometimes it would be nice to be able to specify which outbound interface telnet should bind to. I propose adding a '-I interface' option to telnet. It would work like- telnet -I 192.168.0.10 somehost.mydomain.net That would make the telnet client bind to the outbound IP address of 192.168.0.10 provided of course the client has an interface configured to that IP. Here are patches that implement this feature. >--- cut here ---< diff -c -r telnet/commands.c telnet.new/commands.c *** telnet/commands.c Thu Mar 4 10:29:45 1999 --- telnet.new/commands.c Thu Mar 4 10:26:51 1999 *************** *** 2100,2113 **** char *argv[]; { register struct hostent *host = 0; struct sockaddr_in sin; struct servent *sp = 0; unsigned long temp; #if defined(IP_OPTIONS) && defined(IPPROTO_IP) char *srp = 0, *strrchr(); unsigned long sourceroute(), srlen; #endif ! char *cmd, *hostp = 0, *portp = 0, *user = 0; /* clear the socket address prior to use */ bzero((char *)&sin, sizeof(sin)); --- 2100,2115 ---- char *argv[]; { register struct hostent *host = 0; + struct hostent *interface; struct sockaddr_in sin; + struct sockaddr_in interface_sin; struct servent *sp = 0; unsigned long temp; #if defined(IP_OPTIONS) && defined(IPPROTO_IP) char *srp = 0, *strrchr(); unsigned long sourceroute(), srlen; #endif ! char *cmd, *hostp = 0, *portp = 0, *user = 0, *interfacep = 0; /* clear the socket address prior to use */ bzero((char *)&sin, sizeof(sin)); *************** *** 2143,2148 **** --- 2145,2158 ---- autologin = 1; continue; } + if (strcmp(*argv, "-I") == 0) { + --argc; ++argv; + if (argc == 0) + goto usage; + interfacep = *argv++; + --argc; + continue; + } if (hostp == 0) { hostp = *argv++; --argc; *************** *** 2154,2160 **** continue; } usage: ! printf("usage: telnet [-l user] [-a] host-name [port]\n"); setuid(getuid()); return 0; } --- 2164,2170 ---- continue; } usage: ! printf("usage: telnet [-l user] [-a] [-I interface] host-name [port]\n"); setuid(getuid()); return 0; } *************** *** 2284,2289 **** --- 2294,2334 ---- if (debug && SetSockOpt(net, SOL_SOCKET, SO_DEBUG, 1) < 0) { perror("setsockopt (SO_DEBUG)"); } + + if (interfacep) { + bzero((char *)&interface_sin, sizeof(interface_sin)); + + temp = inet_addr(interfacep); + if (temp != INADDR_NONE) { + interface_sin.sin_addr.s_addr = temp; + interface_sin.sin_family = AF_INET; + interface_sin.sin_port = htons(0); + } else { + interface = gethostbyname(interfacep); + if (interface) { + interface_sin.sin_family = interface->h_addrtype; + #if defined(h_addr) /* In 4.3, this is a #define */ + memmove((caddr_t)&interface_sin.sin_addr, + interface->h_addr_list[0], + MIN(interface->h_length, sizeof(interface_sin.sin_addr))); + #else /* defined(h_addr) */ + memmove((caddr_t)&interface_sin.sin_addr, interface->h_addr, + MIN(interface->h_length, sizeof(interface_sin.sin_addr))); + #endif /* defined(h_addr) */ + interface_sin.sin_port = htons(0); + } else { + herror(interfacep); + setuid(getuid()); + return 0; + } + } + if (bind(net, (struct sockaddr *)&interface_sin, + sizeof (interface_sin)) == -1) { + perror("telnet: Unable to bind to specified interface"); + return 0; + } + } + if (connect(net, (struct sockaddr *)&sin, sizeof (sin)) < 0) { #if defined(h_addr) /* In 4.3, this is a #define */ diff -c -r telnet/main.c telnet.new/main.c *** telnet/main.c Thu Mar 4 10:29:46 1999 --- telnet.new/main.c Tue Mar 2 18:53:33 1999 *************** *** 81,91 **** fprintf(stderr, "Usage: %s %s%s%s%s\n", prompt, #ifdef AUTHENTICATION ! "[-8] [-E] [-K] [-L] [-S tos] [-X atype] [-a] [-c] [-d] [-e char]", ! "\n\t[-k realm] [-l user] [-f/-F] [-n tracefile] ", #else ! "[-8] [-E] [-L] [-S tos] [-a] [-c] [-d] [-e char] [-l user]", ! "\n\t[-n tracefile]", #endif #if defined(TN3270) && defined(unix) # ifdef AUTHENTICATION --- 81,91 ---- fprintf(stderr, "Usage: %s %s%s%s%s\n", prompt, #ifdef AUTHENTICATION ! "[-8] [-E] [-I interface] [-K] [-L] [-S tos] [-X atype] [-a] [-c]", ! "\n\t[-d] [-e char] [-k realm] [-l user] [-f/-F] [-n tracefile] ", #else ! "[-8] [-E] [-I interface] [-L] [-S tos] [-a] [-c] [-d]", ! "\n\t[-e char] [-l user] [-n tracefile]", #endif #if defined(TN3270) && defined(unix) # ifdef AUTHENTICATION *************** *** 113,119 **** extern char *optarg; extern int optind; int ch; ! char *user, *strrchr(); #ifdef FORWARD extern int forward_flags; #endif /* FORWARD */ --- 113,119 ---- extern char *optarg; extern int optind; int ch; ! char *user, *interface, *strrchr(); #ifdef FORWARD extern int forward_flags; #endif /* FORWARD */ *************** *** 131,141 **** prompt = argv[0]; user = NULL; rlogin = (strncmp(prompt, "rlog", 4) == 0) ? '~' : _POSIX_VDISABLE; autologin = -1; ! while ((ch = getopt(argc, argv, "8EKLNS:X:acde:fFk:l:n:rt:x")) != -1) { switch(ch) { case '8': eight = 3; /* binary output and input */ --- 131,142 ---- prompt = argv[0]; user = NULL; + interface = NULL; rlogin = (strncmp(prompt, "rlog", 4) == 0) ? '~' : _POSIX_VDISABLE; autologin = -1; ! while ((ch = getopt(argc, argv, "8EI:KLNS:X:acde:fFk:l:n:rt:x")) != -1) { switch(ch) { case '8': eight = 3; /* binary output and input */ *************** *** 219,224 **** --- 220,228 ---- prompt); #endif break; + case 'I': + interface = optarg; + break; case 'k': #if defined(AUTHENTICATION) && defined(KRB4) { *************** *** 283,289 **** argv += optind; if (argc) { ! char *args[7], **argp = args; if (argc > 2) usage(); --- 287,293 ---- argv += optind; if (argc) { ! char *args[8], **argp = args; if (argc > 2) usage(); *************** *** 291,296 **** --- 295,304 ---- if (user) { *argp++ = "-l"; *argp++ = user; + } + if (interface) { + *argp++ = "-I"; + *argp++ = interface; } *argp++ = argv[0]; /* host */ if (argc > 1) diff -c -r telnet/telnet.1 telnet.new/telnet.1 *** telnet/telnet.1 Thu Mar 4 10:29:48 1999 --- telnet.new/telnet.1 Tue Mar 2 18:53:33 1999 *************** *** 30,36 **** .\" SUCH DAMAGE. .\" .\" @(#)telnet.1 8.5 (Berkeley) 3/1/94 ! .\" $Id: telnet.1,v 1.10 1998/12/14 22:40:38 billf Exp $ .\" .Dd March 1, 1994 .Dt TELNET 1 --- 30,36 ---- .\" SUCH DAMAGE. .\" .\" @(#)telnet.1 8.5 (Berkeley) 3/1/94 ! .\" $Id: telnet.1,v 1.2 1999/03/03 02:53:33 cts Exp $ .\" .Dd March 1, 1994 .Dt TELNET 1 *************** *** 43,48 **** --- 43,49 ---- .Sh SYNOPSIS .Nm .Op Fl 8EFKLacdfrx + .Op Fl I Ar interface .Op Fl S Ar tos .Op Fl X Ar authtype .Op Fl e Ar escapechar *************** *** 87,92 **** --- 88,96 ---- option allows the local credentials to be forwarded to the remote system, including any credentials that have already been forwarded into the local environment. + .It Fl I Ar interface + Specify the IP address of the interface to bind to for + the outbound connection. .It Fl K Specifies no automatic login to the remote system. .It Fl L >--- cut here ---< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 11:29:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id B8991150C4 for ; Thu, 4 Mar 1999 11:29:36 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA195423683; Thu, 4 Mar 1999 13:54:43 -0500 Date: Thu, 4 Mar 1999 13:54:43 -0500 (EST) From: Bill Fumerola To: "Daniel C. Sobral" Cc: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: Moving on and check out my .sig In-Reply-To: <36DDB131.630AF7F1@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, 4 Mar 1999, Daniel C. Sobral wrote: > > Note my .sig. 49.7 days is how long it takes a 32-bit millisecond counter > > to roll over to zero. It's kind of hilarious that nobody seems to have had > > windows up that long until now. > > What's worse is that this problem looks obvious. I wonder if whoever > was responsible for this part of the code did not simply think along > the line "Windows running for 49 days straight? Get real!" A mentioned this to a few of my co-workers who responded, "what part of Windows". Is there a page that has the gory details somewhere? - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Mar 4 12: 5:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shattered.disturbed.net (shattered.disturbed.net [192.139.81.180]) by hub.freebsd.org (Postfix) with ESMTP id A510114ED8 for ; Thu, 4 Mar 1999 12:04:52 -0800 (PST) (envelope-from veers@disturbed.net) Received: from shattered.disturbed.net ([192.139.81.180]:33029 "EHLO shattered" ident: "IDENT-NONSENSE") by disturbed.net with ESMTP id <61621-272>; Thu, 4 Mar 1999 15:06:19 -0500 Date: Thu, 4 Mar 1999 15:06:17 -0500 (EST) From: Alex Perel To: David Beck Cc: freebsd-hackers@freebsd.org Subject: Re: Upgrade to 3.x In-Reply-To: <71FD97AF0B5ED2118FD600E0292558180FC54F@msserv.exchange.freesoft.hu> 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, 4 Mar 1999, David Beck wrote: > I found that due the crypt algorythm change I can't login any more. > > Finally I managed to logon and could fix my password, but what can > I do with the other users passwords ? The same problem happend to me > with the apache passwords... > > I thought you might have an idea... heh! I ran into this problem just yesterday, entirely due to my own neglegence. It's caused either by 1) not installing DES if the old setup was using DES 2) installing DES when the old setup was not.. What I did was reboot to single user mode, reset the root password, goto multiuser, and fetch the DES distribution (either with /stand/sysinstall or by hand). That solved it, I reset the root password AGAIN, and it works great now. Hope this helps. Alex G. Perel -=- AP5081 alexp@iplink.net -=- (work) veers@disturbed.net -=- (play) Disturbed Networks - Powered exclusively by 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 Mar 4 12:14:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 7F94C14CEA for ; Thu, 4 Mar 1999 12:14:32 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id MAA23672; Thu, 4 Mar 1999 12:14:15 -0800 (PST) (envelope-from ulf) Message-ID: <19990304121414.A3659@TelcoSucks.org> Date: Thu, 4 Mar 1999 12:14:14 -0800 From: Ulf Zimmermann To: Matthew Dillon , Bob Bishop Cc: Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE Reply-To: ulf@Alameda.net References: <199903041733.JAA30220@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903041733.JAA30220@apollo.backplane.com>; from Matthew Dillon on Thu, Mar 04, 1999 at 09:33:25AM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 09:33:25AM -0800, Matthew Dillon wrote: > :On Thu, 4 Mar 1999, Ulf Zimmermann wrote: > : > :> Langsam habe ich die schnauze voll (for the ones who know german) > :> > :> This machine is a AMD K6-233 with 128MB, Adaptec 2940UW, Brooktree 848, > :> Intel fxp, SB16 PnP. > :> > :> This machine was running 3.0-BETA for > 70 days. As soon I upgraded to > :> 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with > :> wire count already 0, for which Jordan took the panic out. But I am still > :> getting other panics, like page fault. > > Someone took a panic out in the VM system? Where? He only took out the call to trap/panic for these kinds of messages: Mar 4 00:47:10 PacHell /kernel: vm_page_free: freeing wired page Mar 4 00:47:10 PacHell /kernel: vm_page_unwire: invalid wire count: 0 > > :> I have several core dumps. If anyone wants to look at them, please contact > :> me. (I am otherwise close to go back to 3.0R). > : > :Have a look at kern/10376 in case there's any common factor (but I doubt > :it). No, this has nothing to do with my problems. > : > :-- > :Bob Bishop +44 118 977 4017 > :rb@gid.co.uk fax +44 118 989 4254 > > -Matt > Matthew Dillon > -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 12:28:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D04E14D82 for ; Thu, 4 Mar 1999 12:27:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31748; Thu, 4 Mar 1999 12:27:38 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 12:27:38 -0800 (PST) From: Matthew Dillon Message-Id: <199903042027.MAA31748@apollo.backplane.com> To: Ulf Zimmermann Cc: Bob Bishop , Ulf Zimmermann , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with :> :> wire count already 0, for which Jordan took the panic out. But I am still :> :> getting other panics, like page fault. :> :> Someone took a panic out in the VM system? Where? : :He only took out the call to trap/panic for these kinds of messages: : :Mar 4 00:47:10 PacHell /kernel: vm_page_free: freeing wired page :Mar 4 00:47:10 PacHell /kernel: vm_page_unwire: invalid wire count: 0 These are pretty serious panics. You would not want to allow the system to run after such conditions occur. Taking out the panics is not going to solve the problem. A backtrace from the core dump would be useful. It's hard to tell what the cause of the crash is - it could be the BT848, it could the SBPRO. It could be something else. You might have to mess around disabling various bits to figure out the cause. -Matt Matthew Dillon :Regards, Ulf. : :--------------------------------------------------------------------- :Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 :Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 12:31:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 922A714EC8 for ; Thu, 4 Mar 1999 12:31:07 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.212]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA73B0 for ; Thu, 4 Mar 1999 21:30:49 +0100 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id VAA13517 for ; Thu, 4 Mar 1999 21:31:25 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 04 Mar 1999 21:31:24 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Hackers Subject: /usr/include/net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just got a question that might be easy to answer (and mayhaps not): 4.x has a /usr/include/net/if.h if_dl.h and if_var.h and 3.x is likely to be the same. However 2.2.x does not, at least not up to .7. Is this the correct division? (cvs log show a creation date of 03-01-1997, so that likely to have been 3.x CURRENT at that time, I might be wrong offcourse) But let's say that 3.x and 4.x use the if_var.h, how would I best use this with includes? use #ifndef __FREEBSD_2_2__; #include ? That's kinda puzzling me for now. Thanks for any clearification and enlightenment =) --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 12:33:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 04E9D150B0 for ; Thu, 4 Mar 1999 12:33:16 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id MAA28051; Thu, 4 Mar 1999 12:33:11 -0800 (PST) (envelope-from ulf) Message-ID: <19990304123311.C3659@TelcoSucks.org> Date: Thu, 4 Mar 1999 12:33:11 -0800 From: Ulf Zimmermann To: Matthew Dillon , Ulf Zimmermann Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE Reply-To: ulf@alameda.net References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> <199903042027.MAA31748@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903042027.MAA31748@apollo.backplane.com>; from Matthew Dillon on Thu, Mar 04, 1999 at 12:27:38PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 12:27:38PM -0800, Matthew Dillon wrote: > :> :> 3.1-RELEASE and then 3.1-STABLE (SNAP 19990218) I get panics. Mostly with > :> :> wire count already 0, for which Jordan took the panic out. But I am still > :> :> getting other panics, like page fault. > :> > :> Someone took a panic out in the VM system? Where? > : > :He only took out the call to trap/panic for these kinds of messages: > : > :Mar 4 00:47:10 PacHell /kernel: vm_page_free: freeing wired page > :Mar 4 00:47:10 PacHell /kernel: vm_page_unwire: invalid wire count: 0 > > These are pretty serious panics. You would not want to allow the > system to run after such conditions occur. Taking out the panics is not > going to solve the problem. Tell that Jordan. > > A backtrace from the core dump would be useful. It's hard to tell > what the cause of the crash is - it could be the BT848, it could the > SBPRO. It could be something else. You might have to mess around > disabling various bits to figure out the cause. Crashes have been occuring at all different times. X11 running, no X11 running. X11 with with fxtv or without. I can give you the ssh root login to access the /var/crash. > > -Matt > Matthew Dillon > > > :Regards, Ulf. > : > :--------------------------------------------------------------------- > :Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > :Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 12:42:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6D7F014F21 for ; Thu, 4 Mar 1999 12:42:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA31909; Thu, 4 Mar 1999 12:42:39 -0800 (PST) (envelope-from dillon) Date: Thu, 4 Mar 1999 12:42:39 -0800 (PST) From: Matthew Dillon Message-Id: <199903042042.MAA31909@apollo.backplane.com> To: Ulf Zimmermann Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> <199903042027.MAA31748@apollo.backplane.com> <19990304123311.C3659@TelcoSucks.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> A backtrace from the core dump would be useful. It's hard to tell :> what the cause of the crash is - it could be the BT848, it could the :> SBPRO. It could be something else. You might have to mess around :> disabling various bits to figure out the cause. : :Crashes have been occuring at all different times. X11 running, no X11 running. :X11 with with fxtv or without. I can give you the ssh root login to access :the /var/crash. : :Regards, Ulf. :Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Well, I don't quite have enough time to get knee deep into a crash dump. I can suggest a few things. You could try moving to -current. The VM group is in the midst of comitting a bunch of bug fixes into -current ( current == -4.x ) but, more importantly, there are bug fixes already in -current which have not yet been backported to -3.x. If your crashing problem does not occur under 4.x, there's a good chance that it will be fixed in -3.x in the next week or so as the fixes are backported. If the crash still occurs under -4.x, we know there's still a problem somewhere. Also, a large number of changes have been made to BT driver even since the 3.1 release. It might be beneficial to upgrade to the latest -stable ( i.e. -3.x ) first, and if that does not clear up the problem to try -current ( i.e. -4.x ). There are no guarentees with any of these, unfortunately. -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 Mar 4 12:47:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 16DA514FC4 for ; Thu, 4 Mar 1999 12:46:39 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id MAA31146; Thu, 4 Mar 1999 12:46:33 -0800 (PST) (envelope-from ulf) Message-ID: <19990304124633.D3659@TelcoSucks.org> Date: Thu, 4 Mar 1999 12:46:33 -0800 From: Ulf Zimmermann To: Matthew Dillon , Ulf Zimmermann Cc: Bob Bishop , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE Reply-To: ulf@alameda.net References: <199903041733.JAA30220@apollo.backplane.com> <19990304121414.A3659@TelcoSucks.org> <199903042027.MAA31748@apollo.backplane.com> <19990304123311.C3659@TelcoSucks.org> <199903042042.MAA31909@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903042042.MAA31909@apollo.backplane.com>; from Matthew Dillon on Thu, Mar 04, 1999 at 12:42:39PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 04, 1999 at 12:42:39PM -0800, Matthew Dillon wrote: > :> A backtrace from the core dump would be useful. It's hard to tell > :> what the cause of the crash is - it could be the BT848, it could the > :> SBPRO. It could be something else. You might have to mess around > :> disabling various bits to figure out the cause. > : > :Crashes have been occuring at all different times. X11 running, no X11 running. > :X11 with with fxtv or without. I can give you the ssh root login to access > :the /var/crash. > : > :Regards, Ulf. > :Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > > Well, I don't quite have enough time to get knee deep into a crash > dump. I can suggest a few things. > > You could try moving to -current. The VM group is in the midst of No thank you. This is my desktop, which specific I do not want to reboot, rebuilt all the time. Before that, I would go back to 3.0R. > comitting a bunch of bug fixes into -current ( current == -4.x ) but, more > importantly, there are bug fixes already in -current which have not > yet been backported to -3.x. If your crashing problem does not occur > under 4.x, there's a good chance that it will be fixed in -3.x in the > next week or so as the fixes are backported. If the crash still occurs > under -4.x, we know there's still a problem somewhere. > > Also, a large number of changes have been made to BT driver even since > the 3.1 release. It might be beneficial to upgrade to the latest -stable > ( i.e. -3.x ) first, and if that does not clear up the problem to try > -current ( i.e. -4.x ). There are no guarentees with any of these, > unfortunately. Like I said, the machine is crashing with VM errors also when the card is not in use. I think I tried even a kernel without bktr driver. > > -Matt > Matthew Dillon > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 13:59:12 1999 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 0DC2814D88 for ; Thu, 4 Mar 1999 13:58:57 -0800 (PST) (envelope-from ad@mailhub.psn.ie) Received: from ad (helo=localhost) by mailhub.psn.ie with local-esmtp (Exim 2.12 #3) id 10Ig83-0000fD-00; Thu, 4 Mar 1999 21:58:03 +0000 Date: Thu, 4 Mar 1999 21:58:03 +0000 (GMT) From: Andy Doran To: Jeroen Ruigrok/Asmodai Cc: hackers@FreeBSD.org Subject: Re: /usr/include/net 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 > But let's say that 3.x and 4.x use the if_var.h, how would I best use this > with includes? use #ifndef __FREEBSD_2_2__; #include ? > > That's kinda puzzling me for now. > See the FAQ/Handbook entry on porting for more information, but basically AFAIR: -- snip #include #if defined(__FreeBSD__) && __FreeBSD_version >= 300001 #include #endif --snip If you're getting interface lists, a lot of stuff has changed from 3.0-RELEASE (queues are now used). Take a look interface.c from the latest source for fetchmail for an example, which I added FreeBSD support to. Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 14:39:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 83C931504C for ; Thu, 4 Mar 1999 14:39:23 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id RAA08114 for freebsd-hackers@freebsd.org; Thu, 4 Mar 1999 17:48:25 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199903042248.RAA08114@cc942873-a.ewndsr1.nj.home.com> Subject: FP Math Problem To: freebsd-hackers@freebsd.org Date: Thu, 4 Mar 1999 17:48:25 -0500 (EST) Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (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 I am trying to figure out why the following program produces a floating point exception and core dumps. #include #include #include int main() { double a = 1e200; double b; printf("fpgetmask: %o\n",fpgetmask()); printf("a: %e\n",a); b = a*a; printf("isinf: %d\n",isinf(b)); printf("isnan: %d\n",isnan(b)); printf("b > DBL_MAX: %d\n",b>DBL_MAX); printf("b: %e\n",b); return 0; } My output is, [112:~/tmp] ./dtest fpgetmask: 15 a: 1.000000e+200 isinf: 0 isnan: 0 Floating exception (core dumped) I started with this on -questions and (although the thread got sidetracked by a bad test program I presented at the beginning) other FreeBSDers have not reproduced the error, but get what I would expect, % ./dtest fpgetmask: 15 a: 1.000000e+200 isinf: 1 isnan: 0 b > DBL_MAX: 1 b: inf However, I get the FPE and core dump on my three FreeBSD machines (different hardware on each). All are, FreeBSD pc252.scitec.com 2.2.8-STABLE FreeBSD 2.2.8-STABLE #0: Mon Mar 1 14:25:39 EST 1999 Give or take a few days on the CVSup. (All were recently built to 2.2.8-S from 2.2.7-R.) It has been suggested I have somehow mucked up my floating point, but I do not know where to start and -questions did not produce many leads. Thanks for any help. More details can be provided; I would not know where to start. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 16:58:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id 8EEE81511A for ; Thu, 4 Mar 1999 16:58:35 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id QAA28267 for ; Thu, 4 Mar 1999 16:58:27 -0800 (PST) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id QAA20889 for hackers@FreeBSD.org; Thu, 4 Mar 1999 16:58:18 -0800 (PST) Message-ID: <19990304165818.A20680@proxydev.inktomi.com> Date: Thu, 4 Mar 1999 16:58:18 -0800 From: John Plevyak To: hackers@FreeBSD.org Subject: aio_read/write pread/pwrite Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In investigating the lack of pread/pwrite, I found the bug report kern/8011, and the patch therein. This patch mashes fd->f_offset around the (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred) and then resets it to achieve a sort of poor-mans pread/pwrite. This breaks multi-threaded programs. The same problem exists for aio_read/aio_write. The simple solution would be to use 'auio.uio_offset' directly (which is what aio_read/aio_write do), but alas, vn_read() mangles fp->f_offset anyway. Moreover, vn_write totally ignores auio.uio_offset == -1. The correct solution seems to be to recognize (aio.uio_offset != -1) as indicating 'don't mess with fp->f_offset at all!' since this is really what is intended in the places where it is set to non-zero. I have a patch for this which I am attaching to kern/8011, but I think it is more generally applicable since it should also fix aio_XXXX. Is anyone interested in it? john -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 18:12:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id D506A15101 for ; Thu, 4 Mar 1999 18:12:18 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 13906 invoked from network); 5 Mar 1999 02:11:58 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 02:11:58 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id VAA00381; Thu, 4 Mar 1999 21:11:58 -0500 (EST) Message-Id: <199903050211.VAA00381@y.dyson.net> Subject: Re: aio_read/write pread/pwrite In-Reply-To: <19990304165818.A20680@proxydev.inktomi.com> from John Plevyak at "Mar 4, 99 04:58:18 pm" To: jplevyak@inktomi.com (John Plevyak) Date: Thu, 4 Mar 1999 21:11:58 -0500 (EST) Cc: hackers@FreeBSD.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Plevyak said: > > In investigating the lack of pread/pwrite, I found the bug > report kern/8011, and the patch therein. > > This patch mashes fd->f_offset around the > (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred) and then resets > it to achieve a sort of poor-mans pread/pwrite. > > This breaks multi-threaded programs. The same problem exists > for aio_read/aio_write. > There are some things that need to be completed in the vn_read and vn_write routines. I suggest forwarding it to ALC (alc@cs.rice.edu) or Matt (dillon@backplane.apollo.com). I'll support them in the fix. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 19:29:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 536AF14F0F for ; Thu, 4 Mar 1999 19:29:35 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA15192; Thu, 4 Mar 1999 19:24:59 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdS15188; Fri Mar 5 03:24:56 1999 Date: Thu, 4 Mar 1999 19:24:52 -0800 (PST) From: Julian Elischer To: John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: aio_read/write pread/pwrite In-Reply-To: <19990304165818.A20680@proxydev.inktomi.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 the patch is in base64.. how do you read base64 files? On Thu, 4 Mar 1999, John Plevyak wrote: > > In investigating the lack of pread/pwrite, I found the bug > report kern/8011, and the patch therein. > > This patch mashes fd->f_offset around the > (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred) and then resets > it to achieve a sort of poor-mans pread/pwrite. > > This breaks multi-threaded programs. The same problem exists > for aio_read/aio_write. > > The simple solution would be to use 'auio.uio_offset' directly > (which is what aio_read/aio_write do), but alas, > vn_read() mangles fp->f_offset anyway. > > Moreover, vn_write totally ignores auio.uio_offset == -1. > > The correct solution seems to be to recognize (aio.uio_offset != -1) > as indicating 'don't mess with fp->f_offset at all!' since this is > really what is intended in the places where it is set to non-zero. > > I have a patch for this which I am attaching to kern/8011, but > I think it is more generally applicable since it should also > fix aio_XXXX. > > Is anyone interested in it? > > john > > > -- > John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD > Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 > W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net > > > 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 Mar 4 19:45: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id E22C414D82 for ; Thu, 4 Mar 1999 19:44:58 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA24868; Thu, 4 Mar 1999 20:44:40 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd024837; Thu Mar 4 20:44:34 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id UAA24997; Thu, 4 Mar 1999 20:44:32 -0700 (MST) From: Terry Lambert Message-Id: <199903050344.UAA24997@usr01.primenet.com> Subject: Re: lockf and kernel threads To: dyson@iquest.net Date: Fri, 5 Mar 1999 03:44:32 +0000 (GMT) Cc: tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903020401.XAA62227@y.dyson.net> from "John S. Dyson" at Mar 1, 99 11:01:25 pm X-Mailer: ELM [version 2.4 PL25] 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 > > IMO, the Linux threading, in particular, and the POSIX aio and thread > > interfaces, in general, represents a bunch of ill-thought-out hacks > > on hacks by the respective Linux and POSIX responsible persons. The > > Linux hacks were by people who didn't know better, and the POSIX > > hacks were political by people who did know better, but didn't have > > the courage of their convictions. It is time for some considered > > design. > > The AIO api has to be implemented for legitimacy, and likewise the > threading. In fact, the AIO API is quite useful. It doesn't have to be implemented in kernel space. An async call gate could all you to implement POSIX AIO in user space, at the same time not buying into the POSIX error of implementing only a few calls as asynchronous. Don't you agree that it's moronic that I can't, for example, do an asynchronous bind(2)? What about an asynchronous SYSV IPC message send or receive? From a kernel perspective, POSIX is an old coat, which you leave lying around in user space, but which you don't wear into the shower with you (kernel space). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 19:54:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id E5D8B14FB8 for ; Thu, 4 Mar 1999 19:54:38 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA08498; Thu, 4 Mar 1999 20:54:21 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd008485; Thu Mar 4 20:54:14 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id UAA25677; Thu, 4 Mar 1999 20:54:13 -0700 (MST) From: Terry Lambert Message-Id: <199903050354.UAA25677@usr01.primenet.com> Subject: Re: lockf and kernel threads To: jplevyak@inktomi.com (John Plevyak) Date: Fri, 5 Mar 1999 03:54:13 +0000 (GMT) Cc: tlambert@primenet.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <19990303120101.A21432@proxydev.inktomi.com> from "John Plevyak" at Mar 3, 99 12:01:01 pm X-Mailer: ELM [version 2.4 PL25] 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 think you can do this by recursing on the peers in the middle > > of handling the kill before you pass it to the trampoline (then > > it's too late). > > Why is it too late after that? In the patch I did the wait in exit1() > right after the 'kill' of the peers. It's too late if you've gone to user space with the signal, because it's an untrappable signal. That's the trampoline I was referring to. > The peers signal when they take themselves off the list > farther down in exit1, after the fdfree() call which > can result in the close and which would benefit from > having the p_leader still around. That's exactly the right way to do it, if you have to do it. > > Really, the thread specific data needs to be seperated from the > > proc struct; that is, the p->p_leader->foo should become meaningless. > > > > Basically, the litany on this is "everything that can differ between > > threads". > > You are very right. In the short term it might be best to > separate the parts of 'struct proc' which are thread specific > from those which are process specific. The process specific > parts can then always be accessed via 'p->p_leader' which > would amount to 't->t_proc' when at some future time these > two structures can be unwoven. Right. Such a structure is essentially identical in content to an async call context for an async call gate, BTW. 8-). > > I think the POSIX semantics, since they predate threads, can be > > reasonably interpreted either way. > > > > However, the use that you described seemed to want to scope file > > descriptors to a particular thread, such that a thread exit would > > result in the close. I don't think this is reasonable (the descriptor > > space is shared between all threads in a process). The only way > > to reasonably achieve such scoping is pthread_cleanup_push(). > > Actually, the opposite. What I would like is for file locks > to have process scope so that (for example) one thread could > open the file, a second could take out the lock, and a third > could close it, and the lock would be released. Currently > the lock is left hanging past when the process exits. Ah. OK, I was turned around from the desired semantics. I actually think that relying on the unlock as a side effect of the close is probably bad form. But I understand how it could come abut from a strict reading of POSIX. > I understand that generally signalling and threads is a bit messed up, > but I (somewhat urgently) have to solve the smaller problem of file > locking being broken for programs which use kernel threads. In any case, > FreeBSD should not be leaving the lock lying around past when the > process/thread which originated it died. That is clearly a bug. Strongly agreed. > I would like to get some patch into the FreeBSD source since > this is going to be an issue for production sites which would likely > prefer a 'blessed' solution rather than my personal patch. Don't look at me, I'm a heretic. I could curse you, if you think that'd help. 8-). > There are a number of possible solutions including the patch I proposed, > using a seperate id (rpid), adding additional bookkeeping to the > open fds vector etc. That's wouldn't actually work, unless the code believed you when you lied about the local PID (which it wouldn't), since it is different per thread in a "process" in the rfork implementation. Catch-22. You'd have to go forward on the proc/thread struct split. > However, I was hoping that by keeping the p_leader around, we could > use it as the 'process' and migrate to a model of seperate threads > and processes. That is what I am proposing. You might be able to get someone to commit this, at least as a short term soloution to the problem. It would get you over the "blessed" hump so you can concentrate on more pressing issues. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 21:23: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 4DD4914E0F for ; Thu, 4 Mar 1999 21:23:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id VAA56233; Thu, 4 Mar 1999 21:21:10 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903050521.VAA56233@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert Cc: dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 03:44:32 GMT." <199903050344.UAA24997@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Mar 1999 21:21:10 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, given that most likely we have quite a few ex-VMS hackers I am surprised that you have to explain or sell the idea of an async gate maybe you ought to refer to the term as a QIO 8) Cheers, Amancio > > > IMO, the Linux threading, in particular, and the POSIX aio and thread > > > interfaces, in general, represents a bunch of ill-thought-out hacks > > > on hacks by the respective Linux and POSIX responsible persons. The > > > Linux hacks were by people who didn't know better, and the POSIX > > > hacks were political by people who did know better, but didn't have > > > the courage of their convictions. It is time for some considered > > > design. > > > > The AIO api has to be implemented for legitimacy, and likewise the > > threading. In fact, the AIO API is quite useful. > > > It doesn't have to be implemented in kernel space. > > An async call gate could all you to implement POSIX AIO in user space, > at the same time not buying into the POSIX error of implementing only > a few calls as asynchronous. > > Don't you agree that it's moronic that I can't, for example, do > an asynchronous bind(2)? > > What about an asynchronous SYSV IPC message send or receive? > > From a kernel perspective, POSIX is an old coat, which you leave > lying around in user space, but which you don't wear into the > shower with you (kernel space). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > > 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 Mar 4 21:24:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 6E8BB1514E for ; Thu, 4 Mar 1999 21:24:27 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 6532 invoked from network); 5 Mar 1999 05:24:06 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 05:24:06 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id AAA20441; Fri, 5 Mar 1999 00:24:07 -0500 (EST) Message-Id: <199903050524.AAA20441@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903050344.UAA24997@usr01.primenet.com> from Terry Lambert at "Mar 5, 99 03:44:32 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 5 Mar 1999 00:24:07 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Terry Lambert said: > > > IMO, the Linux threading, in particular, and the POSIX aio and thread > > > interfaces, in general, represents a bunch of ill-thought-out hacks > > > on hacks by the respective Linux and POSIX responsible persons. The > > > Linux hacks were by people who didn't know better, and the POSIX > > > hacks were political by people who did know better, but didn't have > > > the courage of their convictions. It is time for some considered > > > design. > > > > The AIO api has to be implemented for legitimacy, and likewise the > > threading. In fact, the AIO API is quite useful. > > It doesn't have to be implemented in kernel space. > Kernel AIO is as trivial (and practically as fast) for async raw I/O as for normal raw I/O. The expedient implementation of AIO that I put together is just that, and a super efficient version for other types of file descriptors is possible, and not really hard to do. By doing threading type things, without a proper kernel infrastructure (which the BSD and Linux kernels don't have), all that is happening is to increase overheads. Don't thread something that it is just a fun exercise to do so. The stack context in the kernel is just plain evil. The BSD kernel is meant to provide a UNIX API, and implementing the UNIX API should be done in an efficient way, which often means to minimize the user/kernel transitions. AIO isn't really that hard to do in the kernel, and should be done there. Sure, there are probably things that shouldn't be in the kernel. Much of the complexity that is in the existing AIO code is the thread emulation of AIO, and will reside somewhere. If it is done in user-mode, it will require lots more transitions. Remember the AIO package can do LOTS of requests per system call. Unnecessarily doing things with threads on the BSD kernel is really a no-no, and is basically a way of spending CPU. The AIO code should be implemented like it is for raw devices -- a clean and efficient way. Lots of I/O requests can be processed with only one I/O user-kernel-user request given the current implementation. With promiscuous knowledge, it is even possible to minimize system calls (and do some work in user space) with the current code. Some of the stubs have experimental versions on my machine that support such a bypass. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 21:39: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 3B2CF14F0F for ; Thu, 4 Mar 1999 21:39:06 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 16806 invoked from network); 5 Mar 1999 05:38:45 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 05:38:45 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id AAA20475; Fri, 5 Mar 1999 00:38:46 -0500 (EST) Message-Id: <199903050538.AAA20475@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903050521.VAA56233@rah.star-gate.com> from Amancio Hasty at "Mar 4, 99 09:21:10 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 00:38:46 -0500 (EST) Cc: tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Amancio Hasty said: > > Actually, given that most likely we have quite a few ex-VMS hackers I am > surprised > that you have to explain or sell the idea of an async gate maybe you ought > to refer to the term as a QIO 8) > I am quite familar with qio$ stuff. It is cool, but so is AIO, and AIO is the standard. qio$ is really neat, when on I/O completion, an AST is posted. AIO is really neat, when on I/O completion a (real-time|normal) signal is posted. What is missing is a nicely sized set of real-time signals. I seem to remember that NetBSD has expanded their signal set. It would behoove FreeBSD to increase the signal set to include 32,64,96 realtime signals. If handling the UNIX-type API, more work needs to be done, like realtime signals (with a nice number of them.) More things become interesting at that point. Rather than inventing a whole raft of something that is as complex as the goal, and then emulating the goal with that infrastructure -- it is sometimes just as easy to produce the goal directly. These new fangled computers encourage complex answers to simple problems, I suggest just solving the problem. Nowadays, I don't think that some of us could implement a debug monitor on a PDP-8, because it is obviously impossible :-). With 2-3 days of unscrambled thought, I could upgrade AIO to implement much more true async I/O than it does today, without threads. The only really problematical part would be the network code, but to solve the problem without threads (so it would be efficient), might require more internal hacking than I want to do. Note that the AIO code as it is, can queue multiple raw I/O requests to multiple devices in one system call. The completion can be signaled, tested for, or blocked on (in an or or and fashion.) There is little else than to increase the number of signals (for convienence), and improve the signal semantics to the real-time posix requirements. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 21:46:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 38C7D14FEC for ; Thu, 4 Mar 1999 21:46:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id VAA62143; Thu, 4 Mar 1999 21:45:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903050545.VAA62143@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dyson@iquest.net Cc: tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 00:38:46 EST." <199903050538.AAA20475@y.dyson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Mar 1999 21:45:12 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whats your love with signals ? With respect to AIO , standards are great when their work... Amancio > Amancio Hasty said: > > > > Actually, given that most likely we have quite a few ex-VMS hackers I am > > surprised > > that you have to explain or sell the idea of an async gate maybe you ought > > to refer to the term as a QIO 8) > > > I am quite familar with qio$ stuff. It is cool, but so is AIO, and AIO > is the standard. qio$ is really neat, when on I/O completion, an AST > is posted. AIO is really neat, when on I/O completion a (real-time|normal) > signal is posted. What is missing is a nicely sized set of real-time > signals. I seem to remember that NetBSD has expanded their signal set. > It would behoove FreeBSD to increase the signal set to include 32,64,96 > realtime signals. > > If handling the UNIX-type API, more work needs to be done, like > realtime signals (with a nice number of them.) More things become > interesting at that point. > > Rather than inventing a whole raft of something that is as complex as > the goal, and then emulating the goal with that infrastructure -- it > is sometimes just as easy to produce the goal directly. These new > fangled computers encourage complex answers to simple problems, I suggest > just solving the problem. Nowadays, I don't think that some of us > could implement a debug monitor on a PDP-8, because it is obviously > impossible :-). > > With 2-3 days of unscrambled thought, I could upgrade AIO to implement > much more true async I/O than it does today, without threads. The only > really problematical part would be the network code, but to solve the > problem without threads (so it would be efficient), might require more > internal hacking than I want to do. > > Note that the AIO code as it is, can queue multiple raw I/O requests > to multiple devices in one system call. The completion can be signaled, > tested for, or blocked on (in an or or and fashion.) There is little > else than to increase the number of signals (for convienence), and > improve the signal semantics to the real-time posix requirements. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 21:59:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 39ACB1503C for ; Thu, 4 Mar 1999 21:59:28 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 1195 invoked from network); 5 Mar 1999 05:59:09 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 05:59:09 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id AAA20532; Fri, 5 Mar 1999 00:59:08 -0500 (EST) Message-Id: <199903050559.AAA20532@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903050545.VAA62143@rah.star-gate.com> from Amancio Hasty at "Mar 4, 99 09:45:12 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 00:59:08 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Amancio Hasty said: > > Whats your love with signals ? > Standards. > > With respect to AIO , standards are great when their work... > There is very little that qio$ would add, if you had a proper implementation of AIO. (Relative to a UNIX style API.) The current implementation works with every type of FD, and with the additional realtime signals, and perhaps the addition of async support for normal files, and also perhaps some of the networking mechanisms -- one has mostly everything. Each of these things that I mention are part of the POSIX specs. AIO is the standard, whether or not it is perfect. qio$ isn't defined, other than looking at old VMS or RSX-11 manuals. Hey, if someone wants to write RSX-UNIX, then more power to them. I am playing with a modular kernel (not to be confused with a micro-kernel), and it can implement such primitives. However, BSD is a UNIX kernel, and implements a UNIX API. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 22: 8:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id C10DE15015 for ; Thu, 4 Mar 1999 22:08:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA65635; Thu, 4 Mar 1999 22:06:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903050606.WAA65635@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dyson@iquest.net Cc: tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 00:59:08 EST." <199903050559.AAA20532@y.dyson.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Mar 1999 22:06:54 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I supposed that for a limited distinct events signals are really cool. If you can deliver a signal there is nothing to stop you from delivering an AST provided that one can muster up the queuing delivery mechanism which is not that much different than the beloved old fashion signal delivery mechanism. Does the current AIO implementation for an async call create s a thread per call? If so we are done talking 8) Cheers, Amancio > Amancio Hasty said: > > > > Whats your love with signals ? > > > Standards. > > > > > With respect to AIO , standards are great when their work... > > > There is very little that qio$ would add, if you had a proper > implementation of AIO. (Relative to a UNIX style API.) > > The current implementation works with every type of FD, and > with the additional realtime signals, and perhaps the addition > of async support for normal files, and also perhaps some of the > networking mechanisms -- one has mostly everything. Each of > these things that I mention are part of the POSIX specs. > > AIO is the standard, whether or not it is perfect. qio$ isn't > defined, other than looking at old VMS or RSX-11 manuals. > > Hey, if someone wants to write RSX-UNIX, then more power to > them. I am playing with a modular kernel (not to be confused > with a micro-kernel), and it can implement such primitives. > However, BSD is a UNIX kernel, and implements a UNIX API. > > -- > John | Never try to teach a pig to sing, > dyson@iquest.net | it makes one look stupid > jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 22:16:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 9BBCE1500E for ; Thu, 4 Mar 1999 22:16:24 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.191]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA32B1; Fri, 5 Mar 1999 07:16:06 +0100 Received: from daemon.ninth-circle.org (abaddon@daemon [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id HAA14376; Fri, 5 Mar 1999 07:16:46 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 05 Mar 1999 07:16:46 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Andy Doran Subject: Re: /usr/include/net Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Mar-99 Andy Doran wrote: >> But let's say that 3.x and 4.x use the if_var.h, how would I best use >> this with includes? use #ifndef __FREEBSD_2_2__; #include ? >> > See the FAQ/Handbook entry on porting for more information, but basically > AFAIR: It's not for a port, it's for native support alongsides Linux and a couple of other OS's. > -- snip >#include > >#if defined(__FreeBSD__) && __FreeBSD_version >= 300001 >#include >#endif > --snip thanks, will try > If you're getting interface lists, a lot of stuff has changed from > 3.0-RELEASE (queues are now used). Take a look interface.c from the > latest source for fetchmail for an example, which I added FreeBSD support > to. Well, the reason the program gets interface lists is because it needs them for routing, in how much this is a general hack I still need to find out and I'll be calling on -hackers whenever I need more advice =) The program is the Zebra project @ www.zebra.org --- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 22:47:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from theo.thg.goe.ni.schule.de (theo.THG.Goe.NI.Schule.DE [195.27.182.97]) by hub.freebsd.org (Postfix) with ESMTP id B41311507C; Thu, 4 Mar 1999 22:47:27 -0800 (PST) (envelope-from gratke@thg.goe.ni.schule.de) Received: from elly.thg.goe.ni.schule.de (gratke@elly.thg.goe.ni.schule.de [195.27.182.98]) by theo.thg.goe.ni.schule.de (8.8.8/8.8.8) with SMTP id HAA21471; Fri, 5 Mar 1999 07:46:07 +0100 Date: Fri, 5 Mar 1999 07:47:09 +0100 (MET) From: Georg Ratke To: hackers@FreeBSD.ORG Cc: freebsd-hackers-digest@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #415 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 Unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 4 22:53:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id A1AF01507C; Thu, 4 Mar 1999 22:53:54 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id WAA70054; Thu, 4 Mar 1999 22:53:37 -0800 (PST) From: Archie Cobbs Message-Id: <199903050653.WAA70054@bubba.whistle.com> Subject: PPP over synchronous lines To: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Date: Thu, 4 Mar 1999 22:53:37 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (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 To folks doing PPP over a synchronous line of any type.. If you're interesting in trying something new, I'd love to hear any comments/feedback from using mpd (net/mpd in ports) over netgraph (ftp://ftp.whistle.com/pub/archie/netgraph/index.html). With this combination you can do PPP over raw synchronous, frame relay, Ethernet, etc. If your synchronous driver is not supported, we can add support for it. Currently the ar and sr drivers are netgraph-enabled. Right now the performance will be somewhat slower due to the use of the tunnel interface; this will be fixed in the future. Feedback regarding non-PPP connections using netgraph also appreciated. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 2:41:32 1999 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 C13EB1516B; Fri, 5 Mar 1999 02:39:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA14806; Fri, 5 Mar 1999 19:39:41 +0900 (JST) Message-ID: <36DFB421.1A845720@newsguy.com> Date: Fri, 05 Mar 1999 19:38:25 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Terry Lambert Cc: sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: GGI References: <199903050304.UAA22223@usr01.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (changed, subject, list, and cc list... it's almost a new mail! :) Terry Lambert wrote: > ... > I can't do the work for FreeBSD until it adopts GGI, and supports ELF ... > > The GGI people have been looking for someone (with commit priviledges, > obviously) to do a FreeBSD port, and have gone so far as to put the > kernel pieces of their predominantly Linux project *in the public domain*. I looked at GGI, and I liked it. If my memory doesn't fail me, Soren remarked that he was not much impressed with it last he checked it. What I'd like to know is if the Powers That Be of FreeBSD console (Soren and Yokota?) would, present state of the code notwithstanding, accept the adoption of GGI once deemed to be "ready", or if there is any fundamental flaw with it that makes this a hopeless propositon. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 2:49:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 9C24315094; Fri, 5 Mar 1999 02:49:17 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA91535; Fri, 5 Mar 1999 11:48:32 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903051048.LAA91535@freebsd.dk> Subject: Re: GGI In-Reply-To: <36DFB421.1A845720@newsguy.com> from "Daniel C. Sobral" at "Mar 5, 1999 7:38:25 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Fri, 5 Mar 1999 11:48:32 +0100 (CET) Cc: tlambert@primenet.com, sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daniel C. Sobral wrote: > Terry Lambert wrote: > > The GGI people have been looking for someone (with commit priviledges, > > obviously) to do a FreeBSD port, and have gone so far as to put the > > kernel pieces of their predominantly Linux project *in the public domain*. > > I looked at GGI, and I liked it. If my memory doesn't fail me, Soren > remarked that he was not much impressed with it last he checked it. Thats right. > What I'd like to know is if the Powers That Be of FreeBSD console > (Soren and Yokota?) would, present state of the code > notwithstanding, accept the adoption of GGI once deemed to be > "ready", or if there is any fundamental flaw with it that makes this > a hopeless propositon. Hmmmmm....... I'll have to take a look at it (again) before commenting to heavily on that, at least it has to be done as a minimal impact thing, it should try to use what we allready have in there, instead of reinventing the wheel. It should be done as a kernel module if anything. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 3: 3: 1 1999 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 A4B5E15102 for ; Fri, 5 Mar 1999 03:00:24 -0800 (PST) (envelope-from ad@mailhub.psn.ie) Received: from ad (helo=localhost) by mailhub.psn.ie with local-esmtp (Exim 2.12 #3) id 10IrW0-0000zi-00; Fri, 5 Mar 1999 10:07:32 +0000 Date: Fri, 5 Mar 1999 10:07:32 +0000 (GMT) From: Andy Doran To: Jeroen Ruigrok/Asmodai Cc: hackers@FreeBSD.org Subject: Re: /usr/include/net 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 > > See the FAQ/Handbook entry on porting for more information, but basically > > AFAIR: > > It's not for a port, it's for native support alongsides Linux and a couple > of other OS's. > This contains information on how to find the version of FreeBSD, and what you should test *before* you try to include sys/param.h, although if you're only targeting Linux/*BSD then including it anyway isn't a problem. Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 4:25: 1 1999 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 926CE15159 for ; Fri, 5 Mar 1999 04:24:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id EAA47523; Fri, 5 Mar 1999 04:24:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Ulf Zimmermann , Bob Bishop , hackers@FreeBSD.ORG Subject: Re: vm problems in 3.1-RELEASE and -STABLE In-reply-to: Your message of "Thu, 04 Mar 1999 12:27:38 PST." <199903042027.MAA31748@apollo.backplane.com> Date: Fri, 05 Mar 1999 04:24:44 -0800 Message-ID: <47519.920636684@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These are pretty serious panics. You would not want to allow the > system to run after such conditions occur. Taking out the panics is not > going to solve the problem. Just to clarify, this was only done to deliberately _move_ the problem, not to fix it. Once we did that, we were able to observe other symptoms and some of the secondary (or perhaps tertiary) effects and verify its severity. I never got back to Ulf's system after this very preliminary bit of discovery work to try and actually decipher the clues obtained. Just too busy. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 5:53:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penmax.com (cc595093-a.mdltwn1.nj.home.com [24.3.192.38]) by hub.freebsd.org (Postfix) with ESMTP id 4EC0C1516C for ; Fri, 5 Mar 1999 05:53:46 -0800 (PST) (envelope-from vincef@penmax.com) Received: from rembrandt (rembrandt.penmax.com [10.1.3.2]) by penmax.com (8.8.8/8.8.8) with SMTP id IAA02266 for ; Fri, 5 Mar 1999 08:57:09 -0500 (EST) (envelope-from vincef@penmax.com) Received: by rembrandt with Microsoft Mail id <01BE66E6.05FE0F80@rembrandt>; Fri, 5 Mar 1999 08:56:14 -0500 Message-ID: <01BE66E6.05FE0F80@rembrandt> From: Vincent Fleming To: "'hackers@freebsd.org'" Subject: samba performance Date: Fri, 5 Mar 1999 08:56:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi; I've bee playing around with smbd, trying to adjust the performance. I seem to be getting around 2200k/s (2MB/s) on reads, but only 315k/s on writes! Now, that's a BIG difference. I've been going over the docs, and have tried all the suggestions in there for increasing performance. Does anyone out there have any more suggestions on how I can get the write performance to more closely resemble the read performance? I have the sources, and have enabled MMAP use, among other things. So, if any suggestions involve hacking the server, don't hesitate mentioning them! My server: (yeah, I know, I should use a better machine! It's pretty fast, though) AMD K6 233 64 MB RAM Buslogic PCI Fast/Wide SCSI card Seagate Barracuda ST12550N Fast/Narrow 2GB drive 3com 905B PCI 100 base T ethernet FreeBSD 2.2.7 My Client: PII 300 320 MB RAM Adaptec 2940UW SCSI Seagate Barracuda ST32171W Ultra Wide 2GB drive 3 com 905B PCI 100 base T ethernet Win98 They are directly connected with a cross-over 100 baseT cable, so they're running full-duplex. Thanks for any suggestions! Vince Fleming To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 6:12:32 1999 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 2040A15118 for ; Fri, 5 Mar 1999 06:12:28 -0800 (PST) (envelope-from ad@psn.ie) Received: from charlie.internal ([192.168.0.2]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10IvIa-00015e-00; Fri, 5 Mar 1999 14:09:56 +0000 Received: from localhost ([127.0.0.1]) by charlie.internal with esmtp (Exim 2.05 #1) id 10IvIb-0001mW-00; Fri, 5 Mar 1999 14:09:57 +0000 Date: Fri, 5 Mar 1999 14:09:57 +0000 (GMT) From: Andy Doran X-Sender: ad@charlie.internal To: Vincent Fleming Cc: "'hackers@freebsd.org'" Subject: Re: samba performance In-Reply-To: <01BE66E6.05FE0F80@rembrandt> 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 could mount your filesystems with the async flag. Search the mailing list archive (of hackers) for the last two months for caveats and more information. Andy. On Fri, 5 Mar 1999, Vincent Fleming wrote: > Hi; > > I've bee playing around with smbd, trying to adjust the performance. > > I seem to be getting around 2200k/s (2MB/s) on reads, but only 315k/s > on writes! > > Now, that's a BIG difference. > > I've been going over the docs, and have tried all the suggestions in there > for increasing performance. Does anyone out there have any more > suggestions on how I can get the write performance to more closely resemble > the read performance? > > I have the sources, and have enabled MMAP use, among other things. So, > if any suggestions involve hacking the server, don't hesitate mentioning them! > > My server: (yeah, I know, I should use a better machine! It's pretty fast, though) > AMD K6 233 > 64 MB RAM > Buslogic PCI Fast/Wide SCSI card > Seagate Barracuda ST12550N Fast/Narrow 2GB drive > 3com 905B PCI 100 base T ethernet > FreeBSD 2.2.7 > > My Client: > PII 300 > 320 MB RAM > Adaptec 2940UW SCSI > Seagate Barracuda ST32171W Ultra Wide 2GB drive > 3 com 905B PCI 100 base T ethernet > Win98 > > They are directly connected with a cross-over 100 baseT cable, so they're > running full-duplex. > > Thanks for any suggestions! > > Vince Fleming > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 7:31:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (Postfix) with ESMTP id CBC5415183 for ; Fri, 5 Mar 1999 07:31:41 -0800 (PST) (envelope-from stephw@xs4all.nl) Received: from xs3.xs4all.nl (stephw@xs3.xs4all.nl [194.109.6.44]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id QAA17386 for ; Fri, 5 Mar 1999 16:31:24 +0100 (CET) From: stephw@xs4all.nl Received: (from stephw@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) id QAA28458 for freebsd-hackers@freebsd.org; Fri, 5 Mar 1999 16:31:23 +0100 (CET) Date: Fri, 5 Mar 1999 16:31:23 +0100 To: freebsd-hackers@freebsd.org Subject: adaptec 2940u2w hangs on external disks Message-ID: <19990305163123.E20535@xs3.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We now got 3 boxes converted from bsdi to freebsd 3.1R with two adaptec 2940U2W with Seagate ST39102 ultra2lv disks. We tried attaching only one outside disk to only one controller but the problem still persists. Once in a while freebsd will not boot, but hang during boot up, after 'waiting for scsi devices to settle.' We tried the same controller with the same scsi setup, and the same disks in a linux box and the problem didnt occur, so it's definetely some freebsd problem. Is this problem known yet, and is there some fix for it ? many thanks in advance, bye, Stephanie ----------------------------<> _@r4k.net <>-----------------<> FreeBSD <>--- "I had to hit him -- he was starting to make sense." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 7:54:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id 62E7E15194 for ; Fri, 5 Mar 1999 07:54:53 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from tsdev.inktomi.com (tsdev.inktomi.com [209.1.32.119]) by mercury.inktomi.com (8.9.1a/8.9.1) with SMTP id HAA14634; Fri, 5 Mar 1999 07:54:44 -0800 (PST) Received: by tsdev.inktomi.com (SMI-8.6/SMI-SVR4) id HAA22602; Fri, 5 Mar 1999 07:54:35 -0800 Message-ID: <19990305075435.A22589@tsdev.inktomi.com> Date: Fri, 5 Mar 1999 07:54:35 -0800 From: John Plevyak To: Julian Elischer , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: aio_read/write pread/pwrite References: <19990304165818.A20680@proxydev.inktomi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Julian Elischer on Thu, Mar 04, 1999 at 07:24:52PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can translate base64 with metamail; available from ports/mail/metamail. john On Thu, Mar 04, 1999 at 07:24:52PM -0800, Julian Elischer wrote: > the patch is in base64.. > how do you read base64 files? > > > On Thu, 4 Mar 1999, John Plevyak wrote: > > > > > In investigating the lack of pread/pwrite, I found the bug > > report kern/8011, and the patch therein. > > > > This patch mashes fd->f_offset around the > > (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred) and then resets > > it to achieve a sort of poor-mans pread/pwrite. > > > > This breaks multi-threaded programs. The same problem exists > > for aio_read/aio_write. > > > > The simple solution would be to use 'auio.uio_offset' directly > > (which is what aio_read/aio_write do), but alas, > > vn_read() mangles fp->f_offset anyway. > > > > Moreover, vn_write totally ignores auio.uio_offset == -1. > > > > The correct solution seems to be to recognize (aio.uio_offset != -1) > > as indicating 'don't mess with fp->f_offset at all!' since this is > > really what is intended in the places where it is set to non-zero. > > > > I have a patch for this which I am attaching to kern/8011, but > > I think it is more generally applicable since it should also > > fix aio_XXXX. > > > > Is anyone interested in it? > > > > john > > > > > > -- > > John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD > > Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 > > W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 8: 3: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 1AE2F151A3 for ; Fri, 5 Mar 1999 08:02:53 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 22814 invoked by uid 1001); 5 Mar 1999 16:02:35 +0000 (GMT) To: stephw@xs4all.nl Cc: freebsd-hackers@freebsd.org Subject: Re: adaptec 2940u2w hangs on external disks From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 5 Mar 1999 16:31:23 +0100" References: <19990305163123.E20535@xs3.xs4all.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 05 Mar 1999 17:02:35 +0100 Message-ID: <22812.920649755@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We now got 3 boxes converted from bsdi to freebsd 3.1R with two > adaptec 2940U2W with Seagate ST39102 ultra2lv disks. We tried > attaching only one outside disk to only one controller but the > problem still persists. Once in a while freebsd will not boot, but > hang during boot up, after 'waiting for scsi devices to settle.' > We tried the same controller with the same scsi setup, and the same > disks in a linux box and the problem didnt occur, so it's definetely > some freebsd problem. > > Is this problem known yet, and is there some fix for it ? A possibly related problem we've seen here: FreeBSD sometimes needs a hard reset (hit reset button) to reboot, while a software reboot will hang during bootup. This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, *and* DAT on single-ended chain. Using verbose boot, we see that the hang occurs while probing the DAT and/or the CDROM player on the SE chain. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 8: 6:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id 8FF0515039 for ; Fri, 5 Mar 1999 08:06:36 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from tsdev.inktomi.com (tsdev.inktomi.com [209.1.32.119]) by mercury.inktomi.com (8.9.1a/8.9.1) with SMTP id IAA15404; Fri, 5 Mar 1999 08:06:28 -0800 (PST) Received: by tsdev.inktomi.com (SMI-8.6/SMI-SVR4) id IAA22611; Fri, 5 Mar 1999 08:06:18 -0800 Message-ID: <19990305080618.B22589@tsdev.inktomi.com> Date: Fri, 5 Mar 1999 08:06:18 -0800 From: John Plevyak To: Terry Lambert , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads References: <19990303120101.A21432@proxydev.inktomi.com> <199903050354.UAA25677@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903050354.UAA25677@usr01.primenet.com>; from Terry Lambert on Fri, Mar 05, 1999 at 03:54:13AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 03:54:13AM +0000, Terry Lambert wrote: > > > I think you can do this by recursing on the peers in the middle > > > of handling the kill before you pass it to the trampoline (then > > > it's too late). > > > > Why is it too late after that? In the patch I did the wait in exit1() > > right after the 'kill' of the peers. > > It's too late if you've gone to user space with the signal, because > it's an untrappable signal. That's the trampoline I was referring > to. I understand about the trampoline, but I don't see why you can't send the signal out of user space, mostly because that is what 3.0+ currently does! (near the beginning of exit1() to all peers of a p_leader.) > Right. Such a structure is essentially identical in content to > an async call context for an async call gate, BTW. 8-). I am missing context on this, however if it was a mechanism for generalized async calls w/o signals/polling but 'wait for one of N events' I am interested. > I actually think that relying on the unlock as a side effect of > the close is probably bad form. But I understand how it could > come abut from a strict reading of POSIX. The close is really an implementation detail, since it is the mechanism by which the kernel releases the lock when the process exits. I could live with the lock persisting beyond the close (just more bookkeeping on my part), but not with it persisting beyond the exit of the processes (since I cannot trap 'kill -9'). > You might be able to get someone to commit this, at least as a short > term soloution to the problem. It would get you over the "blessed" > hump so you can concentrate on more pressing issues. Hummm... any guesses as to whom might be most sympathetic? john > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 8:44:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 27DFC151C1 for ; Fri, 5 Mar 1999 08:44:09 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id RAA17085; Fri, 5 Mar 1999 17:43:13 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id RAA86182; Fri, 5 Mar 1999 17:43:45 +0100 (CET) Date: Fri, 5 Mar 1999 17:43:44 +0100 From: Bernd Walter To: sthaug@nethelp.no Cc: stephw@xs4all.nl, freebsd-hackers@FreeBSD.ORG Subject: Re: adaptec 2940u2w hangs on external disks Message-ID: <19990305174344.A85423@cicely7.cicely.de> References: <19990305163123.E20535@xs3.xs4all.nl> <22812.920649755@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <22812.920649755@verdi.nethelp.no>; from sthaug@nethelp.no on Fri, Mar 05, 1999 at 05:02:35PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 05:02:35PM +0100, sthaug@nethelp.no wrote: > > We now got 3 boxes converted from bsdi to freebsd 3.1R with two > > adaptec 2940U2W with Seagate ST39102 ultra2lv disks. We tried > > attaching only one outside disk to only one controller but the > > problem still persists. Once in a while freebsd will not boot, but > > hang during boot up, after 'waiting for scsi devices to settle.' > > We tried the same controller with the same scsi setup, and the same > > disks in a linux box and the problem didnt occur, so it's definetely > > some freebsd problem. > > > > Is this problem known yet, and is there some fix for it ? > > A possibly related problem we've seen here: FreeBSD sometimes needs a > hard reset (hit reset button) to reboot, while a software reboot will > hang during bootup. > > This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec > 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, > *and* DAT on single-ended chain. Using verbose boot, we see that the > hang occurs while probing the DAT and/or the CDROM player on the SE > chain. > I also seeing this kind of problem on 3 independent ASUS P2BLS Boards. Another board (Maybe later revision) is not showing this. We have tried a bios update and several FreeBSD Versions including some 4.0-current - but the problem still exists. I remember that boot -v showed something that I wanted to send to the FreeBSD-SCSI list - but I didn't yet because I don't have it logged. It stopped after probing some but not all drives before it would print the non -v informations. I expect this problem has something to do with the aic revision on that boards. I'll try to get the boot -v informations and the revision next week. > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:19:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.kudra.com (gw.kudra.com [199.6.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 6592014BE9 for ; Fri, 5 Mar 1999 09:19:29 -0800 (PST) (envelope-from robert@kudra.com) Received: (from robert@localhost) by tabby.kudra.com (8.9.2/8.6.12) id MAA48440; Fri, 5 Mar 1999 12:19:08 -0500 (EST) Message-ID: <19990305121908.A48418@kudra.com> Date: Fri, 5 Mar 1999 12:19:08 -0500 From: Robert Sexton To: sthaug@nethelp.no Cc: freebsd-hackers@freebsd.org Subject: Re: adaptec 2940u2w hangs on external disks References: <19990305163123.E20535@xs3.xs4all.nl> <22812.920649755@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <22812.920649755@verdi.nethelp.no>; from sthaug@nethelp.no on Fri, Mar 05, 1999 at 05:02:35PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 05:02:35PM +0100, sthaug@nethelp.no wrote: > > A possibly related problem we've seen here: FreeBSD sometimes needs a > hard reset (hit reset button) to reboot, while a software reboot will > hang during bootup. > > This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec > 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, > *and* DAT on single-ended chain. Using verbose boot, we see that the > hang occurs while probing the DAT and/or the CDROM player on the SE > chain. I've seen this quite a few times recently, as of 3.1. Last night in my machine (Symbios 875 & 895 COntrollers) and two weeks ago in a customers machine (HP Netserver with build in Adaptec EISA controller) I'll try to reproduce it this weekend at home and file a pr. -- Robert Sexton, robert@kudra.com FreeBSD - Quality BSD UNIX for Intel and Alpha that you don't have to shave your head to use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:31:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 69408151E1 for ; Fri, 5 Mar 1999 09:31:15 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA22596; Fri, 5 Mar 1999 12:31:45 -0500 (EST) Date: Fri, 5 Mar 1999 12:31:43 -0500 (EST) From: Alfred Perlstein To: Robert Sexton Cc: sthaug@nethelp.no, freebsd-hackers@FreeBSD.ORG Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: <19990305121908.A48418@kudra.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, 5 Mar 1999, Robert Sexton wrote: > On Fri, Mar 05, 1999 at 05:02:35PM +0100, sthaug@nethelp.no wrote: > > > > A possibly related problem we've seen here: FreeBSD sometimes needs a > > hard reset (hit reset button) to reboot, while a software reboot will > > hang during bootup. > > > > This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec > > 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, > > *and* DAT on single-ended chain. Using verbose boot, we see that the > > hang occurs while probing the DAT and/or the CDROM player on the SE > > chain. > > > I've seen this quite a few times recently, as of 3.1. > Last night in my machine (Symbios 875 & 895 COntrollers) > and two weeks ago in a customers machine (HP Netserver with build in > Adaptec EISA controller) > > > I'll try to reproduce it this weekend at home and file a pr. Have you guys tried increasing: options SCSI_DELAY to something really high? options SCSI_DELAY=30000 how about enabling DDB and seeing where it is stuck? -Alfred > > -- > Robert Sexton, robert@kudra.com > FreeBSD - Quality BSD UNIX for Intel and Alpha that you don't > have to shave your head to use. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:37:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.web-tic.com (ns.web-tic.com [194.109.18.33]) by hub.freebsd.org (Postfix) with ESMTP id 85A85151E1 for ; Fri, 5 Mar 1999 09:37:37 -0800 (PST) (envelope-from paulj@ns.web-tic.com) Received: (from paulj@localhost) by ns.web-tic.com (8.9.1a/8.8.2) id SAA29317; Fri, 5 Mar 1999 18:18:56 +0100 (MET) From: Paul Jongsma Message-Id: <199903051718.SAA29317@ns.web-tic.com> Subject: Compaq SMART on 3.1 To: freebsd-hackers@freebsd.org Date: Fri, 5 Mar 1999 18:18:55 +0100 (MET) Cc: paulj@webtic.com, md@doc.ic.ac.uk Reply-To: paulj@webtic.com X-Mailer: ELM [version 2.4ME+ PL31 (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 Is anyone using the IDA driver for the Compaq SMART array controller on 3.1-RELEASE? The drivers at http://www.doc.ic.ac.uk/~md/ida compile fine and the installation is succesfull. However copying any file of >100 Kb or so gives a kernel panic. If anyone is using this driver on 3.1 without any problems I'd like to compare configs. Thanks, Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:49:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 4D60D151C5 for ; Fri, 5 Mar 1999 09:49:40 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id KAA06585; Fri, 5 Mar 1999 10:49:21 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd006547; Fri Mar 5 10:49:17 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id KAA08647; Fri, 5 Mar 1999 10:49:15 -0700 (MST) From: Terry Lambert Message-Id: <199903051749.KAA08647@usr06.primenet.com> Subject: Re: lockf and kernel threads To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 17:49:15 +0000 (GMT) Cc: dyson@iquest.net, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903050606.WAA65635@rah.star-gate.com> from "Amancio Hasty" at Mar 4, 99 10:06:54 pm X-Mailer: ELM [version 2.4 PL25] 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 supposed that for a limited distinct events signals are really cool. No, they aren't. Signals are persistant conditions, not events. Otherwise I would be able to count them accurately. Right now, I can be counting one of them, queue another of the same signal, and all subsequent signals of that type are dropped on the floor. > If you can deliver a signal there is nothing to stop you from > delivering an AST provided that one can muster up the queuing > delivery mechanism which is not that much different than the > beloved old fashion signal delivery mechanism. Actually, AST's run in a mode between supervisor and user. The x86 handles this (the infrequently used "ring 1" and "ring 2", but other processor architectures do not. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:55:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 762951522C for ; Fri, 5 Mar 1999 09:55:10 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id JAA81858; Fri, 5 Mar 1999 09:53:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903051753.JAA81858@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Plevyak Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 08:06:18 PST." <19990305080618.B22589@tsdev.inktomi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 09:53:37 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am missing context on this, however if it was a mechanism for > generalized async calls w/o signals/polling but 'wait for one > of N events' I am interested. Yes that is what Terry is reffering to and some like to think about it as old fashion and not to be use technology . A system which widely use Terry's "async call gate" is DEC's VMS QIO mechanism which allow applications to issue async calls for system calls . I once help developed an OSI FTAM file server to handle multiple file requests all in one process. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 9:59:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 4588C14A2F for ; Fri, 5 Mar 1999 09:59:32 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id JAA81871; Fri, 5 Mar 1999 09:57:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903051757.JAA81871@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert Cc: dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 17:49:15 GMT." <199903051749.KAA08647@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 09:57:43 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You are right ! However, I was thinking about the set of signals which user has available to use . SIGFPE, SIGIO, etc... Amancio > > I supposed that for a limited distinct events signals are really cool. > > No, they aren't. > > Signals are persistant conditions, not events. Otherwise I would be > able to count them accurately. Right now, I can be counting one of > them, queue another of the same signal, and all subsequent signals > of that type are dropped on the floor. > > > > If you can deliver a signal there is nothing to stop you from > > delivering an AST provided that one can muster up the queuing > > delivery mechanism which is not that much different than the > > beloved old fashion signal delivery mechanism. > > Actually, AST's run in a mode between supervisor and user. The x86 > handles this (the infrequently used "ring 1" and "ring 2", but other > processor architectures do not. > or previous employers. Thats a kernel implementation issue and not necessarily a platform specific feature assuming that the platform can do multitasking . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:16:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 05EEE152EA for ; Fri, 5 Mar 1999 10:16:41 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA03611; Fri, 5 Mar 1999 11:16:24 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd003588; Fri Mar 5 11:16:20 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id LAA10950; Fri, 5 Mar 1999 11:16:18 -0700 (MST) From: Terry Lambert Message-Id: <199903051816.LAA10950@usr06.primenet.com> Subject: Re: lockf and kernel threads To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 18:16:18 +0000 (GMT) Cc: tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903051757.JAA81871@rah.star-gate.com> from "Amancio Hasty" at Mar 5, 99 09:57:43 am X-Mailer: ELM [version 2.4 PL25] 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 > > Actually, AST's run in a mode between supervisor and user. The x86 > > handles this (the infrequently used "ring 1" and "ring 2", but other > > processor architectures do not. > > or previous employers. > > Thats a kernel implementation issue and not necessarily a platform specific > feature assuming > that the platform can do multitasking . It was my understanding that it had to run in the user's process on potentially N alternate stacks, simultaneously, if an AST fires while an AST is filiring. Basically, ring 2 is used to supply th stack and the program counter. I think you could queue it, but you would lose your interleave. I think that completion functions are less useful than select type functions. For VMS, this would be SYS$WAITEFLOR, which waits for an event flag to be set by an AST callback into event-flag-setting code. You have to use a "wait for completion" interface of some kind if you intend to implement threads, since, the wait is the top of the call conversion scheduler pyramid. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:24:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 72B9315205 for ; Fri, 5 Mar 1999 10:23:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA49114; Fri, 5 Mar 1999 10:23:39 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 10:23:39 -0800 (PST) From: Matthew Dillon Message-Id: <199903051823.KAA49114@apollo.backplane.com> To: Terry Lambert Cc: hasty@rah.star-gate.com (Amancio Hasty), tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads References: <199903051816.LAA10950@usr06.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Two things. First, ASTs were a VAXen thing and must be 'simulated' on every other architecture, including intel. Second, Intel's ring architecture is 100% *broken*. The only useful rings are ring 0 and ring 3. That's it. The intermediate rings are no better then a glorified user mode because most privilaged instructions cannot be run in them. Matthew Dillon :> > Actually, AST's run in a mode between supervisor and user. The x86 :> > handles this (the infrequently used "ring 1" and "ring 2", but other :> > processor architectures do not. :> > or previous employers. :> :> Thats a kernel implementation issue and not necessarily a platform specific :> feature assuming :> that the platform can do multitasking . : :It was my understanding that it had to run in the user's process on :potentially N alternate stacks, simultaneously, if an AST fires :while an AST is filiring. : :Basically, ring 2 is used to supply th stack and the program counter. : :I think you could queue it, but you would lose your interleave. : :I think that completion functions are less useful than select type :functions. For VMS, this would be SYS$WAITEFLOR, which waits for :an event flag to be set by an AST callback into event-flag-setting :code. : :You have to use a "wait for completion" interface of some kind if :... : Terry Lambert : terry@lambert.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:31:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 20B6B15188 for ; Fri, 5 Mar 1999 10:31:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA82072; Fri, 5 Mar 1999 10:29:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903051829.KAA82072@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert Cc: dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 18:16:18 GMT." <199903051816.LAA10950@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 10:29:54 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Basically, ring 2 is used to supply th stack and the program counter. > > I think you could queue it, but you would lose your interleave. I think that we can use some sort of heuristic to provide interleaving. > I think that completion functions are less useful than select type > functions. For VMS, this would be SYS$WAITEFLOR, which waits for > an event flag to be set by an AST callback into event-flag-setting > code. > > You have to use a "wait for completion" interface of some kind if > you intend to implement threads, since, the wait is the top of the > call conversion scheduler pyramid. You have a good point however wouldn't prioritized ASTs be able to accomplish same thing? Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:35: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 5A866151DD for ; Fri, 5 Mar 1999 10:35:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id KAA82111; Fri, 5 Mar 1999 10:33:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903051833.KAA82111@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: Terry Lambert , dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 10:23:39 PST." <199903051823.KAA49114@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 10:33:23 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Two things. > > First, ASTs were a VAXen thing and must be 'simulated' on every other > architecture, including intel. Well, if we adhere to the strict sense of the word you are probably correct. I would say that asynchronous delivery of events mechanism is NOT only a VAX thing. > Second, Intel's ring architecture is 100% *broken*. The only useful > rings are ring 0 and ring 3. That's it. The intermediate rings are no > better then a glorified user mode because most privilaged instructions > cannot be run in them. Thats probably true however for delivery of an AST I don't thing that we need priviliged instructions --- I could be wrong. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:41:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CE30A151D4 for ; Fri, 5 Mar 1999 10:41:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA49799; Fri, 5 Mar 1999 10:41:07 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 10:41:07 -0800 (PST) From: Matthew Dillon Message-Id: <199903051841.KAA49799@apollo.backplane.com> To: Amancio Hasty Cc: Terry Lambert , dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG Subject: Re: lockf and kernel threads References: <199903051833.KAA82111@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> rings are ring 0 and ring 3. That's it. The intermediate rings are no :> better then a glorified user mode because most privilaged instructions :> cannot be run in them. : :Thats probably true however for delivery of an AST I don't thing that we :need priviliged instructions --- I could be wrong. : : Amancio Little things like, ohhhhh disabling interrupts. Accessing the MMU registers, flushing the TLB, etc..... believe me, ring 1 and ring 2 is utterly useless for anything FreeBSD wants to run in supervisor mode. 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 Mar 5 10:53:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.42]) by hub.freebsd.org (Postfix) with ESMTP id 2C0E8151FE for ; Fri, 5 Mar 1999 10:53:13 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.2/8.9.1) id MAA27415; Fri, 5 Mar 1999 12:51:57 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 5 Mar 1999 12:51:56 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: hackers@freebsd.org Subject: base64 X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14048.10089.598598.919239@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Julian Elischer : : the patch is in base64.. : how do you read base64 files? This raises a good point: The base system should include mechanisms for MIME. It's rather basic. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:54:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 5205E15219 for ; Fri, 5 Mar 1999 10:54:09 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 25499 invoked from network); 5 Mar 1999 18:53:49 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 18:53:49 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id NAA00631; Fri, 5 Mar 1999 13:53:50 -0500 (EST) Message-Id: <199903051853.NAA00631@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903050606.WAA65635@rah.star-gate.com> from Amancio Hasty at "Mar 4, 99 10:06:54 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 13:53:50 -0500 (EST) Cc: dyson@iquest.net, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Amancio Hasty said: > > I supposed that for a limited distinct events signals are really cool. > > If you can deliver a signal there is nothing to stop you from delivering an > AST provided > that one can muster up the queuing delivery mechanism which is not that much > different than the beloved old fashion signal delivery mechanism. > > Does the current AIO implementation for an async call create s a thread per > call? > For raw I/O, it uses hooks into the I/O mechanisms, so it doesn't need to create threads. (Actually, close to how a realtime kernel would work.) For other I/O, it dynamically creates thread pools, and uses threads as needed. Threads don't end up being created and destroyed that often, because the requests are handled dynamically by the threads, and the threads dynamically attach/detach to the process address space. If the threads don't get used for a long time, they start disappearing. The scheme sort-of creates anonymous threads that are used as resources for multiple processes. Eventually, most of the I/O types won't have to be threaded, but the thread scheme is a concept proof of the ability to create anonymous workers in the BSD kernel. (Actually, the thread work was much more complex than the RAW I/O.) -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 10:59:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penmax.com (cc595093-a.mdltwn1.nj.home.com [24.3.192.38]) by hub.freebsd.org (Postfix) with ESMTP id E637D151DD for ; Fri, 5 Mar 1999 10:59:30 -0800 (PST) (envelope-from vincef@penmax.com) Received: from rembrandt (rembrandt.penmax.com [10.1.3.2]) by penmax.com (8.8.8/8.8.8) with SMTP id OAA00404; Fri, 5 Mar 1999 14:02:06 -0500 (EST) (envelope-from vincef@penmax.com) Received: by rembrandt with Microsoft Mail id <01BE6710.A0EEE120@rembrandt>; Fri, 5 Mar 1999 14:01:13 -0500 Message-ID: <01BE6710.A0EEE120@rembrandt> From: Vincent Fleming To: "'Andy Doran'" Cc: "'hackers@freebsd.org'" Subject: RE: samba performance Date: Fri, 5 Mar 1999 14:01:12 -0500 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 Very strange... but mounting the filesystems asynch has no effect. I'll have to look through the code to see if smbd is creating the files with O_SYNC or something. I would think mounting the filesystems async would make a difference. Hmm... I thought we had it there! Vince You could mount your filesystems with the async flag. Search the mailing list archive (of hackers) for the last two months for caveats and more information. Andy. On Fri, 5 Mar 1999, Vincent Fleming wrote: > Hi; > > I've bee playing around with smbd, trying to adjust the performance. > > I seem to be getting around 2200k/s (2MB/s) on reads, but only 315k/s > on writes! > > Now, that's a BIG difference. > > I've been going over the docs, and have tried all the suggestions in there > for increasing performance. Does anyone out there have any more > suggestions on how I can get the write performance to more closely resemble > the read performance? > > I have the sources, and have enabled MMAP use, among other things. So, > if any suggestions involve hacking the server, don't hesitate mentioning them! > > My server: (yeah, I know, I should use a better machine! It's pretty fast, though) > AMD K6 233 > 64 MB RAM > Buslogic PCI Fast/Wide SCSI card > Seagate Barracuda ST12550N Fast/Narrow 2GB drive > 3com 905B PCI 100 base T ethernet > FreeBSD 2.2.7 > > My Client: > PII 300 > 320 MB RAM > Adaptec 2940UW SCSI > Seagate Barracuda ST32171W Ultra Wide 2GB drive > 3 com 905B PCI 100 base T ethernet > Win98 > > They are directly connected with a cross-over 100 baseT cable, so they're > running full-duplex. > > Thanks for any suggestions! > > Vince Fleming > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11: 3: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id F35F8151BB for ; Fri, 5 Mar 1999 11:03:07 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 4897 invoked from network); 5 Mar 1999 19:02:47 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 19:02:47 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id OAA00724; Fri, 5 Mar 1999 14:02:36 -0500 (EST) Message-Id: <199903051902.OAA00724@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903051841.KAA49799@apollo.backplane.com> from Matthew Dillon at "Mar 5, 99 10:41:07 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 5 Mar 1999 14:02:36 -0500 (EST) Cc: hasty@rah.star-gate.com, tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon said: > : > :Thats probably true however for delivery of an AST I don't thing that we > :need priviliged instructions --- I could be wrong. > : > : Amancio > > Little things like, ohhhhh disabling interrupts. Accessing the MMU > registers, flushing the TLB, etc..... believe me, ring 1 and ring 2 > is utterly useless for anything FreeBSD wants to run in supervisor mode. > AST's could be simulated, but it is just more hair added to an already sufficient set of hair. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:13:38 1999 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 1C55F15206 for ; Fri, 5 Mar 1999 11:13:28 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10IzxR-0002tJ-00; Fri, 5 Mar 1999 19:08:26 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10IzyX-00004p-00; Fri, 5 Mar 1999 19:09:33 +0000 Date: Fri, 5 Mar 1999 19:09:33 +0000 (GMT) From: Andy Doran To: Bernd Walter Cc: sthaug@nethelp.no, stephw@xs4all.nl, freebsd-hackers@FreeBSD.ORG Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: <19990305174344.A85423@cicely7.cicely.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that this is an issue with CAM. I have a bunch of DEC RZ25 disks here which work fine with ULTRIX, NetBSD and Linux on several different machines. After upgrading from FreeBSD-2.2.6 to 3.0 (and -current) the system hangs on boot whenever an RZ25 is hooked up. This is with a crappy 'ol Adaptec 1542CP controller. Andy. > > > We now got 3 boxes converted from bsdi to freebsd 3.1R with two > > > adaptec 2940U2W with Seagate ST39102 ultra2lv disks. We tried > > > attaching only one outside disk to only one controller but the > > > problem still persists. Once in a while freebsd will not boot, but > > > hang during boot up, after 'waiting for scsi devices to settle.' > > > We tried the same controller with the same scsi setup, and the same > > > disks in a linux box and the problem didnt occur, so it's definetely > > > some freebsd problem. > > > > > > Is this problem known yet, and is there some fix for it ? > > > > A possibly related problem we've seen here: FreeBSD sometimes needs a > > hard reset (hit reset button) to reboot, while a software reboot will > > hang during bootup. > > > > This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec > > 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, > > *and* DAT on single-ended chain. Using verbose boot, we see that the > > hang occurs while probing the DAT and/or the CDROM player on the SE > > chain. > > > I also seeing this kind of problem on 3 independent ASUS P2BLS Boards. > Another board (Maybe later revision) is not showing this. > We have tried a bios update and several FreeBSD Versions including some > 4.0-current - but the problem still exists. > I remember that boot -v showed something that I wanted to send to the > FreeBSD-SCSI list - but I didn't yet because I don't have it logged. > It stopped after probing some but not all drives before it would print the > non -v informations. > I expect this problem has something to do with the aic revision on that boards. > I'll try to get the boot -v informations and the revision next week. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:15:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from exchange-server.modacad.com (fw.modacad.com [207.199.66.93]) by hub.freebsd.org (Postfix) with ESMTP id 68C2315203; Fri, 5 Mar 1999 11:15:05 -0800 (PST) (envelope-from MattL@ModaCAD.com) Message-ID: From: Matt Liu To: "'smp@freebsd.org'" Cc: "'freebsd-hackers@freebsd.org'" Subject: why vm is rewriten much? Date: Fri, 5 Mar 1999 11:14:01 -0800 MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys: One of the question is pondering on me is that why the Mach vm is much changed. From what version it's changed, is it from 2.2.8, 2.2.7. Look like 2.2.5 isn't changed much. I heard Mach vm support SMP. UNIX/NT ADM @ModaCad Inc. A Berkeley follower To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:17:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 44DC0151ED for ; Fri, 5 Mar 1999 11:17:43 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA17560; Fri, 5 Mar 1999 11:13:50 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdr17555; Fri Mar 5 19:13:47 1999 Date: Fri, 5 Mar 1999 11:13:44 -0800 (PST) From: Julian Elischer To: Vincent Fleming Cc: "'Andy Doran'" , "'hackers@freebsd.org'" Subject: RE: samba performance In-Reply-To: <01BE6710.A0EEE120@rembrandt> 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 really should ask the SAMBA mailing list as well. On Fri, 5 Mar 1999, Vincent Fleming wrote: > > Very strange... but mounting the filesystems asynch has no effect. > > I'll have to look through the code to see if smbd is creating the files > with O_SYNC or something. I would think mounting the filesystems > async would make a difference. Hmm... I thought we had it there! > > Vince > > > > You could mount your filesystems with the async flag. Search the mailing > list archive (of hackers) for the last two months for caveats and more > information. > > > Andy. > > On Fri, 5 Mar 1999, Vincent Fleming wrote: > > > Hi; > > > > I've bee playing around with smbd, trying to adjust the performance. > > > > I seem to be getting around 2200k/s (2MB/s) on reads, but only 315k/s > > on writes! > > > > Now, that's a BIG difference. > > > > I've been going over the docs, and have tried all the suggestions in there > > for increasing performance. Does anyone out there have any more > > suggestions on how I can get the write performance to more closely resemble > > the read performance? > > > > I have the sources, and have enabled MMAP use, among other things. So, > > if any suggestions involve hacking the server, don't hesitate mentioning them! > > > > My server: (yeah, I know, I should use a better machine! It's pretty fast, though) > > AMD K6 233 > > 64 MB RAM > > Buslogic PCI Fast/Wide SCSI card > > Seagate Barracuda ST12550N Fast/Narrow 2GB drive > > 3com 905B PCI 100 base T ethernet > > FreeBSD 2.2.7 > > > > My Client: > > PII 300 > > 320 MB RAM > > Adaptec 2940UW SCSI > > Seagate Barracuda ST32171W Ultra Wide 2GB drive > > 3 com 905B PCI 100 base T ethernet > > Win98 > > > > They are directly connected with a cross-over 100 baseT cable, so they're > > running full-duplex. > > > > Thanks for any suggestions! > > > > Vince Fleming > > > > > > > > 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 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:25: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id 693ED151F7 for ; Fri, 5 Mar 1999 11:24:50 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id UAA04118; Fri, 5 Mar 1999 20:30:54 +0100 (CET) Message-Id: <199903051930.UAA04118@rt2.synx.com> Date: Fri, 5 Mar 1999 20:22:47 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: RE: samba performance To: vincef@penmax.com Cc: ad@psn.ie, hackers@FreeBSD.ORG In-Reply-To: <01BE6710.A0EEE120@rembrandt> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 Mar, Vincent Fleming wrote: > > Very strange... but mounting the filesystems asynch has no effect. > > I'll have to look through the code to see if smbd is creating the files > with O_SYNC or something. I would think mounting the filesystems > async would make a difference. Hmm... I thought we had it there! > > Vince Have you checked, using a tcpdump trace, that you are not yet another victim of the TCP delayed ack ? RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:27:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penmax.com (cc595093-a.mdltwn1.nj.home.com [24.3.192.38]) by hub.freebsd.org (Postfix) with ESMTP id A0721151F7 for ; Fri, 5 Mar 1999 11:27:13 -0800 (PST) (envelope-from vincef@penmax.com) Received: from rembrandt (rembrandt.penmax.com [10.1.3.2]) by penmax.com (8.8.8/8.8.8) with SMTP id OAA01610; Fri, 5 Mar 1999 14:30:25 -0500 (EST) (envelope-from vincef@penmax.com) Received: by rembrandt with Microsoft Mail id <01BE6714.958E7260@rembrandt>; Fri, 5 Mar 1999 14:29:31 -0500 Message-ID: <01BE6714.958E7260@rembrandt> From: Vincent Fleming To: "'Julian Elischer'" Cc: "'hackers@freebsd.org'" Subject: RE: samba performance Date: Fri, 5 Mar 1999 14:29:31 -0500 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 Sorry, didn' know there was a samba mailing list. I found the problem, though. It seems that the server is fsync()'ing all the time. I set -DNO_FSYNC (disables the fsync code), and the write performance went up to about 2MB/s. Much better. I guess I'll be looking into why the default of not sync'ing all the time isn't working... the code's full of #defines and is going to take some time to go through. Meanwhile, the FreeBSD's on a UPS, so I don't think I should worry about it much. I think I'll just leave it as is until I find the time to look further into it. Thanks everyone, Vince you really should ask the SAMBA mailing list as well. On Fri, 5 Mar 1999, Vincent Fleming wrote: > > Very strange... but mounting the filesystems asynch has no effect. > > I'll have to look through the code to see if smbd is creating the files > with O_SYNC or something. I would think mounting the filesystems > async would make a difference. Hmm... I thought we had it there! > > Vince > > > > You could mount your filesystems with the async flag. Search the mailing > list archive (of hackers) for the last two months for caveats and more > information. > > > Andy. > > On Fri, 5 Mar 1999, Vincent Fleming wrote: > > > Hi; > > > > I've bee playing around with smbd, trying to adjust the performance. > > > > I seem to be getting around 2200k/s (2MB/s) on reads, but only 315k/s > > on writes! > > > > Now, that's a BIG difference. > > > > I've been going over the docs, and have tried all the suggestions in there > > for increasing performance. Does anyone out there have any more > > suggestions on how I can get the write performance to more closely resemble > > the read performance? > > > > I have the sources, and have enabled MMAP use, among other things. So, > > if any suggestions involve hacking the server, don't hesitate mentioning them! > > > > My server: (yeah, I know, I should use a better machine! It's pretty fast, though) > > AMD K6 233 > > 64 MB RAM > > Buslogic PCI Fast/Wide SCSI card > > Seagate Barracuda ST12550N Fast/Narrow 2GB drive > > 3com 905B PCI 100 base T ethernet > > FreeBSD 2.2.7 > > > > My Client: > > PII 300 > > 320 MB RAM > > Adaptec 2940UW SCSI > > Seagate Barracuda ST32171W Ultra Wide 2GB drive > > 3 com 905B PCI 100 base T ethernet > > Win98 > > > > They are directly connected with a cross-over 100 baseT cable, so they're > > running full-duplex. > > > > Thanks for any suggestions! > > > > Vince Fleming > > > > > > > > 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 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:37:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 5544615219 for ; Fri, 5 Mar 1999 11:37:20 -0800 (PST) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id UAA15838; Fri, 5 Mar 1999 20:36:50 +0100 (CET) Message-Id: <199903051936.UAA15838@midten.fast.no> To: jplevyak@inktomi.com Cc: hackers@FreeBSD.ORG Subject: Re: aio_read/write pread/pwrite From: Tor.Egge@fast.no In-Reply-To: Your message of "Thu, 4 Mar 1999 16:58:18 -0800" References: <19990304165818.A20680@proxydev.inktomi.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 05 Mar 1999 20:36:50 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In investigating the lack of pread/pwrite, I found the bug > report kern/8011, and the patch therein. NetBSD has allocated some syscall numbers for pread, pwrite, preadv and pwritev. We should use the same syscall interface (same syscall numbers and parameter alignment) for those functions. This means that offset should be 64-bit aligned, as is the case with the lseek system call. Extra wrappers in the C library should probably be present (/usr/src/lib/libc/sys should contain a pread.c and a pwrite.c) In NetBSD, the prototype for vn_read and vn_write has changed (a pointer to an offset and a flag has been added). That is a cleaner approach, but requires changes throughout the source tree. Common parts has also been split out into separate subroutines in NetBSD: read, pread uses dofileread readv, preadv uses dofilereadv write, pwrite uses dofilewrite writev, pwritev uses dofilewritev - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:47:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id DCA8C1522D for ; Fri, 5 Mar 1999 11:47:19 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18701; Fri, 5 Mar 1999 11:38:27 -0800 (PST) Received: from crab.whistle.com(207.76.205.112), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpdd18691; Fri Mar 5 19:38:21 1999 Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id LAA27004; Fri, 5 Mar 1999 11:37:42 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199903051937.LAA27004@whistle.com> Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: from Andy Doran at "Mar 5, 99 07:09:33 pm" To: ad@psn.ie (Andy Doran) Date: Fri, 5 Mar 1999 11:37:42 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Andy Doran writes: | I believe that this is an issue with CAM. I have a bunch of DEC RZ25 disks | here which work fine with ULTRIX, NetBSD and Linux on several different | machines. After upgrading from FreeBSD-2.2.6 to 3.0 (and -current) | the system hangs on boot whenever an RZ25 is hooked up. This is with a | crappy 'ol Adaptec 1542CP controller. Most DEC drives as shipped with DEC system do not spin up on power up (for sure not in the era of the RZ25). I recall that some DEC drives had a jumper to select spin up on power up but I don't think all of them did. I think they was also a mode page switch. I also recall that the 1542 BIOS had options to send the command to spin up on power up. Things to look at. A long time ago I ran DEC drives on FreeBSD 1.5/2.0 when I had easy access to them. So I ran into these problems. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 11:54: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assurance.rstcorp.com (unknown [206.29.49.3]) by hub.freebsd.org (Postfix) with ESMTP id 943091522D for ; Fri, 5 Mar 1999 11:54:03 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id OAA03317; Fri, 5 Mar 1999 14:53:45 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma003303; Fri, 5 Mar 99 14:52:49 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id OAA23890; Fri, 5 Mar 1999 14:52:47 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.3/8.8.8) id OAA59557; Fri, 5 Mar 1999 14:52:47 -0500 (EST) Date: Fri, 5 Mar 1999 14:52:47 -0500 (EST) Message-Id: <199903051952.OAA59557@jabberwock.rstcorp.com> From: "Viren R. Shah" To: paulj@webtic.com Cc: freebsd-hackers@freebsd.org Subject: Re:Compaq SMART on 3.1 In-Reply-To: <199903051718.SAA29317@ns.web-tic.com> References: <199903051718.SAA29317@ns.web-tic.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Paul" == Paul Jongsma writes: Paul> Is anyone using the IDA driver for the Compaq SMART array controller Paul> on 3.1-RELEASE? The drivers at http://www.doc.ic.ac.uk/~md/ida Paul> compile fine and the installation is succesfull. However copying Paul> any file of >100 Kb or so gives a kernel panic. I'm using it on -current. It works great. The machine is an old Compaq ProLiant 2000 (IIRC). I run make worlds on it every day. Is yours an EISA machine? I know I had to put in a couple of minor hacks to get mine to work probe correctly (but that doesn't sound like what you are experiencing). Paul> Thanks, Paul> Paul. Viren -- Viren R. Shah | viren@rstcorp.com Research Associate | viren@viren.org Reliable Software Technologies | http://www.rstcorp.com/~vshah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12: 1:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 8EEBA15210 for ; Fri, 5 Mar 1999 12:01:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id LAA82525; Fri, 5 Mar 1999 11:59:55 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903051959.LAA82525@rah.star-gate.com> To: Matthew Dillon Cc: Amancio Hasty , Terry Lambert , dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 10:41:07 PST." <199903051841.KAA49799@apollo.backplane.com> Date: Fri, 05 Mar 1999 11:59:55 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Little things like, ohhhhh disabling interrupts. Accessing the MMU And I supposed that we can not provide a mechanism or layer to deliver AST which does not require disabling interrupts, etc... Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12: 2: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 51A7B15259 for ; Fri, 5 Mar 1999 12:02:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA51599; Fri, 5 Mar 1999 12:01:37 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 12:01:37 -0800 (PST) From: Matthew Dillon Message-Id: <199903052001.MAA51599@apollo.backplane.com> To: freebsd-hackers@FreeBSD.ORG, nsouch@teaser.fr, des@flood.ping.uio.no Subject: new ppbus driver problem Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is with -current. I've been getting crashes during boot with the new ppbus stuff and lpt0 enabled. It detects the parallel port just fine, but further on in the boot sequence the system gets an RTC error and then it just locks up completely... it doesn't even get past the kernel config ( never gets to execing init ). I was able to solve the problem by commenting out most of the probe code in i386/isa/ppc.c, as shown below. I don't know which port in the probe code is causing the problem, but something in there is blowing up my systems. Maybe the probe code should be a little more conservative, with a kernel config option to be less conservative ???? -Matt Matthew Dillon static int ppc_detect(struct ppc_data *ppc, int chipset_mode) { int i, mode; /* list of supported chipsets */ int (*chipset_detect[])(struct ppc_data *, int) = { #if 0 ppc_pc873xx_detect, ppc_smc37c66xgt_detect, ppc_w83877f_detect, #endif ppc_generic_detect, NULL }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12: 5: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B93BC15299 for ; Fri, 5 Mar 1999 12:04:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA52547; Fri, 5 Mar 1999 12:04:33 -0800 (PST) (envelope-from dillon) Date: Fri, 5 Mar 1999 12:04:33 -0800 (PST) From: Matthew Dillon Message-Id: <199903052004.MAA52547@apollo.backplane.com> To: Amancio Hasty Cc: Terry Lambert , dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: lockf and kernel threads References: <199903051959.LAA82525@rah.star-gate.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> Little things like, ohhhhh disabling interrupts. Accessing the MMU : :And I supposed that we can not provide a mechanism or layer to deliver :AST which does not require disabling interrupts, etc... : : Amancio Not unless you want to rewrite the kernel. But it's actually more the inability to access the MMU, cache control, and other priv instructions that pretty much trashes the usefullness of ring 1 & 2. -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 Mar 5 12:15:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 165E415151 for ; Fri, 5 Mar 1999 12:14:57 -0800 (PST) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id VAA18648; Fri, 5 Mar 1999 21:14:35 +0100 (CET) Message-Id: <199903052014.VAA18648@midten.fast.no> To: sthaug@nethelp.no Cc: stephw@xs4all.nl, freebsd-hackers@FreeBSD.ORG Subject: Re: adaptec 2940u2w hangs on external disks From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 05 Mar 1999 17:02:35 +0100" References: <22812.920649755@verdi.nethelp.no> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 05 Mar 1999 21:14:35 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A possibly related problem we've seen here: FreeBSD sometimes needs a > hard reset (hit reset button) to reboot, while a software reboot will > hang during bootup. > > This happens on FreeBSD boxes with 3.1R or 3.1-STABLE, onboard Adaptec > 7890 U2W controller. Various (Seagate, IBM) LVD disks on LVD chain, > *and* DAT on single-ended chain. Using verbose boot, we see that the > hang occurs while probing the DAT and/or the CDROM player on the SE > chain. I've also noticed this problem. Having more disks on a machines gives a higher probability of a hang. I'm using a serial console and options BREAK_TO_DEBUGGER in the kernel config file. Sending a break to enter the kernel debugger does not work when the hang has occured. The virtual NMI pushbutton does not work when the hang has occured (SMP kernel, IOAPIC reprogrammed to treat irq 3 as NMI to be delivered to CPU#0). Programming CPU#1 to run with interrupts disabled (and lapic.tpr set to 255) sending about 100K IPIs/second to CPU#0 for sampling the program counter at CPU#0 does not help. CPU#1 stops running when the hang occurs: e0122535 -> scsi_interpret_sense+0x1 e011e59c -> xpt_release_devq+0x4 e012ff21 -> ahc_action+0x1 e021a002 -> splcam+0x46 e01306a1 -> ahc_action+0x781 e011f983 -> xpt_set_transfer_settings+0x7b e01302fb -> ahc_action+0x3db e012b501 -> ahc_find_syncrate+0x1 e012b6ea -> ahc_update_target_msg_request+0xce HANG e0122586 -> scsi_interpret_sense+0x52 e014725e -> free+0x3a e0130462 -> ahc_action+0x542 e011f923 -> xpt_set_transfer_settings+0x1b e022aefa -> strncpy+0x16 e011f9e3 -> xpt_set_transfer_settings+0xdb e0219fbc -> splcam+0x0 e012b501 -> ahc_find_syncrate+0x1 e012b6e7 -> ahc_update_target_msg_request+0xcb HANG Going back to an UP kernel, adding limited debug output has resulted in the following reconstructed call stacks when the hang occurs: camisr probedone xpt_action xpt_set_transfer_settings ahc_action ahc_set_width ahc_update_target_msg_request unpause_sequencer and camisr probedone xpt_action xpt_set_transfer_settings ahc_action ahc_set_syncrate ahc_update_target_msg_request unpause_sequencer where ahc_inb(ahc, INTSTAT) in unpause_sequencer seems to hang. removing AHC_ALLOW_MEMIO from the kernel configuration file caused the hang to occur a few lines earlier (while setting new value for TARGET_MSG_REQUEST or TARGET_MSG_REQUEST + 1). I'm using a modified splvm (which blocks cam interrupts) and a modified splsoftcam (which blocks cam interrupts during device probing), but this does not prevent the hangs. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12:22:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id 25C6315243 for ; Fri, 5 Mar 1999 12:22:21 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 26927 invoked from network); 5 Mar 1999 20:21:42 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 5 Mar 1999 20:21:42 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id PAA00372; Fri, 5 Mar 1999 15:21:41 -0500 (EST) Message-Id: <199903052021.PAA00372@y.dyson.net> Subject: Re: lockf and kernel threads In-Reply-To: <199903052004.MAA52547@apollo.backplane.com> from Matthew Dillon at "Mar 5, 99 12:04:33 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 5 Mar 1999 15:21:41 -0500 (EST) Cc: hasty@rah.star-gate.com, tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon said: > > : > :> Little things like, ohhhhh disabling interrupts. Accessing the MMU > : > :And I supposed that we can not provide a mechanism or layer to deliver > :AST which does not require disabling interrupts, etc... > : > : Amancio > > Not unless you want to rewrite the kernel. But it's actually more the > inability to access the MMU, cache control, and other priv instructions > that pretty much trashes the usefullness of ring 1 & 2. > (Unless you want to create an API that supports that in ring 0.) That would be more layers of abstraction :-(. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12:24: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id AB456152A0 for ; Fri, 5 Mar 1999 12:23:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA82649; Fri, 5 Mar 1999 12:22:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903052022.MAA82649@rah.star-gate.com> To: Matthew Dillon Cc: Amancio Hasty , Terry Lambert , dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 12:04:33 PST." <199903052004.MAA52547@apollo.backplane.com> Date: Fri, 05 Mar 1999 12:22:14 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not unless you want to rewrite the kernel. But it's actually more the We shall see if the above statement is true or not . In the mean time, with the intent to anchor the discussion in a positive direction , I ask Terry to produce a draft paper on how to implement ASTs on FreeBSD. Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12:27:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id D928715229 for ; Fri, 5 Mar 1999 12:27:45 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA13122; Fri, 5 Mar 1999 21:20:31 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA01199; Fri, 5 Mar 1999 21:01:15 +0100 (CET) From: Wilko Bulte Message-Id: <199903052001.VAA01199@yedi.iaf.nl> Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: <199903051937.LAA27004@whistle.com> from Doug Ambrisko at "Mar 5, 99 11:37:42 am" To: ambrisko@whistle.com (Doug Ambrisko) Date: Fri, 5 Mar 1999 21:01:15 +0100 (CET) Cc: ad@psn.ie, freebsd-hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As Doug Ambrisko wrote... > Andy Doran writes: > | I believe that this is an issue with CAM. I have a bunch of DEC RZ25 disks > | here which work fine with ULTRIX, NetBSD and Linux on several different > | machines. After upgrading from FreeBSD-2.2.6 to 3.0 (and -current) > | the system hangs on boot whenever an RZ25 is hooked up. This is with a > | crappy 'ol Adaptec 1542CP controller. > > Most DEC drives as shipped with DEC system do not spin up on power up > (for sure not in the era of the RZ25). I recall that some DEC drives > had a jumper to select spin up on power up but I don't think all of them RZ25 has a spinup jumper. Remove jumper 8 on J6 (for reference, jumper 5 & 7 should be left in) for spinup on powerup. > did. I think they was also a mode page switch. I also recall that the Yes, a vendor unique mode page setting. > 1542 BIOS had options to send the command to spin up on power up. Not all 1542, the 1542C can do it, the older ones don't IRRC. Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 12:46:34 1999 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 7A58515252 for ; Fri, 5 Mar 1999 12:46:15 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA16422; Fri, 5 Mar 1999 12:45:57 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA02016; Fri, 5 Mar 1999 12:45:56 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 5 Mar 1999 12:45:56 -0800 (PST) Message-Id: <199903052045.MAA02016@vashon.polstra.com> To: garyj@muc.de Subject: Re: brandelf (necessary?) In-Reply-To: <199903032249.XAA32433@peedub.muc.de> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903032249.XAA32433@peedub.muc.de>, Gary Jennejohn wrote: > Christoph Kukulies writes: > >In an environment where FreeBSD needs to run linux binaries > >that are shared with linux systems, would it do harm to brandelf > >these binaries? Or in other words, would it be possible for FreeBSD > >to autodetect that it's a linux ELF binary without having to brand it? > > > > as long as the linuxulator is loaded (linux.ko) it does not seem to be > necessary to brandelf Linux binaries. At least, that's been my experience. If the executables are dynamically linked, the image loader can normally guess their OS type based on the dynamic linker name that's stored in the executable file. But for statically-linked programs, a correct brand is necessary. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 14:16:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id 2F70914DD7 for ; Fri, 5 Mar 1999 14:15:33 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA15754 for ; Fri, 5 Mar 1999 17:15:14 -0500 (EST) Date: Fri, 5 Mar 1999 17:15:13 -0500 (EST) From: "Matthew N. Dodd" To: hackers@freebsd.org Subject: Reading a file inside the kernel. 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 have a driver that needs to read a file that will eventually be located somewhere in /boot. It is likely that this file will be determined by an additional configuration file, also located in /boot, but the configuration file will be loaded by the ELF bootstrap, so I don't need to worry about it. Any ideas on how to go about opening and reading the file? I suspect the answer may be buried somewhere in sys/dev/vn (the vnode driver) but I lack sufficient clue to recognize it. Thanks. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 14:25:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (Postfix) with ESMTP id 0232F15077 for ; Fri, 5 Mar 1999 14:25:23 -0800 (PST) (envelope-from mark.hannon@stockholm.mail.telia.com) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id XAA04351 for ; Fri, 5 Mar 1999 23:25:05 +0100 (CET) Received: from doorway.home.lan (t4o1p11.telia.com [195.67.240.191]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id XAA16551 for ; Fri, 5 Mar 1999 23:25:03 +0100 (CET) Received: from stockholm.mail.telia.com (putte.home.lan [192.168.255.2]) by doorway.home.lan (8.9.2/8.8.7) with ESMTP id XAA11418 for ; Fri, 5 Mar 1999 23:03:44 +0100 (CET) (envelope-from mark.hannon@stockholm.mail.telia.com) Message-ID: <36E054BE.EEE34881@stockholm.mail.telia.com> Date: Fri, 05 Mar 1999 23:03:43 +0100 From: Mark Hannon X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: could not fdopen() the new stderr: Invalid argument Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Ever since moving to 3.1 I have been having problems with Netscape, I occasionally get an error dialogue saying: could not fdopen() the new stderr: Invalid argument I can press OK and clear the message and proceed but I am wondering what it is. Any ideas? Rgds/Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 15: 4:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 6622814CC4 for ; Fri, 5 Mar 1999 15:04:29 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA25177; Fri, 5 Mar 1999 16:04:11 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd025104; Fri Mar 5 16:04:05 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id QAA05576; Fri, 5 Mar 1999 16:03:49 -0700 (MST) From: Terry Lambert Message-Id: <199903052303.QAA05576@usr06.primenet.com> Subject: Re: lockf and kernel threads To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 5 Mar 1999 23:03:48 +0000 (GMT) Cc: tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903051829.KAA82072@rah.star-gate.com> from "Amancio Hasty" at Mar 5, 99 10:29:54 am X-Mailer: ELM [version 2.4 PL25] 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 think that completion functions are less useful than select type > > functions. For VMS, this would be SYS$WAITEFLOR, which waits for > > an event flag to be set by an AST callback into event-flag-setting > > code. > > > > You have to use a "wait for completion" interface of some kind if > > you intend to implement threads, since, the wait is the top of the > > call conversion scheduler pyramid. > > You have a good point however wouldn't prioritized ASTs be able to accomplish > same thing? Actually, yes. Practically, though, even though select(2) can be used to implement I/O stream multiplexing, when use in combination with a finite state automaton, most programmers have a hard time getting their heads around non-procedural problem decomposition. Just like threads allow programmers to program linearly, making them popular even when they aren't strictly necessary (e.g. all non-SMP OS's, and many SMP OS's with poor architectures), I think that most programmers would find the non-linearity of AST priority juggling difficult to wrap their heads around. It's not that it's not possible, it's just that there are so few people who could program effectively in that model. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 15: 9:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles168.castles.com [208.214.165.168]) by hub.freebsd.org (Postfix) with ESMTP id 27FD814C35 for ; Fri, 5 Mar 1999 15:09:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA06871; Fri, 5 Mar 1999 15:03:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903052303.PAA06871@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Vince Vielhaber Cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Fixing dlopen, ld.so, and upgrading the resolver In-reply-to: Your message of "Tue, 02 Mar 1999 06:32:28 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 15:03:31 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If the arhives are down, try www.egroups.com instead. They have a pretty good interface. > On Tue, 2 Mar 1999, Terry Lambert wrote: > > > Instructions on what to change are so old they have fallen out of my > > brain; see the -current list archives, using "mount" and "root" as > > search terms. > > Mail archives are still down. Anyone have an idea when they'll > be back? > > Vince. > -- > ========================================================================== > Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null > # include TEAM-OS2 > Online Campground Directory http://www.camping-usa.com > Online Giftshop Superstore http://www.cloudninegifts.com > ========================================================================== > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 5 15:31:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 07C0914F0A for ; Fri, 5 Mar 1999 15:31:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id PAA83315; Fri, 5 Mar 1999 15:30:11 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903052330.PAA83315@rah.star-gate.com> To: Terry Lambert Cc: hasty@rah.star-gate.com (Amancio Hasty), dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: lockf and kernel threads In-reply-to: Your message of "Fri, 05 Mar 1999 23:03:48 GMT." <199903052303.QAA05576@usr06.primenet.com> Date: Fri, 05 Mar 1999 15:30:11 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It's not that it's not possible, it's just that there are so few >people who could program effectively in that model. Thats not necessesarily a problem given that the intended target functionality (extreme high performance servers ) is really for a selected few with hopefully a justifiable intent. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 16: 0:43 1999 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 A14E51528C for ; Fri, 5 Mar 1999 16:00:16 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10J4Eh-0002zV-00; Fri, 5 Mar 1999 23:42:31 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10J4Fl-00004U-00; Fri, 5 Mar 1999 23:43:37 +0000 Date: Fri, 5 Mar 1999 23:43:37 +0000 (GMT) From: Andy Doran To: Doug Ambrisko Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: <199903051937.LAA27004@whistle.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 > Andy Doran writes: > | I believe that this is an issue with CAM. I have a bunch of DEC RZ25 disks > | here which work fine with ULTRIX, NetBSD and Linux on several different > | machines. After upgrading from FreeBSD-2.2.6 to 3.0 (and -current) > | the system hangs on boot whenever an RZ25 is hooked up. This is with a > | crappy 'ol Adaptec 1542CP controller. > > Most DEC drives as shipped with DEC system do not spin up on power up > (for sure not in the era of the RZ25). I recall that some DEC drives > had a jumper to select spin up on power up but I don't think all of them > did. I think they was also a mode page switch. I also recall that the > 1542 BIOS had options to send the command to spin up on power up. > By default, most of the old DEC RZxx disks don't spin up, yes. But these disks I do have spinning up (via the AHA BIOS). It's not any simple SCSI problem. Please don't take me the wrong way (i.e. this is an informational statement), but I do this for a living, and it's *not* a hardware problem. They work fine with all manner of cables, on DECstations with the NCR and the old SII controllers, PCs with various DPT RAID and Adaptec controllers, and FreeBSD 2.2.x with the old mach derived SCSI layer. They don't work with CAM for some reason. Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 16:19:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (ip222.houston3.tx.pub-ip.psi.net [38.12.169.222]) by hub.freebsd.org (Postfix) with ESMTP id C1D5914BE9 for ; Fri, 5 Mar 1999 16:19:22 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id SAA17432; Fri, 5 Mar 1999 18:19:53 -0600 (CST) (envelope-from chris) Date: Fri, 5 Mar 1999 18:19:52 -0600 From: Chris Costello To: Mark Hannon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: could not fdopen() the new stderr: Invalid argument Message-ID: <19990305181952.A17412@holly.dyndns.org> Reply-To: chris@calldei.com References: <36E054BE.EEE34881@stockholm.mail.telia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: <36E054BE.EEE34881@stockholm.mail.telia.com>; from Mark Hannon on Fri, Mar 05, 1999 at 11:03:43PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 5, 1999, Mark Hannon put this into my mailbox: > Hi, > Ever since moving to 3.1 I have been having problems with Netscape, I > occasionally get > an error dialogue saying: > > could not fdopen() the new stderr: Invalid argument > > I can press OK and clear the message and proceed but I am wondering what > it is. Any > ideas? Beyond "Netscape's broken?" Nope. Maybe you should contact Netscape about it... which version are you using, and is it the FreeBSD binary or the Linux binary? > > Rgds/Mark > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -Chris -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" "OK, now let's look at four dimensions on the blackboard." -- Dr. Joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 16:35:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles168.castles.com [208.214.165.168]) by hub.freebsd.org (Postfix) with ESMTP id 8879C15280 for ; Fri, 5 Mar 1999 16:35:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA07389; Fri, 5 Mar 1999 16:29:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060029.QAA07389@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christoph Kukulies Cc: hackers@freebsd.org Subject: Re: brandelf (necessary?) In-reply-to: Your message of "Wed, 03 Mar 1999 09:50:59 +0100." <199903030850.JAA26515@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 16:29:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In an environment where FreeBSD needs to run linux binaries > that are shared with linux systems, would it do harm to brandelf > these binaries? Or in other words, would it be possible for FreeBSD > to autodetect that it's a linux ELF binary without having to brand it? Unless the binaries are statically linked, this will always work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Mar 5 17:17:16 1999 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 AFDC7152BC for ; Fri, 5 Mar 1999 17:16:27 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id KAA11799; Sat, 6 Mar 1999 10:16:21 +0900 (JST) Message-ID: <36E07AEC.101F3467@newsguy.com> Date: Sat, 06 Mar 1999 09:46:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: alk@pobox.com Cc: hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > > Quoth Julian Elischer : > : the patch is in base64.. > : how do you read base64 files? > > This raises a good point: The base system should include mechanisms > for MIME. It's rather basic. Why? It doesn't even include a decent mail reader. If you are going to install a mail reader, anyway, you can install a mime extra, if needed at all (most mail readers do not require it). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 17:17:17 1999 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 2B66C152C0 for ; Fri, 5 Mar 1999 17:16:30 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id KAA11808; Sat, 6 Mar 1999 10:16:23 +0900 (JST) Message-ID: <36E07C08.D11DAB7D@newsguy.com> Date: Sat, 06 Mar 1999 09:51:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > I have a driver that needs to read a file that will eventually be located > somewhere in /boot. It is likely that this file will be determined by an > additional configuration file, also located in /boot, but the > configuration file will be loaded by the ELF bootstrap, so I don't need to > worry about it. > > Any ideas on how to go about opening and reading the file? I suspect the > answer may be buried somewhere in sys/dev/vn (the vnode driver) but I lack > sufficient clue to recognize it. Would something like what splash_bmp do be ok with you? It delegates to loader the responsibility of loading the file (ie, expects it to be loaded already). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 18:40:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 9875715266; Fri, 5 Mar 1999 18:39:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA17293; Sat, 6 Mar 1999 13:08:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA09304; Sat, 6 Mar 1999 13:07:41 +1030 (CST) Message-ID: <19990306130741.N490@lemis.com> Date: Sat, 6 Mar 1999 13:07:41 +1030 From: Greg Lehey To: Bill Fumerola , "Daniel C. Sobral" Cc: "Ron G. Minnich" , FreeBSD Chat Subject: Microsoft dies after 47 days (was: Moving on and check out my .sig) References: <36DDB131.630AF7F1@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bill Fumerola on Thu, Mar 04, 1999 at 01:54:43PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moving from -hackers to -chat] On Thursday, 4 March 1999 at 13:54:43 -0500, Bill Fumerola wrote: > On Thu, 4 Mar 1999, Daniel C. Sobral wrote: > >>> Note my .sig. 49.7 days is how long it takes a 32-bit millisecond counter >>> to roll over to zero. It's kind of hilarious that nobody seems to have had >>> windows up that long until now. >> >> What's worse is that this problem looks obvious. I wonder if whoever >> was responsible for this part of the code did not simply think along >> the line "Windows running for 49 days straight? Get real!" > > A mentioned this to a few of my co-workers who responded, "what part of > Windows". Is there a page that has the gory details somewhere? http://support.microsoft.com/support/kb/articles/q216/6/41.asp Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 19: 6: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id AC8081506E for ; Fri, 5 Mar 1999 19:06:01 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id WAA18438; Fri, 5 Mar 1999 22:05:42 -0500 (EST) Date: Fri, 5 Mar 1999 22:05:42 -0500 (EST) From: "Matthew N. Dodd" To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. In-Reply-To: <36E07C08.D11DAB7D@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 Sat, 6 Mar 1999, Daniel C. Sobral wrote: > Would something like what splash_bmp do be ok with you? It delegates > to loader the responsibility of loading the file (ie, expects it to be > loaded already). If thats all I've got to work with then it will have to do. The file I need to read is a firmware image for a network device that cannot be attached until the firmware is loaded. I would like to use something like splash_bmp to load a config file that specifys a vendor ID/cookie, an image type, offset, and filename. The driver would parse this config file and would load the appropriate firmware image for each card it detects. Due to licensing issues, firmware licensed for use with a particular vendor card may not be used with cards from a different vendor, though there is no technical reason why the same image can be used (that I know of so far.) Obviously, I could pre-load all the firmware images available but this seems wasteful. In addition, I would like the ability to upgrade the firmware on a card without bringing down the system. While I might make a device node to pipe the firmware image to the card once the system is up, giving the driver the ability to request and load the firmware image on demand would be nicer. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 19:42:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bursa01.cuneydi.com (bursa01.cuneydi.com [206.109.102.130]) by hub.freebsd.org (Postfix) with ESMTP id 22E5515037 for ; Fri, 5 Mar 1999 19:41:58 -0800 (PST) (envelope-from cucu@cuneydi.com) Received: from ibmlaptop.cuneydi.com ([206.109.102.140]) by bursa01.cuneydi.com (Netscape Mail Server v1.1) with SMTP id AAA464; Fri, 5 Mar 1999 20:46:32 -0600 From: "cucu" To: , Cc: Subject: RE: Compaq SMART on 3.1 Date: Fri, 5 Mar 1999 20:49:24 -0600 Message-ID: <001001be677b$f1cc77e0$8c666dce@ibmlaptop.cuneydi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199903051718.SAA29317@ns.web-tic.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem with 3.0(Smart II/P) and could not able to resolve it. Mark Dawson posted 3.1 and 3.x drivers and at this point I can not compile them without errors under 3.1 stable. Any ideas? cuneyt here is the error: .... cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-exte rns -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuniniti aliz ed -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. - I../ ../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../i386/isa/id a.c ../../i386/isa/ida.c: In function `ida_attach_drives': ../../i386/isa/ida.c:813: too few arguments to function `devstat_add_entry' *** Error code 1 Stop. > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Paul Jongsma > Sent: Friday, March 05, 1999 11:19 AM > To: freebsd-hackers@FreeBSD.ORG > Cc: paulj@webtic.com; md@doc.ic.ac.uk > Subject: Compaq SMART on 3.1 > > > > Is anyone using the IDA driver for the Compaq SMART array controller > on 3.1-RELEASE? The drivers at http://www.doc.ic.ac.uk/~md/ida > compile fine and the installation is succesfull. However copying > any file of >100 Kb or so gives a kernel panic. > > If anyone is using this driver on 3.1 without any problems I'd > like to compare configs. > > Thanks, > Paul. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 20:55:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 76A7214D95 for ; Fri, 5 Mar 1999 20:55:25 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA03941; Fri, 5 Mar 1999 21:54:33 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903060454.VAA03941@panzer.plutotech.com> Subject: Re: adaptec 2940u2w hangs on external disks In-Reply-To: from Andy Doran at "Mar 5, 1999 11:43:37 pm" To: ad@psn.ie (Andy Doran) Date: Fri, 5 Mar 1999 21:54:33 -0700 (MST) Cc: ambrisko@whistle.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Doran wrote... > > Andy Doran writes: > > | I believe that this is an issue with CAM. I have a bunch of DEC RZ25 disks > > | here which work fine with ULTRIX, NetBSD and Linux on several different > > | machines. After upgrading from FreeBSD-2.2.6 to 3.0 (and -current) > > | the system hangs on boot whenever an RZ25 is hooked up. This is with a > > | crappy 'ol Adaptec 1542CP controller. > > > > Most DEC drives as shipped with DEC system do not spin up on power up > > (for sure not in the era of the RZ25). I recall that some DEC drives > > had a jumper to select spin up on power up but I don't think all of them > > did. I think they was also a mode page switch. I also recall that the > > 1542 BIOS had options to send the command to spin up on power up. > > > By default, most of the old DEC RZxx disks don't spin up, yes. But these > disks I do have spinning up (via the AHA BIOS). It's not any simple SCSI > problem. Please don't take me the wrong way (i.e. this is an informational > statement), but I do this for a living, and it's *not* a hardware > problem. They work fine with all manner of cables, on DECstations with the > NCR and the old SII controllers, PCs with various DPT RAID and Adaptec > controllers, and FreeBSD 2.2.x with the old mach derived SCSI layer. They > don't work with CAM for some reason. 1. CAM will spin up any drives that need it once they're accessed. 2. We suspect that there are problems with the aha driver. See PR #10281. 3. There are known problems with CAM hanging on boot. Justin checked a possible fix into -current this afternoon, but we don't yet know whether this will solve the problem. Since you seem to have so many other SCSI controllers, I'd be interested to hear whether you have the same problem with those disk on another supported controller. That will tell us whether the problem is the aha driver or something else. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 21:20:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from unix.tfs.net (as1-p60.tfs.net [139.146.210.60]) by hub.freebsd.org (Postfix) with ESMTP id 6BD2314DFE for ; Fri, 5 Mar 1999 21:20:54 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id XAA60093; Fri, 5 Mar 1999 23:20:16 -0600 (CST) From: Jim Bryant Message-Id: <199903060520.XAA60093@unix.tfs.net> Subject: Re: Microsoft dies after 47 days (was: Moving on and check out my .sig) In-Reply-To: <19990306130741.N490@lemis.com> from Greg Lehey at "Mar 6, 99 01:07:41 pm" To: grog@lemis.com (Greg Lehey) Date: Fri, 5 Mar 1999 23:20:06 -0600 (CST) Cc: freebsd-hackers@freebsd.org Reply-To: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #46: Sun Dec 6 03:10:25 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (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 In reply: > From POPmail Fri Mar 5 20:52:10 1999 > Delivered-To: freebsd-hackers@freebsd.org > Message-ID: <19990306130741.N490@lemis.com> > Date: Sat, 6 Mar 1999 13:07:41 +1030 > From: Greg Lehey > To: Bill Fumerola , "Daniel C. Sobral" > Cc: "Ron G. Minnich" , FreeBSD Chat > Subject: Microsoft dies after 47 days (was: Moving on and check out my .sig) > References: <36DDB131.630AF7F1@newsguy.com> > X-Mailer: Mutt 0.93.2i > In-Reply-To: ; from Bill Fumerola on Thu, Mar 04, 1999 at 01:54:43PM -0500 > WWW-Home-Page: http://www.lemis.com/~grog > Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia > Phone: +61-8-8388-8286 > Fax: +61-8-8388-8725 > Mobile: +61-41-739-7062 > Sender: owner-freebsd-hackers@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > X-DPOP: DPOP Version 2.00j > X-UIDL: 920688748.000 > [moving from -hackers to -chat] > > On Thursday, 4 March 1999 at 13:54:43 -0500, Bill Fumerola wrote: > > On Thu, 4 Mar 1999, Daniel C. Sobral wrote: > > > >>> Note my .sig. 49.7 days is how long it takes a 32-bit millisecond counter > >>> to roll over to zero. It's kind of hilarious that nobody seems to have had > >>> windows up that long until now. > >> > >> What's worse is that this problem looks obvious. I wonder if whoever > >> was responsible for this part of the code did not simply think along > >> the line "Windows running for 49 days straight? Get real!" > > > > A mentioned this to a few of my co-workers who responded, "what part of > > Windows". Is there a page that has the gory details somewhere? > > http://support.microsoft.com/support/kb/articles/q216/6/41.asp NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support. [Does this not cover 95% of all win95 installations? "Bugs for Bucks 101"] jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 21:53: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.42]) by hub.freebsd.org (Postfix) with ESMTP id DE2D215068 for ; Fri, 5 Mar 1999 21:52:56 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.2/8.9.1) id XAA30188; Fri, 5 Mar 1999 23:51:35 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 5 Mar 1999 23:51:34 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: dcs@newsguy.com Cc: hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14048.48864.918087.631128@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Daniel C. Sobral on Sat, 6 March: : > : > This raises a good point: The base system should include mechanisms : > for MIME. It's rather basic. : : Why? It doesn't even include a decent mail reader. If you are going : to install a mail reader, anyway, you can install a mime extra... It is an issue of what the package is intended to be. I think of FreeBSD is more than a kernel. Some substantial portion of its appeal relative to Linux is that it is as a coherent OS, a general-purpose platform, which incorporates the necessary facilities for ordinary uses. As the set of ordinary uses changes over time, then in order for FreeBSD to remain that, its facilities must change over time. But perhaps FreeBSD does not intend to remain, without add-ons, a sufficient platform for general-purpose use. MHO: If the included mail reader is not 'decent', throw it away. Oh, replacing UCB mail is socially difficult, but such compunctions seem to be damaging the future of the product, its coherent vision, and its ability to keep up with the times. I still think FreeBSD should be packaged as a layered system, a group of functional complexes serving different areas. And sooner rather than later, for as it grows the components of what should be distinct modules become increasingly interdependent. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 22: 2:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (Postfix) with SMTP id CA6EF150FD for ; Fri, 5 Mar 1999 22:01:37 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 24227 invoked from network); 6 Mar 1999 06:01:18 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 6 Mar 1999 06:01:18 -0000 Received: (from toor@localhost) by y.dyson.net (8.9.1/8.9.1) id BAA00476; Sat, 6 Mar 1999 01:01:16 -0500 (EST) Message-Id: <199903060601.BAA00476@y.dyson.net> Subject: Re: why vm is rewriten much? In-Reply-To: from Matt Liu at "Mar 5, 99 11:14:01 am" To: MattL@ModaCAD.com (Matt Liu) Date: Sat, 6 Mar 1999 01:01:16 -0500 (EST) Cc: smp@freebsd.org, freebsd-hackers@freebsd.org From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (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 Matt Liu said: > Hi guys: > > One of the question is pondering on me is that why the Mach vm is much > changed. From what version it's changed, is it from 2.2.8, 2.2.7. Look like > 2.2.5 isn't changed much. I heard Mach vm support SMP. > UNIX/NT ADM > @ModaCad Inc. > > A Berkeley follower > The MACH VM needed work to efficiently implement the requirements for UNIX. There is a huge improvement in performance over the original code. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 23:12:36 1999 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 6239D14D34 for ; Fri, 5 Mar 1999 23:12:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id QAA14772; Sat, 6 Mar 1999 16:12:26 +0900 (JST) Message-ID: <36E0D50F.CE515D4E@newsguy.com> Date: Sat, 06 Mar 1999 16:11:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: hackers@freebsd.org Subject: Cross-referenced kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A few weeks ago someone posted a notice about a cross-referenced FreeBSD kernel (complete source?) www page, produced by some Linux folks. I have been trying to find that resource, seen it has disappeared from my bookmarks after I rearranged then... Can someone give me the link? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 5 23:18:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles171.castles.com [208.214.165.171]) by hub.freebsd.org (Postfix) with ESMTP id 1979014DF1; Fri, 5 Mar 1999 23:18:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA66928; Fri, 5 Mar 1999 23:12:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060712.XAA66928@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Terry Lambert , sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: Re: GGI In-reply-to: Your message of "Fri, 05 Mar 1999 19:38:25 +0900." <36DFB421.1A845720@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 23:12:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (changed, subject, list, and cc list... it's almost a new mail! :) > > Terry Lambert wrote: > > > ... > > I can't do the work for FreeBSD until it adopts GGI, and supports ELF > ... > > > > The GGI people have been looking for someone (with commit priviledges, > > obviously) to do a FreeBSD port, and have gone so far as to put the > > kernel pieces of their predominantly Linux project *in the public domain*. > > I looked at GGI, and I liked it. If my memory doesn't fail me, Soren > remarked that he was not much impressed with it last he checked it. > > What I'd like to know is if the Powers That Be of FreeBSD console > (Soren and Yokota?) would, present state of the code > notwithstanding, accept the adoption of GGI once deemed to be > "ready", or if there is any fundamental flaw with it that makes this > a hopeless propositon. Just FWIW, I was approached by one of the GGI group (actually, in the employ of Creative, who are apparently going crazy right now about cross-platform support) at Linuxworld. The GGI folks seem quite fervent about fixing GGI so that everyone loves it, and they see FreeBSD as possibly a better place to start getting it right than Linux (which already has a half-assed framebuffer driver). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Mar 6 0:27:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id DF2291512D for ; Sat, 6 Mar 1999 00:27:23 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: (from uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id JAA12340 for FreeBSD-hackers@freebsd.org; Sat, 6 Mar 1999 09:24:27 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id JAA02163 for FreeBSD-hackers@freebsd.org; Sat, 6 Mar 1999 09:26:54 +0100 (CET) From: Wilko Bulte Message-Id: <199903060826.JAA02163@yedi.iaf.nl> Subject: making release on 2.2.8-stable tree To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Sat, 6 Mar 1999 09:26:54 +0100 (CET) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 Hi there, Maybe I'm missing something but: I keep a cvssupped 2.2.8-stable tree around of which I want to create a couple of CDs. make buildworld ran just fine, but make release in src/release does not: for i in /sbin/mount /sbin/umount /usr/bin/cpio ; do cp -p /usr/release$i /usr/release//bootstrap ; done cd /usr/release/usr && rm -rf src && cvs -R -d /usr/src/CVS co -P src cvs [checkout aborted]: /usr/src/CVS/CVSROOT: No such file or directory *** Error code 1 I pointed make to src/CVS: time make release CHROOTDIR=/usr/release BUILDNAME=2.2.8-stable-6-mar-99 CVSROOT=/usr/src/CVS 2>&1 | tee ../LOG because it refused to run otherwise. Given the references to CVSROOT in the makefile this sounds logical. But: from the error above I it seems you need a full CVS repository (which I obviously don't have). Is this really true?? Wilko _ ______________________________________________________________________ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 0:50:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 210CF14C35 for ; Sat, 6 Mar 1999 00:50:38 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-67-67.atl.bellsouth.net [209.214.67.67]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id DAA26621; Sat, 6 Mar 1999 03:49:47 -0500 (EST) Received: from wghicks (localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id DAA26823; Sat, 6 Mar 1999 03:40:42 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199903060840.DAA26823@bellsouth.net> To: Wilko Bulte Cc: FreeBSD-hackers@FreeBSD.ORG (FreeBSD hackers list), wghicks@wghicks.bellsouth.net Subject: Re: making release on 2.2.8-stable tree In-reply-to: Your message of "Sat, 06 Mar 1999 09:26:54 +0100." <199903060826.JAA02163@yedi.iaf.nl> Date: Sat, 06 Mar 1999 03:40:41 -0500 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But: from the error above I it seems you need a full CVS repository (which > I obviously don't have). Is this really true?? Yes, you need a full repo for making releases. Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 1:23:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 2E768150A3 for ; Sat, 6 Mar 1999 01:23:38 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 5263 invoked by uid 1001); 6 Mar 1999 09:23:20 +0000 (GMT) To: dcs@newsguy.com Cc: hackers@freebsd.org Subject: Re: Cross-referenced kernel From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 06 Mar 1999 16:11:11 +0900" References: <36E0D50F.CE515D4E@newsguy.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 06 Mar 1999 10:23:20 +0100 Message-ID: <5261.920712200@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A few weeks ago someone posted a notice about a cross-referenced > FreeBSD kernel (complete source?) www page, produced by some Linux > folks. I have been trying to find that resource, seen it has > disappeared from my bookmarks after I rearranged then... Can someone > give me the link? http://lxr.linux.no/freebsd/source Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 2:24:14 1999 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 24D8515162 for ; Sat, 6 Mar 1999 02:24:11 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA03733; Sat, 6 Mar 1999 19:24:05 +0900 (JST) Message-ID: <36E1006E.8F5517CA@newsguy.com> Date: Sat, 06 Mar 1999 19:16:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Sat, 6 Mar 1999, Daniel C. Sobral wrote: > > Would something like what splash_bmp do be ok with you? It delegates > > to loader the responsibility of loading the file (ie, expects it to be > > loaded already). > > If thats all I've got to work with then it will have to do. Actually, I think there is some way to read a file. I vaguely remember such discussions in the past. But I recall it is very messy. But all I am doing is presenting alternatives. > The file I need to read is a firmware image for a network device that > cannot be attached until the firmware is loaded. > > I would like to use something like splash_bmp to load a config file that > specifys a vendor ID/cookie, an image type, offset, and filename. > > The driver would parse this config file and would load the appropriate > firmware image for each card it detects. > > Due to licensing issues, firmware licensed for use with a particular > vendor card may not be used with cards from a different vendor, though > there is no technical reason why the same image can be used (that I know > of so far.) > > Obviously, I could pre-load all the firmware images available but this > seems wasteful. In addition, I would like the ability to upgrade the > firmware on a card without bringing down the system. While I might make a > device node to pipe the firmware image to the card once the system is up, > giving the driver the ability to request and load the firmware image on > demand would be nicer. You can unload them if you find they are not needed. I can see your point, though. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 5:11:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 65DF8151D0 for ; Sat, 6 Mar 1999 05:10:59 -0800 (PST) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id OAA09535; Sat, 6 Mar 1999 14:10:29 +0100 (MET) Received: (from nsouch@localhost) by teaser.fr (8.9.2/8.9.1) id MAA00799; Sat, 6 Mar 1999 12:33:55 +0100 (CET) (envelope-from nsouch) Message-ID: <19990306123355.04328@breizh.teaser.fr> Date: Sat, 6 Mar 1999 12:33:55 +0100 From: Nicolas Souchu To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG, des@flood.ping.uio.no Subject: Re: new ppbus driver problem References: <199903052001.MAA51599@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199903052001.MAA51599@apollo.backplane.com>; from Matthew Dillon on Fri, Mar 05, 1999 at 12:01:37PM -0800 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 12:01:37PM -0800, Matthew Dillon wrote: > > This is with -current. > > I've been getting crashes during boot with the new ppbus stuff and lpt0 > enabled. Hmm, your the first reporting such problem. > > It detects the parallel port just fine, but further on in the boot > sequence the system gets an RTC error and then it just locks up > completely... it doesn't even get past the kernel config ( never gets > to execing init ). What's your hardware? Motherboard, and parallel port chipset? Parallel port is generaly handled by a superIO chip, but your system may rely on the PCI/ISA chip.. > > I was able to solve the problem by commenting out most of the probe code > in i386/isa/ppc.c, as shown below. I don't know which port in the probe > code is causing the problem, but something in there is blowing up my > systems. > > Maybe the probe code should be a little more conservative, with a > kernel config option to be less conservative ???? A boot option is available for this. Undocumented :( flag 0x40 for ppc at boot does it. > > -Matt > Matthew Dillon > > >static int >ppc_detect(struct ppc_data *ppc, int chipset_mode) { > > int i, mode; > > /* list of supported chipsets */ > int (*chipset_detect[])(struct ppc_data *, int) = { >#if 0 > ppc_pc873xx_detect, > ppc_smc37c66xgt_detect, > ppc_w83877f_detect, >#endif > ppc_generic_detect, > NULL > }; > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sat Mar 6 7: 0: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.kudra.com (gw.kudra.com [199.6.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 2463F15005 for ; Sat, 6 Mar 1999 06:59:45 -0800 (PST) (envelope-from robert@kudra.com) Received: (from robert@localhost) by tabby.kudra.com (8.9.2/8.6.12) id JAA53189; Sat, 6 Mar 1999 09:59:27 -0500 (EST) Message-ID: <19990306095927.B53145@kudra.com> Date: Sat, 6 Mar 1999 09:59:27 -0500 From: Robert Sexton To: alk@pobox.com Cc: freebsd-hackers@freebsd.org Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <14048.48864.918087.631128@avalon.east>; from Tony Kimball on Fri, Mar 05, 1999 at 11:51:34PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 11:51:34PM -0600, Tony Kimball wrote: > : Why? It doesn't even include a decent mail reader. If you are going > : to install a mail reader, anyway, you can install a mime extra... > > It is an issue of what the package is intended to be. I think of > FreeBSD is more than a kernel. Some substantial portion of its appeal > relative to Linux is that it is as a coherent OS, a general-purpose > platform, which incorporates the necessary facilities for ordinary > uses. As the set of ordinary uses changes over time, then in order > for FreeBSD to remain that, its facilities must change over time. But > perhaps FreeBSD does not intend to remain, without add-ons, a > sufficient platform for general-purpose use. You've touched upon what can only be called a religeous issue. Based on my take of of the user base, nobody here wants FreeBSD to be a general purpose platform 'out of the box'. The consensus seems to be that the minimal system is quite popular. I for one don't want to schlep around a lot of mime code that my news machine will never run. Likewise for uucp :-) Its not just that we've got to support the old machine crowd, but that bloat is in general bad. One point I'd add is that Linux without add ons is pretty much unusable. Since its a kernel, you need add ons to even log in. FreeBSD is a coherent OS because its a complete package out of the box. We have a usable base system. And there's no dispute of which things are add ons and which aren't. Attempts to expand the base system have met with what I'd consider justified resistance. > MHO: If the included mail reader is not 'decent', throw it away. Oh, > replacing UCB mail is socially difficult, but such compunctions seem > to be damaging the future of the product, its coherent vision, and its > ability to keep up with the times. This is the path that has made linux such a mess. There is _no_way_ that FreeBSD could even include a mail reader that would make most people happy. Thats why we have the ports tree. If we switched to elm for instance, that would be a wasted megabye of disk for me, and many other people. Can you say 'Creeping Featureism?' If I may be so presumptious, I'd say that the coherent vision is that we have the smallest base distribution which makes up a complete system, and that the rest can be convieniently flavored to taste. > I still think FreeBSD should be packaged as a layered system, a group > of functional complexes serving different areas. And sooner rather > than later, for as it grows the components of what should be distinct > modules become increasingly interdependent. This the solution to the problem that could make everybody happy. So hows it coming along, Jordan? :-) -- Robert Sexton, robert@kudra.com "No one told me that it could not be done, and so I did it." - Jack Kloepfer Read the Newton FAQ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 11:13:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id E63B614C13 for ; Sat, 6 Mar 1999 11:13:39 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA27811; Sat, 6 Mar 1999 12:13:22 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd027792; Sat Mar 6 12:13:21 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA08788; Sat, 6 Mar 1999 12:13:21 -0700 (MST) From: Terry Lambert Message-Id: <199903061913.MAA08788@usr06.primenet.com> Subject: Re: lockf and kernel threads To: jplevyak@inktomi.com (John Plevyak) Date: Sat, 6 Mar 1999 19:13:21 +0000 (GMT) Cc: tlambert@primenet.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <19990305080618.B22589@tsdev.inktomi.com> from "John Plevyak" at Mar 5, 99 08:06:18 am X-Mailer: ELM [version 2.4 PL25] 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 > > > Why is it too late after that? In the patch I did the wait in exit1() > > > right after the 'kill' of the peers. > > > > It's too late if you've gone to user space with the signal, because > > it's an untrappable signal. That's the trampoline I was referring > > to. > > I understand about the trampoline, but I don't see why you can't send > the signal out of user space, mostly because that is what 3.0+ > currently does! (near the beginning of exit1() to all peers of a p_leader.) Assume a kill -9 of a PID that is a "thread" in a "thread group" (process). The exit call is not explicit. The SIGKILL is mandatorily not caught. The kill comes from the kernel, with no user space notification. > > Right. Such a structure is essentially identical in content to > > an async call context for an async call gate, BTW. 8-). > > I am missing context on this, however if it was a mechanism for > generalized async calls w/o signals/polling but 'wait for one > of N events' I am interested. Yes, that's exactly it. Basically, you use an alternate entry point to the system call trap code, and immediately return after queuing the trap to the kernel. The context you need is a kernel stack for the call, a kernel program counter, etc.. Basically the call runs as far as it can (potentially to completion), and instead of putting the process to sleep, puts the call context to sleep, returning the remainder of the quantum to user space. This provides SMP scalability (call contexts can be serviced by multiple CPU's) without requiring strict kernel threads to implement. You can program with the calls directly (like the current AIO code) to get operation interleave, or you can implement a user space call conversion scheduler, which converts standard calls into async calls plus a thread context switch. The advantage to doing this method of implementation of call conversion is that the call wrapping code is then generic, and no additional work needs to be done for threads, other than wrapping the conversion. In this way, the implementation is drastically simpler, and drastically lower overhead than the current call conversion scheduler, which must do wrapping and locking in user space. In addition, this implementation has significantly smaller context switch overhead, compared to traditional kernel threading models, since making a blocking system call is not the same thing as an explicit scheduler yield, as it is with kernel threads. When the scheduler assigns a quantum, it's your quantum. You can deal with multiple CPU's being in user space simultaneously in the same process trivially: you just allow more than one CPU to return up with the code from the converted call, and enter your call conversion scheduler -- the real reason for threads is to provide procedural work-to-do for a quantum as a scheduled resource. There are some obvious optimizations, as well. You could easily classify system calls with another entry in the struct sysent[] structure element for a given call, and act accordingly, by type: o call may block Treat as the unoptimized case, and return when you hit a tsleep that blocks the call. o call never blocks Do not allocate a call context, and trivially return a static context for completion. o call always blocks Obtain parameters and immediately return so that the long latency event (e.g., tty I/O) does not detract from overall throughput. Another optimization which is obvious after consideration, is to modify trap entry for SMP architectures, and immediately return all but the calls which never block. The calls which never block are treated as if they are static data in user space, and merely referenced via accessor functions for convenience and abstraction. Onece the context is in the kernel, it is given to the scheduler, where it competes for a quantum on whatever CPU becomes next available. This is a bit counterintuitive, in that we are attempting to reduce scheduler context switch overhead. However, it doesn't matter that the quantum is given back to the system (or, alternately, given to the threads scheduler in the process that made the request, based on some administrative fiat) because these events are intrinsically short duration. In other words, they are expected to run to sleep, then run to completion following a wakeup, both in less than a quantum. Since the sleep discontinuity is impossible to overcome, and the completion discontinuity is also impossible to overcome, this is the minimal implementation of "non-interrupt scheduled kernel work-to-do". The possbilities are really pretty great. The architecture bypasses most of the issues for SMP scalability, without taking a hit for having ignored rather than dealt with the issues. Additionally, the architecture in the second optimization can, in fact, be used to proxy the request in a distributed computing environment. Obviously, looking at this architecture, one of my hot buttons is massively parallel distrbuted systems with completion agents that operate with incomplete knowledge. I think these types of systems are going to be THE Most Important(tm) in the long to medium term future -- e.g., they are exactly what is needed for operating a fleet of hundereds of thousands of nanometer scale semiautonomous machines doing organ repair. > > You might be able to get someone to commit this, at least as a short > > term soloution to the problem. It would get you over the "blessed" > > hump so you can concentrate on more pressing issues. > > Hummm... any guesses as to whom might be most sympathetic? Matt Dillion, David Greenamn, Julian Elisher, Peter Wemm all spring immediately to mind. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 11:20: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 4D3B71521C for ; Sat, 6 Mar 1999 11:20:02 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA28490; Sat, 6 Mar 1999 12:19:44 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd028465; Sat Mar 6 12:19:36 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA09233; Sat, 6 Mar 1999 12:19:34 -0700 (MST) From: Terry Lambert Message-Id: <199903061919.MAA09233@usr06.primenet.com> Subject: Re: lockf and kernel threads To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 6 Mar 1999 19:19:34 +0000 (GMT) Cc: hasty@rah.star-gate.com, tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903051841.KAA49799@apollo.backplane.com> from "Matthew Dillon" at Mar 5, 99 10:41:07 am X-Mailer: ELM [version 2.4 PL25] 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 > :Thats probably true however for delivery of an AST I don't thing that we > :need priviliged instructions --- I could be wrong. > > Little things like, ohhhhh disabling interrupts. Accessing the MMU > registers, flushing the TLB, etc..... believe me, ring 1 and ring 2 > is utterly useless for anything FreeBSD wants to run in supervisor mode. Uh, if you ran the AST target function in supervisor mode, it would be a nice truck-size hole in the security model. The distinction between ring 2 and ring 3 is useful primarily for drawing a border between calls to user code from the kernel vs. calls to user code by the user. In both cases, it's user code that's executing: unpriviledged code. I think you are maybe being confused with "installed images" and "symbionts", which generally did *not* run at the same level as AST's. I can (and I think Wes Peters can) dig up a reference to a VMS-like OS educational implementation for which the University we went to had source that implemented a four-tier protection menchanism in general, and AST's from kernel to user, in particular. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 11:23:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 4FBA5152BA for ; Sat, 6 Mar 1999 11:23:27 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA00217; Sat, 6 Mar 1999 12:23:09 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp03.primenet.com, id smtpd000199; Sat Mar 6 12:23:09 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA09558; Sat, 6 Mar 1999 12:23:08 -0700 (MST) From: Terry Lambert Message-Id: <199903061923.MAA09558@usr06.primenet.com> Subject: Re: lockf and kernel threads To: dyson@iquest.net Date: Sat, 6 Mar 1999 19:23:07 +0000 (GMT) Cc: dillon@apollo.backplane.com, hasty@rah.star-gate.com, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903051902.OAA00724@y.dyson.net> from "John S. Dyson" at Mar 5, 99 02:02:36 pm X-Mailer: ELM [version 2.4 PL25] 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 > > :Thats probably true however for delivery of an AST I don't thing that we > > :need priviliged instructions --- I could be wrong. > > > > Little things like, ohhhhh disabling interrupts. Accessing the MMU > > registers, flushing the TLB, etc..... believe me, ring 1 and ring 2 > > is utterly useless for anything FreeBSD wants to run in supervisor mode. > > AST's could be simulated, but it is just more hair added to an already > sufficient set of hair. Let me state, categorically, and for the records, that I think that system call completion functions are an architectural dead-end. The point of an async call gate is to allow queueing of operations which are later specifically waited on and/or for which a wait-any is executed to reap their status. They differ primarily from signals in that completion is an event that modifies data rather than triggering procedural code, and an explicit (potentially non-blocking, but *not* asynchronous) test must be done to determine completion. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 11:25:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id C397915031 for ; Sat, 6 Mar 1999 11:25:08 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA24327; Sat, 6 Mar 1999 13:00:44 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd024278; Sat Mar 6 13:00:39 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA09686; Sat, 6 Mar 1999 12:24:45 -0700 (MST) From: Terry Lambert Message-Id: <199903061924.MAA09686@usr06.primenet.com> Subject: Re: lockf and kernel threads To: dyson@iquest.net Date: Sat, 6 Mar 1999 19:24:45 +0000 (GMT) Cc: hasty@rah.star-gate.com, tlambert@primenet.com, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903051853.NAA00631@y.dyson.net> from "John S. Dyson" at Mar 5, 99 01:53:50 pm X-Mailer: ELM [version 2.4 PL25] 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 > For other I/O, it dynamically creates thread pools, and uses threads > as needed. Threads don't end up being created and destroyed that often, > because the requests are handled dynamically by the threads, and the > threads dynamically attach/detach to the process address space. If the > threads don't get used for a long time, they start disappearing. > > The scheme sort-of creates anonymous threads that are used as resources > for multiple processes. > > Eventually, most of the I/O types won't have to be threaded, but the > thread scheme is a concept proof of the ability to create anonymous > workers in the BSD kernel. > > (Actually, the thread work was much more complex than the RAW I/O.) This resembles my second optimization for async call gates. This code is worthwhile, despite the complexity, due to the ability to proxy the operations in a distributed environment, if you don't know how to complete the operations locally, or can't because of resource starvation. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 11:28:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 45F28152BB for ; Sat, 6 Mar 1999 11:28:42 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA00794; Sat, 6 Mar 1999 12:28:25 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd000781; Sat Mar 6 12:28:20 1999 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id MAA09945; Sat, 6 Mar 1999 12:28:19 -0700 (MST) From: Terry Lambert Message-Id: <199903061928.MAA09945@usr06.primenet.com> Subject: Re: lockf and kernel threads To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 6 Mar 1999 19:28:19 +0000 (GMT) Cc: dillon@apollo.backplane.com, hasty@rah.star-gate.com, tlambert@primenet.com, dyson@iquest.net, dick@tar.com, jplevyak@inktomi.com, hackers@FreeBSD.ORG In-Reply-To: <199903052022.MAA82649@rah.star-gate.com> from "Amancio Hasty" at Mar 5, 99 12:22:14 pm X-Mailer: ELM [version 2.4 PL25] 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 > > Not unless you want to rewrite the kernel. But it's actually more the > > We shall see if the above statement is true or not . In the mean time, > with the intent to anchor the discussion in a positive direction , I ask > Terry to produce a draft paper on how to implement ASTs on FreeBSD. I will work on an async call gate paper. I have published much of what I have to say, short of an implementation, in this thread, already. I will *not* work on AST's. I believe they are a dead end, since they fail in the face of proxy distribution by requiring complete knowledge on both ends. This prevents an intermediary from forwarding a request that it can't personally satisfy. Consider the difference between "call by descriptor" and "call by argument" that distinguished John Heidemann's network VFS proxy layer from NFS. Call by argument is evil. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 14:38:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 6151B1514F for ; Sat, 6 Mar 1999 14:37:42 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id PAA18368; Sat, 6 Mar 1999 15:36:57 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36E1AE09.760B4EF8@softweyr.com> Date: Sat, 06 Mar 1999 15:36:57 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Robert Sexton Cc: alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Sexton wrote: > > Tony Kimball wrote: > > > I still think FreeBSD should be packaged as a layered system, a group > > of functional complexes serving different areas. And sooner rather > > than later, for as it grows the components of what should be distinct > > modules become increasingly interdependent. > > This the solution to the problem that could make everybody happy. > So hows it coming along, Jordan? :-) This is not that hard to do with the current system. You just make up packages that depend on the "sets" of packages (or use ports, if you prefer) and don't contain anything else. I believe the top- level KDE package already does this. For vanilla usability out of the box, I think KDE and Gnome are going to be "the way to go." Not due to technical excellence or any particular feature of either, but simply because each provides a relatively consistent and well-rounded set of "Accessories." Speaking of which, has anyone looked at doing a port of AbiWord from AbiSource yet? Conceptually, the idea of a freely available word processor that stores documents in XML sounds great. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 15: 7:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (Postfix) with SMTP id EAB081501B for ; Sat, 6 Mar 1999 15:07:02 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 27735 invoked by uid 1001); 6 Mar 1999 23:06:48 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36E1AE09.760B4EF8@softweyr.com> Date: Sat, 06 Mar 1999 18:06:48 -0500 (EST) X-Face: *0^4Iw) To: Wes Peters Subject: Re: base64 Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Mar-99 Wes Peters wrote: > Speaking of which, has anyone looked at doing a port of AbiWord from > AbiSource yet? Conceptually, the idea of a freely available word > processor that stores documents in XML sounds great. Never even heard of it. Care to elaborate? Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 15:30:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles117.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id CC4D0151C3 for ; Sat, 6 Mar 1999 15:30:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA00691; Sat, 6 Mar 1999 15:24:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903062324.PAA00691@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: BIOS reboot question from Linux user In-reply-to: Your message of "Thu, 04 Mar 1999 11:58:28 +0200." <33057.920541508@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Mar 1999 15:24:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hi folks, > > The following question is cluttering up the GNATS database (misc/5552): > > | I found out today that the Linux parameter of append reboot=bios > | (which passes the reboot=bios) is unavailable under FreeBSD. Is this > | correct? The keyboard fix in the kernel does not fix my problem, and > | the machine still does not reboot. > | > | Is there a way to tell the machine to reboot via the bios? > > I don't understand what this chap's talking about and wondered if anyone > here with an understanding of how the referenced Linux option works. > > Does reboot(8) use the BIOS code for rebooting? No. There are arguments for and against trying; currently the only systems that would benefit from such an option are those with broken hardware. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Mar 6 15:40:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 227A015141 for ; Sat, 6 Mar 1999 15:40:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA11268; Sat, 6 Mar 1999 15:40:17 -0800 (PST) (envelope-from dillon) Date: Sat, 6 Mar 1999 15:40:17 -0800 (PST) From: Matthew Dillon Message-Id: <199903062340.PAA11268@apollo.backplane.com> To: Nicolas Souchu Cc: freebsd-hackers@FreeBSD.ORG, des@flood.ping.uio.no Subject: Re: new ppbus driver problem References: <199903052001.MAA51599@apollo.backplane.com> <19990306123355.04328@breizh.teaser.fr> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Fri, Mar 05, 1999 at 12:01:37PM -0800, Matthew Dillon wrote: :> :> This is with -current. :> :> I've been getting crashes during boot with the new ppbus stuff and lpt0 :> enabled. : : Hmm, your the first reporting such problem. :> :> It detects the parallel port just fine, but further on in the boot :> sequence the system gets an RTC error and then it just locks up :> completely... it doesn't even get past the kernel config ( never gets :> to execing init ). : : What's your hardware? Motherboard, and parallel port chipset? : Parallel port is generaly handled by a superIO chip, but your : system may rely on the PCI/ISA chip.. It's a K6-2/300 Compaq presario, so presumably a custom motherboard. The problem also occured on another machine but I forget whether it was on one of my old P90's or whether it was on a newer (but still old) P166. :> systems. :> :> Maybe the probe code should be a little more conservative, with a :> kernel config option to be less conservative ???? : : A boot option is available for this. Undocumented :( flag 0x40 : for ppc at boot does it. Cool! This is just an FYI - in case more reports are made. -Matt Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #13: Fri Mar 5 11:56:13 PST 1999 dillon@apollo.backplane.com:/FreeBSD/FreeBSD-4.x/src/sys/compile/TEST2 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299609044 Hz CPU: AMD-K6(tm) 3D processor (299.61-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 50331648 (49152K bytes) avail memory = 46231552 (45148K bytes) Preloaded elf kernel "kernel" at 0xf02ae000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x30 int a irq 11 on pci0. 19.0 xl0: command never completed! xl0: Ethernet address: 00:50:04:61:56:ae xl0: autoneg complete, link status good (half-duplex, 100Mbps) vga0: rev 0x01 int a irq 9 on pci0.20.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 2060MB (4219425 sectors), 4465 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 5511KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 15:42:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles117.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id E65F2152DA for ; Sat, 6 Mar 1999 15:42:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA00753; Sat, 6 Mar 1999 15:37:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903062337.PAA00753@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Ambrisko Cc: freebsd-hackers@FreeBSD.ORG, ken@nlc.net.au Subject: Re: Invitation to participate in Open Source NILO project (fwd) In-reply-to: Your message of "Wed, 03 Mar 1999 08:11:34 PST." <199903031611.IAA96563@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Mar 1999 15:37:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ken asked me to forward this to the FreeBSD project. He is the main > force behind the Etherboot package that I made a port of to boot > FreeBSD a.out & ELF kernels. It appears to be GPL'd. It looks like an > interesting project. "Yuck". We can work with this, certainly, but as you point out it will be GPLed, as well as using the TIF and a lot of linux-specific gunk. From the loader's perspective, you just haul it somewhere into memory somehow and let it run; it doesen't need all this handholding. > Doug A. > > ----- Forwarded message from Ken Yap ----- > [Hi Doug, I believe you are on some FreeBSD lists. Would you be kind > enough to forward this to those lists? TIA, Ken] > > NLnet is pleased to announce that the NILO (Network Interface > LOader) project has commenced in February 1999 with Rob Savoye, of > welcomehome.org, as the project contractor. The NILO project has the > goal of developing Open Source Software for network booting ROMs based > on Linux network adaptor drivers. The resulting ROMs will be able > to boot operating systems such as Linux, FreeBSD and Windows. It will > support the Intel PXE (Preboot Execution Environment) specification. > The project will run until October 1999. For further details please > visit the NILO home page at > > http://www.nilo.org/ > > The NILO project invites the Open Source community to actively participate > in NILO development by joining the NILO developers mailing list and > providing feedback on the documents and software releases as they appear > on the web site. Details of how to subscribe are on the NILO web page. > > The NLnet foundation, started in 1982, is the principal founder of global > area networking in Europe, in what is called today the Internet. NLnet > originates from initiatives taken from the Unix (tm) community and is > fully non-profit. Currently NLnet funds network technology projects > to stimulate electronic information exchange, mainly on the Internet. > See the home page at http://www.nlnet.nl > > Ken > > ----- End of forwarded message from Ken Yap ----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Mar 6 16: 0:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 6D60915126 for ; Sat, 6 Mar 1999 16:00:49 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.2/8.9.2) id TAA85234; Sat, 6 Mar 1999 19:00:05 -0500 (EST) (envelope-from lee) Message-ID: <19990306190005.A85183@tidalwave.net> Date: Sat, 6 Mar 1999 19:00:05 -0500 From: Lee Cremeans To: Mike Smith , Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: BIOS reboot question from Linux user Reply-To: lcremean@tidalwave.net References: <33057.920541508@axl.noc.iafrica.com> <199903062324.PAA00691@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903062324.PAA00691@dingo.cdrom.com>; from Mike Smith on Sat, Mar 06, 1999 at 03:24:50PM -0800 X-OS: FreeBSD 3.0-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 06, 1999 at 03:24:50PM -0800, Mike Smith wrote: > > > > Hi folks, > > > > The following question is cluttering up the GNATS database (misc/5552): > > > > | I found out today that the Linux parameter of append reboot=bios > > | (which passes the reboot=bios) is unavailable under FreeBSD. Is this > > | correct? The keyboard fix in the kernel does not fix my problem, and > > | the machine still does not reboot. > > | > > | Is there a way to tell the machine to reboot via the bios? > > > > I don't understand what this chap's talking about and wondered if anyone > > here with an understanding of how the referenced Linux option works. > > > > Does reboot(8) use the BIOS code for rebooting? > > No. > > There are arguments for and against trying; currently the only systems > that would benefit from such an option are those with broken hardware. To clarify, FreeBSD first tries to reset the computer using the keyboard controller (which is the original AT-compatible way of doing it). Some machines, however, don't have the RST# line from the CPU connected to the controller. In this case, FreeBSD resets the machine by unmapping all of memory space, which triple-faults the processor, putting it into the SHUTDOWN state. The chipset on the motherboard is supposed to convert this to a hard reset, and if it doesn't, well, it's bogus -- you're not fully AT-compatible if this doesn't work. All this is in /sys/i386/i386/vm_machdep.c if you want a look. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 18:10:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles117.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id A3BC1152DB for ; Sat, 6 Mar 1999 18:10:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA00994; Sat, 6 Mar 1999 18:04:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903070204.SAA00994@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. In-reply-to: Your message of "Fri, 05 Mar 1999 22:05:42 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Mar 1999 18:04:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 6 Mar 1999, Daniel C. Sobral wrote: > > Would something like what splash_bmp do be ok with you? It delegates > > to loader the responsibility of loading the file (ie, expects it to be > > loaded already). > > If thats all I've got to work with then it will have to do. Of course it's not all you have to work with; it's quite easy to read files inside the kernel. See eg. the new module code or the gzip image activator. > The file I need to read is a firmware image for a network device that > cannot be attached until the firmware is loaded. > > I would like to use something like splash_bmp to load a config file that > specifys a vendor ID/cookie, an image type, offset, and filename. > > The driver would parse this config file and would load the appropriate > firmware image for each card it detects. > > Due to licensing issues, firmware licensed for use with a particular > vendor card may not be used with cards from a different vendor, though > there is no technical reason why the same image can be used (that I know > of so far.) > > Obviously, I could pre-load all the firmware images available but this > seems wasteful. In addition, I would like the ability to upgrade the > firmware on a card without bringing down the system. While I might make a > device node to pipe the firmware image to the card once the system is up, > giving the driver the ability to request and load the firmware image on > demand would be nicer. I guess it depends on how the device might be used; myself I would actually almost be inclined to write the probe/download code in BootForth so that the adapter could be used to netboot the system. Failing that, it would make definite sense to demand-load the firmware as required, yes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Mar 6 18:19:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles117.castles.com [208.214.165.117]) by hub.freebsd.org (Postfix) with ESMTP id 7DBF414BFF for ; Sat, 6 Mar 1999 18:19:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA01052; Sat, 6 Mar 1999 18:14:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903070214.SAA01052@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD and ThinkPad In-reply-to: Your message of "Tue, 02 Mar 1999 22:56:03 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Mar 1999 18:14:13 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To start with, does it have more than 64M of memory? At least some of the stinkpads have problems with our speculative memory probes. > My new employer provided me with a brand new ThinkPad 770X. Of course the > first thing I tried was to boot FreeBSD on it. No luck :( > > The symptoms are as follows: sometime during the probing, or even later if > I'm active enough pressing keys (see below) the machine hangs, and never > recovers. I suspect it's somehow related to energy saving features - > perhaps it just decides to go to sleep? Anyway, after this I'm totally > unable to reboot it. The funny thing is that ThinkPad doesn't have the > reset button, so I have to pull out the battery in order to reboot it... > :-) > > Perhaps someone already went through this, and can give me a hint... TIA. > Oh, BTW - the BIOS setup on this really sucks, it's a winblows oriented > dummy icons which really don't give you any control over the details. > > Andrzej Bialecki > > -------------------- ++-------++ ------------------------------------- > ||PicoBSD|| FreeBSD in your pocket? Go and see: > Research & Academic |+-------+| "Small & Embedded FreeBSD" > Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ > -------------------- ~-+==---+-+ ------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Mar 6 19: 0:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 160AA14BFF for ; Sat, 6 Mar 1999 19:00:44 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id CAA60978 for ; Sun, 7 Mar 1999 02:34:54 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id CAA12643 for ; Sun, 7 Mar 1999 02:34:23 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903070234.CAA12643@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.org Subject: pipe(2) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 02:34:23 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Should pipe(2) be a bit stronger about what's ``conventional'' and mention that two uni-directional descriptors are returned by most operating systems ? I've been stung twice recently because I've assumed that the descriptors are bidirectional :-( If there are no objections, I'll update the man page: Index: pipe.2 =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/pipe.2,v retrieving revision 1.7 diff -u -r1.7 pipe.2 --- pipe.2 1997/01/20 23:18:01 1.7 +++ pipe.2 1999/03/07 02:32:11 @@ -111,6 +111,9 @@ .Xr read 2 , .Xr socketpair 2 , .Xr write 2 +.Sh STANDARDS +POSIX does not require that each descriptor is bidirectional. For +portability reasons, unidirectional descriptors should be assumed. .Sh HISTORY A .Fn pipe -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 19:13:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nias.int.gu.edu.au. (nias.int.gu.edu.au [132.234.113.102]) by hub.freebsd.org (Postfix) with SMTP id E783E14DEF for ; Sat, 6 Mar 1999 19:13:45 -0800 (PST) (envelope-from a1329698@nias.int.gu.edu.au) Received: from nias.int.gu.edu.au by nias.int.gu.edu.au. (SMI-8.6/SMI-SVR4) id NAA10121; Sun, 7 Mar 1999 13:12:21 +1000 Message-Id: <199903070312.NAA10121@nias.int.gu.edu.au.> Date: Sun, 7 Mar 1999 13:12:21 +1000 (EST) From: Andrew Stevenson Reply-To: Andrew Stevenson Subject: DTMF detection with a modem To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 8ezMjRZ3H/H0Q3Brqhoriw== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was just wondering if there was an easy way to use a modem for DTMF decoding under FreeBSD. The only info I can find seems to assume you are using TAPI under Windows. Does it vary from modem to modem? Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 20: 9:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (Postfix) with ESMTP id C859E14DEF for ; Sat, 6 Mar 1999 20:09:37 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id XAA02007; Sat, 6 Mar 1999 23:08:57 -0500 (EST) Date: Sat, 6 Mar 1999 23:08:57 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith Cc: "Daniel C. Sobral" , hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. In-Reply-To: <199903070204.SAA00994@dingo.cdrom.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, 6 Mar 1999, Mike Smith wrote: > I guess it depends on how the device might be used; myself I would > actually almost be inclined to write the probe/download code in > BootForth so that the adapter could be used to netboot the system. Thats certainly and idea but the set of people using token ring and the set of people wishing to netboot from it are non-intersecting at this point. I'm not sure likely that is to change. Any pointers on writing the probe/download code in Forth? I'm assuming I'll need to learn Forth first, but what are the entry points for drivers in BootForth? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 20:26: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id BCDC714C34 for ; Sat, 6 Mar 1999 20:26:00 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id PAA00750 for freebsd-hackers@FreeBSD.ORG; Sun, 7 Mar 1999 15:25:41 +1100 (EST) Message-ID: <19990307152541.O4858@rf900.physics.usyd.edu.au> Date: Sun, 7 Mar 1999 15:25:41 +1100 From: David Dawes To: freebsd-hackers@FreeBSD.ORG Subject: Re: GGI References: <36DFB421.1A845720@newsguy.com> <199903060712.XAA66928@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903060712.XAA66928@dingo.cdrom.com>; from Mike Smith on Fri, Mar 05, 1999 at 11:12:41PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 05, 1999 at 11:12:41PM -0800, Mike Smith wrote: >> (changed, subject, list, and cc list... it's almost a new mail! :) >> >> Terry Lambert wrote: >> > >> ... >> > I can't do the work for FreeBSD until it adopts GGI, and supports ELF >> ... >> > >> > The GGI people have been looking for someone (with commit priviledges, >> > obviously) to do a FreeBSD port, and have gone so far as to put the >> > kernel pieces of their predominantly Linux project *in the public domain*. >> >> I looked at GGI, and I liked it. If my memory doesn't fail me, Soren >> remarked that he was not much impressed with it last he checked it. >> >> What I'd like to know is if the Powers That Be of FreeBSD console >> (Soren and Yokota?) would, present state of the code >> notwithstanding, accept the adoption of GGI once deemed to be >> "ready", or if there is any fundamental flaw with it that makes this >> a hopeless propositon. > >Just FWIW, I was approached by one of the GGI group (actually, in the >employ of Creative, who are apparently going crazy right now about >cross-platform support) at Linuxworld. The GGI folks seem quite fervent >about fixing GGI so that everyone loves it, and they see FreeBSD as >possibly a better place to start getting it right than Linux (which >already has a half-assed framebuffer driver). Speaking of which (the Linux fb driver, not GGI), we're just adding a driver to XFree86 4.0 that can use the Linux fb driver. It is useful from our point of view for getting initial unaccelerated support for otherwise unsupported video cards. I had a feeling that something similar could be done for FreeBSD (using the VESA support in -current). Is that right? If so, is anyone interested in doing it? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 20:34:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id D34F3151B4 for ; Sat, 6 Mar 1999 20:34:08 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id PAA00777 for hackers@freebsd.org; Sun, 7 Mar 1999 15:33:50 +1100 (EST) Message-ID: <19990307153350.P4858@rf900.physics.usyd.edu.au> Date: Sun, 7 Mar 1999 15:33:50 +1100 From: David Dawes To: hackers@freebsd.org Subject: Setting MTRRs from the X server Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For XFree86 4.0, we really need to be able to have the X server request specific MTRR settings for different parts of a video card's physical memory address space. While turning WC on for the framebuffer is a big performance boost, a more critical issue is being able to make sure that WC is turned off for areas that are used for memory mapped I/O. We've found that some BIOSs enable WC in areas that our drivers want to use for MMIO. One example is the 0xb0000-0xbffff range. So what I'm looking for is an interface that our X server can use to request MTRR settings. An interface for this is present in the Linux 2.2.x kernel (and we recently added code to use it), although it doesn't currently allow changing the settings for the low 1MB of address space (but I'm told that will be added at some point). David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 20:41:57 1999 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 9AC3314C10 for ; Sat, 6 Mar 1999 20:41:55 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id NAA28768; Sun, 7 Mar 1999 13:41:38 +0900 (JST) Message-ID: <36E20333.884D63E7@newsguy.com> Date: Sun, 07 Mar 1999 13:40:19 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Reading a file inside the kernel. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > Any pointers on writing the probe/download code in Forth? I'm assuming > I'll need to learn Forth first, but what are the entry points for drivers > in BootForth? I suspect the idea is a forth code, loaded at "loader" time, that would do the probing and then load the appropriate file with load -t something, for later use by the driver by the driver at boot time. It would be along this line: : card_exists? ( -- flag ) ; : which_card? ( -- n ) ; : probe ( -- n | 0 ) card_exists? if which_card? else false then ; : load-microcode ( n -- ) n-to-name s" -t my_type" load ; : probe-and-load ( -- flag ) probe ?dup if ['] load-microcode catch then ; probe-and-load [if] .( Could not load microcode! ) cr [then] Only, hopefully, prettier. :-) With the about-to-be-introduced new loader.rc mechanism, you would actually place something similar to the above code in a microcode_probe.4th file, then add the following lines to loader.conf: yourmodulename_load="yes" yourmodulename_beforeload="probe-and-load" exec="include microcode_probe.4th" The thing is... bootforth is an afterthought of three-stage boot loader, not a solution carefully designed. It was along the lines "hey, we are beginning to write a scripting language, so not just add one?", and ficl was selected because it was small enough (and easy to plug in). :-) So, nobody actually stopped and made sure everything one needs is there. Dynamic memory allocation almost didn't made 3.1-RELEASE... :-) There is inb/outb, for instance, but if the probe requires anything else, it will probably have to be added. And until the time comes when someone actually wants to do something like this, it is unlikely that the situation will change. Me, I'm working to make bootforth useful, but the only driver I ever wrote didn't need anything more than inb/outb. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 6 22: 0:55 1999 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 050DD14CCC for ; Sat, 6 Mar 1999 22:00:52 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10JWB3-0004Ae-00; Sun, 7 Mar 1999 05:32:37 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10JWBx-00004Y-00; Sun, 7 Mar 1999 05:33:34 +0000 Date: Sun, 7 Mar 1999 05:33:33 +0000 (GMT) From: Andy Doran To: lcremean@tidalwave.net Cc: Mike Smith , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: BIOS reboot question from Linux user In-Reply-To: <19990306190005.A85183@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To clarify, FreeBSD first tries to reset the computer using the keyboard > controller (which is the original AT-compatible way of doing it). Some > machines, however, don't have the RST# line from the CPU connected to the > controller. In this case, FreeBSD resets the machine by unmapping all of > memory space, which triple-faults the processor, putting it into the > SHUTDOWN state. The chipset on the motherboard is supposed to convert this > to a hard reset, and if it doesn't, well, it's bogus -- you're not fully > AT-compatible if this doesn't work. > Isn't it a hell of a lot easier to generate a triple fault by doing: lidt bunch_of_zeros int 0 Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message