From owner-freebsd-hackers Sun Dec 20 02:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25111 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 02:59:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dana.clari.net.au (dana.clari.net.au [203.27.85.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA25106 for ; Sun, 20 Dec 1998 02:59:30 -0800 (PST) (envelope-from peter@clari.net.au) Received: from localhost (peter@localhost) by dana.clari.net.au (8.9.1/8.8.7) with ESMTP id VAA12149; Sun, 20 Dec 1998 21:59:16 +1100 (EST) (envelope-from peter@clari.net.au) X-Authentication-Warning: dana.clari.net.au: peter owned process doing -bs Date: Sun, 20 Dec 1998 21:59:16 +1100 (EST) From: Peter Hawkins To: Mike Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: WP 8 Howto In-Reply-To: <199812151311.FAA05421@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, I *meant* that you can turn your Gates partition into swap. I didn't say wp is heavy on swap. I am also most surprised to hear that loading the linux kvm affects the installation of libraries - certainly it made no difference to me that I've seen so far. Still you're the guru there I know so I'll take your word for it. You are probably correct about the .gz netscape-ism. I also have had a 100% success rate loading word documents and it is all very well to say "buy the CD" (which I'm doing) but that is beside the point. Try following the install instructions and selecting the aus dictionary. It will install but the binary will then not run. I was letting people know how to get an install to go. Peter Clarinet Internet Solutions Peter Hawkins 381 Swan St Richmond, Vic, Australia Ph: +61-3-9421 2006 Fax: +61-3-9421 2007 http://www.clari.net.au Peter@clari.net.au FreeBSD Project: thepish@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 03:40:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01336 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 03:40:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01291 for ; Sun, 20 Dec 1998 03:39:55 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id KAA00744; Sun, 20 Dec 1998 10:01:16 +0200 (EET) Date: Sun, 20 Dec 1998 10:01:16 +0200 (EET) From: Narvi To: rssh@grad.kiev.ua cc: "Jordan K. Hubbard" , Terry Lambert , dkelly@hiwaay.net, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Back to sysinstall (was Re: Fortran in the base system (was Re: sysinstall)) In-Reply-To: <367BDDA7.52011CC7@Shevchenko.Kiev.UA> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Dec 1998, Ruslan Shevchenko wrote: > Jordan K. Hubbard wrote: > > > > a) to get the new package system, we need good C/C++ compiler > > > > yes. > > > > > b) to get good C/C++ compiler, we need TenDRA > > It yet not able to compile STL. This sentence is unparseable. What is not yet able to compile STL? And What do you mean by compiling STL? Among all the other things: a) gcc is not STL compatible, it just doesn't fully support C++ yet, plus there are some misc bogons of the (let's do it so, it will in time make it to the standard) kind. b) TenDRA as produced by the port is unusable. Among other things, the port does not for some reason include support for long long (cure with the addition of one line to the build config file) c) TenDRA implements full C++ as of Nov. 1997 draft. It does not, however, come with the full set of standard libraries. As it is combinable with the SGI STL implementation, the only piece really missing is the iostreams library. Compared to what will be needed to be doem to get the system compilable with TenDRA, it is a minor problem. [snip] Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 04:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03744 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 04:02:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03739 for ; Sun, 20 Dec 1998 04:02:18 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id IAA08356; Sun, 20 Dec 1998 08:02:06 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 20 Dec 1998 08:02:06 -0400 (AST) From: The Hermit Hacker To: Peter Hawkins cc: freebsd-hackers@FreeBSD.ORG, custserv2@corel.ca Subject: Re: Howto: wordperfect 8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, Peter Hawkins wrote: > Ever wanted to turn that little dos partition into a swap partition? Well > now is your chance and while you're at it you'll be helping to make your > stand against OS monopolies by supporting Corel in what is a brave and > commendable move. > > Corel released wp 8 for linux this week and after some playing I managed to > make it run. the 90 day free trial version is at http://www.downloads.com. > It will read your word documents and provides as good or better functionality > than Word IMHO. > > I am using: FreeBSD 3.0 stable, X11R6 (latest release) > > Unfortunately it does not install as documented but you can do it anyway as > follows: Just curious, but what failed for you? I just downloaded it, ran the Runme file, and have it up and running on my screen...in fact, just laoded a Word97 file up, which was why I downloaded it... > 5. The Runme installer fails so to install do the following in the directory > from which you did step 4 above: > > cd linux/bin In my case, after untar'ng, I didn't have this directory...all I had was: .wpdata b_ins00.bk b_us00.bk g_req03.bk GUILG00.GZ b_ins01.bk g_req00.bk g_us00.bk Readme b_req00.bk g_req01.bk g_us01.bk Runme b_req01.bk g_req02.bk > cat mwp?? > mwp > cd ../../shared > foreach i ( sf5028 sf5128 prs_b prs_g prs5028 prs5128 ) > cp ${i}.us ${i}c.us > done > cd .. > ln -s shared/install.wp . > ./install.wp > > 6. (a) Don't attempt to install non-us dictionaries or thesauruses - if you > can work out how let me know! They do not seem to be there for me. > > (b) ignore the warnings about files not being found > > (c) ignore the lack of printer drivers in the menu and continue without > installing a printer - it seems to install them all anyway (at least > it did for me) > > 7. Use the trial version until you are convinced it's the best word processor > around (approx 10 minutes) then I would strongly urge you to register your > copy at https://livewire.corel.com/wp8LinuxReg/register.html - For less > than $70 you can save yourself $$$ in updating corel's competitor program, > add the dos partition as a swap partition and get more memory for your box > and show the world's software houses that taking a punt on FreeBSD/Linux > can pay off. > > Peter > > Clarinet Internet Solutions Peter Hawkins > 381 Swan St Richmond, > Vic, Australia Ph: +61-3-9421 2006 Fax: +61-3-9421 2007 > http://www.clari.net.au Peter@clari.net.au > > FreeBSD Project: thepish@FreeBSD.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 04:08:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05477 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 04:08:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wind.freenet.am ([194.151.101.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05454 for ; Sun, 20 Dec 1998 04:08:37 -0800 (PST) (envelope-from casper@acc.am) Received: from lemming.acc.am (acc.freenet.am [194.151.101.251]) by wind.freenet.am (8.9.1/8.9.1) with ESMTP id QAA07342 for ; Sun, 20 Dec 1998 16:08:28 +0400 (GMT) Received: from acc.am (nightmar.acc.am [192.168.100.108]) by lemming.acc.am (8.9.1a/8.9.1) with ESMTP id QAA03458 for ; Sun, 20 Dec 1998 16:11:16 +0400 (AMT) Message-ID: <367CA2FC.3F42F288@acc.am> Date: Sun, 20 Dec 1998 11:10:52 +0400 From: Casper Organization: Armenian Computer Center X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Joliet file system? References: <367C5118.4C32904B@freedomnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone give me some documents/description/standard of this file system ? I have the same proble and wonna try to hack a cd9660 module ...... I already analized dump of this FS , but there are a lot problems ..... I'll we thankful if you send any docs/URLs :) Kelly Yancey wrote: > > You have to forgive me if this has already been done in 3.0, but I'm > still in stable-ville; is there any interest, or has there been any > effort to add the Joliet extensions to the the iso9660 filesystem? > > Thanks, > > Kelly > > -- > Kelly Yancey "Bill Gates is only a white Persian cat and > ~kbyanc@freedomnet.com~ a monocle away from being the villain in a > James Bond movie" - comedian Dennis Miller > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 05:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11359 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 05:37:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11350 for ; Sun, 20 Dec 1998 05:37:39 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id PAA03483; Sun, 20 Dec 1998 15:36:25 +0200 Message-ID: <367D19A1.B83221D8@Shevchenko.Kiev.UA> Date: Sun, 20 Dec 1998 17:37:05 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Narvi CC: rssh@grad.kiev.ua, "Jordan K. Hubbard" , Terry Lambert , dkelly@hiwaay.net, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Back to sysinstall (was Re: Fortran in the base system (was Re: sysinstall)) References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Narvi wrote: > On Sat, 19 Dec 1998, Ruslan Shevchenko wrote: > > > Jordan K. Hubbard wrote: > > > > > > a) to get the new package system, we need good C/C++ compiler > > > > > > yes. > > > > > > > b) to get good C/C++ compiler, we need TenDRA > > > > It yet not able to compile STL. > > This sentence is unparseable. What is not yet able to compile STL? And > What do you mean by compiling STL? It means, that I spend many time, trying to port STL port to TenDRA, After I fix all *misunderstandig* of "TenDRA C++ standart " and STL, I discovered, that any program wich use STL and have more 10 lines in length , cause "Internal error" message during compiling. > > Among all the other things: > a) gcc is not STL compatible, it just doesn't fully support C++ > yet, plus there are some misc bogons of the (let's do it so, it > will in time make it to the standard) kind. egcs is, in some sence. > > b) TenDRA as produced by the port is unusable. Among other things, > the port does not for some reason include support for long > long (cure with the addition of one line to the build config > file) You can add this support by command line option C++ standart have not longlong type. > > c) TenDRA implements full C++ as of Nov. 1997 draft. It does not, > however, come with the full set of standard libraries. As it is > combinable with the SGI STL implementation, the only piece > really missing is the iostreams library. Compared to what will > be needed to be doem to get the system compilable with TenDRA, > it is a minor problem. Usially, better to check such information before declaring ;) I ported GNU Iostream to TenDRA, but I was unable to port STL. And as I guess, the development of TenDRA is stopped. In principle, it is quite good idea to get TenDRA used, but only if anybody with good knovellage of it internals decide to support it. > > [snip] > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 06:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14251 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 06:16:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14243 for ; Sun, 20 Dec 1998 06:16:10 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id QAA03872; Sun, 20 Dec 1998 16:15:52 +0200 (EET) Date: Sun, 20 Dec 1998 16:15:52 +0200 (EET) From: Narvi To: rssh@grad.kiev.ua cc: "Jordan K. Hubbard" , Terry Lambert , dkelly@hiwaay.net, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Back to sysinstall (was Re: Fortran in the base system (was Re: sysinstall)) In-Reply-To: <367D19A1.B83221D8@Shevchenko.Kiev.UA> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, Ruslan Shevchenko wrote: > Narvi wrote: > > > On Sat, 19 Dec 1998, Ruslan Shevchenko wrote: > > > > > Jordan K. Hubbard wrote: > > > > > > > > a) to get the new package system, we need good C/C++ compiler > > > > > > > > yes. > > > > > > > > > b) to get good C/C++ compiler, we need TenDRA > > > > > > It yet not able to compile STL. > > > > This sentence is unparseable. What is not yet able to compile STL? And > > What do you mean by compiling STL? > > It means, that I spend many time, trying to port STL port to TenDRA, > > After I fix all *misunderstandig* of > "TenDRA C++ standart " and STL, I discovered, > that any program wich use STL and have more 10 lines in length , cause > "Internal error" message during compiling. > > > > > > Among all the other things: > > a) gcc is not STL compatible, it just doesn't fully support C++ > > yet, plus there are some misc bogons of the (let's do it so, it > > will in time make it to the standard) kind. > > egcs is, in some sence. > Unless you want to use something like nested templates > > > > b) TenDRA as produced by the port is unusable. Among other things, > > the port does not for some reason include support for long > > long (cure with the addition of one line to the build config > > file) > > You can add this support by command line option > > C++ standart have not longlong type. > long long supprt is needed to compile FreeBSD sources. Pretty much any FreeBSD sources. > > > > c) TenDRA implements full C++ as of Nov. 1997 draft. It does not, > > however, come with the full set of standard libraries. As it is > > combinable with the SGI STL implementation, the only piece > > really missing is the iostreams library. Compared to what will > > be needed to be doem to get the system compilable with TenDRA, > > it is a minor problem. > > Usially, better to check such information before declaring ;) I have been using TenDRA for some time now. While I am a bit more interested in the C side ofthe things, I have both used and tested the c++ side of it aswell. > I ported GNU Iostream to TenDRA, but I was unable to port STL. Was it the SGI STL or the "adaption of SGI STL"? GNU iostreams is *unusable* with TenDRA. A clause in the copyright of GNU iostreams declares that linking with GNU iostreams (which is under the GPL) does not cause the other code to fall under GPL *IF* it is used with a GNU compiler. But as TenDRA is not a GNU compiler... > And as I guess, the development of TenDRA is stopped. > I haven't checked, but I find nothing supporting this. > In principle, it is quite good idea to get TenDRA used, but only if anybody > with good knovellage of it internals decide to support it. > Agreed. Sander There is no love, no good, no happiness and no future - all these are just illusions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 06:55:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17102 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 06:55:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17097 for ; Sun, 20 Dec 1998 06:55:52 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id PAA19814; Sun, 20 Dec 1998 15:55:29 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id QAA00552; Sun, 20 Dec 1998 16:55:55 GMT (envelope-from son) Message-ID: <19981220165555.52107@breizh.prism.uvsq.fr> Date: Sun, 20 Dec 1998 16:55:55 +0000 From: Nicolas Souchu To: Drew Baxter Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp Subject: Re: Mainboard Monitor Probes References: <4.1.19981218001152.009ae100@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <4.1.19981218001152.009ae100@genesis.ispace.com>; from Drew Baxter on Fri, Dec 18, 1998 at 12:17:31AM -0500 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 18, 1998 at 12:17:31AM -0500, Drew Baxter wrote: > >Maybe someone has brought this up before, Didn't really know how to go about searching for it on the FreeBSD search page. > >My Supermicro P6SBA Mainboard (like many Pentium II boards) has 11 hardware monitors installed. Aparantely these are linked to the BIOS, and the Super Doctor software for Win* directly communicates with it to give realtime voltages and temperatures. > >The question is, is there currently any way to access these levels under FreeBSD? This would be pretty nice information to throw into some sort of an administration CGI or status CGI. Maybe I've just been hitting the caffiene too hard... naah. > >If there is actually one or it's been brought up, I apologize in advance. Was not quite sure if "Cool Mainboard Temperature Thingy" would be a valid search criteria :-) > There's some work in progress. The iicbus/smbus framework present in -current branch provides generic mechanism for I2C and SMBus support. We're working one the PIIX4 smbus function support (Takanori Watanabe ) which is the function present in newer Intel chips. Now the question is "what are the involved monitor components on your board?" LMxx? W83781? You propose a cgi, a great idea. You may want to interface with "Steve Friedrich" Nicolas. > >--- >Drew "Droobie" Baxter >Network Admin/Professional Computer Nerd(TM) >OneEX: The OneNetwork Exchange, Bangor Maine USA >http://www.droo.orland.me.us > >PGP ID: 409A1F7D > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 07:30:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19928 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 07:30:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19923 for ; Sun, 20 Dec 1998 07:30:29 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4018.ime.net [209.90.195.28]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id KAA27717; Sun, 20 Dec 1998 10:30:23 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981220100335.009f3ee0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 20 Dec 1998 10:28:12 -0500 To: Nicolas Souchu From: Drew Baxter Subject: Re: Mainboard Monitor Probes Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp In-Reply-To: <19981220165555.52107@breizh.prism.uvsq.fr> References: <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:55 PM 12/20/98 +0000, Nicolas Souchu wrote: > >There's some work in progress. The iicbus/smbus framework present in -current >branch provides generic mechanism for I2C and SMBus support. We're working >one the PIIX4 smbus function support (Takanori Watanabe >) which is the function present >in newer Intel chips. I do have SMBUS installed, but it doesn't detect the hardware monitor, at least not that I can tell in dmesg. The only I2C device in there is the Brooktree 848 card that Intel gave me a while back.. >Now the question is "what are the involved monitor components on your board?" >LMxx? W83781? Ok, I disassembled the program, got nowhere. But when I disassembled its DLL, I found two string refs.. "National LM78 Compatible" "Winbond 83781D". I'd assume all of their boards are the same since this Super Doctor program comes on the installation cd with the boards. Can't seem to find any technical specs on the board itself aside from disassembly.. >You propose a cgi, a great idea. You may want to interface with >"Steve Friedrich" I did the perl thing a few years ago. Been using it ever since for a lot of various things.. Direct interface into the monitors would be a good addon to a runtime status page certainly. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 07:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21815 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 07:56:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21810 for ; Sun, 20 Dec 1998 07:56:09 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4018.ime.net [209.90.195.28]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id KAA27783; Sun, 20 Dec 1998 10:55:05 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981220105116.00c01400@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 20 Dec 1998 10:52:54 -0500 To: Nicolas Souchu From: Drew Baxter Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp In-Reply-To: <19981220165555.52107@breizh.prism.uvsq.fr> References: <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.netroedge.com/~lm78/ Appears someone is already trying to do it for Linux.. maybe these can be ported some, not sure.. Aparantely it supports the W83781D, which I guess I have on all of my Supermicro boards.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 08:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23571 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 08:11:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23566 for ; Sun, 20 Dec 1998 08:11:49 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.121]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA3E4B; Sun, 20 Dec 1998 17:11:47 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36797669.29CC1C37@most.fw.hac.com> Date: Sun, 20 Dec 1998 17:18:07 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Bill Loraine Subject: RE: Writing device drivers for FreeBSD Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc:-ed to hackers, removed from doc] On 17-Dec-98 Bill Loraine wrote: > In the Tutorial "Writing device drivers for FreeBSD" on the Standard > Model steps required for adding a driver, step 2 Make room in conf.c - > Which the tutorial says is located in "/usr/src/sys/i386/i386/conf.c" on > my operating system files(my hard drive with FreeBSD installed) I don't > have a conf.c file at all much less in that location. I think conf.c needs to be renamed to autoconf.c. Then again, I might be wrong. Someone care to update/verify my assumption? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 08:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23750 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 08:14:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shidahara1.planet.kobe-u.ac.jp (shidahara1.planet.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23745 for ; Sun, 20 Dec 1998 08:14:35 -0800 (PST) (envelope-from takawata@shidahara1.planet.kobe-u.ac.jp) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id BAA15545; Mon, 21 Dec 1998 01:05:29 +0900 (JST) Message-Id: <199812201605.BAA15545@shidahara1.planet.kobe-u.ac.jp> To: Drew Baxter cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp, Nicolas Souchu Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) In-reply-to: Your message of "Sun, 20 Dec 1998 10:52:54 EST" References: <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981220105116.00c01400@genesis.ispace.com> Date: Mon, 21 Dec 1998 01:05:28 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.1.19981220105116.00c01400@genesis.ispace.com>, Mr./Ms. Drew Baxter : >http://www.netroedge.com/~lm78/ > >Appears someone is already trying to do it for Linux.. maybe these can be >ported some, not sure.. Many datasheets are available at http://developer.intel.com/ial/WfM/wfm20/design/sensdt/SDTSTEP.HTM . (including LM75/78.) NOTICE: I'm not subscriber of hackers@FreeBSD.ORG . Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 08:18:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24103 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 08:18:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24097 for ; Sun, 20 Dec 1998 08:18:54 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4018.ime.net [209.90.195.28]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id LAA27902; Sun, 20 Dec 1998 11:18:42 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981220111603.00c08350@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 20 Dec 1998 11:16:32 -0500 To: Takanori Watanabe From: Drew Baxter Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp, Nicolas Souchu In-Reply-To: <199812201605.BAA15545@shidahara1.planet.kobe-u.ac.jp> References: <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981220105116.00c01400@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:05 AM 12/21/98 +0900, Takanori Watanabe wrote: >In message <4.1.19981220105116.00c01400@genesis.ispace.com>, Mr./Ms. Drew >Baxter >: >>http://www.netroedge.com/~lm78/ >> >>Appears someone is already trying to do it for Linux.. maybe these can be >>ported some, not sure.. > >Many datasheets are available at >http://developer.intel.com/ial/WfM/wfm20/design/sensdt/SDTSTEP.HTM Unfortunately I'm not a hardware guy.. minor soldering and all, but no implementation/driver work :) --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 08:50:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27552 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 08:50:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27547 for ; Sun, 20 Dec 1998 08:50:34 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id SAA03945; Sun, 20 Dec 1998 18:49:53 +0200 Message-ID: <367D46FA.5A587C09@Shevchenko.Kiev.UA> Date: Sun, 20 Dec 1998 20:50:34 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Narvi CC: rssh@grad.kiev.ua, "Jordan K. Hubbard" , Terry Lambert , dkelly@hiwaay.net, FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Back to sysinstall (was Re: Fortran in the base system (was Re: sysinstall)) References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I ported GNU Iostream to TenDRA, but I was unable to port STL. > > Was it the SGI STL or the "adaption of SGI STL"? > It was MetaByte port of STL. i. e. "adaption of SGI STL" (based on SGI STL + autoconfig + couple of defines.) Of course, after I checking SGI STL . > > GNU iostreams is *unusable* with TenDRA. A clause in the copyright of GNU > iostreams declares that linking with GNU iostreams (which is under the > GPL) does not cause the other code to fall under GPL *IF* it is used with > a GNU compiler. But as TenDRA is not a GNU compiler... Hmm, really, GNU-ism is dangerous. In principle, it is not very difficult to write own one. > > > And as I guess, the development of TenDRA is stopped. > > > > I haven't checked, but I find nothing supporting this. > 4.1.2 was *very* buggy in C++ side, and it was year ago. Updates or next minor version are absent. We can ask Robert Anderson about current TenDRA status. > > > In principle, it is quite good idea to get TenDRA used, but only if anybody > > with good knovellage of it internals decide to support it. > > > > Agreed. > So if you will find such person, inform me ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 10:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05269 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 10:21:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05263 for ; Sun, 20 Dec 1998 10:21:30 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id TAA24131; Sun, 20 Dec 1998 19:21:15 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id UAA11745; Sun, 20 Dec 1998 20:21:08 GMT (envelope-from son) Message-ID: <19981220202106.49153@breizh.prism.uvsq.fr> Date: Sun, 20 Dec 1998 20:21:06 +0000 From: Nicolas Souchu To: Drew Baxter Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) References: <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <19981220165555.52107@breizh.prism.uvsq.fr> <4.1.19981220105116.00c01400@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <4.1.19981220105116.00c01400@genesis.ispace.com>; from Drew Baxter on Sun, Dec 20, 1998 at 10:52:54AM -0500 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 20, 1998 at 10:52:54AM -0500, Drew Baxter wrote: > >http://www.netroedge.com/~lm78/ Really interesting! Linux' manpower is really surprising. Discouraging, but good news... all is already done. So, the best will be to port there code to FreeBSD, something like additionnal package to avoid GPL'ed code in the kernel distribution. But, if someone wants to rewrite it... this is not a problem. Controller drivers (PIIX4, VIA) will need particular attention since they're inside the kernel. Thanks to Takanori's work, we'll soon have the PIIX4 support. I don't know yet if the monitoring chips (LMxx and so) are supported with user-land code or kernel code. We initially planed to do this at user level. > >Appears someone is already trying to do it for Linux.. maybe these can be >ported some, not sure.. I hope this we'll be mostly an integration issue. What do you think about it Takanori? > >Aparantely it supports the W83781D, which I guess I have on all of my >Supermicro boards.. > Let's do it then. You could take charge of the GUI interfaces once we have defined kernel/user-low-level interfaces. Depending on there distribution we'll have to make a package or what else specific to FreeBSD. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 10:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08752 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 10:48:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08744 for ; Sun, 20 Dec 1998 10:48:39 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4002.ime.net [209.90.195.12]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id NAA00684; Sun, 20 Dec 1998 13:48:13 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981220134357.00a7f2d0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 20 Dec 1998 13:45:53 -0500 To: Nicolas Souchu From: Drew Baxter Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp In-Reply-To: <19981220202106.49153@breizh.prism.uvsq.fr> References: <4.1.19981220105116.00c01400@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <19981220165555.52107@breizh.prism.uvsq.fr> <4.1.19981220105116.00c01400@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:21 PM 12/20/98 +0000, Nicolas Souchu wrote: >On Sun, Dec 20, 1998 at 10:52:54AM -0500, Drew Baxter wrote: >> >>http://www.netroedge.com/~lm78/ > >Really interesting! Linux' manpower is really surprising. Discouraging, >but good news... all is already done. > >So, the best will be to port there code to FreeBSD, something like >additionnal package to avoid GPL'ed code in the kernel distribution. But, >if someone wants to rewrite it... this is not a problem. Controller drivers >(PIIX4, VIA) will need particular attention since they're inside the >kernel. Thanks to Takanori's work, we'll soon have the PIIX4 support. > >I don't know yet if the monitoring chips (LMxx and so) are supported with >user-land code or kernel code. We initially planed to do this at user level. > >> >>Appears someone is already trying to do it for Linux.. maybe these can be >>ported some, not sure.. > >I hope this we'll be mostly an integration issue. What do you think about >it Takanori? > >> >>Aparantely it supports the W83781D, which I guess I have on all of my >>Supermicro boards.. >> > >Let's do it then. You could take charge of the GUI interfaces once we have >defined kernel/user-low-level interfaces. Depending on there distribution >we'll have to make a package or what else specific to FreeBSD. The guys over at netroedge appear to have a rather tacky CGI going. .Seems like they're moving things to/fro NFS to their web server, and using GNUplot.. I think I saw a better graphing program somewhere. Just as long as you can get numbers, comma delimited or something, throwing it through perl would be a breeze. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 12:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15180 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 12:08:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15175 for ; Sun, 20 Dec 1998 12:08:21 -0800 (PST) (envelope-from kaleb@ics.com) Received: from kaleb.keithley.belmont.ma.us (pmdialin5.ics.com [140.186.40.179]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id PAA07184 Sun, 20 Dec 1998 15:08:18 -0500 (EST) Received: from kaleb.keithley.belmont.ma.us (localhost [127.0.0.1]) by kaleb.keithley.belmont.ma.us (8.9.1/8.9.1) with SMTP id QAA02497 for ; Sun, 20 Dec 1998 16:32:20 -0500 (EST) (envelope-from kaleb@ics.com) Message-ID: <367D6CE2.31DFF4F5@ics.com> Date: Sun, 20 Dec 1998 16:32:18 -0500 From: "Kaleb S. KEITHLEY" Reply-To: kaleb@ics.com Organization: Integrated Computer Solutions X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: where do the /usr/share/local/mumble directories get created Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Both /usr/src/usr.bin/{colldef,mklocale}/data/ makefiles assume the prior existance of /usr/share/local/mumble directories, e.g. /usr/share/locale/en_US.ISO_8859-1, into which e.g. /usr/share/locale/en_US.ISO_8859-1/{LC_CTYPE,LC_COLLATE} files or symlinks can be installed. Perhaps I don't have enough of the sources, or I'm looking in all the wrong places. Where do these directories get created? -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 12:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15298 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 12:09:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15293 for ; Sun, 20 Dec 1998 12:09:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA34020; Sun, 20 Dec 1998 12:09:21 -0800 (PST) (envelope-from dillon) Date: Sun, 20 Dec 1998 12:09:21 -0800 (PST) From: Matthew Dillon Message-Id: <199812202009.MAA34020@apollo.backplane.com> To: Greg Lehey Cc: Kaleb Keithley , hackers@FreeBSD.ORG Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. References: <199812191330.IAA26067@sunoco> <19981220102731.Q24125@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I don't know. A number of ``fixes'' were bandied around, but there :was so much discussion that I can't recall if any of them was the :final fix. : :> Did the fix not make it into 3.0-RELEASE? : :No. : :> Before I go snag the LaG inetd sources, will that fix the problem? : :I don't know. But some fixes were committed to -current about 10 days :ago which claim to have fixed the problem. Since then I haven't had :any problems. : :Greg :-- :See complete headers for address, home page and phone numbers :finger grog@lemis.com for PGP public key It should be all fixed now in -current. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 12:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18980 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 12:39:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18962 for ; Sun, 20 Dec 1998 12:39:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA46634; Sun, 20 Dec 1998 12:37:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812202037.MAA46634@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: Bill Loraine , FreeBSD Hackers Subject: Re: Writing device drivers for FreeBSD In-reply-to: Your message of "Sun, 20 Dec 1998 17:18:07 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 12:37:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [cc:-ed to hackers, removed from doc] > > On 17-Dec-98 Bill Loraine wrote: > > In the Tutorial "Writing device drivers for FreeBSD" on the Standard > > Model steps required for adding a driver, step 2 Make room in conf.c - > > Which the tutorial says is located in "/usr/src/sys/i386/i386/conf.c" on > > my operating system files(my hard drive with FreeBSD installed) I don't > > have a conf.c file at all much less in that location. > > I think conf.c needs to be renamed to autoconf.c. Then again, I might be wrong. > Someone care to update/verify my assumption? conf.c was exterminated lo, so many moons ago that I can't remember. It used to contain a static table of device driver entry points; truly a bad and sucky thing; they're now generated more or less automatically - still not perfect, but certainly less sucky. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 13:28:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23535 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 13:28:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23530 for ; Sun, 20 Dec 1998 13:28:26 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA04945; Sun, 20 Dec 1998 13:24:26 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdsl4939; Sun Dec 20 21:24:18 1998 Date: Sun, 20 Dec 1998 13:24:14 -0800 (PST) From: Julian Elischer To: Nicolas Souchu cc: Drew Baxter , hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp Subject: Re: Mainboard Monitor Probes In-Reply-To: <19981220165555.52107@breizh.prism.uvsq.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whistle has some basic support for the LM80 power-supply and environmental monitor chip. When I port it back to the IICbus generic code it may supply a basis to work on. On Sun, 20 Dec 1998, Nicolas Souchu wrote: > On Fri, Dec 18, 1998 at 12:17:31AM -0500, Drew Baxter wrote: > > > >Maybe someone has brought this up before, Didn't really know how to go about searching for it on the FreeBSD search page. > > > >My Supermicro P6SBA Mainboard (like many Pentium II boards) has 11 hardware monitors installed. Aparantely these are linked to the BIOS, and the Super Doctor software for Win* directly communicates with it to give realtime voltages and temperatures. > > > >The question is, is there currently any way to access these levels under FreeBSD? This would be pretty nice information to throw into some sort of an administration CGI or status CGI. Maybe I've just been hitting the caffiene too hard... naah. > > > >If there is actually one or it's been brought up, I apologize in advance. Was not quite sure if "Cool Mainboard Temperature Thingy" would be a valid search criteria :-) > > > > There's some work in progress. The iicbus/smbus framework present in -current > branch provides generic mechanism for I2C and SMBus support. We're working > one the PIIX4 smbus function support (Takanori Watanabe > ) which is the function present > in newer Intel chips. > > Now the question is "what are the involved monitor components on your board?" > LMxx? W83781? > > You propose a cgi, a great idea. You may want to interface with > "Steve Friedrich" > > Nicolas. > > > > >--- > >Drew "Droobie" Baxter > >Network Admin/Professional Computer Nerd(TM) > >OneEX: The OneNetwork Exchange, Bangor Maine USA > >http://www.droo.orland.me.us > > > >PGP ID: 409A1F7D > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-hackers" in the body of the message > > > > -- > nsouch@teaser..fr / nsouch@freebsd.org > FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 13:33:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24178 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 13:33:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24171 for ; Sun, 20 Dec 1998 13:33:11 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id QAA17785 for ; Sun, 20 Dec 1998 16:36:52 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 20 Dec 1998 16:36:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: hackers@FreeBSD.ORG Subject: question about re-entrancy. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm a bit confused. I've been watching the discussions going on about SMP. The issue of kernel re-entrancy has been brought up many times. So here's the question: I thought the kernel was re-entrant, when a process makes a syscall it's thread of execution enters the kernel where its arguments are validated and careful checks are done to ensure security then the syscall is done. If during the system call the process is put to sleep or rescheduled, another process may enter the kernel. As long as the splxxx() calls do not interfere with each other you have 2 processes excuting in the kernel at that point. (more can enter as well) Or.... what i'm now thinking is that once a process enters the kernel it must run until it exits the system call. I have a problem with this though, processes such as nfsiod/nfsd enter the kernel through a syscall and never exit (according to design and implementation) how then are other processes allowed into the kernel? Can anyone explain this a bit better? I understand deadlock can occur if something like this happens: process 1 process 2 syscall() splbio() rescheduled -----> syscall() splimp() <----- rescheduled splimp()? -no,reschedule-> <-no,reschedule- splbio()? splimp()? -no,reschedule-> splbio()? some sorta flipflop deadlock happens at this point as nested locks are held and won't be released as two in kernel processes never relinquish resources. Or are the spl calls simply there to diable interupts? but that brings me back to the question about "well how do nfsd and nfsiod do it?" Perhaps once an spl is initiated the process can not block? the more I thought about this, the more my head ached :) Mike, Terry, Matt, John? thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 13:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24466 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 13:38:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24460 for ; Sun, 20 Dec 1998 13:38:45 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA05069; Sun, 20 Dec 1998 13:31:37 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdnu5065; Sun Dec 20 21:31:36 1998 Date: Sun, 20 Dec 1998 13:31:33 -0800 (PST) From: Julian Elischer To: Jeroen Ruigrok/Asmodai cc: Bill Loraine , FreeBSD Hackers Subject: RE: Writing device drivers for FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG conf.c no longer exists. Every driver used to have to have an entry in it. Now each driver adds it's own entry dynamically using a function in kern_conf.c julian p.s. if it's an ISA device try running the script /usr/share/examples/drivers/make_device_driver.sh or /usr/share/examples/drivers/make_pseudo_driver.sh (depending on whether you have actual hardware to inteface with ot if you are using a device driver to present some 'pretend' device). the scripts need a little updating. but they will do 90% of what you need (You need to add code to register the interrupt vector in the first and remove it from the config line it generates. On Sun, 20 Dec 1998, Jeroen Ruigrok/Asmodai wrote: > [cc:-ed to hackers, removed from doc] > > On 17-Dec-98 Bill Loraine wrote: > > In the Tutorial "Writing device drivers for FreeBSD" on the Standard > > Model steps required for adding a driver, step 2 Make room in conf.c - > > Which the tutorial says is located in "/usr/src/sys/i386/i386/conf.c" on > > my operating system files(my hard drive with FreeBSD installed) I don't > > have a conf.c file at all much less in that location. > > I think conf.c needs to be renamed to autoconf.c. Then again, I might be wrong. > Someone care to update/verify my assumption? > > --- > Jeroen Ruigrok van der Werven Life is the only Pain > asmodai(at)wxs.nl we endeavour... > Network/Security Specialist > BSD & picoBSD: The Power to Serve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 14:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28996 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 14:29:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28991 for ; Sun, 20 Dec 1998 14:28:58 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id WAA27573; Sun, 20 Dec 1998 22:28:20 GMT Date: Sun, 20 Dec 1998 22:28:20 +0000 (GMT) From: Karl Pielorz To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: question about re-entrancy. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, Alfred Perlstein wrote: > > I'm a bit confused. I've been watching the discussions going on about > SMP. The issue of kernel re-entrancy has been brought up many times. > > So here's the question: > > I thought the kernel was re-entrant, when a process makes a syscall it's > thread of execution enters the kernel where its arguments are validated > and careful checks are done to ensure security then the syscall is done. Hmmm... AFAIK the FreeBSD kernel at the moment is like the Linux one certainly used to be (at last week ;-) - i.e. under SMP the kernel has a big lock around it - so that only 1 CPU can actively be in the kernel at a time... I beleive it's also the goal to make the granularity on this 'big lock' ever finer as more code get's developed... > Or are the spl calls simply there to diable interupts? but that brings me > back to the question about "well how do nfsd and nfsiod do it?" Hmmm... At the risk of being totally wrong - I thought that's all they did?... > Mike, Terry, Matt, John? Uhgh, yes - good idea, I'll leave it for someone who knows what their talking about to give the 'right' answer :-) - Some of the details for the current SMP implementaion were hanging around on www.freebsd.org a while ago... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 15:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04998 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 15:28:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04993 for ; Sun, 20 Dec 1998 15:28:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA06878; Sun, 20 Dec 1998 15:23:44 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdxu6876; Sun Dec 20 23:23:33 1998 Date: Sun, 20 Dec 1998 15:23:31 -0800 (PST) From: Julian Elischer To: zhihuizhang cc: hackers Subject: Re: questions/problems with vm_fault() in Stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG very interesting.. there is a lack of people who understand the VM system very well at this time so it may take a while for people to get back to you.. but.. I'm sure I'm not the only person lokking at your suggestions... (you are talking about -current, right?) julian On Sat, 19 Dec 1998, zhihuizhang wrote: > > Hi, > > I have some questions about the routine vm_fault() in the file vm_fault.c: > > (1) The condition (!change_wiring || wired) is always TRUE! Three possible > values of change_wiring are FALSE (0), VM_FAULT_CHANGE_WIRING (1), and > VM_FAULT_USER_WIRE (2). When its value is VM_FAULT_CHANGE_WIRING or > VM_FAULT_USER_WIRE, the wired count of the map entry has already been > incremented (see vm_map_user_pageable() and vm_map_pageable()), so > vm_map_lookup() will set wired as non-zero. If the argment's value is > FALSE, the condition is trivially true. > > (2) Following the label readrest: in the source code, there are some codes > trying to handle read ahead for sequential objects. However, the following > statement is wrong: > > for (tmppindex = first_index - 1; tmppindex >=first_pindex; -- tmppindex) > > We should probably use firstpindex instead of first_pindex in the comparison > (pay attention to the underscore here). However, the for loop will not loop > forever, because vm_page_lookup() called within the loop will return NULL > anyway. > > (3) If the pager fails to bring in a page for the very first object in the > shadow chain, the page will contain invalid content. If the pager fails to > bring in a page for other objects in the shadow chain, the page is freed > and invalid. Yet, we still reference to that page (m) later. This means > that after the page fault, we could get a page with invalid contents. > There is a XXX near the related comment in the source code. > > (4) The comment in the source code says that the pager can move a page, so > we must relookup the page by calling vm_page_lookup(). How could this be > the case? Why move the page? > > (5) The comment in the source code says that we do not COW read-only region > on a user wire. "If we do not make this restriction, the bookkeeping would > be nearly impossible." Can anyone explain this for me? > > (6) The comment in the source code says map entries may be pageable. I really > doubt this because vm_map_entry_create() always allocates wired down memory > for new map entries and enter them into pmap immediately. > > (7) The comment in the source code says pmap_enter() may cause other faults. > I can not see any reason for this to happen. > > I am just wondering how this important routine in VM system can have these > imperfect things (except (4) through (7)). I hope I am wrong. Please help > me out with understanding of these points. > > Any help is appreciated. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 15:48:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07477 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 15:48:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07472 for ; Sun, 20 Dec 1998 15:48:13 -0800 (PST) (envelope-from benedict@echonyc.com) Received: from localhost by echonyc.com (8.9.1/8.9.1) with ESMTP id SAA06894; Sun, 20 Dec 1998 18:48:11 -0500 (EST) Date: Sun, 20 Dec 1998 18:48:11 -0500 (EST) From: Snob Art Genre Reply-To: ben@rosengart.com To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: question about re-entrancy. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, Alfred Perlstein wrote: > Or.... what i'm now thinking is that once a process enters the kernel it > must run until it exits the system call. I have a problem with this > though, processes such as nfsiod/nfsd enter the kernel through a syscall > and never exit (according to design and implementation) how then are other > processes allowed into the kernel? As I understand it, more than one process can be in the kernel as long as all but one are asleep. That's why the kernel stack is per-process instead of per-system. I'm not sure about your splfoo() question. I suspect that kernel code is not supposed to sleep while interrupts are blocked. Chuck Youse told me that interrupts on the i386 use a mask instead of a level, so it may be that a process can sleep in the kernel with an interrupt blocked as long as no one else will be needing that particular interrupt. But this is pure speculation. Ben "You have your mind on computers, it seems." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 15:48:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07495 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 15:48:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07487 for ; Sun, 20 Dec 1998 15:48:19 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA07216; Sun, 20 Dec 1998 15:42:05 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdgC7201; Sun Dec 20 23:42:03 1998 Date: Sun, 20 Dec 1998 15:41:59 -0800 (PST) From: Julian Elischer To: zhihuizhang cc: hackers Subject: Re: questions/problems with vm_fault() in Stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you commenting the source as you go? Are yu writing a document on these things? you seem to be going through the entire kernel :-) If so. can we get a copy :-) julian On Sat, 19 Dec 1998, zhihuizhang wrote: > > Hi, > > I have some questions about the routine vm_fault() in the file vm_fault.c: > > (1) The condition (!change_wiring || wired) is always TRUE! Three possible > values of change_wiring are FALSE (0), VM_FAULT_CHANGE_WIRING (1), and > VM_FAULT_USER_WIRE (2). When its value is VM_FAULT_CHANGE_WIRING or > VM_FAULT_USER_WIRE, the wired count of the map entry has already been > incremented (see vm_map_user_pageable() and vm_map_pageable()), so > vm_map_lookup() will set wired as non-zero. If the argment's value is > FALSE, the condition is trivially true. > > (2) Following the label readrest: in the source code, there are some codes > trying to handle read ahead for sequential objects. However, the following > statement is wrong: > > for (tmppindex = first_index - 1; tmppindex >=first_pindex; -- tmppindex) > > We should probably use firstpindex instead of first_pindex in the comparison > (pay attention to the underscore here). However, the for loop will not loop > forever, because vm_page_lookup() called within the loop will return NULL > anyway. > > (3) If the pager fails to bring in a page for the very first object in the > shadow chain, the page will contain invalid content. If the pager fails to > bring in a page for other objects in the shadow chain, the page is freed > and invalid. Yet, we still reference to that page (m) later. This means > that after the page fault, we could get a page with invalid contents. > There is a XXX near the related comment in the source code. > > (4) The comment in the source code says that the pager can move a page, so > we must relookup the page by calling vm_page_lookup(). How could this be > the case? Why move the page? > > (5) The comment in the source code says that we do not COW read-only region > on a user wire. "If we do not make this restriction, the bookkeeping would > be nearly impossible." Can anyone explain this for me? > > (6) The comment in the source code says map entries may be pageable. I really > doubt this because vm_map_entry_create() always allocates wired down memory > for new map entries and enter them into pmap immediately. > > (7) The comment in the source code says pmap_enter() may cause other faults. > I can not see any reason for this to happen. > > I am just wondering how this important routine in VM system can have these > imperfect things (except (4) through (7)). I hope I am wrong. Please help > me out with understanding of these points. > > Any help is appreciated. > > -------------------------------------------------- > | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | > | Dept. of Computer Science, SUNY at Binghamton | > -------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 16:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10602 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 16:06:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fan.net.au (fan.net.au [203.20.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10597 for ; Sun, 20 Dec 1998 16:06:03 -0800 (PST) (envelope-from q@fan.net.au) Received: from gromit.fan.net.au (gromit.fan.net.au [203.23.133.34]) by fan.net.au (8.9.1/8.9.1) with SMTP id KAA11807; Mon, 21 Dec 1998 10:05:54 +1000 (EST) Date: Mon, 21 Dec 1998 10:05:53 +1000 (EST) From: Q To: Peter Hawkins cc: freebsd-hackers@FreeBSD.ORG, custserv2@corel.ca Subject: Re: Howto: wordperfect 8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, Peter Hawkins wrote: > > Unfortunately it does not install as documented but you can do it anyway as > follows: Yes it does... if you follow the instructions exactly. It should be noted that the installation instructions, specifically those at download.com are case sensitive. :) If you have a peek inside the Runme script it becomes evident what is happening. > 4. the distribution is *not* gzcompressed despite the extensions and the > documentation. Just use tar xvf to extract the kit. (if you get it as > seven separate parts, each is a separate tar file and untar them all > separately: > > foreach i (0 1 2 3 4 5 6) > tar xvf GUI0${i}.GZ > done They are compressed, netscape probably gunzipped it/them for you. The problem you do have however is the filenames must be in LOWER CASE!!!. You can correctly do the installation by doing something along these lines (assuming the files are still gzipped): gunzip GUI* foreach a (GUI*) tar -xvf $a mv $a `echo $a | awk '{ printf(tolower($0)) }'` end ./Runme > 5. The Runme installer fails so to install do the following in the directory > from which you did step 4 above: [snip] The Runme script will run fine with the tar files correctly named. > > 6. (a) Don't attempt to install non-us dictionaries or thesauruses - if you > can work out how let me know! They do not seem to be there for me. If you correctly run the installation script you will only be given the option of US dictionaries. > (b) ignore the warnings about files not being found There should be only one message that is displayed relating to trailing text in the OS version number (or at least there was on my 3.0 system). > (c) ignore the lack of printer drivers in the menu and continue without > installing a printer - it seems to install them all anyway (at least > it did for me) A correctly run installation will allow you to select a printer and bind it to a print spool. I think perhaps you should try your installation again.. maybe this time you will have more luck. Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan - q@fan.net.au __ __/ / / __/ / / Systems Administrator / __ / _/ / / Fast Access Network __/ __/ __/ ____/ / - / Gold Coast, QLD, Australia _______ / Ph: +61 7 5574 1050 \_\ SAGE-AU Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 17:55:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19679 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 17:55:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from enya.clari.net.au (enya.clari.net.au [203.8.14.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19673 for ; Sun, 20 Dec 1998 17:55:29 -0800 (PST) (envelope-from peter@clari.net.au) Received: from localhost (peter@localhost) by enya.clari.net.au (8.8.8/8.8.7) with SMTP id MAA24310; Mon, 21 Dec 1998 12:31:45 +1100 (EST) (envelope-from peter@clari.net.au) X-Authentication-Warning: enya.clari.net.au: peter owned process doing -bs Date: Mon, 21 Dec 1998 12:31:45 +1100 (EST) From: Peter Hawkins To: The Hermit Hacker cc: freebsd-hackers@FreeBSD.ORG, custserv2@corel.ca Subject: Re: Howto: wordperfect 8 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Just curious, but what failed for you? I just downloaded it, ran the >Runme file, and have it up and running on my screen...in fact, just laoded >a Word97 file up, which was why I downloaded it... It appears there is a (big) diff between the multipart and the single archive versions. Looks like the single file version is the way to go. All the problems I described are irrelevant in the single-file case. Peter Clarinet Internet Solutions Peter Hawkins 381 Swan St Richmond, Vic, Australia Ph: +61-3-9421 2006 Fax: +61-3-9421 2007 http://www.clari.net.au Peter@clari.net.au FreeBSD Project: thepish@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 18:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22822 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 18:36:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22816 for ; Sun, 20 Dec 1998 18:36:28 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id NAA22827 for ; Mon, 21 Dec 1998 13:06:22 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 21 Dec 1998 13:08:55 +1030 (CST) From: "Daniel O'Connor" To: freebsd-hackers@FreeBSD.ORG Subject: PCI IRQ mappings Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm wondering if its possible to reassign IRQ's for PCI cards. The BIOS does the origional mapping (I think) but sometimes this is broken, so the only way to change IRQ's is to shuffle cards in the machine. Is there a better way? :) I had a look at the 440BX datasheet but I couldn't find anything pertinent. Is it possible? Windows seems to let you do it, and I'm curious how. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 19:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26208 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 19:19:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pobox.com (honoghr-3.mdm.mkt.execpc.com [169.207.82.131]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA25978 for ; Sun, 20 Dec 1998 19:16:39 -0800 (PST) (envelope-from hamilton@pobox.com) Message-Id: <199812210316.TAA25978@hub.freebsd.org> Received: (qmail 22734 invoked from network); 20 Dec 1998 21:15:16 -0600 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 20 Dec 1998 21:15:16 -0600 To: "Daniel O'Connor" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Mon, 21 Dec 1998 13:08:55 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:15:16 -0600 From: Jon Hamilton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Daniel O'Connor" wrote : } Hi, } I'm wondering if its possible to reassign IRQ's for PCI cards. The BIOS does } the } origional mapping (I think) but sometimes this is broken, so the only way to } change IRQ's } is to shuffle cards in the machine. Is there a better way? :) } } I had a look at the 440BX datasheet but I couldn't find anything pertinent. I } s it } possible? Windows seems to let you do it, and I'm curious how. I can't provide hard technical details, but I do know that while motherboard shopping recently, I came across several BIOSes which have a setting which tells the BIOS that the OS may reassign the IRQs out from under it (or maybe it controls a bit in the chipset which _allows_ the OS to do so, I dunno). Based upon this, I assume it's feasable for the OS to actually do this kind of thing. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 19:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26867 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 19:30:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from qix (ppp005.infranet.fr [195.68.70.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26861 for ; Sun, 20 Dec 1998 19:30:26 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.1/8.8.7) id EAA47108; Mon, 21 Dec 1998 04:31:59 +0100 (MET) Date: Mon, 21 Dec 1998 04:31:59 +0100 (MET) Message-Id: <199812210331.EAA47108@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: doconnor@gsoft.com.au CC: freebsd-hackers@FreeBSD.ORG In-reply-to: Subject: Re: PCI IRQ mappings X-Mailer: Emacs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Daniel O'Connor writes: > Hi, > I'm wondering if its possible to reassign IRQ's for PCI cards. The > BIOS does the > origional mapping (I think) but sometimes this is broken, so the > only way to change IRQ's > is to shuffle cards in the machine. Is there a better way? :) I think you just have to change the interrupt line register in the configuration registers, and maybe the route control register (offset 0x60) Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 20:00:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29630 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 20:00:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29625 for ; Sun, 20 Dec 1998 20:00:35 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id UAA25976; Sun, 20 Dec 1998 20:59:40 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Sun, 20 Dec 1998 20:59:40 -0700 (MST) From: Doug Russell To: Mike Smith cc: Peter Hawkins , freebsd-hackers@FreeBSD.ORG, custserv2@corel.ca Subject: Re: Howto: wordperfect 8 (off topic) In-Reply-To: <199812200157.RAA04126@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Dec 1998, Mike Smith wrote: > Not quite as good, but perhaps more reliable. It does a barely > tolerable job of reading Word documents. Depends on what's in the files you are trying to read, of course... It certainly does a better job of reading most Word files I've tried than Word does reading most Wordperfect files I've tried. YMMV, of course! Note to Corel: Thank you thank you thank you thank you thank you thank you! :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 20:03:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29791 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 20:03:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29777; Sun, 20 Dec 1998 20:03:34 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA23494; Mon, 21 Dec 1998 14:33:29 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812210331.EAA47108@qix> Date: Mon, 21 Dec 1998 14:36:04 +1030 (CST) From: "Daniel O'Connor" To: Jean-Marc Zucconi Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Jean-Marc Zucconi wrote: > > is to shuffle cards in the machine. Is there a better way? :) > I think you just have to change the interrupt line register in the > configuration registers, and maybe the route control register (offset > 0x60) Hmmm.. I looked at offset 60 and its the 'DRAM Row Boundary Registers' in device 0, and non existant in device 1. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 20:31:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01729 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 20:31:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01722 for ; Sun, 20 Dec 1998 20:31:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA48958; Sun, 20 Dec 1998 20:28:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210428.UAA48958@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Hawkins cc: The Hermit Hacker , freebsd-hackers@FreeBSD.ORG Subject: Re: Howto: wordperfect 8 In-reply-to: Your message of "Mon, 21 Dec 1998 12:31:45 +1100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 20:28:45 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Just curious, but what failed for you? I just downloaded it, ran the > >Runme file, and have it up and running on my screen...in fact, just laoded > >a Word97 file up, which was why I downloaded it... > > It appears there is a (big) diff between the multipart and the single > archive versions. Looks like the single file version is the way to go. All > the problems I described are irrelevant in the single-file case. ... and just to point out that the port uses (requires) the single-file version. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05128 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:14:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05106 for ; Sun, 20 Dec 1998 21:13:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA49211; Sun, 20 Dec 1998 21:11:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210511.VAA49211@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Mon, 21 Dec 1998 13:08:55 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:11:32 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm wondering if its possible to reassign IRQ's for PCI cards. The > BIOS does the origional mapping (I think) but sometimes this is broken, > so the only way to change IRQ's is to shuffle cards in the machine. Is > there a better way? :) Can you define "broken" in a useful fashion? > I had a look at the 440BX datasheet but I couldn't find anything > pertinent. Is it possible? Windows seems to let you do it, and I'm > curious how. Windows 9[58] take it upon themselves to manage resource allocation, and they do this using int 1a functions 0xb10e and 0xb10f (get IRQ routing information, set PCI IRQ). You also have to update the config register on the PCI device. This is the only way to do this correctly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:18:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05509 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:18:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05504 for ; Sun, 20 Dec 1998 21:18:20 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA24039; Mon, 21 Dec 1998 15:48:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812210511.VAA49211@dingo.cdrom.com> Date: Mon, 21 Dec 1998 15:50:51 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Mike Smith wrote: > > so the only way to change IRQ's is to shuffle cards in the machine. Is > > there a better way? :) > Can you define "broken" in a useful fashion? Doesn't work/crashes machine. The network cards don't appear to like sharing IRQ's :( (Although its a little hard to say what causes it) > Windows 9[58] take it upon themselves to manage resource allocation, > and they do this using int 1a functions 0xb10e and 0xb10f (get IRQ > routing information, set PCI IRQ). You also have to update the config > register on the PCI device. I see.. I thought it was device independat (ie based on the PCI chipset) This is a VM86 thing then? :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:23:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05983 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:23:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05978 for ; Sun, 20 Dec 1998 21:23:11 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: (from vanmaren@localhost) by fast.cs.utah.edu (8.9.1/8.9.1) id WAA02144 for freebsd-hackers@FreeBSD.ORG; Sun, 20 Dec 1998 22:23:10 -0700 (MST) Date: Sun, 20 Dec 1998 22:23:10 -0700 (MST) From: Kevin Van Maren Message-Id: <199812210523.WAA02144@fast.cs.utah.edu> To: freebsd-hackers@FreeBSD.ORG Subject: RAID support in FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone looking at supporting RAID 5 in FreeBSD (w/o a hardware RAID controller)? The ccd driver's RAID 0 doesn't provide all the desired functionality. The reason I bring this up now is that I was poking around the NetBSD web pages tonight and I noticed that they've had it in their -CURRENT for over a month, using the CMU RAIDframe code. (Yes, it's only a month.) http://www.cs.usask.ca/staff/oster/raid.html How hard would it be for someone to port it to FreeBSD? (It is integrated at the vnode layer; I'm not familiar with the differences we have there, but we do use a similar vnode driver and ccd driver). Is someone already working on this? Or maybe someone will volunteer now? Kevin Van Maren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06016 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:23:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06011 for ; Sun, 20 Dec 1998 21:23:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA49288; Sun, 20 Dec 1998 21:21:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210521.VAA49288@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Mon, 21 Dec 1998 15:50:51 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:21:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 21-Dec-98 Mike Smith wrote: > > > so the only way to change IRQ's is to shuffle cards in the machine. Is > > > there a better way? :) > > Can you define "broken" in a useful fashion? > Doesn't work/crashes machine. The network cards don't appear to like sharing IRQ's :( > (Although its a little hard to say what causes it) Bleagh. Our IRQ sharing is supposed to work; is this a hardware-level problem (does it work under Windows)? > > Windows 9[58] take it upon themselves to manage resource allocation, > > and they do this using int 1a functions 0xb10e and 0xb10f (get IRQ > > routing information, set PCI IRQ). You also have to update the config > > register on the PCI device. > I see.. I thought it was device independat (ie based on the PCI chipset) That's device dependant, and yes, it is, which is why you have to use the BIOS (or have drivers for every motherboard chipset in the OS, which would suck). (I should have pointed out that there are different interrupt vectors for PCI 2.1-compliant functions.) > This is a VM86 thing then? :) That's the easiest way to do it. I get the impression that you should be able to call the PCI BIOS from 32-bit mode as well, but I don't have the documentation to hand. It sounds to me like you have a BIOS misconfiguration or bug there; if the crash happens under "other" operating systems (eg. NT, which is more like us in that I think it trusts the BIOS to get it right) then you might be able to get an update out of the board vendor. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:31:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06899 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:31:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06892 for ; Sun, 20 Dec 1998 21:31:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA49341; Sun, 20 Dec 1998 21:29:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210529.VAA49341@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Van Maren cc: freebsd-hackers@FreeBSD.ORG Subject: Re: RAID support in FreeBSD In-reply-to: Your message of "Sun, 20 Dec 1998 22:23:10 MST." <199812210523.WAA02144@fast.cs.utah.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:29:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is anyone looking at supporting RAID 5 in FreeBSD (w/o a > hardware RAID controller)? The ccd driver's RAID 0 doesn't > provide all the desired functionality. Greg Lehey's vinum code has support for a Raid5 module, however the module is currently only available from the sponsor of the work. > The reason I bring this up now is that I was poking around > the NetBSD web pages tonight and I noticed that they've > had it in their -CURRENT for over a month, using the CMU > RAIDframe code. (Yes, it's only a month.) Yup. There was some discussion of this a little while back. > http://www.cs.usask.ca/staff/oster/raid.html > > How hard would it be for someone to port it to FreeBSD? (It > is integrated at the vnode layer; I'm not familiar with the > differences we have there, but we do use a similar vnode > driver and ccd driver). Not terribly. It would be nice, if when they ported it, they didn't butcher it quite like the NetBSD integrator did. I took the NetBSD code and the original to see what the changes they made were; there's far too much noise to be able to work easily with the diffs. Terry also posted some diffs that he produced a while back to make RaidFrame build under FreeBSD. > Is someone already working on this? Or maybe someone will > volunteer now? I was sort of hoping that this might have been you volunteering... We can provide all the help you might need (not a lot I suspect). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06989 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:31:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06984 for ; Sun, 20 Dec 1998 21:31:46 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA24122; Mon, 21 Dec 1998 16:01:42 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812210521.VAA49288@dingo.cdrom.com> Date: Mon, 21 Dec 1998 16:04:18 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Mike Smith wrote: > > > Can you define "broken" in a useful fashion? > > Doesn't work/crashes machine. The network cards don't appear to like sharing IRQ's :( > > (Although its a little hard to say what causes it) > Bleagh. Our IRQ sharing is supposed to work; is this a hardware-level > problem (does it work under Windows)? I know and no :( It works but you have to be careful around it :-/ (ie that it gets its own IRQ) > > I see.. I thought it was device independat (ie based on the PCI chipset) > That's device dependant, and yes, it is, which is why you have to use > the BIOS (or have drivers for every motherboard chipset in the OS, > which would suck). (I should have pointed out that there are different > interrupt vectors for PCI 2.1-compliant functions.) Doh! :( Thats sucks :-/ > It sounds to me like you have a BIOS misconfiguration or bug there; if > the crash happens under "other" operating systems (eg. NT, which is > more like us in that I think it trusts the BIOS to get it right) then > you might be able to get an update out of the board vendor. Hmm.. OK.. well, we don't have NT :) (thankfully ;) I don't have a proper problem description, so I was just curious if it was possible :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:35:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07208 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:35:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07202 for ; Sun, 20 Dec 1998 21:35:34 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA26924; Mon, 21 Dec 1998 16:05:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA68117; Mon, 21 Dec 1998 16:05:22 +1030 (CST) Message-ID: <19981221160521.A24125@freebie.lemis.com> Date: Mon, 21 Dec 1998 16:05:21 +1030 From: Greg Lehey To: Mike Smith , Kevin Van Maren Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: RAID support in FreeBSD References: <199812210523.WAA02144@fast.cs.utah.edu> <199812210529.VAA49341@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812210529.VAA49341@dingo.cdrom.com>; from Mike Smith on Sun, Dec 20, 1998 at 09:29:03PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 20 December 1998 at 21:29:03 -0800, Mike Smith wrote: >> Is anyone looking at supporting RAID 5 in FreeBSD (w/o a >> hardware RAID controller)? The ccd driver's RAID 0 doesn't >> provide all the desired functionality. > > Greg Lehey's vinum code has support for a Raid5 module, however the > module is currently only available from the sponsor of the work. This will, however, change in mid-2000. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:37:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07324 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:37:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07319 for ; Sun, 20 Dec 1998 21:37:04 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA06013; Sun, 20 Dec 1998 21:36:09 -0800 (PST) Message-Id: <199812210536.VAA06013@lestat.nas.nasa.gov> To: Mike Smith Cc: Kevin Van Maren , freebsd-hackers@FreeBSD.ORG Subject: Re: RAID support in FreeBSD Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 20 Dec 1998 21:36:09 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998 21:29:03 -0800 Mike Smith wrote: > Not terribly. It would be nice, if when they ported it, they didn't > butcher it quite like the NetBSD integrator did. I took the NetBSD > code and the original to see what the changes they made were; there's > far too much noise to be able to work easily with the diffs. Greg Oster actually fixed a significant number of bugs, and the CMU people aren't planning on another release anyhow. I.e. NetBSD integrated the end-of-the-line. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07462 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:39:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles336.castles.com [208.214.167.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07455 for ; Sun, 20 Dec 1998 21:39:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA49409; Sun, 20 Dec 1998 21:36:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812210536.VAA49409@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jason Thorpe cc: Kevin Van Maren , freebsd-hackers@FreeBSD.ORG Subject: Re: RAID support in FreeBSD In-reply-to: Your message of "Sun, 20 Dec 1998 21:36:09 PST." <199812210536.VAA06013@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 21:36:58 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 20 Dec 1998 21:29:03 -0800 > Mike Smith wrote: > > > Not terribly. It would be nice, if when they ported it, they didn't > > butcher it quite like the NetBSD integrator did. I took the NetBSD > > code and the original to see what the changes they made were; there's > > far too much noise to be able to work easily with the diffs. > > Greg Oster actually fixed a significant number of bugs, and the CMU people > aren't planning on another release anyhow. I.e. NetBSD integrated the > end-of-the-line. Ah; that's a significant (and perhaps slightly saddening) datapoint. Do you (NetBSD) have plans to continue its development? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 21:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08379 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 21:46:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08374 for ; Sun, 20 Dec 1998 21:46:50 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id VAA06159; Sun, 20 Dec 1998 21:46:41 -0800 (PST) Message-Id: <199812210546.VAA06159@lestat.nas.nasa.gov> To: Mike Smith Cc: Kevin Van Maren , freebsd-hackers@FreeBSD.ORG Subject: Re: RAID support in FreeBSD Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 20 Dec 1998 21:46:40 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998 21:36:58 -0800 Mike Smith wrote: > Ah; that's a significant (and perhaps slightly saddening) datapoint. > > Do you (NetBSD) have plans to continue its development? Yes, we plan on continuing to improve it. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 22:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09460 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 22:01:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09455 for ; Sun, 20 Dec 1998 22:00:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA27009; Mon, 21 Dec 1998 16:30:44 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA68193; Mon, 21 Dec 1998 16:30:43 +1030 (CST) Message-ID: <19981221163041.C24125@freebie.lemis.com> Date: Mon, 21 Dec 1998 16:30:41 +1030 From: Greg Lehey To: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: question about re-entrancy. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alfred Perlstein on Sun, Dec 20, 1998 at 04:36:51PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 20 December 1998 at 16:36:51 -0500, Alfred Perlstein wrote: > > I'm a bit confused. I've been watching the discussions going on about > SMP. The issue of kernel re-entrancy has been brought up many times. > > So here's the question: > > I thought the kernel was re-entrant, when a process makes a syscall it's > thread of execution enters the kernel where its arguments are validated > and careful checks are done to ensure security then the syscall is done. Well, those are two different things. AFAIK the kernel is *not* reentrant, in the sense that only one process can be executing in the kernel at any one point. Certainly the classical UNIX kernel is not, anyway, but it makes sense to allow concurrent execution on SMP machines. I believe that at the moment, though, the kernel does not allow this. On the other hand, of course the kernel checks parameters for validity and protects itself. > If during the system call the process is put to sleep or rescheduled, > another process may enter the kernel. Right. That's the only way, but then the process isn't executing. > As long as the splxxx() calls do not interfere with each other you > have 2 processes excuting in the kernel at that point. (more can > enter as well) You seem to be confused here. splxxx() is an interrupt-level mechanism, and it's not needed for resources which are accessed by processes (i.e. non-interrupt environments) alone. > Or.... what i'm now thinking is that once a process enters the kernel it > must run until it exits the system call. Or it gets suspended. > I have a problem with this though, processes such as nfsiod/nfsd > enter the kernel through a syscall and never exit (according to > design and implementation) how then are other processes allowed into > the kernel? The normal state of all daemons is sleeping. > Can anyone explain this a bit better? > > I understand deadlock can occur if something like this happens: > > process 1 process 2 > syscall() > splbio() > rescheduled -----> This can't happen, not inside splbio(). How can it get rescheduled? > syscall() > splimp() > <----- rescheduled > splimp()? -no,reschedule-> > <-no,reschedule- splbio()? > splimp()? -no,reschedule-> > splbio()? > > some sorta flipflop deadlock happens at this point as nested locks are > held and won't be released as two in kernel processes never relinquish > resources. > > Or are the spl calls simply there to diable interupts? Yes, that's exactly what they do. > but that brings me back to the question about "well how do nfsd and > nfsiod do it?" They don't sleep inside spl()s. > Perhaps once an spl is initiated the process can not block? Right. > the more I thought about this, the more my head ached :) You'd probably find ``The Design and Implementation'' a useful read. It'll give you a better understanding of the issues. But it seems to me that you're attributing more importance to the splxxx() functions than they deserve. To recap: you don't need to synchronize between processes, because the kernel (currently) guarantees that only one process will be doing something in the kernel at any one time. On the other hand, non-process activity (interrupts, bottom halves of device drivers) can execute at just about any time. You resolve conflicts between interrupt handlers and possibly the process currently running by locking out specific interrupts in critical sections of code. That's what the splxxx() routines do. In the PDP-11, they set the processor priority level (which is why you'll occasionally see the System Visms spl4(), spl5(), spl6() and spl7()). On the i386, they mask specific interrupts relating to the function (for example, splbio() masks disk controller/host adaptor interrupts). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 22:42:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12830 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 22:42:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12824; Sun, 20 Dec 1998 22:42:39 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA51848; Sun, 20 Dec 1998 22:42:02 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812210642.WAA51848@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jean-Marc Zucconi cc: doconnor@gsoft.com.au, freebsd-hackers@FreeBSD.ORG Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Mon, 21 Dec 1998 04:31:59 +0100." <199812210331.EAA47108@qix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 22:42:02 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, it is possible. Take a look at my bktr driver or at the matrox meteor driver;additionally, some folks in the -multimedia group were reassigning the IRQ of their video capture boards all the time. Amancio > >>>>> Daniel O'Connor writes: > > > Hi, > > I'm wondering if its possible to reassign IRQ's for PCI cards. The > > BIOS does the > > origional mapping (I think) but sometimes this is broken, so the > > only way to change IRQ's > > is to shuffle cards in the machine. Is there a better way? :) > > I think you just have to change the interrupt line register in the > configuration registers, and maybe the route control register (offset > 0x60) > > Jean-Marc > > -- > Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 20 23:13:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15614 for freebsd-hackers-outgoing; Sun, 20 Dec 1998 23:13:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15607 for ; Sun, 20 Dec 1998 23:13:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA35942; Sun, 20 Dec 1998 23:13:26 -0800 (PST) (envelope-from dillon) Date: Sun, 20 Dec 1998 23:13:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812210713.XAA35942@apollo.backplane.com> To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: question about re-entrancy. References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm a bit confused. I've been watching the discussions going on about :SMP. The issue of kernel re-entrancy has been brought up many times. : :So here's the question: : :I thought the kernel was re-entrant, when a process makes a syscall it's :thread of execution enters the kernel where its arguments are validated :and careful checks are done to ensure security then the syscall is done. : :If during the system call the process is put to sleep or rescheduled, :another process may enter the kernel. As long as the splxxx() calls do :not interfere with each other you have 2 processes excuting in the kernel :at that point. (more can enter as well) : :Or.... what i'm now thinking is that once a process enters the kernel it :must run until it exits the system call. I have a problem with this :... This is how it works: There is a big lock around the *execution* of supervisor code. Once a process running in supervisor mode goes to sleep, it is no longer executing and the lock is released. The lock is regained when the supervisor-mode-context process is woken up and gets cpu again. So, for example, if you have a shell that is blocked in a read() system call, it is not actually executing anything even though it is in a supervisor context. The spl*() calls work differently. For one thing, the process making the calls already owns the overall SMP lock so, really, the spl*() stuff is independant. SMP motherboards have an interrupt-forwarding capability allowing interrupts to be assigned to specific cpu's. FreeBSD just assigns all of them to one cpu or the other depending on which one currently owns the SMP lock. Thus when an interrupt does occur, it always occurs on the cpu that is *already* running in supervisor mode. spl*() calls do not disable specific interrupts. Instead they add to a 'bitmask' representing disabled interrupt sources. Various spl*() calls will disable different (but often overlapping) masks. In fact, they do not disable anything at all... they simply set a global variable. When an interrupt occurs the global is checked and if the interrupt has been marked as being masked, it sets a bit in another global saying that it is pending and returns immediately without executing the interrupt routine designated for that interrupt. When the spl is 'restored', a check is made between the global disable mask and the global pending mask and any pending interrupts that get unmasked are executed then. The spl mask is a per-process element. When a process which has masked interrupts goes to sleep, the mask is saved along with the process and interrupts are effectively enabled again (when a process is switched in, the mask is 'restored' based on whatever it was when the process went to sleep). This is, in fact, a big problem with the current kernel because sometimes a piece of code will disable interrupts and then unexpectedly sleep synchronously. Even though the interrupts are still disabled on resumption, the code might have assumed atomic operation when in fact atomic operation wound up getting broken by the sleep. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) :though, processes such as nfsiod/nfsd enter the kernel through a syscall :and never exit (according to design and implementation) how then are other :processes allowed into the kernel? : :Can anyone explain this a bit better? : :I understand deadlock can occur if something like this happens: : :process 1 process 2 :syscall() :splbio() :rescheduled -----> : syscall() : splimp() : <----- rescheduled :splimp()? -no,reschedule-> : <-no,reschedule- splbio()? :splimp()? -no,reschedule-> : splbio()? : :some sorta flipflop deadlock happens at this point as nested locks are :held and won't be released as two in kernel processes never relinquish :resources. : :Or are the spl calls simply there to diable interupts? but that brings me :back to the question about "well how do nfsd and nfsiod do it?" : :Perhaps once an spl is initiated the process can not block? : :the more I thought about this, the more my head ached :) : :Mike, Terry, Matt, John? : :thanks, :Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com :-- There are operating systems, and then there's FreeBSD. :-- http://www.freebsd.org/ 3.0-current : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 01:45:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29382 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 01:45:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29372 for ; Mon, 21 Dec 1998 01:45:10 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id LAA02813; Mon, 21 Dec 1998 11:30:59 +0200 (SAST) Received: by citadel via recvmail id 2753; Mon Dec 21 11:30:28 1998 From: Graham Wheeler Message-Id: <199812210938.LAA17923@cdsec.com> Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. To: kaleb@ics.com (Kaleb Keithley) Date: Mon, 21 Dec 1998 11:38:00 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199812191330.IAA26067@sunoco> from "Kaleb Keithley" at Dec 19, 98 08:30:13 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > My 3.0-RELEASE system, up some 17 days, is now doing this when I telnet > (or ping, or anything else that uses inetd) to it. (I don't know how long > it's been like this, perhaps it explains why my outgoing email seem to > be being dropped on the floor. > > Do I remember correctly that there was some fix for this made shortly > before 3.0-RELEASE? Did the fix not make it into 3.0-RELEASE? Before > I go snag the LaG inetd sources, will that fix the problem? There is an open problem report, bin/8183, about this. I have just received mail saying that the fix I posted changes the signal mask for child processes and breaks Amanda; I haven't had a chance to look at this yet, and have not experienced any problems myself. You may want to try the patches and see how it goes. cheers Graham -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Internet/Intranet Network Specialists Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 02:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02327 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 02:11:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02322 for ; Mon, 21 Dec 1998 02:11:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id CAA42292; Mon, 21 Dec 1998 02:11:18 -0800 (PST) (envelope-from dillon) Date: Mon, 21 Dec 1998 02:11:18 -0800 (PST) From: Matthew Dillon Message-Id: <199812211011.CAA42292@apollo.backplane.com> To: Julian Elischer Cc: zhihuizhang , hackers Subject: Re: questions/problems with vm_fault() in Stable References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :very interesting.. :there is a lack of people who understand the VM system very well at this :time so it may take a while for people to get back to you.. but.. I'm sure :I'm not the only person lokking at your suggestions... : (you are talking about -current, right?) : :julian : :On Sat, 19 Dec 1998, zhihuizhang wrote: : :> Hi, :> :> I have some questions about the routine vm_fault() in the file vm_fault.c: :> :> (1) The condition (!change_wiring || wired) is always TRUE! Three possible :> values of change_wiring are FALSE (0), VM_FAULT_CHANGE_WIRING (1), and :> VM_FAULT_USER_WIRE (2). When its value is VM_FAULT_CHANGE_WIRING or :> VM_FAULT_USER_WIRE, the wired count of the map entry has already been :> incremented (see vm_map_user_pageable() and vm_map_pageable()), so :> vm_map_lookup() will set wired as non-zero. If the argment's value is :> FALSE, the condition is trivially true. What line and RCS rev are you looking at here? I don't see this anywhere in either -stable or -current in vm_fault.c :> (2) Following the label readrest: in the source code, there are some codes :> trying to handle read ahead for sequential objects. However, the following :> statement is wrong: :> :> for (tmppindex = first_index - 1; tmppindex >=first_pindex; -- tmppindex) :> We should probably use firstpindex instead of first_pindex in the comparison :> (pay attention to the underscore here). However, the for loop will not loop :> forever, because vm_page_lookup() called within the loop will return NULL :> anyway. This was fixed in -current. It does NOT appear to be fixed in -stable. Hmm. The entire read-ahead codeblock is disabled due to this error, but since I am not running a -stable system any more I can't just commit the change because it will bring in a whole block of code that's never been run before. Maybe one of the other guys can. It isn't in a critical code section for -stable.. that is, the bug only makes the code a little less efficient so I'm loath to actually make the change in -stable myself. Maybe if DG or Luoqi or someone similar reviews it for -stable. :> (3) If the pager fails to bring in a page for the very first object in the :> shadow chain, the page will contain invalid content. If the pager fails to :> bring in a page for other objects in the shadow chain, the page is freed :> and invalid. Yet, we still reference to that page (m) later. This means :> that after the page fault, we could get a page with invalid contents. :> There is a XXX near the related comment in the source code. What line? Line 483 of vm_fault.c (from -current) ?: /* * XXX - we cannot just fall out at this * point, m has been freed and is invalid! */ This ? Could you be a bit more specific about the problem, like give line numbers and such? The code does look somewhat odd but I don't see where m is reused. :> (4) The comment in the source code says that the pager can move a page, so :> we must relookup the page by calling vm_page_lookup(). How could this be :> the case? Why move the page? Line? and file version too... I don't think you are looking at a recent version of vm_fault.c :> (5) The comment in the source code says that we do not COW read-only region :> on a user wire. "If we do not make this restriction, the bookkeeping would :> be nearly impossible." Can anyone explain this for me? I think this pertains to the fact that a COW page is made read+write, and trying to do it and then leave a page read+only confuses other parts of the code. This isn't a bug or anything. :> (6) The comment in the source code says map entries may be pageable. I really :> doubt this because vm_map_entry_create() always allocates wired down memory :> for new map entries and enter them into pmap immediately. Most of the pmap system operates with throw-away pages and page table directories. If a piece of code sleeps anywhere, the pagemap may not still exist after it wakes up again. I think that is what this comment is refering to. :> (7) The comment in the source code says pmap_enter() may cause other faults. :> I can not see any reason for this to happen. pmap_enter() may have to allocate a page table page (see i386/i386/pmap.c). If the allocation fails, the process will block there until memory is available. -Matt :> I am just wondering how this important routine in VM system can have these :> imperfect things (except (4) through (7)). I hope I am wrong. Please help :> me out with understanding of these points. :> :> Any help is appreciated. :> :> -------------------------------------------------- :> | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | :> | Dept. of Computer Science, SUNY at Binghamton | :> -------------------------------------------------- :> :> :> To Unsubscribe: send mail to majordomo@FreeBSD.org :> with "unsubscribe freebsd-hackers" in the body of the message :> : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 02:25:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03815 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 02:25:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA03809 for ; Mon, 21 Dec 1998 02:25:10 -0800 (PST) (envelope-from marc@bowtie.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.8.8/8.8.8) with IAEhv.nl id LAA24261 for hackers@freebsd.org; Mon, 21 Dec 1998 11:25:04 +0100 (MET) (envelope-from marc@bowtie.nl) Received: from localhost (localhost [127.0.0.1]) by bowtie.nl (8.8.8/8.8.8) with ESMTP id LAA19441 for ; Mon, 21 Dec 1998 11:24:15 +0100 (CET) (envelope-from marc@bowtie.nl) Message-Id: <199812211024.LAA19441@bowtie.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: Anyone with DHCP experience Reply-to: marc@bowtie.nl Date: Mon, 21 Dec 1998 11:24:15 +0100 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm having some troubles getting DHCP to work with my 3c509b network card. I know this card is not among the best supported, but I'm forced to use this card by my cable network provider. I have used both wide-dhcp and isc-dhcp, but only succeeded so far with wide-dhcp. I have had some success, but now it seems to refuse to come back up. When I look at the packets floating by with tcpdump, it seems the client sends out the request (DHCPDISCOVER) correctly, but then gets a response back that contains a remark about an incorrect cksum. I'm not fluent at reading tcpdump output, but this is what it looks like. Now, does this ring a bell for someone? I stronly suspect the driver for the 3c509b, but I'm tied to it, or could I use another card, and sent the mac address of the 3c509b with the DHCP request? Isc-dhcp seems to have that capability, but sends out its broadcast addresses using 'ifconfig ep0 0.0.0.0 broadcast 255.255.255.255' and that results in a send error when I run it (the latest isc-dhcp from december 4) Oh, and to rule out any dhcp server configurations errors, Win95 comes up with no problems at all (assuming this means anything at all ;-)) Regards, 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 ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 03:55:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11764 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 03:55:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA11756 for ; Mon, 21 Dec 1998 03:55:18 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id LAFWTHMN; Mon, 21 Dec 98 11:55:13 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981221125508.0091cd10@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Mon, 21 Dec 1998 12:55:08 +0100 To: Casper , freebsd-hackers@FreeBSD.ORG From: Marius Bendiksen Subject: Re: Joliet file system? In-Reply-To: <367CA2FC.3F42F288@acc.am> References: <367C5118.4C32904B@freedomnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check out the PR database. A set of real patches exist there. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 04:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19915 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 04:58:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19910 for ; Mon, 21 Dec 1998 04:58:23 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zs4ui-000I4yC; Mon, 21 Dec 1998 07:58:20 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: kernel panic To: hackers@FreeBSD.ORG Date: Mon, 21 Dec 1998 07:58:20 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last week, x11amp seemed to work absolutely reliably with the OSS sound system. (x11amp -b 1024 on FreeBSD-current with creative AWE-64). I updated the system Sunday AM with cvsup and ever since, I get a kernel panic within 5 minutes of starting x11amp. First the sound stops, with x11amp happily executing, then in 3-4 seconds, panicsville. No core dump that I could ascertain. Any hints? Any recent changes affecting dma, virtual memory swapping, etc? Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 04:59:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20027 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 04:59:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19974 for ; Mon, 21 Dec 1998 04:58:51 -0800 (PST) (envelope-from wosch@cs.tu-berlin.de) Received: from caramba.cs.tu-berlin.de (wosch@caramba.cs.tu-berlin.de [130.149.17.12]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id NAA11221 for ; Mon, 21 Dec 1998 13:53:06 +0100 (MET) Received: (from wosch@localhost) by caramba.cs.tu-berlin.de (8.9.1/8.9.0) id NAA08802 for freebsd-hackers@freebsd.org; Mon, 21 Dec 1998 13:53:02 +0100 (MET) Message-ID: <19981221135300.A578@caramba.cs.tu-berlin.de> Date: Mon, 21 Dec 1998 13:53:00 +0100 From: Wolfram Schneider To: freebsd-hackers@FreeBSD.ORG Subject: [HTML index of current mail archive] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Forwarded message from Wolfram Schneider ----- Date: Sun, 20 Dec 1998 23:38:01 +0100 From: Wolfram Schneider To: doc@FreeBSD.ORG Subject: HTML index of current mail archive I setup a primitve HTML index of the current mail archive (*) The mails are sorted by date (physical order). The pages are updated every 10 minutes for all mailing list - this should be enough for mail junkies ;-) (*) all emails which are not yet indexed by the FreeBSD mailing list archive. See http://www.freebsd.org/~wosch/test/mail/ ----- End forwarded message ----- -- Wolfram Schneider http://freebsd.org/~w/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 06:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27924 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 06:17:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA27883 for ; Mon, 21 Dec 1998 06:17:16 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id JAA02877; Mon, 21 Dec 1998 09:16:18 -0500 Date: Mon, 21 Dec 1998 09:16:18 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: zhihuizhang cc: hackers Subject: Re: questions/problems with vm_fault() in Stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG are you looking to learn about VMs, or do you have a specific project. If you are really looking to learn about good VM systems check out netbsd. It has Chuck Cranor's new VM. ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 06:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28702 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 06:21:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wind.freenet.am ([194.151.101.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28683 for ; Mon, 21 Dec 1998 06:21:43 -0800 (PST) (envelope-from casper@acc.am) Received: from lemming.acc.am (acc.freenet.am [194.151.101.251]) by wind.freenet.am (8.9.1/8.9.1) with ESMTP id SAA01845 for ; Mon, 21 Dec 1998 18:20:57 +0400 (GMT) Received: from acc.am (nightmar.acc.am [192.168.100.108]) by lemming.acc.am (8.9.1a/8.9.1) with ESMTP id SAA11266 for ; Mon, 21 Dec 1998 18:24:19 +0400 (AMT) Message-ID: <367E588F.E20CE19F@acc.am> Date: Mon, 21 Dec 1998 18:17:51 +0400 From: Casper Organization: Armenian Computer Center X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Joliet file system? References: <367C5118.4C32904B@freedomnet.com> <3.0.5.32.19981221125508.0091cd10@mail.scancall.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry for silly question , how can i do that ? URL's /docs are welcome ..... Marius Bendiksen wrote: > > Check out the PR database. A set of real patches exist there. > > --- > Marius Bendiksen, IT-Trainee, ScanCall AS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 06:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28911 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 06:24:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from qix (ppp001.infranet.fr [195.68.70.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28906 for ; Mon, 21 Dec 1998 06:24:24 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.1/8.8.7) id PAA48229; Mon, 21 Dec 1998 15:25:44 +0100 (MET) Date: Mon, 21 Dec 1998 15:25:44 +0100 (MET) Message-Id: <199812211425.PAA48229@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: doconnor@gsoft.com.au CC: freebsd-hackers@FreeBSD.ORG In-reply-to: Subject: Re: PCI IRQ mappings X-Mailer: Emacs Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Daniel O'Connor writes: > On 21-Dec-98 Jean-Marc Zucconi wrote: >> > is to shuffle cards in the machine. Is there a better way? :) >> I think you just have to change the interrupt line register in the >> configuration registers, and maybe the route control register (offset >> 0x60) > Hmmm.. I looked at offset 60 and its the 'DRAM Row Boundary Registers' in device 0, and > non existant in device 1. You looked in the MXTC documentation. The interrupt routing is described in the PIIX4 documentation (PCI-TO-ISA/IDE XCELERATOR), 20956201.pdf. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 07:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03146 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 07:13:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03135 for ; Mon, 21 Dec 1998 07:13:15 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id PAA32067; Mon, 21 Dec 1998 15:11:35 GMT Message-ID: <367E6525.A232C8B8@tdx.co.uk> Date: Mon, 21 Dec 1998 15:11:33 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Casper CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Joliet file system? References: <367C5118.4C32904B@freedomnet.com> <3.0.5.32.19981221125508.0091cd10@mail.scancall.no> <367E588F.E20CE19F@acc.am> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Casper wrote: > > Sorry for silly question , how can i do that ? > URL's /docs are welcome ..... > Marius Bendiksen wrote: Hmmm... I've found the PR, the patches look OK - I've not got time at the moment to apply them, I'll see if I can get a chance this evening... If you go to this URL you'll find the details: http://www.freebsd.org/cgi/query-pr.cgi?pr=5038 Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 08:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12823 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 08:14:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12818 for ; Mon, 21 Dec 1998 08:14:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id IAA83471; Mon, 21 Dec 1998 08:14:43 -0800 (PST) To: tom@tomqnx.com (Tom Torrance at home) cc: hackers@FreeBSD.ORG Subject: Re: kernel panic In-reply-to: Your message of "Mon, 21 Dec 1998 07:58:20 EST." Date: Mon, 21 Dec 1998 08:14:43 -0800 Message-ID: <83468.914256883@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Last week, x11amp seemed to work absolutely reliably with the OSS sound > system. (x11amp -b 1024 on FreeBSD-current with creative AWE-64). Hmmm. I just updated this port to the latest version (from, oddly enough, the OSS folks) and now it works with the stock sound driver. It also claims to work with OSS and if that's not the case then you should definitely get back to the OSS folks about this (at the very least, their code shouldn't PANIC the system) since they're the one who created this update in the first place and I'd expect it to Just Work(tm) with OSS. Let me know what they say, thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 08:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13472 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 08:23:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13460 for ; Mon, 21 Dec 1998 08:23:05 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: (from vanmaren@localhost) by fast.cs.utah.edu (8.9.1/8.9.1) id JAA01401; Mon, 21 Dec 1998 09:22:56 -0700 (MST) Date: Mon, 21 Dec 1998 09:22:56 -0700 (MST) From: Kevin Van Maren Message-Id: <199812211622.JAA01401@fast.cs.utah.edu> To: doconnor@gsoft.com.au, mike@smith.net.au Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Windows 9[58] take it upon themselves to manage resource allocation, > and they do this using int 1a functions 0xb10e and 0xb10f (get IRQ > routing information, set PCI IRQ). You also have to update the config > register on the PCI device. Yes, this should allow you to change the interrupt mapping. > This is the only way to do this correctly. Well, almost. The problem is that if the PCI interrupts ARE shared, then redirecting the IRQ for one board WILL also change the redirection for the other devices using the same interrupt pin -- they are connected at the motherboard/hardware level. So this does not allow you to make a device not share an interrupt. Intel's PCI chipsets only support redirecting 4 PCI interrupts to an "ISA" vector number. So if you want more than 4 interrupts for all your PCI devices, you are out of luck. Motherboard manufacturers just connect multiple interrupt sources together and feed them into the same interrupt pin. Those 4 interrupt pins are programmable to a variety of values. If you have 4 interrupts to dedicate to PCI devices, the BIOS will use 4 different interrupts (PCI IDE are a special case, btw). So the only way you would get shared PCI interrupts are a) you don't have enough interrupts for PCI devices, and the BIOS programmed multiple PCI IRQ redirection pins to the same value, but you can't do anything about it becaue you don't have a free interrupt, or b) the motherboard manufacturer physically connected the interrupt pins together, so changing the interrupt number will change it for both (all) devices using the same redirection pin, and it will still be a shared interrupt. To be PCI-compliant, the device MUST support the use of shared interrupts. It is amost never the case that the hardware is broken, but many drivers (especially for Windows) are. If the hardware is broken, complain bitterly to the vendor. If the driver is broken, complain bitterly to the driver writer. Kevin Van Maren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 09:17:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21048 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 09:17:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from foonly.scimitar.org (cr323989-a.yec1.on.wave.home.com [24.112.82.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21006; Mon, 21 Dec 1998 09:17:34 -0800 (PST) (envelope-from pnadeau@wave.home.com) Received: from localhost (pnadeau@localhost) by foonly.scimitar.org (8.8.5/8.8.5) with SMTP id MAA14037; Mon, 21 Dec 1998 12:17:31 -0500 (EST) X-Authentication-Warning: foonly.scimitar.org: pnadeau owned process doing -bs Date: Mon, 21 Dec 1998 12:17:30 -0500 (EST) From: Patrick Nadeau X-Sender: pnadeau@foonly.scimitar.org To: wollman@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Locking arp entries Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Originally sent to: wollman@freebsd.org I recently had to make a mod to the kernel to fix a problem I had with arp. I'm letting you know in case anyone else is interested in it. In a nutshell I have an internal ethernet on the 10 network. I have a number of machines on the inside and a multihomed FreeBSD box connected to the Rogers @home service. It serves as a firewall and does the NAT for the machines on the inside. Somebody hooked up his machine to the Rogers network as 10.0.0.2. This caused gratuitous arp packets to reach my firewall and corrupt the arp entries for my inside host 10.0.0.2, making it unreachable. The problem persisted for a whole day and became so bad I decided to add a routing flag RTF_LOCK and some logic in in_arpinput to ignore packets if the flag is on. I also added code to set the lock flag to arp(8). I am mentioning this to you because I noticed the comment TODO: add "inuse/lock" bit in if_ether.c and assumed somebody meant to get around to do it. Let me know if you want to see the patches, it's not rocket science but it really fixed my problem! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 09:26:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22954 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 09:26:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.cs.unc.edu (austin.cs.unc.edu [152.2.128.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22918 for ; Mon, 21 Dec 1998 09:26:15 -0800 (PST) (envelope-from moorthy@cs.unc.edu) Received: from buzzard.cs.unc.edu (moorthy@buzzard.cs.unc.edu [152.2.129.17]) by austin.cs.unc.edu (8.8.8/8.8.8) with SMTP id MAA00308; Mon, 21 Dec 1998 12:25:54 -0500 (EST) Date: Mon, 21 Dec 1998 12:25:54 -0500 (EST) From: Arun Moorthy To: Brian McGovern cc: hackers@FreeBSD.ORG Subject: Re: install disk for CAM and 3C905 In-Reply-To: <199810091351.JAA01796@bmcgover-pc.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Oct 1998, Brian McGovern wrote: > Once you've checked them out, branch the source tree, since you'll be making > your own local changes that you'll want to keep. To do this, issue a > "cvs tag -b YOURTAG src" from the aforementioned "working directory", so it > will tag all of the src directory. YOURTAG can be replaced by anything you > want, so long as its valid, and hasn't been used. What I'm doing now is to apply the CAM patch to 2.2.8-REL. My question is how to apply my changes (actually the changes done by CAM devel). after i do the cvs checkout and the cvs branch, can i go in and apply the patch in the src directory, follow that up with a cvs commit? what i want to do is to build a 2.2.8 release that has support for CAM in it. thankx, -arun > > Then, to change the boot disk, edit src/sys/i386/conf/GENERIC. The release > process will strip out portions of this to minimalize it. Its in > src/release/floppies/boot/floppy/Makefile (you'll probably want to edit > both the one in /usr/src, and in your currently checked out copy, although the > latter is the one that should be used). Otherwise, add the options you need > to GENERIC. > > Once done, go back to your working directory, and "cvs commit src". It should > check in all of your changes (and ask you to provide CVS comments for each). > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 09:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23229 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 09:28:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA23221 for ; Mon, 21 Dec 1998 09:28:49 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zs98J-0001TQ-00; Mon, 21 Dec 1998 10:28:39 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id KAA02738 for ; Mon, 21 Dec 1998 10:26:53 -0700 (MST) Message-Id: <199812211726.KAA02738@harmony.village.org> To: hackers@FreeBSD.ORG Subject: Information needed on SMI Date: Mon, 21 Dec 1998 10:26:52 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I'm looking for information on the SMI bios stuff. I don't mean Intel's SMBios, but the SMI in "Power management: APM, SMI" that comes up when I boot my machine. My web searches have turned up the Intel spec a lot, but nothing on SMI itself (except that this or that computer support it). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 09:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24059 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 09:35:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24040 for ; Mon, 21 Dec 1998 09:35:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA02317; Mon, 21 Dec 1998 09:33:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211733.JAA02317@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tom@tomqnx.com (Tom Torrance at home) cc: hackers@FreeBSD.ORG Subject: Re: kernel panic In-reply-to: Your message of "Mon, 21 Dec 1998 07:58:20 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 09:33:17 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Last week, x11amp seemed to work absolutely reliably with the OSS sound > system. (x11amp -b 1024 on FreeBSD-current with creative AWE-64). > > I updated the system Sunday AM with cvsup and ever since, I get > a kernel panic within 5 minutes of starting x11amp. First the sound > stops, with x11amp happily executing, then in 3-4 seconds, panicsville. > No core dump that I could ascertain. You want to perhaps tell us what the panic message was? Or was it a trap? C'mon, give us something to work with here. > Any hints? Any recent changes affecting dma, virtual memory > swapping, etc? The Posix realtime scheduling stuff may have been enabled by default; I've run multiple world builds with it here, but it's possible that x11amp has actually detected and enabled it, which is something I haven't been able to test much. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 09:55:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26106 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 09:55:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles130.castles.com [208.214.165.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26095 for ; Mon, 21 Dec 1998 09:55:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA02386; Mon, 21 Dec 1998 09:40:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812211740.JAA02386@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: hackers@FreeBSD.ORG Subject: Re: Information needed on SMI In-reply-to: Your message of "Mon, 21 Dec 1998 10:26:52 MST." <199812211726.KAA02738@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 09:40:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Greetings, > I'm looking for information on the SMI bios stuff. I don't > mean Intel's SMBios, but the SMI in "Power management: APM, SMI" that > comes up when I boot my machine. My web searches have turned up the > Intel spec a lot, but nothing on SMI itself (except that this or that > computer support it). SMI is "system management interrupt", it causes the processor to enter SMM ("system management mode"). You'll find documentation on it in the Intel processor manuals, IIRC from the '486 onwards. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 10:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29081 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 10:15:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29076 for ; Mon, 21 Dec 1998 10:15:11 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id TAA39964; Mon, 21 Dec 1998 19:14:54 +0100 (CET) (envelope-from des) To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: Wordperfect port committed References: <199812200533.VAA41524@dingo.cdrom.com> From: Dag-Erling Smorgrav Date: 21 Dec 1998 19:14:53 +0100 In-Reply-To: Mike Smith's message of "Sat, 19 Dec 1998 21:33:38 -0800" Message-ID: Lines: 50 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > Feedback would be welcome; this works here for me (install and > uninstall) and it portlints, but the install is somewhat complex and > I'm sure to have missed something... Here's feedback: root@flood /usr/ports/editors/wordperfect# make install ===> Installing for wordperfect-8.0 ===> wordperfect-8.0 depends on file: /compat/linux/lib/libc.so.5 - not found ===> Verifying install for /compat/linux/lib/libc.so.5 in /usr/ports/emulators/linux_lib >> linux_lib-2.6.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/. Receiving linux_lib-2.6.tar.gz (8529195 bytes): 100% 8529195 bytes transfered in 1254.9 seconds (6.64 Kbytes/s) ===> Extracting for linux_lib-2.6 >> Checksum OK for linux_lib-2.6.tar.gz. ===> Patching for linux_lib-2.6 ===> Configuring for linux_lib-2.6 ===> Installing for linux_lib-2.6 ===> Generating temporary packing list /compat/linux/sbin/ldconfig /bin/mkdir -p /compat/linux/usr/lib/zoneinfo ln -sf /etc/localtime //compat/linux/usr/lib/zoneinfo/localtime ===> Registering installation for linux_lib-2.6 ===> Returning to build of wordperfect-8.0 This installation of WordPerfect will expire in 90 days, unless you retrieve a free registration key from https://livewire.corel.com/wp8LinuxReg/ to register your copy TODAY. Do this now! Bad Line Option: 00 OK_BUTTON=Accept Bad Line Option: 00 CANCEL_BUTTON=Decline Bad Line Option: 00 HELP_BUTTON= Bad Line Option: 00 Comment=WordPerfect 8 for UNIX Systems Bad Line Option: 00 Comment= Bad Line Option: 00 Comment=Please read the following license agreement before Bad Line Option: 00 Comment=proceeding. Bad Line Option: 00 Comment=DONE Bad Line Option: 00 PRINTERS_GUI=shared/license está de acuerdo con este Acuerdo de Licencia,seleccione "Decline" y devuelva el software aldistribuidor que le vendió este producto.Si vous êtes en accord avec les clauses de cecontrat de licence, choisissez « Accept ». Dansle cas contraire, choisissez « Decline » etIf retournez le logiciel à votre revendeur.AgrSe si è d'accordo con i termini di questowitcontratto di licenza, scegliere "Accept". Se nonretsi è d'accordo con questo contratto di licenza,Wähscegliere "Decline" e restituire il programma aldierivenditore.SieAls u met de voorwaarden van dezeeinlicentie-overeenkomst akkoord gaat, kiest udas"Accept". Als u deze licentieovereenkomst niet wiltSi accepteren, kiest u "Decline" en stuurt u deAcusoftware terug naar de verkoper.------------------------------------------------------u,U = Upd,D = Downo = Accept p = Prev c = Decline it hangs there. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 10:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03328 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 10:46:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03319 for ; Mon, 21 Dec 1998 10:46:26 -0800 (PST) (envelope-from ugen@undp.org) Received: from inet01.hq.undp.org (inet01.hq.undp.org [192.124.42.9]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id NAA04423 for ; Mon, 21 Dec 1998 13:46:12 -0500 (EST) Received: from undp.org ([165.65.2.224]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA73A2 for ; Mon, 21 Dec 1998 13:45:27 -0500 Message-ID: <367E9711.2DC74676@undp.org> Date: Mon, 21 Dec 1998 13:44:33 -0500 From: "Ugen Antsilevitch" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Apache with dynamic modules files miserably. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well..subject says it all. Both the 1.3.2 in packages and new 1.3.3 after compilation are unable to use dynamic loaded modules. It seems dlopen fails for any module that attempts to call a function from the server itself (such as pa_alloc etc.). I am really not sure how this can/should be fixed... Ideas? --Ugen P.S. On the completely different topic - can i force PCI Ethernet cards to have different IRQ numbers. BIOS assigns same number for both and it seems to impact network performance - i.e. i get this "micro"stalls once in a while..or could it be BPF enabled? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:01:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05471 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:01:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05459 for ; Mon, 21 Dec 1998 11:01:27 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id OAA15127; Mon, 21 Dec 1998 14:00:49 -0500 (EST) Date: Mon, 21 Dec 1998 14:00:49 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Kaleb Keithley cc: hackers@FreeBSD.ORG Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. In-Reply-To: <199812191330.IAA26067@sunoco> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, on a 2.2-stable snap, I started getting this soon after installing KDE. In other words, I was running dangerously low on swap... Dumping 128M in the machine fixed the problem. Is this really anything besides a rather confusing way of inetd saying "can't allocate memory"? Charles --- Charles Sprickman spork@super-g.com On Sat, 19 Dec 1998, Kaleb Keithley wrote: > > My 3.0-RELEASE system, up some 17 days, is now doing this when I telnet > (or ping, or anything else that uses inetd) to it. (I don't know how long > it's been like this, perhaps it explains why my outgoing email seem to > be being dropped on the floor. > > Do I remember correctly that there was some fix for this made shortly > before 3.0-RELEASE? Did the fix not make it into 3.0-RELEASE? Before > I go snag the LaG inetd sources, will that fix the problem? > > Thanks, > > -- > > Kaleb > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:01:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05477 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:01:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05462 for ; Mon, 21 Dec 1998 11:01:28 -0800 (PST) (envelope-from lching@cisco.com) Received: from lching-pc.cisco.com (lching-pc.cisco.com [171.69.206.55]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA29477; Mon, 21 Dec 1998 14:01:18 -0500 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lching-pc.cisco.com (8.8.8/8.8.8) with ESMTP id OAA08482; Mon, 21 Dec 1998 14:02:03 -0500 (EST) (envelope-from lching@cisco.com) Message-ID: <367E9B2B.9E5355DE@cisco.com> Date: Mon, 21 Dec 1998 14:02:03 -0500 From: Larry Ching X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Daniel Eischen CC: hackers@FreeBSD.ORG, lching@cisco.com Subject: Re: pthreads question References: <199812190417.XAA10236@pcnet1.pcnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > > I am having a problem porting an application that runs on FreeBSD > > 2.2.6 and doesn't on FreeBSD 3.0. The problem seems to be caused > > by differences in the pthreads implemention on the two systems. > > > > Trying to state the problem in its simplest terms, the application > > spawns a thread that continually tries to read data from a device. > > The thread, of course, blocks on the read() call if no data is > > available from the device. To terminate the read thread, another > > thread issues a pthread_kill() call to the read thread, which in > > 2.2.6 would cause the read() to return -1 with an errno of EINTR. > > This would cause the thread to terminate itself. However, under > > 3.0 the read does not return and the reader thread remains blocked. > > Each thread has it's own signal mask. Does the thread that you're > trying to interrupt have the signal blocked? > > > I have scanned through the pthread code under 3.0 and the difference > > seems to lie in the pthread_kill() code in uthread_kill.c. > > Specifically, the signal specified in pthread_kill() is just added > > to the signal list if the thread is in any other state except > > PS_SIGSUSPEND or PS_SIGWAIT. I believe that the reader thread is > > in PS_FDR_WAIT state at this point and thus nothing happens. > > A quick glance of the code shows that this is what happens only > if the signal is blocked in the thread. If the signal is unblocked, > then the thread should return with EINTR. Use sigprocmask(2) to > unblock the signal in the thread that you want to interrupt. Thank you for your help above. The thread in question was making acall to pthread_sigmask(SIG_UNBLOCK,...) to unblock the signal I was using in pthread_kill(). I changed this call to sigprocmask(SIG_UNBLOCK, ...) with no effect. The thread remains blocked in the read() call and no EINTR error code is returned. Any suggestions as to where to look next??? Larry Ching > > > Dan Eischen > eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:15:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07010 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:15:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from postino.raremedium.com (postino.raremedium.com [209.67.44.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA06989 for ; Mon, 21 Dec 1998 11:14:57 -0800 (PST) (envelope-from daniell@raremedium.com) Received: (qmail 15700 invoked from network); 21 Dec 1998 19:20:59 -0000 Received: from steamer.raremedium.com (209.67.44.116) by postino.raremedium.com with SMTP; 21 Dec 1998 19:20:59 -0000 Received: by steamer.raremedium.com with Internet Mail Service (5.5.2232.9) id ; Mon, 21 Dec 1998 14:11:45 -0500 Message-ID: <93A9C7D71478D211ACEC00805F65C14F1BD06C@steamer.raremedium.com> From: Daniel Leeds To: "'hackers@freebsd.org'" Subject: adaptec 2940uw2 Date: Mon, 21 Dec 1998 14:11:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does freebsd support the adaptec 2940uw2 card? and if so, which release? thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:15:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07252 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:15:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07242 for ; Mon, 21 Dec 1998 11:15:35 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id LAA14214; Mon, 21 Dec 1998 11:13:49 -0800 (PST) (envelope-from dhw) Date: Mon, 21 Dec 1998 11:13:49 -0800 (PST) From: David Wolfskill Message-Id: <199812211913.LAA14214@pau-amma.whistle.com> To: gram@cdsec.com, kaleb@ics.com Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. Cc: hackers@FreeBSD.ORG In-Reply-To: <199812210938.LAA17923@cdsec.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Graham Wheeler >Date: Mon, 21 Dec 1998 11:38:00 +0200 (SAT) >> My 3.0-RELEASE system, up some 17 days, is now doing this when I telnet >> (or ping, or anything else that uses inetd) to it. (I don't know how long >> it's been like this, perhaps it explains why my outgoing email seem to >> be being dropped on the floor. >> Do I remember correctly that there was some fix for this made shortly >> before 3.0-RELEASE? Did the fix not make it into 3.0-RELEASE? Before >> I go snag the LaG inetd sources, will that fix the problem? >There is an open problem report, bin/8183, about this. I have just received >mail saying that the fix I posted changes the signal mask for child processes >and breaks Amanda; I haven't had a chance to look at this yet, and have not >experienced any problems myself. You may want to try the patches and see how >it goes. It's still a little early to tell for sure, but things with amanda & 3.0 seem to be no worse than they were before Matt's first patch (that caused inet's child processes (such as amandad) to be forked off with interrupts blocked), and may actually be better. With only the first patch applied, the symptom was an immediate amandad failure, whining about dup UDP packets, then amandad would hang (until killed). (One of my colleagues is running a 3.0 system that is often under significant load; its amandad typically has started failing within 3 or 4 days. He re-started the patched inetd Friday....) david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08510 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:26:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08494 for ; Mon, 21 Dec 1998 11:26:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA07476; Mon, 21 Dec 1998 11:25:41 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA04664; Mon, 21 Dec 1998 11:25:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 21 Dec 1998 11:25:38 -0800 (PST) Message-Id: <199812211925.LAA04664@vashon.polstra.com> To: ugen@undp.org Subject: Re: Apache with dynamic modules files miserably. Newsgroups: polstra.freebsd.hackers In-Reply-To: <367E9711.2DC74676@undp.org> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <367E9711.2DC74676@undp.org>, Ugen Antsilevitch wrote: > Well..subject says it all. > Both the 1.3.2 in packages and new 1.3.3 after compilation are unable to > use dynamic > loaded modules. It seems dlopen fails for any module that attempts to > call a function from > the server itself (such as pa_alloc etc.). > I am really not sure how this can/should be fixed... > Ideas? Well, it would be a lot easier if you had told us which version of FreeBSD you're using. If it's current/ELF, then make sure your ELF dynamic linker is newer than October 13. I put a bugfix into "src/libexec/rtld-elf/rtld.c" on that date which fixed a problem in the apache13 port. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:34:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09841 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:34:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09800 for ; Mon, 21 Dec 1998 11:34:12 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA01713; Mon, 21 Dec 1998 14:33:53 -0500 (EST) Date: Mon, 21 Dec 1998 14:33:53 -0500 (EST) From: Daniel Eischen Message-Id: <199812211933.OAA01713@pcnet1.pcnet.com> To: eischen@vigrid.com, lching@cisco.com Subject: Re: pthreads question Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Ching wrote: > > A quick glance of the code shows that this is what happens only > > if the signal is blocked in the thread. If the signal is unblocked, > > then the thread should return with EINTR. Use sigprocmask(2) to > > unblock the signal in the thread that you want to interrupt. > > Thank you for your help above. The thread in question was making acall > to pthread_sigmask(SIG_UNBLOCK,...) to unblock the signal I > was using in pthread_kill(). I changed this call to > sigprocmask(SIG_UNBLOCK, ...) with no effect. The thread remains > blocked in the read() call and no EINTR error code is returned. > > Any suggestions as to where to look next??? You haven't set the action for the signal to SIG_IGN, have you? Got a simple prgram to demonstrate the problem? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:35:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10230 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:35:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10200 for ; Mon, 21 Dec 1998 11:35:47 -0800 (PST) (envelope-from lile@stdio.com) Received: from heathers.stdio.com (lile@heathers.stdio.com [199.89.192.5]) by heathers.stdio.com (8.8.8/8.8.8) with ESMTP id OAA09990 for ; Mon, 21 Dec 1998 14:39:06 -0500 (EST) (envelope-from lile@stdio.com) Date: Mon, 21 Dec 1998 14:39:05 -0500 (EST) From: Larry Lile To: hackers@FreeBSD.ORG Subject: Binary conversion ELF/COFF -> a.out Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I need to convert either an ELF or SCO COFF object to an a.out object so that I can link it in a 2.2.x kernel. Anyone know of a utility that can do this? If not, what would be involved in writing a utility to do this? Alternately is there any other trick that could be done to get around this. Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13409 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:52:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13389 for ; Mon, 21 Dec 1998 11:52:43 -0800 (PST) (envelope-from lching@cisco.com) Received: from lching-pc.cisco.com (lching-pc.cisco.com [171.69.206.55]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA00903; Mon, 21 Dec 1998 14:52:32 -0500 (EST) Received: from cisco.com (localhost.cisco.com [127.0.0.1]) by lching-pc.cisco.com (8.8.8/8.8.8) with ESMTP id OAA08528; Mon, 21 Dec 1998 14:53:21 -0500 (EST) (envelope-from lching@cisco.com) Message-ID: <367EA731.BFAB48C3@cisco.com> Date: Mon, 21 Dec 1998 14:53:21 -0500 From: Larry Ching X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Daniel Eischen CC: hackers@FreeBSD.ORG, lching@cisco.com Subject: Re: pthreads question References: <199812211933.OAA01713@pcnet1.pcnet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen wrote: > Larry Ching wrote: > > > > A quick glance of the code shows that this is what happens only > > > if the signal is blocked in the thread. If the signal is unblocked, > > > then the thread should return with EINTR. Use sigprocmask(2) to > > > unblock the signal in the thread that you want to interrupt. > > > > Thank you for your help above. The thread in question was making acall > > to pthread_sigmask(SIG_UNBLOCK,...) to unblock the signal I > > was using in pthread_kill(). I changed this call to > > sigprocmask(SIG_UNBLOCK, ...) with no effect. The thread remains > > blocked in the read() call and no EINTR error code is returned. > > > > Any suggestions as to where to look next??? > > You haven't set the action for the signal to SIG_IGN, have you? There is this code segment in the thread to be killed: struct sigaction sa; sigset_t setUser1; sa.sa_handler = SigUsr1Handler; sigemptyset(&sa.sa_mask); sa.sa_flags = 0; sigaction(SIGUSR1, &sa, NULL); sigemptyset(&setUser1); sigaddset(&setUser1, SIGUSR1); sigprocmask(SIG_UNBLOCK, &setUser1, NULL); //pthread_sigmask(SIG_UNBLOCK, &setUser1, NULL); where SigUsr1Handler is defined as: void SigUsr1Handler(int signal) { } My understanding is that this guarantees the action to not be SIG_IGN. I don't understand why this is not sufficient for the read() call to be interrupted. > Got a simple prgram to demonstrate the problem? No, but I will attempt to create one. Larry Ching Cisco Systems lching@cisco.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 11:56:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13854 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 11:56:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13744 for ; Mon, 21 Dec 1998 11:56:14 -0800 (PST) (envelope-from ugen@undp.org) Received: from inet01.hq.undp.org (inet01.hq.undp.org [192.124.42.9]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id OAA09137 for ; Mon, 21 Dec 1998 14:56:04 -0500 (EST) Received: from undp.org ([165.65.2.224]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA1789; Mon, 21 Dec 1998 14:52:25 -0500 Message-ID: <367EA6C2.917286BD@undp.org> Date: Mon, 21 Dec 1998 14:51:30 -0500 From: "Ugen Antsilevitch" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: hackers@FreeBSD.ORG Subject: Re: Apache with dynamic modules files miserably. References: <199812211925.LAA04664@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well...sorry for omitting that - it is 3.0 - RELEASE. I just downloaded rtld.c from 3.0-CURRENT - that one seems to be dated Nov.27 . I recompiled ld-elf.so.1 and installed it but Apache still fails. Here is the error i get: Cannot load /usr/local/apache/libexec/mod_env.so into server: /usr/local/apache/lib exec/mod_env.so: Undefined symbol "ap_palloc". This can change depending on which module gets loaded first but function it complains about is one in the main source. Any other advice will be appretiated...:) --Ugen John Polstra wrote: > In article <367E9711.2DC74676@undp.org>, > Ugen Antsilevitch wrote: > > Well..subject says it all. > > Both the 1.3.2 in packages and new 1.3.3 after compilation are unable to > > use dynamic > > loaded modules. It seems dlopen fails for any module that attempts to > > call a function from > > the server itself (such as pa_alloc etc.). > > I am really not sure how this can/should be fixed... > > Ideas? > > Well, it would be a lot easier if you had told us which version of > FreeBSD you're using. > > If it's current/ELF, then make sure your ELF dynamic linker is newer > than October 13. I put a bugfix into "src/libexec/rtld-elf/rtld.c" > on that date which fixed a problem in the apache13 port. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 12:00:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14451 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 12:00:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rs1s2.datacenter.cha.cantv.net (rs1s2.datacenter.cha.cantv.net [200.44.32.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14446 for ; Mon, 21 Dec 1998 12:00:45 -0800 (PST) (envelope-from lem@cantv.net) Received: from lg (tc1r9-117.ras.cha.cantv.net [200.44.7.117]) by rs1s2.datacenter.cha.cantv.net (8.9.1a/8.9.1/1.0) with SMTP id QAA22655; Mon, 21 Dec 1998 16:00:34 -0400 (VET) Message-Id: <3.0.6.32.19981221160025.008547d0@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 21 Dec 1998 16:00:25 -0400 To: spork , Kaleb Keithley From: Luis =?iso-8859-1?Q?Mu=F1oz?= Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199812191330.IAA26067@sunoco> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:00 PM 21/12/98 -0500, spork wrote: >FWIW, on a 2.2-stable snap, I started getting this soon after installing >KDE. In other words, I was running dangerously low on swap... Dumping >128M in the machine fixed the problem. Is this really anything besides a >rather confusing way of inetd saying "can't allocate memory"? I've seen a very similar behavior in sendmail after applying some perl related patches. I believe this code is actually in the libraries and not in inetd. A free() or realloc() when fed with a wrong pointer would output this message to STDERR, which in inetd is already pointed to the socket assigned to the process to be fork()'ed. Killing and restarting inetd fixes this in a 2.2.x machine, but will eventually reappear. It definitely is related to vm (not enough vm I mean). Look... bash-2.01# pwd /usr/src/lib/libc bash-2.01# egrep 'too high' */*.c stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); bash-2.01# egrep 'too low' */*.c stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); and in stdlib/malloc.c... static void wrtwarning(char *p) { char *q = " warning: "; if (malloc_abort) wrterror(p); write(STDERR_FILENO, __progname, strlen(__progname)); write(STDERR_FILENO, malloc_func, strlen(malloc_func)); write(STDERR_FILENO, q, strlen(q)); write(STDERR_FILENO, p, strlen(p)); } It would be easy to stop this error, perhaps by some malloc() option or via an additional call (or even commenting or selective compilation of this function). Hope this helps. -lem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 12:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16139 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 12:09:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15994 for ; Mon, 21 Dec 1998 12:09:29 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA22109; Mon, 21 Dec 1998 15:08:52 -0500 (EST) Date: Mon, 21 Dec 1998 15:08:52 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Luis =?iso-8859-1?Q?Mu=F1oz?= cc: Kaleb Keithley , hackers@FreeBSD.ORG Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. In-Reply-To: <3.0.6.32.19981221160025.008547d0@pop.cantv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA16134 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, here's what sendmail does here, it's pretty scary, with those truncated messages about spwd.db: Dec 17 15:42:27 super-g Dec 17 15:42:27sendmail[: NOQUEUE Dec 17 15:51:11 super-g Dec 17 15:51:11sendmail[: /etc/spwd.db Dec 17 15:51:11 super-g sendmail[16594]: NOQUEUE: SYSERR(root): Out of memory!!: Cannot allocate memory Dec 17 16:30:01 super-g Dec 17 16:30:00sendmail[: /etc/spwd.db Dec 17 16:30:16 super-g /kernel: pid 20618 (sendmail), uid 0: exited on signal 11 Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: NOQUEUE Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db Charles --- Charles Sprickman spork@super-g.com On Mon, 21 Dec 1998, Luis [iso-8859-1] Muñoz wrote: > At 02:00 PM 21/12/98 -0500, spork wrote: > >FWIW, on a 2.2-stable snap, I started getting this soon after installing > >KDE. In other words, I was running dangerously low on swap... Dumping > >128M in the machine fixed the problem. Is this really anything besides a > >rather confusing way of inetd saying "can't allocate memory"? > > I've seen a very similar behavior in sendmail after applying some > perl related patches. I believe this code is actually in the > libraries and not in inetd. A free() or realloc() when fed with > a wrong pointer would output this message to STDERR, which in inetd > is already pointed to the socket assigned to the process to be fork()'ed. > > Killing and restarting inetd fixes this in a 2.2.x machine, but will > eventually reappear. It definitely is related to vm (not enough vm I > mean). > > Look... > > bash-2.01# pwd > /usr/src/lib/libc > bash-2.01# egrep 'too high' */*.c > stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); > stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); > bash-2.01# egrep 'too low' */*.c > stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); > stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); > > and in stdlib/malloc.c... > > static void > wrtwarning(char *p) > { > char *q = " warning: "; > if (malloc_abort) > wrterror(p); > write(STDERR_FILENO, __progname, strlen(__progname)); > write(STDERR_FILENO, malloc_func, strlen(malloc_func)); > write(STDERR_FILENO, q, strlen(q)); > write(STDERR_FILENO, p, strlen(p)); > } > > It would be easy to stop this error, perhaps by some malloc() > option or via an additional call (or even commenting or > selective compilation of this function). > > Hope this helps. > > -lem > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 12:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16476 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 12:11:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16470 for ; Mon, 21 Dec 1998 12:11:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id MAA07618; Mon, 21 Dec 1998 12:11:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id MAA04772; Mon, 21 Dec 1998 12:11:05 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <367EA6C2.917286BD@undp.org> Date: Mon, 21 Dec 1998 12:11:05 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Ugen Antsilevitch Subject: Re: Apache with dynamic modules files miserably. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Ugen Antsilevitch wrote: > Well...sorry for omitting that - it is 3.0 - RELEASE. > I just downloaded rtld.c from 3.0-CURRENT - that one seems to be dated Nov.27 > . > I recompiled ld-elf.so.1 and installed it but Apache still fails. > Here is the error i get: > Cannot load /usr/local/apache/libexec/mod_env.so into server: > /usr/local/apache/lib > exec/mod_env.so: Undefined symbol "ap_palloc". > This can change depending on which module gets loaded first but function it > complains about is > one in the main source. This sounds like the port is out of date. Get the latest version of it from the web site. Also, get the ports upgrade kit that updates the files in "/usr/share/mk". That should fix it. I know this port works in -current, and somebody confirmed it just two days ago. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 12:31:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20131 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 12:31:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gvinpin.grad.kiev.ua (KievglavArhit-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20123 for ; Mon, 21 Dec 1998 12:31:41 -0800 (PST) (envelope-from Ruslan@Shevchenko.Kiev.UA) Received: from Shevchenko.Kiev.UA (kulshedra [10.0.1.99]) by gvinpin.grad.kiev.ua (8.8.7/8.8.7) with ESMTP id WAA08452; Mon, 21 Dec 1998 22:31:10 +0200 Message-ID: <367ECC5F.E9414DDA@Shevchenko.Kiev.UA> Date: Tue, 22 Dec 1998 00:31:59 +0200 From: Ruslan Shevchenko Reply-To: rssh@grad.kiev.ua X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Larry Lile CC: hackers@FreeBSD.ORG Subject: Re: Binary conversion ELF/COFF -> a.out References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry Lile wrote: > I need to convert either an ELF or SCO COFF object to an > a.out object so that I can link it in a 2.2.x kernel. > > Anyone know of a utility that can do this? If not, what > would be involved in writing a utility to do this? > look at ports/7150 in PR database. > > Alternately is there any other trick that could be done > to get around this. > > Larry Lile > lile@stdio.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 12:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22985 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 12:50:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22976 for ; Mon, 21 Dec 1998 12:50:50 -0800 (PST) (envelope-from ncbp@freesbee.t.dk) Received: (qmail 20486 invoked by uid 1002); 21 Dec 1998 20:44:06 -0000 Date: Mon, 21 Dec 1998 21:44:06 +0100 From: "Niels Chr. Bank-Pedersen" To: hackers@FreeBSD.ORG Subject: Re: Wordperfect port committed Message-ID: <19981221214406.B20266@bank-pedersen.dk> Mail-Followup-To: hackers@FreeBSD.ORG References: <199812200533.VAA41524@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i In-Reply-To: ; from Dag-Erling Smorgrav on Mon, Dec 21, 1998 at 07:14:53PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 07:14:53PM +0100, Dag-Erling Smorgrav wrote: [...] > Bad Line Option: 00 PRINTERS_GUI=shared/license > está de acuerdo con este Acuerdo de Licencia,seleccione "Decline" y devuelva el software aldistribuidor que le vendió este producto.Si vous êtes en accord avec les clauses de cecontrat de licence, choisissez « Accept ». Dansle cas contraire, choisissez « Decline » etIf retournez le logiciel à votre revendeur.AgrSe si è d'accordo con i termini di questowitcontratto di licenza, scegliere "Accept". Se nonretsi è d'accordo con questo contratto di licenza,Wähscegliere "Decline" e restituire il programma aldierivenditore.SieAls u met de voorwaarden van dezeeinlicentie-overeenkomst akkoord gaat, kiest udas"Accept". Als u deze licentieovereenkomst niet wiltSi accepteren, kiest u "Decline" en stuurt u deAcusoftware terug naar de verkoper.------------------------------------------------------u,U = Upd,D = Downo = Accept p = Prev c = Decline > > it hangs there. I guess you weren't running X? (I ran into this one too since I usually don't run X as privileged user, but for wp8 I'll do alot of things :) > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark DataNET, IP-section. # rsh -l God universe.all find / -name '*windows*' -exec rm -rf {} \\; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 13:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25533 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 13:10:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rs5s2.datacenter.cha.cantv.net (rs5s2.datacenter.cha.cantv.net [200.44.32.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25528 for ; Mon, 21 Dec 1998 13:10:35 -0800 (PST) (envelope-from lem@cantv.net) Received: from lg (tc2r9-185.ras.cha.cantv.net [200.44.8.185]) by rs5s2.datacenter.cha.cantv.net (8.9.1a/8.9.1/1.0) with SMTP id RAA11978; Mon, 21 Dec 1998 17:10:25 -0400 (VET) Message-Id: <3.0.6.32.19981221171019.008451f0@pop.cantv.net> X-Sender: lem@pop.cantv.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 21 Dec 1998 17:10:19 -0400 To: spork From: Luis =?iso-8859-1?Q?Mu=F1oz?= Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. Cc: Kaleb Keithley , hackers@FreeBSD.ORG In-Reply-To: References: <3.0.6.32.19981221160025.008547d0@pop.cantv.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA25529 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:08 PM 21/12/98 -0500, spork wrote: >Well, here's what sendmail does here, it's pretty scary, with those >truncated messages about spwd.db: > >Dec 17 15:42:27 super-g Dec 17 15:42:27sendmail[: NOQUEUE >Dec 17 15:51:11 super-g Dec 17 15:51:11sendmail[: /etc/spwd.db >Dec 17 15:51:11 super-g sendmail[16594]: NOQUEUE: SYSERR(root): Out of >memory!!: Cannot allocate memory >Dec 17 16:30:01 super-g Dec 17 16:30:00sendmail[: /etc/spwd.db >Dec 17 16:30:16 super-g /kernel: pid 20618 (sendmail), uid 0: exited on >signal 11 >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: NOQUEUE >Dec 17 16:30:57 super-g Dec 17 16:30:57sendmail[: /etc/spwd.db > >Charles Agreed. Are your files consistent/sane? I've never seen this before! -lem > >--- >Charles Sprickman >spork@super-g.com > >On Mon, 21 Dec 1998, Luis [iso-8859-1] Muñoz wrote: > >> At 02:00 PM 21/12/98 -0500, spork wrote: >> >FWIW, on a 2.2-stable snap, I started getting this soon after installing >> >KDE. In other words, I was running dangerously low on swap... Dumping >> >128M in the machine fixed the problem. Is this really anything besides a >> >rather confusing way of inetd saying "can't allocate memory"? >> >> I've seen a very similar behavior in sendmail after applying some >> perl related patches. I believe this code is actually in the >> libraries and not in inetd. A free() or realloc() when fed with >> a wrong pointer would output this message to STDERR, which in inetd >> is already pointed to the socket assigned to the process to be fork()'ed. >> >> Killing and restarting inetd fixes this in a 2.2.x machine, but will >> eventually reappear. It definitely is related to vm (not enough vm I >> mean). >> >> Look... >> >> bash-2.01# pwd >> /usr/src/lib/libc >> bash-2.01# egrep 'too high' */*.c >> stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); >> stdlib/malloc.c: wrtwarning("junk pointer, too high to make sense.\n"); >> bash-2.01# egrep 'too low' */*.c >> stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); >> stdlib/malloc.c: wrtwarning("junk pointer, too low to make sense.\n"); >> >> and in stdlib/malloc.c... >> >> static void >> wrtwarning(char *p) >> { >> char *q = " warning: "; >> if (malloc_abort) >> wrterror(p); >> write(STDERR_FILENO, __progname, strlen(__progname)); >> write(STDERR_FILENO, malloc_func, strlen(malloc_func)); >> write(STDERR_FILENO, q, strlen(q)); >> write(STDERR_FILENO, p, strlen(p)); >> } >> >> It would be easy to stop this error, perhaps by some malloc() >> option or via an additional call (or even commenting or >> selective compilation of this function). >> >> Hope this helps. >> >> -lem >> >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 14:12:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02483 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 14:12:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02478 for ; Mon, 21 Dec 1998 14:12:17 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zsDYd-000I4yC; Mon, 21 Dec 1998 17:12:07 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: kernel panic In-Reply-To: <83468.914256883@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 21, 1998 8:14:43 am" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 21 Dec 1998 17:12:06 -0500 (EST) Cc: tom@tomqnx.com, hackers@FreeBSD.ORG, support@opensound.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM914278326-5143-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM914278326-5143-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > Last week, x11amp seemed to work absolutely reliably with the OSS sound > > system. (x11amp -b 1024 on FreeBSD-current with creative AWE-64). > > Hmmm. I just updated this port to the latest version (from, oddly > enough, the OSS folks) and now it works with the stock sound driver. > > It also claims to work with OSS and if that's not the case then you > should definitely get back to the OSS folks about this (at the very > least, their code shouldn't PANIC the system) since they're the one > who created this update in the first place and I'd expect it to Just > Work(tm) with OSS. Let me know what they say, thanks! > > - Jordan > Strange stuff. I cvsup'd again & did a make world and updated to the latest elf version 0.8 of x11amp. Still with OSS... I started x11amp in the background. <----NB 2:03 into the 1st song all sound stopped, and the gui stopped as well. By that I mean the time stayed at 2:03. The system remained stable. att'mt ps.axl.1 at this point. 5 instances of x11amp running. clicked the xbutton at upper right of GUI. GUI disappeared. att'mt ps.axl.2 at this point. 4 instances of x11amp running. did kill -TERM for each of the 4 attm't ps.axl.3 at this point. 1 instance of x11amp running. did kill -KILL for the x11amp as originating user and as root. attm't ps.axl.4 at this point. 1 instance of x11amp still running. attm't soundon.log contains dmesg from the same boot. --------------------- At this point, I rebooted the machine and started x11amp in the foreground. 10 seconds into the exact same song, the whole system seized/halted. X still up. No response to mouse movement. No sound. System will not respond to pings. The first time I touched a key on the keyboard, The system rebooted immediately. --------------------- I have been coughing so bad I haven't slept since yesterday AM. I will sleep a bit then try all this with the standard sound package, and let y'all know how it went... If anyone has special tests/procedures they would like me to try, send e-mail. Regards, Tom V 0.7 aout P.S. after a cvsup done last week, x11amp -b 1024 worked great with OSS. Some change introduced to FreeBSD-current within the past week has apparently screwed the pooch. Maybe OSS just needs to be recompiled?? Maybe much worse than that... --ELM914278326-5143-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=ps.axl.1 Content-Description: ps.axl.1 Content-Transfer-Encoding: 7bit UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 496 260 wait Is ?? 0:00.01 /sbin/init - 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.00 (pagedaemon 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 0:00.25 (syncer) 0 26 1 35 18 0 204 88 pause Is ?? 0:00.00 adjkerntz -i 0 91 1 0 2 0 820 536 select Ss ?? 0:00.17 syslogd 1 103 1 2 2 0 800 464 select Is ?? 0:00.00 portmap 0 136 1 0 2 0 860 588 select Ss ?? 0:00.06 inetd 0 139 1 2 10 0 992 576 nanslp Ss ?? 0:00.03 cron 0 143 1 30 2 0 832 620 select Is ?? 0:00.02 lpd 0 146 1 0 2 0 1240 988 select Is ?? 0:00.01 /usr/sbin/se 0 195 1 15 2 0 1368 908 select Is ?? 0:00.00 /usr/local/s 1000 251 1 0 2 0 1308 932 select Ss ?? 0:00.01 /usr/local/b 0 274 273 32 2 0 13220 12328 select S ?? 2:58.89 /usr/X11R6/b 1000 324 1 0 2 0 1308 948 select Is ?? 0:00.01 /usr/local/b 1000 319 314 0 10 0 1496 1032 wait Ss p0 0:00.14 -bash (bash) 1000 350 319 14 31 0 2884 2352 - R p0 0:53.12 x11amp -b 10 1000 351 350 0 10 0 3476 2388 nanslp S p0 0:27.29 x11amp -b 10 1000 357 351 2 10 0 2376 1256 nanslp S p0 0:02.33 x11amp -b 10 1000 358 351 74 10 0 3476 1352 nanslp S p0 4:38.72 x11amp -b 10 1000 359 351 0 2 0 3476 2364 - R p0 0:01.47 x11amp -b 10 1000 702 319 1 28 0 408 244 - R+ p0 0:00.00 ps -axl 1000 318 309 0 10 0 772 412 nanslp Ss+ p1 0:00.50 tail -f /hom 1000 244 1 0 10 0 1512 1008 wait Is v0 0:00.15 -bash (bash) 1000 268 244 0 10 0 508 320 wait I+ v0 0:00.01 /bin/sh /usr 1000 273 268 0 10 0 1864 1052 wait I+ v0 0:00.03 xinit /home/ 1000 277 273 0 10 0 508 324 wait I v0 0:00.01 sh /home/tom 1000 284 1 0 18 0 840 584 pause S v0 0:00.03 /usr/local/b 1000 285 277 0 2 0 2292 1988 select I v0 0:00.16 xsm 1000 289 1 0 2 0 2088 1764 select S v0 0:02.86 fvwm2 1000 291 1 0 2 0 1944 1532 select S v0 0:00.48 smproxy 1000 293 1 0 2 0 2212 1832 select I v0 0:00.10 xpostit+ 1000 295 1 0 2 0 2684 2280 select I v0 0:00.77 xman 0 297 1 0 2 0 3684 3340 select S v0 0:01.17 xmcd 1000 299 1 0 2 0 5248 4880 select S v0 0:05.78 tkdesksh /us 1000 308 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c s 0 309 308 0 2 0 2416 2084 select I v0 0:00.24 xterm -e tai 1000 310 289 0 2 0 1604 928 select I v0 0:00.11 /usr/X11R6/l 1000 311 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c x 0 314 311 0 2 0 2420 2124 select S v0 0:00.42 xterm 1000 325 289 0 2 0 1580 924 select S v0 0:00.09 /usr/X11R6/l 1000 330 1 0 2 0 1996 1596 select S v0 0:01.10 xeyes 1000 331 1 0 2 0 2120 1744 select I v0 0:00.08 xclock 1000 332 1 0 2 0 1576 952 select S v0 0:01.71 asclock -pos 1000 333 1 0 2 0 1920 1508 select S v0 0:00.06 coolmail -e 1000 419 1 0 2 0 3068 2620 select S v0 0:01.42 plan 0 245 1 0 3 0 824 576 ttyin Is+ v1 0:00.01 /usr/libexec 0 246 1 0 3 0 824 576 ttyin Is+ v2 0:00.01 /usr/libexec --ELM914278326-5143-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=ps.axl.2 Content-Description: ps.axl.2 Content-Transfer-Encoding: 7bit UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 496 260 wait Is ?? 0:00.01 /sbin/init - 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.00 (pagedaemon 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 0:00.26 (syncer) 0 26 1 35 18 0 204 88 pause Is ?? 0:00.00 adjkerntz -i 0 91 1 0 2 0 820 536 select Ss ?? 0:00.17 syslogd 1 103 1 2 2 0 800 464 select Is ?? 0:00.00 portmap 0 136 1 0 2 0 860 588 select Ss ?? 0:00.06 inetd 0 139 1 0 10 0 992 616 nanslp Ss ?? 0:00.03 cron 0 143 1 30 2 0 832 620 select Is ?? 0:00.02 lpd 0 146 1 0 2 0 1240 988 select Is ?? 0:00.01 /usr/sbin/se 0 195 1 15 2 0 1368 908 select Is ?? 0:00.00 /usr/local/s 1000 251 1 0 2 0 1308 932 select Ss ?? 0:00.01 /usr/local/b 0 274 273 1 2 0 10740 9848 select S ?? 3:03.87 /usr/X11R6/b 1000 324 1 0 2 0 1308 948 select Is ?? 0:00.01 /usr/local/b 1000 319 314 1 10 0 1496 1024 wait Ss p0 0:00.17 -bash (bash) 1000 351 1 0 10 0 3476 2376 nanslp S p0 0:27.41 x11amp -b 10 1000 357 351 0 10 0 2376 1240 nanslp S p0 0:02.44 x11amp -b 10 1000 358 351 67 10 0 3476 1348 nanslp S p0 5:02.12 x11amp -b 10 1000 359 351 0 2 0 3476 2352 - R p0 0:01.47 x11amp -b 10 1000 721 319 0 28 0 408 244 - R+ p0 0:00.00 ps -axl 1000 318 309 0 10 0 772 412 nanslp Ss+ p1 0:00.54 tail -f /hom 1000 244 1 0 10 0 1512 1008 wait Is v0 0:00.15 -bash (bash) 1000 268 244 0 10 0 508 320 wait I+ v0 0:00.01 /bin/sh /usr 1000 273 268 0 10 0 1864 1052 wait I+ v0 0:00.03 xinit /home/ 1000 277 273 0 10 0 508 324 wait I v0 0:00.01 sh /home/tom 1000 284 1 0 18 0 840 584 pause I v0 0:00.04 /usr/local/b 1000 285 277 0 2 0 2292 1988 select I v0 0:00.16 xsm 1000 289 1 0 2 0 2088 1764 select S v0 0:02.88 fvwm2 1000 291 1 0 2 0 1944 1532 select S v0 0:00.48 smproxy 1000 293 1 0 2 0 2212 1832 select I v0 0:00.11 xpostit+ 1000 295 1 0 2 0 2684 2280 select I v0 0:00.77 xman 0 297 1 0 2 0 3684 3340 select S v0 0:01.21 xmcd 1000 299 1 0 2 0 5260 4896 select S v0 0:06.45 tkdesksh /us 1000 308 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c s 0 309 308 0 2 0 2416 2084 select I v0 0:00.24 xterm -e tai 1000 310 289 0 2 0 1604 928 select I v0 0:00.11 /usr/X11R6/l 1000 311 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c x 0 314 311 0 2 0 2420 2124 select S v0 0:00.48 xterm 1000 325 289 0 2 0 1580 924 select S v0 0:00.09 /usr/X11R6/l 1000 330 1 0 2 0 1996 1596 select S v0 0:01.16 xeyes 1000 331 1 0 2 0 2120 1744 select I v0 0:00.08 xclock 1000 332 1 0 2 0 1576 952 select S v0 0:01.84 asclock -pos 1000 333 1 0 2 0 1920 1508 select S v0 0:00.06 coolmail -e 1000 419 1 0 2 0 3068 2620 select S v0 0:01.42 plan 0 245 1 0 3 0 824 576 ttyin Is+ v1 0:00.01 /usr/libexec 0 246 1 0 3 0 824 576 ttyin Is+ v2 0:00.01 /usr/libexec --ELM914278326-5143-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=ps.axl.3 Content-Description: ps.axl.3 Content-Transfer-Encoding: 7bit UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 496 260 wait Is ?? 0:00.01 /sbin/init - 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.00 (pagedaemon 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 0:00.29 (syncer) 0 26 1 35 18 0 204 88 pause Is ?? 0:00.00 adjkerntz -i 0 91 1 0 2 0 820 536 select Ss ?? 0:00.18 syslogd 1 103 1 2 2 0 800 464 select Is ?? 0:00.00 portmap 0 136 1 0 2 0 860 588 select Ss ?? 0:00.06 inetd 0 139 1 0 10 0 992 616 nanslp Is ?? 0:00.03 cron 0 143 1 30 2 0 832 620 select Is ?? 0:00.02 lpd 0 146 1 0 2 0 1240 972 select Is ?? 0:00.01 /usr/sbin/se 0 195 1 15 2 0 1368 908 select Is ?? 0:00.00 /usr/local/s 1000 251 1 0 2 0 1308 932 select Is ?? 0:00.01 /usr/local/b 0 274 273 1 2 0 10740 9848 select S ?? 3:04.39 /usr/X11R6/b 1000 324 1 0 2 0 1308 948 select Ss ?? 0:00.02 /usr/local/b 1000 319 314 1 10 0 1496 1032 wait Ss p0 0:00.21 -bash (bash) 1000 359 1 0 2 0 3476 2296 - R p0 0:01.47 x11amp -b 10 1000 745 319 2 28 0 408 244 - R+ p0 0:00.00 ps -axl 1000 318 309 0 10 0 772 412 nanslp Ss+ p1 0:00.59 tail -f /hom 1000 244 1 0 10 0 1512 1008 wait Is v0 0:00.15 -bash (bash) 1000 268 244 0 10 0 508 320 wait I+ v0 0:00.01 /bin/sh /usr 1000 273 268 0 10 0 1864 1052 wait I+ v0 0:00.03 xinit /home/ 1000 277 273 0 10 0 508 324 wait I v0 0:00.01 sh /home/tom 1000 284 1 0 18 0 840 584 pause I v0 0:00.04 /usr/local/b 1000 285 277 0 2 0 2292 1988 select I v0 0:00.16 xsm 1000 289 1 0 2 0 2088 1764 select I v0 0:02.89 fvwm2 1000 291 1 0 2 0 1944 1532 select I v0 0:00.48 smproxy 1000 293 1 0 2 0 2212 1832 select I v0 0:00.11 xpostit+ 1000 295 1 0 2 0 2684 2280 select I v0 0:00.77 xman 0 297 1 0 2 0 3684 3340 select S v0 0:01.24 xmcd 1000 299 1 0 2 0 5268 4904 select S v0 0:07.18 tkdesksh /us 1000 308 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c s 0 309 308 0 2 0 2416 2084 select I v0 0:00.24 xterm -e tai 1000 310 289 0 2 0 1604 928 select I v0 0:00.11 /usr/X11R6/l 1000 311 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c x 0 314 311 0 2 0 2420 2124 select S v0 0:00.55 xterm 1000 325 289 0 2 0 1580 924 select I v0 0:00.09 /usr/X11R6/l 1000 330 1 0 2 0 1996 1596 select S v0 0:01.22 xeyes 1000 331 1 0 2 0 2120 1744 select S v0 0:00.08 xclock 1000 332 1 0 2 0 1576 952 select S v0 0:01.99 asclock -pos 1000 333 1 0 2 0 1920 1508 select S v0 0:00.07 coolmail -e 1000 419 1 0 2 0 3068 2620 select S v0 0:01.43 plan 0 245 1 0 3 0 824 576 ttyin Is+ v1 0:00.01 /usr/libexec 0 246 1 0 3 0 824 576 ttyin Is+ v2 0:00.01 /usr/libexec --ELM914278326-5143-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=ps.axl.4 Content-Description: ps.axl.4 Content-Transfer-Encoding: 7bit UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 10 0 496 260 wait Is ?? 0:00.01 /sbin/init - 0 2 0 0 -18 0 0 0 psleep DL ?? 0:00.00 (pagedaemon 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 18 0 0 0 syncer DL ?? 0:00.39 (syncer) 0 26 1 35 18 0 204 88 pause Is ?? 0:00.00 adjkerntz -i 0 91 1 0 2 0 820 536 select Ss ?? 0:00.18 syslogd 1 103 1 2 2 0 800 464 select Is ?? 0:00.00 portmap 0 136 1 0 2 0 860 588 select Ss ?? 0:00.07 inetd 0 139 1 0 10 0 992 616 nanslp Is ?? 0:00.04 cron 0 143 1 30 2 0 832 620 select Is ?? 0:00.02 lpd 0 146 1 0 2 0 1240 972 select Is ?? 0:00.01 /usr/sbin/se 0 195 1 15 2 0 1368 908 select Is ?? 0:00.00 /usr/local/s 1000 251 1 0 2 0 1308 932 select Is ?? 0:00.02 /usr/local/b 0 274 273 1 2 0 10740 9848 select S ?? 3:06.05 /usr/X11R6/b 1000 324 1 0 2 0 1308 948 select Ss ?? 0:00.02 /usr/local/b 1000 319 314 0 10 0 1504 1040 wait Is p0 0:00.26 -bash (bash) 1000 359 1 0 2 0 3476 2296 - R p0 0:01.47 x11amp -b 10 0 834 319 0 10 0 1504 1040 wait S p0 0:00.09 su (bash) 0 845 834 1 28 0 408 244 - R+ p0 0:00.00 ps -axl 1000 318 309 0 10 0 772 412 nanslp Ss+ p1 0:00.81 tail -f /hom 1000 244 1 0 10 0 1512 1008 wait Is v0 0:00.15 -bash (bash) 1000 268 244 0 10 0 508 320 wait I+ v0 0:00.01 /bin/sh /usr 1000 273 268 0 10 0 1864 1052 wait I+ v0 0:00.03 xinit /home/ 1000 277 273 0 10 0 508 324 wait I v0 0:00.01 sh /home/tom 1000 284 1 0 18 0 840 584 pause I v0 0:00.04 /usr/local/b 1000 285 277 0 2 0 2292 1988 select I v0 0:00.16 xsm 1000 289 1 0 2 0 2088 1764 select I v0 0:02.94 fvwm2 1000 291 1 0 2 0 1944 1532 select I v0 0:00.49 smproxy 1000 293 1 0 2 0 2212 1832 select I v0 0:00.11 xpostit+ 1000 295 1 0 2 0 2684 2280 select I v0 0:00.77 xman 0 297 1 0 2 0 3684 3340 select S v0 0:01.37 xmcd 1000 299 1 0 2 0 5276 4912 select S v0 0:08.85 tkdesksh /us 1000 308 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c s 0 309 308 0 2 0 2416 2084 select I v0 0:00.24 xterm -e tai 1000 310 289 0 2 0 1604 928 select I v0 0:00.11 /usr/X11R6/l 1000 311 289 10 10 0 504 336 wait I v0 0:00.01 /bin/sh -c x 0 314 311 0 2 0 2420 2124 select S v0 0:00.68 xterm 1000 325 289 0 2 0 1580 924 select I v0 0:00.09 /usr/X11R6/l 1000 330 1 0 2 0 1996 1596 select S v0 0:01.51 xeyes 1000 331 1 0 2 0 2120 1744 select S v0 0:00.08 xclock 1000 332 1 0 2 0 1576 952 select S v0 0:02.61 asclock -pos 1000 333 1 0 2 0 1920 1508 select S v0 0:00.08 coolmail -e 1000 419 1 0 2 0 3068 2620 select S v0 0:01.45 plan 0 245 1 0 3 0 824 576 ttyin Is+ v1 0:00.01 /usr/libexec 0 246 1 0 3 0 824 576 ttyin Is+ v2 0:00.01 /usr/libexec --ELM914278326-5143-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=soundon.log Content-Description: soundon.log Content-Transfer-Encoding: 7bit Starting OSS/FreeBSD Mon Dec 21 14:59:21 EST 1998 2:59PM up 1 min, 0 users, load averages: 0.06, 0.02, 0.00 Module loaded as ID 0 ======= config ===== # Use soundconf to edit this file. /SECUREAUDIO OFF /IRQEXCLUDE 3 4 /DMAEXCLUDE 2 -CTL00C1 #Creative Sound Blaster AWE64 (type-2) /CONTROL run ~/sfxload ~/synthgm.sf2 /PNPDEV CTL0042 P220 P300 P388 I10 D3 D5 /PNPDEV CTL0022 P620 Pa20 Pe20 SBPNP OPNP P220 I10 D3 d5 SBMPU OPNP P300 OPL3 OPNP P388 PNP ============ Resources for PnP card #0 0000: 0e 8c 00 c1 94 e0 41 16 0e 0a 10 10 82 15 00 43 0010: 72 65 61 74 69 76 65 20 53 42 20 41 57 45 36 34 0020: 20 50 6e 50 15 0e 8c 00 42 00 82 05 00 41 75 64 0030: 69 6f 31 00 22 20 00 2a 02 08 2a 20 12 47 01 20 0040: 02 20 02 01 10 47 01 30 03 30 03 01 02 47 01 88 0050: 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 2a e0 12 0060: 47 01 20 02 80 02 20 10 47 01 00 03 30 03 30 02 0070: 47 01 88 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 0080: 2a e0 12 47 01 20 02 80 02 20 10 47 01 00 03 30 0090: 03 30 02 31 01 22 a0 06 2a 0b 08 2a e0 12 47 01 00a0: 20 02 80 02 20 10 31 01 22 a0 06 2a 0b 08 47 01 00b0: 20 02 80 02 20 10 47 01 00 03 30 03 30 02 47 01 00c0: 88 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 47 01 00d0: 20 02 80 02 20 10 47 01 00 03 30 03 30 02 31 01 00e0: 22 a0 06 2a 0b 08 47 01 20 02 80 02 20 10 31 02 00f0: 22 a0 06 2a 0b 08 2a e0 12 47 01 20 02 80 02 20 0100: 10 47 01 00 03 30 03 10 02 47 01 88 03 94 03 04 0110: 04 38 15 0e 8c 70 02 00 1c 41 d0 b0 2f 82 04 00 0120: 47 61 6d 65 31 00 47 01 00 02 00 02 01 08 31 01 0130: 47 01 00 02 08 02 08 08 38 15 0e 8c 00 22 00 82 0140: 09 00 57 61 76 65 54 61 62 6c 65 31 00 47 01 20 0150: 06 20 06 01 04 31 01 47 01 20 06 80 06 20 04 38 0160: 79 11 ==================== The following OSS options are required for your current hardware configuration: AWE Remember to select them while ordering the permanent OSS license. OSS/FreeBSD 3.9.1i (C) 4Front Technologies 1996-1998 License serial number: E00000008 Open Sound System is licensed for evaluation purposes only. License will expire after: 05/1999 Options: ALL Kernel: FreeBSD 3.0-CURRENT #6: Mon Dec 21 14:09:09 EST 1998 tom@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Card config: Generic PnP support Sound Blaster PnP at 0x220 irq 10 drq 3,5 OPL-2/OPL-3 FM at 0x388 SB MPU-401 at 0x300 irq 10 Emu 8000 MIDI Engine at 0x620 Audio devices: 0: Creative SB AWE64 PnP (4.16) (DUPLEX) 1: SB secondary device (DUPLEX) Synth devices: 0: Yamaha OPL-3 1: AWE32-0.4.2 (RAM512k) Midi devices: 0: Sound Blaster 16 Timers: 0: System clock Mixers: 0: Sound Blaster 1: AWE32 Equalizer ========== dmesg printout follows ======== Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #6: Mon Dec 21 14:09:09 EST 1998 tom@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Calibrating clock(s) ... TSC clock: 200453044 Hz, i8254 clock: 1193174 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200453044 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00273000 - 0x03ff5fff, 64499712 bytes (15747 pages) config> quit avail memory = 62722048 (61252K bytes) Found BIOS32 Service Directory header at 0xf00f9a20 Entry = 0xf04e0 (0xf00f04e0) Rev = 0 Len = 1 PCI BIOS entry at 0x510 DMI header at 0xf00f52a0 Version 2.0 Table at 0xf52ba, 33 entries, 1044 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcf10 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e000, size 4 ide_pci0: rev 0x01 on pci0.1.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000e002 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e00a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=3 map[0]: type 4, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.1.3 found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, locked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175623463 bytes/sec bzero() bandwidth = 88417329 bytes/sec joy0 at 0x201 on isa joy0: joystick imasks: bio c008c040, tty c00710b2, net c00710b2 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c00710b2, net c00710b2 bpf: lo0 attached Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates OSS/FreeBSD loading, address = f45ab020 --ELM914278326-5143-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 16:57:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22353 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 16:57:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22320; Mon, 21 Dec 1998 16:57:07 -0800 (PST) (envelope-from y912k@eudoramail.com) Received: from suna.pl-net.pl (suna.pl-net.pl [193.91.4.1]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id QAA10788; Mon, 21 Dec 1998 16:27:38 -0800 (PST) Message-Id: <199812220028.BAA04425@suna.pl-net.pl> Received: from james by suna.pl-net.pl with ESMTP (8.8.5/GEN-1.0.18) via EUnet for freefall.cdrom.com id BAA04425; Tue, 22 Dec 1998 01:28:54 +0100 (MET) From: "Steve" Subject: Between our.. To: jfjhj@888h.net X-Mailer: Microsoft Outlook Express 4.72.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V(null).1712.3 Mime-Version: 1.0 Date: Mon, 21 Dec 1998 18:42:18 -0500 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 QAA22322 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NO TRICKS - IT'S FREE! Process all major credit cards on your web site. NO MONTHLY COSTS, NO TRANSACTION FEES. CHECK IT OUT. You get: - Virtual Terminal for phone/fax/mail orders - Email receipt - Recurring billing feature - Password generation for membership sites - Automatic batch closing - Address Verification Service (AVS) - Backoffice to access account history - Remote mode - Interface for all major shopping carts - Installation included For our free information package just reply to: mailto:ccard@topchat.com?subject=more_info If you are interested in becoming an authorized agent please reply to: mailto:ccard@topchat.com?subject=agent If you wish to be removed from our mailing list please reply to: mailto:fltr9@yahoo.com?subject=remove To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 17:15:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24494 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 17:15:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24480; Mon, 21 Dec 1998 17:15:17 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA00890; Tue, 22 Dec 1998 11:44:51 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812211425.PAA48229@qix> Date: Tue, 22 Dec 1998 11:47:54 +1030 (CST) From: "Daniel O'Connor" To: Jean-Marc Zucconi Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Jean-Marc Zucconi wrote: > You looked in the MXTC documentation. The interrupt routing is > described in the PIIX4 documentation (PCI-TO-ISA/IDE XCELERATOR), > 20956201.pdf. OK, I'll have a look at that one :) I thought that it wasn't relevant. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 17:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24924 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 17:18:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24917 for ; Mon, 21 Dec 1998 17:18:29 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA00920; Tue, 22 Dec 1998 11:47:28 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812211622.JAA01401@fast.cs.utah.edu> Date: Tue, 22 Dec 1998 11:50:31 +1030 (CST) From: "Daniel O'Connor" To: Kevin Van Maren Subject: Re: PCI IRQ mappings Cc: freebsd-hackers@FreeBSD.ORG, mike@smith.net.au Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-98 Kevin Van Maren wrote: [ useful PCI IRQ info deleted ] > If the hardware is broken, complain bitterly to the vendor. If the > driver is broken, complain bitterly to the driver writer. OK.. Next question, how do I write a driver that shares interrupts correctly? Just make sure it checks the cards IRQ register? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 17:32:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26968 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 17:32:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26952 for ; Mon, 21 Dec 1998 17:32:12 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id CAA19526; Tue, 22 Dec 1998 02:32:07 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id CAA22260; Tue, 22 Dec 1998 02:32:06 +0100 (MET) Message-ID: <19981222023206.L14124@follo.net> Date: Tue, 22 Dec 1998 02:32:06 +0100 From: Eivind Eklund To: Kaleb Keithley , hackers@FreeBSD.ORG Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. References: <199812191330.IAA26067@sunoco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812191330.IAA26067@sunoco>; from Kaleb Keithley on Sat, Dec 19, 1998 at 08:30:13AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 19, 1998 at 08:30:13AM -0500, Kaleb Keithley wrote: > > My 3.0-RELEASE system, up some 17 days, is now doing this when I telnet > (or ping, or anything else that uses inetd) to it. (I don't know how long > it's been like this, perhaps it explains why my outgoing email seem to > be being dropped on the floor. > > Do I remember correctly that there was some fix for this made shortly > before 3.0-RELEASE? Did the fix not make it into 3.0-RELEASE? Before > I go snag the LaG inetd sources, will that fix the problem? This has been fixed recently (last week, I think). Not fixed for 3.0-RELEASE. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 17:45:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28908 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 17:45:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gras-varg.worldgate.com (gras-varg.worldgate.com [198.161.84.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28892 for ; Mon, 21 Dec 1998 17:44:59 -0800 (PST) (envelope-from skafte@gras-varg.worldgate.com) Received: (from skafte@localhost) by gras-varg.worldgate.com (8.9.1a/8.9.1) id SAA19713; Mon, 21 Dec 1998 18:44:36 -0700 (MST) Date: Mon, 21 Dec 1998 18:44:36 -0700 From: Greg Skafte To: Marc van Kempen Cc: hackers@FreeBSD.ORG Subject: Re: Anyone with DHCP experience Message-ID: <19981221184436.I15812@gras-varg.worldgate.com> References: <199812211024.LAA19441@bowtie.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812211024.LAA19441@bowtie.nl>; from Marc van Kempen on Mon, Dec 21, 1998 at 11:24:15AM +0100 Organization: WorldGate Inc. X-PGP-Fingerprint: 42 9C 2C A8 4D 2B C9 C4 7D B6 00 B0 50 47 20 97 X-URL: http://gras-varg.worldgate.com/~skafte Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG not haveing any issues with isc-dhcp2 on 509b's either as a server or a client Quoting Marc van Kempen (marc@bowtie.nl) On Subject: Anyone with DHCP experience Date: Mon, Dec 21, 1998 at 11:24:15AM +0100 > > Hi, > > I'm having some troubles getting DHCP to work with my 3c509b network > card. I know this card is not among the best supported, but I'm forced > to use this card by my cable network provider. > > I have used both wide-dhcp and isc-dhcp, but only succeeded so far > with wide-dhcp. > > I have had some success, but now it seems to refuse to come back up. > When I look at the packets floating by with tcpdump, it seems the > client sends out the request (DHCPDISCOVER) correctly, but then > gets a response back that contains a remark about an incorrect cksum. > > I'm not fluent at reading tcpdump output, but this is what it looks > like. > > Now, does this ring a bell for someone? > > I stronly suspect the driver for the 3c509b, but I'm tied to it, or > could I use another card, and sent the mac address of the > 3c509b with the DHCP request? > Isc-dhcp seems to have that capability, but sends out its broadcast > addresses using 'ifconfig ep0 0.0.0.0 broadcast 255.255.255.255' and > that results in a send error when I run it (the latest isc-dhcp from > december 4) > > Oh, and to rule out any dhcp server configurations errors, Win95 comes > up with no problems at all (assuming this means anything at all ;-)) > > Regards, > 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 > ---------------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Email: skafte@worldgate.com Voice: +403 413 1910 Fax: +403 421 4929 #575 Sun Life Place * 10123 99 Street * Edmonton, AB * Canada * T5J 3H1 -- -- When things can't get any worse, they simplify themselves by getting a whole lot worse then complicated. A complete and utter disaster is the simplest thing in the world; it's preventing one that's complex. (Janet Morris) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 18:42:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06017 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 18:42:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06011 for ; Mon, 21 Dec 1998 18:42:17 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id SAA16786 for ; Mon, 21 Dec 1998 18:42:16 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id VAA19849 for ; Mon, 21 Dec 1998 21:42:18 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id WAA26303 for ; Mon, 21 Dec 1998 22:29:33 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id VAA21066 for freebsd-hackers@freefall.cdrom.com; Mon, 21 Dec 1998 21:43:24 -0500 (EST) Date: Mon, 21 Dec 1998 21:43:24 -0500 (EST) From: Thomas David Rivers Message-Id: <199812220243.VAA21066@lakes.dignus.com> To: freebsd-hackers@freefall.cdrom.com Subject: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try the following on a 3.0-RELEASE system, under the bourne shell: while true do sleep 2 done You'll quickly discover there's no way to interrupt it (i.e. control-C if that's your intr character.) But, individually, the two ideas (the while loop and the sleep) are quite interruptable. That is, you can interrupt this: while true do done And, you can interrupt this: sleep 10 But, I can't interrupt the combination; even when I hold down control-C (which, should eventually be in the 'right place at the right time' to interrupt the sleep followed by another control-C to interrupt the while loop. Even a ^\ (my quit character) won't stop the loop; it does get sleep to dump core.. but the loop quickly (too quickly apparently) starts up another sleep. I'd have to guess it to be a shell bug... seems like it could affect trap behaviour as well. This "interesting" phenomenon doesn't seem to be present on a 2.2.X system. Could some other people with 3.0 (RELEASE or later) try it out... if it's a consistent problem; I'll submit a pr on it. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 19:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08467 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 19:04:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08462 for ; Mon, 21 Dec 1998 19:04:37 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id TAA18459 for ; Mon, 21 Dec 1998 19:04:36 -0800 (PST) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA01542; Tue, 22 Dec 1998 13:33:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA08709; Tue, 22 Dec 1998 13:33:54 +1030 (CST) Message-ID: <19981222133354.C85005@freebie.lemis.com> Date: Tue, 22 Dec 1998 13:33:54 +1030 From: Greg Lehey To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <199812220243.VAA21066@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812220243.VAA21066@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 21, 1998 at 09:43:24PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 21 December 1998 at 21:43:24 -0500, Thomas David Rivers wrote: > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > while true > do > sleep 2 > done > > You'll quickly discover there's no way to interrupt it (i.e. control-C > if that's your intr character.) Right. It's obviously a sh problem; it works fine under bash. How about a PR (with a solution if possible :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 21 21:41:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29866 for freebsd-hackers-outgoing; Mon, 21 Dec 1998 21:41:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29859 for ; Mon, 21 Dec 1998 21:41:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id VAA65066; Mon, 21 Dec 1998 21:40:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812220540.VAA65066@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: Kevin Van Maren , freebsd-hackers@FreeBSD.ORG, mike@smith.net.au Subject: Re: PCI IRQ mappings In-reply-to: Your message of "Tue, 22 Dec 1998 11:50:31 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Dec 1998 21:40:15 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 21-Dec-98 Kevin Van Maren wrote: > > [ useful PCI IRQ info deleted ] > > If the hardware is broken, complain bitterly to the vendor. If the > > driver is broken, complain bitterly to the driver writer. > OK.. > > Next question, how do I write a driver that shares interrupts correctly? Just make sure > it checks the cards IRQ register? You have to check that your card has set the interrupt bit if not then return. There is no PCI standard for specifying where can you check for interrupt active in a PCI device. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 00:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16173 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 00:14:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16155 for ; Tue, 22 Dec 1998 00:14:19 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id KAA05184; Tue, 22 Dec 1998 10:13:26 +0200 (SAST) Received: by citadel via recvmail id 5124; Tue Dec 22 10:13:07 1998 From: Graham Wheeler Message-Id: <199812220820.KAA20421@cdsec.com> Subject: Re: inetd in realloc(): warning: junk pointer, too low to make sense. To: dhw@whistle.com (David Wolfskill) Date: Tue, 22 Dec 1998 10:20:47 +0200 (SAT) Cc: hackers@FreeBSD.ORG In-Reply-To: <199812211913.LAA14214@pau-amma.whistle.com> from "David Wolfskill" at Dec 21, 98 11:13:49 am X-Mailer: ELM [version 2.4 PL25-h4.1] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >There is an open problem report, bin/8183, about this. I have just received > >mail saying that the fix I posted changes the signal mask for child processes > >and breaks Amanda; I haven't had a chance to look at this yet, and have not > >experienced any problems myself. You may want to try the patches and see how > >it goes. > > It's still a little early to tell for sure, but things with amanda & 3.0 > seem to be no worse than they were before Matt's first patch (that > caused inet's child processes (such as amandad) to be forked off with > interrupts blocked), and may actually be better. I think that the Amanda problem was actually with that patch, and not with mine. I was sent a test program to illustrate the break, and ran it on the unpatched inetd and then again after applying my patch, and the signal masks in the child were the same in each case (no signals blocked). We have a number of clients running our firewalls with my patch applied to inetd and no-one has reported any problems yet. The standard disclaimers apply, of course ;-). The idea of using a pipe to hold flags for signals to be processed was not mine; Don Lewis and Warner Losh suggested it to me, so they should take much of the credit for the patch. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Internet/Intranet Network Specialists Data Security Products WWW: http://www.cdsec.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 01:20:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21691 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 01:20:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21683 for ; Tue, 22 Dec 1998 01:20:22 -0800 (PST) (envelope-from marc@bowtie.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.8.8/8.8.8) with IAEhv.nl id KAA15532; Tue, 22 Dec 1998 10:20:07 +0100 (MET) (envelope-from marc@bowtie.nl) Received: from localhost (localhost [127.0.0.1]) by bowtie.nl (8.8.8/8.8.8) with ESMTP id KAA18855; Tue, 22 Dec 1998 10:19:39 +0100 (CET) (envelope-from marc@bowtie.nl) Message-Id: <199812220919.KAA18855@bowtie.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Skafte cc: hackers@FreeBSD.ORG Subject: Re: Anyone with DHCP experience In-reply-to: skafte's message of Mon, 21 Dec 1998 18:44:36 -0700. <19981221184436.I15812@gras-varg.worldgate.com> Reply-to: marc@bowtie.nl Date: Tue, 22 Dec 1998 10:19:39 +0100 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > not haveing any issues with isc-dhcp2 on 509b's either as a server or a > client > That's odd, after hacking the kernel to overwrite the MAC address of the NE2000 clone that I'm using now, with that of the 3c509b everything started working immediately! 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 ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 03:28:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA01970 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 03:28:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA01963 for ; Tue, 22 Dec 1998 03:28:47 -0800 (PST) (envelope-from kaleb@ics.com) Received: from kaleb.keithley.belmont.ma.us (pmdialin1.ics.com [140.186.40.175]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id GAA13428; Tue, 22 Dec 1998 06:28:37 -0500 (EST) Received: from kaleb.keithley.belmont.ma.us (localhost [127.0.0.1]) by kaleb.keithley.belmont.ma.us (8.9.1/8.9.1) with SMTP id HAA05238; Tue, 22 Dec 1998 07:53:07 -0500 (EST) (envelope-from kaleb@ics.com) Message-ID: <367F9630.13728473@ics.com> Date: Tue, 22 Dec 1998 07:53:04 -0500 From: "Kaleb S. KEITHLEY" Reply-To: kaleb@ics.com Organization: Integrated Computer Solutions X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG CC: kaleb@ics.com Subject: Euro support part 2 Content-Type: multipart/mixed; boundary="------------2C67412E284797A9500F9F30" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------2C67412E284797A9500F9F30 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The attached patch adds more changes necessary to support for the Euro. Specifically it adds the following: o) Adds creation of /usr/share/locale/*.DIS_8859-15 subdirs to /usr/src/etc/mtree/BSD.usr.dist. o) Adds installation of LC_TIME specs for 8859-15 locales (symlinks from 8859-1 version) to /usr/src/share/timedef/data/Makefile o) Adds an 8859-15 charmap and LC_COLLATE specifications to /usr/src/usr.bin/colldef/data. Adds installation of generated LC_COLLATE files to the Makefile. I don't recall that 2.x systems needed LC_TIME and LC_COLLATE. The first item is definitely necessary on both 2.x and 3.0 systems. The second two items may be optional on a 2.x system. -- Kaleb --------------2C67412E284797A9500F9F30 Content-Type: text/plain; charset=us-ascii; name="euro.patch2" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="euro.patch2" *** /usr/src/etc/mtree/BSD.usr.dist.orig Mon Dec 21 21:24:49 1998 --- /usr/src/etc/mtree/BSD.usr.dist Mon Dec 21 21:22:56 1998 *************** *** 401,442 **** --- 401,476 ---- locale da_DK.ISO_8859-1 .. + da_DK.DIS_8859-15 + .. de_AT.ISO_8859-1 .. + de_AT.DIS_8859-15 + .. de_CH.ISO_8859-1 .. + de_CH.DIS_8859-15 + .. de_DE.ISO_8859-1 .. + de_DE.DIS_8859-15 + .. en_AU.ISO_8859-1 .. + en_AU.DIS_8859-15 + .. en_CA.ISO_8859-1 .. + en_CA.DIS_8859-15 + .. en_GB.ISO_8859-1 .. + en_GB.DIS_8859-15 + .. en_US.ISO_8859-1 .. + en_US.DIS_8859-15 + .. es_ES.ISO_8859-1 .. + es_ES.DIS_8859-15 + .. fi_FI.ISO_8859-1 .. + fi_FI.DIS_8859-15 + .. fr_BE.ISO_8859-1 .. + fr_BE.DIS_8859-15 + .. fr_CA.ISO_8859-1 .. + fr_CA.DIS_8859-15 + .. fr_CH.ISO_8859-1 .. + fr_CH.DIS_8859-15 + .. fr_FR.ISO_8859-1 .. + fr_FR.DIS_8859-15 + .. hr_HR.ISO_8859-2 .. hu_HU.ISO_8859-2 .. is_IS.ISO_8859-1 .. + is_IS.DIS_8859-15 + .. it_CH.ISO_8859-1 .. + it_CH.DIS_8859-15 + .. it_IT.ISO_8859-1 .. + it_IT.DIS_8859-15 + .. ja_JP.EUC .. ja_JP.SJIS *************** *** 447,464 **** --- 481,508 ---- .. lt_LN.ISO_8859-1 .. + lt_LN.DIS_8859-15 + .. lt_LN.ISO_8859-2 .. nl_BE.ISO_8859-1 .. + nl_BE.DIS_8859-15 + .. nl_NL.ISO_8859-1 .. + nl_NL.DIS_8859-15 + .. no_NO.ISO_8859-1 .. + no_NO.DIS_8859-15 + .. pl_PL.ISO_8859-2 .. pt_PT.ISO_8859-1 .. + pt_PT.DIS_8859-15 + .. ru_SU.CP866 .. ru_SU.KOI8-R *************** *** 466,471 **** --- 510,517 ---- sl_SI.ISO_8859-2 .. sv_SE.ISO_8859-1 + .. + sv_SE.DIS_8859-15 .. zh_CN.EUC .. *** /usr/src/share/timedef/data/Makefile.orig Mon Dec 21 22:32:43 1998 --- /usr/src/share/timedef/data/Makefile Tue Dec 22 07:20:29 1998 *************** *** 31,36 **** --- 31,38 ---- LOCALEDIR= ${DESTDIR}/usr/share/locale + 8859_15_LINKS = da_DK de_AT de_DE en_GB en_US es_ES fi_FI fr_FR is_IS \ + it_IT lt_LN nl_NL no_NO pt_PT sv_SE DE_LINKS = de_CH FR_LINKS = fr_BE fr_CA fr_CH IT_LINKS = it_CH *************** *** 51,68 **** --- 53,86 ---- ${INSTALL} ${COPY} -m 644 -o ${BINOWN} -g ${BINGRP} $$l.out \ ${LOCALEDIR}/$$l/LC_TIME; \ done + for l in ${8859_15_LINKS}; do \ + ln -fs ../$$l.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${DE_LINKS}; do \ ln -fs ../de_DE.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ done + for l in ${DE_LINKS}; do \ + ln -fs ../de_DE.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${IT_LINKS}; do \ ln -fs ../it_IT.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ done + for l in ${IT_LINKS}; do \ + ln -fs ../it_IT.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${FR_LINKS}; do \ ln -fs ../fr_FR.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ done + for l in ${FR_LINKS}; do \ + ln -fs ../fr_FR.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${LN_LINKS}; do \ ln -fs ../lt_LN.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l/LC_TIME; \ *************** *** 71,83 **** --- 89,113 ---- ln -fs ../nl_NL.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ done + for l in ${NL_LINKS}; do \ + ln -fs ../nl_NL.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${US_LINKS}; do \ ln -fs ../en_US.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ done + for l in ${US_LINKS}; do \ + ln -fs ../en_US.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ + done for l in ${GB_LINKS}; do \ ln -fs ../en_GB.ISO_8859-1/LC_TIME \ ${LOCALEDIR}/$$l.ISO_8859-1/LC_TIME; \ + done + for l in ${GB_LINKS}; do \ + ln -fs ../en_GB.ISO_8859-1/LC_TIME \ + ${LOCALEDIR}/$$l.DIS_8859-15/LC_TIME; \ done .include *** /usr/src/usr.bin/colldef/data/Makefile.orig Sun Dec 20 09:36:35 1998 --- /usr/src/usr.bin/colldef/data/Makefile Tue Dec 22 07:29:59 1998 *************** *** 10,16 **** lt_LN.ISO_8859-1 \ lt_LN.ISO_8859-2 \ ru_SU.CP866 \ ! ru_SU.KOI8-R LOCALEDIR= ${DESTDIR}/usr/share/locale --- 10,20 ---- lt_LN.ISO_8859-1 \ lt_LN.ISO_8859-2 \ ru_SU.CP866 \ ! ru_SU.KOI8-R \ ! de_DE.DIS_8859-15 \ ! es_ES.DIS_8859-15 \ ! is_IS.DIS_8859-15 \ ! lt_LN.DIS_8859-15 LOCALEDIR= ${DESTDIR}/usr/share/locale *************** *** 41,46 **** --- 45,55 ---- lt_LN.ISO_8859-2.out: map.ISO_8859-2 es_ES.ISO_8859-1.out: map.ISO_8859-1 de_DE.ISO_8859-1.out: map.ISO_8859-1 + is_IS.ISO_8859-1.out: map.ISO_8859-1 + lt_LN.DIS_8859-15.out: map.DIS_8859-15 + es_ES.DIS_8859-15.out: map.DIS_8859-15 + de_DE.DIS_8859-15.out: map.DIS_8859-15 + is_IS.DIS_8859-15.out: map.DIS_8859-15 .if !defined(_BUILD_TOOLS) afterinstall: *************** *** 56,61 **** --- 65,74 ---- ln -fs ../lt_LN.ISO_8859-1/LC_COLLATE \ ${LOCALEDIR}/${link}.ISO_8859-1/LC_COLLATE .endfor + .for link in ${LATIN1LINKS} + ln -fs ../lt_LN.DIS_8859-15/LC_COLLATE \ + ${LOCALEDIR}/${link}.DIS_8859-15/LC_COLLATE + .endfor .for link in ${LATIN2LINKS} ln -fs ../lt_LN.ISO_8859-2/LC_COLLATE \ ${LOCALEDIR}/${link}.ISO_8859-2/LC_COLLATE *************** *** 63,68 **** --- 76,85 ---- .for link in ${DELINKS} ln -fs ../de_DE.ISO_8859-1/LC_COLLATE \ ${LOCALEDIR}/${link}.ISO_8859-1/LC_COLLATE + .endfor + .for link in ${DELINKS} + ln -fs ../de_DE.DIS_8859-15/LC_COLLATE \ + ${LOCALEDIR}/${link}.DIS_8859-15/LC_COLLATE .endfor .endif *** /dev/null Tue Dec 22 02:02:53 1998 --- /usr/src/usr.bin/colldef/data/de_DE.DIS_8859-15.src Mon Dec 21 22:13:28 1998 *************** *** 0 **** --- 1,38 ---- + # German/ISO 8859-1 (backward compatible with ASCII) + # + # $Id: de_DE.DIS_8859-15.src,v 1.4 1997/03/10 21:59:53 ache Exp $ + # + charmap map.DIS_8859-15 + order \ + # controls + ;...;;;...;;\ + # + ;;!;;\";<<<>;/>>;;\ + ;;;;;\ + %;&;';\(;\);*;+;<+->;<-:>;<*X>;\,;<-->;-;.;/;\ + # digits + 0;(1,<1S>);(2,<2S>);(3,<3S>);4;...;9;\ + # + :;\;;\<;=;>;?;;;;;;;\ + # capital + (A,,,>,,,,);\ + B;(C,);D;(E,,,>,);\ + F;G;H;(I,,,>,);\ + J;...;M;(N,);(O,,,>,,,,);\ + P;...;R;(S,);T;(U,,,>,);\ + V;W;X;(Y,,);(Z,);\ + ;;\ + # + [;\\;];^;_;<'m>;`;\ + # small + (a,,,>,,,,);\ + b;(c,);d;(e,,,>,);\ + f;g;h;(i,,,>,);\ + j;...;m;(n,);(o,,,>,,,,);\ + p;...;r;(s,);(,ss);t;(u,,,>,);\ + v;w;x;(y,,);(z,);\ + ;;\ + # + \{;;|;\};~;<.M>;;;
;\ + # remains + <-a>;<-o> *** /dev/null Tue Dec 22 02:02:53 1998 --- /usr/src/usr.bin/colldef/data/is_IS.DIS_8859-15.src Mon Dec 21 22:14:08 1998 *************** *** 0 **** --- 1,38 ---- + # icelandic (backward compatible with ASCII) + # + # $Id: is_IS.DIS_8859-15.src,v 1.4 1997/02/22 19:54:38 peter Exp $ + # + charmap map.DIS_8859-15 + order \ + # controls + ;...;;;...;;\ + # + ;;!;;\";<<<>;/>>;;\ + ;;;;;\ + %;&;';\(;\);*;+;<+->;<-:>;<*X>;\,;<-->;-;.;/;\ + # digits + 0;(1,<1S>);(2,<2S>);(3,<3S>);4;...;9;\ + # + :;\;;\<;=;>;?;;;;;;;\ + # capital + (A,,,>,,,);\ + B;(C,);(D,);(E,,,>,);\ + F;G;H;(I,,,>,);\ + J;...;M;(N,);(O,,,>,,,);\ + P;...;R;(S,);T;(U,,,>,);\ + V;W;X;(Y,,);(Z,);\ + ;;;\ + # + [;\\;];^;_;<'m>;`;\ + # small + (a,,,>,,,);\ + b;(c,);(d,);(e,,,>,);\ + f;g;h;(i,,,>,);\ + j;...;m;(n,);(o,,,>,,,);\ + p;...;r;(s,);t;(u,,,>,);\ + v;w;x;(y,,);(z,);\ + ;;;;\ + # + \{;;|;\};~;<.M>;;;
;\ + # remains + <-a>;<-o> *** /dev/null Tue Dec 22 02:02:53 1998 --- /usr/src/usr.bin/colldef/data/lt_LN.DIS_8859-15.src Mon Dec 21 22:14:49 1998 *************** *** 0 **** --- 1,38 ---- + # latin1 (backward compatible with ASCII) + # + # $Id: lt_LN.DIS_8859-15.src,v 1.8 1997/02/22 19:54:39 peter Exp $ + # + charmap map.DIS_8859-15 + order \ + # controls + ;...;;;...;;\ + # + ;;!;;\";<<<>;/>>;;\ + ;;;;;\ + %;&;';\(;\);*;+;<+->;<-:>;<*X>;\,;<-->;-;.;/;\ + # digits + 0;(1,<1S>);(2,<2S>);(3,<3S>);4;...;9;\ + # + :;\;;\<;=;>;?;;;;;;;\ + # capital + (A,,,>,,,,);\ + B;(C,);D;(E,,,>,);\ + F;G;H;(I,,,>,);\ + J;...;M;(N,);(O,,,>,,,,);\ + P;...;R;(S,);T;(U,,,>,);\ + V;W;X;(Y,,);(Z,);\ + ;;\ + # + [;\\;];^;_;<'m>;`;\ + # small + (a,,,>,,,,);\ + b;(c,);d;(e,,,>,);\ + f;g;h;(i,,,>,);\ + j;...;m;(n,);(o,,,>,,,,);\ + p;...;r;(s,);t;(u,,,>,);\ + v;w;x;(y,,);(z,);\ + ;;;\ + # + \{;;|;\};~;<.M>;;;
;\ + # remains + <-a>;<-o> *** /dev/null Tue Dec 22 02:02:53 1998 --- /usr/src/usr.bin/colldef/data/map.DIS_8859-15 Mon Dec 21 21:41:30 1998 *************** *** 0 **** --- 1,174 ---- + NU \x00 + SH \x01 + SX \x02 + EX \x03 + ET \x04 + EQ \x05 + AK \x06 + BL \x07 + BS \x08 + HT \x09 + LF \x0a + VT \x0b + FF \x0c + CR \x0d + SO \x0e + SI \x0f + DL \x10 + D1 \x11 + D2 \x12 + D3 \x13 + D4 \x14 + NK \x15 + SY \x16 + EB \x17 + CN \x18 + EM \x19 + SB \x1a + EC \x1b + FS \x1c + GS \x1d + RS \x1e + US \x1f + SP \x20 + Nb \x23 + DO \x24 + At \x40 + <( \x5b + // \x5c + )> \x5d + '> \x5e + '! \x60 + (! \x7b + !! \x7c + !) \x7d + '? \x7e + DT \x7f + PA \x80 + HO \x81 + BH \x82 + NH \x83 + IN \x84 + NL \x85 + SA \x86 + ES \x87 + HS \x88 + HJ \x89 + VS \x8a + PD \x8b + PU \x8c + RI \x8d + S2 \x8e + S3 \x8f + DC \x90 + P1 \x91 + P2 \x92 + TS \x93 + CC \x94 + MW \x95 + SG \x96 + EG \x97 + SS \x98 + GC \x99 + SC \x9a + CI \x9b + ST \x9c + OC \x9d + PM \x9e + AC \x9f + NS \xa0 + !I \xa1 + Ct \xa2 + Pd \xa3 + Eu \xa4 + Ye \xa5 + S< \xa6 + SE \xa7 + s< \xa8 + Co \xa9 + -a \xaa + << \xab + NO \xac + -- \xad + Rg \xae + 'm \xaf + DG \xb0 + +- \xb1 + 2S \xb2 + 3S \xb3 + Z< \xb4 + My \xb5 + PI \xb6 + .M \xb7 + z< \xb8 + 1S \xb9 + -o \xba + >> \xbb + OE \xbc + oe \xbd + Y: \xbe + ?I \xbf + A! \xc0 + A' \xc1 + A> \xc2 + A? \xc3 + A: \xc4 + AA \xc5 + AE \xc6 + C, \xc7 + E! \xc8 + E' \xc9 + E> \xca + E: \xcb + I! \xcc + I' \xcd + I> \xce + I: \xcf + D- \xd0 + N? \xd1 + O! \xd2 + O' \xd3 + O> \xd4 + O? \xd5 + O: \xd6 + *X \xd7 + O/ \xd8 + U! \xd9 + U' \xda + U> \xdb + U: \xdc + Y' \xdd + TH \xde + ss \xdf + a! \xe0 + a' \xe1 + a> \xe2 + a? \xe3 + a: \xe4 + aa \xe5 + ae \xe6 + c, \xe7 + e! \xe8 + e' \xe9 + e> \xea + e: \xeb + i! \xec + i' \xed + i> \xee + i: \xef + d- \xf0 + n? \xf1 + o! \xf2 + o' \xf3 + o> \xf4 + o? \xf5 + o: \xf6 + -: \xf7 + o/ \xf8 + u! \xf9 + u' \xfa + u> \xfb + u: \xfc + y' \xfd + th \xfe + y: \xff --------------2C67412E284797A9500F9F30-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 04:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11885 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 04:47:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11879 for ; Tue, 22 Dec 1998 04:47:01 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id EAA14567 for ; Tue, 22 Dec 1998 04:47:01 -0800 (PST) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id NAA12166; Tue, 22 Dec 1998 13:46:42 +0100 (MET) Message-ID: <19981222134641.A12019@cons.org> Date: Tue, 22 Dec 1998 13:46:41 +0100 From: Martin Cracauer To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <199812220243.VAA21066@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199812220243.VAA21066@lakes.dignus.com>; from Thomas David Rivers on Mon, Dec 21, 1998 at 09:43:24PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199812220243.VAA21066@lakes.dignus.com>, Thomas David Rivers wrote: > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > while true > do > sleep 2 > done Sorry, this works for me. I'm on current, but sh didn't change since 3.0-RELEASE. What does this show? ktrace sh thisscript kdump | grep sleep BTW, an easier way to have an endless look is while : ; do sleep 2 ; done Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 04:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12213 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 04:50:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12159 for ; Tue, 22 Dec 1998 04:50:02 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id EAA14735 for ; Tue, 22 Dec 1998 04:50:03 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id HAA22141; Tue, 22 Dec 1998 07:50:02 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id IAA27157; Tue, 22 Dec 1998 08:37:30 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id HAA22231; Tue, 22 Dec 1998 07:51:10 -0500 (EST) Date: Tue, 22 Dec 1998 07:51:10 -0500 (EST) From: Thomas David Rivers Message-Id: <199812221251.HAA22231@lakes.dignus.com> To: cracauer@cons.org, freebsd-hackers@freefall.cdrom.com, rivers@dignus.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) In-Reply-To: <19981222134641.A12019@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In <199812220243.VAA21066@lakes.dignus.com>, Thomas David Rivers wrote: > > > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > > > while true > > do > > sleep 2 > > done > > Sorry, this works for me. I'm on current, but sh didn't change since > 3.0-RELEASE. > > What does this show? > ktrace sh thisscript > kdump | grep sleep > > BTW, an easier way to have an endless look is > while : ; do sleep 2 ; done > > Martin > -- Martin brings up an interesting 'twist' on this. If you place the script in a file; the control-C works just fine (on a 3.0-RELEASE system.) Martin - did you place the small script in a file and run the file? If so, can you try simply typing it on the sh's command line and seeing if control-C works/doesn't work. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 05:06:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14048 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 05:06:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14043 for ; Tue, 22 Dec 1998 05:06:17 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA15473 for ; Tue, 22 Dec 1998 05:06:17 -0800 (PST) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id OAA12269; Tue, 22 Dec 1998 14:06:04 +0100 (MET) Message-ID: <19981222140604.A12246@cons.org> Date: Tue, 22 Dec 1998 14:06:04 +0100 From: Martin Cracauer To: Thomas David Rivers , freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <199812220243.VAA21066@lakes.dignus.com> <19981222134641.A12019@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19981222134641.A12019@cons.org>; from Martin Cracauer on Tue, Dec 22, 1998 at 01:46:42PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <19981222134641.A12019@cons.org>, Martin Cracauer wrote: > In <199812220243.VAA21066@lakes.dignus.com>, Thomas David Rivers wrote: > > > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > > > while true > > do > > sleep 2 > > done While you're at it, what does this show? which sleep sleep -? This most probable cause of this problem is a sleep binary that catches SIGINT, but doesn't kill itself with SIGINT afterwards. I could imagine that some braindead port installs such a thing. Maybe GNU shellutils or such? If it's /bin/sleep, these please send me the full kdump output (of SIGINTing the above script, not of `which` :-). Thanks Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 05:22:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15791 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 05:22:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15780 for ; Tue, 22 Dec 1998 05:22:17 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.48]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA29257 for ; Tue, 22 Dec 1998 08:25:06 +0500 Message-ID: <367F9D58.D755DAB0@bachue.usc.unal.edu.co> Date: Tue, 22 Dec 1998 08:23:36 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: Re: questions/problems with vm_fault() in Stable References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In this thread I've heard good comment on UVM and also that there is not anyone really in charge of the VM. Would this indicate that we want UVM ?? Chuck Cranor's papers say a port could be done but, as I understand, our VM is faster. cheers, Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 05:48:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17970 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 05:48:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.datafax.com (gatekeeper.datafax.com [207.219.232.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17959 for ; Tue, 22 Dec 1998 05:48:29 -0800 (PST) (envelope-from jim@datafax.com) Received: from taos.datafax.com (taos.datafax.com [192.168.3.17]) by gatekeeper.datafax.com (8.8.8/8.8.8) with SMTP id IAA28700 for ; Tue, 22 Dec 1998 08:48:23 -0500 (EST) (envelope-from jim@taos.datafax.com) Received: from taos by taos.datafax.com (SMI-8.6/SMI-SVR4) id IAA28419; Tue, 22 Dec 1998 08:47:09 -0500 Message-Id: <199812221347.IAA28419@taos.datafax.com> Date: Tue, 22 Dec 1998 08:47:09 -0500 (EST) From: "Jim W. Towne" Reply-To: "Jim W. Towne" Subject: Anyone know of ... To: hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: kB6wkcm+NdrUWy4eNjGNxg== X-Mailer: dtmail 1.2.0 CDE Version 1.2 SunOS 5.6 i86pc i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone herd of an X11 gui application tester for FreeBSD, GNU or Linix? Thank you. ------------------------------------------------------ Jim Towne Clinical DataFax Systems Inc. Voice: 905.522.3282.x230 Fax: 905.522.7284 Email: jim@datafax.com ------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 06:07:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20687 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 06:07:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20681 for ; Tue, 22 Dec 1998 06:07:19 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id GAA17806 for ; Tue, 22 Dec 1998 06:07:12 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id JAA28650; Tue, 22 Dec 1998 09:07:19 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id JAA27235; Tue, 22 Dec 1998 09:54:50 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id JAA22681; Tue, 22 Dec 1998 09:08:27 -0500 (EST) Date: Tue, 22 Dec 1998 09:08:27 -0500 (EST) From: Thomas David Rivers Message-Id: <199812221408.JAA22681@lakes.dignus.com> To: cracauer@cons.org, freebsd-hackers@freefall.cdrom.com, rivers@dignus.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) In-Reply-To: <19981222140604.A12246@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In <19981222134641.A12019@cons.org>, Martin Cracauer wrote: > > In <199812220243.VAA21066@lakes.dignus.com>, Thomas David Rivers wrote: > > > > > > Try the following on a 3.0-RELEASE system, under the bourne shell: > > > > > > while true > > > do > > > sleep 2 > > > done > > While you're at it, what does this show? > > which sleep > sleep -? > > This most probable cause of this problem is a sleep binary that > catches SIGINT, but doesn't kill itself with SIGINT afterwards. I > could imagine that some braindead port installs such a thing. Maybe > GNU shellutils or such? > > If it's /bin/sleep, these please send me the full kdump output (of > SIGINTing the above script, not of `which` :-). > > Thanks > Martin Well - it can't be sleep - as the same thing happens if you substitute sync for the sleep command, i.e. while true do sync done can't be interrupted either (although, it can be if you place it in a file and execute the file.) That kinda points to the shell (/bin/sh) as the culprit (or, perhaps the tty driver somehow?) - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 06:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25376 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 06:43:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25368 for ; Tue, 22 Dec 1998 06:43:05 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zsT1X-000I5eC; Tue, 22 Dec 1998 09:42:59 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: kernel panic In-Reply-To: from Tom Torrance at home at "Dec 21, 1998 5:12: 6 pm" To: tom@mailx.tomqnx.com (Tom Torrance at home) Date: Tue, 22 Dec 1998 09:42:59 -0500 (EST) Cc: jkh@zippy.cdrom.com, tom@tomqnx.com, hackers@FreeBSD.ORG, support@opensound.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to the opensound folks, the 0.8 version of x11amp is supposed to work with the standard FreeBSD sound drivers. With the 3.0 OS, current as of yesterday, it does NOT. There is an initial message "Unable to get fragment size" followed by a copy of the following message for each entry in the playlist: "unable to open the audio device". Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 06:49:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26449 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 06:49:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA26440 for ; Tue, 22 Dec 1998 06:49:54 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA00998; Tue, 22 Dec 1998 13:36:21 +0100 From: Luigi Rizzo Message-Id: <199812221236.NAA00998@labinfo.iet.unipi.it> Subject: Re: kernel panic To: tom@tomqnx.com (Tom Torrance at home) Date: Tue, 22 Dec 1998 13:36:21 +0100 (MET) Cc: tom@mailx.tomqnx.com, jkh@zippy.cdrom.com, tom@tomqnx.com, hackers@FreeBSD.ORG, support@opensound.com In-Reply-To: from "Tom Torrance at home" at Dec 22, 98 09:42:40 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to the opensound folks, the 0.8 version of x11amp is > supposed to work with the standard FreeBSD sound drivers. > > With the 3.0 OS, current as of yesterday, it does NOT. are you sure you are not using an old copy of 0.8 -- the OSS people were very cooperative in fixing the problem, the only thing was they did not change the file name when changing the binary. luigi > There is an initial message "Unable to get fragment size" > followed by a copy of the following message for each > entry in the playlist: > "unable to open the audio device". > > Regards, > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 06:56:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28113 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 06:56:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA28094 for ; Tue, 22 Dec 1998 06:56:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id GAA21544; Tue, 22 Dec 1998 06:56:21 -0800 (PST) To: tom@tomqnx.com (Tom Torrance at home) cc: tom@mailx.tomqnx.com (Tom Torrance at home), hackers@FreeBSD.ORG, support@opensound.com Subject: Re: kernel panic In-reply-to: Your message of "Tue, 22 Dec 1998 09:42:59 EST." Date: Tue, 22 Dec 1998 06:56:20 -0800 Message-ID: <21529.914338580@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to the opensound folks, the 0.8 version of x11amp is > supposed to work with the standard FreeBSD sound drivers. > > With the 3.0 OS, current as of yesterday, it does NOT. Running a 3.0-current kernel as of this morning, x11amp works just fine with the the stock sound drivers. What does /dev/sndstat print for you? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 07:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05936 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 07:52:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail1.tor.accglobal.net ([204.92.55.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05931 for ; Tue, 22 Dec 1998 07:52:07 -0800 (PST) (envelope-from josh@ican.net) Received: from staff.tor.acc.ca ([204.92.55.27]) by mail1.tor.accglobal.net with esmtp (Exim 2.02 #1) id 0zsU5a-0007W2-01; Tue, 22 Dec 1998 10:51:14 -0500 Received: from josh by staff.tor.acc.ca with local (Exim 1.92 #1) id 0zsU5a-0002sK-00; Tue, 22 Dec 1998 10:51:14 -0500 Message-ID: <19981222105114.48671@ican.net> Date: Tue, 22 Dec 1998 10:51:14 -0500 From: Josh Tiefenbach To: Tom Torrance at home Cc: jkh@zippy.cdrom.com, hackers@FreeBSD.ORG, support@opensound.com Subject: Re: kernel panic References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Tom Torrance at home on Tue, Dec 22, 1998 at 09:42:59AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 22, 1998 at 09:42:59AM -0500, Tom Torrance at home wrote: > According to the opensound folks, the 0.8 version of x11amp is > supposed to work with the standard FreeBSD sound drivers. > > With the 3.0 OS, current as of yesterday, it does NOT. Actually, it does, after a fashion. I noticed that when run as a normal user, it loads, but refuses to play any mp3s, and dmesg fills up with sorry, read DMA channel unavailable all over the place, and the odd pid 2209 (x11amp), uid 701954: exited on signal 10 (core dumped) When running as root, however, everthing is fine. This is from: FreeBSD 3.0-CURRENT #3: Mon Dec 21 18:00:18 EST 1998 josh@asherah.zipperup.org:/usr/src/sys/compile/ASHERAH and: asherah:/usr/home/josh$ cat /dev/sndstat FreeBSD Audio Driver (981002) Dec 21 1998 18:00:00 Installed devices: pcm1: at 0x220 irq 5 dma 5:1 sequencer1: at 0x388 (not functional) Actually, I just noticed the sequencer1 bit now. I havent noticed any problems otherwise tho. josh -- Josh Tiefenbach - Member - ACC Corps of Internet Engineers - josh@ican.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 08:37:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13694 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 08:37:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.mod.uk (relay.mod.uk [192.5.29.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA13666 for ; Tue, 22 Dec 1998 08:37:54 -0800 (PST) (envelope-from druid@atc.dera.gov.uk) Received: from hermes.dra.hmg.gb by relay.mod.uk with local SMTP id ; Tue, 22 Dec 1998 16:37:47 +0000 Received: from atc.dera.gov.uk by hermes.dra.hmg.gb (MX V4.2 VAX) with SMTP; Tue, 22 Dec 1998 16:36:51 GMT Received: from atc.dera.gov.uk by atc.dera.gov.uk (8.8.8+Sun/SMI-SVR4) id QAA00685; Tue, 22 Dec 1998 16:36:36 GMT Message-ID: <367FCA84.3DBE8085@atc.dera.gov.uk> Date: Tue, 22 Dec 1998 16:36:20 +0000 From: Mark Templeton Organization: ATC Systems Group, DERA Malvern X-Mailer: Mozilla 4.05 [en] (X11; I; SunOS 5.6 sun4u) MIME-Version: 1.0 To: Mike Smith CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Memory holes for ISA device drivers References: <199812141110.DAA00438@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > OS is 2.2.5 > > Card is on ISA bus, preferably at 0xA00000. > > > > How do I create a (physical) memory hole for a card, > > as the card holds 64k shared memory? > > The target system BIOS does not support the 15-16M memory hole. > > pmap_mapdev() maps physical to virtual memory, but does not > > create a hole. > > > > How do I create a memory hole? > > This is chipset- and motherboard-specific. If you can't map the card > into the ISA 'hole' at 0xa0000, then you're SOL short of building a > custom PCI:ISA bridge (eg. using a PLX9050) and remapping it into PCI > space. Thank you for your comments, Mike. But even on systems that support the ISA memory hole, this restricts FreeBSD to effectively see only 15MB of RAM. Surely this is undesirable? Are there no software alternatives? If not, then I guess I have to talk to MRBIOS and see if they can supply me a BIOS which will do what I need. Mark. -- 0 00000000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 The Druid 0 B1013, DERA Malvern, Internet: Mark.Templeton@atc.dera.gov.uk St Andrews Road, Janet : Mark.Templeton@uk.mod.hermes Malvern, Worcs., WR14 3PS, Phone: +44-1684-894213 United Kingdom, Fax: +44-1684-894109 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 09:22:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19686 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 09:22:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19681 for ; Tue, 22 Dec 1998 09:22:17 -0800 (PST) (envelope-from cracauer@cons.org) Received: from cons.org (knight.cons.org [194.233.237.86]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id JAA20990 for ; Tue, 22 Dec 1998 09:22:17 -0800 (PST) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id SAA05508; Tue, 22 Dec 1998 18:21:58 +0100 (CET) Message-ID: <19981222182157.A5343@cons.org> Date: Tue, 22 Dec 1998 18:21:57 +0100 From: Martin Cracauer To: Thomas David Rivers , cracauer@cons.org, freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <19981222134641.A12019@cons.org> <199812221251.HAA22231@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199812221251.HAA22231@lakes.dignus.com>; from Thomas David Rivers on Tue, Dec 22, 1998 at 07:51:10AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199812221251.HAA22231@lakes.dignus.com>, Thomas David Rivers wrote: > > > while true > > > do > > > sleep 2 > > > done > Martin brings up an interesting 'twist' on this. If you place the > script in a file; the control-C works just fine (on a 3.0-RELEASE system.) OK, that (to me :-) a known issue. In a script (that is a non-interactive shell), sh exists itself if a child returns with WIFSIGNALED(status). Unless you set or unset traps yourself, that is. For interactive shells, you can't do it that way, since you don't want the shell to exit if the child is being killed. What is needed here is that sh breaks the loop (instead of exiting itself) if a child inside a loop exists with WIFSIGNALED(status). This is not trivial to implement since you can have nested loops and want to break the outermost. Also, I'll have to see what POSIX sais about the issue (yes, the fat book arrived and is paid :-). I'll give it a shot over the holidays, for now I'll file a PR to document the issue. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 10:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28598 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 10:30:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28590 for ; Tue, 22 Dec 1998 10:30:46 -0800 (PST) (envelope-from rhyatt@stdio.com) Received: (from rhyatt@localhost) by heathers.stdio.com (8.8.8/8.8.8) id NAA23666; Tue, 22 Dec 1998 13:33:44 -0500 (EST) (envelope-from rhyatt) From: "Ray Hyatt Jr." Message-Id: <199812221833.NAA23666@heathers.stdio.com> Subject: Re: Anyone know of ... In-Reply-To: <199812221347.IAA28419@taos.datafax.com> from "Jim W. Towne" at "Dec 22, 98 08:47:09 am" To: jim@datafax.com Date: Tue, 22 Dec 1998 13:33:44 -0500 (EST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Has anyone herd of an X11 gui application tester for FreeBSD, GNU or Linix? > > Thank you. If you are wanting to exercise the GUI and have a supported server, X-runner ( http://www.merc-int.com/products/xrunguide.html ) by Mercury Interactive will do alot of automation for testing of X11. Scriptable too! I don't know if it is supported on any of the free unixen. As I haven't worked with it in a couple years. Hope this helps. Ray To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 12:23:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09618 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 12:23:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09492 for ; Tue, 22 Dec 1998 12:23:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA05612; Tue, 22 Dec 1998 12:23:19 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 12:23:19 -0800 (PST) From: Matthew Dillon Message-Id: <199812222023.MAA05612@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: vfs_bio / struct buf Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that Luoqi has committed the vfs_bio.c fixes, I have commited some updated comments plus committed a 'buf' and 'bp' manual page describing its operation (/usr/src/share/man/man9/buf.9). People are welcome to correct any mistakes in the manual page. I'm sure I've muffed up some of it. Please feel free to commit (if you are a committer) your corrections, it's easier then sending me diffs. The more I look at the code, the more glaringly obvious is the fact that the buf/bp subsystem was supposed to handle smaller non-page-aligned block sizes. It is also glaringly obvious that there are some hacks in there that we should probably work to remove. We ought to be able to fix NFS to not have to use the validoff/validend/dirtyoff/dirtyend junk, and we ought to be able to clean the system up such that it is possible to get rid of the bogus_page stuff and we should also be able to fix the bogus way pages are marked clean in the VFS layer ( rather then being marked clean in the device layer ). I may take this up post-3.0.1. -Matt :- Jordan : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 12:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17762 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 12:37:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hotmail.com (f319.hotmail.com [207.82.250.239]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17673 for ; Tue, 22 Dec 1998 12:36:52 -0800 (PST) (envelope-from kuman123@hotmail.com) Received: (qmail 27272 invoked by uid 0); 22 Dec 1998 20:36:46 -0000 Message-ID: <19981222203646.27271.qmail@hotmail.com> Received: from 207.135.94.115 by www.hotmail.com with HTTP; Tue, 22 Dec 1998 12:36:45 PST X-Originating-IP: [207.135.94.115] From: "ku man" To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: multiple routers for multiple NICs Date: Tue, 22 Dec 1998 12:36:45 PST Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a box running FreeBSD 3.0 with 2 Intel 10/100 PRO ethernet adapters. Instead of using a single default router, is there a way to configure the system so that traffic on each NIC will be routed through a NIC-specific router? That is, how can I associate a different router for each NIC? Thanks for any help. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 12:55:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25621 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 12:55:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25484 for ; Tue, 22 Dec 1998 12:54:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA05836; Tue, 22 Dec 1998 12:54:12 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 12:54:12 -0800 (PST) From: Matthew Dillon Message-Id: <199812222054.MAA05836@apollo.backplane.com> To: "Pedro F. Giffuni" Cc: hackers Subject: Re: questions/problems with vm_fault() in Stable References: <367F9D58.D755DAB0@bachue.usc.unal.edu.co> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In this thread I've heard good comment on UVM and also that there is not :anyone really in charge of the VM. : :Would this indicate that we want UVM ?? Chuck Cranor's papers say a port :could be done but, as I understand, our VM is faster. : :cheers, : Pedro. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-hackers" in the body of the message We don't want UVM. It isn't quite true that there is nobody working on the VM system: There are at least four of us who know enough about it to work on it and probably another half a dozen specialists, but nobody as good as John was. I actually like FreeBSD's VM system - It has a few more hacks then it should, but nothing that can't be evolved out. There's definitely a ramp-up period involved, though. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 13:14:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05448 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 13:14:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05384 for ; Tue, 22 Dec 1998 13:14:45 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA18403 for ; Tue, 22 Dec 1998 13:14:41 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id QAA08725; Tue, 22 Dec 1998 16:14:39 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id RAA27711; Tue, 22 Dec 1998 17:02:19 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id QAA23936; Tue, 22 Dec 1998 16:15:47 -0500 (EST) Date: Tue, 22 Dec 1998 16:15:47 -0500 (EST) From: Thomas David Rivers Message-Id: <199812222115.QAA23936@lakes.dignus.com> To: cracauer@cons.org, freebsd-hackers@freefall.cdrom.com, rivers@dignus.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) In-Reply-To: <19981222182157.A5343@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In <199812221251.HAA22231@lakes.dignus.com>, Thomas David Rivers wrote: > > > > while true > > > > do > > > > sleep 2 > > > > done > > Martin brings up an interesting 'twist' on this. If you place the > > script in a file; the control-C works just fine (on a 3.0-RELEASE system.) > > OK, that (to me :-) a known issue. > > In a script (that is a non-interactive shell), sh exists itself if a > child returns with WIFSIGNALED(status). Unless you set or unset traps > yourself, that is. > > For interactive shells, you can't do it that way, since you don't want > the shell to exit if the child is being killed. > > What is needed here is that sh breaks the loop (instead of exiting > itself) if a child inside a loop exists with WIFSIGNALED(status). This > is not trivial to implement since you can have nested loops and want > to break the outermost. Also, I'll have to see what POSIX sais about > the issue (yes, the fat book arrived and is paid :-). > > I'll give it a shot over the holidays, for now I'll file a PR to > document the issue. > > Martin > -- Sounds like you've got a good handle on it, then... I won't bother with a PR. But, just for your own information; this doesn't seem to be a problem in 2.2.x... just 3.0. So, perhaps it's something that changes in /bin/sh since then, or something that changed with signal() in the system? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 13:28:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16395 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 13:28:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16375 for ; Tue, 22 Dec 1998 13:28:39 -0800 (PST) (envelope-from cracauer@cons.org) Received: from cons.org (knight.cons.org [194.233.237.86]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA26622 for ; Tue, 22 Dec 1998 13:28:39 -0800 (PST) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id WAA06015; Tue, 22 Dec 1998 22:28:16 +0100 (CET) Message-ID: <19981222222815.A6007@cons.org> Date: Tue, 22 Dec 1998 22:28:15 +0100 From: Martin Cracauer To: Thomas David Rivers , cracauer@cons.org, freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <19981222182157.A5343@cons.org> <199812222115.QAA23936@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199812222115.QAA23936@lakes.dignus.com>; from Thomas David Rivers on Tue, Dec 22, 1998 at 04:15:47PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199812222115.QAA23936@lakes.dignus.com>, Thomas David Rivers wrote: > But, just for your own information; this doesn't seem to be a problem > in 2.2.x... just 3.0. So, perhaps it's something that changes in /bin/sh > since then, or something that changed with signal() in the system? The signal handling in 2.2.x was changed between 2.2.6 and 2.2.7. Could you verify that the systems that doesn't have the problem is older than 2.2.7? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 13:31:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16851 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 13:31:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16838 for ; Tue, 22 Dec 1998 13:31:49 -0800 (PST) (envelope-from rivers@dignus.com) Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA26798 for ; Tue, 22 Dec 1998 13:31:41 -0800 (PST) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id QAA10534; Tue, 22 Dec 1998 16:31:47 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.1/8.8.5) with ESMTP id RAA27730; Tue, 22 Dec 1998 17:19:28 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.1/8.6.9) id QAA24092; Tue, 22 Dec 1998 16:32:57 -0500 (EST) Date: Tue, 22 Dec 1998 16:32:57 -0500 (EST) From: Thomas David Rivers Message-Id: <199812222132.QAA24092@lakes.dignus.com> To: cracauer@cons.org, freebsd-hackers@freefall.cdrom.com, rivers@dignus.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) In-Reply-To: <19981222222815.A6007@cons.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In <199812222115.QAA23936@lakes.dignus.com>, Thomas David Rivers wrote: > > But, just for your own information; this doesn't seem to be a problem > > in 2.2.x... just 3.0. So, perhaps it's something that changes in /bin/sh > > since then, or something that changed with signal() in the system? > > The signal handling in 2.2.x was changed between 2.2.6 and > 2.2.7. Could you verify that the systems that doesn't have the problem > is older than 2.2.7? > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer > Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 > Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany > The system that doesn't have the problem is: FreeBSD puddles.dignus.com 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Wed Mar 18 14:31:17 EST 1998 Unfortunately, I don't have a 2.2.6/2.2.7/2.2.8 release around to test those... I know, though, that 2.2.5 doesn't have the problem. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 13:39:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19312 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 13:39:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19287 for ; Tue, 22 Dec 1998 13:38:54 -0800 (PST) (envelope-from cracauer@cons.org) Received: from cons.org (knight.cons.org [194.233.237.86]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id NAA27238 for ; Tue, 22 Dec 1998 13:38:52 -0800 (PST) Received: (from cracauer@localhost) by cons.org (8.8.8/8.7.3) id WAA06069; Tue, 22 Dec 1998 22:38:33 +0100 (CET) Message-ID: <19981222223832.A6060@cons.org> Date: Tue, 22 Dec 1998 22:38:32 +0100 From: Martin Cracauer To: Thomas David Rivers , cracauer@cons.org, freebsd-hackers@freefall.cdrom.com Subject: Re: Interesting un-interruptible shell script on 3.0-RELEASE (possible sh bug?) References: <19981222222815.A6007@cons.org> <199812222132.QAA24092@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199812222132.QAA24092@lakes.dignus.com>; from Thomas David Rivers on Tue, Dec 22, 1998 at 04:32:57PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199812222132.QAA24092@lakes.dignus.com>, Thomas David Rivers wrote: > The system that doesn't have the problem is: > > FreeBSD puddles.dignus.com 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Wed Mar 18 14:31:17 EST 1998 Thanks, as I thought, this is pre-SIGINT fixes in sh. In a word, you've been bitten by the fact that I treated /bin/sh mainly as a scripting language and less as an interactive shell :-) Anyway, I'll look for a fix over the holidays. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 14:00:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09470 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 14:00:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09434 for ; Tue, 22 Dec 1998 14:00:11 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id OAA18089; Tue, 22 Dec 1998 14:00:40 -0800 (PST) Message-Id: <199812222200.OAA18089@root.com> To: Daniel Leeds cc: "'hackers@freebsd.org'" Subject: Re: adaptec 2940uw2 In-reply-to: Your message of "Mon, 21 Dec 1998 14:11:44 EST." <93A9C7D71478D211ACEC00805F65C14F1BD06C@steamer.raremedium.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 22 Dec 1998 14:00:40 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >does freebsd support the adaptec 2940uw2 card? and if so, which release? Yes. 3.0. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 14:46:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14117 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 14:46:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14054 for ; Tue, 22 Dec 1998 14:46:36 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id OAA18640; Tue, 22 Dec 1998 14:47:00 -0800 (PST) Message-Id: <199812222247.OAA18640@root.com> To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: vfs_bio / struct buf In-reply-to: Your message of "Tue, 22 Dec 1998 12:23:19 PST." <199812222023.MAA05612@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 22 Dec 1998 14:47:00 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is also glaringly obvious that there are some hacks in there that > we should probably work to remove. We ought to be able to fix NFS > to not have to use the validoff/validend/dirtyoff/dirtyend junk, and > we ought to be able to clean the system up such that it is possible > to get rid of the bogus_page stuff and we should also be able to fix > the bogus way pages are marked clean in the VFS layer ( rather then being > marked clean in the device layer ). I may take this up post-3.0.1. valid/dirty off/end are there to reduce wire traffic, but aren't strictly necessary. We would not want to remove it. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 15:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24832 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 15:00:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fan.net.au (fan.net.au [203.20.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24756 for ; Tue, 22 Dec 1998 15:00:16 -0800 (PST) (envelope-from q@fan.net.au) Received: from gromit.fan.net.au (gromit.fan.net.au [203.23.133.34]) by fan.net.au (8.9.1/8.9.1) with SMTP id JAA10092 for ; Wed, 23 Dec 1998 09:00:10 +1000 (EST) Date: Wed, 23 Dec 1998 09:00:10 +1000 (EST) From: Q To: freebsd-hackers@FreeBSD.ORG Subject: Unusual kernel panic?? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't experimented with this incident yet, so I am not sure of the exact circumstances that cause it. I have done the following on my 3.0-RELEASE machine twice now and both times it crashed. I meant to try and find the cause last night but forgot. #mount -t msdos /dev/da1s1 /dos/modrive/ ^^-- Trailing slash. System will lockup and reboot. I was in X both times so didn't get to see the console messages. Both times I immediately did it again after the system rebooted, this time without the slash and it worked fine. When I get home I will try it again to see if this is actually the cause. Anyone want to try it and see if it happens to them? The media in the Fujitsu DynaMO 230 drive hadn't been access since the system was booted, and hadn't been recently inserted. The volume was a FAT16 dos. No entry for /dev/da1s1 was in fstab Just something to play around with if you feel so inclined. I will try it myself tonight and see what I can find. Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan - q@fan.net.au __ __/ / / __/ / / Systems Administrator / __ / _/ / / Fast Access Network __/ __/ __/ ____/ / - / Gold Coast, QLD, Australia _______ / Ph: +61 7 5574 1050 \_\ SAGE-AU Member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 15:05:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00920 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 15:05:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00704 for ; Tue, 22 Dec 1998 15:05:43 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.40]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA373 for ; Tue, 22 Dec 1998 18:08:34 +0500 Message-ID: <36802615.E5E264EB@bachue.usc.unal.edu.co> Date: Tue, 22 Dec 1998 18:07:01 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: New packaging system Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From the recent discussion in the list I remembered that Ronald Joe Record in SCO said they would release their packaging system in a future. I asked again, and I received this: ________ Hello Pedro, We released the source to the pkgadd packaging tools (UnixWare's native packaging technology) in Skunkware 98. You can download these sources via: ftp://ftp.sco.com/skunkware/src/sysadmin/pkg-15.1-src.tar.gz I am trying to get the native OpenServer packaging technology released in source form. This is, in my opinion, a far superior C++ storage section Posix compliant technology (the SCO Software Manager also known as custom or custom+). ... ________ So, ...what's next ?? Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 15:45:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19247 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 15:45:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19242 for ; Tue, 22 Dec 1998 15:45:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01608; Tue, 22 Dec 1998 15:43:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812222343.PAA01608@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Templeton cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Memory holes for ISA device drivers In-reply-to: Your message of "Tue, 22 Dec 1998 16:36:20 GMT." <367FCA84.3DBE8085@atc.dera.gov.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 15:43:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > OS is 2.2.5 > > > Card is on ISA bus, preferably at 0xA00000. > > > > > > How do I create a (physical) memory hole for a card, > > > as the card holds 64k shared memory? > > > The target system BIOS does not support the 15-16M memory hole. > > > pmap_mapdev() maps physical to virtual memory, but does not > > > create a hole. > > > > > > How do I create a memory hole? > > > > This is chipset- and motherboard-specific. If you can't map the card > > into the ISA 'hole' at 0xa0000, then you're SOL short of building a > > custom PCI:ISA bridge (eg. using a PLX9050) and remapping it into PCI > > space. > > Thank you for your comments, Mike. > > But even on systems that support the ISA memory hole, this > restricts FreeBSD to effectively see only 15MB of RAM. > Surely this is undesirable? Unless I'm muchly mistaken, FreeBSD does support noncontiguous memory chunks. I'm not certain that the speculative probe stuff would get it right (your card would probably confuse it), but the vm86-based probe uses the BIOS, which knows about the hole. > Are there no software alternatives? Since you have to manipulate the motherboard hardware in order to create a hole which maps into the ISA memory space, and since we make no attempt to support motherboard chipsets to that level (the support issues alone would be horrific), the answer has to be no. > If not, then I guess I have to talk to MRBIOS and see if they > can supply me a BIOS which will do what I need. If this is a one-off application, and you know the exact hardware on which it will always be running, you have a much narrower problem set. At that level you can easily arrange to remove the 64k region from the VM and twiddle the hardware to chage the mappings (contingent on you having chipset documentation). This will hurt you later if you have to move platforms of course... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 16:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23538 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 16:16:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23533 for ; Tue, 22 Dec 1998 16:16:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA08122; Tue, 22 Dec 1998 16:16:49 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 16:16:49 -0800 (PST) From: Matthew Dillon Message-Id: <199812230016.QAA08122@apollo.backplane.com> To: David Greenman Cc: hackers@FreeBSD.ORG Subject: Re: vfs_bio / struct buf Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> It is also glaringly obvious that there are some hacks in there that :> we should probably work to remove. We ought to be able to fix NFS :> to not have to use the validoff/validend/dirtyoff/dirtyend junk, and :> we ought to be able to clean the system up such that it is possible :> to get rid of the bogus_page stuff and we should also be able to fix :> the bogus way pages are marked clean in the VFS layer ( rather then being :> marked clean in the device layer ). I may take this up post-3.0.1. : : valid/dirty off/end are there to reduce wire traffic, but aren't strictly :necessary. We would not want to remove it. : :-DG Right. I don't see how they reduce the wire traffic, though, since the page dirty and valid bits are already available with a DEV_BSIZE (i.e. 512 byte) granularity. Can't we just use the valid/dirty bits to optimize NFS operations? -Matt :David Greenman :Co-founder/Principal Architect, The FreeBSD Project : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 16:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23954 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 16:19:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23949 for ; Tue, 22 Dec 1998 16:19:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA08154; Tue, 22 Dec 1998 16:19:43 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 16:19:43 -0800 (PST) From: Matthew Dillon Message-Id: <199812230019.QAA08154@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: M_KERNEL in sys/malloc.h ??? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know what M_KERNEL is sys/malloc.h is supposed to do? It is used in precisely two places in the code as far as I can tell: vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { vm/swap_pager.c: spc->spc_bp = malloc(sizeof(*bp), M_TEMP, M_KERNEL); But kern/kern_malloc.c doesn't appear to really use it. On the otherhand I do see lots of absolute comparison of the malloc 'flags' to M_WAITOK (0) or M_NOWAIT which the use of M_KERNEL would interfere with. I can't tell if the side effects are something that are expected, or if the side effects are a bug. Anybody know? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 16:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26710 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 16:49:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from csmd2.cs.uni-magdeburg.de (csmd2.CS.Uni-Magdeburg.De [141.44.22.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26705 for ; Tue, 22 Dec 1998 16:48:58 -0800 (PST) (envelope-from jesse@prinz-atm.CS.Uni-Magdeburg.De) Received: from knecht.cs.uni-magdeburg.de (knecht [141.44.21.3]) by csmd2.cs.uni-magdeburg.de (8.9.1a/8.9.1) with ESMTP id BAA27369 for ; Wed, 23 Dec 1998 01:48:51 +0100 (MET) Received: (from jesse@localhost) by knecht.cs.uni-magdeburg.de (8.8.8+Sun/8.8.8) id BAA05273; Wed, 23 Dec 1998 01:47:40 +0100 (MET) From: Roland Jesse MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13952.15788.136215.866276@knecht> Date: Wed, 23 Dec 1998 01:47:40 +0100 (MET) To: freebsd-hackers@FreeBSD.ORG Subject: ACE 4.6 on -current (still) X-Mailer: VM 6.63 under 20.4 "Emerald" XEmacs Lucid Reply-To: Roland Jesse X-Organization: University of Magdeburg X-Pgp-Fingerprint: 5D 08 5A E3 B4 AA 68 C1 FF 67 06 29 62 DD 9A D7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I already fiddled around with this about a month ago but still couldn't figure out what I am missing. The problem is to get ACE (http://siesta.cs.wustl.edu/~schmidt/ACE.html) up and running on a 3.0-RELEASE machine. Thanks to Robert Schulhof who brought up the idea of using egcs 1.1 or g++ 2.8 instead of the default gcc 2.7.2. For my last tries I used egcs-2.91.60 out of the egcs-1.1.1 port from the ports collection. Robert provided his config files which worked for him but don't for me. They can be found at http://www.apfel.de/~jesse/config.h and http://www.apfel.de/~jesse/platform_macros.GNU. I put the output of the make process to http://www.apfel.de/~jesse/gmake.ACE.out. If anybody has an idea of how to avoid all the "conflicting type"s errors, I would very much appreciate a hint in the right direction. Thanks in advance, Roland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 17:20:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01236 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 17:20:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01224 for ; Tue, 22 Dec 1998 17:20:42 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id RAA20237; Tue, 22 Dec 1998 17:21:10 -0800 (PST) Message-Id: <199812230121.RAA20237@root.com> To: Matthew Dillon cc: hackers@FreeBSD.ORG Subject: Re: vfs_bio / struct buf In-reply-to: Your message of "Tue, 22 Dec 1998 16:16:49 PST." <199812230016.QAA08122@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 22 Dec 1998 17:21:10 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:> It is also glaringly obvious that there are some hacks in there that >:> we should probably work to remove. We ought to be able to fix NFS >:> to not have to use the validoff/validend/dirtyoff/dirtyend junk, and >:> we ought to be able to clean the system up such that it is possible >:> to get rid of the bogus_page stuff and we should also be able to fix >:> the bogus way pages are marked clean in the VFS layer ( rather then being >:> marked clean in the device layer ). I may take this up post-3.0.1. >: >: valid/dirty off/end are there to reduce wire traffic, but aren't strictly >:necessary. We would not want to remove it. >: >:-DG > > Right. I don't see how they reduce the wire traffic, though, since > the page dirty and valid bits are already available with a DEV_BSIZE > (i.e. 512 byte) granularity. Can't we just use the valid/dirty bits > to optimize NFS operations? The optimization is primarily for short writes (like 1 byte or a few bytes) so couldn't really be replaced by something that has 512 byte granularity without losing some performance. Granted, applications that show this behavior are probably broken, but that's another issue. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 17:55:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06666 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 17:55:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from copper.singnet.com.sg (copper.singnet.com.sg [165.21.7.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06658 for ; Tue, 22 Dec 1998 17:55:41 -0800 (PST) (envelope-from vrfight@singnet.com.sg) Received: from w98sysrec (tns01020.singnet.com.sg [165.21.186.90]) by copper.singnet.com.sg (8.9.1a/8.9.1) with SMTP id JAA29374 for ; Wed, 23 Dec 1998 09:55:33 +0800 (SGT) Message-ID: <003001be2e17$58174c80$5aba15a5@w98sysrec> From: "cyberbug" To: Date: Sun, 13 Dec 1998 23:19:17 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01BE26EF.01269EA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_003D_01BE26EF.01269EA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unscribe ------=_NextPart_000_003D_01BE26EF.01269EA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unscribe
------=_NextPart_000_003D_01BE26EF.01269EA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 19:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17189 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 19:41:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17172 for ; Tue, 22 Dec 1998 19:41:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA00797; Tue, 22 Dec 1998 19:31:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812230331.TAA00797@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Pedro F. Giffuni" cc: hackers@FreeBSD.ORG Subject: Re: New packaging system In-reply-to: Your message of "Tue, 22 Dec 1998 18:07:01 EST." <36802615.E5E264EB@bachue.usc.unal.edu.co> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Dec 1998 19:31:11 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From the recent discussion in the list I remembered that Ronald Joe > Record in SCO said they would release their packaging system in a > future. I asked again, and I received this: > ________ > Hello Pedro, > > We released the source to the pkgadd packaging tools > (UnixWare's native packaging technology) in Skunkware 98. > You can download these sources via: > > ftp://ftp.sco.com/skunkware/src/sysadmin/pkg-15.1-src.tar.gz > > I am trying to get the native OpenServer packaging technology > released in source form. This is, in my opinion, a far superior > C++ storage section Posix compliant technology (the SCO > Software Manager also known as custom or custom+). > > ... > ________ > > So, ...what's next ?? 8) I've suggested that our fearless SVr4 folks might want to look at this, as I'm fairly sure that the package format is relatively standard. I've also looked briefly at the code; there's quite a bit that will need to be rewritten (or possibly just cut out of its functionality), but on the whole the code is clean and the job looks quite feasible. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 22 20:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23420 for freebsd-hackers-outgoing; Tue, 22 Dec 1998 20:44:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23415 for ; Tue, 22 Dec 1998 20:44:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA10868; Tue, 22 Dec 1998 20:44:42 -0800 (PST) (envelope-from dillon) Date: Tue, 22 Dec 1998 20:44:42 -0800 (PST) From: Matthew Dillon Message-Id: <199812230444.UAA10868@apollo.backplane.com> To: David Greenman Cc: hackers@FreeBSD.ORG Subject: Re: vfs_bio / struct buf Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : The optimization is primarily for short writes (like 1 byte or a few bytes) :so couldn't really be replaced by something that has 512 byte granularity :without losing some performance. Granted, applications that show this behavior :are probably broken, but that's another issue. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project Ah. Hmmm. I see the problem... the buf's need some sort of native block size and NFS doesn't really have a native block size. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 03:02:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29507 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 03:02:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from oddbjorn.bdc.no (oddbjorn.bdc.no [193.69.204.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29491 for ; Wed, 23 Dec 1998 03:02:30 -0800 (PST) (envelope-from oddbjorn@oddbjorn.bdc.no) Received: (from oddbjorn@localhost) by oddbjorn.bdc.no (8.8.8/8.8.7) id MAA17654; Wed, 23 Dec 1998 12:02:19 +0100 (CET) (envelope-from oddbjorn) From: Oddbjorn Steffensen Message-Id: <199812231102.MAA17654@oddbjorn.bdc.no> Subject: Re: ACE 4.6 on -current (still) In-Reply-To: <13952.15788.136215.866276@knecht> from Roland Jesse at "Dec 23, 1998 1:47:40 am" To: jesse@prinz-atm.CS.Uni-Magdeburg.De Date: Wed, 23 Dec 1998 12:02:19 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I already fiddled around with this about a month ago but still > couldn't figure out what I am missing. I got it to work by using gcc 2.8 and uncommenting the // #define ACE_HAS_SIGWAIT line in $ACE_ROOT/ace/config-freebsd[-pthread].h. It gave some warnings during compilation, but nothing fatal. I haven't tested it beyond a few of the example programs, 'tho. This was on -CURRENT as of late November. > Roland -oddbjørn ______________________________________________________________________ http://www.tricknology.org/ FreeBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 07:42:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00620 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 07:42:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00615 for ; Wed, 23 Dec 1998 07:42:16 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id HAA02528; Wed, 23 Dec 1998 07:42:03 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id HAA09672; Wed, 23 Dec 1998 07:42:03 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 23 Dec 1998 07:42:03 -0800 (PST) Message-Id: <199812231542.HAA09672@vashon.polstra.com> To: mike@smith.net.au Subject: Re: New packaging system Newsgroups: polstra.freebsd.hackers In-Reply-To: <199812230331.TAA00797@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812230331.TAA00797@dingo.cdrom.com>, Mike Smith wrote: > > 8) I've suggested that our fearless SVr4 folks might want to look at > this, as I'm fairly sure that the package format is relatively standard. The format is documented in the SVR4 ABI book. The one I have is out of print. But I'd be happy to FAX or snail-mail the relevant pages to a couple of people. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 08:34:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06986 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 08:34:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ol.kyrnet.kg (ol.kyrnet.kg [195.254.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06979 for ; Wed, 23 Dec 1998 08:34:37 -0800 (PST) (envelope-from mlists@gizmo.kyrnet.kg) Received: from gizmo.kyrnet.kg (IDENT:mlists@gizmo.kyrnet.kg [195.254.160.13]) by ol.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id VAA04499; Wed, 23 Dec 1998 21:02:44 +0600 Received: from localhost (mlists@localhost) by gizmo.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id VAA11701; Wed, 23 Dec 1998 21:32:31 +0500 Date: Wed, 23 Dec 1998 21:32:29 +0500 (KGT) From: CyberPsychotic Reply-To: fygrave@tigerteam.net To: freebsd-hackers@FreeBSD.ORG, bsdi-users@bsdi.com Subject: LD_PRELOAD similarities. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello people, Some time ago I've written a library wrapper for some Linux boxes in my university, which are doing some additional checks for system(..); and exec*(,...) libc library functions before letting them being executed. (since we are running a restricted shell there, and limit the set of binaries, users could run, by a system table). Some time ago we had some FreeBSD and BSDi servers installed, where we aim to give students an access. I tried to port my library to FreeBSD but I got stuck alittle bit with LD_PRELOAD functionality: (*) is there a predefined library name, which would be preloaded all the time, when a dinamically-linked binary executed? (on linux it's /etc/ld.so.preload) (*) Is BSDi compatible with FreeBSD here? (seems not quite, since whether I try to set LD_PRELOAD variable on BSDi machine, it makes no effect). Thanks beforehands best regards Fyodor -- fygrave@tigerteam.net http://www.kalug.lug.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 09:28:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13452 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 09:28:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from vip.consys.com (Comobabi.ConSys.COM [209.141.107.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13446 for ; Wed, 23 Dec 1998 09:28:31 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.1/8.9.1) id KAA24942; Wed, 23 Dec 1998 10:28:22 -0700 (MST) Date: Wed, 23 Dec 1998 10:28:22 -0700 (MST) From: "Russell L. Carter" Message-Id: <199812231728.KAA24942@vip.consys.com> To: jesse@prinz-atm.CS.Uni-Magdeburg.De, oddbjorn@oddbjorn.bdc.no Subject: Re: ACE 4.6 on -current (still) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199812231102.MAA17654@oddbjorn.bdc.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, ELF ACE 4.6 works fine (passes all the tests, including netscvs) with the stock cc and egcs 1.1.1 too (modulo a couple of nits). More interesting (to me) though is getting TAO's MT_Cubit test working. The problem is entangled in the posix sched functions, and I am looking forward to trying out the LinuxThread stuff (which appears to have the required implementations) as soon as I boot the end of the year proposals out the door. I think FreeBSD-current is really close. Then it will be interesting to see how FreeBSD's CORBA performance compares with the systems examined in "An Empirical Evaluation of OS Support for Real-time CORBA Object Request Brokers" http://www.cs.wustl.edu/~schmidt/RT-OS.ps.gz I'm really itching to see how the FreeBSD sched_*(2) stuff affects the comparitive performance, especially the real-time aspects. My config files have evolved a bit from the stock ACE freebsd configs, maybe it would make sense to work together. I've been working with the cvsup'd sources (i.e. TAO-current, FreeBSD-current). I'm also looking forward to an 1836 DLUAN, compiling TAO abuses the heck out of my pitiful P6-200/128MB box :-). Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 11:19:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26447 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 11:19:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26442 for ; Wed, 23 Dec 1998 11:19:03 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id UAA04792; Wed, 23 Dec 1998 20:18:45 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id BAA01827; Tue, 22 Dec 1998 01:12:26 GMT (envelope-from son) Message-ID: <19981222011226.50577@breizh.prism.uvsq.fr> Date: Tue, 22 Dec 1998 01:12:26 +0000 From: Nicolas Souchu To: Julian Elischer Cc: Drew Baxter , hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp Subject: Re: Mainboard Monitor Probes (Linux port too hard?) References: <19981220165555.52107@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Julian Elischer on Sun, Dec 20, 1998 at 01:24:14PM -0800 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 20, 1998 at 01:24:14PM -0800, Julian Elischer wrote: > >Whistle has some basic support for the LM80 power-supply and environmental >monitor chip. When I port it back to the IICbus generic code it may >supply a basis to work on. > Sure. We'll also have to consider Linux stuff. It may be a hard issue since they rely on there /proc and module loadable mechanism. We should certainly use kld too. Another problem is the license... -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 11:19:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26482 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 11:19:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26457 for ; Wed, 23 Dec 1998 11:19:09 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id UAA29378; Wed, 23 Dec 1998 20:18:54 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id WAA00671; Mon, 21 Dec 1998 22:08:26 GMT (envelope-from son) Message-ID: <19981221220826.45773@breizh.prism.uvsq.fr> Date: Mon, 21 Dec 1998 22:08:26 +0000 From: Nicolas Souchu To: Drew Baxter Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp Subject: Re: LM75/78 Monitor Probes (was Re: Mainboard Monitor Probes) References: <4.1.19981220105116.00c01400@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <4.1.19981218001152.009ae100@genesis.ispace.com> <19981220165555.52107@breizh.prism.uvsq.fr> <4.1.19981220105116.00c01400@genesis.ispace.com> <19981220202106.49153@breizh.prism.uvsq.fr> <4.1.19981220134357.00a7f2d0@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <4.1.19981220134357.00a7f2d0@genesis.ispace.com>; from Drew Baxter on Sun, Dec 20, 1998 at 01:45:53PM -0500 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 20, 1998 at 01:45:53PM -0500, Drew Baxter wrote: > >The guys over at netroedge appear to have a rather tacky CGI going. .Seems >like they're moving things to/fro NFS to their web server, and using >GNUplot.. I think I saw a better graphing program somewhere. Just as long >as you can get numbers, comma delimited or something, throwing it through >perl would be a breeze. > We'll need some working code ASAP to let you try out this... anything better we'll be of course wellcome. I'll test there stuff, and GUIs they propose, then try to see if we can easly share userlevel code. > >--- >Drew "Droobie" Baxter >Network Admin/Professional Computer Nerd(TM) >OneEX: The OneNetwork Exchange, Bangor Maine USA >http://www.droo.orland.me.us > >PGP ID: 409A1F7D > > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 11:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29729 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 11:52:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29724 for ; Wed, 23 Dec 1998 11:52:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA03752; Wed, 23 Dec 1998 11:49:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812231949.LAA03752@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nicolas Souchu cc: hackers@FreeBSD.ORG Subject: Re: Mainboard Monitor Probes (Linux port too hard?) In-reply-to: Your message of "Tue, 22 Dec 1998 01:12:26 GMT." <19981222011226.50577@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 23 Dec 1998 11:49:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Dec 20, 1998 at 01:24:14PM -0800, Julian Elischer wrote: > > > >Whistle has some basic support for the LM80 power-supply and environmental > >monitor chip. When I port it back to the IICbus generic code it may > >supply a basis to work on. > > Sure. We'll also have to consider Linux stuff. Or at least basic compatibility with it, yes. > It may be a hard issue since they rely on there /proc and module > loadable mechanism. We should certainly use kld too. Indeed. So when will ppbus move to the new-bus model and become KLDable? > Another problem is the license... I think our designs are sufficiently different that all we're going to get from their code are ideas, so the licenses aren't necessarily a real problem... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 12:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04145 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 12:29:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ime.net (ime.net [209.90.192.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04134 for ; Wed, 23 Dec 1998 12:29:38 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4002.ime.net [209.90.195.12]) by ime.net (8.8.7/8.8.7) with SMTP id PAA10596; Wed, 23 Dec 1998 15:29:24 -0500 (EST) Message-Id: <4.1.19981223152411.00b4d2d0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 23 Dec 1998 15:27:00 -0500 To: Nicolas Souchu , Julian Elischer From: Drew Baxter Subject: Re: Mainboard Monitor Probes (Linux port too hard?) Cc: hackers@FreeBSD.ORG, Steve Friedrich , takawata@shidahara1.planet.kobe-u.ac.jp In-Reply-To: <19981222011226.50577@breizh.prism.uvsq.fr> References: <19981220165555.52107@breizh.prism.uvsq.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:12 AM 12/22/98 +0000, Nicolas Souchu wrote: > >Sure. We'll also have to consider Linux stuff. > The LM80 software may be able to be retrofitted with the LM78 code, I'm not sure how far off they are between each other, maybe they're compatible. >It may be a hard issue since they rely on there /proc and module >loadable mechanism. We should certainly use kld too. > >Another problem is the license... > The Linux stuff is GPL.. Perhaps it'd be more logical to use the Linux material only as a reference and not to extract code from it.. That'd be a sound way to get around that. Since most of the code does indeed rely on the /proc, that's about all it's good for. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 13:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08025 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 13:04:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08020 for ; Wed, 23 Dec 1998 13:04:27 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zsvRK-000I5eC; Wed, 23 Dec 1998 16:03:30 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: kernel panic To: hackers@FreeBSD.ORG Date: Wed, 23 Dec 1998 16:03:29 -0500 (EST) Cc: jkh@zippy.cdrom.com, tom@tomqnx.com, mike@dingo.cdrom.com, support@opensound.com, luigi@labinfo.iet.unipi.it, josh@ican.net X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM914447009-5162-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM914447009-5162-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Important business first - Merry Christmas! I hope that you and your loved ones have the best Xmas ever!! I would like to thank those folks that have sent me advice about my x11amp problems - very helpful... Now to kernel panics... I have been testing the heck out of this. All testing done with FreeBSD-current (elf) cvsuped at 22:30 hours EST on Dec.22. (make world & kernel) Guaranteed using the latest elf version of x11amp-0.8 as fetched by the ports/audio/x11amp port. VOXWare sound drivers: see attachments vox.x11amp, vox.dmesg, vox.sndstat ---------------- x11amp does NOT work with the standard VOXware drivers. It simply generates the messages in vox.x11amp. xmcd worked perfectly as a control program. Question re vox.sndstat > What are all those references to irq 1? Irq10 was specified... Luigi's sound drivers: attachments pcm.dmesg, pcm.sndstat ----------------- x11amp appears to work fine here as a normal user or as root BUT- Q1. WHat is the cause/effect of the sequencer1 error message in sndstat? Q2. Why does the driver generate a stream of "sorry, read DMA channel unavailable" messages? Q3. According to the code, pcm handles /dev/sndproc. How is it generated? MAKEDEV never heard of it. OSS sound drivers: attachments oss.dmesg, oss.sndstat, oss.soundon.log ----------------- xmcd works perfectly as a control program. x11amp starts, then in a very short time the system panics with a page fault. Kernel and core dumps can be made available via fast ftp to trusted souls that need the info. Send me e-mail. CONCLUSIONS: Originally, I thought that changes to FreeBSD were causing the panics, as I had previously been running x11amp with oss drivers for 3 days without problems. Mea Culpa - I had been running the previous 0.7 aout version. The problems started when I updated the port to the new elf version, which is supposed to work with standard FreeBSD and OSS sound drivers, according to the www.opensound.com WWW pages. I now believe that the x11amp elf port is very buggy. Regards, Tom --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=vox.x11amp Content-Description: vox.x11amp Content-Transfer-Encoding: 7bit Unable to get fragment size Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device Unable to open the audio device --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=vox.dmesg Content-Description: vox.dmesg Content-Transfer-Encoding: 7bit Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #16: Wed Dec 23 11:35:20 EST 1998 tom@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Calibrating clock(s) ... TSC clock: 200453471 Hz, i8254 clock: 1193178 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200453471 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00291000 - 0x03ff5fff, 64376832 bytes (15717 pages) config> FreeBSD Kernel Configuration Utility - Version 1.2 Type "help" for help or "visual" to go to the visual configuration interface (requires MGA/VGA display or serial terminal capable of displaying ANSI graphics). config> pnp 1 0 enable os port0 0x220 port1 0x300 port2 0x388 irq0 10 drq0 3 drq1 5 config> pnp 1 1 enable os port0 0x200 config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config> quit avail memory = 62599168 (61132K bytes) Found BIOS32 Service Directory header at 0xf00f9a20 Entry = 0xf04e0 (0xf00f04e0) Rev = 0 Len = 1 PCI BIOS entry at 0x510 DMI header at 0xf00f52a0 Version 2.0 Table at 0xf52ba, 33 entries, 1044 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcf10 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e000, size 4 ide_pci0: rev 0x01 on pci0.1.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000e002 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e00a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=3 map[0]: type 4, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.1.3 found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175346308 bytes/sec bzero() bandwidth = 88417329 bytes/sec sb0 at 0x220 irq 10 drq 3 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x300 on isa snd0: awe0 at 0x620 on isa awe0: opl0 at 0x388 on isa snd0: joy0 at 0x201 on isa joy0: joystick imasks: bio c008c040, tty c00710b2, net c00710b2 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c00710b2, net c00710b2 bpf: lo0 attached Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. PCM device 1 not installed. --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=vox.sndstat Content-Description: vox.sndstat Content-Transfer-Encoding: 7bit VoxWare Sound Driver:3.5-alpha15-970902 (Wed Aug 6 22:58:35 PDT 1997 Amancio Hasty@rah.star-gate.com) Config options: Installed drivers: Type 1: OPL-2/OPL-3 FM Type 2: SoundBlaster Type 6: SoundBlaster16 Type 25: AWE32 Synth Type 7: SB16 MIDI Card config: SoundBlaster at 0x220 irq 10 drq 3 SoundBlaster16 at 0xffffffff irq 1 drq 5 SB16 MIDI at 0x300 irq 1 AWE32 Synth at 0x620 irq 1 OPL-2/OPL-3 FM at 0x388 irq 1 Audio devices: 0: SoundBlaster 16 4.16 Synth devices: 0: AWE32-0.4.2c (RAM512k) 1: Yamaha OPL-3 Midi devices: 0: SoundBlaster 16 Midi Timers: 0: System clock Mixers: 0: SoundBlaster 1: AWE32 Equalizer --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=pcm.dmesg Content-Description: pcm.dmesg Content-Transfer-Encoding: 7bit Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #18: Wed Dec 23 12:29:17 EST 1998 tom@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Calibrating clock(s) ... TSC clock: 200454424 Hz, i8254 clock: 1193183 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200454424 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0027e000 - 0x03ff5fff, 64454656 bytes (15736 pages) config> FreeBSD Kernel Configuration Utility - Version 1.2 Type "help" for help or "visual" to go to the visual configuration interface (requires MGA/VGA display or serial terminal capable of displaying ANSI graphics). config> pnp 1 0 enable os port0 0x220 poprt1 \^H \^H\^H \^H\^H \^H\^H \^H\^H \^Hrt1 0x300 port2 0x388 irq0 10 drq0 3 drq1 5 config> pnp 1 1 enable os port0 0x200 config> pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 config> quit avail memory = 62676992 (61208K bytes) Found BIOS32 Service Directory header at 0xf00f9a20 Entry = 0xf04e0 (0xf00f04e0) Rev = 0 Len = 1 PCI BIOS entry at 0x510 DMI header at 0xf00f52a0 Version 2.0 Table at 0xf52ba, 33 entries, 1044 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcf10 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e000, size 4 ide_pci0: rev 0x01 on pci0.1.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000e002 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e00a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=3 map[0]: type 4, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.1.3 found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 pcm1 (SB16pnp sn 0x1641e094) at 0x220-0x22f irq 10 drq 3 flags 0x15 on isa Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 pcm0 not probed due to drq conflict with pcm1 at 3 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175284837 bytes/sec bzero() bandwidth = 88417329 bytes/sec imasks: bio c008c040, tty c00714b2, net c00714b2 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c00714b2, net c00714b2 bpf: lo0 attached Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=pcm.sndstat Content-Description: pcm.sndstat Content-Transfer-Encoding: 7bit FreeBSD Audio Driver (981002) Dec 23 1998 12:29:09 Installed devices: pcm1: at 0x220 irq 10 dma 3:5 sequencer1: at 0x388 (not functional) --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=oss.dmesg Content-Description: oss.dmesg Content-Transfer-Encoding: 7bit Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #19: Wed Dec 23 13:08:40 EST 1998 root@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200454518 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) config> quit avail memory = 62722048 (61252K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.1.0 ide_pci0: rev 0x01 on pci0.1.1 chip2: rev 0x01 on pci0.1.3 ncr0: rev 0x03 int a irq 9 on pci0.10.0 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] 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 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, unlocked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 15 seconds for SCSI devices to settle changing root device to da0s2a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] ffs_mountfs: superblock updated for soft updates OSS/FreeBSD loading, address = f45be020 --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=oss.sndstat Content-Description: oss.sndstat Content-Transfer-Encoding: 7bit OSS/FreeBSD 3.9.1i (C) 4Front Technologies 1996-1998 License serial number: E00000008 Open Sound System is licensed for evaluation purposes only. License will expire after: 05/1999 Options: ALL Kernel: FreeBSD 3.0-CURRENT #19: Wed Dec 23 13:08:40 EST 1998 root@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Card config: Generic PnP support Sound Blaster PnP at 0x220 irq 10 drq 3,5 OPL-2/OPL-3 FM at 0x388 SB MPU-401 at 0x300 irq 10 Emu 8000 MIDI Engine at 0x620 Audio devices: 0: Creative SB AWE64 PnP (4.16) (DUPLEX) 1: SB secondary device (DUPLEX) Synth devices: 0: Yamaha OPL-3 1: AWE32-0.4.2 (RAM512k) Midi devices: 0: Sound Blaster 16 Timers: 0: System clock Mixers: 0: Sound Blaster 1: AWE32 Equalizer --ELM914447009-5162-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=oss.soundon.log Content-Description: oss.soundon.log Content-Transfer-Encoding: 7bit Starting OSS/FreeBSD Wed 23 Dec 14:10:59 EST 1998 2:10PM up 3 mins, 1 user, load averages: 0.02, 0.01, 0.00 Module loaded as ID 0 ======= config ===== # Use soundconf to edit this file. /SECUREAUDIO OFF /IRQEXCLUDE 3 4 /DMAEXCLUDE 2 -CTL00C1 #Creative Sound Blaster AWE64 (type-2) /CONTROL run ~/sfxload ~/synthgm.sf2 /PNPDEV CTL0042 P220 P300 P388 I10 D3 D5 /PNPDEV CTL0022 P620 Pa20 Pe20 SBPNP OPNP P220 I10 D3 d5 SBMPU OPNP P300 OPL3 OPNP P388 PNP ============ Resources for PnP card #0 0000: 0e 8c 00 c1 94 e0 41 16 0e 0a 10 10 82 15 00 43 0010: 72 65 61 74 69 76 65 20 53 42 20 41 57 45 36 34 0020: 20 50 6e 50 15 0e 8c 00 42 00 82 05 00 41 75 64 0030: 69 6f 31 00 22 20 00 2a 02 08 2a 20 12 47 01 20 0040: 02 20 02 01 10 47 01 30 03 30 03 01 02 47 01 88 0050: 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 2a e0 12 0060: 47 01 20 02 80 02 20 10 47 01 00 03 30 03 30 02 0070: 47 01 88 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 0080: 2a e0 12 47 01 20 02 80 02 20 10 47 01 00 03 30 0090: 03 30 02 31 01 22 a0 06 2a 0b 08 2a e0 12 47 01 00a0: 20 02 80 02 20 10 31 01 22 a0 06 2a 0b 08 47 01 00b0: 20 02 80 02 20 10 47 01 00 03 30 03 30 02 47 01 00c0: 88 03 88 03 01 04 31 01 22 a0 06 2a 0b 08 47 01 00d0: 20 02 80 02 20 10 47 01 00 03 30 03 30 02 31 01 00e0: 22 a0 06 2a 0b 08 47 01 20 02 80 02 20 10 31 02 00f0: 22 a0 06 2a 0b 08 2a e0 12 47 01 20 02 80 02 20 0100: 10 47 01 00 03 30 03 10 02 47 01 88 03 94 03 04 0110: 04 38 15 0e 8c 70 02 00 1c 41 d0 b0 2f 82 04 00 0120: 47 61 6d 65 31 00 47 01 00 02 00 02 01 08 31 01 0130: 47 01 00 02 08 02 08 08 38 15 0e 8c 00 22 00 82 0140: 09 00 57 61 76 65 54 61 62 6c 65 31 00 47 01 20 0150: 06 20 06 01 04 31 01 47 01 20 06 80 06 20 04 38 0160: 79 11 ==================== The following OSS options are required for your current hardware configuration: AWE Remember to select them while ordering the permanent OSS license. OSS/FreeBSD 3.9.1i (C) 4Front Technologies 1996-1998 License serial number: E00000008 Open Sound System is licensed for evaluation purposes only. License will expire after: 05/1999 Options: ALL Kernel: FreeBSD 3.0-CURRENT #19: Wed Dec 23 13:08:40 EST 1998 root@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Card config: Generic PnP support Sound Blaster PnP at 0x220 irq 10 drq 3,5 OPL-2/OPL-3 FM at 0x388 SB MPU-401 at 0x300 irq 10 Emu 8000 MIDI Engine at 0x620 Audio devices: 0: Creative SB AWE64 PnP (4.16) (DUPLEX) 1: SB secondary device (DUPLEX) Synth devices: 0: Yamaha OPL-3 1: AWE32-0.4.2 (RAM512k) Midi devices: 0: Sound Blaster 16 Timers: 0: System clock Mixers: 0: Sound Blaster 1: AWE32 Equalizer ========== dmesg printout follows ======== Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #19: Wed Dec 23 13:08:40 EST 1998 root@darkstar.tomqnx.com:/usr/src/sys/compile/DARKSTAR Calibrating clock(s) ... TSC clock: 200454584 Hz, i8254 clock: 1193183 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 200454584 Hz CPU: Pentium/P55C (200.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping=4 Features=0x8001bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00273000 - 0x03ff5fff, 64499712 bytes (15747 pages) config> quit avail memory = 62722048 (61252K bytes) Found BIOS32 Service Directory header at 0xf00f9a20 Entry = 0xf04e0 (0xf00f04e0) Rev = 0 Len = 1 PCI BIOS entry at 0x510 DMI header at 0xf00f52a0 Version 2.0 Table at 0xf52ba, 33 entries, 1044 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fcf10 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e000, size 4 ide_pci0: rev 0x01 on pci0.1.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000e002 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000e00a found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=3 map[0]: type 4, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.1.3 found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base 0000d400, size 8 map[1]: type 1, range 32, base e7000000, size 8 map[2]: type 1, range 32, base e6800000, size 12 ncr0: rev 0x03 int a irq 9 on pci0.10.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x5333, dev=0x8a01, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x01 int a irq 11 on pci0.11.0 Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x1641e094 Comp ID: PNPb02f [0x2fb0d041] PnP: override config for CSN 1 LDN 0 vend_id 0xc1008c0e port 0x0220 0x0300 0x0388 0x0000 irq 10:0 drq 3:5 en 1 PnP: override config for CSN 1 LDN 1 vend_id 0xc1008c0e port 0x0200 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 PnP: override config for CSN 1 LDN 2 vend_id 0xc1008c0e port 0x0620 0x0000 0x0000 0x0000 irq 0:0 drq 4:4 en 1 Called nullpnp_probe with tag 0x00000001, type 0xc1008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c4644, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordy wcd0: 689KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm audio disc loaded, locked 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 5 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:62:a5:65 bpf: ep0 attached npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175346308 bytes/sec bzero() bandwidth = 88417329 bytes/sec imasks: bio c008c040, tty c00710b2, net c00710b2 BIOS Geometries: 0:020afe3f 0..522=523 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fd893f 0..1021=1022 cylinders, 0..137=138 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c00710b2, net c00710b2 bpf: lo0 attached Linux-ELF exec handler installed Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe5:ncr0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ncr0:0:5:0): ILLEGAL REQUEST asc:24,0 (probe5:ncr0:0:5:0): Invalid field in CDB sks:c0,1 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled pass1 at ncr0 bus 0 target 5 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [176780 x 2048 byte records] Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s2a da0s1: type 0x6, start 63, end = 1025891, size 1025829 : OK da0s2: type 0xa5, start 1025892, end = 8885267, size 7859376 : OK WARNING: / was not properly dismounted wd0s1: type 0xb, start 63, end = 6152894, size 6152832 : OK wd0s2: type 0x82, start 6152895, end = 8353799, size 2200905 : OK ffs_mountfs: superblock updated for soft updates OSS/FreeBSD loading, address = f45af020 --ELM914447009-5162-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 13:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10657 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 13:30:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10651 for ; Wed, 23 Dec 1998 13:30:01 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id NAA04623 for ; Wed, 23 Dec 1998 13:29:26 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id NAA13848 for hackers@freebsd.org; Wed, 23 Dec 1998 13:30:38 -0800 (PST) From: Gary Kline Message-Id: <199812232130.NAA13848@tao.thought.org> Subject: observation.... To: hackers@FreeBSD.ORG Date: Wed, 23 Dec 1998 13:30:38 -0800 (PST) Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This might be better sent to -question except that it really isn't a question; just an observation. Or discovery. For at least two years, on rare occasions, my system would freeze up. Power-cyclying was the only way back from this sudden death. It just happened again and I thought: Nuts!! But I rlogged in from my other cconsole to find things entirely alive. And I found the culprit. xscreensaver; ps ax shows that it spawned decayscreen. I was running netscape; killed it. Nada; then killed decayscreen and instantly every xterm came back to life. So one more of Life's mysteries solved; it wasn't the kernel. Hmm. gary PS: I'm going to be un-reachable for the next N days as my company moves across town. The network is going down 24dec98 and back up:: dunno. -g -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 14:01:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13380 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 14:01:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bursa01.cuneydi.com (bursa01.cuneydi.com [206.109.102.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13375 for ; Wed, 23 Dec 1998 14:01:31 -0800 (PST) (envelope-from cucu@cuneydi.com) Received: from ibmlaptop.texascommerce.com ([206.109.102.140]) by bursa01.cuneydi.com (Netscape Mail Server v1.1) with SMTP id AAA520 for ; Wed, 23 Dec 1998 16:00:37 -0600 From: "cucu" To: Subject: kernel on boot flpy Date: Wed, 23 Dec 1998 16:03:01 -0600 Message-ID: <001001be2ec0$01d530e0$8c666dce@ibmlaptop.texascommerce.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can I use the std floppy image (3.0R) and replace the kernel with a custom kernel and use this disk? Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 15:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22503 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 15:31:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA22497 for ; Wed, 23 Dec 1998 15:30:59 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 25018 invoked from network); 23 Dec 1998 23:24:09 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 23 Dec 1998 23:24:09 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id SAA26271; Wed, 23 Dec 1998 18:24:01 -0500 (EST) Message-Id: <199812232324.SAA26271@y.dyson.net> Subject: Re: questions/problems with vm_fault() in Stable In-Reply-To: <367F9D58.D755DAB0@bachue.usc.unal.edu.co> from "Pedro F. Giffuni" at "Dec 22, 98 08:23:36 am" To: pfgiffun@bachue.usc.unal.edu.co (Pedro F. Giffuni) Date: Wed, 23 Dec 1998 18:24:01 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pedro F. Giffuni said: > In this thread I've heard good comment on UVM and also that there is not > anyone really in charge of the VM. > > Would this indicate that we want UVM ?? Chuck Cranor's papers say a port > could be done but, as I understand, our VM is faster. > In *no way* is UVM done. It is still missing merged VM buffer cache and is not productized (from a performance standpoint.) As the optimizations for performance are done, the complexities also arise. From a tutorial standpoint, UVM might be good because of it's cleanliness -- however the performance is the critical thing that distinguishes FreeBSD from the alternatives. Almost any negative allegations as to portability regarding the FreeBSD VM are incorrect and mostly spin. There are features in the FreeBSD VM that take advantage of CPU capabilities that are inherently non-portable. However, those features are optional, and not necessary for correct operation. I suspect that as the Alpha platform is optimized, the VM code will be tuned to support that super-well also. Geesh, there is already support in FreeBSD for non-copy read/write to/from the buffer cache also. It isn't complete, but is there. It only takes someone to finish the job (which I was in the middle of.) On some machines, that feature would definitely be a mis-feature, but on the X86, it would be useful. Also, the FreeBSD VFS/VM code already supports the ability to have non-mapped buffers (and has for 2years.) There is alot in there that might make the complexity look excessive, but that is only because there are features in there that are almost ready to go. I suspect that if there is a concentrated effort on UVM for a couple of years, by a couple of people, it will be as functional as FreeBSD VM. At that point, it might be worthwhile to adopt it. For an opinion about using a FreeBSD VM vs. a UVM development environment -- use both for awhile, and then notice the very significant (noticible) differences in performance. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 16:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03457 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 16:46:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03451 for ; Wed, 23 Dec 1998 16:46:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA31256; Wed, 23 Dec 1998 16:46:11 -0800 (PST) To: "cucu" cc: hackers@FreeBSD.ORG Subject: Re: kernel on boot flpy In-reply-to: Your message of "Wed, 23 Dec 1998 16:03:01 CST." <001001be2ec0$01d530e0$8c666dce@ibmlaptop.texascommerce.com> Date: Wed, 23 Dec 1998 16:46:10 -0800 Message-ID: <31253.914460370@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can I use the std floppy image (3.0R) and replace the kernel with a custom > kernel > and use this disk? Yes, just so long as options MFS_ROOT are in the custom kernel. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 17:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07099 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 17:23:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07094 for ; Wed, 23 Dec 1998 17:23:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA04120; Wed, 23 Dec 1998 17:23:36 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA00351; Wed, 23 Dec 1998 17:23:36 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 23 Dec 1998 17:23:36 -0800 (PST) Message-Id: <199812240123.RAA00351@vashon.polstra.com> To: fygrave@tigerteam.net Subject: Re: LD_PRELOAD similarities. Newsgroups: polstra.freebsd.hackers In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , CyberPsychotic wrote: > > (*) is there a predefined library name, which would be preloaded all the > time, when a dinamically-linked binary executed? (on linux it's > /etc/ld.so.preload) No, we don't have anything like that. > (*) Is BSDi compatible with FreeBSD here? (seems not quite, since > whether I try to set LD_PRELOAD variable on BSDi machine, it makes > no effect). That's really a BSDi question, and I don't know the answer to it. I believe that our LD_PRELOAD support does the "standard" thing. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 17:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08822 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 17:42:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08801; Wed, 23 Dec 1998 17:42:17 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA10070; Thu, 24 Dec 1998 12:11:55 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA14661; Thu, 24 Dec 1998 12:11:57 +1030 (CST) Message-ID: <19981224121157.D12346@freebie.lemis.com> Date: Thu, 24 Dec 1998 12:11:57 +1030 From: Greg Lehey To: ku man , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: multiple routers for multiple NICs References: <19981222203646.27271.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981222203646.27271.qmail@hotmail.com>; from ku man on Tue, Dec 22, 1998 at 12:36:45PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 22 December 1998 at 12:36:45 -0800, ku man wrote: > I have a box running FreeBSD 3.0 with 2 Intel 10/100 PRO ethernet > adapters. Instead of using a single default router, is there a way to > configure the system so that traffic on each NIC will be routed through > a NIC-specific router? That is, how can I associate a different router > for each NIC? Can you explain your net topography? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 17:55:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09885 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 17:55:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bursa01.cuneydi.com (bursa01.cuneydi.com [206.109.102.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09879 for ; Wed, 23 Dec 1998 17:55:57 -0800 (PST) (envelope-from cucu@cuneydi.com) Received: from ibmlaptop.texascommerce.com ([206.109.102.140]) by bursa01.cuneydi.com (Netscape Mail Server v1.1) with SMTP id AAA466; Wed, 23 Dec 1998 19:55:05 -0600 From: "cucu" To: "Jordan K. Hubbard" Cc: Subject: RE: kernel on boot flpy Date: Wed, 23 Dec 1998 19:57:26 -0600 Message-ID: <001301be2ee0$c1831d60$8c666dce@ibmlaptop.texascommerce.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <31253.914460370@zippy.cdrom.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ok. I boot with the floppy with the custom kernel, detects everything and panics with init not found panic init reboot Any pointers? > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Wednesday, December 23, 1998 6:46 PM > To: cucu > Cc: hackers@FreeBSD.ORG > Subject: Re: kernel on boot flpy > > > > Can I use the std floppy image (3.0R) and replace the kernel > with a custom > > kernel > > and use this disk? > > Yes, just so long as options MFS_ROOT are in the custom kernel. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 21:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11274 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 21:28:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ol.kyrnet.kg (ol.kyrnet.kg [195.254.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11184 for ; Wed, 23 Dec 1998 21:28:02 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from gizmo.kyrnet.kg (IDENT:fygrave@gizmo.kyrnet.kg [195.254.160.13]) by ol.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id JAA05336; Thu, 24 Dec 1998 09:55:59 +0600 Received: from localhost (fygrave@localhost) by gizmo.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id KAA16269; Thu, 24 Dec 1998 10:25:46 +0500 X-Authentication-Warning: gizmo.kyrnet.kg: fygrave owned process doing -bs Date: Thu, 24 Dec 1998 10:25:46 +0500 (KGT) From: CyberPsychotic X-Sender: fygrave@gizmo.kyrnet.kg To: John Polstra cc: hackers@FreeBSD.ORG Subject: Re: LD_PRELOAD similarities. In-Reply-To: <199812240123.RAA00351@vashon.polstra.com> Message-ID: Confirm-receipt-to: fygrave@usa.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ~ No, we don't have anything like that. oh.. well, pity. Then I will probably have to change SHELLLVL to 2, so user will not be able to modify LD_PRELOAD setting, right? ~ > (*) Is BSDi compatible with FreeBSD here? (seems not quite, since ~ > whether I try to set LD_PRELOAD variable on BSDi machine, it makes ~ > no effect). ~ ~ That's really a BSDi question, and I don't know the answer to it. I ~ believe that our LD_PRELOAD support does the "standard" thing. ~ Yep. Probably. I just hoped some people here expirienced with both FreeBSD and BSDi clone. Well, manual seems to mention LD_PRELOAD thing, but ktrace doesn't show that it reacts on it in any sort of way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 21:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13477 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 21:51:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ol.kyrnet.kg (ol.kyrnet.kg [195.254.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13463 for ; Wed, 23 Dec 1998 21:51:08 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from gizmo.kyrnet.kg (IDENT:fygrave@gizmo.kyrnet.kg [195.254.160.13]) by ol.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id KAA05430 for ; Thu, 24 Dec 1998 10:19:36 +0600 Received: from localhost (fygrave@localhost) by gizmo.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id KAA16444 for ; Thu, 24 Dec 1998 10:49:23 +0500 X-Authentication-Warning: gizmo.kyrnet.kg: fygrave owned process doing -bs Date: Thu, 24 Dec 1998 10:49:23 +0500 (KGT) From: CyberPsychotic X-Sender: fygrave@gizmo.kyrnet.kg To: freebsd-hackers@FreeBSD.ORG Subject: Re: LD_PRELOAD equvalency (fwd) Message-ID: Confirm-receipt-to: fygrave@usa.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding my post yesterday. Just wondering if anyone gets a feeling that BSDi and guys from Richmond have something similar? ;-) ---------- Forwarded message ---------- Date: Wed, 23 Dec 1998 22:37:12 -0700 (MST) From: Phil Duclos To: fygrave@tigerteam.net Subject: Re: LD_PRELOAD equvalency According to CyberPsychotic: > >On Wed, 23 Dec 1998 seebs@plethora.net wrote: > >thanks for quick responce. > >~ >~ Unfortunately, I am tragically unaware of the significance of "LD_PRELOAD". >~ Could you, perchance, tell us what it does elsewhere, that we may better >~ suggest what you want? > > >~ Also, you should identify the version you're using. >~ > >BSDi 3.1 server. No real dynamic linking in 3.1, sorry. Use 4.0. Phil Duclos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 23 21:55:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13989 for freebsd-hackers-outgoing; Wed, 23 Dec 1998 21:55:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13982 for ; Wed, 23 Dec 1998 21:55:03 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id EAA04022; Thu, 24 Dec 1998 04:02:26 +0100 From: Luigi Rizzo Message-Id: <199812240302.EAA04022@labinfo.iet.unipi.it> Subject: Re: kernel panic To: tom@tomqnx.com (Tom Torrance at home) Date: Thu, 24 Dec 1998 04:02:26 +0100 (MET) Cc: hackers@FreeBSD.ORG, jkh@zippy.cdrom.com, tom@tomqnx.com, mike@dingo.cdrom.com, support@opensound.com, josh@ican.net In-Reply-To: from "Tom Torrance at home" at Dec 23, 98 04:03:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BUT- > Q1. WHat is the cause/effect of the sequencer1 error message in sndstat? is not an error message, just a notification that the hardware is there but the software is not ready yet. > Q2. Why does the driver generate a stream of "sorry, read DMA channel > unavailable" messages? not sure. either misconfiguration of the card, or too verbose msgs in the kernel. > Q3. According to the code, pcm handles /dev/sndproc. How is it generated? > MAKEDEV never heard of it. i don't even know what sndproc does! cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 00:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00517 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 00:08:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA00512 for ; Thu, 24 Dec 1998 00:08:37 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 10659 invoked from network); 24 Dec 1998 08:08:23 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 24 Dec 1998 08:08:23 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id DAA46738; Thu, 24 Dec 1998 03:08:18 -0500 (EST) Message-Id: <199812240808.DAA46738@y.dyson.net> Subject: Re: M_KERNEL in sys/malloc.h ??? In-Reply-To: <199812230019.QAA08154@apollo.backplane.com> from Matthew Dillon at "Dec 22, 98 04:19:43 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 24 Dec 1998 03:08:18 -0500 (EST) Cc: hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon said: > Does anyone know what M_KERNEL is sys/malloc.h is supposed to do? It > is used in precisely two places in the code as far as I can tell: > > vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { > vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { > vm/swap_pager.c: spc->spc_bp = malloc(sizeof(*bp), M_TEMP, M_KERNEL); > > But kern/kern_malloc.c doesn't appear to really use it. On the otherhand > I do see lots of absolute comparison of the malloc 'flags' to M_WAITOK > (0) or M_NOWAIT which the use of M_KERNEL would interfere with. I can't > tell if the side effects are something that are expected, or if the > side effects are a bug. > > Anybody know? > As I remember, M_KERNEL means that it really needs memory. waiting for memory is bad, and dip deeply into the page reserves. Normally, the malloc (in vm_kern) code will only dip into the interrupt accessible free pages. The M_KERNEL allows it to dip into all of the pages. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 00:13:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00821 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 00:13:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA00815 for ; Thu, 24 Dec 1998 00:13:29 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 14517 invoked from network); 24 Dec 1998 08:13:14 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 24 Dec 1998 08:13:14 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id DAA46747; Thu, 24 Dec 1998 03:13:11 -0500 (EST) Message-Id: <199812240813.DAA46747@y.dyson.net> Subject: Re: questions/problems with vm_fault() in Stable In-Reply-To: from Julian Elischer at "Dec 20, 98 03:41:59 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 24 Dec 1998 03:13:11 -0500 (EST) Cc: bf20761@binghamton.edu, freebsd-hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer said: > Are you commenting the source as you go? > Are yu writing a document on these things? > you seem to be going through the entire kernel :-) > > If so. can we get a copy :-) > I would also be willing to review it (to help.) > > > > (4) The comment in the source code says that the pager can move a page, so > > we must relookup the page by calling vm_page_lookup(). How could this be > > the case? Why move the page? > > Device pager allocates it's own page as needed. Specifically, hardware VM pseudo devices have more freedom with this (questionable) ability. > > > (5) The comment in the source code says that we do not COW read-only region > > on a user wire. "If we do not make this restriction, the bookkeeping would > > be nearly impossible." Can anyone explain this for me? > > As I remember, it is quite complex to handle it correctly for debuggers and other such situations. > > > (6) The comment in the source code says map entries may be pageable. I really > > doubt this because vm_map_entry_create() always allocates wired down memory > > for new map entries and enter them into pmap immediately. > That is quite an anachronism, and that comment should be totally ignored. > > > > (7) The comment in the source code says pmap_enter() may cause other faults. > > I can not see any reason for this to happen. > > It doesn't on the X86, but *might* elsewhere. At one time I thought about doing that, but found it to be evil (due to possible deadlocks and lock handling.) On the X86, I handled the issue(s) differently. > > > I am just wondering how this important routine in VM system can have these > > imperfect things (except (4) through (7)). I hope I am wrong. Please help > > me out with understanding of these points. > > The code isn't perfect, but there are lots of subtile reasons things being the way that they are, and also sometimes bugs that just don't get exercised. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 07:22:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11737 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 07:22:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from acheron.middleboro.ma.us (gbliss.ne.mediaone.net [24.128.162.149]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11723 for ; Thu, 24 Dec 1998 07:22:43 -0800 (PST) (envelope-from mason@acheron.middleboro.ma.us) Received: (from mason@localhost) by acheron.middleboro.ma.us (8.9.1/8.9.1) id KAA15046 for freebsd-hackers@freebsd.org; Thu, 24 Dec 1998 10:22:31 -0500 (EST) Date: Thu, 24 Dec 1998 10:22:30 -0500 From: Mason Loring Bliss To: freebsd-hackers@FreeBSD.ORG Subject: SCSI question... Message-ID: <19981224102230.T365@acheron.middleboro.ma.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, all. My company is trying to support FreeBSD, and it's been left to me to figure out a couple things without having a FreeBSD box handy. 1) Our box is a multi-LUN SCSI device. Are multiple LUNs supported in FreeBSD by default? (A complication is that I don't know what version of FreeBSD our client runs. I've been told -current, but I doubt that. I'm guessing 2.0.x. I will find out for sure on Monday, but getting a jump over the weekend would be cool.) 2) Can I access multiple LUNs through individual device files? If so, can I assume that the kernel will pop up messages saying what files have devices attached? 3) Should I have the client do "/dev/MAKEDEV all" before rebooting with the device attached? That would do what I want under NetBSD, but I'm not quite sure about FreeBSD. I'll probably have a FreeBSD box at both work and home before too long, but at the moment I'm sort of groping in the dark to figure some of this out. I want to know as much as possible before leading my client through an install on Monday. Thanks in advance! PS: Replies to the list are welcome. I'm subscribed, so I'll see 'em here. -- Mason Loring Bliss..mason@acheron.middleboro.ma.us..acheron.ddns.org/mason/ "In the drowsy dark cave of the mind dreams build their nest with fragments dropped from day's caravan."--Rabindranath Tagore..awake ? sleep : dream; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 09:21:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24605 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 09:21:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24600 for ; Thu, 24 Dec 1998 09:21:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA27982; Thu, 24 Dec 1998 09:21:01 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Dec 1998 09:21:01 -0800 (PST) From: Matthew Dillon Message-Id: <199812241721.JAA27982@apollo.backplane.com> To: "John S. Dyson" Cc: hackers@FreeBSD.ORG Subject: Re: M_KERNEL in sys/malloc.h ??? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon said: :> Does anyone know what M_KERNEL is sys/malloc.h is supposed to do? It :> is used in precisely two places in the code as far as I can tell: :> :> vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { :> vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { :> vm/swap_pager.c: spc->spc_bp = malloc(sizeof(*bp), M_TEMP, M_KERNEL); :> :> But kern/kern_malloc.c doesn't appear to really use it. On the otherhand :> I do see lots of absolute comparison of the malloc 'flags' to M_WAITOK :> (0) or M_NOWAIT which the use of M_KERNEL would interfere with. I can't :> tell if the side effects are something that are expected, or if the :> side effects are a bug. :> :> Anybody know? :> :As I remember, M_KERNEL means that it really needs memory. waiting :for memory is bad, and dip deeply into the page reserves. Normally, the :malloc (in vm_kern) code will only dip into the interrupt accessible :free pages. The M_KERNEL allows it to dip into all of the pages. Ok, I'll document it then and make sure it operates the same with my cleanups. -Matt :John | Never try to teach a pig to sing, :dyson@iquest.net | it makes one look stupid Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 09:48:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27984 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 09:48:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from m4.stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27978 for ; Thu, 24 Dec 1998 09:48:34 -0800 (PST) (envelope-from ken@stox.sa.enteract.com) Received: from localhost (localhost.stox.sa.enteract.com [127.0.0.1]) by m4.stox.sa.enteract.com (8.9.1/8.6.12) with ESMTP id LAA00631; Thu, 24 Dec 1998 11:48:22 -0600 (CST) Date: Thu, 24 Dec 1998 11:48:21 -0600 (CST) From: "Kenneth P. Stox" Reply-To: stox@enteract.com To: Mason Loring Bliss cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI question... In-Reply-To: <19981224102230.T365@acheron.middleboro.ma.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1) Our box is a multi-LUN SCSI device. Are multiple LUNs supported in FreeBSD > by default? (A complication is that I don't know what version of FreeBSD our > client runs. I've been told -current, but I doubt that. I'm guessing 2.0.x. > I will find out for sure on Monday, but getting a jump over the weekend would > be cool.) I can't speak on 2.X, but 3.X supports them just fine. I should note that my experience with multiple LUN's has been limited to a CD drive. > > 2) Can I access multiple LUNs through individual device files? If so, can I > assume that the kernel will pop up messages saying what files have devices > attached? Yes. I have been using a 7 CD changer for some time with no problems. They come up as cd0 through cd6. I have used with with both Adaptec and NCR controllers. > 3) Should I have the client do "/dev/MAKEDEV all" before rebooting with the > device attached? That would do what I want under NetBSD, but I'm not quite > sure about FreeBSD. Since, you don't mention what kind of multiple LUN device you are talking about, that is hard to answer. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 12:08:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14529 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 12:08:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14524 for ; Thu, 24 Dec 1998 12:08:29 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA18231; Thu, 24 Dec 1998 11:59:51 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda18228; Thu Dec 24 19:59:49 1998 Date: Thu, 24 Dec 1998 11:59:46 -0800 (PST) From: Julian Elischer To: Matthew Dillon cc: "John S. Dyson" , hackers@FreeBSD.ORG Subject: Re: M_KERNEL in sys/malloc.h ??? In-Reply-To: <199812241721.JAA27982@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would rename it to M_RESERVED or something that indicates that this is a request that is allowed dip into the emergency reserves to satisfy the request. On Thu, 24 Dec 1998, Matthew Dillon wrote: > > :Matthew Dillon said: > :> Does anyone know what M_KERNEL is sys/malloc.h is supposed to do? It > :> is used in precisely two places in the code as far as I can tell: > :> > :> vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { > :> vm/default_pager.c: if (swap_pager_swp_alloc(object, M_KERNEL) != 0) { > :> vm/swap_pager.c: spc->spc_bp = malloc(sizeof(*bp), M_TEMP, M_KERNEL); > :> > :> But kern/kern_malloc.c doesn't appear to really use it. On the otherhand > :> I do see lots of absolute comparison of the malloc 'flags' to M_WAITOK > :> (0) or M_NOWAIT which the use of M_KERNEL would interfere with. I can't > :> tell if the side effects are something that are expected, or if the > :> side effects are a bug. > :> > :> Anybody know? > :> > :As I remember, M_KERNEL means that it really needs memory. waiting > :for memory is bad, and dip deeply into the page reserves. Normally, the > :malloc (in vm_kern) code will only dip into the interrupt accessible > :free pages. The M_KERNEL allows it to dip into all of the pages. > > Ok, I'll document it then and make sure it operates the same with my > cleanups. > > -Matt > > :John | Never try to teach a pig to sing, > :dyson@iquest.net | it makes one look stupid > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 12:17:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15166 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 12:17:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA15161 for ; Thu, 24 Dec 1998 12:17:44 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 19989 invoked from network); 24 Dec 1998 20:17:29 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 24 Dec 1998 20:17:29 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id PAA50847; Thu, 24 Dec 1998 15:17:29 -0500 (EST) Message-Id: <199812242017.PAA50847@y.dyson.net> Subject: Re: M_KERNEL in sys/malloc.h ??? In-Reply-To: from Julian Elischer at "Dec 24, 98 11:59:46 am" To: julian@whistle.com (Julian Elischer) Date: Thu, 24 Dec 1998 15:17:29 -0500 (EST) Cc: dillon@apollo.backplane.com, dyson@iquest.net, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer said: > > I would rename it to M_RESERVED or something that indicates > that this is a request that is allowed dip into the emergency reserves > to satisfy the request. > > > :> > > :As I remember, M_KERNEL means that it really needs memory. waiting > > :for memory is bad, and dip deeply into the page reserves. Normally, the > > :malloc (in vm_kern) code will only dip into the interrupt accessible > > :free pages. The M_KERNEL allows it to dip into all of the pages. > > > That isn't what it really does. In reality, malloc normally grabs memory from the interrupt available queues. The M_KERNEL relaxes the restriction so that more memory is available. M_KERNEL cannot be used from interrupt time. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 12:23:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15469 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 12:23:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA15464 for ; Thu, 24 Dec 1998 12:23:31 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 27453 invoked from network); 24 Dec 1998 20:23:17 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 24 Dec 1998 20:23:17 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id PAA50865; Thu, 24 Dec 1998 15:23:16 -0500 (EST) Message-Id: <199812242023.PAA50865@y.dyson.net> Subject: Re: M_KERNEL in sys/malloc.h ??? In-Reply-To: <199812242017.PAA50847@y.dyson.net> from "John S. Dyson" at "Dec 24, 98 03:17:29 pm" To: dyson@iquest.net Date: Thu, 24 Dec 1998 15:23:16 -0500 (EST) Cc: julian@whistle.com, dillon@apollo.backplane.com, dyson@iquest.net, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson said: > Julian Elischer said: > > > > I would rename it to M_RESERVED or something that indicates > > that this is a request that is allowed dip into the emergency reserves > > to satisfy the request. > > > > > :> > > > :As I remember, M_KERNEL means that it really needs memory. waiting > > > :for memory is bad, and dip deeply into the page reserves. Normally, the > > > :malloc (in vm_kern) code will only dip into the interrupt accessible > > > :free pages. The M_KERNEL allows it to dip into all of the pages. > > > > > > That isn't what it really does. In reality, malloc normally grabs > memory from the interrupt available queues. The M_KERNEL relaxes the > restriction so that more memory is available. M_KERNEL cannot > be used from interrupt time. > Following up: M_WAITOK -- Get any pages, but block if you cannot get them M_NOWAIT -- Get only interrupt available pages, but don't block. M_KERNEL -- Get any pages, but don't block M_KERNEL is used to keep the VM from deadlocking, and should mostly be used in the pagers. M_WAITOK should normally be used in the non-interrupt part of the kernel except when M_KERNEL is more appropriate. M_NOWAIT should normally be used in the interrupt part of the kernel, but can be used elsewhere. If you rename, you might want to call M_KERNEL: M_VMREQ or somesuch to note that this is a vm deadlock avoidance compromise. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 13:48:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24380 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 13:48:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24351 for ; Thu, 24 Dec 1998 13:47:59 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id QAA24691 for ; Thu, 24 Dec 1998 16:49:14 GMT Message-Id: <199812241649.QAA24691@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Thu, 24 Dec 1998 16:49:30 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: routing table issue with 3.0 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Im not certain exactly what the issue is, but in tracking down a porting problem I discovered the following, which was NOT the case in previous versions. It seems wrong to me. if you call if_up() from a driver before running ifconfig on a PTP interface ifconfig will fail to add the destination address with EEXIST. However the address is not in the routing table. Its pretty messy stuff, so I havent gone further than eliminating the if_up call from our driver at init time (and I dont intend to go further), but something may be amuck so if anyone knows what changed it might be worth thinking about. Dennis Emerging Technologies, Inc. http://www.etinc.com ISA and PCI T1/V35/HSSI Cards for FreeBSD, LINUX and BSD/OS Bandwidth Manager http://www.etinc.com/bwmgr.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 24 23:25:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14308 for freebsd-hackers-outgoing; Thu, 24 Dec 1998 23:25:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ol.kyrnet.kg (ol.kyrnet.kg [195.254.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14302 for ; Thu, 24 Dec 1998 23:25:25 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from gizmo.kyrnet.kg (IDENT:fygrave@gizmo.kyrnet.kg [195.254.160.13]) by ol.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id LAA08112 for ; Fri, 25 Dec 1998 11:53:39 +0600 Received: from localhost (fygrave@localhost) by gizmo.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id MAA23095 for ; Fri, 25 Dec 1998 12:23:26 +0500 X-Authentication-Warning: gizmo.kyrnet.kg: fygrave owned process doing -bs Date: Fri, 25 Dec 1998 12:23:26 +0500 (KGT) From: CyberPsychotic X-Sender: fygrave@gizmo.kyrnet.kg To: freebsd-hackers@FreeBSD.ORG Subject: dynamic libraries loading Message-ID: Confirm-receipt-to: fygrave@usa.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello people, sorry for pulling another question in a row, but here I got stuck abit with another thing while bringing my library (loaded with LD_PRELOAD) from linux to BSD world: I used my own _init(..) function on Linux, which is called, when the library is loaded, and compiling it library with -nostdlib switch was enough to get rid off names collision. However I noticed that neither FreeBSD nor BSDi calls _init when loads library. On bsdi-users mailing list I was suggested to use __attribute__((__constructor__)) to achieve this . The similar thing seem to work on FreeBSD as well, but I am wondering if any other technique could be used? thanks beforehands Fyodor ---------- Forwarded message ---------- Date: Thu, 24 Dec 1998 10:39:54 -0700 From: Donn Seeley To: fygrave@tigerteam.net Cc: seebs@plethora.net, bsdi-users@bsdi.com, unix-lizards@mailinglists.org Subject: Re: LD_PRELOAD equvalency Date: Thu, 24 Dec 1998 10:22:12 +0500 (KGT) From: CyberPsychotic [...] ~ Also, you should identify the version you're using. BSDi 3.1 server. As others have pointed out, BSD/OS 3.1 didn't support dynamically linked executables, and LD_PRELOAD is a feature of dynamically linked executables. 3.1 did support dynamically linked objects (dlopen(3)) but that feature alone doesn't provide support for LD_PRELOAD. If you want to use LD_PRELOAD, I recommend that you upgrade to 4.0. well, yep.. , but here's what I am trying to do: [...] bash-2.02# cat lib.c #include int _init(void) { printf("I am here\n"); return 0; } bash-2.02# gcc -shared lib.c -o lib.so bash-2.02# LD_PRELOAD="./lib.so"; export LD_PRELOAD bash-2.02# /usr/bin/troff aaa /usr/bin/troff: fatal error: can't open `aaa': No such file or directory bash-2.02#ktrace -f ktr.out /usr/bin/troff aaa bash-2.02#ktdump -f ktr.out | grep lib.so gives nothing. So it doesn't seem to even attempt to load it. Ideas? This won't work in either 3.1 or 4.0. /usr/bin/troff is statically linked in both versions of BSD/OS, and LD_PRELOAD won't affect a statically linked program. However, groff (GNU troff) sources are provided on the contributed software CD-ROM that comes with every distribution, so you can rebuild troff as a dynamically linked executable if you want to. (Use 'LDCC=cc; export LDCC' or 'setenv LDCC cc', as appropriate for your shell, to override the default shlicc(1) link command.) Even if you use a dynamically linked executable in 4.0, you should do this slightly differently. Here's an example using cat(1) from the BSD/OS source distribution: % cat here.c #include static void my_init(void) __attribute__((__constructor__)); static void my_init() { printf("I am here\n"); } % cc -shared -o here.so here.c -lc % cc -o cat -O2 /usr/src/bin/cat/cat.c % (setenv LD_PRELOAD $cwd/here.so; ./cat /etc/fstab) I am here # # Filesystem mount table information. See the fstab(5) man page # and the /etc/fstab.sample file for more information and examples. [...] % Note that building cat(1) with cc(1) instead of shlicc(1) produces a dynamically linked executable in 4.0: % file cat /bin/cat cat: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked /bin/cat: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, stripped % shlist cat /bin/cat cat: /shlib/ld-bsdi.so libgcc.so libc.so /bin/cat: /shlib/libc_s.4.0.0 % size cat /bin/cat text data bss dec hex 4169 388 364 4921 1339 cat 2241 160 36 2437 985 /bin/cat % You should also note that it isn't safe to attempt to replace symbols like _init in dynamically linked programs. The GCC __attribute__((__constructor__)) feature is a handy way of getting the right effect (although it's not portable). Donn Seeley / BSDI Engineering To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 25 19:15:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26422 for freebsd-hackers-outgoing; Fri, 25 Dec 1998 19:15:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26417 for ; Fri, 25 Dec 1998 19:15:42 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id TAA29239; Fri, 25 Dec 1998 19:15:25 -0800 (PST) (envelope-from obrien) Message-ID: <19981225191525.A29195@nuxi.com> Date: Fri, 25 Dec 1998 19:15:25 -0800 From: "David O'Brien" To: Wolfram Schneider , freebsd-hackers@FreeBSD.ORG Subject: Re: [HTML index of current mail archive] Reply-To: obrien@nuxi.ucdavis.edu References: <19981221135300.A578@caramba.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221135300.A578@caramba.cs.tu-berlin.de>; from Wolfram Schneider on Mon, Dec 21, 1998 at 01:53:00PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I setup a primitve HTML index of the current mail archive (*) The It would be great if we could change our mailing list WWW software to MHonarc. While I generally *hate* frames, email lists are the one place they are truely a step up. Otherwise navigation is quite a pain. And when you are following a thread and wish to get back to the index, it is *TONS* of . See: http://www.oac.uci.edu/indiv/ehood/tmp/frame/ http://www.oac.uci.edu/indiv/ehood/mhonarc.html for an example of a really nice way to do mailing lists. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 25 19:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28009 for freebsd-hackers-outgoing; Fri, 25 Dec 1998 19:53:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28004; Fri, 25 Dec 1998 19:53:19 -0800 (PST) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.1/8.7) id OAA01444; Sat, 26 Dec 1998 14:22:19 +1030 (CST) Date: Sat, 26 Dec 1998 14:22:19 +1030 (CST) From: Mark Newton Message-Id: <199812260352.OAA01444@atdot.dotat.org> To: cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: LDT entries - Proposed change Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to make some low-level changes over the next couple of days to support the svr4 emulator which I'll be committing after new-year. Synopsis of problem: Sun bug ID 1251858 describes how Sun changed the system call semantics of Solaris between 2.5.1 and 2.6. System calls are still done by means of an intersegment jump into one of the system's LDT entries; FreeBSD has historically supported system call execution through LDT entries 0 and 16 (for iBCS2 COFF and BSDI emulation respectively), but Solaris 2.6 uses LDT entry 4. Unfortunately, FreeBSD has historically used LDT entry 4 for user process data. I have a patch for sys/i386/include/segments.h and sys/i386/i386/machdep.c which changes LUDATA_SEL from 4 to 5 (why 5? Why not?) and provides for system call entries via LDT entry 4 (termed LSOL26CALLS_SEL at present). I'm running this kernel at the moment with no ill effects, and I'd like to commit the change at some point over the next couple of days. Does anyone know of any applications using USER_LDT which might be in love with entry 5 already? Does anyone know of any BadThings(tm) which will occur if LUDATA_SEL is moved to entry 5? If I don't get back any bad feedback I'll commit the change shortly before new-year. In the meantime, a patch against 3.0-RELEASE which makes the change is at http://www.freebsd.org/~newton/freebsd-svr4/segpatch if anyone wants to see it. Cheers, - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 25 21:04:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02290 for freebsd-hackers-outgoing; Fri, 25 Dec 1998 21:04:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02273; Fri, 25 Dec 1998 21:04:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA29295; Fri, 25 Dec 1998 21:04:04 -0800 (PST) (envelope-from dillon) Date: Fri, 25 Dec 1998 21:04:04 -0800 (PST) From: Matthew Dillon Message-Id: <199812260504.VAA29295@apollo.backplane.com> To: Mark Newton Cc: cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LDT entries - Proposed change Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a patch for sys/i386/include/segments.h and sys/i386/i386/machdep.c :which changes LUDATA_SEL from 4 to 5 (why 5? Why not?) and provides for :system call entries via LDT entry 4 (termed LSOL26CALLS_SEL at present). :... : :Cheers, : : - mark Unless you think you'll have the solaris emulation done by the 3.0.1 release, I would recommend waiting until the source tree split before commiting this change. I can't think of any specific problems that might occur but I don't think a month is long enough to test something like this and while the direct LDT references are constrained to a few files in i386, those files are pretty convoluted and it's a pretty scary change to make. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 00:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12293 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 00:10:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12288 for ; Sat, 26 Dec 1998 00:10:05 -0800 (PST) (envelope-from tom@tomqnx.com) Received: from alphie by TomQNX.tomqnx.com with smtp (Smail3.2 #1) id m0ztomW-000I0PC; Sat, 26 Dec 1998 03:09:04 -0500 (EST) From: "Tom Torrance" To: "Luigi Rizzo" Cc: , , , , Subject: RE: kernel panic Date: Sat, 26 Dec 1998 03:09:04 -0500 Message-ID: <000201be30a7$00cf2640$062b96cd@alphie.tomqnx.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-reply-to: <199812240302.EAA04022@labinfo.iet.unipi.it> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Luigi Rizzo [mailto:luigi@labinfo.iet.unipi.it] > Sent: December 23, 1998 10:02 PM > To: Tom Torrance at home > Cc: hackers@freebsd.org; jkh@zippy.cdrom.com; tom@tomqnx.com; > mike@dingo.cdrom.com; support@opensound.com; josh@ican.net > Subject: Re: kernel panic > > > > Q2. Why does the driver generate a stream of "sorry, read DMA channel > > unavailable" messages? > > not sure. either misconfiguration of the card, or too verbose msgs in > the kernel. > FYI, the card was not misconfigured & worked perfectly with xmcd. This happened ONLY with x11amp. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 00:26:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12941 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 00:26:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA12931 for ; Sat, 26 Dec 1998 00:26:09 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA07263; Sat, 26 Dec 1998 07:15:40 +0100 From: Luigi Rizzo Message-Id: <199812260615.HAA07263@labinfo.iet.unipi.it> Subject: Re: kernel panic To: tom@tomqnx.com (Tom Torrance) Date: Sat, 26 Dec 1998 07:15:39 +0100 (MET) Cc: hackers@FreeBSD.ORG, jkh@zippy.cdrom.com, mike@dingo.cdrom.com, support@opensound.com, josh@ican.net In-Reply-To: <000201be30a7$00cf2640$062b96cd@alphie.tomqnx.com> from "Tom Torrance" at Dec 26, 98 03:08:45 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Q2. Why does the driver generate a stream of "sorry, read DMA channel > > > unavailable" messages? > > > > not sure. either misconfiguration of the card, or too verbose msgs in > > the kernel. > > > FYI, the card was not misconfigured & worked perfectly with xmcd. This > happened ONLY with x11amp. xmcd, and other mixer/cdplayer applications only use the mixer section of the card, leaving ample room for undetected misconfiguration of IRQ and DMA channels cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 03:08:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20038 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 03:08:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20033 for ; Sat, 26 Dec 1998 03:08:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id DAA03713; Sat, 26 Dec 1998 03:08:27 -0800 (PST) To: obrien@nuxi.ucdavis.edu cc: Wolfram Schneider , freebsd-hackers@FreeBSD.ORG Subject: Re: [HTML index of current mail archive] In-reply-to: Your message of "Fri, 25 Dec 1998 19:15:25 PST." <19981225191525.A29195@nuxi.com> Date: Sat, 26 Dec 1998 03:08:27 -0800 Message-ID: <3709.914670507@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It would be great if we could change our mailing list WWW software to > MHonarc. While I generally *hate* frames, email lists are the one place It would be great if MHonarc worked on lists this big. Try it sometime. :( I also don't know of any way to build "incremental indexes" from multiple pieces and I've tried that too. Basically, unless they've substantially improved it lately, mhonarc is not sufficient to the job. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 05:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00169 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 05:37:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from atdot.dotat.org (atdot.dotat.org [203.23.150.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00164; Sat, 26 Dec 1998 05:37:18 -0800 (PST) (envelope-from newton@atdot.dotat.org) Received: (from newton@localhost) by atdot.dotat.org (8.9.1/8.7) id AAA05205; Sun, 27 Dec 1998 00:06:10 +1030 (CST) From: Mark Newton Message-Id: <199812261336.AAA05205@atdot.dotat.org> Subject: Re: LDT entries - Proposed change To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 27 Dec 1998 00:06:09 +1030 (CST) Cc: cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199812260504.VAA29295@apollo.backplane.com> from "Matthew Dillon" at Dec 25, 98 09:04:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :I have a patch for sys/i386/include/segments.h and sys/i386/i386/machdep.c > :which changes LUDATA_SEL from 4 to 5 (why 5? Why not?) and provides for > :system call entries via LDT entry 4 (termed LSOL26CALLS_SEL at present). > > Unless you think you'll have the solaris emulation done by the 3.0.1 > release, I don't think it'll ever be "done" any more than the Linux emulator is ever "done". It's currently in a state where it runs a decent selection of Solaris software with libraries from a Solaris 2.5.1 CD-ROM and a somewhat smaller selection of software if libraries are taken from a Solaris 2.6 CD-ROM (we've only just got executables to run with 2.6 libraries at all due to the LDT issue described above, and Sun has made enough libc/ld.so.1 changes between 2.5.1 and 2.6 to tickle the edges of the emulation's accuracy, so a bit more work will be required to provide 2.6 libraries with an environment where they can provide the same functionality as 2.5.1 libraries). I think most of those issues are actually answered by changes in the NetBSD codebase that I haven't tracked so I don't expect them to represent a major problem. I've had RealPlayer for Solaris 2.5.1 working (without audio) and most of the OpenWindows stuff from /usr/openwin on a Solaris/x86 CD. I've also done a small amount of fiddling with a SCO OpenServer CD-ROM with reasonable success. There's still a lot of work to do, but the core is there and limping along. I expect that bde will complain about some stylistic issues, but I'm keeping them in mind too :-) It's still an LKM, it compiles with too many warnings, and there are too many bits enclosed by #ifdef BOGUS or #ifdef NOTYET that I haven't had time to give attention to yet. http://www.freebsd.org/~newton/freebsd-svr4/index.html > I would recommend waiting until the source tree split > before commiting this change. I can't think of any specific problems > that might occur but I don't think a month is long enough to test > something like this and while the direct LDT references are constrained > to a few files in i386, those files are pretty convoluted and it's > a pretty scary change to make. I don't have a major problem with any of that. Whether it's committed or not I'll still be working on it, so this means it'll just be better when it is finally committed. When the time comes I'll also need to change a couple of prototypes (to un-staticize a couple of symbols in uipc_syscalls.c) and add a field to the end of struct socket in order to support emulation of icky SysV STREAMS over BSD sockets. I've been going over those with Mike Smith and discussed them briefly with Garrett earlier this year; See http://www.freebsd.org/~newton/freebsd-svr4/svr4patch for more diffs against 3.0-RELEASE. - mark -------------------------------------------------------------------- I tried an internal modem, newton@atdot.dotat.org but it hurt when I walked. Mark Newton ----- Voice: +61-4-1958-3414 ------------- Fax: +61-8-83034403 ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 06:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02192 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 06:12:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02187 for ; Sat, 26 Dec 1998 06:12:10 -0800 (PST) (envelope-from kaleb@ics.com) Received: from kaleb.keithley.belmont.ma.us (pmdialin5.ics.com [140.186.40.179]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA03002 Sat, 26 Dec 1998 09:07:37 -0500 (EST) Received: from kaleb.keithley.belmont.ma.us (localhost [127.0.0.1]) by kaleb.keithley.belmont.ma.us (8.9.1/8.9.1) with SMTP id KAA06882 for ; Sat, 26 Dec 1998 10:32:10 -0500 (EST) (envelope-from kaleb@ics.com) Message-ID: <36850172.41C67EA6@ics.com> Date: Sat, 26 Dec 1998 10:32:03 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: dynamic libraries loading References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CyberPsychotic wrote: > > I used my own _init(..) function on Linux, which is called, when the > library is loaded, and compiling it library with -nostdlib switch was > enough to get rid off names collision. However I noticed that neither > FreeBSD nor BSDi calls _init when loads library. On which version of FreeBSD? On my 3.0-RELEASE machine the shared lib _init() and _fini() functions are called. Note however that the ELF specification says that these functions should be called .init() and .fini(). (Getting functions named .init() and .fini requires a little extra effort; but it's not that hard. You have to compile to assembler, then change the names (using sed) because a leading '.' is not valid for a name in C, then use the assembler to generate the .o file(s)) Looking at the sources in /usr/src/libexec/rtld-elf/, I see that rtld relies on the DT_INIT and DT_FINI tags to find the functions in the shared lib. Apparently it's ld that looks for functions named _init() and _fini() and tags them accordingly. Guess I'll have to suck down the FreeBSD/gnu sources to have a look see. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 06:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05028 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 06:57:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shell6.ba.best.com (shell6.ba.best.com [206.184.139.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05021 for ; Sat, 26 Dec 1998 06:57:14 -0800 (PST) (envelope-from jkb@shell6.ba.best.com) Received: (from jkb@localhost) by shell6.ba.best.com (8.9.1/8.9.0/best.sh) id GAA15993 for hackers@freebsd.org; Sat, 26 Dec 1998 06:56:33 -0800 (PST) Message-ID: <19981226065633.A14892@best.com> Date: Sat, 26 Dec 1998 06:56:33 -0800 From: "Jan B. Koum " To: hackers@FreeBSD.ORG Subject: IPv6 - when? which? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to beat around dead horse - but what was the final outcome of the "which IPv6 vendor" thread a few weeks back? Will 3.1-CURRENT get an IPsec and IPv6? To be very honest - I am more interested in IPsec then v6. -- Yan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 09:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14555 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 09:26:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shidahara1.planet.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14537 for ; Sat, 26 Dec 1998 09:26:06 -0800 (PST) (envelope-from takawata@shidahara1.planet.kobe-u.ac.jp) From: takawata@shidahara1.planet.kobe-u.ac.jp Received: from libr.scitec.kobe-u.ac.jp (cs2d209.ppp.infoweb.ne.jp [202.219.141.169]) by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id CAA09443 for ; Sun, 27 Dec 1998 02:17:04 +0900 (JST) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id CAA02742 for ; Sun, 27 Dec 1998 02:25:18 +0900 (JST) Message-Id: <199812261725.CAA02742@libr.scitec.kobe-u.ac.jp> To: hackers@FreeBSD.ORG Subject: Please test my code for Intel onboard SMBus function. Date: Sun, 27 Dec 1998 02:25:16 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a driver for PIIX4 SMBus and I need some feedback and advice about PCI code, especially intrrupt code. The code is currently available at http://www.freebsd.org/~nsouch/intiic-981224.tgz or http://www.planet.sci.kobe-u.ac.jp/~takawata/intiic-981224.tgz The device have somewhat odd PCI configuration space about intrrupt. It uses only SMI or IRQ 9 intpin #a and normal IRQ and intpin configuration register shows no intrupt. So I cut ,paste and modify pci_map_int() code. If you know more better way,please advice me. Thanks in advance. Takanori Watanabe. Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 10:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19051 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 10:12:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18895 for ; Sat, 26 Dec 1998 10:12:37 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA26125 for hackers@FreeBSD.ORG; Sat, 26 Dec 1998 19:12:22 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F32A9155A; Sat, 26 Dec 1998 17:05:09 +0100 (CET) Date: Sat, 26 Dec 1998 17:05:09 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: IPv6 - when? which? Message-ID: <19981226170509.A20826@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19981226065633.A14892@best.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981226065633.A14892@best.com>; from Jan B. Koum on Sat, Dec 26, 1998 at 06:56:33AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4926 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jan B. Koum : > Not to beat around dead horse - but what was the final > outcome of the "which IPv6 vendor" thread a few weeks > back? Will 3.1-CURRENT get an IPsec and IPv6? To be > very honest - I am more interested in IPsec then v6. Then take it either from OpenBSD or from the KAME folks. I think it would be unwise to choose one implementation over the other considereing they'll be merged in a few months. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 10:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20870 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 10:35:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20865 for ; Sat, 26 Dec 1998 10:35:51 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id KAA05538 for freebsd-hackers@FreeBSD.ORG; Sat, 26 Dec 1998 10:35:32 -0800 (PST) (envelope-from obrien) Message-ID: <19981226103531.B29283@nuxi.com> Date: Sat, 26 Dec 1998 10:35:31 -0800 From: "David O'Brien" To: freebsd-hackers@FreeBSD.ORG Subject: Re: [HTML index of current mail archive] Reply-To: obrien@nuxi.ucdavis.edu References: <19981225191525.A29195@nuxi.com> <3709.914670507@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3709.914670507@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Dec 26, 1998 at 03:08:27AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 26, 1998 at 03:08:27AM -0800, Jordan K. Hubbard wrote: > It would be great if MHonarc worked on lists this big. Try it > sometime. :( I also don't know of any way to build "incremental" from Ah. That's a shame, but thanks for the info. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 11:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23615 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 11:10:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ime.net (ime.net [209.90.192.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23610 for ; Sat, 26 Dec 1998 11:10:38 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4042.ime.net [209.90.195.52]) by ime.net (8.8.7/8.8.7) with SMTP id OAA29849; Sat, 26 Dec 1998 14:10:13 -0500 (EST) Message-Id: <4.1.19981226140415.00c2a8b0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 26 Dec 1998 14:07:03 -0500 To: takawata@shidahara1.planet.kobe-u.ac.jp, hackers@FreeBSD.ORG From: Drew Baxter Subject: Re: Please test my code for Intel onboard SMBus function. In-Reply-To: <199812261725.CAA02742@libr.scitec.kobe-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:25 AM 12/27/98 +0900, takawata@shidahara1.planet.kobe-u.ac.jp wrote: >I wrote a driver for PIIX4 SMBus and I need some feedback and advice about >PCI code, especially intrrupt code. >The code is currently available at >http://www.freebsd.org/~nsouch/intiic-981224.tgz >or >http://www.planet.sci.kobe-u.ac.jp/~takawata/intiic-981224.tgz > >The device have somewhat odd PCI configuration space about intrrupt. >It uses only SMI or IRQ 9 intpin #a and normal IRQ and intpin >configuration register shows no intrupt. So I cut ,paste and modify >pci_map_int() code. >If you know more better way,please advice me. I get this: Loki# ./spd OPEN: No such file or directory It'd probably help to have the stuff to throw into mknod, because I don't have a /dev/smb*.. :-) --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 13:38:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03937 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 13:38:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ywing.creative.net.au ([203.26.193.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03932 for ; Sat, 26 Dec 1998 13:38:46 -0800 (PST) (envelope-from adrian@ywing.creative.net.au) Received: from ywing.creative.net.au (localhost.speedport.net [127.0.0.1] (may be forged)) by ywing.creative.net.au (8.8.8/8.8.8) with ESMTP id WAA04817 for ; Sat, 26 Dec 1998 22:38:04 +0100 (CET) Message-Id: <199812262138.WAA04817@ywing.creative.net.au> To: freebsd-hackers@FreeBSD.ORG From: adrian@FreeBSD.ORG Subject: auto-allocation of ptys Date: Sat, 26 Dec 1998 22:38:02 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got sick of running out of ptys while running X, and having to result in rebuilding a kernel with more ptys enabled. So, I modified sys/kern/tty_pty.c to dynamically allocate pt_ioctl and tty structs when a pty access is made. I'm not totally familar with the tty IO system just yet, so it creates the structs whenever *some* form of access is done, not just open(). It also doesn't return the memory used by pt_ioctl and tty structs back to the memory pool - I didn't think the code complexity it would add would justify it. The patch is relative to sys/kern/tty_pty.c in 2.2.7-REL . Redefine MAXPTY in the source to set the initial number of ptys to allow to be opened. It creates two sysctl variables - kern.maxpty and kern.openptys - it allows you to set the max number of ptys you can have opened, and shows the current number of ptys opened respectively. This patch breaks pstat -t (strangely enough :) ... I haven't looked at it yet, but I guess you would have to just walk the pt_dynpty linked lists to grab the open ptys and go from there. It also will break devfs - I'm sure a devfs solution could be nutted out, but I'm still looking at it atm, and I'm not entirely sure on the status of it. The upshoot of all this of course is that you don't have to rebuild your kernel whenever you need more ptys. :-) Does anyone want to take a look at the idea and comment on it ? Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 13:57:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06402 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 13:57:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ywing.creative.net.au ([203.26.193.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06397 for ; Sat, 26 Dec 1998 13:57:11 -0800 (PST) (envelope-from adrian@ywing.creative.net.au) Received: from ywing.creative.net.au (localhost.speedport.net [127.0.0.1] (may be forged)) by ywing.creative.net.au (8.8.8/8.8.8) with ESMTP id WAA04874 for ; Sat, 26 Dec 1998 22:56:27 +0100 (CET) Message-Id: <199812262156.WAA04874@ywing.creative.net.au> To: freebsd-hackers@FreeBSD.ORG Subject: Re: auto-allocation of ptys In-reply-to: Your message of "Sat, 26 Dec 1998 22:38:02 +0100." <199812262138.WAA04817@ywing.creative.net.au> Date: Sat, 26 Dec 1998 22:56:25 +0100 From: Adrian Chadd Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG adrian@FreeBSD.ORG writes: > > >I got sick of running out of ptys while running X, and having to result >in rebuilding a kernel with more ptys enabled. > >So, I modified sys/kern/tty_pty.c to dynamically allocate pt_ioctl and >tty structs when a pty access is made. Did I forget to mention that the patch is at http://www.freebsd.org/~adrian/tty_pty.c.diff ? I hope not. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 15:38:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13556 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 15:38:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13551; Sat, 26 Dec 1998 15:38:36 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA00886; Sat, 26 Dec 1998 15:28:46 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdDmZ884; Sat Dec 26 23:28:42 1998 Date: Sat, 26 Dec 1998 15:28:40 -0800 (PST) From: Julian Elischer To: Matthew Dillon cc: Mark Newton , cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: LDT entries - Proposed change In-Reply-To: <199812260504.VAA29295@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there is enough already running that it SHOULD be committed. On Fri, 25 Dec 1998, Matthew Dillon wrote: > > :I have a patch for sys/i386/include/segments.h and sys/i386/i386/machdep.c > :which changes LUDATA_SEL from 4 to 5 (why 5? Why not?) and provides for > :system call entries via LDT entry 4 (termed LSOL26CALLS_SEL at present). > :... > : > :Cheers, > : > : - mark > > Unless you think you'll have the solaris emulation done by the 3.0.1 > release, I would recommend waiting until the source tree split > before commiting this change. I can't think of any specific problems > that might occur but I don't think a month is long enough to test > something like this and while the direct LDT references are constrained > to a few files in i386, those files are pretty convoluted and it's > a pretty scary change to make. > > -Matt > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 16:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17832 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 16:07:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17818; Sat, 26 Dec 1998 16:07:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA33903; Sat, 26 Dec 1998 16:07:29 -0800 (PST) (envelope-from dillon) Date: Sat, 26 Dec 1998 16:07:29 -0800 (PST) From: Matthew Dillon Message-Id: <199812270007.QAA33903@apollo.backplane.com> To: cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: new swap system work Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After a number of long conversations with John Dyson in regards to memory deadlock issues and related kernel hacks used to get around them, I've decided to embark on a major project to revamp the vm/pager_* code to allow paging to occur in zero-memory-free situations. This work is going to be mostly concentrated in vm/swap_pager.c but will have a ripple effect throughout the core VM system (vm/*.c) and the memory subsystem. The work is going to be broken down into two parts: * rewriting the swap_pager. * filesystem / VOP_STRATEGY work to guarentee that all VOP_STRATEGY() calls for all filesystems and devices will operate without a memory deadlock occuring in zero-free-memory situations. The first part I'm working on now and expect to commit sometime POST 3.0.1. We'll see how long it takes me to get it solid. Basically, fixing the swap system requires moving the allocation of the swap metadata structures out of the pageout code. To accomplish this, vm_page_t will get a new field, called 'swapblk'. All swap-backed memory-resident pages will have their swap blocks stored in the vm_page_t rather then the swap-metadata structure. Swap blocks assigned to resident pages do not have to be moved into the object swap metadata structures until the page is actually freed (at which point there is free memory available to allocate the swap metadata structure, hence the ability to operate in a zero-free-page environment). The side effects of doing this are all beneficial. The VM system becomes more swap-aware and doesn't have to worry about free memory as much. A great deal of simplification can be done all over place. These simplifications will take longer to accomplish since my goal is to get the thing working first, but I think the long term prospects are very good. Eventually we should be able to page out swap metadata associated with active processes (but that's a long ways off). The raw swap allocation / deallocation code (the rlist stuff) will also eventually be rewritten to remove the memory blocking constraints that rlist_free currently has and to make it possible to remove swap. - I'll start work on the second part after I finish the first part. Fixing VOP_STRATEGY basically involves giving each device or filesystem its own guarenteed pool of N private pages (e.g. like 5 or so per active device or mount). The device drivers will then be modified such that they are able to guarentee operation without memory deadlock when operating solely out of their private pool (i.e. when no system global free pages are available). So, for example, a VOP_*() call could still block on memory, but the use of the private pool means it would be guarenteed to unblock sometime later as other I/O's in progress on that device complete and free private pool memory. The system's global free pool could then be reduced accordingly, an overall wash. Still, I think the use of private pools will actually make low-memory FreeBSD configurations more efficient. Fixing VOP_STRATEGY() and the swapper will together allow reliable paging to files and remove memory deadlock issues related to VFS layering (e.g. like mounting a vn partition on top of NFS and then mounting a filesystem through that) - though even so there are still a number of deadlock issues still remaining in the VFS layering department. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 17:14:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21927 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 17:14:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21920; Sat, 26 Dec 1998 17:14:23 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA03548; Sat, 26 Dec 1998 17:10:48 -0800 (PST) Message-Id: <199812270110.RAA03548@implode.root.com> To: Matthew Dillon cc: cvs-all@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: new swap system work In-reply-to: Your message of "Sat, 26 Dec 1998 16:07:29 PST." <199812270007.QAA33903@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 26 Dec 1998 17:10:47 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The first part I'm working on now and expect to commit sometime POST 3.0.1. > We'll see how long it takes me to get it solid. You will not commit anything like this without careful review by at least myself and perhaps others. > Basically, fixing the swap system requires moving the allocation of the > swap metadata structures out of the pageout code. To accomplish this, > vm_page_t will get a new field, called 'swapblk'. All swap-backed > memory-resident pages will have their swap blocks stored in the vm_page_t > rather then the swap-metadata structure. Swap blocks assigned to > resident pages do not have to be moved into the object swap metadata > structures until the page is actually freed (at which point there is > free memory available to allocate the swap metadata structure, hence > the ability to operate in a zero-free-page environment). This seems to assume that all pages are backed by swap, which is definately not the case. On many system, it is not even 'most'. I could almost swallow this if it was abstracted to a pager-private struct. > The side effects of doing this are all beneficial. I don't agree. I can think of at least two negatives: It bloats the vm_page struct and it makes a mess out of the layering. > The VM system becomes > more swap-aware and doesn't have to worry about free memory as much. I don't think this is a significant advantage. Most of the problems we've seen in the past are actually on the vnode pager side and not the swap pager side. > A great deal of simplification can be done all over place. I'm not convinced of this. I'm sure the code will be different, but I doubt it will be much simpler. > These > simplifications will take longer to accomplish since my goal is to get > the thing working first, but I think the long term prospects are very > good. Eventually we should be able to page out swap metadata associated > with active processes (but that's a long ways off). The raw swap > allocation / deallocation code (the rlist stuff) will also eventually be > rewritten to remove the memory blocking constraints that rlist_free > currently has and to make it possible to remove swap. It is possible to remove swap with the current framework. Noone has bothered to write the code to do it, however. It seems to me that it will be much more difficult to remove swap in the future if you put pager related storage data in each struct vm_page. > I'll start work on the second part after I finish the first part. Fixing > VOP_STRATEGY basically involves giving each device or filesystem its own > guarenteed pool of N private pages (e.g. like 5 or so per active device > or mount). Yuck. One of the benefits of 4.4BSD (and further work by us) was getting rid of private pools of memory. In some cases we reverted for performance reasons, but private pools almost always get in the way of dynamicly scaled systems. > Fixing VOP_STRATEGY() and the swapper will together allow reliable > paging to files and remove memory deadlock issues related to VFS > layering (e.g. like mounting a vn partition on top of NFS and then > mounting a filesystem through that) - though even so there are still a > number of deadlock issues still remaining in the VFS layering department. I think the deadlock issues are a bit overrated. The main problem that I know about has to do with allocating really large swap block arrays for large objects. There are ways of solving this at the swap pager level without moving it into the struct vm_page. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 18:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26981 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 18:22:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26976; Sat, 26 Dec 1998 18:22:16 -0800 (PST) (envelope-from kaleb@ics.com) Received: from kaleb.keithley.belmont.ma.us (pmdialin3.ics.com [140.186.40.177]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id VAA17809; Sat, 26 Dec 1998 21:21:33 -0500 (EST) Received: from kaleb.keithley.belmont.ma.us (localhost [127.0.0.1]) by kaleb.keithley.belmont.ma.us (8.9.1/8.9.1) with SMTP id WAA07669; Sat, 26 Dec 1998 22:45:39 -0500 (EST) (envelope-from kaleb@ics.com) Message-ID: <3685AD58.167EB0E7@ics.com> Date: Sat, 26 Dec 1998 22:45:28 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: /usr/src/gnu sources in 3.0-RELEASE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I couldn't find this in the FAQ or Handbook. What am I supposed to do for the real sources? (Don't tell me ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/src/sgnu.* because I already have those, and that's not the question I'm asking.) Am I supposed to, e.g. get binutils-2.9.1.tar.gz from gnu and untar them on top of /usr/src/gnu/binutils? -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 18:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27412 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 18:25:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27394; Sat, 26 Dec 1998 18:25:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01241; Sat, 26 Dec 1998 18:22:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812270222.SAA01241@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kaleb S. KEITHLEY" cc: hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: /usr/src/gnu sources in 3.0-RELEASE In-reply-to: Your message of "Sat, 26 Dec 1998 22:45:28 EST." <3685AD58.167EB0E7@ics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 26 Dec 1998 18:22:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I couldn't find this in the FAQ or Handbook. What am I supposed to do > for the real sources? > > (Don't tell me ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/src/sgnu.* > because I already have those, and that's not the question I'm asking.) > > Am I supposed to, e.g. get binutils-2.9.1.tar.gz from gnu and untar them > on top of /usr/src/gnu/binutils? No; if you're looking for where all the 'meat' is, see /usr/src/contrib; the gnu stuff is built out of src/gnu, but the actual from-the-FSF files live in the contrib area. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 18:47:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29096 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 18:47:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from abraracourcix.galea.com (ppp020.110.mmtl.videotron.net [207.253.110.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29091 for ; Sat, 26 Dec 1998 18:47:41 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by abraracourcix.galea.com (8.9.1/8.9.1) with ESMTP id VAA00286; Sat, 26 Dec 1998 21:46:55 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <36859F9F.5B8DAFF@videotron.ca> Date: Sat, 26 Dec 1998 21:46:55 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith , Hackers@FreeBSD.ORG Subject: Re: New bootloader and network iface References: <199812180212.SAA00576@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > I have to be able to boot a kernel over the network. > > Looking at the new bootloader. I gather from the code that > > it should be possible given that the right device support > > is added. Does anyone know if any nic is already supported > > and if so where I could find the code? If there are no nic > > drivers available right now is there any doc about what > > the bootloader is expecting the driver to look like apart > > from the code? Btw, I can't use nic boot roms to do it. > > There's no documentation, apart from the code at this stage, no. Network > booting works on the Alpha, although it has some rough edges at the > moment. If you're interested in working on this, I'd be more than > happy to help you with it. > Well, I surely could use some help :) Could you explain to me how does the match mechanism works for netif_driver devices? Especially how the select of the right iface (de, lnc, ...) is supposed to be done. Btw, I was unable to get the loader to work until I aligned then end variable to a MEMNODE_SIZE_MASK boundary in the call to setheap in "main.c". Is is really needed? Thanks in advance! Stephane E. Potvin Galea Network Security To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 20:25:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07235 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 20:25:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bingsun2.cc.binghamton.edu (bingsun2.cc.binghamton.edu [128.226.1.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07230 for ; Sat, 26 Dec 1998 20:25:13 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun2.cc.binghamton.edu (8.8.7/8.6.9) with SMTP id XAA13377 for ; Sat, 26 Dec 1998 23:24:55 -0500 (EST) Date: Sat, 26 Dec 1998 23:24:54 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun2 Reply-To: zhihuizhang To: hackers Subject: Questions about interrupt handling Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I know that FreeBSD handles interrupts on a software basis which means that we do not mask any interrupt off in 8259. I am just wondering if a certain interrupt is masked off in 8259 or it does not get serviced quick enough, what will the device controller (such as disk controller) respond? Will it re-issue the interrupt or just give up? Or will it NOT generate another interrupt until the previous one has been serviced? Maybe different device controllers behave differently. Thanks for any help. -------------------------------------------------- | Zhihui Zhang, http://cs.binghamton.edu/~zzhang | | Dept. of Computer Science, SUNY at Binghamton | -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 20:27:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07333 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 20:27:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fgwmail.fujitsu.co.jp (fgwmail.fujitsu.co.jp [164.71.1.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07328 for ; Sat, 26 Dec 1998 20:27:04 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from fdmnews.fujitsu.co.jp by fgwmail.fujitsu.co.jp (8.9.1a/3.7W-MX9808-Fujitsu Gateway) id NAA15551; Sun, 27 Dec 1998 13:26:48 +0900 (JST) Received: from incapgw.fujitsu.co.jp by fdmnews.fujitsu.co.jp (8.8.8+2.7Wbeta7/3.6W-980929-Fujitsu Domain Master) id NAA18014; Sun, 27 Dec 1998 13:26:47 +0900 (JST) Received: from localhost ([192.168.245.147]) by incapgw.fujitsu.co.jp (8.9.1a/3.7W-9810-MobileGateWay) id NAA02845; Sun, 27 Dec 1998 13:26:46 +0900 (JST) To: hackers@FreeBSD.ORG Subject: Re: IPv6 - when? which? In-Reply-To: Your message of "Sat, 26 Dec 1998 17:05:09 +0100" <19981226170509.A20826@keltia.freenix.fr> References: <19981226170509.A20826@keltia.freenix.fr> X-Mailer: Mew version 1.93b38 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981227132444B.shin@nd.net.fujitsu.co.jp> Date: Sun, 27 Dec 1998 13:24:44 +0900 From: Yoshinobu Inoue (=?ISO-2022-JP?B?GyRCMGY+ZU5JPy4bKEI=?=) X-Dispatcher: imput version 980905(IM100) Lines: 26 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Not to beat around dead horse - but what was the final > > outcome of the "which IPv6 vendor" thread a few weeks > > back? Will 3.1-CURRENT get an IPsec and IPv6? To be > > very honest - I am more interested in IPsec then v6. > Then take it either from OpenBSD or from the KAME folks. I think it would > be unwise to choose one implementation over the other considereing they'll > be merged in a few months. KAME for 3.0 is almost ready. (IPsec and IPv6 is working. Some user-land work is left.) And I can make KAME for current as the next step, if it is necessary. Because unified-ipv6 issue happened when I began TCP v4/v6 merging, I tried to make TCP part alike INRIA code, as much as possible. However this is not from formal unified-ipv6 source tree. It is being prepared separately. If IPsec and IPv6 is needed for FreeBSD current so urgently, KAME will soon be available. (But some major change will happen in the future, as it is unified with other IPv6 protocol stacks) Or if people think more unified version should be incorporated at first, it will also be ready in few months. Yoshinobu Inoue shin@kame.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 21:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09871 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 21:01:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shidahara1.planet.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09865 for ; Sat, 26 Dec 1998 21:01:33 -0800 (PST) (envelope-from takawata@shidahara1.planet.kobe-u.ac.jp) From: takawata@shidahara1.planet.kobe-u.ac.jp Received: from libr.scitec.kobe-u.ac.jp (cs2d240.ppp.infoweb.ne.jp [202.219.141.200]) by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id NAA10199; Sun, 27 Dec 1998 13:52:31 +0900 (JST) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by libr.scitec.kobe-u.ac.jp (8.9.1/3.5Wpl7) with ESMTP id NAA04526; Sun, 27 Dec 1998 13:58:07 +0900 (JST) Message-Id: <199812270458.NAA04526@libr.scitec.kobe-u.ac.jp> To: Drew Baxter Cc: hackers@FreeBSD.ORG Subject: Re: Please test my code for Intel onboard SMBus function. In-reply-to: Your message of "Sat, 26 Dec 1998 14:07:03 EST." <4.1.19981226140415.00c2a8b0@genesis.ispace.com> Date: Sun, 27 Dec 1998 13:58:06 +0900 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.1.19981226140415.00c2a8b0@genesis.ispace.com>, Mr./Ms. Drew Baxter wrote. >I get this: >Loki# ./spd >OPEN: No such file or directory > >It'd probably help to have the stuff to throw into mknod, because I don't >have a /dev/smb*.. :-) % cd /dev % mknod smb0 c 106 0 . . . % mknod smb5 c 106 5 I'll incorporate it later. And currently the generic driver code does not have the way to report error to userland,and device name is hard coded.(Sorry.) So if you get odd result,replace device name into /dev/smb[1-4]. (Normally you will get output 'Bytes used:128'.) Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 21:28:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12035 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 21:28:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ime.net (ime.net [209.90.192.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12030 for ; Sat, 26 Dec 1998 21:28:29 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4044.ime.net [209.90.195.54]) by ime.net (8.8.7/8.8.7) with SMTP id AAA17841; Sun, 27 Dec 1998 00:28:09 -0500 (EST) Message-Id: <4.1.19981227002412.00a86a10@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 27 Dec 1998 00:25:34 -0500 To: takawata@shidahara1.planet.kobe-u.ac.jp From: Drew Baxter Subject: Re: Please test my code for Intel onboard SMBus function. Cc: hackers@FreeBSD.ORG In-Reply-To: <199812270458.NAA04526@libr.scitec.kobe-u.ac.jp> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:58 PM 12/27/98 +0900, takawata@shidahara1.planet.kobe-u.ac.jp wrote: >In message <4.1.19981226140415.00c2a8b0@genesis.ispace.com>, Mr./Ms. Drew >Baxter wrote. > >>I get this: >>Loki# ./spd >>OPEN: No such file or directory >> >>It'd probably help to have the stuff to throw into mknod, because I don't >>have a /dev/smb*.. :-) > >% cd /dev >% mknod smb0 c 106 0 >. >. >. >% mknod smb5 c 106 5 > >I'll incorporate it later. > >And currently the generic driver code does not have the way to report >error to userland,and device name is hard coded.(Sorry.) >So if you get odd result,replace device name into /dev/smb[1-4]. >(Normally you will get output 'Bytes used:128'.) Loki# gcc -o spd spd.c Loki# ./spd OPEN: Invalid argument Nothing too impressive there.. I'm running as root as well. Loki# cd /dev Loki# ls -al smb* crw-r--r-- 1 root wheel 106, 0 Dec 27 00:23 smb0 crw-r--r-- 1 root wheel 106, 1 Dec 27 00:23 smb1 crw-r--r-- 1 root wheel 106, 2 Dec 27 00:23 smb2 crw-r--r-- 1 root wheel 106, 3 Dec 27 00:23 smb3 crw-r--r-- 1 root wheel 106, 4 Dec 27 00:23 smb4 crw-r--r-- 1 root wheel 106, 5 Dec 27 00:24 smb5 even doing u+xrw (chmod) doesn't work either.. ideas? :-) --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 22:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15528 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 22:12:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15523 for ; Sat, 26 Dec 1998 22:12:21 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.1+3.1W/3.7W) with ESMTP id PAA09698; Sun, 27 Dec 1998 15:11:59 +0900 (JST) To: Yoshinobu Inoue (=?ISO-2022-JP?B?GyRCMGY+ZU5JPy4bKEI=?=) cc: hackers@FreeBSD.ORG In-reply-to: shin's message of Sun, 27 Dec 1998 13:24:44 JST. <19981227132444B.shin@nd.net.fujitsu.co.jp> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPv6 - when? which? From: Jun-ichiro itojun Hagino Date: Sun, 27 Dec 1998 15:11:59 +0900 Message-ID: <9694.914739119@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If IPsec and IPv6 is needed for FreeBSD current so urgently, KAME will >soon be available. (But some major change will happen in the future, >as it is unified with other IPv6 protocol stacks) >Or if people think more unified version should be incorporated at >first, it will also be ready in few months. "IPsec-only KAME" release for FreeBSD 3.0 will be available next week (hopefully). I'm working on it... I'll provide it as patchkit. We have several issues to be nailed down: - can I, or someone, safely import it to repository on freefall? commit logs provide a good way to track down when the crypto code crossed the border, and by who :-( - how should we import? which part must be imported into which repository? (freefall or somewhere else?) - how to redistribute IPsec part in the future? I don't want to see Jordan going to jail for redistributing IPsec :-P itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 22:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15549 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 22:12:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ime.net (ime.net [209.90.192.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15539 for ; Sat, 26 Dec 1998 22:12:28 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from celeris (56k-port4044.ime.net [209.90.195.54]) by ime.net (8.8.7/8.8.7) with SMTP id BAA21200; Sun, 27 Dec 1998 01:12:09 -0500 (EST) Message-Id: <4.1.19981227010910.00ae6160@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 27 Dec 1998 01:09:34 -0500 To: takawata@shidahara1.planet.kobe-u.ac.jp From: Drew Baxter Subject: Re: Please test my code for Intel onboard SMBus function. Cc: hackers@FreeBSD.ORG In-Reply-To: <199812270458.NAA04526@libr.scitec.kobe-u.ac.jp> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:58 PM 12/27/98 +0900, takawata@shidahara1.planet.kobe-u.ac.jp wrote: >In message <4.1.19981226140415.00c2a8b0@genesis.ispace.com>, Mr./Ms. Drew >Baxter wrote. > >>I get this: >>Loki# ./spd >>OPEN: No such file or directory >> >>It'd probably help to have the stuff to throw into mknod, because I don't >>have a /dev/smb*.. :-) > >% cd /dev >% mknod smb0 c 106 0 >. >. >. >% mknod smb5 c 106 5 > >I'll incorporate it later. > >And currently the generic driver code does not have the way to report >error to userland,and device name is hard coded.(Sorry.) >So if you get odd result,replace device name into /dev/smb[1-4]. >(Normally you will get output 'Bytes used:128'.) ../../dev/iicbus/iicbus.c:150: unbalanced `#endif' ../../dev/iicbus/iicbus.c:175: unbalanced `#endif' I get this during make depend after patching.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange, Bangor Maine USA http://www.droo.orland.me.us PGP ID: 409A1F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18104 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:01:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18097 for ; Sat, 26 Dec 1998 23:01:07 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA19600; Sat, 26 Dec 1998 23:00:34 -0800 (PST) (envelope-from obrien) Message-ID: <19981226230034.A19562@nuxi.com> Date: Sat, 26 Dec 1998 23:00:34 -0800 From: "David O'Brien" To: Yoshinobu Inoue , hackers@FreeBSD.ORG Subject: Re: IPv6 - when? which? Reply-To: obrien@nuxi.ucdavis.edu References: <19981226170509.A20826@keltia.freenix.fr> <19981227132444B.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981227132444B.shin@nd.net.fujitsu.co.jp>; from Yoshinobu Inoue on Sun, Dec 27, 1998 at 01:24:44PM +0900 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If IPsec and IPv6 is needed for FreeBSD current so urgently, KAME will > soon be available. (But some major change will happen in the future, > as it is unified with other IPv6 protocol stacks) Personally, I would like to see *some* movement on this issue. However small it is. (shoot, even the creation of an empty src/sys/netinet/ip_v6.h would be enough as it would so some movement) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:05:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA18492 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:05:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA18487 for ; Sat, 26 Dec 1998 23:05:27 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA19616; Sat, 26 Dec 1998 23:04:54 -0800 (PST) (envelope-from obrien) Message-ID: <19981226230454.B19562@nuxi.com> Date: Sat, 26 Dec 1998 23:04:54 -0800 From: "David O'Brien" To: Mark Newton , freebsd-hackers@FreeBSD.ORG Subject: Re: LDT entries - Proposed change Reply-To: obrien@nuxi.ucdavis.edu References: <199812260504.VAA29295@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Julian Elischer on Sat, Dec 26, 1998 at 03:28:40PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think there is enough already running that it SHOULD > be committed. \begin{AOL} me too :-) \end{AOL} -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) P.S. the sooner the better, to give more time for little nits to shake down before 3.0.1. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19352 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:17:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19347 for ; Sat, 26 Dec 1998 23:17:22 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA19651; Sat, 26 Dec 1998 23:16:47 -0800 (PST) (envelope-from obrien) Message-ID: <19981226231646.C19562@nuxi.com> Date: Sat, 26 Dec 1998 23:16:46 -0800 From: "David O'Brien" To: spork , Bernd Walter Cc: hackers@FreeBSD.ORG Subject: Re: NFS thoughts Reply-To: obrien@nuxi.ucdavis.edu References: <19981214073605.20458@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from spork on Mon, Dec 14, 1998 at 11:13:03AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can anyone else help confirm that in general 2/udp is the most dependable > way to run if you're not traversing anything slower than 100Mb? Have you tried 3/udp or 2/tcp to see if the problem is with the transport port (ie. UDP/TCP) or the NFS protocol? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:20:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19678 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:20:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19673 for ; Sat, 26 Dec 1998 23:20:37 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA19672; Sat, 26 Dec 1998 23:18:55 -0800 (PST) (envelope-from obrien) Message-ID: <19981226231855.D19562@nuxi.com> Date: Sat, 26 Dec 1998 23:18:55 -0800 From: "David O'Brien" To: Bernd Walter , Robert Withrow Cc: dmlb@ragnet.demon.co.uk, hackers@FreeBSD.ORG Subject: Re: NFS thoughts Reply-To: obrien@nuxi.ucdavis.edu References: <19981214191651.22189@cicely.de> <199812150156.UAA28685@spooky.rwwa.com> <19981215072941.19075@cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981215072941.19075@cicely.de>; from Bernd Walter on Tue, Dec 15, 1998 at 07:29:41AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > returning the wrong IP in a packet. Also, I thought the > > "noconn" option was the work-around for this problem. > > intereting - since all my recent machines shows the following when amd > is nfs-mounting: Dec 9 07:40:34 cicely5 amd[940]: noconn option > exists, and was turned OFF! (May cause NFS hangs on some systems...) > > Where can I place this option? > Can't find it in any manpage. UTSL :-) It is addressed in the Amd souce in some comments I can't quite understand what they are saying. So I left it alone with I imported the new Amd. I really need to email the Amd people to understand just what they were getting at. In their code the Amd people tend to lump all the BSDs together (including 4.4BSD proper). So I'm not sure what they think applys to us and what to the other BSD groups. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:21:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19904 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:21:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19899 for ; Sat, 26 Dec 1998 23:21:25 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id XAA19696; Sat, 26 Dec 1998 23:20:51 -0800 (PST) (envelope-from obrien) Message-ID: <19981226232050.E19562@nuxi.com> Date: Sat, 26 Dec 1998 23:20:50 -0800 From: "David O'Brien" To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: NFS thoughts Reply-To: obrien@nuxi.ucdavis.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Mon, Dec 14, 1998 at 11:55:21AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > btw, didn't the FreeBSD project pay someone big bucks to fix some of these > problems? > Kirk McKusic was asked to review the code and fix any errors he wanted to. He he noticed a few obvious errors and some architectural problems. He didn't have the time and inclination to fix the architectural problems. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 26 23:43:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA20813 for freebsd-hackers-outgoing; Sat, 26 Dec 1998 23:43:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA20808 for ; Sat, 26 Dec 1998 23:43:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA42331; Sat, 26 Dec 1998 23:43:06 -0800 (PST) (envelope-from dillon) Date: Sat, 26 Dec 1998 23:43:06 -0800 (PST) From: Matthew Dillon Message-Id: <199812270743.XAA42331@apollo.backplane.com> To: zhihuizhang Cc: hackers Subject: Re: Questions about interrupt handling References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :I know that FreeBSD handles interrupts on a software basis which means :that we do not mask any interrupt off in 8259. I am just wondering if a :certain interrupt is masked off in 8259 or it does not get serviced quick :enough, what will the device controller (such as disk controller) respond? :Will it re-issue the interrupt or just give up? Or will it NOT generate :another interrupt until the previous one has been serviced? Maybe :different device controllers behave differently. : :Thanks for any help. : :-------------------------------------------------- :| Zhihui Zhang, http://cs.binghamton.edu/~zzhang | On Intel machines, virtually all interrupts are edge triggered. They occur once and the system must 'remember' them if it can't deal with them instantly. The hardware interrupt is not reissued. One of the oddest problems with Intel boxes is the keyboard interrupt. If you loose the interrupt, the controller can get into a state where it doesn't issue another interrupt every again. The code required to deal with this is messy but there isn't much we can do about it -- it's the hardware that is screwing up. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
;\ + # remains + <-a>;<-o> *** /dev/null Tue Dec 22 02:02:53 1998 --- /usr/src/usr.bin/colldef/data/es_ES.DIS_8859-15.src Mon Dec 21 22:13:46 1998 *************** *** 0 **** --- 1,38 ---- + # Espan~ol (backward compatible with ASCII) + # + # $Id: es_ES.DIS_8859-15.src,v 1.3 1997/02/22 19:54:35 peter Exp $ + # + charmap map.DIS_8859-15 + order \ + # controls + ;...;;;...;;\ + # + ;;!;;\";<<<>;/>>;;\ + ;;;;;\ + %;&;';\(;\);*;+;<+->;<-:>;<*X>;\,;<-->;-;.;/;\ + # digits + 0;(1,<1S>);(2,<2S>);(3,<3S>);4;...;9;\ + # + :;\;;\<;=;>;?;;;;;;;\ + # capital + (A,,,>,,,,);\ + B;(C,);{CH,Ch};D;(E,,,>,);\ + F;G;H;(I,,,>,);\ + J;...;K;L;{LL,Ll};M;(N,);(O,,,>,,,,);\ + P;Q;R;{RR,Rr};(S,);T;(U,,,>,);\ + V;W;X;(Y,,);(Z,);\ + ;;\ + # + [;\\;];^;_;<'m>;`;\ + # small + (a,,,>,,,,);\ + b;(c,);ch;d;(e,,,>,);\ + f;g;h;(i,,,>,);\ + j;...;k;l;ll;m;(n,);(o,,,>,,,,);\ + p;q;r;rr;(s,);t;(u,,,>,);\ + v;w;x;(y,,);(z,);\ + ;;;\ + # + \{;;|;\};~;<.M>;;;