From owner-freebsd-hackers Sun Jul 13 00:00:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA08799 for hackers-outgoing; Sun, 13 Jul 1997 00:00:36 -0700 (PDT) Received: from friley01.res.iastate.edu (friley01.res.iastate.edu [129.186.189.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA08794 for ; Sun, 13 Jul 1997 00:00:31 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.6/8.8.5) with ESMTP id CAA12323 for ; Sun, 13 Jul 1997 02:02:26 -0500 (CDT) Message-Id: <199707130702.CAA12323@friley01.res.iastate.edu> X-Mailer: exmh version 2.0delta 6/3/97 To: hackers@freebsd.org Subject: DMA directly to user space? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Jul 1997 02:02:25 -0500 From: Chris Csanady Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am looking into implementing something along the lines of SGI's /dev/hippi, only for a gigabit ethernet device. Basically, you would write frames to the device, and it would ship them off. The thing is, I am looking for a way to do this without copying any data. Is this possible? Are there any existing devices that do such things? DMAing to userspace seems ideal, but I'm not sure how you could ensure that the memory is aligned and contiguous. Or how to deal with the user/kernel space boundry crossing. Another thought was remapping pages from the kernel to the process. However, this seems like even more of a memory management nightmare. If anyone has any ideas on how I could do this either way, I'd appreciate it. Doing a copy would greatly simplify things, but at these speeds, there doesn't seem to be much bandwidth left as it is. It also becomes quite apparent how inefficient our TCP/IP stack is. :( Chris Csanady From owner-freebsd-hackers Sun Jul 13 00:21:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09370 for hackers-outgoing; Sun, 13 Jul 1997 00:21:34 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09362 for ; Sun, 13 Jul 1997 00:21:28 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA05038; Sun, 13 Jul 1997 09:21:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA15740; Sun, 13 Jul 1997 09:05:26 +0200 (MET DST) Message-ID: <19970713090526.UC00767@uriah.heep.sax.de> Date: Sun, 13 Jul 1997 09:05:26 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: weasel@temp.harborcom.net (Bradley Reynolds) Subject: Re: Data Recovery References: <199707120252.MAA27497@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Bradley Reynolds on Jul 13, 1997 01:54:05 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bradley Reynolds wrote: > > Do you know the details of the disklabel, ie. which partitions were where? > > If so, you can recreate the label fairly painlessly. > > > Its been tried and didn't work. ``Didn't work'' is nothing you should ever quote in a technical forum. It's a useless sentence. If you want help, you need at least to tell us why it didn't work, or what happened. You also need to tell us _how_ you tried it, and it would help if you let us know about which details of the original setup you remember, and which you eventually forgot. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jul 13 01:52:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11663 for hackers-outgoing; Sun, 13 Jul 1997 01:52:25 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA11658 for ; Sun, 13 Jul 1997 01:52:21 -0700 (PDT) Message-Id: <199707130852.BAA11658@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA076603306; Sun, 13 Jul 1997 18:41:46 +1000 From: Darren Reed Subject: Re: ipfw rules processing order when DIVERTing To: archie@whistle.com (Archie Cobbs) Date: Sun, 13 Jul 1997 18:41:46 +1000 (EST) Cc: julian@whistle.com, archie@whistle.com, owensc@enc.edu, freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi In-Reply-To: <199707102329.QAA04387@bubba.whistle.com> from "Archie Cobbs" at Jul 10, 97 04:29:50 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Archie Cobbs, sie said: > Yes! ``It could start processing at the next higher number.'' > I agree with that :-) > > The problem is that when the packet returns to the kernel from > user-land, that bit of state that says "this packet has already > seen rules 1-2000 (or whatever)" is lost, and you can't retrieve > it. The only way to do this would be for the user-land process > to send back some additional info that says "skip to rule 2000". > > Doable, but .. not very pretty? what if the packet is changed enough to make the outcome of starting at N+1 different to starting at 1 ? From owner-freebsd-hackers Sun Jul 13 05:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17028 for hackers-outgoing; Sun, 13 Jul 1997 05:43:32 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17023 for ; Sun, 13 Jul 1997 05:43:29 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id GAA10485; Sun, 13 Jul 1997 06:54:18 -0400 (EDT) From: Peter Dufault Message-Id: <199707131054.GAA10485@hda.hda.com> Subject: Re: DMA directly to user space? In-Reply-To: <199707130702.CAA12323@friley01.res.iastate.edu> from Chris Csanady at "Jul 13, 97 02:02:25 am" To: ccsanady@friley01.res.iastate.edu (Chris Csanady) Date: Sun, 13 Jul 1997 06:54:16 -0400 (EDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The thing is, I am looking for a way to do this without copying any data. > Is this possible? Are there any existing devices that do such things? > DMAing to userspace seems ideal, but I'm not sure how you could ensure > that the memory is aligned and contiguous. Or how to deal with the > user/kernel space boundry crossing. All raw I/O works that way. Handle misaligned memory by faulting, punting the issue back to the application. Basically write a strategy function and hook it in as a raw device and you'll have read and write directly to the user space. Non-contiguous memory must be handled either by the device hardware via some flavor of scatter-gather hardware (hopefully you'll find the device in question already does that) or by allocating contiguous memory. -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hackers Sun Jul 13 06:40:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA18727 for hackers-outgoing; Sun, 13 Jul 1997 06:40:25 -0700 (PDT) Received: from george.rutgers.edu (muralir@george.rutgers.edu [128.6.5.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA18716 for ; Sun, 13 Jul 1997 06:40:18 -0700 (PDT) Received: from localhost (muralir@localhost) by george.rutgers.edu (8.8.5/8.8.5) with SMTP id JAA19576 for ; Sun, 13 Jul 1997 09:40:16 -0400 (EDT) Date: Sun, 13 Jul 1997 09:40:16 -0400 (EDT) From: Murali Rangarajan To: freebsd-hackers@freebsd.org Subject: help on cgi... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've installed apache as the http server on my machine running FreeBSD 2.2 release. I'm unable to get the cgi scripts to work even though I think I've set up the .conf files properly... ANy suggestions from guys who have done it for their machines? Thanks Murali From owner-freebsd-hackers Sun Jul 13 08:27:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22718 for hackers-outgoing; Sun, 13 Jul 1997 08:27:57 -0700 (PDT) Received: from wafu.netgate.net (wafu.netgate.net [204.145.147.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22713 for ; Sun, 13 Jul 1997 08:27:53 -0700 (PDT) Received: from chiota.signet.or.jp (INS91.tama.dti.ne.jp [210.159.144.45]) by wafu.netgate.net (8.7.5/8.7.3) with ESMTP id HAA04417; Sun, 13 Jul 1997 07:21:36 GMT Message-Id: <199707130721.HAA04417@wafu.netgate.net> Received: from chiota.signet.or.jp (localhost.signet.or.jp [127.0.0.1]) by chiota.signet.or.jp (8.8.5/) with ESMTP id AAA00602; Mon, 14 Jul 1997 00:28:34 +0900 (JST) To: hackers@freebsd.org Cc: shigio@wafu.netgate.net Subject: RFC about vi's new function Date: Mon, 14 Jul 1997 00:28:33 +0900 From: Shigio Yamaguchi Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm thinking about new function on ex command line. How about using '^' as a line number of current position on ex command line? It is like this. :!emacs +^ % emacs +122 editing_file o Is this useful? o Is this the correct way to do it? o Are there better candidate character other than '^'? I'm ready to write a patch for it. Thank you in advanced. -- Shigio Yamaguchi (Freelance programmer) Mail: shigio@wafu.netgate.net, WWW: http://wafu.netgate.net/tama/ From owner-freebsd-hackers Sun Jul 13 08:52:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24142 for hackers-outgoing; Sun, 13 Jul 1997 08:52:24 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA24137 for ; Sun, 13 Jul 1997 08:52:21 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Sun, 13 Jul 1997 11:51:50 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA22829; Sun, 13 Jul 97 11:51:48 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id LAA04866; Sun, 13 Jul 1997 11:49:47 -0400 Message-Id: <19970713114946.61308@ct.picker.com> Date: Sun, 13 Jul 1997 11:49:46 -0400 From: Randall Hopper To: Chuck Robey , Nathan Dorfman , FreeBSD-Hackers Subject: Re: upgrading XFree86 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Chuck Robey on Sat, Jul 12, 1997 at 12:11:22AM -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey: |I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my |existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an |overlay? Otherwise, this's gonna be the upgrade from hell ... I know what you mean. For the same reason we compile non-X ports into /usr/local, I'd sure like to see our X ports compiled for /usr/local/X11. I've never untarring on top of an existing dist because: 1) some XFree alphas I believe have mentioned, don't do that -- it won't work, and 2) if I don't like the new version, I'll want to go back or switch back and forth to help debug the new, and no guarentee that untarring the old on top will get me back to square 1 (likely, but no guarentee). [Backing the whole thing up first is a pain and a space killer, and (for me) the only reason to do that is because all our ports are mingled into the files]. I instead use a custom script to cross-link all the port files into the new distdir, and then make /usr/X11R6 a symlink. Works, but wish it wasn't necessary. Randall Hopper From owner-freebsd-hackers Sun Jul 13 09:48:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27606 for hackers-outgoing; Sun, 13 Jul 1997 09:48:20 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27597 for ; Sun, 13 Jul 1997 09:48:16 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id SAA28393; Sun, 13 Jul 1997 18:47:59 +0200 (SAT) From: John Hay Message-Id: <199707131647.SAA28393@zibbi.mikom.csir.co.za> Subject: Re: IPX routing? In-Reply-To: <199707130323.MAA01113@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jul 13, 97 12:53:07 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 13 Jul 1997 18:47:59 +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 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Is there a document anywhere which describes the delicacies of setting > up a FreeBSD box as an IPX router? Nope, except maybe in the mail archives where I have helped a few people to get it working. There has been someone who promissed to write it up and get into the handbook, but it hasn't happened yet. > It was at this point that things came unstuck; adding IPX support to > the kernel was quite straightforward, as was assigning IPX addresses > to the interface. > > Except that one can only assign a single net address to each > interface, and Netware servers insist on using different net addresses > for 802.2 and 802.3 frame types. This isn't discussed in any of the > documentation. 8( > > Next, IPXrouted was started, and in trace mode it was certainly seeing > a lot of relevant traffic, but it wasn't learning any routes from it. > > After much tinkering trying to make various things work, we had to > back the system out and reinstate the Novell server, something that > neither I nor the customer really wanted to do. > > So, any suggestions? I could probably be convinced to roll some > longer words onthe subject if the information was available... > At the moment the code in FreeBSD only do Ethernet_II framing, so you will have use that on the nets that connects to the FreeBSD box. I do have code that do the Novel 802.3 protocol, but it only works on the ed0 type cards because I use link1 in ifconfig to set it and most other cards use that for something else like switching 10BT on/off. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Sun Jul 13 10:03:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28451 for hackers-outgoing; Sun, 13 Jul 1997 10:03:23 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28446 for ; Sun, 13 Jul 1997 10:03:20 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id NAA27040; Sun, 13 Jul 1997 13:03:18 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id NAA15150; Sun, 13 Jul 1997 13:03:16 -0400 Date: Sun, 13 Jul 1997 13:03:25 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Randall Hopper cc: Nathan Dorfman , FreeBSD-Hackers Subject: Re: upgrading XFree86 In-Reply-To: <19970713114946.61308@ct.picker.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Randall Hopper wrote: > Chuck Robey: > |I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > |existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > |overlay? Otherwise, this's gonna be the upgrade from hell ... > > I know what you mean. For the same reason we compile non-X ports into > /usr/local, I'd sure like to see our X ports compiled for /usr/local/X11. This'd be pretty difficult, I think, because of imake's very incestuous relationship with the X11R6 tree. It would be a fantastic win, but I just don't think it'd be possible. > > I've never untarring on top of an existing dist because: 1) some XFree > alphas I believe have mentioned, don't do that -- it won't work, and 2) if > I don't like the new version, I'll want to go back or switch back and forth > to help debug the new, and no guarentee that untarring the old on top will > get me back to square 1 (likely, but no guarentee). [Backing the whole > thing up first is a pain and a space killer, and (for me) the only reason > to do that is because all our ports are mingled into the files]. I instead > use a custom script to cross-link all the port files into the new distdir, > and then make /usr/X11R6 a symlink. Works, but wish it wasn't necessary. > > Randall Hopper > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jul 13 10:25:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29550 for hackers-outgoing; Sun, 13 Jul 1997 10:25:32 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA29544 for ; Sun, 13 Jul 1997 10:25:27 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id TAA29973; Sun, 13 Jul 1997 19:25:08 +0200 Message-ID: <33C90F7A.41C67EA6@bonn-online.com> Date: Sun, 13 Jul 1997 19:25:14 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hackers@freebsd.org Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> <19970711211440.BV38545@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > If you're NFS-exporting your /usr/local, you are basically expected to > care for /usr/local/etc yourself. Typically, this would be a symlink > to /etc/local/ then. There's quite more in /usr/local/etc that will > make it machine-specific, like various configuration files. > > This should probably be mentioned somewhere. > But /usr/local is *very* likely to be NFS-exported in a NIS/NFS-server environment. So it should not be used for host specific data anyway. You suggest this yourself, to use /etc/local instead of /usr/local/etc. What would be the disadvantages if we used /etc/local by default (on machines in an nfs-less environment) ? -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Sun Jul 13 11:12:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01711 for hackers-outgoing; Sun, 13 Jul 1997 11:12:57 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA01706 for ; Sun, 13 Jul 1997 11:12:52 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id NAA03005; Sun, 13 Jul 1997 13:12:32 -0500 (EST) Date: Sun, 13 Jul 1997 13:12:31 -0500 (EST) From: John Fieber To: Chuck Robey cc: Randall Hopper , Nathan Dorfman , FreeBSD-Hackers Subject: Re: upgrading XFree86 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Chuck Robey wrote: > On Sun, 13 Jul 1997, Randall Hopper wrote: > > > Chuck Robey: > > |I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > > |existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > > |overlay? Otherwise, this's gonna be the upgrade from hell ... > > > > I know what you mean. For the same reason we compile non-X ports into > > /usr/local, I'd sure like to see our X ports compiled for /usr/local/X11. > > This'd be pretty difficult, I think, because of imake's very incestuous > relationship with the X11R6 tree. It would be a fantastic win, but I just > don't think it'd be possible. Some time ago I tried in vain to get things to work outside of /usr/X11R6. However, the imake stuff has changed quite a bit in the last couple releases---I discovered this when trying to re-compile Motif 2.0 with R6.3. There were a quite a few improvements, some of which might be helpful. However, I start feeling homicidal if I work with imake too long so I would encourage someone else to revisit the issue. :) Have a look at http://www.primate.wisc.edu/software/imake-stuff/ for some useful information about recent changes. -john From owner-freebsd-hackers Sun Jul 13 11:21:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA02068 for hackers-outgoing; Sun, 13 Jul 1997 11:21:22 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA02057 for ; Sun, 13 Jul 1997 11:21:19 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA11280 for freebsd-hackers@freebsd.org; Sun, 13 Jul 1997 20:21:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id TAA16977; Sun, 13 Jul 1997 19:53:54 +0200 (MET DST) Message-ID: <19970713195353.AD25187@uriah.heep.sax.de> Date: Sun, 13 Jul 1997 19:53:53 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> <19970711211440.BV38545@uriah.heep.sax.de> <33C90F7A.41C67EA6@bonn-online.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33C90F7A.41C67EA6@bonn-online.com>; from Sebastian Lederer on Jul 13, 1997 19:25:14 +0200 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Sebastian Lederer wrote: > What would be the disadvantages if we used > /etc/local by default (on machines in an nfs-less environment) ? The ports paradigm is to not install/modify anything outside ${PREFIX} (except indirectly, e.g. by running ldconfig -m). The number of NFS-exported /usr/local's probably makes 5 % of the installed base (wild guess). Just since it applies to you doesn't mean it's a very general configuration. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jul 13 12:00:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03437 for hackers-outgoing; Sun, 13 Jul 1997 12:00:17 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03429 for ; Sun, 13 Jul 1997 12:00:12 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id MAA01735 for ; Sun, 13 Jul 1997 12:00:13 -0700 (PDT) Message-Id: <199707131900.MAA01735@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: aha1522 ?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Jul 1997 12:00:13 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Move from the sane list.... Do we have an aha1522 expert? Cheers, Amancio gord@m-tech.ab.ca said: > Hi! > >>>>> eric writes: > e> First, it wasn't a matter of the scanner blocking the scsi bus -- > e> it had an entire scsi bus to itself on an Adaptec 1522 (which > e> turned out to be the problem) Second, I'm using the "pt" driver, > e> although i suspect the "uk" driver would work too now that I've > e> moved the scanner to an Adaptec 2940W. Everything works more or > e> less fine now, except the scanner still needs to be the _only_ > e> device on the bus. If I put a disk on the same bus as the scanner, > e> (with a different SCSI id# obviously) accesses to the disk time > e> out and stuff. It seems like it may be a termination issue, which > e> I'll fiddle around with some more. But anyway, it will not work > e> at all using an AHA1522, with either a Umax or an HP4c scanner. > Amancio... > I have a strong suspicion that the FreeBSD AHA1522 driver is a little > flaky. Last year, when I was trying to port the PINT (`ss' SCSI > scanner device) driver to FreeBSD 2.1.5 using my AHA1522, I ran into > endless problems, because the scanner just *would not respond* to any > commands I sent it. > It was very frustrating, and at the time, I attributed it to my shoddy > kernel hacking, so I did not report the bug. > When I talked more with PINT's author, and tried both `upgrading' > (?... don't know if that's the right word for it) to NetBSD 1.2, then > reintegrating PINT, it worked like a charm. > Later, I became even more convinced that my kernel hacking job had > been correct, and that FreeBSD's AHA1522 driver was at fault. Again, > I didn't report this because I didn't have a FreeBSD machine any more > in order to narrow down the bug. > Anyway, now that it appears somebody else is having the same problem, > this may be an opportunity to find out what it is. > Right now I'm running my ScanJet 4p with an AHA1522 under Linux > without any problems, and as I said before, it also worked under > NetBSD. > Thanks for any comments you folks may have. I'd really like to figure > out if this behaviour is a driver bug, so that the FreeBSD folks can > fix it (if it isn't fixed already)! :) > -- > Gord Matzigkeit | Proudly running pieces of the GNU operating > system. > gord@m-tech.ab.ca | Jacques Cousteau loved programming in > assembler. From owner-freebsd-hackers Sun Jul 13 13:51:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06928 for hackers-outgoing; Sun, 13 Jul 1997 13:51:50 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06923 for ; Sun, 13 Jul 1997 13:51:46 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA08663; Sun, 13 Jul 1997 13:42:06 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008648; Sun Jul 13 20:42:00 1997 Date: Sun, 13 Jul 1997 13:39:45 -0700 (PDT) From: Julian Elischer To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: TCP bug in 2.2 In-Reply-To: <199707122153.OAA28921@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Terry Lambert wrote: > > If I could borrow the ear of someone with more knowledge of TCP > > states than me.. > > > > We see the following in a kernel dated from around March 4 > > and from the logs it looks as if it's present in 2.2.2+ > > > > finger, (after a lot of iterations of the test) > > goes into a permanent wait reading from a socket. > > > > the socket is seen to be in FIN_WAIT_2 state > > after the finger proces is killed the socket STAYS in FIN_WAIT_2 > > state forever. > > > > from what I've read in tcp_input.c etc. This shouldn't happen. > > > > 2 problems: > > 1/ why doesn't finger wake up and return EOF? > > Probably you have an Annex or similar terminal server which has a > buggy TCP/IP implementation which does not correctly do option > negotiation. > > tcp_extensions=NO Terry, I am aware of that ok? And yes TCP exensions WAS (to our surprise) enabled on that machine. We have since turned it off, however despite this it should be IMPOSSIBLE to hang a socket in that way. > > > Also, get an updated stack forwhatever hardware you have which is > failing to implement TCP/IP according to the RFC's. There could be > less obvious problems with the stack as well, so it's a good idea > to not trust it until it's updated. it was SOLARIS 2.5.1 and it didn't happen consitently so it's a race condition of some sort. > > > > > 2/ why doesn't the close() ofthe socket start > > the 2MSL timer? > > This is generally the case with Winsock implementations in general > and Microsoft's in particular. Microsoft OS's don't do resource > tracking correctly, and so even though you can now tell that a > program has exited in Windows95, the Windows 3.1 Winsock code still > requires that the client application call "shutdown()" on the socket > prior to closing it. Basically, Microsoft's TCP/IP stack is too > stupid to send the FIN like it's supposed to on the close. As I said.. SOLARIS 2.5.1 but no matter WHAT OS, we should not have a code path that can get to the state that a tcp session is totally hung, without a timer running for it. > > 1) You reboot a machine without shuttding down all Winsock > clients. The solaris machine was not rebooted. > > 2) Your client program crashes and expect the OS to be able > to back out state on its behalf. > > 3) The client software was ported from a sane TCP/IP environment, > like UNIX, and the programmers have no idea that "shutdown()" > is supposed to be called (amazingly enough, on UNIX systems, > calling "shutdown()" shuts the machine down... who would have > ever thought of naming a function for what the function does? > Apparently not the originators of Winsock.). > > > Try correcting your client software. Also try running client machines > with OS's that can't be crashed by client programs (ie: real protected > mode operating systems). Finally, try running an OS that knows how to > recover resources that a program was using in the event of a program > crash which does not crash the OS (ie: real protected mode operating > systems). > > > and either tcp_usrclosed() is not being called > > during the socket closure for some reason, > > or the timer is being continually reset by something else. > > The timer is not started until the FIN is sent if SO_KEEPALIVE was > specified by the client. It usually is. I'll check this but it still seems to be a bug to me because the socket is in FIN_WAIT2 state and HAS BEEN CLOSED. From owner-freebsd-hackers Sun Jul 13 15:02:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09304 for hackers-outgoing; Sun, 13 Jul 1997 15:02:53 -0700 (PDT) Received: from ucsee.EECS.Berkeley.EDU (benco@ucsee.EECS.Berkeley.EDU [128.32.156.173]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09299 for ; Sun, 13 Jul 1997 15:02:49 -0700 (PDT) Received: (from benco@localhost) by ucsee.EECS.Berkeley.EDU (8.8.4/8.8.4) id PAA21450 for freebsd-hackers@freebsd.org; Sun, 13 Jul 1997 15:02:47 -0700 Date: Sun, 13 Jul 1997 15:02:47 -0700 From: Ben Cottrell Message-Id: <199707132202.PAA21450@ucsee.EECS.Berkeley.EDU> To: freebsd-hackers@freebsd.org Subject: Re: upgrading XFree86 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This'd be pretty difficult, I think, because of imake's very incestuous > relationship with the X11R6 tree. It would be a fantastic win, but I just > don't think it'd be possible. My customary solution to this is to use a union mount to put /usr/local/X11 on top of /usr/X11R6. That way I can replace the underlying X tree, and my local changes go right back on top afterwards. ~Ben From owner-freebsd-hackers Sun Jul 13 15:13:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09891 for hackers-outgoing; Sun, 13 Jul 1997 15:13:36 -0700 (PDT) Received: from punt-2.mail.demon.net (punt-2c.mail.demon.net [194.217.242.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA09865 for ; Sun, 13 Jul 1997 15:13:24 -0700 (PDT) Received: from longacre.demon.co.uk ([158.152.156.24]) by punt-2.mail.demon.net id aa0523188; 13 Jul 97 19:08 BST From: Michael Searle Message-ID: To: hackers@freebsd.org Subject: Re: sd0 timed out while idle References: <199707112133.OAA04679@hub.freebsd.org> Date: Sun, 13 Jul 1997 13:05:44 BST X-Mailer: Offlite 0.09 / Termite Internet for Acorn RISC OS Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk owner-hackers-digest@FreeBSD.ORG wrote: > On Fri, 11 Jul 1997, Jamie Bowden wrote: >> The 2.5G Bigfoot drives were fine and ran very cool. The Quantum SCSI >> drives are the ones that have overheating problems. > Bigfoot drives are 3400rpm, which makes them cool, and really slow. > Until, I saw the Bigfoot specs, I had no idea that anybody made anything > slower than 5400rpm these days! There's loads of 4500rpm 3.5" IDE drives still around. (maybe they're not made any more, but they are still sold.) And nearly all 2.5" IDE drives are 4000-4500rpm. -- Michael Searle - csubl@csv.warwick.ac.uk From owner-freebsd-hackers Sun Jul 13 15:43:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA11280 for hackers-outgoing; Sun, 13 Jul 1997 15:43:40 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11275 for ; Sun, 13 Jul 1997 15:43:35 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id SAA07827; Sun, 13 Jul 1997 18:43:33 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA02149; Sun, 13 Jul 1997 18:43:31 -0400 Date: Sun, 13 Jul 1997 18:43:39 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Ben Cottrell cc: freebsd-hackers@FreeBSD.ORG Subject: Re: upgrading XFree86 In-Reply-To: <199707132202.PAA21450@ucsee.EECS.Berkeley.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Ben Cottrell wrote: > > This'd be pretty difficult, I think, because of imake's very incestuous > > relationship with the X11R6 tree. It would be a fantastic win, but I just > > don't think it'd be possible. > > My customary solution to this is to use a union mount to put > /usr/local/X11 on top of /usr/X11R6. That way I can replace the > underlying X tree, and my local changes go right back on top > afterwards. If union mounts worked reliably, and did not crash the machine, that'd be a good idea. I don't think they are that stable, tho. Good luck! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jul 13 16:21:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12707 for hackers-outgoing; Sun, 13 Jul 1997 16:21:21 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12700 for ; Sun, 13 Jul 1997 16:21:16 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id TAA01158 for hackers@freebsd.org; Sun, 13 Jul 1997 19:21:14 -0400 (EDT) Date: Sun, 13 Jul 1997 19:21:14 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707132321.TAA01158@pandora.hh.kew.com> To: hackers@freebsd.org Subject: access to SIO port freezes FreeBSD 2.2.1 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's a wacky one ... I have two systems both running FreeBSD 2.2.1 with four serial ports enabled. athena is a 386/33 with 16M, ISA bus, two dumb serial ports, two internal modems with FIFO UARTS. Modems are COM3/COM4, IRQ 5 and 9; one is IBM/Reveal v.32, other is Zoom v.34 pandora is a 386/66 with VLB for the display, but mostly ISA with two dumb serial ports and two 16650x uarts. FIFO UARTs are COM3/COM4, IRQ 9 and 5. Due to a "little" accident with athena (why in hell I give myself root password, I don't know, but it's another story anyway), I needed to put the modems into pandora. So I disable the internal dumb ports, move the FIFO UART's to COM1/COM2, and put the modems in at COM3/COM4, IRQ 5 and regen the kernel, and system comes up fine. Then I enable ttyd2 and ttyd3, and HUP init, and it hangs. Solid. Can't even get console to switch screens or reboot. Works out that ttyd3 works, but not ttyd2 (v.32). Windows 95 sees it, FreeBSD sees it, but locks solid when opening. Same two modems worked great 24 hours before on pandora's little sister. Suggestions as to where to look? -ahd- -- Drew Derbyshire Internet: ahd@kew.com Kendra Electronic Wonderworks Telephone: 617-279-9812 "Men are like fudge: sweet, but dense and rarely good for you." -- Audrey Walton-Hadlock, '99 From owner-freebsd-hackers Sun Jul 13 18:26:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19042 for hackers-outgoing; Sun, 13 Jul 1997 18:26:24 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19034 for ; Sun, 13 Jul 1997 18:26:20 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA13945; Sun, 13 Jul 1997 18:26:55 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd013942; Mon Jul 14 01:26:46 1997 Message-ID: <33C97FBE.41C67EA6@whistle.com> Date: Sun, 13 Jul 1997 18:24:14 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Darren Reed CC: Archie Cobbs , owensc@enc.edu, freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing References: <199707130852.BAA26310@gatekeeper.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed wrote: > > In some mail from Archie Cobbs, sie said: > > Yes! ``It could start processing at the next higher number.'' > > I agree with that :-) > > > > The problem is that when the packet returns to the kernel from > > user-land, that bit of state that says "this packet has already > > seen rules 1-2000 (or whatever)" is lost, and you can't retrieve > > it. The only way to do this would be for the user-land process > > to send back some additional info that says "skip to rule 2000". > > > > Doable, but .. not very pretty? > > what if the packet is changed enough to make the outcome of starting at > N+1 different to starting at 1 ? As I said earlier, this is the main argument FOR keeping it as it is... the new semantic however would allow this decision to be taken by the diverting program. If it feeds it back with the received line number processing carries on where it left off. if it sets it to 0 processing restarts at the beginning... it would be easier to set up "cascades" of processes where you could chain theoutput of one to another.. I'd also like to see the 'only forwards' rule with 'skipto' removed.. and some sort of 'subroutine' capability. :) julian From owner-freebsd-hackers Sun Jul 13 18:55:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20769 for hackers-outgoing; Sun, 13 Jul 1997 18:55:53 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20763 for ; Sun, 13 Jul 1997 18:55:48 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA24197; Mon, 14 Jul 1997 11:53:51 +1000 (EST) Message-ID: <19970714115351.32520@rf900.physics.usyd.edu.au> Date: Mon, 14 Jul 1997 11:53:51 +1000 From: David Dawes To: Randall Hopper Cc: Chuck Robey , Nathan Dorfman , FreeBSD-Hackers Subject: Re: upgrading XFree86 References: <19970713114946.61308@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19970713114946.61308@ct.picker.com>; from Randall Hopper on Sun, Jul 13, 1997 at 11:49:46AM -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 13, 1997 at 11:49:46AM -0400, Randall Hopper wrote: >Chuck Robey: > |I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > |existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > |overlay? Otherwise, this's gonna be the upgrade from hell ... > >I know what you mean. For the same reason we compile non-X ports into >/usr/local, I'd sure like to see our X ports compiled for /usr/local/X11. > >I've never untarring on top of an existing dist because: 1) some XFree >alphas I believe have mentioned, don't do that -- it won't work, and 2) if Did they? No XFree86 alphas were ever made available to the public, and all of the public releases could be installed in this way (that's how I always install them). The only caveat is that the provided preinst.sh script should be run first. There has been the odd case of a file being replaced with a directory of the same name, and the provided script would remove such files first. >I don't like the new version, I'll want to go back or switch back and forth >to help debug the new, and no guarentee that untarring the old on top will >get me back to square 1 (likely, but no guarentee). [Backing the whole >thing up first is a pain and a space killer, and (for me) the only reason >to do that is because all our ports are mingled into the files]. I instead Another reason to back things up is if you've customised anything within /usr/X11R6. I guess everyone has to weigh up the pain of backing up against the pain of recovering from problems (even unrelated ones like a disk failure). >use a custom script to cross-link all the port files into the new distdir, >and then make /usr/X11R6 a symlink. Works, but wish it wasn't necessary. Each to his own. I personally find it much simpler to backup the old directory. David From owner-freebsd-hackers Sun Jul 13 18:58:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20954 for hackers-outgoing; Sun, 13 Jul 1997 18:58:03 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20947 for ; Sun, 13 Jul 1997 18:57:58 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id LAA24222; Mon, 14 Jul 1997 11:57:41 +1000 (EST) Message-ID: <19970714115741.38405@rf900.physics.usyd.edu.au> Date: Mon, 14 Jul 1997 11:57:41 +1000 From: David Dawes To: Chuck Robey Cc: Randall Hopper , Nathan Dorfman , FreeBSD-Hackers Subject: Re: upgrading XFree86 References: <19970713114946.61308@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Chuck Robey on Sun, Jul 13, 1997 at 01:03:25PM -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 13, 1997 at 01:03:25PM -0400, Chuck Robey wrote: >On Sun, 13 Jul 1997, Randall Hopper wrote: > >> Chuck Robey: >> |I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my >> |existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an >> |overlay? Otherwise, this's gonna be the upgrade from hell ... >> >> I know what you mean. For the same reason we compile non-X ports into >> /usr/local, I'd sure like to see our X ports compiled for /usr/local/X11. > >This'd be pretty difficult, I think, because of imake's very incestuous >relationship with the X11R6 tree. It would be a fantastic win, but I just >don't think it'd be possible. It should be possible, but the task isn't a trivial one. I'd really like to see it happen though. I'd do it myself if I could still see the end of my TODO list. David From owner-freebsd-hackers Sun Jul 13 20:29:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24719 for hackers-outgoing; Sun, 13 Jul 1997 20:29:18 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust59.Max17.Washington.DC.MS.UU.NET [153.34.57.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24713; Sun, 13 Jul 1997 20:29:05 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id XAA07021; Sun, 13 Jul 1997 23:29:00 -0400 (EDT) Message-ID: <19970713232900.32111@wakky.dyn.ml.org> Date: Sun, 13 Jul 1997 23:29:00 -0400 From: Lee Cremeans To: brian@freebsd.org Cc: hackers@freebsd.org Subject: PPP -alias and DCC RESUME Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e Reply-to: hcremean@vt.edu X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed something tonight: The alias_irc.c in ppp-970620 and 970629 doesn't seem to handle DCC RESUME (a mIRCism that's supported by the EPIC versions of ircII) correctly. When I turn off aliasing, things work, but from the looks of the code in alias_irc.c, it should be working even with aliasing ON. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower)|A! JW223 "People are idiots who deserve to be mocked."--Dogbert|YWD+++i P&B+++ SL+++^i My home page:http://wakky.dyn.ml.org/~lee | MD+++r P+ I++ Di "Whoa, dumber than advertised!" | $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi From owner-freebsd-hackers Sun Jul 13 20:46:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25304 for hackers-outgoing; Sun, 13 Jul 1997 20:46:43 -0700 (PDT) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25299 for ; Sun, 13 Jul 1997 20:46:37 -0700 (PDT) Received: from saturn.ajc.state.net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with SMTP id WAA22943 for ; Sun, 13 Jul 1997 22:45:23 -0500 (CDT) Received: by localhost with Microsoft MAPI; Sun, 13 Jul 1997 22:44:21 -0500 Message-ID: <01BC8FDE.4DE20120.Al.Johnson@AJC.State.Net> From: Al Johnson To: "'hackers@freebsd.org'" Subject: What I consider and odd install Date: Sun, 13 Jul 1997 22:44:20 -0500 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey folks, I've been among the FreeBSD ranks for some time now but I've got my self in a spot I can't figure my way out of. I've got 3 machines running 2.2.2-RELEASE all the time. Dedicated disk (no funky partitions) serving specific purposes. My problem is that two of them are 486's and one is a Pentium 75. Needless to say it's difficult to keep current on machine like this when a make includes;make world takes somewhere around 14 hours. Now to the problem. I've a GW2K Pentrium Pro 180 that I want to use for compiles of any package. It's got a 3.8GB EIDE Disk and CDROM. I've also got an Adaptec 2940UW SCSI with a 1GB fixed disk, 8G tape unit, 135Syquest (ya I know), and 1G Jaz drive. I want FreeBSD on the Jaz drive since I won't be using it all the time (The machine runs mostly Win95...uggg) No matter what I do I can't get the FreeBSD boot manager to give me the option of booting from the JAZ drive. I've gone thru and made sure it's BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB Seagate, 82h JAZ, 83h EZ135. Any suggestions as to a solution or pointers to where I can get more info would be greatly appreciated. I'm really interested in seeing just how well FreeBSD run when it's allowed to open up an a PPro 180 with 64MB of memory as opposed to my 486/66 with 16MB. Thanks for the help, -- Al ------------------------------------------------------------------------ ------- Al Johnson Consulting Rescuing ISP's pays my bills. From owner-freebsd-hackers Sun Jul 13 21:21:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26949 for hackers-outgoing; Sun, 13 Jul 1997 21:21:38 -0700 (PDT) Received: from pluto.plutotech.com (root@[206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26940 for ; Sun, 13 Jul 1997 21:21:32 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id WAA05785; Sun, 13 Jul 1997 22:20:54 -0600 (MDT) Message-Id: <199707140420.WAA05785@pluto.plutotech.com> To: Al Johnson cc: "'hackers@freebsd.org'" Subject: Re: What I consider and odd install In-reply-to: Your message of "Sun, 13 Jul 1997 22:44:20 CDT." <01BC8FDE.4DE20120.Al.Johnson@AJC.State.Net> Date: Sun, 13 Jul 1997 22:20:54 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >No matter what I do I can't get the FreeBSD boot manager to give me the >option of booting from the JAZ drive. I've gone thru and made sure it's >BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB >Seagate, 82h JAZ, 83h EZ135. Perhaps it will work if you enable "support more than two disks" in the BIOS options for the 2940. >Thanks for the help, > > -- Al > >------------------------------------------------------------------------ >------- >Al Johnson Consulting >Rescuing ISP's pays my bills. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Sun Jul 13 21:31:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27712 for hackers-outgoing; Sun, 13 Jul 1997 21:31:49 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27703 for ; Sun, 13 Jul 1997 21:31:42 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA07478; Mon, 14 Jul 1997 14:00:25 +0930 (CST) From: Michael Smith Message-Id: <199707140430.OAA07478@genesis.atrad.adelaide.edu.au> Subject: Re: What I consider and odd install In-Reply-To: <01BC8FDE.4DE20120.Al.Johnson@AJC.State.Net> from Al Johnson at "Jul 13, 97 10:44:20 pm" To: Al.Johnson@AJC.State.Net (Al Johnson) Date: Mon, 14 Jul 1997 14:00:24 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Al Johnson stands accused of saying: > > No matter what I do I can't get the FreeBSD boot manager to give me the > option of booting from the JAZ drive. I've gone thru and made sure it's > BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB > Seagate, 82h JAZ, 83h EZ135. The bootmangler (and many BIOSsen) only supports booting from the first two drives. You may have better luck installing a different boot manager. (eg. OS-BS) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jul 13 21:42:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28438 for hackers-outgoing; Sun, 13 Jul 1997 21:42:18 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28433 for ; Sun, 13 Jul 1997 21:42:14 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id AAA00266; Mon, 14 Jul 1997 00:42:09 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id AAA27844; Mon, 14 Jul 1997 00:42:03 -0400 Date: Mon, 14 Jul 1997 00:42:08 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Al Johnson cc: "'hackers@freebsd.org'" Subject: Re: What I consider and odd install In-Reply-To: <01BC8FDE.4DE20120.Al.Johnson@AJC.State.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Al Johnson wrote: > Now to the problem. I've a GW2K Pentrium Pro 180 that I want to use for > compiles of any package. It's got a 3.8GB EIDE Disk and CDROM. I've also > got an Adaptec 2940UW SCSI with a 1GB fixed disk, 8G tape unit, 135Syquest > (ya I know), and 1G Jaz drive. I want FreeBSD on the Jaz drive since I > won't be using it all the time (The machine runs mostly Win95...uggg) > > No matter what I do I can't get the FreeBSD boot manager to give me the > option of booting from the JAZ drive. I've gone thru and made sure it's > BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB > Seagate, 82h JAZ, 83h EZ135. > > Any suggestions as to a solution or pointers to where I can get more info > would be greatly appreciated. I'm really interested in seeing just how > well FreeBSD run when it's allowed to open up an a PPro 180 with 64MB of > memory as opposed to my 486/66 with 16MB. Al, on the Jaz drive, is either the FreeBSD partition marked as the active one (via fdisk) or is bteasy installed on the Jaz drive? On your original boot disk, bteasy requires _one_ of those two or it will refuse to transfer control. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sun Jul 13 22:03:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29246 for hackers-outgoing; Sun, 13 Jul 1997 22:03:02 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29241 for ; Sun, 13 Jul 1997 22:02:59 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA18892; Sun, 13 Jul 1997 22:58:35 -0600 (MDT) Date: Sun, 13 Jul 1997 22:58:35 -0600 (MDT) Message-Id: <199707140458.WAA18892@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Drew Derbyshire Cc: hackers@freebsd.org Subject: Re: access to SIO port freezes FreeBSD 2.2.1 In-Reply-To: <199707132321.TAA01158@pandora.hh.kew.com> References: <199707132321.TAA01158@pandora.hh.kew.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Due to a "little" accident with athena (why in hell I give myself > root password, I don't know, but it's another story anyway), I > needed to put the modems into pandora. So I disable the internal > dumb ports, move the FIFO UART's to COM1/COM2, and put the modems > in at COM3/COM4, IRQ 5 and regen the kernel, and system comes up > fine. You have both UART's sharing the same IRQ? This is *bad* news, and can cause all sorts of problems. Also, some 'internal' serial ports claim to allow themselves to be disabled, but in reality the electronics are still hooked up. Nate From owner-freebsd-hackers Sun Jul 13 22:17:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29865 for hackers-outgoing; Sun, 13 Jul 1997 22:17:05 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA29856 for ; Sun, 13 Jul 1997 22:17:00 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wndQU-0002iM-00; Sun, 13 Jul 1997 22:11:58 -0700 Date: Sun, 13 Jul 1997 22:11:57 -0700 (PDT) From: Tom Samplonius To: Michael Smith cc: Al Johnson , hackers@freebsd.org Subject: Re: What I consider and odd install In-Reply-To: <199707140430.OAA07478@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Michael Smith wrote: > Al Johnson stands accused of saying: > > > > No matter what I do I can't get the FreeBSD boot manager to give me the > > option of booting from the JAZ drive. I've gone thru and made sure it's > > BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB > > Seagate, 82h JAZ, 83h EZ135. > > The bootmangler (and many BIOSsen) only supports booting from the first > two drives. You may have better luck installing a different boot manager. > (eg. OS-BS) FreeBSD's booteasy can boot from the 2nd drive, at least on IDE systems. I just displays something like "F5 - Disk 2", and then you press F5 to display the boot selections for disk 2. Very neat. I think the problem is with the 2940 and the Jaz. The Jaz is a removable disk, and I recall special options in the Adaptec bios for bios support for various removable, and extra drive type stuff. > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > > Tom From owner-freebsd-hackers Sun Jul 13 22:31:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00550 for hackers-outgoing; Sun, 13 Jul 1997 22:31:33 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA00543 for ; Sun, 13 Jul 1997 22:31:30 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wndjB-0005Un-00; Sun, 13 Jul 1997 23:31:17 -0600 To: hcremean@vt.edu Subject: Re: upgrading XFree86 Cc: Chuck Robey , hackers@freebsd.org In-reply-to: Your message of "Sat, 12 Jul 1997 00:33:57 EDT." <19970712003357.51472@wakky.dyn.ml.org> References: <19970712003357.51472@wakky.dyn.ml.org> Date: Sun, 13 Jul 1997 23:31:17 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970712003357.51472@wakky.dyn.ml.org> Lee Cremeans writes: : Yes, it can; in fact, that's the default for the 3.3 tarballs. It does not : require you to start fresh (and AFAIK, Xfree never has). Just make sure that you save all the files from the 3.2.x release that you've touched. I got bit with one of my Xterminals because I didn't save the xdm config files that were overwritten when I upgraded to 3.3. I did it via making the sources (via the ports mechanism), so the binaries might be different. I'd also save XF86Config out of paranoia. I've hand tweaked mine over the years to work on my old Solbourne (and 66MHz Sun) monitors, which isn't an install option in their cool install program, AFAICT. Warner From owner-freebsd-hackers Sun Jul 13 22:33:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA00673 for hackers-outgoing; Sun, 13 Jul 1997 22:33:14 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA00668 for ; Sun, 13 Jul 1997 22:33:11 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wndkU-0005VA-00; Sun, 13 Jul 1997 23:32:38 -0600 To: Jason Thorpe Subject: Re: Make World Explodes Cc: Peter Dufault , Shimon@i-connect.net (Simon Shapiro), hackers@freebsd.org In-reply-to: Your message of "Sat, 12 Jul 1997 10:34:34 PDT." <199707121734.KAA18014@lestat.nas.nasa.gov> References: <199707121734.KAA18014@lestat.nas.nasa.gov> Date: Sun, 13 Jul 1997 23:32:37 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707121734.KAA18014@lestat.nas.nasa.gov> Jason Thorpe writes: : > One of the truly great useful reasons for constructors/destructors. : : Bah... -Wuninitialized. I've found myself wanting it when I exit scope for an error after I've increased the spl... Warner From owner-freebsd-hackers Sun Jul 13 23:15:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02505 for hackers-outgoing; Sun, 13 Jul 1997 23:15:17 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02495 for ; Sun, 13 Jul 1997 23:15:11 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA08466; Mon, 14 Jul 1997 15:44:00 +0930 (CST) From: Michael Smith Message-Id: <199707140614.PAA08466@genesis.atrad.adelaide.edu.au> Subject: Re: What I consider and odd install In-Reply-To: from Tom Samplonius at "Jul 13, 97 10:11:57 pm" To: tom@sdf.com (Tom Samplonius) Date: Mon, 14 Jul 1997 15:44:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Al.Johnson@AJC.State.Net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius stands accused of saying: > >>> No matter what I do I can't get the FreeBSD boot manager to give me the >>> option of booting from the JAZ drive. I've gone thru and made sure it's >>> BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB >>> Seagate, 82h JAZ, 83h EZ135. >> >> The bootmangler (and many BIOSsen) only supports booting from the first >> two drives. You may have better luck installing a different boot manager. >> (eg. OS-BS) > > FreeBSD's booteasy can boot from the 2nd drive, at least on IDE systems. Note that the disk in question is the _third_ drive, ie 0x82. > I just displays something like "F5 - Disk 2", and then you press F5 to > display the boot selections for disk 2. Very neat. Yes. Unfortunately it uses the LSB of the BIOS disk count to swap between 1- and 2-disk mode. With 3 disks you can only boot from the 1st. > I think the problem is with the 2940 and the Jaz. The Jaz is a > removable disk, and I recall special options in the Adaptec bios for bios > support for various removable, and extra drive type stuff. The default 2940 configuration treats removables as fixed disks for booting only. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jul 13 23:25:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02899 for hackers-outgoing; Sun, 13 Jul 1997 23:25:28 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA02891 for ; Sun, 13 Jul 1997 23:25:26 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wneUe-0004RY-00; Sun, 13 Jul 1997 23:20:20 -0700 Date: Sun, 13 Jul 1997 23:20:17 -0700 (PDT) From: Tom Samplonius To: Michael Smith cc: Al.Johnson@AJC.State.Net, hackers@freebsd.org Subject: Re: What I consider and odd install In-Reply-To: <199707140614.PAA08466@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Michael Smith wrote: > > I think the problem is with the 2940 and the Jaz. The Jaz is a > > removable disk, and I recall special options in the Adaptec bios for bios > > support for various removable, and extra drive type stuff. > > The default 2940 configuration treats removables as fixed disks for > booting only. How about enabling BIOS support for more drives? Boot easy should see the other drives, if the bios does, unless there is a design limitation in boot easy. > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > > Tom From owner-freebsd-hackers Sun Jul 13 23:29:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03064 for hackers-outgoing; Sun, 13 Jul 1997 23:29:43 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03058 for ; Sun, 13 Jul 1997 23:29:40 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA08552; Mon, 14 Jul 1997 15:59:24 +0930 (CST) From: Michael Smith Message-Id: <199707140629.PAA08552@genesis.atrad.adelaide.edu.au> Subject: Re: What I consider and odd install In-Reply-To: from Tom Samplonius at "Jul 13, 97 11:20:17 pm" To: tom@sdf.com (Tom Samplonius) Date: Mon, 14 Jul 1997 15:59:23 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Al.Johnson@AJC.State.Net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius stands accused of saying: > > How about enabling BIOS support for more drives? Boot easy should see > the other drives, if the bios does, unless there is a design limitation in > boot easy. Booteasy, especially 1.7, is very old. It dates from the days when most biossen only supported two drives (as previously mentioned). There is no correct way of discovering whether the BIOS supports more drives. You're invited to find the booteasy source code and improve on it. 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jul 13 23:38:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03654 for hackers-outgoing; Sun, 13 Jul 1997 23:38:13 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03647 for ; Sun, 13 Jul 1997 23:38:10 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wneh1-0005HF-00; Sun, 13 Jul 1997 23:33:07 -0700 Date: Sun, 13 Jul 1997 23:33:06 -0700 (PDT) From: Tom Samplonius To: Michael Smith cc: Al.Johnson@AJC.State.Net, hackers@freebsd.org Subject: Re: What I consider and odd install In-Reply-To: <199707140629.PAA08552@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Michael Smith wrote: > Tom Samplonius stands accused of saying: > > > > How about enabling BIOS support for more drives? Boot easy should see > > the other drives, if the bios does, unless there is a design limitation in > > boot easy. > > Booteasy, especially 1.7, is very old. It dates from the days when > most biossen only supported two drives (as previously mentioned). > > There is no correct way of discovering whether the BIOS supports more > drives. > > You're invited to find the booteasy source code and improve on it. 8) Strange... booteasy was a rather new addition to FreeBSD (2.0, 2.05, or something... well that is "somewhat new"). Adaptec 2940 has had the "bios support for more than two drives" option for a long time. Does os-bs really work in this case (ie. when booteasy doesn't)? > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > > Tom From owner-freebsd-hackers Sun Jul 13 23:43:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03934 for hackers-outgoing; Sun, 13 Jul 1997 23:43:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03927 for ; Sun, 13 Jul 1997 23:43:23 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA08765; Mon, 14 Jul 1997 16:13:00 +0930 (CST) From: Michael Smith Message-Id: <199707140643.QAA08765@genesis.atrad.adelaide.edu.au> Subject: Re: What I consider and odd install In-Reply-To: from Tom Samplonius at "Jul 13, 97 11:33:06 pm" To: tom@sdf.com (Tom Samplonius) Date: Mon, 14 Jul 1997 16:13:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Al.Johnson@AJC.State.Net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius stands accused of saying: > > Strange... booteasy was a rather new addition to FreeBSD (2.0, 2.05, or > something... well that is "somewhat new"). Adaptec 2940 has had the > "bios support for more than two drives" option for a long time. I recall using booteasy on a DOS/Xenix 2.1.1 system. 8) > Does os-bs really work in this case (ie. when booteasy doesn't)? OS-BS is generally much better. I has the downside that it has to be configured, unlike booteasy which autodetects. > Tom -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jul 14 00:51:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06530 for hackers-outgoing; Mon, 14 Jul 1997 00:51:15 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA06522 for ; Mon, 14 Jul 1997 00:51:11 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA19195 for hackers@FreeBSD.ORG; Mon, 14 Jul 1997 09:51:08 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA00462; Mon, 14 Jul 1997 09:41:47 +0200 (MET DST) Message-ID: <19970714094147.SE11660@uriah.heep.sax.de> Date: Mon, 14 Jul 1997 09:41:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: aha1522 ?? References: <199707131900.MAA01735@rah.star-gate.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707131900.MAA01735@rah.star-gate.com>; from Amancio Hasty on Jul 13, 1997 12:00:13 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Amancio Hasty wrote: > Do we have an aha1522 expert? Many. :-) > > I have a strong suspicion that the FreeBSD AHA1522 driver is a little > > flaky. This is an understatement. I would call it ``basically unusable''. It suffers extensive bit-rot. I have removed it from the list of supported devices in the release notes. This should probably be merged into the 2.2 branch as well. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 14 00:54:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06609 for hackers-outgoing; Mon, 14 Jul 1997 00:54:24 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA06430; Mon, 14 Jul 1997 00:49:49 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id IAA10143; Mon, 14 Jul 1997 08:44:35 +0200 From: Luigi Rizzo Message-Id: <199707140644.IAA10143@labinfo.iet.unipi.it> Subject: snd driver attach routine To: hasty@rah.star-gate.com (Amancio Hasty) Date: Mon, 14 Jul 1997 08:44:35 +0200 (MET DST) Cc: rhh@ct.picker.com, multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199707140136.SAA00270@rah.star-gate.com> from "Amancio Hasty" at Jul 13, 97 06:35:45 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [I am Cc'ing this to hackers since there someone might have some useful suggestion] Problem: what should be the return type of *attach() routines ? > 2. "< long attach_awe_obsolete(long mem_start, struct address_info *hw_config); > > void attach_awe_obsolete(struct address_info *hw_config);" > > That is to sort out long vs. void for attach routines. Personally, > I think the return type should be "long" but lets see > what Luigi had in mind. I have checked /sys/i386/isa/isa.c -- while the attach routine has return type "int", it is not tested for failure, which means that it better not fail :) . Note that there is no consistency at all about this in the various driver. Many (including sio.c and others that I wrote, e.g. asc.c) can fail in the attach routine, but this might mean nothing, just that I copied from a bad example (and in the case of sio.c, the attach routine is also called from another part of the driver). The drivers in /sys/pci all return void for the attach routine. So I'd go for the following: - make "void" the return type of all soundcard attach routines; - move all actions which might fail (e.g. allocate memory ?) to the probe routine; - do not invoke the probe routine again during the attach. Does this sound (er... look ?:) reasonable ? Should we also fix the existing isa drivers accordingly, if possible ? Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Jul 14 00:57:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA06751 for hackers-outgoing; Mon, 14 Jul 1997 00:57:27 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA06741 for ; Mon, 14 Jul 1997 00:57:19 -0700 (PDT) Received: from rain (portC7.bonn-online.com [195.52.214.78]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id JAA02989; Mon, 14 Jul 1997 09:56:17 +0200 Message-ID: <33C9DBA5.41C67EA6@bonn-online.com> Date: Mon, 14 Jul 1997 09:56:21 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> <19970711211440.BV38545@uriah.heep.sax.de> <33C90F7A.41C67EA6@bonn-online.com> <19970713195353.AD25187@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Sebastian Lederer wrote: > > > What would be the disadvantages if we used > > /etc/local by default (on machines in an nfs-less environment) ? > > The ports paradigm is to not install/modify anything outside ${PREFIX} > (except indirectly, e.g. by running ldconfig -m). > > The number of NFS-exported /usr/local's probably makes 5 % of the > installed base (wild guess). Just since it applies to you doesn't > mean it's a very general configuration. So what do you mean: That FreeBSD is rarely used as an NFS server for other FreeBSD machines, or that /usr/local is rarely used for sharing common binaries, libraries, includes, etc. among several FreeBSD machines via NFS ? Or, to put it another way, which directory should be used for NFS exporting, if not /usr/local? Maybe /opt? :-) -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Mon Jul 14 02:16:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA10050 for hackers-outgoing; Mon, 14 Jul 1997 02:16:00 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA10042 for ; Mon, 14 Jul 1997 02:15:55 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA09440; Mon, 14 Jul 1997 18:45:28 +0930 (CST) From: Michael Smith Message-Id: <199707140915.SAA09440@genesis.atrad.adelaide.edu.au> Subject: Re: IPX routing? In-Reply-To: <199707131647.SAA28393@zibbi.mikom.csir.co.za> from John Hay at "Jul 13, 97 06:47:59 pm" To: jhay@mikom.csir.co.za (John Hay) Date: Mon, 14 Jul 1997 18:45:28 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Hay stands accused of saying: > > > > Is there a document anywhere which describes the delicacies of setting > > up a FreeBSD box as an IPX router? > > Nope, except maybe in the mail archives where I have helped a few people > to get it working. There has been someone who promissed to write it up > and get into the handbook, but it hasn't happened yet. Ah. > At the moment the code in FreeBSD only do Ethernet_II framing, so > you will have use that on the nets that connects to the FreeBSD box. Ok. That would have been more or less impossible. 8( > I do have code that do the Novel 802.3 protocol, but it only works > on the ed0 type cards because I use link1 in ifconfig to set it > and most other cards use that for something else like switching > 10BT on/off. Erk. Do I take it then that it's not possible to do the 802.[23] protocols as well as Ethernet_II simultaneously on the same interface? > John Hay -- John.Hay@mikom.csir.co.za -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jul 14 02:44:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA10970 for hackers-outgoing; Mon, 14 Jul 1997 02:44:21 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA10963 for ; Mon, 14 Jul 1997 02:44:15 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id LAA13223; Mon, 14 Jul 1997 11:43:25 +0200 (SAT) From: John Hay Message-Id: <199707140943.LAA13223@zibbi.mikom.csir.co.za> Subject: Re: IPX routing? In-Reply-To: <199707140915.SAA09440@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jul 14, 97 06:45:28 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 14 Jul 1997 11:43:25 +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 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > At the moment the code in FreeBSD only do Ethernet_II framing, so > > you will have use that on the nets that connects to the FreeBSD box. > > Ok. That would have been more or less impossible. 8( Why? I don't know of any clients that can't do Ethernet_II framing. > > > I do have code that do the Novel 802.3 protocol, but it only works > > on the ed0 type cards because I use link1 in ifconfig to set it > > and most other cards use that for something else like switching > > 10BT on/off. > > Erk. Do I take it then that it's not possible to do the 802.[23] protocols > as well as Ethernet_II simultaneously on the same interface? It isn't technically impossible to do it. We can probably add code to FreeBSD to do it. The way to do it is like Netware servers to make each frame a seperate subnet. It is a waste on a big network though, because all your ipx broadcasts will have to be done once for each frame type on an interface. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Mon Jul 14 02:50:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA11186 for hackers-outgoing; Mon, 14 Jul 1997 02:50:24 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11181 for ; Mon, 14 Jul 1997 02:50:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA09576; Mon, 14 Jul 1997 19:19:00 +0930 (CST) From: Michael Smith Message-Id: <199707140949.TAA09576@genesis.atrad.adelaide.edu.au> Subject: Re: IPX routing? In-Reply-To: <199707140943.LAA13223@zibbi.mikom.csir.co.za> from John Hay at "Jul 14, 97 11:43:25 am" To: jhay@mikom.csir.co.za (John Hay) Date: Mon, 14 Jul 1997 19:19:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Hay stands accused of saying: > > > > > At the moment the code in FreeBSD only do Ethernet_II framing, so > > > you will have use that on the nets that connects to the FreeBSD box. > > > > Ok. That would have been more or less impossible. 8( > > Why? I don't know of any clients that can't do Ethernet_II framing. Well, when I asked why half of their workstations used 802.2 and the other half used 802.3, they complained that it was "too hard" to have them all work the same. Getting them to move all of them to Ethernet_II would, I think, have been difficult without a Very Good Argument. If you have one, I'm all ears of course 8) > It isn't technically impossible to do it. We can probably add code to > FreeBSD to do it. The way to do it is like Netware servers to make each > frame a seperate subnet. It is a waste on a big network though, because > all your ipx broadcasts will have to be done once for each frame type on > an interface. Ok, so it's not that there's some hardware evil involved in the different frame types. Understood. I would say from my experience it would be a Very Good Thing, actually 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jul 14 03:15:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA11946 for hackers-outgoing; Mon, 14 Jul 1997 03:15:08 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA11940 for ; Mon, 14 Jul 1997 03:15:04 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Mon, 14 Jul 1997 6:13:57 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA07392; Mon, 14 Jul 97 06:13:55 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id GAA06583; Mon, 14 Jul 1997 06:11:53 -0400 Message-Id: <19970714061152.52336@ct.picker.com> Date: Mon, 14 Jul 1997 06:11:52 -0400 From: Randall Hopper To: David Dawes Cc: FreeBSD-Hackers Subject: Re: upgrading XFree86 References: <19970713114946.61308@ct.picker.com> <19970714115351.32520@rf900.physics.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <19970714115351.32520@rf900.physics.usyd.edu.au>; from David Dawes on Mon, Jul 14, 1997 at 11:53:51AM +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David Dawes: |On Sun, Jul 13, 1997 at 11:49:46AM -0400, Randall Hopper wrote: |>I've never untarring on top of an existing dist because: 1) some XFree |>alphas I believe have mentioned, don't do that -- it won't work, and 2) if | |Did they? No XFree86 alphas were ever made available to the public, Sorry, had alpha on the brain. I meant to say beta. |and all of the public releases could be installed in this way (that's |how I always install them). The only caveat is that the provided |preinst.sh script should be run first. There has been the odd case of |a file being replaced with a directory of the same name, and the provided |script would remove such files first. This may have been what I was remembering, or it could be one of the 3.1.1 betas didn't have a preinst.sh. Anyway, it'd still be nice to be able to just rm -r and install the new one. Randall From owner-freebsd-hackers Mon Jul 14 03:52:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA13481 for hackers-outgoing; Mon, 14 Jul 1997 03:52:49 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA13457; Mon, 14 Jul 1997 03:52:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id UAA02952; Mon, 14 Jul 1997 20:46:14 +1000 Date: Mon, 14 Jul 1997 20:46:14 +1000 From: Bruce Evans Message-Id: <199707141046.UAA02952@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, luigi@labinfo.iet.unipi.it Subject: Re: snd driver attach routine Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, rhh@ct.picker.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Problem: what should be the return type of *attach() routines ? Perhaps it should be void to match reality, but it currently must be int for isa drivers to match the prototype in `struct isa_driver'. >The drivers in /sys/pci all return void for the attach routine. They have to, to match the prototype in `strcuct pci_driver'. >- move all actions which might fail (e.g. allocate memory ?) to the > probe routine; Impossible, e.g. since probe routines shouldn't allocate memory. Bruce From owner-freebsd-hackers Mon Jul 14 04:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14459 for hackers-outgoing; Mon, 14 Jul 1997 04:16:39 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14452 for ; Mon, 14 Jul 1997 04:16:35 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id MAA11322; Mon, 14 Jul 1997 12:15:45 +0100 (BST) Date: Mon, 14 Jul 1997 12:15:44 +0100 (BST) From: Stephen Roome To: BRiGHTMN cc: Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: The Linux emulator & weird Linux mmap semantics In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, BRiGHTMN wrote: > > I've been messing about with the Linux emulator, to add support for the kinds > > of manipulation involving mmaping sound devices that the OSS sound drivers > > support. A test program compiled natively works fine, but after hacking away > > at the Linux emulator to get it to recognize the various ioctls that OSS > > supports (get caps, mmaping, getospace) I am not getting any joy. The linux > > app (yes, it is quake if you must know) does not produce any sound, but thinks > > that it's doing fine. Has anyone else come across this? > > someone told me they were able to get sound in quake already (OSS), but i > haven't been able to do it. if you are successful that would be great. I think that someone (in the core team?) did it with an AWE 32/64, I'm sure others have but I've not yet got my AWE 64 going yet. Besides, last time I tried to use OSS my computer started crashing a lot, but then I had a really cheap CS4232 (eh?) or something that couldn't even emulate 20% of a soundblaster. I think you really just need the exact right card, nothing else ever works great - my one great gripe with FreeBSD. Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-hackers Mon Jul 14 05:23:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17319 for hackers-outgoing; Mon, 14 Jul 1997 05:23:53 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA17308 for ; Mon, 14 Jul 1997 05:23:47 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id IAA04038; Thu, 26 Jun 1997 08:24:03 GMT Date: Thu, 26 Jun 1997 08:24:03 +0000 (GMT) From: BRiGHTMN To: Drew Derbyshire cc: hackers@FreeBSD.ORG Subject: Re: access to SIO port freezes FreeBSD 2.2.1 In-Reply-To: <199707132321.TAA01158@pandora.hh.kew.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk a) conflicts with network cards or soundcard would be my guess, (IRQ) b) remove the modems and make SURE that on board serials are disabled c) maybe the modems are conflicting with some device's port address? good luck Alfred perlsta@sunyit.edu > Here's a wacky one ... > > I have two systems both running FreeBSD 2.2.1 with four serial ports > enabled. > > athena is a 386/33 with 16M, ISA bus, two dumb serial ports, > two internal modems with FIFO UARTS. Modems are COM3/COM4, > IRQ 5 and 9; one is IBM/Reveal v.32, other is Zoom v.34 > > pandora is a 386/66 with VLB for the display, but mostly ISA > with two dumb serial ports and two 16650x uarts. FIFO UARTs are > COM3/COM4, IRQ 9 and 5. > > Due to a "little" accident with athena (why in hell I give myself > root password, I don't know, but it's another story anyway), I > needed to put the modems into pandora. So I disable the internal > dumb ports, move the FIFO UART's to COM1/COM2, and put the modems > in at COM3/COM4, IRQ 5 and regen the kernel, and system comes up > fine. > > Then I enable ttyd2 and ttyd3, and HUP init, and it hangs. Solid. > Can't even get console to switch screens or reboot. Works out that > ttyd3 works, but not ttyd2 (v.32). Windows 95 sees it, FreeBSD > sees it, but locks solid when opening. Same two modems worked > great 24 hours before on pandora's little sister. > > Suggestions as to where to look? From owner-freebsd-hackers Mon Jul 14 05:37:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18281 for hackers-outgoing; Mon, 14 Jul 1997 05:37:07 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18257 for ; Mon, 14 Jul 1997 05:37:02 -0700 (PDT) Received: from sonata (sonata.hh.kew.com [192.195.203.135]) by pandora.hh.kew.com (8.8.5/8.8.5) with SMTP id IAA03019; Mon, 14 Jul 1997 08:36:55 -0400 (EDT) Message-ID: <33CA1D7B.3432@kew.com> Date: Mon, 14 Jul 1997 08:37:15 -0400 From: Drew Derbyshire Reply-To: ahd@kew.com Organization: Kendra Electronic Wonderworks X-Mailer: Mozilla 3.01GoldC-MOENE (WinNT; U) MIME-Version: 1.0 To: Nate Williams CC: hackers@freebsd.org Subject: Re: access to SIO port freezes FreeBSD 2.2.1 References: <199707132321.TAA01158@pandora.hh.kew.com> <199707140458.WAA18892@rocky.mt.sri.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams wrote: > > > So I disable the internal > > dumb ports, move the FIFO UART's to COM1/COM2, and put the modems > > in at COM3/COM4, IRQ 5/9 and regen the kernel, and system comes up ^^ (corrected) > > fine. > > You have both UART's sharing the same IRQ? No. I missed the second IRQ description above (it was correct in the now deleted first paragraph). I corrected _both_ values in the kernel, not changing the (working) physical configuration of the modems. Let me clarify the final configuration: Jul 13 15:17:30 pandora /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 13 15:17:30 pandora /kernel: sio0: type 16550A Jul 13 15:17:30 pandora /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 13 15:17:30 pandora /kernel: sio1: type 16550A Jul 13 15:17:30 pandora /kernel: sio2 at 0x3e8-0x3ef irq 5 on isa Jul 13 15:17:31 pandora /kernel: sio2: type 16550A Jul 13 15:17:31 pandora /kernel: sio3 at 0x2e8-0x2ef irq 9 on isa Jul 13 15:17:31 pandora /kernel: sio3: type 16550A > Also, some 'internal' serial ports claim to allow themselves to be > disabled, but in reality the electronics are still hooked up. This would not be the problem in this case, because the internal ports were COM1/COM2, and don't support 0x3e8-0x3ef irq 5. -- Internet: ahd@kew.com Voice: 617-279-9810 Support Little League Roller Ball! From owner-freebsd-hackers Mon Jul 14 06:30:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21314 for hackers-outgoing; Mon, 14 Jul 1997 06:30:54 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA21307 for ; Mon, 14 Jul 1997 06:30:50 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA22700 for hackers@FreeBSD.ORG; Mon, 14 Jul 1997 15:30:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA00996; Mon, 14 Jul 1997 15:14:07 +0200 (MET DST) Message-ID: <19970714151407.FQ00024@uriah.heep.sax.de> Date: Mon, 14 Jul 1997 15:14:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: What I consider and odd install References: <199707140430.OAA07478@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Samplonius on Jul 13, 1997 22:11:57 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Samplonius wrote: > > The bootmangler (and many BIOSsen) only supports booting from the first > > two drives. > FreeBSD's booteasy can boot from the 2nd drive, ... That's what Mike wrote. However, it treats any system with != 2 drives as being a system with 1 drive. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 14 06:54:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22351 for hackers-outgoing; Mon, 14 Jul 1997 06:54:20 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA22343 for ; Mon, 14 Jul 1997 06:54:15 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA22840 for freebsd-hackers@FreeBSD.ORG; Mon, 14 Jul 1997 15:53:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id PAA01251; Mon, 14 Jul 1997 15:38:05 +0200 (MET DST) Message-ID: <19970714153805.EE26390@uriah.heep.sax.de> Date: Mon, 14 Jul 1997 15:38:05 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> <19970711211440.BV38545@uriah.heep.sax.de> <33C90F7A.41C67EA6@bonn-online.com> <19970713195353.AD25187@uriah.heep.sax.de> <33C9DBA5.41C67EA6@bonn-online.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <33C9DBA5.41C67EA6@bonn-online.com>; from Sebastian Lederer on Jul 14, 1997 09:56:21 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Sebastian Lederer wrote: > So what do you mean: That FreeBSD is rarely used as an > NFS server for other FreeBSD machines, ... If you translate `rarely' into `not for most of the installations', so: yes. I suspect that most of the installations serve standalone machines, maybe sitting in a network of other machines, but often not with other FreeBSD machines. > Or, to put it another way, which directory should be used for > NFS exporting, if not /usr/local? Maybe /opt? :-) /home? /usr/X11R6? /usr/share? There are too many possibilites to make `generic' assumptions. I agree however that the standard install might ask whether it should move /usr/local/etc (and/or /usr/X11R6/etc) out to /etc/local (or /etc/X11R6). But first i'm waiting for Jordan's new `setup' tool (projected new name for the sysinstall successor). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 14 07:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA23427 for hackers-outgoing; Mon, 14 Jul 1997 07:16:49 -0700 (PDT) Received: from iq.org (profane.iq.org [203.4.184.222]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA23413 for ; Mon, 14 Jul 1997 07:16:43 -0700 (PDT) From: proff@iq.org Received: (qmail 5384 invoked by uid 110); 13 Jul 1997 18:04:24 -0000 Date: 13 Jul 1997 18:04:24 -0000 Message-ID: <19970713180424.5383.qmail@iq.org> To: hackers@freebsd.org Subject: sunworld Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Seen in sunword] Date: Tue Apr 22 17:19:54 PDT 1997 Sun, please give us a break. Java is MAYBE, MAYBE on a good day an alpha quality language. You've built an industry out of nothing. As a result, your OS has suffered. Our SPARC/Solaris systems are being replaced ENTIRELY by DEC Digital Unix and Intel/FreeBSD. It is unfortunate but a reality. Cheers, Julian. From owner-freebsd-hackers Mon Jul 14 07:18:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA23488 for hackers-outgoing; Mon, 14 Jul 1997 07:18:00 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA23472 for ; Mon, 14 Jul 1997 07:17:42 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA10835; Mon, 14 Jul 1997 15:12:15 +0200 From: Luigi Rizzo Message-Id: <199707141312.PAA10835@labinfo.iet.unipi.it> Subject: Re: snd driver attach routine To: bde@zeta.org.au (Bruce Evans) Date: Mon, 14 Jul 1997 15:12:14 +0200 (MET DST) Cc: hackers@freebsd.org In-Reply-To: <199707141156.VAA05457@godzilla.zeta.org.au> from "Bruce Evans" at Jul 14, 97 09:56:12 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >The reality (i.e. isa and pci) suggest that the attach routine should > >not report failures to the calling routine. > > Failure is possible, so it should be reported and tested for. This is > more important for LKM'ed drivers. Even malloc() failures are not > unlikely after the the system has been running for a while. this is an issue for the core team I guess... as well as defining a standard for reporting errors in the attach routine. The changes would have to go in i386/isa/isa.c and pci/pci.c and perhaps in other places as well. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Jul 14 08:44:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27689 for hackers-outgoing; Mon, 14 Jul 1997 08:44:15 -0700 (PDT) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27683 for ; Mon, 14 Jul 1997 08:44:11 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id QAA27908; Mon, 14 Jul 1997 16:42:56 +0100 (BST) Message-ID: <19970714164256.29024@pavilion.net> Date: Mon, 14 Jul 1997 16:42:56 +0100 From: Josef Karthauser To: Murali Rangarajan Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: help on cgi... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Murali Rangarajan on Sun, Jul 13, 1997 at 09:40:16AM -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Jul 13, 1997 at 09:40:16AM -0400, Murali Rangarajan wrote: > Hi, > I've installed apache as the http server on my machine running FreeBSD 2.2 > release. I'm unable to get the cgi scripts to work even though I think > I've set up the .conf files properly... ANy suggestions from guys who have > done it for their machines? Make sure that you've got something like: AllowOverride None Options ExecCGI FollowSymLinks in your access.conf file. Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Mon Jul 14 08:49:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27932 for hackers-outgoing; Mon, 14 Jul 1997 08:49:48 -0700 (PDT) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27927 for ; Mon, 14 Jul 1997 08:49:44 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id QAA28157; Mon, 14 Jul 1997 16:47:08 +0100 (BST) Message-ID: <19970714164708.28827@pavilion.net> Date: Mon, 14 Jul 1997 16:47:08 +0100 From: Josef Karthauser To: Stephen Roome Cc: BRiGHTMN , Stephen Hocking , hackers@FreeBSD.ORG Subject: =?iso-8859-1?Q?Things_that_=A3$=22$_me_off_about_fbsd?= References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Stephen Roome on Mon, Jul 14, 1997 at 12:15:44PM +0100 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Jul 14, 1997 at 12:15:44PM +0100, Stephen Roome wrote: > > I think you really just need the exact right card, nothing else ever > works great - my one great gripe with FreeBSD. > I've got none ;) (apart from crashing my machine this morning whilst trying to ls an msdos floppy which was busy having a file copied to it. Carnage!! Takes the entire fs mechanism down, i.e. mount hangs, umount hangs, aaarrrrgggghhh!) Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Mon Jul 14 09:29:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00305 for hackers-outgoing; Mon, 14 Jul 1997 09:29:43 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA00300 for ; Mon, 14 Jul 1997 09:29:38 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA01510; Mon, 14 Jul 1997 09:22:53 -0700 From: Terry Lambert Message-Id: <199707141622.JAA01510@phaeton.artisoft.com> Subject: Re: TCP bug in 2.2 To: julian@whistle.com (Julian Elischer) Date: Mon, 14 Jul 1997 09:22:53 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Jul 13, 97 01:39:45 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > tcp_extensions=NO > > Terry, I am aware of that ok? Sorry, thought it was one of the other Julian's... > And yes TCP exensions WAS (to our surprise) enabled on that machine. > We have since turned it off, however despite this it should be > IMPOSSIBLE to hang a socket in that way. I agree. However... did turning them off affect the hanging at all? The information would be useful in tracking down the real bug. Just a shot in the dark... > it was SOLARIS 2.5.1 > and it didn't happen consitently so it's a race condition of some sort. 2.5.1 thinks it supports T/TCP, right? Maybe it's 2.5.1's T/TCP? [ ... ] > but no matter WHAT OS, we should not have a code path that can get to > the state that a tcp session is totally hung, without a timer running > for it. Sorry; I didn't know what patches you did or didn't have. The timers were relatively new. What about the recent commits that you had to fix the Appletalk stuff for ...is it possible that they are the source of the problem? > > 1) You reboot a machine without shuttding down all Winsock > > clients. > The solaris machine was not rebooted. Well, there's a nice mising notification theory shot to hell... 8-). > > The timer is not started until the FIN is sent if SO_KEEPALIVE was > > specified by the client. It usually is. > > I'll check this but it still seems to be a bug to me > because the socket is in FIN_WAIT2 state and HAS BEEN CLOSED. Yep; sorry for the assumptions... hope you find it. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 14 09:45:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01045 for hackers-outgoing; Mon, 14 Jul 1997 09:45:39 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01033 for ; Mon, 14 Jul 1997 09:45:27 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id TAA15849; (8.8.3/zah/2.1) Mon, 14 Jul 1997 19:34:36 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id RAA04444; (8.6.11/zah/2.1) Mon, 14 Jul 1997 17:22:17 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id TAA26348; (8.6.9/zah/1.1) Mon, 14 Jul 1997 19:17:59 +0100 Received: from 194.44.146.14 (mac.ipri.kiev.ua [194.44.146.14]) by cki.ipri.kiev.ua (8.7.6/8.7.3) with SMTP id SAA00454; Mon, 14 Jul 1997 18:26:51 +0300 (EET DST) Message-ID: <33CA3780.389F@cki.ipri.kiev.ua> Date: Mon, 14 Jul 1997 17:28:04 +0300 From: Ruslan Shevchenko Reply-To: rssh@cki.ipri.kiev.ua Organization: IPRI X-Mailer: Mozilla 3.01Gold (Macintosh; I; 68K) MIME-Version: 1.0 To: Terry Lambert CC: Gary.Jennejohn@munich.netsurf.de, freebsd-hackers@freefall.FreeBSD.org Subject: Re: /etc/init.d/ References: <199707112126.OAA25717@phaeton.artisoft.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > I run a SVR4 box here at home, and the only useful run-level options > > (IMHO) it offers involve NFS services. When I need NFS I just > > switch to that run-level and all the services are started. When I'm > > done using NFS I just switch to a lower level and the NFS stuff is > > removed. But a box without networking is pretty useless and I've never > > run the box in that configuration. > > Most of the advocates of run states (not levels) agree with you. > > However, say I have a laptop; it can be: > > o Docked at the office and hooked into a net > o Undocked at the office in a conference room > and hooked into a net via a 4Mbit IR link > at the conference table > o Undocked on a plane with a dialup link > o Undocked anywhere with a cellular link > o Undocked anywhere with a cellular link, but > out of cell range > o Undocked anywhere with no link > o Docked at home and hooked into a *different* net > o Docked at home with a dialup connection > o Docked at home and not hooked into a net > > I want the boot run state to assess the connectivity options, > and pick the run state it ends up in based on the current > hardware configuration. > > I also want to be able to "hot" undock/dock, and automatically > change between the appropriate states, as needed. > > Windows95 assumes you shut the machine down. You must also > manually pick one of several "Hardware Profiles" (which you > can do at boot time). > > Even if the states are not automatically configured by docking > state/PCMCIA card state changes, in order to do what Windows95 > can do, several client and service configuration details normally > handled globally in a single rc file in traditional BSD need to > be handled otherwise. > > For example, should I mount the NFS server with the shared copy > of WordPerfect 4.2 for IBCS2? > > There is also the issue of service anonymity: > > 1) I'm docked at the office, and have created a > presentation using a presentation graphics package > with a floating network license, run from an office > server. > 2) I undock at the office to go to a meeting in a > conference room > 3) I arrive at the conference room and am IR linked > 4) I leave the conference room and get in the car > 5) I enter my home and redock at the home dock > 6) I undock and get back in my car > 7) I drive to the airport > 8) While waiting for my flight, I check on my stocks > via a cellular link > 9) I get on the plane, where if I were to use the > cellular link, I would get in trouble because > the airlines can't make as much money off me (planes > would fall out of the sky over any metropolitan area > if the avionics claims were true). > 10) Halfway through my flight from LA to New York, I > user the 28.8 modem built into my ethernet PCMCIA > card to connect to the in flight phone and check > the stock close price. > 11) I arrive at my hotel and use the ISDN card to > connect to the hotel's digital PBX, and check > my corporate mail. > 12) The next morning I check my corporate mail and > the opening value of my stock. > 13) I drive the rent-a-car to the corporate offices, > go into the conference room, and get an IR link and > mount the local server where the same presentation > software is installed, obtain a local license, and > make my presentation to the board. > Yes. The concept of init states is very good. for example, my currently problem: At home: 1. booting without net 2. X 3. Connect with my provider via phone. AT work: (one of mashines) 1. boot without net 1.1 Start X 2. Check, if router is live 3. Check for living of NFS and rumba mashines. start rumba and NFS (Of course, I can do it all from amd, but I must start it *after* the net is up) And in all levels, I can work few hours (debuging a C programm, for example) From owner-freebsd-hackers Mon Jul 14 10:51:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04711 for hackers-outgoing; Mon, 14 Jul 1997 10:51:42 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04706; Mon, 14 Jul 1997 10:51:35 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id LAA02683; Mon, 14 Jul 1997 11:51:33 -0600 (MDT) Message-Id: <199707141751.LAA02683@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: smp@freebsd.org cc: hackers@freebsd.org Subject: interrupt latency Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 11:51:32 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Can anyone recommend a test suite/methodology for evaluating interrupt latency? I have some ideas for improving the (currently poor) int response of the SMP kernel, but need a way to determine if I am actually bettering things. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 11:38:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06839 for hackers-outgoing; Mon, 14 Jul 1997 11:38:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA06834 for ; Mon, 14 Jul 1997 11:38:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01726; Mon, 14 Jul 1997 11:30:15 -0700 From: Terry Lambert Message-Id: <199707141830.LAA01726@phaeton.artisoft.com> Subject: Re: help on cgi... To: joe@pavilion.net (Josef Karthauser) Date: Mon, 14 Jul 1997 11:30:15 -0700 (MST) Cc: muralir@george.rutgers.edu, freebsd-hackers@FreeBSD.ORG In-Reply-To: <19970714164256.29024@pavilion.net> from "Josef Karthauser" at Jul 14, 97 04:42:56 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi, > > I've installed apache as the http server on my machine running FreeBSD 2.2 > > release. I'm unable to get the cgi scripts to work even though I think > > I've set up the .conf files properly... ANy suggestions from guys who have > > done it for their machines? > > Make sure that you've got something like: > > This directory should be wherever the cgi-bin directory was installed. > AllowOverride None > Options ExecCGI FollowSymLinks > > > in your access.conf file. In your srm.conf file, you should also have: ScriptAlias /cgi-bin/ /data/httpd/cgi-bin Again, assuming this is where the cgi-bin directory was installed, and then you should reference your CGI's as:
In your documents. ...Assuming your CGI is named "foo" and you are using "post"; change to another name for another cgi (test-cgi is recommended, assuming you downloaded and built it) or "get" for the "get" method instead of the "post" method ("post" is recommended because it doesn't have the length limitations or URL exposure that "get" has). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 14 11:52:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07656 for hackers-outgoing; Mon, 14 Jul 1997 11:52:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07651 for ; Mon, 14 Jul 1997 11:52:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA01772; Mon, 14 Jul 1997 11:44:35 -0700 From: Terry Lambert Message-Id: <199707141844.LAA01772@phaeton.artisoft.com> Subject: Re: IPX routing? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Mon, 14 Jul 1997 11:44:35 -0700 (MST) Cc: jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199707140949.TAA09576@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 14, 97 07:19:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Why? I don't know of any clients that can't do Ethernet_II framing. > > Well, when I asked why half of their workstations used 802.2 and the > other half used 802.3, they complained that it was "too hard" to have > them all work the same. Getting them to move all of them to > Ethernet_II would, I think, have been difficult without a Very Good > Argument. If you have one, I'm all ears of course 8) One good argument is that the 802.3 framining use incomplete packet headers, and is adulterated. The reason it works is because the IPX packet type uses an ID which is an invalid length in a correctly encoded packet, and you can make an exception in recognition on that basis. In reality, IPX on 802.3 is not correctly encapsulated according to the 802.3 specification. How's that? 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 14 12:17:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08867 for hackers-outgoing; Mon, 14 Jul 1997 12:17:29 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08860; Mon, 14 Jul 1997 12:17:10 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id NAA00523; Mon, 14 Jul 1997 13:16:06 -0600 (MDT) Message-Id: <199707141916.NAA00523@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Luigi Rizzo cc: smp@freebsd.org, hackers@freebsd.org Subject: Re: interrupt latency In-reply-to: Your message of "Mon, 14 Jul 1997 19:33:51 +0200." <199707141733.TAA11310@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 13:16:06 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > what are the starting and ending event that you are looking for ? > > start: hw_irq, handler (glue code) called ? > end: handler called, driver called ? thats a good question. the problem: in our SMP system an INT may be sent to a CPU that can't enter the kernel because another CPU is currently inside the kernel. this causes a long delay between the time the INT tickels the hardware and the time the ISR actually runs. --- So I guess the 2 points in time are the actual instance of hardware INT and the time the ISR completes. The closest the software can get to determining the start point would be on entry to _XintrNN (isa/apic_vector.s) A convenient stop point would be immediately after the lock is acquired (ie, after GET_MPLOCK in _XintrNN), the completion of the ISR code should be constant. But this hides the time between the actual firing of the hardware INT and the time a CPU accepts it. This could be fairly long if the "accepting CPU" is stuck behing the "giant lock", as hardware INTs are blocked during this time. The "ideal hardware solution" would be a card with a counter per INT source. each counter would be started by an INT, stopped & read via the ISR specific to that INT. I guess 2 cards, PCI & ISA, would be required for a complete solution. And MBs with onboard periphials such as disk and net would hide the most important INTs. WHich suggests an ISA card for the counters with an umbilical cord to attach to the APIC on the MB (a discrete chip with the natoma/triton chipset). --- Having said all this perhaps what I need are repeatable, disk/net IO intensive tests that benefit from latency improvements. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 12:46:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10130 for hackers-outgoing; Mon, 14 Jul 1997 12:46:13 -0700 (PDT) Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10122 for ; Mon, 14 Jul 1997 12:46:09 -0700 (PDT) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.8.5/8.8.5) id OAA07339 for hackers@freefall.freebsd.org; Mon, 14 Jul 1997 14:43:34 -0500 (CDT) Date: Mon, 14 Jul 1997 14:43:34 -0500 (CDT) From: "M. L. Dodson" Message-Id: <199707141943.OAA07339@beowulf.utmb.edu> To: hackers@freefall.freebsd.org Subject: Re: aha1522 ?? X-Sun-Charset: US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > As Amancio Hasty wrote: > > > Do we have an aha1522 expert? > > Many. :-) > > > > I have a strong suspicion that the FreeBSD AHA1522 driver is a little > > > flaky. > > This is an understatement. I would call it ``basically unusable''. > It suffers extensive bit-rot. I have removed it from the list of > supported devices in the release notes. > Whoops! Doesn't the 1522 use the same driver as the little minimal controller that comes with internal SCSI ZIP disks? I've been recommending that to people to "gently" introduce them to SCSI (for SCSI tape drives, for example). Is this status likely to remain this way? If so, I'll have to change my errant ways :) Bud Dodson > This should probably be merged into the 2.2 branch as well. > - -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > ------------------------------ > -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 From owner-freebsd-hackers Mon Jul 14 12:53:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10630 for hackers-outgoing; Mon, 14 Jul 1997 12:53:13 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10620; Mon, 14 Jul 1997 12:53:06 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA11489; Mon, 14 Jul 1997 20:49:00 +0200 From: Luigi Rizzo Message-Id: <199707141849.UAA11489@labinfo.iet.unipi.it> Subject: Re: interrupt latency To: smp@csn.net (Steve Passe) Date: Mon, 14 Jul 1997 20:48:59 +0200 (MET DST) Cc: smp@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199707141916.NAA00523@Ilsa.StevesCafe.com> from "Steve Passe" at Jul 14, 97 01:15:47 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi, > > > what are the starting and ending event that you are looking for ? > > > > start: hw_irq, handler (glue code) called ? > > end: handler called, driver called ? > > thats a good question. > > the problem: > > in our SMP system an INT may be sent to a CPU that can't enter the kernel > because another CPU is currently inside the kernel. this causes a long delay > between the time the INT tickels the hardware and the time the ISR actually > runs. I am not familiar at all with the SMP code or the apic, but using a hardware solution seems extremely complex. Since you are looking at solution to improve the int latency anyways, can you consider the following approach: Replace the "giant lock" with a couple of nested locks; the most external one would only allow the posting of the hardware intr to some cpu, but not the acquisition of the "giant lock" (i.e. the right to enter the kernel). The nested lock is what you currently call 'the giant lock'. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Mon Jul 14 13:02:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11108 for hackers-outgoing; Mon, 14 Jul 1997 13:02:50 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA11101; Mon, 14 Jul 1997 13:02:44 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id OAA00792; Mon, 14 Jul 1997 14:02:38 -0600 (MDT) Message-Id: <199707142002.OAA00792@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Luigi Rizzo cc: smp@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: interrupt latency In-reply-to: Your message of "Mon, 14 Jul 1997 20:48:59 +0200." <199707141849.UAA11489@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 14:02:37 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > I am not familiar at all with the SMP code or the apic, but using > a hardware solution seems extremely complex. Since you are looking > at solution to improve the int latency anyways, can you consider > the following approach: > > Replace the "giant lock" with a couple of nested locks; the most > external one would only allow the posting of the hardware intr to > some cpu, but not the acquisition of the "giant lock" (i.e. the > right to enter the kernel). The nested lock is what you currently > call 'the giant lock'. The APICs don't quite work that way. There is an IO APIC connected to the external INT sources, and a local APIC in each CPU. All the APICs communicate thru a private bus. The IO APIC sends the INT to whichever CPU it determines is the best candidate based on several algorithms. for more info on the APIC as currently used, see: http://www.freebsd.org/~fsmp/SMP/papers/apicsubsystem.txt -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 13:13:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11599 for hackers-outgoing; Mon, 14 Jul 1997 13:13:29 -0700 (PDT) Received: from iq.org (profane.iq.org [203.4.184.222]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA11586 for ; Mon, 14 Jul 1997 13:13:21 -0700 (PDT) From: proff@iq.org Received: (qmail 6625 invoked by uid 110); 14 Jul 1997 19:22:43 -0000 Message-ID: <19970714192243.6624.qmail@iq.org> Subject: Re: sunworld In-Reply-To: <9707141849.AA07859@pscwa.psca.com> from Manu Iyengar at "Jul 14, 97 11:49:06 am" To: m@pscwa.psca.com Date: Tue, 15 Jul 1997 05:22:42 +1000 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From iyengar@pscwa.psca.com Mon Jul 14 17:58:46 1997 > Delivered-To: proff@iq.org > Message-Id: <9707141849.AA07859@pscwa.psca.com> > In-Reply-To: <19970713180424.5383.qmail@iq.org> > X-Nextstep-Mailer: Mail 4.1mach (Enhance 2.0b5) > From: Manu Iyengar > Date: Mon, 14 Jul 97 11:49:06 -0700 > To: proff@iq.org > Subject: Re: sunworld > Reply-To: m@pscwa.psca.com > References: <19970713180424.5383.qmail@iq.org> > X-Wired: FreeBSD > Hmm, do you have reference information for this? I can't find this in the > SunWorld Online web pages...I looked under "Letters" for the April, May, June > & July issues.... > > -mi > > > >From the keyboard of proff@iq.org on 13 Jul 1997: > > [Seen in sunword] > > > > Date: Tue Apr 22 17:19:54 PDT 1997 > > Sun, please give us a break. Java is MAYBE, MAYBE on a good day an alpha > > quality language. You've built an industry out of nothing. As a result, > > your OS has suffered. Our SPARC/Solaris systems are being replaced ENTIRELY > > by DEC Digital Unix and Intel/FreeBSD. It is unfortunate but a reality. > > > > Cheers, > > Julian. > It's part of the Sun World Java survey. Cheers, Julian. From owner-freebsd-hackers Mon Jul 14 14:00:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA13972 for hackers-outgoing; Mon, 14 Jul 1997 14:00:15 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13930; Mon, 14 Jul 1997 14:00:01 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id VAA11169; Mon, 14 Jul 1997 21:43:10 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 14 Jul 1997 21:42:00 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199707141751.LAA02683@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 14 Jul 1997 21:38:11 +0100 To: Steve Passe From: Bob Bishop Subject: Re: interrupt latency Cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 18:51 +0100 14/7/97, Steve Passe wrote: >Hi, > >Can anyone recommend a test suite/methodology for evaluating interrupt >latency? >I have some ideas for improving the (currently poor) int response of the SMP >kernel, but need a way to determine if I am actually bettering things. A digital output port and an oscilloscope, logic analyser or something similar. Any other (ie non-hardware) method is just inviting confusion. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Mon Jul 14 14:05:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14242 for hackers-outgoing; Mon, 14 Jul 1997 14:05:51 -0700 (PDT) Received: from pscwa.psca.com (romulus.pscwa.psca.com [199.99.162.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA14235 for ; Mon, 14 Jul 1997 14:05:44 -0700 (PDT) Received: from vulcan by pscwa.psca.com (NX5.67f2/NX3.0M, PSCWA update 950701) id AA12106; Mon, 14 Jul 97 14:05:36 -0700 Message-Id: <9707142105.AA12106@pscwa.psca.com> Received: by vulcan.pscwa.psca.com (NX5.67g/NX3.0X) id AA01317; Mon, 14 Jul 97 14:05:35 -0700 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 4.1mach v148) In-Reply-To: <19970714192243.6624.qmail@iq.org> X-Nextstep-Mailer: Mail 4.1mach (Enhance 2.0b5) Received: by NeXT.Mailer (1.148) From: Manu Iyengar Date: Mon, 14 Jul 97 14:05:33 -0700 To: proff@iq.org Subject: Re: sunworld Cc: hackers@freebsd.org Reply-To: m@pscwa.psca.com References: <19970714192243.6624.qmail@iq.org> X-Wired: FreeBSD Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FYI, the URL is: http://www.sun.com/sunworldonline/swol-07-1997/swol-07-java.comments.html >From the keyboard of proff@iq.org on Tue, 15 Jul 1997: > > It's part of the Sun World Java survey. > > Cheers, > Julian. From owner-freebsd-hackers Mon Jul 14 14:14:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14675 for hackers-outgoing; Mon, 14 Jul 1997 14:14:59 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14653; Mon, 14 Jul 1997 14:14:36 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id PAA01080; Mon, 14 Jul 1997 15:13:49 -0600 (MDT) Message-Id: <199707142113.PAA01080@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Bob Bishop cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: interrupt latency In-reply-to: Your message of "Mon, 14 Jul 1997 21:38:11 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 15:13:48 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > >Can anyone recommend a test suite/methodology for evaluating interrupt > >latency? > >I have some ideas for improving the (currently poor) int response of the SMP > >kernel, but need a way to determine if I am actually bettering things. > > A digital output port and an oscilloscope, logic analyser or something > similar. Any other (ie non-hardware) method is just inviting confusion. I tend to agree, but I think the "hardware" solution could be a 4 CPU MB. I was just discussing another possibility that goes as follows: program the first 2/3 CPUsas a 2/3 CPU SMP system. program the 4th CPU as a standalone INT receiver/statistic counter. program the APIC to send all INTs to the 4th CPU. the 4th CPU could then do nothing but accept INTs from the APIC, record the time, then dispatch them to the APIC bus, in a manner identical to that used by the IO APIC. The mainline ISR code could then be modified to send an IPI to the 4th CPU when the ISR was done. The 4th CPU would record the total time and record it in global memory. The 1st 3 CPUs wouldn't have a clue that they weren't getting them from the APIC, and the 4th CPU could service the real INTs almost as fast as they occur. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 15:44:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19120 for hackers-outgoing; Mon, 14 Jul 1997 15:44:07 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19037; Mon, 14 Jul 1997 15:42:31 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id SAA05440; Thu, 26 Jun 1997 18:44:25 GMT Date: Thu, 26 Jun 1997 18:44:25 +0000 (GMT) From: BRiGHTMN To: Steve Passe cc: Bob Bishop , hackers@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: interrupt latency In-Reply-To: <199707142113.PAA01080@Ilsa.StevesCafe.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk dedicate a 600+$ CPU only to interupt control? doesn't sound very cost effective, that would mean a 2 CPU machine would almost "loose" a CPU... > I tend to agree, but I think the "hardware" solution could be a 4 CPU MB. > I was just discussing another possibility that goes as follows: > > program the first 2/3 CPUsas a 2/3 CPU SMP system. > program the 4th CPU as a standalone INT receiver/statistic counter. > program the APIC to send all INTs to the 4th CPU. > > the 4th CPU could then do nothing but accept INTs from the APIC, record > the time, then dispatch them to the APIC bus, in a manner identical to > that used by the IO APIC. The mainline ISR code could then be modified > to send an IPI to the 4th CPU when the ISR was done. The 4th CPU would > record the total time and record it in global memory. The 1st 3 CPUs > wouldn't have a clue that they weren't getting them from the APIC, and the 4th > CPU could service the real INTs almost as fast as they occur. > > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD > > > From owner-freebsd-hackers Mon Jul 14 15:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19128 for hackers-outgoing; Mon, 14 Jul 1997 15:44:10 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19108; Mon, 14 Jul 1997 15:44:02 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id XAA12178; Mon, 14 Jul 1997 23:28:12 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 14 Jul 1997 23:30:30 +0100 X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199707142113.PAA01080@Ilsa.StevesCafe.com> References: Your message of "Mon, 14 Jul 1997 21:38:11 BST." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 14 Jul 1997 23:26:41 +0100 To: Steve Passe From: Bob Bishop Subject: Re: interrupt latency Cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 22:13 +0100 14/7/97, Steve Passe wrote: [...] >> A digital output port and an oscilloscope, logic analyser or something >> similar. Any other (ie non-hardware) method is just inviting confusion. [...] >... and the 4th >CPU could service the real INTs almost as fast as they occur. ^^^^^^ |||||| As I was saying... :-) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Mon Jul 14 16:01:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20075 for hackers-outgoing; Mon, 14 Jul 1997 16:01:09 -0700 (PDT) Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA20065 for ; Mon, 14 Jul 1997 16:01:06 -0700 (PDT) Received: from roo.isi.edu by zephyr.isi.edu (5.65c/5.61+local-26) id ; Mon, 14 Jul 1997 16:01:05 -0700 Message-Id: <199707142301.AA11182@zephyr.isi.edu> X-Mailer: exmh version 1.6.4 10/10/95 To: hackers@freebsd.org Subject: vm_page_alloc_contig again Reply-To: hutton@ISI.EDU Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 97 16:00:04 PDT From: Anne Hutton Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I was hoping for a response from someone on the core team about the functionality of vm_page_alloc_contig...does it do what it is supposed to do in version 3.0? One of the last emails I see on it in the hackers archive suggest it doesn't work as intended - see the included email. The comments in cvsweb on vm revisions also seem unclear as to the status of vm_page_contig_alloc. Anne ------- Forwarded Message Date: Thu, 6 Feb 1997 00:12:02 -0500 (EST) From: "John S. Dyson" To: Shimon@i-Connect.Net (Simon Shapiro) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG Subject: Re: Contigious (spelling?) allocation in kernel Take a look at contigmalloc() or vm_page_alloc_contig() as defined in /sys/vm/vm_page.c. These are almost guaranteed NOT to work after the system is fully up. John ------- End of Forwarded Message From owner-freebsd-hackers Mon Jul 14 16:08:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20423 for hackers-outgoing; Mon, 14 Jul 1997 16:08:20 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20344; Mon, 14 Jul 1997 16:06:48 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id RAA01584; Mon, 14 Jul 1997 17:05:43 -0600 (MDT) Message-Id: <199707142305.RAA01584@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: BRiGHTMN cc: Bob Bishop , hackers@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: interrupt latency In-reply-to: Your message of "Thu, 26 Jun 1997 18:44:25 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 17:05:43 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, --- > dedicate a 600+$ CPU only to interupt control? this is STRICTLY for purposes of testing algorithms, NOT for normal use. --- > doesn't sound very cost effective, that would mean a 2 CPU machine would > almost "loose" a CPU... thats why I said a 4 CPU board would be necessary for this testing method -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 16:11:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20618 for hackers-outgoing; Mon, 14 Jul 1997 16:11:29 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20600; Mon, 14 Jul 1997 16:11:18 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id RAA01616; Mon, 14 Jul 1997 17:11:13 -0600 (MDT) Message-Id: <199707142311.RAA01616@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Bob Bishop cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: interrupt latency In-reply-to: Your message of "Mon, 14 Jul 1997 23:26:41 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 1997 17:11:13 -0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > >> A digital output port and an oscilloscope, logic analyser or something > >> similar. Any other (ie non-hardware) method is just inviting confusion. > [...] > >... and the 4th > >CPU could service the real INTs almost as fast as they occur. > ^^^^^^ > |||||| > > As I was saying... :-) but for this scheme that delay is irrelevant, as I can time exactly the difference from the point that the '4th CPU' sends the INT via the APIC bus and the time the ISR is completed. think of the 4th CPU as a very intelligent IO APIC that can record (once tied to specific software) all the timings of the INT events. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hackers Mon Jul 14 16:37:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21852 for hackers-outgoing; Mon, 14 Jul 1997 16:37:55 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA21847; Mon, 14 Jul 1997 16:37:52 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wnubk-0005kw-00; Mon, 14 Jul 1997 16:32:44 -0700 Date: Mon, 14 Jul 1997 16:32:43 -0700 (PDT) From: Tom Samplonius To: BRiGHTMN cc: hackers@freebsd.org, smp@freebsd.org Subject: Re: interrupt latency In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997, BRiGHTMN wrote: > dedicate a 600+$ CPU only to interupt control? > doesn't sound very cost effective, that would mean a 2 CPU machine would > almost "loose" a CPU... I guess you missed that the thread here was to measure interupt latency. The above is a way to do that. Tom From owner-freebsd-hackers Mon Jul 14 16:45:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22131 for hackers-outgoing; Mon, 14 Jul 1997 16:45:19 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22120 for ; Mon, 14 Jul 1997 16:45:11 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id SAA00363; Mon, 14 Jul 1997 18:45:05 -0500 (EST) From: "John S. Dyson" Message-Id: <199707142345.SAA00363@dyson.iquest.net> Subject: Re: vm_page_alloc_contig again In-Reply-To: <199707142301.AA11182@zephyr.isi.edu> from Anne Hutton at "Jul 14, 97 04:00:04 pm" To: hutton@ISI.EDU Date: Mon, 14 Jul 1997 18:45:04 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Hi, > > I was hoping for a response from someone on the core team about the > functionality of vm_page_alloc_contig...does it do what it is supposed to do > in version 3.0? > vm_page_alloc_contig works best before the system is fully up. It is used to allocate medium sized contiguous chunks at bootup time. > > One of the last emails I see on it in the hackers archive suggest it doesn't > work as intended - see the included email. The comments in cvsweb on vm > revisions also seem unclear as to the status of vm_page_contig_alloc. > We don't have a very reliable method for allocating large amounts of contiguous memory in the kernel. If you don't need contiguous memory, then there are other ways to allocate virtually contiguous memory. The simplest is kernel malloc. The memory will be virtually contiguous, but will not likely be physically contiguous. I don't/can't keep up with all questions... What exactly are you trying to do? John dyson@freebsd.org (Core) From owner-freebsd-hackers Mon Jul 14 16:46:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22274 for hackers-outgoing; Mon, 14 Jul 1997 16:46:53 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22267 for ; Mon, 14 Jul 1997 16:46:50 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id QAA11206 for freebsd-hackers@freebsd.org; Mon, 14 Jul 1997 16:44:44 -0700 (PDT) From: Vinay Bannai Message-Id: <199707142344.QAA11206@agni.nuko.com> Subject: PCI ethernet driver clarification?? To: freebsd-hackers@freebsd.org Date: Mon, 14 Jul 1997 16:44:44 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I am in the middle of writing a PCI driver for i960 based card. I am using the fxp driver for clarifications (since it is more elegant than de driver). After searching through the files, I still have not figured out the exact function of each member of the fxp_csr and the fxp_cb_config structure in if_fxp.h. Is this information available anywhere? Thanks Vinay From owner-freebsd-hackers Mon Jul 14 16:55:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22742 for hackers-outgoing; Mon, 14 Jul 1997 16:55:38 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22737 for ; Mon, 14 Jul 1997 16:55:35 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA11304; Mon, 14 Jul 1997 16:56:05 -0700 (PDT) Message-Id: <199707142356.QAA11304@implode.root.com> To: hutton@ISI.EDU cc: hackers@FreeBSD.ORG Subject: Re: vm_page_alloc_contig again In-reply-to: Your message of "Mon, 14 Jul 1997 16:00:04 PDT." <199707142301.AA11182@zephyr.isi.edu> From: David Greenman Reply-To: dg@root.com Date: Mon, 14 Jul 1997 16:56:04 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I was hoping for a response from someone on the core team about the >functionality of vm_page_alloc_contig...does it do what it is supposed to do >in version 3.0? > >One of the last emails I see on it in the hackers archive suggest it doesn't >work as intended - see the included email. The comments in cvsweb on vm >revisions also seem unclear as to the status of vm_page_contig_alloc. vm_page_alloc_contig works fine, but it must be used at startup time as it has no mechanism for doing paging and thus can fail if memory becomes too fragmented. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 14 17:03:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA23135 for hackers-outgoing; Mon, 14 Jul 1997 17:03:56 -0700 (PDT) Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA23130; Mon, 14 Jul 1997 17:03:49 -0700 (PDT) Received: from roo.isi.edu by zephyr.isi.edu (5.65c/5.61+local-26) id ; Mon, 14 Jul 1997 17:03:04 -0700 Message-Id: <199707150003.AA14675@zephyr.isi.edu> X-Mailer: exmh version 1.6.4 10/10/95 To: dyson@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Reply-To: hutton@ISI.EDU Subject: Re: vm_page_alloc_contig again In-Reply-To: Your message of Mon, 14 Jul 1997 18:45:04 -0500. <199707142345.SAA00363@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Jul 97 17:02:03 PDT From: Anne Hutton Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > vm_page_alloc_contig works best before the system is fully up. It is used > to allocate medium sized contiguous chunks at bootup time. > we use vm_page_alloc_contig in a device driver...so it is at boot time and it is a small chunk - 1/2 meg. It allocates ok and the device driver works but we suspect that the pages aren't (really) wired down. We see a page fault and the machine panics when we are forwarding packets through the NIC from another NIC on the same host. Is there a known problem with the pages not being wired down once allocated by vm_page_alloc_contig at boot time? Anne > We don't have a very reliable method for allocating large amounts of > contiguous memory in the kernel. If you don't need contiguous memory, > then there are other ways to allocate virtually contiguous memory. The > simplest is kernel malloc. The memory will be virtually contiguous, > but will not likely be physically contiguous. > From owner-freebsd-hackers Mon Jul 14 18:09:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25768 for hackers-outgoing; Mon, 14 Jul 1997 18:09:42 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25757; Mon, 14 Jul 1997 18:09:34 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA11903; Mon, 14 Jul 1997 18:10:03 -0700 (PDT) Message-Id: <199707150110.SAA11903@implode.root.com> To: hutton@ISI.EDU cc: dyson@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: vm_page_alloc_contig again In-reply-to: Your message of "Mon, 14 Jul 1997 17:02:03 PDT." <199707150003.AA14675@zephyr.isi.edu> From: David Greenman Reply-To: dg@root.com Date: Mon, 14 Jul 1997 18:10:03 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> vm_page_alloc_contig works best before the system is fully up. It is used >> to allocate medium sized contiguous chunks at bootup time. >> > >we use vm_page_alloc_contig in a device driver...so it is at boot time and it >is a small chunk - 1/2 meg. > >It allocates ok and the device driver works but we suspect that the pages >aren't (really) wired down. We see a page fault and the machine panics when we >are forwarding packets through the NIC from another NIC on the same host. Is >there a known problem with the pages not being wired down once allocated by >vm_page_alloc_contig at boot time? There aren't any known problems and several other device drivers use the function to allocate memory without any trouble. Memory allocated to the kernel is never reclaimed by the pagedaemon, so I suspect you've got a bug somewhere in your code. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 14 18:16:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26138 for hackers-outgoing; Mon, 14 Jul 1997 18:16:10 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26131 for ; Mon, 14 Jul 1997 18:16:07 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id SAA06017; Mon, 14 Jul 1997 18:11:58 -0700 (PDT) Message-Id: <199707150111.SAA06017@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Vinay Bannai Cc: freebsd-hackers@freebsd.org Subject: Re: PCI ethernet driver clarification?? Reply-To: Jason Thorpe From: Jason Thorpe Date: Mon, 14 Jul 1997 18:11:57 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997 16:44:44 -0700 (PDT) Vinay Bannai wrote: > I am in the middle of writing a PCI driver for i960 based card. I am using > the fxp driver for clarifications (since it is more elegant than de > driver). After searching through the files, I still have not figured out I'd say "simpler". The "de" driver supports a large variation of chip and board types. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Mon Jul 14 18:27:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26659 for hackers-outgoing; Mon, 14 Jul 1997 18:27:25 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26653 for ; Mon, 14 Jul 1997 18:27:22 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id SAA11462; Mon, 14 Jul 1997 18:25:35 -0700 (PDT) From: Vinay Bannai Message-Id: <199707150125.SAA11462@agni.nuko.com> Subject: Re: PCI ethernet driver clarification?? To: thorpej@nas.nasa.gov Date: Mon, 14 Jul 1997 18:25:35 -0700 (PDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199707150111.SAA06017@lestat.nas.nasa.gov> from "Jason Thorpe" at "Jul 14, 97 06:11:57 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Jason Thorpe: > On Mon, 14 Jul 1997 16:44:44 -0700 (PDT) > Vinay Bannai wrote: > > > I am in the middle of writing a PCI driver for i960 based card. I am using > > the fxp driver for clarifications (since it is more elegant than de > > driver). After searching through the files, I still have not figured out > > I'd say "simpler". The "de" driver supports a large variation of > chip and board types. > Yup. I guess that was I meant. Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Mon Jul 14 18:36:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27125 for hackers-outgoing; Mon, 14 Jul 1997 18:36:27 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27120 for ; Mon, 14 Jul 1997 18:36:24 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA12200; Mon, 14 Jul 1997 18:36:53 -0700 (PDT) Message-Id: <199707150136.SAA12200@implode.root.com> To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI ethernet driver clarification?? In-reply-to: Your message of "Mon, 14 Jul 1997 16:44:44 PDT." <199707142344.QAA11206@agni.nuko.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 14 Jul 1997 18:36:53 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I am in the middle of writing a PCI driver for i960 based card. I am using >the fxp driver for clarifications (since it is more elegant than de >driver). After searching through the files, I still have not figured out >the exact function of each member of the fxp_csr and the fxp_cb_config >structure in if_fxp.h. Struct fxp_csr are the control/status registers for the controller. Struct fxp_cb_config is a special configuration data structure that is initialized and DMAed to the card in order to configure various internal parameters. Sorry, I should better document the header file/register definitions. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 14 19:09:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28949 for hackers-outgoing; Mon, 14 Jul 1997 19:09:51 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28929 for ; Mon, 14 Jul 1997 19:09:48 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id UAA13306 for ; Mon, 14 Jul 1997 20:09:54 -0600 (MDT) Date: Mon, 14 Jul 1997 20:09:54 -0600 (MDT) From: Brandon Gillespie To: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <199707110048.RAA02792@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk So THATS why GIMP doesn't run!! I've installed GIMP several times, and its pissed me off because all it does is die when I run it with SIGSYS. The least that could happen is the port for GIMP could _MENTION_ if not check to see if SYSVSHM is installed. -Brandon Gillespie From owner-freebsd-hackers Mon Jul 14 19:16:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29297 for hackers-outgoing; Mon, 14 Jul 1997 19:16:37 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29285 for ; Mon, 14 Jul 1997 19:16:31 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA13392; Tue, 15 Jul 1997 11:44:48 +0930 (CST) From: Michael Smith Message-Id: <199707150214.LAA13392@genesis.atrad.adelaide.edu.au> Subject: Re: IPX routing? In-Reply-To: <199707141842.LAA01763@phaeton.artisoft.com> from Terry Lambert at "Jul 14, 97 11:42:15 am" To: terry@lambert.org (Terry Lambert) Date: Tue, 15 Jul 1997 11:44:48 +0930 (CST) Cc: jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > At the moment the code in FreeBSD only do Ethernet_II framing, so > > > > you will have use that on the nets that connects to the FreeBSD box. > > > > > > Ok. That would have been more or less impossible. 8( > > > > Why? I don't know of any clients that can't do Ethernet_II framing. > > All clients using Novell supplied "remote reset" (NetWare based > remote boot protocol to boot from NetWare servers) are hard-coded > as 802.3 clients. Oh. That sinks that idea; we were trying to "remote reset" clients across the router too. Booger. > Yes, you can get 3rd party ROM's, but that's an additional expense. Hmm. How about getting the Netware server to gateway DHCP requests? > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Jul 14 19:21:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29494 for hackers-outgoing; Mon, 14 Jul 1997 19:21:28 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29488 for ; Mon, 14 Jul 1997 19:21:24 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id UAA13366 for ; Mon, 14 Jul 1997 20:21:30 -0600 (MDT) Date: Mon, 14 Jul 1997 20:21:30 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: /etc/init.d/ .. both? In-Reply-To: <33CA3780.389F@cki.ipri.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just a thought.. why not have both? Somebody mentioned /var as a better machine-specific mount point than /etc--but /sbin is also used. If it was /var/ there should at least be a softlink from /etc to lessen confusion. Regardless, it would not be a problem at all to check both locations.. no? Frankly, if I were to do things via NFS I would also have exported 'local' without giving it a second thought. 'local' IMHO is the repository for software systems outside the normal bounds of the standard OS install--not necessarily the configurations. I can live with local/etc/rc.d, but there should still be an option for packages which are not necessarily something you want to globally install--and are instead specific to one or a few hosts (such as HTTPd). -Brandon Gillespie From owner-freebsd-hackers Mon Jul 14 19:28:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29670 for hackers-outgoing; Mon, 14 Jul 1997 19:28:13 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29665 for ; Mon, 14 Jul 1997 19:28:12 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id UAA13383 for ; Mon, 14 Jul 1997 20:28:19 -0600 (MDT) Date: Mon, 14 Jul 1997 20:28:19 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freefall.FreeBSD.org Subject: multiple run-levels (was: Re: /etc/init.d/) In-Reply-To: <33CA3780.389F@cki.ipri.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Terry mentioned, the concept of run-levels is sound, its just that the SysV implementation where '1' is single user and '2' can be something else and '3' is sometimes network level, etc, SUCKS Frankly, abstraction by simply using tokens instead of digits would be a simple solution to allow a standard as well as an easy means to extend without confusing things. For instance, it could ship with: SYSV FreeBSD 1 singleuser -- Single User Mode 2 multiuser -- Multi User Mode 3 network -- generic "Network" mode The SYSV is listed simply for comparison. With this, simply give a startup/shutdown capability for each run-level, and you are set. Perhaps create a RUNLEVEL/select script which returns 0 when this level should be run, and a 1 when it shouldn't be run--the select could decide these things based off the hardware situation or current run-level. This way joe-wiz could have 30 different run levels with hardware based changing, etc. Just a thought.. -Brandon Gillespie From owner-freebsd-hackers Mon Jul 14 20:26:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01668 for hackers-outgoing; Mon, 14 Jul 1997 20:26:57 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01663 for ; Mon, 14 Jul 1997 20:26:54 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id XAA27623; Mon, 14 Jul 1997 23:26:47 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA25126; Mon, 14 Jul 1997 23:26:45 -0400 Date: Mon, 14 Jul 1997 23:26:46 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brandon Gillespie cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Brandon Gillespie wrote: > So THATS why GIMP doesn't run!! > > I've installed GIMP several times, and its pissed me off because all it > does is die when I run it with SIGSYS. The least that could happen is the > port for GIMP could _MENTION_ if not check to see if SYSVSHM is installed. I think, Brandon, that you're wrong. The gimp software uses SYSVSHM, not the port. The port works fine, and if you have an argument with how gimp works, you should take that up with the guys who wrote it. You know very well that you're pointing your gun at the wrong people. > > -Brandon Gillespie > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jul 14 21:31:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04016 for hackers-outgoing; Mon, 14 Jul 1997 21:31:55 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04011 for ; Mon, 14 Jul 1997 21:31:51 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.6) id OAA18880 for freebsd-hackers@freebsd.org; Tue, 15 Jul 1997 14:31:45 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id OAA01561; Tue, 15 Jul 1997 14:16:01 +1000 (EST) Message-Id: <199707150416.OAA01561@ogre.dtir.qld.gov.au> To: freebsd-hackers@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: multiple run-levels (was: Re: /etc/init.d/) References: In-Reply-To: from Brandon Gillespie at "Tue, 15 Jul 1997 02:28:19 +0000" Date: Tue, 15 Jul 1997 14:16:00 +1000 From: Stephen McKay Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, 15th July 1997, Brandon Gillespie wrote: >As Terry mentioned, the concept of run-levels is sound, its just that the >SysV implementation where '1' is single user and '2' can be something else >and '3' is sometimes network level, etc, SUCKS I'm one of the (raving monster looney) objectors to the run level concept. Even if you fix the crap that System V has, I still find the whole concept intensely objectionable. There are reasons to have a maintenance mode, and an operational mode, which we call single user mode and multi user mode. There is no need for the other junk. Terry described a complex way to use his mobile computer which boils down to a desire to: 1) add and remove network connections 2) add and remove hardware while continuing in multiuser mode. No more magic than that. Appearing and disappearing network connections can be dealt with using some program similar to routed. Adding and removing hardware will be more difficult, but won't be handled by run states. It will have to be handled by device drivers. Run levels suck, and I'm going to hold my breath until you all forget about them. Run states also suck, because they are too simplistic. Why consider the presence of a network connection as different from the presence of my window manager (say). I've got at least 6 window managers I could use, but I don't need run states for that. When I change my mind, I kill one and start another. When I need different networking, I run the connect program. You can call these things different "states", but you don't gain anything by coding all possible arrangements and wiring them into a directory structure. Fuzzy thinking here will just lumber us with more cruft. Stephen. From owner-freebsd-hackers Mon Jul 14 22:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA05703 for hackers-outgoing; Mon, 14 Jul 1997 22:12:39 -0700 (PDT) Received: from roguetrader.com (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA05698 for ; Mon, 14 Jul 1997 22:12:36 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id XAA13842; Mon, 14 Jul 1997 23:12:39 -0600 (MDT) Date: Mon, 14 Jul 1997 23:12:39 -0600 (MDT) From: Brandon Gillespie To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Chuck Robey wrote: > On Mon, 14 Jul 1997, Brandon Gillespie wrote: > > > So THATS why GIMP doesn't run!! > > > > I've installed GIMP several times, and its pissed me off because all it > > does is die when I run it with SIGSYS. The least that could happen is the > > port for GIMP could _MENTION_ if not check to see if SYSVSHM is installed. > > I think, Brandon, that you're wrong. The gimp software uses SYSVSHM, not > the port. The port works fine, and if you have an argument with how gimp > works, you should take that up with the guys who wrote it. You know very > well that you're pointing your gun at the wrong people. > Yes, I know its the GIMP author's fault for using SYSVSHM, that isn't my point. I assumed that a port would create a software package which would run with a GENERIC kernel, my mistake for assuming. -Brandon From owner-freebsd-hackers Mon Jul 14 22:19:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA05931 for hackers-outgoing; Mon, 14 Jul 1997 22:19:00 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA05926 for ; Mon, 14 Jul 1997 22:18:58 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id WAA11817; Mon, 14 Jul 1997 22:16:30 -0700 (PDT) From: Vinay Bannai Message-Id: <199707150516.WAA11817@agni.nuko.com> Subject: Re: PCI ethernet driver clarification?? To: dg@root.com Date: Mon, 14 Jul 1997 22:16:29 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707150136.SAA12200@implode.root.com> from "David Greenman" at "Jul 14, 97 06:36:53 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to David Greenman: > >I am in the middle of writing a PCI driver for i960 based card. I am using > >the fxp driver for clarifications (since it is more elegant than de > >driver). After searching through the files, I still have not figured out > >the exact function of each member of the fxp_csr and the fxp_cb_config > >structure in if_fxp.h. > > Struct fxp_csr are the control/status registers for the controller. > Struct fxp_cb_config is a special configuration data structure that is > initialized and DMAed to the card in order to configure various internal > parameters. > Sorry, I should better document the header file/register definitions. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project Thanks for your response. But my question was how do I get hold of the map of the internal parameters on the card mapped to the memory? Meaning what do each of the bit fields in the fxp_cb_config mean? Does Intel make such information public and what is procedure to get this information from vendors? I guess you are the best person to answer such questions. :-) Vinay -- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Mon Jul 14 22:59:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07754 for hackers-outgoing; Mon, 14 Jul 1997 22:59:59 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07749 for ; Mon, 14 Jul 1997 22:59:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA14352; Mon, 14 Jul 1997 23:00:25 -0700 (PDT) Message-Id: <199707150600.XAA14352@implode.root.com> To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCI ethernet driver clarification?? In-reply-to: Your message of "Mon, 14 Jul 1997 22:16:29 PDT." <199707150516.WAA11817@agni.nuko.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 14 Jul 1997 23:00:25 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Thanks for your response. But my question was how do I get hold of the map >of the internal parameters on the card mapped to the memory? Meaning what >do each of the bit fields in the fxp_cb_config mean? Does Intel make such >information public and what is procedure to get this information from >vendors? The programming manual is available from Intel under an NDA. I was able to get the manual via a special inside arrangement and didn't have to sign an NDA...but this special arrangement will probably never happen again. The bitfields are described in the device driver where they are initialized. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 14 23:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09885 for hackers-outgoing; Mon, 14 Jul 1997 23:52:11 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09880 for ; Mon, 14 Jul 1997 23:52:05 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id QAA00408; Tue, 15 Jul 1997 16:50:53 +1000 (EST) Message-Id: <199707150650.QAA00408@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: /etc/rc.shutdown X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jul 1997 16:50:52 +1000 From: David Nugent Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm in the process of testing your patch with some minor changes that make it work better, but I've come across a problem. /etc/rc.shutdown will never be run, because setctty() never returns - it reports "can't get /dev/console for controlling terminal: Operation not permitted" and exits the child process. Any ideas? The first ioctl() in login_tty() seems to be the point at which things fail. BTW, this is no doubt covering old ground, but obviously /sbin/shutdown doesn't run this. Should it, or should an option be added to cause it to raise a SIGINT/SIGQUIT to init? From owner-freebsd-hackers Tue Jul 15 00:44:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12476 for hackers-outgoing; Tue, 15 Jul 1997 00:44:23 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12336; Tue, 15 Jul 1997 00:40:46 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA10413; Tue, 15 Jul 1997 17:32:50 +1000 Date: Tue, 15 Jul 1997 17:32:50 +1000 From: Bruce Evans Message-Id: <199707150732.RAA10413@godzilla.zeta.org.au> To: smp@csn.net, smp@FreeBSD.ORG Subject: Re: interrupt latency Cc: hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can anyone recommend a test suite/methodology for evaluating interrupt latency? I sent Steve some code. Bruce From owner-freebsd-hackers Tue Jul 15 00:51:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12963 for hackers-outgoing; Tue, 15 Jul 1997 00:51:04 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA12948 for ; Tue, 15 Jul 1997 00:50:58 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA03848 for hackers@freefall.freebsd.org; Tue, 15 Jul 1997 09:50:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA06303; Tue, 15 Jul 1997 09:37:47 +0200 (MET DST) Message-ID: <19970715093747.OA57762@uriah.heep.sax.de> Date: Tue, 15 Jul 1997 09:37:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@freefall.freebsd.org Subject: Re: aha1522 ?? References: <199707141943.OAA07339@beowulf.utmb.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707141943.OAA07339@beowulf.utmb.edu>; from M. L. Dodson on Jul 14, 1997 14:43:34 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As M. L. Dodson wrote: > > This is an understatement. I would call it ``basically unusable''. > > It suffers extensive bit-rot. > Doesn't the 1522 use the same driver as the little minimal controller > that comes with internal SCSI ZIP disks? It does. > I've been recommending that > to people to "gently" introduce them to SCSI (for SCSI tape drives, > for example). Is this status likely to remain this way? Unless you volunteer to change it, probably. Even if the driver were better, the AIC6[23]60 is a PIO-mode chip, which makes it suffering the same performance vs. CPU-load problems like IDE. Btw., since most machines these days are PCI anyway, you can always recommend the SymBios controllers (formerly NCR) for a cheap solution. They aren't only cheap, but powerful, and FreeBSD ships with a well- working driver for them (...says Joerg, typing this on a machine with two 53c810's). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 15 01:02:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA13578 for hackers-outgoing; Tue, 15 Jul 1997 01:02:33 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA13548 for ; Tue, 15 Jul 1997 01:02:16 -0700 (PDT) Received: (qmail 9365 invoked by uid 1000); 15 Jul 1997 08:02:10 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707141751.LAA02683@Ilsa.StevesCafe.com> Date: Tue, 15 Jul 1997 01:02:10 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Steve Passe Subject: RE: interrupt latency Cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Steve Passe; On 14-Jul-97 you wrote: > Hi, > > Can anyone recommend a test suite/methodology for evaluating interrupt > latency? > I have some ideas for improving the (currently poor) int response of the > SMP > kernel, but need a way to determine if I am actually bettering things. > > -- > Steve Passe | powered by > smp@csn.net | Symmetric MultiProcessor FreeBSD > > I have microtime calls in the DPT driver. If I understand it correctly, on a P6-200 I could have 200 times better resolution with access to the registers in the CPU. I see interrupt latency of 0-3us with UP, and about the same with SMP, but suspect the timers resolution at these low numbers. Will be glad to acomodate. Simon From owner-freebsd-hackers Tue Jul 15 01:25:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14770 for hackers-outgoing; Tue, 15 Jul 1997 01:25:15 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA14722; Tue, 15 Jul 1997 01:24:00 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id JAA12495; Tue, 15 Jul 1997 09:19:25 +0200 From: Luigi Rizzo Message-Id: <199707150719.JAA12495@labinfo.iet.unipi.it> Subject: Re: interrupt latency To: Shimon@i-Connect.Net (Simon Shapiro) Date: Tue, 15 Jul 1997 09:19:25 +0200 (MET DST) Cc: smp@csn.net, hackers@FreeBSD.ORG, smp@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Jul 15, 97 01:01:51 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have microtime calls in the DPT driver. If I understand it correctly, on > a P6-200 I could have 200 times better resolution with access to the > registers in the CPU. I see interrupt latency of 0-3us with UP, and about perhaps 200 is too much (since any cpu stall, cache miss, etc. will hit you with a fair number of wasted cycles) but certainly 10-20 times better resolution. Luigi From owner-freebsd-hackers Tue Jul 15 01:26:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14824 for hackers-outgoing; Tue, 15 Jul 1997 01:26:02 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA14819 for ; Tue, 15 Jul 1997 01:25:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA04117 for hackers@FreeBSD.ORG; Tue, 15 Jul 1997 10:25:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA06577; Tue, 15 Jul 1997 10:12:31 +0200 (MET DST) Message-ID: <19970715101231.JO07295@uriah.heep.sax.de> Date: Tue, 15 Jul 1997 10:12:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Chuck Robey on Jul 14, 1997 23:26:46 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Chuck Robey wrote: > I think, Brandon, that you're wrong. The gimp software uses SYSVSHM, not > the port. Sure. But why not adding a small `patch' that catches SIGSYS, and exits cleanly telling the user to include SYSVSHM into her kernel? (That's the same way the XFree86 servers use to disable MIT-SHM.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 15 02:22:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17283 for hackers-outgoing; Tue, 15 Jul 1997 02:22:18 -0700 (PDT) Received: from ns.uk.peer.net ([194.117.157.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA17258 for ; Tue, 15 Jul 1997 02:21:25 -0700 (PDT) Received: (from aledm@localhost) by ns.uk.peer.net (8.6.12/8.6.12) id KAA27592; Tue, 15 Jul 1997 10:42:12 +0100 Date: Tue, 15 Jul 1997 10:42:11 +0100 (BST) From: Aled Morris X-Sender: aledm@ns.uk.peer.net To: freebsd-hackers@FreeBSD.ORG cc: Stephen McKay Subject: Re: multiple run-levels (was: Re: /etc/init.d/) In-Reply-To: <199707150416.OAA01561@ogre.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Jul 1997, Stephen McKay wrote: > Run levels suck, For what it's worth, I agree with this. One of the major advantages of using FreeBSD over SCO or NT is the simplicity of the system. Adding run levels adds uneccesary complexity. Run levels don't do away with "ps", "init", "/etc/rc" or any of those other tools that we currently use to achieve process control, they just add more cruft, and more to the learning curve that dissuades new users from choosing FreeBSD over the alternatives. If anyone out there is desperate to implement run levels, you could release it as a pkg. Aled -- +44 973 207987 O- From owner-freebsd-hackers Tue Jul 15 02:35:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17650 for hackers-outgoing; Tue, 15 Jul 1997 02:35:53 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17454 for ; Tue, 15 Jul 1997 02:28:36 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id PAA08078; Tue, 15 Jul 1997 15:26:58 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707150926.PAA08078@hq.icb.chel.su> Subject: Re: IPX routing? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 15 Jul 1997 15:26:57 +0600 (ESD) Cc: jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199707140915.SAA09440@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 14, 97 06:45:28 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I do have code that do the Novel 802.3 protocol, but it only works > > on the ed0 type cards because I use link1 in ifconfig to set it > > and most other cards use that for something else like switching > > 10BT on/off. > > Erk. Do I take it then that it's not possible to do the 802.[23] protocols > as well as Ethernet_II simultaneously on the same interface? It's possible to receive both types of frames. But how to know which kind of encapsulation to use when you SEND the packets ? The only way to use both encapsulations I see is to keep a table that maps each network address to encapsulation type and fill it using the received packets. I've looked ayt the Linux code and it seems to me that they just allow the applied software to decide which encapsulation type to use: they just fill the full IPX header (that includes Ethernet header) in user-level software rather than in driver. It would be not bad to make the IPX implementation more Linux-like so it would be easy to port Netware emulators. -SB From owner-freebsd-hackers Tue Jul 15 02:54:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA18384 for hackers-outgoing; Tue, 15 Jul 1997 02:54:15 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18379 for ; Tue, 15 Jul 1997 02:54:12 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id TAA15895; Tue, 15 Jul 1997 19:11:56 +0930 (CST) From: Michael Smith Message-Id: <199707150941.TAA15895@genesis.atrad.adelaide.edu.au> Subject: Re: IPX routing? In-Reply-To: <199707150919.PAA07043@hq.icb.chel.su> from "Serge A. Babkin" at "Jul 15, 97 03:19:58 pm" To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Tue, 15 Jul 1997 19:11:55 +0930 (CST) Cc: jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Serge A. Babkin stands accused of saying: > > By the way, is there any free link level flag ? As far as I remember > some flag was obsoleted and freed the space. I think it can be used > to switch the IPX code on an interface between 802.3 and EthernetII. This should probably be done with the if_media stuff, I guess. > -SB -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jul 15 03:15:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19247 for hackers-outgoing; Tue, 15 Jul 1997 03:15:49 -0700 (PDT) Received: from gateway.cam-ani.co.uk (gateway.cam-ani.co.uk [193.195.55.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA19239 for ; Tue, 15 Jul 1997 03:15:40 -0700 (PDT) Received: from louie by gateway.cam-ani.co.uk (CAS1.1) id AA09737; Tue, 15 Jul 97 11:15:31 +0100 Received: from dumbo.cam-ani.co.uk (dumbo [192.42.172.34]) by louie.cam-ani.co.uk (8.7.5/8.7.3) with SMTP id LAA08129 for ; Tue, 15 Jul 1997 11:15:30 +0100 (BST) Message-Id: <199707151015.LAA08129@louie.cam-ani.co.uk> Received: by dumbo.cam-ani.co.uk (NX5.67f2/NX3.0X) id AA28350; Tue, 15 Jul 97 11:15:29 +0100 Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Ian Stephenson Date: Tue, 15 Jul 97 11:15:28 +0100 To: hackers@FreeBSD.ORG Subject: Apple Localtalk X-Url: http://www.geocities.com/SunsetStrip/Club/9199/ Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've been working on a driver for an Apple ISA Localtalk card. Last night I finally got the Mac to mount volumes from freeBSD! :-) Big grins... There are still a few issues to be resolved, particularly testing on mixed Ether/Localtalk and phase1/phase2 nets. Is anyone running a phase 1 ethertalk? I had to patch some of the phase 1 kernel code to get things working, and I suspect that the fixes may be generic. If anyone has a suitable setup, and could help with testing (and release?) that would be a big help, as I've only got one working Mac so I can't really push things! $an From owner-freebsd-hackers Tue Jul 15 03:30:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19858 for hackers-outgoing; Tue, 15 Jul 1997 03:30:50 -0700 (PDT) Received: from veda.is (veda.is [193.4.230.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19853 for ; Tue, 15 Jul 1997 03:30:45 -0700 (PDT) Received: from ubiq.veda.is (ubiq.veda.is [193.4.230.60]) by veda.is (8.8.5/8.8.5) with ESMTP id KAA14951 for ; Tue, 15 Jul 1997 10:30:41 GMT From: Adam David Received: (from adam@localhost) by ubiq.veda.is (8.8.6/8.8.5) id KAA23198 for freebsd-hackers@freebsd.org; Tue, 15 Jul 1997 10:30:37 GMT Message-Id: <199707151030.KAA23198@ubiq.veda.is> Subject: numeric UID/GID names? To: freebsd-hackers@freebsd.org Date: Tue, 15 Jul 1997 10:30:36 +0000 (GMT) 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Are there any problems involved with giving users/groups all-numeric names, in addition to the confusion that could exist when for instance UID number 1234 is named 4321 (or 5678)? What problems might this confusion give rise to? Which are human-based and which are programmatical? Is this any different if all such names are larger numbers than the maximum available ID#, or some other identification scheme is used? (for instance, rather than specify >4G of users all individually, they could be hashed into subgroups of which all members share a common ID, or individual members could be tagged on entry and exit from the ID pool). -- Adam David From owner-freebsd-hackers Tue Jul 15 04:20:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA21646 for hackers-outgoing; Tue, 15 Jul 1997 04:20:08 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21400 for ; Tue, 15 Jul 1997 04:14:33 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id PAA07043; Tue, 15 Jul 1997 15:19:59 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707150919.PAA07043@hq.icb.chel.su> Subject: Re: IPX routing? To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 15 Jul 1997 15:19:58 +0600 (ESD) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199707131647.SAA28393@zibbi.mikom.csir.co.za> from "John Hay" at Jul 13, 97 06:47:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > At the moment the code in FreeBSD only do Ethernet_II framing, so > you will have use that on the nets that connects to the FreeBSD box. > I do have code that do the Novel 802.3 protocol, but it only works > on the ed0 type cards because I use link1 in ifconfig to set it > and most other cards use that for something else like switching > 10BT on/off. By the way, is there any free link level flag ? As far as I remember some flag was obsoleted and freed the space. I think it can be used to switch the IPX code on an interface between 802.3 and EthernetII. -SB From owner-freebsd-hackers Tue Jul 15 05:15:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23322 for hackers-outgoing; Tue, 15 Jul 1997 05:15:32 -0700 (PDT) Received: from aaka.3skel.com (aaka.3skel.com [207.240.134.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA23316 for ; Tue, 15 Jul 1997 05:15:27 -0700 (PDT) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by aaka.3skel.com (8.8.5/8.8.2) with ESMTP id IAA06493 for ; Tue, 15 Jul 1997 08:15:24 -0400 (EDT) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by fnur.3skel.com (8.8.5/8.8.2) with ESMTP id IAA02098 for ; Tue, 15 Jul 1997 08:15:23 -0400 (EDT) Message-ID: <33CB69DA.9B1052@3skel.com> Date: Tue, 15 Jul 1997 08:15:22 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: multiple run-levels (was: Re: /etc/init.d/) X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi All, A multiple runlevel mechanism provides some benefits, but most of them are secondary. The runlevel part is mostly smoke. The benefits are that each class or group of programs/processes has its own shell script for initialization. This is a LOT like the way we have stuff in /usr/local/etc/rc.d. The other stuff, concerning what services should be started if you are at init 2 instead of init 3 is more complicated than what a "runlevel" can address. A long time ago, when I was younger, I wrote an entire runlevel and init.d/rc?.d system for Linux based on IRIX. There were only two things that were of any use: 1. At the boot loader prompt you could set a variable (LOCALE) that was available to the rc scripts that would allow the employment of location based control of what services should/shouldn't, network interfaces... 2. chkconfig, which is an IRIX particular rc mechanism that allows one to type 'chkconfig timed off' at a prompt, and the next time you go to a multiuser state, timed would not be started. This meant that no actual file editing was necessary. To REALLY be useful, a mechanism has to be able to change resolv.conf, host.conf, hosts, ifconfigs, fstabs (for local and NFS), libsocks.conf, routes, etc. All kinds of crap really. Init.d ain't gonna do it. Another mechanism can be designed and implemented, but it isn't really going to look like anything that we've seen before. Dan -- danj@3skel.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-hackers Tue Jul 15 05:19:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23477 for hackers-outgoing; Tue, 15 Jul 1997 05:19:54 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA23469 for ; Tue, 15 Jul 1997 05:19:51 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id NAA13882; Tue, 15 Jul 1997 13:18:59 +0100 (BST) Date: Tue, 15 Jul 1997 13:18:59 +0100 (BST) From: Stephen Roome To: Josef Karthauser cc: BRiGHTMN , Stephen Hocking , hackers@FreeBSD.ORG Subject: Re: =?iso-8859-1?Q?Things_that_=A3$=22$_me_off_about_fbsd?= In-Reply-To: <19970714164708.28827@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Jul 1997, Josef Karthauser wrote: > On Mon, Jul 14, 1997 at 12:15:44PM +0100, Stephen Roome wrote: > > > > I think you really just need the exact right card, nothing else ever > > works great - my one great gripe with FreeBSD. > > > > I've got none ;) > (apart from crashing my machine this morning whilst trying to > ls an msdos floppy which was busy having a file copied to it. Someone once mentioned that this is due to not using the correct device, although I'm not sure it's that simple. But then if you think that's bad how about nfs. mount a filesystem off any other freebsd machine and then unplug that freebsd machine, you can't unmount that remote system without going through hell - or a power cycle. > > Carnage!! Takes the entire fs mechanism down, i.e. mount hangs, > umount hangs, aaarrrrgggghhh!) Same for nfs. It's not as bad as M$ Windows which can't do anything while formatting a floppy, but it's pretty bad. (Perhaps I have more gripes with FreeBSD than I realised!) Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-hackers Tue Jul 15 05:38:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24473 for hackers-outgoing; Tue, 15 Jul 1997 05:38:56 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24379; Tue, 15 Jul 1997 05:37:52 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA21429; Tue, 15 Jul 1997 22:34:34 +1000 Date: Tue, 15 Jul 1997 22:34:34 +1000 From: Bruce Evans Message-Id: <199707151234.WAA21429@godzilla.zeta.org.au> To: luigi@labinfo.iet.unipi.it, smp@csn.net Subject: Re: interrupt latency Cc: hackers@FreeBSD.ORG, smp@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >the problem: > > in our SMP system an INT may be sent to a CPU that can't enter the kernel >because another CPU is currently inside the kernel. this causes a long delay >between the time the INT tickels the hardware and the time the ISR actually >runs. > >--- >So I guess the 2 points in time are the actual instance of hardware >INT and the time the ISR completes. The closest the software can get to >determining the start point would be on entry to _XintrNN (isa/apic_vector.s) >A convenient stop point would be immediately after the lock is acquired >(ie, after GET_MPLOCK in _XintrNN), the completion of the ISR code should be >constant. High-resolution kernel profiling (option GUPROF + kgmon -B) would show the time spent by interrupt handlers (if it worked on SMP systems :-]). The results wouldn't be very interesting. Some ISRs take several msec. You don't need hardware to measure such gross latency. I think a latency of several msec is actually only bad (relative to the uniprocessor case) for clock and fast interrupts. Network interrupts probably should have higher priority than disk interrupts, but disk interrupts can currently preempt network interrupts, and vice versa. Handling pcaudio (clock) interrupts at 16KHz is a good test. The clock interrupts should not be affected by disk and network ISRs. >But this hides the time between the actual firing of the hardware INT and >the time a CPU accepts it. This could be fairly long if the "accepting CPU" >is stuck behing the "giant lock", as hardware INTs are blocked during this >time. You'll have to arrange for INTs sent to CPUs not in the kernel to be sent to the one in the kernel just to match uniprocessor interrupt latency. Bruce From owner-freebsd-hackers Tue Jul 15 05:48:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24849 for hackers-outgoing; Tue, 15 Jul 1997 05:48:09 -0700 (PDT) Received: from zeus.carroll.com (zeus.carroll.com [199.224.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24844 for ; Tue, 15 Jul 1997 05:48:06 -0700 (PDT) Received: from apollo.carroll.com [199.224.10.3] by zeus.carroll.com with ESMTP (8.8.5/0) id IAA29239; Tue, 15 Jul 1997 08:48:04 -0400 Received: by apollo.carroll.com (8.8.5) is IAA09307; Tue, 15 Jul 1997 08:48:04 -0400 Date: Tue, 15 Jul 1997 08:48:01 -0400 From: Jim Carroll To: freebsd-hackers@freebsd.org Subject: make boot.flp Explodes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been having trouble now for 5 days trying to get the stock boot.flp make file to compile under FreeBSD 2.2.1 with absolutely no luck. I have reinstalled the OS from scratch on a clean hard drive, but each time I try the make, I get the same error. Here is the sequence of events I perform, and the error message: cd /usr/src/release make boot.flp ( cd /R/stage/trees/bin/dev && ls console tty ttyv0 ttyv1 ttyv2 ttyv3 null zero *[swo]d* cuaa[01] cuaa[23] fd[01] rfd[01] cd0a mcd0a scd0a matcd0a wcd0c rst0 rft0 rwt0 | cpio -dump /R/stage/mfsfd/dev ) cd: can't cd to /R/stage/trees/bin/dev *** Error code 2 Stop. *** Error code 1 Stop I have been pulling my hair out on this one. I would be grateful to anyone who can point me in the correct direction. Both I (and my hairline) thank-you. --- Jim C., President | C A R R O L L - N E T, Inc. 201-488-1332 voice | New Jersey's Premier Internet Service Provider 201-487-5717 dialup | http://www.carroll.com | Ask about our Business Messaging Services From owner-freebsd-hackers Tue Jul 15 06:19:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA25871 for hackers-outgoing; Tue, 15 Jul 1997 06:19:10 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA25866 for ; Tue, 15 Jul 1997 06:19:06 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id GAA00746; Tue, 15 Jul 1997 06:17:54 -0700 (PDT) To: Jim Carroll cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make boot.flp Explodes In-reply-to: Your message of "Tue, 15 Jul 1997 08:48:01 EDT." Date: Tue, 15 Jul 1997 06:17:54 -0700 Message-ID: <743.868972674@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have been having trouble now for 5 days trying to get the stock > boot.flp make file to compile under FreeBSD 2.2.1 with absolutely no > luck. > > I have reinstalled the OS from scratch on a clean hard drive, but each > time I try the make, I get the same error. Here is the sequence of > events I perform, and the error message: > > cd /usr/src/release > make boot.flp Heh. This target is not meant to be run stand-alone; you MUST run it as part of the release target. To put it another way, there are only two supported targets in /usr/src/release/Makefile: release and rerelease. Attempts to use anything else will not work. Jordan From owner-freebsd-hackers Tue Jul 15 06:33:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA26444 for hackers-outgoing; Tue, 15 Jul 1997 06:33:21 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA26438 for ; Tue, 15 Jul 1997 06:33:17 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA16913; Tue, 15 Jul 1997 23:03:06 +0930 (CST) From: Michael Smith Message-Id: <199707151333.XAA16913@genesis.atrad.adelaide.edu.au> Subject: Re: make boot.flp Explodes In-Reply-To: from Jim Carroll at "Jul 15, 97 08:48:01 am" To: jim@carroll.com (Jim Carroll) Date: Tue, 15 Jul 1997 23:03:06 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jim Carroll stands accused of saying: > > I have reinstalled the OS from scratch on a clean hard drive, but each > time I try the make, I get the same error. Here is the sequence of > events I perform, and the error message: > > cd /usr/src/release > make boot.flp Nope. The only way to build the boot floppy images is "make release". You will probably want to set NOPORTS and probably NODOC as well. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jul 15 07:14:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA29041 for hackers-outgoing; Tue, 15 Jul 1997 07:14:10 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA29032 for ; Tue, 15 Jul 1997 07:14:07 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id KAA04012; Tue, 15 Jul 1997 10:14:48 -0400 (EDT) Date: Tue, 15 Jul 1997 10:14:48 -0400 (EDT) From: "David E. Cross" To: Adam David cc: freebsd-hackers@FreeBSD.ORG Subject: Re: numeric UID/GID names? In-Reply-To: <199707151030.KAA23198@ubiq.veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Jul 1997, Adam David wrote: > Are there any problems involved with giving users/groups all-numeric names, > in addition to the confusion that could exist when for instance UID number > 1234 is named 4321 (or 5678)? > > What problems might this confusion give rise to? Which are human-based > and which are programmatical? It would depend on the program... Some programs do a atoi(3) to determine if the 'value' is a UID or UNAME. The human errors should be more than enough reason to avoid this though and go with an alternate naming scheme; instead of user '4321' how about user 'u4321'? -- David Cross From owner-freebsd-hackers Tue Jul 15 07:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA29159 for hackers-outgoing; Tue, 15 Jul 1997 07:15:04 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA29145 for ; Tue, 15 Jul 1997 07:14:59 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA07223 for freebsd-hackers@FreeBSD.ORG; Tue, 15 Jul 1997 16:14:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id QAA07598; Tue, 15 Jul 1997 16:07:20 +0200 (MET DST) Message-ID: <19970715160719.ON49440@uriah.heep.sax.de> Date: Tue, 15 Jul 1997 16:07:19 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: numeric UID/GID names? References: <199707151030.KAA23198@ubiq.veda.is> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707151030.KAA23198@ubiq.veda.is>; from Adam David on Jul 15, 1997 10:30:36 +0000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > Are there any problems involved with giving users/groups all-numeric names, > in addition to the confusion that could exist when for instance UID number > 1234 is named 4321 (or 5678)? We are running a setup at a customer's site where the login IDs are the customer IDs of the customer's customers. (:-) No problems seen so far, but the numbers are large enough to not be confused with numerical IDs. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 15 07:41:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA00795 for hackers-outgoing; Tue, 15 Jul 1997 07:41:11 -0700 (PDT) Received: from zappa.cs.uncc.edu (zappa.cs.uncc.edu [152.15.35.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA00788 for ; Tue, 15 Jul 1997 07:41:08 -0700 (PDT) Received: from (oracle.uncc.edu) by zappa.cs.uncc.edu (5.x/SMI-SVR4) id AA19815; Tue, 15 Jul 1997 10:36:11 -0400 Received: by Tue Jul 15 10:40:56 1997 (SMI-8.6/SMI-SVR4) id KAA01986; Tue, 15 Jul 1997 10:40:56 -0400 From: jlrobins@zappa.cs.uncc.edu (James Robinson) Message-Id: <199707151440.KAA01986@Tue Jul 15 10:40:56 1997> Subject: PS/2 aux port info To: hackers@freebsd.org Date: Tue, 15 Jul 1997 10:40:56 -0400 (TZ=EST5EDT) X-Mailer: ELM [version 2.4ME+ PL30 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm currently trying to get more information on the keyboard contoller / PS/2 port, in hopes of figuring out how to get the PS/2 version of the Microsoft Intellimouse to start reporting info when that mutant wheel middle button gets manipulated. Can someone kindly offer up any info about how to program the keyboard controller / PS/2 port? Thanks, James -- James Robinson Phone: (704) 547-4876 Department of Computer Science FAX: (704) 547-3516 UNC Charlotte email: jlrobins@uncc.edu Charlotte, NC 28223-0001 System Administrator From owner-freebsd-hackers Tue Jul 15 09:29:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA08445 for hackers-outgoing; Tue, 15 Jul 1997 09:29:22 -0700 (PDT) Received: from netserver.mila-inc.com (netserver.mila-inc.com [207.153.181.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA08433 for ; Tue, 15 Jul 1997 09:29:17 -0700 (PDT) Received: from eagle.mila-inc.com by netserver.mila-inc.com with ESMTP RingTwice (Mac-only); 15 Jul 97 09:28:52 UT Message-ID: <33CBA5D0.7A0CE223@mila-inc.com> Date: Tue, 15 Jul 1997 09:31:13 -0700 From: "J.B. LaRue" X-Mailer: Mozilla 4.0 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.FreeBSD.org Subject: SILO Overflow errors X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm running Hylafax on a FreeBSD 2.1.7 server with a Cyclades PCI 32 port board. I keep getting SILO over flow errors and I can't find any connection to the Cyclades board or the Hylafax software. Can anyone point me in the right direction to find an answer to my problem? jb.larue@mila-inc.com From owner-freebsd-hackers Tue Jul 15 09:36:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA08969 for hackers-outgoing; Tue, 15 Jul 1997 09:36:27 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA08961 for ; Tue, 15 Jul 1997 09:36:20 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id LAA24232; Tue, 15 Jul 1997 11:35:51 -0500 (CDT) Message-Id: <199707151635.LAA24232@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: Ada T Lim cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CD Writers (was Any 4x...) In-reply-to: Your message of "Sun, 13 Jul 1997 10:47:38 +1000." <199707130047.KAA09515@polya.blah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Jul 1997 11:35:51 -0500 From: Wm Brian McCane Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hmm, I'm not sure if anyone has tried these models in particular, but more > > or less everything seems to act like an HP or a Plasmon...if you were to > > borrow one, plug it in and make the appropriate adjustment to scsiconf.c > > so it probes right, it might work. (That's how the Phillips Cdd2600 came > > to be supported one day.) > > On this note, has anyone managed to get the matshita/panasonic 2x writer to > work? This is a fairly popular bottom-end drive that I know quite a few people > have, and I'd like to know if anyone else has started ona driver before I start > wasting blanks :) > > Ada I hate people who send me too messages, but does the work like any of the other supported devices? I haven't had time to test the different options, or the money to screw up a blank if it fails. brian From owner-freebsd-hackers Tue Jul 15 09:51:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09856 for hackers-outgoing; Tue, 15 Jul 1997 09:51:05 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA09709 for ; Tue, 15 Jul 1997 09:49:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA03613; Tue, 15 Jul 1997 09:40:09 -0700 From: Terry Lambert Message-Id: <199707151640.JAA03613@phaeton.artisoft.com> Subject: Re: IPX routing? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 15 Jul 1997 09:40:09 -0700 (MST) Cc: terry@lambert.org, jhay@mikom.csir.co.za, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199707150214.LAA13392@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 15, 97 11:44:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > All clients using Novell supplied "remote reset" (NetWare based > > remote boot protocol to boot from NetWare servers) are hard-coded > > as 802.3 clients. > > Oh. That sinks that idea; we were trying to "remote reset" clients > across the router too. Booger. > > > Yes, you can get 3rd party ROM's, but that's an additional expense. So you are using Novell supplied ROMs, apparently. > Hmm. How about getting the Netware server to gateway DHCP requests? I think you mean "bridge", not "gateway". You can do this, but at the expense of losing most of your IP router functionality. DHCP and ICMP are discussed in the same section of the Novell manual for the TCP/IP stack (at least they were). If you need more help, I'm probably not going to be too helpful; I don't have a NetWare server I can poke at right now. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 09:55:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10204 for hackers-outgoing; Tue, 15 Jul 1997 09:55:45 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA10128 for ; Tue, 15 Jul 1997 09:54:03 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA03601; Tue, 15 Jul 1997 09:37:13 -0700 From: Terry Lambert Message-Id: <199707151637.JAA03601@phaeton.artisoft.com> Subject: Re: IPX routing? To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Tue, 15 Jul 1997 09:37:13 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, jhay@mikom.csir.co.za, hackers@FreeBSD.ORG In-Reply-To: <199707150926.PAA08078@hq.icb.chel.su> from "Serge A. Babkin" at Jul 15, 97 03:26:57 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've looked ayt the Linux code and it seems to me that they > just allow the applied software to decide which encapsulation > type to use: they just fill the full IPX header (that includes > Ethernet header) in user-level software rather than in driver. > It would be not bad to make the IPX implementation more > Linux-like so it would be easy to port Netware emulators. If this is true, then they are not doing full 802.3 encapsulation for 802.3. If this code is not special cased to be IPX specific (it would seem to me that it could not be, if their IPX is in user space), then their 802.3 implementation is not useful for 802.3 packets other than IPX. This is because the IPX packets are only partially encapsulated (Novell misunderstood the 802.3 encapsulation requirements, and never corrected their implementation). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 10:08:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10926 for hackers-outgoing; Tue, 15 Jul 1997 10:08:51 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA10908 for ; Tue, 15 Jul 1997 10:08:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA03654; Tue, 15 Jul 1997 10:01:35 -0700 From: Terry Lambert Message-Id: <199707151701.KAA03654@phaeton.artisoft.com> Subject: Re: multiple run-levels (was: Re: /etc/init.d/) To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Tue, 15 Jul 1997 10:01:35 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG, syssgm@dtir.qld.gov.au In-Reply-To: <199707150416.OAA01561@ogre.dtir.qld.gov.au> from "Stephen McKay" at Jul 15, 97 02:16:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >As Terry mentioned, the concept of run-levels is sound, its just that the > >SysV implementation where '1' is single user and '2' can be something else > >and '3' is sometimes network level, etc, SUCKS > > I'm one of the (raving monster looney) objectors to the run level concept. > Even if you fix the crap that System V has, I still find the whole concept > intensely objectionable. There are reasons to have a maintenance mode, and > an operational mode, which we call single user mode and multi user mode. > There is no need for the other junk. Yes and no. IBCS2 compatability requires that the target system support run levels to correctly support IBCS2 compliant installation scripts for commercial shrink-wrapped products designed to be run on UNIX platforms. In an ideal world, everyone would share your vision (and mine) that BSD is the best OS, and they would create their software on BSD and port it to any other platform they wanted to sell it on. I think we can agree that that is not going to happen. The question becomes: "How can we take advantage of existing off-the-shelf UNIX applications". The answer is IBCS2 compliance, in the near term, and common UNIX standard, in the long term. > Terry described a complex way to use his mobile computer which boils down > to a desire to: > 1) add and remove network connections > 2) add and remove hardware > while continuing in multiuser mode. No more magic than that. This is true. I never claimed more magic was required. > Appearing and disappearing network connections can be dealt with using > some program similar to routed. No, they can't. If they can, I'd like a cookbook on how to make this happen. The problem is that there is no configuration monitor that can react to device arrival and departure events, assuming they occur in the first place. One easy conversion is from "plain old init" into "init plus some configuration management capabilities". > Adding and removing hardware will be more difficult, but won't be > handled by run states. It will have to be handled by device drivers. It's a lot easier, actually, to get arrival/departure events out of what are, essentially, plugable interfaces (docking port, PCMCIA, etc.). It can *not* be handled solely by the device drivers; a configuration monitor is required, as is a list of possible configurations, and what should occur as a result of leaving one configuration and entering another. Now it's quite possible to write a bunch of new code to handle configuration change events (including power management events). It may even be possible to do this such that you can preserve the anonymity of the NFS server from which you are mounting your presentation software package into the same place in your local FS hiearchy. By why go to this trouble when an init mechanism already exists? > Run levels suck, and I'm going to hold my breath until you all > forget about them. Fine; I never wanted run *levels* anyway. 8-). > Run states also suck, because they are too simplistic. Why consider the > presence of a network connection as different from the presence of my > window manager (say). Because ideally you'd use a single window manager so that you would not require retraining on other window managers. Window managers are also not a system configuration issue; in point of fact, they are not even a system service issue (ie: I want or don't want an HTTP service provided by my system to other systems, regardless of what the idiot user wants to run as a window manager). A network connection is different in that you don't care *how* you are connected, only that you *are* connected (hopefully by the most efficient method for a given set of possibilities). > I need different networking, I run the connect program. No. End users should not be expected to know about building and destroying network connections in order for their systems to be minimally usable. This type of thinking is why your market is small and Bill Gates market is large. > You can call these things different "states", but you don't > gain anything by coding all possible arrangements and wiring > them into a directory structure. I gain a user base, which gains me more products that I can personally run. There are good, selfish reasons for doing this as well as "bad" non-selfish reasons. 8-). > Fuzzy thinking here will just lumber us with more cruft. And a fuzzy control system will save us both more cruft and more pain. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 10:26:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA11748 for hackers-outgoing; Tue, 15 Jul 1997 10:26:37 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA11712 for ; Tue, 15 Jul 1997 10:24:50 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id XAA19286; Tue, 15 Jul 1997 23:22:22 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707151722.XAA19286@hq.icb.chel.su> Subject: Re: IPX routing? To: terry@lambert.org (Terry Lambert) Date: Tue, 15 Jul 1997 23:22:22 +0600 (ESD) Cc: msmith@atrad.adelaide.edu.au, jhay@mikom.csir.co.za, hackers@FreeBSD.ORG In-Reply-To: <199707151637.JAA03601@phaeton.artisoft.com> from "Terry Lambert" at Jul 15, 97 09:37:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I've looked ayt the Linux code and it seems to me that they > > just allow the applied software to decide which encapsulation > > type to use: they just fill the full IPX header (that includes > > Ethernet header) in user-level software rather than in driver. > > It would be not bad to make the IPX implementation more > > Linux-like so it would be easy to port Netware emulators. > > If this is true, then they are not doing full 802.3 encapsulation > for 802.3. If this code is not special cased to be IPX specific > (it would seem to me that it could not be, if their IPX is in > user space), then their 802.3 implementation is not useful for > 802.3 packets other than IPX. This is because the IPX packets > are only partially encapsulated (Novell misunderstood the 802.3 > encapsulation requirements, and never corrected their implementation). I'm not quite sure, I looked that in the NWE sources. May be the kernel then repackages the packets, I don't know. But I can say for sure that the applied program can write the port numbers and addresses right into the packet (not into the address structure or by binding) and then transfer it to kernel. -SB From owner-freebsd-hackers Tue Jul 15 10:33:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA12154 for hackers-outgoing; Tue, 15 Jul 1997 10:33:39 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12146 for ; Tue, 15 Jul 1997 10:33:34 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA15309; Tue, 15 Jul 1997 10:22:13 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015301; Tue Jul 15 17:22:03 1997 Message-ID: <33CBB12F.2F1CF0FB@whistle.com> Date: Tue, 15 Jul 1997 10:19:43 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jim Carroll CC: freebsd-hackers@FreeBSD.ORG Subject: Re: make boot.flp Explodes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jim Carroll wrote: you have to have the CVS tree available and be able to do a "make release" I fixed the directory release/floppies/boot to ba able to do it after just a "make world" but I think jordan has continued his policy of ignoring this and it's fallen out of step possibly you can 'repair this directory and use it. (If jordan HAS decided to use this separate floppy production system I appologise) > > I have been having trouble now for 5 days trying to get the stock > boot.flp make file to compile under FreeBSD 2.2.1 with absolutely no > luck. > > I have reinstalled the OS from scratch on a clean hard drive, but each > time I try the make, I get the same error. Here is the sequence of > events I perform, and the error message: > > cd /usr/src/release > make boot.flp > > ( cd /R/stage/trees/bin/dev && ls console tty ttyv0 ttyv1 ttyv2 ttyv3 > null zero *[swo]d* cuaa[01] cuaa[23] fd[01] rfd[01] cd0a mcd0a scd0a > matcd0a wcd0c rst0 rft0 rwt0 | cpio -dump /R/stage/mfsfd/dev ) > cd: can't cd to /R/stage/trees/bin/dev > *** Error code 2 > > Stop. > *** Error code 1 > > Stop > > I have been pulling my hair out on this one. I would be grateful to > anyone who can point me in the correct direction. Both I (and my > hairline) thank-you. > http://www.carroll.com | Ask about our Business Messaging Services From owner-freebsd-hackers Tue Jul 15 10:57:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13403 for hackers-outgoing; Tue, 15 Jul 1997 10:57:15 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13268 for ; Tue, 15 Jul 1997 10:55:41 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA15135; Tue, 15 Jul 1997 10:18:42 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015133; Tue Jul 15 17:18:39 1997 Message-ID: <33CBB063.237C228A@whistle.com> Date: Tue, 15 Jul 1997 10:16:19 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Serge A. Babkin" CC: Michael Smith , jhay@mikom.csir.co.za, hackers@FreeBSD.ORG Subject: Re: IPX routing? References: <199707150926.PAA08078@hq.icb.chel.su> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Serge A. Babkin wrote: > > > > I do have code that do the Novel 802.3 protocol, but it only works > > > on the ed0 type cards because I use link1 in ifconfig to set it > > > and most other cards use that for something else like switching > > > 10BT on/off. > > > > Erk. Do I take it then that it's not possible to do the 802.[23] protocols > > as well as Ethernet_II simultaneously on the same interface? > > It's possible to receive both types of frames. But how to know > which kind of encapsulation to use when you SEND the packets ? > The only way to use both encapsulations I see is to keep a table > that maps each network address to encapsulation type and fill > it using the received packets. This is done by keeping the framing type in an IPX ARP equivalent. > > I've looked ayt the Linux code and it seems to me that they > just allow the applied software to decide which encapsulation > type to use: they just fill the full IPX header (that includes > Ethernet header) in user-level software rather than in driver. > It would be not bad to make the IPX implementation more > Linux-like so it would be easy to port Netware emulators. > > -SB From owner-freebsd-hackers Tue Jul 15 11:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA13867 for hackers-outgoing; Tue, 15 Jul 1997 11:05:56 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA13858 for ; Tue, 15 Jul 1997 11:05:53 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA29930; Tue, 15 Jul 1997 12:02:06 -0600 (MDT) Date: Tue, 15 Jul 1997 12:02:06 -0600 (MDT) Message-Id: <199707151802.MAA29930@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: syssgm@dtir.qld.gov.au (Stephen McKay), freebsd-hackers@freebsd.org Subject: Re: multiple run-levels (was: Re: /etc/init.d/) In-Reply-To: <199707151701.KAA03654@phaeton.artisoft.com> References: <199707150416.OAA01561@ogre.dtir.qld.gov.au> <199707151701.KAA03654@phaeton.artisoft.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > IBCS2 compatability requires that the target system support run levels > to correctly support IBCS2 compliant installation scripts for commercial > shrink-wrapped products designed to be run on UNIX platforms. I and others have run lots of 'shrink-wrapped' software, and none of them required 'run-levels' to work, though they did require the ability to start/stop processes (which is independent of run-levels). Also, you're 'docked/undocked' run-level requirement is a straw man. All of your configuration is completely un-related to run-levels. Nate From owner-freebsd-hackers Tue Jul 15 11:27:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15228 for hackers-outgoing; Tue, 15 Jul 1997 11:27:46 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA15222 for ; Tue, 15 Jul 1997 11:27:41 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id OAA27127; Tue, 15 Jul 1997 14:27:27 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id OAA03925; Tue, 15 Jul 1997 14:27:26 -0400 Date: Tue, 15 Jul 1997 14:27:23 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <19970715101231.JO07295@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Jul 1997, J Wunsch wrote: > As Chuck Robey wrote: > > > I think, Brandon, that you're wrong. The gimp software uses SYSVSHM, not > > the port. > > Sure. But why not adding a small `patch' that catches SIGSYS, and > exits cleanly telling the user to include SYSVSHM into her kernel? > (That's the same way the XFree86 servers use to disable MIT-SHM.) I think that's great, but it was the XFree86 folks who did that, not the FreeBSD porter. If FreeBSD porters had to patch the software to eliminate bugs, there'd be nearly no ports. Such things should be forwarded to the software authors. > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Tue Jul 15 11:55:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA16942 for hackers-outgoing; Tue, 15 Jul 1997 11:55:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA16937 for ; Tue, 15 Jul 1997 11:55:57 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03861; Tue, 15 Jul 1997 11:48:03 -0700 From: Terry Lambert Message-Id: <199707151848.LAA03861@phaeton.artisoft.com> Subject: Re: multiple run-levels (was: Re: /etc/init.d/) To: nate@mt.sri.com (Nate Williams) Date: Tue, 15 Jul 1997 11:48:03 -0700 (MST) Cc: terry@lambert.org, syssgm@dtir.qld.gov.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707151802.MAA29930@rocky.mt.sri.com> from "Nate Williams" at Jul 15, 97 12:02:06 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > IBCS2 compatability requires that the target system support run levels > > to correctly support IBCS2 compliant installation scripts for commercial > > shrink-wrapped products designed to be run on UNIX platforms. > > I and others have run lots of 'shrink-wrapped' software, and none of > them required 'run-levels' to work, though they did require the ability > to start/stop processes (which is independent of run-levels). And you had to manually comprehend and write equivalents for the scripts that would have been installed. And the installation was not automatic, since we don't have IBCS2 compliant package management tools. Try installing the IBCS2 Lotus 1-2-3 (as one example). As far as starting or stopping servers, try installing an IBCS2 Sybase database server without installing the correct startup scripts into the rc3.d directory. > Also, you're 'docked/undocked' run-level requirement is a straw man. > All of your configuration is completely un-related to run-levels. The configuration is related to run *states*. The hardware can be *run* in several *states*, which *could* be represented by seperate run states. It is not a strawman, it is simply not the soloution you personally would choose (apparently). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 11:59:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA17149 for hackers-outgoing; Tue, 15 Jul 1997 11:59:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA17143 for ; Tue, 15 Jul 1997 11:59:25 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA03875; Tue, 15 Jul 1997 11:51:28 -0700 From: Terry Lambert Message-Id: <199707151851.LAA03875@phaeton.artisoft.com> Subject: Re: no SYSVSHM in GENERIC now.. To: chuckr@glue.umd.edu (Chuck Robey) Date: Tue, 15 Jul 1997 11:51:28 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Jul 15, 97 02:27:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Sure. But why not adding a small `patch' that catches SIGSYS, and > > exits cleanly telling the user to include SYSVSHM into her kernel? > > (That's the same way the XFree86 servers use to disable MIT-SHM.) > > I think that's great, but it was the XFree86 folks who did that, not the > FreeBSD porter. If FreeBSD porters had to patch the software to eliminate > bugs, there'd be nearly no ports. Such things should be forwarded to the > software authors. The software authors, not unreasonably, expect the system calls required for the software to function, to exist. If a particular port of the software can potentially be run on a platform where the calls may not exist, then it is the job of that port to resolve the missing calls. Preferably, the OS will demand-load the facilities backing the call, via a demand-loaded LKM. Alternately, the porter should patch the software to run in the new environment, and hope the originators of the code adopt his patch. Either way, while the originators have not adopted the patch, it's the porters responsibility to ensure that it is part of the port. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 12:05:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17552 for hackers-outgoing; Tue, 15 Jul 1997 12:05:24 -0700 (PDT) Received: from hwcn.org (main.hwcn.org [199.212.94.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA17540 for ; Tue, 15 Jul 1997 12:05:20 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id PAA06071; Tue, 15 Jul 1997 15:05:37 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id PAA10411; Tue, 15 Jul 1997 15:05:50 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Tue, 15 Jul 1997 15:05:49 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Chuck Robey cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Jul 1997, Chuck Robey wrote: > I think that's great, but it was the XFree86 folks who did that, not the > FreeBSD porter. If FreeBSD porters had to patch the software to eliminate > bugs, there'd be nearly no ports. Such things should be forwarded to the > software authors. It was written for a SysV system that includes SYSVSHM. It was ported to a BSD system that does not (normally) include SYSVSHM. At what point in the process did it break? -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Tue Jul 15 12:07:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17684 for hackers-outgoing; Tue, 15 Jul 1997 12:07:58 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA17679 for ; Tue, 15 Jul 1997 12:07:54 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA00376; Tue, 15 Jul 1997 13:03:59 -0600 (MDT) Date: Tue, 15 Jul 1997 13:03:59 -0600 (MDT) Message-Id: <199707151903.NAA00376@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), syssgm@dtir.qld.gov.au, freebsd-hackers@freebsd.org Subject: Re: multiple run-levels (was: Re: /etc/init.d/) In-Reply-To: <199707151848.LAA03861@phaeton.artisoft.com> References: <199707151802.MAA29930@rocky.mt.sri.com> <199707151848.LAA03861@phaeton.artisoft.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > IBCS2 compatability requires that the target system support run levels > > > to correctly support IBCS2 compliant installation scripts for commercial > > > shrink-wrapped products designed to be run on UNIX platforms. > > > > I and others have run lots of 'shrink-wrapped' software, and none of > > them required 'run-levels' to work, though they did require the ability > > to start/stop processes (which is independent of run-levels). > > And you had to manually comprehend and write equivalents for > the scripts that would have been installed. Sort of, but they are un-related to run-levels. > And the installation was not automatic, since we don't have IBCS2 > compliant package management tools. None of the packages I've used have used the 'package' tools. Most use cpio. > As far as starting or stopping servers, try installing an IBCS2 > Sybase database server without installing the correct startup > scripts into the rc3.d directory. Again, this isn't an issue of run-levels, but of startup script support. > > Also, you're 'docked/undocked' run-level requirement is a straw man. > > All of your configuration is completely un-related to run-levels. > > The configuration is related to run *states*. The hardware can be > *run* in several *states*, which *could* be represented by seperate > run states. No, they are not 'states'. A state is something that you transition to/from, and very few of your configurations are actually 'states' that are transitioned to/from. Either you're undocked, or you're not. You don't transition only from 'docked/undocked', but you *are* either docked/undocked. Read state theory, and then get back to me about 'run state/levels'. 'docked/undocked' is a configuration, 'networked ethernet/networked serial/off-the-net' are other configurations, but there is no simple 'transition' where you always go from one state to the next when moving around. You jump all over the place, so states is simply the wrong paradigm. (I always like bringing up that word.) Nate From owner-freebsd-hackers Tue Jul 15 12:09:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA17808 for hackers-outgoing; Tue, 15 Jul 1997 12:09:05 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA17775 for ; Tue, 15 Jul 1997 12:08:42 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id BAA15546; Wed, 16 Jul 1997 01:07:24 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707151907.BAA15546@hq.icb.chel.su> Subject: hot plugging & other sysV stuff To: terry@lambert.org (Terry Lambert) Date: Wed, 16 Jul 1997 01:07:23 +0600 (ESD) Cc: syssgm@dtir.qld.gov.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707151701.KAA03654@phaeton.artisoft.com> from "Terry Lambert" at Jul 15, 97 10:01:35 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Adding and removing hardware will be more difficult, but won't be > > handled by run states. It will have to be handled by device drivers. > > It's a lot easier, actually, to get arrival/departure events out > of what are, essentially, plugable interfaces (docking port, PCMCIA, > etc.). > > It can *not* be handled solely by the device drivers; a configuration > monitor is required, as is a list of possible configurations, and > what should occur as a result of leaving one configuration and > entering another. By the way, the next release of SysV from SCO will include the support for hot plug cards. They have added a driver call to transfer the system control events (before this) and now they added the configure/unconfigure functions to it. Another interesting thing they have is driver interface versioning and version dependent linking according to the specified version. By the way, they got rid of the off_t in the driver calls to make the drivers independent from it to allow it to change easily in the next versions. -SB From owner-freebsd-hackers Tue Jul 15 12:12:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA18051 for hackers-outgoing; Tue, 15 Jul 1997 12:12:41 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA18036 for ; Tue, 15 Jul 1997 12:12:33 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id VAA18020; Tue, 15 Jul 1997 21:12:05 +0200 (SAT) From: John Hay Message-Id: <199707151912.VAA18020@zibbi.mikom.csir.co.za> Subject: Re: IPX routing? In-Reply-To: <33CBB063.237C228A@whistle.com> from Julian Elischer at "Jul 15, 97 10:16:19 am" To: julian@whistle.com (Julian Elischer) Date: Tue, 15 Jul 1997 21:12:05 +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 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > > > I do have code that do the Novel 802.3 protocol, but it only works > > > > on the ed0 type cards because I use link1 in ifconfig to set it > > > > and most other cards use that for something else like switching > > > > 10BT on/off. > > > > > > Erk. Do I take it then that it's not possible to do the 802.[23] protocols > > > as well as Ethernet_II simultaneously on the same interface? > > > > It's possible to receive both types of frames. But how to know > > which kind of encapsulation to use when you SEND the packets ? > > The only way to use both encapsulations I see is to keep a table > > that maps each network address to encapsulation type and fill > > it using the received packets. > > This is done by keeping the framing type in an IPX ARP equivalent. > And how do you handle RIP and SAP broadcasts? There may be more than one router on that segment and they may not use the same framing, eg. two other routers, one using 802.3 and the other Ethernet_II. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-hackers Tue Jul 15 12:28:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19067 for hackers-outgoing; Tue, 15 Jul 1997 12:28:55 -0700 (PDT) Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA19046; Tue, 15 Jul 1997 12:28:46 -0700 (PDT) Received: from janus by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020) id ; Tue, 15 Jul 1997 22:25:04 +0200 with ESMTP X-Ncc-Regid: de.netcologne Message-ID: <33CBCF59.6944D32C@netcologne.de> Date: Tue, 15 Jul 1997 21:28:25 +0200 From: Richard Cochius Reply-To: richard.cochius@netcologne.de Organization: Media Connect Cologne X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: "\"'freebsd-bugs@freebsd.org'\"" , "freebsd-chat@FreeBSD.ORG" , "freebsd-current@FreeBSD.ORG" , "freebsd-multimedia@FreeBSD.ORG" , "freebsd-questions@FreeBSD.ORG" , "hackers@FreeBSD.ORG" , "owner-hackers@FreeBSD.ORG" , "questions@FreeBSD.ORG" Subject: unsubscribe X-Priority: 3 (Normal) Content-Type: multipart/mixed; boundary="------------A49C1ABE0E75DBD5710EBE03" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------A49C1ABE0E75DBD5710EBE03 Content-Type: text/plain; charset=us-ascii Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit unsubscribe --------------A49C1ABE0E75DBD5710EBE03 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Richard Cochius Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Richard Cochius n: Cochius;Richard org: Media Connect Cologne adr: ;;;;;; email;internet: richard.cochius@netcologne.de tel;work: tel;fax: tel;home: x-mozilla-cpt: ;0 x-mozilla-html: FALSE end: vcard --------------A49C1ABE0E75DBD5710EBE03-- From owner-freebsd-hackers Tue Jul 15 12:33:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19549 for hackers-outgoing; Tue, 15 Jul 1997 12:33:17 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19544 for ; Tue, 15 Jul 1997 12:33:11 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA15717; Tue, 15 Jul 1997 10:30:54 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015708; Tue Jul 15 17:30:47 1997 Message-ID: <33CBB33B.7DE14518@whistle.com> Date: Tue, 15 Jul 1997 10:28:27 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Jim Carroll , freebsd-hackers@FreeBSD.ORG Subject: Re: make boot.flp Explodes References: <743.868972674@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > I have been having trouble now for 5 days trying to get the stock > > boot.flp make file to compile under FreeBSD 2.2.1 with absolutely no > > luck. > > > > I have reinstalled the OS from scratch on a clean hard drive, but each > > time I try the make, I get the same error. Here is the sequence of > > events I perform, and the error message: > > > > cd /usr/src/release > > make boot.flp > > Heh. This target is not meant to be run stand-alone; you MUST run it > as part of the release target. To put it another way, there are only > two supported targets in /usr/src/release/Makefile: release and > rerelease. Attempts to use anything else will not work. > > Jordan Jordan this is why I made the 'floppies' directory WHY WHY WHY WHY WHY do you INSIST on not using it? it DOESN'T require a Make release (which most people can't do) only a "Make world" (and vn support) (or floppy I guess) it's fallen WAY WAY WAY out of date because I can't spend the time keeping the crunch config file up to date with your continued changes but it always works fine for me wheneve I check it.. why do you keep perpetuating this "impossible to use" (for most people) feature? From owner-freebsd-hackers Tue Jul 15 12:34:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19639 for hackers-outgoing; Tue, 15 Jul 1997 12:34:36 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19634 for ; Tue, 15 Jul 1997 12:34:33 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id MAA28885 for ; Tue, 15 Jul 1997 12:34:31 -0700 (PDT) Date: Tue, 15 Jul 1997 12:34:31 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: What is IdlePTD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying to get some BSDI software running under FreeBSD, and it barfs with a segmenatation fault. GDB on the core file says: kernel symbol 'IdlePTD' not found. In words of < 15 syllables, what the heck does that mean for me? From owner-freebsd-hackers Tue Jul 15 13:11:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA21564 for hackers-outgoing; Tue, 15 Jul 1997 13:11:38 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21556 for ; Tue, 15 Jul 1997 13:11:30 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA20172; Tue, 15 Jul 1997 13:11:53 -0700 (PDT) Message-Id: <199707152011.NAA20172@implode.root.com> To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: What is IdlePTD? In-reply-to: Your message of "Tue, 15 Jul 1997 12:34:31 PDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 15 Jul 1997 13:11:52 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm trying to get some BSDI software running under FreeBSD, and >it barfs with a segmenatation fault. > >GDB on the core file says: > >kernel symbol 'IdlePTD' not found. > >In words of < 15 syllables, what the heck does that mean for me? IdlePTD should only be referenced when using gdb -k (kernel debugging). It's the address of the page table directory when "idle". -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 15 13:28:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22277 for hackers-outgoing; Tue, 15 Jul 1997 13:28:41 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA22271 for ; Tue, 15 Jul 1997 13:28:35 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0woECx-0000hj-00; Tue, 15 Jul 1997 14:28:27 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: aha1522 ?? Cc: hackers@freefall.freebsd.org In-reply-to: Your message of "Tue, 15 Jul 1997 09:37:47 +0200." <19970715093747.OA57762@uriah.heep.sax.de> References: <19970715093747.OA57762@uriah.heep.sax.de> <199707141943.OAA07339@beowulf.utmb.edu> Date: Tue, 15 Jul 1997 14:28:27 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <19970715093747.OA57762@uriah.heep.sax.de> J Wunsch writes: : Unless you volunteer to change it, probably. Even if the driver were : better, the AIC6[23]60 is a PIO-mode chip, which makes it suffering : the same performance vs. CPU-load problems like IDE. If someone will tell me what is wrong, or at least how to recreate the problems, I will take a look at it. I have the hw docs on the 6360, but noothing on the 6260, or even diffs between the two. And my 1522A works great right now. I've not seen any major problems with it. My friend has a 1510A (or something else that has the 6360 on it) and he's able to do cdrom w/o major problems. I've never been able to get my 1522 to work (which has the 6260), however. Won't even boot. Also, even though the driver hasn't change much at all since the 2.1 days, some versions of FreeBSD seem to be happier with it than others. I had a 2.1.7 boot disk love it, when the 2.1.5 disk hated it, and there were no deltas that I could find between the two. OpenBSD's driver has had the same problem with the cards that I have here. Warner From owner-freebsd-hackers Tue Jul 15 13:31:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22475 for hackers-outgoing; Tue, 15 Jul 1997 13:31:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA22470 for ; Tue, 15 Jul 1997 13:31:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03987; Tue, 15 Jul 1997 13:22:44 -0700 From: Terry Lambert Message-Id: <199707152022.NAA03987@phaeton.artisoft.com> Subject: Re: multiple run-levels (was: Re: /etc/init.d/) To: nate@mt.sri.com (Nate Williams) Date: Tue, 15 Jul 1997 13:22:43 -0700 (MST) Cc: terry@lambert.org, nate@mt.sri.com, syssgm@dtir.qld.gov.au, freebsd-hackers@freebsd.org In-Reply-To: <199707151903.NAA00376@rocky.mt.sri.com> from "Nate Williams" at Jul 15, 97 01:03:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > The configuration is related to run *states*. The hardware can be > > *run* in several *states*, which *could* be represented by seperate > > run states. > > No, they are not 'states'. A state is something that you transition > to/from, and very few of your configurations are actually 'states' that > are transitioned to/from. Either you're undocked, or you're not. You > don't transition only from 'docked/undocked', but you *are* either > docked/undocked. This is silly; are you claiming that I don't "dock" and "undock", that my machine is only ever turned on when I am "docked" or "undocked" instead? This is patently false. It's also generally false for the use of PCMCIA cards to provide cellular modem, ethernet, or IR network connections. > Read state theory, and then get back to me about 'run state/levels'. You are incorrectly claiming that state transitions are not trappable events. > 'docked/undocked' is a configuration, 'networked ethernet/networked > serial/off-the-net' are other configurations, but there is no simple > 'transition' where you always go from one state to the next when moving > around. You jump all over the place, so states is simply the wrong > paradigm. (I always like bringing up that word.) There is no "simple" transition because the software to make it simple never gets into the tree, mostly because of idiotic arguments like this one. "Oh, this is the way it has always been, and even though it is admittedly shitty, we fear change and are comforted in our backwardness by the lack of labor necessary to remain here". Bah Humbug. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 13:35:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22736 for hackers-outgoing; Tue, 15 Jul 1997 13:35:41 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA22727 for ; Tue, 15 Jul 1997 13:35:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA03997; Tue, 15 Jul 1997 13:23:57 -0700 From: Terry Lambert Message-Id: <199707152023.NAA03997@phaeton.artisoft.com> Subject: Re: hot plugging & other sysV stuff To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Tue, 15 Jul 1997 13:23:57 -0700 (MST) Cc: terry@lambert.org, syssgm@dtir.qld.gov.au, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707151907.BAA15546@hq.icb.chel.su> from "Serge A. Babkin" at Jul 16, 97 01:07:23 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > By the way, the next release of SysV from SCO will include the support > for hot plug cards. [ ... ] I know. I'm not claiming I invented the stuff... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 14:07:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA24359 for hackers-outgoing; Tue, 15 Jul 1997 14:07:02 -0700 (PDT) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA24353 for ; Tue, 15 Jul 1997 14:06:58 -0700 (PDT) Received: from suburbia.net (suburbia.net [198.142.2.24]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id OAA15681 for ; Tue, 15 Jul 1997 14:10:56 -0700 (PDT) Received: (qmail 5879 invoked by uid 110); 15 Jul 1997 21:05:05 -0000 From: proff@suburbia.net MBOX-Line: From richard@a42.deep-thought.org Tue Jul 15 14:13:43 1997 remote from suburbia.net Delivered-To: proff@suburbia.net Received: (qmail 15999 invoked from network); 15 Jul 1997 14:13:42 -0000 Received: from a42.deep-thought.org (203.4.184.227) by suburbia.net with SMTP; 15 Jul 1997 14:13:42 -0000 Received: from a42.deep-thought.org ([127.0.0.1]) by a42.deep-thought.org with esmtp id m0wo8O7-0024wkC (Debian Smail-3.2 1996-Jul-4 #2); Wed, 16 Jul 1997 00:15:35 +1000 (EST) Message-Id: X-Mailer: exmh version 1.6.9 8/22/96 To: proff@suburbia.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Jul 1997 00:15:35 +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ------- Forwarded Message >From debian-devel-request@lists.debian.org Fri Jul 11 07:42:24 1997 Return-Path: Received: from debian.novare.net ([205.229.104.5]) by a42.deep-thought.org with smtp id m0wmQyi-0024wkC (Debian Smail-3.2 1996-Jul-4 #2); Fri, 11 Jul 1997 07:42:20 +1000 (EST) Received: (qmail 13197 invoked by uid 38); 10 Jul 1997 22:38:58 -0000 Resent-Date: 10 Jul 1997 22:38:58 -0000 Resent-Cc: recipient list not shown: ; X-Envelope-Sender: jim@jimpick.com Message-Id: <199707102138.OAA27289@fleming.jimpick.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: debian-devel@lists.debian.org Subject: GNU Win32? Not anymore. Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_876665148P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 10 Jul 1997 14:38:40 -0700 From: Jim Pick Resent-Message-ID: <"x8pCy.0.wD3.2IMnp"@debian> Resent-From: debian-devel@lists.debian.org X-Mailing-List: archive/latest/5195 X-Loop: debian-devel@lists.debian.org Precedence: list Resent-Sender: debian-devel-request@lists.debian.org - --==_Exmh_876665148P Content-Type: text/plain; charset=us-ascii Well, at least I didn't spend too much time trying to get dpkg to run on "GNU Win32"... As I was saying before - another "almost-free" license to stick on the trophy shelf beside the Troll Tech license. I'm particularily disturbed by Cygnus' concept of "Free Sofware". Cheers, - Jim - ------- Forwarded Message Subject: Revised Cygwin32 licensing terms To: gnu-win32@cygnus.com Date: Tue, 8 Jul 1997 16:58:37 -0700 (PDT) From: gordoni@cygnus.com (Gordon Irlam) We have revised the licensing terms on Cygwin32. Previously Cygwin32 was licensed under the GPL. This restricted the use of Cygwin32 in proprietary software. The new license allows Cygwin32 to be used in both free and proprietary software, except by direct competitors of Cygnus. Details of the new license are available from the GNU Win32 home page: http://www.cygnus.com/misc/gnu-win32/ We haven't yet built a new release, but when we do, we will be incorporating the new licensing terms into it. It has been tricky for us to figure out the details of the Cygwin32 license. This is because Cygwin32 includes both a set of applications, and a set of library code developers include with the code they have written. The original license for Cygwin32 was the FSF Library GPL. However, we found the Library GPL went to far in enabling Cygnus' business competitors to take and benefit from the work we had performed on Cygwin32, without contributing anything back in return. As a result we decided to switch to licensing Cygwin32 under the GPL. Unfortunately, we then found a lot of people who would otherwise have been interested in using Cygwin32 were unwilling to do so, because they were not willing to license their code under the GPL. We are now attempting to find a balance somewhere between the two previous licenses we tried. The new licensing terms for Cygwin32 permits anyone to make use of Cygwin32 without adhering to the GPL, and without being required to make their sources available, provided that in so doing they are not attempting to directly compete with Cygnus. The reason we decided it was necessary to prevent the use of Cygwin32 by companies that are competing directly with Cygnus is explained below. Cygnus specializes in the provision of development tools for embedded systems. Cygnus is responsible for perhaps 80% of all on going GCC development, and 95% of all GDB development. We commercialize our development efforts through our GNUPro compiler tool chain. Other people and organizations contribute to, and benefits from our work. We have found that some of our embedded systems competitors have taken the work we have publically released and then are using it to compete directly with us. These companies typically do not contribute back to the ongoing development of GCC. Several examples follow. Taos Systems uses GCC as the compiler for their embedded operating system, but are not involved in the ongoing maintenance of GCC, and haven't made any of the modifications they have made to GCC publicly available. Wind River, a major embedded systems developer, with a market valuation of around $1100m, makes heavy uses of the GNU tools including GCC, and even has a proprietary graphical front end to GDB (that has been designed in such a way as to get around the GPL), but they currently don't contribute anything to the ongoing development of any of GCC and GDB tools. Tao Mountain (unrelated to Taos Systems) did a port of GCC for IDT to the IDT MIPS R5000, but have never merged their sources back with the FSF. We find ourselves at a competitive disadvantage relative to these companies because these companies manage to avoid the software development costs Cygnus has to pay. We want to make Cygwin32 widely available, because we want to maximum number of people that have access to it, and are able to extend and modify it. We believe that doing this will improve Cygwin32 both in terms of its quality and features, and you are encouraged to return any changes you make to Cygwin32 to Cygnus for inclusion in a future release. On the other hand we feel our direct competitors in the embedded tools space should not be able to take Cygwin32, which we developed, and use it to compete directly with us. We hope the new Cygwin32 licensing terms will meet our goals. Gordon Irlam (gordoni@cygnus.com) Technical Product Manager Cygnus Solutions - - - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help". - ------- End of Forwarded Message - --==_Exmh_876665148P Content-Type: application/pgp-signature - -----BEGIN PGP MESSAGE----- Version: 2.6.3a iQCVAwUBM8VWXuQz770qyIfJAQHz+AP+L7T4O6tYYN9JdvvuSn48cFwJxxULaSQT x6wRHBBrLxD0BkaZS5Y8VzaxJfA49HpzuCM+MAjy8471YhwXNPXXu5nUwn3mEgLH HT2f9VGGV/MZBTV16SDv8AzLv+DpQ+AykqHf4RZbTmJ8+oHrh4PkJoxW1Lcaed5D HzDIClrxwA8= =GNYB - -----END PGP MESSAGE----- - --==_Exmh_876665148P-- - -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to debian-devel-request@lists.debian.org . Trouble? e-mail to templin@bucknell.edu . ------- End of Forwarded Message From owner-freebsd-hackers Tue Jul 15 14:58:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26688 for hackers-outgoing; Tue, 15 Jul 1997 14:58:08 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA26675 for ; Tue, 15 Jul 1997 14:58:05 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA01869; Tue, 15 Jul 1997 15:54:19 -0600 (MDT) Date: Tue, 15 Jul 1997 15:54:19 -0600 (MDT) Message-Id: <199707152154.PAA01869@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), syssgm@dtir.qld.gov.au, freebsd-hackers@freebsd.org Subject: Re: multiple run-levels (was: Re: /etc/init.d/) In-Reply-To: <199707152022.NAA03987@phaeton.artisoft.com> References: <199707151903.NAA00376@rocky.mt.sri.com> <199707152022.NAA03987@phaeton.artisoft.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert writes: > > > *run* in several *states*, which *could* be represented by seperate > > > run states. > > > > No, they are not 'states'. A state is something that you transition > > to/from, and very few of your configurations are actually 'states' that > > are transitioned to/from. Either you're undocked, or you're not. You > > don't transition only from 'docked/undocked', but you *are* either > > docked/undocked. > > This is silly; are you claiming that I don't "dock" and "undock", > that my machine is only ever turned on when I am "docked" or > "undocked" instead? No, I'm stating that you don't transition from one state to the other the same way everytime. You can move from 'undocked w/serial networking' to 'docked w/ethernet networking', *OR* you can move from 'undocked w/serial networking' to 'docked w/serial networking'. There is no 'state machine' that describes the list of states. Instead of states you have a jumbled mess of configuration, which doesn't map well with 'run states'. As always, you've got a hammer, and everything in the world looks like a nail to you again. The solution you propose is not remotely applicable to the problem faced. Every problems with FreeBSD is resolvable to: 1) FS layering 2) Run levels 3) VM86 mode 4) CVS tree locking 5) Not letting anyone who shows interest hacking the code. Ie; all of Terry's abilities resolve to something in the above class, so all of the problems must be solvable by the above solutions. Nate From owner-freebsd-hackers Tue Jul 15 14:58:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA26761 for hackers-outgoing; Tue, 15 Jul 1997 14:58:38 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA26745 for ; Tue, 15 Jul 1997 14:58:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00460; Tue, 15 Jul 1997 14:57:32 -0700 From: Terry Lambert Message-Id: <199707152157.OAA00460@phaeton.artisoft.com> Subject: Re: IPX routing? To: jhay@mikom.csir.co.za (John Hay) Date: Tue, 15 Jul 1997 14:57:32 -0700 (MST) Cc: julian@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199707151912.VAA18020@zibbi.mikom.csir.co.za> from "John Hay" at Jul 15, 97 09:12:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This is done by keeping the framing type in an IPX ARP equivalent. > > And how do you handle RIP and SAP broadcasts? There may be more than > one router on that segment and they may not use the same framing, eg. > two other routers, one using 802.3 and the other Ethernet_II. As of Netware 3.1, an "internal wire segment" was defined for all routers. Effectively, prior to this, the architecture was: server | | | | net net segment segment 1 2 After this change, the architecture is: server | | --+----+---+--Internal segment | | | | net net segment segment 1 2 Effectively, then, broadcasts are handled as multicasts, and the hop count incremented accordingly (the server broadcasts to the internal segment, and it is "hopped" to each external segment attacked to the machine). A NetWare router, by default, will forward broadcasts up to 16 hops, after which time packets will be dropped. A correct IPX implementation, then, has an "internal network number" which identifies the server, and an "external network number" for each card which identifies the wire segment to which the card has been attached. The default convention for coexistance of IPX and IP networks is to assign the four tuple IP address of the card, minus the netmask, to each card, and the IP address of the machine to the internal segment (any IP address unique to the machine will do). If your IPX stack on your router does not match this description, your implementation is broken. The relevant documents are downloadable from the Utah State University archives (one of the usu.edu servers; I forget which one exactly... use Yahoo or Altavista to find out which one). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 15 15:03:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27101 for hackers-outgoing; Tue, 15 Jul 1997 15:03:01 -0700 (PDT) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27094 for ; Tue, 15 Jul 1997 15:02:55 -0700 (PDT) Received: from saturn.ajc.state.net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with SMTP id RAA25623 for ; Tue, 15 Jul 1997 17:01:32 -0500 (CDT) Received: by localhost with Microsoft MAPI; Tue, 15 Jul 1997 17:00:39 -0500 Message-ID: <01BC9140.9F77E320.Al.Johnson@AJC.State.Net> From: Al Johnson To: "'hackers@freebsd.org'" Subject: RE: What I consider and odd install Date: Tue, 15 Jul 1997 17:00:38 -0500 Organization: Al Johnson Consulting 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Monday, July 14, 1997 1:33 AM, Tom Samplonius [SMTP:tom@sdf.com] wrote: > > On Mon, 14 Jul 1997, Michael Smith wrote: > > > Tom Samplonius stands accused of saying: > > > > > > How about enabling BIOS support for more drives? Boot easy should see > > > the other drives, if the bios does, unless there is a design limitation > > > in > > > boot easy. > > > > Booteasy, especially 1.7, is very old. It dates from the days when > > most biossen only supported two drives (as previously mentioned). > > > > There is no correct way of discovering whether the BIOS supports more > > drives. > > > > You're invited to find the booteasy source code and improve on it. 8) > > Strange... booteasy was a rather new addition to FreeBSD (2.0, 2.05, or > something... well that is "somewhat new"). Adaptec 2940 has had the > "bios support for more than two drives" option for a long time. My Adaptec 2940 is not very old, acquired sometime around jan-feb 97 and I do not have a "bios support for more than two drives" option. Hmm, maybe in need of a EPROM update on the adaptec? From owner-freebsd-hackers Tue Jul 15 15:08:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27336 for hackers-outgoing; Tue, 15 Jul 1997 15:08:18 -0700 (PDT) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA27331 for ; Tue, 15 Jul 1997 15:08:11 -0700 (PDT) Received: from saturn.ajc.state.net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with SMTP id RAA25632; Tue, 15 Jul 1997 17:06:38 -0500 (CDT) Received: by localhost with Microsoft MAPI; Tue, 15 Jul 1997 17:05:46 -0500 Message-ID: <01BC9141.56250620.Al.Johnson@AJC.State.Net> From: Al Johnson To: "'Chuck Robey'" Cc: "'hackers@freebsd.org'" Subject: RE: What I consider and odd install Date: Tue, 15 Jul 1997 17:05:45 -0500 Organization: Al Johnson Consulting 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sunday, July 13, 1997 11:42 PM, Chuck Robey [SMTP:chuckr@glue.umd.edu] wrote: > On Sun, 13 Jul 1997, Al Johnson wrote: > > > Now to the problem. I've a GW2K Pentrium Pro 180 that I want to use for > > compiles of any package. It's got a 3.8GB EIDE Disk and CDROM. I've also > > got an Adaptec 2940UW SCSI with a 1GB fixed disk, 8G tape unit, 135Syquest > > (ya I know), and 1G Jaz drive. I want FreeBSD on the Jaz drive since I > > won't be using it all the time (The machine runs mostly Win95...uggg) > > > > No matter what I do I can't get the FreeBSD boot manager to give me the > > option of booting from the JAZ drive. I've gone thru and made sure it's > > BIOS recognized. The order displayed at boot time is: C:3.8GB EIDE D:1GB > > Seagate, 82h JAZ, 83h EZ135. > > > > Any suggestions as to a solution or pointers to where I can get more info > > would be greatly appreciated. I'm really interested in seeing just how > > well FreeBSD run when it's allowed to open up an a PPro 180 with 64MB of > > memory as opposed to my 486/66 with 16MB. > > Al, on the Jaz drive, is either the FreeBSD partition marked as the active > one (via fdisk) or is bteasy installed on the Jaz drive? On your original > boot disk, bteasy requires _one_ of those two or it will refuse to > transfer control. > I've got the boot manager installed on the jaz drive but for some reason, apparently booteasy only supports 2 drives, I never get the chance to select the jaz for booting. I think this is a case where two many drives is complicating the issue. I've even gone so far as to disable the primary EIDE interface (3.8G). Booteasy still discovers the disk. I select Disk2 and it wants to boot from the CDROM. still no jaz drive in the picture. Looks like I may have to partition my 3.8G disk to boot FreeBSD. Hmm, maybe just go out and buy another EIDE drive for the primary controller and all will be well. From owner-freebsd-hackers Tue Jul 15 15:33:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28585 for hackers-outgoing; Tue, 15 Jul 1997 15:33:03 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28572 for ; Tue, 15 Jul 1997 15:32:58 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id SAA10745; Tue, 15 Jul 1997 18:32:42 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA12305; Tue, 15 Jul 1997 18:32:41 -0400 Date: Tue, 15 Jul 1997 18:32:37 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Al Johnson cc: "'hackers@freebsd.org'" Subject: RE: What I consider and odd install In-Reply-To: <01BC9141.56250620.Al.Johnson@AJC.State.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 15 Jul 1997, Al Johnson wrote: > I've got the boot manager installed on the jaz drive but for some reason, > apparently booteasy only supports 2 drives, I never get the chance to select > the jaz for booting. I think this is a case where two many drives is > complicating the issue. > > I've even gone so far as to disable the primary EIDE interface (3.8G). Booteasy > still discovers the disk. I select Disk2 and it wants to boot > from the CDROM. still no jaz drive in the picture. Looks like I may have > to partition my 3.8G disk to boot FreeBSD. Hmm, maybe just go out and buy > another EIDE drive for the primary controller and all will be well. As others have told you, bteasy only handles 2 disks. I think which two disks, in a SCSI system, is handled in order of scsi ID #, and I've juggled disks to do that in the past, but you not only have a mixed system (with both SCSI and EIDE) but you have a large load of scsi devices, and juggling ID numbers is going to involve your having to do things like inspect your /etc/fstab, to make sure it's right, else it won't find the new disks in the right place (when you change the scsi order). I don't know of a boot manager that will handle your setup easily. > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Jul 17 20:38:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24506 for hackers-outgoing; Thu, 17 Jul 1997 20:38:57 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24500 for ; Thu, 17 Jul 1997 20:38:52 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id XAA17368 for ; Thu, 17 Jul 1997 23:38:32 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id XAA15166 for ; Thu, 17 Jul 1997 23:37:55 -0400 Date: Thu, 17 Jul 1997 23:37:39 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: ppp default routes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm experimenting with ppp again. I can get it going, and all is perfectly correct, except I can't get a default route to my isp going. My machine, journey2.mat.net. is 205.252.122.116, static. The isp isd mat.net, and the machine I ppp to is earth.mat.net, at 205.252.122.1. The end of my ppp.conf entry is: set ifaddr 205.252.122.116 205.252.122.1 255.255.255.0 the ppp.linkup entry is: matppp: delete ALL add 0 0 205.252.122.1 How come I always have to add the default routing entry via a route command? It's never done for me, but I duplicate the entry in the man page just exactly. This is _not_ auto, btw. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Jul 17 20:40:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24649 for hackers-outgoing; Thu, 17 Jul 1997 20:40:18 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24644 for ; Thu, 17 Jul 1997 20:40:11 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA03649 for hackers@freebsd.org; Fri, 18 Jul 1997 13:10:08 +0930 (CST) From: Michael Smith Message-Id: <199707180340.NAA03649@genesis.atrad.adelaide.edu.au> Subject: DMI / SMBIOS ? To: hackers@freebsd.org Date: Fri, 18 Jul 1997 13:10:08 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a quick call to see if there's any interest in handling any of the DMI or SMBIOS stuff that is being noised around lately. For more in-depth details on SMBIOS, see http://www.ptltd.com/techs/specs.html Unfortuately, I don't have access to a system implementing the table-based SMBIOS data structures, so I'm interested in hearing from anyone that does, or thinks they might. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 17 21:14:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26331 for hackers-outgoing; Thu, 17 Jul 1997 21:14:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26323 for ; Thu, 17 Jul 1997 21:14:37 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA03981; Fri, 18 Jul 1997 13:44:26 +0930 (CST) From: Michael Smith Message-Id: <199707180414.NAA03981@genesis.atrad.adelaide.edu.au> Subject: Re: ppp default routes In-Reply-To: from Chuck Robey at "Jul 17, 97 11:37:39 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Fri, 18 Jul 1997 13:44:25 +0930 (CST) Cc: FreeBSD-Hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey stands accused of saying: > > How come I always have to add the default routing entry via a > route command? It's never done for me, but I duplicate the entry in the > man page just exactly. This is _not_ auto, btw. How recent is your kernel? There was some breakage in the routing code yesterday which would have hurt you here. Check that net/rtsock.c is at version 1.30. > Chuck Robey | Interests include any kind of voice or data -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 17 21:27:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26969 for hackers-outgoing; Thu, 17 Jul 1997 21:27:13 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26964 for ; Thu, 17 Jul 1997 21:27:10 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id AAA05624; Fri, 18 Jul 1997 00:27:07 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id AAA17506; Fri, 18 Jul 1997 00:27:05 -0400 Date: Fri, 18 Jul 1997 00:26:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Michael Smith cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: ppp default routes In-Reply-To: <199707180414.NAA03981@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Michael Smith wrote: > Chuck Robey stands accused of saying: > > > > How come I always have to add the default routing entry via a > > route command? It's never done for me, but I duplicate the entry in the > > man page just exactly. This is _not_ auto, btw. > > How recent is your kernel? There was some breakage in the routing code > yesterday which would have hurt you here. Check that net/rtsock.c > is at version 1.30. My kernel's about 10 days old. I stopped updating when I got caught in the CVSROOT/history messup, and only now started up again. I don't think that's the problem, but let me regenerate it all now from the fresh stuff, and complain again if it's not working tomorrow. I sure do like Satoshi's new Makefile for /usr/src, tho! > > > Chuck Robey | Interests include any kind of voice or data > > > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Jul 17 21:27:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27011 for hackers-outgoing; Thu, 17 Jul 1997 21:27:39 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA26994 for ; Thu, 17 Jul 1997 21:27:36 -0700 (PDT) Received: (qmail 505 invoked by uid 1000); 18 Jul 1997 04:21:05 -0000 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970716214222.61218@mi.uni-koeln.de> Date: Thu, 17 Jul 1997 16:35:22 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Stefan Esser Subject: Re: pcireg.h lost children... ? Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Stefan Esser; On 16-Jul-97 you wrote: ... Excellent explanation deleted ... It did, for a while, break compatability... > I did not expect drivers to actually care for the class code > or command register values of a device, since higher level > code should take care of things ... > > What are you using those values for ? In pci/dpt_pci.c: dpt_pci_probe() ... if ((dpt_id = (type & 0xffff0000) >> 16) == DPT_DEVICE_ID) { /* This one appears to belong to us, but what is it? */ class = pci_conf_read(tag, PCI_CLASS_REG); if (((class & PCI_CLASS_MASK) == PCI_CLASS_MASS_STORAGE) && ((class & PCI_SUBCLASS_MASK) == PCI_SUBCLASS_MASS_STORAGE_SCSI) ) { /* It is a SCSI storage device. How do talk to it? */ command = pci_conf_read(tag, PCI_COMMAND_STATUS_REG); if ( ((command & PCI_COMMAND_MEM_ENABLE) == 0) && ((command & PCI_COMMAND_IO_ENABLE) == 0) ) { printf("DPT: Cannot map the controller as memory, nor as I/O :-(\n"); return(NULL); } } else { printf("DPT: Device is not Mass Storage, nor SCSI controller :-(\n"); return(NULL); } command = pci_conf_read(tag, PCI_COMMAND_STATUS_REG); if ( (command & PCI_COMMAND_MASTER_ENABLE) == 0 ) { printf("DPT: BUSMASTER disabled :-(\n"); return (NULL); } And in dpt_pci_attach() ... io_base = 0; vaddr = 0; paddr = 0; data = pci_conf_read(config_id, PCI_BASEADR0); command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); if ( ((command & PCI_COMMAND_MEM_ENABLE) == 0) || (pci_map_mem(config_id, PCI_BASEADR0, &vaddr, &paddr) == 0) ) { /* Either not memory mappable or mapping failed. Try I/O mapping */ if ((command & PCI_COMMAND_IO_ENABLE) == 0 || (pci_map_port(config_id, PCI_BASEADR0, &io_base) == 0) ) { free(dpt, M_DEVBUF); printf ("dpt%d: Failed to map memory or I/O registers :-(\n", unit); return; } } Makes sense? Simon From owner-freebsd-hackers Thu Jul 17 21:28:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27108 for hackers-outgoing; Thu, 17 Jul 1997 21:28:11 -0700 (PDT) Received: from ra.bpsi.net (ra.bpsi.net [199.199.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27068; Thu, 17 Jul 1997 21:28:02 -0700 (PDT) Received: from localhost (duccini@localhost) by ra.bpsi.net (8.8.5/8.6.9) with SMTP id XAA08161; Thu, 17 Jul 1997 23:28:27 -0500 (CDT) Date: Thu, 17 Jul 1997 23:28:27 -0500 (CDT) From: "David V. Duccini" To: FreeBSD-ISP@FreeBSD.ORG cc: hackers@FreeBSD.ORG Subject: FAQ, I'm sure of it... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is there a way to set up the PPP stuff to recognize a PAP/CHAP packet and switch into PPP mode (and...while I'm at it...perform client side radius authentication?) Please, straight answers only, this relates to a driver porting job I'm doing for Multitech, and we run Livingston, CompuTone, and Chase Research terminal servers. I want to make sure that I can emulate or exceed in capability "normal" terminal servers -Duck ------------------------------------------------------------------------------- duccini@bpsi.net BackPack Software, Inc. www.backpack.com +1 612.645.7550 voice BPSI Internet Services www.bpsi.net +1 612.645.9798 fax 1.800eMail info@one800.net www.one800.net ------------------------------------------------------------------------------- From owner-freebsd-hackers Thu Jul 17 22:10:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29262 for hackers-outgoing; Thu, 17 Jul 1997 22:10:38 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29235; Thu, 17 Jul 1997 22:10:20 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id PAA26812; Fri, 18 Jul 1997 15:09:50 +1000 (EST) Date: Fri, 18 Jul 1997 15:09:49 +1000 (EST) From: "Daniel O'Callaghan" To: "David V. Duccini" cc: FreeBSD-ISP@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: FAQ, I'm sure of it... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 17 Jul 1997, David V. Duccini wrote: > > Is there a way to set up the PPP stuff to recognize a PAP/CHAP packet and > switch into PPP mode (and...while I'm at it...perform client side radius > authentication?) > > Please, straight answers only, this relates to a driver porting job I'm > doing for Multitech, and we run Livingston, CompuTone, and Chase > Research terminal servers. I want to make sure that I can emulate or > exceed in capability "normal" terminal servers See ftp.hilink.com.au:/pub/FreeBSD/pppkit.tgz Danny From owner-freebsd-hackers Fri Jul 18 05:04:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA17445 for hackers-outgoing; Fri, 18 Jul 1997 05:04:30 -0700 (PDT) Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA17437 for ; Fri, 18 Jul 1997 05:04:21 -0700 (PDT) Received: by kremvax.demos.su (8.6.13/D) from root@localhost for hackers@freebsd.org id QAA24866; Fri, 18 Jul 1997 16:03:06 +0400 Received: by vnukovo.msk.su (dMail for DOS v1.23, 15Jun94); Fri, 18 Jul 1997 16:00:09 +0100 To: hackers@freebsd.org X-Class: Fast Message-Id: Organization: Vnukovo Airlines UserID: 1D010009 Date: Fri, 18 Jul 1997 16:00:09 +0100 (MSD) From: "ìÁ×ÒÉÞÅ× äÍÉÔÒÉÊ ÷ÅÎÉÁÍÉÎÏ×ÉÞ" X-Mailer: dMail [Demos Mail for DOS v1.23] Subject: CDROM linux+bsd Lines: 8 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi great hackers! I write from Russia and have some problems with a installiung of Linux Please describe process of installing!! How can I make boot floppy disks and write system to my HDD for start installation? HELP! From owner-freebsd-hackers Fri Jul 18 05:23:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18143 for hackers-outgoing; Fri, 18 Jul 1997 05:23:13 -0700 (PDT) Received: from shell.monmouth.com (root@shell.monmouth.com [205.164.220.9]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18138 for ; Fri, 18 Jul 1997 05:23:11 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp1.monmouth.com [205.164.221.33]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id IAA02075 for ; Fri, 18 Jul 1997 08:21:13 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id IAA00359 (8.8.5/IDA-1.6 for freebsd-hackers@freebsd.org); Fri, 18 Jul 1997 08:23:07 -0400 (EDT) From: Bill Pechter Message-ID: <199707181223.IAA00359@i4got.lakewood.com> Subject: Status of PCVT To: freebsd-hackers@freebsd.org Date: Fri, 18 Jul 1997 08:23:06 -0400 (EDT) Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL19 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know the latest version avaialable of PCVT. I've been having a number of problems since I put up my new motherboard. I don't see these with syscons... I also now have a DEC LK250 keyboard -- and I'm looking to see what's needed to work in some special support for it. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hackers Fri Jul 18 06:06:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA19833 for hackers-outgoing; Fri, 18 Jul 1997 06:06:35 -0700 (PDT) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA19825 for ; Fri, 18 Jul 1997 06:06:28 -0700 (PDT) Received: from saturn.ajc.state.net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with SMTP id IAA01393 for ; Fri, 18 Jul 1997 08:06:20 -0500 (CDT) Received: by localhost with Microsoft MAPI; Fri, 18 Jul 1997 08:04:14 -0500 Message-ID: <01BC9351.2E7B5540.Al.Johnson@AJC.State.Net> From: Al Johnson To: "'hackers@freebsd.org'" Subject: Latest "stable" Date: Fri, 18 Jul 1997 08:04:12 -0500 Organization: Al Johnson Consulting 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been using cvsup to keep my sources up to date, actually to a couple different versions. Using "." as the release yields a source that won't compile with the following error: cc -O -DLIBC_SCCS -I/sys -c /usr/local/src/lib/libkvm.c -o kvm.o In file included from /sys/sys/time.h:118, from /sys/sys/user.h:44, from /usr/local/src/lib/libkvm.c:43: /usr/include/time.h:92 redifinition of 'struct timespec' I used to be a programmer but that was more than 10 years ago so I don't feel real confident diving into this. So this may be a FYI for you regulars. What I'm really after is: What is the best cvsup release to grab hold of to keep current. I see references to 3.0 but nothing in the cvsup docs or example config files refers to this, unless of course it's ".". -- Al From owner-freebsd-hackers Fri Jul 18 06:13:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20058 for hackers-outgoing; Fri, 18 Jul 1997 06:13:34 -0700 (PDT) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20050 for ; Fri, 18 Jul 1997 06:13:31 -0700 (PDT) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id WAA11757; Fri, 18 Jul 1997 22:01:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (MyJo6MMySAgpw7N2JA4Fht9v0Xomb/7f@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id WAA27432; Fri, 18 Jul 1997 22:01:57 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA11174; Fri, 18 Jul 1997 22:07:40 +0900 (JST) Message-Id: <199707181307.WAA11174@zodiac.mech.utsunomiya-u.ac.jp> To: pechter@lakewood.com cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Status of PCVT In-reply-to: Your message of "Fri, 18 Jul 1997 08:23:06 -0400." <199707181223.IAA00359@i4got.lakewood.com> References: <199707181223.IAA00359@i4got.lakewood.com> Date: Fri, 18 Jul 1997 22:07:39 +0900 From: Kazutaka YOKOTA Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Does anyone know the latest version avaialable of PCVT. > >I've been having a number of problems since I put up my new motherboard. >I don't see these with syscons... > >I also now have a DEC LK250 keyboard -- and I'm looking to see what's needed >to work in some special support for it. > >Bill What sort of problems? Which version of FreeBSD are you using? If you are using 2.2.x, you may want to try PCVT in the 3.0-current source tree. You don't need to get entire 3.0-current. You just grab files in src/sys/i386/isa/pcvt from the -current and drop them into 2.2.x... Kazu From owner-freebsd-hackers Fri Jul 18 06:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20749 for hackers-outgoing; Fri, 18 Jul 1997 06:32:44 -0700 (PDT) Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20739 for ; Fri, 18 Jul 1997 06:32:39 -0700 (PDT) Received: from rodan.UU.NET by relay2.UU.NET with ESMTP (peer crosschecked as: rodan.UU.NET [153.39.130.10]) id QQcyss27904; Fri, 18 Jul 1997 09:32:31 -0400 (EDT) Received: by rodan.UU.NET id QQcyss04068; Fri, 18 Jul 1997 09:32:19 -0400 (EDT) Date: Fri, 18 Jul 1997 09:32:19 -0400 (EDT) From: mo@UU.NET (Mike O'Dell) Message-Id: To: msmith@atrad.adelaide.edu.au Subject: SMBIOS/DMI etc Cc: hackers@freebsd.org, mo@UU.NET Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i have a new ASUS TX97-E motherboard with the DMI/SMBIOS stuff on it and it's pretty cool. the National parts which do the actual work are docuemented and everyone is using the same thing, or so it seems. the part gives you all DC voltages, fan rotation speed for each of possibly 3 fans (cpu, cabinet, and power supply), "cabinet intrusion detector", and some other stuff =mo From owner-freebsd-hackers Fri Jul 18 07:39:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA23445 for hackers-outgoing; Fri, 18 Jul 1997 07:39:11 -0700 (PDT) Received: from ns.newreach.net (root@ns.newreach.net [206.25.170.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23432 for ; Fri, 18 Jul 1997 07:39:08 -0700 (PDT) Received: from inetgw.aristar.com (inetgw.aristar.com [206.25.171.180]) by ns.newreach.net (8.8.4/8.6.9) with ESMTP id KAA20593 for ; Fri, 18 Jul 1997 10:38:52 -0400 (EDT) Message-Id: <199707181438.KAA20593@ns.newreach.net> From: "Matthew A. Gessner" To: Subject: Installation - SYSVSHM required for X??? Date: Fri, 18 Jul 1997 10:49:29 -0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, all, Why would the X servers (XF86_SVGA) give me a lot of grief about not being able to do SYSVSHM? It's not in GENERIC, but it is in LINT. Do I need to rebuild the kernel to support X??? I have a TSENG ET4000/W32 chipset, which SuperProbe gives as Super-VGA. I had X under 2.1.5-RELEASE running just fine under this chipset, although that old XF86Config file doesn't seem to work now either. I did go to XFree86.org and try to find out what was going on, and I followed their suggestions, but that didn't solve the SYSVSHM error message problem. TIA, Matt -- Matthew A. Gessner, Computer Scientist Aristar, Inc. Akron, OH 330.668.2267 FAX 330.668.2961 From owner-freebsd-hackers Fri Jul 18 08:03:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24855 for hackers-outgoing; Fri, 18 Jul 1997 08:03:37 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA24850 for ; Fri, 18 Jul 1997 08:03:33 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <52069(4)>; Fri, 18 Jul 1997 08:02:57 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Fri, 18 Jul 1997 08:02:41 -0700 To: Julian Elischer cc: hackers@freebsd.org Subject: Re: TCP bug in 2.2 In-reply-to: Your message of "Fri, 11 Jul 97 17:35:04 PDT." <33C6D138.7D55368C@whistle.com> Date: Fri, 18 Jul 1997 08:02:29 PDT From: Bill Fenner Message-Id: <97Jul18.080241pdt.177512@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try using kgdb to look at tp->t_timer[TCPT_2MSL] to see if it got set at all or if it's getting reset. Bill From owner-freebsd-hackers Fri Jul 18 08:37:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28381 for hackers-outgoing; Fri, 18 Jul 1997 08:37:04 -0700 (PDT) Received: from beowulf.utmb.edu (beowulf.utmb.edu [129.109.59.83]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA28375 for ; Fri, 18 Jul 1997 08:36:59 -0700 (PDT) Received: (from bdodson@localhost) by beowulf.utmb.edu (8.8.5/8.8.5) id KAA13685 for hackers@freebsd.org; Fri, 18 Jul 1997 10:34:30 -0500 (CDT) Date: Fri, 18 Jul 1997 10:34:30 -0500 (CDT) From: "M. L. Dodson" Message-Id: <199707181534.KAA13685@beowulf.utmb.edu> To: hackers@freebsd.org Subject: PentiumPro/II floating point "errata" impact X-Sun-Charset: US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Does anyone know if the floating point bug in PentiumPros and PentiumIIs is likely to be manifest in libm? I'm talking about the unflagged overflow when converting from floating point to integer (FIST? or some such). If it is, does anyone know whether this can be handled by code generation in the gcc backend? (The Intel web site talks about software workarounds.) I use g77 to compile chemical kinetics simulation code, just got a new PentiumPro workstation, and would like to know how likely this is to affect my results. Would not be too happy to have to compile it all to assembler, and grep out the the instruction codes :) TIA, Bud Dodson -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790 From owner-freebsd-hackers Fri Jul 18 09:02:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29983 for hackers-outgoing; Fri, 18 Jul 1997 09:02:22 -0700 (PDT) Received: from casparc.ppp.net (mail.ppp.net [194.64.12.35]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA29977 for ; Fri, 18 Jul 1997 09:02:14 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0wpFTo-000o3KC; Fri, 18 Jul 97 18:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Fri, 18 Jul 1997 17:37:20 +0200 (MET DST) (Smail-3.2.0.91 1997-Jan-14 #2 built 1997-Feb-8) Received: by bert.kts.org via sendmail with stdio id for freebsd-hackers@FreeBSD.ORG; Fri, 18 Jul 1997 17:32:11 +0200 (CEST) (Smail-3.2.0.94 1997-Apr-22 #7 built 1997-Jul-4) Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: Re: Status of PCVT In-Reply-To: <199707181223.IAA00359@i4got.lakewood.com> from Bill Pechter at "Jul 18, 97 08:23:06 am" To: pechter@lakewood.com Date: Fri, 18 Jul 1997 17:32:11 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Pechter wrote: > Does anyone know the latest version avaialable of PCVT. 3.32. About a year old. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe There is a difference between an open mind and a hole in the head From owner-freebsd-hackers Fri Jul 18 09:48:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02502 for hackers-outgoing; Fri, 18 Jul 1997 09:48:52 -0700 (PDT) Received: from bmccane.uit.net (bmccane.uit.net [208.129.189.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02413 for ; Fri, 18 Jul 1997 09:47:32 -0700 (PDT) Received: from bmccane.uit.net (localhost.mccane.com [127.0.0.1]) by bmccane.uit.net (8.8.5/8.8.5) with ESMTP id LAA17049 for ; Fri, 18 Jul 1997 11:42:18 -0500 (CDT) Message-Id: <199707181642.LAA17049@bmccane.uit.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@FreeBSD.Org Subject: Strange SCSI problem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Jul 1997 11:42:18 -0500 From: Wm Brian McCane Sender: owner-hackers@FreeBSD.Org X-Loop: FreeBSD.org Precedence: bulk Howdy, I have built `gimp' on my system, and also have built `sane'. Sane is a scanner interface program that directly accesses the SCSI `uk0' device to get data from the scanner. Anyway, to make a long story short, when I try to use `sane', it doesn't get any data from the scanner. The `scsireq_enter' returns a success status, and that there were 96 bytes read, but the buffer contains the data that was in it when the function was called. To experiment with this, I used the `scsi' command: scsi -f /dev/uk0 -c "12 0 0 0 60 0" -i 96 "i4 i4 i4 i4 i4 i4 i4 i4" It reports 96 bytes read, but the buffer contains all 0's, because the `scsi' command bzero's the buffer before calling the `scsireq_enter' function. I have looked at the kernel code, and I can't find the problem, but I assume that the data is not being copied into user space from kernel space. Any ideas? brian From owner-freebsd-hackers Fri Jul 18 09:57:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02914 for hackers-outgoing; Fri, 18 Jul 1997 09:57:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02906 for ; Fri, 18 Jul 1997 09:57:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id CAA08954; Sat, 19 Jul 1997 02:52:36 +1000 Date: Sat, 19 Jul 1997 02:52:36 +1000 From: Bruce Evans Message-Id: <199707181652.CAA08954@godzilla.zeta.org.au> To: bdodson@beowulf.utmb.edu, hackers@FreeBSD.ORG Subject: Re: PentiumPro/II floating point "errata" impact Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Does anyone know if the floating point bug in PentiumPros and PentiumIIs >is likely to be manifest in libm? I'm talking about the unflagged >overflow when converting from floating point to integer (FIST? or some >such). If it is, does anyone know whether this can be handled by code >generation in the gcc backend? (The Intel web site talks about software >workarounds.) Overflow for this conversion gives undefined behaviour in ANSI C. In FreeBSD, the default behaviour is to generate a SIGFPE. If you mask FPU exceptions, then FIST gives the result LONG_LONG_MIN for 64-bit integers and sets various exception flags. Gcc uses the 64-bit FIST for both 32-bit and 64-bit integers and mangles it to various mostly wrong values (except for calculations done at compile time, gcc acts as if it used the 32-bit FIST and mangles it to different mostly wrong values), e.g., volatile double var = 1e50; (long) 1e50 = LONG_MIN right (unsigned long) 1e50 = 0x80000000 wrong? (long) var = LONG_MIN right (unsigned long) var = 0 wrong (long long) 1e50 = 0xffffffff00000000 wrong (unsigned long long)1e50 = 0xffffffff00000000 wrong (long long) var = LONG_LONG_MIN right (unsigned long long)var = 0 wrong Errors in setting the exception flags will probably be lost in this noise. libm attempts to never generate overflows, except on purpose. I think it never generates a float -> int conversion overflow. Bruce From owner-freebsd-hackers Fri Jul 18 11:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07918 for hackers-outgoing; Fri, 18 Jul 1997 11:26:17 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA07906; Fri, 18 Jul 1997 11:26:09 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA16526 (5.67b/IDA-1.5); Fri, 18 Jul 1997 20:26:01 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA09831; Fri, 18 Jul 1997 20:25:59 +0200 (CEST) X-Face: " Date: Fri, 18 Jul 1997 20:25:58 +0200 From: Stefan Esser To: Simon Shapiro Cc: freebsd-hackers@FreeBSD.ORG, Stefan Esser Subject: Re: pcireg.h lost children... ? References: <19970716214222.61218@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Simon Shapiro on Thu, Jul 17, 1997 at 04:35:22PM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 17, Simon Shapiro wrote: [ ... new macro names for PCI classes and config register bits ... ] > It did, for a while, break compatability... Well, I'm sorry for that. But I did not expect drivers to actually use those names ... And you were warned: I left no doubt in my commit messages, that the new PCI code was a independent implementation :) > > I did not expect drivers to actually care for the class code > > or command register values of a device, since higher level > > code should take care of things ... > > > > What are you using those values for ? > > In pci/dpt_pci.c: > > dpt_pci_probe() > .... > > if ((dpt_id = (type & 0xffff0000) >> 16) == DPT_DEVICE_ID) { > /* This one appears to belong to us, but what is it? */ > class = pci_conf_read(tag, PCI_CLASS_REG); > if (((class & PCI_CLASS_MASK) == PCI_CLASS_MASS_STORAGE) && > ((class & PCI_SUBCLASS_MASK) == PCI_SUBCLASS_MASS_STORAGE_SCSI) ) { > /* It is a SCSI storage device. How do talk to it? */ > command = pci_conf_read(tag, PCI_COMMAND_STATUS_REG); > if ( ((command & PCI_COMMAND_MEM_ENABLE) == 0) > && ((command & PCI_COMMAND_IO_ENABLE) == 0) ) { > printf("DPT: Cannot map the controller as memory, nor as I/O :-(\n"); > return(NULL); > } > } else { > printf("DPT: Device is not Mass Storage, nor SCSI controller :-(\n"); > return(NULL); > } Hmmm, why don't you probe for known vendor and device IDs ? One of the changes to the PCI code, that might follow (I have not completely made up my mind) is, that the probe will just associate a driver with a list of vendor/device IDs, and there will no longer be a xxx_probe() function in the drivers. One reason is that I want to be able to assign drivers to IDs (chip or cards IDs) without recompilation. NCR put a similar probe into their SDMS BIOS (3.xx.xx), where they used the vendor ID and class code, but changed the code to check for specific decide IDs in 4.xx.xx. The old approach caused trouble to people with NCR SCSI cards based on new chips, which came with their own 4.xx BIOS, but had the (inappropriate) 3.xx BIOS trying to initialize them. > command = pci_conf_read(tag, PCI_COMMAND_STATUS_REG); > if ( (command & PCI_COMMAND_MASTER_ENABLE) == 0 ) { > printf("DPT: BUSMASTER disabled :-(\n"); > return (NULL); > } I've never heard of a PCI BIOS, that failed to enable the bus-master functionality, but did set up the chip correctly, else. I really can't imagine a system that would trigger this condition! > And in dpt_pci_attach() > .... > io_base = 0; > vaddr = 0; > paddr = 0; > data = pci_conf_read(config_id, PCI_BASEADR0); > > command = pci_conf_read(config_id, PCI_COMMAND_STATUS_REG); > if ( ((command & PCI_COMMAND_MEM_ENABLE) == 0) > || (pci_map_mem(config_id, PCI_BASEADR0, &vaddr, &paddr) == 0) ) { > /* Either not memory mappable or mapping failed. Try I/O mapping */ > if ((command & PCI_COMMAND_IO_ENABLE) == 0 > || (pci_map_port(config_id, PCI_BASEADR0, &io_base) == 0) ) { > free(dpt, M_DEVBUF); > printf ("dpt%d: Failed to map memory or I/O registers :-(\n", unit); > return; > } > } > > Makes sense? The other driver's don't test for the enable bits, and just rely on the error indication returned by the call to pci_map_XXX(). You should not check those values from within any driver, IMHO, but instead just try to map the regions you need, and perform an error exit if mandatory mappings failed. BTW: There appears to be a buglet in your code: Every base address register may only hold either a memory or a port address, and the address type is hard-wired into the chip! This means, that the use of base addr reg 0 for both the call to pci_map_mem() and pci_map_port() must be wrong. (I assume the letter is never tried, since the prior always succeeds.) The PCI BIOS needs the type bits (low order bits of the address base registers) to be R/O in order to assign valid addresses. If both memory and port accesses are supported, then one register will have the two low order bits wired to 01, and another one will have low order 4 bits of 0000 (or less likely some other even number). The PCI BIOS uses the low order bits to decide whether some currently unused port or memory region is reserved for that chip, and then puts the base into the register. You know from the data sheet, which register will hold a port and which one will hold a memory address, if they can be assigned. BTW: Your test of the memory and port enable bits is not sufficient, if the devices are behind a PCI to PCI bridge, as Justin Gibbs pointed out to me. (And I'll modify the PCI code to correctly return an error indication to the pci_map_xxx() call, in such a case.) Regards, STefan From owner-freebsd-hackers Fri Jul 18 11:37:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA08706 for hackers-outgoing; Fri, 18 Jul 1997 11:37:19 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA08679; Fri, 18 Jul 1997 11:37:05 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA17421 (5.67b/IDA-1.5); Fri, 18 Jul 1997 20:36:55 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA09874; Fri, 18 Jul 1997 20:36:45 +0200 (CEST) X-Face: " Date: Fri, 18 Jul 1997 20:36:44 +0200 From: Stefan Esser To: Bruce Evans Cc: hasty@rah.star-gate.com, luigi@labinfo.iet.unipi.it, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, rhh@ct.picker.com, Stefan Esser Subject: Re: snd driver attach routine References: <199707141046.UAA02952@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707141046.UAA02952@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jul 14, 1997 at 08:46:14PM +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 14, Bruce Evans wrote: > >Problem: what should be the return type of *attach() routines ? > > Perhaps it should be void to match reality, but it currently must be > int for isa drivers to match the prototype in `struct isa_driver'. > > >The drivers in /sys/pci all return void for the attach routine. > > They have to, to match the prototype in `strcuct pci_driver'. I could easily change the return type of the PCI attach function. Should I ??? Regards, STefan From owner-freebsd-hackers Fri Jul 18 12:15:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10841 for hackers-outgoing; Fri, 18 Jul 1997 12:15:21 -0700 (PDT) Received: from insl1.etec.uni-karlsruhe.de (uucp@insl1.etec.uni-karlsruhe.de [129.13.109.178]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10835 for ; Fri, 18 Jul 1997 12:15:16 -0700 (PDT) Received: (from uucp@localhost) by insl1.etec.uni-karlsruhe.de (8.8.6/8.8.2) with UUCP id VAA25648 for hackers@FreeBSD.ORG; Fri, 18 Jul 1997 21:14:54 +0200 (CEST) Received: (from erb@localhost) by insl2.etec.uni-karlsruhe.de (8.8.5/8.8.2) id VAA12362 for hackers@FreeBSD.ORG; Fri, 18 Jul 1997 21:14:01 +0200 (CEST) Message-Id: <199707181914.VAA12362@insl2.etec.uni-karlsruhe.de> Subject: integrating ppp-2.3.0, predictor compression To: hackers@FreeBSD.ORG Date: Fri, 18 Jul 1997 21:14:01 +0200 (CEST) Reply-To: erb@inss1.etec.uni-karlsruhe.de From: erb@inss1.etec.uni-karlsruhe.de (Olaf Erb) 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, are there plans to integrate ppp-2.3.0 w/deflate? I've seen some files were updated in -current, but still no deflate. I hacked ppp-2.3.0 myself into a 2.2.2 kernel, but sometimes panics occured I weren't able to track down. Well, I didn't tried that hard though and gave up quick, it was just a test to see how good deflate is (it's a lot better than BSD comp). Btw, is anyone doing predictor compression for kernel-ppp? Olaf -- Argue your limitations, and sure enough, they're yours. -- Richard Bach, Illusions From owner-freebsd-hackers Fri Jul 18 13:37:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA14927 for hackers-outgoing; Fri, 18 Jul 1997 13:37:55 -0700 (PDT) Received: from zeus.carroll.com (zeus.carroll.com [199.224.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14922 for ; Fri, 18 Jul 1997 13:37:40 -0700 (PDT) Received: from apollo.carroll.com [199.224.10.3] by zeus.carroll.com with ESMTP (8.8.5/0) id QAA09222; Fri, 18 Jul 1997 16:36:51 -0400 Received: by apollo.carroll.com (8.8.5) is QAA05188; Fri, 18 Jul 1997 16:36:50 -0400 Date: Fri, 18 Jul 1997 16:36:48 -0400 From: Jim Carroll To: freebsd-hackers@freebsd.org Subject: CVSup and the CVS repository (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been having a tremendous amount of trouble trying to get the CVS repository installed on my system (FreeBSD 2.2.1). CVSup (version 15.1) seems to indicate that it has succeeded (and it does build the list file), but it does not create the CVS repository. By this, I mean it does not create the CVSROOT/ directory needed by the 'cvs' utility. Here is my cvsup supfile *default release=cvs tag=. *default delete use-rel-suffix *default host=cvsup.FreeBSD.org *default base=/usr prefix=/usr *default compress src-all I ran cvsup thusly: cvsup -g -L2 supfile After it was done, it seems nothing I do can access the CVS repository. I have tried a basic listing of tags, but it yields no results: cvs -d /usr history -T This yields: cvs [history aborted]: cannot open history file: /usr/CVSROOT/history: No such file or directory All attempts to extract source also fails, with an error that the release does not exist: cvs -d /usr -P -r RELENG_2_2_1_RELEASE src This yeilds the error: cvs [checkout aborted]: no such tag RELENG_2_2_1_RELEASE I obviously do not have a firm graps of the inner workings of the CVS system. I have read every reference from the FreeBSD site (handbook & FAQ) I could find. I also have read over the docs that came with the cvsup executable (version 15.1). Any help you can offer would be much appreciated. Thanks in advance --- Jim C., President | C A R R O L L - N E T, Inc. 201-488-1332 voice | New Jersey's Premier Internet Service Provider 201-487-5717 dialup | http://www.carroll.com | Ask about our Business Messaging Services From owner-freebsd-hackers Fri Jul 18 13:44:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15133 for hackers-outgoing; Fri, 18 Jul 1997 13:44:19 -0700 (PDT) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15127 for ; Fri, 18 Jul 1997 13:44:14 -0700 (PDT) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.4/8.8.4) with UUCP id VAA20467 for freebsd.org!hackers; Fri, 18 Jul 1997 21:28:02 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 18 Jul 1997 21:21:22 +0100 X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 18 Jul 1997 21:17:29 +0100 To: hackers@freebsd.org From: Bob Bishop Subject: Iomega Zip Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK From owner-freebsd-hackers Fri Jul 18 14:55:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA18594 for hackers-outgoing; Fri, 18 Jul 1997 14:55:13 -0700 (PDT) Received: from zeus.carroll.com (zeus.carroll.com [199.224.10.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18586 for ; Fri, 18 Jul 1997 14:55:07 -0700 (PDT) Received: from apollo.carroll.com [199.224.10.3] by zeus.carroll.com with ESMTP (8.8.5/0) id RAA24123; Fri, 18 Jul 1997 17:55:04 -0400 Received: by apollo.carroll.com (8.8.5) is RAA23807; Fri, 18 Jul 1997 17:55:03 -0400 Date: Fri, 18 Jul 1997 17:55:02 -0400 From: Jim Carroll To: Bob Bishop cc: freebsd-hackers@freebsd.org Subject: Re: Iomega Zip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Bob Bishop wrote: > Date: Fri, 18 Jul 1997 21:17:29 +0100 > From: Bob Bishop > To: hackers@FreeBSD.ORG > Subject: Iomega Zip > > Hi, > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA We are. The drive works like a champ. The complete source, and full docs on how to setup this solution is available at: http://www.prism.uvsq.fr/~son/ppa3.html Feel free to email me directly if you have any trouble getting it to work. --- Jim C., President | C A R R O L L - N E T, Inc. 201-488-1332 voice | New Jersey's Premier Internet Service Provider 201-487-5717 dialup | http://www.carroll.com | Ask about our Business Messaging Services From owner-freebsd-hackers Fri Jul 18 15:04:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18961 for hackers-outgoing; Fri, 18 Jul 1997 15:04:15 -0700 (PDT) Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18956 for ; Fri, 18 Jul 1997 15:04:10 -0700 (PDT) Received: from saturn.ajc.state.net (saturn.ajc.state.net [204.120.158.166]) by neptune.ajc.state.net (8.8.6/8.8.5) with SMTP id RAA00351 for ; Fri, 18 Jul 1997 17:04:06 -0500 (CDT) Received: by localhost with Microsoft MAPI; Fri, 18 Jul 1997 17:01:47 -0500 Message-ID: <01BC939C.46CF4020.Al.Johnson@AJC.State.Net> From: Al Johnson To: "'hackers@freebsd.org'" Subject: HP LaserJet 6L Date: Fri, 18 Jul 1997 17:01:46 -0500 Organization: Al Johnson Consulting 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey folks, I'm trying to migrate all my ciritical functions from Win95 to FreeBSD. Ya, I hear you all groaning now :) Since I'm no expert at this, been a long time since I was a unix sysadmin, I need assistance with the filters needed for this printer. I have successfully printed plain text on the HP from the directly connected system sort of. An lptest > /dev/lpt0 gets me a sheet of paper with a single line printed on it. Obvisouly not what it's supposed to generate. Anyone with a filter or an adequate printcap definition for this (or just about any PCL) printer I would really appreciate an email copy. In addition, is there any special setup required to get the appropriate conversion from a Win95 print job to the printer via Samba? -- Al From owner-freebsd-hackers Fri Jul 18 15:18:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19610 for hackers-outgoing; Fri, 18 Jul 1997 15:18:29 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19605 for ; Fri, 18 Jul 1997 15:18:26 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id SAA15985; Fri, 18 Jul 1997 18:18:21 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA04229; Fri, 18 Jul 1997 18:18:14 -0400 Date: Fri, 18 Jul 1997 18:17:54 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Bob Bishop cc: hackers@FreeBSD.ORG Subject: Re: Iomega Zip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Bob Bishop wrote: > Hi, > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA > I am, scsi interface. Works just fine. 96 megs of instant backup. > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Jul 18 15:31:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20268 for hackers-outgoing; Fri, 18 Jul 1997 15:31:08 -0700 (PDT) Received: from Blinky.HEMPAC.Net (Blinky.HEMPAC.Net [199.17.40.222]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20259 for ; Fri, 18 Jul 1997 15:31:04 -0700 (PDT) Received: (from markh@localhost) by Blinky.HEMPAC.Net (8.8.5/8.8.5) id RAA19487; Fri, 18 Jul 1997 17:30:32 -0500 (CDT) From: Mark Holden Message-Id: <199707182230.RAA19487@Blinky.HEMPAC.Net> Subject: Re: HP LaserJet 6L To: Al.Johnson@AJC.State.Net (Al Johnson) Date: Fri, 18 Jul 1997 17:30:32 -0500 (CDT) Cc: hackers@FreeBSD.ORG In-Reply-To: <01BC939C.46CF4020.Al.Johnson@AJC.State.Net> from "Al Johnson" at Jul 18, 97 05:01:46 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >needed for this printer. I have successfully printed plain text on the >HP from the directly connected system sort of. An lptest > /dev/lpt0 >gets me a sheet of paper with a single line printed on it. Obvisouly not >what it's supposed to generate. Anyone with a filter or an adequate printcap >definition for this (or just about any PCL) printer I would really appreciate >an email copy. > >In addition, is there any special setup required to get the appropriate >conversion from a Win95 print job to the printer via Samba? It's not so much that you need a printcap entry, as that you need a filter that converts LF to CR+LF. I've done stuff like this in the past, but it's been a long time since I neded to make a non Postscript HP work with a UNIX box. It might be possible to do with stty settings in printcap, but I never had any luck doing that. Given that this has to be one of the most common problems when hooking a printer up to most UNIXes, I'm kinda surprised they're not a standard fix for it with an example in /etc/printcap. Or have I been painfully stupid about this for the last 7 or so years? -Mark Holden From owner-freebsd-hackers Fri Jul 18 16:13:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22572 for hackers-outgoing; Fri, 18 Jul 1997 16:13:59 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22565 for ; Fri, 18 Jul 1997 16:13:55 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id TAA22973; Fri, 18 Jul 1997 19:13:47 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id TAA05971; Fri, 18 Jul 1997 19:13:44 -0400 Date: Fri, 18 Jul 1997 19:13:22 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Mark Holden cc: Al Johnson , hackers@FreeBSD.ORG Subject: Re: HP LaserJet 6L In-Reply-To: <199707182230.RAA19487@Blinky.HEMPAC.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Mark Holden wrote: > It's not so much that you need a printcap entry, as that you need a filter > that converts LF to CR+LF. I've done stuff like this in the past, but it's > been a long time since I neded to make a non Postscript HP work with a UNIX > box. It might be possible to do with stty settings in printcap, but I never > had any luck doing that. > > Given that this has to be one of the most common problems when hooking a > printer up to most UNIXes, I'm kinda surprised they're not a standard fix > for it with an example in /etc/printcap. > > Or have I been painfully stupid about this for the last 7 or so years? I wouldn't call you that, just that there's more stuff out there than any six people could keep track of. One thing here, in particular, that you guys should look at is the port of apsfilter. That's a great, automatic, multipurpose printer filter. Send anything your heart desires off to the printer, and it converts it intelligently and prints it. Before you get that, get ghostscript5 working well for you, so that you know just which of the _large_ assortment of printer drivers that are available for it work for you. This will mean also installing the things that ghostscript5 wants, like tiff, jpeg, and png libraries. Once you get that working, read up on lpd, then try /usr/ports/print/apsfilter. You'll be glad you did. If you need help, ask on the FreeBSD-ports list for help. I think I'll do some surgery on apsfilter anyhow, it's needed it for a while now. I have a new port of a2ps ready (waiting for the author to release a new version next week, he asked for it, and I'm going to do that) and apsfilter uses a2ps. Apsfilter has to be hacked to use the new version. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Jul 18 16:25:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23364 for hackers-outgoing; Fri, 18 Jul 1997 16:25:05 -0700 (PDT) Received: from wakky.dyn.ml.org (root@1Cust47.Max17.Washington.DC.MS.UU.NET [153.34.57.47]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23354 for ; Fri, 18 Jul 1997 16:24:55 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id SAA01042; Fri, 18 Jul 1997 18:17:08 -0400 (EDT) Message-ID: <19970718181703.13407@wakky.dyn.ml.org> Date: Fri, 18 Jul 1997 18:17:03 -0400 From: Lee Cremeans To: Jim Carroll Cc: hackers@freebsd.org Subject: Re: Iomega Zip References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e Reply-to: hcremean@vt.edu X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We are. The drive works like a champ. > > The complete source, and full docs on how to setup this solution is > available at: > > http://www.prism.uvsq.fr/~son/ppa3.html > Note that this is only for the parallel-port Zip. If you have a SCSI Zip, all you need is a supported SCSI host adapter and the cables. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower)|A! JW223 "People are idiots who deserve to be mocked."--Dogbert|YWD+++i P&B+++ SL+++^i My home page:http://wakky.dyn.ml.org/~lee | MD+++r P+ I++ Di "Whoa, dumber than advertised!" | $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi From owner-freebsd-hackers Fri Jul 18 16:29:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23559 for hackers-outgoing; Fri, 18 Jul 1997 16:29:26 -0700 (PDT) Received: from Kryten.nina.org (port-55.ts1.gnv.fdt.net [205.229.51.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23554 for ; Fri, 18 Jul 1997 16:29:22 -0700 (PDT) Received: from localhost (frankd@localhost) by Kryten.nina.org (8.8.5/8.8.5) with SMTP id TAA08954 for ; Fri, 18 Jul 1997 19:14:04 -0400 (EDT) X-Authentication-Warning: Kryten.nina.org: frankd owned process doing -bs Date: Fri, 18 Jul 1997 19:14:04 -0400 (EDT) From: Frank Seltzer X-Sender: frankd@Kryten.nina.org To: hackers@freebsd.org Subject: sys/vfs.h Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Do we have an equivalent file to this Linux file? I am trying to build XVFilemanager and mount.c has #include which causes the build to fall over. Thanks, Frank -- Only in America can a homeless veteran sleep in a cardboard box while a draft dodger sleeps in the White House - anonymous From owner-freebsd-hackers Fri Jul 18 17:18:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA25606 for hackers-outgoing; Fri, 18 Jul 1997 17:18:42 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA25587; Fri, 18 Jul 1997 17:18:33 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id RAA07293; Fri, 18 Jul 1997 17:18:20 -0700 (PDT) Message-Id: <199707190018.RAA07293@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Stefan Esser cc: Bruce Evans , luigi@labinfo.iet.unipi.it, hackers@freebsd.org, multimedia@freebsd.org, rhh@ct.picker.com Subject: Re: snd driver attach routine In-reply-to: Your message of "Fri, 18 Jul 1997 20:36:44 +0200." <19970718203644.04289@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Jul 1997 17:18:19 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, we should be able to detect device specific failure and not allow access to the device driver that way our drivers don't have to handle a fatal low level device configuration . Amancio >From The Desk Of Stefan Esser : > On Jul 14, Bruce Evans wrote: > > >Problem: what should be the return type of *attach() routines ? > > > > Perhaps it should be void to match reality, but it currently must be > > int for isa drivers to match the prototype in `struct isa_driver'. > > > > >The drivers in /sys/pci all return void for the attach routine. > > > > They have to, to match the prototype in `strcuct pci_driver'. > > I could easily change the return type of > the PCI attach function. Should I ??? > > Regards, STefan From owner-freebsd-hackers Fri Jul 18 17:51:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26955 for hackers-outgoing; Fri, 18 Jul 1997 17:51:21 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26950 for ; Fri, 18 Jul 1997 17:51:18 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id RAA07456; Fri, 18 Jul 1997 17:50:40 -0700 (PDT) Message-Id: <199707190050.RAA07456@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Wm Brian McCane cc: hackers@FreeBSD.ORG Subject: Re: Strange SCSI problem In-reply-to: Your message of "Fri, 18 Jul 1997 11:42:18 CDT." <199707181642.LAA17049@bmccane.uit.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Jul 1997 17:50:40 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, We need a couple of things, a sample run with tracing enable: setenv SANE_DEBUG_UMAX 128 scsi -f device -d 255 The actual code which takes care of sending the scsi request is in sane/sanei/sanei_scsi.c: result = scsireq_enter (fd, &hdr); if (result < 0) { DBG(1, "sanei_scsi_cmd: scsi_reqenter() failed: %s\n", strerror (errno)); return SANE_STATUS_IO_ERROR; } if (hdr.retsts != SCCMD_OK) { DBG(1, "sanei_scsi_cmd: scsi returned with status %d\n", hdr.retsts); switch (hdr.retsts) { case SCCMD_TIMEOUT: case SCCMD_BUSY: return SANE_STATUS_DEVICE_BUSY; case SCCMD_SENSE: if (fd < num_handlers_alloced && sense_handler[fd]) return (*sense_handler[fd]) (fd, &hdr.sense[0]); /* fall through */ default: return SANE_STATUS_IO_ERROR; } } You can always add additional error logging if you like. The trace is important because it will let us know if something before failed which causes the scanner not to respond. Also, do you have target queueing enabled in your scsi driver? OS version, scsi controller and if you have any other devices on the scsi bus. Tnks, Amancio >From The Desk Of Wm Brian McCane : > Howdy, > > I have built `gimp' on my system, and also have built `sane'. Sane is a > scanner interface program that directly accesses the SCSI `uk0' device to get > data from the scanner. Anyway, to make a long story short, when I try to use > `sane', it doesn't get any data from the scanner. The `scsireq_enter' return s > a success status, and that there were 96 bytes read, but the buffer contains > the data that was in it when the function was called. To experiment with > this, I used the `scsi' command: > scsi -f /dev/uk0 -c "12 0 0 0 60 0" -i 96 "i4 i4 i4 i4 i4 i4 i4 i4" > It reports 96 bytes read, but the buffer contains all 0's, because the `scsi' > command bzero's the buffer before calling the `scsireq_enter' function. I > have looked at the kernel code, and I can't find the problem, but I assume > that the data is not being copied into user space from kernel space. Any > ideas? > > brian > > From owner-freebsd-hackers Fri Jul 18 17:58:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27294 for hackers-outgoing; Fri, 18 Jul 1997 17:58:30 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27281 for ; Fri, 18 Jul 1997 17:58:23 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id RAA07028; Fri, 18 Jul 1997 17:58:13 -0700 (PDT) Message-Id: <199707190058.RAA07028@austin.polstra.com> To: jim@carroll.com Subject: Re: CVSup and the CVS repository (fwd) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Fri, 18 Jul 1997 17:58:13 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Jim Carroll wrote: > > I have been having a tremendous amount of trouble trying to get the CVS > repository installed on my system (FreeBSD 2.2.1). CVSup (version 15.1) > seems to indicate that it has succeeded (and it does build the list file), > but it does not create the CVS repository. By this, I mean it does not > create the CVSROOT/ directory needed by the 'cvs' utility. > > Here is my cvsup supfile > > *default release=cvs tag=. > [...] Bleep. If you want the repository, you must not specify "tag" or "date" in the supfile. Specifying "tag" or "date" causes it to deliver a specific checked out version of each file. Also: > *default base=/usr prefix=/usr You probably don't want "prefix=/usr" for the repository. The "standard" prefix is "/home/ncvs". If you use "prefix=/usr" it will put the repository on top of your "/usr/src" tree, which surely is not what you want. I'd suggest starting with /usr/share/examples/cvsup/cvs-supfile, and modifying it if necessary to meet your needs. Look also at secure-cvs-supfile in the same directory. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Fri Jul 18 18:03:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27546 for hackers-outgoing; Fri, 18 Jul 1997 18:03:41 -0700 (PDT) Received: from agni.nuko.com ([206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27541 for ; Fri, 18 Jul 1997 18:03:38 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id SAA23276 for freebsd-hackers@freebsd.org; Fri, 18 Jul 1997 18:01:30 -0700 (PDT) From: Vinay Bannai Message-Id: <199707190101.SAA23276@agni.nuko.com> Subject: What interrupts to mask in my device driver?? To: freebsd-hackers@freebsd.org Date: Fri, 18 Jul 1997 18:01:29 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I am in the middle of a PCI driver implementation. The board has a i960 processor and memory. I have been able to probe and attach it successfully. Here are couple of questions: - Before calling pci_map_mem() and pci_map_int(), I noticed that David Greenman has disabled network device interrupts. What interrupts should I disable on the device that I have? Here are the details of my device from the probe routine. Currently I am not disabling any interrupts and it seems to attach okay.. cyclone0 rev 19 int a irq 9 on pci0:15 cyclone0: attach: unit configured cyclone0: attach: memmory successfully mapped Vendor ID = 113c Device ID = 0001 Command = 0107 Status = 0280 Base class = ff, Sub-class = 00, Interface = 00 Revision = 13 BIST = 00 Header type = 00 Latency = 42 Cache line size = 00 Base addr 0 = 0001113c Base addr 1 = 02800107 Base addr 2 = ff000013 Base addr 3 = 00004200 Base addr 4 = fffbec00 Base addr 5 = 0000fc81 ROM base = fee00000 Interrupt line = 09 Interrupt pin = 01 Min_Gnt = 00 Max_Lat = 00 - Next question: Are there any freely available gcc cross compilers for i960 Kx architecture? Thanks Vinay --- Vinay Bannai E-mail: vinay@agni.nuko.com (408)-526-0280 x 275 (Work) http://agni.nuko.com/~vinay From owner-freebsd-hackers Fri Jul 18 18:42:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29451 for hackers-outgoing; Fri, 18 Jul 1997 18:42:08 -0700 (PDT) Received: from jazz.snu.ac.kr (jazz.snu.ac.kr [147.46.102.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29446 for ; Fri, 18 Jul 1997 18:42:05 -0700 (PDT) Received: (from junker@localhost) by jazz.snu.ac.kr (8.8.5/8.8.4-procmail) id KAA04662; Sat, 19 Jul 1997 10:39:59 +1000 (KDT) To: hackers@FreeBSD.ORG Subject: Re: Iomega Zip References: From: Choi Jun Ho Date: 19 Jul 1997 10:39:59 +1000 In-Reply-To: Chuck Robey's message of Fri, 18 Jul 1997 18:17:54 -0400 (EDT) Message-ID: Lines: 17 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA > > > > I am, scsi interface. Works just fine. 96 megs of instant backup. > Some people(like me) use ATAPI Zip(EIDE). It also works fine. (no cmos setup is need, but detects well in kernel!) It is very fast(though I have no info about SCSI version), and just like EIDE... (even I have installed 2.2-970618-RELENG from ZipDrive! :) -- ---Cool FreeBSD!-----MSX Forever!-----J.U.N.K.E.R/Beat Snatchers!--- ***Call me `Mr. Choi', not `Mr. Ho'! My family name is `Choi'!!*** Choi Jun Ho http://jazz.snu.ac.kr/~junker Distributed Computing System Lab,CS Dept.,Seoul National Univ.,ROK From owner-freebsd-hackers Fri Jul 18 21:08:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04765 for hackers-outgoing; Fri, 18 Jul 1997 21:08:10 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04758 for ; Fri, 18 Jul 1997 21:08:05 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id VAA03638; Fri, 18 Jul 1997 21:09:12 -0700 (PDT) Date: Fri, 18 Jul 1997 21:09:11 -0700 (PDT) From: Howard Lew To: Bob Bishop cc: hackers@FreeBSD.ORG Subject: Re: Iomega Zip In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Bob Bishop wrote: > Hi, > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA > Awesome drive. Get the scsi version to make sure it is compatible. The probe doesn't look right, but it works: sd0 at scbus0 target 5 lun 0 sd0: Direct-Access sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry sd0: NOT READY asc:3a,0 Medium not present sd0: could not get size 0MB (0 512 byte sectors) sd0: with 0 cyls, 64 heads, and an average 32 sectors/track This is using the scsi card that came with the drive. > > -- > Bob Bishop (0118) 977 4017 international code +44 118 > rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK > > > From owner-freebsd-hackers Fri Jul 18 21:21:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA05407 for hackers-outgoing; Fri, 18 Jul 1997 21:21:34 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA05401 for ; Fri, 18 Jul 1997 21:21:28 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id NAA12564; Sat, 19 Jul 1997 13:51:14 +0930 (CST) From: Michael Smith Message-Id: <199707190421.NAA12564@genesis.atrad.adelaide.edu.au> Subject: Re: Iomega Zip In-Reply-To: from Bob Bishop at "Jul 18, 97 09:17:29 pm" To: rb@gid.co.uk (Bob Bishop) Date: Sat, 19 Jul 1997 13:51:14 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bob Bishop stands accused of saying: > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA Parallel, SCSI or IDE? SCSI and IDE work just like you would expect them to. For a driver for the parallel units, see http://www.prism.uvsq.fr/~son/ppa3.html > Bob Bishop (0118) 977 4017 international code +44 118 -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 18 21:41:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06175 for hackers-outgoing; Fri, 18 Jul 1997 21:41:56 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06167 for ; Fri, 18 Jul 1997 21:41:50 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA12625; Sat, 19 Jul 1997 14:11:37 +0930 (CST) From: Michael Smith Message-Id: <199707190441.OAA12625@genesis.atrad.adelaide.edu.au> Subject: Re: Iomega Zip In-Reply-To: from Howard Lew at "Jul 18, 97 09:09:11 pm" To: hlew@www2.shoppersnet.com (Howard Lew) Date: Sat, 19 Jul 1997 14:11:36 +0930 (CST) Cc: rb@gid.co.uk, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Howard Lew stands accused of saying: > > The probe doesn't look right, but it works: The probe is _exactly_ right. > sd0 at scbus0 target 5 lun 0 > sd0: Direct-Access > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > sd0 could not mode sense (4). Using ficticious geometry The drive has refused a MODE SENSE command, so it's not possible to establish its geometry. Geometry is only (really) relevant for processing the MBR. Instead, the driver will fake some sensible falues. > sd0: NOT READY asc:3a,0 Medium not present > sd0: could not get size > 0MB (0 512 byte sectors) The driver has attempted to interrogate the drive to obtain its total size in sectors. The drive reports an error because you haven't inserted a disk. This is common for removables, particularly those that support more than one media size. > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track And this is the resultant fake geometry, given a size of 0 sectors. It's good enough. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 18 21:50:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06505 for hackers-outgoing; Fri, 18 Jul 1997 21:50:27 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06500 for ; Fri, 18 Jul 1997 21:50:22 -0700 (PDT) Message-Id: <199707190450.VAA06500@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA083587134; Sat, 19 Jul 1997 14:38:54 +1000 From: Darren Reed Subject: Re: Iomega Zip To: hlew@www2.shoppersnet.com (Howard Lew) Date: Sat, 19 Jul 1997 14:38:54 +1000 (EST) Cc: rb@gid.co.uk, hackers@FreeBSD.ORG In-Reply-To: from "Howard Lew" at Jul 18, 97 09:09:11 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Howard Lew, sie said: > > On Fri, 18 Jul 1997, Bob Bishop wrote: > > > Hi, > > > > Anyone using Iomega Zip drives with FBSD? Any hints/comments? TIA > > > > Awesome drive. Get the scsi version to make sure it is compatible. > > The probe doesn't look right, but it works: > > sd0 at scbus0 target 5 lun 0 > sd0: Direct-Access > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > sd0 could not mode sense (4). Using ficticious geometry > > sd0: NOT READY asc:3a,0 Medium not present > sd0: could not get size > 0MB (0 512 byte sectors) > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track > > This is using the scsi card that came with the drive. Well, 2.2.1 detects neither ZIP or JAZ with recognised SCSI cards. Jul 19 14:33:20 freebsd /kernel: ahc0 rev 0 int a irq 9 on pci0:12 Jul 19 14:33:20 freebsd /kernel: ahc0: Using left over BIOS settings Jul 19 14:33:20 freebsd /kernel: ahc0: aic7880 sxfrctl1 == 0x1 Jul 19 14:33:20 freebsd /kernel: Wide Channel, SCSI Id=7, 16 SCBs Jul 19 14:33:20 freebsd /kernel: ahc0 waiting for scsi devices to settle Jul 19 14:33:20 freebsd /kernel: (ahc0:4:0): "iomega jaz 1GB J^77" type 0 remova ble SCSI 2 Jul 19 14:33:20 freebsd /kernel: sd0(ahc0:4:0): Direct-Access Jul 19 14:33:20 freebsd /kernel: sd0(ahc0:4:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB Jul 19 14:33:20 freebsd /kernel: sd0 could not mode sense (4). Using ficticious geometry Jul 19 14:33:20 freebsd /kernel: Jul 19 14:33:20 freebsd /kernel: sd0(ahc0:4:0): NOT READY asc:3a,0 Medium not pr esent Jul 19 14:33:20 freebsd /kernel: sd0: could not get size Jul 19 14:33:20 freebsd /kernel: 0MB (0 512 byte sectors) Jul 19 14:33:20 freebsd /kernel: sd0(ahc0:4:0): with 0 cyls, 64 heads, and an av erage 32 sectors/track Jul 19 14:33:20 freebsd /kernel: (ahc0:6:0): "IOMEGA ZIP 100 E.08" type 0 remova ble SCSI 2 Jul 19 14:33:20 freebsd /kernel: sd1(ahc0:6:0): Direct-Access Jul 19 14:33:20 freebsd /kernel: sd1(ahc0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB Jul 19 14:33:21 freebsd /kernel: sd1 could not mode sense (4). Using ficticious geometry Jul 19 14:33:21 freebsd /kernel: Jul 19 14:33:21 freebsd /kernel: sd1(ahc0:6:0): NOT READY asc:3a,0 Medium not pr esent Jul 19 14:33:21 freebsd /kernel: sd1: could not get size Jul 19 14:33:21 freebsd /kernel: 0MB (0 512 byte sectors) Jul 19 14:33:21 freebsd /kernel: sd1(ahc0:6:0): with 0 cyls, 64 heads, and an av erage 32 sectors/track also, anyone know why I get these messages ? Jul 19 14:33:22 freebsd /kernel: Device wd0: name slot allocation failed (Errno= 17) Jul 19 14:33:22 freebsd /kernel: Device rwd0: name slot allocation failed (Errno =17) Darren From owner-freebsd-hackers Fri Jul 18 22:20:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07745 for hackers-outgoing; Fri, 18 Jul 1997 22:20:00 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA07723; Fri, 18 Jul 1997 22:19:48 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA18529; Sat, 19 Jul 1997 06:16:45 +0200 From: Luigi Rizzo Message-Id: <199707190416.GAA18529@labinfo.iet.unipi.it> Subject: Re: snd driver attach routine To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 19 Jul 1997 06:16:45 +0200 (MET DST) Cc: se@FreeBSD.ORG, bde@zeta.org.au, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, rhh@ct.picker.com In-Reply-To: <199707190018.RAA07293@rah.star-gate.com> from "Amancio Hasty" at Jul 18, 97 05:18:00 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, we should be able to detect device specific failure and > not allow access to the device driver that way our drivers don't > have to handle a fatal low level device configuration . I think I get the rationale for not testing return value in the attach routine. After the probe you (should) know that the peripheral is there. A failure to attach should then depend only on os problems (typically, failure to allocate resources such as memory, dma, irq, or a device descriptor). Since no resource allocation was in the probe, the routine calling the attach has nothing to do on failure -- all deallocations should be done in the attach routine being device specific. Secondly, if I am not mistaken, once you create a device entry in the fs with a major number corresponding to an existing device, the routines for the devices are always invoked and they have to check the minor dev anyways to see if it corresponds to a configured device. So basically I think that it is ok to have the attach routine to return void for all buses (which means that, if something has to be changed, is the attach for isa drivers). Cheers Luigi > >From The Desk Of Stefan Esser : > > On Jul 14, Bruce Evans wrote: > > > >Problem: what should be the return type of *attach() routines ? > > > > > > Perhaps it should be void to match reality, but it currently must be > > > int for isa drivers to match the prototype in `struct isa_driver'. > > > > > > >The drivers in /sys/pci all return void for the attach routine. > > > > > > They have to, to match the prototype in `strcuct pci_driver'. > > > > I could easily change the return type of > > the PCI attach function. Should I ??? > > > > Regards, STefan -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Fri Jul 18 22:41:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08454 for hackers-outgoing; Fri, 18 Jul 1997 22:41:24 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA08448 for ; Fri, 18 Jul 1997 22:41:21 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id WAA06988; Fri, 18 Jul 1997 22:42:30 -0700 (PDT) Date: Fri, 18 Jul 1997 22:42:30 -0700 (PDT) From: Howard Lew To: Michael Smith cc: rb@gid.co.uk, hackers@FreeBSD.ORG Subject: Re: Iomega Zip In-Reply-To: <199707190441.OAA12625@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 19 Jul 1997, Michael Smith wrote: > Howard Lew stands accused of saying: > > > > The probe doesn't look right, but it works: > > The probe is _exactly_ right. > > > sd0 at scbus0 target 5 lun 0 > > sd0: Direct-Access > > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > sd0 could not mode sense (4). Using ficticious geometry > > The drive has refused a MODE SENSE command, so it's not possible to > establish its geometry. Geometry is only (really) relevant for > processing the MBR. Instead, the driver will fake some sensible > falues. > > > sd0: NOT READY asc:3a,0 Medium not present > > sd0: could not get size > > 0MB (0 512 byte sectors) > > The driver has attempted to interrogate the drive to obtain its total > size in sectors. The drive reports an error because you haven't > inserted a disk. This is common for removables, particularly those > that support more than one media size. > > > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track > > And this is the resultant fake geometry, given a size of 0 sectors. It's > good enough. > oh... I guess the probe is fine then. The zip drive (scsi) works great. > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > From owner-freebsd-hackers Fri Jul 18 22:45:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08576 for hackers-outgoing; Fri, 18 Jul 1997 22:45:29 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA08571 for ; Fri, 18 Jul 1997 22:45:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA12806; Sat, 19 Jul 1997 15:14:56 +0930 (CST) From: Michael Smith Message-Id: <199707190544.PAA12806@genesis.atrad.adelaide.edu.au> Subject: Re: Iomega Zip In-Reply-To: <199707190450.VAA06500@hub.freebsd.org> from Darren Reed at "Jul 19, 97 02:38:54 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Sat, 19 Jul 1997 15:14:55 +0930 (CST) Cc: hlew@www2.shoppersnet.com, rb@gid.co.uk, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > > Well, 2.2.1 detects neither ZIP or JAZ with recognised SCSI cards. Bollocks. Your probes look fine; have you tried actully sticking a disk in and talking to it? > also, anyone know why I get these messages ? > > Jul 19 14:33:22 freebsd /kernel: Device wd0: name slot allocation failed (Errno= > 17) > Jul 19 14:33:22 freebsd /kernel: Device rwd0: name slot allocation failed (Errno > =17) These look like devfs messages. If you're not using it, and the messages annoy you, turn it off. 8) If a working DEVFS is important to you, then you should chase Julian and see if he can make time to work on it... > Darren -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 18 23:11:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09396 for hackers-outgoing; Fri, 18 Jul 1997 23:11:40 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09391 for ; Fri, 18 Jul 1997 23:11:36 -0700 (PDT) Message-Id: <199707190611.XAA09391@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA104842014; Sat, 19 Jul 1997 16:00:14 +1000 From: Darren Reed Subject: Re: Iomega Zip To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 19 Jul 1997 16:00:14 +1000 (EST) Cc: avalon@coombs.anu.edu.au, hlew@www2.shoppersnet.com, rb@gid.co.uk, hackers@FreeBSD.ORG In-Reply-To: <199707190544.PAA12806@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 19, 97 03:14:55 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Michael Smith, sie said: > > Darren Reed stands accused of saying: > > > > Well, 2.2.1 detects neither ZIP or JAZ with recognised SCSI cards. > > Bollocks. Your probes look fine; have you tried actully sticking a > disk in and talking to it? Yes, they work. My observations are based on compaing kernel SCSI output compared with what I see using NetBSD 1.2G (which doesn't barf all over the screen): sd0 at scsibus0 targ 4 lun 0: SCSI2 0/direct removable sd0: drive offline sd1 at scsibus0 targ 6 lun 0: SCSI2 0/direct removable sd1: drive offline Neither are Linux or Solaris as loud about them as FreeBSD. Darren From owner-freebsd-hackers Fri Jul 18 23:48:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10961 for hackers-outgoing; Fri, 18 Jul 1997 23:48:35 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10942; Fri, 18 Jul 1997 23:48:25 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA29949; Sat, 19 Jul 1997 16:43:32 +1000 Date: Sat, 19 Jul 1997 16:43:32 +1000 From: Bruce Evans Message-Id: <199707190643.QAA29949@godzilla.zeta.org.au> To: hasty@rah.star-gate.com, luigi@labinfo.iet.unipi.it Subject: Re: snd driver attach routine Cc: bde@zeta.org.au, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, rhh@ct.picker.com, se@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I think I get the rationale for not testing return value in the attach >routine. > >After the probe you (should) know that the peripheral is there. A >failure to attach should then depend only on os problems (typically, >failure to allocate resources such as memory, dma, irq, or a device >descriptor). Since no resource allocation was in the probe, the routine >calling the attach has nothing to do on failure -- all deallocations >should be done in the attach routine being device specific. In practice, for isa devices the IRQ allocation is done in generic code, so the probe status is necessary (but not used). >Secondly, if I am not mistaken, once you create a device entry in the >fs with a major number corresponding to an existing device, the >routines for the devices are always invoked and they have to check the >minor dev anyways to see if it corresponds to a configured device. This is a bug. Drivers whose probe or attach can fail should not use SYSINIT() to register their device switches. Bruce From owner-freebsd-hackers Sat Jul 19 00:12:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11712 for hackers-outgoing; Sat, 19 Jul 1997 00:12:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11693 for ; Sat, 19 Jul 1997 00:12:00 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA13020; Sat, 19 Jul 1997 16:41:45 +0930 (CST) From: Michael Smith Message-Id: <199707190711.QAA13020@genesis.atrad.adelaide.edu.au> Subject: Re: Iomega Zip In-Reply-To: <199707190611.PAA12885@genesis.atrad.adelaide.edu.au> from Darren Reed at "Jul 19, 97 04:00:14 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Sat, 19 Jul 1997 16:41:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, avalon@coombs.anu.edu.au, hlew@www2.shoppersnet.com, rb@gid.co.uk, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > In some mail from Michael Smith, sie said: > > > > Darren Reed stands accused of saying: > > > > > > Well, 2.2.1 detects neither ZIP or JAZ with recognised SCSI cards. > > > > Bollocks. Your probes look fine; have you tried actully sticking a > > disk in and talking to it? > > Yes, they work. So why do you claim that they aren't detected? > My observations are based on compaing kernel SCSI output > compared with what I see using NetBSD 1.2G (which doesn't barf all over > the screen): Arguably the errors could be suppressed, sure. This doesn't mean that the device is "not detected". -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 00:19:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11871 for hackers-outgoing; Sat, 19 Jul 1997 00:19:24 -0700 (PDT) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11860 for ; Sat, 19 Jul 1997 00:19:19 -0700 (PDT) Message-Id: <199707190719.AAA11860@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA122166083; Sat, 19 Jul 1997 17:08:03 +1000 From: Darren Reed Subject: Re: Iomega Zip To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 19 Jul 1997 17:08:03 +1000 (EST) Cc: avalon@coombs.anu.edu.au, msmith@atrad.adelaide.edu.au, hlew@www2.shoppersnet.com, rb@gid.co.uk, hackers@FreeBSD.ORG In-Reply-To: <199707190711.QAA13020@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jul 19, 97 04:41:44 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Michael Smith, sie said: > > Darren Reed stands accused of saying: > > In some mail from Michael Smith, sie said: > > > > > > Darren Reed stands accused of saying: > > > > > > > > Well, 2.2.1 detects neither ZIP or JAZ with recognised SCSI cards. > > > > > > Bollocks. Your probes look fine; have you tried actully sticking a > > > disk in and talking to it? > > > > Yes, they work. > > So why do you claim that they aren't detected? Sorry, perhaps I was too strong with what I said above. When I first saw it, it look like it saw the drives but didn't like them and thus wouldn't use them. Darren From owner-freebsd-hackers Sat Jul 19 01:06:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA13363 for hackers-outgoing; Sat, 19 Jul 1997 01:06:37 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13358 for ; Sat, 19 Jul 1997 01:06:31 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id KAA15717 for hackers@FreeBSD.ORG; Sat, 19 Jul 1997 10:00:26 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.6/8.8.6) id RAA00643; Fri, 18 Jul 1997 17:27:09 +0200 (CEST) Message-ID: <19970718172709.25620@gtn.com> Date: Fri, 18 Jul 1997 17:27:09 +0200 From: Andreas Klemm To: hackers@FreeBSD.ORG Subject: sendmail complains about being unable to write his pid file Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sendmail couldn't write his /var/run/sendmail.pid file. I saw this behaviour in FreeBSD 2.2.2 and -current. I think the newest sendmail version introduces this. It's important, that every directory is owned by root. FreeBSD's /var/run directory permissions are drwxr-xr-x 2 bin bin 512 Jul 18 17:20 run After changing the permissions to: drwxr-xr-x 2 root bin 512 Jul 18 17:20 run everything is fine. So we should fix the installation and possibly the mtree files as well. Any takers ? Any other voices ??? Andreas /// -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Jul 19 01:09:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA13445 for hackers-outgoing; Sat, 19 Jul 1997 01:09:53 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA13439 for ; Sat, 19 Jul 1997 01:09:51 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA13184; Sat, 19 Jul 1997 17:39:43 +0930 (CST) From: Michael Smith Message-Id: <199707190809.RAA13184@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: from Mike O'Dell at "Jul 18, 97 09:32:19 am" To: mo@UU.NET (Mike O'Dell) Date: Sat, 19 Jul 1997 17:39:43 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org, mo@UU.NET X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike O'Dell stands accused of saying: > > i have a new ASUS TX97-E motherboard with the DMI/SMBIOS stuff on it > and it's pretty cool. the National parts which do the actual work > are docuemented and everyone is using the same thing, or so it seems. Hmm. Are you interested in doing any work to tinker with this? Having exhausted what's possible on the board I have here (ie. nothing), I can't actually go much further. I do think that the information would be quite interesting, or at least it's worth supporting the National part(s) (which ones?) directly. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 02:38:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA16036 for hackers-outgoing; Sat, 19 Jul 1997 02:38:36 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA16030 for ; Sat, 19 Jul 1997 02:38:30 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 15279 invoked by uid 1001); 19 Jul 1997 09:38:25 +0000 (GMT) To: andreas@klemm.gtn.com Cc: hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file In-Reply-To: Your message of "Fri, 18 Jul 1997 17:27:09 +0200" References: <19970718172709.25620@gtn.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 19 Jul 1997 11:38:25 +0200 Message-ID: <15277.869305105@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Sendmail couldn't write his /var/run/sendmail.pid file. > I saw this behaviour in FreeBSD 2.2.2 and -current. > > I think the newest sendmail version introduces this. > It's important, that every directory is owned by root. > > FreeBSD's /var/run directory permissions are > drwxr-xr-x 2 bin bin 512 Jul 18 17:20 run > > After changing the permissions to: > drwxr-xr-x 2 root bin 512 Jul 18 17:20 run > > everything is fine. So we should fix the installation and > possibly the mtree files as well. > > Any takers ? Any other voices ??? I'm always nervous about directories owned by bin, on the assumption that bin might be easier to break than root, and could then be used as a stepstone to breaking root. So I tend to manually change most system directories to be owned by root. *Why* are so many of the FreeBSD system directories owned by bin in the standard distribution? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Jul 19 03:22:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA17048 for hackers-outgoing; Sat, 19 Jul 1997 03:22:51 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA17041 for ; Sat, 19 Jul 1997 03:22:46 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA04379; Sat, 19 Jul 1997 12:15:13 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.6/8.8.6) id MAA25991; Sat, 19 Jul 1997 12:08:27 +0200 (CEST) Message-ID: <19970719120826.19772@gtn.com> Date: Sat, 19 Jul 1997 12:08:26 +0200 From: Andreas Klemm To: sthaug@nethelp.no Cc: andreas@klemm.gtn.com, hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file References: <19970718172709.25620@gtn.com> <15277.869305105@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <15277.869305105@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Jul 19, 1997 at 11:38:25AM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Jul 19, 1997 at 11:38:25AM +0200, sthaug@nethelp.no wrote: > > I'm always nervous about directories owned by bin, on the assumption > that bin might be easier to break than root, and could then be used > as a stepstone to breaking root. I don't believe this, because bin isn't a password protected login. Look here: bin:*:3:7:Binaries Commands and Source,,,:/:/nonexistent > So I tend to manually change most system directories to be owned > by root. Since bin isn't an active login I'd vote to keep things as they are but only change the paths for programs like sendmail, that need special permissions. > *Why* are so many of the FreeBSD system directories owned by bin in > the standard distribution? I think it's a BSDism. bin is the UID and GID for Binaries, Commands and source as shown by the entry in /etc/passwd ... -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Jul 19 03:27:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA17141 for hackers-outgoing; Sat, 19 Jul 1997 03:27:57 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA17135 for ; Sat, 19 Jul 1997 03:27:51 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 15408 invoked by uid 1001); 19 Jul 1997 10:27:47 +0000 (GMT) To: andreas@klemm.gtn.com Cc: hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file In-Reply-To: Your message of "Sat, 19 Jul 1997 12:08:26 +0200" References: <19970719120826.19772@gtn.com> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 19 Jul 1997 12:27:46 +0200 Message-ID: <15406.869308066@verdi.nethelp.no> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I'm always nervous about directories owned by bin, on the assumption > > that bin might be easier to break than root, and could then be used > > as a stepstone to breaking root. > > I don't believe this, because bin isn't a password protected login. > Look here: > bin:*:3:7:Binaries Commands and Source,,,:/:/nonexistent That's fine - until somebody decides to run NFS. Then all bets are off. > I think it's a BSDism. bin is the UID and GID for Binaries, Commands > and source as shown by the entry in /etc/passwd ... Yes, but the question stands - why is it setup this way? What is gained by having binaries (and important directories) owned by bin instead of root? Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hackers Sat Jul 19 03:40:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19383 for hackers-outgoing; Sat, 19 Jul 1997 03:40:54 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19348 for ; Sat, 19 Jul 1997 03:40:49 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id MAA04732; Sat, 19 Jul 1997 12:42:30 +0200 (CEST) From: Mikael Karpberg Message-Id: <199707191042.MAA04732@ocean.campus.luth.se> Subject: Re: Iomega Zip In-Reply-To: <199707190441.OAA12625@genesis.atrad.adelaide.edu.au> from Michael Smith at "Jul 19, 97 02:11:36 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sat, 19 Jul 1997 12:42:29 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Michael Smith: > Howard Lew stands accused of saying: > > > > The probe doesn't look right, but it works: > > The probe is _exactly_ right. > > > sd0 at scbus0 target 5 lun 0 > > sd0: Direct-Access > > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > sd0 could not mode sense (4). Using ficticious geometry > > The drive has refused a MODE SENSE command, so it's not possible to > establish its geometry. Geometry is only (really) relevant for > processing the MBR. Instead, the driver will fake some sensible > falues. > > > sd0: NOT READY asc:3a,0 Medium not present > > sd0: could not get size > > 0MB (0 512 byte sectors) > > The driver has attempted to interrogate the drive to obtain its total > size in sectors. The drive reports an error because you haven't > inserted a disk. This is common for removables, particularly those > that support more than one media size. > > > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track > > And this is the resultant fake geometry, given a size of 0 sectors. It's > good enough. Is this in non-verbose boot mode? It really seem to be completely unneeded information, which should be hidden behind the verbose flag. Don't you guys think so? It's bound to be interpreted as an error message. Furthermore, shouldn't the messages maybe explain themselfs a bit better and tell the poor, innocent user that it's not really an error, kinda like autoconf printouts during probing: "Couldn't find stricmp, but that's ok..." :-) *pokes maintainer to fix it* :-) /Mikael From owner-freebsd-hackers Sat Jul 19 03:46:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19486 for hackers-outgoing; Sat, 19 Jul 1997 03:46:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19479 for ; Sat, 19 Jul 1997 03:46:35 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA13659; Sat, 19 Jul 1997 20:16:19 +0930 (CST) From: Michael Smith Message-Id: <199707191046.UAA13659@genesis.atrad.adelaide.edu.au> Subject: Re: Iomega Zip In-Reply-To: <199707191042.MAA04732@ocean.campus.luth.se> from Mikael Karpberg at "Jul 19, 97 12:42:29 pm" To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Sat, 19 Jul 1997 20:16:19 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mikael Karpberg stands accused of saying: > According to Michael Smith: > > Howard Lew stands accused of saying: > > > > > > The probe doesn't look right, but it works: > > > > The probe is _exactly_ right. > > > > > sd0 at scbus0 target 5 lun 0 > > > sd0: Direct-Access > > > sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB > > > sd0 could not mode sense (4). Using ficticious geometry > > > > The drive has refused a MODE SENSE command, so it's not possible to > > establish its geometry. Geometry is only (really) relevant for > > processing the MBR. Instead, the driver will fake some sensible > > falues. > > > > > sd0: NOT READY asc:3a,0 Medium not present > > > sd0: could not get size > > > 0MB (0 512 byte sectors) > > > > The driver has attempted to interrogate the drive to obtain its total > > size in sectors. The drive reports an error because you haven't > > inserted a disk. This is common for removables, particularly those > > that support more than one media size. > > > > > sd0: with 0 cyls, 64 heads, and an average 32 sectors/track > > > > And this is the resultant fake geometry, given a size of 0 sectors. It's > > good enough. > > Is this in non-verbose boot mode? It really seem to be completely unneeded > information, which should be hidden behind the verbose flag. Don't you guys You want to hide SCSI errors behind the verbose flag? This is not the right way to go at all. Yes, you could argue that in the case of removables, different handling of certain errors would cut down on console traffic, but as a general rule, if there's something unhappy going on on the SCSI bus I'd prefer to know about it. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 03:52:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19659 for hackers-outgoing; Sat, 19 Jul 1997 03:52:32 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19653 for ; Sat, 19 Jul 1997 03:52:27 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA13690; Sat, 19 Jul 1997 20:22:21 +0930 (CST) From: Michael Smith Message-Id: <199707191052.UAA13690@genesis.atrad.adelaide.edu.au> Subject: Re: What interrupts to mask in my device driver?? In-Reply-To: <199707190101.SAA23276@agni.nuko.com> from Vinay Bannai at "Jul 18, 97 06:01:29 pm" To: vinay@agni.nuko.com (Vinay Bannai) Date: Sat, 19 Jul 1997 20:22:21 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Vinay Bannai stands accused of saying: > - Before calling pci_map_mem() and pci_map_int(), I noticed that David > Greenman has disabled network device interrupts. What interrupts should > I disable on the device that I have? Here are the details of my device Anything that's likely to pop up and disturb you or your hardware. Typically you would ensure that your own interrupt handler couldn't be called, or any other interrupt handler that might upset what you're doing. > from the probe routine. Currently I am not disabling any interrupts and > it seems to attach okay.. It may be that this is all you need. > - Next question: Are there any freely available gcc cross compilers for > i960 Kx architecture? You should be able to use the stock gcc distribution for this. If you need a C runtime library, the Cygnus 'newlib' is pretty good. > Vinay -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 03:55:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19699 for hackers-outgoing; Sat, 19 Jul 1997 03:55:12 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19694 for ; Sat, 19 Jul 1997 03:55:06 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA13703; Sat, 19 Jul 1997 20:24:56 +0930 (CST) From: Michael Smith Message-Id: <199707191054.UAA13703@genesis.atrad.adelaide.edu.au> Subject: Re: HP LaserJet 6L In-Reply-To: <01BC939C.46CF4020.Al.Johnson@AJC.State.Net> from Al Johnson at "Jul 18, 97 05:01:46 pm" To: Al.Johnson@AJC.State.Net (Al Johnson) Date: Sat, 19 Jul 1997 20:24:55 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Al Johnson stands accused of saying: > > I'm trying to migrate all my ciritical functions from Win95 to FreeBSD. > Ya, I hear you all groaning now :) Since I'm no expert at this, been a > long time since I was a unix sysadmin, I need assistance with the filters > needed for this printer. I have successfully printed plain text on the > HP from the directly connected system sort of. An lptest > /dev/lpt0 > gets me a sheet of paper with a single line printed on it. Obvisouly not > what it's supposed to generate. Anyone with a filter or an adequate printcap > definition for this (or just about any PCL) printer I would really appreciate > an email copy. I _strongly_ recommend using apsfilter for this. It automates prettymuch the entire process. (It's in the ports collection) > In addition, is there any special setup required to get the appropriate > conversion from a Win95 print job to the printer via Samba? If you're using apsfilter, you can tell Windows that it's a generic postscript printer, or you can use a printer-specific driver. The latter method is probably a little better. There's no special conversion required, just set Samba up to talk to the printer as per the Samba documentation. > -- Al > -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 04:07:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA20006 for hackers-outgoing; Sat, 19 Jul 1997 04:07:48 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA19989 for ; Sat, 19 Jul 1997 04:07:40 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id NAA10871; Sat, 19 Jul 1997 13:00:20 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.6/8.8.6) id MAA04192; Sat, 19 Jul 1997 12:51:19 +0200 (CEST) Message-ID: <19970719125118.60102@gtn.com> Date: Sat, 19 Jul 1997 12:51:18 +0200 From: Andreas Klemm To: sthaug@nethelp.no Cc: andreas@klemm.gtn.com, hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file References: <19970719120826.19772@gtn.com> <15406.869308066@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <15406.869308066@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Jul 19, 1997 at 12:27:46PM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Jul 19, 1997 at 12:27:46PM +0200, sthaug@nethelp.no wrote: > > > I'm always nervous about directories owned by bin, on the assumption > > > that bin might be easier to break than root, and could then be used > > > as a stepstone to breaking root. > > > > I don't believe this, because bin isn't a password protected login. > > Look here: > > bin:*:3:7:Binaries Commands and Source,,,:/:/nonexistent > > That's fine - until somebody decides to run NFS. Then all bets are off. Ok, I understand. But this szenario only arise, if a system administrator decides to put a site into a hosts.equiv file. And yes, you are right, then people could start to 'hack' the server by making the clients ,bin' account to a login account, and if /var should be exported, then files or directories could be renamed or such ... It would be safer, to change the owner of system binaries and directories to root, since then you could put hosts more safely into the /etc/hosts.equiv file. You would have to add the -root export option, so that the NFS server's exported directories could be compromised. -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Jul 19 04:51:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA21773 for hackers-outgoing; Sat, 19 Jul 1997 04:51:59 -0700 (PDT) Received: from Hydro.CAM.ORG (Hydro.CAM.ORG [198.168.100.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21742; Sat, 19 Jul 1997 04:51:51 -0700 (PDT) Received: from 1 (DynamicPPP-193.HIP.CAM.ORG [205.151.119.193]) by Hydro.CAM.ORG (8.8.4/8.8.4) with ESMTP id HAA18548; Sat, 19 Jul 1997 07:51:42 -0400 (EDT) Message-ID: <33D0AA62.56ED3612@coproductions.com> Date: Sat, 19 Jul 1997 07:52:02 -0400 From: Jean-Marc Felio Reply-To: Reply-to-Felio@coproductions.com X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: Ragan Slawomir CC: "\"'freebsd-bugs@freebsd.org'\"" , "freebsd-chat@FreeBSD.ORG" , "freebsd-current@FreeBSD.ORG" , "freebsd-multimedia@FreeBSD.ORG" , "freebsd-questions@FreeBSD.ORG" , "hackers@FreeBSD.ORG" , "owner-hackers@FreeBSD.ORG" , "questions@FreeBSD.ORG" , freebsd-bugs@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, "\"freebsd-chat@FreeBSD.ORG\"" , "\"freebsd-current@FreeBSD.ORG\"" , freebsd-multimedia@FreeBSD.ORG Subject: unsubscribe X-Priority: 3 (Normal) References: <9707171549.ZM21695@liza.trier.fh-rpl.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Sat Jul 19 05:21:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23072 for hackers-outgoing; Sat, 19 Jul 1997 05:21:44 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA23062 for ; Sat, 19 Jul 1997 05:21:39 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id OAA21158 for hackers@FreeBSD.ORG; Sat, 19 Jul 1997 14:15:12 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.6/8.8.6) id NAA02691; Sat, 19 Jul 1997 13:28:38 +0200 (CEST) Message-ID: <19970719132838.54020@gtn.com> Date: Sat, 19 Jul 1997 13:28:38 +0200 From: Andreas Klemm To: Andreas Klemm Cc: hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file References: <19970718172709.25620@gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <19970718172709.25620@gtn.com>; from Andreas Klemm on Fri, Jul 18, 1997 at 05:27:09PM +0200 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 18, 1997 at 05:27:09PM +0200, Andreas Klemm wrote: > Sendmail couldn't write his /var/run/sendmail.pid file. > I saw this behaviour in FreeBSD 2.2.2 and -current. > > I think the newest sendmail version introduces this. > It's important, that every directory is owned by root. Hmm, I re-changed /var/tmp to permissions bin.bin and couldn't reproduce the problem :-/ -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Sat Jul 19 05:42:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24073 for hackers-outgoing; Sat, 19 Jul 1997 05:42:15 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24062 for ; Sat, 19 Jul 1997 05:42:11 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.6/8.8.5) id OAA28753; Sat, 19 Jul 1997 14:41:49 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199707191241.OAA28753@helbig.informatik.ba-stuttgart.de> Subject: Re: sendmail complains about being unable to write his pid file In-Reply-To: <15406.869308066@verdi.nethelp.no> from "sthaug@nethelp.no" at "Jul 19, 97 12:27:46 pm" To: sthaug@nethelp.no Date: Sat, 19 Jul 1997 14:41:47 +0200 (MET DST) Cc: andreas@klemm.gtn.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I'm always nervous about directories owned by bin, on the assumption > > > that bin might be easier to break than root, and could then be used > > > as a stepstone to breaking root. > > > > I don't believe this, because bin isn't a password protected login. > > Look here: > > bin:*:3:7:Binaries Commands and Source,,,:/:/nonexistent > > That's fine - until somebody decides to run NFS. Then all bets are off. > > > I think it's a BSDism. bin is the UID and GID for Binaries, Commands > > and source as shown by the entry in /etc/passwd ... > > Yes, but the question stands - why is it setup this way? What is gained > by having binaries (and important directories) owned by bin instead of > root? More security? setuid / setgid will give you the powers of bin only, not of root. Wolfgang From owner-freebsd-hackers Sat Jul 19 05:53:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24544 for hackers-outgoing; Sat, 19 Jul 1997 05:53:49 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA24521; Sat, 19 Jul 1997 05:53:39 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA18801; Sat, 19 Jul 1997 13:46:57 +0200 From: Luigi Rizzo Message-Id: <199707191146.NAA18801@labinfo.iet.unipi.it> Subject: Re: snd driver attach routine To: bde@zeta.org.au (Bruce Evans) Date: Sat, 19 Jul 1997 13:46:57 +0200 (MET DST) Cc: hasty@rah.star-gate.com, bde@zeta.org.au, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG, rhh@ct.picker.com, se@FreeBSD.ORG In-Reply-To: <199707190643.QAA29949@godzilla.zeta.org.au> from "Bruce Evans" at Jul 19, 97 04:43:13 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >I think I get the rationale for not testing return value in the attach > >routine. > > > >After the probe you (should) know that the peripheral is there. A > >failure to attach should then depend only on os problems (typically, > >failure to allocate resources such as memory, dma, irq, or a device > >descriptor). Since no resource allocation was in the probe, the routine > >calling the attach has nothing to do on failure -- all deallocations > >should be done in the attach routine being device specific. > > In practice, for isa devices the IRQ allocation is done in generic code, > so the probe status is necessary (but not used). ^^^^^ you mean attach I guess... but in isa.c I see the following piece of code: ... isdp->id_alive = id_alive; } (*dp->attach)(isdp); if (isdp->id_irq) { if (mp) INTRMASK(*mp, isdp->id_irq); register_intr(ffs(isdp->id_irq) - 1, isdp->id_id, isdp->id_ri_flags, isdp->id_intr, mp, isdp->id_unit); INTREN(isdp->id_irq); } ... so all the necessary info is in the id_irq field of the struct isa_device -- a device which does not attach properly could just zero this field. > >Secondly, if I am not mistaken, once you create a device entry in the > >fs with a major number corresponding to an existing device, the > >routines for the devices are always invoked and they have to check the > >minor dev anyways to see if it corresponds to a configured device. > > This is a bug. Drivers whose probe or attach can fail should not use > SYSINIT() to register their device switches. it is not a bug, it is a need. A device switch (registered with SYSINIT) serves for a device _type_, but you can have several units of the same type (hence with the same major number), so you have to check the minor number anyways. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Sat Jul 19 06:37:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA25831 for hackers-outgoing; Sat, 19 Jul 1997 06:37:15 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA25825 for ; Sat, 19 Jul 1997 06:37:11 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id XAA06005; Sat, 19 Jul 1997 23:36:50 +1000 (EST) Date: Sat, 19 Jul 1997 23:36:49 +1000 (EST) From: "Daniel O'Callaghan" To: Wolfgang Helbig cc: sthaug@nethelp.no, andreas@klemm.gtn.com, hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file In-Reply-To: <199707191241.OAA28753@helbig.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 19 Jul 1997, Wolfgang Helbig wrote: > > Yes, but the question stands - why is it setup this way? What is gained > > by having binaries (and important directories) owned by bin instead of > > root? > > More security? setuid / setgid will give you the powers of bin > only, not of root. If you gain access to bin, you can write a tojan 'ls', or other command likely to be run by root. Danny From owner-freebsd-hackers Sat Jul 19 06:56:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA26362 for hackers-outgoing; Sat, 19 Jul 1997 06:56:24 -0700 (PDT) Received: from relay6.UU.NET (relay6.UU.NET [192.48.96.16]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA26357 for ; Sat, 19 Jul 1997 06:56:21 -0700 (PDT) Received: from rodan.UU.NET by relay6.UU.NET with ESMTP (peer crosschecked as: rodan.UU.NET [153.39.130.10]) id QQcywl03259; Sat, 19 Jul 1997 09:56:28 -0400 (EDT) Received: from localhost by rodan.UU.NET with SMTP (peer crosschecked as: mo@localhost) id QQcywl13112; Sat, 19 Jul 1997 09:56:19 -0400 (EDT) Message-Id: To: Michael Smith cc: mo@UU.NET (Mike O'Dell), hackers@freebsd.org Subject: Re: SMBIOS/DMI etc In-reply-to: Your message of "Sat, 19 Jul 1997 17:39:43 +0930." <199707190809.RAA13184@genesis.atrad.adelaide.edu.au> Date: Sat, 19 Jul 1997 09:56:19 -0400 From: "Mike O'Dell" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk yeah, i'm gonna take a hack at it. reading the info shouldn't be hard. it's just a couple of ISA IO ports (usual "address" and "value" stupidity). it can do interrupts to either ISA or SMI. i haven't checked for certain, but i'd put a six-pack of beer that the BIOS programs it for SMI interrupts. at the moment, i'm trying to print the LM78 data sheets (on www.national.com as a PDF file) but Acrobat generates broken postscript!!! GRRRRRRRRRRRRR..... i may have to fire up latest ghostview to get it printed!! BTW - has there been any thought to using the SMI mode? it essentially gives you one mostly-virtual processor. -mo From owner-freebsd-hackers Sat Jul 19 07:32:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA27466 for hackers-outgoing; Sat, 19 Jul 1997 07:32:02 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA27444 for ; Sat, 19 Jul 1997 07:31:57 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA14199; Sun, 20 Jul 1997 00:01:49 +0930 (CST) From: Michael Smith Message-Id: <199707191431.AAA14199@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: from Mike O'Dell at "Jul 19, 97 09:56:19 am" To: mo@UU.NET (Mike O'Dell) Date: Sun, 20 Jul 1997 00:01:49 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mo@UU.NET, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike O'Dell stands accused of saying: > > reading the info shouldn't be hard. it's just a couple > of ISA IO ports (usual "address" and "value" stupidity). it can > do interrupts to either ISA or SMI. i haven't checked for certain, > but i'd put a six-pack of beer that the BIOS programs it for SMI > interrupts. OK. As long as it doesn't have one of those stupid "lock configuration" bits, all will be well. > at the moment, i'm trying to print the LM78 data sheets > (on www.national.com as a PDF file) but Acrobat generates > broken postscript!!! GRRRRRRRRRRRRR..... It does? Prints fine here to an HP JLIII ps cart or via ghostscript. Try fiddling the level 1/level 2 option. > BTW - has there been any thought to using the SMI mode? > it essentially gives you one mostly-virtual processor. I'm not sure I follow you here. All the SMI information I have applies to the sucky SMI calling interface and function list (16-bit protected mode? Who do they think they're kidding?) If you have more documentation references, I'm all ears. If it's of any interest to you, the bios32 code I was working on (knows how to locate the SMIBIOS and DMI tables in the BIOS image) is available at ftp://smith.net.au/misc/bios32/. It's mostly just a signature-hunter and some structure definitions. Stick bios32.c in i386/i386 and bios32.h in i386/include, add bios32.c to files.i386 and reconfig your kernel. It'll search for a BIOS32 Service Directory and then the _SM_ and _DMI_ cookies as well. If you _do_ turn out to have a BIOS32 Service Directory, it'd be great if you could : - change the #if 0 in bios32_init() to #if 1 - build a new (test) kernel - boot to ddb (boot with -d) - set a breakpoint : `break bios32_SDlookup' - run to the breakpoint : `cont' - single-step through the BIOS routine that this calls and make a note of the value(s) that it compares %eax with. The reason I ask is just to attempt to identify whether the BIOS32 thing ever took off; I can't find _diddly_ about it online, but it does appear to be reasonably widely implemented. Sorry for the handholding ddb-walkthrough above; not sure how deep your experience with it goes. Note that you should expect a GPF when the BIOS routine tries to return; I don't know why. > -mo -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 07:37:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA27796 for hackers-outgoing; Sat, 19 Jul 1997 07:37:03 -0700 (PDT) Received: from prova.iet.unipi.it (prova1.iet.unipi.it [131.114.9.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA27773; Sat, 19 Jul 1997 07:36:50 -0700 (PDT) Received: (from luigi@localhost) by prova.iet.unipi.it (8.8.5/8.8.5) id QAA01053; Sat, 19 Jul 1997 16:37:50 +0200 (CEST) From: Luigi Rizzo Message-Id: <199707191437.QAA01053@prova.iet.unipi.it> Subject: dma handling in the sound driver To: hackers@freebsd.org, multimedia@freebsd.org Date: Sat, 19 Jul 1997 16:37:50 +0200 (CEST) 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have planned to rewrite the dma buffer handling routines for the sound driver as follows. To me this seems reasonably simple and efficient. Can you please have a look at this high-level description of the problem (including some pseudo-code, very close to the actual implementation) and tell if this looks reasonable ? (this description will also go into the source files, so hopefully people will not have a hard time in understanding how it works...) Thanks Luigi ------- The main problem with the DMA in the sound driver is to avoid that the flow of data from/to the codec is interrupted, resulting in missing samples or clicks. The problem is dealt with at several levels. 1) within the sound card, there is some amount of buffering (e.g. a FIFO, or on-board memory, etc.) so as to overcome occasional periods when the user process is slow. 2) some amount of buffering must be supplied in the driver as well, for those boards (many) which do not have enough buffering. Even in presence of buffering, there might be problems when the current DMA operation terminates and a new one is restarted. In fact: - if we use a single DMA buffer, we need the time to refill it before starting the next op. The largest the buffer (and the size of the block being transferred), the longest is the idle time; - with two DMA buffers, we can refill one buffer while the other one is in use by the DMA engine. We can still have troubles if we start a long refill near the end of operation of DMA on the other buffer, but this problem can be minimized (but not avoided; if we are late, we are late, no matter how many buffers we have!) In our implementation, we use a single memory block structured as three logical, variable-size, buffers: one in use by the dma engine, the next one ready for use by the dma (already filled up), the last one free for refills. dp,dl rp,rl fp,fl +-------+-------------+---------------+------+ | free | used by dma | ready for use | free | +-------+-------------+---------------+------+ Both the "ready" and "free" areas can wrap around the end of the buffer. The "dma" are Three pointers (dp, rp, fp) and three length (dl, rl, fl) are used for the purpose. At initialization: dp = rp = fp = 0 ; /* beginning of buffer */ dl = 0 ; /* meaning no dma activity) */ rl = 0 ; /* meaning no data ready */ fl = bufsize ; Upon dma_interrupt(), we try to use the next buffer if possible: s=splhigh(); fl += dl ; dp = rp ; dl = 0 ; if (rl > 0) { dl = min(rl, bufsize - rp ) ; /* do not wrap */ rl -= dl ; rp += dl ; if (rp == bufsize) rp = 0; /* * now try to avoid too small dma transfers in the near future. * This can happen if I let rp start too close to the end of * the buffer. If this happens, and have enough data, try to * split the available block in two approx. equal parts. */ if (bufsize - rp < MIN_DMA_SIZE && bufsize - dp > 2*MIN_DMA_SIZE) { dl = (bufsize - dp) / 2; rl += (rp - (dp + dl) ) ; rp = dp + dl ; } restart_dma(); } splx(s) Upon user_write() for n bytes we copy data into the free buffer and then extend the ready block. Instead of doing all the copy at once, we start with small pieces in order to minimize the chance of a starvation. The size of the smallest chunk is chosen in a way that the execution time of uiomove is still dominated by the constant part. bsz = 64 ; /* min block size */ while (n>0) { int l = min (n, bsz); l = min (l, fl); l = min (l, bufsize - fp ); uiomove(buf, .. , l); s=splhigh(); rl += l ; fl -= l ; fp += l ; if (fp == bufsize) fp = 0 ; if (rl == l) { dl = rl ; restart_dma(); } splx(s); if (fl == 0) { /* buffer full, must sleep */ tsleep( ... ); /* handle errors etc. */ } bsz = min(bufsize, bsz*2); } ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-hackers Sat Jul 19 07:40:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA28015 for hackers-outgoing; Sat, 19 Jul 1997 07:40:32 -0700 (PDT) Received: from csla.csl.sri.com (csla.csl.sri.com [192.12.33.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA28009 for ; Sat, 19 Jul 1997 07:40:30 -0700 (PDT) Received: from japonica.csl.sri.com (japonica.csl.sri.com [130.107.15.17]) by csla.csl.sri.com (8.8.5/8.8.5) with ESMTP id HAA02814 for ; Sat, 19 Jul 1997 07:36:34 -0700 (PDT) Received: from japonica.csl.sri.com (localhost.csl.sri.com [127.0.0.1]) by japonica.csl.sri.com (8.8.5/8.7.3) with ESMTP id HAA12910 for ; Sat, 19 Jul 1997 07:39:51 -0700 (PDT) Message-Id: <199707191439.HAA12910@japonica.csl.sri.com> to: hackers@FreeBSD.ORG Subject: NFS wierdness? Date: Sat, 19 Jul 1997 07:39:51 -0700 From: Fred Gilham Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have this user who runs programs that generate lots of output to stdout. The output sometimes contains very long `lines'---long stretches of output without a newline. The programs are also supposed to be very CPU intensive. Most of the time he invokes them like this: user-program >> output Unfortunately when he does this on a FreeBSD box where the directory he's writing to is NFS mounted, he gets almost no CPU time; the process spends most of its time in the `nfsfsy' state (according to top). Here's a program that basically simulates the user's programs: ---------------------------------------- #include int main(int argc, char *argv[]) { long rnum = rand(); long i; while(1) { for(i = 0; i < 10000; rnum = rand(), i++) { printf("%ld ", rnum); } fflush(stdout); /* Soak up some CPU time. */ for(i = 0; i < 1000000; i++) rnum *= rnum; } } ---------------------------------------- I called the program `tester' for FreeBSD and `tester.sol' for the ultrasparc. Here's a top output line for a FreeBSD-2.2.2 box running on a Pentium Pro 200: 16639 gilham -5 0 148K 300K nfsfsy 0:10 16.18% 15.49% tester Here's one on an Ultrasparc 167MhZ: 6755 gilham -25 0 736K 584K run 0:42 36.86% 87.84% tester.sol This gives an idea of the problem; usually the user sees 98% cpu utilization on an ultrasparc and around 2% on a FreeBSD box. Both of these boxes are on the same network segment as the directory they're writing to. They were invoked as follows: tester >> dummy and tester.sol >> dummy Another symptom of the problem is that it's not possible to get any output from tail -f dummy on the same box that's running on tester program under FreeBSD. However, solaris has no problems. Just for comparison we also tried invoking the program as tester > dummy This gave somewhat better results: 16792 gilham 47 0 148K 300K RUN 0:21 27.21% 26.66% tester but the program still spent a lot of time in the `nfsaio' state. With the user's program he saw a similar improvement---from 2% to 4%. But still not very useful. Here's the solaris top line by comparison: 6772 gilham -25 0 736K 584K run 1:00 52.97% 94.41% tester.sol The bottom line is that the user's program runs really slowly under FreeBSD when he tries to save the output to an nfs-mounted directory. Does anyone have any suggestions as to what might be going on? -Fred Gilham gilham@csl.sri.com From owner-freebsd-hackers Sat Jul 19 07:53:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA28381 for hackers-outgoing; Sat, 19 Jul 1997 07:53:55 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA28376 for ; Sat, 19 Jul 1997 07:53:52 -0700 (PDT) Received: from dbws.etinc.com (dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id LAA06757 for ; Sat, 19 Jul 1997 11:01:03 -0400 (EDT) Message-Id: <3.0.32.19970719105230.00740168@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 19 Jul 1997 10:52:36 -0400 To: hackers@freebsd.org From: Dennis Subject: fxpX: warning: unsupported PHY, type = 7, addr = 1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any patch forthcoming for this message? Its a little embarrassing recommending a card and the first thing they get is a bunch of "unsupported" warning messages. Dennis From owner-freebsd-hackers Sat Jul 19 08:03:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28728 for hackers-outgoing; Sat, 19 Jul 1997 08:03:57 -0700 (PDT) Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA28722 for ; Sat, 19 Jul 1997 08:03:51 -0700 (PDT) Received: from rodan.UU.NET by relay1.UU.NET with ESMTP (peer crosschecked as: rodan.UU.NET [153.39.130.10]) id QQcywq23961; Sat, 19 Jul 1997 11:02:53 -0400 (EDT) Received: from localhost by rodan.UU.NET with SMTP (peer crosschecked as: mo@localhost) id QQcywq17534; Sat, 19 Jul 1997 11:02:43 -0400 (EDT) Message-Id: To: Michael Smith cc: mo@UU.NET, hackers@freebsd.org Subject: Re: SMBIOS/DMI etc In-reply-to: Your message of "Sun, 20 Jul 1997 00:01:49 +0930." <199707191431.AAA14199@genesis.atrad.adelaide.edu.au> Date: Sat, 19 Jul 1997 11:02:43 -0400 From: "Mike O'Dell" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i know the latest Linux kernels do the BIOS32 thing -mo From owner-freebsd-hackers Sat Jul 19 08:12:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA29040 for hackers-outgoing; Sat, 19 Jul 1997 08:12:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA29034; Sat, 19 Jul 1997 08:12:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA14340; Sun, 20 Jul 1997 00:42:09 +0930 (CST) From: Michael Smith Message-Id: <199707191512.AAA14340@genesis.atrad.adelaide.edu.au> Subject: Re: SMBIOS/DMI etc In-Reply-To: from Mike O'Dell at "Jul 19, 97 11:02:43 am" To: mo@UU.NET (Mike O'Dell) Date: Sun, 20 Jul 1997 00:42:09 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, mo@UU.NET, hackers@freebsd.org, se@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mike O'Dell stands accused of saying: > > i know the latest Linux kernels do the BIOS32 thing Yes, I've been reading what code I can find. Anyone have a reference to a hyperlinked Linux kernel source online? Stefan, do you have any interest in using the PCI BIOS as well as/instead of doing things the "hard way" as is done at the moment? > -mo -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 19 08:31:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA29650 for hackers-outgoing; Sat, 19 Jul 1997 08:31:26 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA29645 for ; Sat, 19 Jul 1997 08:31:24 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA20004; Sat, 19 Jul 1997 08:33:29 -0700 (PDT) Message-Id: <199707191533.IAA20004@implode.root.com> To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: fxpX: warning: unsupported PHY, type = 7, addr = 1 In-reply-to: Your message of "Sat, 19 Jul 1997 10:52:36 EDT." <3.0.32.19970719105230.00740168@etinc.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 19 Jul 1997 08:33:29 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Any patch forthcoming for this message? Its a little embarrassing recommending >a card and the first thing they get is a bunch of "unsupported" warning >messages. A fix was committed to 2.2-stable and -current more than a month ago. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project Index: if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.21.2.7 diff -c -r1.21.2.7 if_fxp.c *** if_fxp.c 1997/04/23 01:49:12 1.21.2.7 --- if_fxp.c 1997/06/13 07:45:42 *************** *** 961,975 **** csr->scb_command = FXP_SCB_COMMAND_RU_START; /* ! * Toggle a few bits in the DP83840 PHY. */ ! if (sc->phy_primary_device == FXP_PHY_DP83840 || ! sc->phy_primary_device == FXP_PHY_DP83840A) { fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_DP83840_PCR, fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_DP83840_PCR) | FXP_DP83840_PCR_LED4_MODE | /* LED4 always indicates duplex */ FXP_DP83840_PCR_F_CONNECT | /* force link disconnect bypass */ FXP_DP83840_PCR_BIT10); /* XXX I have no idea */ /* * If link0 is set, disable auto-negotiation and then: * If link1 is unset = 10Mbps --- 961,978 ---- csr->scb_command = FXP_SCB_COMMAND_RU_START; /* ! * Toggle a few bits in the PHY. */ ! switch (sc->phy_primary_device) { ! case FXP_PHY_DP83840: ! case FXP_PHY_DP83840A: fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_DP83840_PCR, fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_DP83840_PCR) | FXP_DP83840_PCR_LED4_MODE | /* LED4 always indicates duplex */ FXP_DP83840_PCR_F_CONNECT | /* force link disconnect bypass */ FXP_DP83840_PCR_BIT10); /* XXX I have no idea */ + /* fall through */ + case FXP_PHY_82555: /* * If link0 is set, disable auto-negotiation and then: * If link1 is unset = 10Mbps *************** *** 981,999 **** int flags; flags = (ifp->if_flags & IFF_LINK1) ? ! FXP_DP83840_BMCR_SPEED_100M : 0; flags |= (ifp->if_flags & IFF_LINK2) ? ! FXP_DP83840_BMCR_FULLDUPLEX : 0; ! fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_DP83840_BMCR, ! (fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_DP83840_BMCR) & ! ~(FXP_DP83840_BMCR_AUTOEN | FXP_DP83840_BMCR_SPEED_100M | ! FXP_DP83840_BMCR_FULLDUPLEX)) | flags); } else { ! fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_DP83840_BMCR, ! (fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_DP83840_BMCR) | ! FXP_DP83840_BMCR_AUTOEN)); } ! } else { printf("fxp%d: warning: unsupported PHY, type = %d, addr = %d\n", ifp->if_unit, sc->phy_primary_device, sc->phy_primary_addr); } --- 984,1003 ---- int flags; flags = (ifp->if_flags & IFF_LINK1) ? ! FXP_PHY_BMCR_SPEED_100M : 0; flags |= (ifp->if_flags & IFF_LINK2) ? ! FXP_PHY_BMCR_FULLDUPLEX : 0; ! fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_PHY_BMCR, ! (fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_PHY_BMCR) & ! ~(FXP_PHY_BMCR_AUTOEN | FXP_PHY_BMCR_SPEED_100M | ! FXP_PHY_BMCR_FULLDUPLEX)) | flags); } else { ! fxp_mdi_write(sc->csr, sc->phy_primary_addr, FXP_PHY_BMCR, ! (fxp_mdi_read(sc->csr, sc->phy_primary_addr, FXP_PHY_BMCR) | ! FXP_PHY_BMCR_AUTOEN)); } ! break; ! default: printf("fxp%d: warning: unsupported PHY, type = %d, addr = %d\n", ifp->if_unit, sc->phy_primary_device, sc->phy_primary_addr); } Index: if_fxpreg.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxpreg.h,v retrieving revision 1.3.2.3 diff -c -r1.3.2.3 if_fxpreg.h *** if_fxpreg.h 1997/03/21 08:01:52 1.3.2.3 --- if_fxpreg.h 1997/06/13 07:38:42 *************** *** 292,306 **** #define FXP_PHY_DP83840 4 #define FXP_PHY_80C240 5 #define FXP_PHY_80C24 6 #define FXP_PHY_DP83840A 10 /* ! * DP84830 PHY, BMCR Basic Mode Control Register */ ! #define FXP_DP83840_BMCR 0x0 ! #define FXP_DP83840_BMCR_FULLDUPLEX 0x0100 ! #define FXP_DP83840_BMCR_AUTOEN 0x1000 ! #define FXP_DP83840_BMCR_SPEED_100M 0x2000 /* * DP84830 PHY, PCS Configuration Register --- 292,307 ---- #define FXP_PHY_DP83840 4 #define FXP_PHY_80C240 5 #define FXP_PHY_80C24 6 + #define FXP_PHY_82555 7 #define FXP_PHY_DP83840A 10 /* ! * PHY BMCR Basic Mode Control Register */ ! #define FXP_PHY_BMCR 0x0 ! #define FXP_PHY_BMCR_FULLDUPLEX 0x0100 ! #define FXP_PHY_BMCR_AUTOEN 0x1000 ! #define FXP_PHY_BMCR_SPEED_100M 0x2000 /* * DP84830 PHY, PCS Configuration Register From owner-freebsd-hackers Sat Jul 19 11:20:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05896 for hackers-outgoing; Sat, 19 Jul 1997 11:20:09 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05891 for ; Sat, 19 Jul 1997 11:20:06 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id UAA00487 for ; Sat, 19 Jul 1997 20:20:07 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id UAA04468 for hackers@FreeBSD.ORG; Sat, 19 Jul 1997 20:19:53 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id TAA06347; Sat, 19 Jul 1997 19:55:57 +0200 (CEST) Message-ID: <19970719195557.20490@keltia.freenix.fr> Date: Sat, 19 Jul 1997 19:55:57 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file References: <19970719120826.19772@gtn.com> <15406.869308066@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <15406.869308066@verdi.nethelp.no>; from sthaug@nethelp.no on Sat, Jul 19, 1997 at 12:27:46PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3461 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to sthaug@nethelp.no: > Yes, but the question stands - why is it setup this way? What is gained > by having binaries (and important directories) owned by bin instead of > root? See the archive of at least hackers & security for many discussions about this. I've patched by bsd.own.mk and mtree/* files to makes everything owned by root.wheel. Nothing is gained IMO by using bin.bin and it is making easier to put a trojan somewhere. Patch available. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #22: Sun Jul 13 22:07:09 CEST 1997 From owner-freebsd-hackers Sat Jul 19 11:45:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06924 for hackers-outgoing; Sat, 19 Jul 1997 11:45:32 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06907; Sat, 19 Jul 1997 11:45:26 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id LAA17575; Sat, 19 Jul 1997 11:45:07 -0700 (PDT) Message-Id: <199707191845.LAA17575@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Luigi Rizzo cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: dma handling in the sound driver In-reply-to: Your message of "Sat, 19 Jul 1997 16:37:50 +0200." <199707191437.QAA01053@prova.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Jul 1997 11:45:06 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lets take a case example the dma algorithm from the current sound driver for the SB16 dmabuf splits a pool of continous memory into N buffers where each buffer can hold upto a 1/2 second. auto dma is chosen. In the case of playing sun style au files recorded at 8khz , the size of a buffer is 4096 , 1/2 seconds worth. The dma auto init pool size is taken from a sound driver constant which is usually a multiple of 4k for our example the dma auto init buffer is 32k. A high level audio write routine whose buffer count usually is a bigger than 32k , breaks up the the write request in 4096 bytes buffers. The sound card loops on its auto init dma buffer as well as the sound driver's dma buffer routines. Cheers, Amancio >From The Desk Of Luigi Rizzo : > I have planned to rewrite the dma buffer handling routines for > the sound driver as follows. > > To me this seems reasonably simple and efficient. Can you please > have a look at this high-level description of the problem (including some > pseudo-code, very close to the actual implementation) and tell if this > looks reasonable ? > > (this description will also go into the source files, so hopefully > people will not have a hard time in understanding how it works...) > > Thanks > Luigi > > ------- > > > The main problem with the DMA in the sound driver is to avoid that the > flow of data from/to the codec is interrupted, resulting in missing > samples or clicks. The problem is dealt with at several levels. > > 1) within the sound card, there is some amount of buffering (e.g. a > FIFO, or on-board memory, etc.) so as to overcome occasional > periods when the user process is slow. > > 2) some amount of buffering must be supplied in the driver as well, > for those boards (many) which do not have enough buffering. > > Even in presence of buffering, there might be problems when the > current DMA operation terminates and a new one is restarted. In fact: > - if we use a single DMA buffer, we need the time to refill it before > starting the next op. The largest the buffer (and the size of the > block being transferred), the longest is the idle time; > - with two DMA buffers, we can refill one buffer while the other one > is in use by the DMA engine. We can still have troubles if we start > a long refill near the end of operation of DMA on the other buffer, > but this problem can be minimized (but not avoided; if we are late, > we are late, no matter how many buffers we have!) > > In our implementation, we use a single memory block structured as > three logical, variable-size, buffers: one in use by the dma engine, > the next one ready for use by the dma (already filled up), the last > one free for refills. > > dp,dl rp,rl fp,fl > +-------+-------------+---------------+------+ > | free | used by dma | ready for use | free | > +-------+-------------+---------------+------+ > > Both the "ready" and "free" areas can wrap around the end of the > buffer. The "dma" are > > Three pointers (dp, rp, fp) and three length (dl, rl, fl) are used for > the purpose. > > At initialization: > dp = rp = fp = 0 ; /* beginning of buffer */ > dl = 0 ; /* meaning no dma activity) */ > rl = 0 ; /* meaning no data ready */ > fl = bufsize ; > > Upon dma_interrupt(), we try to use the next buffer if possible: > > s=splhigh(); > fl += dl ; > dp = rp ; > dl = 0 ; > if (rl > 0) { > dl = min(rl, bufsize - rp ) ; /* do not wrap */ > rl -= dl ; > rp += dl ; > if (rp == bufsize) rp = 0; > /* > * now try to avoid too small dma transfers in the near future. > * This can happen if I let rp start too close to the end of > * the buffer. If this happens, and have enough data, try to > * split the available block in two approx. equal parts. > */ > if (bufsize - rp < MIN_DMA_SIZE && bufsize - dp > 2*MIN_DMA_SIZE) { > dl = (bufsize - dp) / 2; > rl += (rp - (dp + dl) ) ; > rp = dp + dl ; > } > restart_dma(); > } > splx(s) > > Upon user_write() for n bytes we copy data into the free buffer and > then extend the ready block. Instead of doing all the copy at once, we > start with small pieces in order to minimize the chance of a > starvation. The size of the smallest chunk is chosen in a way that the > execution time of uiomove is still dominated by the constant part. > > bsz = 64 ; /* min block size */ > while (n>0) { > int l = min (n, bsz); > l = min (l, fl); > l = min (l, bufsize - fp ); > uiomove(buf, .. , l); > s=splhigh(); > rl += l ; > fl -= l ; > fp += l ; > if (fp == bufsize) fp = 0 ; > if (rl == l) { > dl = rl ; > restart_dma(); > } > splx(s); > if (fl == 0) { /* buffer full, must sleep */ > tsleep( ... ); > /* handle errors etc. */ > } > bsz = min(bufsize, bsz*2); > } > > ==================================================================== > Luigi Rizzo Dip. di Ingegneria dell'Informazione > email: luigi@iet.unipi.it Universita' di Pisa > tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) > fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ > ==================================================================== From owner-freebsd-hackers Sat Jul 19 12:35:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08502 for hackers-outgoing; Sat, 19 Jul 1997 12:35:26 -0700 (PDT) Received: from cedb.dpcsys.com (cedb.DPCSYS.com [209.25.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08495 for ; Sat, 19 Jul 1997 12:35:20 -0700 (PDT) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id TAA05276; Sat, 19 Jul 1997 19:34:53 GMT Date: Sat, 19 Jul 1997 12:34:53 -0700 (PDT) From: Dan Busarow To: Andreas Klemm cc: hackers@FreeBSD.ORG Subject: Re: sendmail complains about being unable to write his pid file In-Reply-To: <19970719132838.54020@gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 19 Jul 1997, Andreas Klemm wrote: > Hmm, I re-changed /var/tmp to permissions bin.bin and couldn't > reproduce the problem :-/ If sendmail.pid exists safefopen works. Delete the existing sendmail.pid and try again. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 From owner-freebsd-hackers Sat Jul 19 12:54:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09463 for hackers-outgoing; Sat, 19 Jul 1997 12:54:24 -0700 (PDT) Received: from folco.lms.ru (folco.lms.ru [193.125.142.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09458 for ; Sat, 19 Jul 1997 12:54:19 -0700 (PDT) Received: from minas-tirith.lms.ru (uucp@localhost) by folco.lms.ru (8.8.5/8.6.9) with UUCP id XAA24105 for freebsd.org!hackers; Sat, 19 Jul 1997 23:54:14 +0400 (MSD) Received: from minas-tirith (minas-tirith [127.0.0.1]) by minas-tirith.lms.ru (8.8.5/8.6.9) with ESMTP id NAA00599; Sat, 19 Jul 1997 13:37:36 +0400 (MSD) Message-Id: <199707190937.NAA00599@minas-tirith.lms.ru> To: freebsd.org!questions@minas-tirith.lms.ru cc: freebsd.org!hackers@minas-tirith.lms.ru Subject: sysinstall fails with panic Date: Sat, 19 Jul 1997 13:37:36 +0400 From: Alex Povolotsky Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello! I currently have 3 IDE drives, one with working system, one with distributions and one to set up. I've tried to set it up with /stand/sysinstall, and it ALWAYS produce panic diring first newfs or fsck. fsck andnewfs from command line runs just FINE. Am I the unlucky one or it's just a bug somewhere? (FreeBSD 2.2.2-RELEASE). Alex. From owner-freebsd-hackers Sat Jul 19 15:21:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14595 for hackers-outgoing; Sat, 19 Jul 1997 15:21:46 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14587 for ; Sat, 19 Jul 1997 15:21:42 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id SAA07010 for ; Sat, 19 Jul 1997 18:21:40 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA09252 for ; Sat, 19 Jul 1997 18:21:39 -0400 Date: Sat, 19 Jul 1997 18:21:39 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: lpd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I've been getting an error from lpd, and I can't figure out why. It says duplicate spool directories, and I applied the patch I read to give me the name of the file, but I can't see where there is any duplicate spool directory: Jul 19 17:41:10 journey2 lpd[1140]: startup: duplicate spool directories: /usr/spool/cdjmono-raw Trouble is, inspecting /etc/printcap _real_ carefully, /usr/spool/cdjmono-raw just isn't duplicated in the sd parameter at all! It shows up exactly once. I can't figure out what the source of this erro might be. Can anyone else toss any hints they can think of? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Jul 19 16:24:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16780 for hackers-outgoing; Sat, 19 Jul 1997 16:24:21 -0700 (PDT) Received: from minor.stranger.com (stranger.vip.best.com [204.156.129.250]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA16775 for ; Sat, 19 Jul 1997 16:24:14 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.6.12/8.6.12) with ESMTP id QAA07474 for ; Sat, 19 Jul 1997 16:47:57 -0700 Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id QAA22569 for freebsd-hackers@freebsd.org; Sat, 19 Jul 1997 16:28:38 -0700 (PDT) Received: from dog.farm.org (dog.farm.org [207.111.140.47]) by minor.stranger.com (8.6.12/8.6.12) with ESMTP id OAA07221; Sat, 19 Jul 1997 14:30:29 -0700 Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id OAA21295; Sat, 19 Jul 1997 14:06:26 -0700 (PDT) Date: Sat, 19 Jul 1997 14:06:26 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199707192106.OAA21295@dog.farm.org> To: gilham@csl.sri.com (Fred Gilham) Cc: freebsd-hackers@freebsd.org Subject: Re: NFS wierdness? Newsgroups: cs-monolit.gated.lists.freebsd.hackers Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199707191439.HAA12910@japonica.csl.sri.com> you wrote: > I have this user who runs programs that generate lots of output to > stdout. The output sometimes contains very long `lines'---long > stretches of output without a newline. The programs are also supposed > to be very CPU intensive. [...] > Unfortunately when he does this on a FreeBSD box where the directory > he's writing to is NFS mounted, he gets almost no CPU time; the > process spends most of its time in the `nfsfsy' state (according to > top). [...] First, some questions: - what is your NFS server? - is NFS mount v3 or v2? On last FreeBSD-SFUG meeting, I talked to Dyson and he confirmed that NFS appends are broken in FreeBSD; I do not know does this relate to 3.0 or 2.2 as well. I have got full-zero blocks written to mail folders opened in append mode, sometimes (folders were written by mail user agent, mutt, not by MTA), so there were no concurrency / locking problems - only one process involved. Also, NFSv3 mount on FreeBSD 2.2.2 is simply broken - it is a sure way to crash thew system by simple `rm -rf /some/dir' when /some/dir has many files (i.e., /usr/src/sys directory mounted from NFS server). This is infamous readdirplus() bug. Same on 2.2-GAMMA, or 2.2-STABLE past 2.2.2-RELEASE (which I run now). NFS v2 mounts do not show these problems (crashes / zero writes). So, please try `mount -t nfs -o nonfsv3 ...' and see whether your problem goes away. My NFS server is NetApp F330, running ONTAP 4.0-something. (this is not a Unix box). It works absolutely flawlessly with Solaris clients, which also use v3 mounts as the default. I think that changing default mount from v2 to v3 was a bad idea. > Both of these boxes are on the same network segment as the directory > they're writing to. They were invoked as follows: > tester >> dummy > and > tester.sol >> dummy > Another symptom of the problem is that it's not possible to get any > output from > tail -f dummy > on the same box that's running on tester program under FreeBSD. > However, solaris has no problems. again, this looks like file append problem. Have you tried writing numbers separated by newlines? Does this make any difference?? -- "The only problem with troubleshooting is that sometimes trouble shoots back." --joez@earthlink.net From owner-freebsd-hackers Sat Jul 19 17:39:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA19567 for hackers-outgoing; Sat, 19 Jul 1997 17:39:28 -0700 (PDT) Received: from phoenix.cardconnect.atlas.com (phoenix.cardconnect.atlas.com [206.190.150.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA19562 for ; Sat, 19 Jul 1997 17:39:24 -0700 (PDT) Received: (qmail-queue invoked by uid 4026); 20 Jul 1997 00:40:48 -0000 Message-ID: X-Mailer: XFMail 0.5-alpha [p0] on Solaris Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 19 Jul 1997 17:39:44 -0700 (PDT) Organization: CardConnect project at Atlas Telecom From: Steve Tarkalson To: freebsd-hackers@FreeBSD.org Subject: unsubscribe Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk unsubscribe From owner-freebsd-hackers Sat Jul 19 21:36:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA28450 for hackers-outgoing; Sat, 19 Jul 1997 21:36:26 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA28445 for ; Sat, 19 Jul 1997 21:36:24 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.8.5/8.7.3) with SMTP id EAA18042; Sun, 20 Jul 1997 04:36:11 GMT Date: Sun, 20 Jul 1997 04:36:10 +0000 (GMT) From: Alfred Perlstein To: Al Johnson cc: "'hackers@freebsd.org'" Subject: Re: HP LaserJet 6L In-Reply-To: <01BC939C.46CF4020.Al.Johnson@AJC.State.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 18 Jul 1997, Al Johnson wrote: > Hey folks, > > I'm trying to migrate all my ciritical functions from Win95 to FreeBSD. > Ya, I hear you all groaning now :) Since I'm no expert at this, been a > long time since I was a unix sysadmin, I need assistance with the filters > needed for this printer. I have successfully printed plain text on the > HP from the directly connected system sort of. An lptest > /dev/lpt0 > gets me a sheet of paper with a single line printed on it. Obvisouly not > what it's supposed to generate. Anyone with a filter or an adequate printcap > definition for this (or just about any PCL) printer I would really appreciate > an email copy. I'm not sure but all i think HP printers need is a linefeed added after a carriage return for each cr. > In addition, is there any special setup required to get the appropriate > conversion from a Win95 print job to the printer via Samba? If you can wait a bit, i'll have some info up on my webpage at: http://www.cs.sunyit.edu/~perlsta in 1-3 days basically all you need to do is give Samba access to the printer as almost a raw device but configure samba to tell win95 what printer driver to use. Alfred