From owner-freebsd-hackers Sun Jul 27 00:09:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA21315 for hackers-outgoing; Sun, 27 Jul 1997 00:09:01 -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 AAA21308 for ; Sun, 27 Jul 1997 00:08:56 -0700 (PDT) Received: (qmail 18165 invoked by uid 1000); 27 Jul 1997 07:09:09 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707261958.MAA02939@phaeton.artisoft.com> Date: Sun, 27 Jul 1997 00:09:09 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: SVR4.2MP source code has become available recently? Cc: hackers@FreeBSD.ORG, stesin@gu.net Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I basically agree with the below comments. The SMP code was derived (according to legend) from Sequent work and therfore should be interesting. The only thing I liked about the desktop was the desktop itself (the class of functionality comparable to xfm). The rest of it was, well... Let it rest in peace indeed. I worked mostly on I/O, boot and other such messes and was endlessly amused at the number of lines of code everything took. I honestly (as a newcomer to FreeBSD), think we have here a superior O/S. Much lower level of pompousness, in any case... Much lower. Simon Hi Terry Lambert; On 26-Jul-97 you wrote: > [ ... UnixWare ... ] > > > It has a descent SMP implementation (Better than Solaris). > > The SCSI layer may be interesting. > > Used to have a nice desktop for X11 > > Ugh. > > The SMP implementation *is* "better"... quoted because it is more > x86 dependent tha the Solaris stuff. Personally, I'd use the > Solaris model, if only for hardware compatability, if I had the > choice to make, and if doing so would not infringe trade secrets > and copyrights, and risk contamination. Remember that both these > source bases are *licensed*, not freely usable. > > > The UnixWare SCSI layer probably excludes the HIM-derived code for > the Adaptec controllers, which is about the only thing that I found > interesting about the code. Honestly, Julian's code was better > than UnixWare's at the time. > > > The X11 desktop was only nice in that it was an OpenLook with hacks > to let it have a Motif "look and feel", and let you switch between > them. Like all compromise soloutions, it was vastly disliked. > > The major reason the desktop was shipped was "Not Invented Here" > for CDE and Visix Looking Glass. > > This type of crap is why UnixWare never succeeded in the desktop > market. > > Most of the driving forces behind the UnixWare developement, which > mainly occurred at Univel, a partnership between AT&T and Novell, > before Novell bought USL and owned it all themselves, were people > like Gary Tomlinson and Brian Sparks. > > If that second name is familiar, it should be: Brian Sparks was > the person behind the original NetWare for UNIX product, and > through it, the genesis of the Platform Independent NetWare > code (a derivitive of his idea, not something he personally did; > it was, IMO, inferior to the NetWare for UNIX code in many ways, > and ended up being pulled into the mainline NetWare -- an unfortunate > occurance). > > Brian Sparks is also the guy behind the Novell project to build > a desktop OS based on Linux (internally, they were called "Linivel"), > and eventually went on to be the principle founder of Caldera > when the internal project was killed for fear of it damaging > UnixWare sales (UnixWare has a rather large footprint). > > The shitty UnixWare desktop that could not be replaced because > it was USL technology was IMO, one of the straws that broke the > camels back; I would not recommend getting the code... let it die > in peace. > > > 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 Jul 27 00:13:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA21535 for hackers-outgoing; Sun, 27 Jul 1997 00:13:05 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA21526; Sun, 27 Jul 1997 00:12:55 -0700 (PDT) Message-Id: <199707270712.AAA21526@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA246816387; Sun, 27 Jul 1997 16:53:07 +1000 From: Darren Reed Subject: Re: SVR4.2MP source code has become available recently? To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Sun, 27 Jul 1997 16:53:07 +1000 (EST) Cc: stesin@gu.net, dyson@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199707270509.LAA25603@hq.icb.chel.su> from "Serge A. Babkin" at Jul 27, 97 11:09:08 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Serge A. Babkin, sie said: > > > And they have some kind of "unified driver interface" spec for UW. > > How nice would it be -- to have an ability to use hardware > > vendor's own drivers for UW, compatible with that spec, > > just out of the box. Aaghh, dreams, dreams... :( > > About the driver interface. They have the document named "Device Driver > Interface", the current version (that will be implemented in SCO > Gemini) is DDI 8. A good thing is this documents descripts not only > the calls that driver must support but the functions it can use too. > It is made to allow to link the drivers with compliance to different > levels of DDI simultaneously. The linking is dynamic, the function > names are substituted to reflect the DDI level. This has > one important consequence: all you need to link in the SVR4 > drivers is to have the DDI-compliant in-kernel library and > a SVR4->BSD object file format converter. Of course, you'll > need STREAMS to use the SVR4 network drivers. mmm, DDI & DDK. Darren From owner-freebsd-hackers Sun Jul 27 00:22:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA21893 for hackers-outgoing; Sun, 27 Jul 1997 00:22:27 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA21881 for ; Sun, 27 Jul 1997 00:22:20 -0700 (PDT) Message-Id: <199707270722.AAA21881@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA248256867; Sun, 27 Jul 1997 17:01:07 +1000 From: Darren Reed Subject: Re: ipfw divert, transparent proxy To: kernel@acromail.ml.org (FreeBSD Technical Reader) Date: Sun, 27 Jul 1997 17:01:07 +1000 (EST) Cc: danny@panda.hilink.com.au, danj@3skel.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "FreeBSD Technical Reader" at Jul 26, 97 12:32:31 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from FreeBSD Technical Reader, sie said: > > I know I could be banned for life for saying this --- but you could also > use a linux machine and the ipmasquerading built into the kernel for doing > this, there are no equivalent features in FreeBSD and it works much better > than natd (Ipmasquerading is one of the things i miss from linux). Please > forgive me for this sin. Ugh.. I hate seeing people promote broken algorithms which they've come to love. Darren From owner-freebsd-hackers Sun Jul 27 07:36:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07168 for hackers-outgoing; Sun, 27 Jul 1997 07:36:22 -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 HAA07158 for ; Sun, 27 Jul 1997 07:36:17 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wsUQU-00034s-00; Sun, 27 Jul 1997 08:36:02 -0600 To: "Jordan K. Hubbard" Subject: Re: Adaptec 2940UW Cc: "Jeff Kreska" , freebsd-hackers@freebsd.org In-reply-to: Your message of "Fri, 25 Jul 1997 12:06:30 PDT." <18546.869857590@time.cdrom.com> References: <18546.869857590@time.cdrom.com> Date: Sun, 27 Jul 1997 08:36:02 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <18546.869857590@time.cdrom.com> "Jordan K. Hubbard" writes: : Odd - I'm having no problems with my 2940UWs at all. What was : the PR#? I've seen lots of problem reports for the 2940AU (or that UA) under a variety of OSes. Maybe that's the problem? Warner From owner-freebsd-hackers Sun Jul 27 07:38:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07260 for hackers-outgoing; Sun, 27 Jul 1997 07:38:56 -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 HAA07252 for ; Sun, 27 Jul 1997 07:38:53 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wsUT6-000351-00; Sun, 27 Jul 1997 08:38:44 -0600 To: "Daniel M. Eischen" Subject: Re: Adaptec 2940UW Cc: Jeff.Kreska@MCI.Com, hackers@freebsd.org In-reply-to: Your message of "Fri, 25 Jul 1997 15:17:17 CDT." <199707252017.PAA03765@iworks.InterWorks.org> References: <199707252017.PAA03765@iworks.InterWorks.org> Date: Sun, 27 Jul 1997 08:38:44 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707252017.PAA03765@iworks.InterWorks.org> "Daniel M. Eischen" writes: : And it's working perfectly with 2.2 (some version of stable) and 3.0-current : for me. How about a more detailed description of your problem? I'm betting : it's a cabling or termination problem. I know of several people who have had problems with the 2940AU. This is a different board from the 2940U or UW. Some revs of it have lots of problems with reset and other oddities. Since I don't have one of these cards, I think that the output from dmesg of the boot probe of the aha device might not be a bad thing to get too. Warner From owner-freebsd-hackers Sun Jul 27 07:46:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07528 for hackers-outgoing; Sun, 27 Jul 1997 07:46:23 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA07522; Sun, 27 Jul 1997 07:46:20 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id JAA24051; Sun, 27 Jul 1997 09:46:19 -0500 (EST) Date: Sun, 27 Jul 1997 09:46:19 -0500 (EST) From: John Fieber To: "Jonathan M. Bresler" cc: freebsd-hackers@FreeBSD.ORG Subject: Installing cf files (was Re: Sendmail Problems?) In-Reply-To: <199707271425.HAA06705@hub.freebsd.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 [slight topic change, redirect to hackers] On Sun, 27 Jul 1997, Jonathan M. Bresler wrote: > hmm...you sent your /etc/sendmail.cf rather then your > .mc file....you are using the m4 macros for sendmail arent you. > /usr/src/usr.sbin/sendmail/cf/cf/*.mc I was just thinking the other day, it would be handy if the cf directory were installed somewhere so that people (like myself) who want to brew a new sendmail.cf using m4 don't have to go dig sendmail out of the source tree to do it. Thoughts? -john From owner-freebsd-hackers Sun Jul 27 08:56:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10263 for hackers-outgoing; Sun, 27 Jul 1997 08:56:25 -0700 (PDT) Received: from aaka.3skel.com (aaka.3skel.com [207.240.134.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10258 for ; Sun, 27 Jul 1997 08:56:19 -0700 (PDT) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by aaka.3skel.com (8.8.5/8.8.2) with ESMTP id LAA10434; Sun, 27 Jul 1997 11:56:00 -0400 (EDT) Received: (from danj@localhost) by fnur.3skel.com (8.8.5/8.8.2) id LAA00845; Sun, 27 Jul 1997 11:55:58 -0400 (EDT) Date: Sun, 27 Jul 1997 11:55:58 -0400 (EDT) From: Dan Janowski Message-Id: <199707271555.LAA00845@fnur.3skel.com> To: avalon@coombs.anu.edu.au, kernel@acromail.ml.org Subject: Re: ipfw divert, transparent proxy Cc: danj@3skel.com, danny@panda.hilink.com.au, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There seems to be some agreement that using divert sockets is the way to go, but I still am at a loss for any examples using the mechanism. Does anyone have any code, snippet or functional, that utilizes the interface? Reading the kernel code is only a step away, but an example, even a simple one, would help. Dan From owner-freebsd-hackers Sun Jul 27 09:03:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10548 for hackers-outgoing; Sun, 27 Jul 1997 09:03:51 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10531; Sun, 27 Jul 1997 09:03:43 -0700 (PDT) Received: from dbws.etinc.com (db@dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id MAA22401; Sun, 27 Jul 1997 12:08:47 -0400 (EDT) Message-Id: <3.0.32.19970727115943.006dad5c@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 27 Jul 1997 11:59:48 -0400 To: "Serge A. Babkin" , stesin@gu.net From: Dennis Subject: Re: SVR4.2MP source code has become available recently? Cc: dyson@FreeBSD.ORG, hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:09 AM 7/27/97 +0600, Serge A. Babkin wrote: >> And they have some kind of "unified driver interface" spec for UW. >> How nice would it be -- to have an ability to use hardware >> vendor's own drivers for UW, compatible with that spec, >> just out of the box. Aaghh, dreams, dreams... :( > >About the driver interface. They have the document named "Device Driver >Interface", the current version (that will be implemented in SCO >Gemini) is DDI 8. A good thing is this documents descripts not only >the calls that driver must support but the functions it can use too. >It is made to allow to link the drivers with compliance to different >levels of DDI simultaneously. The linking is dynamic, the function >names are substituted to reflect the DDI level. This has >one important consequence: all you need to link in the SVR4 >drivers is to have the DDI-compliant in-kernel library and >a SVR4->BSD object file format converter. Of course, you'll >need STREAMS to use the SVR4 network drivers. > >-SB What about DLPI? And (I'm sorry, i missed the beginning of this thread), what are we talking about? SCO, Univel, Solaris? dennis > From owner-freebsd-hackers Sun Jul 27 09:04:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10620 for hackers-outgoing; Sun, 27 Jul 1997 09:04:32 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10609; Sun, 27 Jul 1997 09:04:21 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199707271604.JAA10609@hub.freebsd.org> Subject: Re: Installing cf files (was Re: Sendmail Problems?) To: jfieber@indiana.edu (John Fieber) Date: Sun, 27 Jul 1997 09:04:21 -0700 (PDT) Cc: jmb@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "John Fieber" at Jul 27, 97 09:46:19 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Fieber wrote: > > [slight topic change, redirect to hackers] > > On Sun, 27 Jul 1997, Jonathan M. Bresler wrote: > > > hmm...you sent your /etc/sendmail.cf rather then your > > .mc file....you are using the m4 macros for sendmail arent you. > > /usr/src/usr.sbin/sendmail/cf/cf/*.mc > > I was just thinking the other day, it would be handy if the cf > directory were installed somewhere so that people (like myself) > who want to brew a new sendmail.cf using m4 don't have to go dig > sendmail out of the source tree to do it. i would suggest /usr/share/....cf per hier(7) share/ architecture-independent ascii text files including the me macros and groff_fonts cf seems to fit the bill. better ideas? jmb From owner-freebsd-hackers Sun Jul 27 09:31:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11658 for hackers-outgoing; Sun, 27 Jul 1997 09:31:10 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA11646 for ; Sun, 27 Jul 1997 09:31:07 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id JAA23528; Sun, 27 Jul 1997 09:31:06 -0700 Date: Sun, 27 Jul 1997 09:31:06 -0700 From: Sean Eric Fagan Message-Id: <199707271631.JAA23528@kithrup.com> To: hackers@freebsd.org Subject: Re: SVR4.2MP source code has become available recently? In-Reply-To: Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you write: >I've hear rumors that the source code for SCO UnixWare 2.1.x >is now available from SCO for $500 for educational >institutions. > >Isn't this interesting as a reference? How do you think? No. Under no circumstances should you use it as a reference. This is dangerous. Unless, of course, you don't want to do any FreeBSD development, or, if you do, you want to get yourself and/or Jordan Hubbard sued for some intellectual property violation (e.g., copyright or trade secret). From owner-freebsd-hackers Sun Jul 27 11:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA16446 for hackers-outgoing; Sun, 27 Jul 1997 11:46:44 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA16441 for ; Sun, 27 Jul 1997 11:46:41 -0700 (PDT) Received: from slip129-37-195-174.nc.us.ibm.net (slip129-37-195-174.nc.us.ibm.net [129.37.195.174]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id SAA74664 for ; Sun, 27 Jul 1997 18:46:38 GMT From: mouth@ibm.net (John Kelly) To: hackers@FreeBSD.ORG Subject: Re: Modem problems Date: Sun, 27 Jul 1997 18:48:44 GMT Message-ID: <33dd94bb.3095243@smtp-gw01.ny.us.ibm.net> References: <19970726201841.20682@goof.com> In-Reply-To: <19970726201841.20682@goof.com> X-Mailer: Forte Agent 1.01/16.397 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 LAA16442 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 26 Jul 1997 20:18:41 -0400, you wrote: > Hi. I'm having some problems with a no-name internal >modem that are baffling me, and I'm hoping to find some help. I >recently started to need two serial ports in addition to my >modem, so I moved it to sio3 and irq 2/9, whereas it used to be >setup as sio1 irq 3. Once I changed the modem over, FreeBSD >would no longer get decent transfer rates. I have 16 serial ports in my machine. By means of resistors and diodes, two of them are sharing IRQ 9, and they work fine under FreeBSD 2-2-2. There are all sorts of things that can be wrong. I've heard some people claim that because it's the "slave" interrupt, IRQ 2/9 would not work properly in their machine, or anyone else's machine for that matter. I've never found that to be true in any machine of mine, though. I nearly always use IRQ 9 for a modem serial port without any problems. You might try a different IRQ. Even if you have to pull out some other card to try IRQ 5, 7, or whatever, the most likely person to diagnose the problem is you since you have access to the hardware. John. From owner-freebsd-hackers Sun Jul 27 12:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17705 for hackers-outgoing; Sun, 27 Jul 1997 12:22:08 -0700 (PDT) Received: from goof.com (qmailr@goof.com [128.173.247.211]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA17699 for ; Sun, 27 Jul 1997 12:22:04 -0700 (PDT) Received: (qmail 29865 invoked by uid 10000); 27 Jul 1997 19:18:51 -0000 Message-ID: <19970727151851.49300@goof.com> Date: Sun, 27 Jul 1997 15:18:51 -0400 From: "matthew c. mead" To: John Kelly Cc: hackers@FreeBSD.ORG Subject: Re: Modem problems References: <19970726201841.20682@goof.com> <33dd94bb.3095243@smtp-gw01.ny.us.ibm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <33dd94bb.3095243@smtp-gw01.ny.us.ibm.net>; from John Kelly on Sun, Jul 27, 1997 at 06:48:44PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 27, 1997 at 06:48:44PM +0000, John Kelly wrote: > On Sat, 26 Jul 1997 20:18:41 -0400, you wrote: > > Hi. I'm having some problems with a no-name internal > >modem that are baffling me, and I'm hoping to find some help. I > >recently started to need two serial ports in addition to my > >modem, so I moved it to sio3 and irq 2/9, whereas it used to be > >setup as sio1 irq 3. Once I changed the modem over, FreeBSD > >would no longer get decent transfer rates. > I have 16 serial ports in my machine. By means of resistors and > diodes, two of them are sharing IRQ 9, and they work fine under > FreeBSD 2-2-2. Hmm. > There are all sorts of things that can be wrong. I've heard some > people claim that because it's the "slave" interrupt, IRQ 2/9 would > not work properly in their machine, or anyone else's machine for that > matter. I've never found that to be true in any machine of mine, > though. I nearly always use IRQ 9 for a modem serial port without any > problems. Interesting. Like I mentioned, it works fine under every other operating system I've tried, which is why I'm asking here. > You might try a different IRQ. Even if you have to pull out some > other card to try IRQ 5, 7, or whatever, the most likely person to > diagnose the problem is you since you have access to the hardware. I'll yank this POS SB 32 PnP card and try it at irq 5. Unfortunately, I can't get the damn thing to stay at irq 10 under FreeBSD. Maybe that could be a solution. I'll try using the modem at IRQ 9 and see if it works. At that point, I'm not sure which way to turn. Any thoughts? Thanks for the response. -matt -- Matthew C. Mead mmead@goof.com http://www.goof.com/~mmead/ From owner-freebsd-hackers Sun Jul 27 12:58:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18964 for hackers-outgoing; Sun, 27 Jul 1997 12:58:35 -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 MAA18958 for ; Sun, 27 Jul 1997 12:58:30 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA01210; Sun, 27 Jul 1997 12:55:29 -0700 From: Terry Lambert Message-Id: <199707271955.MAA01210@phaeton.artisoft.com> Subject: Re: /bin/chio: why in /bin ? To: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=) Date: Sun, 27 Jul 1997 12:55:29 -0700 (MST) Cc: louie@TransSys.COM, gibbs@plutotech.com, laskavy@cs.msu.su, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=" at Jul 27, 97 00:29:58 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 > > chio is not clearly machine dependent. It talks to any SCSI media > > changer device, just like mt works with any SCSI tape device. > > Your words are in conflict: you talk about "not machine dependent" > and "SCSI device". Any phisical device which not exist for all machines > (like memory f.e.) IS machine dependance. SCSI not exist for all machines. Kind of a pyrric victory, there... the damn thing is an x86 binary any way you look at 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 Sun Jul 27 13:47:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA20620 for hackers-outgoing; Sun, 27 Jul 1997 13:47:34 -0700 (PDT) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA20615 for ; Sun, 27 Jul 1997 13:47:32 -0700 (PDT) Received: from hot1.auctionfever.com (slip129-37-195-113.nc.us.ibm.net [129.37.195.113]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id UAA48612 for ; Sun, 27 Jul 1997 20:47:30 GMT From: mouth@ibm.net (John Kelly) To: hackers@FreeBSD.ORG Subject: Re: Modem problems Date: Sun, 27 Jul 1997 20:49:31 GMT Message-ID: <33dbb1b6.318235@smtp-gw01.ny.us.ibm.net> References: <19970726201841.20682@goof.com> <33dd94bb.3095243@smtp-gw01.ny.us.ibm.net> <19970727151851.49300@goof.com> In-Reply-To: <19970727151851.49300@goof.com> X-Mailer: Forte Agent 1.01/16.397 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 NAA20616 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 27 Jul 1997 15:18:51 -0400, you wrote: > I'll yank this POS SB 32 PnP card and try it at irq 5. >Unfortunately, I can't get the damn thing to stay at irq 10 under >FreeBSD. Maybe that could be a solution. I'll try using the >modem at IRQ 9 and see if it works. At that point, I'm not sure >which way to turn. Any thoughts? Thanks for the response. One of my machines had a Soundblaster 16 in it for a while, and every so often, during bootup the BIOS would report a floppy drive failure. I swapped floppy drives, the power supply, even the motherboard trying to figure out what was wrong, but nothing helped. Then one day I took out the Soundblaster, and the problem has since disappeared. Flakey hardware can produce all sorts of strange problems via unwanted feedback, undervoltages, overvoltages, etc. John From owner-freebsd-hackers Sun Jul 27 14:50:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA23373 for hackers-outgoing; Sun, 27 Jul 1997 14:50:21 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA23366; Sun, 27 Jul 1997 14:50:18 -0700 (PDT) Received: from panke.panke.de (anonymous228.ppp.cs.tu-berlin.de [130.149.17.228]) by bsd.fs.bauing.th-darmstadt.de (8.8.6/8.8.5) with ESMTP id XAA05302; Sun, 27 Jul 1997 23:50:14 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id VAA00822; Sun, 27 Jul 1997 21:53:01 +0200 (MET DST) To: John Fieber Cc: "Jonathan M. Bresler" , freebsd-hackers@FreeBSD.ORG Subject: Re: Installing cf files (was Re: Sendmail Problems?) References: From: Wolfram Schneider Date: 27 Jul 1997 21:52:58 +0200 In-Reply-To: John Fieber's message of Sun, 27 Jul 1997 09:46:19 -0500 (EST) Message-ID: Lines: 13 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Fieber writes: > > /usr/src/usr.sbin/sendmail/cf/cf/*.mc > I was just thinking the other day, it would be handy if the cf > directory were installed somewhere so that people (like myself) > who want to brew a new sendmail.cf using m4 don't have to go dig > sendmail out of the source tree to do it. > > Thoughts? Good idea! -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Sun Jul 27 16:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA27756 for hackers-outgoing; Sun, 27 Jul 1997 16:31:03 -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 QAA27750 for ; Sun, 27 Jul 1997 16:30:56 -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 XAA10503; Sun, 27 Jul 1997 23:24:02 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id XAA29470; Sun, 27 Jul 1997 23:24:02 +0100 (BST) Message-Id: <199707272224.XAA29470@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: FreeBSD Technical Reader cc: Dan Janowski , hackers Subject: Re: ipfw divert, transparent proxy In-reply-to: Your message of "Sat, 26 Jul 1997 12:26:27 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jul 1997 23:24:01 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > natd is the tool you are looking for -- unfortunately I was running it on > my machine and it would cause a reboot every 10 to 15 minutes. This was fixed recently in RELENG_2_2 and -current. Check the log for /sys/net/slcompress.c. -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jul 27 16:31:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA27829 for hackers-outgoing; Sun, 27 Jul 1997 16:31:37 -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 QAA27810 for ; Sun, 27 Jul 1997 16:31:31 -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 XAA10510; Sun, 27 Jul 1997 23:27:34 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id XAA29484; Sun, 27 Jul 1997 23:27:34 +0100 (BST) Message-Id: <199707272227.XAA29484@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: FreeBSD Technical Reader cc: "Daniel O'Callaghan" , Dan Janowski , hackers Subject: Re: ipfw divert, transparent proxy In-reply-to: Your message of "Sat, 26 Jul 1997 12:32:31 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jul 1997 23:27:33 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I know I could be banned for life for saying this --- but you could also > use a linux machine and the ipmasquerading built into the kernel for doing > this, there are no equivalent features in FreeBSD and it works much better > than natd (Ipmasquerading is one of the things i miss from linux). Please > forgive me for this sin. Not true. Linux masquerading can not tunnel sockets to internal machines and cannot create RPC based connections. The only thing it has that Charles' code doesn't is CUSeeMe (and I've promised to have a look at that when I can). Anyway, the divert stuff is way cooler too ! -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jul 27 18:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA01989 for hackers-outgoing; Sun, 27 Jul 1997 18:31:02 -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 SAA01918 for ; Sun, 27 Jul 1997 18:28:54 -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 CAA13303; Mon, 28 Jul 1997 02:15:23 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id CAA07484; Mon, 28 Jul 1997 02:15:23 +0100 (BST) Message-Id: <199707280115.CAA07484@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Dan Janowski cc: avalon@coombs.anu.edu.au, kernel@acromail.ml.org, danny@panda.hilink.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw divert, transparent proxy In-reply-to: Your message of "Sun, 27 Jul 1997 11:55:58 EDT." <199707271555.LAA00845@fnur.3skel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jul 1997 02:15:23 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There seems to be some agreement that using divert > sockets is the way to go, but I still am at a loss > for any examples using the mechanism. Does anyone > have any code, snippet or functional, that utilizes > the interface? Reading the kernel code is only a > step away, but an example, even a simple one, would > help. See /usr/src/usr.sbin/natd/samples/natd.test. If you don't run -current, it's available on ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD- current/src..... > Dan > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jul 27 18:33:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02082 for hackers-outgoing; Sun, 27 Jul 1997 18:33:19 -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 SAA02047; Sun, 27 Jul 1997 18:32:05 -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 CAA13296; Mon, 28 Jul 1997 02:13:21 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id CAA07467; Mon, 28 Jul 1997 02:13:21 +0100 (BST) Message-Id: <199707280113.CAA07467@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Wolfram Schneider cc: John Fieber , "Jonathan M. Bresler" , freebsd-hackers@FreeBSD.ORG, Joerg Wunsch Subject: Re: Installing cf files (was Re: Sendmail Problems?) In-reply-to: Your message of "27 Jul 1997 21:52:58 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jul 1997 02:13:20 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > John Fieber writes: > > > /usr/src/usr.sbin/sendmail/cf/cf/*.mc > > I was just thinking the other day, it would be handy if the cf > > directory were installed somewhere so that people (like myself) > > who want to brew a new sendmail.cf using m4 don't have to go dig > > sendmail out of the source tree to do it. > > > > Thoughts? > > Good idea! Hmmmm, I'm sure Joerg has already done this (cc'd). > -- > Wolfram Schneider http://www.apfel.de/~wosch/ -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Jul 27 18:38:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA02244 for hackers-outgoing; Sun, 27 Jul 1997 18:38:35 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA02234 for ; Sun, 27 Jul 1997 18:37:44 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id UAA06632; Sun, 27 Jul 1997 20:42:23 -0500 (CDT) Message-Id: <199707280142.UAA06632@iworks.InterWorks.org> Date: Sun, 27 Jul 1997 20:42:23 -0500 (CDT) From: "Daniel M. Eischen" To: imp@rover.village.org Subject: Re: Adaptec 2940UW Cc: Jeff.Kreska@MCI.Com, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I know of several people who have had problems with the 2940AU. This > is a different board from the 2940U or UW. Some revs of it have lots > of problems with reset and other oddities. Since I don't have one of > these cards, I think that the output from dmesg of the boot probe of > the aha device might not be a bad thing to get too. Right, the AU only has 3 SCBs compared to 16 SCBs (like the 787x/788x based chips). There are also problems with the FIFO counters, but Justin has worked around that in the sequencer code. Another problem that I have seen with these controllers is rebooting into another OS requires a cold reboot. The work around for this is to enable SCAM support in SCSI Select Utilities. There may also be problems with auto-termination. Booting verbose will (I think) show what the driver uses for termination settings. If the driver doesn't get the correct termination settings, just manually set the termination in SCSI Select Utilities. I know I've had termination problems with a couple of machines at work (this with the 2940UW). With UW drives on the wide bus and Ultra enabled, the devices on the narrow bus couldn't properly terminate it. I had to use an inline active terminator on the narrow bus. Neither a Plextor 12-plex CD-ROM or an HP C1599 DAT drive would properly terminate the bus. I tried different cables, but only the addition of the active terminator solved the problem. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Sun Jul 27 18:58:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03068 for hackers-outgoing; Sun, 27 Jul 1997 18:58:09 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA03062 for ; Sun, 27 Jul 1997 18:58:05 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id WAA25980; Sun, 27 Jul 1997 22:04:38 -0400 (EDT) Message-Id: <3.0.32.19970727215623.00b1fa00@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 27 Jul 1997 21:56:28 -0400 To: Sean Eric Fagan , hackers@FreeBSD.ORG From: dennis Subject: Re: SVR4.2MP source code has become available recently? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 09:31 AM 7/27/97 -0700, Sean Eric Fagan wrote: >In article you write: >>I've hear rumors that the source code for SCO UnixWare 2.1.x >>is now available from SCO for $500 for educational >>institutions. >> >>Isn't this interesting as a reference? How do you think? > >No. Under no circumstances should you use it as a reference. This is >dangerous. > >Unless, of course, you don't want to do any FreeBSD development, or, if >you do, you want to get yourself and/or Jordan Hubbard sued for some >intellectual property violation (e.g., copyright or trade secret). HAHAHA This is the joke of modern software "non-disclosure". Do you really think that Jordan is worth enough for SCO to deal with suing? Or any other individual or small company? I love it when a little ISP tells me they will sign a ND if we give them source...thats all I need, a bunch of servers and some modem pools in Moosebreath Montana...which is exactly what I'll get if I have to sue them. Another interesting issue is that states and universities are exempt from many copyright infringement type suits (I forget the exact wording), so giving source to a university is like putting it in skywriting......I doubt if SCO is that stupid, unless they are hoping that some major concern blossoms as a result so that they would have someone worth suing. They know that in todays world if a university has it, the rest of the world will have it soon. You can't sue Cornell because some freshman puts a tarball on the internet "by accident". Dennis Dennis From owner-freebsd-hackers Sun Jul 27 19:35:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA04891 for hackers-outgoing; Sun, 27 Jul 1997 19:35:57 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA04886 for ; Sun, 27 Jul 1997 19:35:55 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id TAA02251 for hackers@FreeBSD.ORG; Sun, 27 Jul 1997 19:35:54 -0700 Date: Sun, 27 Jul 1997 19:35:54 -0700 From: Sean Eric Fagan Message-Id: <199707280235.TAA02251@kithrup.com> To: hackers@FreeBSD.ORG Subject: Re: SVR4.2MP source code has become available recently? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This is the joke of modern software "non-disclosure". Do you really >think that Jordan is worth enough for SCO to deal with suing? Or >any other individual or small company? Yes. If, in fact, SCO believes their trade secrets have been compromised, Jordan makes a wonderful target. And they would *have* to, due to how trade secret protection works. But never let reality get in the way of your amusement, Dennis. >Another interesting issue is that states and universities are exempt >from many copyright infringement type suits (I forget the exact wording), Wrong. States are immune from copyright infringement, due to emminent domain. This has been upheld by the Supreme Court within the past 15 years. (Specifically, someone sued a UCB employee for font copying; the court concluded that, as long as the employee was acting in an official capacity, he was immune, and UCB, being part of the state constitution, was also immune.) Universities in general do not have this protection; Stanford University's only protection is that it has more lawyers than most states. And most state universities do not actually have this protection. >You can't sue Cornell because some freshman puts >a tarball on the internet "by accident". Again: wrong. And also again: don't bother letting reality get in the way of your amusement, Dennis. Sean. From owner-freebsd-hackers Sun Jul 27 19:50:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05631 for hackers-outgoing; Sun, 27 Jul 1997 19:50:57 -0700 (PDT) Received: from mail.be.com (be.be.com [207.113.215.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA05625 for ; Sun, 27 Jul 1997 19:50:54 -0700 (PDT) Received: from localhost by mail.be.com with smtp (Smail3.1.29.1 #1) id m0wsfvd-000oIXC; Sun, 27 Jul 97 19:52 PDT Date: Sun, 27 Jul 1997 19:46:59 -0800 Message-ID: <19970727194659.PM-3fwlm6so@Adam.BeOS> MIME-Version: 1.0 X-Mailer: Adam 1.0 on BeOS Subject: Anyone tried VirtualPC with FreeBSD? From: Jake Hamby To: 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 TAA05626 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just for fun, I tried to boot FreeBSD 2.2.2 from within the VirtualPC emulator for MacOS, which claims to simulate a full Intel Pentium PC at the hardware level. It can run unmodified version of Windows 95, NT, OS/2, and NextStep, and so I assumed it wouldn't have much trouble with FreeBSD. Unfortunately, immediately after loading the kernel, FreeBSD panicked with this error: Fatal trap 1: privileged instruction fault while in kernel mode instruction ptr = 0x8:0xf01b99aa stack ptr = 0x10:0xefbfff38 frame ptr = 0x10:0xefbfff50 code segment = base 0x0, limit 0xfffff type 0x1b = DPL 0, pres 1, def 32 1, grant process eflags = IOPL = 0 current process = 0 () interrupt mask = net tty bio panic: privileged instruction fault Obviously, this is a bug in Connectix's CPU emulator. But I'm curious if anyone could give any information off-hand as to what they might be doing wrong that would trigger such an error from the FreeBSD kernel. Thanks, Jake Hamby From owner-freebsd-hackers Sun Jul 27 20:17:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06548 for hackers-outgoing; Sun, 27 Jul 1997 20:17:22 -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 UAA06543 for ; Sun, 27 Jul 1997 20:17:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA03611; Mon, 28 Jul 1997 12:46:36 +0930 (CST) From: Michael Smith Message-Id: <199707280316.MAA03611@genesis.atrad.adelaide.edu.au> Subject: Re: Anyone tried VirtualPC with FreeBSD? In-Reply-To: <19970727194659.PM-3fwlm6so@Adam.BeOS> from Jake Hamby at "Jul 27, 97 07:46:59 pm" To: jehamby@be.com (Jake Hamby) Date: Mon, 28 Jul 1997 12:46:36 +0930 (CST) Cc: 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 Jake Hamby stands accused of saying: > Just for fun, I tried to boot FreeBSD 2.2.2 from within the VirtualPC > emulator for MacOS, which claims to simulate a full Intel Pentium PC at > the hardware level. It can run unmodified version of Windows 95, NT, > OS/2, and NextStep, and so I assumed it wouldn't have much trouble with > FreeBSD. > > Unfortunately, immediately after loading the kernel, FreeBSD panicked with > this error: > > Fatal trap 1: privileged instruction fault while in kernel mode > > instruction ptr = 0x8:0xf01b99aa Where is this in the kernel? Are you booting an installation disk? If so, which one? Suck the kernel off the disk, and say : nm kernel | sort | less and send us the symbols from around the IP above. > Obviously, this is a bug in Connectix's CPU emulator. But I'm curious if > anyone could give any information off-hand as to what they might be doing > wrong that would trigger such an error from the FreeBSD kernel. Not _necessarily_ "obviously"; it's possible that the emulator just does something "odd" that's upsetting the kernel. > Jake Hamby -- ]] 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 Jul 27 20:21:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06675 for hackers-outgoing; Sun, 27 Jul 1997 20:21:07 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06669 for ; Sun, 27 Jul 1997 20:21:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id UAA05327; Sun, 27 Jul 1997 20:16:14 -0700 (PDT) Message-Id: <199707280316.UAA05327@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Jake Hamby Cc: hackers@freebsd.org Subject: Re: Anyone tried VirtualPC with FreeBSD? Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 27 Jul 1997 20:16:13 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 27 Jul 1997 19:46:59 -0800 Jake Hamby wrote: > Unfortunately, immediately after loading the kernel, FreeBSD panicked with > this error: > > Fatal trap 1: privileged instruction fault while in kernel mode > > instruction ptr = 0x8:0xf01b99aa > stack ptr = 0x10:0xefbfff38 > frame ptr = 0x10:0xefbfff50 > code segment = base 0x0, limit 0xfffff type 0x1b > = DPL 0, pres 1, def 32 1, grant > process eflags = IOPL = 0 > current process = 0 () > interrupt mask = net tty bio > panic: privileged instruction fault > > Obviously, this is a bug in Connectix's CPU emulator. But I'm curious if > anyone could give any information off-hand as to what they might be doing > wrong that would trigger such an error from the FreeBSD kernel. Funny... It boots the NetBSD/i386 kernel just fine... NetBSD, however, incorrectly detects the PCI configuration mode ... we're hoping to address that shortly. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Sun Jul 27 22:54:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11759 for hackers-outgoing; Sun, 27 Jul 1997 22:54:10 -0700 (PDT) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA11743 for ; Sun, 27 Jul 1997 22:53:37 -0700 (PDT) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.5/8.8.5) with SMTP id MAA09616 for ; Mon, 28 Jul 1997 12:54:24 +0700 (NSS) Date: Mon, 28 Jul 1997 12:54:24 +0700 (NSS) From: Max Khon To: hackers@freebsd.org Subject: AMD PCNet/PCI troubles 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, there! We've got fifteen workstations with AMD PCNet/PCI network adapters Linux runs perfectly with this cards, but FreeBSD LANCE driver seems to be quite unstable: Jul 28 12:16:30 ws09 /kernel: Copyright (c) 1992-1997 FreeBSD Inc. Jul 28 12:16:30 ws09 /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jul 28 12:16:30 ws09 /kernel: The Regents of the University of California. All rights reserved. Jul 28 12:16:30 ws09 /kernel: Jul 28 12:16:30 ws09 /kernel: FreeBSD 2.2.2-RELEASE #0: Sat Jun 28 16:14:13 NSS 1997 Jul 28 12:16:30 ws09 /kernel: max@iclub.nsu.ru:/usr/src/sys/compile/iclub Jul 28 12:16:30 ws09 /kernel: CPU: Pentium (99.72-MHz 586-class CPU) Jul 28 12:16:30 ws09 /kernel: Origin = "GenuineIntel" Id = 0x526 Stepping=6 Jul 28 12:16:30 ws09 /kernel: Features=0x1bf Jul 28 12:16:30 ws09 /kernel: real memory = 16777216 (16384K bytes) Jul 28 12:16:30 ws09 /kernel: avail memory = 14270464 (13936K bytes) Jul 28 12:16:30 ws09 /kernel: Probing for devices on PCI bus 0: Jul 28 12:16:30 ws09 /kernel: chip0 rev 2 on pci0:0 Jul 28 12:16:30 ws09 /kernel: chip1 rev 2 on pci0:7:0 Jul 28 12:16:30 ws09 /kernel: chip2 rev 2 on pci0:7:1 Jul 28 12:16:30 ws09 /kernel: vga0 rev 0 int a irq ?? on pci0:8 Jul 28 12:16:30 ws09 /kernel: lnc1 rev 22 int a irq 11 on pci0:19 Jul 28 12:16:30 ws09 /kernel: lnc1: NE2100 (C-LANCE) address 10:00:5a:5b:ee:dc Jul 28 12:16:30 ws09 /kernel: Probing for devices on the ISA bus: Jul 28 12:16:31 ws09 /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 28 12:16:31 ws09 /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 28 12:16:31 ws09 /kernel: ed0: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: ed1: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: fe0: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 28 12:16:31 ws09 /kernel: sio0: type 16550A Jul 28 12:16:31 ws09 /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 28 12:16:31 ws09 /kernel: sio1: type 16550A Jul 28 12:16:31 ws09 /kernel: sio2: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: sio3: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: lpt0 at 0x3bc-0x3c3 irq 7 on isa Jul 28 12:16:31 ws09 /kernel: lpt0: Interrupt-driven port Jul 28 12:16:31 ws09 /kernel: lp0: TCP/IP capable interface Jul 28 12:16:31 ws09 /kernel: lpt1: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: mse0: disabled, not probed. Jul 28 12:16:31 ws09 /kernel: psm0 at 0x60-0x64 irq 12 on motherboard Jul 28 12:16:31 ws09 /kernel: psm0: device ID 0 Jul 28 12:16:31 ws09 /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 28 12:16:31 ws09 /kernel: fdc0: NEC 72065B Jul 28 12:16:31 ws09 /kernel: fd0: 1.44MB 3.5in Jul 28 12:16:32 ws09 /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 28 12:16:32 ws09 /kernel: wdc0: unit 0 (wd0): Jul 28 12:16:32 ws09 /kernel: wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S Jul 28 12:16:32 ws09 /kernel: wdc1: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: bt0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: uha0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: aha0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: aic0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: nca0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: nca1: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: sea0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: wt0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: mcd0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: matcdc0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: scd0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: ie0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: ie1: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: ep0: disabled, not probed. Jul 28 12:16:32 ws09 /kernel: ex0: disabled, not probed. Jul 28 12:16:33 ws09 /kernel: le0: disabled, not probed. Jul 28 12:16:33 ws09 /kernel: lnc0: disabled, not probed. Jul 28 12:16:33 ws09 /kernel: ze0: disabled, not probed. Jul 28 12:16:33 ws09 /kernel: zp0: disabled, not probed. Jul 28 12:16:33 ws09 /kernel: npx0 flags 0x1 on motherboard Jul 28 12:16:33 ws09 /kernel: npx0: INT 16 interface Jul 28 12:16:33 ws09 /kernel: apm0: disabled, not probed. Jul 28 12:16:41 ws09 lpd[118]: restarted Jul 28 12:16:51 ws09 login: ROOT LOGIN (root) ON ttyv0 Jul 28 12:29:31 ws09 su: max to root on /dev/ttyv5 Jul 28 12:35:57 ws09 last message repeated 30 times Jul 28 12:36:54 ws09 last message repeated 57 times Jul 28 12:36:54 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:36:55 ws09 last message repeated 3 times Jul 28 12:36:55 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:36:56 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:36:56 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:28 ws09 last message repeated 31 times Jul 28 12:37:33 ws09 last message repeated 5 times Jul 28 12:37:34 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:34 ws09 last message repeated 2 times Jul 28 12:37:35 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:41 ws09 last message repeated 5 times Jul 28 12:37:41 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:42 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:42 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:46 ws09 last message repeated 3 times Jul 28 12:37:46 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:47 ws09 last message repeated 4 times Jul 28 12:37:47 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:47 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:48 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:48 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:53 ws09 last message repeated 4 times Jul 28 12:37:53 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:54 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:54 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:54 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:55 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:37:55 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:01 ws09 last message repeated 5 times Jul 28 12:38:01 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:02 ws09 last message repeated 2 times Jul 28 12:38:02 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:12 ws09 last message repeated 9 times Jul 28 12:38:12 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:12 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:13 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:13 ws09 /kernel: lnc1: Receive CRC error Jul 28 12:38:13 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted Jul 28 12:38:14 ws09 last message repeated 2 times Jul 28 12:38:14 ws09 /kernel: lnc1: Framming error Jul 28 12:38:45 ws09 last message repeated 31 times /max From owner-freebsd-hackers Mon Jul 28 00:58:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16739 for hackers-outgoing; Mon, 28 Jul 1997 00:58:41 -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 AAA16733 for ; Mon, 28 Jul 1997 00:58:24 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA05486; Mon, 28 Jul 1997 17:27:14 +0930 (CST) From: Michael Smith Message-Id: <199707280757.RAA05486@genesis.atrad.adelaide.edu.au> Subject: Re: AMD PCNet/PCI troubles In-Reply-To: from Max Khon at "Jul 28, 97 12:54:24 pm" To: max@iclub.nsu.ru (Max Khon) Date: Mon, 28 Jul 1997 17:27:13 +0930 (CST) Cc: 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 Max Khon stands accused of saying: > > We've got fifteen workstations with AMD PCNet/PCI network adapters > Linux runs perfectly with this cards, but FreeBSD LANCE driver seems to > be quite unstable: Is it "unstable", or is it just verbose in its complaining? > Jul 28 12:38:13 ws09 /kernel: lnc1: Receive CRC error > Jul 28 12:38:14 ws09 /kernel: lnc1: Framming error These two indicate that there's something bad going on with either your cabling or a card that's generating bad signal. > Jul 28 12:38:13 ws09 /kernel: lnc1: Babble error - more than 1519 bytes transmitted This is directly reporting an error from the Lance. It doesn't look too good. 8( I don't have access to a current Linux kernel tree (as getting such an animal requires real effort, as opposed to the FreeBSD tree 8), so I can't check offhand and see if they actually report these errors to the console. -- ]] 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 Jul 28 01:17:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA17460 for hackers-outgoing; Mon, 28 Jul 1997 01:17:03 -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 BAA17454 for ; Mon, 28 Jul 1997 01:17:00 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA05659; Mon, 28 Jul 1997 17:46:08 +0930 (CST) From: Michael Smith Message-Id: <199707280816.RAA05659@genesis.atrad.adelaide.edu.au> Subject: Re: utmp/wtmp interface In-Reply-To: <199707222247.IAA00521@labs.usn.blaze.net.au> from David Nugent at "Jul 23, 97 08:47:07 am" To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Mon, 28 Jul 1997 17:46:08 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, 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 David Nugent stands accused of saying: > [wtmp] > > Actually, I would have suggested a textual format, but I thought that > > the screams would be audible from here. If you think it's a goer, you > > have my absolute support. > > Given the space savings, I can't see any reason for it NOT to be > text. All but a couple of the fields are text anyway. :) I recently > played with a 13mb wtmp which reduced down to 4.8mb when converted > to variable-length text (this was a 8-character username system too), > which should give you some idea of the potential savings. Eep. Pretty convincing. > This will make it harder for things like last(1) to page back > through the file from the end, but life is sometimes tough. Besides, > last(1) will use the API, which will handle this transparently in any > case, including the buffering. Yup. Sounds good. -- ]] 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 Jul 28 01:34:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18245 for hackers-outgoing; Mon, 28 Jul 1997 01:34:46 -0700 (PDT) Received: from dorotech.fr (mail.dorotech.fr [193.56.144.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA18238 for ; Mon, 28 Jul 1997 01:34:41 -0700 (PDT) Received: from fritz.UUCP (uucp@localhost) by dorotech.fr (8.6.12/8.6.10) with UUCP id KAA21163; Mon, 28 Jul 1997 10:37:16 +0200 Received: from pchot4 by fritz.dorotech.fr (4.1/SMI-4.1) id AA02458; Mon, 28 Jul 97 10:15:52 +0200 Message-Id: <33DC5875.167EB0E7@dorotech.fr> Date: Mon, 28 Jul 1997 08:29:41 +0000 From: Patrice BLEUZE X-Mailer: Mozilla 2.0 (X11; I; FreeBSD 2.2.1-RELEASE i386) Mime-Version: 1.0 To: Vinay Bannai Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Where is cdevsw_add ?? References: <199707251829.LAA19660@agni.nuko.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Vinay Bannai wrote: > > Hi folks > > I am trying to attach the upper half of my device driver to the cdevsw > struct and most of the device drivers make a call to cdevsw_add() or > bdevsw_add() to be included in the struct. Despite my etags and searches, > I could not locate where cdevsw_add() or bdevsw_add() is defined? Is it a > macro or a function?? > > Thanks > Vinay > -- > Vinay Bannai E-mail: vinay@agni.nuko.com > (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay This is a macro. See /usr/include/sys/conf.h. pbl From owner-freebsd-hackers Mon Jul 28 02:24:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20408 for hackers-outgoing; Mon, 28 Jul 1997 02:24:29 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20401 for ; Mon, 28 Jul 1997 02:24:24 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id FAA15748 for ; Mon, 28 Jul 1997 05:29:23 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Mon, 28 Jul 1997 05:29:23 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: freebsd-hackers@FreeBSD.ORG Subject: SMP? In-Reply-To: <33DC5875.167EB0E7@dorotech.fr> 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 a couple of questions about SMP, what boards do i have to watch out for, not working? will the SMP kernel work with cyrix/AMD chips? I was recently considering, just to experiment (it would kill my budget though) to buy my roomate's P150 chip (real bargain) then buy a dual pentium mb plus another P150. The whole thing will cost me almost 400$, is it worth it? The thing is I just read that dual pentiums are nothing compared to dual pentium pros, is this true (especially running at 150mhz) What kind of performance increase could i expect over a single P150? Last general question, is the SMP kernel stable as of now and are the same drivers and ports available for it? Thanks in advance, Alfred perlsta@sunyit.edu From owner-freebsd-hackers Mon Jul 28 04:49:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA24925 for hackers-outgoing; Mon, 28 Jul 1997 04:49:43 -0700 (PDT) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA24918 for ; Mon, 28 Jul 1997 04:49:32 -0700 (PDT) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.5/8.8.5) with SMTP id SAA10939; Mon, 28 Jul 1997 18:48:58 +0700 (NSS) Date: Mon, 28 Jul 1997 18:48:58 +0700 (NSS) From: Max Khon To: Michael Smith cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/PCI troubles In-Reply-To: <199707280757.RAA05486@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 Mon, 28 Jul 1997, Michael Smith wrote: > I don't have access to a current Linux kernel tree (as getting such an > animal requires real effort, as opposed to the FreeBSD tree 8), so I can't > check offhand and see if they actually report these errors to the console. but under FreeBSD (unlike Linux) networking sometimes is very slow (~30-50K/s via ftp) /max From owner-freebsd-hackers Mon Jul 28 04:55:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25672 for hackers-outgoing; Mon, 28 Jul 1997 04:55:51 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25652 for ; Mon, 28 Jul 1997 04:55:45 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.6/8.8.5) with SMTP id NAA22936; Mon, 28 Jul 1997 13:57:01 +0200 (CEST) Date: Mon, 28 Jul 1997 13:57:01 +0200 (CEST) From: Andrzej Bialecki To: Ollivier Robert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Nvi and locale In-Reply-To: <19970726113734.28396@keltia.freenix.fr> 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, 26 Jul 1997, Ollivier Robert wrote: > According to Andrzej Bialecki: > > setenv LANG C > > setenv LC_CTYPE lt_LN.ISO-8859-1 <- from nvi docs (why ???) > > Try using > > setenv LANG lt_LN.ISO_8859-1 Thanks. This works. However, in the meantime I started to read the manpages and the sources for mklocale(1) (perhaps I should begin with it :-). Now, I have prepared the complete Polish locale and the vi message catalog in Polish. Whom should I send it to? BTW. I'm using Polish screen font and kbdmap as well (otherwise the whole issue would be meaningless). I think it would be nice to include them as an option during installation and after. I can send them too. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Mon Jul 28 05:06:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27072 for hackers-outgoing; Mon, 28 Jul 1997 05:06:37 -0700 (PDT) Received: from server.netplus.com.br (root@[200.247.23.97]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27063 for ; Mon, 28 Jul 1997 05:06:32 -0700 (PDT) Received: from sergio.lenzi (dial11.netplus [192.168.9.18]) by server.netplus.com.br (8.8.5/8.8.5) with ESMTP id JAA25389; Mon, 28 Jul 1997 09:09:26 GMT Received: from localhost (lenzi@localhost) by sergio.lenzi (8.8.5/8.8.5) with SMTP id JAA07229; Mon, 28 Jul 1997 09:06:47 GMT X-Authentication-Warning: sergio.lenzi: lenzi owned process doing -bs Date: Mon, 28 Jul 1997 09:06:47 +0000 (GMT) From: "Lenzi, Sergio" X-Sender: lenzi@sergio To: FreeBSD Technical Reader cc: "Daniel O'Callaghan" , Dan Janowski , hackers Subject: Re: ipfw divert, transparent proxy 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, 26 Jul 1997, FreeBSD Technical Reader wrote: > > I know I could be banned for life for saying this --- but you could also > use a linux machine and the ipmasquerading built into the kernel for doing > this, there are no equivalent features in FreeBSD and it works much better > than natd (Ipmasquerading is one of the things i miss from linux). Please > forgive me for this sin. > Hello all, I use FreeBSD 2.2.X and ip divert options on the firewall, tied with a program (natd) network address translator daemon ant it works great I use it on a ISP ant all my clientes use net 192.168.x.x All have full internet access (telnet,ftp,www,rpc,irc...) the whole thing works great. wihthout any linux code... I am very satisfied with natd. Sergio Lenzi. Unix consult. From owner-freebsd-hackers Mon Jul 28 05:10:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27924 for hackers-outgoing; Mon, 28 Jul 1997 05:10:32 -0700 (PDT) Received: from server.netplus.com.br (root@[200.247.23.97]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27887 for ; Mon, 28 Jul 1997 05:10:26 -0700 (PDT) Received: from sergio.lenzi (dial11.netplus [192.168.9.18]) by server.netplus.com.br (8.8.5/8.8.5) with ESMTP id JAA25508; Mon, 28 Jul 1997 09:13:40 GMT Received: from localhost (lenzi@localhost) by sergio.lenzi (8.8.5/8.8.5) with SMTP id JAA07245; Mon, 28 Jul 1997 09:12:06 GMT X-Authentication-Warning: sergio.lenzi: lenzi owned process doing -bs Date: Mon, 28 Jul 1997 09:12:06 +0000 (GMT) From: "Lenzi, Sergio" X-Sender: lenzi@sergio To: Dan Janowski cc: avalon@coombs.anu.edu.au, kernel@acromail.ml.org, danny@panda.hilink.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: ipfw divert, transparent proxy In-Reply-To: <199707271555.LAA00845@fnur.3skel.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 Sun, 27 Jul 1997, Dan Janowski wrote: > > There seems to be some agreement that using divert > sockets is the way to go, but I still am at a loss > for any examples using the mechanism. Does anyone > have any code, snippet or functional, that utilizes > the interface? Reading the kernel code is only a > step away, but an example, even a simple one, would > help. > There is a "package" (natd_1.8.tgz) at ftp://netplus.com.br/packages install the package and use man natd to see the example. It works great with that ISP that uses ONLY ONE IP (200.247.23.97). Hope this can help, Sergio Lenzi. Unix consult. From owner-freebsd-hackers Mon Jul 28 05:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA29542 for hackers-outgoing; Mon, 28 Jul 1997 05:22:08 -0700 (PDT) Received: from beta.mcit.com (beta.mcit.com [199.249.19.143]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29537 for ; Mon, 28 Jul 1997 05:22:02 -0700 (PDT) Received: from omzrelay.mcit.com (omzrelay.mcit.com [166.37.204.49]) by beta.mcit.com (8.8.6/) with ESMTP id HAA21992; Mon, 28 Jul 1997 07:21:31 -0500 (CDT) Received: from pop3a.mail.mci.com (pop3a.mail.mci.com [166.37.172.2]) by omzrelay.mcit.com (8.8.5/) with ESMTP id HAA04459; Mon, 28 Jul 1997 07:21:30 -0500 (CDT) Received: from rip01643 ([166.35.248.180]) by pop3a.mail.mci.com (Post.Office MTA Undefined release Undefined ID# 1-123U25000L1S10) with ESMTP id AAA6301; Mon, 28 Jul 1997 08:21:30 -0400 Message-ID: <33DC8E66.37223549@mci.com> Date: Mon, 28 Jul 1997 07:19:50 -0500 From: "Jeff Kreska" Organization: MCI X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Adaptec 2940UW X-Priority: 3 (Normal) References: <18546.869857590@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: > > Is anybody working on resolving the problems with the Adapatec > 2940. It > > appears that the problems exist in all tree's. I have personaly > used > > the 2.1, latest 2.2snap, and 3.0snap with none of them working 100%. > > Odd - I'm having no problems with my 2940UWs at all. What was > the PR#? > Critical problems o [1997/07/11] kern/4076 Adaptec 2940 and non-wide devices This is the one I submitted, I can't rember the specifics of the dmesg output. I will try and capture the dmesg output and post it for suggestions -- Regards, Jeff mailto:jeff.kreska@mci.com From owner-freebsd-hackers Mon Jul 28 07:15:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA08549 for hackers-outgoing; Mon, 28 Jul 1997 07:15:26 -0700 (PDT) Received: from mail.wup.de ([149.237.200.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA08535 for ; Mon, 28 Jul 1997 07:15:14 -0700 (PDT) Received: (from root@localhost) by mail.wup.de (8.8.6/8.8.6) id QAA12479; Mon, 28 Jul 1997 16:14:55 +0200 (CEST) Message-ID: <19970728161455.30081@wup.de> Date: Mon, 28 Jul 1997 16:14:55 +0200 From: Andreas Klemm To: hackers@FreeBSD.org Subject: inn problem, don't receive news Reply-To: andreas@FreeBSD.org, andreas.klemm@wup.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I'm struggeling with inn 1.5.1 on my companies FreeBSD Gateway machine (FreeBSD-2.2-STABLE). I only have experience with inn getting news via UUCP. This worked fine so far. But now I deceided, to get news faster, so our internet service provider and I tried to change the delivery to immediate delivery. At my site I added his site (news.technet.net) to my sites (news.wup.de) hosts.nntp file: ## hosts.nntp - names and addresses that feed us news news.technet.net: For outgoing - which is currently working well here - I changed the entries in the newsfeeds file from: # meservb/ddfservb.technet.net,meservb.technet.net,news.technet.net\ # :*,!wup*,!junk,!local*,!control/!foo\ # :Tf,Wfb: to technet/ddfservb.technet.net,meservb.technet.net,news.technet.net\ :*,!wup*,!junk,!local*,!control/!foo\ :Tf,Wnm: My nntpsend.ctl file looks like this: technet:news.technet.net:2m: My crontab entry checks for news and deliveres every 5 Minutes ... 5,10,15,20,25,30,35,40,45,50,55,0 * * * * /usr/local/news/bin/nntpsend technet news.technet.net The only thing I want to now is, what might be the reason, that I don't receive any news from him ??? What else do I have to configure, that he is allowed to send me news using nntpsend (Netscape news server) ??? I see no debug/log file, that indicates an error.... Any thoughts ??? Andreas Klemm /// From owner-freebsd-hackers Mon Jul 28 07:43:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA10147 for hackers-outgoing; Mon, 28 Jul 1997 07:43:06 -0700 (PDT) Received: from houseofduck.dyn.ml.org (ts002d19.sal-ut.concentric.net [206.173.156.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA10141; Mon, 28 Jul 1997 07:43:01 -0700 (PDT) Received: (from shaggy@localhost) by houseofduck.dyn.ml.org (8.8.5/8.7.3) id IAA13917; Mon, 28 Jul 1997 08:42:41 -0600 (MDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970728161455.30081@wup.de> Date: Mon, 28 Jul 1997 08:40:43 -0600 (MDT) Organization: Shaggy Enterprises From: Joshua Fielden To: andreas@FreeBSD.ORG, andreas.klemm@wup.de Subject: RE: inn problem, don't receive news Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk just as a heads-up, 1.5 was the version found to have a security hole in it... http://www.computerworld.com/news/index.html#970725SECURITY has the story On 28-Jul-97 Andreas Klemm wrote: >Hi ! > >I'm struggeling with inn 1.5.1 on my companies FreeBSD >Gateway machine (FreeBSD-2.2-STABLE). > >I only have experience with inn getting news via UUCP. >This worked fine so far. But now I deceided, to get >news faster, so our internet service provider and I >tried to change the delivery to immediate delivery. > >At my site I added his site (news.technet.net) to >my sites (news.wup.de) hosts.nntp file: > >## hosts.nntp - names and addresses that feed us news >news.technet.net: > >For outgoing - which is currently working well here - >I changed the entries in the newsfeeds file from: ># meservb/ddfservb.technet.net,meservb.technet.net,news.technet.net\ ># :*,!wup*,!junk,!local*,!control/!foo\ ># :Tf,Wfb: > >to > >technet/ddfservb.technet.net,meservb.technet.net,news.technet.net\ > :*,!wup*,!junk,!local*,!control/!foo\ > :Tf,Wnm: > >My nntpsend.ctl file looks like this: >technet:news.technet.net:2m: > >My crontab entry checks for news and deliveres every 5 Minutes ... > >5,10,15,20,25,30,35,40,45,50,55,0 * * * * /usr/local/news/bin/nntpsend >technet news.technet.net > >The only thing I want to now is, what might be the reason, that >I don't receive any news from him ??? > >What else do I have to configure, that he is allowed to send me news >using nntpsend (Netscape news server) ??? > >I see no debug/log file, that indicates an error.... > >Any thoughts ??? > > > Andreas Klemm /// > -- Joshua Fielden, shag@concentric.net SCSI is *not* magic. There are many technical reasons why it's occasionally nessicary to sacrifice a small goat to your SCSI chain. From owner-freebsd-hackers Mon Jul 28 07:52:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA10686 for hackers-outgoing; Mon, 28 Jul 1997 07:52:50 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA10681 for ; Mon, 28 Jul 1997 07:52:46 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id QAA00892 for ; Mon, 28 Jul 1997 16:52:40 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id QAA04105 for freebsd-hackers@FreeBSD.ORG; Mon, 28 Jul 1997 16:52:34 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id MAA03036; Mon, 28 Jul 1997 12:00:46 +0200 (CEST) Message-ID: <19970728120045.44434@keltia.freenix.fr> Date: Mon, 28 Jul 1997 12:00:45 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: SMP? References: <33DC5875.167EB0E7@dorotech.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Alfred Perlstein on Mon, Jul 28, 1997 at 05:29:23AM +0000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ don't forget there is a freebsd-smp list ] According to Alfred Perlstein: > I have a couple of questions about SMP, what boards do i have to watch > out for, not working? will the SMP kernel work with cyrix/AMD chips? See for details. It won't work on Cyrix/AMD processors because they don't use the same APIC as Intel. There is a document about OpenPIC for these processors but only the AMD 640 chipset implement it (to my knowledge). For now, SMP == Intel. > is it worth it? The thing is I just read that dual pentiums are nothing > compared to dual pentium pros, is this true (especially running at 150mhz) You should be able to run your P150 at 2.5x 66 MHz (== 166 MHz) without problem. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hackers Mon Jul 28 08:14:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA11743 for hackers-outgoing; Mon, 28 Jul 1997 08:14:46 -0700 (PDT) Received: from sunny.wup.de ([149.237.200.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA11732 for ; Mon, 28 Jul 1997 08:14:30 -0700 (PDT) Received: (from andreas@localhost) by sunny.wup.de (8.8.6/8.8.6) id RAA07089; Mon, 28 Jul 1997 17:10:01 +0200 (MET DST) Message-ID: <19970728171000.50356@sunny.wup.de> Date: Mon, 28 Jul 1997 17:10:00 +0200 From: Andreas Klemm To: Joshua Fielden Cc: hackers@FreeBSD.ORG Subject: Re: inn problem, don't receive news References: <19970728161455.30081@wup.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Joshua Fielden on Mon, Jul 28, 1997 at 08:40:43AM -0600 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Jul 28, 1997 at 08:40:43AM -0600, Joshua Fielden wrote: > just as a heads-up, 1.5 was the version found to have a security hole > in it... Which should be fixed in 1.5.1 ... or am I wrong ? -- aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-hackers Mon Jul 28 08:28:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA12343 for hackers-outgoing; Mon, 28 Jul 1997 08:28:38 -0700 (PDT) Received: from houseofduck.dyn.ml.org (ts002d19.sal-ut.concentric.net [206.173.156.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA12337 for ; Mon, 28 Jul 1997 08:28:35 -0700 (PDT) Received: (from shaggy@localhost) by houseofduck.dyn.ml.org (8.8.5/8.7.3) id JAA14055; Mon, 28 Jul 1997 09:27:07 -0600 (MDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970728171000.50356@sunny.wup.de> Date: Mon, 28 Jul 1997 09:26:40 -0600 (MDT) Organization: Shaggy Enterprises From: Joshua Fielden To: Andreas Klemm Subject: Re: inn problem, don't receive news Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The article specified 1.6 as the "fixed" version. On 28-Jul-97 Andreas Klemm wrote: >On Mon, Jul 28, 1997 at 08:40:43AM -0600, Joshua Fielden wrote: >> just as a heads-up, 1.5 was the version found to have a security >hole >> in it... > >Which should be fixed in 1.5.1 ... or am I wrong ? > >-- >aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH >Andreas Klemm ___/\/\/ - Support Unix - -- Joshua Fielden, shag@concentric.net SCSI is *not* magic. There are many technical reasons why it's occasionally nessicary to sacrifice a small goat to your SCSI chain. From owner-freebsd-hackers Mon Jul 28 08:45:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA13421 for hackers-outgoing; Mon, 28 Jul 1997 08:45:18 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA13409 for ; Mon, 28 Jul 1997 08:45:13 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id RAA01132 for ; Mon, 28 Jul 1997 17:45:10 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id RAA04797 for hackers@FreeBSD.ORG; Mon, 28 Jul 1997 17:44:52 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id RAA05467; Mon, 28 Jul 1997 17:33:28 +0200 (CEST) Message-ID: <19970728173328.50083@keltia.freenix.fr> Date: Mon, 28 Jul 1997 17:33:28 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: inn problem, don't receive news References: <19970728161455.30081@wup.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <19970728161455.30081@wup.de>; from Andreas Klemm on Mon, Jul 28, 1997 at 04:14:55PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Andreas Klemm: > I see no debug/log file, that indicates an error.... What does he have in his log files for you ? Did he setup a crontab entry to send you news ? What does the screen show when he does a "telnet your.machine 119" ? He should see something like this: 200 keltia.frmug.fr.net InterNetNews server INN 1.5.1 17-Dec-1996 ready not NNRPD ! -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hackers Mon Jul 28 09:31:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA16046 for hackers-outgoing; Mon, 28 Jul 1997 09:31:19 -0700 (PDT) Received: from mexico.brainstorm.eu.org (mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA16041 for ; Mon, 28 Jul 1997 09:31:14 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id SAA01495 for ; Mon, 28 Jul 1997 18:31:11 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id SAA05449 for hackers@FreeBSD.ORG; Mon, 28 Jul 1997 18:30:46 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id RAA05602; Mon, 28 Jul 1997 17:48:56 +0200 (CEST) Message-ID: <19970728174856.53042@keltia.freenix.fr> Date: Mon, 28 Jul 1997 17:48:56 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: inn problem, don't receive news References: <19970728161455.30081@wup.de> <19970728171000.50356@sunny.wup.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <19970728171000.50356@sunny.wup.de>; from Andreas Klemm on Mon, Jul 28, 1997 at 05:10:00PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Andreas Klemm: > Which should be fixed in 1.5.1 ... or am I wrong ? No, you're right. The hole fixed in 1.6b2 (soon to be 1.6b3 I think) is a very minor one and 1.6* is simply too buggy for production servers. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hackers Mon Jul 28 10:36:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20042 for hackers-outgoing; Mon, 28 Jul 1997 10:36:53 -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 KAA20036 for ; Mon, 28 Jul 1997 10:36:50 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA01313; Mon, 28 Jul 1997 10:34:05 -0700 From: Terry Lambert Message-Id: <199707281734.KAA01313@phaeton.artisoft.com> Subject: Re: SVR4.2MP source code has become available recently? To: dennis@etinc.com (dennis) Date: Mon, 28 Jul 1997 10:34:04 -0700 (MST) Cc: sef@Kithrup.COM, hackers@FreeBSD.ORG In-Reply-To: <3.0.32.19970727215623.00b1fa00@etinc.com> from "dennis" at Jul 27, 97 09:56:28 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 > >No. Under no circumstances should you use it as a reference. This is > >dangerous. > > > >Unless, of course, you don't want to do any FreeBSD development, or, if > >you do, you want to get yourself and/or Jordan Hubbard sued for some > >intellectual property violation (e.g., copyright or trade secret). > > > HAHAHA > > This is the joke of modern software "non-disclosure". Do you really > think that Jordan is worth enough for SCO to deal with suing? USL thought so, when they sent a "cease and desist" letter to all of the various principle developers in the BSD camps when they went after UCB for Net/2. Also, consider that beating Jordan up legally is a lot easier than beating up, say, MIT. And a decision against Jordan, if he appealed it and lost again, would be binding against MIT. They'd have to assume that MIT wouldn't jump in with Amicus Curie, and that Jordan would be stupid enough to not seek outside help (Jordan's not that dumb). But yes, he would be an attractive target of oportunity. > Or any other individual or small company? Yes, as the other people who got the letters can attest. As I can attest, when I marched down to Mike DeFazio's office (then VP in charge of Novell USG) and fought tooth and nail, risking livelihood and life savings, and dragging Ray Noorda into the fray, to get them to drop the damn lawsuit. > I love it when a little ISP tells me they will sign a ND if we > give them source...thats all I need, a bunch of servers and some > modem pools in Moosebreath Montana...which is exactly what I'll > get if I have to sue them. The issue here is "due dilligence". You would have to sue *anyone* who disclosed, period, to show that you were protecting your trade secrets. Otherwise you lose them. The issue as to whether or not USL had trade secrets was much more easily proven against a small company with little capitol; it was no wonder that BSDI dragged UCB into the fray by claiming them as path-of-disclosure. > Another interesting issue is that states and universities are exempt > from many copyright infringement type suits (I forget the exact wording), > so giving source to a university is like putting it in skywriting......I > doubt if SCO is that stupid, unless they are hoping that some major concern > blossoms as a result so that they would have someone worth suing. > They know that in todays world if a university has it, the rest of the world > will have it soon. You can't sue Cornell because some freshman puts > a tarball on the internet "by accident". This is wrong. The wording you are looking for is "fair use". Patents are allowed to be used for research purposes. As far as copyrights are concerned, "fair use" only applies to excerpting the material for educational purposes, and not to providing it in any form for any other reason. BTW: fair use applies equally well to commercial businesses with internal training programs, or who wish to use the information as example or whatever else in a board meeting. As far as university disclosure: a university is just as subject to the terms of a license contract as any other legal entity which enters into the contract. The only potential difference for a university is it's governmental ties. Which is why you (or any sane vendor) sites DFARS rights restrictions in their copyright notice, and again in their license agreement. Contact the SPA for more information; I've had to research this subject in incredible detail for two small software companies, and the SPA has all of the information required. 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 Jul 28 10:40:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20273 for hackers-outgoing; Mon, 28 Jul 1997 10:40: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 KAA20267 for ; Mon, 28 Jul 1997 10:40:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA01326; Mon, 28 Jul 1997 10:38:32 -0700 From: Terry Lambert Message-Id: <199707281738.KAA01326@phaeton.artisoft.com> Subject: Re: AMD PCNet/PCI troubles To: max@iclub.nsu.ru (Max Khon) Date: Mon, 28 Jul 1997 10:38:32 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: from "Max Khon" at Jul 28, 97 06:48:58 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 don't have access to a current Linux kernel tree (as getting such an > > animal requires real effort, as opposed to the FreeBSD tree 8), so I can't > > check offhand and see if they actually report these errors to the console. > > but under FreeBSD (unlike Linux) networking sometimes is very slow > (~30-50K/s via ftp) In combination with the babble error, I suspect you are either on the wrong IRQ, or you have another noise source on the IRQ: IRQ 2: Check to see if the video card is sending vertical retrace interrupts. IRQ 5: You have a sound card. You can not share interrupts with ISA cards. Period. IRQ 7: Garbage interrupt. Don't use IRQ 7 for anything other than the parallel printer port. 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 Jul 28 10:45:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20463 for hackers-outgoing; Mon, 28 Jul 1997 10:45:06 -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 KAA20442 for ; Mon, 28 Jul 1997 10:44:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA01338; Mon, 28 Jul 1997 10:43:18 -0700 From: Terry Lambert Message-Id: <199707281743.KAA01338@phaeton.artisoft.com> Subject: Re: utmp/wtmp interface To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 28 Jul 1997 10:43:18 -0700 (MST) Cc: davidn@labs.usn.blaze.net.au, msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707280816.RAA05659@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 28, 97 05:46: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 > > > Actually, I would have suggested a textual format, but I thought that > > > the screams would be audible from here. If you think it's a goer, you > > > have my absolute support. > > > > Given the space savings, I can't see any reason for it NOT to be > > text. All but a couple of the fields are text anyway. :) I recently > > played with a 13mb wtmp which reduced down to 4.8mb when converted > > to variable-length text (this was a 8-character username system too), > > which should give you some idea of the potential savings. > > Eep. Pretty convincing. > > > This will make it harder for things like last(1) to page back > > through the file from the end, but life is sometimes tough. Besides, > > last(1) will use the API, which will handle this transparently in any > > case, including the buffering. > > Yup. Sounds good. I suggest that you provide either a fixed lenth record format, or a fixed length header containing an index. Without an index, a large utmp/wtmp would be unbearably slow. The way it works now, multiplying the record number by the size of the struct keeps it happy. As an alternative, I think it would be nice to have an index prefixed block compressed mmap(). The RAM image would be uncompressed and accessed normally as an mmap'ed file, but the file acting as the backing store would be compressed. This would also be usedful for standard file compression, if you had a bit in the inode to mark the thing; otherwise, and mmap() flag is a good first cut. 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 Jul 28 11:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA23204 for hackers-outgoing; Mon, 28 Jul 1997 11:31:36 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23194 for ; Mon, 28 Jul 1997 11:31:30 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id TAA26460; Mon, 28 Jul 1997 19:31:05 +0100 (BST) Date: Mon, 28 Jul 1997 19:31:03 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: MAX physical memory for FreeBSD ? In-Reply-To: <199707220814.BAA12568@implode.root.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 Tue, 22 Jul 1997, David Greenman wrote: > >> There isn't any specific limit, but some kernel parameters need to be > >> tweaked before more than 256MB can be used. > > > >Which? We have a machine (a root name server) that needs to be brought > >up to 512 MB urgently. > > Ugh. Actually, the kernel virtual address space must be increased and this > requires, in addition to changing some kernel parameters (which are hardcoded > in a couple of source files), that you do a "make world" to fix certain > kernel start address assumptions that are in some of the system utilities. > Patches attached. Note that the process limit increases aren't strictly > necessary, but are probably desired. -- message from the person applying the patches :-( -------------------- > > FreeBSD 2.2.2-RELEASE #0: Tue Jul 29 02:32:20 BST 1997 > > gordon@kg1.uk1.vbc.net:/usr/src/sys/compile/NS > > CPU: Pentium (132.96-MHz 586-class CPU) > > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > > Features=0x3bf > > real memory = 402653184 (393216K bytes) > > avail memory = 386772992 (377708K bytes) > > > > Any idea of what version of freebsd these patches were applied to? > > I believe that whatever info I had I sent you. Well, after applying the patches, I now get: panic: bouce memory out of range during boot. ------------------------------------------------------------------------ Any ideas ?? -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Mon Jul 28 11:49:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24275 for hackers-outgoing; Mon, 28 Jul 1997 11:49:46 -0700 (PDT) Received: from zeus.carroll.com (zeus.carroll.com [199.224.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24270 for ; Mon, 28 Jul 1997 11:49:43 -0700 (PDT) Received: from apollo.carroll.com [199.224.10.3] by zeus.carroll.com with ESMTP (8.8.5/0) id OAA19613; Mon, 28 Jul 1997 14:49:42 -0400 Received: by apollo.carroll.com (8.8.5) is OAA07942; Mon, 28 Jul 1997 14:49:41 -0400 Date: Mon, 28 Jul 1997 14:49:38 -0400 From: Jim Carroll To: freebsd-hackers@freebsd.org Subject: make boot.flp FIXED! 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 Several weeks ago I embarked on what I thought was a simple task; to make a boot floppy, with a custom version of the operating system. It turns out, this is not so simple. I believe I now have a working Makefile that anyone can use to re-create either the standard boot OS, or to create their own (I needed a version of the OS with the Iomega parallel Zip drive at boot time). There were basically 4 changes that needed to be made. I have included a description of the changes here, and a Makefile diff output below. 1. changed /R to ${RR} macro. This was a consistancy change (consistant with the ${RD} macro), to permit sending the output somewhere other than to the root of the filesystem. Without changing this to a macro, the /R directory (which is quite large upon completion) would go to /. 2. change doMFSKERN target to work the the KERNELS? macro defined at top of makefile. By forcing doMFSKERN to use the KERNELS macro, you can define which custom OS to build. 3. change release.8 to get device definitions from /dev instead of ${RD}/trees/bin/dev. I spent alot of time agonizing over this one. Somehow release.8 expects the target directory ${RD}/trees.bin/dev to get created with devices from /dev, but I could not figure out where this was supposed to happen. In any event, since this directory is built from /dev, I saw no harm in going to the "horeses mouth". 4. added custom.floppy target to handle the details of building a floppy OS from scratch assuming no other make tages from the /usr/src/release makefile were first built. To use the custom.floppy (which defaults to GENERIC), you must first: cd /usr/src make world (go away for about 12-hours) After that: cd /usr/src/release vi Makefile Be sure to set: BUILDNAME, CHROOTDIR, RELEASETAG, RR Here are my settings (to create 2.2.1 generic release) BUILDNAME=2.2-RELEASE CHROOTDIR=/var/junk/release RELEASETAG=RELENG_2_2_1_RELEASE RR=/var/R make custom.floppy On a 486/133-16MB RAM, the make takes about 2 hours. I have included the output from a diff of the new Makefile from the distribution Makefile: diff -e Makefile.old Makefile.new Yeilds: 56,58c56,59 < RD= /R/stage < FD= /R/ftp < CD= /R/cdrom --- > RR= /var/R > RD= ${RR}/stage > FD= ${RR}/ftp > CD= ${RR}/cdrom 143c144 < echo "export RELEASEDIR=/R" >> ${CHROOTDIR}/mk --- > echo "export RELEASEDIR=${RR}" >> ${CHROOTDIR}/mk 178c179,196 < # Clean out /R and make the directory structure. --- > custom.floppy: > .if !defined(CHROOTDIR) || !defined(BUILDNAME) > @echo "To make a release you must set CHROOTDIR and BUILDNAME" && false > .endif > .if exists(${CHROOTDIR}) > chflags -R noschg ${CHROOTDIR}/. > -rm -rf ${CHROOTDIR} > .endif > -mkdir -p ${CHROOTDIR} > cd ${.CURDIR}/../etc && ${MAKE} distrib-dirs DESTDIR=${CHROOTDIR} > cd ${.CURDIR}/../etc && ${MAKE} distribution DESTDIR=${CHROOTDIR} > cd ${.CURDIR}/.. && ${MAKE} install DESTDIR=${CHROOTDIR} NOMAN=1 > ${MAKE} release.1 > ${MAKE} release.2 > ${MAKE} boot.flp > > > # Clean out ${RR} and make the directory structure. 180,187c198,205 < -mkdir /R < chflags -R noschg /R/. < rm -rf /R/* < mkdir ${RD} < mkdir ${RD}/floppies < mkdir ${RD}/trees < mkdir ${RD}/dists < mkdir ${RD}/kernels --- > -mkdir ${RR} > chflags -R noschg ${RR}/. > rm -rf ${RR}/* > mkdir -p ${RD} > mkdir -p ${RD}/floppies > mkdir -p ${RD}/trees > mkdir -p ${RD}/dists > mkdir -p ${RD}/kernels 401c419 < ( cd ${RD}/trees/bin/dev && \ --- > ( cd /dev && \ 627,628c645,646 < -e 's/GENERIC/BOOTMFS/g' \ < -e '/maxusers/s/10/4/' < GENERIC > BOOTMFS && \ --- > -e 's/${KERNELS}/BOOTMFS/g' \ > -e '/maxusers/s/10/4/' < ${KERNELS} > BOOTMFS && \ There was one other change necessary to make the targets compile. sysinstall needed to libs not listed in the boot floppy crunch.conf file. Add these to libs to the 'libs' statement in the file: /usr/src/release/floppies/boot/crunch -lcrypt -lftpio I believe this is the core of the changes I had to make to get this all to work. If anyone needs help, please feel free to email me. --- Jim C., President | C A R R O L L - N E T, Inc. 201-488-1332 voice | New Jersey's Premier Internet Service Provider 201-487-5717 dialup | http://www.carroll.com | Ask about our Business Messaging Services From owner-freebsd-hackers Mon Jul 28 11:54:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24560 for hackers-outgoing; Mon, 28 Jul 1997 11:54:20 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24550 for ; Mon, 28 Jul 1997 11:54:15 -0700 (PDT) Received: from shell1.cybercom.net (ksmm@shell1.cybercom.net [209.21.136.6]) by kalypso.cybercom.net (8.8.5/8.8.5) with ESMTP id OAA01894; Mon, 28 Jul 1997 14:42:33 -0400 (EDT) Received: from localhost (ksmm@localhost) by shell1.cybercom.net (8.8.5/8.8.5) with SMTP id PAA20038; Mon, 28 Jul 1997 15:05:25 -0400 (EDT) Date: Mon, 28 Jul 1997 15:05:25 -0400 (EDT) From: The Classiest Man Alive To: Terry Lambert cc: dennis , sef@Kithrup.COM, hackers@FreeBSD.ORG Subject: Re: SVR4.2MP source code has become available recently? In-Reply-To: <199707281734.KAA01313@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 On Mon, 28 Jul 1997, Terry Lambert wrote: :>No. Under no circumstances should you use it as a reference. This is :>dangerous. : :>Unless, of course, you don't want to do any FreeBSD development, or, if :>you do, you want to get yourself and/or Jordan Hubbard sued for some :>intellectual property violation (e.g., copyright or trade secret). I'm sure that Jordan wouldn't mind doing a little hard time if it was in the best interest of "The Project." ;-) K.S. From owner-freebsd-hackers Mon Jul 28 12:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA25186 for hackers-outgoing; Mon, 28 Jul 1997 12:05:12 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA25174 for ; Mon, 28 Jul 1997 12:05:06 -0700 (PDT) Received: from shell1.cybercom.net (ksmm@shell1.cybercom.net [209.21.136.6]) by kalypso.cybercom.net (8.8.5/8.8.5) with ESMTP id OAA01894; Mon, 28 Jul 1997 14:42:33 -0400 (EDT) Received: from localhost (ksmm@localhost) by shell1.cybercom.net (8.8.5/8.8.5) with SMTP id PAA20038; Mon, 28 Jul 1997 15:05:25 -0400 (EDT) Date: Mon, 28 Jul 1997 15:05:25 -0400 (EDT) From: The Classiest Man Alive To: Terry Lambert cc: dennis , sef@Kithrup.COM, hackers@FreeBSD.ORG Subject: Re: SVR4.2MP source code has become available recently? In-Reply-To: <199707281734.KAA01313@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 On Mon, 28 Jul 1997, Terry Lambert wrote: :>No. Under no circumstances should you use it as a reference. This is :>dangerous. : :>Unless, of course, you don't want to do any FreeBSD development, or, if :>you do, you want to get yourself and/or Jordan Hubbard sued for some :>intellectual property violation (e.g., copyright or trade secret). I'm sure that Jordan wouldn't mind doing a little hard time if it was in the best interest of "The Project." ;-) K.S. From owner-freebsd-hackers Mon Jul 28 12:17:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA25819 for hackers-outgoing; Mon, 28 Jul 1997 12:17:55 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA25814 for ; Mon, 28 Jul 1997 12:17:49 -0700 (PDT) Received: from shell1.cybercom.net (ksmm@shell1.cybercom.net [209.21.136.6]) by kalypso.cybercom.net (8.8.5/8.8.5) with ESMTP id OAA01894; Mon, 28 Jul 1997 14:42:33 -0400 (EDT) Received: from localhost (ksmm@localhost) by shell1.cybercom.net (8.8.5/8.8.5) with SMTP id PAA20038; Mon, 28 Jul 1997 15:05:25 -0400 (EDT) Date: Mon, 28 Jul 1997 15:05:25 -0400 (EDT) From: The Classiest Man Alive To: Terry Lambert cc: dennis , sef@Kithrup.COM, hackers@FreeBSD.ORG Subject: Re: SVR4.2MP source code has become available recently? In-Reply-To: <199707281734.KAA01313@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 On Mon, 28 Jul 1997, Terry Lambert wrote: :>No. Under no circumstances should you use it as a reference. This is :>dangerous. : :>Unless, of course, you don't want to do any FreeBSD development, or, if :>you do, you want to get yourself and/or Jordan Hubbard sued for some :>intellectual property violation (e.g., copyright or trade secret). I'm sure that Jordan wouldn't mind doing a little hard time if it was in the best interest of "The Project." ;-) K.S. From owner-freebsd-hackers Mon Jul 28 12:32:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA26643 for hackers-outgoing; Mon, 28 Jul 1997 12:32:52 -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 MAA26638 for ; Mon, 28 Jul 1997 12:32:49 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wsvPb-0006Y1-00; Mon, 28 Jul 1997 12:24:55 -0700 Date: Mon, 28 Jul 1997 12:24:54 -0700 (PDT) From: Tom Samplonius To: Jim Dixon cc: David Greenman , hackers@freebsd.org Subject: Re: MAX physical memory 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 Mon, 28 Jul 1997, Jim Dixon wrote: > panic: bouce memory out of range Do you have bounce buffers in your kernel? You probably shouldn't, unless you have ISA devices that require DMA. But who would use ISA devices in a large server? > during boot. > > ------------------------------------------------------------------------ > > Any ideas ?? > > -- > Jim Dixon VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 > > > Tom From owner-freebsd-hackers Mon Jul 28 13:15:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29518 for hackers-outgoing; Mon, 28 Jul 1997 13:15:03 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29506 for ; Mon, 28 Jul 1997 13:14:58 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id VAA26735; Mon, 28 Jul 1997 21:14:33 +0100 (BST) Date: Mon, 28 Jul 1997 21:14:33 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Tom Samplonius cc: hackers@FreeBSD.ORG Subject: Re: MAX physical memory 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 Mon, 28 Jul 1997, Tom Samplonius wrote: > > panic: bouce memory out of range > > Do you have bounce buffers in your kernel? You probably shouldn't, > unless you have ISA devices that require DMA. But who would use ISA > devices in a large server? The only "ISA" devices are a floppy drive and an IDE drive. And, yes, bounce buffers are enabled. The server has a lot of memory (we are building it with 384 MB) but should only hit the disk during once-daily reloads. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Mon Jul 28 13:45:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA01520 for hackers-outgoing; Mon, 28 Jul 1997 13:45:07 -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 NAA01511 for ; Mon, 28 Jul 1997 13:45:03 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA01576; Mon, 28 Jul 1997 13:42:33 -0700 From: Terry Lambert Message-Id: <199707282042.NAA01576@phaeton.artisoft.com> Subject: Re: SVR4.2MP source code has become available recently? To: ksmm@cybercom.net (The Classiest Man Alive) Date: Mon, 28 Jul 1997 13:42:33 -0700 (MST) Cc: terry@lambert.org, dennis@etinc.com, sef@Kithrup.COM, hackers@FreeBSD.ORG In-Reply-To: from "The Classiest Man Alive" at Jul 28, 97 03:05: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 > On Mon, 28 Jul 1997, Terry Lambert wrote: > > :>No. Under no circumstances should you use it as a reference. This is > :>dangerous. > : > :>Unless, of course, you don't want to do any FreeBSD development, or, if > :>you do, you want to get yourself and/or Jordan Hubbard sued for some > :>intellectual property violation (e.g., copyright or trade secret). > > I'm sure that Jordan wouldn't mind doing a little hard time if it was in > the best interest of "The Project." ;-) Actually, your quote has been misattributed. I believe the actual author was Sean Eric Fagan. 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 Jul 28 13:54:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02139 for hackers-outgoing; Mon, 28 Jul 1997 13:54:59 -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 NAA02117 for ; Mon, 28 Jul 1997 13:54:53 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wswoc-0006d9-00; Mon, 28 Jul 1997 13:54:50 -0700 Date: Mon, 28 Jul 1997 13:54:48 -0700 (PDT) From: Tom Samplonius To: Jim Dixon cc: hackers@freebsd.org Subject: Re: MAX physical memory 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 Mon, 28 Jul 1997, Jim Dixon wrote: > On Mon, 28 Jul 1997, Tom Samplonius wrote: > > > > panic: bouce memory out of range > > > > Do you have bounce buffers in your kernel? You probably shouldn't, > > unless you have ISA devices that require DMA. But who would use ISA > > devices in a large server? > > The only "ISA" devices are a floppy drive and an IDE drive. And, > yes, bounce buffers are enabled. Turn them off. You don't need them. > The server has a lot of memory (we are building it with 384 MB) but > should only hit the disk during once-daily reloads. Ugh... all IDE drives have poor MTBF ratings... > -- > Jim Dixon VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 > > > Tom From owner-freebsd-hackers Mon Jul 28 14:02:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA02579 for hackers-outgoing; Mon, 28 Jul 1997 14:02:13 -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 NAA02267 for ; Mon, 28 Jul 1997 13:56:58 -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 UAA17193 for ; Mon, 28 Jul 1997 20:49:28 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id UAA21778 for ; Mon, 28 Jul 1997 20:49:28 +0100 (BST) Message-Id: <199707281949.UAA21778@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-hackers@FreeBSD.org Subject: date(1) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jul 1997 20:49:28 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'd like to add the following functionality to date(1) in -current, and eventually backport it to RELENG_2_2. The argument against is that it introduces more cruft into /bin, but I think date(1) is the correct place for it. The following flags will "adjust" the displayed date: -D [+|-]days -M [+|-]months -W [+|-]weekdays -Y [+|-]years Without the + or - before the given day/month/weekday/year, the appropriate bit of the date will be set to the given value. With the + or -, the date will be adjusted by the given value. For example, ``date -D1'' will output the date on the first of this month, ``date -D1 -D-1'' will output the last day of last month, ``date -D1 -D-1 -W+saturday'' will output the date on the first Saturday of this month and ``date -D1 -M+1 -W-fri'' will output the last Friday of the month. The flags are processed strictly in order. The functionality can be used to provide arguments to programs and would be *really* useful for archiving scripts. Any objections or suggestions ? -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jul 28 14:37:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA04909 for hackers-outgoing; Mon, 28 Jul 1997 14:37:58 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA04904 for ; Mon, 28 Jul 1997 14:37:56 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA26496 (5.67b/IDA-1.5 for ); Mon, 28 Jul 1997 23:37:46 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id XAA12202; Mon, 28 Jul 1997 23:37:40 +0200 (CEST) X-Face: " Date: Mon, 28 Jul 1997 23:37:40 +0200 From: Stefan Esser To: Michael Smith Cc: "Mike O'Dell" , hackers@FreeBSD.ORG Subject: Re: SMBIOS/DMI etc References: <199707191431.AAA14199@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707191431.AAA14199@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Jul 20, 1997 at 12:01:49AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 20, Michael Smith wrote: > The reason I ask is just to attempt to identify whether the BIOS32 > thing ever took off; I can't find _diddly_ about it online, but it > does appear to be reasonably widely implemented. All systems with PCI BIOS are supposed to have BIOS32 support. I can check the PCI BIOS specs, but I'm quite sure that this is not obtional, from the PCI point of view ... Regards, STefan From owner-freebsd-hackers Mon Jul 28 14:44:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA05279 for hackers-outgoing; Mon, 28 Jul 1997 14:44:36 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA05273 for ; Mon, 28 Jul 1997 14:44:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-5.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA27499 (5.67b/IDA-1.5 for ); Mon, 28 Jul 1997 23:44:28 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id XAA12237; Mon, 28 Jul 1997 23:44:28 +0200 (CEST) X-Face: " Date: Mon, 28 Jul 1997 23:44:28 +0200 From: Stefan Esser To: Michael Smith Cc: "Mike O'Dell" , hackers@FreeBSD.ORG Subject: Re: SMBIOS/DMI etc References: <199707191512.AAA14340@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707191512.AAA14340@genesis.atrad.adelaide.edu.au>; from Michael Smith on Sun, Jul 20, 1997 at 12:42:09AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 20, Michael Smith wrote: > Stefan, do you have any interest in using the PCI BIOS as well > as/instead of doing things the "hard way" as is done at the moment? Well, yes and no ... I have considered adding calls to the PCI BIOS as an alternate mechanism to directly reading configuration space registers. But I have no intention to make the PCI code depend on PCI BIOS services. There is one function that might be interesting for SMP motherboards that are not compliant to the latest SMP spec. and that need some knowledge about the routing of PCI interrupt pins to the chip-set. There is a PCI BIOS function that builds a table which contains the necessary information (which else has to be guessed). But I do not have time to debug the BIOS32 functionality, right now, and need to know it is operational, before I try to use it ... Regards, STefan From owner-freebsd-hackers Mon Jul 28 14:53:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA05976 for hackers-outgoing; Mon, 28 Jul 1997 14:53:54 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA05971 for ; Mon, 28 Jul 1997 14:53:46 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id OAA01303 for freebsd-hackers@freebsd.org; Mon, 28 Jul 1997 14:50:17 -0700 (PDT) From: Vinay Bannai Message-Id: <199707282150.OAA01303@agni.nuko.com> Subject: Location of copyin() and copyout().. To: freebsd-hackers@freebsd.org Date: Mon, 28 Jul 1997 14:50:17 -0700 (PDT) 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 Hi folks, I was wondering if it is considered a good idea to move data back and forth between the user and kernel space using copyin() and copyout() without calling uiomove(). I can't seem to find the location of these functions/macros. Can someone point me where they are defined?? Thanks Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Mon Jul 28 15:16:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07327 for hackers-outgoing; Mon, 28 Jul 1997 15:16:46 -0700 (PDT) Received: from labs.usn.blaze.net.au (root@labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA07315 for ; Mon, 28 Jul 1997 15:16:31 -0700 (PDT) Received: from labs.usn.blaze.net.au (davidn@local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id IAA24833; Tue, 29 Jul 1997 08:15:16 +1000 (EST) Message-Id: <199707282215.IAA24833@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), freebsd-hackers@FreeBSD.ORG Subject: Re: utmp/wtmp interface In-reply-to: Your message of "Mon, 28 Jul 1997 10:43:18 MST." <199707281743.KAA01338@phaeton.artisoft.com> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 08:15:13 +1000 From: David Nugent Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This will make it harder for things like last(1) to page back > > > through the file from the end, but life is sometimes tough. Besides, > > > last(1) will use the API, which will handle this transparently in any > > > case, including the buffering. > > > > Yup. Sounds good. > > I suggest that you provide either a fixed lenth record format, or > a fixed length header containing an index. I definitely disagree. > Without an index, a large utmp/wtmp would be unbearably slow. No, it isn't. Whether accessed forwards or reverse order, wtmp is invariably accessed *sequentially*. An index is entirely unnecessary, and nor is it slow. I have working code here that shows it to be pretty much comparable with fixed length records, even though a variable length (newline delimited) record is used *and* parsed. The cost is a little more code, but certainly not performance to any significant degree. > The way it works now, multiplying the record number by the size of the > struct keeps it happy. The way it would work would be to read in blocks of data until EOF, and scanned from either end of the file. The internal parser scans for newlines and keeps track of where it is at in the internal buffer. Using an index for sequentially accessed data is just unnecessary overhead. utmp is of course different. init primarily manages this and needs to *update* records in it, which are accessed randomly. This really does need to be fixed length format. I'm currently reworking the interface(s) based on suggestions by a number of people, which will solve the problem of using static data completely. Actually it is based on a paradigm I've used quite often, and I have no idea why it didn't occur to me to use it here as well. :-/ I'll announce again when I'm done (I'd say a few days, but the way things are right now, it might be a few weeks :-(). And Terry, just for you, I'll include the proposed new version of last that uses the getwt*() api and the wtmp (current format) -> wtmp (text) converter which will demonstrate my point with regards to performance; you only need to recompile/install the new libutil to change the format you want to test with (which is really the point of this exercise). FWIW, if anything truely wants to access wtmp randomly, it isn't so hard to write some code to index whatever you want into a .db file (or memory, for that matter). The idea here isn't so much the format itself, but that file access be hidden behind files be behind a standard API. Once that is done, then you can add bells and whistles like the .db index(es) or mmap()ing, or whatever you like by modifying one library function. I'm actually not really intended to (yet) rework the file formats, although obviously I had a strong leaning towards a varlen text format for wtmp and nothing else fancy to solve imaginary problems. Regards, David -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Mon Jul 28 15:19:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07508 for hackers-outgoing; Mon, 28 Jul 1997 15:19:20 -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 PAA07497 for ; Mon, 28 Jul 1997 15:19:11 -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 PAA27147; Mon, 28 Jul 1997 15:20:26 -0700 (PDT) Message-Id: <199707282220.PAA27147@implode.root.com> To: Jim Dixon cc: hackers@FreeBSD.ORG Subject: Re: MAX physical memory for FreeBSD ? In-reply-to: Your message of "Mon, 28 Jul 1997 19:31:03 BST." From: David Greenman Reply-To: dg@root.com Date: Mon, 28 Jul 1997 15:20:26 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Well, after applying the patches, I now get: > > panic: bouce memory out of range > >during boot. Just remove the BOUNCE_BUFFERS. There was a bug in the calculation for the size of the pool that was fixed after the release. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 28 15:20:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07614 for hackers-outgoing; Mon, 28 Jul 1997 15:20:55 -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 PAA07607 for ; Mon, 28 Jul 1997 15:20:48 -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 PAA04955; Mon, 28 Jul 1997 15:20:19 -0700 (PDT) To: Andrzej Bialecki cc: Ollivier Robert , freebsd-hackers@FreeBSD.ORG Subject: Re: Nvi and locale In-reply-to: Your message of "Mon, 28 Jul 1997 13:57:01 +0200." Date: Mon, 28 Jul 1997 15:20:19 -0700 Message-ID: <4951.870128419@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sure, simply submit your diffs / keymap / screen files as a PR and someone from the I18N side of things will incorporate them into future releases. Jordan From owner-freebsd-hackers Mon Jul 28 15:31:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08196 for hackers-outgoing; Mon, 28 Jul 1997 15:31:26 -0700 (PDT) Received: from mail.be.com (be.be.com [207.113.215.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA08185 for ; Mon, 28 Jul 1997 15:31:19 -0700 (PDT) Received: from localhost by mail.be.com with smtp (Smail3.1.29.1 #1) id m0wsyMB-000odRC; Mon, 28 Jul 97 15:33 PDT Date: Mon, 28 Jul 1997 15:24:16 -0800 Message-ID: <19970728152416.PM-jriro5pm@Adam.BeOS> MIME-Version: 1.0 X-Mailer: Adam 1.0 on BeOS Subject: Re: Anyone tried VirtualPC with FreeBSD? To: Michael Smith Cc: From: Jake Hamby 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 PAA08187 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: >Jake Hamby stands accused of saying: >> Just for fun, I tried to boot FreeBSD 2.2.2 from within the VirtualPC >> emulator for MacOS, which claims to simulate a full Intel Pentium PC at >> the hardware level. It can run unmodified version of Windows 95, NT, >> OS/2, and NextStep, and so I assumed it wouldn't have much trouble with >> FreeBSD. >> >> Unfortunately, immediately after loading the kernel, FreeBSD panicked with >> this error: >> >> Fatal trap 1: privileged instruction fault while in kernel mode >> >> instruction ptr = 0x8:0xf01b99aa > >Where is this in the kernel? Are you booting an installation disk? If >so, which one? Suck the kernel off the disk, and say : > >nm kernel | sort | less > >and send us the symbols from around the IP above. I'm using the BOOTMFS kernel from the FreeBSD 2.2.2 RELEASE. Here are the symbols near the area of the crash: f01b93cc t _clkintr f01b9598 T _acquire_timer0 f01b95fc T _acquire_timer2 f01b9624 T _release_timer0 f01b9660 T _release_timer2 f01b9684 t _rtcintr f01b96a8 t _getit f01b96d4 T _DELAY f01b9794 t _sysbeepstop f01b97b0 T _sysbeep f01b985c T _rtcin f01b98e4 t _calibrate_clocks f01b9a90 t _set_timer_freq f01b9bb4 T _startrtclock f01b9d3c T _inittodr f01b9ef0 T _resettodr f01ba0e4 T _cpu_initclocks f01ba1e8 T _setstatclockrate f01ba218 t _sysctl_machdep_i8254_freq f01ba284 t _sysctl___machdep_i8254_freq f01ba2b0 t ___set_sysctl__machdep_sym_sysctl___machdep_i8254_freq f01ba2b4 t _set_i586_ctr_freq f01ba338 t _sysctl_machdep_i586_freq f01ba398 t _sysctl___machdep_i586_freq f01ba3c0 t ___set_sysctl__machdep_sym_sysctl___machdep_i586_freq >> Obviously, this is a bug in Connectix's CPU emulator. But I'm curious if >> anyone could give any information off-hand as to what they might be doing >> wrong that would trigger such an error from the FreeBSD kernel. > >Not _necessarily_ "obviously"; it's possible that the emulator just does >something "odd" that's upsetting the kernel. Yep. It actually would be better if it *was* a bug in FreeBSD because we're much more likely to fix it than they are, since FreeBSD isn't on their list of "supported" OS's. BTW, here's some further info on the hardware that Virtual PC simulates (from the manual). It's important to keep in mind that this is an all-software emulator: despite the detailed chipset listing, there is no actual PC hardware involved! Intel Pentium with MMX Includes complete support for Pentium architecture including protected-mode, MMU, FPU, and MMX. Virtual PC uses the Intel Triton chipset (Intel Zappa motherboard). It includes all auxiliary chips needed for a PC including: 8259 PIC 8254 PIT 8237 DMA controller CMOS RTC BIOS is the Microid Reserach System BIOS Hard drive image and CD-ROM accessed through dual IDE/ATAPI controllers 8255 keyboard controller Emulates a PS/2 mouse using IRQ 12 SoundBlaster Pro card on port 0x220, IRQ 5, and DMA channel 1 DEC 21041-based PCI Ethernet card, Plug and Play but on IRQ 11 by default -jake From owner-freebsd-hackers Mon Jul 28 15:40:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08942 for hackers-outgoing; Mon, 28 Jul 1997 15:40:53 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA08930; Mon, 28 Jul 1997 15:40:41 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id IAA02358; Tue, 29 Jul 1997 08:10:41 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707282240.IAA02358@freebie.lemis.com> Subject: Re: AMD PCNet/PCI troubles In-Reply-To: from Max Khon at "Jul 28, 97 06:48:58 pm" To: max@iclub.nsu.ru (Max Khon) Date: Tue, 29 Jul 1997 08:10:41 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG 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-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 Max Khon writes: > > On Mon, 28 Jul 1997, Michael Smith wrote: > >> I don't have access to a current Linux kernel tree (as getting such an >> animal requires real effort, as opposed to the FreeBSD tree 8), so I can't >> check offhand and see if they actually report these errors to the console. > > but under FreeBSD (unlike Linux) networking sometimes is very slow > (~30-50K/s via ftp) I'm sure this happens under Linux too, like it sometimes happens under any operating system. It's a bug, probably in the configuration. Greg From owner-freebsd-hackers Mon Jul 28 15:52:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09659 for hackers-outgoing; Mon, 28 Jul 1997 15:52:32 -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 PAA09651 for ; Mon, 28 Jul 1997 15:52:29 -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 PAA05195; Mon, 28 Jul 1997 15:50:27 -0700 (PDT) To: The Classiest Man Alive cc: Terry Lambert , dennis , sef@Kithrup.COM, hackers@FreeBSD.ORG Subject: Re: SVR4.2MP source code has become available recently? In-reply-to: Your message of "Mon, 28 Jul 1997 15:05:25 EDT." Date: Mon, 28 Jul 1997 15:50:27 -0700 Message-ID: <5192.870130227@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm sure that Jordan wouldn't mind doing a little hard time if it was in > the best interest of "The Project." ;-) Sigh.. :) From owner-freebsd-hackers Mon Jul 28 15:55:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09841 for hackers-outgoing; Mon, 28 Jul 1997 15:55:22 -0700 (PDT) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09833 for ; Mon, 28 Jul 1997 15:55:20 -0700 (PDT) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.6/8.7.3) with SMTP id QAA18471 for ; Mon, 28 Jul 1997 16:56:18 -0600 (MDT) Date: Mon, 28 Jul 1997 16:56:17 -0600 (MDT) From: Brett Taylor To: hackers@freebsd.org Subject: weird warning and a thank you (fwd) 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 forgot to cc this to hackers and so far questions hasn't produced any response so .... If you respond to this from hackers, please cc as I'm not subscribed to that list. Thanks. Brett Taylor ---------- Forwarded message ---------- Date: Mon, 28 Jul 1997 13:47:32 -0600 (MDT) From: Brett Taylor To: questions@FreeBSD.ORG Subject: weird warning and a thank you Hi all, First let me thank all those who responded to the pstat question I had awhile back. Now, as you may recall from that question, I have just moved from 2.2.1 to 2.2.-STABLE. When I now telnet to my machine, to itself or from another machine, I get a warning: inetd in realloc(): warning: junk pointer, too low to make sense. Anyone know what causes this and how to fix it? Thanks in advance! ********************************************************* Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ With the time I waste on a life I never had I could have turned myself into a better man. - Toad the Wet Sprocket From owner-freebsd-hackers Mon Jul 28 16:14:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA10895 for hackers-outgoing; Mon, 28 Jul 1997 16:14:43 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA10875; Mon, 28 Jul 1997 16:14:23 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id IAA02459; Tue, 29 Jul 1997 08:44:23 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707282314.IAA02459@freebie.lemis.com> Subject: Re: MAX physical memory for FreeBSD ? In-Reply-To: from Jim Dixon at "Jul 28, 97 09:14:33 pm" To: jdd@vbc.net (Jim Dixon) Date: Tue, 29 Jul 1997 08:44:23 +0930 (CST) Cc: tom@sdf.com, hackers@FreeBSD.ORG 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-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 Jim Dixon writes: > On Mon, 28 Jul 1997, Tom Samplonius wrote: > >>> panic: bouce memory out of range >> >> Do you have bounce buffers in your kernel? You probably shouldn't, >> unless you have ISA devices that require DMA. But who would use ISA >> devices in a large server? > > The only "ISA" devices are a floppy drive and an IDE drive. And, > yes, bounce buffers are enabled. I've just completed an upgrade of my 3.0-current system from mid-December 1996 to now. I'm running an aha and an ahc, have BOUNCE_BUFFERS enabled, yet I get a lot of messages like: Jul 28 22:44:34 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3fcad14 Jul 28 22:44:42 freebie /kernel: aha0: DMA beyond end Of ISA: 0x227bd14 Jul 28 22:44:42 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3cc9d14 I haven't looked at the code yet, but it seems that there's something funny here. Greg From owner-freebsd-hackers Mon Jul 28 16:25:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11846 for hackers-outgoing; Mon, 28 Jul 1997 16:25:32 -0700 (PDT) Received: from roguetrader.com (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11840 for ; Mon, 28 Jul 1997 16:25:26 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id RAA00331 for ; Mon, 28 Jul 1997 17:25:44 -0600 (MDT) Date: Mon, 28 Jul 1997 17:25:43 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: pkg_* commands vs 'pkg' command Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-891458119-870132343=:318" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-891458119-870132343=:318 Content-Type: TEXT/PLAIN; charset=US-ASCII Just curious, but does anybody else find having to use '_' in ANY command clunky and unweildy? I recently had to take a little bit of light flack (nothing serious 8) from a debian linux user because they have a simple 'dpkg' command (I think it was). In response to this I hacked up a simple wrapper to the various 'pkg_' commands, and added a 'list' option as well (see attachment). This is just a shell script which I personally have dropped in /usr/sbin/pkg (alongside the counterparts it execs). Yeah, it simply nixes the '_' in typing, but it saves a keystroke and stretch of the finger--not to mention it feels better from a UI point of view :) Has anybody ever considered unifying the various seperate package commands? At least in a manner similar to how mount is unified? (i.e. seperate commands for specific things, but still one central command for ease of use). -Brandon Gillespie --0-891458119-870132343=:318 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=pkg Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: IyEvYmluL3NoDQoNCmNtZD0iIg0KYXJncz0iIg0Kc3ludGF4KCkgew0KICAg IGNhdCA8PEVORA0KU3ludGF4OiBwa2cgPGFkZHxkZWx8bGlzdHxjcmVhdGU+ IFthcmdzXQ0KDQpXaGVyZSBbYXJnc10gYXJlIGFkZC9kZWwvbGlzdC9jcmVh dGUgc3BlY2lmaWMgYXJndW1lbnRzLg0KRU5EDQp9DQoNCmlmIFsgIiQxIiA9 ICIiIF07IHRoZW4NCiAgICBzeW50YXgNCiAgICBleGl0IDENCmZpDQoNCmNh c2UgJDEgaW4NCiAgICBsaXN0KQ0KICAgICAgICBjbWQ9InBrZ19pbmZvIg0K ICAgICAgICBhcmdzPSIkYXJncyAtYUkiIDs7DQogICAgYWRkKQ0KICAgICAg ICBjbWQ9InBrZ19hZGQiIDs7DQogICAgZGVsIHwgZGVsZXRlIHwgcm0pDQog ICAgICAgIGNtZD0icGtnX2RlbGV0ZSIgOzsNCiAgICBjcmVhdGUpDQogICAg ICAgIGNtZD0icGtnX2NyZWF0ZSIgOzsNCiAgICAqKQ0KICAgICAgICBzeW50 YXggOzsNCmVzYWMNCg0Kc2hpZnQNCg0KZXhlYyAkY21kICRhcmdzICQqDQo= --0-891458119-870132343=:318-- From owner-freebsd-hackers Mon Jul 28 17:00:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14036 for hackers-outgoing; Mon, 28 Jul 1997 17:00:45 -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 RAA14028 for ; Mon, 28 Jul 1997 17:00:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA01875; Mon, 28 Jul 1997 16:58:25 -0700 From: Terry Lambert Message-Id: <199707282358.QAA01875@phaeton.artisoft.com> Subject: Re: utmp/wtmp interface To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Mon, 28 Jul 1997 16:58:25 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707282215.IAA24833@labs.usn.blaze.net.au> from "David Nugent" at Jul 29, 97 08:15:13 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 > utmp is of course different. init primarily manages this and > needs to *update* records in it, which are accessed randomly. > This really does need to be fixed length format. Yes; are you suggesting different formats for the files? This is kind of an annoying idea, if only because it's been murder trying to get most of the configuration data into a unified format, and then here we go adding Yet Another Format. 8-(. > I'll announce again when I'm done (I'd say a few days, but the way > things are right now, it might be a few weeks :-(). And Terry, > just for you, I'll include the proposed new version of last that > uses the getwt*() api and the wtmp (current format) -> wtmp (text) > converter which will demonstrate my point with regards to performance; > you only need to recompile/install the new libutil to change the > format you want to test with (which is really the point of this > exercise). Thanks; 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 Mon Jul 28 17:04:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14317 for hackers-outgoing; Mon, 28 Jul 1997 17:04: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 RAA14274 for ; Mon, 28 Jul 1997 17:04:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA01897; Mon, 28 Jul 1997 17:03:00 -0700 From: Terry Lambert Message-Id: <199707290003.RAA01897@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: vinay@agni.nuko.com (Vinay Bannai) Date: Mon, 28 Jul 1997 17:03:00 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707282150.OAA01303@agni.nuko.com> from "Vinay Bannai" at Jul 28, 97 02:50:17 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 was wondering if it is considered a good idea to move data back and > forth between the user and kernel space using copyin() and copyout() > without calling uiomove(). I can't seem to find the location of these > functions/macros. Can someone point me where they are defined?? They are kernel intrinsics. It's OK to use them, if you aren't using them for an I/O buffer. The primary reason to use UIO is that it handles user I/O request, ie: it does buffer paging correctly, and anonymously. There are lots of places where copyin/copyout is used (ioctl() paramters, the path name copy in namei(), etc.). 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 Jul 28 17:09:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14820 for hackers-outgoing; Mon, 28 Jul 1997 17:09:16 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14776; Mon, 28 Jul 1997 17:09:00 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id JAA02705; Tue, 29 Jul 1997 09:39:01 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707290009.JAA02705@freebie.lemis.com> Subject: Re: SVR4.2MP source code has become available recently? In-Reply-To: from The Classiest Man Alive at "Jul 28, 97 03:05:25 pm" To: ksmm@cybercom.net (The Classiest Man Alive) Date: Tue, 29 Jul 1997 09:39:01 +0930 (CST) Cc: terry@lambert.org, dennis@etinc.com, sef@Kithrup.COM, hackers@FreeBSD.ORG 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-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 The Classiest Man Alive writes: > On Mon, 28 Jul 1997, Terry Lambert wrote: > >>> No. Under no circumstances should you use it as a reference. This is >>> dangerous. >> >>> Unless, of course, you don't want to do any FreeBSD development, or, if >>> you do, you want to get yourself and/or Jordan Hubbard sued for some >>> intellectual property violation (e.g., copyright or trade secret). > > I'm sure that Jordan wouldn't mind doing a little hard time if it was in > the best interest of "The Project." ;-) I'd strongly contest the notion that inclusion of System V code would be in the best interest of the project. I've always claimed that the real reason they want it kept secret is so that people don't find out how crappily it's written. Greg From owner-freebsd-hackers Mon Jul 28 17:19:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA15712 for hackers-outgoing; Mon, 28 Jul 1997 17:19:35 -0700 (PDT) Received: from labs.usn.blaze.net.au (root@labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15685 for ; Mon, 28 Jul 1997 17:19:12 -0700 (PDT) Received: from labs.usn.blaze.net.au (davidn@local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id KAA13363; Tue, 29 Jul 1997 10:18:04 +1000 (EST) Message-Id: <199707290018.KAA13363@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG Subject: Re: utmp/wtmp interface In-reply-to: Your message of "Mon, 28 Jul 1997 16:58:25 MST." <199707282358.QAA01875@phaeton.artisoft.com> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 10:18:03 +1000 From: David Nugent Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > utmp is of course different. init primarily manages this and > > needs to *update* records in it, which are accessed randomly. > > This really does need to be fixed length format. > > Yes; are you suggesting different formats for the files? No, only suggesting a way in which changes to the file formats can be made transparent, and even offer binary compatibility to dynamically linked applications when changes are made. The initial implementation will use backwards compatible (in fact almost identical) formats to the current files we use. Only one 'special' field is being reused to the first (currently unused) record in utmp to define the record size, which an application doesn't have to deal with anyway. The actual record size won't initially be changed either. > This is > kind of an annoying idea, if only because it's been murder trying > to get most of the configuration data into a unified format, and > then here we go adding Yet Another Format. 8-(. Well, that's the point. There shouldn't need to be any "unified format" - just a "unified api" by which the data can be updated and accessed. It'd be nice if others adopted the same api, which ultimately leads to portability at the applications level - whatever "extra" an OS vendor wishes to add is also allowed for in the api, and applications can take advantage of those if it wishes, again without worrying about how the actual files are formatted, stored or even if they exist at all. Regards, David -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Mon Jul 28 18:32:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21778 for hackers-outgoing; Mon, 28 Jul 1997 18:32:25 -0700 (PDT) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21773 for ; Mon, 28 Jul 1997 18:32:20 -0700 (PDT) Received: from slip129-37-195-162.nc.us.ibm.net (slip129-37-195-162.nc.us.ibm.net [129.37.195.162]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id BAA121314; Tue, 29 Jul 1997 01:30:55 GMT From: mouth@ibm.net (John Kelly) To: hackers@FreeBSD.ORG Cc: Terry Lambert Subject: Sharing interrupts Date: Tue, 29 Jul 1997 01:33:00 GMT Message-ID: <33df45b3.744892@smtp-gw01.ny.us.ibm.net> References: <199707281738.KAA01326@phaeton.artisoft.com> In-Reply-To: <199707281738.KAA01326@phaeton.artisoft.com> X-Mailer: Forte Agent 1.01/16.397 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 SAA21774 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 28 Jul 1997 10:38:32 -0700 (MST), Terry Lambert wrote: > You can not share interrupts with ISA cards. Period. Semicolon; With the multiport support in the FreeBSD kernel config, and by soldering resistors and diodes in the right places, you can share interrupts among multiple serial cards. The technique has been previously published on Usenet, and it works. I have verified it. John From owner-freebsd-hackers Mon Jul 28 19:08:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24564 for hackers-outgoing; Mon, 28 Jul 1997 19:08:50 -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 TAA24513; Mon, 28 Jul 1997 19:08:02 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA09417; Tue, 29 Jul 1997 11:37:54 +0930 (CST) From: Michael Smith Message-Id: <199707290207.LAA09417@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: <19970728233740.25649@mi.uni-koeln.de> from Stefan Esser at "Jul 28, 97 11:37:40 pm" To: se@freebsd.org (Stefan Esser) Date: Tue, 29 Jul 1997 11:37:53 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mo@uu.net, 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 Stefan Esser stands accused of saying: > On Jul 20, Michael Smith wrote: > > The reason I ask is just to attempt to identify whether the BIOS32 > > thing ever took off; I can't find _diddly_ about it online, but it > > does appear to be reasonably widely implemented. > > All systems with PCI BIOS are supposed to have BIOS32 support. > I can check the PCI BIOS specs, but I'm quite sure that this is > not obtional, from the PCI point of view ... OK. Next question; is access to the PCI BIOS useful from the POV of FreeBSD's PCI code? ie. would you prefer to talk to the BIOS rather than deal with probing the hardware yourself? I ask specifically in the light of the problems you've had in the past wrt. chipsets which implement PCI autoconfig in, er, interesting ways. Regardless of how broken their hardware might be, the BIOS must work properly or the dreaded MS operating systems wouldn't work properly... > Regards, STefan -- ]] 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 Jul 28 19:11:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24753 for hackers-outgoing; Mon, 28 Jul 1997 19:11:21 -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 TAA24704 for ; Mon, 28 Jul 1997 19:10:44 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA09434; Tue, 29 Jul 1997 11:40:27 +0930 (CST) From: Michael Smith Message-Id: <199707290210.LAA09434@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199707281949.UAA21778@awfulhak.org> from Brian Somers at "Jul 28, 97 08:49:28 pm" To: brian@awfulhak.org (Brian Somers) Date: Tue, 29 Jul 1997 11:40:27 +0930 (CST) 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 Brian Somers stands accused of saying: > > I'd like to add the following functionality to date(1) in -current, > and eventually backport it to RELENG_2_2. The argument against is > that it introduces more cruft into /bin, but I think date(1) is the > correct place for it. > > The following flags will "adjust" the displayed date: > > -D [+|-]days > -M [+|-]months > -W [+|-]weekdays > -Y [+|-]years > > Without the + or - before the given day/month/weekday/year, the > appropriate bit of the date will be set to the given value. With > the + or -, the date will be adjusted by the given value. > > For example, ``date -D1'' will output the date on the first of this > month, ``date -D1 -D-1'' will output the last day of last month, > ``date -D1 -D-1 -W+saturday'' will output the date on the first > Saturday of this month and ``date -D1 -M+1 -W-fri'' will output > the last Friday of the month. > > The flags are processed strictly in order. > > The functionality can be used to provide arguments to programs and > would be *really* useful for archiving scripts. > > Any objections or suggestions ? Please also add : - The ability to parse timestamps in ctime()-like format. - The ability to input and output the timestamp in decimal or hex localtime() format, ie. 0xXXXXXXXX or DDDDDDDDDD > Brian , -- ]] 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 Jul 28 19:12:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24866 for hackers-outgoing; Mon, 28 Jul 1997 19:12:32 -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 TAA24801; Mon, 28 Jul 1997 19:11:50 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA09448; Tue, 29 Jul 1997 11:41:43 +0930 (CST) From: Michael Smith Message-Id: <199707290211.LAA09448@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: <19970728234428.16657@mi.uni-koeln.de> from Stefan Esser at "Jul 28, 97 11:44:28 pm" To: se@freebsd.org (Stefan Esser) Date: Tue, 29 Jul 1997 11:41:42 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mo@uu.net, 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 Stefan Esser stands accused of saying: > > I have considered adding calls to the PCI BIOS as an > alternate mechanism to directly reading configuration > space registers. But I have no intention to make the > PCI code depend on PCI BIOS services. This is because...? > But I do not have time to debug the BIOS32 functionality, > right now, and need to know it is operational, before I > try to use it ... I think I've found enough help to sort it out; I'd be more than happy to present you with an API of your choice on a platter. > Regards, STefan -- ]] 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 Jul 28 19:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA25523 for hackers-outgoing; Mon, 28 Jul 1997 19:21: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 TAA25516 for ; Mon, 28 Jul 1997 19:20:54 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA09491; Tue, 29 Jul 1997 11:50:41 +0930 (CST) From: Michael Smith Message-Id: <199707290220.LAA09491@genesis.atrad.adelaide.edu.au> Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707282150.OAA01303@agni.nuko.com> from Vinay Bannai at "Jul 28, 97 02:50:17 pm" To: vinay@agni.nuko.com (Vinay Bannai) Date: Tue, 29 Jul 1997 11:50:40 +0930 (CST) 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 Vinay Bannai stands accused of saying: > > I was wondering if it is considered a good idea to move data back and > forth between the user and kernel space using copyin() and copyout() > without calling uiomove(). I can't seem to find the location of these > functions/macros. Can someone point me where they are defined?? It is generally considered _extremely_ bad to use copyin/copyout, as it precludes your functions from being called from within kernel space. FWIW, this is what eventually stumped me when it came to getting Linux WABI running on FreeBSD. > Vinay Bannai E-mail: vinay@agni.nuko.com -- ]] 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 Jul 28 19:30:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA26115 for hackers-outgoing; Mon, 28 Jul 1997 19:30: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 TAA26105 for ; Mon, 28 Jul 1997 19:29:53 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA09521; Tue, 29 Jul 1997 11:59:11 +0930 (CST) From: Michael Smith Message-Id: <199707290229.LAA09521@genesis.atrad.adelaide.edu.au> Subject: Re: Anyone tried VirtualPC with FreeBSD? In-Reply-To: <19970728152416.PM-jriro5pm@Adam.BeOS> from Jake Hamby at "Jul 28, 97 03:24:16 pm" To: jehamby@be.com (Jake Hamby) Date: Tue, 29 Jul 1997 11:59:11 +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 Jake Hamby stands accused of saying: > >> >> Fatal trap 1: privileged instruction fault while in kernel mode > >> >> instruction ptr = 0x8:0xf01b99aa ... > I'm using the BOOTMFS kernel from the FreeBSD 2.2.2 RELEASE. Here are the > symbols near the area of the crash: > > f01b98e4 t _calibrate_clocks > f01b9a90 t _set_timer_freq Ok. This may be the wrmsr() call : wrmsr(u_int msr, quad_t newval) { __asm __volatile(".byte 0x0f, 0x30" : : "A" (newval), "c" (msr)); } which is conditional on the CPU type reported being a P5 or P6, which is what it claims to be. It would be very interesting if you were to build a GENERIC kernel, stick it on a bootstrap-enabled floppy (do you know how to build a bootable FreeBSD floppy? ask if not), and modify calibrate_clocks in sys/i386/isa/clock.c to remove the wrmsr() call. You might also try removing the code that calls rdtsc() towards the bottom. > hardware that Virtual PC simulates (from the manual). It's important to > keep in mind that this is an all-software emulator: despite the detailed > chipset listing, there is no actual PC hardware involved! Yeah. The evidence so far suggests that their emulation may not be quite as complete as they claim. Please keep us posted! -- ]] 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 Jul 28 19:57:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29016 for hackers-outgoing; Mon, 28 Jul 1997 19:57:44 -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 TAA29008 for ; Mon, 28 Jul 1997 19:57:36 -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 DAA18934; Tue, 29 Jul 1997 03:57:06 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id DAA18266; Tue, 29 Jul 1997 03:57:05 +0100 (BST) Message-Id: <199707290257.DAA18266@awfulhak.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Michael Smith cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Tue, 29 Jul 1997 11:40:27 +0930." <199707290210.LAA09434@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 03:57:05 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brian Somers stands accused of saying: > > > > I'd like to add the following functionality to date(1) in -current, [.....] > Please also add : > > - The ability to parse timestamps in ctime()-like format. Yep. I think I'll fix the usage message too - shouldn't it be: [[yy[mm[dd[hh]]]]mm[.ss]] I must say, this format beats the mmddhhmmyy format in SYSV ! > - The ability to input and output the timestamp in decimal or hex > localtime() format, ie. 0xXXXXXXXX or DDDDDDDDDD Do you mean to output the actual "number of seconds since the epoch", as in the opposite of the -r option ? > > Brian , > > -- > ]] 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 [[ -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jul 28 20:12:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00779 for hackers-outgoing; Mon, 28 Jul 1997 20:12:12 -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 UAA00754 for ; Mon, 28 Jul 1997 20:12:06 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA09780; Tue, 29 Jul 1997 12:41:47 +0930 (CST) From: Michael Smith Message-Id: <199707290311.MAA09780@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199707290257.DAA18266@awfulhak.org> from Brian Somers at "Jul 29, 97 03:57:05 am" To: brian@awfulhak.org (Brian Somers) Date: Tue, 29 Jul 1997 12:41:47 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, brian@awfulhak.org, 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 Brian Somers stands accused of saying: > Yep. I think I'll fix the usage message too - shouldn't it be: > > [[yy[mm[dd[hh]]]]mm[.ss]] That'd be consistent with the manpage. > > - The ability to input and output the timestamp in decimal or hex > > localtime() format, ie. 0xXXXXXXXX or DDDDDDDDDD > > Do you mean to output the actual "number of seconds since the epoch", > as in the opposite of the -r option ? -r emits seconds since the epoch in decimal. At the very least, -r with a timevalue argument should set the time in seconds, preferably using strtoul so that it can handle decimal, hex and octal. Actually, -r is redundant, as +%s will do the same thing. On further thought, an alternative approach would be to use the new strptime() function and take a format string for scanning the time, much as it takes now for formatting the output. -- ]] 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 Jul 28 20:21:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01621 for hackers-outgoing; Mon, 28 Jul 1997 20:21:39 -0700 (PDT) Received: from onyx.atipa.com (user25806@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA01606 for ; Mon, 28 Jul 1997 20:21:19 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 29 Jul 1997 03:23:24 -0000 Date: Mon, 28 Jul 1997 21:23:24 -0600 (MDT) From: FreeBSD Development X-Sender: freebsd@dot.ishiboo.com To: John Kelly cc: hackers@FreeBSD.ORG, Terry Lambert Subject: Re: Sharing interrupts In-Reply-To: <33df45b3.744892@smtp-gw01.ny.us.ibm.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 Tue, 29 Jul 1997, John Kelly wrote: > On Mon, 28 Jul 1997 10:38:32 -0700 (MST), Terry Lambert wrote: > > > You can not share interrupts with ISA cards. Period. > You can share interrupts, but not use both SIMULTANEOUSLY. A very good example would be to have LPT1: and a sound card on IRQ7 (both ISA). As long as they have unique base addresses (0x378h and 0x220 for instance), both devices can coexist. You just can't use them at the same time without conflicting. Sharing IRQs is definitely not recommend, but I believe your statement may require a bit more qualifying. Kevin From owner-freebsd-hackers Mon Jul 28 20:27:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02037 for hackers-outgoing; Mon, 28 Jul 1997 20:27:15 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02007; Mon, 28 Jul 1997 20:26:49 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id MAA01445; Tue, 29 Jul 1997 12:56:38 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707290326.MAA01445@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199707290257.DAA18266@awfulhak.org> from Brian Somers at "Jul 29, 97 03:57:05 am" To: brian@awfulhak.org (Brian Somers) Date: Tue, 29 Jul 1997 12:56:38 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, brian@awfulhak.org, freebsd-hackers@FreeBSD.ORG 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-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 Brian Somers writes: > > Brian Somers stands accused of saying: > > > > > > I'd like to add the following functionality to date(1) in -current, > [.....] > > Please also add : > > > > - The ability to parse timestamps in ctime()-like format. > > Yep. I think I'll fix the usage message too - shouldn't it be: > > [[yy[mm[dd[hh]]]]mm[.ss]] > > I must say, this format beats the mmddhhmmyy format in SYSV ! Sure, it beats it, but it also includes a gratuitous incompatibility. I vote to leave it as it is. Greg From owner-freebsd-hackers Mon Jul 28 20:48:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03743 for hackers-outgoing; Mon, 28 Jul 1997 20:48:49 -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 UAA03735 for ; Mon, 28 Jul 1997 20:48:41 -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 EAA19123; Tue, 29 Jul 1997 04:33:19 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id EAA20583; Tue, 29 Jul 1997 04:33:18 +0100 (BST) Message-Id: <199707290333.EAA20583@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Smith cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Tue, 29 Jul 1997 12:41:47 +0930." <199707290311.MAA09780@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 04:33:18 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brian Somers stands accused of saying: > > Yep. I think I'll fix the usage message too - shouldn't it be: > > > > [[yy[mm[dd[hh]]]]mm[.ss]] > > That'd be consistent with the manpage. > > > > - The ability to input and output the timestamp in decimal or hex > > > localtime() format, ie. 0xXXXXXXXX or DDDDDDDDDD > > > > Do you mean to output the actual "number of seconds since the epoch", > > as in the opposite of the -r option ? > > -r emits seconds since the epoch in decimal. At the very least, -r > with a timevalue argument should set the time in seconds, preferably > using strtoul so that it can handle decimal, hex and octal. > > Actually, -r is redundant, as +%s will do the same thing. Not true. -r takes a ``seconds'' arg, and uses that instead of calling time(). It's a non-setting input value. I can get -r to use strtol(), but do we want to do things the other way too ? Do we want to be able to output hex too (ie, a change to strftime(3) - pity %x is gone...) ? > On further thought, an alternative approach would be to use the new > strptime() function and take a format string for scanning the time, > much as it takes now for formatting the output. This would allow us to change (say) the current month without touching the time..... how new is "strptime" ? It ain't on my machine (supped 1.5 hours ago). > -- > ]] 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 [[ -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jul 28 20:53:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04217 for hackers-outgoing; Mon, 28 Jul 1997 20:53: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 UAA04211 for ; Mon, 28 Jul 1997 20:53:04 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA10067; Tue, 29 Jul 1997 13:22:44 +0930 (CST) From: Michael Smith Message-Id: <199707290352.NAA10067@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199707290333.EAA20583@awfulhak.org> from Brian Somers at "Jul 29, 97 04:33:18 am" To: brian@awfulhak.org (Brian Somers) Date: Tue, 29 Jul 1997 13:22:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, brian@awfulhak.org, 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 Brian Somers stands accused of saying: > > > > Actually, -r is redundant, as +%s will do the same thing. > > Not true. -r takes a ``seconds'' arg, and uses that instead of > calling time(). It's a non-setting input value. Oops, sorry about that. > I can get -r to use strtol(), but do we want to do things the other > way too ? Do we want to be able to output hex too (ie, a change to > strftime(3) - pity %x is gone...) ? On reflection, probably not. Anyone that needs hex can get it with printf(1) already. > > On further thought, an alternative approach would be to use the new > > strptime() function and take a format string for scanning the time, > > much as it takes now for formatting the output. > > This would allow us to change (say) the current month without touching > the time..... how new is "strptime" ? It ain't on my machine (supped > 1.5 hours ago). Uhh. Perhaps it didn't get committed; it should have. Chase the -hackers mailing list for the perp who had it ready. I do think it is a better way to go than having a whole bag of new flags. -- ]] 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 Jul 28 20:56:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04607 for hackers-outgoing; Mon, 28 Jul 1997 20:56:53 -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 UAA04575 for ; Mon, 28 Jul 1997 20:56:27 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA10082; Tue, 29 Jul 1997 13:26:13 +0930 (CST) From: Michael Smith Message-Id: <199707290356.NAA10082@genesis.atrad.adelaide.edu.au> Subject: Re: Sharing interrupts In-Reply-To: from FreeBSD Development at "Jul 28, 97 09:23:24 pm" To: freebsd@atipa.com (FreeBSD Development) Date: Tue, 29 Jul 1997 13:26:13 +0930 (CST) Cc: mouth@ibm.net, hackers@FreeBSD.ORG, terry@lambert.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 FreeBSD Development stands accused of saying: > > On Mon, 28 Jul 1997 10:38:32 -0700 (MST), Terry Lambert wrote: > > > > > You can not share interrupts with ISA cards. Period. > > > You can share interrupts, but not use both SIMULTANEOUSLY. A very good > example would be to have LPT1: and a sound card on IRQ7 (both ISA). As > long as they have unique base addresses (0x378h and 0x220 for instance), > both devices can coexist. You just can't use them at the same time > without conflicting. Sharing IRQs is definitely not recommend, but I believe > your statement may require a bit more qualifying. More specifically, you can only allow _one_ device to drive an ISA IRQ line at any given time. ISA bus drivers use totem-pole outputs, so a device which has control of an interrupt line but not asserting an interrupt still counts as "driving". You can _only_ "share" interrupt lines by disabling drive of the line on one device before enabling it on another, or by using nonstandard ISA bus drivers (normally found only on cards specifically designed for this, eg. the AST 4-port serial adapter). See the comments and procedure in sioprobe() in i286/isa/sio.c and cross-reference the 8250 datasheet for an understanding of the quirks and complexities involved in getting this right. It is _not_ trivial. Far simpler to stick to "YOU CANNOT SHARE ISA INTERRUPTS BETWEEN CARDS". > Kevin -- ]] 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 Jul 28 20:59:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04855 for hackers-outgoing; Mon, 28 Jul 1997 20:59: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 UAA04835; Mon, 28 Jul 1997 20:59:35 -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 EAA19387; Tue, 29 Jul 1997 04:56:52 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id EAA22036; Tue, 29 Jul 1997 04:56:52 +0100 (BST) Message-Id: <199707290356.EAA22036@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: grog@FreeBSD.ORG cc: brian@awfulhak.org (Brian Somers), msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Tue, 29 Jul 1997 12:56:38 +0930." <199707290326.MAA01445@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 04:56:51 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brian Somers writes: > > > Brian Somers stands accused of saying: > > > > > > > > I'd like to add the following functionality to date(1) in -current, > > [.....] > > > Please also add : > > > > > > - The ability to parse timestamps in ctime()-like format. > > > > Yep. I think I'll fix the usage message too - shouldn't it be: > > > > [[yy[mm[dd[hh]]]]mm[.ss]] > > > > I must say, this format beats the mmddhhmmyy format in SYSV ! > > Sure, it beats it, but it also includes a gratuitous incompatibility. > I vote to leave it as it is. I would intend to allow both. I don't want to break anything. > Greg -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Mon Jul 28 21:14:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA05984 for hackers-outgoing; Mon, 28 Jul 1997 21:14:48 -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 VAA05965 for ; Mon, 28 Jul 1997 21:14:31 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA10221; Tue, 29 Jul 1997 13:43:28 +0930 (CST) From: Michael Smith Message-Id: <199707290413.NAA10221@genesis.atrad.adelaide.edu.au> Subject: Re: AMD PCNet/PCI troubles In-Reply-To: from Max Khon at "Jul 28, 97 06:48:58 pm" To: max@iclub.nsu.ru (Max Khon) Date: Tue, 29 Jul 1997 13:43:27 +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 Max Khon stands accused of saying: > > I don't have access to a current Linux kernel tree (as getting such an > > animal requires real effort, as opposed to the FreeBSD tree 8), so I can't > > check offhand and see if they actually report these errors to the console. > > but under FreeBSD (unlike Linux) networking sometimes is very slow > (~30-50K/s via ftp) Well, that's handy to know. How about giving us a complete description of the problem, including what (if anything) differs between the Linux and FreeBSD configurations of the card. For that matter, have you tried running Linux on this _particular_ machine? -- ]] 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 Jul 28 21:20:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06562 for hackers-outgoing; Mon, 28 Jul 1997 21:20:38 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06549 for ; Mon, 28 Jul 1997 21:20:28 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id WAA24399 for ; Mon, 28 Jul 1997 22:04:53 -0500 (CDT) Date: Mon, 28 Jul 1997 22:04:52 -0500 (CDT) From: Craig Johnston To: hackers@hub.freebsd.org Subject: iEEPro NIC + mach32 + XFree = splat 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 Problem summary: when I start X, the background comes up, my xclock comes up with a vertical line that's not supposed to be there on it and then the system locks up _hard_ -- no response at all to anything. System seems to do everything else just fine. The problem started after the addition of an Intel EEPro 10/100 NIC to the system, and when I remove the card, the problem disappears. Nothing exciting shows up in the output from the X server or in the system logs. The Xserver is XFree86 3.2. Hardware details that don't come up in the boot messages: Mobo: Abit IT5H rev 1.5 Graphics card: ATI Graphics Ultra Pro, mach32 vram pci My config file: machine "i386" cpu "I586_CPU" ident URTH maxusers 32 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ncr0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" flags 0x7 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device fxp0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device pty 32 pseudo-device bpf 2 options SYSVMSG options SYSVSEM options SYSVSHM Boot messages: FreeBSD 2.2-STABLE #0: Thu Jul 24 13:14:39 CDT 1997 root@urth.autarch.com:/usr/src/sys/compile/URTH CPU: AMD K5 PR166 (116.93-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x524 Stepping=4 Features=0x21bf real memory = 33554432 (32768K bytes) avail memory = 31326208 (30592K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 fxp0 rev 2 int a irq 11 on pci0:9 fxp0: Ethernet address 00:a0:c9:74:b6:be vga0 rev 2 int a irq 14 on pci0:11 ncr0 rev 4 int a irq 15 on pci0:15 (ncr0:1:0): "SEAGATE ST12400N SUN2.1G 8720" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) 2048MB (4194685 512 byte sectors) (ncr0:3:0): "TOSHIBA CD-ROM XM-5701TA 0167" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): 10.0 MB/s (100 ns, offset 8) can't get the size Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 flags 0x7 on motherboard npx0: INT 16 interface Anything I left out? regards, Craig From owner-freebsd-hackers Mon Jul 28 22:36:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11144 for hackers-outgoing; Mon, 28 Jul 1997 22:36:43 -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 WAA11139 for ; Mon, 28 Jul 1997 22:36:40 -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 BAA26414; Tue, 29 Jul 1997 01:36:28 -0400 Date: Tue, 29 Jul 1997 01:36:43 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD Development cc: John Kelly , hackers@FreeBSD.ORG, Terry Lambert Subject: Re: Sharing interrupts 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, 28 Jul 1997, FreeBSD Development wrote: > > > On Tue, 29 Jul 1997, John Kelly wrote: > > > On Mon, 28 Jul 1997 10:38:32 -0700 (MST), Terry Lambert wrote: > > > > > You can not share interrupts with ISA cards. Period. > > > You can share interrupts, but not use both SIMULTANEOUSLY. A very good > example would be to have LPT1: and a sound card on IRQ7 (both ISA). As > long as they have unique base addresses (0x378h and 0x220 for instance), > both devices can coexist. You just can't use them at the same time > without conflicting. Sharing IRQs is definitely not recommend, but I believe > your statement may require a bit more qualifying. You must be _very_ innocent. Terry is right on the money here. Go ahead, share your irq 7. Then you can join the large group of FreeBSDers who claim the printer driver's broken (it isn't). That's not fair, I'm too tired and shouldn't be so harsh, but really, Terry _is_ right here, there are strong hardware reasons that it's so. I'll let Terry respond, he seems to like typing more than I. > > Kevin > > > > ----------------------------+----------------------------------------------- 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 Jul 28 23:55:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA17135 for hackers-outgoing; Mon, 28 Jul 1997 23:55:58 -0700 (PDT) Received: from konig.elte.hu (konig.elte.hu [157.181.6.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA17091 for ; Mon, 28 Jul 1997 23:55:36 -0700 (PDT) Received: from localhost (sebesty@localhost) by konig.elte.hu (8.8.3/8.7.3/7s) with SMTP id IAA11524 for ; Tue, 29 Jul 1997 08:55:10 +0200 Date: Tue, 29 Jul 1997 08:55:10 +0200 (MET DST) From: Zoltan Sebestyen X-Sender: sebesty@konig To: freebsd-hackers@freebsd.org Subject: communcating with cdrom 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 porting a cdplayer to FreeBSD and run into several problems. The first one was that in FreeBSD there are no constants describing a cdrom's tracks wether they are audio or data tracks. Now I've found out that the control tag of cd_toc_entry structure is 4, if the track in question is a data track, at least for ATAPI devices. But I still have some questions. This cdplayer allows to mount the first data track of the cd, if there's any but it seems that FreeBSD doesn't allow to open the device (actually it's /dev/wcd0c) for ioctl calls and to mount the same device at the same time. Is this true? Should I redirect the ioctl calls to the raw device (/dev/rwcd0c) instead of the block one? Another problem is that I just can't close the tray of the cdrom neither with the CDIOCCLOSE ioctl call nor with the button on the cdrom player after opening it. If I closed the open device, I could close the cd manually, but it didn't solve the problem, because with the tray open I can't open the device again. If you can help me, please let me know. Thanks in advance -------------------------------------------------------------------------------- Sebestyen Zoltan It all seems so stupid, it makes me want to give up. szoli@caesar.elte.hu But why should I give up, when it all seems so stupid? From owner-freebsd-hackers Tue Jul 29 00:15:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19282 for hackers-outgoing; Tue, 29 Jul 1997 00:15:13 -0700 (PDT) Received: from baygate.bayarea.net (root@baygate.bayarea.net [204.71.212.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA19268 for ; Tue, 29 Jul 1997 00:15:07 -0700 (PDT) Received: from [205.219.66.123] (pppmaxsc2-123.bayarea.net [205.219.66.123]) by baygate.bayarea.net (8.8.5/8.8.5) with SMTP id AAA24104; Tue, 29 Jul 1997 00:11:57 -0700 (PDT) Message-Id: <199707290711.AAA24104@baygate.bayarea.net> Subject: Re: VirtualPC and FreeBSD Date: Tue, 29 Jul 97 00:22:47 -0700 From: Eric Traut To: "John Mitchell" cc: "Jorg Brown" , "John Mitchell" , Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jake, I'm the lead engineer of Connectix Virtual PC 1.0. I received your bug report regarding FreeBSD second-hand through a coworker. You were correct - the problem is a bug in the Pentium emulator within Virtual PC 1.0. The details: The exception reported by the kernel is caused by the execution of a WRMSR (write to model-specific register) instruction. Because of Intel's poor documentation for this instruction and its rare usage (before this I've never seen it executed), we never implemented it. FreeBSD's kernel executes a WRMSR instruction to clear the TSC (time stamp count) register (MSR index 0x10). I have implemented the missing functionality, and the fix will probably make its way out in an upcoming Virtual PC bug fix update. Thanks for the bug report. Hope you are enjoying Virtual PC otherwise. Eric Traut Virtual PC Lead Engineer Connectix Corp. ----------------------------- Jake Hamby, jehamby@be.com wrote: >Just for fun, I tried to boot FreeBSD 2.2.2 from within the VirtualPC >emulator for MacOS, which claims to simulate a full Intel Pentium PC at >the hardware level. It can run unmodified version of Windows 95, NT, >OS/2, and NextStep, and so I assumed it wouldn't have much trouble with >FreeBSD. > >Unfortunately, immediately after loading the kernel, FreeBSD panicked with >this error: > >Fatal trap 1: privileged instruction fault while in kernel mode > >instruction ptr = 0x8:0xf01b99aa >stack ptr = 0x10:0xefbfff38 >frame ptr = 0x10:0xefbfff50 >code segment = base 0x0, limit 0xfffff type 0x1b > = DPL 0, pres 1, def 32 1, grant >process eflags = IOPL = 0 >current process = 0 () >interrupt mask = net tty bio >panic: privileged instruction fault > >Obviously, this is a bug in Connectix's CPU emulator. But I'm curious if >anyone could give any information off-hand as to what they might be doing >wrong that would trigger such an error from the FreeBSD kernel. > >Thanks, >Jake Hamby From owner-freebsd-hackers Tue Jul 29 00:16:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA19430 for hackers-outgoing; Tue, 29 Jul 1997 00:16:31 -0700 (PDT) Received: from mail.be.com (be.be.com [207.113.215.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA19420 for ; Tue, 29 Jul 1997 00:16:26 -0700 (PDT) Received: from localhost by mail.be.com with smtp (Smail3.1.29.1 #1) id m0wt6YU-000ofgC; Tue, 29 Jul 97 00:18 PDT Date: Tue, 29 Jul 1997 00:09:12 -0800 Message-ID: <19970729000912.PM-bhtfkqph@Adam.BeOS> MIME-Version: 1.0 X-Mailer: Adam 1.0 on BeOS Subject: Re: Anyone tried VirtualPC with FreeBSD? To: Michael Smith Cc: From: Jake Hamby 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 AAA19424 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: >Ok. This may be the wrmsr() call : > >wrmsr(u_int msr, quad_t newval) >{ > __asm __volatile(".byte 0x0f, 0x30" : : "A" (newval), "c" (msr)); >} > >which is conditional on the CPU type reported being a P5 or P6, which >is what it claims to be. > >It would be very interesting if you were to build a GENERIC kernel, >stick it on a bootstrap-enabled floppy (do you know how to build a >bootable FreeBSD floppy? ask if not), and modify calibrate_clocks in >sys/i386/isa/clock.c to remove the wrmsr() call. > >You might also try removing the code that calls rdtsc() towards the >bottom. Unfortunately, I don't have time to play around with this any further. Thanks for tracking this down, though. I suspect FreeBSD is doing the right thing. At least if anyone else complains that FreeBSD isn't compatible with VirtualPC in the future, you'll have a starting point from which to try patching the problem. Also, I'll go ahead and forward your mail to Connectix tech support, just to let them know an area of their emulation that might be weak. By the way, I just installed a PC Compatibility Card that was lying around here, and it does boot FreeBSD, but it's completely impossible to install, because the card provides absolutely no support for hard drive, floppy drive, CD-ROM drive, or network! All of those functions are supported through 16-bit real mode drivers, which means you can only use this card for DOS, Windows 3.1, or Windows 95. :( Cheers, Jake From owner-freebsd-hackers Tue Jul 29 00:21:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA20149 for hackers-outgoing; Tue, 29 Jul 1997 00:21:15 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA20111 for ; Tue, 29 Jul 1997 00:21:08 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id RAA01540; Tue, 29 Jul 1997 17:21:03 +1000 (EST) Date: Tue, 29 Jul 1997 17:21:02 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: Netscape Communicator and ppp -alias 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 Has anyone looked at getting ppp -alias to work for Netscape's Communicator facility, to allow conferencing with whiteboards etc. Thanks, /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Tue Jul 29 00:25:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA20605 for hackers-outgoing; Tue, 29 Jul 1997 00:25:35 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA20591 for ; Tue, 29 Jul 1997 00:25:26 -0700 (PDT) Received: from default (hahaha@max008-49.netroplex.com [207.212.27.49]) by netroplex.com (8.8.5/8.8.2) with ESMTP id AAA24546 for ; Tue, 29 Jul 1997 00:25:55 -0700 (PDT) Message-Id: <199707290725.AAA24546@netroplex.com> From: "Rod Ebrahimi" To: Subject: Pentium II? Date: Tue, 29 Jul 1997 00:24:19 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 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 Recently I was looking into some of Dell's server systems and found that they offer Pentium II 233mhz and 266mhz... I was wondering if anyone had any experience with these types of systems (Pentium II) or knows how they will interact with FreeBSD... Thank You. From owner-freebsd-hackers Tue Jul 29 01:54:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25670 for hackers-outgoing; Tue, 29 Jul 1997 01:54:09 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA25652 for ; Tue, 29 Jul 1997 01:54:01 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.6.12/8.6.12) with ESMTP id BAA00681; Tue, 29 Jul 1997 01:54:31 -0700 Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id BAA13807; Tue, 29 Jul 1997 01:52:00 -0700 (PDT) Date: Tue, 29 Jul 1997 01:52:00 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199707290852.BAA13807@dog.farm.org> To: brian@awfulhak.org (Brian Somers) Cc: freebsd-hackers@freebsd.org Subject: Re: date(1) Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199707290356.EAA22036@awfulhak.org> you wrote: > > > Yep. I think I'll fix the usage message too - shouldn't it be: > > > > > > [[yy[mm[dd[hh]]]]mm[.ss]] It should become [[[cc]yy[mm[dd[hh]]]]mm[.ss]] or we are screwed in 866 days from now. > > > I must say, this format beats the mmddhhmmyy format in SYSV ! /usr/bin/date [-u] [[mmdd]HHMM | mmddHHMM[cc]yy][.SS] (quote from Solaris 2.5.1 manpage) -- I have BSD, but SYSV has me. -- heared from Igor Uwkin (uwka@big.Sun.nsk.SU) From owner-freebsd-hackers Tue Jul 29 02:03:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA26299 for hackers-outgoing; Tue, 29 Jul 1997 02:03:51 -0700 (PDT) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA26294 for ; Tue, 29 Jul 1997 02:03:46 -0700 (PDT) Received: from brother.ludd.luth.se (gozer@brother.ludd.luth.se [130.240.16.78]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id LAA01169 for ; Tue, 29 Jul 1997 11:03:44 +0200 Date: Tue, 29 Jul 1997 11:03:42 +0200 (MET DST) From: Johan Larsson To: FreeBSD Hackers Subject: nls in libc 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 libc support nls like in NetBSD? If not, how can we do to make that happen, because we want that, right? :-) How is the overhead nls support? ./johan -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * finger gozer@mother.ludd.luth.se for more information... +-+-+-+ * * Powered by FreeBSD. http://www.se.freebsd.org/ +-+-+-+-+-+-+-+-+ * From owner-freebsd-hackers Tue Jul 29 02:19:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27201 for hackers-outgoing; Tue, 29 Jul 1997 02:19:04 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA27193 for ; Tue, 29 Jul 1997 02:18:59 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id FAA17410 for ; Tue, 29 Jul 1997 05:24:37 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Tue, 29 Jul 1997 05:24:37 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: FreeBSD Hackers Subject: HD transfer? 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've been running a gateway/router on a failing 120meg hard drive for some time, i recently got a hold of a cheap 250 meg drive, is there a way to transfer my system to the drive without messing up the /dev directory and other stuff? Alfred From owner-freebsd-hackers Tue Jul 29 03:40:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA03049 for hackers-outgoing; Tue, 29 Jul 1997 03:40:20 -0700 (PDT) Received: from vader.runit.sintef.no (vader.runit.sintef.no [129.241.100.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA03036 for ; Tue, 29 Jul 1997 03:40:16 -0700 (PDT) Received: from runit.sintef.no (localhost [127.0.0.1]) by vader.runit.sintef.no (8.8.5/8.7.3) with ESMTP id MAA18633 for ; Tue, 29 Jul 1997 12:40:09 +0200 (MEST) Message-Id: <199707291040.MAA18633@vader.runit.sintef.no> To: freebsd-hackers@freebsd.org Subject: FreeBSD, APM and laptops From: Havard.Eidnes@runit.sintef.no X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Date: Tue, 29 Jul 1997 12:40:09 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA03038 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, a while ago I installed FreeBSD 2.2.2-RELEASE with the matching PAO patches on my laptop, primarily to be able to run the Xi Graphics X server. The reason I run the Xi Graphics server is that my laptop has the NeoMagic 2090 chip, and it's not (and probably won't be) supported by XFree86 due to NeoMagic's policy wrt. low-level programming documentation availability. (Sigh.) Be that as it may. However, the most annoying problem with my configuration is that it appears that APM does not work as intended, in particular: doing a "suspend" causes the machine to freeze, not to enter the suspend state, even if I've powered down both PCMCIA cards before doing the suspend. Is this a known problem? On which mailing lists should I listen to to be aware of any progress on solving this problem? (I get enough mail as it is, so volume is of concern.) Please include me in any replies as I currently don't subscribe to this mailing list. Regards, - Håvard From owner-freebsd-hackers Tue Jul 29 04:14:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA04891 for hackers-outgoing; Tue, 29 Jul 1997 04:14: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 EAA04883 for ; Tue, 29 Jul 1997 04:14:02 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA12764; Tue, 29 Jul 1997 20:43:36 +0930 (CST) From: Michael Smith Message-Id: <199707291113.UAA12764@genesis.atrad.adelaide.edu.au> Subject: Re: FreeBSD, APM and laptops In-Reply-To: <199707291040.MAA18633@vader.runit.sintef.no> from "Havard.Eidnes@runit.sintef.no" at "Jul 29, 97 12:40:09 pm" To: Havard.Eidnes@runit.sintef.no Date: Tue, 29 Jul 1997 20:43:35 +0930 (CST) 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 Havard.Eidnes@runit.sintef.no stands accused of saying: > server. The reason I run the Xi Graphics server is that my laptop > has the NeoMagic 2090 chip, and it's not (and probably won't be) > supported by XFree86 due to NeoMagic's policy wrt. low-level > programming documentation availability. (Sigh.) Be that as it may. *spit* at NeoMagic, but a big thankyou to Xi. > However, the most annoying problem with my configuration is that it > appears that APM does not work as intended, in particular: doing a > "suspend" causes the machine to freeze, not to enter the suspend > state, even if I've powered down both PCMCIA cards before doing the > suspend. > > Is this a known problem? APM BIOSsen in general are a known problem. 8( Are you enabling APM first, with 'apmconf -e'? How are you trying to suspend, with 'zzz', or 'apmconf -z', or by closing the lid? > On which mailing lists should I listen to to be aware of any > progress on solving this problem? (I get enough mail as it is, so > volume is of concern.) The -mobile list is quiet, and there would definitely be traffic there in the case of any results. -- ]] 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 Tue Jul 29 04:46:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA06346 for hackers-outgoing; Tue, 29 Jul 1997 04:46:37 -0700 (PDT) Received: from vader.runit.sintef.no (vader.runit.sintef.no [129.241.100.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA06341 for ; Tue, 29 Jul 1997 04:46:32 -0700 (PDT) Received: from runit.sintef.no (localhost [127.0.0.1]) by vader.runit.sintef.no (8.8.5/8.7.3) with ESMTP id NAA20155; Tue, 29 Jul 1997 13:46:18 +0200 (MEST) Message-Id: <199707291146.NAA20155@vader.runit.sintef.no> To: msmith@atrad.adelaide.edu.au Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD, APM and laptops From: Havard.Eidnes@runit.sintef.no In-Reply-To: Your message of "Tue, 29 Jul 1997 20:43:35 +0930 (CST)" References: <199707291113.UAA12764@genesis.atrad.adelaide.edu.au> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Date: Tue, 29 Jul 1997 13:46:17 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id EAA06342 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > However, the most annoying problem with my configuration is that it > > appears that APM does not work as intended, in particular: doing a > > "suspend" causes the machine to freeze, not to enter the suspend > > state, even if I've powered down both PCMCIA cards before doing the > > suspend. > > > > Is this a known problem? > > APM BIOSsen in general are a known problem. 8( For what it's worth, FreeBSD says the following during boot about APM: apm0 on isa apm: found APM BIOS version 1.1 It's a Dell Latitude XPi. FWIW, I had NetBSD installed prior to installing FreeBSD on this laptop, and there suspending worked just fine (modulo PCMCIA issues). > Are you enabling APM first, with 'apmconf -e'? No. Do I need to? I didn't need to do that when my laptop ran NetBSD, and foolishly (?) I assumed I didn't have to fiddle anything extra to enable power management in FreeBSD either. It appears problematic to find the default state for the variables apmconf provide an interface to... Hmm, doing 'apmconf -e' may have solved at least part of my problem. I think I need to experiment some more before the final conclusion, but now I have at least once managed to take the PC into and out of the suspend state, although the behaviour appears somewhat erratic (sometimes it "auto-resumes" after about a minute...). > How are you trying to suspend, with 'zzz', or 'apmconf -z', or by > closing the lid? Before I did 'apmconf -e', zzz, pressing the "suspend" function key or closing the lid all have the same effect -- the machine froze. > > On which mailing lists should I listen to to be aware of any > > progress on solving this problem? (I get enough mail as it is, so > > volume is of concern.) > > The -mobile list is quiet, and there would definitely be traffic there > in the case of any results. Ok, sounds like I need to subscribe there. Thanks! - Håvard From owner-freebsd-hackers Tue Jul 29 05:07:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA07232 for hackers-outgoing; Tue, 29 Jul 1997 05:07:27 -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 FAA07219 for ; Tue, 29 Jul 1997 05:07:20 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA13070; Tue, 29 Jul 1997 21:36:40 +0930 (CST) From: Michael Smith Message-Id: <199707291206.VAA13070@genesis.atrad.adelaide.edu.au> Subject: Re: FreeBSD, APM and laptops In-Reply-To: <199707291146.NAA20155@vader.runit.sintef.no> from "Havard.Eidnes@runit.sintef.no" at "Jul 29, 97 01:46:17 pm" To: Havard.Eidnes@runit.sintef.no Date: Tue, 29 Jul 1997 21:36:40 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, 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 Havard.Eidnes@runit.sintef.no stands accused of saying: > > It's a Dell Latitude XPi. FWIW, I had NetBSD installed prior to > installing FreeBSD on this laptop, and there suspending worked > just fine (modulo PCMCIA issues). Their code is quite possibly better. > > Are you enabling APM first, with 'apmconf -e'? > > No. Do I need to? I didn't need to do that when my laptop ran > NetBSD, and foolishly (?) I assumed I didn't have to fiddle > anything extra to enable power management in FreeBSD either. Yes. For some time, automatically enabling power management was risky because the APM interface would spontaneously explode on the first call, making the kernel unbootable on those machines. > It appears problematic to find the default state for the > variables apmconf provide an interface to... I think I unserstand you here. Apmconf should at most be a wrapper to sysctl (but isn't). > Hmm, doing 'apmconf -e' may have solved at least part of my > problem. I think I need to experiment some more before the final > conclusion, but now I have at least once managed to take the PC > into and out of the suspend state, although the behaviour appears > somewhat erratic (sometimes it "auto-resumes" after about a > minute...). I haven't observed this, although I have seen 'zzz' suspend and then immediately resume again. If you have any time to investigate/work on this, your support would be greatly appreciated. If not, keep in touch so that the issues you've raised don't get lost. -- ]] 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 Tue Jul 29 05:16:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA07726 for hackers-outgoing; Tue, 29 Jul 1997 05:16:41 -0700 (PDT) Received: from beta.mcit.com (beta.mcit.com [199.249.19.143]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA07721 for ; Tue, 29 Jul 1997 05:16:38 -0700 (PDT) Received: from omzrelay.mcit.com (omzrelay.mcit.com [166.37.204.49]) by beta.mcit.com (8.8.6/) with ESMTP id HAA20492 for ; Tue, 29 Jul 1997 07:16:07 -0500 (CDT) Received: from pop3a.mail.mci.com (pop3a.mail.mci.com [166.37.172.2]) by omzrelay.mcit.com (8.8.5/) with ESMTP id HAA32018 for ; Tue, 29 Jul 1997 07:16:07 -0500 (CDT) Received: from rip01643 ([166.35.248.180]) by pop3a.mail.mci.com (Post.Office MTA Undefined release Undefined ID# 1-123U25000L1S10) with ESMTP id AAA25972 for ; Tue, 29 Jul 1997 08:16:06 -0400 Message-ID: <33DDDEB3.53182D6A@mci.com> Date: Tue, 29 Jul 1997 07:14:44 -0500 From: "Jeff Kreska" Organization: MCI X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Adaptec 2940UW X-Priority: 3 (Normal) References: <18546.869857590@time.cdrom.com> <33DC8E66.37223549@mci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jeff Kreska wrote: > Jordan K. Hubbard wrote: > > > > Is anybody working on resolving the problems with the Adapatec > > 2940. It > > > appears that the problems exist in all tree's. I have personaly > > used > > > the 2.1, latest 2.2snap, and 3.0snap with none of them working > 100%. > > > > Odd - I'm having no problems with my 2940UWs at all. What was > > the PR#? > > > > Critical problems > > o [1997/07/11] kern/4076 Adaptec 2940 and non-wide devices > Here is the output from a boot that caueses the last device in the SCSI chain to be disabeled.If I go into the SCSI Bios and disable wide negotiation for the CD and DAT all works fine. It seems odd that I would have to do this, and it could be a burden if I connected a wide device to the bus and forgot to go re-enable wide negotiation. Any suggestions??? FreeBSD 2.2-961014-SNAP #5: Mon Dec 2 13:08:08 CST 1996 root@flowmaster.jeff.com:/usr/src/sys/compile/FLOWMASTER Calibrating clock(s) relative to mc146818A clock... i586 clock: 133652352 Hz, i8254 clock: 1193325 Hz CPU: Pentium (133.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62529536 (61064K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 11 on pci0:17 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "HP C3325A 5293" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers (ahc0:2:0): "ARCHIVE Python 25501-XXX 2.50" type 1 removable SCSI 2 st0(ahc0:2:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers ahc0: board is not responding (ahc0:4:0): timed out in dataout phase, SCSISIGI == 0x0 ahc0: Issued Channel A Bus Reset #2. 1 SCBs aborted vga0 rev 2 int a irq 10 on pci0:18 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 9 on isa ed0: address 00:80:ad:0d:0f:67, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in .... deleted ... npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. changing root device to sd0a sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred, retries:2 -- Regards, Jeff mailto:jeff.kreska@mci.com From owner-freebsd-hackers Tue Jul 29 05:51:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA09592 for hackers-outgoing; Tue, 29 Jul 1997 05:51:36 -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 FAA09585 for ; Tue, 29 Jul 1997 05:51:34 -0700 (PDT) Message-Id: <199707291249.IAA13511@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Tue, 29 Jul 1997 08:52:25 -0400 (EDT) From: Jamie Bowden To: FreeBSD Development cc: John Kelly , hackers@freebsd.org, Terry Lambert Subject: Re: Sharing interrupts In-Reply-To: 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, 28 Jul 1997, FreeBSD Development wrote: > > > On Tue, 29 Jul 1997, John Kelly wrote: > > > On Mon, 28 Jul 1997 10:38:32 -0700 (MST), Terry Lambert wrote: > > > > > You can not share interrupts with ISA cards. Period. > > > You can share interrupts, but not use both SIMULTANEOUSLY. A very good > example would be to have LPT1: and a sound card on IRQ7 (both ISA). As > long as they have unique base addresses (0x378h and 0x220 for instance), > both devices can coexist. You just can't use them at the same time > without conflicting. Sharing IRQs is definitely not recommend, but I believe > your statement may require a bit more qualifying. I wouldn't call what you describe sharing an interrupt. I would compare it to sleeping with someone's girlfriend and hoping they don't happen to try sleeping with her at the same time, cause who the hell knows what will happen then (of course, this breaks down at this point, due to the fact that some people don't mind sharing. Your hardware is about as forgiving as an old New England WASP). Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Tue Jul 29 07:10:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15421 for hackers-outgoing; Tue, 29 Jul 1997 07:10:58 -0700 (PDT) Received: from vader.runit.sintef.no (vader.runit.sintef.no [129.241.100.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15416 for ; Tue, 29 Jul 1997 07:10:54 -0700 (PDT) Received: from runit.sintef.no (localhost [127.0.0.1]) by vader.runit.sintef.no (8.8.5/8.7.3) with ESMTP id QAA22085; Tue, 29 Jul 1997 16:10:47 +0200 (MEST) Message-Id: <199707291410.QAA22085@vader.runit.sintef.no> To: msmith@atrad.adelaide.edu.au Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD, APM and laptops From: Havard.Eidnes@runit.sintef.no In-Reply-To: Your message of "Tue, 29 Jul 1997 21:36:40 +0930 (CST)" References: <199707291206.VAA13070@genesis.atrad.adelaide.edu.au> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Date: Tue, 29 Jul 1997 16:10:47 +0200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id HAA15417 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If you have any time to investigate/work on this, your support would > be greatly appreciated. If not, keep in touch so that the issues > you've raised don't get lost. Ok. I'll probably return to the issue, but "not right now"... Again, thanks, - Håvard From owner-freebsd-hackers Tue Jul 29 07:27:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16833 for hackers-outgoing; Tue, 29 Jul 1997 07:27:51 -0700 (PDT) Received: from onyx.atipa.com (user4188@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA16827 for ; Tue, 29 Jul 1997 07:27:46 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 29 Jul 1997 14:29:41 -0000 Date: Tue, 29 Jul 1997 08:29:41 -0600 (MDT) From: FreeBSD Mailing List X-Sender: freebsd@dot.ishiboo.com To: Rod Ebrahimi cc: hackers@FreeBSD.ORG Subject: Re: Pentium II? In-Reply-To: <199707290725.AAA24546@netroplex.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 Tue, 29 Jul 1997, Rod Ebrahimi wrote: > Recently I was looking into some of Dell's server systems and found that > they offer Pentium II 233mhz and 266mhz... I was wondering if anyone had > any experience with these types of systems (Pentium II) or knows how they > will interact with FreeBSD... > > Thank You. > The PPro is still faster for a true 32-bit OS, primarily due to the fact that the L2 is 1:1 with the CPU clock. On the Pentium II, the L2 caching is at 1/2 the CPU clock. The PII runs 16-bit software better and adds MMX extensions, but for a network server the PPro will still be faster. Kevin From owner-freebsd-hackers Tue Jul 29 07:49:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA18380 for hackers-outgoing; Tue, 29 Jul 1997 07:49:45 -0700 (PDT) Received: from pangeia.com.br (spliff.pangeia.com.br [200.239.53.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA18355 for ; Tue, 29 Jul 1997 07:49:17 -0700 (PDT) Received: from localhost (nelson@localhost) by pangeia.com.br (8.8.6/8.8.0) with SMTP id MAA20167 for ; Tue, 29 Jul 1997 12:11:28 -0300 Date: Tue, 29 Jul 1997 12:11:28 -0300 (EST) From: Nelson Murilo To: hackers@freebsd.org Subject: SCSI 1542 error 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 have a problem with maybe more well know board. One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, my console say: /kernel: sd0 (aha0:0:0): timeout /kernel: adapter not talking commands... frozen?! /kernel: aha0: MBO 02 and not 00 (free) [...] Next step as change speed for 5.0 (default), disable all shadow and disable check parity, but the problem not stop. After display this errors in console none command are possible. # pwd Input/output error # /sbin/shutdown -r now /sbin/shutdown: I/O error If anybody have any hint, please send for nelson@pangeia.com.br (I'm not in this list). Thanks, -- ./nelson -murilo From owner-freebsd-hackers Tue Jul 29 08:06:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19663 for hackers-outgoing; Tue, 29 Jul 1997 08:06:17 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19656 for ; Tue, 29 Jul 1997 08:06:11 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id KAA11272; Tue, 29 Jul 1997 10:11:04 -0500 (CDT) Message-Id: <199707291511.KAA11272@iworks.InterWorks.org> Date: Tue, 29 Jul 1997 10:11:04 -0500 (CDT) From: "Daniel M. Eischen" To: Jeff.Kreska@MCI.Com, freebsd-hackers@FreeBSD.ORG Subject: Re: Adaptec 2940UW Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Here is the output from a boot that caueses the last device in the SCSI > chain to be disabeled.If I go into the SCSI Bios and disable wide > negotiation for the CD and DAT all works fine. It seems odd that I > would have to do this, and it could be a burden if I connected a wide > device to the bus and forgot to go re-enable wide negotiation. [...] > (ahc0:0:0): "HP C3325A 5293" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2069MB (4238836 512 byte sectors) > ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers > (ahc0:2:0): "ARCHIVE Python 25501-XXX 2.50" type 1 removable SCSI 2 > st0(ahc0:2:0): Sequential-Access density code 0x13, 512-byte blocks, > write-enabled > ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers What device is at ID 4? Can you boot verbose (-v)? Some older SCSI devices will choke on a wide negotiation message, so it does become necessary to disable it for that device. What happens if you disable wide negotiation on the Archive only? Does the unit at ID 4 still choke? I would think that whatever is at ID 4 just cannot handle a wide negotiation attempt. I don't understand your statement "if I connected a wide device to the bus and forgot to re-enable wide negotation". If you've got narrow devices on the bus, set them for non-wide and set all the unused IDs for wide. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Tue Jul 29 08:09:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19911 for hackers-outgoing; Tue, 29 Jul 1997 08:09:58 -0700 (PDT) Received: from marlin.exis.net (root@marlin.exis.net [205.252.72.102]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19902 for ; Tue, 29 Jul 1997 08:09:54 -0700 (PDT) Received: from sailfish.exis.net (sailfish.exis.net [205.252.72.104]) by marlin.exis.net (8.8.4/8.8.5) with SMTP id LAA02167; Tue, 29 Jul 1997 11:07:48 -0400 Date: Tue, 29 Jul 1997 07:04:07 -0400 (EDT) From: Stefan Molnar To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Netscape Communicator and ppp -alias 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 > Has anyone looked at getting ppp -alias to work for Netscape's > Communicator facility, to allow conferencing with whiteboards etc. It should work just fine, I have used it and as with alot of other clients pulling off of the fbsd box. I have only a problem with is KHAN and KALI, but since that is doing something strange already I was not sure it would work at all. Stefan From owner-freebsd-hackers Tue Jul 29 08:44:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22716 for hackers-outgoing; Tue, 29 Jul 1997 08:44:09 -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 IAA22705 for ; Tue, 29 Jul 1997 08:44:04 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA12346; Tue, 29 Jul 1997 09:42:35 -0600 (MDT) Date: Tue, 29 Jul 1997 09:42:35 -0600 (MDT) Message-Id: <199707291542.JAA12346@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nelson Murilo Cc: hackers@freebsd.org Subject: Re: SCSI 1542 error 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 > I'm have a problem with maybe more well know board. > > One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, > my console say: You're not the first. It appears to me from watching the mailing list that the 1542 boards are not supported in 2.2. *Many* people have reported problems with them, which unfortunately means that I can no longer do 2.2 development at home. :( Nate From owner-freebsd-hackers Tue Jul 29 09:29:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26742 for hackers-outgoing; Tue, 29 Jul 1997 09:29:49 -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 JAA26730 for ; Tue, 29 Jul 1997 09:29:46 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.6/8.7.3) id SAA00257; Tue, 29 Jul 1997 18:28:37 +0200 (MEST) From: Søren Schmidt Message-Id: <199707291628.SAA00257@sos.freebsd.dk> Subject: Re: SCSI 1542 error In-Reply-To: <199707291542.JAA12346@rocky.mt.sri.com> from Nate Williams at "Jul 29, 97 09:42:35 am" To: nate@mt.sri.com (Nate Williams) Date: Tue, 29 Jul 1997 18:28:37 +0200 (MEST) Cc: nelson@pangeia.com.br, 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 Nate Williams who wrote: > > I'm have a problem with maybe more well know board. > > > > One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, > > my console say: > > You're not the first. It appears to me from watching the mailing list > that the 1542 boards are not supported in 2.2. *Many* people have > reported problems with them, which unfortunately means that I can no > longer do 2.2 development at home. :( Hmm, I run 2.2-STABLE on my junkbox, its an old 100Mhz 486 32MB with a 1542B with a 1.3G disk and a 525MB tape, works like a charm... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Tue Jul 29 09:31:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26957 for hackers-outgoing; Tue, 29 Jul 1997 09:31:55 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26944 for ; Tue, 29 Jul 1997 09:31:51 -0700 (PDT) Received: from slip129-37-53-122.ca.us.ibm.net (slip129-37-53-122.ca.us.ibm.net [129.37.53.122]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id QAA125742; Tue, 29 Jul 1997 16:31:42 GMT From: mouth@ibm.net (John Kelly) To: FreeBSD Development Cc: hackers@FreeBSD.ORG, Terry Lambert Subject: Sharing interrupts (on ISA serial cards) Date: Tue, 29 Jul 1997 16:33:46 GMT Message-ID: <33de18a4.1100092@smtp-gw01.ny.us.ibm.net> References: In-Reply-To: X-Mailer: Forte Agent 1.01/16.397 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 JAA26947 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 28 Jul 1997 21:23:24 -0600 (MDT), you wrote: >You can share interrupts, but not use both SIMULTANEOUSLY. A very good >example would be to have LPT1: and a sound card on IRQ7 (both ISA). As >long as they have unique base addresses (0x378h and 0x220 for instance), >both devices can coexist. You just can't use them at the same time >without conflicting. Correct, and that is true when you have tri-state drivers on both devices and you do not have both open at the same time. > Sharing IRQs is definitely not recommend, but I believe your statement may > require a bit more qualifying. I'm only talking about two or more ISA serial adapters sharing the same interrupt. I'm not talking about two different types of devices sharing the same interrupt. Sharing an edge-triggered, ISA interrupt among two or more serial cards can be done if you have a little knowledge of electricity, a few $0.50 parts, and a steady hand with a soldering iron. If anyone wants to understand the electrical details of how and why it works, I will write it up and post it. It will take a couple of hours to write, so I won't bother unless someone is interested in knowing more about it. John From owner-freebsd-hackers Tue Jul 29 09:32:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27107 for hackers-outgoing; Tue, 29 Jul 1997 09:32:52 -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 JAA27102 for ; Tue, 29 Jul 1997 09:32:48 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA12693; Tue, 29 Jul 1997 10:32:32 -0600 (MDT) Date: Tue, 29 Jul 1997 10:32:32 -0600 (MDT) Message-Id: <199707291632.KAA12693@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Søren Schmidt Cc: nate@mt.sri.com (Nate Williams), nelson@pangeia.com.br, hackers@freebsd.org Subject: Re: SCSI 1542 error In-Reply-To: <199707291628.SAA00257@sos.freebsd.dk> References: <199707291542.JAA12346@rocky.mt.sri.com> <199707291628.SAA00257@sos.freebsd.dk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > I'm have a problem with maybe more well know board. > > > > > > One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, > > > my console say: > > > > You're not the first. It appears to me from watching the mailing list > > that the 1542 boards are not supported in 2.2. *Many* people have > > reported problems with them, which unfortunately means that I can no > > longer do 2.2 development at home. :( > > Hmm, I run 2.2-STABLE on my junkbox, its an old 100Mhz 486 32MB with a > 1542B with a 1.3G disk and a 525MB tape, works like a charm... That's good to know. I've seen a half-dozen or more complaints from 1542B/C users in the last few months who've had problems with the board. There haven't been *any* responses from the SCSI folks, so I assumed they didn't care. Check the archives if interested. Nate From owner-freebsd-hackers Tue Jul 29 09:52:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28408 for hackers-outgoing; Tue, 29 Jul 1997 09:52:04 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28400 for ; Tue, 29 Jul 1997 09:52:01 -0700 (PDT) Received: from slip129-37-53-122.ca.us.ibm.net (slip129-37-53-122.ca.us.ibm.net [129.37.53.122]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id QAA103440; Tue, 29 Jul 1997 16:51:41 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: freebsd@atipa.com (FreeBSD Development), hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Tue, 29 Jul 1997 16:53:40 GMT Message-ID: <33df1cb8.2144876@smtp-gw01.ny.us.ibm.net> References: <199707290356.NAA10082@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707290356.NAA10082@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 JAA28402 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >More specifically, you can only allow _one_ device to drive an ISA >IRQ line at any given time. Not strictly true, see below. >ISA bus drivers use totem-pole outputs, so a device which has control >of an interrupt line but not asserting an interrupt still counts as >"driving" A standard totem-pole output is either driving the line to ground (logic low) or 3.5-4.5 volts (logic high). But if the device has a tri-state driver, that third state is "floating," and it can be on the line at the same time in the floating state without interfering with another device. But in any event, that's not what I'm talking about. I'm talking about sharing an edge-triggered, ISA interrupt among two or more serial cards (with single or multiple UARTS per card). >See the comments and procedure in sioprobe() in i286/isa/sio.c and I have, and that documentation does not tell the electrical story. >cross-reference the 8250 datasheet for an understanding of the quirks >and complexities involved in getting this right. It is _not_ trivial. I have. It's not hard at all. In the 8259 datasheet, what many people overlook are its electrical characteristics. As I said in another post, with a little knowledge of electricity, a few $0.50 parts, and a soldering iron, you can share a single, edge-triggered, ISA interrupt among two or more serial cards. I'll post the gory details if anyone wants to know. John From owner-freebsd-hackers Tue Jul 29 09:54:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28562 for hackers-outgoing; Tue, 29 Jul 1997 09:54:49 -0700 (PDT) Received: from gta.gta.com (gta.gta.com [199.120.225.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA28557 for ; Tue, 29 Jul 1997 09:54:46 -0700 (PDT) Message-Id: <199707291659.MAA08615@gta.gta.com> Received: forwarded by SMTP 1.6.0. From: "Larry Baird" Date: Tue, 29 Jul 1997 12:51:12 -0400 X-Mailer: Z-Mail (3.0.1 04apr94) To: hackers@freebsd.org Subject: debugging double fault Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone give me a little guidance in how to find the original stack during a double fault. I have searched the archives and found references to "curpcb" and "tmpstk". But I am not sure what to do with these structures. I suspect the one I am really interested in is tmpstk. My code is some networking code that runs out of ip_input(). I have using the remote debugging option of gdb -k over a serial line. Almost forgot, I am running FreeBSD 2.2.2. Thanks, Larry -- ----------------------------------------------------------------------------- Larry Baird | Global Technology Associates, Inc. Director, Software Development | Orlando, FL Email: lab@gta.com | Tel 407-380-0220 FAX 407-380-6080 From owner-freebsd-hackers Tue Jul 29 10:02:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29210 for hackers-outgoing; Tue, 29 Jul 1997 10:02:36 -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 KAA29202 for ; Tue, 29 Jul 1997 10:02:32 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtFf9-0007Jj-00; Tue, 29 Jul 1997 10:02:19 -0700 Date: Tue, 29 Jul 1997 10:02:18 -0700 (PDT) From: Tom Samplonius To: FreeBSD Mailing List cc: Rod Ebrahimi , hackers@freebsd.org Subject: Re: Pentium II? 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, 29 Jul 1997, FreeBSD Mailing List wrote: > On Tue, 29 Jul 1997, Rod Ebrahimi wrote: > > > Recently I was looking into some of Dell's server systems and found that > > they offer Pentium II 233mhz and 266mhz... I was wondering if anyone had > > any experience with these types of systems (Pentium II) or knows how they > > will interact with FreeBSD... > > > > Thank You. > > > The PPro is still faster for a true 32-bit OS, primarily due to the fact > that the L2 is 1:1 with the CPU clock. On the Pentium II, the L2 caching > is at 1/2 the CPU clock. Not, not quite. At the same clock rate, the PPro is faster, but the PII can operate at 266mhz, while the PPro maxes at 200mhz. > The PII runs 16-bit software better and adds MMX extensions, but for a > network server the PPro will still be faster. The PII/266 will be faster than a PPro/200. > Kevin Tom From owner-freebsd-hackers Tue Jul 29 10:19:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00337 for hackers-outgoing; Tue, 29 Jul 1997 10:19:06 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA00317 for ; Tue, 29 Jul 1997 10:19:00 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id NAA04079 for ; Tue, 29 Jul 1997 13:20:10 -0400 (EDT) Date: Tue, 29 Jul 1997 13:20:10 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: hackers@freebsd.org Subject: de0 under 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 Hi, I ran this by -questions, and it was suggested I move over here... I have a Digital DE500: Jul 28 19:03:24 newporn /kernel: de0 rev 32 int a irq 12 on pci0:10 Jul 28 19:03:24 newporn /kernel: de0: DE500-AA 21140A [10-100Mb/s] pass 2.0 Jul 28 19:03:24 newporn /kernel: de0: address 00:00:f8:03:66:e9 [skip to npx0 detection] Jul 29 12:59:41 newporn /kernel: de0: link up: enabling 10baseT port ...and I'm running 2.2-stable cvsupped from yesterday afternoon. The card seems to work fine except for when the cable is unplugged. This message gets logged: Jul 29 13:00:05 newporn /kernel: de0: link down: cable problem? If the cable is plugged back in, the link is dead and the link LED on the card flashes. netstat -i will freeze after the first line is output. If I give it a "ifconfig de0 down" and then "ifconfig de0 up" it comes back and works fine and has a solid link light. Is this a known problem? And if so, is there a fix in the works, or is support for the Digital cards going away? Someone had suggested getting the de0 package from 3am-software.com; can anyone give me a "yay" or "nay" on that? Thanks much, Charles From owner-freebsd-hackers Tue Jul 29 10:40:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01688 for hackers-outgoing; Tue, 29 Jul 1997 10:40:47 -0700 (PDT) Received: from mail2.lancs.ac.uk (mail2.lancs.ac.uk [148.88.8.13]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA01682 for ; Tue, 29 Jul 1997 10:40:44 -0700 (PDT) Received: from unixc.lancs.ac.uk by mail2.lancs.ac.uk with SMTP (PP); Tue, 29 Jul 1997 18:40:27 +0100 Received: (from costa@localhost) by unixc.lancs.ac.uk (8.8.4/8.6.12) id SAA06159; Tue, 29 Jul 1997 18:40:19 +0100 (BST) Date: Tue, 29 Jul 1997 18:40:08 +0100 (BST) From: EMANUELE COSTA To: freebsd-hackers@FreeBSD.ORG Subject: Sound Blaster 16 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 Hi, I'm trying to install a Sound Balster 16 PnP and I've been told that I should search for the OSS package. Could anyone help me? Thanks in advance, EMANUELE -- e-mail: costa@unix.lancs.ac.uk http://www.leganordsen.it/ From owner-freebsd-hackers Tue Jul 29 10:58:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02592 for hackers-outgoing; Tue, 29 Jul 1997 10:58:06 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02584 for ; Tue, 29 Jul 1997 10:58:00 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id OAA11087; Tue, 29 Jul 1997 14:05:46 -0400 (EDT) Message-Id: <3.0.32.19970729135626.00dce720@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 29 Jul 1997 13:56:30 -0400 To: spork , hackers@FreeBSD.ORG From: dennis Subject: Re: de0 under 2.2-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Has the new de driver and if_media stuff been put in -stable yet, or does this continue to be a manual operation to add it? Dennis At 01:20 PM 7/29/97 -0400, spork wrote: >Hi, > >I ran this by -questions, and it was suggested I move over here... > >I have a Digital DE500: > >Jul 28 19:03:24 newporn /kernel: de0 rev 32 >int a irq 12 on pci0:10 >Jul 28 19:03:24 newporn /kernel: de0: DE500-AA 21140A [10-100Mb/s] pass >2.0 >Jul 28 19:03:24 newporn /kernel: de0: address 00:00:f8:03:66:e9 >[skip to npx0 detection] >Jul 29 12:59:41 newporn /kernel: de0: link up: enabling 10baseT port > >...and I'm running 2.2-stable cvsupped from yesterday afternoon. > >The card seems to work fine except for when the cable is unplugged. This >message gets logged: > >Jul 29 13:00:05 newporn /kernel: de0: link down: cable problem? > >If the cable is plugged back in, the link is dead and the link LED on the >card flashes. netstat -i will freeze after the first line is output. If >I give it a "ifconfig de0 down" and then "ifconfig de0 up" it comes back >and works fine and has a solid link light. > >Is this a known problem? And if so, is there a fix in the works, or is >support for the Digital cards going away? > >Someone had suggested getting the de0 package from 3am-software.com; can >anyone give me a "yay" or "nay" on that? > >Thanks much, > >Charles > > > From owner-freebsd-hackers Tue Jul 29 11:01:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02938 for hackers-outgoing; Tue, 29 Jul 1997 11:01:58 -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 LAA02908 for ; Tue, 29 Jul 1997 11:01:50 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 3265 invoked by uid 1001); 29 Jul 1997 18:01:35 +0000 (GMT) To: spork@super-g.com Cc: hackers@FreeBSD.ORG Subject: Re: de0 under 2.2-STABLE In-Reply-To: Your message of "Tue, 29 Jul 1997 13:20:10 -0400 (EDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 29 Jul 1997 20:01:35 +0200 Message-ID: <3263.870199295@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Someone had suggested getting the de0 package from 3am-software.com; can > anyone give me a "yay" or "nay" on that? Definitely get this package. Matt Thomas is the original developer of the de driver, and the version at http://www.3am-software.com/de-970703.tar.gz is much newer than the one in 2.2.2. For me it works much better, but note that I have no experience with the particular card that you're having problems with. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Tue Jul 29 11:21:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04060 for hackers-outgoing; Tue, 29 Jul 1997 11:21:47 -0700 (PDT) Received: from ns1.primelink.com (ns1.primelink.com [206.24.58.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04052 for ; Tue, 29 Jul 1997 11:21:43 -0700 (PDT) Received: from mystic ([206.24.58.91]) by ns1.primelink.com (post.office MTA v1.9.3 ID# 0-11777) with SMTP id AAA78; Tue, 29 Jul 1997 13:23:41 -0500 Message-ID: <3494236D.4C30@primelink.com> Date: Sun, 14 Dec 1997 13:20:29 -0500 From: Kevin Brown Reply-To: kbrown@primelink.com Organization: Huber and Associates X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 To: EMANUELE COSTA CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk EMANUELE COSTA wrote: > > Hi, > I'm trying to install a Sound Balster 16 PnP and I've been told > that I should search for the OSS package. Could anyone help me? > Thanks in advance, > EMANUELE > I hardly believe this question is deserving to be in -hackers. Try perhaps -questions, or better yet, go to radio shack... cause when you got questions... they've got answers. From owner-freebsd-hackers Tue Jul 29 11:30:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04534 for hackers-outgoing; Tue, 29 Jul 1997 11:30:11 -0700 (PDT) Received: from onyx.atipa.com (user10617@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04522 for ; Tue, 29 Jul 1997 11:30:05 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 29 Jul 1997 18:31:56 -0000 Date: Tue, 29 Jul 1997 12:31:55 -0600 (MDT) From: FreeBSD Mailing List X-Sender: freebsd@dot.ishiboo.com To: Tom Samplonius cc: Rod Ebrahimi , hackers@FreeBSD.ORG Subject: Re: Pentium II? 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, 29 Jul 1997, Tom Samplonius wrote: > > > Recently I was looking into some of Dell's server systems and found that > > > they offer Pentium II 233mhz and 266mhz... I was wondering if anyone had > > > any experience with these types of systems (Pentium II) or knows how they > > > will interact with FreeBSD... > > The PPro is still faster for a true 32-bit OS, primarily due to the fact > > that the L2 is 1:1 with the CPU clock. On the Pentium II, the L2 caching > > is at 1/2 the CPU clock. > Not, not quite. At the same clock rate, the PPro is faster, but the PII > can operate at 266mhz, while the PPro maxes at 200mhz. You are correct there. Expandability is much better with the "next generation." Another plus is that P2s come standard with 512K L2. Per cycle, the Pro is a better processor, but the higher frequency of the P2 is definitely a factor. > > The PII runs 16-bit software better and adds MMX extensions, but for a > > network server the PPro will still be faster. > > The PII/266 will be faster than a PPro/200. On most things. The S. E. C. cartridge is unwieldy and proprietary, and the 266 is still a bit pricey. I may be antiquated, but I prefer the Pro. On an unlimited budget, the PII-266 is a good choice. Kevin From owner-freebsd-hackers Tue Jul 29 12:02:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06103 for hackers-outgoing; Tue, 29 Jul 1997 12:02:52 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA06097 for ; Tue, 29 Jul 1997 12:02:44 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id OAA25154; Tue, 29 Jul 1997 14:02:07 -0500 (CDT) Date: Tue, 29 Jul 1997 14:02:07 -0500 (CDT) From: Craig Johnston To: Tom Samplonius cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@FreeBSD.ORG Subject: Re: Pentium II? 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, 29 Jul 1997, Tom Samplonius wrote: > > On Tue, 29 Jul 1997, FreeBSD Mailing List wrote: > > > On Tue, 29 Jul 1997, Rod Ebrahimi wrote: > > > > > Recently I was looking into some of Dell's server systems and found that > > > they offer Pentium II 233mhz and 266mhz... I was wondering if anyone had > > > any experience with these types of systems (Pentium II) or knows how they > > > will interact with FreeBSD... > > > > > The PPro is still faster for a true 32-bit OS, primarily due to the fact > > that the L2 is 1:1 with the CPU clock. On the Pentium II, the L2 caching > > is at 1/2 the CPU clock. > > Not, not quite. At the same clock rate, the PPro is faster, but the PII > can operate at 266mhz, while the PPro maxes at 200mhz. > > > The PII runs 16-bit software better and adds MMX extensions, but for a > > network server the PPro will still be faster. > > The PII/266 will be faster than a PPro/200. Not buying into Intel's slot 1 ploy is a good enough reason not to run PII's. Slot 1 is not going to be around very long and I wouldn't count on not running into bugs in the relatively untested slot 1 chipset. The PPro chipset is known to be robust. FreeBSD systems have run stably on it for quite a while now. It just works. Slot 1 is also entirely proprietary -- Intel's response to more competition than it likes from AMD and now Cyrix. The PPro 200 offers all the CPU horsepower you're going to need on a FreeBSD network server. I'd worry about the amount of RAM and the speed, latency, and number of hard drives. SCSI, of course. regards, Craig From owner-freebsd-hackers Tue Jul 29 12:20:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06948 for hackers-outgoing; Tue, 29 Jul 1997 12:20:00 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust103.max6.washington2.dc.ms.uu.net [153.34.2.231]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA06935 for ; Tue, 29 Jul 1997 12:19:52 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id PAA12406; Tue, 29 Jul 1997 15:19:01 -0400 (EDT) Message-ID: <19970729151900.33228@wakky.dyn.ml.org> Date: Tue, 29 Jul 1997 15:19:00 -0400 From: Lee Cremeans To: Craig Johnston Cc: hackers@freebsd.org Subject: Re: Pentium II? Reply-To: hcremean@vt.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e In-Reply-To: ; from Craig Johnston on Tue, Jul 29, 1997 at 02:02:07PM -0500 X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, Jul 29, 1997 at 02:02:07PM -0500, Craig Johnston wrote: > Slot 1 is also entirely proprietary -- Intel's response to more > competition than it likes from AMD and now Cyrix. > HOw well does FreeBSD run on a K6, anyway? I saw the CPUID stuff in the kernel source, and was wondering... -- 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 Tue Jul 29 12:25:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07267 for hackers-outgoing; Tue, 29 Jul 1997 12:25:48 -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 MAA07250 for ; Tue, 29 Jul 1997 12:25:31 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.6/8.8.6) id QAA09968 for hackers@freebsd.org; Tue, 29 Jul 1997 16:25:24 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199707291925.QAA09968@gaia.coppe.ufrj.br> Subject: NFS Problems in 2.2 ? To: hackers@freebsd.org Date: Tue, 29 Jul 1997 16:25:24 -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 Hi, I'm having lots of problems with NFS deadlocks in my recent configuration. Both client and server are 2.2-STABLE, with 3c905 100Mbps ethernet boards. Right now, for example, I have a netscape and am elm locked. If this helps, here's the output of a "ps -axlww | grep nfs" on the client: zeus::jonny [501] ps -axlww | grep nfs 0 112 1 0 2 0 236 0 accept IWs ?? 0:00.00 nfsd: master (nfsd) 0 114 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) 0 115 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) 0 116 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) 0 117 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) 0 127 1 0 -1 0 212 12 nfsrcv D ?? 0:00.09 nfsiod -n 8 0 128 1 0 -1 0 212 12 nfsrcv D ?? 0:00.06 nfsiod -n 8 0 129 1 0 -1 0 212 12 nfsrcv D ?? 0:00.03 nfsiod -n 8 0 130 1 0 2 0 212 12 sbwait D ?? 0:00.03 nfsiod -n 8 0 131 1 0 -1 0 212 12 nfsrcv D ?? 0:00.03 nfsiod -n 8 0 132 1 0 -1 0 212 12 nfsrcv D ?? 0:00.02 nfsiod -n 8 0 133 1 0 -1 0 212 12 nfsrcv D ?? 0:00.02 nfsiod -n 8 0 134 1 0 -1 0 212 12 nfsrcv D ?? 0:00.01 nfsiod -n 8 100 410 1 0 -6 0 7048 4304 nfsaio D v1 0:10.64 /usr/local/lib/netscape/netscape.bin zeus::jonny [502] The relevant fstab options are as follows: gaia:/ /gaia nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 gaia:/usr /gaia/usr nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 gaia:/var /gaia/var nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 gaia:/extra /gaia/extra nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 Using option "tcp" helps a lot, but if the server reboots, the client does not reconect. "nfsv2" and "dumbtimer" seem to have helped, but did not solve the problem. Is there anything I can do to help debug this ? 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 Tue Jul 29 13:07:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09544 for hackers-outgoing; Tue, 29 Jul 1997 13:07:11 -0700 (PDT) Received: from mail.eclipse.net (root@mail.eclipse.net [207.207.192.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09539 for ; Tue, 29 Jul 1997 13:07:08 -0700 (PDT) Received: from gws (ha1-189.eclipse.net [207.207.196.189]) by mail.eclipse.net (8.8.6/8.7.3) with SMTP id QAA07484 for ; Tue, 29 Jul 1997 16:06:58 -0400 (EDT) Message-Id: <199707292006.QAA07484@mail.eclipse.net> Comments: Authenticated sender is From: "Guy Silliman" Organization: Eclipse Internet Access To: freebsd-hackers@FreeBSD.ORG Date: Tue, 29 Jul 1997 16:06:03 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: /bin/chio: why in /bin ? Reply-to: gws@eclipse.net Priority: normal In-reply-to: <199707260818.MAA05176@janus.msu.su> X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sergei, This seems to have stired up ALOT of heat... but I have to ask... does it REALY make that much difference?!? If you want it in a different directory structure... move it... I am sure there will be flames for this... so have a day! Guy Silliman > Dear FreeBSD hackers! > > I wonder why "mt", "tar" are in "/usr/bin" while chio is in "/bin". > > Sergei S. Laskavy > From owner-freebsd-hackers Tue Jul 29 13:40:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11483 for hackers-outgoing; Tue, 29 Jul 1997 13:40:18 -0700 (PDT) Received: from x1.boston.juno.com (x1.boston.juno.com [205.231.100.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11470 for ; Tue, 29 Jul 1997 13:40:11 -0700 (PDT) Received: (from rondzierwa@juno.com) by x1.boston.juno.com (queuemail) id QHT00665; Tue, 29 Jul 1997 16:38:40 EDT To: hackers@freebsd.org Date: Tue, 29 Jul 1997 16:34:54 EDT Subject: PCMCIA on FreeBSD2.2.1 Message-ID: <19970729.164516.11567.0.RonDzierwa@juno.com> X-Mailer: Juno 1.38 X-Juno-Line-Breaks: 0-1,8-9,15-16,22-23,29-46 From: rondzierwa@juno.com (Ron Dzierwa) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Hackers, I recently installed 2.2.1 on an Ergo Powerbrick 100 Notebook computer and had some questions regarding the PCMCIA support. The hardware compatibility list indicates that the 3Com 3c589 pcmcia ethernet is supported, as well as the adaptec AIC-6360 pcmcia scsi controller both of which I have installed and tested using dos/windows drivers and even NT 3.51. I am having problems getting them to work under FreeBSD 2.2.1 however, and hoped somebody there could help. The 3Com card I have is NOT a combo card, but it is the `D" version which is mentioned in the HARDWARE.TXT file on the distribution as possibly being supported in the new generic PCMCIA code but there is little/no documentation on how to set it up. I was hoping that somebody could give me some hints as to how to set this up so I could muddle around with it until it is better supported. Also, the computer uses a DataBook DB86082 PCMCIA controller chip. I looked thru the PCMCIA support code and did not find any mention of this chip, so I am wondering if it is supported. I have the data sheets and some diagnostic/test/development software for the chip (runs under dos), so I would be willing to put some work into adding support for the chip to the existing PCMCIA code if necessary. Regarding the scsi controller, the driver in the generic kernel seems to be able to find it when booting from the CDROM using fbsdboot, but shortly thereafter the system hangs up. I believe that it could find the scsi controller because I was booting from dos and the pcmcia controller was still set up from the dos driver. This leads me back to the PCMCIA support code. So I guess what I am asking is: - How to setup/configure the `D' version of the 3c589 - Is my PCMCIA chip supported at all? - How to configure the AIC-6360 driver to work with the PCMCIA chip. Any answers, hints, or even guesses would be deeply appreciated. Thanks, ron From owner-freebsd-hackers Tue Jul 29 14:13:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13318 for hackers-outgoing; Tue, 29 Jul 1997 14:13:20 -0700 (PDT) Received: from weenix.guru.org (weenix.guru.org [198.82.200.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13303 for ; Tue, 29 Jul 1997 14:13:16 -0700 (PDT) Received: (from kmitch@localhost) by weenix.guru.org (8.8.6/8.8.5) id RAA14306 for hackers@freebsd.org; Tue, 29 Jul 1997 17:13:05 -0400 (EDT) From: Keith Mitchell Message-Id: <199707292113.RAA14306@weenix.guru.org> Subject: Re: Bug in pw? (account/pasword exp dates) In-Reply-To: From kmitch at "Jul 25, 97 08:40:27 am" To: hackers@freebsd.org Date: Tue, 29 Jul 1997 17:13:05 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL30 (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 > If I give pw the following command: > > pw useradd tuser -P -c "Test User" -e 901944000 -p 869834290 -m -h 0 > > everything seems to work except that the account expiration date and the > password expiration date are set to the same thing (to the -e param). I think I found the bug. In pw_pwdpolicy it tests for a -e instead of the -p. The following patched seemingly fixed the problem. Index: pw_user.c =================================================================== RCS file: /src/cvs/src/usr.sbin/pw/pw_user.c,v retrieving revision 1.21 diff -c -r1.21 pw_user.c *** pw_user.c 1997/06/14 00:23:49 1.21 --- pw_user.c 1997/07/29 20:50:16 *************** *** 732,738 **** { time_t result = 0; time_t now = time(NULL); ! struct carg *arg = getarg(args, 'e'); if (arg != NULL) { if ((result = parse_date(now, arg->val)) == now) --- 732,738 ---- { time_t result = 0; time_t now = time(NULL); ! struct carg *arg = getarg(args, 'p'); if (arg != NULL) { if ((result = parse_date(now, arg->val)) == now) -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserved Unauthorized use or duplication prohibited From owner-freebsd-hackers Tue Jul 29 15:33:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17389 for hackers-outgoing; Tue, 29 Jul 1997 15:33:44 -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 PAA17383 for ; Tue, 29 Jul 1997 15:33:41 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA01449; Tue, 29 Jul 1997 16:33:35 -0600 (MDT) Date: Tue, 29 Jul 1997 16:33:35 -0600 (MDT) Message-Id: <199707292233.QAA01449@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: rondzierwa@juno.com (Ron Dzierwa) Cc: hackers@freebsd.org Subject: Re: PCMCIA on FreeBSD2.2.1 In-Reply-To: <19970729.164516.11567.0.RonDzierwa@juno.com> References: <19970729.164516.11567.0.RonDzierwa@juno.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The 3Com card I have is NOT a combo card, but it is the `D" version which > is mentioned in the HARDWARE.TXT file on the distribution as possibly > being supported in the new generic PCMCIA code but there is little/no > documentation on how to set it up. Umm, the 'D' version is meantioned as 'un-supported' in HARDWARE.TXT I believe. In any case, there is support for it in newer boot disks, check releng22.FreeBSD.org for some. > Also, the computer uses a DataBook DB86082 PCMCIA controller chip. I > looked thru the PCMCIA support code and did not find any mention of this > chip, so I am wondering if it is supported. I have the data sheets and > some diagnostic/test/development software for the chip (runs under dos), > so I would be willing to put some work into adding support for the chip > to the existing PCMCIA code if necessary. Probably. > Regarding the scsi controller Where did you read that FreeBSD supported the PCMCIA SCSI card? Stock FreeBSD doesn't support it, although the PAO boot floppy does. See http://www.freebsd.org.jp/PAO. Nate From owner-freebsd-hackers Tue Jul 29 15:38:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17731 for hackers-outgoing; Tue, 29 Jul 1997 15:38:07 -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 PAA17714 for ; Tue, 29 Jul 1997 15:37:41 -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 UAA22446; Tue, 29 Jul 1997 20:35:21 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id UAA20712; Tue, 29 Jul 1997 20:35:20 +0100 (BST) Message-Id: <199707291935.UAA20712@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: dk+@ua.net cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Tue, 29 Jul 1997 01:52:00 PDT." <199707290852.BAA13807@dog.farm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 20:35:20 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In article <199707290356.EAA22036@awfulhak.org> you wrote: > > > > Yep. I think I'll fix the usage message too - shouldn't it be: > > > > > > > > [[yy[mm[dd[hh]]]]mm[.ss]] > > It should become > > [[[cc]yy[mm[dd[hh]]]]mm[.ss]] > > or we are screwed in 866 days from now. More like: [[cc[yy[mm[dd[hh]]]]]mm[.ss]] (you can't have the century without the year). I'll look into allowing this too. On that note, I'd expect a year of 00+n to mean 2000+n up to whatever the maximum is. Any objections ? > -- > I have BSD, but SYSV has me. > -- heared from Igor Uwkin (uwka@big.Sun.nsk.SU) -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Tue Jul 29 15:38:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17772 for hackers-outgoing; Tue, 29 Jul 1997 15:38:22 -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 PAA17715 for ; Tue, 29 Jul 1997 15:37:43 -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 UAA22450; Tue, 29 Jul 1997 20:38:25 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id UAA20736; Tue, 29 Jul 1997 20:38:25 +0100 (BST) Message-Id: <199707291938.UAA20736@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alfred Perlstein cc: FreeBSD Hackers Subject: Re: HD transfer? In-reply-to: Your message of "Tue, 29 Jul 1997 05:24:37 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 20:38:25 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been running a gateway/router on a failing 120meg hard drive for some > time, i recently got a hold of a cheap 250 meg drive, is there a way to > transfer my system to the drive without messing up the /dev directory and > other stuff? You can backup, install on the new disk and restore :) You can also plug in the new disk, do an install onto it and then just tar/pax from one disk to the other. Then you just have to swap the disks around. > Alfred > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Tue Jul 29 15:38:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17847 for hackers-outgoing; Tue, 29 Jul 1997 15:38: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 PAA17840 for ; Tue, 29 Jul 1997 15:38: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 PAA10124; Tue, 29 Jul 1997 15:37:40 -0700 (PDT) To: Tom Samplonius cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@FreeBSD.ORG Subject: Re: Pentium II? In-reply-to: Your message of "Tue, 29 Jul 1997 10:02:18 PDT." Date: Tue, 29 Jul 1997 15:37:40 -0700 Message-ID: <10120.870215860@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Not, not quite. At the same clock rate, the PPro is faster, but the PII > can operate at 266mhz, while the PPro maxes at 200mhz. Of course, everyone I know (myself included) runs their PPro/200 at 233. :-) Jordan From owner-freebsd-hackers Tue Jul 29 15:39:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17927 for hackers-outgoing; Tue, 29 Jul 1997 15:39:14 -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 PAA17908 for ; Tue, 29 Jul 1997 15:39:08 -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 UAA22436; Tue, 29 Jul 1997 20:28:06 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id UAA20404; Tue, 29 Jul 1997 20:28:05 +0100 (BST) Message-Id: <199707291928.UAA20404@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: dk+@ua.net cc: brian@awfulhak.org (Brian Somers), freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Tue, 29 Jul 1997 01:52:00 PDT." <199707290852.BAA13807@dog.farm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 20:28:05 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In article <199707290356.EAA22036@awfulhak.org> you wrote: > > > > Yep. I think I'll fix the usage message too - shouldn't it be: > > > > > > > > [[yy[mm[dd[hh]]]]mm[.ss]] > > It should become > > [[[cc]yy[mm[dd[hh]]]]mm[.ss]] > > or we are screwed in 866 days from now. > > > > > I must say, this format beats the mmddhhmmyy format in SYSV ! > > /usr/bin/date [-u] [[mmdd]HHMM | mmddHHMM[cc]yy][.SS] > > (quote from Solaris 2.5.1 manpage) Hmm, this says that the following are ok (the [mmdd] bit is extraneous too): date HHMM date mmddHHMM date mmddHHMMyy date mmddHHMMccyy date .SS date HHMM.SS date mmddHHMM.SS date mmddHHMMyy.SS date mmddHHMMccyy.SS If this usage message reflects the behaviour of date(1) on Solaris, I'd be surprised :-I > -- > I have BSD, but SYSV has me. > -- heared from Igor Uwkin (uwka@big.Sun.nsk.SU) -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Tue Jul 29 15:52:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18804 for hackers-outgoing; Tue, 29 Jul 1997 15:52:45 -0700 (PDT) Received: from netcom14.netcom.com (hasty@netcom14.netcom.com [192.100.81.126]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA18794 for ; Tue, 29 Jul 1997 15:52:42 -0700 (PDT) Received: (from hasty@localhost) by netcom14.netcom.com (8.6.13/Netcom) id PAA27082; Tue, 29 Jul 1997 15:52:29 -0700 Date: Tue, 29 Jul 1997 15:52:29 -0700 From: hasty@netcom.com (Amancio Hasty Jr) Message-Id: <199707292252.PAA27082@netcom14.netcom.com> To: e.costa@lancaster.ac.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Can you tell me who told you to look for the OSS sound driver so that you can use your Sound Blaster 16 PnP? You can use your SB16 PnP by installing Sujal's PnP package. It is available from the ftp site ftp://rah.star-gate.com/pub/FreeBSD-PnP .. something Also you can post your questions related to multimedia to multimedia@freebsd.org Regards, Amancio From owner-freebsd-hackers Tue Jul 29 15:58:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19274 for hackers-outgoing; Tue, 29 Jul 1997 15:58:58 -0700 (PDT) Received: from zeus.gel.usherb.ca (zeus.gel.usherb.ca [132.210.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA19268 for ; Tue, 29 Jul 1997 15:58:55 -0700 (PDT) Received: from pollux.gel.usherb.ca by zeus.gel.usherb.ca (4.1/SMI-4.1) id AA21335; Tue, 29 Jul 97 18:58:47 EDT Received: by pollux.gel.usherb.ca (SMI-8.6/SMI-SVR4) id SAA14216; Tue, 29 Jul 1997 18:58:47 -0400 Date: Tue, 29 Jul 1997 18:58:44 -0400 (EDT) From: "Alex.Boisvert" To: freebsd-hackers@freebsd.org Subject: Almost JDK 1.1.2 port! 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 is a repost since I haven't got any response from first post) Hello all hackers - I'm almost done with a native port of JDK 1.1.2 to FreeBSD and I am having a few difficulties with dynamic libraries. (Yes, that's ld.so stuff) The java virtual machine (java_g) gets a segmentation fault when going through the _GLOBAL_OFFSET_TABLE_ to execute a function in a dynamic library (in this case, libawt_g.so). The libawt_g.so library is loaded via a dlopen() call. In gdb, I get the following output after the library is loaded and the VM crashed: ---- cut here ----- Program received signal SIGSEGV, Segmentation fault. 0x0 in ?? () (gdb) info sharedlibrary >From To Syms Read Shared Object Library 0x0807a000 0x0808a000 Yes /usr/libexec/ld.so 0x08091000 0x080ab000 Yes /usr/lib/libm.so.2.0 0x080aa000 0x081a5434 Yes /usr/X11R6/lib/libXm.so.1.2 0x081a5000 0x081e7000 Yes /usr/X11R6/lib/libXt.so.6.0 0x081e6000 0x081f0000 Yes /usr/X11R6/lib/libXext.so.6.1 0x081ef000 0x082851a0 Yes /usr/X11R6/lib/libX11.so.6.1 0x08285000 0x082ef710 Yes /usr/lib/libc.so.3.0 0x09403000 0x0946552c No /home/alex/jdk/javasrc/build/lib/i386/green_threads/libawt_g.so (gdb) ------ cut here ------ Notice the "No" for libawt_g.so in the column "Syms Read". What does this mean??? Have I forgotten to do something after dlopen()? Regards, Alex. PS: I am using dlsym() to get the address of the function. From owner-freebsd-hackers Tue Jul 29 16:03:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19546 for hackers-outgoing; Tue, 29 Jul 1997 16:03:31 -0700 (PDT) Received: from gvr.win.tue.nl (root@gvr.win.tue.nl [194.151.74.97]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19534 for ; Tue, 29 Jul 1997 16:03:21 -0700 (PDT) Received: (from guido@localhost) by gvr.win.tue.nl (8.8.6/8.8.2) id BAA10072 for FreeBSD-hackers@freebsd.org; Wed, 30 Jul 1997 01:03:14 +0200 (MET DST) From: Guido van Rooij Message-Id: <199707292303.BAA10072@gvr.win.tue.nl> Subject: bad sectors and sysinstall To: FreeBSD-hackers@freebsd.org (FreeBSD-hackers) Date: Wed, 30 Jul 1997 01:03:14 +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've got an IDE drive with bad sectors I still want to use. I think bad144 is the thing to use, however sysinstall does not seem to be able to specify it. Am I missing something? Further; are there any caveats I should know? -Guido From owner-freebsd-hackers Tue Jul 29 16:30:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20955 for hackers-outgoing; Tue, 29 Jul 1997 16:30:08 -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 QAA20948 for ; Tue, 29 Jul 1997 16:30:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id IAA15471; Wed, 30 Jul 1997 08:59:50 +0930 (CST) From: Michael Smith Message-Id: <199707292329.IAA15471@genesis.atrad.adelaide.edu.au> Subject: Re: Sharing interrupts In-Reply-To: <33df1cb8.2144876@smtp-gw01.ny.us.ibm.net> from John Kelly at "Jul 29, 97 04:53:40 pm" To: mouth@ibm.net (John Kelly) Date: Wed, 30 Jul 1997 08:59:50 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.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 John Kelly stands accused of saying: > >More specifically, you can only allow _one_ device to drive an ISA > >IRQ line at any given time. > > Not strictly true, see below. That depends on whether you feel like violating the bus standard. > >ISA bus drivers use totem-pole outputs, so a device which has control > >of an interrupt line but not asserting an interrupt still counts as > >"driving" > > A standard totem-pole output is either driving the line to ground > (logic low) or 3.5-4.5 volts (logic high). But if the device has a > tri-state driver, that third state is "floating," and it can be on the > line at the same time in the floating state without interfering with > another device. A device with a tristated output is not _driving_ the line. This is consistent with my original statement. > But in any event, that's not what I'm talking about. I'm talking > about sharing an edge-triggered, ISA interrupt among two or more > serial cards (with single or multiple UARTS per card). This can only be done correctly using extra logic. > >See the comments and procedure in sioprobe() in i286/isa/sio.c and > > I have, and that documentation does not tell the electrical story. Specifically, it describes the problems with gating tristated drive to the IRQ lines, with regard to the electrical behaviour of an undriven line. > >cross-reference the 8250 datasheet for an understanding of the quirks > >and complexities involved in getting this right. It is _not_ trivial. > > I have. It's not hard at all. It sounds suspiciously like you are either Marilyn Vos Savant, or underestimating the situation. > In the 8259 datasheet, what many people overlook are its electrical > characteristics. As I said in another post, with a little knowledge > of electricity, a few $0.50 parts, and a soldering iron, you can share > a single, edge-triggered, ISA interrupt among two or more serial > cards. Very few boards these days use the 8259. Most, if not all, of the current chipsets use a logically equivalent macrocell, however their electrical characteristics are likely to be very different to those of a 70's vintage NMOS device. > I'll post the gory details if anyone wants to know. Using diodes and resistors to convert totem-pole outputs into open-collector-like outputs is highschool electronics. You will note my employer's field in my .sig; my work profile covers bus and interface design as well as OS and UI development. You're quite welcome to butcher your cards and live with the potential uncertainties involved in what you're doing, and I have no problems with you sharing the information with others that want to do the same. The problem arises when you claim that this is a universal case : it isn't, and your statements are not helpful when it comes to getting the message across. -- ]] 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 Tue Jul 29 16:31:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21096 for hackers-outgoing; Tue, 29 Jul 1997 16:31:44 -0700 (PDT) Received: from grendel.IAEhv.nl (grendel.IAEhv.nl [194.151.72.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA21079 for ; Tue, 29 Jul 1997 16:31:33 -0700 (PDT) Received: (from peter@localhost) by grendel.IAEhv.nl (8.8.5/8.8.5) id XAA00665; Tue, 29 Jul 1997 23:22:10 +0200 (CEST) Message-ID: <19970729232210.28736@grendel.IAEhv.nl> Date: Tue, 29 Jul 1997 23:22:10 +0200 From: Peter Korsten To: hackers@freebsd.org Subject: Re: Sound Blaster 16 PnP References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67e In-Reply-To: ; from EMANUELE COSTA on Tue, Jul 29, 1997 at 06:40:08PM +0100 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk EMANUELE COSTA shared with us: > I'm trying to install a Sound Balster 16 PnP and I've been told > that I should search for the OSS package. Could anyone help me? I was wondering, am I the only person who just looked under Windows 95 (tm) which resources the PnP Soundblaster 16 used and configured his kernel likewise? With just an PnP SB16 and a non-PnP Teles ISDN card, this works fine. Of course, adding a PnP card would stir up things, but in my case that would mean rebuilding my kernel anyway (I stripped it to the bare essentials). - Peter From owner-freebsd-hackers Tue Jul 29 16:36:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21433 for hackers-outgoing; Tue, 29 Jul 1997 16:36:09 -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 QAA21405; Tue, 29 Jul 1997 16:36:03 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 29 Jul 1997 19:35:25 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA05492; Tue, 29 Jul 97 19:35:24 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id TAA22994; Tue, 29 Jul 1997 19:33:03 -0400 Message-Id: <19970729193303.55916@ct.picker.com> Date: Tue, 29 Jul 1997 19:33:03 -0400 From: Randall Hopper To: EMANUELE COSTA Cc: freebsd-hackers@freebsd.org, multimedia@freebsd.org Subject: Re: Sound Blaster 16 PnP References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from EMANUELE COSTA on Tue, Jul 29, 1997 at 06:40:08PM +0100 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk | I'm trying to install a Sound Balster 16 PnP and I've been told |that I should search for the OSS package. Could anyone help me? | Thanks in advance, (I'm forwarding this on over to the multimedia list since it's more likely to be noticed by a person that can help you there.) I believe Luigi Rizzo's (luigi@labinfo.iet.unipi.it) gotten his SB16-compatible PnP card working using the latest beta Voxware sound drivers. The latest two driver snaps are at: ftp://rah.star-gate.com/pub/guspnp12.tar.gz ftp://rah.star-gate.com/pub/guspnp11.tar.gz (Ignore the filename -- it continues to cause confusion.) There have also been posts to the lists recently regarding folks that having gotten their PnP sound cards working using Sujal Patel's ISA PnP tools. In fact there was one today on -current where someone posted their mods for a SB16 PnP. I'd try the latest driver rev above first since its destined shortly to be the new sound driver, and it'd be good to get your input and make sure it supports your card out-of-the-box. If you have any problems, please post to the multimedia@freebsd.org list. The sound driver rework is the current hot topic; input is being solicited from anyone with a soundcard. Randall Hopper From owner-freebsd-hackers Tue Jul 29 17:00:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA22783 for hackers-outgoing; Tue, 29 Jul 1997 17:00:01 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22761 for ; Tue, 29 Jul 1997 16:59:58 -0700 (PDT) Received: from default (hahaha@max008-7.netroplex.com [207.212.27.7]) by netroplex.com (8.8.5/8.8.2) with ESMTP id RAA03155 for ; Tue, 29 Jul 1997 17:00:24 -0700 (PDT) Message-Id: <199707300000.RAA03155@netroplex.com> From: "Rod Ebrahimi" To: Subject: 2.2.1 Date: Tue, 29 Jul 1997 16:58:42 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 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 I was wondering if anyone was running 2.2.1 for internet services and if it is as stable and robust as the previous versions of the system. Thank you for your time... Rod From owner-freebsd-hackers Tue Jul 29 17:16:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23826 for hackers-outgoing; Tue, 29 Jul 1997 17:16:55 -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 RAA23821; Tue, 29 Jul 1997 17:16:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03604; Tue, 29 Jul 1997 17:15:14 -0700 From: Terry Lambert Message-Id: <199707300015.RAA03604@phaeton.artisoft.com> Subject: Re: SMBIOS/DMI etc To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 29 Jul 1997 17:15:14 -0700 (MST) Cc: se@FreeBSD.ORG, msmith@atrad.adelaide.edu.au, mo@uu.net, hackers@FreeBSD.ORG In-Reply-To: <199707290211.LAA09448@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 29, 97 11:41:42 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 considered adding calls to the PCI BIOS as an > > alternate mechanism to directly reading configuration > > space registers. But I have no intention to make the > > PCI code depend on PCI BIOS services. > > This is because...? If I had to guess, it's probably because BIOS calls are Intel-centric. 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 Tue Jul 29 17:27:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24320 for hackers-outgoing; Tue, 29 Jul 1997 17:27:11 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24315 for ; Tue, 29 Jul 1997 17:27:08 -0700 (PDT) Received: from default (max008-7.netroplex.com [207.212.27.7]) by netroplex.com (8.8.5/8.8.2) with ESMTP id RAA03486 for ; Tue, 29 Jul 1997 17:27:39 -0700 (PDT) Message-Id: <199707300027.RAA03486@netroplex.com> From: "Rod Ebrahimi" To: Subject: hourly wages Date: Tue, 29 Jul 1997 17:26:00 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 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 I was very curious as to what the average FreeBSD admin and/or consultant normally charges for setup and implementation... From owner-freebsd-hackers Tue Jul 29 17:32:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24597 for hackers-outgoing; Tue, 29 Jul 1997 17:32:53 -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 RAA24592 for ; Tue, 29 Jul 1997 17:32:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03691; Tue, 29 Jul 1997 17:30:46 -0700 From: Terry Lambert Message-Id: <199707300030.RAA03691@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 29 Jul 1997 17:30:46 -0700 (MST) Cc: vinay@agni.nuko.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707290220.LAA09491@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 29, 97 11:50: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 > It is generally considered _extremely_ bad to use copyin/copyout, as it > precludes your functions from being called from within kernel space. > > FWIW, this is what eventually stumped me when it came to getting Linux > WABI running on FreeBSD. This is a good point, considering that kernel preemption is one of my own goals. The issue is recursion with a paging operation in progress. I think with the limited cases I gave (the page is filled, the call made, and the page is still mapped) are OK. copying out is more likely to cause problems than copying in, since you copy in pages after they are touched, but you potentially touch on copyout. Probably there needs to be _copyin/_copyout for the internal usage, and a "safe" copyin/copyout for usage which isn't safed against reentrancy. 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 Tue Jul 29 18:30:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27343 for hackers-outgoing; Tue, 29 Jul 1997 18:30:32 -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 SAA27334; Tue, 29 Jul 1997 18:30:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA16101; Wed, 30 Jul 1997 10:59:26 +0930 (CST) From: Michael Smith Message-Id: <199707300129.KAA16101@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: <199707300015.RAA03604@phaeton.artisoft.com> from Terry Lambert at "Jul 29, 97 05:15:14 pm" To: terry@lambert.org (Terry Lambert) Date: Wed, 30 Jul 1997 10:59:26 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, se@FreeBSD.ORG, mo@uu.net, 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: > > > I have considered adding calls to the PCI BIOS as an > > > alternate mechanism to directly reading configuration > > > space registers. But I have no intention to make the > > > PCI code depend on PCI BIOS services. > > > > This is because...? > > If I had to guess, it's probably because BIOS calls are Intel-centric. Fair enough. How do other platforms (PReP, Alpha, etc) handle PCI autoconfig? Does the BIOS on those platforms provide the same set of management primitives? I would have assumed so, from my reading of PCI-spec-derived documents. (I don't have the "real thing", obviously) > Terry Lambert -- ]] 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 Tue Jul 29 18:30:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27384 for hackers-outgoing; Tue, 29 Jul 1997 18:30:58 -0700 (PDT) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27376 for ; Tue, 29 Jul 1997 18:30:55 -0700 (PDT) Received: from rhiannon.scsn.net ([208.133.153.149]) by mail.scsn.net (Post.Office MTA v3.1 release PO203a ID# 0-32322U5000L100S10000) with ESMTP id AAA59; Tue, 29 Jul 1997 21:22:04 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.8.6/8.8.5) id VAA00370; Tue, 29 Jul 1997 21:30:45 -0400 (EDT) Message-ID: <19970729213045.26986@scsn.net> Date: Tue, 29 Jul 1997 21:30:45 -0400 From: "Donald J. Maddox" To: Peter Korsten Cc: hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP Reply-To: dmaddox@scsn.net References: <19970729232210.28736@grendel.IAEhv.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <19970729232210.28736@grendel.IAEhv.nl>; from Peter Korsten on Tue, Jul 29, 1997 at 11:22:10PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Jul 29, 1997 at 11:22:10PM +0200, Peter Korsten wrote: > EMANUELE COSTA shared with us: > > I'm trying to install a Sound Balster 16 PnP and I've been told > > that I should search for the OSS package. Could anyone help me? > > I was wondering, am I the only person who just looked under Windows > 95 (tm) which resources the PnP Soundblaster 16 used and configured > his kernel likewise? With just an PnP SB16 and a non-PnP Teles ISDN > card, this works fine. No, you're not the only one, but this can work *only* if you have a PnP BIOS that puts everything where it should be at boottime. Not everyone is so lucky. > > Of course, adding a PnP card would stir up things, but in my case > that would mean rebuilding my kernel anyway (I stripped it to the > bare essentials). Yeah, this is another misfortune of having to rely on the BIOS to configure the PnP cards... Adding a new PnP card will almost certainly scramble your config :-( > > - Peter From owner-freebsd-hackers Tue Jul 29 18:42:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27862 for hackers-outgoing; Tue, 29 Jul 1997 18:42:18 -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 SAA27853 for ; Tue, 29 Jul 1997 18:42:12 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA16160; Wed, 30 Jul 1997 11:11:57 +0930 (CST) From: Michael Smith Message-Id: <199707300141.LAA16160@genesis.atrad.adelaide.edu.au> Subject: Re: hourly wages In-Reply-To: <199707300027.RAA03486@netroplex.com> from Rod Ebrahimi at "Jul 29, 97 05:26:00 pm" To: info@pagecreators.com (Rod Ebrahimi) Date: Wed, 30 Jul 1997 11:11:57 +0930 (CST) Cc: 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 Rod Ebrahimi stands accused of saying: > I was very curious as to what the average FreeBSD admin and/or > consultant normally charges for setup and implementation... That depends on whether you persistently badly indent your mail messages 8) My stock setup fee is AUD$500 flat for a basic-service machine (mail, web proxy, empty http server), and AUD$100/hr. beyond that. The flat fee has actually proven very successful in attracting customers, as they know up front what they (think they) are in store for. (Most of them get carried away with all the New Stuff and buy more time, but that's their own choice.) But. Your stated goal is to run an IAP, not set up a one-off office system. You don't want a one-off setup, you want at least a part-time, if not full-time admin for at least a couple of weeks. That sort of contract position I'd normally ask AUD$60/hr. for, particularly if you were expecting me to be responsible for things such as your fundamental security and QOS. I'd want a pretty significant say in your purchasing and strategy decisions, and a good line to someone with authority to spend money in a hurry if required. Beyond that, you're likely to want an admin on call, and possibly working a day a week. If you're serious, you could probably negotiate a pretty good maintenance deal; I haven't been in that market, so I haven't costed it out, but something around AUD$50/hr for an 8-hour day would not be unreasonable, on a 6-month contractual basis. Note that there is considerable virtue in using the same admin(s) for repeat business; you don't really want to pay each new one for a couple of hours of learning time where they're not actually helping you. (For reference, AUD$1 ~= US$0.75. Labour rates may vary to some degree depending on your area.) -- ]] 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 Tue Jul 29 18:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27985 for hackers-outgoing; Tue, 29 Jul 1997 18:44:10 -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 SAA27980 for ; Tue, 29 Jul 1997 18:44:06 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id SAA02533; Tue, 29 Jul 1997 18:43:58 -0700 (PDT) Message-Id: <199707300143.SAA02533@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Peter Korsten cc: hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP In-reply-to: Your message of "Tue, 29 Jul 1997 23:22:10 +0200." <19970729232210.28736@grendel.IAEhv.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 18:43:58 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just take it up to the multimedia mailing list since thats where the sound cards pnp issue is being hammered out. To GUS PnP owner you *don't* have to worry about the PnP issues since the driver has builtin PnP support: For instance , this is my config line for my gus pnp. controller snd0 device gus0 at isa? vector gusintr Hopefully the same level of ease of configuration or better will be extended to other cards. Cheers, Amancio >From The Desk Of Peter Korsten : > EMANUELE COSTA shared with us: > > I'm trying to install a Sound Balster 16 PnP and I've been told > > that I should search for the OSS package. Could anyone help me? > > I was wondering, am I the only person who just looked under Windows > 95 (tm) which resources the PnP Soundblaster 16 used and configured > his kernel likewise? With just an PnP SB16 and a non-PnP Teles ISDN > card, this works fine. > > Of course, adding a PnP card would stir up things, but in my case > that would mean rebuilding my kernel anyway (I stripped it to the > bare essentials). > > - Peter > From owner-freebsd-hackers Tue Jul 29 18:46:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28117 for hackers-outgoing; Tue, 29 Jul 1997 18:46:21 -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 SAA28107 for ; Tue, 29 Jul 1997 18:46:17 -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 SAA11272; Tue, 29 Jul 1997 18:46:09 -0700 (PDT) Message-Id: <199707300146.SAA11272@implode.root.com> To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Location of copyin() and copyout().. In-reply-to: Your message of "Tue, 29 Jul 1997 17:30:46 PDT." <199707300030.RAA03691@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 29 Jul 1997 18:46:08 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> It is generally considered _extremely_ bad to use copyin/copyout, as it >> precludes your functions from being called from within kernel space. >> >> FWIW, this is what eventually stumped me when it came to getting Linux >> WABI running on FreeBSD. > >This is a good point, considering that kernel preemption is one >of my own goals. > >The issue is recursion with a paging operation in progress. > >I think with the limited cases I gave (the page is filled, the >call made, and the page is still mapped) are OK. > >copying out is more likely to cause problems than copying in, >since you copy in pages after they are touched, but you potentially >touch on copyout. > >Probably there needs to be _copyin/_copyout for the internal usage, >and a "safe" copyin/copyout for usage which isn't safed against >reentrancy. There is no problem with using copyout() in the kernel to copy data out to a user process, assuming that the currently running process is the intended target of the copy. That is the sole purpose of the function. copyout() correctly handles all issues of COW/ZF/page faults. uiomove() is escentially a wrapper for copyin/copyout that has an optimization for the case of kernel-to-kernel copies (in which case it uses bcopy instead). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 29 18:54:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28561 for hackers-outgoing; Tue, 29 Jul 1997 18:54:15 -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 SAA28552 for ; Tue, 29 Jul 1997 18:54:13 -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 VAA10618; Tue, 29 Jul 1997 21:54:00 -0400 Date: Tue, 29 Jul 1997 21:54:15 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Alex.Boisvert" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Almost JDK 1.1.2 port! 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, 29 Jul 1997, Alex.Boisvert wrote: > > (This is a repost since I haven't got any response from first post) > > Hello all hackers - > > I'm almost done with a native port of JDK 1.1.2 to FreeBSD and > I am having a few difficulties with dynamic libraries. (Yes, that's ld.so > stuff) > > The java virtual machine (java_g) gets a segmentation fault when going > through the _GLOBAL_OFFSET_TABLE_ to execute a function in a dynamic > library (in this case, libawt_g.so). > > The libawt_g.so library is loaded via a dlopen() call. In gdb, I get the > following output after the library is loaded and the VM crashed: If you don't get a reply, it means no one who's reading knows for sure. It's not terrifically hard to write a short program to verify that you can dlopen and dlsym the symbols, or report the error that dlerror returns. Or use gdb to catch your program as it's reading the symbols in, and make sure they aren't returning NULL (the error condition). What mode are you using for the calls, RTLD_LAZY or RTLD_NOW? Maybe you should change that? > > ---- cut here ----- > > Program received signal SIGSEGV, Segmentation fault. > 0x0 in ?? () > (gdb) info sharedlibrary > From To Syms Read Shared Object Library > 0x0807a000 0x0808a000 Yes /usr/libexec/ld.so > 0x08091000 0x080ab000 Yes /usr/lib/libm.so.2.0 > 0x080aa000 0x081a5434 Yes /usr/X11R6/lib/libXm.so.1.2 > 0x081a5000 0x081e7000 Yes /usr/X11R6/lib/libXt.so.6.0 > 0x081e6000 0x081f0000 Yes /usr/X11R6/lib/libXext.so.6.1 > 0x081ef000 0x082851a0 Yes /usr/X11R6/lib/libX11.so.6.1 > 0x08285000 0x082ef710 Yes /usr/lib/libc.so.3.0 > 0x09403000 0x0946552c No > /home/alex/jdk/javasrc/build/lib/i386/green_threads/libawt_g.so > (gdb) > > ------ cut here ------ > > Notice the "No" for libawt_g.so in the column "Syms Read". What does > this mean??? > > Have I forgotten to do something after dlopen()? > > Regards, > Alex. > > PS: I am using dlsym() to get the address of the function. > > > ----------------------------+----------------------------------------------- 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 Tue Jul 29 19:03:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29235 for hackers-outgoing; Tue, 29 Jul 1997 19:03:48 -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 TAA29228 for ; Tue, 29 Jul 1997 19:03:43 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA16420; Wed, 30 Jul 1997 11:33:19 +0930 (CST) From: Michael Smith Message-Id: <199707300203.LAA16420@genesis.atrad.adelaide.edu.au> Subject: Re: Pentium II? In-Reply-To: <10120.870215860@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 29, 97 03:37:40 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 30 Jul 1997 11:33:19 +0930 (CST) Cc: tom@sdf.com, freebsd@atipa.com, info@pagecreators.com, 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 Jordan K. Hubbard stands accused of saying: > > Not, not quite. At the same clock rate, the PPro is faster, but the PII > > can operate at 266mhz, while the PPro maxes at 200mhz. > > Of course, everyone I know (myself included) runs their PPro/200 at 233. :-) I don't because I didn't get any documentation with my &(^%$%& Supermicro P6SNE board, and nobody has come forward with the right jumper settings. (Fiddling has given me 150, 180, 200 and a system that won't boot. I hope that the "won't boot" setting isn't 233 8) *sulk* > Jordan -- ]] 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 Tue Jul 29 19:09:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29603 for hackers-outgoing; Tue, 29 Jul 1997 19:09:52 -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 TAA29595 for ; Tue, 29 Jul 1997 19:09:48 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA16495; Wed, 30 Jul 1997 11:39:39 +0930 (CST) From: Michael Smith Message-Id: <199707300209.LAA16495@genesis.atrad.adelaide.edu.au> Subject: Re: Almost JDK 1.1.2 port! In-Reply-To: from "Alex.Boisvert" at "Jul 29, 97 06:58:44 pm" To: boia01@pollux.GEL.USherb.CA (Alex.Boisvert) Date: Wed, 30 Jul 1997 11:39:39 +0930 (CST) 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 Alex.Boisvert stands accused of saying: > > The java virtual machine (java_g) gets a segmentation fault when going > through the _GLOBAL_OFFSET_TABLE_ to execute a function in a dynamic > library (in this case, libawt_g.so). > > The libawt_g.so library is loaded via a dlopen() call. In gdb, I get the > following output after the library is loaded and the VM crashed: > ---- cut here ----- > > Program received signal SIGSEGV, Segmentation fault. > 0x0 in ?? () Ugh. You have almost certainly jumped through a null pointer. What does 'where' tell you? > (gdb) info sharedlibrary > From To Syms Read Shared Object Library > 0x0807a000 0x0808a000 Yes /usr/libexec/ld.so > 0x08091000 0x080ab000 Yes /usr/lib/libm.so.2.0 > 0x080aa000 0x081a5434 Yes /usr/X11R6/lib/libXm.so.1.2 > 0x081a5000 0x081e7000 Yes /usr/X11R6/lib/libXt.so.6.0 > 0x081e6000 0x081f0000 Yes /usr/X11R6/lib/libXext.so.6.1 > 0x081ef000 0x082851a0 Yes /usr/X11R6/lib/libX11.so.6.1 > 0x08285000 0x082ef710 Yes /usr/lib/libc.so.3.0 > 0x09403000 0x0946552c No > /home/alex/jdk/javasrc/build/lib/i386/green_threads/libawt_g.so > (gdb) > > ------ cut here ------ > > Notice the "No" for libawt_g.so in the column "Syms Read". What does > this mean??? It looks like something has failed during the setup of the shared library. > Have I forgotten to do something after dlopen()? Check its return value, maybe? > Regards, > Alex. > > PS: I am using dlsym() to get the address of the function. Are you checking the return value from dlsym? It sounds awfully like you've got NULL back from it and just jumped there... -- ]] 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 Tue Jul 29 19:16:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29859 for hackers-outgoing; Tue, 29 Jul 1997 19:16: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 TAA29852 for ; Tue, 29 Jul 1997 19:16:35 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id TAA03025; Tue, 29 Jul 1997 19:16:26 -0700 (PDT) Message-Id: <199707300216.TAA03025@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: dmaddox@scsn.net cc: Peter Korsten , hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP In-reply-to: Your message of "Tue, 29 Jul 1997 21:30:45 EDT." <19970729213045.26986@scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 19:16:25 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Donald J. Maddox" : > Yeah, this is another misfortune of having to rely on the BIOS to > configure the PnP cards... Adding a new PnP card will almost certainly > scramble your config :-( True, however, I hope, with most modern bios you can disable PnP and really on your favorite OS to init the PnP devices. Sujal Patel's PnP patches can init your PnP device: ftp://rah.star-gate.com/pub/FreeBSD-ISA_PnP_June8.tar.gz Thats an old version however in most cases it works. Hopefully, with the on-going work in the multimedia group we will make the use of PnP devices a very painless experience. Amancio From owner-freebsd-hackers Tue Jul 29 19:18:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29993 for hackers-outgoing; Tue, 29 Jul 1997 19:18:50 -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 TAA29984 for ; Tue, 29 Jul 1997 19:18:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA16641; Wed, 30 Jul 1997 11:47:22 +0930 (CST) From: Michael Smith Message-Id: <199707300217.LAA16641@genesis.atrad.adelaide.edu.au> Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707300146.SAA11272@implode.root.com> from David Greenman at "Jul 29, 97 06:46:08 pm" To: dg@root.com Date: Wed, 30 Jul 1997 11:47:21 +0930 (CST) Cc: terry@lambert.org, 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 David Greenman stands accused of saying: > > There is no problem with using copyout() in the kernel to copy data out to > a user process, assuming that the currently running process is the intended > target of the copy. That is the sole purpose of the function. copyout() > correctly handles all issues of COW/ZF/page faults. The only issue here is that the consumer of your service may _not_ be a user process, eg. in the case of an ABI emulation module. I would specifically request that people avoid using copyout unless they can be _absolutely_ certain that they will only ever be talking to user processes. As I said, this has already caused me heartache several times 8( > uiomove() is escentially a wrapper for copyin/copyout that has an > optimization for the case of kernel-to-kernel copies (in which case it > uses bcopy instead). You're ignoring the support for readv/writev here, although it would seem that user-level scatter-gather never really took off. > -DG -- ]] 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 Tue Jul 29 19:30:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA00642 for hackers-outgoing; Tue, 29 Jul 1997 19:30:09 -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 TAA00636 for ; Tue, 29 Jul 1997 19:30:03 -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 TAA11782; Tue, 29 Jul 1997 19:30:39 -0700 (PDT) Message-Id: <199707300230.TAA11782@implode.root.com> To: Michael Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Location of copyin() and copyout().. In-reply-to: Your message of "Wed, 30 Jul 1997 11:47:21 +0930." <199707300217.LAA16641@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Tue, 29 Jul 1997 19:30:39 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >David Greenman stands accused of saying: >> >> There is no problem with using copyout() in the kernel to copy data out to >> a user process, assuming that the currently running process is the intended >> target of the copy. That is the sole purpose of the function. copyout() >> correctly handles all issues of COW/ZF/page faults. > >The only issue here is that the consumer of your service may _not_ be >a user process, eg. in the case of an ABI emulation module. I would >specifically request that people avoid using copyout unless they can >be _absolutely_ certain that they will only ever be talking to user >processes. > >As I said, this has already caused me heartache several times 8( I don't understand the distinction you're making. copyout *always* runs in the (kernel) context of a user process and the destination is always process (as opposed to kernel) memory. Please explain. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 29 19:33:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA00797 for hackers-outgoing; Tue, 29 Jul 1997 19:33:06 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00778 for ; Tue, 29 Jul 1997 19:32:57 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id TAA05696; Tue, 29 Jul 1997 19:27:31 -0700 (PDT) From: Vinay Bannai Message-Id: <199707300227.TAA05696@agni.nuko.com> Subject: Re: Location of copyin() and copyout().. To: dg@root.com Date: Tue, 29 Jul 1997 19:27:30 -0700 (PDT) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300146.SAA11272@implode.root.com> from "David Greenman" at "Jul 29, 97 06:46:08 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: > >> It is generally considered _extremely_ bad to use copyin/copyout, as it > >> precludes your functions from being called from within kernel space. > >> > >> FWIW, this is what eventually stumped me when it came to getting Linux > >> WABI running on FreeBSD. > > > >This is a good point, considering that kernel preemption is one > >of my own goals. > > > >The issue is recursion with a paging operation in progress. > > > >I think with the limited cases I gave (the page is filled, the > >call made, and the page is still mapped) are OK. > > > >copying out is more likely to cause problems than copying in, > >since you copy in pages after they are touched, but you potentially > >touch on copyout. > > > >Probably there needs to be _copyin/_copyout for the internal usage, > >and a "safe" copyin/copyout for usage which isn't safed against > >reentrancy. > > There is no problem with using copyout() in the kernel to copy data out to > a user process, assuming that the currently running process is the intended > target of the copy. That is the sole purpose of the function. copyout() > correctly handles all issues of COW/ZF/page faults. > uiomove() is escentially a wrapper for copyin/copyout that has an > optimization for the case of kernel-to-kernel copies (in which case it > uses bcopy instead). > > -DG So in a situation where I pin the user pages down (for DMA), it is okay to use copyin()/copyout(). In the meantime, I am having a little trouble with the code that is running on the i960 board. It is essentially probed/attached/mmapped from the host side. It mostly pertains to style and structure on the code that is running on the i960 board. The card offers a broad functionality (depending on the code running on the board). How do I offer these services thru the device driver end on the host side? For instance I can't seem to map the functiions provided by the i960 processor onto the ioctl(). I am ignoring the I2O model for the time being. I want to be able to get the initial prototype atleast working before I touch the I20 specs... Suggestions and words of wisdom gladly accepted... Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Tue Jul 29 19:50:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01629 for hackers-outgoing; Tue, 29 Jul 1997 19:50:02 -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 TAA01597 for ; Tue, 29 Jul 1997 19:49:57 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA17292; Wed, 30 Jul 1997 12:19:49 +0930 (CST) From: Michael Smith Message-Id: <199707300249.MAA17292@genesis.atrad.adelaide.edu.au> Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707300230.TAA11782@implode.root.com> from David Greenman at "Jul 29, 97 07:30:39 pm" To: dg@root.com Date: Wed, 30 Jul 1997 12:19:48 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, 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 David Greenman stands accused of saying: > >David Greenman stands accused of saying: > >> > >> There is no problem with using copyout() in the kernel to copy data out to > >> a user process, assuming that the currently running process is the intended > >> target of the copy. That is the sole purpose of the function. copyout() > >> correctly handles all issues of COW/ZF/page faults. > > > >The only issue here is that the consumer of your service may _not_ be > >a user process, eg. in the case of an ABI emulation module. I would > >specifically request that people avoid using copyout unless they can > >be _absolutely_ certain that they will only ever be talking to user > >processes. > > > >As I said, this has already caused me heartache several times 8( > > I don't understand the distinction you're making. copyout *always* runs in > the (kernel) context of a user process and the destination is always process > (as opposed to kernel) memory. Please explain. If I am writing an ABI emulation function that exchanges data with the emulated binary in one format, but need to pass the data in a different format to/from the function(s) in the kernel which provide the required functionality, I have to perform the format translation in buffers in kernel space. If the kernel function(s) use copyin/copyout, they cannot access these buffers, and thus the emulation cannot be performed. > David Greenman -- ]] 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 Tue Jul 29 19:56:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01925 for hackers-outgoing; Tue, 29 Jul 1997 19:56:33 -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 TAA01920 for ; Tue, 29 Jul 1997 19:56:31 -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 TAA12085; Tue, 29 Jul 1997 19:57:42 -0700 (PDT) Message-Id: <199707300257.TAA12085@implode.root.com> To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Location of copyin() and copyout().. In-reply-to: Your message of "Tue, 29 Jul 1997 19:27:30 PDT." <199707300227.TAA05696@agni.nuko.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 29 Jul 1997 19:57:42 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >So in a situation where I pin the user pages down (for DMA), it is okay to >use copyin()/copyout(). copyin/copyout can only be used at non-interrupt time while running in the context of the process to which you're copying to/from. Otherwise, you have to temporarily map the pages into the kernel address space, after which you can access them directly (i.e. not use copyin/copyout). Does this make sense? The main purpose of copyin/copyout is to provide a machine-independant mechanism for copying data through the kernel<->user protection domain. In the case of the x86, it just happens that user process memory is accessible to the kernel in the lower part of the address space, with one caveat: the i386 processor doesn't honor kernel (CPL 0/supervisor) write protection on pages and thus breaks COW when running in the kernel. So for the i386, copyout, if necessary, simulates a write fault to the affected pages. A secondary purpose of copyin/copyout is to catch page protection violations. There is a mechanism for catching a fatal page fault trap during a copyin/copyout so that the kernel can recover from such an event gracefully rather than crashing. When this happens, copyin/copyout return EFAULT to the caller. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 29 20:09:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02581 for hackers-outgoing; Tue, 29 Jul 1997 20:09:34 -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 UAA02576 for ; Tue, 29 Jul 1997 20:09:29 -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 UAA12221; Tue, 29 Jul 1997 20:10:28 -0700 (PDT) Message-Id: <199707300310.UAA12221@implode.root.com> To: Michael Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Location of copyin() and copyout().. In-reply-to: Your message of "Wed, 30 Jul 1997 12:19:48 +0930." <199707300249.MAA17292@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Tue, 29 Jul 1997 20:10:28 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I don't understand the distinction you're making. copyout *always* runs in >> the (kernel) context of a user process and the destination is always process >> (as opposed to kernel) memory. Please explain. > >If I am writing an ABI emulation function that exchanges data with the >emulated binary in one format, but need to pass the data in a >different format to/from the function(s) in the kernel which provide >the required functionality, I have to perform the format translation >in buffers in kernel space. > >If the kernel function(s) use copyin/copyout, they cannot access these >buffers, and thus the emulation cannot be performed. I still don't understand. copyin/out is only for copying between the kernel and user memory. If this is what you're doing and you don't need the extra features of uiomove (which is designed to do piecemeal copies by keeping track of offsets/lengths in a struct uio), then copyin/out is the function to use. If on the other hand you're copying from kernel<->kernel, then you can just use bcopy. I'm afraid that I started reading this thread rather late into it and don't have the original context...so what are we talking about? :-) -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 29 20:13:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02818 for hackers-outgoing; Tue, 29 Jul 1997 20:13:45 -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 UAA02807 for ; Tue, 29 Jul 1997 20:13:35 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA17635; Wed, 30 Jul 1997 12:41:26 +0930 (CST) From: Michael Smith Message-Id: <199707300311.MAA17635@genesis.atrad.adelaide.edu.au> Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707300227.TAA05696@agni.nuko.com> from Vinay Bannai at "Jul 29, 97 07:27:30 pm" To: vinay@agni.nuko.com (Vinay Bannai) Date: Wed, 30 Jul 1997 12:41:26 +0930 (CST) Cc: dg@root.com, terry@lambert.org, 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 Vinay Bannai stands accused of saying: > > So in a situation where I pin the user pages down (for DMA), it is okay to > use copyin()/copyout(). You don't have to pin them down for copyin/copyout, but it will work fine, yes. > In the meantime, I am having a little trouble with the code that is > running on the i960 board. It is essentially probed/attached/mmapped from > the host side. It mostly pertains to style and structure on the code that > is running on the i960 board. The card offers a broad functionality > (depending on the code running on the board). How do I offer these > services thru the device driver end on the host side? For instance I can't > seem to map the functiions provided by the i960 processor onto the > ioctl(). I am ignoring the I2O model for the time being. I want to be able > to get the initial prototype atleast working before I touch the I20 > specs... Hohohoho, you're working on I2O? 8) I'd be inclined to write the driver as really nothing more than something that provides the probe/attach/map functionality, and then write another layer that sits on top that speaks the protocol that the software on the card does, using the comms facilities that the lower layer driver offers. This allows you to swap upper layers as you swap software on the card. -- ]] 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 Tue Jul 29 20:23:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03281 for hackers-outgoing; Tue, 29 Jul 1997 20:23:32 -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 UAA03271 for ; Tue, 29 Jul 1997 20:23:22 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA17715; Wed, 30 Jul 1997 12:52:19 +0930 (CST) From: Michael Smith Message-Id: <199707300322.MAA17715@genesis.atrad.adelaide.edu.au> Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707300310.UAA12221@implode.root.com> from David Greenman at "Jul 29, 97 08:10:28 pm" To: dg@root.com Date: Wed, 30 Jul 1997 12:52:18 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, 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 David Greenman stands accused of saying: >>> I don't understand the distinction you're making. copyout *always* runs in >>>the (kernel) context of a user process and the destination is always process >>>(as opposed to kernel) memory. Please explain. > > > >If I am writing an ABI emulation function that exchanges data with the > >emulated binary in one format, but need to pass the data in a > >different format to/from the function(s) in the kernel which provide > >the required functionality, I have to perform the format translation > >in buffers in kernel space. > > > >If the kernel function(s) use copyin/copyout, they cannot access these > >buffers, and thus the emulation cannot be performed. > > I still don't understand. copyin/out is only for copying between the kernel > and user memory. If this is what you're doing and you don't need the extra > features of uiomove (which is designed to do piecemeal copies by keeping track > of offsets/lengths in a struct uio), then copyin/out is the function to use. > If on the other hand you're copying from kernel<->kernel, then you can just > use bcopy. I'm afraid that I started reading this thread rather late into it > and don't have the original context...so what are we talking about? :-) AAARGH! 8) 8) 8) How about a specific example, the one that bloodied my nose a little while back. The FreeBSD kernel function i386_set_ldt() uses copyin() to retrieve its arguments from the user process. Linux uses the i386_modify_ldt syscall to perform the same functionality. It has a different set of arguments, which convey essentially the same information. So, I write a function linux_i386_modify_ldt(), which lives in the linux emulation module. It takes the Linux i386_modify_ldt() syscall, converts the arguments to the right format, and tries to call i386_set_ldt(). Only it _can't_, because the latter is using copyin(), and cannot access the argument structure in kernel space. If i386_set_ldt() used uiomove, I could construct a uio structure in linux_i386_modify_ldt() that told uimove that the source address was in kernel space, and i386_set_ldt() wouldn't have to care. So, what I am _begging_ is : do *not* use copyin()/copyout() unless you are absolutely, utterly, 110% certain that you will only _ever_ be talking directly to user memory. This boils down to not ever using copyin/out to handle data in device drivers, syscall handlers, protocol stacks, etc., ie. basically not at all. -- ]] 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 Tue Jul 29 20:32:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03845 for hackers-outgoing; Tue, 29 Jul 1997 20:32:58 -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 UAA03836 for ; Tue, 29 Jul 1997 20:32:55 -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 UAA12396; Tue, 29 Jul 1997 20:33:56 -0700 (PDT) Message-Id: <199707300333.UAA12396@implode.root.com> To: Michael Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Location of copyin() and copyout().. In-reply-to: Your message of "Wed, 30 Jul 1997 12:52:18 +0930." <199707300322.MAA17715@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Tue, 29 Jul 1997 20:33:55 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >So, I write a function linux_i386_modify_ldt(), which lives in the >linux emulation module. It takes the Linux i386_modify_ldt() syscall, >converts the arguments to the right format, and tries to call >i386_set_ldt(). > >Only it _can't_, because the latter is using copyin(), and cannot access >the argument structure in kernel space. Ah, now I understand. Yes, copyin/out do page protection checking and will not allow a copyout to kernel memory or a copyin from kernel memory (since kernel memory is protected against users). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 29 20:45:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04333 for hackers-outgoing; Tue, 29 Jul 1997 20:45:08 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA04328 for ; Tue, 29 Jul 1997 20:45:03 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id UAA16264; Tue, 29 Jul 1997 20:44:55 -0700 Date: Tue, 29 Jul 1997 20:44:55 -0700 From: Sean Eric Fagan Message-Id: <199707300344.UAA16264@kithrup.com> To: hackers@freebsd.org Subject: Re: Location of copyin() and copyout().. In-Reply-To: <199707300310.UAA12221.kithrup.freebsd.hackers@implode.root.com> References: Your message of "Wed, 30 Jul 1997 12:19:48 +0930." <199707300249.MAA17292@genesis.atrad.adelaide.edu.au> Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199707300310.UAA12221.kithrup.freebsd.hackers@implode.root.com> you write: >If on the other hand you're copying from kernel<->kernel, then you can just >use bcopy. I'm afraid that I started reading this thread rather late into it >and don't have the original context...so what are we talking about? :-) Many kernel functions already use copyin/copyout. Consider fstat(). The last thing it does (before a return) is: error = copyout((caddr_t)&ub, (caddr_t)uap->sb, sizeof (ub)); Now consider ibcs2_fstat(). Rather than duplicate the work of fstat (which would really be a bad thing, because fstat may change and ibcs2_fstat may not be updated), ibcs2_fstat goes through some *HORRIBLE* hacks to allocate some space in user space, using the stackgap_alloc() function. If fstat used uiomove(), then it could go to a kernel address. (Admittedly, it would still have to be changed -- it would have to have a struct uio passed in, probably. But then ibcs2_fstat could call that common function, with less pain.) Mind you, I'm probably not going to stop using copyin()/copyout() myself... but it is something to consider. And it's a valid point. (Unless, of course, you don't think that the emulation support is worthwhile :).) Please let me know if this still isn't clear... I've been working on some other stuff, and am tired, and my explanation ability goes downhill quickly when I'm tired :). From owner-freebsd-hackers Tue Jul 29 20:53:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04819 for hackers-outgoing; Tue, 29 Jul 1997 20:53:43 -0700 (PDT) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04814 for ; Tue, 29 Jul 1997 20:53:40 -0700 (PDT) Received: from slip129-37-195-169.nc.us.ibm.net (slip129-37-195-169.nc.us.ibm.net [129.37.195.169]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id DAA155024; Wed, 30 Jul 1997 03:53:16 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Wed, 30 Jul 1997 03:55:20 GMT Message-ID: <33e1a2da.17148628@smtp-gw01.ny.us.ibm.net> References: <199707292329.IAA15471@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707292329.IAA15471@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 UAA04815 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997 08:59:50 +0930 (CST), Michael Smith wrote: >John Kelly stands accused of saying: >> >More specifically, you can only allow _one_ device to drive an ISA >> >IRQ line at any given time. >> >> Not strictly true, see below. > >That depends on whether you feel like violating the bus standard. It can be done without violating any standards. In fact, the TTL logic level standards are what make it possible. With your being knowledgeable in "bus interface design," it's strange you don't already know this. >> >cross-reference the 8250 datasheet for an understanding of the quirks >> >and complexities involved in getting this right. It is _not_ trivial. >> >> I have. It's not hard at all. > >It sounds suspiciously like you are either Marilyn Vos Savant, or >underestimating the situation. It's sounds like you're jumping to conclusions. You haven't read my explanation of the technique yet. >Very few boards these days use the 8259. Most, if not all, of the >current chipsets use a logically equivalent macrocell, however their >electrical characteristics are likely to be very different to those of >a 70's vintage NMOS device. You're the one who brought up the 8259, calling it an "8250." It established a reference design, and its input logic level specs agree precisely with the TTL logic level standards. Even if clone makers didn't follow the 8259's input logic voltages, they would certainly follow the input logic voltages of the TTL standard itself, which not by coincidence, match the input logic voltages of the 8259. >Using diodes and resistors to convert totem-pole outputs into >open-collector-like outputs is highschool electronics. What a negative spin on a positive idea. Why should it require an electrical engineer to make a few simple calculations and modifications? Your smearing phraseology is not very persuasive. >You will note my employer's field in my .sig; my work profile covers >bus and interface design as well as OS and UI development. I do note this: some people swagger about like intellectual bullies, wearing a resume like a chip on their shoulder. >You're quite welcome to butcher your cards and live with the potential >uncertainties involved in what you're doing Butcher my cards? Now you're losing credibility. Anyone with real experience in electronics should be able to solder a few simple parts to a PCB without ruining the board or its components. Or haven't you heard of the common practice of rework and repair? If you can offer some genuine criticism, give it another try. But first read the technique which I will post in a day or so, and attack it on a factual basis, if you can. >The problem arises when you claim that this is a universal case: I never said it was a "universal case." You're twisting my words. First you said any high schooler can do it, and now you're implying it won't work. Well, make up your mind, which is it? >your statements are not helpful when it comes to getting >the message across. >]] Mike Smith, Software Engineer msmith@gsoft.com.au >]] Genesis Software genesis@gsoft.com.au Exactly what I would say about your smear tactics. The notion that serial cards with totem-pole outputs cannot share an edge-triggered ISA interrupt is a widespread misconception, promoted and sustained by those who believe that "tampering" with a factory product amounts to technologic sacrilege. Those of us unconstrained by such feelings can discover what lies beyond the hallowed walls of corporate conformity. Stay tuned. I'll post the technique as soon as I can write it up. John From owner-freebsd-hackers Tue Jul 29 21:26:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06604 for hackers-outgoing; Tue, 29 Jul 1997 21:26:06 -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 VAA06590 for ; Tue, 29 Jul 1997 21:25:55 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA18299; Wed, 30 Jul 1997 13:55:21 +0930 (CST) From: Michael Smith Message-Id: <199707300425.NAA18299@genesis.atrad.adelaide.edu.au> Subject: Re: Sharing interrupts In-Reply-To: <33e1a2da.17148628@smtp-gw01.ny.us.ibm.net> from John Kelly at "Jul 30, 97 03:55:20 am" To: mouth@ibm.net (John Kelly) Date: Wed, 30 Jul 1997 13:55:20 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.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 John Kelly stands accused of saying: > > > >That depends on whether you feel like violating the bus standard. > > It can be done without violating any standards. In fact, the TTL > logic level standards are what make it possible. With your being > knowledgeable in "bus interface design," it's strange you don't > already know this. If you are using a diode-OR construction with pullup resistors (your previous component listing implies this is about the only technique that you could be using), you will have to be using schottky or germanium diodes to meet the V0 specification. You also violate the I1 specification unless you change the resistor values depending on the number of cards you have inserted. Then you violate the termination standard by putting DC loads at various points along the bus. > >Very few boards these days use the 8259. Most, if not all, of the > >current chipsets use a logically equivalent macrocell, however their > >electrical characteristics are likely to be very different to those of > >a 70's vintage NMOS device. > > You're the one who brought up the 8259, calling it an "8250." I specifically and intentionally referenced the 8250 in the context of the sio driver and its enabling/disabling of tristate drive from the UART to the IRQ line. > It established a reference design, and its input logic level specs > agree precisely with the TTL logic level standards. Even if clone > makers didn't follow the 8259's input logic voltages, they would > certainly follow the input logic voltages of the TTL standard itself, > which not by coincidence, match the input logic voltages of the 8259. Actually, most of the chipsets currently in use are CMOS or BiCMOS, and use the 30%/60% 0/-/1 logic level set, usually with TTL-friendly output drivers. > >Using diodes and resistors to convert totem-pole outputs into > >open-collector-like outputs is highschool electronics. > > What a negative spin on a positive idea. Urk. Do you actually work with fast digital electronics? Diode-OR in a fast environment is _disgusting_; you have a made-to-order impedance mismatch, an RC network with an unknown time constant (and a funny knee in the curve to boot), and a beaut spike generator (think about Toff on your 1n4148 as the TP output on the other side of it drives high). > Why should it require an electrical engineer to make a few simple > calculations and modifications? Because these aren't actually "simple". It's like asking why, if all it takes to make a nuclear explosion is a critical mass of fissionables, it took a horde of physicists many years to get it right. > Butcher my cards? Now you're losing credibility. Anyone with real > experience in electronics should be able to solder a few simple parts > to a PCB without ruining the board or its components. Or haven't you > heard of the common practice of rework and repair? Taking a card and modifying it out of spec. counts as "butchering". > The notion that serial cards with totem-pole outputs cannot share an > edge-triggered ISA interrupt is a widespread misconception, promoted > and sustained by those who believe that "tampering" with a factory > product amounts to technologic sacrilege. I really don't give a rat's ass what you do with your hardware, and in fact my own inclinations lie in a very similar plane; I have a lot of hardware that doesn't look very much at all like it did when it left the factory. The gripe I have is that you are claiming that what you are doing is perfectly right and correct, whilst I am describing it more accurately as a bletcherous hack which can have some very unpleasant side effects. This isn't meant to detract from the fact that, at least for you, it works; all I ask is that you and other people understand and admit the basically ugly nature of what you are doing. Just as an aside; the concept of "sharing" an edge-triggered interrupt is laughable in itself. > Stay tuned. I'll post the technique as soon as I can write it up. Parts : 1 signal diode (1n4148 or equivalent) 1 0.25W resistor, 220 ohms. (red, red, brown if you need that) Locate the interrupt output from the UART, on pin 30 of the 40-pin DIP package. You may have to backtrack from the IRQ jumpers on the card if your card uses a different package or an integrated device. Cut the track from this pin, and solder your diode across the gap, with the cathode end (the one with the black band) towards the ISA bus. Solder the resistor from the anode end of the diode to ground. Sound about right? -- ]] 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 Tue Jul 29 21:33:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07050 for hackers-outgoing; Tue, 29 Jul 1997 21:33:50 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07040; Tue, 29 Jul 1997 21:33:42 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id OAA00328; Wed, 30 Jul 1997 14:03:22 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707300433.OAA00328@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199707291935.UAA20712@awfulhak.org> from Brian Somers at "Jul 29, 97 08:35:20 pm" To: brian@awfulhak.org (Brian Somers) Date: Wed, 30 Jul 1997 14:03:20 +0930 (CST) Cc: dk+@ua.net, brian@awfulhak.org, freebsd-hackers@FreeBSD.ORG 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-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 Brian Somers writes: >> In article <199707290356.EAA22036@awfulhak.org> you wrote: >>>>> Yep. I think I'll fix the usage message too - shouldn't it be: >>>>> >>>>>> [yy[mm[dd[hh]]]]mm[.ss]] >> >> It should become >> >> [[[cc]yy[mm[dd[hh]]]]mm[.ss]] >> >> or we are screwed in 866 days from now. > > More like: > >>> cc[yy[mm[dd[hh]]]]]mm[.ss]] > > (you can't have the century without the year). Isn't that just what this syntax suggests? > I'll look into allowing this too. > > On that note, I'd expect a year of 00+n to mean 2000+n up to whatever > the maximum is. Any objections ? I'm still wondering whether this is the way to go. It seems that the number of permutations of individual options is just too much. I can't be bothered to check rigourously what potential there is for ambiguity, but consider: # date 2001 According to the above syntax, this means: Century 20, 1 minute I suspect that this isn't your intention, but I can't see how you can design a syntax which is unambiguous. Even if computers can understand it, people won't be able to. How about a more general parser which can understand dates written in a 'normal' manner. For example: 30 July 1997 14:2 July 30 1997 2:2 pm 30/7/97 14.2 14:2 97.7.30 Of course, deciding whether 4/3/97 means the 4th of March or the 3rd of April is something that will have to be determined in some other manner. Greg From owner-freebsd-hackers Tue Jul 29 21:53:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07828 for hackers-outgoing; Tue, 29 Jul 1997 21:53:20 -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 VAA07821 for ; Tue, 29 Jul 1997 21:53:17 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wtQkE-0000I6-00; Tue, 29 Jul 1997 22:52:18 -0600 To: Michael Smith Subject: Re: Pentium II? Cc: jkh@time.cdrom.com (Jordan K. Hubbard), tom@sdf.com, freebsd@atipa.com, info@pagecreators.com, hackers@freebsd.org In-reply-to: Your message of "Wed, 30 Jul 1997 11:33:19 +0930." <199707300203.LAA16420@genesis.atrad.adelaide.edu.au> References: <199707300203.LAA16420@genesis.atrad.adelaide.edu.au> Date: Tue, 29 Jul 1997 22:52:18 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707300203.LAA16420@genesis.atrad.adelaide.edu.au> Michael Smith writes: : I don't because I didn't get any documentation with my &(^%$%& Supermicro : P6SNE board, and nobody has come forward with the right jumper settings. The supermicro FAQ has jumper settings for many boards, my SNS included. At least for the clock speeds. It isn't too hard to figure out what does what. Also, I have overclocked my 180 to 200 w/o problems, but wasn't brave enough to try 233. Warner From owner-freebsd-hackers Tue Jul 29 22:04:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08402 for hackers-outgoing; Tue, 29 Jul 1997 22:04:05 -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 WAA08374; Tue, 29 Jul 1997 22:03:58 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA03229; Wed, 30 Jul 1997 06:04:33 +0200 From: Luigi Rizzo Message-Id: <199707300404.GAA03229@labinfo.iet.unipi.it> Subject: Advice sought on PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 30 Jul 1997 06:04:33 +0200 (MET DST) Cc: hackers@freebsd.org, multimedia@freebsd.org In-Reply-To: <199707300216.TAA03025@rah.star-gate.com> from "Amancio Hasty" at Jul 29, 97 07:16:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hopefully, with the on-going work in the multimedia group we will > make the use of PnP devices a very painless experience. I am revising the PnP configuration stuff. I have got to a point where it behaves very similarly to the PCI configuration stuff, i.e. it relies on the BIOS to set addresses and IRQs correctly, and then fetches the parameters from the board and passes them to the driver. No manual configuration required (of course, the OS must recognize your card, but that's another problem and is common with PCI stuff -- within some time, a reasonable database of card IDs can be compiled to have things working for a wide range of boards). HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to work correctly (which might be false, see at the end of the message). In order to configure cards correctly, the bios should know which IRQs and which I/O address ranges are used by plain isa devices. The former can be told to some bioses, the latter I have never seen how to do on my systems. This is not a big deal with PCI devices since they usually map addresses in the high range of iospace, but a serious problem with PnP ISA devices where iospace is tight and shared with non PnP devices. Since we cannot trust the BIOS (because it does not have enough info) the only way to do autoconfiguration reliably in FreeBSD is the following: 1 probe & attach pci devices 2 disable all pnp devices, so that they are not recognized by isa probes; 3 probe & attach plain isa devices; 4 configure PnP devices, using info derived from the isa configuration process to determine which address ranges and irqs are busy; 5 activate PnP devices; 6 finally, probe and attach PnP devices. Any comments on the above ? Right now I am doing steps in the order 1, 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can fail in some cases for the reasons stated above. 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 Tue Jul 29 22:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08778 for hackers-outgoing; Tue, 29 Jul 1997 22:12:10 -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 WAA08767 for ; Tue, 29 Jul 1997 22:12:07 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtR3H-0007kx-00; Tue, 29 Jul 1997 22:11:59 -0700 Date: Tue, 29 Jul 1997 22:11:58 -0700 (PDT) From: Tom Samplonius To: spork cc: hackers@freebsd.org Subject: Re: de0 under 2.2-STABLE 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, 29 Jul 1997, spork wrote: > Jul 29 13:00:05 newporn /kernel: de0: link down: cable problem? > > If the cable is plugged back in, the link is dead and the link LED on the > card flashes. netstat -i will freeze after the first line is output. If Use a "-n" too, because it is probably hanging because DNS is unreachable. > I give it a "ifconfig de0 down" and then "ifconfig de0 up" it comes back > and works fine and has a solid link light. > > Is this a known problem? And if so, is there a fix in the works, or is The "ifconfig down", "ifconfig up" is the solution. Just don't unplug the card. The severity of this problem depends on the card you use. > support for the Digital cards going away? No, not at all. Correct media detection is major pain with those cards, though. > Someone had suggested getting the de0 package from 3am-software.com; can > anyone give me a "yay" or "nay" on that? > > Thanks much, > > Charles Tom From owner-freebsd-hackers Tue Jul 29 22:22:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09252 for hackers-outgoing; Tue, 29 Jul 1997 22:22:28 -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 WAA09247 for ; Tue, 29 Jul 1997 22:22:25 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtRDF-0007lK-00; Tue, 29 Jul 1997 22:22:17 -0700 Date: Tue, 29 Jul 1997 22:22:16 -0700 (PDT) From: Tom Samplonius To: FreeBSD Mailing List cc: Rod Ebrahimi , hackers@freebsd.org Subject: Re: Pentium II? 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, 29 Jul 1997, FreeBSD Mailing List wrote: ... > > Not, not quite. At the same clock rate, the PPro is faster, but the PII > > can operate at 266mhz, while the PPro maxes at 200mhz. > > You are correct there. Expandability is much better with the "next > generation." Another plus is that P2s come standard with 512K L2. PPro's come standard with 512k cache too. > Per cycle, the Pro is a better processor, but the higher frequency of > the P2 is definitely a factor. > > > > The PII runs 16-bit software better and adds MMX extensions, but for a > > > network server the PPro will still be faster. > > > > The PII/266 will be faster than a PPro/200. > > On most things. The S. E. C. cartridge is unwieldy and proprietary, and > the 266 is still a bit pricey. I may be antiquated, but I prefer the Pro. > On an unlimited budget, the PII-266 is a good choice. The PII/266 is competitive with the PPro/200 w/512k cache. In fact, when I checked, the PII/266 was cheaper... Plus, a PII/300 will be available soon. > Kevin > > Tom From owner-freebsd-hackers Tue Jul 29 22:22:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09294 for hackers-outgoing; Tue, 29 Jul 1997 22:22: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 WAA09287 for ; Tue, 29 Jul 1997 22:22:54 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtRDf-0007lP-00; Tue, 29 Jul 1997 22:22:43 -0700 Date: Tue, 29 Jul 1997 22:22:43 -0700 (PDT) From: Tom Samplonius To: dennis cc: spork , hackers@freebsd.org Subject: Re: de0 under 2.2-STABLE In-Reply-To: <3.0.32.19970729135626.00dce720@etinc.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 Tue, 29 Jul 1997, dennis wrote: > Has the new de driver and if_media stuff been put in -stable yet, > or does this continue to be a manual operation to add it? > > Dennis Slowly. See manpage for ifconfig. Tom From owner-freebsd-hackers Tue Jul 29 22:26:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09503 for hackers-outgoing; Tue, 29 Jul 1997 22:26:47 -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 WAA09497 for ; Tue, 29 Jul 1997 22:26:43 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtRHR-0007lX-00; Tue, 29 Jul 1997 22:26:37 -0700 Date: Tue, 29 Jul 1997 22:26:36 -0700 (PDT) From: Tom Samplonius To: Craig Johnston cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@freebsd.org Subject: Re: Pentium II? 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, 29 Jul 1997, Craig Johnston wrote: > > > The PII runs 16-bit software better and adds MMX extensions, but for a > > > network server the PPro will still be faster. > > > > The PII/266 will be faster than a PPro/200. > > Not buying into Intel's slot 1 ploy is a good enough reason not to run > PII's. Slot 1 is not going to be around very long and I wouldn't count > on not running into bugs in the relatively untested slot 1 chipset. If you use that arguement, you shouldn't by anything then! The PPro (socket 8?) is doomed too, as Intel will not be developing it further (a 233mhz version would be nice). The Pentium MMX is going to max at 233, before being put out to pasture. So, every option is "doomed"... > The PPro chipset is known to be robust. FreeBSD systems have run > stably on it for quite a while now. It just works. > > Slot 1 is also entirely proprietary -- Intel's response to more > competition than it likes from AMD and now Cyrix. > > The PPro 200 offers all the CPU horsepower you're going to need on > a FreeBSD network server. I'd worry about the amount of RAM and > the speed, latency, and number of hard drives. SCSI, of course. Really? You need to get out more... > regards, > Craig Tom From owner-freebsd-hackers Tue Jul 29 22:27:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09584 for hackers-outgoing; Tue, 29 Jul 1997 22:27:34 -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 WAA09571 for ; Tue, 29 Jul 1997 22:27:30 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtRID-0007lj-00; Tue, 29 Jul 1997 22:27:25 -0700 Date: Tue, 29 Jul 1997 22:27:25 -0700 (PDT) From: Tom Samplonius To: "Jordan K. Hubbard" cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@freebsd.org Subject: Re: Pentium II? In-Reply-To: <10120.870215860@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 Tue, 29 Jul 1997, Jordan K. Hubbard wrote: > > Not, not quite. At the same clock rate, the PPro is faster, but the PII > > can operate at 266mhz, while the PPro maxes at 200mhz. > > Of course, everyone I know (myself included) runs their PPro/200 at 233. :-) > > Jordan My PPro 200 (with 512k cache) doesn't run at all clocked at 233... Tom From owner-freebsd-hackers Tue Jul 29 22:33:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09953 for hackers-outgoing; Tue, 29 Jul 1997 22:33:34 -0700 (PDT) Received: from x22 (ppp6495.on.sympatico.ca [206.172.208.87]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA09947; Tue, 29 Jul 1997 22:33:27 -0700 (PDT) Received: from localhost (tim@localhost) by x22 (8.8.5/8.7.3) with SMTP id BAA00276; Wed, 30 Jul 1997 01:33:00 -0400 (EDT) Date: Wed, 30 Jul 1997 01:32:59 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: grog@FreeBSD.ORG cc: Brian Somers , dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-Reply-To: <199707300433.OAA00328@freebie.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 On Wed, 30 Jul 1997 grog@FreeBSD.ORG wrote: > >>>>>> [yy[mm[dd[hh]]]]mm[.ss]] At risk of missing the obvious, why can't the above simply be extended to [cc[yy[mm[dd[hh]]]]]mm[.ss]] ? This format strikes me as being right since any usually, if the date is off by a large amount (eg. centuries), the year, month, day, hour, and minute will also be off. However, the date being off by a minute or two, while the hour, day, month, year, and century are correct is not unusual. This seems to avoid the below monstrosities. > >> [[[cc]yy[mm[dd[hh]]]]mm[.ss]] > >>> cc[yy[mm[dd[hh]]]]]mm[.ss]] The first is hopelessly ambigious and the 2nd is hopelessly annoying. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. From owner-freebsd-hackers Tue Jul 29 22:47:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA10587 for hackers-outgoing; Tue, 29 Jul 1997 22:47:25 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA10570; Tue, 29 Jul 1997 22:47:17 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id XAA11340; Tue, 29 Jul 1997 23:47:09 -0600 (MDT) Message-Id: <199707300547.XAA11340@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Luigi Rizzo cc: hasty@rah.star-gate.com (Amancio Hasty), hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Wed, 30 Jul 1997 06:04:33 +0200." <199707300404.GAA03229@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Jul 1997 23:47:08 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > Any comments on the above ? Right now I am doing steps in the order 1, > 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can > fail in some cases for the reasons stated above. do you have the MindShare Inc. book on PnP? I've never looked inside it, but if its half as good as their other books (Pentium Processor System Architecture, etc.) it would probably prove invaluable: Plus and Play System Architecture, MindShare Inc., Tom Shanley, Don Anderson Addison Wesley Longman 0-201-41013-30 4/95 Soft Cover 400 pages Designed as a companion volume to the official hardware design guide for Windows 95, this book provides a detailed hardware and software description of the Plug and Play technology that is integrated into Windows 95 and will soon appear in other operating systems, including Windows NT. In addition to coverage of ISA and EISA Plug and Play, PCMCIA and PCI are also discussed. Tom Shanley provides a comprehensive treatment of the subject including: Legacy ISA drawbacks Plug and Play EISA and ISA cards Windows 95 PCI problems Windows 95 PCMCIA enhancements Plug and Play terminology defined Description of configuration registers Resource data structure Plug and Play BIOS Device ID format and Windows 95 device IDs -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Tue Jul 29 23:01:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11298 for hackers-outgoing; Tue, 29 Jul 1997 23:01:59 -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 XAA11264; Tue, 29 Jul 1997 23:01:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA19038; Wed, 30 Jul 1997 15:30:45 +0930 (CST) From: Michael Smith Message-Id: <199707300600.PAA19038@genesis.atrad.adelaide.edu.au> Subject: Re: Advice sought on PnP configuration In-Reply-To: <199707300404.GAA03229@labinfo.iet.unipi.it> from Luigi Rizzo at "Jul 30, 97 06:04:33 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 30 Jul 1997 15:30:44 +0930 (CST) Cc: hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@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 Luigi Rizzo stands accused of saying: > > I am revising the PnP configuration stuff. I have got to a point > where it behaves very similarly to the PCI configuration stuff, > i.e. it relies on the BIOS to set addresses and IRQs correctly, > and then fetches the parameters from the board and passes them to > the driver. No manual configuration required (of course, the OS > must recognize your card, but that's another problem and is common > with PCI stuff -- within some time, a reasonable database of card > IDs can be compiled to have things working for a wide range of > boards). This information is also available from the ECSD, which can also only be fetched from the BIOS. > In order to configure cards correctly, the bios should know which > IRQs and which I/O address ranges are used by plain isa devices. > The former can be told to some bioses, the latter I have never seen > how to do on my systems. The former is available from the ECSD, the latter is specifically covered in the PnP specification. > Since we cannot trust the BIOS (because it does not have enough > info) the only way to do autoconfiguration reliably in FreeBSD is > the following: We should only not trust the BIOS if it is broken. The bottom line here is actually easy to determine; how do Microsoft do it? Do they trust the BIOS if present, or do they start from scratch. Given that we have to work on systems with no BIOS PnP support, I'd be inclined to look for means for locating IRQ availability information (ECSD, perhaps reading back the IRQ routing data from known chipsets), and then use the PnP technique to handle I/O conflicts. > 1 probe & attach pci devices > 2 disable all pnp devices, so that they are not recognized by isa probes; > 3 probe & attach plain isa devices; > 4 configure PnP devices, using info derived from the isa configuration > process to determine which address ranges and irqs are busy; > 5 activate PnP devices; > 6 finally, probe and attach PnP devices. > > Any comments on the above ? Right now I am doing steps in the order 1, > 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can > fail in some cases for the reasons stated above. My personal preference : - gather all the information : PCI probe PnP probe get ISA config (compiled in, datafile, etc.) get PCI/PnP identifier tables (compiled in, bootloader, etc.) - attach PCI devices I/O ports and IRQs are assigned by the PCI rules. - attach PnP devices IRQs are taken from the free pool left after PCI assignment and those marked for 'legacy' use. I/O ports are probed as per the PnP spec. - walk ISA config data, probe possible devices We know which IRQ and I/O resources are still available, we can hunt for devices that match the gaps. I think it's important to leave the 'legacy' devices until _last_, as this prevents a PnP device being accidentally recognised as a 'legacy' device. -- ]] 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 Tue Jul 29 23:15:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11904 for hackers-outgoing; Tue, 29 Jul 1997 23:15:59 -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 XAA11898 for ; Tue, 29 Jul 1997 23:15:56 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtS2l-00001j-00; Tue, 29 Jul 1997 23:15:31 -0700 Date: Tue, 29 Jul 1997 23:15:30 -0700 (PDT) From: Tom Samplonius To: Nate Williams cc: Nelson Murilo , hackers@freebsd.org Subject: Re: SCSI 1542 error In-Reply-To: <199707291542.JAA12346@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 Tue, 29 Jul 1997, Nate Williams wrote: > > I'm have a problem with maybe more well know board. > > > > One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, > > my console say: > > You're not the first. It appears to me from watching the mailing list > that the 1542 boards are not supported in 2.2. *Many* people have > reported problems with them, which unfortunately means that I can no > longer do 2.2 development at home. :( It just appears that bounce buffers are broken. > Nate > > Tom From owner-freebsd-hackers Tue Jul 29 23:17:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11992 for hackers-outgoing; Tue, 29 Jul 1997 23:17:50 -0700 (PDT) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11983 for ; Tue, 29 Jul 1997 23:17:39 -0700 (PDT) Received: (from peter@localhost) by rhiannon.clari.net.au (8.8.5/8.8.5) id QAA29131; Wed, 30 Jul 1997 16:17:21 +1000 (EST) Date: Wed, 30 Jul 1997 16:17:21 +1000 (EST) From: Peter Hawkins Message-Id: <199707300617.QAA29131@rhiannon.clari.net.au> To: hackers@FreeBSD.ORG, info@pagecreators.com Subject: Re: 2.2.1 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Our ISP runs 2.2.2 and it's excellent. Don't go for 2.2.1 when 2.2.2 is the current stable release. Peter From owner-freebsd-hackers Tue Jul 29 23:32:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12759 for hackers-outgoing; Tue, 29 Jul 1997 23:32:09 -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 XAA12700 for ; Tue, 29 Jul 1997 23:31:59 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.6) id QAA03133; Wed, 30 Jul 1997 16:31:03 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id QAA05299; Wed, 30 Jul 1997 16:21:56 +1000 (EST) Message-Id: <199707300621.QAA05299@ogre.dtir.qld.gov.au> To: Nelson Murilo cc: freebsd-hackers@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: SCSI 1542 error References: In-Reply-To: from Nelson Murilo at "Tue, 29 Jul 1997 15:11:28 +0000" Date: Wed, 30 Jul 1997 16:21:56 +1000 From: Stephen McKay Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, 29th July 1997, Nelson Murilo wrote: >One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, >my console say: > >/kernel: sd0 (aha0:0:0): timeout >/kernel: adapter not talking commands... frozen?! >/kernel: aha0: MBO 02 and not 00 (free) >[...] I used to have this problem all the time running 2.0.5 (I think) using this driver with a BT-545S (which can run in 1542 compatible mode). My problem was that the 486DX4/100 I was using wasn't completely compatible with my old Dell motherboard. When I went back to a 33 (and then to a DX2/66) everything was fine. While I never proved my theory conclusively, I think it was a cache coherency problem with the DX4/100. Now I run 2.2.1 using the bt driver with a DX2/66 cpu. There are no problems. >Next step as change speed for 5.0 (default), disable all shadow and >disable check parity, but the problem not stop. My problem was solved by changing the CPU. You could try disabling L1 and L2 caches to see if your problem could be the same as my old problem. If this has no effect, try using only 16Mb of memory. If this helps, there must be bit-rot in the bounce buffer code. Of course, I'd be pissed if it turns out that it was just a code bug all along, and triggered by the faster CPU. I basically gave it away! Stephen. From owner-freebsd-hackers Tue Jul 29 23:40:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA13166 for hackers-outgoing; Tue, 29 Jul 1997 23:40:40 -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 XAA13145; Tue, 29 Jul 1997 23:40:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA19238; Wed, 30 Jul 1997 16:09:29 +0930 (CST) From: Michael Smith Message-Id: <199707300639.QAA19238@genesis.atrad.adelaide.edu.au> Subject: Re: Advice sought on PnP configuration In-Reply-To: <199707300600.PAA19038@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jul 30, 97 03:30:44 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 16:09:29 +0930 (CST) Cc: luigi@labinfo.iet.unipi.it, hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@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 Michael Smith stands accused of saying: > > My personal preference : > > - gather all the information : > PCI probe > PnP probe > get ISA config (compiled in, datafile, etc.) > get PCI/PnP identifier tables (compiled in, bootloader, etc.) > > - attach PCI devices > I/O ports and IRQs are assigned by the PCI rules. > - attach PnP devices > IRQs are taken from the free pool left after PCI assignment and > those marked for 'legacy' use. I/O ports are probed as per the > PnP spec. > - walk ISA config data, probe possible devices > We know which IRQ and I/O resources are still available, > we can hunt for devices that match the gaps. - attach/detach PCCARD devices we know which resources are still free, and can map these across possible config indexes in the card until a match is found. -- ]] 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 Tue Jul 29 23:56:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14023 for hackers-outgoing; Tue, 29 Jul 1997 23:56:26 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13986; Tue, 29 Jul 1997 23:55:59 -0700 (PDT) Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id QAA00650; Wed, 30 Jul 1997 16:25:50 +0930 (CST) From: grog@FreeBSD.ORG Message-Id: <199707300655.QAA00650@freebie.lemis.com> Subject: Re: SCSI 1542 error In-Reply-To: from Tom Samplonius at "Jul 29, 97 11:15:30 pm" To: tom@sdf.com (Tom Samplonius) Date: Wed, 30 Jul 1997 16:25:50 +0930 (CST) Cc: nate@mt.sri.com, nelson@pangeia.com.br, hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Follow-up-to: scsi@freebsd.org 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-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 Tom Samplonius writes: > > On Tue, 29 Jul 1997, Nate Williams wrote: > >>> I'm have a problem with maybe more well know board. >>> >>> One hour after install FreeBSD 2.2.2 on 486, with 32Mb and SCSI 1542C, >>> my console say: >> >> You're not the first. It appears to me from watching the mailing list >> that the 1542 boards are not supported in 2.2. *Many* people have >> reported problems with them, which unfortunately means that I can no >> longer do 2.2 development at home. :( > > It just appears that bounce buffers are broken. I think I'd go along with that. I recently upgraded from a version of 3.0-current just before Christmas last year to the latest version. Since then, without changing the configuration file, I'm getting lots of these messages: Jul 30 13:36:31 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3183d14 Jul 30 13:36:32 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3354d14 Jul 30 13:47:48 freebie /kernel: aha0: DMA beyond end Of ISA: 0x3394d14 Jul 30 13:47:50 freebie /kernel: aha0: DMA beyond end Of ISA: 0x31bfd14 Of course I have BOUNCE_BUFFERS set in the config file. In addition, lots of spurious error messages are caused by my Archive DDS changer. It got so bad (for some reason the driver wasn't able to read or write the tape) that I had to hang it on the 2940 which I usually reserve for disks (where it works perfectly). I'm copying this to -scsi, since it really beloings there. Greg From owner-freebsd-hackers Tue Jul 29 23:57:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14079 for hackers-outgoing; Tue, 29 Jul 1997 23:57: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 XAA14055; Tue, 29 Jul 1997 23:57:09 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA03429; Wed, 30 Jul 1997 07:52:59 +0200 From: Luigi Rizzo Message-Id: <199707300552.HAA03429@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 07:52:58 +0200 (MET DST) Cc: hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707300600.PAA19038@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 30, 97 03:30:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Luigi Rizzo stands accused of saying: > > the driver. No manual configuration required (of course, the OS > > must recognize your card, but that's another problem and is common ... > This information is also available from the ECSD, which can also only > be fetched from the BIOS. wrong wording... I should have said "the OS must _know_ your card, or how can it know that pnp_id 0x12345678 corresponds to the board "foo" and must use driver "bar"... > > In order to configure cards correctly, the bios should know which > > IRQs and which I/O address ranges are used by plain isa devices. > > The former can be told to some bioses, the latter I have never seen > > how to do on my systems. > > The former is available from the ECSD, the latter is specifically > covered in the PnP specification. how ? I am talking about non-pnp devices... > > Since we cannot trust the BIOS (because it does not have enough > > info) the only way to do autoconfiguration reliably in FreeBSD is > > the following: > > We should only not trust the BIOS if it is broken. The bottom line > here is actually easy to determine; how do Microsoft do it? Do they > trust the BIOS if present, or do they start from scratch. > > Given that we have to work on systems with no BIOS PnP support, I'd be > inclined to look for means for locating IRQ availability information > (ECSD, perhaps reading back the IRQ routing data from known chipsets), > and then use the PnP technique to handle I/O conflicts. > > > 1 probe & attach pci devices > > 2 disable all pnp devices, so that they are not recognized by isa probes; > > 3 probe & attach plain isa devices; > > 4 configure PnP devices, using info derived from the isa configuration > > process to determine which address ranges and irqs are busy; > > 5 activate PnP devices; > > 6 finally, probe and attach PnP devices. > > > > Any comments on the above ? Right now I am doing steps in the order 1, > > 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can > > fail in some cases for the reasons stated above. > > My personal preference : > > - gather all the information : > PCI probe > PnP probe > get ISA config (compiled in, datafile, etc.) > get PCI/PnP identifier tables (compiled in, bootloader, etc.) unfortunately, in the current code, a device is probed and attached right after the probe succeeds (otherwise, I guess one should store information on which devices have been probed successfully and where... etc) > - attach PCI devices > I/O ports and IRQs are assigned by the PCI rules. > - attach PnP devices > IRQs are taken from the free pool left after PCI assignment and > those marked for 'legacy' use. I/O ports are probed as per the > PnP spec. > - walk ISA config data, probe possible devices > We know which IRQ and I/O resources are still available, > we can hunt for devices that match the gaps. but this is a problem: you cannot (generally) reprogram isa device, so it would be better to probe them first and then relocate the programmable ones at a later time. As I said, for PCI devices it is not much of a problem: io addresses are generally taken from a different range, DMA does not use the ISA dma controller, and interrupts can be shared. But for PnP... > I think it's important to leave the 'legacy' devices until _last_, as > this prevents a PnP device being accidentally recognised as a 'legacy' > device. same goal that I have, but in a slightly different manner: step 2 _disables_ all pnp devices so they cannot be recognised as legacy devices. so the non-pnp isa attach cannot find PnP devices. As for getting isa config info: the only way we can do it is by looking at what devices have been successfully attached; compiled-in information are not helpful when a kernel such as GENERIC is built, with a ton of different devices compiled in. Thanks 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 Wed Jul 30 00:01:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14477 for hackers-outgoing; Wed, 30 Jul 1997 00:01: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 AAA14456; Wed, 30 Jul 1997 00:01:41 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id AAA00475; Wed, 30 Jul 1997 00:01:14 -0700 (PDT) Message-Id: <199707300701.AAA00475@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: hackers@freebsd.org, multimedia@freebsd.org Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Wed, 30 Jul 1997 06:04:33 +0200." <199707300404.GAA03229@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jul 1997 00:01:13 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Luigi, PCI devices should be probed and attached last for they are they are the most flexible to configure and can share interrupts. Cheers, Amancio >From The Desk Of Luigi Rizzo : > > Hopefully, with the on-going work in the multimedia group we will > > make the use of PnP devices a very painless experience. > > I am revising the PnP configuration stuff. I have got to a point > where it behaves very similarly to the PCI configuration stuff, > i.e. it relies on the BIOS to set addresses and IRQs correctly, > and then fetches the parameters from the board and passes them to > the driver. No manual configuration required (of course, the OS > must recognize your card, but that's another problem and is common > with PCI stuff -- within some time, a reasonable database of card > IDs can be compiled to have things working for a wide range of > boards). > > HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to > work correctly (which might be false, see at the end of the message). > > In order to configure cards correctly, the bios should know which > IRQs and which I/O address ranges are used by plain isa devices. > The former can be told to some bioses, the latter I have never seen > how to do on my systems. This is not a big deal with PCI devices > since they usually map addresses in the high range of iospace, but > a serious problem with PnP ISA devices where iospace is tight and > shared with non PnP devices. > > Since we cannot trust the BIOS (because it does not have enough > info) the only way to do autoconfiguration reliably in FreeBSD is > the following: > > 1 probe & attach pci devices > 2 disable all pnp devices, so that they are not recognized by isa probes; > 3 probe & attach plain isa devices; > 4 configure PnP devices, using info derived from the isa configuration > process to determine which address ranges and irqs are busy; > 5 activate PnP devices; > 6 finally, probe and attach PnP devices. > > Any comments on the above ? Right now I am doing steps in the order 1, > 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can > fail in some cases for the reasons stated above. > > Cheers > Luigi From owner-freebsd-hackers Wed Jul 30 00:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14633 for hackers-outgoing; Wed, 30 Jul 1997 00:04:39 -0700 (PDT) Received: from iclub.nsu.ru (max@iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14628 for ; Wed, 30 Jul 1997 00:04:29 -0700 (PDT) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.5/8.8.5) with SMTP id OAA04807; Wed, 30 Jul 1997 14:02:36 +0700 (NSS) Date: Wed, 30 Jul 1997 14:02:36 +0700 (NSS) From: Max Khon To: Michael Smith cc: hackers@FreeBSD.ORG Subject: Re: AMD PCNet/PCI troubles In-Reply-To: <199707290413.NAA10221@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 Tue, 29 Jul 1997, Michael Smith wrote: > How about giving us a complete description of the problem, including > what (if anything) differs between the Linux and FreeBSD > configurations of the card. Linux uses PCNet32/PCNet PCI optimized driver (dword i/o operations), while FreeBSD uses Generic LANCE/PCNet driver (word i/o access mode) btw, is there anybody going to write PCNet32/PCNet PCI driver for FreeBSD? Linux (and Win95 ;) have no troubles with these network cards > For that matter, have you tried running Linux on this _particular_ > machine? yep. and it runs perfectly. the only reason to against installing Linux is that our main server is a FreeBSD box (YP password shadowing will not work with Linux clients) /max From owner-freebsd-hackers Wed Jul 30 00:06:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14776 for hackers-outgoing; Wed, 30 Jul 1997 00:06:53 -0700 (PDT) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14645; Wed, 30 Jul 1997 00:04:43 -0700 (PDT) Received: from localhost (max@localhost) by iclub.nsu.ru (8.8.5/8.8.5) with SMTP id OAA04814; Wed, 30 Jul 1997 14:05:15 +0700 (NSS) Date: Wed, 30 Jul 1997 14:05:15 +0700 (NSS) From: Max Khon To: grog@FreeBSD.ORG cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: AMD PCNet/PCI troubles In-Reply-To: <199707282240.IAA02358@freebie.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 On Tue, 29 Jul 1997 grog@FreeBSD.ORG wrote: > > but under FreeBSD (unlike Linux) networking sometimes is very slow > > (~30-50K/s via ftp) > > I'm sure this happens under Linux too, like it sometimes happens under > any operating system. It's a bug, probably in the configuration. this does not happen under Linux and Win95 afair there were no troubles with these cards in 2.2-GAMMA /max From owner-freebsd-hackers Wed Jul 30 00:16:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA15242 for hackers-outgoing; Wed, 30 Jul 1997 00:16:36 -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 AAA15219; Wed, 30 Jul 1997 00:16:08 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA19565; Wed, 30 Jul 1997 16:42:49 +0930 (CST) From: Michael Smith Message-Id: <199707300712.QAA19565@genesis.atrad.adelaide.edu.au> Subject: Re: Advice sought on PnP configuration In-Reply-To: <199707300552.HAA03429@labinfo.iet.unipi.it> from Luigi Rizzo at "Jul 30, 97 07:52:58 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Wed, 30 Jul 1997 16:42:48 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@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 Luigi Rizzo stands accused of saying: > > Luigi Rizzo stands accused of saying: > > > > the driver. No manual configuration required (of course, the OS > > > must recognize your card, but that's another problem and is common > ... > > This information is also available from the ECSD, which can also only > > be fetched from the BIOS. > > wrong wording... I should have said "the OS must _know_ your card, or > how can it know that pnp_id 0x12345678 corresponds to the board "foo" and > must use driver "bar"... I was only referring to the resource information being available from the ECSD. > > > In order to configure cards correctly, the bios should know which > > > IRQs and which I/O address ranges are used by plain isa devices. > > > The former can be told to some bioses, the latter I have never seen > > > how to do on my systems. > > > > The former is available from the ECSD, the latter is specifically > > covered in the PnP specification. > > how ? I am talking about non-pnp devices... Have you read the PnP document from Microsoft? The procedure is explicitly detailed in the section on configuring cards. Basically, you configure the card such that it drives half its outputs low and expect to read 0x55 from all its ports, then swap to the other half of its outputs and expect to read 0xaa. If you don't read the right pattern from all the ports, there's something else there as well, so you relocate the card. > > My personal preference : > > > > - gather all the information : > > PCI probe > > PnP probe > > get ISA config (compiled in, datafile, etc.) > > get PCI/PnP identifier tables (compiled in, bootloader, etc.) > > unfortunately, in the current code, a device is probed and attached > right after the probe succeeds (otherwise, I guess one should store > information on which devices have been probed successfully and where... > etc) I appreciate this; I believe that the process should be changed. > > - walk ISA config data, probe possible devices > > We know which IRQ and I/O resources are still available, > > we can hunt for devices that match the gaps. > > but this is a problem: you cannot (generally) reprogram isa device, so > it would be better to probe them first and then relocate the > programmable ones at a later time. As I said, for PCI devices it is not > much of a problem: io addresses are generally taken from a different > range, DMA does not use the ISA dma controller, and interrupts can be > shared. But for PnP... You don't _want_ to reprogram an ISA device. You specifically _avoid_ them in the resource allocation for PnP and PCI devices by using the BIOS/chipset supplied resource information. Thus, when you get to the ISA probe stage, you know that resources allocated can't have ISA devices connected to them. > same goal that I have, but in a slightly different manner: step 2 > _disables_ all pnp devices so they cannot be recognised as legacy > devices. so the non-pnp isa attach cannot find PnP devices. As for > getting isa config info: the only way we can do it is by looking at > what devices have been successfully attached; compiled-in information > are not helpful when a kernel such as GENERIC is built, with a ton of > different devices compiled in. Disabling PnP devices, then probing and then assigning PnP devices later has the (dubious) advantage of helping bind ISA devices to assigned device names/numbers. I don't actually like this very much; the kernel configuration should do no more than enumerate the drivers which will be linked into the kernel; the drivers should then search for their devices using a set of "likely" resources. (Yes, defining "likely" is tough, but the information doesn't belong in the driver.) What I propose basically involves a "Poke and Pray" cycle after the "Plug and Play" process has inserted devices at known-safe locations; what the poking cycle is doing is prodding spaces that either have devices or are empty. -- ]] 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 Wed Jul 30 00:36:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16013 for hackers-outgoing; Wed, 30 Jul 1997 00:36:43 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA16008 for ; Wed, 30 Jul 1997 00:36:40 -0700 (PDT) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.6/8.8.5) with ESMTP id JAA04268 for ; Wed, 30 Jul 1997 09:36:37 +0200 (MDT) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.6/8.8.5) with ESMTP id JAA03751 for ; Wed, 30 Jul 1997 09:36:36 +0200 (MDT) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.6/8.8.6) id JAA25444 for ; Wed, 30 Jul 1997 09:36:34 +0200 (MET DST) From: Andre Albsmeier Message-Id: <199707300736.JAA23201@curry.mchp.siemens.de> Subject: Re: NFS Problems in 2.2 ? In-Reply-To: <199707291925.QAA09968@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Jul 29, 97 04:25:24 pm" To: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Wed, 30 Jul 1997 09:36:24 +0200 (CEST) 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 > Hi, > > I'm having lots of problems with NFS deadlocks in my recent configuration. > Both client and server are 2.2-STABLE, with 3c905 100Mbps ethernet boards. > Right now, for example, I have a netscape and am elm locked. If this helps, > here's the output of a "ps -axlww | grep nfs" on the client: > Same here. I have a 2.2-STABLE server with one SMC 8434 and one SMC8416C. This machine serves: 4 SGIs, 1 Suns, 2 HPs, 2 Linux :-(, 4 Apples and about 100 PCs. Among the PCs there are 4 BSD 2.2-STABLE machines and only one has severe problems. This is a: PPro 200 with 2940 and one SMC8416C (== EtherEZ on ISA BUS). When mounting a nfs drive from the above mentioned server, it takes between 2 and 60 minutes and all nfs activities get frozen. I have some error messages in dmesg: When mounting with "-v -o -i,-s" I get: nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding nfs server p-h:/people: not responding Out of mbuf clusters - increase maxusers! nfs server p-h:/people: not responding When mounting with "-v -o -i,-s,-T" I get: impossible packet length (1516126026) from nfs server se:/people receive error 27 from nfs server se:/people impossible packet length (808342880) from nfs server se:/people receive error 27 from nfs server se:/people impossible packet length (861948492) from nfs server se:/people receive error 27 from nfs server se:/people impossible packet length (721158501) from nfs server se:/people receive error 27 from nfs server se:/people I have changed the ethernetcard already and on the same wire there are other machines which work great... -Andre From owner-freebsd-hackers Wed Jul 30 00:51:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16712 for hackers-outgoing; Wed, 30 Jul 1997 00:51:09 -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 AAA16704 for ; Wed, 30 Jul 1997 00:51:01 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA20088; Wed, 30 Jul 1997 17:20:04 +0930 (CST) From: Michael Smith Message-Id: <199707300750.RAA20088@genesis.atrad.adelaide.edu.au> Subject: Re: AMD PCNet/PCI troubles In-Reply-To: from Max Khon at "Jul 30, 97 02:02:36 pm" To: max@iclub.nsu.ru (Max Khon) Date: Wed, 30 Jul 1997 17:20:03 +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 Max Khon stands accused of saying: > > > How about giving us a complete description of the problem, including > > what (if anything) differs between the Linux and FreeBSD > > configurations of the card. > > Linux uses PCNet32/PCNet PCI optimized driver (dword i/o operations), > while FreeBSD uses Generic LANCE/PCNet driver (word i/o access mode) > btw, is there anybody going to write PCNet32/PCNet PCI driver for FreeBSD? > Linux (and Win95 ;) have no troubles with these network cards This isn't a useful problem description. To answer your question; someone will write a driver if/when they decide it's worth their effort. At the moment, it's easier to buy a card that works than run around writing and supporting a driver for a pile of ungrateful users. > > For that matter, have you tried running Linux on this _particular_ > > machine? > > yep. and it runs perfectly. the only reason to against installing Linux is > that our main server is a FreeBSD box (YP password shadowing will not work > with Linux clients) Well, I guess you have your choice; software that works but is slightly choosy about hardware, or software that loves your hardware but basically doesn't work. Now, if you actually costed your time, and the time that people have spent answering your questions, you'd probably find that it would have been more cost-effective to visit your local Electron Hut and buy a Tulip-based PCI ethernet adapter (about US$50 retail). -- ]] 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 Wed Jul 30 00:54:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA16940 for hackers-outgoing; Wed, 30 Jul 1997 00:54:04 -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 AAA16933; Wed, 30 Jul 1997 00:53:57 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA20171; Wed, 30 Jul 1997 17:22:43 +0930 (CST) From: Michael Smith Message-Id: <199707300752.RAA20171@genesis.atrad.adelaide.edu.au> Subject: Re: AMD PCNet/PCI troubles In-Reply-To: from Max Khon at "Jul 30, 97 02:05:15 pm" To: max@iclub.nsu.ru (Max Khon) Date: Wed, 30 Jul 1997 17:22:43 +0930 (CST) Cc: grog@FreeBSD.ORG, 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 Max Khon stands accused of saying: > > > > but under FreeBSD (unlike Linux) networking sometimes is very slow > > > (~30-50K/s via ftp) > > > > I'm sure this happens under Linux too, like it sometimes happens under > > any operating system. It's a bug, probably in the configuration. > > this does not happen under Linux and Win95 > afair there were no troubles with these cards in 2.2-GAMMA This sounds like it might be a result of the bounce-buffer problems that are being reported recently. > /max -- ]] 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 Wed Jul 30 00:58:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17156 for hackers-outgoing; Wed, 30 Jul 1997 00:58:07 -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 AAA17135; Wed, 30 Jul 1997 00:58:01 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id AAA00286; Wed, 30 Jul 1997 00:56:39 -0700 (PDT) Message-Id: <199707300756.AAA00286@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Michael Smith cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo), hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Wed, 30 Jul 1997 16:42:48 +0930." <199707300712.QAA19565@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jul 1997 00:56:39 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tnks Michalel we do have PnP code to locate the PnP cards. The problem is how to locate the ISA devices whether they are configured by the kernel or not. Cheers, Amancio >From The Desk Of Michael Smith : > Luigi Rizzo stands accused of saying: > > > Luigi Rizzo stands accused of saying: > > > > > > the driver. No manual configuration required (of course, the OS > > > > must recognize your card, but that's another problem and is common > > ... > > > This information is also available from the ECSD, which can also only > > > be fetched from the BIOS. > > > > wrong wording... I should have said "the OS must _know_ your card, or > > how can it know that pnp_id 0x12345678 corresponds to the board "foo" and > > must use driver "bar"... > > I was only referring to the resource information being available from the > ECSD. > > > > > In order to configure cards correctly, the bios should know which > > > > IRQs and which I/O address ranges are used by plain isa devices. > > > > The former can be told to some bioses, the latter I have never seen > > > > how to do on my systems. > > > > > > The former is available from the ECSD, the latter is specifically > > > covered in the PnP specification. > > > > how ? I am talking about non-pnp devices... > > Have you read the PnP document from Microsoft? The procedure is > explicitly detailed in the section on configuring cards. Basically, > you configure the card such that it drives half its outputs low and > expect to read 0x55 from all its ports, then swap to the other half of > its outputs and expect to read 0xaa. If you don't read the right > pattern from all the ports, there's something else there as well, so > you relocate the card. > > > > My personal preference : > > > > > > - gather all the information : > > > PCI probe > > > PnP probe > > > get ISA config (compiled in, datafile, etc.) > > > get PCI/PnP identifier tables (compiled in, bootloader, etc.) > > > > unfortunately, in the current code, a device is probed and attached > > right after the probe succeeds (otherwise, I guess one should store > > information on which devices have been probed successfully and where... > > etc) > > I appreciate this; I believe that the process should be changed. > > > > - walk ISA config data, probe possible devices > > > We know which IRQ and I/O resources are still available, > > > we can hunt for devices that match the gaps. > > > > but this is a problem: you cannot (generally) reprogram isa device, so > > it would be better to probe them first and then relocate the > > programmable ones at a later time. As I said, for PCI devices it is not > > much of a problem: io addresses are generally taken from a different > > range, DMA does not use the ISA dma controller, and interrupts can be > > shared. But for PnP... > > You don't _want_ to reprogram an ISA device. You specifically _avoid_ > them in the resource allocation for PnP and PCI devices by using the > BIOS/chipset supplied resource information. Thus, when you get to the > ISA probe stage, you know that resources allocated can't have ISA > devices connected to them. > > > same goal that I have, but in a slightly different manner: step 2 > > _disables_ all pnp devices so they cannot be recognised as legacy > > devices. so the non-pnp isa attach cannot find PnP devices. As for > > getting isa config info: the only way we can do it is by looking at > > what devices have been successfully attached; compiled-in information > > are not helpful when a kernel such as GENERIC is built, with a ton of > > different devices compiled in. > > Disabling PnP devices, then probing and then assigning PnP devices > later has the (dubious) advantage of helping bind ISA devices to > assigned device names/numbers. I don't actually like this very much; > the kernel configuration should do no more than enumerate the drivers > which will be linked into the kernel; the drivers should then search > for their devices using a set of "likely" resources. (Yes, defining > "likely" is tough, but the information doesn't belong in the driver.) > > What I propose basically involves a "Poke and Pray" cycle after the > "Plug and Play" process has inserted devices at known-safe locations; > what the poking cycle is doing is prodding spaces that either have > devices or are empty. > > -- > ]] 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 Wed Jul 30 01:04:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA17826 for hackers-outgoing; Wed, 30 Jul 1997 01:04:50 -0700 (PDT) Received: from thorin.hway.ru (root@thorin.hway.ru [194.87.58.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA17819 for ; Wed, 30 Jul 1997 01:04:44 -0700 (PDT) Received: from flash.intech.hway.ru (flash.intech.hway.ru [194.87.58.132]) by thorin.hway.ru (8.8.6/8.8.6) with ESMTP id LAA15470; Wed, 30 Jul 1997 11:54:32 +0400 (MSD) Message-Id: <199707300754.LAA15470@thorin.hway.ru> From: "Alexander V. Tischenko" To: "Max Khon" , "Michael Smith" Cc: Subject: Re: AMD PCNet/PCI troubles Date: Wed, 30 Jul 1997 11:50:30 +0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 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 Max, I've got a source for one. It was once a port of linux driver code to 2.1.5-RELEASE. If you need it, i'll send you. Alexander V. Tischenko ---------- > From: Max Khon > To: Michael Smith > Cc: hackers@FreeBSD.ORG > Subject: Re: AMD PCNet/PCI troubles > Date: 30 èþëÿ 1997 ã. 11:02 > > > > On Tue, 29 Jul 1997, Michael Smith wrote: > > > How about giving us a complete description of the problem, including > > what (if anything) differs between the Linux and FreeBSD > > configurations of the card. > > Linux uses PCNet32/PCNet PCI optimized driver (dword i/o operations), > while FreeBSD uses Generic LANCE/PCNet driver (word i/o access mode) > btw, is there anybody going to write PCNet32/PCNet PCI driver for FreeBSD? > Linux (and Win95 ;) have no troubles with these network cards > > > For that matter, have you tried running Linux on this _particular_ > > machine? > > yep. and it runs perfectly. the only reason to against installing Linux is > that our main server is a FreeBSD box (YP password shadowing will not work > with Linux clients) > > /max From owner-freebsd-hackers Wed Jul 30 01:08:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18074 for hackers-outgoing; Wed, 30 Jul 1997 01:08:53 -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 BAA18051; Wed, 30 Jul 1997 01:08:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA20455; Wed, 30 Jul 1997 17:30:42 +0930 (CST) From: Michael Smith Message-Id: <199707300800.RAA20455@genesis.atrad.adelaide.edu.au> Subject: Re: Advice sought on PnP configuration In-Reply-To: <199707300756.AAA00286@rah.star-gate.com> from Amancio Hasty at "Jul 30, 97 00:56:39 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 30 Jul 1997 17:30:42 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG, multimedia@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: > Tnks Michalel we do have PnP code to locate the PnP cards. The problem > is how to locate the ISA devices whether they are configured by the > kernel or not. I'm aware of this. I have just been trying to explain how you do this, as it is detailed in the PnP spec quite clearly. The issue regarding ECSD information and IRQ/DMA resources is very significant as well; without this information you cannot safely perform PnP setup no matter how good your code. > Amancio -- ]] 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 Wed Jul 30 01:15:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18452 for hackers-outgoing; Wed, 30 Jul 1997 01:15:51 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA18443 for ; Wed, 30 Jul 1997 01:15:44 -0700 (PDT) Received: from slip129-37-53-124.ca.us.ibm.net (slip129-37-53-124.ca.us.ibm.net [129.37.53.124]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id IAA19696; Wed, 30 Jul 1997 08:15:21 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Wed, 30 Jul 1997 08:17:25 GMT Message-ID: <33e5c558.25976723@smtp-gw01.ny.us.ibm.net> References: <199707292329.IAA15471@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707292329.IAA15471@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 BAA18444 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997 08:59:50 +0930 (CST), Michael Smith wrote: >I have no problems with you sharing the information Good. Here it is. Is this appropriate for the list? Yes, because the man page for SIO says "Shared IRQs on different cards are not supported," and that statement is false. The multiport support in FreeBSD is NOT the determining factor. Everyone agrees that FreeBSD does support interrupt sharing for non-intelligent multiport cards which have two or more UARTS (on a single ISA adapter). However, to the multiport support in FreeBSD, two or more serial cards can appear to function as a single card as long as each UART is given a unique I/O address. People often say that two or more serial cards with totem-pole or tri-stated outputs cannot ACTIVELY share an edge-triggered ISA interrupt. Once the serial port is opened, either type of driver will hold the IRQ line to ground (logic low). When the UART signals an interrupt, the driver gates a voltage onto the IRQ line, between 3.5 to 4.5 volts (logic high). This means that two serial cards jumpered to use the same IRQ line will fight each other. To signal an interrupt, one card will try to drive the line high while the other card is still holding it to ground. Which one wins? The one holding the line to ground, because TTL pulls low better than it pulls high. So unless they both signal an interrupt at precisely the same instant, neither one will be able to tell the 8259 interrupt controller they need service. This is why people say it won't work. But with diodes, a resistor, and a soldering iron, we can overcome these limitations. If we prevent the TTL drivers from pulling the line to ground, the cards will no longer fight each other. However, we would still want the TTL drivers to gate their voltage onto the line for signaling an interrupt. For that, we need a diode. It's a one-way street for electricity. Serial cards typically have jumpers which select the IRQ line. We can easily break the connection between the IRQ line and the TTL output by pulling the jumper off. Then we can solder a diode between the two pins, orienting the diode with the visible stripe towards the IRQ pin. Do this for each port on each serial card. It does not matter how many ports you have per card or how many cards you have. Since the diodes will prevent every TTL driver from pulling the line to ground, how is this going to work? For an edge triggered interrupt to be recognized, there must be a transition from low to high. TTL specifies that any voltage between -0.5V and 0.8V is a valid input for logic low, and any voltage between 2.0V and 5.5V is a valid input for logic high. On an ISA bus motherboard, another voltage source is present on the IRQ line. There is a 10K (10,000 ohm) resistor connected between the IRQ line and Vcc (5.0V), so when your ISA slots are empty the IRQ line is held high at 5.0V. But with a serial card in place, the TTL driver pulls the line to ground, overpowering the resistor, and the voltage drops to 0.0V. Or at least it would have before we modified the card with diodes. Now that our diodes in place, we can accomplish the same thing with a "pull-down" resistor. A 390 ohm resistor connected between the IRQ line and ground will pull the line IRQ line down to about 0.4V, giving us a reasonable margin of noise immunity between 0.4V and the upper limit of 0.8V for logic low. Since all the cards will be wired together through the IRQ line when installed in the machine, we only need one resistor. Choose any of the modified serial cards and solder the resistor between the IRQ pin (corresponding to IRQ line you are sharing) and a ground pin on the serial card. This card will be the "master" because it must remain in the machine for any of the other modified cards to work properly (do not confuse this with the "master" serial port terminology used in the FreeBSD kernel config). When one of the UARTs signals an interrupt, the TTL output will gate its voltage of 3.5-4.5V through the diode onto the line. It will have enough current to overpower the pull-down resistor and pull the IRQ line up to a voltage recognized as "input high." There will be a small voltage drop across the diode, about 0.5V. That should leave at least 2.9V on the IRQ line, giving a reasonable margin of noise immunity above the "logic high" minimum of 2.0V. Available at Radio Shack, 1N4001silicon diodes are ideal for this application because they have a minimal voltage drop. If those are not in stock, substitute 1N4002 or others of the same family. For our purposes, their higher peak inverse voltage will not matter. John From owner-freebsd-hackers Wed Jul 30 01:48:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19707 for hackers-outgoing; Wed, 30 Jul 1997 01:48:29 -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 BAA19702 for ; Wed, 30 Jul 1997 01:48:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA21116; Wed, 30 Jul 1997 18:18:15 +0930 (CST) From: Michael Smith Message-Id: <199707300848.SAA21116@genesis.atrad.adelaide.edu.au> Subject: Re: Sharing interrupts In-Reply-To: <33e5c558.25976723@smtp-gw01.ny.us.ibm.net> from John Kelly at "Jul 30, 97 08:17:25 am" To: mouth@ibm.net (John Kelly) Date: Wed, 30 Jul 1997 18:18:14 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.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 John Kelly stands accused of saying: > On Wed, 30 Jul 1997 08:59:50 +0930 (CST), Michael Smith wrote: > > >I have no problems with you sharing the information > > Good. Here it is. I hope you don't mind some minor editorial comment. 8) > Is this appropriate for the list? Yes, because the man page for SIO > says "Shared IRQs on different cards are not supported," and that > statement is false. The multiport support in FreeBSD is NOT the > determining factor. It would be if the search for interrupting devices worked "correctly". Whilst there has been talk of this, it hasn't been changed. The current "incorrect" behaviour is probably better. > People often say that two or more serial cards with totem-pole or > tri-stated outputs cannot ACTIVELY share an edge-triggered ISA > interrupt. "It is correct to say" > Once the serial port is opened, either type of driver will > hold the IRQ line to ground (logic low). When the UART signals an > interrupt, the driver gates a voltage onto the IRQ line, between 3.5 > to 4.5 volts (logic high). ... with CMOS devices this is typically a current source, not a voltage source; the drain current-limit resistor is usually aroundthe 50 ohm mark (varies with logic family). With little or no load as is common for CMOS busses, this usually corresponds to very close to 5V. > To signal an interrupt, one card will try to drive the line high while > the other card is still holding it to ground. Which one wins? The > one holding the line to ground, because TTL pulls low better than it > pulls high. So unless they both signal an interrupt at precisely the > same instant, neither one will be able to tell the 8259 interrupt > controller they need service. This is why people say it won't work. CMOS output stages are about as good pulling high as low; this often runs you to about 2.5V. Same difference, really. See any current NatSemi CMOS logic databook for details on the logic level change implemented for most logic families a few years back. > There will be a small voltage drop across the diode, about 0.5V. > That should leave at least 2.9V on the IRQ line, giving a reasonable > margin of noise immunity above the "logic high" minimum of 2.0V. Vih for CMOS devices is 3V (60% of Vdd), Vil is 1.5V (30%). I would suspect that most ISA bus interfaces are more lenient however. > Available at Radio Shack, 1N4001silicon diodes are ideal for this > application because they have a minimal voltage drop. If those are > not in stock, substitute 1N4002 or others of the same family. For > our purposes, their higher peak inverse voltage will not matter. I would avoid the use of silicon power diodes for this application; they have a significant parasitic capacitance, and will generate a substantial spike on the ICU input when your device signals an interrupt. They also have a long Toff (turnoff time), meaning that when your device drives the interrupt output low you will generate another spike and considerable ground noise. They also have a very _substantial_ voltage drop at low current, certainly not "minimal". If you must use a large diode, use a "fast-recovery" type such as a UF4001; ideally, you should be using a fast small-signal diode like the (very cheap) BAT-47. This device also has a much lower Vf(max), around 0.4V, and very low parasitic capacitance. -- ]] 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 Wed Jul 30 01:52:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19840 for hackers-outgoing; Wed, 30 Jul 1997 01:52:13 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19835 for ; Wed, 30 Jul 1997 01:52:11 -0700 (PDT) Received: from slip129-37-53-124.ca.us.ibm.net (slip129-37-53-124.ca.us.ibm.net [129.37.53.124]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id IAA141160; Wed, 30 Jul 1997 08:52:01 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Wed, 30 Jul 1997 08:54:05 GMT Message-ID: <33e7fc5c.40042247@smtp-gw01.ny.us.ibm.net> References: <199707300425.NAA18299@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707300425.NAA18299@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 BAA19836 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997 13:55:20 +0930 (CST), Michael Smith wrote: >This isn't meant to detract from the fact that, at least for you, it >works; all I ask is that you and other people understand and admit >the basically ugly nature of what you are doing. You made some interesting points and I'll keep your post for future reference in case I ever start having problems. But for now, I use it daily without serial errors, so it appears my hack has produced no ill effects. I'm not recommending it as the *best* solution for sharing IRQs. As I stated in another thread, http://www.byterunner.com sells a variety of multiport comm boards already designed for interrupt sharing, at surprisingly reasonable cost. They have an 8-port board with 16650s for about $150, a bargain price compared to an 8-port Digiboard. I'm planning to buy several of them. It may be quicker than soldering all those diodes. :) John From owner-freebsd-hackers Wed Jul 30 01:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20076 for hackers-outgoing; Wed, 30 Jul 1997 01:58:18 -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 BAA20069 for ; Wed, 30 Jul 1997 01:58:15 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 12408 on Wed, 30 Jul 1997 08:58:06 GMT; id IAA12408 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id KAA00795; Wed, 30 Jul 1997 10:56:11 +0200 (MET DST) Message-Id: <199707300856.KAA00795@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: kbrown@primelink.com cc: EMANUELE COSTA , freebsd-hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP In-reply-to: kbrown's message of Sun, 14 Dec 1997 13:20:29 -0500. <3494236D.4C30@primelink.com> Reply-to: marc@bowtie.nl Date: Wed, 30 Jul 1997 10:56:11 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > EMANUELE COSTA wrote: > > > > Hi, > > I'm trying to install a Sound Balster 16 PnP and I've been told > > that I should search for the OSS package. Could anyone help me? > > Thanks in advance, > > EMANUELE > > > > I hardly believe this question is deserving to be in -hackers. Try > perhaps -questions, or better yet, go to radio shack... cause when you > got questions... they've got answers. I think you'll be better of in -multimedia. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Wed Jul 30 02:03:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20363 for hackers-outgoing; Wed, 30 Jul 1997 02:03:08 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20352 for ; Wed, 30 Jul 1997 02:03:05 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id EAA02602; Wed, 30 Jul 1997 04:02:39 -0500 (CDT) Date: Wed, 30 Jul 1997 04:02:39 -0500 (CDT) From: Craig Johnston To: Tom Samplonius cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@FreeBSD.ORG Subject: Re: Pentium II? 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, 29 Jul 1997, Tom Samplonius wrote: > > On Tue, 29 Jul 1997, Craig Johnston wrote: > > > > > The PII runs 16-bit software better and adds MMX extensions, but for a > > > > network server the PPro will still be faster. > > > > > > The PII/266 will be faster than a PPro/200. > > > > Not buying into Intel's slot 1 ploy is a good enough reason not to run > > PII's. Slot 1 is not going to be around very long and I wouldn't count > > on not running into bugs in the relatively untested slot 1 chipset. > > If you use that arguement, you shouldn't by anything then! The PPro Um, no. There's this idea of relative quantities, you see? Slot 1 is going to be short-lived _compared_ to other solutions. How long has socket 7 been ticking along now? It's well known that slot 2 is coming right on the heels of slot 1. Why bother with the Intel "chipset of the week" game? Slot 1 systems don't offer anything you can't do better with the same cash with PPro and socket 7 systems. The only folks likely to benefit from slot 1 at all are likely to be Intel -- they'll make a bundle off upgrade-happy power-lusers who've been exposed to one too many Ziff-Davis magazines. > (socket 8?) is doomed too, as Intel will not be developing it further (a > 233mhz version would be nice). The Pentium MMX is going to max at 233, > before being put out to pasture. So, every option is "doomed"... The real issue is that the PII is untried, whereas FreeBSD systems on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous ftp users) have been ticking along reliably for quite some time now. > > The PPro 200 offers all the CPU horsepower you're going to need on > > a FreeBSD network server. I'd worry about the amount of RAM and > > the speed, latency, and number of hard drives. SCSI, of course. > > Really? You need to get out more... Oh, I should have said "unless you're going to be doing a significant fraction of what ftp.cdrom.com does" -- pardon me. ( Notice I said "on a network server.") So exactly whose critical FreeBSD systems are you building with PIIs right now, Tom? -Craig From owner-freebsd-hackers Wed Jul 30 02:03:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20395 for hackers-outgoing; Wed, 30 Jul 1997 02:03:15 -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 CAA20377 for ; Wed, 30 Jul 1997 02:03:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA21210; Wed, 30 Jul 1997 18:32:59 +0930 (CST) From: Michael Smith Message-Id: <199707300902.SAA21210@genesis.atrad.adelaide.edu.au> Subject: Re: Sharing interrupts In-Reply-To: <33e7fc5c.40042247@smtp-gw01.ny.us.ibm.net> from John Kelly at "Jul 30, 97 08:54:05 am" To: mouth@ibm.net (John Kelly) Date: Wed, 30 Jul 1997 18:32:58 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.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 John Kelly stands accused of saying: > > You made some interesting points and I'll keep your post for future > reference in case I ever start having problems. But for now, I use it > daily without serial errors, so it appears my hack has produced no ill > effects. Qool! More to the point, thanks for the less-technical recipie. Aside from the odd gripe, I reckon it's worth adding to the handbook in a 'munging your hardware for useful results' section. > surprisingly reasonable cost. They have an 8-port board with 16650s > for about $150, a bargain price compared to an 8-port Digiboard. I'm > planning to buy several of them. It may be quicker than soldering all > those diodes. :) *chuckle* > John -- ]] 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 Wed Jul 30 02:03:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20481 for hackers-outgoing; Wed, 30 Jul 1997 02:03:57 -0700 (PDT) Received: from out1.ibm.net (out1.ibm.net [165.87.194.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA20474 for ; Wed, 30 Jul 1997 02:03:53 -0700 (PDT) Received: from slip129-37-53-124.ca.us.ibm.net (slip129-37-53-124.ca.us.ibm.net [129.37.53.124]) by out1.ibm.net (8.8.5/8.6.9) with SMTP id JAA89708; Wed, 30 Jul 1997 09:03:43 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Wed, 30 Jul 1997 09:05:47 GMT Message-ID: <33e90332.41786720@smtp-gw01.ny.us.ibm.net> References: <199707300848.SAA21116@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707300848.SAA21116@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 CAA20475 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997 18:18:14 +0930 (CST), you wrote: >I would avoid the use of silicon power diodes for this application; >they have a significant parasitic capacitance, and will generate a >substantial spike on the ICU input when your device signals an >interrupt. They also have a long Toff (turnoff time), meaning that >when your device drives the interrupt output low you will generate >another spike and considerable ground noise. They also have a very >_substantial_ voltage drop at low current, certainly not "minimal". > >If you must use a large diode, use a "fast-recovery" type such as a >UF4001; ideally, you should be using a fast small-signal diode like >the (very cheap) BAT-47. This device also has a much lower Vf(max), >around 0.4V, and very low parasitic capacitance. More interesting points. Thanks for the heads-up. John From owner-freebsd-hackers Wed Jul 30 04:50:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA26006 for hackers-outgoing; Wed, 30 Jul 1997 04:50:48 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25998 for ; Wed, 30 Jul 1997 04:50:45 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA00350 for hackers@freebsd.org; Wed, 30 Jul 1997 07:05:03 -0400 (EDT) From: Peter Dufault Message-Id: <199707301105.HAA00350@hda.hda.com> Subject: Assigning PRS to myself To: hackers@freebsd.org Date: Wed, 30 Jul 1997 07:05:01 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (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 want to assign all P1003.4 and rtprio PRS to myself. How do I do that, outside of asking someone? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hackers Wed Jul 30 05:02:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA26481 for hackers-outgoing; Wed, 30 Jul 1997 05:02:56 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26460; Wed, 30 Jul 1997 05:02:47 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp12.monmouth.com [205.164.221.44]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id IAA26213; Wed, 30 Jul 1997 08:00:31 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id IAA15575 (8.8.5/IDA-1.6); Wed, 30 Jul 1997 08:02:41 -0400 (EDT) From: Bill Pechter Message-ID: <199707301202.IAA15575@i4got.lakewood.com> Subject: Re: SCSI 1542 error To: grog@FreeBSD.ORG Date: Wed, 30 Jul 1997 08:02:41 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300655.QAA00650@freebie.lemis.com> from "grog@FreeBSD.ORG" at "Jul 30, 97 04:25:50 pm" Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL19 (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 > Tom Samplonius writes: > > > > On Tue, 29 Jul 1997, Nate Williams wrote: > > > Jul 30 13:47:50 freebie /kernel: aha0: DMA beyond end Of ISA: 0x31bfd14 > > Of course I have BOUNCE_BUFFERS set in the config file. > > In addition, lots of spurious error messages are caused by my Archive > DDS changer. It got so bad (for some reason the driver wasn't able to > read or write the tape) that I had to hang it on the 2940 which I > usually reserve for disks (where it works perfectly). > > I'm copying this to -scsi, since it really beloings there. > > Greg > BTW -- the ch device doesn't use bounce buffers at all (unfortunately)... I've got the same problem with 2.2.2... I don't see any bounce problems in 2.2.2 except with the archive changer. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hackers Wed Jul 30 05:07:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA26706 for hackers-outgoing; Wed, 30 Jul 1997 05:07:39 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA26700 for ; Wed, 30 Jul 1997 05:07:34 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA00393 for hackers@freebsd.org; Wed, 30 Jul 1997 07:21:56 -0400 (EDT) From: Peter Dufault Message-Id: <199707301121.HAA00393@hda.hda.com> Subject: Re: where to put access restriction for scheduling classes In-Reply-To: <199707300126.VAA16803@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jul 29, 97 09:26:58 pm" To: hackers@freebsd.org Date: Wed, 30 Jul 1997 07:21:55 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (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 (Sorry that went out on -current. Redirecting to -hackers) > No shell should break as a result of defining a new resource limit. > Therefore, you should update setusercontext(3) and the two system > shells, and let the other shells fend for themselves. Shells won't break, but you won't be able to set the new resource using "limit" in unchanged shells. I'll do as you suggest - add RLIMIT_SCHEDULER and change csh and sh to support it. Then specific users can be permitted to change their process scheduler. I do have a related question - ptolemy for example uses 1003.4 process scheduling semantics for some simulations to ensure things run the way they want them to. I'd like per-process group scheduling so that one could ensure that a group of processes preempt each other without potentially hogging the CPU. This would be good both for this sort of simulation and for development of realtime systems. It is "half threaded": the process group as a whole would be fairly scheduled with other processes, but when it was readied the appropriate process would run, Does anyone have suggestions for how to specify this and how to implement this? Source should not have to be changed, so again an inherited per-process flag for real time flavor would be appropriate. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hackers Wed Jul 30 05:56:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA28661 for hackers-outgoing; Wed, 30 Jul 1997 05:56:55 -0700 (PDT) Received: from zeus.gel.usherb.ca (zeus.gel.usherb.ca [132.210.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA28656 for ; Wed, 30 Jul 1997 05:56:52 -0700 (PDT) Received: from castor.gel.usherb.ca by zeus.gel.usherb.ca (4.1/SMI-4.1) id AA03062; Wed, 30 Jul 97 08:56:48 EDT Received: by castor.gel.usherb.ca (SMI-8.6/SMI-SVR4) id IAA04389; Wed, 30 Jul 1997 08:56:47 -0400 Date: Wed, 30 Jul 1997 08:56:46 -0400 (EDT) From: "Alex.Boisvert" To: Chuck Robey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Almost JDK 1.1.2 port! 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 > > What mode are you using for the calls, RTLD_LAZY or RTLD_NOW? Maybe you > should change that? > I am sorry to have asked the question since I found out that the problem isn't related to dynamic linking (ld.so)... BTW: I'm using RTLD_LAZY. Where is RTLD_NOW documented? From owner-freebsd-hackers Wed Jul 30 06:19:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA29680 for hackers-outgoing; Wed, 30 Jul 1997 06:19:18 -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 GAA29667 for ; Wed, 30 Jul 1997 06:19:13 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id WAA22225; Wed, 30 Jul 1997 22:48:55 +0930 (CST) From: Michael Smith Message-Id: <199707301318.WAA22225@genesis.atrad.adelaide.edu.au> Subject: Re: Almost JDK 1.1.2 port! In-Reply-To: from "Alex.Boisvert" at "Jul 30, 97 08:56:46 am" To: boia01@castor.GEL.USherb.CA (Alex.Boisvert) Date: Wed, 30 Jul 1997 22:48:55 +0930 (CST) Cc: chuckr@glue.umd.edu, 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 Alex.Boisvert stands accused of saying: > > > > What mode are you using for the calls, RTLD_LAZY or RTLD_NOW? Maybe you > > should change that? > > > > I am sorry to have asked the question since I found out that the problem > isn't related to dynamic linking (ld.so)... > > BTW: I'm using RTLD_LAZY. Where is RTLD_NOW documented? 'man dlopen' -- ]] 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 Wed Jul 30 06:50:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA01537 for hackers-outgoing; Wed, 30 Jul 1997 06:50:51 -0700 (PDT) Received: from zeus.gel.usherb.ca (zeus.gel.usherb.ca [132.210.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA01522 for ; Wed, 30 Jul 1997 06:50:47 -0700 (PDT) Received: from castor.gel.usherb.ca by zeus.gel.usherb.ca (4.1/SMI-4.1) id AA04132; Wed, 30 Jul 97 09:50:41 EDT Received: by castor.gel.usherb.ca (SMI-8.6/SMI-SVR4) id JAA05743; Wed, 30 Jul 1997 09:50:41 -0400 Date: Wed, 30 Jul 1997 09:50:40 -0400 (EDT) From: "Alex.Boisvert" To: Michael Smith Cc: chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Almost JDK 1.1.2 port! In-Reply-To: <199707301318.WAA22225@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 > > > > BTW: I'm using RTLD_LAZY. Where is RTLD_NOW documented? > > 'man dlopen' > Under 2.2.1, there is not reference to RTLD_* in the dlopen man page (dated 24 september 1989!) Maybe it's time to upgrade, but for a few update man pages, that seems odd. Alex. From owner-freebsd-hackers Wed Jul 30 06:58:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02033 for hackers-outgoing; Wed, 30 Jul 1997 06:58:32 -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 GAA02025 for ; Wed, 30 Jul 1997 06:58:29 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA22566; Wed, 30 Jul 1997 23:28:13 +0930 (CST) From: Michael Smith Message-Id: <199707301358.XAA22566@genesis.atrad.adelaide.edu.au> Subject: Re: Almost JDK 1.1.2 port! In-Reply-To: from "Alex.Boisvert" at "Jul 30, 97 09:50:40 am" To: boia01@castor.GEL.USherb.CA (Alex.Boisvert) Date: Wed, 30 Jul 1997 23:28:13 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, chuckr@glue.umd.edu, 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 Alex.Boisvert stands accused of saying: > > > > > > BTW: I'm using RTLD_LAZY. Where is RTLD_NOW documented? > > > > 'man dlopen' > > > > Under 2.2.1, there is not reference to RTLD_* in the dlopen man page > (dated 24 september 1989!) > > Maybe it's time to upgrade, but for a few update man pages, that seems odd. Sorry; I was in a 3.x window - you're quie correct, RTLD_LAZY isn't documented for 2.2 > Alex. > > -- ]] 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 Wed Jul 30 07:03:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA02392 for hackers-outgoing; Wed, 30 Jul 1997 07:03:02 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA02383 for ; Wed, 30 Jul 1997 07:02:56 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id KAA26737; Wed, 30 Jul 1997 10:10:59 -0400 (EDT) Message-Id: <3.0.32.19970730100137.00ca6530@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 30 Jul 1997 10:01:40 -0400 To: Tom Samplonius From: dennis Subject: Re: de0 under 2.2-STABLE Cc: spork , hackers@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:22 PM 7/29/97 -0700, Tom Samplonius wrote: > >On Tue, 29 Jul 1997, dennis wrote: > >> Has the new de driver and if_media stuff been put in -stable yet, >> or does this continue to be a manual operation to add it? >> >> Dennis > > Slowly. See manpage for ifconfig. > >Tom Is there something wrong with it? Why the hesitation...this stuff has been around (and necessary to work with 100Mb/s cards) for quite awhile. Dennis > > > From owner-freebsd-hackers Wed Jul 30 07:09:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA03074 for hackers-outgoing; Wed, 30 Jul 1997 07:09:32 -0700 (PDT) Received: from eurogate.nortel.co.uk (pp@eurogate.nortel.co.uk [192.100.101.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA03069 for ; Wed, 30 Jul 1997 07:09:30 -0700 (PDT) Received: from hedera.bnr.co.uk (actually eharg1e1.nortel.co.uk) by eurogate.nortel.co.uk with SMTP (PP); Wed, 30 Jul 1997 13:58:48 +0000 Received: from bhars8cd.europe.nortel.com by hedera.bnr.co.uk with SMTP (PP); Wed, 30 Jul 1997 13:58:32 +0000 Received: from bharh4d4.europe.nortel.com by bhars8cd.europe.nortel.com (5.61++/UK-2.1-MX-nortel-(19970425)) with SMTP id AA27043; Wed, 30 Jul 97 14:58:22 +0100 Date: Wed, 30 Jul 1997 14:56:32 +0100 (BST) From: "Andy J. Smith" X-Sender: ajsmith@bharh4d4.europe.nortel.com To: freebsd-hackers@freebsd.org Subject: Cross compiling for FreeBSD 3.0 Message-Id: Organisation: Nortel Technology Ltd. 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 have been directed here from the gnu.gcc.help newsgroup. I have several linux boxes (2.0.30 kernel) and I want to install GCC as a cross-compiler so I can produce FreeBSD binaries. Can anyone help me out and give me some info as to home I might do this? I have limited access to a FreeBSD 3.0 sytem, so if I need libraries, header files and includes I could get them that way, but it is a real hassle so I'm hoping I don't need too much. Please mail to me as well as the list as this is a one-off question and I am not subscribed. Thanks, Andy Only one creature could have duplicated the expressions on their faces, and that would be a pigeon who has heard not only that Lord Nelson has got down off his column but has also been seen buying a 12-bore repeater and a box of cartridges. -- (Terry Pratchett, Mort) From owner-freebsd-hackers Wed Jul 30 07:37:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA04634 for hackers-outgoing; Wed, 30 Jul 1997 07:37:53 -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 HAA04599; Wed, 30 Jul 1997 07:37:19 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA03822; Wed, 30 Jul 1997 15:22:47 +0200 From: Luigi Rizzo Message-Id: <199707301322.PAA03822@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 15:22:47 +0200 (MET DST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707300712.QAA19565@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 30, 97 04:42:29 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > The former is available from the ECSD, the latter is specifically > > > covered in the PnP specification. > > > > how ? I am talking about non-pnp devices... > > Have you read the PnP document from Microsoft? The procedure is > explicitly detailed in the section on configuring cards. Basically, > you configure the card such that it drives half its outputs low and > expect to read 0x55 from all its ports, then swap to the other half of ... ok, clearly I need a good reading on PnP... I'll go and get some book :) Cheers Luigi From owner-freebsd-hackers Wed Jul 30 07:58:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA06275 for hackers-outgoing; Wed, 30 Jul 1997 07:58:42 -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 HAA06268 for ; Wed, 30 Jul 1997 07:58:39 -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 KAA08954; Wed, 30 Jul 1997 10:58:35 -0400 Date: Fri, 1 Aug 1997 10:58:47 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Alex.Boisvert" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Almost JDK 1.1.2 port! 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, 30 Jul 1997, Alex.Boisvert wrote: > > > > What mode are you using for the calls, RTLD_LAZY or RTLD_NOW? Maybe you > > should change that? > > > > I am sorry to have asked the question since I found out that the problem > isn't related to dynamic linking (ld.so)... > > BTW: I'm using RTLD_LAZY. Where is RTLD_NOW documented? Among other places, the dlopen man page. > > ----------------------------+----------------------------------------------- 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 Wed Jul 30 08:01:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA06507 for hackers-outgoing; Wed, 30 Jul 1997 08:01:07 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA06500 for ; Wed, 30 Jul 1997 08:01:02 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id LAA01362; Wed, 30 Jul 1997 11:00:53 -0400 (EDT) Date: Wed, 30 Jul 1997 11:00:53 -0400 (EDT) From: Charles Henrich Message-Id: <199707301500.LAA01362@crh.cl.msu.edu> To: craig@gnofn.org, freebsd-hackers@freebsd.org Subject: Re: Pentium II? Newsgroups: lists.freebsd.hackers References: <5rn128$57r$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >The real issue is that the PII is untried, whereas FreeBSD systems >on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous >ftp users) have been ticking along reliably for quite some time >now. I've been running a P-II/266 for months, overclocked at 300 even. It works flawlessly. It blows the hell out of my PPro/233. Hands Down, left right, forwards, backwards, and inside out. And I dont give a rip if its Slot 1, Slot 3, socket 8, or a bunch of wires glued to a CPU. I buy motherboards and processors together, and I dont give a rip what the connection is. I require performance for my apps, and there's nothing on the planet that will (currently) touch a P-II/300. -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Jul 30 08:01:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA06544 for hackers-outgoing; Wed, 30 Jul 1997 08:01:22 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA06539 for ; Wed, 30 Jul 1997 08:01:20 -0700 (PDT) Received: from slip129-37-195-126.nc.us.ibm.net (slip129-37-195-126.nc.us.ibm.net [129.37.195.126]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id PAA102342; Wed, 30 Jul 1997 15:00:29 GMT From: mouth@ibm.net (John Kelly) To: Michael Smith Cc: msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts Date: Wed, 30 Jul 1997 15:02:32 GMT Message-ID: <33df4e3f.1984385@smtp-gw01.ny.us.ibm.net> References: <199707300902.SAA21210@genesis.atrad.adelaide.edu.au> In-Reply-To: <199707300902.SAA21210@genesis.atrad.adelaide.edu.au> X-Mailer: Forte Agent 1.01/16.397 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 IAA06540 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Jul 1997 18:32:58 +0930 (CST), Michael Smith wrote: >Qool! More to the point, thanks for the less-technical recipie. >Aside from the odd gripe, I reckon it's worth adding to the handbook >in a 'munging your hardware for useful results' section. BTW, I used a meter to measure and verify all the voltages given in that recipe. With two machines connected via serial ports and a crossover cable as outlined in the handbook, I used the kernel debugger to step through sioprobe line by line, noting the voltage levels and when they changed. That in itself was educational. Even if my recipe has little project value for most readers, I think adding it to the handbook (with some of the caveats you mentioned) will help future readers better understand interrupt sharing and how FreeBSD supports non-intelligent multiport serial cards. When I first read the FreeBSD docs and man page on that topic, I was confused. Some of it is unclear and misleading. John From owner-freebsd-hackers Wed Jul 30 08:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA07425 for hackers-outgoing; Wed, 30 Jul 1997 08:12:49 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA07419 for ; Wed, 30 Jul 1997 08:12:46 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id LAA18487; Wed, 30 Jul 1997 11:15:22 -0400 (EDT) Date: Wed, 30 Jul 1997 11:15:22 -0400 (EDT) From: "David E. Cross" To: Guido van Rooij cc: FreeBSD-hackers Subject: Re: bad sectors and sysinstall In-Reply-To: <199707292303.BAA10072@gvr.win.tue.nl> 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, 30 Jul 1997, Guido van Rooij wrote: > I've got an IDE drive with bad sectors I still want to use. > I think bad144 is the thing to use, however sysinstall does not > seem to be able to specify it. Am I missing something? > Further; are there any caveats I should know? > When you are partitioning the drive ( _not_ labeling it ), select each partition that you want to scan for bad blocks and hit 'b'. That will have bad144 run on those partitions automatically. -- David Cross From owner-freebsd-hackers Wed Jul 30 08:46:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10267 for hackers-outgoing; Wed, 30 Jul 1997 08:46:27 -0700 (PDT) Received: from onyx.atipa.com (user1854@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA10254 for ; Wed, 30 Jul 1997 08:46:17 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 30 Jul 1997 15:48:28 -0000 Date: Wed, 30 Jul 1997 09:48:28 -0600 (MDT) From: FreeBSD Mailing List X-Sender: freebsd@dot.ishiboo.com To: hackers@freebsd.org cc: Tom Samplonius Subject: Re: Pentium II? 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, 30 Jul 1997, Craig Johnston wrote: > > > Not buying into Intel's slot 1 ploy is a good enough reason not to run > > > PII's. Slot 1 is not going to be around very long and I wouldn't count > > > on not running into bugs in the relatively untested slot 1 chipset. > > If you use that arguement, you shouldn't by anything then! The PPro > > Um, no. There's this idea of relative quantities, you see? Slot 1 > is going to be short-lived _compared_ to other solutions. How long > has socket 7 been ticking along now? It's well known that slot 2 is > coming right on the heels of slot 1. Just to make the point more muddled, the PII's and PPro's use THE EXACT SAME CHIPSET! In fact, you can buy a SEC to ZIF SOCKET 8 converter. The chipset is not or should not be the concern (97% of all P2's and Pro's are using the Intel Natoma (440FX) chipset). > Why bother with the Intel "chipset of the week" game? Slot 1 systems > don't offer anything you can't do better with the same cash with PPro and > socket 7 systems. The only folks likely to benefit from slot 1 at > all are likely to be Intel -- they'll make a bundle off upgrade-happy > power-lusers who've been exposed to one too many Ziff-Davis magazines. With the same cash is important. P2 boards will be more expensive, along with the chips. > > (socket 8?) is doomed too, as Intel will not be developing it further (a > > 233mhz version would be nice). The Pentium MMX is going to max at 233, > > before being put out to pasture. So, every option is "doomed"... ZIF architecture is being promoted heavily by AMD, Cyrix, etc. The new Socket 7 motherboards we carry go up to 363MHz (66 x 5.5) and above (83MHZ x 4.5). I expect ZIF-8 solutions to be available soon from competitive vendors. > The real issue is that the PII is untried, whereas FreeBSD systems > on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous > ftp users) have been ticking along reliably for quite some time > now. Correct. Pro is definitely solid. > > > The PPro 200 offers all the CPU horsepower you're going to need on > > > a FreeBSD network server. I'd worry about the amount of RAM and > > > the speed, latency, and number of hard drives. SCSI, of course. > > > > Really? You need to get out more... SCSI vs. IDE is a whole different issue, but I definitely agree with the gist of the statement. Overemphasizing the CPU is a common mistake. > Oh, I should have said "unless you're going to be doing a significant > fraction of what ftp.cdrom.com does" -- pardon me. ( Notice I said > "on a network server.") The main justifications for the P2 are gaming and multimedia. If you are a gamer, I dont think you will be using FreeBSD for your jollies. For NFS servers, web servers, and shell machines, I'd go with the Pro. We migrated our machines from Pentium 133's to Pro 166 512k's, and the network as a whole was very noticably faster. Our custmoers who know almost all go with Pro. Check out http://www.atipa.com/pentium2.shtml for additional reference. Kevin From owner-freebsd-hackers Wed Jul 30 08:47:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10323 for hackers-outgoing; Wed, 30 Jul 1997 08:47:01 -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 IAA10315 for ; Wed, 30 Jul 1997 08:46:54 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtaxZ-0000Lp-00; Wed, 30 Jul 1997 08:46:45 -0700 Date: Wed, 30 Jul 1997 08:46:45 -0700 (PDT) From: Tom Samplonius To: dennis cc: spork , hackers@freebsd.org Subject: Re: de0 under 2.2-STABLE In-Reply-To: <3.0.32.19970730100137.00ca6530@etinc.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 Wed, 30 Jul 1997, dennis wrote: > At 10:22 PM 7/29/97 -0700, Tom Samplonius wrote: > > > >On Tue, 29 Jul 1997, dennis wrote: > > > >> Has the new de driver and if_media stuff been put in -stable yet, > >> or does this continue to be a manual operation to add it? > >> > >> Dennis > > > > Slowly. See manpage for ifconfig. > > > >Tom > > Is there something wrong with it? Why the hesitation...this stuff has > been around (and necessary to work with 100Mb/s cards) for quite > awhile. > > Dennis It isn't necessary for 100mbs cards. ifmedia requires corresponding changes to ifconfig, etc. and the driver. Someone on the list was looking for testers for the a new de driver he was going to commit, as he didn't have any of the appropiate hw. Last I heard about it. Tom From owner-freebsd-hackers Wed Jul 30 08:48:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10476 for hackers-outgoing; Wed, 30 Jul 1997 08:48:55 -0700 (PDT) Received: from lucky.innet.com (root@lucky.innet.com [204.149.226.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10462 for ; Wed, 30 Jul 1997 08:48:43 -0700 (PDT) From: club@intol.com Received: from 204.149.245.110 (www.intol.com [204.149.245.110]) by lucky.innet.com (8.8.5/8.8.5) with SMTP id LAA19824 for ; Wed, 30 Jul 1997 11:50:08 -0400 Date: Wed, 30 Jul 1997 11:50:08 -0400 Message-Id: <199707301550.LAA19824@lucky.innet.com> To: hackers@freebsd.org Subject: INTEL Cuts prices - Updated Price Sheet! X-Mailer: Allaire Cold Fusion 2.0 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Wholesale parts to the Public TRUE WHOLESALE - BRAND NAMES 1-800-551-1449 TOLL FREE 813-796-0806 Mon - Fri 9am-7pm & Sat 10am - 4pm EST <<<<<< NO CREDIT CARD SURCHARGES >>>>>>> << Send mail to price@intol.com for instant current pricing! >> << More parts listed at http://www.intol.com >> ==================================== NEW MEMORY LIFETIME WARRANTY!! 72 Pin MEMORY Today's Price 4MB 1X32-60 8 Chip Non-Parity $21 4MB 1X36-60 True Parity $26 4MB 1X32-60 EDO 8 Chip $21 8MB 2X32-60 16 Chip Non-Parity $35 8MB 2X36-60 True Parity $48 8MB 2X32-60 EDO 16 Chip $34 16MB 4X32-60 8 Chip Non-Parity $54 16MB 4X36-60 True Parity $69 16MB 4X32-60 EDO 8 Chip $57 32MB 8X32-60 16 Chip Non-Parity $108 32MB 8X36-60 True Parity $129 32MB 8X32-60 EDO 16 Chip $109 64MB 16X32-60 Non-Parity $353 64MB 16X36-60 Parity $364 64MB 16X32-60 EDO $325 168 Pin MEMORY Today's Price 8MB DIMM (MAC) $40 16MB DIMM (MAC) $70 32MB DIMM (MAC) $120 32MB SDRAM Unbuffered 10ns (PC) $149 64MB SDRAM Unbuffered 10ns (PC) $364 30 Pin MEMORY Today's Price 1MB 1X3 $12 4MB 4X3 $22 4MB 4X9 $26 Cache Modules Today's Price 256K Pipe Line Burst Cache $28 512K Pipe Line Burst Cache $38 Lifetime Warranty! Prices do not apply to any prior sales. ========================================== Motherboards SHUTTLE HOT-557 Only $99 MMX READY! 75Mhz - 200Mhz http://www.intol.com/shuttle.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RHINO 12 512K Cache Only $129 75Mhz-200+ & AMD K6 Support http://www.intol.com/p_r12.htm Motherboard, CPU & Fan M/B & CPU INTEL SHUTTLE HOT 557 P5-200MMX PCI (Shuttle VX Board) $392 P5-166MMX PCI (Shuttle VX Board) $279 P5-200 PCI (Shuttle VX Board) $345 P5-166 PCI (Shuttle VX Board) $294 P5-133 PCI (Shuttle VX Board) $225 P5-120 PCI (Shuttle VX Board) $219 RHINO 12 P5-200MMX PCI (Rhino 12 512K PB Cache) $421 P5-166MMX PCI (Rhino 12 512K PB Cache) $309 P5-200 PCI (Rhino 12 512K PB Cache) $375 P5-166 PCI (Rhino 12 512K PB Cache) $324 P5-133 PCI (Rhino 12 512K PB Cache) $255 P5-120 PCI (Rhino 12 512K PB Cache) $248 RHINO15 P5-233MMX PCI (Rhino 15 512K PB Cache) $610 P5-200MMX PCI (Rhino 15 512K PB Cache) $441 P5-166MMX PCI (Rhino 15 512K PB Cache) $329 P5-200 PCI (Rhino 15 512K PB Cache) $395 P5-166 PCI (Rhino 15 512K PB Cache) $344 P5-133 PCI (Rhino 15 512K PB Cache) $275 P5-120 PCI (Rhino 15 512K PB Cache) $268 CYRIX SHUTTLE HOT-557 6X86-166+ (Shuttle VX Board) $191 RHINO 12 6X86-200+ (Rhino 12 512K PB Cache) $227 6X86-166+ (Rhino 12 512K PB Cache) $221 RHINO15 6X86-200+ (Rhino 15 512K PB Cache) $247 6X86-166+ (Rhino 15 512K PB Cache) $241 AMD SHUTTLE HOT-557 AMD K5-75 (Shuttle VX Board) $152 AMD K5-90 (Shuttle VX Board) $155 AMD K5-100 (Shuttle VX Board) $173 AMD K5-133 (Shuttle VX Board) $192 AMD K5-166 (Shuttle VX Board) $222 RHINO 12 AMD K5-75 (Rhino 12 512K PB Cache) $182 AMD K5-90 (Rhino 12 512K PB Cache) $185 AMD K5-100 (Rhino 12 512K PB Cache) $203 AMD K5-133 (Rhino 12 512K PB Cache) $222 AMD K5-166 (Rhino 12 512K PB Cache) $251 AMD K6-166 (Rhino 12 512K PB Cache) $294 RHINO 15 AMD K5-75 (Rhino 15 512K PB Cache) $202 AMD K5-90 (Rhino 15 512K PB Cache) $205 AMD K5-100 (Rhino 15 512K PB Cache) $223 AMD K5-133 (Rhino 15 512K PB Cache) $242 AMD K5-166 (Rhino 15 512K PB Cache) $271 AMD K6-166 (Rhino 15 512K PB Cache) $314 ========================================= CPU's Today's Price AMD K5-75 AMD $43 K5-90 AMD $46 K5-100 AMD $64 K5-133 AMD $83 K5-166 AMD $113 K6-166 AMD $151 K6-200 AMD $218 K6-233 AMD $326 INTEL P5 120 $110 P5 133 $116 P5 166 $185 P5 200 $236 INTEL PRO P6 200 PRO w/ 256K $532 (NEW) KLAMATH 233Mhz $623 (NEW) KLAMATH 266Mhz $798 INTEL MMX P5 233 MMX $452 P5 200 MMX $283 P5 166 MMX $170 Cyrix Cyrix / IBM P166+ $77 Cyrix / IBM P200+ $83 CPU Fans CPU FAN 486 $8 CPU FAN 586 $10 CPU FAN Cyrix $15 All CPU's are new! 1 year Manufacturers warranty! ========================================== Hard Drives Today's Price MAXTOR 2GB - 12ms $180 4GB - 12ms $281 5GB - 10ms $338 Western Digital 1.2GB - 10ms $162 1.6GB - 11ms $173 2.1GB - 11ms $189 2.5GB - 11ms $204 3.1GB - 11ms $221 4.0GB - 11ms $275 3 Year Warranty! All drives are OEM. ========================================== Part # CD Roms Today's Price CD-IDE8x 8x Int IDE $79 CD-IDE12x 12x Int IDE $89 CD-IDE16x 16x Int IDE $109 CD-IDE24x 24x Int IDE $129 Part # CD Rom Kits Today's Price CD-KIT8x 8x, PnP Snd Crd, Spks $118 CDKIT12x 12x, PnP Snd Crd, Spkrs $129 CDKIT16x 16x, PnP Snd Crd, Spkrs $148 CDKIT24x 24x, PnP Snd Crd, Spkrs $168 Each Kit comes with 5w Speakers and our PnP ESS Sound Card Add $13 to upgrade to our 24W powered speakers. Part # Sound Cards Today's Price SND-ESS16 Full Dup 3D PnP 16Bit $29 SND-BLST16 Creative Labs 16 Pnp $59 SND-BLST32 Creative 32 PnP $93 SND-BLST64 Creative 64AWE PnP $185 SND-BLST64-v Creative 64AWE Value $99 Part # Fun Multi Media Stuff Today's Price VC-PCI-TVPCI STB TV Tuner $119 FM-ZOLTRIX Zoltrix FM Tuner Card $39 Part # Speakers Today's Price SPRK-5W 5w Stereo Speakers $10 SPRK-24W 24w Stereo Sprks w/ Power $19 SPRK-72W 72w Stereo Sprks w/ Power $29 ========================================== Modems 33.6 Internal MODEM336 Zoltrix $74 Full Duplex, Voice, Data, Fax USR 33.6 Fax/Modem UPGRADABLE to 56K $149 ========================================== I/O Cards IO-SCSI-PCI PCI NCR SCSI / SCSI II $58 ========================================== Part # Floppy Drives Today's Price FLOPPY144 Mitsumi 1.44 $22 ========================================== Part # Video Cards Today's Price VC-PCI-TR1MB Trident 9680 PCI 1MB W/MPEG $29 VC-PCI-TRI2MB Trident 9680 PCI 2MB W/MPEG $43 VC-PCI-STB-4MB Velocity 3D 4MB EDO VRAM w/o game $179 VC-PCI-STB-4MB Velocity 3D 4MB EDO VRAM w/ game $185 VC-UPG-STB-4MB Velocity 3D 4MB UPGRADE $119 VC-PCI-STB-8MB Velocity 3D 8MB EDO VRAM $294 VC-PCI-ST3D-2MB Stealth 64 2MB W/MPEG $129 ========================================== Part # Cases Today's Price CASE-MINI Mini Tower 230W Pro Case $49 CASE-MID Mid Tower 230W Pro Case $55 CASE-FULL Full Tower 230W Pro Case $99 CASE-DSK Desk Top 230w Pro Case $47 ========================================== INTOL Computers 813-796-0806 Local 1-800-551-1449 TOLL FREE! 22065 US Highway 19 North, Clearwater, FL 34625 Check our current pricing at http://www.intol.com NO CREDIT CARD SURCHARGES NO QUANTITY REQUIRED TO BUY AT THESE PRICES! We accept Visa, Master card, Discover, & American Express. 10 Day unconditional money back guarantee applies on all items. All returns must be in original packing material with manuals and registration cards included. Money back guarantee does not cover price protection. A restocking fee may be charged on assembled systems only. Shipping fees are non-refundable. Not responsible for typographical errors. Prices are subject to change without notice. From owner-freebsd-hackers Wed Jul 30 08:52:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10682 for hackers-outgoing; Wed, 30 Jul 1997 08:52:01 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10669 for ; Wed, 30 Jul 1997 08:51:50 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id KAA18490; Wed, 30 Jul 1997 10:55:35 -0500 (CDT) Message-Id: <199707301555.KAA18490@iworks.InterWorks.org> Date: Wed, 30 Jul 1997 10:55:35 -0500 (CDT) From: "Daniel M. Eischen" To: A.J.Smith@nortel.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Cross compiling for FreeBSD 3.0 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have several linux boxes (2.0.30 kernel) and I want to install GCC as a > cross-compiler so I can produce FreeBSD binaries. Can anyone help me out > and give me some info as to home I might do this? > > I have limited access to a FreeBSD 3.0 sytem, so if I need libraries, > header files and includes I could get them that way, but it is a real > hassle so I'm hoping I don't need too much. I've built FreeBSD binaries on a Sparc-Sun-Solaris system. In lieu of FreeBSD emulation in Linux, your best bet will be to build ELF binaries for FreeBSD (3.0-current will support native ELF binaries). The binutils 2.7 (and greater) has support for FreeBSD ELF builtin - you just need a couple of minor patches to get it to work properly. If you wanted to make a.out binaries you'd have to port FreeBSDs ld to Linux. I tried doing this for Solaris, but gave up because I didn't understand it well enough (and ELF was much easier :). Start with getting the Elfkit from: ftp://ftp.polstra.com/pub/FreeBSD/elfkit-1.2.1.tar.gz ftp://ftp.polstra.com/pub/FreeBSD/elfkit-1.2.1.patch1 You'll need elfkit-1.2.1.patch1 and binutils-2.6.0.12.patch (the latter patch coming from the elfkit tarball). Apply these patches to binutils-2.7 (or 2.8). Read the READMEs in John Polstras elfkit if you are unsure how to build a cross compiler - you don't need the elfkit for anything other than the READMEs and patch. Pick a directory in which to want your cross-compilation system to be installed (/usr/local/freebsdelf?) and build the patched binutils with this prefix. Get the include files from a 3.0 FreeBSd system and install them in /i386-unknown-freebsdelf/include. Grab the necessary libraries from a 3.0 FreeBSD system and place them in /i386-unknown-freebsdelf/lib. (I am assuming you're configuring binutils/gcc for i386-unknown-freebsdelf). Configure gcc-2.7.2 for i386-unknown-freebsdelf and your chosen prefix. Build and install gcc. You're now ready to start cross compiling. I know I left out some of the details - I have more precise notes at home if you need them. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Wed Jul 30 08:55:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10915 for hackers-outgoing; Wed, 30 Jul 1997 08:55: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 IAA10906 for ; Wed, 30 Jul 1997 08:55:54 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtb66-0000MC-00; Wed, 30 Jul 1997 08:55:34 -0700 Date: Wed, 30 Jul 1997 08:55:33 -0700 (PDT) From: Tom Samplonius To: Charles Henrich cc: craig@gnofn.org, freebsd-hackers@freebsd.org Subject: Re: Pentium II? In-Reply-To: <199707301500.LAA01362@crh.cl.msu.edu> 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, 30 Jul 1997, Charles Henrich wrote: > In lists.freebsd.hackers you write: > > >The real issue is that the PII is untried, whereas FreeBSD systems > >on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous > >ftp users) have been ticking along reliably for quite some time > >now. > > I've been running a P-II/266 for months, overclocked at 300 even. It works > flawlessly. It blows the hell out of my PPro/233. Hands Down, left right, > forwards, backwards, and inside out. And I dont give a rip if its Slot 1, > Slot 3, socket 8, or a bunch of wires glued to a CPU. I buy motherboards and > processors together, and I dont give a rip what the connection is. I require > performance for my apps, and there's nothing on the planet that will > (currently) touch a P-II/300. Yep, that's what I've been trying to say. > -Crh > -- > > Charles Henrich Michigan State University henrich@msu.edu > > http://pilot.msu.edu/~henrich > > Tom From owner-freebsd-hackers Wed Jul 30 09:01:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11211 for hackers-outgoing; Wed, 30 Jul 1997 09:01:40 -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 JAA11205 for ; Wed, 30 Jul 1997 09:01:36 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtbBp-0000MZ-00; Wed, 30 Jul 1997 09:01:29 -0700 Date: Wed, 30 Jul 1997 09:01:27 -0700 (PDT) From: Tom Samplonius To: FreeBSD Mailing List cc: hackers@freebsd.org Subject: Re: Pentium II? 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, 30 Jul 1997, FreeBSD Mailing List wrote: > With the same cash is important. P2 boards will be more expensive, along > with the chips. Really, I find that PII/266 chips are cheaper than the PPro/200 w/512k cache? > > > (socket 8?) is doomed too, as Intel will not be developing it further (a > > > 233mhz version would be nice). The Pentium MMX is going to max at 233, > > > before being put out to pasture. So, every option is "doomed"... > > ZIF architecture is being promoted heavily by AMD, Cyrix, etc. The new > Socket 7 motherboards we carry go up to 363MHz (66 x 5.5) and above > (83MHZ x 4.5). I expect ZIF-8 solutions to be available soon from > competitive vendors. AMD, Cyrix. Ugh... ... > Our custmoers who know almost all go with Pro. Know what? That the PPro is dead, and likely be discontinued in less than a year? > Check out http://www.atipa.com/pentium2.shtml for additional reference. > > Kevin > > Tom From owner-freebsd-hackers Wed Jul 30 09:08:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11661 for hackers-outgoing; Wed, 30 Jul 1997 09:08:31 -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 JAA11646 for ; Wed, 30 Jul 1997 09:08:26 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wtbIO-0000Ml-00; Wed, 30 Jul 1997 09:08:16 -0700 Date: Wed, 30 Jul 1997 09:08:15 -0700 (PDT) From: Tom Samplonius To: Craig Johnston cc: FreeBSD Mailing List , Rod Ebrahimi , hackers@freebsd.org Subject: Re: Pentium II? 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, 30 Jul 1997, Craig Johnston wrote: > On Tue, 29 Jul 1997, Tom Samplonius wrote: > > > > On Tue, 29 Jul 1997, Craig Johnston wrote: > > > > > > > The PII runs 16-bit software better and adds MMX extensions, but for a > > > > > network server the PPro will still be faster. > > > > > > > > The PII/266 will be faster than a PPro/200. > > > > > > Not buying into Intel's slot 1 ploy is a good enough reason not to run > > > PII's. Slot 1 is not going to be around very long and I wouldn't count > > > on not running into bugs in the relatively untested slot 1 chipset. > > > > If you use that arguement, you shouldn't by anything then! The PPro > > Um, no. There's this idea of relative quantities, you see? Slot 1 > is going to be short-lived _compared_ to other solutions. How long > has socket 7 been ticking along now? It's well known that slot 2 is > coming right on the heels of slot 1. The PPro series is already dead: no further development. The Pentium series will end with the 233mhz MMX chip. Only the here-and-now matters. Sure the Pentium and Pro have been around longer, but Intel is already winding them down! As short lived as slot 1 may be (in total lifespan), it will be around long after the Pro. > Why bother with the Intel "chipset of the week" game? Slot 1 systems > don't offer anything you can't do better with the same cash with PPro and > socket 7 systems. The only folks likely to benefit from slot 1 at > all are likely to be Intel -- they'll make a bundle off upgrade-happy > power-lusers who've been exposed to one too many Ziff-Davis magazines. PII/266 chips are cheaper than than Pro/200 w/512k cache, and faster. Besides the chipset is the same! > > (socket 8?) is doomed too, as Intel will not be developing it further (a > > 233mhz version would be nice). The Pentium MMX is going to max at 233, > > before being put out to pasture. So, every option is "doomed"... > > The real issue is that the PII is untried, whereas FreeBSD systems > on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous > ftp users) have been ticking along reliably for quite some time > now. Hardly untried, just souped up Pentium technology. ... > So exactly whose critical FreeBSD systems are you building with > PIIs right now, Tom? I suggest you try one first. > -Craig > > > > From owner-freebsd-hackers Wed Jul 30 09:23:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12498 for hackers-outgoing; Wed, 30 Jul 1997 09:23:26 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12488 for ; Wed, 30 Jul 1997 09:23:21 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id MAA07597; Wed, 30 Jul 1997 12:25:21 -0400 (EDT) Date: Wed, 30 Jul 1997 12:25:21 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: sthaug@nethelp.no cc: hackers@FreeBSD.ORG Subject: Re: de0 under 2.2-STABLE In-Reply-To: <3263.870199295@verdi.nethelp.no> 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 Thanks to all for the help... I'm currently using the "alternate" driver from 3am-software, and it seems to be working great so far. I don't know how it does with 100M, because we don't yet use it anywhere... It has alleviated the "don't unplug it or you're hosed" problem, so I'm happy. Is there any reason this isn't merged into the -stable tree? Is there any testing I can do before I take this thing "live"? Thanks again, Charles On Tue, 29 Jul 1997 sthaug@nethelp.no wrote: > > Someone had suggested getting the de0 package from 3am-software.com; can > > anyone give me a "yay" or "nay" on that? > > Definitely get this package. Matt Thomas is the original developer of > the de driver, and the version at > > http://www.3am-software.com/de-970703.tar.gz > > is much newer than the one in 2.2.2. For me it works much better, but > note that I have no experience with the particular card that you're > having problems with. > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > From owner-freebsd-hackers Wed Jul 30 09:24:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12569 for hackers-outgoing; Wed, 30 Jul 1997 09:24:07 -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 JAA12551 for ; Wed, 30 Jul 1997 09:24:03 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 10557 invoked by uid 1001); 30 Jul 1997 16:23:55 +0000 (GMT) To: henrich@crh.cl.msu.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Pentium II? In-Reply-To: Your message of "Wed, 30 Jul 1997 11:00:53 -0400 (EDT)" References: <199707301500.LAA01362@crh.cl.msu.edu> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 30 Jul 1997 18:23:55 +0200 Message-ID: <10555.870279835@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I require > performance for my apps, and there's nothing on the planet that will > (currently) touch a P-II/300. Um, if you don't require Intel compatibility, I believe an Alpha could easily beat it :-) Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Wed Jul 30 09:38:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA13736 for hackers-outgoing; Wed, 30 Jul 1997 09:38:03 -0700 (PDT) Received: from internet.milkyway.com (milkyway.com [198.53.167.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA13720 for ; Wed, 30 Jul 1997 09:37:58 -0700 (PDT) Received: id MAA02911; Wed, 30 Jul 1997 12:36:28 -0400 Received: by gateway id MAA23981 for ; Wed, 30 Jul 1997 12:32:16 -0400 Received: by gateway id AA03229; Wed, 30 Jul 97 12:36:14 EDT Message-Id: <19970730123613.03490@milkyway.com> Date: Wed, 30 Jul 1997 12:36:13 -0400 From: Brian Campbell To: hackers@FreeBSD.ORG Subject: Re: Pentium II? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: ; from Tom Samplonius on Wed, Jul 30, 1997 at 09:08:15AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Jul 30, 1997 at 09:08:15AM -0700, Tom Samplonius wrote: > The PPro series is already dead: no further development. The Pentium > series will end with the 233mhz MMX chip. Only the here-and-now matters. > Sure the Pentium and Pro have been around longer, but Intel is already > winding them down! As short lived as slot 1 may be (in total lifespan), > it will be around long after the Pro. Actually the 266Mhz P5/MMX has already been announced for early next year. www.zdnet.com/zdnn/content/pcwo/0723/pcwo0005.html From owner-freebsd-hackers Wed Jul 30 09:53:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14908 for hackers-outgoing; Wed, 30 Jul 1997 09:53:02 -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 JAA14895 for ; Wed, 30 Jul 1997 09:52:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA05201; Wed, 30 Jul 1997 09:50:36 -0700 From: Terry Lambert Message-Id: <199707301650.JAA05201@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: dg@root.com Date: Wed, 30 Jul 1997 09:50:36 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300146.SAA11272@implode.root.com> from "David Greenman" at Jul 29, 97 06:46: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 > >Probably there needs to be _copyin/_copyout for the internal usage, > >and a "safe" copyin/copyout for usage which isn't safed against > >reentrancy. > > There is no problem with using copyout() in the kernel to copy data out to > a user process, assuming that the currently running process is the intended > target of the copy. That is the sole purpose of the function. copyout() > correctly handles all issues of COW/ZF/page faults. > uiomove() is escentially a wrapper for copyin/copyout that has an > optimization for the case of kernel-to-kernel copies (in which case it > uses bcopy instead). The magic I was thinking of was related to reentrancy... I could see how you could also make the statement Mike made, and have it refer to the copy[in|out] -> bcopy conversion (ie: you can't call the new function from the kernel if your code will attempt a copy[in|out] instead of a bcopy). Shows my bias as a kernel preemption/multithreaing advocate, I suppose. ;-). 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 Jul 30 09:53:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14985 for hackers-outgoing; Wed, 30 Jul 1997 09:53:32 -0700 (PDT) Received: from relay3.smtp.psi.net (relay3.smtp.psi.net [38.8.210.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14974 for ; Wed, 30 Jul 1997 09:53:26 -0700 (PDT) Received: from netmail.canoga.com by relay3.smtp.psi.net (8.8.3/SMI-5.4-PSI) id MAA03092; Wed, 30 Jul 1997 12:52:58 -0400 (EDT) Message-Id: <199707301652.MAA03092@relay3.smtp.psi.net> Received: by netmail.canoga.com with Internet Mail Service (5.0.1458.49) id <380R86JQ>; Wed, 30 Jul 1997 09:53:44 -0700 From: Joo Hong To: hackers@freebsd.org Subject: Internal Design specification. Date: Wed, 30 Jul 1997 09:55:00 -0700 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: multipart/mixed; boundary="---- =_NextPart_000_01BC9CCE.77A30660" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_000_01BC9CCE.77A30660 Content-Type: text/plain Dear Sir: Where can I find or get the design documentation or specification for the functions or routines implemented inside the FreeBSD kernel. I am trying to understand some of the source code of the kernel. (The 4.4 FreeBSD internal design book does not cover deep enough the information I am looking for). Thank you very much for your help. Joo Hong jhong@canoga.com ------ =_NextPart_000_01BC9CCE.77A30660 Content-Type: application/ms-tnef Content-Transfer-Encoding: base64 eJ8+Ii0QAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQmAAQAhAAAANEU0QThEOUQzQzA0RDExMUFGNTAwMEEwQzk1NUIx MDcAFQcBIIADAA4AAADNBwcAHgAJADUAKgADAGQBAQWAAwAOAAAAzQcHAB4ACQA3AAAAAwA8AQEE gAEAHwAAAEludGVybmFsIERlc2lnbiBzcGVjaWZpY2F0aW9uLgBmCwENgAQAAgAAAAIAAgABA5AG ABgFAAAeAAAAHgAxQAEAAAAJAAAAN0U1MDNDNjUAAAAAAwAaQAAAAAAeADBAAQAAAAkAAAA3RTUw M0M2NQAAAAADABlAAAAAAEAAOQAAChNRCZ28AQMAJgAAAAAACwAGDAAAAAACAQkQAQAAAM8BAADL AQAAvAIAAExaRnV3RW3VAwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3/wqAAqQD5AcTAoAP8wBQBFY/ CFUHshElDlEDAQIAY2jhCsBzZXQyBgAGwwKAtxEzCO8J9zsVvw4wNREiHQxgYwBQCwkBZDM2MCsD MQvFYwEwIBrDRGXhCsFTaXI6CqIKgBrDiRu5V2gEkGUgYwORSEkgZguAZCAFsWdpFCAgdB0gIAEA AJBnYQOgZG9jdQeAAjBhzHRpAiAeEnNwBZAGkD8N4B/EAhAK1Bv1HpJmdbxuYx/SBCAFsQNgdR/Q 7m4HkQdwC1BlH4IJgCOwFwCBAQAeg0YJ0UJTREQgawSRZWwuHaFhUm0ha3J5C4BnHoBvtiAicASB cwGQHfFzA3C5HVBvZh6DKIAIcGMdUScEcSjGJbYoVB6hNC7+NBxaJTYLgA6wBKAHQB7GmQbgb2sf MQeRbm8FQI0FoHYSgQEAZXAgCfD5CGBnaB6DG7kLgCExAMC/H9MmMxVQLdAnYiExKSYQVysAAHAt 4HkIYCAusXn8IG0YcC+QITIy8QXAHSBYbHAuG78aw0otwCBKSAIgZzS5amg2YUChHXFvZ2EuBaBt NLQCfTiwAAMA/T/kBAAAHgBwAAEAAAAfAAAASW50ZXJuYWwgRGVzaWduIHNwZWNpZmljYXRpb24u AAACAXEAAQAAABYAAAABvJ0JISidjUpPBDwR0a9QAKDJVbEHAAACAUcAAQAAADUAAABjPVVTO2E9 IDtwPUNhbm9nYSBQZXJraW5zO2w9TkVUTUFJTC05NzA3MzAxNjUzMzkwNTQ1AAAAAAIB+T8BAAAA YgAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAAAAYAAAAvTz1DQU5PR0EgUEVSS0lOUy9PVT1DQU5P R0FfQ0hBVFNXT1JUSC9DTj1DQzpNQUlMIEFERFJFU1MvQ049N0U1MDNDNjUAAAAeAPg/AQAAAAkA AABKb28gSG9uZwAAAAAeADhAAQAAAAkAAAA3RTUwM0M2NQAAAAACAfs/AQAAAGIAAAAAAAAA3KdA yMBCEBq0uQgAKy/hggEAAAAGAAAAL089Q0FOT0dBIFBFUktJTlMvT1U9Q0FOT0dBX0NIQVRTV09S VEgvQ049Q0M6TUFJTCBBRERSRVNTL0NOPTdFNTAzQzY1AAAAHgD6PwEAAAAJAAAASm9vIEhvbmcA AAAAHgA5QAEAAAAJAAAAN0U1MDNDNjUAAAAAQAAHMDZnKCEJnbwBQAAIMBx9oyIJnbwBHgA9AAEA AAABAAAAAAAAAB4AHQ4BAAAAHwAAAEludGVybmFsIERlc2lnbiBzcGVjaWZpY2F0aW9uLgAAAwA2 AAAAAAALACkAAAAAAAsAIwAAAAAAAwAGEJuwsdUDAAcQLgEAAAMAEBAAAAAAAwAREAAAAAAeAAgQ AQAAAGUAAABERUFSU0lSOldIRVJFQ0FOSUZJTkRPUkdFVFRIRURFU0lHTkRPQ1VNRU5UQVRJT05P UlNQRUNJRklDQVRJT05GT1JUSEVGVU5DVElPTlNPUlJPVVRJTkVTSU1QTEVNRU5URURJAAAAAEA3 ------ =_NextPart_000_01BC9CCE.77A30660-- From owner-freebsd-hackers Wed Jul 30 10:12:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16533 for hackers-outgoing; Wed, 30 Jul 1997 10:12:30 -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 KAA16517; Wed, 30 Jul 1997 10:12:20 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05257; Wed, 30 Jul 1997 10:10:27 -0700 From: Terry Lambert Message-Id: <199707301710.KAA05257@phaeton.artisoft.com> Subject: Re: SMBIOS/DMI etc To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 10:10:27 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, se@FreeBSD.ORG, mo@uu.net, hackers@FreeBSD.ORG In-Reply-To: <199707300129.KAA16101@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 30, 97 10:59:26 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 > > If I had to guess, it's probably because BIOS calls are Intel-centric. > > Fair enough. How do other platforms (PReP, Alpha, etc) handle PCI > autoconfig? Does the BIOS on those platforms provide the same set > of management primitives? There is not necessarily ROM code for doing the autoconfiguration; some of the Alpha boxes actually have an x86 emulation in software... they use it for video card ROMs, and booting from disk controllers, and so on. For those that have no ROM whatsoever, and no x86 "Poor man's JAVA" VM's, the boot devices are default configed, and the OS is expected to do much of what Stefan's code does, using code much like his. 8-(. > I would have assumed so, from my reading of PCI-spec-derived documents. > (I don't have the "real thing", obviously) Why not? They are cheap... all specs go down in price to 10% of their former cost days after I buy them. It's a law of nature. 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 Jul 30 10:16:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16815 for hackers-outgoing; Wed, 30 Jul 1997 10:16:13 -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 KAA16756 for ; Wed, 30 Jul 1997 10:15:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05270; Wed, 30 Jul 1997 10:13:39 -0700 From: Terry Lambert Message-Id: <199707301713.KAA05270@phaeton.artisoft.com> Subject: Re: Sound Blaster 16 PnP To: dmaddox@scsn.net Date: Wed, 30 Jul 1997 10:13:39 -0700 (MST) Cc: peter@grendel.IAEhv.nl, hackers@FreeBSD.ORG In-Reply-To: <19970729213045.26986@scsn.net> from "Donald J. Maddox" at Jul 29, 97 09:30:45 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 was wondering, am I the only person who just looked under Windows > > 95 (tm) which resources the PnP Soundblaster 16 used and configured > > his kernel likewise? With just an PnP SB16 and a non-PnP Teles ISDN > > card, this works fine. > > No, you're not the only one, but this can work *only* if you have > a PnP BIOS that puts everything where it should be at boottime. Not > everyone is so lucky. I have to echo this. Windows 95 has PnP code for dealing with such machines using OS software. The monolithic name for it it "card services". Note that on non-PnP BIOS machines, PnP cards are not necessarily initially disabled... 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 Jul 30 10:25:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17810 for hackers-outgoing; Wed, 30 Jul 1997 10:25:48 -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 KAA17790 for ; Wed, 30 Jul 1997 10:25:39 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05290; Wed, 30 Jul 1997 10:23:05 -0700 From: Terry Lambert Message-Id: <199707301723.KAA05290@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: dg@root.com Date: Wed, 30 Jul 1997 10:23:04 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300310.UAA12221@implode.root.com> from "David Greenman" at Jul 29, 97 08:10:28 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 kernel function(s) use copyin/copyout, they cannot access these > >buffers, and thus the emulation cannot be performed. > > I still don't understand. copyin/out is only for copying between the kernel > and user memory. If this is what you're doing and you don't need the extra > features of uiomove (which is designed to do piecemeal copies by keeping track > of offsets/lengths in a struct uio), then copyin/out is the function to use. > If on the other hand you're copying from kernel<->kernel, then you can just > use bcopy. I'm afraid that I started reading this thread rather late into it > and don't have the original context...so what are we talking about? :-) bsd_syscall_X() { ... copyin(...); /* copy in arguments*/ ... /* do syscall stuff*/ copyout(...); /* copy out results*/ } /* * XXX BROKEN! BSD SYSCALL CALLS COPYIN/COPYOUT, AND CAN NOT USE * XXX DATA FROM KERNEL SPACE INSTEAD OF USER SPACE! */ linux_syscall_X() { ... copyin(...); /* copy in arguments*/ ... /* massage Linux arguments into BSD format...*/ /* call BSD call to implement Linux call...*/ bsd_syscall_X(); ... /* massage BSD returns into Linux format...*/ copyout(...); /* copy out results*/ } I didn't get this part from his orginal posting either, since my interpretation of his original posting assumed that he was worried about kernel preeemption for RT and threading and SMP (like I was) instead of being worried about calling functions from within the kernel *from other functions within the kernel*. 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 Jul 30 10:28:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA18099 for hackers-outgoing; Wed, 30 Jul 1997 10:28:44 -0700 (PDT) Received: from nic.aic.net (NIC.AIC.NET [195.250.64.111]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA18086 for ; Wed, 30 Jul 1997 10:28:34 -0700 (PDT) Received: from nic.aic.net (NIC.AIC.NET [195.250.64.111]) by nic.aic.net (8.8.5/8.8.5) with SMTP id VAA00518 for ; Wed, 30 Jul 1997 21:28:28 +0400 (MSD) Message-ID: <33DF79BC.41C67EA6@arminco.com> Date: Wed, 30 Jul 1997 17:28:28 +0000 From: Samvel Stepanian Organization: ARMINCO Ltd X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: FreeBSD hanging because of ethernet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear hackers, I am experiencing repeated hangings of FreeBSD-2.2.2 box and I suppose that these hangings are related with ethernet. Before hanging I have the following dump on console from arpwatch: Jul 30 21:09:55 nic arpwatch: 0:c0:5:1:7:9c sent packet not ETHERTYPE_IP (0x811) Jul 30 21:09:55 nic arpwatch: 0:c0:5:1:7:9c sent bad hardware format 0xff Jul 30 21:09:55 nic arpwatch: 0:c0:5:1:7:9c sent bad addr len (hard 6, prot 19) Jul 30 21:09:55 nic arpwatch: 0:c0:5:1:7:9c sent packet not ETHERTYPE_IP (0x811) Jul 30 21:10:43 nic arpwatch: 0:c0:5:1:7:9c sent bad hardware format 0xff Jul 30 21:10:43 nic arpwatch: 0:c0:5:1:7:9c sent bad addr len (hard 255, prot 255) Jul 30 21:11:13 nic arpwatch: 0:c0:5:1:7:9c sent wrong arp op 21 Jul 30 21:11:13 nic arpwatch: 0:c0:5:1:7:9c sent bad addr len (hard 70, prot 4) Jul 30 21:11:44 nic arpwatch: 0:c0:5:1:7:9c sent bad hardware format 0xff then system immediately freezes. 0:c0:5:1:7:9c is our Livingston Enterprises PM-2e terminal server which is a default gateway in our network. our LAN is 10-base-2 based. I tried to change the card in BSD box - it didn't help. We have another FreeBSD box (which is 2.1.5 actually) on the same net and it also hangs almost simultaneously with mine when these Ethernet problems are starting. Please advise what is the problem? A buggy ethernet card in our LAN? Why FreeBSD should hang because of Ethernet problems? What are that "bad hardware format" ARP problems? Please help! Regards, Sam From owner-freebsd-hackers Wed Jul 30 10:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA18239 for hackers-outgoing; Wed, 30 Jul 1997 10:30: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 KAA18223 for ; Wed, 30 Jul 1997 10:30:14 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05314; Wed, 30 Jul 1997 10:27:15 -0700 From: Terry Lambert Message-Id: <199707301727.KAA05314@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 10:27:15 -0700 (MST) Cc: vinay@agni.nuko.com, dg@root.com, terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707300311.MAA17635@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 30, 97 12:41:26 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 > Vinay Bannai stands accused of saying: > > > > So in a situation where I pin the user pages down (for DMA), it is okay to > > use copyin()/copyout(). > > You don't have to pin them down for copyin/copyout, but it will work > fine, yes. Note: you can get a bigger win, depending on how you pin it. If you pin it in the process of mmap()ing the device from user space, then you create a bufer in KVM that you export to user space; this is what the SVGA stuff does. Because the memory exists in both kernel and user space, you can use bcopy() to the kernel space address. This saves the creation and deletion (potentially) of mapping the target address of the user process into and out of the kernel address space. If you only allow one user space process at a time, you can further cache the translation factor in the device instance data, and save the lookup for the user->kernel address conversion when you are in the kernel processing a user address request. 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 Jul 30 10:32:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA18499 for hackers-outgoing; Wed, 30 Jul 1997 10:32:38 -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 KAA18484 for ; Wed, 30 Jul 1997 10:32:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05329; Wed, 30 Jul 1997 10:30:42 -0700 From: Terry Lambert Message-Id: <199707301730.KAA05329@phaeton.artisoft.com> Subject: Re: Location of copyin() and copyout().. To: sef@Kithrup.COM (Sean Eric Fagan) Date: Wed, 30 Jul 1997 10:30:42 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199707300344.UAA16264@kithrup.com> from "Sean Eric Fagan" at Jul 29, 97 08:44: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 > Now consider ibcs2_fstat(). Rather than duplicate the work of fstat > (which would really be a bad thing, because fstat may change and > ibcs2_fstat may not be updated), ibcs2_fstat goes through some > *HORRIBLE* hacks to allocate some space in user space, using the > stackgap_alloc() function. > > If fstat used uiomove(), then it could go to a kernel address. > (Admittedly, it would still have to be changed -- it would have to have a > struct uio passed in, probably. But then ibcs2_fstat could call that > common function, with less pain.) Better to have a common function that was not a system-specific system call implementation, and have the system specific system call and the ABI system call call the same function. This implies a kernel level service interface that does not currently exist. Nevertheless, this would be very useful for doing things like moving NFS servers and others into kernel threads instead of heavier user processes which call a system call and never return. 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 Jul 30 10:57:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20218 for hackers-outgoing; Wed, 30 Jul 1997 10:57:34 -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 KAA20211 for ; Wed, 30 Jul 1997 10:57:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05362; Wed, 30 Jul 1997 10:54:23 -0700 From: Terry Lambert Message-Id: <199707301754.KAA05362@phaeton.artisoft.com> Subject: Re: Sharing interrupts To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 30 Jul 1997 10:54:23 -0700 (MST) Cc: mouth@ibm.net, msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org In-Reply-To: <199707300425.NAA18299@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 30, 97 01:55:20 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 > > Why should it require an electrical engineer to make a few simple > > calculations and modifications? > > Because these aren't actually "simple". It's like asking why, if all > it takes to make a nuclear explosion is a critical mass of > fissionables, it took a horde of physicists many years to get it > right. Specifically, Neutron numbers had to be determined empirically before they could be curve-fit, without quantum theory advanced enough to provide a mathematical model (you can't make a model without data to which you are trying to tailor the output of the model). The process is described in the book "The Curve of Binding Energy", a must-read book for any high-energy or nuclear physicist. They also didn't use more advanced techniques in the initial devices to allow them to reach hypercritically sooner (ie: things like a K-Alpha reflector cavity or EMP-driven magnetic binding), which would have made a "good guess" sufficient to get a moderately efficient device. But again, without the models, these techniques couldn't be developed. Well, so much for history of science... back to your regularly scheduled argument... 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 Jul 30 11:20:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA21856 for hackers-outgoing; Wed, 30 Jul 1997 11:20:31 -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 LAA21850 for ; Wed, 30 Jul 1997 11:20:26 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA05450; Wed, 30 Jul 1997 11:17:51 -0700 From: Terry Lambert Message-Id: <199707301817.LAA05450@phaeton.artisoft.com> Subject: Re: Pentium II? To: brianc@milkyway.com (Brian Campbell) Date: Wed, 30 Jul 1997 11:17:51 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970730123613.03490@milkyway.com> from "Brian Campbell" at Jul 30, 97 12:36:13 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 > Actually the 266Mhz P5/MMX has already been announced for early next year. > www.zdnet.com/zdnn/content/pcwo/0723/pcwo0005.html Actually, these are the same people who said I could get a 486 DX/2-100, and thus convinced me to buy my 486 DX-50. ^ ^ | | NOTE NOTE My 486 DX-50 still beats the snot of of a P5 DX/2-66, and is more than fast enough (EISA bus overclocked to 50MHz) to handle a lot of stuff that early P5 machines couldn't. Nevertheless, I remain pissed that I can't get a 486 DX/2-100 and leave my bus speed up at 50MHz. 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 Jul 30 11:25:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22187 for hackers-outgoing; Wed, 30 Jul 1997 11:25:33 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22180 for ; Wed, 30 Jul 1997 11:25:31 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id LAA22115; Wed, 30 Jul 1997 11:24:58 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Wed, 30 Jul 1997 11:24:57 -0700 (PDT) From: Curt Sampson To: Tom Samplonius cc: Craig Johnston , FreeBSD Mailing List , Rod Ebrahimi , hackers@FreeBSD.ORG Subject: Re: Pentium II? 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, 30 Jul 1997, Tom Samplonius wrote: > The PPro series is already dead: no further development. The Pentium > series will end with the 233mhz MMX chip. Only the here-and-now matters. > Sure the Pentium and Pro have been around longer, but Intel is already > winding them down! As short lived as slot 1 may be (in total lifespan), > it will be around long after the Pro. So? Given that the PPro is near the end of its development, that's an even better reason to buy one now. You'll get around the same, or perhaps just slightly less, performance for considerably less money (I bought a PPro150 CPU for under US$200 a while back), and in the mean time the PII stuff will have a chance to fall in price. If cost is any concern whatsoever, and you're not running applications that crawl on a PPro200, you are just dumb to buy a PII this soon. (And if you do need the utmost performance, you're silly buying any Intel chip when you can get a 600 MHz 21164 for not much more, and get noticably better performance.) > PII/266 chips are cheaper than than Pro/200 w/512k cache, and faster. > Besides the chipset is the same! Yes, but much cheaper 256K cache PPro200s are also available. Is 512K of slow cache better than 256K of fast cache for your application? And despite the chipset being the same, you have to count in your motherboard costs and the like as well. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Wed Jul 30 11:27:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22310 for hackers-outgoing; Wed, 30 Jul 1997 11:27:23 -0700 (PDT) Received: from x22 (ppp6492.on.sympatico.ca [206.172.208.84]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22291 for ; Wed, 30 Jul 1997 11:27:13 -0700 (PDT) Received: from localhost (tim@localhost) by x22 (8.8.5/8.7.3) with SMTP id MAA00235; Wed, 30 Jul 1997 12:27:21 -0400 (EDT) Date: Wed, 30 Jul 1997 12:27:20 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: John Kelly cc: Michael Smith , freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org Subject: Re: Sharing interrupts In-Reply-To: <33e5c558.25976723@smtp-gw01.ny.us.ibm.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 Wed, 30 Jul 1997, John Kelly wrote: > Available at Radio Shack, 1N4001silicon diodes are ideal for this I've never seen a radio-shack which sells this kind of stuff. Their most low-level components seem to be speaker-wire, often-as-not. Is this a US-specific thing, or do I just not look hard enough? (Only out of curiousity. There are plenty of other places to find these things. :) -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. From owner-freebsd-hackers Wed Jul 30 11:31:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA22655 for hackers-outgoing; Wed, 30 Jul 1997 11:31:31 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA22649 for ; Wed, 30 Jul 1997 11:31:28 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19367 (5.67b/IDA-1.5 for ); Wed, 30 Jul 1997 20:30:57 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA12308; Wed, 30 Jul 1997 20:30:38 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 20:30:37 +0200 From: Stefan Esser To: Terry Lambert Cc: Michael Smith , mo@uu.net, hackers@FreeBSD.ORG Subject: Re: SMBIOS/DMI etc References: <199707290211.LAA09448@genesis.atrad.adelaide.edu.au> <199707300015.RAA03604@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707300015.RAA03604@phaeton.artisoft.com>; from Terry Lambert on Tue, Jul 29, 1997 at 05:15:14PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 29, Terry Lambert wrote: > > > I have considered adding calls to the PCI BIOS as an > > > alternate mechanism to directly reading configuration > > > space registers. But I have no intention to make the > > > PCI code depend on PCI BIOS services. > > > > This is because...? > > If I had to guess, it's probably because BIOS calls are Intel-centric. Yes, this is one of the reasons. PCI introduced the concept of the configuration space, which requires another distinct address space other than memory and (optionally) I/O port address space to exist. Configuration space can be seen as "bus controller registers" provided as part of each PCI device. In some way the config space registers belong not to the device, but to a "virtual" "bus tree" device. Due to backwards compatibility constraints in PC motherboards, the PCI BIOS has additional knowledge, that is not available from any other source. This includes the traces between the PCI bus interrupt lines and the emulated ICUs in the chip-set, for example. But the PCI BIOS puts information about the Int to IRQ routing for each device that has been located into a config space register of that device, and you don't need to call the PCI BIOS, except if you are interested in where those traces end even though *no* device is directly connected. (Well, the SMP people are interested in exactly that information, in order to deal with some (old) format of the SMP table, but that is a different story :) The PCI BIOS is known to be buggy on lots of older mother-boards. And there still are quite some 486 boards, where calling the 32bit functions may not be a good idea, even though the real mode calls work just fine. (Nobody cared for the 32bit calls at that time, it seems, since they are not used by Win3.11 :) There are quite some broken chip-sets, which violate explicit and boldly printed requirements of the PCI specs, even in the latest machines. If you want to have fun, just run "probepci" on just about any Compaq and watch it go mad ... :) I once complained about this, and some Compaq engineer replied, that their systems worked fine with their BIOS and all O/S code they release, and that it is their decision, whether the system complies at the register level or at the BIOS level with the PCI spec. Well, that's definitely not true, but I don't think there is much I can do about it, except work around their bugs. (And that broke EISA support some time ago, until I added even more work-arounds, since they broke exactly the machanism that is proposed to distinguish a PCI chip-set from some EISA device.) I'm going to add some code to deal with their latest TriFlex to -current soon, since I just got access to a Deskpro 4000 for testing ... One thing that calling the PCI BIOS may be good for is that the device scan order is not defined, and some BIOS does it from low to high, the other from high to low slot numbers. Calling the PCI BIOS from the FreeBSD probe code is the only way to have FreeBSD probe the PCI bus in the same order as the BIOS init code does, and some people with multiple SCSI cards asked for that feature. (But I'd rather want to be able to wire devices to bus slots from the user config menu as an alternative with many more uses :) Regards, STefan From owner-freebsd-hackers Wed Jul 30 11:36:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA23220 for hackers-outgoing; Wed, 30 Jul 1997 11:36:40 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA23213 for ; Wed, 30 Jul 1997 11:36:33 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19426 (5.67b/IDA-1.5 for ); Wed, 30 Jul 1997 20:36:27 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA12337; Wed, 30 Jul 1997 20:36:26 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 20:36:26 +0200 From: Stefan Esser To: Michael Smith Cc: mo@uu.net, hackers@FreeBSD.ORG Subject: Re: SMBIOS/DMI etc References: <19970728234428.16657@mi.uni-koeln.de> <199707290211.LAA09448@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707290211.LAA09448@genesis.atrad.adelaide.edu.au>; from Michael Smith on Tue, Jul 29, 1997 at 11:41:42AM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 29, Michael Smith wrote: > Stefan Esser stands accused of saying: > > > > I have considered adding calls to the PCI BIOS as an > > alternate mechanism to directly reading configuration > > space registers. But I have no intention to make the > > PCI code depend on PCI BIOS services. > > This is because...? 1) I don't like to have assembler code in the PCI driver 2) The 32bit PCI BIOS calls are known to be broken in many 486 based systems, and you can't get BIOS upgrades for them, anymore. 3) Most functions of the PCI BIOS are trivial to implement. > > But I do not have time to debug the BIOS32 functionality, > > right now, and need to know it is operational, before I > > try to use it ... > > I think I've found enough help to sort it out; I'd be more than > happy to present you with an API of your choice on a platter. Thanks. Did you consider to commit the bios32.{c,h} files to -current soon ? (Or did I just miss the commit message ?? :) If I know that the assembler part is working, I can easily implement the missing interface code myself. This is probably easier then specifying the API in text form ... Regards, STefan From owner-freebsd-hackers Wed Jul 30 11:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA23757 for hackers-outgoing; Wed, 30 Jul 1997 11:43:32 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA23713; Wed, 30 Jul 1997 11:42:48 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19518 (5.67b/IDA-1.5); Wed, 30 Jul 1997 20:42:42 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA12380; Wed, 30 Jul 1997 20:42:34 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 20:42:34 +0200 From: Stefan Esser To: Amancio Hasty Cc: Luigi Rizzo , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration References: <199707300404.GAA03229@labinfo.iet.unipi.it> <199707300701.AAA00475@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707300701.AAA00475@rah.star-gate.com>; from Amancio Hasty on Wed, Jul 30, 1997 at 12:01:13AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > PCI devices should be probed and attached last for they are they > are the most flexible to configure NO !!! PCI devices get their addresses assigned by the PCI BIOS before giving control to the primary boot loader. They can not easily be moved around, since there may be constraints that are only known to the BIOS! > and can share interrupts. Yes, that much is true. But they can't share interrupts with non-PnP devices, and the BIOS has arranged all things before the FreeBSD device probe gets a chance ... PCI devices are probed first, because they are assumed to have got assigned unique and non-conflicting addresses. Regards, STefan From owner-freebsd-hackers Wed Jul 30 11:49:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24109 for hackers-outgoing; Wed, 30 Jul 1997 11:49:33 -0700 (PDT) Received: from internet.milkyway.com (milkyway.com [198.53.167.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA24102 for ; Wed, 30 Jul 1997 11:49:26 -0700 (PDT) Received: id OAA03001; Wed, 30 Jul 1997 14:46:24 -0400 Received: by gateway id OAA25920 for ; Wed, 30 Jul 1997 14:40:22 -0400 Received: by gateway id AA07997; Wed, 30 Jul 97 14:44:20 EDT Message-Id: <19970730144420.16698@milkyway.com> Date: Wed, 30 Jul 1997 14:44:20 -0400 From: Brian Campbell To: hackers@FreeBSD.ORG Subject: Re: Pentium II? References: <19970730123613.03490@milkyway.com> <199707301817.LAA05450@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199707301817.LAA05450@phaeton.artisoft.com>; from Terry Lambert on Wed, Jul 30, 1997 at 11:17:51AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Jul 30, 1997 at 11:17:51AM -0700, Terry Lambert wrote: > > Actually the 266Mhz P5/MMX has already been announced for early next year. > > www.zdnet.com/zdnn/content/pcwo/0723/pcwo0005.html > > Actually, these are the same people who said I could get a > 486 DX/2-100, and thus convinced me to buy my 486 DX-50. Can't now, or couldn't ever? I used to have a DX4, and did manage to get it to boot at 2*50, but my graphics and scsi cards didn't like that much. I know at least one other person that claims to keep his DX4 running at 2*50. > My 486 DX-50 still beats the snot of of a P5 DX/2-66, and is > more than fast enough (EISA bus overclocked to 50MHz) to handle > a lot of stuff that early P5 machines couldn't. Hmmm ... Never heard of a P5 DX/2-66 ;-) From owner-freebsd-hackers Wed Jul 30 12:04:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA25341 for hackers-outgoing; Wed, 30 Jul 1997 12:04:24 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA25330 for ; Wed, 30 Jul 1997 12:04:19 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19725 (5.67b/IDA-1.5 for ); Wed, 30 Jul 1997 21:04:05 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id VAA12491; Wed, 30 Jul 1997 21:04:03 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 21:04:02 +0200 From: Stefan Esser To: Terry Lambert Cc: Brian Campbell , hackers@FreeBSD.ORG Subject: Re: Pentium II? References: <19970730123613.03490@milkyway.com> <199707301817.LAA05450@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707301817.LAA05450@phaeton.artisoft.com>; from Terry Lambert on Wed, Jul 30, 1997 at 11:17:51AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 30, Terry Lambert wrote: > > Actually the 266Mhz P5/MMX has already been announced for early next year. > > www.zdnet.com/zdnn/content/pcwo/0723/pcwo0005.html > > Actually, these are the same people who said I could get a > 486 DX/2-100, and thus convinced me to buy my 486 DX-50. > ^ ^ > | | > NOTE NOTE > > My 486 DX-50 still beats the snot of of a P5 DX/2-66, and is > more than fast enough (EISA bus overclocked to 50MHz) to handle > a lot of stuff that early P5 machines couldn't. > > Nevertheless, I remain pissed that I can't get a 486 DX/2-100 > and leave my bus speed up at 50MHz. The AMD 5x86-133 is designed for 4*33Mhz, but was successfully used with 3*40MHz in many systems (and slighlty faster that way). On the other hand, it can safely be over-clocked to 4*40MHz, and I'm quite sure it wouldn't mind being run at 3*50MHz :) So, if you want to give it a try ... At 3*50 it should be about as fast as a P-100 (under FreeBSD, with non-Pentium optimized binaries as created by the stock gcc). Regards, STefan PS: If you really want to overclock an AMD 5x86, try to get the ADZ version, which can be used with no heat sind or fan at 133MHz ... From owner-freebsd-hackers Wed Jul 30 12:06:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA25532 for hackers-outgoing; Wed, 30 Jul 1997 12:06:05 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA25495 for ; Wed, 30 Jul 1997 12:05:48 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id VAA27279; Wed, 30 Jul 1997 21:04:51 +0200 (CEST) Date: Wed, 30 Jul 1997 21:04:51 +0200 (CEST) Message-Id: <199707301904.VAA27279@bitbox.follo.net> From: Eivind Eklund To: freebsd-hackers@freebsd.org Subject: ISDN drivers/cards Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If anybody would like to attempt to develop drivers for the the Tele/S ISDN cards, I've got some cards I'm not using. These are European cards; they won't work on a standard US endpoint. Also, they are fairly low-level, and need a lot of logic in the driver. Contact me for further info if you're interested. (Yeah, I know of the bISDN people, but nothing seems to be happening there; besides, they have already got hardware, it seems.) Eivind. From owner-freebsd-hackers Wed Jul 30 12:25:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA26738 for hackers-outgoing; Wed, 30 Jul 1997 12:25:50 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA26715; Wed, 30 Jul 1997 12:25:37 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19896 (5.67b/IDA-1.5); Wed, 30 Jul 1997 21:25:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id VAA12572; Wed, 30 Jul 1997 21:25:27 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 21:25:26 +0200 From: Stefan Esser To: Luigi Rizzo Cc: Amancio Hasty , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, Stefan Esser Subject: Re: Advice sought on PnP configuration References: <199707300216.TAA03025@rah.star-gate.com> <199707300404.GAA03229@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707300404.GAA03229@labinfo.iet.unipi.it>; from Luigi Rizzo on Wed, Jul 30, 1997 at 06:04:33AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 30, Luigi Rizzo wrote: > HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to > work correctly (which might be false, see at the end of the message). Well, there are **lots** of non-PnP mother boards out there (and I happen to own one, and for that reason I care :) Whatever solution we finally implement, we must be able to attach PnP boards without any help from the PnP BIOS. > In order to configure cards correctly, the bios should know which > IRQs and which I/O address ranges are used by plain isa devices. > The former can be told to some bioses, the latter I have never seen > how to do on my systems. This is not a big deal with PCI devices > since they usually map addresses in the high range of iospace, but > a serious problem with PnP ISA devices where iospace is tight and > shared with non PnP devices. > > Since we cannot trust the BIOS (because it does not have enough > info) the only way to do autoconfiguration reliably in FreeBSD is > the following: > > 1 probe & attach pci devices > 2 disable all pnp devices, so that they are not recognized by isa probes; > 3 probe & attach plain isa devices; > 4 configure PnP devices, using info derived from the isa configuration > process to determine which address ranges and irqs are busy; > 5 activate PnP devices; > 6 finally, probe and attach PnP devices. I'm planning to make PCI probe before user_config, and attach after, and I think the same should be done for PnP ISA devices. (I don't explicitly mention EISA or MCA, but both fall into the same category as PCI, I guess ...) In other words: All devices that can be positively detected and whose resource requirements can be determined without actually attaching them should be probed and their resource preferences or requirements should be recorded. Then a configuration defaults file should be loaded from the boot partition. As proposed earlier, scanning this file could replace the generated tables with ISA device parameters, that are currently compiled into the kernel. Fallback resources can be included into the kenrel in the same textual form that is normally read from the configuration defaults file, if a compact representation is chosen. (I proposed one, a few weeks ago.) The (optional) user configuration step allows to disable devices or to set ISA probe parameters, but I want to see this extended to include wiring of devices to buses (including PCI and SCSI :) Then the PCI and ISA PnP devices are attached, followed by the probe and attach of ISA devices. The conflicts checking is to be extended to know about resources assigned to PCI and ISA PnP devices. (I have implemented a working prototype for such resource registration and conflicts checking code, but I think it should be done quite differently than I tried it, and don't want to commit my code for that reason. There should be a functional interface that checks for conflicts, and I'm goind to implement that for PCI in such a way that it can be added to all other bus drivers easily.) > Any comments on the above ? Right now I am doing steps in the order 1, > 5, 6, 3 (2 and 4 are not necessary if the bios works), but it can > fail in some cases for the reasons stated above. What do you think about my proposed sequence ? Regards, STefan From owner-freebsd-hackers Wed Jul 30 12:30:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA27233 for hackers-outgoing; Wed, 30 Jul 1997 12:30:14 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA27137; Wed, 30 Jul 1997 12:29:39 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA19950 (5.67b/IDA-1.5); Wed, 30 Jul 1997 21:29:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id VAA12601; Wed, 30 Jul 1997 21:29:28 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 21:29:27 +0200 From: Stefan Esser To: Michael Smith Cc: Luigi Rizzo , hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, Stefan Esser Subject: Re: Advice sought on PnP configuration References: <199707300404.GAA03229@labinfo.iet.unipi.it> <199707300600.PAA19038@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707300600.PAA19038@genesis.atrad.adelaide.edu.au>; from Michael Smith on Wed, Jul 30, 1997 at 03:30:44PM +0930 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 30, Michael Smith wrote: > My personal preference : > > - gather all the information : > PCI probe > PnP probe > get ISA config (compiled in, datafile, etc.) > get PCI/PnP identifier tables (compiled in, bootloader, etc.) > > - attach PCI devices > I/O ports and IRQs are assigned by the PCI rules. > - attach PnP devices > IRQs are taken from the free pool left after PCI assignment and > those marked for 'legacy' use. I/O ports are probed as per the > PnP spec. > - walk ISA config data, probe possible devices > We know which IRQ and I/O resources are still available, > we can hunt for devices that match the gaps. Exactly what I think too. > I think it's important to leave the 'legacy' devices until _last_, as > this prevents a PnP device being accidentally recognised as a 'legacy' > device. Yes. This problem does exist with PCI cards that fully emulate some ISA card, too, and the PCI probe was moved to the head of the probes for that reason, a long time ago ... Regards, STefan From owner-freebsd-hackers Wed Jul 30 12:44:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28346 for hackers-outgoing; Wed, 30 Jul 1997 12:44:41 -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 MAA28336 for ; Wed, 30 Jul 1997 12:44:36 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id UAA19743; Wed, 30 Jul 1997 20:27:32 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Wed, 30 Jul 1997 20:28:56 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199707301817.LAA05450@phaeton.artisoft.com> References: <19970730123613.03490@milkyway.com> from "Brian Campbell" at Jul 30, 97 12:36:13 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Jul 1997 20:24:47 +0100 To: Terry Lambert , brianc@milkyway.com (Brian Campbell) From: Bob Bishop Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 19:17 +0100 30/7/97, Terry Lambert wrote: >[...] >Nevertheless, I remain pissed that I can't get a 486 DX/2-100 >and leave my bus speed up at 50MHz. I've heard people claiming to clock Cyrix DX2/80's up to 50MHz; goodness knows what they do for cooling. -- 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 Jul 30 12:51:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28731 for hackers-outgoing; Wed, 30 Jul 1997 12:51:57 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA28712; Wed, 30 Jul 1997 12:51:52 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-2.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA20092 (5.67b/IDA-1.5); Wed, 30 Jul 1997 21:51:38 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id VAA12710; Wed, 30 Jul 1997 21:51:36 +0200 (CEST) X-Face: " Date: Wed, 30 Jul 1997 21:51:35 +0200 From: Stefan Esser To: Luigi Rizzo Cc: Michael Smith , hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration References: <199707300600.PAA19038@genesis.atrad.adelaide.edu.au> <199707300552.HAA03429@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707300552.HAA03429@labinfo.iet.unipi.it>; from Luigi Rizzo on Wed, Jul 30, 1997 at 07:52:58AM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 30, Luigi Rizzo wrote: > > My personal preference : > > > > - gather all the information : > > PCI probe > > PnP probe > > get ISA config (compiled in, datafile, etc.) > > get PCI/PnP identifier tables (compiled in, bootloader, etc.) > > unfortunately, in the current code, a device is probed and attached > right after the probe succeeds (otherwise, I guess one should store > information on which devices have been probed successfully and where... > etc) The PCI probe/attach being combined is one of the shortcomings of the PCI code in 2.x. This was one of the reasons to rewrite the PCI code from scratch. The code as currently commited contains quite some compatibility wrappers, which hide the differences to the drivers, since I did not want them to diverge from 2.x too much, right now. > > - attach PCI devices > > I/O ports and IRQs are assigned by the PCI rules. > > - attach PnP devices > > IRQs are taken from the free pool left after PCI assignment and > > those marked for 'legacy' use. I/O ports are probed as per the > > PnP spec. > > - walk ISA config data, probe possible devices > > We know which IRQ and I/O resources are still available, > > we can hunt for devices that match the gaps. > > but this is a problem: you cannot (generally) reprogram isa device, so > it would be better to probe them first and then relocate the > programmable ones at a later time. As I said, for PCI devices it is not > much of a problem: io addresses are generally taken from a different > range, DMA does not use the ISA dma controller, and interrupts can be > shared. But for PnP... > > I think it's important to leave the 'legacy' devices until _last_, as > > this prevents a PnP device being accidentally recognised as a 'legacy' > > device. > > same goal that I have, but in a slightly different manner: step 2 > _disables_ all pnp devices so they cannot be recognised as legacy > devices. so the non-pnp isa attach cannot find PnP devices. As for > getting isa config info: the only way we can do it is by looking at > what devices have been successfully attached; compiled-in information > are not helpful when a kernel such as GENERIC is built, with a ton of > different devices compiled in. You could do PCI probe, ISA PnP Probe, config, PCI attach, ISA probe and attach (with PnP devices disabled) and finally PnP attach. But I think it would be sufficient to do it in the order: PCI probe, PnP probe, config (incl. disable non-PnPP devices that conflict with ISA PnP devices, if desired), attach PCI, attach PnP and finally probe and attach ISA. Regards, STefan From owner-freebsd-hackers Wed Jul 30 13:55:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02917 for hackers-outgoing; Wed, 30 Jul 1997 13:55:30 -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 NAA02908 for ; Wed, 30 Jul 1997 13:55:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA05832; Wed, 30 Jul 1997 13:54:00 -0700 From: Terry Lambert Message-Id: <199707302054.NAA05832@phaeton.artisoft.com> Subject: Re: Pentium II? To: brianc@milkyway.com (Brian Campbell) Date: Wed, 30 Jul 1997 13:54:00 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970730144420.16698@milkyway.com> from "Brian Campbell" at Jul 30, 97 02:44:20 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 > > Actually, these are the same people who said I could get a > > 486 DX/2-100, and thus convinced me to buy my 486 DX-50. > > Can't now, or couldn't ever? It was announced, in almost the same format as this 266 announcement that was referenced. Do not believe announcements; believe only shrink-wrapped packages which you can touch. > I used to have a DX4, and did manage to get it to boot at 2*50, but my > graphics and scsi cards didn't like that much. I know at least one > other person that claims to keep his DX4 running at 2*50. One wonders how he managed to change his clock multiplier on board the chip from the mask-programmed value of "3"... 8-). For video, he should run an S3 chipset board, which is more tolerant of bus overclocking than the nasty Mach-32/64 chipsets; the only boards in my bus-overclocked EISA machine are an S3 graphics board and an AHA1742B. > > My 486 DX-50 still beats the snot of of a P5 DX/2-66, and is > > more than fast enough (EISA bus overclocked to 50MHz) to handle > > a lot of stuff that early P5 machines couldn't. > > Hmmm ... Never heard of a P5 DX/2-66 ;-) Dell was selling them. This was back when they were using the Saturn I chipset, which did not have DMA writeback notification connected from the macrocell (missing trace). Clock-doubled 66 MHz Pentiums were at one time common, before CPU fans became common. Dell also had 60MHz non-doubled chips available before the doubled 66's were available. The non-doubled 60's kicked butt over the doubled 66's for anything I/O bound. Just as my 486/50 kicks butt over the same chips. 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 Jul 30 14:33:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA05150 for hackers-outgoing; Wed, 30 Jul 1997 14:33:53 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA05144 for ; Wed, 30 Jul 1997 14:33:50 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA18024 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Wed, 30 Jul 1997 23:33:24 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id WAA02706; Wed, 30 Jul 1997 22:45:09 +0200 (MET DST) From: Wilko Bulte Message-Id: <199707302045.WAA02706@yedi.iaf.nl> Subject: Re: Sharing interrupts To: ac199@hwcn.org Date: Wed, 30 Jul 1997 22:45:08 +0200 (MET DST) Cc: mouth@ibm.net, msmith@atrad.adelaide.edu.au, freebsd@atipa.com, hackers@FreeBSD.ORG, terry@lambert.org In-Reply-To: from "Tim Vanderhoek" at Jul 30, 97 12:27:20 pm 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 Tim Vanderhoek wrote... > On Wed, 30 Jul 1997, John Kelly wrote: > > > Available at Radio Shack, 1N4001silicon diodes are ideal for this > > I've never seen a radio-shack which sells this kind of stuff. Their > most low-level components seem to be speaker-wire, often-as-not. Is > this a US-specific thing, or do I just not look hard enough? (Only No, we had one here in Arnhem, the Netherlands that had stuff like this. They went belly up because they were simply too expensive compared to the local electronics shops. > out of curiousity. There are plenty of other places to find these > things. :) Yep. [Back to our regular scheduled -hackers traffic] Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 30 14:34:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA05195 for hackers-outgoing; Wed, 30 Jul 1997 14:34:17 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA05187 for ; Wed, 30 Jul 1997 14:34:13 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA18039 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Wed, 30 Jul 1997 23:34:31 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id WAA02719; Wed, 30 Jul 1997 22:47:29 +0200 (MET DST) From: Wilko Bulte Message-Id: <199707302047.WAA02719@yedi.iaf.nl> Subject: Re: ISDN drivers/cards To: perhaps@yes.no (Eivind Eklund) Date: Wed, 30 Jul 1997 22:47:29 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707301904.VAA27279@bitbox.follo.net> from "Eivind Eklund" at Jul 30, 97 09:04:51 pm 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 Eivind Eklund wrote... > > > If anybody would like to attempt to develop drivers for the the Tele/S > ISDN cards, I've got some cards I'm not using. These are European > cards; they won't work on a standard US endpoint. Also, they are > fairly low-level, and need a lot of logic in the driver. There is already working ISDN stuff for the Teles. At least we run a 2.2.1R system that uses it. It ain't the prettiest of things but it works and seems quite stable. Do you want to clean things up? Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 30 15:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09072 for hackers-outgoing; Wed, 30 Jul 1997 15:32:04 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09024; Wed, 30 Jul 1997 15:31:50 -0700 (PDT) Received: from ntws (ntws.etinc.com [204.141.95.142]) by etinc.com (8.8.3/8.6.9) with SMTP id SAA00492; Wed, 30 Jul 1997 18:39:09 -0400 (EDT) Message-Id: <3.0.32.19970730182946.00e44bc0@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 30 Jul 1997 18:29:49 -0400 To: Stefan Esser , Luigi Rizzo From: dennis Subject: Re: Advice sought on PnP configuration Cc: Amancio Hasty , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, Stefan Esser Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 09:25 PM 7/30/97 +0200, Stefan Esser wrote: >On Jul 30, Luigi Rizzo wrote: >> HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to >> work correctly (which might be false, see at the end of the message). > [much snipage] Note the PnP for ISA is a nightmare...a real joke if you have shared memory cards because of the limited space available. If you try to set a PCI card with 64kb of ram to "below 1 meg" most of the time the machine will hang or fail if you have another shared card also, because there isnt enough contiguous space for both of them. The bios' just aren't smart enough to solve these problems, and once a card is configured they can "reallocate" the space if something else needs to be fit in. They just fail. Dennis From owner-freebsd-hackers Wed Jul 30 15:52:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA10285 for hackers-outgoing; Wed, 30 Jul 1997 15:52:47 -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 PAA10254; Wed, 30 Jul 1997 15:52:37 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id PAA00566; Wed, 30 Jul 1997 15:38:04 -0700 (PDT) Message-Id: <199707302238.PAA00566@rah.star-gate.com> To: dennis cc: Stefan Esser , Luigi Rizzo , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Wed, 30 Jul 1997 18:29:49 EDT." <3.0.32.19970730182946.00e44bc0@etinc.com> Date: Wed, 30 Jul 1997 15:38:04 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk the stuff that I did for the gus pnp allows the uses to override whatever the bios thinks that I should have 8) The reason for this is because the first box that I tried the gus pnp had a broken PnP bios . So we should provide a general mechanism for handling PnP devices and a *manual* or old style config capability. I have just simply ran into too many brain-dead PnP bios. Cheers, Amancio >From The Desk Of dennis : > At 09:25 PM 7/30/97 +0200, Stefan Esser wrote: > >On Jul 30, Luigi Rizzo wrote: > >> HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to > >> work correctly (which might be false, see at the end of the message). > > > [much snipage] > > Note the PnP for ISA is a nightmare...a real joke if you have shared > memory cards because of the limited space available. If you try > to set a PCI card with 64kb of ram to "below 1 meg" most of the > time the machine will hang or fail if you have another shared card > also, because there isnt enough contiguous space for both of them. > The bios' just aren't smart enough to solve these problems, and once > a card is configured they can "reallocate" the space if something else > needs to be fit in. They just fail. > > Dennis From owner-freebsd-hackers Wed Jul 30 17:11:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14807 for hackers-outgoing; Wed, 30 Jul 1997 17:11:36 -0700 (PDT) Received: from mail5.doit.wisc.edu (mail5.doit.wisc.edu [144.92.104.215]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14796 for ; Wed, 30 Jul 1997 17:11:30 -0700 (PDT) Received: from audumla.students.wisc.edu by mail5.doit.wisc.edu; id TAA56146; 8.7.5/50; Wed, 30 Jul 1997 19:11:06 -0500 Received: from gabor-bsd by audumla.students.wisc.edu; id TAA48464; 8.6.9W/42; Wed, 30 Jul 1997 19:10:46 -0500 Message-ID: <33DFD7E5.41C67EA6@acm.org> Date: Wed, 30 Jul 1997 19:10:13 -0500 From: Gabor Kincses X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: PPP chap problem 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 tried to make chap work, but no go. I have used pap and no authentication for over 6 months now, but chap doesn't seem to work. I always get LCP: SendConfigRej(Req-Sent) AUTHPROTO proto = c223 which means that my side rejects chap authentication. Even though I added enable chap, accept chap. I also tried to disable chap and only accept chap, but that didn't work either. I also tried accept pap in which case the SendConfigRej became a SendConfigNak with c023 suggested to the peer. I got the same results under 2.1.5 and 2.2.2. Any help is really appreciated. BTW, I have to use term so that I can enter an SNK response before going into packet mode. I don't think that should matter. -- Gabor Kincses (gabor@acm.org) FreeBSD 2.1.5/2.2.2 From owner-freebsd-hackers Wed Jul 30 17:44:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17245 for hackers-outgoing; Wed, 30 Jul 1997 17:44:29 -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 RAA17227 for ; Wed, 30 Jul 1997 17:44:23 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id KAA24721; Thu, 31 Jul 1997 10:14:09 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id KAA18156; Thu, 31 Jul 1997 10:14:03 +0930 (CST) Message-Id: <199707310044.KAA18156@freebie.lemis.com> Subject: Re: ISDN drivers/cards In-Reply-To: <199707301904.VAA27279@bitbox.follo.net> from Eivind Eklund at "Jul 30, 97 09:04:51 pm" To: perhaps@yes.no (Eivind Eklund) Date: Thu, 31 Jul 1997 10:14:03 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers), isdn@muc.ditec.de (FreeBSD ISDN Distribution List) 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-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 Eivind Eklund writes: > > If anybody would like to attempt to develop drivers for the the Tele/S > ISDN cards, I've got some cards I'm not using. These are European > cards; they won't work on a standard US endpoint. Also, they are > fairly low-level, and need a lot of logic in the driver. > > Contact me for further info if you're interested. (Yeah, I know of > the bISDN people, but nothing seems to be happening there; besides, > they have already got hardware, it seems.) The thing you apparently don't know is that the bisdn stuff runs on exactly these boards. The real problem isn't the board, it's the different ISDN standards in the US and in Europe. But I appreciate the idea. Don't look at me, though--I live in Australia, and though I would dearly love to run ISDN, it's too expensive here. Greg From owner-freebsd-hackers Wed Jul 30 17:54:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17874 for hackers-outgoing; Wed, 30 Jul 1997 17:54:58 -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 RAA17867 for ; Wed, 30 Jul 1997 17:54:55 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id KAA24813; Thu, 31 Jul 1997 10:24:51 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id KAA18204; Thu, 31 Jul 1997 10:24:45 +0930 (CST) Message-Id: <199707310054.KAA18204@freebie.lemis.com> Subject: Re: PCMCIA on FreeBSD2.2.1 In-Reply-To: <19970729.164516.11567.0.RonDzierwa@juno.com> from Ron Dzierwa at "Jul 29, 97 04:34:54 pm" To: rondzierwa@juno.com (Ron Dzierwa) Date: Thu, 31 Jul 1997 10:24:45 +0930 (CST) Cc: hackers@FreeBSD.ORG 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-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 Ron Dzierwa writes: > Dear Hackers, > > I recently installed 2.2.1 on an Ergo Powerbrick 100 Notebook computer > and had some questions regarding the PCMCIA support. The hardware > compatibility list indicates that the 3Com 3c589 pcmcia ethernet is > supported, as well as the adaptec AIC-6360 pcmcia scsi controller both of > which I have installed and tested using dos/windows drivers and even NT > 3.51. I am having problems getting them to work under FreeBSD 2.2.1 > however, and hoped somebody there could help. You might be running into a problem I had a few months back. It seems that, at that time (December 1996), the PCMCIA code was not able to grok my notebook hardware (AcerNote Lite, apparently one of many different machines to bear that name. This one is a 75MHz Pentium, and must have one of the slowest disks I've seen in a long time). > Also, the computer uses a DataBook DB86082 PCMCIA controller chip. I > looked thru the PCMCIA support code and did not find any mention of this > chip, so I am wondering if it is supported. I have the data sheets and > some diagnostic/test/development software for the chip (runs under dos), > so I would be willing to put some work into adding support for the chip > to the existing PCMCIA code if necessary. That sounds like a good idea. It also sounds like my problem. > Regarding the scsi controller, the driver in the generic kernel seems to > be able to find it when booting from the CDROM using fbsdboot, but > shortly thereafter the system hangs up. I believe that it could find > the scsi controller because I was booting from dos and the pcmcia > controller was still set up from the dos driver. This leads me back to > the PCMCIA support code. > > So I guess what I am asking is: > - How to setup/configure the `D' version of the 3c589 > - Is my PCMCIA chip supported at all? > - How to configure the AIC-6360 driver to work with the PCMCIA chip. About the only thing I can suggest is that you first try the generic kernel. That's what I'm running on my notebook (that's right, without any PCMCIA support), and it works. If I install the PCMCIA support, it stops working. Greg From owner-freebsd-hackers Wed Jul 30 18:09:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA18952 for hackers-outgoing; Wed, 30 Jul 1997 18:09:18 -0700 (PDT) Received: from mail5.doit.wisc.edu (mail5.doit.wisc.edu [144.92.104.215]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA18935 for ; Wed, 30 Jul 1997 18:09:13 -0700 (PDT) Received: from audumla.students.wisc.edu by mail5.doit.wisc.edu; id UAA48862; 8.7.5/50; Wed, 30 Jul 1997 20:09:12 -0500 Received: from gabor-bsd by audumla.students.wisc.edu; id UAA40446; 8.6.9W/42; Wed, 30 Jul 1997 20:09:01 -0500 Message-ID: <33DFE58C.794BDF32@acm.org> Date: Wed, 30 Jul 1997 20:08:28 -0500 From: Gabor Kincses X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: PLIP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have successfully brought up the FreeBSD version of the lpt0 interface with -link0 flag and was wondering if I could connect my laptop running Win95 to the FreeBSD box. Looking at the pertinent info it seems that the lpt0 driver is quite a "home-grown" development, ie. interoperability with other systems is quite limited. Is this because Micro$oft does not release it's parallel line protocols? Also is running nfs over two lpt0 interfaces a reasonable networking solution between two FreeBSD boxes? ftp reported ~80kbps and the hardware is cheap, I mean free. -- Gabor Kincses (gabor@acm.org) FreeBSD 2.1.5/2.2.2 From owner-freebsd-hackers Wed Jul 30 19:19:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23112 for hackers-outgoing; Wed, 30 Jul 1997 19:19:34 -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 TAA23094; Wed, 30 Jul 1997 19:19:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA25096; Thu, 31 Jul 1997 11:48:44 +0930 (CST) From: Michael Smith Message-Id: <199707310218.LAA25096@genesis.atrad.adelaide.edu.au> Subject: Re: Advice sought on PnP configuration In-Reply-To: <199707301322.PAA03822@labinfo.iet.unipi.it> from Luigi Rizzo at "Jul 30, 97 03:22:47 pm" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 31 Jul 1997 11:48:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@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 Luigi Rizzo stands accused of saying: > > Have you read the PnP document from Microsoft? The procedure is > > explicitly detailed in the section on configuring cards. Basically, > > you configure the card such that it drives half its outputs low and > > expect to read 0x55 from all its ports, then swap to the other half of > ... > > ok, clearly I need a good reading on PnP... I'll go and get some book :) Save yourself some money, and start with (shudder) http://www.microsoft.com/hwdev/ Then try http://developer.intel.com/ > Luigi -- ]] 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 Wed Jul 30 19:22:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23361 for hackers-outgoing; Wed, 30 Jul 1997 19:22: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 TAA23354 for ; Wed, 30 Jul 1997 19:22:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA25145; Thu, 31 Jul 1997 11:52:30 +0930 (CST) From: Michael Smith Message-Id: <199707310222.LAA25145@genesis.atrad.adelaide.edu.au> Subject: Re: Cross compiling for FreeBSD 3.0 In-Reply-To: from "Andy J. Smith" at "Jul 30, 97 02:56:32 pm" To: A.J.Smith@nortel.co.uk (Andy J. Smith) Date: Thu, 31 Jul 1997 11:52:30 +0930 (CST) 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 Andy J. Smith stands accused of saying: > > I have several linux boxes (2.0.30 kernel) and I want to install GCC as a > cross-compiler so I can produce FreeBSD binaries. Can anyone help me out > and give me some info as to home I might do this? You'll probably actually have quite a lot of trouble with this. If you're looking for a single-system development platform that will allow you to produce both Linux and FreeBSD binaries, you're much better off running FreeBSD with the Linux binary compatability and Linux crossdevelopment packages installed. I use both of these quite heavily, and would be happy to talk you through getting yourself set up. > I have limited access to a FreeBSD 3.0 sytem, so if I need libraries, > header files and includes I could get them that way, but it is a real > hassle so I'm hoping I don't need too much. Your biggest problem would be building the toolchain, as the GNU tools don't correctly support the FreeBSD environment. (This is only partly the GNU peoples' fault.) Let me know if I can help... -- ]] 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 Wed Jul 30 19:42:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24849 for hackers-outgoing; Wed, 30 Jul 1997 19:42:17 -0700 (PDT) Received: from herculis.alphawest.com.au (herculis.alphawest.com.au [203.14.124.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA24831 for ; Wed, 30 Jul 1997 19:42:10 -0700 (PDT) Received: from KERIS by herculis.alphawest.com.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id PXDX4QW7; Thu, 31 Jul 1997 10:45:03 +0800 Message-ID: <33DFF9EC.217BDE7A@alphawest.com.au> Date: Thu, 31 Jul 1997 10:35:25 +0800 From: Stephen Cooper Organization: Alphawest Pty Ltd X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: (no subject) X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -- Stephen Cooper Internet Engineer, Internet and Open Systems Group AlphaWest, Level 10, QV1 Building, 250 St Georges Tce, Perth, WA 6000 Main: (+61 8) 94296000 Fax: (+61 8) 94296030 From owner-freebsd-hackers Wed Jul 30 19:52:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA25521 for hackers-outgoing; Wed, 30 Jul 1997 19:52: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 TAA25508; Wed, 30 Jul 1997 19:52:36 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA25196; Thu, 31 Jul 1997 12:08:16 +0930 (CST) From: Michael Smith Message-Id: <199707310238.MAA25196@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: <199707301710.KAA05257@phaeton.artisoft.com> from Terry Lambert at "Jul 30, 97 10:10:27 am" To: terry@lambert.org (Terry Lambert) Date: Thu, 31 Jul 1997 12:08:16 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, terry@lambert.org, se@FreeBSD.ORG, mo@uu.net, 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: > > > > Fair enough. How do other platforms (PReP, Alpha, etc) handle PCI > > autoconfig? Does the BIOS on those platforms provide the same set > > of management primitives? > > There is not necessarily ROM code for doing the autoconfiguration; > some of the Alpha boxes actually have an x86 emulation in software... > they use it for video card ROMs, and booting from disk controllers, > and so on. OK, but the PCI spec doesn't require the bootstrap firmware to do it. I think in that case that PCI BIOS support is probably a waste of time. > > I would have assumed so, from my reading of PCI-spec-derived documents. > > (I don't have the "real thing", obviously) > > Why not? They are cheap... all specs go down in price to 10% of > their former cost days after I buy them. It's a law of nature. Uhh, define "cheap". Especially define "cheap" including airfreight to the antipodes. > Terry Lambert -- ]] 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 Wed Jul 30 20:04:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26475 for hackers-outgoing; Wed, 30 Jul 1997 20:04:18 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26462 for ; Wed, 30 Jul 1997 20:04:14 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id WAA11498; Wed, 30 Jul 1997 22:03:52 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <14878.870303204@time.cdrom.com> References: Your message of "Wed, 30 Jul 1997 14:04:33 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 30 Jul 1997 22:01:02 -0500 To: "Jordan K. Hubbard" From: Richard Wackerbarth Subject: On the subject of ISP Administration Cc: Vincent Poy , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 5:53 PM -0500 7/30/97, Jordan K. Hubbard wrote: >What's the deal here? Did >somebody drop a million matchbooks over the U.S. saying "become an ISP >and make tons of $$$ in your spare time ... No, it wasn't matchbooks. It arrives every hour in the "spam mail". :-) By the way, if you don't recognize that "SPAM" is a registered trademark of Hormel, you, like many others, may not be qualified to do ISP administration either. Seriously, those of us who have been around since the "dark ages" need to remember that there is a fine line between mentoring and putting those "think they know it all whippersnappers" in their place. There is a saying about wisdom which is something to the effect that once you pass through the teen years, your father becomes more intellegent every year. ... Let's ALL try to do a better job of learning rather than whining and mentoring rather than berating. PS: This is not directed at Jordan. He does a much better job of it than most of us. ... But, for the rest, "if the Foo shits, wear it." And I, too, think that the subject has been beaten to death ... From owner-freebsd-hackers Wed Jul 30 20:08:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26780 for hackers-outgoing; Wed, 30 Jul 1997 20:08:51 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26775 for ; Wed, 30 Jul 1997 20:08:48 -0700 (PDT) Received: from w2xo.pgh.pa.us (localhost [127.0.0.1]) by w2xo.pgh.pa.us (8.8.4/8.8.4) with SMTP id XAA06805 for ; Wed, 30 Jul 1997 23:09:13 -0400 (EDT) Message-ID: <33E001D9.446B9B3D@w2xo.pgh.pa.us> Date: Wed, 30 Jul 1997 23:09:13 -0400 From: Jim Durham Organization: Dis- X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Generic PCI ethernet card 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 a "generic" (read "cheap") PCI ethernet card here that purports to be able to use the NE2000 driver. I notice when I boot the system that the PCI stuff is all OK, but, apparently, the ID code on the card is not recognized, and no driver is assigned. Is this just a matter of adding the ID code to the driver in if_ed_p.c, where it lists RealTek 8029, ProLan, and etc...and I guess I have to boot the system and see what code is returned...or am I off on the wrong path? Also, how does the system know to even have if_ed_p.c scan for a code if it doesn't know what kind of card it is dealing with? Is this handed down from the bios? Lotsa questions... regards, Jim Durham From owner-freebsd-hackers Wed Jul 30 20:18:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA27380 for hackers-outgoing; Wed, 30 Jul 1997 20:18:08 -0700 (PDT) Received: from pobox.com (ras139.microplus.ca [207.81.20.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA27357 for ; Wed, 30 Jul 1997 20:17:58 -0700 (PDT) Resent-From: brianc@pobox.com Received: (from brianc@localhost) by pobox.com (8.8.5/8.8.5) id XAA20521 for freebsd-hackers@FreeBSD.org; Wed, 30 Jul 1997 23:15:47 -0400 (EDT) Resent-Message-Id: <199707310315.XAA20521@pobox.com> Message-ID: <19970730231525.13198@pobox.com> Date: Wed, 30 Jul 1997 23:15:25 -0400 From: Brian Campbell To: Terry Lambert Subject: Re: Pentium II? References: <19970730144420.16698@milkyway.com> <199707302054.NAA05832@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199707302054.NAA05832@phaeton.artisoft.com>; from Terry Lambert on Wed, Jul 30, 1997 at 01:54:00PM -0700 Resent-Date: Wed, 30 Jul 1997 23:15:47 -0400 Resent-To: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Jul 30, 1997 at 01:54:00PM -0700, Terry Lambert wrote: > > > Actually, these are the same people who said I could get a > > > 486 DX/2-100, and thus convinced me to buy my 486 DX-50. > > > > Can't now, or couldn't ever? > > It was announced, in almost the same format as this 266 announcement > that was referenced. Do not believe announcements; believe only > shrink-wrapped packages which you can touch. > > > I used to have a DX4, and did manage to get it to boot at 2*50, but my > > graphics and scsi cards didn't like that much. I know at least one > > other person that claims to keep his DX4 running at 2*50. > > One wonders how he managed to change his clock multiplier on > board the chip from the mask-programmed value of "3"... 8-). Pardon me for suggesting that I or others could accomplish something you apparently could not. I'm sure we're all mistaken. Send a nasty letter to the maintainer of: www.xmission.com/~doswald/clkfaq.html P.S. I will, in the future, not believe any announcements. From owner-freebsd-hackers Wed Jul 30 21:03:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA29520 for hackers-outgoing; Wed, 30 Jul 1997 21:03:32 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA29513 for ; Wed, 30 Jul 1997 21:03:26 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id VAA12099; Wed, 30 Jul 1997 21:06:10 -0700 (PDT) Date: Wed, 30 Jul 1997 21:06:10 -0700 (PDT) From: Howard Lew To: FreeBSD Mailing List cc: hackers@FreeBSD.ORG, Tom Samplonius Subject: Re: Pentium II? 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, 30 Jul 1997, FreeBSD Mailing List wrote: > > > On Wed, 30 Jul 1997, Craig Johnston wrote: > > > > > Not buying into Intel's slot 1 ploy is a good enough reason not to run > > > > PII's. Slot 1 is not going to be around very long and I wouldn't count > > > > on not running into bugs in the relatively untested slot 1 chipset. > > > > If you use that arguement, you shouldn't by anything then! The PPro > > > > Um, no. There's this idea of relative quantities, you see? Slot 1 > > is going to be short-lived _compared_ to other solutions. How long > > has socket 7 been ticking along now? It's well known that slot 2 is > > coming right on the heels of slot 1. > > Just to make the point more muddled, the PII's and PPro's use THE EXACT > SAME CHIPSET! In fact, you can buy a SEC to ZIF SOCKET 8 converter. The > chipset is not or should not be the concern (97% of all P2's and Pro's > are using the Intel Natoma (440FX) chipset). > > > Why bother with the Intel "chipset of the week" game? Slot 1 systems > > don't offer anything you can't do better with the same cash with PPro and > > socket 7 systems. The only folks likely to benefit from slot 1 at > > all are likely to be Intel -- they'll make a bundle off upgrade-happy > > power-lusers who've been exposed to one too many Ziff-Davis magazines. > > With the same cash is important. P2 boards will be more expensive, along > with the chips. > > > > (socket 8?) is doomed too, as Intel will not be developing it further (a > > > 233mhz version would be nice). The Pentium MMX is going to max at 233, > > > before being put out to pasture. So, every option is "doomed"... > > ZIF architecture is being promoted heavily by AMD, Cyrix, etc. The new > Socket 7 motherboards we carry go up to 363MHz (66 x 5.5) and above > (83MHZ x 4.5). I expect ZIF-8 solutions to be available soon from > competitive vendors. > Anyone know what brands of motherboards with 5.5X jumpers are available now? I know FreeTech has one, but then it is a VX chipset one. From owner-freebsd-hackers Wed Jul 30 21:10:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00227 for hackers-outgoing; Wed, 30 Jul 1997 21:10:38 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA00219 for ; Wed, 30 Jul 1997 21:10:33 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA18977; Wed, 30 Jul 1997 21:10:01 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018972; Wed Jul 30 21:09:47 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id VAA24294; Wed, 30 Jul 1997 21:09:42 -0700 (PDT) From: Archie Cobbs Message-Id: <199707310409.VAA24294@bubba.whistle.com> Subject: Re: PPP chap problem In-Reply-To: <33DFD7E5.41C67EA6@acm.org> from Gabor Kincses at "Jul 30, 97 07:10:13 pm" To: gabor@acm.org (Gabor Kincses) Date: Wed, 30 Jul 1997 21:09:42 -0700 (PDT) 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 have tried to make chap work, but no go. I have used pap and no > authentication for over 6 months now, but chap doesn't seem to work. > > I always get > LCP: SendConfigRej(Req-Sent) > AUTHPROTO proto = c223 > > which means that my side rejects chap authentication. > Even though I added enable chap, accept chap. Enable chap means "i want the peer to authenticate to me using chap", so you don't want to do that. > I also tried to disable chap and only accept chap, but that didn't work Hmm, should have. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Wed Jul 30 21:10:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00252 for hackers-outgoing; Wed, 30 Jul 1997 21:10: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 VAA00243 for ; Wed, 30 Jul 1997 21:10:47 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA25701; Thu, 31 Jul 1997 13:40:38 +0930 (CST) From: Michael Smith Message-Id: <199707310410.NAA25701@genesis.atrad.adelaide.edu.au> Subject: Re: Generic PCI ethernet card In-Reply-To: <33E001D9.446B9B3D@w2xo.pgh.pa.us> from Jim Durham at "Jul 30, 97 11:09:13 pm" To: durham@w2xo.pgh.pa.us (Jim Durham) Date: Thu, 31 Jul 1997 13:40:38 +0930 (CST) Cc: 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 Jim Durham stands accused of saying: > > Is this just a matter of adding the ID code to > the driver in if_ed_p.c, where it lists RealTek 8029, > ProLan, and etc...and I guess I have to boot the > system and see what code is returned...or am I off > on the wrong path? Spot on. If you boot with '-v' you will get a listing of the vendor and board ID numbers, which you can plug in there. Could you please let us know what these numbers are when you've got them so that other people can benefit? Either mail the hardware list, or send the details straight to Stefan (se@freebsd.org). > Also, how does the system know to > even have if_ed_p.c scan for a code if it doesn't know > what kind of card it is dealing with? Is this handed > down from the bios? Lotsa questions... Each code is handed to every PCI probe routine, so the probe routines get to decide whether the card is for them. This is a mechanism that's likely to change in the future. > Jim Durham -- ]] 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 Wed Jul 30 21:52:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA02862 for hackers-outgoing; Wed, 30 Jul 1997 21:52:10 -0700 (PDT) Received: from mail5.doit.wisc.edu (mail5.doit.wisc.edu [144.92.104.215]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA02855 for ; Wed, 30 Jul 1997 21:52:05 -0700 (PDT) Received: from audumla.students.wisc.edu by mail5.doit.wisc.edu; id XAA162880; 8.7.5/50; Wed, 30 Jul 1997 23:52:03 -0500 Received: from gabor-bsd by audumla.students.wisc.edu; id XAA24318; 8.6.9W/42; Wed, 30 Jul 1997 23:51:54 -0500 Message-ID: <33E019CE.167EB0E7@acm.org> Date: Wed, 30 Jul 1997 23:51:26 -0500 From: Gabor Kincses X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Archie Cobbs CC: hackers@FreeBSD.ORG Subject: Re: PPP chap problem References: <199707310409.VAA24294@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: > > > I have tried to make chap work, but no go. I have used pap and no > > authentication for over 6 months now, but chap doesn't seem to work. > > > > I always get > > LCP: SendConfigRej(Req-Sent) > > AUTHPROTO proto = c223 > > > > which means that my side rejects chap authentication. > > Even though I added enable chap, accept chap. > > Enable chap means "i want the peer to authenticate to me using chap", > so you don't want to do that. > > > I also tried to disable chap and only accept chap, but that didn't work > > Hmm, should have. > > -Archie > I understood what enable chap meant after reading someone's post on the newgroup and tried out disable chap and accept chap, which didn't work either. The really interesting part is that if I say accept pap, then the SendConfigRej becomes SendConfigNak AUTHPROTO proto = c023, so it seems there might be something wrong with the chap state in the code. Again I'm getting this after I escape out of term into packet mode. Is there anything different here from executing a script? I only have the 2.1.5 source code, but haven't been able to dig through the relevant portions. All I can tell that the code never really gets into the chap.c stuff... -- Gabor Kincses (gabor@acm.org) FreeBSD 2.1.5/2.2.2 From owner-freebsd-hackers Wed Jul 30 22:02:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA03316 for hackers-outgoing; Wed, 30 Jul 1997 22:02:24 -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 WAA03311 for ; Wed, 30 Jul 1997 22:02:21 -0700 (PDT) Received: (qmail 12008 invoked by uid 1000); 31 Jul 1997 05:02:35 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-PRIORITY: 2 (High) Priority: urgent Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 30 Jul 1997 22:02:35 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: (mainly CMOS) - howto? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I need to have the followinf struct filled up with sane information. Other than inb and outb to the BIOS registers, how do I get this data? typedef struct dpt_sysinfo { u_int8_t drive0CMOS; /* CMOS Drive 0 Type */ u_int8_t drive1CMOS; /* CMOS Drive 1 Type */ u_int8_t numDrives; /* 0040:0075 contents */ u_int8_t processorFamily; /* i386 vs. Alpha, etc. */ u_int8_t processorType; /* {3,4,5,6}86 */ u_int8_t smartROMMajorVersion; /* I know that :-) */ u_int8_t smartROMMinorVersion; /* ... and that... */ u_int8_t smartROMRevision; /* ... and even that */ u_int16_t flags; /* Forget this one */ u_int16_t conventionalMemSize; /* in KB */ u_int32_t extendedMemSize /* in KB */ u_int32_t osType; /* I think I know this one */ u_int8_t osMajorVersion; u_int8_t osMinorVersion; /* The OS version */ u_int8_t osRevision; u_int8_t osSubRevision; u_int8_t busType; /* I can guess this one */ u_int8_t pad[3]; /* This one is easy */ driveParam_T drives[16]; /* Do not worry about these... */ */ } dpt_sysinfo_t; Thanx a million (well, 17, at least :-) Simon From owner-freebsd-hackers Wed Jul 30 22:11:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA03850 for hackers-outgoing; Wed, 30 Jul 1997 22:11:15 -0700 (PDT) Received: from daemonweed.reanimators.org (fmc@daemonweed.reanimators.org [198.137.202.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA03833; Wed, 30 Jul 1997 22:11:03 -0700 (PDT) Received: (from fmc@localhost) by daemonweed.reanimators.org (8.8.5/8.8.5) id WAA15704; Wed, 30 Jul 1997 22:10:56 -0700 (PDT) Message-Id: <199707310510.WAA15704@daemonweed.reanimators.org> To: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI 1542 error References: <199707301202.IAA15575@i4got.lakewood.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Frank McConnell Date: 30 Jul 1997 22:10:55 -0700 In-Reply-To: Bill Pechter's message of Wed, 30 Jul 1997 08:02:41 -0400 (EDT) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Pechter writes: > BTW -- the ch device doesn't use bounce buffers at all (unfortunately)... > I've got the same problem with 2.2.2... I noticed this the other day (similar config, 2.2.1, ISA bus, 1542CP? with Archive changer) and have come up with what I think is a fix. Diffs below. But first, some notes: (a) I am running FreeBSD 2.2.1-RELEASE, not 2.2.2. I have no idea how much the ch driver has changed in that span. (b) This corrects the malloc()s of data buffers in ch_usergetelemstatus() so that bounce buffers may be used instead. (c) Still questionable to me is the use of a stack temporary (sense_data) in ch_get_params() as a data buffer. It seems to work but I don't understand why, probably because I don't quite understand how what happens down below happens. Should it be changed too? (d) From (c), I probably have no business monkeying with this sort of thing, and someone who knows more ought to look this over. It lets me do chio status in addition to chio move, but that's as far as I've tested it. Criticism is welcome. -Frank McConnell, maybe-wannabe-freebsd-hacker --- cut here --- *** ch.c.2.2.1-RELEASE Fri Mar 7 01:34:26 1997 --- ch.c Tue Jul 29 21:30:42 1997 *************** *** 36,41 **** --- 36,42 ---- * $Id: ch.c,v 1.34.2.1 1997/03/07 09:34:26 joerg Exp $ */ + #include "opt_bounce.h" #include "opt_scsi.h" #include *************** *** 511,517 **** struct read_element_status_page_header *pg_hdr; struct read_element_status_descriptor *desc; caddr_t data = NULL; ! size_t size, desclen; int avail, i, error = 0; u_int8_t *user_data = NULL; --- 512,518 ---- struct read_element_status_page_header *pg_hdr; struct read_element_status_descriptor *desc; caddr_t data = NULL; ! size_t size, desclen, datalen; int avail, i, error = 0; u_int8_t *user_data = NULL; *************** *** 528,534 **** * we can allocate enough storage for all of them. We assume * that the first one can fit into 1k. */ ! data = (caddr_t)malloc(1024, M_DEVBUF, M_WAITOK); if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], 1, data, 1024)) goto done; --- 529,540 ---- * we can allocate enough storage for all of them. We assume * that the first one can fit into 1k. */ ! datalen = 1024; ! #ifdef BOUNCE_BUFFERS ! data = (caddr_t)vm_bounce_kva_alloc(btoc(datalen)); ! #else ! data = (caddr_t)malloc(datalen, M_DEVBUF, M_WAITOK); ! #endif if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], 1, data, 1024)) goto done; *************** *** 545,554 **** * Reallocate storage for descriptors and get them from the * device. */ free(data, M_DEVBUF); data = (caddr_t)malloc(size, M_DEVBUF, M_WAITOK); if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], ! sc->sc_counts[chet], data, size)) goto done; /* --- 551,566 ---- * Reallocate storage for descriptors and get them from the * device. */ + #ifdef BOUNCE_BUFFERS + vm_bounce_kva_alloc_free((vm_offset_t)data, btoc(datalen)); + data = (caddr_t)vm_bounce_kva_alloc(btoc(size)); + #else free(data, M_DEVBUF); data = (caddr_t)malloc(size, M_DEVBUF, M_WAITOK); + #endif + datalen = size; if (error = ch_getelemstatus(sc, sc->sc_firsts[chet], ! sc->sc_counts[chet], data, size)) goto done; /* *************** *** 575,581 **** --- 587,597 ---- done: if (data != NULL) + #ifdef BOUNCE_BUFFERS + vm_bounce_kva_alloc_free((vm_offset_t)data, btoc(datalen)); + #else free(data, M_DEVBUF); + #endif if (user_data != NULL) free(user_data, M_DEVBUF); return (error); From owner-freebsd-hackers Wed Jul 30 22:50:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA05736 for hackers-outgoing; Wed, 30 Jul 1997 22:50:41 -0700 (PDT) Received: from onyx.atipa.com (ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA05668 for ; Wed, 30 Jul 1997 22:49:34 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 31 Jul 1997 05:47:02 -0000 Date: Wed, 30 Jul 1997 23:47:02 -0600 (MDT) From: FreeBSD Mailing List X-Sender: freebsd@dot.ishiboo.com To: Howard Lew cc: hackers@FreeBSD.ORG, Tom Samplonius Subject: Re: Pentium II? 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 > > Socket 7 motherboards we carry go up to 363MHz (66 x 5.5) and above > > (83MHZ x 4.5). I expect ZIF-8 solutions to be available soon from > > competitive vendors. > Anyone know what brands of motherboards with 5.5X jumpers are available > now? I know FreeTech has one, but then it is a VX chipset one. The first mentioned is the Gigabyte GA-586HX2-512 (rev 2.0). The second is the ASUS TX-series. We have also been evaluating a *jumperless* motherboard manufactrued by ABIT. It seems really nice at first; the bus frequency, multiplier, and voltage are all set in the BIOS. It gives options for 50,55,60,66,75 and 83MHz, with multipliers up to 5.5X. The only, and major, downfall is that you CAN NOT OVERCLOCK! How silly is that? As soon as you exceed spec, it either auto-resets the values or runs unreliably. I couldn't even squeak 187.5MHZ out of a K6-166... It amazes me that the board can actually tell the difference. Pentiums also had similar results. I know the "hobbyist" would get a bit frustrated. Kevin From owner-freebsd-hackers Wed Jul 30 22:54:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA06077 for hackers-outgoing; Wed, 30 Jul 1997 22:54:05 -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 WAA06066 for ; Wed, 30 Jul 1997 22:53:59 -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 WAA16204 for ; Wed, 30 Jul 1997 22:53:48 -0700 (PDT) Prev-Resent: Wed, 30 Jul 1997 22:53:48 -0700 Prev-Resent: "hackers@freebsd.org " Received: from hub.freebsd.org (jkh-sl0-o.cdrom.com [204.216.27.193]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id LAA13923 for ; Wed, 30 Jul 1997 11:45:39 -0700 (PDT) Received: from five.aces.com (mjr@Five.ACES.COM [192.195.240.63]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23888 for ; Wed, 30 Jul 1997 11:45:45 -0700 (PDT) Received: from localhost (mjr@localhost) by five.aces.com (8.8.5/8.8.5) with SMTP id LAA02835 for ; Wed, 30 Jul 1997 11:45:38 -0700 (MST) Date: Wed, 30 Jul 1997 11:45:37 -0700 (MST) From: Matt Ramsey To: jkh@freebsd.org Subject: traceroute ... finally Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-To: hackers@freebsd.org Resent-Date: Wed, 30 Jul 1997 22:53:48 -0700 Resent-Message-ID: <16200.870328428@time.cdrom.com> Resent-From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Jordan we exchanged some email ages ago regarding getting the NANOG traceroute included in freebsd (or at least as a port). Well, after finally getting around all sorts of distractions, I finally finished the manpage describing the various features found in this enhanced version of traceroute. The tar.gz file may be found at ftp://ftp.primenet.com/pub/mjr/traceroute.tar.gz If you would please forward this to the appropriate person, I would greatly appreciate it, as I have long since forgotten who the contact was :-) If either of you have any questions or requests regarding this version of traceroute, please feel free to mail me. Thanks -mjr From owner-freebsd-hackers Wed Jul 30 23:00:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA06767 for hackers-outgoing; Wed, 30 Jul 1997 23:00:38 -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 XAA06742; Wed, 30 Jul 1997 23:00:29 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA05164; Thu, 31 Jul 1997 07:00:37 +0200 From: Luigi Rizzo Message-Id: <199707310500.HAA05164@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 31 Jul 1997 07:00:37 +0200 (MET DST) Cc: msmith@atrad.adelaide.edu.au, hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707310218.LAA25096@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 31, 97 11:48:25 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Save yourself some money, and start with (shudder) > http://www.microsoft.com/hwdev/ too bad they only have MS Word documents (what would you expect!) The PnPisa document was the one I had. some time ago i tried to extract text from it and reformat it somehow, but never printed it. In fact the details are there, it's just that on a window you cannot see them very well and need a printed copy. 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 Wed Jul 30 23:01:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA06845 for hackers-outgoing; Wed, 30 Jul 1997 23:01:56 -0700 (PDT) Received: from acromail.ml.org (acroal.vip.best.com [206.86.222.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA06838 for ; Wed, 30 Jul 1997 23:01:52 -0700 (PDT) Received: from localhost (kernel@localhost) by acromail.ml.org (8.8.6/8.8.5) with SMTP id XAA00656 for ; Wed, 30 Jul 1997 23:02:20 -0700 (PDT) Date: Wed, 30 Jul 1997 23:02:19 -0700 (PDT) From: FreeBSD Technical Reader To: hackers@FreeBSD.ORG Subject: Timer interrupt frequency 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 Can someone fill me in on the side effecs of changing HZ in param.h to 1000 or 2000 -- i need to have usleep() that will sleep 1ms under no load. Also will a make world fix the problems with top after doing this i assume such a change must go in the .h files (instead of GENERIC) since it effects out of kernel sources right? From owner-freebsd-hackers Wed Jul 30 23:07:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA07149 for hackers-outgoing; Wed, 30 Jul 1997 23:07:17 -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 XAA07123; Wed, 30 Jul 1997 23:07:06 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA05175; Thu, 31 Jul 1997 07:07:59 +0200 From: Luigi Rizzo Message-Id: <199707310507.HAA05175@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: se@FreeBSD.ORG (Stefan Esser) Date: Thu, 31 Jul 1997 07:07:59 +0200 (MET DST) Cc: hasty@rah.star-gate.com, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, se@FreeBSD.ORG In-Reply-To: <19970730212526.55863@mi.uni-koeln.de> from "Stefan Esser" at Jul 30, 97 09:25:07 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Jul 30, Luigi Rizzo wrote: > > HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to > > work correctly (which might be false, see at the end of the message). > > Well, there are **lots** of non-PnP mother boards out there > (and I happen to own one, and for that reason I care :) > > Whatever solution we finally implement, we must be able to > attach PnP boards without any help from the PnP BIOS. Ok, so you are calling for a more powerful configuration mechanism, whereas I was trying to see if I could implement something much simpler which would not require user help, etc.etc. > What do you think about my proposed sequence ? I like it, the only problem is I am unable to implement it myself :) 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 Wed Jul 30 23:18:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA07898 for hackers-outgoing; Wed, 30 Jul 1997 23:18:44 -0700 (PDT) Received: from lab321.ru (root@anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA07863 for ; Wed, 30 Jul 1997 23:18:14 -0700 (PDT) Received: from localhost (kev@localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id NAA12709; Thu, 31 Jul 1997 13:17:27 +0700 (OSD) Date: Thu, 31 Jul 1997 13:17:27 +0700 (OSD) From: Eugeny Kuzakov To: EMANUELE COSTA cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP 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, 29 Jul 1997, EMANUELE COSTA wrote: > Hi, > I'm trying to install a Sound Balster 16 PnP and I've been told > that I should search for the OSS package. Could anyone help me? > Thanks in advance, You may find OSS at http://www.4fron-tech.com Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Wed Jul 30 23:28:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08570 for hackers-outgoing; Wed, 30 Jul 1997 23:28:29 -0700 (PDT) Received: from acromail.ml.org (acroal.vip.best.com [206.86.222.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08561 for ; Wed, 30 Jul 1997 23:28:25 -0700 (PDT) Received: from localhost (kernel@localhost) by acromail.ml.org (8.8.6/8.8.5) with SMTP id XAA00689; Wed, 30 Jul 1997 23:28:43 -0700 (PDT) Date: Wed, 30 Jul 1997 23:28:43 -0700 (PDT) From: FreeBSD Technical Reader To: Charles Henrich cc: craig@gnofn.org, freebsd-hackers@FreeBSD.ORG Subject: Re: Pentium II? In-Reply-To: <199707301500.LAA01362@crh.cl.msu.edu> 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 > (currently) touch a P-II/300. Correction --- That should be: "Nothing on the planet that runs freebsd" You should take a look at WeatherbeeOS it runs on almost every piece of hardware in existence --- like tetris as an operating system (i've seen tetris run on wrist watches and wordprocessors) From owner-freebsd-hackers Wed Jul 30 23:31:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08708 for hackers-outgoing; Wed, 30 Jul 1997 23:31:21 -0700 (PDT) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08702 for ; Wed, 30 Jul 1997 23:31:15 -0700 (PDT) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.5/8.8.5) with ESMTP id IAA09669; Thu, 31 Jul 1997 08:31:05 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.6/8.8.5) id IAA05508; Thu, 31 Jul 1997 08:31:04 +0200 (CEST) To: Michael Smith Cc: boia01@castor.GEL.USherb.CA (Alex.Boisvert), chuckr@glue.umd.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: Almost JDK 1.1.2 port! References: <199707301358.XAA22566@genesis.atrad.adelaide.edu.au> From: Thomas Gellekum Date: 31 Jul 1997 08:31:03 +0200 In-Reply-To: Michael Smith's message of Wed, 30 Jul 1997 23:28:13 +0930 (CST) Message-ID: <8767tr91i0.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 19 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > > Sorry; I was in a 3.x window - you're quie correct, RTLD_LAZY isn't > documented for 2.2 >From dlopen(3) on 2.2-STABLE: RTLD_LAZY Each external function reference is resolved when the func- tion is first called. RTLD_NOW All external function references are bound immediately by dlopen(). RTLD_LAZY is normally preferred, for reasons of efficiency. However, RTLD_NOW is useful to ensure that any undefined symbols are discovered during the call to dlopen(). If dlopen() fails, it returns a null point- er, and sets an error condition which may be interrogated with dlerror(). tg From owner-freebsd-hackers Wed Jul 30 23:59:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10718 for hackers-outgoing; Wed, 30 Jul 1997 23:59:28 -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 XAA10695; Wed, 30 Jul 1997 23:59:14 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id XAA00481; Wed, 30 Jul 1997 23:58:48 -0700 (PDT) Message-Id: <199707310658.XAA00481@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: msmith@atrad.adelaide.edu.au (Michael Smith), hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Thu, 31 Jul 1997 07:00:37 +0200." <199707310500.HAA05164@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jul 1997 23:58:48 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am sure someone can volunteer a postscrip version of the document 8) Cheers, Amancio >From The Desk Of Luigi Rizzo : > > > > Save yourself some money, and start with (shudder) > > http://www.microsoft.com/hwdev/ > > too bad they only have MS Word documents (what would you expect!) > > The PnPisa document was the one I had. some time ago i tried to extract > text from it and reformat it somehow, but never printed it. In fact > the details are there, it's just that on a window you cannot see them > very well and need a printed copy. > > 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 Thu Jul 31 00:13:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11545 for hackers-outgoing; Thu, 31 Jul 1997 00:13:12 -0700 (PDT) Received: from insl1.etec.uni-karlsruhe.de (uucp@insl1.etec.uni-karlsruhe.de [129.13.109.178]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11540 for ; Thu, 31 Jul 1997 00:13:08 -0700 (PDT) Received: (from uucp@localhost) by insl1.etec.uni-karlsruhe.de (8.8.6/8.8.2) with UUCP id JAA26464 for hackers@freebsd.org; Thu, 31 Jul 1997 09:13:06 +0200 (CEST) Received: (from erb@localhost) by insl2.etec.uni-karlsruhe.de (8.8.6/8.8.2) id JAA09572; Thu, 31 Jul 1997 09:12:23 +0200 (CEST) Date: Thu, 31 Jul 1997 09:12:23 +0200 (CEST) From: Olaf Erb Message-Id: <199707310712.JAA09572@insl2.etec.uni-karlsruhe.de> To: hackers@freebsd.org Subject: Re: SCSI 1542 error Reply-To: erb@inss1.etec.uni-karlsruhe.de In-Reply-To: <199707291542.JAA12346@rocky.mt.sri.com> References: Organization: University of Karlsruhe, Germany Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199707291542.JAA12346@rocky.mt.sri.com>, Nate Williams wrote: >You're not the first. It appears to me from watching the mailing list >that the 1542 boards are not supported in 2.2. *Many* people have >reported problems with them, which unfortunately means that I can no >longer do 2.2 development at home. :( I'm running three machines with 1542B/C's, no problems at all. Just rock solid. (with 40/32/16MB) Olaf -- Argue your limitations, and sure enough, they're yours. -- Richard Bach, Illusions From owner-freebsd-hackers Thu Jul 31 00:24:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12105 for hackers-outgoing; Thu, 31 Jul 1997 00:24: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 AAA12072; Thu, 31 Jul 1997 00:23:41 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id AAA00321; Thu, 31 Jul 1997 00:22:51 -0700 (PDT) Message-Id: <199707310722.AAA00321@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: se@FreeBSD.ORG (Stefan Esser), hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Thu, 31 Jul 1997 07:07:59 +0200." <199707310507.HAA05175@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Jul 1997 00:22:51 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Luigi Rizzo : > > > > On Jul 30, Luigi Rizzo wrote: > > > HOWEVER: this relies on the PnP (or PCI for what matters) BIOS to > > > work correctly (which might be false, see at the end of the message). > > > > Well, there are **lots** of non-PnP mother boards out there > > (and I happen to own one, and for that reason I care :) > > > > Whatever solution we finally implement, we must be able to > > attach PnP boards without any help from the PnP BIOS. > > Ok, so you are calling for a more powerful configuration mechanism, > whereas I was trying to see if I could implement something much simpler > which would not require user help, etc.etc. > > > What do you think about my proposed sequence ? > > I like it, the only problem is I am unable to implement it myself :) You can . The gus pnp sub module does just that. For non-PnP boards it takes the configuration information from the config file . --- device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr --- When the driver sees the configuration information for the card it just simply overrides whatever the BIOS set the card to or in the case of a non-PnP bios it sets the card to the desired configuration. Just code up the driver as you planned and when you are done I can step in and wrap it up. Cheers, Amancio From owner-freebsd-hackers Thu Jul 31 00:40:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13349 for hackers-outgoing; Thu, 31 Jul 1997 00:40:10 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13288 for ; Thu, 31 Jul 1997 00:40:02 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id AAA09741; Thu, 31 Jul 1997 00:36:12 -0700 (PDT) From: Vinay Bannai Message-Id: <199707310736.AAA09741@agni.nuko.com> Subject: Re: Generic PCI ethernet card To: durham@w2xo.pgh.pa.us (Jim Durham) Date: Thu, 31 Jul 1997 00:36:12 -0700 (PDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <33E001D9.446B9B3D@w2xo.pgh.pa.us> from "Jim Durham" at "Jul 30, 97 11:09:13 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 Jim Durham: > I have a "generic" (read "cheap") PCI ethernet > card here that purports to be able to use the > NE2000 driver. > > I notice when I boot the system that the PCI stuff > is all OK, but, apparently, the ID code on the card > is not recognized, and no driver is assigned. The pci_configure()/pci_bus_config() in pci.c program check for the configuration registers. Baed on the bus #, device number and function associated with the device it will look up the device's probe routine from a location in its symbol table. This happens only if the device driver struct for pci is defined for this particular device and registered with DATA_SET macro. Normally if it does not find a probe() routine(because the driver is not registered with the kernel) you should still be able to see the device number, vendor id and the function number displayed (without turning on the verbose during your boot). > > Is this just a matter of adding the ID code to > the driver in if_ed_p.c, where it lists RealTek 8029, > ProLan, and etc...and I guess I have to boot the > system and see what code is returned...or am I off > on the wrong path? Also, how does the system know to > even have if_ed_p.c scan for a code if it doesn't know > what kind of card it is dealing with? Is this handed > down from the bios? Lotsa questions... > > regards, > Jim Durham Also registering the pcidevice struct with the symbol table entry corresponding to the pci devices is required before your device is completely recognised by the OS. This is done by a macro DATA_SET. Check any of the pci drivers and you will find answers to most of your questions... Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Thu Jul 31 00:45:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13749 for hackers-outgoing; Thu, 31 Jul 1997 00:45:56 -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 AAA13739 for ; Thu, 31 Jul 1997 00:45:49 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id RAA27114; Thu, 31 Jul 1997 17:15:44 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id RAA20235; Thu, 31 Jul 1997 17:15:42 +0930 (CST) Message-Id: <199707310745.RAA20235@freebie.lemis.com> Subject: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310500.HAA05164@labinfo.iet.unipi.it> from Luigi Rizzo at "Jul 31, 97 07:00:37 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 31 Jul 1997 17:15:41 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers) 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-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 Luigi Rizzo writes: >> >> Save yourself some money, and start with (shudder) >> http://www.microsoft.com/hwdev/ > > too bad they only have MS Word documents (what would you expect!) Has anybody investigated what it would take to convert MS Word to a portable format? So much stuff is sent in it nowadays, even by people who should know better. Is it that difficult? If somebody can point me to some format documentation, I'm prepared to have a hack at it. Greg From owner-freebsd-hackers Thu Jul 31 01:18:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA16364 for hackers-outgoing; Thu, 31 Jul 1997 01:18:11 -0700 (PDT) Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA16358 for ; Thu, 31 Jul 1997 01:17:54 -0700 (PDT) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.6/8.8.5) with SMTP id JAA02540; Thu, 31 Jul 1997 09:51:02 +0200 (CEST) Date: Thu, 31 Jul 1997 09:51:02 +0200 (CEST) From: Andrzej Bialecki To: spork cc: sthaug@nethelp.no, hackers@FreeBSD.ORG Subject: Re: de0 under 2.2-STABLE 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, 30 Jul 1997, spork wrote: > Thanks to all for the help... > > I'm currently using the "alternate" driver from 3am-software, and it seems > to be working great so far. I don't know how it does with 100M, because > we don't yet use it anywhere... It has alleviated the "don't unplug it or > you're hosed" problem, so I'm happy. > > Is there any reason this isn't merged into the -stable tree? > > Is there any testing I can do before I take this thing "live"? I also had many problems with de0 driver wrt. to the media switching when the cable was pulled out. I used the following kludge: I run the script, which would check every 5 minutes if I can see the router, if not - I'd do ifconfig de0 down/up to force it to check the media; if it's ok, the script would sleep the next 5 min. I know it's ugly, but it works. Sincerely yours, --- Andrzej Bialecki FreeBSD: Turning PCs Into Workstations http://www.freebsd.org Research and Academic Network in Poland From owner-freebsd-hackers Thu Jul 31 01:29:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA17360 for hackers-outgoing; Thu, 31 Jul 1997 01:29:31 -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 BAA17355 for ; Thu, 31 Jul 1997 01:29:26 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id JAA22417 for freebsd.org!hackers; Thu, 31 Jul 1997 09:12:24 +0100 (BST) From: Bob Bishop Date: Thu, 31 Jul 1997 09:11:11 +0100 Message-Id: <23781.199707310811@seagoon.gid.co.uk> To: hackers@freebsd.org Subject: Re: SCSI 1542 error Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199707291542.JAA12346@rocky.mt.sri.com>, Nate Williams wrote: >You're not the first. It appears to me from watching the mailing list >that the 1542 boards are not supported in 2.2. *Many* people have >reported problems with them, which unfortunately means that I can no >longer do 2.2 development at home. :( I've got two machines running 2.2.x on 1542CF with no problems; my -current machine runs on one too. A thought: have those reporting trouble got the transfer rate wound up on the controller? Mine are running on the defaults. From owner-freebsd-hackers Thu Jul 31 01:36:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA18215 for hackers-outgoing; Thu, 31 Jul 1997 01:36: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 BAA18200; Thu, 31 Jul 1997 01:36:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA27390; Thu, 31 Jul 1997 18:06:31 +0930 (CST) From: Michael Smith Message-Id: <199707310836.SAA27390@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI 1542 error In-Reply-To: <199707310510.WAA15704@daemonweed.reanimators.org> from Frank McConnell at "Jul 30, 97 10:10:55 pm" To: fmc@reanimators.org (Frank McConnell) Date: Thu, 31 Jul 1997 18:06:31 +0930 (CST) Cc: freebsd-scsi@FreeBSD.ORG, 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 Frank McConnell stands accused of saying: > > I noticed this the other day (similar config, 2.2.1, ISA bus, 1542CP? > with Archive changer) and have come up with what I think is a fix. > Diffs below. As a non-SCSI-god, I can't actually commit to this one. I would ask that if it's not done in the next day or two that you file a PR with this patch so that it's not lost 8) > (d) From (c), I probably have no business monkeying with this > sort of thing, and someone who knows more ought to look this over. > It lets me do chio status in addition to chio move, but that's as > far as I've tested it. Criticism is welcome. Well, this deserves some criticism; there's no other way to learn than to muck around with it, and nobody has more "business" to be monkeying with it that someone who cares about it. 8) -- ]] 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 Thu Jul 31 01:47:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA19214 for hackers-outgoing; Thu, 31 Jul 1997 01:47:15 -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 BAA19208 for ; Thu, 31 Jul 1997 01:47:07 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA27474; Thu, 31 Jul 1997 18:16:56 +0930 (CST) From: Michael Smith Message-Id: <199707310846.SAA27474@genesis.atrad.adelaide.edu.au> Subject: Re: (mainly CMOS) - howto? In-Reply-To: from Simon Shapiro at "Jul 30, 97 10:02:35 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Thu, 31 Jul 1997 18:16:56 +0930 (CST) 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 Simon Shapiro stands accused of saying: > > I need to have the followinf struct filled up with sane information. "sane" or "correct"? > Other than inb and outb to the BIOS registers, how do I get this data? > > typedef struct dpt_sysinfo { > u_int8_t drive0CMOS; /* CMOS Drive 0 Type */ > u_int8_t drive1CMOS; /* CMOS Drive 1 Type */ Uhh, are you _NUTS_? Or if you don't care, just set them to 1, or 47. > u_int8_t numDrives; /* 0040:0075 contents */ Uhm. This isn't a constant. Is '2' good enough? > u_int8_t processorFamily; /* i386 vs. Alpha, etc. */ sysctl_byname on hw.machine will tell you sys. > u_int8_t processorType; /* {3,4,5,6}86 */ There's a global cpu_class (in the kernel) which is set for this. sysctl_byname on hw.model can be used to obtain it too. > u_int8_t osMajorVersion; > u_int8_t osMinorVersion; /* The OS version */ > u_int8_t osRevision; > u_int8_t osSubRevision; Parse the results of sysctl_byname on kern.osrelease / kern.osrevision for this. Care to explain the context? It might make guessing the "right" answers a little easier 8) -- ]] 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 Thu Jul 31 02:02:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA20489 for hackers-outgoing; Thu, 31 Jul 1997 02:02:13 -0700 (PDT) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA20484 for ; Thu, 31 Jul 1997 02:02:06 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0wtr7S-000o86C; Thu, 31 Jul 97 11:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Thu, 31 Jul 1997 10:41:34 +0200 (MET DST) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@FreeBSD.ORG; Thu, 31 Jul 1997 10:34:53 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: ISDN drivers/cards In-Reply-To: <199707301904.VAA27279@bitbox.follo.net> from Eivind Eklund at "Jul 30, 97 09:04:51 pm" To: perhaps@yes.no (Eivind Eklund) Date: Thu, 31 Jul 1997 10:34:53 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.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 Eivind Eklund wrote: > [...] (Yeah, I know of the bISDN people, but nothing seems to be > happening there; besides, they have already got hardware, it seems.) Just for the record: i'm currently working on a new ISDN stack which will replace BISDN. Its much more modular and coded exactly as the specs want it. Layer 1 (I.430) runs and currently supports Siemens ISDN chipsets, Layer 2 (Q.921) runs and Layer 3 (currently only Q.931) also runs. Right now i'm working on getting the various B-channel protocols up and running and to make shure, future development of active (CAPI equipped) ISDN cards (i've got some which also support the US protocols) will fit in this model. I expect to have something ready which can be given out for alpha test by the end of the year or in the first quarter of 1998. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe There is a difference between an open mind and a hole in the head From owner-freebsd-hackers Thu Jul 31 02:22:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA21934 for hackers-outgoing; Thu, 31 Jul 1997 02:22:36 -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 CAA21927 for ; Thu, 31 Jul 1997 02:22:31 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.6/8.7.3) id LAA00130; Thu, 31 Jul 1997 11:22:24 +0200 (MEST) From: Søren Schmidt Message-Id: <199707310922.LAA00130@sos.freebsd.dk> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310745.RAA20235@freebie.lemis.com> from Greg Lehey at "Jul 31, 97 05:15:41 pm" To: grog@lemis.com (Greg Lehey) Date: Thu, 31 Jul 1997 11:22:24 +0200 (MEST) Cc: luigi@labinfo.iet.unipi.it, 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: > Luigi Rizzo writes: > >> > >> Save yourself some money, and start with (shudder) > >> http://www.microsoft.com/hwdev/ > > > > too bad they only have MS Word documents (what would you expect!) > > Has anybody investigated what it would take to convert MS Word to a > portable format? So much stuff is sent in it nowadays, even by people > who should know better. Is it that difficult? If somebody can point > me to some format documentation, I'm prepared to have a hack at it. I use StarDivision StarOffice packet, it reads word6 docs and writes it in almost anything, it has a little problems with word7 but it can be used. You then get a nice Office packet as a sideeffect :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Jul 31 02:25:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA22176 for hackers-outgoing; Thu, 31 Jul 1997 02:25:20 -0700 (PDT) Received: from polya.blah.org (slmel56p09.ozemail.com.au [203.108.203.185]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22171 for ; Thu, 31 Jul 1997 02:25:15 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.6/8.8.5) id TAA08099 for hackers@freebsd.org; Thu, 31 Jul 1997 19:25:12 +1000 (EST) From: Ada T Lim Message-Id: <199707310925.TAA08099@polya.blah.org> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310745.RAA20235@freebie.lemis.com> from Greg Lehey at "Jul 31, 97 05:15:41 pm" To: hackers@freebsd.org Date: Thu, 31 Jul 1997 19:25:12 +1000 (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 > Has anybody investigated what it would take to convert MS Word to a > portable format? So much stuff is sent in it nowadays, even by people > who should know better. Is it that difficult? If somebody can point > me to some format documentation, I'm prepared to have a hack at it. If you _really_ need to read word files, StarOffice (in the ports collection) will do in a pinch. I think there's something out there that converts word to rtf, and I know there's rtf->html Ada From owner-freebsd-hackers Thu Jul 31 02:33:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA22600 for hackers-outgoing; Thu, 31 Jul 1997 02:33:56 -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 CAA22588 for ; Thu, 31 Jul 1997 02:33:53 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id CAA00327; Thu, 31 Jul 1997 02:31:57 -0700 (PDT) Message-Id: <199707310931.CAA00327@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Eugeny Kuzakov cc: EMANUELE COSTA , freebsd-hackers@FreeBSD.ORG Subject: Re: Sound Blaster 16 PnP In-reply-to: Your message of "Thu, 31 Jul 1997 13:17:27 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Jul 1997 02:31:57 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Could you please re-direct such requests in the future to the multimedia group. Thank You, Amancio >From The Desk Of Eugeny Kuzakov : > On Tue, 29 Jul 1997, EMANUELE COSTA wrote: > > > Hi, > > I'm trying to install a Sound Balster 16 PnP and I've been told > > that I should search for the OSS package. Could anyone help me? > > Thanks in advance, > You may find OSS at http://www.4fron-tech.com > > > Best wishes, Eugeny Kuzakov > Laboratory 321 ( Omsk, Russia ) > kev@lab321.ru > > From owner-freebsd-hackers Thu Jul 31 02:41:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23167 for hackers-outgoing; Thu, 31 Jul 1997 02:41:02 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA23150 for ; Thu, 31 Jul 1997 02:40:54 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id EAA27604; Thu, 31 Jul 1997 04:40:11 -0500 (CDT) Date: Thu, 31 Jul 1997 04:40:11 -0500 (CDT) From: Craig Johnston To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: Pentium II? In-Reply-To: <199707301500.LAA01362@crh.cl.msu.edu> 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, 30 Jul 1997, Charles Henrich wrote: > > >The real issue is that the PII is untried, whereas FreeBSD systems > >on PPro hardware, like ftp.cdrom.com (which serves 2000 simultaneous > >ftp users) have been ticking along reliably for quite some time > processors together, and I dont give a rip what the connection is. I require > performance for my apps, and there's nothing on the planet that will > (currently) touch a P-II/300. Digital might beg to differ. -Craig From owner-freebsd-hackers Thu Jul 31 02:47:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23508 for hackers-outgoing; Thu, 31 Jul 1997 02:47:29 -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 CAA23477; Thu, 31 Jul 1997 02:47:12 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA05418; Thu, 31 Jul 1997 10:46:36 +0200 From: Luigi Rizzo Message-Id: <199707310846.KAA05418@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 31 Jul 1997 10:46:36 +0200 (MET DST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707310658.XAA00481@rah.star-gate.com> from "Amancio Hasty" at Jul 30, 97 11:58:29 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am sure someone can volunteer a postscrip version of the document 8) Could someone comment on the copyright issues ? Many docs on the net say explicitly that you (and everybody else) can make your own copy, but you cannot redistribute them without explicit authorization. Of course this is the most stupid restriction they can put, but go and convince these people... Clearly things are different if someone ships me a postscript copy of the file, or if someone sells a CD with all the docs found on the net. The copyright should at least try to make a difference between the two cases. In any cases this is a real shame. As I told amancio, I have collected quite a few data sheets (many in PDF format) about the PC hardware, and it would be great if future freebsd distributions could include those files on the CD. Perhaps I have to talk to Jordan about this and see what he can do... Apart from FreeBSD: here at the university, students are trying to produce a CD with didactic matherial, and this would include data sheets of sample hardware devices, if there were not such stupid restrictions. The last time I tried to get a written authorization from various manufacturers, all of them said "of course you can make copies of the data sheets and distribute them to students, but it is a problem for us to put this in writing..." 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 Thu Jul 31 02:57:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA24225 for hackers-outgoing; Thu, 31 Jul 1997 02:57:57 -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 CAA24159; Thu, 31 Jul 1997 02:57:06 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA05446; Thu, 31 Jul 1997 10:57:09 +0200 From: Luigi Rizzo Message-Id: <199707310857.KAA05446@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 31 Jul 1997 10:57:09 +0200 (MET DST) Cc: se@FreeBSD.ORG, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707310722.AAA00321@rah.star-gate.com> from "Amancio Hasty" at Jul 31, 97 00:22:32 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Whatever solution we finally implement, we must be able to > > > attach PnP boards without any help from the PnP BIOS. > > > > Ok, so you are calling for a more powerful configuration mechanism, ... > > > What do you think about my proposed sequence ? > > > > I like it, the only problem is I am unable to implement it myself :) > > You can . The gus pnp sub module does just that. For non-PnP > boards it takes the configuration information from the config > file . > --- > device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr > --- > When the driver sees the configuration information for the card > it just simply overrides whatever the BIOS set the card to or honestly, I would call that a quick hack, not a general configuration mechanism. Especially because I plan to support more than one sound card, and the PnP cards would show up as pcm1, pcm2, ... I think I will look at the userconfig stuff and see if changes are not too hard to implement... Cheers Luigi From owner-freebsd-hackers Thu Jul 31 03:07:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA24687 for hackers-outgoing; Thu, 31 Jul 1997 03:07:50 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA24678 for ; Thu, 31 Jul 1997 03:07:43 -0700 (PDT) Received: from sparkie.gnofn.org (sparkie.gnofn.org [206.27.168.35]) by sparkie.gnofn.org (8.7.Beta.10/8.7.Beta.10) with SMTP id FAA28200; Thu, 31 Jul 1997 05:06:51 -0500 (CDT) Date: Thu, 31 Jul 1997 05:06:51 -0500 (CDT) From: Craig Johnston To: FreeBSD Mailing List cc: Howard Lew , hackers@FreeBSD.ORG Subject: Re: Pentium II? 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, 30 Jul 1997, FreeBSD Mailing List wrote: > We have also been evaluating a *jumperless* motherboard manufactrued by > ABIT. It seems really nice at first; the bus frequency, multiplier, and > voltage are all set in the BIOS. It gives options for 50,55,60,66,75 and > 83MHz, with multipliers up to 5.5X. The only, and major, downfall is that > you CAN NOT OVERCLOCK! How silly is that? As soon as you exceed spec, it Huh? Don't tell mine! I clock my IT5H's bus at 83 Mhz and the multiplier at 1.5 using a K5-PR166. I also run it at 75 * 1.75 (needs extra volts). I prefer the 83Mhz setting, although the CPU clock speed (125ish) is actually slower than the 133 or so of the 75*1.75 setup. > either auto-resets the values or runs unreliably. I couldn't even squeak > 187.5MHZ out of a K6-166... It amazes me that the board can actually tell > the difference. There is a "safety feature" involving the settings going away if the machine is reset quickly more than once, or something to that effect, and I think it causes flakiness. I do find that I will come up at the correct speed when I set the speed in CPU softmenu and then exit and continue booting. Once you're sure your speed works, setting "speed error hold" to "disable" under CPU softmenu seems to help. If your setting won't boot, try more voltage, it often helps. > Pentiums also had similar results. I know the "hobbyist" would get a bit > frustrated. This is actually a favorite board of overclockers, and many are overclocking K6s in them. Play with it some more and if you can't get even mediocre OCing results, you may have flaky hardware. regards, Craig From owner-freebsd-hackers Thu Jul 31 03:11:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA24923 for hackers-outgoing; Thu, 31 Jul 1997 03:11:02 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA24912 for ; Thu, 31 Jul 1997 03:10:53 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id NAA08676; Thu, 31 Jul 1997 13:08:33 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Thu, 31 Jul 1997 13:08:32 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Ada T Lim cc: hackers@FreeBSD.ORG Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310925.TAA08099@polya.blah.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 On Thu, 31 Jul 1997, Ada T Lim wrote: > > Has anybody investigated what it would take to convert MS Word to a > > portable format? So much stuff is sent in it nowadays, even by people > > who should know better. Is it that difficult? If somebody can point > > me to some format documentation, I'm prepared to have a hack at it. > > If you _really_ need to read word files, StarOffice (in the ports collection) > will do in a pinch. > > I think there's something out there that converts word to rtf, and I know > there's rtf->html There's also an rtf->LaTeX converter in the ports. Haven't put it to heavy use, but it may be worth a try too. > > Ada > Nadav From owner-freebsd-hackers Thu Jul 31 03:11:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA24951 for hackers-outgoing; Thu, 31 Jul 1997 03:11:09 -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 DAA24909; Thu, 31 Jul 1997 03:10:49 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id DAA05428; Thu, 31 Jul 1997 03:08:45 -0700 (PDT) Message-Id: <199707311008.DAA05428@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: se@FreeBSD.ORG, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Advice sought on PnP configuration In-reply-to: Your message of "Thu, 31 Jul 1997 10:57:09 +0200." <199707310857.KAA05446@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Jul 1997 03:08:45 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Yes, it is a quick hack and it is also a manual mechanism to override very intelligent algorithms;additionally, is not and all encompassing solution and one that will allow us to get the stuff out soon *safely*. Most likely for any intellingent PnP subsystem we will have to support Did the last PnP configuration failed?, plug, remember, pray dear lord that the system does not reboot or gets hung. Cheers, Amancio >From The Desk Of Luigi Rizzo : > > > > Whatever solution we finally implement, we must be able to > > > > attach PnP boards without any help from the PnP BIOS. > > > > > > Ok, so you are calling for a more powerful configuration mechanism, > ... > > > > What do you think about my proposed sequence ? > > > > > > I like it, the only problem is I am unable to implement it myself :) > > > > You can . The gus pnp sub module does just that. For non-PnP > > boards it takes the configuration information from the config > > file . > > --- > > device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr > > --- > > When the driver sees the configuration information for the card > > it just simply overrides whatever the BIOS set the card to or > > honestly, I would call that a quick hack, not a general configuration > mechanism. Especially because I plan to support more than one sound > card, and the PnP cards would show up as pcm1, pcm2, ... > > I think I will look at the userconfig stuff and see if changes are > not too hard to implement... > > Cheers > Luigi From owner-freebsd-hackers Thu Jul 31 03:18:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA25452 for hackers-outgoing; Thu, 31 Jul 1997 03:18: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 DAA25447 for ; Thu, 31 Jul 1997 03:18:13 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id DAA05496; Thu, 31 Jul 1997 03:17:46 -0700 (PDT) Message-Id: <199707311017.DAA05496@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Greg Lehey cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo), hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-reply-to: Your message of "Thu, 31 Jul 1997 17:15:41 +0930." <199707310745.RAA20235@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Jul 1997 03:17:46 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am pretty sure that StarOffice can read word documents but not word documents from Office97. Cheers, Amancio >From The Desk Of Greg Lehey : > Luigi Rizzo writes: > >> > >> Save yourself some money, and start with (shudder) > >> http://www.microsoft.com/hwdev/ > > > > too bad they only have MS Word documents (what would you expect!) > > Has anybody investigated what it would take to convert MS Word to a > portable format? So much stuff is sent in it nowadays, even by people > who should know better. Is it that difficult? If somebody can point > me to some format documentation, I'm prepared to have a hack at it. > > Greg > > From owner-freebsd-hackers Thu Jul 31 03:48:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA27339 for hackers-outgoing; Thu, 31 Jul 1997 03:48:30 -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 DAA27333 for ; Thu, 31 Jul 1997 03:48:24 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 4232 on Thu, 31 Jul 1997 10:48:05 GMT; id KAA04232 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id MAA20133; Thu, 31 Jul 1997 12:47:07 +0200 (MET DST) Message-Id: <199707311047.MAA20133@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: Greg Lehey cc: luigi@labinfo.iet.unipi.it (Luigi Rizzo), hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-reply-to: grog's message of Thu, 31 Jul 1997 17:15:41 +0930. <199707310745.RAA20235@freebie.lemis.com> Reply-to: marc@bowtie.nl Date: Thu, 31 Jul 1997 12:47:07 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There is a little utility, word2x, that will convert most word documents to readable ascii, or tex. don't have an url, but search for word2x Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Thu Jul 31 04:34:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA00548 for hackers-outgoing; Thu, 31 Jul 1997 04:34:15 -0700 (PDT) Received: from tenuki.honte.es ([195.53.15.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA00500 for ; Thu, 31 Jul 1997 04:33:57 -0700 (PDT) Received: (from root@localhost) by tenuki.honte.es (8.8.5/8.8.5) id NAA25146 for hackers@freebsd.org; Thu, 31 Jul 1997 13:33:19 +0200 (MET DST) Date: Thu, 31 Jul 1997 13:33:19 +0200 (MET DST) From: Garey Mills Message-Id: <199707311133.NAA25146@tenuki.honte.es> To: hackers@freebsd.org Subject: advice on porting Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello - I am looking at trying to port Toba, the University of Arizona's Java to C compiler. There are several versions, one for Linux and one for Solaris. Which would be the best base for porting? Is there anything written on porting issues in general? Thanks for any help; Garey Mills From owner-freebsd-hackers Thu Jul 31 04:34:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA00597 for hackers-outgoing; Thu, 31 Jul 1997 04:34:29 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA00580 for ; Thu, 31 Jul 1997 04:34:23 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-6.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA15494 (5.67b/IDA-1.5 for ); Thu, 31 Jul 1997 13:33:50 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id NAA14572; Thu, 31 Jul 1997 13:33:40 +0200 (CEST) X-Face: " Date: Thu, 31 Jul 1997 13:33:40 +0200 From: Stefan Esser To: Jim Durham Cc: hackers@FreeBSD.ORG Subject: Re: Generic PCI ethernet card References: <33E001D9.446B9B3D@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <33E001D9.446B9B3D@w2xo.pgh.pa.us>; from Jim Durham on Wed, Jul 30, 1997 at 11:09:13PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 30, Jim Durham wrote: > I have a "generic" (read "cheap") PCI ethernet > card here that purports to be able to use the > NE2000 driver. > > I notice when I boot the system that the PCI stuff > is all OK, but, apparently, the ID code on the card > is not recognized, and no driver is assigned. > > Is this just a matter of adding the ID code to > the driver in if_ed_p.c, where it lists RealTek 8029, > ProLan, and etc...and I guess I have to boot the > system and see what code is returned...or am I off > on the wrong path? Also, how does the system know to > even have if_ed_p.c scan for a code if it doesn't know > what kind of card it is dealing with? Is this handed > down from the bios? Lotsa questions... Please send a boot message log and information on the name the card is sold under. I'll send a patch and will add the device ID to -current. For the -current PCI code I plan to allow assigning drivers to PCI devices that could not be identified. (I.e. your card would show up in the user config screen with a "no driver" flag, and you could assign "ed" to it, or, say, "ed4" if you care for the unit number.) Regards, STefan From owner-freebsd-hackers Thu Jul 31 04:42:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA01418 for hackers-outgoing; Thu, 31 Jul 1997 04:42:50 -0700 (PDT) Received: from ns.cs.msu.su (laskavy@redsun.cs.msu.su [158.250.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA01411 for ; Thu, 31 Jul 1997 04:42:44 -0700 (PDT) Received: (from laskavy@localhost) by ns.cs.msu.su (8.8.6/8.6.12) id PAA02696; Thu, 31 Jul 1997 15:42:43 +0400 (DST) Date: Thu, 31 Jul 1997 15:42:43 +0400 (DST) Message-Id: <199707311142.PAA02696@ns.cs.msu.su> From: "Sergei S. Laskavy" To: grog@lemis.com CC: luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-reply-to: <199707310745.RAA20235@freebie.lemis.com> (message from Greg Lehey on Thu, 31 Jul 1997 17:15:41 +0930 (CST)) Subject: Re: MS Word documents (was: Advice sought on PnP configuration) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>> "Greg" == Greg Lehey writes: Greg> Luigi Rizzo writes: >>> Save yourself some money, and start with (shudder) >>> http://www.microsoft.com/hwdev/ >> too bad they only have MS Word documents (what would you >> expect!) Greg> Has anybody investigated what it would take to convert MS Greg> Word to a portable format? So much stuff is sent in it Greg> nowadays, even by people who should know better. Is it that Greg> difficult? If somebody can point me to some format Greg> documentation, I'm prepared to have a hack at it. Here is a small proggy. I found it in $HOME of one user. He said that author unknown... It works for me for some DOCs and prints garbadge for other. Maybe, this can help. ------------------------------------------------------------------------ /* catdoc.c version 0.3 */ #include #include #include #define TEXT_WIDTH 72 /* #define LATIN1 */ /* enable this define, if you don't want cyrillic code page translations */ unsigned char specs[]={7, /* tab columns separator - handled specially*/ '\n',/* hook to handle end of line in tables */ 0x1E,/* unbreakable defis */ 0x1F,/* soft hyphen */ 0x85,/* dots */ 0x91,/* opening single quote */ 0x92,/* closing single quote */ 0x93,/* opening double quote */ 0x94,/* closing double quote */ 0x96,/* em-dash (or em-space)*/ 0x97,/* en-dash */ 0x99,/* Trade Mark sign */ 0xA0,/* unbreakable space */ 0xA9,/* Copyright sign */ 0xAE,/* Reserved sign */ 0xAB,/* opening << quote*/ 0xBB,/* closing >> quote*/ /* The rest is translated into itself unless TeX mode is selected */ '%','$','_','{','}','\\', }; char *ascii_specs[]={"\t","\n","-","","...","`","'","``","''","-","-","tm", " ","(c)","(R)","\"","\"","%","$","_","{","}","\\"}; char *TeX_specs[]={"\t&","\\\\\n","-","\\-","\\dots{}","`","'","``","''","---","--", "${}^{\\scriptscriptstyle\\mathrm{TM}}$",/* this is my idea about tm sign*/ "~", "{\\copyright}", "(R)",/* to be replaced with correct command */ "<",">","\\%","\\$","$\\{$","$\\}$","$\\backslash$",}; #ifndef LATIN1 #ifdef unix unsigned char table[256]={ /* Windows cyrillic code page to KOI-8 */ 0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0A,0x0D,0x0C,0x0D,0x0E,0x0F, 0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1A,0x1B,0x1C,0x1D,0x2D,0x20, 0x20,0x21,0x22,0x23,0x24,0x25,0x26,0x27,0x28,0x29,0x2A,0x2B,0x2C,0x2D,0x2E,0x2F, 0x30,0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,0x39,0x3A,0x3B,0x3C,0x3D,0x3E,0x3F, 0x40,0x41,0x42,0x43,0x44,0x45,0x46,0x47,0x48,0x49,0x4A,0x4B,0x4C,0x4D,0x4E,0x4F, 0x50,0x51,0x52,0x53,0x54,0x55,0x56,0x57,0x58,0x59,0x5A,0x5B,0x5C,0x5D,0x5E,0x5F, 0x60,0x61,0x62,0x63,0x64,0x65,0x66,0x67,0x68,0x69,0x6A,0x6B,0x6C,0x6D,0x6E,0x6F, 0x70,0x71,0x72,0x73,0x74,0x75,0x76,0x77,0x78,0x79,0x7A,0x7B,0x7C,0x7D,0x7E,0x7F, 0x80,0x81,0x82,0xAA,0x8F,0x90,0xA9,0x93,0x84,0x92,0x91,0x94,0x83,0x95,0x99,0x8B, 0x98,0x60,0x27,0x22,0x22,0x9A,0x2D,0x2D,0x9E,0xA6,0x87,0xB0,0x8D,0x97,0x86,0xA2, 0x20,0xA7,0xA5,0x88,0xA4,0x8E,0x96,0x85,0xB3,0xA1,0x9F,0x22,0xAB,0xAC,0xAD,0xAE, 0xAF,0xB2,0xB1,'i',0xB5,0xB6,0xB7,0xB8,0xA3,0xB9,0xBA,0x22,0xBC,0xBD,0xBE,0x9B, 0xE1,0xE2,0xF7,0xE7,0xE4,0xE5,0xF6,0xFA,0xE9,0xEA,0xEB,0xEC,0xED,0xEE,0xEF,0xF0, 0xF2,0xF3,0xF4,0xF5,0xE6,0xE8,0xE3,0xFE,0xFB,0xFD,0xFF,0xF9,0xF8,0xFC,0xE0,0xF1, 0xC1,0xC2,0xD7,0xC7,0xC4,0xC5,0xD6,0xDA,0xC9,0xCA,0xCB,0xCC,0xCD,0xCE,0xCF,0xD0, 0xD2,0xD3,0xD4,0xD5,0xC6,0xC8,0xC3,0xDE,0xDB,0xDD,0xDF,0xD9,0xD8,0xDC,0xC0,0xD1}; #else unsigned char table[256]={ 0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x0a,0x0D,0x0c,0x0d,0x0e,0x0f, 0x10,0x11,0x12,0x13,0x14,0x15,0x16,0x17,0x18,0x19,0x1a,0x1b,0x1c,0x1d,0x2D,0x20, 0x20,0x21,0x22,0x23,0x24,0x25,0x26,0x27,0x28,0x29,0x2a,0x2b,0x2c,0x2d,0x2e,0x2f, 0x30,0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,0x39,0x3a,0x3b,0x3c,0x3d,0x3e,0x3f, 0x40,0x41,0x42,0x43,0x44,0x45,0x46,0x47,0x48,0x49,0x4a,0x4b,0x4c,0x4d,0x4e,0x4f, 0x50,0x51,0x52,0x53,0x54,0x55,0x56,0x57,0x58,0x59,0x5a,0x5b,0x5c,0x5d,0x5e,0x5f, 0x60,0x61,0x62,0x63,0x64,0x65,0x66,0x67,0x68,0x69,0x6a,0x6b,0x6c,0x6d,0x6e,0x6f, 0x70,0x71,0x72,0x73,0x74,0x75,0x76,0x77,0x78,0x79,0x7a,0x7b,0x7c,0x7d,0x7e,0x7f, 0x80,0x81,0x82,0x83,0x84,0x85,0x86,0x87,0x88,0x89,0x8a,0x8b,0x8c,0x8d,0x8e,0x8f, 0x90,0x60,0x27,0x22,0x22,0x95,0x2D,0x2D,0x98,0x99,0x9a,0x9b,0x9c,0x9d,0x9e,0x9f, 0x20,0xa1,0xa2,0xa3,0xa4,0xa5,0xa6,0xa7,0xa8,0xa9,0xaa,0x22,0xac,0xad,0xae,0xaf, 0xb0,0xb1,0xb2,0xb3,'i',0xb5,0xb6,0xb7,0xb8,0xb9,0xba,0x22,0xbc,0xbd,0xbe,0xbf, 0x80,0x81,0x82,0x83,0x84,0x85,0x86,0x87,0x88,0x89,0x8a,0x8b,0x8c,0x8d,0x8e,0x8f, 0x90,0x91,0x92,0x93,0x94,0x95,0x96,0x97,0x98,0x99,0x9a,0x9b,0x9c,0x9d,0x9e,0x9f, 0xa0,0xa1,0xa2,0xa3,0xa4,0xa5,0xa6,0xa7,0xa8,0xa9,0xaa,0xab,0xac,0xad,0xae,0xaf, 0xe0,0xe1,0xe2,0xe3,0xe4,0xe5,0xe6,0xe7,0xe8,0xe9,0xea,0xeb,0xec,0xed,0xee,0xef}; #endif #define recode_char(x) table[x] #else #define recode_char(x) x #endif char *map_char(char **map,int c) {unsigned char *ptr; static char buffer[2]="a"; if ((ptr=strchr(specs,c))) return map[ptr-specs]; else { buffer[0]=recode_char(c); return buffer; } } void format(char *buf,char **map) { unsigned char outstring[128]=""; unsigned char *sp=buf,*dp;int table=0; while (*sp) { if (*sp==7&&table) { printf("%s%s",outstring,map_char(map,'\n')); outstring[0]=0; table=0;sp++; } else { if (strlen(strcat(outstring,map_char(map,*sp)))>TEXT_WIDTH) { dp=strrchr(outstring,' '); if (dp) { *(dp++)=0; printf("%s\n",outstring); strcpy(outstring,dp); } else { int i; for(i=0;i<72;i++) putc(outstring[i],stdout); putc('\n',stdout); strcpy(outstring,outstring+72); } } table=*(sp++)==7; } } if (outstring[0]==0) putc('\n',stdout); else printf("%s\n\n",outstring); } void help(void) { printf("catdoc - exctract text from MS-Word files and catenate it to stdout\n" "Copyright (c) by Victor B. Wagner, 1996\n" "Usage catdoc [-ast] files ...\n" "\t-a - converts non-standard printable chars into readable form (default)\n" "\t-t - converts them into TeX control sequences\n" "\t-s - exits with code 1 if MSWordDoc signature not found before\n" "\t\tfirst printable paragraph\n\n" "All options affects only files, specified AFTER them\n"); exit(2); } char buf[8192]; void do_file(FILE *f,char **map,int search_sign) { int ok=!search_sign; int bufptr,c; while(!feof(f)) {bufptr=-1; do { c=getc(f); /* Special printable symbols 7- table separator \r - paragraph end 0x1E - short defis */ if ((c<=255&&c>=32)||c==7||c=='\t'||c=='\r'||c==0x1E) buf[++bufptr]=c; else if (c==0x0b) buf[++bufptr]='\r'; else { if (!c) {buf[++bufptr]=0; if(!strcmp(buf,"MSWordDoc")) { ok=1; } } if (c!=2) bufptr=-1;/* \002 is Word's footnote mark */ } } while (c!='\r'&&c!=EOF); if (bufptr>0&&buf[bufptr]=='\r') { if (!ok) exit( 1); buf[bufptr]=0; format(buf,map); } } } int main(int argc,char **argv) { int search_sign =0; /* Must program exit with exit code 1 if MSWordDoc signature is not found? */ char **sequences=ascii_specs;/* pointer to array of character sequences to represent special characters of Word */ int i=1,stdin_processed=0; if (argc<2) help(); for(;i Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA02791 for hackers-outgoing; Thu, 31 Jul 1997 05:07: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 FAA02785 for ; Thu, 31 Jul 1997 05:07:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id VAA28144; Thu, 31 Jul 1997 21:37:28 +0930 (CST) From: Michael Smith Message-Id: <199707311207.VAA28144@genesis.atrad.adelaide.edu.au> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310925.TAA08099@polya.blah.org> from Ada T Lim at "Jul 31, 97 07:25:12 pm" To: ada@not-enough.bandwidth.org (Ada T Lim) Date: Thu, 31 Jul 1997 21:37:27 +0930 (CST) Cc: 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 Ada T Lim stands accused of saying: > > Has anybody investigated what it would take to convert MS Word to a > > portable format? So much stuff is sent in it nowadays, even by people > > who should know better. Is it that difficult? If somebody can point > > me to some format documentation, I'm prepared to have a hack at it. > > If you _really_ need to read word files, StarOffice (in the ports collection) > will do in a pinch. Unfortunately (and to my significant disappointment) this is not the case. All of the Microsoft-sourced Word documents I have met cannot be opened by StarOffice. Oddly, those from many other vendors (eg. Compaq, Intel, etc.) can. > I think there's something out there that converts word to rtf, and I know > there's rtf->html Word itself will save in RTF format, but true to their traditions Microsoft's RTF output is sufficiently mutant that I haven't found anything (yet) that will swallow it reliably. Note that neither of these problems tend to show up with short documents, but in the case of these specifications we're usually talking > 50 pages. To answer Grog's question; there was a discussion of this very issue a while back here, and the upshot was that the one individual that had come close to deciphering the Word document format was sat on by Microsoft's lawyers. There is apparently some documentation somewhere (ref Terry, IIRC) which might allow you to read Word documents, but at the cost of your mortal soul. -- ]] 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 Thu Jul 31 05:26:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA03852 for hackers-outgoing; Thu, 31 Jul 1997 05:26:07 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA03847 for ; Thu, 31 Jul 1997 05:26:02 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id IAA00364 for hackers@freebsd.org; Thu, 31 Jul 1997 08:25:55 -0400 (EDT) Date: Thu, 31 Jul 1997 08:25:55 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707311225.IAA00364@pandora.hh.kew.com> To: hackers@freebsd.org Subject: Upgrade 2.2.1 --> 2.2.2 broke su? Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Login with s/key works, but su to root does not since I moved from 2.2.1 to 2.2.2 last weekend. Suggestions as to how I blew the upgrade? I've rebuilt/reinstalled both lib and the su command ... su root -c exec tcsh Password: (turning echo on) Password:GAD THEN FEED OIL ANT FILM (null): Undefined symbol "_MD4Init" called from su:/usr/lib/libskey.so.2.0 at 0x8025214 -- Drew Derbyshire Internet: ahd@kew.com Kendra Electronic Wonderworks Telephone: 617-279-9812 "If I had it all to do over again, I'd spell creat with an 'e'." - Brian Kernighan From owner-freebsd-hackers Thu Jul 31 06:46:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA09458 for hackers-outgoing; Thu, 31 Jul 1997 06:46:38 -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 GAA09422; Thu, 31 Jul 1997 06:46:22 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA05722; Thu, 31 Jul 1997 14:46:17 +0200 From: Luigi Rizzo Message-Id: <199707311246.OAA05722@labinfo.iet.unipi.it> Subject: Re: Advice sought on PnP configuration To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 31 Jul 1997 14:46:17 +0200 (MET DST) Cc: se@FreeBSD.ORG, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG In-Reply-To: <199707311008.DAA05428@rah.star-gate.com> from "Amancio Hasty" at Jul 31, 97 03:08:26 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yes, it is a quick hack and it is also a manual mechanism to override > very intelligent algorithms;additionally, is not and all encompassing > solution and one that will allow us to get the stuff out soon *safely*. As a matter of fact I do like this approach and have done (and/or planned) something very similar to test my cards. However I would go a step further and use some bits in the "flags" field to say things like - do not use this entry to configure a plain isa device; rather, use it for the i-th PnP device which matches card type TT i.e. something like #standard entry for isa devices device pcm0 at isa? port 0x220 irq 11 drq 5 flags 0x17 # || # use dual dma channel ----------'| * secondary dma channel -----------' # #special entry for PnP device device pcm1 at isa? port 0x604 irq 7 drq 1 flags 0x10TT10 # |||||| # special entry for PnP ----------'||||| # use it for device 0 -----------'|||| # matching type TT ------------''|| # use two dma channels --------------'| # secondary dma is 0 ---------------' The device type TT is a unique identifier associated with the card and presumably returned by the PnP probe code in the kernel. I have almost all of this (including the device type) implemented in my code. Note however that not always things are so simple. Some (many) PnP cards use multiple address ranges, some of which might not be associated with any particular function. An example, the OPTi931 (I have two here and plan to support them rsn) has a block of addresses used for configuration purposes and not associated with any I/O. Conclusion: the manual override mechanism is surely needed, the problem is that there are not enough bits in the config line to specify the desired ranges. Maybe we can modify "config" to allow a syntax like device pnp0 id "CSC4236" config "io 0x604 0x300 0x200 mem 0x300 irq 6 dma 5 6" device pnp1 id "OPT9310" config "io 0x530 0x330 irq 7 dma 5 6" ... Cheers Luigi From owner-freebsd-hackers Thu Jul 31 06:53:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA10058 for hackers-outgoing; Thu, 31 Jul 1997 06:53:21 -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 GAA10053 for ; Thu, 31 Jul 1997 06:53:17 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 17167 on Thu, 31 Jul 1997 13:52:59 GMT; id NAA17167 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id PAA23341; Thu, 31 Jul 1997 15:50:31 +0200 (MET DST) Message-Id: <199707311350.PAA23341@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: Michael Smith cc: ada@not-enough.bandwidth.org (Ada T Lim), hackers@FreeBSD.ORG Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-reply-to: msmith's message of Thu, 31 Jul 1997 21:37:27 +0930. <199707311207.VAA28144@genesis.atrad.adelaide.edu.au> Reply-to: marc@bowtie.nl Date: Thu, 31 Jul 1997 15:50:30 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > To answer Grog's question; there was a discussion of this very issue a > while back here, and the upshot was that the one individual that had > come close to deciphering the Word document format was sat on by > Microsoft's lawyers. There is apparently some documentation somewhere > (ref Terry, IIRC) which might allow you to read Word documents, but at > the cost of your mortal soul. > I remembered saving a reference... http://wwwwbs.cs.tu-berlin.de/~schwartz/pmh/ It has a sort of description of the word 6.0 document format. Marc. > -- > ]] 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 [[ ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Thu Jul 31 07:32:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA12097 for hackers-outgoing; Thu, 31 Jul 1997 07:32:50 -0700 (PDT) Received: from geotech.pauir.itb.ac.id (geotech.pauir.ITB.ac.id [167.205.22.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA12073 for ; Thu, 31 Jul 1997 07:32:32 -0700 (PDT) Received: (from ari@localhost) by geotech.pauir.itb.ac.id (8.8.5/8.8.5) id VAA08516; Thu, 31 Jul 1997 21:33:24 +0700 (JVT) Date: Thu, 31 Jul 1997 21:33:24 +0700 (JVT) From: Ari Noviandi cc: hackers@FreeBSD.ORG Subject: Re: PCMCIA on FreeBSD2.2.1 In-Reply-To: <199707292233.QAA01449@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 unsubscribe From owner-freebsd-hackers Thu Jul 31 07:45:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA12756 for hackers-outgoing; Thu, 31 Jul 1997 07:45:41 -0700 (PDT) Received: from eurogate.nortel.co.uk (eurogate.nortel.co.uk [192.100.101.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA12713 for ; Thu, 31 Jul 1997 07:44:31 -0700 (PDT) Received: from hedera.bnr.co.uk (actually eharg1e1.nortel.co.uk) by eurogate.nortel.co.uk with SMTP (PP); Thu, 31 Jul 1997 14:00:52 +0000 Received: from bhars8cd.europe.nortel.com by hedera.bnr.co.uk with SMTP (PP); Thu, 31 Jul 1997 14:00:20 +0000 Received: from bharh4d4.europe.nortel.com by bhars8cd.europe.nortel.com (5.61++/UK-2.1-MX-nortel-(19970425)) with SMTP id AA03075; Thu, 31 Jul 97 15:00:11 +0100 Date: Thu, 31 Jul 1997 14:58:19 +0100 (BST) From: "Andy J. Smith" X-Sender: ajsmith@bharh4d4.europe.nortel.com To: "Daniel M. Eischen" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cross compiling for FreeBSD 3.0 In-Reply-To: <199707301555.KAA18490@iworks.InterWorks.org> Message-Id: Organisation: Nortel Technology Ltd. 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, 30 Jul 1997, Daniel M. Eischen wrote: I have the source for binutils and gcc on my Linux developer's kit CDs, so presumably I just need to go ahead and: > Start with getting the Elfkit from: > > ftp://ftp.polstra.com/pub/FreeBSD/elfkit-1.2.1.tar.gz > ftp://ftp.polstra.com/pub/FreeBSD/elfkit-1.2.1.patch1 > > You'll need elfkit-1.2.1.patch1 and binutils-2.6.0.12.patch (the latter > patch coming from the elfkit tarball). Apply these patches to binutils-2.7 > (or 2.8). Read the READMEs in John Polstras elfkit if you are unsure > how to build a cross compiler - you don't need the elfkit for anything > other than the READMEs and patch. > > Pick a directory in which to want your cross-compilation system to > be installed (/usr/local/freebsdelf?) and build the patched binutils > with this prefix. Is there more info in the bin utils about doing this? I've never built binutils or gcc myself, having previously relied on the installed binaries. > Get the include files from a 3.0 FreeBSd system > and install them in /i386-unknown-freebsdelf/include. Do I need to take everything in /usr/include and below? > Grab > the necessary libraries from a 3.0 FreeBSD system and place them in > /i386-unknown-freebsdelf/lib. (I am assuming you're configuring > binutils/gcc for i386-unknown-freebsdelf). Yes. Again, is this everything from /usr/lib? I have a feeling this will be a somewhat massive set of files... > Configure gcc-2.7.2 for i386-unknown-freebsdelf and your chosen prefix. > Build and install gcc. I believe I've seen gcc documentation on this: Setting up gcc as a cross compiler, the gcc --target etc., is this the right stuff? > You're now ready to start cross compiling. I know I left out some > of the details - I have more precise notes at home if you need them. On the areas I mentioned above, yes please! Thanks, Andy Ways to annoy your roommate #8: Always flush the toilet three times. From owner-freebsd-hackers Thu Jul 31 08:34:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15779 for hackers-outgoing; Thu, 31 Jul 1997 08:34:56 -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 IAA15743; Thu, 31 Jul 1997 08:34:26 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id QAA05841; Thu, 31 Jul 1997 16:34:42 +0200 From: Luigi Rizzo Message-Id: <199707311434.QAA05841@labinfo.iet.unipi.it> Subject: working snap of new sound driver To: hackers@freebsd.org Date: Thu, 31 Jul 1997 16:34:42 +0200 (MET DST) Cc: multimedia@freebsd.org X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After about two weeks of intense development, I am pleased to say that all the major pieces of my new sound driver now work satisfactorily. As a consequence, a _working_ snap of my new sound driver is available at http://www.iet.unipi.it/~luigi/snd970731.tgz (I am running this code on my machine now). The package includes a README file with detailed installation instructions, and all the pieces you need if you are using 2.2 or above. At the time of this writing I fixed the final bugs and /dev/audio works reliably (at 8KHz, mono) with MSS-clones and SBpro (tested used the CS4232 and CS4236 PnP). PnP cards are supported (with a minor fix, you need to change the probe routine in ad1848.c to add the ID for your card), and possibly even multiple sound cards in the same system (if bugs are present, they are in the PnP probe&configure code). Many ioctls are still unimplemented (but the mixer calls work), but fixing them will be trivial and probably ready for the next snap. Do not expect any new release for a week or so, but I will be able to read email and reply. PLEASE if you have the time, test the code with your cards. I am running this code on my machine at the moment, and it seems reasonably stable. 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 Thu Jul 31 09:15:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA17784 for hackers-outgoing; Thu, 31 Jul 1997 09:15:12 -0700 (PDT) Received: from plunger.gdeb.com (plunger.gdeb.com [153.11.11.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA17735 for ; Thu, 31 Jul 1997 09:14:22 -0700 (PDT) Received: from clcrtr.clc.gdeb.com ([153.11.109.11]) by plunger.gdeb.com with SMTP (1.37.109.16/CSC-E_1.6) id AA292415146; Thu, 31 Jul 1997 12:05:46 -0400 Message-Id: <33E0B900.41C67EA6@iworks.InterWorks.org> Date: Thu, 31 Jul 1997 12:11:01 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) Mime-Version: 1.0 To: A.J.Smith@nortel.co.uk Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cross compiling for FreeBSD 3.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there more info in the bin utils about doing this? I've never built > binutils or gcc myself, having previously relied on the installed > binaries. Yes, but John Polstras Elfkit describes what you need to do. Something like: Extract binutils-2.7 (or 2.8) Apply (probably have to hand apply since they are based on binutils-2.6) the 2 binutils patches. The patches are very small. cd binutils-2.7 # or binutils-2.8 # Configure should correctly determine your host system as linux, # but you could additionally specify --host=i486-unknown-linux(elf|aout) configure --prefix=/usr/local/cross --target=i386-unknown-freebsdelf (cd bfd; make headers) make CC=cc CFLAGS=-O su make CC=cc CFLAGS=-O install > > Get the include files from a 3.0 FreeBSd system > > and install them in /i386-unknown-freebsdelf/include. > > Do I need to take everything in /usr/include and below? I would (and did). John gives you directions on how to easily do this (I've silently thanked John more than a few times :) su cd /usr find -d include | cpio -pdmv /usr/local/cross/i386-unknown-freebsdelf > > Grab > > the necessary libraries from a 3.0 FreeBSD system and place them in > > /i386-unknown-freebsdelf/lib. (I am assuming you're configuring > > binutils/gcc for i386-unknown-freebsdelf). > > Yes. Again, is this everything from /usr/lib? I have a feeling this will > be a somewhat massive set of files... No, just what you are going to link with and the crt* objects. Usually, libc should be enough. Hmm, these have to be elf-built. It would be easier if you could build Johns Elfkit on a 3.0 box to get these libraries. I don't have my 3.0-current elf-built libs around anymore, but I do have 2.2 elf-libs. Perhaps someone with 3.0 elf libs can make you a tarball so you don't have to do it yourself. > > Configure gcc-2.7.2 for i386-unknown-freebsdelf and your chosen prefix. > > Build and install gcc. > > I believe I've seen gcc documentation on this: Setting up gcc as a cross > compiler, the gcc --target etc., is this the right stuff? Really, all you need to do is in Johns README: configure --prefix=/usr/local/elf --target=i386-unknown-freebsdelf make CC=cc CFLAGS=-O LIBGCC1=libgcc1.a OLDCC="./xgcc -B./" \ FLOAT_H=/usr/include/float.h LANGUAGES=c su make CC=cc CFLAGS=-O LIBGCC1=libgcc1.a OLDCC="./xgcc -B./" \ FLOAT_H=/usr/include/float.h LANGUAGES=c install I believe the elf-built libraries are going to be your only hurdle. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Thu Jul 31 09:41:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA19368 for hackers-outgoing; Thu, 31 Jul 1997 09:41:43 -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 JAA19356 for ; Thu, 31 Jul 1997 09:41:39 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wtyHh-0002gU-00; Thu, 31 Jul 1997 10:41:05 -0600 To: Michael Smith Subject: Re: Cross compiling for FreeBSD 3.0 Cc: A.J.Smith@nortel.co.uk (Andy J. Smith), freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 31 Jul 1997 11:52:30 +0930." <199707310222.LAA25145@genesis.atrad.adelaide.edu.au> References: <199707310222.LAA25145@genesis.atrad.adelaide.edu.au> Date: Thu, 31 Jul 1997 10:41:05 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707310222.LAA25145@genesis.atrad.adelaide.edu.au> Michael Smith writes: : Your biggest problem would be building the toolchain, as the GNU tools : don't correctly support the FreeBSD environment. (This is only partly : the GNU peoples' fault.) I think that the ELF kit that was put together might help this. Warner From owner-freebsd-hackers Thu Jul 31 11:16:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24081 for hackers-outgoing; Thu, 31 Jul 1997 11:16:55 -0700 (PDT) Received: from ns1.arlut.utexas.edu (dns1.arlut.utexas.edu [129.116.212.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24076 for ; Thu, 31 Jul 1997 11:16:52 -0700 (PDT) Received: from mail-firewall.arlut.utexas.edu (dns1.arlut.utexas.edu [129.116.212.1]) by ns1.arlut.utexas.edu (8.8.5/8.8.5) with ESMTP id NAA17762 for ; Thu, 31 Jul 1997 13:16:48 -0500 (CDT) Received: from mamba.arlut.utexas.edu (mamba.arlut.utexas.edu [129.116.176.42]) by mail-firewall.arlut.utexas.edu (8.8.5/8.8.5) with SMTP id NAA17752 for ; Thu, 31 Jul 1997 13:16:46 -0500 (CDT) Received: from localhost by mamba.arlut.utexas.edu (SMI-8.6/SMI-SVR4) id NAA00458; Thu, 31 Jul 1997 13:16:45 -0500 Date: Thu, 31 Jul 1997 13:16:45 -0500 (CDT) From: "Lee Crites (AEI)" X-Sender: crites@mamba To: freebsd-hackers@freebsd.org Subject: strange communications problems... 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 sending this from a client site -- please respond to my real address, leec@adonai.net. The reason, in fact, is part of the problem I'm having. I am having difficulty communicating with the internet via my dedicated 128k isdn line. It's getting worse as time goes on. When we started this isp business, one of "us" was a network admin. When he saw haw "easy" it was to start up an isp business, he left us to start one on his own. Even though we have a lot of computer experience, network stuff is somewhat out of our league -- mine especially. So I have spent the last year reading and tinkering, with somewhat limited success. Here's what's happening: I am getting somewhat random in-bound and out-bound communications problems. I can send email to some sites and not others; I have not been made aware of any problems with people sending me mail. I can ftp to certain sites with impunity from which I cannot ftp back in -- or conversly, I can ftp in from sites I cannot ftp back to. I have not found a single problem with brousing other web pages; from many places you can't get pages from my server which are greater than around 1k. Some places get all of my web pages without a hitch. And none of the people who dial in, via my digiboard, can get access to anything outside of my physical server -- not even other things on my lan. The 1k limit seems to be across the board. If I cannot, say, send you a 'regular' email, if I send you one which is *very small* (like "hello there"), you will most likely get it. This started about three months ago with just a few sites. In fact, only one. It has now grown to nearly every site I work with. I started this message from my own server, since at the time I could *send* mail to freebsd.org, but when I sent it last night it didn't echo back to me. I tried again this morning but still haven't received a reply. So I assume freebsd.org is the latest victim of my creeping problem. One day reverse name service just ceased. My upline provider helped me get that back, so at least you know it's me... So I've spent time off and on during the last few months trying to get this fixed totally without success. I cannot find anything which seems wrong on my system. Of course, I'm scanning the books I have on hand (The Essential SA, etc) trying to figure out what might be happening, but getting nowhere. It is quite possible I have screwed up something very basic, but not having a lot of 'real' network admin experience, I can't see it. SO.... Any clues where I can start looking? Anyone in the Austin area willing to send me a bid for coming in and giving the box a once over to see what I've done wrong? I'd appreciate any help you can toss my way. If it's a RTM, please include some specific references -- I probably have the book, just didn't understand what was there. (note: can't RTFM since none of my texts are anatomically equipped) If more info is needed, please let me know and I'll try to supply it. The server in question is adam.adonai.net (205.182.92.2), which should be providing it's own primary name service. Thanks muchly... Lee From owner-freebsd-hackers Thu Jul 31 11:27:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24538 for hackers-outgoing; Thu, 31 Jul 1997 11:27:42 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA24530; Thu, 31 Jul 1997 11:27:37 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id OAA28895; Thu, 31 Jul 1997 14:30:27 -0400 (EDT) Date: Thu, 31 Jul 1997 14:30:27 -0400 (EDT) From: "David E. Cross" To: questions@freebsd.org, hackers@freebsd.org Subject: SCSI Card to use. 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 am looking to pick up a SCSI 3 Ultrawide card. I was looking at the Adaptec 2940 Ultrawide. Is there a better card to get, or one that has better support within the FreeBSD comunity? -- David Cross ACS Consultant From owner-freebsd-hackers Thu Jul 31 12:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA26630 for hackers-outgoing; Thu, 31 Jul 1997 12:00:28 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26624 for ; Thu, 31 Jul 1997 12:00:25 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA23554; Thu, 31 Jul 1997 11:59:49 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma023550; Thu Jul 31 11:59:20 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id LAA26936; Thu, 31 Jul 1997 11:59:20 -0700 (PDT) From: Archie Cobbs Message-Id: <199707311859.LAA26936@bubba.whistle.com> Subject: Re: advice on porting In-Reply-To: <199707311133.NAA25146@tenuki.honte.es> from Garey Mills at "Jul 31, 97 01:33:19 pm" To: garey@tenuki.honte.es (Garey Mills) Date: Thu, 31 Jul 1997 11:59:20 -0700 (PDT) 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 > Hello - I am looking at trying to port Toba, the University of Arizona's > Java to C compiler. There are several versions, one for Linux and one > for Solaris. Which would be the best base for porting? Is there anything > written on porting issues in general? I would *guess* that the Linux version would be easier. The main work is making Toba use FreeBSD's pthreads I think. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jul 31 12:55:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29130 for hackers-outgoing; Thu, 31 Jul 1997 12:55:53 -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 MAA29125 for ; Thu, 31 Jul 1997 12:55:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA07603; Thu, 31 Jul 1997 12:52:01 -0700 From: Terry Lambert Message-Id: <199707311952.MAA07603@phaeton.artisoft.com> Subject: Re: PCMCIA on FreeBSD2.2.1 To: grog@lemis.com (Greg Lehey) Date: Thu, 31 Jul 1997 12:52:01 -0700 (MST) Cc: rondzierwa@juno.com, hackers@FreeBSD.ORG In-Reply-To: <199707310054.KAA18204@freebie.lemis.com> from "Greg Lehey" at Jul 31, 97 10:24:45 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 > > Also, the computer uses a DataBook DB86082 PCMCIA controller chip. I > > looked thru the PCMCIA support code and did not find any mention of this > > chip, so I am wondering if it is supported. I have the data sheets and > > some diagnostic/test/development software for the chip (runs under dos), > > so I would be willing to put some work into adding support for the chip > > to the existing PCMCIA code if necessary. There are actually 5 PCMCIA chipsets, 2 of which are popular (there are more than 5, but they emulate one of the 5 command sets). The DataBook is one of the unpopular ones. I believe there was ENPIC (PCMCIA interface chipset enabler) code for the DataBook at the DataBook www site (at least it was there at one time). 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 Jul 31 13:03:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29659 for hackers-outgoing; Thu, 31 Jul 1997 13:03:29 -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 NAA29630 for ; Thu, 31 Jul 1997 13:03:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA07633; Thu, 31 Jul 1997 13:00:40 -0700 From: Terry Lambert Message-Id: <199707312000.NAA07633@phaeton.artisoft.com> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) To: nadav@cs.technion.ac.il (Nadav Eiron) Date: Thu, 31 Jul 1997 13:00:40 -0700 (MST) Cc: ada@not-enough.bandwidth.org, hackers@FreeBSD.ORG In-Reply-To: from "Nadav Eiron" at Jul 31, 97 01:08: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 > > I think there's something out there that converts word to rtf, and I know > > there's rtf->html > > There's also an rtf->LaTeX converter in the ports. Haven't put it to heavy > use, but it may be worth a try too. Word->rtf needs word (or WordPad). One in rtf, the rest is easy. I think the copyright issues someone else brought up would be a problem, since rtf would require redistribution. 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 Jul 31 14:55:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06342 for hackers-outgoing; Thu, 31 Jul 1997 14:55:33 -0700 (PDT) Received: from igw3.watson.ibm.com (igw3.watson.ibm.com [198.81.209.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06333 for ; Thu, 31 Jul 1997 14:55:30 -0700 (PDT) Received: from mailhub1.watson.ibm.com (mailhub1.watson.ibm.com [9.2.249.31]) by igw3.watson.ibm.com (8.8.5/07-11-97) with ESMTP id RAA08666 for ; Thu, 31 Jul 1997 17:54:19 -0400 Received: from hawpub1.watson.ibm.com (hawpub1.watson.ibm.com [9.2.90.32]) by mailhub1.watson.ibm.com (8.8.2/07-14-97) with SMTP id RAA65727; Thu, 31 Jul 1997 17:55:26 -0400 Received: by hawpub1.watson.ibm.com (AIX 3.2/UCB 5.64/6/25/96) id AA25609; Thu, 31 Jul 1997 17:55:25 -0400 Date: Thu, 31 Jul 1997 17:55:25 -0400 From: Kavitha Message-Id: <9707312155.AA25609@hawpub1.watson.ibm.com> To: freebsd-hackers@freebsd.org Subject: unix plugins Cc: kavitha@watson.ibm.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I want to know if there are any plugins for Unix based platforms, specifically for FreeBSD, NetBSD, AIX? Most of the plugins I found on the Web are for Windows & Mac. I have found a plugin-sdk for unix from netscape developer site. But it just doesn't work, i.e. I'm able to create the sharable object module and put it in .netscpae/plugins. But netscape just doesn't recognise it. It doesn't even give any error. It behaves as if the netscape/plugins directory is empty. Has anyone tried this before? Any pointers will be greatly appreciated. TIA Kavitha From owner-freebsd-hackers Thu Jul 31 15:34:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08461 for hackers-outgoing; Thu, 31 Jul 1997 15:34:47 -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 PAA08455 for ; Thu, 31 Jul 1997 15:34:42 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id IAA29970; Fri, 1 Aug 1997 08:04:33 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id IAA07578; Fri, 1 Aug 1997 08:04:31 +0930 (CST) Message-Id: <199707312234.IAA07578@freebie.lemis.com> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707310922.LAA00130@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Jul 31, 97 11:22:24 am" To: sos@sos.freebsd.dk (Søren Schmidt) Date: Fri, 1 Aug 1997 08:04:31 +0930 (CST) Cc: grog@lemis.com, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG 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-Mailer: ELM [version 2.4ME+ PL32 (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 Søren Schmidt writes: > In reply to Greg Lehey who wrote: >> Luigi Rizzo writes: >>>> >>>> Save yourself some money, and start with (shudder) >>>> http://www.microsoft.com/hwdev/ >>> >>> too bad they only have MS Word documents (what would you expect!) >> >> Has anybody investigated what it would take to convert MS Word to a >> portable format? So much stuff is sent in it nowadays, even by people >> who should know better. Is it that difficult? If somebody can point >> me to some format documentation, I'm prepared to have a hack at it. > > I use StarDivision StarOffice packet, it reads word6 docs and writes it > in almost anything, it has a little problems with word7 but it can be > used. You then get a nice Office packet as a sideeffect :) I've heard conflicting things about StarOffice. But it's not what I'm looking for: I'm looking for a program, UNIX-style, which converts MS Word format to something readable. It could, for example, be used to read MS Word mail attachments. Greg From owner-freebsd-hackers Thu Jul 31 15:42:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08836 for hackers-outgoing; Thu, 31 Jul 1997 15:42:03 -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 PAA08831 for ; Thu, 31 Jul 1997 15:42:00 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id IAA29995; Fri, 1 Aug 1997 08:11:55 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id IAA07609; Fri, 1 Aug 1997 08:11:53 +0930 (CST) Message-Id: <199707312241.IAA07609@freebie.lemis.com> Subject: Re: PPP chap problem In-Reply-To: <33E019CE.167EB0E7@acm.org> from Gabor Kincses at "Jul 30, 97 11:51:26 pm" To: gabor@acm.org (Gabor Kincses) Date: Fri, 1 Aug 1997 08:11:53 +0930 (CST) Cc: archie@whistle.com, hackers@FreeBSD.ORG 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-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 Gabor Kincses writes: > Archie Cobbs wrote: >> >>> I have tried to make chap work, but no go. I have used pap and no >>> authentication for over 6 months now, but chap doesn't seem to work. >>> >>> I always get >>> LCP: SendConfigRej(Req-Sent) >>> AUTHPROTO proto = c223 >>> >>> which means that my side rejects chap authentication. >>> Even though I added enable chap, accept chap. >> >> Enable chap means "i want the peer to authenticate to me using chap", >> so you don't want to do that. >> >>> I also tried to disable chap and only accept chap, but that didn't work >> >> Hmm, should have. > > I understood what enable chap meant after reading someone's post on the > newgroup and tried out disable chap and accept chap, which didn't work > either. The really interesting part is that if I say accept pap, then > the SendConfigRej becomes SendConfigNak AUTHPROTO proto = c023, so it > seems there might be something wrong with the chap state in the > code. No. PAP is 0xc023, CHAP is 0xc223 (see net/ppp_defs.h). > Again I'm getting this after I escape out of term into packet mode. Is > there anything different here from executing a script? Well, yes. I don't understand the question. > I only have the 2.1.5 source code, but haven't been able to dig through > the relevant portions. All I can tell that the code never really gets > into the chap.c stuff... That seems unlikely. Have you done a complete trace? There's nothing you've shown here which disproves Archie's suggestion, which I think is correct. Greg From owner-freebsd-hackers Thu Jul 31 16:08:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA09865 for hackers-outgoing; Thu, 31 Jul 1997 16:08:11 -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 QAA09858 for ; Thu, 31 Jul 1997 16:08:08 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id SAA00423; Thu, 31 Jul 1997 18:06:57 -0500 (EST) From: "John S. Dyson" Message-Id: <199707312306.SAA00423@dyson.iquest.net> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707312234.IAA07578@freebie.lemis.com> from Greg Lehey at "Aug 1, 97 08:04:31 am" To: grog@lemis.com (Greg Lehey) Date: Thu, 31 Jul 1997 18:06:56 -0500 (EST) Cc: sos@sos.freebsd.dk, grog@lemis.com, luigi@labinfo.iet.unipi.it, 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've heard conflicting things about StarOffice. But it's not what I'm > looking for: I'm looking for a program, UNIX-style, which converts MS > Word format to something readable. It could, for example, be used to > read MS Word mail attachments. > > Greg > Have you heard of laola??? It can pull apart the directory structure of the MS file format. The ascii text is still rough, but is alot better than the original file: http://wwwwbs.cs.tu-berlin.de/~schwartz/pmh/laola.html Hope this helps. John From owner-freebsd-hackers Thu Jul 31 16:21:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA10481 for hackers-outgoing; Thu, 31 Jul 1997 16:21:37 -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 QAA10473 for ; Thu, 31 Jul 1997 16:21:32 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id IAA00229; Fri, 1 Aug 1997 08:51:26 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id IAA07707; Fri, 1 Aug 1997 08:51:25 +0930 (CST) Message-Id: <199707312321.IAA07707@freebie.lemis.com> Subject: Re: MS Word documents (was: Advice sought on PnP configuration) In-Reply-To: <199707312306.SAA00423@dyson.iquest.net> from "John S. Dyson" at "Jul 31, 97 06:06:56 pm" To: toor@dyson.iquest.net (John S. Dyson) Date: Fri, 1 Aug 1997 08:51:24 +0930 (CST) Cc: grog@lemis.com, sos@sos.freebsd.dk, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG 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-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 John S. Dyson writes: >> >> I've heard conflicting things about StarOffice. But it's not what I'm >> looking for: I'm looking for a program, UNIX-style, which converts MS >> Word format to something readable. It could, for example, be used to >> read MS Word mail attachments. >> >> Greg >> > Have you heard of laola??? > > It can pull apart the directory structure > of the MS file format. The ascii text is still rough, but is alot > better than the original file: > > http://wwwwbs.cs.tu-berlin.de/~schwartz/pmh/laola.html Thanks, yes, now I have. I got a private reply to this question pointing me to the URL. Greg From owner-freebsd-hackers Thu Jul 31 16:37:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11185 for hackers-outgoing; Thu, 31 Jul 1997 16:37: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 QAA11180 for ; Thu, 31 Jul 1997 16:36:59 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id QAA08729; Thu, 31 Jul 1997 16:36:58 -0700 (PDT) Message-Id: <199707312336.QAA08729@rah.star-gate.com> To: Kavitha cc: freebsd-hackers@FreeBSD.ORG Subject: Re: unix plugins In-reply-to: Your message of "Thu, 31 Jul 1997 17:55:25 EDT." <9707312155.AA25609@hawpub1.watson.ibm.com> Date: Thu, 31 Jul 1997 16:36:58 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Not too long ago I built the unix midi plugin and I use amaya to load the plugin. I don't think that the bsdi version of netscape supports plugins however the linux version of netscape/communicator does however you have to locate a linux plugin or build one in a linux box. Cheers, Amancio >From The Desk Of Kavitha : > Hi, > > I want to know if there are any plugins for Unix based platforms, specific ally > for FreeBSD, NetBSD, AIX? Most of the plugins I found on the Web are for Wind ows & Mac. > I have found a plugin-sdk for unix from netscape developer site. But it just doesn't > work, i.e. I'm able to create the sharable object module and put it in .netsc pae/plugins. > But netscape just doesn't recognise it. It doesn't even give any error. It b ehaves as if > the netscape/plugins directory is empty. Has anyone tried this before? Any po inters will be > greatly appreciated. > > TIA > Kavitha > From owner-freebsd-hackers Thu Jul 31 16:37:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11222 for hackers-outgoing; Thu, 31 Jul 1997 16:37:26 -0700 (PDT) Received: from mail5.doit.wisc.edu (mail5.doit.wisc.edu [144.92.104.215]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11217 for ; Thu, 31 Jul 1997 16:37:23 -0700 (PDT) Received: from audumla.students.wisc.edu by mail5.doit.wisc.edu; id SAA63200; 8.7.5/50; Thu, 31 Jul 1997 18:37:11 -0500 Received: from ww720-3320r by audumla.students.wisc.edu; id SAA35096; 8.6.9W/42; Thu, 31 Jul 1997 18:36:30 -0500 Message-ID: <33E121A1.7432@acm.org> Date: Thu, 31 Jul 1997 18:37:05 -0500 From: Gabor Kincses X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Greg Lehey CC: archie@whistle.com, hackers@FreeBSD.ORG Subject: Re: PPP chap problem References: <199707312241.IAA07609@freebie.lemis.com> 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: > > Gabor Kincses writes: > > Archie Cobbs wrote: > >> > >>> I have tried to make chap work, but no go. I have used pap and no > >>> authentication for over 6 months now, but chap doesn't seem to work. > >>> > >>> I always get > >>> LCP: SendConfigRej(Req-Sent) > >>> AUTHPROTO proto = c223 > >>> > >>> which means that my side rejects chap authentication. > >>> Even though I added enable chap, accept chap. > >> > >> Enable chap means "i want the peer to authenticate to me using chap", > >> so you don't want to do that. > >> > >>> I also tried to disable chap and only accept chap, but that didn't work > >> > >> Hmm, should have. > > > > I understood what enable chap meant after reading someone's post on the > > newgroup and tried out disable chap and accept chap, which didn't work > > either. The really interesting part is that if I say accept pap, then > > the SendConfigRej becomes SendConfigNak AUTHPROTO proto = c023, so it > > seems there might be something wrong with the chap state in the > > code. > > No. PAP is 0xc023, CHAP is 0xc223 (see net/ppp_defs.h). I know. I looked (actually also defined in /usr/src/usr.sbin/ppp). What I meant here is that with accept or deny pap, my side refuses to accept chap. When pap is allowed (accept pap) my side suggests the use of pap instead of chap (since maybe it thinks chap is not allowed, which would be the hypothesized bug, since I DID accept chap), hence the SendConfigNak AUTHPROTO proto = c023 message. When pap is not allowed (deny pap) it sends a SendConfigRej AUTHPROTO proto = c223, attesting that it (ppp) thinks that chap is in fact disallowed. Whether pap is denied or accepted should really be irrelevant to the chap discussion, except in both cases I see indication that ppp thinks chap is not allowed on my side, in spite of the explicit 'accept chap'. I haven't read the RFC, but it seems logical that it would try to use pap as a fallback, if chap is denied. > > > Again I'm getting this after I escape out of term into packet mode. Is > > there anything different here from executing a script? > > Well, yes. I don't understand the question. I meant that people have gotten chap working a zillion times fine. The only thing that seems non-standard in my case is that I need to enter term to answer the SNK challenge number and then enter packet mode from there. I felt that most people use the scripting method to dial up their providers. > > > I only have the 2.1.5 source code, but haven't been able to dig through > > the relevant portions. All I can tell that the code never really gets > > into the chap.c stuff... > > That seems unlikely. Have you done a complete trace? There's nothing > you've shown here which disproves Archie's suggestion, which I think > is correct. > > Greg I looked at the code where the log messages are written to the log file (based on what I have found in the log file itself) and concluded that ppp thinks that chap is not allowed, so it never goes into trying to perform chap. Ie. when a SendConfigRej AUTHPROTO = c223 message is written to the log file, you have not yet done chap and you never will. Is this last assumption wrong? -- Gabor Kincses (gabor@acm.org) FreeBSD 2.1.5/2.2.2 From owner-freebsd-hackers Thu Jul 31 17:19:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12639 for hackers-outgoing; Thu, 31 Jul 1997 17:19:31 -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 RAA12631 for ; Thu, 31 Jul 1997 17:19:27 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id JAA00624; Fri, 1 Aug 1997 09:49:21 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id JAA07918; Fri, 1 Aug 1997 09:49:18 +0930 (CST) Message-Id: <199708010019.JAA07918@freebie.lemis.com> Subject: Re: SCSI 1542 error In-Reply-To: <23781.199707310811@seagoon.gid.co.uk> from Bob Bishop at "Jul 31, 97 09:11:11 am" To: rb@gid.co.uk (Bob Bishop) Date: Fri, 1 Aug 1997 09:49:18 +0930 (CST) Cc: hackers@FreeBSD.ORG 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-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 Bob Bishop writes: > In article <199707291542.JAA12346@rocky.mt.sri.com>, > Nate Williams wrote: >> You're not the first. It appears to me from watching the mailing list >> that the 1542 boards are not supported in 2.2. *Many* people have >> reported problems with them, which unfortunately means that I can no >> longer do 2.2 development at home. :( > > I've got two machines running 2.2.x on 1542CF with no problems; my -current > machine runs on one too. > > A thought: have those reporting trouble got the transfer rate wound up > on the controller? Mine are running on the defaults. So is mine. I think the problem is related to the combination of device and controller; since moving my Archive changer from the 1542 to the 2940, things are running fine. Greg From owner-freebsd-hackers Thu Jul 31 17:37:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA13636 for hackers-outgoing; Thu, 31 Jul 1997 17:37:46 -0700 (PDT) Received: from thor.i-connect.net (qmailr@thor.i-Connect.Net [206.190.143.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA13625 for ; Thu, 31 Jul 1997 17:37:42 -0700 (PDT) Received: (qmail 8750 invoked by uid 4028); 1 Aug 1997 00:37:41 -0000 Message-ID: X-Mailer: XFMail 0.5-alpha [p0] on Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 31 Jul 1997 17:29:46 -0700 (PDT) From: ron@cts.com To: "David E. Cross" Subject: RE: SCSI Card to use. Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk There is a new driver for the DPT SCSI 3 disc controller. E-mail simon@iconnect.net for details. The DPT is probably the highest performance SCSI 3 controller supported under FreeBSD. You will have to be at revision 2.2 or better. Subscribe to the scsi mailing list to keep abreast of new versions, etc. Ron McDaniels On 01-Aug-97 "David E. Cross" wrote: >>I am looking to pick up a SCSI 3 Ultrawide card. I was looking at the >Adaptec 2940 Ultrawide. Is there a better card to get, or one that has >better support within the FreeBSD comunity? > >-- >David Cross >ACS Consultant > ---------------------------------- E-Mail: ron@cts.com Date: 07/31/97 Time: 17:29:46 This message was sent by XF-Mail ---------------------------------- From owner-freebsd-hackers Thu Jul 31 17:46:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14118 for hackers-outgoing; Thu, 31 Jul 1997 17:46:48 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA14113 for ; Thu, 31 Jul 1997 17:46:45 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA26118; Thu, 31 Jul 1997 17:46:14 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma026110; Thu Jul 31 17:46:07 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id RAA00665; Thu, 31 Jul 1997 17:46:07 -0700 (PDT) From: Archie Cobbs Message-Id: <199708010046.RAA00665@bubba.whistle.com> Subject: Re: PPP chap problem In-Reply-To: <33E121A1.7432@acm.org> from Gabor Kincses at "Jul 31, 97 06:37:05 pm" To: gabor@acm.org (Gabor Kincses) Date: Thu, 31 Jul 1997 17:46:07 -0700 (PDT) Cc: grog@lemis.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 > > >>> I have tried to make chap work, but no go. I have used pap and no > > >>> authentication for over 6 months now, but chap doesn't seem to work. > > >>> > > >>> I always get > > >>> LCP: SendConfigRej(Req-Sent) > > >>> AUTHPROTO proto = c223 > > >>> > > >>> which means that my side rejects chap authentication. > > >>> Even though I added enable chap, accept chap. > > >> > > >> Enable chap means "i want the peer to authenticate to me using chap", > > >> so you don't want to do that. > > >> > > >>> I also tried to disable chap and only accept chap, but that didn't work > > >> > > >> Hmm, should have. > > > > > > I understood what enable chap meant after reading someone's post on the > > > newgroup and tried out disable chap and accept chap, which didn't work > > > either. The really interesting part is that if I say accept pap, then > > > the SendConfigRej becomes SendConfigNak AUTHPROTO proto = c023, so it > > > seems there might be something wrong with the chap state in the > > > code. > > > > No. PAP is 0xc023, CHAP is 0xc223 (see net/ppp_defs.h). > > I know. I looked (actually also defined in /usr/src/usr.sbin/ppp). > What I meant here is that with accept or deny pap, my side refuses to > accept chap. When pap is allowed (accept pap) my side suggests the use > of pap instead of chap (since maybe it thinks chap is not allowed, which > would be the hypothesized bug, since I DID accept chap), hence the > SendConfigNak AUTHPROTO proto = c023 message. When pap is not allowed > (deny pap) it sends a SendConfigRej AUTHPROTO proto = c223, attesting > that it (ppp) thinks that chap is in fact disallowed. Whether pap is > denied or accepted should really be irrelevant to the chap discussion, > except in both cases I see indication that ppp thinks chap is not > allowed on my side, in spite of the explicit 'accept chap'. > > I haven't read the RFC, but it seems logical that it would try to use > pap as a fallback, if chap is denied. Yes, the logic should be "prefer CHAP" but accept anything that's marked "accept". > > > Again I'm getting this after I escape out of term into packet mode. Is > > > there anything different here from executing a script? > > > > Well, yes. I don't understand the question. > > I meant that people have gotten chap working a zillion times fine. The > only thing that seems non-standard in my case is that I need to enter > term to answer the SNK challenge number and then enter packet mode from > there. I felt that most people use the scripting method to dial up > their providers. Yep... > > > I only have the 2.1.5 source code, but haven't been able to dig through > > > the relevant portions. All I can tell that the code never really gets > > > into the chap.c stuff... > > > > That seems unlikely. Have you done a complete trace? There's nothing > > you've shown here which disproves Archie's suggestion, which I think > > is correct. > > > > Greg > > I looked at the code where the log messages are written to the log file > (based on what I have found in the log file itself) and concluded that > ppp thinks that chap is not allowed, so it never goes into trying to > perform chap. Ie. when a SendConfigRej AUTHPROTO = c223 message is > written to the log file, you have not yet done chap and you never will. > Is this last assumption wrong? No, that sounds right. Guess there's just a gremlin in there somewhere. I'm not familiar enough with that code to speculate with any more detail :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jul 31 18:31:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA15933 for hackers-outgoing; Thu, 31 Jul 1997 18:31:28 -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 SAA15927; Thu, 31 Jul 1997 18:31:21 -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 CAA03793; Fri, 1 Aug 1997 02:31:11 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id CAA21758; Fri, 1 Aug 1997 02:31:14 +0100 (BST) Message-Id: <199708010131.CAA21758@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: ac199@hwcn.org cc: grog@FreeBSD.ORG, Brian Somers , dk+@ua.net, freebsd-hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Wed, 30 Jul 1997 01:32:59 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 02:31:14 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, 30 Jul 1997 grog@FreeBSD.ORG wrote: > > > >>>>>> [yy[mm[dd[hh]]]]mm[.ss]] > > At risk of missing the obvious, why can't the above simply be > extended to > > [cc[yy[mm[dd[hh]]]]]mm[.ss]] Yep. As I suggested. > ? This format strikes me as being right since any usually, if the > date is off by a large amount (eg. centuries), the year, month, day, > hour, and minute will also be off. However, the date being off by a > minute or two, while the hour, day, month, year, and century are > correct is not unusual. > > This seems to avoid the below monstrosities. > > > >> [[[cc]yy[mm[dd[hh]]]]mm[.ss]] > > >>> cc[yy[mm[dd[hh]]]]]mm[.ss]] > > The first is hopelessly ambigious and the 2nd is hopelessly > annoying. The first is just wrong, and the second is a mis-quote. I originally said: > More like: > > [[cc[yy[mm[dd[hh]]]]]mm[.ss]] > > (you can't have the century without the year). > > -- > tIM...HOEk > OPTIMIZATION: the process of using many one-letter variables names > hoping that the resultant code will run faster. > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 18:34:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA16115 for hackers-outgoing; Thu, 31 Jul 1997 18:34:16 -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 SAA16108 for ; Thu, 31 Jul 1997 18:34:08 -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 CAA03882; Fri, 1 Aug 1997 02:33:21 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id CAA22677; Fri, 1 Aug 1997 02:33:23 +0100 (BST) Message-Id: <199708010133.CAA22677@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Dufault cc: hackers@FreeBSD.ORG Subject: Re: Assigning PRS to myself In-reply-to: Your message of "Wed, 30 Jul 1997 07:05:01 EDT." <199707301105.HAA00350@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 02:33:23 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I want to assign all P1003.4 and rtprio PRS to myself. How do I do that, > outside of asking someone? edit-pr > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Safety critical systems, Agency approval -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 19:00:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17130 for hackers-outgoing; Thu, 31 Jul 1997 19:00:46 -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 TAA17125 for ; Thu, 31 Jul 1997 19:00:42 -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 CAA03908; Fri, 1 Aug 1997 02:53:58 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id CAA23814; Fri, 1 Aug 1997 02:53:58 +0100 (BST) Message-Id: <199708010153.CAA23814@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Gabor Kincses cc: hackers@FreeBSD.ORG Subject: Re: PPP chap problem In-reply-to: Your message of "Wed, 30 Jul 1997 19:10:13 CDT." <33DFD7E5.41C67EA6@acm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 02:53:58 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have tried to make chap work, but no go. I have used pap and no > authentication for over 6 months now, but chap doesn't seem to work. > > I always get > LCP: SendConfigRej(Req-Sent) > AUTHPROTO proto = c223 > > which means that my side rejects chap authentication. > Even though I added enable chap, accept chap. > > I also tried to disable chap and only accept chap, but that didn't work > either. I also tried accept pap in which case the SendConfigRej became > a SendConfigNak with c023 suggested to the peer. > > I got the same results under 2.1.5 and 2.2.2. > > Any help is really appreciated. > > BTW, I have to use term so that I can enter an SNK response before going > into packet mode. I don't think that should matter. ppp only does CHAP with MD5 (this is the only requirement according to rfc1994). You'll need to "set log +HDLC" to see what the fifth octet in the chap packet is. If you drop me a line telling me, I'll put it on my list of things to add. > -- > Gabor Kincses > (gabor@acm.org) > FreeBSD 2.1.5/2.2.2 -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 19:08:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17609 for hackers-outgoing; Thu, 31 Jul 1997 19:08:56 -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 TAA17601 for ; Thu, 31 Jul 1997 19:08:51 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id LAA01674; Fri, 1 Aug 1997 11:38:43 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id LAA08172; Fri, 1 Aug 1997 11:38:39 +0930 (CST) Message-Id: <199708010208.LAA08172@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010131.CAA21758@awfulhak.org> from Brian Somers at "Aug 1, 97 02:31:14 am" To: brian@awfulhak.org (Brian Somers) Date: Fri, 1 Aug 1997 11:38:39 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers) 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-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 Brian Somers writes: >> On Wed, 30 Jul 1997 grog@FreeBSD.ORG wrote: >> >>>>>>>>>> yy[mm[dd[hh]]]]mm[.ss]] >> >> At risk of missing the obvious, why can't the above simply be >> extended to >> >>> cc[yy[mm[dd[hh]]]]]mm[.ss]] > > Yep. As I suggested. > >> ? This format strikes me as being right since any usually, if the >> date is off by a large amount (eg. centuries), the year, month, day, >> hour, and minute will also be off. However, the date being off by a >> minute or two, while the hour, day, month, year, and century are >> correct is not unusual. >> >> This seems to avoid the below monstrosities. >> >>>>> [[[cc]yy[mm[dd[hh]]]]mm[.ss]] >>>>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] >> >> The first is hopelessly ambigious and the 2nd is hopelessly >> annoying. > > The first is just wrong, and the second is a mis-quote. I originally > said: > >> More like: >> >>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] >> >> (you can't have the century without the year). I think this confusion is making my point: the syntax is too complicated. I understand the [...] to mean optional parts. In this case, we have two unbalanced ]s: cc[yy[mm[dd[hh]]]]]mm[.ss]] ^ ^ | | Ignoring this problem, this syntax can be expanded to: cc[yy[mm[dd]]]mm[.ss] cc[yy[mm]]mm[.ss] cc[yy]mm[.ss] ccmm[.ss] cc[yy[mm[dd]]]mm cc[yy[mm]]mm cc[yy]mm ccmm So 'date 2001' must mean "set the date to century 20, year undefined, month, day, and hour undefined, minute 1. Most newcomers to UNIX hate date(1) because the date entry format is already too cryptic. This would just make it worse. There are some other alternatives for date entry--tar uses one, for example, though it may be GNU code. Why not base an implementation on one of those? Greg From owner-freebsd-hackers Thu Jul 31 19:39:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA19094 for hackers-outgoing; Thu, 31 Jul 1997 19:39:21 -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 TAA19083 for ; Thu, 31 Jul 1997 19:39:13 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id MAA01994; Fri, 1 Aug 1997 12:09:08 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id MAA08318; Fri, 1 Aug 1997 12:09:06 +0930 (CST) Message-Id: <199708010239.MAA08318@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010131.CAA21758@awfulhak.org> from Brian Somers at "Aug 1, 97 02:31:14 am" To: brian@awfulhak.org (Brian Somers) Date: Fri, 1 Aug 1997 12:09:06 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers) 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-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 Brian Somers writes: >> On Wed, 30 Jul 1997 grog@FreeBSD.ORG wrote: >> >>>>>>>>>> yy[mm[dd[hh]]]]mm[.ss]] > > (etc) Now here's an enhancement that I *would* like to see: specify a timezone file to use. Something like: $ date -z /usr/share/zoneinfo/Asia/Tokyo to give you the current time in Tokyo. Greg From owner-freebsd-hackers Thu Jul 31 19:41:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA19338 for hackers-outgoing; Thu, 31 Jul 1997 19:41:26 -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 TAA19318 for ; Thu, 31 Jul 1997 19:41:18 -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 DAA04138; Fri, 1 Aug 1997 03:40:06 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id DAA03883; Fri, 1 Aug 1997 03:40:05 +0100 (BST) Message-Id: <199708010240.DAA03883@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: brian@awfulhak.org (Brian Somers), hackers@freebsd.org (FreeBSD Hackers) Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 11:38:39 +0930." <199708010208.LAA08172@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 03:40:05 +0100 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [.....] > > The first is just wrong, and the second is a mis-quote. I originally > > said: > > > >> More like: > >> > >>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] Arrrghhhhhh ! Your mailer is gobbling the "open square brace" characters ! That is *NOT* what I posted. There are two opening brackets prior to the ``cc'' that something's eating. I'm sure we can all agree that this means the above usage (with the two wandering brackets included) is correct ? [.....] > Greg > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 20:00:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20447 for hackers-outgoing; Thu, 31 Jul 1997 20:00:41 -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 UAA20438 for ; Thu, 31 Jul 1997 20:00:35 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id MAA02167; Fri, 1 Aug 1997 12:30:31 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id MAA08376; Fri, 1 Aug 1997 12:30:30 +0930 (CST) Message-Id: <199708010300.MAA08376@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010240.DAA03883@awfulhak.org> from Brian Somers at "Aug 1, 97 03:40:05 am" To: brian@awfulhak.org (Brian Somers) Date: Fri, 1 Aug 1997 12:30:29 +0930 (CST) Cc: grog@lemis.com, brian@awfulhak.org, hackers@freebsd.org 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-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 Brian Somers writes: >> .....] >> > The first is just wrong, and the second is a mis-quote. I originally >> > said: >> > >> >> More like: >> >> >> >>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] > > Arrrghhhhhh ! Your mailer is gobbling the "open square brace" > characters ! That is *NOT* what I posted. There are two opening > brackets prior to the ``cc'' that something's eating. Mea culpa. OK, that changes things: + [[cc[yy[mm[dd[hh]]]]]mm[.ss]] + + this syntax can be expanded to: + + [[cc[yy[mm[dd]]]]mm[.ss]] + [[cc[yy[mm]]]mm[.ss]] + [[cc[yy]]mm[.ss]] + [[cc]mm[.ss]] + [mm[.ss]] + [[cc[yy[mm[dd]]]]mm] + [[cc[yy[mm]]]mm] + [[cc[yy]]mm] + [[cc]mm] + + So 'date 2001' must mean "set the date to century 20, year undefined, + month, day, and hour undefined, minute 1. + + Most newcomers to UNIX hate date(1) because the date entry format is + already too cryptic. This would just make it worse. There are some + other alternatives for date entry--tar uses one, for example, though + it may be GNU code. Why not base an implementation on one of those? In other words, yes, my mail macros screwed up the syntax, but they didn't change much. > I'm sure we can all agree that this means the above usage (with the > two wandering brackets included) is correct ? No, it's still wrong. Greg From owner-freebsd-hackers Thu Jul 31 20:04:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20646 for hackers-outgoing; Thu, 31 Jul 1997 20:04:31 -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 UAA20641 for ; Thu, 31 Jul 1997 20:04:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA02188; Fri, 1 Aug 1997 12:34:00 +0930 (CST) From: Michael Smith Message-Id: <199708010304.MAA02188@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199708010208.LAA08172@freebie.lemis.com> from Greg Lehey at "Aug 1, 97 11:38:39 am" To: grog@lemis.com (Greg Lehey) Date: Fri, 1 Aug 1997 12:33:59 +0930 (CST) Cc: brian@awfulhak.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 Greg Lehey stands accused of saying: > > Most newcomers to UNIX hate date(1) because the date entry format is > already too cryptic. This would just make it worse. There are some > other alternatives for date entry--tar uses one, for example, though > it may be GNU code. Why not base an implementation on one of those? This is what I proposed back at the beginning of the thread : something like : date -f %H:%M:%S 12:31:00 date -f %c%y,%m,%d 1997,Aug,1 etc, with some standard builtin templates for trying, eg : date -a "Fri 1 Aug 12:33:15 CST 1997" is the standard ctime format, one that's worth parsing. > 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 Thu Jul 31 20:33:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA22134 for hackers-outgoing; Thu, 31 Jul 1997 20:33:35 -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 UAA22119 for ; Thu, 31 Jul 1997 20:33:25 -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 EAA04444; Fri, 1 Aug 1997 04:27:48 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id EAA05954; Fri, 1 Aug 1997 04:27:47 +0100 (BST) Message-Id: <199708010327.EAA05954@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: brian@awfulhak.org (Brian Somers), hackers@freebsd.org Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 12:30:29 +0930." <199708010300.MAA08376@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 04:27:47 +0100 From: Brian Somers Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > + [[cc[yy[mm[dd[hh]]]]]mm[.ss]] > + > + this syntax can be expanded to: > + > + [[cc[yy[mm[dd]]]]mm[.ss]] > + [[cc[yy[mm]]]mm[.ss]] > + [[cc[yy]]mm[.ss]] > + [[cc]mm[.ss]] > + [mm[.ss]] > + [[cc[yy[mm[dd]]]]mm] > + [[cc[yy[mm]]]mm] > + [[cc[yy]]mm] > + [[cc]mm] > + > + So 'date 2001' must mean "set the date to century 20, year undefined, > + month, day, and hour undefined, minute 1. > + > + Most newcomers to UNIX hate date(1) because the date entry format is > + already too cryptic. This would just make it worse. There are some > + other alternatives for date entry--tar uses one, for example, though > + it may be GNU code. Why not base an implementation on one of those? > > In other words, yes, my mail macros screwed up the syntax, but they > didn't change much. > > > I'm sure we can all agree that this means the above usage (with the > > two wandering brackets included) is correct ? > > No, it's still wrong. Oops, let me just delete that "no no no" mail that I nearly sent *blush*. Of course it should be: [[[[[cc]yy]mm]dd]HH]MM[.SS] As we strip the brackets from the outside in, we get the right answer :-) Thanks. > Greg -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 20:33:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA22153 for hackers-outgoing; Thu, 31 Jul 1997 20:33:40 -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 UAA22123 for ; Thu, 31 Jul 1997 20:33:30 -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 EAA04533; Fri, 1 Aug 1997 04:30:42 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.6/8.8.6) with ESMTP id EAA06049; Fri, 1 Aug 1997 04:30:42 +0100 (BST) Message-Id: <199708010330.EAA06049@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Smith cc: grog@lemis.com (Greg Lehey), brian@awfulhak.org, hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 12:33:59 +0930." <199708010304.MAA02188@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 04:30:41 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is what I proposed back at the beginning of the thread : something > like : > > date -f %H:%M:%S 12:31:00 > date -f %c%y,%m,%d 1997,Aug,1 > > etc, with some standard builtin templates for trying, eg : > > date -a "Fri 1 Aug 12:33:15 CST 1997" > > is the standard ctime format, one that's worth parsing. So who's lurking with the strptime() code ? > -- > ]] 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 [[ -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Thu Jul 31 20:50:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23009 for hackers-outgoing; Thu, 31 Jul 1997 20:50:23 -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 UAA22996 for ; Thu, 31 Jul 1997 20:50:17 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA02681; Fri, 1 Aug 1997 13:19:55 +0930 (CST) From: Michael Smith Message-Id: <199708010349.NAA02681@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199708010240.DAA03883@awfulhak.org> from Brian Somers at "Aug 1, 97 03:40:05 am" To: brian@awfulhak.org (Brian Somers) Date: Fri, 1 Aug 1997 13:19:54 +0930 (CST) Cc: grog@lemis.com, brian@awfulhak.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 Brian Somers stands accused of saying: > [.....] > > > The first is just wrong, and the second is a mis-quote. I originally > > > said: > > > > > >> More like: > > >> > > >>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] > > Arrrghhhhhh ! Your mailer is gobbling the "open square brace" > characters ! That is *NOT* what I posted. There are two opening > brackets prior to the ``cc'' that something's eating. Greg is almost certainly using supercite inside emacs. Bad boy! > I'm sure we can all agree that this means the above usage (with the > two wandering brackets included) is correct ? Yes. -- ]] 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 Thu Jul 31 20:52:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23221 for hackers-outgoing; Thu, 31 Jul 1997 20:52: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 UAA23216 for ; Thu, 31 Jul 1997 20:52:13 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id NAA02713; Fri, 1 Aug 1997 13:22:02 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id NAA08506; Fri, 1 Aug 1997 13:22:01 +0930 (CST) Message-Id: <199708010352.NAA08506@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010349.NAA02681@genesis.atrad.adelaide.edu.au> from Michael Smith at "Aug 1, 97 01:19:54 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 1 Aug 1997 13:22:00 +0930 (CST) Cc: brian@awfulhak.org, grog@lemis.com, hackers@FreeBSD.ORG 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-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 Michael Smith writes: > Brian Somers stands accused of saying: >>> .....] >>>> The first is just wrong, and the second is a mis-quote. I originally >>>> said: >>>> >>>>> More like: >>>>> >>>>>>> cc[yy[mm[dd[hh]]]]]mm[.ss]] >> >> Arrrghhhhhh ! Your mailer is gobbling the "open square brace" >> characters ! That is *NOT* what I posted. There are two opening >> brackets prior to the ``cc'' that something's eating. > > Greg is almost certainly using supercite inside emacs. Bad boy! No. Real Hackers write their own Emacs macros. And they don't always work right. >> I'm sure we can all agree that this means the above usage (with the >> two wandering brackets included) is correct ? > > Yes. Oh. Think-again-ing you what Grog From owner-freebsd-hackers Thu Jul 31 20:55:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23464 for hackers-outgoing; Thu, 31 Jul 1997 20:55:44 -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 UAA23451 for ; Thu, 31 Jul 1997 20:55:19 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA02772; Fri, 1 Aug 1997 13:24:48 +0930 (CST) From: Michael Smith Message-Id: <199708010354.NAA02772@genesis.atrad.adelaide.edu.au> Subject: Re: date(1) In-Reply-To: <199708010352.NAA08506@freebie.lemis.com> from Greg Lehey at "Aug 1, 97 01:22:00 pm" To: grog@lemis.com (Greg Lehey) Date: Fri, 1 Aug 1997 13:24:48 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, brian@awfulhak.org, grog@lemis.com, 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: > >> > >> Arrrghhhhhh ! Your mailer is gobbling the "open square brace" > >> characters ! That is *NOT* what I posted. There are two opening > >> brackets prior to the ``cc'' that something's eating. > > > > Greg is almost certainly using supercite inside emacs. Bad boy! > > No. Real Hackers write their own Emacs macros. And they don't always > work right. "almost" 8) You should be using it, then 8) > >> I'm sure we can all agree that this means the above usage (with the > >> two wandering brackets included) is correct ? > > > > Yes. > > Oh. > > Think-again-ing you what Me, or you? All he's proposing is to extend the current syntax so that if there are two more digits than expected, they're interpreted as the century. Sounds eminently sensible to me... If you want to go completely nuts, I'm sure you can find a date-parsing library out there that will let you say things like 'date three weeks ago' > Grog -- ]] 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 Thu Jul 31 20:58:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA23638 for hackers-outgoing; Thu, 31 Jul 1997 20:58:14 -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 UAA23605 for ; Thu, 31 Jul 1997 20:57:47 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA02814; Fri, 1 Aug 1997 13:27:40 +0930 (CST) From: Michael Smith Message-Id: <199708010357.NAA02814@genesis.atrad.adelaide.edu.au> Subject: Updated Wavelan code in -current To: hackers@freebsd.org, wavelan@smith.net.au Date: Fri, 1 Aug 1997 13:27:39 +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 punters; if you're running a Wavelan and have -current lying around, I've just updated the driver to Jim Binkley's latest work. This includes various new features and more useful documentation. I'd be particularly interested to hear of any problems with this code, as I'd like to bring it back into 2.2 fairly soon. -- ]] 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 Thu Jul 31 21:18:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA24650 for hackers-outgoing; Thu, 31 Jul 1997 21:18:17 -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 VAA24632 for ; Thu, 31 Jul 1997 21:17:35 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id NAA03134; Fri, 1 Aug 1997 13:47:23 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id NAA08639; Fri, 1 Aug 1997 13:47:22 +0930 (CST) Message-Id: <199708010417.NAA08639@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010415.VAA13820@kithrup.com> from Sean Eric Fagan at "Jul 31, 97 09:15:09 pm" To: sef@Kithrup.COM (Sean Eric Fagan) Date: Fri, 1 Aug 1997 13:47:22 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers) 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-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 Sean Eric Fagan writes: > In article <199708010239.MAA08318.kithrup.freebsd.hackers@freebie.lemis.com> you write: >> Now here's an enhancement that I *would* like to see: specify a >> timezone file to use. Something like: >> >> $ date -z /usr/share/zoneinfo/Asia/Tokyo >> >> to give you the current time in Tokyo. > > You can already do that, using $TZ. > > E.g., > > kithrup 1% date > Thu Jul 31 21:11:01 PDT 1997 > kithrup 2% env TZ=Asia/Tokyo date > Fri Aug 1 13:11:21 JST 1997 Just what I need. Thanks! Greg From owner-freebsd-hackers Thu Jul 31 21:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA24898 for hackers-outgoing; Thu, 31 Jul 1997 21:21:19 -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 VAA24888 for ; Thu, 31 Jul 1997 21:21:14 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id AAA01912; Fri, 1 Aug 1997 00:21:20 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id AAA06960; Fri, 1 Aug 1997 00:21:34 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Fri, 1 Aug 1997 00:21:33 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca To: Greg Lehey cc: Brian Somers , FreeBSD Hackers Subject: Re: date(1) In-Reply-To: <199708010208.LAA08172@freebie.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 On Fri, 1 Aug 1997, Greg Lehey wrote: > I think this confusion is making my point: the syntax is too > complicated. I understand the [...] to mean optional parts. In this > case, we have two unbalanced ]s: > > cc[yy[mm[dd[hh]]]]]mm[.ss]] > ^ ^ > | | I saw this later, too. It turns out that there should be two brackets preceding `cc'. That is a simple, normal, logical extension. > Most newcomers to UNIX hate date(1) because the date entry format is > already too cryptic. This would just make it worse. There are some I disagree. Calling on my experience as a newcomer, what was cryptic was the format used to print the date (eg. date ``+DATE: %m/%d/%y%nTIME: %H:%M:%S''). Once I realized that printing and setting the date were two different things, and that the syntax for setting the date was simply [[yy[mm[dd[hh]]]]mm[.ss]] It was very easy. However, before realizing this, I did get frustrated with the syntax. I wouldn't mind seeing the manpage simplified. > other alternatives for date entry--tar uses one, for example, though > it may be GNU code. Why not base an implementation on one of those? Because POSIX specifies the proper format for date(1)? I don't know how much POSIX specifies, but I rather suspect some new arcane "user-friendly" entry format is outlawed. Of course, in the interest of script-portability, we should not extend date(1) at all. Anyone trying to enter the century should get an error. This is the whole purpose of Posix, to increase portability. By creating extensions to it, we defeat the whole purpose just for the sake of creating a better operating system. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Thu Jul 31 21:52:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26872 for hackers-outgoing; Thu, 31 Jul 1997 21:52:05 -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 VAA26736 for ; Thu, 31 Jul 1997 21:50:32 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA06838; Fri, 1 Aug 1997 05:02:11 +0200 From: Luigi Rizzo Message-Id: <199708010302.FAA06838@labinfo.iet.unipi.it> Subject: device close behaviour - a question To: hackers@freebsd.org Date: Fri, 1 Aug 1997 05:02:11 +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 Hi, I am having a problem related to the having multiple (actually, 2) open descriptors on the same character device. More specifically, I notice that only the last close does actually invoke the device close routine. >From the code in /sys/miscfs/specfs/spec_vnops.c, function spec_close(), this behaviour seems intentional. But can someone explain why this is done and where this is useful ? I do not dare to suggest that this be changed since I guess it would break many things... or not ? In my case, I have implemented the ability of having up to two open descriptors on full-duplex audio devices, one for read and one for write. The above behaviour does not let me record that a channel has been freed (this I would have done using the close() call), and complicates life to the driver since it has to guess what is happening. I do have locks on concurrent operations of the same type, and have implemented some hacks to (more or less) control that proper device usage is done. However, these are hacks, and the lack of information can cause suboptimal behaviours. As an example, due to the missing close I cannot decide to stop a DMA read since I don't know if the reading process has gone. 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 Thu Jul 31 21:52:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26891 for hackers-outgoing; Thu, 31 Jul 1997 21:52:06 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26809 for ; Thu, 31 Jul 1997 21:52:01 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.6/8.7.3) with SMTP id AAA12016; Fri, 1 Aug 1997 00:51:20 -0400 (EDT) Message-Id: <199708010451.AAA12016@whizzo.TransSys.COM> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: brian@awfulhak.org (Brian Somers), hackers@FreeBSD.ORG (FreeBSD Hackers) From: "Louis A. Mamakos" Subject: Re: date(1) References: <199708010239.MAA08318@freebie.lemis.com> In-reply-to: Your message of "Fri, 01 Aug 1997 12:09:06 +0930." <199708010239.MAA08318@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Aug 1997 00:51:20 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Now here's an enhancement that I *would* like to see: specify a > timezone file to use. Something like: > > $ date -z /usr/share/zoneinfo/Asia/Tokyo > Just set the TZ env var when you invoke the command: $ TZ=Asia/Tokyo date Fri Aug 1 13:49:34 JST 1997 louie From owner-freebsd-hackers Thu Jul 31 22:00:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27738 for hackers-outgoing; Thu, 31 Jul 1997 22:00:20 -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 WAA27722 for ; Thu, 31 Jul 1997 22:00:15 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id OAA03410; Fri, 1 Aug 1997 14:30:01 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id OAA08806; Fri, 1 Aug 1997 14:30:00 +0930 (CST) Message-Id: <199708010500.OAA08806@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <199708010451.AAA12016@whizzo.TransSys.COM> from "Louis A. Mamakos" at "Aug 1, 97 00:51:20 am" To: louie@TransSys.COM (Louis A. Mamakos) Date: Fri, 1 Aug 1997 14:30:00 +0930 (CST) Cc: grog@lemis.com, brian@awfulhak.org, hackers@FreeBSD.ORG 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-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 Louis A. Mamakos writes: > >> Now here's an enhancement that I *would* like to see: specify a >> timezone file to use. Something like: >> >> $ date -z /usr/share/zoneinfo/Asia/Tokyo >> > > Just set the TZ env var when you invoke the command: > > $ TZ=Asia/Tokyo date > Fri Aug 1 13:49:34 JST 1997 Thanks. sef got there first in a private mail, but it's just the thing I was looking for. Greg From owner-freebsd-hackers Thu Jul 31 22:19:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA28817 for hackers-outgoing; Thu, 31 Jul 1997 22:19:19 -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 WAA28811 for ; Thu, 31 Jul 1997 22:19:16 -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 WAA28426; Thu, 31 Jul 1997 22:18:31 -0700 (PDT) To: Greg Lehey cc: brian@awfulhak.org (Brian Somers), hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 12:09:06 +0930." <199708010239.MAA08318@freebie.lemis.com> Date: Thu, 31 Jul 1997 22:18:31 -0700 Message-ID: <28422.870412711@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Now here's an enhancement that I *would* like to see: specify a > timezone file to use. Something like: > > $ date -z /usr/share/zoneinfo/Asia/Tokyo > > to give you the current time in Tokyo. Blah. What's wrong with: jkh@time-> TZ=Asia/Tokyo date Fri Aug 1 14:18:15 JST 1997 ? From owner-freebsd-hackers Thu Jul 31 22:26:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29201 for hackers-outgoing; Thu, 31 Jul 1997 22:26:37 -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 WAA29192 for ; Thu, 31 Jul 1997 22:26:31 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id OAA03568; Fri, 1 Aug 1997 14:56:23 +0930 (CST) From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.6/8.6.12) id OAA08967; Fri, 1 Aug 1997 14:56:21 +0930 (CST) Message-Id: <199708010526.OAA08967@freebie.lemis.com> Subject: Re: date(1) In-Reply-To: <28422.870412711@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 31, 97 10:18:31 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 1 Aug 1997 14:56:21 +0930 (CST) Cc: grog@lemis.com, brian@awfulhak.org, hackers@FreeBSD.ORG 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-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 Jordan K. Hubbard writes: >> Now here's an enhancement that I *would* like to see: specify a >> timezone file to use. Something like: >> >> $ date -z /usr/share/zoneinfo/Asia/Tokyo >> >> to give you the current time in Tokyo. > > Blah. What's wrong with: > > jkh@time-> TZ=Asia/Tokyo date > Fri Aug 1 14:18:15 JST 1997 > > ? 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. From owner-freebsd-hackers Thu Jul 31 22:32:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29680 for hackers-outgoing; Thu, 31 Jul 1997 22:32:49 -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 WAA29666 for ; Thu, 31 Jul 1997 22:32:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA03720; Fri, 1 Aug 1997 15:01:24 +0930 (CST) From: Michael Smith Message-Id: <199708010531.PAA03720@genesis.atrad.adelaide.edu.au> Subject: Re: device close behaviour - a question In-Reply-To: <199708010302.FAA06838@labinfo.iet.unipi.it> from Luigi Rizzo at "Aug 1, 97 05:02:11 am" To: luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Fri, 1 Aug 1997 15:01:23 +0930 (CST) Cc: 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 Luigi Rizzo stands accused of saying: > > I am having a problem related to the having multiple (actually, > 2) open descriptors on the same character device. More specifically, > I notice that only the last close does actually invoke the device > close routine. Heh. This one is tricky. > >From the code in /sys/miscfs/specfs/spec_vnops.c, function > spec_close(), this behaviour seems intentional. But can someone > explain why this is done and where this is useful ? > I do not dare to suggest that this be changed since I guess it would > break many things... or not ? Think about inheritance of fd's by a child process from the parent. > In my case, I have implemented the ability of having up to two open > descriptors on full-duplex audio devices, one for read and one for > write. The above behaviour does not let me record that a channel > has been freed (this I would have done using the close() call), > and complicates life to the driver since it has to guess what is > happening. You cannot ever guarantee any fixed number of openers on a device. -- ]] 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 Thu Jul 31 23:16:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02563 for hackers-outgoing; Thu, 31 Jul 1997 23:16: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 XAA02427; Thu, 31 Jul 1997 23:12:41 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA04240; Fri, 1 Aug 1997 15:42:24 +0930 (CST) From: Michael Smith Message-Id: <199708010612.PAA04240@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: <19970730203625.22764@mi.uni-koeln.de> from Stefan Esser at "Jul 30, 97 08:36:26 pm" To: se@freebsd.org (Stefan Esser) Date: Fri, 1 Aug 1997 15:42:23 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mo@uu.net, 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 Stefan Esser stands accused of saying: > > > > I think I've found enough help to sort it out; I'd be more than > > happy to present you with an API of your choice on a platter. > > Thanks. Did you consider to commit the bios32.{c,h} files to > -current soon ? (Or did I just miss the commit message ?? :) Ask and ye shall receive. > If I know that the assembler part is working, I can easily > implement the missing interface code myself. This is probably > easier then specifying the API in text form ... Sure. Thanks to Jonathan Lemon for helping me with 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 Fri Aug 1 01:05:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA07758 for hackers-outgoing; Fri, 1 Aug 1997 01:05:51 -0700 (PDT) Received: from w2xo.pgh.pa.us (w2xo.pgh.pa.us [206.210.70.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA07753 for ; Fri, 1 Aug 1997 01:05:47 -0700 (PDT) Received: from w2xo.pgh.pa.us (localhost [127.0.0.1]) by w2xo.pgh.pa.us (8.8.4/8.8.4) with SMTP id EAA04921 for ; Fri, 1 Aug 1997 04:06:02 -0400 (EDT) Message-ID: <33E198E9.2781E494@w2xo.pgh.pa.us> Date: Fri, 01 Aug 1997 04:06:01 -0400 From: Jim Durham Organization: Dis- X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.7-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: re: generic PCI card Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to Michael Smith, Vinnay Bannai and Stefan Esser, who replied to my posting. Michael Smith wrote: > > Spot on. If you boot with '-v' you will get a listing of the > vendor and board ID numbers, which you can plug in there. Could you > please let us know what these numbers are when you've got them so > that other people can benefit? Either mail the hardware list, or > send the details straight to Stefan (se@freebsd.org). > I will attempt to do same and Stefan, I will get you the info on the marketing name, etc. Have to wait until I have time to attack it this weekend. Thanks, Jim Durham From owner-freebsd-hackers Fri Aug 1 02:04:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA10422 for hackers-outgoing; Fri, 1 Aug 1997 02:04:45 -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 CAA10415; Fri, 1 Aug 1997 02:04:40 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id CAA00641; Fri, 1 Aug 1997 02:04:39 -0700 (PDT) Message-Id: <199708010904.CAA00641@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 to: multimedia@FreeBSD.ORG cc: hackers@FreeBSD.ORG Date: Fri, 01 Aug 1997 02:04:37 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Subject: Re: working snap of new sound driver In-reply-to: Your message of "Thu, 31 Jul 1997 16:34:42 +0200." <199707311434.QAA05841@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii -------- Well folks , Any feedback 8) Hint: Now is a good time to join in the hacking frenzy Tnks, Amancio >From The Desk Of Luigi Rizzo : > After about two weeks of intense development, I am pleased to say that > all the major pieces of my new sound driver now work satisfactorily. As > a consequence, a _working_ snap of my new sound driver is available at > > http://www.iet.unipi.it/~luigi/snd970731.tgz > > (I am running this code on my machine now). > > The package includes a README file with detailed installation > instructions, and all the pieces you need if you are using 2.2 or > above. At the time of this writing I fixed the final bugs and > /dev/audio works reliably (at 8KHz, mono) with MSS-clones and SBpro > (tested used the CS4232 and CS4236 PnP). > > PnP cards are supported (with a minor fix, you need to change the > probe routine in ad1848.c to add the ID for your card), and possibly > even multiple sound cards in the same system (if bugs are present, > they are in the PnP probe&configure code). > > Many ioctls are still unimplemented (but the mixer calls work), but > fixing them will be trivial and probably ready for the next snap. > > Do not expect any new release for a week or so, but I will be able to > read email and reply. PLEASE if you have the time, test the code > with your cards. I am running this code on my machine at the moment, > and it seems reasonably stable. > > 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 1 03:04:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA12558 for hackers-outgoing; Fri, 1 Aug 1997 03:04:51 -0700 (PDT) Received: from konig.elte.hu (konig.elte.hu [157.181.6.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA12550 for ; Fri, 1 Aug 1997 03:04:39 -0700 (PDT) Received: from localhost (sebesty@localhost) by konig.elte.hu (8.8.3/8.7.3/7s) with SMTP id MAA14135 for ; Fri, 1 Aug 1997 12:03:42 +0200 Date: Fri, 1 Aug 1997 12:03:41 +0200 (MET DST) From: Zoltan Sebestyen X-Sender: sebesty@konig Reply-To: Zoltan Sebestyen To: FreeBSD hackers mailinglist Subject: ATAPI doc 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 searching for some online documentation about IDE-ATAPI cdroms, especially how they communicate with the PC. -------------------------------------------------------------------------------- Sebestyen Zoltan It all seems so stupid, it makes me want to give up. szoli@caesar.elte.hu But why should I give up, when it all seems so stupid? From owner-freebsd-hackers Fri Aug 1 07:01:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA21418 for hackers-outgoing; Fri, 1 Aug 1997 07:01:35 -0700 (PDT) Received: from dublin.iona.ie (root@operation.dublin.iona.ie [192.122.221.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA21413 for ; Fri, 1 Aug 1997 07:01:28 -0700 (PDT) Received: from ultra (ultra [192.122.221.136]) by dublin.iona.ie (8.7.5/jm-1.01) with SMTP id PAA20458 for ; Fri, 1 Aug 1997 15:01:40 +0100 (BST) Date: Fri, 1 Aug 1997 15:01:19 +0100 (BST) From: Niall Smart X-Sender: nsmart@ultra To: freebsd-hackers@freebsd.org Subject: strace for FreeBSD? Message-ID: X-IONA-Employee-Number: 12992 X-IONA-Department: Customer Engineering MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, As far as I can see strace has not been ported to FreeBSD, does anyone know if porting this tool would be a major effort? It is a great deal better than ktrace IMO. -- Niall Smart Customer Engineering, IONA Technologies. (www.iona.com) From owner-freebsd-hackers Fri Aug 1 08:14:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24514 for hackers-outgoing; Fri, 1 Aug 1997 08:14:45 -0700 (PDT) Received: from labs.usn.blaze.net.au (root@labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA24503 for ; Fri, 1 Aug 1997 08:14:33 -0700 (PDT) Received: from labs.usn.blaze.net.au (davidn@local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id BAA03391; Sat, 2 Aug 1997 01:13:35 +1000 (EST) Message-Id: <199708011513.BAA03391@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Keith Mitchell cc: hackers@FreeBSD.ORG Subject: Re: Bug in pw? (account/pasword exp dates) In-reply-to: Your message of "Tue, 29 Jul 1997 17:13:05 -0400." <199707292113.RAA14306@weenix.guru.org> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Aug 1997 01:13:35 +1000 From: David Nugent Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> If I give pw the following command: >> >> pw useradd tuser -P -c "Test User" -e 901944000 -p 869834290 -m -h 0 >> >> everything seems to work except that the account expiration date and the >> password expiration date are set to the same thing (to the -e param). > > I think I found the bug. In pw_pwdpolicy it tests for a -e instead of the -p. > The following patched seemingly fixed the problem. Thanks, I committed this fix to all three branches. Could I suggest in future that this sort of thing be sent into the bugs database via send-pr? I only get to the hackers mailing list if I have time, and if I get too far behind, I'll just delete anything older than a few days to catch up. So there is no guarantees that I'll see it except via gnats - which I do read scrupulously. Regards, David -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-hackers Fri Aug 1 08:35:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA25390 for hackers-outgoing; Fri, 1 Aug 1997 08:35:33 -0700 (PDT) Received: from netroplex.com (ns1.netroplex.com [206.171.95.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA25383 for ; Fri, 1 Aug 1997 08:35:15 -0700 (PDT) Received: from default (max008-90.netroplex.com [207.212.27.90]) by netroplex.com (8.8.5/8.8.2) with SMTP id IAA21395 for ; Fri, 1 Aug 1997 08:35:47 -0700 (PDT) Message-Id: <199708011535.IAA21395@netroplex.com> From: "Rod Ebrahimi" To: "FreeBSD Help" Subject: IE4 Channels Date: Fri, 1 Aug 1997 08:33:54 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01BC9E55.A5C39B80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0000_01BC9E55.A5C39B80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Has anyone ever tried to host IE4 Pre2 Channels on FreeBSD? Or do those = only run on WinNT? Thank you... ------=_NextPart_000_0000_01BC9E55.A5C39B80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

 Has anyone ever = tried to host IE4=20 Pre2 Channels on FreeBSD? Or do those only run on WinNT?

 

Thank = you... ------=_NextPart_000_0000_01BC9E55.A5C39B80-- From owner-freebsd-hackers Fri Aug 1 09:57:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29103 for hackers-outgoing; Fri, 1 Aug 1997 09:57:18 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29095 for ; Fri, 1 Aug 1997 09:57:15 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA03079; Fri, 1 Aug 1997 09:55:15 -0700 (PDT) Date: Fri, 1 Aug 1997 09:55:15 -0700 (PDT) From: Jim Shankland Message-Id: <199708011655.JAA03079@biggusdiskus.flyingfox.com> To: luigi@labinfo.iet.unipi.it, msmith@atrad.adelaide.edu.au Subject: Re: device close behaviour - a question Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Luigi Rizzo would like his audio driver to be notified every time the device is closed, not just on last close.] The way I've dealt with a similar situation in the past is to represent each physical device as an array of minor device numbers, on each of which the driver enforces an exclusive-open. User-level code must then iterate over the devices, until an open() call does not return EBUSY (just like looking for an available pty). Since each "device" is open at most once, the device_close() routine gets called on every user-level close() call. Hope this is useful. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Fri Aug 1 10:04:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29525 for hackers-outgoing; Fri, 1 Aug 1997 10:04:28 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29518 for ; Fri, 1 Aug 1997 10:04:24 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id NAA00308 for ; Fri, 1 Aug 1997 13:04:15 -0400 (EDT) Date: Fri, 1 Aug 1997 13:04:15 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: fs wierdness 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 Not entirely sure how this happened, but I was logged onto my system when (at least, have not found others) these following files were corrupted: /bin/mkdir /bin/mv /bin/pax /bin/ps They were corrupted to be character special files, with the same major/minors as /dev/ttyp0,/dev/pty0. I then fsck-ed the volume and it reported numerous errors with these files. the system 'had' an uptime of 25 days before this, without any other problems. Any idea what could have caused this? -- David Cross ACS Consultant From owner-freebsd-hackers Fri Aug 1 10:44:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01959 for hackers-outgoing; Fri, 1 Aug 1997 10: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 KAA01953 for ; Fri, 1 Aug 1997 10:44:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA09486; Fri, 1 Aug 1997 10:40:34 -0700 From: Terry Lambert Message-Id: <199708011740.KAA09486@phaeton.artisoft.com> Subject: Re: device close behaviour - a question To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 1 Aug 1997 10:40:34 -0700 (MST) Cc: luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: <199708010531.PAA03720@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 1, 97 03:01:23 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 am having a problem related to the having multiple (actually, > > 2) open descriptors on the same character device. More specifically, > > I notice that only the last close does actually invoke the device > > close routine. > > Heh. This one is tricky. Poul-Henning was talking about this before on the -current list. In general, I believe everyone agreed that it was desirable to differentiate between "close" and "last close" to provide for "per open instance" private data on devices. There is an issue on open, as well, since a device may be instanced once, but have multiple references created for it (Mike's inheritance of fd's on fork() or on exec() without the close-on-exec flag set via fcntl() is one example of this). The issue is that there is not a semantic seperation between reference instance vs. device instance at open time, so a close differentiation is less than useful. Both corrections would need to occur simultaneously for either one to be useful alone. > You cannot ever guarantee any fixed number of openers on a device. O_EXCL or function equivalent. 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 1 12:25:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07072 for hackers-outgoing; Fri, 1 Aug 1997 12:25:13 -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 MAA07057 for ; Fri, 1 Aug 1997 12:25:07 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id MAA05657; Fri, 1 Aug 1997 12:23:48 -0700 (PDT) Message-Id: <199708011923.MAA05657@rah.star-gate.com> To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG Subject: Re: device close behaviour - a question In-reply-to: Your message of "Fri, 01 Aug 1997 10:40:34 PDT." <199708011740.KAA09486@phaeton.artisoft.com> Date: Fri, 01 Aug 1997 12:23:48 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Curious, shouldn't the responsibility of managing the behavior of open/close fall on the device driver . After all the driver should dictate whether it can manage multiple open instances. As for determining whether there are multiple opens on a device we can create an ioctl which returns the number of opens . Ideally, it should return instances of the states for each open. Amancio >From The Desk Of Terry Lambert : > > > I am having a problem related to the having multiple (actually, > > > 2) open descriptors on the same character device. More specifically, > > > I notice that only the last close does actually invoke the device > > > close routine. > > > > Heh. This one is tricky. > > Poul-Henning was talking about this before on the -current list. > > In general, I believe everyone agreed that it was desirable to > differentiate between "close" and "last close" to provide for > "per open instance" private data on devices. > > There is an issue on open, as well, since a device may be > instanced once, but have multiple references created for it > (Mike's inheritance of fd's on fork() or on exec() without > the close-on-exec flag set via fcntl() is one example of this). > > The issue is that there is not a semantic seperation between > reference instance vs. device instance at open time, so a close > differentiation is less than useful. Both corrections would > need to occur simultaneously for either one to be useful alone. > > > > You cannot ever guarantee any fixed number of openers on a device. > > O_EXCL or function equivalent. > > > 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 1 12:32:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07563 for hackers-outgoing; Fri, 1 Aug 1997 12:32:41 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA07554 for ; Fri, 1 Aug 1997 12:32:36 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA04334; Fri, 1 Aug 1997 12:32:25 -0700 Date: Fri, 1 Aug 1997 12:32:25 -0700 (PDT) From: "Brian N. Handy" To: hackers@freebsd.org Subject: Mail question Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey folks, This turned up in my maillog this morning: Aug 1 09:40:58 lambic sendmail[14378]: JAA14376: to="HK STATIONERY MFG. CO., LTD." , ctladdr=handy (9956/9956), delay=00:00:34, xdelay=00:00:29, mailer=esmtp, relay=mail.asiaonline.net. [202.85.0.1], stat=Sent (AAA22758 Message accepted for delivery) It seems to suggest to me I'm being used as a relay for somebody, but I don't understand the lingo well enough to really be able to tell. I remember the recent thread on dealing with being exploited as a relay, though if there was a fix listed there, I missed it. So -- (1) Does the above log entry hold any significance to me, and (2) What's the fix to my sendmail.cf to turn off this relay business? Thanks, Brian From owner-freebsd-hackers Fri Aug 1 13:00:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08735 for hackers-outgoing; Fri, 1 Aug 1997 13:00:31 -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 NAA08729 for ; Fri, 1 Aug 1997 13:00:24 -0700 (PDT) Received: (qmail 5695 invoked by uid 1000); 1 Aug 1997 20:00:25 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 01 Aug 1997 13:00:25 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.ORG Subject: Kernel howto, Second Request Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Old, unanswered question: How do I find the following, from a device driver? Drive Type in CMOS Drive 0 Drive Type in CMOS Drive 1 Number of drives (in CMOS location 40:75 Processor Family (i386 vs. Alpha, etc.) Procesor Type (386 vs. 486 vs. P5 vs P6, etc.) OS Major Version (version 1 vs. 2. vs 3 ) OS minor Version (x.1, etc.) OS Revision (or build number) Next Question: What is the equivalent of SysV physmap()? Physmap takes a physical memory address and returns a virtual address. I am trying to access certain memory location only known by physical addresses. Thanx, Simon From owner-freebsd-hackers Fri Aug 1 13:48:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11371 for hackers-outgoing; Fri, 1 Aug 1997 13:48:15 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.DPCSYS.com [209.25.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11356 for ; Fri, 1 Aug 1997 13:48:08 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id UAA02605; Fri, 1 Aug 1997 20:47:55 GMT Date: Fri, 1 Aug 1997 13:47:54 -0700 (PDT) From: Dan Busarow To: "Brian N. Handy" cc: hackers@FreeBSD.ORG Subject: Re: Mail question 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 Fri, 1 Aug 1997, Brian N. Handy wrote: > Aug 1 09:40:58 lambic sendmail[14378]: JAA14376: to="HK STATIONERY MFG. > CO., LTD." , ctladdr=handy (9956/9956), delay=00:00:34, > xdelay=00:00:29, mailer=esmtp, relay=mail.asiaonline.net. [202.85.0.1], > stat=Sent (AAA22758 Message accepted for delivery) Looks more like you replied to a mailing list question from someone in HK :) ctladdr is the sender (you), to is victorwu@hksm.com and relay is the correct MX for hksm.com > (1) Does the above log entry hold any significance to me, and Not going by that entry alone. > (2) What's the fix to my sendmail.cf to turn off this relay business? Goto http://www.informatik.uni-kiel.de/%7Eca/email/check.html and see the check_rcpt ruleset. These may have aleady been folded into -release or -current, there was talk of that quite a while back. You still need to turn them on by supplying the supporting data files. If you have trouble figuring out how the rules work I have a line by line description at http://www.beach.net/~dan Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Fri Aug 1 14:05:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12139 for hackers-outgoing; Fri, 1 Aug 1997 14:05:30 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA12133 for ; Fri, 1 Aug 1997 14:05:25 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA06251; Fri, 1 Aug 1997 14:05:26 -0700 Date: Fri, 1 Aug 1997 14:05:26 -0700 (PDT) From: "Brian N. Handy" To: Dan Busarow Cc: hackers@FreeBSD.ORG Subject: Re: Mail question In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Looks more like you replied to a mailing list question from someone >in HK :) ctladdr is the sender (you), to is victorwu@hksm.com and relay >is the correct MX for hksm.com Arrgh, after thinking about it a while longer it finally kicked in what that was, and ayep it was my fault. (sigh.) However, it did finally kick me into action to figure out how to turn some of this stuff off here at our site. > [check_* rules] >If you have trouble figuring out how the rules work I have a line by line >description at http://www.beach.net/~dan Hey, this looks great! I'll put some time into this over the weekend. Thanks! Cheers, Brian From owner-freebsd-hackers Fri Aug 1 14:18:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12874 for hackers-outgoing; Fri, 1 Aug 1997 14:18:50 -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 OAA12868 for ; Fri, 1 Aug 1997 14:18:45 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id QAA05888; Fri, 1 Aug 1997 16:18:33 -0500 (EST) From: "John S. Dyson" Message-Id: <199708012118.QAA05888@dyson.iquest.net> Subject: Re: Kernel howto, Second Request In-Reply-To: from Simon Shapiro at "Aug 1, 97 01:00:25 pm" To: Shimon@i-connect.net (Simon Shapiro) Date: Fri, 1 Aug 1997 16:18:33 -0500 (EST) Cc: 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 > > Next Question: What is the equivalent of SysV physmap()? > Physmap takes a physical memory address and returns a virtual address. > I am trying to access certain memory location only known by physical > addresses. > Unlike certain (broken) systems, FreeBSD doesn't map all of phys memory by default. This of course, saves address space for user processes, and keeps physical memory size from being constrained by kernel space limitations. /* Map memory mapped device */ va = kmem_alloc_pageable(kernel_map, size_in_bytes); for(indx = 0; indx < size_in_bytes; indx += PAGE_SIZE) pmap_kenter(va + indx, phys_addr + indx); /* do stuff here */ /* Now, unmap, release resources */ for(indx = 0; indx < size_in_bytes; indx += PAGE_SIZE) pmap_kremove(va + indx); kmem_free(kernel_map, va, size_in_bytes); Notes: You cannot do this at interrupt time, but there is a way to do it. Kernel_map is a limited resource, but don't worry about allocations of even 10-20MB. If you are going to use the resource for a long time, then don't allocate/free repeatedly unless you have to. I might have made a mistake, so RTSL :-). John From owner-freebsd-hackers Fri Aug 1 14:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14046 for hackers-outgoing; Fri, 1 Aug 1997 14:41:06 -0700 (PDT) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14037 for ; Fri, 1 Aug 1997 14:40:59 -0700 (PDT) Received: (from uucp@localhost) by DNS.Lamb.net (8.8.6/8.8.5) id OAA26860; Fri, 1 Aug 1997 14:40:50 -0700 (PDT) Received: from gatekeeper.Alameda.net(207.90.181.2) via SMTP by DNS.Lamb.net, id smtpd026858; Fri Aug 1 14:40:49 1997 Received: (from ulf@localhost) by Gatekeeper.Alameda.net (8.8.6/8.7.6) id OAA21956; Fri, 1 Aug 1997 14:40:43 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199708012140.OAA21956@Gatekeeper.Alameda.net> Subject: Re: Mail question In-Reply-To: from "Brian N. Handy" at "Aug 1, 97 02:05:26 pm" To: handy@sag.space.lockheed.com (Brian N. Handy) Date: Fri, 1 Aug 1997 14:40:42 -0700 (PDT) Cc: dan@dpcsys.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 I would also take a lok at smtpd from the Juniper firewall toolkit. http://www.obtuse.com/ It has in the SMTP receiving part filters for allowing many things. the newest beta which should out in the next days, has even regular expression to help match certain spammers. > > >Looks more like you replied to a mailing list question from someone > >in HK :) ctladdr is the sender (you), to is victorwu@hksm.com and relay > >is the correct MX for hksm.com > > Arrgh, after thinking about it a while longer it finally kicked in what > that was, and ayep it was my fault. (sigh.) However, it did finally kick > me into action to figure out how to turn some of this stuff off here at > our site. > > > [check_* rules] > >If you have trouble figuring out how the rules work I have a line by line > >description at http://www.beach.net/~dan > > Hey, this looks great! I'll put some time into this over the weekend. > Thanks! > > > Cheers, > > Brian > > -- Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 From owner-freebsd-hackers Fri Aug 1 14:50:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14353 for hackers-outgoing; Fri, 1 Aug 1997 14:50:49 -0700 (PDT) Received: from jenolan.rutgers.edu (davem@jenolan.rutgers.edu [128.6.111.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14348 for ; Fri, 1 Aug 1997 14:50:47 -0700 (PDT) Received: (from davem@localhost) by jenolan.rutgers.edu (8.8.5/8.8.5) id RAA03675; Fri, 1 Aug 1997 17:50:03 -0400 Date: Fri, 1 Aug 1997 17:50:03 -0400 Message-Id: <199708012150.RAA03675@jenolan.rutgers.edu> From: "David S. Miller" To: toor@dyson.iquest.net CC: Shimon@i-connect.net, FreeBSD-Hackers@FreeBSD.ORG In-reply-to: <199708012118.QAA05888@dyson.iquest.net> (toor@dyson.iquest.net) Subject: Re: Kernel howto, Second Request Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: "John S. Dyson" Date: Fri, 1 Aug 1997 16:18:33 -0500 (EST) Unlike certain (broken) systems, FreeBSD doesn't map all of phys memory by default. This of course, saves address space for user processes, and keeps physical memory size from being constrained by kernel space limitations. Yes, but please do not ignore the fact that on modern architectures (read as: 64-bit) it lacks any these limitations. (for example, on the UltraSparc under Linux, the full 64-bit virtual address space is given to the user, and arbitrarily large physical memory configurations are supported, all this is done at zero cost, and it's possible to be zero cost because of this "broken" system's design). Not to mention the fact that in many cases it also makes SMP cheaper (Linux only performs tlb flush cross calls during swapping, ptrace(), and for user threads). Later, David "Sparc" Miller davem@caip.rutgers.edu From owner-freebsd-hackers Fri Aug 1 15:54:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16883 for hackers-outgoing; Fri, 1 Aug 1997 15:54:22 -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 PAA16876 for ; Fri, 1 Aug 1997 15:54:17 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id RAA06093; Fri, 1 Aug 1997 17:42:48 -0500 (EST) From: "John S. Dyson" Message-Id: <199708012242.RAA06093@dyson.iquest.net> Subject: Re: Kernel howto, Second Request In-Reply-To: <199708012150.RAA03675@jenolan.rutgers.edu> from "David S. Miller" at "Aug 1, 97 05:50:03 pm" To: davem@jenolan.rutgers.edu (David S. Miller) Date: Fri, 1 Aug 1997 17:42:48 -0500 (EST) Cc: toor@dyson.iquest.net, Shimon@i-connect.net, 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 > From: "John S. Dyson" > Date: Fri, 1 Aug 1997 16:18:33 -0500 (EST) > > Unlike certain (broken) systems, FreeBSD doesn't map all of phys > memory by default. This of course, saves address space for user > processes, and keeps physical memory size from being constrained by > kernel space limitations. > > Yes, but please do not ignore the fact that on modern architectures > (read as: 64-bit) it lacks any these limitations. (for example, on > the UltraSparc under Linux, the full 64-bit virtual address space is > given to the user, and arbitrarily large physical memory > configurations are supported, all this is done at zero cost, and it's > possible to be zero cost because of this "broken" system's design). > Not to mention the fact that in many cases it also makes SMP cheaper > (Linux only performs tlb flush cross calls during swapping, ptrace(), > and for user threads). > The problem is that we are getting questions about large systems now, and limiting phys mem is not an option for us on the PPro. Also, in FreeBSD if you want a mapping to stay around, you can leave it there. (I didn't realize that Linux mapped all of memory anyway, or does it?) I agree that on some architectures mapping all of memory into the kernel is almost free. On other architectures you don't have a choice, and on an X86 it is likely not needed and wasteful. Note that just because of a kernel mapping change it doesn't mean that a TLB flush is needed on ALL processors in every circumstance -- we currently do so too often, but it is only a matter of convienience (read laziness) right now. I have been working/studying the issue of more intelligent (and deferred) shootdowns, and will have some solutions soon, not be so lazy. Yep, for 64Bit architectures, it is probably okay to map all of physical memory -- but the generic kernel depending on it is a mistake (IMO.) There will be 32Bit machines in the future, where it can be advantageous to avoid mapping physical memory. The FreeBSD kernel structure as it is today can do with or without mapping physical memory, just as it can do with or without having the user process mapped when executing in the kernel. On PPros it appears that it is becoming a limitation in certain applications that I am supporting to restrict the physical memory to 1GByte or under -- and FreeBSD is even "limited" to approx 3GBytes (on a PPro.) All this said, I don't really know what Linux does, and that is likely a subject for a Linux mailing list or private email. :-). John dyson@freebsd.org From owner-freebsd-hackers Fri Aug 1 16:09:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA17571 for hackers-outgoing; Fri, 1 Aug 1997 16:09:53 -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 QAA17563 for ; Fri, 1 Aug 1997 16:09:46 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA09757; Fri, 1 Aug 1997 14:46:52 -0700 From: Terry Lambert Message-Id: <199708012146.OAA09757@phaeton.artisoft.com> Subject: Re: device close behaviour - a question To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 1 Aug 1997 14:46:52 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG In-Reply-To: <199708011923.MAA05657@rah.star-gate.com> from "Amancio Hasty" at Aug 1, 97 12:23:48 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 > Curious, shouldn't the responsibility of managing the behavior of > open/close fall on the device driver . After all the driver should > dictate whether it can manage multiple open instances. As for determining > whether there are multiple opens on a device we can create an ioctl > which returns the number of opens . Ideally, it should return instances > of the states for each open. The problem is that there is not an addref entry point for drivers. Specifically, when a process fork()'s, the new fd's are fd references to the same vnode, and an open is not called, and an "addref" that would add a reference instance is not called. One can not treat this reference creation as if it were an open, and call the open entry point. For one thing, there might be an implied exclusive use. For another, the open may not result in an identical descriptor... consider an open that completed because some condition (which is no longer true) was met. There needs to be a seperation of open instances from reference instances, and that's ll there is to 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 1 16:21:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA18080 for hackers-outgoing; Fri, 1 Aug 1997 16:21:54 -0700 (PDT) Received: from server.netplus.com.br (root@[200.247.23.97]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA18074 for ; Fri, 1 Aug 1997 16:21:46 -0700 (PDT) Received: from server.netplus.com.br (lenzi@server.netplus.com.br [200.247.23.97]) by server.netplus.com.br (8.8.5/8.8.5) with SMTP id UAA26024 for ; Fri, 1 Aug 1997 20:22:59 GMT Date: Fri, 1 Aug 1997 20:22:56 +0000 (GMT) From: Sergio Lenzi X-Sender: lenzi@server.netplus.com.br To: hackers@freebsd.org Subject: security hole on FreeBSD 2.2.2 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 Hello all Forgive me to send this message on this list. There is a security hole on FreeBSD 2.2.2 This is done using a script and a superl* on /usr/bin A friend of mine received root priority by telneting to my machine (2.2.2) and executing a perl script. My solution: remove /usr/bin/superl* Hope this can helphelp From owner-freebsd-hackers Fri Aug 1 16:52:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19732 for hackers-outgoing; Fri, 1 Aug 1997 16:52:56 -0700 (PDT) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19725 for ; Fri, 1 Aug 1997 16:52:53 -0700 (PDT) Received: from crocodile.vale.com (crocodile [192.168.128.47]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id SAA02269; Fri, 1 Aug 1997 18:52:45 -0500 (CDT) Received: (from daniel@localhost) by crocodile.vale.com (8.8.3/8.7.3) id SAA06962; Fri, 1 Aug 1997 18:52:45 -0500 (CDT) Date: Fri, 1 Aug 1997 18:52:44 -0500 (CDT) From: Dan Riley To: Sergio Lenzi cc: hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 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 Fri, 1 Aug 1997, Sergio Lenzi wrote: > > > > Hello all > > Forgive me to send this message on this list. > > There is a security hole on FreeBSD 2.2.2 > > This is done using a script and a superl* on /usr/bin > > A friend of mine received root priority by telneting to my machine (2.2.2) > and executing a perl script. > > My solution: remove /usr/bin/superl* > > Hope this can helphelp > Ditto, at least 3 of my machines were hacked using this method, all of which were installed last week. (2.2.2-R) From owner-freebsd-hackers Fri Aug 1 17:00:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA20332 for hackers-outgoing; Fri, 1 Aug 1997 17:00:50 -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 RAA20327 for ; Fri, 1 Aug 1997 17:00:48 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id UAA26527; Fri, 1 Aug 1997 20:06:59 -0400 Date: Fri, 1 Aug 1997 20:06:59 -0400 (EDT) From: Ben Black To: Sergio Lenzi cc: hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 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 wow, with a problem report like that i'll be sure to get right on removing superl. how about a copy of the script or an explanaition of the bug? On Fri, 1 Aug 1997, Sergio Lenzi wrote: > > > > Hello all > > Forgive me to send this message on this list. > > There is a security hole on FreeBSD 2.2.2 > > This is done using a script and a superl* on /usr/bin > > A friend of mine received root priority by telneting to my machine (2.2.2) > and executing a perl script. > > My solution: remove /usr/bin/superl* > > Hope this can helphelp > > From owner-freebsd-hackers Fri Aug 1 17:15:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21043 for hackers-outgoing; Fri, 1 Aug 1997 17:15:36 -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 RAA21037 for ; Fri, 1 Aug 1997 17:15:33 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wuRqq-00029H-00; Fri, 1 Aug 1997 17:15:20 -0700 Date: Fri, 1 Aug 1997 17:15:19 -0700 (PDT) From: Tom Samplonius To: Dan Riley cc: Sergio Lenzi , hackers@freebsd.org Subject: Re: security hole on FreeBSD 2.2.2 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 Fri, 1 Aug 1997, Dan Riley wrote: > > > On Fri, 1 Aug 1997, Sergio Lenzi wrote: > > > > > > > > > Hello all > > > > Forgive me to send this message on this list. > > > > There is a security hole on FreeBSD 2.2.2 > > > > This is done using a script and a superl* on /usr/bin > > > > A friend of mine received root priority by telneting to my machine (2.2.2) > > and executing a perl script. > > > > My solution: remove /usr/bin/superl* > > > > Hope this can helphelp > > > > Ditto, at least 3 of my machines were hacked using this method, all of > which were installed last week. (2.2.2-R) > > > Huh? I'm looking at /usr/bin/ on couple of 2.2.2 machines and there is no superl*... what is that file supposed to be anyhow? Are you sure you did not install from a tainted distribution that had a backdoor installed? Or, were you fooled in running a trojan horse as root and it created the superl* file? Tom From owner-freebsd-hackers Fri Aug 1 17:19:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21190 for hackers-outgoing; Fri, 1 Aug 1997 17:19:13 -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 RAA21183 for ; Fri, 1 Aug 1997 17:19:07 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wuRuD-00029S-00; Fri, 1 Aug 1997 17:18:49 -0700 Date: Fri, 1 Aug 1997 17:18:48 -0700 (PDT) From: Tom Samplonius To: Ben Black cc: Sergio Lenzi , hackers@freebsd.org Subject: Re: security hole on FreeBSD 2.2.2 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 Fri, 1 Aug 1997, Ben Black wrote: > wow, with a problem report like that i'll be sure to get right on > removing superl. how about a copy of the script or an explanaition of > the bug? But what the hell is superl? I don't think it comes with 2.2.2. Tom > On Fri, 1 Aug 1997, Sergio Lenzi wrote: > > > > > > > > > Hello all > > > > Forgive me to send this message on this list. > > > > There is a security hole on FreeBSD 2.2.2 > > > > This is done using a script and a superl* on /usr/bin > > > > A friend of mine received root priority by telneting to my machine (2.2.2) > > and executing a perl script. > > > > My solution: remove /usr/bin/superl* > > > > Hope this can helphelp > > > > > > From owner-freebsd-hackers Fri Aug 1 17:23:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21505 for hackers-outgoing; Fri, 1 Aug 1997 17:23:10 -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 RAA21492 for ; Fri, 1 Aug 1997 17:23:02 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id UAA26904; Fri, 1 Aug 1997 20:29:11 -0400 Date: Fri, 1 Aug 1997 20:29:11 -0400 (EDT) From: Ben Black To: Tom Samplonius cc: Sergio Lenzi , hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 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 exactly. i have no clue what this guy is talking about. On Fri, 1 Aug 1997, Tom Samplonius wrote: > > On Fri, 1 Aug 1997, Ben Black wrote: > > > wow, with a problem report like that i'll be sure to get right on > > removing superl. how about a copy of the script or an explanaition of > > the bug? > > But what the hell is superl? I don't think it comes with 2.2.2. > > Tom > > > > On Fri, 1 Aug 1997, Sergio Lenzi wrote: > > > > > > > > > > > > > > Hello all > > > > > > Forgive me to send this message on this list. > > > > > > There is a security hole on FreeBSD 2.2.2 > > > > > > This is done using a script and a superl* on /usr/bin > > > > > > A friend of mine received root priority by telneting to my machine (2.2.2) > > > and executing a perl script. > > > > > > My solution: remove /usr/bin/superl* > > > > > > Hope this can helphelp > > > > > > > > > > > From owner-freebsd-hackers Fri Aug 1 17:26:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21671 for hackers-outgoing; Fri, 1 Aug 1997 17:26:39 -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 RAA21661 for ; Fri, 1 Aug 1997 17:26:36 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wuS1Y-00029i-00; Fri, 1 Aug 1997 17:26:24 -0700 Date: Fri, 1 Aug 1997 17:26:23 -0700 (PDT) From: Tom Samplonius To: Ben Black cc: Sergio Lenzi , hackers@freebsd.org Subject: Re: security hole on FreeBSD 2.2.2 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 Fri, 1 Aug 1997, Ben Black wrote: > exactly. i have no clue what this guy is talking about. Exactly. It looks like this guy installed some bogus software, probably setuid to root, that has a gaping hole in it. Tom From owner-freebsd-hackers Fri Aug 1 17:41:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA22315 for hackers-outgoing; Fri, 1 Aug 1997 17:41:14 -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 RAA22308 for ; Fri, 1 Aug 1997 17:41:12 -0700 (PDT) Received: (qmail 10478 invoked by uid 1000); 2 Aug 1997 00:41:27 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708012118.QAA05888@dyson.iquest.net> Date: Fri, 01 Aug 1997 17:41:27 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: "John S. Dyson" Subject: Re: Kernel howto, Second Request Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanx a million! Simon Hi "John S. Dyson"; On 01-Aug-97 you wrote: > > > > Next Question: What is the equivalent of SysV physmap()? > > Physmap takes a physical memory address and returns a virtual > address. > > I am trying to access certain memory location only known by physical > > addresses. > > > > Unlike certain (broken) systems, FreeBSD doesn't map all of phys memory > by default. This of course, saves address space for user processes, and > keeps physical memory size from being constrained by kernel space > limitations. > > /* Map memory mapped device */ > > va = kmem_alloc_pageable(kernel_map, size_in_bytes); > > for(indx = 0; indx < size_in_bytes; indx += PAGE_SIZE) > pmap_kenter(va + indx, phys_addr + indx); > > > > /* do stuff here */ > > > /* Now, unmap, release resources */ > > for(indx = 0; indx < size_in_bytes; indx += PAGE_SIZE) > pmap_kremove(va + indx); > > kmem_free(kernel_map, va, size_in_bytes); > > > Notes: > You cannot do this at interrupt time, but there is a way to do it. > Kernel_map is a limited resource, but don't worry about allocations > of even 10-20MB. > If you are going to use the resource for a long time, then don't > allocate/free repeatedly unless you have to. > I might have made a mistake, so RTSL :-). > > John > > From owner-freebsd-hackers Fri Aug 1 17:59:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23050 for hackers-outgoing; Fri, 1 Aug 1997 17:59:57 -0700 (PDT) Received: from rhiannon.clari.net.au (dns1.clari.net.au [203.27.85.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA23044 for ; Fri, 1 Aug 1997 17:59:53 -0700 (PDT) Received: (from root@localhost) by rhiannon.clari.net.au (8.8.5/8.8.5) id KAA20479; Sat, 2 Aug 1997 10:59:48 +1000 (EST) Date: Sat, 2 Aug 1997 10:59:48 +1000 (EST) From: Peter Hawkins Message-Id: <199708020059.KAA20479@rhiannon.clari.net.au> To: hackers@FreeBSD.ORG, handy@sag.space.lockheed.com Subject: Re: Mail question Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Danny O'Callahan wrote a fix that I think is excellent. it is available as a gz file from ftp.hilink.com.au. I have been using it for a while now but it really needs a man page. A few misconfigurations left my customers' mail inoperative for a day last week - make sure your domain is listed in the virtdomains file!! Peter From owner-freebsd-hackers Fri Aug 1 18:19:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23675 for hackers-outgoing; Fri, 1 Aug 1997 18:19:44 -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 SAA23670 for ; Fri, 1 Aug 1997 18:19:40 -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 SAA09101; Fri, 1 Aug 1997 18:18:48 -0700 (PDT) To: Dan Riley cc: Sergio Lenzi , hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 In-reply-to: Your message of "Fri, 01 Aug 1997 18:52:44 CDT." Date: Fri, 01 Aug 1997 18:18:47 -0700 Message-ID: <9097.870484727@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > There is a security hole on FreeBSD 2.2.2 Sigh.. I really wish people would read the CERT advisories (or make it a practice to visit www.cert.org occasionally) since otherwise what's the point of even releasing them? If you're running a FreeBSD machine for which public access is allowed then you MUST keep up to date on these advisories! This is not an optional exercise and the penalty for failing to keep up to date is to be hacked by those who DO read the advisories and are probably laughing their heads off as they nail another system admin who has failed to deal with a well-known security hole. It took me all of 30 seconds to track down: ftp://info.cert.org/pub/cert_advisories/CA-97.17.sperl This is also a topic for freebsd-security, not freebsd-hackers. Jordan From owner-freebsd-hackers Fri Aug 1 18:28:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24057 for hackers-outgoing; Fri, 1 Aug 1997 18:28:30 -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 SAA24052 for ; Fri, 1 Aug 1997 18:28:27 -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 SAA09163; Fri, 1 Aug 1997 18:27:32 -0700 (PDT) To: Tom Samplonius cc: Ben Black , Sergio Lenzi , hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 In-reply-to: Your message of "Fri, 01 Aug 1997 17:18:48 PDT." Date: Fri, 01 Aug 1997 18:27:32 -0700 Message-ID: <9160.870485252@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > But what the hell is superl? I don't think it comes with 2.2.2. I think he meant sperl, e.g. suidperl. Trusting perl to run as root strikes me as horrendously risky in any case, and perhaps it's time for us to just turn the damn thing off. The next bug is only a security advisory away, I'm sure. Jordan From owner-freebsd-hackers Fri Aug 1 18:35:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24309 for hackers-outgoing; Fri, 1 Aug 1997 18:35:18 -0700 (PDT) Received: from colonel.42inc.com (colonel.42inc.com [205.217.47.81]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA24302 for ; Fri, 1 Aug 1997 18:35:14 -0700 (PDT) Received: from [205.217.47.88] (vegas.42inc.com [205.217.47.88]) by colonel.42inc.com (8.8.5/8.6.12) with ESMTP id SAA29356 for ; Fri, 1 Aug 1997 18:34:53 -0700 (PDT) X-Sender: jal@205.217.47.82 Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 1 Aug 1997 18:34:16 -0700 To: hackers@FreeBSD.ORG From: Jamie Lawrence Subject: Re: security hole on FreeBSD 2.2.2 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The poster might be thinking of suidperl*, which I believe does pose security problems in some cases. -j >On Fri, 1 Aug 1997, Ben Black wrote: [...] > But what the hell is superl? I don't think it comes with 2.2.2. > >Tom > > >> On Fri, 1 Aug 1997, Sergio Lenzi wrote: >> >> > >> > >> > >> > Hello all >> > >> > Forgive me to send this message on this list. >> > >> > There is a security hole on FreeBSD 2.2.2 >> > >> > This is done using a script and a superl* on /usr/bin >> > >> > A friend of mine received root priority by telneting to my machine (2.2.2) >> > and executing a perl script. >> > >> > My solution: remove /usr/bin/superl* >> > >> > Hope this can helphelp >> > >> > >> >> -- "I am about to, or going to, die. Either expression is used." --Last words of Mme. Brouhors, Grammarian, August, 1752. __________________________________________________________________ jamie@42is.com Special Agent jal@acm.org From owner-freebsd-hackers Fri Aug 1 18:41:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24595 for hackers-outgoing; Fri, 1 Aug 1997 18:41:08 -0700 (PDT) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA24587 for ; Fri, 1 Aug 1997 18:41:04 -0700 (PDT) Received: (from tim@localhost) by shell.futuresouth.com (8.8.5/8.8.5) id UAA05321; Fri, 1 Aug 1997 20:40:53 -0500 (CDT) Message-ID: <19970801204053.21398@futuresouth.com> Date: Fri, 1 Aug 1997 20:40:53 -0500 From: Tim Tsai To: Tom Samplonius Cc: Ben Black , Sergio Lenzi , hackers@FreeBSD.ORG Subject: Re: security hole on FreeBSD 2.2.2 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Tom Samplonius on Fri, Aug 01, 1997 at 05:26:23PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Fri, 1 Aug 1997, Ben Black wrote: > > exactly. i have no clue what this guy is talking about. > > Exactly. It looks like this guy installed some bogus software, probably > setuid to root, that has a gaping hole in it. Maybe he's talking about suidperl. I seemed to remember this being a known problem and we had disabled ours long time ago. Tim From owner-freebsd-hackers Fri Aug 1 18:51:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25028 for hackers-outgoing; Fri, 1 Aug 1997 18:51:56 -0700 (PDT) Received: from terror.hungry.com (fn@terror.hungry.com [169.131.1.215]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25023 for ; Fri, 1 Aug 1997 18:51:54 -0700 (PDT) Received: (from fn@localhost) by terror.hungry.com (8.8.6/8.8.4) id SAA08923; Fri, 1 Aug 1997 18:51:32 -0700 (PDT) To: tom@sdf.com (Tom Samplonius) Cc: freebsd-hackers@freebsd.org Subject: Re: security hole on FreeBSD 2.2.2 References: From: Faried Nawaz Date: 01 Aug 1997 18:51:31 -0700 In-Reply-To: tom@sdf.com's message of 1 Aug 1997 18:34:08 -0700 Message-ID: Lines: 40 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk tom@sdf.com (Tom Samplonius) writes: On Fri, 1 Aug 1997, Ben Black wrote: > exactly. i have no clue what this guy is talking about. Exactly. It looks like this guy installed some bogus software, probably setuid to root, that has a gaping hole in it. Tom The "bogus" software is called suidperl. There are known exploits for it that'll work on 2.2.2-RELEASE: % ls -li sperl4036 /usr/bin/suidperl /usr/bin/sperl4.036 7749 ---s--x--x 2 root bin 282624 May 20 03:32 /usr/bin/sperl4.036 7749 ---s--x--x 2 root bin 282624 May 20 03:32 /usr/bin/suidperl 184410 -rwx------ 1 fn user 8846 Aug 1 18:43 sperl4036 % id uid=297(fn) gid=29(user) groups=29(user), 0(wheel), 7(bin) % ./sperl4036 # id uid=297(fn) euid=0(root) gid=29(user) groups=29(user), 0(wheel), 7(bin) # exit % uname -r 2.2.2-RELEASE % For obvious reasons, I won't be posting the exploit. Note that a similar exploit exists for certain versions of Perl 5. Your choices are: 1. remove the suid bit on sperl4.036, and 2. upgrade to 2.2-STABLE. faried. -- faried nawaz box 3582, moscow id 83843-1914 From owner-freebsd-hackers Fri Aug 1 19:10:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA25778 for hackers-outgoing; Fri, 1 Aug 1997 19:10:34 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA25771 for ; Fri, 1 Aug 1997 19:10:29 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id MAA19476; Sat, 2 Aug 1997 12:12:46 +1000 (EST) Date: Sat, 2 Aug 1997 12:12:45 +1000 (EST) From: "Daniel O'Callaghan" To: Peter Hawkins cc: hackers@FreeBSD.ORG, handy@sag.space.lockheed.com Subject: Re: Mail question In-Reply-To: <199708020059.KAA20479@rhiannon.clari.net.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 Sat, 2 Aug 1997, Peter Hawkins wrote: > Danny O'Callahan wrote a fix that I think is excellent. it is available > as a gz file from ftp.hilink.com.au. > > I have been using it for a while now but it really needs a man page. > A few misconfigurations left my customers' mail inoperative for a day > last week - make sure your domain is listed in the virtdomains file!! Just to clarify this. I took sendmail rules which were posted by Adrian Chadd (and obtained elsewhere) and gave them to Peter, along with a perl script which manages virtual domains and redirections. I wrote the perl script, but not the sendmail rules. Danny From owner-freebsd-hackers Fri Aug 1 19:52:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA27336 for hackers-outgoing; Fri, 1 Aug 1997 19:52: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 TAA27331 for ; Fri, 1 Aug 1997 19:52:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA08782; Sat, 2 Aug 1997 12:22:18 +0930 (CST) From: Michael Smith Message-Id: <199708020252.MAA08782@genesis.atrad.adelaide.edu.au> Subject: Re: device close behaviour - a question In-Reply-To: <199708011655.JAA03079@biggusdiskus.flyingfox.com> from Jim Shankland at "Aug 1, 97 09:55:15 am" To: jas@flyingfox.com (Jim Shankland) Date: Sat, 2 Aug 1997 12:22:18 +0930 (CST) Cc: luigi@labinfo.iet.unipi.it, 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 Jim Shankland stands accused of saying: > [Luigi Rizzo would like his audio driver to be notified every time > the device is closed, not just on last close.] > > The way I've dealt with a similar situation in the past is to represent > each physical device as an array of minor device numbers, on each of > which the driver enforces an exclusive-open. User-level code must The point I am trying to make here is that you _cannot_ enforce an exclusive open, because the devic driver is not notified under all of the circumstances which result in a new fd being granted. > then iterate over the devices, until an open() call does not return > EBUSY (just like looking for an available pty). Since each "device" > is open at most once, the device_close() routine gets called on > every user-level close() call. This scheme works well if you are at liberty to enforce the behaviour of userland programs. Luigi is faced with remaining compatible with previous versions and also with the Linux interface, which is a fairly crippling requirement in and of itself. -- ]] 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 Fri Aug 1 20:26:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA28898 for hackers-outgoing; Fri, 1 Aug 1997 20:26:55 -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 UAA28893 for ; Fri, 1 Aug 1997 20:26:52 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA08876; Sat, 2 Aug 1997 12:56:45 +0930 (CST) From: Michael Smith Message-Id: <199708020326.MAA08876@genesis.atrad.adelaide.edu.au> Subject: Re: Kernel howto, Second Request In-Reply-To: from Simon Shapiro at "Aug 1, 97 01:00:25 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Sat, 2 Aug 1997 12:56:45 +0930 (CST) 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 Simon Shapiro stands accused of saying: [Charset iso-8859-8 unsupported, filtering to ASCII...] > Old, unanswered question: I responded to these. Let me know if you didn't get the rsponse, but more importantly _why_ do you want them? > Next Question: What is the equivalent of SysV physmap()? > Physmap takes a physical memory address and returns a virtual address. > I am trying to access certain memory location only known by physical > addresses. Are you trying to perform this operation in userspace or in the kernel? Do you know the the physical address range in question has been mapped yet? If it has, by whom? If not, then you will need to establish a mapping, which will give you this information. > Simon -- ]] 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 Fri Aug 1 20:49:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA29842 for hackers-outgoing; Fri, 1 Aug 1997 20:49:11 -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 UAA29837 for ; Fri, 1 Aug 1997 20:49:08 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA08948; Sat, 2 Aug 1997 13:17:58 +0930 (CST) From: Michael Smith Message-Id: <199708020347.NAA08948@genesis.atrad.adelaide.edu.au> Subject: Re: security hole on FreeBSD 2.2.2 In-Reply-To: from Tom Samplonius at "Aug 1, 97 05:26:23 pm" To: tom@sdf.com (Tom Samplonius) Date: Sat, 2 Aug 1997 13:17:58 +0930 (CST) Cc: black@zen.cypher.net, lenzi@bsi.com.br, 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 Tom Samplonius stands accused of saying: > > On Fri, 1 Aug 1997, Ben Black wrote: > > > exactly. i have no clue what this guy is talking about. > > Exactly. It looks like this guy installed some bogus software, probably > setuid to root, that has a gaping hole in it. The "bogus software" is Perl. "superl" should have been "sperl", and my last world build of -stable left me with : silver:~>ls -l /usr/bin/sperl* ---s--x--x 2 root bin 286720 Jun 7 18:35 /usr/bin/sperl4.036 Naturally, I don't leave it installed on public machines; setuid script interpreters are a Really Bad Idea. -- ]] 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 Fri Aug 1 21:02:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA00383 for hackers-outgoing; Fri, 1 Aug 1997 21:02:07 -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 VAA00376 for ; Fri, 1 Aug 1997 21:02:00 -0700 (PDT) Received: (qmail 12998 invoked by uid 1000); 2 Aug 1997 04:02:15 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708020326.MAA08876@genesis.atrad.adelaide.edu.au> Date: Fri, 01 Aug 1997 21:02:15 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Michael Smith Subject: Re: Kernel howto, Second Request Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Michael Smith; On 02-Aug-97 you wrote: > Simon Shapiro stands accused of saying: > [Charset iso-8859-8 unsupported, filtering to ASCII...] > > Old, unanswered question: > > I responded to these. Let me know if you didn't get the rsponse, but > more importantly _why_ do you want them? I didn't get the response :-( I do not want these. I need them. The DPT raid manager requires these. They do not do anything dramatic with them, but the application (originally DOS) expects them in reply to an IOCTL. > > Next Question: What is the equivalent of SysV physmap()? > > Physmap takes a physical memory address and returns a virtual > address. > > I am trying to access certain memory location only known by physical > > addresses. > > Are you trying to perform this operation in userspace or in the > kernel? Do you know the the physical address range in question has > been mapped yet? If it has, by whom? If not, then you will need to > establish a mapping, which will give you this information. Kernel, of course. The addresses are all BIOS data pages and the DPT BIOS and firmware addresses. The code is really, really not portable (I am being very kind with my words here :-) If I an have the values for the struct, I will gladly avoid writing all these nasty inb/outb and funny memory accesses. I really do not knowif this memory has been mapped or not. What I need to do is probe certain location, in BIOS ranges for certain signatures. This probing should not be destructive. Simon From owner-freebsd-hackers Fri Aug 1 21:55:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA01958 for hackers-outgoing; Fri, 1 Aug 1997 21:55: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 VAA01953 for ; Fri, 1 Aug 1997 21:55:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA09123; Sat, 2 Aug 1997 14:24:35 +0930 (CST) From: Michael Smith Message-Id: <199708020454.OAA09123@genesis.atrad.adelaide.edu.au> Subject: Re: Kernel howto, Second Request In-Reply-To: from Simon Shapiro at "Aug 1, 97 09:02:15 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Sat, 2 Aug 1997 14:24:35 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, 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 Simon Shapiro stands accused of saying: > > > > I responded to these. Let me know if you didn't get the rsponse, but > > more importantly _why_ do you want them? > > I didn't get the response :-( Booger. > I do not want these. I need them. The DPT raid manager requires these. > They do not do anything dramatic with them, but the application (originally > DOS) expects them in reply to an IOCTL. Ok. Can you lie about them, or fix the application? The CMOS drive type is unlikely to be relevant, the CPU and architecture you can get inside the kernel (look at the output of sysctl -a and backtrack that into the kernel, or pester me some more and I can cons you some code for the job). > Kernel, of course. The addresses are all BIOS data pages and the DPT > BIOS and firmware addresses. The code is really, really not portable > (I am being very kind with my words here :-) If I an have the values > for the struct, I will gladly avoid writing all these nasty inb/outb > and funny memory accesses. > > I really do not knowif this memory has been mapped or not. What I need > to do is probe certain location, in BIOS ranges for certain signatures. > This probing should not be destructive. Oh, that's completely different again. If you want to poke at the ISA 'hole', that's mapped as part of the kernel address space. If you have an up-to-date -current lurking somewhere, have a look in sys/i386/i386/bios.c to see how to rummage in that area. The BIOS data area I'm not so sure about; I'm fairly sure it's preserved, but I'm not entirely sure where. If you _really_ need numbers from here, go ahead and chase it. In most cases, I'd suggest you fake the numbers instead. -- ]] 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 Fri Aug 1 23:14:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA04679 for hackers-outgoing; Fri, 1 Aug 1997 23:14:48 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA04674 for ; Fri, 1 Aug 1997 23:14:46 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id CAA05768 for ; Sat, 2 Aug 1997 02:14:45 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id CAA07778 for ; Sat, 2 Aug 1997 02:14:45 -0400 (EDT) To: hackers@freebsd.org From: "Gary Palmer" Subject: non-blocking file i/o Date: Sat, 02 Aug 1997 02:14:44 -0400 Message-ID: <7776.870502484@orion.webspan.net> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A friend (who mainly does his devel under solaris/linux) recently came up with a patch to the INN database code which made the writes non-blocking. On linux/solaris, the non-blocking writes would take fractions of a ms. On FreeBSD, the blocking write took 8ms and the ``non-blocking'' write took 4ms (set using fcntl). It also seems that Linux and Solaris use open(file, O_NONBLOCK, 0) to put the file into non-blocking mode for reading and writing also, where our open flag only affects the open. O_NONBLOCK seems nearly a no-op on FreeBSD. Is this true? Is there anything that can be done about it? (just as a test, the mmap'd version on a FreeBSD PPro came out with pretty similar figures to the Linux one on similar h/w ... it's just non-blocking writes that seem troublesome). The reason that a non-blocking writes one could be attractive is that the .pag file is bloated a lot, and could be a lot of trouble on smaller machines ... Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sat Aug 2 00:07:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06801 for hackers-outgoing; Sat, 2 Aug 1997 00:07:31 -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 AAA06796; Sat, 2 Aug 1997 00:07:24 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id CAA11836; Sat, 2 Aug 1997 02:07:22 -0500 (EST) From: "John S. Dyson" Message-Id: <199708020707.CAA11836@dyson.iquest.net> Subject: Re: non-blocking file i/o In-Reply-To: <7776.870502484@orion.webspan.net> from Gary Palmer at "Aug 2, 97 02:14:44 am" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sat, 2 Aug 1997 02:07:22 -0500 (EST) Cc: 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 > > A friend (who mainly does his devel under solaris/linux) recently came > up with a patch to the INN database code which made the writes > non-blocking. On linux/solaris, the non-blocking writes would take > fractions of a ms. On FreeBSD, the blocking write took 8ms and the > ``non-blocking'' write took 4ms (set using fcntl). It also seems that > Linux and Solaris use open(file, O_NONBLOCK, 0) to put the file into > non-blocking mode for reading and writing also, where our open flag > only affects the open. > > O_NONBLOCK seems nearly a no-op on FreeBSD. Is this true? Is there > anything that can be done about it? > > (just as a test, the mmap'd version on a FreeBSD PPro came out with > pretty similar figures to the Linux one on similar h/w ... it's just > non-blocking writes that seem troublesome). The reason that a > non-blocking writes one could be attractive is that the .pag file is > bloated a lot, and could be a lot of trouble on smaller machines ... > The AIO code is a standard (nice) way to implement database I/O. John From owner-freebsd-hackers Sat Aug 2 00:34:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA08833 for hackers-outgoing; Sat, 2 Aug 1997 00:34:31 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA08825 for ; Sat, 2 Aug 1997 00:34:27 -0700 (PDT) Received: from zeus.coppe.ufrj.br (jonny@zeus.coppe.ufrj.br [146.164.63.6]) by gaia.coppe.ufrj.br (8.8.6/8.8.6) with ESMTP id EAA15882; Sat, 2 Aug 1997 04:34:24 -0300 (EST) From: Joao Carlos Mendes Luis Received: (from jonny@localhost) by zeus.coppe.ufrj.br (8.8.6/8.8.5) id EAA06531; Sat, 2 Aug 1997 04:34:31 -0300 (EST) Message-Id: <199708020734.EAA06531@zeus.coppe.ufrj.br> Subject: Re: NFS Problems in 2.2 ? In-Reply-To: <199707291925.QAA09968@gaia.coppe.ufrj.br> from Joao Carlos Mendes Luis at "Jul 29, 97 04:25:24 pm" To: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Sat, 2 Aug 1997 04:34:30 -0300 (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 Just in case this can help. I lowered the speed of the NIC to 10M, and got no more problems. If this is not a problem with the 100Mbps code (is it different ???), surely is a problem with packet loss. #define quoting(Joao Carlos Mendes Luis) // Hi, // // I'm having lots of problems with NFS deadlocks in my recent configuration. // Both client and server are 2.2-STABLE, with 3c905 100Mbps ethernet boards. // Right now, for example, I have a netscape and am elm locked. If this helps, // here's the output of a "ps -axlww | grep nfs" on the client: // // zeus::jonny [501] ps -axlww | grep nfs // 0 112 1 0 2 0 236 0 accept IWs ?? 0:00.00 nfsd: master (nfsd) // 0 114 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) // 0 115 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) // 0 116 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) // 0 117 112 0 2 0 228 0 nfsd IW ?? 0:00.00 nfsd: server (nfsd) // 0 127 1 0 -1 0 212 12 nfsrcv D ?? 0:00.09 nfsiod -n 8 // 0 128 1 0 -1 0 212 12 nfsrcv D ?? 0:00.06 nfsiod -n 8 // 0 129 1 0 -1 0 212 12 nfsrcv D ?? 0:00.03 nfsiod -n 8 // 0 130 1 0 2 0 212 12 sbwait D ?? 0:00.03 nfsiod -n 8 // 0 131 1 0 -1 0 212 12 nfsrcv D ?? 0:00.03 nfsiod -n 8 // 0 132 1 0 -1 0 212 12 nfsrcv D ?? 0:00.02 nfsiod -n 8 // 0 133 1 0 -1 0 212 12 nfsrcv D ?? 0:00.02 nfsiod -n 8 // 0 134 1 0 -1 0 212 12 nfsrcv D ?? 0:00.01 nfsiod -n 8 // 100 410 1 0 -6 0 7048 4304 nfsaio D v1 0:10.64 /usr/local/lib/netscape/netscape.bin // zeus::jonny [502] // // The relevant fstab options are as follows: // // gaia:/ /gaia nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 // gaia:/usr /gaia/usr nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 // gaia:/var /gaia/var nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 // gaia:/extra /gaia/extra nfs rw,soft,intr,bg,nfsv2,dumbtimer 0 0 // // Using option "tcp" helps a lot, but if the server reboots, the client does // not reconect. "nfsv2" and "dumbtimer" seem to have helped, but did not // solve the problem. // // Is there anything I can do to help debug this ? 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 Sat Aug 2 00:52:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09780 for hackers-outgoing; Sat, 2 Aug 1997 00:52:43 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09773 for ; Sat, 2 Aug 1997 00:52:41 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA27459; Sat, 2 Aug 1997 02:51:37 -0500 Message-Id: <3.0.2.32.19970802024821.0069d68c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 02 Aug 1997 02:48:21 -0500 To: Craig Johnston From: Tony Overfield Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:02 PM 7/29/97 -0500, Craig Johnston wrote: > >[black helicopters deleted] >I wouldn't count >on not running into bugs in the relatively untested slot 1 chipset. No. The Pentium II uses Pentium Pro chipsets, not Pentium chipsets or "Slot 1 chipsets." >Slot 1 is also entirely proprietary -- Intel's response to more >competition than it likes from AMD and now Cyrix. No. Think like an engineer and you will probably be able to understand why Slot 1 was created. - Tony From owner-freebsd-hackers Sat Aug 2 00:53:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09815 for hackers-outgoing; Sat, 2 Aug 1997 00:53:33 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09808 for ; Sat, 2 Aug 1997 00:53:29 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA27462; Sat, 2 Aug 1997 02:51:38 -0500 Message-Id: <3.0.2.32.19970802025130.006c2488@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 02 Aug 1997 02:51:30 -0500 To: Tom Samplonius , Craig Johnston From: Tony Overfield Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 09:08 AM 7/30/97 -0700, Tom Samplonius wrote: > >On Wed, 30 Jul 1997, Craig Johnston wrote: >> >> The real issue is that the PII is untried ... > > Hardly untried, just souped up Pentium technology. The Pentium II is a souped up Pentium Pro. - Tony From owner-freebsd-hackers Sat Aug 2 00:53:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09831 for hackers-outgoing; Sat, 2 Aug 1997 00:53:35 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09810 for ; Sat, 2 Aug 1997 00:53:31 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA27465; Sat, 2 Aug 1997 02:51:39 -0500 Message-Id: <3.0.2.32.19970802025046.006c51f8@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 02 Aug 1997 02:50:46 -0500 To: Curt Sampson , Tom Samplonius From: Tony Overfield Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:24 AM 7/30/97 -0700, Curt Sampson wrote: >On Wed, 30 Jul 1997, Tom Samplonius wrote: >> PII/266 chips are cheaper than than Pro/200 w/512k cache, and faster. >> Besides the chipset is the same! > >Yes, but much cheaper 256K cache PPro200s are also available. Is >512K of slow cache better than 256K of fast cache for your application? Most likely, yes. In addition to that, which would you rather have: 8+8 KB L1 cache at 200MHz or 16+16 KB L1 cache at 266MHz? - Tony From owner-freebsd-hackers Sat Aug 2 00:54:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09859 for hackers-outgoing; Sat, 2 Aug 1997 00:54:00 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09854 for ; Sat, 2 Aug 1997 00:53:56 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA27453; Sat, 2 Aug 1997 02:51:36 -0500 Message-Id: <3.0.2.32.19970802023853.0069c4c4@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 02 Aug 1997 02:38:53 -0500 To: Terry Lambert , brianc@milkyway.com (Brian Campbell) From: Tony Overfield Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG In-Reply-To: <199707302054.NAA05832@phaeton.artisoft.com> References: <19970730144420.16698@milkyway.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:54 PM 7/30/97 -0700, Terry Lambert wrote: >> > My 486 DX-50 still beats the snot of of a P5 DX/2-66, and is >> > more than fast enough (EISA bus overclocked to 50MHz) to handle >> > a lot of stuff that early P5 machines couldn't. >> >> Hmmm ... Never heard of a P5 DX/2-66 ;-) > >Dell was selling them. This is wrong! Dell sold no such thing as a "P5 DX/2-66"! >This was back when they were using the >Saturn I chipset, which did not have DMA writeback notification >connected from the macrocell (missing trace). Due to that bug, that version of the Saturn chipset does not support write-back L2 caching and it is therefore configured by the BIOS to use the L2 cache in write-through mode, though the L1 cache is always write-back. The missing trace is not used or needed when the L2 cache is in write-through mode. >Clock-doubled 66 MHz Pentiums were at one time common, before >CPU fans became common. Hmm, they weren't common enough for me to have ever heard of them before. >Dell also had 60MHz non-doubled chips >available before the doubled 66's were available. Well, of course the 66 MHz chips were available after the 60 MHz chips were, but they weren't "doubled." >The non-doubled >60's kicked butt over the doubled 66's for anything I/O bound. They probably would have, had the "doubled 66's" ever existed. >Just as my 486/50 kicks butt over the same chips. I doubt this, unless you're "stacking the deck" in some perverse way, or you're simply dreaming. - Tony From owner-freebsd-hackers Sat Aug 2 00:54:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09890 for hackers-outgoing; Sat, 2 Aug 1997 00:54:15 -0700 (PDT) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09885 for ; Sat, 2 Aug 1997 00:54:11 -0700 (PDT) Received: from ant.us.dell.com (ant.us.dell.com [198.64.66.34]) by bugs.us.dell.com (8.6.12/8.6.12) with SMTP id CAA27456; Sat, 2 Aug 1997 02:51:37 -0500 Message-Id: <3.0.2.32.19970802024954.006dfb1c@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sat, 02 Aug 1997 02:49:54 -0500 To: FreeBSD Mailing List , Tom Samplonius From: Tony Overfield Subject: Re: Pentium II? Cc: hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 08:29 AM 7/29/97 -0600, FreeBSD Mailing List wrote: >> > The PPro is still faster for a true 32-bit OS, primarily due to the fact >> > that the L2 is 1:1 with the CPU clock. On the Pentium II, the L2 caching >> > is at 1/2 the CPU clock. On Tue, 29 Jul 1997, Tom Samplonius wrote: >> >> Not, not quite. At the same clock rate, the PPro is faster, but the PII >> can operate at 266mhz, while the PPro maxes at 200mhz. Whoa! Not so fast... Conspicuously overlooked by this whole Pentium II thread is a simple, yet very important, detail. The Pentium II level-one (L1) cache is twice the size of the one in the Pentium Pro. That means you've got a 16+16 KB L1 cache running at up to 300 MHz. This makes a proper comparision a little more complicated because the relative performance of the two processors, even when using the bogus "same clock rate" argument, is dependent on the specific code sequences being run. Since the hit rate of the L1 cache is usually much higher than that of the L2 cache, the effect of the slower L2 cache in the Pentium II is usually offset by the beneficial effect of not having to access it. So even at the same clock rate, the Pentium II can run faster than the Pentium Pro. - Tony From owner-freebsd-hackers Sat Aug 2 02:02:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA11843 for hackers-outgoing; Sat, 2 Aug 1997 02:02:14 -0700 (PDT) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA11838 for ; Sat, 2 Aug 1997 02:02:07 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0wua4Y-000o8fC; Sat, 2 Aug 97 11:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Sat, 2 Aug 1997 09:49:51 +0200 (MET DST) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for FreeBSD-Hackers@FreeBSD.ORG; Sat, 2 Aug 1997 09:43:12 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Kernel howto, Second Request In-Reply-To: from Simon Shapiro at "Aug 1, 97 01:00:25 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Sat, 2 Aug 1997 09:43:12 +0200 (CEST) Cc: FreeBSD-Hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.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 Simon Shapiro wrote: > How do I find the following, from a device driver? > > Drive Type in CMOS Drive 0 > > Drive Type in CMOS Drive 1 > > Number of drives (in CMOS location 40:75 This can be found in the bios equipment byte, you can get this by calling rtcin(RTC_EQUIPMENT) and decode the result according to a bios ref manual. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe There is a difference between an open mind and a hole in the head From owner-freebsd-hackers Sat Aug 2 02:39:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14933 for hackers-outgoing; Sat, 2 Aug 1997 02:39:44 -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 CAA14928 for ; Sat, 2 Aug 1997 02:39:39 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 1944 invoked by uid 1001); 2 Aug 1997 09:39:34 +0000 (GMT) To: tony@dell.com Cc: freebsd@atipa.com, tom@sdf.com, hackers@FreeBSD.ORG Subject: Re: Pentium II? In-Reply-To: Your message of "Sat, 02 Aug 1997 02:49:54 -0500" References: <3.0.2.32.19970802024954.006dfb1c@bugs.us.dell.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 02 Aug 1997 11:39:34 +0200 Message-ID: <1942.870514774@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Since the hit rate of the L1 cache is usually much higher than that of the L2 >cache, the effect of the slower L2 cache in the Pentium II is usually offset >by the beneficial effect of not having to access it. So even at the same >clock rate, the Pentium II can run faster than the Pentium Pro. *Can run* being the operative phrase here. According to Intel's Web site: PPro-200, 256 KB L2 cache 8.20 SPECint95 PII-233, 512 KB L2 cache 9.49 SPECint95 So 15.7% higher SPECint95 at 16.5% higher clock rate. Personally, I don't want to draw any conclusions at all from these numbers - they are so very close. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Aug 2 03:21:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA16297 for hackers-outgoing; Sat, 2 Aug 1997 03:21:34 -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 DAA16292 for ; Sat, 2 Aug 1997 03:21:29 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA09873 for hackers@freebsd.org; Sat, 2 Aug 1997 19:51:26 +0930 (CST) From: Michael Smith Message-Id: <199708021021.TAA09873@genesis.atrad.adelaide.edu.au> Subject: kernel parameter registry To: hackers@freebsd.org Date: Sat, 2 Aug 1997 19:51:26 +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, I have to tool off for possibly the rest of the weekend, maybe even some of next week (not clear yet). In the meantime, I'd like people (if they have a chance) to have a look at a couple of things which may take their fancy. In keeping with the title, and various discussions that have been undertaken over the last year or so, please find in : ftp://smith.net.au/FreeBSD/registry/ some first-cut code for a basic kernel parameter registry. Note that the manpage is a little behind the current state of affairs, and shockingly incomplete, but it outlines the design fairly clearly. I hope to spend some more time on this very soon, as it is crucial to the ongoing PCI/PnP/PCCARD debate, as well as countles other parametric issues. I would especially appreciate any suggestions for improving the speed of lookup, as the component-by-component traversal is bound to be inefficient. And second, for those of you that like to actually read your mail, I offer for your study and delectation the future of parallel-port I/O on FreeBSD : ftp://smith.net.au/ppa/ppbus-970730.tgz At this point in time, the kit is operational but a shade messy. We'd really appreciate any input that you might have before I get game and risk the wrath of everyone by committing it. -- ]] 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 Sat Aug 2 03:32:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA16735 for hackers-outgoing; Sat, 2 Aug 1997 03:32:04 -0700 (PDT) Received: from cenotaph.snafu.de (gw-deadnet.snafu.de [194.121.229.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA16717 for ; Sat, 2 Aug 1997 03:31:56 -0700 (PDT) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0wubTL-000K93C; Sat, 2 Aug 1997 12:31:43 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Received: by deadline.snafu.de id m0wubTK-0004jwC; Sat, 2 Aug 1997 12:31:42 +0200 (CEST) (Smail-3.2 1996-Jul-4 #1) Message-Id: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Need help on writing SCSI scanner driver To: hackers@freebsd.org Date: Sat, 2 Aug 1997 12:31:42 +0200 (CEST) Organization: A world stranger than you have ever imagined. X-Mailer: ELM [version 2.4ME+ PL13] 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! --- Some time ago I started to write a high level SCSI driver for my AGFA Studio Star scanner. Now I'm facing some minor problems in the overall design of the driver code. My imagination of a scanner driver has been to have a device that is opened by the application software by a open(2) call and than configured to the correct scan parameters using ioctls before the scan data is retrieved via one or more read(2) calls. The problem in this context seems to be that the scanner is in fact able to deliver all the scan data at once, but the I/O subsystem seems to split a big read call into several 64k segments. Another problem is that the scanner expects the READ_SCANNED_DATA SCSI command to have a number of scanlines (not bytes) attached, so I will have to convert the number of bytes from a read(2) call to a number of scan lines internally in the driver code. My question is, if it is possible to read in all the scan data at once from the scanner (wheter or not it is handed to the user process in 64k segments). In other words, I do want to only issue a READ_SCANNED_DATA SCSI command to the scanner once, but not everytime a 64k segment is read by the user process. Thankful for any advice. Rergards, Mickey -- (__) (@@) Andreas S. Wetzel Mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://cenotaph.snafu.de/ / | || 13347 Berlin Fon: <+4930> 456 066 90 * ||----|| Germany Fax: <+4930> 456 066 91/92 ~~ ~~ From owner-freebsd-hackers Sat Aug 2 03:39:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA17017 for hackers-outgoing; Sat, 2 Aug 1997 03:39:22 -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 DAA17011 for ; Sat, 2 Aug 1997 03:39:15 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id DAA02744 for ; Sat, 2 Aug 1997 03:39:15 -0700 (PDT) Message-Id: <199708021039.DAA02744@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: Voodo Rush ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Aug 1997 03:39:15 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone managed to get a Voodoo Rush board running on FreeBSD? http://www.3dfx.com The 3dfx stuff for linux comes with a library and I think that there are patches to quake linux floating around to make it work with the 3dfx.... Cheers, Amancio From owner-freebsd-hackers Sat Aug 2 05:57:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA22320 for hackers-outgoing; Sat, 2 Aug 1997 05:57:16 -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 FAA22303; Sat, 2 Aug 1997 05:57:11 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id FAA00415; Sat, 2 Aug 1997 05:57:05 -0700 (PDT) Message-Id: <199708021257.FAA00415@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@FreeBSD.ORG cc: multimedia@FreeBSD.ORG Subject: Voodoo Graphics works on FreeBSD 8) Date: Sat, 02 Aug 1997 05:57:05 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Howdy, I downloaded the linux thingy from ftp.3dfx.com and it seems to work on my FreeBSD-current box 8) Had to patch the linux emulation layer to support iopl. A quick and dirty hack: linux_dummy.c: #include #include #include . . . int linux_iopl(struct proc *p, struct linux_iopl_args *args, int *retval) { struct open_args bsd_open_args; char *buf; p->p_md.md_regs->tf_eflags |= PSL_IOPL; return 0; } My combo is a Diamond Monster 3D / Matrox Millenium. Now to wait for glquake for linux 8) Enjoy, Amancio From owner-freebsd-hackers Sat Aug 2 06:04:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22557 for hackers-outgoing; Sat, 2 Aug 1997 06:04:07 -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 GAA22539 for ; Sat, 2 Aug 1997 06:04:00 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA08390; Sat, 2 Aug 1997 14:05:17 +0200 From: Luigi Rizzo Message-Id: <199708021205.OAA08390@labinfo.iet.unipi.it> Subject: Re: device close behaviour - a question To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 2 Aug 1997 14:05:16 +0200 (MET DST) Cc: jas@flyingfox.com, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708020252.MAA08782@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 2, 97 12:21:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > then iterate over the devices, until an open() call does not return > > EBUSY (just like looking for an available pty). Since each "device" > > is open at most once, the device_close() routine gets called on > > every user-level close() call. > > This scheme works well if you are at liberty to enforce the behaviour > of userland programs. Luigi is faced with remaining compatible with > previous versions and also with the Linux interface, which is a fairly however, to be honest, in this case there is no backward compatibility issue since I don't think linux (voxware) allows multiple opens on the sound device. But boy, it's nice to make 1sec echos cat /dev/audio1 | dd obs=8000 > /dev/audio1 Cheers Luigi From owner-freebsd-hackers Sat Aug 2 07:58:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26366 for hackers-outgoing; Sat, 2 Aug 1997 07:58:17 -0700 (PDT) Received: from sakaki.communique.net (sakaki.communique.net [204.27.65.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA26361 for ; Sat, 2 Aug 1997 07:58:15 -0700 (PDT) Received: from FRK1.blue.frk.cmq.com (fcreel.Frk.Cmq.com [204.27.66.50]) by sakaki.communique.net (8.8.5/8.8.5) with SMTP id JAA04079 for ; Sat, 2 Aug 1997 09:57:43 -0500 (CDT) Message-ID: <33E34AA6.5A7F@communique.net> Date: Sat, 02 Aug 1997 09:56:38 -0500 From: Frank Creel Reply-To: fcreel@communique.net Organization: IFC X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: DOS PROGRAMS References: <33E3497C.510@communique.net> <33E34A22.2069@communique.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Frank Creel wrote: > > Frank Creel wrote: > > > > I have heard that there is a hackers group working on a program to run > > MS dos programs under unix or freebds.?? > > > > Can you aim me in the direction of this group..I would like to work with them.. > > > > Thanks, > > Frank From owner-freebsd-hackers Sat Aug 2 07:59:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26412 for hackers-outgoing; Sat, 2 Aug 1997 07:59:16 -0700 (PDT) Received: from sakaki.communique.net (sakaki.communique.net [204.27.65.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA26401 for ; Sat, 2 Aug 1997 07:59:11 -0700 (PDT) Received: from FRK1.blue.frk.cmq.com (fcreel.Frk.Cmq.com [204.27.66.50]) by sakaki.communique.net (8.8.5/8.8.5) with SMTP id JAA04167 for ; Sat, 2 Aug 1997 09:58:41 -0500 (CDT) Message-ID: <33E34AE0.4409@communique.net> Date: Sat, 02 Aug 1997 09:57:36 -0500 From: Frank Creel Reply-To: fcreel@communique.net Organization: IFC X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Re: DOS PROGRAMS References: <33E3497C.510@communique.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Frank Creel wrote: > > I have heard that there is a hackers group working on a program to run > MS dos programs under unix or freebds.?? > > Can you aim me in the direction of this group..I would like to work with > them.. > > Thanks, > Frank From owner-freebsd-hackers Sat Aug 2 08:03:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26601 for hackers-outgoing; Sat, 2 Aug 1997 08:03:21 -0700 (PDT) Received: from sakaki.communique.net (sakaki.communique.net [204.27.65.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26596 for ; Sat, 2 Aug 1997 08:03:17 -0700 (PDT) Received: from FRK1.blue.frk.cmq.com (fcreel.Frk.Cmq.com [204.27.66.50]) by sakaki.communique.net (8.8.5/8.8.5) with SMTP id KAA04603 for ; Sat, 2 Aug 1997 10:02:46 -0500 (CDT) Message-ID: <33E34BD6.4B76@communique.net> Date: Sat, 02 Aug 1997 10:01:42 -0500 From: Frank Creel Reply-To: fcreel@communique.net Organization: IFC X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: MS DOS programs running in freebsd 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 heard that there is a group working on a program to run MS dos programs under freebsd..I would like to work with this group..Can you aim me me the correct direction??? Thanks, Frank Creel 45135 Oner Miller Rd. Franklinton, LA 70438 Phone 504 839 2019 From owner-freebsd-hackers Sat Aug 2 10:00:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01559 for hackers-outgoing; Sat, 2 Aug 1997 10:00:36 -0700 (PDT) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01552 for ; Sat, 2 Aug 1997 10:00:32 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.8.6/8.8.6) id MAA07632; Sat, 2 Aug 1997 12:00:21 -0500 (CDT) Message-ID: <19970802120020.37958@dan.emsphone.com> Date: Sat, 2 Aug 1997 12:00:20 -0500 From: Dan Nelson To: Joao Carlos Mendes Luis Cc: hackers@FreeBSD.ORG Subject: Re: NFS Problems in 2.2 ? References: <199707291925.QAA09968@gaia.coppe.ufrj.br> <199708020734.EAA06531@zeus.coppe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79e In-Reply-To: <199708020734.EAA06531@zeus.coppe.ufrj.br>; from "Joao Carlos Mendes Luis" on Sat Aug 2 04:34:30 GMT 1997 X-OS: FreeBSD 2.2-970701-RELENG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In the last episode (Aug 02), Joao Carlos Mendes Luis said: > Just in case this can help. I lowered the speed of the NIC to 10M, > and got no more problems. > > If this is not a problem with the 100Mbps code (is it different ???), > surely is a problem with packet loss. > > #define quoting(Joao Carlos Mendes Luis) > // I'm having lots of problems with NFS deadlocks in my recent > // configuration. Both client and server are 2.2-STABLE, with 3c905 > // 100Mbps ethernet boards. Right now, for example, I have a netscape > // and am elm locked. If this helps, here's the output of a "ps > // -axlww | grep nfs" on the client: The 3c905 is just a low-quality card. Check out http://www.3com.com/0files/products/dsheets/400243.html, and look at the "Transmit/Receive Buffer Memory" section. It has an 8k buffer, partitioned by default at 4k xmit, 4k recv. At 100Mbps, the card will never be able to receive a full 8k NFS packet without dropping a fragment. NFS retries by resending the entire 8k packet, and that's where your deadlocks are coming from. At 10Mbps, the card is able to process an entire 8K packet, so your deadlock disappears. You can try mounting the NFS volumes with -r1024,-w1024,-I512, which will force 1K NFS packets. You might want to try another network card, if you can. The DEC 21140-based cards are supposed to be good, and the Intel EtherExpress Pro 10/100B is also a good card. I can sustain 4MB/s reads over NFS from a P6/200 server to a P133 client with 100B cards in both machines. -Dan Nelson dnelson@emsphone.com From owner-freebsd-hackers Sat Aug 2 10:07:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01817 for hackers-outgoing; Sat, 2 Aug 1997 10:07:38 -0700 (PDT) Received: from mikonos.dia.unisa.it (root@edu-gw.dia.unisa.it [192.41.218.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01811 for ; Sat, 2 Aug 1997 10:07:31 -0700 (PDT) Received: from mikonos.dia.unisa.it ([194.185.85.57]) by mikonos.dia.unisa.it (8.8.3/8.7.3) with SMTP id TAA17895 for ; Sat, 2 Aug 1997 19:07:06 +0200 Date: Sat, 2 Aug 1997 19:07:06 +0200 Message-Id: <199708021707.TAA17895@mikonos.dia.unisa.it> X-Sender: luicat@mikonos.dia.unisa.it X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: luicat@edu-gw.dia.unisa.it (Luigi Catuogno) Subject: kernel documentation Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am involved in the TCFS Project at University of Salerno. TCFS is a Cryptographic filesystem based on NFS developed on Linux. I am studying a porting on FreeBSD, and I am searching for detailed documentation of Free's Kernel. Could someone give me some informations about this? Thanks in advance. Luigi Catuogno | VOICE +39 (81) 8372700 TCFS Developer | | e-mail: luicat@mikonos.dia.unisa.it | URL: http://mikonos.dia.unisa.it/~luicat From owner-freebsd-hackers Sat Aug 2 11:15:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04650 for hackers-outgoing; Sat, 2 Aug 1997 11:15:31 -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 LAA04644 for ; Sat, 2 Aug 1997 11:15:21 -0700 (PDT) Received: (qmail 534 invoked by uid 1000); 2 Aug 1997 18:15:22 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708020454.OAA09123@genesis.atrad.adelaide.edu.au> Date: Sat, 02 Aug 1997 11:15:22 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Michael Smith Subject: Re: Kernel howto, Second Request Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Michael Smith; On 02-Aug-97 you wrote: ... [ Most excellent advise deleted... ] > The BIOS data area I'm not so sure about; I'm fairly sure it's > preserved, but I'm not entirely sure where. If you _really_ need > numbers from here, go ahead and chase it. In most cases, I'd suggest > you fake the numbers instead. This is the best thing to do. I managed to get at most of the numbers but they look bogus anyway. I thought I'd try to just use the SCO executables for a while. They expect all this nonsense. There is a struct called bootinfo in UW, which has all this data in it. Thanx anyway. Simon From owner-freebsd-hackers Sat Aug 2 12:25:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07786 for hackers-outgoing; Sat, 2 Aug 1997 12:25:14 -0700 (PDT) Received: from becker2.u.washington.edu (spaz@becker2.u.washington.edu [140.142.12.68]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA07759; Sat, 2 Aug 1997 12:24:50 -0700 (PDT) Received: from localhost (spaz@localhost) by becker2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA20590; Sat, 2 Aug 1997 12:24:43 -0700 (PDT) Date: Sat, 2 Aug 1997 12:24:42 -0700 (PDT) From: "J. Utz" To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Finally back at it! Re: working snap of new sound driver In-Reply-To: <199707311434.QAA05841@labinfo.iet.unipi.it> 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 Ok; I have no soundcards that have plugnpray or pci, looking at the patches in the readme it appears that i probably dont need to patch autoconf.c, because it does not have anything important happening as far as i am concerned...but if i get ahead of my bills and decide to splurge for a gus..i imagine i would want to do it then...... i just *hate* diddling kernel srcs on functioning machines needlessly... N, OTOH.... isa_dmastatus() looks to be quite cool....i am really looking forward to this part! i have a feeling a lot of the popping and slamming is gonna go away after this..... if not, i will at least have a way to convieniently start mapping dma traffic, this gonna be a general purpose kernel fiddling win, not just a soundcard win this'l be fun..... i just gotta remember to get up and get the family from la aeroporto at 19:15 tonight......:-) On Thu, 31 Jul 1997, Luigi Rizzo wrote: > After about two weeks of intense development, I am pleased to say that > all the major pieces of my new sound driver now work satisfactorily. As > a consequence, a _working_ snap of my new sound driver is available at > > http://www.iet.unipi.it/~luigi/snd970731.tgz > > (I am running this code on my machine now). > > The package includes a README file with detailed installation > instructions, and all the pieces you need if you are using 2.2 or > above. At the time of this writing I fixed the final bugs and > /dev/audio works reliably (at 8KHz, mono) with MSS-clones and SBpro > (tested used the CS4232 and CS4236 PnP). > > PnP cards are supported (with a minor fix, you need to change the > probe routine in ad1848.c to add the ID for your card), and possibly > even multiple sound cards in the same system (if bugs are present, > they are in the PnP probe&configure code). > > Many ioctls are still unimplemented (but the mixer calls work), but > fixing them will be trivial and probably ready for the next snap. > > Do not expect any new release for a week or so, but I will be able to > read email and reply. PLEASE if you have the time, test the code > with your cards. I am running this code on my machine at the moment, > and it seems reasonably stable. > > 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/ > _____________________________|______________________________________ > ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Aug 2 12:44:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09155 for hackers-outgoing; Sat, 2 Aug 1997 12:44:39 -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 MAA09141 for ; Sat, 2 Aug 1997 12:44:34 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id MAA01510; Sat, 2 Aug 1997 12:44:21 -0700 (PDT) Message-Id: <199708021944.MAA01510@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: root@deadline.snafu.de (Andreas S. Wetzel) cc: hackers@FreeBSD.ORG Subject: Re: Need help on writing SCSI scanner driver In-reply-to: Your message of "Sat, 02 Aug 1997 12:31:42 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Aug 1997 12:44:21 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I own a UMAX S12 and it works with sane and/or gimp 8) sane has a graphical frontend and it also provides a plugin for gimp so you can scan images directly into gimp . You may want to joing the sane project: http://www.azstarnet.com/~axplinux/sane/ Cheers, Amancio >From The Desk Of Andreas S. Wetzel : > Hi! > --- > > Some time ago I started to write a high level SCSI driver for my > AGFA Studio Star scanner. Now I'm facing some minor problems in > the overall design of the driver code. My imagination of a scanner > driver has been to have a device that is opened by the application > software by a open(2) call and than configured to the correct scan > parameters using ioctls before the scan data is retrieved via one > or more read(2) calls. The problem in this context seems to be > that the scanner is in fact able to deliver all the scan data > at once, but the I/O subsystem seems to split a big read call into > several 64k segments. Another problem is that the scanner expects > the READ_SCANNED_DATA SCSI command to have a number of scanlines > (not bytes) attached, so I will have to convert the number of > bytes from a read(2) call to a number of scan lines internally > in the driver code. My question is, if it is possible to read > in all the scan data at once from the scanner (wheter or not > it is handed to the user process in 64k segments). In other words, > I do want to only issue a READ_SCANNED_DATA SCSI command to the > scanner once, but not everytime a 64k segment is read by the user > process. > > Thankful for any advice. > > Rergards, Mickey > > -- > (__) > (@@) Andreas S. Wetzel Mail: mickey@deadline.snafu.de > /-------\/ Utrechter Strasse 41 Web: http://cenotaph.snafu.de/ > / | || 13347 Berlin Fon: <+4930> 456 066 90 > * ||----|| Germany Fax: <+4930> 456 066 91/92 > ~~ ~~ > From owner-freebsd-hackers Sat Aug 2 12:49:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09586 for hackers-outgoing; Sat, 2 Aug 1997 12:49:54 -0700 (PDT) Received: from becker1.u.washington.edu (spaz@becker1.u.washington.edu [140.142.12.67]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09565; Sat, 2 Aug 1997 12:49:48 -0700 (PDT) Received: from localhost (spaz@localhost) by becker1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA27255; Sat, 2 Aug 1997 12:49:41 -0700 (PDT) Date: Sat, 2 Aug 1997 12:49:41 -0700 (PDT) From: "J. Utz" To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Minor bump in new paradigm,,Re: working snap of new sound driver In-Reply-To: <199707311434.QAA05841@labinfo.iet.unipi.it> 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 This is the first time i have actually looked at this code before 9pm at night so please excuse the delay in noticing this.... controller snd0 device pcm0 at isa ? port? tty irq N drq D flags F vector pcmintr device midi0 at isa ? port? tty flags F device synth0 at isa ? port? tty flags F What happened to the synth and midi irq's? tnx! ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Aug 2 13:02:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10648 for hackers-outgoing; Sat, 2 Aug 1997 13:02:32 -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 NAA10633 for ; Sat, 2 Aug 1997 13:02:18 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wukMk-0005o2-00; Sat, 2 Aug 1997 14:01:30 -0600 To: Dan Riley Subject: Re: security hole on FreeBSD 2.2.2 Cc: Sergio Lenzi , hackers@freebsd.org In-reply-to: Your message of "Fri, 01 Aug 1997 18:52:44 CDT." References: Date: Sat, 02 Aug 1997 14:01:29 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Dan Riley writes: : Ditto, at least 3 of my machines were hacked using this method, all of : which were installed last week. (2.2.2-R) At least one of the setuid security holes in 2.2 has been fixed after 2.2.2-RELEASE was built. I know. I fixed it :-). Warner From owner-freebsd-hackers Sat Aug 2 13:02:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA10678 for hackers-outgoing; Sat, 2 Aug 1997 13:02:48 -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 NAA10664 for ; Sat, 2 Aug 1997 13:02:39 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wukNf-0005oI-00; Sat, 2 Aug 1997 14:02:27 -0600 To: Ben Black Subject: Re: security hole on FreeBSD 2.2.2 Cc: Sergio Lenzi , hackers@freebsd.org In-reply-to: Your message of "Fri, 01 Aug 1997 20:06:59 EDT." References: Date: Sat, 02 Aug 1997 14:02:26 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Ben Black writes: : wow, with a problem report like that i'll be sure to get right on : removing superl. how about a copy of the script or an explanaition of : the bug? The problem was that you could pass a huge command line arg, overflow a buffer in some cases, and get an egg to hatch a root shell... Check out the bugtraq archive for more details. Warner From owner-freebsd-hackers Sat Aug 2 13:07:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11110 for hackers-outgoing; Sat, 2 Aug 1997 13:07:49 -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 NAA11099 for ; Sat, 2 Aug 1997 13:07:43 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id NAA01719 for ; Sat, 2 Aug 1997 13:07:44 -0700 (PDT) Message-Id: <199708022007.NAA01719@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: linux lib + freebsd binary? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Aug 1997 13:07:43 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dumb question, can I link a linux lib with a freebsd binary? Just got hold of a 3d graphics library for my 3d hardware accelerator. The only issue is that is a linux library other than the library kicks butt 8) I have the Diamond 3d monster which uses a 3dfx chipset... Tnks, Amancio From owner-freebsd-hackers Sat Aug 2 14:45:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA16137 for hackers-outgoing; Sat, 2 Aug 1997 14:45:44 -0700 (PDT) Received: from becker2.u.washington.edu (spaz@becker2.u.washington.edu [140.142.12.68]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16115; Sat, 2 Aug 1997 14:45:39 -0700 (PDT) Received: from localhost (spaz@localhost) by becker2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id OAA22740; Sat, 2 Aug 1997 14:45:33 -0700 (PDT) Date: Sat, 2 Aug 1997 14:45:32 -0700 (PDT) From: "J. Utz" To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Why did it pull in all this stuff? Re: working snap of new driver In-Reply-To: <199707311434.QAA05841@labinfo.iet.unipi.it> 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 just finally compiled a kernel, with this stuff in it. i noticede that the compile visited every driver in the directory, gus, auidotrix, sb etc..why would it do that when all i want is a pas16 and its associarted opl3 and pseudo midi? tnx! john ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Aug 2 15:02:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16941 for hackers-outgoing; Sat, 2 Aug 1997 15:02:51 -0700 (PDT) Received: from becker1.u.washington.edu (spaz@becker1.u.washington.edu [140.142.12.67]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16914; Sat, 2 Aug 1997 15:02:40 -0700 (PDT) Received: from localhost (spaz@localhost) by becker1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA31961; Sat, 2 Aug 1997 15:02:34 -0700 (PDT) Date: Sat, 2 Aug 1997 15:02:33 -0700 (PDT) From: "J. Utz" To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: working snap of new sound driver In-Reply-To: <199707311434.QAA05841@labinfo.iet.unipi.it> 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; first off, in previous correspondence, you ( luigi ) indicated to me that u thought that the pcm device on a pas was the soundblaster. I am pretty sure that this is not true...Both from recollection, and the fact that when i started using jeff_tranter@pobox.com 's wave-1.0 program, i had to modify it to get 16 bit sound to work. specifically i had to reverse the endianess of the 16 bit linear play. here is my config entry. i am not even messing wiht my maui card right now. i wnt to get the reference implementation working first, before we tackle the downloadable os card... # pas-16 device pcm0 at isa? port 0x388 tty irq 10 drq 7 flags 0 vector pcmintr device midi0 at isa? port 0x300 tty flags 0 device synth0 at isa? port 0x38a tty flags 0 #where A0 is the ioaddr for the pcm interface on the pas16 (which is #actually a soundblaster) ( quoting luigi ) # finally, there is the other evidence in the form of my non working soundcard: pcm0 at 0x0388 irq 10 drq 7 mem 0x00000000 flags 0x00000000 en 1 confl 0 I/O address inactive (ff), try pseudo_mss sb_reset_dsp failed pcm0 not found at 0x388 midi0 at 0x0300 irq -1 drq -1 mem 0x00000000 flags 0x00000000 en 1 confl 0 midi0 not found at 0x300 synth0 at 0x038a irq -1 drq -1 mem 0x00000000 flags 0x00000000 en 1 confl 0 synth0 not found at 0x38a ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Aug 2 15:03:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17024 for hackers-outgoing; Sat, 2 Aug 1997 15:03:33 -0700 (PDT) Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17004 for ; Sat, 2 Aug 1997 15:03:24 -0700 (PDT) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.7.6/8.7.3) with SMTP id SAA01269 for ; Sat, 2 Aug 1997 18:07:22 -0400 (EDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 02 Aug 1997 18:02:29 -0400 (EDT) Organization: Cybernet Systems From: "Mark J. Taylor" To: hackers@freebsd.org Subject: make world for 2.2.2 with DESTDIR fails Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all- Firstly: I've done searches on FreeBSD's WWW site. I've also looked in the Handbook and FAQ. I've also looked in the -current mailing list. There is no references that I've found to this problem, except a note somewhere that having a "DESTDIR" when 'make'ing world can cause linking problems. I've never tried to make world before, so please please excuse me if I ask stupid questions. I've been trying to do a 'make world' with DESTDIR set to /home/freebsd. It seems to fail in two places, 1) on making contrib/libgmp gmp.info: says it doesn't know how to make the target gmp.info; and 2) libncurses, shared (version 3.0) dies complaining about crt0.o and missing _main. I 'fixed' (1) by hacking Makefile.in and making a target for gmp.info. That lets me compile to the point of (2). I don't know how to get around (2). Why is it trying to link in crt0.o to a shared library? The systems that I've tried compiling on are FreeBSD 2.2.1 and 2.2.2. I've tried makeing world (with DESTDIR set to /home/freebsd) for 2.1.7.1 as well, and it falls over somewhere else. What I really want is to build a complete 2.2.2 system and NOT have it installed over the currently running system. I'd like to use it as a place to store a complete binary system where I can do upgrades from. If there is some work that needs to be done to use the DESTDIR option, then I'd be glad to do it and send diffs. First, though, I have to identify if I am at fault (from lack of knowledge), or if there is actually a problem here. Please respond via email as well as via the mailing list, as I am not currently (directly) subscribed. -------------------------------------------------------------------- Mark J. Taylor Network R&D Manager Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (313) 668-2567 Ann Arbor, MI 48108 FAX (313) 668-8780 -------------------------------------------------------------------- From owner-freebsd-hackers Sat Aug 2 15:13:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17803 for hackers-outgoing; Sat, 2 Aug 1997 15:13:58 -0700 (PDT) Received: from gnostic.cynic.net (gnostic.cynic.net [198.73.220.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA17652 for ; Sat, 2 Aug 1997 15:12:19 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by gnostic.cynic.net (8.8.5/8.6.12) with SMTP id PAA04686; Sat, 2 Aug 1997 15:10:45 -0700 (PDT) X-Authentication-Warning: gnostic.cynic.net: cjs owned process doing -bs Date: Sat, 2 Aug 1997 15:10:44 -0700 (PDT) From: Curt Sampson X-Sender: cjs@gnostic.cynic.net To: Tony Overfield cc: FreeBSD Mailing List , Tom Samplonius , hackers@FreeBSD.ORG Subject: Re: Pentium II? In-Reply-To: <3.0.2.32.19970802024954.006dfb1c@bugs.us.dell.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, 2 Aug 1997, Tony Overfield wrote: > Since the hit rate of the L1 cache is usually much higher than that of the L2 > cache, the effect of the slower L2 cache in the Pentium II is usually offset > by the beneficial effect of not having to access it. So even at the same > clock rate, the Pentium II can run faster than the Pentium Pro. Do you have any benchmarks that indicate this? Or are you just dreaming? cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. `And malt does more than Milton can Vancouver, BC (604) 257-9400 To justify God's ways to man.' From owner-freebsd-hackers Sat Aug 2 15:42:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19164 for hackers-outgoing; Sat, 2 Aug 1997 15:42:53 -0700 (PDT) Received: from becker2.u.washington.edu (spaz@becker2.u.washington.edu [140.142.12.68]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19145; Sat, 2 Aug 1997 15:42:45 -0700 (PDT) Received: from localhost (spaz@localhost) by becker2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id PAA23823; Sat, 2 Aug 1997 15:42:33 -0700 (PDT) Date: Sat, 2 Aug 1997 15:42:32 -0700 (PDT) From: "J. Utz" To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: correct me if i am wrong :-) Re: working snap of new sound driver In-Reply-To: <199707311434.QAA05841@labinfo.iet.unipi.it> 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; Am i mistaken, or is PAS support waiting for somebody to go back thru all the pas2*.[ch] files and make them look like sb_dsp.c and ad1848.c ? tnx! john who has decided to go out and enjoy the remainder of the afternoon while he waits for an answer! ******************************************************************************* John Utz spaz@u.washington.edu idiocy is the impulse function in the convolution of life From owner-freebsd-hackers Sat Aug 2 16:00:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20214 for hackers-outgoing; Sat, 2 Aug 1997 16:00:10 -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 QAA20209 for ; Sat, 2 Aug 1997 16:00:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00412; Sat, 2 Aug 1997 15:58:11 -0700 From: Terry Lambert Message-Id: <199708022258.PAA00412@phaeton.artisoft.com> Subject: Re: device close behaviour - a question To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 2 Aug 1997 15:58:10 -0700 (MST) Cc: jas@flyingfox.com, luigi@labinfo.iet.unipi.it, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708020252.MAA08782@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 2, 97 12:22: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 > > [Luigi Rizzo would like his audio driver to be notified every time > > the device is closed, not just on last close.] > > > > The way I've dealt with a similar situation in the past is to represent > > each physical device as an array of minor device numbers, on each of > > which the driver enforces an exclusive-open. User-level code must > > The point I am trying to make here is that you _cannot_ enforce an > exclusive open, because the devic driver is not notified under all of > the circumstances which result in a new fd being granted. This was kinda my point as well on the "addref" response. Really, there is a need for this notification to happen in all cases. Really, the only issues are dup, dup2 (a special case of dup), fork, close on exec, and descriptor passing (this last is not really an issue, IMO -- I think it falls into the dup case). I'm 100% behind Poul on this one... 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 2 16:02:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20328 for hackers-outgoing; Sat, 2 Aug 1997 16:02:28 -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 QAA20320; Sat, 2 Aug 1997 16:02:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA00445; Sat, 2 Aug 1997 16:02:10 -0700 From: Terry Lambert Message-Id: <199708022302.QAA00445@phaeton.artisoft.com> Subject: Re: non-blocking file i/o To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sat, 2 Aug 1997 16:02:09 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <7776.870502484@orion.webspan.net> from "Gary Palmer" at Aug 2, 97 02:14: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 > A friend (who mainly does his devel under solaris/linux) recently came > up with a patch to the INN database code which made the writes > non-blocking. On linux/solaris, the non-blocking writes would take > fractions of a ms. On FreeBSD, the blocking write took 8ms and the > ``non-blocking'' write took 4ms (set using fcntl). It also seems that > Linux and Solaris use open(file, O_NONBLOCK, 0) to put the file into > non-blocking mode for reading and writing also, where our open flag > only affects the open. Are you confusion O_NONBLOCK with O_NDELAY? It used to be on SysV systems that O_NDELAY was "open without waiting for DCD on modem control devices" and *also* put the device into non-blocking mode. 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 2 16:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20691 for hackers-outgoing; Sat, 2 Aug 1997 16:11: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 QAA20684 for ; Sat, 2 Aug 1997 16:10:57 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA00461; Sat, 2 Aug 1997 16:10:06 -0700 From: Terry Lambert Message-Id: <199708022310.QAA00461@phaeton.artisoft.com> Subject: Re: Pentium II? To: tony@dell.com (Tony Overfield) Date: Sat, 2 Aug 1997 16:10:06 -0700 (MST) Cc: terry@lambert.org, brianc@milkyway.com, hackers@FreeBSD.ORG In-Reply-To: <3.0.2.32.19970802023853.0069c4c4@bugs.us.dell.com> from "Tony Overfield" at Aug 2, 97 02:38:53 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 > >Dell was selling them. > > This is wrong! > > Dell sold no such thing as a "P5 DX/2-66"! You guys didn't call them that, but the memory bus was running at 33MHz; that's "clock doubled" in my book. I have a friend who had one until the Pentium math bugs reared their ugly heads (he was an IDE weenie, so he didn't care that PCI bus mastering failed on the thing). > >This was back when they were using the > >Saturn I chipset, which did not have DMA writeback notification > >connected from the macrocell (missing trace). > > Due to that bug, that version of the Saturn chipset does not support > write-back L2 caching and it is therefore configured by the BIOS to > use the L2 cache in write-through mode, though the L1 cache is always > write-back. The missing trace is not used or needed when the L2 > cache is in write-through mode. Unless a DMA initiated by a controller rather than the host occurs. Check the -hackers list archives for postings on disabling the L1 and L2 cache on these monstrosities... > >Dell also had 60MHz non-doubled chips > >available before the doubled 66's were available. > > Well, of course the 66 MHz chips were available after the 60 MHz > chips were, but they weren't "doubled." Maybe not; maybe the memory was just jumpered for an extra wait state; whatever; memory access was half as fast as it should have been in a reasonable implementation. > They probably would have, had the "doubled 66's" ever existed. > > >Just as my 486/50 kicks butt over the same chips. > > I doubt this, unless you're "stacking the deck" in some perverse > way, or you're simply dreaming. Of course I am, if an I/O intensive benchmark is "stacking the deck" and a CPU intensive benchmark is somehow "a good idea". I'm doing disk I/O, of course, and I am overclocking the EISA bus on the machine to 50MHz instead of 2x25. 50MHz EISA transfers data faster than 30MHz PCI... or 33MHz. 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 2 16:15:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20902 for hackers-outgoing; Sat, 2 Aug 1997 16:15:49 -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 QAA20878; Sat, 2 Aug 1997 16:15:30 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id QAA00352; Sat, 2 Aug 1997 16:15:05 -0700 (PDT) Message-Id: <199708022315.QAA00352@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "J. Utz" cc: Luigi Rizzo , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: correct me if i am wrong :-) Re: working snap of new sound driver In-reply-to: Your message of "Sat, 02 Aug 1997 15:42:32 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 Aug 1997 16:15:05 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lets try to keep the low level soundcard specific stuff on multimedia mailing list and whenever we need OS specific assistance we should post to hackers. Tnks, Amancio >From The Desk Of "J. Utz" : > Hi; > > Am i mistaken, or is PAS support waiting for somebody to go back thru all > the pas2*.[ch] files and make them look like sb_dsp.c and ad1848.c ? > > tnx! > > john > > who has decided to go out and enjoy the remainder of the afternoon while > he waits for an answer! > > ***************************************************************************** ** > John Utz spaz@u.washington.edu > idiocy is the impulse function in the convolution of life > > From owner-freebsd-hackers Sat Aug 2 16:46:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22297 for hackers-outgoing; Sat, 2 Aug 1997 16:46:05 -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 QAA22292 for ; Sat, 2 Aug 1997 16:46:02 -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 QAA16879; Sat, 2 Aug 1997 16:45:10 -0700 (PDT) To: "Mark J. Taylor" cc: hackers@FreeBSD.ORG Subject: Re: make world for 2.2.2 with DESTDIR fails In-reply-to: Your message of "Sat, 02 Aug 1997 18:02:29 EDT." Date: Sat, 02 Aug 1997 16:45:10 -0700 Message-ID: <16875.870565510@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If there is some work that needs to be done to use the DESTDIR option, > then I'd be glad to do it and send diffs. First, though, I have to > identify if I am at fault (from lack of knowledge), or if there is > actually a problem here. There is actually a problem here. Good luck! :-) Jordan From owner-freebsd-hackers Sat Aug 2 16:53:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22567 for hackers-outgoing; Sat, 2 Aug 1997 16:53:24 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22562 for ; Sat, 2 Aug 1997 16:53:21 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id TAA05915; Sat, 2 Aug 1997 19:53:19 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id TAA21592; Sat, 2 Aug 1997 19:53:19 -0400 (EDT) To: Terry Lambert cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: non-blocking file i/o In-reply-to: Your message of "Sat, 02 Aug 1997 16:02:09 PDT." <199708022302.QAA00445@phaeton.artisoft.com> Date: Sat, 02 Aug 1997 19:53:19 -0400 Message-ID: <21590.870565999@orion.webspan.net> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote in message ID <199708022302.QAA00445@phaeton.artisoft.com>: > > A friend (who mainly does his devel under solaris/linux) recently came > > up with a patch to the INN database code which made the writes > > non-blocking. On linux/solaris, the non-blocking writes would take > > fractions of a ms. On FreeBSD, the blocking write took 8ms and the > > ``non-blocking'' write took 4ms (set using fcntl). It also seems that > > Linux and Solaris use open(file, O_NONBLOCK, 0) to put the file into > > non-blocking mode for reading and writing also, where our open flag > > only affects the open. > > Are you confusion O_NONBLOCK with O_NDELAY? There is no difference on FreeBSD. For files, they are both NOPS. > It used to be on SysV systems that O_NDELAY was "open without waiting > for DCD on modem control devices" and *also* put the device into > non-blocking mode. No idea. I don't have a linux/solaris system to play with (not quite true, but I'm not touching the Solaris/x86 box here more than I have to). All I *DO* know, is when the file was opened with O_NONBLOCK, both Solaris and Linux recorded write() times in fractions of a milisecond. FreeBSD consistantly recorded write() times in the order of 8ms on my test box. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sat Aug 2 16:58:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22870 for hackers-outgoing; Sat, 2 Aug 1997 16:58:28 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22865; Sat, 2 Aug 1997 16:58:22 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id TAA06388; Sat, 2 Aug 1997 19:58:21 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id TAA22936; Sat, 2 Aug 1997 19:58:21 -0400 (EDT) To: dyson@FreeBSD.ORG cc: hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: non-blocking file i/o In-reply-to: Your message of "Sat, 02 Aug 1997 02:07:22 CDT." <199708020707.CAA11836@dyson.iquest.net> Date: Sat, 02 Aug 1997 19:58:20 -0400 Message-ID: <22934.870566300@orion.webspan.net> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "John S. Dyson" wrote in message ID <199708020707.CAA11836@dyson.iquest.net>: > The AIO code is a standard (nice) way to implement database I/O. Will it allow the write() to complete more quickly and actually be async, or just provide a callback to the program when the OS finally commits the data to disk? For INN's DBZ, I don't think the callback matters at all. The time it takes to do the write() is what is important in this case. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Sat Aug 2 20:17:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01125 for hackers-outgoing; Sat, 2 Aug 1997 20:17:29 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01118 for ; Sat, 2 Aug 1997 20:17:26 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id UAA28022; Sat, 2 Aug 1997 20:20:45 -0700 (PDT) Date: Sat, 2 Aug 1997 20:20:45 -0700 (PDT) From: Howard Lew To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: device close behaviour - a question In-Reply-To: <199708010302.FAA06838@labinfo.iet.unipi.it> 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 had a chance to play around with the sound code. I like the driver documentation a lot. Is the guspnp14 stuff much different from Luigi's snd970726 code? Hmmm... Is the isa_dmastatus really used at this point? I looked around the isa code trying to patch it up to compile, but I couldn't find a function related to it. Or was this the question below? > > I am having a problem related to the having multiple (actually, > 2) open descriptors on the same character device. More specifically, > I notice that only the last close does actually invoke the device > close routine. > > >From the code in /sys/miscfs/specfs/spec_vnops.c, function > spec_close(), this behaviour seems intentional. But can someone > explain why this is done and where this is useful ? > I do not dare to suggest that this be changed since I guess it would > break many things... or not ? > > In my case, I have implemented the ability of having up to two open > descriptors on full-duplex audio devices, one for read and one for > write. The above behaviour does not let me record that a channel > has been freed (this I would have done using the close() call), > and complicates life to the driver since it has to guess what is > happening. > > I do have locks on concurrent operations of the same type, and have > implemented some hacks to (more or less) control that proper device > usage is done. However, these are hacks, and the lack of information > can cause suboptimal behaviours. As an example, due to the missing > close I cannot decide to stop a DMA read since I don't know if the > reading process has gone. > > 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/ > _____________________________|______________________________________ > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hackers Sat Aug 2 22:09:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA04963 for hackers-outgoing; Sat, 2 Aug 1997 22:09:52 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA04958 for ; Sat, 2 Aug 1997 22:09:48 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id BAA04333; Sun, 3 Aug 1997 01:09:46 -0400 (EDT) Message-ID: <19970803010946.06461@crh.cl.msu.edu> Date: Sun, 3 Aug 1997 01:09:46 -0400 From: Charles Henrich To: freebsd-hackers@freebsd.org Subject: tty-level buffer overflows Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.80 X-Operating-System: FreeBSD 2.2.2-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've searched the FreeBSD archives over and over, and all I find is dozens of complaints of this error (I too am seeing it: sio0: 1081 more tty-level buffer overflows (total 3960) sio0: 526 more tty-level buffer overflows (total 4486) sio0: 532 more tty-level buffer overflows (total 5018) sio0: 2784 more tty-level buffer overflows (total 7802) sio0: 9439 more tty-level buffer overflows (total 17241) sio0: 677 more tty-level buffer overflows (total 17918) But no resolutions.. Because of this I cannot use the serial ports on my FreeBSD box.. does anyone have any solutions? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Sat Aug 2 23:27:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA07718 for hackers-outgoing; Sat, 2 Aug 1997 23:27:31 -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 XAA07713 for ; Sat, 2 Aug 1997 23:27:29 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wuu8H-0003Pu-00; Sat, 2 Aug 1997 23:27:13 -0700 Date: Sat, 2 Aug 1997 23:27:12 -0700 (PDT) From: Tom Samplonius To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: tty-level buffer overflows In-Reply-To: <19970803010946.06461@crh.cl.msu.edu> 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, 3 Aug 1997, Charles Henrich wrote: > I've searched the FreeBSD archives over and over, and all I find is dozens of > complaints of this error (I too am seeing it: > > sio0: 1081 more tty-level buffer overflows (total 3960) > sio0: 526 more tty-level buffer overflows (total 4486) > sio0: 532 more tty-level buffer overflows (total 5018) > sio0: 2784 more tty-level buffer overflows (total 7802) > sio0: 9439 more tty-level buffer overflows (total 17241) > sio0: 677 more tty-level buffer overflows (total 17918) > > But no resolutions.. Because of this I cannot use the serial ports on my > FreeBSD box.. does anyone have any solutions? Dozens of complaints? Generally the above is caused by a poor UART, and and an overloaded CPU. I've seen it with p2p links, when the link dies but the application (in this case a stupid UDP app) keeps pumping data. Since it has no place to go, so the kernel throws it aways, and prints a warning. I've never seen that error in normal operation. I see some overruns on 115200 bps ppp connection to 3COM ISDN TA. But this was only a 486 that is running a lot of stuff, and should be upgraded to a faster CPU. > -Crh > > Charles Henrich Michigan State University henrich@msu.edu > > http://pilot.msu.edu/~henrich > > Tom From owner-freebsd-hackers Sat Aug 2 23:57:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08792 for hackers-outgoing; Sat, 2 Aug 1997 23:57:41 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08787 for ; Sat, 2 Aug 1997 23:57:35 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id CAA05166; Sun, 3 Aug 1997 02:57:30 -0400 (EDT) Message-ID: <19970803025730.57257@crh.cl.msu.edu> Date: Sun, 3 Aug 1997 02:57:30 -0400 From: Charles Henrich To: Tom Samplonius Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: tty-level buffer overflows References: <19970803010946.06461@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.80 In-Reply-To: ; from Tom Samplonius on Sat, Aug 02, 1997 at 11:27:12PM -0700 X-Operating-System: FreeBSD 2.2.2-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: tty-level buffer overflows, Tom Samplonius stated: > Dozens of complaints? Well, at least a dozen. > Generally the above is caused by a poor UART, and and an overloaded CPU. Not in this case, its a 16550A, on a 486/66 doing absolutely nothing except trying to do filetransfer over the serial port with a custom app I wrote.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich