From owner-freebsd-hackers Sun Mar 7 2: 4:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DA53414BE4 for ; Sun, 7 Mar 1999 02:04:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA97959; Sun, 7 Mar 1999 11:03:42 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903071003.LAA97959@freebsd.dk> Subject: Re: GGI In-Reply-To: <19990307152541.O4858@rf900.physics.usyd.edu.au> from David Dawes at "Mar 7, 1999 3:25:41 pm" To: dawes@rf900.physics.usyd.edu.au (David Dawes) Date: Sun, 7 Mar 1999 11:03:42 +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 It seems David Dawes wrote: > >Just FWIW, I was approached by one of the GGI group (actually, in the > >employ of Creative, who are apparently going crazy right now about > >cross-platform support) at Linuxworld. The GGI folks seem quite fervent > >about fixing GGI so that everyone loves it, and they see FreeBSD as > >possibly a better place to start getting it right than Linux (which > >already has a half-assed framebuffer driver). > > Speaking of which (the Linux fb driver, not GGI), we're just adding a > driver to XFree86 4.0 that can use the Linux fb driver. It is useful > from our point of view for getting initial unaccelerated support for > otherwise unsupported video cards. I had a feeling that something > similar could be done for FreeBSD (using the VESA support in -current). > Is that right? If so, is anyone interested in doing it? It can easily be done using the VESA stuff and/or libvgl. And no, I think I have plenty on my platter for the time being :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 7: 7:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id 8FA2714C4E for ; Sun, 7 Mar 1999 07:07:01 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.9.2/8.8.8) with ESMTP id PAA83502; Sun, 7 Mar 1999 15:06:43 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA01343; Sun, 7 Mar 1999 13:54:13 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199903071354.NAA01343@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Stevenson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DTMF detection with a modem In-reply-to: Your message of "Sun, 07 Mar 1999 13:12:21 +1000." <199903070312.NAA10121@nias.int.gu.edu.au.> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 13:54:13 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I was just wondering if there was an easy way to use a modem for DTMF decoding > under FreeBSD. The only info I can find seems to assume you are using TAPI under > Windows. Does it vary from modem to modem? I have a fairly old version of vgetty (mgetty+sendfax) that does limited DTMF processing. It's set to execute a script when it receives ``*N#'' where N is one or more digits. N is passed as an argument to the script. From what I remember, it wasn't a port at that point, but it probably is now. > Thanks, > > Andrew -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 10:24: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id D819B14D6D for ; Sun, 7 Mar 1999 10:23:43 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id MAA01086 for freebsd-hackers@freebsd.org; Sun, 7 Mar 1999 12:23:25 -0600 (CST) (envelope-from bob) Date: Sun, 7 Mar 1999 12:23:25 -0600 From: Bob Willcox To: hackers list Subject: Need help isolating prob w/rtc0 intr's stopping Message-ID: <19990307122325.A969@luke.pmr.com> Reply-To: Bob Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm hoping that someone out there can give me some suggestions on what I can do to track down a problem I'm having on my dual Xeon system that's running 3.1-stable. When I first boot the machine rtc0 interrupts just fine, however, as soon as I put a load on it (like starting X) my rtc0 interrupts stop. This causes all of the system monitors (like top, vmstat, iostat, etc.) to display 0% cpu usage and idle times. My system is consists of the following: ASUS XG-DLS motherboard 2 Xeon 400MHz/512KB cache processors 512MB of ECC SDRAM Note that if I boot a UP kernel the problem does not occur. I have exchanged email with Tor Egge who suggested that I change the interrupt vector for IRQ8 (from 0x68 to 0x48) but that didn't solve the problem. I have already opened a PR on this: kern/10411. Thanks for any help you can offer, Bob -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 10:44:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (Postfix) with ESMTP id 1750714D75 for ; Sun, 7 Mar 1999 10:44:29 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA07169; Sun, 7 Mar 1999 19:52:06 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 7 Mar 1999 19:52:06 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD and ThinkPad In-Reply-To: <199903070214.SAA01052@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Mar 1999, Mike Smith wrote: > > To start with, does it have more than 64M of memory? At least some of > the stinkpads have problems with our speculative memory probes. Yeah, 128MB. I've put "MAXMEM" into kernel config file, and it seemed to help. But overall, I'm really less than pleased with this sucker. One thing is the BIOS which requires Windows to configure anything significant, the other thing is built-in softmodem (which of course will not work). My impression is that under the hood this machine is not quite a PC, but WinIBM or something :-( I still experience total freezes when accessing sio0. The same goes for 'pnpinfo' - machine freezes completely, and only hard reboot helps. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 12:52:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id EA87914D6A for ; Sun, 7 Mar 1999 12:52:41 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id NAA00926; Sun, 7 Mar 1999 13:52:24 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd000916; Sun Mar 7 13:52:23 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id NAA28076; Sun, 7 Mar 1999 13:52:22 -0700 (MST) From: Terry Lambert Message-Id: <199903072052.NAA28076@usr04.primenet.com> Subject: Re: pipe(2) To: brian@Awfulhak.org (Brian Somers) Date: Sun, 7 Mar 1999 20:52:21 +0000 (GMT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199903070234.CAA12643@keep.lan.Awfulhak.org> from "Brian Somers" at Mar 7, 99 02:34:23 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Should pipe(2) be a bit stronger about what's ``conventional'' and > mention that two uni-directional descriptors are returned by most > operating systems ? I've been stung twice recently because I've > assumed that the descriptors are bidirectional :-( > > If there are no objections, I'll update the man page: [ ... ] > +.Sh STANDARDS > +POSIX does not require that each descriptor is bidirectional. For > +portability reasons, unidirectional descriptors should be assumed. > .Sh HISTORY In addition to the statement: The bidirectional nature of this implementation of pipes is not portable to older systems, so it is recommended to use the convention for using the endpoints in the traditional manner when using a pipe in one direc- tion. I guess? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 12:57:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id F288914D40 for ; Sun, 7 Mar 1999 12:57:20 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id NAA20544; Sun, 7 Mar 1999 13:56:48 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36E2E810.B9D679EF@softweyr.com> Date: Sun, 07 Mar 1999 13:56:48 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Vince Vielhaber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vince Vielhaber wrote: > > On 06-Mar-99 Wes Peters wrote: > > > Speaking of which, has anyone looked at doing a port of AbiWord from > > AbiSource yet? Conceptually, the idea of a freely available word > > processor that stores documents in XML sounds great. > > Never even heard of it. Care to elaborate? No, let's let THEM elaborate: http://www.abisource.com/ ;^) Apparently they have early-access versions that run on Linux and do something useful now. I've been meaning to scarf a binary and give it a whirl here, but I've been buried lately. Maybe this afternoon, while the rest of the family is napping. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 13:20: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 270ED14DA9 for ; Sun, 7 Mar 1999 13:19:56 -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 NAA03851 for ; Sun, 7 Mar 1999 13:19:31 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903072119.NAA03851@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: usb irq 255?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 13:19:31 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dmesg output: create_intr: requested irq255 too high, limit is 15 usb0: could not map irq Does anyone have a clue as to why the usb driver is requesting an IRQ 255? System : Petium III 450 Mhz 128MB sdram, I-Will BX based motherboard . USB device: Microsoft keyboard. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 14:22:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (Postfix) with ESMTP id 4192F154CC for ; Sun, 7 Mar 1999 14:22:36 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id QAA26652; Sun, 7 Mar 1999 16:22:05 -0600 (CST) From: Kevin Day Message-Id: <199903072222.QAA26652@home.dragondata.com> Subject: Re: usb irq 255?? In-Reply-To: <199903072119.NAA03851@rah.star-gate.com> from Amancio Hasty at "Mar 7, 1999 1:19:31 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 7 Mar 1999 16:22:04 -0600 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > dmesg output: > > create_intr: requested irq255 too high, limit is 15 > usb0: could not map irq > > Does anyone have a clue as to why the usb driver is requesting an IRQ 255? > > System : Petium III 450 Mhz 128MB sdram, I-Will BX based motherboard . > USB device: Microsoft keyboard. > > Tnks, > Amancio > > This happened to me, until I went into the BIOS setup and enabled 'USB Operation' or some other cryptic setting.... USB works even when it's turned off, on my system, just no IRQ gets assigned..... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 14:36: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.42]) by hub.freebsd.org (Postfix) with ESMTP id 1235414DEF for ; Sun, 7 Mar 1999 14:35:06 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id QAA80669; Sun, 7 Mar 1999 16:33:28 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 7 Mar 1999 16:33:27 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: robert@kudra.com Cc: freebsd-hackers@freebsd.org Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14049.29637.311448.247778@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Robert Sexton on Sat, 6 March: : One point I'd add is that Linux without add ons is pretty much : unusable. Since its a kernel, you need add ons to even log in. : FreeBSD is a coherent OS because its a complete package out of the : box. We have a usable base system. And there's no dispute of which : things are add ons and which aren't. Attempts to expand the base : system have met with what I'd consider justified resistance. I object to the current modularization, precisely because it is either bloated or inadequate, depending on your application. The circulation would only benefit if the system was easier to tailor to the application. This would result from layering the functional areas -- a development package, and admin tool package, a networking package, an X server package, etc. The base system has expanded. DHCP is one recent example. In the modern world, a system without DHCP is much less generally useful than one with DHCP. MIME should be another functional adaptation to the modern environment. Uu-coding can go. (Well, not yet, but before I die.) : Thats why we have the ports tree. If we switched to : elm for instance, that would be a wasted megabye of disk for me, and : many other people. Can you say 'Creeping Featureism?' Like DHCP. Or C++. Creeping Featurism? I don't think so. But it would be better to be able to trivially configure a system without DHCP, or C++, or MIME, I agree. : If I may be so presumptious, I'd say that the coherent vision is that : we have the smallest base distribution which makes up a complete : system, and that the rest can be convieniently flavored to taste. 'Complete system' is not a fungible term. It's a semantic game. One person's complete system in another person's bloated monstrosity or underpowered midget. : > MHO: If the included mail reader is not 'decent', throw it away. Oh, : > replacing UCB mail is socially difficult, but such compunctions seem : > to be damaging the future of the product, its coherent vision, and its : > ability to keep up with the times. : : This is the path that has made linux such a mess. There is _no_way_ : that FreeBSD could even include a mail reader that would make most : people happy. Nor should it try! I'm not arguing for making people happy. I'm arguing for going the minimum lawful speed on the freeway. That speed has gone up in the past few years, on this particular freeway. If you can't drive at the minimum speed, stay off the freeway. Linux qua apple, not orange. You should compare the kernel to Linux, And the distribution to SUSE/RedHat/Debian/Caldera -- all of which are much better candidates for a general end-user *or* server OS than is FreeBSD on the evidence of circulation alone. (FreeBSD will never be given a fair shot unless its circulation rises sufficiently to be a known contender.) FreeBSD 2.1.x is perfect for some people. FreeBSD 2.2.x is perfect for some people. FreeBSD 3.x is perfect for some people. -current is perfect for some people. That's great, but -current is becoming something, something new. That new thing will not be an improvement for those who find 2.2.x to be perfect. I am of the impression that -current exists for a number of distinct reasons, significant among them being 1) a desire to sell CDs on the part of Walnut Creek 2) a desire for control/self-actualization/money on the part of core/committers 3) a desire for a certain product by the end-users with the last being as diverse as the user base. While the 4.x user base will overlap with the 3.x user base, it is (1) hopeful that the subscription base will increase by virtue of the product being more competetive in order to provide a hope of a business future, and (2) hopeful that it will fulfill the needs of its contributors in order to provide a hope of a technical future. : You've touched upon what can only be called a religeous issue. : Based on my take of of the user base, nobody here wants FreeBSD to be : a general purpose platform 'out of the box'. The consensus seems to : be that the minimal system is quite popular. Well, Sam, it certainly is not 'minimal'. PicoBSD is more like minimal. There is a minimal Linux distribution too, the name of which I forget. : I for one don't want to schlep around a lot of mime code that my news : machine will never run. Likewise for uucp :-) Its not just that we've : got to support the old machine crowd, but that bloat is in general : bad. Ugh. Then stick to 2.1.X -- certainly don't run 3.x! But I agree that bloat is bad (that's part of the meaning of the word 'bloat'). The current system is much more bloated than past systems, in the sense that if you add up the number of unused bits in each installation, it is much, much larger. : > I still think FreeBSD should be packaged as a layered system, a group : > of functional complexes serving different areas. And sooner rather : > than later, for as it grows the components of what should be distinct : > modules become increasingly interdependent. : : This the solution to the problem that could make everybody happy. : So hows it coming along, Jordan? :-) Is there actual motion in this direction? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 15:27:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 3919214DEF for ; Sun, 7 Mar 1999 15:27:10 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id PAA04325; Sun, 7 Mar 1999 15:26:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903072326.PAA04325@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Day Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Sun, 07 Mar 1999 16:22:04 CST." <199903072222.QAA26652@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 15:26:42 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you happen to know if the USB keyboard sub driver works or the proper kernel configuration? Because after I modified the BIOS to assing an IRQ to the USB port and booted again my keyboard does not work. Say whats a good AGP video board for FreeBSD? Tnks Again! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 15:39:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 5E60614DC1 for ; Sun, 7 Mar 1999 15:39:49 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id PAA04392 for ; Sun, 7 Mar 1999 15:39:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903072339.PAA04392@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Sun, 07 Mar 1999 16:22:04 CST." <199903072222.QAA26652@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 15:39:23 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, now after Kevin's suggestion of tweaking the sytstem BIOS to assigning an IRQ to the USB controller I cant use the keyboard on my new system. Every time that I type , I get : . (28) pressed 40 . (30) pressed 4 . . . It looks like the USB device driver is stucked in echoing debug messages. Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 18: 4: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from absinthe.shenton.org (Absinthe.Shenton.Org [209.31.147.194]) by hub.freebsd.org (Postfix) with ESMTP id 6A81C14D9E for ; Sun, 7 Mar 1999 18:04:03 -0800 (PST) (envelope-from chris@shenton.org) Received: (from chris@localhost) by absinthe.shenton.org (8.9.1/8.9.1) id VAA14818; Sun, 7 Mar 1999 21:03:44 -0500 (EST) To: hackers@freeBSD.org Subject: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs X-Emacs: Emacs 20.3, MULE 4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.8.5 - "Nishi-Takaoka") Content-Type: text/plain; charset=US-ASCII From: Chris Shenton Date: 07 Mar 1999 21:03:43 -0500 Message-ID: <877lsslou8.fsf@absinthe.shenton.org> Lines: 44 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Been trying to use both Amanda and a simple script to dump my local filesystems to a HP Colorado T4000 Travan-4 SCSI tape drive, /dev/nrsa0. It appears to NOT be honoring the "no rewind" device and therefore rewinding and overwriting all earlier files. This breaks backups, etc. Doing simple Amanda "amlabel" talks to nrsa0 OK but it appears to read the tape, rewind, write the amanda label (file 1), rewind AGAIN, and then store the first filesystem template (file 2). But the second rewind causes file 2 to overwrite file 1. It acts like it's not honoring the "no rewind" flag. Doing something simpler -- a little script which loops over my local filesystems and does a dump to nrst0 -- has similar behavior. It dumps /, /var, /usr, and /home each time rewinding between dumps thus overwriting the previous filesystem image. I finally discovered in /var/log/messages errors like: Mar 7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0 Mar 7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:2c,0 Mar 7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): Command sequence error Mar 7 20:10:01 Thanatos /kernel: (sa0:ahc0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety Mar 7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): SPACE. CDB: 11 1 ff ff ff 0 Mar 7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:2c,0 Mar 7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): Command sequence error Mar 7 20:35:56 Thanatos /kernel: (sa0:ahc0:0:5:0): unable to backspace over one of double filemarks at EOD- opting for safety And I see these times correlate with the times my script goes to dump the next filesystem: # /sbin/dump 0aubf 128 /dev/nrsa0 /usr DUMP: Date of this level 0 dump: Sun Mar 7 20:10:01 1999 DUMP: level 0 dump on Sun Mar 7 20:10:01 1999 [...] DUMP: Closing /dev/nrsa0 # /sbin/dump 0aubf 128 /dev/nrsa0 /home DUMP: Date of this level 0 dump: Sun Mar 7 20:35:56 1999 I believe I had this T4000 drive working fine back on 2.2.8-STABLE. Anything I can do to debug the problem? Makes it pretty useless for backups. :-( Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 18:10:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 65B4214E16 for ; Sun, 7 Mar 1999 18:10:08 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id TAA27724; Sun, 7 Mar 1999 19:09:43 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id TAA28284; Sun, 7 Mar 1999 19:09:32 -0700 Date: Sun, 7 Mar 1999 19:09:32 -0700 Message-Id: <199903080209.TAA28284@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: alk@pobox.com Cc: robert@kudra.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <14049.29637.311448.247778@avalon.east> References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The base system has expanded. DHCP is one recent example. > In the modern world, a system without DHCP is much less generally > useful than one with DHCP. MIME should be another functional > adaptation to the modern environment. I disagree completely. DHCP is necessary for running the machine, email is not necessary, which is why sendmail is easily disabled and/or removed. Finally, there is *NO* way to distribute a standard MIME client that will not add bloat. I use XEmacs + VM, alot of people use Pine, others use ELM, others mush, others who knows what. None of them are 'best' to be shipped with FreeBSD. A mail client is exactly like an editor or shell. There is no 'correct' answer, so by shipping the simplest (smallest) version out there, then the user is allowed to choose whatever version they like. This *IS* the unix way, and any attempts to make FreeBSD into Linux and it's 'all things to all people' will validly be met with resistence. M$ is taking it in the shorts for doing such a thing, and people are moving to FreeBSD because it tries to have the base system work well. > : This is the path that has made linux such a mess. There is _no_way_ > : that FreeBSD could even include a mail reader that would make most > : people happy. > > Nor should it try! I'm not arguing for making people happy. I'm > arguing for going the minimum lawful speed on the freeway. MIME attachments are *NOT* the standard form of email used on the internet. As a matter of fact, I would venture to guess that 99% of the email traffic on the internet does not contain MIME attachments. Many ISP's are now refusing to accept MIME attachments due to the spreading of virus's and SPAM. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 19: 4:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dhcp9547172.columbus.rr.com (dhcp9547172.columbus.rr.com [24.95.47.172]) by hub.freebsd.org (Postfix) with ESMTP id 5921F14DEB for ; Sun, 7 Mar 1999 19:04:13 -0800 (PST) (envelope-from rowland@dhcp9547172.columbus.rr.com) Received: (from rowland@localhost) by dhcp9547172.columbus.rr.com (8.9.2/8.9.2) id WAA11793; Sun, 7 Mar 1999 22:02:02 -0500 (EST) (envelope-from rowland) To: Nate Williams Cc: alk@pobox.com, robert@kudra.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> X-Face: "<|%>c@Vfv/8}+Av1z:R5sDzf!3QVer!n\,.&+&h\k1,BHAoyw8Gp10<-SqZ<*"|!U!a#xg6ls?1,Vj$m@r?uHcfB,'i:LLgtyb;~}O8v7zZThuB`X~#IE{v*"PhI]cl/>&ys(MGa%y:6~TuHFw&~|V?!9HZ_R"<}dC5D:%igP2Q6ZJex,P0M From: Shaun Rowland Date: 07 Mar 1999 22:02:01 -0500 In-Reply-To: Nate Williams's message of "Sun, 7 Mar 1999 19:09:32 -0700" Message-ID: <87bti4fzva.fsf@dhcp9547172.columbus.rr.com> Lines: 34 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: > > Finally, there is *NO* way to distribute a standard MIME client that > will not add bloat. I use XEmacs + VM, alot of people use Pine, others > use ELM, others mush, others who knows what. > > None of them are 'best' to be shipped with FreeBSD. I can agree with this. It makes sense... but below: > MIME attachments are *NOT* the standard form of email used on the > internet. As a matter of fact, I would venture to guess that 99% of the > email traffic on the internet does not contain MIME attachments. Many > ISP's are now refusing to accept MIME attachments due to the spreading > of virus's and SPAM. MIME attachments are extensions to the SMTP protocol, and are as such definitely standards. They *ARE* standard extensions, and thus forms of email used on the Internet. I have not heard of any ISPs blocking MIME attachments either. That is not only ridiculous, but rather stupid and a bad decision from a business standpoint. The use of MIME attachments is also much higher than 1%... I would venture to guess. SPAM has nothing to do with MIME either. Not only is MIME a part of email, but Usenet and the Web. Read some RFCs. As the name implies, what you have said above is is not correct. -- Shaun Rowland rowland@cis.ohio-state.edu IICF System Administrator DL798 http://www.cis.ohio-state.edu/~rowland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 19:55:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ensim.com (bigip14.aitcom.net [208.234.0.29]) by hub.freebsd.org (Postfix) with ESMTP id 3209214C57 for ; Sun, 7 Mar 1999 19:55:10 -0800 (PST) (envelope-from wilson@ensim.com) Received: from ensim.com (goldengate.ensim.net [209.150.239.146]) by ensim.com (8.8.8/8.8.5) with ESMTP id WAA08271 for ; Sun, 7 Mar 1999 22:54:51 -0500 Message-ID: <36E34B29.67D3F564@ensim.com> Date: Sun, 07 Mar 1999 22:59:37 -0500 From: Xun Wilson Huang Organization: Ensim Corp. X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: system call test suite? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there any system call test suites avaialbe? Say, when one release of FreeBSD is made, is there any toolsets being use to make sure that all, or at least only system calls past the test? wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 20:18:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 7907C14DC6 for ; Sun, 7 Mar 1999 20:18:11 -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 UAA05489 for ; Sun, 7 Mar 1999 20:17:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903080417.UAA05489@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-hackers@FreeBSD.ORG Subject: usb, ums0 ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 20:17:43 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bought a USB hub and attached my USB mouse to it . a " cat /dev/ms0" results in instant panic ... Here is the relevant kenel config file segment: controller uhci0 controller ohci0 controller usb0 # # for the moment we have to specify the priorities of the device # drivers explicitly by the ordering in the list below. This will # be changed in the future. # device ums0 device ukbd0 device ulpt0 device uhub0 device ucom0 device umodem0 Just trying to take advantage of some of the capabilities in my system. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 20:27:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat196.27.mpoweredpc.net [142.177.196.27]) by hub.freebsd.org (Postfix) with ESMTP id D597414E67; Sun, 7 Mar 1999 20:27:32 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id AAA51000; Mon, 8 Mar 1999 00:26:02 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 8 Mar 1999 00:26:02 -0400 (AST) From: The Hermit Hacker To: Mike Smith Cc: "Daniel C. Sobral" , Terry Lambert , sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: GGI In-Reply-To: <199903060712.XAA66928@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 Fri, 5 Mar 1999, Mike Smith wrote: > > (changed, subject, list, and cc list... it's almost a new mail! :) > > > > Terry Lambert wrote: > > > > > ... > > > I can't do the work for FreeBSD until it adopts GGI, and supports ELF > > ... > > > > > > The GGI people have been looking for someone (with commit priviledges, > > > obviously) to do a FreeBSD port, and have gone so far as to put the > > > kernel pieces of their predominantly Linux project *in the public domain*. > > > > I looked at GGI, and I liked it. If my memory doesn't fail me, Soren > > remarked that he was not much impressed with it last he checked it. > > > > What I'd like to know is if the Powers That Be of FreeBSD console > > (Soren and Yokota?) would, present state of the code > > notwithstanding, accept the adoption of GGI once deemed to be > > "ready", or if there is any fundamental flaw with it that makes this > > a hopeless propositon. > > Just FWIW, I was approached by one of the GGI group (actually, in the > employ of Creative, who are apparently going crazy right now about > cross-platform support) at Linuxworld. The GGI folks seem quite fervent > about fixing GGI so that everyone loves it, and they see FreeBSD as > possibly a better place to start getting it right than Linux (which > already has a half-assed framebuffer driver). If this means that my Creative Blaster RivaTNT video card will be supported in 3D accelerated mode, I'll volunteer my computer to guinea pig any drivers/software ... A friend just picked himself up a Voodoo2 card that Linux now supports and keeps cramming down the "FreeBSD doesn't support 3D accelleration" line down my throat :( My card is *supposedly* faster then what he has, from comparing specs...be great if I can slam it back down his throat :) 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 Mar 7 21:10:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id D34DE14E03; Sun, 7 Mar 1999 21:09:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA04942; Sun, 7 Mar 1999 21:03:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080503.VAA04942@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: The Hermit Hacker Cc: "Daniel C. Sobral" , Terry Lambert , sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: GGI In-reply-to: Your message of "Mon, 08 Mar 1999 00:26:02 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 21:03:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A friend just picked himself up a Voodoo2 card that Linux now supports and > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > down my throat :( My card is *supposedly* faster then what he has, from > comparing specs...be great if I can slam it back down his throat :) Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite see how "supporting" this card actually achieves anything. If he's talking about GLIDE, you might mention that we support the Linux GLIDE library... -- \\ 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 Mar 7 21:30:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.42]) by hub.freebsd.org (Postfix) with ESMTP id BF55114DBA for ; Sun, 7 Mar 1999 21:29:55 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id XAA83900; Sun, 7 Mar 1999 23:28:23 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 7 Mar 1999 23:28:22 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: nate@mt.sri.com Cc: alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14051.24548.250885.992678@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Nate Williams on Sun, 7 March: : : Finally, there is *NO* way to distribute a standard MIME client that : will not add bloat. mpack/munpack. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 21:48:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id B63DE14DF5 for ; Sun, 7 Mar 1999 21:48:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA05079; Sun, 7 Mar 1999 21:42:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080542.VAA05079@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Sun, 07 Mar 1999 15:39:23 PST." <199903072339.PAA04392@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 21:42:55 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oops, now after Kevin's suggestion of tweaking the sytstem BIOS to assigning > an IRQ to > the USB controller I cant use the keyboard on my new system. > > Every time that I type , I get : > > . (28) pressed 40 > . (30) pressed 4 > . > . > . > It looks like the USB device driver is stucked in echoing debug messages. Ah, you have a USB keyboard, and it's not in AT emulation mode anymore. We don't support USB keyboards yet... -- \\ 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 Mar 7 22: 0:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 39A8A14DF4 for ; Sun, 7 Mar 1999 22:00:30 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA29086; Sun, 7 Mar 1999 22:59:54 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA28627; Sun, 7 Mar 1999 22:59:43 -0700 Date: Sun, 7 Mar 1999 22:59:43 -0700 Message-Id: <199903080559.WAA28627@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Shaun Rowland Cc: Nate Williams , alk@pobox.com, robert@kudra.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <87bti4fzva.fsf@dhcp9547172.columbus.rr.com> References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> <87bti4fzva.fsf@dhcp9547172.columbus.rr.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > MIME attachments are *NOT* the standard form of email used on the > > internet. As a matter of fact, I would venture to guess that 99% of the > > email traffic on the internet does not contain MIME attachments. Many > > ISP's are now refusing to accept MIME attachments due to the spreading > > of virus's and SPAM. > > MIME attachments are extensions to the SMTP protocol, and are as such > definitely standards. I didn't say they weren't a standard, but they aren't the 'standard' way of sending email. Plain-text is the standard email format. > SPAM has nothing to do with MIME either. Tell that to my parents, who get bombarded with sex-gifs and such. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 22: 0:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id A3F3414E3B for ; Sun, 7 Mar 1999 22:00:51 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA29108; Sun, 7 Mar 1999 23:00:33 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA28637; Sun, 7 Mar 1999 23:00:22 -0700 Date: Sun, 7 Mar 1999 23:00:22 -0700 Message-Id: <199903080600.XAA28637@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: alk@pobox.com Cc: nate@mt.sri.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <14051.24548.250885.992678@avalon.east> References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> <14051.24548.250885.992678@avalon.east> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Finally, there is *NO* way to distribute a standard MIME client that > : will not add bloat. > > mpack/munpack. How can they be integrated with bin/mail, which is the standard unix mail reader? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 22: 4:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id CE82814E92 for ; Sun, 7 Mar 1999 22:04:34 -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 WAA05855; Sun, 7 Mar 1999 22:03:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903080603.WAA05855@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Sun, 07 Mar 1999 21:42:55 PST." <199903080542.VAA05079@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 22:03:59 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks, Now how about mouse support, whats needed?. Got a Macally USB mouse and want to give a whirl. Tnks! Amancio > > Oops, now after Kevin's suggestion of tweaking the sytstem BIOS to assigning > > an IRQ to > > the USB controller I cant use the keyboard on my new system. > > > > Every time that I type , I get : > > > > . (28) pressed 40 > > . (30) pressed 4 > > . > > . > > . > > It looks like the USB device driver is stucked in echoing debug messages. > > Ah, you have a USB keyboard, and it's not in AT emulation mode anymore. > > We don't support USB keyboards yet... > -- > \\ 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 Mar 7 22: 5:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from poboxer.pobox.com (unknown [208.149.16.42]) by hub.freebsd.org (Postfix) with ESMTP id 784A614DBE for ; Sun, 7 Mar 1999 22:05:11 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id AAA84846; Mon, 8 Mar 1999 00:03:04 -0600 (CST) (envelope-from alk) From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 8 Mar 1999 00:03:00 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: nate@mt.sri.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> <14051.24548.250885.992678@avalon.east> <199903080600.XAA28637@mt.sri.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14051.26618.409741.264371@avalon.east> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Nate Williams on Sun, 7 March: : > : Finally, there is *NO* way to distribute a standard MIME client that : > : will not add bloat. : > : > mpack/munpack. : : How can they be integrated with bin/mail, which is the standard unix : mail reader? Similarly to uuencode/uudecode: ~|command To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 22: 9:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 7D63814CA7 for ; Sun, 7 Mar 1999 22:09:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA29185; Sun, 7 Mar 1999 23:09:13 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA28680; Sun, 7 Mar 1999 23:09:02 -0700 Date: Sun, 7 Mar 1999 23:09:02 -0700 Message-Id: <199903080609.XAA28680@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: alk@pobox.com Cc: nate@mt.sri.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <14051.26618.409741.264371@avalon.east> References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> <14051.24548.250885.992678@avalon.east> <199903080600.XAA28637@mt.sri.com> <14051.26618.409741.264371@avalon.east> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > : Finally, there is *NO* way to distribute a standard MIME client that > : > : will not add bloat. > : > > : > mpack/munpack. > : > : How can they be integrated with bin/mail, which is the standard unix > : mail reader? > > Similarly to uuencode/uudecode: ~|command Ahh, but that doesn't work well if you have multiple attachments (been there, done that). My old email client (not /bin/mail) did not handle attachments, and I struggled along with the MIME stuff from Bell labs, and they finally gave up and installed a MIME capable reader. However, I rarely have use for them anymore on FreeBSD, since the only non-text files ever sent around are Word documents (with the appropriate version of the Word Virus sprinkled in). Since I don't have word, I have very little use for the attachments. :) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 7 22:33:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat196.27.mpoweredpc.net [142.177.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 290A814E52 for ; Sun, 7 Mar 1999 22:33:10 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id CAA72450; Mon, 8 Mar 1999 02:32:32 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 8 Mar 1999 02:32:31 -0400 (AST) From: The Hermit Hacker To: Mike Smith Cc: sandman@hub.org, freebsd-hackers@FreeBSD.ORG Subject: Re: GGI In-Reply-To: <199903080503.VAA04942@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 Sun, 7 Mar 1999, Mike Smith wrote: > > A friend just picked himself up a Voodoo2 card that Linux now supports and > > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > > down my throat :( My card is *supposedly* faster then what he has, from > > comparing specs...be great if I can slam it back down his throat :) > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > see how "supporting" this card actually achieves anything. > > If he's talking about GLIDE, you might mention that we support the > Linux GLIDE library... Well, let me CC him in...I don't follow Linux too closely, so don't feel that I can adequately comment on this... 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 Mar 7 22:49:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id 10AAC14E15 for ; Sun, 7 Mar 1999 22:49: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.3/8.8.8) with ESMTP id WAA05254; Sun, 7 Mar 1999 22:44:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080644.WAA05254@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Amancio Hasty Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Sun, 07 Mar 1999 22:03:59 PST." <199903080603.WAA05855@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Mar 1999 22:44:09 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tnks, > > Now how about mouse support, whats needed?. > > Got a Macally USB mouse and want to give a whirl. Go for it. Talk to Nick Hibma (n_hibma@freebsd.org) if you have any problems. -- \\ 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 Mar 7 23:40:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.dyn.ml.org (pm3-12.ppp.wenet.net [206.15.85.12]) by hub.freebsd.org (Postfix) with ESMTP id 320F014D43 for ; Sun, 7 Mar 1999 23:40:29 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id XAA60503; Sun, 7 Mar 1999 23:40:07 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sun, 7 Mar 1999 23:40:07 -0800 (PST) From: Alex Zepeda To: Nate Williams Cc: alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <199903080609.XAA28680@mt.sri.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Mar 1999, Nate Williams wrote: > Ahh, but that doesn't work well if you have multiple attachments (been > there, done that). Perhaps this should serve as an incentive for those who would like a MIME capable reader in the base distribution to work on some commandline MIME tools. I for one would object less to a few command line tools to handle MIME "streams" than to a full featured mail client in the base distrib. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 0:51:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orbit.flnet.com (orbit.flnet.com [205.240.232.32]) by hub.freebsd.org (Postfix) with ESMTP id 40DCF14C25; Mon, 8 Mar 1999 00:51:43 -0800 (PST) (envelope-from henrich@orbit.flnet.com) Received: (from henrich@localhost) by orbit.flnet.com (8.8.5/8.8.4) id DAA02696; Mon, 8 Mar 1999 03:51:25 -0500 (EST) Message-ID: <19990308005125.10555@orbit.flnet.com> Date: Mon, 8 Mar 1999 00:51:25 -0800 From: Charles Henrich To: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Erorr: isa_dmainit(2, 1024) failed Mail-Followup-To: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Operating-System: FreeBSD 2.2-BETA_A X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG During startup on my FreeBSD box (a dual proc 1GB system) I see: isa_dmainit(2, 1024) failed And (perhaps) coincidentally any access to the ISA sound card causes the machine to panic with an isa page map missing. Does anyone out there have any ideas whats causing this, and what a solution might be? Thanks! -Crh Charles Henrich Manex Visual Effects henrich@flnet.com http://orbit.flnet.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 0:57:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id E02E314C9D for ; Mon, 8 Mar 1999 00:57:09 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA21804; Mon, 8 Mar 1999 00:48:22 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdM21801; Mon Mar 8 08:48:16 1999 Date: Mon, 8 Mar 1999 00:48:12 -0800 (PST) From: Julian Elischer To: Alex Zepeda Cc: Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 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, 7 Mar 1999, Alex Zepeda wrote: > On Sun, 7 Mar 1999, Nate Williams wrote: > > > Ahh, but that doesn't work well if you have multiple attachments (been > > there, done that). > > Perhaps this should serve as an incentive for those who would like a MIME > capable reader in the base distribution to work on some commandline MIME > tools. I for one would object less to a few command line tools to handle > MIME "streams" than to a full featured mail client in the base distrib. A couple of years ago someone submitted a version of uudecode (they called it something else) that also decoded Base64 and had other functionality. I wonder what happenned of it? julian > > - alex > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 1:17:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles178.castles.com [208.214.165.178]) by hub.freebsd.org (Postfix) with ESMTP id C9B6514E7F; Mon, 8 Mar 1999 01:17:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA05661; Mon, 8 Mar 1999 01:11:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903080911.BAA05661@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Charles Henrich Cc: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed In-reply-to: Your message of "Mon, 08 Mar 1999 00:51:25 PST." <19990308005125.10555@orbit.flnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 01:11:30 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > During startup on my FreeBSD box (a dual proc 1GB system) I see: > > isa_dmainit(2, 1024) failed > > And (perhaps) coincidentally any access to the ISA sound card causes the > machine to panic with an isa page map missing. Does anyone out there have any > ideas whats causing this, and what a solution might be? Thanks! You have too much memory. 8) Seriously, by the time the ISA code gets a chance to allocate memory, all the physically dma-able-to memory is gone for other uses. This is basically a bug in the way kernel memory is handed out. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 1:32:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from copperhead.cisco.com (copperhead.cisco.com [171.69.192.42]) by hub.freebsd.org (Postfix) with ESMTP id D0ABD14CF2 for ; Mon, 8 Mar 1999 01:32:25 -0800 (PST) (envelope-from brainey@cisco.com) Received: (brainey@localhost) by copperhead.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) id BAA12009; Mon, 8 Mar 1999 01:31:51 -0800 (PST) Date: Mon, 8 Mar 1999 01:31:51 -0800 (PST) Message-Id: <199903080931.BAA12009@copperhead.cisco.com> From: Bill Rainey To: julian@whistle.com Cc: garbanzo@hooked.net, nate@mt.sri.com, alk@pobox.com, freebsd-hackers@FreeBSD.ORG In-reply-to: (message from Julian Elischer on Mon, 8 Mar 1999 00:48:12 -0800 (PST)) Subject: Re: base64 Reply-To: brainey@cisco.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you might be referring to uudeview ... pretty handy for dealing with MIME stuff. From the /usr/ports/INDEX uudeview-0.5.13 /usr/ports/converters/uudeview A program for uu/xx/Base64/BinHex de-/encoding. On Sun 8 Mar 1999, Juliuan Elischer wrote: > > On Sun, 7 Mar 1999, Alex Zepeda wrote: > > > On Sun, 7 Mar 1999, Nate Williams wrote: > > > > > Ahh, but that doesn't work well if you have multiple attachments (been > > > there, done that). > > > > Perhaps this should serve as an incentive for those who would like a MIME > > capable reader in the base distribution to work on some commandline MIME > > tools. I for one would object less to a few command line tools to handle > > MIME "streams" than to a full featured mail client in the base distrib. > > A couple of years ago someone submitted a version of uudecode (they called > it something else) that also decoded Base64 and had other functionality. > > I wonder what happenned of it? > > julian Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 1:41:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id ADF3014BF4 for ; Mon, 8 Mar 1999 01:41:14 -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 BAA06778; Mon, 8 Mar 1999 01:40:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903080940.BAA06778@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer Cc: Alex Zepeda , Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-reply-to: Your message of "Mon, 08 Mar 1999 00:48:12 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 01:40:37 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MIMENCODE(1) MIMENCODE(1) NAME mimencode - Translate to and from mail-oriented encoding formats (Same program also installed as "mmencode".) This is not a new program and it has been around for a while . Enjoy, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 2:18: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.indigo.ie (relay02.indigo.ie [194.125.133.226]) by hub.freebsd.org (Postfix) with SMTP id DD7D614D8B for ; Mon, 8 Mar 1999 02:17:59 -0800 (PST) (envelope-from nsmart@kira.team400.ie) Received: (qmail 6577 messnum 46530 invoked from network[194.125.134.175/ts02-045.dublin.indigo.ie]); 8 Mar 1999 10:17:40 -0000 Received: from ts02-045.dublin.indigo.ie (HELO kira.team400.ie) (194.125.134.175) by relay02.indigo.ie (qp 6577) with SMTP; 8 Mar 1999 10:17:40 -0000 Message-ID: <36E3A450.2ABBFD0E@kira.team400.ie> Date: Mon, 08 Mar 1999 10:20:00 +0000 From: Niall Smart Organization: Trinity Commerce X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: alk@pobox.com Cc: robert@kudra.com, freebsd-hackers@freebsd.org Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The base system has expanded. DHCP is one recent example. > In the modern world, a system without DHCP is much less generally > useful than one with DHCP. MIME should be another functional > adaptation to the modern environment. Uu-coding can go. (Well, > not yet, but before I die.) > > : Thats why we have the ports tree. If we switched to > : elm for instance, that would be a wasted megabye of disk for me, and > : many other people. Can you say 'Creeping Featureism?' > > Like DHCP. Or C++. Creeping Featurism? I don't think so. > But it would be better to be able to trivially configure a system > without DHCP, or C++, or MIME, I agree. What about the maintanence cost of importing DHCP and a decent C++ compiler into the base tree? There is no point of integrating them without a maintainer who keeps the package in sync with the "vendor sources" in a reasonably timely manner.  IMHO the ports provide the best compromise to cater for per-site customisation without the hassle of maintanence and "lively discussions" over what constitutes a base system. Thats not to say the definition isn't up for debate, but when in doubt "make -f /usr/ports/net/isc-dhcp/Makefile all install" seems best to me. Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 2:52:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 1CB5914DF4 for ; Mon, 8 Mar 1999 02:52:44 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id LAA28655; Mon, 8 Mar 1999 11:55:07 +0100 (MET) Date: Mon, 8 Mar 1999 11:53:19 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Amancio Hasty Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-Reply-To: <199903080603.WAA05855@rah.star-gate.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 Compile in USB mouse support. ums Keyboard support will be added soon. Watch freebsd-current. If you do not receive that mailing list, wait a week and ask again. Nick > Now how about mouse support, whats needed?. > > Got a Macally USB mouse and want to give a whirl. > > Tnks! > Amancio > > > > > > Oops, now after Kevin's suggestion of tweaking the sytstem BIOS to assigning > > > an IRQ to > > > the USB controller I cant use the keyboard on my new system. > > > > > > Every time that I type , I get : > > > > > > . (28) pressed 40 > > > . (30) pressed 4 > > > . > > > . > > > . > > > It looks like the USB device driver is stucked in echoing debug messages. > > > > Ah, you have a USB keyboard, and it's not in AT emulation mode anymore. > > > > We don't support USB keyboards yet... > > -- > > \\ 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 2:53:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 679A214BE1 for ; Mon, 8 Mar 1999 02:53:46 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elpc36.jrc.it (elpc36.jrc.it [139.191.71.36]) by mrelay.jrc.it (LMC5692) with SMTP id LAA28726; Mon, 8 Mar 1999 11:55:54 +0100 (MET) Date: Mon, 8 Mar 1999 11:54:06 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@elpc36.jrc.it Reply-To: Nick Hibma To: Mike Smith Cc: Amancio Hasty , freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-Reply-To: <199903080644.WAA05254@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 Mouse support is fully working already. Apart from crashes on UHCI controllers that is. But that is being solved at the moment. Nick > > Now how about mouse support, whats needed?. > > > > Got a Macally USB mouse and want to give a whirl. > > Go for it. Talk to Nick Hibma (n_hibma@freebsd.org) if you have any > problems. > -- > \\ 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 3: 2:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id BE6BE14EB1 for ; Mon, 8 Mar 1999 03:02:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id DAA07139; Mon, 8 Mar 1999 03:01:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903081101.DAA07139@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: usb irq 255?? In-reply-to: Your message of "Mon, 08 Mar 1999 11:54:06 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 03:01:36 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I added the option -DDIAGNOSTICS and recompile all of the USB files. I was getting a crash in : uhci.c: uhci_check_intr ->usb_untimeout . Without the above define I get an instant crash every time that I try to access ums0. I will keep digging. Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 4:25:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 791B614E5E for ; Mon, 8 Mar 1999 04:25:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA05672; Mon, 8 Mar 1999 21:25:26 +0900 (JST) Message-ID: <36E3BDAD.D23D5E5B@newsguy.com> Date: Mon, 08 Mar 1999 21:08:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Alex Zepeda Cc: Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > On Sun, 7 Mar 1999, Nate Williams wrote: > > > Ahh, but that doesn't work well if you have multiple attachments (been > > there, done that). > > Perhaps this should serve as an incentive for those who would like a MIME > capable reader in the base distribution to work on some commandline MIME > tools. I for one would object less to a few command line tools to handle > MIME "streams" than to a full featured mail client in the base distrib. metamail. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 4:27:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id D6DFB14E56 for ; Mon, 8 Mar 1999 04:25:43 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id VAA05652; Mon, 8 Mar 1999 21:25:22 +0900 (JST) Message-ID: <36E3BD67.AA51513F@newsguy.com> Date: Mon, 08 Mar 1999 21:07:03 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Nate Williams Cc: alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 References: <14048.10089.598598.919239@avalon.east> <36E07AEC.101F3467@newsguy.com> <14048.48864.918087.631128@avalon.east> <19990306095927.B53145@kudra.com> <14049.29637.311448.247778@avalon.east> <199903080209.TAA28284@mt.sri.com> <14051.24548.250885.992678@avalon.east> <199903080600.XAA28637@mt.sri.com> <14051.26618.409741.264371@avalon.east> <199903080609.XAA28680@mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > > > : > : Finally, there is *NO* way to distribute a standard MIME client that > > : > : will not add bloat. > > : > > > : > mpack/munpack. > > : > > : How can they be integrated with bin/mail, which is the standard unix > > : mail reader? > > > > Similarly to uuencode/uudecode: ~|command > > Ahh, but that doesn't work well if you have multiple attachments (been > there, done that). My old email client (not /bin/mail) did not handle > attachments, and I struggled along with the MIME stuff from Bell labs, > and they finally gave up and installed a MIME capable reader. > > However, I rarely have use for them anymore on FreeBSD, since the only > non-text files ever sent around are Word documents (with the appropriate > version of the Word Virus sprinkled in). Since I don't have word, I > have very little use for the attachments. :) We could replace our /bin/mail with the one supplied with metamail. IMHO, that would be bloat. No one who reads mail on a regular basis use /bin/mail. Unless they are reading root's log mail. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 4:57:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 7A0AA14E88 for ; Mon, 8 Mar 1999 04:57:28 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 08 Mar 1999 12:52:13 +0000 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id FSG3LFQ8; Mon, 8 Mar 1999 12:46:10 -0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10JzYg-0000BK-00; Mon, 8 Mar 1999 12:54:58 +0000 To: "Daniel C. Sobral" Cc: Alex Zepeda , Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: "Daniel C. Sobral"'s message of "Mon, 08 Mar 1999 21:08:13 +0900" <36E3BDAD.D23D5E5B@newsguy.com> Date: Mon, 08 Mar 1999 12:54:58 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 March 1999, "Daniel C. Sobral" proclaimed: > metamail. No. Not unless you want to rewrite all of metamail's scripts in bourne syntax. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Anybody who can paint a fence Tinky-Winky purple is alright in my book." -- LLB -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 5: 3: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 96D5114BE1 for ; Mon, 8 Mar 1999 05:03:06 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id IAA14508; Mon, 8 Mar 1999 08:02:25 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA01209; Mon, 8 Mar 1999 08:02:20 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id IAA05232; Mon, 8 Mar 1999 08:02:20 -0500 (EST) Date: Mon, 8 Mar 1999 08:02:20 -0500 (EST) From: Thomas David Rivers Message-Id: <199903081302.IAA05232@lakes.dignus.com> To: dcs@newsguy.com, nate@mt.sri.com Subject: Re: base64 Cc: alk@pobox.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <36E3BD67.AA51513F@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel C. Sobral wrote: > > We could replace our /bin/mail with the one supplied with metamail. > > IMHO, that would be bloat. No one who reads mail on a regular basis > use /bin/mail. Unless they are reading root's log mail. > I'd have to disagree - as someone who uses /bin/mail exclusively for reading mail. And, I get a *lot* of mail a day, several hundred messages on a slow day... Nothing works better for me than good ol' /bin/mail. (Of course, I take it you mean /usr/bin/mail on FreeBSD - there isn't a /bin/mail.) - 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 Mar 8 5: 8:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1E69314EDD for ; Mon, 8 Mar 1999 05:07:48 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10Jzki-000Lih-00 for freebsd-hackers@FreeBSD.ORG; Mon, 8 Mar 1999 15:07:24 +0200 From: Sheldon Hearn To: freebsd-hackers@FreeBSD.ORG Subject: Re: base64 Date: Mon, 08 Mar 1999 15:07:24 +0200 Message-ID: <83494.920898444@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Shush. This is yet another stupid thread born out of too much free time and a whining resentment about having to install a port on every machine one sets up. We've had this with shells, pagers, MTA's and who knows what else and the outcome is always the same. Save us all the hard-on and customize your own source tree as you see fit. Here's the crux in 2 lines, people: *************** We'll never have the majority of folk using the base mail reader, but we do need _something_. So let's keep it simple and ubiquitous. *************** Think before you reply. Shush if you have nothing new and useful to add. Ciao, Sheldon (EgoBSD-hater). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 5:44:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id BA7B814E30 for ; Mon, 8 Mar 1999 05:44:51 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id CAA14734; Tue, 9 Mar 1999 02:44:30 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.2/8.9.1) id CAA95937; Tue, 9 Mar 1999 02:44:29 +1300 (NZDT) (envelope-from jabley) Date: Tue, 9 Mar 1999 02:44:29 +1300 From: Joe Abley To: Dom Mitchell Cc: "Daniel C. Sobral" , Alex Zepeda , Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: base64 Message-ID: <19990309024429.A95913@clear.co.nz> References: <36E3BDAD.D23D5E5B@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dom Mitchell on Mon, Mar 08, 1999 at 12:54:58PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 08, 1999 at 12:54:58PM +0000, Dom Mitchell wrote: > On 8 March 1999, "Daniel C. Sobral" proclaimed: > > metamail. > > No. Not unless you want to rewrite all of metamail's scripts in bourne > syntax. I smell a religious issue, but what the hell... ... what's wrong with csh? We have csh in the tree. It's in the root filesystem. Although I have certainly written bourne scripts galore, I tend to write ad-hoc scripts in csh because that's what I use as my shell, and hence that's what any interactive scripts are written in. What's so great about sh? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 5:53:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id 203DC14EC3 for ; Mon, 8 Mar 1999 05:53:29 -0800 (PST) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Mon, 08 Mar 1999 13:53:09 +0000 Received: from voodoo.pandhm.co.uk ([10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id FSG3LFSC; Mon, 8 Mar 1999 13:47:07 -0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 10K0Vf-0000GB-00; Mon, 8 Mar 1999 13:55:55 +0000 To: Joe Abley Cc: "Daniel C. Sobral" , Alex Zepeda , Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG Subject: Re: base64 X-Mailer: nmh-1.0 X-Colour: Green Organization: Palmer & Harvey McLane In-Reply-To: Joe Abley's message of "Tue, 09 Mar 1999 02:44:29 +1300" <19990309024429.A95913@clear.co.nz> Date: Mon, 08 Mar 1999 13:55:54 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 March 1999, Joe Abley proclaimed: > On Mon, Mar 08, 1999 at 12:54:58PM +0000, Dom Mitchell wrote: > > On 8 March 1999, "Daniel C. Sobral" proclaimed: > > > metamail. > > > > No. Not unless you want to rewrite all of metamail's scripts in bourne > > syntax. > > I smell a religious issue, but what the hell... > > ... what's wrong with csh? We have csh in the tree. It's in the root > filesystem. Although I have certainly written bourne scripts galore, > I tend to write ad-hoc scripts in csh because that's what I use as > my shell, and hence that's what any interactive scripts are written > in. What's so great about sh? http://language.perl.com/versus/csh.whynot -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator "Anybody who can paint a fence Tinky-Winky purple is alright in my book." -- LLB -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 5:54:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (Postfix) with ESMTP id 1447214EF4 for ; Mon, 8 Mar 1999 05:54:33 -0800 (PST) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by samizdat.uucom.com (8.9.1/8.9.0) id IAA14568; Mon, 8 Mar 1999 08:54:46 -0500 To: Chris Shenton Cc: hackers@FreeBSD.ORG Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs References: <877lsslou8.fsf@absinthe.shenton.org> From: Chris Shenton Date: 08 Mar 1999 08:54:45 -0500 In-Reply-To: Chris Shenton's message of 07 Mar 1999 21:03:43 -0500 Message-ID: <86hfrwnl22.fsf@samizdat.uucom.com> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, should have provided details on the drive; dmesg says: ahc0: rev 0x03 int a irq 9 on pci0.8.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers da0 at ahc0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 8682MB (17781964 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 5.681MB/s transfers (5.681MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 5:58:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kyrnet.kg (ns.kyrnet.kg [195.254.160.9]) by hub.freebsd.org (Postfix) with ESMTP id 8E6EC14EDD for ; Mon, 8 Mar 1999 05:58:12 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from localhost by kyrnet.kg (8.9.3/8.9.1) with ESMTP id SAA20878 for ; Mon, 8 Mar 1999 18:52:02 +0500 (GMT) X-Authentication-Warning: kyrnet.kg: fygrave owned process doing -bs Date: Mon, 8 Mar 1999 18:52:01 +0500 (GMT) From: CyberPsychotic X-Sender: fygrave@kyrnet.kg To: freebsd-hackers@freebsd.org Subject: SOCK_RAW on BSD 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, here I've been playing with RAW sockets on FreeBSD and got stumbled abit. Any ideas why code bellow does't seem to get anything passed by kernel. (I read manual pages and /sys/netinet/raw_ip.c but neither place mention any incompatibilies with other systems. This piece would work fine on Linux platforms). #include #include #include #include #include #include void main(void) { char buf[10000]; int s,rdln; s=socket(AF_INET, SOCK_RAW, IPPROTO_RAW); while(1) { rdln=read(s, buf, 9999); printf("got pack len: %i\n",rdln); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 7: 7:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat196.27.mpoweredpc.net [142.177.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 10ECE14E19 for ; Mon, 8 Mar 1999 07:07:15 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA77070; Mon, 8 Mar 1999 11:06:56 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 8 Mar 1999 11:06:56 -0400 (AST) From: The Hermit Hacker To: Duane Currie Cc: freebsd-hackers@freebsd.org Subject: Re: GGI 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 Again, questions I can't answer... One thing that I'm curious about...somewhere along the way, I read that the 3D stuff was 'kernel based'...basically, you needed kernel drivers to make use o fthe 3D acceleration features of the various cards ... is this not accurate? On Mon, 8 Mar 1999, Duane Currie wrote: > > FreeBSD supports it? kewl. > Is that through emulation or a port? > > Oh, actually another question: Do you support the card as a device so > non-root users can use it without making programs setuid? > > Duane > > > On Mon, 8 Mar 1999, The Hermit Hacker wrote: > > > On Sun, 7 Mar 1999, Mike Smith wrote: > > > > > > A friend just picked himself up a Voodoo2 card that Linux now supports and > > > > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > > > > down my throat :( My card is *supposedly* faster then what he has, from > > > > comparing specs...be great if I can slam it back down his throat :) > > > > > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > > > see how "supporting" this card actually achieves anything. > > > > > > If he's talking about GLIDE, you might mention that we support the > > > Linux GLIDE library... > > > > Well, let me CC him in...I don't follow Linux too closely, so don't feel > > that I can adequately comment on this... > > > > Marc G. Fournier > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > > > 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 Mon Mar 8 7:15:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hub.org (hub.org [209.47.145.100]) by hub.freebsd.org (Postfix) with ESMTP id D6EF614DDB for ; Mon, 8 Mar 1999 07:15:28 -0800 (PST) (envelope-from sandman@hub.org) Received: from localhost (sandman@localhost) by hub.org (8.9.2/8.9.1) with ESMTP id KAA88184; Mon, 8 Mar 1999 10:15:10 -0500 (EST) (envelope-from sandman@hub.org) Date: Mon, 8 Mar 1999 10:15:09 -0500 (EST) From: Duane Currie To: The Hermit Hacker Cc: freebsd-hackers@freebsd.org Subject: Re: GGI 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 Not quite... You can run it without any kernel support, but the 3dfx executables would then have to be run with root privileges. There is a kernel driver that executes the necessary code in privileged mode, but the program itself can be run by any user. So, basically, to run the programs in user-land, you have to use the device driver. GGI seems to take a similar approach, but they might require kgi (the kernel part of the interface) and not allow it to be done otherwise. It all comes down to the fact that hardware operations generally have to be done with privileged access, either as root or in the kernel. The kernel is the better option mainly due to the fact that it allows access by any user. As usual, correct me if I'm wrong on any of this... Duane On Mon, 8 Mar 1999, The Hermit Hacker wrote: > > Again, questions I can't answer... > > One thing that I'm curious about...somewhere along the way, I read that > the 3D stuff was 'kernel based'...basically, you needed kernel drivers to > make use o fthe 3D acceleration features of the various cards ... is this > not accurate? > > On Mon, 8 Mar 1999, Duane Currie wrote: > > > > > FreeBSD supports it? kewl. > > Is that through emulation or a port? > > > > Oh, actually another question: Do you support the card as a device so > > non-root users can use it without making programs setuid? > > > > Duane > > > > > > On Mon, 8 Mar 1999, The Hermit Hacker wrote: > > > > > On Sun, 7 Mar 1999, Mike Smith wrote: > > > > > > > > A friend just picked himself up a Voodoo2 card that Linux now supports and > > > > > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > > > > > down my throat :( My card is *supposedly* faster then what he has, from > > > > > comparing specs...be great if I can slam it back down his throat :) > > > > > > > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > > > > see how "supporting" this card actually achieves anything. > > > > > > > > If he's talking about GLIDE, you might mention that we support the > > > > Linux GLIDE library... > > > > > > Well, let me CC him in...I don't follow Linux too closely, so don't feel > > > that I can adequately comment on this... > > > > > > Marc G. Fournier > > > Systems Administrator @ hub.org > > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > > > > > > > > > > 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 Mon Mar 8 7:17:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 88BBD14EED for ; Mon, 8 Mar 1999 07:17:40 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id KAA00540 for ; Mon, 8 Mar 1999 10:17:21 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id KAA00329 for ; Mon, 8 Mar 1999 10:17:19 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id KAA09942 for freebsd-hackers@freebsd.org; Mon, 8 Mar 1999 10:17:19 -0500 (EST) Date: Mon, 8 Mar 1999 10:17:19 -0500 (EST) From: Thomas David Rivers Message-Id: <199903081517.KAA09942@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: "scratchiness" in 3.1 pcm? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using "Luigi's" driver in 3.1-RELEASE, and notice a lot of pops and scratches, etc.. when a JAVA program writes to pcm (i.e. AOL Instant Messenger.) The relevant pieces of my dmesg output: Probing for PnP devices: CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x001c4a17 Comp ID: PNP0600 [0x0006d041] pcm1 (SB16pnp sn 0x001c4a17) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa (i.e. a sound blaster PnP card.) In noticed some pops and clicks in 3.0 but it seems to have gotten worse in 3.1... any thoughts? - 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 Mar 8 7:28:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 7DBD214F04 for ; Mon, 8 Mar 1999 07:28:52 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id EAA19477; Tue, 9 Mar 1999 04:28:31 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.2/8.9.1) id EAA46557; Tue, 9 Mar 1999 04:28:30 +1300 (NZDT) (envelope-from jabley) Date: Tue, 9 Mar 1999 04:28:30 +1300 From: Joe Abley To: Dom Mitchell Cc: "Daniel C. Sobral" , Alex Zepeda , Nate Williams , alk@pobox.com, freebsd-hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: base64 Message-ID: <19990309042830.A35854@clear.co.nz> References: <19990309024429.A95913@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Dom Mitchell on Mon, Mar 08, 1999 at 01:55:54PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 08, 1999 at 01:55:54PM +0000, Dom Mitchell wrote: > > http://language.perl.com/versus/csh.whynot Oh. Ok then :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 7:38:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (ip161.houston3.tx.pub-ip.psi.net [38.12.169.161]) by hub.freebsd.org (Postfix) with ESMTP id 5FC7714C15 for ; Mon, 8 Mar 1999 07:38:12 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id JAA95871; Mon, 8 Mar 1999 09:38:36 -0600 (CST) (envelope-from chris) Date: Mon, 8 Mar 1999 09:38:35 -0600 From: Chris Costello To: CyberPsychotic Cc: freebsd-hackers@freebsd.org Subject: Re: SOCK_RAW on BSD Message-ID: <19990308093835.B93344@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3us In-Reply-To: ; from CyberPsychotic on Mon, Mar 08, 1999 at 06:52:01PM +0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 8, 1999, CyberPsychotic put this into my mailbox: > Hello people, > here I've been playing with RAW sockets on FreeBSD and got stumbled abit. > Any ideas why code bellow does't seem to get anything passed by kernel. > (I read manual pages and /sys/netinet/raw_ip.c but neither place mention any > incompatibilies with other systems. This piece would work fine on Linux > platforms). See below: > > > #include > #include > #include > #include > #include > #include > > > > > void main(void) { > > char buf[10000]; > int s,rdln; > s=socket(AF_INET, SOCK_RAW, IPPROTO_RAW); > while(1) > { > rdln=read(s, buf, 9999); > printf("got pack len: %i\n",rdln); if (rdln < 0) perror("read"); > } > } Did you run this as the super-user? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!" Every program in development at MIT expands until it can read mail. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 7:51:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 15FD714C15 for ; Mon, 8 Mar 1999 07:51:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id HAA12943; Mon, 8 Mar 1999 07:50:26 -0800 Date: Mon, 8 Mar 1999 07:50:26 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Chris Shenton Cc: Chris Shenton , hackers@FreeBSD.ORG Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs In-Reply-To: <86hfrwnl22.fsf@samizdat.uucom.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 What errors? And what 'does not honor'? I know that Tom Torrance claimed this happened- which I can't reproduce. On 8 Mar 1999, Chris Shenton wrote: > Oops, should have provided details on the drive; dmesg says: > > ahc0: rev 0x03 int a irq 9 on pci0.8.0 > ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs > > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > > da0 at ahc0 bus 0 target 3 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 8682MB (17781964 512 byte sectors: 255H 63S/T 1106C) > changing root device to da0s1a > > cd0 at ahc0 bus 0 target 2 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 5.681MB/s transfers (5.681MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 8:57:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id E327E14F04 for ; Mon, 8 Mar 1999 08:57:27 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA13047; Mon, 8 Mar 1999 11:59:26 -0500 (EST) Date: Mon, 8 Mar 1999 11:59:24 -0500 (EST) From: Alfred Perlstein To: CyberPsychotic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SOCK_RAW on BSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Mar 1999, CyberPsychotic wrote: > Hello people, > here I've been playing with RAW sockets on FreeBSD and got stumbled abit. > Any ideas why code bellow does't seem to get anything passed by kernel. > (I read manual pages and /sys/netinet/raw_ip.c but neither place mention any > incompatibilies with other systems. This piece would work fine on Linux > platforms). If you are trying to capture packets you should look at 'bpf', if you are trying to capture packets in a portable fashion, look at the library 'pcap' -Alfred man bpf man pcap > > > #include > #include > #include > #include > #include > #include > > > > > void main(void) { > > char buf[10000]; > int s,rdln; > s=socket(AF_INET, SOCK_RAW, IPPROTO_RAW); > while(1) > { > rdln=read(s, buf, 9999); > printf("got pack len: %i\n",rdln); > } > } > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 9:11:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106]) by hub.freebsd.org (Postfix) with ESMTP id C185514EC6 for ; Mon, 8 Mar 1999 09:11:07 -0800 (PST) (envelope-from gurudatt@cs.tamu.edu) Received: from dilbert.cs.tamu.edu (IDENT:2146@dilbert [128.194.133.100]) by cs.tamu.edu (8.9.1/8.9.1) with ESMTP id LAA15714 for ; Mon, 8 Mar 1999 11:10:12 -0600 (CST) Received: from localhost by dilbert.cs.tamu.edu (8.9.1/8.9.1) with SMTP id LAA11167 for ; Mon, 8 Mar 1999 11:08:43 -0600 (CST) X-Authentication-Warning: dilbert.cs.tamu.edu: gurudatt owned process doing -bs Date: Mon, 8 Mar 1999 11:08:43 -0600 (CST) From: Gurudatt Shenoy X-Sender: gurudatt@dilbert To: FreeBSD Hackers Subject: Repeated reboots. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, Some time back I had posted this problem I had when I added some stuff to the kernel. I suppose I had not been specific enough (I never got any solution to my problem). Here's a better description. Hope one of you knows what's happening: this thing has been a kinda show-stopper for my work: I added 2 microtime() calls to the kernel: One in /sys/net in the file if_ethersubr.c in the function ether_output. : Additional routing options: routed clntudp_create: out of memory clntudp_create: out of memory (null) Fatal Trap 12: PAge fault while in kernel mode. : : : panic: page fault syncing disks... Automatic reboot in 15 seconds... *ANY* help will be very much appreciated. I commented out the two microtime calls I made and I had no problems compiling and running the new kernel. Thanks in advance, Guru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 9:36:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles302.castles.com [208.214.167.2]) by hub.freebsd.org (Postfix) with ESMTP id 4071814EAD for ; Mon, 8 Mar 1999 09:36:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA06930; Mon, 8 Mar 1999 09:31:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903081731.JAA06930@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: CyberPsychotic Cc: freebsd-hackers@freebsd.org Subject: Re: SOCK_RAW on BSD In-reply-to: Your message of "Mon, 08 Mar 1999 18:52:01 +0500." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 09:31:06 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello people, > here I've been playing with RAW sockets on FreeBSD and got stumbled abit. > Any ideas why code bellow does't seem to get anything passed by kernel. > (I read manual pages and /sys/netinet/raw_ip.c but neither place mention any > incompatibilies with other systems. This piece would work fine on Linux > platforms). There is no mention ofincompatabilities with other systems because there are none; the BSD stack is the reference implementation with which all other implementations are compatible or incompatible. In this case, you are being tripped up by the bogus way that Linux does packet capture. To achieve your goals in a portable fashion, you should use a portable packet capture library like libpcap. As for using code from a Linux utility like tcplog - now you know why the rest of the world laughs at Linux - when there's a way to do it hard or wrong or just plain weird, they'll do it. > > #include > #include > #include > #include > #include > #include > > > > > void main(void) { > > char buf[10000]; > int s,rdln; > s=socket(AF_INET, SOCK_RAW, IPPROTO_RAW); > while(1) > { > rdln=read(s, buf, 9999); > printf("got pack len: %i\n",rdln); > } > } > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 9:41:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orbit.flnet.com (orbit.flnet.com [205.240.232.32]) by hub.freebsd.org (Postfix) with ESMTP id 25B7914EEE; Mon, 8 Mar 1999 09:41:33 -0800 (PST) (envelope-from henrich@orbit.flnet.com) Received: (from henrich@localhost) by orbit.flnet.com (8.8.5/8.8.4) id MAA09237; Mon, 8 Mar 1999 12:41:01 -0500 (EST) Message-ID: <19990308094100.14836@orbit.flnet.com> Date: Mon, 8 Mar 1999 09:41:00 -0800 From: Charles Henrich To: Mike Smith Cc: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed Mail-Followup-To: Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org References: <19990308005125.10555@orbit.flnet.com> <199903080911.BAA05661@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199903080911.BAA05661@dingo.cdrom.com>; from Mike Smith on Mon, Mar 08, 1999 at 01:11:30AM -0800 X-Operating-System: FreeBSD 2.2-BETA_A X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the subject of Re: Erorr: isa_dmainit(2, 1024) failed, Mike Smith stated: > > During startup on my FreeBSD box (a dual proc 1GB system) I see: > > > > isa_dmainit(2, 1024) failed > > > > And (perhaps) coincidentally any access to the ISA sound card causes the > > machine to panic with an isa page map missing. Does anyone out there have > > any ideas whats causing this, and what a solution might be? Thanks! > > You have too much memory. 8) > > Seriously, by the time the ISA code gets a chance to allocate memory, all > the physically dma-able-to memory is gone for other uses. > > This is basically a bug in the way kernel memory is handed out. How does one fix this? :) -Crh Charles Henrich Manex Visual Effects henrich@flnet.com http://orbit.flnet.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 9:46:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles302.castles.com [208.214.167.2]) by hub.freebsd.org (Postfix) with ESMTP id CABBD14EF8; Mon, 8 Mar 1999 09:46:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA06967; Mon, 8 Mar 1999 09:40:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903081740.JAA06967@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Charles Henrich Cc: Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed In-reply-to: Your message of "Mon, 08 Mar 1999 09:41:00 PST." <19990308094100.14836@orbit.flnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 09:40:28 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On the subject of Re: Erorr: isa_dmainit(2, 1024) failed, Mike Smith stated: > > > > During startup on my FreeBSD box (a dual proc 1GB system) I see: > > > > > > isa_dmainit(2, 1024) failed > > > > > > And (perhaps) coincidentally any access to the ISA sound card causes the > > > machine to panic with an isa page map missing. Does anyone out there have > > > any ideas whats causing this, and what a solution might be? Thanks! > > > > You have too much memory. 8) > > > > Seriously, by the time the ISA code gets a chance to allocate memory, all > > the physically dma-able-to memory is gone for other uses. > > > > This is basically a bug in the way kernel memory is handed out. > > How does one fix this? :) With a text editor. Find the code that does it wrong, change it and recompile. Send us the diffs when you're done. Actually, fixing it "right" will be very difficult. I suspect that the ISA DMA code will need a statically-allocated buffer to overcome this. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 10:11:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orbit.flnet.com (orbit.flnet.com [205.240.232.32]) by hub.freebsd.org (Postfix) with ESMTP id 5715D14BE0; Mon, 8 Mar 1999 10:11:23 -0800 (PST) (envelope-from henrich@orbit.flnet.com) Received: (from henrich@localhost) by orbit.flnet.com (8.8.5/8.8.4) id NAA09977; Mon, 8 Mar 1999 13:10:59 -0500 (EST) Message-ID: <19990308101059.50251@orbit.flnet.com> Date: Mon, 8 Mar 1999 10:10:59 -0800 From: Charles Henrich To: Mike Smith Cc: freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed Mail-Followup-To: Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org References: <19990308094100.14836@orbit.flnet.com> <199903081740.JAA06967@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199903081740.JAA06967@dingo.cdrom.com>; from Mike Smith on Mon, Mar 08, 1999 at 09:40:28AM -0800 X-Operating-System: FreeBSD 2.2-BETA_A X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the subject of Re: Erorr: isa_dmainit(2, 1024) failed, Mike Smith stated: > With a text editor. Find the code that does it wrong, change it and > recompile. Send us the diffs when you're done. Smartass :) > Actually, fixing it "right" will be very difficult. I suspect that the ISA > DMA code will need a statically-allocated buffer to overcome this. Ah, that makes sense. I shall look into this. -Crh Charles Henrich Manex Visual Effects henrich@flnet.com http://orbit.flnet.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 10:28:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id D260814F26; Mon, 8 Mar 1999 10:28:45 -0800 (PST) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.1/8.9.1) with ESMTP id TAA70476; Mon, 8 Mar 1999 19:27:59 +0100 (CET) Message-Id: <199903081827.TAA70476@midten.fast.no> To: mike@smith.net.au Cc: henrich@flnet.com, freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Erorr: isa_dmainit(2, 1024) failed From: Tor.Egge@fast.no In-Reply-To: Your message of "Mon, 08 Mar 1999 09:40:28 -0800" References: <199903081740.JAA06967@dingo.cdrom.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Mar__8_19:22:22_1999)--" Content-Transfer-Encoding: 7bit Date: Mon, 08 Mar 1999 19:27:59 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Mon_Mar__8_19:22:22_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > How does one fix this? :) > > With a text editor. Find the code that does it wrong, change it and > recompile. Send us the diffs when you're done. > > Actually, fixing it "right" will be very difficult. I suspect that the > ISA DMA code will need a statically-allocated buffer to overcome this. I've been using the appended patch to use SoundBlaster AWE64 Gold on a machine with 512 MB memory. - Tor Egge ----Next_Part(Mon_Mar__8_19:22:22_1999)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Index: sys/i386/include/pmap.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v retrieving revision 1.58 diff -u -r1.58 pmap.h --- pmap.h 1999/03/02 16:20:39 1.58 +++ pmap.h 1999/03/03 15:24:59 @@ -265,6 +285,7 @@ void putfmtrr __P((void)); void pmap_setdevram __P((unsigned long long, unsigned)); void pmap_setvidram __P((void)); +int pmap_defer_avail __P((vm_offset_t)); #endif /* KERNEL */ Index: sys/i386/i386/pmap.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v retrieving revision 1.223 diff -u -r1.223 pmap.c --- pmap.c 1999/02/19 14:25:33 1.223 +++ pmap.c 1999/02/26 04:25:22 @@ -71,6 +71,7 @@ #include "opt_disable_pse.h" #include "opt_pmap.h" #include "opt_msgbuf.h" +#include "isa.h" #include #include @@ -3411,6 +3623,16 @@ return val; } +int +pmap_defer_avail(vm_offset_t pa) +{ +#if NISA > 0 + if (pa >= 0x0 && pa < 0x1000000) + return 1; +#endif + return 0; +} + void pmap_activate(struct proc *p) { Index: sys/i386/i386/machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.326 diff -u -r1.326 machdep.c --- machdep.c 1999/02/13 17:45:15 1.326 +++ machdep.c 1999/02/18 15:20:53 @@ -1544,7 +1545,9 @@ * so that we keep going. The first bad page * will terminate the loop. */ - if (phys_avail[pa_indx] == target_page) { + if (phys_avail[pa_indx] == target_page && + pmap_defer_avail(target_page) == + pmap_defer_avail(target_page - PAGE_SIZE)) { phys_avail[pa_indx] += PAGE_SIZE; if (speculative_mprobe == TRUE && phys_avail[pa_indx] >= (64*1024*1024)) Index: sys/vm/vm_page.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_page.c,v retrieving revision 1.127 diff -u -r1.127 vm_page.c --- vm_page.c 1999/02/24 21:26:26 1.127 +++ vm_page.c 1999/02/26 04:10:32 @@ -201,11 +203,13 @@ register vm_page_t m; register struct vm_page **bucket; vm_size_t npages, page_range; + vm_size_t tmpnpages; register vm_offset_t new_start; int i; vm_offset_t pa; int nblocks; vm_offset_t first_managed_page; + int pass; /* the biggest memory array is the second group of pages */ vm_offset_t start; @@ -324,22 +328,30 @@ cnt.v_page_count = 0; cnt.v_free_count = 0; - for (i = 0; phys_avail[i + 1] && npages > 0; i += 2) { - if (i == biggestone) - pa = ptoa(first_managed_page); - else - pa = phys_avail[i]; - while (pa < phys_avail[i + 1] && npages-- > 0) { - ++cnt.v_page_count; - ++cnt.v_free_count; - m = PHYS_TO_VM_PAGE(pa); - m->phys_addr = pa; - m->flags = 0; - m->pc = (pa >> PAGE_SHIFT) & PQ_L2_MASK; - m->queue = m->pc + PQ_FREE; - TAILQ_INSERT_TAIL(vm_page_queues[m->queue].pl, m, pageq); - ++(*vm_page_queues[m->queue].lcnt); - pa += PAGE_SIZE; + for (pass = 0; pass < 2; pass++) { + tmpnpages = npages; + for (i = 0; phys_avail[i + 1] && npages > 0; i += 2) { + if (i == biggestone) + pa = ptoa(first_managed_page); + else + pa = phys_avail[i]; + while (pa < phys_avail[i + 1] && tmpnpages-- > 0) { + if (pass != pmap_defer_avail(pa)) { + pa += PAGE_SIZE; + continue; + } + ++cnt.v_page_count; + ++cnt.v_free_count; + m = PHYS_TO_VM_PAGE(pa); + m->phys_addr = pa; + m->flags = 0; + m->pc = (pa >> PAGE_SHIFT) & PQ_L2_MASK; + m->queue = m->pc + PQ_FREE; + TAILQ_INSERT_TAIL(vm_page_queues[m->queue].pl, + m, pageq); + ++(*vm_page_queues[m->queue].lcnt); + pa += PAGE_SIZE; + } } } return (mapped); ----Next_Part(Mon_Mar__8_19:22:22_1999)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 10:33:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id D6BA214BDC; Mon, 8 Mar 1999 10:33:35 -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 KAA00878; Mon, 8 Mar 1999 10:32:28 -0800 (PST) Message-Id: <199903081832.KAA00878@lestat.nas.nasa.gov> To: The Hermit Hacker Cc: Mike Smith , "Daniel C. Sobral" , Terry Lambert , sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: GGI Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 08 Mar 1999 10:32:27 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Mar 1999 00:26:02 -0400 (AST) The Hermit Hacker wrote: > A friend just picked himself up a Voodoo2 card that Linux now supports and > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > down my throat :( My card is *supposedly* faster then what he has, from > comparing specs...be great if I can slam it back down his throat :) Why should FreeBSD (or NetBSD for that matter) have to care about the acceleration on the card? An operating system shoudl care about that only for if the console is a linear framebuffer, and you want scrolling to be Really Fast. (NetBSD's "wscons" console driver has hooks in the terminal emulation layer for using hardware acceleration, which we use on TURBOchannel "sfb" framebuffers, and soon on PCI TGA framebuffers.) For _everything_ else, it all belongs in userland. At this point, the OS's responsibility is to provide a reasonable set of device mapping primitives which allow source code portability across architectures. NetBSD's "wscons" has some (albiet not all, yet) of the hooks for this, as well as some other basic things to make it possible to implement naive graphics applications, such as get/set colormap, get/set hardware cursor shape, get/set hardware cursor position, etc. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 10:39: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id B4FEC14F43 for ; Mon, 8 Mar 1999 10:38:59 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10K4iQ-00055p-00; Mon, 8 Mar 1999 18:25:22 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10K4jU-000054-00; Mon, 8 Mar 1999 18:26:28 +0000 Date: Mon, 8 Mar 1999 18:26:28 +0000 (GMT) From: Andy Doran To: Vincent Fleming Cc: "'hackers@freebsd.org'" Subject: RE: samba performance In-Reply-To: <01BE6710.A0EEE120@rembrandt> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Very strange... but mounting the filesystems asynch has no effect. > > I'll have to look through the code to see if smbd is creating the files > with O_SYNC or something. I would think mounting the filesystems > async would make a difference. Hmm... I thought we had it there! > > Vince > This could be a network problem. Here, from mailhub, a FreeBSD box running 3.1 we get performance as high as is possible with 10Mb Ethernet when doing NFS. This drops to about 90kB/s when doing writes over TCP (ftp, Samba, etc). This is with a 3Com Etherlink XL. Go figure. Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 10:39:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id B6F8314F3B for ; Mon, 8 Mar 1999 10:39:24 -0800 (PST) (envelope-from ad@psn.ie) Received: from vmunix.psn.ie ([194.106.150.252]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 10K4uj-000567-00; Mon, 8 Mar 1999 18:38:05 +0000 Received: from localhost.psn.ie ([127.0.0.1] helo=localhost) by vmunix.psn.ie with esmtp (Exim 2.10 #1) id 10K4rO-00005F-00; Mon, 8 Mar 1999 18:34:38 +0000 Date: Mon, 8 Mar 1999 18:34:38 +0000 (GMT) From: Andy Doran To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed In-Reply-To: <199903081740.JAA06967@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 > Actually, fixing it "right" will be very difficult. I suspect that the > ISA DMA code will need a statically-allocated buffer to overcome this. > I've run into the same kind of problem when working on a driver for NetBSD recently. The solution would be to use NetBSD's BUS_DMA(9), but this card needs a DMA buffer which has *crazy* alignment and position requirements. One of them is that the buffer needs to be within the first 8MB, hence the same problem. The solution for me was to put in a call to steal the DMA buffer just after the VM system is up and before buffers get allocated (which doesn't happen in FreeBSD), so why not just use a solution like this? (I think in FreeBSD the right place would be init386()). Andy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 11:25:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Michelle.esfm.ipn.mx (Michelle.esfm.ipn.mx [148.204.104.23]) by hub.freebsd.org (Postfix) with ESMTP id C1B04152F5; Mon, 8 Mar 1999 11:25:03 -0800 (PST) (envelope-from mrspock@esfm.ipn.mx) Received: from localhost (mrspock@localhost) by Michelle.esfm.ipn.mx (8.9.1/8.9.1) with ESMTP id NAA10845; Mon, 8 Mar 1999 13:24:06 -0600 (CST) (envelope-from mrspock@esfm.ipn.mx) X-Authentication-Warning: Michelle.esfm.ipn.mx: mrspock owned process doing -bs Date: Mon, 8 Mar 1999 13:24:05 -0600 (CST) From: Eduardo Viruena Silva To: questions@freebsd.org Cc: hackers@freebsd.org Subject: starting partition 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 there! I think this is not a question but an observation... I have asked you about a problem that occurres when you install FreeBSD in two different PARTITIONS of the same IDE disk. It seems to me that FreeBSD does not let you do that, I mean, you cannot have version 2.2.8 and version 3.0 in the same disk because the installation process destroys one of the disk labels. (I made a question about it some weeks ago, they answered me that I have made a mess with my disk labels, so I repeated the experiment and it happened again... I installed version 2.2.8 in partition 1, and version 3.0 in partition 2. Patition 2 became a mess). Some other Unix versions (the old ultrix and osf/1) require three "coordinates" for specifying the kernel's position: the disk number, the patition number, and the slice letter. So, if you want to start from disk 2, patition 1, slice a, the loader should have to receive: wd(2,1,a)kernel and not: wd(2,a)kernel But this is not possbile in FreeBSD loader. I am not saying only non-sense, aren't I? Could you do something for correct this? Thank you in advance. Eduardo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 11:38:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (Postfix) with ESMTP id B8D7F153F2 for ; Mon, 8 Mar 1999 11:37:49 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA061549735; Mon, 8 Mar 1999 14:02:15 -0500 Date: Mon, 8 Mar 1999 14:02:15 -0500 (EST) From: Bill Fumerola To: Joe Abley Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-Reply-To: <19990309024429.A95913@clear.co.nz> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Mar 1999, Joe Abley wrote: > ... what's wrong with csh? We have csh in the tree. It's in the root > filesystem. Although I have certainly written bourne scripts galore, > I tend to write ad-hoc scripts in csh because that's what I use as > my shell, and hence that's what any interactive scripts are written > in. What's so great about sh? Prorgramming anything in csh(1) is a Bad Thing. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 12: 9:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id CE3D314FAC for ; Mon, 8 Mar 1999 12:09:31 -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 MAA02543; Mon, 8 Mar 1999 12:07:40 -0800 (PST) Message-Id: <199903082007.MAA02543@lestat.nas.nasa.gov> To: Andy Doran Cc: Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Erorr: isa_dmainit(2, 1024) failed Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 08 Mar 1999 12:07:39 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Mar 1999 18:34:38 +0000 (GMT) Andy Doran wrote: > I've run into the same kind of problem when working on a driver for > NetBSD recently. The solution would be to use NetBSD's BUS_DMA(9), but > this card needs a DMA buffer which has *crazy* alignment and position > requirements. One of them is that the buffer needs to be within the first > 8MB, hence the same problem. Well, your driver was for a non-i386 architecture :-) And, the suggestion I gave on port-pmax@netbsd.org is already employed by NetBSD/i386 to "reserve" memory for ISA DMA. That is to say, the Right solution for this is multiple memory free lists, which NetBSD's UVM has support for. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 12:30:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 9BAE815259; Mon, 8 Mar 1999 12:30:21 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id OAA23842; Mon, 8 Mar 1999 14:29:48 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id OAA00544; Mon, 8 Mar 1999 14:29:47 -0600 (CST) Date: Mon, 8 Mar 1999 14:29:47 -0600 From: Alan Cox To: Charles Henrich Cc: Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed Message-ID: <19990308142947.A471@nonpc.cs.rice.edu> References: <19990308094100.14836@orbit.flnet.com> <199903081740.JAA06967@dingo.cdrom.com> <19990308101059.50251@orbit.flnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990308101059.50251@orbit.flnet.com>; from Charles Henrich on Mon, Mar 08, 1999 at 10:10:59AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles, Please try the following simpler patch. It should accomplish the same thing as Tor's patch. Replace the TAILQ_INSERT_TAIL in vm_page_startup (in vm_page.c) with a TAILQ_INSERT_HEAD. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 12:32:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 73B3D15368 for ; Mon, 8 Mar 1999 12:32:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA60468; Mon, 8 Mar 1999 12:31:03 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: base64 In-reply-to: Your message of "Mon, 08 Mar 1999 15:07:24 +0200." <83494.920898444@axl.noc.iafrica.com> Date: Mon, 08 Mar 1999 12:31:03 -0800 Message-ID: <60464.920925063@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Shush. This is yet another stupid thread born out of too much free time > and a whining resentment about having to install a port on every machine > one sets up. Finally, a message in this thread that I can unreservedly agree with. I haven't seen anything so far which indicates that this whole idiotic thread on mail readers has advanced the state of the art in any way or done anything but give those who prefer their time dead a new way to kill it. Can we find something more productive to discuss in -hackers? I'm completely sick of this discussion, especially when we have so many more important things to worry about right now. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:18:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 4F7E415176 for ; Mon, 8 Mar 1999 13:18:46 -0800 (PST) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id QAA19899 for ; Mon, 8 Mar 1999 16:18:27 -0500 (EST) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20599; Mon, 8 Mar 1999 16:18:26 -0500 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.1/8.9.1) id QAA14724; Mon, 8 Mar 1999 16:18:25 -0500 (EST) (envelope-from brdean) From: Brian Dean Message-Id: <199903082118.QAA14724@dean.pc.sas.com> Subject: install using serial console? To: freebsd-hackers@freebsd.org Date: Mon, 8 Mar 1999 16:18:25 -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 Hi, I understand that FreeBSD supports the use of the serial port as a console device. I would like to take advantage of this feature, however, I still need to be able to do new installs on these same machines from time to time. Are serial consoles supported in some way for 'sysinstall'ing on a new machine without having to have a keyboard/monitor connected? Is this supported out of the box, or does it, perhaps, require a special kernel for the boot disk to be built-in during the make release process? Is anyone doing this? Any help/pointers are appreciated! Thanks, -Brian -- Brian Dean Process Engineering brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:52:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BE5AD14C15 for ; Mon, 8 Mar 1999 13:52:09 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id VAA52579; Mon, 8 Mar 1999 21:51:47 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA17787; Mon, 8 Mar 1999 14:52:05 -0700 (MST) Message-Id: <199903082152.OAA17787@harmony.village.org> To: Ladavac Marino Subject: Re: SCSI Tape (HP SureStore T20) trouble Cc: "'mjacob@feral.com'" , Josh MacDonald , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 01 Mar 1999 10:44:12 +0100." <97A8CA5BF490D211A94F0000F6C2E55D097550@s-lmh-wi-900.corpnet.at> References: <97A8CA5BF490D211A94F0000F6C2E55D097550@s-lmh-wi-900.corpnet.at> Date: Mon, 08 Mar 1999 14:52:05 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <97A8CA5BF490D211A94F0000F6C2E55D097550@s-lmh-wi-900.corpnet.at> Ladavac Marino writes: : [ML] Not necessarily. Might be a 3.0R sync negotiation bug, : because : I get the same rate for IBM DCASmumble hard disk hung off an : aha1542CF. : The disc and the card are fast SCSI devices, 10 MB/s should be : possible : (okay, I don't care much because ISA cannot trasfer more than : 2-3 MB/s : anyway :) I've seen this bug in the aha driver, but haven't tracked it down yet. It appears that most (all?) disks will default to this rate. I don't know if that is a bios issue, or a driver issue. I suspect the latter.... This is not a generic CAM bug. WArner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:52:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4EBFA15314 for ; Mon, 8 Mar 1999 13:52:52 -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.3/8.8.8) with ESMTP id NAA00580; Mon, 8 Mar 1999 13:47:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903082147.NAA00580@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Dean Cc: freebsd-hackers@freebsd.org Subject: Re: install using serial console? In-reply-to: Your message of "Mon, 08 Mar 1999 16:18:25 EST." <199903082118.QAA14724@dean.pc.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 13:47:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It should be supported out of the box; boot without a keyboard. If not, the fix should be simple; mount the install floppy and create a file 'boot.config' containing just '-h'. > I understand that FreeBSD supports the use of the serial port as a > console device. I would like to take advantage of this feature, > however, I still need to be able to do new installs on these same > machines from time to time. Are serial consoles supported in some way > for 'sysinstall'ing on a new machine without having to have a > keyboard/monitor connected? Is this supported out of the box, or does > it, perhaps, require a special kernel for the boot disk to be built-in > during the make release process? Is anyone doing this? > > Any help/pointers are appreciated! > > Thanks, > -Brian > -- > Brian Dean Process Engineering brdean@unx.sas.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:53:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-23-dbn.dial-up.net [196.34.155.87]) by hub.freebsd.org (Postfix) with ESMTP id 6DD9415321 for ; Mon, 8 Mar 1999 13:53:39 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA18690; Mon, 8 Mar 1999 23:51:49 +0200 (SAT) From: Robert Nordier Message-Id: <199903082151.XAA18690@ceia.nordier.com> Subject: Re: starting partition In-Reply-To: from Eduardo Viruena Silva at "Mar 8, 99 01:24:05 pm" To: mrspock@esfm.ipn.mx (Eduardo Viruena Silva) Date: Mon, 8 Mar 1999 23:03:46 +0200 (SAT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Status: RO Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cc'd to -hackers; bcc'd to -questions] Eduardo Viruena Silva wrote: > Hello there! > > I think this is not a question but an observation... > > I have asked you about a problem that occurres when you install FreeBSD in > two different PARTITIONS of the same IDE disk. It seems to me that > FreeBSD does not let you do that, I mean, you cannot have version 2.2.8 > and version 3.0 in the same disk because the installation process destroys > one of the disk labels. (I made a question about it some weeks ago, > they answered me that I have made a mess with my disk labels, so I > repeated the experiment and it happened again... I installed version 2.2.8 > in partition 1, and version 3.0 in partition 2. Patition 2 became a > mess). BTW: You seem to be using partitions and slices in the SVR4 sense, where "partition" is what you create with fdisk, and "slice" is a subdivision of a partition. FreeBSD uses these two terms in an exactly opposite sense (partitions go inside slices). Just to keep things confusing, I'll use the FreeBSD terminology below. :) I sometimes install up to four versions of FreeBSD on the same disk. However I would usually make it seem to sysinstall that no FreeBSD slices already exist, by changing the slice type from 0xa5 to something else (say 0x42 or 0x69) before each install. The reason for doing this is that support for multiple FreeBSD slices per disk is something of an "at own risk" option rather than a fully-recommended way of doing things. Once all the installation is done, the slices types can be changed back to 0xa5. > Some other Unix versions (the old ultrix and osf/1) require three > "coordinates" for specifying the kernel's position: the disk number, the > patition number, and the slice letter. > > So, if you want to start from disk 2, patition 1, slice a, > the loader should have to receive: > > wd(2,1,a)kernel > > and not: > wd(2,a)kernel > > But this is not possbile in FreeBSD loader. >From the 3.1 release (and a bit earlier in -stable), it is possible to specify wd(2,1,a)kernel at the "boot:" prompt. It is also possible to specify the slice at the /boot/loader prompt (the new /boot/loader being an added third stage to the bootstrap) using syntax like "disk2s1a". If you use a boot manager like BootEasy (or the FreeBSD boot0 workalike) which sets the selected slice as active, the new 3.1R boot code will automatically boot from the slice you select. So it should be as simple as pressing F1 or F2, say. You can use the 3.1R boot code to boot prior versions of FreeBSD. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:55:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 06BA715408 for ; Mon, 8 Mar 1999 13:55:21 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA14516; Mon, 8 Mar 1999 13:54:42 -0800 Date: Mon, 8 Mar 1999 13:54:42 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Warner Losh Cc: Ladavac Marino , Josh MacDonald , freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Tape (HP SureStore T20) trouble In-Reply-To: <199903082152.OAA17787@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Context? On Mon, 8 Mar 1999, Warner Losh wrote: > In message <97A8CA5BF490D211A94F0000F6C2E55D097550@s-lmh-wi-900.corpnet.at> Ladavac Marino writes: > : [ML] Not necessarily. Might be a 3.0R sync negotiation bug, > : because > : I get the same rate for IBM DCASmumble hard disk hung off an > : aha1542CF. > : The disc and the card are fast SCSI devices, 10 MB/s should be > : possible > : (okay, I don't care much because ISA cannot trasfer more than > : 2-3 MB/s > : anyway :) > > I've seen this bug in the aha driver, but haven't tracked it down > yet. It appears that most (all?) disks will default to this rate. I > don't know if that is a bios issue, or a driver issue. I suspect the > latter.... This is not a generic CAM bug. > > WArner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 13:58:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 57162155F6 for ; Mon, 8 Mar 1999 13:58:01 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id VAA52647; Mon, 8 Mar 1999 21:57:43 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA17956; Mon, 8 Mar 1999 14:58:03 -0700 (MST) Message-Id: <199903082158.OAA17956@harmony.village.org> To: mjacob@feral.com Subject: Re: SCSI Tape (HP SureStore T20) trouble Cc: Ladavac Marino , Josh MacDonald , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 08 Mar 1999 13:54:42 PST." References: Date: Mon, 08 Mar 1999 14:58:03 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : Context? The surestore tape discussion. Someone said that there was a bug in 3.0's sync negotiations. I was pointing out this bug is limited to the aha driver. The original poster was using a ncr, so this isn't the problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 14: 0: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orbit.flnet.com (orbit.flnet.com [205.240.232.32]) by hub.freebsd.org (Postfix) with ESMTP id A0C4F159F3; Mon, 8 Mar 1999 14:00:00 -0800 (PST) (envelope-from henrich@orbit.flnet.com) Received: (from henrich@localhost) by orbit.flnet.com (8.8.5/8.8.4) id QAA15790; Mon, 8 Mar 1999 16:59:40 -0500 (EST) Message-ID: <19990308135939.46895@orbit.flnet.com> Date: Mon, 8 Mar 1999 13:59:39 -0800 From: Charles Henrich To: Alan Cox Cc: Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Erorr: isa_dmainit(2, 1024) failed Mail-Followup-To: Alan Cox , Mike Smith , freebsd-hackers@freebsd.org, freebsd-smp@freebsd.org References: <19990308094100.14836@orbit.flnet.com> <199903081740.JAA06967@dingo.cdrom.com> <19990308101059.50251@orbit.flnet.com> <19990308142947.A471@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19990308142947.A471@nonpc.cs.rice.edu>; from Alan Cox on Mon, Mar 08, 1999 at 02:29:47PM -0600 X-Operating-System: FreeBSD 2.2-BETA_A X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the subject of Re: Erorr: isa_dmainit(2, 1024) failed, Alan Cox stated: > Charles, > > Please try the following simpler patch. It should accomplish the same thing > as Tor's patch. > > Replace the TAILQ_INSERT_TAIL in vm_page_startup (in vm_page.c) with a > TAILQ_INSERT_HEAD. It works almost perfectly! Whenever I first open the audio device there is all sorts of wacky siezing of the seizing until the audio starts to play, then everything goes back to normal. In any case, thanks (!) -Crh Charles Henrich Manex Visual Effects henrich@flnet.com http://orbit.flnet.com/~henrich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 14: 0:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 92F2F159FD for ; Mon, 8 Mar 1999 14:00:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA14547; Mon, 8 Mar 1999 13:59:35 -0800 Date: Mon, 8 Mar 1999 13:59:35 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Warner Losh Cc: Ladavac Marino , Josh MacDonald , freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Tape (HP SureStore T20) trouble In-Reply-To: <199903082158.OAA17956@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess I've missed the discussion about the T20 - is it in the archives of freebsd-hackers? If so I'll go refresh... On Mon, 8 Mar 1999, Warner Losh wrote: > In message Matthew Jacob writes: > : Context? > > The surestore tape discussion. Someone said that there was a bug in > 3.0's sync negotiations. I was pointing out this bug is limited to > the aha driver. The original poster was using a ncr, so this isn't > the problem. > > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 14:18:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id EBBE91546B; Mon, 8 Mar 1999 14:18:38 -0800 (PST) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA198941389; Mon, 8 Mar 1999 16:16:29 -0600 Date: Mon, 8 Mar 1999 16:16:29 -0600 From: Shawn Leas To: Mike Smith Cc: The Hermit Hacker , "Daniel C. Sobral" , Terry Lambert , sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: GGI Message-Id: <19990308161629.A16314@ixion.honeywell.com> References: <199903080503.VAA04942@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903080503.VAA04942@dingo.cdrom.com>; from Mike Smith on Sun, Mar 07, 1999 at 09:03:57PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: > > A friend just picked himself up a Voodoo2 card that Linux now supports and > > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > > down my throat :( My card is *supposedly* faster then what he has, from > > comparing specs...be great if I can slam it back down his throat :) > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > see how "supporting" this card actually achieves anything. > > If he's talking about GLIDE, you might mention that we support the > Linux GLIDE library... Jon Taylor, the Creative guy who works on GGI and KGI drivers, is also coding libggi3d, a modular 3d library that is SOOO COOL sounding. Anyone interested in learning more, please let me know, I'll get you some email addresses, and you can start talking to the movers and shakers. 3d in free unix will be MUCH more than glide... -- Shawn <=========== America Held Hostage ===========> Day 2238 for the poor and the middle class. Day 2257 for the rich and the dead. 684 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 14:47: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8269115609; Mon, 8 Mar 1999 14:46:53 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA23418; Mon, 8 Mar 1999 22:45:29 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 8 Mar 1999 22:45:29 +0000 (GMT) From: Doug Rabson To: Jason Thorpe Cc: The Hermit Hacker , Mike Smith , "Daniel C. Sobral" , Terry Lambert , sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: Re: GGI In-Reply-To: <199903081832.KAA00878@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 8 Mar 1999, Jason Thorpe wrote: > On Mon, 8 Mar 1999 00:26:02 -0400 (AST) > The Hermit Hacker wrote: > > > A friend just picked himself up a Voodoo2 card that Linux now supports and > > keeps cramming down the "FreeBSD doesn't support 3D accelleration" line > > down my throat :( My card is *supposedly* faster then what he has, from > > comparing specs...be great if I can slam it back down his throat :) > > Why should FreeBSD (or NetBSD for that matter) have to care about the > acceleration on the card? An operating system shoudl care about that > only for if the console is a linear framebuffer, and you want scrolling > to be Really Fast. (NetBSD's "wscons" console driver has hooks in the > terminal emulation layer for using hardware acceleration, which we > use on TURBOchannel "sfb" framebuffers, and soon on PCI TGA framebuffers.) > > For _everything_ else, it all belongs in userland. At this point, the > OS's responsibility is to provide a reasonable set of device mapping > primitives which allow source code portability across architectures. > NetBSD's "wscons" has some (albiet not all, yet) of the hooks for this, > as well as some other basic things to make it possible to implement naive > graphics applications, such as get/set colormap, get/set hardware cursor > shape, get/set hardware cursor position, etc. It just isn't possible to get full performance out of a modern DMA driven 3D chipset (which doesn't include the 3dfx) without a very small kernel based driver to feed the DMA pipe. Pretty near all of the rest of the code can live in userland. The bandwidth requirements for fast 3D are much greater than 2D. The 3dfx has a memory-based fifo to feed commands to the card and for this device, the only privileged operation is mapping the register set. AFAIK, the kernel driver for 3dfx does just this. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 15:13:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 3E10814CC1; Mon, 8 Mar 1999 15:13:37 -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 JAA01522; Tue, 9 Mar 1999 09:43:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA18005; Tue, 9 Mar 1999 09:43:18 +1030 (CST) Message-ID: <19990309094317.L490@lemis.com> Date: Tue, 9 Mar 1999 09:43:17 +1030 From: Greg Lehey To: wayne@crb-web.com, FreeBSD Hackers Subject: Re: writing device drivers for fbsd References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Wayne Cuddy on Mon, Mar 08, 1999 at 01:57:38PM -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 [following up to -hackers] On Monday, 8 March 1999 at 13:57:38 -0500, Wayne Cuddy wrote: > > What is a good reference to learn to to write device drivers for > fbsd? I remember someone recommended a good book a few months ago > but I forgot to save the message. I don't think there is a good book. The ones I have seen have been more "that's all there is" than "this is a great book". > I saw "Writing Unix Device Drivers" by George Pajari, this weekend > at the store,is this a good book? I don't know it. If you like the look of it, if it's not too old, and if it describes the BSD driver structures, it's probably worth having. Don't rely on any book by itself. > Where would I look in the kernel source to find out that functions > the kernel exports for driver usage and driver interfaces? /usr/src/sys. Most driver sources are in /usr/src/sys/dev, but some are in places like /usr/src/sys/i386 and /usr/src/sys/pci. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 15:31:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0923C14F91 for ; Mon, 8 Mar 1999 15:31:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA61032; Mon, 8 Mar 1999 15:31:19 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Joerg B. Micheel" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Need a cdevsw major number In-reply-to: Your message of "Thu, 04 Mar 1999 17:34:07 +0800." <19990304173407.O12467@krdl.org.sg> Date: Mon, 08 Mar 1999 15:31:19 -0800 Message-ID: <61028.920935879@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'd need a character device major number for a driver I have written. > I got permission to share with the public. It needs to be: Done. You have cdev #115. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 16: 1:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from helen.CS.Berkeley.EDU (helen.CS.Berkeley.EDU [128.32.131.251]) by hub.freebsd.org (Postfix) with ESMTP id E0D4214BE0 for ; Mon, 8 Mar 1999 16:01:28 -0800 (PST) (envelope-from jmacd@helen.CS.Berkeley.EDU) Received: (from jmacd@localhost) by helen.CS.Berkeley.EDU (8.9.1a/8.9.1) id QAA25814; Mon, 8 Mar 1999 16:00:58 -0800 (PST) Message-ID: <19990308160058.26896@helen.CS.Berkeley.EDU> Date: Mon, 8 Mar 1999 16:00:58 -0800 From: Josh MacDonald To: mjacob@feral.com, Warner Losh Cc: Ladavac Marino , Josh MacDonald , freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI Tape (HP SureStore T20) trouble References: <199903082158.OAA17956@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Matthew Jacob on Mon, Mar 08, 1999 at 01:59:35PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Matthew Jacob (mjacob@feral.com): > > I guess I've missed the discussion about the T20 - is it in the archives > of freebsd-hackers? If so I'll go refresh... There isn't much of a discussion. I still have the drive and I'm waiting to upgrade to 3.1 before I test it again. -josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 17:55:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 919DC14FCE for ; Mon, 8 Mar 1999 17:55:50 -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.3/8.8.8) with ESMTP id RAA02067; Mon, 8 Mar 1999 17:49:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903090149.RAA02067@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Dawes Cc: hackers@freebsd.org Subject: Re: Setting MTRRs from the X server In-reply-to: Your message of "Sun, 07 Mar 1999 15:33:50 +1100." <19990307153350.P4858@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 17:49:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For XFree86 4.0, we really need to be able to have the X server request > specific MTRR settings for different parts of a video card's physical > memory address space. While turning WC on for the framebuffer is a big > performance boost, a more critical issue is being able to make sure that > WC is turned off for areas that are used for memory mapped I/O. We've > found that some BIOSs enable WC in areas that our drivers want to use > for MMIO. One example is the 0xb0000-0xbffff range. > > So what I'm looking for is an interface that our X server can use to > request MTRR settings. An interface for this is present in the Linux > 2.2.x kernel (and we recently added code to use it), although it doesn't > currently allow changing the settings for the low 1MB of address space > (but I'm told that will be added at some point). For want of anything better, I'd guess that emulating the Linux interface would probably be the way to go. Is there a spec for it somewhere that can be read? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 17:57:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id BF08B14BDD for ; Mon, 8 Mar 1999 17:57:22 -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.3/8.8.8) with ESMTP id RAA02086; Mon, 8 Mar 1999 17:51:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903090151.RAA02086@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Dawes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: GGI In-reply-to: Your message of "Sun, 07 Mar 1999 15:25:41 +1100." <19990307152541.O4858@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 17:51:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of which (the Linux fb driver, not GGI), we're just adding a > driver to XFree86 4.0 that can use the Linux fb driver. It is useful > from our point of view for getting initial unaccelerated support for > otherwise unsupported video cards. I had a feeling that something > similar could be done for FreeBSD (using the VESA support in -current). > Is that right? If so, is anyone interested in doing it? It should be very simple; basically all that's missing right now is the ability to get the linear framebuffer address information from the VESA BIOS back into user-space. You should have no trouble mapping the video aperture. Would you want an interface for page-flipping etc. as well? Any design proposals that would make life optimal for you? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 18: 1:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 1F95514FCE for ; Mon, 8 Mar 1999 18:01: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.3/8.8.8) with ESMTP id RAA02140; Mon, 8 Mar 1999 17:55:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903090155.RAA02140@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Li ChunAn (Nokia/Beijing)" Cc: "'freebsd-hackers@FreeBSD.ORG'" Subject: Re: interrupt mechanism In-reply-to: Your message of "Tue, 02 Mar 1999 07:16:05 +0200." <199903022342.BAA24824@ns10.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Mar 1999 17:55:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello > I am a kernel programmer. Would you like to tell me something detailed about > the interrupt mechanism and kernel programming guides? Where can I find the > IRQ-handler table in kernel codes? FreeBSD generates the interrupt handler table dynamically at runtime, as interrupts can be moved from one handler to another, or chained between multiple handlers. You can read the low-level interrupt handler code for the i386 in /usr/src/sys/i386/isa/icu_* (for uniprocessor kernels) and /usr/src/sys/i386/isa/apic_* (for SMP kernels). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 18:47:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A30EE14D2D for ; Mon, 8 Mar 1999 18:47:12 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id SAA15429; Mon, 8 Mar 1999 18:45:41 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id SAA04601; Mon, 8 Mar 1999 18:45:37 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id TAA27563; Mon, 8 Mar 1999 19:45:25 -0700 Message-ID: <36E48B4F.BD62B07D@softweyr.com> Date: Mon, 08 Mar 1999 19:45:35 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: wayne@crb-web.com, FreeBSD Hackers Subject: Re: writing device drivers for fbsd References: <19990309094317.L490@lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > On Monday, 8 March 1999 at 13:57:38 -0500, Wayne Cuddy wrote: > > > > What is a good reference to learn to to write device drivers for > > fbsd? I remember someone recommended a good book a few months ago > > but I forgot to save the message. > > I don't think there is a good book. The ones I have seen have been > more "that's all there is" than "this is a great book". That's pretty much the state of affairs. I only a few, the Pajari book, the Egan & Texiera (?? this is from 10-year old memory), and the one by "J. E. Lapin" which was actually the staff at Rabbit Systems. They were all pretty much in the category of "there isn't a good choice." > > I saw "Writing Unix Device Drivers" by George Pajari, this weekend > > at the store,is this a good book? > > I don't know it. If you like the look of it, if it's not too old, and > if it describes the BSD driver structures, it's probably worth > having. Don't rely on any book by itself. I have a copy that is so old I used it to write a Minix driver, ca 1986. It's ancient, but will describe what UNIX device drivers do and how they do it. Along with several example drivers from the FreeBSD sources, it should be an adequate intoduction. IIRC, it doesn't cover network interface drivers at all. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 20:24:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 3DD8A14F46 for ; Mon, 8 Mar 1999 20:23:52 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: (qmail 14301 invoked from network); 9 Mar 1999 04:23:34 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 9 Mar 1999 04:23:34 -0000 Date: Mon, 8 Mar 1999 20:23:26 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Crash with ICMP bandwidth limiter. 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 Not exactly sure what happened. I started getting a truckload of warnings from syslog about ICMP responses, which was fine. Then I stopped the program that was creating them, and about 2 seconds later, I got a panic. I include the kernel backtrace: Any ideas? (kgdb) quit router4# !! gdb -k kernel.4 vmcore.4 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... IdlePTD 3268608 initial pcb at 270300 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor write, page not present instruction pointer = 0x8:0xf02429bd stack pointer = 0x10:0xf025bdcc frame pointer = 0x10:0xf025bde4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = trap number = 12 panic: page fault syncing disks... 1 1 done dumping to dev 1, offset 273184 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xf0131a84 in at_shutdown ( function=0xf02526ff <__set_sysinit_set_sym_memdev_sys_init+1115>, arg=0x0, queue=12) at ../../kern/kern_shutdown.c:446 #2 0xf01fccf5 in trap_fatal (frame=0xf025bd90, eva=16) at ../../i386/i386/trap.c:942 #3 0xf01fc9d3 in trap_pfault (frame=0xf025bd90, usermode=0, eva=16) at ../../i386/i386/trap.c:835 #4 0xf01fc64a in trap (frame={tf_es = -256180208, tf_ds = -256573424, tf_edi = -256163840, tf_esi = 0, tf_ebp = -265962012, tf_isp = -265962056, tf_ebx = -265961860, tf_edx = 0, tf_ecx = 920951465, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -266065475, tf_cs = 8, tf_eflags = 66118, tf_esp = -265961860, tf_ss = 0}) at ../../i386/i386/trap.c:437 #5 0xf02429bd in etp_multioutput () #6 0xf017c590 in ip_output (m0=0xf0754c80, opt=0x0, ro=0xf025be78, flags=0, imo=0x0) at ../../netinet/ip_output.c:608 #7 0xf0178854 in icmp_send (m=0xf0754c80, opts=0x0) at ../../netinet/ip_icmp.c:675 #8 0xf01787e7 in icmp_reflect (m=0xf0754c80) at ../../netinet/ip_icmp.c:638 #9 0xf0178120 in icmp_error (n=0xf075d500, type=3, code=3, dest=0, destifp=0x0) at ../../netinet/ip_icmp.c:200 #10 0xf0184d08 in udp_input (m=0xf075d500, iphlen=20) ---Type to continue, or q to quit--- at ../../netinet/udp_usrreq.c:304 #11 0xf01792bf in ip_input (m=0xf075d500) at ../../netinet/ip_input.c:693 #12 0xf0179337 in ipintr () at ../../netinet/ip_input.c:720 (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 22: 8: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (FLEDGE.RES.CMU.EDU [128.2.93.229]) by hub.freebsd.org (Postfix) with ESMTP id 7DA3414D3D for ; Mon, 8 Mar 1999 22:08:03 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.8.8/8.8.8) with SMTP id BAA15959; Tue, 9 Mar 1999 01:07:15 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Tue, 9 Mar 1999 01:07:15 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Andrzej Bialecki Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: FreeBSD and ThinkPad 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, 7 Mar 1999, Andrzej Bialecki wrote: > On Sat, 6 Mar 1999, Mike Smith wrote: > > > > > To start with, does it have more than 64M of memory? At least some of > > the stinkpads have problems with our speculative memory probes. > > Yeah, 128MB. I've put "MAXMEM" into kernel config file, and it seemed to > help. But overall, I'm really less than pleased with this sucker. One > thing is the BIOS which requires Windows to configure anything > significant, the other thing is built-in softmodem (which of course will > not work). My impression is that under the hood this machine is not quite > a PC, but WinIBM or something :-( So I have a ThinkPad 560E (well, two of them actually :) for work on Coda; I've found that there is a config program from IBM that runs on a single DOS bootable DOS floppy that is certainly preferable to keeping windows around. On the other hand, this machine doesn't have a soft modem so I don't have to deal with that. When I returned the first to them for repairs, they unfortunately upgraded the BIOS :( making it go from XiG-APM-HAPPY to XiG-APM-CRANKY in which it doesn't like to restore the delay if X was running when it suspended. Curiously, the second machine to be returned, be upgraded against my instructions, and come back seems to work fine. I speculate another version of the BIOS, but am not sure how to verify that. Try IBM's web page for the DOS configurator. It may be that it could run under doscmd if it were given access to the right IO ports; it's a purely text program in the style of a boring UNIX utility without even curses. I haven't tried yet. Robert N Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon University http://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ Safeport Network Services http://www.safeport.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 8 22:26: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marvin.albury.net.au (marvin.albury.NET.AU [203.15.244.108]) by hub.freebsd.org (Postfix) with ESMTP id 8F31815116 for ; Mon, 8 Mar 1999 22:25:58 -0800 (PST) (envelope-from josh2@marvin.albury.net.au) Received: (from josh2@localhost) by marvin.albury.net.au (8.9.1a/8.9.1) id RAA28603 for freebsd-hackers@freebsd.org; Tue, 9 Mar 1999 17:28:12 +1100 (EST) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 09 Mar 1999 17:00:12 +1100 (EST) From: Josh To: freebsd-hackers@freebsd.org Subject: Trafshow / file Byte discrepency Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I am playing with trafshow and have noticed that it will report LESS bytes transferred than the file size! This occurs on two seperate copies of trafshow (ie. one copy I have NOT played with) and yet a BIOCGSTATS reports NO dropped packets. I am at a loss and really do not want to go through the code digging out the different protocol information to try and find out where the discrepency is. I would love to hear any explanation anyone may have or even pure conjecture ;-) Josh ---------------------------------- E-Mail: Josh Date: 09-Mar-99 Time: 17:00:13 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 0:51:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kyrnet.kg (ns.kyrnet.kg [195.254.160.9]) by hub.freebsd.org (Postfix) with ESMTP id 139F115040 for ; Tue, 9 Mar 1999 00:51:18 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from localhost by kyrnet.kg (8.9.3/8.9.1) with ESMTP id NAA12309; Tue, 9 Mar 1999 13:41:25 +0500 (GMT) X-Authentication-Warning: kyrnet.kg: fygrave owned process doing -bs Date: Tue, 9 Mar 1999 13:41:25 +0500 (GMT) From: CyberPsychotic X-Sender: fygrave@kyrnet.kg To: Alfred Perlstein , Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SOCK_RAW on BSD In-Reply-To: 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 ~ ~ If you are trying to capture packets you should look at 'bpf', if you ~ are trying to capture packets in a portable fashion, look at the library ~ 'pcap' ~ Yep. Yesterday night I got back to my R.Steven's Unix Network Programming biblebook which says in section 25.4: "Received UDP/TCP packets are never passed to a raw socket. if process wants to read IP datagrams containing UDP/TCP packets, they must be read at datalink layer." This should explain everything. This morning I had a chance to test this thing on several Solaris systems (2.5-2.7), and got the same result as on BSD. Looks like Linux is the only platform which acts different. Not the reason to laugh at it but... ;-) Thanks again to everyone who responded, I will probably switch to pcap for the sake of compatibility. regards ~ Fyodor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 1: 1:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 354A0151C9 for ; Tue, 9 Mar 1999 01:00:59 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id UAA26379 for ; Tue, 9 Mar 1999 20:00:39 +1100 (EDT) Received: from areilly.bpc-users.org (CPE-24-192-50-137.nsw.bigpond.net.au [24.192.50.137]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with SMTP id UAA10317 for ; Tue, 9 Mar 1999 20:00:38 +1100 (EDT) Received: (qmail 14681 invoked by uid 1000); 9 Mar 1999 09:00:38 -0000 From: "Andrew Reilly" Message-ID: <19990309200037.A14630@reilly.home> Date: Tue, 9 Mar 1999 20:00:37 +1100 To: Mike Smith , The Hermit Hacker Cc: "Daniel C. Sobral" , Terry Lambert , sos@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: GGI References: <199903080503.VAA04942@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199903080503.VAA04942@dingo.cdrom.com>; from Mike Smith on Sun, Mar 07, 1999 at 09:03:57PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > see how "supporting" this card actually achieves anything. Isn't the PEX extension some sort of 3D thing? I never hear anyone talk about it, so perhaps there's something wrong with it, but couldn't some sort of 3D acceleration be built around it? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 1:28: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 398B515046; Tue, 9 Mar 1999 01:27:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA05986; Tue, 9 Mar 1999 18:26:57 +0900 (JST) Message-ID: <36E4E25D.DE57F27B@newsguy.com> Date: Tue, 09 Mar 1999 17:57:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mike Smith Cc: Charles Henrich , freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Erorr: isa_dmainit(2, 1024) failed References: <199903081740.JAA06967@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > How does one fix this? :) > > With a text editor. Find the code that does it wrong, change it and > recompile. Send us the diffs when you're done. A text editor... :-) The ultimate bug-fixing tool! :-) I loved it... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 1:28:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2AFB81515C; Tue, 9 Mar 1999 01:28:04 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id SAA06086; Tue, 9 Mar 1999 18:27:32 +0900 (JST) Message-ID: <36E4E31B.9CA2AA70@newsguy.com> Date: Tue, 09 Mar 1999 18:00:11 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Tor.Egge@fast.no Cc: mike@smith.net.au, henrich@flnet.com, freebsd-hackers@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Erorr: isa_dmainit(2, 1024) failed References: <199903081740.JAA06967@dingo.cdrom.com> <199903081827.TAA70476@midten.fast.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tor.Egge@fast.no wrote: > > Index: sys/i386/i386/pmap.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/i386/pmap.c,v > retrieving revision 1.223 > diff -u -r1.223 pmap.c > --- pmap.c 1999/02/19 14:25:33 1.223 > +++ pmap.c 1999/02/26 04:25:22 > @@ -71,6 +71,7 @@ > #include "opt_disable_pse.h" > #include "opt_pmap.h" > #include "opt_msgbuf.h" > +#include "isa.h" ^^^^^ I have a slight suspicion that Bruce would not be very please with this... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 1:49:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 17A8B1505F; Tue, 9 Mar 1999 01:49:02 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA24886; Tue, 9 Mar 1999 09:49:10 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 9 Mar 1999 09:49:10 +0000 (GMT) From: Doug Rabson To: Andrew Reilly Cc: Mike Smith , The Hermit Hacker , "Daniel C. Sobral" , Terry Lambert , sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: Re: GGI In-Reply-To: <19990309200037.A14630@reilly.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Mar 1999, Andrew Reilly wrote: > On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > > see how "supporting" this card actually achieves anything. > > Isn't the PEX extension some sort of 3D thing? I never hear > anyone talk about it, so perhaps there's something wrong with > it, but couldn't some sort of 3D acceleration be built around > it? PEX is several years away from the cutting edge of graphics. I'm not sure that it even supports texture mapping. A better base for working on 3D acceleration is Mesa which is exactly what the guys at Precision Insight (www.precisioninsight.com) are doing to create a decent modern 3D solution for Linux and BSD. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 2:42:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id 42D0714CC1 for ; Tue, 9 Mar 1999 02:42:43 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10KJxs-000HytC; Tue, 9 Mar 1999 05:42:20 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs (fwd) To: chris@shenton.org, hackers@freebsd.org Date: Tue, 9 Mar 1999 05:42:20 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM920976140-19527-0_ Content-Transfer-Encoding: 7bit Content-Length: 6536 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM920976140-19527-0_ Content-Type: message/rfc822 Content-Disposition: inline Content-Description: Forwarded message from Tom Torrance Content-Transfer-Encoding: 7bit Return-Path: Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10KJSk-000HytC; Tue, 9 Mar 1999 05:10:10 -0500 (EST) Message-Id: From: freebsd (Tom Torrance) Subject: Re: 3.1-STABLE: nrsa0 T4000 doesn't honor "no rewind"? SCSI errs in logs In-Reply-To: from Matthew Jacob at "Mar 8, 1999 7:50:26 am" To: mjacob@feral.com Date: Tue, 9 Mar 1999 05:10:10 -0500 (EST) Cc: scsi@freebsd.org, tom@tomqnx.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM920974210-19344-0_ Content-Transfer-Encoding: 7bit Content-Length: 5661 --ELM920974210-19344-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > > What errors? And what 'does not honor'? I know that Tom Torrance claimed > this happened- which I can't reproduce. RELENG_3 generates errors. Your routine to rewind the tape at EOM is activated by those errors. The test version of "current" that you sent me does not generate those errors. Your routine to rewind the tape is not activated. Attached you will find a backup script and the associated errors generated from it using today's version of RELENG_3. More errors than usual are generated now. It used to only complain about the PREVENT/ALLOW. Using RELENG_3 the tape always rewinds on the "DUMP: Closing /dev/nrsa0" message which appears on the console. Note that a person running X-windows would not see the error messages. Regards, Tom > > On 8 Mar 1999, Chris Shenton wrote: > > > Oops, should have provided details on the drive; dmesg says: > > > > ahc0: rev 0x03 int a irq 9 on pci0.8.0 > > ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs > > > > sa0 at ahc0 bus 0 target 5 lun 0 > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 3.300MB/s transfers > > > > da0 at ahc0 bus 0 target 3 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > > da0: 8682MB (17781964 512 byte sectors: 255H 63S/T 1106C) > > changing root device to da0s1a > > > > cd0 at ahc0 bus 0 target 2 lun 0 > > cd0: Removable CD-ROM SCSI-2 device > > cd0: 5.681MB/s transfers (5.681MHz, offset 15) > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > > > > > > > > > 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 > --ELM920974210-19344-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=dmesg Content-Description: dmesg Content-Transfer-Encoding: 7bit evice sa0: 3.300MB/s transfers pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JKA5580002KB3M pass0: 20.000MB/s transfers (20.000MHz, 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 pass2 at ncr0 bus 0 target 6 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: 3.300MB/s transfers cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [253970 x 2048 byte records] da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JKA5580002KB3M da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) 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 ffs_mountfs: superblock updated for soft updates (sa0:ncr0:0:6:0): MODE SENSE(06). CDB: 1a 0 f 0 1c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (sa0:ncr0:0:6:0): Invalid field in CDB (sa0:ncr0:0:6:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:26,0 (sa0:ncr0:0:6:0): Invalid field in parameter list (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 ff ff ff 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:2c,0 (sa0:ncr0:0:6:0): Command sequence error (sa0:ncr0:0:6:0): unable to backspace over one of double filemarks at EOD- opting for safety (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): SPACE. CDB: 11 1 ff ff ff 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:2c,0 (sa0:ncr0:0:6:0): Command sequence error (sa0:ncr0:0:6:0): unable to backspace over one of double filemarks at EOD- opting for safety (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code (sa0:ncr0:0:6:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (sa0:ncr0:0:6:0): ILLEGAL REQUEST asc:20,0 (sa0:ncr0:0:6:0): Invalid command operation code --ELM920974210-19344-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=backup Content-Description: backup script Content-Transfer-Encoding: 7bit #!/bin/sh # System Backup export TAPE=/dev/nrsa0 mt rewind mt status >/dev/null 2>&1 dump 0abuf 64 /dev/nrsa0 / dump 0abuf 64 /dev/nrsa0 /usr mt rewind --ELM920974210-19344-0_-- --ELM920976140-19527-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 3: 8:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 8CBA615190 for ; Tue, 9 Mar 1999 03:08:13 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA19513; Tue, 9 Mar 1999 20:07:38 +0900 (JST) Message-ID: <36E4ED98.26E59466@newsguy.com> Date: Tue, 09 Mar 1999 18:44:56 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Wes Peters Cc: Greg Lehey , wayne@crb-web.com, FreeBSD Hackers Subject: Re: writing device drivers for fbsd References: <19990309094317.L490@lemis.com> <36E48B4F.BD62B07D@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > > > I don't think there is a good book. The ones I have seen have been > > more "that's all there is" than "this is a great book". > > That's pretty much the state of affairs. I only a few, the Pajari book, > the Egan & Texiera (?? this is from 10-year old memory), and the one by > "J. E. Lapin" which was actually the staff at Rabbit Systems. They were > all pretty much in the category of "there isn't a good choice." > > > > I saw "Writing Unix Device Drivers" by George Pajari, this weekend > > > at the store,is this a good book? > > I have a copy that is so old I used it to write a Minix driver, ca 1986. > It's ancient, but will describe what UNIX device drivers do and how they do > it. Along with several example drivers from the FreeBSD sources, it should > be an adequate intoduction. > > IIRC, it doesn't cover network interface drivers at all. How about The Design and Implementation of 4.4 BSD? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 4:35: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from theo.thg.goe.ni.schule.de (theo.THG.Goe.NI.Schule.DE [195.27.182.97]) by hub.freebsd.org (Postfix) with ESMTP id 8184514CD0; Tue, 9 Mar 1999 04:34:37 -0800 (PST) (envelope-from gratke@thg.goe.ni.schule.de) Received: from elly.thg.goe.ni.schule.de (gratke@elly.thg.goe.ni.schule.de [195.27.182.98]) by theo.thg.goe.ni.schule.de (8.8.8/8.8.8) with SMTP id NAA06778; Tue, 9 Mar 1999 13:33:09 +0100 Date: Tue, 9 Mar 1999 13:34:16 +0100 (MET) From: Georg Ratke To: hackers@FreeBSD.ORG Cc: freebsd-hackers-digest@FreeBSD.ORG Subject: Re: freebsd-hackers-digest V4 #416 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers-digest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 5:55:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat196.27.mpoweredpc.net [142.177.196.27]) by hub.freebsd.org (Postfix) with ESMTP id B540F15038; Tue, 9 Mar 1999 05:55:21 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id JAA97408; Tue, 9 Mar 1999 09:54:33 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 9 Mar 1999 09:54:33 -0400 (AST) From: The Hermit Hacker To: Doug Rabson Cc: Andrew Reilly , Mike Smith , "Daniel C. Sobral" , Terry Lambert , sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: Re: GGI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Mar 1999, Doug Rabson wrote: > On Tue, 9 Mar 1999, Andrew Reilly wrote: > > > On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: > > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > > > see how "supporting" this card actually achieves anything. > > > > Isn't the PEX extension some sort of 3D thing? I never hear > > anyone talk about it, so perhaps there's something wrong with > > it, but couldn't some sort of 3D acceleration be built around > > it? > > PEX is several years away from the cutting edge of graphics. I'm not sure > that it even supports texture mapping. A better base for working on 3D > acceleration is Mesa which is exactly what the guys at Precision Insight > (www.precisioninsight.com) are doing to create a decent modern 3D solution > for Linux and BSD. Most intriguing...just went through the site, and its another project "supported by RedHat", and "binary-only"...is anyone from FreeBSD, Inc approaching them from the *BSD camp? Also, and correct me if I'm wrong, but looking at the FAQ, they don't support 3Dfx/Voodoo2 stuff? I would have thought that those would have been the first ones that they would have concentrated on, considering how big they appear to be...? The project itself looks promising...hopefully we'll see *BSD binaries eventually...:) 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 Tue Mar 9 6: 8:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id DBDDD153A0 for ; Tue, 9 Mar 1999 06:08:55 -0800 (PST) (envelope-from dennis@etinc.com) Received: from workstation.etinc.com (port51.netsvr1.cst.vastnet.net [207.252.73.51]) by etinc.com (8.8.8/8.6.9) with SMTP id JAA24926; Tue, 9 Mar 1999 09:11:43 -0500 (EST) Message-Id: <199903091411.JAA24926@etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 09 Mar 1999 09:18:06 -0500 To: "Daniel C. Sobral" , Wes Peters From: Dennis Subject: Re: writing device drivers for fbsd Cc: Greg Lehey , wayne@crb-web.com, FreeBSD Hackers In-Reply-To: <36E4ED98.26E59466@newsguy.com> References: <19990309094317.L490@lemis.com> <36E48B4F.BD62B07D@softweyr.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 06:44 PM 3/9/99 +0900, Daniel C. Sobral wrote: >Wes Peters wrote: >> >> > I don't think there is a good book. The ones I have seen have been >> > more "that's all there is" than "this is a great book". >> >> That's pretty much the state of affairs. I only a few, the Pajari book, >> the Egan & Texiera (?? this is from 10-year old memory), and the one by >> "J. E. Lapin" which was actually the staff at Rabbit Systems. They were >> all pretty much in the category of "there isn't a good choice." >> >> > > I saw "Writing Unix Device Drivers" by George Pajari, this weekend >> > > at the store,is this a good book? >> >> I have a copy that is so old I used it to write a Minix driver, ca 1986. >> It's ancient, but will describe what UNIX device drivers do and how they do >> it. Along with several example drivers from the FreeBSD sources, it should >> be an adequate intoduction. >> >> IIRC, it doesn't cover network interface drivers at all. > >How about The Design and Implementation of 4.4 BSD? The "good" thing is that the design is solid and hasn't changed much. The Linux device driver book, although useful, is wrong on some counts and missing info on others. 'BSD has remained similar across major releases while Linux changes twice a year. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 8:53:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id B8C8E14E1D for ; Tue, 9 Mar 1999 08:53:28 -0800 (PST) (envelope-from terry@ppsl.demon.co.uk) Received: from [158.152.16.214] (helo=yeoman.ppsl.co.uk) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 10KPki-0005F7-0B for freebsd-hackers@freebsd.org; Tue, 9 Mar 1999 16:53:08 +0000 Date: Tue, 9 Mar 99 16:52:52 GMT Message-Id: <9903091652.AA04146@ppsl.demon.co.uk> From: Terry Glanfield To: freebsd-hackers@freebsd.org Subject: Tunnel loopback Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to use a FreeBSD (3.0-RELEASE and 3.1-RELEASE) tunnel device (/dev/tunN) to push packets back onto the IP stack[1] with some success. Firstly I redirect all packets on one interface (ed0) to the tunnel using IPFilter: pass in quick on ed0 to tun0 all Then with a simple read/write loop attached to /dev/tun0 I can bounce all packets back in again. This works up to a point. I'm finding that a single icmp packet send into tun0 results in thousands of packets entering my read/write loop before one packet finally finds its way out again. If I insert a short sleep between the read and write calls the number of packets are reduced but the overall time taken remains constant (~1 second). Hacking the loopback into the kernel (if_tun.c) results in a similar time scale but hundreds of thousands of packets being bounced around. I get the feeling I'm missing something obvious. Short-term state information or optimisations maybe? Any pointers would be much appreciated. Regards, Terry. [1] The idea is to mix NAT and SKIP on the same box by doing the SKIP encryption on a different interface before it hits NAT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 11:12:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy.upg.sinn.ru (proxy.upg.sinn.ru [195.166.168.195]) by hub.freebsd.org (Postfix) with SMTP id C4B9B14DE2 for ; Tue, 9 Mar 1999 11:11:08 -0800 (PST) (envelope-from saenara@usa.net) Received: by proxy.upg.sinn.ru with MERCUR-SMTP/POP3/IMAP4-Server (v3.00.25 RI-0000000) for at Tue, 9 Mar 1999 22:13:11 +0300 Received: by localhost with Microsoft MAPI; Tue, 9 Mar 1999 22:17:34 +0300 Message-ID: <01BE6A7A.A1CE2A70.saenara@usa.net> From: Saenara Reply-To: "saenara@usa.net" To: "'freebsd-hardware@freebsd.org'" Cc: "'freebsd-hackers@freebsd.org'" Subject: PCI modem Date: Tue, 9 Mar 1999 22:06:18 +0300 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 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 Can you please explain what shall I do to setup PCI modem under FreeBSD 3.0. wbr, saenara. mailto:saenara@usa.net PGP#0x0D60E26F ICQ#13647173 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 11:21:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 6EB3A14F82 for ; Tue, 9 Mar 1999 11:21:15 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA13520; Tue, 9 Mar 1999 11:10:54 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdA13501; Tue Mar 9 19:10:40 1999 Message-ID: <36E57226.15FB7483@whistle.com> Date: Tue, 09 Mar 1999 11:10:30 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Terry Glanfield Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Tunnel loopback References: <9903091652.AA04146@ppsl.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Glanfield wrote: > > Hi, > > I've been trying to use a FreeBSD (3.0-RELEASE and 3.1-RELEASE) tunnel > device (/dev/tunN) to push packets back onto the IP stack[1] with some > success. Firstly I redirect all packets on one interface (ed0) to > the tunnel using IPFilter: > > pass in quick on ed0 to tun0 all > > Then with a simple read/write loop attached to /dev/tun0 I can bounce > all packets back in again. This works up to a point. > > I'm finding that a single icmp packet send into tun0 results in > thousands of packets entering my read/write loop before one packet > finally finds its way out again. If I insert a short sleep between > the read and write calls the number of packets are reduced but the > overall time taken remains constant (~1 second). Hacking the loopback > into the kernel (if_tun.c) results in a similar time scale but > hundreds of thousands of packets being bounced around. > > I get the feeling I'm missing something obvious. Short-term state > information or optimisations maybe? Any pointers would be much > appreciated. > > Regards, > Terry. You might find that using ipfw and divert sockets is a much more natural fit to this problem. Divert sockets can be used instead of or in conjunction with the tun device. > > [1] The idea is to mix NAT and SKIP on the same box by doing the SKIP > encryption on a different interface before it hits NAT. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 11:36:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 126671507A; Tue, 9 Mar 1999 11:36:06 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.1a/8.8.8) id WAA09441; Tue, 9 Mar 1999 22:39:37 +0300 (MSK) (envelope-from babolo) Message-Id: <199903091939.WAA09441@aaz.links.ru> Subject: Re: starting partition In-Reply-To: from "Eduardo Viruena Silva" at "Mar 8, 99 01:24:05 pm" To: mrspock@esfm.ipn.mx (Eduardo Viruena Silva) Date: Tue, 9 Mar 1999 22:39:37 +0300 (MSK) Cc: questions@FreeBSD.ORG, hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eduardo Viruena Silva writes: > I think this is not a question but an observation... > > I have asked you about a problem that occurres when you install FreeBSD in > two different PARTITIONS of the same IDE disk. It seems to me that > FreeBSD does not let you do that, I mean, you cannot have version 2.2.8 > and version 3.0 in the same disk because the installation process destroys > one of the disk labels. (I made a question about it some weeks ago, > they answered me that I have made a mess with my disk labels, so I > repeated the experiment and it happened again... I installed version 2.2.8 > in partition 1, and version 3.0 in partition 2. Patition 2 became a > mess). > > Some other Unix versions (the old ultrix and osf/1) require three > "coordinates" for specifying the kernel's position: the disk number, the > patition number, and the slice letter. > > So, if you want to start from disk 2, patition 1, slice a, > the loader should have to receive: > > wd(2,1,a)kernel > > and not: > wd(2,a)kernel > > But this is not possbile in FreeBSD loader. > > I am not saying only non-sense, aren't I? > > Could you do something for correct this? Why do you need different slices? This is my way as example: wd0s1a / for 2.2.8-R wd0s1b swap for 2.2.8-R and 3.1-R wd0s1d / for 3.1-R wd0s1e /tmp for 2.2.8-R and 3.1-R wd0s1f / with /var & /usr in it for 2.1.7-R wd0s1g /home for 2.2.8-R and 3.1-R and 2.1.7-R ..... wd0s2d /var for 3.1-R wd0s2e /var for 2.2.8-R ..... wd0s3g /usr for 3.1-R wd0s3h /usr for 2.2.8-R ... so on When you share the same disk with BSDI then use only s1 partitions for BSDI (for compatibility disk labels) -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 12: 3:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id D2A24153B6; Tue, 9 Mar 1999 12:03:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA25667; Tue, 9 Mar 1999 20:03:15 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 9 Mar 1999 20:03:15 +0000 (GMT) From: Doug Rabson To: The Hermit Hacker Cc: Andrew Reilly , Mike Smith , "Daniel C. Sobral" , Terry Lambert , sos@freebsd.org, freebsd-hackers@freebsd.org, yokota@freebsd.org Subject: Re: GGI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Mar 1999, The Hermit Hacker wrote: > On Tue, 9 Mar 1999, Doug Rabson wrote: > > > On Tue, 9 Mar 1999, Andrew Reilly wrote: > > > > > On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: > > > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite > > > > see how "supporting" this card actually achieves anything. > > > > > > Isn't the PEX extension some sort of 3D thing? I never hear > > > anyone talk about it, so perhaps there's something wrong with > > > it, but couldn't some sort of 3D acceleration be built around > > > it? > > > > PEX is several years away from the cutting edge of graphics. I'm not sure > > that it even supports texture mapping. A better base for working on 3D > > acceleration is Mesa which is exactly what the guys at Precision Insight > > (www.precisioninsight.com) are doing to create a decent modern 3D solution > > for Linux and BSD. > > Most intriguing...just went through the site, and its another project > "supported by RedHat", and "binary-only"...is anyone from FreeBSD, Inc > approaching them from the *BSD camp? I approached them (on my own behalf) to ask them about BSD support and they are keen. They really are open source people but are attempting to work around the NDA mentality which some of the chip vendors have. Already they have donated the source for some of their servers (NeoMagic and Glint I think) to XFree86 as the vendors relaxed their NDAs. > > Also, and correct me if I'm wrong, but looking at the FAQ, they don't > support 3Dfx/Voodoo2 stuff? I would have thought that those would have > been the first ones that they would have concentrated on, considering how > big they appear to be...? They are trying to build an infrastructure for 3D under XFree86. For various reasons Voodoo1 and Voodoo2 will never be a good platform for an X server. > > The project itself looks promising...hopefully we'll see *BSD binaries > eventually...:) I think we will be able to use this stuff with a minimum effort (porting the small kernel drivers). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 14: 8: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id AE17A14F45 for ; Tue, 9 Mar 1999 14:07:46 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from jehovah (jehovah.technokratis.com [207.139.115.248]) by oracle.dsuper.net (Delphi 1.3/8.6.9) with SMTP id RAA08352; Tue, 9 Mar 1999 17:07:22 -0500 (EST) Message-ID: <001d01be6a79$cfbefd20$0100000a@jehovah.technokratis.com> Reply-To: "Bosko Milekic" From: "Bosko Milekic" To: "CyberPsychotic" Cc: Subject: Re: SOCK_RAW on BSD Date: Tue, 9 Mar 1999 17:11:38 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Read below... -----Original Message----- From: CyberPsychotic To: Alfred Perlstein ; Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Date: Tuesday, March 09, 1999 3:52 AM Subject: Re: SOCK_RAW on BSD >~ >~ If you are trying to capture packets you should look at 'bpf', if you >~ are trying to capture packets in a portable fashion, look at the library >~ 'pcap' >~ > > Yep. Yesterday night I got back to my R.Steven's Unix Network Programming >biblebook which says in section 25.4: > >"Received UDP/TCP packets are never passed to a raw socket. if process wants > to read IP datagrams containing UDP/TCP packets, they must be read at > datalink layer." > >This should explain everything. This morning I had a chance to test this >thing on several Solaris systems (2.5-2.7), and got the same result as on >BSD. Looks like Linux is the only platform which acts different. Not the >reason to laugh at it but... ;-) Actually, under Linux, one _also_ has to read from the datalink layer in order to be able to get TCP and/or UDP datagrams. The difference is that under Linux, one would create a socket of type SOCK_PACKET to be able to consequently read from it. There are several disadvantages to SOCK_PACKET (in comparison to libpcap and bpf, for instance) -- such as no kernel buffering and/or filtering. Therefore, to end this thread, as Mike Smith mentionned in an earlier reply to this: ideally, for portability issues, using libpcap is the best idea (support for BPF, DLPI, NIT, SOCK_PACKET, etc.) > >Thanks again to everyone who responded, I will probably switch to pcap for >the sake of compatibility. > > >regards > >~ Fyodor > > Cheers, <- - - - - - - - - - - --- --- -- - - Bosko Milekic http://www.supernet.ca/~bmilekic/ Delphi SuperNet - 1-888-SUPER-MTL -- - -- - - - - - --- --- - - - - - - - - - - > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 14:41: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id 6AE5214F39 for ; Tue, 9 Mar 1999 14:40:59 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from ivy.ezo.net (ivy.ezo.net [206.150.211.171]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id RAA03003; Tue, 9 Mar 1999 17:40:20 -0500 (EST) Message-ID: <000d01be6a7e$39343960$abd396ce@ivy.ezo.net> From: "Jim Flowers" To: "Terry Glanfield" , Subject: Re: Tunnel loopback Date: Tue, 9 Mar 1999 17:43:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a basic problem with your strategy. SKIP is unidirectional and the inbound packets will have to be received on the configured interface to be authenticated. There are other problems, as well. When you hide SKIP behind NAT the outside skiphost can't communicate with the inside skiphost as its address is unknown. Each direction is independent of the other, so even if the inside skiphost starts the communication the return from the outside skiphost is blocked by NAT. The good news is that you can mix SKIP and NAT on the same box as designed. Just remember that SKIP gets the last shot (outbound, really the first shot - inbound) as it is shimmed in just before the ethernet interface that you are controlling. I think I posted a how-to on freebsd-security a couple of months back. You can put ipfw rules in before the divert to accept and therefore bypass NAT for the skip and cdp protocols. Also control when a host on the local network uses SKIP or NAT by setting its default route for the SKIP/NAT box and then including a rule prior to the divert to accept it if you want SKIP instead of NAT. The only thing I was not able to work out was putting the default route in a tunnel to the Internet. That worked OK for the hosts that were SKIPping but also ate the routes for the hosts that were still trying to use NAT. Tunnels are OK but only for named networks; not so great for the Internet at large. Were you able to get the FreeBSD Skip-1.0 port to compile on 3.1? Good Luck. -----Original Message----- From: Terry Glanfield To: freebsd-hackers@FreeBSD.ORG Date: Tuesday, March 09, 1999 11:53 AM Subject: Tunnel loopback > >Hi, > >I've been trying to use a FreeBSD (3.0-RELEASE and 3.1-RELEASE) tunnel > >[1] The idea is to mix NAT and SKIP on the same box by doing the SKIP >encryption on a different interface before it hits NAT. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 14:41:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C598614DB7 for ; Tue, 9 Mar 1999 14:41:38 -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 JAA07635; Wed, 10 Mar 1999 09:11:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA20874; Wed, 10 Mar 1999 09:11:17 +1030 (CST) Message-ID: <19990310091116.C490@lemis.com> Date: Wed, 10 Mar 1999 09:11:16 +1030 From: Greg Lehey To: "Daniel C. Sobral" , Wes Peters Cc: wayne@crb-web.com, FreeBSD Hackers Subject: Re: writing device drivers for fbsd References: <19990309094317.L490@lemis.com> <36E48B4F.BD62B07D@softweyr.com> <36E4ED98.26E59466@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <36E4ED98.26E59466@newsguy.com>; from Daniel C. Sobral on Tue, Mar 09, 1999 at 06:44:56PM +0900 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, 9 March 1999 at 18:44:56 +0900, Daniel C. Sobral wrote: > Wes Peters wrote: >> >>> I don't think there is a good book. The ones I have seen have been >>> more "that's all there is" than "this is a great book". >> >> That's pretty much the state of affairs. I only a few, the Pajari book, >> the Egan & Texiera (?? this is from 10-year old memory), and the one by >> "J. E. Lapin" which was actually the staff at Rabbit Systems. They were >> all pretty much in the category of "there isn't a good choice." >> >>>> I saw "Writing Unix Device Drivers" by George Pajari, this weekend >>>> at the store,is this a good book? >> >> I have a copy that is so old I used it to write a Minix driver, ca 1986. >> It's ancient, but will describe what UNIX device drivers do and how they do >> it. Along with several example drivers from the FreeBSD sources, it should >> be an adequate intoduction. >> >> IIRC, it doesn't cover network interface drivers at all. > > How about The Design and Implementation of 4.4 BSD? I assume that Dennis missed a reference to the book rather than the design. I don't think it's much help for writing device drivers; at any rate, it's not a complete reference. 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 Tue Mar 9 15: 6:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (ntu-kpi.kiev.ua [195.178.136.20]) by hub.freebsd.org (Postfix) with ESMTP id 5B62314ECB for ; Tue, 9 Mar 1999 15:06:02 -0800 (PST) (envelope-from lx@hosix.ntu-kpi.kiev.ua) Received: from hosix.ntu-kpi.kiev.ua (IDENT:0@eth0.hosix.ntu-kpi.kiev.ua [10.100.0.6]) by relay1.ntu-kpi.kiev.ua (8.NYB/8.NYB) with ESMTP id BAA03598 for ; Wed, 10 Mar 1999 01:05:42 +0200 (EET) (envelope-from lx@hosix.ntu-kpi.kiev.ua) Received: from lx.hosix.ntu-kpi.kiev.ua (lx.hosix.ntu-kpi.kiev.ua [10.100.23.72]) by hosix.ntu-kpi.kiev.ua (1.2.3.4/hidden) with ESMTP id BAA02374 for ; Wed, 10 Mar 1999 01:05:41 +0200 (EET) Received: (from lx@localhost) by lx.hosix.ntu-kpi.kiev.ua (8.9.2/8.9.1) id BAA00511 for freebsd-hackers@freebsd.org; Wed, 10 Mar 1999 01:05:41 +0200 (EET) Date: Wed, 10 Mar 1999 01:05:40 +0200 From: Alexander Matey To: freebsd-hackers@freebsd.org Subject: Static ARP again. kern/6432 revisited. Message-ID: <19990310010540.A441@hosix.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=sdtB3X0nJg68CQEu X-Mailer: Mutt 0.95.1i Organization: NTUU "KPI" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Hello, I'm taking the courage :) to bring up the "static ARP on ethernet interfaces" issue again. The audit trail of kern/6432 gives sufficient background and I only want to refresh your memory by mentioning that all this is about making -arp parameter of ifconfig(8) work for ethernet interfaces. Attached are diffs for LINT, conf/options and netinet/if_ether.c made against 3.1-STABLE cvsupped few hours ago. The purpose of STATIC_ARP_HACK option is covered in the LINT diff. I tried to keep everything clean and straightforward. If someone could take time to review these diffs and comment on them while paying special attention to the correctness of updated if_ether.c I would be very grateful. -- Alexander Matey Kyiv, Ukraine --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_ether.c.diff" --- /sys/netinet/if_ether.c.orig Thu Mar 4 06:04:48 1999 +++ /sys/netinet/if_ether.c Wed Mar 10 00:37:48 1999 @@ -30,9 +30,9 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * @(#)if_ether.c 8.1 (Berkeley) 6/10/93 - * $Id: if_ether.c,v 1.52.2.1 1999/03/04 04:04:48 wpaul Exp $ + * $Id: if_ether.c,v 1.52 1999/01/19 23:17:03 fenner Exp $ */ /* * Ethernet address resolution protocol. @@ -41,8 +41,9 @@ */ #include "opt_inet.h" #include "opt_bdg.h" +#include "opt_static_arp_hack.h" #include #include #include @@ -284,8 +285,11 @@ register struct ether_header *eh; register struct ether_arp *ea; struct sockaddr sa; + if ((ac->ac_if.if_flags & IFF_NOARP) != 0) { + return; + } if ((m = m_gethdr(M_DONTWAIT, MT_DATA)) == NULL) return; m->m_len = sizeof(*ea); m->m_pkthdr.len = sizeof(*ea); @@ -362,8 +366,12 @@ sdl->sdl_family == AF_LINK && sdl->sdl_alen != 0) { bcopy(LLADDR(sdl), desten, sdl->sdl_alen); return 1; } + if ((ac->ac_if.if_flags & IFF_NOARP) != 0) { + m_freem(m); + return (0); + } /* * There is an arptab entry, but no ethernet address * response yet. Replace the held mbuf with this * latest one. @@ -407,8 +415,11 @@ splx(s); if (m == 0 || (m->m_flags & M_PKTHDR) == 0) panic("arpintr"); if (m->m_len >= sizeof(struct arphdr) && +#ifndef STATIC_ARP_HACK + (m->m_pkthdr.rcvif->if_flags & IFF_NOARP) == 0 && +#endif (ar = mtod(m, struct arphdr *)) && ntohs(ar->ar_hrd) == ARPHRD_ETHER && m->m_len >= sizeof(struct arphdr) + 2 * ar->ar_hln + 2 * ar->ar_pln) @@ -502,8 +513,13 @@ ea->arp_sha, ":", inet_ntoa(isaddr)); itaddr = myaddr; goto reply; } +#ifdef STATIC_ARP_HACK + if ((ac->ac_if.if_flags & IFF_NOARP) != 0) { + goto reply; + } +#endif la = arplookup(isaddr.s_addr, itaddr.s_addr == myaddr.s_addr, 0); if (la && (rt = la->la_rt) && (sdl = SDL(rt->rt_gateway))) { #ifndef BRIDGE /* the following is not an error when doing bridging */ if (rt->rt_ifp != &ac->ac_if) { --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="options.diff" --- /sys/conf/options.orig Mon Feb 8 21:05:55 1999 +++ /sys/conf/options Wed Mar 10 00:11:37 1999 @@ -67,8 +67,9 @@ SYSVSEM opt_sysvipc.h SYSVSHM opt_sysvipc.h UCONSOLE ICMP_BANDLIM +STATIC_ARP_HACK # POSIX kernel options P1003_1B opt_posix.h _KPOSIX_PRIORITY_SCHEDULING opt_posix.h --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="LINT.diff" --- /sys/i386/conf/LINT.orig Sun Feb 21 23:12:26 1999 +++ /sys/i386/conf/LINT Wed Mar 10 00:11:26 1999 @@ -481,8 +481,15 @@ # You can use IPFIREWALL and dummynet together with bridging. options DUMMYNET options BRIDGE +# STATIC_ARP_HACK enables sending responses to ARP who-has queries +# received on an ethernet interface with ARP disabled (see ifconfig(8) for +# info on -arp parameter). Default is to disable ARP completely on +# such interface. With ARP disabled internal ARP table should be setup +# manually with arp(8) before any routing daemons have been started. +options STATIC_ARP_HACK + # # ATM (HARP version) options # # ATM_CORE includes the base ATM functionality code. This must be included --sdtB3X0nJg68CQEu-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 15:27: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (ntu-kpi.kiev.ua [195.178.136.20]) by hub.freebsd.org (Postfix) with ESMTP id 15F7B14EBB for ; Tue, 9 Mar 1999 15:27:00 -0800 (PST) (envelope-from lx@hosix.ntu-kpi.kiev.ua) Received: from hosix.ntu-kpi.kiev.ua (IDENT:0@eth0.hosix.ntu-kpi.kiev.ua [10.100.0.6]) by relay1.ntu-kpi.kiev.ua (8.NYB/8.NYB) with ESMTP id BAA04399 for ; Wed, 10 Mar 1999 01:26:41 +0200 (EET) (envelope-from lx@hosix.ntu-kpi.kiev.ua) Received: from lx.hosix.ntu-kpi.kiev.ua (lx.hosix.ntu-kpi.kiev.ua [10.100.23.72]) by hosix.ntu-kpi.kiev.ua (1.2.3.4/hidden) with ESMTP id BAA02864 for ; Wed, 10 Mar 1999 01:26:40 +0200 (EET) Received: (from lx@localhost) by lx.hosix.ntu-kpi.kiev.ua (8.9.2/8.9.1) id BAA00588 for freebsd-hackers@freebsd.org; Wed, 10 Mar 1999 01:26:40 +0200 (EET) Date: Wed, 10 Mar 1999 01:26:40 +0200 From: Alexander Matey To: freebsd-hackers@freebsd.org Subject: Re: Static ARP again. kern/6432 revisited. Message-ID: <19990310012640.A545@hosix.ntu-kpi.kiev.ua> References: <19990310010540.A441@hosix.ntu-kpi.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990310010540.A441@hosix.ntu-kpi.kiev.ua>; from Alexander Matey on Wed, Mar 10, 1999 at 01:05:40AM +0200 Organization: NTUU "KPI" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Just a quick note about if_ether.c.diff - please ignore the change to $Id$ in first hunk - the rest of this diff is current as of revision 1.52.2.1 of if_ether.c. On Wed, Mar 10, 1999 at 01:05:40AM +0200, Alexander Matey wrote: > Hello, > > I'm taking the courage :) to bring up the "static ARP on ethernet > interfaces" issue again. The audit trail of kern/6432 gives sufficient > background and I only want to refresh your memory by mentioning that all > this is about making -arp parameter of ifconfig(8) work for ethernet > interfaces. > > Attached are diffs for LINT, conf/options and netinet/if_ether.c > made against 3.1-STABLE cvsupped few hours ago. > > The purpose of STATIC_ARP_HACK option is covered in the LINT diff. > I tried to keep everything clean and straightforward. > > If someone could take time to review these diffs and comment on them > while paying special attention to the correctness of updated if_ether.c > I would be very grateful. > [..] -- Alexander Matey Kyiv, Ukraine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 15:42:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 23F9414F7A; Tue, 9 Mar 1999 15:41:51 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA05375; Wed, 10 Mar 1999 10:11:08 +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: Date: Wed, 10 Mar 1999 10:11:07 +1030 (CST) From: "Daniel O'Connor" To: The Hermit Hacker Subject: Re: GGI Cc: yokota@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, Terry Lambert , "Daniel C. Sobral" , Mike Smith , Andrew Reilly , Doug Rabson Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Mar-99 The Hermit Hacker wrote: > Also, and correct me if I'm wrong, but looking at the FAQ, they don't > support 3Dfx/Voodoo2 stuff? I would have thought that those would have > been the first ones that they would have concentrated on, considering how > big they appear to be...? Well, a 3dfx card is a _bad_ 2D performer.. Thats why they work in conjunction with a normal 2D card.. Also a 3dfx card doesn't actually support that much of the OpenGL API, and for Mesa at least, once you wander off and do something that isn't possible in hardware, its forced to switch entirely to software which is slooooow. --- 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 Tue Mar 9 15:56:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id A5D8F14F1B for ; Tue, 9 Mar 1999 15:56:08 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id PAA86008; Tue, 9 Mar 1999 15:55:14 -0800 (PST) From: Archie Cobbs Message-Id: <199903092355.PAA86008@bubba.whistle.com> Subject: Re: Crash with ICMP bandwidth limiter. In-Reply-To: from Jaye Mathisen at "Mar 8, 99 08:23:26 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Tue, 9 Mar 1999 15:55:14 -0800 (PST) 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 Jaye Mathisen writes: > Not exactly sure what happened. I started getting a truckload of warnings > from syslog about ICMP responses, which was fine. > > Then I stopped the program that was creating them, and about 2 seconds > later, I got a panic. This is kindof a long shot, but try backing out rev. 134 of netinet/ip_icmp.c and see if that fixes it. If so, then it's probably a bug in the limiting stuff that is triggered by this change (which fixed kern/9723). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 16:43:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orcrist.mediacity.com (orcrist.mediacity.com [208.138.36.146]) by hub.freebsd.org (Postfix) with ESMTP id 0B1AF150C2 for ; Tue, 9 Mar 1999 16:43:08 -0800 (PST) (envelope-from gsutter@orcrist.mediacity.com) Received: (from gsutter@localhost) by orcrist.mediacity.com (8.8.8/8.8.8) id QAA17971 for freebsd-hackers@freebsd.org; Tue, 9 Mar 1999 16:42:59 -0800 (PST) (envelope-from gsutter) Date: Tue, 9 Mar 1999 16:42:59 -0800 From: Gregory Sutter To: freebsd-hackers@freebsd.org Subject: [ted@urbanite.com: DCE porting.....] Message-ID: <19990309164259.I1249@orcrist.mediacity.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Organization: Zer0 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note the fourth paragraph of the following message. I am not a kernel hacker by any means, and I don't know if Ted's information is current. I do know that threads support has been a problem for many different FreeBSD developers. As well as possibly addressing the message below, can someone provide a short status report on the threads support in -STABLE? TIA. Greg ----- Forwarded message from "Ted W. Larson" ----- Message-Id: <3.0.1.32.19990309133925.00bdddc4@giraffe.urbanite.com> Date: Tue, 09 Mar 1999 13:39:25 -0800 To: linux-dce-list@bu.edu From: "Ted W. Larson" Subject: DCE porting..... Sender: owner-linux-dce-list@bu.edu For a long time, I have been dreaming of an open source initiative for DCE. Let's face it....DCE is good technology, but not widely used because it isn't out there for free on all the platforms people want to develop applications on. When I saw the Linux port of Free DCE-RPC is was really excited. It is clear that the Free-DCE kit which was released into the public domain, was a porting nightmare to wade through, ..hehe...unless you were planning on building on AIX. Using a mixture of the original kit, and the Linux DCE kit, I have built running ports which work on both Solaris 2.6 for Sparc, and Solaris-X86 2.6 for Intel. There were some really tricky little porting bugs to get it going, but they both seem to work quite well now. I have been fiddling with an HP/UX build, but it seems unnecessary, because DCE-RPC comes bundled with the HP/UX core OS for free already. Also, I am very interested in porting to FreeBSD as well. The threads package is the big problem on FreeBSD. There seem to be seveal initiatives to get Linux-threads working on FreeBSD, which it seems would solve the problem. But, no easy solution to this right away. The threads package on FreeBSD 2.x is really ancient and doesn't support important things like pthread_cancel() ..ugh. Regardless, I have had them both working for a couple of weeks now, but haven't had a chance to bundle up the two ports, to release back to the public through a web page or something like that. Also, I would like to bundle up the binaries into a Solaris package so that people could just install it using pkgadd. I also still need to add comments to certain sections I rewrote in the threads-wrappers, so one can understand the Solaris platform differences from Linux. What I would REALLY like to do is take the Linux DCE kit as a starting point, and write an autoconf script to make it automatically recognize, and build for Linux, Solaris-X86, or Solaris-Sparc. Any help on this effort would be GREATLY appreciated. Not to cloud the water or anything, but I think if there were a stable Free-DCE kit, freely available to the world to use on most platforms, it would be compelling for lots of people to use it. ....heh...including myself...:-) Thanks, - Ted Larson ted@urbanite.com ----- End forwarded message ----- -- Gregory S. Sutter I got a Pentium II for my girlfriend. mailto:gsutter@pobox.com Good trade, eh? http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 16:48:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9941015044 for ; Tue, 9 Mar 1999 16:47:47 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA20540; Tue, 9 Mar 1999 16:47:06 -0800 Date: Tue, 9 Mar 1999 16:47:06 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: An Update on- 'Panic in FFS/4.0 as of yesterday - update' In-Reply-To: <199903030034.QAA59145@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've taken a kernel source as of of today, added your patches on top, used a CCD to build a 120GB disk partition (2 raid units), and have resumed testing with my stuff again. If that all passes reasonably well (so far so good- 32 processes, each writing 2GB files- getting a range of 15-25MB/s on the CCD)- what's the likelihood of getting it checked in? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 16:56: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 3547615019; Tue, 9 Mar 1999 16:56:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id QAA28222; Tue, 9 Mar 1999 16:55:40 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id QAA25874; Tue, 9 Mar 1999 16:55:39 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id RAA05504; Tue, 9 Mar 1999 17:55:37 -0700 Message-ID: <36E5C315.ACBDD93C@softweyr.com> Date: Tue, 09 Mar 1999 17:55:49 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "saenara@usa.net" Cc: "'freebsd-hardware@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: Re: PCI modem References: <01BE6A7A.A1CE2A70.saenara@usa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Saenara wrote: > > Can you please explain what shall I do to setup PCI modem under > FreeBSD 3.0. Break it up, encase it in cement, and throw it into the deepest ocean you can find? Most PCI modems are "WinModems" and are not supported under FreeBSD anything.anything. They are nasty little pieces of trash foisted on people who don't know better by hardware charlatans. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 17: 5:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id EED9615019 for ; Tue, 9 Mar 1999 17:04:48 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA50707; Tue, 9 Mar 1999 17:04:29 -0800 (PST) (envelope-from dillon) Date: Tue, 9 Mar 1999 17:04:29 -0800 (PST) From: Matthew Dillon Message-Id: <199903100104.RAA50707@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Update on- 'Panic in FFS/4.0 as of yesterday - update' References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I've taken a kernel source as of of today, added your patches on top, used :a CCD to build a 120GB disk partition (2 raid units), and have resumed :testing with my stuff again. : :If that all passes reasonably well (so far so good- 32 processes, each :writing 2GB files- getting a range of 15-25MB/s on the CCD)- what's the :likelihood of getting it checked in? : :-matt Well, I would hope 100% likelihood. The VFS/BIO/NFS patch is the only major bug-fix patch of mine that has not been committed into -4.x yet. The new 'VN' device for -4.x ( the current one is broken due to other VM changes ) has also not yet been comitted. Both are waiting for final approval/review. Core is being slow. I have no time frame for backporting the recent (last 30 days) worth of committs from -4.x to -3.x - that is up to core too as it currently stands. There is nothing I can do about it. I have a preliminary patch for the read/mmap/open deadlock too. -- http://www.backplane.com/FreeBSD4/ -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 17: 6:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C1CAB1507A for ; Tue, 9 Mar 1999 17:06:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA27828; Tue, 9 Mar 1999 17:04:14 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW27825; Wed Mar 10 01:04:11 1999 Message-ID: <36E5C507.7DE14518@whistle.com> Date: Tue, 09 Mar 1999 17:04:07 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: mjacob@feral.com Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: An Update on- 'Panic in FFS/4.0 as of yesterday - update' References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > I've taken a kernel source as of of today, added your patches on top, used > a CCD to build a 120GB disk partition (2 raid units), and have resumed > testing with my stuff again. > > If that all passes reasonably well (so far so good- 32 processes, each > writing 2GB files- getting a range of 15-25MB/s on the CCD)- what's the > likelihood of getting it checked in? > > -matt pretty good.. committers have been flooded but this hasn't been forgotten.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 17:26:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id CFC1015045 for ; Tue, 9 Mar 1999 17:26:45 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id RAA08108; Tue, 9 Mar 1999 17:26:36 -0800 (PST) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id RAA07616; Tue, 9 Mar 1999 17:26:26 -0800 (PST) Message-ID: <19990309172626.A7182@proxydev.inktomi.com> Date: Tue, 9 Mar 1999 17:26:26 -0800 From: John Plevyak To: dick@tar.com Cc: hackers@freebsd.org Subject: bug in linuxthreads for FreeBSD 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 I have been using the linuxthreads for FreeBSD port, and running it under high stress. It seems that there is a bug/race which triggers the ASSERT in queue.h. Essentially the problem is that when a thread goes into pthread_cond_timedwait (and hence pthread_cond_timedwait_relative) there is a race between the timeout wakeup and the signal wakeup. Here is the order of events which exhibits the bug: T1: thread A goes into pthread_cond_timedwait_relative and puts itself on the cond->c_waiting queue. T2: thread A wakes up from a timeout and blocks the restart signal T3: (context switch) thread B triggers the conditional variable, and send the signal T4: (context switch) thread A grabs the spinlock and tries to remove_from_queue() (which fails silently) T5: thread A goes into pthread_cond_timedwait_relative again as soon as it unblocks the restart it is awoken (NOTE: it is still on cond->c_waiting. T6: (another thread blocks on the condition variable, so that th->p_nextwaiting != NULL) T7: thread A tries to block on a mutex which sees that self->p_nextwaiting != NULL and asserts. The patch I am using unconditionally removes the thread from the queue. This does not prevent the thread from being woken up extaneously, but it does prevent the ASSERT and corruption of the p_nextwaiting lists. This looks like it may be a general problem with linuxthreads, and I am wondering if anyone else has seen it. Also, there is no 'lock prefix' before the xchg in _atomic_lock.S which will prevent the library from working correctly with SMP. john -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 22:53:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kyrnet.kg (ns.kyrnet.kg [195.254.160.9]) by hub.freebsd.org (Postfix) with ESMTP id 172CA1501B for ; Tue, 9 Mar 1999 22:52:39 -0800 (PST) (envelope-from fygrave@tigerteam.net) Received: from localhost by kyrnet.kg (8.9.3/8.9.1) with ESMTP id LAA07810; Wed, 10 Mar 1999 11:44:50 +0500 (GMT) X-Authentication-Warning: kyrnet.kg: fygrave owned process doing -bs Date: Wed, 10 Mar 1999 11:44:50 +0500 (GMT) From: CyberPsychotic X-Sender: fygrave@kyrnet.kg To: Bosko Milekic Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SOCK_RAW on BSD In-Reply-To: <001d01be6a79$cfbefd20$0100000a@jehovah.technokratis.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 ~ Actually, under Linux, one _also_ has to read from the datalink layer in ~ order to be able to get TCP and/or UDP datagrams. The difference is that ~ under Linux, one would create a socket of type SOCK_PACKET to be able to ~ consequently read from it. There are several disadvantages to SOCK_PACKET ~ (in comparison to libpcap and bpf, for instance) -- such as no kernel ~ buffering and/or filtering. ~ in theory yes, only SOCK_PACKET gives you access to datalink layer, and thus make it possible to read TCP/UDP/ICMP/* packs. But try that piece of code I had posted before. Specifying IPPROTO_RAW, for the type of socket you wouldn't get much, however specifying IPPROTO_IP you will be able to get all the sorts of broken packets (which kernel wasn't able to classify as udp/tcp/or icmp datagrams), going by analogue, specifying IPPROTO_TCP|UDP|ICMP you will be able to monitor these sorts of datagrams. What's good about this thing, that you will not have to open several devices on multihomed machine. However the incompatibility with BSD stack (and probably others, I wasn't able to test it on hpux/sunos4.X/irix machines) makes this thing good only, if you are writing Linux-only packages. Also this might be problem of compatibility with recent kernel releases. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 23:17:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 6B10C14F96 for ; Tue, 9 Mar 1999 23:17:37 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id SAA12846 for freebsd-hackers@FreeBSD.ORG; Wed, 10 Mar 1999 18:17:17 +1100 (EST) Message-ID: <19990310181717.M11634@rf900.physics.usyd.edu.au> Date: Wed, 10 Mar 1999 18:17:17 +1100 From: David Dawes To: freebsd-hackers@FreeBSD.ORG Subject: Re: GGI References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug Rabson on Tue, Mar 09, 1999 at 08:03:15PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 09, 1999 at 08:03:15PM +0000, Doug Rabson wrote: >On Tue, 9 Mar 1999, The Hermit Hacker wrote: > >> On Tue, 9 Mar 1999, Doug Rabson wrote: >> >> > On Tue, 9 Mar 1999, Andrew Reilly wrote: >> > >> > > On Sun, Mar 07, 1999 at 09:03:57PM -0800, Mike Smith wrote: >> > > > Since the voodoo2 is a 3d card, and X is exclusively 2d, I can't quite >> > > > see how "supporting" this card actually achieves anything. >> > > >> > > Isn't the PEX extension some sort of 3D thing? I never hear >> > > anyone talk about it, so perhaps there's something wrong with >> > > it, but couldn't some sort of 3D acceleration be built around >> > > it? >> > >> > PEX is several years away from the cutting edge of graphics. I'm not sure >> > that it even supports texture mapping. A better base for working on 3D >> > acceleration is Mesa which is exactly what the guys at Precision Insight >> > (www.precisioninsight.com) are doing to create a decent modern 3D solution >> > for Linux and BSD. >> >> Most intriguing...just went through the site, and its another project >> "supported by RedHat", and "binary-only"...is anyone from FreeBSD, Inc >> approaching them from the *BSD camp? > >I approached them (on my own behalf) to ask them about BSD support and >they are keen. They really are open source people but are attempting to >work around the NDA mentality which some of the chip vendors have. Already >they have donated the source for some of their servers (NeoMagic and Glint >I think) to XFree86 as the vendors relaxed their NDAs. For the record, they donated the NeoMagic source. SuSE sponsored the Glint (3Dlabs) driver work, with help from Elsa. They have a binary-only driver for the Intel i740. They don't have permission to release that source though, and I don't know if there will ever be *BSD binaries of that (Red Hat is funding the work). When XFree86 4.0 is available, that won't be a problem because the *BSD X server will be able to load Linux-compiled driver modules. Precision Insight is planning to release as much of their work as possible as "open source". Their track record is good so far, convincing NeoMagic to allow them to release the source for that driver, and playing a role in both SGI's release of GLX as open source and in getting the Mesa licence converted to an XFree86-friendly licence. Their initial integration of GLX, Mesa and XFree86 was committed to the XFree86-4.0 code base recently. The plan is that hw 3D support and a direct rendering infrastructure will come later. >> The project itself looks promising...hopefully we'll see *BSD binaries >> eventually...:) > >I think we will be able to use this stuff with a minimum effort (porting >the small kernel drivers). Yes, I expect so. FreeBSD is my OS of choice, and I certainly want to see that as much XFree86-related work as possible is usable with FreeBSD. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 9 23:50:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 56C4B150B6 for ; Tue, 9 Mar 1999 23:50:21 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id IAA15148 for hackers@freebsd.org; Wed, 10 Mar 1999 08:50:10 +0100 (MET) (envelope-from kuku) Date: Wed, 10 Mar 1999 08:50:10 +0100 (MET) From: Christoph Kukulies Message-Id: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE> To: hackers@freebsd.org Subject: netscape situation Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could anyone tell me which netscape to choose that does not bail out under FreeBSD 3.1 when clicking on a mail link or when one wants to launch a mail? Also I have the impression that the linux netscape 4.51 isn't that good either (java pages seem to have problems - have to manifest this still though). -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 0: 3:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DA7614DE2 for ; Wed, 10 Mar 1999 00:03:29 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA15218; Wed, 10 Mar 1999 09:03:19 +0100 (MET) (envelope-from kuku) Message-ID: <19990310090318.A15203@gil.physik.rwth-aachen.de> Date: Wed, 10 Mar 1999 09:03:18 +0100 From: Christoph Kukulies To: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: netscape situation References: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91 In-Reply-To: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE>; from Christoph Kukulies on Wed, Mar 10, 1999 at 08:50:10AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 10, 1999 at 08:50:10AM +0100, Christoph Kukulies wrote: > > Could anyone tell me which netscape to choose that does not bail > out under FreeBSD 3.1 when clicking on a mail link or > when one wants to launch a mail? > > Also I have the impression that the linux netscape 4.51 isn't > that good either (java pages seem to have problems - have to manifest > this still though). Following up my own post: Can netscape be built from sources? I mean, the source are freely available, aren't they? So if one wants to set out to find the point where it crashes one could build a debuggable version? Did anyone go though this already? > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 2:28:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 6A6C315015 for ; Wed, 10 Mar 1999 02:28:34 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id UAA22329; Wed, 10 Mar 1999 20:59:08 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA19240; Wed, 10 Mar 1999 20:57:53 +0930 Date: Wed, 10 Mar 1999 20:57:53 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Christoph Kukulies Cc: hackers@freebsd.org Subject: Re: netscape situation In-Reply-To: <19990310090318.A15203@gil.physik.rwth-aachen.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Mar 1999, Christoph Kukulies wrote: > Can netscape be built from sources? I mean, the source are freely > available, aren't they? No and no. The source code to an early version of 5.0 was what became the Mozilla project, which is still very much a developing effort and not at all stable last I checked. No source code to 4.x or earlier browsers is freely available. I don't use Netscape for mail - I've found it quite stable except for the DNS resoluytion problems (which I've solved by running a local copy of squid and passing off the DNS resolution and caching to that). However, I know lots of other people seem to be experiencing the same problem as you are. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 2:28:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 55D5C150F6 for ; Wed, 10 Mar 1999 02:28:54 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA13989; Wed, 10 Mar 1999 19:28:38 +0900 (JST) Message-ID: <36E64631.C49D25A8@newsguy.com> Date: Wed, 10 Mar 1999 19:15:13 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: CyberPsychotic Cc: Bosko Milekic , freebsd-hackers@FreeBSD.ORG Subject: Re: SOCK_RAW on BSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CyberPsychotic wrote: > > on multihomed machine. However the incompatibility with BSD stack (and > probably others, I wasn't able to test it on hpux/sunos4.X/irix machines) SunOS 4.x is BSD. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "FreeBSD is Yoda, Linux is Luke Skywalker." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 3:40:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 9DA6D14FF4 for ; Wed, 10 Mar 1999 03:40:23 -0800 (PST) (envelope-from pete@bowtie.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id MAA01573 for hackers@freebsd.org; Wed, 10 Mar 1999 12:40:05 +0100 (MET) Received: from bowtie.nl (sartre.intra.bowtie.nl [192.168.4.5]) by bowtie.nl (8.8.8/8.8.8) with ESMTP id MAA17907 for ; Wed, 10 Mar 1999 12:35:18 +0100 (CET) (envelope-from pete@bowtie.nl) Message-ID: <36E658FE.F60CAC31@bowtie.nl> Date: Wed, 10 Mar 1999 12:35:26 +0100 From: Peter Weijmarshausen X-Mailer: Mozilla 4.5 [en] (X11; I; IRIX 6.3 IP32) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: using dd to make backup of disk? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I have a question concerning the use of dd to make a backup of a harddisk onto an *identical* backup disk using FreeBSD 2.2.8: If the disk copied contains a live filesystem, which is modified by user processes all the time, what can there be said about the dd copy? I tried this and the only problem fsck detected was that the clean flag isn't set, other than that there were no problems. Before you all start mailing me about how stupid it is to use dd as a backup mechanism: I use this in order to maintain an instant bootable backup. So if the primary disk crashes I unplug it, reboot the system and I have a working system again. Please respond to my email address because I am not a member of hackers Thanks in advance for any help, Pete -- Peter Weymarshausen BowTie Technology Email: P.Weymarshausen@bowtie.nl WWW & Databases To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 5:48:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D66A150F9 for ; Wed, 10 Mar 1999 05:48:22 -0800 (PST) (envelope-from terry@ppsl.demon.co.uk) Received: from [158.152.16.214] (helo=yeoman.ppsl.co.uk) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 10KjLA-0000va-0A; Wed, 10 Mar 1999 13:48:04 +0000 To: "Jim Flowers" , Subject: Re: Tunnel loopback References: <000d01be6a7e$39343960$abd396ce@ivy.ezo.net> From: Terry Glanfield Date: 10 Mar 1999 13:47:31 +0000 In-Reply-To: "Jim Flowers"'s message of "Tue, 9 Mar 1999 17:43:16 -0500" Message-Id: Lines: 33 X-Mailer: Gnus v5.6.44/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jim Flowers" writes: > There is a basic problem with your strategy. SKIP is unidirectional and the > inbound packets will have to be received on the configured interface to be > authenticated. Exactly. Along with the rule for the internal interface: pass in quick on ed0 to tun0 all I have a rule on the external interface to redirect SKIP packets to the tunnel: pass in quick on ed1 to tun0 proto skip all Similarly for UDP port 1640. I've tested this and it works admirably (except for the duplicate packets mentioned earlier). The object is to move SKIP from its position closest to the wire to a point before NAT occurs. Then, so long as the SKIP packets have a properly rewritten source address and are not modified by NAT, all of the problems you mention are addressed. Nomadic SKIP hosts on the Internet should also be possible although I've not tried this yet. Now, if only I could stop the duplicate packets bouncing around the tunnel... > Were you able to get the FreeBSD Skip-1.0 port to compile on 3.1? Apparently it won't work with LKM and needs a KLM rewrite. Regards, Terry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 6:31:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat196.27.mpoweredpc.net [142.177.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 4199515128 for ; Wed, 10 Mar 1999 06:31:07 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA11605; Wed, 10 Mar 1999 10:30:25 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 10 Mar 1999 10:30:25 -0400 (AST) From: The Hermit Hacker To: David Dawes Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: GGI In-Reply-To: <19990310181717.M11634@rf900.physics.usyd.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Mar 1999, David Dawes wrote: > For the record, they donated the NeoMagic source. SuSE sponsored the > Glint (3Dlabs) driver work, with help from Elsa. They have a binary-only > driver for the Intel i740. They don't have permission to release that > source though, and I don't know if there will ever be *BSD binaries of > that (Red Hat is funding the work). So...has FreeBSD, Inc jumped in and offered to co-sponsor the project? If not, why not? For that matter, *does* FreeBSD, Inc do anything like that? 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 Wed Mar 10 6:52: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id AE11C150B2 for ; Wed, 10 Mar 1999 06:51:52 -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 PAA26059 for hackers@FreeBSD.ORG; Wed, 10 Mar 1999 15:51:34 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8CFAE8837; Wed, 10 Mar 1999 15:42:22 +0100 (CET) Date: Wed, 10 Mar 1999 15:42:22 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: netscape situation Message-ID: <19990310154222.A9746@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE>; from Christoph Kukulies on Wed, Mar 10, 1999 at 08:50:10AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Christoph Kukulies: > Could anyone tell me which netscape to choose that does not bail > out under FreeBSD 3.1 when clicking on a mail link or > when one wants to launch a mail? The "navigator" is not able to deal with mailto: at all. You have to use the "communicator" for that. I'm able to send & receive email with Communicator 4.5 just fine. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 7:15:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 8082A150B2 for ; Wed, 10 Mar 1999 07:15:37 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id KAA01521; Wed, 10 Mar 1999 10:24:41 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199903101524.KAA01521@cc942873-a.ewndsr1.nj.home.com> Subject: Re: using dd to make backup of disk? In-Reply-To: <36E658FE.F60CAC31@bowtie.nl> from Peter Weijmarshausen at "Mar 10, 99 12:35:26 pm" To: pete@bowtie.nl (Peter Weijmarshausen) Date: Wed, 10 Mar 1999 10:24:41 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Weijmarshausen wrote, > Before you all start mailing me about how stupid it > is to use dd as a backup mechanism: I use this in > order to maintain an instant bootable backup. > So if the primary disk crashes I unplug it, reboot the > system and I have a working system again. Why is, # cd backupfs # dump -0af - origfs | restore -rf - Any less 'instant?' And 'dump' is meant to handle live filesystems. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 7:25:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id AC4B414D0B for ; Wed, 10 Mar 1999 07:25:34 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (crossd@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id KAA21929; Wed, 10 Mar 1999 10:24:58 -0500 (EST) Message-Id: <199903101524.KAA21929@cs.rpi.edu> To: Ollivier Robert Cc: hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: netscape situation In-Reply-To: Message from Ollivier Robert of "Wed, 10 Mar 1999 15:42:22 +0100." <19990310154222.A9746@keltia.freenix.fr> Date: Wed, 10 Mar 1999 10:24:55 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also use Netscape on FreeBSD 3.1 with few problems. However I have noticed all version of Netscape sometimes have problems handling mail. I have been in 2 totally seperate environments on Solaris where clicking for mail would lock up Netscape totally. Same goes for other platforms, but I have only used them in one environment, so I can not say definitely that it was netscape or the environment. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 7:32:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CD19615130; Wed, 10 Mar 1999 07:32:25 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id QAA55471; Wed, 10 Mar 1999 16:31:59 +0100 (CET) (envelope-from des) To: jim@reptiles.org (Jim Mercer) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: problems with the ep (ethernet) driver? 2.2.[67] References: From: Dag-Erling Smorgrav Date: 10 Mar 1999 16:31:59 +0100 In-Reply-To: jim@reptiles.org's message of "Tue, 23 Feb 1999 15:55:44 -0500 (EST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jim@reptiles.org (Jim Mercer) writes: > since the swap, gated (running on both machines) seems to lose contact > and the interior machine (and/or the core) decides that it can't pass > packets over the route. ...and the interface is stuck with the OACTIVE bit set. It's a known bug in the ep driver. The only known workaround is to run "ifconfig ep0 up" when the symptoms appear. 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 Wed Mar 10 7:53:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id 53DC0150B2 for ; Wed, 10 Mar 1999 07:53:47 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from crocus (c3-1d196.neo.rr.com [24.93.233.196]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id KAA10682; Wed, 10 Mar 1999 10:53:08 -0500 (EST) Message-ID: <004301be6b0e$2efd77f0$23b197ce@crocus.ezo.net> From: "Jim Flowers" To: , "Terry Glanfield" Subject: Re: Tunnel loopback Date: Wed, 10 Mar 1999 10:53:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An interesting approach but I'm having difficulty understanding your description. See below. -----Original Message----- From: Terry Glanfield To: Jim Flowers ; freebsd-hackers@freebsd.org Date: Wednesday, March 10, 1999 8:47 AM Subject: Re: Tunnel loopback > pass in quick on ed0 to tun0 all This rule looks as if ipfw will accept all inbound packets received on any interface and exit thereby passing the packets up the stack. I am unfamiliar with the "quick" and "on" keywords; they don't appear in the ipfw man page. Also tun0 is not a legal choice for the dst argument which requires some form of IP address or keywords "not" and "any". Is this a special version of ipfw? Quick and on don't work on mine > >I have a rule on the external interface to redirect SKIP packets to >the tunnel: > > pass in quick on ed1 to tun0 proto skip all Again, I don't know the "quick" and "on" keywords but the "pass" (alias to allow) action is only for matching. It doesn't do any destination address or port redirection as do pipe, divert, tee and fwd. Won't the "all" keyword (matches every ip packet) override the proto skip specification? > >Similarly for UDP port 1640. I've tested this and it works admirably >(except for the duplicate packets mentioned earlier). The object is >to move SKIP from its position closest to the wire to a point before >NAT occurs. Then, so long as the SKIP packets have a properly >rewritten source address and are not modified by NAT, all of the >problems you mention are addressed. Rewriting the source address isn't of much consequence as the far-end skiphost will restore the original when it unencapsulates the packet. The one exception to this is using a public address in place of a private address as some ISP's are discarding packets that have private addresses in the source. >Nomadic SKIP hosts on the >Internet should also be possible although I've not tried this yet. The main problem with a nomadic host is that at the nomad end the original packet source and the skiphost have the same IP number and, by definition, it is unknown in advance. Not a problem for a simple host-to-host network but definitely a routing problem for a single-interface nomadic server in a host-to-network tunnel topology. You have to figure out how to route return packets to the skiphost for processing and then route the same packets (now encrypted but with the same destination address) to the nomad (far-end) skiphost. > >Now, if only I could stop the duplicate packets bouncing around the >tunnel... > >> Were you able to get the FreeBSD Skip-1.0 port to compile on 3.1? > >Apparently it won't work with LKM and needs a KLM rewrite. You might want to check with Archie Cobbs to see if this is going to happen. I'm still using 2.2.8 which compiles OK. I'm beginning to think SKIP may be reaching end-of-life status with the vanishing of the mailing list and archive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 8:34:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post-20.mail.demon.net (post-20.mail.demon.net [194.217.242.27]) by hub.freebsd.org (Postfix) with ESMTP id 1E79D14C30 for ; Wed, 10 Mar 1999 08:34:38 -0800 (PST) (envelope-from terry@ppsl.demon.co.uk) Received: from [158.152.16.214] (helo=yeoman.ppsl.co.uk) by post-20.mail.demon.net with esmtp (Exim 2.10 #2) id 10Klvu-0005Rf-0K; Wed, 10 Mar 1999 16:34:11 +0000 To: "Jim Flowers" , freebsd-hackers@freebsd.org Subject: Re: Tunnel loopback References: <004301be6b0e$2efd77f0$23b197ce@crocus.ezo.net> From: Terry Glanfield Date: 10 Mar 1999 16:32:19 +0000 In-Reply-To: "Jim Flowers"'s message of "Wed, 10 Mar 1999 10:53:45 -0500" Message-Id: Lines: 45 X-Mailer: Gnus v5.6.44/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jim Flowers" writes: > An interesting approach but I'm having difficulty understanding your > description. See below. I'm using IPFilter, not ipfw. From the man page: to causes the packet to be moved to the outbound queue on the specified interface. This can be used to circumvent kernel routing decisions, and even to bypass the rest of the kernel processing of the packet (if applied to an inbound rule). It is thus possible to construct a firewall that behaves transparently, like a filtering hub or switch, rather than a router. The fastroute key- word is a synonym for this option. I'm simply moving all packets arriving on the internal interface and SKIP packets on the external interface to the tunnel interface. > The main problem with a nomadic host is that at the nomad end the original > packet source and the skiphost have the same IP number and, by definition, > it is unknown in advance. Not a problem for a simple host-to-host network > but definitely a routing problem for a single-interface nomadic server in a > host-to-network tunnel topology. You have to figure out how to route return > packets to the skiphost for processing and then route the same packets (now > encrypted but with the same destination address) to the nomad (far-end) > skiphost. The idea is that *all* packets destined for the outside pass through SKIP. I'm assuming that SKIP will keep state information about nomadic hosts that have made inbound connections and extract/encrypt what it needs while leaving the rest to pass through untouched. Like a said though, I haven't played with "skiphost -a *" yet. > I'm beginning to think SKIP may be reaching end-of-life status with the > vanishing of the mailing list and archive. I noticed that the archive was unaccessible. Was there an announcement that I missed? Regards, Terry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 8:47: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles229.castles.com [208.214.165.229]) by hub.freebsd.org (Postfix) with ESMTP id 7C61815110 for ; Wed, 10 Mar 1999 08:47:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id IAA04096; Wed, 10 Mar 1999 08:41:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903101641.IAA04096@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: The Hermit Hacker Cc: David Dawes , freebsd-hackers@FreeBSD.ORG Subject: Re: GGI In-reply-to: Your message of "Wed, 10 Mar 1999 10:30:25 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Mar 1999 08:41:05 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 10 Mar 1999, David Dawes wrote: > > > For the record, they donated the NeoMagic source. SuSE sponsored the > > Glint (3Dlabs) driver work, with help from Elsa. They have a binary-only > > driver for the Intel i740. They don't have permission to release that > > source though, and I don't know if there will ever be *BSD binaries of > > that (Red Hat is funding the work). > > So...has FreeBSD, Inc jumped in and offered to co-sponsor the > project? If not, why not? Because FreeBSD Inc. doesn't have that kind of money. When it does spend on development, it needs to keep it closely tied to FreeBSD's goals, and you have to admit that 3D graphics aren't really a high-riority server feature. 8) > For that matter, *does* FreeBSD, Inc do anything like that? Yes, when funds are available. -- \\ 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 Mar 10 9: 0: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id 262A81549A for ; Wed, 10 Mar 1999 09:00:05 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id KAA11118; Wed, 10 Mar 1999 10:59:44 -0600 (CST) (envelope-from dick) Date: Wed, 10 Mar 1999 10:59:44 -0600 From: "Richard Seaman, Jr." To: John Plevyak Cc: hackers@freebsd.org Subject: Re: bug in linuxthreads for FreeBSD Message-ID: <19990310105944.F4440@tar.com> References: <19990309172626.A7182@proxydev.inktomi.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=0ntfKIWw70PvrIHh X-Mailer: Mutt 0.95.1i In-Reply-To: <19990309172626.A7182@proxydev.inktomi.com>; from John Plevyak on Tue, Mar 09, 1999 at 05:26:26PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii On Tue, Mar 09, 1999 at 05:26:26PM -0800, John Plevyak wrote: > I have been using the linuxthreads for FreeBSD port, and running > it under high stress. Glad to see it. Also glad you can only find *one* bug :) > It seems that there is a bug/race which triggers the ASSERT in queue.h. After looking at the code and your description, I would agree that there is a race bug, though I'm not at all convinced your description is completely accurate. I've attached a patch, and I'd be interested if it solves the wait queue corruption problem. [snip] > The patch I am using unconditionally removes the thread from the > queue. This does not prevent the thread from being woken up > extaneously, but it does prevent the ASSERT and corruption of > the p_nextwaiting lists. It might be possible to eliminate, or at least narrow the window for the "extraneous" wakeup. It would require reworking the linux threads code more. OTOH, it could just be left as is. Here's what Butenhof's "Programming with POSIX Threads" says about the pthread_cond_* wait functions: "It is important that you test the predicate after locking the mutex and before waiting on the condition variable. If a thread signals a condition variable while no threads are waiting, nothing happens. If some other thread calls pthread_cond_wait right after that, it will just keep waiting...." and, "It is equally important that you test the predicate again when the thread wakes up. You should always wait for a condition variable in a loop, to protect against program errors, multiprocessor races, and spurious wakeups." > This looks like it may be a general problem with linuxthreads, > and I am wondering if anyone else has seen it. You're the first to report it to me. > Also, there is no 'lock prefix' before the xchg in _atomic_lock.S which > will prevent the library from working correctly with SMP. I'd like to know more about this. According to the Intel documents I have, the xchg op code implies a 'lock prefix'. You can add the 'lock prefix', but its redundant. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 --0ntfKIWw70PvrIHh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="condvar.diff" *** condvar.c.orig Wed Mar 10 10:12:49 1999 --- condvar.c Wed Mar 10 10:13:37 1999 *************** *** 152,157 **** --- 152,158 ---- #endif /* Otherwise, return normally */ + remove_from_queue(&cond->c_waiting, self); release(&cond->c_spinlock); pthread_mutex_lock(mutex); return 0; --0ntfKIWw70PvrIHh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 9:26:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 4D3C115528 for ; Wed, 10 Mar 1999 09:26:44 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id TAA04414 for ; Wed, 10 Mar 1999 19:26:25 +0200 (SAST) Received: by citadel via recvmail id 4411; Wed Mar 10 19:25:50 1999 Message-ID: <36E6AB40.742D64BB@cdsec.com> Date: Wed, 10 Mar 1999 19:26:24 +0200 From: Graham Wheeler X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: C++ global constructors and shared libraries Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks I have just changed some C++ code libraries from static to shared. I now find that some global objects declared in these libraries are no longer having their constructors called. If I move the object declarations into the main.cc file, then they work fine. However, I don't want to do this for all the objects - we are talking about 15 libraries here consisting of hundreds of .cc files that would have to be checked. Is there some command line argument that I need for this, or is it a problem with g++/ld on FreeBSD generally? I am using FreeBSD 2.2.7 at present. TIA gram -- 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 Wed Mar 10 10:19:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (Postfix) with ESMTP id F38E314EE8 for ; Wed, 10 Mar 1999 10:19:12 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.9.2/8.9.2) id MAA54775 for freebsd-hackers@FreeBSD.ORG; Wed, 10 Mar 1999 12:18:51 -0600 (CST) (envelope-from greg) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 10 Mar 1999 12:18:51 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-hackers@FreeBSD.ORG Subject: SMP Woes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still struggling to get this last batch of SMP systems working correctly. Originally I was having Fatal Trap errors under high IO load on my Tyan dual CPU systems but somewhere close to 3.1 Release level, the problems cleared up and they seem to be running fine. Unfortunately, around the same build level my Quad Xeon box started up with the Fatal Traps ??? It's starting to drive me crazy !!! As far as I can tell, 3.0 Release worked fine on all the SMP systems here. Somewhere between 3.0 Release and 3.1 Release something changed that's causing these failures. I went up to 4.0 current yesterday to see if Matt's recent changes had any effect, but they didn't. I only get the failures when running in SMP mode on the system. Single CPU works fine. The failure is easily reproducable by running a couple cpio's or even a make world (I have to go to single CPU to upgrade). The Xeon is a SC450NX with a SCSI backplane. I've tried both the on-board NCR and Adaptec controllers. The DDB output is always the same, except the CPU ID changes. Again, it works at 3.0 Release, so I don't think it's a hardware failure. Attached is the DDB output and trace from a terminal server window. I'm more than willing to try any suggestions and can provide access to crash dumps or the system. Thanks. Fatal trap 12: page fault while in kernel mode mp_lock = 03000002; cpuid = 3; lapic.id = 02000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf020ec9f stack pointer = 0x10:0xfe5a3c34 frame pointer = 0x10:0xfe5a3c58 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 245 (cpio) interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) db> trace generic_bzero(f3283f80,0,f4801900,fe5a3c90,fe5a3c98) at generic_bzero+0xf zalloci(f3283f80,f488bb00,f4801900,6f802,fe541180) at zalloci+0x29 getnewvnode(1,f33f0200,f3266200,fe5a3cfc,100) at getnewvnode+0x2f8 ffs_vget(f33f0200,6f802,fe5a3d7c,ff779d00,fe5a3edc) at ffs_vget+0xa5 ufs_lookup(fe5a3dd4,fe5a3de8,f016f6d4,fe5a3dd4,fe553c1d) at ufs_lookup+0x936 ufs_vnoperate(fe5a3dd4,fe553c1d,ff779d00,fe5a3edc,0) at ufs_vnoperate+0x15 vfs_cache_lookup(fe5a3e30,fe5a3e40,f0171ae9,fe5a3e30,fe53b640) at vfs_cache_lookup+0x248 ufs_vnoperate(fe5a3e30,fe53b640,fe5a3edc,fe5a3eb8,0) at ufs_vnoperate+0x15 lookup(fe5a3eb8,fe541180,f0250848,fe541180,1) at lookup+0x2c1 namei(fe5a3eb8,fe541180,f0250848,0,8057000) at namei+0x133 lstat(fe541180,fe5a3f94,8057000,ffffffff,3) at lstat+0x44 syscall(2f,efbf002f,3,ffffffff,efbfdc70) at syscall+0x187 Xint0x80_syscall() at Xint0x80_syscall+0x4c db> Greg Rowe US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 10:27:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id ED39115182 for ; Wed, 10 Mar 1999 10:27:31 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA09671; Wed, 10 Mar 1999 19:26:56 +0100 (CET) (envelope-from des) To: Mike Smith Cc: David Dawes , freebsd-hackers@FreeBSD.ORG Subject: Re: GGI References: <199903090151.RAA02086@dingo.cdrom.com> From: Dag-Erling Smorgrav Date: 10 Mar 1999 19:26:55 +0100 In-Reply-To: Mike Smith's message of "Mon, 08 Mar 1999 17:51:21 -0800" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > It should be very simple; basically all that's missing right now is the > ability to get the linear framebuffer address information from the VESA > BIOS back into user-space. You should have no trouble mapping the > video aperture. On cards which do not support it, LFB can be simulated by trapping page faults and, if the fault address is within a specific range, setting the frame buffer window origin correctly and mapping it into memory so that the instruction which caused the fault, once restarted, will succeed. It's a hack and it's probably slow as hell, but it works. 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 Wed Mar 10 10:47:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak.texar.com (pak.texar.com [207.112.49.1]) by hub.freebsd.org (Postfix) with ESMTP id 0FE7015204 for ; Wed, 10 Mar 1999 10:47:42 -0800 (PST) (envelope-from dseg@pak.texar.com) Received: (from dseg@localhost) by pak.texar.com (8.8.8/8.8.3) id NAA26721; Wed, 10 Mar 1999 13:47:27 -0500 (EST) Date: Wed, 10 Mar 1999 13:47:26 -0500 (EST) From: Dan Seguin To: freebsd-hackers@freebsd.org Subject: KLD 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 all, I've got two questions: 1. Is there a way of creating more than one syscall in the same KLD? Is syscall_register() all one needs to do? If not, what kind of hand waving is necessary with SYSCALL_MODULE, DECLARE_MODULE, SYSINIT, DATASET? 2. Is it possible to replace a syscall with a new one but still call the old one? Thanks for your help. Dan Seguin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 10:53:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay02.indigo.ie (relay02.indigo.ie [194.125.133.226]) by hub.freebsd.org (Postfix) with SMTP id 7E36014E22 for ; Wed, 10 Mar 1999 10:53:05 -0800 (PST) (envelope-from nsmart@kira.team400.ie) Received: (qmail 14792 messnum 46199 invoked from network[194.125.148.182/ts04-052.dublin.indigo.ie]); 10 Mar 1999 18:52:46 -0000 Received: from ts04-052.dublin.indigo.ie (HELO kira.team400.ie) (194.125.148.182) by relay02.indigo.ie (qp 14792) with SMTP; 10 Mar 1999 18:52:46 -0000 Message-ID: <36E6BFE4.951172E3@kira.team400.ie> Date: Wed, 10 Mar 1999 18:54:28 +0000 From: Niall Smart Organization: Trinity Commerce X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Graham Wheeler Cc: hackers@freebsd.org Subject: Re: C++ global constructors and shared libraries References: <36E6AB40.742D64BB@cdsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Graham Wheeler wrote: > > Hi folks > > I have just changed some C++ code libraries from static to shared. > I now find that some global objects declared in these libraries > are no longer having their constructors called. If I move the object niall% g++ -v cc -v gcc version 2.7.2.1 niall% g++ -c -fpic libfoo.cc niall% g++ -shared libfoo.o -o libfoo.so niall% g++ main.cc -Wl,-R,. -L. -lfoo niall% ./a.out foo niall% cat libfoo.cc #include struct foo { foo() { printf("%s\n", "foo"); } }; foo f; niall% cat main.cc int main() { } niall% uname -a FreeBSD niall.boi.ie 3.1-STABLE FreeBSD 3.1-STABLE #1: Sat Feb 27 15:18:27 GMT 1999 niall@niall.boi.ie:/usr/src/sys/compile/NIALL i386 Regards, Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 10:59:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id E78AF15253 for ; Wed, 10 Mar 1999 10:59:14 -0800 (PST) (envelope-from babolo@aaz.links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.1a/8.8.8) id WAA25960; Wed, 10 Mar 1999 22:03:49 +0300 (MSK) (envelope-from babolo) Message-Id: <199903101903.WAA25960@aaz.links.ru> Subject: Re: using dd to make backup of disk? In-Reply-To: <199903101524.KAA01521@cc942873-a.ewndsr1.nj.home.com> from "Crist J. Clark" at "Mar 10, 99 10:24:41 am" To: cjclark@home.com Date: Wed, 10 Mar 1999 22:03:49 +0300 (MSK) Cc: pete@bowtie.nl, hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crist J. Clark writes: > Peter Weijmarshausen wrote, > > Before you all start mailing me about how stupid it > > is to use dd as a backup mechanism: I use this in > > order to maintain an instant bootable backup. > > So if the primary disk crashes I unplug it, reboot the > > system and I have a working system again. > > Why is, > > # cd backupfs > # dump -0af - origfs | restore -rf - > > Any less 'instant?' And 'dump' is meant to handle live filesystems. dd is much faster. boot codes and disk labels are not copied by dump|restore only ufs (and ext2fs) can be copied by dump|restore -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 11: 6:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id E268615197 for ; Wed, 10 Mar 1999 11:06:20 -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 LAA05432; Wed, 10 Mar 1999 11:06:00 -0800 (PST) Message-Id: <199903101906.LAA05432@implode.root.com> To: greg@uswest.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes In-reply-to: Your message of "Wed, 10 Mar 1999 12:18:51 CST." From: David Greenman Reply-To: dg@root.com Date: Wed, 10 Mar 1999 11:06:00 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are at least two things that are strange in the following. First, there is no call to bzero() from zalloci() (or in zlock(), _zalloc(), and zunlock(), which are inlined). Second, the parameters to generic_bzero() indicate that 0 bytes are to be zeroed. It's also strange that the address of the first arg is the same as in the zalloci call, which might indicate that the first structure element of vm_zone, which is the simplelock, is being zeroed. It might be interesting to see if the addresses of the generic_bzero() and simple_lock() functions are similar (such as different by one bit or something). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project > Attached is the DDB output and trace from a terminal server window. I'm >more than willing to try any suggestions and can provide access to crash dumps >or the system. Thanks. > >Fatal trap 12: page fault while in kernel mode >mp_lock = 03000002; cpuid = 3; lapic.id = 02000000 >fault virtual address = 0x0 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xf020ec9f >stack pointer = 0x10:0xfe5a3c34 >frame pointer = 0x10:0xfe5a3c58 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 245 (cpio) >interrupt mask = net tty bio cam <- SMP: XXX >kernel: type 12 trap, code=0 >Stopped at generic_bzero+0xf: repe stosl %es:(%edi) >db> trace >generic_bzero(f3283f80,0,f4801900,fe5a3c90,fe5a3c98) at generic_bzero+0xf >zalloci(f3283f80,f488bb00,f4801900,6f802,fe541180) at zalloci+0x29 >getnewvnode(1,f33f0200,f3266200,fe5a3cfc,100) at getnewvnode+0x2f8 >ffs_vget(f33f0200,6f802,fe5a3d7c,ff779d00,fe5a3edc) at ffs_vget+0xa5 >ufs_lookup(fe5a3dd4,fe5a3de8,f016f6d4,fe5a3dd4,fe553c1d) at ufs_lookup+0x936 >ufs_vnoperate(fe5a3dd4,fe553c1d,ff779d00,fe5a3edc,0) at ufs_vnoperate+0x15 >vfs_cache_lookup(fe5a3e30,fe5a3e40,f0171ae9,fe5a3e30,fe53b640) at >vfs_cache_lookup+0x248 >ufs_vnoperate(fe5a3e30,fe53b640,fe5a3edc,fe5a3eb8,0) at ufs_vnoperate+0x15 >lookup(fe5a3eb8,fe541180,f0250848,fe541180,1) at lookup+0x2c1 >namei(fe5a3eb8,fe541180,f0250848,0,8057000) at namei+0x133 >lstat(fe541180,fe5a3f94,8057000,ffffffff,3) at lstat+0x44 >syscall(2f,efbf002f,3,ffffffff,efbfdc70) at syscall+0x187 >Xint0x80_syscall() at Xint0x80_syscall+0x4c >db> > > > >Greg Rowe US WEST - Internet Service Operations > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 11:21:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id ADBA31547C for ; Wed, 10 Mar 1999 11:21:33 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id LAA08202; Wed, 10 Mar 1999 11:21:24 -0800 (PST) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id LAA16727; Wed, 10 Mar 1999 11:21:15 -0800 (PST) Message-ID: <19990310112115.B16206@proxydev.inktomi.com> Date: Wed, 10 Mar 1999 11:21:15 -0800 From: John Plevyak To: "Richard Seaman, Jr." , John Plevyak Cc: hackers@freebsd.org Subject: Re: bug in linuxthreads for FreeBSD References: <19990309172626.A7182@proxydev.inktomi.com> <19990310105944.F4440@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990310105944.F4440@tar.com>; from Richard Seaman, Jr. on Wed, Mar 10, 1999 at 10:59:44AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 10, 1999 at 10:59:44AM -0600, Richard Seaman, Jr. wrote: > On Tue, Mar 09, 1999 at 05:26:26PM -0800, John Plevyak wrote: > > > I have been using the linuxthreads for FreeBSD port, and running > > it under high stress. > > Glad to see it. Also glad you can only find *one* bug :) Actually, the p_nextwaiting list has a tendency to circularize as well, but I am still working on that :) > > > Also, there is no 'lock prefix' before the xchg in _atomic_lock.S which > > will prevent the library from working correctly with SMP. > > I'd like to know more about this. According to the Intel documents > I have, the xchg op code implies a 'lock prefix'. You can add the > 'lock prefix', but its redundant. Your right, that's what I get for assuming any consistency in the x86 ISA. > > -- > Richard Seaman, Jr. email: dick@tar.com > 5182 N. Maple Lane phone: 414-367-5450 > Chenequa WI 53058 fax: 414-367-5852 > *** condvar.c.orig Wed Mar 10 10:12:49 1999 > --- condvar.c Wed Mar 10 10:13:37 1999 > *************** > *** 152,157 **** > --- 152,158 ---- > > #endif > /* Otherwise, return normally */ > + remove_from_queue(&cond->c_waiting, self); > release(&cond->c_spinlock); > pthread_mutex_lock(mutex); > return 0; Testing now. I'll keep you informed. -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 11:23:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 686E015505 for ; Wed, 10 Mar 1999 11:23:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA57293; Wed, 10 Mar 1999 11:22:54 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 11:22:54 -0800 (PST) From: Matthew Dillon Message-Id: <199903101922.LAA57293@apollo.backplane.com> To: "Crist J. Clark" Cc: pete@bowtie.nl (Peter Weijmarshausen), hackers@FreeBSD.ORG Subject: Re: using dd to make backup of disk? References: <199903101524.KAA01521@cc942873-a.ewndsr1.nj.home.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :# cd backupfs :# dump -0af - origfs | restore -rf - : :Any less 'instant?' And 'dump' is meant to handle live filesystems. :-- :Crist J. Clark cjclark@home.com Mmm... more like dump has been hacked to attempt to deal with live filesystem. If the filesystem isn't mostly idle, there's a good chance that dump will fail to properly dump it. And, in fact, that has happened to me several times. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 11:31: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 39ADB14A2F for ; Wed, 10 Mar 1999 11:31:02 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id OAA01900; Wed, 10 Mar 1999 14:30:31 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199903101930.OAA01900@cc942873-a.ewndsr1.nj.home.com> Subject: Re: using dd to make backup of disk? In-Reply-To: <199903101903.WAA25960@aaz.links.ru> from "Aleksandr A.Babaylov" at "Mar 10, 99 10:03:49 pm" To: babolo@links.ru (Aleksandr A.Babaylov) Date: Wed, 10 Mar 1999 14:30:31 -0500 (EST) Cc: cjclark@home.com, pete@bowtie.nl, hackers@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aleksandr A.Babaylov wrote, > Crist J. Clark writes: > > Peter Weijmarshausen wrote, > > > Before you all start mailing me about how stupid it > > > is to use dd as a backup mechanism: I use this in > > > order to maintain an instant bootable backup. > > > So if the primary disk crashes I unplug it, reboot the > > > system and I have a working system again. > > > > Why is, > > > > # cd backupfs > > # dump -0af - origfs | restore -rf - > > > > Any less 'instant?' And 'dump' is meant to handle live filesystems. > dd is much faster. > boot codes and disk labels are not copied by dump|restore > only ufs (and ext2fs) can be copied by dump|restore That idea kind of scares me. You are assuming the two disks involved have identical geometries and characteristics when copying a disklabel. It just seems to me that dump|restore is a much safer alternative. Write the bootblocks and disklabel the backup manually once, then backup filesystems periodically. How often would the bootsectors and label change? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 12: 6:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gauntlet.petech.ac.za (gauntlet.petech.ac.za [196.37.151.34]) by hub.freebsd.org (Postfix) with ESMTP id 1F4F4151D6 for ; Wed, 10 Mar 1999 12:05:59 -0800 (PST) (envelope-from 9846817@ml.petech.ac.za) Received: by gauntlet.petech.ac.za; id WAA10378; Wed, 10 Mar 1999 22:05:40 +0200 (SAT) Received: from ed.petech.ac.za(192.96.7.1) by gauntlet.petech.ac.za via smap (4.0) id xma010329; Wed, 10 Mar 99 22:05:35 +0200 Received: from ml.petech.ac.za (ml.petech.ac.za [192.96.7.37]) by ed.petech.ac.za (8.7.5/8.6.10) with SMTP id EAA06439 for ; Thu, 11 Mar 1999 04:21:50 +0200 Received: from PETNET-Message_Server by ml.petech.ac.za with Novell_GroupWise; Wed, 10 Mar 1999 22:05:44 +0200 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 10 Mar 1999 16:20:55 +0200 From: JDM BEZUIDENHOUT <9846817@ml.petech.ac.za> To: FREEBSD-HACKERS@freebsd.org Subject: subscribe FREEBSD-HACKERS Mime-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe FREEBSD-HACKERS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 12:17:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pak.texar.com (pak.texar.com [207.112.49.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D3A81531A for ; Wed, 10 Mar 1999 12:17:30 -0800 (PST) (envelope-from dseg@pak.texar.com) Received: (from dseg@localhost) by pak.texar.com (8.8.8/8.8.3) id PAA26886; Wed, 10 Mar 1999 15:17:15 -0500 (EST) Date: Wed, 10 Mar 1999 15:17:15 -0500 (EST) From: Dan Seguin To: freebsd-hackers@FreeBSD.org Subject: KLD 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 all, I've got two questions: 1. Is there a way of creating more than one syscall in the same KLD? Is syscall_register() all one needs to do? If not, what kind of hand waving is necessary with SYSCALL_MODULE, DECLARE_MODULE, SYSINIT, DATASET? 2. Is it possible to replace a syscall with a new one but still call the old one? Thanks for your help. Dan Seguin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 13:43:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B74E215223 for ; Wed, 10 Mar 1999 13:43:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA71403; Wed, 10 Mar 1999 13:43:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: The Hermit Hacker Cc: David Dawes , freebsd-hackers@FreeBSD.ORG Subject: Re: GGI In-reply-to: Your message of "Wed, 10 Mar 1999 10:30:25 -0400." Date: Wed, 10 Mar 1999 13:43:07 -0800 Message-ID: <71400.921102187@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So...has FreeBSD, Inc jumped in and offered to co-sponsor the > project? If not, why not? Too much buck, too little bang. > For that matter, *does* FreeBSD, Inc do anything like that? We do occasionally, and I've already talked to the Precision Insight folks, but they want more $$$ than we can justify spending on making FreeBSD a better desktop solution. That's not our bread and butter, and the money would be far better spent on something which makes us a better *server* solution. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14: 9:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 8675014E22 for ; Wed, 10 Mar 1999 14:09:38 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA28406; Wed, 10 Mar 1999 22:10:16 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 10 Mar 1999 22:10:16 +0000 (GMT) From: Doug Rabson To: Dan Seguin Cc: freebsd-hackers@freebsd.org Subject: Re: KLD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Mar 1999, Dan Seguin wrote: > > Hi all, > > > I've got two questions: > > 1. Is there a way of creating more than one syscall in the same KLD? Is > syscall_register() all one needs to do? If not, what kind of hand waving > is necessary with SYSCALL_MODULE, DECLARE_MODULE, SYSINIT, DATASET? Just have more than one SYSCALL_MODULE statement. > > 2. Is it possible to replace a syscall with a new one but still call the > old one? The old contents of the syscall table are saved in the struct syscall_module_data in the old_sysent field. If you declare a syscall with: SYSCALL_MODULE(foo, off, &my_sysent, 0, 0); then the old sysent is in foo_syscall_mod.old_sysent. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14:12:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 3E22E14BD0 for ; Wed, 10 Mar 1999 14:12:27 -0800 (PST) (envelope-from terry@ppsl.demon.co.uk) Received: from [158.152.16.214] (helo=yeoman.ppsl.co.uk) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 10KrCz-0004ck-0A; Wed, 10 Mar 1999 22:12:09 +0000 To: julian@whistle.com (Julian Elischer), freebsd-hackers@freebsd.org Subject: Re: Tunnel loopback References: <9903091652.AA04146@ppsl.demon.co.uk> <36E57226.15FB7483@whistle.com> From: Terry Glanfield Date: 10 Mar 1999 22:11:46 +0000 In-Reply-To: julian@whistle.com's message of "9 Mar 99 19:10:30 GMT" Message-Id: Lines: 17 X-Mailer: Gnus v5.6.44/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG julian@whistle.com (Julian Elischer) writes: > Terry Glanfield wrote: > > I've been trying to use a FreeBSD (3.0-RELEASE and 3.1-RELEASE) tunnel > > device (/dev/tunN) to push packets back onto the IP stack[1] with some > > success. > > You might find that using ipfw and divert sockets is a much more natural > fit to this problem. Indeed it was. I now have outbound packets pushed into tun0 then diverted out and inbound SKIP packets diverted and shoved into tun0. Works a treat - cheers Julian. Regards, Terry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14:16:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-01.cdsnet.net (mail-01.cdsnet.net [206.107.16.35]) by hub.freebsd.org (Postfix) with SMTP id 07A66152FE for ; Wed, 10 Mar 1999 14:16:07 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: (qmail 16732 invoked from network); 10 Mar 1999 22:15:49 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail.cdsnet.net with SMTP; 10 Mar 1999 22:15:49 -0000 Date: Wed, 10 Mar 1999 14:15:38 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Anybody using the 4 port Znyx card? 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 just about to order one, but wanted to check first. It's not listed specifically in the release notes for 3.1, but I suspect it's a DEC chipset based card (tulip?) and am hoping it just shows up as de0, de1, de2, de3, etc. THanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14:39:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 4B8471516A for ; Wed, 10 Mar 1999 14:39:23 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.9.2/8.9.2) id QAA55379; Wed, 10 Mar 1999 16:38:28 -0600 (CST) (envelope-from greg) 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: <199903101906.LAA05432@implode.root.com> Date: Wed, 10 Mar 1999 16:38:28 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: David Greenman Subject: Re: SMP Woes Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, I built a kernel with debugging and had one of the guys here take a look through the crash dump. First, is the new "Fatal Trap" DDB output and then his comments on what he saw. Anything else we should try ?? Greg On 10-Mar-99 David Greenman wrote: > There are at least two things that are strange in the following. First, > there is no call to bzero() from zalloci() (or in zlock(), _zalloc(), and > zunlock(), which are inlined). Second, the parameters to generic_bzero() > indicate that 0 bytes are to be zeroed. It's also strange that the address > of the first arg is the same as in the zalloci call, which might indicate > that the first structure element of vm_zone, which is the simplelock, is > being zeroed. It might be interesting to see if the addresses of the > generic_bzero() and simple_lock() functions are similar (such as different > by one bit or something). Fatal trap 12: page fault while in kernel mode mp_lock = 03000002; cpuid = 3; lapic.id = 02000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf020ec9f stack pointer = 0x10:0xfe5d2c34 frame pointer = 0x10:0xfe5d2c58 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 243 (cpio) interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at generic_bzero+0xf: repe stosl %es:(%edi) db> trace generic_bzero(f3283f80,0,f47f7000,fe5d2c90,fe5d2c98) at generic_bzero+0xf zalloci(f3283f80,f4880100,f47f7000,6f7f9,fe540ec0) at zalloci+0x29 getnewvnode(1,f33f0400,f3266200,fe5d2cfc,100) at getnewvnode+0x2f8 ffs_vget(f33f0400,6f7f9,fe5d2d7c,ff77d700,fe5d2edc) at ffs_vget+0xa5 ufs_lookup(fe5d2dd4,fe5d2de8,f016f6d4,fe5d2dd4,fe553021) at ufs_lookup+0x936 ufs_vnoperate(fe5d2dd4,fe553021,ff77d700,fe5d2edc,0) at ufs_vnoperate+0x15 vfs_cache_lookup(fe5d2e30,fe5d2e40,f0171ae9,fe5d2e30,fe53b640) at vfs_cache_lookup+0x248 ufs_vnoperate(fe5d2e30,fe53b640,fe5d2edc,fe5d2eb8,0) at ufs_vnoperate+0x15 lookup(fe5d2eb8,fe540ec0,f0250848,fe540ec0,1) at lookup+0x2c1 namei(fe5d2eb8,fe540ec0,f0250848,0,8057000) at namei+0x133 lstat(fe540ec0,fe5d2f94,8057000,ffffffff,3) at lstat+0x44 syscall(2f,efbf002f,3,ffffffff,efbfdc70) at syscall+0x187 Xint0x80_syscall() at Xint0x80_syscall+0x4c db> ******************************************************************************** Kgdb gives us a bit more info: (kgdb) bt ....snip.... #10 0xf020ec9f in generic_bzero () #11 0xf01f1869 in zalloci (z=0xf3283f80) at ../../vm/vm_zone.h:....snip.... (ki5 ....snip....gdb) frame 11 #11 0xf01f1869 in zalloci (z=0xf3283f80) at ../../vm/vm_zone.h:85 85 return _zget(z); (kgdb) print _zget $6 = {void *(struct vm_zone *)} 0xf01f18d4 <_zget> (kgdb) print generic_bzero $7 = {} 0xf020ec90 So, it doesn't look like a 1-bit off error.... Because zget/zalloc is an inline function, I can't seem to get gdb to print simple_lock or simple_unlock. -Chris Greg Rowe US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14:47:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id C3F4E1535C; Wed, 10 Mar 1999 14:47:15 -0800 (PST) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id RAA03486; Wed, 10 Mar 1999 17:46:57 -0500 (EST) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 10 Mar 1999 17:47:53 -0500 (EST) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: freebsd-hackers@freebsd.org, jkh@freebsd.org Subject: ccd driver problems with > 2GB segments, +fix Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've found, and corrected, a serious problem with the ccd driver with regards to large segments. The bugs were discovered while developing our NetMAX system, under FreeBSD 2.2.x. The problems still exist in 3.x, and are easily repeatable. Creating a ccd with a segment that is greater than 2048 MB bytes in size will cause a kernel panic. Fix: The ccd driver has a variable "bcount" that is a long: it needs to be a u_long. And, a 64 bit int is shifted into a 32 bit int in ccdbuffer(): the 32 bit int must changed to be a 64 bit int. This second change has already been made in NetBSD (somebody else figured it out), where the ccd driver originated from. It was rather tricky to find: the math involving block numbers and ccd segment size had to work our just right, which generally meant that I had to create thousands (or tens of thousands) of files before the kernel would hang. But once I found that block, it was infinitely repeatable. Please, don't ignore this one. I've sent patches before, and made PRs, and they've just ended up in a black hole. I've got more patches to FreeBSD, but I feel reluctant to submit them, because nobody cares to either review them or commit them. Here's the patch to 3.1's /sys/dev/ccd/ccd.c, followed by a sequence of commands to generate a panic using the original ccd code: *** ccd.c.orig Thu Feb 25 23:07:51 1999 --- ccd.c Tue Mar 9 21:11:01 1999 *************** *** 196,204 **** static void ccdintr __P((struct ccd_softc *, struct buf *)); static int ccdinit __P((struct ccddevice *, char **, struct proc *)); static int ccdlookup __P((char *, struct proc *p, struct vnode **)); static void ccdbuffer __P((struct ccdbuf **ret, struct ccd_softc *, ! struct buf *, daddr_t, caddr_t, long)); static void ccdgetdisklabel __P((dev_t)); static void ccdmakedisklabel __P((struct ccd_softc *)); static int ccdlock __P((struct ccd_softc *)); static void ccdunlock __P((struct ccd_softc *)); --- 196,204 ---- static void ccdintr __P((struct ccd_softc *, struct buf *)); static int ccdinit __P((struct ccddevice *, char **, struct proc *)); static int ccdlookup __P((char *, struct proc *p, struct vnode **)); static void ccdbuffer __P((struct ccdbuf **ret, struct ccd_softc *, ! struct buf *, daddr_t, caddr_t, u_long)); static void ccdgetdisklabel __P((dev_t)); static void ccdmakedisklabel __P((struct ccd_softc *)); static int ccdlock __P((struct ccd_softc *)); static void ccdunlock __P((struct ccd_softc *)); *************** *** 764,772 **** ccdstart(cs, bp) register struct ccd_softc *cs; register struct buf *bp; { ! register long bcount, rcount; struct ccdbuf *cbp[4]; /* XXX! : 2 reads and 2 writes for RAID 4/5 */ caddr_t addr; daddr_t bn; --- 764,772 ---- ccdstart(cs, bp) register struct ccd_softc *cs; register struct buf *bp; { ! register u_long bcount, rcount; struct ccdbuf *cbp[4]; /* XXX! : 2 reads and 2 writes for RAID 4/5 */ caddr_t addr; daddr_t bn; *************** *** 819,831 **** register struct ccd_softc *cs; struct buf *bp; daddr_t bn; caddr_t addr; ! long bcount; { register struct ccdcinfo *ci, *ci2 = NULL; /* XXX */ register struct ccdbuf *cbp; register daddr_t cbn, cboff; #ifdef DEBUG if (ccddebug & CCDB_IO) printf("ccdbuffer(%x, %x, %d, %x, %d)\n", --- 819,832 ---- register struct ccd_softc *cs; struct buf *bp; daddr_t bn; caddr_t addr; ! u_long bcount; { register struct ccdcinfo *ci, *ci2 = NULL; /* XXX */ register struct ccdbuf *cbp; register daddr_t cbn, cboff; + register off_t cbc; #ifdef DEBUG if (ccddebug & CCDB_IO) printf("ccdbuffer(%x, %x, %d, %x, %d)\n", *************** *** 902,914 **** cbp->cb_buf.b_vp = ci->ci_vp; LIST_INIT(&cbp->cb_buf.b_dep); cbp->cb_buf.b_resid = 0; if (cs->sc_ileave == 0) ! cbp->cb_buf.b_bcount = dbtob(ci->ci_size - cbn); else ! cbp->cb_buf.b_bcount = dbtob(cs->sc_ileave - cboff); ! if (cbp->cb_buf.b_bcount > bcount) ! cbp->cb_buf.b_bcount = bcount; cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; /* --- 903,914 ---- cbp->cb_buf.b_vp = ci->ci_vp; LIST_INIT(&cbp->cb_buf.b_dep); cbp->cb_buf.b_resid = 0; if (cs->sc_ileave == 0) ! cbc = dbtob((off_t)(ci->ci_size - cbn)); else ! cbc = dbtob((off_t)(cs->sc_ileave - cboff)); ! cbp->cb_buf.b_bcount = (cbc < bcount) ? cbc : bcount; cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; /* How To Repeat (using a vnode instead of a disk slice): 1) create a vnode that we can use as a ccd: dd if=/dev/zero of=/var/tmp/XXX bs=1m count=2049 2) configure the vnode and label it: vnconfig -c -s labels /dev/vn0 /var/tmp/XXX disklabel -w -B vn0 auto 3) edit the disklabel to set "c" to type "4.2BSD" disklabel -e vn0 4) config this vnode as a ccd: ccdconfig -c ccd0 0 0 /dev/vn0c PANIC... With the patches above, the ccdconfig will not cause a panic, and the ccd should work as expected. -------------------------------------------------------------------- Mark J. Taylor Networking Research Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (734) 668-2567 Ann Arbor, MI 48108 FAX (734) 668-8780 http://www.cybernet.com/ http://www.netmax.com/ -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 14:52: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 88DFC15171 for ; Wed, 10 Mar 1999 14:52:06 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA08625; Wed, 10 Mar 1999 17:51:19 -0500 (EST) Date: Wed, 10 Mar 1999 17:51:19 -0500 (EST) From: Daniel Eischen Message-Id: <199903102251.RAA08625@pcnet1.pcnet.com> To: hackers@FreeBSD.ORG, mrcpu@internetcds.com Subject: Re: Anybody using the 4 port Znyx card? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm just about to order one, but wanted to check first. It's not listed > specifically in the release notes for 3.1, but I suspect it's a DEC > chipset based card (tulip?) and am hoping it just shows up as de0, de1, > de2, de3, etc. Probing for devices on PCI bus 1: de0 rev 34 int a irq 10 on pci1:4:0 de0: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:95:e0:31:20 de1 rev 34 int a irq 12 on pci1:5:0 de1: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de1: address 00:c0:95:e0:31:21 de2 rev 34 int a irq 9 on pci1:6:0 de2: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de2: address 00:c0:95:e0:31:22 de3 rev 34 int a irq 14 on pci1:7:0 pcibus_ihandler_attach: counting pci irq14's as clk0 irqs de3: ZNYX ZX34X 21140A [10-100Mb/s] pass 2.2 de3: address 00:c0:95:e0:31:2 Machine is running FreeBSD 2.2.7-STABLE from before 2.2.8-RELEASE. System is working flawlessly, running IPFW, NATD, DHCP server, X-windows, etc. The next time I'll have to reboot is probably when I upgrade it to 3.1-stable. 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 Wed Mar 10 16: 6:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 2124015157 for ; Wed, 10 Mar 1999 16:06:20 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA00825; Wed, 10 Mar 1999 16:56:54 -0700 (MST) Date: Wed, 10 Mar 1999 16:56:54 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199903102356.QAA00825@narnia.plutotech.com> To: Andrzej Bialecki Cc: hackers@FreeBSD.org Subject: Re: FreeBSD and ThinkPad X-Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you wrote: > > I still experience total freezes when accessing sio0. The same goes for > 'pnpinfo' - machine freezes completely, and only hard reboot helps. Under DOS or Win9X, run: PS2 SERA enable PS2 SERA 1 The serial port should work correctly under FreeBSD after that. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 16:32:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 909ED15060 for ; Wed, 10 Mar 1999 16:31:59 -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 QAA13664; Wed, 10 Mar 1999 16:31:39 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id QAA56123; Wed, 10 Mar 1999 16:31:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 10 Mar 1999 16:31:38 -0800 (PST) Message-Id: <199903110031.QAA56123@vashon.polstra.com> To: sheldonh@iafrica.com Subject: Re: ppp.h in contrib/libpcap and contrib/tcpdump In-Reply-To: <72492.920494856@axl.noc.iafrica.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <72492.920494856@axl.noc.iafrica.com>, Sheldon Hearn wrote: > > Hi folks, > > While trawling my buildworld output for warnings, I noticed that we have > two identical copies of ppp.h in contrib/libpcap and contrib/tcpdump. > > If I were to try to get world to use only one ppp.h, where would I put > that single file and would I wasting time in the light of historic holy > wars? I don't know of any holy wars on this particular topic. But since both of these files are in the contrib tree, I think it's best to leave them alone. We generally try to leave the contrib stuff as pristine as possible. 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 Mar 10 16:44:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (Postfix) with ESMTP id 9021514FD8 for ; Wed, 10 Mar 1999 16:44:47 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA21357; Thu, 11 Mar 1999 01:52:52 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 11 Mar 1999 01:52:51 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Justin T. Gibbs" Cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad In-Reply-To: <199903102356.QAA00825@narnia.plutotech.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 Wed, 10 Mar 1999, Justin T. Gibbs wrote: > In article you wrote: > > > > I still experience total freezes when accessing sio0. The same goes for > > 'pnpinfo' - machine freezes completely, and only hard reboot helps. > > Under DOS or Win9X, run: > > PS2 SERA enable > PS2 SERA 1 > > The serial port should work correctly under FreeBSD after that. Ah.. Ok, thanks, I'll try this. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 16:51:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 2FC2B14EEF for ; Wed, 10 Mar 1999 16:51:21 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id LAA15704; Thu, 11 Mar 1999 11:50:50 +1100 (EST) Message-ID: <19990311115050.E15533@rf900.physics.usyd.edu.au> Date: Thu, 11 Mar 1999 11:50:50 +1100 From: David Dawes To: Mike Smith Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: GGI References: <19990307152541.O4858@rf900.physics.usyd.edu.au> <199903090151.RAA02086@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903090151.RAA02086@dingo.cdrom.com>; from Mike Smith on Mon, Mar 08, 1999 at 05:51:21PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 08, 1999 at 05:51:21PM -0800, Mike Smith wrote: >> Speaking of which (the Linux fb driver, not GGI), we're just adding a >> driver to XFree86 4.0 that can use the Linux fb driver. It is useful >> from our point of view for getting initial unaccelerated support for >> otherwise unsupported video cards. I had a feeling that something >> similar could be done for FreeBSD (using the VESA support in -current). >> Is that right? If so, is anyone interested in doing it? > >It should be very simple; basically all that's missing right now is the >ability to get the linear framebuffer address information from the VESA >BIOS back into user-space. You should have no trouble mapping the >video aperture. > >Would you want an interface for page-flipping etc. as well? Any design >proposals that would make life optimal for you? Linear fb access is preferred, although we do have a more general way of handling banked framebuffers in 4.0. In the first instance I'm looking for something fairly basic that sets a graphics mode and maps the linear framebuffer. We'd probably need information about the framebuffer layout too (pitch, pixel size/format), and a way of reading/writing the colourmap. Unfortunately I don't have much time to spend on this myself at the moment. Is anyone else here interested in looking into it? BTW, I notice that the kernel's VESA option can't be used with SMP. Is this restriction likely to go away? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 16:57:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep01-svc.tin.it (mta01-acc.tin.it [212.216.176.32]) by hub.freebsd.org (Postfix) with ESMTP id AF7A41507E for ; Wed, 10 Mar 1999 16:56:40 -0800 (PST) (envelope-from paipai@box4.tin.it) Received: from harlock ([212.216.234.148]) by fep01-svc.tin.it (InterMail v4.0 201-221-105) with SMTP id <19990311005620.RIMA2097.fep01-svc@harlock> for ; Thu, 11 Mar 1999 01:56:20 +0100 From: "Paolo Di Francesco" To: hackers@FreeBSD.ORG Date: Thu, 11 Mar 1999 01:05:57 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: where is the kernel? X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990311005620.RIMA2097.fep01-svc@harlock> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I want to install/play/compile the last version of the kernel. I want to download the 4.0 version (snapshot) but I don't find it. I don't want to use CVS, only to download the kernel packages, unpack them and putting them somewhere, then compile them. Can I use an arbitrary directory to compile the kernel? Ciao Ciao Paolo Di Francesco _ ->B<- All Recycled Bytes Message ... ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 17: 2:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (Postfix) with SMTP id 9613D1516A for ; Wed, 10 Mar 1999 17:02:05 -0800 (PST) (envelope-from wayne@crb.crb-web.com) Received: (qmail 8066 invoked by uid 1001); 11 Mar 1999 01:48:09 -0000 Date: Wed, 10 Mar 1999 20:48:09 -0500 (EST) From: Wayne Cuddy Reply-To: wayne@crb-web.com To: FreeBSD Hackers List Subject: new to driver coding Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been reading any information I can find, which is very little, on writing unix device drivers. Specifically I would like information on FreeBSD;) I really want to start simple by writing a character driver that is not attached to a REAL device but just holds on to some memory and allows me to writing some bytes in (write()) and read them back (read()). I don't think this will be very difficult but I need some detailed information specific to FreeBDS on what header files I need to include and how to build my driver as part of the kernel. What directory should I build my driver in? What entry point will the kernel call when the system boots so I can print a pretty little string from my driver showing a sample initialization. I am kinda in the dark here to specifics of this so ALL help is greatly appreciated. Thanks, Wayne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 17: 2:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id A954315190 for ; Wed, 10 Mar 1999 17:02:43 -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 CAA23215 for hackers@FreeBSD.ORG; Thu, 11 Mar 1999 02:02:24 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id AA0188837; Thu, 11 Mar 1999 01:09:47 +0100 (CET) Date: Thu, 11 Mar 1999 01:09:47 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Anybody using the 4 port Znyx card? Message-ID: <19990311010947.A18990@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Jaye Mathisen on Wed, Mar 10, 1999 at 02:15:38PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jaye Mathisen: > I'm just about to order one, but wanted to check first. It's not listed > specifically in the release notes for 3.1, but I suspect it's a DEC > chipset based card (tulip?) and am hoping it just shows up as de0, de1, > de2, de3, etc. They should work fine AFAIK with the 'de' driver. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 17: 8:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 711DA15193 for ; Wed, 10 Mar 1999 17:08:39 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id SAA01544; Wed, 10 Mar 1999 18:08:18 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903110108.SAA01544@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: "Justin T. Gibbs" , hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad In-reply-to: Your message of "Thu, 11 Mar 1999 01:52:51 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Mar 1999 17:59:16 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Under DOS or Win9X, run: >> PS2 SERA 1 Oops. Should be PS2 SERA add 1 -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 17:30:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pacman.redwoodsoft.com (redwoodsoft.com [207.181.199.182]) by hub.freebsd.org (Postfix) with SMTP id 9DD1815190 for ; Wed, 10 Mar 1999 17:30:16 -0800 (PST) (envelope-from dnelson@redwoodsoft.com) Received: (qmail 2357 invoked from network); 11 Mar 1999 01:29:57 -0000 Received: from localhost.redwoodsoft.com (127.0.0.1) by localhost.redwoodsoft.com with SMTP; 11 Mar 1999 01:29:57 -0000 Date: Wed, 10 Mar 1999 17:29:57 -0800 (PST) From: Dru Nelson To: freebsd-hackers@freebsd.org Subject: Re: using dd to make backup of disk? 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've used dump and dd. Both work great. dd can be slow with large disks, and dump deals with varied disk sizes better. dump requires a little extra work for the disk label. Dru Nelson Redwood City, California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 17:38:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (Postfix) with ESMTP id 7349F14C3B for ; Wed, 10 Mar 1999 17:38:09 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.9.1a/8.9.1) id MAA15882; Thu, 11 Mar 1999 12:37:34 +1100 (EST) Message-ID: <19990311123734.G15533@rf900.physics.usyd.edu.au> Date: Thu, 11 Mar 1999 12:37:34 +1100 From: David Dawes To: Mike Smith Cc: hackers@freebsd.org Subject: Re: Setting MTRRs from the X server References: <19990307153350.P4858@rf900.physics.usyd.edu.au> <199903090149.RAA02067@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=C7zPtVaVf+AK4Oqc X-Mailer: Mutt 0.93.2i In-Reply-To: <199903090149.RAA02067@dingo.cdrom.com>; from Mike Smith on Mon, Mar 08, 1999 at 05:49:47PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii On Mon, Mar 08, 1999 at 05:49:47PM -0800, Mike Smith wrote: >> For XFree86 4.0, we really need to be able to have the X server request >> specific MTRR settings for different parts of a video card's physical >> memory address space. While turning WC on for the framebuffer is a big >> performance boost, a more critical issue is being able to make sure that >> WC is turned off for areas that are used for memory mapped I/O. We've >> found that some BIOSs enable WC in areas that our drivers want to use >> for MMIO. One example is the 0xb0000-0xbffff range. >> >> So what I'm looking for is an interface that our X server can use to >> request MTRR settings. An interface for this is present in the Linux >> 2.2.x kernel (and we recently added code to use it), although it doesn't >> currently allow changing the settings for the low 1MB of address space >> (but I'm told that will be added at some point). > >For want of anything better, I'd guess that emulating the Linux >interface would probably be the way to go. Is there a spec for it >somewhere that can be read? I've included a description of the current Linux interface below, and the header from the 2.2.2 kernel. I can send a copy of the code we have that uses it to anyone who is interested. They have a /proc/mtrr device that can be accessed via read()/write() and ioctl(). When using the ioctl interface, the changes are undone when the device is closed. Apparently the ioctl interface for removing mtrr entries isn't implemented in current Linux kernels, so our code uses the ASCII interface for that. Also, they may be replacing /proc/mtrr with /dev/cpu/mtrr at some point. Providing a similar ioctl interface (using whatever device naming is consistent with "the BSD way") would be fine for our needs, providing that it can handle the MTRRs for the low 1MB of memory. David --C7zPtVaVf+AK4Oqc Content-Type: text/plain Content-Disposition: attachment; filename="mtrr.txt" MTRR (Memory Type Range Register) control 2 May 1998 Richard Gooch On Intel Pentium Pro/Pentium II systems the Memory Type Range Registers (MTRRs) may be used to control processor access to memory ranges. This is most useful when you have a video (VGA) card on a PCI or AGP bus. Enabling write-combining allows bus write transfers to be combined into a larger transfer before bursting over the PCI/AGP bus. This can increase performance of image write operations 2.5 times or more. The CONFIG_MTRR option creates a /proc/mtrr file which may be used to manipulate your MTRRs. Typically the X server should use this. This should have a reasonably generic interface so that similar control registers on other processors can be easily supported. There are two interfaces to /proc/mtrr: one is an ASCII interface which allows you to read and write. The other is an ioctl() interface. The ASCII interface is meant for administration. The ioctl() interface is meant for C programmes (i.e. the X server). The interfaces are described below, with sample commands and C code. =============================================================================== Reading MTRRs from the shell: % cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1 reg01: base=0x08000000 ( 128MB), size= 64MB: write-back, count=1 =============================================================================== Creating MTRRs from the shell: # echo "base=0xf8000000 size=0x400000 type=write-combining" >! /proc/mtrr And the result thereof: % cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 128MB: write-back, count=1 reg01: base=0x08000000 ( 128MB), size= 64MB: write-back, count=1 reg02: base=0xf8000000 (3968MB), size= 4MB: write-combining, count=1 This is for videoram at base address 0xf8000000 and size 4 MBytes. To find out your base address, you need to look at the output of your X server, which tells you where the linear framebuffer address is. A typical line that you may get is: (--) S3: PCI: 968 rev 0, Linear FB @ 0xf8000000 Note that you should only use the value from the X server, as it may move the framebuffer base address, so the only value you can trust is that reported by the X server. To find out the size of your framebuffer (what, you don't actually know?), the following line will tell you: (--) S3: videoram: 4096k That's 4 MBytes, which is 0x400000 bytes (in hexadecimal). A patch is being written for XFree86 which will make this automatic: in other words the X server will manipulate /proc/mtrr using the ioctl() interface, so users won't have to do anything. If you use a commercial X server, lobby your vendor to add support for MTRRs. =============================================================================== Removing MTRRs from the shell: % echo "disable=2" >! /proc/mtrr =============================================================================== Reading MTRRs from a C programme using ioctl()'s: /* mtrr-show.c Source file for mtrr-show (example programme to show MTRRs using ioctl()'s) Copyright (C) 1997-1998 Richard Gooch This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Richard Gooch may be reached by email at rgooch@atnf.csiro.au The postal address is: Richard Gooch, c/o ATNF, P. O. Box 76, Epping, N.S.W., 2121, Australia. */ /* This programme will use an ioctl() on /proc/mtrr to show the current MTRR settings. This is an alternative to reading /proc/mtrr. Written by Richard Gooch 17-DEC-1997 Last updated by Richard Gooch 2-MAY-1998 */ #include #include #include #include #include #include #include #define MTRR_NEED_STRINGS #include #define TRUE 1 #define FALSE 0 #define ERRSTRING strerror (errno) int main () { int fd; struct mtrr_gentry gentry; if ( ( fd = open ("/proc/mtrr", O_RDONLY, 0) ) == -1 ) { if (errno == ENOENT) { fputs ("/proc/mtrr not found: not supported or you don't have a PPro?\n", stderr); exit (1); } fprintf (stderr, "Error opening /proc/mtrr\t%s\n", ERRSTRING); exit (2); } for (gentry.regnum = 0; ioctl (fd, MTRRIOC_GET_ENTRY, &gentry) == 0; ++gentry.regnum) { if (gentry.size < 1) { fprintf (stderr, "Register: %u disabled\n", gentry.regnum); continue; } fprintf (stderr, "Register: %u base: 0x%lx size: 0x%lx type: %s\n", gentry.regnum, gentry.base, gentry.size, mtrr_strings[gentry.type]); } if (errno == EINVAL) exit (0); fprintf (stderr, "Error doing ioctl(2) on /dev/mtrr\t%s\n", ERRSTRING); exit (3); } /* End Function main */ =============================================================================== Creating MTRRs from a C programme using ioctl()'s: /* mtrr-add.c Source file for mtrr-add (example programme to add an MTRRs using ioctl()) Copyright (C) 1997-1998 Richard Gooch This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Richard Gooch may be reached by email at rgooch@atnf.csiro.au The postal address is: Richard Gooch, c/o ATNF, P. O. Box 76, Epping, N.S.W., 2121, Australia. */ /* This programme will use an ioctl() on /proc/mtrr to add an entry. The first available mtrr is used. This is an alternative to writing /proc/mtrr. Written by Richard Gooch 17-DEC-1997 Last updated by Richard Gooch 2-MAY-1998 */ #include #include #include #include #include #include #include #include #include #define MTRR_NEED_STRINGS #include #define TRUE 1 #define FALSE 0 #define ERRSTRING strerror (errno) int main (int argc, char **argv) { int fd; struct mtrr_sentry sentry; if (argc != 4) { fprintf (stderr, "Usage:\tmtrr-add base size type\n"); exit (1); } sentry.base = strtoul (argv[1], NULL, 0); sentry.size = strtoul (argv[2], NULL, 0); for (sentry.type = 0; sentry.type < MTRR_NUM_TYPES; ++sentry.type) { if (strcmp (argv[3], mtrr_strings[sentry.type]) == 0) break; } if (sentry.type >= MTRR_NUM_TYPES) { fprintf (stderr, "Illegal type: \"%s\"\n", argv[3]); exit (2); } if ( ( fd = open ("/proc/mtrr", O_WRONLY, 0) ) == -1 ) { if (errno == ENOENT) { fputs ("/proc/mtrr not found: not supported or you don't have a PPro?\n", stderr); exit (3); } fprintf (stderr, "Error opening /proc/mtrr\t%s\n", ERRSTRING); exit (4); } if (ioctl (fd, MTRRIOC_ADD_ENTRY, &sentry) == -1) { fprintf (stderr, "Error doing ioctl(2) on /dev/mtrr\t%s\n", ERRSTRING); exit (5); } fprintf (stderr, "Sleeping for 5 seconds so you can see the new entry\n"); sleep (5); close (fd); fputs ("I've just closed /proc/mtrr so now the new entry should be gone\n", stderr); } /* End Function main */ =============================================================================== --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mtrr.h" /* Generic MTRR (Memory Type Range Register) ioctls. Copyright (C) 1997-1998 Richard Gooch This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with this library; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. Richard Gooch may be reached by email at rgooch@atnf.csiro.au The postal address is: Richard Gooch, c/o ATNF, P. O. Box 76, Epping, N.S.W., 2121, Australia. */ #ifndef _LINUX_MTRR_H #define _LINUX_MTRR_H #include #include #define MTRR_IOCTL_BASE 'M' struct mtrr_sentry { unsigned long base; /* Base address */ unsigned long size; /* Size of region */ unsigned int type; /* Type of region */ }; struct mtrr_gentry { unsigned int regnum; /* Register number */ unsigned long base; /* Base address */ unsigned long size; /* Size of region */ unsigned int type; /* Type of region */ }; /* These are the various ioctls */ #define MTRRIOC_ADD_ENTRY _IOW(MTRR_IOCTL_BASE, 0, struct mtrr_sentry) #define MTRRIOC_SET_ENTRY _IOW(MTRR_IOCTL_BASE, 1, struct mtrr_sentry) #define MTRRIOC_DEL_ENTRY _IOW(MTRR_IOCTL_BASE, 2, struct mtrr_sentry) #define MTRRIOC_GET_ENTRY _IOWR(MTRR_IOCTL_BASE, 3, struct mtrr_gentry) /* These are the region types */ #define MTRR_TYPE_UNCACHABLE 0 #define MTRR_TYPE_WRCOMB 1 /*#define MTRR_TYPE_ 2*/ /*#define MTRR_TYPE_ 3*/ #define MTRR_TYPE_WRTHROUGH 4 #define MTRR_TYPE_WRPROT 5 #define MTRR_TYPE_WRBACK 6 #define MTRR_NUM_TYPES 7 #ifdef MTRR_NEED_STRINGS static char *mtrr_strings[MTRR_NUM_TYPES] = { "uncachable", /* 0 */ "write-combining", /* 1 */ "?", /* 2 */ "?", /* 3 */ "write-through", /* 4 */ "write-protect", /* 5 */ "write-back", /* 6 */ }; #endif #ifdef __KERNEL__ /* The following functions are for use by other drivers */ # if defined(CONFIG_MTRR) || defined(CONFIG_MTRR_MODULE) extern int mtrr_add (unsigned long base, unsigned long size, unsigned int type, char increment); extern int mtrr_del (int reg, unsigned long base, unsigned long size); # else static __inline__ int mtrr_add (unsigned long base, unsigned long size, unsigned int type, char increment) { return -ENODEV; } static __inline__ int mtrr_del (int reg, unsigned long base, unsigned long size) { return -ENODEV; } # endif /* The following functions are for initialisation: don't use them! */ extern int mtrr_init (void); # if defined(__SMP__) && defined(CONFIG_MTRR) extern void mtrr_init_boot_cpu (void); extern void mtrr_init_secondary_cpu (void); # endif #endif #endif /* _LINUX_MTRR_H */ --C7zPtVaVf+AK4Oqc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 18: 4:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.inktomi.com (mercury.inktomi.com [209.1.32.126]) by hub.freebsd.org (Postfix) with ESMTP id A673814D0F for ; Wed, 10 Mar 1999 18:04:27 -0800 (PST) (envelope-from jplevyak@inktomi.com) Received: from proxydev.inktomi.com (proxydev.inktomi.com [209.1.32.44]) by mercury.inktomi.com (8.9.1a/8.9.1) with ESMTP id SAA01995; Wed, 10 Mar 1999 18:04:18 -0800 (PST) Received: (from jplevyak@localhost) by proxydev.inktomi.com (8.8.5/8.7.3) id SAA20737; Wed, 10 Mar 1999 18:04:09 -0800 (PST) Message-ID: <19990310180408.E19442@proxydev.inktomi.com> Date: Wed, 10 Mar 1999 18:04:08 -0800 From: John Plevyak To: "Richard Seaman, Jr." , John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: bug in linuxthreads for FreeBSD References: <19990309172626.A7182@proxydev.inktomi.com> <19990310105944.F4440@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990310105944.F4440@tar.com>; from Richard Seaman, Jr. on Wed, Mar 10, 1999 at 10:59:44AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The patch I am using unconditionally removes the thread from the > > queue. This does not prevent the thread from being woken up > > extaneously, but it does prevent the ASSERT and corruption of > > the p_nextwaiting lists. > > It might be possible to eliminate, or at least narrow the window > for the "extraneous" wakeup. It would require reworking the linux > threads code more. OTOH, it could just be left as is. Here's > what Butenhof's "Programming with POSIX Threads" says about > the pthread_cond_* wait functions: > > "It is important that you test the predicate after locking the mutex > and before waiting on the condition variable. If a thread signals > a condition variable while no threads are waiting, nothing happens. > If some other thread calls pthread_cond_wait right after that, > it will just keep waiting...." > > and, > > "It is equally important that you test the predicate again when the > thread wakes up. You should always wait for a condition variable > in a loop, to protect against program errors, multiprocessor races, > and spurious wakeups." I agree for (at least for now). I have now tested it for hours under high load and haven't seen any problems. Here is the complete patch. I needed to patch up mutex_lock in mutex.c as well, so I moved a couple things around, and added some asserts. john diff -c --exclude=*.0 --exclude=*o --exclude=*a ./condvar.c ../../../linuxthreads.2/work/linuxthreads-0.71/condvar.c *** ./condvar.c Wed Mar 10 17:37:17 1999 --- ../../../linuxthreads.2/work/linuxthreads-0.71/condvar.c Wed Mar 10 12:20:40 1999 *************** *** 22,29 **** #include "queue.h" #include "restart.h" - static void remove_from_queue(pthread_queue * q, pthread_descr th); - int pthread_cond_init(pthread_cond_t *cond, const pthread_condattr_t *cond_attr) { --- 22,27 ---- *************** *** 51,56 **** --- 49,55 ---- release(&cond->c_spinlock); pthread_mutex_unlock(mutex); suspend_with_cancellation(self); + assert(self->p_nextwaiting == NULL && cond->c_waiting.head != self); pthread_mutex_lock(mutex); /* This is a cancellation point */ if (self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE) { *************** *** 107,159 **** or the timeout occurred (retsleep == 0) or another interrupt occurred (retsleep == -1) */ /* Re-acquire the spinlock */ - acquire(&cond->c_spinlock); /* This is a cancellation point */ ! if (self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE) { remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); pthread_exit(PTHREAD_CANCELED); - } /* If not signaled: also remove ourselves and return an error code */ ! if (self->p_signal == 0) { ! remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); return retsleep == 0 ? ETIMEDOUT : EINTR; - } #else acquire(&cond->c_spinlock); enqueue(&cond->c_waiting, self); release(&cond->c_spinlock); pthread_mutex_unlock(mutex); retsleep = 0; ! if (!(self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE)) { /* We really should make thr_sleep return EINTR too. It just returns EAGAIN if it timed out, or 0 if awakened (or EINVAL if bad parameter. */ retsleep = syscall(SYS_thr_sleep, reltime); - } acquire(&cond->c_spinlock); ! if (self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE) { remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); pthread_exit(PTHREAD_CANCELED); ! } ! if (retsleep) { ! remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); return retsleep == EAGAIN ? ETIMEDOUT : EINTR; - } - #endif - /* Otherwise, return normally */ - release(&cond->c_spinlock); - pthread_mutex_lock(mutex); return 0; } --- 106,145 ---- or the timeout occurred (retsleep == 0) or another interrupt occurred (retsleep == -1) */ /* Re-acquire the spinlock */ /* This is a cancellation point */ ! acquire(&cond->c_spinlock); ! if (self->p_nextwaiting != NULL || cond->c_waiting.head == self) remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); ! if (self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE) pthread_exit(PTHREAD_CANCELED); /* If not signaled: also remove ourselves and return an error code */ ! if (self->p_signal == 0) return retsleep == 0 ? ETIMEDOUT : EINTR; #else acquire(&cond->c_spinlock); enqueue(&cond->c_waiting, self); release(&cond->c_spinlock); pthread_mutex_unlock(mutex); retsleep = 0; ! if (!(self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE)) /* We really should make thr_sleep return EINTR too. It just returns EAGAIN if it timed out, or 0 if awakened (or EINVAL if bad parameter. */ retsleep = syscall(SYS_thr_sleep, reltime); acquire(&cond->c_spinlock); ! if (self->p_nextwaiting != NULL || cond->c_waiting.head == self) remove_from_queue(&cond->c_waiting, self); ! release(&cond->c_spinlock); ! pthread_mutex_lock(mutex); ! if (self->p_canceled && self->p_cancelstate == PTHREAD_CANCEL_ENABLE) pthread_exit(PTHREAD_CANCELED); ! if (retsleep) return retsleep == EAGAIN ? ETIMEDOUT : EINTR; #endif return 0; } *************** *** 210,234 **** return 0; } ! /* Auxiliary function on queues */ ! ! static void remove_from_queue(pthread_queue * q, pthread_descr th) { pthread_descr t; ! if (q->head == NULL) return; if (q->head == th) { q->head = th->p_nextwaiting; if (q->head == NULL) q->tail = NULL; th->p_nextwaiting = NULL; ! return; } for (t = q->head; t->p_nextwaiting != NULL; t = t->p_nextwaiting) { if (t->p_nextwaiting == th) { t->p_nextwaiting = th->p_nextwaiting; if (th->p_nextwaiting == NULL) q->tail = t; th->p_nextwaiting = NULL; ! return; } } } --- 196,219 ---- return 0; } ! int remove_from_queue(pthread_queue * q, pthread_descr th) { pthread_descr t; ! if (q->head == NULL) return 0; if (q->head == th) { q->head = th->p_nextwaiting; if (q->head == NULL) q->tail = NULL; th->p_nextwaiting = NULL; ! return 1; } for (t = q->head; t->p_nextwaiting != NULL; t = t->p_nextwaiting) { if (t->p_nextwaiting == th) { t->p_nextwaiting = th->p_nextwaiting; if (th->p_nextwaiting == NULL) q->tail = t; th->p_nextwaiting = NULL; ! return 1; } } + return 0; } diff -c --exclude=*.0 --exclude=*o --exclude=*a ./mutex.c ../../../linuxthreads.2/work/linuxthreads-0.71/mutex.c *** ./mutex.c Wed Mar 10 17:37:17 1999 --- ../../../linuxthreads.2/work/linuxthreads-0.71/mutex.c Wed Mar 10 12:18:22 1999 *************** *** 83,92 **** int pthread_mutex_lock(pthread_mutex_t * mutex) { ! pthread_descr self; while(1) { acquire(&mutex->m_spinlock); switch(mutex->m_kind) { case PTHREAD_MUTEX_FAST_NP: if (mutex->m_count == 0) { --- 83,94 ---- int pthread_mutex_lock(pthread_mutex_t * mutex) { ! pthread_descr self = thread_self(); while(1) { acquire(&mutex->m_spinlock); + if (self->p_nextwaiting != NULL || mutex->m_waiting.head == self) + remove_from_queue(&mutex->m_waiting, self); switch(mutex->m_kind) { case PTHREAD_MUTEX_FAST_NP: if (mutex->m_count == 0) { *************** *** 94,103 **** release(&mutex->m_spinlock); return 0; } - self = thread_self(); break; case PTHREAD_MUTEX_RECURSIVE_NP: - self = thread_self(); if (mutex->m_count == 0 || mutex->m_owner == self) { mutex->m_count++; mutex->m_owner = self; --- 96,103 ---- *************** *** 106,112 **** } break; case PTHREAD_MUTEX_ERRORCHECK_NP: - self = thread_self(); if (mutex->m_count == 0) { mutex->m_count = 1; mutex->m_owner = self; --- 106,111 ---- diff -c --exclude=*.0 --exclude=*o --exclude=*a ./queue.h ../../../linuxthreads.2/work/linuxthreads-0.71/queue.h *** ./queue.h Fri Dec 5 09:28:21 1997 --- ../../../linuxthreads.2/work/linuxthreads-0.71/queue.h Wed Mar 10 12:20:04 1999 *************** *** 60,62 **** --- 60,64 ---- } return th; } + + int remove_from_queue(pthread_queue * q, pthread_descr th); -- John Bradley Plevyak, PhD, jplevyak@inktomi.com, PGP KeyID: 051130BD Inktomi Corporation, 1900 S. Norfolk Street, Suite 110, San Mateo, CA 94403 W:(415)653-2830 F:(415)653-2801 P:(888)491-1332/5103192436.4911332@pagenet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 18:19:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail1.atl.bellsouth.net (mail1.atl.bellsouth.net [205.152.0.28]) by hub.freebsd.org (Postfix) with ESMTP id 97CA815167 for ; Wed, 10 Mar 1999 18:19:17 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-77-30.atl.bellsouth.net [209.214.77.30]) by mail1.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id VAA22514; Wed, 10 Mar 1999 21:18:14 -0500 (EST) Received: from wghicks (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.2/8.9.2) with ESMTP id VAA45202; Wed, 10 Mar 1999 21:09:26 -0500 (EST) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199903110209.VAA45202@bellsouth.net> To: wayne@crb-web.com Cc: FreeBSD Hackers List , wghicks@wghicks.bellsouth.net Subject: Re: new to driver coding In-reply-to: Your message of "Wed, 10 Mar 1999 20:48:09 EST." Date: Wed, 10 Mar 1999 21:09:26 -0500 From: W Gerald Hicks Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You've been through /usr/share/examples/kld first? Cheers, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 18:24:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id CF0AA151B5 for ; Wed, 10 Mar 1999 18:24:49 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA05153; Wed, 10 Mar 1999 18:20:41 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdqy5151; Thu Mar 11 02:20:32 1999 Date: Wed, 10 Mar 1999 18:20:29 -0800 (PST) From: Julian Elischer To: Wayne Cuddy Cc: FreeBSD Hackers List Subject: Re: new to driver coding 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 check out /usr/share.examples/drivers/psuedo[mumble] this is a shellscript that writes a dummy driver, and even links it into the kernel and compile sit for you.. edit to taste.. (I haven't run it for 6 months so it may need a few slight cleanups to work on a new system) julian On Wed, 10 Mar 1999, Wayne Cuddy wrote: > > > I have been reading any information I can find, which is very little, on > writing unix device drivers. Specifically I would like information on > FreeBSD;) > > I really want to start simple by writing a character driver that is not > attached to a REAL device but just holds on to some memory and allows me to > writing some bytes in (write()) and read them back (read()). > > I don't think this will be very difficult but I need some detailed information > specific to FreeBDS on what header files I need to include and how to build my > driver as part of the kernel. What directory should I build my driver in? > What entry point will the kernel call when the system boots so I can print a > pretty little string from my driver showing a sample initialization. > > > I am kinda in the dark here to specifics of this so ALL help is greatly > appreciated. > > Thanks, > Wayne > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 19:12:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.crb-web.com (ns1.crb-web.com [209.70.120.131]) by hub.freebsd.org (Postfix) with SMTP id 502DC151E5 for ; Wed, 10 Mar 1999 19:12:13 -0800 (PST) (envelope-from wayne@crb.crb-web.com) Received: (qmail 8713 invoked by uid 1001); 11 Mar 1999 03:58:21 -0000 Date: Wed, 10 Mar 1999 22:58:21 -0500 (EST) From: Wayne Cuddy Reply-To: wayne@crb-web.com Cc: FreeBSD Hackers List Subject: Re: new to driver coding 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 It looks like it was just a matter of not knowing they were there. These examples are exactly what I am looking for. Thanks, Wayne On Wed, 10 Mar 1999, Julian Elischer wrote: > Date: Wed, 10 Mar 1999 18:20:29 -0800 (PST) > From: Julian Elischer > To: Wayne Cuddy > Cc: FreeBSD Hackers List > Subject: Re: new to driver coding > > check out /usr/share.examples/drivers/psuedo[mumble] > this is a shellscript that writes a dummy driver, and even links it into > the kernel and compile sit for you.. > > edit to taste.. > > (I haven't run it for 6 months so it may need a few slight cleanups to > work on a new system) > > julian > > > On Wed, 10 Mar 1999, Wayne Cuddy wrote: > > > > > > > I have been reading any information I can find, which is very little, on > > writing unix device drivers. Specifically I would like information on > > FreeBSD;) > > > > I really want to start simple by writing a character driver that is not > > attached to a REAL device but just holds on to some memory and allows me to > > writing some bytes in (write()) and read them back (read()). > > > > I don't think this will be very difficult but I need some detailed information > > specific to FreeBDS on what header files I need to include and how to build my > > driver as part of the kernel. What directory should I build my driver in? > > What entry point will the kernel call when the system boots so I can print a > > pretty little string from my driver showing a sample initialization. > > > > > > I am kinda in the dark here to specifics of this so ALL help is greatly > > appreciated. > > > > Thanks, > > Wayne > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 19:19:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from stumpy.dannyland.org (danman.isdn.uiuc.edu [192.17.16.228]) by hub.freebsd.org (Postfix) with SMTP id 900E815190 for ; Wed, 10 Mar 1999 19:19:46 -0800 (PST) (envelope-from dannyman@stumpy.dannyland.org) Received: (qmail 18297 invoked by uid 1000); 11 Mar 1999 03:19:37 -0000 Date: Wed, 10 Mar 1999 21:19:37 -0600 From: dannyman To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: netscape situation Message-ID: <19990310211937.C27080@stumpy.dannyland.org> References: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE> <19990310090318.A15203@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19990310090318.A15203@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Wed, Mar 10, 1999 at 09:03:18AM +0100 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 10, 1999 at 09:03:18AM +0100, Christoph Kukulies wrote: > Can netscape be built from sources? I mean, the source are freely > available, aren't they? > > So if one wants to set out to find the point where it crashes > one could build a debuggable version? > > Did anyone go though this already? The original Netscape source doesn't include Java, and requires Motif. The new Mozilla project is allegedly coming along well and usually builds. It's a lot to build, and it's a development browser - meaning it's little more than a rendering engine at this point. If someone could advise on the best way of getting old aout X libraries onto an ELF system, I'd like to hear it. I'm currently browsing with grail, which isn't too bad. I like that it handles my existing Netscape bookmarks, actually. -danny -danny -- dannyman - http://www.dannyland.org/~dannyman/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 19:29: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id B2BA21520D for ; Wed, 10 Mar 1999 19:28:40 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id WAA29904; Wed, 10 Mar 1999 22:27:54 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id WAA05914; Wed, 10 Mar 1999 22:27:52 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id WAA42322; Wed, 10 Mar 1999 22:27:52 -0500 (EST) Date: Wed, 10 Mar 1999 22:27:52 -0500 (EST) From: Thomas David Rivers Message-Id: <199903110327.WAA42322@lakes.dignus.com> To: dannyman@dannyland.org, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: netscape situation Cc: hackers@FreeBSD.ORG In-Reply-To: <19990310211937.C27080@stumpy.dannyland.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, Mar 10, 1999 at 09:03:18AM +0100, Christoph Kukulies wrote: > > > Can netscape be built from sources? I mean, the source are freely > > available, aren't they? > > > > So if one wants to set out to find the point where it crashes > > one could build a debuggable version? > > > > Did anyone go though this already? > > The original Netscape source doesn't include Java, and requires Motif. > > The new Mozilla project is allegedly coming along well and usually builds. > It's a lot to build, and it's a development browser - meaning it's little more > than a rendering engine at this point. > > If someone could advise on the best way of getting old aout X libraries onto > an ELF system, I'd like to hear it. I'm currently browsing with grail, which > isn't too bad. I like that it handles my existing Netscape bookmarks, > actually. > > -danny > > -danny > > -- > dannyman - http://www.dannyland.org/~dannyman/ I put a bug in the PR data base on this; the aout X libraries shipped with the 3.1-RELEASE CDs have some issues. I solved the problem by grabbing the X11 libraries from a 2.2.8 CD (they are in the XF86bin gzipped tar file) and copying them to /usr/X11R6/lib/aout. At that point, I was able to run netscape 4.5 and 4.08 just fine. Also - you may want to know, the problem affects JAVA programs as well. See pr#10473 in the PR database for more details. - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 19:29:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (Postfix) with ESMTP id 32412151EA for ; Wed, 10 Mar 1999 19:29:09 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id QAA13635; Thu, 11 Mar 1999 16:28:43 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.3/8.9.1) id QAA09906; Thu, 11 Mar 1999 16:28:43 +1300 (NZDT) (envelope-from jabley) Date: Thu, 11 Mar 1999 16:28:43 +1300 From: Joe Abley To: dannyman Cc: Christoph Kukulies , hackers@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: netscape situation Message-ID: <19990311162843.A9877@clear.co.nz> References: <199903100750.IAA15148@gilberto.physik.RWTH-Aachen.DE> <19990310090318.A15203@gil.physik.rwth-aachen.de> <19990310211937.C27080@stumpy.dannyland.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990310211937.C27080@stumpy.dannyland.org>; from dannyman on Wed, Mar 10, 1999 at 09:19:37PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 10, 1999 at 09:19:37PM -0600, dannyman wrote: > If someone could advise on the best way of getting old aout X libraries onto > an ELF system, I'd like to hear it. I'm currently browsing with grail, which > isn't too bad. I like that it handles my existing Netscape bookmarks, > actually. If you install the current XFree86 port you will be given the option of installing aout libraries as well as elf ones. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 22: 5:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 18BE814BDD for ; Wed, 10 Mar 1999 22:05:25 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id WAA93967; Wed, 10 Mar 1999 22:05:01 -0800 (PST) From: Archie Cobbs Message-Id: <199903110605.WAA93967@bubba.whistle.com> Subject: Re: Tunnel loopback In-Reply-To: <004301be6b0e$2efd77f0$23b197ce@crocus.ezo.net> from Jim Flowers at "Mar 10, 99 10:53:45 am" To: terry@ppsl.demon.co.uk Date: Wed, 10 Mar 1999 22:05:01 -0800 (PST) Cc: freebsd-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 Jim Flowers writes: > >> Were you able to get the FreeBSD Skip-1.0 port to compile on 3.1? > > > >Apparently it won't work with LKM and needs a KLM rewrite. > > You might want to check with Archie Cobbs to see if > this is going to happen. I'm still using 2.2.8 which compiles OK. I'm This has happened :-) Please give the new port a try. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 22:49:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from theo.thg.goe.ni.schule.de (theo.THG.Goe.NI.Schule.DE [195.27.182.97]) by hub.freebsd.org (Postfix) with ESMTP id 92BF415064 for ; Wed, 10 Mar 1999 22:49:08 -0800 (PST) (envelope-from gratke@thg.goe.ni.schule.de) Received: from elly.thg.goe.ni.schule.de (gratke@elly.thg.goe.ni.schule.de [195.27.182.98]) by theo.thg.goe.ni.schule.de (8.8.8/8.8.8) with SMTP id HAA08553 for ; Thu, 11 Mar 1999 07:48:34 +0100 Date: Thu, 11 Mar 1999 07:48:45 +0100 (MET) From: Georg Ratke Reply-To: Georg Ratke To: hackers@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 23:33: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id CB7E2150F9 for ; Wed, 10 Mar 1999 23:33:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA61853; Wed, 10 Mar 1999 23:32:43 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 23:32:43 -0800 (PST) From: Matthew Dillon Message-Id: <199903110732.XAA61853@apollo.backplane.com> To: Greg Rowe Cc: David Greenman , freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi David, : : I built a kernel with debugging and had one of the guys here take a look :through the crash dump. First, is the new "Fatal Trap" DDB output and then his :comments on what he saw. Anything else we should try ?? : :Greg : :On 10-Mar-99 David Greenman wrote: :> There are at least two things that are strange in the following. First, :> there is no call to bzero() from zalloci() (or in zlock(), _zalloc(), and :> zunlock(), which are inlined). Second, the parameters to generic_bzero() :> indicate that 0 bytes are to be zeroed. It's also strange that the address Well, zalloci() can call _zget(), which can call bzero(). Maybe the underscore in the _zget() is preventing DDB from listing it. The call offset in zalloci() in the trace below is zalloci+0x29. If you disassemble zalloci, you will note that this is the call-return point for _zget: 0xf020b59f : pushl %ebx 0xf020b5a0 : call 0xf020b5f8 <_zget> 0xf020b5a5 : movl %eax,%ebx The generic_bzero() call arguments are either bogus, or the stack length argument has been modified by generic_bzero(). The fault virtual address is 0, but vm_page_alloc() seems to properly test for m == NULL so this should not be possible. It would be useful to print out the contents of *m from the _zget frame, and also the *z structure. -- If this machine has a large amount of memory, it may have overrun its KVA allocation. This can also happen if you have a large 'maxusers' in the kernel config. If so, try reducing maxusers to 128 or less. -Matt Matthew Dillon :Fatal trap 12: page fault while in kernel mode :mp_lock = 03000002; cpuid = 3; lapic.id = 02000000 :fault virtual address = 0x0 :fault code = supervisor write, page not present :instruction pointer = 0x8:0xf020ec9f :stack pointer = 0x10:0xfe5d2c34 :frame pointer = 0x10:0xfe5d2c58 :code segment = base 0x0, limit 0xfffff, type 0x1b : = DPL 0, pres 1, def32 1, gran 1 :processor eflags = interrupt enabled, resume, IOPL = 0 :current process = 243 (cpio) :interrupt mask = net tty bio cam <- SMP: XXX :kernel: type 12 trap, code=0 :Stopped at generic_bzero+0xf: repe stosl %es:(%edi) :db> trace :generic_bzero(f3283f80,0,f47f7000,fe5d2c90,fe5d2c98) at generic_bzero+0xf :zalloci(f3283f80,f4880100,f47f7000,6f7f9,fe540ec0) at zalloci+0x29 :getnewvnode(1,f33f0400,f3266200,fe5d2cfc,100) at getnewvnode+0x2f8 :... :....snip....gdb) frame 11 :#11 0xf01f1869 in zalloci (z=0xf3283f80) at ../../vm/vm_zone.h:85 :85 return _zget(z); :(kgdb) print _zget :$6 = {void *(struct vm_zone *)} 0xf01f18d4 <_zget> :(kgdb) print generic_bzero :$7 = {} 0xf020ec90 : :So, it doesn't look like a 1-bit off error.... : :Because zget/zalloc is an inline function, I can't seem to get gdb to :print simple_lock or simple_unlock. : :-Chris : : :Greg Rowe US WEST - Internet Service Operations : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 10 23:52: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5A4A515254; Wed, 10 Mar 1999 23:51:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA62027; Wed, 10 Mar 1999 23:51:29 -0800 (PST) (envelope-from dillon) Date: Wed, 10 Mar 1999 23:51:29 -0800 (PST) From: Matthew Dillon Message-Id: <199903110751.XAA62027@apollo.backplane.com> To: "Mark J. Taylor" Cc: freebsd-hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: ccd driver problems with > 2GB segments, +fix References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting. What if each disk is 8GB and we set the stripe size to 8GB? Won't that break the u_long ( i.e. was broken before, and is still broken now ). Perhaps these variables should be 64 bit quantities throughout except for the bp->b_count? -Matt Matthew Dillon :Fix: :The ccd driver has a variable "bcount" that is a long: it needs :to be a u_long. And, a 64 bit int is shifted into a 32 bit int :in ccdbuffer(): the 32 bit int must changed to be a 64 bit int. : :This second change has already been made in NetBSD (somebody else :figured it out), where the ccd driver originated from. It was :rather tricky to find: the math involving block numbers and ccd :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 0: 9:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 575BB1525B for ; Thu, 11 Mar 1999 00:07:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA73368; Thu, 11 Mar 1999 00:07:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mtaylor@cybernet.com Cc: freebsd-hackers@freebsd.org Subject: Re: ccd driver problems with > 2GB segments, +fix In-reply-to: Your message of "Wed, 10 Mar 1999 17:47:53 EST." Date: Thu, 11 Mar 1999 00:07:18 -0800 Message-ID: <73364.921139638@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've found, and corrected, a serious problem with the ccd driver > with regards to large segments. The bugs were discovered while > developing our NetMAX system, under FreeBSD 2.2.x. > The problems still exist in 3.x, and are easily repeatable. Your diffs are definitely desired - I'm sorry if previous ones are mouldering due to inattention; we're somewhat understaffed. :( If you also have some PR#s for the older ones that got black-holed, I'll also do my best to dig them up and deal with them. > I've got more patches to FreeBSD, but I feel reluctant to submit > them, because nobody cares to either review them or commit them. Again, if you can make sure that both Mike Smith and I have these and any pending problems brought to our attention, we'll do our best. Something else you might want to consider is the option of applying for a commit bit so that you can simply make the changes yourself. Are you ready for the heavy mantle of direct responsibility? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 0:19:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.a2000.nl (spartacus.a2000.nl [62.108.1.20]) by hub.freebsd.org (Postfix) with ESMTP id D6DAF152AE for ; Thu, 11 Mar 1999 00:19:35 -0800 (PST) (envelope-from alexlh@funk.org) Received: from node1484.a2000.nl ([62.108.20.132] helo=funk.org) by smtp2.a2000.nl with esmtp (Exim 2.02 #4) id 10L0gS-0003Dg-00; Thu, 11 Mar 1999 09:19:12 +0100 Message-ID: <36E77C61.8600D744@funk.org> Date: Thu, 11 Mar 1999 09:18:41 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Jaye Mathisen , freebsd-hackers@freebsd.org Subject: Re: Anybody using the 4 port Znyx card? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen wrote: > > I'm just about to order one, but wanted to check first. It's not listed > specifically in the release notes for 3.1, but I suspect it's a DEC > chipset based card (tulip?) and am hoping it just shows up as de0, de1, > de2, de3, etc. I am, and it works very well. No problems with it. Alex -- +--------------------------------+-------------------+ | SMTP: | E-Gold: 101979 | | ICBM: N52 22.647' E4 51.555' | PGP: 0x1d512a3f | +--------------------------------+-------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 0:23:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id A31E7151F8 for ; Thu, 11 Mar 1999 00:23:00 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id KAA29023; Thu, 11 Mar 1999 10:22:01 +0200 (SAST) Received: by citadel via recvmail id 29020; Thu Mar 11 10:21:39 1999 Message-ID: <36E77D39.7A2F779D@cdsec.com> Date: Thu, 11 Mar 1999 10:22:17 +0200 From: Graham Wheeler X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Niall Smart , hackers@freebsd.org Subject: Re: C++ global constructors and shared libraries References: <36E6AB40.742D64BB@cdsec.com> <36E6BFE4.951172E3@kira.team400.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Niall Smart wrote: > > Graham Wheeler wrote: > > > > Hi folks > > > > I have just changed some C++ code libraries from static to shared. > > I now find that some global objects declared in these libraries > > are no longer having their constructors called. If I move the object > > niall% g++ -v > cc -v > gcc version 2.7.2.1 This is the same version I am using. > niall% g++ -c -fpic libfoo.cc > niall% g++ -shared libfoo.o -o libfoo.so I am using the bsd.lib.mk and related include files for the Make; certainly I don't think that there is anything strange in these. > niall% g++ main.cc -Wl,-R,. -L. -lfoo I don't have the -Wl,-R,. options; would these make any difference at all? -- 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 Thu Mar 11 0:37:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 651FF15106 for ; Thu, 11 Mar 1999 00:37:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA29654; Thu, 11 Mar 1999 08:38:06 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 11 Mar 1999 08:38:06 +0000 (GMT) From: Doug Rabson To: Dan Seguin Cc: freebsd-hackers@freebsd.org Subject: Re: KLD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 Mar 1999, Dan Seguin wrote: > > > On Wed, 10 Mar 1999, Doug Rabson wrote: > > > > I've got two questions: > > > > > > 1. Is there a way of creating more than one syscall in the same KLD? Is > > > syscall_register() all one needs to do? If not, what kind of hand waving > > > is necessary with SYSCALL_MODULE, DECLARE_MODULE, SYSINIT, DATASET? > > > > Just have more than one SYSCALL_MODULE statement. > > > > It was the first thing I tried. Then looked around in the code, found out > how the module is recorded: it has a unique name. I've included the > example source file I'm using and the make message. > > ... > > SYSCALL_MODULE(syscall, &offset, &hello_sysent, load, NULL); > > SYSCALL_MODULE(syscall, &offset2, &hello_sysent2, NULL, NULL); Try using a different name for the second entry (i.e. syscall2). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 2:15:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cdsec.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id AA10E15243 for ; Thu, 11 Mar 1999 02:14:33 -0800 (PST) (envelope-from gram@cdsec.com) Received: (from nobody@localhost) by citadel.cdsec.com (8.8.8/8.6.9) id MAA05764 for ; Thu, 11 Mar 1999 12:14:14 +0200 (SAST) Received: by citadel via recvmail id 5704; Thu Mar 11 12:13:29 1999 Message-ID: <36E7976F.434678BE@cdsec.com> Date: Thu, 11 Mar 1999 12:14:07 +0200 From: Graham Wheeler X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: C++ global constructors and shared libraries] Content-Type: multipart/mixed; boundary="------------8EB273D000AF610B01F3FE9E" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------8EB273D000AF610B01F3FE9E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Graham Wheeler wrote: > Niall Smart wrote: > > Graham Wheeler wrote: > > > > Niall Smart wrote: > > > > > niall% g++ -c -fpic libfoo.cc > > > niall% g++ -shared libfoo.o -o libfoo.so > > > > I am using the bsd.lib.mk and related include files for the Make; > > certainly I don't think that there is anything strange in these. > > Well, why don't you try the exact same commands I used. Okay, I have hacked my own copy of bsd.lib.mk to use g++ to make the library rather than ld, and it works now! Thanks... -- 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/ --------------8EB273D000AF610B01F3FE9E Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <36E7972F.D69E69CE@cdsec.com> Date: Thu, 11 Mar 1999 12:13:03 +0200 From: Graham Wheeler X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Niall Smart Subject: Re: C++ global constructors and shared libraries References: <36E6AB40.742D64BB@cdsec.com> <36E6BFE4.951172E3@kira.team400.ie> <36E77D39.7A2F779D@cdsec.com> <36E79434.8E222FA2@kira.team400.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Niall Smart wrote: > > Graham Wheeler wrote: > > > > Niall Smart wrote: > > > > > niall% g++ -c -fpic libfoo.cc > > > niall% g++ -shared libfoo.o -o libfoo.so > > > > I am using the bsd.lib.mk and related include files for the Make; > > certainly I don't think that there is anything strange in these. > > Well, why don't you try the exact same commands I used. Okay, I have hacked my own copy of bsd.lib.mk to use g++ to make the library rather than ld, and it works now! Thanks... -- 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/ --------------8EB273D000AF610B01F3FE9E-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 3:16:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 138DC1531B for ; Thu, 11 Mar 1999 03:16:35 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.12 #1) id 10L3Rm-000078-00 for hackers@freebsd.org; Thu, 11 Mar 1999 13:16:14 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Re: 3.0-STABLE, rc.shutdown is still ignored. Date: Thu, 11 Mar 1999 13:16:14 +0200 Message-ID: <441.921150974@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, PR10035 describes an interesting problem, where rc.shutdown is run for ``shutdown now'' but not for ``shutdown -r now''. I think the problem is that init(8) is sent a SIGKILL by reboot(8) before it's had a chance to run rc.shutdown. If so, the fix that seems obvious to me is to have reboot(8) send a SIGINT to init(8), by my reading of the init(8) manpage. Am I on the right track here? Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 6:20:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.149.24]) by hub.freebsd.org (Postfix) with ESMTP id 1416C14CFF for ; Thu, 11 Mar 1999 06:20:39 -0800 (PST) (envelope-from avalon@cheops.anu.edu.au) Received: (from avalon@localhost) by cheops.anu.edu.au (8.9.1/8.9.1) id BAA06755 for hackers@freebsd.org; Fri, 12 Mar 1999 01:20:15 +1100 (EDT) From: Darren Reed Message-Id: <199903111420.BAA06755@cheops.anu.edu.au> Subject: zp driver. To: hackers@freebsd.org Date: Fri, 12 Mar 1999 01:20:15 +1100 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whilst I'm using 2.2.7 still on my laptop, I was wondering if there has been any improvement in the zp driver for the 3c589 ? I find that it locks up (about once a second under high traffic) and generates a large number of erroneous packets under high traffic. Strangely this problem is not observed when running Winders NT. Has there been any work done on that driver since then for 3.X or 2.2.8 or has the card been "dropped" ? Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 6:53:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 1B93B1533C for ; Thu, 11 Mar 1999 06:53:17 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp083.dialup.st.keio.ac.jp [131.113.27.83]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id XAA18380; Thu, 11 Mar 1999 23:52:56 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.2/3.7W) id XAA04991; Thu, 11 Mar 1999 23:53:11 +0900 (JST) Date: Thu, 11 Mar 1999 23:53:11 +0900 (JST) Message-Id: <199903111453.XAA04991@lavender.yy.cs.keio.ac.jp> To: sheldonh@iafrica.com Cc: hackers@FreeBSD.ORG, sanpei@sanpei.org Subject: Re: 3.0-STABLE, rc.shutdown is still ignored. In-Reply-To: Your message of "Thu, 11 Mar 1999 20:16:14 JST". <441.921150974@axl.noc.iafrica.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sheldonh@iafrica.com Wrote: >> PR10035 describes an interesting problem, where rc.shutdown is run for >> ``shutdown now'' but not for ``shutdown -r now''. Also discussed in bin/5451, ``halt/reboot does not execute /etc/rc.shutdown as kill -INT 1'' I hope to fix it, and we hope to use /etc/rc.shutdown for some programs, for example, inn, ja-Canna.... Some people want to use it: http://www.freebsd.org/cgi/getmsg.cgi?fetch=653883+0+archive/1998/freebsd-current/19981115.freebsd-current Subject: Re: /etc/rc.d, and changes to /etc/rc? But I don't have enough skill to fix it..... Cheers MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 7:24:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (Postfix) with ESMTP id A800D153B3 for ; Thu, 11 Mar 1999 07:24:27 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.3/8.9.3) id JAA40763; Thu, 11 Mar 1999 09:23:58 -0600 (CST) (envelope-from dick) Date: Thu, 11 Mar 1999 09:23:58 -0600 From: "Richard Seaman, Jr." To: John Plevyak Cc: hackers@FreeBSD.ORG Subject: Re: bug in linuxthreads for FreeBSD Message-ID: <19990311092357.G24744@tar.com> References: <19990309172626.A7182@proxydev.inktomi.com> <19990310105944.F4440@tar.com> <19990310180408.E19442@proxydev.inktomi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990310180408.E19442@proxydev.inktomi.com>; from John Plevyak on Wed, Mar 10, 1999 at 06:04:08PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 10, 1999 at 06:04:08PM -0800, John Plevyak wrote: > I have now tested it for hours under high load and haven't > seen any problems. > > Here is the complete patch. I needed to patch up mutex_lock > in mutex.c as well, so I moved a couple things around, and added > some asserts. Looks ok to me. I've incorporated them into the port, and posted a new version to http://lt.tar.com . FYI, this also fixed a problem that appeared under SMP testing (using Luoqi Chen's kernel patches). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 8: 2:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by hub.freebsd.org (Postfix) with ESMTP id 39E88153AE; Thu, 11 Mar 1999 08:02:55 -0800 (PST) (envelope-from mtaylor@cybernet.com) Received: from spiffy.cybernet.com (spiffy.cybernet.com [192.245.33.55]) by gateway.cybernet.com (8.8.8/8.8.8) with ESMTP id LAA25156; Thu, 11 Mar 1999 11:02:05 -0500 (EST) (envelope-from mtaylor@cybernet.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903110751.XAA62027@apollo.backplane.com> Date: Thu, 11 Mar 1999 11:03:04 -0500 (EST) Reply-To: mtaylor@cybernet.com Organization: Cybernet Systems From: "Mark J. Taylor" To: Matthew Dillon Subject: Re: ccd driver problems with > 2GB segments, +fix Cc: jkh@FreeBSD.ORG, msmith@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fixes actually came at two separate times: one to fix the panic, and another to fix the filesystem. 1) Changing the long to u_long makes the ccd not panic the system when it is configured. The corrected problem, specifically, was that the "<< 9" of a 32 bit (signed) word and subsequent store into a 32 bit (signed) word was causing negative transfer sizes. 2) Using an off_f in read/write size comparisons corrected the problem of putting a 64 bit value into a 32 bit word. The second fix (the off_t) is really the only fix needed. The first patch (the u_long) is not necessary: it hid the real problem under most cases (32 bit << 9 being put into a 32 bit value ends up being negative much of the time!), until the math worked out "badly". Here's the final and complete patch (for -current): (this is exactly what NetBSD does, BTW) *** ccd.c.orig Wed Mar 10 11:22:41 1999 --- ccd.c Thu Mar 11 10:53:13 1999 *************** *** 841,846 **** --- 841,847 ---- register struct ccdcinfo *ci, *ci2 = NULL; /* XXX */ register struct ccdbuf *cbp; register daddr_t cbn, cboff; + register off_t cbc; #ifdef DEBUG if (ccddebug & CCDB_IO) *************** *** 919,929 **** LIST_INIT(&cbp->cb_buf.b_dep); cbp->cb_buf.b_resid = 0; if (cs->sc_ileave == 0) ! cbp->cb_buf.b_bcount = dbtob(ci->ci_size - cbn); else ! cbp->cb_buf.b_bcount = dbtob(cs->sc_ileave - cboff); ! if (cbp->cb_buf.b_bcount > bcount) ! cbp->cb_buf.b_bcount = bcount; cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; --- 920,929 ---- LIST_INIT(&cbp->cb_buf.b_dep); cbp->cb_buf.b_resid = 0; if (cs->sc_ileave == 0) ! cbc = dbtob((off_t)(ci->ci_size - cbn)); else ! cbc = dbtob((off_t)(cs->sc_ileave - cboff)); ! cbp->cb_buf.b_bcount = (cbc < bcount) ? cbc : bcount; cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; On 11-Mar-99 Matthew Dillon wrote: > Interesting. What if each disk is 8GB and we set the stripe > size to 8GB? Won't that break the u_long ( i.e. was broken > before, and is still broken now ). Perhaps these variables > should be 64 bit quantities throughout except for the > bp->b_count? > > -Matt > Matthew Dillon > > >:Fix: >:The ccd driver has a variable "bcount" that is a long: it needs >:to be a u_long. And, a 64 bit int is shifted into a 32 bit int >:in ccdbuffer(): the 32 bit int must changed to be a 64 bit int. >: >:This second change has already been made in NetBSD (somebody else >:figured it out), where the ccd driver originated from. It was >:rather tricky to find: the math involving block numbers and ccd >:... -------------------------------------------------------------------- Mark J. Taylor Networking Research Cybernet Systems mtaylor@cybernet.com 727 Airport Blvd. PHONE (734) 668-2567 Ann Arbor, MI 48108 FAX (734) 668-8780 http://www.cybernet.com/ http://www.netmax.com/ -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 8:29: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from reliant.pmr.com (reliant.pmr.com [207.170.114.33]) by hub.freebsd.org (Postfix) with ESMTP id D4E1A15221 for ; Thu, 11 Mar 1999 08:28:01 -0800 (PST) (envelope-from wayne@reliant.pmr.com) Received: (from wayne@localhost) by reliant.pmr.com (8.8.7/8.8.7) id KAA19586; Thu, 11 Mar 1999 10:27:43 -0600 (CST) (envelope-from wayne) Message-ID: <19990311102743.B19542@reliant.pmr.com> Date: Thu, 11 Mar 1999 10:27:43 -0600 From: Wayne Willcox To: freebsd-hackers@freebsd.org Subject: question with linux emmulation Reply-To: Wayne Willcox Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an application that I would like to run on freebsd it is a linux app. It has a few private shared libraries that were built on Linux. Is there a way I can run this under Linux emmulation? Thanks. -- Slowly and surely the unix crept up on the Nintendo user ... Wayne Willcox I will not eat green eggs and ham wayne@reliant.pmr.com I will not eat them Sam I Am!! A wise person makes his own decisions, a weak one obeys public opinion. -- Chinese proverb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 9:11:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5423015004; Thu, 11 Mar 1999 09:11:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id JAA28583; Thu, 11 Mar 1999 09:10:27 -0800 Date: Thu, 11 Mar 1999 09:10:27 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: "Mark J. Taylor" , freebsd-hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: ccd driver problems with > 2GB segments, +fix In-Reply-To: <199903110751.XAA62027@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 Umm- I don't remember the details exactly but there were some fixes in NetBSD for this a while back. On Wed, 10 Mar 1999, Matthew Dillon wrote: > Interesting. What if each disk is 8GB and we set the stripe > size to 8GB? Won't that break the u_long ( i.e. was broken > before, and is still broken now ). Perhaps these variables > should be 64 bit quantities throughout except for the > bp->b_count? > > -Matt > Matthew Dillon > > > :Fix: > :The ccd driver has a variable "bcount" that is a long: it needs > :to be a u_long. And, a 64 bit int is shifted into a 32 bit int > :in ccdbuffer(): the 32 bit int must changed to be a 64 bit int. > : > :This second change has already been made in NetBSD (somebody else > :figured it out), where the ccd driver originated from. It was > :rather tricky to find: the math involving block numbers and ccd > :... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 9:44:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 6AB1E14C2E for ; Thu, 11 Mar 1999 09:44:27 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.9.2/8.9.2) id LAA58931; Thu, 11 Mar 1999 11:43:32 -0600 (CST) (envelope-from greg) 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: <199903110732.XAA61853@apollo.backplane.com> Date: Thu, 11 Mar 1999 11:43:32 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: Matthew Dillon Subject: Re: SMP Woes Cc: freebsd-hackers@FreeBSD.ORG, David Greenman Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved the Fatal Trap problem. I'll try moving the number up in stages and see where it breaks. I had been using 256 and a couple times 512 in testing. Thanks. Greg On 11-Mar-99 Matthew Dillon wrote: > Well, zalloci() can call _zget(), which can call bzero(). Maybe the > underscore in the _zget() is preventing DDB from listing it. > > The call offset in zalloci() in the trace below is zalloci+0x29. If > you disassemble zalloci, you will note that this is the call-return > point for _zget: > > 0xf020b59f : pushl %ebx > 0xf020b5a0 : call 0xf020b5f8 <_zget> > 0xf020b5a5 : movl %eax,%ebx > > The generic_bzero() call arguments are either bogus, or the stack > length argument has been modified by generic_bzero(). > > The fault virtual address is 0, but vm_page_alloc() seems to properly > test for m == NULL so this should not be possible. > > It would be useful to print out the contents of *m from the _zget > frame, and also the *z structure. > > -- > > If this machine has a large amount of memory, it may have overrun its > KVA allocation. This can also happen if you have a large 'maxusers' > in the kernel config. If so, try reducing maxusers to 128 or less. > > -Matt > Matthew Dillon > > Greg Rowe US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 9:49: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 17A7114CAA for ; Thu, 11 Mar 1999 09:48:59 -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 JAA17720; Thu, 11 Mar 1999 09:48:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id JAA57916; Thu, 11 Mar 1999 09:48:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 11 Mar 1999 09:48:40 -0800 (PST) Message-Id: <199903111748.JAA57916@vashon.polstra.com> To: cjclark@home.com Subject: Re: FP Math Problem In-Reply-To: <199903042248.RAA08114@cc942873-a.ewndsr1.nj.home.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903042248.RAA08114@cc942873-a.ewndsr1.nj.home.com>, Crist J. Clark wrote: > I am trying to figure out why the following program produces a > floating point exception and core dumps. > > #include > #include > #include > > int main() > { > > double a = 1e200; > double b; > > printf("fpgetmask: %o\n",fpgetmask()); > > printf("a: %e\n",a); > > b = a*a; > > printf("isinf: %d\n",isinf(b)); > > printf("isnan: %d\n",isnan(b)); > > printf("b > DBL_MAX: %d\n",b>DBL_MAX); > > printf("b: %e\n",b); > > return 0; > } > > My output is, > > [112:~/tmp] ./dtest > fpgetmask: 15 > a: 1.000000e+200 > isinf: 0 > isnan: 0 > Floating exception (core dumped) > > I started with this on -questions and (although the thread got > sidetracked by a bad test program I presented at the beginning) other > FreeBSDers have not reproduced the error, but get what I would expect, > > % ./dtest > fpgetmask: 15 > a: 1.000000e+200 > isinf: 1 > isnan: 0 > b > DBL_MAX: 1 > b: inf > > However, I get the FPE and core dump on my three FreeBSD machines > (different hardware on each). I played around with this a little bit on a Pentium-II. I also got the floating exception. There _should_ be a floating exception, but it should happen at the "b = a*a" statement, I believe. If you add a second "b = a*a" after it, then you do get the FPE. As the code is written, for some reason nothing is stored into b at all. That's why some people get the core dump later on and others don't. (It might also depend on the specific FP hardware.) You can confirm this by initializing b to 1.0. Bruce Evans could probably explain this. You might wish to ask him about it. 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 Thu Mar 11 9:56:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 007B214C8D for ; Thu, 11 Mar 1999 09:56:49 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.9.2/8.9.2) id LAA58966 for freebsd-hackers@FreeBSD.ORG; Thu, 11 Mar 1999 11:56:32 -0600 (CST) (envelope-from greg) 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: Date: Thu, 11 Mar 1999 11:56:32 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG By the way, in my testing at 4.0 -current of 2 days ago, this problem appeared. It's probably been fixed by now, but in case no ones happened upon it, I repeatedly get the following when I type "sysctl -a": Fatal trap 12: page fault while in kernel mode mp_lock = 02000002; cpuid = 2; lapic.id = 01000000 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01f1adc stack pointer = 0x10:0xfa9e5da0 frame pointer = 0x10:0xfa9e5e54 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 239 (sysctl) interrupt mask = <- SMP: XXX kernel: type 12 trap, code=0 Stopped at sysctl_vm_zone+0x90: repne scasb (%esi) db> trace sysctl_vm_zone(f025c7ec,0,0,fa9e5ea8,0) at sysctl_vm_zone+0x90 sysctl_root(0,fa9e5f30,2,fa9e5ea8,0) at sysctl_root+0x115 userland_sysctl(fa98d5a0,fa9e5f30,2,0,efbfcf7c) at userland_sysctl+0x11e __sysctl(fa98d5a0,fa9e5f94,efbfdbd8,2,efbfdbd8) at __sysctl+0x60 syscall(2f,2f,efbfdbd8,2,efbfcf40) at syscall+0x187 Xint0x80_syscall() at Xint0x80_syscall+0x4c db> On 11-Mar-99 Greg Rowe wrote: > Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 > solved > the Fatal Trap problem. I'll try moving the number up in stages and see where > it breaks. I had been using 256 and a couple times 512 in testing. Thanks. > > Greg > Greg Rowe US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 9:59:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1BD9015160 for ; Thu, 11 Mar 1999 09:59:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA66670; Thu, 11 Mar 1999 09:58:55 -0800 (PST) (envelope-from dillon) Date: Thu, 11 Mar 1999 09:58:55 -0800 (PST) From: Matthew Dillon Message-Id: <199903111758.JAA66670@apollo.backplane.com> To: Greg Rowe Cc: freebsd-hackers@FreeBSD.ORG, David Greenman Subject: Re: SMP Woes References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved :the Fatal Trap problem. I'll try moving the number up in stages and see where :it breaks. I had been using 256 and a couple times 512 in testing. Thanks. : :Greg Uh huh! David, hackers, Gentlemen! This is the third person to hit this problem. It is especially nasty because the failure condition is not always something easily traceable. I, for one, would personally like to see the problem fixed and damn the BSDI compatibility. At the very least, we have to panic when the kernel's page table is overrun! Can we commit Tor.Egge's patch or something similar? I've re-included it below for reference. -Matt :To: jfieber@indiana.edu :Cc: dillon@apollo.backplane.com :Subject: Re: Problems in VM structure ? :From: Tor.Egge@fast.no :In-Reply-To: Your message of "Tue, 16 Feb 1999 09:28:32 -0500 (EST)" :References: :X-Mailer: Mew version 1.70 on Emacs 19.34.1 :Mime-Version: 1.0 :Content-Type: Text/Plain; charset=us-ascii :Content-Transfer-Encoding: 7bit :Date: Tue, 16 Feb 1999 23:11:37 +0100 :Sender: tegge@fast.no : :... : :If your system has 512 MB or more memory, you might need to increase :the kernel KVA range. ------------ Index: sys/i386/include/pmap.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v retrieving revision 1.57 diff -u -r1.57 pmap.h --- pmap.h 1998/11/24 20:25:52 1.57 +++ pmap.h 1999/02/07 00:18:50 @@ -92,9 +94,9 @@ #endif #ifndef NKPDE #ifdef SMP -#define NKPDE 62 /* addressable number of page tables/pde's */ +#define NKPDE 126 /* addressable number of page tables/pde's */ #else -#define NKPDE 63 /* addressable number of page tables/pde's */ +#define NKPDE 127 /* addressable number of page tables/pde's */ #endif /* SMP */ #endif Index: sys/i386/conf/Makefile.i386 =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Makefile.i386,v retrieving revision 1.139 diff -u -r1.139 Makefile.i386 --- Makefile.i386 1999/02/14 13:56:15 1.139 +++ Makefile.i386 1999/02/15 00:24:21 @@ -56,7 +56,7 @@ CFLAGS+= -aout .endif -LOAD_ADDRESS?= F0100000 +LOAD_ADDRESS?= E0100000 DEFINED_PROF= ${PROF} .if defined(PROF) CFLAGS+= -malign-functions=4 Index: sys/i386/conf/kernel.script =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/kernel.script,v retrieving revision 1.1 diff -u -r1.1 kernel.script --- kernel.script 1998/09/30 12:14:39 1.1 +++ kernel.script 1999/01/16 00:49:59 @@ -5,7 +5,7 @@ SECTIONS { /* Read-only sections, merged into text segment: */ - . = 0xf0100000 + SIZEOF_HEADERS; + . = 0xe0100000 + SIZEOF_HEADERS; .interp : { *(.interp) } .hash : { *(.hash) } .dynsym : { *(.dynsym) } -------------------- Combined with some extra kernel options options "VM_KMEM_SIZE=(128*1024*1024)" options "VM_KMEM_SIZE_MAX=(128*1024*1024)" You'll need a fairly recent version of /boot/loader in order to boot ELF kernels with larger KVA range. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10: 6:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D0EDA14D83 for ; Thu, 11 Mar 1999 10:05:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA28838; Thu, 11 Mar 1999 10:04:38 -0800 Date: Thu, 11 Mar 1999 10:04:37 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Update on- 'Panic in FFS/4.0 as of yesterday - update' In-Reply-To: <199903100104.RAA50707@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'm finding that the last set of patches are pretty good. So far, the hardware is breaking before FreeBSD, which is a good sign. I've been running with a 120GB CCD (two RAID units) and beating on it moderately severely. So far, so good. I'll probably extend the tests somewhat to starting testing directory stuff at the same time. Oh- with one minor exception- it uncovered a stupid bug in *my* stuff (repeated failures to allocate DMA caused eventual constipation in an internal softc for the ISP driver- that'll be fixed- but I also have to find out how ocme DMA allocation could fail on an i386)... Thanks for the good work here. It's very heartening so far. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10:12:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B228E14C37 for ; Thu, 11 Mar 1999 10:12:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA66780; Thu, 11 Mar 1999 10:12:34 -0800 (PST) (envelope-from dillon) Date: Thu, 11 Mar 1999 10:12:34 -0800 (PST) From: Matthew Dillon Message-Id: <199903111812.KAA66780@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: An Update on- 'Panic in FFS/4.0 as of yesterday - update' References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm finding that the last set of patches are pretty good. So far, the :hardware is breaking before FreeBSD, which is a good sign. I've been :running with a 120GB CCD (two RAID units) and beating on it moderately :severely. So far, so good. I'll probably extend the tests somewhat to :starting testing directory stuff at the same time. : :Oh- with one minor exception- it uncovered a stupid bug in *my* stuff :(repeated failures to allocate DMA caused eventual constipation in an :internal softc for the ISP driver- that'll be fixed- but I also have to :find out how ocme DMA allocation could fail on an i386)... : :Thanks for the good work here. It's very heartening so far. : : :-matt Thanks for the report, Matt! Your test scripts made a big difference in helping us track down and fix the various problems! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10:21:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5F77414C8D; Thu, 11 Mar 1999 10:21:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA66914; Thu, 11 Mar 1999 10:20:48 -0800 (PST) (envelope-from dillon) Date: Thu, 11 Mar 1999 10:20:48 -0800 (PST) From: Matthew Dillon Message-Id: <199903111820.KAA66914@apollo.backplane.com> To: "Mark J. Taylor" Cc: jkh@FreeBSD.ORG, msmith@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: ccd driver problems with > 2GB segments, +fix References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The fixes actually came at two separate times: one to fix :the panic, and another to fix the filesystem. :... :The second fix (the off_t) is really the only fix needed. The :first patch (the u_long) is not necessary: it hid the real :problem under most cases (32 bit << 9 being put into a 32 bit :value ends up being negative much of the time!), until the :math worked out "badly". : :Here's the final and complete patch (for -current): :(this is exactly what NetBSD does, BTW) Ah! Ok, now I understand. This seems totally reasonable. Jordan or David, can you commit this into -4.x plus backport it to 3.x? I don't think it needs any additional review. -Matt Matthew Dillon :*** ccd.c.orig Wed Mar 10 11:22:41 1999 :--- ccd.c Thu Mar 11 10:53:13 1999 :*************** :*** 841,846 **** :--- 841,847 ---- : register struct ccdcinfo *ci, *ci2 = NULL; /* XXX */ : register struct ccdbuf *cbp; : register daddr_t cbn, cboff; :+ register off_t cbc; : : #ifdef DEBUG : if (ccddebug & CCDB_IO) :*************** :*** 919,929 **** : LIST_INIT(&cbp->cb_buf.b_dep); : cbp->cb_buf.b_resid = 0; : if (cs->sc_ileave == 0) :! cbp->cb_buf.b_bcount = dbtob(ci->ci_size - cbn); : else :! cbp->cb_buf.b_bcount = dbtob(cs->sc_ileave - cboff); :! if (cbp->cb_buf.b_bcount > bcount) :! cbp->cb_buf.b_bcount = bcount; : : cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; : :--- 920,929 ---- : LIST_INIT(&cbp->cb_buf.b_dep); : cbp->cb_buf.b_resid = 0; : if (cs->sc_ileave == 0) :! cbc = dbtob((off_t)(ci->ci_size - cbn)); : else :! cbc = dbtob((off_t)(cs->sc_ileave - cboff)); :! cbp->cb_buf.b_bcount = (cbc < bcount) ? cbc : bcount; : : cbp->cb_buf.b_bufsize = cbp->cb_buf.b_bcount; : : : : : :On 11-Mar-99 Matthew Dillon wrote: :> Interesting. What if each disk is 8GB and we set the stripe :> size to 8GB? Won't that break the u_long ( i.e. was broken :> before, and is still broken now ). Perhaps these variables :> should be 64 bit quantities throughout except for the :> bp->b_count? :> :> -Matt :> Matthew Dillon :> :> :>:Fix: :>:The ccd driver has a variable "bcount" that is a long: it needs :>:to be a u_long. And, a 64 bit int is shifted into a 32 bit int :>:in ccdbuffer(): the 32 bit int must changed to be a 64 bit int. :>: :>:This second change has already been made in NetBSD (somebody else :>:figured it out), where the ccd driver originated from. It was :>:rather tricky to find: the math involving block numbers and ccd :>:... : :-------------------------------------------------------------------- :Mark J. Taylor Networking Research :Cybernet Systems mtaylor@cybernet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10:32:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id C3EDD14DCD for ; Thu, 11 Mar 1999 10:32:11 -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 KAA08792; Thu, 11 Mar 1999 10:30:50 -0800 (PST) Message-Id: <199903111830.KAA08792@implode.root.com> To: Matthew Dillon Cc: Greg Rowe , freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes In-reply-to: Your message of "Thu, 11 Mar 1999 09:58:55 PST." <199903111758.JAA66670@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 11 Mar 1999 10:30:50 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >:Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved >:the Fatal Trap problem. I'll try moving the number up in stages and see where >:it breaks. I had been using 256 and a couple times 512 in testing. Thanks. >: >:Greg > > Uh huh! > > David, hackers, Gentlemen! This is the third person to hit this problem. > It is especially nasty because the failure condition is not always > something easily traceable. I, for one, would personally like to see the > problem fixed and damn the BSDI compatibility. At the very least, we > have to panic when the kernel's page table is overrun! I've increased the KVA space to 1GB, which should be sufficient for most high-end applications while keeping happy the people who want large process address spaces (>2GB). I also fixed another problem that prevented machines with >=2GB of RAM from booting. -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 Thu Mar 11 10:40: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 02CD314E71 for ; Thu, 11 Mar 1999 10:39:57 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA22544; Fri, 12 Mar 1999 03:39:45 +0900 (JST) Message-ID: <36E80BAB.ADF73A60@newsguy.com> Date: Fri, 12 Mar 1999 03:30:03 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Matthew Dillon Cc: Greg Rowe , freebsd-hackers@FreeBSD.ORG, David Greenman Subject: Re: SMP Woes References: <199903111758.JAA66670@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > David, hackers, Gentlemen! This is the third person to hit this problem. > It is especially nasty because the failure condition is not always > something easily traceable. I, for one, would personally like to see the > problem fixed and damn the BSDI compatibility. At the very least, we > have to panic when the kernel's page table is overrun! Besides, Gb-range memory is getting ever more common. For new high-end servers, it is getting to the point of being a "must". -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10:45:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D433314C37 for ; Thu, 11 Mar 1999 10:45:57 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA25038; Thu, 11 Mar 1999 10:41:48 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdl25035; Thu Mar 11 18:41:44 1999 Date: Thu, 11 Mar 1999 10:41:39 -0800 (PST) From: Julian Elischer To: Wayne Willcox Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: question with linux emmulation In-Reply-To: <19990311102743.B19542@reliant.pmr.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 sure.. see the FAQ entries for Linux emulation and also look at http://lt.tar.com/ if you think it needs linuxthreads.. On Thu, 11 Mar 1999, Wayne Willcox wrote: > I have an application that I would like to run on freebsd it is > a linux app. It has a few private shared libraries that were built > on Linux. Is there a way I can run this under Linux emmulation? > > Thanks. > > -- > Slowly and surely the unix crept up on the Nintendo user ... > Wayne Willcox I will not eat green eggs and ham > wayne@reliant.pmr.com I will not eat them Sam I Am!! > A wise person makes his own decisions, a weak one obeys public opinion. > -- Chinese proverb > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 10:48: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id BA0E514E71 for ; Thu, 11 Mar 1999 10:48:01 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from crocus (p165.ezo.net [206.102.130.97]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id NAA01849; Thu, 11 Mar 1999 13:47:09 -0500 (EST) Message-ID: <001501be6bef$b74a05b0$23b197ce@crocus.ezo.net> From: "Jim Flowers" To: , "Terry Glanfield" Subject: Re: Tunnel loopback Date: Thu, 11 Mar 1999 13:48:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the clarification. It looks like I would have to do a number of things (clearly spelled out) to use ipfilter rather than ipfw which only requires a simple kernel rebuild. More below: -----Original Message----- From: Terry Glanfield >I'm simply moving all packets arriving on the internal interface and >SKIP packets on the external interface to the tunnel interface. Yep, I see it now. Similarly, with ipfw I use matching rules: allow 57 from any to any allow tcp from any 1640 to any allow tcp from any 1639 to any allow all from inside.host.or subnet.ip to outside.host.or.subnet.ip before the natd divert rule to effectively bypass nat. > > >I'm assuming that SKIP will keep state information about >nomadic hosts that have made inbound connections and extract/encrypt >what it needs while leaving the rest to pass through untouched. Like >a said though, I haven't played with "skiphost -a *" yet. I've just been doing '*' setups to configure a nomadic server. When all outbound packets go through the skipped interface, you are correct and skip will figure out which to process and which to just pass along in cleartext. I want to locate a skip server with a single interface on a perimeter network between exterior and interior firewall router interfaces. That means that an outbound packet is routed to the skiphost via the inside router interface for authentication/encryption/encapsulation and then the processed packet must be directed out the router external interface to the nomad. Unfortunately the brand name 3 port firewall routers that I use can route only on destination addresses so it can't be done. >I noticed that the archive was unaccessible. Was there an >announcement that I missed? No announcement. It (and the listserver) just went away. Archie Cobbs is trying to reestablish contact. He has also reworked the SKIP port to work with 3.1. It compiles and runs well. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 11:56:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jane.lfn.org (www.rfno.com [209.16.92.3]) by hub.freebsd.org (Postfix) with SMTP id 7D694151AB for ; Thu, 11 Mar 1999 11:56:31 -0800 (PST) (envelope-from caj@lfn.org) Received: (qmail 11751 invoked by uid 100); 11 Mar 1999 19:56:12 -0000 Date: Thu, 11 Mar 1999 13:56:12 -0600 (CST) From: Craig Johnston To: freebsd-hackers@freebsd.org, freebsd-bugs@freebsd.org Subject: failure to boot after 3.1-RELEASE install 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 saw the exact same problem mentioned once before on the lists and I was wondering if any headway had been made on the problem. (reference message id <199810181251.IAA17735@vger.foo.com> ) The system: Tyan Thunder II mobo, 2 x PII @ 266 384 megs SDRAM adaptec 7895 onboard fast/wide 9 gig WD scsi disk I am installing 3.1-RELEASE I got off ftp.cdrom.com last night. The install goes fine, but when I reboot and it comes up off the hard disk, at the F1: Freebsd, etc. prompt, when it either times out or you press F1, it just beeps. Further keypresses elicit further beeps but nothing real ever happens. I am about to go the route of using a fully dedicated disk (which fixed the problem in the case previously mentioned on the lists), but I thought I should report this. If anyone is interested in further details or having me poke at the problem in some way, drop me a line. Please cc: me directly in responses as I'm not sure my reception of the lists has been 100%. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 12:12:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (Postfix) with ESMTP id 4DAB8150C7 for ; Thu, 11 Mar 1999 12:12:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00824; Thu, 11 Mar 1999 12:06:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903112006.MAA00824@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: wayne@crb-web.com Cc: FreeBSD Hackers List Subject: Re: new to driver coding In-reply-to: Your message of "Wed, 10 Mar 1999 20:48:09 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Mar 1999 12:06:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been reading any information I can find, which is very little, on > writing unix device drivers. Specifically I would like information on > FreeBSD;) Just copy another device driver like the rest of us. 8) -- \\ 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 Thu Mar 11 12:39:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles134.castles.com [208.214.165.134]) by hub.freebsd.org (Postfix) with ESMTP id 95E611527E for ; Thu, 11 Mar 1999 12:39:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01071; Thu, 11 Mar 1999 12:33:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903112033.MAA01071@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: greg@uswest.net Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG, David Greenman Subject: Re: SMP Woes In-reply-to: Your message of "Thu, 11 Mar 1999 11:43:32 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Mar 1999 12:33:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved > the Fatal Trap problem. I'll try moving the number up in stages and see where > it breaks. I had been using 256 and a couple times 512 in testing. Thanks. You can also raise the kernel VM size with set kern.vm.kmem.size= in /boot/loader.rc You'll need to look at how the kernel memory is actually sized to determine what a good value for this is; this is a runtime override for the compile-time option VM_KMEM_SIZE. -- \\ 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 Thu Mar 11 13:14:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-49-dbn.dial-up.net [196.34.155.113]) by hub.freebsd.org (Postfix) with ESMTP id DC81E1513B; Thu, 11 Mar 1999 13:14:39 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA02967; Thu, 11 Mar 1999 23:13:02 +0200 (SAT) From: Robert Nordier Message-Id: <199903112113.XAA02967@ceia.nordier.com> Subject: Re: failure to boot after 3.1-RELEASE install In-Reply-To: from Craig Johnston at "Mar 11, 99 01:56:12 pm" To: ceia.nordier.com@ceia.nordier.com (Craig Johnston) Date: Thu, 11 Mar 1999 23:13:00 +0200 (SAT) Cc: freebsd-bugs@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Cross-posted: replying to -bugs] > I saw the exact same problem mentioned once before on the lists > and I was wondering if any headway had been made on the problem. > (reference message id <199810181251.IAA17735@vger.foo.com> ) Five months is a long time, where the new boot code is concerned. FWIW, there's actually no chance that the problem you have has anything to do with that reported in PR 8368, mentioned above. > The system: Tyan Thunder II mobo, 2 x PII @ 266 > 384 megs SDRAM > adaptec 7895 onboard > fast/wide 9 gig WD scsi disk > > I am installing 3.1-RELEASE I got off ftp.cdrom.com last night. > > The install goes fine, but when I reboot and it comes up off > the hard disk, at the F1: Freebsd, etc. prompt, when it either > times out or you press F1, it just beeps. Further keypresses > elicit further beeps but nothing real ever happens. Is there an F5 Drive 0 line displayed? If so, this is a known BIOS compatibility issue, and there's a fix available at http://www.freebsd.org/~rnordier/boot0-1.7.tar.gz If not, something was almost certainly wrongly configured, somehow, during the installation. If you can boot from floppy, sending along the output of the commands fdisk da0 disklabel da0 dd if=/dev/rda0 count=1 dd if=/dev/rda0s1 count=17 (assuming FreeBSD is slice 1) will probably enable us to sort out what went wrong and get you booting. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 13:35:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 272EA151A0 for ; Thu, 11 Mar 1999 13:35:39 -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 NAA09556; Thu, 11 Mar 1999 13:33:57 -0800 (PST) Message-Id: <199903112133.NAA09556@implode.root.com> To: Mike Smith Cc: greg@uswest.net, Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes In-reply-to: Your message of "Thu, 11 Mar 1999 12:33:50 PST." <199903112033.MAA01071@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 11 Mar 1999 13:33:57 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved >> the Fatal Trap problem. I'll try moving the number up in stages and see where >> it breaks. I had been using 256 and a couple times 512 in testing. Thanks. > >You can also raise the kernel VM size with > >set kern.vm.kmem.size= > >in /boot/loader.rc > >You'll need to look at how the kernel memory is actually sized to >determine what a good value for this is; this is a runtime override for >the compile-time option VM_KMEM_SIZE. Actually, that only increases the kernel malloc space. The total KVM is still controlled by other parameters. -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 Thu Mar 11 15:14:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 85666152B9 for ; Thu, 11 Mar 1999 15:14:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id XAA63009; Thu, 11 Mar 1999 23:13:58 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA14174; Thu, 11 Mar 1999 16:14:02 -0700 (MST) Message-Id: <199903112314.QAA14174@harmony.village.org> To: Darren Reed Subject: Re: zp driver. Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Mar 1999 01:20:15 +1100." <199903111420.BAA06755@cheops.anu.edu.au> References: <199903111420.BAA06755@cheops.anu.edu.au> Date: Thu, 11 Mar 1999 16:14:02 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903111420.BAA06755@cheops.anu.edu.au> Darren Reed writes: : Whilst I'm using 2.2.7 still on my laptop, I was wondering if there has : been any improvement in the zp driver for the 3c589 ? I find that it : locks up (about once a second under high traffic) and generates a large : number of erroneous packets under high traffic. Strangely this problem : is not observed when running Winders NT. Has there been any work done : on that driver since then for 3.X or 2.2.8 or has the card been "dropped" ? The ep driver works much better for this card. I've not seen any lockups on it. The zp driver is a crutch to enable network installs only (as far as I know). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 15:37: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from stingray.ivision.co.uk (stingray.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (Postfix) with ESMTP id 3FE9415104 for ; Thu, 11 Mar 1999 15:36:59 -0800 (PST) (envelope-from manar@ivision.co.uk) Received: from pretender.ivision.co.uk ([195.50.91.43] helo=pretender) by stingray.ivision.co.uk with smtp (Exim 2.04 #1) id 10LEx4-0006Wc-00 for freebsd-hackers@FreeBSD.ORG; Thu, 11 Mar 1999 23:33:18 +0000 Message-Id: <3.0.5.32.19990311233322.00abfe20@stingray.ivision.co.uk> X-Sender: manarpop@stingray.ivision.co.uk X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 11 Mar 1999 23:33:22 +0000 To: freebsd-hackers@FreeBSD.ORG From: Manar Hussain Subject: Re: Anybody using the 4 port Znyx card? In-Reply-To: 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 just about to order one, but wanted to check first. It's not listed > specifically in the release notes for 3.1, but I suspect it's a DEC > chipset based card (tulip?) and am hoping it just shows up as de0, de1, > de2, de3, etc. Roughly how much do these beasts cost? Regards, Manar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 15:57:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (00-60-67-24-29-83.bconnected.net [209.53.17.55]) by hub.freebsd.org (Postfix) with ESMTP id E03AE14F4C for ; Thu, 11 Mar 1999 15:57:43 -0800 (PST) (envelope-from jwalther@localhost) Received: from jwalther by localhost with local-smtp (Exim 2.11 #1 (Debian)) id 10LFId-0004W2-00; Thu, 11 Mar 1999 15:55:35 -0800 Date: Thu, 11 Mar 1999 15:55:35 -0800 (PST) From: Jonathan Walther X-Sender: jwalther@localhost To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: Re: /dev/vesa usage In-Reply-To: <199903010110.KAA07570@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Mar 1999, Kazutaka YOKOTA wrote: > There is no such thing as /dev/vesa. If you want to set a video mode > of your VESA-compliant VGA card, just issue ioctl to stdin. The explanation was very clear, and I was happy to receive it. However, I am getting mysterious errors. > /* obtain mode information */ > mode_info.vi_mode = M_VESA_CG1024x768; > ioctl(0, CONS_MODEINFO, &mode_info); Right here, the ioctl fails with errno 19, saying, "operation not supported by device". Woops, guess I forgot to insert the vesa.ko module. Just to be safe, I went into /usr/src/sys/modules and rebuilt and reinstalled it. Ok. But wait! # kldload /modules/vesa.ko module_register_init: module_register(vesa, f099a0c0, 0) error 6 Device not configured? I compiled my kernel with vm86 and vesa options and rebooted into it... What am I doing wrong? Is there perhaps a /dev/vesa after all and I have to use mknod? My video card is an ATI Rage 3d, and on bootup it clearly says VESA 2.0 compliant. Is our vesa support for 1.2 only, or for 2.0? Had this same error with 3.0, 3.1, and now 4.0 Cheers! Jonathan Walther To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 16: 8:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (00-60-67-24-29-83.bconnected.net [209.53.17.55]) by hub.freebsd.org (Postfix) with ESMTP id A1F8F1519C for ; Thu, 11 Mar 1999 16:08:56 -0800 (PST) (envelope-from jwalther@localhost) Received: from jwalther by localhost with local-smtp (Exim 2.11 #1 (Debian)) id 10LFTU-0004WO-00; Thu, 11 Mar 1999 16:06:48 -0800 Date: Thu, 11 Mar 1999 16:06:48 -0800 (PST) From: Jonathan Walther X-Sender: jwalther@localhost To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: more info. Re: /dev/vesa usage In-Reply-To: <199903010110.KAA07570@zodiac.mech.utsunomiya-u.ac.jp> 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 A little more information on the previous message, I hope it helps. On booting with the -v option, I see this in dmesg: Found BIOS32 Service Directory header at 0xf00fae90 Entry = 0xfb290 (0xf00fb290) Rev = 0 Len = 1 PCI BIOS entry at 0xb2c0 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fbfb0 Preloaded elf kernel "kernel" at 0xf023c000. VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 22 00 00 01 80 00 00 01 0b 01 00 01 21 01 00 01 2a 01 00 01 00 01 01 01 10 01 11 01 12 01 03 01 13 01 14 01 15 01 05 01 16 01 17 01 18 01 07 01 19 01 VESA: 3 mode(s) found vga0: rev 0x5c on pci0.17.0 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base e1100000, size 12 map[1]: type 4, range 32, base 00006200, size 5 map[2]: type 1, range 32, base e1000000, size 20 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k 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 VESA: v2.0, 8192k memory, flags:0x0, mode table:0xf020293a (1000022) VESA: ATI MACH64 VESA: ATI Technologies Inc. VESA: MACH64GT VESA: 01.00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 16:17:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id D37EF1522F; Thu, 11 Mar 1999 16:17:35 -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 KAA19054; Fri, 12 Mar 1999 10:47:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA28540; Fri, 12 Mar 1999 10:47:13 +1030 (CST) Message-ID: <19990312104713.L490@lemis.com> Date: Fri, 12 Mar 1999 10:47:13 +1030 From: Greg Lehey To: Paolo Di Francesco Cc: FreeBSD Questions Subject: Re: where is the kernel? References: <19990311005620.RIMA2097.fep01-svc@harlock> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990311005620.RIMA2097.fep01-svc@harlock>; from Paolo Di Francesco on Thu, Mar 11, 1999 at 01:05:57AM -0000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [following up to -questions] On Thursday, 11 March 1999 at 1:05:57 -0000, Paolo Di Francesco wrote: > I want to install/play/compile the last version of the kernel. I want to > download the 4.0 version (snapshot) but I don't find it. > I don't want to use CVS, only to download the kernel packages, unpack > them and putting them somewhere, then compile them. This isn't really an in-depth technical discussion, so I'm following up to -questions. On the CD-ROM, they're in the files src/ssys.a*. You'll find them on the ftp site in a similar place. > Can I use an arbitrary directory to compile the kernel? No. Use /usr/src/sys. You should have a symlink /sys -> /usr/src/sys; some software may depend on it, but I haven't checked. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Thu Mar 11 18: 4: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 7E50E15020 for ; Thu, 11 Mar 1999 18:03:57 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:LZurN9ddulKBND8LLDugcstoP+8xlnIS@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id LAA05281; Fri, 12 Mar 1999 11:03:34 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA23975; Fri, 12 Mar 1999 11:06:46 +0900 (JST) Message-Id: <199903120206.LAA23975@zodiac.mech.utsunomiya-u.ac.jp> To: Jonathan Walther Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: /dev/vesa usage In-reply-to: Your message of "Thu, 11 Mar 1999 15:55:35 PST." References: Date: Fri, 12 Mar 1999 11:06:45 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Mon, 1 Mar 1999, Kazutaka YOKOTA wrote: >> There is no such thing as /dev/vesa. If you want to set a video mode >> of your VESA-compliant VGA card, just issue ioctl to stdin. > >The explanation was very clear, and I was happy to receive it. However, I >am getting mysterious errors. > >> /* obtain mode information */ >> mode_info.vi_mode = M_VESA_CG1024x768; >> ioctl(0, CONS_MODEINFO, &mode_info); > >Right here, the ioctl fails with errno 19, saying, "operation not supported >by device". Woops, guess I forgot to insert the vesa.ko module. Just to >be safe, I went into /usr/src/sys/modules and rebuilt and reinstalled it. >Ok. But wait! The error may mean: 1. You are not running the program in one of vtys. Issuing this ioctl from a serial terminal or pty (such as xterm in the X session) generates this error. 2. The VESA BIOS support is not linked to the kernel nor loaded as a KLD module. 3. Your VESA ROM BIOS does not support this particular video mode. Your video "card" may support it, but its "ROM BIOS" may not. This may sound strange, but it is permissible in the VESA BIOS extension standard; the ROM BIOS includes minimal "stub" for the VESA extension and a DOS TSR (oh, good-old DOS TSR!) implements the full VESA BIOS services. Because video ROM space is limited, the vendor may find it difficult to implement full VESA BIOS specification in ROM... (I don't know if we can support the VESA TSR in vm86...) To find out exactly which video modes are supported by the VESA BIOS (ROM) and detected by the VESA support in FreeBSD, run vidcontrol in a vty: vidcontrol -i mode The list of video modes will be printed to stdout. (The list includes standard VGA modes as well.) It is also a good idea to consult with your card's manual. It may describe state of VESA support on your card. ># kldload /modules/vesa.ko >module_register_init: module_register(vesa, f099a0c0, 0) error 6 > >Device not configured? I compiled my kernel with vm86 and vesa options and >rebooted into it... What am I doing wrong? Please read the man page for vga(4). The VESA support can be either statically included in the kernel by defining "options VESA", OR by loading the vesa module. You don't need to load the vesa module if the VESA support is statically linked into the kernel. You are attempting to load the vesa module to the kernel which already has the statically-linked VESA BIOS support. >Is there perhaps a /dev/vesa >after all and I have to use mknod? Please forget about this non-existent device node. It does NOT exist. Where did you get this idea? Is there any doc or man page talking about it? If there is one, I have to correct it! >My video card is an ATI Rage 3d, and on >bootup it clearly says VESA 2.0 compliant. Is our vesa support for 1.2 >only, or for 2.0? Had this same error with 3.0, 3.1, and now 4.0 VESA BIOS Extension 1.2 or later, including 2.0, is supported. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 18:24:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (00-60-67-24-29-83.bconnected.net [209.53.17.55]) by hub.freebsd.org (Postfix) with ESMTP id 9F19814D45 for ; Thu, 11 Mar 1999 18:24:43 -0800 (PST) (envelope-from jwalther@localhost) Received: from jwalther by localhost with local-smtp (Exim 2.11 #1 (Debian)) id 10LHao-0004c8-00; Thu, 11 Mar 1999 18:22:30 -0800 Date: Thu, 11 Mar 1999 18:22:29 -0800 (PST) From: Jonathan Walther X-Sender: jwalther@localhost To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: recommended VESA compliant cards for fbsd? In-Reply-To: <199903120206.LAA23975@zodiac.mech.utsunomiya-u.ac.jp> 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 Once again, thank you. May I ask which cards you would recommend? I am looking to kick this thing into TrueColor RGB mode. Even normal VGA stuff tends to flake out, as the new cards don't seem to support VGA fully now that they support VESA. Jonathan On Fri, 12 Mar 1999, Kazutaka YOKOTA wrote: > 3. Your VESA ROM BIOS does not support this particular video mode. > Your video "card" may support it, but its "ROM BIOS" may not. This > may sound strange, but it is permissible in the VESA BIOS extension > standard; the ROM BIOS includes minimal "stub" for the VESA extension > and a DOS TSR (oh, good-old DOS TSR!) implements the full VESA BIOS > services. Because video ROM space is limited, the vendor may find it > difficult to implement full VESA BIOS specification in ROM... > (I don't know if we can support the VESA TSR in vm86...) > vidcontrol -i mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 18:28:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id EF3C5152DC for ; Thu, 11 Mar 1999 18:27:24 -0800 (PST) (envelope-from piet@cup.hp.com) Received: from hpfsvr02.cup.hp.com (root@hpfsvr02.cup.hp.com [15.28.74.198]) by palrel3.hp.com (8.8.6 (PHNE_14041)/8.8.5tis) with ESMTP id SAA07338; Thu, 11 Mar 1999 18:27:23 -0800 (PST) Received: from piet1.sparc.engr.sgi.com (piet1.cup.hp.com [15.28.75.241]) by hpfsvr02.cup.hp.com with SMTP (8.8.6/8.7.3 TIS Messaging 5.0) id SAA22664; Thu, 11 Mar 1999 18:27:00 -0800 (PST) Date: Thu, 11 Mar 1999 18:27:00 -0800 (PST) From: Piet Delaney Message-Id: <199903120227.SAA22664@hpfsvr02.cup.hp.com> To: moreinfo@tci.net Subject: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) Cc: piet@hpfsvr02.cup.hp.com, piet@piet.net, sadiq@piet.net, bonnie@piet.net, obrien@nuxi.com, hasty@star-gate.com, dave@relay.net, freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Dan: How about providing us with the source code for the NIC card for a PC and we'll slam it into a few UNIX systems (FreeBSD, NetBSD, OpenBSD, SunOS) over a few weekeends while we are waiting for your cable hunks to wire up the neighborhood. It's not good business to support a monopoly like MicroSoft. The UNIX/Linux folks are a much nicer crowd. -piet > From moreinfo@tci.net Thu Mar 11 18:06:03 PST 1999 > Date: Thu, 11 Mar 1999 19:01:50 GMT+00:00 > To: Piet Delaney > Subject: Re: Form posted from Mozilla (KMM25773C0KM) > From: "TCI@Home Customer Care" > Reply-To: "TCI@Home Customer Care" > MIME-Version: 1.0 > Content-Type> : > text/plain> ; > charset = "us-ascii"> > Content-Transfer-Encoding: quoted-printable > X-Mailer: Kana Customer Messaging System 3.0 > Content-Length: 3028 > > Delaney, > > Thank you for writing TCI@Home. > > In response to your previous Email concerning availability, > > Unfortunately, TCI@Home is not currently available in Santa Clara, Ca. = > > We are committed to notifying all interested parties once @Home is > available in a given area. > > Before we can offer the @Home service to your neighborhood, we must > first upgrade the cable plant that serves your neighborhood for = > two-way > communication. These upgrades must pass very strict quality control > standards. In order to ensure your satisfaction with the service, > TCI@Home will not certify the plant until our service is in compliance = > > with these standards. > > TCI@Home recognizes that many TCI customers are anxious to experience > @Home. Therefore, we are continuing to evaluate new launch markets. = > As > soon as these plans are final, we will make a formal announcement. > > I have put your information on our waiting list. Someone will contact = > > you when the @Home service is available in your neighborhood. > > It is possible to connect multiple PC's to the TCI@Home service. > However, TCI@Home does not support networking. > > Any configuration and/or maintaining of a home network or LAN is your > responsibility. Our technicians will install the TCI@Home Service on > one stand alone PC meeting our system requirements only. > > You are not required to use Windows, but TCI@Home does not support = > Unix > so installing and configuring the TCI@Home service to work with your = > LAN > and operating system is your responsibility. The TCI@Home technician > will install the external cable modem and leave you with the NIC card > and software. > > You will be required to sign off on the installation indicating that = > you > are responsible for all computer hardware and software configurations. > > The @Home service is oriented to single-home computer use. > > The alternative to limitations in IP addresses, domain name addresses > and web space is using @Work, which is a division of @Home. This is a = > > business solution with applicable pricing. For information see: > http://www.home.net/work/index.html > > If you should have any additional questions, you may Email us at > customer.care@tci.net, or call our Customer Support Center at > 1-888-262-6300, or 1-888-404-4663. Customer Support Representatives = > are > available 24 hours a day, 7 days a week for your convenience. > > Thank you again for contacting TCI@Home. > > Dan S > TCI @Home Electronic Communications Support > > > > Original message follows: > ------------------------- > > Firstname=3DDelaney > Lastname=3DPiet > Address1=3D2812 Toledo Ave > City=3DSanta Clara > State=3DCA > Zipcode=3D95051 > Homephone=3D > Workphone=3D(408) 447-4309 > UserEmail=3Dpiet@piet.net, piet@cup.hp.com > MessageType=3Demailme > Subject=3DSystem requirements question > SubjectOther=3D > Comments=3DHow about UNIX support. I;ve got > UNIX systems at home: > Sun Sparstations with SunOS and Solaris > PC Running FreeBSD > Sparcstation running Linux > Sparcstations running OpenBSD > > Would like to have a small subnet of about > 16 host addresses. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 19: 9:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (Postfix) with ESMTP id D466214F28 for ; Thu, 11 Mar 1999 19:08:09 -0800 (PST) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.3/8.8.8) id WAA55650; Thu, 11 Mar 1999 22:03:55 -0500 (EST) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 11 Mar 1999 22:03:54 -0500 (EST) To: Piet Delaney Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: <199903120227.SAA22664@hpfsvr02.cup.hp.com> References: <199903120227.SAA22664@hpfsvr02.cup.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14056.33022.162512.398060@tbuswell.ne.mediaone.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You don't need the source code for the ethernet card that they sell you. You can simply buy an ethernet card that you know works with your OS. Like the guy said, the cable modem is an external device. It talks 10BaseT on one end and cable network on the other. This information is in their FAQ. http://www.tci.net/tcinet.pgs/athomeframe.html You should consider yourself fortunate, receiving such a UNIX friendly response. -Ted Piet Delaney writes: > > From moreinfo@tci.net Thu Mar 11 18:06:03 PST 1999 [...] > > You are not required to use Windows, but TCI@Home does not support = > > Unix > > so installing and configuring the TCI@Home service to work with your = > > LAN > > and operating system is your responsibility. The TCI@Home technician > > will install the external cable modem and leave you with the NIC card > > and software. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 20:36:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id EB73114D2B for ; Thu, 11 Mar 1999 20:35:50 -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 UAA10415; Thu, 11 Mar 1999 20:22:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903120422.UAA10415@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Piet Delaney Cc: moreinfo@tci.net, piet@hpfsvr02.cup.hp.com, piet@piet.net, sadiq@piet.net, bonnie@piet.net, obrien@nuxi.com, hasty@star-gate.com, dave@relay.net, freebsd-hackers@freebsd.org Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-reply-to: Your message of "Thu, 11 Mar 1999 18:27:00 PST." <199903120227.SAA22664@hpfsvr02.cup.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Mar 1999 20:22:42 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You probably don't need their funky NIC card in all likelyhood their nic card is an ethernet card and if so you may want to kindly give TCI their "NIC Card" back --- they really ought to specify what exactly do they mean by "NIC Card". Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 22: 6: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from teton.srv.net (teton.srv.net [199.104.81.6]) by hub.freebsd.org (Postfix) with SMTP id 4FA0114F13 for ; Thu, 11 Mar 1999 22:05:56 -0800 (PST) (envelope-from cmott@scientech.com) Received: by teton.srv.net; id AA18899; Thu, 11 Mar 1999 23:05:34 -0700 Date: Thu, 11 Mar 1999 23:05:21 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: <199903120422.UAA10415@rah.star-gate.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 11 Mar 1999, Amancio Hasty wrote: > You probably don't need their funky NIC card in all likelyhood their nic card > is an ethernet > card and if so you may want to kindly give TCI their "NIC Card" back --- > they really > ought to specify what exactly do they mean by "NIC Card". > > Amancio The question is, how are IP addresses assigned? The Time Warner "Road Runner" system is known to use a DHCP-like mechanism which has been deciphered. I haven't read anything about @Home. Of course, static addressing would be preferable. Charles Mott P.S. It's going to be a long time before I see a cable modem in eastern Idaho. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 22:21:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.is.co.za (apollo.is.co.za [196.4.160.2]) by hub.freebsd.org (Postfix) with ESMTP id 76415151CF for ; Thu, 11 Mar 1999 22:21:04 -0800 (PST) (envelope-from geoff@hangdog.is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by apollo.is.co.za (8.8.6/8.7.5/IShub#2) with ESMTP id IAA14804 for ; Fri, 12 Mar 1999 08:20:45 +0200 (GMT) Received: from hangdog.is.co.za (hangdog.is.co.za [196.26.1.216]) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) with ESMTP id IAA10216 for ; Fri, 12 Mar 1999 08:20:44 +0200 (GMT) Received: (from geoff@localhost) by hangdog.is.co.za (8.9.3/8.9.2) id IAA09997 for hackers@freebsd.org; Fri, 12 Mar 1999 08:20:43 +0200 (SAST) (envelope-from geoff) From: Geoff Rehmet Message-Id: <199903120620.IAA09997@hangdog.is.co.za> Subject: The infamours "temp cleaner" debate To: hackers@freebsd.org Date: Fri, 12 Mar 1999 08:20:43 +0200 (SAST) Reply-To: "Geoff Rehmet" 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 Hmm, yes, after everyone though that one had been put to bed. I've been trying to write a script that is not susceptible to security problems, to handle my temp cleaning - delete old files from /tmp and /var/tmp. The idea was to write it in Perl, without running any external commands, and sitting in a chroot jail. That way, it should (I hope) not be possible for anyone to exploit any race conditions, and subvert my script to delete any file on the system. The script is somewhat paranoid about re-stat(2)ing things that have alrrady been stat(2)ed, in case there is any change in the unerlying directory strcuture that it is traversing. (If it gets unconfortable, it bails.) Now I'm ready to throw it open for comments. If it lives up to scrutiny here, and there is general agreement, I'd like to commit it, to have a better replacement for the (currently disabled) mechanism in /etc/periodic/daily. Another use for the script is to periodically clean out /usr/share/man/cat?. I've also included my version of /etc/periodic/daily/110.clean-tmps. (Watch out for the overlong lines in this file.) 110.clean-tmps should be a bit more elegant, allowing people to specifify how many days to keep files for etc. Especially useful, would be any suggestions to make the script more paranoid. Also, the name "purgeold" sucks - can anyone think of a better one? Geoff. --- snip, snip -- /usr/local/bin/purgeold ----------------------- #!/usr/bin/perl # # Copyright (c) 1999 Geoffrey M. Rehmet # All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # 3. All advertising materials mentioning features or use of this software # must display the following acknowledgement: # This product includes software developed by Geoffrey M. Rehmet # 4. The name of Geoffrey M Rehmet may not be used to endorse or promote # products derived from this software without specific prior written # permission. # # THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. # IN NO EVENT SHALL GEOFFREY M. REHMET BE LIABLE FOR ANY DIRECT, # INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $Id$ # # # Purge old files from a temp dir. Runs in a chroot jail # and does not call any external executable programs. # use Cwd; # Defaults - some are args, some should be args $REMOVETIME = 7; # Delete older than 1 week $VERBOSE = 0; # By default, be terse $DOIT = 1; # Actually delete files $ENV{'PATH'}=''; $SIG{'INT'}='IGNORE'; $SIG{'QUIT'}='IGNORE'; if ( @ARGV < 1 ) { usage(); } while ( $arg = shift ) { if ($arg eq '-v') { $VERBOSE = 1; } elsif ($arg eq '-d') { $REMOVETIME = shift; } elsif ($arg eq '-n') { $DOIT = 0 ; $VERBOSE = 1; } elsif ($arg eq '-xf') { push @EXCLUDE_FILE, shift ; } elsif ($arg eq '-xd') { push @EXCLUDE_DIR, shift ; } elsif ($arg =~ "^-.*") { die "invalid argument $arg"; } else { $TMPDIR = $arg ; } } $TMPDIR eq '' && die "No temp directory specified"; $TMPDIR =~ '\/$' || ( $TMPDIR = "$TMPDIR/" ); # make sure path ends with '/' $TMPDIR =~ "^\/" || die "$TMPDIR is not an absolute path"; verbose ("Clearing files older than $REMOVETIME days from $TMPDIR\n"); $basedir = ""; # We start out at the root ($TMPDIR already starts with "/") # Check that we have a directory # Use stat (rather than lstat) - we are happy to follow a symlink on this # one occasion stat $TMPDIR || die "Cannot stat $TMPDIR"; if (-d _ ) { if ($> == 0){ (chroot $TMPDIR) || die "Could not chroot to $TMPDIR" ; # Dir to clean is now our root dir! $basedir = $TMPDIR; # Remember our old starting point $basedir =~ s/\/$//; # Remove trailing '/' from base $TMPDIR="/"; } chdir($TMPDIR) || die "Cannot chdir to $TMPDIR"; do_dir($TMPDIR); exit 0; } else { die "$TMPDIR is not a directory" } # # Recursively handle each directory # sub do_dir ($) { my $item = shift; my $direntry; my @dirs; my $wdir; my $subdir; # Keep a record of where we are # This is used later to see if anyone has changed things while we # weren't looking $wdir = cwd; # Open dir and get rid of "." and ".." (opendir DIRHND, ".") || die "Cannot open directory $item"; (readdir DIRHND) || die "Error reading $item"; # Chomp "." (readdir DIRHND) || die "Error reading $item"; # Chomp ".." # Go through directory entries, keeping subdirectories for later # attention. while ($direntry = readdir DIRHND) { lstat $direntry || die "Cannot stat $direntry"; if (-d _ ) { # Keep subdirectories for later use -l $direntry && die "$direntry is a symlink"; $skip = 0; for ($j = 0 ; $j < @EXCLUDE_DIR; $j++) { $skip = $skip || ($direntry =~ /\A$EXCLUDE_DIR[$j]\Z/); } $skip || push @dirs, $direntry; } else { # We've got a regular file, device, symlink, named pipe or socket $skip = 0; for ($j = 0 ; $j < @EXCLUDE_FILE; $j++) { $skip = $skip || ($direntry =~ /\A$EXCLUDE_FILE[$j]\Z/); } if (!$skip) { lstat $direntry || die "cannot stat $direntry"; if ( -A _ > $REMOVETIME) { verbose ("Deleting ${basedir}${item}${direntry}\n"); $DOIT && ( unlink $direntry || die "Could not delete $direntry"); } } } } closedir DIRHND; # Now traverse subdirectories while ( $subdir = pop @dirs ) { lstat($subdir) || die "Cannot stat $subdir"; -d _ || die "$subdir is no longer a directory!!"; chdir ($subdir) || die "Could not chdir from $item to $subdir"; do_dir("${item}${subdir}/"); # We intentionally "chdir .." chdir ("..") || die "Could not chdir to parent"; # Check that we are where we think we are if (cwd ne $wdir ) { $newwd = cwd; die "$newwd != $wdir: Directory has been moved or deleted!"; } # Now check if we need to delete the subdirectory (stat again) lstat $subdir || die "cannot stat $subdir"; if ( -M _ > $REMOVETIME ) { verbose ("Deleting directory ${basedir}${item}${subdir}\n"); $DOIT && rmdir $subdir; } } } # # print verbose messages # sub verbose ($) { my $message = shift; $VERBOSE && print STDERR $message; } # # Print usage message # sub usage ($) { print STDERR "Usage: $0 [-v] [-d ] [-xf ] [-xd ] [-n]\n"; print STDERR " options:\n"; print STDERR " -v: print verbose messages\n"; print STDERR " -d : delete files older than n days\n"; print STDERR " -n : Don't delete any files (turns on verbose)\n"; print STDERR " -xf : Do not delete files matching regex f\n"; print STDERR " -xd : Do not delete directories matching regex d\n"; print STDERR "\n"; print STDERR "-xf and -xd may be repeated\n"; exit (1); } --- snip, snip -- /etc/periodic/daily/110.clean-tmps------------- #!/bin/sh # # $Id: 110.clean-tmps,v 1.3 1997/09/11 15:21:30 ache Exp $ # # if [ -d /tmp ]; then /usr/local/bin/purgeold /tmp -d 4 -xf '\.X.*-lock' -xf 'quotas' -xd 'lost+found' -xd '\.X11-unix' -v fi if [ -d /var/tmp ]; then /usr/local/bin/purgeold /var/tmp -d 4 -xd 'vi.recover' -xf 'quotas' -xd 'lost+found' -v fi ----------------------------------------------------------------- -- Geoff Rehmet, The Internet Solution - Infrastructure tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23: 4:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id E038214FF2 for ; Thu, 11 Mar 1999 23:04:23 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id AAA02475; Fri, 12 Mar 1999 00:03:58 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36E8BC5E.66F7AC89@softweyr.com> Date: Fri, 12 Mar 1999 00:03:58 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Charles Mott Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Mott wrote: > > On Thu, 11 Mar 1999, Amancio Hasty wrote: > > You probably don't need their funky NIC card in all likelyhood their nic card > > is an ethernet > > card and if so you may want to kindly give TCI their "NIC Card" back --- > > they really > > ought to specify what exactly do they mean by "NIC Card". > > > > Amancio > > The question is, how are IP addresses assigned? The Time Warner "Road > Runner" system is known to use a DHCP-like mechanism which has been > deciphered. I haven't read anything about @Home. Of course, static > addressing would be preferable. From their FAQ it sounds like they give you a single static address. With NAT, that's entire enough, now isn't it? ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23:38:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp1.pcnet.ro (uucp1.pcnet.ro [193.230.188.6]) by hub.freebsd.org (Postfix) with ESMTP id E262D14CB6 for ; Thu, 11 Mar 1999 23:37:41 -0800 (PST) (envelope-from fnicoles@pcnet.pcnet.ro) Received: (from uucp@localhost) by uucp1.pcnet.ro (8.8.5/8.8.5) with UUCP id JAA10074 for freebsd-hackers@FreeBSD.ORG; Fri, 12 Mar 1999 09:33:07 +0200 Received: (from nick@localhost) by nick.ro (8.8.8/8.8.8) id JAA11891 for freebsd-hackers@FreeBSD.ORG; Fri, 12 Mar 1999 09:31:14 +0200 (EET) (envelope-from nick) From: Florin Nicolescu Message-Id: <199903120731.JAA11891@nick.ro> Subject: Y2K bug To: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) Date: Fri, 12 Mar 1999 09:31:13 +0200 (EET) X-OS: FreeBSD-2.2.7-RELEASE X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, According to the discontinuities in the earth move around the sun, once a four years there is inserted an extra day (29 of February), but once a 400 years (when the first 2 digits of the year divide by 4) it is not added. This is the case for 2000 (20 mod 4 = 0). When I inserted the date 29 of February 2000 in FreeBSD, it has accepted it OK, meaning that it believes that 2000 has the date 29 of Feb. I don't know about other systems, but I know that a lot of people ignore this rule (I've just looked into my agenda, and it has the same error). Ciao, Nick -- ------------------------------------------------------------------ | Florin-Nicolae Nicolescu | | University of Bucharest, Faculty of Mathematics | | Bucharest,Romania | ------------------------------------------------------------------ | Friends don't let friends use Windows. | | Double your hard drive space instantly! Delete Windows! | ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23:42:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4C50814BF2 for ; Thu, 11 Mar 1999 23:42:27 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id HAA64237; Fri, 12 Mar 1999 07:42:09 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA16875; Fri, 12 Mar 1999 00:42:17 -0700 (MST) Message-Id: <199903120742.AAA16875@harmony.village.org> To: "Geoff Rehmet" Subject: Re: The infamours "temp cleaner" debate Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Mar 1999 08:20:43 +0200." <199903120620.IAA09997@hangdog.is.co.za> References: <199903120620.IAA09997@hangdog.is.co.za> Date: Fri, 12 Mar 1999 00:42:17 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903120620.IAA09997@hangdog.is.co.za> Geoff Rehmet writes: : Hmm, yes, after everyone though that one had been put to bed. : I've been trying to write a script that is not susceptible to : security problems, to handle my temp cleaning - delete old files : from /tmp and /var/tmp. How is this not handled by fts(3) now? It does the race condition proof algorythm. Also, I believe that find -delete also is immune to the race conditions as well. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23:49: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2B08815210 for ; Thu, 11 Mar 1999 23:48:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id HAA64248; Fri, 12 Mar 1999 07:48:40 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA16897; Fri, 12 Mar 1999 00:48:48 -0700 (MST) Message-Id: <199903120748.AAA16897@harmony.village.org> To: "Geoff Rehmet" Subject: Re: The infamours "temp cleaner" debate Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Mar 1999 08:20:43 +0200." <199903120620.IAA09997@hangdog.is.co.za> References: <199903120620.IAA09997@hangdog.is.co.za> Date: Fri, 12 Mar 1999 00:48:48 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is at least one winnable race here. If someone changed the dierctory between the -d and chdir, then you could chdir someplace else. In message <199903120620.IAA09997@hangdog.is.co.za> Geoff Rehmet writes: : lstat($subdir) || die "Cannot stat $subdir"; : -d _ || die "$subdir is no longer a directory!!"; attacker removes subdir and replaces it with a symbolic link to some other place in the tree. : chdir ($subdir) || die "Could not chdir from $item to $subdir"; boom. You have just followed the symbolic link. You are now in the wrong part of the tree. Files start to disappear from places they shouldn't disappear from. : do_dir("${item}${subdir}/"); : : # We intentionally "chdir .." : chdir ("..") || die "Could not chdir to parent"; And you compound the problem by using relative paths. fts(3) handles these problems already. Unless you can do a fchdir, you won't solve the races that are plague this problem. Finally, you die too much. An attacker could launch a denial of service attack against cleaning programs which would cause them not to run. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23:53: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 63E5C14BF2 for ; Thu, 11 Mar 1999 23:51:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id HAA64258; Fri, 12 Mar 1999 07:51:27 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA16925; Fri, 12 Mar 1999 00:51:36 -0700 (MST) Message-Id: <199903120751.AAA16925@harmony.village.org> To: Florin Nicolescu Subject: Re: Y2K bug Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) In-reply-to: Your message of "Fri, 12 Mar 1999 09:31:13 +0200." <199903120731.JAA11891@nick.ro> References: <199903120731.JAA11891@nick.ro> Date: Fri, 12 Mar 1999 00:51:35 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903120731.JAA11891@nick.ro> Florin Nicolescu writes: : According to the discontinuities in the earth move around the sun, : once a four years there is inserted an extra day (29 of February), : but once a 400 years (when the first 2 digits of the year divide by : 4) it is not added. This is the case for 2000 (20 mod 4 = 0). When I : inserted the date 29 of February 2000 in FreeBSD, it has accepted it : OK, meaning that it believes that 2000 has the date 29 of Feb. I : don't know about other systems, but I know that a lot of people : ignore this rule (I've just looked into my agenda, and it has the : same error). Feb 29, 2000 is a leap year. Your leap year rule is wrong. The correct rule is as follows if (year is divisible by 4) -> leap year unless also divisible by 100 -> not a leap year (eg 1900) unless also divisible by 400 -> leap year (eg 2000) FreeBSD (and most systems) handles this correctly. It is not a bug. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 11 23:57:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8D3E6151CF for ; Thu, 11 Mar 1999 23:57:34 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id HAA64274; Fri, 12 Mar 1999 07:57:16 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA16980; Fri, 12 Mar 1999 00:57:24 -0700 (MST) Message-Id: <199903120757.AAA16980@harmony.village.org> Subject: Re: Y2K bug Cc: Florin Nicolescu , freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) In-reply-to: Your message of "Fri, 12 Mar 1999 00:51:35 MST." <199903120751.AAA16925@harmony.village.org> References: <199903120751.AAA16925@harmony.village.org> <199903120731.JAA11891@nick.ro> Date: Fri, 12 Mar 1999 00:57:24 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199903120751.AAA16925@harmony.village.org> Warner Losh writes: : Feb 29, 2000 is a leap year. Your leap year rule is wrong. The I hate to follow up my own post. 2000 is a leap year. The leap day is added on Feb 29. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 0:45:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B9DAE1525B for ; Fri, 12 Mar 1999 00:44:43 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA16503; Fri, 12 Mar 1999 00:36:04 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdg16484; Fri Mar 12 08:36:02 1999 Date: Fri, 12 Mar 1999 00:35:57 -0800 (PST) From: Julian Elischer To: Florin Nicolescu Cc: FreeBSD-hackers Subject: Re: Y2K bug In-Reply-To: <199903120731.JAA11891@nick.ro> 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 no if ((Year % 4) == 0) { if ((Year % 100) == 0) { if (( Year % 400) == 0) { Feb = 29; } else { Feb = 28; } } else { Feb = 29; } } else { Feb = 28; } On Fri, 12 Mar 1999, Florin Nicolescu wrote: > Hi, > > According to the discontinuities in the earth move around the sun, once > a four years there is inserted an extra day (29 of February), but once a > 400 years (when the first 2 digits of the year divide by 4) it is not > added. This is the case for 2000 (20 mod 4 = 0). When I inserted the > date 29 of February 2000 in FreeBSD, it has accepted it OK, meaning that > it believes that 2000 has the date 29 of Feb. I don't know about other > systems, but I know that a lot of people ignore this rule (I've just > looked into my agenda, and it has the same error). > > Ciao, > Nick > > -- > ------------------------------------------------------------------ > | Florin-Nicolae Nicolescu | > | University of Bucharest, Faculty of Mathematics | > | Bucharest,Romania | > ------------------------------------------------------------------ > | Friends don't let friends use Windows. | > | Double your hard drive space instantly! Delete Windows! | > ------------------------------------------------------------------ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 1:23:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id C4EAE14BCD for ; Fri, 12 Mar 1999 01:22:34 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id LAA94258; Fri, 12 Mar 1999 11:18:41 +0200 (EET) (envelope-from ru) Date: Fri, 12 Mar 1999 11:18:41 +0200 From: Ruslan Ermilov To: Julian Elischer Cc: Florin Nicolescu , FreeBSD-hackers Subject: Re: Y2K bug Message-ID: <19990312111841.A91406@relay.ucb.crimea.ua> Mail-Followup-To: Julian Elischer , Florin Nicolescu , FreeBSD-hackers References: <199903120731.JAA11891@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Julian Elischer on Fri, Mar 12, 1999 at 12:35:57AM -0800 X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Or, according to Kernighan & Ritchie's "The C Programming Language", Second Edition: if (Year % 4 == 0 && Year % 100 != 0 || Year % 400 == 0) Feb = 29; else Feb = 28; On Fri, Mar 12, 1999 at 12:35:57AM -0800, Julian Elischer wrote: > > > no > > > if ((Year % 4) == 0) { > if ((Year % 100) == 0) { > if (( Year % 400) == 0) { > Feb = 29; > } else { > Feb = 28; > } > } else { > Feb = 29; > } > } else { > Feb = 28; > } > > > > On Fri, 12 Mar 1999, Florin Nicolescu wrote: > > > Hi, > > > > According to the discontinuities in the earth move around the sun, once > > a four years there is inserted an extra day (29 of February), but once a > > 400 years (when the first 2 digits of the year divide by 4) it is not > > added. This is the case for 2000 (20 mod 4 = 0). When I inserted the > > date 29 of February 2000 in FreeBSD, it has accepted it OK, meaning that > > it believes that 2000 has the date 29 of Feb. I don't know about other > > systems, but I know that a lot of people ignore this rule (I've just > > looked into my agenda, and it has the same error). > > > > Ciao, > > Nick > > > > -- > > ------------------------------------------------------------------ > > | Florin-Nicolae Nicolescu | > > | University of Bucharest, Faculty of Mathematics | > > | Bucharest,Romania | > > ------------------------------------------------------------------ > > | Friends don't let friends use Windows. | > > | Double your hard drive space instantly! Delete Windows! | > > ------------------------------------------------------------------ > > Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 2:25:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1F58914CA5 for ; Fri, 12 Mar 1999 02:25:48 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA01802; Fri, 12 Mar 1999 19:25:26 +0900 (JST) Message-ID: <36E8E69E.6824D76F@newsguy.com> Date: Fri, 12 Mar 1999 19:04:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Florin Nicolescu Cc: FreeBSD-hackers Subject: Re: Y2K bug References: <199903120731.JAA11891@nick.ro> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Florin Nicolescu wrote: > > According to the discontinuities in the earth move around the sun, once a four years there > is inserted an extra day (29 of February), but once a 400 years (when the first 2 digits of > the year divide by 4) it is not added. This is the case for 2000 (20 mod 4 = 0). When I > inserted the date 29 of February 2000 in FreeBSD, it has accepted it OK, meaning that it > believes that 2000 has the date 29 of Feb. I don't know about other systems, but I know that a lot > of people ignore this rule (I've just looked into my agenda, and it has the same error). I think it was 1900 which did not have Feb 29. Meaning we are safe until 2300. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "My theory is that his ignorance clouded his poor judgment." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 2:59:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 60C50152F7 for ; Fri, 12 Mar 1999 02:59:00 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:W+kxtElfd118hTO7X2/yrxUO4RfA/Vc2@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id TAA06997; Fri, 12 Mar 1999 19:58:24 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA09690; Fri, 12 Mar 1999 20:01:33 +0900 (JST) Message-Id: <199903121101.UAA09690@zodiac.mech.utsunomiya-u.ac.jp> To: Jonathan Walther Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: recommended VESA compliant cards for fbsd? In-reply-to: Your message of "Thu, 11 Mar 1999 18:22:29 PST." References: Date: Fri, 12 Mar 1999 20:01:32 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Once again, thank you. May I ask which cards you would recommend? I am >looking to kick this thing into TrueColor RGB mode. Sorry, I don't have any recommendation. In the VESA specification, video cards are not required to support any particular video modes. It is entirely up to the vendor to decide which video modes to support. We have to find out which mode is supported on which card. I don't have the list of supported video modes in each and every modern VGA card. (If there exists such a list, I would be most interested, though.) The current situation is "If the VESA BIOS Extension of your card does not support the video mode you want, bad luck." Oh, well... I personally use Millennium, which supports VBE 2.0, to test the vesa module. But, it doesn't mean that I find that this card is in any way better than the others regarding the VESA BIOS support. It is that this card just happens to be in my box... I used to have a no-name, S3-968 based card with VBE 1.2, and it worked well too. >Even normal VGA stuff >tends to flake out, as the new cards don't seem to support VGA fully now >that they support VESA. I don't know if the VBE support is the reason why a vendor no longer bothers to provide full support for all standard VGA modes. If the vendor is only interested in W*ndows market, I suspect they may decide to drop support for VBE as well as the standard VGA support, entirely or partially, and provide a W*ndows driver only. Kazu >Jonathan > >On Fri, 12 Mar 1999, Kazutaka YOKOTA wrote: >> 3. Your VESA ROM BIOS does not support this particular video mode. >> Your video "card" may support it, but its "ROM BIOS" may not. This >> may sound strange, but it is permissible in the VESA BIOS extension >> standard; the ROM BIOS includes minimal "stub" for the VESA extension >> and a DOS TSR (oh, good-old DOS TSR!) implements the full VESA BIOS >> services. Because video ROM space is limited, the vendor may find it >> difficult to implement full VESA BIOS specification in ROM... >> (I don't know if we can support the VESA TSR in vm86...) >> vidcontrol -i mode To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 8:51:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 0878D14D9A for ; Fri, 12 Mar 1999 08:49:53 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id JAA03572; Fri, 12 Mar 1999 09:48:55 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36E94577.F90221F8@softweyr.com> Date: Fri, 12 Mar 1999 09:48:55 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel C. Sobral" Cc: Florin Nicolescu , FreeBSD-hackers Subject: Re: Y2K bug References: <199903120731.JAA11891@nick.ro> <36E8E69E.6824D76F@newsguy.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 C. Sobral" wrote: > > I think it was 1900 which did not have Feb 29. Meaning we are safe > until 2300. :-) No, just 2100. if !(year % 400) you are in a leap century, and have to add an extra day. This will happen again in 2400. I don't plan to stay up that late. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 9:20: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id CEC241538B for ; Fri, 12 Mar 1999 09:19:57 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id MAA00881; Fri, 12 Mar 1999 12:19:27 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199903121719.MAA00881@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: from Charles Mott at "Mar 11, 99 11:05:21 pm" To: cmott@scientech.com (Charles Mott) Date: Fri, 12 Mar 1999 12:19:27 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Charles Mott wrote, > On Thu, 11 Mar 1999, Amancio Hasty wrote: > > You probably don't need their funky NIC card in all likelyhood their nic card > > is an ethernet > > card and if so you may want to kindly give TCI their "NIC Card" back --- > > they really > > ought to specify what exactly do they mean by "NIC Card". > > > > Amancio > > The question is, how are IP addresses assigned? The Time Warner "Road > Runner" system is known to use a DHCP-like mechanism which has been > deciphered. I haven't read anything about @Home. Of course, static > addressing would be preferable. As my address implies, I have @Home service. Specifically, I have Comcast@Home in NJ. I have had the same IP since I got service (in October). I was left a little data sheet by the "techncian[1]" who installed my NIC with the IP addresses of my machine and the DNS. I had to guess at the gateway. I have used DHCP to see if anyone out there is listening and there is no DHCP server on my LAN. I assume that means we are static. BTW, back to the NIC, the one they put in my machine is a pretty generic piece of equipment that has never given me any grief[2], % dmesg [snip] de0 rev 33 int a irq 11 on pci0:14:0 de0: SMC 21041 [10Mb/s] pass 2.1 [snip] I asked on the phone about NICs before I got my service, and they told me they just use off-the-shelf products that they can get a good deal on at the moment. Typically, the techie that comes brings some ISA and PCI ones depending on what there is room for in your machine. [1] Mine looked like she could have been an extra from that new 'Carrie 2' movie. If she was out of highschool, she fooled me. [2] But coax is not always all it is cracked up to be. At the moment I am suffering through about 20% packet loss. I am 'ssh'ed into my home computer from work. Coax cable on one end, a fractional T1 here at work.. but with the ploss it is worse than a modem. Here's a snip of my traceroute, 6 phl0-1.pne0-1.verio.net (129.250.2.133) 10.136 ms 10.292 ms 13.204 ms 7 sprint-nap.home.net (192.157.69.85) 13.015 ms 15.612 ms 19.236 ms 8 * * * 9 * r1.rdc1.nj.home.net (24.3.128.2) 66.767 ms 56.600 ms 10 * cr2.ewndsr1.nj.home.net (24.3.196.55) 73.549 ms 69.407 ms 11 cc942873-a.ewndsr1.nj.home.com (24.2.89.207) 109.903 ms * 80.967 ms Problem looks to be inside of @Home. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:15:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CDB69152F7 for ; Fri, 12 Mar 1999 10:15:15 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id TAA52426; Fri, 12 Mar 1999 19:14:57 +0100 (CET) (envelope-from des) To: hackers@freebsd.org Subject: Proposed patch to /etc/rc From: Dag-Erling Smorgrav Date: 12 Mar 1999 19:14:56 +0100 Message-ID: Lines: 23 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anybody have any objections to the attached patch? It fixes pty ownership at boot time so last doesn't show users as "still logged in" after a reboot. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.180 diff -u -r1.180 rc --- rc 1999/03/11 16:17:24 1.180 +++ rc 1999/03/12 18:06:41 @@ -172,6 +172,7 @@ # Whack the pty perms back into shape. chmod 666 /dev/tty[pqrsPQRS]* +chown root.tty /dev/tty/[pqrsPQRS]* # clean up left-over files clean_var # If it hasn't already been done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:15:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id C63C715385 for ; Fri, 12 Mar 1999 10:15:41 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from scientia.demon.co.uk (ident=ben) by scientia.demon.co.uk with local (Exim 2.12 #2) id 10LUra-000Et4-00; Fri, 12 Mar 1999 16:32:42 +0000 (envelope-from ben@scientia.demon.co.uk) Date: Fri, 12 Mar 1999 16:32:42 +0000 From: Ben Smithurst To: Florin Nicolescu Cc: FreeBSD-hackers Subject: Re: Y2K bug Message-ID: <19990312163242.A57183@scientia.demon.co.uk> References: <199903120731.JAA11891@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199903120731.JAA11891@nick.ro> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Florin Nicolescu wrote: > According to the discontinuities in the earth move around the sun, > once a four years there is inserted an extra day (29 of February), but > once a 400 years (when the first 2 digits of the year divide by 4) it > is not added. No. Once every _100_ years it is not added, _except_ every 400th years (1600, 2000, etc), when it _is_ added. This is my understanding anyway, I may be wrong. > When I inserted the date 29 of February 2000 in FreeBSD, it has > accepted it OK, meaning that it believes that 2000 has the date 29 of > Feb. It does. 2100 won't, however, if my understanding is correct. -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:29:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id E87941557D; Fri, 12 Mar 1999 10:28:44 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id UAA31696; Fri, 12 Mar 1999 20:21:35 +0200 (EET) (envelope-from ru) Date: Fri, 12 Mar 1999 20:21:35 +0200 From: Ruslan Ermilov To: jkh@freebsd.org Cc: FreeBSD Hackers Subject: doscmd is disabled in RELENG_3 Message-ID: <19990312202135.A30044@relay.ucb.crimea.ua> Mail-Followup-To: jkh@freebsd.org, FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! It seems it's safe now to re-enable doscmd in RELENG_3. What do you think? RCS file: /usr/FreeBSD-CVS/src/usr.bin/Makefile,v Working file: /usr/src/usr.bin/Makefile head: 1.123 branch: locks: strict access list: keyword substitution: kv total revisions: 145; selected revisions: 1 description: ---------------------------- revision 1.114 date: 1998/09/25 02:15:56; author: jkh; state: Exp; lines: +1 -2 Take doscmd back out - it relies on installed X components to build (!). ============================================================================= Cheers, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:40:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.energyinteractive.com (mail.energyinteractive.com [204.217.253.66]) by hub.freebsd.org (Postfix) with ESMTP id 01A94155E6 for ; Fri, 12 Mar 1999 10:40:37 -0800 (PST) (envelope-from frf@energyinteractive.com) Received: from eimail.energyinteractive.com (primary.energyinteractive.com [204.217.253.254]) by mail.energyinteractive.com (8.9.2/8.9.1) with ESMTP id KAA14379 for ; Fri, 12 Mar 1999 10:40:18 -0800 (PST) (envelope-from frf@energyinteractive.com) Received: from energyinteractive.com ([192.168.20.5]) by eimail.energyinteractive.com (Netscape Messaging Server 3.5) with ESMTP id 259 for ; Fri, 12 Mar 1999 10:40:21 -0800 Message-ID: <36E95F91.5AA0DEFE@energyinteractive.com> Date: Fri, 12 Mar 1999 10:40:17 -0800 From: "Robert Faulds" X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) References: <199903120227.SAA22664@hpfsvr02.cup.hp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG TCI's tech gave me a 3C900B. No problems. Tci uses DHCP, but it uses a unique hostname (installing their software changed my hostname to something like B9182734-B) to get a preassigned IP address. This address was printed, along with default route, on the top of the work order. One thing that was missing were name servers. The biggest "suprise" was when running FreeBSD, I was getting close to 2Mbs downstream, and 512Kbs upstream. When I booted NT, It was pretty close to 512Kbs both directions. At first I laughed and blamed it on Windoze, but upon closer inspection I found that installing the @home software set a bunch of NT registry setting to limit my bandwidth. Client-side throttling. I reinstalled windows (like I do every week), didn't install their software, and 'bingo' 1.5Mbs downstream. Of course, now I do not have access to an @home email address, but heh, like I don't have enough already. I still use thier http cache although it took a little work to find. Basically, I am very happy with the service, but beware. -- frf@energyinteractive.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:41:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (Postfix) with ESMTP id 6060014D53 for ; Fri, 12 Mar 1999 10:41:37 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id KAA08889; Fri, 12 Mar 1999 10:41:06 -0800 Date: Fri, 12 Mar 1999 10:41:06 -0800 (PST) From: Neal Westfall To: cjclark@home.com Cc: Charles Mott , freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: <199903121719.MAA00881@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Mar 1999, Crist J. Clark wrote: > > As my address implies, I have @Home service. Specifically, I have > Comcast@Home in NJ. So does this mean that @home does not really enforce their policy of "no servers of any kind" that appears in their FAQ? I have heard of some horror stories with them canceling people's accounts for running Quake (only temporary sessions, not full-time servers). -- Neal Westfall mailto:nwestfal@odc.net http://www.odc.net/~nwestfal/ FreeBSD: The Power To Serve! http://www.freebsd.org/ $Id: dot.signature,v 1.2 1998/12/30 08:23:13 nwestfal Exp nwestfal $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 10:47:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (Postfix) with ESMTP id 6164E15657 for ; Fri, 12 Mar 1999 10:47:48 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id MAA03488; Fri, 12 Mar 1999 12:47:21 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19990312124719.03ba4b00@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 12 Mar 1999 12:47:19 -0600 To: Florin Nicolescu From: Tony Overfield Subject: Re: Y2K bug Cc: freebsd-hackers@FreeBSD.ORG (FreeBSD-hackers) In-Reply-To: <199903120751.AAA16925@harmony.village.org> References: <199903120731.JAA11891@nick.ro> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <199903120731.JAA11891@nick.ro> Florin Nicolescu writes: > > According to the discontinuities in the earth move around the sun, Of course, this is wrong too. A year doesn't come out to a whole number of days, so adjustments are made whenever the error builds up sufficiently. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 11: 8:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 8A1AC154BA; Fri, 12 Mar 1999 11:08:25 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.8.8) id OAA01095; Fri, 12 Mar 1999 14:07:43 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199903121907.OAA01095@cc942873-a.ewndsr1.nj.home.com> Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-Reply-To: from Neal Westfall at "Mar 12, 99 10:41:06 am" To: nwestfal@Vorlon.odc.net (Neal Westfall) Date: Fri, 12 Mar 1999 14:07:43 -0500 (EST) Cc: cmott@scientech.com, freebsd-questions@freebsd.org Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This has totally diverged from -hackers scope. Headers set so followups are going to -questions.] Neal Westfall wrote, > On Fri, 12 Mar 1999, Crist J. Clark wrote: > > > > > As my address implies, I have @Home service. Specifically, I have > > Comcast@Home in NJ. > > So does this mean that @home does not really enforce their policy > of "no servers of any kind" that appears in their FAQ? I have > heard of some horror stories with them canceling people's accounts > for running Quake (only temporary sessions, not full-time servers). To quote from the service agreement (note the caps are how it appears in the agreement), "(b)In addition, Customer agrees not to: . . . viii) RESELL THE SERVICE OR OTHERWISE CHARGE OTHERS TO USE THE SERVICE, IN WHOLE OR IN PART, DIRECTLY OR INDIRECTLY, OR ON A BUNDLED OR UNUNBUNDLED BASIS. THE SERVICE IS TO BE USED SOLELY IN A PRIVATE RESIDENCE; LIVING QUARTERS IN A HOTEL, HOSPITAL, DORM, SORORITY OR FRATERNITY HOUSE, OR BOARDING HOUSE; OR THE RESIDENTIAL PORTION OF A PREMISES USED FOR BOTH BUSINESS AND RESIDENTIAL PURPOSES. THE SERVICE IS FOR PERSONAL AND NON-COMMERCIAL USE ONLY AND CUSTOMER AGREES NOT TO USE THE SERVICE FOR OPERATION AS AN INTERNET SERVICE PROVIDER, A SERVER SITE FOR FTP, TELNET, RLOGIN, E-MAIL HOSTING, "WEB HOSTING" OR OTHER SIMILAR APPLICATIONS, FOR ANY BUSINESS ENTERPRISE INCLUDING, BUT NOT LIMITED TO, THOSE IN COMPETITION WITH THE SERVICE, OR AS AN END-POINT ON A NON-COMCAST LOCAL AREA NETWORK OR WIDE AREA NETWORK; or" My reading, and I am no lawyer, says to me that you cannot set up a server "for any business enterprises." Typically, it is written in precise legallese that is actually quite poor at getting the point across. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 13: 9:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 708071536B for ; Fri, 12 Mar 1999 13:09:43 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA19872 for hackers@freebsd.org; Fri, 12 Mar 1999 16:16:14 -0500 From: Bill Paul Message-Id: <199903122116.QAA19872@skynet.ctr.columbia.edu> Subject: Gigabit ethernet -- what am I doing wrong? To: hackers@freebsd.org Date: Fri, 12 Mar 1999 16:16:13 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2852 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I have my Tigon driver working to the point where I can now exchange traffic with another machine. But no matter what I do, I can't seem to get my gigabit ethernet device to generate more than 200Mbps on transmit. I'm confused. The machines I'm using are Dell workstations with Pentium II 400Mhz CPUs, 128MB of RAM, Adaptec 2940UW2 SCSI controller (the disk is idle during the tests though). The cards are Netgear GA620s. One machine runs FreeBSD 3.1-RELEASE, the other LoseNT 4 (service pack 3). The FreeBSD 3.1 host reports: CPU: Pentium II/Xeon/Celeron (397.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 127016960 (124040K bytes) [...] chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 [...] ti0: rev 0x01 int a irq 11 on pci0.13.0 ti0: Ethernet address: 00:a0:cc:73:31:4a ahc0: rev 0x03 int a irq 10 on pci0.14.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int b irq 14 on pci0.14.1 ahc1: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs chip4: rev 0x03 on pci0.15.0 Even using jumbo frames, I can't get more than about 200Mbps on transmit. The LoseNT machine doens't seem to be able to get above 200Mbps either (I don't have a decent way to test it, but from what I can tell it's in about the same ballpark, maybe a little slower). Note that I am not doing checksum offloading. I can get around 450Mbps through the loopback interface on these machines, so I'm pretty sure the bottleneck isn't in the IP stack. I don't think I've done anything blazingly stupid in the code. (Those of you who are curious can look at http://www.freebsd.org/~wpaul/Alteon/3.0/tigon.tar.gz. Note: this is not an official release or anything. Don't come asking me silly questions like "Where can I get gigabit ethernet for FreeBSD?" just because you saw this post.) Anybody have any ideas? I'm a little stumped. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 13:17: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 45EE21544B; Fri, 12 Mar 1999 13:17:03 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA24314; Fri, 12 Mar 1999 13:17:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Ruslan Ermilov Cc: jkh@FreeBSD.ORG, FreeBSD Hackers Subject: Re: doscmd is disabled in RELENG_3 In-reply-to: Your message of "Fri, 12 Mar 1999 20:21:35 +0200." <19990312202135.A30044@relay.ucb.crimea.ua> Date: Fri, 12 Mar 1999 13:17:07 -0800 Message-ID: <24312.921273427@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems it's safe now to re-enable doscmd in RELENG_3. > What do you think? Seems to work with and without X, done. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 13:21:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maila.telia.com (maila.telia.com [194.236.189.4]) by hub.freebsd.org (Postfix) with ESMTP id 1EBF1152FD for ; Fri, 12 Mar 1999 13:21:44 -0800 (PST) (envelope-from lahna@ollbox.com) Received: from d1o71.telia.com (root@d1o71.telia.com [194.237.172.245]) by maila.telia.com (8.8.8/8.8.8) with ESMTP id WAA10930 for ; Fri, 12 Mar 1999 22:21:23 +0100 (CET) Received: from k9d4 (k9d4.isdn-adv.telia.com [195.198.192.68]) by d1o71.telia.com (8.8.8/8.8.5) with SMTP id WAA20332 for ; Fri, 12 Mar 1999 22:21:22 +0100 (MET) From: "Lennart Blomstrom" To: Subject: FW: vlan Date: Fri, 12 Mar 1999 22:24:41 +0100 Message-ID: <001201be6cce$bda4a7a0$44c0c6c3@k9d4.isdn-adv.telia.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.2232.26 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I've tried to use vlan (if_vlan.c ) on 3.0 and 3.1 release . I've made a "hack" to set "parent" and "vlan#" via SIOCSETVLAN and I have changed pci/id_de.c to accept mtu > 1500. I've set MTU to 1504 on de1, used it as parent if. I'm useing an Compaq 3322 sw . It works well with ICMP and UDP and frames up to 1500 bytes, but when I try TCP (telnet or http) I get a panic. Trap 12 supervisor read, page not present. Anybody got vlan working for TCP sessions ? Am I completle off ? Please help and give me a hint where to go on. /lahna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 13:30: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id EE74F14D1C for ; Fri, 12 Mar 1999 13:29:38 -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 WAA18288 for hackers@FreeBSD.ORG; Fri, 12 Mar 1999 22:29:08 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id A9BBE883F; Fri, 12 Mar 1999 22:27:17 +0100 (CET) Date: Fri, 12 Mar 1999 22:27:17 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc Message-ID: <19990312222717.A17750@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Mar 12, 1999 at 07:14:56PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Dag-Erling Smorgrav: > Does anybody have any objections to the attached patch? It fixes pty > ownership at boot time so last doesn't show users as "still logged in" > after a reboot. > +chown root.tty /dev/tty/[pqrsPQRS]* Please use the "root:tty" form (POSIX). Apart from that, no objection. Who screamed "devfs! devfs!" in the back ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 13:58:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id 6643614F8C for ; Fri, 12 Mar 1999 13:58:55 -0800 (PST) (envelope-from chris@dei.calldei.com) Received: from localhost (chris@localhost) by dei.calldei.com (8.9.0/8.9.0) with ESMTP id OAA12052; Fri, 12 Mar 1999 14:01:04 -0800 (PST) Date: Fri, 12 Mar 1999 14:00:58 -0800 (PST) From: Chris Costello To: Ollivier Robert Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc In-Reply-To: <19990312222717.A17750@keltia.freenix.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 On Fri, 12 Mar 1999, Ollivier Robert wrote: > According to Dag-Erling Smorgrav: > > Does anybody have any objections to the attached patch? It fixes pty > > ownership at boot time so last doesn't show users as "still logged in" > > after a reboot. > > > +chown root.tty /dev/tty/[pqrsPQRS]* > > Please use the "root:tty" form (POSIX). Are there any advantages of user:group as opposed to user.group? I doubt /etc/rc is going to be portable to, say, Solaris anytime soon. (I'd look through the source if it wasn't for the miniscule problem of my disk being entirely unreadable except /usr2 and that I'm using an old 2.2 CD to boot until I get a new hard disk) > Apart from that, no objection. Who screamed "devfs! devfs!" in the back ? > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 14:25:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles321.castles.com [208.214.167.21]) by hub.freebsd.org (Postfix) with ESMTP id 9D66C15504 for ; Fri, 12 Mar 1999 14:25: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.3/8.8.8) with ESMTP id OAA01216; Fri, 12 Mar 1999 14:18:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903122218.OAA01216@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wes Peters Cc: Charles Mott , freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) In-reply-to: Your message of "Fri, 12 Mar 1999 00:03:58 MST." <36E8BC5E.66F7AC89@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 14:18:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Charles Mott wrote: > > > > On Thu, 11 Mar 1999, Amancio Hasty wrote: > > > You probably don't need their funky NIC card in all likelyhood their nic card > > > is an ethernet > > > card and if so you may want to kindly give TCI their "NIC Card" back --- > > > they really > > > ought to specify what exactly do they mean by "NIC Card". > > > > > > Amancio > > > > The question is, how are IP addresses assigned? The Time Warner "Road > > Runner" system is known to use a DHCP-like mechanism which has been > > deciphered. I haven't read anything about @Home. Of course, static > > addressing would be preferable. > > >From their FAQ it sounds like they give you a single static address. > With NAT, that's entire enough, now isn't it? ;^) A staffer at WC recently ordered service from @home, and reported that it took about 30 seconds to configure his FreeBSD system to use it, compared to about 5 reboots and 30+ minutes for W95 on the same machine. He's written up a FAQ entry for @home and is hoping that they will add it to their list. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 14:36:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id E91161553B for ; Fri, 12 Mar 1999 14:36:03 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 20276 invoked by uid 1001); 12 Mar 1999 22:35:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Mar 1999 22:35:42 -0000 Date: Fri, 12 Mar 1999 15:35:42 -0700 (MST) From: Steven Young To: freebsd-hackers@freebsd.org Subject: visual config editor Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiya. Work is progressing pretty nicely on the visual config editor (which is named vconfig, pretty creative I thought). The main time waster right now is creating the DESC file. Basically, vconfig runs through LINT, extracts all the information it needs from each entry in the LINT file, and then does a lookup in the DESC file for additional information. In the DESC file, there is a help text for each option, a list of arguments that are required for that option, and a list of arguments that aren't required, but can be present anyway. My question: Does this seem like the most efficient way to do things? Is there somewhere else I can find the information that I'm currently putting in the DESC file? Is it true that, by contributing in my own little way to the FreeBSD project, I will instantly become irresistable to members of the opposite sex? Steve. PS: If anyone wants to help me in creating the DESC file, I'd be much appreciative. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 14:41:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 44BF9153E9 for ; Fri, 12 Mar 1999 14:41:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA24808; Fri, 12 Mar 1999 14:41:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Steven Young Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor In-reply-to: Your message of "Fri, 12 Mar 1999 15:35:42 MST." Date: Fri, 12 Mar 1999 14:41:33 -0800 Message-ID: <24806.921278493@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My question: Does this seem like the most efficient way to do things? Is > there somewhere else I can find the information that I'm currently putting > in the DESC file? Is it true that, by contributing in my own little way to If you could come up with a comment syntax for LINT which wasn't too offensive, you might be able to swing that. It would, at least, consolidate the information into one file. > the FreeBSD project, I will instantly become irresistable to members of > the opposite sex? It's never worked for me, but I have it on good authority that it's at least not entirely improbable either. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 14:50:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id 627711546A for ; Fri, 12 Mar 1999 14:49:26 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 20299 invoked by uid 1001); 12 Mar 1999 22:49:03 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Mar 1999 22:49:03 -0000 Date: Fri, 12 Mar 1999 15:49:03 -0700 (MST) From: Steven Young To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor In-Reply-To: <24806.921278493@zippy.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 Fri, 12 Mar 1999, Jordan K. Hubbard wrote: > > My question: Does this seem like the most efficient way to do things? Is > > there somewhere else I can find the information that I'm currently putting > > in the DESC file? Is it true that, by contributing in my own little way to > > If you could come up with a comment syntax for LINT which wasn't too > offensive, you might be able to swing that. It would, at least, > consolidate the information into one file. Hm, well now. The help text would be pretty easy to put in the LINT file - probably something simple like just putting a comment block above each option, and that will be imported as the help text. However, as far as including a list of required/possible arguments.. hm. Are the arguments listed in the LINT file all the _possible_ arguments for a particular option, or are they just the required ones? I'm hoping it's only the required ones, because then I can just make the user fill those out and let them insert any additional options manually (for now, anyway). Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 14:59:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B8DE9153D9 for ; Fri, 12 Mar 1999 14:59:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA24928; Fri, 12 Mar 1999 14:59:53 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Steven Young Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor In-reply-to: Your message of "Fri, 12 Mar 1999 15:49:03 MST." Date: Fri, 12 Mar 1999 14:59:53 -0800 Message-ID: <24926.921279593@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hm, well now. The help text would be pretty easy to put in the LINT > file - probably something simple like just putting a comment block above > each option, and that will be imported as the help text. However, as I think the comment block should contain some sort of standardized "record" of not just help text, but possible values for certain fields (or information which denotes that they're display-only, or whatever). > far as including a list of required/possible arguments.. hm. Are the > arguments listed in the LINT file all the _possible_ arguments for a > particular option, or are they just the required ones? I'm hoping it's "Yes" :) The answer is that LINT represents something of a pastiche' of formats. Some drivers have all their flags and such enumerated there, others expect you to read the man page, etc. Nobody has ever really tried to use LINT as more than a, well, lint checker on the kernel ("does LINT still config and build?") even though it's now evolved far beyond that as a kind of documentation repository, driver checklist file ("what do we support?"), home for experimental drivers (that will never see GENERIC), etc. It is in dire need of a "given what we know now" sort of review and if you can get the end result by Bruce, you'll be able to get it by anybody. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 15: 4:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 80E05153F7 for ; Fri, 12 Mar 1999 15:04:17 -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 AAA22163 for hackers@FreeBSD.ORG; Sat, 13 Mar 1999 00:03:48 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id B41018848; Fri, 12 Mar 1999 23:51:11 +0100 (CET) Date: Fri, 12 Mar 1999 23:51:11 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc Message-ID: <19990312235111.A24106@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19990312222717.A17750@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: ; from Chris Costello on Fri, Mar 12, 1999 at 02:00:58PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Chris Costello: > Are there any advantages of user:group as opposed to user.group? None to my knowledge, it is just that user.group is supposed to be more or less deprecated. The default is not to support the '.' form but our chown, for old BSD compatibility, is compiled with -DSUPPORT_DOT (since 4.4BSD Lite). -=-=- if (ischown) { if ((cp = strchr(*argv, ':')) != NULL) { *cp++ = '\0'; a_gid(cp); } #ifdef SUPPORT_DOT else if ((cp = strchr(*argv, '.')) != NULL) { *cp++ = '\0'; a_gid(cp); } #endif -=-=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 15:16:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6E48414CBA for ; Fri, 12 Mar 1999 15:16:40 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id SAA00578; Fri, 12 Mar 1999 18:14:47 -0500 (EST) Date: Fri, 12 Mar 1999 18:14:47 -0500 (EST) From: Chuck Robey To: "Jordan K. Hubbard" Cc: Steven Young , freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor In-Reply-To: <24926.921279593@zippy.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 Fri, 12 Mar 1999, Jordan K. Hubbard wrote: > > Hm, well now. The help text would be pretty easy to put in the LINT > > file - probably something simple like just putting a comment block above > > each option, and that will be imported as the help text. However, as > > I think the comment block should contain some sort of standardized > "record" of not just help text, but possible values for certain fields > (or information which denotes that they're display-only, or whatever). Could I make a suggestion? Lint isn't a C source file, but there's a new style coming into use, starting in the Java world, but moving slowly to C and C++. It's exemplified by Java's Javadoc, or for C/C++, see the port devel/doc++. This allows one to embed tags, do even a little formatting. I'm not really convinced it's the absolutely best for this particular application (so I'd understand if you said yeccch! here) but I'd sure like to get some example of this style documentation into the FreeBSD sources. I could describe it, but I think it's better if you go look at devel/doc++. The automatically generated docs I've made in Java, well, they're simply awesome, generated right from the source code. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 15:17:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id E0F90153CD for ; Fri, 12 Mar 1999 15:17:27 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 20416 invoked by uid 1001); 12 Mar 1999 23:17:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Mar 1999 23:17:08 -0000 Date: Fri, 12 Mar 1999 16:17:08 -0700 (MST) From: Steven Young To: "Jordan K. Hubbard" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: visual config editor In-Reply-To: <24926.921279593@zippy.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 Fri, 12 Mar 1999, Jordan K. Hubbard wrote: > > Hm, well now. The help text would be pretty easy to put in the LINT > > file - probably something simple like just putting a comment block above > > each option, and that will be imported as the help text. However, as > > I think the comment block should contain some sort of standardized > "record" of not just help text, but possible values for certain fields > (or information which denotes that they're display-only, or whatever). Hm.. well, my DESC file format isn't really appropriate for use in the LINT file, as it uses up a lot of vertical space. How about: # help-text: This is the AT keyboard controller. It's great! You really # +want to include this option. # changeable-options: irq device atkbd0 at isa? tty irq 1 The possible fields might be: help-text (obvious) required-args (a list of arguments that are required, in case they aren't in the device line for whatever reason) possible-args (a list of arguments that can be in the device line, but aren't necessary) unchangeable-required-args (a list of arguments that are required, and cannot have their values changed) unchangeable-possible-args (a list of arguments that are not required, and cannot have their values changed) requires (a list of other devices/controllers/etc this option needs to function - planned, but not planned for implementation in v1) Or perhaps something a bit less verbose, but you get the idea. In addition, any arguments that are present in the LINT device line, but not mentioned explicitly in the comment block above, are assumed to be required-changeable (ie, required-args), saving a bit of typing on the part of the comment writer. Does this sound sane? Now that I actually read what I've written, it seems kind of whacky, but I'm not sure of any really "easy" ways to represent the information that needs to be represented in a manner that is simple for a program to parse. Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 16:33:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id B229A14D4C for ; Fri, 12 Mar 1999 16:33:35 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA16954 for ; Fri, 12 Mar 1999 16:33:17 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 12 Mar 1999 16:33:16 -0800 (PST) From: Doug White To: hackers@freebsd.org Subject: Will IPFW pass GRE packets? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello ... I wanted to check if IPFW will pass GRE packets in a standard config from 3.0. I'm trying to use the patched natd to translate PPTP packets and natd isn't seeing them (from what I can tell). Is there anything special I should do to make sure IP proto 47 packets are getting in and out? Thanks for any hints... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 16:35:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pobox.com (harconia-2-119.mdm.mke.execpc.com [169.207.132.247]) by hub.freebsd.org (Postfix) with SMTP id 43E3F15362 for ; Fri, 12 Mar 1999 16:34:29 -0800 (PST) (envelope-from hamilton@pobox.com) Received: (qmail 18967 invoked from network); 12 Mar 1999 18:33:38 -0600 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 12 Mar 1999 18:33:38 -0600 To: Ollivier Robert Cc: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc In-reply-to: Your message of "Fri, 12 Mar 1999 23:51:11 +0100." <19990312235111.A24106@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 18:33:38 -0600 From: Jon Hamilton Message-Id: <19990313003444.43E3F15362@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990312235111.A24106@keltia.freenix.fr>, Ollivier Robert wrote: } According to Chris Costello: } > Are there any advantages of user:group as opposed to user.group? } } None to my knowledge, it is just that user.group is supposed to be more or } less deprecated. On systems which allow a dot in the username, user.group is ambiguous. Since a colon is not legal in a username under any UNIX, user:group is not. -- 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 Fri Mar 12 16:48:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 1B78F152F7 for ; Fri, 12 Mar 1999 16:48:16 -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 LAA27099; Sat, 13 Mar 1999 11:17:57 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA06377; Sat, 13 Mar 1999 11:17:55 +1030 (CST) Message-ID: <19990313111755.N429@lemis.com> Date: Sat, 13 Mar 1999 11:17:55 +1030 From: Greg Lehey To: Ollivier Robert , hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc References: <19990312222717.A17750@keltia.freenix.fr> <19990312235111.A24106@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19990312235111.A24106@keltia.freenix.fr>; from Ollivier Robert on Fri, Mar 12, 1999 at 11:51:11PM +0100 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 Friday, 12 March 1999 at 23:51:11 +0100, Ollivier Robert wrote: > According to Chris Costello: >> Are there any advantages of user:group as opposed to user.group? > > None to my knowledge, it is just that user.group is supposed to be more or > less deprecated. My understanding is that you can have periods in user names, but obviously (see /etc/passwd) not colons. Greg - See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 19:39:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from localhost (00-60-67-24-29-83.bconnected.net [209.53.17.55]) by hub.freebsd.org (Postfix) with ESMTP id BFB6014DEF for ; Fri, 12 Mar 1999 19:39:27 -0800 (PST) (envelope-from jwalther@localhost) Received: from jwalther by localhost with local-smtp (Exim 2.11 #1 (Debian)) id 10LfEc-0005jf-00; Fri, 12 Mar 1999 19:37:10 -0800 Date: Fri, 12 Mar 1999 19:37:10 -0800 (PST) From: Jonathan Walther X-Sender: jwalther@localhost To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: VESA double buffering and pan and zoom In-Reply-To: <199903121101.UAA09690@zodiac.mech.utsunomiya-u.ac.jp> 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 In the VESA spec function 07h lets you switch the beginning of the video mem to anywhere in the video cards memory space. This would mean one could easily do double buffering, by writing to the right area of memory, then changing the one address, and eliminating annoying flicker. Is this currently supported by FreeBSD? I am also curious if 06h has been implemented, to allow pan and scrolling to be done. Cheers! Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 19:50:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from atl1.america.net (atl1.america.net [199.170.121.2]) by hub.freebsd.org (Postfix) with ESMTP id 7E54E14CCE for ; Fri, 12 Mar 1999 19:50:49 -0800 (PST) (envelope-from pritchet@bigfoot.com) Received: from fury (tnt1-41.america.net [206.67.248.41]) by atl1.america.net (8.9.1/8.9.1) with SMTP id WAA01032; Fri, 12 Mar 1999 22:50:27 -0500 (EST) Message-Id: <3.0.5.32.19990312225026.007dac70@mindspring.com> X-Sender: pritchett@mindspring.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 12 Mar 1999 22:50:26 -0500 To: Doug White From: Ron Pritchett Subject: Re: Will IPFW pass GRE packets? Cc: hackers@FreeBSD.ORG In-Reply-To: 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:33 PM 99/03/12 -0800, Doug White wrote: >hello ... > >I wanted to check if IPFW will pass GRE packets in a standard config from >3.0. I'm trying to use the patched natd to translate PPTP packets and >natd isn't seeing them (from what I can tell). Is there anything special >I should do to make sure IP proto 47 packets are getting in and out? > >Thanks for any hints... Have you tried adding a "log" to your deny all statement and then run natd from the console with -v? This is what I had to do when debugging PC Anywhere traffic: 1) Make a kernal with the IPFIREWALL_VERBOSE stuff, install, reboot the box. 2) look thru the process table and kill -15 natd. Run it manually with the -v option 'natd -v -n vr0 -f /etc/natd.conf' in my case. 3) Alt-F2 to another screen. then add a statement like 'ipfw add 64000 deny ip log from any to any' (maybe a 'deny 47' would be needed instead of 'deny ip'???) 4) watch the fun ensue! I hope this was helpful. --- Ron++ Atlanta, GA "This message has been digitally remastered and letterboxed to 16:9 format for your viewing pleasure." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 20:18:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 1868714CFE for ; Fri, 12 Mar 1999 20:18:19 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id XAA02768; Fri, 12 Mar 1999 23:21:42 -0500 (EST) Date: Fri, 12 Mar 1999 23:21:41 -0500 (EST) From: Alfred Perlstein To: Doug White Cc: hackers@FreeBSD.ORG Subject: Re: Will IPFW pass GRE packets? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Mar 1999, Doug White wrote: > hello ... > > I wanted to check if IPFW will pass GRE packets in a standard config from > 3.0. I'm trying to use the patched natd to translate PPTP packets and > natd isn't seeing them (from what I can tell). Is there anything special > I should do to make sure IP proto 47 packets are getting in and out? > > Thanks for any hints... Someone had/has something working with this, I didn't take a mental note of it, you should search the lists. GRE is some windows NT thing? If it is, someone has already figured this out for you, the lists have it. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 20:45:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 87F0D14E2C for ; Fri, 12 Mar 1999 20:45:13 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id WAA01632 for freebsd-hackers@freebsd.org; Fri, 12 Mar 1999 22:44:55 -0600 (CST) Message-ID: <19990312224455.D1582@Denninger.Net> Date: Fri, 12 Mar 1999 22:44:55 -0600 From: Karl Denninger To: freebsd-hackers@freebsd.org Subject: Its BAAAAACK! :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I thought this one was gone... but I guess not! From /var/log/messages: Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0xb - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xb Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Mar 12 13:05:27 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 Mar 12 13:05:27 Genesis /kernel: SEQADDR == 0x154 Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x2 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xc Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Mar 12 13:06:27 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 Mar 12 13:06:27 Genesis /kernel: SEQADDR == 0x154 Mar 12 13:07:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x12 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Mar 12 13:11:28 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 Mar 12 13:11:28 Genesis /kernel: SEQADDR == 0x154 Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x6 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Mar 12 13:11:28 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 Mar 12 13:11:28 Genesis /kernel: SEQADDR == 0x154 And a bunch more. FreeBSD 4.0-CURRENT (KARL) #2: Fri Mar 12 11:38:33 CST 1999 That's the build date; it was updated last night via CVS (so the kernel is current as of March 11th in the evening). Here's the boot output... Mar 12 11:44:29 Genesis /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Mar 12 11:44:29 Genesis /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Mar 12 11:44:29 Genesis /kernel: The Regents of the University of California. All rights reserved. Mar 12 11:44:29 Genesis /kernel: FreeBSD 4.0-CURRENT #2: Fri Mar 12 11:38:33 CST 1999 Mar 12 11:44:29 Genesis /kernel: karl@Genesis.Denninger.Net:/usr/src/sys/compile/KARL Mar 12 11:44:29 Genesis /kernel: Timecounter "i8254" frequency 1193182 Hz Mar 12 11:44:29 Genesis /kernel: Timecounter "TSC" frequency 166194213 Hz Mar 12 11:44:29 Genesis /kernel: CPU: Pentium/P54C (166.19-MHz 586-class CPU) Mar 12 11:44:29 Genesis /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Mar 12 11:44:29 Genesis /kernel: Features=0x1bf Mar 12 11:44:29 Genesis /kernel: real memory = 67108864 (65536K bytes) Mar 12 11:44:29 Genesis /kernel: avail memory = 62185472 (60728K bytes) Mar 12 11:44:29 Genesis /kernel: Preloaded elf kernel "kernel" at 0xc02f0000. Mar 12 11:44:29 Genesis /kernel: Probing for devices on PCI bus 0: Mar 12 11:44:29 Genesis /kernel: chip0: rev 0x03 on pci0.0.0 Mar 12 11:44:29 Genesis /kernel: chip1: rev 0x01 on pci0.7.0 Mar 12 11:44:29 Genesis /kernel: fxp0: rev 0x04 int a irq 12 on pci0.17.0 Mar 12 11:44:29 Genesis /kernel: fxp0: Ethernet address 00:a0:c9:a4:78:c3 Mar 12 11:44:29 Genesis /kernel: ahc0: rev 0x00 int a irq 9 on pci0.18.0 Mar 12 11:44:29 Genesis /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Mar 12 11:44:29 Genesis /kernel: vga0: rev 0x0a on pci0.19.0 Mar 12 11:44:29 Genesis /kernel: ahc1: rev 0x00 int a irq 11 on pci0.20.0 Mar 12 11:44:29 Genesis /kernel: ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Mar 12 11:44:29 Genesis /kernel: Probing for PnP devices: Mar 12 11:44:29 Genesis /kernel: CSN 1 Vendor ID: CTL0042 [0x42008c0e] Serial 0x00022b1f Comp ID: PNP0600 [0x0006d041] Mar 12 11:44:29 Genesis /kernel: Probing for devices on the ISA bus: Mar 12 11:44:29 Genesis /kernel: sc0 on isa Mar 12 11:44:29 Genesis /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Mar 12 11:44:29 Genesis /kernel: atkbdc0 at 0x60-0x6f on motherboard Mar 12 11:44:29 Genesis /kernel: atkbd0 irq 1 on isa Mar 12 11:44:29 Genesis /kernel: psm0 not found Mar 12 11:44:29 Genesis /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Mar 12 11:44:29 Genesis /kernel: sio0: type 16550A Mar 12 11:44:29 Genesis /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 12 11:44:29 Genesis /kernel: sio1: type 16550A Mar 12 11:44:29 Genesis /kernel: ppc0 at 0x378 irq 7 on isa Mar 12 11:44:29 Genesis /kernel: ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode Mar 12 11:44:29 Genesis /kernel: plip0: on ppbus 0 Mar 12 11:44:29 Genesis /kernel: lpt0: on ppbus 0 Mar 12 11:44:29 Genesis /kernel: lpt0: Interrupt-driven port Mar 12 11:44:29 Genesis /kernel: ppi0: on ppbus 0 Mar 12 11:44:29 Genesis /kernel: ppc1 at 0x278 on isa Mar 12 11:44:29 Genesis /kernel: ppc1: Generic chipset (NIBBLE-only) in COMPATIBLE mode Mar 12 11:44:29 Genesis /kernel: plip: not an interrupt driven port, failed. Mar 12 11:44:29 Genesis /kernel: lpt1: on ppbus 1 Mar 12 11:44:29 Genesis /kernel: ppi1: on ppbus 1 Mar 12 11:44:30 Genesis /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on Mar 12 11:44:30 Genesis /kernel: isa Mar 12 11:44:30 Genesis /kernel: fdc0: FIFO enabled, 8 bytes threshold Mar 12 11:44:30 Genesis /kernel: fd0: 1.44MB 3.5in Mar 12 11:44:30 Genesis /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Mar 12 11:44:30 Genesis /kernel: npx0 on motherboard Mar 12 11:44:30 Genesis /kernel: npx0: INT 16 interface Mar 12 11:44:30 Genesis /kernel: Intel Pentium detected, installing workaround for F00F bug Mar 12 11:44:30 Genesis /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry Mar 12 11:44:30 Genesis /kernel: IP Filter: initialized. Default = pass all, Logging = enabled Mar 12 11:44:30 Genesis /kernel: Waiting 5 seconds for SCSI devices to settle Mar 12 11:44:30 Genesis /kernel: sa0 at ahc1 bus 0 target 6 lun 0 Mar 12 11:44:30 Genesis /kernel: sa0: Removable Sequential Access SCSI-2 device Mar 12 11:44:30 Genesis /kernel: sa0: 5.000MB/s transfers (5.000MHz, offset 8) Mar 12 11:44:30 Genesis /kernel: da1 at ahc0 bus 0 target 8 lun 0 Mar 12 11:44:30 Genesis /kernel: da1: Fixed Direct Access SCSI-2 device Mar 12 11:44:30 Genesis /kernel: da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 12 11:44:30 Genesis /kernel: da1: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) Mar 12 11:44:30 Genesis /kernel: da0 at ahc0 bus 0 target 0 lun 0 Mar 12 11:44:30 Genesis /kernel: da0: Fixed Direct Access SCSI-2 device Mar 12 11:44:30 Genesis /kernel: da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 12 11:44:30 Genesis /kernel: da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Mar 12 11:44:30 Genesis /kernel: changing root device to da0s1a Mar 12 11:44:30 Genesis /kernel: ffs_mountfs: superblock updated for soft updates Mar 12 11:44:30 Genesis /kernel: ffs_mountfs: superblock updated for soft updates Mar 12 11:44:30 Genesis named[103]: starting. named 8.1.2 Tue Feb 16 11:14:57 CST 1999 karl@Genesis.Denninger.Net:/disk/obj/usr/src/usr.sbin/named Mar 12 11:44:31 Genesis named[104]: Ready to answer queries. Mar 12 11:44:31 Genesis xntpd[108]: xntpd version=3.4e (beta multicast); Tue Feb 16 11:20:46 CST 1999 (1) Mar 12 11:44:31 Genesis xntpd[108]: tickadj = 5, tick = 10000, tvu_maxslew = 495 Mar 12 11:44:34 Genesis lpd[149]: restarted Mar 12 11:44:36 Genesis FaxQueuer[204]: sendq/q37: line 51: Null or missing number in job request Mar 12 11:44:37 Genesis HylaFAX[208]: HylaFAX INET Protocol Server: restarted. Ideas? -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 21:15:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pacman.redwoodsoft.com (redwoodsoft.com [207.181.199.182]) by hub.freebsd.org (Postfix) with SMTP id AB37E14E54 for ; Fri, 12 Mar 1999 21:15:41 -0800 (PST) (envelope-from dnelson@redwoodsoft.com) Received: (qmail 7397 invoked from network); 13 Mar 1999 05:15:20 -0000 Received: from localhost.redwoodsoft.com (127.0.0.1) by localhost.redwoodsoft.com with SMTP; 13 Mar 1999 05:15:20 -0000 Date: Fri, 12 Mar 1999 21:15:20 -0800 (PST) From: Dru Nelson To: freebsd-hackers@freebsd.org Subject: Will IPFW pass GRE packets? 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, yes, ipfw will pass GRE packets, but I don't know what the standard config is. # grep gre /etc/protocols gre 47 GRE # IP encapsulation protocol - used for PPTP then ipfw will need something like (this had been changed to protect the innocent). 00001 allow gre from any to any log and watch the ipfw code and it will help... Dru Nelson Redwood City, California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 21:39:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (Postfix) with ESMTP id 90B9F14DCC for ; Fri, 12 Mar 1999 21:39:17 -0800 (PST) (envelope-from ck@adsu.bellsouth.com) Received: from oreo (grommit.adsu.bellsouth.com [205.152.173.122]) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) with SMTP id AAA12553; Sat, 13 Mar 1999 00:38:09 -0500 (EST) From: "Christian Kuhtz" To: "Alfred Perlstein" , "Doug White" Cc: Subject: RE: Will IPFW pass GRE packets? Date: Sat, 13 Mar 1999 00:33:39 -0500 Message-ID: <002c01be6d13$0cdc8f60$7aad98cd@oreo.adsu.bellsouth.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.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > GRE is some windows NT thing? If it is, someone has already figured this > out for you, the lists have it. GRE stands for "Generic Route Encapsulation" and is an IETF standard as defined by RFC1701 (http://www.adsu.bellsouth.com/pub/ietf/rfc/rfc1701 and RFC1702). It is used to tunnel all sorts of things across IPv4 networks, including IPv4 itself. It has jack squat to do with NT. Cisco IOS has probably the most implementations of using GRE for various tunnels. Not very many other vendors implement it (but now that Tony works for Juniper, I'm sure they will too :). Sometimes IPSec in tunnel mode is used to provide GRE with encryption based security. Cheers, Chris -- BellSouth Corporation, Advanced Data Services, Sr. Network Architect ck@adsu.bellsouth.com -wk, ck@gnu.org -hm "Affiliation given for identification, not representation." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 22:31:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from m4.stox.sa.enteract.com (stox.sa.enteract.com [207.229.132.161]) by hub.freebsd.org (Postfix) with ESMTP id 2D47614C85 for ; Fri, 12 Mar 1999 22:30:42 -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.3/8.6.12) with ESMTP id AAA00508; Sat, 13 Mar 1999 00:29:55 -0600 (CST) Date: Sat, 13 Mar 1999 00:29:55 -0600 (CST) From: "Kenneth P. Stox" Reply-To: stox@enteract.com To: Karl Denninger Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Its BAAAAACK! :-) In-Reply-To: <19990312224455.D1582@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last time I saw this was when I had the old Adaptec firmware, and auto-termination was enabled. Have you tried setting the termination to the desired mode in the Adaptec BIOS ? Also, which version of the Adaptec BIOS are you running ? Unless I am mistaken, this function is set by the BIOS at inititialization, and FreeBSD does not muck with it. But the last time I looked at it in detail was in the Pre-CAM days, and that may have changed. On Fri, 12 Mar 1999, Karl Denninger wrote: > > Hi folks, > > I thought this one was gone... but I guess not! > > >From /var/log/messages: > > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0xb - timed out while idl > e, LASTPHASE == 0x1, SEQADDR == 0xb > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status > = 353 > Mar 12 13:05:27 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 12 13:05:27 Genesis /kernel: SEQADDR == 0x154 > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x2 - timed out while idl > e, LASTPHASE == 0x1, SEQADDR == 0xc > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status > = 353 > Mar 12 13:06:27 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 12 13:06:27 Genesis /kernel: SEQADDR == 0x154 > Mar 12 13:07:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x12 - timed out while id > le, LASTPHASE == 0x1, SEQADDR == 0xb > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status > = 353 > Mar 12 13:11:28 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 12 13:11:28 Genesis /kernel: SEQADDR == 0x154 > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x6 - timed out while idl > e, LASTPHASE == 0x1, SEQADDR == 0x9 > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 12 13:11:28 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status > = 353 > Mar 12 13:11:28 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 12 13:11:28 Genesis /kernel: SEQADDR == 0x154 > > And a bunch more. > > FreeBSD 4.0-CURRENT (KARL) #2: Fri Mar 12 11:38:33 CST 1999 > > That's the build date; it was updated last night via CVS (so the kernel is > current as of March 11th in the evening). > > Here's the boot output... > > > Mar 12 11:44:29 Genesis /kernel: Copyright (c) 1992-1999 FreeBSD Inc. > Mar 12 11:44:29 Genesis /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > Mar 12 11:44:29 Genesis /kernel: The Regents of the University of California. All rights reserved. > Mar 12 11:44:29 Genesis /kernel: FreeBSD 4.0-CURRENT #2: Fri Mar 12 11:38:33 CST 1999 > Mar 12 11:44:29 Genesis /kernel: karl@Genesis.Denninger.Net:/usr/src/sys/compile/KARL > Mar 12 11:44:29 Genesis /kernel: Timecounter "i8254" frequency 1193182 Hz > Mar 12 11:44:29 Genesis /kernel: Timecounter "TSC" frequency 166194213 Hz > Mar 12 11:44:29 Genesis /kernel: CPU: Pentium/P54C (166.19-MHz 586-class CPU) > Mar 12 11:44:29 Genesis /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Mar 12 11:44:29 Genesis /kernel: Features=0x1bf > Mar 12 11:44:29 Genesis /kernel: real memory = 67108864 (65536K bytes) > Mar 12 11:44:29 Genesis /kernel: avail memory = 62185472 (60728K bytes) > Mar 12 11:44:29 Genesis /kernel: Preloaded elf kernel "kernel" at 0xc02f0000. > Mar 12 11:44:29 Genesis /kernel: Probing for devices on PCI bus 0: > Mar 12 11:44:29 Genesis /kernel: chip0: rev 0x03 on pci0.0.0 > Mar 12 11:44:29 Genesis /kernel: chip1: rev 0x01 on pci0.7.0 > Mar 12 11:44:29 Genesis /kernel: fxp0: rev 0x04 int a irq 12 on pci0.17.0 > Mar 12 11:44:29 Genesis /kernel: fxp0: Ethernet address 00:a0:c9:a4:78:c3 > Mar 12 11:44:29 Genesis /kernel: ahc0: rev 0x00 int a irq 9 on pci0.18.0 > Mar 12 11:44:29 Genesis /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > Mar 12 11:44:29 Genesis /kernel: vga0: Mar 12 11:44:29 Genesis /kernel: hics accelerator> rev 0x0a on pci0.19.0 > Mar 12 11:44:29 Genesis /kernel: ahc1: rev 0x00 int a irq 11 on pci0.20.0 > Mar 12 11:44:29 Genesis /kernel: ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > Mar 12 11:44:29 Genesis /kernel: Probing for PnP devices: > Mar 12 11:44:29 Genesis /kernel: CSN 1 Vendor ID: CTL0042 [0x42008c0e] Serial 0x00022b1f Comp ID: PNP0600 [0x0006d041] > Mar 12 11:44:29 Genesis /kernel: Probing for devices on the ISA bus: > Mar 12 11:44:29 Genesis /kernel: sc0 on isa > Mar 12 11:44:29 Genesis /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > Mar 12 11:44:29 Genesis /kernel: atkbdc0 at 0x60-0x6f on motherboard > Mar 12 11:44:29 Genesis /kernel: atkbd0 irq 1 on isa > Mar 12 11:44:29 Genesis /kernel: psm0 not found > Mar 12 11:44:29 Genesis /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > Mar 12 11:44:29 Genesis /kernel: sio0: type 16550A > Mar 12 11:44:29 Genesis /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Mar 12 11:44:29 Genesis /kernel: sio1: type 16550A > Mar 12 11:44:29 Genesis /kernel: ppc0 at 0x378 irq 7 on isa > Mar 12 11:44:29 Genesis /kernel: ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE) in COMPATIBLE mode > Mar 12 11:44:29 Genesis /kernel: plip0: on ppbus 0 > Mar 12 11:44:29 Genesis /kernel: lpt0: on ppbus 0 > Mar 12 11:44:29 Genesis /kernel: lpt0: Interrupt-driven port > Mar 12 11:44:29 Genesis /kernel: ppi0: on ppbus 0 > Mar 12 11:44:29 Genesis /kernel: ppc1 at 0x278 on isa > Mar 12 11:44:29 Genesis /kernel: ppc1: Generic chipset (NIBBLE-only) in COMPATIBLE mode > Mar 12 11:44:29 Genesis /kernel: plip: not an interrupt driven port, failed. > Mar 12 11:44:29 Genesis /kernel: lpt1: on ppbus 1 > Mar 12 11:44:29 Genesis /kernel: ppi1: on ppbus 1 > Mar 12 11:44:30 Genesis /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on > Mar 12 11:44:30 Genesis /kernel: isa > Mar 12 11:44:30 Genesis /kernel: fdc0: FIFO enabled, 8 bytes threshold > Mar 12 11:44:30 Genesis /kernel: fd0: 1.44MB 3.5in > Mar 12 11:44:30 Genesis /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > Mar 12 11:44:30 Genesis /kernel: npx0 on motherboard > Mar 12 11:44:30 Genesis /kernel: npx0: INT 16 interface > Mar 12 11:44:30 Genesis /kernel: Intel Pentium detected, installing workaround for F00F bug > Mar 12 11:44:30 Genesis /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry > Mar 12 11:44:30 Genesis /kernel: IP Filter: initialized. Default = pass all, Logging = enabled > Mar 12 11:44:30 Genesis /kernel: Waiting 5 seconds for SCSI devices to settle > Mar 12 11:44:30 Genesis /kernel: sa0 at ahc1 bus 0 target 6 lun 0 > Mar 12 11:44:30 Genesis /kernel: sa0: Removable Sequential Access SCSI-2 device > Mar 12 11:44:30 Genesis /kernel: sa0: 5.000MB/s transfers (5.000MHz, offset 8) > Mar 12 11:44:30 Genesis /kernel: da1 at ahc0 bus 0 target 8 lun 0 > Mar 12 11:44:30 Genesis /kernel: da1: Fixed Direct Access SCSI-2 device > Mar 12 11:44:30 Genesis /kernel: da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Mar 12 11:44:30 Genesis /kernel: da1: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) > Mar 12 11:44:30 Genesis /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Mar 12 11:44:30 Genesis /kernel: da0: Fixed Direct Access SCSI-2 device > Mar 12 11:44:30 Genesis /kernel: da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Mar 12 11:44:30 Genesis /kernel: da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > Mar 12 11:44:30 Genesis /kernel: changing root device to da0s1a > Mar 12 11:44:30 Genesis /kernel: ffs_mountfs: superblock updated for soft updates > Mar 12 11:44:30 Genesis /kernel: ffs_mountfs: superblock updated for soft updates > Mar 12 11:44:30 Genesis named[103]: starting. named 8.1.2 Tue Feb 16 11:14:57 CST 1999 karl@Genesis.Denninger.Net:/disk/obj/usr/src/usr.sbin/named > Mar 12 11:44:31 Genesis named[104]: Ready to answer queries. > Mar 12 11:44:31 Genesis xntpd[108]: xntpd version=3.4e (beta multicast); Tue Feb 16 11:20:46 CST 1999 (1) > Mar 12 11:44:31 Genesis xntpd[108]: tickadj = 5, tick = 10000, tvu_maxslew = 495 > Mar 12 11:44:34 Genesis lpd[149]: restarted > Mar 12 11:44:36 Genesis FaxQueuer[204]: sendq/q37: line 51: Null or missing number in job request > Mar 12 11:44:37 Genesis HylaFAX[208]: HylaFAX INET Protocol Server: restarted. > > Ideas? > > -- > -- > Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl > I ain't even *authorized* to speak for anyone other than myself, so give > up now on trying to associate my words with any particular organization. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 12 23: 5:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 6059314DB0 for ; Fri, 12 Mar 1999 23:05:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id AAA01003; Sat, 13 Mar 1999 00:05:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903130705.AAA01003@panzer.plutotech.com> Subject: Re: Its BAAAAACK! :-) In-Reply-To: <19990312224455.D1582@Denninger.Net> from Karl Denninger at "Mar 12, 1999 10:44:55 pm" To: karl@Denninger.Net (Karl Denninger) Date: Sat, 13 Mar 1999 00:05:10 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote... > > Hi folks, > > I thought this one was gone... but I guess not! You might get a better response by posting SCSI problems to the -scsi list, and by using a reasonable subject line. I only happened to look at this message by accident... > >From /var/log/messages: > > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0xb - timed out while idl > e, LASTPHASE == 0x1, SEQADDR == 0xb > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Mar 12 13:05:27 Genesis /kernel: (da0:ahc0:0:0:0): no longer in timeout, status > = 353 > Mar 12 13:05:27 Genesis /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Mar 12 13:05:27 Genesis /kernel: SEQADDR == 0x154 > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): SCB 0x2 - timed out while idl > e, LASTPHASE == 0x1, SEQADDR == 0xc > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Mar 12 13:06:27 Genesis /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent [ ... ] > And a bunch more. > > FreeBSD 4.0-CURRENT (KARL) #2: Fri Mar 12 11:38:33 CST 1999 > > That's the build date; it was updated last night via CVS (so the kernel is > current as of March 11th in the evening). Updating your source probably won't help a whole lot. I'm surprised you haven't seen this a whole lot more. My guess is that you just haven't been banging on the disk in question a whole lot. > Mar 12 11:44:30 Genesis /kernel: da1 at ahc0 bus 0 target 8 lun 0 > Mar 12 11:44:30 Genesis /kernel: da1: Fixed Direct Access SCSI-2 device > Mar 12 11:44:30 Genesis /kernel: da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Mar 12 11:44:30 Genesis /kernel: da1: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) > Mar 12 11:44:30 Genesis /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Mar 12 11:44:30 Genesis /kernel: da0: Fixed Direct Access SCSI-2 device > Mar 12 11:44:30 Genesis /kernel: da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Mar 12 11:44:30 Genesis /kernel: da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) The 'timed out while idle' messages are generally evidence of a disk problem. It means that a command timeout expired, and there was nothing going on when the timeout expired. The timeout for read/write commands from the da driver is 60 seconds. That means that the cause of the above error messages is most likely that your drive has gone "out to lunch". When a drive goes "dead" like that, we hit it with a BDR (Bus Device Reset) to wake it up. This will make more sense when you look at the model number for the Compaq drive in question. It looks very suspiciously like a rebadged Quantum Atlas I. (The 4 gig Atlas I's model number was XP34300) My guess is that you should look for updated firmware for the disk. IIRC, there was a problem with the Atlas I that got fixed with a firmware upgrade. I don't remember what the problem was, but I suspect it was a 'goes out to lunch' type problem. I'm surprised you haven't had trouble with your other disk as well. The LXY4 firmware of the Atlas II is known to have the 'goes out to lunch' problem as well. If you upgrade to the LYK8 firmware for your Atlas II, you at least won't have the drive hanging up on you. That firmware still has the famous Quantum queue full bug, but we work around it in CAM fairly well. (I've got 4 Atlas II's, with LYK8 firmware, and they're working fine.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 4:51: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 081E514E46 for ; Sat, 13 Mar 1999 04:50:54 -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 NAA27104 for hackers@FreeBSD.ORG; Sat, 13 Mar 1999 13:50:35 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9FEFA8848; Sat, 13 Mar 1999 12:24:43 +0100 (CET) Date: Sat, 13 Mar 1999 12:24:43 +0100 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: Proposed patch to /etc/rc Message-ID: <19990313122443.B26855@keltia.freenix.fr> Mail-Followup-To: hackers@FreeBSD.ORG References: <19990312235111.A24106@keltia.freenix.fr> <199903130034.BAA26286@frmug.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.3i In-Reply-To: <199903130034.BAA26286@frmug.org>; from Jon Hamilton on Fri, Mar 12, 1999 at 06:33:38PM -0600 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5130 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jon Hamilton: > On systems which allow a dot in the username, user.group is ambiguous. > Since a colon is not legal in a username under any UNIX, user:group is not. There is that too of course. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 5:40:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cicely8.cicely.de (cicely.de [194.231.9.142]) by hub.freebsd.org (Postfix) with ESMTP id CFFC314D06 for ; Sat, 13 Mar 1999 05:40:05 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id OAA83453; Sat, 13 Mar 1999 14:39:42 +0100 (CET) (envelope-from ticso) Date: Sat, 13 Mar 1999 14:39:41 +0100 From: Bernd Walter To: Greg Rowe Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SMP Woes Message-ID: <19990313143941.A83428@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Greg Rowe on Wed, Mar 10, 1999 at 12:18:51PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > db> trace > generic_bzero(f3283f80,0,f4801900,fe5a3c90,fe5a3c98) at generic_bzero+0xf > zalloci(f3283f80,f488bb00,f4801900,6f802,fe541180) at zalloci+0x29 > getnewvnode(1,f33f0200,f3266200,fe5a3cfc,100) at getnewvnode+0x2f8 > ffs_vget(f33f0200,6f802,fe5a3d7c,ff779d00,fe5a3edc) at ffs_vget+0xa5 > ufs_lookup(fe5a3dd4,fe5a3de8,f016f6d4,fe5a3dd4,fe553c1d) at ufs_lookup+0x936 > ufs_vnoperate(fe5a3dd4,fe553c1d,ff779d00,fe5a3edc,0) at ufs_vnoperate+0x15 > vfs_cache_lookup(fe5a3e30,fe5a3e40,f0171ae9,fe5a3e30,fe53b640) at > vfs_cache_lookup+0x248 > ufs_vnoperate(fe5a3e30,fe53b640,fe5a3edc,fe5a3eb8,0) at ufs_vnoperate+0x15 > lookup(fe5a3eb8,fe541180,f0250848,fe541180,1) at lookup+0x2c1 > namei(fe5a3eb8,fe541180,f0250848,0,8057000) at namei+0x133 > lstat(fe541180,fe5a3f94,8057000,ffffffff,3) at lstat+0x44 > syscall(2f,efbf002f,3,ffffffff,efbfdc70) at syscall+0x187 > Xint0x80_syscall() at Xint0x80_syscall+0x4c > db> > > db> trace > sysctl_vm_zone(f025c7ec,0,0,fa9e5ea8,0) at sysctl_vm_zone+0x90 > sysctl_root(0,fa9e5f30,2,fa9e5ea8,0) at sysctl_root+0x115 > userland_sysctl(fa98d5a0,fa9e5f30,2,0,efbfcf7c) at userland_sysctl+0x11e > __sysctl(fa98d5a0,fa9e5f94,efbfdbd8,2,efbfdbd8) at __sysctl+0x60 > syscall(2f,2f,efbfdbd8,2,efbfcf40) at syscall+0x187 > Xint0x80_syscall() at Xint0x80_syscall+0x4c > db> > Are these fixed now? I remember that I got similar things with 4.0-current from Monday and Wednesday. Both versions should be compiled with maxuser 32. It was on a PII-400 (Single CPU) and 1G RAM Now it is running with a 3.1-STABLE from Wednesday (checked out the same time as the 4.0) If anybody is interessted in I can check for dumps and debug kernels - there should be some. It is not possible to me to run further tests on this hardware. -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 6:37:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 8146B14D4F for ; Sat, 13 Mar 1999 06:37:34 -0800 (PST) (envelope-from bf20761@binghamton.edu) Received: from localhost by bingsun1.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id JAA12981 for ; Sat, 13 Mar 1999 09:37:14 -0500 (EST) X-Authentication-Warning: bingsun1.cc.binghamton.edu: bf20761 owned process doing -bs Date: Sat, 13 Mar 1999 09:37:14 -0500 (EST) From: zhihuizhang X-Sender: bf20761@bingsun1 To: freebsd-hackers@FreeBSD.ORG Subject: Kernel-internal process vs. user deamon 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 need some advice on how to design a system service. I can think of three choices: (1) Implement the system service as a kernel internal process. Since FreeBSD 2.2.8 kernel is not multithreaded, this means for each request we must create a process. This can add a lot of context switch overhead. I wonder if by using a kernel process, I can get a higher priority. (2) Implement the system service as a user-level process. This way, I can make use of the multi-threaded feature available at the user level. I do not know whether I can make a user process has at least the same priority as a kernel process and how to make the user-level process running as a deamon (has no controlling terminal). (3) Implement the system service directly in the interrupt handling routine. This saves scheduling overhead and can repond quickly. But I guess that this technique can be more tricky and error prone. I do not have very intimate knowledge of FreeBSD kernel, so I hope I can get some precious advice/hints on these tentative ideas. Any help is highly 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 From owner-freebsd-hackers Sat Mar 13 9: 4:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 7CDB314C23 for ; Sat, 13 Mar 1999 09:04:38 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id TAA13794 for ; Sat, 13 Mar 1999 19:04:19 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id TAA97969 for ; Sat, 13 Mar 1999 19:04:21 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903131704.TAA97969@greenpeace.grondar.za> To: hackers@freebsd.org Subject: Randomness and vnodes Date: Sat, 13 Mar 1999 19:04:19 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi One for you filesystem types; of all the parts of a struct vnode, which are the most dynamic? Which would be the most usable as input for an entropy collector running in the namei cache? The ones I am most interested in are the simple types; pointers, ints (short or long) or chars. Volatile would be good :-) I am working on improving /dev/random, and in my Copious Free Time, also trying to understand the kernel. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 10: 2:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id B2D6F14EAF; Sat, 13 Mar 1999 10:02:18 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.2/8.9.2/UCB) id UAA95234; Sat, 13 Mar 1999 20:01:51 +0200 (EET) (envelope-from ru) Date: Sat, 13 Mar 1999 20:01:50 +0200 From: Ruslan Ermilov To: dg@freebsd.org Cc: FreeBSD Hackers Subject: ipflow and ipfirewall Message-ID: <19990313200150.A83040@relay.ucb.crimea.ua> Mail-Followup-To: dg@freebsd.org, FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.1-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I thought about starting to use fast IP forwarding, but... It seems that such "fast forwardable" packets, when passed from ether_input(), for example, just simply bypass all firewall checks. Am I right? P.S. It would be fine to announce such changes via freebsd-announce and document all sysctl variables. Thanks, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 10:13:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id 5250F14ED6 for ; Sat, 13 Mar 1999 10:13:26 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id TAA29395; Sat, 13 Mar 1999 19:19:32 +0100 (CET) Message-Id: <199903131819.TAA29395@rt2.synx.com> Date: Sat, 13 Mar 1999 19:11:19 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: ipflow and ipfirewall To: ru@ucb.crimea.ua Cc: hackers@FreeBSD.ORG In-Reply-To: <19990313200150.A83040@relay.ucb.crimea.ua> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Mar, Ruslan Ermilov wrote: > Hi! > > I thought about starting to use fast IP forwarding, but... > > It seems that such "fast forwardable" packets, when passed from > ether_input(), for example, just simply bypass all firewall checks. > > Am I right? > you are. RN. IaM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 12:17:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B1F8C14E37 for ; Sat, 13 Mar 1999 12:17:45 -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 MAA00303; Sat, 13 Mar 1999 12:17:25 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA64976; Sat, 13 Mar 1999 12:17:25 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 13 Mar 1999 12:17:25 -0800 (PST) Message-Id: <199903132017.MAA64976@vashon.polstra.com> To: gram@cdsec.com Subject: Re: C++ global constructors and shared libraries In-Reply-To: <36E6AB40.742D64BB@cdsec.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <36E6AB40.742D64BB@cdsec.com>, Graham Wheeler wrote: > Hi folks > > I have just changed some C++ code libraries from static to shared. > I now find that some global objects declared in these libraries > are no longer having their constructors called. If I move the object > declarations into the main.cc file, then they work fine. However, I > don't want to do this for all the objects - we are talking about 15 > libraries here consisting of hundreds of .cc files that would have to be > checked. > > Is there some command line argument that I need for this, or is it > a problem with g++/ld on FreeBSD generally? I am using FreeBSD 2.2.7 > at present. I bet I know what the problem is. With a.out, you have to build your shared libraries using "gcc -shared" -- not "ld -Bshareable". There is an extra start-up file "c++rt0.o" that must be linked into the shared library in order for its global constructors / destructors to be invoked. "gcc -shared" takes care of that for you automatically. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 12:39:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7E0A414D4A for ; Sat, 13 Mar 1999 12:39:24 -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 MAA00330; Sat, 13 Mar 1999 12:39:05 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.2/8.9.1) id MAA65042; Sat, 13 Mar 1999 12:39:01 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 13 Mar 1999 12:39:01 -0800 (PST) Message-Id: <199903132039.MAA65042@vashon.polstra.com> To: ck@adsu.bellsouth.com Subject: Re: Will IPFW pass GRE packets? In-Reply-To: <002c01be6d13$0cdc8f60$7aad98cd@oreo.adsu.bellsouth.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <002c01be6d13$0cdc8f60$7aad98cd@oreo.adsu.bellsouth.com>, Christian Kuhtz wrote: > > GRE is some windows NT thing? If it is, someone has already figured this > > out for you, the lists have it. > > GRE stands for "Generic Route Encapsulation" and is an IETF standard as > defined by RFC1701 (http://www.adsu.bellsouth.com/pub/ietf/rfc/rfc1701 and > RFC1702). It is used to tunnel all sorts of things across IPv4 networks, > including IPv4 itself. It has jack squat to do with NT. Not quite true. Like a dog who must piss on every bush, Microsoft couldn't endure the thought of following existing standards. So they invented an "enhanced GRE header" for their PPTP tunneling. See "draft-ietf-pppext-pptp-01.txt" from your favorite Internet Drafts repository. It gets even better. They explicitly specify that checksums must be disabled in the GRE encapsulation. And the PPP packets contained therein are stripped of all link-level headers. Thus, as far as I can tell, there is zero, zilch, nada error detection of any kind on the encapsulated PPP packets (i.e., your valuable data). Tcpdump confirms this. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 12:40:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 98B0814E78 for ; Sat, 13 Mar 1999 12:40:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA05511; Sat, 13 Mar 1999 12:39:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 13 Mar 1999 12:39:20 -0800 (PST) From: Doug White To: Ron Pritchett Cc: hackers@FreeBSD.ORG Subject: Re: Will IPFW pass GRE packets? In-Reply-To: <3.0.5.32.19990312225026.007dac70@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Mar 1999, Ron Pritchett wrote: > At 04:33 PM 99/03/12 -0800, Doug White wrote: > >hello ... > > > >I wanted to check if IPFW will pass GRE packets in a standard config from > >3.0. I'm trying to use the patched natd to translate PPTP packets and > >natd isn't seeing them (from what I can tell). Is there anything special > >I should do to make sure IP proto 47 packets are getting in and out? > > > >Thanks for any hints... > > Have you tried adding a "log" to your deny all statement and then run natd > from > the console with -v? I hadn't checked that, but this is also going through natd patched to handle GRE. Running natd with -v doesn't show the GRE packets coming through. But I'll give the other suggestions a try. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 14:28:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FB8014CEF for ; Sat, 13 Mar 1999 14:28:37 -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 RAA19255 for ; Sat, 13 Mar 1999 17:32:54 -0500 (EST) Message-Id: <199903132232.RAA19255@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 13 Mar 1999 17:41:04 -0500 To: hackers@freebsd.org From: Dennis Subject: 'C' language question Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a memory mapped controller that requires that all of its register reads and writes be 32 bits....the follow code: *reg |= 0x80000000; generates a byte OR (ORB instruction) which trashes the register with gcc 2.9.2....a stupid "optimization" that happens to be wrong in this case. is there a declaration that will force the compiler to generate a 32bit OR (ORL instruction) on this? Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 14:39:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (Postfix) with ESMTP id 62BFD14D7E for ; Sat, 13 Mar 1999 14:39:58 -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 OAA12983; Sat, 13 Mar 1999 14:39:31 -0800 (PST) Message-Id: <199903132239.OAA12983@lestat.nas.nasa.gov> To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: 'C' language question Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 13 Mar 1999 14:39:31 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Mar 1999 17:41:04 -0500 Dennis wrote: > I have a memory mapped controller that requires that all of its > register reads and writes be 32 bits....the follow code: > > *reg |= 0x80000000; > > generates a byte OR (ORB instruction) which trashes the register with > gcc 2.9.2....a stupid "optimization" that happens to be wrong in this > case. For gcc's definition of `volatile': volatile u_int32_t val, *reg = ...; val = *reg; val |= 0x80000000; *reg = val; ...but, you should really be using bus_space (hey, even FreeBSD has it now! :-), as the operation primitives there are specifically written to do access in the explcitly specified size. For best results, also make sure there are barrier operations in there, so the system core logic isn't allowed to do write piggybacking. > is there a declaration that will force the compiler to generate a 32bit > OR (ORL instruction) on this? Actually, you get it to do a load and a store, and you place your own OR operation in between. -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 14:48: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 4BAF014E9B for ; Sat, 13 Mar 1999 14:48:04 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA19214; Sat, 13 Mar 1999 17:47:40 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA04271; Sat, 13 Mar 1999 17:47:39 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA05825; Sat, 13 Mar 1999 17:47:39 -0500 (EST) Date: Sat, 13 Mar 1999 17:47:39 -0500 (EST) From: Thomas David Rivers Message-Id: <199903132247.RAA05825@lakes.dignus.com> To: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: 'C' language question In-Reply-To: <199903132232.RAA19255@etinc.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have a memory mapped controller that requires that all of its > register reads and writes be 32 bits....the follow code: > > *reg |= 0x80000000; > > generates a byte OR (ORB instruction) which trashes the register with > gcc 2.9.2....a stupid "optimization" that happens to be wrong in this > case. > > is there a declaration that will force the compiler to generate a 32bit > OR (ORL instruction) on this? > > Dennis > Interesting problem... I don't believe the C language speaks to this; because the operation may be implemented as the compiler sees fit, as long as it gets the right answer (and, it would, in this case.) Perhaps, if you play around with volatile a bit, you can get a full 32-bit move, something like: volatile int i; i = *reg; i |= 0x80000000; *reg = i; The assigment of *reg = i should move all 32 bits, and you really don't care how the OR is accomplished. Also, because of the volatile keyword, the compiler can't eliminate the reference. But - this will force moves to/from memory - which may be a performance issue for you in a device driver... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 14:53:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.201]) by hub.freebsd.org (Postfix) with ESMTP id 7171515471; Sat, 13 Mar 1999 14:53:41 -0800 (PST) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua1.iastate.edu (8.8.5/8.8.5) with SMTP id QAA09676; Sat, 13 Mar 1999 16:53:17 -0600 (CST) Message-Id: <199903132253.QAA09676@isua1.iastate.edu> To: freebsd-hackers@freebsd.org Cc: dillon@freebsd.org Subject: FreeBSD 3.1-Stable Being Unstable Date: Sat, 13 Mar 1999 16:53:17 CST From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Nathan Ahlstrom has been helping me try to gather up information to solve a problem with FreeBSD-Stable and asked me to send the following information to freebsd-hackers. The problem is that Freebsd-Stable crashes after just a few hours of use. No core file is generated either. The crashing occurs on two separate machines, one a dual-p133 and the other a 486-33. Both these kernels are only hours old. I have been updating the kernels daily in hopes of a fix. If any further information is needed, please let me know. Kent Vander Velden wrote: > > Hi. Shortly after sending you tellin you that DDB had not been working > the 486 machine failed and dropped to DDB. I typed the intial message > and the stack trace from the screen. If there is an easier way to capture > the output form DDB I would sure like to hear it. Also enclosed is the > output of dmesg. If any other information would be helpful > please let me know. BTW: The other machine, the dual-p133 does not have > a screen saver enabled. Both of the machines load eaxctly one module, > the dual-p133 loads the linux module while the 486 loads the blank screen > saver module. > > Thanks! > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-STABLE #0: Thu Mar 11 22:35:22 CST 1999 > kent@pseudo:/usr/src/sys/compile/TOYBOX > Timecounter "i8254" frequency 1193182 Hz > CPU: i486DX (486-class CPU) > real memory = 16777216 (16384K bytes) > avail memory = 13758464 (13436K bytes) > Preloaded elf kernel "kernel" at 0xf02cb000. > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA mono <8 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16450 > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16450 > sio2 at 0x3e8-0x3ef irq 5 on isa > sio2: type 16550A > ppc0 at 0x378 irq 7 on isa > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > nlpt0: on ppbus 0 > nlpt0: Interrupt-driven port > ppi0: on ppbus 0 > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > lnc0 at 0x360-0x377 irq 12 drq 7 on isa > lnc0: PCnet-ISA address 00:c0:6d:00:78:fd > aha0 at 0x330-0x333 irq 11 drq 5 on isa > aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > sb0 at 0x220 irq 10 drq 1 on isa > > NOTE! SB Pro support required with your soundcard! > snd0: > opl0 at 0x388 on isa > snd0: > ccd0-3: Concatenated disk drivers > Waiting 2 seconds for SCSI devices to settle > da0 at aha0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 3.300MB/s transfers > da0: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) > da1 at aha0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 3.300MB/s transfers > da1: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) > changing root device to da0s1a > WARNING: / was not properly dismounted > > > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xb8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf014b15b > stack pointer = 0x10:0xf024ad2c > frame pointer = 0x10:0xf024ad40 > code segment = base 0x0, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = net tty bio cam > kernel: type 12 trap, code=0 > Stopped at tsleep+0x1b: movl 0xb8(%ebx),%eax > > > > db> trace > tsleep(f1147f90,4,f023e255,7d0) at tsleep+0x1b > swap_pager_getpages(f2ae35d8,f024ae4c,1,0,f024ae8c) at swap_pager_getpages+0x3c8 > vm_pager_get_pages(f2ae35b8,f024ae4c,1,0,) at vm_pager_get_pages+0x1f > vm_fault(f026f4a4,f00000000,3,0,0) at vm_fault+0x464 > trap_pfault(...) at trap_pfault+0xc4 > trap(...) at trap+0x3b6 > calltrap() at calltrap()+0x1c > --- trap 0xc, eip=0xf022d857, esp=0xf024af2c, ebp=0xf024af48 > vga_load_state(...) at vga_load_state+0x13b > vga_set_mode(...) at vga_set_mode+0x2c2 > set_mode(...) at set_mode+0x5c > restore_scrn_saver_mode(...) at restore_scrn_saver_mode+0x47 > scsplash_saver(...) at scsplash_saver+0xc7 > stop_scrn_saver(...) at stop_scrn_saver+0xa > scrn_timer(...) at scrn_timer+0x177 > softclock(...) at softclock+0xc3 > doreti_swi(...) at doreti_swi+0xf --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 14:55:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 8050C1547A for ; Sat, 13 Mar 1999 14:55:29 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id PAA07767; Sat, 13 Mar 1999 15:55:07 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EAECCA.42F5C549@softweyr.com> Date: Sat, 13 Mar 1999 15:55:06 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: 'C' language question References: <199903132232.RAA19255@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > > I have a memory mapped controller that requires that all of its > register reads and writes be 32 bits....the follow code: > > *reg |= 0x80000000; > > generates a byte OR (ORB instruction) which trashes the register with > gcc 2.9.2....a stupid "optimization" that happens to be wrong in this > case. > > is there a declaration that will force the compiler to generate a 32bit > OR (ORL instruction) on this? No. Read the register into a word in memory (or a register in asm code), set/clear bits in the word, then write the word back. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 15: 5: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dei.calldei.com (dei.calldei.com [205.179.37.1]) by hub.freebsd.org (Postfix) with ESMTP id CEE3514BE7 for ; Sat, 13 Mar 1999 15:05:06 -0800 (PST) (envelope-from chris@dei.calldei.com) Received: from localhost (chris@localhost) by dei.calldei.com (8.9.0/8.9.0) with ESMTP id PAA07658; Sat, 13 Mar 1999 15:09:06 -0800 (PST) Date: Sat, 13 Mar 1999 15:09:06 -0800 (PST) From: Chris Costello To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: 'C' language question In-Reply-To: <199903132232.RAA19255@etinc.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, 13 Mar 1999, Dennis wrote: > > I have a memory mapped controller that requires that all of its > register reads and writes be 32 bits....the follow code: > > *reg |= 0x80000000; > > generates a byte OR (ORB instruction) which trashes the register with > gcc 2.9.2....a stupid "optimization" that happens to be wrong in this > case. > > is there a declaration that will force the compiler to generate a 32bit > OR (ORL instruction) on this? > Try using the 'asm { ... }' syntax in C. (of course, this is where your code becomes platform-specific...) > Dennis > > > 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 Mar 13 15:38:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (Postfix) with ESMTP id AFDC514CBF for ; Sat, 13 Mar 1999 15:38:08 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id AAA29762; Sun, 14 Mar 1999 00:45:17 +0100 (CET) Message-Id: <199903132345.AAA29762@rt2.synx.com> Date: Sun, 14 Mar 1999 00:37:04 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: 'C' language question To: dennis@etinc.com Cc: hackers@FreeBSD.ORG In-Reply-To: <199903132232.RAA19255@etinc.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Mar, Dennis wrote: > *reg |= 0x80000000; > > generates a byte OR (ORB instruction) which trashes the register with > gcc 2.9.2....a stupid "optimization" that happens to be wrong in this > case. Just for fun: i couldn't resist to expose you all a real 'optimization' madness of the C compiler of a big (really big) company : (after macros expension) Original : if (A == 0) {...} if ((A == 0 ? *ptr++ : func()) == 7) {...} assembler code generated : if (A == 0) {..} else if (*++ptr == 7) {..} ^^^^^ just to say that 'stupid' seems a little hard in the original message case. RN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 16:58:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 5AEAA14EAD for ; Sat, 13 Mar 1999 16:58:29 -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 LAA01709; Sun, 14 Mar 1999 11:28:10 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA10881; Sun, 14 Mar 1999 11:28:08 +1030 (CST) Message-ID: <19990314112807.K429@lemis.com> Date: Sun, 14 Mar 1999 11:28:07 +1030 From: Greg Lehey To: Mark Murray , hackers@FreeBSD.ORG Subject: Re: Randomness and vnodes References: <199903131704.TAA97969@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903131704.TAA97969@greenpeace.grondar.za>; from Mark Murray on Sat, Mar 13, 1999 at 07:04:19PM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 13 March 1999 at 19:04:19 +0200, Mark Murray wrote: > Hi > > One for you filesystem types; of all the parts of a struct vnode, > which are the most dynamic? Which would be the most usable as > input for an entropy collector running in the namei cache? > > The ones I am most interested in are the simple types; pointers, > ints (short or long) or chars. Volatile would be good :-) Depends on how many bits you want. Most pointers will have the top 4 bits set and the bottom 2 bits cleared. Why do you want to use a vnode? 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 Sat Mar 13 18:29:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id EE70D14F76 for ; Sat, 13 Mar 1999 18:29:18 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:cFKDSKI/tzwokRdyCh4H+3Tx7iZSquiH@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id LAA09880; Sun, 14 Mar 1999 11:28:47 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA14352; Sun, 14 Mar 1999 11:32:03 +0900 (JST) Message-Id: <199903140232.LAA14352@zodiac.mech.utsunomiya-u.ac.jp> To: Kent Vander Velden Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sat, 13 Mar 1999 16:53:17 CST." <199903132253.QAA09676@isua1.iastate.edu> References: <199903132253.QAA09676@isua1.iastate.edu> Date: Sun, 14 Mar 1999 11:32:02 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. Nathan Ahlstrom has been helping me try to gather up information >to solve a problem with FreeBSD-Stable and asked me to send the following >information to freebsd-hackers. > The problem is that Freebsd-Stable crashes after just a few hours of >use. No core file is generated either. The crashing occurs on two >separate machines, one a dual-p133 and the other a 486-33. Both these >kernels are only hours old. I have been updating the kernels daily >in hopes of a fix. > If any further information is needed, please let me know. Would you possibly test the following patch for /sys/i386/include/pmap.h and /sys/i386/i386/locore.s? It's for 3.1-STABLE and 4.0-CURRENT. Kazu Index: include/pmap.h =================================================================== RCS file: /src/CVS/src/sys/i386/include/pmap.h,v retrieving revision 1.58 diff -u -r1.58 pmap.h --- pmap.h 1999/03/02 16:20:39 1.58 +++ pmap.h 1999/03/11 10:47:11 @@ -122,6 +122,8 @@ */ #define ISA_HOLE_START 0xa0000 #define ISA_HOLE_LENGTH (0x100000-ISA_HOLE_START) +#define BIOS_DATA_START 0x00000 +#define BIOS_DATA_LENGTH 0x00600 #ifndef LOCORE Index: i386/locore.s =================================================================== RCS file: /src/CVS/src/sys/i386/i386/locore.s,v retrieving revision 1.120 diff -u -r1.120 locore.s --- locore.s 1999/01/31 02:04:43 1.120 +++ locore.s 1999/03/11 10:45:35 @@ -857,6 +857,11 @@ movl $UPAGES, %ecx fillkptphys($PG_RW) +/* Map BIOS data area */ + movl $BIOS_DATA_START, %eax + movl $(BIOS_DATA_LENGTH + PAGE_MASK)>>PAGE_SHIFT, %ecx + fillkptphys($PG_RW) + /* Map ISA hole */ movl $ISA_HOLE_START, %eax movl $ISA_HOLE_LENGTH>>PAGE_SHIFT, %ecx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 18:58:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 826D314FDD; Sat, 13 Mar 1999 18:58:55 -0800 (PST) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id WAA02398; Sat, 13 Mar 1999 22:02:37 -0500 (EST) Date: Sat, 13 Mar 1999 22:02:35 -0500 (EST) From: Alfred Perlstein To: Kent Vander Velden Cc: freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable In-Reply-To: <199903132253.QAA09676@isua1.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 13 Mar 1999, Kent Vander Velden wrote: > > > Hi. Nathan Ahlstrom has been helping me try to gather up information > to solve a problem with FreeBSD-Stable and asked me to send the following > information to freebsd-hackers. > The problem is that Freebsd-Stable crashes after just a few hours of > use. No core file is generated either. The crashing occurs on two > separate machines, one a dual-p133 and the other a 486-33. Both these > kernels are only hours old. I have been updating the kernels daily > in hopes of a fix. > If any further information is needed, please let me know. As a temporary workaround please disable the screen saver code. I was having the same problems with 4.0 and taking out the saver module kept my machine from crashing. As far as the linux emulation... The same box that i disabled the screen saver is also running the linux module. It's still running it and seems stable, however the linux code itself is not being used, it's just loaded (i don't have any linux apps to test). I suggest you check if your kernels are being compiled with INVARIANTS or something of the likes, kernels compiled with these options mixed with modules that don't can crash your machine afaik. -Alfred > > > Kent Vander Velden wrote: > > > > Hi. Shortly after sending you tellin you that DDB had not been working > > the 486 machine failed and dropped to DDB. I typed the intial message > > and the stack trace from the screen. If there is an easier way to capture > > the output form DDB I would sure like to hear it. Also enclosed is the > > output of dmesg. If any other information would be helpful > > please let me know. BTW: The other machine, the dual-p133 does not have > > a screen saver enabled. Both of the machines load eaxctly one module, > > the dual-p133 loads the linux module while the 486 loads the blank screen > > saver module. > > > > Thanks! > > > > Copyright (c) 1992-1999 FreeBSD Inc. > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > The Regents of the University of California. All rights reserved. > > FreeBSD 3.1-STABLE #0: Thu Mar 11 22:35:22 CST 1999 > > kent@pseudo:/usr/src/sys/compile/TOYBOX > > Timecounter "i8254" frequency 1193182 Hz > > CPU: i486DX (486-class CPU) > > real memory = 16777216 (16384K bytes) > > avail memory = 13758464 (13436K bytes) > > Preloaded elf kernel "kernel" at 0xf02cb000. > > Probing for devices on the ISA bus: > > sc0 on isa > > sc0: VGA mono <8 virtual consoles, flags=0x0> > > atkbdc0 at 0x60-0x6f on motherboard > > atkbd0 irq 1 on isa > > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > > sio0: type 16450 > > sio1 at 0x2f8-0x2ff irq 3 on isa > > sio1: type 16450 > > sio2 at 0x3e8-0x3ef irq 5 on isa > > sio2: type 16550A > > ppc0 at 0x378 irq 7 on isa > > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > > nlpt0: on ppbus 0 > > nlpt0: Interrupt-driven port > > ppi0: on ppbus 0 > > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > lnc0 at 0x360-0x377 irq 12 drq 7 on isa > > lnc0: PCnet-ISA address 00:c0:6d:00:78:fd > > aha0 at 0x330-0x333 irq 11 drq 5 on isa > > aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs > > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > > npx0 on motherboard > > npx0: INT 16 interface > > sb0 at 0x220 irq 10 drq 1 on isa > > > > NOTE! SB Pro support required with your soundcard! > > snd0: > > opl0 at 0x388 on isa > > snd0: > > ccd0-3: Concatenated disk drivers > > Waiting 2 seconds for SCSI devices to settle > > da0 at aha0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 3.300MB/s transfers > > da0: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) > > da1 at aha0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 3.300MB/s transfers > > da1: 1041MB (2131992 512 byte sectors: 64H 32S/T 1041C) > > changing root device to da0s1a > > WARNING: / was not properly dismounted > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xb8 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xf014b15b > > stack pointer = 0x10:0xf024ad2c > > frame pointer = 0x10:0xf024ad40 > > code segment = base 0x0, limit 0xffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = Idle > > interrupt mask = net tty bio cam > > kernel: type 12 trap, code=0 > > Stopped at tsleep+0x1b: movl 0xb8(%ebx),%eax > > > > > > > > db> trace > > tsleep(f1147f90,4,f023e255,7d0) at tsleep+0x1b > > swap_pager_getpages(f2ae35d8,f024ae4c,1,0,f024ae8c) at swap_pager_getpages+0x3c8 > > vm_pager_get_pages(f2ae35b8,f024ae4c,1,0,) at vm_pager_get_pages+0x1f > > vm_fault(f026f4a4,f00000000,3,0,0) at vm_fault+0x464 > > trap_pfault(...) at trap_pfault+0xc4 > > trap(...) at trap+0x3b6 > > calltrap() at calltrap()+0x1c > > --- trap 0xc, eip=0xf022d857, esp=0xf024af2c, ebp=0xf024af48 > > vga_load_state(...) at vga_load_state+0x13b > > vga_set_mode(...) at vga_set_mode+0x2c2 > > set_mode(...) at set_mode+0x5c > > restore_scrn_saver_mode(...) at restore_scrn_saver_mode+0x47 > > scsplash_saver(...) at scsplash_saver+0xc7 > > stop_scrn_saver(...) at stop_scrn_saver+0xa > > scrn_timer(...) at scrn_timer+0x177 > > softclock(...) at softclock+0xc3 > > doreti_swi(...) at doreti_swi+0xf > > --- > Kent Vander Velden > kent@iastate.edu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 4.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 19:37:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rgate.ricochet.net (rgate1.ricochet.net [204.179.143.6]) by hub.freebsd.org (Postfix) with ESMTP id AAE6514E30 for ; Sat, 13 Mar 1999 19:37:24 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg131-045.ricochet.net (mg131-045.ricochet.net [204.179.131.45]) by rgate.ricochet.net (8.8.8/8.8.8) with ESMTP id VAA05735 for ; Sat, 13 Mar 1999 21:37:02 -0600 (CST) Date: Sat, 13 Mar 1999 19:35:51 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: Christopher Nielsen To: hackers@FreeBSD.ORG Subject: Re: FreeBSD and ThinkPad 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 Thu, 11 Mar 1999, Andrzej Bialecki wrote: > On Wed, 10 Mar 1999, Justin T. Gibbs wrote: > > > In article you wrote: > > > > > > I still experience total freezes when accessing sio0. The same goes for > > > 'pnpinfo' - machine freezes completely, and only hard reboot helps. > > > > Under DOS or Win9X, run: > > > > PS2 SERA enable > > PS2 SERA 1 > > > > The serial port should work correctly under FreeBSD after that. > > Ah.. Ok, thanks, I'll try this. > > Andrzej Bialecki I've recently been given a ThinkPad 770X, and I've been wrestling with it just the same. I think I finally found a stable kernel config for -stable. The key seems to have been disabling syscons in favor of pcvt. Once I did that, it stopped randomly hanging and crashing. I still need to run some stress tests. I'll report more as I find out more info. -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 20: 6:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (Postfix) with ESMTP id 5BF7715370 for ; Sat, 13 Mar 1999 20:05:29 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.3/8.9.1) id XAA40001; Sat, 13 Mar 1999 23:04:29 -0500 (EST) To: Bill Paul Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903122116.QAA19872@skynet.ctr.columbia.edu> Cc: freebsd-hackers@freebsd.org From: Cory Kempf Date: 13 Mar 1999 23:04:29 -0500 In-Reply-To: Bill Paul's message of "Fri, 12 Mar 1999 16:16:13 -0500 (EST)" Message-ID: <5femmslnsi.fsf@singularity.enigami.com> Lines: 45 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nobody else seems to have touched this, so I thought I would toss in my $0.02... Bill Paul writes: > Well, I have my Tigon driver working to the point where I can now exchange > traffic with another machine. But no matter what I do, I can't seem to get > my gigabit ethernet device to generate more than 200Mbps on transmit. I'm > confused. > > Even using jumbo frames, I can't get more than about 200Mbps on transmit. > The LoseNT machine doens't seem to be able to get above 200Mbps either You may well be running in to limitations of the available bandwidth of PCI. The Theoretical Maximum bandwidth is 33MHz * 32 bits = 132 MB/s. That number assumes that you move all the data at once, as a single operation, and your hardware can keep up. Not bloody likely. There is some bus overhead with setting up the data transfer. You can also lose if you are not transfering 32 bit data. If I remember, the worst case was something like 11 or 4MB/s or so. Realistically, on a PowerPC (which is where my experince with PCI is), if you do everything right AND are moving lots of data, you can see up to 96 MB/s. To get this, it is important that the card be able to accept a cache line at a time, and that you deliver a cache line at a time (16 bytes, if memory serves). 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of what I would expect. Finally, take all this with a grain of salt, as I have never worked with gigabit ethernet... +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 20:22: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (Postfix) with ESMTP id 2DAE514F7F; Sat, 13 Mar 1999 20:21:53 -0800 (PST) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id WAA15614; Sat, 13 Mar 1999 22:21:25 -0600 (CST) Message-Id: <199903140421.WAA15614@isua3.iastate.edu> To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sat, 13 Mar 1999 22:02:35 EST." Date: Sat, 13 Mar 1999 22:21:25 CST From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >As a temporary workaround please disable the screen saver code. >I was having the same problems with 4.0 and taking out the saver >module kept my machine from crashing. > >As far as the linux emulation... The same box that i disabled the >screen saver is also running the linux module. It's still running >it and seems stable, however the linux code itself is not being >used, it's just loaded (i don't have any linux apps to test). Does this mean not loading a module or disabling the splash pseudo-device? While both machines have the splash pseudo device, only the 486 actually loads a screen saver module. The dual-p133 does not load a screen saver and it crashes. The dual-p133 loads the linux module but the functionality is not used. >I suggest you check if your kernels are being compiled with >INVARIANTS or something of the likes, kernels compiled with >these options mixed with modules that don't can crash your machine >afaik. INVARIANTS and other similar diagnostic code switches are not enabled on either machine. When the dual-p133 crashes the text screen is completely screwed up. The machine is normally running X and the it crashes the screen goes blank. The reboot cycle completes and an OS is loaded. During the reboot cycle I nothing on the screen. If FreeBSD loads I see nothing. If NT loads I see nothing until the login screen. If I reboot NT I see nothing until NT loads again. Simply, when FreeBSD crashes on this machine while in X (and perhaps when not in X) no text mode screen is visible. So, even if DDB does kick in on this machine I would have not way of seeing the text. Can the text mode problem be fixed? Thanks. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 20:26: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C8DB114F38 for ; Sat, 13 Mar 1999 20:25:57 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id FAA85618; Sun, 14 Mar 1999 05:25:34 +0100 (CET) (envelope-from des) To: "Robert Faulds" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Src code for @Home NIC Card for Slaming into UNIX - Re: (Form posted from Mozilla (KMM25773C0KM)) References: <199903120227.SAA22664@hpfsvr02.cup.hp.com> <36E95F91.5AA0DEFE@energyinteractive.com> From: Dag-Erling Smorgrav Date: 14 Mar 1999 05:25:33 +0100 In-Reply-To: "Robert Faulds"'s message of "Fri, 12 Mar 1999 10:40:17 -0800" Message-ID: Lines: 24 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Robert Faulds" writes: > Tci uses DHCP, but it uses a unique hostname (installing their software > changed my hostname to something like B9182734-B) to get a preassigned > IP address. This address was printed, along with default route, on the > top of the work order. One thing that was missing were name servers. That's what DHCP is for. It's "Dynamic host configuration protocol", not "Dynamic IP address allocation protocol". There are two ways of really appreciating DHCP: 1) try running a server which by sheer coincidence has an IP address which was previously assigned to a large ISP's name server. Watch your named logs closely. While you're at it, write an awk script which counts occurrences of such household words as "sex", "nude", "teensex", "celebs", etc. Before long, you'll wish that ISP had used DHCP instead of manual resolver configuration. 2) try running the network at a medium to large LAN party. You will really, really love DHCP after going through that. 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 Sat Mar 13 20:44:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ninsei.com (24.64.9.93.ab.wave.home.com [24.64.9.93]) by hub.freebsd.org (Postfix) with SMTP id CF0A814BDA for ; Sat, 13 Mar 1999 20:44:18 -0800 (PST) (envelope-from dreamer@freelow.ninsei.com) Received: (qmail 36772 invoked by uid 1001); 14 Mar 1999 04:43:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Mar 1999 04:43:58 -0000 Date: Sat, 13 Mar 1999 21:43:58 -0700 (MST) From: Steven Young To: Alfred Perlstein Cc: Kent Vander Velden , freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: FreeBSD 3.1-Stable Being Unstable 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 Sat, 13 Mar 1999, Alfred Perlstein wrote: > As a temporary workaround please disable the screen saver code. > I was having the same problems with 4.0 and taking out the saver > module kept my machine from crashing. For the record, I have been experiencing a large number of kernel panics under 3.1-RELEASE due to the screen saver. Happens with all the different screen saver modules, basically whenever I hit a key or whatever to get rid of the screen saver, the system crashes and burns. Disabling the screen saver entirely and not compiling in the pseudo-device seem to have fixed the problem, but I'm probably one of the last five people on the planet that still uses an amber monitor that actually needs a screen blanker. ;) Steve. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 21: 1:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id 583CB14F76 for ; Sat, 13 Mar 1999 21:01:36 -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 VAA73230; Sat, 13 Mar 1999 21:00:25 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903140500.VAA73230@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cory Kempf Cc: Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "13 Mar 1999 23:04:29 EST." <5femmslnsi.fsf@singularity.enigami.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Mar 1999 21:00:24 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > what I would expect. > I think the system should be able to support at least 70MB/s at least I do over here with a bt848 video capture board capturing 640x480x4 at 30 frames per second and then displaying the frames on video display card 8) Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 21:23:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (Postfix) with ESMTP id 8C34E14F3B for ; Sat, 13 Mar 1999 21:23:29 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.3/8.9.1) id AAA40285; Sun, 14 Mar 1999 00:22:37 -0500 (EST) To: Amancio Hasty Cc: Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903140500.VAA73230@rah.star-gate.com> Cc: From: Cory Kempf Date: 14 Mar 1999 00:22:37 -0500 In-Reply-To: Amancio Hasty's message of "Sat, 13 Mar 1999 21:00:24 -0800" Message-ID: <5fd82clk6a.fsf@singularity.enigami.com> Lines: 36 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty writes: > > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > > what I would expect. > > I think the system should be able to support at least 70MB/s at least I > do over here > with a bt848 video capture board capturing 640x480x4 at 30 frames per second > and then displaying the frames on video display card 8) A video capture board is generally moving bulk data without any protocol in the way. It is idealy suited for getting maximal bandwidth from PCI, as you can essentially set up the transfer, then just let it run. With an ethernet driver, though, there is often additional host<->card traffic, such as telling the card "here is some data", the card responding "Ok, I am done with it", etc. Additionally, the protocol doesn't lend itself to exclusively bulk data transfers. ARP and other overhead will eat up a lot of that theoretical bandwidth. So, if you are seeing 70 MB/s with video, where you can probably get by with a single ACK between frames -- i.e. 2 bus operations / block -- it wouldn't surprise me to see an ethernet card, with a protocol that might require five bus operations / block getting less. Remember too, that trip through the protocol stack was only a little over 50 MB/s... +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 21:26: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 67B3314FD9 for ; Sat, 13 Mar 1999 21:25:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA08448; Sat, 13 Mar 1999 22:25:00 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36EB482B.14BD236@softweyr.com> Date: Sat, 13 Mar 1999 22:24:59 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Amancio Hasty Cc: Cory Kempf , Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? References: <199903140500.VAA73230@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > > what I would expect. > > I think the system should be able to support at least 70MB/s at least I do over here > with a bt848 video capture board capturing 640x480x4 at 30 frames per second > and then displaying the frames on video display card 8) An article in IEEE Computer magazine last summer reported achieving 320 Mb/s throughput with Myricom Myrinet boards on FreeBSD. I've seen this number batted around industry publications like Network World a number of times also. That would seem to require only a 10 Mhz clock with a 32-bit bus bandwidth; is there really this much overhead in the PCI transactions? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 21:33:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (Postfix) with ESMTP id 2B9A314EE2 for ; Sat, 13 Mar 1999 21:33:13 -0800 (PST) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id XAA26490; Sat, 13 Mar 1999 23:32:51 -0600 (CST) Message-Id: <199903140532.XAA26490@isua3.iastate.edu> To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sun, 14 Mar 1999 11:32:02 +0900." <199903140232.LAA14352@zodiac.mech.utsunomiya-u.ac.jp> Date: Sat, 13 Mar 1999 23:32:51 CST From: Kent Vander Velden Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am afraid that this patch did not help. In fact, the machine crashed after less than 1/2 hour of use. I am going to try disabling the splash pseudo device now in addition to this patch. >Would you possibly test the following patch for /sys/i386/include/pmap.h >and /sys/i386/i386/locore.s? > >It's for 3.1-STABLE and 4.0-CURRENT. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 21:50:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rah.star-gate.com (rah.star-gate.com [209.249.129.138]) by hub.freebsd.org (Postfix) with ESMTP id DEF2514FBB for ; Sat, 13 Mar 1999 21:49:46 -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 VAA74949; Sat, 13 Mar 1999 21:48:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199903140548.VAA74949@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Cory Kempf Cc: Bill Paul , freebsd-hackers@FreeBSD.ORG Subject: Re: Gigabit ethernet -- what am I doing wrong? In-reply-to: Your message of "14 Mar 1999 00:22:37 EST." <5fd82clk6a.fsf@singularity.enigami.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Mar 1999 21:48:47 -0800 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Point well taken , however in the case of the bt848 driver there is a protocol between the host and the card in the form of a dma controller program which tells programs the bt848's dma controller so in reality there two data streams : host -- program ( line 1. to memory region line 2. to memory region line 3. to memory region ) it is a bit more involved than that however that is the essence of it. And you are correct there are FreeBSD systems out there which do saturate the PCI bus with bt848 cards . Not too long ago above.net was testing a security cam setup using 3 bt848s and transmitting the data to the mbone using FreeBSD of course 8) Have Fun Guys, Amancio > Amancio Hasty writes: > > > > 200 Mb/s = 25 MB/s, which seems a little low, but is within the realm of > > > what I would expect. > > > > I think the system should be able to support at least 70MB/s at least I > > do over here > > with a bt848 video capture board capturing 640x480x4 at 30 frames per second > > and then displaying the frames on video display card 8) > > A video capture board is generally moving bulk data without any protocol > in the way. It is idealy suited for getting maximal bandwidth from PCI, > as you can essentially set up the transfer, then just let it run. > > With an ethernet driver, though, there is often additional host<->card > traffic, such as telling the card "here is some data", the card responding > "Ok, I am done with it", etc. Additionally, the protocol doesn't lend > itself to exclusively bulk data transfers. ARP and other overhead will > eat up a lot of that theoretical bandwidth. > > So, if you are seeing 70 MB/s with video, where you can probably get by > with a single ACK between frames -- i.e. 2 bus operations / block -- it > wouldn't surprise me to see an ethernet card, with a protocol that might > require five bus operations / block getting less. > > Remember too, that trip through the protocol stack was only a little > over 50 MB/s... > > +C > > -- > Thinking of purchasing RAM from the Chip Merchant? > Please read this first: > > Cory Kempf Macintosh / Unix Consulting & Software Development > ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 22:19:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 39C7E14F91 for ; Sat, 13 Mar 1999 22:19:04 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id IAA15017; Sun, 14 Mar 1999 08:18:44 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id IAA64577; Sun, 14 Mar 1999 08:18:46 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903140618.IAA64577@greenpeace.grondar.za> To: Greg Lehey Cc: hackers@FreeBSD.ORG Subject: Re: Randomness and vnodes In-Reply-To: Your message of " Sun, 14 Mar 1999 11:28:07 +1030." <19990314112807.K429@lemis.com> References: <199903131704.TAA97969@greenpeace.grondar.za> <19990314112807.K429@lemis.com> Date: Sun, 14 Mar 1999 08:18:44 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Saturday, 13 March 1999 at 19:04:19 +0200, Mark Murray wrote: > > Hi > > > > One for you filesystem types; of all the parts of a struct vnode, > > which are the most dynamic? Which would be the most usable as > > input for an entropy collector running in the namei cache? > > > > The ones I am most interested in are the simple types; pointers, > > ints (short or long) or chars. Volatile would be good :-) > > Depends on how many bits you want. Most pointers will have the top 4 > bits set and the bottom 2 bits cleared. Why do you want to use a > vnode? I don't care, as long as there is some entropy. I want to add a entropy harvester into the namei cache, and if I can also pass in some genuine junk, that helps things. For interrupts, the interrupt number is used; for the keyboard, scancodes; the available environmental stuff in the namei cache is centred around vnodes, so I'm looking for dirt in them. Heck - I may just xor the whole thing into an int to get some junk if necessary. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 22:45:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id BF22214FA0 for ; Sat, 13 Mar 1999 22:45:50 -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 RAA02918; Sun, 14 Mar 1999 17:15:31 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA13082; Sun, 14 Mar 1999 17:15:30 +1030 (CST) Message-ID: <19990314171529.Z429@lemis.com> Date: Sun, 14 Mar 1999 17:15:29 +1030 From: Greg Lehey To: Mark Murray Cc: hackers@FreeBSD.ORG Subject: Re: Randomness and vnodes References: <199903131704.TAA97969@greenpeace.grondar.za> <19990314112807.K429@lemis.com> <199903140618.IAA64577@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903140618.IAA64577@greenpeace.grondar.za>; from Mark Murray on Sun, Mar 14, 1999 at 08:18:44AM +0200 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 14 March 1999 at 8:18:44 +0200, Mark Murray wrote: > Greg Lehey wrote: >> On Saturday, 13 March 1999 at 19:04:19 +0200, Mark Murray wrote: >>> Hi >>> >>> One for you filesystem types; of all the parts of a struct vnode, >>> which are the most dynamic? Which would be the most usable as >>> input for an entropy collector running in the namei cache? >>> >>> The ones I am most interested in are the simple types; pointers, >>> ints (short or long) or chars. Volatile would be good :-) >> >> Depends on how many bits you want. Most pointers will have the top 4 >> bits set and the bottom 2 bits cleared. Why do you want to use a >> vnode? > > I don't care, as long as there is some entropy. > > I want to add a entropy harvester into the namei cache, and if I can > also pass in some genuine junk, that helps things. > > For interrupts, the interrupt number is used; for the keyboard, scancodes; > the available environmental stuff in the namei cache is centred around > vnodes, so I'm looking for dirt in them. Heck - I may just xor the whole > thing into an int to get some junk if necessary. I don't think xoring would be very random, given the number of fields with predictable content. That's my main concern with using vnodes in the first place, but if you want to use them, you should at least divide and get a remainder. 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 Sat Mar 13 22:52:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 27D5914CB2 for ; Sat, 13 Mar 1999 22:52:14 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:hAKnGY77pnXZXs03I6WZBVOkZ+iXSxwt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id PAA10804; Sun, 14 Mar 1999 15:51:51 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id PAA19274; Sun, 14 Mar 1999 15:55:06 +0900 (JST) Message-Id: <199903140655.PAA19274@zodiac.mech.utsunomiya-u.ac.jp> To: Kent Vander Velden Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FreeBSD 3.1-Stable Being Unstable In-reply-to: Your message of "Sat, 13 Mar 1999 23:32:51 CST." <199903140532.XAA26490@isua3.iastate.edu> References: <199903140532.XAA26490@isua3.iastate.edu> Date: Sun, 14 Mar 1999 15:55:05 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am afraid that this patch did not help. In fact, the machine crashed >after less than 1/2 hour of use. I am going to try disabling the splash >pseudo device now in addition to this patch. > >>Would you possibly test the following patch for /sys/i386/include/pmap.h >>and /sys/i386/i386/locore.s? Ok, then, Remove my previous patch and apply the following patch to /sys/i386/isa/vga_isa.c. With this patch, you can use the splash pseudo-device, screen savers, and the X server without crashing the machine. This is a workaround which I rather don't like, but is known to work. (A couple of other users reported success...) Kazu Index: vga_isa.c =================================================================== RCS file: /src/CVS/src/sys/i386/isa/vga_isa.c,v retrieving revision 1.4 diff -u -r1.4 vga_isa.c --- vga_isa.c 1999/02/05 12:58:40 1.4 +++ vga_isa.c 1999/03/09 00:34:00 @@ -1973,6 +1973,7 @@ inb(crtc_addr + 6); /* reset flip-flop */ outb(ATC, 0x20); /* enable palette */ +#if 0 #ifndef VGA_NO_BIOS if (adp->va_unit == V_ADP_PRIMARY) { writeb(BIOS_PADDRTOVADDR(0x44a), buf[0]); /* COLS */ @@ -1984,6 +1985,7 @@ #endif } #endif /* VGA_NO_BIOS */ +#endif splx(s); return 0; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 23: 2:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id C6DED14E90 for ; Sat, 13 Mar 1999 23:02:39 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id JAA15079; Sun, 14 Mar 1999 09:02:20 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id JAA02264; Sun, 14 Mar 1999 09:02:22 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903140702.JAA02264@greenpeace.grondar.za> To: Greg Lehey Cc: hackers@FreeBSD.ORG Subject: Re: Randomness and vnodes In-Reply-To: Your message of " Sun, 14 Mar 1999 17:15:29 +1030." <19990314171529.Z429@lemis.com> References: <199903131704.TAA97969@greenpeace.grondar.za> <19990314112807.K429@lemis.com> <199903140618.IAA64577@greenpeace.grondar.za> <19990314171529.Z429@lemis.com> Date: Sun, 14 Mar 1999 09:02:20 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > For interrupts, the interrupt number is used; for the keyboard, scancodes; > > the available environmental stuff in the namei cache is centred around > > vnodes, so I'm looking for dirt in them. Heck - I may just xor the whole > > thing into an int to get some junk if necessary. > > I don't think xoring would be very random, given the number of fields > with predictable content. That's my main concern with using vnodes in > the first place, but if you want to use them, you should at least > divide and get a remainder. Ah! There is a theorem (sez Schneier) that says that if you xor two bits and only one of them is truly random, then the result is truly random. By xor'ing the lot, I shall get any randomness that is anywhere in the structure. However, I may lose some, and I may waste time if only a subset of the struct is random enough. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 13 23:11:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id ED40914DD2 for ; Sat, 13 Mar 1999 23:11:16 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:bxiAs+gTHcsZTcuoYKQONxjjpmFdNYPs@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id QAA10699; Sun, 14 Mar 1999 16:10:55 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id QAA19970; Sun, 14 Mar 1999 16:14:10 +0900 (JST) Message-Id: <199903140714.QAA19970@zodiac.mech.utsunomiya-u.ac.jp> To: Jonathan Walther Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA double buffering and pan and zoom In-reply-to: Your message of "Fri, 12 Mar 1999 19:37:10 PST." References: Date: Sun, 14 Mar 1999 16:14:09 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In the VESA spec function 07h lets you switch the >beginning of the video mem to anywhere in the video cards memory space. > >This would mean one could easily do double buffering, by writing to the >right area of memory, then changing the one address, and eliminating >annoying flicker. Is this currently supported by FreeBSD? > >I am also curious if 06h has been implemented, to allow pan and scrolling to >be done. These functions are not currently accessible from the userland via the vesa module. However, it is planned that the next update on the video drivers and the vesa module will add these services. BTW, the VESA function 06h is not for panning and scrolling. It's to change the size of the scan line. Panning and scrolling are achieved by the function 07h. Kazu PS: in the meantime, I have to fix kernel panic related to screen savers first ;-< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message