From owner-freebsd-hackers Sun Jul 6 00:21:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12021 for hackers-outgoing; Sun, 6 Jul 1997 00:21:59 -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 AAA12016 for ; Sun, 6 Jul 1997 00:21:56 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA19953; Sun, 6 Jul 1997 09:21:52 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA15708; Sun, 6 Jul 1997 09:17:05 +0200 (MET DST) Message-ID: <19970706091705.QO21495@uriah.heep.sax.de> Date: Sun, 6 Jul 1997 09:17:05 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: davidn@blaze.net.au (David Nugent) Subject: Re: cvs commit: src/sbin/init init.c References: <19970705190030.VQ65491@uriah.heep.sax.de> <199707051800.EAA03933@labs.usn.blaze.net.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707051800.EAA03933@labs.usn.blaze.net.au>; from David Nugent on Jul 6, 1997 04:00:17 +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk (Moved away from the committers list to a more appropriate place.) As David Nugent wrote: > > Also, somebody should implement rc.shutdown... ;-) > > I'm sure I saw diffs which did precisely that. The question is, > why aren't they committed? :-) It was from one of our French friends (i think Ollivier, but i might be mistaken). I remember a minor discussion (partially by me) about a few things that should be modified before importing... but i think it mostly waits for a committer to put this under his wings. Yes, it was Ollivier, * ah * here it is. (Searching a MO takes quite some time...) Ollivier's original mail: Message-ID: Date: Sun, 12 Jan 1997 16:03:14 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: hackers@freebsd.org Subject: Re: DEVFS permissions &c. Relevant followups: Message-ID: Date: Sun, 12 Jan 1997 18:35:43 +0100 From: j@uriah.heep.sax.de (J Wunsch) Message-ID: Date: Mon, 13 Jan 1997 01:11:43 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) David, if you need these articles, i'm happy to resend them to you. *hint hint* -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jul 6 04:32:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA19537 for hackers-outgoing; Sun, 6 Jul 1997 04:32:27 -0700 (PDT) Received: from glacier.wise.edt.ericsson.se (glacier-ext.wise.edt.ericsson.se [193.180.251.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA19529 for ; Sun, 6 Jul 1997 04:32:22 -0700 (PDT) Received: from erlang (erlang.ericsson.se [147.214.36.16]) by glacier.wise.edt.ericsson.se (8.7.5/8.7.3/glacier-0.9) with SMTP id NAA25711; Sun, 6 Jul 1997 13:32:11 +0200 (MET DST) Received: from townsend.ericsson.se by erlang (SMI-8.6/LME-2.2.4) id NAA03956; Sun, 6 Jul 1997 13:32:10 +0200 Received: from townsend by townsend.ericsson.se (SMI-8.6/client-1.5) id NAA29134; Sun, 6 Jul 1997 13:32:38 +0200 Message-Id: <199707061132.NAA29134@townsend.ericsson.se> To: tom@sdf.com Cc: freebsd-hackers@FreeBSD.ORG Cc: kent@erlang.ericsson.se Subject: Re: Application os version compatibility? Reply-To: kent@erlang.ericsson.se In-Reply-To: Your message of "Sat, 5 Jul 1997 20:17:24 -0700 (PDT)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 X-URL: http://www.ericsson.se/erlang Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 06 Jul 1997 13:32:37 +0200 From: Kent Boortz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you Tom, it is more clear to me know but I'm still a bit confused. > The libc version is ONLY changed if the interface changes. If the > interface changes, some applications will not work. Hence, the version > number change. Do you talk about "system calls" like read/write? Or the interface from the library to the user, like fread/fwrite? > Huh? Statically linked applications ALWAYS work. Could it be the case that a new system call is added from FreeBSD X.X.1 to X.X.2 and for example a new libc.a implement fopen() with this new call? Then running even statically linked applications compiled in X.X.2 running on X.X.1 will break, right? Do the behaviour of system calls *ever* change change in an incompatible way? > Statically link it, and it will work on any version, or > dynamically link it to the oldest good release (probably 2.1.7), and 2.2 > users can install the 2.1 compat package (basically just a copy of > libc.2.2). This will solve the problem I describe above, good idea, thanks. (even though I hate to install an old 2.1.7 on my system just to be able to compile ;-) > It is foolish to make binary-only releases to support an unreleases > os version. There will be other libraries than 'libc' in this application. What I'm after is that if I compile and release a 2.2.2 version and an unreleased 2.2.3 shows up that "there is a good chance" it will work. No guarantee of cause, I may have to do a new release or give instruction how to use a compatibility package or something. The sad thing is that when the user starts the application and he get lots of warnings or it refuses to run he will blame me ;-) or think the product is crap. It doesn't help if the release note says 2.2.2, he runs 2.2.3 and expect it to work I want a FreeBSD version of our free non-commercial version of the product we develop (Erlang, a development system for concurrent and distributed applications) and want FreeBSD look like a "good option" to Solaris that is mostly used by our customers. Thats why I try to understand how I make binary distributions the best way and how and how well new releases are handled in this respect by the FreeBSD group. > It really is quite simple. For you maybe ;-) Thank you for your reply, /kgb From owner-freebsd-hackers Sun Jul 6 05:08:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20404 for hackers-outgoing; Sun, 6 Jul 1997 05:08:15 -0700 (PDT) Received: from ns.NL.net (ns.NL.net [193.78.240.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA20399 for ; Sun, 6 Jul 1997 05:08:11 -0700 (PDT) Received: from stuyts by ns.NL.net (5.65b/NLnet1.3) id AA26874; Sun, 6 Jul 1997 13:52:55 +0200 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.6/8.8.5) with ESMTP id NAA06853 for ; Sun, 6 Jul 1997 13:48:50 +0200 (MET DST) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id NAA02981 for hackers@FreeBSD.ORG; Sun, 6 Jul 1997 13:46:18 +0200 (MET DST) Message-Id: <199707061146.NAA02981@daneel.stuyts.nl> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sun, 6 Jul 97 13:46:15 +0200 To: hackers@FreeBSD.ORG Subject: 2.2.2. make world fails with 'boot2 is too big' Reply-To: ben@stuyts.nl X-Unexpected: The Spanish Inquisition Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I asked this on the questions mailing list but got no response. Recent cvsup's didn't fix it. Can somebody help me out with this? Original message: During a make world of 2.2.2: ===> sys/i386/boot/biosboot cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 -DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 -I/usr/src/sys/i386/boot/biosboot/../../.. -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DBOOT_HD_BIAS=1 -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o cp -p boot boot.strip strip boot.strip size boot.strip text data bss dec hex 7616 96 49052 56764 ddbc dd if=boot.strip of=boot.nohdr ibs=32 skip=1 obs=1024b 241+0 records in 0+1 records out 7712 bytes transferred in 0.003247 secs (2375186 bytes/sec) ls -l boot.nohdr -rw-r--r-- 1 root wheel 7712 Jul 3 23:14 boot.nohdr dd if=boot.nohdr of=boot1 bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.000271 secs (1889559 bytes/sec) dd if=boot.nohdr of=boot2 bs=512 skip=1 14+1 records in 14+1 records out 7200 bytes transferred in 0.001539 secs (4678387 bytes/sec) boot2 is too big *** Error code 2 Stop. I've updated my src tree with cvsup just half an hour ago. Any idea how I can fix this? Thanks, Ben From owner-freebsd-hackers Sun Jul 6 05:28:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20961 for hackers-outgoing; Sun, 6 Jul 1997 05:28:11 -0700 (PDT) Received: from haywire.dialix.com.au (news@haywire.dialix.com.au [192.203.228.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA20955 for ; Sun, 6 Jul 1997 05:28:06 -0700 (PDT) Received: (from news@localhost) by haywire.dialix.com.au id UAA21632 for freebsd-hackers@freebsd.org; Sun, 6 Jul 1997 20:27:30 +0800 (WST) X-Authentication-Warning: haywire.dialix.com.au: news set sender to usenet-request@haywire.dialix.com using -f Received: from GATEWAY by haywire.dialix.com.au with netnews for freebsd-hackers@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-hackers@freebsd.org Date: 6 Jul 1997 12:27:29 GMT From: peter@spinner.dialix.com.au (Peter Wemm) Message-ID: <868192049.512817@haywire.dialix.com.au> Organization: DIALix Internet Services References: <199707060136.DAA28936@townsend.ericsson.se> Subject: Re: Application os version compatibility? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article , tom@sdf.com (Tom Samplonius) writes: > On Sun, 6 Jul 1997, Kent Boortz wrote: [..] >> - If changing the second number staticly linked will still work. > > Huh? Statically linked applications ALWAYS work. > >> - If changing the first number we may have to recompile the >> whole thing and do a new release. > > Unless it is statically linked, in which case it will still work. Umm.. not true.. In some particular cases, static linked programs are *not* compatable across releases while the dynamic versions are. Take programs calling setproctitle() or sleep() for instance. Back when 2.1 was -stable and 2.2 was -current, there were two different versions of libutil.so.2.1. Programs linked dynamically against libutil.so.2.1 would work on either system even though the implementation of setproctitle() was different. The main thing this affected was sendmail. (The difference in this case was the address space of the process's stack as set up by the kernel at exec() time) Take programs using sleep() in 3.0. If you statically link a program under 3.0, sleep() makes a call to either the nanosleep() or signanosleep() syscall (depending on the age of libc). If you try and run this program under 2.2 or 2.1, it'll get a SIGSYS and die when it tries to sleep. /bin/sleep is the primary offender. On the other hand, a dynamically linked /bin/sleep works on both systems because both branches provide their own implementation of sleep(3). Strictly speaking, freebsd-3.0 should be compiling an interface-compatable version of libc.so.2.2 but using the 3.0 kernel primatives. The same goes for all the other libraries in the compat* dists. From owner-freebsd-hackers Sun Jul 6 05:57:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA21690 for hackers-outgoing; Sun, 6 Jul 1997 05:57:38 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21685 for ; Sun, 6 Jul 1997 05:57:33 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.6/8.8.5) id QAA00504; Sun, 6 Jul 1997 16:56:54 +0400 (MSD) Date: Sun, 6 Jul 1997 16:56:48 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: Peter Wemm cc: freebsd-hackers@FreeBSD.ORG Subject: sleep (was Re: Application os version compatibility?) In-Reply-To: <868192049.512817@haywire.dialix.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 6 Jul 1997, Peter Wemm wrote: > Take programs using sleep() in 3.0. If you statically link a program under > 3.0, sleep() makes a call to either the nanosleep() or signanosleep() syscall > (depending on the age of libc). If you try and run this program under 2.2 > or 2.1, it'll get a SIGSYS and die when it tries to sleep. /bin/sleep is > the primary offender. On the other hand, a dynamically linked /bin/sleep > works on both systems because both branches provide their own implementation > of sleep(3). Peter, why not remove special handling of ignored ALARMs in sleep() code? It is not compatible with world sleep() implementations and gives no advantages, but can cause potential incompatibility in future. I remember you agree with this statement too. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-hackers Sun Jul 6 06:41:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA22824 for hackers-outgoing; Sun, 6 Jul 1997 06:41:01 -0700 (PDT) Received: from spinner.dialix.com.au (spinner.dialix.com.au [192.203.228.67]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA22814 for ; Sun, 6 Jul 1997 06:40:35 -0700 (PDT) Received: from spinner.dialix.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.dialix.com.au with ESMTP id VAA23239; Sun, 6 Jul 1997 21:39:45 +0800 (WST) Message-Id: <199707061339.VAA23239@spinner.dialix.com.au> X-Mailer: exmh version 2.0delta 6/3/97 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sleep (was Re: Application os version compatibility?) In-reply-to: Your message of "Sun, 06 Jul 1997 16:56:48 +0400." Date: Sun, 06 Jul 1997 21:39:44 +0800 From: Peter Wemm Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= wrote: > On 6 Jul 1997, Peter Wemm wrote: > > > Take programs using sleep() in 3.0. If you statically link a program under > > 3.0, sleep() makes a call to either the nanosleep() or signanosleep() sysca ll > > (depending on the age of libc). If you try and run this program under 2.2 > > or 2.1, it'll get a SIGSYS and die when it tries to sleep. /bin/sleep is > > the primary offender. On the other hand, a dynamically linked /bin/sleep > > works on both systems because both branches provide their own implementatio n > > of sleep(3). > > Peter, why not remove special handling of ignored ALARMs in sleep() code? > It is not compatible with world sleep() implementations and gives no > advantages, but can cause potential incompatibility in future. I remember > you agree with this statement too. I'm not quite sure I follow you there.. I once talked about how using plain nanosleep() as a replacement for sleep() is incompatable with some things that depeneded on the SIGALRM eating semantics, and that one way around it was to build make a merged sigprocmask/nanosleep syscall which is basically "wait for specific signals or timeout, whichever comes first" - this is what is in the tree at present. I also talked about using another syscall to directly implement the sleep(3)/usleep(3) semantics, perhaps called nsleep(), which has the same args as nanosleep() (ie: requested and returned times). What were you thinking of? > -- > Andrey A. Chernov > > http://www.nagual.pp.ru/~ache/ Cheers, -Peter From owner-freebsd-hackers Sun Jul 6 07:38:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24406 for hackers-outgoing; Sun, 6 Jul 1997 07:38:57 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24385 for ; Sun, 6 Jul 1997 07:38:49 -0700 (PDT) Received: (from root@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id KAA00514 for hackers@freebsd.org; Sun, 6 Jul 1997 10:38:47 -0400 (EDT) Date: Sun, 6 Jul 1997 10:38:47 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707061438.KAA00514@pandora.hh.kew.com> To: hackers@freebsd.org Subject: authpriv and /var/log.messages Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Any special reason why LOG_AUTHPRIV is allowed to go into /var/log/messages and not a private file in 2.2.1? From owner-freebsd-hackers Sun Jul 6 09:25:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27138 for hackers-outgoing; Sun, 6 Jul 1997 09:25:28 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27133 for ; Sun, 6 Jul 1997 09:25:24 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id SAA04732; Sun, 6 Jul 1997 18:24:44 +0200 Message-ID: <33BFC684.167EB0E7@bonn-online.com> Date: Sun, 06 Jul 1997 18:23:32 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Bill Paul CC: hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707041537.LAA19945@skynet.ctr.columbia.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Paul wrote: > I can tell you at least one thing nfssys() does: if you look at the > keylogin(1) and chkey(1) source code from the tirpcsrc-2.3 > distribution (on playground.sun.com:/pub/rpc, among other places), > you'll see that it's used for revoking Secure RPC credentials for use > with 'Secure NFS' (nfssys(NFS_REVAUTH, &foo)). What I don't know is > how Secure RPC credentials are established for secure NFS in the > first place. I think the kernel may actually communicate with the > keyserv daemon to do it, but I'm not certain. Assuming that nfssys() is the same as nfssvc() in BSD, nfssys() is mainly used for starting the nfs server kernel thread or the nfs read ahead daemon. In BSD, nfssvc() it is also used to do kerberos authentication for nfs. This would be similar to Secure RPC authentication in Solaris. > Here's how it works (I think): > > - A process on a client decides it wants to lock something so it uses > the flock() or fcntl() system calls. > - The kernel eventually works out that the filesystem on which the > process is trying to establish the lock is an NFS filesystem. > - The kernel uses the klm_prot (llockmgr) protocol to ask the > local rpc.lockd to go out and talk to the rpc.lockd on the NFS > server and ask it for a lock. > - The rpc.lockd on the server gets the request, locks the file, then > replies back to the client. > - The rpc.lockd on the client gets the remote lockd's reply and replies > back to the kernel to tell it what happened. > That's exactly the way I think it works. Perhaps it would be easier to implement a pseudo-device like /dev/klog or /dev/tun to communicate with the local rpc.lockd rather than a full-fledged rpc protocol. Well, that might be not as elegant... Of course, the most elegant solution would be to place the complete rpc.lockd inside a kernel process. I could be of little help, then, since I've never did kernel programming before. I would still try to do what I can, though, as I think nfs locking is quite important (nearly all the competition OS's have it, by now). Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Sun Jul 6 11:11:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00352 for hackers-outgoing; Sun, 6 Jul 1997 11:11:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00344 for ; Sun, 6 Jul 1997 11:11:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA16083; Sun, 6 Jul 1997 11:07:19 -0700 From: Terry Lambert Message-Id: <199707061807.LAA16083@phaeton.artisoft.com> Subject: Re: Application os version compatibility? To: kent@erlang.ericsson.se Date: Sun, 6 Jul 1997 11:07:19 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707060136.DAA28936@townsend.ericsson.se> from "Kent Boortz" at Jul 6, 97 03:36:17 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I know some just link "libc.2.2" to "libc.3.0" to get *some* > applications working that was built for another os version than > the one running but there must be a better way to create > applications that will survive over os version? > > A reasonable rule would be that > > - If changing the third version number applications with > shared libraries will still work. > > - If changing the second number staticly linked will still work. There is no reason for this distinction. Statically linked applications never quit working unless there is a system interface change without a backward compatability provision (it is policy that can not happen). A minor number rev on a shared library means 1) Interface or parametric functionality ADDED. 2) No interface or parametric functionality DELETED. 3) No interface or parametric functionality MODIFIED. A major number rev on a shared library means 1) Interface or parametric functionality MAY have been ADDED. AND 2) Interface or parameteric functionality was DELETED. OR 3) Interface or parametric functionality was MODIFIED. So for a library revision X.Y with an application linked against x.y: 1) if X > x, application MAY NOT work To work, the application MUST NOT reference DELETED or MODIFIED interfaces 2) if X < x, application MAY NOT work To work, the application MUST NOT reference ADDED or MODIFIED interfaces 3) if X == x, and Y > y, application MUST work y > Y, application MAY NOT work To work, the application MUST NOT reference ADDED interfaces Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sun Jul 6 11:22:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00672 for hackers-outgoing; Sun, 6 Jul 1997 11:22:31 -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 LAA00665 for ; Sun, 6 Jul 1997 11:22:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA28489; Sun, 6 Jul 1997 20:22:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA24076; Sun, 6 Jul 1997 18:39:49 +0200 (MET DST) Message-ID: <19970706183948.WI18973@uriah.heep.sax.de> Date: Sun, 6 Jul 1997 18:39:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: kent@erlang.ericsson.se Subject: Re: Application os version compatibility? References: <199707061132.NAA29134@townsend.ericsson.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: <199707061132.NAA29134@townsend.ericsson.se>; from Kent Boortz on Jul 6, 1997 13:32:37 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Kent Boortz wrote: > Could it be the case that a new system call is added from FreeBSD > X.X.1 to X.X.2 and for example a new libc.a implement fopen() with > this new call? New functions (or new syscalls) will bump libc's minor number. > Then running even statically linked applications > compiled in X.X.2 running on X.X.1 will break, right? Yes, in this sense, only upwards compatibility is guaranteed. > Do the behaviour of system calls *ever* change change in an > incompatible way? Normally not. Even when moving from 4.3BSD (32 bit off_t) to 4.4BSD (64 bit off_t), the old syscalls have been retained. (The have an `o' prepended inside the kernel, and the new syscalls have been given new slots in the syscall vector.) There was only one oversight, using the syscall fcntl(2) with the file locking commands breaks it, since there's no new fcntl call. Apart from this, FreeBSD 1.x (BSD/Net2) binaries still run on FreeBSD 2 (4.4BSD). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Sun Jul 6 11:56:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01928 for hackers-outgoing; Sun, 6 Jul 1997 11:56:30 -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 LAA01920 for ; Sun, 6 Jul 1997 11:56:26 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wkwPN-0003cO-00; Sun, 6 Jul 1997 11:51:41 -0700 Date: Sun, 6 Jul 1997 11:51:40 -0700 (PDT) From: Tom Samplonius To: Kent Boortz cc: freebsd-hackers@freebsd.org Subject: Re: Application os version compatibility? In-Reply-To: <199707061132.NAA29134@townsend.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997, Kent Boortz wrote: > Thank you Tom, it is more clear to me know but I'm still a bit > confused. > > > The libc version is ONLY changed if the interface changes. If the > > interface changes, some applications will not work. Hence, the version > > number change. > > Do you talk about "system calls" like read/write? Or the interface > from the library to the user, like fread/fwrite? Only about libc, as that what the original message was about. > > Huh? Statically linked applications ALWAYS work. > > Could it be the case that a new system call is added from FreeBSD > X.X.1 to X.X.2 and for example a new libc.a implement fopen() with > this new call? Then running even statically linked applications > compiled in X.X.2 running on X.X.1 will break, right? > > Do the behaviour of system calls *ever* change change in an > incompatible way? I don't believe this has ever happened. A new syscall would be created in that case. New syscalls have been added, but the behaviour of existing syscalls are rarely changed, and then generally to fix bugs. .. > There will be other libraries than 'libc' in this application. > What I'm after is that if I compile and release a 2.2.2 version > and an unreleased 2.2.3 shows up that "there is a good chance" it will > work. No guarantee of cause, I may have to do a new release or > give instruction how to use a compatibility package or something. This should almost be guarrenteed. When there is a post 2.2.2 release, it should maintain full compatibility. Only bug fixes and minor feature improvements are going into 2.2.2. Big API changes are definitely NOT the thing that would go into the 2.2 branch. Tom From owner-freebsd-hackers Sun Jul 6 13:40:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05270 for hackers-outgoing; Sun, 6 Jul 1997 13:40:58 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA05265 for ; Sun, 6 Jul 1997 13:40:55 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id GAA03705; Mon, 7 Jul 1997 06:36:00 +1000 Date: Mon, 7 Jul 1997 06:36:00 +1000 From: Bruce Evans Message-Id: <199707062036.GAA03705@godzilla.zeta.org.au> To: benst@terminus.stuyts.nl, hackers@FreeBSD.ORG Subject: Re: 2.2.2. make world fails with 'boot2 is too big' Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >===> sys/i386/boot/biosboot >cc -O2 -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mno-486 >-DDO_BAD144 -DBOOTWAIT=5000 -DTIMEOUT= -DBOOTSEG=0x1000 -DBOOTSTACK=0xFFF0 >-I/usr/src/sys/i386/boot/biosboot/../../.. -Wreturn-type -Wcomment >-Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes >-Wmissing-prototypes -Wpointer-arith -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 >-DBOOT_HD_BIAS=1 -N -T 0 -nostdlib -static -o boot start.o table.o boot2.o >boot.o asm.o bios.o serial.o probe_keyboard.o io.o disk.o sys.o >... >7200 bytes transferred in 0.001539 secs (4678387 bytes/sec) >boot2 is too big >*** Error code 2 This is caused by using nonstandard option(s) like BOOT_HD_BIAS. Here is the list of nonstandard options that will fit: {} :-). To use nonstandard option(s), you have to remove standard option(s). The BOOT_HD_BIAS option should not be used and will go away soon, at least in -current. Put the drive numbers in /boot.config instead. Bruce From owner-freebsd-hackers Sun Jul 6 14:20:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA06619 for hackers-outgoing; Sun, 6 Jul 1997 14:20:42 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA06608 for ; Sun, 6 Jul 1997 14:20:38 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.6/8.8.5) id BAA17383; Mon, 7 Jul 1997 01:19:56 +0400 (MSD) Date: Mon, 7 Jul 1997 01:19:55 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Peter Wemm cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sleep (was Re: Application os version compatibility?) In-Reply-To: <199707061339.VAA23239@spinner.dialix.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997, Peter Wemm wrote: > I'm not quite sure I follow you there.. I once talked about how using > plain nanosleep() as a replacement for sleep() is incompatable with some > things that depeneded on the SIGALRM eating semantics, and that one way > around it was to build make a merged sigprocmask/nanosleep syscall which > is basically "wait for specific signals or timeout, whichever comes first" > - this is what is in the tree at present. I also talked about using I mean present code. If SIGALRM is already ignored, you _not_ allow it while sleep() called i.e. not install signal handler for it. Another sleep() implementations like our previous one or GNU one allows it. I think this optimization gains nothing but may cause incompatibilities. > another syscall to directly implement the sleep(3)/usleep(3) semantics, > perhaps called nsleep(), which has the same args as nanosleep() (ie: > requested and returned times). What were you thinking of? Yes, such code will be better indeed, but it is separate issue, I talk about just bugfix to current code now. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-hackers Sun Jul 6 15:41:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA09348 for hackers-outgoing; Sun, 6 Jul 1997 15:41:03 -0700 (PDT) Received: from quack.kfu.com (quack.kfu.com [204.147.226.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA09262; Sun, 6 Jul 1997 15:39:46 -0700 (PDT) From: nsayer@quack.kfu.com Received: (from nsayer@localhost) by quack.kfu.com (8.8.5/8.6.12) id PAA26655; Sun, 6 Jul 1997 15:39:44 -0700 (PDT) Message-Id: <199707062239.PAA26655@quack.kfu.com> Subject: Re: kern/3446 To: fenner@FreeBSD.ORG (Bill Fenner) Date: Sun, 6 Jul 1997 15:39:44 -0700 (PDT) Cc: joerg@FreeBSD.ORG, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199707061943.MAA03503@hub.freebsd.org> from "Bill Fenner" at Jul 6, 97 12:43:16 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bill Fenner writes: > Synopsis: IPFIREWALL reject returns port unreachable, not host > State-Changed-From-To: open-closed > State-Changed-By: fenner > State-Changed-When: Sun Jul 6 12:42:34 PDT 1997 > State-Changed-Why: > Turns out this is yet another duplicate, for kern/3452. > I missed that one because it's closed. I don't know how so many duplicates got made. I believe I sent this in a total of twice. I must protest in the strongest possible terms the closure without action of this PR. The language given in the closure of 3452 suggests that the PR should be dismissed because FreeBSD is acting correctly according to the RFCs. That is not the issue here. The issue here is that behavior that is correct according to the RFC breaks what is perhaps the most populous unix implementation that the world has ever known. I feel that that is worth at _least_ of a sysctl variable (as exists for TCP extensions, for exmaple), if not an outright substitution of behavior that actually works for behavior that is theoretically correct. Do we live and work in the real world or not?! -- Nick Sayer http://www.kfu.com/~nsayer/ | nsayer [at] quack [dot] kfu [dot] com | AMD UNSOLICITED BULK EMAIL IS UNACCEPTABLE | Inside AND WILL BE CONSIDERED AS HARASSMENT | From owner-freebsd-hackers Sun Jul 6 16:33:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11231 for hackers-outgoing; Sun, 6 Jul 1997 16:33:22 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA11217 for ; Sun, 6 Jul 1997 16:33:16 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA18474 for ; Sun, 6 Jul 1997 16:32:42 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018472; Sun Jul 6 16:32:28 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id QAA13618 for freebsd-hackers@freebsd.org; Sun, 6 Jul 1997 16:32:28 -0700 (PDT) From: Archie Cobbs Message-Id: <199707062332.QAA13618@bubba.whistle.com> Subject: VJ compression and MAX_HDR To: freebsd-hackers@freebsd.org Date: Sun, 6 Jul 1997 16:32:28 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In slcompress.h, MAX_HDR is defined so: #define MAX_HDR MLEN /* XXX 4bsd-ism: should really be 128 */ MLEN is like 108 or something. This means that when Van Jacobson compression is active, any packets sent to us with combined IP and TCP header length greater than MLEN will be dropped, always. This is an admittedly rare case, but my question is, why was this done? What code would break if MAX_HDR is changed back to 128? Searching for "MAX_HDR" in every source file in /usr/src/sys shows that it only appears in slcompress.c and slcompress.h; moreover, the code in if_ppp.c and if_sl.c seems to properly handle uncompressed headers having length greater than MLEN (from a cursory glance). Therefore, may I propose the following patch? Or else someone please elighten me. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: slcompress.h =================================================================== RCS file: /cvs/freebsd/src/sys/net/slcompress.h,v retrieving revision 1.9 diff -c -r1.9 slcompress.h *** 1.9 1996/01/30 22:58:03 --- slcompress.h 1997/07/06 23:21:52 *************** *** 42,48 **** #define _NET_SLCOMPRESS_H_ #define MAX_STATES 16 /* must be > 2 and < 256 */ ! #define MAX_HDR MLEN /* XXX 4bsd-ism: should really be 128 */ /* * Compressed packet format: --- 42,48 ---- #define _NET_SLCOMPRESS_H_ #define MAX_STATES 16 /* must be > 2 and < 256 */ ! #define MAX_HDR 128 /* max size of combined IP + TCP headers */ /* * Compressed packet format: From owner-freebsd-hackers Sun Jul 6 16:37:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11429 for hackers-outgoing; Sun, 6 Jul 1997 16:37:06 -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 QAA11419 for ; Sun, 6 Jul 1997 16:36:40 -0700 (PDT) Received: (qmail 3290 invoked by uid 1000); 6 Jul 1997 23:36: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: Sun, 06 Jul 1997 16:36:19 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.ORG Subject: PCI Bridge Question Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, 2 Simple Questions: 1. Upon booting on a SuperMicro P6DNH (dual Pentium, 8 PCi Slots, etc.), and having an Intel EtherPro 100B installed ``across the bridge'', one gets: fxp0 rev 2 int a irq 9 on pci0:19 fxp0: Ethernet address 00:a0:c9:6b:2c:e1 chip3 rev 1 on pci0:20 :0 pci0:20:1: Intel Corporation, device=0x1960, class=memory (misc) int a irq 10 [n o driver assigned] Probing for devices on PCI bus 1: fxp1 rev 2 int a irq 10 on pci1:0 pci_map_mem failed: device's memrange 0xff9ff000-0xff9fffff is incompatible with its bridge's memrange 0xfd200000-0xfd6fffff fxp1: Ethernet address 00:a0:c9:6b:8e:b6 What can I do to make this work? 2. Said machine has 256MB of RAM, another has ``only'' 128MB, etc.. Can I configure ONE kernel, with `options "MAXMEM=(256*1024)" ' and have things work nicely, still? Thanx, Simon From owner-freebsd-hackers Sun Jul 6 16:49:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11900 for hackers-outgoing; Sun, 6 Jul 1997 16:49:08 -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 QAA11893; Sun, 6 Jul 1997 16:48:51 -0700 (PDT) Received: from localhost (brian@localhost) by shell.firehouse.net (8.8.5/8.8.5) with SMTP id TAA13606; Sun, 6 Jul 1997 19:48:42 -0400 (EDT) Date: Sun, 6 Jul 1997 19:48:41 -0400 (EDT) From: Brian Mitchell To: nsayer@quack.kfu.com cc: Bill Fenner , joerg@FreeBSD.ORG, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: kern/3446 In-Reply-To: <199707062239.PAA26655@quack.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997 nsayer@quack.kfu.com wrote: > Bill Fenner writes: > > > Synopsis: IPFIREWALL reject returns port unreachable, not host > > > State-Changed-From-To: open-closed > > State-Changed-By: fenner > > State-Changed-When: Sun Jul 6 12:42:34 PDT 1997 > > State-Changed-Why: > > Turns out this is yet another duplicate, for kern/3452. > > I missed that one because it's closed. > > I don't know how so many duplicates got made. I believe I sent this > in a total of twice. > > I must protest in the strongest possible terms the closure without > action of this PR. > > The language given in the closure of 3452 suggests that the PR > should be dismissed because FreeBSD is acting correctly > according to the RFCs. That is not the issue here. The issue > here is that behavior that is correct according to the RFC > breaks what is perhaps the most populous unix implementation > that the world has ever known. I feel that that is worth at > _least_ of a sysctl variable (as exists for TCP extensions, > for exmaple), if not an outright substitution of behavior that > actually works for behavior that is theoretically correct. > > Do we live and work in the real world or not?! A sysctl is probably a good idea, although personally I dont use host or port unreachables - ICMP_UNREACH_FILTER_PROHIB seems to me to be _much_ more appropriate, but sysctl would let the firewall admin decide at boot time which he/she prefers. Brian Mitchell brian@firehouse.net "BSD code sucks. Of course, everything else sucks far more." - Theo de Raadt From owner-freebsd-hackers Sun Jul 6 16:50:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA11988 for hackers-outgoing; Sun, 6 Jul 1997 16:50:29 -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 QAA11982; Sun, 6 Jul 1997 16:50:18 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA03258; Sun, 6 Jul 1997 16:43:29 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003254; Sun Jul 6 23:43:21 1997 Date: Sun, 6 Jul 1997 16:41:51 -0700 (PDT) From: Julian Elischer To: nsayer@quack.kfu.com cc: Bill Fenner , joerg@FreeBSD.ORG, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: kern/3446 In-Reply-To: <199707062239.PAA26655@quack.kfu.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997 nsayer@quack.kfu.com wrote: > Bill Fenner writes: > > > Synopsis: IPFIREWALL reject returns port unreachable, not host > > > State-Changed-Why: > > Turns out this is yet another duplicate, for kern/3452. > > I missed that one because it's closed. > > I must protest in the strongest possible terms the closure without > action of this PR. There was action the entire IPFW code has been changed so that you may now select the way in which you reject a packet.. please check out the new version of ipfw in both 2.2 and 3.0 let me know it this does not solve the problem for you. julian From owner-freebsd-hackers Sun Jul 6 16:51:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12096 for hackers-outgoing; Sun, 6 Jul 1997 16:51:54 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12087; Sun, 6 Jul 1997 16:51:43 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA18549; Sun, 6 Jul 1997 16:51:13 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018547; Sun Jul 6 16:51:01 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id QAA13723; Sun, 6 Jul 1997 16:51:01 -0700 (PDT) From: Archie Cobbs Message-Id: <199707062351.QAA13723@bubba.whistle.com> Subject: Re: kern/3446 In-Reply-To: <199707062239.PAA26655@quack.kfu.com> from "nsayer@quack.kfu.com" at "Jul 6, 97 03:39:44 pm" To: nsayer@quack.kfu.com Date: Sun, 6 Jul 1997 16:51:01 -0700 (PDT) Cc: fenner@FreeBSD.ORG, joerg@FreeBSD.ORG, jkh@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Synopsis: IPFIREWALL reject returns port unreachable, not host > > > State-Changed-From-To: open-closed > > State-Changed-By: fenner > > State-Changed-When: Sun Jul 6 12:42:34 PDT 1997 > > State-Changed-Why: > > Turns out this is yet another duplicate, for kern/3452. > > I missed that one because it's closed. > > I don't know how so many duplicates got made. I believe I sent this > in a total of twice. > > I must protest in the strongest possible terms the closure without > action of this PR. > > The language given in the closure of 3452 suggests that the PR > should be dismissed because FreeBSD is acting correctly > according to the RFCs. That is not the issue here. The issue > here is that behavior that is correct according to the RFC > breaks what is perhaps the most populous unix implementation > that the world has ever known. I feel that that is worth at > _least_ of a sysctl variable (as exists for TCP extensions, > for exmaple), if not an outright substitution of behavior that > actually works for behavior that is theoretically correct. This bug is made obsolete by the new ipfw changes, which allow you to specify as part of the rule itself what type of ICMP error code is returned... so you can now choose either way :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Sun Jul 6 16:57:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12341 for hackers-outgoing; Sun, 6 Jul 1997 16:57:46 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12336 for ; Sun, 6 Jul 1997 16:57:43 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA18592 for ; Sun, 6 Jul 1997 16:57:13 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma018590; Sun Jul 6 16:56:47 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id QAA13745 for freebsd-hackers@FreeBSD.ORG; Sun, 6 Jul 1997 16:56:47 -0700 (PDT) From: Archie Cobbs Message-Id: <199707062356.QAA13745@bubba.whistle.com> Subject: Re: VJ compression and MAX_HDR In-Reply-To: <199707062332.QAA13618@bubba.whistle.com> from Archie Cobbs at "Jul 6, 97 04:32:28 pm" To: freebsd-hackers@FreeBSD.ORG Date: Sun, 6 Jul 1997 16:56:47 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In slcompress.h, MAX_HDR is defined so: > > #define MAX_HDR MLEN /* XXX 4bsd-ism: should really be 128 */ > > MLEN is like 108 or something. > > This means that when Van Jacobson compression is active, any packets > sent to us with combined IP and TCP header length greater than MLEN > will be dropped, always. > > This is an admittedly rare case, but my question is, why was this > done? What code would break if MAX_HDR is changed back to 128? > > Searching for "MAX_HDR" in every source file in /usr/src/sys shows > that it only appears in slcompress.c and slcompress.h; moreover, > the code in if_ppp.c and if_sl.c seems to properly handle uncompressed > headers having length greater than MLEN (from a cursory glance). > > Therefore, may I propose the following patch? Or else someone please > elighten me. After further review, it looks like the genesis of this change is the fact that sl_compress_tcp() requires the full TCP/IP headers to lie within the first mbuf, and sl_uncompress_tcp() requires the TCP/IP header (in the TYPE_UNCOMPRESSED_TCP case) to also be in a contiguous buffer... Plus the fact that m_pullup() won't work for values greater than MHLEN doesn't help. Hmm.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Sun Jul 6 17:52:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA14962 for hackers-outgoing; Sun, 6 Jul 1997 17:52:36 -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 RAA14955 for ; Sun, 6 Jul 1997 17:52:27 -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 RAA18621; Sun, 6 Jul 1997 17:53:37 -0700 (PDT) Message-Id: <199707070053.RAA18621@implode.root.com> To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VJ compression and MAX_HDR In-reply-to: Your message of "Sun, 06 Jul 1997 16:56:47 PDT." <199707062356.QAA13745@bubba.whistle.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 06 Jul 1997 17:53:37 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> This means that when Van Jacobson compression is active, any packets >> sent to us with combined IP and TCP header length greater than MLEN >> will be dropped, always. >> >> This is an admittedly rare case, but my question is, why was this >> done? What code would break if MAX_HDR is changed back to 128? ... >After further review, it looks like the genesis of this change is >the fact that sl_compress_tcp() requires the full TCP/IP headers >to lie within the first mbuf, and sl_uncompress_tcp() requires the >TCP/IP header (in the TYPE_UNCOMPRESSED_TCP case) to also be in a >contiguous buffer... > >Plus the fact that m_pullup() won't work for values greater than MHLEN >doesn't help. I think the case of IP+TCP header > MLEN is more than rare...I think it never happens. Even with all options, the IP header doesn't exceed 64 bytes. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Jul 6 17:54:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA15060 for hackers-outgoing; Sun, 6 Jul 1997 17:54:46 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA15049 for ; Sun, 6 Jul 1997 17:54:42 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA26374; Mon, 7 Jul 1997 10:24:27 +0930 (CST) From: Michael Smith Message-Id: <199707070054.KAA26374@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2.2. make world fails with 'boot2 is too big' In-Reply-To: <199707061146.NAA02981@daneel.stuyts.nl> from Ben Stuyts at "Jul 6, 97 01:46:15 pm" To: ben@stuyts.nl Date: Mon, 7 Jul 1997 10:24:26 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ben Stuyts stands accused of saying: > I asked this on the questions mailing list but got no response. Recent > cvsup's didn't fix it. Can somebody help me out with this? You may have too many bootsector features enabled in /etc/make.conf. 2.2 builds just fine here. And just in passing, -current bootstraps quite happily off 2.2.2 with nothing more than 'make includes' to get it going. I _am_ impressed 8) (2 hours for 'make world' with only NOSECURE set seems to have vindicated my choice of an IDE disk for my budget P6 box too. Now for some more memory... 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Jul 6 17:55:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA15103 for hackers-outgoing; Sun, 6 Jul 1997 17:55:02 -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 RAA15089 for ; Sun, 6 Jul 1997 17:54:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id RAA18675; Sun, 6 Jul 1997 17:56:25 -0700 (PDT) Message-Id: <199707070056.RAA18675@implode.root.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI Bridge Question In-reply-to: Your message of "Sun, 06 Jul 1997 16:36:19 PDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 06 Jul 1997 17:56:25 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >1. Upon booting on a SuperMicro P6DNH (dual Pentium, 8 PCi Slots, etc.), > and having an Intel EtherPro 100B installed ``across the bridge'', one > gets: > >fxp0 rev 2 int a irq 9 on >pci0:19 >fxp0: Ethernet address 00:a0:c9:6b:2c:e1 >chip3 rev 1 on >pci0:20 >:0 >pci0:20:1: Intel Corporation, device=0x1960, class=memory (misc) int a irq >10 [n >o driver assigned] >Probing for devices on PCI bus 1: >fxp1 rev 2 int a irq 10 on pci1:0 >pci_map_mem failed: device's memrange 0xff9ff000-0xff9fffff is incompatible >with > its bridge's memrange 0xfd200000-0xfd6fffff >fxp1: Ethernet address 00:a0:c9:6b:8e:b6 > > What can I do to make this work? Did you verify that it actually doesn't work? From the above, the device appears to have been mapped and attached okay. >2. Said machine has 256MB of RAM, another has ``only'' 128MB, etc.. > Can I configure ONE kernel, with `options "MAXMEM=(256*1024)" ' and > have things work nicely, still? Yes. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Jul 6 18:37:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA16645 for hackers-outgoing; Sun, 6 Jul 1997 18:37:18 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA16640 for ; Sun, 6 Jul 1997 18:37:16 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id SAA19005; Sun, 6 Jul 1997 18:36:45 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma019003; Sun Jul 6 18:36:30 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id SAA08578; Sun, 6 Jul 1997 18:36:30 -0700 (PDT) From: Archie Cobbs Message-Id: <199707070136.SAA08578@bubba.whistle.com> Subject: Re: VJ compression and MAX_HDR In-Reply-To: <199707070053.RAA18621@implode.root.com> from David Greenman at "Jul 6, 97 05:53:37 pm" To: dg@root.com Date: Sun, 6 Jul 1997 18:36:30 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think the case of IP+TCP header > MLEN is more than rare...I think it > never happens. Even with all options, the IP header doesn't exceed 64 bytes. (Max IP header = 64 bytes) + (max TCP header = 64 bytes) = 128 bytes > MLEN, no? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Sun Jul 6 18:47:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA17017 for hackers-outgoing; Sun, 6 Jul 1997 18:47:22 -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 SAA17011 for ; Sun, 6 Jul 1997 18:47:19 -0700 (PDT) Received: from johndoe (1Cust17.Max13.Boston.MA.MS.UU.NET [153.35.75.145]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id SAA08619; Sun, 6 Jul 1997 18:46:43 -0700 (PDT) Message-Id: <3.0.2.32.19970706214619.00777548@ranier.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Sun, 06 Jul 1997 21:46:19 -0400 To: dg@root.com, Archie Cobbs From: Matt Thomas Subject: Re: VJ compression and MAX_HDR Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707070053.RAA18621@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 05:53 PM 7/6/97 -0700, David Greenman wrote: >>After further review, it looks like the genesis of this change is >>the fact that sl_compress_tcp() requires the full TCP/IP headers >>to lie within the first mbuf, and sl_uncompress_tcp() requires the >>TCP/IP header (in the TYPE_UNCOMPRESSED_TCP case) to also be in a >>contiguous buffer... >> >>Plus the fact that m_pullup() won't work for values greater than MHLEN >>doesn't help. > > I think the case of IP+TCP header > MLEN is more than rare...I think it >never happens. Even with all options, the IP header doesn't exceed 64 bytes. But the maximum TCP header is also 64 bytes so it could be > MLEN. For now it isn't probable since few TCP options exist to push the TCP header beyond 32 byte mark. SACK will push that close to the limit however. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-hackers Sun Jul 6 19:02:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17584 for hackers-outgoing; Sun, 6 Jul 1997 19:02:42 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA17574 for ; Sun, 6 Jul 1997 19:02:39 -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 TAA19627; Sun, 6 Jul 1997 19:04:18 -0700 (PDT) Message-Id: <199707070204.TAA19627@implode.root.com> To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VJ compression and MAX_HDR In-reply-to: Your message of "Sun, 06 Jul 1997 18:36:30 PDT." <199707070136.SAA08578@bubba.whistle.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 06 Jul 1997 19:04:18 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> I think the case of IP+TCP header > MLEN is more than rare...I think it >> never happens. Even with all options, the IP header doesn't exceed 64 bytes. > >(Max IP header = 64 bytes) + (max TCP header = 64 bytes) = 128 bytes > MLEN, >no? Perhaps, but I don't think any of the current TCP options are large enough for this to be a problem (I think the largest is still under 40 bytes). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Sun Jul 6 19:20:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18442 for hackers-outgoing; Sun, 6 Jul 1997 19:20: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 TAA18432 for ; Sun, 6 Jul 1997 19:20:35 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22018; Sun, 6 Jul 1997 22:20:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun, 6 Jul 1997 22:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id VAA00369 for ; Sun, 6 Jul 1997 21:49:08 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id VAA00413 for freebsd-hackers@freefall.cdrom.com; Sun, 6 Jul 1997 21:57:33 -0400 (EDT) Date: Sun, 6 Jul 1997 21:57:33 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707070157.VAA00413@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: 127.1 and "localhost" (name resolution problem.) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just discovered this on 2.2.1+ (dated 970510) - so it may not be in 2.2.2. But, I just tried to "ping localhost" to discover it couldn't be resolved. # ping localhost ping: unknown host localhost Now - I have no name servers; /etc/host.conf is set to go to the hosts file, which contains: 127.1 localhost.water.net localhost But - If I replace that line with: 127.0.0.1 localhost.water.net localhost Everything works fine. I suggest that, until this problem is fixed, we use 127.0.0.1 in any automated generation of /etc/hosts... I'm not sure where mine came from; it could be an older installation (e.g. upgrades...) If someone happens to be poking around in /etc/hosts resolution code; I'd be interested in knowning why this didn't work... - Dave Rivers - From owner-freebsd-hackers Sun Jul 6 19:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA18445 for hackers-outgoing; Sun, 6 Jul 1997 19: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 TAA18433 for ; Sun, 6 Jul 1997 19:20:35 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22040; Sun, 6 Jul 1997 22:20:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sun, 6 Jul 1997 22:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id VAA00380 for ; Sun, 6 Jul 1997 21:54:38 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id WAA00427; Sun, 6 Jul 1997 22:03:05 -0400 (EDT) Date: Sun, 6 Jul 1997 22:03:05 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707070203.WAA00427@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.water.net!rivers Subject: Why news expiration is sooo slowww with 2.2.x. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk If you recall, I mentioned that my news expiration took a serious turn for the worse when I installed 2.2.1. That is, expirations went from a few hours to 2-3 days (sometimes even longer now...) I believe I've tripped over the issue. It would appear that readdir et. al. is taking a *long* time. If I go to a directory which has a lot of files and simply do an 'ls', it can take on the order of 20-30 minutes... I wouldn't expect the sort to be the culprit here... and, since I'm not asking for any file information, I think we can eliminate stat() as a potential culprit. I thought I would try to investigate what the problem was, but, before that; I'd send out the standard "has anyone seen/done anything in this area already?" Has anyone else noticed an issue with readdir()? - Thanks - - Dave Rivers - From owner-freebsd-hackers Sun Jul 6 19:50:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA19747 for hackers-outgoing; Sun, 6 Jul 1997 19:50:24 -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 TAA19740 for ; Sun, 6 Jul 1997 19:50:20 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id MAA20411; Mon, 7 Jul 1997 12:50:16 +1000 (EST) Date: Mon, 7 Jul 1997 12:50:16 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: Real Videa proxy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know of a Real Video proxy which can run on FreeBSD? Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Sun Jul 6 20:10:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20443 for hackers-outgoing; Sun, 6 Jul 1997 20:10:42 -0700 (PDT) Received: from students.itb.ac.id (root@students.ITB.ac.id [167.205.22.114]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA20430 for ; Sun, 6 Jul 1997 20:10:23 -0700 (PDT) Received: from localhost (firman@localhost) by students.itb.ac.id (8.8.6/8.7.3) with SMTP id KAA18687 for ; Mon, 7 Jul 1997 10:10:22 +0700 (JVT) Date: Mon, 7 Jul 1997 10:10:22 +0700 (JVT) From: Gua Firmansyah To: hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe hackers From owner-freebsd-hackers Sun Jul 6 20:29:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA20908 for hackers-outgoing; Sun, 6 Jul 1997 20:29:21 -0700 (PDT) Received: from kiyoko.communique.net (kiyoko.Communique.Net [204.27.65.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA20901 for ; Sun, 6 Jul 1997 20:29:16 -0700 (PDT) Received: (from mango@localhost) by kiyoko.communique.net (8.8.5/8.7.3) id WAA20993 for hackers@freebsd.org; Sun, 6 Jul 1997 22:28:45 -0500 (CDT) Date: Sun, 6 Jul 1997 22:28:45 -0500 (CDT) From: Raul Zighelboim Message-Id: <199707070328.WAA20993@kiyoko.communique.net> To: hackers@freebsd.org Subject: kern.maxvnodes and systat -v Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello there! When running 2.1.7-RELEASE of freebsd, setting kern.maxvnodes=32000 on the kernel (sysctl -w ...) would increase the number of vnodes from the default. I could see this increase on the 'systat -v' window under buf on the bottom right column, under cow. The I upgraded to 2.2.2-RELEASE. Now systat -v show always '16415 buf' (ie, 16000). Is this a bug, or something I am reading wrong ? Thanks. From owner-freebsd-hackers Sun Jul 6 20:37:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA21322 for hackers-outgoing; Sun, 6 Jul 1997 20:37:27 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA21313; Sun, 6 Jul 1997 20:37:16 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15640(2)>; Sun, 6 Jul 1997 20:36:16 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Sun, 6 Jul 1997 20:36:02 -0700 To: nsayer@quack.kfu.com cc: fenner@freebsd.org (Bill Fenner), joerg@freebsd.org, jkh@freebsd.org, hackers@freebsd.org Subject: Re: kern/3446 In-reply-to: Your message of "Sun, 06 Jul 97 15:39:44 PDT." <199707062239.PAA26655@quack.kfu.com> Date: Sun, 6 Jul 1997 20:35:58 PDT From: Bill Fenner Message-Id: <97Jul6.203602pdt.177512@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nsayer@quack.kfu.com wrote: >I don't know how so many duplicates got made. I believe I sent this >in a total of twice. The GNATS system was going through a strange period right around the time that this PR was submitted, and a lot of PR's got duplicated. >I must protest in the strongest possible terms the closure without >action of this PR. I'm sorry, I erred in not including the current status when I closed the PR. I believe you will find that both my suggestion (sending a RST) and your suggestion (sending a host unreachable) are possible using the new ipfw code in the kernel; the piece of code that you suggested patching now looks like icmp_error(*m, ICMP_UNREACH, rule->fw_reject_code, 0L, 0); implying that you can set fw_reject_code to ICMP_UNREACH_HOST if you want. It should probably normally be set to ICMP_UNREACH_FILTER_PROHIB (which doesn't have the ill effects that ICMP_UNREACH_PORT does on SunOS). Bill From owner-freebsd-hackers Sun Jul 6 20:58:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA21832 for hackers-outgoing; Sun, 6 Jul 1997 20:58:43 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA21827 for ; Sun, 6 Jul 1997 20:58:41 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15380(1)>; Sun, 6 Jul 1997 20:58:09 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Sun, 6 Jul 1997 20:57:58 -0700 To: dg@root.com cc: Archie Cobbs , freebsd-hackers@freebsd.org Subject: Re: VJ compression and MAX_HDR In-reply-to: Your message of "Sun, 06 Jul 97 17:53:37 PDT." <199707070053.RAA18621@implode.root.com> Date: Sun, 6 Jul 1997 20:57:57 PDT From: Bill Fenner Message-Id: <97Jul6.205758pdt.177512@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk David Greenman wrote: > I think the case of IP+TCP header > MLEN is more than rare...I think it >never happens. Even with all options, the IP header doesn't exceed 64 bytes. Both IP and TCP headers have maximum lengths of 60 bytes. A maximum size IP + max size TCP header, however, is 120 bytes, which > MLEN. sl_compress_tcp() requires the IP and TCP headers to be contiguous; the only way to require that without requiring them to be shorter than MLEN is to require that sl_compress_tcp() be passed a cluster mbuf. Failing that, the code that checks TCP options (maybe just the last BCMP in the check-if-we-should-send-this-one-compressed) needs to learn about mbuf chains. Bill From owner-freebsd-hackers Sun Jul 6 21:04:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA22008 for hackers-outgoing; Sun, 6 Jul 1997 21:04:25 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA21998 for ; Sun, 6 Jul 1997 21:04:21 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15376(2)>; Sun, 6 Jul 1997 21:03:49 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Sun, 6 Jul 1997 21:03:44 -0700 To: Archie Cobbs cc: freebsd-hackers@freebsd.org Subject: Re: VJ compression and MAX_HDR In-reply-to: Your message of "Sun, 06 Jul 97 16:56:47 PDT." <199707062356.QAA13745@bubba.whistle.com> Date: Sun, 6 Jul 1997 21:03:43 PDT From: Bill Fenner Message-Id: <97Jul6.210344pdt.177512@crevenia.parc.xerox.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: >Plus the fact that m_pullup() won't work for values greater than MHLEN >doesn't help. Arguably, it should check n->m_flags for M_PKTHDR and use MLEN if needed. However, the first mbuf in the kind of chain that you'd normally call m_pullup() on should be an M_PKTHDR anyway, so in practice this is not likely to make any difference. Bill From owner-freebsd-hackers Sun Jul 6 21:08:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA22183 for hackers-outgoing; Sun, 6 Jul 1997 21:08:45 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA22175 for ; Sun, 6 Jul 1997 21:08:40 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id WAA04970 for hackers@freebsd.org; Sun, 6 Jul 1997 22:08:39 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id WAA08634 for ; Sun, 6 Jul 1997 22:07:34 -0600 (MDT) Date: Sun, 6 Jul 1997 22:07:33 -0600 (MDT) From: Marc Slemko To: hackers@freebsd.org Subject: figuring out size of unshared pages for a process Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a large number of the same process (Apache) running. I want to figure out how much each process takes, ignoring all shared pages. I don't see any option to ps to give me what I want. Am I missing something? /proc//map seems the closest I can get without dropping into the kernel debugger and adding up the structures. One example: 0x1000 0x36000 45 0 r-x COW vnode 0x36000 0x38000 2 2 rwx COW vnode 0x38000 0x93000 45 7 rwx COW swap 0x93000 0x98000 0 0 rwx COW swap 0x98000 0xa0000 5 5 rwx default 0x8036000 0x8044000 10 0 r-x COW vnode 0x8044000 0x8046000 2 0 rwx COW vnode 0x8046000 0x804f000 5 2 rwx COW swap 0x8050000 0x8053000 3 0 r-x COW vnode 0x8053000 0x8054000 1 0 rwx COW vnode 0x8054000 0x8065000 0 0 rwx none 0x8065000 0x80c6000 68 0 r-x COW vnode 0x80c6000 0x80ca000 4 3 rwx COW vnode 0x80ca000 0x80e1000 9 8 rwx COW swap 0x80e1000 0x80ed000 12 0 rwx default 0xefbde000 0xefbfe000 5 4 rwx COW swap If I assume I can ignore all the COW stuff since it is presumably still a reference to a shared physical page, there are only three map entries I care about. Ideas on what the one with a type of none is, and should it be included? Adding them up, I get ~150k which is about what seems right in theory, although it feels like they are using _far_ more in reality, ie. the system maxes out far sooner than it should if they were using 150k + a little bit of kernel overhead per process. Is my math valid? From owner-freebsd-hackers Sun Jul 6 22:00:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24034 for hackers-outgoing; Sun, 6 Jul 1997 22:00:07 -0700 (PDT) Received: from lister.bogon.net (0@gw.bogon.net [204.137.132.49]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA24029 for ; Sun, 6 Jul 1997 22:00:04 -0700 (PDT) Received: from kryten.bogon.net (500@kryten.bogon.net [204.137.132.58]) by lister.bogon.net (8.8.5/8.8.5) with ESMTP id WAA09109 for ; Sun, 6 Jul 1997 22:00:01 -0700 (PDT) From: Wes Santee Received: (from wes@localhost) by kryten.bogon.net (8.8.6/8.8.5) id VAA05316 for hackers@freebsd.org; Sun, 6 Jul 1997 21:59:58 -0700 (PDT) Message-Id: <199707070459.VAA05316@kryten.bogon.net> Subject: Is there a thread-happy recv()? To: hackers@freebsd.org Date: Sun, 6 Jul 1997 21:59:58 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all. I noticed in a chunk of code I'm writing that a blocking call to recv() is putting the entire process to sleep such that even the other threads in the process are blocked from executing. I'm linking against libc_r (2.2-STABLE cvsup'd July 3rd) right now, is there anything else I should be doing to stop recv() (or any blocking call for that matter) from suspending the entire process? Here's a more detailed explanation. I've got two threads, T1 and T2. Here's what they do: T1 T2 -- -- 1) Issue blocking recv on a socket Acquire mutex 2) Acquire mutex after recv returns Wait for condition (which unlocks mutex) 3) Do something with data Do something with data (mutex reaquired) 4) Unlock mutex Unlock Mutex 5) Signal a conditional in T2 Loop back to 1 6) Loop back to 1 What I'm seeing is that while T2 is doing step 3, T1 is doing step 1. Then when T2 does step 4, it blocks while trying to unlock the mutex! Both T1 and T2 try to acquire the same mutex, of course. At first I thought this shouldn't be possible, but I set up another test where no blocking calls are issued in either thread ('cept for the pthread calls themselves), and everything worked just fine. Any pointers to why this wouldn't be working (including what the state of user-process threads is in 2.2-STABLE) is appreciated. Cheers, -- ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) ( mailto:wes@bogon.net ) From owner-freebsd-hackers Sun Jul 6 22:08:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24339 for hackers-outgoing; Sun, 6 Jul 1997 22:08:27 -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 WAA24333 for ; Sun, 6 Jul 1997 22:08:22 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wl5xY-0003qU-00; Sun, 6 Jul 1997 22:03:36 -0700 Date: Sun, 6 Jul 1997 22:03:35 -0700 (PDT) From: Tom Samplonius To: Thomas David Rivers cc: freebsd-hackers@freebsd.org Subject: Re: 127.1 and "localhost" (name resolution problem.) In-Reply-To: <199707070157.VAA00413@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997, Thomas David Rivers wrote: > 127.1 localhost.water.net localhost > > > But - If I replace that line with: > > 127.0.0.1 localhost.water.net localhost > > > Everything works fine. I suggest that, until this problem > is fixed, we use 127.0.0.1 in any automated generation of > /etc/hosts... I'm not sure where mine came from; it could be an > older installation (e.g. upgrades...) I suspect that you put it there. The last change to the /etc/hosts file was made in 96/03/20. > If someone happens to be poking around in /etc/hosts resolution > code; I'd be interested in knowning why this didn't work... Is it supposed to? It is not a behaviour that seems useful in anyway. > - Dave Rivers - Tom From owner-freebsd-hackers Sun Jul 6 22:14:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA24602 for hackers-outgoing; Sun, 6 Jul 1997 22:14:33 -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 WAA24594 for ; Sun, 6 Jul 1997 22:14:28 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wl63T-0003qb-00; Sun, 6 Jul 1997 22:09:43 -0700 Date: Sun, 6 Jul 1997 22:09:43 -0700 (PDT) From: Tom Samplonius To: Thomas David Rivers cc: freebsd-hackers@freebsd.org Subject: Re: Why news expiration is sooo slowww with 2.2.x. In-Reply-To: <199707070203.WAA00427@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Jul 1997, Thomas David Rivers wrote: (BTW, can you stop your mail headers from getting mangled?) > If you recall, I mentioned that my news expiration took > a serious turn for the worse when I installed 2.2.1. That is, > expirations went from a few hours to 2-3 days (sometimes even > longer now...) I use a 2.2.1 on a news server, although I should upgrade... > I believe I've tripped over the issue. It would appear that > readdir et. al. is taking a *long* time. If I go to a directory > which has a lot of files and simply do an 'ls', it can > take on the order of 20-30 minutes... I wouldn't expect the sort > to be the culprit here... and, since I'm not asking for any > file information, I think we can eliminate stat() as a potential > culprit. What options are you using on the "ls"? "-l" causes lots of getpwuid() calls. "-f" will avoid sorting. How many files were actually in that directory? If the directory is screwed, and you have a million files in it, 20-30 minutes is probably normal, and chances are the expiry will never remove them either. > I thought I would try to investigate what the problem was, but, > before that; I'd send out the standard "has anyone seen/done anything > in this area already?" Has anyone else noticed an issue with > readdir()? No. I have over 20GB of news spool space. It only takes a couple of hours to expire. Uptime is currently at 37 days, running 2.2.1 > - Thanks - > - Dave Rivers - Tom From owner-freebsd-hackers Sun Jul 6 22:36:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25619 for hackers-outgoing; Sun, 6 Jul 1997 22:36:42 -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 WAA25612 for ; Sun, 6 Jul 1997 22:36:33 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id WAA11292; Sun, 6 Jul 1997 22:37:06 -0700 (PDT) Message-ID: <19970706223705.64320@hydrogen.nike.efn.org> Date: Sun, 6 Jul 1997 22:37:05 -0700 From: John-Mark Gurney To: Wes Santee Cc: hackers@FreeBSD.ORG Subject: Re: Is there a thread-happy recv()? References: <199707070459.VAA05316@kryten.bogon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199707070459.VAA05316@kryten.bogon.net>; from Wes Santee on Sun, Jul 06, 1997 at 09:59:58PM -0700 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wes Santee scribbled this message on Jul 6: > Hi all. I noticed in a chunk of code I'm writing that a blocking call > to recv() is putting the entire process to sleep such that even the don't use recv, use read instead... the reason recv isn't wrapped is that wrapping it is pointless, and may be removed in the future (from man page) this should fix the problem... ttyl... -- 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 Jul 6 22:43:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25897 for hackers-outgoing; Sun, 6 Jul 1997 22:43:48 -0700 (PDT) Received: from ucsee.EECS.Berkeley.EDU (benco@ucsee.EECS.Berkeley.EDU [128.32.156.173]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA25892 for ; Sun, 6 Jul 1997 22:43:45 -0700 (PDT) Received: (from benco@localhost) by ucsee.EECS.Berkeley.EDU (8.8.4/8.8.4) id WAA05484; Sun, 6 Jul 1997 22:43:42 -0700 Date: Sun, 6 Jul 1997 22:43:42 -0700 From: Ben Cottrell Message-Id: <199707070543.WAA05484@ucsee.EECS.Berkeley.EDU> To: ponds!rivers@dg-rtp.dg.com, tom@sdf.com Subject: Re: 127.1 and "localhost" (name resolution problem.) Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I suspect that you put it there. The last change to the /etc/hosts file > was made in 96/03/20. Not so fast, there :-) 127.1 *was* standard in BSD /etc/hosts files for a long time. I couldn't tell you at what release FreeBSD changed over, but it's not something to be dismissed as pilot error. People can and will have incompatibilities of this sort when they upgrade. ~Ben From owner-freebsd-hackers Sun Jul 6 23:22:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27529 for hackers-outgoing; Sun, 6 Jul 1997 23:22:17 -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 XAA27524 for ; Sun, 6 Jul 1997 23:22:12 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA04962 for freebsd-hackers@freebsd.org; Mon, 7 Jul 1997 08:22:10 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA15150; Mon, 7 Jul 1997 08:02:36 +0200 (MET DST) Message-ID: <19970707080236.YR30818@uriah.heep.sax.de> Date: Mon, 7 Jul 1997 08:02:36 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: addgroup / rmgroup References: <199707051804.EAA03953@labs.usn.blaze.net.au> <199707070143.LAA26654@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707070143.LAA26654@genesis.atrad.adelaide.edu.au>; from Michael Smith on Jul 7, 1997 11:13:03 +0930 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Moved off the -committers list.) As Michael Smith wrote: > > I agree completely. Perhaps it would be better if adduser/rmuser and > > friends were modified to use pw(8)? An interactive front-end is > > definitely useful, even one in #!/bin/sh. > > Is this a "wanted" thing? I'd be happy to generate a 'pw' frontend, > as I already have code for this from a half-finished GUI 'pw' frontend > I was using to test some concepts for the remote config stuff. I was hoping on jkh to get the prototype of his new sysadm^H^H^Hinstall ready. It would probably be best to make this the official frontend then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 7 00:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29744 for hackers-outgoing; Mon, 7 Jul 1997 00:16:49 -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 AAA29739 for ; Mon, 7 Jul 1997 00:16:42 -0700 (PDT) Received: (qmail 9379 invoked by uid 1000); 7 Jul 1997 07:16:52 -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: <199707070056.RAA18675@implode.root.com> Date: Mon, 07 Jul 1997 00:16:52 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: PCI Bridge Question Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 07-Jul-97 you wrote: ... > >fxp1 rev 2 int a irq 10 on > pci1:0 > >pci_map_mem failed: device's memrange 0xff9ff000-0xff9fffff is > incompatible > >with > > its bridge's memrange 0xfd200000-0xfd6fffff > >fxp1: Ethernet address 00:a0:c9:6b:8e:b6 > > > > What can I do to make this work? > > Did you verify that it actually doesn't work? From the above, the > device appears to have been mapped and attached okay. Yup. Dead as a dead horse. The other card is very alive. This problem does not exist under 3.0-current 9as of today). BTW, under SMP, this driver panics. This happens under NFS load. What one sees is: Page fault on cpuid = 0; It blows on fxp_add_rfabuf + 0xc7. We get there via: fxp_add_rfabuf fxp_intr smp_idleloop fork_trampoline (wish had a clue what a trampoline is - other than the Kmart type :-) Simon From owner-freebsd-hackers Mon Jul 7 01:29:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA02628 for hackers-outgoing; Mon, 7 Jul 1997 01:29:42 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA02622 for ; Mon, 7 Jul 1997 01:29:38 -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 BAA23800; Mon, 7 Jul 1997 01:31:15 -0700 (PDT) Message-Id: <199707070831.BAA23800@implode.root.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI Bridge Question In-reply-to: Your message of "Mon, 07 Jul 1997 00:16:52 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Jul 1997 01:31:15 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >fxp1 rev 2 int a irq 10 on >> pci1:0 >> >pci_map_mem failed: device's memrange 0xff9ff000-0xff9fffff is >> incompatible >> >with >> > its bridge's memrange 0xfd200000-0xfd6fffff >> >fxp1: Ethernet address 00:a0:c9:6b:8e:b6 >> > >> > What can I do to make this work? >> >> Did you verify that it actually doesn't work? From the above, the >> device appears to have been mapped and attached okay. > >Yup. Dead as a dead horse. The other card is very alive. >This problem does not exist under 3.0-current 9as of today). Then what version was it failing under? >BTW, under SMP, this driver panics. This happens under NFS load. >What one sees is: > >Page fault on cpuid = 0; > >It blows on fxp_add_rfabuf + 0xc7. > >We get there via: > >fxp_add_rfabuf >fxp_intr Hmmm. That function just allocates mbufs/mbuf clusters and adds them to the end of a chain. It appears that the index into the mclrefcnt array is causing the panic - apparantly because the mbuf cluster pointer value, which was just gotten from mclfree, is bogus. This might indicate that something that wasn't an mbuf cluster had been freed onto the mclfree list. In any case, this appears to be a much more generic problem - not specific to the fxp device driver. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 7 02:33:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA05217 for hackers-outgoing; Mon, 7 Jul 1997 02:33:41 -0700 (PDT) Received: from inetfw.sonycsl.co.jp (inetfw.sonycsl.co.jp [203.137.129.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA05211 for ; Mon, 7 Jul 1997 02:33:36 -0700 (PDT) Received: from hotaka.csl.sony.co.jp (hotaka.csl.sony.co.jp [43.27.98.57]) by inetfw.sonycsl.co.jp (8.8.5/3.5W) with ESMTP id SAA16296; Mon, 7 Jul 1997 18:33:24 +0900 (JST) Received: from localhost (localhost [127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.4/3.3W3) with ESMTP id SAA14014; Mon, 7 Jul 1997 18:33:09 +0900 (JST) Message-Id: <199707070933.SAA14014@hotaka.csl.sony.co.jp> To: rsvp-test@isi.edu, freebsd-hackers@FreeBSD.ORG Subject: altq-0.3.1 released Date: Mon, 07 Jul 1997 18:33:08 +0900 From: Kenjiro Cho Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk altq-0.3.1 is now available from or The release includes: alternate queueing support for FreeBSD-2.2.1R or 2.2.2R kernel CBQ and WFQ implementation tools for CBQ RSVP stubs for CBQ What's New since version 0.2: - merged LBNL cbq v2.0 featuring Top-Level link-sharing and Weighted-Round Robin. - FreeBSD-2.2.2R based. - better bandwidth allocation. - sppp (synchronous ppp) device support. - ATM multicast workaround for RSVP developpers. - many bug fixes. The idea behind this package is to provide better queueing schemes required to realize resource-sharing and quality of service. Currently, the only queueing scheme implemented in BSD Unix is the simple tail-drop FIFO queueing. The BSD Unix systems have no general method to implement alternate queueing schemes, which is the main obstacle to implement a new queueing scheme to BSD Unix. We have designed and implemented a generic alternate queueing framework for the BSD Unix systems, and ported Sun's CBQ onto this framework. The system can be used for resource reservation with the RSVP implementation from ISI. The preliminary performance test result is encouraging; our CBQ implementation is able to handle 100Mbps without noticeable overhead. The goals of this project are three-fold: - to provide a framework to implement better queueing schemes. - to provide a link-sharing test-bed for network operators. - to provide a traffic control kernel to the RSVP community. Send bug reports, suggestions, etc. to kjc@csl.sony.co.jp. --- Kenjiro Cho Sony Computer Science Laboratory, Inc. From owner-freebsd-hackers Mon Jul 7 05:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA10984 for hackers-outgoing; Mon, 7 Jul 1997 05:51:29 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10957 for ; Mon, 7 Jul 1997 05:50:31 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.8.5/8.6.9) with SMTP id NAA13229 for ; Mon, 7 Jul 1997 13:50:20 +0100 (BST) Date: Mon, 7 Jul 1997 13:50:20 +0100 (BST) From: Developer To: hackers@freebsd.org Subject: X-Windows hacking? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a list which I can get some help on hacking X-Windows or is this the correct one? Please reply by email. Thanks. Trefor S. From owner-freebsd-hackers Mon Jul 7 06:34:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA12565 for hackers-outgoing; Mon, 7 Jul 1997 06:34:02 -0700 (PDT) Received: from intertrader.com ([195.89.144.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA12560 for ; Mon, 7 Jul 1997 06:33:59 -0700 (PDT) Received: from butterfly.intertrader.com(really [195.89.144.135]) by intertrader.com via smail with smtp id for ; Mon, 7 Jul 1997 15:41:49 +0100 (BST) (Smail-3.2 1996-Jul-4 #1 built 1997-Mar-5) Message-Id: <3.0.2.32.19970707143438.006f0430@mail> X-Sender: rachel@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Mon, 07 Jul 1997 14:34:38 +0100 To: freebsd-hackers@freebsd.org From: Rachel Willmer Subject: trouble getting machine to boot Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just installed freebsd V2.2 on a 486. Installation has gone fine apart from one thing, it won't boot automatically on power-up. If I use the Freebsd boot disk to manually boot 0:wd(0,a)/kernel, it works fine. Otherwise, it just sits there like a dead thing. Any pointers most gratefully received... Thanks Rachel From owner-freebsd-hackers Mon Jul 7 06:55:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13535 for hackers-outgoing; Mon, 7 Jul 1997 06:55:59 -0700 (PDT) Received: from inner.cortx.com (root@inner.cortx.com [207.207.221.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13530 for ; Mon, 7 Jul 1997 06:55:56 -0700 (PDT) Received: from cman (cman.cortx.com [207.207.221.12] (may be forged)) by inner.cortx.com (8.8.6/8.8.6) with SMTP id JAA00727 for ; Mon, 7 Jul 1997 09:56:42 -0400 (EDT) Message-Id: <3.0.2.32.19970707095652.00926920@inner.cortx.com> X-Sender: costa@inner.cortx.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Mon, 07 Jul 1997 09:56:52 -0400 To: freebsd-hackers@freebsd.org From: Costa Morris Subject: sd0 timed out while idle Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk i am having probs with my system. I have: FreeBSD 2.2.1-RELEASE ahc0 rev 1 int a irq 10 on pci0:10 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs (ahc0:6:0): "QUANTUM FIREBALL ST4.3S 0F0C" type 0 fixed SCSI 2 sd0(ahc0:6:0): Direct-Access 4136MB (8471232 512 byte sectors) (ahc0:1:0): "MATSHITA CD-ROM CR-504 ST23" type 5 removable SCSI 2 cd0(ahc0:1:0): CD-ROM cd present [332512 x 2048 byte records] The problem is, sometime my drive locks up for no apparent reason. the error i get which doesn't even get logged in /var/log/messages is: sd0(ahc0:6:0): timed out while idle SEQADDR = = 0x6 sd0(ahc0:6:0): abort SCB or something like that. I had to write it down because the log files had no records of this. The system was locked up where i had to use the reboot button. Once i rebooted the SCSI bios check could not find my HD. only until i did a cold boot did the controller find the HD. It booted up with some errors but it came up. This happend three times so far in about a week and a half. I checked the mail archives and found similar probs but no real solutions. please email me at: costa@cortx.com thanks in advance. From owner-freebsd-hackers Mon Jul 7 07:26:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15060 for hackers-outgoing; Mon, 7 Jul 1997 07:26:38 -0700 (PDT) Received: from mail.award.de (mail.award.de [195.30.16.205]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA15048 for ; Mon, 7 Jul 1997 07:26:31 -0700 (PDT) Message-Id: <199707071426.HAA15048@hub.freebsd.org> Received: (qmail 29019 invoked from network); 7 Jul 1997 14:25:05 -0000 Received: from unknown (HELO timo?working) (192.168.2.2) by 192.168.1.1 with SMTP; 7 Jul 1997 14:25:05 -0000 X-Mailer: Microsoft Outlook Express 4.71.0544.0 From: "Timo Geusch" To: , "Rachel Willmer" Subject: Re: trouble getting machine to boot Date: Mon, 7 Jul 1997 16:20:54 +0200 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Rachel, this may be a dumb question, but 1. Do you have other OSs installed that may require a boot manager installation ? 2. Did you set the FreeBSD partition to bootable. Timo Geusch Software engineer AWARD Software International, Inc. (Europe) ---- From: Rachel Willmer To: freebsd-hackers@FreeBSD.ORG Date: Monday, July 07, 1997 3:48 PM Subject: trouble getting machine to boot >I've just installed freebsd V2.2 on a 486. Installation has gone fine apart >from one thing, it won't boot automatically on power-up. > >If I use the Freebsd boot disk to manually boot 0:wd(0,a)/kernel, it works >fine. > >Otherwise, it just sits there like a dead thing. > >Any pointers most gratefully received... > >Thanks >Rachel > > From owner-freebsd-hackers Mon Jul 7 07:41:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16132 for hackers-outgoing; Mon, 7 Jul 1997 07:41:00 -0700 (PDT) Received: from intertrader.com ([195.89.144.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16125 for ; Mon, 7 Jul 1997 07:40:57 -0700 (PDT) Received: from butterfly.intertrader.com(really [195.89.144.135]) by intertrader.com via smail with smtp id for ; Mon, 7 Jul 1997 16:48:14 +0100 (BST) (Smail-3.2 1996-Jul-4 #1 built 1997-Mar-5) Message-Id: <3.0.2.32.19970707154103.006f9a84@mail> X-Sender: rachel@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Mon, 07 Jul 1997 15:41:03 +0100 To: "Timo Geusch" , From: Rachel Willmer Subject: Re: trouble getting machine to boot In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 16:20 07/07/97 +0200, Timo Geusch wrote: >Rachel, >this may be a dumb question, but >1. Do you have other OSs installed that may require a boot manager >installation ? No. >2. Did you set the FreeBSD partition to bootable. Yes. But I'm not sure that it has been saved correctly, and I don't yet know enough about freebsd to know how to check. I'm a converted linux hacker, and they do things a bit differently... Thanks Rachel From owner-freebsd-hackers Mon Jul 7 08:13:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA18224 for hackers-outgoing; Mon, 7 Jul 1997 08:13:08 -0700 (PDT) Received: from androcles.com (androcles.com [204.57.240.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA18202 for ; Mon, 7 Jul 1997 08:13:02 -0700 (PDT) Received: (from dhh@localhost) by androcles.com (8.8.6/8.6.12) id IAA02894; Mon, 7 Jul 1997 08:08:14 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.2.32.19970707143438.006f0430@mail> Date: Mon, 07 Jul 1997 08:07:51 -0700 (PDT) From: "Duane H. Hesser" To: Rachel Willmer Subject: RE: trouble getting machine to boot Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Perhaps the boot block is missing on the freebsd partition? -------------- Duane H. Hesser dhh@androcles.com From owner-freebsd-hackers Mon Jul 7 08:42:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA19680 for hackers-outgoing; Mon, 7 Jul 1997 08:42:32 -0700 (PDT) Received: from hotpoint.dcs.qmw.ac.uk (hotpoint.dcs.qmw.ac.uk [138.37.88.162]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19675 for ; Mon, 7 Jul 1997 08:42:29 -0700 (PDT) Received: from dominic.dcs.qmw.ac.uk [138.37.88.223]; by hotpoint.dcs.qmw.ac.uk (8.8.5/8.8.5/S-4.0) with ESMTP; for ""; id QAA23911; Mon, 7 Jul 1997 16:42:20 +0100 (BST) Received: from dom@localhost; by dominic.dcs.qmw.ac.uk (8.8.5/8.8.4/C-3.2); id QAA16859; Mon, 7 Jul 1997 16:42:19 +0100 (BST) To: hackers@freebsd.org Subject: Audio CDs in ATAPI CD-ROMs - do you have [minor] problems? Mime-Version: 1.0 (generated by tm-edit 7.96) Content-Type: text/plain; charset=US-ASCII From: Dominic Froud Date: 07 Jul 1997 16:42:15 +0100 Message-ID: Lines: 36 X-Mailer: Gnus v5.2.40/XEmacs 19.14 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FreeBSD 2.2.* hackers (but not -current people :) . Does xmcd/cda work for you? Does it successfully find catalogue data for your audio discs? . Does 'cdcontrol info' return the last two lines like: 11 36:10.55 108:09.36 162655 -162655 audio 170 0:02.00 - 0 - - instead of: 11 36:10.55 3:58.10 162655 17710 audio 170 40:06.65 - 180365 - - . Does 'cdcontrol status' say "Media catalog is inactive" where it should say: Media catalog is active, number "2438750200001" ?? If you have a spare moment, can you do me a favour a drop me a line and let me know if the above work -either way- and which distribution you're using? I'm doing some work on wcd.c, fixing things that seem broken on my machine (and haven't been fixed according to the cvs tree). Is someone already working on wcd.c in this area? (He asks, probably too late! :) Thanks, Dominic Froud -- Postmaster/Programmer, Computer Science Department, Queen Mary & Westfield College, London University From owner-freebsd-hackers Mon Jul 7 09:02:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20505 for hackers-outgoing; Mon, 7 Jul 1997 09:02:06 -0700 (PDT) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA20496 for ; Mon, 7 Jul 1997 09:01:57 -0700 (PDT) Received: from zeus.leitch.com (0@tap.zeus.leitch.com [204.187.60.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id LAA28453 for ; Mon, 7 Jul 1997 11:57:49 -0400 (EDT) Received: from bitter.zeus.leitch.com (0@bitter.zeus.leitch.com [204.187.61.66]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id LAA22310 for ; Mon, 7 Jul 1997 11:57:49 -0400 (EDT) From: Tony Holmes Received: (tholmes@localhost) by bitter.zeus.leitch.com (8.8.5/8.6.9) id LAA01700 for FreeBSD-hackers@freebsd.org; Mon, 7 Jul 1997 11:57:48 -0400 (EDT) Message-Id: <199707071557.LAA01700@bitter.zeus.leitch.com> Subject: uid > 32000 To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Mon, 7 Jul 1997 11:57:48 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I've been pouring through any document I can get my hands onto and can't find if there is any significance to a user id that is greater than 32000. There are a couple of user id's in our system defined in the 64000 range (notably the nobody user) and I was wondering if this infers additional/reduced priviledges. If anyone could answer this question or point out documentation for this, I would greatly appreciate it. Tony From owner-freebsd-hackers Mon Jul 7 09:46:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22701 for hackers-outgoing; Mon, 7 Jul 1997 09:46: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 JAA22690 for ; Mon, 7 Jul 1997 09:46: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 JAA20806; Mon, 7 Jul 1997 09:44:01 -0700 (PDT) To: Developer cc: hackers@FreeBSD.ORG Subject: Re: X-Windows hacking? In-reply-to: Your message of "Mon, 07 Jul 1997 13:50:20 BST." Date: Mon, 07 Jul 1997 09:44:00 -0700 Message-ID: <20802.868293840@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is there a list which I can get some help on hacking X-Windows or is this > the correct one? The answer to both questions is "no", I'm afraid. For X Window System information, you should probably consult some of the XFree86 lists (see http://www.xfree86.org) or look into purchasing a book on X. We have enough trouble dealing with just the OS issues here without getting into X as well, thank you. :-) Jordan From owner-freebsd-hackers Mon Jul 7 09:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22884 for hackers-outgoing; Mon, 7 Jul 1997 09:50:42 -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 JAA22872 for ; Mon, 7 Jul 1997 09:50:38 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02296; Mon, 7 Jul 1997 12:50:05 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA11957; Mon, 7 Jul 1997 07:27:23 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA01419; Mon, 7 Jul 1997 07:35:43 -0400 (EDT) Date: Mon, 7 Jul 1997 07:35:43 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707071135.HAA01419@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!sdf.com!tom Subject: Re: Why news expiration is sooo slowww with 2.2.x. Cc: ponds!FreeBSD.ORG!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Sun, 6 Jul 1997, Thomas David Rivers wrote: > > (BTW, can you stop your mail headers from getting mangled?) I've been working on it for some time. Often times, it's an incorrectly configured host between my machine and someone else. Can you send me the header you receive from this? > > > If you recall, I mentioned that my news expiration took > > a serious turn for the worse when I installed 2.2.1. That is, > > expirations went from a few hours to 2-3 days (sometimes even > > longer now...) > > I use a 2.2.1 on a news server, although I should upgrade... > > > I believe I've tripped over the issue. It would appear that > > readdir et. al. is taking a *long* time. If I go to a directory > > which has a lot of files and simply do an 'ls', it can > > take on the order of 20-30 minutes... I wouldn't expect the sort > > to be the culprit here... and, since I'm not asking for any > > file information, I think we can eliminate stat() as a potential > > culprit. > > What options are you using on the "ls"? "-l" causes lots of getpwuid() > calls. "-f" will avoid sorting. How many files were actually in that > directory? If the directory is screwed, and you have a million files in > it, 20-30 minutes is probably normal, and chances are the expiry will > never remove them either. No -l, just 'ls' (to avoid the stat()) - the directory isn't messed up - an fsck indicates everything is just fine. It's just that there are a lot of files. A /bin/ls -1 | wc -l reveals: > > > I thought I would try to investigate what the problem was, but, > > before that; I'd send out the standard "has anyone seen/done anything > > in this area already?" Has anyone else noticed an issue with > > readdir()? > > No. I have over 20GB of news spool space. It only takes a couple of > hours to expire. Uptime is currently at 37 days, running 2.2.1 I should have mentioned, this is a 386-33 (with an Intel 387) and only 8megs of RAM. Prior to 2.2.1, it took only a few hours to expire; now it takes many days.... Examining swapinfo during this process indicates swap is mostly free, so I don't believe my constrained memory is the problem (I'm not even swapping...) Certainly my CPU is slow, but it wasn't any faster prior to version 2.2.1.. :-) - Thanks - - Dave R. - From owner-freebsd-hackers Mon Jul 7 09:50:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22906 for hackers-outgoing; Mon, 7 Jul 1997 09:50:47 -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 JAA22879 for ; Mon, 7 Jul 1997 09:50:41 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02325; Mon, 7 Jul 1997 12:50:09 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA12218; Mon, 7 Jul 1997 07:33:05 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA01460; Mon, 7 Jul 1997 07:41:32 -0400 (EDT) Date: Mon, 7 Jul 1997 07:41:32 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707071141.HAA01460@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!sdf.com!tom Subject: Re: 127.1 and "localhost" (name resolution problem.) Cc: ponds!freebsd.org!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Sun, 6 Jul 1997, Thomas David Rivers wrote: > > > 127.1 localhost.water.net localhost > > > > > > But - If I replace that line with: > > > > 127.0.0.1 localhost.water.net localhost > > > > > > Everything works fine. I suggest that, until this problem > > is fixed, we use 127.0.0.1 in any automated generation of > > /etc/hosts... I'm not sure where mine came from; it could be an > > older installation (e.g. upgrades...) > > I suspect that you put it there. The last change to the /etc/hosts file > was made in 96/03/20. Yes - it seems I did put it there. The /etc/hosts that comes from an install appears to say 127.0.0.1 > > > If someone happens to be poking around in /etc/hosts resolution > > code; I'd be interested in knowning why this didn't work... > > Is it supposed to? It is not a behaviour that seems useful in anyway. I believe the IP dot-notation indicates this is supposed to work. If you don't have an entire quad; you're supposed to fill in with zeros from the middle (not from the end as you might expect.) So, 127.1 => 127.0.0.1 127.10.1 => 127.0.10.1 127 => 127.0.0.0 - Dave Rivers - From owner-freebsd-hackers Mon Jul 7 09:50:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22924 for hackers-outgoing; Mon, 7 Jul 1997 09:50:49 -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 JAA22893 for ; Mon, 7 Jul 1997 09:50:44 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02335; Mon, 7 Jul 1997 12:50:11 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA12365; Mon, 7 Jul 1997 07:38:52 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA01484; Mon, 7 Jul 1997 07:47:16 -0400 (EDT) Date: Mon, 7 Jul 1997 07:47:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707071147.HAA01484@lakes.water.net> To: ponds!MX.BA-Stuttgart.De!helbig, ponds!lakes.water.net!rivers Subject: Re: 127.1 and "localhost" (name resolution problem.) Cc: ponds!freefall.cdrom.com!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Wolfgang writes: > > But - If I replace that line with: > > > > 127.0.0.1 localhost.water.net localhost > > > > > > Everything works fine. I suggest that, until this problem > > is fixed, we use 127.0.0.1 in any automated generation of > > You already fixed the problem :-) The ip address ``127.1'' is certainly > bogus. In 2.2.1, 2.2.2 or -current the ip address is correct. (i. e. > 127.0.0.1) > > > /etc/hosts... I'm not sure where mine came from; it could be an > > older installation (e.g. upgrades...) > > > > > If someone happens to be poking around in /etc/hosts resolution > > code; I'd be interested in knowning why this didn't work... > > Should it? Yes - I believe it should; and it's my understanding that 127.1 isn't bogus. It's my understanding that, if an IP quad wasn't complete, the missing components were filled with zero - from the middle. So: 127.1 => 127.0.0.1 127.10.1 => 127.0.10.1 127 => 127.0.0.0 It's a rarely exercised "feature" these days; but 127.1 does mean 127.0.0.1 and should work... (it used to work, anyway.) - Dave Rivers - From owner-freebsd-hackers Mon Jul 7 09:50:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA22932 for hackers-outgoing; Mon, 7 Jul 1997 09:50:50 -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 JAA22899 for ; Mon, 7 Jul 1997 09:50:45 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02361; Mon, 7 Jul 1997 12:50:13 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id HAA12514; Mon, 7 Jul 1997 07:40:52 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id HAA01494; Mon, 7 Jul 1997 07:49:03 -0400 (EDT) Date: Mon, 7 Jul 1997 07:49:03 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707071149.HAA01494@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!sdf.com!tom Subject: Re: Why news expiration is sooo slowww with 2.2.x. Cc: ponds!FreeBSD.ORG!freebsd-hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > What options are you using on the "ls"? "-l" causes lots of getpwuid() > > calls. "-f" will avoid sorting. How many files were actually in that > > directory? If the directory is screwed, and you have a million files in > > it, 20-30 minutes is probably normal, and chances are the expiry will > > never remove them either. > > No -l, just 'ls' (to avoid the stat()) - the directory isn't messed > up - an fsck indicates everything is just fine. It's just that there > are a lot of files. > > A > /bin/ls -1 | wc -l > > reveals: > Oops - I left that out (it ran for about 15 minutes before giving me the answer). In my spool/control directory: [ponds.water.net]$ /bin/ls -1 | wc -l 41734 So - I have about that many files... - Dave Rivers - From owner-freebsd-hackers Mon Jul 7 09:52:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA23124 for hackers-outgoing; Mon, 7 Jul 1997 09:52: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 JAA23119 for ; Mon, 7 Jul 1997 09:52:20 -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 JAA20895; Mon, 7 Jul 1997 09:50:33 -0700 (PDT) To: "Duane H. Hesser" cc: Rachel Willmer , freebsd-hackers@FreeBSD.ORG Subject: Re: trouble getting machine to boot In-reply-to: Your message of "Mon, 07 Jul 1997 08:07:51 PDT." Date: Mon, 07 Jul 1997 09:50:33 -0700 Message-ID: <20892.868294233@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Perhaps the boot block is missing on the freebsd partition? If it were, she'd never see the boot: prompt at all. Jordan From owner-freebsd-hackers Mon Jul 7 10:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA25052 for hackers-outgoing; Mon, 7 Jul 1997 10:24:14 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA25044 for ; Mon, 7 Jul 1997 10:24:11 -0700 (PDT) Received: (qmail 8635 invoked by uid 1000); 7 Jul 1997 17:24:21 -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: <199707070831.BAA23800@implode.root.com> Date: Mon, 07 Jul 1997 10:24:21 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: PCI Bridge Question Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 07-Jul-97 you wrote: ... > >> > its bridge's memrange 0xfd200000-0xfd6fffff > >> >fxp1: Ethernet address 00:a0:c9:6b:8e:b6 > >> > > >> > What can I do to make this work? > >> > >> Did you verify that it actually doesn't work? From the above, the > >> device appears to have been mapped and attached okay. > > > >Yup. Dead as a dead horse. The other card is very alive. > >This problem does not exist under 3.0-current 9as of today). > > Then what version was it failing under? RELENG_2_2 as of Saturday. Are you maintaining this driver? Is there a maintainer? Should I dig into it? ... > >fxp_add_rfabuf > >fxp_intr > > Hmmm. That function just allocates mbufs/mbuf clusters and adds them > to the > end of a chain. It appears that the index into the mclrefcnt array is > causing > the panic - apparantly because the mbuf cluster pointer value, which was > just > gotten from mclfree, is bogus. This might indicate that something that > wasn't > an mbuf cluster had been freed onto the mclfree list. In any case, this > appears to be a much more generic problem - not specific to the fxp > device > driver. Most likely. The fxp is where I see it on this system. BTW, what are your thoughts on my project using 3.0 kernel with 2.2 release? We really like the SMP kernel, even where it stands today (already better than NiceTry :-) Simon From owner-freebsd-hackers Mon Jul 7 10:39:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26069 for hackers-outgoing; Mon, 7 Jul 1997 10:39:50 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26061 for ; Mon, 7 Jul 1997 10:39:45 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id TAA22123; Mon, 7 Jul 1997 19:39:00 +0200 Message-ID: <33C129B4.41C67EA6@bonn-online.com> Date: Mon, 07 Jul 1997 19:39:00 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Terry Lambert CC: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707022052.NAA08047@phaeton.artisoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, I have now started exploring the vfs/nfs kernel code. It appears to me that maybe some things we need for the fcntl(F_CNVT) call are already there. Namely, the nfsrv_fhtovp() function in nfs/nfs_subs.c converts a file handle (fhandle_t, not struct fid) into a vnode. So one could possibly use this function (or a modified version) to create the vnode from the handle, use falloc() to create an open file and then tie the vnode to the file struct. Question is, is the fhandle_t the same as the nfs file handle? This is only guesswork, since I am absolutely no kernel programming expert. Am I thinking in the right direction? Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Mon Jul 7 10:43:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26391 for hackers-outgoing; Mon, 7 Jul 1997 10:43: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 KAA26384 for ; Mon, 7 Jul 1997 10:43:51 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wlHke-0004Gw-00; Mon, 7 Jul 1997 10:39:04 -0700 Date: Mon, 7 Jul 1997 10:39:04 -0700 (PDT) From: Tom Samplonius To: Costa Morris cc: freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <3.0.2.32.19970707095652.00926920@inner.cortx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Costa Morris wrote: > button. Once i rebooted the SCSI bios check could not find my HD. only Throw the drive away, because it is going bad. Chances are the drive is spinning down, and you need a power cycle to get it going again. Very bad. The ahc driver in 2.2-stable is better at kick starting stalled drives. But even if it fixes it, it is just a matter of time before your drive spins down for the last time. Tom From owner-freebsd-hackers Mon Jul 7 10:49:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26801 for hackers-outgoing; Mon, 7 Jul 1997 10:49:25 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26796 for ; Mon, 7 Jul 1997 10:49:21 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id NAA11866; Mon, 7 Jul 1997 13:49:04 -0400 (EDT) Date: Mon, 7 Jul 1997 13:49:04 -0400 (EDT) From: "David E. Cross" To: Tony Holmes cc: FreeBSD hackers list Subject: Re: uid > 32000 In-Reply-To: <199707071557.LAA01700@bitter.zeus.leitch.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Tony Holmes wrote: > Hello, > > I've been pouring through any document I can get my hands onto and > can't find if there is any significance to a user id that is greater > than 32000. > > There are a couple of user id's in our system defined in the 64000 > range (notably the nobody user) and I was wondering if this infers > additional/reduced priviledges. > > If anyone could answer this question or point out documentation for > this, I would greatly appreciate it. > It generall does not mean anything with modern unices. In the 'old' days UID was a signed 16bit integer, which limited you to 32767 different userids. Userids > 32767 were really negative numbers. The definition in has the UID as an unsigned int (32 bits), giving 2.1 billion different possibilities. Other than that, it is just a number for the computer to use to track who owns what, there is nothing 'special' about it. (the only special uid/gid is '0'). -- David Cross From owner-freebsd-hackers Mon Jul 7 11:15:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28171 for hackers-outgoing; Mon, 7 Jul 1997 11:15:11 -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 LAA28162 for ; Mon, 7 Jul 1997 11:15:06 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18043; Mon, 7 Jul 1997 11:10:17 -0700 From: Terry Lambert Message-Id: <199707071810.LAA18043@phaeton.artisoft.com> Subject: Re: figuring out size of unshared pages for a process To: marcs@znep.com (Marc Slemko) Date: Mon, 7 Jul 1997 11:10:17 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Marc Slemko" at Jul 6, 97 10:07:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have a large number of the same process (Apache) running. I want to > figure out how much each process takes, ignoring all shared pages. > > I don't see any option to ps to give me what I want. Am I missing > something? man ps and look at "-o" and "-O". I believe you can get the information you want by taking out the test size from the vsize. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:26:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28784 for hackers-outgoing; Mon, 7 Jul 1997 11:26: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 LAA28775 for ; Mon, 7 Jul 1997 11:26:03 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wlITd-0003wg-00; Mon, 7 Jul 1997 12:25:33 -0600 To: Thomas David Rivers Subject: Re: 127.1 and "localhost" (name resolution problem.) Cc: hackers@freebsd.org In-reply-to: Your message of "Sun, 06 Jul 1997 21:57:33 EDT." <199707070157.VAA00413@lakes.water.net> References: <199707070157.VAA00413@lakes.water.net> Date: Mon, 07 Jul 1997 12:25:33 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707070157.VAA00413@lakes.water.net> Thomas David Rivers writes: : 127.1 localhost.water.net localhost : 127.0.0.1 localhost.water.net localhost :-). And people said that when this change went in, only crusty old farts like me would notice because they couldn't type 10.1 for 10.0.0.1 any more. It should be changed to generate 127.0.0.1 in any event... Warner From owner-freebsd-hackers Mon Jul 7 11:26:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28862 for hackers-outgoing; Mon, 7 Jul 1997 11:26:47 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA28857 for ; Mon, 7 Jul 1997 11:26:45 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id MAA18855; Mon, 7 Jul 1997 12:25:24 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id MAA12239; Mon, 7 Jul 1997 12:26:48 -0600 (MDT) Date: Mon, 7 Jul 1997 12:26:48 -0600 (MDT) From: Marc Slemko To: Terry Lambert cc: hackers@FreeBSD.ORG Subject: Re: figuring out size of unshared pages for a process In-Reply-To: <199707071810.LAA18043@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Terry Lambert wrote: > > I have a large number of the same process (Apache) running. I want to > > figure out how much each process takes, ignoring all shared pages. > > > > I don't see any option to ps to give me what I want. Am I missing > > something? > > man ps and look at "-o" and "-O". I believe you can get the information > you want by taking out the test size from the vsize. Doesn't the vsize include all the shared pages, but the text size only includes shared text pages? In this case, because there are a bunch of children generated from the parent forking (without execing), there are a lot more shared pages that are not text pages and are tagged for copy on write. From owner-freebsd-hackers Mon Jul 7 11:26:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28877 for hackers-outgoing; Mon, 7 Jul 1997 11:26: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 LAA28863 for ; Mon, 7 Jul 1997 11:26:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18058; Mon, 7 Jul 1997 11:22:13 -0700 From: Terry Lambert Message-Id: <199707071822.LAA18058@phaeton.artisoft.com> Subject: Re: Is there a thread-happy recv()? To: wes@bogon.net (Wes Santee) Date: Mon, 7 Jul 1997 11:22:13 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199707070459.VAA05316@kryten.bogon.net> from "Wes Santee" at Jul 6, 97 09:59:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi all. I noticed in a chunk of code I'm writing that a blocking call > to recv() is putting the entire process to sleep such that even the > other threads in the process are blocked from executing. I'm linking > against libc_r (2.2-STABLE cvsup'd July 3rd) right now, is there > anything else I should be doing to stop recv() (or any blocking call > for that matter) from suspending the entire process? Yes. The threads package operates through call conversion, where a call on a putatively blocking fd is made instead on a non-blocking fd, and select is used as a multiplexer. Note that mutexes are not selectable objects. I had a similar problem under DEC's MTS when extending Mentat Streams for VMS (MTS is an internal DEC product: "MultiThreading Services"). I ended up having to add event flags, and so on (my BLISS was rusty at the time; so far as I know, DEC just took the code in its entirety). Probably the correct method of dealing with the problem is to use rfork() instead; this is one planned option; effectively it means mapping user space threads to kernel "threads". Another possibility is to use an async call gate instead of non-blocking I/O. A call which could block would be tagged, and a context record generated. If the call blocked, the context record would be returned; if not, the call would complete. This is similar to the VMS soloution for mutexes, using event flag clusters, which I ended up with for event dispatch. Effectively, you are implementing asynchronus system traps. Unfortunately, neither of these soloutions is available without more than a bit of hacking (mostly on the threads implementation). > At first I thought this shouldn't be possible, but I set up another > test where no blocking calls are issued in either thread ('cept for > the pthread calls themselves), and everything worked just fine. This is an order-of-operation issue. You might also be able to overcome it by issuing an explicit yield before attempting to acquire the mutex in T1 so that T2 has the CPU in order to complete it's processing. This is a bit of a kludge, given that it requires you to know when there are potential lock-stepping issues. The code that results will be implementation dependent, meaning that the workaround might cause the code to fail on another (different) threads implementation. If portability isn't an issue, then this is probably the way to go. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:31:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29271 for hackers-outgoing; Mon, 7 Jul 1997 11:31:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA29264 for ; Mon, 7 Jul 1997 11:31:09 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18090; Mon, 7 Jul 1997 11:26:04 -0700 From: Terry Lambert Message-Id: <199707071826.LAA18090@phaeton.artisoft.com> Subject: Re: Is there a thread-happy recv()? To: gurney_j@resnet.uoregon.edu Date: Mon, 7 Jul 1997 11:26:04 -0700 (MST) Cc: wes@bogon.net, hackers@FreeBSD.ORG In-Reply-To: <19970706223705.64320@hydrogen.nike.efn.org> from "John-Mark Gurney" at Jul 6, 97 10:37:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Wes Santee scribbled this message on Jul 6: > > Hi all. I noticed in a chunk of code I'm writing that a blocking call > > to recv() is putting the entire process to sleep such that even the > > don't use recv, use read instead... the reason recv isn't wrapped is > that wrapping it is pointless, and may be removed in the future (from > man page) What about recvfrom()? The reason cited for it's redundancy is its identity with recvfrom() with a nil parameter. In any case, the socket should be non-blocking, right? I think the problem is elsewhere. I *know* that read() is useless for distinguishing OOB data. I also suspect that the recvfrom() may not be appropriate, given the connection identification hack (select comes true on a connection, and then you get the address before issuing an accept() to determine if you want to accept() or close() the socket based on who originated the connection -- see Stevens...). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:33:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29457 for hackers-outgoing; Mon, 7 Jul 1997 11:33:24 -0700 (PDT) Received: from intertrader.com ([195.89.144.130]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA29448 for ; Mon, 7 Jul 1997 11:33:20 -0700 (PDT) Received: from butterfly.intertrader.com(really [195.89.144.135]) by intertrader.com via smail with smtp id for ; Mon, 7 Jul 1997 20:41:09 +0100 (BST) (Smail-3.2 1996-Jul-4 #1 built 1997-Mar-5) Message-Id: <3.0.2.32.19970707193357.006db178@mail> X-Sender: rachel@mail X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Mon, 07 Jul 1997 19:33:57 +0100 To: freebsd-hackers@FreeBSD.ORG From: Rachel Willmer Subject: RE: trouble getting machine to boot In-Reply-To: References: <3.0.2.32.19970707143438.006f0430@mail> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I've just done a complete reinstallation using the "novice" option rather than the "expert" and it's all working fine now. It looks as though I was missing out one of the steps to make the partition active and bootable, even though I thought I had done this OK. Thanks to all who chipped in with suggestions Rachel -- Rachel Willmer Intertrader Ltd 4 John's Place Tel: +44 131 475 7108 Edinburgh EH6 7EL Fax: +44 131 475 7109 Authors of "Digital Money Online" (TM) From owner-freebsd-hackers Mon Jul 7 11:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA29723 for hackers-outgoing; Mon, 7 Jul 1997 11:36: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 LAA29715 for ; Mon, 7 Jul 1997 11:36:08 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wlIdj-0003y3-00; Mon, 7 Jul 1997 12:35:59 -0600 To: hackers@freebsd.org Subject: Re: 127.1 and "localhost" (name resolution problem.) In-reply-to: Your message of "Mon, 07 Jul 1997 07:41:32 EDT." <199707071141.HAA01460@lakes.water.net> References: <199707071141.HAA01460@lakes.water.net> Date: Mon, 07 Jul 1997 12:35:59 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707071141.HAA01460@lakes.water.net> Thomas David Rivers writes: : I believe the IP dot-notation indicates this is supposed to work. : If you don't have an entire quad; you're supposed to fill in with : zeros from the middle (not from the end as you might expect.) So, You are correct. This is traditional behavior. However, it was desided that this tradition was bad and support for it was dropped. My CVS tree isn't new enough to have this delta in it, but I think that if you look at inet_addr.c you'll see when/where this change was made. My systems predate this change, so 10.1 still works for me :-). Warner From owner-freebsd-hackers Mon Jul 7 11:40:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00153 for hackers-outgoing; Mon, 7 Jul 1997 11:40:31 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00145 for ; Mon, 7 Jul 1997 11:40:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18117; Mon, 7 Jul 1997 11:35:47 -0700 From: Terry Lambert Message-Id: <199707071835.LAA18117@phaeton.artisoft.com> Subject: Re: uid > 32000 To: tholmes@zeus.leitch.com (Tony Holmes) Date: Mon, 7 Jul 1997 11:35:47 -0700 (MST) Cc: FreeBSD-hackers@FreeBSD.ORG In-Reply-To: <199707071557.LAA01700@bitter.zeus.leitch.com> from "Tony Holmes" at Jul 7, 97 11:57:48 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been pouring through any document I can get my hands onto and > can't find if there is any significance to a user id that is greater > than 32000. NFS v2 implementations using a 16 bit signed value for uid_t. Such implementations exist because uid_t must be able to represent -1 as an error condition. > There are a couple of user id's in our system defined in the 64000 > range (notably the nobody user) and I was wondering if this infers > additional/reduced priviledges. No. There is no bit-decoding of uid_t values, other than reserved values. The user "Nobody" is generally UID -2, represented as 65534. The user "Nobody" will show as an error if the program is testing with: uid_t result; ... if( result < 0) vs. testing with: if( result == -1) So it is minorly significant, mostly for buggy programs, or programs which specifically disallow "Nobody" and other "reserved range" user ID's. Note that these programs which specifically disallow such users by value fail in the presence of 32 bit uid_t; for historical reasons of interoperability with remote systems, uid_t should be treated as a signed 16 bit value wherever possible. Expectations of special "negative", non-minus-one, "token" values for UID's means that the program is also buggy (for what that's worth)... meaning all compares for "cheating" programs should be explicitly "-1" or "(uid_t)65534" instead of "< 0". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:48:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00639 for hackers-outgoing; Mon, 7 Jul 1997 11:48:32 -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 LAA00608 for ; Mon, 7 Jul 1997 11:48:17 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18139; Mon, 7 Jul 1997 11:43:17 -0700 From: Terry Lambert Message-Id: <199707071843.LAA18139@phaeton.artisoft.com> Subject: Re: NFS locking, was: Re: NFS V3 is it stable? To: lederer@bonn-online.com (Sebastian Lederer) Date: Mon, 7 Jul 1997 11:43:17 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: <33C129B4.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 7, 97 07:39:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have now started exploring the vfs/nfs kernel code. > It appears to me that maybe some things we need for the > fcntl(F_CNVT) call are already there. Namely, > the nfsrv_fhtovp() function in nfs/nfs_subs.c > converts a file handle (fhandle_t, not struct fid) into a vnode. > So one could possibly use this function (or a modified version) > to create the vnode from the handle, use falloc() to create an open > file and then tie the vnode to the file struct. > Question is, is the fhandle_t the same as the nfs file handle? I don't know. From a preliminary discussion with Andrew, I didn't think so, so I didn't implement the F_CNVT handle-to-fd fcntl() conversion call. Before I get jumped on again: I intentionally chose the SunOS 4.x fcntl() model instead of the SVR4 nfssvc() model *specifically* because I was exposed to the USL source code for a long period of time, and I didn't want any possibility of "contamination claims" haunting the implementation. Also, SunOS 4.x is the NFS reference implementation. Note that for NFS to be a loadable module, there must be a call through the VOP for the conversion instead of a call directly to the fuction. See the lease handling callback registration for details (note: I am not happy with this implementation of the lease interface, specifically because of operations in progress prior to registration completing after registration -- they can result in a catastrophic failure because there is no "in progress" tag to prevent the failure). > This is only guesswork, since I am absolutely no kernel programming > expert. > Am I thinking in the right direction? Yes. These are the conversion functions which will need to be called, oncce the handle is converted from "wire representation with validator" to "validated internal representation". I seriously suggest contacting Andrew directly on this question; he is the person who I would have to contact for the same information. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:51:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00834 for hackers-outgoing; Mon, 7 Jul 1997 11:51:20 -0700 (PDT) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00824 for ; Mon, 7 Jul 1997 11:51:13 -0700 (PDT) Received: from zeus.leitch.com (0@tap.zeus.leitch.com [204.187.60.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id OAA29748 for ; Mon, 7 Jul 1997 14:47:32 -0400 (EDT) Received: from bitter.zeus.leitch.com (0@bitter.zeus.leitch.com [204.187.61.66]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id OAA00405 for ; Mon, 7 Jul 1997 14:47:32 -0400 (EDT) From: Tony Holmes Received: (tholmes@localhost) by bitter.zeus.leitch.com (8.8.5/8.6.9) id OAA00363 for FreeBSD-hackers@freebsd.org; Mon, 7 Jul 1997 14:47:31 -0400 (EDT) Message-Id: <199707071847.OAA00363@bitter.zeus.leitch.com> Subject: Re: uid > 32000 To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Mon, 7 Jul 1997 14:47:31 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > No. There is no bit-decoding of uid_t values, other than reserved > values. The user "Nobody" is generally UID -2, represented as 65534. > > The user "Nobody" will show as an error if the program is testing > with: > > uid_t result; > > ... > > if( result < 0) > > vs. testing with: > > if( result == -1) > > So it is minorly significant, mostly for buggy programs, or programs > which specifically disallow "Nobody" and other "reserved range" user > ID's. Thanks. This was exactly the kind of info I was looking for. I had also poured through the kernel sources and saw the declaration of uid_t, but was also aware of user land use of it as a signed 16 bit integer. It was just unclear on how this assumption was significant. Tony From owner-freebsd-hackers Mon Jul 7 11:52:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00961 for hackers-outgoing; Mon, 7 Jul 1997 11:52:41 -0700 (PDT) Received: from gateman.zeus.leitch.com (gateman.zeus.leitch.com [204.187.61.193]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00956 for ; Mon, 7 Jul 1997 11:52:38 -0700 (PDT) Received: from zeus.leitch.com (0@tap.zeus.leitch.com [204.187.60.10]) by gateman.zeus.leitch.com (8.8.5/8.7.3/1.0) with ESMTP id OAA29761; Mon, 7 Jul 1997 14:48:51 -0400 (EDT) Received: from bitter.zeus.leitch.com (0@bitter.zeus.leitch.com [204.187.61.66]) by zeus.leitch.com (8.7.5/8.7.3/1.0) with ESMTP id OAA00416; Mon, 7 Jul 1997 14:48:51 -0400 (EDT) From: Tony Holmes Received: (tholmes@localhost) by bitter.zeus.leitch.com (8.8.5/8.6.9) id OAA00371; Mon, 7 Jul 1997 14:48:51 -0400 (EDT) Message-Id: <199707071848.OAA00371@bitter.zeus.leitch.com> Subject: Re: uid > 32000 In-Reply-To: from "David E. Cross" at "Jul 7, 97 01:49:04 pm" To: dec@phoenix.its.rpi.edu (David E. Cross) Date: Mon, 7 Jul 1997 14:48:51 -0400 (EDT) Cc: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It generall does not mean anything with modern unices. In the 'old' days > UID was a signed 16bit integer, which limited you to 32767 different > userids. Userids > 32767 were really negative numbers. The definition in > has the UID as an unsigned int (32 bits), giving 2.1 billion > different possibilities. Other than that, it is just a number for the > computer to use to track who owns what, there is nothing 'special' about > it. (the only special uid/gid is '0'). Thanks for the quick response. I should have clarified that I was looking for the user-land assumptions when the number was negative (in light of some user-land treatment as an signed 16 bit integer). Tony From owner-freebsd-hackers Mon Jul 7 11:53:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01113 for hackers-outgoing; Mon, 7 Jul 1997 11:53: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 LAA01102 for ; Mon, 7 Jul 1997 11:53:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18164; Mon, 7 Jul 1997 11:47:52 -0700 From: Terry Lambert Message-Id: <199707071847.LAA18164@phaeton.artisoft.com> Subject: Re: sd0 timed out while idle To: tom@sdf.com (Tom Samplonius) Date: Mon, 7 Jul 1997 11:47:52 -0700 (MST) Cc: costa@inner.cortx.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jul 7, 97 10:39:04 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > button. Once i rebooted the SCSI bios check could not find my HD. only > > Throw the drive away, because it is going bad. Or jumper it to spin up without a reset command, so that it is on line before it is probed to see if it is online. Or set the BIOS settings for the controller to have a higher delay after the reset before the probe. Seriously, I've had a number of drives which showed up when the machine went through the cold POST, but not when the machine did a warm reset. They were all spin-up-timing issues. > Chances are the drive is spinning down, and you need a power cycle to > get it going again. Very bad. You can turn this off in mode page 3, if it is happening (if I remember my "green drives" correctly -- I don't buy them, since "green" systems take about 5 times the energy to manufacture as they are expected to use in their lifetime -- they are only useful in laptop form-factor as battery life extenders, IMO). > The ahc driver in 2.2-stable is better at kick starting stalled drives. > But even if it fixes it, it is just a matter of time before your drive > spins down for the last time. I agree that spinning down-up-down-up is a bad thing. Disable the "feature" if you can. You may also want to consider that the drive may be spinning down because it has overheated, and in reality, what you need is to fix your fan, or add a fan, or mode the machine away from the wall, etc.. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 11:56:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01277 for hackers-outgoing; Mon, 7 Jul 1997 11:56:08 -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 LAA01270 for ; Mon, 7 Jul 1997 11:56:06 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18194; Mon, 7 Jul 1997 11:51:30 -0700 From: Terry Lambert Message-Id: <199707071851.LAA18194@phaeton.artisoft.com> Subject: Re: figuring out size of unshared pages for a process To: marcs@znep.com (Marc Slemko) Date: Mon, 7 Jul 1997 11:51:30 -0700 (MST) Cc: terry@lambert.org, hackers@FreeBSD.ORG In-Reply-To: from "Marc Slemko" at Jul 7, 97 12:26:48 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I have a large number of the same process (Apache) running. I want to > > > figure out how much each process takes, ignoring all shared pages. > > > > > > I don't see any option to ps to give me what I want. Am I missing > > > something? > > > > man ps and look at "-o" and "-O". I believe you can get the information > > you want by taking out the test size from the vsize. > > Doesn't the vsize include all the shared pages, but the text size only > includes shared text pages? In this case, because there are a bunch of > children generated from the parent forking (without execing), there are a > lot more shared pages that are not text pages and are tagged for copy on > write. Well, you have to do math on the output, but that's trivial. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Jul 7 12:02:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01616 for hackers-outgoing; Mon, 7 Jul 1997 12:02:09 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA01602 for ; Mon, 7 Jul 1997 12:01:54 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA24005; Mon, 7 Jul 1997 12:01:22 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma023999; Mon Jul 7 12:01:07 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id MAA15711; Mon, 7 Jul 1997 12:01:07 -0700 (PDT) From: Archie Cobbs Message-Id: <199707071901.MAA15711@bubba.whistle.com> Subject: Re: VJ compression and MAX_HDR In-Reply-To: <199707070204.TAA19627@implode.root.com> from David Greenman at "Jul 6, 97 07:04:18 pm" To: dg@root.com Date: Mon, 7 Jul 1997 12:01:07 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >(Max IP header = 64 bytes) + (max TCP header = 64 bytes) = 128 bytes > MLEN, > >no? > > Perhaps, but I don't think any of the current TCP options are large enough > for this to be a problem (I think the largest is still under 40 bytes). This makes it no less of a bug, just a bug that's not likely to hurt you :-) Should I file a PR, so that it will be explicitly documented? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Mon Jul 7 12:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01640 for hackers-outgoing; Mon, 7 Jul 1997 12:02: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 MAA01617 for ; Mon, 7 Jul 1997 12:02:09 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wlIyR-0004K8-00; Mon, 7 Jul 1997 11:57:23 -0700 Date: Mon, 7 Jul 1997 11:57:22 -0700 (PDT) From: Tom Samplonius To: Terry Lambert cc: costa@inner.cortx.com, freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <199707071847.LAA18164@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Terry Lambert wrote: > > > button. Once i rebooted the SCSI bios check could not find my HD. only > > > > Throw the drive away, because it is going bad. > > Or jumper it to spin up without a reset command, so that it is > on line before it is probed to see if it is online. > > Or set the BIOS settings for the controller to have a higher > delay after the reset before the probe. > > Seriously, I've had a number of drives which showed up when the > machine went through the cold POST, but not when the machine did > a warm reset. They were all spin-up-timing issues. Not necessarily. If the drive goes through a warm reset without problems over, and over, over again without problems, but as soon as you get a "timeout error", and it hangs, and then it doesn't probe properly then you have a big problem. Also, the ncr controllers are little finicky. They have a delay option that I had to increase otherwise it wouldn't wait long enough for the drives to spin up. But I only had this problem on cold boots (never on warm), and only with the ncr controllers. The Adaptec controllers seem to wait much longer by default. Quatum drives are known to go on a holiday after some continuous use. Grand Prix drives are particularly bad. In fact, I think the Atlas is the only respectible Quantum drive. BTW, I only get Seagate Barracuda 4LP or 4XL drives in either 2gb or 4gb now. Very nice drives. Tom From owner-freebsd-hackers Mon Jul 7 12:47:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04031 for hackers-outgoing; Mon, 7 Jul 1997 12:47:18 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04022 for ; Mon, 7 Jul 1997 12:47:15 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id MAA24633; Mon, 7 Jul 1997 12:50:45 -0700 (PDT) Date: Mon, 7 Jul 1997 12:50:45 -0700 (PDT) From: Howard Lew To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Real Videa proxy In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Daniel O'Callaghan wrote: > > Does anyone know of a Real Video proxy which can run on FreeBSD? There is a raproxy program available from Real Audio. It does both Real Audio & Real Video, but as far as I know there is no Real Video player for FreeBSD yet. I have tested the proxy program on a FreeBSD server and a Win95 machine using Real Player 4.0 and it works great. > > Danny > > /* Daniel O'Callaghan */ > /* HiLink Internet danny@hilink.com.au */ > /* FreeBSD - works hard, plays hard... danny@freebsd.org */ > > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hackers Mon Jul 7 12:53:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04347 for hackers-outgoing; Mon, 7 Jul 1997 12:53:26 -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 MAA04339 for ; Mon, 7 Jul 1997 12:53:14 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA25213 (5.67b/IDA-1.5 for ); Mon, 7 Jul 1997 21:49:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id VAA13349; Mon, 7 Jul 1997 21:49:09 +0200 (CEST) X-Face: " Date: Mon, 7 Jul 1997 21:49:08 +0200 From: Stefan Esser To: Tom Samplonius Cc: Terry Lambert , costa@inner.cortx.com, freebsd-hackers@FreeBSD.ORG Subject: Re: sd0 timed out while idle References: <199707071847.LAA18164@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Tom Samplonius on Mon, Jul 07, 1997 at 11:57:22AM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 7, Tom Samplonius wrote: > Also, the ncr controllers are little finicky. They have a delay option > that I had to increase otherwise it wouldn't wait long enough for the > drives to spin up. But I only had this problem on cold boots (never on > warm), and only with the ncr controllers. The Adaptec controllers seem to > wait much longer by default. The "NCR controllers" ??? They don't exist ... :) In fact, there are several independently developed BIOS versions offered with the various brands of NCR chip, and even my (2.5 year old) ASUS SP3G lets you specify an additional power on delay ... The Tekram cards seem to wait significantly longer by default (at least my DC390F does), compared to the SDMS BIOS cards from Symbios and others. > Quatum drives are known to go on a holiday after some continuous use. > Grand Prix drives are particularly bad. In fact, I think the Atlas is the > only respectible Quantum drive. How about the quality of the Atlas II and the Viking ? I don't really understand, why they offer two 7200RPM drives, again. Reminds me of the Atlas/Grand Prix ... Regards, STefan From owner-freebsd-hackers Mon Jul 7 12:59:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04588 for hackers-outgoing; Mon, 7 Jul 1997 12:59:04 -0700 (PDT) Received: from ice.cold.org (brandon@cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04580 for ; Mon, 7 Jul 1997 12:59:02 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id NAA00618 for ; Mon, 7 Jul 1997 13:58:59 -0600 (MDT) Date: Mon, 7 Jul 1997 13:58:59 -0600 (MDT) From: Brandon Gillespie To: hackers@freebsd.org Subject: Alternative to /etc/*.conf files? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just a note.. the _one_ thing from Unixware that I actually liked is rather than having a spattering of *.conf files dropped all througout /etc, there is an /etc/default directory where everything is tossed--dunno if this is exclusive to unixware or not, but we could follow in the same theme and have /etc/conf/* rather than /etc/*.conf (imho). Just a random thought, most likely this would be too much of a change, and people would not know what to do. -Brandon Gillespie From owner-freebsd-hackers Mon Jul 7 13:34:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06493 for hackers-outgoing; Mon, 7 Jul 1997 13:34:13 -0700 (PDT) Received: from pluto.plutotech.com (root@[206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06467; Mon, 7 Jul 1997 13:34:01 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id OAA05078; Mon, 7 Jul 1997 14:33:42 -0600 (MDT) Message-Id: <199707072033.OAA05078@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Stefan Esser cc: Tom Samplonius , Terry Lambert , costa@inner.cortx.com, freebsd-hackers@FreeBSD.ORG Subject: Re: sd0 timed out while idle In-reply-to: Your message of "Mon, 07 Jul 1997 21:49:08 +0200." <19970707214908.44376@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Jul 1997 14:33:41 -0600 From: "Justin T. Gibbs" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >How about the quality of the Atlas II and the Viking ? >I don't really understand, why they offer two 7200RPM >drives, again. Reminds me of the Atlas/Grand Prix ... > >Regards, STefan The Viking supposedly doen't have the "QUEUE FULL" dain bramage that the Atlas II has, but we haven't gotten any in here yet to test. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hackers Mon Jul 7 14:02:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08063 for hackers-outgoing; Mon, 7 Jul 1997 14:02:40 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08053 for ; Mon, 7 Jul 1997 14:02:26 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA15393 for ; Mon, 7 Jul 1997 23:01:19 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id XAA10920 for hackers@FreeBSD.ORG; Mon, 7 Jul 1997 23:00:59 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id WAA10080; Mon, 7 Jul 1997 22:51:49 +0200 (CEST) Message-ID: <19970707225149.19828@keltia.freenix.fr> Date: Mon, 7 Jul 1997 22:51:49 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: /etc/rc.shutdown (Was: Re: DEVFS permissions &c.) References: <16902.853042470@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from J Wunsch on Sun, Jan 12, 1997 at 06:35:42PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ digging this old mail from my archive, I love Glimpse ] According to J Wunsch (a long time ago): > I think stall() is the wrong thing to do here. If the shutdown script > fails, it's best to log what can be logged, and proceed to really shut > down the system to the desired state. stall() is the same function as warning() except that it waits for STALL_TIMEOUT (browsing through init.c again, there are a fes places where warning() is used and then a sleep() is done just after...). Both are syslogging. So even with stall, it will proceed if runshutdown() returns. In this case, stall is better IMO because if you're at the console you'll have time to see the message... If not, you won't be too disturbed (except by waiting a bit more of course). > Here's an alarm() missing, to prevent infinite hangs of the shutdown > script. Such an infinite hang should be answered with sending > rc.shutdown a terminate signal, and by syslogging it. Will do. What do you people think of this (against current of course) ? My ALRM handling may be a bit off track so I welcome comments (and diffs :-)). Index: init.8 =================================================================== RCS file: /spare/FreeBSD-current/src/sbin/init/init.8,v retrieving revision 1.9 diff -u -2 -r1.9 init.8 --- init.8 1997/04/01 20:41:04 1.9 +++ init.8 1997/07/07 20:19:36 @@ -242,4 +242,13 @@ or from X when the machine appears to be hung. .Pp +When shuting down the machine, +.Nm init +will try to run the +.Pa /etc/rc.shutdown +script. This script can be used to cleanly terminate specific programs such +as +.Nm innd +(the InterNetNews server). +.Pp The role of .Nm init @@ -281,4 +290,6 @@ .It Pa /etc/rc System startup commands. +.It Pa /etc/rc.shutdown +System shutdown commands. .El .Sh SEE ALSO Index: init.c =================================================================== RCS file: /spare/FreeBSD-current/src/sbin/init/init.c,v retrieving revision 1.17 diff -u -2 -r1.17 init.c --- init.c 1997/06/13 06:24:42 1.17 +++ init.c 1997/07/07 20:49:39 @@ -98,4 +98,5 @@ #define STALL_TIMEOUT 30 /* wait N secs after warning */ #define DEATH_WATCH 10 /* wait N secs for procs to die */ +#define DEATH_SCRIPT 120 /* wait for 2mn for /etc/rc.shutdown */ #define RESOURCE_RC "daemon" #define RESOURCE_WINDOW "default" @@ -110,4 +111,5 @@ void disaster __P((int)); void badsys __P((int)); +int runshutdown __P((void)); /* @@ -1385,4 +1387,5 @@ { register session_t *sp; + register int rcdown; register int i; pid_t pid; @@ -1392,4 +1395,10 @@ sp->se_flags |= SE_SHUTDOWN; + /* Try to run the rc.shutdown script within a period of time */ + rcdown = runshutdown(); + if (rcdown) + stall("Could not run %s, proceeding with shutdown anyway.", + _PATH_RUNDOWN); + /* NB: should send a message to the session logger to avoid blocking. */ logwtmp("~", "shutdown", ""); @@ -1413,4 +1422,99 @@ return (state_func_t) single_user; +} + +/* + * Run the system shutdown script. + * + * Exit codes: XXX I should document more + * 0 good. + * 1 fatal error + * 2 some error + */ +int +runshutdown() +{ + pid_t pid, wpid; + int status; + char *argv[3]; + struct sigaction sa; + + if ((pid = fork()) == 0) { + sigemptyset(&sa.sa_mask); + sa.sa_flags = 0; + sa.sa_handler = SIG_IGN; + (void) sigaction(SIGTSTP, &sa, (struct sigaction *)0); + (void) sigaction(SIGHUP, &sa, (struct sigaction *)0); + + setctty(_PATH_CONSOLE); + + argv[0] = "sh"; + argv[1] = _PATH_RUNDOWN; + argv[2] = 0; + + sigprocmask(SIG_SETMASK, &sa.sa_mask, (sigset_t *) 0); + + execv(_PATH_BSHELL, argv); + stall("can't exec %s for %s: %m", _PATH_BSHELL, _PATH_RUNDOWN); + _exit(1); /* force single user mode */ + } + + if (pid == -1) { + emergency("can't fork for %s on %s: %m", + _PATH_BSHELL, _PATH_RUNDOWN); + while (waitpid(-1, (int *) 0, WNOHANG) > 0) + continue; + sleep(STALL_TIMEOUT); + return 1; + } + + /* + * Copied from single_user(). This is a bit paranoid. + * Use the same ALRM handler. + */ + alarm(DEATH_SCRIPT); + do { + if ((wpid = waitpid(-1, &status, WUNTRACED)) != -1) + collect_child(wpid); + if (wpid == -1 || clang == 1) { + if (errno == EINTR) + continue; + if (clang) { + /* we were waiting for the sub-shell */ + kill(wpid, SIGTERM); + warning("timeout expired for %s on %s: %m; goinh to single used mode", + _PATH_BSHELL, _PATH_RUNDOWN); + } + else + warning("wait for %s on %s failed: %m; going to single user mode", + _PATH_BSHELL, _PATH_RUNDOWN); + return 2; + } + if (wpid == pid && WIFSTOPPED(status)) { + warning("init: %s on %s stopped, restarting\n", + _PATH_BSHELL, _PATH_RUNDOWN); + kill(pid, SIGCONT); + wpid = -1; + } + } while (wpid != pid && !clang); + + if (WIFSIGNALED(status) && WTERMSIG(status) == SIGTERM && + requested_transition == catatonia) { + /* /etc/rc executed /sbin/reboot; wait for the end quietly */ + sigset_t s; + + sigfillset(&s); + for (;;) + sigsuspend(&s); + } + + if (!WIFEXITED(status)) { + warning("%s on %s terminated abnormally, going to single user mode", + _PATH_BSHELL, _PATH_RUNDOWN); + return 1; + } + + if (WEXITSTATUS(status)) + return 2; } char * Index: pathnames.h =================================================================== RCS file: /spare/FreeBSD-current/src/sbin/init/pathnames.h,v retrieving revision 1.1.1.1 diff -u -2 -r1.1.1.1 pathnames.h --- pathnames.h 1994/05/26 06:34:19 1.1.1.1 +++ pathnames.h 1997/07/07 20:19:36 @@ -41,2 +41,3 @@ #define _PATH_SLOGGER "/sbin/session_logger" #define _PATH_RUNCOM "/etc/rc" +#define _PATH_RUNDOWN "/etc/rc.shutdown" -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Mon Jul 7 14:03:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08251 for hackers-outgoing; Mon, 7 Jul 1997 14:03:55 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08245 for ; Mon, 7 Jul 1997 14:03:52 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id RAA26061; Mon, 7 Jul 1997 17:03:41 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id RAA06783; Mon, 7 Jul 1997 17:03:31 -0400 Date: Mon, 7 Jul 1997 17:03:38 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Jordan K. Hubbard" cc: Developer , hackers@FreeBSD.ORG Subject: Re: X-Windows hacking? In-Reply-To: <20802.868293840@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Jordan K. Hubbard wrote: > > Is there a list which I can get some help on hacking X-Windows or is this > > the correct one? > > The answer to both questions is "no", I'm afraid. > > For X Window System information, you should probably consult some of > the XFree86 lists (see http://www.xfree86.org) or look into purchasing > a book on X. > > We have enough trouble dealing with just the OS issues here without > getting into X as well, thank you. :-) Well, there are a couple of good usenet lists for that, search for "X11". > > Jordan > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jul 7 14:32:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09896 for hackers-outgoing; Mon, 7 Jul 1997 14:32:21 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09891 for ; Mon, 7 Jul 1997 14:32:19 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id OAA09509 for ; Mon, 7 Jul 1997 14:32:11 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id XAA15448 for ; Mon, 7 Jul 1997 23:30:49 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id XAA11283 for freebsd-hackers@FreeBSD.ORG; Mon, 7 Jul 1997 23:30:43 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id XAA10245; Mon, 7 Jul 1997 23:26:49 +0200 (CEST) Message-ID: <19970707232649.37692@keltia.freenix.fr> Date: Mon, 7 Jul 1997 23:26:49 +0200 From: Ollivier Robert To: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? References: <199707021632.JAA06741@phaeton.artisoft.com> <33BABD1C.41C67EA6@bonn-online.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <33BABD1C.41C67EA6@bonn-online.com>; from Sebastian Lederer on Wed, Jul 02, 1997 at 10:42:04PM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Sebastian Lederer: > Solaris would surely be preferable, but the current price list shows > Solaris 2.5.1 for x86 as about 5000 DM (about 2700 US-$). > As soon as I see any special offer there I will probably get it. If you're a student or you have access to one (or an academic entity), you can now even get the _source code_ for Slowlaris. See Sun's Web site for details. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Mon Jul 7 14:32:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09954 for hackers-outgoing; Mon, 7 Jul 1997 14:32:47 -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 OAA09829 for ; Mon, 7 Jul 1997 14:31:44 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA01265 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Mon, 7 Jul 1997 23:32:03 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id VAA01118 for FreeBSD-hackers@freebsd.org; Mon, 7 Jul 1997 21:51:48 +0200 (MET DST) From: Wilko Bulte Message-Id: <199707071951.VAA01118@yedi.iaf.nl> Subject: experiences with seagate st32550N ? To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Mon, 7 Jul 1997 21:51:48 +0200 (MET DST) 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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, What is the general experience with a Seagate ST32550N disk? Good/bad? Might be able to pick one up for a good price. TIA Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-hackers Mon Jul 7 14:44:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10681 for hackers-outgoing; Mon, 7 Jul 1997 14:44:50 -0700 (PDT) Received: from lsd.relcom.eu.net (lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10660 for ; Mon, 7 Jul 1997 14:44:44 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.6/8.8.5) id BAA02978; Tue, 8 Jul 1997 01:44:33 +0400 (MSD) Date: Tue, 8 Jul 1997 01:44:32 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: Ollivier Robert cc: hackers@FreeBSD.ORG Subject: Re: /etc/rc.shutdown (Was: Re: DEVFS permissions &c.) In-Reply-To: <19970707225149.19828@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Ollivier Robert wrote: > + /* Try to run the rc.shutdown script within a period of time */ > + rcdown = runshutdown(); > + if (rcdown) > + stall("Could not run %s, proceeding with shutdown anyway.", > + _PATH_RUNDOWN); > + > /* NB: should send a message to the session logger to avoid blocking. */ > logwtmp("~", "shutdown", ""); rhushutdown() is part of shutdown, so logwtmp() must be BEFORE runshutdown() call. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-hackers Mon Jul 7 15:16:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12524 for hackers-outgoing; Mon, 7 Jul 1997 15:16:30 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12515 for ; Mon, 7 Jul 1997 15:16:24 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id SAA09402; Mon, 7 Jul 1997 18:16:16 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id SAA09008; Mon, 7 Jul 1997 18:16:07 -0400 Date: Mon, 7 Jul 1997 18:16:14 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Ollivier Robert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NFS locking, was: Re: NFS V3 is it stable? In-Reply-To: <19970707232649.37692@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Ollivier Robert wrote: > According to Sebastian Lederer: > > Solaris would surely be preferable, but the current price list shows > > Solaris 2.5.1 for x86 as about 5000 DM (about 2700 US-$). > > As soon as I see any special offer there I will probably get it. > > If you're a student or you have access to one (or an academic entity), you > can now even get the _source code_ for Slowlaris. See Sun's Web site for > details. That's what the announcement said, but it wasn't true, I tried it (with cash in hand) and they said they'd go along with it ONLY if the University was doing the ordering. > > -- > Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Mon Jul 7 15:40:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13670 for hackers-outgoing; Mon, 7 Jul 1997 15:40:59 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA13662 for ; Mon, 7 Jul 1997 15:40:56 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wlMO8-0004U8-00; Mon, 7 Jul 1997 15:36:08 -0700 Date: Mon, 7 Jul 1997 15:36:06 -0700 (PDT) From: Tom Samplonius To: Wilko Bulte cc: FreeBSD hackers list Subject: Re: experiences with seagate st32550N ? In-Reply-To: <199707071951.VAA01118@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Wilko Bulte wrote: > Hello, > > What is the general experience with a Seagate ST32550N disk? Good/bad? > Might be able to pick one up for a good price. > > TIA > Wilko > _ ____________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands > |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda > -------------------------------------------------------------------------- > > Barracuda 2LP 2GB narrow ? I have very good success with the new Barracuda 4LP/4XL series (available in 2 and 4GB sizes). But they are costly :( Tom From owner-freebsd-hackers Mon Jul 7 15:54:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14159 for hackers-outgoing; Mon, 7 Jul 1997 15:54:52 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA14153; Mon, 7 Jul 1997 15:54:45 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wlMbW-0004Up-00; Mon, 7 Jul 1997 15:49:58 -0700 Date: Mon, 7 Jul 1997 15:49:57 -0700 (PDT) From: Tom Samplonius To: Stefan Esser cc: Terry Lambert , costa@inner.cortx.com, freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <19970707214908.44376@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Jul 1997, Stefan Esser wrote: > On Jul 7, Tom Samplonius wrote: > > Also, the ncr controllers are little finicky. They have a delay option > > that I had to increase otherwise it wouldn't wait long enough for the > > drives to spin up. But I only had this problem on cold boots (never on > > warm), and only with the ncr controllers. The Adaptec controllers seem to > > wait much longer by default. > > The "NCR controllers" ??? > They don't exist ... :) Sure do. Symbios has come down to my place and re-labeled my controlor, and until they do, it will remain a NCR810. > In fact, there are several independently developed BIOS > versions offered with the various brands of NCR chip, > and even my (2.5 year old) ASUS SP3G lets you specify > an additional power on delay ... I have a ASUS 3P3G too, and had to lengthen the delay for the 4 drives I put on the internal SCSI bus. ... > > Quatum drives are known to go on a holiday after some continuous use. > > Grand Prix drives are particularly bad. In fact, I think the Atlas is the > > only respectible Quantum drive. > > How about the quality of the Atlas II and the Viking ? > I don't really understand, why they offer two 7200RPM > drives, again. Reminds me of the Atlas/Grand Prix ... The writing is on the wall for the Atlas II, now that the Atlas III is available. > Regards, STefan > > Tom From owner-freebsd-hackers Mon Jul 7 17:13:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16792 for hackers-outgoing; Mon, 7 Jul 1997 17:13:48 -0700 (PDT) Received: from argus.tfs.net (pm3-p5.tfs.net [206.154.183.197]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16781 for ; Mon, 7 Jul 1997 17:13:27 -0700 (PDT) Received: (from jbryant@localhost) by argus.tfs.net (8.8.5/8.8.5) id TAA03052; Mon, 7 Jul 1997 19:12:56 -0500 (CDT) From: Jim Bryant Message-Id: <199707080012.TAA03052@argus.tfs.net> Subject: Re: experiences with seagate st32550N ? In-Reply-To: <199707071951.VAA01118@yedi.iaf.nl> from Wilko Bulte at "Jul 7, 97 09:51:48 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Mon, 7 Jul 1997 19:12:55 -0500 (CDT) Cc: freebsd-hackers@freebsd.org Reply-to: jbryant@tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply: > Hello, > > What is the general experience with a Seagate ST32550N disk? Good/bad? > Might be able to pick one up for a good price. (ahc0:0:0): "SEAGATE ST32550N 0022" type 0 fixed SCSI 2 it rox!@# just keep it ventilated, and you will find it's a great drive. they tend to run a little warm. i have mine right in front of the power supply fan intake, and the front bay bezel is left off, this seems to keeps it from getting too warm. plus, if you get a bad one, or it goes bad within five years, seagate has an excellant warranty.. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" jbryant@tfs.net - KC5VDJ 2M, 70cm, KPC-3+ - kc5vdj@wv0t.#neks.ks.usa.noam From owner-freebsd-hackers Mon Jul 7 18:37:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20644 for hackers-outgoing; Mon, 7 Jul 1997 18:37:14 -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 SAA20639 for ; Mon, 7 Jul 1997 18:37:12 -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 SAA02838; Mon, 7 Jul 1997 18:38:42 -0700 (PDT) Message-Id: <199707080138.SAA02838@implode.root.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI Bridge Question In-reply-to: Your message of "Mon, 07 Jul 1997 10:24:21 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Jul 1997 18:38:42 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Then what version was it failing under? > >RELENG_2_2 as of Saturday. Are you maintaining this driver? Is there a >maintainer? Should I dig into it? I wrote it; I maintain it. >> an mbuf cluster had been freed onto the mclfree list. In any case, this >> appears to be a much more generic problem - not specific to the fxp >> device >> driver. > >Most likely. The fxp is where I see it on this system. I can't reproduce the problem here, but I haven't tried very hard. Is NFS static in your kernel, or is it getting loaded as an LKM? >BTW, what are your thoughts on my project using 3.0 kernel with 2.2 release? >We really like the SMP kernel, even where it stands today (already better >than >NiceTry :-) Use -current kernel with -current userland sources; start with 2.2.2 and upgrade to -current ("3.0") with a "make world" if necessary. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 7 18:40:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA20838 for hackers-outgoing; Mon, 7 Jul 1997 18:40:19 -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 SAA20832 for ; Mon, 7 Jul 1997 18:40:16 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id SAA09549 for ; Mon, 7 Jul 1997 18:39:58 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd009547; Tue Jul 8 01:39:48 1997 Message-ID: <33C19A05.15FB7483@whistle.com> Date: Mon, 07 Jul 1997 18:38:13 -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: Something screwy with 2.2.x? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been seeing sporadic SIG-11 failures on busy machines with 2.2.2+ (sources from last week. for example forking off 34 'ping -c 17 -s 500' (don't ask) will cause failures in random sh and ping processes. It's a small machine (8MB) so there's paging going on.. Unfortunatl;y the ping is not giving core dumps (why not?) even wne not suid root. the shell was doing so, but as more of the failures are happenning in ping, I'd like to see that core-file. Any ideas ? Am persuing my own inquiries.. julian From owner-freebsd-hackers Mon Jul 7 18:45:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21017 for hackers-outgoing; Mon, 7 Jul 1997 18:45:37 -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 SAA21011 for ; Mon, 7 Jul 1997 18:45:34 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA02910; Mon, 7 Jul 1997 18:47:01 -0700 (PDT) Message-Id: <199707080147.SAA02910@implode.root.com> To: Thomas David Rivers cc: hackers@freebsd.org Subject: Re: Why news expiration is sooo slowww with 2.2.x. In-reply-to: Your message of "Mon, 07 Jul 1997 07:35:43 EDT." <199707071135.HAA01419@lakes.water.net> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Jul 1997 18:47:01 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I should have mentioned, this is a 386-33 (with an Intel 387) and >only 8megs of RAM. Prior to 2.2.1, it took only a few hours to expire; >now it takes many days.... Examining swapinfo during this process >indicates swap is mostly free, so I don't believe my constrained memory >is the problem (I'm not even swapping...) Certainly my CPU is >slow, but it wasn't any faster prior to version 2.2.1.. :-) You might be hitting a knee on available buffers vs. directory size. Usenet has been a cesspool of cancel messages recently and I was seeing the control.cancel newsgroup > 10MB in size (per day!) recently. I had to set up a special cronjob just to delete all the crap every hour. Anyway, a directory that large (and any others) will interact very poorly when the buffer pool is real small - such as the case on a machine with only 8MB of main memory. You might try tinkering with the calculation of "nbuf" in /sys/i386/i386/machdep.c. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 7 19:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA21694 for hackers-outgoing; Mon, 7 Jul 1997 19:04:39 -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 TAA21687 for ; Mon, 7 Jul 1997 19:04:35 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA03071; Mon, 7 Jul 1997 19:06:04 -0700 (PDT) Message-Id: <199707080206.TAA03071@implode.root.com> To: Archie Cobbs cc: freebsd-hackers@FreeBSD.ORG Subject: Re: VJ compression and MAX_HDR In-reply-to: Your message of "Mon, 07 Jul 1997 12:01:07 PDT." <199707071901.MAA15711@bubba.whistle.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 07 Jul 1997 19:06:04 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> >(Max IP header = 64 bytes) + (max TCP header = 64 bytes) = 128 bytes > MLEN, >> >no? >> >> Perhaps, but I don't think any of the current TCP options are large enough >> for this to be a problem (I think the largest is still under 40 bytes). > >This makes it no less of a bug, just a bug that's not likely to hurt you :-) Certainly...I was only trying to put this into perspective - if we have a serious bug that needs to be acted on immediately, or if we have a "someday maybe" bug that doesn't affect anyone right now and can be fixed at some point in the future (measured in months or years :-)). I actually intended to acknowledge that it was a bug and should be fixed in the above, but I got interrupted and sent the reply prematurely. >Should I file a PR, so that it will be explicitly documented? Yes, that would be a good idea. It will be forgotten otherwise. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 7 19:50:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA23460 for hackers-outgoing; Mon, 7 Jul 1997 19:50:37 -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 TAA23455 for ; Mon, 7 Jul 1997 19:50:34 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA13125; Mon, 7 Jul 1997 22:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 7 Jul 1997 22:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id WAA25093; Mon, 7 Jul 1997 22:10:42 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id WAA03025; Mon, 7 Jul 1997 22:19:16 -0400 (EDT) Date: Mon, 7 Jul 1997 22:19:16 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707080219.WAA03025@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!lakes.water.net!rivers, ponds!sdf.com!tom Subject: Re: Why news expiration is sooo slowww with 2.2.x. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I should have mentioned, this is a 386-33 (with an Intel 387) and > > only 8megs of RAM. Prior to 2.2.1, it took only a few hours to expire; > > now it takes many days.... Examining swapinfo during this process > > indicates swap is mostly free, so I don't believe my constrained memory > > is the problem (I'm not even swapping...) Certainly my CPU is > > slow, but it wasn't any faster prior to version 2.2.1.. :-) > > Yes, but is your machine doing for these two to three days? Yes - it seems to be... > Is the CPU > load high? According to top - the CPU seems to be about 25-30% idle. Also, interestingly enough; doing an rm on as many files as I can before I run into the sh's command line limit takes about 20 minutes itself. top indicates the machine is still about 20-30% idle, with ~26% of the time taken up doing the 'rm'. The rm process seems to be in biowait a good portion of that time; which tends to indicate a disk bottle neck... e.g. - here's the first few lines of top - shortly after one of the "big" rm commands got started... last pid: 25001; load averages: 0.57, 0.61, 0.70 22:08:23 32 processes: 1 running, 30 sleeping, 1 zombie CPU states: 1.2% user, 0.0% nice, 25.2% system, 35.1% interrupt, 38.5% idle Mem: 3208K Active, 36K Inact, 2020K Wired, 1096K Cache, 515K Buf, 456K Free Swap: 150M Total, 5340K Used, 145M Free, 3% Inuse PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 25000 news -6 0 300K 88K biowai 0:14 24.16% 22.96% rm 25001 root 38 0 308K 680K RUN 0:07 12.83% 11.48% top 23095 root 18 0 448K 236K pause 0:03 0.00% 0.00% csh > Is the disk load high (iostat)? To what disk? Only have the one disk - the news directories are on a different partition; but that shouldn't affect the number of I/Os... Here's the result of iostat -c 3 (this was done during one the the 'rm' jobs, I had to kill expire and begin rebuilding the history file): # iostat -c 3 tty wd0 cpu tin tout sps tps msps us ni sy in id 972 93 684 43 17.3 7 0 29 28 37 0 37 922 57 10.5 1 0 29 33 38 0 35 773 47 13.2 1 0 26 32 41 > Do you do > delayed article removal? I run expire once a night; my explist does delay some things (hold on to them for a week) but the default for the bulk of news is to expire after two days... > > I can't tell the difference between 2.2 and 2.2.1 in terms of speed. Hmm... right now I can't recall if I ever had 2.2 running on the news server; so my experience may be relative to 2.1.7.1. I'd have to guess that things seem to be waiting in biowait() for quite some time... could it be changes in the wd driver (this is an IDE disk)? - Dave Rivers - From owner-freebsd-hackers Mon Jul 7 20:32:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24848 for hackers-outgoing; Mon, 7 Jul 1997 20:32:09 -0700 (PDT) Received: from lister.bogon.net (0@gw.bogon.net [204.137.132.49]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24843 for ; Mon, 7 Jul 1997 20:32:06 -0700 (PDT) Received: from kryten.bogon.net (500@kryten.bogon.net [204.137.132.58]) by lister.bogon.net (8.8.5/8.8.5) with ESMTP id UAA19993; Mon, 7 Jul 1997 20:32:04 -0700 (PDT) From: Wes Santee Received: (from wes@localhost) by kryten.bogon.net (8.8.6/8.8.5) id UAA08043; Mon, 7 Jul 1997 20:31:59 -0700 (PDT) Message-Id: <199707080331.UAA08043@kryten.bogon.net> Subject: Re: Is there a thread-happy recv()? In-Reply-To: <199707071826.LAA18090@phaeton.artisoft.com> from Terry Lambert at "Jul 7, 97 11:26:04 am" To: terry@lambert.org (Terry Lambert) Date: Mon, 7 Jul 1997 20:31:59 -0700 (PDT) Cc: gurney_j@resnet.uoregon.edu, wes@bogon.net, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From the desk of Terry Lambert comes: > > Wes Santee scribbled this message on Jul 6: > > > Hi all. I noticed in a chunk of code I'm writing that a blocking call > > > to recv() is putting the entire process to sleep such that even the > > > > don't use recv, use read instead... the reason recv isn't wrapped is > > that wrapping it is pointless, and may be removed in the future (from > > man page) > > What about recvfrom()? recvfrom() seems to work okay. I substituted it for recv() and everything completed normally without suspending the entire process. I should have tried it, but I try to avoid the functions that do the same, but with more parameters. :) Cheers, -- ( Wes Santee PGP: e-mail w/Subject: "Send PGP Key" ) ( mailto:wes@bogon.net ) From owner-freebsd-hackers Mon Jul 7 21:15:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26452 for hackers-outgoing; Mon, 7 Jul 1997 21:15:39 -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 VAA26441 for ; Mon, 7 Jul 1997 21:15:34 -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 VAA23637 for ; Mon, 7 Jul 1997 21:15:16 -0700 (PDT) To: hackers@freebsd.org Subject: no SYSVSHM in GENERIC now.. Date: Mon, 07 Jul 1997 21:15:16 -0700 Message-ID: <23634.868335316@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can't remember - why did we take it out? Jordan From owner-freebsd-hackers Mon Jul 7 21:31:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26909 for hackers-outgoing; Mon, 7 Jul 1997 21:31:28 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26903 for ; Mon, 7 Jul 1997 21:31:25 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id GAA16297 for ; Tue, 8 Jul 1997 06:31:20 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id GAA15572 for hackers@FreeBSD.ORG; Tue, 8 Jul 1997 06:31:15 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id AAA10511; Tue, 8 Jul 1997 00:07:49 +0200 (CEST) Message-ID: <19970708000749.16378@keltia.freenix.fr> Date: Tue, 8 Jul 1997 00:07:49 +0200 From: Ollivier Robert To: hackers@FreeBSD.ORG Subject: Re: /etc/rc.shutdown (Was: Re: DEVFS permissions &c.) References: <19970707225149.19828@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.76 In-Reply-To: =?iso-8859-1?Q?=3CPine=2EBSF=2E3=2E96=2E970708014302=2E2953A-100000=40ls?= =?iso-8859-1?Q?d=2Erelcom=2Eeu=2Enet=3E=3B_from_=E1=CE=C4=D2=C5=CA_=FE?= =?iso-8859-1?Q?=C5=D2=CE=CF=D7_on_Tue=2C_Jul_08=2C_1997_at_01=3A44=3A32A?= =?iso-8859-1?Q?M_+0400?= X-Operating-System: FreeBSD 3.0-CURRENT ctm#3392 AMD-K6 MMX @ 208 MHz Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to áÎÄÒÅÊ þÅÒÎÏ×: > rhushutdown() is part of shutdown, so logwtmp() must be BEFORE > runshutdown() call. Hmmmm, agreed. Will change it in my copy. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #20: Fri Jun 13 00:16:13 CEST 1997 From owner-freebsd-hackers Mon Jul 7 21:43:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27346 for hackers-outgoing; Mon, 7 Jul 1997 21:43:50 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27324 for ; Mon, 7 Jul 1997 21:43:02 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.6/8.6.9) with ESMTP id GAA17919; Tue, 8 Jul 1997 06:41:19 GMT Message-Id: <199707080641.GAA17919@peedub.gj.org> X-Mailer: exmh version 2.0delta 6/3/97 To: Julian Elischer Cc: freebsd-hackers@freefall.FreeBSD.org Subject: Re: Something screwy with 2.2.x? Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 07 Jul 1997 18:38:13 MST." <33C19A05.15FB7483@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jul 1997 06:41:19 +0000 From: Gary Jennejohn Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: >I've been seeing sporadic SIG-11 failures on busy machines >with 2.2.2+ (sources from last week. > >for example forking off 34 'ping -c 17 -s 500' >(don't ask) will cause failures in random sh and ping processes. > >It's a small machine (8MB) so there's paging going on.. >Unfortunatl;y the ping is not giving core dumps (why not?) >even wne not suid root. >the shell was doing so, but as more of the failures are happenning >in ping, I'd like to see that core-file. > >Any ideas ? > on my system ping is setuid root. Seems to me that the kernel refuses to generate core dumps for setuid processes. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-hackers Mon Jul 7 21:52:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27654 for hackers-outgoing; Mon, 7 Jul 1997 21:52:34 -0700 (PDT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27646 for ; Mon, 7 Jul 1997 21:52:31 -0700 (PDT) Received: from new-world.cs.rice.edu (new-world.cs.rice.edu [128.42.6.103]) by cs.rice.edu (8.8.5/8.7.1) with ESMTP id XAA00257 for ; Mon, 7 Jul 1997 23:52:08 -0500 (CDT) From: "Mark W. Krentel" Received: (from krentel@localhost) by new-world.cs.rice.edu (8.8.5/8.7.3) id XAA13559 for freebsd-hackers@FreeBSD.ORG; Mon, 7 Jul 1997 23:52:26 -0500 (CDT) Date: Mon, 7 Jul 1997 23:52:26 -0500 (CDT) Message-Id: <199707080452.XAA13559@new-world.cs.rice.edu> To: freebsd-hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can't remember - why did we take it out? I don't know, but I recommend putting SYSVSHM, SYSVSEM and SYSVMSG back into GENERIC. I've seen things in XFree86 that barf without them. Mark Krentel Rice University krentel@cs.rice.edu From owner-freebsd-hackers Mon Jul 7 22:05:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA27990 for hackers-outgoing; Mon, 7 Jul 1997 22:05:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA27981 for ; Mon, 7 Jul 1997 22:05:48 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id OAA31397; Tue, 8 Jul 1997 14:57:20 +1000 Date: Tue, 8 Jul 1997 14:57:20 +1000 From: Bruce Evans Message-Id: <199707080457.OAA31397@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: no SYSVSHM in GENERIC now.. Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I can't remember - why did we take it out? We never had them, except in in a forgotten branch :-). Bruce From owner-freebsd-hackers Mon Jul 7 23:10:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29915 for hackers-outgoing; Mon, 7 Jul 1997 23:10:05 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29869 for ; Mon, 7 Jul 1997 23:09:38 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id KAA22166; (8.8.2-MVC-141196/vak/1.9) Tue, 8 Jul 1997 10:05:17 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id JAA27784; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA12223 (5.65/IDA-simtel for hackers@freebsd.org); Tue, 8 Jul 1997 11:50:13 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Tue, 8 Jul 97 11:50:13 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: question about DDB Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I perform command 'trace' in DDB (kernel configuring with -g option) and receive next strings name_of_function(arg1=...,arg2=...,...) in /sys/compile/${MASHINE}:xxxx .... where xxxx - integer Questions: 1. what is the number xxxx ? 2. how I can see value of arg1, arg2, etc (I can see global variable only) # Á ÏÔ×ÅÞÁÔØ ÍÏÖÎÏ É ÐÏ ÒÕÓÓËÉ :) --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Mon Jul 7 23:29:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00706 for hackers-outgoing; Mon, 7 Jul 1997 23:29:29 -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 XAA00688 for ; Mon, 7 Jul 1997 23:29:24 -0700 (PDT) Received: (qmail 13749 invoked by uid 1000); 8 Jul 1997 06:29:34 -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: <199707080138.SAA02838@implode.root.com> Date: Mon, 07 Jul 1997 23:29:34 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: PCI Bridge Question Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 08-Jul-97 you wrote: > >> Then what version was it failing under? > > > >RELENG_2_2 as of Saturday. Are you maintaining this driver? Is there a > >maintainer? Should I dig into it? > > I wrote it; I maintain it. Great. Now i know who to blame :-) > > >> an mbuf cluster had been freed onto the mclfree list. In any case, > this > >> appears to be a much more generic problem - not specific to the fxp > >> device > >> driver. > > > >Most likely. The fxp is where I see it on this system. > > I can't reproduce the problem here, but I haven't tried very hard. Is > NFS > static in your kernel, or is it getting loaded as an LKM? * Setup BONDING PPP (128Kbps) * NFS mount a large file system (say, FreeBSD/packages-current) directly form the host you PPP to * cd to the NFS mount point * find . | cpio -dmpv /somewhere/else * Go about your business * Wait about 20-30 minutes [ I don't really expect you to do that. This is the setup I am using to ``prove'' the problem ] ... > Use -current kernel with -current userland sources; start with 2.2.2 > and > upgrade to -current ("3.0") with a "make world" if necessary. I understand the procedure and it works well. I was inquiring about 2.2 userland and -current kernel. Guess your answer is ``no''. the more I play with it, the less I like it (the hybrid idea). Simon From owner-freebsd-hackers Mon Jul 7 23:30:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00813 for hackers-outgoing; Mon, 7 Jul 1997 23:30:11 -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 XAA00744 for ; Mon, 7 Jul 1997 23:29:35 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.6/8.8.5) id IAA03908 for hackers@FreeBSD.ORG; Tue, 8 Jul 1997 08:29:20 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199707080629.IAA03908@helbig.informatik.ba-stuttgart.de> Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <23634.868335316@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 7, 97 09:15:16 pm" To: hackers@FreeBSD.ORG Date: Tue, 8 Jul 1997 08:29:17 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can't remember - why did we take it out? Because of space constraints - either boot.flp or 4 MByte RAM. I think it was boot.flp Wolfgang > > Jordan > From owner-freebsd-hackers Mon Jul 7 23:46:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01474 for hackers-outgoing; Mon, 7 Jul 1997 23:46:35 -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 XAA01469 for ; Mon, 7 Jul 1997 23:46:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA06241; Tue, 8 Jul 1997 16:13:51 +0930 (CST) From: Michael Smith Message-Id: <199707080643.QAA06241@genesis.atrad.adelaide.edu.au> Subject: Re: question about DDB In-Reply-To: from Igor at "Jul 8, 97 11:50:13 am" To: igor@blik.samara.su (Igor) Date: Tue, 8 Jul 1997 16:13:51 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Igor stands accused of saying: > I perform command 'trace' in DDB (kernel configuring with -g option) > and receive next strings > name_of_function(arg1=...,arg2=...,...) in /sys/compile/${MASHINE}:xxxx > .... > where xxxx - integer > Questions: > 1. what is the number xxxx ? There should be a filename in there as well; it's the line number the call was made on. > 2. how I can see value of arg1, arg2, etc (I can see global variable only) I don't know whether ddb groks local symbols or not; the values of the arguments at call time are there already. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Jul 8 00:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA02360 for hackers-outgoing; Tue, 8 Jul 1997 00:16:22 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA02355 for ; Tue, 8 Jul 1997 00:16:18 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA20977 for hackers@FreeBSD.ORG; Tue, 8 Jul 1997 09:16:16 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA06875; Tue, 8 Jul 1997 09:14:50 +0200 (MET DST) Message-ID: <19970708091450.QL25215@uriah.heep.sax.de> Date: Tue, 8 Jul 1997 09:14:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. References: <199707080457.OAA31397@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707080457.OAA31397@godzilla.zeta.org.au>; from Bruce Evans on Jul 8, 1997 14:57:20 +1000 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > >I can't remember - why did we take it out? > > We never had them, except in in a forgotten branch :-). ...where jkh added them. jkh seems to operate a lot on forgotten branches, and afterwards wonders why the bits didn't wander into the HEAD theirselves. :) But Jordan, don't add SYSVMSG, almost nobody uses them. They are really non-generic in a world that can use sockets to pass messages. (I know that there are differences, but nevertheless, they are not in wide use.) Even SYSVSEM is arguable, i think the only `canned' application that uses them is PEX. (Who uses PEX, anyway? :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 8 00:46:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03672 for hackers-outgoing; Tue, 8 Jul 1997 00:46:25 -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 AAA03661 for ; Tue, 8 Jul 1997 00:46:19 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id RAA27786; Tue, 8 Jul 1997 17:46:09 +1000 (EST) Date: Tue, 8 Jul 1997 17:45:58 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: news server behaviour Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [forwarded from isp due to lack of response] Hi, I've just put together a news server. I know it is underpowered somewhat. It is a Pentium 100, 32 MB RAM, wd0 is 540 MB IDE, sd0 is Quantum 730MB, sd1 is Quantum 1 GB. aha0 is 1542cf with 8Mbps scsi bus. sd0 and sd1 are ccd0 (/var/news) with interleave of 65536. News is coming in via a ppp link on a directly attached modem, at about 3-4kbps. It has been running for 36 hours and there is now 475 MB news on /var/news. There is no-one at all reading news. That all sounds reasonable, but I'm not so sure about the stats from top and systat -vmstat. Top shows innd (1.5.1) at 60-70% CPU (39% user, 50% system). Systat shows similar figures. I'm running kernel pppd with compression, and there seem to be about 4000 sio0 interrupts per systat refresh, but it shows 4% CPU for interrupt servicing. /var/news is mounted noatime. innd has 2 MB resident size. Is the CPU utilisation normal for the situation? In a previous incarnation the box was a Linux machine doing the same job under a different admin, and CPU for innd was more like 5-20% with no readers. /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Tue Jul 8 01:19:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04769 for hackers-outgoing; Tue, 8 Jul 1997 01:19:23 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04764 for ; Tue, 8 Jul 1997 01:19:20 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id BAA22304; Tue, 8 Jul 1997 01:21:30 -0700 (PDT) Date: Tue, 8 Jul 1997 01:21:30 -0700 (PDT) From: Howard Lew To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <19970708091450.QL25215@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, J Wunsch wrote: > As Bruce Evans wrote: > > > >I can't remember - why did we take it out? > > > > We never had them, except in in a forgotten branch :-). > > ...where jkh added them. jkh seems to operate a lot on forgotten > branches, and afterwards wonders why the bits didn't wander into the > HEAD theirselves. :) > > But Jordan, don't add SYSVMSG, almost nobody uses them. They are > really non-generic in a world that can use sockets to pass messages. > (I know that there are differences, but nevertheless, they are not in > wide use.) > > Even SYSVSEM is arguable, i think the only `canned' application that > uses them is PEX. (Who uses PEX, anyway? :) > Err uh... will taking this out prevent some programs from running properly? It will still be there as an option for us to add in our kernel if we need it right? > -- > 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. ;-) > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hackers Tue Jul 8 01:38:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA05664 for hackers-outgoing; Tue, 8 Jul 1997 01:38:36 -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 BAA05659 for ; Tue, 8 Jul 1997 01:38:33 -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 BAA24630; Tue, 8 Jul 1997 01:38:08 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Tue, 08 Jul 1997 09:14:50 +0200." <19970708091450.QL25215@uriah.heep.sax.de> Date: Tue, 08 Jul 1997 01:38:08 -0700 Message-ID: <24626.868351088@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ...where jkh added them. jkh seems to operate a lot on forgotten > branches, and afterwards wonders why the bits didn't wander into the > HEAD theirselves. :) Yeah yeah, well. What can I say? :) > But Jordan, don't add SYSVMSG, almost nobody uses them. They are > really non-generic in a world that can use sockets to pass messages. > (I know that there are differences, but nevertheless, they are not in > wide use.) > > Even SYSVSEM is arguable, i think the only `canned' application that > uses them is PEX. (Who uses PEX, anyway? :) I was thinking actually of just SYSVSHM so I don't have to see the X server whining all the time (or hear people reporting this). Jordan From owner-freebsd-hackers Tue Jul 8 01:55:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA06387 for hackers-outgoing; Tue, 8 Jul 1997 01:55:52 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA06380 for ; Tue, 8 Jul 1997 01:55:46 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id SAA01650; Tue, 8 Jul 1997 18:55:44 +1000 (EST) Message-Id: <199707080855.SAA01650@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Tom Samplonius Cc: freebsd-hackers@freebsd.org Subject: Re: Why news expiration is sooo slowww with 2.2.x. In-reply-to: Your message of "Sun, 06 Jul 1997 22:09:43 MST." X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jul 1997 18:55:44 +1000 From: David Nugent Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What options are you using on the "ls"? "-l" causes lots of getpwuid() > calls. I don't think he was using any options (otherwise it would require a stat(), but he said it didn't). But, fyi, doing this, particularly on a news spool where everything is owned by the same user/group, there'd only ever be one getpwuid(). ls uses libc's pwcache function, which caches user/group information. > > I thought I would try to investigate what the problem was, but, > > before that; I'd send out the standard "has anyone seen/done anything > > in this area already?" Has anyone else noticed an issue with > > readdir()? > > No. I have over 20GB of news spool space. It only takes a couple of > hours to expire. Uptime is currently at 37 days, running 2.2.1 Same here (on a 2.2.2 news server). Expiry usually takes less than an hour, and it isn't by any means a fast machine by today's standards (486DX4/100). Obviously we don't carry a full news feed. :) Regards, David From owner-freebsd-hackers Tue Jul 8 02:22:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07423 for hackers-outgoing; Tue, 8 Jul 1997 02:22:42 -0700 (PDT) Received: from sunny.wup.de (www.wup.de [149.237.200.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07417; Tue, 8 Jul 1997 02:22:35 -0700 (PDT) Received: (from andreas@localhost) by sunny.wup.de (8.8.6/8.8.6) id LAA09519; Tue, 8 Jul 1997 11:18:35 +0200 (MET DST) Message-ID: <19970708111834.07868@sunny.wup.de> Date: Tue, 8 Jul 1997 11:18:34 +0200 From: Andreas Klemm To: jkh@FreeBSD.org Cc: hackers@FreeBSD.org Subject: Additional problems with 2.2.2 CD-Rom installation (WWW Service) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Another one: tried to add apache WWW Server during installation: "Unable to fetch package apache-1.2b7 from selected media" I use the 2.2.2-RELEASE Boot Floppy from our ftp server and the official 2.2.2 CD-Rom. Andreas /// -- aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-hackers Tue Jul 8 02:26:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07549 for hackers-outgoing; Tue, 8 Jul 1997 02:26:13 -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 CAA07544; Tue, 8 Jul 1997 02:26:08 -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 CAA24941; Tue, 8 Jul 1997 02:25:37 -0700 (PDT) To: Andreas Klemm cc: jkh@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Additional problems with 2.2.2 CD-Rom installation (WWW Service) In-reply-to: Your message of "Tue, 08 Jul 1997 11:18:34 +0200." <19970708111834.07868@sunny.wup.de> Date: Tue, 08 Jul 1997 02:25:37 -0700 Message-ID: <24936.868353937@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Another one: tried to add apache WWW Server during installation: > > "Unable to fetch package apache-1.2b7 from selected media" > > I use the 2.2.2-RELEASE Boot Floppy from our ftp server and > the official 2.2.2 CD-Rom. Hmmm - probably forgot to sync versions at the last minute. In any case, that feature's gone now anyway. :) Jordan From owner-freebsd-hackers Tue Jul 8 03:46:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10409 for hackers-outgoing; Tue, 8 Jul 1997 03:46:14 -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 DAA10400 for ; Tue, 8 Jul 1997 03:46:09 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id MAA16934; Tue, 8 Jul 1997 12:45:54 +0200 (CEST) Date: Tue, 8 Jul 1997 12:45:54 +0200 (CEST) Message-Id: <199707081045.MAA16934@bitbox.follo.net> From: Eivind Eklund To: hackers@FreeBSD.ORG In-reply-to: j@uriah.heep.sax.de's message of Tue, 8 Jul 1997 09:14:50 +0200 Subject: Re: no SYSVSHM in GENERIC now.. References: <199707080457.OAA31397@godzilla.zeta.org.au> <19970708091450.QL25215@uriah.heep.sax.de> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [Jörg Wunsch] > But Jordan, don't add SYSVMSG, almost nobody uses them. They are > really non-generic in a world that can use sockets to pass messages. > (I know that there are differences, but nevertheless, they are not in > wide use.) KDE depends on them, so they might arguably be in very large use very soon. Of course, KDE hasn't deployed yet, so we might be able to talk them out of using it still... Eivind. From owner-freebsd-hackers Tue Jul 8 04:18:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA11761 for hackers-outgoing; Tue, 8 Jul 1997 04:18: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 EAA11754 for ; Tue, 8 Jul 1997 04:18:26 -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 EAA08592; Tue, 8 Jul 1997 04:19:47 -0700 (PDT) Message-Id: <199707081119.EAA08592@implode.root.com> To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: news server behaviour In-reply-to: Your message of "Tue, 08 Jul 1997 17:45:58 +1000." From: David Greenman Reply-To: dg@root.com Date: Tue, 08 Jul 1997 04:19:47 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >730MB, sd1 is Quantum 1 GB. aha0 is 1542cf with 8Mbps scsi bus. ... >That all sounds reasonable, but I'm not so sure about the stats from top >and systat -vmstat. Top shows innd (1.5.1) at 60-70% CPU (39% user, 50% >system). Systat shows similar figures. > >I'm running kernel pppd with compression, and there seem to be about 4000 >sio0 interrupts per systat refresh, but it shows 4% CPU for interrupt >servicing. > >/var/news is mounted noatime. innd has 2 MB resident size. > >Is the CPU utilisation normal for the situation? In a previous incarnation >the box was a Linux machine doing the same job under a different admin, >and CPU for innd was more like 5-20% with no readers. A couple of comments: FreeBSD might be accounting for the system CPU time more accurately than Linux. I also see that you're using a 1542 with > 16MB of RAM...which means that bounce buffers will be involved for about half of the I/O. This could have a significant effect on system time when doing lots of disk I/O. You didn't mention which version of FreeBSD you're using, but you might want to try enabling the Pentium bcopy optimization if it's not already enabled (make sure no npx0 flags are set). Is expire running? That might help explain the high numbers. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 8 04:34:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12443 for hackers-outgoing; Tue, 8 Jul 1997 04:34:40 -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 EAA12438 for ; Tue, 8 Jul 1997 04:34:36 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id VAA28707; Tue, 8 Jul 1997 21:34:25 +1000 (EST) Date: Tue, 8 Jul 1997 21:34:24 +1000 (EST) From: "Daniel O'Callaghan" To: David Greenman cc: freebsd-hackers@FreeBSD.ORG Subject: Re: news server behaviour In-Reply-To: <199707081119.EAA08592@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, David Greenman wrote: > >730MB, sd1 is Quantum 1 GB. aha0 is 1542cf with 8Mbps scsi bus. > ... > >That all sounds reasonable, but I'm not so sure about the stats from top > >and systat -vmstat. Top shows innd (1.5.1) at 60-70% CPU (39% user, 50% > >system). Systat shows similar figures. > > > >Is the CPU utilisation normal for the situation? In a previous incarnation > >the box was a Linux machine doing the same job under a different admin, > >and CPU for innd was more like 5-20% with no readers. > > A couple of comments: FreeBSD might be accounting for the system CPU time > more accurately than Linux. I also see that you're using a 1542 with > 16MB > of RAM...which means that bounce buffers will be involved for about half of I forgot about the bounce buffers having an effect. I guess the best thing to do is dig out an ahc 2940 and see what the effect is (apart from constructing a "proper" news server) > the I/O. This could have a significant effect on system time when doing lots > of disk I/O. You didn't mention which version of FreeBSD you're using, but > you might want to try enabling the Pentium bcopy optimization if it's not > already enabled (make sure no npx0 flags are set). Is expire running? That > might help explain the high numbers. Expire is not running. FreeBSD version is 2.2.2-RELEASE. npx0 config is from GENERIC. How do I enable the bcopy optimization? Thanks, Danny From owner-freebsd-hackers Tue Jul 8 04:39:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12609 for hackers-outgoing; Tue, 8 Jul 1997 04:39:45 -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 EAA12604 for ; Tue, 8 Jul 1997 04:39:43 -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 EAA08754; Tue, 8 Jul 1997 04:41:00 -0700 (PDT) Message-Id: <199707081141.EAA08754@implode.root.com> To: "Daniel O'Callaghan" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: news server behaviour In-reply-to: Your message of "Tue, 08 Jul 1997 21:34:24 +1000." From: David Greenman Reply-To: dg@root.com Date: Tue, 08 Jul 1997 04:41:00 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > npx0 config is >from GENERIC. How do I enable the bcopy optimization? Set npx0 flags to 0 - either in your kernel config file, or in "userconfig" at bootup. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 8 04:45:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12912 for hackers-outgoing; Tue, 8 Jul 1997 04:45:58 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA12906 for ; Tue, 8 Jul 1997 04:45:55 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id EAA08802; Tue, 8 Jul 1997 04:47:22 -0700 (PDT) Message-Id: <199707081147.EAA08802@implode.root.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI Bridge Question In-reply-to: Your message of "Mon, 07 Jul 1997 23:29:34 PDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 08 Jul 1997 04:47:22 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >> an mbuf cluster had been freed onto the mclfree list. In any case, >> this >> >> appears to be a much more generic problem - not specific to the fxp >> >> device >> >> driver. >> > >> >Most likely. The fxp is where I see it on this system. >> >> I can't reproduce the problem here, but I haven't tried very hard. Is >> NFS >> static in your kernel, or is it getting loaded as an LKM? > >* Setup BONDING PPP (128Kbps) >* NFS mount a large file system (say, FreeBSD/packages-current) directly > form the host you PPP to >* cd to the NFS mount point >* find . | cpio -dmpv /somewhere/else >* Go about your business >* Wait about 20-30 minutes > >[ I don't really expect you to do that. This is the setup I am using to > ``prove'' the problem ] It would be useful if you could examine the longword pointed to by mclfree; it is apparantly outside of the mb_map map range. Knowing it's value might give a clue as to the cause of the problem (then again, maybe not). >> Use -current kernel with -current userland sources; start with 2.2.2 >> and >> upgrade to -current ("3.0") with a "make world" if necessary. > >I understand the procedure and it works well. I was inquiring about 2.2 >userland and -current kernel. Guess your answer is ``no''. the more I play >with it, the less I like it (the hybrid idea). Right, I'm saying it's a bad idea and will cause problems. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Tue Jul 8 05:15:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA13991 for hackers-outgoing; Tue, 8 Jul 1997 05:15:54 -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 FAA13985 for ; Tue, 8 Jul 1997 05:15:51 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id OAA01985; (8.8.3/zah/2.1) Tue, 8 Jul 1997 14:59:13 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id MAA07678; (8.6.11/zah/2.1) Tue, 8 Jul 1997 12:05:05 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id NAA05218; (8.6.9/zah/1.1) Tue, 8 Jul 1997 13:59:51 +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 OAA08977; Tue, 8 Jul 1997 14:00:17 +0300 (EET DST) Message-ID: <33C21026.59@cki.ipri.kiev.ua> Date: Tue, 08 Jul 1997 13:02:13 +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: Bruce Evans CC: hackers@FreeBSD.ORG, jkh@time.cdrom.com Subject: Re: no SYSVSHM in GENERIC now.. References: <199707080457.OAA31397@godzilla.zeta.org.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > >I can't remember - why did we take it out? > Hmm, and why X work with GENERIC ? (it' s print messages on console, but work fine) > We never had them, except in in a forgotten branch :-). > > Bruce From owner-freebsd-hackers Tue Jul 8 05:19:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA14150 for hackers-outgoing; Tue, 8 Jul 1997 05:19:45 -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 FAA14145 for ; Tue, 8 Jul 1997 05:19:42 -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 FAA28670; Tue, 8 Jul 1997 05:17:54 -0700 (PDT) To: rssh@cki.ipri.kiev.ua cc: Bruce Evans , hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Tue, 08 Jul 1997 13:02:13 +0300." <33C21026.59@cki.ipri.kiev.ua> Date: Tue, 08 Jul 1997 05:17:54 -0700 Message-ID: <28667.868364274@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hmm, and why X work with GENERIC ? > (it' s print messages on console, but work fine) Because it's not mandatory for the X server to support the MIT-SHM extention. If you don't have it, it doesn't. Jordan From owner-freebsd-hackers Tue Jul 8 08:28:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22355 for hackers-outgoing; Tue, 8 Jul 1997 08:28: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 IAA22348 for ; Tue, 8 Jul 1997 08:28:00 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA19235; Tue, 8 Jul 1997 09:27:54 -0600 (MDT) Date: Tue, 8 Jul 1997 09:27:54 -0600 (MDT) Message-Id: <199707081527.JAA19235@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <23634.868335316@time.cdrom.com> References: <23634.868335316@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I can't remember - why did we take it out? The size of the kernel was too big for the floppies. Nate From owner-freebsd-hackers Tue Jul 8 08:40:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22938 for hackers-outgoing; Tue, 8 Jul 1997 08:40:14 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA22927 for ; Tue, 8 Jul 1997 08:40:11 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id KAA04638; Tue, 8 Jul 1997 10:39:49 -0500 (EST) Date: Tue, 8 Jul 1997 10:39:49 -0500 (EST) From: John Fieber To: Joerg Wunsch cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <19970708091450.QL25215@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, J Wunsch wrote: > Even SYSVSEM is arguable, i think the only `canned' application that > uses them is PEX. (Who uses PEX, anyway? :) Wine seems to use them, and I think postgresql must because wine allocates bunches of semaphores but doesn't release them, and postgresql fails if wine has been run until you manually ipcrm the semaphors that wine left hanging around.... Postgresql definately uses SYSVSHM. -john From owner-freebsd-hackers Tue Jul 8 08:40:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA22988 for hackers-outgoing; Tue, 8 Jul 1997 08:40:44 -0700 (PDT) Received: from weblanix.vianet.com.mx (200-23-228-1.intervan.com.mx [200.23.228.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA22982 for ; Tue, 8 Jul 1997 08:40:36 -0700 (PDT) Received: from APARADA (APARADA [200.23.228.3]) by weblanix.vianet.com.mx (NTMail 3.02.10) with ESMTP id ia023356 for ; Tue, 8 Jul 1997 10:39:25 +0000 From: "Alejandro I. Parada Aguilera" To: Subject: I need help Date: Tue, 8 Jul 1997 10:39:13 -0600 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1162 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <16392526509480@vianet.com.mx> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! I'm a new user in Freebsd. it is my problem, i need refuse a IP address in my routers; i have 6 routers. Departamento de Ingeniería de Servicio Ing. Alejandro I. Parada Aguilera Tel.: 671-1012 aparada@vianet.com.mx aparada@topservice.com http://www.vianet.com.mx/amigos/aparada/ ____________________________________ From owner-freebsd-hackers Tue Jul 8 09:02:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24092 for hackers-outgoing; Tue, 8 Jul 1997 09:02:56 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24087 for ; Tue, 8 Jul 1997 09:02:52 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id JAA06763; Tue, 8 Jul 1997 09:02:05 -0700 (PDT) Message-Id: <199707081602.JAA06763@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jordan K. Hubbard" cc: rssh@cki.ipri.kiev.ua, Bruce Evans , hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Tue, 08 Jul 1997 05:17:54 PDT." <28667.868364274@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jul 1997 09:02:05 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From a cdrom, can users select a kernel from a list or dependencies on packages? Tnks, Amancio From owner-freebsd-hackers Tue Jul 8 11:46:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA01615 for hackers-outgoing; Tue, 8 Jul 1997 11:46:36 -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 LAA01609 for ; Tue, 8 Jul 1997 11:46:34 -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 LAA29692; Tue, 8 Jul 1997 11:46:16 -0700 (PDT) To: Nate Williams cc: hackers@freebsd.org Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Tue, 08 Jul 1997 09:27:54 MDT." <199707081527.JAA19235@rocky.mt.sri.com> Date: Tue, 08 Jul 1997 11:46:15 -0700 Message-ID: <29688.868387575@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk That can't be it - those options are stripped out for BOOTMFS. Jordan > > I can't remember - why did we take it out? > > The size of the kernel was too big for the floppies. > > > Nate From owner-freebsd-hackers Tue Jul 8 13:21:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05968 for hackers-outgoing; Tue, 8 Jul 1997 13:21:20 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA05956 for ; Tue, 8 Jul 1997 13:21:16 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id QAA13217 for ; Tue, 8 Jul 1997 16:20:32 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id QAA00222 for ; Tue, 8 Jul 1997 16:20:20 -0400 (EDT) Message-Id: <199707082020.QAA00222@bmcgover-pc.cisco.com> To: hackers@freebsd.org Subject: PPP input processing problem (slowness) Date: Tue, 08 Jul 1997 16:20:19 -0400 From: Brian McGovern Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a bit of a problem with my device driver when receiving PPP packets. I've taken a look at sio.c and read what I can find in the BSD 4.4 Implementation book (read - the Red Book), and I'm doing what I'm told I'm supposed to do. Obviously, I'm missing something :) Transmitting packets work fine, as does character mode. The problem appears in getting the system to process incoming packets. Basically, in my interrupt handler, I do EITHER move the bytes with b_to_q() to &tp->t_rawq OR use l_rint to move the bytes, one at a time. THEN call setsofttty(). I have no idea what this does, but the sio driver had it, so its here... :) call ttwakeup(); Also, based on what else happens during the interrupt cycle, wakeup(tp) and ttwwakeup(tp) can also get called. Any suggestions are welcome. -Brian From owner-freebsd-hackers Tue Jul 8 16:06:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14904 for hackers-outgoing; Tue, 8 Jul 1997 16:06:59 -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 QAA14896 for ; Tue, 8 Jul 1997 16:06:54 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id QAA03183 for ; Tue, 8 Jul 1997 16:06:53 -0700 (PDT) Date: Tue, 8 Jul 1997 16:06:52 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: Not sure about this netstat -ss output Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was messing around with Net.Medic's vitalsigns the other day, and it told me that my DNS server was having problems responding. It's a P120, 64MB RAM, BIND 4.9.5-p1 (recently upgraded to 4.9.6), under a version of FreeBSD 2.2-current from Aug of 96. The machine has been running for about 4 months, does this output look abnormal? udp: 126913455 datagrams received 6 with bad data length field 498 with bad checksum 428654 dropped due to no socket 10764636 broadcast/multicast datagrams dropped due to no socket 143 dropped due to full socket buffers 115150923 not for hashed pcb 115719518 delivered 118314487 datagrams output The no socket/no hashed pcb ones have me concerned, the full socket buffers not so much, although perhaps a kernel parameter could be tweaked? I haven't noticed any problem myself with the nameserver, but perhaps my machines are running off the backups or somesuch. From owner-freebsd-hackers Tue Jul 8 16:25:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15867 for hackers-outgoing; Tue, 8 Jul 1997 16:25:27 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15862 for ; Tue, 8 Jul 1997 16:25:25 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id <3PASSYJV>; Tue, 8 Jul 1997 18:24:54 -0500 Message-ID: From: Raul Zighelboim To: "'hackers@freefall.freebsd.org'" Subject: There must be something really wrong with 2.2.2-release... Date: Tue, 8 Jul 1997 18:24:52 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello there. I manage a few FreeBSD boxes. 3 of these boxes are running FreeBSD 2.2.2 RELEASE.Those 3 boxes are configured very differently: 1 Usenet news server with (a ppro with 256 megs of ram, used and abused). 1 a mail server with 18 megs of ram, and some 16 mailboxes 1 a socks server with 64 megs of ram and a handfull (may 15 ! 20 at a time) connections. The hardware on these 3 system is very different. they do not have anything in common; different MB, controllers, ... These 3 boxes tend to crash after a while, with 'not enough swap space' or not enough mbuf'. Although I cannot guaranty that the problem is related to 2.2.2-RELEASE, none of the other systems I have access to is having thes problems. Has anyine seens this behavior ? As I monitor the news server much closely than the other machines: I have at this time 768Megs of swap space on the machine, and I have noticed that: the first day the system is up, no more than 1% if the swap space is used. The second day, I can see swap space jump to 60 - 70 - 80% (before I reboot the machine). Killing all processes (no reboot) extends the life of the system a little. I am running innd (with a few optimization patches) and named uucp and sendmail on this system). From owner-freebsd-hackers Tue Jul 8 16:29:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16094 for hackers-outgoing; Tue, 8 Jul 1997 16:29:21 -0700 (PDT) Received: from numachi.numachi.com (numachi.numachi.com [198.175.254.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16073 for ; Tue, 8 Jul 1997 16:29:14 -0700 (PDT) Received: (from reichert@localhost) by numachi.numachi.com (8.8.5/8.8.5) id TAA02265; Tue, 8 Jul 1997 19:29:03 -0400 (EDT) Message-ID: <19970708192857.54365@numachi.numachi.com> Date: Tue, 8 Jul 1997 19:28:58 -0400 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: xmcd-2.1 and NEC ATAPI drive Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.68 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I don't know if this was supposed to be a problem, but I had to do some arm-wrestling to get xmcd-2.1 to recognize my cdrom. What I have: 2.2.1-RELEASE wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, iordy wcd0: 689Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray The xmcd package was convinced that the 'proper' device was /dev/rcd0c, which is not the case at all on my box. I had to yank the device checks out of its guts, as well at it's install utility. Seems to be behaving at this point, although I can't get it to close the door. I might be able to solve that by editing it's config file. My question: has anyone else gotten any grief from this utility, or did I end up with a mutant box/intallation? -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Derry NH 03038-1713 USA Intel architecture: the left-hand path From owner-freebsd-hackers Tue Jul 8 17:32:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA19540 for hackers-outgoing; Tue, 8 Jul 1997 17:32:47 -0700 (PDT) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA19535 for ; Tue, 8 Jul 1997 17:32:44 -0700 (PDT) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.5/8.8.5) with ESMTP id UAA19964; Tue, 8 Jul 1997 20:31:10 -0400 (EDT) Message-Id: <199707090031.UAA19964@spooky.rwwa.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Howard Lew cc: Joerg Wunsch , hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Tue, 08 Jul 1997 01:21:30 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jul 1997 20:31:09 -0400 From: Robert Withrow Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hlew@www2.shoppersnet.com said: :- Err uh... will taking this out prevent some programs from running :- properly? It will still be there as an option for us to add in our :- kernel if we need it right? Postgres won't work right. ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM From owner-freebsd-hackers Tue Jul 8 21:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26671 for hackers-outgoing; Tue, 8 Jul 1997 21:35:05 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA26651 for ; Tue, 8 Jul 1997 21:34:58 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wloOF-0005Iy-00; Tue, 8 Jul 1997 21:30:07 -0700 Date: Tue, 8 Jul 1997 21:30:07 -0700 (PDT) From: Tom Samplonius To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Not sure about this netstat -ss output In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, Jaye Mathisen wrote: > I was messing around with Net.Medic's vitalsigns the other day, and it > told me that my DNS server was having problems responding. Net.Quack is junk. Since it runs in the background (and Win95 multitasking isn't so great), it will report all kinds of "slow downs" as you do stuff in the foreground. It will also misreport all kinds of connection problems. For example, if you disconnect the ethernet, it wil tell you the DNS server and gateway routers are down. But of course they aren't, the connection itself is down, but net.quack can't tell the difference! Plus, if you do a big download at the same moment that net.medic is "testing", it determine that all kinds of things are "slow". If you want to test DNS response time, use "dig" under unix. It gives you the DNS server response times in ms. Meanwhile, I'm still trying to figure out what units net.quack uses. Tom From owner-freebsd-hackers Tue Jul 8 21:36:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26770 for hackers-outgoing; Tue, 8 Jul 1997 21:36:12 -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 VAA26759 for ; Tue, 8 Jul 1997 21:36:08 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wloPN-0005J2-00; Tue, 8 Jul 1997 21:31:17 -0700 Date: Tue, 8 Jul 1997 21:31:17 -0700 (PDT) From: Tom Samplonius To: Raul Zighelboim cc: "'hackers@freefall.freebsd.org'" Subject: Re: There must be something really wrong with 2.2.2-release... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, Raul Zighelboim wrote: > These 3 boxes tend to crash after a while, with 'not enough swap > space' or not enough mbuf'. You need to allocated more swap space, and more mbuf space. Tom From owner-freebsd-hackers Wed Jul 9 01:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA04169 for hackers-outgoing; Wed, 9 Jul 1997 01:02:15 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA04162 for ; Wed, 9 Jul 1997 01:02:11 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA17725; Wed, 9 Jul 1997 17:50:47 +1000 Date: Wed, 9 Jul 1997 17:50:47 +1000 From: Bruce Evans Message-Id: <199707090750.RAA17725@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, mango@communique.net Subject: Re: kern.maxvnodes and systat -v Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >When running 2.1.7-RELEASE of freebsd, setting kern.maxvnodes=32000 on the kernel (sysctl -w ...) would increase the number of vnodes from the default. > >I could see this increase on the 'systat -v' window under buf on the bottom right column, under cow. > >The I upgraded to 2.2.2-RELEASE. > >Now systat -v show always '16415 buf' (ie, 16000). > >Is this a bug, or something I am reading wrong ? `buf' gives the number of Kbytes for buffers. It has nothing to do with kern.maxvnodes. The kern.maxvnodes sysctl is somewhat broken in all versions of FreeBSD. In all released versions, it changes a limit on the number of vnodes but not the size of the namecache hash table. This isn't much of a problem in practice. In some old unreleased versions, kern.maxvnodes was readonly. In -current, changing the variable behind kern.maxvnodes (desirevnodes) is a no-op (desiredvnodes no longer has anything to do with vnodes; it is only used to size the namecache hash table, and this table is initialized before the kern.maxvnode sysctl can be executed). Bruce From owner-freebsd-hackers Wed Jul 9 01:38:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA05581 for hackers-outgoing; Wed, 9 Jul 1997 01:38:08 -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 BAA05574 for ; Wed, 9 Jul 1997 01:38:02 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.6/8.8.3) id LAA08745; Wed, 9 Jul 1997 11:35:44 +0300 (EET DST) From: mika ruohotie Message-Id: <199707090835.LAA08745@shadows.aeon.net> Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: from Narvi at "Jun 12, 97 10:49:39 am" To: narvi@haldjas.folklore.ee (Narvi) Date: Wed, 9 Jul 1997 11:35:44 +0300 (EET DST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk i know, an old post... > if I add options PQ_LARGECACHE to the kernel config file. i dont remember anyone commenting this, so what is it? something we with 512K cache should use or not? mickey From owner-freebsd-hackers Wed Jul 9 04:44:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA10833 for hackers-outgoing; Wed, 9 Jul 1997 04:44:51 -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 EAA10826 for ; Wed, 9 Jul 1997 04:44:45 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id VAA04331; Wed, 9 Jul 1997 21:44:41 +1000 (EST) Date: Wed, 9 Jul 1997 21:44:40 +1000 (EST) From: "Daniel O'Callaghan" To: freebsd-hackers@freebsd.org Subject: Re: news server behaviour Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm still puzzled by the news server behaviour. The machine is a P100 with 32 MB RAM, 1 x 1GB and 1 x 730 MB quantum HDD, no readers, receiving about kbps from a ppp connection. Innd shows CPU usage of 90%; user CPU is about 45%; system CPU is about 50%. I did have an adaptec 1542cf host adapter and DG suggested the bounce buffers were causing problems. He also suggested enabling the Pentium bcopy optimizations. I have replaced the 1542cf with a 2940 pci host adapter and enabled the bcopy optimizations, with no discernable difference in behaviour. Below is the output of 'iostat -c 50'. Can anyone tell me why the CPU is spending so much time on system things? Thanks, Danny tty sd0 sd1 wd0 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 221 61 11 1 0.0 6 0 0.0 12 1 12.0 9 0 14 1 76 598 0 20 2 0.0 16 1 0.0 214 13 17.8 33 0 60 4 4 15 0 44 3 0.0 167 15 0.0 60 4 9.9 36 0 47 2 16 0 0 0 0 0.0 0 0 0.0 0 0 0.0 39 0 60 1 0 0 0 0 0 0.0 167 11 0.0 0 0 0.0 27 0 56 2 15 4340 0 16 2 0.0 65 8 0.0 91 5 18.1 43 0 53 4 0 0 0 0 0 0.0 16 1 0.0 0 0 0.0 36 0 64 1 0 445 0 60 6 0.0 0 0 0.0 0 0 0.0 35 0 56 1 9 902 0 100 7 0.0 10 1 0.0 32 2 13.7 51 0 48 2 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 29 0 71 0 0 2351 0 107 8 0.0 0 0 0.0 32 2 9.8 34 0 60 2 5 0 0 32 4 0.0 0 0 0.0 0 0 0.0 42 0 58 0 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 25 0 75 0 0 62 0 28 2 0.0 0 0 0.0 0 0 0.0 25 0 71 2 3 980 0 62 5 0.0 0 0 0.0 32 2 2.0 38 0 57 5 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 31 0 67 2 0 0 0 603 38 0.0 191 12 0.0 0 0 0.0 22 0 35 1 42 0 0 42 4 0.0 16 1 0.0 32 2 5.9 48 0 51 1 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 33 0 67 0 0 1727 0 16 1 0.0 0 0 0.0 32 2 5.9 44 0 53 3 0 tty sd0 sd1 wd0 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 0 0 0 0 0.0 0 0 0.0 0 0 0.0 46 0 53 1 0 0 0 0 0 0.0 175 11 0.0 0 0 0.0 22 0 61 1 16 0 0 619 40 0.0 32 2 0.0 34 3 11.6 29 0 43 3 26 0 0 85 7 0.0 32 2 0.0 374 27 13.9 42 0 47 12 0 1116 0 79 6 0.0 0 0 0.0 0 0 0.0 40 0 53 3 5 0 0 0 0 0.0 0 0 0.0 0 0 0.0 34 0 63 3 0 153 0 22 2 0.0 0 0 0.0 0 0 0.0 32 0 64 2 3 1791 0 49 5 0.0 0 0 0.0 33 3 14.2 39 0 58 2 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 33 0 67 0 0 0 0 587 37 0.0 191 12 0.0 0 0 0.0 19 0 34 2 45 0 0 35 4 0.0 16 1 0.0 32 2 13.7 42 0 57 2 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 30 0 69 1 0 1277 0 16 1 0.0 0 0 0.0 32 2 9.8 45 0 52 3 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 41 0 57 2 0 0 0 95 6 0.0 167 11 0.0 0 0 0.0 24 0 51 2 23 2083 0 54 4 0.0 48 4 0.0 32 2 5.9 47 0 47 3 3 0 0 0 0 0.0 0 0 0.0 0 0 0.0 43 0 57 1 0 600 0 28 2 0.0 0 0 0.0 0 0 0.0 40 0 56 1 3 943 0 37 3 0.0 43 4 0.0 47 3 13.7 39 0 58 3 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 32 0 68 0 0 tty sd0 sd1 wd0 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 2098 0 52 5 0.0 0 0 0.0 32 2 13.7 41 0 57 1 1 0 0 28 2 0.0 0 0 0.0 0 0 0.0 36 0 61 2 0 0 0 0 0 0.0 158 10 0.0 0 0 0.0 28 0 55 2 15 0 0 637 42 0.0 48 3 0.0 32 2 5.9 33 0 36 2 28 0 0 0 0 0.0 0 0 0.0 0 0 0.0 40 0 59 1 0 63 0 0 0 0.0 0 0 0.0 0 0 0.0 32 0 68 0 0 1532 0 16 1 0.0 0 0 0.0 32 2 5.9 37 0 61 2 0 0 0 0 0 0.0 0 0 0.0 0 0 0.0 39 0 61 0 0 0 0 587 37 0.0 191 12 0.0 0 0 0.0 24 0 37 1 38 0 0 30 3 0.0 16 1 0.0 32 2 5.9 45 0 53 2 0 From owner-freebsd-hackers Wed Jul 9 05:46:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA12781 for hackers-outgoing; Wed, 9 Jul 1997 05:46:41 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12710 for ; Wed, 9 Jul 1997 05:45:23 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id PAA11833; Wed, 9 Jul 1997 15:32:46 +0300 (EEST) Date: Wed, 9 Jul 1997 15:32:37 +0300 (EEST) From: Narvi To: Eivind Eklund cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-Reply-To: <199707081045.MAA16934@bitbox.follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id FAA12773 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, Eivind Eklund wrote: > > [Jörg Wunsch] > > But Jordan, don't add SYSVMSG, almost nobody uses them. They are > > really non-generic in a world that can use sockets to pass messages. > > (I know that there are differences, but nevertheless, they are not in > > wide use.) > > KDE depends on them, so they might arguably be in very large use very > soon. Of course, KDE hasn't deployed yet, so we might be able to talk > them out of using it still... > Well, in 2.1 times my Xserver used to complain if there was no SYSVIPC in my kernel. Perhaps it has changed. The semaphores are also handy (the most widely used of the three?). Sander There is no love, no good, no happiness and no future - all these are just illusions. > Eivind. > From owner-freebsd-hackers Wed Jul 9 07:15:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16228 for hackers-outgoing; Wed, 9 Jul 1997 07:15:23 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16222 for ; Wed, 9 Jul 1997 07:15:19 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id <3PASSYY9>; Wed, 9 Jul 1997 09:14:47 -0500 Message-ID: From: Raul Zighelboim To: hackers@FreeBSD.ORG Subject: RE: kern.maxvnodes and systat -v Date: Wed, 9 Jul 1997 09:14:45 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is there a way I can increase the # of Kbytes fro buffers ? Thanks. > `buf' gives the number of Kbytes for buffers. It has nothing to do > with > kern.maxvnodes. > > The kern.maxvnodes sysctl is somewhat broken in all versions of > FreeBSD. > In all released versions, it changes a limit on the number of vnodes > but not the size of the namecache hash table. This isn't much of a > problem in practice. In some old unreleased versions, kern.maxvnodes > was readonly. In -current, changing the variable behind > kern.maxvnodes > (desirevnodes) is a no-op (desiredvnodes no longer has anything to do > with vnodes; it is only used to size the namecache hash table, and > this > table is initialized before the kern.maxvnode sysctl can be executed). > > Bruce From owner-freebsd-hackers Wed Jul 9 07:30:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17045 for hackers-outgoing; Wed, 9 Jul 1997 07:30:52 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17040 for ; Wed, 9 Jul 1997 07:30:47 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id <3PASSYZ4>; Wed, 9 Jul 1997 09:30:15 -0500 Message-ID: From: Raul Zighelboim Cc: "'hackers@freefall.freebsd.org'" Subject: RE: There must be something really wrong with 2.2.2-release... Date: Wed, 9 Jul 1997 09:30:13 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have 768Megs of swap space on one of the machines, and MAXUSERS set to 256. I don;t believe that mode swap is an option, as the system is already trashing when using 1/2 of that swap space..... Is there a way I set mbuf to a larger value without involving MAXUSERS ? > -----Original Message----- > From: Tom Samplonius [SMTP:tom@sdf.com] > Sent: Tuesday, July 08, 1997 11:31 PM > To: Raul Zighelboim > Cc: 'hackers@freefall.freebsd.org' > Subject: Re: There must be something really wrong with > 2.2.2-release... > > > On Tue, 8 Jul 1997, Raul Zighelboim wrote: > > > These 3 boxes tend to crash after a while, with 'not enough swap > > space' or not enough mbuf'. > > You need to allocated more swap space, and more mbuf space. > > Tom From owner-freebsd-hackers Wed Jul 9 07:35:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17343 for hackers-outgoing; Wed, 9 Jul 1997 07:35:53 -0700 (PDT) Received: from kaori.communique.net (kaori.Communique.Net [204.27.65.55]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17336 for ; Wed, 9 Jul 1997 07:35:50 -0700 (PDT) Received: by kaori.Communique.Net with Internet Mail Service (5.0.1457.3) id <3PASSYZZ>; Wed, 9 Jul 1997 09:35:19 -0500 Message-ID: From: Raul Zighelboim Cc: "'hackers@freefall.freebsd.org'" Subject: RE: There must be something really wrong with 2.2.2-release... Date: Wed, 9 Jul 1997 09:35:18 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk BTW- I just checked one t=of the low-profile systems. running inetd/sendmail and one telnetd session (+ the kernel) and I had some 16Megs of cache used. I killed inetd/sendmail, so only the kernel was sunning (and my telnetd) and swapinfo still reported 30% of 48Megs cache in use... > -----Original Message----- > From: Tom Samplonius [SMTP:tom@sdf.com] > Sent: Tuesday, July 08, 1997 11:31 PM > To: Raul Zighelboim > Cc: 'hackers@freefall.freebsd.org' > Subject: Re: There must be something really wrong with > 2.2.2-release... > > > On Tue, 8 Jul 1997, Raul Zighelboim wrote: > > > These 3 boxes tend to crash after a while, with 'not enough swap > > space' or not enough mbuf'. > > You need to allocated more swap space, and more mbuf space. > > Tom From owner-freebsd-hackers Wed Jul 9 09:10:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA21759 for hackers-outgoing; Wed, 9 Jul 1997 09:10: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 JAA21754 for ; Wed, 9 Jul 1997 09:10:45 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wlzFZ-0005gn-00; Wed, 9 Jul 1997 09:05:53 -0700 Date: Wed, 9 Jul 1997 09:05:52 -0700 (PDT) From: Tom Samplonius To: Raul Zighelboim cc: "'hackers@freefall.freebsd.org'" Subject: RE: There must be something really wrong with 2.2.2-release... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Jul 1997, Raul Zighelboim wrote: > I have 768Megs of swap space on one of the machines, and > MAXUSERS set to 256. > I don;t believe that mode swap is an option, as the system is > already trashing when using 1/2 of that swap space..... > Is there a way I set mbuf to a larger value without involving > MAXUSERS ? But process is using up all the swap (look through ps -aux)? mbufs can be increased with "options NMBCLUSTERS". See LINT. It almost seems like someone is trashing on your server. I have a shell server that runs out mbufs when an bunch of IRC bots go out of control. Tom > > -----Original Message----- > > From: Tom Samplonius [SMTP:tom@sdf.com] > > Sent: Tuesday, July 08, 1997 11:31 PM > > To: Raul Zighelboim > > Cc: 'hackers@freefall.freebsd.org' > > Subject: Re: There must be something really wrong with > > 2.2.2-release... > > > > > > On Tue, 8 Jul 1997, Raul Zighelboim wrote: > > > > > These 3 boxes tend to crash after a while, with 'not enough swap > > > space' or not enough mbuf'. > > > > You need to allocated more swap space, and more mbuf space. > > > > Tom > > From owner-freebsd-hackers Wed Jul 9 10:03:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24888 for hackers-outgoing; Wed, 9 Jul 1997 10:03:55 -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 KAA24879 for ; Wed, 9 Jul 1997 10:03:49 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id MAA00264; Wed, 9 Jul 1997 12:02:32 -0500 (EST) From: "John S. Dyson" Message-Id: <199707091702.MAA00264@dyson.iquest.net> Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: <199707090835.LAA08745@shadows.aeon.net> from mika ruohotie at "Jul 9, 97 11:35:44 am" To: bsdhack@shadows.aeon.net (mika ruohotie) Date: Wed, 9 Jul 1997 12:02:32 -0500 (EST) Cc: narvi@haldjas.folklore.ee, hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > i know, an old post... > > > if I add options PQ_LARGECACHE to the kernel config file. > > i dont remember anyone commenting this, so what is it? > > something we with 512K cache should use or not? > If you have a 512K direct mapped cache, it is significantly useful. If you have a 4-way cache like on the PPro, it is useful, but just a little less so. John From owner-freebsd-hackers Wed Jul 9 10:15:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA25462 for hackers-outgoing; Wed, 9 Jul 1997 10:15:40 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA25457 for ; Wed, 9 Jul 1997 10:15:36 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-7.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA22632 (5.67b/IDA-1.5 for ); Wed, 9 Jul 1997 19:11:38 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id TAA04285; Wed, 9 Jul 1997 19:11:36 +0200 (CEST) X-Face: " Date: Wed, 9 Jul 1997 19:11:36 +0200 From: Stefan Esser To: Tom Samplonius Cc: Terry Lambert , costa@inner.cortx.com, freebsd-hackers@FreeBSD.ORG Subject: Re: sd0 timed out while idle References: <19970707214908.44376@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Tom Samplonius on Mon, Jul 07, 1997 at 03:49:57PM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 7, Tom Samplonius wrote: > On Mon, 7 Jul 1997, Stefan Esser wrote: > > The "NCR controllers" ??? > > They don't exist ... :) > > Sure do. Symbios has come down to my place and re-labeled my controlor, > and until they do, it will remain a NCR810. No, what I meant was, that NCR SCSI cards (the name I use myself for all NCR/Symbios 53c8xx based cards) are not that similar, if you look at them in sufficient detail ... Sure, there are the original NCR brand cards, but they are only a small fraction of all "NCR SCSI" cards installed. (I guess most are from ASUS, with NCR/Symbios second, and companies using the 53c875 for their high end (and other vendors' chips for non-Ultra cards) like Tekram following.) > > In fact, there are several independently developed BIOS > > versions offered with the various brands of NCR chip, > > and even my (2.5 year old) ASUS SP3G lets you specify > > an additional power on delay ... > > I have a ASUS 3P3G too, and had to lengthen the delay for the 4 drives > I put on the internal SCSI bus. Yes, my point was that this is possible by choosing the appropriate delay in the BIOS ... > > > Quatum drives are known to go on a holiday after some continuous use. > > > Grand Prix drives are particularly bad. In fact, I think the Atlas is the > > > only respectible Quantum drive. > > > > How about the quality of the Atlas II and the Viking ? > > I don't really understand, why they offer two 7200RPM > > drives, again. Reminds me of the Atlas/Grand Prix ... > > The writing is on the wall for the Atlas II, now that the Atlas III is > available. I've seen the specs of the Atlas III, and they look very convincing (near Cheetah performance at 7200RPM and thus less noisy and running cooler), but I thought they were only available much later. Can you really buy an Atlas III today ??? Regards, STefan From owner-freebsd-hackers Wed Jul 9 11:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28966 for hackers-outgoing; Wed, 9 Jul 1997 11:22:00 -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 LAA28961 for ; Wed, 9 Jul 1997 11:21:56 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA23219; Wed, 9 Jul 1997 11:23:12 -0700 (PDT) Message-Id: <199707091823.LAA23219@implode.root.com> To: Raul Zighelboim cc: "'hackers@freefall.freebsd.org'" Subject: Re: There must be something really wrong with 2.2.2-release... In-reply-to: Your message of "Wed, 09 Jul 1997 09:35:18 CDT." From: David Greenman Reply-To: dg@root.com Date: Wed, 09 Jul 1997 11:23:11 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >BTW- I just checked one t=of the low-profile systems. > running inetd/sendmail and one telnetd session (+ the kernel) >and I had some 16Megs of cache used. > I killed inetd/sendmail, so only the kernel was sunning (and my >telnetd) and swapinfo still reported 30% of 48Megs cache in use... "cache" memory is memory that is being used to cache files and will not be affected by killing off processes. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Jul 9 12:00:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA01142 for hackers-outgoing; Wed, 9 Jul 1997 12:00:38 -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 MAA01135; Wed, 9 Jul 1997 12:00:26 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wm1tm-0005mq-00; Wed, 9 Jul 1997 11:55:34 -0700 Date: Wed, 9 Jul 1997 11:55:34 -0700 (PDT) From: Tom Samplonius To: Stefan Esser cc: freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <19970709191136.54842@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Jul 1997, Stefan Esser wrote: > I've seen the specs of the Atlas III, and they look very > convincing (near Cheetah performance at 7200RPM and thus > less noisy and running cooler), but I thought they were > only available much later. > > Can you really buy an Atlas III today ??? Yes. When I talked to Globelle last, they had stock for the Atlas III, and the Cheetah. But I decided to go with the Barracuda 4LP (or 4XL) instead. Lower power disapation than the Atlas III too. > Regards, STefan > > From owner-freebsd-hackers Wed Jul 9 12:23:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02408 for hackers-outgoing; Wed, 9 Jul 1997 12:23:57 -0700 (PDT) Received: from bcarsde4.localhost (mailgate.nortel.ca [192.58.194.74]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02400 for ; Wed, 9 Jul 1997 12:23:50 -0700 (PDT) Message-Id: <199707091923.MAA02400@hub.freebsd.org> Received: from bcarsfbb.ott.bnr.ca (actually bcarsfbb.bnr.ca) by bcarsde4.localhost; Wed, 9 Jul 1997 15:14:08 -0400 Received: from bnr.ca by bcarsfbb.bnr.ca id <20498-0@bcarsfbb.bnr.ca>; Wed, 9 Jul 1997 15:16:59 -0400 Date: 09 Jul 1997 15:16 EDT To: hackers@FreeBSD.ORG From: "Andrew Atrens" Subject: Re: no SYSVSHM in GENERIC now.. Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does the X-server run any faster with MIT-SHM than without? If it runs faster then I would vote to keep the stuff in GENERIC. Andrew ( opinions mine, not Nortel's ) In message "no SYSVSHM in GENERIC now..", you write: > > Hmm, and why X work with GENERIC ? > > (it' s print messages on console, but work fine) > > Because it's not mandatory for the X server to support the MIT-SHM > extention. If you don't have it, it doesn't. > > Jordan > From owner-freebsd-hackers Wed Jul 9 13:49:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07771 for hackers-outgoing; Wed, 9 Jul 1997 13:49:54 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA07728 for ; Wed, 9 Jul 1997 13:49:21 -0700 (PDT) Received: (from bsdhack@localhost) by shadows.aeon.net (8.8.6/8.8.3) id XAA24685 for hackers@freebsd.org; Wed, 9 Jul 1997 23:48:40 +0300 (EET DST) From: mika ruohotie Message-Id: <199707092048.XAA24685@shadows.aeon.net> Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: <199707091702.MAA00264@dyson.iquest.net> from "John S. Dyson" at "Jul 9, 97 12:02:32 pm" To: hackers@freebsd.org Date: Wed, 9 Jul 1997 23:48:40 +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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > if I add options PQ_LARGECACHE to the kernel config file. > > something we with 512K cache should use or not? > If you have a 512K direct mapped cache, it is significantly direct mapped? uh, mine's pipeline burst, fx chipset, soon tx. (and 64 megs ram, i know not to use more) > John mickey From owner-freebsd-hackers Wed Jul 9 14:57:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA14424 for hackers-outgoing; Wed, 9 Jul 1997 14:57: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 OAA14419 for ; Wed, 9 Jul 1997 14:57:20 -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 OAA02466; Wed, 9 Jul 1997 14:55:12 -0700 (PDT) To: "Andrew Atrens" cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "09 Jul 1997 15:16:00 EDT." <199707091923.MAA02400@hub.freebsd.org> Date: Wed, 09 Jul 1997 14:55:12 -0700 Message-ID: <2462.868485312@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Does the X-server run any faster with MIT-SHM than without? Uh. I think you're fundamentally confused as to the nature of the MIT-SHM extention. :-) It's only used by a few extention lib calls which allow you to create shared pixmaps and such. Jordan From owner-freebsd-hackers Wed Jul 9 15:03:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14947 for hackers-outgoing; Wed, 9 Jul 1997 15:03:44 -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 PAA14942 for ; Wed, 9 Jul 1997 15:03:39 -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 PAA24433; Wed, 9 Jul 1997 15:02:45 -0700 (PDT) Message-Id: <199707092202.PAA24433@implode.root.com> To: "Andrew Atrens" cc: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "09 Jul 1997 15:16:00 EDT." <199707091923.MAA02400@hub.freebsd.org> From: David Greenman Reply-To: dg@root.com Date: Wed, 09 Jul 1997 15:02:45 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Does the X-server run any faster with MIT-SHM than without? >If it runs faster then I would vote to keep the stuff in GENERIC. It only runs faster for applications which use the MIT-SHM extension, which are _very_ few. I don't think anything in the standard X11 distribution uses it, for example. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Wed Jul 9 15:35:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16698 for hackers-outgoing; Wed, 9 Jul 1997 15:35:22 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16691 for ; Wed, 9 Jul 1997 15:35:14 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id RAA01099; Wed, 9 Jul 1997 17:34:31 -0500 (EST) From: "John S. Dyson" Message-Id: <199707092234.RAA01099@dyson.iquest.net> Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: <199707092048.XAA24685@shadows.aeon.net> from mika ruohotie at "Jul 9, 97 11:48:40 pm" To: bsdhack@shadows.aeon.net (mika ruohotie) Date: Wed, 9 Jul 1997 17:34:31 -0500 (EST) Cc: hackers@FreeBSD.ORG Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > > if I add options PQ_LARGECACHE to the kernel config file. > > > something we with 512K cache should use or not? > > If you have a 512K direct mapped cache, it is significantly > > direct mapped? uh, mine's pipeline burst, fx chipset, soon tx. > (and 64 megs ram, i know not to use more) > The FX chipset definitely supported directed mapped caching, it is likely/possible that TX does also. You'll probably see a perf increase under most circumstances. Actually, it manifests itself as userland CPU operations simply being a little quicker when running large programs. John From owner-freebsd-hackers Wed Jul 9 15:52:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA17605 for hackers-outgoing; Wed, 9 Jul 1997 15:52:24 -0700 (PDT) Received: from mailhub.cts.com (mailhub.cts.com [204.216.216.130]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA17600 for ; Wed, 9 Jul 1997 15:52:22 -0700 (PDT) Received: from crash.cts.com(really [192.188.72.17]) by mailhub.cts.com via smail with smtp id for ; Wed, 9 Jul 97 15:52:21 -0700 (PDT) (Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21) Received: by crash.cts.com (Smail3.1.29.1 #5) id m0wm5av-00009eC; Wed, 9 Jul 97 15:52 PDT Date: Wed, 9 Jul 1997 15:52:20 -0700 (PDT) From: Tony Sterrett To: hackers@FreeBSD.ORG Subject: gcc 2.7.2.2 and FreeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi I've just installed FreeBSD 2.2.2 and I would like to install gcc 2.7.2.2 but its looking for a lib gnumalloc is this known by some other name. I can't find it. Thank for any help sorry for the stupid question. Tony Sterrett From owner-freebsd-hackers Thu Jul 10 00:08:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA11489 for hackers-outgoing; Thu, 10 Jul 1997 00:08:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA11460 for ; Thu, 10 Jul 1997 00:08:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA27017; Thu, 10 Jul 1997 16:59:26 +1000 Date: Thu, 10 Jul 1997 16:59:26 +1000 From: Bruce Evans Message-Id: <199707100659.QAA27017@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, mango@staff.communique.net Subject: RE: kern.maxvnodes and systat -v Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Is there a way I can increase the # of Kbytes fro buffers ? The NBUF option gives the number of buffers, and the amount of space for buffers is limited to (nbuf + 8) * 4K (less if buffers run out before buffer space). Bruce From owner-freebsd-hackers Thu Jul 10 00:34:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12565 for hackers-outgoing; Thu, 10 Jul 1997 00:34:29 -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 AAA12556 for ; Thu, 10 Jul 1997 00:34:23 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22836 for hackers@FreeBSD.ORG; Thu, 10 Jul 1997 09:34:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA00371; Thu, 10 Jul 1997 09:22:21 +0200 (MET DST) Message-ID: <19970710092221.JN34121@uriah.heep.sax.de> Date: Thu, 10 Jul 1997 09:22:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. References: <199707091923.MAA02400@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: <199707091923.MAA02400@hub.freebsd.org>; from Andrew Atrens on Jul 9, 1997 15:16:00 -0500 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrew Atrens wrote: > Does the X-server run any faster with MIT-SHM than without? No, it doesn't. The only thing is that it disables the MIT-SHM extension if no SYSVSHM is available in the kernel (it catches SIGSYS, and attempts to issue a shmget() call). MIT-SHM is an extension that must be explicitly used by the clients, and AFAIK only few clients actually use it. It is not to be confused with a local transport via shared memory (which doesn't exist in any XFree86 server, and to the best of my knowledge, neither in the Xig server). -- 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 Thu Jul 10 00:35:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12679 for hackers-outgoing; Thu, 10 Jul 1997 00:35:40 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12649 for ; Thu, 10 Jul 1997 00:35:10 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id LAA22764; (8.8.2-MVC-141196/vak/1.9) Thu, 10 Jul 1997 11:35:10 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id LAA06769; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA18081 (5.65/IDA-simtel for hackers@freebsd.org); Thu, 10 Jul 1997 13:27:08 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Thu, 10 Jul 97 13:27:08 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: question about kernel sources Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk in kernel sources files encounter next declaretion int (*func) __P((...)) ^^^^^^^^^^ what is this ? --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Thu Jul 10 01:24:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14774 for hackers-outgoing; Thu, 10 Jul 1997 01:24:43 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA14769 for ; Thu, 10 Jul 1997 01:24:41 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id BAA19365 for ; Thu, 10 Jul 1997 01:23:44 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id LAA20026; Thu, 10 Jul 1997 11:18:36 +0300 (EEST) Date: Thu, 10 Jul 1997 11:18:23 +0300 (EEST) From: Narvi To: mika ruohotie cc: hackers@FreeBSD.ORG Subject: Re: PQ_LARGECACHE and page colouring In-Reply-To: <199707092048.XAA24685@shadows.aeon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 9 Jul 1997, mika ruohotie wrote: > > > > if I add options PQ_LARGECACHE to the kernel config file. > > > something we with 512K cache should use or not? > > If you have a 512K direct mapped cache, it is significantly > > direct mapped? uh, mine's pipeline burst, fx chipset, soon tx. > (and 64 megs ram, i know not to use more) I have about the same (asus fx motherboard + 512K pipline burst cache in the form of a coast module). I don't know if it is direct-mapped or not - there is no documentation I can get my hands on. But it does help. Sander There is no love, no good, no happiness and no future - all these are just illusions. > > > John > > > mickey > From owner-freebsd-hackers Thu Jul 10 01:51:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15689 for hackers-outgoing; Thu, 10 Jul 1997 01:51:02 -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 BAA15679 for ; Thu, 10 Jul 1997 01:50:56 -0700 (PDT) Received: (qmail 17870 invoked by uid 1000); 10 Jul 1997 08:51:07 -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: Thu, 10 Jul 1997 01:51:07 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I will get it down one day... On RELENG_2_2 as of today, the following bomb in ``make world'': mkdep -f .depend -a /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c /usr/src/2.2/src/usr.bin/xinstall/xinstall.c cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function `flags_to_string': /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: `UF_NOUNLINK' undeclared (first use this function) ... ===> sbin/fsck cc -O -W -c /usr/src/2.2/src/sbin/fsck/dir.c In file included from /usr/src/2.2/src/sbin/fsck/dir.c:48: /usr/src/2.2/src/sbin/fsck/fsck.h:62: parse error before `ufs_daddr_t' /usr/src/2.2/src/sbin/fsck/fsck.h:62: warning: no semicolon at end of struct or union ... ===> lkm/syscons/fade cc -O -DLKM -I/usr/src/2.2/src/lkm/syscons/fade/.. -I/usr/src/2.2/src/lkm/syscons/fade/../../../sys -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/2.2/src/lkm/syscons/fade/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -c /usr/src/2.2/src/lkm/syscons/fade/fade_saver.c ld -r -o tmp.o fade_saver.o symorder -c symb.tmp tmp.o symorder: 1 symbol not found: _fade_saver_mod *** Error code 1 (continuing) From owner-freebsd-hackers Thu Jul 10 01:51:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA15693 for hackers-outgoing; Thu, 10 Jul 1997 01:51:02 -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 BAA15680 for ; Thu, 10 Jul 1997 01:50:57 -0700 (PDT) Received: (qmail 17873 invoked by uid 1000); 10 Jul 1997 08:51:07 -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: Thu, 10 Jul 1997 01:51:07 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: FreeBSD-Hackers@freebsd.org Subject: Make World Explodes Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk RELENG_2_2, as of tonightdoes the following naughty things: mkdep -f .depend -a /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c /usr/src/2.2/src/usr.bin/xinstall/xinstall.c cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function `flags_to_string': /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: `UF_NOUNLINK' undeclared (first use this function) ... ===> sbin/fsck cc -O -W -c /usr/src/2.2/src/sbin/fsck/dir.c In file included from /usr/src/2.2/src/sbin/fsck/dir.c:48: /usr/src/2.2/src/sbin/fsck/fsck.h:62: parse error before `ufs_daddr_t' /usr/src/2.2/src/sbin/fsck/fsck.h:62: warning: no semicolon at end of struct or union ... This repeats in many, many files in this directory, as well as fsdb, quotacheck. ===> sbin/i386/mount_msdos cc -O -D_NEW_VFSCONF -I/usr/src/2.2/src/sbin/i386/mount_msdos/../../mount -c /usr/src/2.2/src/sbin/i386/mount_msdos/mount_msdos.c In file included from /usr/src/2.2/src/sbin/i386/mount_msdos/mount_msdos.c:40: /usr/include/msdosfs/msdosfsmount.h:62: field `pm_bpb' has incomplete type /usr/include/msdosfs/msdosfsmount.h:83: field `pm_export' has incomplete type ... ===> lkm/syscons/blank cc -O -DLKM -I/usr/src/2.2/src/lkm/syscons/blank/.. -I/usr/src/2.2/src/lkm/syscons/blank/../../../sys -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/2.2/src/lkm/syscons/blank/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -c /usr/src/2.2/src/lkm/syscons/blank/blank_saver.c ld -r -o tmp.o blank_saver.o symorder -c symb.tmp tmp.o symorder: 1 symbol not found: _blank_saver_mod *** Error code 1 (continuing) ... This also appears in daemon, fade, green, snake, star. Any suggestions are welcome. Simon From owner-freebsd-hackers Thu Jul 10 02:07:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA16438 for hackers-outgoing; Thu, 10 Jul 1997 02:07:29 -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 CAA16427 for ; Thu, 10 Jul 1997 02:07:22 -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 LAA16682; Thu, 10 Jul 1997 11:07:34 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id LAA11913; Thu, 10 Jul 1997 11:10:11 +0200 (MEST) Message-ID: <19970710111010.22787@gil.physik.rwth-aachen.de> Date: Thu, 10 Jul 1997 11:10:10 +0200 From: Christoph Kukulies To: Tony Sterrett Cc: hackers@FreeBSD.ORG Subject: Re: gcc 2.7.2.2 and FreeBSD References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: ; from Tony Sterrett on Wed, Jul 09, 1997 at 03:52:20PM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Jul 09, 1997 at 03:52:20PM -0700, Tony Sterrett wrote: > Hi I've just installed FreeBSD 2.2.2 and I would like to install > gcc 2.7.2.2 but its looking for a lib gnumalloc is this known by > some other name. I can't find it. Thank for any help sorry for the It can be found in 2.2.2-RELEASE/compat1.x and goes to /usr/lib/compat/libgnumalloc.so.1.1 > stupid question. > Tony Sterrett -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Thu Jul 10 02:36:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17800 for hackers-outgoing; Thu, 10 Jul 1997 02:36:29 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA17778 for ; Thu, 10 Jul 1997 02:36:24 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id KAA05398; Thu, 10 Jul 1997 10:26:45 +0200 From: Luigi Rizzo Message-Id: <199707100826.KAA05398@labinfo.iet.unipi.it> Subject: Re: no SYSVSHM in GENERIC now.. To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 10 Jul 1997 10:26:44 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <19970710092221.JN34121@uriah.heep.sax.de> from "J Wunsch" at Jul 10, 97 09:22:02 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > As Andrew Atrens wrote: > > > Does the X-server run any faster with MIT-SHM than without? > > No, it doesn't. The only thing is that it disables the MIT-SHM > extension if no SYSVSHM is available in the kernel (it catches SIGSYS, > and attempts to issue a shmget() call). > > MIT-SHM is an extension that must be explicitly used by the clients, > and AFAIK only few clients actually use it. It is not to be confused "tv" and friends seem to run a bit faster with MITSHM since they probably save one copy. Of course it is much faster to let the frame grabber dump data straight to the video card. Cheers Luigi From owner-freebsd-hackers Thu Jul 10 02:37:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA17913 for hackers-outgoing; Thu, 10 Jul 1997 02:37:21 -0700 (PDT) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA17905 for ; Thu, 10 Jul 1997 02:37:15 -0700 (PDT) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.5/8.8.5) with ESMTP id LAA24510; Thu, 10 Jul 1997 11:37:01 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.6/8.8.5) id LAA21219; Thu, 10 Jul 1997 11:37:00 +0200 (CEST) To: Simon Shapiro Cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: none References: From: Thomas Gellekum Date: 10 Jul 1997 11:36:58 +0200 In-Reply-To: Simon Shapiro's message of Thu, 10 Jul 1997 01:51:07 -0700 (PDT) Message-ID: <87vi2jjlj9.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 11 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro writes: > I will get it down one day... > > On RELENG_2_2 as of today, the following bomb in ``make world'': Try `make includes' before `make world'. I have no idea if `make world' actually gets through afterwards, I noticed this only this morning and will find out when I get home. tg From owner-freebsd-hackers Thu Jul 10 02:58:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA21711 for hackers-outgoing; Thu, 10 Jul 1997 02:58:26 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA21705 for ; Thu, 10 Jul 1997 02:58: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 CAA28309; Thu, 10 Jul 1997 02:59:34 -0700 (PDT) Message-Id: <199707100959.CAA28309@implode.root.com> To: Simon Shapiro cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Make World Explodes In-reply-to: Your message of "Thu, 10 Jul 1997 01:51:07 PDT." From: David Greenman Reply-To: dg@root.com Date: Thu, 10 Jul 1997 02:59:34 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >RELENG_2_2, as of tonightdoes the following naughty things: > >mkdep -f .depend -a >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c >/usr/src/2.2/src/usr.bin/xinstall/xinstall.c >cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function >`flags_to_string': >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: >`UF_NOUNLINK' undeclared (first use this function) You must not read your FreeBSD email. This same bug report has been answered at least three times now. "cd /usr/src; make includes" before the "make world". -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Jul 10 06:32:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02188 for hackers-outgoing; Thu, 10 Jul 1997 06:32:24 -0700 (PDT) Received: from mailbox.uq.edu.au (zzshocki.slip.cc.uq.edu.au [130.102.221.173]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02175 for ; Thu, 10 Jul 1997 06:32:14 -0700 (PDT) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by mailbox.uq.edu.au (8.8.6/8.6.12) with ESMTP id XAA00441 for ; Thu, 10 Jul 1997 23:35:46 +1000 (EST) Message-Id: <199707101335.XAA00441@mailbox.uq.edu.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: The Linux emulator & weird Linux mmap semantics Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Jul 1997 23:35:46 +1000 From: Stephen Hocking Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been messing about with the Linux emulator, to add support for the kinds of manipulation involving mmaping sound devices that the OSS sound drivers support. A test program compiled natively works fine, but after hacking away at the Linux emulator to get it to recognize the various ioctls that OSS supports (get caps, mmaping, getospace) I am not getting any joy. The linux app (yes, it is quake if you must know) does not produce any sound, but thinks that it's doing fine. Has anyone else come across this? Stephen From owner-freebsd-hackers Thu Jul 10 06:46:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA02757 for hackers-outgoing; Thu, 10 Jul 1997 06:46:33 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02751 for ; Thu, 10 Jul 1997 06:46:31 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id JAA25923; Sun, 22 Jun 1997 09:54:43 GMT Date: Sun, 22 Jun 1997 09:54:43 +0000 (GMT) From: BRiGHTMN To: Stephen Hocking cc: hackers@FreeBSD.ORG Subject: Re: The Linux emulator & weird Linux mmap semantics In-Reply-To: <199707101335.XAA00441@mailbox.uq.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've been messing about with the Linux emulator, to add support for the kinds > of manipulation involving mmaping sound devices that the OSS sound drivers > support. A test program compiled natively works fine, but after hacking away > at the Linux emulator to get it to recognize the various ioctls that OSS > supports (get caps, mmaping, getospace) I am not getting any joy. The linux > app (yes, it is quake if you must know) does not produce any sound, but thinks > that it's doing fine. Has anyone else come across this? someone told me they were able to get sound in quake already (OSS), but i haven't been able to do it. if you are successful that would be great. Alfred Perlstein perlsta@sunyit.edu From owner-freebsd-hackers Thu Jul 10 07:48:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA05403 for hackers-outgoing; Thu, 10 Jul 1997 07:48:09 -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 HAA05395 for ; Thu, 10 Jul 1997 07:48:07 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id KAA27117; Thu, 10 Jul 1997 10:48:34 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id KAA21825; Thu, 10 Jul 1997 10:48:49 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Thu, 10 Jul 1997 10:48:48 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org To: Igor cc: hackers@FreeBSD.ORG Subject: Re: question about kernel sources -- __P() In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Jul 1997, Igor wrote: > in kernel sources files encounter next declaretion > > int (*func) __P((...)) > ^^^^^^^^^^ > what is this ? grep -Ra '#define __P' /usr/include/* returns a number of net/ppp_defs.h:#define __P(x) x net/ppp_defs.h:#define __P(x) () Vi'ing the file shows that the former is used in ISO C, but the latter in non-ISO. Reading stddef.h, it includes sys/cdefs.h. Reading sys/cdefs.h, it gives an even better hint. It's purpose is to change ANSI prototypes, ie. int function (int, int, string *); to K&R declarations, int function (); It's functionality is only marginally useful. All future compilers will handle ANSI prototypes, but in theory, it is sometimes useful to make the system header files work in retro-mode... It's usefulness in the kernel is even more questionable... -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Thu Jul 10 09:18:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA09571 for hackers-outgoing; Thu, 10 Jul 1997 09:18:43 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA09562 for ; Thu, 10 Jul 1997 09:18:39 -0700 (PDT) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id MAA08783; Thu, 10 Jul 1997 12:15:05 -0400 (EDT) Date: Thu, 10 Jul 1997 12:27:22 -0400 (EDT) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: hackers list FreeBSD cc: ari.suutari@ps.carel.fi Subject: ipfw rules processing order when DIVERTing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I'm a bit unsure about the order in which ipfw rules get processed in relation to a DIVERT rule that calls natd(8). Note the last few sentences from this excerpt from the natd(8) man page: /sbin/ipfw -f flush /sbin/ipfw add divert 6668 all from any to any via ed0 /sbin/ipfw add pass all from any to any The second line depends on your interface and assumes that you've updated /etc/services as above. If you specify real firewall rules, ---> it's best to specify line 2 at the start of the script so that natd ---> sees all packets before they are dropped by the firewall. The fire- ---> wall rules will be run again on each packet after translation by ---> natd, minus any divert rules. If I take this as literally as I can, I interpret it as follows * Rules before divert rule processed * Divert rule ships all packets not dropped by above rules to natd for address translation * Packets return from natd and are then subjected to ALL rules, except this time divert rule is skipped This is somewhat counter-intuitive to me. If this how it works, what is the reason for this design, since, as I think about it, there must be a performance penalty to this approach (multiple passes of rules). I had expected it to work like this: * Rules before divert rule processed * Divert rule ships all packets not dropped by above rules to natd for address translation * Packets return from natd and remaining rules after divert rule are processed What is the real story? Thanks very much, --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Thu Jul 10 09:25:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10030 for hackers-outgoing; Thu, 10 Jul 1997 09:25:30 -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 JAA10025 for ; Thu, 10 Jul 1997 09:25:26 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wmLxH-0006Mc-00; Thu, 10 Jul 1997 09:20:31 -0700 Date: Thu, 10 Jul 1997 09:20:31 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: FreeBSD-Hackers@freebsd.org Subject: Re: Make World Explodes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Jul 1997, Simon Shapiro wrote: > RELENG_2_2, as of tonightdoes the following naughty things: > > mkdep -f .depend -a > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > /usr/src/2.2/src/usr.bin/xinstall/xinstall.c > cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function > `flags_to_string': > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > `UF_NOUNLINK' undeclared (first use this function) > > ... Do a "make includes" first to get the include files up to date. Tom From owner-freebsd-hackers Thu Jul 10 09:31:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10277 for hackers-outgoing; Thu, 10 Jul 1997 09:31: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 JAA10271 for ; Thu, 10 Jul 1997 09:31:42 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wmM7n-0000zd-00; Thu, 10 Jul 1997 10:31:23 -0600 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: no SYSVSHM in GENERIC now.. Cc: hackers@freebsd.org In-reply-to: Your message of "Thu, 10 Jul 1997 09:22:21 +0200." <19970710092221.JN34121@uriah.heep.sax.de> References: <19970710092221.JN34121@uriah.heep.sax.de> <199707091923.MAA02400@hub.freebsd.org> Date: Thu, 10 Jul 1997 10:31:22 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970710092221.JN34121@uriah.heep.sax.de> J Wunsch writes: : MIT-SHM is an extension that must be explicitly used by the clients, : and AFAIK only few clients actually use it. Yes. That is true. However, the ones that do use it are in the "cool" category: mpeg_play and friends. So I have the option enabled on all the machines that I have that run X. Don't know if that makes sense for the whole world or GENERIC, but it makes sense for me. Warner From owner-freebsd-hackers Thu Jul 10 09:32:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10367 for hackers-outgoing; Thu, 10 Jul 1997 09:32:16 -0700 (PDT) Received: from mail.id.net (mail.id.net [199.125.1.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10359 for ; Thu, 10 Jul 1997 09:32:11 -0700 (PDT) Received: from shell.id.net (shell.id.net [199.125.2.8]) by mail.id.net (8.8.6/8.8.6) with ESMTP id MAA12408 for ; Thu, 10 Jul 1997 12:32:17 -0400 (EDT) From: Robert Shady Received: (from rls@localhost) by shell.id.net (8.8.5/8.7.3) id MAA16653 for freebsd-hackers@freebsd.org; Thu, 10 Jul 1997 12:32:16 -0400 (EDT) Message-Id: <199707101632.MAA16653@shell.id.net> Subject: Sig 11 errors... To: freebsd-hackers@freebsd.org Date: Thu, 10 Jul 1997 12:32:16 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry to bring this up again, but I've been having a hell of a time with my Win95 machine crashing all the time, getting corrupted data, etc. Just by coincendance, I happen to install FreeBSD 2.2.2 on it to test something else out, and noticed I was getting a large number of core dumped - exit signal 11 messages.. I remember sometime back Jordan saying something about these possibly being related to having external cache memory installed on the motherboard... Have we narrowed this down to be the cause? What is the effects of running a P200 with 128MB RAM w/o a COAST module? -- Rob === _/_/_/_/_/ _/_/_/_/ _/_/ _/ _/_/_/_/_/ _/_/_/_/_/ _/ _/ _/ _/_/_/ _/ _/ _/ _/_/_/_/ _/ _/_/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/_/ _/ Innovative Data Services Serving South-Eastern Michigan Internet Service Provider / Hardware Sales / Consulting Services Voice: (810)855-0404 / Fax: (810)855-3268 / Web: http://www.id.net From owner-freebsd-hackers Thu Jul 10 09:42:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10957 for hackers-outgoing; Thu, 10 Jul 1997 09:42:55 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA10948; Thu, 10 Jul 1997 09:42:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA23301; Thu, 10 Jul 1997 09:37:38 -0700 From: Terry Lambert Message-Id: <199707101637.JAA23301@phaeton.artisoft.com> Subject: Re: sd0 timed out while idle To: se@freebsd.org (Stefan Esser) Date: Thu, 10 Jul 1997 09:37:38 -0700 (MST) Cc: tom@sdf.com, terry@lambert.org, costa@inner.cortx.com, freebsd-hackers@freebsd.org In-Reply-To: <19970709191136.54842@mi.uni-koeln.de> from "Stefan Esser" at Jul 9, 97 07:11:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In case anyone was wondering: the original drive problems that provoked this thread were thermal shutdown problems. He has been running the machine with an extra fan for the drive, and the problem has not recurred. FYI: it was a Quantum drive... it would have been obvious from that that the problem was thermal. 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 Thu Jul 10 09:49:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA11314 for hackers-outgoing; Thu, 10 Jul 1997 09:49:18 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA11302 for ; Thu, 10 Jul 1997 09:49:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA23317; Thu, 10 Jul 1997 09:42:02 -0700 From: Terry Lambert Message-Id: <199707101642.JAA23317@phaeton.artisoft.com> Subject: Re: question about kernel sources To: igor@blik.samara.su (Igor) Date: Thu, 10 Jul 1997 09:42:01 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: from "Igor" at Jul 10, 97 01:27:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > in kernel sources files encounter next declaretion > > int (*func) __P((...)) > ^^^^^^^^^^ > what is this ? It is bogus. The "..." is for "0 or more arguments as represented in a varradic function declaration". The reason it is bogus is that there must be at least one real argument to serve as an "anchor" for the varargs.h varradic argument handling macros. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 10 10:34:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13679 for hackers-outgoing; Thu, 10 Jul 1997 10:34:15 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13670 for ; Thu, 10 Jul 1997 10:34:12 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA26183; Sun, 22 Jun 1997 13:42:42 GMT Date: Sun, 22 Jun 1997 13:42:42 +0000 (GMT) From: BRiGHTMN To: Charles Owens cc: hackers list FreeBSD , ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk it works like so: first matched = action if you want anything firewalled out put it before it hits natd /sbin/ipfw -f flush /sbin/ipfw add 100 deny ip from evil.place.org to any /sbin/ipfw add 200 divert 6668 all from any to any via ed0 /sbin/ipfw add 300 pass all from any to any the numbers are the order that way if you decide to change anything you can: /sbin/ipfw delete 200 to get rid of the natd... if you want you can take a look at my natd configuration files i'm going to post them on my webpage: www.cs.sunyit.edu/~perlsta it should be up later tonight... > Hi all, > > I'm a bit unsure about the order in which ipfw rules get processed in > relation to a DIVERT rule that calls natd(8). Note the last few sentences > from this excerpt from the natd(8) man page: > > /sbin/ipfw -f flush > /sbin/ipfw add divert 6668 all from any to any via ed0 > /sbin/ipfw add pass all from any to any > The second line depends on your interface and assumes that you've > updated /etc/services as above. If you specify real firewall rules, > ---> it's best to specify line 2 at the start of the script so that natd > ---> sees all packets before they are dropped by the firewall. The fire- > ---> wall rules will be run again on each packet after translation by > ---> natd, minus any divert rules. > > If I take this as literally as I can, I interpret it as follows > > * Rules before divert rule processed > * Divert rule ships all packets not dropped by above rules > to natd for address translation > * Packets return from natd and are then subjected to ALL rules, > except this time divert rule is skipped > > This is somewhat counter-intuitive to me. If this how it works, what is > the reason for this design, since, as I think about it, there must be a > performance penalty to this approach (multiple passes of rules). I had > expected it to work like this: > > * Rules before divert rule processed > * Divert rule ships all packets not dropped by above rules > to natd for address translation > * Packets return from natd and remaining rules after divert rule > are processed > > What is the real story? > > Thanks very much, > --- > ------------------------------------------------------------------------- > Charles N. Owens Email: owensc@enc.edu > http://www.enc.edu/~owensc > Network & Systems Administrator > Information Technology Services "Outside of a dog, a book is a man's > Eastern Nazarene College best friend. Inside of a dog it's > too dark to read." - Groucho Marx > ------------------------------------------------------------------------- > > From owner-freebsd-hackers Thu Jul 10 10:36:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13862 for hackers-outgoing; Thu, 10 Jul 1997 10:36:24 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13852 for ; Thu, 10 Jul 1997 10:36:18 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA26187; Sun, 22 Jun 1997 13:44:54 GMT Date: Sun, 22 Jun 1997 13:44:54 +0000 (GMT) From: BRiGHTMN To: Robert Shady cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Sig 11 errors... In-Reply-To: <199707101632.MAA16653@shell.id.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Sorry to bring this up again, but I've been having a hell of a time with > my Win95 machine crashing all the time, getting corrupted data, etc. > > Just by coincendance, I happen to install FreeBSD 2.2.2 on it to test > something else out, and noticed I was getting a large number of > core dumped - exit signal 11 messages.. I remember sometime back > Jordan saying something about these possibly being related to having > external cache memory installed on the motherboard... Have we narrowed > this down to be the cause? What is the effects of running a P200 > with 128MB RAM w/o a COAST module? i was getting these problems until i told my bios to put a wait state for the ram, but i P200 shouldn't need that... or it could :) try some other ram. From owner-freebsd-hackers Thu Jul 10 10:38:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14055 for hackers-outgoing; Thu, 10 Jul 1997 10:38:54 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14030 for ; Thu, 10 Jul 1997 10:38:34 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id NAA26194; Sun, 22 Jun 1997 13:46:00 GMT Date: Sun, 22 Jun 1997 13:46:00 +0000 (GMT) From: BRiGHTMN To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: sd0 timed out while idle In-Reply-To: <199707101637.JAA23301@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > In case anyone was wondering: the original drive problems that > provoked this thread were thermal shutdown problems. He has > been running the machine with an extra fan for the drive, and > the problem has not recurred. > > FYI: it was a Quantum drive... it would have been obvious from > that that the problem was thermal. 8-). umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use bad idea? From owner-freebsd-hackers Thu Jul 10 12:51:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19821 for hackers-outgoing; Thu, 10 Jul 1997 12:51:49 -0700 (PDT) Received: from relay.linkdesign.com (nserv1.hlink.com.cy [194.42.131.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19803 for ; Thu, 10 Jul 1997 12:51:44 -0700 (PDT) Received: (from michael@localhost) by relay.linkdesign.com (8.8.5/8.8.2) id WAA05929; Thu, 10 Jul 1997 22:52:35 +0300 (EET DST) Message-ID: <19970710225234.08925@linkdesign.com> Date: Thu, 10 Jul 1997 22:52:34 +0300 From: Michael Bielicki To: hackers@freebsd.org Subject: why can't Iinstall 2.2.2 onAdaptec 6360 controller ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, I can't seem to be able to install 2.2.2-RELEASE on a 486 with the Adaptec 6360 on board controller. Sometimes it saays it cant use the swap partition, sometimes it says bad directory, sometimes it simply reboots. I tried quantum fireball and ibm dcas disks. Same stuff. Anybody ever heard of this ?? -- Michael Bielicki Link Design International Ltd. Buisnetco Telecommunications Ltd. 65 Cliff Road, Tramore, Office 23, 13, Iras Street Co. Waterford, Ireland Nicosia 1061, Rep. of Cyprus Tel: +353-51-390880 Tel: +357 9 631 305 Fax: +353 51 386921 http://www.linkdesign.com Fax: +357 2 367 266 From owner-freebsd-hackers Thu Jul 10 13:31:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA27289 for hackers-outgoing; Thu, 10 Jul 1997 13:31:04 -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 NAA27284 for ; Thu, 10 Jul 1997 13:30:59 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wmPr5-0001Wt-00; Thu, 10 Jul 1997 14:30:23 -0600 To: Michael Bielicki Subject: Re: why can't Iinstall 2.2.2 onAdaptec 6360 controller ? Cc: hackers@freebsd.org In-reply-to: Your message of "Thu, 10 Jul 1997 22:52:34 +0300." <19970710225234.08925@linkdesign.com> References: <19970710225234.08925@linkdesign.com> Date: Thu, 10 Jul 1997 14:30:23 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970710225234.08925@linkdesign.com> Michael Bielicki writes: : I can't seem to be able to install 2.2.2-RELEASE on a 486 : with the Adaptec 6360 on board controller. Sometimes it saays : it cant use the swap partition, sometimes it says bad directory, sometimes : it simply reboots. I tried quantum fireball and ibm dcas disks. Same : stuff. : : Anybody ever heard of this ?? I've had mixed luck with the 6360 based boards. The driver is in a state of disrepair right now. However, I have had good luck with them from time to time. They are really fussy about jumper settings, and bus termination. Double check those items. Warner From owner-freebsd-hackers Thu Jul 10 13:38:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA27638 for hackers-outgoing; Thu, 10 Jul 1997 13:38: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 NAA27633 for ; Thu, 10 Jul 1997 13:38:08 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA23699; Thu, 10 Jul 1997 13:32:01 -0700 From: Terry Lambert Message-Id: <199707102032.NAA23699@phaeton.artisoft.com> Subject: Re: sd0 timed out while idle To: brightmn@a-v25.rh.sunyit.edu (BRiGHTMN) Date: Thu, 10 Jul 1997 13:32:01 -0700 (MST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "BRiGHTMN" at Jun 22, 97 01:46:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In case anyone was wondering: the original drive problems that > > provoked this thread were thermal shutdown problems. He has > > been running the machine with an extra fan for the drive, and > > the problem has not recurred. > > > > FYI: it was a Quantum drive... it would have been obvious from > > that that the problem was thermal. 8-). > > umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use > bad idea? They like ventilation, is all. PS: Why is it June 22nd at your house? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Jul 10 14:11:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA28956 for hackers-outgoing; Thu, 10 Jul 1997 14:11:03 -0700 (PDT) Received: from Blinky.HEMPAC.Net (Blinky.HEMPAC.Net [199.17.40.222]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA28946 for ; Thu, 10 Jul 1997 14:10:57 -0700 (PDT) Received: (from markh@localhost) by Blinky.HEMPAC.Net (8.8.5/8.8.5) id QAA02691; Thu, 10 Jul 1997 16:10:47 -0500 (CDT) From: Mark Holden Message-Id: <199707102110.QAA02691@Blinky.HEMPAC.Net> Subject: Re: sd0 timed out while idle To: freebsd-hackers@freebsd.org Date: Thu, 10 Jul 1997 16:10:46 -0500 (CDT) Cc: brightmn@a-v25.rh.sunyit.edu In-Reply-To: <199707102032.NAA23699@phaeton.artisoft.com> from "Terry Lambert" at Jul 10, 97 01:32:01 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use >> bad idea? > >They like ventilation, is all. Also, don't tighten the screws into the drive too hard, I've seen many Quantum drives that were "repaired" by simply loosening the screws. Seems that it's not too tough to warp the drive enough to cause problems. (No, the screws weren't contacting the PC board) All in all, the Quantums are good, reliable drives, just a bit touchy. One of my FreeBSD machines (a PPro 200) has a Quantum 3.8G, and it gets the best performance marks of the ones I've played with (mostly Western Dig.) -Mark Holden From owner-freebsd-hackers Thu Jul 10 15:05:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA01420 for hackers-outgoing; Thu, 10 Jul 1997 15:05:03 -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 PAA01402 for ; Thu, 10 Jul 1997 15:04:59 -0700 (PDT) Received: (from hasty@localhost) by rah.star-gate.com (8.8.5/8.8.5) id PAA02174 for hackers@freebsd.org; Thu, 10 Jul 1997 15:04:57 -0700 (PDT) Date: Thu, 10 Jul 1997 15:04:57 -0700 (PDT) From: Amancio Hasty Message-Id: <199707102204.PAA02174@rah.star-gate.com> To: hackers@freebsd.org Subject: scsi scanner software available Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I did a quick port of "sane" to freebsd . The patches were submitted back to the author. For the record , I have a UMAX S12 scsi scanner which was tested with sane-0.61. sane is at: http://www.azstarnet.com/~axplinux/sane/ Very excited about this port given that UMAX's Win95 package sucks. Have fun, Amancio From owner-freebsd-hackers Thu Jul 10 15:06:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA01516 for hackers-outgoing; Thu, 10 Jul 1997 15:06:42 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA01508 for ; Thu, 10 Jul 1997 15:06:37 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA08748; Thu, 10 Jul 1997 15:04:41 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma008746; Thu Jul 10 15:04:20 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id PAA03534; Thu, 10 Jul 1997 15:04:20 -0700 (PDT) From: Archie Cobbs Message-Id: <199707102204.PAA03534@bubba.whistle.com> Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: from Charles Owens at "Jul 10, 97 12:27:22 pm" To: owensc@enc.edu (Charles Owens) Date: Thu, 10 Jul 1997 15:04:19 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If I take this as literally as I can, I interpret it as follows > > * Rules before divert rule processed > * Divert rule ships all packets not dropped by above rules > to natd for address translation > * Packets return from natd and are then subjected to ALL rules, > except this time divert rule is skipped This is correct. > This is somewhat counter-intuitive to me. If this how it works, what is > the reason for this design, since, as I think about it, there must be a > performance penalty to this approach (multiple passes of rules). I had There are two reasons for this... 1. The new packet (post-diversion) may be different from the old packet (pre-diversion), so it should be checked again to insure that it doesn't avoid any rules that apply to it. 2. It's a lot easier to code this way :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jul 10 15:25:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA02163 for hackers-outgoing; Thu, 10 Jul 1997 15:25:27 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA02158 for ; Thu, 10 Jul 1997 15:25:23 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id SAA20751 for ; Thu, 10 Jul 1997 18:25:39 -0400 (EDT) Date: Thu, 10 Jul 1997 18:25:39 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: 2.2-RELENG vs. 2.2.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I asked in -questions and #freebsd but got no answer. Thought I would try here. Can 2.2-RELENG be assumed as stable as 2.2.2-RELEASE. (I am looking to upgrade from 2.2.1-RELEASE mostly to get rid of the libXt security holes.) -- David Cross From owner-freebsd-hackers Thu Jul 10 15:50:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA03127 for hackers-outgoing; Thu, 10 Jul 1997 15:50:44 -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 PAA03122 for ; Thu, 10 Jul 1997 15:50:38 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA27948; Thu, 10 Jul 1997 18:50:04 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Thu, 10 Jul 1997 18:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id PAA14058; Thu, 10 Jul 1997 15:07:34 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id PAA06181; Thu, 10 Jul 1997 15:16:14 -0400 (EDT) Date: Thu, 10 Jul 1997 15:16:14 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707101916.PAA06181@lakes.water.net> To: ponds!zeta.org.au!bde, ponds!i-Connect.Net!Shimon Subject: pertinent to my "daily panics" (was Re: Clists limited to 1024 bytes?) Cc: ponds!cisco.com!bmcgover, ponds!FreeBSD.ORG!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just saw the following in mail from Simon Shapiro : > > > >We experienced a lot of complex problems with SCSI transactions until we > > >bumped the sio interrupt bufferto double its size. While performance > > (on > > >the sio ports - we use them only for PPP) did not drop visibly, the > > strange > > >incidence of dropping biodone() calls virtually stopped. > > > > This probably just made a race less common. > > It would be interesting to actually solve this mystery; how does a buffer > overflow in the sio (under PPP) cause biodone to lose a completion. > We know, with very high degree of certainty, that we do not lose > interrupts, nor miss a call to scsi_done (which calls biodone, somehow). > It appears that from scsi_done() up things drop in this case. Not every > time. Nasty... > > Simon > This looks like it's in the area of my "daily panic" problem... Especially the part about "from scsi_done() up things..." Has anything more happened along this issue? Did anyone discover anything? - Dave Rivers - From owner-freebsd-hackers Thu Jul 10 16:00:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA03466 for hackers-outgoing; Thu, 10 Jul 1997 16:00:34 -0700 (PDT) Received: from laguna.arc.unm.edu (laguna.arc.unm.edu [198.59.173.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA03448; Thu, 10 Jul 1997 16:00:29 -0700 (PDT) Received: from pegasus.unm.edu (sdn-ts-058txfwoRP14.dialsprint.net [206.133.155.81]) by laguna.arc.unm.edu (8.7.3/8.7.3) with SMTP id RAA19738; Thu, 10 Jul 1997 17:00:26 -0600 (MDT) Message-Id: <3.0.1.32.19970710165919.006c30a4@arc.unm.edu> X-Sender: shawnhsu@arc.unm.edu X-Mailer: Windows Eudora Light Version 3.0.1 (32) Date: Thu, 10 Jul 1997 16:59:19 -0600 To: freebsd-hackers@FreeBSD.ORG From: "Xu, Xiang" Subject: FreeBSD Book Cc: freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi: Feel that our FreeBSD society need new good books. My name is Xiang Xu. I am an editor in a publishing company by the name of Bigi International Inc. Think many people here are willing to write or are writing books for the FreeBSD society. If you are interested in writing whole or some contents of a FreeBSD book (any topic about FreeBSD will be welcomed), please contact me(shawnhsu@arc.unm.edu). Thanks. Sincerely Xiang Xu (shawnhsu@arc.unm.edu) ================================= Xu, Xiang Bigi International USA Inc. email: shawnhsu@arc.unm.edu http://www.bigiintl.com Tel:(505)830-1443(O), (505)232-8223(H) FAX:(505)830-1448 2501, San Pedro Blvd., N.E. Suite 208 Albuquerque, NM 87110, U.S.A. From owner-freebsd-hackers Thu Jul 10 16:02:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA03570 for hackers-outgoing; Thu, 10 Jul 1997 16:02:43 -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 QAA03563 for ; Thu, 10 Jul 1997 16:02:37 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA02776; Thu, 10 Jul 1997 16:01:09 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd002772; Thu Jul 10 23:01:02 1997 Message-ID: <33C5690F.2C67412E@whistle.com> Date: Thu, 10 Jul 1997 15:58: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: Archie Cobbs CC: Charles Owens , freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing References: <199707102204.PAA03534@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: > > > If I take this as literally as I can, I interpret it as follows > > > > * Rules before divert rule processed > > * Divert rule ships all packets not dropped by above rules > > to natd for address translation > > * Packets return from natd and are then subjected to ALL rules, > > except this time divert rule is skipped > > This is correct. > > > This is somewhat counter-intuitive to me. If this how it works, what is > > the reason for this design, since, as I think about it, there must be a > > performance penalty to this approach (multiple passes of rules). I had > > There are two reasons for this... > > 1. The new packet (post-diversion) may be different from the old packet > (pre-diversion), so it should be checked again to insure that it > doesn't avoid any rules that apply to it. > > 2. It's a lot easier to code this way :-) > Just to be devil's advocate, ;-) I think it could start processing at the next higher number after the one it was diverted from.. in other words it could have an implicit 'skipto (N+1)' rule the 'divert' word to me suggests that it should come back to the same place it left from. :) From owner-freebsd-hackers Thu Jul 10 16:16:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA04263 for hackers-outgoing; Thu, 10 Jul 1997 16:16:46 -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 QAA04258 for ; Thu, 10 Jul 1997 16:16:41 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA12507; Fri, 11 Jul 1997 09:15:06 +1000 (EST) Date: Fri, 11 Jul 1997 09:15:05 +1000 (EST) From: "Daniel O'Callaghan" To: Charles Owens cc: hackers list FreeBSD , ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ipfw rules are parsed by rule number. You also need to remember that packets are subjected to ipfw scrutiny on their way IN and on their way OUT. Packets originating on the firewall machine are only seen going OUT, and packets arriving at the firewall machine are only seen coming IN. Forwarded packets are seen going IN and OUT. A rule 00100 pass icmp from any to any will see icmp packets going through the machine twice (look at 'ipfw -a list' and you'll see twice as many packets as you expect. To reduce confusion, you can specify the direction of the packet to be matched, e.g. 00200 pass icmp from any to any in When diverting packets, I always specify the direction, and often the interface. 00200 divert 1 tcp from any 80 to 1.2.3.4 in via de0 Of course, that only clarifies things for that rule, and the reinserted packet is still tested against all rules until a match is found. Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */ From owner-freebsd-hackers Thu Jul 10 16:32:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA04711 for hackers-outgoing; Thu, 10 Jul 1997 16:32:21 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA04704 for ; Thu, 10 Jul 1997 16:32:13 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA09364; Thu, 10 Jul 1997 16:30:13 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma009352; Thu Jul 10 16:29:50 1997 Received: (from archie@localhost) by bubba.whistle.com (8.8.5/8.6.12) id QAA04387; Thu, 10 Jul 1997 16:29:50 -0700 (PDT) From: Archie Cobbs Message-Id: <199707102329.QAA04387@bubba.whistle.com> Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: <33C5690F.2C67412E@whistle.com> from Julian Elischer at "Jul 10, 97 03:58:23 pm" To: julian@whistle.com (Julian Elischer) Date: Thu, 10 Jul 1997 16:29:50 -0700 (PDT) Cc: archie@whistle.com, owensc@enc.edu, freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > This is somewhat counter-intuitive to me. If this how it works, what is > > > the reason for this design, since, as I think about it, there must be a > > > performance penalty to this approach (multiple passes of rules). I had > > > > There are two reasons for this... > > > > 1. The new packet (post-diversion) may be different from the old packet > > (pre-diversion), so it should be checked again to insure that it > > doesn't avoid any rules that apply to it. > > > > 2. It's a lot easier to code this way :-) > > > Just to be devil's advocate, ;-) > I think it could start processing at the next higher number > after the one it was diverted from.. > in other words it could have an implicit 'skipto (N+1)' rule > > the 'divert' word to me suggests that it should come back to the same > place it left from. :) Yes! ``It could start processing at the next higher number.'' I agree with that :-) The problem is that when the packet returns to the kernel from user-land, that bit of state that says "this packet has already seen rules 1-2000 (or whatever)" is lost, and you can't retrieve it. The only way to do this would be for the user-land process to send back some additional info that says "skip to rule 2000". Doable, but .. not very pretty? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jul 10 17:17:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA06120 for hackers-outgoing; Thu, 10 Jul 1997 17:17: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 RAA06115 for ; Thu, 10 Jul 1997 17:17:19 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA05614; Thu, 10 Jul 1997 17:16:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd005612; Fri Jul 11 00:16:13 1997 Message-ID: <33C57AAB.42877E5C@whistle.com> Date: Thu, 10 Jul 1997 17:13:31 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Archie Cobbs CC: owensc@enc.edu, freebsd-hackers@FreeBSD.ORG, ari.suutari@ps.carel.fi Subject: RFC: IPFW-DIVERT change. WAS:[ipfw rules processing order..] References: <199707102329.QAA04387@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Archie Cobbs wrote: > > > > > This is somewhat counter-intuitive to me. If this how it works, what is > > > > the reason for this design, since, as I think about it, there must be a > > > > performance penalty to this approach (multiple passes of rules). I had > > > > > > There are two reasons for this... > > > > > > 1. The new packet (post-diversion) may be different from the old packet > > > (pre-diversion), so it should be checked again to insure that it > > > doesn't avoid any rules that apply to it. This is a legitimate reason I guess.. not this against what I have to say below: > > Just to be devil's advocate, ;-) > > I think it could start processing at the next higher number > > after the one it was diverted from.. > > in other words it could have an implicit 'skipto (N+1)' rule > > > > the 'divert' word to me suggests that it should come back to the same > > place it left from. :) > > Yes! ``It could start processing at the next higher number.'' > I agree with that :-) > > The problem is that when the packet returns to the kernel from > user-land, that bit of state that says "this packet has already > seen rules 1-2000 (or whatever)" is lost, and you can't retrieve > it. The only way to do this would be for the user-land process > to send back some additional info that says "skip to rule 2000". > > Doable, but .. not very pretty? the divert sockets at the moment return from recvfrom() with a sockaddr containing: 1/ the IP address of the interface the packet came in from, and 2/ the ipdivert port number. sendto() needs a sockaddr with 1/ the interface ip addr to say it came from, and 2/ the ipdivert socket to NOT send it to (for loop avoidance) we could change the semantics to be: instead of the divert port number (the process knows thin information anyway), the rule number from which the diversion occured. Also, on sendto() the port number could represent the rule number to restart processing from. in other words, if the number was 1000, processing would begin at 1001. this would allow a divert process to leave the same number there that it received, and to avoid loops in that way because the process ing would start at the NEXT rule. present programs probably just copy this number across, so I guess it would be a transparent change to most of them. does it leave us open to security holes that were blocked before? (see the reason archie gave above)? is this a real threat? can it be proven to (not be)/(be) a threat? I think this would be an easy change to make. what do the USERS think (divert users). (I'd make the change if it seemed reasonable to everyone) divert sockets are still in their infancy (some hope they will die) so it' still a possible change. of course it ties them closer to ipfw and makes it less likely that ipfilter could ever be made to work with them. julian > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com From owner-freebsd-hackers Thu Jul 10 17:48:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA07229 for hackers-outgoing; Thu, 10 Jul 1997 17:48:51 -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 RAA07224 for ; Thu, 10 Jul 1997 17:48:48 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id RAA02792; Thu, 10 Jul 1997 17:48:30 -0700 (PDT) Message-Id: <199707110048.RAA02792@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Warner Losh cc: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Thu, 10 Jul 1997 10:31:22 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Jul 1997 17:48:30 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As a matter of course, every FreeBSD system that I happen to use if it doesnt have SYSVHM and friends I just compile it in. Cheers, Amancio >From The Desk Of Warner Losh : > In message <19970710092221.JN34121@uriah.heep.sax.de> J Wunsch writes: > : MIT-SHM is an extension that must be explicitly used by the clients, > : and AFAIK only few clients actually use it. > > Yes. That is true. However, the ones that do use it are in the > "cool" category: mpeg_play and friends. > > So I have the option enabled on all the machines that I have that run > X. Don't know if that makes sense for the whole world or GENERIC, but > it makes sense for me. > > Warner From owner-freebsd-hackers Thu Jul 10 18:11:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA08008 for hackers-outgoing; Thu, 10 Jul 1997 18:11:43 -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 SAA08002 for ; Thu, 10 Jul 1997 18:11:38 -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 VAA20633 for ; Thu, 10 Jul 1997 21:11:35 -0400 (EDT) Message-Id: <199707110111.VAA20633@spoon.beta.com> To: hackers@freebsd.org Subject: Trigger for received PPP packets? Date: Thu, 10 Jul 1997 21:11:34 -0400 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I asked this question once before a week or so ago, and didn't get a great response about it, so I'll try it from a different angle. I'm playing with serial device X, for which the driver is in a prototype stage... Its working fine, except for receiving PPP packets. Basically the data is being stowed in the clists via the l_rint routine. The problem that I'm seeing is that a received packet is taking quite a long time (roughly 100 - 150ms) to get processed. A ping, for instance, on a 115200 serial link, takes about 347-380ms round trip. Using 16550s, it takes about 47-80ms round trip. Connecting the device to a 16550 yields fast throughput from board to 16550, but much slower from 16550 to the device (hence why I believe its the receive side). Is there anything that needs to be done in the receive code at some point (ie - end of packet, each character, etc) that needs to be done to speed this up? Thanks. -brian From owner-freebsd-hackers Thu Jul 10 18:53:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA09619 for hackers-outgoing; Thu, 10 Jul 1997 18:53:23 -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 SAA09614 for ; Thu, 10 Jul 1997 18:53:20 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id SAA03364 for ; Thu, 10 Jul 1997 18:53:22 -0700 (PDT) Message-Id: <199707110153.SAA03364@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 to: hackers@FreeBSD.ORG Subject: Re: no SYSVSHM in GENERIC now.. In-reply-to: Your message of "Thu, 10 Jul 1997 17:48:30 PDT." <199707110048.RAA02792@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Jul 1997 18:53:21 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In the mean time , out in the field: Subject: Pthread: Is there a better way? Date: 8 Jul 1997 01:09:30 GMT From: tsmurphy@cs.uiuc.edu (TERENCE MURPHY) Organization: University of Illinois at Urbana-Champaign Newsgroups: comp.unix.bsd.freebsd.misc I came across the man page for pthread, exuberant that the package came with the OS, and wrote a little program to test it, and worried when it didn't link. Then I read: > By default, libc_r is not built as part of a 'make world'. To build and > install, it type: > > cd /usr/src/lib/libc_r > > make depend && make all && make install I thought and then... > This assumes you have a full source tree below /usr/src and that you have > at least installed the header files in the way that 'make world' does. Ahhh!!! I seriously don't have the disk space the go out and download and compile the whole source tree. There's got to be a better way! Is there an alternative binary distribution which includes the threaded libc? Are there plans to put threads into the default system in the future? That makes sense to me. Seriously, I don't understand why it isn't already. Heck, if it's not included in the standard distribution, developers are less likely to try to depend on stuff which people aren't going to have. I also don't see why SYSVSHM isn't in the kernel by default. Otherwise, the kernel is totally usable on installation (even without a compile) For system-ish stuff (like threads and shared memory), IMHO, the system should provide that stuff without requiring a recompile. I'm a software engineer, not a system administrator!! FreeBSD follows this well (much better than the alternatives) but I think it can be improved. Thanks, Terry Murphy ------- Happy Reading, Amancio From owner-freebsd-hackers Thu Jul 10 20:17:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA12363 for hackers-outgoing; Thu, 10 Jul 1997 20:17:59 -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 UAA12350 for ; Thu, 10 Jul 1997 20:17:55 -0700 (PDT) Received: (qmail 7981 invoked by uid 1000); 11 Jul 1997 03:18:07 -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: Thu, 10 Jul 1997 20:18:07 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 10-Jul-97 you wrote: > > On Thu, 10 Jul 1997, Simon Shapiro wrote: > > > RELENG_2_2, as of tonightdoes the following naughty things: > > > > mkdep -f .depend -a > > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > > /usr/src/2.2/src/usr.bin/xinstall/xinstall.c > > cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In > function > > `flags_to_string': > > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > > `UF_NOUNLINK' undeclared (first use this function) > > > > ... > > Do a "make includes" first to get the include files up to date. I did. That is not it. Simon From owner-freebsd-hackers Thu Jul 10 20:18:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA12387 for hackers-outgoing; Thu, 10 Jul 1997 20:18: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 UAA12359 for ; Thu, 10 Jul 1997 20:17:58 -0700 (PDT) Received: (qmail 8004 invoked by uid 1000); 11 Jul 1997 03:18:09 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707100959.CAA28309@implode.root.com> Date: Thu, 10 Jul 1997 20:18:09 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 10-Jul-97 you wrote: > >RELENG_2_2, as of tonightdoes the following naughty things: > > > >mkdep -f .depend -a > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > >/usr/src/2.2/src/usr.bin/xinstall/xinstall.c > >cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function > >`flags_to_string': > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > >`UF_NOUNLINK' undeclared (first use this function) > > You must not read your FreeBSD email. This same bug report has been > answered at least three times now. "cd /usr/src; make includes" before > the "make world". I would like to apologize, but cannot do so. It still blows up. The same way. I will delete the entire source tree and try again. Simon From owner-freebsd-hackers Thu Jul 10 20:18:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA12397 for hackers-outgoing; Thu, 10 Jul 1997 20:18:06 -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 UAA12361 for ; Thu, 10 Jul 1997 20:17:59 -0700 (PDT) Received: (qmail 8003 invoked by uid 1000); 11 Jul 1997 03:18:09 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199707100959.CAA28309@implode.root.com> Date: Thu, 10 Jul 1997 20:18:09 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 10-Jul-97 you wrote: > >RELENG_2_2, as of tonightdoes the following naughty things: > > > >mkdep -f .depend -a > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > >/usr/src/2.2/src/usr.bin/xinstall/xinstall.c > >cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function > >`flags_to_string': > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > >`UF_NOUNLINK' undeclared (first use this function) > > You must not read your FreeBSD email. This same bug report has been > answered at least three times now. "cd /usr/src; make includes" before > the "make world". You must jump into conclusions :-) A. I read my mail. B. This does not always help. C. I ``make world'' at least twice a week, without any ``make includes''. D. If make includes is necessary and solves the problem, then it should be added to make world. Right? Anyway, it is running now and in few short hours I will be able to apologize with sincerity. Simon From owner-freebsd-hackers Thu Jul 10 20:23:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA12631 for hackers-outgoing; Thu, 10 Jul 1997 20:23:00 -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 UAA12626 for ; Thu, 10 Jul 1997 20:22:56 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wmWDY-0006mi-00; Thu, 10 Jul 1997 20:18:00 -0700 Date: Thu, 10 Jul 1997 20:17:59 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: FreeBSD-Hackers@freebsd.org Subject: Re: Make World Explodes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Jul 1997, Simon Shapiro wrote: > I did. That is not it. Hmm, I just did a "make world" a couple of days ago, and that's all I had to do. Is there is any chance your source tree is damaged. Try removing the files in /usr/sup, and re-running cvsup. cvsup will then check every file, rather than rely on the database in /usr/sup. Also, how is the DPT driver coming? > Simon Tom From owner-freebsd-hackers Thu Jul 10 20:52:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA13661 for hackers-outgoing; Thu, 10 Jul 1997 20:52:18 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA13656 for ; Thu, 10 Jul 1997 20:52:14 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id NAA32223; Fri, 11 Jul 1997 13:47:08 +1000 Date: Fri, 11 Jul 1997 13:47:08 +1000 From: Bruce Evans Message-Id: <199707110347.NAA32223@godzilla.zeta.org.au> To: hackers@FreeBSD.ORG, mcgovern@spoon.beta.com Subject: Re: Trigger for received PPP packets? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I asked this question once before a week or so ago, and didn't get a great >response about it, so I'll try it from a different angle. It's probably too technical for -hackers. >I'm playing with serial device X, for which the driver is in a prototype >stage... Its working fine, except for receiving PPP packets. Basically >the data is being stowed in the clists via the l_rint routine. The problem ppp doesn't use clists for input. >that I'm seeing is that a received packet is taking quite a long time >(roughly 100 - 150ms) to get processed. A ping, for instance, on a 115200 >serial link, takes about 347-380ms round trip. Apparently the driver is not delivering characters to ppp promptly. I guess it uses huge buffers and doesn't get interrupted for packet framing characters. >Using 16550s, it takes about >47-80ms round trip. Connecting the device to a 16550 yields fast throughput >from board to 16550, but much slower from 16550 to the device (hence why >I believe its the receive side). sio delivers characters to ppp within one fifo full time of receipt of a packet framing character. This gives a maximum additional latency at 115200 bps of 14 character times (1.2 msec) for 16550's and 1 character time (87 usec) for 8250's and 16450's. On a local line with 16550's, ping latency should be about 16 msec for cslip, 17 msec for pppd -bsdcomp, and 8 msec for pppd with the default of bsdcomp enabled and used. Bruce From owner-freebsd-hackers Thu Jul 10 21:06:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA14018 for hackers-outgoing; Thu, 10 Jul 1997 21:06:01 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA14012 for ; Thu, 10 Jul 1997 21:05:55 -0700 (PDT) Received: (qmail 10138 invoked by uid 1000); 11 Jul 1997 04:06:07 -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: Thu, 10 Jul 1997 21:06:07 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Jul-97 you wrote: > > On Thu, 10 Jul 1997, Simon Shapiro wrote: > > > I did. That is not it. > > Hmm, I just did a "make world" a couple of days ago, and that's all I > had to do. > > Is there is any chance your source tree is damaged. Try removing the > files in /usr/sup, and re-running cvsup. cvsup will then check every > file, rather than rely on the database in /usr/sup. DON'T TELL ME THAT :-( I do not mind re-creating the checked out version but re-doing cvsup is a long, painful process. > Also, how is the DPT driver coming? You can track the gory details in the SCSI mailing list; It runs now on every motherboard that the DPT can live on. It appears to be sensitive to some timing problems on the PCI bus. As long as good hardware is used andthe networking code is not interacting (appears unrelated), it is very stable. We use it routinely on about a dozen machines, build releases, backup to two tapes simultaneouly (three angered the SCSI layer in earlier version), and run up to 1048 instances of dd reading and writing to disk. Performance with RAID-5 is a constant 8.9MB/Sec writing/reading mix. RAID-0 is closer to 18-20MB/Sec. The only other problem is that if you use reboot instead of shutdown (or maybe shutdown itself), the kernel does not wait for the ``ALLOW MEDIA REMOVAL'' to complete before resetting the CPU. DPT uses this SCSI command to flush and invalidate the caches. Not waiting for it to finish can leave ``few'' buffers unwritten. ``Few'' can equal 64MB, which is unpeasant. It takes about 21-28.5 seconds to flush the caches written by newfs on a 4096MB file system. Simon From owner-freebsd-hackers Thu Jul 10 21:57:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA16210 for hackers-outgoing; Thu, 10 Jul 1997 21:57:08 -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 VAA16205 for ; Thu, 10 Jul 1997 21:57:05 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wmXgg-0006q8-00; Thu, 10 Jul 1997 21:52:10 -0700 Date: Thu, 10 Jul 1997 21:52:10 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: FreeBSD-Hackers@freebsd.org Subject: Re: Make World Explodes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Jul 1997, Simon Shapiro wrote: > > Is there is any chance your source tree is damaged? Try removing the > > files in /usr/sup, and re-running cvsup. cvsup will then check every > > file, rather than rely on the database in /usr/sup. > > DON'T TELL ME THAT :-( I do not mind re-creating the checked out version > but re-doing cvsup is a long, painful process. Errr... it isn't that bad. It isn't like you are removing every file in /usr/src or anything. It forces the client to check checksums for all files that you have with the server (actually they are probably md5 digests). It only re-transfers the files that are known to different. I did this on a 486, and it only added a half hour or so to cvsup. No big deal, but it did find some files that were old, but cvsup wasn't trasnfering because the /usr/sup database said they were up to date. Crashes during a cvsup can cause this problem. > reading and writing to disk. Performance with RAID-5 is a constant > 8.9MB/Sec writing/reading mix. RAID-0 is closer to 18-20MB/Sec. 8.9MB/s for RAID-5? Is this is a controller limitation or a drive limitation? Could the controller do better with faster drives, or more channels and drives to spread io over? > The only other problem is that if you use reboot instead of shutdown (or > maybe shutdown itself), the kernel does not wait for the ``ALLOW MEDIA > REMOVAL'' to complete before resetting the CPU. DPT uses this SCSI command > to flush and invalidate the caches. Not waiting for it to finish can leave > ``few'' buffers unwritten. ``Few'' can equal 64MB, which is unpeasant. > It takes about 21-28.5 seconds to flush the caches written by newfs on a > 4096MB file system. Not nice. > Simon > > Tom From owner-freebsd-hackers Thu Jul 10 22:22:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17246 for hackers-outgoing; Thu, 10 Jul 1997 22:22:59 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17217 for ; Thu, 10 Jul 1997 22:22:40 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA22603; Fri, 11 Jul 1997 14:50:42 +0930 (CST) From: Michael Smith Message-Id: <199707110520.OAA22603@genesis.atrad.adelaide.edu.au> Subject: Re: sd0 timed out while idle In-Reply-To: from BRiGHTMN at "Jun 22, 97 01:46:00 pm" To: brightmn@a-v25.rh.sunyit.edu (BRiGHTMN) Date: Fri, 11 Jul 1997 14:50:42 +0930 (CST) Cc: terry@lambert.org, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk BRiGHTMN stands accused of saying: > > umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use > bad idea? Ugh. The Bigfoots are _crap_. Or, more to the point, they're designed for the low end of the Windows market. If you want a 6G disk, look at the new high-end IDE quantums, or the 6G Seagate. You may even find that buying two 3G disks is close to cost-effective, in which case the IBM DAQA-33240 is an excellent deal. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 10 22:33:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17578 for hackers-outgoing; Thu, 10 Jul 1997 22:33:45 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17573 for ; Thu, 10 Jul 1997 22:33:41 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA22667; Fri, 11 Jul 1997 15:03:28 +0930 (CST) From: Michael Smith Message-Id: <199707110533.PAA22667@genesis.atrad.adelaide.edu.au> Subject: Re: why can't Iinstall 2.2.2 onAdaptec 6360 controller ? In-Reply-To: <19970710225234.08925@linkdesign.com> from Michael Bielicki at "Jul 10, 97 10:52:34 pm" To: michael@linkdesign.com (Michael Bielicki) Date: Fri, 11 Jul 1997 15:03:28 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Michael Bielicki stands accused of saying: > Hi Folks, > I can't seem to be able to install 2.2.2-RELEASE on a 486 > with the Adaptec 6360 on board controller. Sometimes it saays > it cant use the swap partition, sometimes it says bad directory, sometimes > it simply reboots. I tried quantum fireball and ibm dcas disks. Same > stuff. If it's actuall a 6360 (uses the 'aic' driver), then you should not expect to be able to work well with this system. The 6360 is not a spectacular chip, and the 'aic' driver isn't the greatest either. The problems you are seeing aren't surprising. > Michael Bielicki -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 10 22:35:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA17674 for hackers-outgoing; Thu, 10 Jul 1997 22:35:23 -0700 (PDT) Received: from mailserv.tversu.ac.ru (vadim@mailserv.tversu.ac.ru [193.233.128.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA17669 for ; Thu, 10 Jul 1997 22:35:18 -0700 (PDT) Received: (from vadim@localhost) by mailserv.tversu.ac.ru (8.8.5/8.8.5) id JAA05386; Fri, 11 Jul 1997 09:35:44 +0400 (MSD) Message-ID: <19970711093543.62687@tversu.ac.ru> Date: Fri, 11 Jul 1997 09:35:43 +0400 From: Vadim Kolontsov To: freebsd-hackers@freebsd.org Subject: /etc/init.d/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Morning, how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like scheme in FreeBSD? I think it will be useful. And I am ready to do it. Best regards Vadim -------------------------------------------------------------------------- Vadim Kolontsov Security/Programmer/Admin Tver Regional Internet Center +7-(0822)-365743 (temporary) From owner-freebsd-hackers Thu Jul 10 22:46:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA18057 for hackers-outgoing; Thu, 10 Jul 1997 22:46:07 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA18049 for ; Thu, 10 Jul 1997 22:46:04 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.6/8.8.5) id WAA28594; Thu, 10 Jul 1997 22:46:12 -0700 (PDT) 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: Thu, 10 Jul 1997 22:46:11 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Jul-97 you wrote: ... > /usr/sup database said they were up to date. > Crashes during a cvsup can cause this problem. Here, it is actually /usr/local/etc/cvsup. I thought you were thinking about the archive itself. > > reading and writing to disk. Performance with RAID-5 is a constant > > 8.9MB/Sec writing/reading mix. RAID-0 is closer to 18-20MB/Sec. > > 8.9MB/s for RAID-5? Is this is a controller limitation or a drive > limitation? Could the controller do better with faster drives, or more > channels and drives to spread io over? This is really an algorithm limitation. there are two methods for upating the ``parity'' in a WRITE. One involved reading from evry drive, XORing with the data and writing the data and the XOR back out. this gets progressively worse with size. The better way is to read the old data, XOR with the new, take this bitmask, XOR it with the old parity and write the new result. It still takes a read-XOR-write-compute-read-XOR-write per write operation. Since it involves (exactly) two drives, it is only so fast. This is the cost of trying to beat the cost associated with RAID-1 and obtain READ performance in the process. The solution is to take a group of RAID-5 arrays, treating each as a single ``disk'' and build a RAID-0 array form these. You can do it easily with CCD. IMPORTANT: (I am, again, inviting an argument here, plus ``my system is better that your junk'' comments :-) put as many busses on the DPT as you can (3 is a good number (the maximum too ;-) Then put as few disks on each bus as possible (I say 4-6 with wide-ultra, and doing file system stuff). Let us say you have three busses and 10 disks: Bus 0: 0, 1, 2, 3 Bus 1: 0, 1, 2, 3 Bus 2: 0, 1, 2, 3, 4 If we call Tarket zer on bus 0 0-0 and disk 4 on bus 2 2-4, specify the rais array to dptmgr, in EXACTLY this order: 0-0 1-0 2-0 0-1 1-1 2-1 0-2 1-2 2-2 0-3 1-3 2-3 Designate 2-4 as a Hot Spare. If the drives are 4GB, you will have a 36GB ``disk'' on 0-0 and 2-4 will be invisible to the O/S. Remember! If an array element (say 1-3) fails, 2-4 will not only go into service, but will actually BECOME 1-3 (if in a StorageWorks/DPT cabinet). Now go partition this and see, that for normal Unix installation you have a strange limit: How many partitions does disklabel allow you to have per drive? The rest of this should move to -SCSI ML? Simon From owner-freebsd-hackers Thu Jul 10 22:47:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA18129 for hackers-outgoing; Thu, 10 Jul 1997 22:47: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 WAA18121 for ; Thu, 10 Jul 1997 22:47:22 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id PAA22745; Fri, 11 Jul 1997 15:17:05 +0930 (CST) From: Michael Smith Message-Id: <199707110547.PAA22745@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2-RELENG vs. 2.2.2-RELEASE In-Reply-To: from "David E. Cross" at "Jul 10, 97 06:25:39 pm" To: dec@phoenix.its.rpi.edu (David E. Cross) Date: Fri, 11 Jul 1997 15:17:05 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk David E. Cross stands accused of saying: > I asked in -questions and #freebsd but got no answer. Thought I would try > here. > > Can 2.2-RELENG be assumed as stable as 2.2.2-RELEASE. Generally, more so. > (I am looking to upgrade from 2.2.1-RELEASE mostly to get rid of the libXt > security holes.) Huh? Apart from the fact that AFAIK the Xt holes were fixed ages ago, libXt isn't a part of FreeBSD. It's a part of XFree86, which is a separate distribution. You can upgrade this without having to change the base system at all. > David Cross -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Jul 10 23:11:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA19228 for hackers-outgoing; Thu, 10 Jul 1997 23:11:44 -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 XAA19221 for ; Thu, 10 Jul 1997 23:11:38 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wmYqo-0006sh-00; Thu, 10 Jul 1997 23:06:42 -0700 Date: Thu, 10 Jul 1997 23:06:42 -0700 (PDT) From: Tom Samplonius To: Michael Smith cc: BRiGHTMN , freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <199707110520.OAA22603@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Jul 1997, Michael Smith wrote: > BRiGHTMN stands accused of saying: > > > > umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use > > bad idea? > > Ugh. The Bigfoots are _crap_. Or, more to the point, they're > designed for the low end of the Windows market. Not only that, they are SLOW. Very low rotational speed (3500 rpm I believe!) gives you poor sequentional io, and a really big disk platter (5 1/4 profile) gives you poor random access. > If you want a 6G disk, look at the new high-end IDE quantums, or the > 6G Seagate. You may even find that buying two 3G disks is close to > cost-effective, in which case the IBM DAQA-33240 is an excellent deal. Can't comment. Ever heard of a 7200rpm IDE disk? > -- > ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ > ]] Genesis Software genesis@gsoft.com.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control. (ph) +61-8-8267-3493 [[ > ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ > > Tom From owner-freebsd-hackers Thu Jul 10 23:51:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA21312 for hackers-outgoing; Thu, 10 Jul 1997 23:51:33 -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 XAA21304 for ; Thu, 10 Jul 1997 23:51:29 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA07365; Fri, 11 Jul 1997 08:51:11 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA03360; Fri, 11 Jul 1997 08:46:14 +0200 (MET DST) Message-ID: <19970711084614.RJ19398@uriah.heep.sax.de> Date: Fri, 11 Jul 1997 08:46:14 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: vadim@tversu.ac.ru (Vadim Kolontsov) Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> 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: <19970711093543.62687@tversu.ac.ru>; from Vadim Kolontsov on Jul 11, 1997 09:35:43 +0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Vadim Kolontsov wrote: > how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like > scheme in FreeBSD? I think it will be useful. And I am ready to do it. The usefulness of the SysV run-level scenario is among the points that usually causes the most contradictionary discussions on these lists. A number of people find them useful, and another number of people (at least as large as the first group) think they are a totally crappy idea from the beginning. I don't really belong to either group myself, but the number of disagreeing, different, and inconsistent SysV versions probably made me lean toward the second group in the end as well. Sorry, i can't tell you for sure whether the real&true multi-user level on your version of SysV is level 2, 3, or 4. You gotta find out yourself. :-) Also, i have yet to see one SysV implementation that gets all the state transitions right. It's probably impossible to do, i've seen many implementations that call startup scripts when going down from level 3 to 1, or that call stop scripts when going up from level S to 1. This is probably enough proof of misconcept. ;-) Well, seriously, we've got a good number of rc.something scripts already done. It seems David Nugent is finally committing the idea of a shutdown mechanism built into init(8), something that was still missing badly by now. After this has been done, and leaving out the naming differences, also considering that our ports already install initialization scripts in /usr/local/etc/rc.d/, the only remaining difference between the BSD and the SysV approach (as it is actually used by the various SysV incarnations) is that BSD only knows about single-user vs. multi-user run-levels, while SysV often provides a crippled multi-user level without networking. Now, think about when you've actually been using this level at all, ever, on your SysVs... and it will become very apparent that it _seems_ to be a nice feature, but is _actually_ a totally unused misfeature. -- 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 Fri Jul 11 00:02:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA21741 for hackers-outgoing; Fri, 11 Jul 1997 00:02:03 -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 AAA21736 for ; Fri, 11 Jul 1997 00:02:00 -0700 (PDT) Received: (qmail 24568 invoked by uid 1000); 11 Jul 1997 07:02:12 -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: <87vi2jjlj9.fsf@ghpc6.ihf.rwth-aachen.de> Date: Fri, 11 Jul 1997 00:02:12 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Thomas Gellekum Subject: Re: none Cc: FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Thomas Gellekum; On 10-Jul-97 you wrote: > Simon Shapiro writes: > > > I will get it down one day... > > > > On RELENG_2_2 as of today, the following bomb in ``make world'': > > Try `make includes' before `make world'. I have no idea if `make > world' actually gets through afterwards, I noticed this only this > morning and will find out when I get home. Thanx! Turns out it was nothing rm -rf could not have helped. Had to clean both source tree and the sup ``database''. Apologies for not doing so in the first place and not trusting that the source tree is perfect. Simon From owner-freebsd-hackers Fri Jul 11 00:28:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23015 for hackers-outgoing; Fri, 11 Jul 1997 00:28:35 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23005 for ; Fri, 11 Jul 1997 00:28:30 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id JAA14620; Fri, 11 Jul 1997 09:15:36 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.6/8.8.6) id JAA27044; Fri, 11 Jul 1997 09:07:53 +0200 (CEST) Message-ID: <19970711090753.01372@gtn.com> Date: Fri, 11 Jul 1997 09:07:53 +0200 From: Andreas Klemm To: stronghold@www.ukweb.com Cc: hackers@FreeBSD.org Subject: Stronghold evaluation, Problems with decryption of passwords Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi ! Some days ago I got an evaluation copy of stronghold for our company. I tried to evaluate your great product but trapped into some problems regarding decryption of passwords. So for example I couldn't login into the administration server. With which crypt algorithm was your Stronghold FreeBSD binary created ? I currently use the src/secure distrib from internat.FreeBSD.org. >From the README (usr/src/secure/README.FreeBSD): This code is legal for distribution outside the US and Canada. It was created from code legally exported and from code written entirely outside USA/Canada. This code is made available to the world through the courtesy of the kind folks at the CSIR's Program for Network Design and Security. Without them I would not have a well-connected machine and the high enough bandwidth to support a world accessible FTP site. Thanks for any pointers Andreas /// -- Andreas Klemm | klemm.gtn.com - powered by Symmetric MultiProcessor FreeBSD http://www.freebsd.org/~fsmp/SMP/SMP.html http://www.freebsd.org/~fsmp/SMP/benches.html From owner-freebsd-hackers Fri Jul 11 01:06:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA24720 for hackers-outgoing; Fri, 11 Jul 1997 01:06:29 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24715 for ; Fri, 11 Jul 1997 01:06:24 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA23264; Fri, 11 Jul 1997 17:35:15 +0930 (CST) From: Michael Smith Message-Id: <199707110805.RAA23264@genesis.atrad.adelaide.edu.au> Subject: Re: Make World Explodes In-Reply-To: from Simon Shapiro at "Jul 10, 97 08:18:09 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Fri, 11 Jul 1997 17:35:15 +0930 (CST) Cc: dg@root.com, FreeBSD-Hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro stands accused of saying: [Charset iso-8859-8 unsupported, filtering to ASCII...] > > Hi David Greenman; On 10-Jul-97 you wrote: > > >RELENG_2_2, as of tonightdoes the following naughty things: > > > > > >mkdep -f .depend -a > > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > > >/usr/src/2.2/src/usr.bin/xinstall/xinstall.c > > >cc -O -c /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c > > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c: In function > > >`flags_to_string': > > >/usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > > >`UF_NOUNLINK' undeclared (first use this function) > > > > You must not read your FreeBSD email. This same bug report has been > > answered at least three times now. "cd /usr/src; make includes" before > > the "make world". > > I would like to apologize, but cannot do so. It still blows up. The same > way. I will delete the entire source tree and try again. Ensure your entire tree is at the correct revision (in your case "cd /usr/src; cvs update -Pd -rRELENG_2_2"), then "make includes; make world" _will_ work, unless you are doing something _very_ unconventional. > Simon -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 11 01:09:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA24929 for hackers-outgoing; Fri, 11 Jul 1997 01:09:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA24915 for ; Fri, 11 Jul 1997 01:09:15 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA23281; Fri, 11 Jul 1997 17:38:46 +0930 (CST) From: Michael Smith Message-Id: <199707110808.RAA23281@genesis.atrad.adelaide.edu.au> Subject: Re: Make World Explodes In-Reply-To: from Simon Shapiro at "Jul 10, 97 08:18:09 pm" To: Shimon@i-Connect.Net (Simon Shapiro) Date: Fri, 11 Jul 1997 17:38:46 +0930 (CST) Cc: dg@root.com, FreeBSD-Hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro stands accused of saying: > > You must jump into conclusions :-) Not often. > A. I read my mail. > B. This does not always help. > C. I ``make world'' at least twice a week, without any ``make includes''. > D. If make includes is necessary and solves the problem, then it should > be added to make world. Right? The answer to D. would already be known to you if A. was true, as I have explained at _least_ twice in public mail on this thread exactly why this is a one-off gotcha. Bruce has even clarified the situation with extreme precision in yet another mail. To summarise : - 'make includes' _is_ run as part of 'make world'. - the include files have to be installed with something, namely the 'install' program. - the sources for 'install' inherit a module from 'ls' which knows about some new file flags - the header which defines these flags cannot be installed until install is built which can't be built until the header is installed So you have to help it out by presuming your 'install' is up to it and running the 'make includes' by hand. > Simon -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 11 01:11:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25109 for hackers-outgoing; Fri, 11 Jul 1997 01:11:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA25100 for ; Fri, 11 Jul 1997 01:11:05 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA23301; Fri, 11 Jul 1997 17:40:51 +0930 (CST) From: Michael Smith Message-Id: <199707110810.RAA23301@genesis.atrad.adelaide.edu.au> Subject: Re: Trigger for received PPP packets? In-Reply-To: <199707110347.NAA32223@godzilla.zeta.org.au> from Bruce Evans at "Jul 11, 97 01:47:08 pm" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 11 Jul 1997 17:40:50 +0930 (CST) Cc: hackers@FreeBSD.ORG, mcgovern@spoon.beta.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > > >that I'm seeing is that a received packet is taking quite a long time > >(roughly 100 - 150ms) to get processed. A ping, for instance, on a 115200 > >serial link, takes about 347-380ms round trip. > > Apparently the driver is not delivering characters to ppp promptly. I > guess it uses huge buffers and doesn't get interrupted for packet framing > characters. Just to clarify for Brian; this is what the 'hotchar' stuff in the sio driver is all about. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 11 01:25:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25813 for hackers-outgoing; Fri, 11 Jul 1997 01:25:49 -0700 (PDT) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA25777 for ; Fri, 11 Jul 1997 01:25:07 -0700 (PDT) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.6/8.6.9) with ESMTP id KAA07742 for ; Fri, 11 Jul 1997 10:23:29 GMT Message-Id: <199707111023.KAA07742@peedub.gj.org> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: /etc/init.d/ Reply-To: Gary Jennejohn In-reply-to: Your message of "Fri, 11 Jul 1997 08:46:14 +0200." <19970711084614.RJ19398@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Jul 1997 10:23:29 +0000 From: Gary Jennejohn Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch writes: >As Vadim Kolontsov wrote: > >> how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like >> scheme in FreeBSD? I think it will be useful. And I am ready to do it. [snip] >difference between the BSD and the SysV approach (as it is actually >used by the various SysV incarnations) is that BSD only knows about >single-user vs. multi-user run-levels, while SysV often provides a >crippled multi-user level without networking. Now, think about when >you've actually been using this level at all, ever, on your SysVs... >and it will become very apparent that it _seems_ to be a nice feature, >but is _actually_ a totally unused misfeature. > I run a SVR4 box here at home, and the only useful run-level options (IMHO) it offers involve NFS services. When I need NFS I just switch to that run-level and all the services are started. When I'm done using NFS I just switch to a lower level and the NFS stuff is removed. But a box without networking is pretty useless and I've never run the box in that configuration. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com From owner-freebsd-hackers Fri Jul 11 01:34:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA26318 for hackers-outgoing; Fri, 11 Jul 1997 01:34:03 -0700 (PDT) Received: from circe.bonn-online.com (root@circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA26279 for ; Fri, 11 Jul 1997 01:33:54 -0700 (PDT) Received: from rain (portC6.bonn-online.com [195.52.214.77]) by circe.bonn-online.com (8.8.5/8.8.5) with SMTP id KAA31033; Fri, 11 Jul 1997 10:33:04 +0200 Message-ID: <33C5EFC1.41C67EA6@bonn-online.com> Date: Fri, 11 Jul 1997 10:33:05 +0200 From: Sebastian Lederer X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2-961014-SNAP i386) MIME-Version: 1.0 To: Joerg Wunsch CC: freebsd-hackers@FreeBSD.ORG, Vadim Kolontsov Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > Well, seriously, we've got a good number of rc.something scripts > already done. It seems David Nugent is finally committing the idea of > a shutdown mechanism built into init(8), something that was still > missing badly by now. After this has been done, and leaving out the > naming differences, also considering that our ports already install > initialization scripts in /usr/local/etc/rc.d/, the only remaining > difference between the BSD and the SysV approach (as it is actually > used by the various SysV incarnations) is that BSD only knows about > single-user vs. multi-user run-levels, while SysV often provides a > crippled multi-user level without networking. Now, think about when > you've actually been using this level at all, ever, on your SysVs... > and it will become very apparent that it _seems_ to be a nice feature, > but is _actually_ a totally unused misfeature. > Let me first say that I am very pleased with the direction the FreeBSD /etc/rc model is moving. It provides the possibility for additional software packages to install startup scripts without fiddling with existing files, but it does not have the (mostly useless) overkill complexity of the SystemV model. But I would suggest that the /usr/local/etc/rc.d directory is moved to /etc/rc.d. Imagine a server machine running the apache httpd, which is started from /usr/local/etc/rc.d, and several diskless clients, nfs-mounting their filesystems (including /usr/local) from the server. The /etc/rc script on the clients will then see the apache startup script in /usr/local/etc/rc.d. So you will have a httpd process running on each client, except if you modify the /etc/rc script on each client, which is not excactly what you want. Moving the rc.d directory to /etc would avoid this problem, since /etc is (usually) private to a single machine. Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com From owner-freebsd-hackers Fri Jul 11 02:07:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27853 for hackers-outgoing; Fri, 11 Jul 1997 02:07:52 -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 CAA27846 for ; Fri, 11 Jul 1997 02:07:48 -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 LAA09667; Fri, 11 Jul 1997 11:07:56 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.8.5/8.6.9) id LAA16639; Fri, 11 Jul 1997 11:11:01 +0200 (MEST) Message-ID: <19970711111101.30909@gil.physik.rwth-aachen.de> Date: Fri, 11 Jul 1997 11:11:01 +0200 From: Christoph Kukulies To: Sebastian Lederer Cc: Joerg Wunsch , freebsd-hackers@FreeBSD.ORG, Vadim Kolontsov Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75e In-Reply-To: <33C5EFC1.41C67EA6@bonn-online.com>; from Sebastian Lederer on Fri, Jul 11, 1997 at 10:33:05AM +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 11, 1997 at 10:33:05AM +0200, Sebastian Lederer wrote: > J Wunsch wrote: > > > > Well, seriously, we've got a good number of rc.something scripts > > already done. It seems David Nugent is finally committing the idea of [...] > > Let me first say that I am very pleased with the direction the > FreeBSD /etc/rc model is moving. It provides the possibility > for additional software packages to install startup scripts without > fiddling with existing files, but it does not have the > (mostly useless) overkill complexity of the SystemV model. > > But I would suggest that the /usr/local/etc/rc.d directory is > moved to /etc/rc.d. > > Imagine a server machine running the apache httpd, which is > started from /usr/local/etc/rc.d, and several diskless clients, > nfs-mounting their filesystems (including /usr/local) from the This is exactly what was annoying me here some time ago when I installed apache on a NIS/NFS server machine. Suddenly all clients were running httpds and I had to disable manually on all clients to leave out /usr/local/etc/rc.d in $local_startup (/etc/rc.conf) I agree with moving it to /etc/rc.d unless a better FreeBSD diskless/NFS concept is being developed from ground up. Actually there ain't any diskless strategy right now, afaik. > server. The /etc/rc script on the clients will then see the > apache startup script in /usr/local/etc/rc.d. So you will > have a httpd process running on each client, except if you > modify the /etc/rc script on each client, which is > not excactly what you want. > > Moving the rc.d directory to /etc would avoid this problem, > since /etc is (usually) private to a single machine. > > Best regards, > Sebastian Lederer > > -- > Sebastian Lederer > lederer@bonn-online.com -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Fri Jul 11 02:29:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA28569 for hackers-outgoing; Fri, 11 Jul 1997 02:29:23 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA28564 for ; Fri, 11 Jul 1997 02:29:20 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA23645; Fri, 11 Jul 1997 18:58:12 +0930 (CST) From: Michael Smith Message-Id: <199707110928.SAA23645@genesis.atrad.adelaide.edu.au> Subject: Re: /etc/init.d/ In-Reply-To: <19970711111101.30909@gil.physik.rwth-aachen.de> from Christoph Kukulies at "Jul 11, 97 11:11:01 am" To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Date: Fri, 11 Jul 1997 18:58:11 +0930 (CST) Cc: lederer@bonn-online.com, joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, vadim@tversu.ac.ru X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Christoph Kukulies stands accused of saying: > > I agree with moving it to /etc/rc.d unless a better FreeBSD > diskless/NFS concept is being developed from ground up. Actually > there ain't any diskless strategy right now, afaik. /etc is stupid, given that the drive is to move _away_ from this. If it has to go anywhere, /var is the place. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 11 02:55:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA29507 for hackers-outgoing; Fri, 11 Jul 1997 02:55:33 -0700 (PDT) Received: from relay1.cit.ru (relay1.cit.ru [193.125.82.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA29497 for ; Fri, 11 Jul 1997 02:54:52 -0700 (PDT) Received: from free.tula.su by relay1.cit.ru with UUCP id NAA02186; (8.8.2-MVC-141196/vak/1.9) Fri, 11 Jul 1997 13:50:20 +0400 (MSD) Received: from blik.UUCP by free.tula.su with UUCP id NAA04395; (8.8.2-MVC-141196/vak/1.9) 9b Received: by blik.samara.su id AA04242 (5.65/IDA-simtel for hackers@freebsd.org); Fri, 11 Jul 1997 15:45:03 +0500 To: hackers@freebsd.org Message-Id: Organization: Center of Information Technology From: "Igor" Date: Fri, 11 Jul 97 15:45:02 +0500 X-Mailer: BML [UNIX Beauty Mail v.1.39] Subject: Where I can read about kernel hacking Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Where I can read about 'FreeBSD kernel hacking' ? --- igor@blik.samara.su (Igor) From owner-freebsd-hackers Fri Jul 11 04:21:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA02412 for hackers-outgoing; Fri, 11 Jul 1997 04:21:29 -0700 (PDT) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA02407 for ; Fri, 11 Jul 1997 04:21:24 -0700 (PDT) Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.8.5/1.2.3) with ESMTP id FAA15070 for ; Fri, 11 Jul 1997 05:21:21 -0600 (MDT) Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.8.5/8.8.5) id FAA01337 for freebsd-hackers@freebsd.org; Fri, 11 Jul 1997 05:20:40 -0600 (MDT) Date: Fri, 11 Jul 1997 05:20:40 -0600 (MDT) From: Alan Lundin Message-Id: <199707111120.FAA01337@lundin.abq.nm.us.> In-Reply-To: Christoph Kukulies "Re: /etc/init.d/" (Jul 11, 11:11am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: freebsd-hackers@freebsd.org Subject: Re: /etc/init.d/ Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 11, 11:11am, Christoph Kukulies wrote: > Subject: Re: /etc/init.d/ > > On Fri, Jul 11, 1997 at 10:33:05AM +0200, Sebastian Lederer wrote: > > J Wunsch wrote: > > > > > > Well, seriously, we've got a good number of rc.something scripts > > > already done. It seems David Nugent is finally committing the idea of > > [...] > > > > Let me first say that I am very pleased with the direction the > > FreeBSD /etc/rc model is moving. It provides the possibility > > for additional software packages to install startup scripts without > > fiddling with existing files, but it does not have the > > (mostly useless) overkill complexity of the SystemV model. > > > > But I would suggest that the /usr/local/etc/rc.d directory is > > moved to /etc/rc.d. > > > > Imagine a server machine running the apache httpd, which is > > started from /usr/local/etc/rc.d, and several diskless clients, > > nfs-mounting their filesystems (including /usr/local) from the > > This is exactly what was annoying me here some time ago > when I installed apache on a NIS/NFS server machine. > > Suddenly all clients were running httpds and I had to disable > manually on all clients to leave out /usr/local/etc/rc.d in > $local_startup (/etc/rc.conf) > > I agree with moving it to /etc/rc.d unless a better FreeBSD > diskless/NFS concept is being developed from ground up. Actually > there ain't any diskless strategy right now, afaik. > > > server. The /etc/rc script on the clients will then see the > > apache startup script in /usr/local/etc/rc.d. So you will > > have a httpd process running on each client, except if you > > modify the /etc/rc script on each client, which is > > not excactly what you want. > > > > Moving the rc.d directory to /etc would avoid this problem, > > since /etc is (usually) private to a single machine. I guess I don't see what the problem with the current system is. Currently you can have one script (assuming you have NFS mounting it amoung N machines) that says: case `hostname` in $SERVER) ;; esac where if it is moved to /etc/rc.d, then you must maintain N scripts, AND you stand more of a chance that those scripts will get clobbered on the next OS upgrade. I'm afraid I'd have to say that I consider the current system considerably more elegant than the /etc/rc.d one being proposed. --alan From owner-freebsd-hackers Fri Jul 11 04:35:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA02828 for hackers-outgoing; Fri, 11 Jul 1997 04:35:49 -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 EAA02820 for ; Fri, 11 Jul 1997 04:35:43 -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 HAA22291; Fri, 11 Jul 1997 07:35:11 -0400 (EDT) Message-Id: <199707111135.HAA22291@spoon.beta.com> To: bde@zeta.org.au cc: hackers@freebsd.org Subject: RE:Re: Trigger for received PPP packets? Date: Fri, 11 Jul 1997 07:35:10 -0400 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [IVAN @ Cyclades. thought you'd like to see this (you might have some ideas). Also, scan for "FIRMWARE ENHANCEMENT" for a neat idea] > >>I asked this question once before a week or so ago, and didn't get a great >>response about it, so I'll try it from a different angle. > >It's probably too technical for -hackers. > Too technical for -hackers? Ick... Thats a scary thought.... >>I'm playing with serial device X, for which the driver is in a prototype >>stage... Its working fine, except for receiving PPP packets. Basically >>the data is being stowed in the clists via the l_rint routine. The problem > >ppp doesn't use clists for input. > Ok. Silly me :) But, if thats the case, and it doesn't use clists, how many characters can be l_rint'ed at a time before I have to take a break? It might just be possible that I'm sucking in partial-frames at a time. >>that I'm seeing is that a received packet is taking quite a long time >>(roughly 100 - 150ms) to get processed. A ping, for instance, on a 115200 >>serial link, takes about 347-380ms round trip. > >Apparently the driver is not delivering characters to ppp promptly. I >guess it uses huge buffers and doesn't get interrupted for packet framing >characters. > Hmm... Smells like FIRMWARE ENHANCEMENT :) Realistically, however, I don't think the RX interrupt is that far apart, and if it is, it should level itself out over time. The device will interrupt when the buffer is full, or after 3 character wait-times if no new data comes in. Therefore, for slow traffic, such as pings only, the latency should only be increased by 3 character times. For heavy-load traffic, interrupts will be generated every time the buffers fill, but then (at 8K), a handful of packets should be available, assuming I l_rint them all (see note on number of characters I can move if it doesn't use clists). Even if I don't, additional interrupts will occur when the buffer refills, or 3 character times elapse. Anyhow, this may be the core problem, and I guess I need to understand how PPP wants the data delivered a little better. (Hints, please?) >>Using 16550s, it takes about >>47-80ms round trip. Connecting the device to a 16550 yields fast throughput >>from board to 16550, but much slower from 16550 to the device (hence why >>I believe its the receive side). > >sio delivers characters to ppp within one fifo full time of receipt of >a packet framing character. This gives a maximum additional latency at >115200 bps of 14 character times (1.2 msec) for 16550's and 1 character >time (87 usec) for 8250's and 16450's. On a local line with 16550's, >ping latency should be about 16 msec for cslip, 17 msec for pppd -bsdcomp, >and 8 msec for pppd with the default of bsdcomp enabled and used. > Again, my driver should develiver within either a.) A full RX buffer, which means multiple PPP packets will be ready, or 3 character times of no reception, which will put it in line between a 16550 and the lower end UARTS (Will atually put it at 3x an 8250). I think the problem may be in that I assume I can move no more than TTYHOG bytes on an clist. But, again, this shouldn't affect small packets (ie -pings), either. -Brian >Bruce > >------- End of Forwarded Message > From owner-freebsd-hackers Fri Jul 11 04:42:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA03055 for hackers-outgoing; Fri, 11 Jul 1997 04:42:33 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA03044 for ; Fri, 11 Jul 1997 04:42:08 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id RAA27645; Fri, 11 Jul 1997 17:41:23 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707111141.RAA27645@hq.icb.chel.su> Subject: Re: /etc/init.d/ To: Gary.Jennejohn@munich.netsurf.de Date: Fri, 11 Jul 1997 17:41:22 +0600 (ESD) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199707111023.KAA07742@peedub.gj.org> from "Gary Jennejohn" at Jul 11, 97 10:23:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like > >> scheme in FreeBSD? I think it will be useful. And I am ready to do it. I think the scheme used in HP-UX 10 is better. It collects the scripts in /sbin/init.d, /sbin/rcX.d while their configuration files with tunable parameters are located in /etc/init.d. This allows to keep the configuration parameters between upgrades very easily. -SB From owner-freebsd-hackers Fri Jul 11 05:47:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA05122 for hackers-outgoing; Fri, 11 Jul 1997 05:47:47 -0700 (PDT) Received: from pandora.hh.kew.com (root@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA05117 for ; Fri, 11 Jul 1997 05:47:45 -0700 (PDT) Received: (from root@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id IAA03980 for freebsd-hackers@FreeBSD.ORG; Fri, 11 Jul 1997 08:47:40 -0400 (EDT) Date: Fri, 11 Jul 1997 08:47:40 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707111247.IAA03980@pandora.hh.kew.com> To: freebsd-hackers@FreeBSD.ORG Subject: RFC: IPFW-DIVERT change. WAS:[ipfw rules processing order..] Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sort of a separate issue, but ... While it depends on your plans for divert sockets, in the current motif I prefer the full ruleset be rescanned and processed. As previous noted, the simple semantics (hopefully) make it harder to confuse the user. Avoiding this additional confusion is desirable if you follow my personal rules for the use of divert rules: Inserting a divert rule for _inbound_ packets only near the top of the file. (It may be possible to limit the diverted port range, at least on my system, to 1024-65K; I have not looked at this in detail, but it would help inbound SMTP traffic.) Dropping the "setup" keyword from numerous TCP well-known port rules (WWW is most important, SMTP doesn't use its well-known port for most _outbound_ traffic.) Moving the "pass tcp from any to any established" rule after the well-known port TCP rules. Inserting the outbound packwet divert rule immediately before the above "established" rule. With this configuration on a true firewall system running both a lot of services on well-known ports and natd, natd is bypassed for the bulk of the locally generated outbound traffic with resulting lower CPU usage. Of course, no firewall with natd should be for the faint hearted. -ahd- From owner-freebsd-hackers Fri Jul 11 06:50:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA07271 for hackers-outgoing; Fri, 11 Jul 1997 06:50:12 -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 GAA07265 for ; Fri, 11 Jul 1997 06:50:10 -0700 (PDT) Message-Id: <199707111345.JAA11417@gatekeeper.itribe.net> Received: forwarded by SMTP 1.6.0. Date: Fri, 11 Jul 1997 09:49:52 -0400 (EDT) From: Jamie Bowden To: BRiGHTMN cc: freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, BRiGHTMN wrote: > > In case anyone was wondering: the original drive problems that > > provoked this thread were thermal shutdown problems. He has > > been running the machine with an extra fan for the drive, and > > the problem has not recurred. > > > > FYI: it was a Quantum drive... it would have been obvious from > > that that the problem was thermal. 8-). > > umm i'm looking into buying a Quantum bigfoot 6.4gig for personal use > bad idea? > The 2.5G Bigfoot drives were fine and ran very cool. The Quantum SCSI drives are the ones that have overheating problems. Jamie Bowden System Administrator, iTRiBE.net From owner-freebsd-hackers Fri Jul 11 07:04:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA07875 for hackers-outgoing; Fri, 11 Jul 1997 07:04:24 -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 HAA07870 for ; Fri, 11 Jul 1997 07:04:19 -0700 (PDT) Received: (from sos@localhost) by sos.freebsd.dk (8.8.6/8.7.3) id QAA08826; Fri, 11 Jul 1997 16:03:42 +0200 (MEST) From: Søren Schmidt Message-Id: <199707111403.QAA08826@sos.freebsd.dk> Subject: Re: Where I can read about kernel hacking In-Reply-To: from Igor at "Jul 11, 97 03:45:02 pm" To: igor@blik.samara.su (Igor) Date: Fri, 11 Jul 1997 16:03:42 +0200 (MEST) Cc: 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Igor who wrote: > Where I can read about 'FreeBSD kernel hacking' ? /usr/src/sys -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Fri Jul 11 07:47:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA13168 for hackers-outgoing; Fri, 11 Jul 1997 07:47:15 -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 HAA13163 for ; Fri, 11 Jul 1997 07:47:09 -0700 (PDT) Received: from james.freenet.hamilton.on.ca (ac199@james.hwcn.org [199.212.94.66]) by hwcn.org (8.8.6/8.8.6) with ESMTP id KAA25862; Fri, 11 Jul 1997 10:47:22 -0400 (EDT) Received: from localhost (ac199@localhost) by james.freenet.hamilton.on.ca (8.8.6/8.8.6) with SMTP id KAA24361; Fri, 11 Jul 1997 10:47:36 -0400 (EDT) X-Authentication-Warning: james.freenet.hamilton.on.ca: ac199 owned process doing -bs Date: Fri, 11 Jul 1997 10:47:35 -0400 (EDT) From: Tim Vanderhoek X-Sender: ac199@james.freenet.hamilton.on.ca Reply-To: hoek@hwcn.org cc: Igor , hackers@FreeBSD.ORG Subject: Re: Where I can read about kernel hacking In-Reply-To: <199707111403.QAA08826@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id HAA13164 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Jul 1997, Søren Schmidt wrote: > In reply to Igor who wrote: > > Where I can read about 'FreeBSD kernel hacking' ? > > /usr/src/sys And the bibliography section, the kernel debugging section, and the FreeBSD internals section of the handbook. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk From owner-freebsd-hackers Fri Jul 11 08:03:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA13850 for hackers-outgoing; Fri, 11 Jul 1997 08:03:04 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA13839 for ; Fri, 11 Jul 1997 08:02:59 -0700 (PDT) Received: from smtp1.ts.kiev.ua (viking.ts.kiev.ua [193.124.229.195]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id IAA01894 for ; Fri, 11 Jul 1997 08:02:49 -0700 (PDT) Received: from aviion.ts.kiev.ua by smtp1.ts.kiev.ua with SMTP id RAA26416; (8.8.3/zah/2.1) Fri, 11 Jul 1997 17:51:29 +0300 (EET DST) Received: from nbki.ipri.kiev.ua by aviion.ts.kiev.ua with ESMTP id PAA02319; (8.6.11/zah/2.1) Fri, 11 Jul 1997 15:35:12 GMT Received: from cki.ipri.kiev.ua by nbki.ipri.kiev.ua with ESMTP id RAA18056; (8.6.9/zah/1.1) Fri, 11 Jul 1997 17:25:35 +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 RAA04201; Fri, 11 Jul 1997 17:26:26 +0300 (EET DST) Message-ID: <33C634EA.6354@cki.ipri.kiev.ua> Date: Fri, 11 Jul 1997 16:28:01 +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: Tony Sterrett CC: hackers@FreeBSD.ORG Subject: Re: gcc 2.7.2.2 and FreeBSD References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Sterrett wrote: > > Hi I've just installed FreeBSD 2.2.2 and I would like to install > gcc 2.7.2.2 but its looking for a lib gnumalloc is this known by > some other name. I can't find it. Thank for any help sorry for the > stupid question. Better not change the default compiler, but get pgcc-2.7.2.9 from ports collection. > Tony Sterrett From owner-freebsd-hackers Fri Jul 11 08:40:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA15913 for hackers-outgoing; Fri, 11 Jul 1997 08:40:11 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA15904 for ; Fri, 11 Jul 1997 08:40:05 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id PAA22376; Fri, 11 Jul 1997 15:40:54 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma022372; Fri Jul 11 15:40:29 1997 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id IAA21779; Fri, 11 Jul 1997 08:39:38 -0700 Date: Fri, 11 Jul 1997 08:39:38 -0700 From: "M.R.Murphy" Message-Id: <199707111539.IAA21779@meerkat.mole.org> To: hackers@freebsd.org Subject: grins Cc: mrm@mole.mole.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just for grins: poco# date;uname -a;uptime Fri Jul 11 08:38:09 PDT 1997 FreeBSD poco.mole.org 1.1.5(RELEASE) POCO#0 i386 8:38am up 442 days, 2:53, 1 user, load average: 0.00, 0.00, 0.00 poco# :-) -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-hackers Fri Jul 11 09:33:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA18965 for hackers-outgoing; Fri, 11 Jul 1997 09:33:41 -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 JAA18951 for ; Fri, 11 Jul 1997 09:33:36 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wmiYh-00079a-00; Fri, 11 Jul 1997 09:28:39 -0700 Date: Fri, 11 Jul 1997 09:28:38 -0700 (PDT) From: Tom Samplonius To: Jamie Bowden cc: freebsd-hackers@freebsd.org Subject: Re: sd0 timed out while idle In-Reply-To: <199707111345.JAA11417@gatekeeper.itribe.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 11 Jul 1997, Jamie Bowden wrote: > The 2.5G Bigfoot drives were fine and ran very cool. The Quantum SCSI > drives are the ones that have overheating problems. Bigfoot drives are 3400rpm, which makes them cool, and really slow. Until, I saw the Bigfoot specs, I had no idea that anybody made anything slower than 5400rpm these days! > Jamie Bowden > > System Administrator, iTRiBE.net > > > Tom From owner-freebsd-hackers Fri Jul 11 09:50:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20017 for hackers-outgoing; Fri, 11 Jul 1997 09:50:42 -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 JAA20010 for ; Fri, 11 Jul 1997 09:50:38 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA07037; Fri, 11 Jul 1997 12:50:03 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 11 Jul 1997 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.5/8.7.3) with ESMTP id IAA01233; Fri, 11 Jul 1997 08:11:31 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.5/8.6.9) id IAA07785; Fri, 11 Jul 1997 08:20:14 -0400 (EDT) Date: Fri, 11 Jul 1997 08:20:14 -0400 (EDT) From: Thomas David Rivers Message-Id: <199707111220.IAA07785@lakes.water.net> To: ponds!lakes.water.net!rivers, ponds!i-Connect.Net!Shimon Subject: RE: pertinent to my "daily panics" (was Re: Clists limited to 10 Cc: ponds!zeta.org.au!bde, ponds!cisco.com!bmcgover, ponds!FreeBSD.ORG!hackers Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Simon writes: > > > > This looks like it's in the area of my "daily panic" problem... > > Especially the part about "from scsi_done() up things..." > > > > Has anything more happened along this issue? Did anyone discover > > anything? > > Nope. We still experience it daily. I am in the process of migrating to > -current to see if it is still there. > > Simon > Hmmm... can you relay the detailes of your daily panics; I'd like to know if it fits the profile of my situation.... If it's a match, I'd be happy to share with you everything I've got, perhaps we can, together, nail this one... - Dave Rivers - From owner-freebsd-hackers Fri Jul 11 09:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA20114 for hackers-outgoing; Fri, 11 Jul 1997 09:52:11 -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 JAA20108; Fri, 11 Jul 1997 09:52:05 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA04925 (5.67b/IDA-1.5); Fri, 11 Jul 1997 18:51:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id SAA13726; Fri, 11 Jul 1997 18:51:38 +0200 (CEST) X-Face: " Date: Fri, 11 Jul 1997 18:51:37 +0200 From: Stefan Esser To: Narvi Cc: mika ruohotie , hackers@FreeBSD.ORG, Stefan Esser Subject: Re: PQ_LARGECACHE and page colouring References: <199707092048.XAA24685@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Narvi on Thu, Jul 10, 1997 at 11:18:23AM +0300 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 10, Narvi wrote: > > > > > if I add options PQ_LARGECACHE to the kernel config file. > > > > something we with 512K cache should use or not? > I have about the same (asus fx motherboard + 512K pipline burst cache in > the form of a coast module). > > I don't know if it is direct-mapped or not - there is no documentation I > can get my hands on. But it does help. All current chip sets for Pentium class processors support only a direct mapped secondary cache, AFAIK. 2-way or 4-way mapped caches on the motherboard were common in the 386 days, and may have been supported by some 486 chip set (I don't really know), but made sense mostly because of the much smaller cache size than common today. Regards, STefan From owner-freebsd-hackers Fri Jul 11 10:25:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22642 for hackers-outgoing; Fri, 11 Jul 1997 10:25:54 -0700 (PDT) Received: from odin.visigenic.com (odin.visigenic.com [204.179.98.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22636 for ; Fri, 11 Jul 1997 10:25:52 -0700 (PDT) Received: from VSI48 (vsi48.visigenic.com [206.64.15.185]) by odin.visigenic.com (Netscape Mail Server v2.02) with SMTP id AAA15767 for ; Fri, 11 Jul 1997 10:24:30 -0700 Message-Id: <3.0.2.32.19970711102604.009ca270@visigenic.com> X-Sender: toneil@visigenic.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Fri, 11 Jul 1997 10:26:04 -0700 To: hackers@FreeBSD.ORG From: "Tim Oneil" Subject: Re: sd0 timed out while idle In-Reply-To: References: <199707111345.JAA11417@gatekeeper.itribe.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 09:28 AM 7/11/97 -0700, you wrote: > >On Fri, 11 Jul 1997, Jamie Bowden wrote: > >> The 2.5G Bigfoot drives were fine and ran very cool. The Quantum SCSI >> drives are the ones that have overheating problems. > > Bigfoot drives are 3400rpm, which makes them cool, and really slow. > > Until, I saw the Bigfoot specs, I had no idea that anybody made anything >slower than 5400rpm these days! I've heard that about fireballs, but I have a two drive system sitting in my house without air conditioning (its been a bit hot here lately) and haven't had a problem. The system is in a stock case, ie; only the usual two fans, one at the p/s and one at the cpu. And I like this quantum for its speed. From owner-freebsd-hackers Fri Jul 11 11:13:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA25801 for hackers-outgoing; Fri, 11 Jul 1997 11:13:16 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA25795 for ; Fri, 11 Jul 1997 11:13:12 -0700 (PDT) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id OAA20699; Fri, 11 Jul 1997 14:08:06 -0400 (EDT) Date: Fri, 11 Jul 1997 14:20:24 -0400 (EDT) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: BRiGHTMN cc: hackers list FreeBSD , ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 22 Jun 1997, BRiGHTMN wrote: > it works like so: > first matched = action > > if you want anything firewalled out put it before it hits natd > > /sbin/ipfw -f flush > /sbin/ipfw add 100 deny ip from evil.place.org to any > /sbin/ipfw add 200 divert 6668 all from any to any via ed0 > /sbin/ipfw add 300 pass all from any to any > the numbers are the order that way if you decide to change anything you > can: > /sbin/ipfw delete 200 > to get rid of the natd... > > if you want you can take a look at my natd configuration files i'm going > to post them on my webpage: > > www.cs.sunyit.edu/~perlsta > > it should be up later tonight... Thanks... where on your marvey site might this be located? :-) BTW, yesterday afternoon when I checked I got snappy response from your web server. Today it seems to be crawling mighty slow. Thanks, Chuck > > > Hi all, > > > > I'm a bit unsure about the order in which ipfw rules get processed in > > relation to a DIVERT rule that calls natd(8). Note the last few sentences > > from this excerpt from the natd(8) man page: > > > > /sbin/ipfw -f flush > > /sbin/ipfw add divert 6668 all from any to any via ed0 > > /sbin/ipfw add pass all from any to any > > The second line depends on your interface and assumes that you've > > updated /etc/services as above. If you specify real firewall rules, > > ---> it's best to specify line 2 at the start of the script so that natd > > ---> sees all packets before they are dropped by the firewall. The fire- > > ---> wall rules will be run again on each packet after translation by > > ---> natd, minus any divert rules. > > > > If I take this as literally as I can, I interpret it as follows > > > > * Rules before divert rule processed > > * Divert rule ships all packets not dropped by above rules > > to natd for address translation > > * Packets return from natd and are then subjected to ALL rules, > > except this time divert rule is skipped > > > > This is somewhat counter-intuitive to me. If this how it works, what is > > the reason for this design, since, as I think about it, there must be a > > performance penalty to this approach (multiple passes of rules). I had > > expected it to work like this: > > > > * Rules before divert rule processed > > * Divert rule ships all packets not dropped by above rules > > to natd for address translation > > * Packets return from natd and remaining rules after divert rule > > are processed > > > > What is the real story? > > > > Thanks very much, > > --- > > ------------------------------------------------------------------------- > > Charles N. Owens Email: owensc@enc.edu > > http://www.enc.edu/~owensc > > Network & Systems Administrator > > Information Technology Services "Outside of a dog, a book is a man's > > Eastern Nazarene College best friend. Inside of a dog it's > > too dark to read." - Groucho Marx > > ------------------------------------------------------------------------- > > > > > > --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-hackers Fri Jul 11 11:26:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26364 for hackers-outgoing; Fri, 11 Jul 1997 11:26:35 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA26353 for ; Fri, 11 Jul 1997 11:26:32 -0700 (PDT) Received: (from shimon@localhost) by sendero.i-connect.net (8.8.6/8.8.5) id LAA24849; Fri, 11 Jul 1997 11:26:29 -0700 (PDT) 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: <199707110808.RAA23281@genesis.atrad.adelaide.edu.au> Date: Fri, 11 Jul 1997 11:26:29 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Michael Smith Subject: Re: Make World Explodes Cc: FreeBSD-Hackers@FreeBSD.ORG, dg@root.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Michael Smith; On 11-Jul-97 you wrote: I alrerady apologized for my ignorance and stupidity. Here I apologize again. I am stupid and ignorant and am really sorry for being so. Really and hoestly. Having said that: > Simon Shapiro stands accused of saying: > > > > You must jump into conclusions :-) > > Not often. I agree. ... > The answer to D. would already be known to you if A. was true, as I > have explained at _least_ twice in public mail on this thread exactly > why this is a one-off gotcha. Bruce has even clarified the situation > with extreme precision in yet another mail. There is no logical way to prove something is not or did not happen. Stating that I do not read mail is impossible for anyone but me. It is like saying ``You did not send me that letter''. Maybe I did but you did not receive it? In our case, maybe I read the mail, did what was suggested and it still did not work? ... > So you have to help it out by presuming your 'install' is up to it and > running the 'make includes' by hand. Like I said, I did all that but it still did not work. Turns out the problem was my blind reliance on CVS and CVSUP to work correctly under all conditions. I run CVSUP under cron few times a day and cvs update on my source tree at least twice a week, with manual runs in between. I run make world once a week, and make release every week or two. The problem was solved here (after much digging (and running make includes three times :-) by; a) removing the entire source tree and checking out from CVS, or b) (as suggested) removingthe sup database and running cvsup again. This produced a clean compile, the world have rarely seen before. I admit, in addition to stupidity, bad habits. Being in the RDBMS world for as many decades as I have been, one grows used to complex processes always ending in a well defined state; a) Failure which means ``no change has been made at all or b) succes, which means ``ALL changes are in place'' I know we do not have that with all the tools we use all the time and know why and do not aruge. But some times, I forget and assume the wrong assumptions. Simon From owner-freebsd-hackers Fri Jul 11 11:49:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA27457 for hackers-outgoing; Fri, 11 Jul 1997 11:49:30 -0700 (PDT) Received: from trinity1.tpi.net (trinity1.tpi.net [207.212.42.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA27452 for ; Fri, 11 Jul 1997 11:49:28 -0700 (PDT) Received: from p100 (n2-102-70.thegrid.net [209.60.102.70]) by trinity1.tpi.net (8.6.13/8.6.12) with SMTP id LAA15984 for ; Fri, 11 Jul 1997 11:44:35 -0700 Message-ID: <33C6802D.1707@tpi.net> Date: Fri, 11 Jul 1997 11:49:30 -0700 From: Chris Stefanetti Reply-To: chris@tpi.net Organization: Office of Christopher Stefanetti X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Assigning ip address to FreeBSD host References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Everyone, this may sound rudimentary but---How do I assign an IP address to my FreeBSD machine? I set the IP in sysconfig to the NIC which is being autodetected as ed1. So I've set ed1 to 192.168.1.4 which is the address I want to use. Do I have to change anything in any other files? The host file? This is a bit confusing since what I want to do is just have it on my local net and call it "boogie" The host file examples show names which include . like myname.domainname.net or something like that. could someone send me a simple example of a working sysconfig and hosts file and anyother config files I may need to get this thing on my net. right now I would be very happy to just be able to telnet to it... Thanks ---Chris From owner-freebsd-hackers Fri Jul 11 11:54:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA27718 for hackers-outgoing; Fri, 11 Jul 1997 11:54:30 -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 LAA27711 for ; Fri, 11 Jul 1997 11:54:25 -0700 (PDT) Received: from Elvis.RatsNest.VaBeach.Va.Us (slip166-72-229-66.va.us.ibm.net [166.72.229.66]) by out2.ibm.net (8.8.5/8.6.9) with SMTP id SAA38780 for ; Fri, 11 Jul 1997 18:53:57 GMT Received: by localhost with Microsoft MAPI; Fri, 11 Jul 1997 14:52:28 -0400 Message-ID: <01BC8E0A.0D6D1100.SimsS@IBM.Net> From: Steve Sims Reply-To: "SimsS@IBM.Net" To: "hackers@FreeBSD.ORG" Subject: RE: grins Date: Fri, 11 Jul 1997 14:52:09 -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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gee, and I was pretty proud of this one..... ns2/root:~# date ; uname -a ; uptime Fri Jul 11 14:53:42 1997 FreeBSD ns2.my.org 2.2-960323-SNAP FreeBSD 2.2-960323-SNAP #0: Sat Mar 2 3 21:59:52 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386 2:53PM up 385 days, 18:31, 1 user, load averages: 0.13, 0.03, 0.01 ns2/root:~# Of course, you'll notice that this is a stove-stock 2.2-SNAP release off of a Snapshot CD. (Thanks, Jordan!) ...sjs... On Friday, July 11, 1997 11:40 AM, M.R.Murphy [SMTP:mrm@Mole.ORG] wrote: > > Just for grins: > > poco# date;uname -a;uptime > Fri Jul 11 08:38:09 PDT 1997 > FreeBSD poco.mole.org 1.1.5(RELEASE) POCO#0 i386 > 8:38am up 442 days, 2:53, 1 user, load average: 0.00, 0.00, 0.00 > poco# > > :-) > > -- > Mike Murphy mrm@Mole.ORG +1 619 598 5874 > Better is the enemy of Good > From owner-freebsd-hackers Fri Jul 11 12:13:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28641 for hackers-outgoing; Fri, 11 Jul 1997 12:13:47 -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 MAA28635 for ; Fri, 11 Jul 1997 12:13:37 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wml5z-0002tE-00; Fri, 11 Jul 1997 13:11:11 -0600 To: "M.R.Murphy" Subject: Re: grins Cc: hackers@freebsd.org, mrm@mole.mole.org In-reply-to: Your message of "Fri, 11 Jul 1997 08:39:38 PDT." <199707111539.IAA21779@meerkat.mole.org> References: <199707111539.IAA21779@meerkat.mole.org> Date: Fri, 11 Jul 1997 13:11:11 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707111539.IAA21779@meerkat.mole.org> "M.R.Murphy" writes: : FreeBSD poco.mole.org 1.1.5(RELEASE) POCO#0 i386 : 8:38am up 442 days, 2:53, 1 user, load average: 0.00, 0.00, 0.00 Damn. You have our router best time beat by about 100 days. Silly thing had to be rebooted for the sl0 race problem that was fixed in 2.0. However, we've been cheating. Our machine is on a UPS. Warner From owner-freebsd-hackers Fri Jul 11 12:22:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28957 for hackers-outgoing; Fri, 11 Jul 1997 12:22:19 -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 MAA28951 for ; Fri, 11 Jul 1997 12:22:14 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14555; Fri, 11 Jul 1997 21:22:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA04648; Fri, 11 Jul 1997 21:20:28 +0200 (MET DST) Message-ID: <19970711212028.IM60253@uriah.heep.sax.de> Date: Fri, 11 Jul 1997 21:20:28 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: igor@blik.samara.su (Igor) Subject: Re: Where I can read about kernel hacking References: <199707111403.QAA08826@sos.freebsd.dk> 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 Tim Vanderhoek on Jul 11, 1997 10:47:35 -0400 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Tim Vanderhoek wrote: > And the bibliography section, the kernel debugging section, and > the FreeBSD internals section of the handbook. And in the Daemon book. -- 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 Fri Jul 11 12:23:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29035 for hackers-outgoing; Fri, 11 Jul 1997 12:23: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 MAA29020 for ; Fri, 11 Jul 1997 12:23:06 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14563 for freebsd-hackers@FreeBSD.ORG; Fri, 11 Jul 1997 21:22:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA04604; Fri, 11 Jul 1997 21:14:40 +0200 (MET DST) Message-ID: <19970711211440.BV38545@uriah.heep.sax.de> Date: Fri, 11 Jul 1997 21:14:40 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Subject: Re: /etc/init.d/ References: <19970711093543.62687@tversu.ac.ru> <19970711084614.RJ19398@uriah.heep.sax.de> <33C5EFC1.41C67EA6@bonn-online.com> 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: <33C5EFC1.41C67EA6@bonn-online.com>; from Sebastian Lederer on Jul 11, 1997 10:33:05 +0200 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Sebastian Lederer wrote: > But I would suggest that the /usr/local/etc/rc.d directory is > moved to /etc/rc.d. > > Imagine a server machine running the apache httpd, which is > started from /usr/local/etc/rc.d, and several diskless clients, > nfs-mounting their filesystems (including /usr/local) from the > server. If you're NFS-exporting your /usr/local, you are basically expected to care for /usr/local/etc yourself. Typically, this would be a symlink to /etc/local/ then. There's quite more in /usr/local/etc that will make it machine-specific, like various configuration files. This should probably be mentioned somewhere. -- 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 Fri Jul 11 12:23:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29107 for hackers-outgoing; Fri, 11 Jul 1997 12:23: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 MAA29094 for ; Fri, 11 Jul 1997 12:23:50 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14574 for freebsd-hackers@freefall.FreeBSD.org; Fri, 11 Jul 1997 21:23:22 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA04616; Fri, 11 Jul 1997 21:16:21 +0200 (MET DST) Message-ID: <19970711211621.IU40866@uriah.heep.sax.de> Date: Fri, 11 Jul 1997 21:16:21 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: /etc/init.d/ References: <199707111023.KAA07742@peedub.gj.org> <199707111141.RAA27645@hq.icb.chel.su> 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: <199707111141.RAA27645@hq.icb.chel.su>; from Serge A. Babkin on Jul 11, 1997 17:41:22 +0600 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Serge A. Babkin wrote: > > >> how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like > > >> scheme in FreeBSD? I think it will be useful. And I am ready to do it. > > I think the scheme used in HP-UX 10 is better. It collects > the scripts in /sbin/init.d, /sbin/rcX.d while their configuration > files with tunable parameters are located in /etc/init.d. All SysV-derivatives do it this way, including but not limited to Slowaris. SVR3s didn't have symlinks, they probably did it with hard links then (and everything has been under /etc, of course). -- 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 Fri Jul 11 13:52:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02731 for hackers-outgoing; Fri, 11 Jul 1997 13:52:14 -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 NAA02726 for ; Fri, 11 Jul 1997 13:52:10 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA25630; Fri, 11 Jul 1997 13:45:13 -0700 From: Terry Lambert Message-Id: <199707112045.NAA25630@phaeton.artisoft.com> Subject: Re: Make World Explodes To: Shimon@i-Connect.Net (Simon Shapiro) Date: Fri, 11 Jul 1997 13:45:13 -0700 (MST) Cc: tom@sdf.com, FreeBSD-Hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Jul 10, 97 08:18:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > /usr/src/2.2/src/usr.bin/xinstall/../../bin/ls/stat_flags.c:72: > > > `UF_NOUNLINK' undeclared (first use this function) > > > > > > ... > > > > Do a "make includes" first to get the include files up to date. > > I did. That is not it. Yes, it is. The assumption here is that the kernel source tree is -current, as well, since that value is coming from /usr/src/sys/... 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 Jul 11 14:02:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03150 for hackers-outgoing; Fri, 11 Jul 1997 14:02:23 -0700 (PDT) Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA03141 for ; Fri, 11 Jul 1997 14:02:19 -0700 (PDT) Received: from roo.isi.edu by zephyr.isi.edu (5.65c/5.61+local-26) id ; Fri, 11 Jul 1997 14:02:17 -0700 Message-Id: <199707112102.AA14106@zephyr.isi.edu> X-Mailer: exmh version 1.6.4 10/10/95 To: hackers@freebsd.org Subject: vm_page_alloc_contig Reply-To: hutton@ISI.EDU Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Jul 97 14:01:17 PDT From: Anne Hutton Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I came across this email in the hackers archive...the system I'm using (FreeBSD 2.2.1) is also experiencing panics which are due to page faults - I have a device driver which does a vm_page_alloc_contig. There are no problems until I try to forward packets through this interface from another NIC. Can someone tell me if the problem described in this email was recognised as a problem/bug and, if so, was it fixed? thanks, Anne ------- Forwarded Message Date: Sat, 24 Aug 1996 05:29:56 -0400 (EDT) From: Dave Chapeskie To: FreeBSD-hackers@freebsd.org Cc: davidg@freebsd.org Sender: owner-hackers@freebsd.org Subject: kernel vm_page_alloc_contig() can indirectly cause kernel page faults [Small patch which I'd like committed follows my rather wordy description] I have a scenario where I need large amounts of contiguous memory (8-16MB). A colleague of mine tossed together a contiguous memory driver which uses vm_page_alloc_contig() from sys/vm/vm_page.c to alloc contiguous memory at startup and then makes it available to user processes to mmap that memory in. In using this memory we've been plagued with kernel page faults, commonly at vmapbuf+0x86 when using the memory in a read(2) or write(2) call. In tracking this down I found that there were no problems in the first 4MB or so of memory and that the problems only occurred when the virtual address (in the contig driver) crossed a page directory boundary (ie the top 10 bits changed). I believe the problem can be traced back to vm_page_alloc_contig() which wires down the pages directly with vm_page_wire(). Obviously the memory must be wired if it is to stay contiguous. The problem, I believe, is that the rest of the vm system isn't told that this memory is wired down. I imagine this problem isn't normally seen since vm_page_alloc_contig() maps the memory into the kernel map which has other pages mapped which will cause the entire page directory entry to be wired in. This would explain why I don't see the problem until the memory spreads into the next PDE. The following small patch makes everything work dandy for me. It lets vm_map_pageable() do the dirty work of making sure the entire vm system knows the memory is wired, in particular it tells the pmap so that the new PDE gets wired. Can a vm guru take a look at this and commit it (or tell me another way to fix my problem). I should be able to provide code that demonstrates the failure if it's required (I'd have to ask the guy that wrote it and my boss first). Diff is relative to $Id: vm_page.c,v 1.32.4.1 1996/06/19 07:22:45 davidg Exp $ from 2.1.5-RELEASE *** sys/vm/vm_page.c.orig Sat Aug 24 05:15:34 1996 - --- sys/vm/vm_page.c Sat Aug 24 05:16:32 1996 *************** *** 746,755 **** m->bmapped = 0; m->busy = 0; vm_page_insert(m, kernel_object, tmp_addr - VM_MIN_KERNEL_ADDRESS); - - vm_page_wire(m); pmap_kenter(tmp_addr, VM_PAGE_TO_PHYS(m)); tmp_addr += PAGE_SIZE; } splx(s); return (addr); - --- 746,756 ---- m->bmapped = 0; m->busy = 0; vm_page_insert(m, kernel_object, tmp_addr - VM_MIN_KERNEL_ADDRESS); pmap_kenter(tmp_addr, VM_PAGE_TO_PHYS(m)); tmp_addr += PAGE_SIZE; } + + vm_map_pageable(kernel_map, addr, addr + size, FALSE); splx(s); return (addr); - -- Dave Chapeskie Leitch Technology International Inc. Email: dchapes@zeus.leitch.com ------- End of Forwarded Message From owner-freebsd-hackers Fri Jul 11 14:10:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03578 for hackers-outgoing; Fri, 11 Jul 1997 14:10:50 -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 OAA03567 for ; Fri, 11 Jul 1997 14:10:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA25677; Fri, 11 Jul 1997 14:01:20 -0700 From: Terry Lambert Message-Id: <199707112101.OAA25677@phaeton.artisoft.com> Subject: Re: /etc/init.d/ To: lederer@bonn-online.com (Sebastian Lederer) Date: Fri, 11 Jul 1997 14:01:20 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@FreeBSD.ORG, vadim@tversu.ac.ru In-Reply-To: <33C5EFC1.41C67EA6@bonn-online.com> from "Sebastian Lederer" at Jul 11, 97 10:33:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Moving the rc.d directory to /etc would avoid this problem, > since /etc is (usually) private to a single machine. Not in most of our ideal universes, it's not: / is mounted as read-only via NFS, and /dev is mounted from devfs and reflects the devices which probed true for the particular machine. 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 Jul 11 14:33:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA04670 for hackers-outgoing; Fri, 11 Jul 1997 14:33:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA04665 for ; Fri, 11 Jul 1997 14:33:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA25717; Fri, 11 Jul 1997 14:26:47 -0700 From: Terry Lambert Message-Id: <199707112126.OAA25717@phaeton.artisoft.com> Subject: Re: /etc/init.d/ To: Gary.Jennejohn@munich.netsurf.de Date: Fri, 11 Jul 1997 14:26:47 -0700 (MST) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199707111023.KAA07742@peedub.gj.org> from "Gary Jennejohn" at Jul 11, 97 10:23:29 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I run a SVR4 box here at home, and the only useful run-level options > (IMHO) it offers involve NFS services. When I need NFS I just > switch to that run-level and all the services are started. When I'm > done using NFS I just switch to a lower level and the NFS stuff is > removed. But a box without networking is pretty useless and I've never > run the box in that configuration. Most of the advocates of run states (not levels) agree with you. However, say I have a laptop; it can be: o Docked at the office and hooked into a net o Undocked at the office in a conference room and hooked into a net via a 4Mbit IR link at the conference table o Undocked on a plane with a dialup link o Undocked anywhere with a cellular link o Undocked anywhere with a cellular link, but out of cell range o Undocked anywhere with no link o Docked at home and hooked into a *different* net o Docked at home with a dialup connection o Docked at home and not hooked into a net I want the boot run state to assess the connectivity options, and pick the run state it ends up in based on the current hardware configuration. I also want to be able to "hot" undock/dock, and automatically change between the appropriate states, as needed. Windows95 assumes you shut the machine down. You must also manually pick one of several "Hardware Profiles" (which you can do at boot time). Even if the states are not automatically configured by docking state/PCMCIA card state changes, in order to do what Windows95 can do, several client and service configuration details normally handled globally in a single rc file in traditional BSD need to be handled otherwise. For example, should I mount the NFS server with the shared copy of WordPerfect 4.2 for IBCS2? There is also the issue of service anonymity: 1) I'm docked at the office, and have created a presentation using a presentation graphics package with a floating network license, run from an office server. 2) I undock at the office to go to a meeting in a conference room 3) I arrive at the conference room and am IR linked 4) I leave the conference room and get in the car 5) I enter my home and redock at the home dock 6) I undock and get back in my car 7) I drive to the airport 8) While waiting for my flight, I check on my stocks via a cellular link 9) I get on the plane, where if I were to use the cellular link, I would get in trouble because the airlines can't make as much money off me (planes would fall out of the sky over any metropolitan area if the avionics claims were true). 10) Halfway through my flight from LA to New York, I user the 28.8 modem built into my ethernet PCMCIA card to connect to the in flight phone and check the stock close price. 11) I arrive at my hotel and use the ISDN card to connect to the hotel's digital PBX, and check my corporate mail. 12) The next morning I check my corporate mail and the opening value of my stock. 13) I drive the rent-a-car to the corporate offices, go into the conference room, and get an IR link and mount the local server where the same presentation software is installed, obtain a local license, and make my presentation to the board. Now it's true that few people will benefit from this total scenario; but it's also true that many more than a few could benefit from any two or more elements in the scenario. And it's a stupid design which prevents these people from being able to easily use a piece of non-Microsoft OS software this way. Even if the majority of people somehow believe they will never install commercial software that needs to be started or shutdown before or after other pieces of the OS or other commercial software (I guess these people believe that Microsoft will always dominate the OS software market, for the rest of time?). Or believe that they will never own a portable computer or PDA. Why make those of us who *aren't* technologically clueless suffer for those who (apparently) are? 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 Jul 11 15:09:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA05992 for hackers-outgoing; Fri, 11 Jul 1997 15:09:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA05985 for ; Fri, 11 Jul 1997 15:08:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25774; Fri, 11 Jul 1997 15:01:31 -0700 From: Terry Lambert Message-Id: <199707112201.PAA25774@phaeton.artisoft.com> Subject: Re: /etc/init.d/ To: aflundi@lundin.abq.nm.us (Alan Lundin) Date: Fri, 11 Jul 1997 15:01:31 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707111120.FAA01337@lundin.abq.nm.us.> from "Alan Lundin" at Jul 11, 97 05:20:40 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I guess I don't see what the problem with the > current system is. Currently you can have one > script (assuming you have NFS mounting it amoung > N machines) that says: > > case `hostname` in > $SERVER) > ;; > esac > > where if it is moved to /etc/rc.d, then you must > maintain N scripts, AND you stand more of a chance > that those scripts will get clobbered on the next > OS upgrade. What if I *want* to clobber the scripts for upgraded facilities when I upgrade the facility? What if I want to upgrade some facilities, but not others? I guess you'd have me editing up my rc file so that I couldn't upgrade without editing it again (big hassle). The other side of the coin is, when I install the HTTP server, I want startup and shutdown sequences placed in my startup and shutdown sequences, automatically, without me having to edit an rc file there, either. 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 Jul 11 15:12:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA06245 for hackers-outgoing; Fri, 11 Jul 1997 15:12:59 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA06234 for ; Fri, 11 Jul 1997 15:12:54 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25784; Fri, 11 Jul 1997 15:02:30 -0700 From: Terry Lambert Message-Id: <199707112202.PAA25784@phaeton.artisoft.com> Subject: Re: /etc/init.d/ To: babkin@hq.icb.chel.su (Serge A. Babkin) Date: Fri, 11 Jul 1997 15:02:29 -0700 (MST) Cc: Gary.Jennejohn@munich.netsurf.de, freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <199707111141.RAA27645@hq.icb.chel.su> from "Serge A. Babkin" at Jul 11, 97 05:41:22 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think the scheme used in HP-UX 10 is better. It collects > the scripts in /sbin/init.d, /sbin/rcX.d while their configuration > files with tunable parameters are located in /etc/init.d. > This allows to keep the configuration parameters between > upgrades very easily. Yes. This is what God has on his machines. 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 Fri Jul 11 15:48:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08043 for hackers-outgoing; Fri, 11 Jul 1997 15:48:34 -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 PAA08038 for ; Fri, 11 Jul 1997 15:48:31 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id PAA18858 for ; Fri, 11 Jul 1997 15:48:30 -0700 (PDT) Message-Id: <199707112248.PAA18858@austin.polstra.com> To: hackers@freebsd.org Subject: CVSup vs. firewalls: a solution Date: Fri, 11 Jul 1997 15:48:30 -0700 From: John Polstra Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quite a few of you have been unable to use CVSup in the past, because you are behind a firewall that is too restrictive for it. If you are in that category, I encourage you to try version 15.1, which I just released last night. It supports a new "multiplexed" mode of operation. In multiplexed mode, CVSup needs just a single TCP connection, initiated by the client, to do its work. If you can persuade your firewall administrator to let you issue connections to port 5999 of your favorite CVSup server, you'll be in business. To select multiplexed mode, add the option "-P m" to the cvsup command line. As its name implies, multiplexed mode works by managing a built-in packet protocol on top of the single TCP connection. That enables the client and server to multiplex multiple logical connections in parallel through the channel. Several people have been using it for a month or so, and it seems to function and perform just fine. See the announcement in the FreeBSD-announce mailing list, or just grab it from . -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-hackers Fri Jul 11 16:47:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA09833 for hackers-outgoing; Fri, 11 Jul 1997 16:47:01 -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 QAA09828 for ; Fri, 11 Jul 1997 16:46:59 -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 QAA11378; Fri, 11 Jul 1997 16:47:44 -0700 (PDT) Message-Id: <199707112347.QAA11378@implode.root.com> To: Simon Shapiro cc: Michael Smith , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: Make World Explodes In-reply-to: Your message of "Fri, 11 Jul 1997 11:26:29 PDT." From: David Greenman Reply-To: dg@root.com Date: Fri, 11 Jul 1997 16:47:43 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I alrerady apologized for my ignorance and stupidity. >Here I apologize again. I am stupid and ignorant and am really sorry >for being so. Really and hoestly. I doubt you are stupid. We are all ignorant. Anyway, stranger things have happened and if things are working for you now, then great!!! -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Fri Jul 11 17:40:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12400 for hackers-outgoing; Fri, 11 Jul 1997 17:40:49 -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 RAA12395 for ; Fri, 11 Jul 1997 17:40:47 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA20096 for ; Fri, 11 Jul 1997 17:36:53 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd020090; Sat Jul 12 00:36:47 1997 Message-ID: <33C6D138.7D55368C@whistle.com> Date: Fri, 11 Jul 1997 17:35:04 -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: TCP bug in 2.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If I could borrow the ear of someone with more knowledge of TCP states than me.. We see the following in a kernel dated from around March 4 and from the logs it looks as if it's present in 2.2.2+ finger, (after a lot of iterations of the test) goes into a permanent wait reading from a socket. the socket is seen to be in FIN_WAIT_2 state after the finger proces is killed the socket STAYS in FIN_WAIT_2 state forever. from what I've read in tcp_input.c etc. This shouldn't happen. 2 problems: 1/ why doesn't finger wake up and return EOF? 2/ why doesn't the close() ofthe socket start the 2MSL timer? THere is obviosly a hole.. obviously (so->so_state & SS_CANTRCVMORE) is not true when tp->t_state = TCPS_FIN_WAIT_2; is executed, (tcp_input.c line 1414 in 2.2.2) and either tcp_usrclosed() is not being called during the socket closure for some reason, or the timer is being continually reset by something else. does any of you TCP sleuths have an idea of what migh tbe happenning? I will continue to research anyhow... julian From owner-freebsd-hackers Fri Jul 11 18:52:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA14116 for hackers-outgoing; Fri, 11 Jul 1997 18:52:48 -0700 (PDT) Received: from temp.harborcom.net (temp.harborcom.net [206.158.4.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA14110 for ; Fri, 11 Jul 1997 18:52:46 -0700 (PDT) Received: from localhost (weasel@localhost) by temp.harborcom.net (8.8.5/8.8.5) with SMTP id VAA01594 for ; Fri, 11 Jul 1997 21:53:16 -0400 (EDT) Date: Fri, 11 Jul 1997 21:53:16 -0400 (EDT) From: Bradley Reynolds To: freebsd-hackers@freebsd.org Subject: Data Recovery In-Reply-To: <199707112201.PAA25774@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if someone out there could help me with a data recovery problem. It seems that the disklabel on one of our scsi drives magically disappeared. Does anyone know any data recovery shops that are experienced with freeBSD (if possible, with this issue)? -Bradley From owner-freebsd-hackers Fri Jul 11 19:52:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA15660 for hackers-outgoing; Fri, 11 Jul 1997 19:52: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 TAA15655 for ; Fri, 11 Jul 1997 19:52:50 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA27497; Sat, 12 Jul 1997 12:22:29 +0930 (CST) From: Michael Smith Message-Id: <199707120252.MAA27497@genesis.atrad.adelaide.edu.au> Subject: Re: Data Recovery In-Reply-To: from Bradley Reynolds at "Jul 11, 97 09:53:16 pm" To: weasel@temp.harborcom.net (Bradley Reynolds) Date: Sat, 12 Jul 1997 12:22:29 +0930 (CST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bradley Reynolds stands accused of saying: > > I was wondering if someone out there could help me with a > data recovery problem. It seems that the disklabel on one > of our scsi drives magically disappeared. Do you know the details of the disklabel, ie. which partitions were where? If so, you can recreate the label fairly painlessly. > Does anyone know any data recovery shops that are experienced > with freeBSD (if possible, with this issue)? If all that's gone is the label, there are not a few FreeBSD hackers who would be able to recreate it fairly easily; what sort of geographic range could you ship the drive within? How vital is the data on the disk? Do you have a Recent Backup? > -Bradley -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Fri Jul 11 20:44:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17200 for hackers-outgoing; Fri, 11 Jul 1997 20:44:45 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17185 for ; Fri, 11 Jul 1997 20:44:26 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id JAA17572; Sat, 12 Jul 1997 09:46:30 +0600 (ESD) From: "Serge A. Babkin" Message-Id: <199707120346.JAA17572@hq.icb.chel.su> Subject: Re: /etc/init.d/ To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 12 Jul 1997 09:46:29 +0600 (ESD) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: <19970711211621.IU40866@uriah.heep.sax.de> from "J Wunsch" at Jul 11, 97 09:16:21 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > As Serge A. Babkin wrote: > > > > >> how about implementing /etc/init.d/ .. /etc/rc0.d etc Solaris-like > > > >> scheme in FreeBSD? I think it will be useful. And I am ready to do it. > > > > I think the scheme used in HP-UX 10 is better. It collects > > the scripts in /sbin/init.d, /sbin/rcX.d while their configuration > > files with tunable parameters are located in /etc/init.d. > > All SysV-derivatives do it this way, including but not limited to > Slowaris. SVR3s didn't have symlinks, they probably did it with hard > links then (and everything has been under /etc, of course). Nope. SysV just has the files in /etc/init.d and /etc/rcX.d. These files contain BOTH scripts and parameters. Yes, some of them use configuration files from /etc/default but it is not a common case and the connection between them is not obvious. -SB From owner-freebsd-hackers Fri Jul 11 21:11:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA18136 for hackers-outgoing; Fri, 11 Jul 1997 21:11:49 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18131 for ; Fri, 11 Jul 1997 21:11:43 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id AAA06758 for ; Sat, 12 Jul 1997 00:11:41 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id AAA09861 for ; Sat, 12 Jul 1997 00:11:40 -0400 Date: Sat, 12 Jul 1997 00:11:22 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-Hackers Subject: upgrading XFree86 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an overlay? Otherwise, this's gonna be the upgrade from hell ... ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Fri Jul 11 21:34:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA19011 for hackers-outgoing; Fri, 11 Jul 1997 21:34:59 -0700 (PDT) Received: from wakky.dyn.ml.org (lee@1Cust56.Max17.Washington.DC.MS.UU.NET [153.34.57.56]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19000 for ; Fri, 11 Jul 1997 21:34:34 -0700 (PDT) Received: (from lee@localhost) by wakky.dyn.ml.org (8.8.5/8.8.3) id AAA00798; Sat, 12 Jul 1997 00:33:57 -0400 (EDT) Message-ID: <19970712003357.51472@wakky.dyn.ml.org> Date: Sat, 12 Jul 1997 00:33:57 -0400 From: Lee Cremeans To: Chuck Robey Cc: hackers@freebsd.org Subject: Re: upgrading XFree86 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.66e Reply-to: hcremean@vt.edu X-OS: FreeBSD 2.2-RELEASE X-Evil: microsoft.com Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, Jul 12, 1997 at 12:11:22AM -0400, Chuck Robey wrote: > I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > overlay? Otherwise, this's gonna be the upgrade from hell ... > Yes, it can; in fact, that's the default for the 3.3 tarballs. It does not require you to start fresh (and AFAIK, Xfree never has). -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower)|A! JW223 "People are idiots who deserve to be mocked."--Dogbert|YWD+++i P&B+++ SL+++^i My home page:http://wakky.dyn.ml.org/~lee | MD+++r P+ I++ Di "Whoa, dumber than advertised!" | $++ E5/10/70/3c/73ac Ee34/1/36 H2 PonPippi From owner-freebsd-hackers Fri Jul 11 23:50:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA22954 for hackers-outgoing; Fri, 11 Jul 1997 23:50:56 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA22948 for ; Fri, 11 Jul 1997 23:50:48 -0700 (PDT) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.8.4/8.8.4) with SMTP id JAA05896; Sat, 12 Jul 1997 09:50:09 +0300 (EEST) Date: Sat, 12 Jul 1997 09:50:06 +0300 (EEST) From: Narvi To: Chuck Robey cc: FreeBSD-Hackers Subject: Re: upgrading XFree86 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Chuck Robey wrote: > I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > overlay? Otherwise, this's gonna be the upgrade from hell ... I don't know of a binary upgrade, but you certaibly can do so if you use the port (=upgrade from source). Sander There is no love, no good, no happiness and no future - all these are just illusions. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > From owner-freebsd-hackers Fri Jul 11 23:51:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA22980 for hackers-outgoing; Fri, 11 Jul 1997 23:51:10 -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 XAA22975 for ; Fri, 11 Jul 1997 23:51:04 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA22131; Sat, 12 Jul 1997 08:50:58 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA07409; Sat, 12 Jul 1997 08:47:43 +0200 (MET DST) Message-ID: <19970712084742.LO30344@uriah.heep.sax.de> Date: Sat, 12 Jul 1997 08:47:42 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@FreeBSD.ORG Cc: weasel@temp.harborcom.net (Bradley Reynolds) Subject: Re: Data Recovery References: <199707112201.PAA25774@phaeton.artisoft.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Bradley Reynolds on Jul 11, 1997 21:53:16 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bradley Reynolds wrote: > I was wondering if someone out there could help me with a > data recovery problem. It seems that the disklabel on one > of our scsi drives magically disappeared. If it's really only the disklabel, it's not a big deal: relabel the disk. If you have forgotten where your partitions are, search the disk for the filesystem `magic', this should at least get you those partitions boundaries back that have filesystems on it. -- 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 Sat Jul 12 02:14:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA26764 for hackers-outgoing; Sat, 12 Jul 1997 02:14:48 -0700 (PDT) Received: from ns.isi.co.jp (ns.isi.co.jp [202.214.62.35]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA26758 for ; Sat, 12 Jul 1997 02:14:44 -0700 (PDT) Received: (from john@localhost) by ns.isi.co.jp (8.6.12/3.4W2 ISI-Net 1996/10/27) id SAA28320; Sat, 12 Jul 1997 18:11:59 +0900 Date: Sat, 12 Jul 1997 18:11:59 +0900 From: john cooper Message-Id: <199707120911.SAA28320@ns.isi.co.jp> To: freebsd-hackers@FreeBSD.org Subject: Any 4x CD Writers supported yet? Cc: john@isi.com Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I'm wondering if anyone has managed to get any quad *write* speed drive to work. The two most common drives I see around here are the Yamaha CDR400 and TEAC CD-R50S. Any help/pointers would be most appreciated. Thanks, -john From owner-freebsd-hackers Sat Jul 12 02:57:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA28097 for hackers-outgoing; Sat, 12 Jul 1997 02:57:56 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA28092 for ; Sat, 12 Jul 1997 02:57:53 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.7.6/8.7.3) with SMTP id FAA02083; Sat, 12 Jul 1997 05:57:50 -0400 (EDT) Date: Sat, 12 Jul 1997 05:57:50 -0400 (EDT) From: Alfred Perlstein To: Charles Owens cc: BRiGHTMN , hackers list FreeBSD , ari.suutari@ps.carel.fi Subject: Re: ipfw rules processing order when DIVERTing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > www.cs.sunyit.edu/~perlsta > > > > it should be up later tonight... > > > Thanks... where on your marvey site might this be located? :-) > > BTW, yesterday afternoon when I checked I got snappy response from your > web server. Today it seems to be crawling mighty slow. I'm aweful sorry, i just got 128megs of ram at a bargain price from a friend and wanted to thouroughly check it before giving him the go ahead to spend my money :) the machines were down, but by this night it should be up :) From owner-freebsd-hackers Sat Jul 12 03:05:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA28375 for hackers-outgoing; Sat, 12 Jul 1997 03:05:38 -0700 (PDT) Received: from fang.cs.sunyit.edu (perlsta@fang.cs.sunyit.edu [192.52.220.66]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28370 for ; Sat, 12 Jul 1997 03:05:34 -0700 (PDT) Received: from localhost (perlsta@localhost) by fang.cs.sunyit.edu (8.7.6/8.7.3) with SMTP id GAA02119; Sat, 12 Jul 1997 06:05:27 -0400 (EDT) Date: Sat, 12 Jul 1997 06:05:27 -0400 (EDT) From: Alfred Perlstein To: Bradley Reynolds cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Data Recovery In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was wondering if someone out there could help me with a > data recovery problem. It seems that the disklabel on one > of our scsi drives magically disappeared. > > Does anyone know any data recovery shops that are experienced > with freeBSD (if possible, with this issue)? the minix partition editor is a god-send, it only modifies the partition info and not any structures in the partitions, if you remeber the size of the partition and make SURE ABSOLUTELY NOT to use "newfs" ie new file system (a.k.a. format) if you do the data will be gone, but if you do remeber the size of the partition EXACTLY :) you might be able to use the disklable program to fix it, if you have one large partition it's as easy as pie. Alfred perlsta@sunyit.edu From owner-freebsd-hackers Sat Jul 12 03:13:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA28567 for hackers-outgoing; Sat, 12 Jul 1997 03:13:47 -0700 (PDT) Received: from florence.pavilion.net (mailrelay1.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28560 for ; Sat, 12 Jul 1997 03:13:43 -0700 (PDT) Received: (from joe@localhost) by florence.pavilion.net (8.8.5/8.8.5) id LAA07696; Sat, 12 Jul 1997 11:12:16 +0100 (BST) Message-ID: <19970712111216.46819@pavilion.net> Date: Sat, 12 Jul 1997 11:12:16 +0100 From: Josef Karthauser To: "M.R.Murphy" Cc: hackers@FreeBSD.ORG, mrm@mole.mole.org Subject: Re: grins References: <199707111539.IAA21779@meerkat.mole.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199707111539.IAA21779@meerkat.mole.org>; from M.R.Murphy on Fri, Jul 11, 1997 at 08:39:38AM -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 11, 1997 at 08:39:38AM -0700, M.R.Murphy wrote: > > Just for grins: > > poco# date;uname -a;uptime > Fri Jul 11 08:38:09 PDT 1997 > FreeBSD poco.mole.org 1.1.5(RELEASE) POCO#0 i386 > 8:38am up 442 days, 2:53, 1 user, load average: 0.00, 0.00, 0.00 > poco# > > :-) Roll on modular kernel updates. All my machines are less than 100 days uptime, because of reboots onto new kernels ;( Joe -- Josef Karthauser Technical Manager Email: joe@pavilion.net Pavilion Internet plc. [Tel: +44 1273 607072 Fax: +44 1273 607073] From owner-freebsd-hackers Sat Jul 12 03:45:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA01261 for hackers-outgoing; Sat, 12 Jul 1997 03:45: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 DAA01248 for ; Sat, 12 Jul 1997 03:45:25 -0700 (PDT) Received: (qmail 603 invoked by uid 1000); 12 Jul 1997 10:38:54 -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: <199707112347.QAA11378@implode.root.com> Date: Sat, 12 Jul 1997 03:38:54 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: dg@root.com Subject: Re: Make World Explodes Cc: Michael Smith , FreeBSD-Hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi David Greenman; On 11-Jul-97 you wrote: ... > I doubt you are stupid. We are all ignorant. Anyway, stranger things > have happened and if things are working for you now, then great!!! No, no. I AM stupid. See here: int foo(int bar) { int ospl; ... splx(ospl); } I AM stupid. Took me a day to figure out the ``strange'' things that followed! Have a nice weekend, Y'all... Simon From owner-freebsd-hackers Sat Jul 12 04:46:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA02542 for hackers-outgoing; Sat, 12 Jul 1997 04:46:21 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA02537 for ; Sat, 12 Jul 1997 04:46:17 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA08404; Sat, 12 Jul 1997 07:01:55 -0400 (EDT) From: Peter Dufault Message-Id: <199707121101.HAA08404@hda.hda.com> Subject: Re: Make World Explodes In-Reply-To: from Simon Shapiro at "Jul 12, 97 03:38:54 am" To: Shimon@i-connect.net (Simon Shapiro) Date: Sat, 12 Jul 1997 07:01:54 -0400 (EDT) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > No, no. I AM stupid. See here: > > int > foo(int bar) > { > int ospl; > > ... > > splx(ospl); > } One of the truly great useful reasons for constructors/destructors. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hackers Sat Jul 12 06:57:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA05732 for hackers-outgoing; Sat, 12 Jul 1997 06:57:19 -0700 (PDT) Received: from cais.cais.com (root@cais.com [199.0.216.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA05727 for ; Sat, 12 Jul 1997 06:57:17 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [205.252.122.1]) by cais.cais.com (8.8.5/CJKv1.99-CAIS) with SMTP id JAA11406; Sat, 12 Jul 1997 09:57:13 -0400 (EDT) Received: from Journey2.mat.net (journey2.mat.net [205.252.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id JAA12005; Sat, 12 Jul 1997 09:57:12 -0400 Date: Sat, 12 Jul 1997 09:56:51 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Narvi cc: FreeBSD-Hackers Subject: Re: upgrading XFree86 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Narvi wrote: > > On Sat, 12 Jul 1997, Chuck Robey wrote: > > > I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > > existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > > overlay? Otherwise, this's gonna be the upgrade from hell ... > > I don't know of a binary upgrade, but you certaibly can do so if you use > the port (=upgrade from source). Thanks, guys, I'll try that. > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > > > ----------------------------+----------------------------------------------- > > 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! > > ----------------------------+----------------------------------------------- > > > > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Jul 12 07:13:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA06352 for hackers-outgoing; Sat, 12 Jul 1997 07:13:17 -0700 (PDT) Received: from limbo.senate.org (nathan@senate.org [204.141.125.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA06347 for ; Sat, 12 Jul 1997 07:13:11 -0700 (PDT) Received: (from nathan@localhost) by limbo.senate.org (8.8.5/8.8.5) id KAA17000; Sat, 12 Jul 1997 10:13:02 -0400 (EDT) From: Nathan Dorfman Message-Id: <199707121413.KAA17000@limbo.senate.org> Subject: Re: upgrading XFree86 In-Reply-To: from Narvi at "Jul 12, 97 09:50:06 am" To: narvi@haldjas.folklore.ee (Narvi) Date: Sat, 12 Jul 1997 10:13:02 -0400 (EDT) Cc: chuckr@glue.umd.edu, 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-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk You can do a binary upgrade. Read the RELNOTES in /pub/XFree86/3.3/binaries/ FreeBSD-2.2 (or whatever your FreeBSD version). > > On Sat, 12 Jul 1997, Chuck Robey wrote: > > > I want to upgrade my XFree86 to 3.3, but I have a ton of stuff in my > > existing /usr/X11R6 ... does anyone know if XFree86 can be upgraded via an > > overlay? Otherwise, this's gonna be the upgrade from hell ... > > I don't know of a binary upgrade, but you certaibly can do so if you use > the port (=upgrade from source). > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > > (301) 220-2114 | version 3.0 current -- and great FUN! > > ----------------------------+----------------------------------------------- > > > > > From owner-freebsd-hackers Sat Jul 12 10:38:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA12409 for hackers-outgoing; Sat, 12 Jul 1997 10:38:50 -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 KAA12404 for ; Sat, 12 Jul 1997 10:38:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.5/8.6.12) with SMTP id KAA18014; Sat, 12 Jul 1997 10:34:35 -0700 (PDT) Message-Id: <199707121734.KAA18014@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: Peter Dufault Cc: Shimon@i-connect.net (Simon Shapiro), hackers@freebsd.org Subject: Re: Make World Explodes Reply-To: Jason Thorpe From: Jason Thorpe Date: Sat, 12 Jul 1997 10:34:34 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997 07:01:54 -0400 (EDT) Peter Dufault wrote: > > int > > foo(int bar) > > { > > int ospl; > > > > ... > > > > splx(ospl); > > } ...so, you're saying that you didn't initalize ospl with an spl*() call? > One of the truly great useful reasons for constructors/destructors. Bah... -Wuninitialized. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Sat Jul 12 10:48:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA12751 for hackers-outgoing; Sat, 12 Jul 1997 10:48:13 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12746; Sat, 12 Jul 1997 10:48:08 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id KAA12133; Sat, 12 Jul 1997 10:48:13 -0700 (PDT) Message-Id: <199707121748.KAA12133@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org cc: Julian Elischer Subject: Re: sane-0.61, gimp In-reply-to: Your message of "Fri, 11 Jul 1997 23:32:58 EDT." <19970711233258.19580@tarsier.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Jul 1997 10:48:13 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Shouldn't the default for unknown devices be "SC_UNE_LU" and what happens if I have two unknown devices? Now that we have scsi scanner software perhaps whomever is mantaining scsiconf.c should start thinking about adding entries to scsiconf for the most popular scanners : umax, hp, etc... sane, scsi scanner, home web page is http://www.azstarnet.com/%7eaxplinux/sane/ Any clues as to why Eric's system can't seem to find his UMAX? Tnks, Amancio >From The Desk Of eric : > On Fri, Jul 11, 1997 at 07:29:02PM -0700, Amancio Hasty wrote: > > Hi, > > > > Sorry I forgot to post this : > > > > In scsiconf.c , > > #define SC_SHOWME 0x01 > > #define SC_ONE_LU 0x00 > > #define SC_MORE_LUS 0x02 > > > > static struct scsidevs unknowndev = > > { > > T_UNKNOWN, T_UNKNOWN, 0, "*", "*", "*", > > "uk", SC_ONE_LU > > /* "uk", SC_MORE_LUS*/ > > }; > > Make sure that you define uk to have only one "LU" > > > Hi-- thanks for responding so soon! > I changed scsiconf.c as you said, but now it returns "(aic0:5:0): error > code 96 " when trying to probe it, where before it seemed to successfully > probe it, but "found" eight copies of it, one for each LUN. Does this make > any sense? :) > > eric > > > > > If you like to get the graphical interface feel free to download > > ftp://rah.star-gate.com/pub/gimp-0.99.10.tar.gz > > > > Have fun, > > Amancio > > > > > > >From The Desk Of eric : > > > > > > > > > Hi... I saw a post in comp.unix.bsd.freebsd.misc where you said you are u sing > > > > > sane-0.61 and gimp with a UMAX scanner.. I'm trying to do the same thing but > > > am not having much luck, as the sane sources don't seem to know anything abou > > t > > > freebsd. Do you have any idea which SCSI device driver it's meant to be > > > using? Right now it's probing the scanner as "uk0" but I don't know if th at's > > > right. I've gotten "scanimage" (the non-graphical version) to compile but it > > > doesn't succeed in finding the scanner on /dev/uk0 or anything else for t hat > > > matter. Did you have to do anything special to get it to work? > > > > > > Eric Volpe > > > > > > > > > -- > ----------------------------------------------------------------------------- - > e|a|e|d|c| Eric Volpe > p|t|r|o|o| Erols Internet > v| |o|t|m| Springfield VA > | |l| | | USA > | |s| | | http://tarsier.colo.erols.net/Images/ > ----------------------------------------------------------------------------- - From owner-freebsd-hackers Sat Jul 12 11:50:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA14977 for hackers-outgoing; Sat, 12 Jul 1997 11:50:27 -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 LAA14969 for ; Sat, 12 Jul 1997 11:50:16 -0700 (PDT) Received: (qmail 23810 invoked by uid 1000); 12 Jul 1997 18:50:05 -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: <199707121101.HAA08404@hda.hda.com> Date: Sat, 12 Jul 1997 11:50:05 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Peter Dufault Subject: Re: Make World Explodes Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Peter Dufault; On 12-Jul-97 you wrote: > > No, no. I AM stupid. See here: > > > > int > > foo(int bar) > > { > > int ospl; > > > > ... > > > > splx(ospl); > > } > > One of the truly great useful reasons for constructors/destructors. Yup. Balance that with: ``Have you everseen an O/S written in C++ ?'' I have. Not funny. Simon From owner-freebsd-hackers Sat Jul 12 11:57:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA15158 for hackers-outgoing; Sat, 12 Jul 1997 11:57:49 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA15153 for ; Sat, 12 Jul 1997 11:57:47 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA08196; Sat, 12 Jul 1997 11:56:49 -0700 Date: Sat, 12 Jul 1997 11:56:49 -0700 (PDT) From: "Brian N. Handy" To: john cooper Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Any 4x CD Writers supported yet? In-Reply-To: <199707120911.SAA28320@ns.isi.co.jp> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hmm, I'm not sure if anyone has tried these models in particular, but more or less everything seems to act like an HP or a Plasmon...if you were to borrow one, plug it in and make the appropriate adjustment to scsiconf.c so it probes right, it might work. (That's how the Phillips Cdd2600 came to be supported one day.) I'm sure Joerg will have a more specific answer here, standard operating procedure... :-) Happy trails, brian From owner-freebsd-hackers Sat Jul 12 14:59:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA21564 for hackers-outgoing; Sat, 12 Jul 1997 14:59:20 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA21558 for ; Sat, 12 Jul 1997 14:59:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA28921; Sat, 12 Jul 1997 14:53:13 -0700 From: Terry Lambert Message-Id: <199707122153.OAA28921@phaeton.artisoft.com> Subject: Re: TCP bug in 2.2 To: julian@whistle.com (Julian Elischer) Date: Sat, 12 Jul 1997 14:53:13 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <33C6D138.7D55368C@whistle.com> from "Julian Elischer" at Jul 11, 97 05:35:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > If I could borrow the ear of someone with more knowledge of TCP > states than me.. > > We see the following in a kernel dated from around March 4 > and from the logs it looks as if it's present in 2.2.2+ > > finger, (after a lot of iterations of the test) > goes into a permanent wait reading from a socket. > > the socket is seen to be in FIN_WAIT_2 state > after the finger proces is killed the socket STAYS in FIN_WAIT_2 > state forever. > > from what I've read in tcp_input.c etc. This shouldn't happen. > > 2 problems: > 1/ why doesn't finger wake up and return EOF? Probably you have an Annex or similar terminal server which has a buggy TCP/IP implementation which does not correctly do option negotiation. See /etc/sysconfig: ---------------------------------------------------------------------- # # Some broken implementations can't handle the RFC 1323 and RFC 1644 # TCP options. If TCP connections randomly hang, try disabling this, # and bug the vendor of the losing equipment. # tcp_extensions=NO ---------------------------------------------------------------------- Also, get an updated stack forwhatever hardware you have which is failing to implement TCP/IP according to the RFC's. There could be less obvious problems with the stack as well, so it's a good idea to not trust it until it's updated. > 2/ why doesn't the close() ofthe socket start > the 2MSL timer? This is generally the case with Winsock implementations in general and Microsoft's in particular. Microsoft OS's don't do resource tracking correctly, and so even though you can now tell that a program has exited in Windows95, the Windows 3.1 Winsock code still requires that the client application call "shutdown()" on the socket prior to closing it. Basically, Microsoft's TCP/IP stack is too stupid to send the FIN like it's supposed to on the close. This is mostly a problem if: 1) You reboot a machine without shuttding down all Winsock clients. 2) Your client program crashes and expect the OS to be able to back out state on its behalf. 3) The client software was ported from a sane TCP/IP environment, like UNIX, and the programmers have no idea that "shutdown()" is supposed to be called (amazingly enough, on UNIX systems, calling "shutdown()" shuts the machine down... who would have ever thought of naming a function for what the function does? Apparently not the originators of Winsock.). Try correcting your client software. Also try running client machines with OS's that can't be crashed by client programs (ie: real protected mode operating systems). Finally, try running an OS that knows how to recover resources that a program was using in the event of a program crash which does not crash the OS (ie: real protected mode operating systems). > and either tcp_usrclosed() is not being called > during the socket closure for some reason, > or the timer is being continually reset by something else. The timer is not started until the FIN is sent if SO_KEEPALIVE was specified by the client. It usually is. 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 Jul 12 15:04:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21789 for hackers-outgoing; Sat, 12 Jul 1997 15:04:20 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA21781 for ; Sat, 12 Jul 1997 15:04:16 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA28939; Sat, 12 Jul 1997 14:57:30 -0700 From: Terry Lambert Message-Id: <199707122157.OAA28939@phaeton.artisoft.com> Subject: Re: Make World Explodes To: dufault@hda.com (Peter Dufault) Date: Sat, 12 Jul 1997 14:57:30 -0700 (MST) Cc: Shimon@i-connect.net, hackers@FreeBSD.ORG In-Reply-To: <199707121101.HAA08404@hda.hda.com> from "Peter Dufault" at Jul 12, 97 07:01:54 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ ... variable used before being initialized ... ] > One of the truly great useful reasons for constructors/destructors. One of the truly great useful reasons for making warnings fatal when you are compiling kernels. This would have generated a warning if the highest warnings were on. Oh, and the other great reason for constructors/destructors is to make your code slow when you want to take objects out of scope. 8-|. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Sat Jul 12 15:05:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21864 for hackers-outgoing; Sat, 12 Jul 1997 15:05:08 -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 PAA21857 for ; Sat, 12 Jul 1997 15:05:05 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA28953; Sat, 12 Jul 1997 14:58:30 -0700 From: Terry Lambert Message-Id: <199707122158.OAA28953@phaeton.artisoft.com> Subject: Re: Make World Explodes To: Shimon@i-connect.net (Simon Shapiro) Date: Sat, 12 Jul 1997 14:58:30 -0700 (MST) Cc: dufault@hda.com, hackers@FreeBSD.ORG In-Reply-To: from "Simon Shapiro" at Jul 12, 97 11:50:05 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > One of the truly great useful reasons for constructors/destructors. > > Yup. Balance that with: ``Have you everseen an O/S written in C++ ?'' > I have. Not funny. > Oh, Sprite and Choices are bad, but they're not that bad... 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 Jul 12 15:46:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23489 for hackers-outgoing; Sat, 12 Jul 1997 15:46:39 -0700 (PDT) Received: from phoenix.its.rpi.edu (dec@phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23484 for ; Sat, 12 Jul 1997 15:46:35 -0700 (PDT) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.5/8.8.5) with SMTP id SAA10617 for ; Sat, 12 Jul 1997 18:47:06 -0400 (EDT) Date: Sat, 12 Jul 1997 18:47:06 -0400 (EDT) From: "David E. Cross" To: hackers@freebsd.org Subject: Re: TCP bug in 2.2 In-Reply-To: <199707122153.OAA28921@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Terry Lambert wrote: > 3) The client software was ported from a sane TCP/IP environment, > like UNIX, and the programmers have no idea that "shutdown()" > is supposed to be called (amazingly enough, on UNIX systems, > calling "shutdown()" shuts the machine down... who would have > ever thought of naming a function for what the function does? > Apparently not the originators of Winsock.). The library call shutdown(2) is used to 'shut down' part of a full-duplex socket, you can in essence close() a connection with shutdown(2). -- David Cross From owner-freebsd-hackers Sat Jul 12 16:04:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23957 for hackers-outgoing; Sat, 12 Jul 1997 16:04:53 -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 QAA23949 for ; Sat, 12 Jul 1997 16:04:50 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id QAA01338 for ; Sat, 12 Jul 1997 16:04:49 -0700 (PDT) Message-Id: <199707122304.QAA01338@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: hackers@freebsd.org Subject: Re: system hangs with umax Astra 1200S / freebsd In-reply-to: Your message of "Sat, 12 Jul 1997 18:53:09 EDT." <19970712185309.07650@tarsier.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Jul 1997 16:04:49 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Move to hackers list from sane mailing list: Any clues as to what why the 1522 may a cause a system to hang? Also eric when you get a chance can you try out the "uk" device? Tnks, Amancio >From The Desk Of eric : > On Sat, Jul 12, 1997 at 12:45:36PM -0700, David Mosberger-Tang wrote: > > > > Hmmh, what version of FreeBSD and what SCSI controller are you using? > > I find it strange that a user-level SCSI program would hang the entire > > system. I suppose it might be possible for the scanner to block the > > SCSI bus if something bad happens, but it should not lock up the > > entire system. Hence I wonder whether the problem might be with the > > generic SCSI driver, rather than the UMAX backend. > > > > --david > > > This seemed very strange to me too, but apparently the problem has been > resolved. > > First, it wasn't a matter of the scanner blocking the scsi bus -- it had an > entire scsi bus to itself on an Adaptec 1522 (which turned out to be the > problem) > Second, I'm using the "pt" driver, although i suspect the "uk" driver would > work too now that I've moved the scanner to an Adaptec 2940W. > Everything works more or less fine now, except the scanner still needs to be > the _only_ device on the bus. If I put a disk on the same bus as the scanner, > (with a different SCSI id# obviously) accesses to the disk time out and stuff . > It seems like it may be a termination issue, which I'll fiddle around with > some more. > But anyway, it will not work at all using an AHA1522, with either a Umax or > an HP4c scanner. > > Thank's for all the help! > > > eric > > -- > Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ > To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com > From owner-freebsd-hackers Sat Jul 12 17:05:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA25529 for hackers-outgoing; Sat, 12 Jul 1997 17:05:25 -0700 (PDT) Received: from bug.fe.up.pt (bug.fe.up.pt [193.136.54.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA25523 for ; Sat, 12 Jul 1997 17:05:20 -0700 (PDT) Received: (from jmg@localhost) by bug.fe.up.pt (8.8.5/8.8.5) id BAA14218; Sun, 13 Jul 1997 01:05:12 +0100 Date: Sun, 13 Jul 1997 01:05:11 +0100 (WET DST) From: Jorge Goncalves To: hackers@freebsd.org Subject: w and finger command Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think that like most Unices FreeBSD's w command should report something like this 12:44AM up 184 days, 9:50, 4 users, load averages: 1.63, 1.45, 1.33 USER TTY FROM LOGIN@ IDLE WHAT jmg console - 12:06AM 25 - jmg p0 :0.0 12:13AM - tail -f log jmg p1 :0.0 12:41AM - irc jmg irc.freebsd.org (irc-2 jmg p2 :0.0 12:44AM - w instead of using a 3 character TTY field. About the finger command it should report 'console' as 'co' and not as 'con' as it does. Thanks in advance and in special to all members of the FreeBSD team, keep up with the good work! Jorge From owner-freebsd-hackers Sat Jul 12 17:47:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26758 for hackers-outgoing; Sat, 12 Jul 1997 17:47:59 -0700 (PDT) Received: from polya.blah.org (slmel57p28.ozemail.com.au [203.108.203.236]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26750 for ; Sat, 12 Jul 1997 17:47:49 -0700 (PDT) Received: (from ada@localhost) by polya.blah.org (8.8.6/8.8.5) id KAA09515 for freebsd-hackers@freebsd.org; Sun, 13 Jul 1997 10:47:38 +1000 (EST) From: Ada T Lim Message-Id: <199707130047.KAA09515@polya.blah.org> Subject: Re: CD Writers (was Any 4x...) In-Reply-To: from "Brian N. Handy" at "Jul 12, 97 11:56:49 am" To: freebsd-hackers@freebsd.org Date: Sun, 13 Jul 1997 10:47:38 +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-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hmm, I'm not sure if anyone has tried these models in particular, but more > or less everything seems to act like an HP or a Plasmon...if you were to > borrow one, plug it in and make the appropriate adjustment to scsiconf.c > so it probes right, it might work. (That's how the Phillips Cdd2600 came > to be supported one day.) On this note, has anyone managed to get the matshita/panasonic 2x writer to work? This is a fairly popular bottom-end drive that I know quite a few people have, and I'd like to know if anyone else has started ona driver before I start wasting blanks :) Ada From owner-freebsd-hackers Sat Jul 12 17:48:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26799 for hackers-outgoing; Sat, 12 Jul 1997 17:48:14 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26790 for ; Sat, 12 Jul 1997 17:48:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id KAA05537; Sun, 13 Jul 1997 10:41:37 +1000 Date: Sun, 13 Jul 1997 10:41:37 +1000 From: Bruce Evans Message-Id: <199707130041.KAA05537@godzilla.zeta.org.au> To: dufault@hda.com, thorpej@nas.nasa.gov Subject: Re: Make World Explodes Cc: hackers@FreeBSD.ORG, Shimon@i-connect.net Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ...so, you're saying that you didn't initalize ospl with an spl*() call? > One of the truly great useful reasons for constructors/destructors. Bah... -Wuninitialized. We had -W in the default kernel-building flags, but we turned it off when gcc-2.7 broke -W by adding uncontrollable warnings for sign mismatches to it. -W implies -Wuninitialized and doesn't cause annoying warnings that "-Wuninitialized is not supported without -O". I guess we should use -Wuninitialized anyway. Bruce From owner-freebsd-hackers Sat Jul 12 18:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28248 for hackers-outgoing; Sat, 12 Jul 1997 18:21:26 -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 SAA28231 for ; Sat, 12 Jul 1997 18:21:07 -0700 (PDT) Received: (qmail 27235 invoked by uid 1000); 13 Jul 1997 01:21:03 -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: <199707121734.KAA18014@lestat.nas.nasa.gov> Date: Sat, 12 Jul 1997 18:21:03 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Jason Thorpe Subject: Re: Make World Explodes Cc: hackers@freebsd.org, Peter Dufault Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Jason Thorpe; On 12-Jul-97 you wrote: ... > ...so, you're saying that you didn't initalize ospl with an spl*() call? (embaressed) yes. Happens to the best of us. So why not me? > > One of the truly great useful reasons for constructors/destructors. > > Bah... -Wuninitialized. In the days of Sixth Edition we used to compete who knows more ls flags. Then it became vi commands. Now it is gcc -W. Should be in the kernel mk rules. No? Simon From owner-freebsd-hackers Sat Jul 12 18:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28250 for hackers-outgoing; Sat, 12 Jul 1997 18:21:26 -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 SAA28233 for ; Sat, 12 Jul 1997 18:21:08 -0700 (PDT) Received: (qmail 27246 invoked by uid 1000); 13 Jul 1997 01:21:03 -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: <199707122157.OAA28939@phaeton.artisoft.com> Date: Sat, 12 Jul 1997 18:21:03 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Terry Lambert Subject: Re: Make World Explodes Cc: hackers@FreeBSD.ORG, (Peter Dufault) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Terry Lambert; On 12-Jul-97 you wrote: ... > One of the truly great useful reasons for making warnings fatal when > you are compiling kernels. This would have generated a warning if the > highest warnings were on. Is there a quick and simple (read global) way of doing it? > Oh, and the other great reason for constructors/destructors is to > make your code slow when you want to take objects out of scope. 8-|. This is a very good feature. Would have solved some of my DPT problems. Simon From owner-freebsd-hackers Sat Jul 12 18:54:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29491 for hackers-outgoing; Sat, 12 Jul 1997 18:54:11 -0700 (PDT) Received: from server.local.sunyit.edu (A-V25.rh.sunyit.edu [150.156.211.85]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29486 for ; Sat, 12 Jul 1997 18:54:08 -0700 (PDT) Received: from localhost (brightmn@localhost) by server.local.sunyit.edu (8.8.5/8.8.5) with SMTP id VAA01836 for ; Tue, 24 Jun 1997 21:55:16 GMT Date: Tue, 24 Jun 1997 21:55:16 +0000 (GMT) From: BRiGHTMN To: hackers@FreeBSD.ORG Subject: My web page is up, NATd!!!!!! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Re all, just a couple of days ago i promised to post some info on NATd on my webpage, well it's up at: http://www.cs.sunyit.edu/~perlsta right now my page is has frames, tabels and graphics but because of the tutorials and in the interest of making the page accessable to all i will soon "port" it to text mode. :) sorry for the delay guys. Alfred perlsta@cs.sunyit.edu From owner-freebsd-hackers Sat Jul 12 19:00:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA29797 for hackers-outgoing; Sat, 12 Jul 1997 19:00:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29792 for ; Sat, 12 Jul 1997 19:00:22 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA00796; Sun, 13 Jul 1997 11:30:16 +0930 (CST) From: Michael Smith Message-Id: <199707130200.LAA00796@genesis.atrad.adelaide.edu.au> Subject: Re: system hangs with umax Astra 1200S / freebsd In-Reply-To: <199707122304.QAA01338@rah.star-gate.com> from Amancio Hasty at "Jul 12, 97 04:04:49 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 13 Jul 1997 11:30:15 +0930 (CST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty stands accused of saying: > Move to hackers list from sane mailing list: > > Any clues as to what why the 1522 may a cause a system to hang? The 'aic' driver is Less Than Wonderful. Someone with some motivation and matching documentation should perhaps spend some time on it. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 12 19:50:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA01882 for hackers-outgoing; Sat, 12 Jul 1997 19:50:21 -0700 (PDT) Received: from news.skyinet.net (NEWS.SKYINET.NET [206.101.197.231]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA01877; Sat, 12 Jul 1997 19:50:15 -0700 (PDT) From: trump@foursssst.com Received: from www1.qzn.skyinet.net (WWW1.QZN.SKYINET.NET [206.101.197.226]) by news.skyinet.net (8.8.5/8.8.5) with ESMTP id KAA22981; Sun, 13 Jul 1997 10:54:19 -0800 (GMT) Message-Id: <199707131854.KAA22981@news.skyinet.net> To: you@internet-wide.com Date: Sat, 12 Jul 97 19:54:31 EST Subject: Your mail sent to me by mistake. Reply-To: trump@foursssst.com Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Did you know that as many as 70% of all Americans have negative or incorrect information on their credit report and that one in five complaints to the Federal Trade Commission is against Credit Bureaus. ARE YOU ONE OF THE MILLIONS OF AMERICANS REJECTED FOR CREDIT? If so, we have the information you need: >>Remove negative and incorrect information from your credit report<< * Bankruptcies - REMOVED * Repossessions - REMOVED * Tax Liens - REMOVED * Judgments - REMOVED * Charge Offs - REMOVED * Late Payments - REMOVED >>Get all of the credit cards you want<< >>Obtain a Home mortgage<< >>Qualify for a car loan<< Everyone is entitled to a better lifestyle for themselves and their family and especially such a basic need as a house, a car, or credit cards. Imagine the thrill of driving home for the first time in a new car and showing it to your friends, relatives and neighbors, or the convenience of having a credit card for making purchases, or fulfilling the American dream of owning a Home. NOW IT IS POSSIBLE! All of the information you need is contained in our confidential report; =============================== "Insider's Guide to Credit Repair Secrets." =============================== Best of all, you can have this report RIGHT NOW, delivered directly to your e-mail address in a matter of minutes. Read on for further details. The "Insider's Guide to Credit Repair Secrets" contains everything you need in order to repair your own credit report. In addition, as the title implies, we include some of the industries best kept and guarded secrets, things the Credit Bureaus and Banks don't want you to know. Don't pay hundreds or perhaps thousands of dollars to a credit repair agency. You can do it yourself for FREE, with equal or better results. ===> BONUS OFFER <=== The "Insider's Guide to Credit Repair Secrets" normally sells for $9.95. If you order now, we will include two FREE bonus reports with your order. Each bonus report normally retails for $9.95. You get all three reports for just $9.95.............a $29.85 value. BONUS REPORT #1 HOW TO GET A CREDIT CARD OR BANK LOAN * Shaping your application to improve your chances of being approved * How creditors rate an application * Hot tips on how you can stack the odds in your favor * How to use a co-signer * Secured credit cards * How to establish AAA credit in 30 days BONUS REPORT #2 TOP 10 WEB SITES FOR FREE CREDIT REPAIR & CREDIT CARD INFO These 10 Web sites are the best of the best. All of them are absolutely FREE. They contain additional credit repair information, tips on obtaining credit cards and loans, databases of hundreds upon hundreds of credit card issuers, consumer help on overcoming debt and much, much more........ HOW TO ORDER!!! To have all three reports delivered immediately to your e-mail address, all you need to do is follow these simple steps; 1) Get a pen and piece of paper ready to write down an important e-mail address. 2) Call 1-900-448-8901. (Your phone bill will be charged $9.95 for this call. If you are under 18 years of age, you must receive parental permission before calling) 3) Listen to the 900 number recording and write down the e-mail address given. 4) Send any e-mail message to the address given on the recording and within minutes, the three reports will be electronically delivered to your e-mail inbox. Isn't $9.95 a small price to pay for the convenience of a clean credit record and all of the advantages that go along with it. Order the "Insider's Guide to Credit Repair Secrets", plus the two FREE bonus reports today and start enjoying the credit you deserve. The information supplied in the "Insiders Guide to Credit Repair Secrets" is applicable only to United States residents. If you have received this e-mail solicitation and live outside the United States of America, please accept our apology and disregard this message. Thank you. From owner-freebsd-hackers Sat Jul 12 20:23:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA02897 for hackers-outgoing; Sat, 12 Jul 1997 20:23:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02892 for ; Sat, 12 Jul 1997 20:23:10 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA01113 for hackers@freebsd.org; Sun, 13 Jul 1997 12:53:08 +0930 (CST) From: Michael Smith Message-Id: <199707130323.MAA01113@genesis.atrad.adelaide.edu.au> Subject: IPX routing? To: hackers@freebsd.org Date: Sun, 13 Jul 1997 12:53:07 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a document anywhere which describes the delicacies of setting up a FreeBSD box as an IPX router? I ask as a result of the following scenario, which I had hoped to turn into a minor triumph. A couple of weeks ago, I was contracted by a large secondary college to assemble an SMTP/POP mail server/web cache/web server system for their network of ~150 workstations. Modulo some connectivity problems with their provider, the system has performed faultlessly. Buoyed by this success (in the face of the endless unreliability of the preceeding Netware solution), they asked if the BSD system could be upgraded and used to route their three networks, as well as providing DHCP services for their clients. We installed the ISC DHCP server (and Ted & Paul, if you hear this, _Thankyou_ and congratulations on a fine piece of software!) and verified that it did not exhibit any of the untoward symptoms the Novell server has, and then proceeded to configure the system to route IPX traffic. It was at this point that things came unstuck; adding IPX support to the kernel was quite straightforward, as was assigning IPX addresses to the interface. Except that one can only assign a single net address to each interface, and Netware servers insist on using different net addresses for 802.2 and 802.3 frame types. This isn't discussed in any of the documentation. 8( Next, IPXrouted was started, and in trace mode it was certainly seeing a lot of relevant traffic, but it wasn't learning any routes from it. After much tinkering trying to make various things work, we had to back the system out and reinstate the Novell server, something that neither I nor the customer really wanted to do. So, any suggestions? I could probably be convinced to roll some longer words onthe subject if the information was available... -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sat Jul 12 21:12:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA04187 for hackers-outgoing; Sat, 12 Jul 1997 21:12:27 -0700 (PDT) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04181 for ; Sat, 12 Jul 1997 21:12:21 -0700 (PDT) Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.8.5/1.2.3) with ESMTP id WAA06142; Sat, 12 Jul 1997 22:12:18 -0600 (MDT) Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.8.5/8.8.5) id WAA04700; Sat, 12 Jul 1997 22:11:37 -0600 (MDT) Date: Sat, 12 Jul 1997 22:11:37 -0600 (MDT) From: Alan Lundin Message-Id: <199707130411.WAA04700@lundin.abq.nm.us.> In-Reply-To: Terry Lambert "Re: /etc/init.d/" (Jul 11, 3:01pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Terry Lambert Subject: Re: /etc/init.d/ Cc: freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jul 11, 3:01pm, Terry Lambert wrote: > Subject: Re: /etc/init.d/ > > > I guess I don't see what the problem with the > > current system is. Currently you can have one > > script (assuming you have NFS mounting it amoung > > N machines) that says: > > > > case `hostname` in > > $SERVER) > > ;; > > esac > > > > where if it is moved to /etc/rc.d, then you must > > maintain N scripts, AND you stand more of a chance > > that those scripts will get clobbered on the next > > OS upgrade. > > What if I *want* to clobber the scripts for upgraded facilities > when I upgrade the facility? That's why you put the above code in /usr/local/etc/rc.d/httpd.sh (I guess I didn't say that did I?) > What if I want to upgrade some facilities, but not others? I > guess you'd have me editing up my rc file so that I couldn't > upgrade without editing it again (big hassle). No, my mistake for not stating that the code would go into /usr/local/etc/rc.d/***.sh rather than /etc/rc.*. --alan From owner-freebsd-hackers Sat Jul 12 22:53:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA07010 for hackers-outgoing; Sat, 12 Jul 1997 22:53:18 -0700 (PDT) Received: from temp.harborcom.net (temp.harborcom.net [206.158.4.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA07005 for ; Sat, 12 Jul 1997 22:53:14 -0700 (PDT) Received: from localhost (weasel@localhost) by temp.harborcom.net (8.8.5/8.8.5) with SMTP id BAA04903; Sun, 13 Jul 1997 01:54:05 -0400 (EDT) Date: Sun, 13 Jul 1997 01:54:05 -0400 (EDT) From: Bradley Reynolds To: Michael Smith cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Data Recovery In-Reply-To: <199707120252.MAA27497@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I was wondering if someone out there could help me with a > > data recovery problem. It seems that the disklabel on one > > of our scsi drives magically disappeared. > > Do you know the details of the disklabel, ie. which partitions were where? > If so, you can recreate the label fairly painlessly. > Its been tried and didn't work. > If all that's gone is the label, there are not a few FreeBSD hackers who > would be able to recreate it fairly easily; what sort of geographic range > could you ship the drive within? How vital is the data on the disk? > Do you have a Recent Backup? > The recent backup is > 1month old, so we were trying to do this before using that.