From owner-freebsd-hackers Sun Aug 17 00:02:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12976 for hackers-outgoing; Sun, 17 Aug 1997 00:02:39 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA12953 for ; Sun, 17 Aug 1997 00:02:28 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id RAA07158; Sun, 17 Aug 1997 17:01:20 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id QAA06679; Sun, 17 Aug 1997 16:31:18 +0930 (CST) Message-ID: <19970817163116.16698@lemis.com> Date: Sun, 17 Aug 1997 16:31:16 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: Michael Smith , FreeBSD Hackers Subject: Re: reset screen hardware? References: <199708170311.MAA04998@freebie.lemis.com> <13880.871792654@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <13880.871792654@time.cdrom.com>; from Jordan K. Hubbard on Sat, Aug 16, 1997 at 09:37:34PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Aug 16, 1997 at 09:37:34PM -0700, Jordan K. Hubbard wrote: >> If there's one thing that pisses me off about many FreeBSD hackers, >> it's this attitude "Ooh, this is nasty. I don't want to have anything >> to do with it". Lots of PC hardware is nasty. Messing around in a 16 >> bit BIOS is nasty. IDE is nasty. VGA is nasty. Come to think of it, >> what's nice about PC hardware? But FreeBSD's acceptance suffers >> significantly because nobody can be bothered to deal with these nasty >> things. Where's the Win-32 emulator? ... > > Funny, my bigget rant has to do with people going "Why doesn't FreeBSD > have feature XXX?!" rather than "Here are my diffs to support feature > XXX, please integrate them." And would you? If I had come along with the diffs for doing it this way, you'd have said (with some justification) "Go away, we don't want all this crap in the kernel". I was, in fact, considering doing the implementation, but I see that it's not the way to go. > Why? Well, we'd have support for a lot more "nasty" stuff if there > were more people around who were willing to do the actual > implementation work and be willing to actively support it afterwards > so it doesn't go stale (like the 1st ISDN drivers, for example). > That's the real problem here. Well, since you mention the ISDN stuff, I seem to recall we would have got it in the kernel long ago (like about March 1996) if it had been approved by the core team . That was before Dietmar Friede got bent out of shape about something or another. The lack of ability to commit the code was one reason why the effort seems to have lost focus--if that is the case. I no longer live in an area where ISDN is a viable method to connect to the net, so I'm on analogue again, and I'm not following the ISDN groups too closely. Greg From owner-freebsd-hackers Sun Aug 17 00:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14146 for hackers-outgoing; Sun, 17 Aug 1997 00:21:26 -0700 (PDT) Received: from csnet.cs.technion.ac.il (csnet.cs.technion.ac.il [132.68.32.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA14137 for ; Sun, 17 Aug 1997 00:21:16 -0700 (PDT) Received: from csd.csa (csd [132.68.32.8]) by csnet.cs.technion.ac.il (8.6.11/8.6.10) with ESMTP id KAA19646; Thu, 14 Aug 1997 10:23:45 +0300 Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id KAA10826; Thu, 14 Aug 1997 10:23:36 +0300 Date: Thu, 14 Aug 1997 10:23:35 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Atipa cc: Ada T Lim , "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: Re: Alpha Benchmarks was: Re: FreeBSD --- ALPHA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Atipa wrote: > > > On Wed, 13 Aug 1997, Ada T Lim wrote: > [snip] > > Not true. They are noticably different. The benchmarks show: > > +--------------+------------+-----------+ > | 533MHz | SPECint95 | SPECfp95 | > +--------------|------------|-----------| > | 21164 (LX) | 16.4 | 22.5 | > +--------------|------------|-----------| > | 21164PC (SX) | 14.0 | 17.0 | > +--------------|------------|-----------| > | 300MHz P-II | 11.6 | 7.2 | (Intel's closest to referece) > +--------------+------------+-----------+ > > Max programmable bus speed for the 21164 is 200MHz, and the highest for > the 21164PC is 133MHz. NT (Linux/OpenBSD/NetBSD???) requires the "Windows > NT Alpha BIOS Firmware" on the motherboard. You can get the BIOS on either > the SX or LX motherboard. Also, the 21164PC doesn't have the 96KB L2 cache on-chip cache that the 21164 has, which makes for another reason for the lower performance of the 21164PC. > > Both of these are tons faster than a 300MHz Pentium II. Our latest > DEC catalog says to look for the next generation of Alpha to use a 0.25 > micron CMOS process, with SPECint95 over 30, and SPECfp95 over 50, and > 2GB/sec memory bandwidth. That's over 700% faster floating point than a > 300MHz Pentium II! > > Can't wait for FreeBSD to support it... > > Kevin > Nadav From owner-freebsd-hackers Sun Aug 17 00:42:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA15079 for hackers-outgoing; Sun, 17 Aug 1997 00:42:49 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA15073 for ; Sun, 17 Aug 1997 00:42:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id AAA14345; Sun, 17 Aug 1997 00:42:34 -0700 (PDT) To: Greg Lehey cc: Michael Smith , FreeBSD Hackers Subject: Re: reset screen hardware? In-reply-to: Your message of "Sun, 17 Aug 1997 16:31:16 +0930." <19970817163116.16698@lemis.com> Date: Sun, 17 Aug 1997 00:42:34 -0700 Message-ID: <14340.871803754@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, since you mention the ISDN stuff, I seem to recall we would have > got it in the kernel long ago (like about March 1996) if it had been I was talking about the even earlier stuff - Friede's earlier work with the Dr. Neuhaus cards. That *did* make it into the kernel long ago and then rotted away for lack of attention and was finally removed. Jordan From owner-freebsd-hackers Sun Aug 17 01:11:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16132 for hackers-outgoing; Sun, 17 Aug 1997 01:11:31 -0700 (PDT) Received: from agni.nuko.com (dummy.nuko.com [206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16126 for ; Sun, 17 Aug 1997 01:11:29 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id BAA25936; Sun, 17 Aug 1997 01:09:46 -0700 (PDT) From: Vinay Bannai Message-Id: <199708170809.BAA25936@agni.nuko.com> Subject: Re: Device drivers and DMA details?? To: dg@root.com Date: Sun, 17 Aug 1997 01:09:46 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708170133.SAA04271@implode.root.com> from "David Greenman" at "Aug 16, 97 06:33:20 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to David Greenman: > >Also, while examining the fxp driver, the fxp_start() seems to be > >invoked at the time of each incoming packet (or interrupt from the > >device). Wouldn't this not create a delay in sending packets? Or is it > >that the fxp_start() also gets invoked whenever a packet is shoved on > >the network IF queues? > > The driver start routine is also called when a packet is sent. See the > end of the ether_output() function in /sys/net/if_ethersubr.c. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Ah!! I see that the interface's if_start() routine is called when the network is not busy (IFF_OACTIVE). This means that IFF_OACTIVE is set for the interface while receiving the packet or when the controller is busy. In fact it appears that the fxp driver never has the need to set the IFF_OACTIVE, so the fxp_start() gets called everytime a packet is queued on the interface queue unless it is running at a priority of the hardware interrupt from the network controller. In that case since the hardware interrupt from the network controller being higher than splimp() will make it possible for the IF queues to be flushed before the priority drops back to splimp or whatever. Is that a correct assesment? Thanks Vinay From owner-freebsd-hackers Sun Aug 17 01:35:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16848 for hackers-outgoing; Sun, 17 Aug 1997 01:35:11 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16843 for ; Sun, 17 Aug 1997 01:35:09 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA08684; Sun, 17 Aug 1997 01:36:44 -0700 (PDT) Message-Id: <199708170836.BAA08684@implode.root.com> To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device drivers and DMA details?? In-reply-to: Your message of "Sun, 17 Aug 1997 01:09:46 PDT." <199708170809.BAA25936@agni.nuko.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 17 Aug 1997 01:36:44 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Ah!! I see that the interface's if_start() routine is called when the >network is not busy (IFF_OACTIVE). This means that IFF_OACTIVE is set for >the interface while receiving the packet or when the controller is >busy. Uh, no, IFF_OACTIVE indicates that the interface is busy transmitting one or more packets and that it can't handle any additional packets for xmit right now. > In fact it appears that the fxp driver never has the need to set the >IFF_OACTIVE, so the fxp_start() gets called everytime a packet is queued >on the interface queue Yes, IFF_OACTIVE is optional and is meant as a sort of optimization to avoid calling the driver start routine. It doesn't make sense for if_fxp because the fxp card supports dynamic chaining; in other words, a DMA chain that is currently being transmitted can be extended with additional packets. The only limit to how much the chain can be extend is an arbitrary one having to do with the available DMA descriptors. I could actually set IFF_OACTIVE when all transmit descriptors are exhausted, but the extra overhead to deal with this wasn't worth it - it's a very rare condition and the check at the top of fxp_start() will handle this case and return immediately. > unless it is running at a priority of the hardware >interrupt from the network controller. In that case since the hardware >interrupt from the network controller being higher than splimp() will make >it possible for the IF queues to be flushed before the priority drops back >to splimp or whatever. Huh? "network controller being higher than splimp()"? Huh? None of the above makes any sense. > Is that a correct assesment? Yes, except for the last part. spl* protection is for protecting certain critical regions from modification by interrupt routines. While the code has an spl* level set, interrupts in that class will be blocked. splimp blocks network device interrupts. splnet blocks network (input) packet processing that would normally occur when the system returns to spl0. Received packets are processed at spl0 in order to avoid certain driver reentrancy problems when packets are being forwarded. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Aug 17 02:47:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19720 for hackers-outgoing; Sun, 17 Aug 1997 02:47:27 -0700 (PDT) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19700 for ; Sun, 17 Aug 1997 02:47:21 -0700 (PDT) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.6/8.6.9) with ESMTP id LAA00491 for ; Sun, 17 Aug 1997 11:45:29 GMT Message-Id: <199708171145.LAA00491@peedub.muc.de> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: reset screen hardware? Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 17 Aug 1997 00:42:34 MST." <14340.871803754@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 1997 11:45:29 +0000 From: Gary Jennejohn Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" writes: >> Well, since you mention the ISDN stuff, I seem to recall we would have >> got it in the kernel long ago (like about March 1996) if it had been > >I was talking about the even earlier stuff - Friede's earlier work >with the Dr. Neuhaus cards. That *did* make it into the kernel long >ago and then rotted away for lack of attention and was finally removed. > because we moved from ii0.1 (which was the old stuff in the tree) to ii0.2. ii0.2 was relatively much cleaner than ii0.1 (even though it was still a mess in many ways). Then, as Greg wrote, Dietmar got bent out of shape at about the time J"org had reviewed the new stuff (aka bisdn) and I was ready to import it and we had to start re-writing the whole schmeer. _That's_ the story with ISDN. --- Gary Jennejohn Home - garyj@muc.de Work - gjennejohn@frt.dec.com From owner-freebsd-hackers Sun Aug 17 02:52:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19978 for hackers-outgoing; Sun, 17 Aug 1997 02:52:02 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19956 for ; Sun, 17 Aug 1997 02:51:57 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id LAA00412; Sun, 17 Aug 1997 11:51:19 +0200 (MEST) From: Søren Schmidt Message-Id: <199708170951.LAA00412@sos.freebsd.dk> Subject: Re: reset screen hardware? In-Reply-To: <19970817163116.16698@lemis.com> from Greg Lehey at "Aug 17, 97 04:31:16 pm" To: grog@lemis.com (Greg Lehey) Date: Sun, 17 Aug 1997 11:51:19 +0200 (MEST) Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Greg Lehey who wrote: > > > > Funny, my bigget rant has to do with people going "Why doesn't FreeBSD > > have feature XXX?!" rather than "Here are my diffs to support feature > > XXX, please integrate them." > > And would you? If I had come along with the diffs for doing it this > way, you'd have said (with some justification) "Go away, we don't want > all this crap in the kernel". I was, in fact, considering doing the > implementation, but I see that it's not the way to go. Come on here, what at least I have been advocating for, is that we need that functionality, but we need it done RIGHT. We allready have so many kludges/hacks in the kernel, we don't need another one. If Joe random hacker cannot graps the bigger picture, and get his hacks in the right direction, well, I'm sorry it won't be commited. On the other hand, if Joe mature hacker comes around, and wants to help do the hard work along the guidelines that the responsible person(s) have laid out (and belive me, for the most part things has been thought long and seriously about), he will be welcommed with open arms. So to get concrete in this matter, we need: 1. Being able to call realmode code from the kernel. 2. Being able to run BIOS functions, that is we need to keep track of the BIOS's workspace, most often in low memory. 3. Then write the code to call the right BIOS functions to be able to talk to the video HW. So, if someone is SERIOUS about getting this to work, pick one of the above, come back to me so we can get technical about the details, and them submit the diffs. Then I'm certain it will be committed, and the author will get his fair share of applause.. But gimme a break on just demanding XXX functionality, sometimes with badly (if at all) designed hacks.... So got that of my chest... Ahhhh... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Aug 17 03:10:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20787 for hackers-outgoing; Sun, 17 Aug 1997 03:10:10 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20713 for ; Sun, 17 Aug 1997 03:09:59 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA04212; Sun, 17 Aug 1997 19:39:41 +0930 (CST) From: Michael Smith Message-Id: <199708171009.TAA04212@genesis.atrad.adelaide.edu.au> Subject: Re: reset screen hardware? In-Reply-To: <199708170311.MAA04998@freebie.lemis.com> from Greg Lehey at "Aug 17, 97 12:41:37 pm" To: grog@lemis.com (Greg Lehey) Date: Sun, 17 Aug 1997 19:39:40 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: > >> > >> How about a more positive approach? I know plenty of people who'll > >> tell me in vivid detail why things won't work. > > > > This is like asking for a positive approach to a VMS ABI emulation > > module 8) > > Yes. If people want it. I didn't say it had to be nice. I'm not sure I can parse that. > -- rant mode on -- > > If there's one thing that pisses me off about many FreeBSD hackers, > it's this attitude "Ooh, this is nasty. I don't want to have anything > to do with it". I don't see how this is relevant to the discussion at hand. What is currently being said is "there is a tough problem. The proposed solution sucks both from a practicality and a supportability point of view. In addition, a more general and elegant solution is already being implemented." That's not "this is nasty". > Lots of PC hardware is nasty. Messing around in a 16 > bit BIOS is nasty. IDE is nasty. VGA is nasty. Come to think of it, > what's nice about PC hardware? But FreeBSD's acceptance suffers > significantly because nobody can be bothered to deal with these nasty > things. Where's the Win-32 emulator? ... There are two of them; both accumulating significant support and offering usefully overlapping feature sets. Note that neither of their development teams have the biollion-plus development budget of the original. > >>> We wont have hundreds of K's of code like that in kernel space. > >> > >> That's for sure. But who says it'll be hundreds of Ks? > > > > Have a look at the X server sources someday. > > Must I? I took a look at SuperProbe. The binary is 83 kB, and in the > kernel some of that could go. Sure, that's too much for the kernel, > too, but it's still not hundreds. Turn around, go back. SuperProbe != video chipset drivers. > > Basically, it is not possible to take a snapshot of the state of a > > modern video adapter without uintimate knowledge of the hardware > > involved. Such a snapshot is often useless anyway, as it does not > > contain information about the state transitions prior to the snaphot > > state, which may be very significant to the hardware's current mode of > > operation. > > But we still have the evidence that every X server manages to reset > them most of the time. That's _right_. But it achieves this by knowing, in fact having _been_told_ in advance what the hardware is, and thus having hardware-specific intelligence. The point is that this intelligence is foreign to the kernel, unmaintainable in the kernel environment, and _inevitably_ will lag, often indefinitely, behind hardware development. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 03:11:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20912 for hackers-outgoing; Sun, 17 Aug 1997 03:11:52 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20889; Sun, 17 Aug 1997 03:11:41 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id JAA09308; Sat, 16 Aug 1997 09:20:53 +0200 (CEST) To: Michael Smith cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Sat, 16 Aug 1997 11:08:19 +0930." <199708160138.LAA29530@genesis.atrad.adelaide.edu.au> Date: Sat, 16 Aug 1997 09:20:52 +0200 Message-ID: <9306.871716052@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708160138.LAA29530@genesis.atrad.adelaide.edu.au>, Michael Smith writes: >Poul-Henning Kamp stands accused of saying: >> >> >Anyway, tell us which parallel-port-hardware should be first ported. >> >--------------------------------------------------------------------------- >- >> >> Well, how about parallel printers and the PLIP/LPIP support ? :-) > >Printers are already (sort of) supported with the 'nlpt' driver. If you >could work out why interrupts don't work, that'd be great of course. > >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >done with your help... Come on guys... PLIP is so simple as it can be... I don't have the time at this point to go back and kick PLIP again... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Sun Aug 17 03:12:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20970 for hackers-outgoing; Sun, 17 Aug 1997 03:12:03 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20910; Sun, 17 Aug 1997 03:11:51 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id UAA06619; Fri, 15 Aug 1997 20:42:02 +0200 (CEST) To: Nicolas Souchu cc: FreeBSD hackers , FreeBSD hardware Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Fri, 15 Aug 1997 20:41:23 -0000." <33F4BEF3.446B9B3D@prism.uvsq.fr> Date: Fri, 15 Aug 1997 20:42:02 +0200 Message-ID: <6617.871670522@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <33F4BEF3.446B9B3D@prism.uvsq.fr>, Nicolas Souchu writes: > > - plip should of course. > We want to move it to a standalone file... plip.c? it should probably go in netinet/if_lp.c for consistency... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Sun Aug 17 03:38:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA22218 for hackers-outgoing; Sun, 17 Aug 1997 03:38:07 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22196; Sun, 17 Aug 1997 03:37:59 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA04335; Sun, 17 Aug 1997 20:07:42 +0930 (CST) From: Michael Smith Message-Id: <199708171037.UAA04335@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <6617.871670522@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 15, 97 08:42:02 pm" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Sun, 17 Aug 1997 20:07:42 +0930 (CST) Cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp stands accused of saying: > In message <33F4BEF3.446B9B3D@prism.uvsq.fr>, Nicolas Souchu writes: > > > > - plip should of course. > > We want to move it to a standalone file... plip.c? > > it should probably go in netinet/if_lp.c for consistency... I don't think so. It certainly doesn't belong in the "internet" networking code. The tradition with interface drivers seems to be to park them at the level of the device they drive, ie. ISA network hardware drivers are in the ISA bus-specific directory, so it would make the most sense to me to put it in dev/ppbus/if_lp.c > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 05:21:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA25157 for hackers-outgoing; Sun, 17 Aug 1997 05:21:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA25151 for ; Sun, 17 Aug 1997 05:21:30 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA15673 for hackers@FreeBSD.ORG; Sun, 17 Aug 1997 14:21:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA01412; Sun, 17 Aug 1997 14:16:32 +0200 (MET DST) Message-ID: <19970817141632.FT54182@uriah.heep.sax.de> Date: Sun, 17 Aug 1997 14:16:32 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Aug 12, 1997 15:29:35 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > I can always call it something else (newnewsyslog?), but I was > wondering if FreeBSD Inc would consider utilities that were not > written in C? If the advantages of the prospective rewrite would outweigh the disadvantages (like slower startup and higher CPU load), there are usually only objections by the (not very large) ``anti-bloatist club''. Some of the tools have already been rewritten in Perl, think of Wolfram Schneider's vastely improved catman(1), or my version of whereis(1) that replaced the crippled 4.4BSD version. Whoever has been looking into the 4.3BSD (Net/2) version of whereis(1), and who at least knows how scripting languages work, and what their advantages are, will certainly quickly agree with me that rewriting it in Perl was the better way out. I assume Wolfram's reasoning with catman(1) was similar. The 80 % accepted opinion of the core team is that new languages, and scripting languages in particular, might have their right to exist if they really offer advantage when and where they are used (like easier code maintenance, much improved features, etc.) We are in the 1990's, not in the 1970's. But before you're going to rewrite something that does already exist, look whether it will be justified. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 05:51:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA26068 for hackers-outgoing; Sun, 17 Aug 1997 05:51:19 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA26062 for ; Sun, 17 Aug 1997 05:51:12 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA16179; Sun, 17 Aug 1997 14:51:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA01444; Sun, 17 Aug 1997 14:29:43 +0200 (MET DST) Message-ID: <19970817142943.IB36053@uriah.heep.sax.de> Date: Sun, 17 Aug 1997 14:29:43 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: rdkeys@csemail.cropsci.ncsu.edu Subject: Re: Kernel rebuild timezone error in param.c References: <9708152246.AA101234@csemail.cropsci.ncsu.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9708152246.AA101234@csemail.cropsci.ncsu.edu>; from rdkeys@csemail.cropsci.ncsu.edu on Aug 15, 1997 18:46:20 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As rdkeys@csemail.cropsci.ncsu.edu wrote: > FreeBSD 2.2.-970814-SNAP. > > While rebuilding my kernel I get an error in param.c: > > cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc > -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DSYSVMSG -DSYSVSEM > -DSYSVSHM -DVISUAL_USERCONFIG -DUSERCONFIG -DUCONSOLE -DBOUNCE_BUFFERS > -DCOMPAT_43 -DPROCFS -DDFFS -DINET -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 > -DMAXUSERS=10 param.c > param.c:82: `TIMEZONE' undeclared here (not in a function) > param.c:82: initializer element for `tz.tz_minuteswest' is not constant > param.c:82: `DST' undeclared here (not in a function) > param.c:82: initializer element for `tz.tz_dsttime' is not constant You must be using some terribly old code. The timezone information has long since been diminished from the kernel. Timezones are completely handled in userland (and on a per-process and thus per-user basis). I suspect you're using a config(8) that doesn't match your kernel sources. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 06:06:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA26541 for hackers-outgoing; Sun, 17 Aug 1997 06:06:59 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA26519; Sun, 17 Aug 1997 06:06:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA17339; Sun, 17 Aug 1997 23:03:13 +1000 Date: Sun, 17 Aug 1997 23:03:13 +1000 From: Bruce Evans Message-Id: <199708171303.XAA17339@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com Subject: Re: Parallel port developpements - ppbus Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>[plip driver] >I don't think so. It certainly doesn't belong in the "internet" networking >code. The tradition with interface drivers seems to be to park them at >the level of the device they drive, ie. ISA network hardware drivers >are in the ISA bus-specific directory, so it would make the most sense >to me to put it in dev/ppbus/if_lp.c It makes no sense to put it there either, since sys/dev is for bus-independent (parts of) drivers. Bruce From owner-freebsd-hackers Sun Aug 17 06:31:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA27286 for hackers-outgoing; Sun, 17 Aug 1997 06:31:00 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA27273 for ; Sun, 17 Aug 1997 06:30:56 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id PAA09255 for hackers@FreeBSD.ORG; Sun, 17 Aug 1997 15:15:25 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id NAA28573; Sun, 17 Aug 1997 13:24:24 +0200 (CEST) Message-ID: <19970817132424.37524@klemm.gtn.com> Date: Sun, 17 Aug 1997 13:24:24 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: Re: A bit off topic: GCC 2.8??? References: <199708160900.LAA00307@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.79 In-Reply-To: ; from Chuck Robey on Sat, Aug 16, 1997 at 10:45:27AM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Aug 16, 1997 at 10:45:27AM -0400, Chuck Robey wrote: > On Sat, 16 Aug 1997, Mikael Karpberg wrote: > > > Hello! > > > > I'm interested in using exceptions and other final standard C++ thingies, > > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > > but is it out there somewhere? > > You realize, I hope, that FreeBSD isn't going to jump to 2.8 the moment > it's released, anyhow. Just like every other upgrade of gcc, there will > be a long waiting period, while the new gcc has all the bugs shaken out of > it. I think last time it was about a year, wasn't it? We´ll make a FreeBSD port if 2.8 is out... ;-) Maybe we can wipe out the pgcc stuff then ? Andreas /// -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sun Aug 17 06:35:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA27526 for hackers-outgoing; Sun, 17 Aug 1997 06:35:42 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA27506; Sun, 17 Aug 1997 06:35:34 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA06011; Sun, 17 Aug 1997 23:05:19 +0930 (CST) From: Michael Smith Message-Id: <199708171335.XAA06011@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <199708171303.XAA17339@godzilla.zeta.org.au> from Bruce Evans at "Aug 17, 97 11:03:13 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 17 Aug 1997 23:05:18 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > >>[plip driver] > > >I don't think so. It certainly doesn't belong in the "internet" networking > >code. The tradition with interface drivers seems to be to park them at > >the level of the device they drive, ie. ISA network hardware drivers > >are in the ISA bus-specific directory, so it would make the most sense > >to me to put it in dev/ppbus/if_lp.c > > It makes no sense to put it there either, since sys/dev is for > bus-independent (parts of) drivers. Well, then I'd better move the ppbus stuff. It makes no sense to me to have Yet Another toplevel directory for this though, and sys/dev strikes me as being the ideal place for architecture-independent device drivers. Any consensus on this? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 08:39:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05150 for hackers-outgoing; Sun, 17 Aug 1997 08:39:46 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05113; Sun, 17 Aug 1997 08:39:38 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id BAA06417; Mon, 18 Aug 1997 01:09:14 +0930 (CST) From: Michael Smith Message-Id: <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <9306.871716052@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 16, 97 09:20:52 am" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Mon, 18 Aug 1997 01:09:14 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp stands accused of saying: > > > >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best > >done with your help... > > Come on guys... PLIP is so simple as it can be... I don't have the time > at this point to go back and kick PLIP again... If it's really that simple; where can I find some documentation on it? Is there a Linux mini-hownotto or something that spells it out in terms a poor simple brain like mine could handle? Is it likely to work on a port that's open to shared use? > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 10:18:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10156 for hackers-outgoing; Sun, 17 Aug 1997 10:18:43 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10132; Sun, 17 Aug 1997 10:18:33 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id TAA11280; Sun, 17 Aug 1997 19:13:03 +0200 (CEST) To: Michael Smith cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Mon, 18 Aug 1997 01:09:14 +0930." <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Date: Sun, 17 Aug 1997 19:13:03 +0200 Message-ID: <11278.871837983@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708171539.BAA06417@genesis.atrad.adelaide.edu.au>, Michael Smith writes: >Poul-Henning Kamp stands accused of saying: >> > >> >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >> >done with your help... >> >> Come on guys... PLIP is so simple as it can be... I don't have the time >> at this point to go back and kick PLIP again... > >If it's really that simple; where can I find some documentation on it? >Is there a Linux mini-hownotto or something that spells it out in >terms a poor simple brain like mine could handle? sys/i386/isa/lpt.c :-) >Is it likely to work on a port that's open to shared use? no. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Sun Aug 17 12:24:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA16695 for hackers-outgoing; Sun, 17 Aug 1997 12:24:15 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA16685 for ; Sun, 17 Aug 1997 12:24:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07163; Sun, 17 Aug 1997 12:17:24 -0700 From: Terry Lambert Message-Id: <199708171917.MAA07163@phaeton.artisoft.com> Subject: Re: Password Handling To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Sun, 17 Aug 1997 12:17:23 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Aug 16, 97 05:38:12 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been looking through the source code to login.c and various .h files, > can someone tell me why login.c defines NBUFSIZE (size of the login name > buffer i think) as UT_NAMESIZE+64, where UT_NAMESIZE is 8 (from utmp.h), Read the comment immediately before the definition: "Allow for authentication style and/or kerberos instance" Then read the 20 or so lines of code immediately below the comment... the point is to allow the input of options for kerberos or another authentication style argument, in addition to the user name. > even though MAXLOGNAME from sys/param.h is 12. sys/param.h is a kernel header. Ignore values there unless you are talking to kernel interfaces (published or via libkvm grovelling in /dev/kmem). > The reason I am asking is that I am designing a server that requires > user logins (I have looked at ftpd.c also) and am wondering if it is > appropriate to use the figure in sys/param.h as the max user name length. No. Use the value from utmp.h, it is the value the rest of the system will use. Sidebar: You must be running old code if this value is 8. > Also another thing that confuses me a bit with freebsd is crypt is > systems that use DES you can do a crypt on the plain text and a > strcmp against the encrypted password returned from getpwnam(), in > freebsd with shadowed passwords and either md5 or des are password > checks handled the same assuming your daemon is running uid 0? The actual password field values are accessable only to root. If they were not, then your system would be succeptible to password cracking techniques, including dictionary-based attacks. Your daemon should verify the user credentials, and then give up uid 0 in favor of the uid associated with the credentials. This assumes that the daemon is verifying the credentials against the system user database, and not a service-specific user database... probably the case, or your question would be meaningless (if a daemon is maintaining it's own user database, it can maintain it however it wants, shadow passwords or not, etc.). Things which verify passwords are gatekeepers; you must be able to trust your gatekeepers with the keys to the gate. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 17 12:42:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17445 for hackers-outgoing; Sun, 17 Aug 1997 12:42:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA17439 for ; Sun, 17 Aug 1997 12:42:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07196; Sun, 17 Aug 1997 12:33:21 -0700 From: Terry Lambert Message-Id: <199708171933.MAA07196@phaeton.artisoft.com> Subject: Re: reset screen hardware? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 17 Aug 1997 12:33:21 -0700 (MST) Cc: grog@lemis.com, sos@sos.freebsd.dk, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708170301.MAA03401@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 17, 97 12:31:55 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is like asking for a positive approach to a VMS ABI emulation > module 8) hahahahahahaha! 8-) 8-). > > > We wont have hundreds of K's of code like that in kernel space. > > > > That's for sure. But who says it'll be hundreds of Ks? > > Have a look at the X server sources someday. But be sure to only look at the DDX code for the generic VGA, since that's the only thing that will be there by default in any sane design. Basically, something that has to be there anyway, if we ever go for more Linux support. The difference is the libvga stuff in Linux isn't used by their X server, so it's redundant code. 8-). > > 3. How to we implement it? Ah, there's the rub. I still think it > > belongs in the probe routines when the system starts up, but on > > the other hand I agree with S=F8ren that kernel bloat is Bad. > > Call the BIOS on the video card. See above. This won't necessarily result in the card going from some arbitrary state to some known state, unless the BIOS was used to get the card into that state in the first place. Specifically, there exist write-only registers which are shadowed in RAM on a number of cards, and any modification outside the BIOS will result in the shadow data being rendered stale. Any attempt to restore the card toa known state using BIOS will only operate on the deltas from the shadow state to the desired state. Unless you modify X to use the BIOS calls to set the card state, you will not be able to use the BIOS to reset the card state. Further, it's probably desirable to link the state restoration to the *previous* state, which may not be known to the console driver, rather than the default state (which might be). For example, consider a 50 line text display following the manual loading of a VGA font for support of this mode, the memory for which is subsequently stomped by the X server. Consider also the possible consequences of a previous mode that was not the default mode for the kernel debugger in a break to kernel debugger while X is active on the console. If a BIOS-based approach is used, it will seriously limit the available modes for normal console operation and for X servers; this is probably an unacceptable consequence. [ ... ] > Hah. You obviously haven't had to work with PC viode hardware, have you? I agree with this "hah"... that last suggestion was naieve. On the other hand, I don't think it was punishably so, I think he was just trying to compromise with an uncompromising opponent. 8-) 8). > On the other hand, the manufacturer of the card _does_ know intimately > how it works. They write functions for manipulating the card > hardware, and stick them in a PROM on the card. > > Why not use their code and save ourselves the agony? Because unless you use their code for all things, the result of using their code is indeterminate. Even if the automaton involved is determinant (it is), the results depend entirely on the start states (they aren't). It's like running Conway's "Life" in hardware. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 17 12:46:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17645 for hackers-outgoing; Sun, 17 Aug 1997 12:46:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA17640 for ; Sun, 17 Aug 1997 12:46:02 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07219; Sun, 17 Aug 1997 12:36:56 -0700 From: Terry Lambert Message-Id: <199708171936.MAA07219@phaeton.artisoft.com> Subject: Re: reset screen hardware? To: grog@lemis.com (Greg Lehey) Date: Sun, 17 Aug 1997 12:36:56 -0700 (MST) Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <19970817163116.16698@lemis.com> from "Greg Lehey" at Aug 17, 97 04:31:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Funny, my bigget rant has to do with people going "Why doesn't FreeBSD > > have feature XXX?!" rather than "Here are my diffs to support feature > > XXX, please integrate them." > > And would you? If I had come along with the diffs for doing it this > way, you'd have said (with some justification) "Go away, we don't want > all this crap in the kernel". I was, in fact, considering doing the > implementation, but I see that it's not the way to go. NFS server locking, anyone? <...ducks...> Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 17 12:56:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18181 for hackers-outgoing; Sun, 17 Aug 1997 12:56:23 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18172 for ; Sun, 17 Aug 1997 12:56:20 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07244; Sun, 17 Aug 1997 12:49:10 -0700 From: Terry Lambert Message-Id: <199708171949.MAA07244@phaeton.artisoft.com> Subject: Re: reset screen hardware? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 17 Aug 1997 12:49:09 -0700 (MST) Cc: grog@lemis.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708171009.TAA04212@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 17, 97 07:39:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > That's _right_. But it achieves this by knowing, in fact having > _been_told_ in advance what the hardware is, and thus having > hardware-specific intelligence. The point is that this intelligence > is foreign to the kernel, unmaintainable in the kernel environment, > and _inevitably_ will lag, often indefinitely, behind hardware > development. 1) Make X use the kernel driver. Period. This is necessary whether the driver is card-specific, generic BIOS-based, or generic VGA (and BIOS) based. 2) Default to a generic VGA driver. This is your fallback position for "anything which works is better than anything which doesn't". 3) If there is a card specific driver and you have the card, load the LKM for it at boot time after the FS's are mounted and the driver code can be located. Use the LKM driver in place of the generic driver from then on. 4) If you are running an ELF/OLF kernel, and the VM system supports section attribution and section naming, discard the "generic VGA" section after loading the LKM. 5) If you are running an ELF/OLF kernel, and you have a section archiver available, you may (at your option), take the generic kernel, dearchive the section(s) containing the generic VGA driver, and replace them with the section(s) for the card specific driver. 6) If you are running an ELF/OLF kernel, and you have a section archiver available, you may "tune" the kernel down to the point where it contains *only* drivers for existing hardware and reasonably expected expansion hardware. 7) ...ROM that kernel! (And other nifty things...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 17 12:58:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18270 for hackers-outgoing; Sun, 17 Aug 1997 12:58:21 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA18256 for ; Sun, 17 Aug 1997 12:58:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07267; Sun, 17 Aug 1997 12:52:14 -0700 From: Terry Lambert Message-Id: <199708171952.MAA07267@phaeton.artisoft.com> Subject: Re: What's the interest in standard tools rewritten in perl? To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 17 Aug 1997 12:52:14 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970817141632.FT54182@uriah.heep.sax.de> from "J Wunsch" at Aug 17, 97 02:16:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If the advantages of the prospective rewrite would outweigh the > disadvantages (like slower startup and higher CPU load), there are > usually only objections by the (not very large) ``anti-bloatist > club''. This is kind of unfair. The club is *intentionally* "not very large" for the obvious philosophical reasons... 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 17 13:40:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA20551 for hackers-outgoing; Sun, 17 Aug 1997 13:40:06 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20483 for ; Sun, 17 Aug 1997 13:39:58 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id WAA00331; Sun, 17 Aug 1997 22:40:10 +0200 (MEST) From: Søren Schmidt Message-Id: <199708172040.WAA00331@sos.freebsd.dk> Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: <19970817141632.FT54182@uriah.heep.sax.de> from J Wunsch at "Aug 17, 97 02:16:32 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 17 Aug 1997 22:40:10 +0200 (MEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > As Jaye Mathisen wrote: > > > I can always call it something else (newnewsyslog?), but I was > > wondering if FreeBSD Inc would consider utilities that were not > > written in C? > > If the advantages of the prospective rewrite would outweigh the > disadvantages (like slower startup and higher CPU load), there are > usually only objections by the (not very large) ``anti-bloatist > club''. Give us a break, will ya :) > The 80 % accepted opinion of the core team is that new languages, and > scripting languages in particular, might have their right to exist if > they really offer advantage when and where they are used (like easier > code maintenance, much improved features, etc.) We are in the 1990's, > not in the 1970's. But before you're going to rewrite something that > does already exist, look whether it will be justified. I wouldn't bet on that 80% factor, if somebody is going to rewrite the base utils. For one this is a total waste of time (and maybe talent), the other is that it will render us completely incompatible with the rest of the BSD world. I think that nobody would be stupid enough to willingly takeover that kind of maintenance burden... If I want useless bloat (useless meaning just rewrites here), I'll go use Micro$oft's products, that way I can get all the useless bloat I can even imagine... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Aug 17 13:41:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA20696 for hackers-outgoing; Sun, 17 Aug 1997 13:41:21 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA20673 for ; Sun, 17 Aug 1997 13:41:15 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 500 invoked by uid 1001); 17 Aug 1997 20:41:10 +0000 (GMT) To: hackers@freebsd.org Subject: Problems detecting ATAPI CDROM in 2.2-970801-RELENG X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 17 Aug 1997 22:41:10 +0200 Message-ID: <498.871850470@verdi.nethelp.no> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently upgraded a machine here from 2.2-BETA (as of 961226) to 2.2-970801-RELENG. This broke the detection of an ATAPI CDROM on wdc1. Further checking (by adding kernel printf's to sys/i386/isa/wd.c) showed that the problem is in wdprobe(). If I add a printf just before line 340 of wd.c (version 1.119.2.6): printf("XXX %s%d get errstatus\n", dvp->id_driver->name, unit); du->dk_error = inb(du->dk_port + wd_error); the CDROM is detected just fine. If I revert to the original wd.c, the CDROM is not detected. Obviously there's a timing issue here, and the printf adds enough of a delay that the detection works. However, as far as I can see both wdprobe and wdcommand (which is called just before my printf) are exactly the same in 2.2-BETA and 2.2-970801-RELENG. Any good ideas? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sun Aug 17 14:20:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA23245 for hackers-outgoing; Sun, 17 Aug 1997 14:20:53 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA23238 for ; Sun, 17 Aug 1997 14:20:49 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA22971 for hackers@FreeBSD.ORG; Sun, 17 Aug 1997 23:20:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id XAA06679; Sun, 17 Aug 1997 23:03:59 +0200 (MET DST) Message-ID: <19970817230359.JX15769@uriah.heep.sax.de> Date: Sun, 17 Aug 1997 23:03:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? References: <19970817141632.FT54182@uriah.heep.sax.de> <199708172040.WAA00331@sos.freebsd.dk> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: hackers@FreeBSD.ORG In-Reply-To: =?iso-8859-1?Q?=3C199708172040=2EWAA00331=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Aug_17=2C_1997_22=3A40=3A10_+0200?= Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Søren Schmidt wrote: > I wouldn't bet on that 80% factor, if somebody is going to rewrite the > base utils. For one this is a total waste of time (and maybe talent), > the other is that it will render us completely incompatible with the > rest of the BSD world. I think that nobody would be stupid enough to > willingly takeover that kind of maintenance burden... We've been there before, so this will be my last followup in this thread. (Please, don't redirect any future personal Cc's to me either, i'm getting sick of Cc's for lengthy threads i'm not interested in.) Go and read Net/2's whereis(1) code, and then decide which one is easier maintenable. (Sorry, the Net/2 code is `tainted', so you need a FreeBSD 1.x CD-ROM for it. This was another reason to use Perl for me, the structure is now so clearly different that nobody could claim a copyright violation, even though the user interface is basically the same. Don't count on the 4.4BSD-Lite version at all, it's totally crippled, compared to the historic one. I wouldn't have rewritten it at all otherwise.) Scripting languages are mainly used to _reduce_ the maintenance effort. Wonder why phk prefers Tcl for so many things? ;) > If I want useless bloat That's why i told about a required *justification* before somebody's going to rewrite something. Just a rewrite only, with (nearly) the same features, the same bad structure, etc. constitutes IMHO not a justification. Neither of my quoted examples falls into this. The question whether some particular developer perhaps doesn't `speak' some of the used languages himself might bias him, but this alone doesn't establish ``unmaintenable code''. I bet even CVSup is probably way easier to maintain for me now than it would have been written in C++, or (*shudder* :) in C. And i've got absolutely no experience in M3 right now. But i've got no doubts i could learn it if necessary... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 14:55:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26257 for hackers-outgoing; Sun, 17 Aug 1997 14:55:44 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA26251 for ; Sun, 17 Aug 1997 14:55:41 -0700 (PDT) Received: from bonn-online.com (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id XAA32183 for ; Sun, 17 Aug 1997 23:55:27 +0200 Message-ID: <33F772D4.FB1AB014@bonn-online.com> Date: Sun, 17 Aug 1997 23:53:25 +0200 From: Sebastian Lederer X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: NFS locking Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, first the good news: I have successfully locked a file on a FreeBSD nfs server from a Solaris 2.5.1 nfs client. But that's about all right now. There are still pieces missing in the kernel and in the rpc.lockd, concering the server side. The client side of the nfs locking protocoll is yet another different story. Please see my other posting regarding the design of the rpc.lockd. There are still many unanswered questions there... But now I would like you to take a look the kernel code I've written to convert the nfs file handle to an open file. It seems to work, but since it is the very first kernel code I have ever done, I don't want to take chances (like leaking vnodes or memory). I have placed the whole thing as a subfunction of the nfssvc system call (I *know* Terry will love this), mainly because it depends on the nfs server anyway, and because it was convenient to do so (requires only 3 small patches). The new function: -- int nfssvc(NFSSVC_CNVT,struct nfs_cnvt_args *); struct nfs_cnvt_args { fhandle_t fh; /* The file handle */ struct sockaddr addr; /* Client's IP address*/ int authflag; /* Use Kerberos ? */ struct ucred cred; /* user credentials */ int exclusive; /* access mode 0=shared, 1=exclusive */ }; #define NFSSVC_CNVT 0x800 --- It returns -1 on error, and the open file descriptor on success. Strictly speaking, it does not work on nfs file handles, but on fhandle_t objects. The conversion to fhandle_t is done inside the rpc.lockd (this is just a cast for NFS Version 2). Here is the kernel code that does all the work (appended to nfs/nfs_subs.c): ------------------------------------------------------ int nfsrv_open_fh(struct proc *p, fhandle_t *fh, struct sockaddr *addr, int kerbflag, struct ucred *mycred, int exclusive, int *result_fd) { struct nfssvc_sock slp; struct vnode *vp; struct mbuf nam; /* struct filedesc *fdp = p->p_fd; */ struct file *f; int readonly; int error; int fd; int accessflags; bzero(&slp,sizeof(slp)); /* not used in nfsrv_fhtovp (?) */ bzero(&nam,sizeof(nam)); /* Put the sockaddr into the mbuf */ nam.m_data=(void *) addr; nam.m_len=addr->sa_len; /* Turn fhandle_t into locked vnode */ error=nfsrv_fhtovp(fh,TRUE,&vp,mycred,&slp,&nam,&readonly,kerbflag); if(error) { return error; } VREF(vp); /* Check permissions (mycred possibly modified by nfsrv_fhtovp) */ /* Must have read access for shared lock, write access for exclusive lock */ /* Check for read-only exports */ if(exclusive && readonly) { vput(vp); return EROFS; } accessflags = exclusive ? VREAD | VWRITE : VREAD; error = VOP_ACCESS(vp,accessflags,mycred,p); if(error) { vput(vp); return error; } /* allocate a new fd */ error=falloc(p,&f,&fd); if(error) { vput(vp); return error; } /* Tie the vnode to the fd */ f->f_flag = exclusive ? FREAD | FWRITE : FREAD; f->f_type = DTYPE_VNODE; f->f_ops = &vnops; f->f_data = (caddr_t) vp; VOP_UNLOCK(vp,0,p); *result_fd=fd; return 0; } ------------------------------------------------ There is also a diff to nfs/nfs_syscalls.c: -- *** nfs.orig/nfs_syscalls.c Wed Aug 13 13:20:47 1997 --- nfs/nfs_syscalls.c Fri Aug 15 09:54:19 1997 *************** *** 163,169 **** #endif /* NFS_NOSERVER */ /* ! * Nfs server psuedo system call for the nfsd's * Based on the flag value it either: * - adds a socket to the selection list * - remains in the kernel as an nfsd --- 163,169 ---- #endif /* NFS_NOSERVER */ /* ! * Nfs server pseudo system call for the nfsd's * Based on the flag value it either: * - adds a socket to the selection list * - remains in the kernel as an nfsd *************** *** 211,216 **** --- 211,235 ---- else error = ENXIO; #else /* !NFS_NOSERVER */ + else if (uap->flag & NFSSVC_CNVT) + { + struct nfs_cnvt_args cnvt_args; + + error = copyin(uap->argp, (caddr_t) &cnvt_args, + sizeof(cnvt_args)); + if(error) + return(error); + + error = nfsrv_open_fh(p,&cnvt_args.fh,&cnvt_args.addr, + cnvt_args.authflag, + &cnvt_args.cred, + cnvt_args.exclusive, + retval); + + return error; + } + + else if (uap->flag & NFSSVC_MNTD) { error = copyin(uap->argp, (caddr_t)&ncd, sizeof (ncd)); if (error) -- That's it. Any comments welcome. Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Sun Aug 17 14:58:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26518 for hackers-outgoing; Sun, 17 Aug 1997 14:58:43 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA26509 for ; Sun, 17 Aug 1997 14:58:37 -0700 (PDT) Received: from bonn-online.com (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id XAA32198 for ; Sun, 17 Aug 1997 23:58:25 +0200 Message-ID: <33F77387.B250B404@bonn-online.com> Date: Sun, 17 Aug 1997 23:56:23 +0200 From: Sebastian Lederer X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: NFS locking/rpc.lockd Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi , first of all, the current status of the rpc.lockd is that it does not really work at all. It can process some (nonblocking) locking requests, but only in a very preliminary manner. However, the basic steps are present (translating the nfs file handle and then setting/clearing the lock). Also, when there will be working version, it won't support NFS v3 or Kerberos authentication. These may be supported later. Some problems which need to be solved: * implementation of the F_RSETLK/F_RGETLK fcntl functions - not difficult, already done by Terry Lambert * blocking locks - F_SETLKW cannot be used, since the rpc.lockd must continue servicing rpc requests. It cannot fork, because it must own the fds itself. Busy wait/polling? * managing the lock state - the rpc.lockd must track all active locks so that it can undo a locking operation in some extreme cases, to know when it can safely close a file descriptor, and to cope with retransmitted locking requests. Also not difficult, but probably a lot of design issues hidden here. Your comments are welcome. I would like to have a (generally accepted) overall design set up before I really start to write code, so let me hear what you think. BTW, if anybody wants to test the current rpc.lockd version (especially with other Unixes than Solaris 2.5), I'll provide patches and some small testing programs. Best regards, Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Sun Aug 17 15:32:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28997 for hackers-outgoing; Sun, 17 Aug 1997 15:32:06 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28960; Sun, 17 Aug 1997 15:31:56 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id IAA05593; Mon, 18 Aug 1997 08:30:56 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id IAA08661; Mon, 18 Aug 1997 08:00:55 +0930 (CST) Message-ID: <19970818080055.00098@lemis.com> Date: Mon, 18 Aug 1997 08:00:55 +0930 From: Greg Lehey To: Michael Smith Cc: Poul-Henning Kamp , Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Parallel port developpements - ppbus References: <9306.871716052@critter.dk.tfs.com> <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708171539.BAA06417@genesis.atrad.adelaide.edu.au>; from Michael Smith on Mon, Aug 18, 1997 at 01:09:14AM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 01:09:14AM +0930, Michael Smith wrote: > Poul-Henning Kamp stands accused of saying: >> > >> >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >> >done with your help... >> >> Come on guys... PLIP is so simple as it can be... I don't have the time >> at this point to go back and kick PLIP again... > > If it's really that simple; where can I find some documentation on > it? Would you believe lp(4)? It's one of the best interface man pages in the section. > Is there a Linux mini-hownotto or something that spells it out in > terms a poor simple brain like mine could handle? I don't really understand. What is missing in the man page. > Is it likely to work on a port that's open to shared use? Of course! In fact, you can print and transfer data at the same time :-) Greg From owner-freebsd-hackers Sun Aug 17 16:25:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA03028 for hackers-outgoing; Sun, 17 Aug 1997 16:25:00 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA03018 for ; Sun, 17 Aug 1997 16:24:50 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id IAA07953; Mon, 18 Aug 1997 08:52:27 +0930 (CST) From: Michael Smith Message-Id: <199708172322.IAA07953@genesis.atrad.adelaide.edu.au> Subject: Re: reset screen hardware? In-Reply-To: <199708171933.MAA07196@phaeton.artisoft.com> from Terry Lambert at "Aug 17, 97 12:33:21 pm" To: terry@lambert.org (Terry Lambert) Date: Mon, 18 Aug 1997 08:52:27 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, grog@lemis.com, sos@sos.freebsd.dk, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > 3. How to we implement it? Ah, there's the rub. I still think it > > > belongs in the probe routines when the system starts up, but on > > > the other hand I agree with S=F8ren that kernel bloat is Bad. > > > > Call the BIOS on the video card. See above. > > This won't necessarily result in the card going from some arbitrary > state to some known state, unless the BIOS was used to get the card > into that state in the first place. Heh. Unless you call the reset entry vector. 8) > If a BIOS-based approach is used, it will seriously limit the > available modes for normal console operation and for X servers; > this is probably an unacceptable consequence. I don't think that any solution that made this imposition would be acceptable, although many Linuxers have lived with it for years. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 17:16:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA05738 for hackers-outgoing; Sun, 17 Aug 1997 17:16:56 -0700 (PDT) Received: from pineapple.theshop.net (pineapple.theshop.net [208.128.7.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05733 for ; Sun, 17 Aug 1997 17:16:51 -0700 (PDT) Received: from kd5ob.theshop.net ([208.128.7.71]) by pineapple.theshop.net (Netscape Mail Server v1.1) with SMTP id AAA8046 for ; Sun, 17 Aug 1997 18:47:47 -0500 Message-ID: <33F78D7E.2610@theshop.net> Date: Sun, 17 Aug 1997 18:47:10 -0500 From: "Charles Ebert" Reply-To: kd5ob@theshop.net X-Mailer: Mozilla 3.0Gold (Win95; U) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: The low priority items Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm a little slow. Did I read correctly that Threaded processes are not supported? And the next line down from that mentioned something of the same, however, can I assume it is to deal with multiprocessor CPU boards as well? I can understand the rush to invent new drives and support three channel scsi cards and all that. I was always told of UNIX's unique ability to run multiple processor systems. I never imagined that this system would have a problem with threading. I was hoping that the multiple processor issue would have a higher priority than it does. I'm a commercial windows programmer. I also work on OS2. Seems like this environment is similar to OS2 in the aspect that OS2 for the most part relys on one processor. Yet OS2 has support for threading 5,000 some odd tasks and do it with 255 seperate sessions. >From what I've read this Free BSD seems to support multiple sessions. Yet I also read something about DLL's being supported, but I guess you can't thread anything. As the system piles up, wouldn't it be more and more difficult to achieve these goals? I'm very tempted to help but the only working PC I have right now is this toshiba portable. Perhaps I will get into this next year as I plan on building another machine. You have caught my eye with all this. I just love messes. Love resolving them, working on them. You can only play so many card games you know. -- Charlie From owner-freebsd-hackers Sun Aug 17 17:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA07175 for hackers-outgoing; Sun, 17 Aug 1997 17:35:22 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07154 for ; Sun, 17 Aug 1997 17:35:15 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id TAA01240; Sun, 17 Aug 1997 19:13:55 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id TAA27678; Sun, 17 Aug 1997 19:14:11 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Sun, 17 Aug 1997 19:14:10 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca To: Søren Schmidt cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: <199708172040.WAA00331@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id RAA07171 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Søren Schmidt wrote: [re: make the world with perls] > base utils. For one this is a total waste of time (and maybe talent), Of course, perhaps the holder of this time & talent has no interest in doing anything "better". :-) > the other is that it will render us completely incompatible with the > rest of the BSD world. I think that nobody would be stupid enough to > willingly takeover that kind of maintenance burden... No, since presumably we will gain such huge advantages by rewriting everything in perl that the rest of the BSD world will have little choice but to adopt our version. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Sun Aug 17 18:17:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA09229 for hackers-outgoing; Sun, 17 Aug 1997 18:17:58 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA09211 for ; Sun, 17 Aug 1997 18:17:49 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x0GQH-0007PO-00; Sun, 17 Aug 1997 18:15:57 -0700 Date: Sun, 17 Aug 1997 18:15:56 -0700 (PDT) From: Tom Samplonius To: Charles Ebert cc: freebsd-hackers@freebsd.org Subject: Re: The low priority items In-Reply-To: <33F78D7E.2610@theshop.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Charles Ebert wrote: > I'm a little slow. Did I read correctly that Threaded processes are > not supported? And the next line down from that mentioned something > of the same, however, can I assume it is to deal with multiprocessor > CPU boards as well? > > I can understand the rush to invent new drives and support three > channel scsi cards and all that. > > I was always told of UNIX's unique ability to run multiple processor > systems. I never imagined that this system would have a problem with > threading. I was hoping that the multiple processor issue would > have a higher priority than it does. You are making some interesting relationships between multiple threads and multiple CPUs. Do you know the difference between a process and a thread? User mode threads are supported. Kernel threads are not. > -- > Charlie > > Tom From owner-freebsd-hackers Sun Aug 17 18:23:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA09474 for hackers-outgoing; Sun, 17 Aug 1997 18:23:10 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA09457; Sun, 17 Aug 1997 18:23:01 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA08379; Mon, 18 Aug 1997 10:52:35 +0930 (CST) From: Michael Smith Message-Id: <199708180122.KAA08379@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <19970818080055.00098@lemis.com> from Greg Lehey at "Aug 18, 97 08:00:55 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 18 Aug 1997 10:52:34 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: > >> > >> Come on guys... PLIP is so simple as it can be... I don't have the time > >> at this point to go back and kick PLIP again... > > > > If it's really that simple; where can I find some documentation on > > it? > > Would you believe lp(4)? It's one of the best interface man pages in > the section. Eep, frightening. > > Is it likely to work on a port that's open to shared use? > > Of course! In fact, you can print and transfer data at the same time :-) Really? From lp(4) : Initially, the lpt device is active for printing and the network inter- face is inactive; however, once the corresponding lp device has been con- figured 'up' with ifconfig(8) printing is disabled until the network in- terface is configured 'down'. That's OK though; in this case I merely needed to know whether the if_lp driver should obtain an exclusive lock on the port hardware. It'll let you tie yourself in some interesting knots, of course 8) > Greg -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 18:36:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA10335 for hackers-outgoing; Sun, 17 Aug 1997 18:36:19 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA10321 for ; Sun, 17 Aug 1997 18:36:11 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA08486 for hackers@freebsd.org; Mon, 18 Aug 1997 11:05:38 +0930 (CST) From: Michael Smith Message-Id: <199708180135.LAA08486@genesis.atrad.adelaide.edu.au> Subject: isa_dmastop... (fwd) To: hackers@freebsd.org Date: Mon, 18 Aug 1997 11:05:37 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, to avoid any further agony about ISA DMA, here's a request I've had just recently from Luigi. This looks OK to me, but again it contains the sanity checking that Amancio was unhappy about; folks, how do you feel? ----- Forwarded message from Luigi Rizzo ----- >From luigi@labinfo.iet.unipi.it Sat Aug 9 23:27:10 1997 From: Luigi Rizzo Message-Id: <199708091246.OAA01564@labinfo.iet.unipi.it> Subject: isa_dmastop... To: msmith@gsoft.com.au Date: Sat, 9 Aug 1997 14:46:19 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text For the sound driver to implement pause/abort, the following function is useful (one can do things without it if tolerates some "channel busy" messages from the kernel...) If you like it, can you commit to isa.c ? Thanks Luigi /* * this stops the dma channel and returns the residual count * derived calling isa_dmastatus */ int isa_dmastop(int chan) { if (dma_inuse & (1 << chan) == 0) printf("isa_dmastop: channel %d not acquired\n", chan); if (dma_busy & (1 << chan) == 0) printf("isa_dmastop: channel %d not acquired\n", chan); if ((chan & 4) == 0) outb(DMA1_SMSK, (chan & 3) | 4 /* disable mask */); else outb(DMA2_SMSK, (chan & 3) | 4 /* disable mask */); return isa_dmastatus(chan); } ----- End of forwarded message from Luigi Rizzo ----- -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Aug 17 18:48:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA10958 for hackers-outgoing; Sun, 17 Aug 1997 18:48:21 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA10952 for ; Sun, 17 Aug 1997 18:48:17 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id UAA00359; Sun, 17 Aug 1997 20:48:12 -0500 (EST) From: "John S. Dyson" Message-Id: <199708180148.UAA00359@dyson.iquest.net> Subject: Re: The low priority items In-Reply-To: <33F78D7E.2610@theshop.net> from Charles Ebert at "Aug 17, 97 06:47:10 pm" To: kd5ob@theshop.net Date: Sun, 17 Aug 1997 20:48:12 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > I'm a little slow. Did I read correctly that Threaded processes are > not supported? And the next line down from that mentioned something > of the same, however, can I assume it is to deal with multiprocessor > CPU boards as well? > Threaded processes are not "supported" yet, but code exists in the -current FreeBSD kernel. I am one of the people creating that support. We do have a pthread(s) library, but that doesn't take advantage of SMP (yet.) > channel scsi cards and all that. > > I was always told of UNIX's unique ability to run multiple processor > systems. I never imagined that this system would have a problem with > threading. I was hoping that the multiple processor issue would > have a higher priority than it does. > There aren't any problems. Different OSes have different advantages and disadvantages. For example, you can create an entirely new process on FreeBSD in a few hundred microseconds. A kernel-based thread can be created in several ten's of microseconds. Creating new processes on NT (or many commercial versions of U**X) is/are much much slower. The multiple processor support is a pretty much fully funded effort, and user-land code (like compiles) already sees a significant performance improvement on SMP machines, when running the -current kernel. When we "support" an SMP release, it will be very very good. I am also working on the SMP team. John From owner-freebsd-hackers Sun Aug 17 18:50:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA11190 for hackers-outgoing; Sun, 17 Aug 1997 18:50:40 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA11185 for ; Sun, 17 Aug 1997 18:50:37 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA27967; Sun, 17 Aug 1997 21:50:05 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun, 17 Aug 1997 21:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id PAA07278; Sun, 17 Aug 1997 15:20:10 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id PAA02003; Sun, 17 Aug 1997 15:13:25 -0400 (EDT) Date: Sun, 17 Aug 1997 15:13:25 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708171913.PAA02003@lakes.dignus.com> To: ponds!root.com!dg, ponds!lambert.org!terry Subject: Re: More info on slow "rm" times with 2.2.1+. Cc: ponds!FreeBSD.ORG!hackers, ponds!lakes.dignus.com!rivers Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes > > > > It would be trivial for me to verify any slow or fast times - all > > >I've got to do is make a big directory... seems that ~300 files is > > >enough to run into whatever the problem may be... > > > > How many files are in the directory isn't important. What is important is > > the size of the directory. You can have a 20MB directory and yet have only a > > 100 files in it. There is code to free up unused space in directories, but > > it only works if the free space is at the end. If the directory is large, > > then it will take a large amount of time to search through it. > > Specifically, if I have a directory with 20,000 entries, and I average > 32 entries per block ((512/32) - 8 bytes entry data per 4-7 byte name), > then I am using 625 blocks. > > The opendir/readdir library routines operate by calling getdents() > once per block to refill the user space "snapshot" of a directory > block, on a block by block basis. That is, I call opendir and it > calls getdents() and grabs the first 32 entries. I call readdir > and move forward unitil I've returned all 32, and then call getdents() > again. > > Now you are linearly traversing the directory forward (using getdents()) > to do this. > > Say you want to remove all entries. You delete the first entry > (ignore the vagries of "." and ".." for a second). This modifies > the first directory block. > > Now you get halfway through. > > You must linearly traverse 312 directory blocks in the lookup for the > entry you are going to delete. > > Now you are 3/4 of the way thorugh. > > You must linearly traverse 466 directory blocks in the lookup for the > entry you are going to delete. > > In other words, your traversal is going to increase exponentially > with a slope equalt to a square exponential progreassion divided > by 32 (or whatever your average number of entries per block is, > given your average file name length). > > Deleteing the last entries are going to take the longest of all. > > There were some additional things added into the unlink path in > respect for the lease code, and there were some additional things > added into the getdents path in support of NFSv3. And there is > a *lot* of additional function call and contention overhead from > the BSD4.4-Lite2 locking code, which is upside down (IMO, anyway). > > So yes, it's slower than it was, but no, it wasn't fast before; it > had the same problems. > ... Ok - I can buy that - the last block will take longest to delete (since you have to skip over the previous, un-coalesced, entries...) But - I'm not sure that explains why deleting the last 300 files would have (3*300) 900 seconds with 2.2.1 in this situation, where it only took 2.1.7 3 seconds. Just from listening to the disk and watching I/O I can see that 2.2.1 is doing an *awful* lot of I/O 2.1.7 didn't do... could there be something in this locking? - Dave R. - From owner-freebsd-hackers Sun Aug 17 18:50:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA11235 for hackers-outgoing; Sun, 17 Aug 1997 18:50:48 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA11199 for ; Sun, 17 Aug 1997 18:50:41 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AB28045; Sun, 17 Aug 1997 21:50:07 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun, 17 Aug 1997 21:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id PAA07357; Sun, 17 Aug 1997 15:24:44 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id PAA02042; Sun, 17 Aug 1997 15:17:59 -0400 (EDT) Date: Sun, 17 Aug 1997 15:17:59 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708171917.PAA02042@lakes.dignus.com> To: ponds!sunyit.edu!perlsta, ponds!lakes.dignus.com!rivers Subject: Re: More info on slow "rm" times with 2.2.1+. Cc: ponds!freefall.cdrom.com!freebsd-hackers Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This is a sure sign of a failing disk. > if the disk makes a lot of whirring noises that fade in and out (listen to > it with the cover off) or a grinding kind of noise then youi are in > trouble, use the disk checking program to tet the the disk itr's called > "bad_144" i think... Ummm... I didn't mean to give that impression; the sounds definately sound like "real" I/O (i.e. twiddling, not whirring/grinding). And the case is hardly ever closed :-) It's a relatively new disk and hasn't given me any troubles in the past... But - I'll keep an eye out for something like that happening... - Thanks! - - Dave R. - > > ._________________________________________ __ _ > |Alfred Perlstein - Programming & SysAdmin for hire... > |perlsta@sunyit.edu > |http://www.cs.sunyit.edu/~perlsta > : ---"Have you seen my FreeBSD tatoo?" > ' ---"who was that masked admin?" > > On Thu, 14 Aug 1997, Thomas David Rivers wrote: > > > > > Ok - > > > > I've (at last) replaced the 8meg 386 with a 24meg 486dx2-66. > > > > So, I expected to be able to simply mount that same file system, > > and quickly remove the files in /usr/spool/news/control. > > > > However - things are not going any faster... > > > > I have determined that it's not the argument processing; I can > > simply pick a single file to remove; issue: > > > > rm file > > > > and it takes upwards of 3 to 5 seconds and a *slew* of disk > > activity to accomplish the task... (recall, this is a miserable > > little IDE drive as well.. the 'rm' spends a lot of its time > > in biowait.) > > > > What I'm looking at now is a directory full of about 20,000 files, > > each of which is around 1024 bytes... (should be readily reproducible.) > > Then, simply pick a file to remove & wait... > > > > It appears to me that the remove is rewritting the entire directory > > structure (probably spanning more than one inode, since the file names > > are 7 bytes each - 20,000 * 7 is a few bytes :-) :-) > > > > Is this the case - and if so, is my achingly slow IDE I/O the real > > cause of the bottleneck in getting this data rewritten, or has something > > else happened in this area in 2.2.x? > > > > - Thanks - > > - Dave Rivers - > > > > p.s. We'll see what this 486 does to the "daily panics" when I can > > get news running again... > > > > From owner-freebsd-hackers Sun Aug 17 19:03:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA12030 for hackers-outgoing; Sun, 17 Aug 1997 19:03:06 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11997 for ; Sun, 17 Aug 1997 19:02:58 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA19951; Sun, 17 Aug 1997 19:04:26 -0700 (PDT) Message-Id: <199708180204.TAA19951@implode.root.com> To: Thomas David Rivers cc: freebsd-hackers@freebsd.org Subject: Re: "rm" speeds (2.1.7.1 vs. 2.2.1) In-reply-to: Your message of "Sun, 17 Aug 1997 21:12:38 EDT." <199708180112.VAA03041@lakes.dignus.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 17 Aug 1997 19:04:25 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Again, f.y.i. - this is a 486dx66 with 24meg of RAM, a typical IDE >drive (1+gig)... The 2.2.1 kernel has NBUF defined at 128; to see >if that's the problem... where the 2.1.7 kernel was from the boot floppy >off of a 2.1.7 CDROM. That is the problem. Take out the NBUF= thing from your kernel config file and rebuild/install the kernel. A system with 24MB of RAM will have about 600 buffers if it is allowed to dynamically calculate the amount. What's happening is that the directory is getting pushed out of the cache, forcing the system to re-read much of it and the inode blocks each time. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Aug 17 19:12:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA12520 for hackers-outgoing; Sun, 17 Aug 1997 19:12:14 -0700 (PDT) Received: from thelab.hub.org (root@hal-ns1-45.netcom.ca [207.181.94.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA12515 for ; Sun, 17 Aug 1997 19:12:09 -0700 (PDT) Received: from thelab.hub.org (scrappy@LOCALHOST [127.0.0.1]) by thelab.hub.org (8.8.6/8.8.2) with ESMTP id XAA27699 for ; Sun, 17 Aug 1997 23:12:06 -0300 (ADT) X-Received: from hub.org (scrappy@LOCALHOST [127.0.0.1]) by thelab.hub.org (8.8.6/8.8.2) with ESMTP id XAA27645 for ; Sun, 17 Aug 1997 23:01:39 -0300 (ADT) X-Received: from hub.org (hub.org [207.107.138.200]) by hub.org (8.8.5/8.7.5) with ESMTP id VAA14526; Sun, 17 Aug 1997 21:45:28 -0400 (EDT) X-Received: by hub.org (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32)); Sun, 17 Aug 1997 21:42:36 -0400 (EDT) X-Received: (from majordom@localhost) by hub.org (8.8.5/8.7.5) id VAA09701 for pgsql-hackers-outgoing; Sun, 17 Aug 1997 21:42:32 -0400 (EDT) X-Received: from thelab.hub.org (root@hal-ns1-45.netcom.ca [207.181.94.109]) by hub.org (8.8.5/8.7.5) with ESMTP id VAA09655 for ; Sun, 17 Aug 1997 21:42:26 -0400 (EDT) X-Received: from thelab.hub.org (scrappy@LOCALHOST [127.0.0.1]) by thelab.hub.org (8.8.6/8.8.2) with SMTP id WAA27553 for ; Sun, 17 Aug 1997 22:42:16 -0300 (ADT) Date: Sun, 17 Aug 1997 22:42:16 -0300 (ADT) From: The Hermit Hacker To: hackers@postgreSQL.org Subject: [HACKERS] innd remalloc failure *after* setting MEMDSIZ Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ReSent-Date: Sun, 17 Aug 1997 23:11:59 -0300 (ADT) ReSent-From: The Hermit Hacker ReSent-To: hackers@freebsd.org ReSent-Message-ID: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... After going through "the archives", and finding the suggestion of increasing MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still getting the remalloc 'crash' with innd. The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at the beginning of ~news/etc/rc.news... Can anyone think of something else to try, in order to fix this? My machine is a P166, with 128Meg of RAM, and 430Meg of SWAP...is datasize the only thing that would affect this particular problem? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Sun Aug 17 19:23:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA13053 for hackers-outgoing; Sun, 17 Aug 1997 19:23:11 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA13027 for ; Sun, 17 Aug 1997 19:22:29 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id VAA14571; Sun, 17 Aug 1997 21:38:21 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id VAA18602; Sun, 17 Aug 1997 21:38:36 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Sun, 17 Aug 1997 21:38:35 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Charles Ebert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The low priority items In-Reply-To: <33F78D7E.2610@theshop.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Charles Ebert wrote: > I'm a little slow. Did I read correctly that Threaded processes are > not supported? And the next line down from that mentioned something > of the same, however, can I assume it is to deal with multiprocessor > CPU boards as well? man 3 pthread Current thread support isn't optimal, and there are multiple threading packages to choose from (threads aren't implemented at the kernel level), but it's there, and it's used. :) > I was always told of UNIX's unique ability to run multiple processor > systems. I never imagined that this system would have a problem with > threading. I was hoping that the multiple processor issue would > have a higher priority than it does. Theading really isn't an incredible technological advantage. The unique ability of UNIX that you're probably thinking of is to run "multiple processes", not "multiple processors". Multiple processes is, of course, no longer unique to UNIX (never was, actually), but it is one of the things that set UNIX away from DOS. Windows programmers often see threads as an absolute necessity because of the Windows history. UNIX programmers use and generally prefer fork(), but it's recognized that threads have their purpose (which is why they're supported :). fork(2) manpage should contain a .xref to rfork(2), in case you decide to check any manpages... :) > I'm a commercial windows programmer. I also work on OS2. > Seems like this environment is similar to OS2 in the aspect that > OS2 for the most part relys on one processor. Yet OS2 has support > for threading 5,000 some odd tasks and do it with 255 seperate > sessions. FreeBSD can do the same thing on one processor without using threads. :) > >From what I've read this Free BSD seems to support multiple sessions. > Yet I also read something about DLL's being supported, but I guess > you can't thread anything. Shared libraries (ie. dynamically linked) are supported and (usually) used, yes. By multiple sessions, you mean being logged-into the system more than once? I'm sometimes simultaneously logged into my machine 15 times. Plus the occasional non-FreeBSD user connected from the 'net so I can demonstrate fortune(1) (or whatever) for them. :) > Perhaps I will get into this next year as I plan on building another > machine. You have caught my eye with all this. That's good. :) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Sun Aug 17 19:34:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA13792 for hackers-outgoing; Sun, 17 Aug 1997 19:34:40 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA13785 for ; Sun, 17 Aug 1997 19:34:34 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA28157; Sun, 17 Aug 1997 21:50:11 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun, 17 Aug 1997 21:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id VAA00310; Sun, 17 Aug 1997 21:58:15 -0400 (EDT) Received: (from root@localhost) by lakes.dignus.com (8.8.5/8.6.9) id VAA03041; Sun, 17 Aug 1997 21:12:38 -0400 (EDT) Date: Sun, 17 Aug 1997 21:12:38 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708180112.VAA03041@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.dignus.com!rivers Subject: "rm" speeds (2.1.7.1 vs. 2.2.1) Cc: ponds!root.com!dg Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I've been spending the afternoon verifying my findings on 2.1.7.1 "rm times" vs. 2.2.1 "rm times." Here's what I've done so far: 1) I have another large directory (well, it's the same one, "control" from my news spool - 1061888 bytes of directory space with 42881 entries.. 2) I tar'd that up and copied it to another directory, to determine just how many "empty" entries there were in the directory. About 1/2 of them are empty. (that is, the directory size when everything is untarr'd is about 1/2 the original size.) 3) I booted 2.1.7 and used the "fixit" floppy to remove some files. I noticed that the disk activity was rapid, and the files were deleted fairly quickly. About 10,000 files took less than 5 minutes (wall time.) I was trying removing files that occur later in the directory; so as to incur the delay associated with skipping most of the entries. "Later" was by timestamp, which may not actually be later in the entry list, perhaps I should have done this by inode. 4) I booted 2.2.1, into single user mode to avoid any potential issue there - the directory size was unchanged, so no coalescing of directory entries had occured when I deleted files using 2.1.7. Using the same directory with the remaining files; I attempted to delete about the same number of files; starting toward the beginning of the directory (by time stamp) to give 2.2.1 "an edge." The disk activity has a markedly different pattern - much more bursty, as if each delete is causing a flush of some kind. After 45 minutes of trying to delete ~10,000 files - I gave up. 5) I then rebooted 2.1.7 and tried to delete the same ~10,000 files (which I presume is somewhat less than 10,000 - but I didn't actually count them) - less than 5 minutes, they were gone. From this, I'm guessing that 2.2.1 is doing something different with the directory entries - causing a lot more I/O per deletion, which is a serious drag on performance. Does anyone have a notion about why 2.2.1 would be doing more I/O? Is it writing pieces of the directory back when 2.1.7 didn't? [By the way, these were all synchronous mounts - my previous experiments verified that mounting asynchronously with 2.2.1 didn't improve the unlink performance.] I did start looking into unlink() - it really hasn't changed for 2.2.1 (vs. 2.1.7), at least the code paths would be the same. I also tried running the 2.1.7 "rm" command on 2.2.1 (the one from /stand on the 2.1.7 boot floppy) to ensure that the "rm" command hadn't somehow changed - I got the same less-than-stellar performance. Again, f.y.i. - this is a 486dx66 with 24meg of RAM, a typical IDE drive (1+gig)... The 2.2.1 kernel has NBUF defined at 128; to see if that's the problem... where the 2.1.7 kernel was from the boot floppy off of a 2.1.7 CDROM. - Opinions? - - Dave Rivers - From owner-freebsd-hackers Sun Aug 17 19:49:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA14817 for hackers-outgoing; Sun, 17 Aug 1997 19:49:18 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA14810 for ; Sun, 17 Aug 1997 19:49:15 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id TAA02547; Sun, 17 Aug 1997 19:48:54 -0700 (PDT) Message-Id: <199708180248.TAA02547@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Michael Smith cc: hackers@FreeBSD.ORG Subject: Re: isa_dmastop... (fwd) In-reply-to: Your message of "Mon, 18 Aug 1997 11:05:37 +0930." <199708180135.LAA08486@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 1997 19:48:53 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk My first reaction. I am not too keen on having printfs in the dma handling routines. The routine should return an error code. > if (dma_inuse & (1 << chan) == 0) > printf("isa_dmastop: channel %d not acquired\n", chan); This condition can be met easily by calling isa_dma_acquire;however, the printf is *not* a good idea. --- > if (dma_busy & (1 << chan) == 0) > printf("isa_dmastop: channel %d not acquired\n", chan); Same thing with respect to the printf. Now with respect to the sound driver and the use of auto dma, it appears to me that once we start doing auto dma the busy flag gets on the way because we don't clear the busy flag by calling isa_dmadone. For auto dma , isa_dmastart gets called once which right now it sets the busy flag however since I don't call isa_dmastart again to initiate a dma transfer I don't see the point of calling isa_dmadone . Currently, the sound drivers allocate memory below the 16MB memory region so we dont use bounce buffers. If you want to keep the sanity checks then I suggest that you bracket at least the busy flag check by way of checking to see if the channel is operating in auto dma mode and I will be more than happy to modify the guspnp driver to call isa_dma_acquire. So if the above strategy is applied to isa_dmastatus and to isa_dmastop we will all be a very happy family. Tnks, Amancio >From The Desk Of Michael Smith : > > Ok, to avoid any further agony about ISA DMA, here's a request I've had > just recently from Luigi. This looks OK to me, but again it contains the > sanity checking that Amancio was unhappy about; folks, how do you feel? > > ----- Forwarded message from Luigi Rizzo ----- > > >From luigi@labinfo.iet.unipi.it Sat Aug 9 23:27:10 1997 > From: Luigi Rizzo > Message-Id: <199708091246.OAA01564@labinfo.iet.unipi.it> > Subject: isa_dmastop... > To: msmith@gsoft.com.au > Date: Sat, 9 Aug 1997 14:46:19 +0200 (MET DST) > X-Mailer: ELM [version 2.4 PL23] > Content-Type: text > > For the sound driver to implement pause/abort, the following function > is useful (one can do things without it if tolerates some "channel > busy" messages from the kernel...) If you like it, can you commit to > isa.c ? > > Thanks > Luigi > /* > * this stops the dma channel and returns the residual count > * derived calling isa_dmastatus > */ > int isa_dmastop(int chan) > { > if (dma_inuse & (1 << chan) == 0) > printf("isa_dmastop: channel %d not acquired\n", chan); > if (dma_busy & (1 << chan) == 0) > printf("isa_dmastop: channel %d not acquired\n", chan); > if ((chan & 4) == 0) > outb(DMA1_SMSK, (chan & 3) | 4 /* disable mask */); > else > outb(DMA2_SMSK, (chan & 3) | 4 /* disable mask */); > return isa_dmastatus(chan); > } > > > ----- End of forwarded message from Luigi Rizzo ----- > > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > From owner-freebsd-hackers Sun Aug 17 20:02:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15583 for hackers-outgoing; Sun, 17 Aug 1997 20:02:16 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA15573 for ; Sun, 17 Aug 1997 20:02:12 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id MAA11682; Mon, 18 Aug 1997 12:59:48 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id MAA09982; Mon, 18 Aug 1997 12:29:41 +0930 (CST) Message-ID: <19970818122939.30413@lemis.com> Date: Mon, 18 Aug 1997 12:29:39 +0930 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <19970817163116.16698@lemis.com> <199708170951.LAA00412@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C199708170951=2ELAA00412=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Sun=2C_Aug_17=2C_1997_at_11=3A51=3A1?= =?iso-8859-1?Q?9AM_+0200?= Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id MAA09982 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA15576 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 17, 1997 at 11:51:19AM +0200, Søren Schmidt wrote: > In reply to Greg Lehey who wrote: >>> >>> Funny, my bigget rant has to do with people going "Why doesn't FreeBSD >>> have feature XXX?!" rather than "Here are my diffs to support feature >>> XXX, please integrate them." >> >> And would you? If I had come along with the diffs for doing it this >> way, you'd have said (with some justification) "Go away, we don't want >> all this crap in the kernel". I was, in fact, considering doing the >> implementation, but I see that it's not the way to go. > > Come on here, what at least I have been advocating for, is that > we need that functionality, but we need it done RIGHT. We allready > have so many kludges/hacks in the kernel, we don't need another one. I think you're missing the point. That's what I said. Note the "(with some justification)". > If Joe random hacker cannot graps the bigger picture, and get his > hacks in the right direction, well, I'm sorry it won't be commited. > On the other hand, if Joe mature hacker comes around, and wants to > help do the hard work along the guidelines that the responsible > person(s) have laid out (and belive me, for the most part things > has been thought long and seriously about), he will be welcommed > with open arms. Sure. No debate. > So to get concrete in this matter, we need: > > 1. Being able to call realmode code from the kernel. > > 2. Being able to run BIOS functions, that is we need to keep > track of the BIOS's workspace, most often in low memory. > > 3. Then write the code to call the right BIOS functions to > be able to talk to the video HW. > > So, if someone is SERIOUS about getting this to work, pick one > of the above, come back to me so we can get technical about > the details, and them submit the diffs. Then I'm certain it will > be committed, and the author will get his fair share of applause.. > > But gimme a break on just demanding XXX functionality, sometimes > with badly (if at all) designed hacks.... Wait a while, there was no design at all at this point. We had Mike saying that it wasn't possible, and me suggesting a possible approach. My statement was that the kernel probe routines seemed the obvious place to put such code. I stand by that statement. The question was how to find out the parameters, and the fact that the code is so voluminous makes the approach impractical. But that doesn't make the approach a hack. There is, BTW, a potential problem with the "call the BIOS" approach (which I consider marginally more of a hack, since the driver doesn't know what's going on): what if the driver has set a different mode for the board, like 50 line or some such? That would have to be redone after the BIOS call. Greg From owner-freebsd-hackers Sun Aug 17 20:06:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15818 for hackers-outgoing; Sun, 17 Aug 1997 20:06:21 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA15813 for ; Sun, 17 Aug 1997 20:06:19 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id VAA23890; Sun, 17 Aug 1997 21:06:04 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id VAA01395; Sun, 17 Aug 1997 21:05:41 -0600 (MDT) Date: Sun, 17 Aug 1997 21:05:41 -0600 (MDT) From: Marc Slemko To: The Hermit Hacker cc: hackers@FreeBSD.ORG Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, The Hermit Hacker wrote: > > Hi... > > After going through "the archives", and finding the suggestion of increasing > MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still getting > the remalloc 'crash' with innd. > > The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at the > beginning of ~news/etc/rc.news... What does a ulimit -a run from rc.news after your unlimit say? It should be MAXDSIZ; was the just a typo, or did you set the wrong thing? What does the inn log report? It seems like there may be some VM bogons in 2.2. I have times when innd is 40 megs, but 150 megs of swap is being used on the machine; if I flush a channel that frees 10 megs of memory, I go down to 20 megs of swap in use. I haven't looked into it too deeply since I did some changes to the channel buffer handling to keep the size of them down. I have had innd literally eat up 500 megs of VM while still showing as 40 megs in a ps. This may be related to changes made after 2.2.0. > > Can anyone think of something else to try, in order to fix this? > > My machine is a P166, with 128Meg of RAM, and 430Meg of SWAP...is datasize > the only thing that would affect this particular problem? Probably. From owner-freebsd-hackers Sun Aug 17 20:07:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15937 for hackers-outgoing; Sun, 17 Aug 1997 20:07:17 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA15925 for ; Sun, 17 Aug 1997 20:07:10 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x0I86-0007Sz-00; Sun, 17 Aug 1997 20:05:18 -0700 Date: Sun, 17 Aug 1997 20:05:18 -0700 (PDT) From: Tom Samplonius To: The Hermit Hacker cc: hackers@freebsd.org Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, The Hermit Hacker wrote: > Hi... > > After going through "the archives", and finding the suggestion of increasing > MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still getting > the remalloc 'crash' with innd. > > The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at the > beginning of ~news/etc/rc.news... 1.6b3 is supposed to be quite unstable... > Can anyone think of something else to try, in order to fix this? > > My machine is a P166, with 128Meg of RAM, and 430Meg of SWAP...is datasize > the only thing that would affect this particular problem? Perhaps there really is no memory left? Perhaps innd has a memory leak? How much swap do you have? And how big was innd before it died? And how much more memory did it want? > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > Tom From owner-freebsd-hackers Sun Aug 17 20:24:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA16767 for hackers-outgoing; Sun, 17 Aug 1997 20:24:05 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA16747 for ; Sun, 17 Aug 1997 20:24:00 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA11997; Mon, 18 Aug 1997 13:21:14 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id MAA10096; Mon, 18 Aug 1997 12:50:56 +0930 (CST) Message-ID: <19970818125054.52750@lemis.com> Date: Mon, 18 Aug 1997 12:50:55 +0930 From: Greg Lehey To: Michael Smith Cc: hackers@freebsd.org Subject: Re: reset screen hardware? References: <199708170311.MAA04998@freebie.lemis.com> <199708171009.TAA04212@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708171009.TAA04212@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Aug 17, 1997 at 07:39:40PM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 17, 1997 at 07:39:40PM +0930, Michael Smith wrote: > Greg Lehey stands accused of saying: >>>> >>>> How about a more positive approach? I know plenty of people who'll >>>> tell me in vivid detail why things won't work. >>> >>> This is like asking for a positive approach to a VMS ABI emulation >>> module 8) >> >> Yes. If people want it. I didn't say it had to be nice. > > I'm not sure I can parse that. Can you give me a dump of the parse tree at the point where you abort? >> -- rant mode on -- >> >> If there's one thing that pisses me off about many FreeBSD hackers, >> it's this attitude "Ooh, this is nasty. I don't want to have anything >> to do with it". > > I don't see how this is relevant to the discussion at hand. What is > currently being said is "there is a tough problem. The proposed > solution sucks both from a practicality and a supportability point of > view. In addition, a more general and elegant solution is already > being implemented." Well, what I read was: Michael Smith writes: > Alfred Perlstein stands accused of saying: >> I'm not familiar with the protection mechanism in freebsd, if i wrote a >> program to reset the text screens by programming the ports what kind of >> skeleton code would it need? > > It wouldn't work. > That's not "this is nasty". You did in an earlier message, which unfortunately I didn't keep. >> Lots of PC hardware is nasty. Messing around in a 16 >> bit BIOS is nasty. IDE is nasty. VGA is nasty. Come to think of it, >> what's nice about PC hardware? But FreeBSD's acceptance suffers >> significantly because nobody can be bothered to deal with these nasty >> things. Where's the Win-32 emulator? ... > > There are two of them; both accumulating significant support and > offering usefully overlapping feature sets. Win-32 emulators? I didn't know that. I only knew about wine, and last time I looked it couldn't handle Win-32. I've just taken another look at the emulators ports, and I can't see a second one. > Note that neither of their development teams have the biollion-plus > development budget of the original. Yup, that makes you wonder. Why does it cost Microsoft so much to maintain this particular heap of crap? >>>>> We wont have hundreds of K's of code like that in kernel space. >>>> >>>> That's for sure. But who says it'll be hundreds of Ks? >>> >>> Have a look at the X server sources someday. >> >> Must I? I took a look at SuperProbe. The binary is 83 kB, and in the >> kernel some of that could go. Sure, that's too much for the kernel, >> too, but it's still not hundreds. > > Turn around, go back. SuperProbe != video chipset drivers. Sure, but we don't need a chipset driver here. All we need here is a way to recognize the chipset. Once you've done that, extracting the registers is relatively trivial (yes, I know, you'll come back again and say that there are tricks and things, but they can be overcome). >>> Basically, it is not possible to take a snapshot of the state of a >>> modern video adapter without uintimate knowledge of the hardware >>> involved. Such a snapshot is often useless anyway, as it does not >>> contain information about the state transitions prior to the snaphot >>> state, which may be very significant to the hardware's current mode of >>> operation. >> >> But we still have the evidence that every X server manages to reset >> them most of the time. > > That's _right_. But it achieves this by knowing, in fact having > _been_told_ in advance what the hardware is, and thus having > hardware-specific intelligence. The point is that this intelligence > is foreign to the kernel, I disagree. One of the stated purposes of any OS kernel is management of hardware resources. Currently, display boards are about the only exception. The main reason for the problem is that the kernel has not really accepted graphics cards, but that's not really acceptable. > unmaintainable in the kernel environment, and _inevitably_ will lag, > often indefinitely, behind hardware development. These problems apply equally to the X server. I suppose what we're getting to here is more a question of where to put the "platform" software in a system. Ideally, a user program should not be allowed to access hardware--that's the job of the kernel. On the other hand, the X server alone is bigger than the kernel, so just putting the whole thing in the kernel would be impossible. But why shouldn't it be an LKM? No, I'm not advocating doing this, but from a purely conceptual point of view, that's where it belongs. Greg From owner-freebsd-hackers Sun Aug 17 20:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA16898 for hackers-outgoing; Sun, 17 Aug 1997 20:26:17 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA16892 for ; Sun, 17 Aug 1997 20:26:11 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA12063; Mon, 18 Aug 1997 13:25:06 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id MAA10115; Mon, 18 Aug 1997 12:55:04 +0930 (CST) Message-ID: <19970818125502.35086@lemis.com> Date: Mon, 18 Aug 1997 12:55:02 +0930 From: Greg Lehey To: Terry Lambert Cc: Michael Smith , hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <199708171009.TAA04212@genesis.atrad.adelaide.edu.au> <199708171949.MAA07244@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708171949.MAA07244@phaeton.artisoft.com>; from Terry Lambert on Sun, Aug 17, 1997 at 12:49:09PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 17, 1997 at 12:49:09PM -0700, Terry Lambert wrote: >> That's _right_. But it achieves this by knowing, in fact having >> _been_told_ in advance what the hardware is, and thus having >> hardware-specific intelligence. The point is that this intelligence >> is foreign to the kernel, unmaintainable in the kernel environment, >> and _inevitably_ will lag, often indefinitely, behind hardware >> development. > > 1) Make X use the kernel driver. Period. This is necessary > whether the driver is card-specific, generic BIOS-based, > or generic VGA (and BIOS) based. > > 2) Default to a generic VGA driver. This is your fallback > position for "anything which works is better than anything > which doesn't". > > 3) If there is a card specific driver and you have the card, > load the LKM for it at boot time after the FS's are mounted > and the driver code can be located. Use the LKM driver in > place of the generic driver from then on. So far, so good. Pretty much my position... > 4) If you are running an ELF/OLF kernel, and the VM system > supports section attribution and section naming, discard > the "generic VGA" section after loading the LKM. > > 5) If you are running an ELF/OLF kernel, and you have a > section archiver available, you may (at your option), > take the generic kernel, dearchive the section(s) > containing the generic VGA driver, and replace them > with the section(s) for the card specific driver. > > 6) If you are running an ELF/OLF kernel, and you have a > section archiver available, you may "tune" the kernel > down to the point where it contains *only* drivers > for existing hardware and reasonably expected expansion > hardware. > > 7) ...ROM that kernel! (And other nifty things...). I think we need to sell them on the first three points first. Greg From owner-freebsd-hackers Sun Aug 17 20:36:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17506 for hackers-outgoing; Sun, 17 Aug 1997 20:36:30 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA17500 for ; Sun, 17 Aug 1997 20:36:25 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA12320; Mon, 18 Aug 1997 13:34:05 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id NAA10140; Mon, 18 Aug 1997 13:04:03 +0930 (CST) Message-ID: <19970818130402.63952@lemis.com> Date: Mon, 18 Aug 1997 13:04:02 +0930 From: Greg Lehey To: Terry Lambert Cc: Michael Smith , sos@sos.freebsd.dk, hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <199708170301.MAA03401@genesis.atrad.adelaide.edu.au> <199708171933.MAA07196@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.81e In-Reply-To: <199708171933.MAA07196@phaeton.artisoft.com>; from Terry Lambert on Sun, Aug 17, 1997 at 12:33:21PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id NAA10140 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA17502 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 17, 1997 at 12:33:21PM -0700, Terry Lambert wrote: >>>> We wont have hundreds of K's of code like that in kernel space. >>> >>> That's for sure. But who says it'll be hundreds of Ks? >> >> Have a look at the X server sources someday. > > But be sure to only look at the DDX code for the generic VGA, since > that's the only thing that will be there by default in any sane > design. Yup. >>> 3. How to we implement it? Ah, there's the rub. I still think it >>> belongs in the probe routines when the system starts up, but on >>> the other hand I agree with S=F8ren that kernel bloat is Bad. >> >> Call the BIOS on the video card. See above. > > This won't necessarily result in the card going from some arbitrary > state to some known state, unless the BIOS was used to get the card > into that state in the first place. > > Specifically, there exist write-only registers which are shadowed > in RAM on a number of cards, and any modification outside the BIOS > will result in the shadow data being rendered stale. > > Any attempt to restore the card toa known state using BIOS will only > operate on the deltas from the shadow state to the desired state. > > Unless you modify X to use the BIOS calls to set the card state, > you will not be able to use the BIOS to reset the card state. > > Further, it's probably desirable to link the state restoration to > the *previous* state, which may not be known to the console driver, > rather than the default state (which might be). For example, consider > a 50 line text display following the manual loading of a VGA font > for support of this mode, the memory for which is subsequently > stomped by the X server. > > Consider also the possible consequences of a previous mode that > was not the default mode for the kernel debugger in a break to > kernel debugger while X is active on the console. > > If a BIOS-based approach is used, it will seriously limit the > available modes for normal console operation and for X servers; > this is probably an unacceptable consequence. Are you sure of this? Most BIOSes manage to reset to text mode every time you reboot the machine, even without a hardware reset. But in general I agree, this is a bit of a kludge. >> ... ] > >> Hah. You obviously haven't had to work with PC viode hardware, have you? > > I agree with this "hah"... that last suggestion was naieve. On the > other hand, I don't think it was punishably so, I think he was just > trying to compromise with an uncompromising opponent. 8-) 8). No, it wasn't naïve. You appear to have misinterpreted it. Sure, there's more to it than just supplying a list of register/content pairs, but not too much more. An appropriately intelligent format of the register list would handle it. >> On the other hand, the manufacturer of the card _does_ know intimately >> how it works. They write functions for manipulating the card >> hardware, and stick them in a PROM on the card. >> >> Why not use their code and save ourselves the agony? > > Because unless you use their code for all things, the result of > using their code is indeterminate. Even if the automaton involved > is determinant (it is), the results depend entirely on the start > states (they aren't). There's another point to be made that the board manufacturer's software doesn't do all the things we would like to do with it. It's optimized for Microslop, and even Microslop environments need external drivers. Sure, as I suggested in an earlier message, we can follow up the BIOS calls with appropriate calls from the video driver. And it would probably work. But it's not pretty. Greg From owner-freebsd-hackers Sun Aug 17 20:42:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17866 for hackers-outgoing; Sun, 17 Aug 1997 20:42:19 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA17861; Sun, 17 Aug 1997 20:42:13 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA09705; Mon, 18 Aug 1997 04:34:19 +0200 From: Luigi Rizzo Message-Id: <199708180234.EAA09705@labinfo.iet.unipi.it> Subject: isa_dmastatus To: smp@csn.net (Steve Passe), luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Mon, 18 Aug 1997 04:34:18 +0200 (MET DST) Cc: multimedia@freebsd.org, hackers@freebsd.org In-Reply-To: <199708180245.UAA09140@Ilsa.StevesCafe.com> from "Steve Passe" at Aug 17, 97 08:44:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Feeling much involved with this issue... I fully second Steve's opinion and with the same motivations: > people realize that the days of different pieces of code accessing common > hardware are over. As SMP is brought into more and more of the kernel this > becomes unacceptable. Areas such as the DMA hardware will have to be > encapsolated into "critical regions". No one will be allowed to have private > code to access these sorts of things, not even for short testing periods. this said, and since I cannot track very easily -current and amancio's work, I cannot say from here what in the committed isa_dmastatus conflicts with guxpnpXX. I saw once a comment related to the voxware code not following the proper sequence of calls to the dma functions thus having problems with checks for dma_inuse and dma_busy. Having been there I have the feeling that it would be a pain in the neck to make the voxware code behave properly, and the easiest workaround is to disable such checks. My code does not have these problems but I had the advantage of starting from scratch, so I decided to put the checks in as an additional safety mechanism, and since they did not harm for me. Pragmatically, I suggest that at least temporarily the isa_dmastatus be made to work for guspnpXX. After all the sound driver (guspnpXX, or mine) is the only part of the system using it at the moment, I don't think Amancio is asking for changes to the interface of the function, and disabling some checks does not change the function's behaviour when invoked in the correct way. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Sun Aug 17 20:54:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA18500 for hackers-outgoing; Sun, 17 Aug 1997 20:54:52 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA18470; Sun, 17 Aug 1997 20:54:45 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA12749; Mon, 18 Aug 1997 13:54:00 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id NAA10202; Mon, 18 Aug 1997 13:23:59 +0930 (CST) Message-ID: <19970818132357.12809@lemis.com> Date: Mon, 18 Aug 1997 13:23:57 +0930 From: Greg Lehey To: Michael Smith Cc: phk@critter.dk.tfs.com, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Parallel port developpements - ppbus References: <19970818080055.00098@lemis.com> <199708180122.KAA08379@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708180122.KAA08379@genesis.atrad.adelaide.edu.au>; from Michael Smith on Mon, Aug 18, 1997 at 10:52:34AM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 10:52:34AM +0930, Michael Smith wrote: > Greg Lehey stands accused of saying: >>> Is it likely to work on a port that's open to shared use? >> >> Of course! In fact, you can print and transfer data at the same time :-) > > Really? From lp(4) : > > Initially, the lpt device is active for printing and the network inter- > face is inactive; however, once the corresponding lp device has been con- > figured 'up' with ifconfig(8) printing is disabled until the network in- > terface is configured 'down'. I didn't think that you were humour-impaired. Greg From owner-freebsd-hackers Sun Aug 17 21:02:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA18908 for hackers-outgoing; Sun, 17 Aug 1997 21:02:23 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA18903; Sun, 17 Aug 1997 21:02:15 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA09746; Mon, 18 Aug 1997 04:52:56 +0200 From: Luigi Rizzo Message-Id: <199708180252.EAA09746@labinfo.iet.unipi.it> Subject: PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Mon, 18 Aug 1997 04:52:55 +0200 (MET DST) Cc: msmith@atrad.adelaide.edu.au, terry@lambert.org, freebsd-multimedia@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199708180144.SAA02281@rah.star-gate.com> from "Amancio Hasty" at Aug 17, 97 06:44:03 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >From The Desk Of Michael Smith : > > I'd prefer not to debate it either. I think that it's sufficiently > > separate that when the time comes it can be relocated without > > adversely affecting anything at all. I merely resent the effort > > that's being put into standalone PnP-for-sound-cards-only work where > > the same effort could be better spent on a generalised push. > > > > As far as I know Luigi's PnP efforts are not tied to the sound > driver and we are using the sound driver as a testbed for PnP support. Right. People, if you have the time please read and comment the document on PnP configuration that is in my sound code snapshot http://www.iet.unipi.it/~luigi/snd970814.tgz (the file is sound/doc/pnp.ps.gz). I think this code could almost go into the source tree, with just a little more work (which I am doing at the moment). The PnP code does not harm if it finds a peripheral which is not supported, and it works if a peripheral is supported (yes it assumes a working PnP bios, but that problem will be overocme soon with a manual override mechanism). Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Sun Aug 17 21:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA24728 for hackers-outgoing; Sun, 17 Aug 1997 21:49:13 -0700 (PDT) Received: from ns2.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA24723 for ; Sun, 17 Aug 1997 21:49:11 -0700 (PDT) Received: from localhost (ian@localhost) by ns2.gamespot.com (8.8.5/8.8.5) with SMTP id VAA07197 for ; Sun, 17 Aug 1997 21:48:54 -0700 (PDT) Date: Sun, 17 Aug 1997 21:48:54 -0700 (PDT) From: Ian Kallen To: freebsd-hackers@freebsd.org Subject: dead disk Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What a grrrreat weekend I'm having >:'L ugh! Evidently one of the "spare disks" we had laying around that I had thought would suit me for my needs for additional disk space must have majorly malfunctioned: what was my system disk went south on me. I nabbed another disk (brand new this time, it had been allocated for another project but I need to get this machine back to life...), installed 2.2-970816. Now I have my old dead disk in an enclosure. When I try to fsck it, I get this crap: Aug 18 04:34:58 scorn /kernel: , retries:2 Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 csi:1,79,7,3b asc:16,0 Data s ynchronization mark error field replaceable unit: 15 Aug 18 04:34:59 scorn /kernel: , retries:1 Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 csi:1,79,7,3b asc:16,0 Data s ynchronization mark error field replaceable unit: 15 Aug 18 04:34:59 scorn /kernel: , FAILURE Aug 18 04:34:59 scorn /kernel: pid 162 (fsck), uid 0: exited on signal 8 (core dumped) Everything was fine until I stuck that damn other disk...arg. Anyway, either of the partitions, if I try to access them, I'm SOL. However, I can see the disklabel fine. See: # disklabel sd3 # /dev/rsd3c: type: SCSI disk: sd0s1 label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 1012 sectors/unit: 2074592 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: 65536 0 4.2BSD 0 0 0 # (Cyl. 0 - 31) b: 262144 65536 swap # (Cyl. 32 - 159) c: 2074592 0 unused 0 0 # (Cyl. 0 - 1012*) e: 1746912 327680 4.2BSD 0 0 0 # (Cyl. 160 - 1012*) So is all hope lost for this disk? To rub my face in it, the back up of this system was incomplete and munged. Any suggestions for reviving this poor beast would be most appreciated! Thanks, -Ian -- Ian Kallen ian@gamespot.com Director of Technology and Web Administration SpotMedia Communications http://www.gamespot.com/ http://www.videogamespot.com/ From owner-freebsd-hackers Sun Aug 17 22:29:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA26727 for hackers-outgoing; Sun, 17 Aug 1997 22:29:10 -0700 (PDT) Received: from quasi.bis.co.il (quasi.bis.co.il [192.115.114.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA26717 for ; Sun, 17 Aug 1997 22:29:06 -0700 (PDT) Received: from quasi.bis.co.il (localhost [127.0.0.1]) by quasi.bis.co.il (8.8.3/8.8.3) with SMTP id IAA24346 for ; Mon, 18 Aug 1997 08:34:56 GMT Message-ID: <33F8092F.2C67412E@bis.co.il> Date: Mon, 18 Aug 1997 08:34:56 +0000 From: Meir Dukhan Organization: Bis Software Systems Ltd X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: wd0: interrupt timeout: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Is one can tell me what this messages mean ? wd0: interrupt timeout: wd0: status 50 error 0 thanks, -- Meir From owner-freebsd-hackers Sun Aug 17 22:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27784 for hackers-outgoing; Sun, 17 Aug 1997 22:51:17 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA27779 for ; Sun, 17 Aug 1997 22:51:14 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA29101; Mon, 18 Aug 1997 07:51:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA04455; Mon, 18 Aug 1997 07:32:31 +0200 (MET DST) Message-ID: <19970818073229.DO12056@uriah.heep.sax.de> Date: Mon, 18 Aug 1997 07:32:29 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: ian@gamespot.com (Ian Kallen) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dead disk References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Ian Kallen on Aug 17, 1997 21:48:54 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ian Kallen wrote: > Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 > csi:1,79,7,3b asc:16,0 Data synchronization mark error > field replaceable unit: 15 > So is all hope lost for this disk? Did you turn on automatic error recovery? It's on mode page 1 (see scsi(8)). If you turn it on right now, you can't fix the old errors unless you overwrite the bad block (0x50033, block number from the beginning of the device). If this doesn't help either, you can still try backing it up. I think dump(8) is fairly forgiving if a medium has a few bad spots only. Also, problems of this kind are often temperature-related, so cooling the drive down could get you at least the desired backup. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 22:57:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA28046 for hackers-outgoing; Sun, 17 Aug 1997 22:57:58 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA28038 for ; Sun, 17 Aug 1997 22:57:44 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id BAA09262; Mon, 18 Aug 1997 01:03:07 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 18 Aug 1997 01:03:07 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Charles Ebert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The low priority items In-Reply-To: <33F78D7E.2610@theshop.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm just about totalyly sure that freebsd supports two kinds of threads, native and "pthreads" (which i think are posix threads) i could be wrong. ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" On Sun, 17 Aug 1997, Charles Ebert wrote: > I'm a little slow. Did I read correctly that Threaded processes are > not supported? And the next line down from that mentioned something > of the same, however, can I assume it is to deal with multiprocessor > CPU boards as well? > > I can understand the rush to invent new drives and support three > channel scsi cards and all that. > > I was always told of UNIX's unique ability to run multiple processor > systems. I never imagined that this system would have a problem with > threading. I was hoping that the multiple processor issue would > have a higher priority than it does. > > I'm a commercial windows programmer. I also work on OS2. > Seems like this environment is similar to OS2 in the aspect that > OS2 for the most part relys on one processor. Yet OS2 has support > for threading 5,000 some odd tasks and do it with 255 seperate > sessions. > > >From what I've read this Free BSD seems to support multiple sessions. > Yet I also read something about DLL's being supported, but I guess > you can't thread anything. > > As the system piles up, wouldn't it be more and more difficult to > achieve these goals? I'm very tempted to help but the only working > PC I have right now is this toshiba portable. > > Perhaps I will get into this next year as I plan on building another > machine. You have caught my eye with all this. > > I just love messes. Love resolving them, working on them. > You can only play so many card games you know. > > -- > Charlie > From owner-freebsd-hackers Sun Aug 17 23:08:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28508 for hackers-outgoing; Sun, 17 Aug 1997 23:08:42 -0700 (PDT) Received: from ns2.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28503 for ; Sun, 17 Aug 1997 23:08:38 -0700 (PDT) Received: from localhost (ian@localhost) by ns2.gamespot.com (8.8.5/8.8.5) with SMTP id XAA08887; Sun, 17 Aug 1997 23:08:19 -0700 (PDT) Date: Sun, 17 Aug 1997 23:08:18 -0700 (PDT) From: Ian Kallen To: Joerg Wunsch cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dead disk In-Reply-To: <19970818073229.DO12056@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, J Wunsch wrote: Thanks Joerg! > As Ian Kallen wrote: > > Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 > > csi:1,79,7,3b asc:16,0 Data synchronization mark error > > field replaceable unit: 15 > > Did you turn on automatic error recovery? It's on mode page 1 (see > scsi(8)). > Um, can you provide me with an example of how to use it for automatic error recovery? Like this? scsi -f /dev/rsd3c -m 1 I looked at scsi(8) and /usr/share/misc/scsi_modes for the mode pages... I don't know enough about low level scsi to find anything illuminating there. > If you turn it on right now, you can't fix the old errors unless you > overwrite the bad block (0x50033, block number from the beginning of > the device). > > If this doesn't help either, you can still try backing it up. I think > dump(8) is fairly forgiving if a medium has a few bad spots only. > Also, problems of this kind are often temperature-related, so cooling > the drive down could get you at least the desired backup. > Dumping a raw device? Hmm, never tried it. I've got the disk cooled, it's in it's own enclosure now. thanks! -Ian > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > -- Ian Kallen ian@gamespot.com Director of Technology and Web Administration SpotMedia Communications http://www.gamespot.com/ http://www.videogamespot.com/ From owner-freebsd-hackers Sun Aug 17 23:12:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA28830 for hackers-outgoing; Sun, 17 Aug 1997 23:12:54 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA28814 for ; Sun, 17 Aug 1997 23:12:38 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id BAA09276; Mon, 18 Aug 1997 01:17:49 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 18 Aug 1997 01:17:48 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Meir Dukhan cc: hackers@FreeBSD.ORG Subject: Re: wd0: interrupt timeout: In-Reply-To: <33F8092F.2C67412E@bis.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk dead disk :) a 127 meg that i had was doing that and it bit the dust recently... ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" On Mon, 18 Aug 1997, Meir Dukhan wrote: > Hi, > > > Is one can tell me what this messages mean ? > > wd0: interrupt timeout: > wd0: status 50 error 0 > > thanks, > -- Meir > From owner-freebsd-hackers Sun Aug 17 23:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29334 for hackers-outgoing; Sun, 17 Aug 1997 23:20:40 -0700 (PDT) Received: from ns2.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29322 for ; Sun, 17 Aug 1997 23:20:31 -0700 (PDT) Received: from localhost (ian@localhost) by ns2.gamespot.com (8.8.5/8.8.5) with SMTP id XAA09112; Sun, 17 Aug 1997 23:20:12 -0700 (PDT) Date: Sun, 17 Aug 1997 23:20:12 -0700 (PDT) From: Ian Kallen To: Joerg Wunsch cc: freebsd-hackers@FreeBSD.ORG Subject: Re: dead disk In-Reply-To: <19970818073229.DO12056@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, J Wunsch wrote: > Did you turn on automatic error recovery? It's on mode page 1 (see > scsi(8)). > > If you turn it on right now, you can't fix the old errors unless you > overwrite the bad block (0x50033, block number from the beginning of > the device). Poking through the archives and the man page, I just don't find anything informative leading towards a resolution. Does this tell me anything I can you to save this disk? # scsi -f /dev/rsd3.ctl -m 1 AWRE (Auto Write Reallocation Enbld): 0 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 16 Correction Span: 22 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 16 Recovery Time Limit: 0 thanks -Ian -- Ian Kallen ian@gamespot.com Director of Technology and Web Administration SpotMedia Communications http://www.gamespot.com/ http://www.videogamespot.com/ From owner-freebsd-hackers Sun Aug 17 23:21:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29398 for hackers-outgoing; Sun, 17 Aug 1997 23:21:20 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA29391 for ; Sun, 17 Aug 1997 23:21:16 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29246; Mon, 18 Aug 1997 08:21:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA12824; Mon, 18 Aug 1997 07:54:56 +0200 (MET DST) Message-ID: <19970818075455.EY56732@uriah.heep.sax.de> Date: Mon, 18 Aug 1997 07:54:55 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: mdukhan@bis.co.il (Meir Dukhan) Subject: Re: wd0: interrupt timeout: References: <33F8092F.2C67412E@bis.co.il> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33F8092F.2C67412E@bis.co.il>; from Meir Dukhan on Aug 18, 1997 08:34:56 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Meir Dukhan wrote: > Is one can tell me what this messages mean ? > > wd0: interrupt timeout: > wd0: status 50 error 0 The disk didn't interrupt as expected, and has been `unwedged' by a timeout routine. Happens every now and then. That's IDE. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 23:34:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00123 for hackers-outgoing; Sun, 17 Aug 1997 23:34:07 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA00111 for ; Sun, 17 Aug 1997 23:34:02 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA01628; Mon, 18 Aug 1997 08:34:19 +0200 (MEST) From: Søren Schmidt Message-Id: <199708180634.IAA01628@sos.freebsd.dk> Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: <19970817230359.JX15769@uriah.heep.sax.de> from J Wunsch at "Aug 17, 97 11:03:59 pm" To: hackers@FreeBSD.ORG Date: Mon, 18 Aug 1997 08:34:19 +0200 (MEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to J Wunsch who wrote: > As Søren Schmidt wrote: > > > I wouldn't bet on that 80% factor, if somebody is going to rewrite the > > base utils. For one this is a total waste of time (and maybe talent), > > the other is that it will render us completely incompatible with the > > rest of the BSD world. I think that nobody would be stupid enough to > > willingly takeover that kind of maintenance burden... > > We've been there before, so this will be my last followup in this > thread. (Please, don't redirect any future personal Cc's to me > either, i'm getting sick of Cc's for lengthy threads i'm not > interested in.) Then don't participate :) > Go and read Net/2's whereis(1) code, and then decide which one is > easier maintenable. (Sorry, the Net/2 code is `tainted', so you need > a FreeBSD 1.x CD-ROM for it. This was another reason to use Perl for > me, the structure is now so clearly different that nobody could claim > a copyright violation, even though the user interface is basically the > same. Don't count on the 4.4BSD-Lite version at all, it's totally > crippled, compared to the historic one. I wouldn't have rewritten it > at all otherwise.) > > Scripting languages are mainly used to _reduce_ the maintenance > effort. Wonder why phk prefers Tcl for so many things? ;) He's slightly insane too :) > > If I want useless bloat > > That's why i told about a required *justification* before somebody's > going to rewrite something. Just a rewrite only, with (nearly) the > same features, the same bad structure, etc. constitutes IMHO not a > justification. Neither of my quoted examples falls into this. > > The question whether some particular developer perhaps doesn't `speak' > some of the used languages himself might bias him, but this alone > doesn't establish ``unmaintenable code''. I bet even CVSup is > probably way easier to maintain for me now than it would have been > written in C++, or (*shudder* :) in C. And i've got absolutely no > experience in M3 right now. But i've got no doubts i could learn it > if necessary... Cheap point, and mature/experienced programmers will genrally have no problem adapting to a new language. I think that my point about caompatibility etc still stands as is.. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Aug 17 23:36:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00300 for hackers-outgoing; Sun, 17 Aug 1997 23:36:01 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA00280 for ; Sun, 17 Aug 1997 23:35:56 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA01650; Mon, 18 Aug 1997 08:36:02 +0200 (MEST) From: Søren Schmidt Message-Id: <199708180636.IAA01650@sos.freebsd.dk> Subject: Re: Problems detecting ATAPI CDROM in 2.2-970801-RELENG In-Reply-To: <498.871850470@verdi.nethelp.no> from "sthaug@nethelp.no" at "Aug 17, 97 10:41:10 pm" To: sthaug@nethelp.no Date: Mon, 18 Aug 1997 08:36:02 +0200 (MEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to sthaug@nethelp.no who wrote: > I recently upgraded a machine here from 2.2-BETA (as of 961226) to > 2.2-970801-RELENG. This broke the detection of an ATAPI CDROM on wdc1. > Further checking (by adding kernel printf's to sys/i386/isa/wd.c) showed > that the problem is in wdprobe(). If I add a printf just before line 340 > of wd.c (version 1.119.2.6): > > printf("XXX %s%d get errstatus\n", dvp->id_driver->name, unit); > du->dk_error = inb(du->dk_port + wd_error); > > the CDROM is detected just fine. If I revert to the original wd.c, the > CDROM is not detected. > > Obviously there's a timing issue here, and the printf adds enough of a > delay that the detection works. However, as far as I can see both wdprobe > and wdcommand (which is called just before my printf) are exactly the same > in 2.2-BETA and 2.2-970801-RELENG. > > Any good ideas? What kind of cdrom do you have ?? controller/Motherboard ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Aug 17 23:46:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00795 for hackers-outgoing; Sun, 17 Aug 1997 23:46:26 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA00787 for ; Sun, 17 Aug 1997 23:46:20 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA01679; Mon, 18 Aug 1997 08:45:26 +0200 (MEST) From: Søren Schmidt Message-Id: <199708180645.IAA01679@sos.freebsd.dk> Subject: Re: reset screen hardware? In-Reply-To: <19970818122939.30413@lemis.com> from Greg Lehey at "Aug 18, 97 12:29:39 pm" To: grog@lemis.com (Greg Lehey) Date: Mon, 18 Aug 1997 08:45:26 +0200 (MEST) Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Greg Lehey who wrote: > Sure. No debate. > > > So to get concrete in this matter, we need: > > > > 1. Being able to call realmode code from the kernel. > > > > 2. Being able to run BIOS functions, that is we need to keep > > track of the BIOS's workspace, most often in low memory. > > > > 3. Then write the code to call the right BIOS functions to > > be able to talk to the video HW. > > > > So, if someone is SERIOUS about getting this to work, pick one > > of the above, come back to me so we can get technical about > > the details, and them submit the diffs. Then I'm certain it will > > be committed, and the author will get his fair share of applause.. > > > > But gimme a break on just demanding XXX functionality, sometimes > > with badly (if at all) designed hacks.... > > Wait a while, there was no design at all at this point. We had Mike > saying that it wasn't possible, and me suggesting a possible approach. > My statement was that the kernel probe routines seemed the obvious > place to put such code. I stand by that statement. The question was > how to find out the parameters, and the fact that the code is so > voluminous makes the approach impractical. But that doesn't make the > approach a hack. There was design but only in a few peoples heads sofar, as we need the 3 above points implemented first, so should we start there please ? > There is, BTW, a potential problem with the "call the BIOS" approach > (which I consider marginally more of a hack, since the driver doesn't > know what's going on): what if the driver has set a different mode for > the board, like 50 line or some such? That would have to be redone > after the BIOS call. Sigh, the call BIOS is the only option we've got, (well besides making it possible to use win95/NT drivers, which is a HUGE task if at all feasible). There is no problem in using the BIOS (except that we dont have the code to do it, yet). Syscons allways know exactly where it has its video card, except in the case of X where the app reprograms the card. Now when we have the BIOS calls working syscons takes over the task of modifying the cards regs etc. via the BIOS, and the apps are denied acces to the ports. Then syscons always knows where and how the card is and can restore whatever mode it (and of cause the BIOS) understand. Pretty simple actually, once you have the means to call the BIOS... Now, who volounteers the diffs ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Sun Aug 17 23:51:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01085 for hackers-outgoing; Sun, 17 Aug 1997 23:51:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA01079 for ; Sun, 17 Aug 1997 23:51:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29380; Mon, 18 Aug 1997 08:51:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA02000; Mon, 18 Aug 1997 08:24:17 +0200 (MET DST) Message-ID: <19970818082416.MH42279@uriah.heep.sax.de> Date: Mon, 18 Aug 1997 08:24:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: ian@gamespot.com (Ian Kallen) Subject: Re: dead disk References: <19970818073229.DO12056@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Ian Kallen on Aug 17, 1997 23:20:12 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ian Kallen wrote: > Poking through the archives and the man page, I just don't find anything > informative leading towards a resolution. Does this tell me anything I > can you to save this disk? > > # scsi -f /dev/rsd3.ctl -m 1 Almost. Add ``-e -P 3''. I thought there was an example somewhere in the handbook? I might be mistaken. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 23:51:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01117 for hackers-outgoing; Sun, 17 Aug 1997 23:51:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA01103 for ; Sun, 17 Aug 1997 23:51:33 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA29385; Mon, 18 Aug 1997 08:51:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA03048; Mon, 18 Aug 1997 08:26:17 +0200 (MET DST) Message-ID: <19970818082616.WD01646@uriah.heep.sax.de> Date: Mon, 18 Aug 1997 08:26:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: ian@gamespot.com (Ian Kallen) Subject: Re: dead disk References: <19970818073229.DO12056@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Ian Kallen on Aug 17, 1997 23:08:18 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ian Kallen wrote: > Dumping a raw device? Hmm, never tried it. Dump(8) always uses the raw device. If you provide a mount point, it picks up the raw device from /etc/fstab. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 17 23:57:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01539 for hackers-outgoing; Sun, 17 Aug 1997 23:57:54 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01532 for ; Sun, 17 Aug 1997 23:57:50 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA11093; Mon, 18 Aug 1997 16:27:35 +0930 (CST) From: Michael Smith Message-Id: <199708180657.QAA11093@genesis.atrad.adelaide.edu.au> Subject: Re: dead disk In-Reply-To: from Ian Kallen at "Aug 17, 97 11:20:12 pm" To: ian@gamespot.com (Ian Kallen) Date: Mon, 18 Aug 1997 16:27:35 +0930 (CST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ian Kallen stands accused of saying: > On Mon, 18 Aug 1997, J Wunsch wrote: > > Did you turn on automatic error recovery? It's on mode page 1 (see > > scsi(8)). > > > > If you turn it on right now, you can't fix the old errors unless you > > overwrite the bad block (0x50033, block number from the beginning of > > the device). > > Poking through the archives and the man page, I just don't find anything > informative leading towards a resolution. Does this tell me anything I > can you to save this disk? > > # scsi -f /dev/rsd3.ctl -m 1 > AWRE (Auto Write Reallocation Enbld): 0 > ARRE (Auto Read Reallocation Enbld): 0 The scsi(8) manpage has an example of editing this page to set these values to 1. Once you've done this, you will probably need to arrange to _write_ to the disk region that's broken in order to force the reallocation. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Aug 18 00:05:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA02099 for hackers-outgoing; Mon, 18 Aug 1997 00:05:17 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA02093 for ; Mon, 18 Aug 1997 00:05:10 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id JAA01835; Mon, 18 Aug 1997 09:05:17 +0200 (MEST) From: Søren Schmidt Message-Id: <199708180705.JAA01835@sos.freebsd.dk> Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: from Tim Vanderhoek at "Aug 17, 97 07:14:10 pm" To: hoek@hwcn.org (Tim Vanderhoek) Date: Mon, 18 Aug 1997 09:05:17 +0200 (MEST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Tim Vanderhoek who wrote: > On Sun, 17 Aug 1997, Søren Schmidt wrote: > > [re: make the world with perls] > > > base utils. For one this is a total waste of time (and maybe talent), > > Of course, perhaps the holder of this time & talent has no > interest in doing anything "better". :-) Hmm, right... > > the other is that it will render us completely incompatible with the > > rest of the BSD world. I think that nobody would be stupid enough to > > willingly takeover that kind of maintenance burden... > > No, since presumably we will gain such huge advantages by > rewriting everything in perl that the rest of the BSD world will > have little choice but to adopt our version. That will be the day :), well at least we will serve the same purpose as Micro$lot then, make sure that you have to get the latest greatest hardware to get mediocre performance, sigh.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Mon Aug 18 00:26:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03449 for hackers-outgoing; Mon, 18 Aug 1997 00:26:27 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA03312 for ; Mon, 18 Aug 1997 00:25:10 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 3940 invoked by uid 1001); 18 Aug 1997 07:24:16 +0000 (GMT) To: sos@sos.freebsd.dk Cc: hackers@FreeBSD.ORG Subject: Re: Problems detecting ATAPI CDROM in 2.2-970801-RELENG In-Reply-To: Your message of "Mon, 18 Aug 1997 08:36:02 +0200 (MEST)" References: <199708180636.IAA01650@sos.freebsd.dk> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 18 Aug 1997 09:24:16 +0200 Message-ID: <3938.871889056@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I recently upgraded a machine here from 2.2-BETA (as of 961226) to > > 2.2-970801-RELENG. This broke the detection of an ATAPI CDROM on wdc1. ... > What kind of cdrom do you have ?? controller/Motherboard ?? The motherboard is an EPoX P55-ET motherboard with Intel 82430FX chipset (your typical "noname" OEM motherboard). wdc1 is the normal secondary IDE controller on the 82430FX chipset. The CDROM drive is an Aztech 6x CDA668-01I. When it's detected, the log shows wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (atapi): , removable, iordy wcd0: 1033Kb/sec, 240Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked Another piece of info: When I put in the kernel printf in 970801-RELENG the CDROM was detected. It still doesn't work - attempting to mount a cd9660 file system results in wcd0: i/o error, status=51, error=30 Again, the same thing works fine with a 2.2-BETA (961226) kernel. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Mon Aug 18 00:29:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03710 for hackers-outgoing; Mon, 18 Aug 1997 00:29:40 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA03704; Mon, 18 Aug 1997 00:29:37 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id AAA00439; Mon, 18 Aug 1997 00:23:44 -0700 (PDT) Message-Id: <199708180723.AAA00439@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: smp@csn.net (Steve Passe), multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: isa_dmastatus In-reply-to: Your message of "Mon, 18 Aug 1997 04:34:18 +0200." <199708180234.EAA09705@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Aug 1997 00:23:44 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lets see, If a driver uses auto dma, it generally calls isa_dmastart once. isa_dmastart sets the busy flag: from isa_dmastart: dma_busy |= (1 << chan); When we get a dma interrupt from the device, if I call isa_dmadone to clear the busy flag it does not mean that I am done using the buffer and I can't call isa_dmastart because the dma processes is still active. So if we wish to support auto dma and use the existing dma interface in isa.c then I suggest that we add a simple check in the isa dma routine to bypass the busy flag check when we are using auto dma. What does this mean in an SMP environment I have no idea because when a driver requests auto dma in essence he is requesting exclusive access of the dma channel. Please let me know if my explanation is not clear and if there are any intentions to support auto dma in the isa.c / *dma* routines. Thank you, Amancio >From The Desk Of Luigi Rizzo : > Feeling much involved with this issue... I fully second Steve's opinion > and with the same motivations: > > > people realize that the days of different pieces of code accessing common > > hardware are over. As SMP is brought into more and more of the kernel this > > becomes unacceptable. Areas such as the DMA hardware will have to be > > encapsolated into "critical regions". No one will be allowed to have priva te > > code to access these sorts of things, not even for short testing periods. > > this said, and since I cannot track very easily -current and > amancio's work, I cannot say from here what in the committed > isa_dmastatus conflicts with guxpnpXX. I saw once a comment related > to the voxware code not following the proper sequence of calls to > the dma functions thus having problems with checks for dma_inuse > and dma_busy. Having been there I have the feeling that it would > be a pain in the neck to make the voxware code behave properly, > and the easiest workaround is to disable such checks. > > My code does not have these problems but I had the advantage of > starting from scratch, so I decided to put the checks in as an > additional safety mechanism, and since they did not harm for me. > > Pragmatically, I suggest that at least temporarily the isa_dmastatus > be made to work for guspnpXX. After all the sound driver (guspnpXX, or > mine) is the only part of the system using it at the moment, I don't > think Amancio is asking for changes to the interface of the function, > and disabling some checks does not change the function's behaviour when > invoked in the correct way. > > Cheers > Luigi > -----------------------------+-------------------------------------- > Luigi Rizzo | Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it | Universita' di Pisa > tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ > _____________________________|______________________________________ > From owner-freebsd-hackers Mon Aug 18 00:55:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA05368 for hackers-outgoing; Mon, 18 Aug 1997 00:55:48 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA05360 for ; Mon, 18 Aug 1997 00:55:44 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id RAA19957; Mon, 18 Aug 1997 17:55:05 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id RAA10910; Mon, 18 Aug 1997 17:25:05 +0930 (CST) Message-ID: <19970818172504.50471@lemis.com> Date: Mon, 18 Aug 1997 17:25:04 +0930 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <19970818122939.30413@lemis.com> <199708180645.IAA01679@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C199708180645=2EIAA01679=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Mon=2C_Aug_18=2C_1997_at_08=3A45=3A2?= =?iso-8859-1?Q?6AM_+0200?= Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id RAA10910 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA05361 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 08:45:26AM +0200, Søren Schmidt wrote: > In reply to Greg Lehey who wrote: >> There is, BTW, a potential problem with the "call the BIOS" approach >> (which I consider marginally more of a hack, since the driver doesn't >> know what's going on): what if the driver has set a different mode for >> the board, like 50 line or some such? That would have to be redone >> after the BIOS call. > > Sigh, the call BIOS is the only option we've got, (well besides making > it possible to use win95/NT drivers, which is a HUGE task if at all > feasible). I think the BIOS calls are bad enough without incorporating all the Microslop stuff. To do it halfway right, we probably need to reset the board and then replay any changes that the driver has made since then. Obviously, the first step is to reset the board. > There is no problem in using the BIOS (except that we dont have the > code to do it, yet). Syscons allways know exactly where it has its > video card, except in the case of X where the app reprograms > the card. Now when we have the BIOS calls working syscons takes over the > task of modifying the cards regs etc. via the BIOS, and the apps are > denied acces to the ports. Then syscons always knows where and how > the card is and can restore whatever mode it (and of cause the BIOS) > understand. Yes, it would be even nicer if we could get the X server to call syscons to set the registers... > Pretty simple actually, once you have the means to call the BIOS... > > Now, who volounteers the diffs ?? OK, I'll take a look at it. Mike sent me the URL ftp://sumatra.americantv.com/pub/vm86-970814.tar.gz; anything else I should look at? Greg From owner-freebsd-hackers Mon Aug 18 00:57:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA05487 for hackers-outgoing; Mon, 18 Aug 1997 00:57:35 -0700 (PDT) Received: from agni.nuko.com (dummy.nuko.com [206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA05482 for ; Mon, 18 Aug 1997 00:57:33 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id AAA27888; Mon, 18 Aug 1997 00:55:42 -0700 (PDT) From: Vinay Bannai Message-Id: <199708180755.AAA27888@agni.nuko.com> Subject: Re: Device drivers and DMA details?? To: dg@root.com Date: Mon, 18 Aug 1997 00:55:42 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708170836.BAA08684@implode.root.com> from "David Greenman" at "Aug 17, 97 01:36:44 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to David Greenman: > >Ah!! I see that the interface's if_start() routine is called when the > >network is not busy (IFF_OACTIVE). This means that IFF_OACTIVE is set for > >the interface while receiving the packet or when the controller is > >busy. > > Uh, no, IFF_OACTIVE indicates that the interface is busy transmitting > one or more packets and that it can't handle any additional packets for > xmit right now. > > > In fact it appears that the fxp driver never has the need to set the > >IFF_OACTIVE, so the fxp_start() gets called everytime a packet is queued > >on the interface queue > > Yes, IFF_OACTIVE is optional and is meant as a sort of optimization to > avoid calling the driver start routine. It doesn't make sense for if_fxp > because the fxp card supports dynamic chaining; in other words, a DMA chain > that is currently being transmitted can be extended with additional packets. > The only limit to how much the chain can be extend is an arbitrary one > having to do with the available DMA descriptors. I could actually set > IFF_OACTIVE when all transmit descriptors are exhausted, but the extra > overhead to deal with this wasn't worth it - it's a very rare condition > and the check at the top of fxp_start() will handle this case and return > immediately. > > > unless it is running at a priority of the hardware > >interrupt from the network controller. In that case since the hardware > >interrupt from the network controller being higher than splimp() will make > >it possible for the IF queues to be flushed before the priority drops back > >to splimp or whatever. > > Huh? "network controller being higher than splimp()"? Huh? None of the > above makes any sense. Sorry about that. I was meaning to say splnet() (the software interrupt for protocol processing) instead of splimp(). It is clear to me now. I was a little confused by the interrupt levels and the names. :-) > > > Is that a correct assesment? > > Yes, except for the last part. spl* protection is for protecting certain > critical regions from modification by interrupt routines. While the code > has an spl* level set, interrupts in that class will be blocked. splimp > blocks network device interrupts. splnet blocks network (input) packet > processing that would normally occur when the system returns to spl0. Received > packets are processed at spl0 in order to avoid certain driver reentrancy > problems when packets are being forwarded. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Thanks for the clarification. Vinay From owner-freebsd-hackers Mon Aug 18 01:45:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA08284 for hackers-outgoing; Mon, 18 Aug 1997 01:45:30 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA08279 for ; Mon, 18 Aug 1997 01:45:27 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id BAA26945; Mon, 18 Aug 1997 01:26:03 -0700 (PDT) Date: Mon, 18 Aug 1997 01:26:03 -0700 (PDT) From: "Jamil J. Weatherbee" To: Meir Dukhan cc: hackers@FreeBSD.ORG Subject: Re: wd0: interrupt timeout: In-Reply-To: <33F8092F.2C67412E@bis.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Are you running two hard drives in a master/slave configuration on a single controller --- if you are I think I had similiar problems you don't want more than one hard drive on each controller, I have two IDEs one on the primary as master with a cdrom as slave and one on the secondary set to cable select. These are both western digital 2.1 gigs if i put both say on the primary controller, one as master one as slave -- the second effectively doesn't work, returning lots of messages like yours under heavy usage, my theory is that somehow the ide controller cannot handle two fast eides chugging out data and misses interrupts somehow, when they start making ide hard drives that use atapi protocol then i'll be happy. On Mon, 18 Aug 1997, Meir Dukhan wrote: > Hi, > > > Is one can tell me what this messages mean ? > > wd0: interrupt timeout: > wd0: status 50 error 0 > > thanks, > -- Meir > From owner-freebsd-hackers Mon Aug 18 04:15:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14364 for hackers-outgoing; Mon, 18 Aug 1997 04:15:33 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA14346 for ; Mon, 18 Aug 1997 04:15:25 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA19899; Mon, 18 Aug 1997 07:14:52 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 18 Aug 1997 07:14 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id HAA10485; Mon, 18 Aug 1997 07:24:01 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id HAA04607; Mon, 18 Aug 1997 07:17:29 -0400 (EDT) Date: Mon, 18 Aug 1997 07:17:29 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708181117.HAA04607@lakes.dignus.com> To: ponds!root.com!dg, ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.dignus.com!rivers Subject: Re: "rm" speeds (2.1.7.1 vs. 2.2.1) Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Again, f.y.i. - this is a 486dx66 with 24meg of RAM, a typical IDE > >drive (1+gig)... The 2.2.1 kernel has NBUF defined at 128; to see > >if that's the problem... where the 2.1.7 kernel was from the boot floppy > >off of a 2.1.7 CDROM. > > That is the problem. Take out the NBUF= thing from your kernel config file > and rebuild/install the kernel. A system with 24MB of RAM will have about > 600 buffers if it is allowed to dynamically calculate the amount. > What's happening is that the directory is getting pushed out of the cache, > forcing the system to re-read much of it and the inode blocks each time. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > I'll give it a try! Thanks for pointing it out.. I've still got a directory to try it on - the box has been working overnight (about 9+ hours now) trying to delete it... - Dave Rivers - From owner-freebsd-hackers Mon Aug 18 05:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA16760 for hackers-outgoing; Mon, 18 Aug 1997 05:00:40 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA16735; Mon, 18 Aug 1997 05:00:30 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA10185; Mon, 18 Aug 1997 12:51:31 +0200 From: Luigi Rizzo Message-Id: <199708181051.MAA10185@labinfo.iet.unipi.it> Subject: Re: isa_dmastatus To: hasty@rah.star-gate.com (Amancio Hasty) Date: Mon, 18 Aug 1997 12:51:31 +0200 (MET DST) Cc: smp@csn.net, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199708180723.AAA00439@rah.star-gate.com> from "Amancio Hasty" at Aug 18, 97 00:23:25 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Lets see, > > If a driver uses auto dma, it generally calls isa_dmastart once. > isa_dmastart sets the busy flag: > > from isa_dmastart: > dma_busy |= (1 << chan); > > When we get a dma interrupt from the device, if I call isa_dmadone to > clear the busy flag it does not mean that I am done using the > buffer and I can't call isa_dmastart because the dma processes > is still active. > > So if we wish to support auto dma and use the existing dma interface > in isa.c then I suggest that we add a simple check in the isa > dma routine to bypass the busy flag check when we are using > auto dma. What does this mean in an SMP environment I have no right. > idea because when a driver requests auto dma in essence he is > requesting exclusive access of the dma channel. In fact I doubt ISA DMA channels can be shared since from the hw point of view they work as IRQ lines (i.e. active high). It is true that some peripherals have sw-programmable DMA lines (and IRQ as well) so in principle one could deactivate (i.e. put in Hi-Z) the DMA line and let someone else use it, but I doubt any of our driver does that right now. As for isa_dmadone, I am under the impression that the function is overloaded right now, because it serves to call the bounce-buffer code when necessary, and not just to mark the DMA channel as idle. Moreover there are bigger problems with DMA in automode since when you do a write using bounce buffers you need to invoke isa_dmastart every time, not just the first one. So in the end, I think that our isa_dma routines probably do not work with auto mode _and_ bounce buffers, indipendently of the checks on the dma_busy/dma_inuse flags. We can temporarily bypass the problem by making the DMA routines fail if auto mode is requested and a bounce buffer needs to be used for the channel. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Aug 18 05:17:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17552 for hackers-outgoing; Mon, 18 Aug 1997 05:17:35 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17547 for ; Mon, 18 Aug 1997 05:17:31 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id FAA19404; Mon, 18 Aug 1997 05:17:34 -0700 (PDT) To: S ren Schmidt cc: hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? In-reply-to: Your message of "Mon, 18 Aug 1997 08:34:19 +0200." <199708180634.IAA01628@sos.freebsd.dk> Date: Mon, 18 Aug 1997 05:17:34 -0700 Message-ID: <19400.871906654@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Scripting languages are mainly used to _reduce_ the maintenance > > effort. Wonder why phk prefers Tcl for so many things? ;) > > He's slightly insane too :) "slightly?" That's certainly news to me. Jordan From owner-freebsd-hackers Mon Aug 18 05:42:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA19126 for hackers-outgoing; Mon, 18 Aug 1997 05:42:03 -0700 (PDT) Received: from euthyphro.uchicago.edu (euthyphro.uchicago.edu [128.135.21.31]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA19121 for ; Mon, 18 Aug 1997 05:41:59 -0700 (PDT) Received: from phaedrus.uchicago.edu (phaedrus [128.135.21.10]) by euthyphro.uchicago.edu (8.8.6/8.8.4) with ESMTP id HAA02652; Mon, 18 Aug 1997 07:41:56 -0500 (CDT) Received: (from sfarrell@localhost) by phaedrus.uchicago.edu (8.8.5/8.8.5) id HAA16882; Mon, 18 Aug 1997 07:41:51 -0500 (CDT) To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: The low priority items References: Mime-Version: 1.0 (generated by tm-edit 7.89) Content-Type: text/plain; charset=US-ASCII From: stephen farrell Date: 18 Aug 1997 07:41:50 -0500 In-Reply-To: Alfred Perlstein's message of "Mon, 18 Aug 1997 01:03:07 +0000 (GMT)" Message-ID: <87u3gnacj5.fsf@phaedrus.uchicago.edu> Lines: 18 X-Mailer: Gnus v5.4.64/XEmacs 19.15 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein writes: > I'm just about totalyly sure that freebsd supports two kinds of threads, > native and "pthreads" (which i think are posix threads) i could be wrong. pthreads are a user-space thread library which multiplexes all of the threads into a single process (and hence cannot take advantage of smp). They conform to posix threads standard. recently freebsd has acquired a native threads package which is known as a hybrid threading package--it muliplexes user-space threads across _multiple_ processes--typically 1 per cpu--to take advantage of smp. freebsd native threads _also_ have a posix-conformant api. last I heard john dyson was writing the package... but i'd be interested in further status information myself. From owner-freebsd-hackers Mon Aug 18 06:18:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21235 for hackers-outgoing; Mon, 18 Aug 1997 06:18:05 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA21229 for ; Mon, 18 Aug 1997 06:17:55 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA03390; Mon, 18 Aug 1997 09:16:51 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 18 Aug 1997 09:16 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id JAA00218; Mon, 18 Aug 1997 09:03:53 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id IAA05973; Mon, 18 Aug 1997 08:57:33 -0400 (EDT) Date: Mon, 18 Aug 1997 08:57:33 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708181257.IAA05973@lakes.dignus.com> To: ponds!root.com!dg, ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.dignus.com!rivers Subject: Re: "rm" speeds (2.1.7.1 vs. 2.2.1) Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > > > Again, f.y.i. - this is a 486dx66 with 24meg of RAM, a typical IDE > > >drive (1+gig)... The 2.2.1 kernel has NBUF defined at 128; to see > > >if that's the problem... where the 2.1.7 kernel was from the boot floppy > > >off of a 2.1.7 CDROM. > > > > That is the problem. Take out the NBUF= thing from your kernel config file > > and rebuild/install the kernel. A system with 24MB of RAM will have about > > 600 buffers if it is allowed to dynamically calculate the amount. > > What's happening is that the directory is getting pushed out of the cache, > > forcing the system to re-read much of it and the inode blocks each time. > > > > -DG > > > > David Greenman > > Core-team/Principal Architect, The FreeBSD Project > > > > I'll give it a try! Thanks for pointing it out.. > > I've still got a directory to try it on - the box has been working > overnight (about 9+ hours now) trying to delete it... > That seems to have been the ticket!!! I'm doing an 'rm' right now of that troublesome directory, and I don't hear the tale-tell disk I/O pattern I heard before. It's just merrily spinning along deleteing things... (there was a *big* pause when it started; presumably skipping through those deleted entries...) Thanks everyone! - Dave Rivers - From owner-freebsd-hackers Mon Aug 18 08:27:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27857 for hackers-outgoing; Mon, 18 Aug 1997 08:27:41 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27851; Mon, 18 Aug 1997 08:27:36 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with SMTP id IAA20005; Mon, 18 Aug 1997 08:27:47 -0700 (PDT) Message-ID: <33F869F3.446B9B3D@FreeBSD.org> Date: Mon, 18 Aug 1997 08:27:47 -0700 From: "Jordan K. Hubbard" Organization: Walnut Creek CDROM X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-STABLE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: [Fwd: Re: Please Help Me Understand dlopen()] Content-Type: multipart/mixed; boundary="------------59E2B60015FB7483794BDF32" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------59E2B60015FB7483794BDF32 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hmmm - any comments, ld hackers? Jordan -- --------------59E2B60015FB7483794BDF32 Content-Type: message/news Content-Transfer-Encoding: 7bit Content-Disposition: inline Path: nntp2.ba.best.com!news1.best.com!nntprelay.mathworks.com!news.mathworks.com!fu-berlin.de!informatik.tu-muenchen.de!news From: Walter Hafner Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Please Help Me Understand dlopen() Date: 18 Aug 1997 14:39:35 +0200 Organization: Technische Universitaet Muenchen, Germany Distribution: world Message-ID: References: <5stu4v$aio$1@vixen.cso.uiuc.edu> <33F29838.59E2B600@FreeBSD.org> <5svjcd$209@tooting.netapp.com> NNTP-Posting-Host: pccog4.forwiss.tu-muenchen.de X-Newsreader: Gnus v5.2.25/XEmacs 19.14 Xref: nntp2.ba.best.com comp.unix.bsd.freebsd.misc:48935 guy@netapp.com (Guy Harris) writes: > Jordan K. Hubbard wrote: > >2. You need to look for _hello rather than hello or you won't be able to > >find the symbol. > > That's a significant deficiency: > > 1) not all UNIX C compilers prepend an underscore to symbols (I > think it was originally done to work around the PDP-11 UNIX > assembler having symbols with the names of the registers and > opssibly the opcodes), so if you can't, in some UNIXes, do > > dlsym(handle, "hello") > > to find a pointer to the function "hello" in a > dynamically-loaded object, that makes it impossible to use > "dlsym()" portably - SunOS 5.5.1, which expects C compilers > not to prepend underscores and which supports "dlopen()", > will *not* remove the prepended underscore if the lookup > fails (i.e., the lookup of "_hello" will fail to find a > function "hello()"); > > 2) it's somewhat counterintuitive, as indicated by the fact that > Mr. Murphy didn't know he had to do it; > > 3) at least one of the UNIXes whose C compiler *does* prepend an > underscore and that supports "-ldl", namely SunOS 4.1[.x], > will, if a "dlsym()" lookup fails, retry the lookup with a > prepended underscore, it appears. > > The run-time linker should be changed to do what the SunOS 4.1[.x] > run-time linker does, allowing you to look for "hello" to find a > function "hello()". Hi! I bragged about just the same behaviour about 4 weeks ago. :-) The freeBSD dlsym() is - as far as I know - the only dlsym() implementation that doesn't search for _funktion() ... I also complained about dlopen() not searching LD_LIBRARY_PATH. One answer I got was the suggestion to implement it in the FreeBSD dl routines myself. Well, I could do it but that would be my first try on system programming ever. And I think it would significantly lower the high FreeBSD standards on code quality. :-) Instead I patched the dl code in our application. Our application ("HALCON") runs on Solaris, SunOS, HP/UX, IRIX, AIX, Ultrix, DEC Unix (OSF/1), Linux, FreeBSD, ... you name it. And now there is a very ugly "#ifdef __FreeBSD__" in the dl code. All other platforms show the expected behaviour. :-( -Walter -- Walter Hafner_____________________________ hafner@forwiss.tu-muenchen.de *CLICK* The best observation I can make is that the BSD Daemon logo is _much_ cooler than that Penguin :-) (Donald Whiteside) --------------59E2B60015FB7483794BDF32-- From owner-freebsd-hackers Mon Aug 18 09:23:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00517 for hackers-outgoing; Mon, 18 Aug 1997 09:23:48 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00501 for ; Mon, 18 Aug 1997 09:23:27 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id TAA16323; (8.8.3/zah/2.1) Mon, 18 Aug 1997 19:16:19 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id PAA02475; (8.6.11/zah/2.1) Mon, 18 Aug 1997 15:49:08 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id QAA10270; (8.6.9/zah/1.1) Mon, 18 Aug 1997 16:56:45 +0100 Received: from localhost (rssh@localhost) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id QAA18668; Mon, 18 Aug 1997 16:51:29 +0300 (EET DST) Date: Mon, 18 Aug 1997 16:51:29 +0300 (EET DST) From: Ruslan Shevchenko To: Michael Smith cc: Sergey Shkonda , freebsd-hackers@FreeBSD.ORG Subject: Re: Shared libs In-Reply-To: <199708142344.JAA21991@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 15 Aug 1997, Michael Smith wrote: > Sergey Shkonda stands accused of saying: > > How shared libraries working ? > > (loading 1'st prog, loading next prog, sharing code and data segments ) > > 'man 5 link', and read the kernel *_exec modules. + man dlopen > > > Sergey Shkonda (serg@bcs.zaporizhzhe.ua) > > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > @= mailto:rssh@cki.ipri.kiev.ua //RSSH http://www.ipri.kiev.ua/~rssh From owner-freebsd-hackers Mon Aug 18 09:28:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00716 for hackers-outgoing; Mon, 18 Aug 1997 09:28:44 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00707 for ; Mon, 18 Aug 1997 09:28:38 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id LAA18659; Mon, 18 Aug 1997 11:45:16 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id LAA15083; Mon, 18 Aug 1997 11:29:32 -0500 Message-ID: <19970818112931.19833@right.PCS> Date: Mon, 18 Aug 1997 11:29:31 -0500 From: Jonathan Lemon To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: Greg Lehey , jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <19970817163116.16698@lemis.com> <199708170951.LAA00412@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.61.1 In-Reply-To: =?iso-8859-1?Q?=3C199708170951=2ELAA00412=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Aug_08=2C_1997_at_11=3A51=3A19AM_+02?= =?iso-8859-1?Q?00?= Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 08, 1997 at 11:51:19AM +0200, Søren Schmidt wrote: > So to get concrete in this matter, we need: > > 1. Being able to call realmode code from the kernel. > > 2. Being able to run BIOS functions, that is we need to keep > track of the BIOS's workspace, most often in low memory. > > 3. Then write the code to call the right BIOS functions to > be able to talk to the video HW. > > So, if someone is SERIOUS about getting this to work, pick one > of the above, come back to me so we can get technical about > the details, and them submit the diffs. Then I'm certain it will > be committed, and the author will get his fair share of applause.. Well, I'm working on it. I've posted the results of a proof-of-concept implementation to -emulation, but still have to finish working out all the bugs out of the implementation. Right now, the code can call any random BIOS interrupt for which there is an interrupt vector in low memory. Calling random realmode routines will be equally easy. This is currently done from usermode for debugging, but can also easily be done from the kernel. Right now, what I'm working out is: - how to manage a process that doesn't have a valid 32-bit user context, but needs to be able to process interrupts. - how to serialize access to the BIOS, given that there probably need to be some pre/post processing of memory data areas. - whether to allocate more data area than 0-4K and isadevbase-1M. -- Jonathan From owner-freebsd-hackers Mon Aug 18 09:31:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00857 for hackers-outgoing; Mon, 18 Aug 1997 09:31:01 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00851; Mon, 18 Aug 1997 09:30:58 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id JAA04190; Mon, 18 Aug 1997 09:30:20 -0700 (PDT) Message-Id: <199708181630.JAA04190@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: smp@csn.net, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: isa_dmastatus In-reply-to: Your message of "Mon, 18 Aug 1997 12:51:31 +0200." <199708181051.MAA10185@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Aug 1997 09:30:20 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Luigi Rizzo : > > Lets see, > > > > If a driver uses auto dma, it generally calls isa_dmastart once. > > isa_dmastart sets the busy flag: > > > > from isa_dmastart: > > dma_busy |= (1 << chan); > > > > When we get a dma interrupt from the device, if I call isa_dmadone to > > clear the busy flag it does not mean that I am done using the > > buffer and I can't call isa_dmastart because the dma processes > > is still active. > > > > So if we wish to support auto dma and use the existing dma interface > > in isa.c then I suggest that we add a simple check in the isa > > dma routine to bypass the busy flag check when we are using > > auto dma. What does this mean in an SMP environment I have no > > right. > > > idea because when a driver requests auto dma in essence he is > > requesting exclusive access of the dma channel. > > In fact I doubt ISA DMA channels can be shared since from the hw point > of view they work as IRQ lines (i.e. active high). It is true that some > peripherals have sw-programmable DMA lines (and IRQ as well) so in > principle one could deactivate (i.e. put in Hi-Z) the DMA line and let > someone else use it, but I doubt any of our driver does that right now. > > As for isa_dmadone, I am under the impression that the function is > overloaded right now, because it serves to call the bounce-buffer code > when necessary, and not just to mark the DMA channel as idle. > > Moreover there are bigger problems with DMA in automode since when you > do a write using bounce buffers you need to invoke isa_dmastart every > time, not just the first one. > > So in the end, I think that our isa_dma routines probably do not work > with auto mode _and_ bounce buffers, indipendently of the checks on the > dma_busy/dma_inuse flags. > > We can temporarily bypass the problem by making the DMA routines fail > if auto mode is requested and a bounce buffer needs to be used for the > channel. Your analisys is good. Whats left now, provided that the rest of the team agrees on your proposed solution, is who is going to write the code and when? And Please post the revised code for peer review. Thank You, Amancio From owner-freebsd-hackers Mon Aug 18 10:03:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03199 for hackers-outgoing; Mon, 18 Aug 1997 10:03:00 -0700 (PDT) Received: from phantasm.scl.ameslab.gov (phantasm.scl.ameslab.gov [147.155.142.74]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA03193 for ; Mon, 18 Aug 1997 10:02:55 -0700 (PDT) Received: (from ccsanady@localhost) by phantasm.scl.ameslab.gov (8.6.12/8.6.12) id RAA02047 for freebsd-hackers@freebsd.org; Mon, 18 Aug 1997 17:02:19 GMT From: "Chris Csanady" Message-Id: <9708181202.ZM2045@phantasm.scl.ameslab.gov> Date: Mon, 18 Aug 1997 12:02:19 -0500 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: freebsd-hackers@freebsd.org Subject: fs's on floppies.. (installing many machines) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I need to install a bunch of FreeBSD boxes and was wondering how I may create a bootable floppy. I thought, hey--this should be no trouble.. but I cannot get it to mount the root filesystem. I basically want to have a floppy capable of writing a partition table, disklabeling, newfsing, and untarring a file over nfs. So.. I created a fs on a floppy, copied a kernel, init and friends, but it hangs after something like "mounting root.." and "configure() finished".. Can anyone tell me what I am doing wrong? Thanks, Chris PS, please leave me cc'd From owner-freebsd-hackers Mon Aug 18 10:03:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03215 for hackers-outgoing; Mon, 18 Aug 1997 10:03:06 -0700 (PDT) Received: from csemail.cropsci.ncsu.edu (csemail.cropsci.ncsu.edu [152.1.88.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA03176 for ; Mon, 18 Aug 1997 10:02:40 -0700 (PDT) From: rdkeys@csemail.cropsci.ncsu.edu Received: by csemail.cropsci.ncsu.edu (5.61-AIX-1.2/1.0) id AA107423 (for freebsd-hackers@freebsd.org, from rdkeys/rdkeys@csemail.cropsci.ncsu.edu); Mon, 18 Aug 97 13:11:16 -0400 Message-Id: <9708181711.AA107423@csemail.cropsci.ncsu.edu> Subject: Thought about the sysinstall scripts...... To: freebsd-hackers@freebsd.org Date: Mon, 18 Aug 1997 13:11:12 -0400 (EDT) Cc: rdkeys@csemail.cropsci.ncsu.edu () X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk During the install, especially from a disk slightly out of date, would it be possible to make the install scripts read the directory entries under FreeBSD's root directory on whichever url the default comes up on and then provide a list of what is there, at that time, to allow the user to select an appropriate install tree, and then, if that is not acceptable, default to current.freebsd.org or releng22.freebsd.org for an alternate. That would get around the problem of old install disks not finding the correct or current source trees, and perhaps save some headaches trying to find the ``right'' url...... Just a thought..... Bob Keys rdkeys@csemail.cropsci.ncsu.edu From owner-freebsd-hackers Mon Aug 18 10:10:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA03694 for hackers-outgoing; Mon, 18 Aug 1997 10:10:06 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03624 for ; Mon, 18 Aug 1997 10:09:27 -0700 (PDT) Received: (from kev@localhost) by lab321.ru (8.8.6/8.8.5) id AAA16357; Tue, 19 Aug 1997 00:09:35 +0700 (OSD) Message-ID: <19970819000935.57291@lab321.ru> Date: Tue, 19 Aug 1997 00:09:35 +0700 From: Eugeny Kuzakov To: freebsd-hackers@freebsd.org Subject: JDK 1.1 for FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All ! Are there anyone succesfully run JDK 1.1 for FreeBSD ? -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 18 11:20:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07569 for hackers-outgoing; Mon, 18 Aug 1997 11:20:34 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07560 for ; Mon, 18 Aug 1997 11:20:27 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA02086; Mon, 18 Aug 1997 12:20:01 -0600 (MDT) Date: Mon, 18 Aug 1997 12:20:01 -0600 (MDT) Message-Id: <199708181820.MAA02086@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mikael Karpberg Cc: hackers@freebsd.org Subject: Re: A bit off topic: GCC 2.8??? In-Reply-To: <199708160900.LAA00307@ocean.campus.luth.se> References: <199708160900.LAA00307@ocean.campus.luth.se> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm interested in using exceptions and other final standard C++ thingies, > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > but is it out there somewhere? Check out the gnu newsgroups on Usenet. Basically, the FSF is getting beat up by some folks who think they should make a release, since templates and exceptions are broken. Even the Cygnus folks are wondering why they don't make a release, since it makes their job harder to synchronize up with the FSF codes. Nate From owner-freebsd-hackers Mon Aug 18 11:30:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA08198 for hackers-outgoing; Mon, 18 Aug 1997 11:30:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08146 for ; Mon, 18 Aug 1997 11:29:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15482; Mon, 18 Aug 1997 11:22:59 -0700 From: Terry Lambert Message-Id: <199708181822.LAA15482@phaeton.artisoft.com> Subject: Re: The low priority items To: hoek@hwcn.org Date: Mon, 18 Aug 1997 11:22:59 -0700 (MST) Cc: kd5ob@theshop.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Tim Vanderhoek" at Aug 17, 97 09:38:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm a little slow. Did I read correctly that Threaded processes are > > not supported? And the next line down from that mentioned something > > of the same, however, can I assume it is to deal with multiprocessor > > CPU boards as well? > > man 3 pthread > > Current thread support isn't optimal, and there are multiple > threading packages to choose from (threads aren't implemented at > the kernel level), but it's there, and it's used. :) Kernel threading is not that big a win, unless it is a hybrid system, or unless you are throwing iron at the problem (in the form of more CPU's). > > systems. I never imagined that this system would have a problem with > > threading. I was hoping that the multiple processor issue would > > have a higher priority than it does. > > Theading really isn't an incredible technological advantage. The > unique ability of UNIX that you're probably thinking of is to run > "multiple processes", not "multiple processors". Kernel threading buys the ability to scale a single mutlithreaded process across multiple CPU's. In other words, it reflects on the SMP scalability of single processes. A typical fault in most kernel threading implementations is that a kernel thread is seen as a context for a blocking call; the user issues blocking calls on kernel threads, and a thread context switch occurs. This is bad, since it means you are not fully utilizing your quantum and you get to eat paging overhead. There are some things you can do about this: thread group affinity, which will preferentially switch to another thread in the same process instead of another process. This plays a bit of hell with CPU affinitiy, and the need to maintain cache coherency in a multiprocessor environment. The best (currently) answer out there is to use cooperative scheduling, where a user space scheduler does call conversion threading (just like pthreads, only hopefully a bit less overhead because of native support). The other advantage of loosely coupling kernel threads (kernel schedulable entities) and blocking calls from user space threads (user work-to-do) is that, unlike traditional SVR4/Solaris kernel to user space thread mappings, when there are more user space threads than kernel space threads, you still don't get starvation. Starvation occurs in SVR4/Solaris when there are user space threads capable of being run., but all kernel threads are handling blocking calls, and therefore there are no kernel threads available to run the user space threads: the quantum was allocated, but the kernel threads foolishly gave it away by blocking. The current pthreads implementation is a pure call-conversion implementation: a blocking call is converted into a non-blocking call and a context switch. Call conversion uses an entirely user space threads scheduler, whose job it is to handle the context switch (which includes stack switching and, on some RISC processors, register window flucshing, etc.). This type of call conversion has limited value because it applies only to system calls which operate on file descriptors, and then only for calls for which a non-blocking causes the call to return incomplete. The other problem with this type of threading is stack allocation; stacks can not grow automatically, they have to be preallocated. An alternative implementation of a call conversion threading package uses AIO (asynchronous I/O). Typically (SunOS 4.1.x liblwp, for instance) these implementations use the additional system calls aioread, aiowrite, aiowait, and aiocancel. This is superior to the non-blocking FD implementation, in that it allows I/O to be interleaved instead of terminated with an EWOULDBLOCK or EAGAIN. It is inferior, in that it only applies to read/write operations. In an ideal call-conversion scenario, there would be an async call gate corresponding to the sync call gate used by normal system calls. To implement this would require a pool of stacks and async request contexts that could be used to maintain all outstanding blocking calls. This is very similar to what VMS has in terms of the context records for ASTs (async system traps), but does not require a callback from the kernel to user space -- a major performance win. You could easily improve this even further by adding a flag value in the sysent structure to indicate calls which could potentially block, and delaying the conversion until a block would occur. This "lazy binding" of contexts would both save you total outstanding contexts at any one time, but in the case of a non-sleep completion, the call could return immediately to the caller, having successfully completed. Since a call context could be serviced on any processor, the normal scheduler interface is sufficient to maximize concurrency (there are minor issues of CPU affinity, which would be handled via cooperative scheduling on "EINPROGRESS" returns...). > Windows programmers often see threads as an absolute necessity > because of the Windows history. UNIX programmers use and > generally prefer fork(), but it's recognized that threads have > their purpose (which is why they're supported :). Windows is, historically, a voluntary preemption model cooperative multitasker. In other words, Windows prior to Windows 95 was a single process system, and all your applications were merely call-conversion based threads within that single process. This is why it's so hard to understand the amount of time it has taken the Wine project to get where it is today. In effect, Windows had loadable kernel modules before everyone, only they were called "Windows applications". Even in Windows 95, if you run legacy applications, you are running in a single process for all old applications. The process itself can be preeempted by Windows 95's preemptive multitasking scheduler, but within the process, preemption is entirely voluntary. The next time you are running a legacy application on Windows 95, type the three fingered salute of "CTRL-ALT-DEL" to get the "Close Program" (Task Manager) window, and look for "Winoldapp"... that's the process. > > >From what I've read this Free BSD seems to support multiple sessions. > > Yet I also read something about DLL's being supported, but I guess > > you can't thread anything. You can. You don't get "process attach" and "thread attach" type event notifications into a main loop in the DLL, however. You can get the equivalent of "process attach/detach" events: these are when the ctors/dtors are called, and you can hook these in a library implementation. The "thread attach/detach" is less meaningful, since objects are not constructed in thread local storage in FreeBSD. Why do you have to call CoCreateFreeThreadedMarshaller() to move COM objects between threads in the same process? The address space is not shared, and threads in Windows 95 are thinly disguised kernel threads. This saves them fixing the stack growth problem the right way (seperate stack segment using page anonymity and guard pages), but it means an obect instanced in one thread is not necessarily in the address space of another thread, even in the same process. This is somewhat masked by the use of "first available kernel thread". Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Aug 18 11:31:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA08262 for hackers-outgoing; Mon, 18 Aug 1997 11:31:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08254 for ; Mon, 18 Aug 1997 11:31:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15497 for hackers@freebsd.org; Mon, 18 Aug 1997 11:24:54 -0700 From: Terry Lambert Message-Id: <199708181824.LAA15497@phaeton.artisoft.com> Subject: Re: More info on slow "rm" times with 2.2.1+ To: hackers@freebsd.org Date: Mon, 18 Aug 1997 11:24:53 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ok - I can buy that - the last block will take longest to delete > (since you have to skip over the previous, un-coalesced, entries...) > > But - I'm not sure that explains why deleting the last 300 files > would have (3*300) 900 seconds with 2.2.1 in this situation, where > it only took 2.1.7 3 seconds. Just from listening to the disk > and watching I/O I can see that 2.2.1 is doing an *awful* lot of > I/O 2.1.7 didn't do... could there be something in this locking? Because the logic in VOP_LOCK is inverted, and you are taking a sleep (mostly) on each delete, which in turn results in a context switch. That's like saying "usleep( 10000);" between each one. The need for it comes from vclean() (which, as I've said before, must die). People think the BSD4.4-Lite2 locking stuff is an improvement; it is, but only from the API perspective. The inverted lock ordering in VOP_LOCK specifically for the vnode reclaimation process is bogus as hell. So is the VOP_ADVLOCK calling needing to be implemented per FS. NFS Server locking requires a delay between local assertion and local coelescing to allow for a failed attempt at remote assertion to trigger a local backout, which can't happen after a coelesce, so this is only going to become more obvious as time goes on. I'm patient... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Aug 18 11:36:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA08654 for hackers-outgoing; Mon, 18 Aug 1997 11:36:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08646 for ; Mon, 18 Aug 1997 11:36:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15516; Mon, 18 Aug 1997 11:27:47 -0700 From: Terry Lambert Message-Id: <199708181827.LAA15516@phaeton.artisoft.com> Subject: Re: "rm" speeds (2.1.7.1 vs. 2.2.1) To: dg@root.com Date: Mon, 18 Aug 1997 11:27:47 -0700 (MST) Cc: ponds!rivers@dg-rtp.dg.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708180204.TAA19951@implode.root.com> from "David Greenman" at Aug 17, 97 07:04:25 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Again, f.y.i. - this is a 486dx66 with 24meg of RAM, a typical IDE > >drive (1+gig)... The 2.2.1 kernel has NBUF defined at 128; to see > >if that's the problem... where the 2.1.7 kernel was from the boot floppy > >off of a 2.1.7 CDROM. > > That is the problem. Take out the NBUF= thing from your kernel config file > and rebuild/install the kernel. A system with 24MB of RAM will have about > 600 buffers if it is allowed to dynamically calculate the amount. > What's happening is that the directory is getting pushed out of the cache, > forcing the system to re-read much of it and the inode blocks each time. I think he will find that at 600 buffers, a 20,000 entry directory will still have that problem (625 directory blocks). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Aug 18 11:46:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA09229 for hackers-outgoing; Mon, 18 Aug 1997 11:46:38 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA09221 for ; Mon, 18 Aug 1997 11:46:31 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id NAA14849; Mon, 18 Aug 1997 13:46:13 -0500 (EST) From: "John S. Dyson" Message-Id: <199708181846.NAA14849@dyson.iquest.net> Subject: Re: The low priority items In-Reply-To: <87u3gnacj5.fsf@phaedrus.uchicago.edu> from stephen farrell at "Aug 18, 97 07:41:50 am" To: sfarrell@healthquiz.com (stephen farrell) Date: Mon, 18 Aug 1997 13:46:13 -0500 (EST) Cc: perlsta@sunyit.edu, freebsd-hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > > last I heard john dyson was writing the package... but i'd be > interested in further status information myself. > The kernel now has full support (if you aren't using SMP), but I challenge anyone to use it (without my "secret" userland code :-)). If anyone wants a copy of the "secret" code to use the kernel threads capability, let me know. :-). There are still rough edges, but it does work. Sorry for the lame humor -- I'll probably put the code on a public site if I get enough requests. Otherwise, I'll put together a package for those who ask... John From owner-freebsd-hackers Mon Aug 18 12:06:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10542 for hackers-outgoing; Mon, 18 Aug 1997 12:06:08 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10537 for ; Mon, 18 Aug 1997 12:06:02 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id OAA14914; Mon, 18 Aug 1997 14:05:41 -0500 (EST) From: "John S. Dyson" Message-Id: <199708181905.OAA14914@dyson.iquest.net> Subject: Re: A bit off topic: GCC 2.8??? In-Reply-To: <199708181820.MAA02086@rocky.mt.sri.com> from Nate Williams at "Aug 18, 97 12:20:01 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 18 Aug 1997 14:05:41 -0500 (EST) Cc: karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > > I'm interested in using exceptions and other final standard C++ thingies, > > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > > but is it out there somewhere? > > Check out the gnu newsgroups on Usenet. Basically, the FSF is getting > beat up by some folks who think they should make a release, since > templates and exceptions are broken. Even the Cygnus folks are > wondering why they don't make a release, since it makes their job harder > to synchronize up with the FSF codes. > The egcs project appears to be a spin-off, and looks like they are moving forward quickly. A contributor has already proposed major improvement to the register allocation (spill) scheme. John From owner-freebsd-hackers Mon Aug 18 12:36:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12844 for hackers-outgoing; Mon, 18 Aug 1997 12:36:10 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA12833 for ; Mon, 18 Aug 1997 12:36:05 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA02545; Mon, 18 Aug 1997 13:35:08 -0600 (MDT) Date: Mon, 18 Aug 1997 13:35:08 -0600 (MDT) Message-Id: <199708181935.NAA02545@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eugeny Kuzakov Cc: freebsd-hackers@freebsd.org Subject: Re: JDK 1.1 for FreeBSD In-Reply-To: <19970819000935.57291@lab321.ru> References: <19970819000935.57291@lab321.ru> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are there anyone succesfully run JDK 1.1 for FreeBSD ? Yes, check out: http://www.csi.uottawa.ca/~kwhite/javaport.html Nate From owner-freebsd-hackers Mon Aug 18 12:39:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13052 for hackers-outgoing; Mon, 18 Aug 1997 12:39:19 -0700 (PDT) Received: from clifford.inch.com (omar@clifford.inch.com [207.240.140.163]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA13028; Mon, 18 Aug 1997 12:39:13 -0700 (PDT) Received: (from omar@localhost) by clifford.inch.com (8.8.5/8.8.5) id PAA02028; Mon, 18 Aug 1997 15:39:58 -0400 Message-ID: <19970818153958.19410@clifford.inch.com> Date: Mon, 18 Aug 1997 15:39:58 -0400 From: Omar Thameen To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Re: ftpd/wu-ftpd: login prompt delay Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.65 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Solution: If we turn off virtual domain support in the Makefile, the login prompt returns right away. It seems that stock ftpd, when compiled with virtual support, must be encountering problmes with nameservice lookups. Perhaps it tries to do some kind of lookup on all the IPs aliased to that machine, or maybe the fact that we don't reverse-resolve the webservers is causing the problem. Omar -----Forwarded message from Omar Thameen ----- We're trying to use the stock ftpd on 2.2 machines running as webservers. Hence, each server has a number of IPs aliased. The problem is, on these 2.2 machines, ftpd takes a long time to return a login prompt, preventing some users from connecting because their software has too short of a timeout. I get the "Connected to domain.com" message immediately, but the login prompt takes a good 20-30 seconds more. It's not a nameservice issue, because if I install the wu-ftpd port (which I'm trying to move away from since ftpd seems to be developing nicely), it returns the login prompt right away. One thing I have found is that on machines that have only one IP, the login prompt returns quickly. It's these webservers with a number of IP aliases that seems to be the problem. Any ideas, advice, or commiseration? Omar -----End of forwarded message----- From owner-freebsd-hackers Mon Aug 18 13:28:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15979 for hackers-outgoing; Mon, 18 Aug 1997 13:28:24 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15918 for ; Mon, 18 Aug 1997 13:27:59 -0700 (PDT) Received: (from kev@localhost) by lab321.ru (8.8.6/8.8.5) id DAA00924; Tue, 19 Aug 1997 03:27:28 +0700 (OSD) Message-ID: <19970819032728.13769@lab321.ru> Date: Tue, 19 Aug 1997 03:27:28 +0700 From: Eugeny Kuzakov To: Nate Williams Cc: freebsd-hackers@freebsd.org Subject: Re: JDK 1.1 for FreeBSD References: <19970819000935.57291@lab321.ru> <199708181935.NAA02545@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708181935.NAA02545@rocky.mt.sri.com>; from Nate Williams on Mon, Aug 18, 1997 at 01:35:08PM -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 01:35:08PM -0600, Nate Williams wrote: > > Are there anyone succesfully run JDK 1.1 for FreeBSD ? > > Yes, check out: > http://www.csi.uottawa.ca/~kwhite/javaport.html I have it. But it's permanently core dumps. I have FreeBSD 2.1.7.1. -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 18 13:30:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16255 for hackers-outgoing; Mon, 18 Aug 1997 13:30:51 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16243 for ; Mon, 18 Aug 1997 13:30:37 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id VAA15501; Mon, 18 Aug 1997 21:30:17 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id VAA05198; Mon, 18 Aug 1997 21:30:17 +0100 (BST) Message-Id: <199708182030.VAA05198@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: grog@lemis.com cc: brian@awfulhak.org (Brian Somers), hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: date(1) In-reply-to: Your message of "Tue, 12 Aug 1997 11:29:55 +0900." <199708120229.LAA00484@papillon.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Aug 1997 21:30:17 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brian Somers writes: > >> The documentation's inadequate. Sure, it points to environ(7), but > >> since TZ is almost never used in BSD, there's a tendency to think > >> it'll be like a System V TZ, which is completely different. How about > >> adding: > >> > >> --- /usr/share/man/man1/date.1.orig Fri Aug 1 04:13:12 1997 > >> +++ /usr/share/man/man1/date.1 Fri Aug 1 14:54:38 1997 > >> @@ -171,6 +171,11 @@ > >> .Bl -tag -width Ds > >> .It Ev TZ > >> The timezone to use when displaying dates. > >> +The normal format is a pathname relative to > >> +.Dq Pa /usr/share/zoneinfo . > >> +For example, the command > >> +.Dq env TZ=America/Los_Angeles date > >> +displays the current time in California. > >> See > >> .Xr environ 7 > >> for more information. > > > > But this is already mentioned in environ(7). > > Sure, that's what I said at the top. But it's not obvious what the > reference to environ(7) is for, and the usage of TZ is different > enough from that of other UNIX systems that many people, myself > included, don't expect it and thus don't look at environ(7). Done (2.2 & current). > Greg -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Aug 18 13:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16334 for hackers-outgoing; Mon, 18 Aug 1997 13:31:36 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16326 for ; Mon, 18 Aug 1997 13:31:34 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id OAA02843; Mon, 18 Aug 1997 14:30:54 -0600 (MDT) Date: Mon, 18 Aug 1997 14:30:54 -0600 (MDT) Message-Id: <199708182030.OAA02843@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eugeny Kuzakov Cc: Nate Williams , freebsd-hackers@freebsd.org Subject: Re: JDK 1.1 for FreeBSD In-Reply-To: <19970819032728.13769@lab321.ru> References: <19970819000935.57291@lab321.ru> <199708181935.NAA02545@rocky.mt.sri.com> <19970819032728.13769@lab321.ru> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Are there anyone succesfully run JDK 1.1 for FreeBSD ? > > > > Yes, check out: > > http://www.csi.uottawa.ca/~kwhite/javaport.html > > I have it. But it's permanently core dumps. > I have FreeBSD 2.1.7.1. It requires FreeBSD 2.2, or at least some of the libraries from there. I don't remember exactly, but I think it's the libg++ shared library (which must be in /usr/lib.) Your best bet is to upgrade to 2.2 if you want to do Java. Nate From owner-freebsd-hackers Mon Aug 18 13:39:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16885 for hackers-outgoing; Mon, 18 Aug 1997 13:39:53 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16859 for ; Mon, 18 Aug 1997 13:39:13 -0700 (PDT) Received: (from kev@localhost) by lab321.ru (8.8.6/8.8.5) id DAA01904; Tue, 19 Aug 1997 03:38:34 +0700 (OSD) Message-ID: <19970819033833.39961@lab321.ru> Date: Tue, 19 Aug 1997 03:38:33 +0700 From: Eugeny Kuzakov To: Nate Williams Cc: freebsd-hackers@freebsd.org Subject: Re: JDK 1.1 for FreeBSD References: <19970819000935.57291@lab321.ru> <199708181935.NAA02545@rocky.mt.sri.com> <19970819032728.13769@lab321.ru> <199708182030.OAA02843@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708182030.OAA02843@rocky.mt.sri.com>; from Nate Williams on Mon, Aug 18, 1997 at 02:30:54PM -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 02:30:54PM -0600, Nate Williams wrote: > > > http://www.csi.uottawa.ca/~kwhite/javaport.html > > I have it. But it's permanently core dumps. > > I have FreeBSD 2.1.7.1. > It requires FreeBSD 2.2, or at least some of the libraries from there. > I don't remember exactly, but I think it's the libg++ shared library > (which must be in /usr/lib.) Can I recompile it under 2.1.7.1 ? -- Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 18 13:43:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17041 for hackers-outgoing; Mon, 18 Aug 1997 13:43:03 -0700 (PDT) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17036 for ; Mon, 18 Aug 1997 13:42:53 -0700 (PDT) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Mon, 18 Aug 1997 15:42:52 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freebsd.org'" Subject: help with CCD configuration, I need: Date: Mon, 18 Aug 1997 15:42:48 -0500 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 X-Loop: FreeBSD.org Precedence: bulk This is the issue: su-2.00# ccdconfig ccd0c 32 0 sd4s1b sd5s1b sd6s1b sd7s1b ccdconfig: open: /dev/ccd0c: No such file or directory su-2.00# ./MAKEDEV ccd0 su-2.00# ls ccd* ccd0a ccd0b ccd0c ccd0d ccd0e ccd0f ccd0g ccd0h su-2.00# ccdconfig ccd0c 32 0 sd4s1b sd5s1b sd6s1b sd7s1b ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Device not configured su-2.00# strings /kernel | grep ccd | grep ___ ___pseudo-device ccd 4 su-2.00# What am I missing ? This is under a fresh installation of 2.2.2-RELEASE. Thanks. From owner-freebsd-hackers Mon Aug 18 13:44:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17132 for hackers-outgoing; Mon, 18 Aug 1997 13:44:16 -0700 (PDT) Received: from folco.lms.ru (folco.lms.ru [193.125.142.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17112 for ; Mon, 18 Aug 1997 13:44:08 -0700 (PDT) Received: from minas-tirith.lms.ru (uucp@localhost) by folco.lms.ru (8.8.5/8.6.9) with UUCP id AAA00451 for FreeBSD.ORG!freebsd-hackers; Tue, 19 Aug 1997 00:44:03 +0400 (MSD) Received: (from uucp@localhost) by minas-tirith.lms.ru (8.8.6/8.6.9) with UUCP id XAA02933; Mon, 18 Aug 1997 23:07:29 +0400 (MSD) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by folco.lms.ru (8.8.5/8.6.9) with ESMTP id LAA19947; Mon, 18 Aug 1997 11:11:03 +0400 (MSD) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with ESMTP id OAA07312; Mon, 18 Aug 1997 14:11:10 +0700 (OSD) Date: Mon, 18 Aug 1997 14:11:10 +0700 (OSD) From: Eugeny Kuzakov To: Alex Povolotsky cc: Wolfgang Helbig , FreeBSD.ORG!freebsd-hackers@minas-tirith.lms.ru Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: <199708160544.JAA28399@minas-tirith.lms.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Alex Povolotsky wrote: > <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de>Wolfgang Helbig writes: > > >So you might have to upgrade to FreeBSD 2.2.x to make ppp-2.3.[01] compile. > ppp-2.3.1 I've downloaded several days ago complaints on 2.2.2. It is configured ONLY for 2.1.X. Where can I get patches for it? I have succesfully installed and works ppp-2.3b3 on 2.1.7.1. But I have some problems with compile ppp-2.3.1 on 2.1.7.1. Is beta of ppp better release ? Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 18 14:24:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA19226 for hackers-outgoing; Mon, 18 Aug 1997 14:24:45 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA19094 for ; Mon, 18 Aug 1997 14:21:37 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with ESMTP id EAA05277; Tue, 19 Aug 1997 04:19:49 +0700 (OSD) Date: Tue, 19 Aug 1997 04:19:49 +0700 (OSD) From: Eugeny Kuzakov To: Raul Zighelboim cc: "'hackers@freebsd.org'" Subject: Re: help with CCD configuration, I need: In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, Raul Zighelboim wrote: > su-2.00# ./MAKEDEV ccd0 > su-2.00# ls ccd* > ccd0a ccd0b ccd0c ccd0d ccd0e ccd0f ccd0g ccd0h > su-2.00# ccdconfig ccd0c 32 0 sd4s1b sd5s1b sd6s1b sd7s1b > ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Device not configured I am not shre, but I think you should run: ccdconfig ccd0 32 0 sd4s1b sd5s1b sd6s1b sd7s1b ^^^^ - it is exactly ! disklabel -e ccd0 newfs /dev/ccd0c mount /dev/ccd0c /mount_point Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 18 14:44:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20053 for hackers-outgoing; Mon, 18 Aug 1997 14:44:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA20026 for ; Mon, 18 Aug 1997 14:44:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA08982; Mon, 18 Aug 1997 23:44:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id XAA16111; Mon, 18 Aug 1997 23:16:16 +0200 (MET DST) Message-ID: <19970818231616.HO04222@uriah.heep.sax.de> Date: Mon, 18 Aug 1997 23:16:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: ccsanady@scl.ameslab.gov (Chris Csanady) Subject: Re: fs's on floppies.. (installing many machines) References: <9708181202.ZM2045@phantasm.scl.ameslab.gov> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9708181202.ZM2045@phantasm.scl.ameslab.gov>; from Chris Csanady on Aug 18, 1997 12:02:19 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chris Csanady wrote: > So.. I created a fs on a floppy, copied a kernel, init and friends, > but it hangs after something like "mounting root.." and > "configure() finished".. > > Can anyone tell me what I am doing wrong? But you did have a /dev/console on it, too, didn't you? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Aug 18 14:50:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20406 for hackers-outgoing; Mon, 18 Aug 1997 14:50:15 -0700 (PDT) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20400 for ; Mon, 18 Aug 1997 14:50:10 -0700 (PDT) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Mon, 18 Aug 1997 16:50:09 -0500 Message-ID: From: Raul Zighelboim To: "'Eugeny Kuzakov'" Cc: "'hackers@freebsd.org'" Subject: RE: help with CCD configuration, I need: Date: Mon, 18 Aug 1997 16:50:07 -0500 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 X-Loop: FreeBSD.org Precedence: bulk > On Mon, 18 Aug 1997, Raul Zighelboim wrote: > > su-2.00# ./MAKEDEV ccd0 > > su-2.00# ls ccd* > > ccd0a ccd0b ccd0c ccd0d ccd0e ccd0f ccd0g ccd0h > > su-2.00# ccdconfig ccd0c 32 0 sd4s1b sd5s1b sd6s1b sd7s1b > > ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Device not configured > > I am not shre, but I think you should run: > ccdconfig ccd0 32 0 sd4s1b sd5s1b sd6s1b sd7s1b > ^^^^ - it is exactly ! > [RSZ] I tried ccd0c and ccd0..... I managed to get (somehow???) ccd1 to work. I still need to make a few other ccds.... ccdconfig ccd1 32 0 sd4s1b sd5s1b worked, while ccdconfif ccd0 32 0 sd4s1b sd5s1b will not !!!!! From owner-freebsd-hackers Mon Aug 18 14:59:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20723 for hackers-outgoing; Mon, 18 Aug 1997 14:59:00 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20716; Mon, 18 Aug 1997 14:58:54 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03256; Mon, 18 Aug 1997 15:58:50 -0600 (MDT) Date: Mon, 18 Aug 1997 15:58:50 -0600 (MDT) Message-Id: <199708182158.PAA03256@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <33F869F3.446B9B3D@FreeBSD.org> References: <33F869F3.446B9B3D@FreeBSD.org> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmm - any comments, ld hackers? > > The freeBSD dlsym() is - as far as I know - the only dlsym() > implementation that doesn't search for _funktion() ... Here's a quick and dirty patch that implements it. I tested it locally w/out any problems, but it has lots of possible problems. 1) If fails to prepend another underscore if the symbol already is underscored. 2) I haven't tested it enough on the entire system. 3) It might not be the correct solution. > I also complained about dlopen() not searching LD_LIBRARY_PATH. I didn't even attempt to look at this. Nate From owner-freebsd-hackers Mon Aug 18 15:30:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22214 for hackers-outgoing; Mon, 18 Aug 1997 15:30:29 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22194; Mon, 18 Aug 1997 15:30:20 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id SAA04176; Mon, 18 Aug 1997 18:29:33 -0400 (EDT) Date: Mon, 18 Aug 1997 18:29:32 -0400 (EDT) From: Brian Mitchell To: Nate Williams cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708182158.PAA03256@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, Nate Williams wrote: > > Hmmm - any comments, ld hackers? > > > > The freeBSD dlsym() is - as far as I know - the only dlsym() > > implementation that doesn't search for _funktion() ... > > Here's a quick and dirty patch that implements it. I tested it locally > w/out any problems, but it has lots of possible problems. openbsd's is another that does not look for underscores. freebsd's has a few other minor holes too. If you dlsym() a nonexistant symbol, freebsd (in 2.2.1 atleast) returns a NULL pointer but does not (as it should) set the dlerror() errorcode. > > 1) If fails to prepend another underscore if the symbol already is > underscored. > 2) I haven't tested it enough on the entire system. > 3) It might not be the correct solution. > > > I also complained about dlopen() not searching LD_LIBRARY_PATH. > > I didn't even attempt to look at this. > > > Nate > From owner-freebsd-hackers Mon Aug 18 15:38:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22674 for hackers-outgoing; Mon, 18 Aug 1997 15:38:46 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22668; Mon, 18 Aug 1997 15:38:41 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA03400; Mon, 18 Aug 1997 16:38:30 -0600 (MDT) Date: Mon, 18 Aug 1997 16:38:30 -0600 (MDT) Message-Id: <199708182238.QAA03400@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Mitchell Cc: Nate Williams , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: References: <199708182158.PAA03256@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > Hmmm - any comments, ld hackers? > > > > > > The freeBSD dlsym() is - as far as I know - the only dlsym() > > > implementation that doesn't search for _funktion() ... > > > > Here's a quick and dirty patch that implements it. I tested it locally > > w/out any problems, but it has lots of possible problems. > > openbsd's is another that does not look for underscores. freebsd's has a > few other minor holes too. If you dlsym() a nonexistant symbol, freebsd > (in 2.2.1 atleast) returns a NULL pointer but does not (as it should) set > the dlerror() errorcode. Umm, yes it does. At least, it does in the version in 2.2. >From ld/rtld/rtld.c: if (np == NULL) { generror("Undefined symbol"); return NULL; generror sets the dlerror() error string. I'm working on a better fix than I sent out now, but it's not as easy as it could be due to the way the code is laid out. Nate From owner-freebsd-hackers Mon Aug 18 15:46:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22975 for hackers-outgoing; Mon, 18 Aug 1997 15:46:39 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22964 for ; Mon, 18 Aug 1997 15:46:32 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id PAA04812 for ; Mon, 18 Aug 1997 15:46:31 -0700 (PDT) Message-Id: <199708182246.PAA04812@austin.polstra.com> To: hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <33F869F3.446B9B3D@FreeBSD.org> References: <33F869F3.446B9B3D@FreeBSD.org> Organization: Polstra & Co., Seattle, WA Date: Mon, 18 Aug 1997 15:46:31 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmmm - any comments, ld hackers? I didn't see it in the newsgroup until Joerg brought it to my attention today. (I don't follow the newsgroups, since I already have all the FREE XXX SEX SITE PASSWORDS and FANTASTIC MEGA-INCOME OPPORTUNITIES that I need at the moment.) I agree that it's a bug, and I followed up there saying I planned to fix it. One fix would be switching to ELF, of course ... ;-) I think the fix should assume that the application most likely wants to look up a normal C symbol. So it should do something like this: /* * First try: look for a normal C symbol like (in assembly * language) "_foo". */ if (sym starts with "_") /* Assume caller already added "_" */ trysym = sym; else /* Add "_" for caller */ trysym = concat("_", sym); /* Not C, but you get the idea */ if (lookup(trysym)) return success; /* * Second try: look for a strange C symbol like (in assembly * language) "__foo", or an assembly language symbol "foo" with no * underscore at all. */ if (sym starts with "_") /* Assume C symbol really starts with "_" */ trysym = concat("_", sym); else /* Assume caller wants assembly symbol */ trysym = sym; if (lookup(trysym)) return success; /* * Give up. */ return failure; No matter what heuristic is used, it could do the wrong thing in some cases. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Aug 18 15:50:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23266 for hackers-outgoing; Mon, 18 Aug 1997 15:50:54 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23261; Mon, 18 Aug 1997 15:50:47 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA03442; Mon, 18 Aug 1997 16:50:44 -0600 (MDT) Date: Mon, 18 Aug 1997 16:50:44 -0600 (MDT) Message-Id: <199708182250.QAA03442@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708182158.PAA03256@rocky.mt.sri.com> References: <33F869F3.446B9B3D@FreeBSD.org> <199708182158.PAA03256@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > > The freeBSD dlsym() is - as far as I know - the only dlsym() > > implementation that doesn't search for _funktion() ... > > Here's a quick and dirty patch that implements it. I tested it locally > w/out any problems, but it has lots of possible problems. > > 1) If fails to prepend another underscore if the symbol already is > underscored. > 2) I haven't tested it enough on the entire system. > 3) It might not be the correct solution. > I didn't even send out the original patch, but in any case here's the next version of it, which avoids problem 1 above. Again, it's been lightly tested, but seems to work. The patch is against 2.2-stable. Nate ---------- =================================================================== RCS file: /home/CVS/src/gnu/usr.bin/ld/rtld/rtld.c,v retrieving revision 1.40.2.3 diff -c -r1.40.2.3 rtld.c *** rtld.c 1997/08/08 02:18:14 1.40.2.3 --- rtld.c 1997/08/18 22:48:58 *************** *** 1916,1922 **** } static void * ! __dlsym3(fd, sym, retaddr) void *fd; char *sym; void *retaddr; --- 1916,1922 ---- } static void * ! __resolvesym_(fd, sym, retaddr) void *fd; char *sym; void *retaddr; *************** *** 1973,1978 **** --- 1973,2002 ---- addr += (long)src_map->som_addr; return (void *)addr; + } + + static void * + __dlsym3(fd, sym, retaddr) + void *fd; + char *sym; + void *retaddr; + { + void *result; + + result = __resolvesym_(fd, sym, retaddr); + /* + * XXX - Ugly, but it makes the least impact on the run-time loader + * sources. + */ + if (result == NULL && !strcmp(dlerror_msg, "Undefined symbol")) { + /* Prepend an underscore and try again */ + char *newsym = malloc(strlen(sym) + 1); + + newsym[0] = '_'; + strcpy(&newsym[1], sym); + result = __resolvesym_(fd, newsym, retaddr); + } + return result; } static char * Index: rtld.c From owner-freebsd-hackers Mon Aug 18 16:41:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25529 for hackers-outgoing; Mon, 18 Aug 1997 16:41:46 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25508; Mon, 18 Aug 1997 16:41:40 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA03607; Mon, 18 Aug 1997 17:41:37 -0600 (MDT) Date: Mon, 18 Aug 1997 17:41:37 -0600 (MDT) Message-Id: <199708182341.RAA03607@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nate Williams Cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708182250.QAA03442@rocky.mt.sri.com> References: <33F869F3.446B9B3D@FreeBSD.org> <199708182158.PAA03256@rocky.mt.sri.com> <199708182250.QAA03442@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > The freeBSD dlsym() is - as far as I know - the only dlsym() > > > implementation that doesn't search for _funktion() ... > I didn't even send out the original patch, but in any case here's the > next version of it.. Which leaks memory, and doesn't allocate room enough for the new string. Thanks to sef for pointing it out, here's the new and improved patch, which allocates enough memory and frees it as well. :) Nate ------- Index: rtld.c =================================================================== RCS file: /home/CVS/src/gnu/usr.bin/ld/rtld/rtld.c,v retrieving revision 1.40.2.3 diff -c -r1.40.2.3 rtld.c *** rtld.c 1997/08/08 02:18:14 1.40.2.3 --- rtld.c 1997/08/18 23:39:28 *************** *** 1916,1922 **** } static void * ! __dlsym3(fd, sym, retaddr) void *fd; char *sym; void *retaddr; --- 1916,1922 ---- } static void * ! __resolvesym_(fd, sym, retaddr) void *fd; char *sym; void *retaddr; *************** *** 1973,1978 **** --- 1973,2003 ---- addr += (long)src_map->som_addr; return (void *)addr; + } + + static void * + __dlsym3(fd, sym, retaddr) + void *fd; + char *sym; + void *retaddr; + { + void *result; + + result = __resolvesym_(fd, sym, retaddr); + /* + * XXX - Ugly, but it makes the least impact on the run-time loader + * sources. + */ + if (result == NULL && !strcmp(dlerror_msg, "Undefined symbol")) { + /* Prepend an underscore and try again */ + char *newsym = malloc(strlen(sym) + 2); + + newsym[0] = '_'; + strcpy(&newsym[1], sym); + result = __resolvesym_(fd, newsym, retaddr); + free(newsym); + } + return result; } static char * From owner-freebsd-hackers Mon Aug 18 16:51:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25920 for hackers-outgoing; Mon, 18 Aug 1997 16:51:33 -0700 (PDT) Received: from sarah.asstdc.com.au (root@sarah.asstdc.com.au [202.12.127.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25914 for ; Mon, 18 Aug 1997 16:51:30 -0700 (PDT) Received: from walkabout.asstdc.com.au (ts75ip72.cadvision.com [207.228.113.72]) by sarah.asstdc.com.au (8.8.5/BSD4.4) with ESMTP id JAA12452 Tue, 19 Aug 1997 09:51:16 +1000 (EST) Message-Id: <199708182351.JAA12452@sarah.asstdc.com.au> From: "Michael Butler" To: "Joerg Wunsch" Cc: Subject: Re: dead disk Date: Mon, 18 Aug 1997 17:51:13 -0600 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1162 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 > > csi:1,79,7,3b asc:16,0 Data synchronization mark error > > field replaceable unit: 15 > > So is all hope lost for this disk? > Did you turn on automatic error recovery? It's on mode page 1 (see > scsi(8)). Unfortunately, I have a drive at home that desparately needs reformatting .. worse, the machine is in Australia and I'm in Canada for the short and medium term .. .. can anyone tell me what commands I can throw at scsi(8) to do this? michael From owner-freebsd-hackers Mon Aug 18 17:02:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26468 for hackers-outgoing; Mon, 18 Aug 1997 17:02:39 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26461 for ; Mon, 18 Aug 1997 17:02:33 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA25758 for ; Mon, 18 Aug 1997 17:02:31 -0700 (PDT) Date: Mon, 18 Aug 1997 17:02:27 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: DPT problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmm, just upgraded to a fairly recent 2.2.2-stable, and DPT patch 1.2.0, however, now I can't boot my box anymore, I keep getting: dpt0: Test unit Ready, but controller shutdown... PM3334UW, 64MB RAM, 5 4GB barracuda's, in a digital P6-200. From owner-freebsd-hackers Mon Aug 18 17:24:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27578 for hackers-outgoing; Mon, 18 Aug 1997 17:24:27 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27571 for ; Mon, 18 Aug 1997 17:24:23 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id KAA23462; Tue, 19 Aug 1997 10:23:45 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id JAA12838; Tue, 19 Aug 1997 09:53:45 +0930 (CST) Message-ID: <19970819095344.28357@lemis.com> Date: Tue, 19 Aug 1997 09:53:44 +0930 From: Greg Lehey To: Michael Butler Cc: Joerg Wunsch , freebsd-hackers@FreeBSD.ORG Subject: Re: dead disk References: <199708182351.JAA12452@sarah.asstdc.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708182351.JAA12452@sarah.asstdc.com.au>; from Michael Butler on Mon, Aug 18, 1997 at 05:51:13PM -0600 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 05:51:13PM -0600, Michael Butler wrote: >>> Aug 18 04:34:59 scorn /kernel: sd3(ahc0:3:0): MEDIUM ERROR info:0x50033 >>> csi:1,79,7,3b asc:16,0 Data synchronization mark error >>> field replaceable unit: 15 > >>> So is all hope lost for this disk? > >> Did you turn on automatic error recovery? It's on mode page 1 (see >> scsi(8)). > > Unfortunately, I have a drive at home that desparately needs reformatting .. > worse, the machine is in Australia and I'm in Canada for the short and medium > term .. .. can anyone tell me what commands I can throw at scsi(8) to do > this? If you just want to format the disk, scsiformat(8) will do that. Somebody posted the commands yesterday to turn on error recovery. Greg From owner-freebsd-hackers Mon Aug 18 18:30:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA00553 for hackers-outgoing; Mon, 18 Aug 1997 18:30:39 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA00548; Mon, 18 Aug 1997 18:30:33 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA15154; Tue, 19 Aug 1997 10:57:59 +0930 (CST) From: Michael Smith Message-Id: <199708190127.KAA15154@genesis.atrad.adelaide.edu.au> Subject: Re: isa_dmastatus In-Reply-To: <199708180723.AAA00439@rah.star-gate.com> from Amancio Hasty at "Aug 18, 97 00:23:44 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 19 Aug 1997 10:57:59 +0930 (CST) Cc: luigi@labinfo.iet.unipi.it, smp@csn.net, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty stands accused of saying: > > When we get a dma interrupt from the device, if I call isa_dmadone to > clear the busy flag it does not mean that I am done using the > buffer and I can't call isa_dmastart because the dma processes > is still active. OK. > So if we wish to support auto dma and use the existing dma interface > in isa.c then I suggest that we add a simple check in the isa > dma routine to bypass the busy flag check when we are using > auto dma. What does this mean in an SMP environment I have no > idea because when a driver requests auto dma in essence he is > requesting exclusive access of the dma channel. It sounds like you're just adding hairs to an existing wart. This may well be the most expedient way to go in the short term though. > Please let me know if my explanation is not clear and if there > are any intentions to support auto dma in the isa.c / *dma* routines. It sounds to me as though there is a need for a couple of different levels of access to the DMA support. At the bottom, we need some primitives : isa_dmaacquire - obtain a DMA channel isa_dmarelease - release a DMA channel isa_dmastart - start a DMA transfer isa_dmastop - stop a DMA transfer isa_dmastatus - query DMA status which provide hands-on access to the DMA hardware. Above these, it seems that DMA consumers would benefit from isa_dmatransact - start one-shot DMA transaction isa_dmatransstatus - query/complete DMA transaction where the first would take assorted parameters (address, port, direction, channel etc.), and then use the primitives to obtain the channel and start the transaction, and the second would allow for polling the status of a DMA transaction (instead of sleeping for it to finish, etg.). For auto-DMA operation, you would acquire the DMA channel, and then use the other isa_dma* functions until done, at which point you would release the channel again. It seems to me that this is the critical point; the current mixing of the acquire/release with the start/done functionality is breaking your use of auto DMA, correct? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Aug 18 18:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA00993 for hackers-outgoing; Mon, 18 Aug 1997 18:40:54 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA00988 for ; Mon, 18 Aug 1997 18:40:51 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id SAA22408; Mon, 18 Aug 1997 18:40:57 -0700 (PDT) To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-reply-to: Your message of "Mon, 18 Aug 1997 15:46:31 PDT." <199708182246.PAA04812@austin.polstra.com> Date: Mon, 18 Aug 1997 18:40:57 -0700 Message-ID: <22405.871954857@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I agree that it's a bug, and I followed up there saying I planned to > fix it. One fix would be switching to ELF, of course ... ;-) Well, let's do it then. :) Jordan From owner-freebsd-hackers Mon Aug 18 18:41:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA01048 for hackers-outgoing; Mon, 18 Aug 1997 18:41:23 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA01034; Mon, 18 Aug 1997 18:41:18 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id SAA06127; Mon, 18 Aug 1997 18:41:02 -0700 (PDT) Message-Id: <199708190141.SAA06127@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Michael Smith cc: luigi@labinfo.iet.unipi.it, smp@csn.net, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: isa_dmastatus In-reply-to: Your message of "Tue, 19 Aug 1997 10:57:59 +0930." <199708190127.KAA15154@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Aug 1997 18:41:02 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Michael Smith : > Amancio Hasty stands accused of saying: > > > > When we get a dma interrupt from the device, if I call isa_dmadone to > > clear the busy flag it does not mean that I am done using the > > buffer and I can't call isa_dmastart because the dma processes > > is still active. > > OK. > > > So if we wish to support auto dma and use the existing dma interface > > in isa.c then I suggest that we add a simple check in the isa > > dma routine to bypass the busy flag check when we are using > > auto dma. What does this mean in an SMP environment I have no > > idea because when a driver requests auto dma in essence he is > > requesting exclusive access of the dma channel. > > It sounds like you're just adding hairs to an existing wart. This may > well be the most expedient way to go in the short term though. > > > Please let me know if my explanation is not clear and if there > > are any intentions to support auto dma in the isa.c / *dma* routines. > > It sounds to me as though there is a need for a couple of different > levels of access to the DMA support. At the bottom, we need some > primitives : > > isa_dmaacquire - obtain a DMA channel > isa_dmarelease - release a DMA channel > isa_dmastart - start a DMA transfer > isa_dmastop - stop a DMA transfer > isa_dmastatus - query DMA status > > which provide hands-on access to the DMA hardware. Above these, it seems > that DMA consumers would benefit from > > isa_dmatransact - start one-shot DMA transaction > isa_dmatransstatus - query/complete DMA transaction > > where the first would take assorted parameters (address, port, direction, > channel etc.), and then use the primitives to obtain the channel and start > the transaction, and the second would allow for polling the status of a > DMA transaction (instead of sleeping for it to finish, etg.). > > For auto-DMA operation, you would acquire the DMA channel, and then > use the other isa_dma* functions until done, at which point you would > release the channel again. It seems to me that this is the critical > point; the current mixing of the acquire/release with the start/done > functionality is breaking your use of auto DMA, correct? This is correct. there is no mechanism for me to use auto dma with isa_dmadone, isa_dmastatus or isa_dmastop . I can only call isa_dmadone when the driver is done using the dma channel. However, I do need to use isa_dmastatus and possibly isa_dmastop while I am doing auto dma. Amancio From owner-freebsd-hackers Mon Aug 18 19:12:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02506 for hackers-outgoing; Mon, 18 Aug 1997 19:12:48 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02499 for ; Mon, 18 Aug 1997 19:12:41 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id TAA06345; Mon, 18 Aug 1997 19:11:41 -0700 (PDT) Message-Id: <199708190211.TAA06345@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: nate@mt.sri.com (Nate Williams), karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG Subject: Re: A bit off topic: GCC 2.8??? In-reply-to: Your message of "Mon, 18 Aug 1997 14:05:41 CDT." <199708181905.OAA14914@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Aug 1997 19:11:40 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Went hunting for egcs and found it at: http://www.cygnus.com/egcs/ Enjoy, Amancio >From The Desk Of "John S. Dyson" : > > > I'm interested in using exceptions and other final standard C++ thingies, > > > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD ye t, > > > but is it out there somewhere? > > > > Check out the gnu newsgroups on Usenet. Basically, the FSF is getting > > beat up by some folks who think they should make a release, since > > templates and exceptions are broken. Even the Cygnus folks are > > wondering why they don't make a release, since it makes their job harder > > to synchronize up with the FSF codes. > > > The egcs project appears to be a spin-off, and looks like they are moving > forward quickly. A contributor has already proposed major improvement to the > register allocation (spill) scheme. > > John > From owner-freebsd-hackers Mon Aug 18 19:55:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04260 for hackers-outgoing; Mon, 18 Aug 1997 19:55:23 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04254 for ; Mon, 18 Aug 1997 19:55:20 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id TAA06175; Mon, 18 Aug 1997 19:55:10 -0700 (PDT) Message-Id: <199708190255.TAA06175@austin.polstra.com> To: brian@firehouse.net Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Mon, 18 Aug 1997 19:55:10 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Brian Mitchell wrote: > If you dlsym() a nonexistant symbol, freebsd (in 2.2.1 atleast) > returns a NULL pointer but does not (as it should) set the dlerror() > errorcode. Yes, that's a bug that I just discovered and fixed in a commit to -current on August 2nd. I merged it into the -2.2 branch on August 8th. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Aug 18 19:58:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04403 for hackers-outgoing; Mon, 18 Aug 1997 19:58:04 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04396 for ; Mon, 18 Aug 1997 19:58:00 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id TAA06199; Mon, 18 Aug 1997 19:57:55 -0700 (PDT) Message-Id: <199708190257.TAA06199@austin.polstra.com> To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-reply-to: Your message of "Mon, 18 Aug 1997 18:40:57 PDT." <22405.871954857@time.cdrom.com> Date: Mon, 18 Aug 1997 19:57:55 -0700 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I agree that it's a bug, and I followed up there saying I planned to > > fix it. One fix would be switching to ELF, of course ... ;-) > > Well, let's do it then. :) OK, will do. I'm sure glad that got settled so easily! ;-) [He ducks back into his burrow and stays there, for his own protection.] -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Aug 18 20:29:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05681 for hackers-outgoing; Mon, 18 Aug 1997 20:29:54 -0700 (PDT) Received: from gaia.coppe.ufrj.br (jonny@cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05676 for ; Mon, 18 Aug 1997 20:29:52 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.7/8.8.6) id AAA09885; Tue, 19 Aug 1997 00:29:37 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199708190329.AAA09885@gaia.coppe.ufrj.br> Subject: Re: releng22.freebsd.org ftp In-Reply-To: <6242.871674147@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 15, 97 12:42:27 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 19 Aug 1997 00:29:37 -0300 (EST) Cc: jwb@ulysses.homer.att.com, freebsd-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 X-Loop: FreeBSD.org Precedence: bulk #define quoting(Jordan K. Hubbard) // > Dumb question 724: Is there some specific reason why the // > ftp service on releng22.freebsd.org doesn't allow one to: // > // > get 2.2-970814-RELENG.tar // // That is a feature of wu-ftpd. releng22.freebsd.org is running // the stock FreeBSD ftpd and probably won't change anytime soon. But ftp.cdrom.com does not use wu-ftpd and supports this. Are these DG's private patches ? Any chance of these getting integrated to the stock ftp in FreeBSD ? Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-hackers Mon Aug 18 20:43:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06196 for hackers-outgoing; Mon, 18 Aug 1997 20:43:23 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA06168 for ; Mon, 18 Aug 1997 20:41:56 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA15661; Mon, 18 Aug 1997 23:40:23 -0400 Date: Mon, 18 Aug 1997 23:40:21 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: John Polstra cc: "Jordan K. Hubbard" , hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708190257.TAA06199@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, John Polstra wrote: > > > I agree that it's a bug, and I followed up there saying I planned to > > > fix it. One fix would be switching to ELF, of course ... ;-) > > > > Well, let's do it then. :) Yeah! Great! > > OK, will do. I'm sure glad that got settled so easily! ;-) > > [He ducks back into his burrow and stays there, for his own > protection.] > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Aug 18 21:00:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06987 for hackers-outgoing; Mon, 18 Aug 1997 21:00:11 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06980 for ; Mon, 18 Aug 1997 21:00:03 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.6) id NAA25715 for freebsd-hackers@freebsd.org; Tue, 19 Aug 1997 13:59:58 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id OAA01354; Tue, 19 Aug 1997 14:00:48 +1000 (EST) Message-Id: <199708190400.OAA01354@ogre.dtir.qld.gov.au> To: freebsd-hackers@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: isa_dmastatus References: <199708190127.KAA15154@genesis.atrad.adelaide.edu.au> In-Reply-To: <199708190127.KAA15154@genesis.atrad.adelaide.edu.au> from Michael Smith at "Tue, 19 Aug 1997 01:27:59 +0000" Date: Tue, 19 Aug 1997 14:00:47 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, 19th August 1997, Michael Smith wrote: >Amancio Hasty stands accused of saying: >> So if we wish to support auto dma and use the existing dma interface >> in isa.c then I suggest that we add a simple check in the isa >> dma routine to bypass the busy flag check when we are using >> auto dma. > >It sounds like you're just adding hairs to an existing wart. This may >well be the most expedient way to go in the short term though. To be more specific, this seems like the way to go for 2.2.5. For -current, we can be more flamboyant. >It sounds to me as though there is a need for a couple of different >levels of access to the DMA support. At the bottom, we need some >primitives : > >isa_dmaacquire - obtain a DMA channel >isa_dmarelease - release a DMA channel >isa_dmastart - start a DMA transfer >isa_dmastop - stop a DMA transfer >isa_dmastatus - query DMA status Looks like a good start. Can we please have more underscores? Like isa_dma_status? These look lopsided. >which provide hands-on access to the DMA hardware. Above these, it seems >that DMA consumers would benefit from > >isa_dmatransact - start one-shot DMA transaction >isa_dmatransstatus - query/complete DMA transaction > >where the first would take assorted parameters (address, port, direction, >channel etc.), and then use the primitives to obtain the channel and start >the transaction, and the second would allow for polling the status of a >DMA transaction (instead of sleeping for it to finish, etg.). Since the DMA channels are not shareable (please correct me if wrong), there seems no point in combining acquiring a channel with any other operation. Then there's not much point in having isa_dma_transact. I think we should continue directly using routines very much like we have now, but clear up the difficulties with concepts like bounce buffering and auto DMA by adding a few more routines, or at least some more flags. Stephen. From owner-freebsd-hackers Mon Aug 18 21:04:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07175 for hackers-outgoing; Mon, 18 Aug 1997 21:04:15 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07158 for ; Mon, 18 Aug 1997 21:04:08 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id VAA29776; Mon, 18 Aug 1997 21:04:09 -0700 (PDT) Date: Mon, 18 Aug 1997 21:04:09 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199708190404.VAA29776@kithrup.com> To: hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <22405.871954857.kithrup.freebsd.hackers@time.cdrom.com> Jordan writes: >> I agree that it's a bug, and I followed up there saying I planned to >> fix it. One fix would be switching to ELF, of course ... ;-) >Well, let's do it then. :) I think Jordan is letting the cats type again. From owner-freebsd-hackers Mon Aug 18 21:30:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA08524 for hackers-outgoing; Mon, 18 Aug 1997 21:30:51 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA08519 for ; Mon, 18 Aug 1997 21:30:46 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id OAA02397; Tue, 19 Aug 1997 14:30:11 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id OAA14694; Tue, 19 Aug 1997 14:00:10 +0930 (CST) Message-ID: <19970819140010.04999@lemis.com> Date: Tue, 19 Aug 1997 14:00:10 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <199708182246.PAA04812@austin.polstra.com> <22405.871954857@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <22405.871954857@time.cdrom.com>; from Jordan K. Hubbard on Mon, Aug 18, 1997 at 06:40:57PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 06:40:57PM -0700, Jordan K. Hubbard wrote: >> I agree that it's a bug, and I followed up there saying I planned to >> fix it. One fix would be switching to ELF, of course ... ;-) > > Well, let's do it then. :) On a more serious note, since BSDI has now switched to ELF, aren't we going to have to do so anyway? Greg From owner-freebsd-hackers Mon Aug 18 21:59:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10369 for hackers-outgoing; Mon, 18 Aug 1997 21:59:52 -0700 (PDT) Received: from ra.bpsi.net (ra.bpsi.net [199.199.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10364 for ; Mon, 18 Aug 1997 21:59:49 -0700 (PDT) Received: from localhost (duccini@localhost) by ra.bpsi.net (8.8.5/8.6.9) with SMTP id AAA12444 for ; Tue, 19 Aug 1997 00:00:03 -0500 (CDT) Date: Tue, 19 Aug 1997 00:00:02 -0500 (CDT) From: "David V. Duccini" To: hackers@freebsd.org Subject: replacement files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk can someone be so kind as to point me to an ftp site, or email me copies of: ld.so: warning: /usr/X11R6/lib/libXext.so.6.0: minor version 0 older than expected 3, using it anyway ld.so: warning: /usr/X11R6/lib/libX11.so.6.0: minor version 0 older than expected 1, using it anyway I tried updating my ghostscript, and then foolishly removed it, and am trying to get back to my "baseline" thanks! ------------------------------------------------------------------------------- duccini@bpsi.net BackPack Software, Inc. www.backpack.com +1 612.645.7550 voice BPSI Internet Services www.bpsi.net +1 612.645.9798 fax 1.800eMail info@one800.net www.one800.net ------------------------------------------------------------------------------- From owner-freebsd-hackers Mon Aug 18 22:05:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA10708 for hackers-outgoing; Mon, 18 Aug 1997 22:05:09 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA10699 for ; Mon, 18 Aug 1997 22:05:04 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0x0gTW-0000Rt-00; Mon, 18 Aug 1997 23:05:02 -0600 To: hackers@freebsd.org Subject: fdisk and BIOS Date: Mon, 18 Aug 1997 23:05:02 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK. I'm really confused. I just tried to use the FreeBSD fdisk to label a disk with the proper c/h/s values for the disk (it is an old IDE disk). It totally freaked out on me giving me totally bogus numbers, even after I had entered the ones I wanted. Has anybody else seen this in a 2.2.1R kernel, and does anybody happen to know if it is fixed in newer revs? Warner P.S. No, there is no oddball translation getting in the way. This is pretty close to hit dinosaur over head with club level of hardware (an older 120M Quantum Prodrive LPS). From owner-freebsd-hackers Mon Aug 18 22:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11541 for hackers-outgoing; Mon, 18 Aug 1997 22:24:08 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca8-25.ix.netcom.com [204.31.231.89]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA11535 for ; Mon, 18 Aug 1997 22:24:04 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id WAA25666; Mon, 18 Aug 1997 22:24:00 -0700 (PDT) Date: Mon, 18 Aug 1997 22:24:00 -0700 (PDT) Message-Id: <199708190524.WAA25666@silvia.HIP.Berkeley.EDU> To: hackers@freebsd.org CC: steveg@comtrol.com Subject: [steveg@comtrol.com: updating our older port] From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The "ports" list is for ported software, not serial ports. ;) Satoshi ------- Date: Mon, 18 Aug 1997 14:14:10 -0500 To: ports@FreeBSD.ORG From: Steve Gericke Subject: updating our older port Cc: steveg@rocket.comtrol.com To FreeBSD ports: Our company Comtrol Corp. has a RocketPort (rckt) driver that supports from 4-32 serial ports at one time on 1 card and up to 4 cards per machine. This driver supports isa and/or pci cards. I took the liberty of puting our new driver package in you incoming directory under the name comtrol.gz Please let me know if there is more that I need to do. Thanks !! steveg@comtrol.com From owner-freebsd-hackers Mon Aug 18 22:44:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12394 for hackers-outgoing; Mon, 18 Aug 1997 22:44:17 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12386 for ; Mon, 18 Aug 1997 22:44:14 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.7/8.8.5) with ESMTP id WAA07143; Mon, 18 Aug 1997 22:43:22 -0700 (PDT) Message-Id: <199708190543.WAA07143@austin.polstra.com> To: grog@lemis.com Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <19970819140010.04999@lemis.com> References: <199708182246.PAA04812@austin.polstra.com> <22405.871954857@time.cdrom.com> <19970819140010.04999@lemis.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Mon, 18 Aug 1997 22:43:22 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greg Lehey wrote: > > On a more serious note, since BSDI has now switched to ELF, aren't we > going to have to do so anyway? I didn't realize they had switched, but given that ... Yes, we will have to switch to ELF. But we would have had to anyway -- for the same reasons BSDI had to. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Mon Aug 18 23:08:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA13670 for hackers-outgoing; Mon, 18 Aug 1997 23:08:23 -0700 (PDT) Received: from metro.telecom.samsung.co.kr (metro.telecom.samsung.co.kr [165.213.221.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA13662 for ; Mon, 18 Aug 1997 23:08:16 -0700 (PDT) Received: from metro.telecom.samsung.co.kr by metro.telecom.samsung.co.kr with SMTP (8.6.9H1/25-eef) id PAA17860; Tue, 19 Aug 1997 15:08:11 -0900 Message-ID: <33F938DF.3CB1@telecom.samsung.co.kr> Date: Tue, 19 Aug 1997 15:10:39 +0900 From: Jae-Hyun Park Reply-To: hyunie@telecom.samsung.co.kr Organization: ATM Research Team, Samsung Electronics, Co. X-Mailer: Mozilla 3.01 [ko]C-UNITEL (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Subscribe I would like to subscribe in FreeBSD technical discussions mailing list. Thanks in Advance, Jae-Hyun Park From owner-freebsd-hackers Mon Aug 18 23:22:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14468 for hackers-outgoing; Mon, 18 Aug 1997 23:22:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA14461 for ; Mon, 18 Aug 1997 23:22:33 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13579; Tue, 19 Aug 1997 08:22:32 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA19379; Tue, 19 Aug 1997 08:06:18 +0200 (MET DST) Message-ID: <19970819080618.XR34263@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 08:06:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: imp@rover.village.org (Warner Losh) Subject: Re: fdisk and BIOS References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Warner Losh on Aug 18, 1997 23:05:02 -0600 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Warner Losh wrote: > OK. I'm really confused. I just tried to use the FreeBSD fdisk to > label a disk with the proper c/h/s values for the disk (it is an old > IDE disk). I've never seen this, but well, better tell exactly what you were doing, and what the disk parameters (in particular the BIOS ones) are. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Aug 18 23:50:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA15988 for hackers-outgoing; Mon, 18 Aug 1997 23:50:46 -0700 (PDT) Received: from firewallint.avl.co.at (avlgate.avl.co.at [157.247.254.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA15978 for ; Mon, 18 Aug 1997 23:50:38 -0700 (PDT) Received: from umes01.avl.co.at (umes01.avl.co.at [157.247.2.25]) by firewallint.avl.co.at (8.8.5/8.8.5) with ESMTP id IAA10159 for ; Tue, 19 Aug 1997 08:50:20 +0200 (MDT) Received: from nmes74 (nmes74.avl.co.at [157.247.8.233]) by umes01.avl.co.at (8.8.5/8.8.5) with SMTP id IAA10975 for ; Tue, 19 Aug 1997 08:50:58 +0200 (MET DST) Date: Tue, 19 Aug 1997 08:52:40 From: Hermann Schinagl To: hackers@freebsd.org Subject: Re: Please Help Me Understand dlopen()] Message-Id: <19970819085282.NTM1204@umes01.avl.co.at> X-Mailer: NTXMail B.01.50.340 (Intel 32-bit) (Apr 23 1997 16:40:57 0007-150-BTT00000027) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA15983 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I think the fix should assume that the application most likely wants >to look up a normal C symbol. So it should do something like this: > > /* > * First try: look for a normal C symbol like (in assembly > * language) "_foo". > */ > if (sym starts with "_") /* Assume caller already added "_" */ > trysym = sym; > else /* Add "_" for caller */ > trysym = concat("_", sym); /* Not C, but you get the idea */ > > if (lookup(trysym)) > return success; > > /* > * Second try: look for a strange C symbol like (in assembly > * language) "__foo", or an assembly language symbol "foo" with no > * underscore at all. > */ > if (sym starts with "_") /* Assume C symbol really starts with "_" */ > trysym = concat("_", sym); > else /* Assume caller wants assembly symbol */ > trysym = sym; > > if (lookup(trysym)) > return success; > > /* > * Give up. > */ > return failure; You forgot that the symbols, which are exported by the lib are totally different, if you rename a .c file to .cpp and compile it again. ==> C++ exported symbols Well, it is easy to add '_' before the symbol, but the function-arguments of a C++ exported function are append encoded to the symbolname. eg.: '__func027_dfiv' So writing a wrapper is not that straight forward as mentioned above. You should also think of the C++ exporting mechanism. Ciao Hermann Regards, Hermann Schinagl -------------------------------------------------------------------- Dipl.-Ing. Hermann Schinagl AVL List GmbH Kleiststrasse 48 Email : schinagl@avl.co.at A-8020 Graz Phone : ++43 316 987 324 PGP : http://www.pgp.net/pgp Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Mon Aug 18 23:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16370 for hackers-outgoing; Mon, 18 Aug 1997 23:58:49 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA16363 for ; Mon, 18 Aug 1997 23:58:47 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id XAA25627 for ; Mon, 18 Aug 1997 23:58:16 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id CAA19867; Tue, 19 Aug 1997 02:58:13 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id CAA22501; Tue, 19 Aug 1997 02:58:14 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.6/8.7.3) id BAA27054; Tue, 19 Aug 1997 01:59:27 -0500 (CDT) Date: Tue, 19 Aug 1997 01:59:27 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199708190659.BAA27054@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: hackers@freebsd.org Subject: smbfs X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone done work on smbfs for FreeBSD? From owner-freebsd-hackers Tue Aug 19 00:13:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17628 for hackers-outgoing; Tue, 19 Aug 1997 00:13:57 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA17615 for ; Tue, 19 Aug 1997 00:13:51 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA07480; Tue, 19 Aug 1997 00:15:05 -0700 (PDT) Message-Id: <199708190715.AAA07480@implode.root.com> To: Joao Carlos Mendes Luis cc: freebsd-hackers@FreeBSD.ORG Subject: Re: releng22.freebsd.org ftp In-reply-to: Your message of "Tue, 19 Aug 1997 00:29:37 -0300." <199708190329.AAA09885@gaia.coppe.ufrj.br> From: David Greenman Reply-To: dg@root.com Date: Tue, 19 Aug 1997 00:15:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >#define quoting(Jordan K. Hubbard) >// > Dumb question 724: Is there some specific reason why the >// > ftp service on releng22.freebsd.org doesn't allow one to: >// > >// > get 2.2-970814-RELENG.tar >// >// That is a feature of wu-ftpd. releng22.freebsd.org is running >// the stock FreeBSD ftpd and probably won't change anytime soon. > >But ftp.cdrom.com does not use wu-ftpd and supports this. Are these >DG's private patches ? Any chance of these getting integrated to >the stock ftp in FreeBSD ? "dg-ftpd" is originally based on wu-ftpd and retains many of it's most important features. The problem with wu-ftpd was that it was big, bloated ("feature rich"), and slow. dg-ftpd is small and fast, but is tailored to the exact environment we have on wcarchive and lacks many features that many people think are important. I have no plans on releasing dg-ftpd. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Aug 19 00:42:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19300 for hackers-outgoing; Tue, 19 Aug 1997 00:42:49 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA19289 for ; Tue, 19 Aug 1997 00:42:39 -0700 (PDT) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id KAA07967; Tue, 19 Aug 1997 10:39:40 +0300 (EEST) Date: Tue, 19 Aug 1997 10:39:40 +0300 (EEST) From: Narvi To: Eugeny Kuzakov cc: freebsd-hackers@FreeBSD.ORG Subject: Re: JDK 1.1 for FreeBSD In-Reply-To: <19970819000935.57291@lab321.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Take a look at Sun's java page - under third parties there is a link. Sander There is no love, no good, no happiness and no future - all these are just illusions. On Tue, 19 Aug 1997, Eugeny Kuzakov wrote: > > Hi All ! > > Are there anyone succesfully run JDK 1.1 for FreeBSD ? > > -- > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > kev@lab321.ru > From owner-freebsd-hackers Tue Aug 19 01:24:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21455 for hackers-outgoing; Tue, 19 Aug 1997 01:24:17 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA21450 for ; Tue, 19 Aug 1997 01:24:14 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id KAA04515; Tue, 19 Aug 1997 10:24:06 +0200 (MEST) From: Søren Schmidt Message-Id: <199708190824.KAA04515@sos.freebsd.dk> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708190543.WAA07143@austin.polstra.com> from John Polstra at "Aug 18, 97 10:43:22 pm" To: jdp@polstra.com (John Polstra) Date: Tue, 19 Aug 1997 10:24:06 +0200 (MEST) Cc: grog@lemis.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to John Polstra who wrote: > Greg Lehey wrote: > > > > On a more serious note, since BSDI has now switched to ELF, aren't we > > going to have to do so anyway? > > I didn't realize they had switched, but given that ... > > Yes, we will have to switch to ELF. But we would have had to anyway -- > for the same reasons BSDI had to. OK, I have a spare box standing idle, could you point me at the latest code John ?? I'll have a go on making a system totally ELF then... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Tue Aug 19 04:55:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA00497 for hackers-outgoing; Tue, 19 Aug 1997 04:55:06 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA00487; Tue, 19 Aug 1997 04:54:26 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id MAA11374; Tue, 19 Aug 1997 12:46:01 +0200 From: Luigi Rizzo Message-Id: <199708191046.MAA11374@labinfo.iet.unipi.it> Subject: Re: isa_dmastatus To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 19 Aug 1997 12:46:01 +0200 (MET DST) Cc: smp@csn.net, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199708181630.JAA04190@rah.star-gate.com> from "Amancio Hasty" at Aug 18, 97 09:30:01 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > So in the end, I think that our isa_dma routines probably do not work > > with auto mode _and_ bounce buffers, indipendently of the checks on the > > dma_busy/dma_inuse flags. > > > > We can temporarily bypass the problem by making the DMA routines fail > > if auto mode is requested and a bounce buffer needs to be used for the > > channel. > > Your analisys is good. Whats left now, provided that the rest of the > team agrees on your proposed solution, is who is going to write > the code and when? since I am not using auto dma I won't be able to test anything... amancio can you volunteer on writing the code ? I won't be able to do that before the beginning of september. Cheers Luigi From owner-freebsd-hackers Tue Aug 19 05:51:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA03419 for hackers-outgoing; Tue, 19 Aug 1997 05:51:03 -0700 (PDT) Received: from ns.uk.peer.net ([194.117.157.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA03392 for ; Tue, 19 Aug 1997 05:50:30 -0700 (PDT) Received: (from aledm@localhost) by ns.uk.peer.net (8.6.12/8.6.12) id NAA12738; Tue, 19 Aug 1997 13:50:28 +0100 Date: Tue, 19 Aug 1997 13:50:23 +0100 (BST) From: Aled Morris X-Sender: aledm@ns.uk.peer.net To: hackers@freebsd.org Subject: IBM PC Server 325 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know what SCSI chipset is used in the IBM PC Server 325? (i.e. is this a suitable platform for FreeBSD?) For that matter, what about the 10Mbps integrated Ethernet? Aled -- tel +44 973 207987 O- From owner-freebsd-hackers Tue Aug 19 06:12:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04496 for hackers-outgoing; Tue, 19 Aug 1997 06:12:51 -0700 (PDT) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA04491 for ; Tue, 19 Aug 1997 06:12:45 -0700 (PDT) Message-Id: <199708191311.JAA22884@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Tue, 19 Aug 1997 09:14:21 -0400 (EDT) From: Jamie Bowden To: John Polstra cc: grog@lemis.com, hackers@freebsd.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708190543.WAA07143@austin.polstra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 18 Aug 1997, John Polstra wrote: > Greg Lehey wrote: > > > > On a more serious note, since BSDI has now switched to ELF, aren't we > > going to have to do so anyway? > > I didn't realize they had switched, but given that ... > > Yes, we will have to switch to ELF. But we would have had to anyway -- > for the same reasons BSDI had to. > > John Well, Terry will be happy. On a more serious note, what is the objection to moving to ELF, other than the time involved? Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Tue Aug 19 07:57:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA11053 for hackers-outgoing; Tue, 19 Aug 1997 07:57:35 -0700 (PDT) Received: from mail.ican.net ([204.92.55.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA11043 for ; Tue, 19 Aug 1997 07:57:24 -0700 (PDT) Received: from oddjob.ican.net (oddjob.ican.net [204.92.55.7]) by mail.ican.net (8.8.6/8.8.6) with ESMTP id KAA06232; Tue, 19 Aug 1997 10:56:47 -0400 (EDT) Received: (from josh@localhost) by oddjob.ican.net (8.8.6/8.8.6) id KAA21308; Tue, 19 Aug 1997 10:57:15 -0400 (EDT) Message-ID: <19970819105715.61464@ican.net> Date: Tue, 19 Aug 1997 10:57:15 -0400 From: Josh Tiefenbach To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: DPT problem References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Jaye Mathisen on Mon, Aug 18, 1997 at 05:02:27PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (just a note, you may get better feedback if you post to freebsd-scsi) > Hmm, just upgraded to a fairly recent 2.2.2-stable, and DPT patch 1.2.0, > however, now I can't boot my box anymore, I keep getting: > > dpt0: Test unit Ready, but controller shutdown... Yup. Had this problem as well. The fix is (quoting from Simon. Hope he doesnt mind.) > Please go to sys/pci/dpt_pci.c and in the function dpt_pci_attach, after > the long comment, BEFORE the four TAILQ_INIT calls, add: > > bzero(dpt, sizeof(dpt_softc_t); Apparently, the bit the the driver sets in memory to indicate that the controller is shut down, is not cleared across a reboot. Thus the thing keeps thinking its shut down. josh -- Josh Tiefenbach - Systems Engineer - ACC TelEnterprises - josh@ican.net From owner-freebsd-hackers Tue Aug 19 07:59:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA11119 for hackers-outgoing; Tue, 19 Aug 1997 07:59:07 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA11114 for ; Tue, 19 Aug 1997 07:59:03 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA23746 for ; Tue, 19 Aug 1997 10:58:31 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id KAA00543 for ; Tue, 19 Aug 1997 10:57:47 -0400 (EDT) Message-Id: <199708191457.KAA00543@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: Committers: New Cyclades Z driver ready Date: Tue, 19 Aug 1997 10:57:47 -0400 From: Brian McGovern Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've reached the point where my Cyclades Cyclom-Z driver is stable, and is actually doing quite well (we use it for modem testing here at Cisco in several groups). For those who don't know, the Zs come in one of three forms: 8Zo (V1) - 8 ports per card to 460K per port 8Zo (V2) - 8 ports per card to 920K per port 8Ze - up to 64 ports per card to 920K per port So far, I've run 32 ports (4x8Zo V1) in a Pentium Pro 200 using about 30% of the CPU at 115200 baud (this includes running PPP with FTP sessions saturating all of the links). As you can see, the boards are quite nice. Anyhow, I promised Cyclades that once the driver was stable, I'd offer it up the FreeBSD core for inclusion in to the standard operating system. I've uploaded the driver to ftp.freebsd.org in /pub/FreeBSD/incoming. The archive name is cz-0.N.tgz. It includes everything needed to drop it in to the kernel source, has a RELNOTES file, a makedev program (my shell scripting skills haven't been used for a couple of years, so I wrote it in C. Someone may want to translate it back), the firmware, headers, etc. The only thing that wasn't included prefab was the change to files.i386 in the conf directory (simply because it was straight forward enough). If someone could take a look at it, and either commit it, or reject it with comments on "whats wrong" (don't be too harsh, this is my first "real" Unix driver, and you don't want to scare me off from doing more :) ), and how you'd like it fixed, I'd appreciate it. I also expect to continue to support the driver, and make some changes (for instance, I'll be trying to add DMA capabilities, so the board can move the data directly in to kernel buffers, so the kernel can avoid PCI bus arbitration on an interrupt/poll), so comments, suggestions, and diffs are very much welcome. -Brian From owner-freebsd-hackers Tue Aug 19 09:22:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16545 for hackers-outgoing; Tue, 19 Aug 1997 09:22:14 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA16536 for ; Tue, 19 Aug 1997 09:22:10 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA19381; Tue, 19 Aug 1997 18:22:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id SAA20719; Tue, 19 Aug 1997 18:19:09 +0200 (MET DST) Message-ID: <19970819181909.XU45223@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 18:19:09 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: Anthony.Kimball@East.Sun.COM Subject: Re: smbfs References: <199708190659.BAA27054@compound.east.sun.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708190659.BAA27054@compound.east.sun.com>; from Tony Kimball on Aug 19, 1997 01:59:27 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tony Kimball wrote: > Has anyone done work on smbfs for FreeBSD? No, but did you try rumba (it's in the ports)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 09:25:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16827 for hackers-outgoing; Tue, 19 Aug 1997 09:25:42 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16809 for ; Tue, 19 Aug 1997 09:25:34 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id TAA12916; (8.8.3/zah/2.1) Tue, 19 Aug 1997 19:21:23 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id PAA05638; (8.6.11/zah/2.1) Tue, 19 Aug 1997 15:44:18 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id RAA00555; (8.6.9/zah/1.1) Tue, 19 Aug 1997 17:33:42 +0100 Received: from localhost (rssh@localhost) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id RAA01562; Tue, 19 Aug 1997 17:32:15 +0300 (EET DST) Date: Tue, 19 Aug 1997 17:32:15 +0300 (EET DST) From: Ruslan Shevchenko To: Eugeny Kuzakov cc: freebsd-hackers@FreeBSD.ORG Subject: Re: JDK 1.1 for FreeBSD In-Reply-To: <19970819000935.57291@lab321.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Aug 1997, Eugeny Kuzakov wrote: > > Hi All ! > > Are there anyone succesfully run JDK 1.1 for FreeBSD ? > I run kaffe-0.9.1, all's work. > -- > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > kev@lab321.ru > @= mailto:rssh@cki.ipri.kiev.ua //RSSH http://www.ipri.kiev.ua/~rssh From owner-freebsd-hackers Tue Aug 19 09:51:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA18446 for hackers-outgoing; Tue, 19 Aug 1997 09:51:16 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA18440 for ; Tue, 19 Aug 1997 09:51:13 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA19872 for hackers@FreeBSD.ORG; Tue, 19 Aug 1997 18:51:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id SAA20872; Tue, 19 Aug 1997 18:33:27 +0200 (MET DST) Message-ID: <19970819183327.NZ13302@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 18:33:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <199708190543.WAA07143@austin.polstra.com> <199708191311.JAA22884@gatekeeper.itribe.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708191311.JAA22884@gatekeeper.itribe.net>; from Jamie Bowden on Aug 19, 1997 09:14:21 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jamie Bowden wrote: > Well, Terry will be happy. On a more serious note, what is the objection > to moving to ELF, other than the time involved? Not much objection, but we all remember one good example for how not to do the transition... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 10:14:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20386 for hackers-outgoing; Tue, 19 Aug 1997 10:14:48 -0700 (PDT) Received: from punt-2.mail.demon.net (punt-2d.mail.demon.net [194.217.242.9]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA20381 for ; Tue, 19 Aug 1997 10:14:44 -0700 (PDT) Received: from longacre.demon.co.uk ([158.152.156.24]) by punt-2.mail.demon.net id aa1206762; 19 Aug 97 18:05 BST From: Michael Searle Message-ID: To: hackers@freebsd.org Subject: Fast measurement of used swap? Date: Tue, 19 Aug 1997 17:48:43 BST X-Mailer: Offlite 0.09 / Termite Internet for Acorn RISC OS Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm porting a system monitor from Linux. What's the fastest way of measuring the total amount of swap used (over all devices)? All the programs I've seen that do it use kvm, in fact using the same piece of code from swapinfo. This is very slow (uses several thousand syscalls) and also takes time proportional to the amount of swap (whether this is used or not), so I don't want to do this unless it's the only way. (BTW, I'm using 2.1.0 if it matters.) Thanks, Michael. -- Michael Searle - csubl@csv.warwick.ac.uk From owner-freebsd-hackers Tue Aug 19 10:28:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA21172 for hackers-outgoing; Tue, 19 Aug 1997 10:28:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA21166 for ; Tue, 19 Aug 1997 10:28:48 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0x0s58-00019Q-00; Tue, 19 Aug 1997 11:28:38 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: fdisk and BIOS Cc: freebsd-hackers@freebsd.org (FreeBSD hackers) In-reply-to: Your message of "Tue, 19 Aug 1997 08:06:18 +0200." <19970819080618.XR34263@uriah.heep.sax.de> References: <19970819080618.XR34263@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 11:28:38 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970819080618.XR34263@uriah.heep.sax.de> J Wunsch writes: : I've never seen this, but well, better tell exactly what you were : doing, and what the disk parameters (in particular the BIOS ones) are. OK. I'll grab a dump of these when I get the chance (the machine is off right now in another city). From memory the disk drive reported 901c 5t 53s in demsg. fdisk reported 785c 8h 56s for both the BIOS numbers and the incore numbers. Once I set the numbers to the ones listed first (901, etc), fdisk reported 2047c 3h 34s for both the BIOS and the in core numbers. Rebooting got me back to fdisk reporting the 785c figures, even though dmesg continued to report the 901 numbers (which agree with the Quantum ProDrive LPS numbers on the Quantum web page). This is wd1, if that matters (and yes, it is jumpered to be slave). More details when I can get to the machine again and run a script. None of the numbers fdisk reported matched wd0's geometry. Also, the BIOS was configured with type 47 - 901 5 53 for this drive (this is an old 386 that I got at a garage sale). Warner From owner-freebsd-hackers Tue Aug 19 10:32:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA21364 for hackers-outgoing; Tue, 19 Aug 1997 10:32:00 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA21347 for ; Tue, 19 Aug 1997 10:31:51 -0700 (PDT) Received: from elwing.folklore.ee (elwing.folklore.ee [172.17.2.2]) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id UAA14437 for ; Tue, 19 Aug 1997 20:31:14 +0300 (EEST) Date: Tue, 19 Aug 1997 20:31:14 +0300 (EEST) From: Narvi X-Sender: narvi@elwing.folklore.ee To: hackers@freebsd.org Subject: vn devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How does one label and newfs a vn disk under 2.2-stable? No matter what I say to it, it answers with ioctl DIOCxxxxx: Inappropriate ioctl for device How does one configure a new file for being a vnode disk? And where is it all documented? Sander There is no love, no good, no happiness and no future - all these are just illusions. From owner-freebsd-hackers Tue Aug 19 10:33:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA21481 for hackers-outgoing; Tue, 19 Aug 1997 10:33:27 -0700 (PDT) Received: from webfarm1.whistle.com (webfarm1.whistle.com [207.76.204.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA21474 for ; Tue, 19 Aug 1997 10:33:24 -0700 (PDT) Received: from alpo.whistle.com (alpo.isp.whistle.com [207.76.204.38]) by webfarm1.whistle.com (8.8.5/8.8.5) with ESMTP id XAA19337; Mon, 18 Aug 1997 23:51:31 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA10022; Mon, 18 Aug 1997 23:14:49 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010018; Tue Aug 19 06:14:39 1997 Date: Mon, 18 Aug 1997 23:12:04 -0700 (PDT) From: Julian Elischer To: Greg Lehey cc: "Jordan K. Hubbard" , FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <19970819140010.04999@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk actually I believe it's probably time to start getting ready to do this julian On Tue, 19 Aug 1997, Greg Lehey wrote: > On Mon, Aug 18, 1997 at 06:40:57PM -0700, Jordan K. Hubbard wrote: > >> I agree that it's a bug, and I followed up there saying I planned to > >> fix it. One fix would be switching to ELF, of course ... ;-) > > > > Well, let's do it then. :) > > On a more serious note, since BSDI has now switched to ELF, aren't we > going to have to do so anyway? > > Greg > From owner-freebsd-hackers Tue Aug 19 10:59:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA23032 for hackers-outgoing; Tue, 19 Aug 1997 10:59:15 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22999 for ; Tue, 19 Aug 1997 10:58:56 -0700 (PDT) Received: from elwing.folklore.ee (elwing.folklore.ee [172.17.2.2]) by haldjas.folklore.ee (8.8.6/8.8.4) with SMTP id UAA14517 for ; Tue, 19 Aug 1997 20:58:23 +0300 (EEST) Date: Tue, 19 Aug 1997 20:58:23 +0300 (EEST) From: Narvi X-Sender: narvi@elwing.folklore.ee To: hackers@FreeBSD.ORG Subject: Re: vn devices In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, it did work after a reboot. Strange... Sander There is no love, no good, no happiness and no future - all these are just illusions. On Tue, 19 Aug 1997, Narvi wrote: > > How does one label and newfs a vn disk under 2.2-stable? > > No matter what I say to it, it answers with > > ioctl DIOCxxxxx: Inappropriate ioctl for device > > How does one configure a new file for being a vnode disk? > > And where is it all documented? > > Sander > > From owner-freebsd-hackers Tue Aug 19 11:15:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24235 for hackers-outgoing; Tue, 19 Aug 1997 11:15:09 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24228 for ; Tue, 19 Aug 1997 11:15:05 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id LAA03736; Tue, 19 Aug 1997 11:12:43 -0700 (PDT) To: Julian Elischer cc: Greg Lehey , FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-reply-to: Your message of "Mon, 18 Aug 1997 23:12:04 PDT." Date: Tue, 19 Aug 1997 11:12:43 -0700 Message-ID: <3733.872014363@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You thought I was joking? I think the first step is to start getting some -current testers to convert to ELF and pave the way for a more general effort. Right now, running a FreeBSD system 100% ELF is mostly just a theory. Jordan > actually I believe it's probably time > to start getting ready to do this > > julian > > On Tue, 19 Aug 1997, Greg Lehey wrote: > > > On Mon, Aug 18, 1997 at 06:40:57PM -0700, Jordan K. Hubbard wrote: > > >> I agree that it's a bug, and I followed up there saying I planned to > > >> fix it. One fix would be switching to ELF, of course ... ;-) > > > > > > Well, let's do it then. :) > > > > On a more serious note, since BSDI has now switched to ELF, aren't we > > going to have to do so anyway? > > > > Greg > > > From owner-freebsd-hackers Tue Aug 19 11:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24369 for hackers-outgoing; Tue, 19 Aug 1997 11:16:39 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24364 for ; Tue, 19 Aug 1997 11:16:33 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.7/8.7.1) id OAA30368; Tue, 19 Aug 1997 14:22:48 -0400 Date: Tue, 19 Aug 1997 14:22:48 -0400 (EDT) From: Ben Black To: Joerg Wunsch cc: hackers@FreeBSD.ORG, Anthony.Kimball@East.Sun.COM Subject: Re: smbfs In-Reply-To: <19970819181909.XU45223@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i think you mean samba. On Tue, 19 Aug 1997, J Wunsch wrote: > As Tony Kimball wrote: > > > Has anyone done work on smbfs for FreeBSD? > > No, but did you try rumba (it's in the ports)? > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-hackers Tue Aug 19 11:40:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26133 for hackers-outgoing; Tue, 19 Aug 1997 11:40:09 -0700 (PDT) Received: from inet16.us.oracle.com (inet16.us.oracle.com [192.86.155.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26114 for ; Tue, 19 Aug 1997 11:40:04 -0700 (PDT) Received: from mailsun2.us.oracle.com (mailsun2.us.oracle.com [144.25.88.74]) by inet16.us.oracle.com (8.8.5/8.8.5) with SMTP id LAA01613 for ; Tue, 19 Aug 1997 11:40:03 -0700 (PDT) Received: by mailsun2.us.oracle.com (SMI-8.6/37.8) id LAA23834; Tue, 19 Aug 1997 11:47:37 -0700 Message-Id: <199708191847.LAA23834@mailsun2.us.oracle.com> Date: 19 Aug 97 10:16:52 -0700 From: "RASHAH.US.ORACLE.COM" To: freebsd-hackers@freebsd.org Subject: poll system call on FreeBSD ? MIME-Version: 1.0 X-Mailer: Oracle InterOffice (version 4.0.2.1.40) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi FreeBSD Gurus, I am new to the FreeBSD. I have to port some software from SVR4 to FreeBSD. On SVR4 poll() system call is available but it is not available on FreeBSD. I was just wondering is there any equivalent call of poll() on FreeBSD ? select() won't work as I am not polling on sockets. Another thing is I believe poll() system call require STREAMS implementation of the driver/module. Does BSD have streams implemetation equivalent to SVR4 (i mean file system and all other kernel modules ?). I know my question is bit wague but I hope you will understand. BTW I just subscribe myself for this mailing list and have not got confirmation so would appreciate your direct reply at rashah@us.oracle.com. Thanks in advance. Rajesh From owner-freebsd-hackers Tue Aug 19 11:40:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26171 for hackers-outgoing; Tue, 19 Aug 1997 11:40:44 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA26165 for ; Tue, 19 Aug 1997 11:40:42 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA04879; Tue, 19 Aug 1997 11:40:05 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id OAA08804; Tue, 19 Aug 1997 14:40:03 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id OAA04626; Tue, 19 Aug 1997 14:40:02 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.6/8.7.3) id NAA00390; Tue, 19 Aug 1997 13:41:23 -0500 (CDT) Date: Tue, 19 Aug 1997 13:41:23 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199708191841.NAA00390@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: black@zen.cypher.net Cc: hackers@FreeBSD.ORG Subject: Re: smbfs References: <19970819181909.XU45223@uriah.heep.sax.de> X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Ben Black on Tue, 19 August: : i think you mean samba. : No, he meant rumba. It implements a user-space SMB *client* using the NFS kernel interface. Samba is a *server*. (And thanks for the rumba pointer.) From owner-freebsd-hackers Tue Aug 19 11:42:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26304 for hackers-outgoing; Tue, 19 Aug 1997 11:42:26 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26288 for ; Tue, 19 Aug 1997 11:42:20 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA26833; Tue, 19 Aug 1997 11:23:16 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026825; Tue Aug 19 18:23:04 1997 Message-ID: <33F9E3C6.4DAA423A@whistle.com> Date: Tue, 19 Aug 1997 11:19:50 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Greg Lehey , FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <3733.872014363@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > You thought I was joking? wan't sure, but either way, I'm not.. I think that the first step is to work with the tools I'd like to see an 'ld' that can link libraries in both formats and produce a binary of either output type. also a single option in 'as/gcc' to produce binaries of both types from one program. It might not be impossible to produce a utility to convert .o files from one format to the other either. > > I think the first step is to start getting some -current testers to > convert to ELF and pave the way for a more general effort. Right now, > running a FreeBSD system 100% ELF is mostly just a theory. > > Jordan > > > actually I believe it's probably time > > to start getting ready to do this > > > > julian > > > > On Tue, 19 Aug 1997, Greg Lehey wrote: > > > > > On Mon, Aug 18, 1997 at 06:40:57PM -0700, Jordan K. Hubbard wrote: > > > >> I agree that it's a bug, and I followed up there saying I planned to > > > >> fix it. One fix would be switching to ELF, of course ... ;-) > > > > > > > > Well, let's do it then. :) > > > > > > On a more serious note, since BSDI has now switched to ELF, aren't we > > > going to have to do so anyway? > > > > > > Greg > > > > > From owner-freebsd-hackers Tue Aug 19 12:08:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28063 for hackers-outgoing; Tue, 19 Aug 1997 12:08:18 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA28056 for ; Tue, 19 Aug 1997 12:08:12 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.7/8.7.1) id PAA31349; Tue, 19 Aug 1997 15:15:58 -0400 Date: Tue, 19 Aug 1997 15:15:57 -0400 (EDT) From: Ben Black To: Tony Kimball cc: hackers@FreeBSD.ORG Subject: Re: smbfs In-Reply-To: <199708191841.NAA00390@compound.east.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ah, my mistake. to me, rumba is still a 3270 emulator for windows. On Tue, 19 Aug 1997, Tony Kimball wrote: > Quoth Ben Black on Tue, 19 August: > : i think you mean samba. > : > No, he meant rumba. It implements a user-space SMB *client* using the > NFS kernel interface. Samba is a *server*. > > (And thanks for the rumba pointer.) > From owner-freebsd-hackers Tue Aug 19 13:50:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04411 for hackers-outgoing; Tue, 19 Aug 1997 13:50:35 -0700 (PDT) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA04388 for ; Tue, 19 Aug 1997 13:50:17 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id QAA25930; Tue, 19 Aug 1997 16:50:36 -0400 (EDT) Date: Tue, 19 Aug 1997 16:50:36 -0400 (EDT) From: "David E. Cross" To: "RASHAH.US.ORACLE.COM" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: poll system call on FreeBSD ? In-Reply-To: <199708191847.LAA23834@mailsun2.us.oracle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 19 Aug 1997, RASHAH.US.ORACLE.COM wrote: > SVR4 poll() system call is available but it is not available on FreeBSD. I was > just wondering is there any equivalent call of poll() on FreeBSD ? select() > won't > work as I am not polling on sockets. Another thing is I believe poll() system > call require STREAMS implementation of the driver/module. Does BSD have streams > implemetation equivalent to SVR4 (i mean file system and all other kernel > modules ?). > I know my question is bit wague but I hope you will understand. select() will work on almost any file descriptor, it does not have to be a network (or otherwise) socket. -- David Cross From owner-freebsd-hackers Tue Aug 19 14:20:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06092 for hackers-outgoing; Tue, 19 Aug 1997 14:20:37 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06075; Tue, 19 Aug 1997 14:20:30 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id OAA27105; Tue, 19 Aug 1997 14:20:28 -0700 (PDT) Date: Tue, 19 Aug 1997 14:20:28 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org, ports@freebsd.org Subject: vm86.h compile warning Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have no idea if this warning is apropos to this header file or not, and I wouldn't deign to guess at it's correctness. I just point it out because I don't like warnings that tell me I'm probably not getting what I bargained for. :) Build of skill-3.7.4 on -current: ===> Configuring for skill-3.7.4 Configuring as bsd44: OSTYPE=bsd-44 COPTS= LIBS=-lkvm ===> Building for skill-3.7.4 cc -O -c main.c cc -O -c argparse.c rm -f getproc.c getproc.o ln -s machdep/bsd-44.c getproc.c cc -O -c getproc.c In file included from /usr/include/machine/pcb_ext.h:36, from /usr/include/machine/pcb.h:48, from /usr/include/sys/user.h:40, from getproc.c:22: /usr/include/machine/vm86.h:109: warning: `struct proc' declared inside parameter list /usr/include/machine/vm86.h:109: warning: its scope is only this definition or declaration, /usr/include/machine/vm86.h:109: warning: which is probably not what you want. cc -O main.o argparse.o getproc.o -o skill -lkvm From owner-freebsd-hackers Tue Aug 19 14:22:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06229 for hackers-outgoing; Tue, 19 Aug 1997 14:22:59 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06217 for ; Tue, 19 Aug 1997 14:22:55 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id OAA27463 for ; Tue, 19 Aug 1997 14:22:53 -0700 (PDT) Date: Tue, 19 Aug 1997 14:22:52 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Is there some trick to doing make in /usr/src/release? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I get numerous errors from the various files about syntax errors, extra ;'s and such, and in short, it doesn't work. (I was attempting to build a DPT boot floppy). I'm on 2.2.2-stable, supped as of a week or so ago. From owner-freebsd-hackers Tue Aug 19 14:52:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08186 for hackers-outgoing; Tue, 19 Aug 1997 14:52:16 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA08175 for ; Tue, 19 Aug 1997 14:52:13 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA23576 for hackers@FreeBSD.ORG; Tue, 19 Aug 1997 23:52:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id XAA21637; Tue, 19 Aug 1997 23:36:44 +0200 (MET DST) Message-ID: <19970819233644.BX01311@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 23:36:44 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: smbfs References: <19970819181909.XU45223@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Ben Black on Aug 19, 1997 14:22:48 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Ben Black wrote: > i think you mean samba. No, i mean rumba. The relation between the names is certainly not an incident. j@uriah 160% cat /usr/ports/net/rumba/pkg/DESCR It is part of author's Announcment: This is the first public release of rumba. If you want a short description of what rumba can do for you: you can mount volumes exported by Windows or related operating systems on your Unix machine. For a more detailed description I will quote from the README file: What does rumba do? =================== If you know smbfs for Linux: rumba is roughly the same. It is derived from smbfs, but runs as a user level program, not in the kernel. If you know samba: rumba is roughly the opposite: a client for the Lanmanager protocol. If you know neither of these: rumba lets you mount drives exported by Windows (f.Workgroups/95/NT), Lan Manager, OS/2 etc. on Unix machines. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 14:52:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08229 for hackers-outgoing; Tue, 19 Aug 1997 14:52:30 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA08219 for ; Tue, 19 Aug 1997 14:52:26 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA23584; Tue, 19 Aug 1997 23:52:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id XAA21670; Tue, 19 Aug 1997 23:43:21 +0200 (MET DST) Message-ID: <19970819234321.AK16622@uriah.heep.sax.de> Date: Tue, 19 Aug 1997 23:43:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: RASHAH@us.oracle.com (RASHAH.US.ORACLE.COM) Subject: Re: poll system call on FreeBSD ? References: <199708191847.LAA23834@mailsun2.us.oracle.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708191847.LAA23834@mailsun2.us.oracle.com>; from RASHAH.US.ORACLE.COM on Aug 19, 1997 10:16:52 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As RASHAH.US.ORACLE.COM wrote: > I am new to the FreeBSD. I have to port some software from SVR4 to > FreeBSD. On SVR4 poll() system call is available but it is not > available on FreeBSD. I was just wondering is there any equivalent > call of poll() on FreeBSD ? Wait a little, and FreeBSD will have poll(2), too. It's already been decided. > select() won't work as I am not polling on sockets. select(2) works on any descriptor, not only on socket descriptors. This is not the difference between both. > Another thing is I believe poll() system call require STREAMS > implementation of the driver/module. Does BSD have streams > implemetation equivalent to SVR4 No, and No. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 15:38:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA10689 for hackers-outgoing; Tue, 19 Aug 1997 15:38:43 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA10660; Tue, 19 Aug 1997 15:38:26 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id RAA21885; Tue, 19 Aug 1997 17:56:13 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id RAA17256; Tue, 19 Aug 1997 17:39:40 -0500 Message-ID: <19970819173939.43163@right.PCS> Date: Tue, 19 Aug 1997 17:39:39 -0500 From: Jonathan Lemon To: Jaye Mathisen Cc: hackers@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: vm86.h compile warning References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Jaye Mathisen on Aug 08, 1997 at 02:20:28PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 08, 1997 at 02:20:28PM -0700, Jaye Mathisen wrote: > > I have no idea if this warning is apropos to this header file or not, and > I wouldn't deign to guess at it's correctness. > > I just point it out because I don't like warnings that tell me I'm > probably not getting what I bargained for. :) > > Build of skill-3.7.4 on -current: > > ===> Configuring for skill-3.7.4 > Configuring as bsd44: OSTYPE=bsd-44 COPTS= LIBS=-lkvm > ===> Building for skill-3.7.4 > cc -O -c main.c > cc -O -c argparse.c > rm -f getproc.c getproc.o > ln -s machdep/bsd-44.c getproc.c > cc -O -c getproc.c > In file included from /usr/include/machine/pcb_ext.h:36, > from /usr/include/machine/pcb.h:48, > from /usr/include/sys/user.h:40, > from getproc.c:22: > /usr/include/machine/vm86.h:109: warning: `struct proc' declared inside > parameter list > /usr/include/machine/vm86.h:109: warning: its scope is only this > definition or declaration, > /usr/include/machine/vm86.h:109: warning: which is probably not what you > want. > cc -O main.o argparse.o getproc.o -o skill -lkvm Ugh. declares a function that takes a (struct proc *) as a parameter, but you haven't included beforehand, so thus this error. I see that does pull in proc.h, but too late. I'm not sure what the best way to fix this is; #ifdef KERNEL around the parameter declarations in vm86.h? -- Jonathan From owner-freebsd-hackers Tue Aug 19 16:10:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12255 for hackers-outgoing; Tue, 19 Aug 1997 16:10:18 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12245 for ; Tue, 19 Aug 1997 16:10:11 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA08466; Tue, 19 Aug 1997 16:09:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008463; Tue Aug 19 23:09:22 1997 Message-ID: <33FA26D2.5E652F78@whistle.com> Date: Tue, 19 Aug 1997 16:05:54 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hackers@FreeBSD.ORG, "RASHAH.US.ORACLE.COM" Subject: Re: poll system call on FreeBSD ? References: <199708191847.LAA23834@mailsun2.us.oracle.com> <19970819234321.AK16622@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As RASHAH.US.ORACLE.COM wrote: > > > I am new to the FreeBSD. I have to port some software from SVR4 to > > FreeBSD. On SVR4 poll() system call is available but it is not > > available on FreeBSD. I was just wondering is there any equivalent > > call of poll() on FreeBSD ? > > Wait a little, and FreeBSD will have poll(2), too. It's already been > decided. > > > select() won't work as I am not polling on sockets. > > select(2) works on any descriptor, not only on socket descriptors. > This is not the difference between both. > > > Another thing is I believe poll() system call require STREAMS > > implementation of the driver/module. Does BSD have streams > > implemetation equivalent to SVR4 No, but it depends on what you want to DO with streams that decides whether this is a problem or not. Whistle communications has a STREAMS replacement that is not compatible but can be used to do a lot of the same things.. It is publicly available on an "ask for it" basis.. (presently only works on 2.2 but I will move it to 3.0 soon). > > No, and No. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 16:45:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14151 for hackers-outgoing; Tue, 19 Aug 1997 16:45:49 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14144 for ; Tue, 19 Aug 1997 16:45:44 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA10445; Wed, 20 Aug 1997 01:43:25 +0200 (MET DST) Date: Wed, 20 Aug 1997 01:43:25 +0200 (MET DST) Message-Id: <199708192343.BAA10445@bitbox.follo.net> From: Eivind Eklund To: John Polstra CC: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-reply-to: John Polstra's message of Mon, 18 Aug 1997 19:57:55 -0700 Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <22405.871954857@time.cdrom.com> <199708190257.TAA06199@austin.polstra.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > I agree that it's a bug, and I followed up there saying I planned to > > > fix it. One fix would be switching to ELF, of course ... ;-) > > > > Well, let's do it then. :) > > OK, will do. I'm sure glad that got settled so easily! ;-) *Clapping hands and cheering* [Comments about hiding due to wanting to implement technical progress removed] Eivind. From owner-freebsd-hackers Tue Aug 19 17:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16832 for hackers-outgoing; Tue, 19 Aug 1997 17:35:22 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16822 for ; Tue, 19 Aug 1997 17:35:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id RAA01839; Tue, 19 Aug 1997 17:34:27 -0700 (PDT) To: kudzu@dnai.com Cc: hackers@freebsd.org Subject: Re: su: kerberos: not in root's ACL. In-reply-to: Your message of "Tue, 19 Aug 1997 11:59:08 PDT." <33F9ECFC.4CF@dnai.com> Date: Tue, 19 Aug 1997 17:34:27 -0700 Message-ID: <1835.872037267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sounds like an easy fix: Index: csh.c =================================================================== RCS file: /home/ncvs/src/bin/csh/csh.c,v retrieving revision 1.6 diff -u -r1.6 csh.c --- csh.c 1995/10/23 23:08:25 1.6 +++ csh.c 1997/08/20 00:32:37 @@ -622,7 +622,9 @@ for (;;) { if ((c = *dp) == ':' || c == 0) { *dp = 0; - if (*cp != '/' && (euid == 0 || uid == 0) && + if (!*cp) + break; + else if (*cp != '/' && (euid == 0 || uid == 0) && (intact || intty && isatty(SHOUT))) (void) fprintf(csherr, "Warning: imported path contains relative components\n"); However, what's unclear here is whether or not there is some "historical" behavior in having a trailing : in one's path result in an implicit inclusion of `.', something which is also a side-effect of what happens here. Any csh hackers care to comment? Jordan > Jordan K. Hubbard wrote: > > > > And $SHELL is csh in both su'd and non-su'd cases? > > SHELL=/bin/csh > > and in the su'd case: > > SHELL=/bin/csh > > I think I know where the problem is, I think. I put some "echo" > code in csh.c: > > % su - > Password: > path is: /usr/bin:/bin:/usr/sbin:/sbin: > Warning: imported path contains relative components > > The problem is the terminal ":" -- wherever *that's* > coming from, it's showing a bug in the 'importpath()'. > > > My echo is done here in the code: > > /* > * Re-initialize path if set in environment > * importpath uses intty and intact > */ > > if ((tcp = getenv("PATH")) == NULL) > set1(STRpath, defaultpath(), &shvhed); > else { > (void) fprintf(csherr, "path is: %s\n",tcp); /* I ADDED THIS, Jordan */ > importpath(SAVE(tcp)); > } > > and the bug is in how a terminal ":" is handled in importpath. Wanna > walk through the code with me? See what happens when the ":" is at > the end of the string (followed by a nul). > > void > importpath(cp) > Char *cp; > { > register int i = 0; > register Char *dp; > register Char **pv; > int c; > > for (dp = cp; *dp; dp++) > if (*dp == ':') > i++; > /* > * i+2 where i is the number of colons in the path. There are i+1 > * directories in the path plus we need room for a zero terminator. > */ > pv = (Char **) xcalloc((size_t) (i + 2), sizeof(Char **)); > dp = cp; > i = 0; > if (*dp) > for (;;) { > if ((c = *dp) == ':' || c == 0) { > *dp = 0; > if (*cp != '/' && (euid == 0 || uid == 0) && > (intact || intty && isatty(SHOUT))) > (void) fprintf(csherr, > "Warning: imported path contains relative components\n"); > pv[i++] = Strsave(*cp ? cp : STRdot); > if (c) { > cp = dp + 1; > *dp = ':'; > } > else > break; > } > dp++; > } > pv[i] = 0; > set1(STRpath, pv, &shvhed); > } From owner-freebsd-hackers Tue Aug 19 17:55:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17712 for hackers-outgoing; Tue, 19 Aug 1997 17:55:02 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA17690 for ; Tue, 19 Aug 1997 17:54:56 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id KAA26222; Wed, 20 Aug 1997 10:53:53 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id KAA02292; Wed, 20 Aug 1997 10:23:52 +0930 (CST) Message-ID: <19970820102352.64876@lemis.com> Date: Wed, 20 Aug 1997 10:23:52 +0930 From: Greg Lehey To: "Jordan K. Hubbard" Cc: FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <3733.872014363@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3733.872014363@time.cdrom.com>; from Jordan K. Hubbard on Tue, Aug 19, 1997 at 11:12:43AM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Aug 19, 1997 at 11:12:43AM -0700, Jordan K. Hubbard wrote: > You thought I was joking? > > I think the first step is to start getting some -current testers to > convert to ELF and pave the way for a more general effort. Right now, > running a FreeBSD system 100% ELF is mostly just a theory. What do you mean by "convert to ELF"? I hope you don't mean a wholesale change. I'd be interested in testing it (and the BSD/OS stuff, too, if I can find my BSD/OS 3.0 CD-ROM), and maybe building some packages in ELF instead of a.out, but I wouldn't want to change everything at the moment. Greg >> actually I believe it's probably time >> to start getting ready to do this >> >> julian >> >> On Tue, 19 Aug 1997, Greg Lehey wrote: >> >>> On Mon, Aug 18, 1997 at 06:40:57PM -0700, Jordan K. Hubbard wrote: >>>>> I agree that it's a bug, and I followed up there saying I planned to >>>>> fix it. One fix would be switching to ELF, of course ... ;-) >>>> >>>> Well, let's do it then. :) >>> >>> On a more serious note, since BSDI has now switched to ELF, aren't we >>> going to have to do so anyway? From owner-freebsd-hackers Tue Aug 19 18:04:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA17986 for hackers-outgoing; Tue, 19 Aug 1997 18:04:45 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA17981 for ; Tue, 19 Aug 1997 18:04:42 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA02072; Tue, 19 Aug 1997 18:00:44 -0700 (PDT) To: Greg Lehey cc: FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-reply-to: Your message of "Wed, 20 Aug 1997 10:23:52 +0930." <19970820102352.64876@lemis.com> Date: Tue, 19 Aug 1997 18:00:43 -0700 Message-ID: <2068.872038843@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I think the first step is to start getting some -current testers to > > convert to ELF and pave the way for a more general effort. Right now, > > running a FreeBSD system 100% ELF is mostly just a theory. > > What do you mean by "convert to ELF"? I hope you don't mean a > wholesale change. I'd be interested in testing it (and the BSD/OS > stuff, too, if I can find my BSD/OS 3.0 CD-ROM), and maybe building > some packages in ELF instead of a.out, but I wouldn't want to change > everything at the moment. Well, I don't think that reasonable coverage can be obtained from piecemeal testing so yes, I do mean a wholesale change (up to and including the kernel). This scenario is not out of the question for those of us with hardware dedicated specifically to testing and so I'm hoping that such testers will come forward and help John P. start really testing the ELF toolchain support. Jordan From owner-freebsd-hackers Tue Aug 19 19:49:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22818 for hackers-outgoing; Tue, 19 Aug 1997 19:49:39 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22812 for ; Tue, 19 Aug 1997 19:49:36 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA14576; Tue, 19 Aug 1997 19:41:01 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014572; Wed Aug 20 02:40:56 1997 Message-ID: <33FA585D.167EB0E7@whistle.com> Date: Tue, 19 Aug 1997 19:37:17 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: John Polstra CC: grog@lemis.com, hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <199708182246.PAA04812@austin.polstra.com> <22405.871954857@time.cdrom.com> <19970819140010.04999@lemis.com> <199708190543.WAA07143@austin.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Polstra wrote: > > Greg Lehey wrote: > > > > On a more serious note, since BSDI has now switched to ELF, aren't we > > going to have to do so anyway? > > I didn't realize they had switched, but given that ... > > Yes, we will have to switch to ELF. But we would have had to anyway -- > for the same reasons BSDI had to. > John, what are the chances of being able to link a binary from mixed a.out and elf .o files? And what are the chances of being able to generate both types with just a single switch differnt in the command line? If we could do that then a change-over would become much more painless. We could do parts at a time. From owner-freebsd-hackers Tue Aug 19 19:52:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22997 for hackers-outgoing; Tue, 19 Aug 1997 19:52:51 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA22992 for ; Tue, 19 Aug 1997 19:52:49 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id MAA00608 for ; Wed, 20 Aug 1997 12:52:16 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id MAA09485; Wed, 20 Aug 1997 12:22:15 +0930 (CST) Message-ID: <19970820122215.34114@lemis.com> Date: Wed, 20 Aug 1997 12:22:15 +0930 From: Greg Lehey To: FreeBSD Hackers Subject: gdb: Program received signal SIGTRAP? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anybody seen problems with gdb where you can't continue from a breakpoint? I'm currently trying to test user ppp, but once I hit a breakpoint, I can't continue. I'm running -current as of yesterday. Here's a sample: (gdb) b 773 Breakpoint 1 at 0xfe6d: file /src/FREEBIE/usr.sbin/ppp/main.c, line 773. (gdb) r -nodaemon -ddial bigpond Starting program: /usr/obj/src/FREEBIE/usr.sbin/ppp/ppp -nodaemon -ddial bigpond During symbol reading...unknown symbol type 0x1e... User Process PPP. Written by Toshiharu OHNO. Using interface: tun0 Automatic Dialer mode Warning: No password entry for this host in ppp.secret Warning: Manipulation is allowed by anyone Breakpoint 1, DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 773 if (been_here_before) /* we won't be able to do it again, */ (gdb) n 787 if(mode & MODE_INTER) { (gdb) 788 #ifdef SIGTSTP (gdb) 810 * due to the "set reconnect" value, we'd better bring the line (gdb) c Continuing. Breakpoint 1, DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 773 if (been_here_before) /* we won't be able to do it again, */ (gdb) n Cannot insert breakpoint 0: Error accessing memory address 0xefbfdfdc: Bad address. (gdb) d Delete all breakpoints? (y or n) y (gdb) n signal_recorder (sig=14) at /src/FREEBIE/usr.sbin/ppp/sig.c:48 48 caused[sig-1]++; (gdb) 49 } (gdb) Program received signal SIGTRAP, Trace/breakpoint trap. DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 773 if (been_here_before) /* we won't be able to do it again, */ (gdb) Cannot insert breakpoint 0: Error accessing memory address 0xefbfdfdc: Bad address. I'd be grateful for any suggestions. Greg From owner-freebsd-hackers Tue Aug 19 20:41:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24799 for hackers-outgoing; Tue, 19 Aug 1997 20:41:39 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24791 for ; Tue, 19 Aug 1997 20:41:34 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id WAA22274; Tue, 19 Aug 1997 22:38:26 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA26079; Tue, 19 Aug 1997 22:21:45 -0500 Message-ID: <19970819222144.16313@right.PCS> Date: Tue, 19 Aug 1997 22:21:44 -0500 From: Jonathan Lemon To: "Jordan K. Hubbard" Cc: kudzu@dnai.com, hackers@FreeBSD.ORG Subject: Re: su: kerberos: not in root's ACL. References: <33F9ECFC.4CF@dnai.com> <1835.872037267@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <1835.872037267@time.cdrom.com>; from Jordan K. Hubbard on Aug 08, 1997 at 05:34:27PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 08, 1997 at 05:34:27PM -0700, Jordan K. Hubbard wrote: > However, what's unclear here is whether or not there is some > "historical" behavior in having a trailing : in one's path result in > an implicit inclusion of `.', something which is also a side-effect of > what happens here. Well, it isn't just historical, but is a property of every single shell I know; a null directory component is taken as an implicit '.'. This isn't just a trailing ':', but could also be a PATH like "/bin::/usr/bin". This behavior is also documented in the man page. Was there something else going on here that I missed? -- Jonathan From owner-freebsd-hackers Tue Aug 19 20:50:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25479 for hackers-outgoing; Tue, 19 Aug 1997 20:50:07 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25444 for ; Tue, 19 Aug 1997 20:49:50 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with ESMTP id JAA15858; Wed, 20 Aug 1997 09:57:10 +0700 (OSD) Date: Wed, 20 Aug 1997 09:57:10 +0700 (OSD) From: Eugeny Kuzakov To: Ruslan Shevchenko cc: freebsd-hackers@FreeBSD.ORG Subject: Re: JDK 1.1 for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Aug 1997, Ruslan Shevchenko wrote: > On Tue, 19 Aug 1997, Eugeny Kuzakov wrote: > > > > > Hi All ! > > > > Are there anyone succesfully run JDK 1.1 for FreeBSD ? > > > > I run kaffe-0.9.1, all's work. I am too...:) What about AWT ? With graphics not work... Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Tue Aug 19 20:53:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25757 for hackers-outgoing; Tue, 19 Aug 1997 20:53:29 -0700 (PDT) Received: from phobos.illtel.denver.co.us (root@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25752 for ; Tue, 19 Aug 1997 20:53:26 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id UAA05185 for ; Tue, 19 Aug 1997 20:47:00 -0700 Date: Tue, 19 Aug 1997 20:47:00 -0700 (PDT) From: Alex Belits To: hackers@freebsd.org Subject: S_ISFIFO and S_ISSOCK Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In /usr/include/sys/stat.h: #ifndef _POSIX_SOURCE [skipped] #define S_IFIFO 0010000 /* named pipe (fifo) */ [skipped] #define S_IFSOCK 0140000 /* socket */ #endif [skipped] #define S_ISFIFO(m) (((m) & 0170000) == 0010000 || \ ((m) & 0170000) == 0140000) /* fifo or socket */ #ifndef _POSIX_SOURCE [skipped] #define S_ISSOCK(m) (((m) & 0170000) == 0010000 || \ ((m) & 0170000) == 0140000) /* fifo or socket */ [skipped] #endif In other words, fifo and socket have different flags, but checks for them treat them as one? And it's mentioned that S_IFIFO is set for named pipes while in fact it's set for both anonymous and named ones, while S_IFSOCK is set for sockets only. Is it something that was left of BSD4.4 implementation of anonymous pipe as a kind of socket? But #ifndef _POSIX_SOURCE around S_ISSOCK macro looks suspicious... -- Alex From owner-freebsd-hackers Tue Aug 19 21:23:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27158 for hackers-outgoing; Tue, 19 Aug 1997 21:23:11 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27151 for ; Tue, 19 Aug 1997 21:23:07 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id VAA01541; Tue, 19 Aug 1997 21:23:03 -0700 (PDT) Date: Tue, 19 Aug 1997 21:23:03 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199708200423.VAA01541@kithrup.com> To: julian@whistle.com Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <199708182246.PAA04812@austin.polstra.com> <22405.871954857@time.cdrom.com> <19970819140010.04999@lemis.com> <199708190543.WAA07143@austin.polstra.com> Organization: Kithrup Enterprises, Ltd. Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <33FA585D.167EB0E7.kithrup.freebsd.hackers@whistle.com> you write: >John, what are the chances of being able to link a binary from >mixed a.out and elf .o files? >And what are the chances of being able to generate both types >with just a single switch differnt in the command line? With the wonders of BFD, all things are possible! Well, nearly all, anyway. Given BFD support for the a.out and ELF formats for FreeBSD, ld can accept both, and produce either. In binutils is a utility that can convert from pretty much any format to any other. (Wanna run S-records directly? Can do!) Note that this would require using the GNU binutilies. From owner-freebsd-hackers Tue Aug 19 22:09:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29477 for hackers-outgoing; Tue, 19 Aug 1997 22:09:31 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29463 for ; Tue, 19 Aug 1997 22:09:27 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA04527; Tue, 19 Aug 1997 22:09:08 -0700 (PDT) To: Sean Eric Fagan cc: julian@whistle.com, hackers@FreeBSD.ORG Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-reply-to: Your message of "Tue, 19 Aug 1997 21:23:03 PDT." <199708200423.VAA01541@kithrup.com> Date: Tue, 19 Aug 1997 22:09:08 -0700 Message-ID: <4524.872053748@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Note that this would require using the GNU binutilies. And not much of a hardship since one of the major arguments in favor of going to ELF is that it'd let us abandon some of our older, molding items in the toolchain in favor of the more actively maintained GNU code (which also dropped support for our a.out format some time back). ;-) Jordan From owner-freebsd-hackers Tue Aug 19 23:20:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02235 for hackers-outgoing; Tue, 19 Aug 1997 23:20:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02227 for ; Tue, 19 Aug 1997 23:20:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27742; Wed, 20 Aug 1997 08:20:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA24636; Wed, 20 Aug 1997 07:58:33 +0200 (MET DST) Message-ID: <19970820075833.RL47401@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 07:58:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers) Cc: imp@rover.village.org (Warner Losh) Subject: Re: fdisk and BIOS References: <19970819080618.XR34263@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Warner Losh on Aug 19, 1997 11:28:38 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Warner Losh wrote: > From memory the disk drive reported > 901c 5t 53s in demsg. fdisk reported 785c 8h 56s for both the BIOS > numbers and the incore numbers. Once I set the numbers to the ones > listed first (901, etc), fdisk reported 2047c 3h 34s for both the BIOS > and the in core numbers. Rebooting got me back to fdisk reporting the > 785c figures, even though dmesg continued to report the 901 numbers > (which agree with the Quantum ProDrive LPS numbers on the Quantum web > page). This is wd1, if that matters (and yes, it is jumpered to be > slave). More details when I can get to the machine again and run a > script. None of the numbers fdisk reported matched wd0's geometry. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ No numbers could match any actual geometry these days, unless your number of sectors per track is not constant. But how are you gonna tell this to fdisk. :-) > Also, the BIOS was configured with type 47 - 901 5 53 for this drive > (this is an old 386 that I got at a garage sale). So if the BIOS uses 901*5*53, this is the correct value, and that's also the reason why the disk reports it this way in the probe message. I'm not sure where fdisk gets its weird numbers from, but maybe there's a garbage fdisk table influencing all this. It's always a good idea to completely invalidate the fdisk table (dd if=/dev/zero of=/dev/rwd1 count=20), then perhaps even reboot (so the slice code in the kernel won't see a valid table at all). Try running fdisk afterwards. I'm too lazy to review all relevant code parts now, in order to make a prediction what would happen where. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:20:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02262 for hackers-outgoing; Tue, 19 Aug 1997 23:20:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02256 for ; Tue, 19 Aug 1997 23:20:47 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27745; Wed, 20 Aug 1997 08:20:25 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA24650; Wed, 20 Aug 1997 07:59:58 +0200 (MET DST) Message-ID: <19970820075958.TW31786@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 07:59:58 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: narvi@haldjas.folklore.ee (Narvi) Cc: hackers@FreeBSD.ORG Subject: Re: vn devices References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Narvi on Aug 19, 1997 20:31:14 +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Narvi wrote: > How does one label and newfs a vn disk under 2.2-stable? > > No matter what I say to it, it answers with > > ioctl DIOCxxxxx: Inappropriate ioctl for device vnconfig -s labels > And where is it all documented? In the man page to vnconfig(8). No sorry, i was dreaming. Only in the `usage' message. ``All documentation files usually end up in .c.'' Sigh. :( -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:20:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02286 for hackers-outgoing; Tue, 19 Aug 1997 23:20:54 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02268 for ; Tue, 19 Aug 1997 23:20:50 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27764; Wed, 20 Aug 1997 08:20:49 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA24662; Wed, 20 Aug 1997 08:03:42 +0200 (MET DST) Message-ID: <19970820080342.PN21690@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 08:03:42 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: searle@longacre.demon.co.uk (Michael Searle) Subject: Re: Fast measurement of used swap? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Michael Searle on Aug 19, 1997 17:48:43 +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Michael Searle wrote: > All the programs I've seen that do it use kvm, in fact using the > same piece of code from swapinfo. This is very slow (uses several > thousand syscalls) and also takes time proportional to the amount of > swap (whether this is used or not), so I don't want to do this > unless it's the only way. I'm afraid this is the only way. What is ``systat -vmstat'' using? I would assume this is the definitive reference implementation, since it's a system utility (as opposed to just a port). > (BTW, I'm using 2.1.0 if it matters.) I remember from merging the -current scheme into xperfmon++ that things got worse in later versions. Ah what, i might be confusing this with the network packet counting. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:21:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02308 for hackers-outgoing; Tue, 19 Aug 1997 23:21:02 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02297 for ; Tue, 19 Aug 1997 23:20:56 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27766; Wed, 20 Aug 1997 08:20:54 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA24677; Wed, 20 Aug 1997 08:06:30 +0200 (MET DST) Message-ID: <19970820080630.CM26277@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 08:06:30 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: jlemon@americantv.com (Jonathan Lemon) Subject: Re: vm86.h compile warning References: <19970819173939.43163@right.PCS> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970819173939.43163@right.PCS>; from Jonathan Lemon on Aug 19, 1997 17:39:39 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jonathan Lemon wrote: > Ugh. declares a function that takes a (struct proc *) > as a parameter, but you haven't included beforehand, so > thus this error. I see that does pull in proc.h, but too > late. > > I'm not sure what the best way to fix this is; #ifdef KERNEL around the > parameter declarations in vm86.h? That's ugly. Remember, if you're only passing struct pointers around, you are pretty much allowed using them as ``opaque structs''. Just declare ``struct proc;'' as a forward above to shut up the complaint. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:21:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02327 for hackers-outgoing; Tue, 19 Aug 1997 23:21:14 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02322 for ; Tue, 19 Aug 1997 23:21:11 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27767; Wed, 20 Aug 1997 08:21:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA24686; Wed, 20 Aug 1997 08:08:21 +0200 (MET DST) Message-ID: <19970820080821.TC63834@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 08:08:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: mrcpu@cdsnet.net (Jaye Mathisen) Subject: Re: Is there some trick to doing make in /usr/src/release? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Aug 19, 1997 14:22:52 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > I get numerous errors from the various files about syntax errors, extra > ;'s and such, and in short, it doesn't work. setenv CVSROOT /home/ncvs Needless to say, this assumes /home/ncvs actually _is_ the root of your CVS tree. Oh, you don't have one? Hmm, you're a bit of alone then... This is the release build process. You can try Julian's standalone floppy creation stuff however (it's in /usr/src/release/floppies/). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:36:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03014 for hackers-outgoing; Tue, 19 Aug 1997 23:36:19 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02997 for ; Tue, 19 Aug 1997 23:36:11 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id BAA12342 for ; Wed, 20 Aug 1997 01:41:44 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Wed, 20 Aug 1997 01:41:44 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: threads? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i recently ssaw a flurry of questions relating to threads on the 3.0 smp system, can you split threads among processors? or will they all be bound to the same CPU? ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" From owner-freebsd-hackers Tue Aug 19 23:51:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03654 for hackers-outgoing; Tue, 19 Aug 1997 23:51:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03641 for ; Tue, 19 Aug 1997 23:51:13 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27968 for hackers@FreeBSD.ORG; Wed, 20 Aug 1997 08:51:12 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA24826; Wed, 20 Aug 1997 08:24:59 +0200 (MET DST) Message-ID: <19970820082459.FC27103@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 08:24:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: gdb: Program received signal SIGTRAP? References: <19970820122215.34114@lemis.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970820122215.34114@lemis.com>; from Greg Lehey on Aug 20, 1997 12:22:15 +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > Has anybody seen problems with gdb where you can't continue from a > breakpoint? I'm currently trying to test user ppp, but once I hit a > breakpoint, I can't continue. I'm running -current as of yesterday. SIGTRAP means that gdb got a signal for a breakpoint it didn't set. This can happen if a fork() inherits a breakpoint (but i think this wouldn't show up in gdb, but only as a fatal signal to the child). Seems your context was something of a signal handler, so it wouldn't surprise me there, too. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:51:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03692 for hackers-outgoing; Tue, 19 Aug 1997 23:51:55 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03682 for ; Tue, 19 Aug 1997 23:51:52 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA27971; Wed, 20 Aug 1997 08:51:46 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA24866; Wed, 20 Aug 1997 08:35:48 +0200 (MET DST) Message-ID: <19970820083548.RY05593@uriah.heep.sax.de> Date: Wed, 20 Aug 1997 08:35:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: abelits@phobos.illtel.denver.co.us (Alex Belits) Subject: Re: S_ISFIFO and S_ISSOCK References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Alex Belits on Aug 19, 1997 20:47:00 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Alex Belits wrote: > In other words, fifo and socket have different flags, but checks for > them treat them as one? You ought to use up-to-date versions of the system... #define S_ISFIFO(m) (((m) & 0170000) == 0010000) /* fifo or socket */ #ifndef _POSIX_SOURCE #define S_ISLNK(m) (((m) & 0170000) == 0120000) /* symbolic link */ #define S_ISSOCK(m) (((m) & 0170000) == 0140000) /* socket */ #define S_ISWHT(m) (((m) & 0170000) == 0160000) /* whiteout */ #endif Well, the first comment is still wrong. > And it's mentioned that S_IFIFO is set for named > pipes while in fact it's set for both anonymous and named ones, while > S_IFSOCK is set for sockets only. 4.4BSD unnamed pipes were sockets. John Dyson rewrote the pipe code later, so they are no longer sockets now. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Aug 19 23:57:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04032 for hackers-outgoing; Tue, 19 Aug 1997 23:57:48 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA04027 for ; Tue, 19 Aug 1997 23:57:44 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA17519 for ; Wed, 20 Aug 1997 08:58:51 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id JAA02450 for freebsd-hackers@freefall.cdrom.com; Wed, 20 Aug 1997 09:00:37 +0200 (MEST) Date: Wed, 20 Aug 1997 09:00:37 +0200 (MEST) From: Christoph Kukulies Message-Id: <199708200700.JAA02450@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: yp and adduser Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk When I do an adduser in a NIS/YP environment, that is, on the NIS master, shouldn't the yp databases be updated automatically? I added a user using /usr/sbin/adduser and that user could not login at the clients until I explicitly did a make in /var/yp. (my MASTER_PASSWD is /etc/master.passwd, btw.) I thought rpc.yppasswdd woudl detect a change in MASTER_PASSWD and issue a new make run or am I wrong about the mechanism? Otherwise adduser could be augmented by adding a yp dependent action causing the yp databases to be rebuilt. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Wed Aug 20 00:08:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04529 for hackers-outgoing; Wed, 20 Aug 1997 00:08:24 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA04513 for ; Wed, 20 Aug 1997 00:08:19 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id AAA06141; Wed, 20 Aug 1997 00:28:09 -0700 Date: Wed, 20 Aug 1997 00:28:09 -0700 (PDT) From: Alex Belits To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: S_ISFIFO and S_ISSOCK In-Reply-To: <19970820083548.RY05593@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 20 Aug 1997, J Wunsch wrote: > As Alex Belits wrote: > > > In other words, fifo and socket have different flags, but checks for > > them treat them as one? > > You ought to use up-to-date versions of the system... > > #define S_ISFIFO(m) (((m) & 0170000) == 0010000) /* fifo or socket */ > #ifndef _POSIX_SOURCE > #define S_ISLNK(m) (((m) & 0170000) == 0120000) /* symbolic link */ > #define S_ISSOCK(m) (((m) & 0170000) == 0140000) /* socket */ > #define S_ISWHT(m) (((m) & 0170000) == 0160000) /* whiteout */ > #endif 3.0? > > Well, the first comment is still wrong. > > > And it's mentioned that S_IFIFO is set for named > > pipes while in fact it's set for both anonymous and named ones, while > > S_IFSOCK is set for sockets only. > > 4.4BSD unnamed pipes were sockets. John Dyson rewrote the pipe code > later, so they are no longer sockets now. I know that -- it's just was surprising that I create a socket, and then it's recognized as a pipe (my program creates pipes and sockets, and another program that is connected through them should talk to the first one differently depending on the kind of connection). Does/did anything else 4.4BSD-based behave like that? -- Alex From owner-freebsd-hackers Wed Aug 20 00:11:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04656 for hackers-outgoing; Wed, 20 Aug 1997 00:11:20 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA04651 for ; Wed, 20 Aug 1997 00:11:15 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id JAA06596; Wed, 20 Aug 1997 09:11:12 +0200 (MEST) From: Søren Schmidt Message-Id: <199708200711.JAA06596@sos.freebsd.dk> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <2068.872038843@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 19, 97 06:00:43 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 20 Aug 1997 09:11:12 +0200 (MEST) Cc: grog@lemis.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > > I think the first step is to start getting some -current testers to > > > convert to ELF and pave the way for a more general effort. Right now, > > > running a FreeBSD system 100% ELF is mostly just a theory. > > > > What do you mean by "convert to ELF"? I hope you don't mean a > > wholesale change. I'd be interested in testing it (and the BSD/OS > > stuff, too, if I can find my BSD/OS 3.0 CD-ROM), and maybe building > > some packages in ELF instead of a.out, but I wouldn't want to change > > everything at the moment. > > Well, I don't think that reasonable coverage can be obtained from > piecemeal testing so yes, I do mean a wholesale change (up to and > including the kernel). This scenario is not out of the question for > those of us with hardware dedicated specifically to testing and so I'm > hoping that such testers will come forward and help John P. start > really testing the ELF toolchain support. I'm allready on to it, I have the tools ready, and tonight I hope to do a first initial "make the world elf" shot... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Aug 20 00:49:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06507 for hackers-outgoing; Wed, 20 Aug 1997 00:49:46 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA06498 for ; Wed, 20 Aug 1997 00:49:39 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 5835 on Wed, 20 Aug 1997 07:49:21 GMT; id HAA05835 efrom: hans@brandinnovators.com; eto: UNKNOWN Received: by truk.brandinnovators.com (8.7.5/BI96070101) for <> id JAA21257; Wed, 20 Aug 1997 09:32:27 +0200 (MET DST) Message-Id: <199708200732.JAA21257@truk.brandinnovators.com> From: hans@brandinnovators.com (Hans Zuidam) Subject: Re: gdb: Program received signal SIGTRAP? To: grog@lemis.com (Greg Lehey) Date: Wed, 20 Aug 1997 09:32:27 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970820122215.34114@lemis.com> from Greg Lehey at "Aug 20, 97 12:22:15 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Greg Lehey wrote: > Has anybody seen problems with gdb where you can't continue from a > breakpoint? I'm currently trying to test user ppp, but once I hit a > breakpoint, I can't continue. I'm running -current as of yesterday. > Here's a sample: > Program received signal SIGTRAP, Trace/breakpoint trap. > DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 > 773 if (been_here_before) /* we won't be able to do it again, */ > (gdb) > Cannot insert breakpoint 0: > Error accessing memory address 0xefbfdfdc: Bad address. This is probably because your process (ppp) is corrupting its stack. gdb examines to processes stack to find proper stack frames when inserting/removing breakpoint. If the stack is corrupted gdb gets very confused. Regards, Hans -- H. Zuidam E-Mail: hans@brandinnovators.com Brand Innovators B.V. P-Mail: P.O. Box 1377 de Pinckart 54 5602 BJ Eindhoven, The Netherlands 5674 CC Nuenen Tel. +31 40 2631134, Fax. +31 40 2831138 From owner-freebsd-hackers Wed Aug 20 00:54:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06828 for hackers-outgoing; Wed, 20 Aug 1997 00:54:55 -0700 (PDT) Received: from zwei.siemens.at (zwei.siemens.at [193.81.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA06385; Wed, 20 Aug 1997 00:46:30 -0700 (PDT) Received: from p0.hai.siemens.co.at (root@firix [10.1.143.100]) by zwei.siemens.at with SMTP id JAA25302; Wed, 20 Aug 1997 09:45:53 +0200 (MET DST) Received: from zerberus.hai.siemens.co.at by p0.hai.siemens.co.at with smtp (Smail3.1.28.1 #7 for ) id m0x15Sk-00074OC; Wed, 20 Aug 97 09:45 MET DST Received: from zerberus (localhost) by zerberus.hai.siemens.co.at (4.1/SMI-4.1) id AA24257; Wed, 20 Aug 97 09:46:05 +0200 Message-Id: <33FAA0BC.41C67EA6@zerberus.hai.siemens.co.at> Date: Wed, 20 Aug 1997 09:46:04 +0200 From: Helmut Wirth Organization: Siemens AG. Österreich X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 4.1.4 sun4c) Mime-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Defect -current CTM file on freebsd.org ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I seem to have a problem getting current sources: (I have the 2.2-STABLE sources and want to upgrade to current, because I am working on parts of doscmd) I want to do my update with ctm and so I started with the file .../CTM/src-cur/src-cur.3000xEmpty.gz. I cannot get this file without errors. I fetched it three times over the last days, the last time it came without restarts (ftp reget) in one piece. All three versions of the file had the correct length (and yes, I switched to binary mode). Each of the file versions failed the following test: gzip -cd src-cur.3000xEmpty.gz >/dev/null with gzip - Invalid compressed data, crc error. ctm -v src-cur.3000xEmpty.gz fails with "corrupt patch". I uncompressed the first and the third version of the file each and looked into them: Both had indeed problems starting with the file marker "CTMFM contrib/gcc/README.FRESCO". Inside this file the text becomes garbled. Because both of the files (the first was fetched over the last weekend from ftp.freebsd.org, the third version was fetched about Wed Aug 20, 01:00:00 MET DST, also from ftp.freebsd.org) have the same problem I suspect the file on the server is defect. Could you please look into it ? Thank you Helmut PS: I only read the hackers mailing list, please reply to my mailing address. -- Helmut F. Wirth --------------- E-mail: hfwirth@ping.at E-mail (at work): wirth@zerberus.hai.siemens.co.at Tel. : +43-1-1707-37610 (at work) FAX : +43-1-1707-57602 (at work) From owner-freebsd-hackers Wed Aug 20 01:05:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA07328 for hackers-outgoing; Wed, 20 Aug 1997 01:05:27 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA07323 for ; Wed, 20 Aug 1997 01:05:18 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id IAA10822; Wed, 20 Aug 1997 08:58:16 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 20 Aug 1997 08:56:50 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <2068.872038843@time.cdrom.com> References: Your message of "Wed, 20 Aug 1997 10:23:52 +0930." <19970820102352.64876@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 20 Aug 1997 08:52:18 +0100 To: "Jordan K. Hubbard" From: Bob Bishop Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 2:00 +0100 20/8/97, Jordan K. Hubbard wrote: >[...] This scenario is not out of the question for >those of us with hardware dedicated specifically to testing and so I'm >hoping that such testers will come forward and help John P. start >really testing the ELF toolchain support. My -current machine is doing zip (apart from tracking -current) at present, so I guess I'm up for being a guinea pig (I can even do the squeaking noises :-) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Wed Aug 20 01:48:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09517 for hackers-outgoing; Wed, 20 Aug 1997 01:48:15 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA09512 for ; Wed, 20 Aug 1997 01:48:13 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id SAA08197; Wed, 20 Aug 1997 18:47:33 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id SAA29741; Wed, 20 Aug 1997 18:17:31 +0930 (CST) Message-ID: <19970820181730.19951@lemis.com> Date: Wed, 20 Aug 1997 18:17:30 +0930 From: Greg Lehey To: Hans Zuidam Cc: hackers@FreeBSD.ORG Subject: Re: gdb: Program received signal SIGTRAP? References: <19970820122215.34114@lemis.com> <199708200732.JAA21257@truk.brandinnovators.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708200732.JAA21257@truk.brandinnovators.com>; from Hans Zuidam on Wed, Aug 20, 1997 at 09:32:27AM +0200 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Aug 20, 1997 at 09:32:27AM +0200, Hans Zuidam wrote: >> Greg Lehey wrote: >> Has anybody seen problems with gdb where you can't continue from a >> breakpoint? I'm currently trying to test user ppp, but once I hit a >> breakpoint, I can't continue. I'm running -current as of yesterday. >> Here's a sample: >> Program received signal SIGTRAP, Trace/breakpoint trap. >> DoLoop () at /src/FREEBIE/usr.sbin/ppp/main.c:773 >> 773 if (been_here_before) /* we won't be able to do it again, */ >> (gdb) >> Cannot insert breakpoint 0: >> Error accessing memory address 0xefbfdfdc: Bad address. > This is probably because your process (ppp) is corrupting its stack. > gdb examines to processes stack to find proper stack frames when > inserting/removing breakpoint. If the stack is corrupted gdb gets > very confused. Really? I can't recall seeing that. In any case, the process is not corrupting its stack. If I don't set the breakpoint, it runs fine. It could be that I've shot myself in the foot, though: I updated to -current of this morning, but didn't do a make world, though I did make gdb, so that's not the immediate problem. I'm doing a make world now, and will try again afterwards. Greg From owner-freebsd-hackers Wed Aug 20 02:45:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA11660 for hackers-outgoing; Wed, 20 Aug 1997 02:45:12 -0700 (PDT) Received: from micron.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11655 for ; Wed, 20 Aug 1997 02:45:02 -0700 (PDT) Received: (from mini@localhost) by micron.efn.org (8.8.5/8.8.5) id CAA01864; Wed, 20 Aug 1997 02:45:54 -0700 (PDT) Message-ID: <19970820024553.03988@micron.efn.org> Date: Wed, 20 Aug 1997 02:45:53 -0700 From: Jonathan Mini To: hackers@freebsd.org Subject: MDA and VGA memory overlaps. Reply-To: Jonathan Mini Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e X-files: The Truth is Out There. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am writing a set of drivers that replaces the syscons driver and manages the console via two devices (and a psuedo device) where basically one device is the display, (write only) the other is the keyboard (read only) and then the psuedo device is a tty the can bind to one of each (display+keyboard pair) and possible more (such as a mouse) to implement a tty. Oh, I should mention that it would also be possible to have a tty which didn't bind a device, in that case it simply would never diplay anything (with no display) or never get input (with no keytboard), etc, etc. Well, my problem is this : The MDA memory mapping lies INSIDE the VGA memory mapping. VGA uses 0xa0000-0xaffff (for graphics) and 0xb8000-0xbffff, (for text) and the MDA uses 0xb0000-0xb0fff. One of the goals of this is to allow a system to be able to have both the mda and vga devices configured, and both successfully probe/attach within the system. My question is : What do I do for memory mapping within the device configuration? As I see it I have three chocies : a) dont' trakc memory mappings within the config, as syscons does. b) don't track memory LENGTH, and give the vga the base of 0xa0000, and assume it's base+0x18000 for the position of the text buffer, c) make two devices for the vga.. one to handle text and one to handle video. I don't even want to think about device contention, although the solution is feasable. :( Right now I am using solution b, since it is simplest to implement. -- Jonathan Mini (j_mini@efn.org) Ingenious Productions Software Development P.O. Box 5693 Eugene, Or 97405 From owner-freebsd-hackers Wed Aug 20 03:22:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA12924 for hackers-outgoing; Wed, 20 Aug 1997 03:22:17 -0700 (PDT) Received: from relay1.fnet.fr (relay1.fnet.fr [192.134.192.129]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA12914 for ; Wed, 20 Aug 1997 03:21:55 -0700 (PDT) Received: by relay1.fnet.fr (5.65c8d/96.05.03) via EUnet-France id AA27543; Wed, 20 Aug 1997 12:21:31 +0200 (MET) Received: from ramidus.lrmh.fr by desiree.lrmh.fr with SMTP (1.38.193.4/fla-2.1) id AA28469; Wed, 20 Aug 1997 12:21:15 +0200 Received: (from fla@localhost) by ramidus.lrmh.fr (8.8.5/fla-11.08.97) id MAA16140; Wed, 20 Aug 1997 12:21:10 +0200 (CEST) From: Francois LAISSUS Message-Id: <199708201021.MAA16140@ramidus.lrmh.fr> Subject: netscape's actions To: hackers@freebsd.org Date: Wed, 20 Aug 1997 12:21:10 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I need to know the equivalent of XTerm's action "insert" for mozilla 3.01 (FBSD 2.2.2) ? Plenty of actions in file Netscape.ad (app-defaults for Netscape) but nothing about that purpose. Any idea ? Thanks, François From owner-freebsd-hackers Wed Aug 20 03:41:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA13937 for hackers-outgoing; Wed, 20 Aug 1997 03:41:32 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA13932 for ; Wed, 20 Aug 1997 03:41:24 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id MAA17982; Wed, 20 Aug 1997 12:41:17 +0200 (MEST) From: Søren Schmidt Message-Id: <199708201041.MAA17982@sos.freebsd.dk> Subject: Re: MDA and VGA memory overlaps. In-Reply-To: <19970820024553.03988@micron.efn.org> from Jonathan Mini at "Aug 20, 97 02:45:53 am" To: j_mini@efn.org Date: Wed, 20 Aug 1997 12:41:17 +0200 (MEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jonathan Mini who wrote: > I am writing a set of drivers that replaces the syscons driver and manages > the console via two devices (and a psuedo device) where basically one device is > the display, (write only) the other is the keyboard (read only) and then the > psuedo device is a tty the can bind to one of each (display+keyboard pair) and > possible more (such as a mouse) to implement a tty. Oh, I should mention that > it would also be possible to have a tty which didn't bind a device, in that > case it simply would never diplay anything (with no display) or never get input > (with no keytboard), etc, etc. Hmm, why do you need this ??, or are you trying to resolve the "great unificated console" that was kind of designed a couble of years ago, but never implemented ?? > Well, my problem is this : The MDA memory mapping lies INSIDE the VGA memory > mapping. VGA uses 0xa0000-0xaffff (for graphics) and 0xb8000-0xbffff, (for > text) and the MDA uses 0xb0000-0xb0fff. One of the goals of this is to allow a > system to be able to have both the mda and vga devices configured, and both > successfully probe/attach within the system. > My question is : What do I do for memory mapping within the device > configuration? As I see it I have three chocies : > a) dont' trakc memory mappings within the config, as syscons does. > b) don't track memory LENGTH, and give the vga the base of 0xa0000, > and assume it's base+0x18000 for the position of the text buffer, > c) make two devices for the vga.. one to handle text and one to handle > video. I don't even want to think about device contention, although > the solution is feasable. :( > > Right now I am using solution b, since it is simplest to implement. Solution c is the only that will work, if you have a monochrome VGA solution b breaks... How are you going to handle the communication thats needed between the keyboard, mouse and the video driver ?? (hints: keyboard layouts, virtual consoles, mouse support, misc ioctl's) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Aug 20 04:40:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA16471 for hackers-outgoing; Wed, 20 Aug 1997 04:40:18 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA16464 for ; Wed, 20 Aug 1997 04:40:12 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id EAA17747; Wed, 20 Aug 1997 04:40:03 -0700 (PDT) Message-ID: <19970820044001.11623@hydrogen.nike.efn.org> Date: Wed, 20 Aug 1997 04:40:01 -0700 From: John-Mark Gurney To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: j_mini@efn.org, hackers@FreeBSD.ORG Subject: Re: MDA and VGA memory overlaps. References: <19970820024553.03988@micron.efn.org> <199708201041.MAA17982@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69 In-Reply-To: =?iso-8859-1?Q?=3C199708201041=2EMAA17982=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Wed=2C_Aug_20=2C_1997_at_12=3A41=3A1?= =?iso-8859-1?Q?7PM_+0200?= Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt scribbled this message on Aug 20: > In reply to Jonathan Mini who wrote: > > I am writing a set of drivers that replaces the syscons driver and manages > > the console via two devices (and a psuedo device) where basically one device is > > the display, (write only) the other is the keyboard (read only) and then the > > psuedo device is a tty the can bind to one of each (display+keyboard pair) and > > possible more (such as a mouse) to implement a tty. Oh, I should mention that > > it would also be possible to have a tty which didn't bind a device, in that > > case it simply would never diplay anything (with no display) or never get input > > (with no keytboard), etc, etc. > > Hmm, why do you need this ??, or are you trying to resolve the "great > unificated console" that was kind of designed a couble of years ago, > but never implemented ?? umm.. no, he isn't... he's working on a different project... but I didn't know that it was discussed/designed (a split keyboard/video console) a while ago... the reason I ask is that I recently got some more diskspace that will allow me to start on this project... I haven't started writing any code, but plan on working on this part.. is anyone else working or is it one of those, would be nice projects?? -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Aug 20 04:44:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA16776 for hackers-outgoing; Wed, 20 Aug 1997 04:44:38 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA16771 for ; Wed, 20 Aug 1997 04:44:33 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id NAA18145; Wed, 20 Aug 1997 13:44:33 +0200 (MEST) From: Søren Schmidt Message-Id: <199708201144.NAA18145@sos.freebsd.dk> Subject: Re: MDA and VGA memory overlaps. In-Reply-To: <19970820044001.11623@hydrogen.nike.efn.org> from John-Mark Gurney at "Aug 20, 97 04:40:01 am" To: gurney_j@resnet.uoregon.edu Date: Wed, 20 Aug 1997 13:44:33 +0200 (MEST) Cc: j_mini@efn.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to John-Mark Gurney who wrote: > > > > Hmm, why do you need this ??, or are you trying to resolve the "great > > unificated console" that was kind of designed a couble of years ago, > > but never implemented ?? > > umm.. no, he isn't... he's working on a different project... but > I didn't know that it was discussed/designed (a split keyboard/video > console) a while ago... That still doesn't answer the question, "why do you need this" then.. > the reason I ask is that I recently got some more diskspace that will > allow me to start on this project... I haven't started writing any > code, but plan on working on this part.. is anyone else working or > is it one of those, would be nice projects?? WHAT project ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Aug 20 04:52:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA17045 for hackers-outgoing; Wed, 20 Aug 1997 04:52:43 -0700 (PDT) Received: from micron.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17031 for ; Wed, 20 Aug 1997 04:52:33 -0700 (PDT) Received: (from mini@localhost) by micron.efn.org (8.8.5/8.8.5) id EAA02074; Wed, 20 Aug 1997 04:52:57 -0700 (PDT) Message-ID: <19970820045256.50922@micron.efn.org> Date: Wed, 20 Aug 1997 04:52:56 -0700 From: Jonathan Mini To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: hackers@FreeBSD.ORG Subject: Re: MDA and VGA memory overlaps. Reply-To: Jonathan Mini References: <19970820024553.03988@micron.efn.org> <199708201041.MAA17982@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.76e In-Reply-To: =?iso-8859-1?Q?=3C199708201041=2EMAA17982=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Wed=2C_Aug_20=2C_1997_at_12=3A41=3A1?= =?iso-8859-1?Q?7PM_+0200?= X-files: The Truth is Out There. Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt stands accused of saying : > In reply to Jonathan Mini who wrote: > > I am writing a set of drivers that replaces the syscons driver and manages > > the console via two devices (and a psuedo device) where basically one device is > > the display, (write only) the other is the keyboard (read only) and then the > > psuedo device is a tty the can bind to one of each (display+keyboard pair) and > > possible more (such as a mouse) to implement a tty. Oh, I should mention that > > it would also be possible to have a tty which didn't bind a device, in that > > case it simply would never diplay anything (with no display) or never get input > > (with no keytboard), etc, etc. > > Hmm, why do you need this ??, or are you trying to resolve the "great > unificated console" that was kind of designed a couble of years ago, > but never implemented ?? Nahh. Not "great unificated console" here. Just my perversions to FreeBSD's kernel. One thing I should say is that I don't really plan on making this a wonderous all purpose console driver for FreeBSD general use, in fact, I dont' really plan on releasing the sources, although I have nothing against it :) (I figure that unless I am bound by some legal restriction (read NDA bites) I automatically determine FreeBSD-specific code (such as a driver) to be BSD copywritten :)) Two main reasons : 1) I am going to be running a kernel where (in the end) tty emulation, vtys, etc, etc won't be needed, but graphics output, support for multiple monitors, and the keyboard input will be needed. 2) In the mean time, I want my mono monitor to be able to act as a console for debugging while my VGA monitor shows off the pretty real-time rendering my system is doing. (read debugging console) So, basically, I want to reduce as much bloat as possible, but need to deal with multiple monitors, keyboards, (I have a few keyboards laying around that do input via various fun methods like the parrallel port and serial port) and also multiple methods of accessing display hardware, such as VESA VBE. Mainly, it's "I needed to write a custom console driver, and this was the way I decided to implement it." In the end, I can replace the tty emulator with something like a Teletype emulator, and forget about it. :) > > Well, my problem is this : The MDA memory mapping lies INSIDE the VGA memory > > mapping. VGA uses 0xa0000-0xaffff (for graphics) and 0xb8000-0xbffff, (for > > text) and the MDA uses 0xb0000-0xb0fff. One of the goals of this is to allow a > > system to be able to have both the mda and vga devices configured, and both > > successfully probe/attach within the system. > > My question is : What do I do for memory mapping within the device > > configuration? As I see it I have three chocies : > > a) dont' trakc memory mappings within the config, as syscons does. > > b) don't track memory LENGTH, and give the vga the base of 0xa0000, > > and assume it's base+0x18000 for the position of the text buffer, > > c) make two devices for the vga.. one to handle text and one to handle > > video. I don't even want to think about device contention, although > > the solution is feasable. :( > > > > Right now I am using solution b, since it is simplest to implement. > > Solution c is the only that will work, if you have a monochrome VGA > solution b breaks... If I have a mono VGA card, I can't implement an MDA driver that will coexist with the VGA card, as the two cards would conflict in port addresses. (the mono VGA card uses the MDA's port address) > How are you going to handle the communication thats needed between the > keyboard, mouse and the video driver ?? > (hints: keyboard layouts, virtual consoles, mouse support, misc ioctl's) What's the problem with ioctls? an ioctl would exist to give you the devices the tty emulator was attached to.. from there, you access the device directly if you need to do something the tty emulator doesn't do. (I am assuming you'd "borrow" the device from the tty emulator, so it wouldn't do i/o on that device until you were done. Bleh : keyboard layouts - I plan on there being _two_ modes of keyboard interface. One is used via mmap, the other with read. The mmap method simply gives you a mapped array that states the current status of each key on the keyboard, listed by scancode. I am assuming that the using process/device knows how to interpret that info. The second, via read, gives out ASCII data, in a char-by-char basis, as it is available, i.e. when you press the A key, it spits out an A, on the basis of a keymap lookup. IOCTL's would be used to determine what keymap to use, how it will handle keys not expressed in the ASCII set, but that method gives me the basic typematic support I need. mouse - Actually, I don't plan on implementing mouse support into the tty emulator, since I personally will never use it. I just listed it becuase it was an example of another device you'd want to attach to a tty. (I view the tty as a general "holder" with a simple interface.. pass it to a process, and say "oh, you get to have these devices now") I would think just about any input or output related device could be attached in that manner. (good example is a lightpen or similar device) The tty emulator is responsible for managing what the user DOES with the mouse, so the other code doesn't need to deal with that. (such as the display) The display WOULD have to know how to display a mouse cursor, but oh well. display - all the display does is display stuff. it handles two things : a) dump buffer to real screen buffer. b) dump buffer to real screen buffer through some translation. The only translation I forsee is conversion from a standard text framebuffer type to the framebuffer type for the current video mode. virtual consoles - one per tty emulatior, each emulator stores a framebuffer, and when you switch, the emulator loosing the device stops writing to it, and the emulator gaining it starts writing. In effect, each tty emulator is a virtual console, and it handles it's own info itself. It only uses a display when it has one. Same with keyboard. tty emulators would handle the switches. Basically, it offloads as much "bloat" as possible to the tty emulator, and then whne I dont' compile one into my kernel, I easily remove that bloat from my kernel, and I leave in the support for console i/o that my code needs. (stuff like graphics code) > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. -- Jonathan Mini (j_mini@efn.org) Ingenious Productions Software Development P.O. Box 5693 Eugene, Or 97405 From owner-freebsd-hackers Wed Aug 20 04:53:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA17069 for hackers-outgoing; Wed, 20 Aug 1997 04:53:08 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA17063 for ; Wed, 20 Aug 1997 04:53:01 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id EAA20478; Wed, 20 Aug 1997 04:52:54 -0700 (PDT) Message-ID: <19970820045253.28684@hydrogen.nike.efn.org> Date: Wed, 20 Aug 1997 04:52:53 -0700 From: John-Mark Gurney To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: j_mini@efn.org, hackers@FreeBSD.ORG Subject: Re: MDA and VGA memory overlaps. References: <19970820044001.11623@hydrogen.nike.efn.org> <199708201144.NAA18145@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.69 In-Reply-To: =?iso-8859-1?Q?=3C199708201144=2ENAA18145=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Wed=2C_Aug_20=2C_1997_at_01=3A44=3A3?= =?iso-8859-1?Q?3PM_+0200?= Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Søren Schmidt scribbled this message on Aug 20: > In reply to John-Mark Gurney who wrote: > > > > > > Hmm, why do you need this ??, or are you trying to resolve the "great > > > unificated console" that was kind of designed a couble of years ago, > > > but never implemented ?? > > > > umm.. no, he isn't... he's working on a different project... but > > I didn't know that it was discussed/designed (a split keyboard/video > > console) a while ago... > > That still doesn't answer the question, "why do you need this" then.. he should answer that one... > > the reason I ask is that I recently got some more diskspace that will > > allow me to start on this project... I haven't started writing any > > code, but plan on working on this part.. is anyone else working or > > is it one of those, would be nice projects?? > > WHAT project ?? sorry.. I don't always include enough context.. I was replying to this part: > > > [...] or are you trying to resolve the "great > > > unificated console" that was kind of designed a couble of years ago, > > > but never implemented ?? i.e. the implied discussion of splitting the keyboard/video into seperate parts... and actual specs of what the team descided it should end up looking like... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Aug 20 05:15:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17996 for hackers-outgoing; Wed, 20 Aug 1997 05:15:29 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17988 for ; Wed, 20 Aug 1997 05:15:25 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id OAA18223; Wed, 20 Aug 1997 14:15:25 +0200 (MEST) From: Søren Schmidt Message-Id: <199708201215.OAA18223@sos.freebsd.dk> Subject: Re: MDA and VGA memory overlaps. In-Reply-To: <19970820045253.28684@hydrogen.nike.efn.org> from John-Mark Gurney at "Aug 20, 97 04:52:53 am" To: gurney_j@resnet.uoregon.edu Date: Wed, 20 Aug 1997 14:15:25 +0200 (MEST) Cc: j_mini@efn.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to John-Mark Gurney who wrote: > > > > WHAT project ?? > > sorry.. I don't always include enough context.. I was replying to > this part: > > > > [...] or are you trying to resolve the "great > > > > unificated console" that was kind of designed a couble of years ago, > > > > but never implemented ?? > > i.e. the implied discussion of splitting the keyboard/video into > seperate parts... and actual specs of what the team descided it should > end up looking like... Ahh, that has been discussed, and a general solution has also been found years ago, check the archives way back (or check terry :) ) The problem is that there is no "real" solution to this, it always ends up with alot of compromises, the current one being the splitout of the keyboard stuff into kbdio.c, the rest cannot truely be seperated if the current functionality is to be preserved. Belive me, I've been there more times than I care about being the "father" of syscons... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Wed Aug 20 13:32:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07741 for hackers-outgoing; Wed, 20 Aug 1997 13:32:09 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA07733 for ; Wed, 20 Aug 1997 13:32:04 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id WAA07714 for hackers@FreeBSD.org; Wed, 20 Aug 1997 22:31:56 +0200 (SAT) From: Paul Allenby Message-Id: <199708202031.WAA07714@zibbi.mikom.csir.co.za> Subject: make world To: hackers@FreeBSD.org Date: Wed, 20 Aug 1997 22:31:56 +0200 (SAT) 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 X-Loop: FreeBSD.org Precedence: bulk Hi all Maybe I missed a commit message, or nothing has been done about the following "make buildworld" breakage on -current yet? spray_xdr.c:6: spray.h: No such file or directory yppasswd_xdr.c:6: yppasswd.h: No such file or directory ypxfrd_xdr.c:6: ypxfrd.h: No such file or directory ypupdate_prot_xdr.c:6: ypupdate_prot.h: No such file or directory mkdep: compile failed *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Please correct me if I'm wrong :) Paul From owner-freebsd-hackers Wed Aug 20 16:08:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14841 for hackers-outgoing; Wed, 20 Aug 1997 16:08:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA14830 for ; Wed, 20 Aug 1997 16:08:18 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA21101; Wed, 20 Aug 1997 15:55:31 -0700 From: Terry Lambert Message-Id: <199708202255.PAA21101@phaeton.artisoft.com> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] To: jamie@itribe.net (Jamie Bowden) Date: Wed, 20 Aug 1997 15:55:31 -0700 (MST) Cc: jdp@polstra.com, grog@lemis.com, hackers@FreeBSD.ORG In-Reply-To: <199708191311.JAA22884@gatekeeper.itribe.net> from "Jamie Bowden" at Aug 19, 97 09:14:21 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, Terry will be happy. On a more serious note, what is the objection > to moving to ELF, other than the time involved? I am ecstatic. So quite rocking the boat. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:08:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14868 for hackers-outgoing; Wed, 20 Aug 1997 16:08:47 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA14860 for ; Wed, 20 Aug 1997 16:08:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA21119; Wed, 20 Aug 1997 15:59:08 -0700 From: Terry Lambert Message-Id: <199708202259.PAA21119@phaeton.artisoft.com> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] To: grog@lemis.com (Greg Lehey) Date: Wed, 20 Aug 1997 15:59:08 -0700 (MST) Cc: jkh@time.cdrom.com, hackers@FreeBSD.ORG In-Reply-To: <19970820102352.64876@lemis.com> from "Greg Lehey" at Aug 20, 97 10:23:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > What do you mean by "convert to ELF"? I hope you don't mean a > wholesale change. Why not? > I'd be interested in testing it (and the BSD/OS > stuff, too, if I can find my BSD/OS 3.0 CD-ROM), and maybe building > some packages in ELF instead of a.out, but I wouldn't want to change > everything at the moment. Why not? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14956 for hackers-outgoing; Wed, 20 Aug 1997 16:11:00 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA14947 for ; Wed, 20 Aug 1997 16:10:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21136; Wed, 20 Aug 1997 16:01:47 -0700 From: Terry Lambert Message-Id: <199708202301.QAA21136@phaeton.artisoft.com> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 20 Aug 1997 16:01:47 -0700 (MST) Cc: sef@kithrup.com, julian@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <4524.872053748@time.cdrom.com> from "Jordan K. Hubbard" at Aug 19, 97 10:09:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Note that this would require using the GNU binutilies. > > And not much of a hardship since one of the major arguments in favor > of going to ELF is that it'd let us abandon some of our older, molding > items in the toolchain in favor of the more actively maintained GNU > code (which also dropped support for our a.out format some time > back). ;-) That is Sean's point, I think. To handle the transition piecemeal, as some seem to want to do (it;s a compromise position, but if a compromise is necessary to let some people remain backwards a bit longer so everyone can go foraward, so be it), would require adding the a.out support back into binutils. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:16:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15332 for hackers-outgoing; Wed, 20 Aug 1997 16:16:54 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA15152 for ; Wed, 20 Aug 1997 16:14:17 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id JAA11783 for ; Thu, 21 Aug 1997 09:13:44 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id IAA00402; Thu, 21 Aug 1997 08:42:28 +0930 (CST) Message-ID: <19970821084227.64768@lemis.com> Date: Thu, 21 Aug 1997 08:42:27 +0930 From: Greg Lehey To: Terry Lambert Cc: FreeBSD Hackers Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] References: <19970820102352.64876@lemis.com> <199708202259.PAA21119@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708202259.PAA21119@phaeton.artisoft.com>; from Terry Lambert on Wed, Aug 20, 1997 at 03:59:08PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Aug 20, 1997 at 03:59:08PM -0700, Terry Lambert wrote: > > What do you mean by "convert to ELF"? I hope you don't mean a > > wholesale change. > > Why not? Because I don't have the time at the moment. I'm too busy finding out why libc.so.3.0 doesn't build in -current, and thus blows my world out of the water. Of course, if somebody could show me (or make it plausible) that this would be possible without causing particular compatibility problems, I might change my mind. What I really don't understand is why a wholesale changeover should be necessary: I certainly hope that the new system will still be able to run a.out executables. > > I'd be interested in testing it (and the BSD/OS > > stuff, too, if I can find my BSD/OS 3.0 CD-ROM), and maybe building > > some packages in ELF instead of a.out, but I wouldn't want to change > > everything at the moment. > > Why not? See rule 1. Greg From owner-freebsd-hackers Wed Aug 20 16:17:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15363 for hackers-outgoing; Wed, 20 Aug 1997 16:17:42 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15355 for ; Wed, 20 Aug 1997 16:17:37 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.8.5/8.6.6) id QAA10222; Wed, 20 Aug 1997 16:17:07 -0700 (PDT) Date: Wed, 20 Aug 1997 16:17:07 -0700 (PDT) From: Sean Eric Fagan Message-Id: <199708202317.QAA10222@kithrup.com> To: jkh@time.cdrom.com, terry@lambert.org Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] Cc: hackers@FreeBSD.ORG, julian@whistle.com Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> And not much of a hardship since one of the major arguments in favor >> of going to ELF is that it'd let us abandon some of our older, molding >> items in the toolchain in favor of the more actively maintained GNU >> code (which also dropped support for our a.out format some time >> back). ;-) >That is Sean's point, I think. To handle the transition piecemeal, >as some seem to want to do (it;s a compromise position, but if a >compromise is necessary to let some people remain backwards a bit >longer so everyone can go foraward, so be it), would require adding >the a.out support back into binutils. Actually, that was only *part* of my point. (I've got a binutils here. It configures for freebsd, but doesn't seem to recognize the a.out. I'll keep poking at it.) My main point was that we would pretty much be wedded to the GNU binutils in order to produce both formats. This, as most of you know, doesn't bother me at all -- they're there, they work, they're freely distributable. Other people have their own problems. One problem is that libbfd is pretty darned large. (As one would expect from a library that has the guts of nm, ar, ranlib, and a few others in it.) Making it a shared library will, of course, help considerably, and that's fine. But I want people to be aware of this. Sean. From owner-freebsd-hackers Wed Aug 20 16:25:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15656 for hackers-outgoing; Wed, 20 Aug 1997 16:25:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA15650 for ; Wed, 20 Aug 1997 16:25:30 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21163; Wed, 20 Aug 1997 16:17:28 -0700 From: Terry Lambert Message-Id: <199708202317.QAA21163@phaeton.artisoft.com> Subject: Re: threads? To: perlsta@sunyit.edu (Alfred Perlstein) Date: Wed, 20 Aug 1997 16:17:28 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Aug 20, 97 01:41:44 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i recently ssaw a flurry of questions relating to threads on the 3.0 smp > system, can you split threads among processors? or will they all be bound > to the same CPU? "Can you now" and "will you be able to" are two different questions. I know John Dyson has kernel threads, and they will work between processors; you can ask him for his "magic user space pieces" or wait for a checking of some kind, either way. I'm sure he'd love informed commentary on the code... "Can you now" is a definite "no", without John's stuff. I don't know whether he is attacking this as a cooperative scheduler, but the rume is that he is. If so, there are CPU affinitiy issues that may ned addressing... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:36:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16074 for hackers-outgoing; Wed, 20 Aug 1997 16:36:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA16069 for ; Wed, 20 Aug 1997 16:36:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21184; Wed, 20 Aug 1997 16:26:27 -0700 From: Terry Lambert Message-Id: <199708202326.QAA21184@phaeton.artisoft.com> Subject: Re: su: kerberos: not in root's ACL. To: jlemon@americantv.com (Jonathan Lemon) Date: Wed, 20 Aug 1997 16:26:27 -0700 (MST) Cc: jkh@time.cdrom.com, kudzu@dnai.com, hackers@FreeBSD.ORG In-Reply-To: <19970819222144.16313@right.PCS> from "Jonathan Lemon" at Aug 19, 97 10:21:44 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > However, what's unclear here is whether or not there is some > > "historical" behavior in having a trailing : in one's path result in > > an implicit inclusion of `.', something which is also a side-effect of > > what happens here. > > Well, it isn't just historical, but is a property of every single shell > I know; a null directory component is taken as an implicit '.'. This > isn't just a trailing ':', but could also be a PATH like "/bin::/usr/bin". > > This behavior is also documented in the man page. Was there something > else going on here that I missed? Yes: % ls -l /home/terry/morestuff lrwxrwxrwx 1 terry staff 8 Jun 9 1996 /home/terry/morestuff -> /b/terry % ls -l /home/terry/morestuff/ total 7210 drwxrwxr-x 2 terry wheel 512 Sep 30 1996 DOC drwxrwxr-x 4 terry staff 512 Jul 31 12:42 ELF drwxrwxr-x 2 terry wheel 512 Nov 4 1996 FDISK drwxrwxr-x 2 terry staff 512 Sep 24 1996 FS -rw------- 1 terry staff 23552 May 10 1996 I15_E820.DOC drwxrwxr-x 3 terry wheel 512 Nov 5 1996 LDAP drwxrwxr-x 5 terry wheel 512 Aug 8 14:52 MIME drwxrwxr-x 2 terry wheel 512 Jan 26 1997 PCTS drwxrwxr-x 2 terry wheel 512 Oct 10 1996 RLOCK drwxrwxr-x 2 terry wheel 512 Apr 5 16:33 SMB -rw------- 1 terry staff 11319 Dec 8 1995 SMP.cur drwxrwxr-x 7 terry wheel 512 Aug 27 1996 SYSINIT drwxrwxr-x 2 terry staff 512 Sep 24 1996 UNI drwxr-xr-x 2 terry wheel 512 Oct 18 1996 WIN95 drwxrwxr-x 2 terry wheel 512 Jun 27 1996 dll -rw-rw-r-- 1 terry wheel 371840 Jun 21 1996 draft-heizer-cifs-v1-spec-00.txt ... The additional "." assumed for the "" component following the trailing "/" allows override for "target of symbolic link" in place of "symbolic link". This is: 1) On purpose 2) A very, very good feature 3) Handy as hell Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:39:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16167 for hackers-outgoing; Wed, 20 Aug 1997 16:39:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA16162 for ; Wed, 20 Aug 1997 16:39:52 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21196; Wed, 20 Aug 1997 16:30:28 -0700 From: Terry Lambert Message-Id: <199708202330.QAA21196@phaeton.artisoft.com> Subject: Re: yp and adduser To: kuku@gilberto.physik.RWTH-Aachen.DE (Christoph Kukulies) Date: Wed, 20 Aug 1997 16:30:28 -0700 (MST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199708200700.JAA02450@gil.physik.rwth-aachen.de> from "Christoph Kukulies" at Aug 20, 97 09:00:37 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > When I do an adduser in a NIS/YP environment, that is, on the NIS > master, shouldn't the yp databases be updated automatically? > > I added a user using /usr/sbin/adduser and that user could not login > at the clients until I explicitly did a make in /var/yp. > > (my MASTER_PASSWD is /etc/master.passwd, btw.) It is possible for these to be seperate. The problem is the lack of an event notification when they are not. This is not really a big issue, unless you are adding one user at a time, since an administrative task of adding a bunch of users should be terminated by the asmin doing the make (it doesn't make sense to do it 1000 times after adding 1000 users. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:44:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16394 for hackers-outgoing; Wed, 20 Aug 1997 16:44:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA16388 for ; Wed, 20 Aug 1997 16:44:13 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21244; Wed, 20 Aug 1997 16:35:28 -0700 From: Terry Lambert Message-Id: <199708202335.QAA21244@phaeton.artisoft.com> Subject: Re: Please Help Me Understand dlopen()] To: schinagl@avl.co.at (Hermann Schinagl) Date: Wed, 20 Aug 1997 16:35:28 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970819085282.NTM1204@umes01.avl.co.at> from "Hermann Schinagl" at Aug 19, 97 08:52:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You forgot that the symbols, which are exported by the lib are > totally different, if you rename a .c file to .cpp and compile > it again. ==> C++ exported symbols > > Well, it is easy to add '_' before the symbol, but the function-arguments > of a C++ exported function are append encoded to the symbolname. > eg.: '__func027_dfiv' > > So writing a wrapper is not that straight forward as mentioned > above. You should also think of the C++ exporting mechanism. How do you return a non-NULL pointer with argument type information for symbol space munging, per C++? We all know that the name is not the correct place to mung the symbol, but for some reason, we are married to stupid linkers and less-than-clevel object file symbol table formats. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 16:45:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16500 for hackers-outgoing; Wed, 20 Aug 1997 16:45:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA16491 for ; Wed, 20 Aug 1997 16:45:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA21254; Wed, 20 Aug 1997 16:38:09 -0700 From: Terry Lambert Message-Id: <199708202338.QAA21254@phaeton.artisoft.com> Subject: Re: smbfs To: Anthony.Kimball@East.Sun.COM Date: Wed, 20 Aug 1997 16:38:09 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199708190659.BAA27054@compound.east.sun.com> from "Tony Kimball" at Aug 19, 97 01:59:27 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Has anyone done work on smbfs for FreeBSD? Yes, off an on. See the -hackers and -current list archives for "SMBFS". Pay special attention to the security model problems between "per request credentials" vs. "per connection credentials" with regard to multiuser systems. CIFS resolves some of this by supporting "per request credentials" via Kerberos tickets. The LanMan protocols prior to CIFS had serious issues which could only be addressed through a much more complex session management facility (which no one but Novell has written yet). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 20 17:42:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA19005 for hackers-outgoing; Wed, 20 Aug 1997 17:42:28 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA18998 for ; Wed, 20 Aug 1997 17:42:23 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id TAA04787; Wed, 20 Aug 1997 19:41:22 -0500 (EST) From: "John S. Dyson" Message-Id: <199708210041.TAA04787@dyson.iquest.net> Subject: Re: threads? In-Reply-To: <199708202317.QAA21163@phaeton.artisoft.com> from Terry Lambert at "Aug 20, 97 04:17:28 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 20 Aug 1997 19:41:22 -0500 (EST) Cc: perlsta@sunyit.edu, hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > > i recently ssaw a flurry of questions relating to threads on the 3.0 smp > > system, can you split threads among processors? or will they all be bound > > to the same CPU? > > "Can you now" and "will you be able to" are two different questions. > > I know John Dyson has kernel threads, and they will work between > processors; you can ask him for his "magic user space pieces" or > wait for a checking of some kind, either way. I'm sure he'd love > informed commentary on the code... > > "Can you now" is a definite "no", without John's stuff. > > > I don't know whether he is attacking this as a cooperative scheduler, > but the rume is that he is. If so, there are CPU affinitiy issues > that may ned addressing... > Right now, the code is rough, and I haven't worked on it for about 1mo or so. Soon to work on it again, but SMP has almost all of my attention. BTW, *I always try to work in a cooperative manner* :-). John From owner-freebsd-hackers Wed Aug 20 19:32:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23527 for hackers-outgoing; Wed, 20 Aug 1997 19:32:34 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23518 for ; Wed, 20 Aug 1997 19:32:32 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id VAA24314; Wed, 20 Aug 1997 21:51:17 -0500 (CDT) Received: (jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA20872; Wed, 20 Aug 1997 21:33:58 -0500 Message-ID: <19970820213357.64825@right.PCS> Date: Wed, 20 Aug 1997 21:33:57 -0500 From: Jonathan Lemon To: Terry Lambert Cc: jkh@time.cdrom.com, kudzu@dnai.com, hackers@FreeBSD.ORG Subject: Re: su: kerberos: not in root's ACL. References: <19970819222144.16313@right.PCS> <199708202326.QAA21184@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199708202326.QAA21184@phaeton.artisoft.com>; from Terry Lambert on Aug 08, 1997 at 04:26:27PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 08, 1997 at 04:26:27PM -0700, Terry Lambert wrote: > > > However, what's unclear here is whether or not there is some > > > "historical" behavior in having a trailing : in one's path result in > > > an implicit inclusion of `.', something which is also a side-effect of > > > what happens here. > > > > Well, it isn't just historical, but is a property of every single shell > > I know; a null directory component is taken as an implicit '.'. This > > isn't just a trailing ':', but could also be a PATH like "/bin::/usr/bin". > > > > This behavior is also documented in the man page. Was there something > > else going on here that I missed? [ snip ] The topic was null directory components in the _shell's_ PATH being a shorthand for adding ``.'' to the _shell's_ search path, not namei's behavior when given a null directory component. The comment about missing something was because I originally had no idea as to what this had to do with kerberos. -- Jonathan From owner-freebsd-hackers Wed Aug 20 21:38:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28681 for hackers-outgoing; Wed, 20 Aug 1997 21:38:15 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28668 for ; Wed, 20 Aug 1997 21:38:08 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id VAA25909; Wed, 20 Aug 1997 21:37:58 -0700 (PDT) Message-ID: <19970820213758.07070@hydrogen.nike.efn.org> Date: Wed, 20 Aug 1997 21:37:58 -0700 From: John-Mark Gurney To: Paul Allenby Cc: hackers@FreeBSD.ORG Subject: Re: make world References: <199708202031.WAA07714@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199708202031.WAA07714@zibbi.mikom.csir.co.za>; from Paul Allenby on Wed, Aug 20, 1997 at 10:31:56PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Paul Allenby scribbled this message on Aug 20: > Hi all > > Maybe I missed a commit message, or nothing has been done about the > following "make buildworld" breakage on -current yet? I posted a patch to -current last night... basicly src/includes/rpcsvc wasn't being installed... a make includehdrs was being done in src/include but wasn't installing the headers in rpcsvc... assuming no one complains I'll just commit my changes... oh.. and if your building -current.. post messages like these to current were you should be listening for stuff like this... ttyl... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Wed Aug 20 22:24:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00271 for hackers-outgoing; Wed, 20 Aug 1997 22:24:03 -0700 (PDT) Received: from roundtable.cif.rochester.edu (sadmin@roundtable.cif.rochester.edu [128.151.220.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA00241 for ; Wed, 20 Aug 1997 22:24:00 -0700 (PDT) Received: (from sadmin@localhost) by roundtable.cif.rochester.edu (8.8.6/8.8.3) id BAA29273 for freebsd-hackers@freebsd.org; Thu, 21 Aug 1997 01:23:15 -0400 (EDT) From: Security Administrator Message-Id: <199708210523.BAA29273@roundtable.cif.rochester.edu> Subject: chown,chgrp To: freebsd-hackers@freebsd.org (FreeBSD Hackers) Date: Thu, 21 Aug 1997 01:23:15 -0400 (EDT) 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 X-Loop: FreeBSD.org Precedence: bulk Hi there, I'm sure that this has been covered at great length, but I've missed the discussion. Does anyone know that chgrp and chown are broken on symbolic links. Even if I specify the -RH, -RL, or -RHL flags (I tried each combination), it didn't work. Lemme know if this has been resolved or if I'm doing something wrong. I am using FreeBSD 2.2.2. JP -- System Security Administrator Computer Interest Floor University of Rochester Rochester, NY 14627 sadmin@roundtable.cif.rochester.edu From owner-freebsd-hackers Wed Aug 20 23:15:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01692 for hackers-outgoing; Wed, 20 Aug 1997 23:15:31 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA01684 for ; Wed, 20 Aug 1997 23:15:27 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13538; Thu, 21 Aug 1997 08:15:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA29536; Thu, 21 Aug 1997 08:05:10 +0200 (MET DST) Message-ID: <19970821080509.CY28575@uriah.heep.sax.de> Date: Thu, 21 Aug 1997 08:05:09 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG (FreeBSD Hackers) Cc: sadmin@roundtable.cif.rochester.edu (Security Administrator) Subject: Re: chown,chgrp References: <199708210523.BAA29273@roundtable.cif.rochester.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708210523.BAA29273@roundtable.cif.rochester.edu>; from Security Administrator on Aug 21, 1997 01:23:15 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Security Administrator wrote: > I'm sure that this has been covered at great length, but I've missed the > discussion. Does anyone know that chgrp and chown are broken on > symbolic links. Even if I specify the -RH, -RL, or -RHL flags (I tried > each combination), it didn't work. j@uriah 200% ln -s foo . j@uriah 201% ls -l foo lrwxrwxrwx 1 j bin 3 Aug 21 08:00 foo@ -> foo j@uriah 202% chgrp -h cvs foo j@uriah 203% ls -l foo lrwxrwxrwx 1 j cvs 3 Aug 21 08:00 foo@ -> foo Note that if you're using a historic version of 4.4BSD (anything prior to 2.2.2, or prior to 1997/03/31 in -current for FreeBSD), this was broken on purpose; symlinks didn't have user-changeable attributes there at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Wed Aug 20 23:41:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03087 for hackers-outgoing; Wed, 20 Aug 1997 23:41:55 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03079 for ; Wed, 20 Aug 1997 23:41:52 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id QAA28488; Thu, 21 Aug 1997 16:39:23 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id QAA02274; Thu, 21 Aug 1997 16:09:22 +0930 (CST) Message-ID: <19970821160921.03779@lemis.com> Date: Thu, 21 Aug 1997 16:09:21 +0930 From: Greg Lehey To: Mike Smith Cc: Terry Lambert , FreeBSD Hackers Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) References: <19970821084227.64768@lemis.com> <199708210151.LAA00453@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708210151.LAA00453@word.smith.net.au>; from Mike Smith on Thu, Aug 21, 1997 at 11:20:35AM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Aug 21, 1997 at 11:20:35AM +0930, Mike Smith wrote: >> Of course, if somebody could show me (or make it plausible) that this >> would be possible without causing particular compatibility problems, >> I might change my mind. What I really don't understand is why a >> wholesale changeover should be necessary: I certainly hope that the >> new system will still be able to run a.out executables. > > You should spend some time reading back-issued of the hackers > digest. Right, I *should*. I'm running as fast as I can just to stay where I am. > Can you honestly imagine any such an idea gaining any sort of currency > without this basic criterion being met? No. Well, yes, but it would surprise me. > The entire idea with building mixed-flavour tools is to be able to avoid > a one-hit cutover; you should be able to work with a mixture of a.out > and ELF tools transparently. OK. That's just what I originally thought. But Jordan's message suggested that I should cut over in one swell foop. Greg From owner-freebsd-hackers Wed Aug 20 23:57:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03948 for hackers-outgoing; Wed, 20 Aug 1997 23:57:11 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03938 for ; Wed, 20 Aug 1997 23:57:01 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA00319; Thu, 21 Aug 1997 16:24:37 +0930 (CST) Message-Id: <199708210654.QAA00319@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Mike Smith , Terry Lambert , FreeBSD Hackers Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) In-reply-to: Your message of "Thu, 21 Aug 1997 16:09:21 +0930." <19970821160921.03779@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Aug 1997 16:24:35 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > > You should spend some time reading back-issued of the hackers > > digest. > > Right, I *should*. I'm running as fast as I can just to stay where I > am. Under the circumstances, perhaps a slightly less vehement denunciation of the concept might be indicated then? I'd always be happy to summarise the discussion to date if you wanted to drop me a line. > > Can you honestly imagine any such an idea gaining any sort of currency > > without this basic criterion being met? > > No. Well, yes, but it would surprise me. You have little faith in the conservatism of others 8) > > The entire idea with building mixed-flavour tools is to be able to avoid > > a one-hit cutover; you should be able to work with a mixture of a.out > > and ELF tools transparently. > > OK. That's just what I originally thought. But Jordan's message > suggested that I should cut over in one swell foop. Jordan is looking for developers willing to test the cutover and eradicate problems. At some stage, a 'make world' or (more likely) an / etc/make.conf update will have you suddenly generating ELF objects by default, once it's clear it works. Until then, sleep easy 8) mike From owner-freebsd-hackers Thu Aug 21 00:01:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04173 for hackers-outgoing; Thu, 21 Aug 1997 00:01:04 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA04163 for ; Thu, 21 Aug 1997 00:00:59 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id RAA28967; Thu, 21 Aug 1997 17:00:26 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id QAA05539; Thu, 21 Aug 1997 16:30:25 +0930 (CST) Message-ID: <19970821163025.05196@lemis.com> Date: Thu, 21 Aug 1997 16:30:25 +0930 From: Greg Lehey To: Mike Smith Cc: FreeBSD Hackers Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) References: <19970821160921.03779@lemis.com> <199708210654.QAA00319@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708210654.QAA00319@word.smith.net.au>; from Mike Smith on Thu, Aug 21, 1997 at 04:24:35PM +0930 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, Aug 21, 1997 at 04:24:35PM +0930, Mike Smith wrote: >>> >>> You should spend some time reading back-issued of the hackers >>> digest. >> >> Right, I *should*. I'm running as fast as I can just to stay where I >> am. > > Under the circumstances, perhaps a slightly less vehement denunciation > of the concept might be indicated then? What denunciation? I just said that I wasn't ready for a wholesale conversion. > I'd always be happy to summarise the discussion to date if you > wanted to drop me a line. Sure, if I saw a need. I knew people were working on it. I said that I would be interested, implying "as long as I don't shoot myself in the foot with it". >>> Can you honestly imagine any such an idea gaining any sort of currency >>> without this basic criterion being met? >> >> No. Well, yes, but it would surprise me. > > You have little faith in the conservatism of others 8) I have great faith in the unexpected :-) Greg From owner-freebsd-hackers Thu Aug 21 04:41:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA15170 for hackers-outgoing; Thu, 21 Aug 1997 04:41:21 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA15164 for ; Thu, 21 Aug 1997 04:41:18 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id EAA23250; Thu, 21 Aug 1997 04:39:37 -0700 (PDT) To: Greg Lehey cc: Mike Smith , Terry Lambert , FreeBSD Hackers Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) In-reply-to: Your message of "Thu, 21 Aug 1997 16:09:21 +0930." <19970821160921.03779@lemis.com> Date: Thu, 21 Aug 1997 04:39:33 -0700 Message-ID: <23247.872163573@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > OK. That's just what I originally thought. But Jordan's message > suggested that I should cut over in one swell foop. Erm, no. I'm not suggesting that *you* cut over - we've already established that you're a poor testing candidate. I'm suggesting that others with access to more hardware do so. Now, can we stop talking about it and just get to it? ;-) Jordan From owner-freebsd-hackers Thu Aug 21 05:03:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15943 for hackers-outgoing; Thu, 21 Aug 1997 05:03:35 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA15936 for ; Thu, 21 Aug 1997 05:03:29 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id OAA28632; Thu, 21 Aug 1997 14:02:09 +0200 (MEST) From: Søren Schmidt Message-Id: <199708211202.OAA28632@sos.freebsd.dk> Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) In-Reply-To: <23247.872163573@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 21, 97 04:39:33 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 21 Aug 1997 14:02:09 +0200 (MEST) Cc: grog@lemis.com, mike@smith.net.au, terry@lambert.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Jordan K. Hubbard who wrote: > > OK. That's just what I originally thought. But Jordan's message > > suggested that I should cut over in one swell foop. > > Erm, no. I'm not suggesting that *you* cut over - we've already > established that you're a poor testing candidate. I'm suggesting that > others with access to more hardware do so. > > Now, can we stop talking about it and just get to it? ;-) We are at it... I've had to make a few adjustments to contrib/gcc to get it to compile proberly as an ELF compiler. The binutils is in place. I've relinked the entire a.out system as static (so I won't get conflicting ELF libs) And now the BINFORMAT=elf make world is humbling along (mind this is a 100Mhz 486 machine). The big question is if it works :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Aug 21 05:45:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18290 for hackers-outgoing; Thu, 21 Aug 1997 05:45:50 -0700 (PDT) Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18280 for ; Thu, 21 Aug 1997 05:45:42 -0700 (PDT) Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19]) by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id PAA27232 for ; Thu, 21 Aug 1997 15:37:36 +0300 From: Sakari Jalovaara Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA04003; Thu, 21 Aug 1997 15:37:36 +0300 Date: Thu, 21 Aug 1997 15:37:36 +0300 Message-Id: <9708211237.AA04003@poveri.tekla.fi> To: freebsd-hackers@FreeBSD.ORG Subject: Re: More info on slow "rm" times with 2.2.1+. Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Isn't there a command (which could be run in >> daily, or weekly, or something) that goes through a directory (or many) and >> optimize the space they take? >> >> If there isn't... why? And would it be hard to write? OLD=old-directory NEW=some-unique-name-$$ mkdir "$NEW" mv "$OLD"/* "$NEW" # You'd need a little something called "statf" here # `statf "chmod %m $NEW; chown %u $NEW; chgrp %g $NEW" "$OLD"` rmdir "$OLD" mv "$NEW" "$OLD" You'd have to make sure there are no other processes going through the directory at the time, though. I vaguely recall some UNIX variant having Amazing Automagically Shrinking Directories but I can't remember which one. ++sja From owner-freebsd-hackers Thu Aug 21 07:37:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA23554 for hackers-outgoing; Thu, 21 Aug 1997 07:37:39 -0700 (PDT) Received: from kcgw1.att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA23547 for ; Thu, 21 Aug 1997 07:37:35 -0700 (PDT) Received: from ulysses.att.com by kcig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id JAA25541; Thu, 21 Aug 1997 09:28:12 -0500 Received: from akiva.homer.att.com [135.205.213.77] by ulysses; Thu Aug 21 10:37:22 EDT 1997 Received: by akiva.homer.att.com (4.1) id AA04291; Thu, 21 Aug 97 10:37:23 EDT Message-Id: <9708211437.AA04291@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Thu Aug 21 10:37:22 EDT 1997 To: freebsd-hackers@freebsd.org Subject: 970807-SNAP AKA current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Aug 1997 10:37:20 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just finished loading 3.0-970807-SNAP and noticed a couple of minor SNAFU's: when I attempt to configure X using XF86Setup, it fails with: ld.so failed: Can't find shared library "libtcl.so.75.1" The other problem is with the packages. I noticed that there were some packages which are not included in the INDEX ( eg xlockmore ). Other thoughts on how to resolve these problems?? Thanks in advance Jim Ballantine From owner-freebsd-hackers Thu Aug 21 07:58:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24809 for hackers-outgoing; Thu, 21 Aug 1997 07:58:56 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA24804 for ; Thu, 21 Aug 1997 07:58:52 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 21 Aug 1997 10:58:21 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA13575; Thu, 21 Aug 97 10:58:20 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id KAA22414; Thu, 21 Aug 1997 10:55:27 -0400 Message-Id: <19970821105527.53931@ct.picker.com> Date: Thu, 21 Aug 1997 10:55:27 -0400 From: Randall Hopper To: hackers@freebsd.org Subject: ? "sysinstall" errors labeling a new disk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to do something I think should be very simple -- run sysinstall on an installed system to allocate a sizable free slice of disk to FreeBSD. This will be "wd1s2", with the intent of having: wd1s2b: 128Meg - SWAP wd1s2e: the rest - UFS @ /share3 FDISKING in sysinstall worked flawlessly: Custom-Partition-wd1-Create---Write-Yes Then, I got the new slice layed out in the disklabel editor: Label-Create-128M-SWAP-Create--FS-/share3 So far, looks good. --- BUT I try to "Write" and I get: >> "Unable to add /dev/wd1s2b as a swap device: Device not configured" << ktracing sysinstall, I see it's trying to: swapon( "/dev/wd1s2b" ) I'm wonderering why its trying to do that--I can do it later. Anway, going on it then immediately forks off: newfs -b 8192 -f 1024 /dev/rwd1s2e It appears it attempted no "disklabel" before this, so newfs fails. I guess sysinstall doesn't check the newfs command for failure since it then goes on and tries to mount the partition: mount( ..., "/share3", ..., "/dev/wd1s2e" ) which returns Invalid argument yielding the: >> "Error mounting /dev/wd1s2e on /share3 : Invalid argument" << dialog. If I try the "newfs -b 8192 -f 1024 /dev/rwd1s2e" by hand in the shell, I get: "newfs: /dev/rwd1s2e: `e' partition is unavailable" The /dev/rwd1s2e device file does exist, and "disklabel wd1s2" in the shell confirms the slice was never disklabeled (all blocks are in "c"). Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong or if this is a sysinstall bug? I'd welcome any tips, suggestions, and even enlightening flames. Before I resort to disklabeling via cmd-line, I'd like to make sure that sysinstall isn't an option -- it's definitely the easier and safer way to go if it can work for folks that don't Thanks, Randall From owner-freebsd-hackers Thu Aug 21 09:07:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00242 for hackers-outgoing; Thu, 21 Aug 1997 09:07:56 -0700 (PDT) Received: from bali.bytenet.com.br (bali.bytenet.com.br [200.254.17.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00233 for ; Thu, 21 Aug 1997 09:07:44 -0700 (PDT) Received: from ibiza.bytenet.com.br (ibiza.bytenet.com.br [200.254.17.10]) by bali.bytenet.com.br (8.8.5/8.8.5) with SMTP id KAA03741 for ; Thu, 21 Aug 1997 10:16:21 -0300 (EST) Received: from spanha.bytenet.com.br (200.254.17.27) by ibiza.bytenet.com.br (EMWAC SMTPRS 0.81) with SMTP id ; Thu, 21 Aug 1997 13:20:22 -0300 Received: by spanha.bytenet.com.br with Microsoft Mail id <01BCAE33.661134A0@spanha.bytenet.com.br>; Thu, 21 Aug 1997 13:09:03 -0300 Message-ID: <01BCAE33.661134A0@spanha.bytenet.com.br> From: Claudio Spanha To: "'hackers@freebsd.org'" Date: Thu, 21 Aug 1997 13:09:02 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe hackers spanha@bytenet.com.br From owner-freebsd-hackers Thu Aug 21 09:12:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00616 for hackers-outgoing; Thu, 21 Aug 1997 09:12:20 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA00607 for ; Thu, 21 Aug 1997 09:12:13 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA23481; Thu, 21 Aug 1997 09:03:25 -0700 From: Terry Lambert Message-Id: <199708211603.JAA23481@phaeton.artisoft.com> Subject: Re: ELF cutover (was :Re: [Fwd: Re: Please Help Me Understand dlopen()]) To: mike@smith.net.au (Mike Smith) Date: Thu, 21 Aug 1997 09:03:25 -0700 (MST) Cc: grog@lemis.com, terry@lambert.org, hackers@freeBSD.org In-Reply-To: <199708210151.LAA00453@word.smith.net.au> from "Mike Smith" at Aug 21, 97 11:20:35 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk > The entire idea with building mixed-flavour tools is to be able to avoid > a one-hit cutover; you should be able to work with a mixture of a.out > and ELF tools transparently. Except the kernel; the combined boot code is within tens of bytes of being too large, and is moderately kludged (not my opinion, the author's). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Aug 21 09:20:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01185 for hackers-outgoing; Thu, 21 Aug 1997 09:20:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA01175 for ; Thu, 21 Aug 1997 09:20:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA23531; Thu, 21 Aug 1997 09:12:46 -0700 From: Terry Lambert Message-Id: <199708211612.JAA23531@phaeton.artisoft.com> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] To: grog@lemis.com (Greg Lehey) Date: Thu, 21 Aug 1997 09:12:46 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: <19970821084227.64768@lemis.com> from "Greg Lehey" at Aug 21, 97 08:42:27 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > What do you mean by "convert to ELF"? I hope you don't mean a > > > wholesale change. > > > > Why not? > > Because I don't have the time at the moment. I'm too busy finding > out why libc.so.3.0 doesn't build in -current, and thus blows my > world out of the water. But it does it by making it build. 8-) 8-). > I might change my mind. What I really don't understand is why a > wholesale changeover should be necessary: I certainly hope that the > new system will still be able to run a.out executables. Yes, of course. The main sticking point is that the boot blocks booting an ELF kernel can only boot an ELF kernel, so dancing back and forth, back and forth is a bit out of the question. Yes, the current boot hacks fit (barely; < 80 bytes remaining), but don't cover all the cases the a,out-only boot blocks do. The LKM situation is equally grim; the LKM's must be switched at the same time. This is because the LKM relocation is done by linking against the kernel symbol table. Try linking an a.out image against the kernel symbol table. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Aug 21 10:11:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04547 for hackers-outgoing; Thu, 21 Aug 1997 10:11:50 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04537 for ; Thu, 21 Aug 1997 10:11:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA24300; Thu, 21 Aug 1997 10:11:36 -0700 (PDT) To: Randall Hopper cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-reply-to: Your message of "Thu, 21 Aug 1997 10:55:27 EDT." <19970821105527.53931@ct.picker.com> Date: Thu, 21 Aug 1997 10:11:35 -0700 Message-ID: <24296.872183495@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong > or if this is a sysinstall bug? It's a sysinstall bug - sysinstall is currently almost useless for doing this kind of thing and I'm currently split between trying to fix it or just forging ahead in trying to get setup(1) done in time. :) JOrdan From owner-freebsd-hackers Thu Aug 21 10:36:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06090 for hackers-outgoing; Thu, 21 Aug 1997 10:36:04 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06085 for ; Thu, 21 Aug 1997 10:36:02 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 21 Aug 1997 13:34:58 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA19545; Thu, 21 Aug 97 13:34:56 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id NAA23123; Thu, 21 Aug 1997 13:32:02 -0400 Message-Id: <19970821133201.41713@ct.picker.com> Date: Thu, 21 Aug 1997 13:32:01 -0400 From: Randall Hopper To: "Jordan K. Hubbard" Cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk References: <19970821105527.53931@ct.picker.com> <24296.872183495@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <24296.872183495@time.cdrom.com>; from Jordan K. Hubbard on Thu, Aug 21, 1997 at 10:11:35AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard: |> Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong |> or if this is a sysinstall bug? | |It's a sysinstall bug - sysinstall is currently almost useless for doing |this kind of thing and I'm currently split between trying to fix it |or just forging ahead in trying to get setup(1) done in time. :) Ok. Thanks for the reply. Good to know I didn't miss something. I'll put in my vote for sysinstall (or sysinstall-like) TUI/GUI tool that does this. Really, until I hit this little sysinstall bug, I thought this disk-repartition was going to be too easy to be true! That is, perform the same steps in the same tool as was used to install the original system (minus creating a root or installing distributions of course). Based on this little bit of experience, in whatever tool materializes it'd sure be nice if it were used both for original install and for subsequent system upgrade (new disk, new partition, etc.). BTW, what's setup(1)? Will this ultimately replace sysinstall for original installation as well? Randall From owner-freebsd-hackers Thu Aug 21 10:46:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06549 for hackers-outgoing; Thu, 21 Aug 1997 10:46:23 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06542 for ; Thu, 21 Aug 1997 10:46:19 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA24570; Thu, 21 Aug 1997 10:46:09 -0700 (PDT) To: Randall Hopper cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-reply-to: Your message of "Thu, 21 Aug 1997 13:32:01 EDT." <19970821133201.41713@ct.picker.com> Date: Thu, 21 Aug 1997 10:46:09 -0700 Message-ID: <24565.872185569@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'll put in my vote for sysinstall (or sysinstall-like) TUI/GUI tool that > does this. Really, until I hit this little sysinstall bug, I thought this Ultimately, someone just needs to hack on the disklabel and fdisk programs (and even if it involves a total rewrite of those tools) so that they're more "drivable" from scripts - Terry has an entire interaction model for tools to do this which I'm sure he'd be happy to share with anyone thinking of doing that work. :-) Even if one doesn't go for a full-blown Terry model, it'd still be possible to hack fdisk and disklabel significantly in ways which would make them much friendlier to "front-ending", perhaps enough so that some other perl hacker can come along and provide you a CGI script which enables one to partition and label a disk from one's HTML browser! :-) OK, so I was just kidding about the CGI thing (primarily because of the security issues involved - who wants their httpd running as root?) but it'd still make it possible to whip up some much more friendly disk management front-ends than the "interactive modes" provided by the current disklabel and fdisk programs. Jordan From owner-freebsd-hackers Thu Aug 21 11:31:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10591 for hackers-outgoing; Thu, 21 Aug 1997 11:31:59 -0700 (PDT) Received: from gaia.coppe.ufrj.br (jonny@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10575 for ; Thu, 21 Aug 1997 11:31:35 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.7/8.8.7) id PAA06860 for hackers@freebsd.org; Thu, 21 Aug 1997 15:30:41 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199708211830.PAA06860@gaia.coppe.ufrj.br> Subject: netstat kvm error To: hackers@freebsd.org Date: Thu, 21 Aug 1997 15:30:41 -0300 (EST) 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 X-Loop: FreeBSD.org Precedence: bulk Argh.. I'm tired of these netstat kvm error messages -> netstat: kvm_read: Bad address I get these when doing netstat on my main squid server. It starts looking for DNS addresses, and the race conditions on the PCB list kvm reading gets worse. What if the program first reads the kvm info, and only then do the DNS resolution to get the real names ? It's not a true solution, but at least minimizes the race window. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-hackers Thu Aug 21 11:34:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10945 for hackers-outgoing; Thu, 21 Aug 1997 11:34:58 -0700 (PDT) Received: from msn.globaldialog.com (sgtrock@msn.globaldialog.com [156.46.122.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10923 for ; Thu, 21 Aug 1997 11:34:43 -0700 (PDT) Received: (from sgtrock@localhost) by msn.globaldialog.com (8.8.5/8.6.12) id NAA11137; Thu, 21 Aug 1997 13:34:34 -0500 (CDT) Date: Thu, 21 Aug 1997 13:34:33 -0500 (CDT) From: sgtrock To: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-Reply-To: <91DD7FDA88E4D011BED00000C0DD87E708C28F@pdsmail.paragondev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > -----Original Message----- > From: Jordan K. Hubbard [SMTP:jkh@time.cdrom.com] > Even if one doesn't go for a full-blown Terry model, it'd still be > possible to hack fdisk and disklabel significantly in ways which would > make them much friendlier to "front-ending", perhaps enough so that > some other perl hacker can come along and provide you a CGI script > which enables one to partition and label a disk from one's HTML > browser! :-) I was under the impression that this was only an Internet Explorer feature... Kenny Hanson sgtrock@globaldialog.com I'm not responsible for anything I say or do... just deal with it! From owner-freebsd-hackers Thu Aug 21 12:19:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13469 for hackers-outgoing; Thu, 21 Aug 1997 12:19:13 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA13464 for ; Thu, 21 Aug 1997 12:19:07 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA00944 for ; Thu, 21 Aug 1997 12:19:06 -0700 (PDT) Date: Thu, 21 Aug 1997 12:19:05 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: How hard would it be for the boot blocks to validate Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk the integrity of the kernel binary itself? And then possibly boot an alternate kernel? From owner-freebsd-hackers Thu Aug 21 12:33:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14485 for hackers-outgoing; Thu, 21 Aug 1997 12:33:21 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA14475 for ; Thu, 21 Aug 1997 12:33:18 -0700 (PDT) Received: (qmail 29099 invoked by uid 1000); 21 Aug 1997 19:33:30 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: <19970820192412.DY34615@uriah.heep.sax.de> Date: Thu, 21 Aug 1997 12:33:30 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: (Joerg Wunsch) , freebsd-hackers@freebsd.org Subject: Re: "Content-Type: text/plain; charset=iso-8859-8" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Formal Apologies With great humility and many thanks I submit my apologies to all who got itrritated/agitated/annoyed by the fornt selection in my (not anymore) favorite E-Mil program. The sole cause of this screwup is Gennady's inability to release XFmail without having Hebrew as the default font (told you it was not my fault :-). The fact that I did not check what the default font is is totally irrelevant. I promise it will not happen again. Not before the next release... Cheers and (seriously) many thanks for a great O/S... Simon From owner-freebsd-hackers Thu Aug 21 12:39:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14972 for hackers-outgoing; Thu, 21 Aug 1997 12:39:20 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14962 for ; Thu, 21 Aug 1997 12:39:17 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA04502 for ; Thu, 21 Aug 1997 12:39:04 -0700 (PDT) Date: Thu, 21 Aug 1997 12:39:04 -0700 (PDT) From: Jaye Mathisen Reply-To: Jaye Mathisen To: hackers@freebsd.org Subject: 2.2.2 make release kernel build problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This has cropped up now: On a fairly recent 2.2.2 (Aug 1st I think). The -DMFS_ROOT= certainly looks defective. cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DMFS_ROOT= -DNFS_NOSERVER -DMFS -DAPM_BROKEN_STATCLOCK -DFAILSAFE -DCOMPAT_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../ufs/mfs/mfs_vfsops.c ../../ufs/mfs/mfs_vfsops.c:110: invalid type argument of `unary *' ../../ufs/mfs/mfs_vfsops.c:110: variable `mfs_root' has initializer but incomplete type *** Error code 1 Stop. *** Error code 1 Stop. From owner-freebsd-hackers Thu Aug 21 12:43:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15118 for hackers-outgoing; Thu, 21 Aug 1997 12:43:18 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15109 for ; Thu, 21 Aug 1997 12:43:15 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA05177 for ; Thu, 21 Aug 1997 12:43:14 -0700 (PDT) Date: Thu, 21 Aug 1997 12:43:13 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: More /usr/src/release notes on 2.2.2-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Various steps fail if you aren't running with sh as your shell. and: I don't see where fs.size is made so that MFS_ROOT has the right define: # make ===> crunch Warning: Object directory not changed from original /usr/src/release/floppies/boot/crunch ===> mfs Warning: Object directory not changed from original /usr/src/release/floppies/boot/mfs ===> floppy Warning: Object directory not changed from original /usr/src/release/floppies/boot/floppy cd /usr/src/release/floppies/boot/floppy && make doMFSKERN rm -f /usr/src/release/floppies/boot/floppy/../../../../sys/compile/BOOTMFS/mfs_vfsops.o cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && fgrep -v SYSV GENERIC | fgrep -v pty | fgrep -v PROCFS | sed 's/GENERIC/BOOTMFS/g' | sed '/maxusers/s/10/4/' > BOOTMFS && echo "options MFS" >> BOOTMFS && echo "options NFS_NOSERVER" >> BOOTMFS && echo 'options "MAXCONS=4"' >> BOOTMFS echo "options \"MFS_ROOT=`cat ../mfs/fs-image.size`\"" >> /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf/BOOTMFS cat: ../mfs/fs-image.size: No such file or directory cd /usr/src/release/floppies/boot/floppy && make doKERNEL KERNEL=BOOTMFS cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && config -n BOOTMFS config: line 15: syntax error ^C# make fs-image.size make: don't know how to make fs-image.size. Stop From owner-freebsd-hackers Thu Aug 21 13:12:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16986 for hackers-outgoing; Thu, 21 Aug 1997 13:12:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA16977 for ; Thu, 21 Aug 1997 13:12:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA24892; Thu, 21 Aug 1997 13:03:49 -0700 From: Terry Lambert Message-Id: <199708212003.NAA24892@phaeton.artisoft.com> Subject: Re: ? "sysinstall" errors labeling a new disk To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 21 Aug 1997 13:03:49 -0700 (MST) Cc: rhh@ct.picker.com, hackers@FreeBSD.ORG In-Reply-To: <24565.872185569@time.cdrom.com> from "Jordan K. Hubbard" at Aug 21, 97 10:46:09 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ultimately, someone just needs to hack on the disklabel and fdisk > programs (and even if it involves a total rewrite of those tools) so > that they're more "drivable" from scripts - Terry has an entire > interaction model for tools to do this which I'm sure he'd be happy to > share with anyone thinking of doing that work. :-) Yes: 1) Command line, for incorporation in scripts 2) Command parser, for interactive use 3) Pipeline parser, for driving by GUI/TUI I'll be happy to talk to anyone interested in it... > Even if one doesn't go for a full-blown Terry model, it'd still be > possible to hack fdisk and disklabel significantly in ways which would > make them much friendlier to "front-ending", perhaps enough so that > some other perl hacker can come along and provide you a CGI script > which enables one to partition and label a disk from one's HTML > browser! :-) I still think that it is a bad idea, seperating the fdisk and disklabel function; they are both subclasses of a mor general device management problem, and should be solvable in a single program. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Aug 21 13:32:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17718 for hackers-outgoing; Thu, 21 Aug 1997 13:32:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17712 for ; Thu, 21 Aug 1997 13:32:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id NAA25145; Thu, 21 Aug 1997 13:32:01 -0700 (PDT) To: sgtrock cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-reply-to: Your message of "Thu, 21 Aug 1997 13:34:33 CDT." Date: Thu, 21 Aug 1997 13:32:01 -0700 Message-ID: <25141.872195521@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was under the impression that this was only an Internet Explorer feature... Ha ha. Erm.. I don't see a smiley attached to this. :) Jordan From owner-freebsd-hackers Thu Aug 21 13:38:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA18057 for hackers-outgoing; Thu, 21 Aug 1997 13:38:07 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18051 for ; Thu, 21 Aug 1997 13:38:05 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id WAA15114; Thu, 21 Aug 1997 22:42:06 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708212042.WAA15114@ocean.campus.luth.se> Subject: Re: [Fwd: Re: Please Help Me Understand dlopen()] In-Reply-To: <199708211612.JAA23531@phaeton.artisoft.com> from Terry Lambert at "Aug 21, 97 09:12:46 am" To: terry@lambert.org (Terry Lambert) Date: Thu, 21 Aug 1997 22:42:05 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Terry Lambert: [... moving to ELF...] > The LKM situation is equally grim; the LKM's must be switched at > the same time. This is because the LKM relocation is done by > linking against the kernel symbol table. Try linking an a.out > image against the kernel symbol table. Say, isn't that a good thing? I thought the current LKM scheme was disliked, dysfunctional, and crippled in many ways. That's the impression I've gotten from reading these lists for a while, at least. So if we now have to redo them, that'd be a nice chance to get them right, and possibly compatible with something soneone else uses, if it's good. No? /Mikael From owner-freebsd-hackers Thu Aug 21 13:39:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA18106 for hackers-outgoing; Thu, 21 Aug 1997 13:39:29 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18100 for ; Thu, 21 Aug 1997 13:39:24 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id WAA15126; Thu, 21 Aug 1997 22:44:26 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708212044.WAA15126@ocean.campus.luth.se> Subject: Re: ? "sysinstall" errors labeling a new disk In-Reply-To: <24296.872183495@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 21, 97 10:11:35 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 21 Aug 1997 22:44:26 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > > Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong > > or if this is a sysinstall bug? > > It's a sysinstall bug - sysinstall is currently almost useless for doing > this kind of thing and I'm currently split between trying to fix it > or just forging ahead in trying to get setup(1) done in time. :) Say... Is there any previews of the unser interface out there? A beta version? Alpha? something? :) it's be nice to be able to comment and not first have you (basically) alone write something you think works, and after you've done lots and lots of work on it, most people feel it works the wrong way, and should be remodelled completely. You know? :-) And I'm curious, too. :-) /Mikael From owner-freebsd-hackers Thu Aug 21 13:41:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA18245 for hackers-outgoing; Thu, 21 Aug 1997 13:41:26 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18236 for ; Thu, 21 Aug 1997 13:41:23 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id NAA25186; Thu, 21 Aug 1997 13:41:09 -0700 (PDT) To: Mikael Karpberg cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-reply-to: Your message of "Thu, 21 Aug 1997 22:44:26 +0200." <199708212044.WAA15126@ocean.campus.luth.se> Date: Thu, 21 Aug 1997 13:41:09 -0700 Message-ID: <25182.872196069@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Say... Is there any previews of the unser interface out there? A beta > version? Alpha? something? :) it's be nice to be able to comment and > not first have you (basically) alone write something you think works, > and after you've done lots and lots of work on it, most people feel > it works the wrong way, and should be remodelled completely. > You know? :-) And I'm curious, too. :-) I'm afraid not - the way things are going right now with this, I actually expect the UI to be one of the *last* things added. :-) Also, there are at least 3 people working on it this time, counting myself. Not a solo effort this time around! ;) Jordan From owner-freebsd-hackers Thu Aug 21 13:55:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA18967 for hackers-outgoing; Thu, 21 Aug 1997 13:55:21 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA18960 for ; Thu, 21 Aug 1997 13:55:18 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA09311; Thu, 21 Aug 1997 13:38:23 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd009307; Thu Aug 21 20:38:15 1997 Message-ID: <33FCA733.1CFBAE39@whistle.com> Date: Thu, 21 Aug 1997 13:38:11 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jaye Mathisen CC: hackers@FreeBSD.ORG Subject: Re: More /usr/src/release notes on 2.2.2-stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > > Various steps fail if you aren't running with sh as your shell. > > and: > > I don't see where fs.size is made so that MFS_ROOT has the right define: > > # make > ===> crunch > Warning: Object directory not changed from original > /usr/src/release/floppies/boot/crunch > ===> mfs > Warning: Object directory not changed from original > /usr/src/release/floppies/boot/mfs > ===> floppy > Warning: Object directory not changed from original > /usr/src/release/floppies/boot/floppy > cd /usr/src/release/floppies/boot/floppy && make doMFSKERN > rm -f > /usr/src/release/floppies/boot/floppy/../../../../sys/compile/BOOTMFS/mfs_vfsops.o > cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && > fgrep -v SYSV GENERIC | fgrep -v pty | fgrep -v PROCFS | sed > 's/GENERIC/BOOTMFS/g' | sed '/maxusers/s/10/4/' > BOOTMFS && echo > "options MFS" >> BOOTMFS && echo "options NFS_NOSERVER" >> BOOTMFS && > echo 'options "MAXCONS=4"' >> BOOTMFS > echo "options \"MFS_ROOT=`cat ../mfs/fs-image.size`\"" >> > /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf/BOOTMFS > cat: ../mfs/fs-image.size: No such file or directory > cd /usr/src/release/floppies/boot/floppy && make doKERNEL KERNEL=BOOTMFS > cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && > config -n BOOTMFS can you look at the config file it produced, (/sys/i386/conf/BOOTMFS) and see what's wrong with line 15? > config: line 15: syntax error > ^C# make fs-image.size > make: don't know how to make fs-image.size. Stop From owner-freebsd-hackers Thu Aug 21 14:42:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20976 for hackers-outgoing; Thu, 21 Aug 1997 14:42:00 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA20968 for ; Thu, 21 Aug 1997 14:41:56 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id OAA26276 for ; Thu, 21 Aug 1997 14:41:42 -0700 (PDT) Date: Thu, 21 Aug 1997 14:41:41 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: It appears to be impossible to build a kernel w/o networking... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If so, then the things should be marked mandatory, ala npx0. From owner-freebsd-hackers Thu Aug 21 15:05:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22192 for hackers-outgoing; Thu, 21 Aug 1997 15:05:00 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22177 for ; Thu, 21 Aug 1997 15:04:53 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA06374; Thu, 21 Aug 1997 16:04:48 -0600 (MDT) Date: Thu, 21 Aug 1997 16:04:48 -0600 (MDT) Message-Id: <199708212204.QAA06374@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: It appears to be impossible to build a kernel w/o networking... In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > If so, then the things should be marked mandatory, ala npx0. Where's the patch? I don't see the patch? I *know* you know how to program and create patches. C'mon, gimme the patch Jaye. *grin* Nate From owner-freebsd-hackers Thu Aug 21 15:09:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22349 for hackers-outgoing; Thu, 21 Aug 1997 15:09:00 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22344 for ; Thu, 21 Aug 1997 15:08:55 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id PAA01098 for ; Thu, 21 Aug 1997 15:08:50 -0700 (PDT) Date: Thu, 21 Aug 1997 15:08:50 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Final request for help with release. (DPT boot floppy) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk And then I'll just go back to solaris which works :) I have managed to fix the various syntax errors and such, and build a boot floppy. It boots, and runs, and gets to sysinstall, however, I am unable to either run fixit or install, because it's unable to create any directories, ... no space left on device. I've massaged doFS.sh, and dropped FSINODES from 10000 to 8000 to get more inodes, but nothing seems to help. I'm running out of ideas. Any help appreciated. From owner-freebsd-hackers Thu Aug 21 15:21:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23191 for hackers-outgoing; Thu, 21 Aug 1997 15:21:32 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@libya-197.ppp.hooked.net [206.169.227.197]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23184 for ; Thu, 21 Aug 1997 15:21:26 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id PAA01462; Thu, 21 Aug 1997 15:22:04 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 21 Aug 1997 15:22:04 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Randall Hopper cc: hackers@FreeBSD.ORG Subject: Re: ? "sysinstall" errors labeling a new disk In-Reply-To: <19970821105527.53931@ct.picker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Randall Hopper wrote: > Shouldn't sysinstall be doing a disklabel? Any idea what I'm doing wrong > or if this is a sysinstall bug? > > I'd welcome any tips, suggestions, and even enlightening flames. Before I > resort to disklabeling via cmd-line, I'd like to make sure that sysinstall > isn't an option -- it's definitely the easier and safer way to go if it can > work for folks that don't Yup, that's a bug alright. There was a similar bug that would make sysinstall error out if you tried to label a disk slice, which was fixed a few days ago in the -current sources. Your best bet though is probably to download a 2.2 boot disk and load sysinstall from there, or try cvsup'n the sources and making /usr/src/release/sysinstall. - alex From owner-freebsd-hackers Thu Aug 21 15:44:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA24541 for hackers-outgoing; Thu, 21 Aug 1997 15:44:05 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA24482 for ; Thu, 21 Aug 1997 15:44:00 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id PAA07547; Thu, 21 Aug 1997 15:43:53 -0700 (PDT) Date: Thu, 21 Aug 1997 15:43:53 -0700 (PDT) From: Jaye Mathisen To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: More /usr/src/release notes on 2.2.2-stable In-Reply-To: <33FCA733.1CFBAE39@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon's patch for the DPT controller stuck a line that said ===, w/o the leading #. Fixing that didn't rectify the problem however. I'm installing on a clean chroot partition to make sure it's not just me. On Thu, 21 Aug 1997, Julian Elischer wrote: > Jaye Mathisen wrote: > > > > Various steps fail if you aren't running with sh as your shell. > > > > and: > > > > I don't see where fs.size is made so that MFS_ROOT has the right define: > > > > # make > > ===> crunch > > Warning: Object directory not changed from original > > /usr/src/release/floppies/boot/crunch > > ===> mfs > > Warning: Object directory not changed from original > > /usr/src/release/floppies/boot/mfs > > ===> floppy > > Warning: Object directory not changed from original > > /usr/src/release/floppies/boot/floppy > > cd /usr/src/release/floppies/boot/floppy && make doMFSKERN > > rm -f > > /usr/src/release/floppies/boot/floppy/../../../../sys/compile/BOOTMFS/mfs_vfsops.o > > cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && > > fgrep -v SYSV GENERIC | fgrep -v pty | fgrep -v PROCFS | sed > > 's/GENERIC/BOOTMFS/g' | sed '/maxusers/s/10/4/' > BOOTMFS && echo > > "options MFS" >> BOOTMFS && echo "options NFS_NOSERVER" >> BOOTMFS && > > echo 'options "MAXCONS=4"' >> BOOTMFS > > echo "options \"MFS_ROOT=`cat ../mfs/fs-image.size`\"" >> > > /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf/BOOTMFS > > cat: ../mfs/fs-image.size: No such file or directory > > cd /usr/src/release/floppies/boot/floppy && make doKERNEL KERNEL=BOOTMFS > > cd /usr/src/release/floppies/boot/floppy/../../../../sys/i386/conf && > > config -n BOOTMFS > > can you look at the config file it produced, > (/sys/i386/conf/BOOTMFS) and see what's > wrong with line 15? > > > config: line 15: syntax error > > ^C# make fs-image.size > > make: don't know how to make fs-image.size. Stop > From owner-freebsd-hackers Thu Aug 21 16:01:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25615 for hackers-outgoing; Thu, 21 Aug 1997 16:01:43 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25597 for ; Thu, 21 Aug 1997 16:01:36 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id QAA25623; Thu, 21 Aug 1997 16:01:16 -0700 (PDT) To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-reply-to: Your message of "Thu, 21 Aug 1997 15:08:50 PDT." Date: Thu, 21 Aug 1997 16:01:16 -0700 Message-ID: <25619.872204476@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm running out of ideas. Get the DPT driver into -current? Jordan From owner-freebsd-hackers Thu Aug 21 16:12:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA26231 for hackers-outgoing; Thu, 21 Aug 1997 16:12:47 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26225 for ; Thu, 21 Aug 1997 16:12:44 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA14103; Thu, 21 Aug 1997 16:07:34 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd014101; Thu Aug 21 23:07:33 1997 Message-ID: <33FCCA31.FF6D5DF@whistle.com> Date: Thu, 21 Aug 1997 16:07:29 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jaye Mathisen CC: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > > And then I'll just go back to solaris which works :) > > I have managed to fix the various syntax errors and such, and build a boot > floppy. It boots, and runs, and gets to sysinstall, however, I am unable > to either run fixit or install, because it's unable to create any > directories, ... no space left on device. > > I've massaged doFS.sh, and dropped FSINODES from 10000 to 8000 to get more > inodes, but nothing seems to help. > > I'm running out of ideas. is it the MFS or the disk that is out of vnodes.. it must be the MFS.. did you frob the right FS? :) > > Any help appreciated. From owner-freebsd-hackers Thu Aug 21 16:22:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA27968 for hackers-outgoing; Thu, 21 Aug 1997 16:22:58 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA27920 for ; Thu, 21 Aug 1997 16:22:46 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA06634; Thu, 21 Aug 1997 17:22:35 -0600 (MDT) Date: Thu, 21 Aug 1997 17:22:35 -0600 (MDT) Message-Id: <199708212322.RAA06634@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: References: X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > And then I'll just go back to solaris which works :) And is slower than a dog. I guess you'd need that RAID system to get decent I/O performance out of it. :) :) > floppy. It boots, and runs, and gets to sysinstall, however, I am unable > to either run fixit or install, because it's unable to create any > directories, ... no space left on device. > > I've massaged doFS.sh, and dropped FSINODES from 10000 to 8000 to get more > inodes, but nothing seems to help. Try massaging the kernel config file that is created to be specific to your box (ie; removing un-unused features, etc...) Nate From owner-freebsd-hackers Thu Aug 21 17:27:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA03178 for hackers-outgoing; Thu, 21 Aug 1997 17:27:45 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA03173 for ; Thu, 21 Aug 1997 17:27:42 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1hXp-0002vr-00; Thu, 21 Aug 1997 17:25:41 -0700 Date: Thu, 21 Aug 1997 17:25:41 -0700 (PDT) From: Tom Samplonius To: "Jordan K. Hubbard" cc: Jaye Mathisen , hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <25619.872204476@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > I'm running out of ideas. > > Get the DPT driver into -current? > > Jordan Sure, take the patches from sendero-ppp.i-connect.net/crash and commit them. But according to recent discusions, core has rejected the DPT driver as it stands... Tom From owner-freebsd-hackers Thu Aug 21 17:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA03383 for hackers-outgoing; Thu, 21 Aug 1997 17:30:20 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA03377 for ; Thu, 21 Aug 1997 17:30:16 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1haJ-0002vw-00; Thu, 21 Aug 1997 17:28:15 -0700 Date: Thu, 21 Aug 1997 17:28:15 -0700 (PDT) From: Tom Samplonius To: Nate Williams cc: Jaye Mathisen , hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <199708212322.RAA06634@rocky.mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Nate Williams wrote: > > And then I'll just go back to solaris which works :) > > And is slower than a dog. I guess you'd need that RAID system to get > decent I/O performance out of it. :) :) According to a simple test with dd that I ran on the identical hardware with 2.2-stable and Solaris 2.5.1 x86, the performance results are basically the same. Tom From owner-freebsd-hackers Thu Aug 21 17:40:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04070 for hackers-outgoing; Thu, 21 Aug 1997 17:40:31 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04061 for ; Thu, 21 Aug 1997 17:40:28 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA29051; Thu, 21 Aug 1997 17:40:16 -0700 (PDT) Date: Thu, 21 Aug 1997 17:40:16 -0700 (PDT) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <25619.872204476@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The problem is that I can't even boot the original box anymore because the driver that's installed has a problem that's fixed in DPT-1.2.1, and for some strange reason, the original boot floppy won't work. So I can build a working 1.2.1 kernel, and I can get it on the disk, but fixit won't work so I can copy the kernel off the floppy to the drive. Or ftp it, or any other way that I can think of. On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > I'm running out of ideas. > > Get the DPT driver into -current? > > Jordan > From owner-freebsd-hackers Thu Aug 21 17:43:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04182 for hackers-outgoing; Thu, 21 Aug 1997 17:43:59 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04174 for ; Thu, 21 Aug 1997 17:43:57 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id RAA08236; Thu, 21 Aug 1997 17:43:47 -0700 (PDT) To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-reply-to: Your message of "Thu, 21 Aug 1997 17:40:16 PDT." Date: Thu, 21 Aug 1997 17:43:47 -0700 Message-ID: <8233.872210627@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So I can build a working 1.2.1 kernel, and I can get it on the disk, but > fixit won't work so I can copy the kernel off the floppy to the drive. > Or ftp it, or any other way that I can think of. And I assume that you've already contemplated physically moving the drive to another machine for the xfer? Jordan From owner-freebsd-hackers Thu Aug 21 17:44:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04273 for hackers-outgoing; Thu, 21 Aug 1997 17:44:35 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04267 for ; Thu, 21 Aug 1997 17:44:30 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA29850; Thu, 21 Aug 1997 17:44:16 -0700 (PDT) Date: Thu, 21 Aug 1997 17:44:16 -0700 (PDT) From: Jaye Mathisen To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <33FCCA31.FF6D5DF@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Julian Elischer wrote: > Jaye Mathisen wrote: > > > > I've massaged doFS.sh, and dropped FSINODES from 10000 to 8000 to get more > > inodes, but nothing seems to help. > is it the MFS or the disk that is out of vnodes.. > it must be the MFS.. > did you frob the right FS? Near as I can tell. I'm building with the DPT driver, and the system finds it and sd0 and all that stuff. But I can't make a directory on it to save my life. I tried simplifying the script that creates the MFS to not create some unneeded devices so that there'd be more inodes available, but no luck. it's almost like the script that generates the vn'able image resizes the number of inodes to exactly what's needed. But that can't be right, because certainly a stock 2.2.2 boot.flp works fine. I tried making a tweaked kernel that only had my devices in it, and the boot floppy just got smaller, but had the same problem with inodes. From owner-freebsd-hackers Thu Aug 21 17:46:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA04339 for hackers-outgoing; Thu, 21 Aug 1997 17:46:04 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA04331 for ; Thu, 21 Aug 1997 17:46:01 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id RAA00230; Thu, 21 Aug 1997 17:45:51 -0700 (PDT) Date: Thu, 21 Aug 1997 17:45:51 -0700 (PDT) From: Jaye Mathisen To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <8233.872210627@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It's gotta be laid out on a DPT controller to get the right bizarro geometry, (plus it's raid 5), so an individual disk move wouldn't solve the problem. The problem is somehow specifically related to the number of inodes in the MFS image, but I can't figure out how to make that larger. Making a new kernel only made the floppy image smaller. Chainge FSINODES in doFS.sh didn't seem to help either. On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > So I can build a working 1.2.1 kernel, and I can get it on the disk, but > > fixit won't work so I can copy the kernel off the floppy to the drive. > > Or ftp it, or any other way that I can think of. > > And I assume that you've already contemplated physically moving the > drive to another machine for the xfer? > > Jordan > From owner-freebsd-hackers Thu Aug 21 21:16:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA13258 for hackers-outgoing; Thu, 21 Aug 1997 21:16:05 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13228 for ; Thu, 21 Aug 1997 21:15:59 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA07265; Thu, 21 Aug 1997 22:15:46 -0600 (MDT) Date: Thu, 21 Aug 1997 22:15:46 -0600 (MDT) Message-Id: <199708220415.WAA07265@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Tom Samplonius Cc: Nate Williams , Jaye Mathisen , hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: References: <199708212322.RAA06634@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > And then I'll just go back to solaris which works :) > > > > And is slower than a dog. I guess you'd need that RAID system to get > > decent I/O performance out of it. :) :) > > According to a simple test with dd that I ran on the identical hardware > with 2.2-stable and Solaris 2.5.1 x86, the performance results are > basically the same. What kind of performance tests? Dhrystone and Whetstone's will be exactly the same since it's the same hardware, but I'd be suprised if networking, I/O, and load performance were even close to the same. Nate From owner-freebsd-hackers Thu Aug 21 22:49:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17275 for hackers-outgoing; Thu, 21 Aug 1997 22:49:11 -0700 (PDT) Received: from tatnet.com (tatnet.com [207.239.107.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17270 for ; Thu, 21 Aug 1997 22:49:09 -0700 (PDT) From: pai@somemore4u.com Received: from WINUSER (pm12-13.digital.net [204.215.232.46]) by tatnet.com (8.8.5/8.6.12) with SMTP id BAA01846; Fri, 22 Aug 1997 01:41:58 -0400 (EDT) Date: Fri, 22 Aug 1997 01:41:58 -0400 (EDT) To: pai@somemore4u.com Comments: Authenticated sender is Reply-to: getit@somemore4u.com Subject: Get more visitors! Message-Id: <199708222027DAA6398@post.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Dear Friend and Fellow Entrepreneur, Thanks for signing up with Direct Delivery! You only get one chance to act. DISCOVER The Most Powerful & PROVEN Strategies that Really Work To Place You At The Top of the Search Engines! If you have a web page, or site, that can't be found at the top of the search engines, then this will be the most important information you will ever read. You are about to Discover the most Powerful Strategies used only by the very best on the Web... strategies so Powerful that once used will place your Web Page or site at the TOP 10 - 20 search engine listings! These TOP SECRET strategies will provide you with a cutting edge advantage over your competition and give you the long awaited results you have been looking for. Just imagine opening a Floodgate of People into your Home Page because you have the right information. It doesn't matter if you have one page or 1000 pages--you can achieve a top rating with this powerful information and soon squash your competition! This 25 page in-depth report covers: >Search Engine Tactics your competition doesn't want you to know! >The best kept secrets to getting you a top 10 - 20 listing! The 10 top keywords searched for!7 Getting better positioning than your opposition even when they have the same identical keywords! >Proven techniques for selecting the most effective keywords and how to arrange them! >A powerful way to get your listing seen by potential customers, even if they're not looking for you! >A little-known way to get multiple listings for your site in the same search engine! >Proven strategies used to resubmit your page or site and get that top rating even if you have it listed already! >How to get people to go to your site first even if they see your competition! >The most powerful words used to create the best Web Pages! >A Web tool used to market successfully in the Newsgroups! >Five things you should NEVER do! If you aren't at the top of the search engines now... your competition is! It's estimated that over 1000 new Web Pages are coming online every day! Newspapers are reporting over 14,000 new www addresses are being submitted every week. The competition grows every minute! It just makes sense that those who know and apply this information will definitely have the best chance of realizing their dreams of success. This in-depth report is normally US$49.95... However, if you order within the next 10 days... we'll include ABSOLUTELY FREE... OVER 1000 Links where you can advertise your web site FREE and you can have it all for JUST US$19.95! This INVALUABLE information alone is worth the asking price! Don't delay... this Extraordinary and Valuable Information can be yours today for ONLY $19.95 (USA FUNDS). Why Wait... Order Right Now! As an added BONUS, if you respond within 10 days: You'll also receive free tools, images, and tips to help you with Your Web Page construction, including free CGI scripts, buttons, backgrounds, and loads of Jpegs and Gifs, including animated Gifs! Please print, cut, and fill out the following order coupon: ---------------------------------------------------------------------------- ATTN: Please type or print legibly to ensure timely delivery. Name __________________________________________________________ *E-mail Address (Required) __________________________________________________________ Address __________________________________________________________ City ______________________ State ________ Zip ___________ Country______________________ Phone #______________________ $19.95 SEARCH ENGINE SECRETS (US Dollars) $_____ Sales Tax (MA residents 5.00%) $_____ Order Total PAYMENT BY: ___ Personal/Business Check ___ Money Order ___ Cashiers Check-US FUNDS only! PREFERRED FORMAT (Please check one or more of the following): ___ ASCII ___ Word 2.x for Windows ___Word 6.x ___ Word 7.x ___ Zipped >>If you're ordering from outside the USA, only a Money Order in US Dollars will be accepted. No postal delivery is available outside the USA, so you must include your E-mail address accurately and legibly. If you do not currently have an E-mail address, please get permission to use a friend's. << Discount expires 9-1-97. -------------------------------------------------------------------------------------- For fastest service use Cashiers Check or Money Order. Please include your e-mail address for 24 hour order processing. Please allow 2 weeks for processing by regular postal mail. Please make payable to -> EVA, Inc. and send to: EVA, Inc. 43 Riverside Ave. Suite 72 Medford, MA 02155 USA Reminder: Your order must be postmarked by Monday, September 1st in order to receive the bonuses. m in o From owner-freebsd-hackers Thu Aug 21 23:02:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA17953 for hackers-outgoing; Thu, 21 Aug 1997 23:02:38 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA17933 for ; Thu, 21 Aug 1997 23:02:28 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id CAA09267; Fri, 22 Aug 1997 02:02:25 -0400 (EDT) Date: Fri, 22 Aug 1997 02:02:25 -0400 (EDT) Message-Id: <199708220602.CAA09267@smoke.marlboro.vt.us> From: john hood MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Jaye Mathisen , hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: References: <33FCCA31.FF6D5DF@whistle.com> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen writes: > I tried making a tweaked kernel that only had my devices in it, and the > boot floppy just got smaller, but had the same problem with inodes. I didn't want to deal with the whole floppy-generation process, either. I'll suggest a crude hack in order to get around the problem. I used it to gen up floppies with my own kernel and enough toys to check my IDE code on random PCs that I come across. I haven't tried an install with it, but it ought to work. Oh, there's one possible exceptional case. Are you doing a floppy install? (That anguished wail I heard from you-- I take it you mean 'no'... :) 1) Boot a distribution boot floppy on a FreeBSD box; copy the MFS filesystem off to a temp dir on its hard disk. 2) Copy this stuff, modulo whatever changes you might need (DPT device nodes for you, maybe) to a filesystem floppy. 3) Generate a normal kernel with the DPT driver (except that it has 'swap generic' in the config file), put it on another floppy. 4) boot -a, swap floppies, watch sysinstall run with breathtaking lack of speed from floppy :) --jh -- John Hood cgull@smoke.marlboro.vt.us Predictably, they all eventually wandered away, rubbing their bruises and brushing mud out of their hair. Some went off to work for the ESA, launching much smaller rockets into low orbits, while others elected to sit on their front porches drinking Jim Beam from the bottle and launching bottle rockets from the empties. [Jordan Hubbard] From owner-freebsd-hackers Thu Aug 21 23:11:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18343 for hackers-outgoing; Thu, 21 Aug 1997 23:11:44 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18317 for ; Thu, 21 Aug 1997 23:11:40 -0700 (PDT) Received: (qmail 24928 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: <25619.872204476@time.cdrom.com> Date: Thu, 21 Aug 1997 23:11:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, Jaye Mathisen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 21-Aug-97 you wrote: > > I'm running out of ideas. > > Get the DPT driver into -current? It is available for Current. I am typing from one :-) 15 disks, 2 controllers, 6 SCSI channels. Only need to have SMP work and I can retire. Simon From owner-freebsd-hackers Thu Aug 21 23:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18351 for hackers-outgoing; Thu, 21 Aug 1997 23:11:45 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18318 for ; Thu, 21 Aug 1997 23:11:40 -0700 (PDT) Received: (qmail 24930 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: Date: Thu, 21 Aug 1997 23:11:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 22-Aug-97 you wrote: > > It's gotta be laid out on a DPT controller to get the right bizarro > geometry, (plus it's raid 5), so an individual disk move wouldn't solve > the problem. > > The problem is somehow specifically related to the number of inodes in > the > MFS image, but I can't figure out how to make that larger. Making a new > kernel only made the floppy image smaller. > > Chainge FSINODES in doFS.sh didn't seem to help either. > > On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > > > So I can build a working 1.2.1 kernel, and I can get it on the disk, > > > but > > > fixit won't work so I can copy the kernel off the floppy to the > > > drive. > > > Or ftp it, or any other way that I can think of. > > > > And I assume that you've already contemplated physically moving the > > drive to another machine for the xfer? > > > > Jordan > > Listen guys and gals; The boot images in sendero-ppp are what was used to install snedero-ppp and copper and brass. This is at home, in my office. In our lab there are at least twenty more machines which installed and booted from the same floppy image. Configurations? Sendero: SuperMicro P6DNH with two processors and 256MB RAM, 2 DPT PM3334UW with 8 disks on one and 7 on the other, plus Sony DAT plus Plextor CD. The only thing that does not work is interrupts for the Intel 100MBI PCI 100Base-TX cards and sound. This relates to the MB, not the DPT. This is a -current machine. Copper: Intel PR440FX with twin processors and 64MB of RAM. One DPT PM3334UW with 6 disks on one BUS and 7 on the other. This is a RELENG_2_2 machine. Brass: P6DNH with one DPT and 128MB of RAM, etc. Only 2 disks on bus 0 and 8 on busses 1, 2. In the lab we have several Crystal Industrial computers with Pentium CPU cards, Some Texas Micro with PEntium and some with PP processors. They all work. As soon as I get Justin's last comments integrated and not panic, I will release another patch. First for 2.2, then for -current. We ship our product on 2.2, so that must be done first. Simon From owner-freebsd-hackers Thu Aug 21 23:11:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18360 for hackers-outgoing; Thu, 21 Aug 1997 23:11:46 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18316 for ; Thu, 21 Aug 1997 23:11:40 -0700 (PDT) Received: (qmail 24920 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: Date: Thu, 21 Aug 1997 23:11:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, Jaye Mathisen , Nate Williams Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 22-Aug-97 you wrote: > > On Thu, 21 Aug 1997, Nate Williams wrote: > > > > And then I'll just go back to solaris which works :) > > > > And is slower than a dog. I guess you'd need that RAID system to get > > decent I/O performance out of it. :) :) > > According to a simple test with dd that I ran on the identical > hardware > with 2.2-stable and Solaris 2.5.1 x86, the performance results are > basically the same. > > Tom I take this as a compliment. Thank you. How high is the load in your test. We reject here anything under 256 concurrent processes and release after 1024 concurrent processes ran continually for 48 hours. Then it goes to System Test which does who know what... Simon Almost forgot; Still have to see a Solaris box survive this test. Let alone perform as well as FreeBSD in these casual tests. Simon From owner-freebsd-hackers Thu Aug 21 23:11:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18367 for hackers-outgoing; Thu, 21 Aug 1997 23:11:47 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18322 for ; Thu, 21 Aug 1997 23:11:41 -0700 (PDT) Received: (qmail 24936 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: Date: Thu, 21 Aug 1997 23:11:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, Jaye Mathisen , "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 22-Aug-97 you wrote: > > On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > > > I'm running out of ideas. > > > > Get the DPT driver into -current? > > > > Jordan > > Sure, take the patches from sendero-ppp.i-connect.net/crash and commit > them. > > But according to recent discusions, core has rejected the DPT driver > as > it stands... Good to know. Thanx! Nobody told me that. Now I know what to do. Simon From owner-freebsd-hackers Thu Aug 21 23:11:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18369 for hackers-outgoing; Thu, 21 Aug 1997 23:11:47 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18321 for ; Thu, 21 Aug 1997 23:11:40 -0700 (PDT) Received: (qmail 24917 invoked by uid 1000); 22 Aug 1997 06:11:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: Date: Thu, 21 Aug 1997 23:11:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 21-Aug-97 you wrote: > > > And then I'll just go back to solaris which works :) > > I have managed to fix the various syntax errors and such, and build a > boot > floppy. It boots, and runs, and gets to sysinstall, however, I am > unable > to either run fixit or install, because it's unable to create any > directories, ... no space left on device. > > I've massaged doFS.sh, and dropped FSINODES from 10000 to 8000 to get > more > inodes, but nothing seems to help. > > I'm running out of ideas. > > Any help appreciated. The only way I know to create a boot floppy (and they work, trust me :-) is really ugly: * Start make release * Tail -f the output. * Once you see that the entire sys directory checked out from CVS, do: cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys * Sit back and enjoy the ride. Simon From owner-freebsd-hackers Thu Aug 21 23:20:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18928 for hackers-outgoing; Thu, 21 Aug 1997 23:20:27 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18917 for ; Thu, 21 Aug 1997 23:20:20 -0700 (PDT) Received: (qmail 24942 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: Date: Thu, 21 Aug 1997 23:11:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 22-Aug-97 you wrote: > > The problem is that I can't even boot the original box anymore because > the > driver that's installed has a problem that's fixed in DPT-1.2.1, and for > some strange reason, the original boot floppy won't work. How about mounting the floppy, cp the file to it and umount? > > So I can build a working 1.2.1 kernel, and I can get it on the disk, but > fixit won't work so I can copy the kernel off the floppy to the drive. > Or ftp it, or any other way that I can think of. > > On Thu, 21 Aug 1997, Jordan K. Hubbard wrote: > > > > I'm running out of ideas. > > > > Get the DPT driver into -current? > > > > Jordan > > > From owner-freebsd-hackers Thu Aug 21 23:20:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA18929 for hackers-outgoing; Thu, 21 Aug 1997 23:20:27 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA18918 for ; Thu, 21 Aug 1997 23:20:20 -0700 (PDT) Received: (qmail 24940 invoked by uid 1000); 22 Aug 1997 06:11:49 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: <8233.872210627@time.cdrom.com> Date: Thu, 21 Aug 1997 23:11:49 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, Jaye Mathisen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 22-Aug-97 you wrote: > > So I can build a working 1.2.1 kernel, and I can get it on the disk, > > but > > fixit won't work so I can copy the kernel off the floppy to the drive. > > Or ftp it, or any other way that I can think of. > > And I assume that you've already contemplated physically moving the > drive to another machine for the xfer? Not a good idea, unless the othe machine is a DPT based one. There are some differences between DPT initialized disks and others. Something to do with the RAID information. I already bitched DPT about it in 1985-1986 and got nowhere. You are welcome to try again :-) Simon From owner-freebsd-hackers Thu Aug 21 23:51:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA20803 for hackers-outgoing; Thu, 21 Aug 1997 23:51:53 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA20786 for ; Thu, 21 Aug 1997 23:51:44 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA28091 for hackers@FreeBSD.ORG; Fri, 22 Aug 1997 08:51:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA04886; Fri, 22 Aug 1997 08:26:20 +0200 (MET DST) Message-ID: <19970822082620.XM01678@uriah.heep.sax.de> Date: Fri, 22 Aug 1997 08:26:20 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: How hard would it be for the boot blocks to validate References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jaye Mathisen on Aug 21, 1997 12:19:05 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > the integrity of the kernel binary itself? Right now? Impossible. If we've got 8 spare bytes in the bootblocks, it's probably already plenty. Also, how are you going to check any integrity of /kernel? Would you put the entire MD5 into the bootblocks? Well, when going to a 3-stage bootstrap, space is no longer a big problem, but the number of vulnerable files will be extended (from just /kernel to /boot + /kernel), so no help for your problem at all. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Aug 21 23:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA20880 for hackers-outgoing; Thu, 21 Aug 1997 23:52:11 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA20852 for ; Thu, 21 Aug 1997 23:52:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA28094; Fri, 22 Aug 1997 08:52:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA04926; Fri, 22 Aug 1997 08:37:54 +0200 (MET DST) Message-ID: <19970822083754.DK56116@uriah.heep.sax.de> Date: Fri, 22 Aug 1997 08:37:54 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: mrcpu@cdsnet.net (Jaye Mathisen) Subject: Re: It appears to be impossible to build a kernel w/o networking... References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > If so, then the things should be marked mandatory, ala npx0. Well, you don't even tell us where the problem is. Last time i tried it, it _was_ possible, albeit with a few warnings of the build process (some expected symbols weren't found in symorder). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Aug 22 00:05:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA21786 for hackers-outgoing; Fri, 22 Aug 1997 00:05:37 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA21778 for ; Fri, 22 Aug 1997 00:05:30 -0700 (PDT) Received: (qmail 29323 invoked by uid 1000); 22 Aug 1997 07:05:48 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [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: <199708220602.CAA09267@smoke.marlboro.vt.us> Date: Fri, 22 Aug 1997 00:05:48 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: john hood Subject: Re: Final request for help with release. (DPT boot floppy) Cc: Jaye Mathisen , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The hack with sleep and family life :-) What kind of boot/install floppy for which version? I'll build it. Simon From owner-freebsd-hackers Fri Aug 22 00:38:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23129 for hackers-outgoing; Fri, 22 Aug 1997 00:38:38 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA23124 for ; Fri, 22 Aug 1997 00:38:34 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA28436; Fri, 22 Aug 1997 09:38:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA05144; Fri, 22 Aug 1997 09:36:14 +0200 (MET DST) Message-ID: <19970822093613.ES33724@uriah.heep.sax.de> Date: Fri, 22 Aug 1997 09:36:13 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: tom@sdf.com (Tom Samplonius) Subject: Re: Final request for help with release. (DPT boot floppy) References: <25619.872204476@time.cdrom.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Samplonius on Aug 21, 1997 17:25:41 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Samplonius wrote: > But according to recent discusions, core has rejected the DPT driver as > it stands... Which `core'? Your core memory? Dunno. The NetBSD core team? Dunno. If the term `core', as you're using it, stands as an abbreviation for ``The FreeBSD core team'', then i'm surprised to hear that you're a member of it, apparently. Otherwise, how did you learn this news? I believe i'm a member of this core team, and i frankly can't remember any decision of the kind you're quoting above. So the only explanation, short of you throwing a lie around, is that it must have been some other `core'. Stop spreading misinformation, and please, think before posting. Sentences like these can quickly start major flame wars, and insult personal feelings, as you've already seen from Simon's reaction (which is, assuming your words would be truth, understandable). The truth is, the developer who volunteered to do the DPT driver integration, is Justin Gibbs. (He's incidentally also a member of the FreeBSD core team, but that doesn't matter much in this respect except that one can take it as a sign of some experience in FreeBSD matters.) He had some critics on the DPT driver code (which he discussed with Simon), but he never claimed he would reject the driver wholesale. No, i don't speak for the core team (can't do so without prior discussion, obviously), but felt some words of correction were due now, immediately. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Aug 22 00:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23581 for hackers-outgoing; Fri, 22 Aug 1997 00:49:13 -0700 (PDT) Received: from argus.tfs.net (pm3-p41.tfs.net [206.154.183.233]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23576 for ; Fri, 22 Aug 1997 00:49:09 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id CAA01954 for freebsd-hackers@freebsd.org; Fri, 22 Aug 1997 02:49:07 -0500 (CDT) From: Jim Bryant Message-Id: <199708220749.CAA01954@argus.tfs.net> Subject: Re: Get more visitors! In-Reply-To: <199708222027DAA6398@post.com> from "pai@somemore4u.com" at "Aug 22, 97 01:41:58 am" To: freebsd-hackers@freebsd.org Date: Fri, 22 Aug 1997 02:49:06 -0500 (CDT) Reply-To: /dev/null@argus.tfs.net Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > From POPmail Fri Aug 22 01:20:02 1997 > From: pai@somemore4u.com > Date: Fri, 22 Aug 1997 01:41:58 -0400 (EDT) > To: pai@somemore4u.com > Comments: Authenticated sender is > Reply-to: getit@somemore4u.com > Subject: Get more visitors! > Message-Id: <199708222027DAA6398@post.com> > Sender: owner-freebsd-hackers@FreeBSD.ORG > X-Loop: FreeBSD.org > Precedence: bulk > X-UIDL: f9b14c8647a1d7374edba647e99b4241 I'm getting tired of spam... Let's fight fire with fire.... For some spam to spam the spammers with, please download the file: ftp://ftp.cdrom.com/pub/FreeBSD/incoming/spam.wav [1.5 megs] And send a copy to everyone that spams you too!!!! I DON'T WANT ANY SPAM!@# 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" ------------------------------------------------------------------------------ Internet: jbryant@tfs.net AX.25 Packet: kc5vdj@wv0t.#neks.ks.usa.noam voice: KC5VDJ - 6 Meters AM/FM/SSB, 2 Meters AM/FM/SSB, 70cm FM. grid: EM28PW ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Fri Aug 22 01:00:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA24076 for hackers-outgoing; Fri, 22 Aug 1997 01:00:09 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24066 for ; Fri, 22 Aug 1997 01:00:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id AAA01598; Fri, 22 Aug 1997 00:59:37 -0700 (PDT) To: Simon Shapiro cc: Tom Samplonius , hackers@FreeBSD.ORG, Jaye Mathisen Subject: Re: Final request for help with release. (DPT boot floppy) In-reply-to: Your message of "Thu, 21 Aug 1997 23:11:49 PDT." Date: Fri, 22 Aug 1997 00:59:37 -0700 Message-ID: <1595.872236777@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Sure, take the patches from sendero-ppp.i-connect.net/crash and commit > > them. > > > > But according to recent discusions, core has rejected the DPT driver > > as > > it stands... > > Good to know. Thanx! Nobody told me that. Now I know what to do. These individuals do not speak for core. Jordan From owner-freebsd-hackers Fri Aug 22 01:05:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA24364 for hackers-outgoing; Fri, 22 Aug 1997 01:05:33 -0700 (PDT) Received: from alpha.netvision.net.il (root@alpha.NetVision.net.il [194.90.1.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24352 for ; Fri, 22 Aug 1997 01:05:26 -0700 (PDT) Received: from Burka.NetVision.net.il (burka.NetVision.net.il [194.90.1.23]) by alpha.netvision.net.il (8.8.6/8.8.6) with SMTP id LAA18326; Fri, 22 Aug 1997 11:05:11 +0300 (IDT) Message-ID: X-Mailer: XFMail 1.2-alpha [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: X-XFMail-Comment: Experimental version - for developers only Date: Fri, 22 Aug 1997 11:05:15 +0300 (IDT) X-Face: #v>4HN>#D_"[olq9y`HqTYkLVB89Xy|3')Vs9v58JQ*u-xEJVKY`xa.}E?z0RkLI/P&;BJmi0#u=W0).-Y'J4(dw{"54NhSG|YYZG@[)(`e! >jN#L!~qI5fE-JHS+< Organization: NetVision Ltd. From: Gennady Sorokopud To: Simon Shapiro Subject: Re: "Content-Type: text/plain; charset=iso-8859-8" Cc: freebsd-hackers@FreeBSD.ORG, (Joerg Wunsch) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! On 21-Aug-97 Simon Shapiro wrote: > > Formal Apologies > > With great humility and many thanks I submit my apologies to all > who got itrritated/agitated/annoyed by the fornt selection in my > (not anymore) favorite E-Mil program. > > The sole cause of this screwup is Gennady's inability to release > XFmail without having Hebrew as the default font (told you it was > not my fault :-). The fact that I did not check what the default > font is is totally irrelevant. Heey, the default font is us-ascii !!! You probably just kept your config file during upgrade or something. You've been sending messages with iso-8859-8 for a long time (and not a single one was in Hebrew :-( ). > I promise it will not happen again. Not before the next release... > > Cheers and (seriously) many thanks for a great O/S... > > Simon Best regards. -------- Gennady B. Sorokopud - System programmer at NetVision Israel. E-Mail: Gennady Sorokopud PGP public key is available by fingering gena@netvision.net.il This message was sent at 22-Aug-97 11:05:15 by XFMail From owner-freebsd-hackers Fri Aug 22 01:18:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA24902 for hackers-outgoing; Fri, 22 Aug 1997 01:18:58 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24896 for ; Fri, 22 Aug 1997 01:18:55 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA01659; Fri, 22 Aug 1997 01:18:32 -0700 (PDT) To: Simon Shapiro cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-reply-to: Your message of "Thu, 21 Aug 1997 23:11:48 PDT." Date: Fri, 22 Aug 1997 01:18:32 -0700 Message-ID: <1655.872237912@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The only way I know to create a boot floppy (and they work, trust me :-) is > really ugly: > > * Start make release > * Tail -f the output. > * Once you see that the entire sys directory checked out from CVS, do: > > cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys Or: 1. Recreate DPT.LIST patches to be relative to /usr/src 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST From owner-freebsd-hackers Fri Aug 22 01:35:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25535 for hackers-outgoing; Fri, 22 Aug 1997 01:35:25 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25524 for ; Fri, 22 Aug 1997 01:35:19 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA15386 for hackers@freebsd.org; Fri, 22 Aug 1997 09:26:24 +0200 From: Luigi Rizzo Message-Id: <199708220726.JAA15386@labinfo.iet.unipi.it> Subject: snd970821.tgz available (fwd) To: hackers@freebsd.org Date: Fri, 22 Aug 1997 09:26:23 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A new snap of my sound driver is available at http://www.iet.unipi.it/~luigi/snd970821.tgz ftp://www.iet.unipi.it/~luigi/snd970821.tgz With respect to the previous snap, this one includes many changes to the documentation, some improvements to the DMA code with added functionalities to support real time applications, and a driver for "timidity", a midi-to-pcm converter. I have tested the driver with raplayer3.0 for FreeBSD, the realaudio player, and it works pretty well. Also, I have done a bit more testing on OPTi931 devices (they work fine in play, but do not in capture mode) and added PnP ids for some cards for which I got feedback from the users. Please try out this code, and send feedback on how it works. I am interested in success and failures. In both cases try to include details on your sound card, and possibly the output of "dmesg" (the section related to PnP probe and to audio device attach). Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Aug 22 01:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25563 for hackers-outgoing; Fri, 22 Aug 1997 01:35:48 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25557 for ; Fri, 22 Aug 1997 01:35:45 -0700 (PDT) Received: (qmail 5814 invoked by uid 1000); 22 Aug 1997 08:36:02 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1595.872236777@time.cdrom.com> Date: Fri, 22 Aug 1997 01:36:02 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: Final request for help with release. (DPT boot floppy) Cc: Tom Samplonius , hackers@FreeBSD.ORG, Jaye Mathisen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 22-Aug-97 you wrote: > > > Sure, take the patches from sendero-ppp.i-connect.net/crash and > > > commit > > > them. > > > > > > But according to recent discusions, core has rejected the DPT > > > driver > > > as > > > it stands... > > > > Good to know. Thanx! Nobody told me that. Now I know what to do. > > These individuals do not speak for core. Good! My worst weakness is the ability to connect names and faces. Without faces it is even worst. BTW, the DPT driver for -current is just about completed. Just some minor cleanup and some testing. Will be done by tomorrow. Simon From owner-freebsd-hackers Fri Aug 22 01:35:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25585 for hackers-outgoing; Fri, 22 Aug 1997 01:35:52 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25576 for ; Fri, 22 Aug 1997 01:35:49 -0700 (PDT) Received: (qmail 5809 invoked by uid 1000); 22 Aug 1997 08:36:02 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <1655.872237912@time.cdrom.com> Date: Fri, 22 Aug 1997 01:36:02 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "Jordan K. Hubbard" Subject: Re: Final request for help with release. (DPT boot floppy) Cc: Jaye Mathisen , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi "Jordan K. Hubbard"; On 22-Aug-97 you wrote: > > The only way I know to create a boot floppy (and they work, trust me > > :-) is > > really ugly: > > > > * Start make release > > * Tail -f the output. > > * Once you see that the entire sys directory checked out from CVS, do: > > > > cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys > > Or: > > 1. Recreate DPT.LIST patches to be relative to /usr/src > > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST No Kidding!!! This one gets framed. I am in awe... Really! Thanx! Simon From owner-freebsd-hackers Fri Aug 22 04:58:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA04292 for hackers-outgoing; Fri, 22 Aug 1997 04:58:22 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA04287 for ; Fri, 22 Aug 1997 04:58:16 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id EAA00987; Fri, 22 Aug 1997 04:57:39 -0700 (PDT) Date: Fri, 22 Aug 1997 04:57:39 -0700 (PDT) Message-Id: <199708221157.EAA00987@silvia.HIP.Berkeley.EDU> To: Shimon@i-Connect.Net CC: tom@sdf.com, hackers@FreeBSD.ORG, mrcpu@cdsnet.net, nate@mt.sri.com In-reply-to: (message from Simon Shapiro on Thu, 21 Aug 1997 23:11:48 -0700 (PDT)) Subject: Re: Final request for help with release. (DPT boot floppy) From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I take this as a compliment. Thank you. How high is the load in your test. * We reject here anything under 256 concurrent processes and release after * 1024 concurrent processes ran continually for 48 hours. Then it goes to * System Test which does who know what... * * Simon * * Almost forgot; Still have to see a Solaris box survive this test. Let * alone perform as well as FreeBSD in these casual tests. I have also seen mysterious lockups (for a few seconds) with Solaris x86 when I bombarded more than two twin-channel controllers (Adaptec 3940W/UW) with lots of requests. FreeBSD had no problems whatsoever. Also, the maximum number of transactions (8KB random reads) per second of Solaris x86 maxed out at around 2,500, while FreeBSD went as high as 4,500 on identical hardware. This is with fast-wide SCSI -- with ultra-wide SCSI, FreeBSD went to 4,800 and Solaris couldn't run in ultra-wide mode. Also, FreeBSD could have been much higher if we used all twin-channel controllers, but we only used single-channel controllers because of the "identical hardware" requirement. This is with FreeBSD 2.2-stable of about half a year ago and Solaris x86 2.5.1 (the latast at that time). Satoshi From owner-freebsd-hackers Fri Aug 22 05:01:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA04446 for hackers-outgoing; Fri, 22 Aug 1997 05:01:27 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA04441 for ; Fri, 22 Aug 1997 05:01:22 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id FAA01002; Fri, 22 Aug 1997 05:01:10 -0700 (PDT) Date: Fri, 22 Aug 1997 05:01:10 -0700 (PDT) Message-Id: <199708221201.FAA01002@silvia.HIP.Berkeley.EDU> To: joerg_wunsch@uriah.heep.sax.de CC: hackers@FreeBSD.ORG, tom@sdf.com In-reply-to: <19970822093613.ES33724@uriah.heep.sax.de> (j@uriah.heep.sax.de) Subject: Re: Final request for help with release. (DPT boot floppy) From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * No, i don't speak for the core team (can't do so without prior * discussion, obviously), but felt some words of correction were due * now, immediately. FWIW, I would like to endorse this message. (Should I pgp sign it? :) Satoshi From owner-freebsd-hackers Fri Aug 22 09:17:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16972 for hackers-outgoing; Fri, 22 Aug 1997 09:17:58 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA16963 for ; Fri, 22 Aug 1997 09:17:53 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1wNL-0003Sl-00; Fri, 22 Aug 1997 09:15:51 -0700 Date: Fri, 22 Aug 1997 09:15:50 -0700 (PDT) From: Tom Samplonius To: Joerg Wunsch cc: hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <19970822093613.ES33724@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Aug 1997, J Wunsch wrote: > As Tom Samplonius wrote: > > > But according to recent discusions, core has rejected the DPT driver as > > it stands... > > Which `core'? Your core memory? Dunno. The NetBSD core team? > Dunno. If the term `core', as you're using it, stands as an > abbreviation for ``The FreeBSD core team'', then i'm surprised to hear > that you're a member of it, apparently. Otherwise, how did you learn > this news? I believe i'm a member of this core team, and i frankly > can't remember any decision of the kind you're quoting above. So the > only explanation, short of you throwing a lie around, is that it must > have been some other `core'. That is what the driver writer said in freebsd-scsi. > Stop spreading misinformation, and please, think before posting. > Sentences like these can quickly start major flame wars, and insult > personal feelings, as you've already seen from Simon's reaction (which > is, assuming your words would be truth, understandable). Flame wars? Have you seen any flames yet? The only flames I see, are coming from you. Rather than freaking out about this, perhaps you should just ask to see where this was mentioned. Don't shoot the messager. I'm basically repeating what was said in freebsd-scsi. Which was that the dpt driver would not be integrated as-is. This is NOT misinformation. Check the archives. As for Simon's reaction, I don't know. My original message was to Jordon, who's statement that an easy way to get a dpt bootable disk would be to get the dpt driver into current, to which I wanted to make two points: that patches to current are available now, and that the dpt driver has is apparently not acceptable as-is. > The truth is, the developer who volunteered to do the DPT driver > integration, is Justin Gibbs. (He's incidentally also a member of the > FreeBSD core team, but that doesn't matter much in this respect except > that one can take it as a sign of some experience in FreeBSD matters.) > He had some critics on the DPT driver code (which he discussed with > Simon), but he never claimed he would reject the driver wholesale. I've never heard Justin say yes or no on this matter. I've exchanged private e-mail with him some time ago, at which point he was going to be integrating the driver. However, since the dpt requires modification in other parts of the system beyond the SCSI subsystem, I doubt that Justin in the only one involved. A key issue seems to be software interupts. The dtp driver is apparently the only driver to use them. > No, i don't speak for the core team (can't do so without prior > discussion, obviously), but felt some words of correction were due > now, immediately. I feel some words of correction are necessary. If you don't won't to start flame wars, why didn't you just aske "where did you here that core wouldn't the accept the driver?", and I could have answered "freebsd-scsi", and everyone would be happy. > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > Tom From owner-freebsd-hackers Fri Aug 22 09:29:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA17439 for hackers-outgoing; Fri, 22 Aug 1997 09:29:21 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA17432 for ; Fri, 22 Aug 1997 09:29:17 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1wYO-0003T9-00; Fri, 22 Aug 1997 09:27:16 -0700 Date: Fri, 22 Aug 1997 09:27:15 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: hackers@freebsd.org, Nate Williams Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Aug 1997, Simon Shapiro wrote: > > Hi Tom Samplonius; On 22-Aug-97 you wrote: > > > > On Thu, 21 Aug 1997, Nate Williams wrote: > > > > > > And then I'll just go back to solaris which works :) > > > > > > And is slower than a dog. I guess you'd need that RAID system to get > > > decent I/O performance out of it. :) :) > > > > According to a simple test with dd that I ran on the identical > > hardware > > with 2.2-stable and Solaris 2.5.1 x86, the performance results are > > basically the same. > > > > Tom > > I take this as a compliment. Thank you. How high is the load in your test. > We reject here anything under 256 concurrent processes and release after > 1024 concurrent processes ran continually for 48 hours. Then it goes to > System Test which does who know what... For me a "simple" test is a single dd. Also, Solaris 2.51 is getting kind moldy anyhow. There are all kinds of patches to be installed, which I didn't want to get into. > Simon Tom From owner-freebsd-hackers Fri Aug 22 09:46:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA18599 for hackers-outgoing; Fri, 22 Aug 1997 09:46:51 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18586 for ; Fri, 22 Aug 1997 09:46:47 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA09503; Fri, 22 Aug 1997 10:46:33 -0600 (MDT) Date: Fri, 22 Aug 1997 10:46:33 -0600 (MDT) Message-Id: <199708221646.KAA09503@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: hackers@freebsd.org, tom@sdf.com (Tom Samplonius) Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <19970822093613.ES33724@uriah.heep.sax.de> References: <25619.872204476@time.cdrom.com> <19970822093613.ES33724@uriah.heep.sax.de> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > But according to recent discusions, core has rejected the DPT driver as > > it stands... > > Which `core'? Your core memory? Dunno. The NetBSD core team? > Dunno. If the term `core', as you're using it, stands as an > abbreviation for ``The FreeBSD core team'', then i'm surprised to hear > that you're a member of it, apparently. Otherwise, how did you learn > this news? I believe i'm a member of this core team, and i frankly > can't remember any decision of the kind you're quoting above. Whoa now. Slow down, take a deep breath, and go read the archives. Simon *explicitly* stated that core (yeah, that's the one you belong to) rejected the DPT driver for a number of reasons, all valid, and all listed by Simon. They will be fixed, but until they are fixed it won't be integrated. Nate From owner-freebsd-hackers Fri Aug 22 10:04:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20014 for hackers-outgoing; Fri, 22 Aug 1997 10:04:13 -0700 (PDT) Received: from argus.tfs.net (node1.tfs.net [207.2.220.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19880 for ; Fri, 22 Aug 1997 10:03:13 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id LAA02587; Fri, 22 Aug 1997 11:39:18 -0500 (CDT) From: Jim Bryant Message-Id: <199708221639.LAA02587@argus.tfs.net> Subject: Re: Get more visitors! In-Reply-To: from Richard Wackerbarth at "Aug 22, 97 03:27:48 am" To: rkw@dataplex.net (Richard Wackerbarth) Date: Fri, 22 Aug 1997 11:39:17 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Operating-System: FreeBSD 2.2.2-RELEASE #0: Wed Jul 9 01:01:24 CDT 1997 X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > >I'm getting tired of spam... > As am I. > > >I DON'T WANT ANY SPAM!@# > Unfortunately, I place your posting in the same category. > I would have prefered to have received neither. You simply > compounded the problem. actually congress compounded the problem by not legislating against junk email when the bill was before them this year, but then what do you expect out of conservatives... it's sitting there acting like sheep that compounds the problem... the "oh i'll just ignore it until it goes away" attitude just doesn't work. it didn't work with hitler, it didn't work with our conservative congress either. the only way to remove junk email from the net, until legislation making such illegal is in place, it to simply fight fire with fire, even if it logjams the entire freaking internet. don't write to me, write to your freaking congressman. 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" ------------------------------------------------------------------------------ Internet: jbryant@tfs.net AX.25 Packet: kc5vdj@wv0t.#neks.ks.usa.noam voice: KC5VDJ - 6 Meters AM/FM/SSB, 2 Meters AM/FM/SSB, 70cm FM. grid: EM28PW ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ From owner-freebsd-hackers Fri Aug 22 10:43:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA21354 for hackers-outgoing; Fri, 22 Aug 1997 10:43:08 -0700 (PDT) Received: from unicorn.uk1.vbc.net (unicorn.uk1.vbc.net [194.207.2.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA21346 for ; Fri, 22 Aug 1997 10:43:03 -0700 (PDT) Received: from localhost (gordon@localhost) by unicorn.uk1.vbc.net (8.8.5/8.8.5) with SMTP id SAA07407 for ; Fri, 22 Aug 1997 18:33:35 +0100 Date: Fri, 22 Aug 1997 18:33:33 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn Reply-To: Gordon Henderson To: hackers@freebsd.org Subject: Problems with > 256MB of RAM Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running FreeBSD 2.2-STABLE on a machine with 384MB of RAM. (will be upgraded to 512MB soon). I'm having problems running named with very large zone files. The machine panics and reboots. A 'top' running on the machine at the time shows: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 1418 root 105 0 235M 236M RUN 8:16 97.01% 97.01% named It's always after it's allocated 235MB. The panic message is always: panic: get_pv_entry: cannot get a pv_entry_t The kernel has had 3 patches supplied by David Greenman , modifying files /src/sys/i386/conf/Makefile.i386 /src/sys/i386/include/pmap.h /src/sys/i386/include/vmparam.h The only other bits that have been modified in the kernel config file (apart from deleting unused drivers, etc.) are: maxusers 32 options "MAXMEM=393216" # 384MB options "NMBCLUSTERS=2048" options "MAXDSIZ=402653184" # 384MB options "DFLDSIZ=402653184" # 384MB BOUNCE_BUFFERS are commented out. Heres the catch: If I run a program that grabs all available memory in 1MB chunks (and writes to it as it grabs it), then exits (380MB later), then I can run named and it grows up to full size happily. (I'm running named 8.1.1, but I see the same with 4.9.6-REL). Whn it's running, a top output shows: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 189 root 2 0 236M 94376K select 0:00 0.00% 0.00% named So it's only trying to grab an extra MB... Any insight would be greatly appreciated. Gordon From owner-freebsd-hackers Fri Aug 22 10:48:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA21867 for hackers-outgoing; Fri, 22 Aug 1997 10:48:57 -0700 (PDT) Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [207.155.21.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA21841 for ; Fri, 22 Aug 1997 10:48:50 -0700 (PDT) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.5/8.8.5) with ESMTP id KAA05873; Fri, 22 Aug 1997 10:20:53 -0700 (PDT) Message-Id: <199708221720.KAA05873@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.0delta 6/3/97 To: "Jordan K. Hubbard" Cc: Simon Shapiro , Jaye Mathisen , hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Aug 1997 10:20:53 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> The only way I know to create a boot floppy (and they work, trust me :-) is >> really ugly: > Or: > 1. Recreate DPT.LIST patches to be relative to /usr/src > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST Wow. That simple? What's in the ellipsis? ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet A neighbor's bull broke down Nasrudin's fence and ran back to it's owner. Nasrudin followed and began to lash it. "How dare you whip my bull!" roared the owner. "Never mind about that, you," said Nasrudin. "_he_ knows about it. The matter is between the two of us." From owner-freebsd-hackers Fri Aug 22 11:00:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA22636 for hackers-outgoing; Fri, 22 Aug 1997 11:00:52 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA22629 for ; Fri, 22 Aug 1997 11:00:48 -0700 (PDT) Received: (qmail 3823 invoked by uid 1000); 22 Aug 1997 18:01:05 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 Aug 1997 11:01:05 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Final request for help with release. (DPT boot floppy) Cc: hackers@FreeBSD.ORG, Nate Williams Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 22-Aug-97 you wrote: .. > For me a "simple" test is a single dd. Simple it is. Reflective or indicative of expected workload? Not necessarily. Try st.c from my archive instead. It will do sequential or random, read only, write only, read-modify-write and probably something else I forgot. It even times and computes I/O per second, MB/sec and few other things. Simon From owner-freebsd-hackers Fri Aug 22 11:02:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA22757 for hackers-outgoing; Fri, 22 Aug 1997 11:02:39 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA22751 for ; Fri, 22 Aug 1997 11:02:34 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA03280; Fri, 22 Aug 1997 11:01:40 -0700 (PDT) To: Dave Hayes cc: Simon Shapiro , Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-reply-to: Your message of "Fri, 22 Aug 1997 10:20:53 PDT." <199708221720.KAA05873@hokkshideh.jetcafe.org> Date: Fri, 22 Aug 1997 11:01:40 -0700 Message-ID: <3276.872272900@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> The only way I know to create a boot floppy (and they work, trust me :-) i s > >> really ugly: > > Or: > > 1. Recreate DPT.LIST patches to be relative to /usr/src > > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST > > Wow. That simple? What's in the ellipsis? Whatever your other arguments to make release might be? ;-) Jordan From owner-freebsd-hackers Fri Aug 22 11:09:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23223 for hackers-outgoing; Fri, 22 Aug 1997 11:09:58 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA23216 for ; Fri, 22 Aug 1997 11:09:56 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA26392; Fri, 22 Aug 1997 11:00:27 -0700 From: Terry Lambert Message-Id: <199708221800.LAA26392@phaeton.artisoft.com> Subject: Re: Final request for help with release. (DPT boot floppy) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 22 Aug 1997 11:00:27 -0700 (MST) Cc: Shimon@i-Connect.Net, mrcpu@cdsnet.net, hackers@FreeBSD.ORG In-Reply-To: <1655.872237912@time.cdrom.com> from "Jordan K. Hubbard" at Aug 22, 97 01:18:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > * Start make release > > * Tail -f the output. > > * Once you see that the entire sys directory checked out from CVS, do: > > > > cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys > > Or: > > 1. Recreate DPT.LIST patches to be relative to /usr/src > > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST I suppose these patches are intended to include changes to the file /sys/i386/conf/GENERIC, as well? ...otherwise the code will be there, but the kernel won't contain it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 22 11:10:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23301 for hackers-outgoing; Fri, 22 Aug 1997 11:10:31 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA23295 for ; Fri, 22 Aug 1997 11:10:27 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id LAA18324; Fri, 22 Aug 1997 11:10:03 -0700 (PDT) Date: Fri, 22 Aug 1997 11:10:02 -0700 (PDT) From: Jaye Mathisen To: Simon Shapiro cc: john hood , hackers@FreeBSD.ORG Subject: All fixed. (The hard way)...Re: Final request for help with release. (DPT boot floppy) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I appreciate the offers, however, I have bashed it into shape in the following manner: Although my boot.flp isn't usable for install, it does boot and apparently clears the appropriate bits, such that using a 1.1.10 boot floppy from the sendero site w/o hitting the reset button, and just allowing it to panic, then quickly swap in the 1.1.10 version floppy lets it boot correctly. I was then able to mount fixit, chroot, ifconfig, and build a new kernel that works. I appreciate all the email traffic offering suggestions as to what to try next... If I power cycled it, or hit reset it would never come up right... Next quest is to see why I can't make a working bootable floppy, and send in the few patches I already have for it. On Fri, 22 Aug 1997, Simon Shapiro wrote: > The hack with sleep and family life :-) > > What kind of boot/install floppy for which version? I'll build it. > > Simon > From owner-freebsd-hackers Fri Aug 22 11:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23439 for hackers-outgoing; Fri, 22 Aug 1997 11:12:10 -0700 (PDT) Received: from shrike.depaul.edu (shrike.depaul.edu [140.192.1.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA23431 for ; Fri, 22 Aug 1997 11:12:04 -0700 (PDT) Received: from qslater (dept91.it-ias.depaul.edu [140.192.55.91]) by shrike.depaul.edu (8.8.3/8.5) with SMTP id MAA23902; Fri, 22 Aug 1997 12:18:08 -0500 (CDT) Message-Id: <199708221718.MAA23902@shrike.depaul.edu> From: qhartsla@shrike.depaul.edu (QSlater) To: freebsd-hackers@FreeBSD.org Subject: Re: 3.0-970502-SNAP now on ftp://ftp.freebsd.org/pub/FreeBSD/ Organization: DePaul University Date: Fri, 22 Aug 1997 17:29:19 GMT Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm mainframe with some UNIX and FreeBSD what can I do ? qslater@wppost.depaul.edu >>Yes indeed, it's finally time for our first 3.0 SNAPshot, available >>now from ftp.freebsd.org and its mirrors. I will also be putting this >>snapshot on CDROM, where it will be shipped to subscribers of Walnut >>Creek CDROM's SNAP CD release program. >> >>I've probably also stated this more than enough times in previous >>announcements but what the heck, since people forget (and a price >>increase is an important issue to many people), I'll say it again: >> >> The retail price of the SNAP CDs has now increased to $39.95 >> due to the fact that it's now a 2 CD set (the 2nd CD >> containing the complete, unpacked FreeBSD CVS repository and >> other resources). The subscription price of $14.95 remains >> unchanged and you can also quit a subscription at any time (no >> "minimum purchase" is required). Since this CD was always >> targetted primarily at subscription people, I'm hoping that >> this will not result in any undue hardship. >> >> >>And now to the release notes for this 3.0 SNAP... >> >>I should note that the release notes don't really do this SNAPshot >>justice - a LOT of things have changed and only some of them are noted >>in the "What's New" section. Sorry, but keeping up with this for >>SNAPs is a bit of a job, and when the final 3.0 release rolls around, >>we'll go through the CVS change history in more detail to determine a >>better "what's new" list. >> >> >> >> RELEASE NOTES >> FreeBSD Release 3.0-SNAPSHOT >> >>This is a SNAPSHOT release of FreeBSD 3.0-CURRENT and is aimed primarily >>at release testers. Some parts of the documentation may not be updated >>yet and should be reported if and when seen. Naturally, any installation >>failures or crashes should also be reported ASAP by sending mail to >>freebsd-bugs@FreeBSD.org or using the send-pr command (those preferring a >>WEB based interface can also see http://www.freebsd.org/send-pr.html). >> >>For information about FreeBSD and the layout of the 3.0-SNAPSHOT release >>directory, see ABOUT.TXT. For installation instructions, see the >>INSTALL.TXT and HARDWARE.TXT files. >> >> >>1. What's new since 2.2.X-RELEASE >>------------------------------------ >> >>top(1) is now part of the base system. It was too system-dependant yet >>considered generally useful enough to be maintained in ports. >> >>The kernel code from 4.4BSD-Lite2 has been (finally) merged. >> >>The SMP (Symmetric MultiProcessing) branch has been merged into >>-current. >> >>Use the new if_multiaddrs list for multicast addresses rather than the >>previous hackery involving struct in_ifaddr and arpcom. Get rid of the >>abominable multi_kludge. >> >>2. Supported Configurations >>--------------------------- >> >>FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus >>based PC's, ranging from 386sx to Pentium class machines (though the >>386sx is not recommended). Support for generic IDE or ESDI drive >>configurations, various SCSI controller, network and serial cards is >>also provided. >> >>What follows is a list of all peripherals currently known to work with >>FreeBSD. Other configurations may also work, we have simply not as yet >>received confirmation of this. >> >> >>2.1. Disk Controllers >>--------------------- >> >>WD1003 (any generic MFM/RLL) >>WD1007 (any generic IDE/ESDI) >>IDE >>ATA >> >>Adaptec 1510 series ISA SCSI controllers (not for bootable devices) >>Adaptec 152x series ISA SCSI controllers >>Adaptec 1535 ISA SCSI controllers >>Adaptec 154x series ISA SCSI controllers >>Adaptec 174x series EISA SCSI controller in standard and enhanced mode. >>Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI >>controllers. >>Adaptec AIC7850 on-board SCSI controllers. >> >>Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x >>and SoundBlaster SCSI cards. >> >>** Note: You cannot boot from the SoundBlaster cards as they have no >> on-board BIOS, such being necessary for mapping the boot device into the >> system BIOS I/O vectors. They're perfectly usable for external tapes, >> CDROMs, etc, however. The same goes for any other AIC-6x60 based card >> without a boot ROM. Some systems DO have a boot ROM, which is generally >> indicated by some sort of message when the system is first powered up >> or reset, and in such cases you *will* also be able to boot from them. >> Check your system/board documentation for more details. >> >>Buslogic 545S & 545c >>Buslogic 445S/445c VLB SCSI controller >>Buslogic 742A, 747S, 747c EISA SCSI controller. >>Buslogic 946c PCI SCSI controller >>Buslogic 956c PCI SCSI controller >> >>SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI >>controllers: >> ASUS SC-200 >> Data Technology DTC3130 (all variants) >> NCR cards (all) >> Symbios cards (all) >> Tekram DC390W, 390U and 390F >> Tyan S1365 >> >>Tekram DC390 and DC390T controllers (maybe other cards based on the >>AMD 53c974 as well). >> >>NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. >> >>DTC 3290 EISA SCSI controller in 1542 emulation mode. >> >>UltraStor 14F, 24F and 34F SCSI controllers. >> >>Seagate ST01/02 SCSI controllers. >> >>Future Domain 8xx/950 series SCSI controllers. >> >>WD7000 SCSI controller. >> >>With all supported SCSI controllers, full support is provided for >>SCSI-I & SCSI-II peripherals, including Disks, tape drives (including >>DAT and 8mm Exabyte) and CD ROM drives. >> >>The following CD-ROM type systems are supported at this time: >>(cd) SCSI interface (also includes ProAudio Spectrum and >> SoundBlaster SCSI) >>(mcd) Mitsumi proprietary interface (all models) >>(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary >> interface (562/563 models) >>(scd) Sony proprietary interface (all models) >>(wcd) ATAPI IDE interface (experimental and should be considered ALPHA >> quality!). >> >> >>2.2. Ethernet cards >>------------------- >> >>Allied-Telesis AT1700 and RE2000 cards >> >>AMD PCnet/PCI (79c970 & 53c974 or 79c974) >> >>SMC Elite 16 WD8013 ethernet interface, and most other WD8003E, >>WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT >>based clones. SMC Elite Ultra is also supported. >> >>DEC EtherWORKS III NICs (DE203, DE204, and DE205) >>DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) >>DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) >>DEC FDDI (DEFPA/DEFEA) NICs >> >>Fujitsu MB86960A/MB86965A >> >>HP PC Lan+ cards (model numbers: 27247B and 27252A). >> >>Intel EtherExpress (not recommended due to driver instability) >>Intel EtherExpress Pro/10 >>Intel EtherExpress Pro/100B PCI Fast Ethernet >> >>Isolan AT 4141-0 (16 bit) >>Isolink 4110 (8 bit) >> >>Novell NE1000, NE2000, and NE2100 ethernet interface. >> >>3Com 3C501 cards >> >>3Com 3C503 Etherlink II >> >>3Com 3c505 Etherlink/+ >> >>3Com 3C507 Etherlink 16/TP >> >>3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905 PCI and EISA >>(Fast) Etherlink III / (Fast) Etherlink XL >> >>Toshiba ethernet cards >> >>PCMCIA ethernet cards from IBM and National Semiconductor are also >>supported. >> >>Note that NO token ring cards are supported at this time as we're >>still waiting for someone to donate a driver for one of them. Any >>takers? >> >> >>2.3. Misc >>--------- >> >>AST 4 port serial card using shared IRQ. >> >>ARNET 8 port serial card using shared IRQ. >>ARNET (now Digiboard) Sync 570/i high-speed serial. >> >>Boca BB1004 4-Port serial card (Modems NOT supported) >>Boca IOAT66 6-Port serial card (Modems supported) >>Boca BB1008 8-Port serial card (Modems NOT supported) >>Boca BB2016 16-Port serial card (Modems supported) >> >>Cyclades Cyclom-y Serial Board. >> >>STB 4 port card using shared IRQ. >> >>SDL Communications Riscom/8 Serial Board. >>SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. >> >>Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, >>ONboard 4/16 and Brumby. >> >>Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound >>and Roland MPU-401 sound cards. >> >>Connectix QuickCam >>Matrox Meteor Video frame grabber >>Creative Labs Video Spigot frame grabber >>Cortex1 frame grabber >> >>HP4020i, Philips CDD2000 and PLASMON WORM (CDR) drives. >> >>PS/2 mice >> >>Standard PC Joystick >> >>X-10 power controllers >> >>GPIB and Transputer drivers. >> >>Genius and Mustek hand scanners. >> >> >>FreeBSD currently does NOT support IBM's microchannel (MCA) bus. >> >> >>3. Obtaining FreeBSD >>-------------------- >> >>You may obtain FreeBSD in a variety of ways: >> >>3.1. FTP/Mail >>------------- >> >>You can ftp FreeBSD and any or all of its optional packages from >>`ftp.freebsd.org' - the official FreeBSD release site. >> >>For other locations that mirror the FreeBSD software see the file >>MIRROR.SITES. Please ftp the distribution from the site closest (in >>networking terms) to you. Additional mirror sites are always welcome! >>Contact freebsd-admin@FreeBSD.org for more details if you'd like to >>become an official mirror site. >> >>If you do not have access to the Internet and electronic mail is your >>only recourse, then you may still fetch the files by sending mail to >>`ftpmail@decwrl.dec.com' - putting the keyword "help" in your message >>to get more information on how to fetch files using this mechanism. >>Please do note, however, that this will end up sending many *tens of >>megabytes* through the mail and should only be employed as an absolute >>LAST resort! >> >> >>3.2. CDROM >>---------- >> >>FreeBSD 2.1.7-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from: >> >> Walnut Creek CDROM >> 4041 Pike Lane, Suite D >> Concord CA 94520 >> 1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax) >> >>Or via the Internet from orders@cdrom.com or http://www.cdrom.com. >>Their current catalog can be obtained via ftp from: >> ftp://ftp.cdrom.com/cdrom/catalog. >> >>Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. >>FreeBSD 3.0-SNAP CDs are $39.95 or $14.95 with a FreeBSD-SNAP subscription >>(-RELEASE and -SNAP subscriptions are entirely separate). With a >>subscription, you will automatically receive updates as they are released. >>Your credit card will be billed when each disk is shipped and you may cancel >>your subscription at any time without further obligation. >> >>Shipping (per order not per disc) is $5 in the US, Canada or Mexico >>and $9.00 overseas. They accept Visa, Mastercard, Discover, American >>Express or checks in U.S. Dollars and ship COD within the United >>States. California residents please add 8.25% sales tax. >> >>Should you be dissatisfied for any reason, the CD comes with an >>unconditional return policy. >> >> >>4. Reporting problems, making suggestions, submitting code. >>----------------------------------------------------------- >> >>Your suggestions, bug reports and contributions of code are always >>valued - please do not hesitate to report any problems you may find >>(preferably with a fix attached, if you can!). >> >>The preferred method to submit bug reports from a machine with >>Internet mail connectivity is to use the send-pr command or use the CGI >>script at http://www.freebsd.org/send-pr.html. Bug reports >>will be dutifully filed by our faithful bugfiler program and you can >>be sure that we'll do our best to respond to all reported bugs as soon >>as possible. Bugs filed in this way are also visible on our WEB site >>in the support section and are therefore valuable both as bug reports >>and as "signposts" for other users concerning potential problems to >>watch out for. >> >>If, for some reason, you are unable to use the send-pr command to >>submit a bug report, you can try to send it to: >> >> freebsd-bugs@FreeBSD.org >> >>Note that send-pr itself is a shell script that should be easy to move >>even onto a totally different system. We much prefer if you could use >>this interface, since it make it easier to keep track of the problem >>reports. However, before submitting, please try to make sure whether >>the problem might have already been fixed since. >> >> >>Otherwise, for any questions or suggestions, please send mail to: >> >> freebsd-questions@FreeBSD.org >> >> >>Additionally, being a volunteer effort, we are always happy to have >>extra hands willing to help - there are already far more desired >>enhancements than we'll ever be able to manage by ourselves! To >>contact us on technical matters, or with offers of help, please send >>mail to: >> >> freebsd-hackers@FreeBSD.org >> >> >>Please note that these mailing lists can experience *significant* >>amounts of traffic and if you have slow or expensive mail access and >>are only interested in keeping up with significant FreeBSD events, you >>may find it preferable to subscribe instead to: >> >> freebsd-announce@FreeBSD.org >> >> >>All of the mailing lists can be freely joined by anyone wishing >>to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword >>`help' on a line by itself somewhere in the body of the message. This >>will give you more information on joining the various lists, accessing >>archives, etc. There are a number of mailing lists targeted at >>special interest groups not mentioned here, so send mail to majordomo >>and ask about them! >> >> >>5. Acknowledgements >>------------------- >> >>FreeBSD represents the cumulative work of many dozens, if not >>hundreds, of individuals from around the world who have worked very >>hard to bring you this release. For a complete list of FreeBSD >>project staffers, please see: >> >> http://www.freebsd.org/handbook/staff.html >> >>or, if you've loaded the doc distribution: >> >> file:/usr/share/doc/handbook/staff.html >> >>Additional FreeBSD helpers and beta testers: >> >> Coranth Gryphon Dave Rivers >> Kaleb S. Keithley Terry Lambert >> David Dawes Don Lewis >> >>Special mention to: >> >> Walnut Creek CDROM, without whose help (and continuing support) >> this release would never have been possible. >> >> Dermot McDonnell for his donation of a Toshiba XM3401B CDROM >> drive. >> >> Chuck Robey for his donation of a floppy tape streamer for >> testing. >> >> Larry Altneu and Wilko Bulte for providing us with Wangtek >> and Archive QIC-02 tape drives for testing and driver hacking. >> >> CalWeb Internet Services for the loan of a P6/200 machine for >> speedy package building. >> >> Everyone at Montana State University for their initial support. >> >> And to the many thousands of FreeBSD users and testers all over the >> world, without whom this release simply would not have been possible. >> >>We sincerely hope you enjoy this release of FreeBSD! >> >> The FreeBSD Project >> >> From owner-freebsd-hackers Fri Aug 22 11:15:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23662 for hackers-outgoing; Fri, 22 Aug 1997 11:15:42 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA23647 for ; Fri, 22 Aug 1997 11:15:29 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id LAA19009; Fri, 22 Aug 1997 11:13:58 -0700 (PDT) Date: Fri, 22 Aug 1997 11:13:57 -0700 (PDT) From: Jaye Mathisen To: Terry Lambert cc: "Jordan K. Hubbard" , Shimon@i-Connect.Net, hackers@FreeBSD.ORG Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <199708221800.LAA26392@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The current 2.2.2 DPT patch does patch GENERIC, so things should be fine. On Fri, 22 Aug 1997, Terry Lambert wrote: > > > * Start make release > > > * Tail -f the output. > > > * Once you see that the entire sys directory checked out from CVS, do: > > > > > > cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys > > > > Or: > > > > 1. Recreate DPT.LIST patches to be relative to /usr/src > > > > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST > > I suppose these patches are intended to include changes to the file > /sys/i386/conf/GENERIC, as well? ...otherwise the code will be there, > but the kernel won't contain it. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-hackers Fri Aug 22 11:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23731 for hackers-outgoing; Fri, 22 Aug 1997 11:16:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA23719 for ; Fri, 22 Aug 1997 11:16:14 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA26407; Fri, 22 Aug 1997 11:07:13 -0700 From: Terry Lambert Message-Id: <199708221807.LAA26407@phaeton.artisoft.com> Subject: Re: Final request for help with release. (DPT boot floppy) To: asami@cs.berkeley.edu (Satoshi Asami) Date: Fri, 22 Aug 1997 11:07:13 -0700 (MST) Cc: Shimon@i-Connect.Net, tom@sdf.com, hackers@FreeBSD.ORG, mrcpu@cdsnet.net, nate@mt.sri.com In-Reply-To: <199708221157.EAA00987@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Aug 22, 97 04:57:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have also seen mysterious lockups (for a few seconds) with Solaris > x86 when I bombarded more than two twin-channel controllers (Adaptec > 3940W/UW) with lots of requests. FreeBSD had no problems whatsoever. This is probably a PCI issue. Most Intel PCI bridges do not correctly arbitrate between more than two bus mastering PCI devices simultaneously. Stefan posted about this a while back. I think there's a newer chipset that actually supports any number of devices (up to the number of slots, anyway), but I don't remember the name of the thing off the top of my head. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 22 11:30:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA24434 for hackers-outgoing; Fri, 22 Aug 1997 11:30:35 -0700 (PDT) Received: from kiki.arlington.com (kiki.arlington.com [140.174.170.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA24427 for ; Fri, 22 Aug 1997 11:30:29 -0700 (PDT) Received: from localhost (snatcher@localhost) by kiki.arlington.com (8.8.7/8.8.5) with SMTP id LAA12186 for ; Fri, 22 Aug 1997 11:30:29 -0700 (PDT) Date: Fri, 22 Aug 1997 11:30:29 -0700 (PDT) From: Zach Copley To: hackers@FreeBSD.ORG Subject: Upper limit values set too low? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, recently I've switched my mail machine to FreeBSD, hoping that it would make a nice stable server. I've been encountering a few problems. The machine in question runs some mailing lists. First, I started to get error messages like this when the mailing lists were queueing: kiki /kernel: file: table is full kiki sendmail[6096]: EAA06091: SYSERR(UID0): Can't create transcript file xfEAA06091: Too many open files in system I eventually figured out that what was happening was that sendmail was attempting exceed the maximum number of files that are allowed open per process, which is a value that can be set with the sysctl utility. The solution was to set the value to a much higher number, which I did. Now I am getting some error messages like this: kiki sendmail[589]: BAA00581: SYSERR(daemon): ... openmailer(local): cannot fork: Resource temporarily unavailable The other thing is that when I attempt to open a large mailbox with Pine, it crashes and dumps core--something that never happens on any of my other Unix machines. eg: Aug 21 04:41:19 kiki /kernel: pid 1955 (pine), uid 1002: exited on signal6 (core dumped) What I'm wondering is if maybe there are some other upper limit values for kernel, etc., that may be set too low by default. Could that be the cause of these problems also? If so, what are these values, and what can I use to determine/adjust these values? If not, does anyone have any idea what could be causing these problems? The machine is: P120, 32-megs RAM, Adaptec 7880 SCSI/1-gig Quantum with Kernel Developer install of 2.2.2R with all of the defaults, and then I recompiled the kernel as outlined in the Handbook. Any suggestions would be very much appreciated. Thanks, Zach Copley -- .^....^. snatcher@pigdog.org ! .\/. ! http://www.pigdog.org (. oo .) ~RoR-Alucard~ `{""}' From owner-freebsd-hackers Fri Aug 22 11:47:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25389 for hackers-outgoing; Fri, 22 Aug 1997 11:47:35 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA25382 for ; Fri, 22 Aug 1997 11:47:29 -0700 (PDT) Received: (qmail 4567 invoked by uid 1000); 22 Aug 1997 18:47:46 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708221807.LAA26407@phaeton.artisoft.com> Date: Fri, 22 Aug 1997 11:47:46 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: Final request for help with release. (DPT boot floppy) Cc: tom@sdf.com, hackers@FreeBSD.ORG, mrcpu@cdsnet.net, nate@mt.sri.com, (Satoshi Asami) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 22-Aug-97 you wrote: > > I have also seen mysterious lockups (for a few seconds) with Solaris > > x86 when I bombarded more than two twin-channel controllers (Adaptec > > 3940W/UW) with lots of requests. FreeBSD had no problems whatsoever. > > This is probably a PCI issue. Most Intel PCI bridges do not > correctly arbitrate between more than two bus mastering PCI > devices simultaneously. > > Stefan posted about this a while back. > > I think there's a newer chipset that actually supports any number > of devices (up to the number of slots, anyway), but I don't remember > the name of the thing off the top of my head. You are right. We had here a terrible time with PCI bridges. Some will deliver interrupts before completion of DMA, some will lose interrupts, some will corrupt DMA transfers. Real party. Not only Intel but (for sure) the older DEC bridge (somethign with 50 in the name, vs. 51). Simon From owner-freebsd-hackers Fri Aug 22 11:47:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25393 for hackers-outgoing; Fri, 22 Aug 1997 11:47:36 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA25384 for ; Fri, 22 Aug 1997 11:47:31 -0700 (PDT) Received: (qmail 4546 invoked by uid 1000); 22 Aug 1997 18:47:46 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708221800.LAA26392@phaeton.artisoft.com> Date: Fri, 22 Aug 1997 11:47:45 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: Final request for help with release. (DPT boot floppy) Cc: mrcpu@cdsnet.net, hackers@FreeBSD.ORG, (Jordan K. Hubbard) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 22-Aug-97 you wrote: > > > * Start make release > > > * Tail -f the output. > > > * Once you see that the entire sys directory checked out from CVS, > > > do: > > > > > > cd /usr/src/sys;cat DPT.LIST | cpio -dmpv /wherever/usr/src/sys > > > > Or: > > > > 1. Recreate DPT.LIST patches to be relative to /usr/src > > > > 2. make release ... LOCAL_PATCHES=/some/place/DPT.LIST > > I suppose these patches are intended to include changes to the file > /sys/i386/conf/GENERIC, as well? ...otherwise the code will be there, > but the kernel won't contain it. Even I know that :-) The patch is a complete patch. BTW, it is relative to /usr/src. Simon From owner-freebsd-hackers Fri Aug 22 12:33:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA27712 for hackers-outgoing; Fri, 22 Aug 1997 12:33:30 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA27703 for ; Fri, 22 Aug 1997 12:33:27 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id NAA17299; Fri, 22 Aug 1997 13:36:12 -0600 (MDT) Date: Fri, 22 Aug 1997 13:36:12 -0600 (MDT) From: Brandon Gillespie To: jbryant@tfs.net cc: Richard Wackerbarth , freebsd-hackers@FreeBSD.ORG Subject: Join Cauce.. Re: Get more visitors! In-Reply-To: <199708221639.LAA02587@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Aug 1997, Jim Bryant wrote: > actually congress compounded the problem by not legislating against > junk email when the bill was before them this year, but then what do > you expect out of conservatives... > > it's sitting there acting like sheep that compounds the problem... > the "oh i'll just ignore it until it goes away" attitude just doesn't > work. it didn't work with hitler, it didn't work with our > conservative congress either. > > the only way to remove junk email from the net, until legislation > making such illegal is in place, it to simply fight fire with fire, > even if it logjams the entire freaking internet. > > don't write to me, write to your freaking congressman. Or join the Coalition Against Unsolicited Commercial Email. They are a legit professional organization which is lobbying and contacting congressmen everywhere to get the changes signed. I strongly suggest signing up with them: www.cauce.org -Brandon Gillespie (Sorry for the irrelevantness of this post, but this organization can always use more support). From owner-freebsd-hackers Fri Aug 22 13:22:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA29826 for hackers-outgoing; Fri, 22 Aug 1997 13:22:21 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA29818 for ; Fri, 22 Aug 1997 13:22:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA06397 for hackers@freebsd.org; Fri, 22 Aug 1997 22:22:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id WAA06768; Fri, 22 Aug 1997 22:05:53 +0200 (MET DST) Message-ID: <19970822220553.UQ39882@uriah.heep.sax.de> Date: Fri, 22 Aug 1997 22:05:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freebsd.org Subject: Re: Final request for help with release. (DPT boot floppy) References: <19970822093613.ES33724@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Samplonius on Aug 22, 1997 09:15:50 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tom Samplonius wrote: > I'm basically repeating what was said in freebsd-scsi. Which was that > the dpt driver would not be integrated as-is. This is NOT misinformation. That's right. But your messages sounded as if the driver would have been rejected wholesale, without any chance of being integrated. And that's not the case. > I've never heard Justin say yes or no on this matter. I've exchanged > private e-mail with him some time ago, at which point he was going to be > integrating the driver. However, since the dpt requires modification in > other parts of the system beyond the SCSI subsystem, I doubt that Justin > in the only one involved. A key issue seems to be software interupts. Justin is also supposed to handle this. I think he needed these software interrupts for his ongoing CAM work anyway, and wants the DPT driver make them use as well. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Fri Aug 22 13:35:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA00540 for hackers-outgoing; Fri, 22 Aug 1997 13:35:56 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA00528 for ; Fri, 22 Aug 1997 13:35:51 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id PAA03372; Fri, 22 Aug 1997 15:35:38 -0500 (EST) From: "John S. Dyson" Message-Id: <199708222035.PAA03372@dyson.iquest.net> Subject: Re: Problems with > 256MB of RAM In-Reply-To: from Gordon Henderson at "Aug 22, 97 06:33:33 pm" To: gordon@drogon.net Date: Fri, 22 Aug 1997 15:35:38 -0500 (EST) Cc: hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk I am not exactly familiar with DG's patch (probably have it filed away somewhere.) If you note the change in pmap.h, you'll see that a parameter has been increased. Just increase it again some more, perhaps by double. The pv_entry_t thing is problematical on large systems, and the tuning method that I used in the 2.2 series was just wrong. 3.0 isn't perfect right now, and am open for suggestions. (DG changed it, and made it much-much better in 3.0, but it still doesn't 'feel right' :-)). > > I'm running FreeBSD 2.2-STABLE on a machine with 384MB of RAM. (will be > upgraded to 512MB soon). I'm having problems running named with very large > zone files. The machine panics and reboots. A 'top' running on the machine > at the time shows: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 1418 root 105 0 235M 236M RUN 8:16 97.01% 97.01% named > > It's always after it's allocated 235MB. > > The panic message is always: > > panic: get_pv_entry: cannot get a pv_entry_t > > The kernel has had 3 patches supplied by David Greenman , > modifying files > > /src/sys/i386/conf/Makefile.i386 > /src/sys/i386/include/pmap.h > /src/sys/i386/include/vmparam.h > > The only other bits that have been modified in the kernel config file > (apart from deleting unused drivers, etc.) are: > > maxusers 32 > options "MAXMEM=393216" # 384MB > options "NMBCLUSTERS=2048" > > options "MAXDSIZ=402653184" # 384MB > options "DFLDSIZ=402653184" # 384MB > > BOUNCE_BUFFERS are commented out. > > Heres the catch: If I run a program that grabs all available memory in 1MB > chunks (and writes to it as it grabs it), then exits (380MB later), then I > can run named and it grows up to full size happily. (I'm running named > 8.1.1, but I see the same with 4.9.6-REL). > > Whn it's running, a top output shows: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 189 root 2 0 236M 94376K select 0:00 0.00% 0.00% named > > So it's only trying to grab an extra MB... > > Any insight would be greatly appreciated. > > Gordon > From owner-freebsd-hackers Fri Aug 22 13:44:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA00983 for hackers-outgoing; Fri, 22 Aug 1997 13:44:57 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA00977 for ; Fri, 22 Aug 1997 13:44:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id PAA03394; Fri, 22 Aug 1997 15:44:29 -0500 (EST) From: "John S. Dyson" Message-Id: <199708222044.PAA03394@dyson.iquest.net> Subject: Re: Final request for help with release. (DPT boot floppy) In-Reply-To: <199708221646.KAA09503@rocky.mt.sri.com> from Nate Williams at "Aug 22, 97 10:46:33 am" To: nate@mt.sri.com (Nate Williams) Date: Fri, 22 Aug 1997 15:44:29 -0500 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG, tom@sdf.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 X-Loop: FreeBSD.org Precedence: bulk > > > But according to recent discusions, core has rejected the DPT driver as > > > it stands... > > > > Which `core'? Your core memory? Dunno. The NetBSD core team? > > Dunno. If the term `core', as you're using it, stands as an > > abbreviation for ``The FreeBSD core team'', then i'm surprised to hear > > that you're a member of it, apparently. Otherwise, how did you learn > > this news? I believe i'm a member of this core team, and i frankly > > can't remember any decision of the kind you're quoting above. > > Whoa now. Slow down, take a deep breath, and go read the archives. > Simon *explicitly* stated that core (yeah, that's the one you belong to) > rejected the DPT driver for a number of reasons, all valid, and all > listed by Simon. They will be fixed, but until they are fixed it won't > be integrated. > We all get stressed and under pressure at times, and frankly, I don't know of one member of core today who isn't a very reasonable person in general. So, at the risk of perpetuating this thread, but as a member of -core who makes mistakes once in a while also, just bear with us all, and I think that we all can have a fun and fruitful relationship. (Geesh, I have really found out that my sense of humor does not show well at all on email, and have to restrain myself from writing things, otherwise no-one would like me. Additionally, my own language skills of my native and only language are worse than many non-amerenglish :-) speakers.) John dyson@freebsd.org From owner-freebsd-hackers Fri Aug 22 14:04:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01915 for hackers-outgoing; Fri, 22 Aug 1997 14:04:01 -0700 (PDT) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01894 for ; Fri, 22 Aug 1997 14:03:55 -0700 (PDT) Received: from idt.unit.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idi.ntnu.no (8.8.6/8.8.6) with ESMTP id XAA08591; Fri, 22 Aug 1997 23:03:43 +0200 (MET DST) Message-Id: <199708222103.XAA08591@pat.idi.ntnu.no> To: gordon@drogon.net Cc: hackers@FreeBSD.ORG Subject: Re: Problems with > 256MB of RAM In-Reply-To: Your message of "Fri, 22 Aug 1997 18:33:33 +0100 (BST)" References: 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, 22 Aug 1997 23:03:42 +0200 From: Tor Egge Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm running FreeBSD 2.2-STABLE on a machine with 384MB of RAM. (will be > upgraded to 512MB soon). I'm having problems running named with very large > zone files. The machine panics and reboots. A 'top' running on the machine > at the time shows: > > PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND > 1418 root 105 0 235M 236M RUN 8:16 97.01% 97.01% named > > It's always after it's allocated 235MB. > > The panic message is always: > > panic: get_pv_entry: cannot get a pv_entry_t There are two main reasons for this type of panic 1. temporary shortage of free physical memory (cf PR#2431). Use sysctl to increase limits of reserved free physical memory, reducing the probability for running out of free memory. sysctl -w vm.v_free_reserved=1024 sysctl -w vm.v_free_min=1500 2. permanent shortage of virtual memory allocated for pv entries. Increase the size of allocated virtual memory for pv entries by adding: options "PMAP_SHPGPERPROC=400" to the kernel config file. For most users, the default value of 200 is big enough. I use 800. > The kernel has had 3 patches supplied by David Greenman , > modifying files > > /src/sys/i386/conf/Makefile.i386 > /src/sys/i386/include/pmap.h > /src/sys/i386/include/vmparam.h > > The only other bits that have been modified in the kernel config file > (apart from deleting unused drivers, etc.) are: > > maxusers 32 > options "MAXMEM=393216" # 384MB > options "NMBCLUSTERS=2048" > > options "MAXDSIZ=402653184" # 384MB > options "DFLDSIZ=402653184" # 384MB > > BOUNCE_BUFFERS are commented out. > > Heres the catch: If I run a program that grabs all available memory in 1MB > chunks (and writes to it as it grabs it), then exits (380MB later), then I > can run named and it grows up to full size happily. (I'm running named > 8.1.1, but I see the same with 4.9.6-REL). This indicates that you probably have a temporary shortage of free physical memory. This occur during fork() of big processes. RES 236 MB -> 59000 pv entries needed -> 404 free physical pages needed. --> use a higher value, e.g. 1024 for vm.v_free_reserved - Tor Egge From owner-freebsd-hackers Fri Aug 22 16:52:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA10930 for hackers-outgoing; Fri, 22 Aug 1997 16:52:36 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA10925; Fri, 22 Aug 1997 16:52:33 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA03761; Fri, 22 Aug 1997 16:46:34 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003756; Fri Aug 22 23:46:25 1997 Message-ID: <33FE24CA.52BFA1D7@whistle.com> Date: Fri, 22 Aug 1997 16:46:18 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: wollman@freebsd.org CC: hackers@freebsd.org Subject: promblems with non IP protocols Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Garrett, I've been looking at the problem of address families for which netmasks just "don't work". (e.g. appletalk) I have basically come to the conclusion (as I mentionned to you before) that there needs to be a way for address families to specify some methods for handling their addresses. e.g. how to decide it an address is on an interface or not. There are a couple of 'style' questions though that I'd like your (and in fact any-one's) advise on. 1/ I prefer if it is a dynamic thing and not dependent on a "#ifdef NETATALK" in the kernel. Is this reasonable? (I'd like to work towards loadable protocols) 2/ If it's loadable, and a pointer to a method, then WHERE is the method stored, so that it can be found? there are several options. i) An extra entry in the domain struct (along with dom_externalize() and similar things, but there is no easy way to index this as there is no AF_XXX->protocol lookup array (I might be wrong) ii) add and entry to the ifaddr struct. there is already the protocol dependent rtrequest. adding a protocol dependent address handler (can do compares, and other operations, given the appropriate args) doesn't seem like too much of a leap. iii) An AF_XXX indexed array.. there is already such an array to look up the appropriate routing table for a protocol.. I tend to think a hybrid might be acceptable.. e.g. add a pointer from the ifaddr to the domain and add a new pointer from the domain, to the address method. for that matter, if we hung the routing tables from the domain, then the current routing table index array could be used to find the domain (and hence the routing info), when indexed by the AF_XXX entry, and get a convenient place to hang a number of these things. what are your thoughts? who else would you suggest polling? have an address for Rich Stevens? kieth Skower? Mike karels? etc? From owner-freebsd-hackers Fri Aug 22 20:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18483 for hackers-outgoing; Fri, 22 Aug 1997 20:33:26 -0700 (PDT) Received: from ibmmail.COM (ibmmail.com [204.146.168.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA18465; Fri, 22 Aug 1997 20:33:21 -0700 (PDT) Date: Fri, 22 Aug 1997 20:33:21 -0700 (PDT) From: archie@veronica.com Message-Id: <199708230333.UAA18465@hub.freebsd.org> Received: from [204.216.27.21] by ibmmail.COM (IBM VM SMTP V2R3) with TCP; Fri, 22 Aug 97 23:32:56 EDT To: undisclosed-recipients:; Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just had a super orgasm and came all over. I cleaned it up with a pillow . From owner-freebsd-hackers Fri Aug 22 20:40:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18832 for hackers-outgoing; Fri, 22 Aug 1997 20:40:35 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18827 for ; Fri, 22 Aug 1997 20:40:32 -0700 (PDT) Received: from pf1.phil.uni-sb.de (root@pf1.phil.uni-sb.de [134.96.82.11]) by freefall.freebsd.org (8.8.6/8.8.5) with ESMTP id UAA13519 for ; Fri, 22 Aug 1997 20:40:03 -0700 (PDT) Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by pf1.phil.uni-sb.de (8.8.6/8.8.6/961001chris) with ESMTP id FAA16336 for ; Sat, 23 Aug 1997 05:39:41 +0200 (MET DST) Received: from ngeout01.news.aol.com by relay4.UU.NET with SMTP (peer crosschecked as: ngeout01.news.aol.com [152.163.176.244]) id QQdduc14871; Fri, 22 Aug 1997 23:39:13 -0400 (EDT) Received: from ladder01.news.aol.com (ladder01.news-fddi.aol.com [172.16.30.168]) by ngeout01.news.aol.com (8.6.12/8.6.12) with ESMTP id XAA07223 for ; Fri, 22 Aug 1997 23:39:14 -0400 Date: Fri, 22 Aug 1997 23:39:14 -0400 To: Message-Id: <19970823033901.XAA07511@ladder01.news.aol.com> Newsgroups: saar.lists.freebsd-hackers From: jrodrig103@aol.com (JRodrig103) Organization: AOL http://www.aol.com Subject: warez cd's Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wanna buy warez cd's(cod.cash) email me back at My3dfx@juno.com and ill send u more info -later From owner-freebsd-hackers Fri Aug 22 23:04:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24687 for hackers-outgoing; Fri, 22 Aug 1997 23:04:13 -0700 (PDT) Received: from ais.ais-gwd.com (root@ais.ais-gwd.com [205.160.97.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24682 for ; Fri, 22 Aug 1997 23:04:08 -0700 (PDT) Received: from LOCALNAME (slip166-72-160-103.sc.us.ibm.net [166.72.160.103]) by ais.ais-gwd.com (8.8.5/8.7.3) with SMTP id BAA26873 for ; Sat, 23 Aug 1997 01:01:48 -0400 (EDT) Message-Id: <199708230501.BAA26873@ais.ais-gwd.com> Comments: Authenticated sender is From: "Charles A. Peters" To: hackers@freebsd.org Date: Sat, 23 Aug 1997 00:27:31 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Apache Log Viewer Utility Priority: normal X-mailer: Pegasus Mail for Windows (v2.53/R1) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know of a good log viewer for apachie log files. I am interested in seeing who is visiting my web pages. Thanks in Advance! Charles charlespeters@tecpro.com From owner-freebsd-hackers Fri Aug 22 23:14:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA25021 for hackers-outgoing; Fri, 22 Aug 1997 23:14:06 -0700 (PDT) Received: from mole (mole.slip.net [207.171.193.16]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA25011; Fri, 22 Aug 1997 23:14:02 -0700 (PDT) Received: from localhost.localhost [207.171.230.168] by mole with esmtp (Exim 1.62 #4) id 0x29SL-0000rr-00; Fri, 22 Aug 1997 23:13:53 -0700 Received: (from richw@localhost) by localhost.localhost (8.8.5/RICHW-970725c) id WAA00400; Fri, 22 Aug 1997 22:35:28 -0700 (PDT) Date: Fri, 22 Aug 1997 22:35:27 -0700 (PDT) From: Rich Wales X-Sender: richw@localhost To: smpatel@freebsd.org, hackers@freebsd.org Subject: Couldn't change IRQ on Creative SB16 PnP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried to use FreeBSD-ISA_PnP_June8.tar.gz (with a 2.2.1 kernel) to change the IRQ on my Creative SB16 PnP from 5 to 10. I eventually got the new code to compile, and it recognized my SB16 and seemed to go through the motions of configuring it, but the card simply doesn't work right (kept getting "DMA timed out - IRQ/DRQ config error?" kernel errors). I can change the IRQ for the card in DOS (it works fine at IRQ10 under DOS and Windows) -- but in order to do so, I have to select one of the card's non-default configurations first (configuration 0 only allows IRQ5). Is it possible that this might be why the FreeBSD code couldn't change the IRQ? See below for the output of "pnpinfo" on my system. BTW, I had problems getting the code to compile properly at first, apparently because of confusion between the "pnp.h" file in i386/isa and the "pnp.h" file in my build directory. I eventually got it to work by giving i386/isa/pnp.h a different name and fiddling with the #include line in pnp.c. Rich Wales richw@webcom.com http://www.webcom.com/richw/ ======================================================================== Checking for Plug-n-Play devices... Trying Read_Port at 203 Card assigned CSN #1 Board Vendor ID: CTL0028 Board Serial Number: 100a5cc1 PnP Version: 1.0 Vendor Version: 16 Device Description: Creative SB16 PnP Logical Device ID: CTL0031 (31008c0e) Device Description: Audio Start Dependent Function Good Configuration IRQ: 5 DMA: 0 1 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode DMA: 5 DMA: 16-bit only DMA: Device is not a bus master DMA: May not execute in count by byte mode DMA: May execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x220 I/O alignment for minimum: 1 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x330 I/O Range maximum address: 0x330 I/O alignment for minimum: 1 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Acceptable Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode DMA: 5 6 7 DMA: 16-bit only DMA: Device is not a bus master DMA: May not execute in count by byte mode DMA: May execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Acceptable Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode DMA: 5 6 7 DMA: 16-bit only DMA: Device is not a bus master DMA: May not execute in count by byte mode DMA: May execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode DMA: 5 6 7 DMA: 16-bit only DMA: Device is not a bus master DMA: May not execute in count by byte mode DMA: May execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x388 I/O Range maximum address: 0x388 I/O alignment for minimum: 1 I/O length: 4 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x330 I/O alignment for minimum: 48 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 5 7 10 11 DMA: 0 1 3 DMA: 8-bit only DMA: Device is not a bus master DMA: May execute in count by byte mode DMA: May not execute in count by word mode DMA: Compatibility mode Device decodes the full 16-bit ISA address I/O Range maximum address: 0x220 I/O Range maximum address: 0x280 I/O alignment for minimum: 32 I/O length: 16 End Dependent Function Logical Device ID: CTL2011 (11208c0e) Compatible Device ID: PNP0600 (0006d041) Device Description: IDE Start Dependent Function Good Configuration IRQ: 10 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x168 I/O Range maximum address: 0x168 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x36e I/O Range maximum address: 0x36e I/O alignment for minimum: 1 I/O length: 2 Start Dependent Function Acceptable Configuration IRQ: 11 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x1e8 I/O Range maximum address: 0x1e8 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x3ee I/O Range maximum address: 0x3ee I/O alignment for minimum: 1 I/O length: 2 Start Dependent Function Acceptable Configuration IRQ: 10 11 12 15 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x100 I/O Range maximum address: 0x1f8 I/O alignment for minimum: 8 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x300 I/O Range maximum address: 0x3fe I/O alignment for minimum: 2 I/O length: 2 Start Dependent Function Sub-optimal Configuration IRQ: 15 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x170 I/O Range maximum address: 0x170 I/O alignment for minimum: 1 I/O length: 8 Device decodes the full 16-bit ISA address I/O Range maximum address: 0x376 I/O Range maximum address: 0x376 I/O alignment for minimum: 1 I/O length: 1 End Dependent Function Logical Device ID: PNPffff (ffffd041) Device Description: Reserved Device decodes the full 16-bit ISA address I/O Range maximum address: 0x100 I/O Range maximum address: 0x3f8 I/O alignment for minimum: 8 I/O length: 1 Logical Device ID: CTL7001 (01708c0e) Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game Device decodes the full 16-bit ISA address I/O Range maximum address: 0x200 I/O Range maximum address: 0x200 I/O alignment for minimum: 1 I/O length: 8 End Tag ======================================================================== From owner-freebsd-hackers Sat Aug 23 00:25:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27539 for hackers-outgoing; Sat, 23 Aug 1997 00:25:44 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id AAA27534 for ; Sat, 23 Aug 1997 00:25:40 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA03549 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Sat, 23 Aug 1997 09:26:02 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id IAA00708; Sat, 23 Aug 1997 08:47:52 +0200 (MET DST) From: Wilko Bulte Message-Id: <199708230647.IAA00708@yedi.iaf.nl> Subject: Re: Apache Log Viewer Utility To: charlespeters@tecpro.com (Charles A. Peters) Date: Sat, 23 Aug 1997 08:47:52 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199708230501.BAA26873@ais.ais-gwd.com> from "Charles A. Peters" at Aug 23, 97 00:27:31 am 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.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles A. Peters wrote... > Does anyone know of a good log viewer for apachie log files. I am > interested in seeing who is visiting my web pages. Check out 'analog'. Works pretty well for us. _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hackers Sat Aug 23 00:26:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27563 for hackers-outgoing; Sat, 23 Aug 1997 00:26:42 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust161.tnt1.manassas.va.da.uu.net [153.37.113.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27558 for ; Sat, 23 Aug 1997 00:26:32 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id DAA01715; Sat, 23 Aug 1997 03:26:20 -0400 (EDT) Message-ID: <19970823032619.15770@wakky.dyn.ml.org> Date: Sat, 23 Aug 1997 03:26:19 -0400 From: Lee Cremeans To: hackers@freebsd.org, dalnet@dal.net Subject: Public apology Reply-To: hcremean@vt.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My machine's /var/mail was hosed for several hours tonight, and I didn't notice until just now. :( My apologies to anyone who sent mail to the list and got a bounce message from me...it was one part of a disk burp I neglected to fix. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD++^i WK+++r P&B++ SL+++^i GDF- B&M KK--i MD+++i P++ I++++ Di $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi Ay77 M | hcremean (at) vt.edu FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://wakky.dyn.ml.org/~lee | finger me for geek code From owner-freebsd-hackers Sat Aug 23 00:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA27942 for hackers-outgoing; Sat, 23 Aug 1997 00:35:33 -0700 (PDT) Received: from zippy.dyn.ml.org (root@haiti-93.ppp.hooked.net [206.169.228.93]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27937 for ; Sat, 23 Aug 1997 00:35:28 -0700 (PDT) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.7/8.8.7) with SMTP id KAA19861 for ; Fri, 22 Aug 1997 10:35:42 -0700 (PDT) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 22 Aug 1997 10:35:25 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: freebsd-hackers@FreeBSD.ORG Subject: Re: Get more visitors! In-Reply-To: <199708221639.LAA02587@argus.tfs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 22 Aug 1997, Jim Bryant wrote: > In reply: > > >I'm getting tired of spam... > > As am I. > > > > >I DON'T WANT ANY SPAM!@# > > Unfortunately, I place your posting in the same category. > > I would have prefered to have received neither. You simply > > compounded the problem. > > actually congress compounded the problem by not legislating against > junk email when the bill was before them this year, but then what do > you expect out of conservatives... So has hub.freebsd.org which has appeared in a few spams that I've gotten this month :/. > it's sitting there acting like sheep that compounds the problem... > the "oh i'll just ignore it until it goes away" attitude just doesn't > work. it didn't work with hitler, it didn't work with our > conservative congress either. > > the only way to remove junk email from the net, until legislation > making such illegal is in place, it to simply fight fire with fire, > even if it logjams the entire freaking internet. > > don't write to me, write to your freaking congressman. Yeah, like they're gonna get off their collective asses and do something. - alex From owner-freebsd-hackers Sat Aug 23 00:58:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28611 for hackers-outgoing; Sat, 23 Aug 1997 00:58:48 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28606 for ; Sat, 23 Aug 1997 00:58:45 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id BAA24701; Sat, 23 Aug 1997 01:21:36 -0700 Date: Sat, 23 Aug 1997 01:21:34 -0700 (PDT) From: Alex Belits To: "Charles A. Peters" cc: hackers@FreeBSD.ORG Subject: Re: Apache Log Viewer Utility In-Reply-To: <199708230501.BAA26873@ais.ais-gwd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, Charles A. Peters wrote: > Does anyone know of a good log viewer for apachie log files. I am > interested in seeing who is visiting my web pages. grep -- Alex From owner-freebsd-hackers Sat Aug 23 02:08:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA00683 for hackers-outgoing; Sat, 23 Aug 1997 02:08:18 -0700 (PDT) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA00678 for ; Sat, 23 Aug 1997 02:08:12 -0700 (PDT) Received: from postbox.india.hp.com (postbox.india.hp.com [15.10.45.1]) by palrel1.hp.com (8.8.6/8.8.5) with ESMTP id CAA05685 for ; Sat, 23 Aug 1997 02:08:05 -0700 (PDT) Message-Id: <199708230908.CAA05685@palrel1.hp.com> Received: from localhost by postbox.india.hp.com with ESMTP (1.39.111.2/16.2) id AA120867122; Sat, 23 Aug 1997 14:35:22 +0530 To: freebsd-hackers@freebsd.org Subject: Checking the integrity of system files Date: Sat, 23 Aug 1997 14:35:22 +0530 From: A Joseph Koshy Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, -current being what it supposed to be, I find that as time passes my system as getting filled up with the carcasses of old and abandoned programs. At the minimum this can be a space wasting nuisance, and may also leave way for security breaching Is there any way, barring parsing the output of `make install' to or `make release' to determine the list of `current' files on a system? I'm looking at a registry of files maintaining sizes, permissions, checksums of files, against which I can check a system. If such a registry is to be added, what is a good place to add it? (a) add the functionality to `install' (but this won't handle ports stuff) (b) a separate program callable at install or release time or port addition time. Koshy From owner-freebsd-hackers Sat Aug 23 03:05:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA01939 for hackers-outgoing; Sat, 23 Aug 1997 03:05:00 -0700 (PDT) Received: from gvr.gvr.org (root@gvr.win.tue.nl [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA01931 for ; Sat, 23 Aug 1997 03:04:53 -0700 (PDT) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id MAA05509 for FreeBSD-hackers@freebsd.org; Sat, 23 Aug 1997 12:04:50 +0200 (MET DST) From: Guido van Rooij Message-Id: <199708231004.MAA05509@gvr.gvr.org> Subject: broadcast question To: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) Date: Sat, 23 Aug 1997 12:04:50 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I discovered a difference between the 2.1.7 and 2.2 tcp/ip stack that I cannot explain. If I have a host in a subnetted C-net, say 192.1.1.0/28 and I send an icmp echo request to the broadcast address of the C-net (so NOT to 192.1.1.15) the 2.1.7 stack does send an echo reply but the 2.2 stack does not. So an all-subnets directed broadcast seems to be ignored on 2.2 stacks...I think this broken, yet fail to see where it was broken. -Guido From owner-freebsd-hackers Sat Aug 23 03:49:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA05940 for hackers-outgoing; Sat, 23 Aug 1997 03:49:34 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA05922 for ; Sat, 23 Aug 1997 03:49:26 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19609 (5.67b/IDA-1.5 for ); Sat, 23 Aug 1997 12:49:08 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id KAA00590; Sat, 23 Aug 1997 10:18:16 +0200 (CEST) X-Face: " Date: Sat, 23 Aug 1997 10:18:16 +0200 From: Stefan Esser To: Terry Lambert Cc: Satoshi Asami , Shimon@i-connect.net, tom@sdf.com, hackers@FreeBSD.ORG, mrcpu@cdsnet.net, nate@mt.sri.com Subject: Re: Final request for help with release. (DPT boot floppy) References: <199708221157.EAA00987@silvia.HIP.Berkeley.EDU> <199708221807.LAA26407@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199708221807.LAA26407@phaeton.artisoft.com>; from Terry Lambert on Fri, Aug 22, 1997 at 11:07:13AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 22, Terry Lambert wrote: > > I have also seen mysterious lockups (for a few seconds) with Solaris > > x86 when I bombarded more than two twin-channel controllers (Adaptec > > 3940W/UW) with lots of requests. FreeBSD had no problems whatsoever. > > This is probably a PCI issue. Most Intel PCI bridges do not > correctly arbitrate between more than two bus mastering PCI > devices simultaneously. > > Stefan posted about this a while back. Ummm, I don't remember doing so, actually ... I sent out a reminder about the problem early chip-sets had with multiple PCI bus-masters. The Triton-I seems to be OK, and the later ones too, but everything before may fail under high load. There are also some design flaws in PCI 2.0, which have been resolved in 2.1, and which can lead to a bus lockup (or delivery of wrong data) in systems with bus-masters on the PCI bus and PCI to PCI bridges. Don't use early PCI to PCI bridges in heavily loaded systems, or you may suffer from crashes or system hangs. > I think there's a newer chipset that actually supports any number > of devices (up to the number of slots, anyway), but I don't remember > the name of the thing off the top of my head. The PCI bus arbiter limits the number of bus- master PCI devices on a single bus. Since an arbiter comes with each host to PCI bridge and PCI to PCI bridge, most motherboard and card designs use those, and thus there is a chip-set specific (or PPB specific) limit on the number of bus-master slots (often 4). Since there are typically 4 or more slots, and the PCI to ISA bridge counts as a PCI bus-master, you can not expect that 4 bus-master cards will work on the motherboard ... (Early PCI motherboards often had dedicated bus- master and slave PCI slots, but this is no longer the case. The bus-master slots are dynamically assigned, but still limited in number.) But one is a VGA card, usually, and thus there can be only 3 others in a 4 slot system, and you will never be hurt by the limit :) Regards, STefan From owner-freebsd-hackers Sat Aug 23 03:53:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06802 for hackers-outgoing; Sat, 23 Aug 1997 03:53:07 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA06760 for ; Sat, 23 Aug 1997 03:52:57 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19592 (5.67b/IDA-1.5 for ); Sat, 23 Aug 1997 12:48:51 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id LAA00769; Sat, 23 Aug 1997 11:21:18 +0200 (CEST) X-Face: " Date: Sat, 23 Aug 1997 11:21:18 +0200 From: Stefan Esser To: Simon Shapiro Cc: Terry Lambert , tom@sdf.com, hackers@FreeBSD.ORG, mrcpu@cdsnet.net, nate@mt.sri.com, Satoshi Asami Subject: Re: Final request for help with release. (DPT boot floppy) References: <199708221807.LAA26407@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Simon Shapiro on Fri, Aug 22, 1997 at 11:47:46AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 22, Simon Shapiro wrote: > You are right. We had here a terrible time with PCI bridges. Some will > deliver interrupts before completion of DMA, some will lose interrupts, > some will corrupt DMA transfers. Real party. Not only Intel but (for > sure) the older DEC bridge (somethign with 50 in the name, vs. 51). Well, the complications caused by PCI bridges had not really been understood in all detail, when the first bridges appeared. You can expect any PPB bridge that does not conform to PCI 2.1 to be sensitive to certain situations and to cause a lockup or data corruption, then. (Have a look at pages 99, 243 and 448 of PCI System Architecture published by Addison Wesley for three deadlock scenarios. Don't remember where the data corruption problem is explained, but it is caused by the fast, that a PCI device may issue a "retry", if it can't deliver the requested data immediately, and if there is another request (from a different bus-master), that second request may receive the data meant to be sent to the first one, in very a certain situation.) Revision 2.1 of the PCI specification contains that information, too ... Back to your points about IRQs being delivered before the end of a DMA: PCI had certain design objectives and met them. Those had to do with low power consumption of bus drivers, required for single chip solutions, for example. But the price paid is the limit of only a few slots per bus segment. The solution is the tree structure of buses connected by PCI to PCI bridges. But PCI to PCI bridges cause latencies, and you will be able to measure them easily when doing single memory accesses in a loop (eg. read the same address over and over). In order to hide those latencies, write buffers have been put in all PCI bridges. What you see, if an IRQ is delivered before the end of the DMA, is that the transfer has really ended as seen by the bus-master device: It has sent out all data. But that data may still be in some FIFO on its way to system memory, and there is no coherency check between those FIFOs and memory or the CPU cache. The PCI 2.1 check requires a device driver to enforce coherency be reading from any address mapped into the device that caused the request. This works, because the PPB(s) between the CPU and the device are require to deliver data in order. But it only works, of the CPU and system memory controller are tightly coupled. Else there might be a different data path between the device and system memory, and ordering rules applied to both of them seperately. There is another option that is open to device designers: The device may read from the last memory location written, before it issues an interrupt. The read will not complete, before the write-buffers of all intervening PPBs have been flushed. But a PCI device interrupt handler has to take shared interrupts into account, and will read some interrupt status register of a PCI device as its first action, anyway (and will back out, if the interrupt was caused by some other device). And that read will effectively enforce DMA data to have made it into system RAM ... The DEC 21050 PCI to PCI bridge was one of the first PPBs in wide use, and it was the device that made the shortcomings of the PCI 2.0 spec obvious. Later DEC parts (and recent PPBs from other manufacturers) are built according to revision 2.1 of the PCI specification, and will not suffer from the defects of the early designs. There is no (software) way to work around the design flaws of PCI 2.0 with regard to PCI to PCI bridges. They won't hurt the typical work station user, but will become obvious on servers with multiple bus-master controllers on seperate buses ... Regards, STefan From owner-freebsd-hackers Sat Aug 23 03:54:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA06924 for hackers-outgoing; Sat, 23 Aug 1997 03:54:11 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA06909 for ; Sat, 23 Aug 1997 03:54:06 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id EAA25455; Sat, 23 Aug 1997 04:16:57 -0700 Date: Sat, 23 Aug 1997 04:16:56 -0700 (PDT) From: Alex Belits To: dk+@ua.net cc: hackers@freebsd.org Subject: Re: My pipe is getting muddled?! In-Reply-To: <199708230842.BAA08761@dog.farm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Okay, I posted a question a while back about whether or not it would be okay to > use SYSV message queues in a project. I got a mixed reaction on that, so I'm > looking at FIFO's and/or sockets as well. > > I have one big problem, though: If I have a server sitting on a FIFO, and it > needs to communicate in both directions with multiple clients (imaging something > like the X server sitting on /tmp/.X11-pipe/X0), how do I keep everyone's > messages from getting all mixed up? On a socket, one would sit in a loop and > accept() connections on the server end, and everything just works. > > The thing is, I've been trying to figure out (using truss), how Solaris manages > to do a very similar thing in the X server with FIFO's, and I can't for the life > of me figure out what crazy STREAMS nonsense they're using. The nearest I can > tell, there is some sort of multiplexor in there, because when a new client > connects, the server does an ioctl(fd, I_RECVFD, &buf), and pulls a new file > descriptor out of the stream, and communicates with the client on that. Oddly > enough, the client isn't doing an I_SENDFD anywhere, so I think this is > happening automatically. Can anyone explain what's going on? I believe > /tmp/.X11-pipe/X0 is a new interface, because Solaris also has a > /tmp/.X11-unix/X0, which I believe is how everyone else communicates? I don't have solaris box here (and never seen OpenWindows source, and have enough work to do to have no intent of spending hours looking at the truss output), but X11R6.3 source has I_SENDFD in STREAMS-based version of transport (file xc/lib/xtrans/Xtranslcl.c, my copy is visible as http://phobos.illtel.denver.co.us/pub/X11R6.3/xc/lib/xtrans/Xtranslcl.c). I can imagine that Solaris in its weirdness managed to use STREAMS-based operations on the server and BSD fd-passing emulation on the client, but that is just a wild guess. If you want to check that, keep in mind that Solaris' idea of "BSD" is derived from the need of SunOS 4.x.x compatibility, so it's 4.3, not 4.4. AF_UNIX sockets handling is in xc/lib/xtrans/Xtranssock.c (http://phobos.illtel.denver.co.us/pub/X11R6.3/xc/lib/xtrans/Xtranssock.c), and it looks like regular socket() / bind() / listen() / accept() for both TCP and AF_UNIX. > Any light you can shed on this will be appreciated. In the meantime, I'm going > to start exploring UNIX-domain sockets, because they have the behavior I want. They should work "normal" way, but just 3 days ago I have submitted a PR for a nasty bug that is triggered in some situations while doing fd-passing through AF_UNIX sockets (PR kern/4345, http://www.freebsd.org/cgi/query-pr.cgi?pr=4345), so I don't recommend to use fd-passing through AF_UNIX sockets on versions that can be crashed by the test that I have included in PR. Regular socket() / bind() / listen() / accept() model doesn't appear to have any problems. > But I vaguely remember hearing that the Solaris method is faster (well, at least > for Solaris :). In Solaris a lot of BSD-compatible things are implemented at the top of STREAMS, and therefore are even slower than STREAMS themselves. I have heard about STREAMS implementations for FreeBSD and Linux. IMHO they aren't in "regular" kernels of either because they don't fit into BSD-based system and encourage programmer to use the model, inefficient enough even on real SVR4, and more so in the port to BSD. SVR4 developers claim that STREAMS provide a lot of useful things for them, although BSD already had most of them implemented BSD-native way at the time of STREAMS "invention", and only the base functionality of STREAMS (pushable modules) doesn't have anything matching in BSD. Probably it's a good thing because of the overhead introduced by it and usefullness only in the situation when everything can use it (and therefore has this overhead). BTW, threads support is another thing where Solaris is too proud of its performance while other systems run circles around it with normal processes using better-designed context switches. So optimization of user-space program's interaction with the kernel that will work well on Solaris most likely can't be applied to any BSD-based system, especially if STREAMS-specific vs. BSD-specific operations, threads vs. processes, etc are involved. -- Alex From owner-freebsd-hackers Sat Aug 23 05:51:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11095 for hackers-outgoing; Sat, 23 Aug 1997 05:51:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id FAA11078 for ; Sat, 23 Aug 1997 05:51:32 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id OAA17022 for FreeBSD-hackers@FreeBSD.ORG; Sat, 23 Aug 1997 14:51:31 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA11676; Sat, 23 Aug 1997 14:38:13 +0200 (MET DST) Message-ID: <19970823143813.EY59755@uriah.heep.sax.de> Date: Sat, 23 Aug 1997 14:38:13 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: FreeBSD-hackers@FreeBSD.ORG (FreeBSD-hackers) Subject: Re: broadcast question References: <199708231004.MAA05509@gvr.gvr.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708231004.MAA05509@gvr.gvr.org>; from Guido van Rooij on Aug 23, 1997 12:04:50 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Guido van Rooij wrote: > If I have a host in a subnetted C-net, say 192.1.1.0/28 > and I send an icmp echo request to the broadcast address of the C-net > (so NOT to 192.1.1.15) the 2.1.7 stack does send an echo reply > but the 2.2 stack does not. > So an all-subnets directed broadcast seems to be ignored on 2.2 > stacks...I think this broken, yet fail to see where it was broken. I think 2.1.x was broken. What is an ``all-subnets'' broadcast in a CIDR world? Forget about class A/B/C, forget the term `subnet', they don't exist anymore. (*) The address 192.1.1.255 is not in any way a valid broadcast address for net 192.1.1.0/28, it's a valid broadcast address for 192.1.1.128/25, or maybe for 192.1.1.240/28 (which are entirely different networks from 192.1.1.0/28). (*) The only meaning of the historic classes A/B/C that does still exist is that they determine the default netmask if nothing else has been specified in ifconfig(8), or route(8), etc. This can sometimes be convenient to type. 255.255.255.255 should work, i believe. I'm surprised 2.1.x was still broken in this respect. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Aug 23 06:41:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA13179 for hackers-outgoing; Sat, 23 Aug 1997 06:41:52 -0700 (PDT) Received: from unicorn.uk1.vbc.net (unicorn.uk1.vbc.net [194.207.2.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA13174 for ; Sat, 23 Aug 1997 06:41:47 -0700 (PDT) Received: from localhost (gordon@localhost) by unicorn.uk1.vbc.net (8.8.5/8.8.5) with SMTP id OAA11510 for ; Sat, 23 Aug 1997 14:46:46 +0100 Date: Sat, 23 Aug 1997 14:46:46 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn To: hackers@freeBSD.org Subject: Re: Problems with > 256MB of RAM [what worked & what didn't] Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk Tor Egge suggested: > There are two main reasons for this type of panic > > 1. temporary shortage of free physical memory (cf PR#2431). > > Use sysctl to increase limits of reserved free physical > memory, reducing the probability for running out of free memory. > > sysctl -w vm.v_free_reserved=1024 > sysctl -w vm.v_free_min=1500 This worked. Tor also suggested: > 2. permanent shortage of virtual memory allocated for pv entries. > > Increase the size of allocated virtual memory for pv entries > by adding: > > options "PMAP_SHPGPERPROC=400" This didn't work. Upping it to 800 didn't work either. Same panic at the same place. John S. Dyson suggested changing NKPDE in pmap.h (DG's patch bumped this from 63 to 127). I upped it to 255. Didn't work. Machine didn't even boot! Stopped at: Boot: dosdev= 80, biosdrive = 0, unit = 0, maj = 0 Booting 0:wd(0,a)/kernel @ 0x100000 text=0x8f000 data=0xc000 bss=0xd484 symbols=[+0xb7c+0x4+0xc378+0x4+0x10169] total=0x1c54e9 entry point=0x100000 Needed a hardware reset. So, I've stuck Tor's sysctls in my /etc/rc.local for now and all seems well. If anyone wants to add to this, feel free and I'll check it if I have time. Gordon From owner-freebsd-hackers Sat Aug 23 09:11:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA25744 for hackers-outgoing; Sat, 23 Aug 1997 09:11:30 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust161.tnt1.manassas.va.da.uu.net [153.37.113.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA25738 for ; Sat, 23 Aug 1997 09:11:24 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id MAA02314; Sat, 23 Aug 1997 12:10:41 -0400 (EDT) Message-ID: <19970823121040.49750@wakky.dyn.ml.org> Date: Sat, 23 Aug 1997 12:10:40 -0400 From: Lee Cremeans To: Joerg Wunsch Cc: hackers@freebsd.org Subject: Re: Public apology Reply-To: hcremean@vt.edu References: <19970823032619.15770@wakky.dyn.ml.org> <19970823142842.HQ20285@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e In-Reply-To: <19970823142842.HQ20285@uriah.heep.sax.de>; from J Wunsch on Sat, Aug 23, 1997 at 02:28:42PM +0200 X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Aug 23, 1997 at 02:28:42PM +0200, J Wunsch wrote: > You should always this kind of notification to postmaster@freebsd.org, > our restless Jonathan. He's the one who gets the bounces (not the > poor senders to the list), and his only defense if the number of > bounces to a particular site is getting too high is to unsubscribe the I'll remember that, but my maillog shows the bounces going to people on the list....that's why I posted this. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD++^i WK+++r P&B++ SL+++^i GDF- B&M KK--i MD+++i P++ I++++ Di $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi Ay77 M | hcremean (at) vt.edu FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://wakky.dyn.ml.org/~lee | finger me for geek code From owner-freebsd-hackers Sat Aug 23 09:49:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01359 for hackers-outgoing; Sat, 23 Aug 1997 09:49:52 -0700 (PDT) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01352 for ; Sat, 23 Aug 1997 09:49:49 -0700 (PDT) Received: from idt.unit.no (tegge@ikke.idi.ntnu.no [129.241.111.65]) by pat.idi.ntnu.no (8.8.6/8.8.6) with ESMTP id SAA06260; Sat, 23 Aug 1997 18:49:39 +0200 (MET DST) Message-Id: <199708231649.SAA06260@pat.idi.ntnu.no> To: gordon@drogon.net Cc: hackers@FreeBSD.ORG Subject: Re: Problems with > 256MB of RAM [what worked & what didn't] In-Reply-To: Your message of "Sat, 23 Aug 1997 14:46:46 +0100 (BST)" References: 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: Sat, 23 Aug 1997 18:49:37 +0200 From: Tor Egge Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Tor Egge suggested: > > There are two main reasons for this type of panic > > > > 1. temporary shortage of free physical memory (cf PR#2431). > > > > Use sysctl to increase limits of reserved free physical > > memory, reducing the probability for running out of free memory. > > > > sysctl -w vm.v_free_reserved=1024 > > sysctl -w vm.v_free_min=1500 > > This worked. > > Tor also suggested: > > 2. permanent shortage of virtual memory allocated for pv entries. > > > > Increase the size of allocated virtual memory for pv entries > > by adding: > > > > options "PMAP_SHPGPERPROC=400" > > This didn't work. Upping it to 800 didn't work either. Same panic at the > same place. Both problems are capable of causing the panic by itself. Applying a workaround for problem #2 and not for problem #1 when problem #1 occurs will prevent the panic. problem #1 normally occurs during fork of a process with a large resident set (several hundred megabytes). problem #2 normally occurs when you have many processes with the same data mapped into memory (several hundred megabytes), and all the processes have accessed most of that data. If you have *very* many processes sharing the same data, the workaround for problem #2 might cause problem #3, reported in PR#1880 (panic: kmem_suballoc: bad status return of 3). > John S. Dyson suggested changing NKPDE in pmap.h > (DG's patch bumped this from 63 to 127). I upped it to 255. Didn't work. > Machine didn't even boot! Stopped at: > > Boot: > dosdev= 80, biosdrive = 0, unit = 0, maj = 0 > Booting 0:wd(0,a)/kernel @ 0x100000 > text=0x8f000 data=0xc000 bss=0xd484 symbols=[+0xb7c+0x4+0xc378+0x4+0x10169] > total=0x1c54e9 entry point=0x100000 > > Needed a hardware reset. But that is trying to apply a workaround for problem #3, not problem #2 or problem #1, which are the two problems related to `panic: get_pv_entry: cannot get a pv_entry_t'. If you bump NKPDE to 255, you need to change LOAD_ADDRESS to C0100000 in sys/i386/conf/Makefile.i386. Did you do that ? - Tor Egge From owner-freebsd-hackers Sat Aug 23 09:53:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01701 for hackers-outgoing; Sat, 23 Aug 1997 09:53:03 -0700 (PDT) Received: from brickbat8.mindspring.com (brickbat8.mindspring.com [207.69.200.11]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01696 for ; Sat, 23 Aug 1997 09:53:01 -0700 (PDT) Received: from bogus.mindspring.com (user-37kboik.dialup.mindspring.com [207.69.226.84]) by brickbat8.mindspring.com (8.8.5/8.8.5) with SMTP id MAA24261; Sat, 23 Aug 1997 12:52:57 -0400 (EDT) Message-Id: <1.5.4.32.19970823165223.008c4128@mail.mindspring.com> X-Sender: kpneal@mail.mindspring.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 23 Aug 1997 12:52:23 -0400 To: Alex From: "Kevin P. Neal" Subject: Re: Get more visitors! Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:35 AM 8/22/97 -0700, Alex wrote: > > >On Fri, 22 Aug 1997, Jim Bryant wrote: > >> In reply: >> > >I'm getting tired of spam... >> > As am I. >> > >> actually congress compounded the problem by not legislating against >> junk email when the bill was before them this year, but then what do >> you expect out of conservatives... > >So has hub.freebsd.org which has appeared in a few spams that I've gotten >this month :/. > >> the only way to remove junk email from the net, until legislation >> making such illegal is in place, it to simply fight fire with fire, >> even if it logjams the entire freaking internet. >> >> don't write to me, write to your freaking congressman. > >Yeah, like they're gonna get off their collective asses and do something. This conversation probably doesn't belong on the FreeBSD lists. But anyway, I personally think that giving the Congresscritters even a pinkie-hold on lawmaking for the Internet is a bad idea. We don't want ignorant Congress making laws about the Internet, which means we don't want them to start. The laws concerning junk faxes don't really work so what makes you think that similar laws applied to junk email will work? The only solution through the government is to *sue*, which is happening with some success. A solution that doesn't require the government would be to use routers or something to block out traffic from "offending" domains or networks. Or perhaps don't accept email or news from offending domains or networks. It happened with Uunet, it can happen with any other ISP. We risk fragmenting the Internet, but if we got Sprint, MCI, AT&T, etc in on it then we could have some success. That's all I'm going to say about this on this list. I suggest we take this to one of the net.abuse newsgroups. Actually, it wouldn't surprise me if this was in a FAQ on one of those newsgroups. -- XCOMM Kevin P. Neal, Junior, Comp. Sci. - House of Retrocomputing XCOMM mailto:kpneal@pobox.com - http://www.pobox.com/~kpn/ XCOMM kpneal@eos.ncsu.edu Spoken by Keir Finlow-Bates: XCOMM "Good grief, I've just noticed I've typed in a rant. Sorry chaps!" From owner-freebsd-hackers Sat Aug 23 09:53:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01798 for hackers-outgoing; Sat, 23 Aug 1997 09:53:47 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01779 for ; Sat, 23 Aug 1997 09:53:42 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id SAA01215 for hackers@freebsd.org; Sat, 23 Aug 1997 18:53:41 +0200 (MESZ) From: Robert Eckardt Message-Id: <199708231653.SAA01215@ghost.mep.ruhr-uni-bochum.de> Subject: amd + linux = permission denied To: hackers@freebsd.org Date: Sat, 23 Aug 1997 18:53:41 +0200 (MESZ) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Since I upgraded most of our machine to 2.2.2, I have some problems. Each question will go in a seperate mail. I want to mount a directory with amd on a 2.2.2 box from a linux box. FreeBSD pion 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Wed Aug 20 19:10:25 CEST 1997 root@pion:/usr/src/sys/compile/PION_1 i386 Linux linux19 2.0.30 #4 Fri Aug 8 17:17:53 MEST 1997 i586 unknown (Linux is from the S.u.S.e distrib.) I configured a directory /mounted_homes as the amd managed directory with maps coming from NIS. The problem is that I get `Permission denied' when accessing the auto-mounted directoy. However, it works fine when I mount by hand. Afterwards, I can also access the cached data via the auto-mounted directory. In subdirectories I get again `Permission denied'. Has anyone an idea what might be the cause and where to fix it ? With my thanks, Robert 18:38 pion: / 1#% ypmatch linux19 amd.mounted_homes host==l19-tp2;type:=link;fs:=/usr/local/applix host!=l19-tp2;rhost:=l19-tp2;fs:= ${autodir}/${rhost}/applix;rfs:=/usr/local/applix;sublink:=${autodir}/${rhost}/a pplix;opts:=ro,intr,soft,noconn 18:38 pion: / 1#% ll /linux19/. ls: /linux19/.: Permission denied 18:38 pion: / 0#% mount -o ro,intr,soft,noconn l19-tp2:/usr/local/applix /mnt 18:39 pion: / 0#% ll /mnt total 68 -rwxr-xr-x 1 daemon daemon 58781 7 Apr 18:21 applix drwxr-xr-x 41 daemon daemon 1024 7 Apr 17:27 axart drwxr-xr-x 10 daemon daemon 2048 24 Jul 10:55 axdata drwxr-xr-x 2 daemon daemon 1024 24 Jul 10:55 axfilter drwxr-xr-x 4 daemon daemon 1024 7 Apr 18:45 axfonts drwxr-xr-x 2 daemon daemon 2048 24 Jul 10:55 axlang drwxr-xr-x 2 daemon daemon 1024 24 Jul 10:55 axlocal drwxr-xr-x 9 daemon daemon 1024 7 Apr 18:46 template 18:39 pion: / 0#% umount /mnt 18:39 pion: / 0#% ll /linux19/. total 68 -rwxr-xr-x 1 daemon daemon 58781 7 Apr 18:21 applix drwxr-xr-x 41 daemon daemon 1024 7 Apr 17:27 axart drwxr-xr-x 10 daemon daemon 2048 24 Jul 10:55 axdata drwxr-xr-x 2 daemon daemon 1024 24 Jul 10:55 axfilter drwxr-xr-x 4 daemon daemon 1024 7 Apr 18:45 axfonts drwxr-xr-x 2 daemon daemon 2048 24 Jul 10:55 axlang drwxr-xr-x 2 daemon daemon 1024 24 Jul 10:55 axlocal drwxr-xr-x 9 daemon daemon 1024 7 Apr 18:46 template 18:39 pion: / 0#% ll /linux19/axart ls: alphabet: Permission denied ls: anml_out: Permission denied ls: arrows: Permission denied [....] -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Aug 23 09:54:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA01903 for hackers-outgoing; Sat, 23 Aug 1997 09:54:38 -0700 (PDT) Received: from eddie.mit.edu (EDDIE.MIT.EDU [18.62.0.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA01891 for ; Sat, 23 Aug 1997 09:54:34 -0700 (PDT) Received: from ccomp.inode.com by eddie.mit.edu id aa16206; 23 Aug 97 12:44 EDT Received: (from gdk@localhost) by ccomp.inode.com (8.6.9/1.3) for id MAA00831; Sat, 23 Aug 1997 12:43:01 -0400 From: Gary Kendall Message-Id: <199708231643.MAA00831@ccomp.inode.com> Subject: Sizing mem > 64MB at boot-time To: freebsd-hackers@freebsd.ORG Date: Sat, 23 Aug 1997 12:43:00 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, all. I've been trying to hack enough "smarts" into the memsize() function from sys/i386/boot/biosboot/bios.S to get the actual number of installed 1KB pages of memory from the BIOS, so it can be passed on the the kernel in hopes of eliminating (in most cases) the need for the MAXMEM option in the kernel config file (an ugly hack, IMHO). However, I'm having more than a little difficulty in getting the code right, since this is my first time out with assembler on an Intel chip. I think what I have is close, but I don't seem to be getting pointers to local bss storage in the right segment/register format. The code compiles and runs, but, in the case of xm_e820 (Int 15H, AX=E820), always returns a value of 4096 1KB pages (eg, 4MB). I've been testing it on a floppy, and I suggest anyone who plays with it do the same. ;-) The xm_e801 code seems to work, but I had to test it on a friend's box with an AMI BIOS. The xm_e820 code is what's needed for my BIOS (MR BIOS.. also works on newer Award BIOS's), and that's where the problem lives. I've included a shar file containing just the (revised) memsize() function, and the specs for BIOS calls Int 15H, AX=E820 and AX=E801. I got the specs from the www.ctyme.com web site as part of Ralf's interrupt list. (A very nicely organized serachable database of interrupts!) Any help anyone can give me in sorting out segments and/or operand sizes in real-mode would be greatly appreciated. Regards, Gary Kendall %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % The difficult is done immediately, the impossible takes a little longer. % %----------------------------------------------------------------------------% % gdk@ccomp.inode.com or gkendall@eddie.mit.edu % %----------------------------------------------------------------------------% % Creative Computing * 96 Forest Street * Danvers, MA 01923 * 508-777-3784 % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% --------------------------------- cut here ----------------------------------- # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # /tmp/memsize.S # /tmp/xm_e820 # /tmp/xm_e801 # echo x - /tmp/memsize.S sed 's/^X//' >/tmp/memsize.S << 'END-of-/tmp/memsize.S' X/* X * X * memsize(i) : return the memory size in KB. i == 0 for conventional memory, X * i == 1 for extended memory X * BIOS call "INT 12H" to get conventional memory size X * BIOS call "INT 15H, AH=88H" to get extended memory size X * Both have the return value in AX. X * X */ X XENTRY(memsize) X pushl %ebp X movl %esp, %ebp X pushl %ebx X pushl %ecx X pushl %edx X pushl %edi X X movl 8(%ebp), %ebx X X call EXT(prot_to_real) /* enter real mode */ X X cmpb $0x1, %bl X data32 X je xext X X sti X int $0x12 X cli X data32 X jmp xdone X Xxext: Xxm_e820: X movl $0x100000, %ebx /* start at 1MB */ X1: cmpl $0, %ebx X data32 X je xdone X xorl %eax, %eax X movw $0xE820, %ax X movl $xm_e820_smap, %edx X movl $xm_e820_tbsz, %ecx X movl %es:xm_e820_tab, %edi X sti X int $0x15 X cli X data32 X jc xm_e801 X X cmpl $xm_e820_avail, %es:16(%edi) X data32 X jne 1b X movl %es:8(%edi), %eax X shrl $10, %eax X movl xm_e820_totk, %edx X addl (%edx), %eax X movl %eax, (%edx) X data32 X jmp 1b X Xxm_e801: X xorl %eax, %eax X movw $0xE801, %ax X sti X int $0x15 X cli X data32 X jc xm_88 X X movzwl %cx, %ecx X movzwl %dx, %edx X shll $6, %edx X addl %edx, %ecx X movl %ecx, %eax X data32 X jmp xdone X Xxm_88: X xorl %eax, %eax X movb $0x88, %ah X sti X int $0x15 X cli X movzwl %ax, %eax X Xxdone: X movl %eax, %ebx X X data32 X call EXT(real_to_prot) X X popl %edi X popl %edx X popl %ecx X movl %ebx, %eax X popl %ebx X popl %ebp X ret X Xxm_e820_tbsz= 20 X .lcomm xm_e820_tab, xm_e820_tbsz X .align 2 X .lcomm xm_e820_totk, 4 X Xxm_e820_smap= 0x534D4150 /* "SMAP" */ X X/* e820 memory types */ Xxm_e820_avail= 0x01 Xxm_e820_resvd= 0x02 Xxm_e820_acpi= 0x03 Xxm_e820_nvs= 0x04 END-of-/tmp/memsize.S echo x - /tmp/xm_e820 sed 's/^X//' >/tmp/xm_e820 << 'END-of-/tmp/xm_e820' XFrom gdk Wed Aug 20 10:34:49 1997 XReceived: (from gdk@localhost) by ccomp.inode.com (8.6.9/1.3) id KAA01490; Wed, 20 Aug 1997 10:34:45 -0400 XDate: Wed, 20 Aug 1997 10:34:45 -0400 XFrom: Gary Kendall XMessage-Id: <199708201434.KAA01490@ccomp.inode.com> XX-URL: http://www.ctyme.com/intr/RB-1666.HTM XTo: Gary Kendall XSubject: Int 15/AX=E820h XStatus: O X X X Int 15/AX=E820h X X ---------------------- X X Newer BIOSes - GET SYSTEM MEMORY MAP X XAX = E820h XEAX = 0000E820h XEDX = 534D4150h ('SMAP') XEBX = continuation value or 00000000h to start at beginning of map XECX = size of buffer for result, in bytes (should be >= 20 bytes) XES:DI -> buffer for result (see #0498) X XReturn: XCF clear if successful XEAX = 534D4150h ('SMAP') XES:DI buffer filled XEBX = next offset from which to copy or 00000000h if all done XECX = actual length returned in bytes XCF set on error XAH = error code (86h) (see #0415 at INT 15/AH=80h) X X Notes: Originally introduced with the Phoenix BIOS v4.0, this function X is now supported by most newer BIOSes, since various versions of X Windows call it to find out about the system memory. A maximum of 20 X bytes will be transferred at one time, even if ECX is higher; some X BIOSes (e.g. Award Modular BIOS v4.50PG) ignore the value of ECX on X entry, and always copy 20 bytes. Some BIOSes expect the high word of X EAX to be clear on entry, i.e. EAX=0000E820h. If this function is not X supported, an application should fall back to AX=E802h, AX=E801h, and X then AH=88h. The BIOS is permitted to return a nonzero continuation X value in EBX and indicate that the end of the list has already been X reached by returning with CF set on the next iteration. This function X will return base memory and ISA/PCI memory contiguous with base memory X as normal memory ranges; it will indicate chipset-defined address X holes which are not in use and motherboard memory-mapped devices, and X all occurrences of the system BIOS as reserved; standard PC address X ranges will not be reported X X See Also: AH=C7h - AX=E801h"Phoenix" - AX=E881h - MEM xxxxh:xxx0h"ACPI" X X XFormat of Phoenix BIOS system memory map address range descriptor: X XOffset Size Description (Table 0497) X00h QWORD base address X08h QWORD length in bytes X10h DWORD type of address range (see #0498) X X X(Table 0498) XValues for System Memory Map address type: X01h memory, available to OS X02h reserved, not available (e.g. system ROM, memory-mapped device) X03h ACPI Reclaim Memory (usable by OS after reading ACPI tables) X04h ACPI NVS Memory (OS is required to save this memory between NVS Xsessions) Xother not defined yet -- treat as Reserved X X See Also: #0497 X X Category: Vendor-specific BIOS Extensions - Int 15h - N X X ---------------------- X END-of-/tmp/xm_e820 echo x - /tmp/xm_e801 sed 's/^X//' >/tmp/xm_e801 << 'END-of-/tmp/xm_e801' XFrom gdk Wed Aug 20 10:37:43 1997 XReceived: (from gdk@localhost) by ccomp.inode.com (8.6.9/1.3) id KAA01499; Wed, 20 Aug 1997 10:37:42 -0400 XDate: Wed, 20 Aug 1997 10:37:42 -0400 XFrom: Gary Kendall XMessage-Id: <199708201437.KAA01499@ccomp.inode.com> XX-URL: http://www.ctyme.com/intr/RB-1664.HTM XTo: Gary Kendall XSubject: Int 15/AX=E801h XStatus: O X X X Int 15/AX=E801h X X ---------------------- X X Phoenix BIOS v4.0 - GET MEMORY SIZE FOR >64M CONFIGURATIONS X XAX = E801h X XReturn: XCF clear if successful XAX = extended memory between 1M and 16M, in K (max 3C00h = 15MB) XBX = extended memory above 16M, in 64K blocks XCX = configured memory 1M to 16M, in K XDX = configured memory above 16M, in 64K blocks XCF set on error X X Notes: Supported by the A03 level (6/14/94) and later XPS P90 BIOSes, X as well as the Compaq Contura, 3/8/93 DESKPRO/i, and 7/26/93 LTE Lite X 386 ROM BIOS. Supported by AMI BIOSes dated 8/23/94 or later. This X interface is used by Windows NT 3.1, OS/2 v2.11/2.20, and is used as a X fall-back by newer versions if AX=E820h is not supported X X See Also: AH=8Ah"Phoenix" - AX=E802h - AX=E820h - AX=E881h"Phoenix" X X Category: Vendor-specific BIOS Extensions - Int 15h - P X X ---------------------- X END-of-/tmp/xm_e801 exit --------------------------------- cut here ----------------------------------- From owner-freebsd-hackers Sat Aug 23 10:02:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA02775 for hackers-outgoing; Sat, 23 Aug 1997 10:02:26 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA02770 for ; Sat, 23 Aug 1997 10:02:20 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id TAA01231 for hackers@freebsd.org; Sat, 23 Aug 1997 19:02:18 +0200 (MESZ) From: Robert Eckardt Message-Id: <199708231702.TAA01231@ghost.mep.ruhr-uni-bochum.de> Subject: xdm + login.class ?# To: hackers@freebsd.org Date: Sat, 23 Aug 1997 19:02:18 +0200 (MESZ) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, on questions I asked it already w/o response, but may be hackers is more appropriate. Is it possible to use xdm logins with the benefits of login.class ? (In default-class I set maxproc=100, but xdm-logins only see 40.) I'm running 2.2.2 w/ XF86-3.2 as from the WC CD. (At home I have to use XF86_S3 from XF86-3.3 from the FreeBSD-2.2 binary dist. on xfree86.org) Is it something I can simply configure, I have to recompile or will not work ? TIA, Robert -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Aug 23 10:09:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA03427 for hackers-outgoing; Sat, 23 Aug 1997 10:09:39 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA03420 for ; Sat, 23 Aug 1997 10:09:35 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id TAA01245 for hackers@freebsd.org; Sat, 23 Aug 1997 19:09:33 +0200 (MESZ) From: Robert Eckardt Message-Id: <199708231709.TAA01245@ghost.mep.ruhr-uni-bochum.de> Subject: NIS-master/slave w/ 2.1.7+2.2.2 To: hackers@freebsd.org Date: Sat, 23 Aug 1997 19:09:33 +0200 (MESZ) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, from searching the archives and asking on questions I got no clue. The problem is simply that I want to use a 2.2.2 box as a NIS slave server with a 2.1.7 box as a NIS master. However, when pushing from the master with % yppush -d XYZ amd.home yppush: Transfer request refused by ypserv On the slave side I get messages like: ypserv[24772]: couldn't find master for map amd.home@XYZ ypserv[24772]: host at ZYX (134.147.xxx.yyy) may be pulling my leg Needless to say, all clients (2.2.2 and 2.1.7) are ypbound to the NIS master. Also, I tried w/ and w/o securenets, no change. On the slave exists an empty directory /var/yp/XYZ. Any comments thankfully appreciated, Robert -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Aug 23 10:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04747 for hackers-outgoing; Sat, 23 Aug 1997 10:22:08 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04740 for ; Sat, 23 Aug 1997 10:22:02 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id MAA11474; Sat, 23 Aug 1997 12:21:50 -0500 (EST) From: "John S. Dyson" Message-Id: <199708231721.MAA11474@dyson.iquest.net> Subject: Re: Problems with > 256MB of RAM [what worked & what didn't] In-Reply-To: from Gordon Henderson at "Aug 23, 97 02:46:46 pm" To: gordon@drogon.net (Gordon Henderson) Date: Sat, 23 Aug 1997 12:21:50 -0500 (EST) Cc: hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > > Tor Egge suggested: > > There are two main reasons for this type of panic > > > > 1. temporary shortage of free physical memory (cf PR#2431). > > > > Use sysctl to increase limits of reserved free physical > > memory, reducing the probability for running out of free memory. > > > > sysctl -w vm.v_free_reserved=1024 > > sysctl -w vm.v_free_min=1500 > > This worked. > > Tor also suggested: > > 2. permanent shortage of virtual memory allocated for pv entries. > > > > Increase the size of allocated virtual memory for pv entries > > by adding: > > > > options "PMAP_SHPGPERPROC=400" > > This didn't work. Upping it to 800 didn't work either. Same panic at the > same place. > > John S. Dyson suggested changing NKPDE in pmap.h > (DG's patch bumped this from 63 to 127). I upped it to 255. Didn't work. > Machine didn't even boot! Stopped at: > You would have terrible problems if you increase NKPDE further without other changes (like in the Makefile.) I didn't realize that we had a problem of running out of free memory causing a pv entry allocation failure. I'll have to look at it. John From owner-freebsd-hackers Sat Aug 23 11:01:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA07336 for hackers-outgoing; Sat, 23 Aug 1997 11:01:03 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA07330 for ; Sat, 23 Aug 1997 11:00:57 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id KAA09562; Sat, 23 Aug 1997 10:54:28 -0700 (PDT) To: A Joseph Koshy cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Checking the integrity of system files In-reply-to: Your message of "Sat, 23 Aug 1997 14:35:22 +0530." <199708230908.CAA05685@palrel1.hp.com> Date: Sat, 23 Aug 1997 10:54:28 -0700 Message-ID: <9558.872358868@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there any way, barring parsing the output of `make install' to > or `make release' to determine the list of `current' files on a system? > > I'm looking at a registry of files maintaining sizes, permissions, checksums > of files, against which I can check a system. This is a problem which we're also trying to solve for distributions (or a newer package format which replaced the old "split tarball" distribution format) since you need the same information for upgrades. My impression would be that we'd hack the install rules to also "register" things installed through /usr/src. Jordan From owner-freebsd-hackers Sat Aug 23 11:27:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA08242 for hackers-outgoing; Sat, 23 Aug 1997 11:27:21 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA08237 for ; Sat, 23 Aug 1997 11:27:09 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id NAA05192; Sat, 23 Aug 1997 13:27:04 -0500 (EST) Date: Sat, 23 Aug 1997 13:27:04 -0500 (EST) From: John Fieber To: Robert Eckardt cc: hackers@FreeBSD.ORG Subject: Re: xdm + login.class ?# In-Reply-To: <199708231702.TAA01231@ghost.mep.ruhr-uni-bochum.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, Robert Eckardt wrote: > on questions I asked it already w/o response, but may be hackers is more > appropriate. > > Is it possible to use xdm logins with the benefits of login.class ? Not without patching xdm, unless someone else knows a clever trick I don't know about. I've been pondering looking at the xdm source myself to fix this but have never found the time.... It seems as though the ssh port doesn't do login classes either. -john From owner-freebsd-hackers Sat Aug 23 11:30:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA08391 for hackers-outgoing; Sat, 23 Aug 1997 11:30:19 -0700 (PDT) Received: from actcom.co.il (baum@actcom.co.il [192.114.47.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA08369 for ; Sat, 23 Aug 1997 11:30:12 -0700 (PDT) Received: from localhost by actcom.co.il with SMTP (8.8.6/actcom-0.2) id VAA11630; Sat, 23 Aug 1997 21:22:27 +0300 (EET DST) (rfc931-sender: baum@localhost) Date: Sat, 23 Aug 1997 21:22:26 +0300 (EET DST) From: Alexander Indenbaum To: "Jordan K. Hubbard" cc: A Joseph Koshy , freebsd-hackers@FreeBSD.ORG Subject: Re: Checking the integrity of system files In-Reply-To: <9558.872358868@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, Jordan K. Hubbard wrote: > > Is there any way, barring parsing the output of `make install' to > > or `make release' to determine the list of `current' files on a system? > > > > I'm looking at a registry of files maintaining sizes, permissions, checksums > > of files, against which I can check a system. > > This is a problem which we're also trying to solve for distributions > (or a newer package format which replaced the old "split tarball" > distribution format) since you need the same information for upgrades. > > My impression would be that we'd hack the install rules to also > "register" things installed through /usr/src. > > Jordan > Are you considering to move to RPM-like package management? Alexander Indenbaum baum@actcom.co.il From owner-freebsd-hackers Sat Aug 23 12:08:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09689 for hackers-outgoing; Sat, 23 Aug 1997 12:08:52 -0700 (PDT) Received: from gvr.gvr.org (root@gvr.gvr.org [194.151.74.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09681 for ; Sat, 23 Aug 1997 12:08:47 -0700 (PDT) Received: (from guido@localhost) by gvr.gvr.org (8.8.6/8.8.5) id VAA06497; Sat, 23 Aug 1997 21:08:41 +0200 (MET DST) From: Guido van Rooij Message-Id: <199708231908.VAA06497@gvr.gvr.org> Subject: Re: broadcast question In-Reply-To: <19970823143813.EY59755@uriah.heep.sax.de> from J Wunsch at "Aug 23, 97 02:38:13 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 23 Aug 1997 21:08:41 +0200 (MET DST) Cc: FreeBSD-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > As Guido van Rooij wrote: > > > If I have a host in a subnetted C-net, say 192.1.1.0/28 > > and I send an icmp echo request to the broadcast address of the C-net > > (so NOT to 192.1.1.15) the 2.1.7 stack does send an echo reply > > but the 2.2 stack does not. > > So an all-subnets directed broadcast seems to be ignored on 2.2 > > stacks...I think this broken, yet fail to see where it was broken. > > I think 2.1.x was broken. What is an ``all-subnets'' broadcast in a > CIDR world? Forget about class A/B/C, forget the term `subnet', they > don't exist anymore. (*) The address 192.1.1.255 is not in any way a > valid broadcast address for net 192.1.1.0/28, it's a valid broadcast > address for 192.1.1.128/25, or maybe for 192.1.1.240/28 (which are > entirely different networks from 192.1.1.0/28). I don't agree. See the first Stevens book. There actually are two kinds of broadcasts. Anyway: even if it is a bug, I still can't find where it was fixed. This makes me suspicious. > > (*) The only meaning of the historic classes A/B/C that does still > exist is that they determine the default netmask if nothing else has > been specified in ifconfig(8), or route(8), etc. This can sometimes > be convenient to type. > > 255.255.255.255 should work, i believe. > > I'm surprised 2.1.x was still broken in this respect. At least 2.1 and 2.2 and higher differ here ;-) -Guido From owner-freebsd-hackers Sat Aug 23 12:39:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA10715 for hackers-outgoing; Sat, 23 Aug 1997 12:39:14 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA10710 for ; Sat, 23 Aug 1997 12:39:10 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x2LzK-0004nj-00; Sat, 23 Aug 1997 12:36:46 -0700 Date: Sat, 23 Aug 1997 12:36:46 -0700 (PDT) From: Tom Samplonius To: A Joseph Koshy cc: freebsd-hackers@freebsd.org Subject: Re: Checking the integrity of system files In-Reply-To: <199708230908.CAA05685@palrel1.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, A Joseph Koshy wrote: > > Hi, > > -current being what it supposed to be, I find that as time passes my > system as getting filled up with the carcasses of old and abandoned > programs. At the minimum this can be a space wasting nuisance, and > may also leave way for security breaching > > Is there any way, barring parsing the output of `make install' to > or `make release' to determine the list of `current' files on a system? > > I'm looking at a registry of files maintaining sizes, permissions, checksums > of files, against which I can check a system. > > If such a registry is to be added, what is a good place to add it? > > (a) add the functionality to `install' (but this won't handle ports stuff) > (b) a separate program callable at install or release time or port addition > time. > > Koshy > > mtree can do some of this. See the manpage. Tom From owner-freebsd-hackers Sat Aug 23 15:36:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18370 for hackers-outgoing; Sat, 23 Aug 1997 15:36:16 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA18359; Sat, 23 Aug 1997 15:36:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA04920; Sat, 23 Aug 1997 15:27:49 -0700 From: Terry Lambert Message-Id: <199708232227.PAA04920@phaeton.artisoft.com> Subject: Re: Couldn't change IRQ on Creative SB16 PnP To: richw@webcom.com (Rich Wales) Date: Sat, 23 Aug 1997 15:27:48 -0700 (MST) Cc: smpatel@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Rich Wales" at Aug 22, 97 10:35:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can change the IRQ for the card in DOS (it works fine at IRQ10 under > DOS and Windows) -- but in order to do so, I have to select one of the > card's non-default configurations first (configuration 0 only allows > IRQ5). Is it possible that this might be why the FreeBSD code couldn't > change the IRQ? I assume you mean the configuration 0 in the Windows 95 property page. This is the default from the PnP configuration. You must have an error in your configuration information if IRQ 5 is taken by something else. What you probably ned to do is go into the PnP BIOS configuration and tell it IRQ 5 is taken by an ISA card. PS: If your BIOS doesn't know this, then FreeBSD isn't going to be able to know it either... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Aug 23 15:52:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA18877 for hackers-outgoing; Sat, 23 Aug 1997 15:52:14 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA18872 for ; Sat, 23 Aug 1997 15:52:09 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA24932; Sun, 24 Aug 1997 00:51:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id AAA14592; Sun, 24 Aug 1997 00:26:58 +0200 (MET DST) Message-ID: <19970824002658.FN06965@uriah.heep.sax.de> Date: Sun, 24 Aug 1997 00:26:58 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: roberte@MEP.Ruhr-Uni-Bochum.de (Robert Eckardt) Subject: Re: amd + linux = permission denied References: <199708231653.SAA01215@ghost.mep.ruhr-uni-bochum.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708231653.SAA01215@ghost.mep.ruhr-uni-bochum.de>; from Robert Eckardt on Aug 23, 1997 18:53:41 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Robert Eckardt wrote: > The problem is that I get `Permission denied' when accessing the > auto-mounted directoy. I think that's a problem with (not) using reserved ports. Try -P, or resvport, or something like this. > 18:38 pion: / 0#% mount -o ro,intr,soft,noconn l19-tp2:/usr/local/applix /mnt ro,-i,-s, what's this? The older option names are depreciated. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sat Aug 23 15:58:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19142 for hackers-outgoing; Sat, 23 Aug 1997 15:58:33 -0700 (PDT) Received: from gargoyle.bazzle.com (ppp.bazzle.com [206.103.246.190]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19133 for ; Sat, 23 Aug 1997 15:58:23 -0700 (PDT) Received: from localhost (ejc@localhost) by gargoyle.bazzle.com (8.8.7/8.8.5) with SMTP id SAA01952; Sat, 23 Aug 1997 18:58:06 -0400 (EDT) Date: Sat, 23 Aug 1997 18:58:05 -0400 (EDT) From: "Eric J. Chet" To: Robert Eckardt cc: hackers@FreeBSD.ORG Subject: Re: NIS-master/slave w/ 2.1.7+2.2.2 In-Reply-To: <199708231709.TAA01245@ghost.mep.ruhr-uni-bochum.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, Robert Eckardt wrote: > Hello, > > from searching the archives and asking on questions I got no clue. > > The problem is simply that I want to use a 2.2.2 box as a NIS slave server > with a 2.1.7 box as a NIS master. > > However, when pushing from the master with > % yppush -d XYZ amd.home > yppush: Transfer request refused by ypserv > > On the slave side I get messages like: > ypserv[24772]: couldn't find master for map amd.home@XYZ > ypserv[24772]: host at ZYX (134.147.xxx.yyy) may be pulling my leg > > Needless to say, all clients (2.2.2 and 2.1.7) are ypbound to the NIS master. > Also, I tried w/ and w/o securenets, no change. > On the slave exists an empty directory /var/yp/XYZ. > > > Any comments thankfully appreciated, > Robert Hello The only way I could get the first transfer was manually using ypxfr. Start rpc.ypxfrd, and then use ypxfr. After that everything worked normally with the slave updates. Eric Chet -- ejchet@lucent.com || ejc@bazzle.com Systems Analysts - Specializing in OOA, OOD and CORBA Analysts International Corporation From owner-freebsd-hackers Sat Aug 23 16:55:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA22321 for hackers-outgoing; Sat, 23 Aug 1997 16:55:45 -0700 (PDT) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA22312 for ; Sat, 23 Aug 1997 16:55:40 -0700 (PDT) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.8.5/8.8.4) id BAA02073; Sun, 24 Aug 1997 01:55:27 +0200 (MESZ) From: Robert Eckardt Message-Id: <199708232355.BAA02073@ghost.mep.ruhr-uni-bochum.de> Subject: Re: NIS-master/slave w/ 2.1.7+2.2.2 In-Reply-To: from "Eric J. Chet" at "Aug 23, 97 06:58:05 pm" To: ejc@bazzle.com (Eric J. Chet) Date: Sun, 24 Aug 1997 01:55:27 +0200 (MESZ) Cc: roberte@MEP.Ruhr-Uni-Bochum.de, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It was Eric J. Chet who wrote: > > On Sat, 23 Aug 1997, Robert Eckardt wrote: [..] > > The problem is simply that I want to use a 2.2.2 box as a NIS slave server > > with a 2.1.7 box as a NIS master. > > > > However, when pushing from the master with > > % yppush -d XYZ amd.home > > yppush: Transfer request refused by ypserv > > > > On the slave side I get messages like: > > ypserv[24772]: couldn't find master for map amd.home@XYZ > > ypserv[24772]: host at ZYX (134.147.xxx.yyy) may be pulling my leg [..] > Hello > The only way I could get the first transfer was manually using > ypxfr. Start rpc.ypxfrd, and then use ypxfr. After that everything > worked normally with the slave updates. Thanks ! That was it. I just had to call on the slave machine `ypxfr ' for all maps. Now yppush works again. Robert > Eric Chet -- ejchet@lucent.com || ejc@bazzle.com -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-hackers Sat Aug 23 17:49:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA25085 for hackers-outgoing; Sat, 23 Aug 1997 17:49:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA25075; Sat, 23 Aug 1997 17:49:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA05148; Sat, 23 Aug 1997 17:40:44 -0700 From: Terry Lambert Message-Id: <199708240040.RAA05148@phaeton.artisoft.com> Subject: Re: promblems with non IP protocols To: julian@whistle.com (Julian Elischer) Date: Sat, 23 Aug 1997 17:40:43 -0700 (MST) Cc: wollman@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <33FE24CA.52BFA1D7@whistle.com> from "Julian Elischer" at Aug 22, 97 04:46:18 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1/ I prefer if it is a dynamic thing and > not dependent on a "#ifdef NETATALK" in the kernel. > Is this reasonable? > (I'd like to work towards loadable protocols) I was looking at this as well, recently, mostly because of the ISO stuff going away. I think there are several problems which need to be solved in this area; changing over to a registration mechanism for address families (in the kernel) is only part of it. There also needs to be a set of interfaces for glueing address family manipulation functions into libc, as well. My personal preference would be to provide an interface for listing the available address families that are currently registered at any one time. Then libc would use this to load things like "/usr/lib/af_inet.so"; only it would be "sprintf(loadname,"/usr/lib/af_%s.so", itername);" to build it from an iterated name. Or Strcat or pointer-add it. Whatever. The general address manipulation functions would then change to take a family parameter: net_aton, net_addr, net_network, net_ntoa, net_makeaddr, net_lnaof, net_netof, etc. Backward compatability would be provided via #defines: #define inet_ntoa(in) net_ntoa("inet",in) ... Maybe using inline functions so the compiler can still be anal for those people with compiler fixations: static __inline char *inet_ntoa( struct in_addr in) { return( net_ntoa( "inet", (void *)&in); } > 2/ If it's loadable, and a pointer to a method, then WHERE is the > method stored, so that it can be found? there are several options. [ ... ] > ii) add and entry to the ifaddr struct. > there is already the protocol dependent rtrequest. > adding a protocol dependent address handler > (can do compares, and other operations, given the > appropriate args) doesn't seem like too much of a leap. I vote for this one. The reason I vote for this one instead of a hybrid or an AF_XXX index is that: 1) With dynamic loading of AF_XXX, an array index is out, unless the array is constantly being realloc'ed (ugh.. in the kernel?). 2) It allows you to have a single address family that can inherit multiple policies by having multiple reference structures, and little else in the way of changes. So you could have an "AF_INET" with the default policy and an "AF_INETA" with a modified policy to support classes of service. 3) I think it's cleaner. Yeah, that's an esthetic issue. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Aug 23 18:02:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25530 for hackers-outgoing; Sat, 23 Aug 1997 18:02:42 -0700 (PDT) Received: from ingenieria ([168.176.15.11]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA25513 for ; Sat, 23 Aug 1997 18:02:37 -0700 (PDT) Received: by ingenieria (SMI-8.6/SMI-SVR4) id UAA12701; Sat, 23 Aug 1997 20:49:12 -0400 Date: Sat, 23 Aug 1997 20:49:12 -0400 (EDT) From: Yonny Cardenas To: hackers@freebsd.org Subject: Floppies for FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'am creating floppies of 1.44MB for FreeBSD, I'am puting a UFS filesystem on them, with the following sequence of commands: #fdformat -f 1440 fd0.1440 #disklabel -w -r fd0.1440 floppy3 #newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0 All OK, but I can't mount to them: #:mount_mfs /dev/fd0.1440 /mnt Warning: Block size and bytes per inode restrict cylinders per group to 5. #:Aug 23 19:33:01 zue mount_mfs: /mnt: Operation not supported by device Aug 23 19:33:01 zue mount_mfs: /mnt: Operation not supported by device Thanks, for your help ! ------------------------------------------------------------------------- YONNY CARDENAS B. Systems Engineer || || ||| || Universidad Nacional de Colombia || || || | || Email : yonny@ingenieria.ingsala.unal.edu.co ||||||| || ||| From owner-freebsd-hackers Sat Aug 23 18:03:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25594 for hackers-outgoing; Sat, 23 Aug 1997 18:03:54 -0700 (PDT) Received: from air.infinetgroup.com (air.infinetgroup.com [207.23.43.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25588; Sat, 23 Aug 1997 18:03:50 -0700 (PDT) Received: from localhost (bsdmail@localhost) by air.infinetgroup.com (8.8.5/8.8.4) with SMTP id SAA16981; Sat, 23 Aug 1997 18:01:18 -0700 (PDT) Date: Sat, 23 Aug 1997 18:01:17 -0700 (PDT) From: BSD Mailing Archive To: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: [Q] Win95 SLIP/PPP over null modem? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I apologise if this has been answered b4, but I haven't been in this list for quite a while, and I did search the archives. I'm trying to connect a Win95 laptop to my FreeBSD (2.1) machine and basically have the FreeBSD host act as a gateway to the rest of the network. I was wondering if I could simply use a null modem cable between the two COM ports and trick win95 DUN into using that? AFAIK, DUN will wait for a dial tone, which obviously isn't going to be there. Any ideas? Or should I try PLIP instead? But is there PLIP for win95? :) Please CC all replies to freebsd-hackers@freebsd.org as I don't subscribe to the freebsd-mobile list. Thanks in advance. Len. From owner-freebsd-hackers Sat Aug 23 18:06:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25797 for hackers-outgoing; Sat, 23 Aug 1997 18:06:50 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA25784 for ; Sat, 23 Aug 1997 18:06:42 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id VAA00297; Sat, 23 Aug 1997 21:06:33 -0400 From: Bill Paul Message-Id: <199708240106.VAA00297@skynet.ctr.columbia.edu> Subject: Re: NIS-master/slave w/ 2.1.7+2.2.2 To: roberte@MEP.Ruhr-Uni-Bochum.de (Robert Eckardt) Date: Sat, 23 Aug 1997 21:06:31 -0400 (EDT) Cc: ejc@bazzle.com, hackers@freebsd.org In-Reply-To: <199708232355.BAA02073@ghost.mep.ruhr-uni-bochum.de> from "Robert Eckardt" at Aug 24, 97 01:55:27 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Robert Eckardt had to walk into mine and say: > > It was Eric J. Chet who wrote: > > > > On Sat, 23 Aug 1997, Robert Eckardt wrote: > [..] > > > The problem is simply that I want to use a 2.2.2 box as a NIS slave server > > > with a 2.1.7 box as a NIS master. > > > > > > However, when pushing from the master with > > > % yppush -d XYZ amd.home > > > yppush: Transfer request refused by ypserv > > > > > > On the slave side I get messages like: > > > ypserv[24772]: couldn't find master for map amd.home@XYZ > > > ypserv[24772]: host at ZYX (134.147.xxx.yyy) may be pulling my leg > [..] > > Hello > > The only way I could get the first transfer was manually using > > ypxfr. Start rpc.ypxfrd, and then use ypxfr. After that everything > > worked normally with the slave updates. > > Thanks ! That was it. > I just had to call on the slave machine `ypxfr ' for all maps. > Now yppush works again. For the record, the reason you get the error is that ypserv on the 2.2.2 slave is trying to learn the hostname of the master server from the local copy of the map database file, as opposed to trusting the 'peername' supplied with the ypproc_xfr request. This is a security feature: you don't want to blindly trust the hostname supplied by the caller since the caller may not be a trusted server (you can try to reduce the risk of bogus requests being processed using the securenets feature, but that may not help in the face of IP spoofing). When you first set up an NIS slave, it doesn't have any copies of the maps yet, so the attempt to learn the name of the master fails and you get an error. Same thing happens if you have an already running slave server and you add a new map on the master: you have to go to each slave and ypxfr an intial copy over before future yppush attempts will work. This change was made to the 2.2.x and current branches a while ago. I also patched ypserv in the 2.1.x branch even though there won't be another 2.1.x release. Note that many (most?) ypserv implementations handle the signalling of the error back to yppush incorrectly. The signalling itself is a bit strange because of how map transfers work: when ypserv on a slave receives a request to do a map transfer, it fork()s and exec()s an instance of ypxfr to do the actual transfer rather than doing it itself. This means that ypxfr is the one that has to send the success or failure code back to yppush. It's not possible for ypxfr to inherit the RPC server transport handle from ypserv, so instead ypserv passes arguments to ypxfr that tell it how to 'call back' to the waiting yppush process and let it know what happened. The problem comes when ypserv fails to run ypxfr. In this case, ypserv realizes that it doesn't have an existing local copy of the map in the xfr request, so it doesn't bother launching ypxfr. The SunOS ypserv does the same thing. But since ypxfr is never launched, no error status is ever sent back to yppush, so it ends up just sitting there until the transfer times out. (With the FreeBSD yppush, the timeout is 5 minutes.) The FreeBSD ypserv gets this right: I added code to ypserv to allow it to 'call back' to yppush itself in the event that it can't get ypxfr off the ground. In this case, the error was YPXFR_REFUSED. Yppush gets the message immediately, prints the appropriate error and moves on. What I'm getting at is that if you use a FreeBSD master with a non-FreeBSD slave server, you may get these long delays on the master when trying to yppush a map that the slave doesn't have yet, and this is the reason why. If the 5 minute timeout is too long, you can recompile yppush to use something less (look for YPPUSH_RESPONSE_TIMEOUT in src/usr.sbin/yppush/yppush_extern.h). Oh, lastly: be aware that rpc.ypxfrd should only be run on the NIS master host. Running on the slave won't hurt, but it won't gain you anything either. Also be aware that 2.1.x doesn't support rpc.ypxfrd, so it will always use the 'old' transfer method. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= From owner-freebsd-hackers Sat Aug 23 18:19:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA26476 for hackers-outgoing; Sat, 23 Aug 1997 18:19:12 -0700 (PDT) Received: from thelab.hub.org (root@ppp-173.halifax-01.ican.net [206.231.248.173]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA26464 for ; Sat, 23 Aug 1997 18:19:03 -0700 (PDT) Received: from thelab.hub.org (scrappy@localhost.hub.org [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id WAA00238 for ; Sat, 23 Aug 1997 22:18:50 -0300 (ADT) Date: Sat, 23 Aug 1997 22:18:49 -0300 (ADT) From: The Hermit Hacker To: hackers@freebsd.org Subject: PPP 'Bursts' with newest 3.0-CURRENT... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I'm really curious as to whether anyone has experience with this. I'm running 3.0-CURRENT, and have just upgraded to the newest source tree (as of today) in the hopes of reducing/eliminating the following 'hills and valleys': ================= # netstat -nr Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 127.2.2.2 UGSc 12 0 tun0 127.0.0.1 127.0.0.1 UH 1 44 lo0 206.231.247.114 206.231.248.173 UH 0 0 tun0 # ping 206.231.247.114 PING 206.231.247.114 (206.231.247.114): 56 data bytes 64 bytes from 206.231.247.114: icmp_seq=0 ttl=64 time=244.708 ms 64 bytes from 206.231.247.114: icmp_seq=1 ttl=64 time=260.234 ms 64 bytes from 206.231.247.114: icmp_seq=2 ttl=64 time=2310.207 ms 64 bytes from 206.231.247.114: icmp_seq=3 ttl=64 time=1320.183 ms 64 bytes from 206.231.247.114: icmp_seq=4 ttl=64 time=1730.196 ms 64 bytes from 206.231.247.114: icmp_seq=5 ttl=64 time=2390.181 ms 64 bytes from 206.231.247.114: icmp_seq=6 ttl=64 time=1390.230 ms 64 bytes from 206.231.247.114: icmp_seq=7 ttl=64 time=490.176 ms 64 bytes from 206.231.247.114: icmp_seq=8 ttl=64 time=240.180 ms 64 bytes from 206.231.247.114: icmp_seq=9 ttl=64 time=2100.158 ms ================= This is just me talking to the other end of my PPP link, with the only load on the link being the ping session. No ftp, no telnet, no nothing. Now, the other end of the link is: ============ Aug 23 22:13:15 thelab ppp[181]: Phase: PapInput: ACK Aug 23 22:13:15 thelab ppp[181]: Phase: Received PAP_ACK (Welcome to NetBlazer) ============ A NetBlazer. Has anyone ever noticed this when talking to a Netblazer? I remember back in the UUCP days that talking ??->Telebit would give bad 'interactive' response times, but still? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Sat Aug 23 19:08:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28873 for hackers-outgoing; Sat, 23 Aug 1997 19:08:07 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28792 for ; Sat, 23 Aug 1997 19:07:55 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA26516 for ; Sun, 24 Aug 1997 01:19:31 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id BAA00819 for ; Sun, 24 Aug 1997 01:19:30 +0100 (BST) Message-Id: <199708240019.BAA00819@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@freebsd.org Subject: Broken resolver/named Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 01:19:30 +0100 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a bit of a problem - that I can only put down to being the fault of either the resolver library or named. My /etc/resolv.conf says (in 2.2.2 & -current): domain lan.awfulhak.org (I have a local named running as a primary for ``lan.awfulhak.org'') If I try to resolve an unqualified name that doesn't exist (such as ``x''), the resolver sends two DNS queries (because the first fails). The first query is for ``x.lan.awfulhak.org'', and when that fails, it sends a query for ``x''. The resolver then says "Dunno who ``x'' is, I'll ask someone else.....". This is a bit of a dumb thing to do (I'm on a dial-up to real life)..... There is a compile-time option for named called "LOCALDOM" that allows you to say "domain lan.awfulhak.org" in named.boot, and have the second query answered with "dunno" immediately, but according to named, only broken resolvers send unqualified names to the DNS. Soooooo, does anyone know if the latest version of named deals with this, or if it just keeps the old philosophy of "your resolver is broken" ? BTW, I've tried using "search lan.awfulhak.org" in resolv.conf, and tried both combinations with a trailing ``.'' - makes no difference. IMHO, the resolver shouldn't be sending the second query. Should I look at fixing the resolver ? -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sat Aug 23 19:09:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28963 for hackers-outgoing; Sat, 23 Aug 1997 19:09:27 -0700 (PDT) Received: from thelab.hub.org (root@ppp-142.halifax-01.ican.net [206.231.248.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28948 for ; Sat, 23 Aug 1997 19:09:23 -0700 (PDT) Received: from thelab.hub.org (scrappy@localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id XAA00576; Sat, 23 Aug 1997 23:08:58 -0300 (ADT) Date: Sat, 23 Aug 1997 23:08:58 -0300 (ADT) From: The Hermit Hacker To: Tom Samplonius cc: hackers@FreeBSD.ORG Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Tom Samplonius wrote: > > My machine is a P166, with 128Meg of RAM, and 430Meg of SWAP...is datasize > > the only thing that would affect this particular problem? > > Perhaps there really is no memory left? Perhaps innd has a memory leak? > How much swap do you have? And how big was innd before it died? And how > much more memory did it want? 450meg of Swap, 128Meg of RAM...as for memory leak, thought of that, and monitored innd. Isn't growing to any unreal sizes. Not sure of size just before it died though. Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Sat Aug 23 19:11:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29118 for hackers-outgoing; Sat, 23 Aug 1997 19:11:12 -0700 (PDT) Received: from thelab.hub.org (root@ppp-142.halifax-01.ican.net [206.231.248.142]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29099 for ; Sat, 23 Aug 1997 19:11:05 -0700 (PDT) Received: from thelab.hub.org (scrappy@localhost [127.0.0.1]) by thelab.hub.org (8.8.7/8.8.2) with SMTP id XAA00587; Sat, 23 Aug 1997 23:10:52 -0300 (ADT) Date: Sat, 23 Aug 1997 23:10:52 -0300 (ADT) From: The Hermit Hacker To: Marc Slemko cc: hackers@FreeBSD.ORG Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Marc Slemko wrote: > On Sun, 17 Aug 1997, The Hermit Hacker wrote: > > > > > Hi... > > > > After going through "the archives", and finding the suggestion of increasing > > MEMDSIZ to 256Meg, and recompiling/running the new kernel...I'm still getting > > the remalloc 'crash' with innd. > > > > The kernel is 2.2.2-RELEASE, innd is 1.6b3...I have an 'unlimit' at the > > beginning of ~news/etc/rc.news... > > What does a ulimit -a run from rc.news after your unlimit say? > > It should be MAXDSIZ; was the just a typo, or did you set the wrong thing? typo :( Just checked, and it was MAXDSIZ that I sent... > What does the inn log report? Just the remalloc() error, which varies for each time it happens... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org From owner-freebsd-hackers Sat Aug 23 19:14:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29334 for hackers-outgoing; Sat, 23 Aug 1997 19:14:47 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA29305; Sat, 23 Aug 1997 19:14:31 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 25661 on Sun, 24 Aug 1997 02:14:24 GMT; id CAA25661 efrom: peter@grendel.IAEhv.nl; eto: UNKNOWN Received: (from peter@localhost) by grendel.IAEhv.nl (8.8.5/8.8.5) id EAA00673; Sun, 24 Aug 1997 04:13:10 +0200 (CEST) Message-ID: <19970824041310.14744@grendel.IAEhv.nl> Date: Sun, 24 Aug 1997 04:13:10 +0200 From: Peter Korsten To: BSD Mailing Archive Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: [Q] Win95 SLIP/PPP over null modem? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67e In-Reply-To: ; from BSD Mailing Archive on Sat, Aug 23, 1997 at 06:01:17PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk BSD Mailing Archive shared with us: > > I'm trying to connect a Win95 laptop to my FreeBSD (2.1) machine and > basically have the FreeBSD host act as a gateway to the rest of the > network. I was wondering if I could simply use a null modem cable > between the two COM ports and trick win95 DUN into using that? AFAIK, > DUN will wait for a dial tone, which obviously isn't going to be there. > Any ideas? > > Or should I try PLIP instead? But is there PLIP for win95? :) The problem is not FreeBSD, the problem is Windows 95. (Now that I re-read my mail, this looks a bit like stating the obvious :) ). You could replace 'my FreeBSD machine' by 'my Solaris machine' or 'my NT machine' and the question would be the same: a Windows 95 question. 'Dial-up networking' doesn't look like the solution here, since it intended to, right, dial up. Perhaps you'd better check www.windows95.com or cws.internet.com to find usefull 95/NT tools. - Peter From owner-freebsd-hackers Sat Aug 23 19:24:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29657 for hackers-outgoing; Sat, 23 Aug 1997 19:24:53 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29646 for ; Sat, 23 Aug 1997 19:24:49 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id TAA11638; Sat, 23 Aug 1997 19:24:48 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.6/8.8.5) with SMTP id TAA10068; Sat, 23 Aug 1997 19:24:48 -0700 (PDT) Date: Sat, 23 Aug 1997 19:24:47 -0700 (PDT) From: Chris Timmons To: Robert Eckardt cc: hackers@FreeBSD.ORG Subject: Re: xdm + login.class ?# In-Reply-To: <199708231702.TAA01231@ghost.mep.ruhr-uni-bochum.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk About the only workaround that I know of is to modify your "daemon" entry in /etc/login.conf if you are starting xdm via /etc/rc (or one of the scripts it runs.) I just copied "root"'s parameters to "daemon" and did a cap_mkdb to bump things up on my home machine... which kind of defeats the purpose but I can afford to do so on my personal workstation. -Chris On Sat, 23 Aug 1997, Robert Eckardt wrote: > Hello, > > on questions I asked it already w/o response, but may be hackers is more > appropriate. > > Is it possible to use xdm logins with the benefits of login.class ? > > (In default-class I set maxproc=100, but xdm-logins only see 40.) > > I'm running 2.2.2 w/ XF86-3.2 as from the WC CD. > (At home I have to use XF86_S3 from XF86-3.3 from the FreeBSD-2.2 > binary dist. on xfree86.org) > > Is it something I can simply configure, I have to recompile > or will not work ? > > TIA, > Robert > > -- > Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) > RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) > http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte > For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de > From owner-freebsd-hackers Sat Aug 23 20:02:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA01293 for hackers-outgoing; Sat, 23 Aug 1997 20:02:59 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA01286 for ; Sat, 23 Aug 1997 20:02:40 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00846; Sun, 24 Aug 1997 12:30:58 +0930 (CST) Message-Id: <199708240300.MAA00846@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Broken resolver/named In-reply-to: Your message of "Sun, 24 Aug 1997 01:19:30 +0100." <199708240019.BAA00819@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 12:30:55 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I have a bit of a problem - that I can only put down to being the > fault of either the resolver library or named. Neither. > My /etc/resolv.conf says (in 2.2.2 & -current): > > domain lan.awfulhak.org Have you read the resolver documentation on what this means? > If I try to resolve an unqualified name that doesn't exist (such as > ``x''), the resolver sends two DNS queries (because the first fails). > The first query is for ``x.lan.awfulhak.org'', and when that fails, > it sends a query for ``x''. The resolver then says "Dunno who ``x'' > is, I'll ask someone else.....". > > This is a bit of a dumb thing to do (I'm on a dial-up to real life)..... It is, however, the _correct_ thing to do. If you don't want to dial to resolve names, use the dfilter stuff in user-mode ppp (do I need to tell *you* this?) > There is a compile-time option for named called "LOCALDOM" that > allows you to say "domain lan.awfulhak.org" in named.boot, and have > the second query answered with "dunno" immediately, but according to > named, only broken resolvers send unqualified names to the DNS. I don't understand how this would be useful. If you say "x", and "x" is not a local name, you _must_ consult someone else to determine if it's a valid name at all. How else are you supposed to know one way or the other? If you never want to consult an outside nameserver, disable your forwarders; this is pretty dumb though. > IMHO, the resolver shouldn't be sending the second query. Should I > look at fixing the resolver ? There's nothing there needs fixing, AFAICT. mike From owner-freebsd-hackers Sat Aug 23 20:11:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA01516 for hackers-outgoing; Sat, 23 Aug 1997 20:11:41 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA01511 for ; Sat, 23 Aug 1997 20:11:35 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00881; Sun, 24 Aug 1997 12:33:36 +0930 (CST) Message-Id: <199708240303.MAA00881@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alexander Indenbaum cc: "Jordan K. Hubbard" , A Joseph Koshy , freebsd-hackers@freebsd.org Subject: Re: Checking the integrity of system files In-reply-to: Your message of "Sat, 23 Aug 1997 21:22:26 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 12:33:34 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Is there any way, barring parsing the output of `make install' to > > > or `make release' to determine the list of `current' files on a system? Not trivially, due to enthusiastic use of "install -C" > > This is a problem which we're also trying to solve for distributions > > (or a newer package format which replaced the old "split tarball" > > distribution format) since you need the same information for upgrades. > > > > My impression would be that we'd hack the install rules to also > > "register" things installed through /usr/src. > > Are you considering to move to RPM-like package management? Can you be more specific than "RPM-like"? Yes in that there will be management tools, no in that they are unlikely to be the RPM tools. mike From owner-freebsd-hackers Sat Aug 23 20:25:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA02163 for hackers-outgoing; Sat, 23 Aug 1997 20:25:38 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02157; Sat, 23 Aug 1997 20:25:36 -0700 (PDT) Received: from iago.ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.8.5/8.8.5) with ESMTP id UAA14389 Sat, 23 Aug 1997 20:25:14 -0700 (PDT) Message-Id: <199708240325.UAA14389@iago.ienet.com> From: pius@ienet.com To: BSD Mailing Archive Cc: freebsd-mobile@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, Peter Korsten Subject: Re: [Q] Win95 SLIP/PPP over null modem? Date: Sat, 23 Aug 1997 20:25:14 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry, I don't have the original message anymore. So I'm quoting the first reply. On Sun, 24 Aug 1997, peter@grendel.IAEhv.nl wrote: > BSD Mailing Archive shared with us: > > > > I'm trying to connect a Win95 laptop to my FreeBSD (2.1) machine and > > basically have the FreeBSD host act as a gateway to the rest of the > > network. I was wondering if I could simply use a null modem cable > > between the two COM ports and trick win95 DUN into using that? AFAIK, > > DUN will wait for a dial tone, which obviously isn't going to be there. > > Any ideas? Check out http://www.vt.edu:10021/K/kewells/net/ >From there you can download a null modem dialup networking driver for Windows 95/NT. Best regards, Pius From owner-freebsd-hackers Sat Aug 23 20:37:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03010 for hackers-outgoing; Sat, 23 Aug 1997 20:37:46 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA02997 for ; Sat, 23 Aug 1997 20:37:42 -0700 (PDT) Received: (qmail 7740 invoked by uid 1000); 24 Aug 1997 03:38:01 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-Priority: 1 (High) Priority: urgent Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sat, 23 Aug 1997 20:38:01 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Panic During Install - FFS Bug? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, 3.0-CURRENT as of last night (23-Aug-97) In installing -current on a new machine, it panics during installing packages, pretty much at random. Finally got enough installed to put a kernel with ddb to see the trace: vgonel + 9f getnewvnode + b3 ffs_vget ffs_valloc ufs_makeinode ufs_create vn_open open syscall Xsyscall Crash due to reference to data at location 0x04. Calling process was cpio. Who do I talk to about that? BTW, 2 points: * This happens in single-user from the boot floppy, single user kernel.GENERIC, multi-user kernel.GENERIC or kernel.DPT. * Under normal, even very heavy load, including massive cpio copies, even concurrent ones, this does not happen. Simon From owner-freebsd-hackers Sat Aug 23 20:47:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA03578 for hackers-outgoing; Sat, 23 Aug 1997 20:47:09 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA03557; Sat, 23 Aug 1997 20:47:02 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x2Tbm-00053x-00; Sat, 23 Aug 1997 20:44:58 -0700 Date: Sat, 23 Aug 1997 20:44:57 -0700 (PDT) From: Tom Samplonius To: BSD Mailing Archive cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [Q] Win95 SLIP/PPP over null modem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 23 Aug 1997, BSD Mailing Archive wrote: > Hi, > I apologise if this has been answered b4, but I haven't been in this > list for quite a while, and I did search the archives. > > I'm trying to connect a Win95 laptop to my FreeBSD (2.1) machine and > basically have the FreeBSD host act as a gateway to the rest of the > network. I was wondering if I could simply use a null modem cable > between the two COM ports and trick win95 DUN into using that? AFAIK, > DUN will wait for a dial tone, which obviously isn't going to be there. > Any ideas? It is looking for a dial-tone, it looking for a "CONNECT xxx" in response to an "ATDT xxx-xxxx" command (plus some other AT commands it uses). I think you can work around this by using the scripting addon (part of the Plus pack, which also include SLIP support), and write a script which doesn't send AT commands. > Thanks in advance. > Len. > > > > Tom From owner-freebsd-hackers Sat Aug 23 22:09:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA09240 for hackers-outgoing; Sat, 23 Aug 1997 22:09:11 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA09235 for ; Sat, 23 Aug 1997 22:09:08 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id AAA13345; Sun, 24 Aug 1997 00:08:57 -0500 (EST) From: "John S. Dyson" Message-Id: <199708240508.AAA13345@dyson.iquest.net> Subject: Re: [HACKERS] innd remalloc failure *after* setting MEMDSIZ In-Reply-To: from The Hermit Hacker at "Aug 23, 97 11:10:52 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Sun, 24 Aug 1997 00:08:57 -0500 (EST) Cc: marcs@znep.com, hackers@FreeBSD.ORG 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 X-Loop: FreeBSD.org Precedence: bulk > > > What does the inn log report? > > Just the remalloc() error, which varies for each time it happens... > > Maybe try using phkmalloc or gnumalloc? John From owner-freebsd-hackers Sat Aug 23 23:34:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA16628 for hackers-outgoing; Sat, 23 Aug 1997 23:34:05 -0700 (PDT) Received: from mole (mole.slip.net [207.171.193.16]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA16598; Sat, 23 Aug 1997 23:34:01 -0700 (PDT) Received: from localhost.localhost [207.171.230.91] by mole with esmtp (Exim 1.62 #4) id 0x2WFI-0001jq-00; Sat, 23 Aug 1997 23:33:57 -0700 Received: (from richw@localhost) by localhost.localhost (8.8.5/RICHW-970725c) id XAA00242; Sat, 23 Aug 1997 23:32:56 -0700 (PDT) Date: Sat, 23 Aug 1997 23:32:55 -0700 (PDT) From: Rich Wales X-Sender: richw@localhost Reply-To: Rich Wales To: Terry Lambert cc: smpatel@freebsd.org, hackers@freebsd.org Subject: Re: Couldn't change IRQ on Creative SB16 PnP In-Reply-To: <199708232227.PAA04920@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry -- Replying to: I assume you mean the configuration 0 in the Windows 95 property page. This is the default from the PnP config- uration. Yes, that's what I meant -- configuration 0. Is there any way to tell i386/isa/pnp.c to activate a configuration other than 0? You must have an error in your configuration information if IRQ 5 is taken by something else. IRQ 5 isn't taken by anything else right now. I want to add another (legacy ISA) card that must use IRQ 5. My plan was to reconfigure the SB16 PnP sound card to use IRQ 10 (instead of its default IRQ 5), and =then= add the other card on IRQ 5 =after= the sound card was working on IRQ 10. What you probably need to do is go into the PnP BIOS configuration and tell it IRQ 5 is taken by an ISA card. I tried this, but it didn't help; the sound card still wouldn't accept IRQ 10, and when I ran "pnpinfo", it still reported IRQ 5 as the only IRQ available to the sound card in configuration 0. Note, FWIW, that the SB16 card is an ISA (not PCI) PnP card. I don't know if this makes a difference or not. PS: If your BIOS doesn't know this, then FreeBSD isn't going to be able to know it either... But when I run DOS (6.22) and Windows (3.1) on the same system, and tell them to use IRQ 10 to talk to the sound card, it works just fine. This works even if the BIOS thinks IRQ 5 is available for PnP. So I assume the BIOS is OK, and that the FreeBSD code is failing for some reason to do whatever is necessary to set up the right IRQ. Rich Wales richw@webcom.com http://www.webcom.com/richw/